Bug#859143: kup: please update to v0.3.6 due changes on k.o

On Fri, 31 Mar 2017 09:18:06 +0200 Sebastian Andrzej Siewior wrote: > On 2017-03-30 22:45:57 [+0100], Ben Hutchings wrote: > > Upgrading severity as it would be pointless to release with this > > version. >  > Sure. And probably something for current stable, I don't know. Should we > ask on

Processed: found 859143 in 0.3.2-1

Processing commands for cont...@bugs.debian.org: > found 859143 0.3.2-1 Bug #859143 {Done: Ben Hutchings } [kup] kup: please update to v0.3.6 due changes on k.o There is no source info for the package 'kup' at version '0.3.2-1' with architecture '' Unable to make a source

Bug#859143: marked as done (kup: please update to v0.3.6 due changes on k.o)

Your message dated Sun, 09 Apr 2017 03:03:55 + with message-id and subject line Bug#859143: fixed in kup 0.3.6-1 has caused the Debian Bug report #859143, regarding kup: please update to v0.3.6 due changes on k.o to be marked as done. This means that you

Bug#859143: marked as done (kup: please update to v0.3.6 due changes on k.o)

Your message dated Sun, 09 Apr 2017 03:03:48 + with message-id and subject line Bug#859143: fixed in kup 0.3.4-3 has caused the Debian Bug report #859143, regarding kup: please update to v0.3.6 due changes on k.o to be marked as done. This means that you

Bug#740893: libjs-jquery-hotkeys: Incompatible ABI change

On 06-Apr-2017, Philipp Hahn wrote: > today I spent some time on investigating this issue Thank you! > > introduced an incompatible ABI change how events are registered: So the

Processed: severity normal

Processing commands for cont...@bugs.debian.org: > severity 859902 normal Bug #859902 [gnome-shell-extension-refreshwifi] No longer necessary, should not be released with stretch Severity set to 'normal' from 'serious' > -- Stopping processing here. Please contact me if you need assistance. --

Bug#859885: No longer necessary, should not be released with stretch

control: clone -1 -2 reassign: -2 ftp.debian.org retitle: -2 RM: gnome-shell-extension-refreshwifi -- ROM; obsolete Am 08.04.2017 um 18:25 schrieb Jonathan Carter: > +1, package should be removed > > Last when I checked that extension, stretch hat a slightly older version > of Gnome that didn't

Bug#855094: marked as done (initramfs-tools-core: Error on upgrade if cryptsetup is installed, but a current busybox isn't)

Your message dated Sun, 09 Apr 2017 00:04:16 + with message-id and subject line Bug#855094: fixed in initramfs-tools 0.128 has caused the Debian Bug report #855094, regarding initramfs-tools-core: Error on upgrade if cryptsetup is installed, but a current

Bug#859692: marked as done (initramfs-tools: should depend on busybox)

Your message dated Sun, 09 Apr 2017 00:04:16 + with message-id and subject line Bug#855094: fixed in initramfs-tools 0.128 has caused the Debian Bug report #855094, regarding initramfs-tools: should depend on busybox to be marked as done. This means that

Bug#858556: marked as done (squid 3.5.23-2: upgrade from jesse squid3 fails)

Your message dated Sun, 09 Apr 2017 00:07:23 + with message-id and subject line Bug#858556: fixed in squid3 3.5.23-3 has caused the Debian Bug report #858556, regarding squid 3.5.23-2: upgrade from jesse squid3 fails to be marked as done. This means that

Processed: Re: Bug#859885: No longer necessary, should not be released with stretch

Processing control commands: > clone -1 -2 Bug #859885 [gnome-shell-extension-refreshwifi] No longer necessary, should not be released with stretch Bug 859885 cloned as bug 859902 -- 859885: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859885 Debian Bug Tracking System Contact

Processed: apt: fails to install parl-desktop-world with --install-recommends

Processing control commands: > affects -1 + parl-desktop-world parl-desktop-eu Bug #859900 [apt] apt: fails to install parl-desktop-world with --install-recommends Added indication that 859900 affects parl-desktop-world and parl-desktop-eu -- 859900:

Bug#859900: apt: fails to install parl-desktop-world with --install-recommends

Package: apt Version: 1.4 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Control: affects -1 + parl-desktop-world parl-desktop-eu Hi, during a test with piuparts I noticed that parl-desktop-world could not be tested with --install-recommends enabled. This can be easily

Bug#788585: marked as done (dsh: overwrites host list with a symlink)

Your message dated Sat, 08 Apr 2017 22:49:35 + with message-id and subject line Bug#788585: fixed in dsh 0.25.10-1.3 has caused the Debian Bug report #788585, regarding dsh: overwrites host list with a symlink to be marked as done. This means that you

Bug#788585: dsh: overwrites host list with a symlink

Control: tags -1 patch pending Hi, On Thu, Apr 06, 2017 at 10:58:58PM +0200, Ivo De Decker wrote: > On Sun, Nov 22, 2015 at 04:32:34PM +0100, Andreas Bombe wrote: > > The symlink is not marked as a conffile because debhelper (specifically > > dh_installdeb) does not mark symlinks to be installed

Processed: Re: Bug#788585: dsh: overwrites host list with a symlink

Processing control commands: > tags -1 patch pending Bug #788585 [dsh] dsh: overwrites host list with a symlink Added tag(s) patch and pending. -- 788585: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=788585 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Processed: change severity, and add tags

Processing commands for cont...@bugs.debian.org: > severity 853207 normal Bug #853207 [bluez] bluez: bluetooth.service doesn't start with systemd Severity set to 'normal' from 'grave' > tags 853207 unreproducible Bug #853207 [bluez] bluez: bluetooth.service doesn't start with systemd Added tag(s)

Processed: reopen

Processing commands for cont...@bugs.debian.org: > reopen 853207 Bug #853207 {Done: Nobuhiro Iwamatsu } [bluez] bluez: bluetooth.service doesn't start with systemd Bug reopened Ignoring request to alter fixed versions of bug #853207 to the same values previously set > End

Bug#859894: not compatible with latest OMEMO standard and clients

Package: gajim-omemo Version: 1.0.0-1 Severity: grave Set to grave, because "makes the package in question unusable by most ... users". As outcome of a security audit of the OMEMO protocol (XMPP e2e encryption method), it has been changed: The auth tag is no longer appended to the payload, but

Bug#858375: marked as done (libmongo-client-doc: uninstallable after binNMU)

Your message dated Sat, 08 Apr 2017 21:20:21 + with message-id and subject line Bug#858375: fixed in libmongo-client 0.1.8-2.1 has caused the Debian Bug report #858375, regarding libmongo-client-doc: uninstallable after binNMU to be marked as done. This

Bug#853207: marked as done (bluez: bluetooth.service doesn't start with systemd)

Your message dated Sun, 9 Apr 2017 06:02:50 +0900 with message-id and subject line Re: bluez: bluetooth.service doesn't start with systemd has caused the Debian Bug report #853207, regarding bluez: bluetooth.service doesn't

Processed: Re: Bug#859587: fixed in x2goserver 4.0.1.20-3

Processing control commands: > found -1 4.0.1.20-3 Bug #859587 {Done: Mike Gabriel } [x2goserver-fmbindings] x2goserver-fmbindings: fails to install: x2goserver-fmbindings.postinst: update-mime-database: not found Marked as found in versions x2goserver/4.0.1.20-3; no

Bug#859587: fixed in x2goserver 4.0.1.20-3

Control: found -1 4.0.1.20-3 On Fri, 07 Apr 2017 15:10:02 + Mike Gabriel wrote: >* debian/control: > + Add to D (x2goserver-fmbindings): shared_mime-info. (Closes: #859587). Wrong solution. Now the package fails to purge if shared-mime-info is no longer

Bug#858375: libmongo-client-doc: uninstallable after binNMU

Control: tags -1 patch pending Hi, On Tue, Mar 21, 2017 at 06:44:57PM +0100, Andreas Beckmann wrote: > during a test with piuparts I noticed your package is no longer > installable in sid: > > The following packages have unmet dependencies: > libmongo-client-doc : Depends: libmongo-client0 (=

Processed: Re: libmongo-client-doc: uninstallable after binNMU

Processing control commands: > tags -1 patch pending Bug #858375 [libmongo-client-doc] libmongo-client-doc: uninstallable after binNMU Added tag(s) patch and pending. -- 858375: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858375 Debian Bug Tracking System Contact ow...@bugs.debian.org

Bug#859885: No longer necessary, should not be released with stretch

Am 8. April 2017 18:25:06 MESZ schrieb Jonathan Carter : >+1, package should be removed > Should I reassign this bug to ftp.debian.org so the package is removed completely?

Bug#855279: marked as done (nvidia-graphics-drivers-legacy-304xx: CVE-2017-0309, CVE-2017-0310, CVE-2017-0311, CVE-2017-0321, CVE-2017-0318)

Your message dated Sat, 08 Apr 2017 15:47:09 + with message-id and subject line Bug#855279: fixed in nvidia-graphics-drivers-legacy-304xx 304.135-1 has caused the Debian Bug report #855279, regarding nvidia-graphics-drivers-legacy-304xx: CVE-2017-0309,

Bug#855277: marked as done (nvidia-graphics-drivers: CVE-2017-0309, CVE-2017-0310, CVE-2017-0311, CVE-2017-0321, CVE-2017-0318)

Your message dated Sat, 08 Apr 2017 15:47:08 + with message-id and subject line Bug#855277: fixed in nvidia-graphics-drivers 340.102-1 has caused the Debian Bug report #855277, regarding nvidia-graphics-drivers: CVE-2017-0309, CVE-2017-0310, CVE-2017-0311,

Bug#859885: No longer necessary, should not be released with stretch

Am 08.04.2017 um 17:10 schrieb Michael Biebl: > Package: gnome-shell-extension-refreshwifi > Version: 6.0-1 > Severity: serious > > Hi, > > this extensions was originally developed to work around a bug in > gnome-shell: > https://bugzilla.gnome.org/show_bug.cgi?id=767918 > > This has been fixed

Bug#859885: No longer necessary, should not be released with stretch

Package: gnome-shell-extension-refreshwifi Version: 6.0-1 Severity: serious Hi, this extensions was originally developed to work around a bug in gnome-shell: https://bugzilla.gnome.org/show_bug.cgi?id=767918 This has been fixed in the mean time in gnome-shell 3.22.2 and that fix is available in

Bug#859463: ruby-unf-ext FTBFS on ppc64el: unf/table.hh:13539:25: error: narrowing conversion of '-52' from 'int' to 'char' inside { } [-Wnarrowing]

Antonio Terceiro: > On Tue, Apr 04, 2017 at 02:26:00PM +, Niels Thykier wrote: >>[...] > > Nope. That was actually done after the current upstream release that we > have in Debian, actually tyring to _fix_ the issue. The actual fix comes > a little later in >

Bug#854554: marked as done (dpkg: trigger problem with cracklib-runtime while upgrading libcrypt-cracklib-perl from jessie to stretch)

Your message dated Sat, 08 Apr 2017 11:49:02 + with message-id and subject line Bug#859307: fixed in cracklib2 2.9.2-4 has caused the Debian Bug report #859307, regarding dpkg: trigger problem with cracklib-runtime while upgrading libcrypt-cracklib-perl

Bug#859307: marked as done (cracklib-runtime: Please migrate to a -noawait trigger)

Your message dated Sat, 08 Apr 2017 11:49:02 + with message-id and subject line Bug#859307: fixed in cracklib2 2.9.2-4 has caused the Debian Bug report #859307, regarding cracklib-runtime: Please migrate to a -noawait trigger to be marked as done. This

Processed: Re: Bug#859808: composite: Composite not ready for being qualified package of Debian yet.

Processing control commands: > severity -1 important Bug #859808 [composite] composite: Composite not ready for being qualified package of Debian yet. Severity set to 'important' from 'grave' -- 859808: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859808 Debian Bug Tracking System Contact

Bug#859808: composite: Composite not ready for being qualified package of Debian yet.

Control: severity -1 important [^ Prevent autoremoval while this is disputed] [+CC Gabriel who may be interested] Hi, On 08/04/17 11:49, MAROQQO digital media wrote: > To be honest I really wonder about what qualifies a package to be added > to the repositories of Debian, since I used to tend

Bug#859808: composite: Composite not ready for being qualified package of Debian yet.

Quoting MAROQQO digital media (2017-04-08 12:49:00) > Since I have tested the package I can say that this a 100% copy of an > old Hydrogen version without progression. Quite an interesting claim. > To be honest I really wonder about what qualifies a package to be > added to the repositories

Bug#859808: composite: Composite not ready for being qualified package of Debian yet.

Hi, thanks for your thoughts on this, Jaromir but: On 04/08/2017 08:52 AM, Jaromír Mikeš wrote: composite package builds fine and seems to have it's own users ... by popcon https://qa.debian.org/popcon.php?package=composite To simply say "well, it has its own users" by showing install graphs

Bug#859865: marked as done ([node-test] Package does not package test directory => FTBFS other package)

Your message dated Sat, 08 Apr 2017 09:33:52 + with message-id and subject line Bug#859865: fixed in node-test 0.6.0-3 has caused the Debian Bug report #859865, regarding [node-test] Package does not package test directory => FTBFS other package to be

Processed: reassign 854554 to cracklib-runtime, forcibly merging 859307 854554, severity of 854554 is grave

Processing commands for cont...@bugs.debian.org: > reassign 854554 cracklib-runtime Bug #854554 [cracklib-runtime] dpkg: trigger problem with cracklib-runtime while upgrading libcrypt-cracklib-perl from jessie to stretch Ignoring request to reassign bug #854554 to the same package > forcemerge

Bug#809625: marked as done (empire-hub: maintainer address bounces)

Your message dated Sat, 08 Apr 2017 09:18:52 + with message-id and subject line Bug#809625: fixed in empire-hub 1.0.2.2 has caused the Debian Bug report #809625, regarding empire-hub: maintainer address bounces to be marked as done. This means that you

Bug#859865: [node-test] Package does not package test directory => FTBFS other package

Package: node-test Version: 0.6.0-2 Severity: serious owner: ! will do signature.asc Description: This is a digitally signed message part.

Processed (with 1 error): Re: Bug#854554: dpkg: trigger problem with cracklib-runtime while upgrading libcrypt-cracklib-perl from jessie to stretch

Processing control commands: > reassign -1 cracklib-runtime Bug #854554 [libcrypt-cracklib-perl] dpkg: trigger problem with cracklib-runtime while upgrading libcrypt-cracklib-perl from jessie to stretch Bug reassigned from package 'libcrypt-cracklib-perl' to 'cracklib-runtime'. No longer marked

Bug#854554: dpkg: trigger problem with cracklib-runtime while upgrading libcrypt-cracklib-perl from jessie to stretch

Control: reassign -1 cracklib-runtime Control: forcemerge -1 cracklib2 Control: severity 854554 grave David Kalnischkies: > Control: reassign -1 libcrypt-cracklib-perl 1.7-2 > # beware, this is an RC bug! > > [CC'ed cracklib2 & perl maintainers as it seems to be some "funny" > interaction

Bug#854554: dpkg: trigger problem with cracklib-runtime while upgrading libcrypt-cracklib-perl from jessie to stretch

Control: reassign -1 libcrypt-cracklib-perl 1.7-2 # beware, this is an RC bug! [CC'ed cracklib2 & perl maintainers as it seems to be some "funny" interaction between packages in their responsibility space.] On Sat, Apr 08, 2017 at 04:50:15AM +0200, Guillem Jover wrote: > [ Please see the bug

Bug#859864: r-bioc-genomeinfodb: Reorganization of ftp://ftp.ncbi.nlm.nih.gov/genomes/all

Source: r-bioc-genomeinfodb Version: 1.10.2-1 Severity: grave Affects: r-bioc-annotationhub Tags: upstream fixed-upstream Hi Maintainer Autopkgtests of r-bioc-annotationhub started failing on 2017-0126 [1] with the following error: Error in checkIdentical(setNames(rep(c(FALSE, TRUE), c(4, 1)),

Processed: Re: Bug#854554: dpkg: trigger problem with cracklib-runtime while upgrading libcrypt-cracklib-perl from jessie to stretch

Processing control commands: > reassign -1 libcrypt-cracklib-perl 1.7-2 Bug #854554 [apt] dpkg: trigger problem with cracklib-runtime while upgrading libcrypt-cracklib-perl from jessie to stretch Bug reassigned from package 'apt' to 'libcrypt-cracklib-perl'. Ignoring request to alter found

Bug#859808: composite: Composite not ready for being qualified package of Debian yet.

2017-04-07 17:00 GMT+02:00 Digidog : > Package: composite > Version: 0.006.2+dfsg0-7 > Severity: grave > Justification: renders package unusable > > Dear Maintainer, > > Request > --- > + Please remove the Composite package from the Debian repositories in > near future.