Processed: severity of 852093 is grave

2019-01-09 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 852093 grave Bug #852093 [src:hesiod] hesiod: CVE-2016-10152: Use of hard-coded DNS domain if configuration file cannot be read Severity set to 'grave' from 'normal' > thanks Stopping processing here. Please contact me if you need assis

Processed (with 1 error): Re: Bug#917693: python-skbio: FTBFS: dh_auto_test: pybuild --test --test-nose -i python{version} -p 3.7 returned exit code 13

2019-01-09 Thread Debian Bug Tracking System
Processing control commands: > tags -1 upstream help Bug #917693 [src:python-skbio] python-skbio: FTBFS: dh_auto_test: pybuild --test --test-nose -i python{version} -p 3.7 returned exit code 13 Added tag(s) upstream and help. > forward -1 https://github.com/biocore/scikit-bio/issues/1648 Unknown

Bug#917693: python-skbio: FTBFS: dh_auto_test: pybuild --test --test-nose -i python{version} -p 3.7 returned exit code 13

2019-01-09 Thread Andreas Tille
Control: tags -1 upstream help Control: forward -1 https://github.com/biocore/scikit-bio/issues/1648 I admit I wished python-numpy would do some transition procedure instead of throwing RC candidates to unstable. -- http://fam-tille.de

Processed: severity of 852094 is grave

2019-01-09 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 852094 grave Bug #852094 [src:hesiod] hesiod: CVE-2016-10151: Weak SUID check allowing privilege elevation Severity set to 'grave' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 852094:

Bug#901530: marked as done (fix build failure with libcdio-2.0)

2019-01-09 Thread Debian Bug Tracking System
Your message dated Wed, 09 Jan 2019 09:20:35 + with message-id and subject line Bug#901530: fixed in fuse-umfuse-iso9660 0.3-1.3 has caused the Debian Bug report #901530, regarding fix build failure with libcdio-2.0 to be marked as done. This means that you claim that the problem has been dea

Bug#899516: marked as done (fuse-umfuse-fat: Invalid maintainer address pkg-vsquare-de...@lists.alioth.debian.org)

2019-01-09 Thread Debian Bug Tracking System
Your message dated Wed, 09 Jan 2019 09:20:24 + with message-id and subject line Bug#899516: fixed in fuse-umfuse-fat 0.1a-1.2 has caused the Debian Bug report #899516, regarding fuse-umfuse-fat: Invalid maintainer address pkg-vsquare-de...@lists.alioth.debian.org to be marked as done. This m

Bug#916067: marked as done (fuse-umfuse-ext2 FTBFS with glibc 2.28)

2019-01-09 Thread Debian Bug Tracking System
Your message dated Wed, 09 Jan 2019 09:20:13 + with message-id and subject line Bug#916067: fixed in fuse-umfuse-ext2 0.4-1.2 has caused the Debian Bug report #916067, regarding fuse-umfuse-ext2 FTBFS with glibc 2.28 to be marked as done. This means that you claim that the problem has been de

Bug#899514: marked as done (fuse-umfuse-iso9660: Invalid maintainer address pkg-vsquare-de...@lists.alioth.debian.org)

2019-01-09 Thread Debian Bug Tracking System
Your message dated Wed, 09 Jan 2019 09:20:35 + with message-id and subject line Bug#899514: fixed in fuse-umfuse-iso9660 0.3-1.3 has caused the Debian Bug report #899514, regarding fuse-umfuse-iso9660: Invalid maintainer address pkg-vsquare-de...@lists.alioth.debian.org to be marked as done.

Bug#899817: marked as done (fuse-umfuse-ext2: Invalid maintainer address pkg-vsquare-de...@lists.alioth.debian.org)

2019-01-09 Thread Debian Bug Tracking System
Your message dated Wed, 09 Jan 2019 09:20:13 + with message-id and subject line Bug#899817: fixed in fuse-umfuse-ext2 0.4-1.2 has caused the Debian Bug report #899817, regarding fuse-umfuse-ext2: Invalid maintainer address pkg-vsquare-de...@lists.alioth.debian.org to be marked as done. This

Bug#899905: marked as done (lwipv6: Invalid maintainer address pkg-vsquare-de...@lists.alioth.debian.org)

2019-01-09 Thread Debian Bug Tracking System
Your message dated Wed, 09 Jan 2019 09:34:19 + with message-id and subject line Bug#899905: fixed in lwipv6 1.5a-3 has caused the Debian Bug report #899905, regarding lwipv6: Invalid maintainer address pkg-vsquare-de...@lists.alioth.debian.org to be marked as done. This means that you claim

Processed: The bug in the cruft package prevented testing migration

2019-01-09 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 914680 src:plplot 5.13.0+dfsg-10 Bug #914680 {Done: Ole Streicher } [libplplotada3] libplplotada3: missing Breaks+Replaces: libplplotada2 Bug reassigned from package 'libplplotada3' to 'src:plplot'. No longer marked as found in versions

Bug#917693: Please use a transition for new python-numpy versions

2019-01-09 Thread Andreas Tille
Hi Sandro, python-numpy has a lot of rdepends and new numpy versions. In the past every version bump of numpy has broken some of these. I'd propose to use the well established transition procedure[1] for new numpy versions specifically if you intend to upload RC candidates this should not just b

Bug#917745: marked as done (cross-toolchain-base: FTBFS: applying patches fails)

2019-01-09 Thread Debian Bug Tracking System
Your message dated Wed, 9 Jan 2019 11:11:36 +0100 with message-id and subject line Re: cross-toolchain-base: FTBFS: applying patches fails has caused the Debian Bug report #917745, regarding cross-toolchain-base: FTBFS: applying patches fails to be marked as done. This means that you claim that t

Bug#918780: koji-client: should depend on python-requests and python-dateutil

2019-01-09 Thread Juhani Numminen
Package: koji-client Version: 1.16.0-2 Severity: serious Justification: Policy 3.5 Hi, Forwarding https://bugs.launchpad.net/ubuntu/+bug/1803423 which also happens in Debian Buster. The koji command cannot be used without installing some dependencies first. $ koji help Traceback (most recent cal

Bug#918742: Initialization loop/deadlock when used with jemalloc

2019-01-09 Thread Johannes Schauer
Hi, On Wed, 9 Jan 2019 00:27:03 +0200 Faidon Liambotis wrote: > So jemalloc 5.1.0-2 was recently uploaded to unstable. The build currently > fails due to the explicit dependency on libjemalloc1 (cf. #918741), but as > soon as this gets fixed, another issue is uncovered: > > While building this

Bug#899724: marked as done (vdetelweb: Invalid maintainer address pkg-vsquare-de...@lists.alioth.debian.org)

2019-01-09 Thread Debian Bug Tracking System
Your message dated Wed, 09 Jan 2019 10:23:26 + with message-id and subject line Bug#899724: fixed in vdetelweb 1.2.1-2 has caused the Debian Bug report #899724, regarding vdetelweb: Invalid maintainer address pkg-vsquare-de...@lists.alioth.debian.org to be marked as done. This means that you

Bug#899562: marked as done (kernel-patch-viewos: Invalid maintainer address pkg-vsquare-de...@lists.alioth.debian.org)

2019-01-09 Thread Debian Bug Tracking System
Your message dated Wed, 09 Jan 2019 10:23:17 + with message-id and subject line Bug#899562: fixed in umview 0.8.2-1.2 has caused the Debian Bug report #899562, regarding kernel-patch-viewos: Invalid maintainer address pkg-vsquare-de...@lists.alioth.debian.org to be marked as done. This means

Bug#899659: marked as done (purelibc: Invalid maintainer address pkg-vsquare-de...@lists.alioth.debian.org)

2019-01-09 Thread Debian Bug Tracking System
Your message dated Wed, 09 Jan 2019 10:22:20 + with message-id and subject line Bug#899659: fixed in purelibc 0.4.1-2 has caused the Debian Bug report #899659, regarding purelibc: Invalid maintainer address pkg-vsquare-de...@lists.alioth.debian.org to be marked as done. This means that you c

Bug#916165: marked as done (purelibc FTBFS with glibc 2.28)

2019-01-09 Thread Debian Bug Tracking System
Your message dated Wed, 09 Jan 2019 10:22:20 + with message-id and subject line Bug#916165: fixed in purelibc 0.4.1-2 has caused the Debian Bug report #916165, regarding purelibc FTBFS with glibc 2.28 to be marked as done. This means that you claim that the problem has been dealt with. If thi

Bug#916170: marked as done (umview FTBFS with glibc 2.28)

2019-01-09 Thread Debian Bug Tracking System
Your message dated Wed, 09 Jan 2019 10:23:17 + with message-id and subject line Bug#916170: fixed in umview 0.8.2-1.2 has caused the Debian Bug report #916170, regarding umview FTBFS with glibc 2.28 to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#918782: libvideo-info-perl: non-free package uploaded source-only

2019-01-09 Thread Adrian Bunk
Source: libvideo-info-perl Version: 0.993-3 Severity: serious https://tracker.debian.org/pkg/libvideo-info-perl Long-term this might be fixable with https://www.debian.org/doc/manuals/developers-reference/ch05.en.html#non-free-buildd Short-term this needs a binary uploaded (feel free to close th

Bug#918764: udev: "udevadm control --reload-rules" kills all processes except init

2019-01-09 Thread Axel Beckert
Hi, Axel Beckert wrote: > I have no idea why this is happening, but several packages use "udevadm > control --reload-rules" in their postinst (e.g. fuse) and if that's run, > all process except init are instantly killed (reproducibly; the gettys > seem to be respawned by init then, so I can login

Bug#918741: maintaining fakechroot

2019-01-09 Thread Johannes Schauer
Hi Piotr, I recently NMU-ed fakechroot and now two more RC bugs popped up: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918741 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918741 is it okay if I NMU these again or do you want to take care of them? I'm the maintainer of a reverse depe

Bug#918382: marked as done (trying to overwrite '/usr/lib/x86_64-linux-gnu/libIlmImf-2_3.so.24.0.0', which is also in package libopenexr23:amd64 2.3.0-3)

2019-01-09 Thread Debian Bug Tracking System
Your message dated Wed, 09 Jan 2019 10:38:54 + with message-id and subject line Bug#918382: fixed in openexr 2.3.0-5 has caused the Debian Bug report #918382, regarding trying to overwrite '/usr/lib/x86_64-linux-gnu/libIlmImf-2_3.so.24.0.0', which is also in package libopenexr23:amd64 2.3.0-

Bug#917953: marked as done (openexr: Incomplete debian/copyright?)

2019-01-09 Thread Debian Bug Tracking System
Your message dated Wed, 09 Jan 2019 10:38:54 + with message-id and subject line Bug#917953: fixed in openexr 2.3.0-5 has caused the Debian Bug report #917953, regarding openexr: Incomplete debian/copyright? to be marked as done. This means that you claim that the problem has been dealt with.

Bug#899726: marked as done (vde2: Invalid maintainer address pkg-vsquare-de...@lists.alioth.debian.org)

2019-01-09 Thread Debian Bug Tracking System
Your message dated Wed, 09 Jan 2019 10:42:29 + with message-id and subject line Bug#899726: fixed in vde2 2.3.2+r586-2.2 has caused the Debian Bug report #899726, regarding vde2: Invalid maintainer address pkg-vsquare-de...@lists.alioth.debian.org to be marked as done. This means that you cl

Bug#918569: Could not find 'activerecord' (~> 4.2) - did find: [activerecord-5.2.0]

2019-01-09 Thread Pirate Praveen
On Wed, Jan 9, 2019 at 3:46 PM, t...@schleuder.org wrote: You probably mean a debian package? Unfortunately the maintainer is traveling currently and the rest of us don't know enough to build the package. We could probably produce an unofficial gem once the change is finished if that also

Bug#915804: Should this package be removed?

2019-01-09 Thread Antonio Radici
On Wed, Jan 09, 2019 at 12:03:03AM +0100, Moritz Mühlenhoff wrote: > On Wed, Dec 19, 2018 at 11:56:47PM +0100, Sebastian Andrzej Siewior wrote: > > On 2018-12-06 22:52:32 [+0100], Moritz Muehlenhoff wrote: > > > Source: cfengine2 > > > Severity: serious > > > > > > This is replaced by src:cfengine

Bug#918780: marked as done (koji-client: should depend on python-requests and python-dateutil)

2019-01-09 Thread Debian Bug Tracking System
Your message dated Wed, 09 Jan 2019 11:36:12 + with message-id and subject line Bug#918780: fixed in koji 1.16.0-3 has caused the Debian Bug report #918780, regarding koji-client: should depend on python-requests and python-dateutil to be marked as done. This means that you claim that the pro

Processed: Re: Bug#917693: python-skbio: FTBFS: dh_auto_test: pybuild --test --test-nose -i python{version} -p 3.7 returned exit code 13

2019-01-09 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forwarded 917693 https://github.com/biocore/scikit-bio/issues/1648 Bug #917693 [src:python-skbio] python-skbio: FTBFS: dh_auto_test: pybuild --test --test-nose -i python{version} -p 3.7 returned exit code 13 Set Bug forwarded-to-address to 'http

Bug#918090: theano: C-optimized ops fail with "module 'numpy.core.multiarray' has no attribute '_get_ndarray_c_version'"

2019-01-09 Thread Emilio Pozuelo Monfort
Hi Rebecca, On Thu, 3 Jan 2019 07:26:32 + "Rebecca N. Palmer" wrote: > Source: theano > Version: 1.0.2+dfsg-1 > Severity: serious > Control: tags -1 patch > > Many Theano operations include C code for speed; the compilation process > uses an undocumented Numpy function to check ABI compatib

Bug#918578: gosa: GOsa web interface missing password field

2019-01-09 Thread Eliza Ralph
What further information do you need? What do I do in the case when "apt-cache depends" shows multiple package versions? If I check what version of PHP is running, I get PHP Version => 7.3.0-2. I inherited the system from the previous admin and admittedly it is in a mess. On Mon, 7 Jan 2019 at

Processed: Re: Bug#918722: debootstrap: says InRelease file expired

2019-01-09 Thread Debian Bug Tracking System
Processing control commands: > severity -1 serious Bug #918722 [debootstrap] debootstrap: says InRelease file expired Severity set to 'serious' from 'normal' -- 918722: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918722 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#918722: debootstrap: says InRelease file expired

2019-01-09 Thread Julien Cristau
On 1/8/19 7:46 PM, Michael Büsch wrote: > Package: debootstrap > Version: 1.0.113 > Severity: normal > > When bootstrapping Raspbian with debootstrap it fails since version 1.0.113: > > debootstrap --arch=armhf --foreign --verbose > --keyring=raspbian.public.key.gpg stretch /my/directory > ht

Bug#918511: Bug #918511 in golang-github-shopify-sarama marked as pending

2019-01-09 Thread Christos Trochalakis
Control: tag -1 pending Hello, Bug #918511 in golang-github-shopify-sarama reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/go-team/packages/golang-github-shopi

Bug#899892: marked as done (umview: Invalid maintainer address pkg-vsquare-de...@lists.alioth.debian.org)

2019-01-09 Thread Debian Bug Tracking System
Your message dated Wed, 9 Jan 2019 13:06:44 + with message-id <20190109130644.gc18...@esaurito.net> and subject line fix for wrong changelog entry has caused the Debian Bug report #899892, regarding umview: Invalid maintainer address pkg-vsquare-de...@lists.alioth.debian.org to be marked as do

Processed: fix for wrong changelog entry

2019-01-09 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reopen 899562 Bug #899562 {Done: Renzo Davoli } [src:kernel-patch-viewos] kernel-patch-viewos: Invalid maintainer address pkg-vsquare-de...@lists.alioth.debian.org 'reopen' may be inappropriate when a bug has been closed with a version; all fixe

Processed: Bug #918511 in golang-github-shopify-sarama marked as pending

2019-01-09 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #918511 [golang-github-shopify-sarama-dev] golang-github-shopify-sarama-dev: missing dependency on golang-github-datadog-zstd-dev Added tag(s) pending. -- 918511: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918511 Debian Bug Tracking Syst

Processed: 915642

2019-01-09 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 915642 libcap-ng0 0.7.9-1 Bug #915642 [libapache2-mod-authnz-pam] AuthBasicProvider PAM crashes apache Bug reassigned from package 'libapache2-mod-authnz-pam' to 'libcap-ng0'. No longer marked as found in versions libapache2-mod-authnz-pa

Processed: bug 918670 is forwarded to https://github.com/floatdrop/duplexer3/issues/2

2019-01-09 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forwarded 918670 https://github.com/floatdrop/duplexer3/issues/2 Bug #918670 [src:node-duplexer3] node-duplexer3 FTBFS with nodejs 10.15.0 Set Bug forwarded-to-address to 'https://github.com/floatdrop/duplexer3/issues/2'. > thanks Stopping proces

Processed: Re: Bug#918578: gosa: GOsa web interface missing password field

2019-01-09 Thread Debian Bug Tracking System
Processing control commands: > severity -1 important Bug #918578 [gosa] gosa: GOsa web interface missing password field Severity set to 'important' from 'serious' -- 918578: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918578 Debian Bug Tracking System Contact ow...@bugs.debian.org with pro

Bug#918578: gosa: GOsa web interface missing password field

2019-01-09 Thread Holger Levsen
control: severity -1 important thanks On Mon, Jan 07, 2019 at 06:36:35PM +0100, Wolfgang Schweer wrote: > On Mon, Jan 07, 2019 at 04:20:23PM +0200, Eliza wrote: > > After some updates were applied, the password field disappeared from > > GOsa. The text label "Password" exist, but the text box is

Processed: Bug #918054 in elkcode marked as pending

2019-01-09 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #918054 [src:elkcode] elkcode: frequent test hangs Ignoring request to alter tags of bug #918054 to the same tags previously set -- 918054: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918054 Debian Bug Tracking System Contact ow...@bugs.deb

Processed: Bug #918054 in elkcode marked as pending

2019-01-09 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #918054 [src:elkcode] elkcode: frequent test hangs Added tag(s) pending. -- 918054: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918054 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#918054: Bug #918054 in elkcode marked as pending

2019-01-09 Thread Michael Banck
Control: tag -1 pending Hello, Bug #918054 in elkcode reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/debichem-team/elkcode/commit/92ff4984d9cc50d07e993148e43d2

Bug#918054: Bug #918054 in elkcode marked as pending

2019-01-09 Thread Michael Banck
Control: tag -1 pending Hello, Bug #918054 in elkcode reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/debichem-team/elkcode/commit/ac8efbe3fbaf3af9b76de3b7c125e

Processed: Bug #918670 in node-duplexer3 marked as pending

2019-01-09 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #918670 [src:node-duplexer3] node-duplexer3 FTBFS with nodejs 10.15.0 Added tag(s) pending. -- 918670: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918670 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#918670: Bug #918670 in node-duplexer3 marked as pending

2019-01-09 Thread Xavier Guimard
Control: tag -1 pending Hello, Bug #918670 in node-duplexer3 reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/js-team/node-duplexer3/commit/8c74f0c3152ab0730e61b

Processed: tagging 918670

2019-01-09 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 918670 + upstream Bug #918670 [src:node-duplexer3] node-duplexer3 FTBFS with nodejs 10.15.0 Added tag(s) upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 918670: https://bugs.debian.org/cgi-bin/bugre

Bug#900269: Also hit by this bug

2019-01-09 Thread Hilko Bengen
Hi, I just had the what seems to be the same bug happen to me. This is the relevant output form pstree: , | `-sudo,21446 apt dist-upgrade | `-apt,21447 dist-upgrade | `-dpkg,22875 --status-fd 39 --configure --pending | `-ifupdown.postin,22876 /var/lib/dpkg/info/ifupdo

Bug#918722: marked as done (debootstrap: says InRelease file expired)

2019-01-09 Thread Debian Bug Tracking System
Your message dated Wed, 09 Jan 2019 13:49:46 + with message-id and subject line Bug#918722: fixed in debootstrap 1.0.114 has caused the Debian Bug report #918722, regarding debootstrap: says InRelease file expired to be marked as done. This means that you claim that the problem has been dealt

Bug#918511: marked as done (golang-github-shopify-sarama-dev: missing dependency on golang-github-datadog-zstd-dev)

2019-01-09 Thread Debian Bug Tracking System
Your message dated Wed, 09 Jan 2019 13:50:20 + with message-id and subject line Bug#918511: fixed in golang-github-shopify-sarama 1.20.0-2 has caused the Debian Bug report #918511, regarding golang-github-shopify-sarama-dev: missing dependency on golang-github-datadog-zstd-dev to be marked as

Bug#917672: marked as done (yp-svipc: FTBFS: python/svipc_module.c:869:28: error: expected expression before ')' token)

2019-01-09 Thread Debian Bug Tracking System
Your message dated Wed, 09 Jan 2019 14:06:22 + with message-id and subject line Bug#917672: fixed in yp-svipc 0.16-3 has caused the Debian Bug report #917672, regarding yp-svipc: FTBFS: python/svipc_module.c:869:28: error: expected expression before ')' token to be marked as done. This means

Bug#918808: neutron-fwaas-common: fails to remove: IndentationError in "/usr/bin/neutron-plugin-manage", line 117

2019-01-09 Thread Andreas Beckmann
Package: neutron-fwaas-common Version: 1:13.0.1-3 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to remove. >From the attached log (scroll to the bottom...): Removing neutron-fwaas-common (1:13.0.1-3) ...

Bug#900997: print-manager: probability of package in buster?

2019-01-09 Thread Steven De Herdt
Dear maintainers If a patch providing Antonio's proposed stop-gap message is provided, is it still possible for print-manager to get into buster? In that case, I may possibly try to hack something like that. Thanks for your work and consideration! -Steven

Bug#915345: Remove roar support for now? (Fixes FTBFS)

2019-01-09 Thread Helge Kreutzmann
Hello Ryan, cmus is marked for autoremoval, the freeze is approaching (where no removed packages are allowed to reenter testing) and I see no activity from the cmus side. Also at least the mpd developers are not very confident in the code quality of libroar https://github.com/MusicPlayerDaemon/MPD

Bug#918817: lintian: Returns with exit code of 0 (zero) on failed tests

2019-01-09 Thread Chris Lamb
Package: lintian Version: 2.5.119 Severity: serious X-Debbugs-CC: Felix Lechner Hi Felix, It appears like one of your recent changes has meant that a failing test does not return an non-zero error code. For example: $ debian/rules runtests onlyrun=01-critic t/scripts/01-critic/commands.

Bug#917670: python-pbcore: FTBFS: dh_auto_test: numpy 1.16 arraysetops dtype error

2019-01-09 Thread Drew Parsons
Source: python-pbcore Followup-For: Bug #917670 Control: title -1 FTBFS: dh_auto_test: numpy 1.16 arraysetops dtype error Control: forwarded -1 https://github.com/PacificBiosciences/pbcore/issues/120 Confirmed, still occurs with pbcore 1.6.5. Bug filed upstream. Drew

Processed (with 1 error): python-pbcore: FTBFS: dh_auto_test: numpy 1.16 arraysetops dtype error

2019-01-09 Thread Debian Bug Tracking System
Processing control commands: > title -1 FTBFS: dh_auto_test: numpy 1.16 arraysetops dtype error Unknown command or malformed arguments to command. > forwarded -1 https://github.com/PacificBiosciences/pbcore/issues/120 Bug #917670 [src:python-pbcore] python-pbcore: FTBFS: dh_auto_test: pybuild --

Bug#918823: libc6: [24945.428485] libvirtd[12553]: segfault at 8 ip 00007fb0f515ba63 sp 00007fff86e08370 error 4 in ld-2.24.so[7fb0f514b000+23000]

2019-01-09 Thread leopoldotosi
Package: libc6 Version: 2.24-11+deb9u3 Severity: critical Tags: d-i Justification: breaks unrelated software Dear Maintainer, I can not work libvirtd ?-:-( Reading symbols from virsh...(no debugging symbols found)...done. (gdb) set pagination 8 "on" or "off" expected. (gdb) run Starting progr

Bug#662960: ssmtp doesn't validate server TLS certificates

2019-01-09 Thread Cédric Dufour - Idiap Research Institute
Any chance seeing this issue addressed or its severity lowered, so we can have the package in Buster ? Given its purpose - "extremely simple MTA [...]" - should this issue really be considered "serious" (and Release Critical) ? PS: ssmtp is extremely handy to forward machine-generated messages

Bug#918742: Initialization loop/deadlock when used with jemalloc

2019-01-09 Thread Johannes Schauer
Hi Faidon, Quoting Faidon Liambotis (2019-01-09 16:16:40) > On Wed, Jan 09, 2019 at 11:23:19AM +0100, Johannes Schauer wrote: > > Maybe you can report this directly to upstream? > I thought of that, but then I saw that upstream is Piotr, who is also listed > as a Maintainer of this package. Is tha

Bug#662960: ssmtp doesn't validate server TLS certificates

2019-01-09 Thread Simon Deziel
On 2019-01-09 10:23 a.m., Cédric Dufour - Idiap Research Institute wrote: > PS: ssmtp is extremely handy to forward machine-generated messages in large > deployments, internally, iow. where TLS is not required ssmtp seems like abandonware. Have you tried msmtp(-mta)? It works in a similar way, is

Bug#918817: lintian: Returns with exit code of 0 (zero) on failed tests

2019-01-09 Thread Felix Lechner
Please see https://salsa.debian.org/lintian/lintian/merge_requests/121 although I cannot explain the exit code '2' right now.

Bug#907718: python-dateutil breaks python-vobject autopkgtest

2019-01-09 Thread Adrian Bunk
On Thu, Dec 13, 2018 at 11:21:35PM +0100, Jonas Smedegaard wrote: > Control: tags -1 help > > Quoting Guido Günther (2018-12-13 19:21:45) > > On Thu, Dec 13, 2018 at 05:53:03PM +0100, Jonas Smedegaard wrote: > > > @Guido, could you please have a fresh look at this bug to see if it > > > can eithe

Bug#918817: marked as done (lintian: Returns with exit code of 0 (zero) on failed tests)

2019-01-09 Thread Debian Bug Tracking System
Your message dated Wed, 09 Jan 2019 16:54:23 +0100 with message-id <1547049263.1865336.1629951736.08362...@webmail.messagingengine.com> and subject line Re: Bug#918817: lintian: Returns with exit code of 0 (zero) on failed tests has caused the Debian Bug report #918817, regarding lintian: Returns

Bug#900997: print-manager: probability of package in buster?

2019-01-09 Thread Lisandro Damián Nicanor Pérez Meyer
Please go ahead and try El mié., 9 ene. 2019 11:57, Steven De Herdt escribió: > Dear maintainers > > If a patch providing Antonio's proposed stop-gap message is provided, is > it still possible for print-manager to get into buster? In that case, I > may possibly try to hack something like that.

Bug#918742: Initialization loop/deadlock when used with jemalloc

2019-01-09 Thread Faidon Liambotis
On Wed, Jan 09, 2019 at 11:23:19AM +0100, Johannes Schauer wrote: > Maybe you can report this directly to upstream? I thought of that, but then I saw that upstream is Piotr, who is also listed as a Maintainer of this package. Is that not the case? > Until it is properly fixed upstream we can just

Processed: Re: Bug#914814: spades: FTBFS with jemalloc/experimental

2019-01-09 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 914814 serious Bug #914814 [src:spades] spades: FTBFS with jemalloc/experimental Severity set to 'serious' from 'normal' > retitle 914814 spades: FTBFS with jemalloc 5 Bug #914814 [src:spades] spades: FTBFS with jemalloc/experimental Chan

Bug#918764: udev: "udevadm control --reload-rules" kills all processes except init

2019-01-09 Thread Michael Biebl
Control: tags -1 moreinfo unreproducible Am 09.01.19 um 11:16 schrieb Axel Beckert: > Hi, > > Axel Beckert wrote: >> I have no idea why this is happening, but several packages use "udevadm >> control --reload-rules" in their postinst (e.g. fuse) and if that's run, >> all process except init are i

Processed: Re: Bug#918764: udev: "udevadm control --reload-rules" kills all processes except init

2019-01-09 Thread Debian Bug Tracking System
Processing control commands: > tags -1 moreinfo unreproducible Bug #918764 [udev] udev: "udevadm control --reload-rules" kills all processes except init Added tag(s) moreinfo and unreproducible. -- 918764: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918764 Debian Bug Tracking System Conta

Bug#917635: marked as done (elkcode FTBFS, undefined reference to xc_f90_mgga_x_tb09_set_par_)

2019-01-09 Thread Debian Bug Tracking System
Your message dated Wed, 9 Jan 2019 17:08:43 +0100 with message-id <20190109160843.gr19...@nighthawk.caipicrew.dd-dns.de> and subject line Re: [Debichem-devel] Bug#917635: elkcode FTBFS, undefined reference to xc_f90_mgga_x_tb09_set_par_ has caused the Debian Bug report #917635, regarding elkcode F

Processed: Reopen

2019-01-09 Thread Debian Bug Tracking System
Processing control commands: > reopen -1 Bug #907624 {Done: Andreas Tille } [src:ffindex] ffindex: ffindex_modify segfaults during autopkgtest 'reopen' may be inappropriate when a bug has been closed with a version; all fixed versions will be cleared, and you may need to re-add them. Bug reopened

Bug#907624: Reopen

2019-01-09 Thread Andreas Tille
Control: reopen -1 Control: forwarded -1 https://github.com/soedinglab/ffindex_soedinglab/issues/7 Since we really want this code base I need to re-open the bug which is not solved. In a gdb session I've found the actual code line which causes the SIGSEGV: ffindex_build -s ./test.data ./te

Bug#915345: Remove roar support for now? (Fixes FTBFS)

2019-01-09 Thread Patrick Matthäi
Am 09.01.2019 um 16:03 schrieb Helge Kreutzmann: > Hello Ryan, > cmus is marked for autoremoval, the freeze is approaching (where no > removed packages are allowed to reenter testing) and I see no activity > from the cmus side. > > Also at least the mpd developers are not very confident in the cod

Bug#918764: udev: "udevadm control --reload-rules" kills all processes except init

2019-01-09 Thread Axel Beckert
Hi Michael, thanks for having looked into it. Michael Biebl wrote: > I can't reproduce this problem. Ok, good to know that it doesn't seem to affect more or less standard installations. So I wonder what part of my setup causes this: * 2x LVM on LUKS on MD RAID1 (2 spinning HDDs and 2 SSDs) * a

Bug#917708: Bug #917708 in gnome-settings-daemon marked as pending

2019-01-09 Thread Jeremy Bicha
Control: tag -1 pending Hello, Bug #917708 in gnome-settings-daemon reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/gnome-team/gnome-settings-daemon/commit/63bf

Processed: Bug #917708 in gnome-settings-daemon marked as pending

2019-01-09 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #917708 [src:gnome-settings-daemon] gnome-settings-daemon: FTBFS: dh_auto_test: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 MESON_TESTTHREADS=2 ninja test returned exit code 1 Ignoring request to alter tags of bug #917708 to the same tags previousl

Processed: Bug #917733 in ocaml-atd marked as pending

2019-01-09 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #917733 [src:ocaml-atd] ocaml-atd: FTBFS: dh_install: missing files, aborting Added tag(s) pending. -- 917733: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917733 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#917733: Bug #917733 in ocaml-atd marked as pending

2019-01-09 Thread Stéphane Glondu
Control: tag -1 pending Hello, Bug #917733 in ocaml-atd reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/ocaml-team/ocaml-atd/commit/f38a83d20ca261ce537978f1b983

Bug#917303: Request for help with MariaDB 10.3 / libdbd-mysql-perl packaging

2019-01-09 Thread gregor herrmann
On Tue, 08 Jan 2019 21:40:54 +0100, Otto Kekäläinen wrote: > For the records of this bug report and people following it, there are a lot > of discussions going on in both > https://github.com/perl5-dbi/DBD-mysql/issues/275 and > https://github.com/MariaDB/mariadb-connector-c/pull/95 The changes f

Bug#918782: marked as done (libvideo-info-perl: non-free package uploaded source-only)

2019-01-09 Thread Debian Bug Tracking System
Your message dated Wed, 09 Jan 2019 16:47:53 + with message-id and subject line Bug#918782: fixed in libvideo-info-perl 0.993-4 has caused the Debian Bug report #918782, regarding libvideo-info-perl: non-free package uploaded source-only to be marked as done. This means that you claim that th

Bug#918832: ifupdown2 fails to configure networking when /var/tmp is not present

2019-01-09 Thread Maximilian Wilhelm
Package: ifupdown2 Version: 1.2.2-1 Severity: critical Tags: patch Justification: breaks the whole system Hi Julien, (for others who might also stumble accros this problem I open a bug here besides the PR on github) we noticed that ifupdown2 fails to start and therefore fails to configure any i

Bug#917303: marked as done (libdbd-mysql-perl: FTBFS (test failures) against mariadb 10.3)

2019-01-09 Thread Debian Bug Tracking System
Your message dated Wed, 09 Jan 2019 17:07:00 + with message-id and subject line Bug#917303: fixed in libdbd-mysql-perl 4.050-1 has caused the Debian Bug report #917303, regarding libdbd-mysql-perl: FTBFS (test failures) against mariadb 10.3 to be marked as done. This means that you claim that

Bug#917733: marked as done (ocaml-atd: FTBFS: dh_install: missing files, aborting)

2019-01-09 Thread Debian Bug Tracking System
Your message dated Wed, 09 Jan 2019 17:08:26 + with message-id and subject line Bug#917733: fixed in ocaml-atd 2.0.0-3 has caused the Debian Bug report #917733, regarding ocaml-atd: FTBFS: dh_install: missing files, aborting to be marked as done. This means that you claim that the problem has

Bug#917708: marked as done (gnome-settings-daemon: FTBFS: dh_auto_test: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 MESON_TESTTHREADS=2 ninja test returned exit code 1)

2019-01-09 Thread Debian Bug Tracking System
Your message dated Wed, 09 Jan 2019 17:06:08 + with message-id and subject line Bug#917708: fixed in gnome-settings-daemon 3.30.2-1 has caused the Debian Bug report #917708, regarding gnome-settings-daemon: FTBFS: dh_auto_test: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 MESON_TESTTHREADS=2 nin

Bug#918833: node-browserify-lite: autopkgtest regression

2019-01-09 Thread Graham Inggs
Source: node-browserify-lite Version: 0.5.0-2 Severity: serious X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: regression Hi Maintainer Since the upload of 0.5.0-2, node-browserify-lite has been failing its own autopkgtests [1], where it succeeded in the past,

Bug#918764: udev: "udevadm control --reload-rules" kills all processes except init

2019-01-09 Thread Michael Biebl
Am 09.01.19 um 07:32 schrieb Axel Beckert: > Package: udev > Version: 240-2 Is this specific to version 240-2? Could you try downgrading udev to either 239-15 or 240-1 and report back with the results. Thanks, Michael -- Why is it that all of the instruments seeking intelligent life in the univ

Processed: fixed 917635 in 5.2.14-1

2019-01-09 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > fixed 917635 5.2.14-1 Bug #917635 {Done: Michael Banck } [elkcode] elkcode FTBFS, undefined reference to xc_f90_mgga_x_tb09_set_par_ There is no source info for the package 'elkcode' at version '5.2.14-1' with architecture '' Unable to make a so

Processed: bug 918673 is forwarded to https://github.com/sisyphus/math-mpfr/issues/2

2019-01-09 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forwarded 918673 https://github.com/sisyphus/math-mpfr/issues/2 Bug #918673 [src:libmath-mpfr-perl] libmath-mpfr-perl FTBFS on ppc*: subnormal_doubles.t fails Set Bug forwarded-to-address to 'https://github.com/sisyphus/math-mpfr/issues/2'. > th

Bug#857970: marked as done (mldemos FTBFS on armel/armhf: error: 'glColor3f' was not declared in this scope)

2019-01-09 Thread Debian Bug Tracking System
Your message dated Wed, 9 Jan 2019 20:13:33 +0200 with message-id <20190109181332.GI13260@localhost> and subject line Fixed in 0.5.1+git.1.ee5d11f-4 has caused the Debian Bug report #857970, regarding mldemos FTBFS on armel/armhf: error: 'glColor3f' was not declared in this scope to be marked as d

Bug#916858: marked as done (supercollider-emacs: fails to install with xemacs21)

2019-01-09 Thread Debian Bug Tracking System
Your message dated Wed, 09 Jan 2019 18:51:41 + with message-id and subject line Bug#916858: fixed in supercollider 1:3.10.0+repack-0.1 has caused the Debian Bug report #916858, regarding supercollider-emacs: fails to install with xemacs21 to be marked as done. This means that you claim that t

Bug#914640: marked as done (supercollider FTBFS on amd64/i386 with boost 1.67)

2019-01-09 Thread Debian Bug Tracking System
Your message dated Wed, 09 Jan 2019 18:51:41 + with message-id and subject line Bug#914640: fixed in supercollider 1:3.10.0+repack-0.1 has caused the Debian Bug report #914640, regarding supercollider FTBFS on amd64/i386 with boost 1.67 to be marked as done. This means that you claim that the

Processed: Re: ppp FTBFS with glibc 2.28

2019-01-09 Thread Debian Bug Tracking System
Processing control commands: > tags -1 patch Bug #916163 [src:ppp] ppp FTBFS with glibc 2.28 Added tag(s) patch. -- 916163: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916163 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#916163: ppp FTBFS with glibc 2.28

2019-01-09 Thread Luca Boccassi
Control: tags -1 patch On Mon, 10 Dec 2018 21:16:50 +0200 Adrian Bunk wrote: > Source: ppp > Version: 2.4.7-2+4 > Severity: serious > Tags: ftbfs >  > https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/pp p.html >  > ... > pppcrypt.c: In function 'DesSetkey': > pppcrypt.c:122:2: w

Bug#918053: marked as done (elk-lapw is missing dependency on openmpi-bin)

2019-01-09 Thread Debian Bug Tracking System
Your message dated Wed, 09 Jan 2019 19:06:13 + with message-id and subject line Bug#918053: fixed in elkcode 5.4.24-1 has caused the Debian Bug report #918053, regarding elk-lapw is missing dependency on openmpi-bin to be marked as done. This means that you claim that the problem has been dea

Bug#917633: marked as done (udisk2 post-installation fails in chrooted environments)

2019-01-09 Thread Debian Bug Tracking System
Your message dated Wed, 09 Jan 2019 19:10:19 + with message-id and subject line Bug#917633: fixed in systemd 240-3 has caused the Debian Bug report #917633, regarding udisk2 post-installation fails in chrooted environments to be marked as done. This means that you claim that the problem has b

Bug#918054: marked as done (elkcode: frequent test hangs)

2019-01-09 Thread Debian Bug Tracking System
Your message dated Wed, 9 Jan 2019 19:40:35 +0100 with message-id <20190109184034.gt19...@nighthawk.caipicrew.dd-dns.de> and subject line Re: [Debichem-devel] Bug#918054: elkcode: frequent test hangs has caused the Debian Bug report #918054, regarding elkcode: frequent test hangs to be marked as do

Processed: systemd: CVE-2018-16864

2019-01-09 Thread Debian Bug Tracking System
Processing control commands: > found -1 232-25+deb9u6 Bug #918841 [src:systemd] systemd: CVE-2018-16864 Marked as found in versions systemd/232-25+deb9u6. > found -1 240-2 Bug #918841 [src:systemd] systemd: CVE-2018-16864 Marked as found in versions systemd/240-2. -- 918841: https://bugs.debian.

Bug#918841: systemd: CVE-2018-16864

2019-01-09 Thread Salvatore Bonaccorso
Source: systemd Version: 204-1 Severity: grave Tags: security upstream Justification: user security hole Control: found -1 232-25+deb9u6 Control: found -1 240-2 Hi, The following vulnerability was published for systemd. CVE-2018-16864[0]: memory corruption If you fix the vulnerability please al

  1   2   >