NEW changes in stable-new
Processing changes file: ruby-standalone_0.5+deb8u1_arm64.changes ACCEPT Processing changes file: ruby-standalone_0.5+deb8u1_armhf.changes ACCEPT Processing changes file: ruby-standalone_0.5+deb8u1_i386.changes ACCEPT Processing changes file: ruby-standalone_0.5+deb8u1_mips.changes ACCEPT Processing changes file: ruby-standalone_0.5+deb8u1_mipsel.changes ACCEPT Processing changes file: ruby-standalone_0.5+deb8u1_powerpc.changes ACCEPT Processing changes file: ruby-standalone_0.5+deb8u1_ppc64el.changes ACCEPT Processing changes file: ruby-standalone_0.5+deb8u1_s390x.changes ACCEPT
NEW changes in stable-new
Processing changes file: ruby-standalone_0.5+deb8u1_armel.changes ACCEPT
Processed: Re: Bug#815060: Encouraging removal of nvidia kernel modules from Debian non-free archive.
Processing control commands: > reassign -1 ftp.debian.org Bug #815060 [ftp.debian.org, src:nvidia-graphics-modules] RM: nvidia-graphics-modules -- RoQA; Violates kernel license Bug reassigned from package 'ftp.debian.org, src:nvidia-graphics-modules' to 'ftp.debian.org'. Ignoring request to alter found versions of bug #815060 to the same values previously set Ignoring request to alter fixed versions of bug #815060 to the same values previously set > clone -1 -2 -3 Bug #815060 [ftp.debian.org] RM: nvidia-graphics-modules -- RoQA; Violates kernel license Bug 815060 cloned as bugs 815525-815526 > reassign -2 release.debian.org Bug #815525 [ftp.debian.org] RM: nvidia-graphics-modules -- RoQA; Violates kernel license Bug reassigned from package 'ftp.debian.org' to 'release.debian.org'. Ignoring request to alter found versions of bug #815525 to the same values previously set Ignoring request to alter fixed versions of bug #815525 to the same values previously set > tag -2 jessie Bug #815525 [release.debian.org] RM: nvidia-graphics-modules -- RoQA; Violates kernel license Added tag(s) jessie. > retitle -2 RM: nvidia-graphics-modules/340.96+3.16.0+1 Bug #815525 [release.debian.org] RM: nvidia-graphics-modules -- RoQA; Violates kernel license Changed Bug title to 'RM: nvidia-graphics-modules/340.96+3.16.0+1' from 'RM: nvidia-graphics-modules -- RoQA; Violates kernel license' > reassign -3 release.debian.org Bug #815526 [ftp.debian.org] RM: nvidia-graphics-modules -- RoQA; Violates kernel license Bug reassigned from package 'ftp.debian.org' to 'release.debian.org'. Ignoring request to alter found versions of bug #815526 to the same values previously set Ignoring request to alter fixed versions of bug #815526 to the same values previously set > tag -3 wheezy Bug #815526 [release.debian.org] RM: nvidia-graphics-modules -- RoQA; Violates kernel license Added tag(s) wheezy. > retitle -3 RM: nvidia-graphics-modules/304.131+3.2.0+1 Bug #815526 [release.debian.org] RM: nvidia-graphics-modules -- RoQA; Violates kernel license Changed Bug title to 'RM: nvidia-graphics-modules/304.131+3.2.0+1' from 'RM: nvidia-graphics-modules -- RoQA; Violates kernel license' -- 815060: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815060 815525: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815525 815526: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815526 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#815520: jessie-pu: package fglrx-driver/1:15.9-4~deb8u2 xvba-video_0.8.0-9+deb8u1
Package: release.debian.org Severity: normal Tags: jessie User: release.debian@packages.debian.org Usertags: pu Hi, the last fglrx-driver update in jessie brought a small regression: updates with xvba-va-driver installed fail due to a file overwrite conflict (#813427). xvba-va-driver is currently uninstallable in jessie. xvba-va-driver is no longer needed as a separate package, instead libfglrx-amdxvba1 brings equivalent files. We need to update both packages to fix this issue. The updated src:fglrx-driver package adds proper Breaks+Replaces against the xvba-va-driver package currently in jessie. The updated src:xvba-video package turns xvba-va-driver into an installable empty dummy package. That's less intrusive than removing it while ensuring that a clean upgrade path exists. Let's do the discussion with this one bug here and clone it once it reached confirmed state. Andreas Index: debian/changelog === --- debian/changelog (revision 1603) +++ debian/changelog (revision 1604) @@ -1,3 +1,11 @@ +fglrx-driver (1:15.9-4~deb8u2) jessie; urgency=medium + + * libfglrx-amdxvba1: Add Breaks+Replaces: xvba-va-driver (<< 0.8.0-9+deb) +since we now ship fglrx_drv_video.so and xvba_drv_video.so. +(Closes: #813427) + + -- Andreas Beckmann Mon, 22 Feb 2016 01:31:06 +0100 + fglrx-driver (1:15.9-4~deb8u1) jessie; urgency=medium * Rebuild for jessie. Index: debian/control === --- debian/control (revision 1603) +++ debian/control (revision 1604) @@ -122,8 +122,11 @@ xvba-va-driver, Conflicts: libxvbaw1, +Breaks: + xvba-va-driver (<< 0.8.0-9+deb), Replaces: libxvbaw1, + xvba-va-driver (<< 0.8.0-9+deb), Description: AMD XvBA (X-Video Bitstream Acceleration) backend for VA API${fglrx:VariantDescSuffix} X-Video Bitstream Acceleration (XvBA), designed by AMD for its (ATI) Radeon GPU and Fusion APU, is an arbitrary extension of the X video extension (Xv) for the Index: debian/rules === --- debian/rules (revision 1604) +++ debian/rules (revision 1605) @@ -13,6 +13,8 @@ override_dh_auto_install: dh_auto_install rm -f debian/xvba-va-driver/$(libdir)/dri/*.la + $(RM) debian/xvba-va-driver/$(libdir)/dri/fglrx_drv_video.so + $(RM) debian/xvba-va-driver/$(libdir)/dri/xvba_drv_video.so override_dh_installchangelogs: dh_installchangelogs NEWS Index: debian/control === --- debian/control (revision 1604) +++ debian/control (revision 1605) @@ -23,9 +23,11 @@ Pre-Depends: dpkg (>= 1.15.6~), Depends: - libfglrx-amdxvba1 | libfglrx-legacy-amdxvba1, + libfglrx-amdxvba1 (>= 1:15.9), ${shlibs:Depends}, ${misc:Depends} +Breaks: + libfglrx-legacy-amdxvba1, Provides: va-driver Description: XvBA-based backend for VA API (AMD fglrx implementation) Index: debian/changelog === --- debian/changelog (revision 1604) +++ debian/changelog (revision 1605) @@ -1,3 +1,14 @@ +xvba-video (0.8.0-9+deb8u1) jessie; urgency=medium + + * xvba-va-driver as a separate package has been obsoleted by +fglrx-driver 1:15.9, turn it into an empty metapackage. + * Stop shipping fglrx_drv_video.so and xvba_drv_video.so. (Closes: #813427) + * Bump Depends on libfglrx-amdxvba1 to (>= 1:15.9) which provides them. + * This breaks compatibility with libfglrx-legacy-amdxvba1 (package exists +only in wheezy-backports). + + -- Andreas Beckmann Mon, 22 Feb 2016 01:05:30 +0100 + xvba-video (0.8.0-9) unstable; urgency=medium [ Patrick Matthäi ]
Bug#815517: jessie-pu: package unbound/1.4.22-3+deb8u1
Package: release.debian.org Severity: normal Tags: jessie User: release.debian@packages.debian.org Usertags: pu Hi, The unbound package in jessie has outdated root DNS server address hints for h.root-servers.net, see #815370. I'd like to upload a new version to jessie with the following changes. Thanks! diff --git a/debian/changelog b/debian/changelog index af91f28..2c6d115 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,10 @@ +unbound (1.4.22-3+deb8u1) jessie; urgency=medium + + * iterator/iter_hints.c: Update hints for H.ROOT-SERVERS.NET +(Closes: #815370) + + -- Robert Edmonds Sun, 21 Feb 2016 18:36:43 -0500 + unbound (1.4.22-3) unstable; urgency=medium * Fix CVE-2014-8602: denial of service by making resolver chase endless diff --git a/iterator/iter_hints.c b/iterator/iter_hints.c index 7fa07a7..8e51424 100644 --- a/iterator/iter_hints.c +++ b/iterator/iter_hints.c @@ -135,7 +135,7 @@ compile_time_root_prime(int do_ip4, int do_ip6) if(!ah(dp, "E.ROOT-SERVERS.NET.", "192.203.230.10")) goto failed; if(!ah(dp, "F.ROOT-SERVERS.NET.", "192.5.5.241")) goto failed; if(!ah(dp, "G.ROOT-SERVERS.NET.", "192.112.36.4")) goto failed; - if(!ah(dp, "H.ROOT-SERVERS.NET.", "128.63.2.53")) goto failed; + if(!ah(dp, "H.ROOT-SERVERS.NET.", "198.97.190.53")) goto failed; if(!ah(dp, "I.ROOT-SERVERS.NET.", "192.36.148.17")) goto failed; if(!ah(dp, "J.ROOT-SERVERS.NET.", "192.58.128.30")) goto failed; if(!ah(dp, "K.ROOT-SERVERS.NET.", "193.0.14.129")) goto failed; @@ -146,7 +146,7 @@ compile_time_root_prime(int do_ip4, int do_ip6) if(!ah(dp, "A.ROOT-SERVERS.NET.", "2001:503:ba3e::2:30")) goto failed; if(!ah(dp, "D.ROOT-SERVERS.NET.", "2001:500:2d::d")) goto failed; if(!ah(dp, "F.ROOT-SERVERS.NET.", "2001:500:2f::f")) goto failed; - if(!ah(dp, "H.ROOT-SERVERS.NET.", "2001:500:1::803f:235")) goto failed; + if(!ah(dp, "H.ROOT-SERVERS.NET.", "2001:500:1::53")) goto failed; if(!ah(dp, "I.ROOT-SERVERS.NET.", "2001:7fe::53")) goto failed; if(!ah(dp, "J.ROOT-SERVERS.NET.", "2001:503:c27::2:30")) goto failed; if(!ah(dp, "K.ROOT-SERVERS.NET.", "2001:7fd::1")) goto failed; -- Robert Edmonds edmo...@debian.org
NEW changes in stable-new
Processing changes file: sane-backends_1.0.24-8+deb8u1_mipsel.changes ACCEPT
NEW changes in stable-new
Processing changes file: vsftpd_3.0.2-17+deb8u1_mipsel.changes ACCEPT
NEW changes in stable-new
Processing changes file: ruby-standalone_0.5+deb8u1_amd64.changes ACCEPT
Bug#815356: jessie-pu: package ruby-standalone/0.5+deb8u1
Control: tags -1 + pending On Sun, 2016-02-21 at 13:49 -0300, Antonio Terceiro wrote: > On Sun, Feb 21, 2016 at 10:36:34AM +, Adam D. Barratt wrote: > > Control: tags -1 + confirmed > > > > On Sat, 2016-02-20 at 22:05 -0200, Antonio Terceiro wrote: > > > I would like to upload a stable update for ruby-standalone, that makes > > > it work correctly with bundler, which is a very important use case. > > > > Please go ahead. > > just uploaded; thanks. Flagged for acceptance. Regards, Adam
Processed: Re: Bug#815356: jessie-pu: package ruby-standalone/0.5+deb8u1
Processing control commands: > tags -1 + pending Bug #815356 [release.debian.org] jessie-pu: package ruby-standalone/0.5+deb8u1 Added tag(s) pending. -- 815356: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815356 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#815469: jessie-pu: package osmo/0.2.12-1+deb8u1
Am 21.02.2016 um 20:22 schrieb Adam D. Barratt: > Control: tags -1 + confirmed > > On Sun, 2016-02-21 at 19:46 +0100, Markus Koschany wrote: >> I would like to update Osmo in Jessie because the internal data backup >> function on i386 is broken and it produces only a 50 bytes empty file. >> This will lead to invalid data when user's try to restore the backup. >> >> This is Debian bug https://bugs.debian.org/813414 > > Please go ahead. > > Regards, > > Adam Uploaded. Thanks. signature.asc Description: OpenPGP digital signature
Processed: Re: Bug#815469: jessie-pu: package osmo/0.2.12-1+deb8u1
Processing control commands: > tags -1 + confirmed Bug #815469 [release.debian.org] jessie-pu: package osmo/0.2.12-1+deb8u1 Added tag(s) confirmed. -- 815469: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815469 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#815469: jessie-pu: package osmo/0.2.12-1+deb8u1
Control: tags -1 + confirmed On Sun, 2016-02-21 at 19:46 +0100, Markus Koschany wrote: > I would like to update Osmo in Jessie because the internal data backup > function on i386 is broken and it produces only a 50 bytes empty file. > This will lead to invalid data when user's try to restore the backup. > > This is Debian bug https://bugs.debian.org/813414 Please go ahead. Regards, Adam
Re: 8.4 and 7.10 planning
On 02/21/2016 08:13 AM, Julien Cristau wrote: > On Sun, Feb 21, 2016 at 12:24:35 +, Adam D. Barratt wrote: > >> Hi, >> >> We're due both Jessie and Wheezy point releases, and are proposing doing >> both on the same weekend again, as we did for 8.2 and 7.9, as the CD >> team seem happy to try it again. >> >> Some suggested dates: >> >> March 12th / 13th >> March 19th / 20th >> March 26th / 27th - Easter, holiday weekend in at least the UK >> April 2nd / 3rd March 12/13 is no good (Steve) and March 26/27 is Easter holiday as well in the US. Although the publicity team is flexible on the date ranges, April 2/3 seem to be the better of the date ranges as the delay would give Ben time to push the kernel updates. Best regards, Donald Norwood signature.asc Description: OpenPGP digital signature
Bug#815469: jessie-pu: package osmo/0.2.12-1+deb8u1
Package: release.debian.org Severity: normal Tags: jessie User: release.debian@packages.debian.org Usertags: pu Hello, I would like to update Osmo in Jessie because the internal data backup function on i386 is broken and it produces only a 50 bytes empty file. This will lead to invalid data when user's try to restore the backup. This is Debian bug https://bugs.debian.org/813414 The debdiff is attached. Regards, Markus diff -Nru osmo-0.2.12/debian/changelog osmo-0.2.12/debian/changelog --- osmo-0.2.12/debian/changelog 2014-10-15 14:20:21.0 +0200 +++ osmo-0.2.12/debian/changelog 2016-02-21 19:36:29.0 +0100 @@ -1,3 +1,12 @@ +osmo (0.2.12-1+deb8u1) jessie; urgency=medium + + * Add libarchive-i386.patch. +Fix corrupt data backup on i386. +Thanks to Christian Buchmüller for the report and Maxim Gordienko for the +patch. (Closes: #813414) + + -- Markus Koschany Sun, 21 Feb 2016 19:35:43 +0100 + osmo (0.2.12-1) unstable; urgency=medium * Imported Upstream version 0.2.12. diff -Nru osmo-0.2.12/debian/patches/libarchive-i386.patch osmo-0.2.12/debian/patches/libarchive-i386.patch --- osmo-0.2.12/debian/patches/libarchive-i386.patch 1970-01-01 01:00:00.0 +0100 +++ osmo-0.2.12/debian/patches/libarchive-i386.patch 2016-02-21 19:36:29.0 +0100 @@ -0,0 +1,25 @@ +From: Maxim Gordienko +Date: Thu, 4 Feb 2016 22:38:37 +0100 +Subject: libarchive i386 + +On i386 platforms libarchive does not write the file content if +the archived file content is set only with archive_entry_copy_stat(). + +Forwarded: http://sourceforge.net/p/osmo-pim/code/1051/ +Debian-Bug: https://bugs.debian.org/813414 +--- + src/backup.c | 1 + + 1 file changed, 1 insertion(+) + +diff --git a/src/backup.c b/src/backup.c +index 3ece5f5..ee99236 100644 +--- a/src/backup.c b/src/backup.c +@@ -68,6 +68,7 @@ tar_archive (const gchar *outname, GUI *appGUI) + stat (filename, &st); + entry = archive_entry_new (); + archive_entry_copy_stat (entry, &st); ++ archive_entry_set_size(entry, st.st_size); + archive_entry_set_pathname (entry, filename); + archive_write_header (archive, entry); + fd = open (filename, O_RDONLY); diff -Nru osmo-0.2.12/debian/patches/series osmo-0.2.12/debian/patches/series --- osmo-0.2.12/debian/patches/series 1970-01-01 01:00:00.0 +0100 +++ osmo-0.2.12/debian/patches/series 2016-02-21 19:36:29.0 +0100 @@ -0,0 +1 @@ +libarchive-i386.patch
Bug#812887: transition: iptables
Hello! On Sun, Feb 07, 2016 at 04:23:25PM +, Jonathan Wiltshire wrote: > On Wed, Jan 27, 2016 at 04:58:41PM +0100, Arturo Borrero Gonzalez wrote: > > iptables 1.6.0 has been released and we plan to include it in debian. > > > > The libxtables binary package name has been changed from libxtables10 to > > libxtables11. However, this change seems to affect very few packages (if > > any). > > > > Since an upload to experimental was done, a transition was set up [0]. > > Following the instructions [1] for transition, I've build-tested all > > reverse build-deps of iptables and they seem to build simply fine: > > > > * xtables-addons: no problems > > * connman: no problems > > * west-chamer: no problems > > > > So, I ask for a transition slot to upload iptables 1.6.0 to unstable. > > The transition completed. Please also binNMU iproute2 to build against the new libxtables and pick up a new recommends, or the 'ipt' module will be/stay broken. Regards, Andreas Henriksson
NEW changes in stable-new
Processing changes file: sane-backends_1.0.24-8+deb8u1_armel.changes ACCEPT Processing changes file: sane-backends_1.0.24-8+deb8u1_armhf.changes ACCEPT Processing changes file: sane-backends_1.0.24-8+deb8u1_mips.changes ACCEPT Processing changes file: sane-backends_1.0.24-8+deb8u1_ppc64el.changes ACCEPT Processing changes file: vsftpd_3.0.2-17+deb8u1_armel.changes ACCEPT Processing changes file: vsftpd_3.0.2-17+deb8u1_armhf.changes ACCEPT Processing changes file: vsftpd_3.0.2-17+deb8u1_mips.changes ACCEPT Processing changes file: vsftpd_3.0.2-17+deb8u1_ppc64el.changes ACCEPT
NEW changes in stable-new
Processing changes file: sane-backends_1.0.24-8+deb8u1_arm64.changes ACCEPT Processing changes file: sane-backends_1.0.24-8+deb8u1_i386.changes ACCEPT Processing changes file: sane-backends_1.0.24-8+deb8u1_powerpc.changes ACCEPT Processing changes file: sane-backends_1.0.24-8+deb8u1_s390x.changes ACCEPT Processing changes file: vsftpd_3.0.2-17+deb8u1_arm64.changes ACCEPT Processing changes file: vsftpd_3.0.2-17+deb8u1_i386.changes ACCEPT Processing changes file: vsftpd_3.0.2-17+deb8u1_powerpc.changes ACCEPT Processing changes file: vsftpd_3.0.2-17+deb8u1_s390x.changes ACCEPT
Bug#815356: jessie-pu: package ruby-standalone/0.5+deb8u1
On Sun, Feb 21, 2016 at 10:36:34AM +, Adam D. Barratt wrote: > Control: tags -1 + confirmed > > On Sat, 2016-02-20 at 22:05 -0200, Antonio Terceiro wrote: > > I would like to upload a stable update for ruby-standalone, that makes > > it work correctly with bundler, which is a very important use case. > > Please go ahead. just uploaded; thanks. signature.asc Description: PGP signature
Bug#815036: transition: msgpack-c
On Wed, Feb 17, 2016 at 11:46:53PM -0500, James McCoy wrote: > FTBFS: > > * webdis: > + #811343 filed with patch > * tmate: > + New upstream version is needed > + Will file a bug for this Filed #815381. > * kumofs: > + configure script expects the C++ library (libmsgpack) and therefore > fails > + Trivial patch to remove that expectation leads to a compile failure > due to mixing code with C and C++ linkage > + No upstream activity in 5+ years > + Debian maintainer MIA Given the above and a popcon of 5, should an RM bug be filed? > * libdata-messagepack-stream-perl: > + This likely needs a newer version of libdata-messagepack-perl, which > hasn't been uploaded yet Confirmed that a newer libdata-messagepack-perl is needed. There is a patch in the Debian repo which helps, but a more complete patch is proposed upstream[0]. [0]: https://github.com/msgpack/msgpack-perl/pull/22 > + Needs to be adapted to new msgpack-c API. I have some patches I can > send in that regard. I've provided patches for this upstream[1] and opened bug #815433 to track this. [1]: https://github.com/typester/Data-MessagePack-Stream/issues/6 Cheers, -- James GPG Key: 4096R/331BA3DB 2011-12-05 James McCoy
Bug#814716: marked as done (jessie-pu: package apt-offline/1.5.1)
Your message dated Sun, 21 Feb 2016 19:14:46 +0530 with message-id <1456062286.4681.3.ca...@debian.org> and subject line Re: Bug#814716: jessie-pu: package apt-offline/1.5.1 has caused the Debian Bug report #814716, regarding jessie-pu: package apt-offline/1.5.1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 814716: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814716 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: release.debian.org Severity: normal Tags: jessie User: release.debian@packages.debian.org Usertags: pu There are 2 bugs reported to me privately about functionality broken in apt-offline, in the version shipped in Jessie. Bug 1: apt-offline only look into /etc/apt/trusted.gpg for key verification. This results in most apt data not to be installed because the debian (archive) keyring resides in /usr/share/keyrings Bug 2: Because of the last minute changes in 1.5.x release, the file detection plugin had some output changes that led to .gpg data represented differently by different plugins. Both bugs were known and are already fixed in the current 1.7.x release in Unstable/Testing. This request is to backport those changes for Stable. The patch has been verified by the user who reported the bug to me. I've also verified the patch in a Jessie container, and it seems to not break anything. root@learner:~# apt-offline -v 1.5.2 root@learner:~# apt-offline install /var/tmp/lxc/jessie.zip gpgv: Signature made Sat Jan 23 18:49:39 2016 IST using RSA key ID 46925553 gpgv: Good signature from "Debian Archive Automatic Signing Key (7.0/wheezy) " gpgv: Signature made Sat Jan 23 18:49:39 2016 IST using RSA key ID 2B90D010 gpgv: Good signature from "Debian Archive Automatic Signing Key (8/jessie) " gpgv: Signature made Sat Jan 23 18:55:24 2016 IST using RSA key ID 518E17E1 gpgv: Good signature from "Jessie Stable Release Key " /var/lib/apt/lists/partial/httpredir.debian.org_debian_dists_jessie_Release synced. /var/lib/apt/lists/partial/httpredir.debian.org_debian_dists_jessie_Release.gpg synced. /var/lib/apt/lists/partial/httpredir.debian.org_debian_dists_jessie_main_binary-amd64_Packages.bz2 synced. /var/lib/apt/lists/partial/httpredir.debian.org_debian_dists_jessie_main_i18n_Translation-en.bz2 synced. Please give me an ACK on this email, and then I will go ahead and upload it for Stable (Jessie) inclusion. The debdiff is attached with this bug report. -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (101, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.3.5+ (SMP w/4 CPU cores; PREEMPT) Locale: LANG=en_IN.utf8, LC_CTYPE=en_IN.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) diff -Nru apt-offline-1.5.1/apt_offline_core/AptOfflineCoreLib.py apt-offline-1.5.2/apt_offline_core/AptOfflineCoreLib.py --- apt-offline-1.5.1/apt_offline_core/AptOfflineCoreLib.py 2015-11-18 19:37:20.0 +0530 +++ apt-offline-1.5.2/apt_offline_core/AptOfflineCoreLib.py 2016-02-14 20:53:21.0 +0530 @@ -93,7 +93,7 @@ app_name = "apt-offline" -version = "1.5" +version = "1.5.2" myCopyright = "(C) 2005 - 2014 Ritesh Raj Sarraf" terminal_license = "This program comes with ABSOLUTELY NO WARRANTY.\n\ This is free software, and you are welcome to redistribute it under\n\ @@ -915,15 +915,37 @@ class APTVerifySigs: def __init__(self, gpgv=None, keyring=None): +self.defaultPaths = ['/etc/apt/trusted.gpg.d/', '/usr/share/keyrings/'] + if gpgv is None: self.gpgv="/usr/bin/gpgv" else: self.gpgv=gpgv - + +self.opts = [] if keyring is None: -self.opts="--keyring /etc/apt/trusted.gpg --ignore-time-conflict" + +self.opts.append("--ignore-time-conflict ") + +#INFO: For backwards compatibility +if os.path.exists("/etc/apt/trusted.gpg"): +self.opts.extend("--keyring /etc/apt/trusted.gpg".split()) + +for eachPath in self.defaultPaths: +if os.path.exists(eachPath): +
Bug#796952: english language release notes pdf file is not english (https://www.debian.org/releases/stable/amd64/release-notes.en.pdf)
Hi Julien, > Thanks! I've applied your variant2 patch and installed fonts-sil-charis > on www-master. Ok, not optimal, but not too bad. Maybe we should discuss proper font selection before the next release. If there are any further problems, please don't hesitate to contact me! All the best Norbert PREINING, Norbert http://www.preining.info JAIST, Japan TeX Live & Debian Developer GPG: 0x860CDC13 fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13
Re: 8.4 and 7.10 planning
On Sun, Feb 21, 2016 at 12:24:35 +, Adam D. Barratt wrote: > Hi, > > We're due both Jessie and Wheezy point releases, and are proposing doing > both on the same weekend again, as we did for 8.2 and 7.9, as the CD > team seem happy to try it again. > > Some suggested dates: > > March 12th / 13th > March 19th / 20th > March 26th / 27th - Easter, holiday weekend in at least the UK > April 2nd / 3rd > Should all work for me. Cheers, Julien signature.asc Description: PGP signature
Re: 8.4 and 7.10 planning
On Sun, 2016-02-21 at 12:24 +, Adam D. Barratt wrote: > Hi, > > We're due both Jessie and Wheezy point releases, and are proposing doing > both on the same weekend again, as we did for 8.2 and 7.9, as the CD > team seem happy to try it again. > > Some suggested dates: > > March 12th / 13th > March 19th / 20th > March 26th / 27th - Easter, holiday weekend in at least the UK > April 2nd / 3rd I was planning stable updates for the kernel but haven't uploaded to either suite yet, so I would prefer one of the later dates. But of course this can slip to the next point release. Ben. -- Ben Hutchings Time is nature's way of making sure that everything doesn't happen at once. signature.asc Description: This is a digitally signed message part
NEW changes in stable-new
Processing changes file: sane-backends_1.0.24-8+deb8u1_amd64.changes ACCEPT Processing changes file: vsftpd_3.0.2-17+deb8u1_amd64.changes ACCEPT
Processed: Re: Bug#809319: jessie-pu: package sane-backends/1.0.24-8
Processing control commands: > tags -1 + pending Bug #809319 [release.debian.org] jessie-pu: package sane-backends/1.0.24-8 Bug #797769 [release.debian.org] jessie-pu: package sane-backends/1.0.24-8 Added tag(s) pending. Added tag(s) pending. -- 797769: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=797769 809319: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809319 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#809319: jessie-pu: package sane-backends/1.0.24-8
Control: tags -1 + pending On Sun, 2016-02-21 at 09:36 +0100, John Paul Adrian Glaubitz wrote: > On 02/21/2016 07:38 AM, Jörg Frings-Fürst wrote: > > I have no upload rights. So I ask my sponsor to upload it. But he > > has a lot of work in his job. > > > > It's fine if someone can upload it. The package is on mentors[1]. > > I'm taking care of it right now. No worries. Uploaded and flagged for acceptance. Regards, Adam
Processed: Re: Bug#785047: vsftpd/3.0.2-17+deb8u1
Processing control commands: > tags -1 + pending Bug #785047 [release.debian.org] jessie-pu: package vsftpd/3.0.2-17 Added tag(s) pending. -- 785047: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785047 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#785047: vsftpd/3.0.2-17+deb8u1
Control: tags -1 + pending On Sun, 2016-02-21 at 11:56 +0100, John Paul Adrian Glaubitz wrote: > Control: reopen -1 > > On 02/21/2016 11:08 AM, Jörg Frings-Fürst wrote: > >> @Joerg: Could you re-upload the package to mentors? > >> > > > > done.. [1] > > Reopening since I am preparing the upload now. Uploaded and flagged for acceptance. Regards, Adam
Re: 8.4 and 7.10 planning
On Sun, Feb 21, 2016 at 12:24:35PM +, Adam Barratt wrote: >Hi, > >We're due both Jessie and Wheezy point releases, and are proposing doing >both on the same weekend again, as we did for 8.2 and 7.9, as the CD >team seem happy to try it again. > >Some suggested dates: > > >March 12th / 13th not a chance for me, I'll be on a plane back from a conf in Thailand. >March 19th / 20th fine >March 26th / 27th (probably) fine >April 2nd / 3rd fine -- Steve McIntyre, Cambridge, UK.st...@einval.com "Since phone messaging became popular, the young generation has lost the ability to read or write anything that is longer than one hundred and sixty characters." -- Ignatios Souvatzis
NEW changes in oldstable-new
Processing changes file: cpio_2.11+dfsg-0.1+deb7u2_amd64.changes ACCEPT Processing changes file: cpio_2.11+dfsg-0.1+deb7u2_armel.changes ACCEPT Processing changes file: cpio_2.11+dfsg-0.1+deb7u2_armhf.changes ACCEPT Processing changes file: cpio_2.11+dfsg-0.1+deb7u2_i386.changes ACCEPT Processing changes file: cpio_2.11+dfsg-0.1+deb7u2_ia64.changes ACCEPT Processing changes file: cpio_2.11+dfsg-0.1+deb7u2_kfreebsd-amd64.changes ACCEPT Processing changes file: cpio_2.11+dfsg-0.1+deb7u2_kfreebsd-i386.changes ACCEPT Processing changes file: cpio_2.11+dfsg-0.1+deb7u2_mips.changes ACCEPT Processing changes file: cpio_2.11+dfsg-0.1+deb7u2_mipsel.changes ACCEPT Processing changes file: cpio_2.11+dfsg-0.1+deb7u2_powerpc.changes ACCEPT Processing changes file: cpio_2.11+dfsg-0.1+deb7u2_s390.changes ACCEPT Processing changes file: cpio_2.11+dfsg-0.1+deb7u2_s390x.changes ACCEPT Processing changes file: cpio_2.11+dfsg-0.1+deb7u2_sparc.changes ACCEPT Processing changes file: dbconfig-common_1.8.47+nmu1+deb7u1_amd64.changes ACCEPT Processing changes file: didiwiki_0.5-11+deb7u1_amd64.changes ACCEPT Processing changes file: didiwiki_0.5-11+deb7u1_armel.changes ACCEPT Processing changes file: didiwiki_0.5-11+deb7u1_armhf.changes ACCEPT Processing changes file: didiwiki_0.5-11+deb7u1_i386.changes ACCEPT Processing changes file: didiwiki_0.5-11+deb7u1_ia64.changes ACCEPT Processing changes file: didiwiki_0.5-11+deb7u1_kfreebsd-amd64.changes ACCEPT Processing changes file: didiwiki_0.5-11+deb7u1_kfreebsd-i386.changes ACCEPT Processing changes file: didiwiki_0.5-11+deb7u1_mips.changes ACCEPT Processing changes file: didiwiki_0.5-11+deb7u1_mipsel.changes ACCEPT Processing changes file: didiwiki_0.5-11+deb7u1_powerpc.changes ACCEPT Processing changes file: didiwiki_0.5-11+deb7u1_s390.changes ACCEPT Processing changes file: didiwiki_0.5-11+deb7u1_s390x.changes ACCEPT Processing changes file: didiwiki_0.5-11+deb7u1_sparc.changes ACCEPT Processing changes file: xdelta3_3.0.0.dfsg-1+deb7u1_amd64.changes ACCEPT Processing changes file: xdelta3_3.0.0.dfsg-1+deb7u1_armel.changes ACCEPT Processing changes file: xdelta3_3.0.0.dfsg-1+deb7u1_armhf.changes ACCEPT Processing changes file: xdelta3_3.0.0.dfsg-1+deb7u1_i386.changes ACCEPT Processing changes file: xdelta3_3.0.0.dfsg-1+deb7u1_ia64.changes ACCEPT Processing changes file: xdelta3_3.0.0.dfsg-1+deb7u1_kfreebsd-amd64.changes ACCEPT Processing changes file: xdelta3_3.0.0.dfsg-1+deb7u1_kfreebsd-i386.changes ACCEPT Processing changes file: xdelta3_3.0.0.dfsg-1+deb7u1_mips.changes ACCEPT Processing changes file: xdelta3_3.0.0.dfsg-1+deb7u1_mipsel.changes ACCEPT Processing changes file: xdelta3_3.0.0.dfsg-1+deb7u1_powerpc.changes ACCEPT Processing changes file: xdelta3_3.0.0.dfsg-1+deb7u1_s390.changes ACCEPT Processing changes file: xdelta3_3.0.0.dfsg-1+deb7u1_s390x.changes ACCEPT Processing changes file: xdelta3_3.0.0.dfsg-1+deb7u1_sparc.changes ACCEPT
8.4 and 7.10 planning
Hi, We're due both Jessie and Wheezy point releases, and are proposing doing both on the same weekend again, as we did for 8.2 and 7.9, as the CD team seem happy to try it again. Some suggested dates: March 12th / 13th March 19th / 20th March 26th / 27th - Easter, holiday weekend in at least the UK April 2nd / 3rd Regards, Adam
Processed: Re: Bug#784915: jessie-pu: package rsnapshot/1.3.1-4
Processing control commands: > tags -1 + confirmed Bug #784915 [release.debian.org] jessie-pu: package rsnapshot/1.3.1-4 Added tag(s) confirmed. -- 784915: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784915 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#814269: jessie-pu: package nettle/2.7.1-5
Control: tags -1 + confirmed On Tue, 2016-02-09 at 20:59 +0100, Magnus Holmgren wrote: > OK to upload fix for https://bugs.debian.org/813679 (CVE-2015-8803 > CVE-2015-8804 CVE-2015-8805), as suggested by (a member of) the > security team? (Security-related bugs but unlikely to be exploitable.) Assuming that the resulting package has been tested on Jessie, please go ahead. Regards, Adam
Bug#784915: jessie-pu: package rsnapshot/1.3.1-4
Control: tags -1 + confirmed On Mon, 2015-10-26 at 00:26 +0100, Guillaume Delacour wrote: > Hi, > > Le 21/08/2015 16:34, Adam D. Barratt a écrit : > > > > > The package in unstable and testing appears to have been fixed now. > > > >> In either case, when it comes to an update in stable we'll need a source > >> debdiff of the proposed updated package, built and tested in a Jessie > >> environment, rather than pointers to online patches. > > > > This is still true, however. > > Please find attached a debdiff that fix the problem in Jessie. I've > tested the fix by defining ssh_args in /etc/rsnapshot.conf and it's > works well after the fix (before applying the update rsnapshot fails > with "rsync: Failed to exec /usr/bin/ssh -p222: No such file or directory"). Apologies for the delay in getting back to you. Please go ahead. Regards, Adam
Processed: Re: Bug#814269: jessie-pu: package nettle/2.7.1-5
Processing control commands: > tags -1 + confirmed Bug #814269 [release.debian.org] jessie-pu: package nettle/2.7.1-5 Added tag(s) confirmed. -- 814269: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814269 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#813916: transition: gdal
On 19-02-16 14:08, Sebastiaan Couwenberg wrote: > On 12-02-16 19:05, Emilio Pozuelo Monfort wrote: >> On 12/02/16 18:52, Sebastiaan Couwenberg wrote: >>> On 12-02-16 18:28, Emilio Pozuelo Monfort wrote: On 06/02/16 17:43, Bas Couwenberg wrote: > Package: release.debian.org > For the Debian GIS team I'd like to transition to the recently released > GDAL 1.11.4. Only the packages using C++ symbols need to be rebuilt. > > GDAL 2.0.2 was released along with 1.11.4, but we still don't have > support for GDAL 2.0 in all reverse dependencies. Since the transition > to GDAL 1.11.3, support for GDAL 2.0 was added to all reverse > depedencies except Fiona [0]. Upstream has recently included changes for > GDAL 2.0, but these differ from the initial GDAL 2.0 changes available > as a patch in #802808. The improved GDAL 2.0 changes are entangled with > other changes for the upcoming Fiona 1.7 release, which I've not been > able to successfully backport. This will not be a blocker for the GDAL > 2.0 transition, as discussed with the maintainer on the debian-gis list > [1]. > > Because the transition for GDAL 1.11.4 is ready now, I'd like to do that > first before preparing the transition to GDAL 2.0. All reverse > dependencies rebuilt successfully with GDAL 1.11.4, the summary of > rebuilds is included below. > This would get entangled with the openmpi transition, so it will have to wait. After openmpi, I'm thinking about doing libpng, but we'll see. >>> >>> Waiting for openmpi is no problem, but if the libpng transition is going >>> to happen first, I think it's better to use that time the prepare the >>> transition to GDAL 2.0 instead of 1.11.4. Last week the last blocker was >>> resolved [0], so we're also pretty much ready to transition to GDAL 2.0. >>> The 2.0 packages will have to pass the NEW queue again, because of the >>> delay that will cause I've opted to transition to 1.11.4 which is ready now. >>> >>> If you can confirm that the libpng transition is going to happen first, >>> I'll upload the packages for GDAL 2.0 to experimental, and we can switch >>> to that in unstable after the libpng transition and the new gdal has >>> passed NEW. >> >> Sure, let's do that. > > The GDAL 2.0.2 packages are available in experimental and ready for > transition. > > libgdal-grass (2.0.2-1) not available in experimental yet, liblas and > grass need to be rebuilt with GDAL 2.0 before it can be built too, > because the SOVERSION is included in the binary package it builds the > package will have to pass the NEW queue after upload first. To get it > passed the NEW queue, I'll rebuild liblas & grass with gdal > (2.0.2-1-1~exp2) from experimental and upload all three to experimental too. libgdal-grass (2.0.2-1~exp1) and its dependencies are in experimental now too. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
NEW changes in stable-new
Processing changes file: amavisd-new_2.10.1-2~deb8u1_i386.changes ACCEPT
Processed: tagging 728906
Processing commands for cont...@bugs.debian.org: > tags 728906 - moreinfo Bug #728906 [release.debian.org] pu: package netbeans/7.0.1+dfsg1-6 Removed tag(s) moreinfo. > thanks Stopping processing here. Please contact me if you need assistance. -- 728906: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=728906 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#813071: jessie-pu: package amavisd-new/1:2.10.1-2
Control: tags -1 + pending On Sun, 2016-02-21 at 13:24 +1100, Brian May wrote: > "Adam D. Barratt" writes: > > > You've dropped the epoch in the new stanza. With that fixed, please feel > > free to upload. > > Have had confirmation that the change solves the problem. Fixed the > version and uploaded. Thanks; flagged for acceptance. Regards, Adam
Processed: Re: Bug#813071: jessie-pu: package amavisd-new/1:2.10.1-2
Processing control commands: > tags -1 + pending Bug #813071 [release.debian.org] jessie-pu: package amavisd-new/1:2.10.1-2 Added tag(s) pending. -- 813071: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813071 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#782596: marked as done (RFC: possible wheezy-pu: package debhelper to address #708218 for wheezy?)
Your message dated Sun, 21 Feb 2016 11:11:23 + with message-id <2016022123.gv6...@betterave.cristau.org> and subject line Re: Bug#782596: RFC: possible wheezy-pu: package debhelper to address #708218 for wheezy? has caused the Debian Bug report #782596, regarding RFC: possible wheezy-pu: package debhelper to address #708218 for wheezy? to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 782596: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=782596 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: release.debian.org Severity: normal Hi Stable release managers, This is not a wheezy-pu request per se. The recent libxrender update through security.d.o was initially just a rebuild of libxrender against a fixed version of libx11. This caused #782505 ("libxrender1: dist-upgrade breaks on multiarch due to conflict on changelog.Debian.gz"). The fix for debhelper in #708218 didn't make it into wheezy so binNMUs in wheezy for multiarch enabled packages will have the problem. Would it make sense to have an update of debhelper in wheezy fixing this issue as well? Regards, Salvatore --- End Message --- --- Begin Message --- On Wed, Apr 29, 2015 at 22:21:13 +0100, Adam D. Barratt wrote: > Control: tags -1 + moreinfo > > On Wed, 2015-04-15 at 23:09 +0200, Niels Thykier wrote: > > On 2015-04-14 17:47, Salvatore Bonaccorso wrote: > [...] > > > The fix for debhelper in #708218 didn't make it into wheezy so binNMUs > > > in wheezy for multiarch enabled packages will have the problem. > > > > > > Would it make sense to have an update of debhelper in wheezy fixing > > > this issue as well? > [...] > > >From a debhelper PoV, it looks reasonable at first glance. > > > > It looks like we would need to backport the 4 commits listed in the > > attached "...-commits.diff" file. The combined result (excluding > > changelog entries) is in the "...-dh_installchangelogs.diff" and had no > > merge conflicts (only one chunk required fuzziness to be applied). > > The diff looks okay to me, but... > > > Except a missing changelog entry, is the expected debdiff for such an > > upload. Disclaimer, not tested (not even build tested). > > ... that needs addressing before we can consider an upload. :) > No followup since last April. Closing now. Cheers, Julien signature.asc Description: PGP signature --- End Message ---
Bug#770821: marked as done (wheezy-pu: package soprano/2.7.6+dfsg.1-2wheezy2)
Your message dated Sun, 21 Feb 2016 11:09:16 + with message-id <20160221110916.ga30...@betterave.cristau.org> and subject line Re: Bug#707301: wheezy-pu: make soprano co-installable with multiarch-enabled ODBC drivers has caused the Debian Bug report #770821, regarding wheezy-pu: package soprano/2.7.6+dfsg.1-2wheezy2 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 770821: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770821 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: release-notes Severity: important Hello, Working through release notes, everythign looks good until you get to apt-get dist-upgrade I have found a bug for http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=645726 which says it was fixed in the upstream version but this does not allow for dist-upgrade. This is a second computer that it had happend on in our company. apt-get dist-upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Failed The following packages have unmet dependencies: odbcinst1debian2 : Breaks: tdsodbc (< 0.82-8) but 0.82-7 is to be installed E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages. Solution: Current solution to this problem is to remove the package. What I have done is apt-get remove odbcinst1debian2 Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: libjaxp1.3-java libntfs10 libdb4.7-java fgfs-base libdb4.7-java-gcj libproj0 libogdi3.2 libcoin60 freetds-common ttf-lyx libxerces-c28 lm-sensors libopenthreads13 libhdf5-serial-1.8.4 libgeos-c1 proj-data fancontrol proj-bin libplib1 libgeos-3.2.0 libsysfs2 libpq5 libhdf4-0-alt libxcb-render-util0 libnetcdf6 libsmpeg0 Use 'apt-get autoremove' to remove them. The following extra packages will be installed: libgnutls26 libp11-kit0 libssl1.0.0 virtuoso-opensource-6.1-bin The following packages will be REMOVED: flightgear libgdal1-1.6.0 libopenscenegraph65 libvirtodbc0 odbcinst odbcinst1debian2 python-pyodbc simgear1.9.1 sun-java6-bin sun-java6-jre sun-java6-plugin tdsodbc unixodbc virtuoso-minimal The following NEW packages will be installed: libp11-kit0 libssl1.0.0 The following packages will be upgraded: libgnutls26 virtuoso-opensource-6.1-bin 2 upgraded, 2 newly installed, 14 to remove and 873 not upgraded. Need to get 6,017 kB of archives. After this operation, 265 MB disk space will be freed. Do you want to continue [Y/n]? y Then just to make sure..I did apt-get update apt-get upgrade At this point the apt-get dist-upgrade allowed me to upgrade my system. If you could mention that in the release notes. tdsodbc will need to be reinstalled after upgrade. Thank you, Lucas -- System Information: Debian Release: 6.0.7 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash --- End Message --- --- Begin Message --- On Mon, Nov 24, 2014 at 13:22:19 +0100, Holger Levsen wrote: > reassign 707301 soprano > found 707301 2.7.6+dfsg.1-2wheezy1 > retitle 707301 make soprano co-installable with multiarch-enabled ODBC drivers > clone 707301 -1 > reassign -1 release.debian.org > block -1 by 707301 > severity -1 normal > tags -1 + wheezy > User release.debian@packages.debian.org > usertag -1 + pu > retitle -1 wheezy-pu: package soprano/2.7.6+dfsg.1-2wheezy2 > # this upload still needs to happen and agreed on upon the soprano > # maintainers...! > thanks > > Hi, > > appearantly soprano is not co-installable with multiarch-enabled ODBC drivers > as explained and patched by Steve in > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707301#29 > > I'm not fully convinced this patch is appropriate in stable at this time (but > then I should also say that I'm mostly clueless about this issue too...), so > probably the -1 bug should be reassigned to release-notes or closed after > all... but that's easy enough to do, so that's why. > AFAICT there was no followup or diff sent to the release.d.o bug in the last year and a half; closing. Cheers, Julien signature.asc Description: PGP signature --- End Message ---
Bug#756986: marked as done (wheezy-pu: package debian-lan-config/0.13~bpo70+5)
Your message dated Sun, 21 Feb 2016 11:04:18 + with message-id <20160221110418.gt6...@betterave.cristau.org> and subject line Re: Bug#756986: wheezy-pu: package debian-lan-config/0.13~bpo70+5 has caused the Debian Bug report #756986, regarding wheezy-pu: package debian-lan-config/0.13~bpo70+5 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 756986: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756986 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: release.debian.org Severity: normal Tags: wheezy User: release.debian@packages.debian.org Usertags: pu Dear release managers! I would like to ask for the permission to upload and the inclusion of the latest debian-lan-config package in the upcoming wheezy point release. The debian-lan-config package is kind of special, as it contains no 'program' in itself, but instructions (in a FAI config space) on how to build a composed system within debian, cf. https://wiki.debian.org/DebianLAN>. The package did not make it for the wheezy freeze and I provided it via backports after the release. However, with further improvements, it got less and less justified to use backports, as the wheezy package is not a strict 'backport' of the version in jessie, which is of course targeted at jessie. Content and history of the package is available here: http://anonscm.debian.org/cgit/collab-maint/debian-lan.git/log/?h=wheezy> The package should not pose any risk to the distribution, as it needs to be 'activated' manually to do anything at all. To get an idea, cf. http://anonscm.debian.org/cgit/collab-maint/debian-lan.git/tree/debian/README.Debian?h=wheezy>. Best regards and thanks for your consideration, Andi -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.14-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash --- End Message --- --- Begin Message --- On Mon, Aug 4, 2014 at 10:19:00 +0200, Andreas B. Mundt wrote: > Package: release.debian.org > Severity: normal > Tags: wheezy > User: release.debian@packages.debian.org > Usertags: pu > > > Dear release managers! > > I would like to ask for the permission to upload and the inclusion of > the latest debian-lan-config package in the upcoming wheezy point > release. > We're not normally adding completely new packages post-release, and even less so now wheezy is almost EOL. Closing. Cheers, Julien signature.asc Description: PGP signature --- End Message ---
Bug#761662: marked as done (wheezy-pu: package dictionaries-common/1.12.11+deb7u1)
Your message dated Sun, 21 Feb 2016 11:05:30 + with message-id <20160221110530.gu6...@betterave.cristau.org> and subject line Re: Bug#761662: wheezy-pu: package dictionaries-common/1.12.11+deb7u1 has caused the Debian Bug report #761662, regarding wheezy-pu: package dictionaries-common/1.12.11+deb7u1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 761662: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761662 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: release.debian.org Severity: normal Tags: wheezy User: release.debian@packages.debian.org Usertags: pu Hi, For some time dictionaries-comon package has been complaining loudly with an installation error when a debconf database corruption affecting it is found, together with some relevant info to repair that. This was initially done in purpose to help debconf maintainer gather information about the problem. Also, some recovery process for simple corruptions was added. Usual reason for this was fixed in debconf some time ago. Recently, seems that some other yet unknown cause for big corruption sometimes appears, and I has also been pointed out that accidental removal of stuff under /var/cache/debconf has the same effect, triggering the above mentioned installation error (http://bugs.debian.org/751367). Some code has been added in sid to handle this better, using info provided by packages to get a list of possible values, and using a debconf question to warn sysadmin about the problem instead of a failure error message, together with some other improvements like using always no-await triggers. I have been sugested in http://bugs.debian.org/751367 to put some of this code in a wheezy point release, and I would like to know your opinion here, I am attaching a diff with the minimal changes I suggest to put in that point upload. It consists of two things, a) Select a temporary default from a list of known to be available values. This was formerly extracted from debconf, but it becomes unavailable if corruption is large. b) Use a debconf question to warn about the problem and give advice. Thanks very much for your time, -- Agustin diff -Nru dictionaries-common-1.12.11/debian/changelog dictionaries-common-1.12.11+deb7u1/debian/changelog --- dictionaries-common-1.12.11/debian/changelog 2013-01-22 14:51:12.0 +0100 +++ dictionaries-common-1.12.11+deb7u1/debian/changelog 2014-07-25 16:49:17.0 +0200 @@ -1,3 +1,13 @@ +dictionaries-common (1.12.11+deb7u1) unstable; urgency=low + + * Improve behavior on debconf database corruption (Closes: #751367): +- update-default.in: Use /var/lib/dictionaries-common info as last + resource to try getting a default in case of debconf database + corruption. This should work better around installation error. +- Use a debconf question to warn about debconf database corruption. + + -- Agustin Martin Domingo Fri, 25 Jul 2014 16:48:41 +0200 + dictionaries-common (1.12.11) unstable; urgency=low * debian/control: Add Breaks against ancient myspell-cs-cz, diff -Nru dictionaries-common-1.12.11/debian/dictionaries-common.templates dictionaries-common-1.12.11+deb7u1/debian/dictionaries-common.templates --- dictionaries-common-1.12.11/debian/dictionaries-common.templates 2011-04-27 17:54:16.0 +0200 +++ dictionaries-common-1.12.11+deb7u1/debian/dictionaries-common.templates 2014-07-25 13:04:48.0 +0200 @@ -1,3 +1,19 @@ +Template: dictionaries-common/debconf_database_corruption +Type: note +Description: Possible debconf database corruption + The setting for "${question}" is missing, but packages providing + candidates are installed. + . + This may be due to corruption in the debconf database. See + "/usr/share/doc/dictionaries-common/README.problems" on "Debconf + database corruption". + . + In this case, running "/usr/share/debconf/fix_db.pl" can help to put + the debconf database in a consistent state. + . + Some questions are likely to be asked after this message in order to + leave the dictionaries system in a (provisionally) working state. + Template: dictionaries-common/invalid_debconf_value Type: note _Description: An invalid debconf value [${value}] has been found @@ -108,4 +124,3 @@ will not set the default ispell dictionary. . Use instead 'select-default-ispell' or 'select-default-wordlist' scripts. - diff -Nru dictionaries-common-1.12.11/scripts/system/update-default.in dictionaries-common-1.12.11+deb7u1/scripts/system/update-default.in --- dictionaries-common-1.12.11/scripts/system/update-default.in 2011-06-01 19:
Bug#740435: marked as done (wheezy-pu: package arandr/0.1.7.1-1)
Your message dated Sun, 21 Feb 2016 11:01:16 + with message-id <20160221110116.gr6...@betterave.cristau.org> and subject line Re: Bug#740435: wheezy-pu: package arandr/0.1.7.1-1 has caused the Debian Bug report #740435, regarding wheezy-pu: package arandr/0.1.7.1-1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 740435: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=740435 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: release.debian.org Severity: normal Tags: wheezy User: release.debian@packages.debian.org Usertags: pu hello release team, i'd like to upload a new version of arandr to stable. arandr versions before 0.1.7.1, as described in bug #718366 (originally #507521), completely fail to work with some combinations of x servers (which are present in wheezy), graphics cards and output devices. the changes between 0.1.6-1 and 0.1.7.1-1 affect +94-24 lines of python code, that's practically the minimal patch -- i could squeeze out a line or two where just comments are modified, no more. the larger part of the delta between wheezy and jessie are updates to translation files (four new languages), and the resulting changes to changelog, news, readme and debian/copyright. add changing standards-version and adding a debian menu file, that's it. given the delta on the program itself is already as good as minimal, and given that 0.1.7.1-1 has been used in unstable for half a year without additional bugs, i'd like to ask the release team for its opinion on uploading an unmodified 0.1.7.1-1 (as in `dch -D stable -v 0.1.7.1-1+deb7u1 -m "Unmodified upload to stable"`). a debdiff from wheezy to jessie is attached. if you insist on a minimal diff, i can strip 0.1.7.1 down -- but it is my opinion that the chance of making a mistake in the course of that is much higher than the chance of introducing a bugs by uploading the current testing version. please let me know which course of action you prefer in this case chrysn [The following lists of changes regard files as different if they have different names, permissions or owners.] Files in second .deb but not in first - -rw-r--r-- root/root /usr/share/doc/arandr/TODO.gz -rw-r--r-- root/root /usr/share/locale/el/LC_MESSAGES/arandr.mo -rw-r--r-- root/root /usr/share/locale/hu/LC_MESSAGES/arandr.mo -rw-r--r-- root/root /usr/share/locale/ko_KR/LC_MESSAGES/arandr.mo -rw-r--r-- root/root /usr/share/locale/uk/LC_MESSAGES/arandr.mo -rw-r--r-- root/root /usr/share/menu/arandr -rw-r--r-- root/root /usr/share/pyshared/arandr-0.1.7.1.egg-info -rwxr-xr-x root/root DEBIAN/postrm lrwxrwxrwx root/root /usr/lib/python2.6/dist-packages/arandr-0.1.7.1.egg-info -> ../../../share/pyshared/arandr-0.1.7.1.egg-info lrwxrwxrwx root/root /usr/lib/python2.7/dist-packages/arandr-0.1.7.1.egg-info -> ../../../share/pyshared/arandr-0.1.7.1.egg-info Files in first .deb but not in second - -rw-r--r-- root/root /usr/share/doc/arandr/TODO -rw-r--r-- root/root /usr/share/pyshared/arandr-0.1.6.egg-info lrwxrwxrwx root/root /usr/lib/python2.6/dist-packages/arandr-0.1.6.egg-info -> ../../../share/pyshared/arandr-0.1.6.egg-info lrwxrwxrwx root/root /usr/lib/python2.7/dist-packages/arandr-0.1.6.egg-info -> ../../../share/pyshared/arandr-0.1.6.egg-info Control files: lines which differ (wdiff format) Depends: [-python2.7 | python2.6,-] python (>= 2.6.6-7~), python (<< 2.8), x11-xserver-utils | xrandr, python-gtk2 Installed-Size: [-480-] {+533+} Version: [-0.1.6-1-] {+0.1.7.1-1+} signature.asc Description: Digital signature --- End Message --- --- Begin Message --- On Fri, Aug 21, 2015 at 16:02:14 +0100, Adam D. Barratt wrote: > Control: tags -1 + confirmed > > On Mon, 2015-01-19 at 12:34 +0100, chrysn wrote: > > hello adam, > > > > thanks for your ping -- i've missed the original reply. > > > > >That sounds like it would probably be fine, but a defdiff of the > > >proposed package would be appreciated for confirmation. In the context > > >of package updates, when we refer to a debdiff we usually mean one of > > >the _source_ packages, not the resulting binar(y|ies), to indicate the > > >actual changes to the uploaded package which result from the rebuild. > > > > > >The version number would need to be 0.1.7.1-1~deb7u1; otherwise it would > > >be higher than the version in testing/unstable. > > > > i've attached a debdiff to that respect, and in case you prefer to work > > off a dsc, upl
Processed: Re: Bug#804209: wheezy-pu: package fuse-exfat/0.9.7-2+deb7u1
Processing control commands: > tags -1 + pending Bug #804209 [release.debian.org] wheezy-pu: package fuse-exfat/0.9.7-2+deb7u1 Added tag(s) pending. -- 804209: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=804209 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#750010: marked as done (pu: package mlmmj/1.2.18.1-1)
Your message dated Sun, 21 Feb 2016 11:01:58 + with message-id <20160221110158.gs6...@betterave.cristau.org> and subject line Re: Bug#750010: pu: package mlmmj/1.2.18.1-1 has caused the Debian Bug report #750010, regarding pu: package mlmmj/1.2.18.1-1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 750010: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=750010 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: pu Dear release team, Upstream for MLMMJ has released a bugfix version correcting a few bugs, one of which is the loss of some emails in some cases, which is IMO bad enough to deserve a correction in Debian Stable. The upstream ChangeLog file contains: 1.2.18.1 o Stop mlmmj-maintd deleting list posts while they are being sent o Fix +list from crashing Mlmmj o Fix bug that made double subscription possible I believe these are important bugfixes. I have attached the debdiff between 1.2.18.0-2 and 1.2.18.1-1 which I just uploaded to Sid. There's a bit of noise in this debdiff, like the Makefile.in, some doc updates, and such. These are only updates of the GNU tooling, and I don't believe there's much impact on MLMMJ itself. However, the interesting part is the last bits, with the below files updated: src/mlmmj-maintd.c src/send_list.c src/subscriberfuncs.c When filtering to only these .c files, the patch is only 138 lines long (so, much more easy to review). So, I would like to upgrade the current Wheezy version of MLMMJ to the upstream release 1.2.18.1. If that was not possible from the view of the release team, then I would like to add a patch to the current version including all the modifications on the .c files seen in the attached diff file. Please let me know the stable release team view on this, Cheers, Thomas Goirand (zigo) diff -Nru mlmmj-1.2.18.0/aclocal.m4 mlmmj-1.2.18.1/aclocal.m4 --- mlmmj-1.2.18.0/aclocal.m4 2012-05-29 13:47:25.0 + +++ mlmmj-1.2.18.1/aclocal.m4 2014-02-05 06:12:37.0 + @@ -1,8 +1,7 @@ -# generated automatically by aclocal 1.12 -*- Autoconf -*- +# generated automatically by aclocal 1.12.5 -*- Autoconf -*- + +# Copyright (C) 1996-2012 Free Software Foundation, Inc. -# Copyright (C) 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, -# 2005, 2006, 2007, 2008, 2009, 2010, 2011 Free Software Foundation, -# Inc. # This file is free software; the Free Software Foundation # gives unlimited permission to copy and/or distribute it, # with or without modifications, as long as this notice is preserved. @@ -26,8 +25,6 @@ # gives unlimited permission to copy and/or distribute it, # with or without modifications, as long as this notice is preserved. -# serial 8 - # AM_AUTOMAKE_VERSION(VERSION) # # Automake X.Y traces this macro to ensure aclocal.m4 has been @@ -37,7 +34,7 @@ [am__api_version='1.12' dnl Some users find AM_AUTOMAKE_VERSION and mistake it for a way to dnl require some minimum version. Point them to the right macro. -m4_if([$1], [1.12], [], +m4_if([$1], [1.12.5], [], [AC_FATAL([Do not call $0, use AM_INIT_AUTOMAKE([$1]).])])dnl ]) @@ -53,7 +50,7 @@ # Call AM_AUTOMAKE_VERSION and AM_AUTOMAKE_VERSION so they can be traced. # This function is AC_REQUIREd by AM_INIT_AUTOMAKE. AC_DEFUN([AM_SET_CURRENT_AUTOMAKE_VERSION], -[AM_AUTOMAKE_VERSION([1.12])dnl +[AM_AUTOMAKE_VERSION([1.12.5])dnl m4_ifndef([AC_AUTOCONF_VERSION], [m4_copy([m4_PACKAGE_VERSION], [AC_AUTOCONF_VERSION])])dnl _AM_AUTOCONF_VERSION(m4_defn([AC_AUTOCONF_VERSION]))]) @@ -66,8 +63,6 @@ # gives unlimited permission to copy and/or distribute it, # with or without modifications, as long as this notice is preserved. -# serial 2 - # For projects using AC_CONFIG_AUX_DIR([foo]), Autoconf sets # $ac_aux_dir to '$srcdir/foo'. In other projects, it is set to # '$srcdir', '$srcdir/..', or '$srcdir/../..'. @@ -121,8 +116,6 @@ # gives unlimited permission to copy and/or distribute it, # with or without modifications, as long as this notice is preserved. -# serial 10 - # AM_CONDITIONAL(NAME, SHELL-CONDITION) # - # Define a conditional. @@ -154,7 +147,6 @@ # gives unlimited permission to copy and/or distribute it, # with or without modifications, as long as this notice is preserved. -# serial 16 # There are a few dirty hacks below to avoid letting 'AC_PROG_CC' be # written in clear, in which case automake, when reading aclocal.m4, @@ -166,7 +158,7 @@
Bug#804209: wheezy-pu: package fuse-exfat/0.9.7-2+deb7u1
Control: tags -1 + pending On Thu, 2016-01-07 at 10:26 +0100, Sven Hoexter wrote: > On Fri, Jan 01, 2016 at 06:26:22PM +, Adam D. Barratt wrote: > > Hi Adam, > > > Please go ahead. > > Uploaded. This was accepted a while ago but I apparently forgot to tag it. Regards, Adam
NEW changes in stable-new
Processing changes file: pagekite_0.5.6d-3+deb8u1_amd64.changes ACCEPT Processing changes file: sitesummary_0.1.17+deb8u1_amd64.changes ACCEPT
Bug#731412: marked as done (pu: package am-utils/6.2+rc20110530-3.1~deb7u1)
Your message dated Sun, 21 Feb 2016 10:58:47 + with message-id <20160221105847.gp6...@betterave.cristau.org> and subject line Re: Bug#731412: pu: package am-utils/6.2+rc20110530-3.1~deb7u1 has caused the Debian Bug report #731412, regarding pu: package am-utils/6.2+rc20110530-3.1~deb7u1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 731412: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=731412 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: release.debian.org Severity: normal Tags: wheezy User: release.debian@packages.debian.org Usertags: pu Hi, according to #722145 crashes unless the kernel version has 2 dots. While this is not a problem with the kernel in wheezy, it will prevent using it with newer kernels (backports, custom, vanilla, ...) I'm not a user of am-utils and don't know how to test this change properly. Attached is a proposed debdiff that just rebuilds the fixed package from sid for wheezy (therefore including also a trivial change to the texinfo manual). Andreas diff -u am-utils-6.2+rc20110530/debian/changelog am-utils-6.2+rc20110530/debian/changelog --- am-utils-6.2+rc20110530/debian/changelog +++ am-utils-6.2+rc20110530/debian/changelog @@ -1,3 +1,18 @@ +am-utils (6.2+rc20110530-3.1~deb7u1) wheezy; urgency=low + + * Non-maintainer upload. + * Rebuild for wheezy. + + -- Andreas Beckmann Thu, 05 Dec 2013 10:00:57 +0100 + +am-utils (6.2+rc20110530-3.1) unstable; urgency=low + + * Non-maintainer upload. + * Fix @sp macro usage in the texinfo manual (Closes: #713285). + * Fix crashes on modern kernels (Closes: #722145). + + -- Andrew Shadura Wed, 06 Nov 2013 00:32:42 +0100 + am-utils (6.2+rc20110530-3) unstable; urgency=low * Fixed missing build dependency on dpkg-dev diff -u am-utils-6.2+rc20110530/debian/patches/series am-utils-6.2+rc20110530/debian/patches/series --- am-utils-6.2+rc20110530/debian/patches/series +++ am-utils-6.2+rc20110530/debian/patches/series @@ -9,0 +10,2 @@ +kernel-version.patch +fix-texi.patch only in patch2: unchanged: --- am-utils-6.2+rc20110530.orig/debian/patches/kernel-version.patch +++ am-utils-6.2+rc20110530/debian/patches/kernel-version.patch @@ -0,0 +1,35 @@ +From: Yoram Bar-Haim +Date: Sun, 22 Sep 2013 13:06:33 + (+0300) +Subject: fix flaw when kernel version is 3.x +X-Git-Url: http://git.fsl.cs.sunysb.edu/?p=am-utils-6.2.git;a=commitdiff_plain;h=3a382320e8d0b52a250efd8907f8429497de2335 + +fix flaw when kernel version is 3.x +--- + +--- a/conf/mount/mount_linux.c b/conf/mount/mount_linux.c +@@ -239,14 +239,20 @@ + int + linux_version_code(void) + { ++ char *token; ++ int shift = 16; + struct utsname my_utsname; + static int release = 0; + +- if ( 0 == release && 0 == uname(&my_utsname)) { +-release = 65536 * atoi(strtok(my_utsname.release, ".")) +- + 256 * atoi(strtok(NULL, ".")) +- + atoi(strtok(NULL, ".")); ++ if ( release || uname(&my_utsname)) ++return release; ++ ++ for (token = strtok(my_utsname.release, "."); token && (shift > -1); token = strtok(NULL, ".")) ++ { ++ release |= (atoi(token) << shift); ++ shift -= 8; + } ++ + return release; + } + only in patch2: unchanged: --- am-utils-6.2+rc20110530.orig/debian/patches/fix-texi.patch +++ am-utils-6.2+rc20110530/debian/patches/fix-texi.patch @@ -0,0 +1,11 @@ +--- a/doc/am-utils.texi b/doc/am-utils.texi +@@ -67,7 +67,7 @@ + Copyright @copyright{} 1989 Imperial College of Science, Technology & Medicine + @* + Copyright @copyright{} 1989 The Regents of the University of California. +-@sp ++@sp 1 + All Rights Reserved. + @vskip 1ex + Permission to copy this document, or any portion of it, as --- End Message --- --- Begin Message --- On Fri, Dec 6, 2013 at 21:28:34 +, Adam D. Barratt wrote: > Control: tags -1 + moreinfo > > On Thu, 2013-12-05 at 10:22 +0100, Andreas Beckmann wrote: > > > according to #722145 crashes unless the kernel version has 2 dots. > > While this is not a problem with the kernel in wheezy, it will prevent > > using it with newer kernels (backports, custom, vanilla, ...) > > > > I'm not a user of am-utils and don't know how to test this change > > properly. > > I'd appreciate it if someone could, before we look at including it. > That hasn't happened in the last two years; closing. Cheers, Julien signature.asc Description: PGP signature --- End Message ---
Bug#731414: marked as done (pu: NMU proftpd-mod-vroot/0.9.2-2)
Your message dated Sun, 21 Feb 2016 10:59:54 + with message-id <20160221105954.gq6...@betterave.cristau.org> and subject line Re: Bug#731414: pu: NMU proftpd-mod-vroot/0.9.2-2 has caused the Debian Bug report #731414, regarding pu: NMU proftpd-mod-vroot/0.9.2-2 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 731414: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=731414 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: release.debian.org Severity: normal Tags: wheezy User: release.debian@packages.debian.org Usertags: pu According to #715569 proftpd-mod-vroot needs to be rebuilt to be functional with the proftpd in wheezy. The 0.9.2-2+b2 binNMU that is to be found in most architectures in wheezy has been built against proftpd 1.3.4a-1, while wheezy has 1.3.4a-5+deb7u1 nowadays. I have no idea what causes this binary incompatibility. The usual command would probably be nmu proftpd-mod-vroot_0.9.2-2 . ALL . wheezy . -m "rebuild against proftpd 1.3.4a-5+deb7u1" but there has already been another binNMU in sid, so the next binNMU version is already taken: proftpd-mod-vroot | 0.9.2-2| wheezy | source, armhf proftpd-mod-vroot | 0.9.2-2| sid| source proftpd-mod-vroot | 0.9.2-2+b1 | wheezy | s390x proftpd-mod-vroot | 0.9.2-2+b1 | sid| armhf proftpd-mod-vroot | 0.9.2-2+b2 | wheezy | amd64, armel, i386, ia64, kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, s390, sparc proftpd-mod-vroot | 0.9.2-2+b2 | sid| s390x proftpd-mod-vroot | 0.9.2-2+b3 | sid| amd64, armel, i386, ia64, kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, sparc Andreas --- End Message --- --- Begin Message --- On Sat, Dec 7, 2013 at 13:36:33 +, Adam D. Barratt wrote: > Control: tags -1 + moreinfo > > On Thu, 2013-12-05 at 10:50 +0100, Andreas Beckmann wrote: > > According to #715569 proftpd-mod-vroot needs to be rebuilt to be > > functional with the proftpd in wheezy. The 0.9.2-2+b2 binNMU that is to > > be found in most architectures in wheezy has been built against > > proftpd 1.3.4a-1, while wheezy has 1.3.4a-5+deb7u1 nowadays. > > I have no idea what causes this binary incompatibility. > [...] > > proftpd-mod-vroot | 0.9.2-2| wheezy | source, armhf > > proftpd-mod-vroot | 0.9.2-2| sid| source > > proftpd-mod-vroot | 0.9.2-2+b1 | wheezy | s390x > > proftpd-mod-vroot | 0.9.2-2+b1 | sid| armhf > > proftpd-mod-vroot | 0.9.2-2+b2 | wheezy | amd64, armel, i386, ia64, > > kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, s390, sparc > > proftpd-mod-vroot | 0.9.2-2+b2 | sid| s390x > > proftpd-mod-vroot | 0.9.2-2+b3 | sid| amd64, armel, i386, ia64, > > kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, sparc > > Before we consider another rebuild in sid with a higher binNMU number, > do we know whether the package currently works there? > > Binary incompatibility breaking within uploads of the same upstream > release a) sucks and b) seems like something that should be expressed in > package relationships (or better yet, fixed). > No followup in 2+ years; closing. Cheers, Julien signature.asc Description: PGP signature --- End Message ---
Bug#785047: vsftpd/3.0.2-17+deb8u1
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Control: reopen -1 On 02/21/2016 11:08 AM, Jörg Frings-Fürst wrote: >> @Joerg: Could you re-upload the package to mentors? >> > > done.. [1] Reopening since I am preparing the upload now. Adrian - -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBCAAGBQJWyZfSAAoJEHQmOzf1tfkTTDAQAIfaINeqRqwFAkHslYKf9BjV 1St7RcUfUBk33JG+RMrSFS8ejZ2peDQAYVcgaLQrs0W4Tr0RuiLOeeD2mhPWTdX0 Uediyojh2zjzJHD6rTPe/I4CZMaaXNmUX3uUzmZZYiNwLcH9epbP9OG7v7K8mDC7 w2JS7EBpk0q8B+sZw+5ZC5gtwGud3n1GiJREm3GjZUOu7SSf1ii46Z+IBV1yeY4p Ufzp5FiY6nafYLakZbffATxXUvLIqW6+HpCdMjxJS4insrUiKDQ1CRnKVt+cyUf1 zgyPhVuOWmvqzoxau3Le4alFv+O5e8d1UZ1ye19kINxUjg+3LVKh9vJP5lP3fcUw F0mQdkkVI11nPilxSkQNIlSGZm6+ccCC63AWpD62uZw9DQdMf/FYsMZnxPzdfmlf 8s0TzuOwpUDIC8e+PVzNrSBfe6Rdn4VbZ4zmHYeajD6aM78vZSr+NfNlC1GNhqVu i6pDJD5X2kTDTrr6b1HuQHfSjyoxM74t57DQduQDkeaMJlJ6gd89mg1kd7wKJ6zT Q57o5axq0OVRTXiqll2BlsWGkLXcObSjsku9nn2IFxmygxmzp0dQ+1FbkpQDbaTR HZOIqhBjPIZ5p3Xx2ebnfmWR2aKUZ02b3CqZnYClJOPo7e5CdheBgi7B1xc2bfKy igrVcPwegKURt93/NM6W =vbBf -END PGP SIGNATURE-
Bug#719632: marked as done (pu: package nova/2012.1.1-18)
Your message dated Sun, 21 Feb 2016 10:56:54 + with message-id <20160221105654.go6...@betterave.cristau.org> and subject line Re: Bug#719632: Prepared a new Wheezy update for Nova has caused the Debian Bug report #719632, regarding pu: package nova/2012.1.1-18 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 719632: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=719632 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: pu Dear release team, Please find attached a serrie of correction I want to add to the current Nova package. It comes from the output of git format-patch of the wheezy branch of the Nova package, since the global debdiff for the package was less readable. In the 0001-CVE-2013-2096-OSSA-2013-012-Check-QCOW2-image-size-d.patch patch, there's normally a quilt refresh output, which I have removed from attached file so that you can read it better. Please let me know which of these patches is considered acceptable form the release team point of view. Cheers, Thomas Goirand (zigo) >From 4f384d61f29b604601bc69f66bfa8b10d440dcac Mon Sep 17 00:00:00 2001 From: Thomas Goirand Date: Sat, 13 Jul 2013 22:37:23 +0800 Subject: [PATCH 2/6] Do not use file from /usr/share/doc/nova-compute-xen in postinst (Closes: #710507) --- debian/changelog |2 ++ debian/nova-compute-xen.postinst |2 +- debian/rules |2 +- 3 files changed, 4 insertions(+), 2 deletions(-) diff --git a/debian/changelog b/debian/changelog index 3c5bf44..6e6eaaf 100644 --- a/debian/changelog +++ b/debian/changelog @@ -3,6 +3,8 @@ nova (2012.1.1-18+deb7u1) wheezy-proposed-updates; urgency=low * CVE-2013-2096: [OSSA 2013-012] Check QCOW2 image size during root disk creation (Closes: #710157). * Refreshes various patches (removes offsets when applying). + * Do not use file from /usr/share/doc/nova-compute-xen in postinst, thanks +to Andreas Beckmann for reporting (Closes: #710507). -- Thomas Goirand Sat, 13 Jul 2013 22:26:11 +0800 diff --git a/debian/nova-compute-xen.postinst b/debian/nova-compute-xen.postinst index f74e389..098c2c2 100644 --- a/debian/nova-compute-xen.postinst +++ b/debian/nova-compute-xen.postinst @@ -10,7 +10,7 @@ if [ "$1" = "configure" -o "$1" = "reconfigure" ]; then mkdir /etc/nova fi if ! [ -f ${XENAPI_CONFFILE} ] ; then - cp /usr/share/doc/nova-compute-xen/nova-compute.conf.dist ${XENAPI_CONFFILE} + cp /usr/share/nova-compute-xen/nova-compute.conf.dist ${XENAPI_CONFFILE} fi . /usr/share/debconf/confmodule diff --git a/debian/rules b/debian/rules index 6c91641..6fc41f1 100755 --- a/debian/rules +++ b/debian/rules @@ -30,7 +30,7 @@ override_dh_install: for hypervisor in qemu kvm uml lxc; do \ install -D -m 0600 $(CURDIR)/debian/nova-compute-$${hypervisor}.conf $(CURDIR)/debian/nova-compute-$${hypervisor}/etc/nova/nova-compute.conf; \ done - install -D -m 0600 $(CURDIR)/debian/nova-compute-xen.conf.dist $(CURDIR)/debian/nova-compute-xen/usr/share/doc/nova-compute-xen/nova-compute.conf.dist + install -D -m 0600 $(CURDIR)/debian/nova-compute-xen.conf.dist $(CURDIR)/debian/nova-compute-xen/usr/share/nova-compute-xen/nova-compute.conf.dist override_dh_fixperms: dh_fixperms -Xnova_sudoers -- 1.7.10.4 >From 55f8951757e0923c6919381e280ca4e7a3f7c321 Mon Sep 17 00:00:00 2001 From: Thomas Goirand Date: Sat, 13 Jul 2013 23:03:05 +0800 Subject: [PATCH 4/6] Fixes log rotation of nova-consoleauth.log and nova-xvpvncproxy.log (Closes: #706011) --- debian/changelog |5 + debian/nova-console.logrotate |2 +- debian/nova-xvpvncproxy.logrotate |4 ++-- 3 files changed, 8 insertions(+), 3 deletions(-) diff --git a/debian/changelog b/debian/changelog index 6c73dd9..a873cb7 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,5 +1,6 @@ nova (2012.1.1-18+deb7u1) wheezy-proposed-updates; urgency=low + [ Thomas Goirand ] * CVE-2013-2096: [OSSA 2013-012] Check QCOW2 image size during root disk creation (Closes: #710157). * Refreshes various patches (removes offsets when applying). @@ -7,6 +8,10 @@ nova (2012.1.1-18+deb7u1) wheezy-proposed-updates; urgency=low to Andreas Beckmann for reporting (Closes: #710507). * Updates debian/gbp.conf to use the debian/wheezy branch for building. + [ Julien Cristau ] + * Fixes log rotation of nova-consoleauth.log and nova-xvpvncproxy.log +(Closes: #706011). + -- Thomas Goirand Sat, 13 Jul 2013 22:26:
Processed: Re: Bug#785047: vsftpd/3.0.2-17+deb8u1
Processing control commands: > reopen -1 Bug #785047 {Done: Julien Cristau } [release.debian.org] jessie-pu: package vsftpd/3.0.2-17 Bug reopened Ignoring request to alter fixed versions of bug #785047 to the same values previously set -- 785047: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785047 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#780533: marked as done (pu: package jakarta-taglibs-standard/1.1.2-2)
Your message dated Sun, 21 Feb 2016 10:50:34 + with message-id <20160221105034.gm6...@betterave.cristau.org> and subject line Re: Bug#780533: pu: package jakarta-taglibs-standard/1.1.2-2 has caused the Debian Bug report #780533, regarding pu: package jakarta-taglibs-standard/1.1.2-2 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 780533: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=780533 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: pu Hi, This proposed update is to fix CVE-2015-0254 for jakarta-taglibs-standard in stable. I'm attaching a .debdiff with the proposed change. Cheers, -- System Information: Debian Release: 7.8 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.13-0.bpo.1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8) Shell: /bin/sh linked to /bin/dash -- Miguel Landaeta, nomadium at debian.org secure email with PGP 0x6E608B637D8967E9 available at http://miguel.cc/key. "Faith means not wanting to know what is true." -- Nietzsche jakarta-taglibs-standard_1.1.2-2+deb7u1.debdiff.gz Description: Binary data signature.asc Description: Digital signature --- End Message --- --- Begin Message --- On Sat, Aug 29, 2015 at 16:10:20 +0100, Adam D. Barratt wrote: > Control: tags -1 + confirmed > > Apologies for the delay in getting back to you. > > On Sun, 2015-03-15 at 16:44 -0300, Miguel Landaeta wrote: > > This proposed update is to fix CVE-2015-0254 for > > jakarta-taglibs-standard in stable. > > Please go ahead, using "wheezy" in the changelog rather than "stable". > That upload never happened. Closing. Cheers, Julien signature.asc Description: PGP signature --- End Message ---
Bug#776617: marked as done (wheezy-pu: fso stack)
Your message dated Sun, 21 Feb 2016 10:49:21 + with message-id <20160221104921.gl6...@betterave.cristau.org> and subject line Re: Bug#776617: wheezy-pu: fso stack has caused the Debian Bug report #776617, regarding wheezy-pu: fso stack to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 776617: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=776617 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: release.debian.org Severity: normal Tags: wheezy User: release.debian@packages.debian.org Usertags: pu Hi, I just requested unblocking of the fso stack for unstable -> testing migration. I also prepared fixed packages for wheezy and the security team send me here. This is the debdiff for the proposed stable updates: === debdiff fso-datad_0.11.0-1.dsc fso-datad_0.11.0-1+deb7u1.dsc === diff -Nru fso-datad-0.11.0/debian/changelog fso-datad-0.11.0/debian/changelog --- fso-datad-0.11.0/debian/changelog 2012-05-26 10:29:47.0 +0200 +++ fso-datad-0.11.0/debian/changelog 2015-01-28 00:18:22.0 +0100 @@ -1,3 +1,9 @@ +fso-datad (0.11.0-1+deb7u1) wheezy-security; urgency=high + + * Fix DBus permissions (Closes: CVE-2014-8156) + + -- Sebastian Reichel Wed, 28 Jan 2015 00:04:16 +0100 + fso-datad (0.11.0-1) unstable; urgency=low * New upstream release diff -Nru fso-datad-0.11.0/debian/patches/fix-dbus-permissions.patch fso-datad-0.11.0/debian/patches/fix-dbus-permissions.patch --- fso-datad-0.11.0/debian/patches/fix-dbus-permissions.patch 1970-01-01 01:00:00.0 +0100 +++ fso-datad-0.11.0/debian/patches/fix-dbus-permissions.patch 2015-01-28 00:15:03.0 +0100 @@ -0,0 +1,24 @@ +From: Sebastian Reichel +Reported-By: Simon McVittie +Last-Update: 2015-01-20 +Description: Fix Security Problem in DBus Configuration + Old configuration allows every local user to send arbitrary D-Bus + messages to the path /org/freesmartphone/Framework on *any* D-Bus + system service (rough HTTP analogy: send a POST to + http://server/org/freesmartphone/Framework on any server). +Bug-CVE: https://security-tracker.debian.org/tracker/CVE-2014-8156 + +Index: fso-datad/data/fsodatad.conf +=== +--- fso-datad.orig/data/fsodatad.conf fso-datad/data/fsodatad.conf +@@ -3,8 +3,7 @@ + + + +- +- ++ + + + diff -Nru fso-datad-0.11.0/debian/patches/series fso-datad-0.11.0/debian/patches/series --- fso-datad-0.11.0/debian/patches/series 1970-01-01 01:00:00.0 +0100 +++ fso-datad-0.11.0/debian/patches/series 2015-01-28 00:15:24.0 +0100 @@ -0,0 +1 @@ +fix-dbus-permissions.patch === debdiff fso-deviced_0.11.4-1.dsc fso-deviced_0.11.4-1+deb7u1.dsc === diff -Nru fso-deviced-0.11.4/debian/changelog fso-deviced-0.11.4/debian/changelog --- fso-deviced-0.11.4/debian/changelog 2012-06-01 07:00:15.0 +0200 +++ fso-deviced-0.11.4/debian/changelog 2015-01-28 01:17:12.0 +0100 @@ -1,3 +1,9 @@ +fso-deviced (0.11.4-1+deb7u1) wheezy-security; urgency=high + + * Fix DBus permissions (Closes: CVE-2014-8156) + + -- Sebastian Reichel Wed, 28 Jan 2015 00:40:54 +0100 + fso-deviced (0.11.4-1) unstable; urgency=low * New upstream release diff -Nru fso-deviced-0.11.4/debian/patches/fix-dbus-permissions.patch fso-deviced-0.11.4/debian/patches/fix-dbus-permissions.patch --- fso-deviced-0.11.4/debian/patches/fix-dbus-permissions.patch 1970-01-01 01:00:00.0 +0100 +++ fso-deviced-0.11.4/debian/patches/fix-dbus-permissions.patch 2015-01-28 00:40:03.0 +0100 @@ -0,0 +1,24 @@ +From: Sebastian Reichel +Reported-By: Simon McVittie +Last-Update: 2015-01-20 +Description: Fix Security Problem in DBus Configuration + Old configuration allows every local user to send arbitrary D-Bus + messages to the path /org/freesmartphone/Framework on *any* D-Bus + system service (rough HTTP analogy: send a POST to + http://server/org/freesmartphone/Framework on any server). +Bug-CVE: https://security-tracker.debian.org/tracker/CVE-2014-8156 + +Index: fso-deviced/data/fsodeviced.conf +=== +--- fso-deviced.orig/data/fsodeviced.conf fso-deviced/data/fsodeviced.conf +@@ -3,8 +3,7 @@ + + + +- +- ++ + + + diff -Nru fso-deviced-0.11.4/debian/patches/series fso-deviced-0.11.4/debian/patches/series --- fso-deviced-0.11.4/debian/patches/series2012-06-01 07:00:15.0 +0200 +++ fso-deviced-0.11.4/debi
Bug#746946: marked as done (wheezy-pu: package distro-info-data/0.23~deb7u1)
Your message dated Sun, 21 Feb 2016 10:48:19 + with message-id <20160221104819.gk6...@betterave.cristau.org> and subject line Re: Bug#746946: wheezy-pu: package distro-info-data/0.23~deb7u1 has caused the Debian Bug report #746946, regarding wheezy-pu: package distro-info-data/0.23~deb7u1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 746946: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746946 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: release.debian.org Severity: normal Tags: wheezy User: release.debian@packages.debian.org Usertags: pu Hi, can we please update distro-info-data, to add the next Ubuntu release, 14.10 - Utopic Unicorn. There are also a couple of minor support date updates, included, trivial packaging changes, and a bugfix to the Debian release versions. I don't think that risks regressions. As in the past, e.g. #727020, I'd be nice if this could go through stable-updates, but not essential. The impact of having this data package out of date is mostly restricted to ubuntu-dev-tools, which won't know the name of the current Ubuntu development release. Thanks, SR diff -Nru distro-info-data-0.17~deb7u1/debian/changelog distro-info-data-0.20~deb7u1/debian/changelog --- distro-info-data-0.17~deb7u1/debian/changelog 2013-10-21 17:13:46.0 +0200 +++ distro-info-data-0.20~deb7u1/debian/changelog 2014-05-04 10:58:03.0 +0200 @@ -1,3 +1,17 @@ +distro-info-data (0.20~deb7u1) unstable; urgency=medium + + [ Benjamin Drung ] + * Update EOL date of Ubuntu 12.10 "Quantal Quetzal" to 2014-05-16. + * Update EOL date of Ubuntu 13.04 "Raring Ringtai" to 2014-01-27. + * Bump Standards-Version to 3.9.5. + * Use just the stable release version without the point release suffix, +i.e. 6.0 for squeeze, 7 for wheezy, and 8 for jessie. (Closes: #724557) + + [ Stefano Rivera ] + * Add Ubuntu 14.10, Utopic Unicorn. + + -- Stefano Rivera Sun, 04 May 2014 10:57:29 +0200 + distro-info-data (0.17~deb7u1) stable; urgency=low * Add Ubuntu 14.04, Trusty Tahr. (Closes: #726696, 727020) diff -Nru distro-info-data-0.17~deb7u1/debian/compat distro-info-data-0.20~deb7u1/debian/compat --- distro-info-data-0.17~deb7u1/debian/compat 2013-05-11 01:08:18.0 +0200 +++ distro-info-data-0.20~deb7u1/debian/compat 2013-03-20 00:11:08.0 +0200 @@ -1 +1 @@ -8 +9 diff -Nru distro-info-data-0.17~deb7u1/debian/control distro-info-data-0.20~deb7u1/debian/control --- distro-info-data-0.17~deb7u1/debian/control 2013-05-11 01:08:18.0 +0200 +++ distro-info-data-0.20~deb7u1/debian/control 2014-01-07 23:18:24.0 +0200 @@ -3,10 +3,10 @@ Priority: optional Maintainer: Benjamin Drung Uploaders: Stefano Rivera -Build-Depends: debhelper (>= 8), python -Standards-Version: 3.9.3 -Vcs-Git: git://git.debian.org/git/collab-maint/distro-info-data.git -Vcs-Browser: http://git.debian.org/?p=collab-maint/distro-info-data.git +Build-Depends: debhelper (>= 9), python +Standards-Version: 3.9.5 +Vcs-Git: git://anonscm.debian.org/collab-maint/distro-info-data.git +Vcs-Browser: http://anonscm.debian.org/gitweb/?p=collab-maint/distro-info-data.git Package: distro-info-data Architecture: all diff -Nru distro-info-data-0.17~deb7u1/debian/copyright distro-info-data-0.20~deb7u1/debian/copyright --- distro-info-data-0.17~deb7u1/debian/copyright 2013-05-11 01:08:18.0 +0200 +++ distro-info-data-0.20~deb7u1/debian/copyright 2013-03-20 00:11:10.0 +0200 @@ -3,7 +3,7 @@ Upstream-Contact: Benjamin Drung Files: * -Copyright: 2009-2012, Benjamin Drung +Copyright: 2009-2013, Benjamin Drung License: ISC Permission to use, copy, modify, and/or distribute this software for any purpose with or without fee is hereby granted, provided that the above diff -Nru distro-info-data-0.17~deb7u1/debian.csv distro-info-data-0.20~deb7u1/debian.csv --- distro-info-data-0.17~deb7u1/debian.csv 2013-10-21 16:58:51.0 +0200 +++ distro-info-data-0.20~deb7u1/debian.csv 2014-01-07 23:19:29.0 +0200 @@ -10,7 +10,7 @@ 4.0,Etch,etch,2005-06-06,2007-04-08,2010-02-15 5.0,Lenny,lenny,2007-04-08,2009-02-14,2012-02-06 6.0,Squeeze,squeeze,2009-02-14,2011-02-06,2014-05-04 -7.0,Wheezy,wheezy,2011-02-06,2013-05-04 -8.0,Jessie,jessie,2013-05-04 +7,Wheezy,wheezy,2011-02-06,2013-05-04 +8,Jessie,jessie,2013-05-04 ,Sid,sid,1993-08-16 ,Experimental,experimental,1993-08-16 diff -Nru distro-info-data-0.17~deb7u1/ubuntu.csv distro-info-data-0.20~deb7u1/ubuntu.csv --- distro-info-data-0.17~deb7u1/ubuntu.csv 2013
Bug#731735: marked as done (pu: package glance/2012.1.1-5+deb7u1)
Your message dated Sun, 21 Feb 2016 10:47:03 + with message-id <20160221104703.gj6...@betterave.cristau.org> and subject line Re: Bug#731735: pu: package glance/2012.1.1-5+deb7u1 has caused the Debian Bug report #731735, regarding pu: package glance/2012.1.1-5+deb7u1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 731735: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=731735 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: pu Hi, I have prepared an update for Glance over here: http://archive.gplhost.com/pub/security/glance/ Attached to this mail is the relevant debdiff for Glance. What the update does is only fixing the logrotate path, which is currently wrong in the current Wheezy version. Here's the changelog: [ Thomas Goirand ] * debian/gbp.conf now tracking the debian/wheezy branch. [ Julien Cristau ] * Fix logrotate config to reference the right file names. Thanks considering this and letting me know, Thomas Goirand (zigo) diff -Nru glance-2012.1.1/debian/changelog glance-2012.1.1/debian/changelog --- glance-2012.1.1/debian/changelog 2013-03-14 20:53:41.0 + +++ glance-2012.1.1/debian/changelog 2013-12-09 07:48:43.0 + @@ -1,3 +1,13 @@ +glance (2012.1.1-5+deb7u1) wheezy-proposed-updates; urgency=low + + [ Thomas Goirand ] + * debian/gbp.conf now tracking the debian/wheezy branch. + + [ Julien Cristau ] + * Fix logrotate config to reference the right file names. + + -- Thomas Goirand Mon, 09 Dec 2013 15:44:43 +0800 + glance (2012.1.1-5) unstable; urgency=high * CVE-2013-1840: fixes "Backend credentials leak in Glance v1 API" diff -Nru glance-2012.1.1/debian/gbp.conf glance-2012.1.1/debian/gbp.conf --- glance-2012.1.1/debian/gbp.conf 2013-03-14 20:53:41.0 + +++ glance-2012.1.1/debian/gbp.conf 2013-12-09 07:48:43.0 + @@ -1,6 +1,6 @@ [DEFAULT] upstream-branch = master -debian-branch = debian/unstable +debian-branch = debian/wheezy upstream-tag = %(version)s compression = xz diff -Nru glance-2012.1.1/debian/glance-api.logrotate glance-2012.1.1/debian/glance-api.logrotate --- glance-2012.1.1/debian/glance-api.logrotate 2013-03-14 20:53:41.0 + +++ glance-2012.1.1/debian/glance-api.logrotate 2013-12-09 07:48:43.0 + @@ -1,4 +1,4 @@ -/var/log/glance/glance-api.log { +/var/log/glance/api.log { daily missingok compress diff -Nru glance-2012.1.1/debian/glance-registry.logrotate glance-2012.1.1/debian/glance-registry.logrotate --- glance-2012.1.1/debian/glance-registry.logrotate 2013-03-14 20:53:41.0 + +++ glance-2012.1.1/debian/glance-registry.logrotate 2013-12-09 07:48:43.0 + @@ -1,4 +1,4 @@ -/var/log/glance/glance-registry.log { +/var/log/glance/registry.log { daily missingok compress --- End Message --- --- Begin Message --- On Sat, Jan 17, 2015 at 11:47:40 +, Adam D. Barratt wrote: > On 2014-08-24 19:58, Adam D. Barratt wrote: > >On 2014-01-22 21:37, Adam D. Barratt wrote: > >>On Mon, 2013-12-09 at 18:12 +0100, Moritz Mühlenhoff wrote: > I have prepared an update for Glance over here: > http://archive.gplhost.com/pub/security/glance/ > >>> > >>>The security tracker lists this issue as potentially open in > >>>Wheezy: https://security-tracker.debian.org/tracker/CVE-2013-4354 > >>> > >>>Does this affect stable and is there a fix which can be included > >>>along? > >> > >>Ping? (On both the original upload and Moritz's question.) > > > >Re-ping. > > Re-re-ping. > > If nothing happens with this soon then I'm tempted to close the request, > rather than leaving it open indefinitely. > That was over a year ago; closing. Cheers, Julien--- End Message ---
Bug#726558: marked as done (pu: package policykit-1/0.105-3+deb7u1)
Your message dated Sun, 21 Feb 2016 10:46:24 + with message-id <20160221104624.gi6...@betterave.cristau.org> and subject line Re: Bug#726558: pu: package policykit-1/0.105-3+deb7u1 has caused the Debian Bug report #726558, regarding pu: package policykit-1/0.105-3+deb7u1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 726558: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=726558 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: pu As discussed in [1], I'd like to upload a fix for CVE-2013-4288 for policykit-1 to stable. The patch itself has been applied to the unstable version as well (in 0.105-3+nmu1). Please let me know if I can proceed with the stable upload to get this fix into 7.3. Full debdiff is attached. Regards, Michael [1] https://lists.debian.org/debian-release/2013/10/msg00604.html -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (200, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.10-3-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash diff --git a/debian/changelog b/debian/changelog index c3ab45b..1644c95 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,9 @@ +policykit-1 (0.105-3+deb7u1) stable; urgency=low + + * Fix CVE-2013-4288: race condition in pkcheck. (Closes: #723717) + + -- Michael Biebl Wed, 16 Oct 2013 18:35:01 +0200 + policykit-1 (0.105-3) unstable; urgency=low * 07_set-XAUTHORITY-environment-variable-if-unset.patch: Set XAUTHORITY diff --git a/debian/gbp.conf b/debian/gbp.conf index c31be83..a475fbf 100644 --- a/debian/gbp.conf +++ b/debian/gbp.conf @@ -1,3 +1,3 @@ [DEFAULT] pristine-tar = True -debian-branch = master +debian-branch = wheezy diff --git a/debian/patches/cve-2013-4288.patch b/debian/patches/cve-2013-4288.patch new file mode 100644 index 000..2aad36c --- /dev/null +++ b/debian/patches/cve-2013-4288.patch @@ -0,0 +1,115 @@ +From 52c927893a2ab135462b616c2e00fec377da9885 Mon Sep 17 00:00:00 2001 +From: Colin Walters +Date: Mon, 19 Aug 2013 12:16:11 -0400 +Subject: [PATCH 2/4] pkcheck: Support --process=pid,start-time,uid syntax too + +The uid is a new addition; this allows callers such as libvirt to +close a race condition in reading the uid of the process talking to +them. They can read it via getsockopt(SO_PEERCRED) or equivalent, +rather than having pkcheck look at /proc later after the fact. + +Programs which invoke pkcheck but need to know beforehand (i.e. at +compile time) whether or not it supports passing the uid can +use: + +pkcheck_supports_uid=$($PKG_CONFIG --variable pkcheck_supports_uid polkit-gobject-1) +test x$pkcheck_supports_uid = xyes +--- + data/polkit-gobject-1.pc.in |3 +++ + docs/man/pkcheck.xml| 29 - + src/programs/pkcheck.c |9 +++-- + 3 files changed, 30 insertions(+), 11 deletions(-) + +Index: policykit-1-0.105/data/polkit-gobject-1.pc.in +=== +--- policykit-1-0.105.orig/data/polkit-gobject-1.pc.in 2013-09-11 09:40:56.604225567 -0400 policykit-1-0.105/data/polkit-gobject-1.pc.in 2013-09-11 09:40:56.596225567 -0400 +@@ -11,3 +11,6 @@ + Libs: -L${libdir} -lpolkit-gobject-1 + Cflags: -I${includedir}/polkit-1 + Requires: gio-2.0 >= 2.18 glib-2.0 >= 2.18 ++# Programs using pkcheck can use this to determine ++# whether or not it can be passed a uid. ++pkcheck_supports_uid=true +Index: policykit-1-0.105/docs/man/pkcheck.xml +=== +--- policykit-1-0.105.orig/docs/man/pkcheck.xml 2013-09-11 09:40:56.604225567 -0400 policykit-1-0.105/docs/man/pkcheck.xml 2013-09-11 09:42:28.272223569 -0400 +@@ -55,6 +55,9 @@ + + pid,pid-start-time + ++ ++ pid,pid-start-time,uid ++ + + + +@@ -90,7 +93,7 @@ + DESCRIPTION + + pkcheck is used to check whether a process, specified by +- either --process or --system-bus-name, ++ either --process (see below) or --system-bus-name, + is authorized for action. The --detail + option can be used zero or more times to pass details about action. + If --allow-user-interaction is passed, pkcheck blocks +@@ -160,17 +163,25 @@ + + NOTES + +- Since process ide
Bug#725142: marked as done (pu: package totem-plugin-arte/3.1.2-1+deb7u1)
Your message dated Sun, 21 Feb 2016 10:44:14 + with message-id <20160221104414.gh6...@betterave.cristau.org> and subject line Re: Bug#725142: pu: package totem-plugin-arte/3.2.1-1~wheezy1 has caused the Debian Bug report #725142, regarding pu: package totem-plugin-arte/3.1.2-1+deb7u1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 725142: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=725142 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: pu The current totem-plugin-arte package in Wheezy is unusable because of a changes on Arte's website. My package is on mentors.debian.net: http://mentors.debian.net/package/totem-plugin-arte The version I'm proposing is directly based on the latest upstream release, which fix this problem and some other (small) issues. Backporting the relevant commits as patches to the current wheezy version would bring most of the code from the new upstream version, so I thought adding a small patch to make the new version build with the old Totem from Wheezy was the right thing to do. Here is the upstream changelog since 3.1.2 (the current Wheezy version), with some annotations. - 2013 September 22th - Totem Arte Plugin 3.2.1 Changes since 3.2.0: * Fixed the extraction of https video links * Fixed preferences mnemonics in English 2013 September 10th - Totem Arte Plugin 3.2.0 Changes since 3.1.3: * Fix stream extraction from the new Arte website * Reimplementation of the removed Totem.CellRenderVideo -> could be reverted * New and more efficient primary video feed source (JSON) -> Now required * Support for low quality streams -> could be reverted * Minor bug fixes and translation updates 2012 December 9th - Totem Arte Plugin 3.1.3 Changes since 3.1.2: * Fix compilation with Vala 0.18 and Totem 3.6.0 -> REVERTED, see debian/patches - The new package also includes the harden binary that is already in experimental and Ubuntu since many months. Here is the proposed debian/changelog: totem-plugin-arte (3.2.1-1~wheezy1) stable; urgency=low * New upstream release * Add a patch to build against Totem 3.0 (revert an upstream commit) * Harden the binary, fix 2 lintian warnings * Bump Debian Policy to 3.9.4 (no change needed) -- Nicolas Delvaux Wed, 02 Oct 2013 00:20:15 +0200 Totem-plugin-arte is a leaf package and the current Wheezy version is unusable. IMHO, this looks like a very low risk upgrade. Regards, Nicolas --- End Message --- --- Begin Message --- On Sat, Aug 29, 2015 at 15:51:12 +0100, Adam D. Barratt wrote: > Control: tags -1 + confirmed > > On Thu, 2014-10-09 at 21:15 +0200, Nicolas Delvaux wrote: > > Hi, > > > > A year later, the package is still broken in Stable. > > > > Here is, yet again, a new debdiff. > > Compared to the previous one, I edited a regex in order to be > > compatible with a change that recently happened on the Arte Website. > > Apologies for the delays. If this something you're still interested in > fixing in wheezy, then please feel free to upload (with "wheezy" in the > changelog rather than "stable"). > Apparently not; closing. Cheers, Julien--- End Message ---
Bug#699806: marked as done (pu: dlocate/1.02+deb7u1)
Your message dated Sun, 21 Feb 2016 10:43:39 + with message-id <20160221104339.gg6...@betterave.cristau.org> and subject line Re: Bug#699806: unblock: dlocate/1.02+nmu3 has caused the Debian Bug report #699806, regarding pu: dlocate/1.02+deb7u1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 699806: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=699806 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: release.debian.org Severity: normal Tags: patch User: release.debian@packages.debian.org Usertags: unblock Please unblock package dlocate dlocate has been neglected for quite some time now. I have collected some patches to fix several minor but annoying bugs in the bugtracker and fixed the manpages. I understand that these changes are not relevant for security-related issues and I naturally accept if my unblock request gets rejected. However, I think all these changes are nice to have and bring the package into a much better shape for shipping with Wheezy. I am attaching the debdiff between the version in testing and unstable. Cheers, Adrian unblock dlocate/1.02+nmu3 -- System Information: Debian Release: 7.0 APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.7-trunk-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8) Shell: /bin/sh linked to /bin/dash diff -Nru dlocate-1.02/debian/changelog dlocate-1.02+nmu3/debian/changelog --- dlocate-1.02/debian/changelog 2009-06-03 03:24:04.0 +0200 +++ dlocate-1.02+nmu3/debian/changelog 2012-12-29 14:34:22.0 +0100 @@ -1,3 +1,28 @@ +dlocate (1.02+nmu3) unstable; urgency=low + + * Non-maintainer upload. + * Fix handling of multiple arguments for several commands (Closes: #563881). + * Fix dlocate return codes for several commands on exit (Closes: #564293). + + -- John Paul Adrian Glaubitz Sat, 29 Dec 2012 14:32:54 +0100 + +dlocate (1.02+nmu2) unstable; urgency=low + + * Non-maintainer upload. + * Add missing "--" when invoking grep command (Closes: #587179). + * Fix bash completion for package names in dlocate (Closes: # 658669). + * Fix incorrect exit code 0 on failed search (Closes: #689647). + * Fix parameter passing to dlocate_option_error() in dlocate (Closes: # 690758). + + -- John Paul Adrian Glaubitz Fri, 28 Dec 2012 15:42:16 +0100 + +dlocate (1.02+nmu1) unstable; urgency=low + + * Non-maintainer upload. + * Fix several mistakes in manpages (Closes: #586483, #692896, #696479). + + -- John Paul Adrian Glaubitz Fri, 21 Dec 2012 11:47:08 +0100 + dlocate (1.02) unstable; urgency=low * fixed example in dlocate.1 man page again (Closes: #42) diff -Nru dlocate-1.02/dlocate dlocate-1.02+nmu3/dlocate --- dlocate-1.02/dlocate 2009-06-03 03:28:53.0 +0200 +++ dlocate-1.02+nmu3/dlocate 2012-12-29 14:30:19.0 +0100 @@ -199,7 +199,7 @@ ;; (-*) -dlocate_option_error $1 +dlocate_option_error $p ;; (*) @@ -217,7 +217,7 @@ FILES_REGEXP="($PKGS_REGEXP)" [ "$WORD_RE" = "-w" ] && FILES_REGEXP="\b$FILES_REGEXP\b" -PKGS=$(echo "$PKGS" | sed -e "s/$SEPARATOR/ /") +PKGS=$(echo "$PKGS" | sed -e "s/$SEPARATOR/ /g") if [ "$VERBOSE" = "1" ] ; then echo "PKGS:" $PKGS @@ -277,15 +277,15 @@ PREFIX="^([-a-zA-Z0-9_.+]+:|diversion by )" [ "$RE_TYPE" = "-G" ] && PREFIX="^([-a-zA-Z0-9_.+]+:\|diversion by )" -[ "$VERBOSE" = "1" ] && echo RUNNING: $GREP $RE_TYPE $IGNORE_CASE "$PREFIX.*$FILES_REGEXP" "$DLOCATEDB" -$GREP $RE_TYPE $IGNORE_CASE "$PREFIX.*$FILES_REGEXP" "$DLOCATEDB" | output_filter -result=$? +[ "$VERBOSE" = "1" ] && echo RUNNING: $GREP $RE_TYPE $IGNORE_CASE -- "$PREFIX.*$FILES_REGEXP" "$DLOCATEDB" +$GREP $RE_TYPE $IGNORE_CASE -- "$PREFIX.*$FILES_REGEXP" "$DLOCATEDB" | output_filter +result=${PIPESTATUS[0]} elif [ "$OPTION" = 'DEFAULT' ] ; then -[ "$VERBOSE" = "1" ] && echo RUNNING: $GREP $RE_TYPE $IGNORE_CASE $WORD_RE "$PKGS_REGEXP" "$DLOCATEDB" -$GREP $RE_TYPE $IGNORE_CASE $WORD_RE "$PKGS_REGEXP" "$DLOCATEDB" | output_filter -result=$? +[ "$VERBOSE" = "1" ] && echo RUNNING: $GREP $RE_TYPE $IGNORE_CASE -- $WORD_RE "$PKGS_REGEXP" "$DLOCATEDB" +$GREP $RE_TYPE $IGNORE_CASE -- $WORD_RE "$PKGS_REGEXP" "$DLOCATEDB" | output_filter +result=${PIPESTATUS[0]} elif [ "$OPTION" = '-s' ] ; then DCTRL_REGEXP="^($PKGS_REGEXP)$" @@ -316,48 +316,60 @@ '-L')
Bug#814651: jessie-pu: package sitesummary/0.1.17+deb8u1
Control: tags -1 + pending On Sat, 2016-02-20 at 16:27 +0100, Petter Reinholdtsen wrote: > [Adam D. Barratt] > > The comment for the prerm is wrong (twice) - it's disabling, not > > enabling, the configuration and not checking for cgi.load. > > Right. It was wrong in the master branch and unstable too. I've fixed > the master branch, and will upload the fix later. Thanks. > > Other than that, please go ahead. > > The fix for jessie is uploaded, and the changes available in the jessie > branch in > http://anonscm.debian.org/cgit/debian-edu/upstream/sitesummary.git >. Flagged for acceptance. Regards, Adam
Processed: Re: Bug#814651: jessie-pu: package sitesummary/0.1.17+deb8u1
Processing control commands: > tags -1 + pending Bug #814651 [release.debian.org] jessie-pu: package sitesummary/0.1.17+deb8u1 Added tag(s) pending. -- 814651: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814651 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#814266: jessie-pu: package pagekite/0.5.6d-3+deb8u1
Control: tags -1 + pending On Sat, 2016-02-20 at 15:01 +0100, Petter Reinholdtsen wrote: > [Adam D. Barratt] > > Please go ahead. > > Thank you. Uploaded, and a new branch jessie-update contain the > changes on > https://anonscm.debian.org/gitweb/?p=collab-maint/pagekite.git >. Flagged for acceptance. Regards, Adam
Processed: Re: Bug#814266: jessie-pu: package pagekite/0.5.6d-3+deb8u1
Processing control commands: > tags -1 + pending Bug #814266 [release.debian.org] jessie-pu: package pagekite/0.5.6d-3+deb8u1 Added tag(s) pending. -- 814266: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814266 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#797192: marked as done (jessie-pu: package nova/2014.1.3-11 (CVE-2015-3241, #796109))
Your message dated Sun, 21 Feb 2016 10:36:56 + with message-id <20160221103656.gf6...@betterave.cristau.org> and subject line Re: Bug#797192: Hang on has caused the Debian Bug report #797192, regarding jessie-pu: package nova/2014.1.3-11 (CVE-2015-3241, #796109) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 797192: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=797192 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: release.debian.org Severity: normal Tags: jessie User: release.debian@packages.debian.org Usertags: pu Hi, I've prepared an update of nova for Jessie which fixes CVE-2015-3241. This CVE is about DoS nova-compute machines by resizing and immediately after it delete the VM, which makes nova-compute consume all CPU. The package is available here: http://sid.gplhost.com/jessie-proposed-updates/nova/ Please allow me to upload it to jessie-p-u. Cheers, Thomas Goirand (zigo) P.S: As we speak, I'm preparing the update for Sid, it should be ready soonish today, and it will include the point release update. diff -Nru nova-2014.1.3/debian/changelog nova-2014.1.3/debian/changelog --- nova-2014.1.3/debian/changelog 2015-03-11 08:48:55.0 + +++ nova-2014.1.3/debian/changelog 2015-08-28 09:24:00.0 + @@ -1,3 +1,10 @@ +nova (2014.1.3-11+deb8u1) jessie-proposed-updates; urgency=medium + + * CVE-2015-3241: Resize/delete combo allows to overload nova-compute. Applied +upstream patch (Closes: #796109). + + -- Thomas Goirand Fri, 28 Aug 2015 11:10:06 +0200 + nova (2014.1.3-11) unstable; urgency=high * CVE-2015-0259: Websocket Hijacking Vulnerability in Nova VNC Server. Done diff -Nru nova-2014.1.3/debian/patches/CVE-2015-3241_Resize_delete_combo_allow_to_overload_nova-compute.patch nova-2014.1.3/debian/patches/CVE-2015-3241_Resize_delete_combo_allow_to_overload_nova-compute.patch --- nova-2014.1.3/debian/patches/CVE-2015-3241_Resize_delete_combo_allow_to_overload_nova-compute.patch 1970-01-01 00:00:00.0 + +++ nova-2014.1.3/debian/patches/CVE-2015-3241_Resize_delete_combo_allow_to_overload_nova-compute.patch 2015-08-28 09:24:00.0 + @@ -0,0 +1,103 @@ +Description: CVE-2015-3241: Sync process utils from oslo for execute callbacks + The sync pulls in the following changes: + . + Ifc23325 Add 2 callbacks to processutils.execute() + I22b2d7b processutils: ensure on_completion callback is always called + I59d5799 Let oslotest manage the six.move setting for mox + I245750f Remove `processutils` dependency on `log` + Ia5bb418 Fix exception message in openstack.common.processutils.execute +Author: Abhishek Kekane +Bug-Debian: https://bugs.debian.org/796109 +Origin: upstream, https://review.openstack.org/#/c/208876/ +Bug-Ubuntu: https://launchpad.net/bugs/1387543 +Last-Update: 2015-08-28 + +--- nova-2014.1.3.orig/nova/openstack/common/processutils.py nova-2014.1.3/nova/openstack/common/processutils.py +@@ -112,6 +112,17 @@ def execute(*cmd, **kwargs): + :type shell:boolean + :param loglevel:log level for execute commands. + :type loglevel: int. (Should be logging.DEBUG or logging.INFO) ++:param on_execute: This function will be called upon process creation ++with the object as a argument. The Purpose of this ++is to allow the caller of `processutils.execute` to ++track process creation asynchronously. ++:type on_execute: function(:class:`subprocess.Popen`) ++:param on_completion: This function will be called upon process ++completion with the object as a argument. The ++Purpose of this is to allow the caller of ++`processutils.execute` to track process completion ++asynchronously. ++:type on_completion:function(:class:`subprocess.Popen`) + :returns: (stdout, stderr) from process execution + :raises::class:`UnknownArgumentError` on + receiving unknown arguments +@@ -127,6 +138,8 @@ def execute(*cmd, **kwargs): + root_helper = kwargs.pop('root_helper', '') + shell = kwargs.pop('shell', False) + loglevel = kwargs.pop('loglevel', logging.DEBUG) ++on_execute = kwargs.pop('on_execute', None) ++on_completion = kwargs.pop('on_completion', None) + + if isinstance(check_exit_code, bool): + ignore_exit_code = not check_exit_code +@@ -135,8 +148,7 @@ def exe
Processed: Re: Bug#815356: jessie-pu: package ruby-standalone/0.5+deb8u1
Processing control commands: > tags -1 + confirmed Bug #815356 [release.debian.org] jessie-pu: package ruby-standalone/0.5+deb8u1 Added tag(s) confirmed. -- 815356: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815356 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#815356: jessie-pu: package ruby-standalone/0.5+deb8u1
Control: tags -1 + confirmed On Sat, 2016-02-20 at 22:05 -0200, Antonio Terceiro wrote: > I would like to upload a stable update for ruby-standalone, that makes > it work correctly with bundler, which is a very important use case. Please go ahead. Regards, Adam
Bug#793117: marked as done (jessie-pu: package python-memcache/1.53+2014.06.08.git.918e88c496-1+deb8u1)
Your message dated Sun, 21 Feb 2016 10:33:22 + with message-id <20160221103322.gd6...@betterave.cristau.org> and subject line Re: Bug#793117: jessie-pu: package python-memcache/1.53+2014.06.08.git.918e88c496-1+deb8u1 has caused the Debian Bug report #793117, regarding jessie-pu: package python-memcache/1.53+2014.06.08.git.918e88c496-1+deb8u1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 793117: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=793117 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: release.debian.org Severity: normal Tags: jessie User: release.debian@packages.debian.org Usertags: pu Hi, I would like to propose a stable upload for python-memcache. python-memcache's version currently in stable (1.53+2014.06.08.git.918e88c496-1) is building python3-memcache though its code isn't fully python3 compatible. This python3 package is unusuable and shouldn't exist[0]. The upstream code have been ported to python3 in sid, but this fix shouldn't probably be backported since it would require an upstream code upgrade from 1.53 to 1.54 in Jessie. The easiest solution is to make python-memcache stops building python3-memcache in Jessie. This can be done with the attached fix. The diff against 1.53+2014.06.08.git.918e88c496-1+deb8u1 is attached. Best Regards, Hugo [0] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=788561 -- Hugo Lefeuvre (hugo6390)|www.hugo6390.org 4096/ ACB7 B67F 197F 9B32 1533 431C AC90 AC3E C524 065E --- a/debian/changelog 2015-07-13 11:00:34.426439594 +0200 +++ b/debian/changelog 2015-07-13 11:00:49.106419709 +0200 @@ -1,3 +1,12 @@ +python-memcache (1.53+2014.06.08.git.918e88c496-1+deb8u1) jessie; urgency=medium + + * Team upload. + * debian/control, debian/rules: + - Don't build python3-memcache anymore, upstream's Python3 support + is too incomplete (Closes: #788561). + + -- Hugo Lefeuvre Sun, 12 Jul 2015 22:22:34 +0200 + python-memcache (1.53+2014.06.08.git.918e88c496-1) unstable; urgency=medium * New upstream release. --- a/debian/control 2015-07-13 11:00:34.426439594 +0200 +++ b/debian/control 2015-07-13 11:00:34.422439599 +0200 @@ -5,9 +5,7 @@ Uploaders: Carl Chenet , Thomas Goirand Build-Depends: debhelper (>= 9), python-all (>= 2.6.6-3), - python-setuptools, - python3-all, - python3-setuptools + python-setuptools Standards-Version: 3.9.5 Homepage: http://www.tummy.com/Community/software/python-memcached/ Vcs-Svn: svn://anonscm.debian.org/python-modules/packages/python-memcache/trunk/ @@ -23,14 +21,3 @@ one or more, possibly remote, memcached servers. . This package contains the Python 2.x module. - -Package: python3-memcache -Architecture: all -Depends: python3-six, ${misc:Depends}, ${python3:Depends} -Suggests: memcached -Description: pure python memcached client - Python 3.x - This software is a 100% Python interface to the memcached memory cache daemon. - It is the client side software which allows storing values in one or more, - possibly remote, memcached servers. - . - This package contains the Python 3.x module. --- a/debian/rules 2015-07-13 11:00:34.426439594 +0200 +++ b/debian/rules 2015-07-13 11:00:34.422439599 +0200 @@ -1,22 +1,17 @@ #!/usr/bin/make -f PYTHONS:=$(shell pyversions -vr) -PYTHON3S:=$(shell py3versions -vr) UPSTREAM_GIT = git://github.com/linsomniac/python-memcached.git %: - dh $@ --buildsystem=python_distutils --with python2,python3 + dh $@ --buildsystem=python_distutils --with python2 override_dh_install: set -e && for pyvers in $(PYTHONS); do \ python$$pyvers setup.py install --install-layout=deb \ --root $(CURDIR)/debian/python-memcache; \ done - set -e && for pyvers in $(PYTHON3S); do \ - python$$pyvers setup.py install --install-layout=deb \ - --root $(CURDIR)/debian/python3-memcache; \ - done override_dh_clean: dh_clean -O--buildsystem=python_distutils --- End Message --- --- Begin Message --- On Sat, Jul 25, 2015 at 17:34:13 +0100, Adam D. Barratt wrote: > Control: tags -1 + moreinfo > > On Tue, 2015-07-21 at 15:04 +0200, Hugo Lefeuvre wrote: > > python-memcache's version currently in stable > > (1.53+2014.06.08.git.918e88c496-1) > > is building python3-memcache though its code isn't fully python3 > > compatible. This python3 package is unusuable and shouldn't exist[0]. > > > > The upstream code have been ported to python3 in sid, but this fix > > shouldn't probably be backported since it would require an upstream code > > upgrade from 1.53
Bug#796593: marked as done (pu: package emdebian-archive-keyring/2.0.4)
Your message dated Sun, 21 Feb 2016 10:34:21 + with message-id <20160221103421.ge6...@betterave.cristau.org> and subject line Re: Bug#796593: pu: package emdebian-archive-keyring/2.0.4 has caused the Debian Bug report #796593, regarding pu: package emdebian-archive-keyring/2.0.4 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 796593: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=796593 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: pu The emdebian-archive-keyring package in jessie contains the old key which was revoked when the emdebian server was compromised in November 2014. A new server has since been set up and a new key used for the cross-toolchain/cross-building archive which is still hosted there. This is the recommended way to get cross-toolchains installed for jessie (for pre-built architectures): https://wiki.debian.org/CrossToolchains#For_jessie_.28Debian_8.29 This is made much harder than it should be because manual key downloading and checking is needed due to this package (version 2.0.4) being essentially useless in jessie. The 2.0.5 version in testing really should be in jessie too so that people would have a convenient authenticated route to using the jessie cross-toolchains archive. AIUI I do not need to do a new upload if the package containing just the necesary fix is already in unstable/testing. That is the case here. Attached is the diff for 2.0.4 -> 2.0.5 (Note: I will be offline until 5th Sept - not sure what the schedule for the next stable release is) -- System Information: Debian Release: 7.8 APT prefers oldstable-updates APT policy: (500, 'oldstable-updates'), (500, 'oldstable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/8 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash diff -Nru emdebian-archive-keyring-2.0.4/0x97BB3B58.txt emdebian-archive-keyring-2.0.5/0x97BB3B58.txt --- emdebian-archive-keyring-2.0.4/0x97BB3B58.txt 2014-11-27 09:26:06.0 + +++ emdebian-archive-keyring-2.0.5/0x97BB3B58.txt 1970-01-01 01:00:00.0 +0100 @@ -1,36 +0,0 @@ --BEGIN PGP PUBLIC KEY BLOCK- -Version: GnuPG v1 - -mQGiBEY1QygRBACUM8ypZIqJu1O/jjmZJ2XmVHPUMygzcAOXfOsfLBaIz5UmYOCc -22iFN5Milj4hEpgrVnyGgXZh1vA2xbxGZNdjMfge7z0Bvf93RM6gzVnU4EXWu4sW -4nfyPH28/ChsA89mXFnS99zqsRfZNYjQdRCH4LByP7AnXojKU3gq1b4ydwCgzzBV -izehffV2lW7LDv9NhMePhzMD/0mrIUPfCvp0wKXRSHuYaLZiuoI6gV4HrAxLqeo9 -+GXfBb6n6Fpl52fRGbBAtatZ9wDVJi8v7kFQTvX3vcYGYVKmjJBT2aOx7ZhYNXV2 -lncL6e8+b8gG8f+asV2JbdpZCR4KiDyko6VCWZswqpKytrgK+hK+ECS5Mre1Oy+Z -RuaFBACJcxP4h4M0J1vY0wzlXUw81u+BNJkGanW57JIsP/mwvR4MqLfyi7tAmuPX -L6/aWsLvLGYZlFJynZ+1mXXoRUevCGcEc9gK/dpTKVYLRsS0TtNXwaY4hwF7QpBb -gh6Bx/TDBHYjADaYu2EZcwFI29kgwAfwAfyabB/hCfKHT12D5ohJBCARCgAJBQJU -cueVAh0CAAoJELW3cgCXuztYfq0An07hWjCfb5DuCbWVYyF1Q/j56gBmAJ9x33CB -dPq3IxPOiL3MdLh8tv1H07QcRW1kZWJpYW4gQXJjaGl2ZSBTaWduaW5nIEtleYhg -BBMRAgAgBQJGNUMoAhsDBgsJCAcDAgQVAggDBBYCAwECHgECF4AACgkQtbdyAJe7 -O1gTpgCgv5hYIBB7STKXAzNkQzhDzvMrJM4AoMABwK3Q948TDKFKIWu2yDJ9KAjB -iEUEEBECAAYFAkY3M/4ACgkQIWclcBdP7jX7HwCcDWmGKUTkRA+GA3d81BW7lwRz -SPgAmL2SVYU8VK+TpwLzUbWn2EGkBUWIRgQQEQIABgUCRjZfwwAKCRCIAQlKKLyz -45evAJ4qfetNIo1MWcqM8rA6OyN0vkFV/ACg8/5CZw4oLOHuq4+WIbbpHDiV37SI -RgQQEQIABgUCRjZf2QAKCRCTsNWvqJf9AsixAJ9e3zbMLmBxi0dZng3MmiBF0ex6 -qgCcDWGwW16fPG+XN28ewH8k+WSoS0u5Ag0ERjVDKhAIAMPHsF7MCR/bgzmznXVX -V1QuIDHR9NTAGqFiaGMBKK26rHSN8Wds3zPWR/MBvkCknn9MwW2a4B7Vrdz9RAg3 -cUYmSYbHBNDtCTV8b14fNAoc3nsjblgZ+/+0zDvR9ZNv3cUBaCqJ1hlZqZbOWi1X -PTv2r2CRe2A6q9oGj54NmpSIO7EcH2yYcx0GTafY4ZDqZha3kmzLSq1gh2s5kph9 -NyB2pBu31pY3PDPKkxE6+ZAWb6oHZUaKOtr4aXnqLxYzSi6Wv3kS5xXS+ZbCv5lz -/KlTTIlLRm86wvwRnqGqjBGH4knyB+VKtxlR/T+aRQxCMSIICYzpfvM+O8a+hH9Z -+zMAAwYIAMFAqo9dmRfc7BPLhRxb9erSaEhxb05lwiDyzPP6B5hcK8t8S/L4k9Hw -OXoYfnR7/GqUjSj4dYZ5uLlTLOASMpv+5Yq4EmPhuqKWM7MAK0uQXVsxSktswNHE -Hb5c3H8VfQJvpUdelnJdSfqttKvz9Cm1rtPRKylIK/naQJlZ5XxuAcV+PDcWOHq6 -B2uV2aG5CGT2yVM9VjxIkMLBPGXxPjPIKKZky1TTdOdQdGvSyNOu4gd0o+4i07IZ -SXBsHarFPTKGoAZ+YsKRJ3ODAKeKnYXIQQf/OmmHdkKOfRkVDogZyKHVhSNVEOZ4 -NyZwbjXc8FtKGOUYvXcpjuxqzqRckteISQQYEQIACQUCRjVDKgIbDAAKCRC1t3IA -l7s7WNO0AJ0aws9mKLgL0CQKvAKs5UBmpgATXQCfdqJCUVSEsRcihgP8VfOpPeXm -0Vs= -=aGyf --END PGP PUBLIC KEY BLOCK- diff -Nru emdebian-archive-keyring-2.0.4/1804772E.txt emdebian-archive-keyring-2.0.5/1804772E.txt --- emdebian-archive-keyring-2.0.4/1804772E.txt 1970-01-01 01:00:00.0 +0100 +++ emdebian-archive-keyring-2.0.5/1804772E.txt 2015-07-15 17:51:31.0 +
Bug#815400: transition: ros-ros-comm
Control: tags -1 confirmed On 21/02/16 10:09, Jochen Sprickerhof wrote: > Package: release.debian.org > Severity: normal > User: release.debian@packages.debian.org > Usertags: transition > > Hi, > > we want to transition librosconsole to link against log4cxx instead of an > internal print version. librosconsole exports these symbols, so other packages > depend on the choice and we can't simply switch it. We went for a Soname bump > because it's Debian internal anyhow, as upstream declined to add one. > > The new version of ros-ros-comm is in experimental already. > > Ben file: > > title = "ros-ros-comm"; > is_affected = .depends ~ "librosconsole0d" | .depends ~ "librosconsole1d"; > is_good = .depends ~ "librosconsole1d"; > is_bad = .depends ~ "librosconsole0d"; > > We are maintainer of all reverse dependencies and we did test rebuilds already > and have all needed patches prepared. All rdepends are listed here: > > https://release.debian.org/transitions/html/auto-ros-ros-comm.html Go ahead. Cheers, Emilio
Processed: Re: Bug#815400: transition: ros-ros-comm
Processing control commands: > tags -1 confirmed Bug #815400 [release.debian.org] transition: ros-ros-comm Added tag(s) confirmed. -- 815400: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815400 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#792550: marked as done (jessie-pu: package ldap2zone/0.2-5+deb8u1)
Your message dated Sun, 21 Feb 2016 10:31:28 + with message-id <20160221103128.gc6...@betterave.cristau.org> and subject line Re: Bug#792550: jessie-pu: package ldap2zone/0.2-5+deb8u1 has caused the Debian Bug report #792550, regarding jessie-pu: package ldap2zone/0.2-5+deb8u1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 792550: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=792550 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: release.debian.org Severity: normal Tags: jessie User: release.debian@packages.debian.org Usertags: pu Please consider accepting the following jessie-pu for package ldap2zone. * debian/patches: + Add 0009_support-ldapi-uris.patch. Accept ldapi:/// style URIs. (Closes: #792120). This allows people to use ldapi:// style URIs with ldap2zone. Accepting this change in jessie will be highly welcome and is relevant for the Debian Edu development. light+love Mike -- System Information: Debian Release: 8.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) diff -Nru ldap2zone-0.2/debian/changelog ldap2zone-0.2/debian/changelog --- ldap2zone-0.2/debian/changelog 2015-07-16 08:58:42.0 +0200 +++ ldap2zone-0.2/debian/changelog 2015-07-16 09:03:41.0 +0200 @@ -1,3 +1,11 @@ +ldap2zone (0.2-5+deb8u1) jessie-proposed-updates; urgency=medium + + * debian/patches: ++ Add 0009_support-ldapi-uris.patch. Accept ldapi:/// style URIs. (Closes: + #792120). + + -- Mike Gabriel Thu, 16 Jul 2015 09:03:02 +0200 + ldap2zone (0.2-5) unstable; urgency=low * Rewrite revert-broken-zones.patch to use named-checkzone to check diff -Nru ldap2zone-0.2/debian/patches/0009_support-ldapi-uris.patch ldap2zone-0.2/debian/patches/0009_support-ldapi-uris.patch --- ldap2zone-0.2/debian/patches/0009_support-ldapi-uris.patch 1970-01-01 01:00:00.0 +0100 +++ ldap2zone-0.2/debian/patches/0009_support-ldapi-uris.patch 2015-07-16 09:02:16.0 +0200 @@ -0,0 +1,19 @@ +commit 23c0324685aa4db47c5b30e7a16cceb8c3297c33 +Author: Petter Reinholdtsen +Date: Sun Jul 12 09:27:12 2015 +0200 + +Accept ldapi style URLs too (Closes: #792120). + +diff --git a/ldap2bind b/ldap2bind +index 89f44bf..452cfd3 100755 +--- a/ldap2bind b/ldap2bind +@@ -3,7 +3,7 @@ + [ -r /etc/default/ldap2zone ] && . /etc/default/ldap2zone + + case "$LDAP_URI" in +-ldap://*|ldaps://*) ;; ++ldap://*|ldaps://*|ldapi://*) ;; + *) LDAP_URI="ldap://${LDAP_URI}"; ;; + esac + diff -Nru ldap2zone-0.2/debian/patches/series ldap2zone-0.2/debian/patches/series --- ldap2zone-0.2/debian/patches/series 2015-07-16 08:58:42.0 +0200 +++ ldap2zone-0.2/debian/patches/series 2015-07-16 09:02:35.0 +0200 @@ -6,3 +6,4 @@ avoid-signed-unsigned-warning.patch hardening.patch unused-variables.patch +0009_support-ldapi-uris.patch --- End Message --- --- Begin Message --- On Sat, Aug 29, 2015 at 15:58:00 +0200, Julien Cristau wrote: > Control: tag -1 moreinfo > > On Thu, Jul 16, 2015 at 09:09:13 +0200, Mike Gabriel wrote: > > > Please consider accepting the following jessie-pu for package ldap2zone. > > > > * debian/patches: > > + Add 0009_support-ldapi-uris.patch. Accept ldapi:/// style URIs. > > (Closes: > > #792120). > > > > This allows people to use ldapi:// style URIs with ldap2zone. > > > > Accepting this change in jessie will be highly welcome and is relevant > > for the Debian Edu development. > > > It's not clear to me why that would warrant a stable update, please > elaborate on why this is needed now. > No reply since August, closing. Cheers, Julien--- End Message ---
Bug#787962: marked as done (jessie-pu: package pluma/1.8.1+dfsg1-2+deb8u1)
Your message dated Sun, 21 Feb 2016 10:30:46 + with message-id <20160221103046.gb6...@betterave.cristau.org> and subject line Re: Bug#787962: jessie-pu: package pluma/1.8.1+dfsg1-2+deb8u1 has caused the Debian Bug report #787962, regarding jessie-pu: package pluma/1.8.1+dfsg1-2+deb8u1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 787962: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=787962 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: release.debian.org Severity: normal Tags: jessie User: release.debian@packages.debian.org Usertags: pu + * debian/control: ++ Add D (pluma): python-gtksourceview2. (Closes: #785243). Without this dependency, a couple of pluma plugins cannot be activated -- they just get grayed out. Here is the list: - External Tools - Python Console - Quick Open - Snippets It would be good to see this fixed for Debian 8.2. light+love, Mike -- System Information: Debian Release: 8.0 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) diff -Nru pluma-1.8.1+dfsg1/debian/changelog pluma-1.8.1+dfsg1/debian/changelog --- pluma-1.8.1+dfsg1/debian/changelog 2014-05-05 12:50:48.0 +0200 +++ pluma-1.8.1+dfsg1/debian/changelog 2015-06-07 01:19:53.0 +0200 @@ -1,3 +1,10 @@ +pluma (1.8.1+dfsg1-2+deb8u1) jessie-proposed-updates; urgency=medium + + * debian/control: ++ Add D (pluma): python-gtksourceview2. (Closes: #785243). + + -- Mike Gabriel Sun, 07 Jun 2015 01:19:14 +0200 + pluma (1.8.1+dfsg1-2) unstable; urgency=low * debian/rules: diff -Nru pluma-1.8.1+dfsg1/debian/control pluma-1.8.1+dfsg1/debian/control --- pluma-1.8.1+dfsg1/debian/control 2014-04-22 14:40:07.0 +0200 +++ pluma-1.8.1+dfsg1/debian/control 2015-06-07 01:19:04.0 +0200 @@ -38,6 +38,7 @@ pluma-common (= ${source:Version}), mate-desktop-common, iso-codes, + python-gtksourceview2, Recommends: zenity Provides: mate-text-editor Breaks: mate-text-editor (<< 1.5.0) --- End Message --- --- Begin Message --- On Sat, Aug 29, 2015 at 15:45:19 +0200, Julien Cristau wrote: > Control: tag -1 moreinfo > > On Sun, Jun 7, 2015 at 01:30:37 +0200, Mike Gabriel wrote: > > > + * debian/control: > > ++ Add D (pluma): python-gtksourceview2. (Closes: #785243). > > > > Without this dependency, a couple of pluma plugins cannot > > be activated -- they just get grayed out. Here is the list: > > > > - External Tools > > - Python Console > > - Quick Open > > - Snippets > > > > It would be good to see this fixed for Debian 8.2. > > > How essential are those plugins to the use of pluma? > No reply since August, closing. Cheers, Julien--- End Message ---
Bug#785721: marked as done (jessie-pu: package mate-terminal/1.8.1+dfsg1-4+deb8u1)
Your message dated Sun, 21 Feb 2016 10:28:56 + with message-id <20160221102856.gz6...@betterave.cristau.org> and subject line Re: Bug#785721: jessie-pu: package mate-terminal/1.8.1+dfsg1-4+deb8u1 has caused the Debian Bug report #785721, regarding jessie-pu: package mate-terminal/1.8.1+dfsg1-4+deb8u1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 785721: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785721 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: release.debian.org Severity: normal Tags: jessie User: release.debian@packages.debian.org Usertags: pu + [ Martin Wimpress ] + * debian/patches: + + Add 0001_mate-terminal-wrapper.patch. Adds support for double quoted + strings. Adapted from gnome-terminal.wrapper. (Closes: #783000). -> This update for mate-terminal in jessie replaces mate-terminal.wrapper (written in Python) with one adapted from gnome-terminal.wrapper (written in Perl) so that is now supports double quoted commands. This fixes the following downstream (Ubuntu) issue: https://bugs.launchpad.net/ubuntu-mate/+bug/1445198 It may also fix the a similar issue in Debian, though untested. About the language change (Python -> Perl). Martin and I (both of use do a lot of Python development) both stared at the script for half a day and could not find a simple way to support double quotes. So at the end of the day, we chose to switch over to the Perl script (which upstream did, as well). light+love, Mike -- System Information: Debian Release: 8.0 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) diff -Nru mate-terminal-1.8.1+dfsg1/debian/changelog mate-terminal-1.8.1+dfsg1/debian/changelog --- mate-terminal-1.8.1+dfsg1/debian/changelog 2015-01-06 10:19:42.0 +0100 +++ mate-terminal-1.8.1+dfsg1/debian/changelog 2015-05-19 17:08:04.0 +0200 @@ -1,3 +1,12 @@ +mate-terminal (1.8.1+dfsg1-4+deb8u1) jessie-proposed-updates; urgency=medium + + [ Martin Wimpress ] + * debian/patches: + + Add 0001_mate-terminal-wrapper.patch. Adds support for double quoted + strings. Adapted from gnome-terminal.wrapper. (Closes: #783000). + + -- Mike Gabriel Tue, 19 May 2015 01:42:46 +0100 + mate-terminal (1.8.1+dfsg1-4) unstable; urgency=medium * debian/mate-terminal.{postinst,prerm): diff -Nru mate-terminal-1.8.1+dfsg1/debian/patches/0001_mate-terminal-wrapper.patch mate-terminal-1.8.1+dfsg1/debian/patches/0001_mate-terminal-wrapper.patch --- mate-terminal-1.8.1+dfsg1/debian/patches/0001_mate-terminal-wrapper.patch 1970-01-01 01:00:00.0 +0100 +++ mate-terminal-1.8.1+dfsg1/debian/patches/0001_mate-terminal-wrapper.patch 2015-05-19 17:06:40.0 +0200 @@ -0,0 +1,132 @@ +Description: Adds support for double quoted strings. + Add 0001_mate-terminal-wrapper.patch, adapted from gnome-termnal.wrapper, + that adds support for double quoted strings. (Closes LP: #1445198). +Author: Martin Wimpress +Bug-Ubuntu: https://bugs.launchpad.net/bugs/1445198 + +--- mate-terminal-1.8.1+dfsg1.orig/mate-terminal.wrapper mate-terminal-1.8.1+dfsg1/mate-terminal.wrapper +@@ -1,44 +1,81 @@ +-#!/usr/bin/env python ++#!/usr/bin/perl -w + +-import sys +-import os +-import subprocess ++my $login=0; + +-newargs = ['mate-terminal'] +-oldargs = sys.argv[1:] +- +-while True: +-try: +-arg = oldargs.pop(0) +- +-if arg == '-display': +-os.environ['DISPLAY'] = oldargs.pop(0) +-elif arg == '-name': +-newargs.append('--window-with-profile=' + oldargs.pop(0)) +-elif arg == '-n': +-sys.stderr.write('Set an icon in your profile') +-elif arg == '-T' or arg == '-title': +-newargs.append('-t') +-newargs.append(oldargs.pop(0)) +-elif arg == '-ls' or arg == '+ls': +-sys.stderr.write('Login shell not supported. Set in your profile.') +-elif arg == '-geometry': +-newargs.append('--geometry=' + oldargs.pop(0)) +-elif arg == '-fn': +-newargs.append('--font=' + oldargs.pop(0)) +-elif arg == '-fg': +-newargs.append('--foreground=' + oldargs.pop(0)) +-elif arg == '-bg': +-newargs.append('--background=' + oldargs.pop(0)) +-elif arg == '-tn': +-ne
Bug#783708: marked as done (jessie-pu: package youtube-dl/2015.02.28-1)
Your message dated Sun, 21 Feb 2016 10:27:16 + with message-id <20160221102716.gy6...@betterave.cristau.org> and subject line Re: Bug#783708: jessie-pu: package youtube-dl/2015.02.28-1 has caused the Debian Bug report #783708, regarding jessie-pu: package youtube-dl/2015.02.28-1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 783708: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=783708 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: release.debian.org User: release.debian@packages.debian.org Usertags: pu Tags: jessie Severity: normal Dear Release Team, youtube-dl is one of those packages that needs to be frequently kept up to date with upstream in order to be consistently useful. The version currently in jessie (2014.08.05-1+deb8u1) is failing for many Youtube downloads (see for example bug #781180). The package maintainer has uploaded a newer upstream version (2015.02.28-1) to unstable which resolves the problem; please could this be added to jessie-updates so that youtube-dl can work well in jessie before the next point release? The maintainer agrees with this idea (see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=781180#25 ). Thanks very much. -- System Information: Debian Release: 8.0 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) - ONLY AT VFEmail! - Use our Metadata Mitigator to keep your email out of the NSA's hands! $24.95 ONETIME Lifetime accounts with Privacy Features! 15GB disk! No bandwidth quotas! Commercial and Bulk Mail Options! --- End Message --- --- Begin Message --- On Wed, Apr 29, 2015 at 19:49:51 +0100, Adam D. Barratt wrote: > On Wed, 2015-04-29 at 17:33 +, transylvania wrote: > > Adam D. Barratt: > > > If someone provides a source debdiff for a proposed package, which has > > > been tested on Jessie, then we can certainly look at that. > > > > Hello Adam, > > > > Thanks for your reply. I can confirm that the 2015.02.28-1 package > > installs and works on jessie. > > > > It's a new upstream version and so the source debdiff is quite large, > > about 2.4MB; please can you confirm that it's OK to attach that here? > > You can, although it won't reach the mailing list at that size. > > Without looking at the diff, it often helps to filter the debdiff to > exclude documentation, automatically generated files, test suite changes > and so on. If you do so, please mention what you've filtered. > > Depending on how frequently the package changes and how large future > changes are likely to be, it may be that maintaining the package via > -updates doesn't make sense, but we'll see. > No followup since last April, closing. Cheers, Julien--- End Message ---
Processed: tagging 784373
Processing commands for cont...@bugs.debian.org: > tags 784373 - moreinfo Bug #784373 [release.debian.org] jessie-pu: package ceph/0.80.11-1 (pre approval) Removed tag(s) moreinfo. > thanks Stopping processing here. Please contact me if you need assistance. -- 784373: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784373 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#782190: marked as done (pu: package nginx/1.6.3-1)
Your message dated Sun, 21 Feb 2016 10:25:57 + with message-id <20160221102557.gx6...@betterave.cristau.org> and subject line Re: Bug#782190: pre-approve: nginx/1.6.3-1 has caused the Debian Bug report #782190, regarding pu: package nginx/1.6.3-1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 782190: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=782190 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: release.debian.org Severity: normal Hello, I have prepared an upload for nginx (1.6.3-1) and I'd like to request a pre-approval for jessie. 1.6.3 is the latest upstream stable bugfix release including 6 bug fixes[0]. One of them fixes a tcp nodelay issue with spdy that effectively makes spdy unusuitable for production use. Upstream already maintains a stable branch and has proven that it does it well, backporting only what's absolutely needed. I believe it is better for debian and nginx maintainers to follow suit and package 1.6.3 for jessie. I am attaching a debdiff or the proposed upload. (I'll also file a bug report for packaging 1.6.3 and include it the changelog). Upstream changelog: *) Feature: now the "tcp_nodelay" directive works with SPDY connections. *) Bugfix: in error handling. Thanks to Yichun Zhang and Daniil Bondarev. *) Bugfix: alerts "header already sent" appeared in logs if the "post_action" directive was used; the bug had appeared in 1.5.4. *) Bugfix: alerts "sem_post() failed" might appear in logs. *) Bugfix: in hash table handling. Thanks to Chris West. *) Bugfix: in integer overflow handling. Thanks to Régis Leroy. [0] tcp_nodelay is marked as a feature, but it's actually an important bugfix diff -Nru nginx-1.6.2/auto/unix nginx-1.6.3/auto/unix --- nginx-1.6.2/auto/unix 2014-09-16 15:23:19.0 +0300 +++ nginx-1.6.3/auto/unix 2015-04-07 18:58:37.0 +0300 @@ -489,6 +489,7 @@ ngx_type="time_t"; . auto/types/sizeof ngx_param=NGX_TIME_T_SIZE; ngx_value=$ngx_size; . auto/types/value ngx_param=NGX_TIME_T_LEN; ngx_value=$ngx_max_len; . auto/types/value +ngx_param=NGX_MAX_TIME_T_VALUE; ngx_value=$ngx_max_value; . auto/types/value # syscalls, libc calls and some features diff -Nru nginx-1.6.2/CHANGES nginx-1.6.3/CHANGES --- nginx-1.6.2/CHANGES 2014-09-16 15:23:24.0 +0300 +++ nginx-1.6.3/CHANGES 2015-04-07 18:58:53.0 +0300 @@ -1,4 +1,23 @@ +Changes with nginx 1.6.3 07 Apr 2015 + +*) Feature: now the "tcp_nodelay" directive works with SPDY connections. + +*) Bugfix: in error handling. + Thanks to Yichun Zhang and Daniil Bondarev. + +*) Bugfix: alerts "header already sent" appeared in logs if the + "post_action" directive was used; the bug had appeared in 1.5.4. + +*) Bugfix: alerts "sem_post() failed" might appear in logs. + +*) Bugfix: in hash table handling. + Thanks to Chris West. + +*) Bugfix: in integer overflow handling. + Thanks to Régis Leroy. + + Changes with nginx 1.6.2 16 Sep 2014 *) Security: it was possible to reuse SSL sessions in unrelated contexts diff -Nru nginx-1.6.2/CHANGES.ru nginx-1.6.3/CHANGES.ru --- nginx-1.6.2/CHANGES.ru 2014-09-16 15:23:22.0 +0300 +++ nginx-1.6.3/CHANGES.ru 2015-04-07 18:58:47.0 +0300 @@ -1,4 +1,24 @@ +Изменения в nginx 1.6.3 07.04.2015 + +*) Добавление: теперь директива tcp_nodelay работает для + SPDY-соединений. + +*) Исправление: в обработке ошибок. + Спасибо Yichun Zhang и Даниилу Бондареву. + +*) Исправление: при использовании директивы post_action в лог писались + сообщения "header already sent"; ошибка появилась в nginx 1.5.4. + +*) Исправление: в лог могли писаться сообщения "sem_post() failed". + +*) Исправление: в обработке хэш-таблиц. + Спасибо Chris West. + +*) Исправление: в обработке целочисленных переполнений. + Спасибо Régis Leroy. + + Изменения в nginx 1.6.2 16.09.2014 *) Безопасность: при использовании общего для нескольких блоков server diff -Nru nginx-1.6.2/debian/changelog nginx-1.6.3/debian/changelog --- nginx-1.6.2/debian/changelog2014-12-01 13:12:00.0 +0200 +++ nginx-1.6.3/debian/changelog2015-04-09 11:00:03.0 +0300 @@ -1,3 +1,11 @@ +nginx (1.6.3-1) unstable; urgency=medium + + [ Christos Trochalakis ] + * New upstream release. +Fixes tcp nodelay issue in spdy module. + + -- C
Bug#785047: vsftpd/3.0.2-17+deb8u1
Am Sonntag, den 21.02.2016, 09:50 +0100 schrieb John Paul Adrian Glaubitz: > On 02/20/2016 11:09 PM, Julien Cristau wrote: > > Doesn't look like that's happening. Closing. > > Sorry, I completely missed the pu updates Joerg prepared. That was > not > done intentionally, but it was rather somewhere lost in > communication. > > I'd be happy to take carre of vsftpd. > > @Joerg: Could you re-upload the package to mentors? > done.. [1] > Thanks, > Adrian > CU Jörg [1] http://mentors.debian.net/debian/pool/main/v/vsftpd/vsftpd_3.0.2-17+deb8u1.dsc -- New: GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB 30EE 09F8 9F3C 8CA1 D25D GPG key (long) : 09F89F3C8CA1D25D GPG Key: 8CA1D25D CAcert Key S/N : 0E:D4:56 Old pgp Key: BE581B6E (revoked since 2014-12-31). Jörg Frings-Fürst D-54538 Bausendorf Threema: SYR8SJXB IRC: j_...@freenode.net j_...@oftc.net My wish list: - Please send me a picture from the nature at your home. signature.asc Description: This is a digitally signed message part
Bug#798780: release.debian.org: Please let playonlinux migrate to testing
Le 20/02/2016 22:53, Julien Cristau a écrit : > Seems to be in testing now, closing. > > Cheers, > Julien Hello Julien, Indeed playonlinux migrated to testing, thanks to Markus Koschany who "removed dependency on wine32|wine32-development again to ensure the package can migrate to testing." in 4.2.9-2. Ideally, this would only be temporary as playonlinux should really depend on wine32|wine32-development. Do you think we could find a solution to restore the dependency and let playonlinux migrate to testing ? Cheers, Bertrand signature.asc Description: OpenPGP digital signature
Bug#815400: transition: ros-ros-comm
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition Hi, we want to transition librosconsole to link against log4cxx instead of an internal print version. librosconsole exports these symbols, so other packages depend on the choice and we can't simply switch it. We went for a Soname bump because it's Debian internal anyhow, as upstream declined to add one. The new version of ros-ros-comm is in experimental already. Ben file: title = "ros-ros-comm"; is_affected = .depends ~ "librosconsole0d" | .depends ~ "librosconsole1d"; is_good = .depends ~ "librosconsole1d"; is_bad = .depends ~ "librosconsole0d"; We are maintainer of all reverse dependencies and we did test rebuilds already and have all needed patches prepared. All rdepends are listed here: https://release.debian.org/transitions/html/auto-ros-ros-comm.html -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.3.0-1-amd64 (SMP w/12 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init)
Bug#785047: vsftpd/3.0.2-17+deb8u1
On 02/20/2016 11:09 PM, Julien Cristau wrote: > Doesn't look like that's happening. Closing. Sorry, I completely missed the pu updates Joerg prepared. That was not done intentionally, but it was rather somewhere lost in communication. I'd be happy to take carre of vsftpd. @Joerg: Could you re-upload the package to mentors? Thanks, Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Bug#809319: jessie-pu: package sane-backends/1.0.24-8
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 02/21/2016 07:38 AM, Jörg Frings-Fürst wrote: > I have no upload rights. So I ask my sponsor to upload it. But he > has a lot of work in his job. > > It's fine if someone can upload it. The package is on mentors[1]. I'm taking care of it right now. No worries. Just got up. It's Sunday after all ;). Adrian - -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBCAAGBQJWyXb6AAoJEHQmOzf1tfkTV9gP/3aECdvRBz3vXvbsLxygbfzG 57NEnrEY0eREiEKWZ1WqUEbyztVZjihqWxrv45S4uooqMdIFqKHIhbTDHaN4rfW8 zBFx/PtYUagc/yhyTEj9VxyLYBz6HLue5BWEfbSqe8AhzQf1xc2bdNv0lfbqbX8X iJJcAyBxRI1W9hotRDzl8EsYoVhNlsaI4jpNeQSwt92aDyM4kUhRTL5yOdD2khTk dWXcoS1bR3x9V1cfEhZ1bZMf7WXRFWHzOd29nB9DNhV2Dx5u4fC9ak3binVHThyV UL+KYi9dQwuB943RXb+6MljsNzTmrZBU64d8980fNsft7T4UZk8UeGriW9vsPCU4 GsYsq/vXDGPl1DLvc5BHUXBnTzhMUs0wnRT/KLgcn28HS1ZsFfcYk0WrcwFWZ636 ya1nT6N9zf3sZ9GEhJG/YImCTuE08fQDtEDjSjmonBUjhwL8b8CdX2n+tIbr+bvn qpOsiyCk9xbzkMxVoHppa22fQBwuKvhClE7StZjfsxCPeDnK02UvnAnGm7fMws+B uBF4xTKUp4OX8Ttl6k3xpTeezHMqN6rLT+dRQse5L4fSTzv6FUxCgAtSP1knD6C9 uw10ZogJpBoIcuR2sMYbZkwXxER71uVIp9WU6kJ9Rt6k86VdQMv066hHS1OyGava 9pQyMSrowbQlETt9djFL =uejZ -END PGP SIGNATURE-
Processed: aces3: FTBFS on powerpc
Processing commands for cont...@bugs.debian.org: > found 813722 openmpi/1.10.2-5 Bug #813722 [src:openmpi] aces3: FTBFS on powerpc Marked as found in versions openmpi/1.10.2-5. > unblock 813128 by 813722 Bug #813128 [release.debian.org] transition: openmpi 813128 was blocked by: 813724 813725 813799 813498 813814 813951 813722 813128 was not blocking any bugs. Removed blocking bug(s) of 813128: 813722 > merge 813722 814183 Bug #813722 [src:openmpi] aces3: FTBFS on powerpc Bug #813722 [src:openmpi] aces3: FTBFS on powerpc Added tag(s) sid and stretch. Bug #814183 [src:openmpi] openmpi 1.10.2 is broken on powerpc Merged 813722 814183 > thanks Stopping processing here. Please contact me if you need assistance. -- 813128: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813128 813722: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813722 814183: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814183 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems