Processing control commands:
> tags -1 +pending
Bug #835949 [linux-grsec] linux-grsec: non-standard gcc/g++ used for build
(gcc-5)
Added tag(s) pending.
--
835949: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835949
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
control: tags -1 +pending
On Tue, 14 Feb 2017 09:39:12 +0100 Yves-Alexis Perez wrote:
> > Â It seems that src:linux was fixed
> > Â https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835957
>
> Yes I know. I'm waiting for the src:linux 4.9.9 upload to upload linux-grsec.
On Feb/16, Henri Salo wrote:
> Shouldn't this be closed AFTER the fix is available? Especially since this is
> a
> security issue.
Yes. Bastien, can you please reopen this ?
Cheers,
--Seb
Shouldn't this be closed AFTER the fix is available? Especially since this is a
security issue.
--
Henri Salo
Source: nodejs
Version: 4.7.2~dfsg-2
Severity: serious
Justification: fails to build from source
Dear Maintainer,
The subject package fails to build on alpha systems due to an inappropriate
selection of compiler flags during configuration. In particular "-m32" is not
valid on alpha.
My guess
Source: libgudev
Version: 231-1
Severity: serious
Forwarded: https://bugzilla.gnome.org/show_bug.cgi?id=778734
The test suite that was added in 231 fails on various architectures as
can be seen at
https://buildd.debian.org/status/package.php?p=libgudev=experimental
**
Control: tag -1 pending
Cyril Brulebois (2017-02-13):
> Switching from the Full to the non-Full variant of this font seems to be
> the way to go, at least at the moment, see Changwoo Ryu's reply and mine:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853917#32
>
Processing control commands:
> tag -1 pending
Bug #853921 [fonts-android-udeb] fonts-android-udeb: broken rendering for
Korean glyphs in debian-installer
Added tag(s) pending.
--
853921: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853921
Debian Bug Tracking System
Contact
Hi.
It builds ok for me on eight different autobuilders,
using sbuild on a sid chroot.
Chris, I would try with sbuild and without docker.
Thanks.
Hi Uwe,
this bug is supposed to be fixed in 1.6.2.
I've uploaded a test build to people.debian.org [1]. It would be great
if you can test those packages and report back to confirm whether it's
really fixed for you or not.
Michael
[1] deb [trusted=yes] https://people.debian.org/~biebl/nm ./
--
On 16 Feb 2017, at 9:56 AM, Chris Lamb wrote:
>
> Potter, Tim wrote:
>
>> On 16 Feb 2017, at 9:06 AM, Chris Lamb wrote:
>
>> Hi everyone. This upload is part of updated build dependencies for Docker
>> 1.13.0.
>> Currently the pipeline is stalled while a
On 10/02/17 13:38, Juan Cespedes wrote:
> Package: accountsservice
> Version: 0.6.43-1
> Severity: serious
>
> Summary: accounts-daemon.service fails to work properly when there are
> two users in the system with the same UID. The service is still
> running, but it shows an error message and
Potter, Tim wrote:
> On 16 Feb 2017, at 9:06 AM, Chris Lamb wrote:
> Hi everyone. This upload is part of updated build dependencies for Docker
> 1.13.0.
> Currently the pipeline is stalled while a few things sit in the NEW queue.
> When
> that's all sorted out everything
On 16 Feb 2017, at 9:06 AM, Chris Lamb wrote:
>
> Felipe Sateler wrote:
>
>> Cannot start service web: rpc error: code = 2 desc
>> = "oci runtime error: flag provided but not defined: -bundle"
>
> I can reproduce this. Downgrading to 0.1.1+dfsg1-2 fixed this for me.
Hi
Felipe Sateler wrote:
> Cannot start service web: rpc error: code = 2 desc
> = "oci runtime error: flag provided but not defined: -bundle"
I can reproduce this. Downgrading to 0.1.1+dfsg1-2 fixed this for me.
Regards,
--
,''`.
: :' : Chris Lamb
`. `'`
Andreas Tille wrote:
> tags 854341 unreproducible
> thanks
>
> I can confirm that it now also builds for me again. I'm tempted to
> close this bug again which seems to have been a temporary issue of some
> Build-Dependency.
Still doesn't build for me, alas. Same error.
Regards,
--
Control: severity -1 important
Petter Reinholdtsen wrote:
> Can you explain what rationale you have for setting the severity as
> serious? To me it seem like an important bug at most.
I interpreted it as a "severe violation of Debian policy." A typo in
the upstream version would be relatively
Processing control commands:
> severity -1 important
Bug #839100 [python-bluez] python-bluez: debian pybluez package version 0.22-1
uses upstream source code version 0.18
Severity set to 'important' from 'serious'
--
839100: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839100
Debian Bug
Package: libmariadbclient-dev
Version: 10.1.21-5
Severity: serious
% dpkg --list | grep mariadb
ii libmariadbclient-dev 10.1.21-5amd64MariaDB database
development files
ii libmariadbclient18:amd64 10.1.21-5amd64MariaDB database
client library
%
Your message dated Wed, 15 Feb 2017 21:35:18 +
with message-id
and subject line Bug#854336: fixed in spice 0.12.8-2.1
has caused the Debian Bug report #854336,
regarding CVE-2016-9577 CVE-2016-9578
to be marked as done.
This means that you claim that the
Processing commands for cont...@bugs.debian.org:
> found 854336 0.12.5-1
Bug #854336 [src:spice] CVE-2016-9577 CVE-2016-9578
Marked as found in versions spice/0.12.5-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
854336:
Your message dated Wed, 15 Feb 2017 19:34:12 +
with message-id
and subject line Bug#855076: fixed in giac 1.2.3.25+dfsg1-2
has caused the Debian Bug report #855076,
regarding giac: FTBFS: .../giac-doc/...: No such file or directory
to be marked as done.
Processing control commands:
> tags -1 - patch
Bug #855130 [src:med-fichier] med-fichier: MED library is not compatible with
HDF5 1.10
Removed tag(s) patch.
--
855130: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=855130
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tags -1 - patch
Hi Gilles,
thanks for your effort on this bug, very appreciate. Unfortunately
the provided patch does not solve the problem. med-fichier still
fails on autopkgtests and unit tests. I have to remove the patch
tag.
Best regards
Anton
2017-02-15 9:41 GMT+01:00 Gilles
On Wed 2017-02-15 12:09:54 -0500, Roger Shimizu wrote:
> On Thu, Feb 16, 2017 at 1:36 AM, James Cowgill wrote:
>> On 15/02/17 11:24, Roger Shimizu wrote:
>>> On Wed, Feb 15, 2017 at 7:51 PM, James Cowgill wrote:
So do you know why the tests
Your message dated Wed, 15 Feb 2017 18:49:27 +
with message-id
and subject line Bug#851876: fixed in slt 0.0.git20140301-3
has caused the Debian Bug report #851876,
regarding slt: FTBFS on uniprocessor systems - testsuite deadlocks
to be marked as done.
Hi,
On Wed, Feb 15, 2017 at 07:17:18PM +0100, Salvatore Bonaccorso wrote:
> Please adjust the affected versions in the BTS as needed.
If I did not something wrong, am I right that the issue was introduced
only after 2.8.0, and so older versions in jessie is not affected?
Regards,
Salvatore
Source: qemu
Version: 1:2.8+dfsg-2
Severity: grave
Tags: patch security upstream
Justification: user security hole
Hi,
the following vulnerability was published for qemu.
CVE-2017-2630[0]:
nbd: oob stack write in client routine drop_sync
If you fix the vulnerability please also make sure to
Processing commands for cont...@bugs.debian.org:
> fixed 817232 console-setup/1.60
Bug #817232 {Done: Christian Perrier }
[keyboard-configuration] postinst trying to disable /etc/init.d/keyboard-setup
Marked as fixed in versions console-setup/1.60.
> thanks
Stopping
Your message dated Wed, 15 Feb 2017 17:11:03 +
with message-id
and subject line Bug#854587: fixed in icedove 1:45.7.1-1
has caused the Debian Bug report #854587,
regarding icedove: incorrect start-version in {icedove,thunderbird}.maintscript
to be marked
Your message dated Wed, 15 Feb 2017 17:18:46 +
with message-id
and subject line Bug#854680: fixed in puppet 4.8.2-3
has caused the Debian Bug report #854680,
regarding puppet: service enable control broken when sysv-rc is not present
to be marked as done.
Your message dated Wed, 15 Feb 2017 17:11:03 +
with message-id
and subject line Bug#854135: fixed in icedove 1:45.7.1-1
has caused the Debian Bug report #854135,
regarding icedove-l10n-bn-bd: depends on unavailable thunderbird-l10n-bn-bg
to be marked as
Your message dated Wed, 15 Feb 2017 17:11:03 +
with message-id
and subject line Bug#852867: fixed in icedove 1:45.7.1-1
has caused the Debian Bug report #852867,
regarding icedove: debuild fails because mozilla build system requires SHELL
env var set
to
On Thu, Feb 16, 2017 at 1:36 AM, James Cowgill wrote:
>
> On 15/02/17 11:24, Roger Shimizu wrote:
>> Dear James,
>>
>> On Wed, Feb 15, 2017 at 7:51 PM, James Cowgill wrote:
>>>
>>> So do you know why the tests only pass when using 2 CPUs? That seems
>>>
Processing commands for cont...@bugs.debian.org:
> # forgot to cc control...
> retitle 851876 slt: FTBFS on uniprocessor systems - testsuite deadlocks
Bug #851876 [src:slt] slt: FTBFS (Test killed with quit: ran too long (10m0s))
Changed Bug title to 'slt: FTBFS on uniprocessor systems -
Hello,
I had the same problem on the last version of gitlab in Debian Stretch.
I download manually the deb of unstable and it solved my problem.
My actual gitlab version is 8.13.11+dfsg-2
signature.asc
Description: OpenPGP digital signature
retitle 851876 slt: FTBFS on uniprocessor systems - testsuite deadlocks
forwarded 851876 https://github.com/inconshreveable/slt/issues/5
thanks
Hi,
On 15/02/17 11:24, Roger Shimizu wrote:
> Dear James,
>
> On Wed, Feb 15, 2017 at 7:51 PM, James Cowgill wrote:
>>
>> So do
Processing commands for cont...@bugs.debian.org:
> found 854925 56.0.2924.76-1
Bug #854925 [chromium] chromium: Chromium does not start -- execv failed: No
such file or directory
Marked as found in versions chromium-browser/56.0.2924.76-1.
> thanks
Stopping processing here.
Please contact me if
Package: kubernetes-master
Version: 1.2.5+dfsg-1
Severity: serious
Justification: renders package unusable
Hi!
Trying to install the kubernetes-master package on Debian unstable fails with:
root@test-janluca2:~# apt install kubernetes-master
Reading package lists... Done
Building dependency
Package: runc
Version: 1.0.0~rc2+git20161109.131.5137186-1
Severity: grave
Justification: renders docker unusable
Control: affects -1 docker.io
After upgrading to 1.0.0~rc2+git20161109.131.5137186-1 , docker
containers fail to start:
Cannot start service web: rpc error: code = 2 desc = "oci
Processing control commands:
> affects -1 docker.io
Bug #855208 [runc] runc: 1.0 release candidate breaks docker 1.11 - oci runtime
error: flag provided but not defined: -bundle
Added indication that 855208 affects docker.io
--
855208: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=855208
On 2017-02-15 14:22, Adrien Grellier wrote:
> Do you think fusioninventory will made its way to stretch ?
I'm sorry, but it's too late for that (deadline was Jan 5th).
> The freeze is here, I see no package in testing, but only this bug is
> blocking. In my lab, we are using fusioninventory a
Your message dated Wed, 15 Feb 2017 14:44:35 +0100
with message-id <20170215134435.7tatr5zyxz43c...@mapreri.org>
and subject line Re: Bug#855207: owncloud: ownCloud cannot be updated because
of wrong dependency information, see ownCloud Issue 26999
has caused the Debian Bug report #855207,
Control: reassign -1 release.debian.org
Control: forcemerge 854905 -1
On Wed, Feb 15, 2017 at 01:09:16PM +, James Cowgill wrote:
> Package: libpetsc3.7.5-dev
> Version: 3.7.5+dfsg1-3
> Severity: serious
> Tags: sid stretch
Please look for already reported bugs before reporting new ones
Processing control commands:
> reassign -1 release.debian.org
Bug #855204 [libpetsc3.7.5-dev] libpetsc3.7.5-dev: uninstallable - Depends:
libopenmpi-dev (< 2.0.2~git.20161226)
Bug reassigned from package 'libpetsc3.7.5-dev' to 'release.debian.org'.
No longer marked as found in versions
Package: owncloud
Version: 8.1.9-12.1
Severity: grave
Justification: renders package unusable
See:
https://github.com/owncloud/core/issues/26999
and
https://central.owncloud.org/t/debian-package-conflict-how-to-update-owncloud/5753
-- System Information:
Debian Release: 8.7
APT prefers
Hello,
I may be wrong, but this clearly shows that the Unattended Upgrades Shutdown
unit starts once the target Network is being brought down :
> Feb 15 12:35:52 ZunattendedUpgrade systemd[1]: Stopped target Network is
> Online.
> Feb 15 12:35:52 ZunattendedUpgrade systemd[1]: Stopped target
Hi,
Do you think fusioninventory will made its way to stretch ?
The freeze is here, I see no package in testing, but only this bug is
blocking. In my lab, we are using fusioninventory a lot on Debian, so I
am very interesting to have it for the next stable version.
Kind regards,
Adrien
--
Package: libpetsc3.7.5-dev
Version: 3.7.5+dfsg1-3
Severity: serious
Tags: sid stretch
Hi,
libpetsc3.7.5-dev 3.7.5+dfsg1-3 and 3.7.5+dfsg1-4 cannot be installed
in unstable. This may or may not affect stretch depending on whether
openmpi migrates (I have conservatively tagged it for the moment).
tags 854341 unreproducible
thanks
I can confirm that it now also builds for me again. I'm tempted to
close this bug again which seems to have been a temporary issue of some
Build-Dependency.
Chris, what do you think?
Kind regards
Andreas.
On Tue, Feb 14, 2017 at 08:47:32PM +0100, gregor
Processing commands for cont...@bugs.debian.org:
> tags 854341 unreproducible
Bug #854341 [src:libchado-perl] libchado-perl: FTBFS: The following enviroment
variables not detected: CHADO_DB_USERNAME
Ignoring request to alter tags of bug #854341 to the same tags previously set
> thanks
Stopping
On Wed, 2017-02-15 at 11:13 +, Simon McVittie wrote:
> On Sat, 26 Nov 2016 at 10:27:38 +, Ben Hutchings wrote:
[...]
> > The temporary workaround with /dev/ptmx could be made optional. It's
> > not OK to break the previously working configurations.
>
> If I'm understanding the situation
Your message dated Wed, 15 Feb 2017 11:48:43 +
with message-id
and subject line Bug#854474: fixed in alsa-lib 1.1.3-5
has caused the Debian Bug report #854474,
regarding alsa-lib: FTBFS when built with dpkg-buildpackage -A
to be marked as done.
This means
On Sat, 26 Nov 2016 at 10:27:38 +, Ben Hutchings wrote:
> On Fri, 2016-11-25 at 18:54 +0100, Marco d'Itri wrote:
> > setup_devices_simple() could be easily modified to create /dev/ptmx with
> > mknod instead of the current symlink.
That's presumably:
- ln -s pts/ptmx $TARGET/dev/ptmx
On Tue, Feb 14, 2017 at 06:36:05PM +, Debian Bug Tracking System wrote:
> shotwell (0.25.4+really0.24.5-0.1) unstable; urgency=medium
> .
>* Revert to last stable release 0.24.5 (Closes: #850149).
Thanks for this! Shotwell is finally usable again.
However the original problem (as
Your message dated Wed, 15 Feb 2017 11:01:10 +0100
with message-id
Your message dated Wed, 15 Feb 2017 09:34:12 +
with message-id
and subject line Bug#855103: fixed in webkit2gtk 2.14.5-1
has caused the Debian Bug report #855103,
regarding Rendering fails on wayland/hidpi
to be marked as done.
This means that you claim
Control: tags -1 + patch
On 2017-02-14 14:37, Gilles Filippini wrote:
Source: med-fichier
Version: 3.0.6-11
Severity: grave
Justification: renders package unusable
Hi,
From the Salome Platform support forum [1]:
Problems with Salome and Code Saturne in Debian
Posted by Elektrix at January
Processing control commands:
> tags -1 + patch
Bug #855130 [src:med-fichier] med-fichier: MED library is not compatible with
HDF5 1.10
Added tag(s) patch.
--
855130: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=855130
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
59 matches
Mail list logo