Re: Your libxmlezout upload 1.06.1-7
Jonathan Wiltshire j...@debian.org a écrit : Hi, Hi, Your libxmlezout upload yesterday included an unco-ordinated library transition (SONAME is bumped from 1 to 2). Sorry for that. In 'Bits from the release team' or similar on: - 2013-12-26 - 2014-05-01 - 2014-07-05 - 2014-09-26 it was announced, reminded, and reminded again that the window for transitions was to close on 5th September 2014. Besides being unco-ordinated, you also missed that window. You have a reverse dependency from liblog4ada. Even if I am a DM for some time now, I don't fully master all the Debian arcane. I was polishing my liblog4ada packaging. In this case, the transition is almost self-contained since you maintain the only reverse-dependency, and it's not in testing anyway. It also appears that this should have happened when the new upstream release was uploaded, and not in -7. For this reason, I will schedule the transition as normal[1]. This is an exception, and normally we would ask you to revert your changes. Thanks for the transition schedule. I was catch by surprise that libxmlezout came so fast out of NEW, liblog4ada should follow very soon, also with a bump in SONAME because of gnat-4.9 compilation instead of gnat-4.6. (The reason we get uppity about unco-ordinated transitions is that even if it's self-contained, we generally have to Do Things, including teaching britney about the changes.) Thanks for the explanations. xavier 1: no precedent inferred, before anyone else is tempted -- Jonathan Wiltshire j...@debian.org Debian Developer http://people.debian.org/~jmw 4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC 74C3 5394 479D D352 4C51 directhex i have six years of solaris sysadmin experience, from 8-10. i am well qualified to say it is made from bonghits layered on top of bonghits This message was sent using the webmail platform from IN2P3 Computing Center -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141005102953.159336yvv7tio...@webmail.in2p3.fr
Re: Your libxmlezout upload 1.06.1-7
Jonathan Wiltshire j...@debian.org a écrit : On 2014-10-04 19:39, Jonathan Wiltshire wrote: You have a reverse dependency from liblog4ada. For this reason, I will schedule the transition as normal[1]. liblog4ada build-depends on libxmlezout2-dev, and will therefore be broken by this in sid and require a source upload. Can a two step move be possible : - an upload of 1.2-5 depending on libxmlezout2 and libxmlezout3-dev without soname change in unstable - an upload of 1.3-1 in new in parallel Thanks in advance for your help, advices and time, xavier This message was sent using the webmail platform from IN2P3 Computing Center -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141005103628.17061h82iwx54...@webmail.in2p3.fr
Increasing the testing migration delay
Hi, tl;dr: see how to request further down this mail As announced[1] we have set a mandatory 10-day delay for packages wishing to migrate from unstable to testing. Only members of the release team can override this, and will do so on request for security fixes and other severe issues. If you have a package currently in unstable with urgency!=low, and it hasn't yet migrated, we have preserved its planned migration time so you do not need to request an override. How to request an override == Please use reportbug to file an 'unblock' bug against release.debian.org. You need to provide the package details, version, and a one-line justification (including bug numbers). You don't need to provide a debdiff until the main freeze starts. Don't send mail to debian-release@lists.debian.org or poke us on IRC. These requests are difficult to track and we don't want anybody to be left wondering. You only need to do this if you want the 10-day age period to be reduced. If 10 days is suitable, you don't need to do anything else (provided your package migrates naturally before 5th November 2014). 1: 1411731161.1994.17.ca...@jacala.jungle.funky-badger.org For the release team: -- Jonathan Wiltshire j...@debian.org Debian Developer http://people.debian.org/~jmw 4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC 74C3 5394 479D D352 4C51 signature.asc Description: Digital signature
Re: Your libxmlezout upload 1.06.1-7
On Sun, Oct 05, 2014 at 10:29:53AM +0200, Xavier Grave wrote: Jonathan Wiltshire j...@debian.org a écrit : Thanks for the transition schedule. I was catch by surprise that libxmlezout came so fast out of NEW, liblog4ada should follow very soon, also with a bump in SONAME because of gnat-4.9 compilation instead of gnat-4.6. Ok, that should be fine since liblog4ada has no reverse dependencies, so it won't be too disruptive. liblog4ada build-depends on libxmlezout2-dev, and will therefore be broken by this in sid and require a source upload. Can a two step move be possible : - an upload of 1.2-5 depending on libxmlezout2 and libxmlezout3-dev without soname change in unstable - an upload of 1.3-1 in new in parallel Yes if you want, but liblog4ada still won't migrate to testing until 1.3-1 has cleared NEW. It would clean up libxmlezout though. In that case, an upload of 1.2-5 as soon as possible would be appreciated. Thanks in advance for your help, advices and time, xavier Thanks for your quick attention. -- Jonathan Wiltshire j...@debian.org Debian Developer http://people.debian.org/~jmw 4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC 74C3 5394 479D D352 4C51 signature.asc Description: Digital signature
Bug#763297: marked as done (transition: libsystemd)
Your message dated Sun, 5 Oct 2014 10:54:11 +0100 with message-id 20141005095411.gc22...@lupin.home.powdarrmonkey.net and subject line Re: Bug#763297: transition: libsystemd has caused the Debian Bug report #763297, regarding transition: libsystemd 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.) -- 763297: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=763297 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition Hi, in systemd v209, the various libsystemd-* libraries were merged into a single libsystemd0 library. We still build the old libraries to not break existing packages, though. The libsystemd-(daemon|journal|login|id128)-dev package now point to -lsystemd0, i.e. packages once rebuilt will link against libsystemd0 not the old library names and we want all packages to link against the new libsysemd0 library so we can eventually drop the compat library packages. Please schedule a round of binNMUs so affected packages will be rebuilt against libsystemd0. Afaics this doesn't qualify as library transition but it's probably easiest to find affected packages via a transition tracker. The ben file for it should look something like this: title = libsystemd; is_affected = .depends ~ libsystemd-(daemon|journal|login|id128-)0, | .depends ~ libsystemd0; is_good = .depends ~ libsystemd0; is_bad = .depends ~ libsystemd-(daemon|journal|login|id128-)0,; The binNMU could be something like Rebuild against libsystemd0 Thanks for considering, Michael -- 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.16-2-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 ---End Message--- ---BeginMessage--- On Mon, Sep 29, 2014 at 12:23:32AM +0200, Michael Biebl wrote: in systemd v209, the various libsystemd-* libraries were merged into a single libsystemd0 library. We still build the old libraries to not break existing packages, though. The libsystemd-(daemon|journal|login|id128)-dev package now point to -lsystemd0, i.e. packages once rebuilt will link against libsystemd0 not the old library names and we want all packages to link against the new libsysemd0 library so we can eventually drop the compat library packages. This looks to be complete, so you can withdraw the old libraries now and ask ftp-masters to decruft them so systemd can migrate. Thanks, -- Jonathan Wiltshire j...@debian.org Debian Developer http://people.debian.org/~jmw 4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC 74C3 5394 479D D352 4C51 signature.asc Description: Digital signature ---End Message---
Libvirt testing migration [was: Increasing the testing migration delay]
Hi, On Sun, Oct 05, 2014 at 10:27:18AM +0100, Jonathan Wiltshire wrote: Hi, tl;dr: see how to request further down this mail As announced[1] we have set a mandatory 10-day delay for packages wishing to migrate from unstable to testing. Only members of the release team can override this, and will do so on request for security fixes and other severe issues. If you have a package currently in unstable with urgency!=low, and it hasn't yet migrated, we have preserved its planned migration time so you do not need to request an override. I was hoping to see libvirt 1.2.8 migrate to testing (using the 5 day delay) since it fixes a CVE and then upload 1.2.9 to unstable (which I hope to get into Jessie). But 1.2.8 is blocked on systemd due to: Not touching package due to block-udeb request by freeze (contact debian-release if update is needed) Are there any plans to unblock systemd anytime soon? If not I'd upload 1.2.9 to sid. Cheers, -- Guido -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141005101707.ga2...@bogon.m.sigxcpu.org
Re: Libvirt testing migration [was: Increasing the testing migration delay]
Hi, Guido Günther wrote (05 Oct 2014 10:17:07 GMT) : Are there any plans to unblock systemd anytime soon? The udeb block was lifted a few hours ago, as announced by kibi. Cheers, -- intrigeri -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/858ukuer7h@boum.org
RFC: ntfs-3g/2014.2.15AR.2-1 upload
Hi Release Team, I ask for comments and/or permission to upload ntfs-3g to unstable. I know that KiBi lifted the udeb freeze but I'd like to be sure. The package is available for review[1], the upstream changes[2] show that it's a new stable patchlevel relese. The changes list also included here: - fixed readdir I/O error on very long file names in Solaris (Erik Larsson) - fixed $Bitmap size in index in ntfsresize - fixed inserting a new ACL after they have been wiped out by chkdsk - returned success from ntfsprogs utilities with options --version and the like - allowed group mapping of a few well-known SIDs - ignored chmod/chown/setfacl when Windows inheritance is applied - displayed the parent directory of selected files in usermap - decoded the GENERIC_ALL flag in secaudit - improved the conditions for double inheritance of an ACE - improved the ownership definition when user mapping fails - decoded more well-known and generic SIDs in secaudit - recognized interactive users as any user - fixed checking static groups against process owner - fixed ignoring the umask mount option when permissions are used - fixed getting inherited security ids from cache - defined the configure option --enable-quarantined for non functional utilities - included ntfsfallocate in the quarantined ntfsprogs - showed Windows ownership in verbose situations of secaudit - disabled the default user mapping when Windows inheritance is used - fixed a wrong function header in usermap - fixed processing umask when Posix ACLs are compiled in but not enabled - fixed checking permissions when Posix ACLs are compiled in but not enabled - added manuals for ntfsdecrypt, ntfswipe, ntfstruncate and ntfsfallocate - upgraded fuse-lite to support simple ioctls - implemented FITRIM (fstrim) ioctl (Richard W.M. Jones) - reengineered the compression algorithm (Eric Biggers) - disabled option remove_hiberfile on read-only mounts - developped an option for faster ntfswipe (michael) It would be nice to have it for Jessie. Thanks, Laszlo/GCS [1] dget -x http://www.barcikacomp.hu/gcs/ntfs-3g_2014.2.15AR.2-1.dsc [2] http://jp-andre.pagesperso-orange.fr/changelog.html -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/CAKjSHr1K8zsBcSS+MDieGUWE=o7+efdjebvtbudhwukf5cf...@mail.gmail.com
Bug#754988: Bug#763360: libjpeg-turbo is hijacking binaries from other source packages
On Sat, Oct 4, 2014 at 20:48:31 +0200, Bill Allombert wrote: On Fri, Oct 03, 2014 at 03:03:09PM +0200, Andreas Barth wrote: I hope we could leave it as that for the upload - nobody has a time machine to undo the upload, but we could try to make it better now and discuss where we should go. Ok, let's focus on libjpeg-progs, since I do not think there is a disagreement about it. What would you propose as a course of action that allow either libjpeg8 or lijpeg9 to provide libjpeg-progs with minimal disruption to the archive ? libjpeg8 can start building an epoched libjpeg-progs. Cheers, Julien signature.asc Description: Digital signature
Re: RFC: ntfs-3g/2014.2.15AR.2-1 upload
Hi, On 2014-10-05 12:10, László Böszörményi wrote: I ask for comments and/or permission to upload ntfs-3g to unstable. I know that KiBi lifted the udeb freeze but I'd like to be sure. Yes, you can go ahead with this now. Thanks, -- Jonathan Wiltshire j...@debian.org Debian Developer http://people.debian.org/~jmw 4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC 74C3 5394 479D D352 4C51 directhex i have six years of solaris sysadmin experience, from 8-10. i am well qualified to say it is made from bonghits layered on top of bonghits -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/ac41c2c460802ef3c7176ba7440d0...@hogwarts.powdarrmonkey.net
Bug#763386: wheezy-pu: package keyutils/1.5.5-3+deb7u1
Control: tag -1 + pending On 2014-09-29 20:42, Christian Kastner wrote: keyutils in stable currently provides libkeyutils1, a library package of Priority: standard. As a user discovered in #757740, this package failed to install on a device with only 64MiB memory as this was insufficient memory to uncompress the .deb compressed with xz and -z9. Flagged for acceptance. -- Jonathan Wiltshire j...@debian.org Debian Developer http://people.debian.org/~jmw 4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC 74C3 5394 479D D352 4C51 directhex i have six years of solaris sysadmin experience, from 8-10. i am well qualified to say it is made from bonghits layered on top of bonghits -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/2d7c2a022f80f0fedd02359151a31...@hogwarts.powdarrmonkey.net
Processed: Re: Bug#763386: wheezy-pu: package keyutils/1.5.5-3+deb7u1
Processing control commands: tag -1 + pending Bug #763386 [release.debian.org] wheezy-pu: package keyutils/1.5.5-3+deb7u1 Added tag(s) pending. -- 763386: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=763386 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/handler.s.b.141252422112192.transcr...@bugs.debian.org
Processed: Re: Bug#763386: wheezy-pu: package keyutils/1.5.5-3+deb7u1
Processing control commands: tag -1 + pending Bug #763386 [release.debian.org] wheezy-pu: package keyutils/1.5.5-3+deb7u1 Ignoring request to alter tags of bug #763386 to the same tags previously set -- 763386: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=763386 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/handler.s.b763386.141252422112201.transcr...@bugs.debian.org
NEW changes in stable-new
Processing changes file: keyutils_1.5.5-3+deb7u1_amd64.changes ACCEPT -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/e1xaouc-0008sg...@franck.debian.org
Bug#748535: Bug#764098: gst-plugins-bad0.10: build-depends on libgnutls-dev
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
[ About the benefit of requiring a sourceful upload of reverse b-d,
instead of providing the libgnutls-dev by the accurate package. ]
Le 05/10/2014 12:35, Andreas Metzler a écrit :
On 2014-10-05 David Prévot taf...@debian.org wrote:
On Sun, Oct 05, 2014 at 04:11:44PM +0200, Andreas Metzler wrote:
GnuTLS 2 and 3 are not completely API compatible. And given that this
transition is basically finished […], I would like to keep the small
benefit of having this incompatibility reflected in the package name.
Indeed, the benefit seems rather small compared to making all further
gnutls transition more painful by forcing all of its reverse b-d to
provide a sourceful upload instead of triggering a simple binNMU when
possible.
I think there is small misunderstanding: The fact that we now have
libgnutls28-dev does not mean that we will have matching versioned
development packages (libgnutls{30,31,31,etc}-dev) for the library
package (libgnutls{30,31,31,etc}) in later versions. There is no
reason why future gnutls transition should be hurt by the current naming of
the gnutl development package.
I don’t deny there is a misunderstanding, but I’m not sure how small it
is. I don’t get either the benefit of having “28” somewhere in the name
to make it clear that the package is about GnuTLS 3 (or any later version).
Anyway, documenting those concerns in the transition bug report since
they don’t seem to have been raised before.
Regards
David
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
iQEcBAEBCAAGBQJUMYe9AAoJEAWMHPlE9r08yQ0IAI7XDrlXTpzVmXl8gP/6FqAu
nUfgaCPvfOLxPzK9VSRswLLPfzVmvQ3cWko7sEnA4lqD6Q3AhdETVEOwCXPu/qqT
polrrU7btBBkoG7/2LL2g0nxMXOm6zof7MHsW590mgXS6e5e/GGUlF7WqKipasBf
ZytxJyIHHeO1p1XZkQwfgTgDmTgdBSDIKrtseDYk+ElDkNWVM1ShP1gU2y/cCIVI
tWJEUgKd6vyd6p9SrLpVZ2ymKLrhs/8QsoZsBzSCvQ63MgxV9kcbWJNN8UE0OOeJ
xqGdcGT9QPxHSggHuBiaa+XfmGpZtomqGCV2gjqt3TPp2d0UF5Yv2U8WlDzpebw=
=Qplw
-END PGP SIGNATURE-
--
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/543187be.90...@debian.org
grib-api 1.12.3-1
Hello, I have prepared a new upload of grib-api, version 1.12.3-1. This is the main bit of the changelog: * New upstream version - grib_api has an official soname now! It means that it now builds just a standard libgrib-api0, supported by upstream, and we'd be done with having the library full version in the soname. However, I'm kind of late. Still, I've rebuilt all the reverse build dependencies with it[1], and they build fine with it. This means that the only transition needed would just be a round of binNMUs. It would be nice to have grib_api soname sanity in jessie, but I'm not uploading it without your informed and enthousiastic consent. Please let me know. The new package is on master here: http://anonscm.debian.org/cgit/collab-maint/gribapi.git [1] This is the list as far as I understand: Maintained by Alastair McKinstry: cdo, emoslib, flexpart, magics++, metview, pygrib Maintained by Youhei SASAKI: ruby-grib Enrico -- GPG key: 4096R/E7AD5568 2009-05-08 Enrico Zini enr...@enricozini.org signature.asc Description: Digital signature
Re: grib-api 1.12.3-1
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 05/10/2014 19:19, Enrico Zini wrote: Hello, I have prepared a new upload of grib-api, version 1.12.3-1. This is the main bit of the changelog: * New upstream version - grib_api has an official soname now! It means that it now builds just a standard libgrib-api0, supported by upstream, and we'd be done with having the library full version in the soname. However, I'm kind of late. Still, I've rebuilt all the reverse build dependencies with it[1], and they build fine with it. This means that the only transition needed would just be a round of binNMUs. It would be nice to have grib_api soname sanity in jessie, but I'm not uploading it without your informed and enthousiastic consent. I'm enthusiastically consenting to this, if the release-masters let it go through. It would be good to have a standard SONAME for grib-api in Jessie. Please let me know. The new package is on master here: http://anonscm.debian.org/cgit/collab-maint/gribapi.git [1] This is the list as far as I understand: Maintained by Alastair McKinstry: cdo, emoslib, flexpart, magics++, metview, pygrib Maintained by Youhei SASAKI: ruby-grib Enrico regards Alastair - -- Alastair McKinstry, alast...@sceal.ie, mckins...@debian.org, https://diaspora.sceal.ie/u/amckinstry A decent provision for the poor is the true test of civilization. ~Samuel Johnson, Boswell: Life of Johnson -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJUMZBbAAoJEN9LdrZRJ3Qs1EUP/ibICNF6btIq3FqWsNlWWpAp Z86wSOES70NXx/g7IsFzhTL3+mlobMWNY20j8SxqHOXZwJa81cP7cV82XpNdZxYp oOaDZEmfXqIzuhWWun5emoFpzsKXRJZ80wXqCzf8g0s3otc1X10AgU2KIM1BGVFS l9n/9hZwzF5ApRgYUn95Kw8qFQWiJelUELUUb652+MQsgOAfQ1I6AYUpKaFKf4EH ZLiWMcY46VBI/4O97Zwn/JZbowoj+O9ygBIdvtYRpclXLHmHciyrn/Pndkl99kir 4SKnSyeGr6vPF0sLfTIF5e9szKEYBiY+2g/JxxAQCBWW3qKFHRSFiRQ2etHbyHId Ep6xmNApDLJu7bwWTQ+HiKPqZFOcFY1XKWv9JsyeZB0O+3JyCGE9kp9PaoXazspB vcie48jtfJZ+XjB9ycnsgYKb/iC48CqiKkR9DIg+Ojxn7YIpHjhsaWeeqzafJl7K GoEVwJ82JEuGDOSeJtTBXMPOLteeJpMydfDCizZjBEc2MRfR5wgc5bw9mqHcmcsh WxD+gFELKpSRTMvMKEy1fS8Q2f/ZyGnPWoVzCsq+gdTPlKVrtfeJcsTzqZXpq70g 1Gn/KK41gcBQyV3N+ZLm5uD+Hc6Uqoe5KHLFARIBiwc0haM9RnWbm3IsBgezkj1H KjSoCagCZLiiEiOxrbzZ =tH4k -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/5431905b.6000...@debian.org
Re: Bug#763148: Prevent migration to jessie
Hi, On 05.10.2014 03:26, Michael Gilbert wrote: On Fri, Oct 3, 2014 at 1:44 PM, Andreas Cadhalpun wrote: But I don't think that the mere possibility of such problems is a sufficient reason to disregard Debian policy, which clearly states that embedded code copies should not be used. This is especially the case, if it prevents the properly packaged library and the command line tools from being part of the stable release. That may be worth considering post-jessie, but an unavoidable issue right now is that ffmpeg arrived too late to make it into this release cycle. Sorry, I don't understand what you're saying here: The whole discussion we are having currently is about letting FFmpeg migrate to jessie! So this is no 'unavoidable issue'. But as you seem to be willing to consider this in principle, I think now the time has come for the release team to make an official decision: Is FFmpeg allowed to migrate to testing, so that chromium can use it? Or is chromium allowed to continue to use it's embedded copy? Best regards, Andreas -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/54319957.6020...@googlemail.com
Re: Bug#763148: Prevent migration to jessie
On 05/10/14 21:17, Andreas Cadhalpun wrote: Hi, On 05.10.2014 03:26, Michael Gilbert wrote: On Fri, Oct 3, 2014 at 1:44 PM, Andreas Cadhalpun wrote: But I don't think that the mere possibility of such problems is a sufficient reason to disregard Debian policy, which clearly states that embedded code copies should not be used. This is especially the case, if it prevents the properly packaged library and the command line tools from being part of the stable release. That may be worth considering post-jessie, but an unavoidable issue right now is that ffmpeg arrived too late to make it into this release cycle. Sorry, I don't understand what you're saying here: The whole discussion we are having currently is about letting FFmpeg migrate to jessie! So this is no 'unavoidable issue'. But as you seem to be willing to consider this in principle, I think now the time has come for the release team to make an official decision: Is FFmpeg allowed to migrate to testing, so that chromium can use it? Or is chromium allowed to continue to use it's embedded copy? We won't let ffmpeg into Jessie. Ask again after Jessie is released. And please stop asking the same question over and over again. Emilio -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/54319b87.9020...@debian.org
Re: Bug#763148: Prevent migration to jessie
Andreas Cadhalpun andreas.cadhal...@googlemail.com (2014-10-05): The whole discussion we are having currently is about letting FFmpeg migrate to jessie! So this is no 'unavoidable issue'. But as you seem to be willing to consider this in principle, I think now the time has come for the release team to make an official decision: Is FFmpeg allowed to migrate to testing, so that chromium can use it? Or is chromium allowed to continue to use it's embedded copy? I'm not sure why one would think the decision still needs to be made. Mraw, KiBi. signature.asc Description: Digital signature
Bug#758492: RM: lcms/1.19.dfsg2-1.5
control: tag -1 -moreinfo control: unblock -1 by 740495 control: unblock -1 by 757384 On Mon, Aug 18, 2014 at 1:11 AM, Niels Thykier wrote: Are we (really) ready for this? Removal of lcms in testing would break several packages including gimp and libmagickcore-dev[1] lcms no longer has any reverse dependencies or reverse build dependencies in testing, so it is ready to be removed now. Best wishes, Mike -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/CANTw=MOetUfo_GfQF_OcVkRjv9dMY-Q=krNS=dyxbeheenk...@mail.gmail.com
Bug#758492: RM: lcms/1.19.dfsg2-1.5
On 05/10/14 21:52, Michael Gilbert wrote: control: tag -1 -moreinfo control: unblock -1 by 740495 control: unblock -1 by 757384 On Mon, Aug 18, 2014 at 1:11 AM, Niels Thykier wrote: Are we (really) ready for this? Removal of lcms in testing would break several packages including gimp and libmagickcore-dev[1] lcms no longer has any reverse dependencies or reverse build dependencies in testing, so it is ready to be removed now. Added a hint, let's see how it goes. Emilio -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/5431a576.2010...@debian.org
Why does libtecla not propagate to testing (Was: libtecla is marked for autoremoval from testing)
Hi, the bug mentioned below was fixed on Mon, 08 Sep 2014 09:18:09 +0200 but the package did not migrated to testing. In fact other architectures do not seem to build the package since the testing migration page https://qa.debian.org/excuses.php?package=libtecla shows a lot of missings. I suspect that there was some manual hold or something like this on the package doe to the nature of bug #760790. Can you please check this problem since I have no idea what I can do except for fixing the bug. Thanks Andreas. On Sun, Oct 05, 2014 at 04:39:04AM +, Debian testing autoremoval watch wrote: libtecla 1.6.1-5 is marked for autoremoval from testing on 2014-11-04 It is affected by these RC bugs: 760790: libtecla: FTBFS: fork bombs the buildd ___ Debian-med-packaging mailing list debian-med-packag...@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-med-packaging -- http://fam-tille.de -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141005201256.gb30...@an3as.eu
Processed: Re: Bug#758492: RM: lcms/1.19.dfsg2-1.5
Processing control commands: tag -1 -moreinfo Bug #758492 [release.debian.org] RM: lcms/1.19.dfsg2-1.5 Removed tag(s) moreinfo. unblock -1 by 740495 Bug #758492 [release.debian.org] RM: lcms/1.19.dfsg2-1.5 758492 was blocked by: 743596 740495 757384 758492 was not blocking any bugs. Removed blocking bug(s) of 758492: 740495 unblock -1 by 757384 Bug #758492 [release.debian.org] RM: lcms/1.19.dfsg2-1.5 758492 was blocked by: 743596 757384 758492 was not blocking any bugs. Removed blocking bug(s) of 758492: 757384 -- 758492: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=758492 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/handler.s.b758492.141253879816140.transcr...@bugs.debian.org
Re: Why does libtecla not propagate to testing (Was: libtecla is marked for autoremoval from testing)
On Sun, 2014-10-05 at 22:12 +0200, Andreas Tille wrote: the bug mentioned below was fixed on Mon, 08 Sep 2014 09:18:09 +0200 but the package did not migrated to testing. In fact other architectures do not seem to build the package since the testing migration page https://qa.debian.org/excuses.php?package=libtecla shows a lot of missings. No, it built everywhere. What that page is showing you is that you stopped building libtecla1-dev, having renamed it to libtecla-dev. I suspect that there was some manual hold or something like this on the package doe to the nature of bug #760790. There was not. If you stop building a package, it will not automatically disappear from unstable. Assuming the package is dropped on all architectures then it will appear on ftp-master's cruft report output (https://ftp-master.debian.org/cruft-report-daily.txt) along with an indication of which packages would be broken if it were removed from the archive. Once that number is zero, it will be removed by a member of the FTP team. In the case of libtecla1-dev, because it Provides: libtecla-dev and several packages build-depend on that, dak believed that removing the package would break those other packages. After the confusion was explained on IRC (not by me) the FTP team have now removed the old package. As a consequence, assuming there are no other issues, libtecla should migrate in the next britney run. Regards, Adam -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/1412540832.26144.36.ca...@jacala.jungle.funky-badger.org
Re: Bug#763148: Prevent migration to jessie
Hi, On 05.10.2014 21:27, Cyril Brulebois wrote: Andreas Cadhalpun andreas.cadhal...@googlemail.com (2014-10-05): The whole discussion we are having currently is about letting FFmpeg migrate to jessie! So this is no 'unavoidable issue'. But as you seem to be willing to consider this in principle, I think now the time has come for the release team to make an official decision: Is FFmpeg allowed to migrate to testing, so that chromium can use it? Or is chromium allowed to continue to use it's embedded copy? I'm not sure why one would think the decision still needs to be made. That's because the last message from a release team member in this bug said [1]: 'However (and please note that I'm not a member of the security team and just speak for myself here as always when not otherwise marked) if it would be possible to replace the internal code copy in chromium by a reference to ffmpeg (but it's not possible with libav), that will probably lead to a re-evalutation. (That doesn't necessarily mean sucess guranteed, but it looks to me as it will not make things worse.)' It is possible to replace the internal code copy in chromium by a reference to ffmpeg [2], so I thought this would lead to a re-evaluation. Best regards, Andreas 1: https://bugs.debian.org/763148#27 2: https://bugs.debian.org/763632 -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/5431abb3.9080...@googlemail.com
Re: Bug#763148: Prevent migration to jessie
Andreas Cadhalpun andreas.cadhal...@googlemail.com (2014-10-05): On 05.10.2014 21:27, Cyril Brulebois wrote: I'm not sure why one would think the decision still needs to be made. That's because the last message from a release team member in this bug said [1]. 1: https://bugs.debian.org/763148#27 What I wrote applies to both Andreas. Mraw, KiBi. signature.asc Description: Digital signature
Re: Bug#763148: Prevent migration to jessie
Hi, On 05.10.2014 22:38, Cyril Brulebois wrote: Andreas Cadhalpun andreas.cadhal...@googlemail.com (2014-10-05): On 05.10.2014 21:27, Cyril Brulebois wrote: I'm not sure why one would think the decision still needs to be made. That's because the last message from a release team member in this bug said [1]. 1: https://bugs.debian.org/763148#27 What I wrote applies to both Andreas. When and how was this decision made, if apparently not even all release team members were aware of that? Best regards, Andreas -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/5431ae91.3010...@googlemail.com
Re: Bug#763148: Prevent migration to jessie
* Andreas Cadhalpun (andreas.cadhal...@googlemail.com) [141005 22:36]: That's because the last message from a release team member in this bug said [1]: 'However (and please note that I'm not a member of the security team and just speak for myself here as always when not otherwise marked) if As I said, I was just speaking for myself. That I might be at other times speaking as a member of the release team doesn't make it an opinion of the release team. For the release team opinion on this topic seen Cyrils mails. Also, the re-evaluation happened. It however didn't had the outcome you wanted (basically because the web browser needs so many security updates which only could be done by backporting all of it that the embedded copy doesn't make any difference - this is an exceptional thing which does happen but not very often. I can understand it, and of course it's the call of the security team how to ensure that Debian has security updates. I hadn't know that at the time I though about the possibility, otherwise I would have already achived at that moment at the conclusion). Conclusion: Though I'm usually an optimistic person how to get things achived, I don't see any way left how at this late time it's possible to ship with ffmpeg in jessie. I'm sorry but we have to face the facts. Independend if we like them or not (and I can fully understand that you don't like them, but it's no good pretending facts are different than they are). Sorry. Andi -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141005205445.gh3...@mails.so.argh.org
Re: Re: Bug#763148: Prevent migration to jessie
On Sunday 05 October 2014 22:48:17 Andreas Cadhalpun wrote: When and how was this decision made, if apparently not even all release team members were aware of that? I refrained myself from making this comment on the previous debian-devel thread, but now I consider it necessary to be said: given your apparent lack of understanding of the situation and way of communicating it only makes me wonder on the ability to work with you as the maintainer of such a security- sensitive package that ffmpeg is. I truly hope you understand the implications of such an impediment. Regards, -- Raphael Geissert - Debian Developer www.debian.org - get.debian.net -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/21102124.Bn3hmkj4GS@eee
Bug#764156: wheezy-pu: package debian-archive-keyring/2014.1~deb7u1
Package: release.debian.org Severity: normal Tags: wheezy User: release.debian@packages.debian.org Usertags: pu Hi, I would like to update the attached package update of debian-archive-keyring to proposed-updates. This is a backport of the package in unstable, which adds the Jessie key and replaces my key signing key with the current one in the keyring. Kind regards Philipp Kern diff -Nru debian-archive-keyring-2012.4/active-keys/add-jessie-stable debian-archive-keyring-2014.1~deb7u1/active-keys/add-jessie-stable --- debian-archive-keyring-2012.4/active-keys/add-jessie-stable 1970-01-01 01:00:00.0 +0100 +++ debian-archive-keyring-2014.1~deb7u1/active-keys/add-jessie-stable 2014-08-31 07:22:29.0 +0200 @@ -0,0 +1,68 @@ +Comment: add Jessie stable key (ID: CBF8D6FD518E17E1) +Date: Sun, 31 Aug 2014 07:22:29 +0200 +Action: import +Data: + -BEGIN PGP PUBLIC KEY BLOCK- + Version: GnuPG v1 + + mQINBFIPYFgBEAC2wn0GKL3a6ZI3WtoiRRNYeVEwiSr8xP1zhk+Xavi4XsoHPsru + vo+9DvDiIcID8zDkcbt7QG8QvLP7yN6ucKcZhGOO+NFwKtkDsmEpG35/e17j+M74 + IgrrDs1Z249JwGXb28YN6u6KQBcDudcPFeQ5oZa1bnjgFYHVIxLvriBAoiCf7sT8 + WBfqYoNnIm6w+uEJDK9p3x+6BsJx+lBSUH0ZFGGjnZg+FMhW+IgdkRK9q7y8ofJ6 + HVH1W34qJWTGdYybywJqyaiNbIG7w9a6zbInfOSWEcCTzv6qukK0qzSQecL3cxsD + 7MKbQuQKM3qHb2FDQPnMDuiZKKDb8/zL9sn7xj/OVVpk8nkwMT3wirdQ1EaKz+XM + 7NKu32TjUWsBZpZTHvip13Tu4E17/oeeB6xyjWXu8TDJyBbMXoHv28Ab+pj098it + 1UFZnGlQZRMEa15V7O6f1ym9jyWATGVZii7iH8M73bXGEhEbPT58YBzll0olIHZf + AjtxcONdX82bJDHVo0Fv/Ww4hoitC/6PfdksKpVV2s708OlXGyzBSQg1CE0ozJzK + xnAf6veD+Zol62RkmVwKihvwvK/oE04hyH5eWY+/A1NRyESVeTpI1JJ3URfYLufh + XNBsYjA6mpAgymBJs6+TODDLbquRyhUiKVhfaEmHihp6jz748jvXPU7W+QARAQAB + tDtKZXNzaWUgU3RhYmxlIFJlbGVhc2UgS2V5IDxkZWJpYW4tcmVsZWFzZUBsaXN0 + cy5kZWJpYW4ub3JnPokCPQQTAQgAJwUCUg9gWAIbAwUJDwmcAAULCQgHAwUVCAoJ + CwUWAgMBAAIeAQIXgAAKCRDL+Nb9UY4X4fOGD/94LCoWsVVV+gPfP8R9FCafg5x6 + 5y3QkuL7WlatQbTpZyVZK5XiaoIiWi31lZ3fHG3SRYoqbyYatcVIf8/m9LlRJLOB + ZwQW02sM7jLqf7oA3XLyUnpwgb4xQiNr0Wvdi7aL70/AJaNPL+J7EQZMLppIKoZU + 28UYIfuA7MCJbJXPBr7hBsyzolf6A0qVh7KSaIpdX7Rt3aHcmFkb3iSty99KHN1N + zjb+Y13AE0aXGaEbabZaH3b2cZ2/jrGp6VY2eB6qN0iIa+qQ0nkzR5lFsVq4R85E + Rhcwv6Zr8fp6IiNN/JIs5M1GJoFE8wkR7fEaQ6WK8QB/K2dUQ6y0LtA2t6rUcEVi + 8+/+Nerhal33KlT4ivUbE6X4Z4YqRqfKXDT0juJZR/LLjHWRQHy+pWPAs5DumCNi + J0xkieW6quZ80QoYOWZkyDEemWjgFknYepuT9zHPWeJqavJ5U7copMVdJ/41ESq/ + +J0NREgcWC++aJJdxNwfbOwtQbC+5/fCj0N9gOe6/rpu3BAi99CG6Si9KfBqAbCi + RzfjmLJkHjmAVCjCcduakSI/PfYW2DGS9Yt142zTuxsZP2hqGXFaBlGHbVyvh9Du + yJAPfnF6W22ueFYPoMayR3EqyGTQDohhuxZuYokp/nQZdS7AdV9tHbuMNh7f+dnc + 9u5+C3hTLYgLSvFsQYkEHAQQAQgABgUCVAH+wQAKCRBQw2NNOikc+ZdKH/44JOGM + S536RkWApUXR5b9LIlLyznjOFhf1FQuaoEvzFuY0L6bmD81QOh3r1qzMvB6Ic8Xp + 891gjsL1mqvGLKmHInhcbsplq3XmVoXdDeHjbeUz+QEOLs6mNtLk7eR3Xs7jJQuO + kYCmLY2SfVpP43tqlYwxW8IMXM8rP/XyJAut3+UFPRZznYBDSSYNv8KusxTCDgFO + i2elJiyyrljkoW/MNHBCEVrKAI9zOLkStPVnDQJjogDsWl3zpRq24byllWz/Ye67 + OdCXyLw+/6Xpm4v97Jx64crC+qreBa53D8nMnRaKV9eE9yV7p5hKfoTyyO05DYCM + 1MoQtDbIz9y/Jm09QfQuR04zJVNur7wi5dJKR7Cd3WqBPNX4u0x03UFap8dB5OdI + JVYbvFXZdvDBvqPq7XPThnqXGlrdkQjIMke2cCuC7RirmibFnm3ExLkeAaiCXNEY + tB5LF/01tGSAei4nHrSYfcnz2GvSVqMl9RmqaIEICoHEIOBJwNMs2iLhGYM1qF7I + tUobKjHPpJjmIqIQTMBlQOKUMSKWfSzXcrPEdGBk+pEeTJbZHVh5SALu1ENCUUam + D8l5FDbXesU9A2yiozUTznvcsmLbrlk78AWUtIxQCRCu+Ua9JaNUaCW0s2ooBAlU + bXYSHWt4CVccPDA1FEkqN8+IP2kxq1IZ5bidVLaY0jOtLzy8AMVjUaO/orRUk8zf + ThFN85TG6Y67oXIsELfvFFovo5aYjx8X95xm5jb3hFInwNh0GNdv0bmHS6pb0Vjn + 8WwDJ0emSocaOHMV0fKKFqHHqZ/hJfq3NRx0RbJGG6rqYAy36EkDzVL2uS+t7Zo/ + g1SQ6mByZfX6ylJGNhLgeLkoiupRam8d7CvW1yTmDlZfn7dV++Nfq/s7j3vC1Kr6 + uO+7Mbw97Sb4acxXX1acHb31qFudvec5sMYK2bl76txcE8oYT2AgXXgPKhkMEAPW + peUuiE7ou0Z0JKVdhdK5qItSa0Hz83I4GRCg21//UTmhGcWgTBe9w9OV2wtQTKeb + Dy9RK9b3WksLOU1l45/c6dxKlwcymCB43adefHcLexCIl/kIX9lrYRJkWpYJg8AQ + V5msc3TAQZreNvFat+igBRrpbBQOA/oaj41yqjsO04xsqrEcFIh7KyLGbproJy2+ + WB4D1tXOJCyMFRLCYa4wqPCdtf7wCMoIRCXRZzYjj9vBmi/6D7lDWSJvk5bqwGY8 + sfS3oYw/yIW8QtUVzyDTchuVp0er7W2AbE5Hwxx8oa9r1hvX7x2aXPlA198DLKbu + FDhd6STmiEOggZNad/dkVWz/pIDppi0bhUZhSxqTxV4+pl5y7wQ3bSOBtZre4lSB + ZzZOMnyYe5MvqndRiQIcBBABCAAGBQJUAiR8AAoJEMXOXcLFQs1ZZtoQAJ9m5wV/ + zVw/LOLoT1Foe23MPl6kGdMcCZLvyRyEGnqK58X59GjjT56JEBwLo8lI5acqhBrN + N55/qgcn1Yp5R/KYfz3fYfuHVLexxe3bKWx+Q0LNdQZIPFx/Ly7krRefIE6K1def + SqbyU62sjMXheVDeh5kdTAjgXWZvesjg+ZyXgZnaTf+8x4Fc0llFyqZsLEnxE1qP + U4KLlxUH55j8uUv1dn3wGFuvaURuqwLAIDnIZfsiE05rx8iNZfbxBnQmt2Nrs1x3 + 78aEtQX/kb4HfPreY1BBM3pZiqszOzGB552kP4LoQSm7w8NUfsxEwSDCPeKR4Yk7 + 4eSBfdQIQBPmt9rggNXqw5Si4RRGT6WpKwGFq0QLIC6C1vkiQQqqq13d3w38mIf9 + tb+GDpKGBmkiVD0JBmXDMvCrBfS44HZUZIlhvnB2ME8mQHLhQdCz+saYAixzCwuA + oVpcN3AP0Tl4MBE+xfrM5OlWhWFjjPbjVb29aJdBqsDBNFc2LyissNwn2/RjW/Kg + Scd/zQ2QN57fPQhfbFcbUKbpI49D8iWxk14rYXfV3lfTgkPYGxo/3UQMmRvZ9wdw + ffsCmIuyeAXPkNZbBMADDhD5zU47wfvgEcvK5cfuuNIrY66euUE5hw/wg1VHb/+8 + 2a65h59CeW4zAYbU/0t47ghTDi/ybqTVbcsp + =kPlg + -END PGP PUBLIC KEY BLOCK- + diff -Nru debian-archive-keyring-2012.4/active-keys/index
Re: Bug#763148: Prevent migration to jessie
Hi Raphael, On 05.10.2014 23:01, Raphael Geissert wrote: I refrained myself from making this comment on the previous debian-devel thread, but now I consider it necessary to be said: given your apparent lack of understanding of the situation and way of communicating it only makes me wonder on the ability to work with you as the maintainer of such a security- sensitive package that ffmpeg is. I truly hope you understand the implications of such an impediment. I always tried to understand the arguments of others and explain my point of view extensively. I'm sorry if this wasn't how it looked to you. Best regards, Andreas -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/5431b68e.2090...@googlemail.com
Re: Bug#763148: Prevent migration to jessie
Hi Andreas, On 05.10.2014 22:54, Andreas Barth wrote: * Andreas Cadhalpun (andreas.cadhal...@googlemail.com) [141005 22:36]: That's because the last message from a release team member in this bug said [1]: 'However (and please note that I'm not a member of the security team and just speak for myself here as always when not otherwise marked) if As I said, I was just speaking for myself. That I might be at other times speaking as a member of the release team doesn't make it an opinion of the release team. For the release team opinion on this topic seen Cyrils mails. Also, the re-evaluation happened. It however didn't had the outcome you wanted (basically because the web browser needs so many security updates which only could be done by backporting all of it that the embedded copy doesn't make any difference - this is an exceptional thing which does happen but not very often. I can understand it, and of course it's the call of the security team how to ensure that Debian has security updates. I hadn't know that at the time I though about the possibility, otherwise I would have already achived at that moment at the conclusion). Conclusion: Though I'm usually an optimistic person how to get things achived, I don't see any way left how at this late time it's possible to ship with ffmpeg in jessie. I'm sorry but we have to face the facts. Independend if we like them or not (and I can fully understand that you don't like them, but it's no good pretending facts are different than they are). Sorry. Thanks for explaining. It's sad that it isn't possible to have FFmpeg in jessie, but hopefully it'll be in jessie+1. Best regards, Andreas -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/5431b6bb.8020...@googlemail.com
Bug#764156: wheezy-pu: package debian-archive-keyring/2014.1~deb7u1
Control: tags -1 + confirmed On Sun, 2014-10-05 at 23:13 +0200, Philipp Kern wrote: I would like to update the attached package update of debian-archive-keyring to proposed-updates. This is a backport of the package in unstable, which adds the Jessie key and replaces my key signing key with the current one in the keyring. Please go ahead; thanks. Regards, Adam -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/1412544706.26144.37.ca...@jacala.jungle.funky-badger.org
Processed: Re: Bug#764156: wheezy-pu: package debian-archive-keyring/2014.1~deb7u1
Processing control commands: tags -1 + confirmed Bug #764156 [release.debian.org] wheezy-pu: package debian-archive-keyring/2014.1~deb7u1 Added tag(s) confirmed. -- 764156: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764156 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/handler.s.b764156.141254471519942.transcr...@bugs.debian.org
Bug#763786: wheezy-pu: package dwm/6.0-4+deb7u1
Control: tags -1 + pending On Fri, 2014-10-03 at 21:38 +0530, kamathvasu...@gmail.com wrote: Adam D. Barratt a...@adam-barratt.org.uk writes: Control: tags -1 + confirmed On Thu, 2014-10-02 at 22:50 +0530, Vasudev Kamath wrote: dwm (6.0-4+deb7u1) stable; urgency=low * Fix broken patch headers. Closes: bug#722994, Thanks to Guillem Jover. -- Vasudev Kamath kamathvasu...@gmail.com Thu, 14 Aug 2014 12:01:48 +0530 Please go ahead; thanks. Thanks for the quick response. Package uploaded. Flagged for acceptance; thanks. Regards, Adam -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/1412545755.26144.38.ca...@jacala.jungle.funky-badger.org
Processed: Re: Bug#763786: wheezy-pu: package dwm/6.0-4+deb7u1
Processing control commands: tags -1 + pending Bug #763786 [release.debian.org] wheezy-pu: package dwm/6.0-4+deb7u1 Added tag(s) pending. -- 763786: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=763786 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/handler.s.b763786.141254576727990.transcr...@bugs.debian.org
NEW changes in stable-new
Processing changes file: dwm_6.0-4+deb7u1_amd64.changes ACCEPT Processing changes file: keyutils_1.5.5-3+deb7u1_armel.changes ACCEPT Processing changes file: keyutils_1.5.5-3+deb7u1_armhf.changes ACCEPT Processing changes file: keyutils_1.5.5-3+deb7u1_i386.changes ACCEPT Processing changes file: keyutils_1.5.5-3+deb7u1_ia64.changes ACCEPT Processing changes file: keyutils_1.5.5-3+deb7u1_mips.changes ACCEPT Processing changes file: keyutils_1.5.5-3+deb7u1_mipsel.changes ACCEPT Processing changes file: keyutils_1.5.5-3+deb7u1_powerpc.changes ACCEPT Processing changes file: keyutils_1.5.5-3+deb7u1_s390.changes ACCEPT Processing changes file: keyutils_1.5.5-3+deb7u1_s390x.changes ACCEPT Processing changes file: keyutils_1.5.5-3+deb7u1_sparc.changes ACCEPT -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/e1xau76-0006vf...@franck.debian.org
Bug#763514: marked as done (unblock: dbus/1.8.8-1 systemd/215-5)
Your message dated Mon, 6 Oct 2014 00:11:40 +0200 with message-id 20141005221140.gf8...@mraw.org and subject line Re: Bug#763514: unblock: dbus/1.8.8-1 systemd/215-5 has caused the Debian Bug report #763514, regarding unblock: dbus/1.8.8-1 systemd/215-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.) -- 763514: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=763514 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock dbus in unstable has some security fixes which aren't migrating because it's stuck behind libsystemd0, and because both dbus and systemd produce udebs. Please consider lifting the block-udeb and maybe bumping systemd's urgency, either before Jessie beta 2 or immediately after, depending how soon that's going to be (X-Debbugs-Cc: debian-boot to decide which way to go). As far as I'm aware, these udebs are there to support accessibility (ATK) in the graphical installer. This might be the right syntax: unblock dbus/1.8.8-1 unblock systemd/215-5 Thanks, S ---End Message--- ---BeginMessage--- Simon McVittie s...@debian.org (2014-09-30): On 30/09/14 18:21, Cyril Brulebois wrote: TL;DR: nack for now. Sure, no problem. Hopefully lifting the block-udeb in the normal way after the beta will be enough to resolve this. According to my fuzzy memory (and past excuses files), the root reason is that systemd hasn't been a candidate in a while (too young and/or RC buggy). Yes, it had RC bugs for a while but they seem to have been addressed in unstable now. It's still a bit too new though (2/5 days). (systemd means udev-udeb, nothing something I'd like to rush in at the last minute.) I'd forgotten about udev-udeb, and yes, that's a good reason to not rush it! FWIW it might be a nice idea to coordinate such requests with Michael since I already replied on that topic on #-release earlier today… Sorry, I should have mentioned that I filed this in response to IRC discussion with Michael (about some lower-priority dbus changes which I didn't want uploaded until it migrates), and I had X-Debbugs-Cc'd him in the bug report. Both are in, closing. Mraw, KiBi. signature.asc Description: Digital signature ---End Message---
Re: Updating isc-dhcp udeb to dynamically link bind (was: Bug#762762: nmu fixing bind issues)
Michael Gilbert mgilb...@debian.org (2014-10-05): Dear hurd and kfreebsd porters. I plan to upload the attached patch, which along with the previous upload introduces a bind udeb, which will be dynamically linked by the dhcp udeb. Please let me know if this looks ok. NAK. +bind9 (1:9.9.5.dfsg-4.2) unstable; urgency=low + + * Non-maintainer upload. + * Disable parallel build. Closes: #762766 If parallel building worked before you changed things, you get to fix the issues rather than working around them. bind9 is a pain to build, so having to deal with a forced -j1 is a nasty regression. + * Set -fno-delete-null-pointer-checks. Closes: #750760 + * Fix dependencies for libbind-export-udeb. Closes: #762762 This udeb doesn't make any sense to me. $ cat ./debian/libbind-export-udeb/DEBIAN/shlibs libdns-export 100 libbind-export-udeb libirs-export 91 libbind-export-udeb libisc-export 95 libbind-export-udeb libisccfg-export 90 libbind-export-udeb The udeb is unversioned. ABI is going to be broken as usual in later uploads, meaning the udeb shipping these shared objects will break reverse dependencies: /usr/lib/libisccfg-export.so.90.1.0 /usr/lib/libdns-export.so.100.2.2 /usr/lib/libirs-export.so.91.0.0 /usr/lib/libisc-export.so.95.5.0 /usr/lib/libdns-export.so.100 - libdns-export.so.100.2.2 /usr/lib/libisccfg-export.so.90 - libisccfg-export.so.90.1.0 /usr/lib/libirs-export.so.91 - libirs-export.so.91.0.0 /usr/lib/libisc-export.so.95 - libisc-export.so.95.5.0 I really fail to see how you could possibly imagine anything could work. Since we're late in the D-I release cycle, since we're late in the release cycle in general (window for transitions closed past month), since there was no coordination whatsoever, and since there is apparently no well thought through plan, I think I'll oppose isc-dhcp's using such a udeb. debian-release@ in Cc: to let the team now I might just block the bind9 package to make sure this udeb never reaches testing. Mraw, KiBi. signature.asc Description: Digital signature
Bug#758492: RM: lcms/1.19.dfsg2-1.5
On 05/10/14 22:09, Emilio Pozuelo Monfort wrote: On 05/10/14 21:52, Michael Gilbert wrote: control: tag -1 -moreinfo control: unblock -1 by 740495 control: unblock -1 by 757384 On Mon, Aug 18, 2014 at 1:11 AM, Niels Thykier wrote: Are we (really) ready for this? Removal of lcms in testing would break several packages including gimp and libmagickcore-dev[1] lcms no longer has any reverse dependencies or reverse build dependencies in testing, so it is ready to be removed now. Added a hint, let's see how it goes. trying: -lcms skipped: -lcms (0 - 111) got: 10+0: i-10 * i386: hannah-foo2zjs, printer-driver-all-enforce, printer-driver-foo2zjs Maybe it'll work in a couple of days when foo2zjs migrates. Emilio -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/5431ce1c.5050...@debian.org
Bug#764167: wheezy-pu: package wireless-regdb/2014.06.13-1~deb7u1
Package: release.debian.org
Severity: normal
Tags: wheezy
User: release.debian@packages.debian.org
Usertags: pu
I have just updated wireless-regdb in unstable to a new upstream
release. There have been many changes to the database based on new
regulations and information about additional countries. These should
also go into stable so that users can easily comply with current laws
and use the full permitted ranges of frequency and transmit power.
Ben.
diff -Nru wireless-regdb-2013.11.27/CONTRIBUTING
wireless-regdb-2014.06.13/CONTRIBUTING
--- wireless-regdb-2013.11.27/CONTRIBUTING 1970-01-01 01:00:00.0
+0100
+++ wireless-regdb-2014.06.13/CONTRIBUTING 2014-06-13 20:08:55.0
+0100
@@ -0,0 +1,49 @@
+
+This project embraces the Developer Certificate of Origin (DCO) for
+contributions. This means you must agree to the following prior to submitting
+patches, if you agree with this developer certificate you acknowledge this by
+adding a Signed-off-by tag to your patch commit log. Every submitted patch
+must have this.
+
+The source for the DCO:
+
+http://developercertificate.org/
+
+---
+
+Developer Certificate of Origin
+Version 1.1
+
+Copyright (C) 2004, 2006 The Linux Foundation and its contributors.
+660 York Street, Suite 102,
+San Francisco, CA 94110 USA
+
+Everyone is permitted to copy and distribute verbatim copies of this
+license document, but changing it is not allowed.
+
+
+Developer's Certificate of Origin 1.1
+
+By making a contribution to this project, I certify that:
+
+(a) The contribution was created in whole or in part by me and I
+have the right to submit it under the open source license
+indicated in the file; or
+
+(b) The contribution is based upon previous work that, to the best
+of my knowledge, is covered under an appropriate open source
+license and I have the right under that license to submit that
+work with modifications, whether created in whole or in part
+by me, under the same open source license (unless I am
+permitted to submit under a different license), as indicated
+in the file; or
+
+(c) The contribution was provided directly to me by some other
+person who certified (a), (b) or (c) and I have not modified
+it.
+
+(d) I understand and agree that this project and the contribution
+are public and that a record of the contribution (including all
+personal information I submit with it, including my sign-off) is
+maintained indefinitely and may be redistributed consistent with
+this project or the open source license(s) involved.
diff -Nru wireless-regdb-2013.11.27/dbparse.py
wireless-regdb-2014.06.13/dbparse.py
--- wireless-regdb-2013.11.27/dbparse.py2013-11-27 16:21:08.0
+
+++ wireless-regdb-2014.06.13/dbparse.py2014-06-13 20:08:55.0
+0100
@@ -16,6 +16,7 @@
# hole at bit 8
# hole at bit 9. FIXME: Where is NO-HT40 defined?
'NO-HT40': 110,
+'AUTO-BW': 111,
}
dfs_regions = {
diff -Nru wireless-regdb-2013.11.27/db.txt wireless-regdb-2014.06.13/db.txt
--- wireless-regdb-2013.11.27/db.txt2013-11-27 16:21:08.0 +
+++ wireless-regdb-2014.06.13/db.txt2014-06-13 20:08:55.0 +0100
@@ -4,10 +4,13 @@
# Channel 12 - 13.
(2457 - 2482 @ 40), (20), NO-IR
# Channel 14. Only JP enables this and for 802.11b only
- (2474 - 2494 @ 20), (20), NO-IR
+ (2474 - 2494 @ 20), (20), NO-IR, NO-OFDM
# Channel 36 - 48
- (5170 - 5250 @ 80), (20), NO-IR
- # NB: 5260 MHz - 5700 MHz requies DFS
+ (5170 - 5250 @ 160), (20), NO-IR
+ # Channel 52 - 64
+ (5250 - 5330 @ 160), (20), NO-IR, DFS
+ # Channel 100 - 144
+ (5490 - 5730 @ 160), (20), NO-IR, DFS
# Channel 149 - 165
(5735 - 5835 @ 80), (20), NO-IR
# IEEE 802.11ad (60GHz), channels 1..3
@@ -25,6 +28,12 @@
(5490 - 5730 @ 80), (24), DFS
(5735 - 5835 @ 80), (30)
+country AF: DFS-ETSI
+ (2402 - 2482 @ 40), (20)
+ (5170 - 5250 @ 80), (20)
+ (5250 - 5330 @ 80), (20), DFS
+ (5490 - 5710 @ 80), (27), DFS
+
country AL: DFS-ETSI
(2402 - 2482 @ 40), (20)
(5170 - 5250 @ 80), (20.00)
@@ -101,6 +110,13 @@
# 60 gHz band channels 1-4, ref: Etsi En 302 567
(57240 - 65880 @ 2160), (40), NO-OUTDOOR
+country BF: DFS-FCC
+ (2402 - 2482 @ 40), (20)
+ (5170 - 5250 @ 80), (17)
+ (5250 - 5330 @ 80), (24), DFS
+ (5490 - 5730 @ 80), (24), DFS
+ (5735 - 5835 @ 80), (30)
+
country BG: DFS-ETSI
(2402 - 2482 @ 40), (20)
(5170 - 5250 @ 80), (20)
@@ -136,6 +152,14 @@
(5490 - 5730 @ 80), (24), DFS
(5735 - 5835 @ 80), (30)
+# Source:
+# http://www.bicma.gov.bt/paper/publication/nrrpart4.pdf
+country BT: DFS-ETSI
+ (2402 - 2482 @ 40), (20)
+ (5170 - 5250 @ 80), (20)
+ (5250
finding out why a package is not in testing
I initially asked this on debian-devel ( https://lists.debian.org/debian-devel/2014/10/msg00055.html) and was told that debian-release might be a more suitable place. Since there is no longer a search functionality in https://release.debian.org/migration/ to find out why a particular package is not in testing yet, can we please put a link to https://ftp-master.debian.org/testing/update_excuses.html (or something more appropriate) on that page? This way someone can open up the link and search for the package name they are interested in. thanks raju -- Kamaraju S Kusumanchi http://malayamaarutham.blogspot.com/
Re: Updating isc-dhcp udeb to dynamically link bind (was: Bug#762762: nmu fixing bind issues)
Michael Gilbert mgilb...@debian.org (2014-10-05): On Sun, Oct 5, 2014 at 7:02 PM, Cyril Brulebois wrote: If parallel building worked before you changed things, you get to fix the issues rather than working around them. bind9 is a pain to build, so having to deal with a forced -j1 is a nasty regression. It's a rarely used path through the build system (--enable-exportlib), so it's sort of unsurprising that there was a lurking issue. Anyway, in the meantime I fixed the problem. Thanks for the prodding. I haven't build-checked it but that's the kind of easy fix I'd have expected indeed, thanks. This udeb doesn't make any sense to me. $ cat ./debian/libbind-export-udeb/DEBIAN/shlibs libdns-export 100 libbind-export-udeb libirs-export 91 libbind-export-udeb libisc-export 95 libbind-export-udeb libisccfg-export 90 libbind-export-udeb The udeb is unversioned. ABI is going to be broken as usual in later uploads, meaning the udeb shipping these shared objects will break reverse dependencies: /usr/lib/libisccfg-export.so.90.1.0 /usr/lib/libdns-export.so.100.2.2 /usr/lib/libirs-export.so.91.0.0 /usr/lib/libisc-export.so.95.5.0 /usr/lib/libdns-export.so.100 - libdns-export.so.100.2.2 /usr/lib/libisccfg-export.so.90 - libisccfg-export.so.90.1.0 /usr/lib/libirs-export.so.91 - libirs-export.so.91.0.0 /usr/lib/libisc-export.so.95 - libisc-export.so.95.5.0 I really fail to see how you could possibly imagine anything could work. I was trying to avoid an explosion in the number of udebs, but I get your point now that won't work. I've split up the udebs now so things can be properly versioned. That looks better from a quick glance, yes. (Not that it matters much but you should use Package-Type.) Since we're late in the D-I release cycle, since we're late in the release cycle in general (window for transitions closed past month), since there was no coordination whatsoever, and since there is apparently no well thought through plan, I think I'll oppose isc-dhcp's using such a udeb. Maybe I've addressed your concerns, maybe not, but please consider the revised changes attached. I'm not going to go through building this on a kfreebsd porterbox to try and figure out how isc-dhcp would look if rebuilt against such packages, but that looks a saner base for porters to build upon. That doesn't make the timing issues I've mentioned disappear though. I'm OK with thinking about it again if porters endorse/welcome/successfully test the resulting packages and installation images. Mraw, KiBi. signature.asc Description: Digital signature
Re: Bug#762762: Updating isc-dhcp udeb to dynamically link bind (was: Bug#762762: nmu fixing bind issues)
On Sun, Oct 5, 2014 at 9:59 PM, Cyril Brulebois wrote: I'm not going to go through building this on a kfreebsd porterbox to try and figure out how isc-dhcp would look if rebuilt against such packages, but that looks a saner base for porters to build upon. That doesn't make the timing issues I've mentioned disappear though. I'm OK with thinking about it again if porters endorse/welcome/successfully test the resulting packages and installation images. Thanks for the feedback. Would it be ok to stage the changes in unstable to make it somewhat easy for porters to test? Best wishes, Mike -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/CANTw=mpb5cgpq1oe6d_vpsoggyk6o3y2bqrrxwba_ozlh6m...@mail.gmail.com
Re: Bug#762762: Updating isc-dhcp udeb to dynamically link bind (was: Bug#762762: nmu fixing bind issues)
Michael Gilbert mgilb...@debian.org (2014-10-05): Would it be ok to stage the changes in unstable to make it somewhat easy for porters to test? Since D-I Jessie Beta 2 is out I can't think of a reason why that wouldn't be a good idea. Mraw, KiBi. signature.asc Description: Digital signature
NEW changes in stable-new
Processing changes file: dwm_6.0-4+deb7u1_armhf.changes ACCEPT Processing changes file: dwm_6.0-4+deb7u1_i386.changes ACCEPT Processing changes file: dwm_6.0-4+deb7u1_ia64.changes ACCEPT Processing changes file: dwm_6.0-4+deb7u1_kfreebsd-amd64.changes ACCEPT Processing changes file: dwm_6.0-4+deb7u1_kfreebsd-i386.changes ACCEPT Processing changes file: dwm_6.0-4+deb7u1_mipsel.changes ACCEPT Processing changes file: dwm_6.0-4+deb7u1_powerpc.changes ACCEPT Processing changes file: dwm_6.0-4+deb7u1_s390.changes ACCEPT Processing changes file: dwm_6.0-4+deb7u1_s390x.changes ACCEPT Processing changes file: dwm_6.0-4+deb7u1_sparc.changes ACCEPT -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/e1xazgn-yg...@franck.debian.org
NEW changes in stable-new
Processing changes file: dwm_6.0-4+deb7u1_mips.changes ACCEPT -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/e1xazur-0002su...@franck.debian.org
Re: grib-api 1.12.3-1
Hi, At Sun, 05 Oct 2014 19:39:23 +0100, Alastair McKinstry mckins...@debian.org wrote: On 05/10/2014 19:19, Enrico Zini wrote: Hello, I have prepared a new upload of grib-api, version 1.12.3-1. This is the main bit of the changelog: * New upstream version - grib_api has an official soname now! It means that it now builds just a standard libgrib-api0, supported by upstream, and we'd be done with having the library full version in the soname. Great. It would be nice to have grib_api soname sanity in jessie, but I'm not uploading it without your informed and enthousiastic consent. I'm enthusiastically consenting to this, if the release-masters let it go through. It would be good to have a standard SONAME for grib-api in Jessie. I'll already prepare to upload in package Git repos. I'll wait for release-master's go sign... Best Wishes, Youhei --- Youhei SASAKI uwab...@gfd-dennou.org uwab...@debian.or.jp GPG fingerprint: 4096/RSA: 66A4 EA70 4FE2 4055 8D6A C2E6 9394 F354 891D 7E07 -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/8738b1ydw6.wl-uwab...@gfd-dennou.org
NEW changes in stable-new
Processing changes file: exuberant-ctags_5.9~svn20110310-4+deb7u1_i386.changes ACCEPT Processing changes file: exuberant-ctags_5.9~svn20110310-4+deb7u1_amd64.changes ACCEPT Processing changes file: exuberant-ctags_5.9~svn20110310-4+deb7u1_armel.changes ACCEPT Processing changes file: exuberant-ctags_5.9~svn20110310-4+deb7u1_armhf.changes ACCEPT Processing changes file: exuberant-ctags_5.9~svn20110310-4+deb7u1_ia64.changes ACCEPT Processing changes file: exuberant-ctags_5.9~svn20110310-4+deb7u1_kfreebsd-amd64.changes ACCEPT Processing changes file: exuberant-ctags_5.9~svn20110310-4+deb7u1_kfreebsd-i386.changes ACCEPT Processing changes file: exuberant-ctags_5.9~svn20110310-4+deb7u1_mips.changes ACCEPT Processing changes file: exuberant-ctags_5.9~svn20110310-4+deb7u1_mipsel.changes ACCEPT Processing changes file: exuberant-ctags_5.9~svn20110310-4+deb7u1_powerpc.changes ACCEPT Processing changes file: exuberant-ctags_5.9~svn20110310-4+deb7u1_s390.changes ACCEPT Processing changes file: exuberant-ctags_5.9~svn20110310-4+deb7u1_s390x.changes ACCEPT Processing changes file: exuberant-ctags_5.9~svn20110310-4+deb7u1_sparc.changes ACCEPT Processing changes file: qemu_1.1.2+dfsg-6a+deb7u4_amd64.changes ACCEPT Processing changes file: qemu_1.1.2+dfsg-6a+deb7u4_armel.changes ACCEPT Processing changes file: qemu_1.1.2+dfsg-6a+deb7u4_armhf.changes ACCEPT Processing changes file: qemu_1.1.2+dfsg-6a+deb7u4_i386.changes ACCEPT Processing changes file: qemu_1.1.2+dfsg-6a+deb7u4_ia64.changes ACCEPT Processing changes file: qemu_1.1.2+dfsg-6a+deb7u4_kfreebsd-amd64.changes ACCEPT Processing changes file: qemu_1.1.2+dfsg-6a+deb7u4_kfreebsd-i386.changes ACCEPT Processing changes file: qemu_1.1.2+dfsg-6a+deb7u4_mips.changes ACCEPT Processing changes file: qemu_1.1.2+dfsg-6a+deb7u4_mipsel.changes ACCEPT Processing changes file: qemu_1.1.2+dfsg-6a+deb7u4_powerpc.changes ACCEPT Processing changes file: qemu_1.1.2+dfsg-6a+deb7u4_s390x.changes ACCEPT Processing changes file: qemu_1.1.2+dfsg-6a+deb7u4_sparc.changes ACCEPT Processing changes file: qemu-kvm_1.1.2+dfsg-6+deb7u4_amd64.changes ACCEPT Processing changes file: qemu-kvm_1.1.2+dfsg-6+deb7u4_i386.changes ACCEPT Processing changes file: tryton-server_2.2.4-1+deb7u1_amd64.changes ACCEPT Processing changes file: tryton-server_2.2.4-1+deb7u2_amd64.changes ACCEPT -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/e1xb0g5-ix...@franck.debian.org
