Re: Report from the first tests of d-i beta 1 candidate images
Quoting Samuel Thibault (sthiba...@debian.org): > Cyril Brulebois, le Tue 17 Jul 2012 11:37:50 +0200, a écrit : > > I think I'd rather avoid uploading a new d-i at this point, and just > > get new images built once the gnome bugs are fixed. > > Christian, maybe you could call for fixing the translations of the > installation manual, so we can upload it to get it onto the beta1 > images? Being currently travelling post-Debconf, such things are not that easy for me (this mail is currently written from an eco-ledge lost somewhere in forests of the Norther mountains, through a 3G connectionwhich is quite amazing to have in such distant place). Moreover, tracking of who is translating the D-I manual is quite loose ATM and I can't even use podebconf-report-po on a bunch of PO files given that most D-I manual translators *don't* use gettext (and some don't want to). So, in short, it's hard to send a real call for updates except by posting a mail to debian-i18n which (I know how these things work) will immediately trigger a bunch of questions, half of them being sent in private to me, such as "I would like to translate it to 'foo', how should I proceed"and, on this, I don't really want to spend the few time I still spend during these two weeks for geeky stuff. So, well, absolutely *no* promise made. If I can do something, I'll do it. Otherwise, anybody else is welcome to do it. signature.asc Description: Digital signature
Re: BinNMU changelog handling for Multi-Arch: same packages
On Tue, Jul 17, 2012 at 02:53:19PM +0200, Guillem Jover wrote: > > (I'd currently tend to accept it, however I'm not yet sure of all the > > consequences of this change.) > This change in itself should not have any consequence as it should not > affect the normal build if the value is not being used, or maybe you > are referring to *when* the value is being used? I don't want to special-case a single suite in buildd/sbuild to not put binary-only=something in there. And yes, those are only warnings, I know, but it would be annoying to have the build logs polluted with them. (And it's one reason why we always expect stable to support the features we use in the archive.) Kind regards Philipp Kern signature.asc Description: Digital signature
Re: emacs24 got freeze exception, what happens to emacs add-ons?
"Adam D. Barratt" writes: > It would work, but it's not exactly ideal for future updates, > particularly in stable... Right. During debconf, with some help, I was able to track down the problem. It turns out that Emacs was checking errno after a number of floating point operations, including fabs(), but because fabs() doesn't have any error conditions, it's not guaranteed to leave errno alone -- and as you might imagine, on murphy, it wasn't. In any case, the fix is trivial, and I'll upload a -3 shortly that includes it. After that, I'll foward a diff between -1 and -3 to debian-release, and then you can decide what you'd like to do. It will be a very small diff, just the addition of [linux-any] to the libselinux1-dev build-dep, and this fabs/errno adjustment. Thanks for the help -- Rob Browning rlb @defaultvalue.org and @debian.org GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4 -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87ipdmj6ke@trouble.defaultvalue.org
Re: [Pkg-ia32-libs-maintainers] Bug#679671: ia32-libs-i386: depends on removed package libdb4.8
On Sun, 2012-07-01 at 11:56 +0100, Adam D. Barratt wrote: > On Sun, 2012-07-01 at 11:13 +0200, Goswin von Brederlow wrote: [...] > > - libcurl3 (>= 7.21.0-2), libdb4.8 (>= 4.8.30-2), > > + libcurl3 (>= 7.21.0-2), [...] > Is that the only (non-changelog) change in the package? If so then feel > free to get it uploaded and then come back to us with an unblock > request. You appear to have done the former of those, but never bothered with the latter... > Note that in any case the package won't migrate with #677741 > in the way. That wasn't meant as a suggestion to simply downgrade the bug :-p In an earlier thread you mentioned a number of multiarch issues with ia32-libs-gtk; what's the current status there? Also: out of date on ia64: ia32-libs-gtk (from 20120102) Regards, Adam -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1342565606.14254.24.ca...@jacala.jungle.funky-badger.org
Bug#681935: unblock: electric-fence/2.2.4
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package electric-fence Hi, Sorry for another unblock request, but I've finally got the threading in electric-fence sorted properly, such that it now builds on all archs (no previous version built on hurd-i386). I promise to leave the package alone now :-) Thanks, Matthew unblock electric-fence/2.2.4 -- System Information: Debian Release: 6.0.5 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-686 (SMP w/1 CPU core) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120717221637.10872.44455.report...@aragorn.weathertop.principate.org.uk
Bug#681196: unblock: tryton-proteus/2.2.2-3
* Betr.: " Re: Bug#681196: unblock: tryton-proteus/2.2.2-3" (Tue, 17 Jul 2012 20:34:31 +0200): > tag 681196 moreinfo > kthxbye > > On Wed, Jul 11, 2012 at 12:11:14 +0200, Mathias Behrle wrote: > > > Package: release.debian.org > > Severity: normal > > User: release.debian@packages.debian.org > > Usertags: unblock > > > > Please unblock package tryton-proteus. The -3 upload fixes the #680817 > > FTBFS, revealed by a Lucas-powered rebuild. > > > 680817 is still open. Thx for the hint, 680817 is closed now. Cheers, Mathias signature.asc Description: PGP signature
Re: Collaborative maintenance of mime-support (was Re: Using FreeDesktop MIME entries directly in mime-support).
> > Lastly, I would like to thank Brian for his impressively 16-years long > work on > mime-support. Brian, feel free to stay among the uploaders ! > Thanks. I wish I had the energy to make some of the much-needed changes but I'm just not involved with the project enough these days to have a good feel for how it should be improved. Make it great! Brian bcwh...@pobox.com -- *Treat someone as they are and they will remain that way. Treat someone as they can be and they will become that way.*
Bug#681002: release.debian.org: Freeze exception for libguestfs
* Julien Cristau:
>> If this is still not acceptable, what about a 1.18.2-2wheezy1 that just
>> fixes #678977 (upgrade breakage due to multiarch change), #680885,
>> #680886 (multiarch coinstall)?
>>
> wheezy is not affected by any of those 3 bugs as far as I can tell,
> since they're all related to the multiarch switch which isn't in
> 1:1.18.1-1.
Correct.
But #681587 ("python-guestfs: missing dependency on python", serious)
has popped up since. It is fixed with the attached patch. Should
anything be done about that for wheezy?
Cheers,
-Hilko
diff --git a/debian/rules b/debian/rules
index fb143c4..1f3c435 100755
--- a/debian/rules
+++ b/debian/rules
@@ -130,9 +130,9 @@ override_dh_install:
# Workaround for python3-defaults < 3.2~b2-1
# ("do not rename .so files outside dist-packages directory")
override_dh_python3:
- dh_python3 -p python-libguestfs
+ dh_python3 -p python-guestfs
override_dh_python2:
- dh_python2 -p python-libguestfs -V 2.6-
+ dh_python2 -p python-guestfs -V 2.6-
# Workaround for Lintian warning
# "{pre,post}inst-has-useless-call-to-ldconfig"
Bug#681926: unblock: bluefish/2.2.3-3
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Please unblock package bluefish The package got two new patches: - - one fixes a crash (https://bugzilla.gnome.org/679203, https://bugs.launchpad.net/bugs/954879) on platforms where G_GSIZE_FORMAT does not equal %lu. - - the second patch just updates translation .po files unblock bluefish/2.2.3-3 - -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (850, 'unstable'), (700, 'testing'), (560, 'stable'), (110, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-3-amd64 (SMP w/2 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iEUEARECAAYFAlAFzAoACgkQm0bx+wiPa4z9SwCgidvFwEVYyvWqvoW/jcD/emv+ F8sAmKPnq7MLqWRRWovah0nxjvJzSMI= =IjA2 -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: http://lists.debian.org/20120717203314.29058.56792.report...@haktar.debian.wgdd.de
Re: Migration of emboss and embassy-* to testing?
Hi, On Tue, Jul 17, 2012 at 08:33:40PM +0100, Adam D. Barratt wrote: > Apologies for the delay in getting back to you about this. No problem - I guess you have some other stuff to do as well ... > On Thu, 2012-07-05 at 08:55 +0200, Andreas Tille wrote: > > I admit I can not make any sense out of the numbers you are mentioning > > above but the reason embassy-phylip becomes obvious. > > They're the number of uninstallable packages per architecture; the key > difference is the change from "a-0" to "a-1" indicating the newly > installable (if the hint had succeeded) package on amd64. Thanks for the explanation. > Dropping the most obvious build noise from the diff together with what > could charitably be claimed as "documentation fixes" leaves a reasonably > small set of changes. Given that the package is in non-free, I've > unblocked it and hoped nothing breaks; if it does, we might then lean > towards removal rather than another unblock. That's the perfect solution for us - many thanks Andreas. -- 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: http://lists.debian.org/20120717202319.gb17...@an3as.eu
Bug#681733: marked as done (unblock: sane-backends/1.0.22-7.3)
Your message dated Tue, 17 Jul 2012 22:13:52 +0200 with message-id <5005c780.2070...@thykier.net> and subject line Re: Bug#681733: unblock: sane-backends/1.0.22-7.3 has caused the Debian Bug report #681733, regarding unblock: sane-backends/1.0.22-7.3 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.) -- 681733: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=681733 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: release.debian.org User: release.debian@packages.debian.org Usertags: unblock Severity: normal Please unblock package sane-backends It sets sane-utils as multi-arch: foreign, which is currently blocking multiarch ia32-libs. It also fixes a kfreebsd build failure. unblock sane-backends/1.0.22-7.3 --- End Message --- --- Begin Message --- On 2012-07-16 02:28, Michael Gilbert wrote: > Package: release.debian.org > User: release.debian@packages.debian.org > Usertags: unblock > Severity: normal > > Please unblock package sane-backends > > It sets sane-utils as multi-arch: foreign, which is currently blocking > multiarch ia32-libs. It also fixes a kfreebsd build failure. > > unblock sane-backends/1.0.22-7.3 > > Hi, Unblocked. ~Niels--- End Message ---
Re: emacs24 got freeze exception, what happens to emacs add-ons?
On Tue, 2012-07-10 at 17:41 -0500, Rob Browning wrote: > Rob Browning writes: > > > Also not ideal, but if it's allowed, I could just upload both amd64 and > > i386 (or just i386). So far murphy's the only place we seem to have > > this problem. It would work, but it's not exactly ideal for future updates, particularly in stable... fwiw, the auto-exception was for 24.1+1-1; -2 currently has no such exception. The general policy thus far has been not to grant manual unblocks for source packages which are new for wheezy, although we could possibly be persuaded that there are cases where it makes sense. > So the build in the wheezy chroot, running on the i386 squeeze vm didn't > fail. The host kernel there was linux-image-2.6.32-5-686-bigmem > (2.6.32-45). Whether or not that was close enough to murphy's kernel, I > don't know. (From the murphy build log: "Kernel: Linux > 2.6.32-5-686-bigmem i386 (i686)".) > > At this point, I'm not sure what I should try next. Suggestions? My earlier remembering of one of the i386 buildds being a VM appears to have been mistaken; the most obvious difference is that one is an amd64 host whereas the other is i386. The buildd logs contain a list of all of the packages used during the build. It's often worth comparing those between a failing and successful build to see if there are any possibly relevant differences. Regards, Adam -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1342555808.14254.18.ca...@jacala.jungle.funky-badger.org
Bug#681832: marked as done (unblock: xserver-xorg-video-cirrus/1:1.4.0-2)
Your message dated Tue, 17 Jul 2012 20:58:09 +0100 with message-id <1342555089.14254.12.ca...@jacala.jungle.funky-badger.org> and subject line Re: Bug#681832: unblock: xserver-xorg-video-cirrus/1:1.4.0-2 has caused the Debian Bug report #681832, regarding unblock: xserver-xorg-video-cirrus/1:1.4.0-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.) -- 681832: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=681832 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: unblock Please unblock package xserver-xorg-video-cirrus Avoids conflicting with the KMS driver added for the qemu-emulated chip in Linux 3.5. Well, explicitly conflict by bailing out instead of having two drivers fighting over the hw. unblock xserver-xorg-video-cirrus/1:1.4.0-2 -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'unstable'), (500, 'stable'), (101, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-3-amd64 (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash signature.asc Description: Digital signature --- End Message --- --- Begin Message --- On Mon, 2012-07-16 at 23:36 +0200, Julien Cristau wrote: > Please unblock package xserver-xorg-video-cirrus > > Avoids conflicting with the KMS driver added for the qemu-emulated chip > in Linux 3.5. Well, explicitly conflict by bailing out instead of > having two drivers fighting over the hw. Unblocked. Regards, Adam--- End Message ---
Bug#681831: marked as done (unblock: xserver-xorg-video-mga/1:1.5.0-2)
Your message dated Tue, 17 Jul 2012 20:57:50 +0100 with message-id <1342555070.14254.11.ca...@jacala.jungle.funky-badger.org> and subject line Re: Bug#681831: unblock: xserver-xorg-video-mga/1:1.5.0-2 has caused the Debian Bug report #681831, regarding unblock: xserver-xorg-video-mga/1:1.5.0-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.) -- 681831: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=681831 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: unblock Please unblock package xserver-xorg-video-mga Simple patch to avoid conflicting with a KMS driver (one was added for g200se chips in linux 3.5). unblock xserver-xorg-video-mga/1:1.5.0-2 -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'unstable'), (500, 'stable'), (101, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-3-amd64 (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash signature.asc Description: Digital signature --- End Message --- --- Begin Message --- On Mon, 2012-07-16 at 23:35 +0200, Julien Cristau wrote: > Please unblock package xserver-xorg-video-mga > > Simple patch to avoid conflicting with a KMS driver (one was added for > g200se chips in linux 3.5). Unblocked. Regards, Adam--- End Message ---
Bug#681842: marked as done (unblock: libaugeas-ruby/0.4.1-1.1)
Your message dated Tue, 17 Jul 2012 20:48:58 +0100
with message-id <1342554538.14254.10.ca...@jacala.jungle.funky-badger.org>
and subject line Re: Bug#681842: unblock: libaugeas-ruby/0.4.1-1.1
has caused the Debian Bug report #681842,
regarding unblock: libaugeas-ruby/0.4.1-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.)
--
681842: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=681842
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: unblock
Please unblock package libaugeas-ruby
Fixes RC bug #680684.
unblock libaugeas-ruby/0.4.1-1.1
diff -Nru libaugeas-ruby-0.4.1/debian/changelog libaugeas-ruby-0.4.1/debian/changelog
--- libaugeas-ruby-0.4.1/debian/changelog 2012-04-21 08:41:30.0 -0400
+++ libaugeas-ruby-0.4.1/debian/changelog 2012-07-16 22:23:28.0 -0400
@@ -1,3 +1,12 @@
+libaugeas-ruby (0.4.1-1.1) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * Change libaugeas-ruby depends from ruby1.8 to ruby1.9.1 to match the
+current default ruby and update package description to match
+(Closes: #680684)
+
+ -- Scott Kitterman Mon, 16 Jul 2012 20:59:26 -0400
+
libaugeas-ruby (0.4.1-1) unstable; urgency=low
* New upstream release. Closes: #665927.
diff -Nru libaugeas-ruby-0.4.1/debian/control libaugeas-ruby-0.4.1/debian/control
--- libaugeas-ruby-0.4.1/debian/control 2012-04-21 08:34:10.0 -0400
+++ libaugeas-ruby-0.4.1/debian/control 2012-07-16 20:24:26.0 -0400
@@ -8,14 +8,14 @@
Package: libaugeas-ruby
Architecture: all
-Depends: libaugeas-ruby1.8, ${misc:Depends}
+Depends: libaugeas-ruby1.9.1, ${misc:Depends}
Description: Augeas bindings for the Ruby language
Augeas is a configuration editing tool. It parses configuration files in their
native formats and transforms them into a tree. Configuration changes are made
by populating this tree and saving it back into native config files.
.
This is a dependency package which depends on Debian's default Ruby version
- (currently 1.8.x).
+ (currently 1.9.1).
Package: libaugeas-ruby1.8
Architecture: any
--- End Message ---
--- Begin Message ---
On Mon, 2012-07-16 at 23:01 -0400, Scott Kitterman wrote:
> Please unblock package libaugeas-ruby
>
> Fixes RC bug #680684.
Unblocked.
Regards,
Adam--- End Message ---
Processed: tagging 681719
Processing commands for cont...@bugs.debian.org: > tags 681719 + moreinfo Bug #681719 [release.debian.org] unblock: chromium-browser/20.0.1132.57~r145807-1 Added tag(s) moreinfo. > thanks Stopping processing here. Please contact me if you need assistance. -- 681719: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=681719 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: http://lists.debian.org/handler.s.c.13425537848362.transcr...@bugs.debian.org
Bug#681719: unblock: chromium-browser/20.0.1132.57~r145807-1
On Sun, Jul 15, 2012 at 17:48:32 -0400, Michael Gilbert wrote: > Package: release.debian.org > User: release.debian@packages.debian.org > Usertags: unblock > Severity: normal > > Please unblock package chromium-browser > > This is a new upstream stable release that fixes multiple security > issues, and an rc build failure on arm was fixed. > > unblock chromium-browser/20.0.1132.57~r145807-1 > Care to attach a debdiff? Cheers, Julien signature.asc Description: Digital signature
Re: Migration of emboss and embassy-* to testing?
Hi, Apologies for the delay in getting back to you about this. On Thu, 2012-07-05 at 08:55 +0200, Andreas Tille wrote: > On Thu, Jul 05, 2012 at 07:33:13AM +0100, Adam D. Barratt wrote: [...] > > leading: emboss,embassy-domainatrix,embassy-domalign,embassy-domsearch >> start: 30+0: i-4:a-0:a-0:a-5:i-0:k-6:k-6:m-0:m-0:p-0:s-1:s-6:s-2 >> orig: 30+0: i-4:a-0:a-0:a-5:i-0:k-6:k-6:m-0:m-0:p-0:s-1:s-6:s-2 >> easy: 31+0: i-4:a-1:a-0:a-5:i-0:k-6:k-6:m-0:m-0:p-0:s-1:s-6:s-2 > > * amd64: embassy-phylip > > > > FAILED > > I admit I can not make any sense out of the numbers you are mentioning > above but the reason embassy-phylip becomes obvious. They're the number of uninstallable packages per architecture; the key difference is the change from "a-0" to "a-1" indicating the newly installable (if the hint had succeeded) package on amd64. > Thanks for the > explanation. Would you consider to put a freeze exception on > embassy-phylip (option 1 of my previous mail which is probably welcome > to all Debian Med team members) or would you prefer falling back to > those other options I have mentioned (and these probably need discussion > in Debian Med team first). Dropping the most obvious build noise from the diff together with what could charitably be claimed as "documentation fixes" leaves a reasonably small set of changes. Given that the package is in non-free, I've unblocked it and hoped nothing breaks; if it does, we might then lean towards removal rather than another unblock. Regards, Adam -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1342553620.14254.9.ca...@jacala.jungle.funky-badger.org
Bug#681605: marked as done (unblock: geoip/1.4.8+dfsg-4)
Your message dated Tue, 17 Jul 2012 21:29:29 +0200 with message-id <20120717192929.gr7...@radis.cristau.org> and subject line Re: Bug#681605: unblock: geoip/1.4.8+dfsg-4 has caused the Debian Bug report #681605, regarding unblock: geoip/1.4.8+dfsg-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.) -- 681605: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=681605 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: unblock Please unblock package geoip It adds multiarch support: * Add multiarch support. * Add lintian override for false positive hardening-no-fortify-functions usr/lib/geoip/geoip-generator. * Wrap all debian/control fields. unblock geoip/1.4.8+dfsg-4 -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (200, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-3-amd64 (SMP w/6 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash --- End Message --- --- Begin Message --- On Sun, Jul 15, 2012 at 17:45:55 +0200, Cyril Brulebois wrote: > Hello, > > Patrick Matthäi (14/07/2012): > > It adds multiarch support: > > > > * Add multiarch support. > > that might be me, but it looks to me like that doesn't really match: > 2. changes for release goals, if they are not invasive; > > in http://release.debian.org/wheezy/freeze_policy.html > > It looks to me like it's just too late for that, unless you have a > very good reason. > Closing. Cheers, Julien signature.asc Description: Digital signature --- End Message ---
Bug#681604: marked as done (unblock: mlt/0.8.0-2)
Your message dated Tue, 17 Jul 2012 21:27:20 +0200 with message-id <20120717192720.gq7...@radis.cristau.org> and subject line Re: Bug#681604: unblock: mlt/0.8.0-2 has caused the Debian Bug report #681604, regarding unblock: mlt/0.8.0-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.) -- 681604: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=681604 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: unblock Please unblock package mlt It fixes three bugs reported at the Debian bts: * Add patch 01-changed-preset-path, which corrects the path to the changed location of the preset files. Closes: #681339 * Add patch 02-allow-file-prefix, which adds the file:// prefix support. Closes: #677276 * Add patch 03-audio-limits-and-crash, which fixes a crash if invalid audio bitrates are submitted. Closes: #681319 unblock mlt/0.8.0-2 -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (200, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-3-amd64 (SMP w/6 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash --- End Message --- --- Begin Message --- On Sat, Jul 14, 2012 at 19:18:23 +0200, Patrick Matthäi wrote: > Package: release.debian.org > Severity: normal > User: release.debian@packages.debian.org > Usertags: unblock > > Please unblock package mlt > > It fixes three bugs reported at the Debian bts: > > * Add patch 01-changed-preset-path, which corrects the path to the changed > location of the preset files. > Closes: #681339 > * Add patch 02-allow-file-prefix, which adds the file:// prefix support. > Closes: #677276 > * Add patch 03-audio-limits-and-crash, which fixes a crash if invalid audio > bitrates are submitted. > Closes: #681319 > > unblock mlt/0.8.0-2 > Unblocked. Kinda confused by the last one though, it seems you're leaving one slot nulled out in oc->streams, is other stuff going to be happy with that? Or should the later elements in that array get moved back? Cheers, Julien signature.asc Description: Digital signature --- End Message ---
Bug#681377: marked as done (unblock: libpdfbox-java/1:1.7.0+dfsg-2)
Your message dated Tue, 17 Jul 2012 21:17:55 +0200
with message-id <5005ba63.1000...@thykier.net>
and subject line Re: Bug#681377: (Fwd) Re: Bug#681377: unblock:
libpdfbox-java/1:1.7.0+dfsg-2
has caused the Debian Bug report #681377,
regarding unblock: libpdfbox-java/1:1.7.0+dfsg-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.)
--
681377: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=681377
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: unblock
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Please unblock package libpdfbox-java.
- -2 fixes the (at least) important bug #680778, the only change is is
an added dependency. Full debdiff attached.
unblock libpdfbox-java/1:1.7.0+dfsg-2
Thanks in advance,
gregor
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)
iQIcBAEBCAAGBQJP/xZsAAoJELs6aAGGSaoGyOIP/1IBWJspmKEMQ5AOPolDECrf
9eoSvJbDJXj38q5ULv77frlEK7moGAsQIp3Qpu/yj4mlqv8+YNN3oRXh3mCy683v
pxGJV5psW7SekDOQ+9M2eEpKO3+OmyFvljqigTBl6oKztXIh9mFmtaHd3bQtlxVO
tzKx2bZsDmH2fbRUWRXW7NG/6w0134h533VfGeBQ/EkaXw2qcMkLcnyLkSShgjla
p8uald6d3HTnW7NClBQ6GAgVmdP+wBuE1SzTvnN+K/SV0oBh0K+xI6SyQIRf1KVo
s7X8cjH+aEhF1ZvZjuzVwaai2jUJg/uNgeEukJgtHZuVmb9dsLM8Kmi+PXJDrYNB
daZuFI0gUBJnkgMprFUdJ/RRC8tIlUmGMzr05sUgEufSf0ZQVEqR806F/GiCdFuB
l+hw0ofcrk5yjMucJpZGA7RGmXLqH7Ll89MXIGZFNe7+77kAuA/MSorMzwv0QLnV
PA7CleEgO4U/iksVag73enMshIi/sb4nvFFdoYKrnVAQ0xd4W3zOoWQuPrWQ4Ps9
QF3U24rTd+NAm2z5H//0gHrUkLKcSstol7cCKbDHLumEWIsxyLCbNPqgRjCicFL7
3g584RciWRea8bQK2yxCABXa59wiW5P9zbAzjg26IlOTGo7WDLnZYmZxxVzuwq0z
8qZXJGBao8HHaUhI2oOr
=MdWe
-END PGP SIGNATURE-
diff -Nru libpdfbox-java-1.7.0+dfsg/debian/changelog libpdfbox-java-1.7.0+dfsg/debian/changelog
--- libpdfbox-java-1.7.0+dfsg/debian/changelog 2012-06-01 19:52:38.0 -0600
+++ libpdfbox-java-1.7.0+dfsg/debian/changelog 2012-07-12 12:20:19.0 -0600
@@ -1,3 +1,10 @@
+libpdfbox-java (1:1.7.0+dfsg-2) unstable; urgency=low
+
+ * debian/control: add dependency on libfontbox-java to libpdfbox-java.
+Thanks to Tom Parker for the bug report. (Closes: #680778)
+
+ -- gregor herrmann Thu, 12 Jul 2012 12:20:11 -0600
+
libpdfbox-java (1:1.7.0+dfsg-1) unstable; urgency=low
* New upstream release.
diff -Nru libpdfbox-java-1.7.0+dfsg/debian/control libpdfbox-java-1.7.0+dfsg/debian/control
--- libpdfbox-java-1.7.0+dfsg/debian/control 2012-06-01 19:52:38.0 -0600
+++ libpdfbox-java-1.7.0+dfsg/debian/control 2012-07-12 12:20:19.0 -0600
@@ -30,7 +30,7 @@
Package: libpdfbox-java
Architecture: all
-Depends: ${misc:Depends}
+Depends: ${misc:Depends}, libfontbox-java
Breaks: jabref (<< 2.7~beta1+ds-4)
Description: PDF library for Java
The Apache PDFBox library is an open source Java tool for working with PDF
--- End Message ---
--- Begin Message ---
On 2012-07-13 06:34, tony mancill wrote:
>> [...]
>>
>> I notice it does not add a class-path change in the Jar file; is this
>> class-path entry already present? According to the reporter, he also
>> added a class-path for it to work.
>>
>> ~Niels
>
> Hello Niels,
>
> Mea culpa (again). I misled Gregor regarding whether the classpath
> warning should be addressed for this upload. I have prepared an update
> for the package - debdiff attached - but not yet uploaded.
>
> Gregor, I have pushed this commit into the packaging repo, but wanted to
> hold off on the upload until you had a chance to take a look at it [1].
>
> Cheers,
> tony
>
> [1]
> http://anonscm.debian.org/gitweb/?p=pkg-java/libpdfbox-java.git;a=commitdiff;h=c64e01bf82430d2b0a9b8eb6d17d6c703c652c81
Hi,
I have unblocked libpdfbox-java/1:1.7.0+dfsg-3. Thanks for the fix.
~Niels--- End Message ---
Bug#681603: marked as done (unblock: libphysfs/2.0.2-7)
Your message dated Tue, 17 Jul 2012 21:21:11 +0200 with message-id <20120717192111.gp7...@radis.cristau.org> and subject line Re: Bug#681603: unblock: libphysfs/2.0.2-7 has caused the Debian Bug report #681603, regarding unblock: libphysfs/2.0.2-7 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.) -- 681603: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=681603 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: unblock Please unblock package libphysfs It adds multiarch support as requested with #680607 unblock libphysfs/2.0.2-7 -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (200, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-3-amd64 (SMP w/6 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash --- End Message --- --- Begin Message --- On Sat, Jul 14, 2012 at 19:15:54 +0200, Patrick Matthäi wrote: > Package: release.debian.org > Severity: normal > User: release.debian@packages.debian.org > Usertags: unblock > > Please unblock package libphysfs > > It adds multiarch support as requested with #680607 > multiarch conversions are too invasive at this point IMO. Plus, 2.0.2-7 has this change: + * Drop unused debian/libphysfs1.symbols file. which is either confused or confusing, because libphysfs1.symbols is very much included in 2.0.2-6, and as such used by dpkg-shlibdeps for any reverse dependency. So, not unblocking. Cheers, Julien signature.asc Description: Digital signature --- End Message ---
Processed: tagging 681496
Processing commands for cont...@bugs.debian.org: > tags 681496 + moreinfo Bug #681496 [release.debian.org] unblock: gunicorn/0.14.5-1 Added tag(s) moreinfo. > thanks Stopping processing here. Please contact me if you need assistance. -- 681496: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=681496 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: http://lists.debian.org/handler.s.c.134255256331925.transcr...@bugs.debian.org
Bug#681486: marked as done (unblock: cweb-latex/1.1.1.debian.1)
Your message dated Tue, 17 Jul 2012 21:15:23 +0200 with message-id <20120717191523.go7...@radis.cristau.org> and subject line Re: Bug#681486: unblock: cweb-latex/1.1.1.debian.1 has caused the Debian Bug report #681486, regarding unblock: cweb-latex/1.1.1.debian.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.) -- 681486: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=681486 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: unblock Please unblock package cweb-latex It was just reported to me via email that cweb-latex is now included in the current texlive packages. So I have uploaded a dummy transitional package which simply depends upon the appropriate texlive package instead, to avoid code duplication. My intention is to request the removal of this transitional package post-wheezy. unblock cweb-latex/1.1.1.debian.1 -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_GB.UTF-8) Shell: /bin/sh linked to /bin/dash --- End Message --- --- Begin Message --- On Fri, Jul 13, 2012 at 16:01:10 +0100, Julian Gilbey wrote: > Package: release.debian.org > Severity: normal > User: release.debian@packages.debian.org > Usertags: unblock > > Please unblock package cweb-latex > > It was just reported to me via email that cweb-latex is now included in > the current texlive packages. So I have uploaded a dummy transitional > package which simply depends upon the appropriate texlive package > instead, to avoid code duplication. My intention is to request the > removal of this transitional package post-wheezy. > > unblock cweb-latex/1.1.1.debian.1 > Unblocked, thanks. Cheers, Julien signature.asc Description: Digital signature --- End Message ---
Bug#681485: marked as done (unblock: rcs-latex/3.1.debian.1)
Your message dated Tue, 17 Jul 2012 21:13:00 +0200 with message-id <20120717191300.gn7...@radis.cristau.org> and subject line Re: Bug#681485: unblock: rcs-latex/3.1.debian.1 has caused the Debian Bug report #681485, regarding unblock: rcs-latex/3.1.debian.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.) -- 681485: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=681485 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: unblock Please unblock package rcs-latex It was just reported to me via email that rcs-latex is now included in the current texlive packages. So I have uploaded a dummy transitional package which simply depends upon the appropriate texlive package instead, to avoid code duplication. My intention is to request the removal of this transitional package post-wheezy. unblock rcs-latex/3.1.debian.1 -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_GB.UTF-8) Shell: /bin/sh linked to /bin/dash --- End Message --- --- Begin Message --- On Fri, Jul 13, 2012 at 16:00:20 +0100, Julian Gilbey wrote: > Package: release.debian.org > Severity: normal > User: release.debian@packages.debian.org > Usertags: unblock > > Please unblock package rcs-latex > > It was just reported to me via email that rcs-latex is now included in > the current texlive packages. So I have uploaded a dummy transitional > package which simply depends upon the appropriate texlive package > instead, to avoid code duplication. My intention is to request the > removal of this transitional package post-wheezy. > > unblock rcs-latex/3.1.debian.1 > Unblocked. Cheers, Julien signature.asc Description: Digital signature --- End Message ---
Bug#681463: marked as done (unblock: gyoto/0.0.3-5)
Your message dated Tue, 17 Jul 2012 21:07:55 +0200
with message-id <20120717190755.gm7...@radis.cristau.org>
and subject line Re: Bug#681463: unblock: gyoto/0.0.3-5
has caused the Debian Bug report #681463,
regarding unblock: gyoto/0.0.3-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.)
--
681463: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=681463
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: unblock
Please unblock package gyoto.
I attach a debdiff and explain the changes below.
1- Security Hardening Buld Flags Release Goal
http://bugs.debian.org/680242
Fix: pass build flags explicitly to make. I had to reshuffle some
symbolic targets in debian/rules to make it work reliably. Could be made
cleaner, but I tried to keep changes to a minimum.
2- test suite failed on kfreebsd-any
http://bugs.debian.org/679923
After checking, it appears that the "gyoto" executable from the gyoto
binary package fails to run on kfreebsd. However, the same functionality
is exposed to the Yorick interpreter by the yorick-gyoto package and
this binary package runs fine.
Fix:
- disable building the gyoto binary package on kfreebsd;
- don't let gyoto-dbg (or anything else) depend on it on kfreebsd;
- disable the test suite on kfreebsd, which requires the gyoto
executable to run.
3- test suite failed on some mips buildds
http://bugs.debian.org/681452
After checking, it appears that this failure does not affect all the
machines. It may just be that the test suite is too expensive to run on
some smaller/slower buildds.
Fix: disable test suite on mips. I then tested manually the autobuilt
binaries, which run fine (although slowwwly) in my qemu installation.
4- yorick is waiting for yorick-gyoto
The yorick-full meta-package (src:yorick), already unblocked, is waiting
for yorick-gyoto to build on kfreebsd-* before it can migrate.
http://release.debian.org/migration/testing.pl?package=yorick
Fixing the above-mentioned FTBFSes takes us halfway through to letting
yorick migrate. The other half is unblocking yp-svipc, already requested
here:
http://bugs.debian.org/681314
Kind regards, Thibaut.
unblock gyoto/0.0.3-5
diff -Nru gyoto-0.0.3/debian/changelog gyoto-0.0.3/debian/changelog
--- gyoto-0.0.3/debian/changelog2012-06-25 20:03:10.0 +0200
+++ gyoto-0.0.3/debian/changelog2012-07-13 11:36:16.0 +0200
@@ -1,5 +1,44 @@
+gyoto (0.0.3-5) unstable; urgency=low
+
+ * skip test suite on mips as lucatelli fails on it (but it runs fine on
+other boxes). (Closes: 681452)
+
+ -- Thibaut Paumard Fri, 13 Jul 2012 11:36:16
+0200
+
+gyoto (0.0.3-4) unstable; urgency=low
+
+ * gyoto-dbg must not depend on gyoto on kfreebsd-*, else it is
+uninstallable on these archs.
+
+ -- Thibaut Paumard Wed, 11 Jul 2012 14:30:02
+0200
+
+gyoto (0.0.3-3) unstable; urgency=low
+
+ * debian/control Architectures fields should not be folded: previous
+upload led to missing binary packages for some archs.
+
+ -- Thibaut Paumard Wed, 11 Jul 2012 13:02:34
+0200
+
+gyoto (0.0.3-2) unstable; urgency=low
+
+ * Bug fix: "FTBFS on kfreebsd-i386 and kfreebsd-amd64 (test suite)",
+(Closes: #679923). The previous "fix" did not work at all. The library
+and the Yorick interface work fine, but not the stand-alone application.
+Disable the "gyoto" binary package and the test suite on kfreebsd-*.
+
+ -- Thibaut Paumard Wed, 11 Jul 2012 11:20:09
+0200
+
+gyoto (0.0.3-1+exp1) experimental; urgency=low
+
+ * Bug fix: "FTBFS on kfreebsd-i386 and kfreebsd-amd64 (test suite)"
+(Closes: #679923).
+ * Tentative bug fix: "don't rely on yorick to pass the fortified build
+flags" using patch fix_679923_kfreebsd_FTBFS (Closes: #680242).
+
+ -- Thibaut Paumard Tue, 10 Jul 2012 10:50:50
+0200
+
gyoto (0.0.3-1) unstable; urgency=low
* Initial release (Closes: #640809)
- -- Thibaut Paumard Mon, 25 Jun 2012 20:03:10
+0200
+ -- Thibaut Paumard Fri, 22 Jun 2012 14:22:40
+0200
diff -Nru gyoto-0.0.3/debian/control gyoto-0.0.3/debian/control
--- gyoto-0.0.3/debian/control 2012-06-22 14:21:54.0 +0200
+++ gyoto-0.0.3/debian/control 2012-07-11 14:29:51.0 +0200
@@ -12,7 +12,7 @@
Homepage: http://gyoto.obspm.fr
Package: gyoto
-Architecture: any
+Architecture: linux-any hurd-any
Depends: ${shlibs:Depends}, ${misc:Depends}
Description: General relativistic ray-tracing
Gyoto is a framework for computing geodesics in curved
@@ -41,7 +41,7 @@
Ar
Processed: tagging 681448
Processing commands for cont...@bugs.debian.org: > tags 681448 + moreinfo Bug #681448 [release.debian.org] unblock: nsd3/3.2.11-1 Added tag(s) moreinfo. > thanks Stopping processing here. Please contact me if you need assistance. -- 681448: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=681448 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: http://lists.debian.org/handler.s.c.134255142925669.transcr...@bugs.debian.org
Bug#681377: (Fwd) Re: Bug#681377: unblock: libpdfbox-java/1:1.7.0+dfsg-2
On Fri, Jul 13, 2012 at 16:34:52 -0700, tony mancill wrote: > The reason I opted for "dh_link -O--buildsystem=ant" is that this is the > invocation that dh is using (based on setting DH_VERBOSE and observing > the build). I take it this is due d/rules containing: > > %: > dh $@ --buildsystem ant > > Although I don't suppose there's much chance of dh_link inheriting any > ant-specific behavior in the near future. > > I'll make the change and upload tonight. > The --buildsystem option is for dh (and dh_auto_*), not any other debhelper command. Cheers, Julien signature.asc Description: Digital signature
Bug#681327: marked as done (unblock: modsecurity-apache/2.6.6-2)
Your message dated Tue, 17 Jul 2012 20:51:50 +0200
with message-id <20120717185150.gj7...@radis.cristau.org>
and subject line Re: Bug#681327: unblock: modsecurity-apache/2.6.6-2
has caused the Debian Bug report #681327,
regarding unblock: modsecurity-apache/2.6.6-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.)
--
681327: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=681327
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: unblock
Please unblock package modsecurity-apache
A change in the license went unnoticed. Just debian/copyright was
updated.
debdiff attached.
unblock modsecurity-apache/2.6.6-2
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 3.2.0-2-686-pae (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
diff -Nru modsecurity-apache-2.6.6/debian/changelog
modsecurity-apache-2.6.6/debian/changelog
--- modsecurity-apache-2.6.6/debian/changelog 2012-06-15 13:22:03.0
+0200
+++ modsecurity-apache-2.6.6/debian/changelog 2012-07-02 17:23:28.0
+0200
@@ -1,3 +1,9 @@
+modsecurity-apache (2.6.6-2) unstable; urgency=low
+
+ * Updated debian/copyright with right license.
+
+ -- Alberto Gonzalez Iniesta Mon, 02 Jul 2012 17:23:08
+0200
+
modsecurity-apache (2.6.6-1) unstable; urgency=low
* New upstream release.
diff -Nru modsecurity-apache-2.6.6/debian/copyright
modsecurity-apache-2.6.6/debian/copyright
--- modsecurity-apache-2.6.6/debian/copyright 2012-03-16 13:23:17.0
+0100
+++ modsecurity-apache-2.6.6/debian/copyright 2012-07-02 17:21:53.0
+0200
@@ -1,163 +1,31 @@
-This package was debianized by
-Alberto Gonzalez Iniesta on Mon, 6 Nov 2006
-
-It was downloaded from http://www.modsecurity.org
-
-Copyright (C) 2004-2006 Breach Security, Inc. (http://www.breach.com)
-
-Copyright:
-
- This package is free software; you can redistribute it and/or modify
- it under the terms of the GNU General Public License as published by
- the Free Software Foundation; version 2 dated June, 1991.
-
- This package is distributed in the hope that it will be useful,
- but WITHOUT ANY WARRANTY; without even the implied warranty of
- MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
- GNU General Public License for more details.
-
- You should have received a copy of the GNU General Public License
- along with this package; if not, write to the Free Software
- Foundation, Inc., 51 Franklin St, Fifth Floor, Boston,
- MA 02110-1301, USA.
-
-On Debian GNU/Linux systems, the complete text of the GNU General
-Public License can be found in `/usr/share/common-licenses/GPL-2'.
-
-
-MODSECURITY LICENSING EXCEPTION
-===
-
-Version 1.0, 29 July 2008
-
-As a special exception ("Exception") to the terms and conditions of version 2
-of the GPL, Breach Security, Inc. hereby grants you the rights described
-below, provided you agree to the terms and conditions in this Exception,
-including its obligations and restrictions on use.
-
-
-Exception Intent
-
-
-We want specified Free/Libre and Open Source Software ("FLOSS") programs to be
-able to use ModSecurity (the "Program") despite the fact that not all FLOSS
-licenses are compatible with version 2 of the GNU General Public License (the
-"GPLv2").
-
-
-Legal Terms and Conditions
-==
-
-You are free to distribute a Derivative Work that is formed entirely from the
-Program and one or more works (each, a "FLOSS Work") licensed under one or
-more of the licenses listed below in section 1, as long as all of the
-following conditions are met:
-
- 1. You obey the GPLv2 in all respects for the Program and the Derivative
- Work, except for identifiable sections of the Derivative Work which are
-
- 1. not derived from the Program, and
-
- 2. are not designed to interact with the Program, and
-
- 3. which can reasonably be considered independent and separate works in
-themselves.
-
- 2. All such identifiable sections of the Derivative Work are
-
- 1. distributed subject to one of the FLOSS licenses listed below, and
-
- 2. the object code or executable form of those sections are accompanied
-by the complete corresponding machine-readable source code for those
-sections on the same medium and
Bug#681220: marked as done (unblock: puppet/2.7.18-1)
Your message dated Tue, 17 Jul 2012 20:44:13 +0200 with message-id <20120717184413.gh7...@radis.cristau.org> and subject line Re: Bug#681220: unblock: puppet/2.7.18-1 has caused the Debian Bug report #681220, regarding unblock: puppet/2.7.18-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.) -- 681220: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=681220 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: unblock Please unblock package puppet The 2.8.18 upstream release is a security release, fixing four security issues. - http://puppetlabs.com/security/cve/cve-2012-3864/ - http://puppetlabs.com/security/cve/cve-2012-3865/ - http://puppetlabs.com/security/cve/cve-2012-3866/ - http://puppetlabs.com/security/cve/cve-2012-3867/ The 2.7.18-1 debian release restricts puppet 2.7 to ruby1.8 only, it is not compatible with ruby 1.9.1, and this is not supported upstream. Puppet 2.7.17 was packaged for both ruby versions. - http://docs.puppetlabs.com/guides/platforms.html unblock puppet/2.7.18-1 -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-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 Wed, Jul 11, 2012 at 15:55:59 +0200, Stig Sandbeck Mathisen wrote: > Package: release.debian.org > Severity: normal > User: release.debian@packages.debian.org > Usertags: unblock > > Please unblock package puppet > > The 2.8.18 upstream release is a security release, fixing four security > issues. > > - http://puppetlabs.com/security/cve/cve-2012-3864/ > - http://puppetlabs.com/security/cve/cve-2012-3865/ > - http://puppetlabs.com/security/cve/cve-2012-3866/ > - http://puppetlabs.com/security/cve/cve-2012-3867/ > unblocked. Cheers, Julien signature.asc Description: Digital signature --- End Message ---
Bug#681314: marked as done (unblock: yp-svipc/0.14-2)
Your message dated Tue, 17 Jul 2012 20:47:46 +0200
with message-id <20120717184746.gi7...@radis.cristau.org>
and subject line Re: Bug#681314: unblock: yp-svipc/0.14-2
has caused the Debian Bug report #681314,
regarding unblock: yp-svipc/0.14-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.)
--
681314: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=681314
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: unblock
Please unblock source package yp-svipc.
It builds the following binary packages:
- python-svipc
- python3-svipc
- yorick-svipc
I attach a debdiff and explain the changes below.
1- Hardening flags release goal:
http://bugs.debian.org/680216
Fixed for python*-svipc by putting CPPFLAGS in CFLAGS, for yorick-svipc by
passing Y_LDFLAGS etc. to make.
2- 0.14-1 failed to build on kfreebsd-any:
http://bugs.debian.org/679919
Portability code for *BSD and Darwin is erroneously activated on GNU/kFreeBSD,
which doesn't need it.
Fixed for python*-svipc by patching setup.py; for yorick-svipc by passing
PKG_CFLAGS explicitly to make.
3- the yorick-full meta-package (src:yorick), already unblocked, is waiting for
yorick-svipc to build on kfreebsd-* before it can migrate.
http://release.debian.org/migration/testing.pl?package=yorick
Fixing the above-mentioned FTBFS takes us halfway through to letting yorick
migrate (Yorick is also waiting for yorick-gyoto, I'm working on it).
Kind regards, Thibaut.
unblock yp-svipc/0.14-2
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 3.2.0-2-686-pae (SMP w/2 CPU cores)
diff -Nru yp-svipc-0.14/debian/changelog yp-svipc-0.14/debian/changelog
--- yp-svipc-0.14/debian/changelog 2012-06-22 11:25:24.0 +0200
+++ yp-svipc-0.14/debian/changelog 2012-07-11 13:41:39.0 +0200
@@ -1,3 +1,14 @@
+yp-svipc (0.14-2) unstable; urgency=low
+
+ * Bug fix: "don't rely on yorick to pass the fortified build flags"
+(Closes: #680216).
+ * Bug fix: "FTBFS on kfreebsd-i386 and kfreebsd-amd64: "conflicting
+types for semtimedop"" (Closes: #679919). Involves a patch for the
+Python modules (fix_679919_kFreeBSD_FTBFS) and passing PKG_CFLAGS when
+building the Yorick plug-in.
+
+ -- Thibaut Paumard Wed, 11 Jul 2012 13:41:39 +0200
+
yp-svipc (0.14-1) unstable; urgency=low
* Initial release (Closes: #668841)
diff -Nru yp-svipc-0.14/debian/patches/fix_679919_kFreeBSD_FTBFS yp-svipc-0.14/debian/patches/fix_679919_kFreeBSD_FTBFS
--- yp-svipc-0.14/debian/patches/fix_679919_kFreeBSD_FTBFS 1970-01-01 01:00:00.0 +0100
+++ yp-svipc-0.14/debian/patches/fix_679919_kFreeBSD_FTBFS 2012-07-11 13:58:53.0 +0200
@@ -0,0 +1,24 @@
+Description: fix 679919 FTBFS on kfreebsd-*
+ upstream provides an implementation of semtimedop which they use on FreeBSD
+ and MacOS. It is eroneously used also under GNU/kFreeBSD and GNU/Hurd.
+ This patch disables it altogether for the python modules.
+Author: Thibaut Paumard
+Origin: vendor
+Bug-Debian: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=679919
+Forwarded: no
+Last-Update: 2012-07-11
+---
+This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
+--- a/setup.py
b/setup.py
+@@ -32,10 +32,8 @@
+('SVIPC_NOSEGFUNC', None),
+]
+
+ platform=uname()[0]
+-if platform != 'Linux':
+- define_macros.append(('SVIPC_HACKS', None))
+
+ extra_compile_args=[
+#'-g3',
+#'-ggdb3'
diff -Nru yp-svipc-0.14/debian/patches/series yp-svipc-0.14/debian/patches/series
--- yp-svipc-0.14/debian/patches/series 1970-01-01 01:00:00.0 +0100
+++ yp-svipc-0.14/debian/patches/series 2012-07-11 14:08:11.0 +0200
@@ -0,0 +1 @@
+fix_679919_kFreeBSD_FTBFS
diff -Nru yp-svipc-0.14/debian/rules yp-svipc-0.14/debian/rules
--- yp-svipc-0.14/debian/rules 2012-06-22 11:25:06.0 +0200
+++ yp-svipc-0.14/debian/rules 2012-07-11 14:17:49.0 +0200
@@ -6,6 +6,7 @@
# This has to be exported to make some magic below work.
export DH_OPTIONS
+CFLAGS += $(CPPFLAGS)
%:
dh $@ --with python2 \
@@ -23,7 +24,10 @@
set -ex; for python in $(shell py3versions -r); do \
$$python setup.py build; \
done;
- cd yorick; make
+ cd yorick; make COPT_DEFAULT="" \
+ Y_CFLAGS="$(CFLAGS)" \
+ Y_LDFLAGS="$(LDFLAGS)" \
+ PKG_CFLAGS="-I ../common"
override_dh_auto_install:
dh_auto_install
--- End Message ---
--- Begin Message ---
Bug#681110: unblock: sdl-stretch/0.3.1-3
2012/7/17 Julien Cristau :
>> There's an unblock already for sdl-stretch/0.3.1-2 because it was in
>> unstable before the freeze, but -2 failed to build in kfreebsd-i386
>> and thus it never migrated to testing:
>>
>>
>> https://buildd.debian.org/status/logs.php?pkg=sdl-stretch&arch=kfreebsd-i386
>>
>> I produced -3 and asked the package to be removed from
>> "Packages-arch-specific" (see #680275) so it would build in
>> kfreebsd-amd64 and amd64 [1], but we were asked to restrict the
>> architectures ourselves first (any-amd64 any-386) in a new
>> revision/upload of the package before granting the removal.
>>
>> The package doesn't have rdepends, so this unblock shoudln't cause much
>> impact:
>>
> The package doesn't have rdepends, so the lack of an unblock shouldn't
> cause much impact. Are there users requesting this package on kbsd64,
> or another reason why this is particularly important to add now?
The situation is a bit messy, I hope that I can explain myself in the
next few paragraphs.
I figured out that if -2 was to be allowed, -3 could be as well; and
it's not only kfreebsd-amd64 but amd64 itself, which is probably the
most important architecture by now.
The thing is, sdl-stretch is a relatively unimportant package in the
SDL-team realm, so we attended other packages first (most were
abandoned by the end of 2011). Recently I went to look why
sdl-stretch wasn't migrating, and I discovered that it had a
restriction in "packages-arch-specific" that was restricting it for
386 only. I checked with upstream and the package is actually
amd64-capable (it contains assembler routines, so it's not available
for any actitectures), but it was restricted to 386 in Debian since
2005 or so.
The amd64 package is actually present because we built it with
pbuilder in amd64 arch and uploaded it, but if the package was to be
rebuilt when the P-A-S restriction was in place, it wouldn't build in
amd64 in the buildds.
OTOH, -2 was not restricted in debian/control to amd64 and i386
architectures (which is the thing that I fixed in -3), so if it's
rebuilt now, it will try to be built in all architectures, and in some
of them it will probably fail, thus causing a FTBFS later in the
freeze period or beyond (once released).
So I think that the best thing to do is to allow -3 to go in, the only
actual change it's the restriction on architectures (see debdiff
attached), and it was requested before buildd team accepted to remove
it from the P-A-S file:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=680275
Cheers.
--
Manuel A. Fernandez Montecelo
diff -Nru sdl-stretch-0.3.1/debian/changelog sdl-stretch-0.3.1/debian/changelog
--- sdl-stretch-0.3.1/debian/changelog 2012-04-26 15:51:26.0 +0100
+++ sdl-stretch-0.3.1/debian/changelog 2012-07-04 20:25:34.0 +0100
@@ -1,3 +1,22 @@
+sdl-stretch (0.3.1-3) unstable; urgency=low
+
+ * Change "Architecture: any-amd64 any-i386" for both binary packages.
+
+This package is a bit special because it contains optimised routines in
+assembler for some architectures, so even if it can be built successfully
in
+others, it doesn't really make sense to provide the package. According to
+upstream, current models of both i386 and amd64 are supported, and while
+it's desired to have support in other platforms (e.g. ARM), it's not there
+yet.
+
+Before 0.3.1-1, debian/control was set only to build on i386; and in
0.3.1-1
+it was set to "any", but the file
+https://buildd.debian.org/quinn-diff/sid/Packages-arch-specific restricted
+the architectures effectively to "i386 kfreebsd-i386 hurd-i386" (see
+#680275).
+
+ -- Manuel A. Fernandez Montecelo Wed, 04 Jul
2012 20:12:03 +0100
+
sdl-stretch (0.3.1-2) unstable; urgency=low
* Bump Standards-Version to 3.9.3 (no changes needed)
diff -Nru sdl-stretch-0.3.1/debian/control sdl-stretch-0.3.1/debian/control
--- sdl-stretch-0.3.1/debian/control2012-04-26 15:51:35.0 +0100
+++ sdl-stretch-0.3.1/debian/control2012-07-04 20:07:19.0 +0100
@@ -17,7 +17,7 @@
Homepage: http://sdl-stretch.sourceforge.net
Package: libsdl-stretch-0-3
-Architecture: any
+Architecture: any-amd64 any-i386
Multi-Arch: same
Pre-Depends: ${misc:Pre-Depends}
Depends: ${shlibs:Depends},
@@ -33,7 +33,7 @@
Package: libsdl-stretch-dev
Section: libdevel
-Architecture: any
+Architecture: any-amd64 any-i386
Depends: ${misc:Depends},
libsdl-stretch-0-3 (= ${binary:Version}),
libsdl1.2-dev(>= 1.2.14~)
Processed: Re: Bug#681196: unblock: tryton-proteus/2.2.2-3
Processing commands for cont...@bugs.debian.org: > tag 681196 moreinfo Bug #681196 [release.debian.org] unblock: tryton-proteus/2.2.2-4 Added tag(s) moreinfo. > kthxbye Stopping processing here. Please contact me if you need assistance. -- 681196: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=681196 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: http://lists.debian.org/handler.s.c.134255007518136.transcr...@bugs.debian.org
Bug#681196: unblock: tryton-proteus/2.2.2-3
tag 681196 moreinfo kthxbye On Wed, Jul 11, 2012 at 12:11:14 +0200, Mathias Behrle wrote: > Package: release.debian.org > Severity: normal > User: release.debian@packages.debian.org > Usertags: unblock > > Please unblock package tryton-proteus. The -3 upload fixes the #680817 FTBFS, > revealed by a Lucas-powered rebuild. > 680817 is still open. Cheers, Julien signature.asc Description: Digital signature
Bug#681130: marked as done (unblock: otrs2/3.1.7+dfsg1-2)
Your message dated Tue, 17 Jul 2012 20:32:32 +0200 with message-id <20120717183232.gf7...@radis.cristau.org> and subject line Re: Bug#681130: unblock: otrs2/3.1.7+dfsg1-2 has caused the Debian Bug report #681130, regarding unblock: otrs2/3.1.7+dfsg1-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.) -- 681130: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=681130 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: unblock Please unblock package otrs2 It is a (important) bugfix only release and also a few Debian bugs have been fixed. I will try to summarize: Debian: * Add patch 26-font-paths, which adds the full paths to the font files, so that the PDF export will not die. => All PDF exports of otrs will fail, since the wrong paths for the font files are used by default All upstream changes (source: http://source.otrs.org/viewvc.cgi/otrs/CHANGES?view=markup ).. Related to Debian: - 2012-06-18 Fixed bug#8593 - Wrong description for 'Agent Notifications' on Admin interface. - 2012-06-18 Fixed bug#8587 - Typo in French translation. - 2012-06-15 Fixed bug#7879 - Broken Content-Type in forwarded attachments. - 2012-06-15 Fixed bug#8583 - Unneeded complexity and performance degradation creating Service Lists (Replacement for bug fix 7947). - 2012-06-15 Fixed bug#8580 - SQL warnings for CustomerCompanyGet on some database backends. - 2012-06-14 Fixed bug#8251 - Defect handling of invalid Queues in AJAX refresh. - 2012-06-14 Fixed bug#8574 - Perl special variable $/ is changed and never restored. - 2012-06-14 Fixed bug#8337 - Parentheses in user last_name / first_name are not sanitized (follow-up fix). - 2012-06-12 Fixed bug#8575 - Assignment of users does not work for responsible or owner permission in AgentTicketPhone. - 2012-06-12 Updated Hungarian translation, thanks to Németh Csaba! - 2012-06-12 Updated Danish translation, thanks to Lars Jørgensen! - 2012-06-12 Fixed bug#7872 - "Created" date in Large view is actually Last Updated date. - 2012-06-12 Fixed bug#8457 - Paste on a newly created ckeditor instance does not work on webkit based browsers. - 2012-06-11 Fixed bug#8565 - Exportfile action from otrs.PackageManager.pl is broken. - 2012-06-11 Fixed bug#8544 - Hovering ticket title is still shortened. - 2012-06-07 Fixed bug#8553 - Agent notifications can't be loaded from the database in some scenarios. - 2012-06-05 Fixed bug#8383 - Email address in 'To' field is lost after second reload if address is not in customer database. - 2012-06-06 Fixed bug#8549 - "Need User" warning in error log when creating a ticket for a customer not in DB. - 2012-06-05 Fixed bug#8546 - LinkObject Type is not translated in ticket zoom. - 2012-06-04 Fixed bug#7533 - SQL error if body contains only a picture. - 2012-06-04 Fixed bug#2626 - Default Service does not work for "unknown" customers. You can use the new setting "Ticket::Service::Default::UnknownCustomer" to specify if unknown customers should also receive the default services. - 2012-06-04 Improved performance of TemplateGenerator.pm, thanks to Stelios Gikas! - 2012-05-31 Fixed bug#8481 - Dynamic Fields lost after ticket move to another queue (using quick move Dropdown). Unrelated to Debian and not included in the deb packaging: - 2012-06-11 Fixed bug#8458 - $OTRS_SCHEDULER -a start missing from /etc/init.d/otrs after update. - 2012-06-11 Fixed bug#8139 - SUSE RPM has no dependency on Date::Format perl module. - 2012-05-31 Fixed bug#8533 - Apache will not start using mod_perl on Fedora 16. Sorry that this update comes so late, it was planned with some OTRS stuffs for a few weeks later so I also could upload this bugfix release before Debian freezes and before my VAC, but it was delayed :( unblock otrs2/3.1.7+dfsg1-2 -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (200, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-3-amd64 (SMP w/6 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash --- End Message --- --- Begin Message --- On Tue, Jul 10, 2012 at 22:18:10 +0200, Patrick Matthäi wrote: > unblock otrs2/3.1.7+dfsg1-2 >
Bug#681110: unblock: sdl-stretch/0.3.1-3
On Tue, Jul 10, 2012 at 18:33:46 +0100, Manuel A. Fernandez Montecelo wrote: > I would like to ask an unblock to sdl-stretch/0.3.1-3 > > There's an unblock already for sdl-stretch/0.3.1-2 because it was in > unstable before the freeze, but -2 failed to build in kfreebsd-i386 > and thus it never migrated to testing: > > https://buildd.debian.org/status/logs.php?pkg=sdl-stretch&arch=kfreebsd-i386 > > I produced -3 and asked the package to be removed from > "Packages-arch-specific" (see #680275) so it would build in > kfreebsd-amd64 and amd64 [1], but we were asked to restrict the > architectures ourselves first (any-amd64 any-386) in a new > revision/upload of the package before granting the removal. > > The package doesn't have rdepends, so this unblock shoudln't cause much > impact: > The package doesn't have rdepends, so the lack of an unblock shouldn't cause much impact. Are there users requesting this package on kbsd64, or another reason why this is particularly important to add now? Cheers, Julien signature.asc Description: Digital signature
Bug#681002: release.debian.org: Freeze exception for libguestfs
On Tue, Jul 10, 2012 at 08:28:10 +0200, Hilko Bengen wrote: > There have been three minor upstream releases since 1.18.1. The project > is based around autoconf/automake (57 Makefile.am files), and much of > the source code for the various language bindings is automatically > generated, so there are more than a few "false positives". > > If this is still not acceptable, what about a 1.18.2-2wheezy1 that just > fixes #678977 (upgrade breakage due to multiarch change), #680885, > #680886 (multiarch coinstall)? > wheezy is not affected by any of those 3 bugs as far as I can tell, since they're all related to the multiarch switch which isn't in 1:1.18.1-1. Cheers, Julien signature.asc Description: Digital signature
Bug#681911: marked as done (unblock: apparmor/2.7.103-4)
Your message dated Tue, 17 Jul 2012 19:10:08 +0100 with message-id <1342548608.14254.1.ca...@jacala.jungle.funky-badger.org> and subject line Re: Bug#681911: unblock: apparmor/2.7.103-4 has caused the Debian Bug report #681911, regarding unblock: apparmor/2.7.103-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.) -- 681911: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=681911 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: unblock Please unblock package apparmor Version 2.7.103-3 contains fixes for an RC bug[1] and a piuparts failure. Debdiff attached. Thanks! -Kees [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=679597 [2] http://piuparts.debian.org/sid/source/a/apparmor.html unblock apparmor/2.7.103-4 -- System Information: Debian Release: wheezy/sid APT prefers precise-updates APT policy: (500, 'precise-updates'), (500, 'precise-security'), (500, 'precise') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-26-generic (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 diff -Nru apparmor-2.7.103/debian/apparmor-profiles.dirs apparmor-2.7.103/debian/apparmor-profiles.dirs --- apparmor-2.7.103/debian/apparmor-profiles.dirs 2012-06-28 22:17:27.0 -0700 +++ apparmor-2.7.103/debian/apparmor-profiles.dirs 2012-06-29 01:24:51.0 -0700 @@ -1 +1,3 @@ /etc/apparmor.d/local +/etc/apparmor.d/abstractions/ubuntu-browsers.d +/etc/apparmor.d/abstractions diff -Nru apparmor-2.7.103/debian/changelog apparmor-2.7.103/debian/changelog --- apparmor-2.7.103/debian/changelog 2012-06-29 00:43:20.0 -0700 +++ apparmor-2.7.103/debian/changelog 2012-07-16 11:54:14.0 -0700 @@ -1,3 +1,12 @@ +apparmor (2.7.103-4) unstable; urgency=low + + * debian/apparmor-profiles.dirs: add directories we might collide +with apparmor on during purge. + * debian/patches/fix-network-rule-support.patch: handle lack of +networking features correctly (Closes: 679597). + + -- Kees Cook Mon, 16 Jul 2012 11:52:42 -0700 + apparmor (2.7.103-3) unstable; urgency=low * debian/control: drop deprecated XS-Python-Version (Closes: 673062). diff -Nru apparmor-2.7.103/debian/patches/fix-network-rule-support.patch apparmor-2.7.103/debian/patches/fix-network-rule-support.patch --- apparmor-2.7.103/debian/patches/fix-network-rule-support.patch 1969-12-31 16:00:00.0 -0800 +++ apparmor-2.7.103/debian/patches/fix-network-rule-support.patch 2012-07-16 11:52:23.0 -0700 @@ -0,0 +1,20 @@ +Description: handle missing network mediation support. +Author: John Johansen +Bug-Debian: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=679597 + +Index: apparmor-debian/parser/parser_main.c +=== +--- apparmor-debian.orig/parser/parser_main.c 2012-06-28 22:17:27.433492000 -0700 apparmor-debian/parser/parser_main.c 2012-07-16 11:51:23.742020178 -0700 +@@ -1182,7 +1182,10 @@ + write_cache = 0; + skip_read_cache = 1; + return; +- } ++ } else if (strstr(flags_string, "network")) ++ kernel_supports_network = 1; ++ else ++ kernel_supports_network = 0; + + /* + * Deal with cache directory versioning: diff -Nru apparmor-2.7.103/debian/patches/series apparmor-2.7.103/debian/patches/series --- apparmor-2.7.103/debian/patches/series 2012-06-28 22:17:27.0 -0700 +++ apparmor-2.7.103/debian/patches/series 2012-07-16 11:50:18.0 -0700 @@ -9,3 +9,4 @@ abstractions-ubuntu-browsers.patch pass-compiler-flags.patch non-linux.patch +fix-network-rule-support.patch --- End Message --- --- Begin Message --- On Tue, 2012-07-17 at 10:17 -0700, Kees Cook wrote: > Please unblock package apparmor > > Version 2.7.103-3 contains fixes for an RC bug[1] and a piuparts failure. Unblocked; thanks. Regards, Adam--- End Message ---
Bug#680785: marked as done (unblock: xen/4.1.3~rc1+hg-20120614.a9c0a89c08f2-4)
Your message dated Tue, 17 Jul 2012 20:01:47 +0200 with message-id <20120717180147.gc7...@radis.cristau.org> and subject line Re: Please unblock xen/4.1.3~rc1+hg-20120614.a9c0a89c08f2-4 has caused the Debian Bug report #680785, regarding unblock: xen/4.1.3~rc1+hg-20120614.a9c0a89c08f2-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.) -- 680785: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=680785 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: unblock Please unblock package xen. It fixes upgrades between incompatible versions by removing /usr/lib/xen-default. Also it fixes an oversight in the init script name and finally uses udev to manage qemu network devices. And set Built-Using to the correct value. unblock xen/4.1.3~rc1+hg-20120614.a9c0a89c08f2-4 xen (4.1.3~rc1+hg-20120614.a9c0a89c08f2-4) unstable; urgency=low * Add Build-Using info to xen-utils package. * Fix build-arch target. -- Bastian Blank Sun, 01 Jul 2012 19:52:30 +0200 xen (4.1.3~rc1+hg-20120614.a9c0a89c08f2-3) unstable; urgency=low * Remove /usr/lib/xen-default. It breaks systems if xenstored is not compatible. * Fix init script usage. * Fix udev rules for emulated network devices: - Force names of emulated network devices to a predictable name. -- Bastian Blank Sun, 01 Jul 2012 16:59:04 +0200 --- End Message --- --- Begin Message --- On Sat, Jul 14, 2012 at 12:55:18 +0200, Julien Cristau wrote: > On Sun, Jul 1, 2012 at 20:28:54 +0200, Bastian Blank wrote: > > > * Fix build-arch target. > > > From the build log: > dpkg-buildpackage: warning: debian/rules must be updated to support the > 'build-arch' and 'build-indep' targets (at least 'build-arch' seems to be > missing) > and then it uses debian/rules build instead. So probably not fixed > enough? > > Also the built-using substvar should probably be passed as a parameter > to dh_gencontrol rather than manually playing with debhelper files > directly. > > Unblocked anyway... > *sigh* so there was both a plain mail to the list and a bug, I replied to the former, and didn't notice the latter. Yay for wasted time. Closing now. Cheers, Julien signature.asc Description: Digital signature --- End Message ---
Possible freeze exception for texlive-bin
Dear release managers,
before uploading to unstable I would concur with you about
possible freeze exception for texlive-bin.
The changes in the release I would like to upload are two-fold:
* documentation/format/lintian warning fixes
. some spaces in control files
. additional WIP dep5 copyright file
not replacing the current copyright file, not installed, just
in the source
. better descriptions in the control file
* code change for ptex
recently a bug in ptex (Japanese Publishing TeX) was reported in the
Japanese TeX forum and immediately afterwards fixed in the
TeX Live upstream svn repository.
The code change is minimal:
--- texlive-bin-2012.20120628.orig/texk/web2c/ptexdir/ptex-base.ch
2012-05-12 21:40:41.0 +0900
+++ texlive-bin-2012.20120628/texk/web2c/ptexdir/ptex-base.ch 2012-07-18
02:19:29.125987453 +0900
@@ -2149,7 +2149,7 @@
else if cur_tok255)and(cur_cmd255)and((cur_cmdmax_char_code)) then
begin print_err("Improper alphabetic or KANJI constant");
@.Improper alphabetic constant@>
help2("A one-character control sequence belongs after a ` mark.")@/
and the test case is easy to check. The following TeX code:
\newcount\foo
\foo`\A
\showthe\foo % 65
\foo`\AA % !?
\showthe\foo
\bye
should break, as it doe sin etex:
...
?
! Improper alphabetic constant.
\AA
l.4 \foo`\AA
% !?
while in ptex the \AA is accepted:
(./test.tex
> 65.
l.3 \showthe\foo
% 65
?
> 452.
l.5 \showthe\foo
?
)
No pages of output.
I don't consider any of these *essential* for the stable release,
so I wanted to ask before doing an upload to unstable that might
generate problems later.
So please let me know what you think, if this is ok for stable
or I should wait and leave it like it is for now!
Thanks a lot and all the best
Norbert
Norbert Preiningpreining@{jaist.ac.jp, logic.at, debian.org}
JAIST, Japan TeX Live & Debian Developer
DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094
BELPER
A knob of someone else's chewing gum which you unexpectedly find your
hand resting on under a deck's top, under the passenger seat of your
car or on somebody's thigh under their skirt.
--- Douglas Adams, The Meaning of Liff
--
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120717180212.ge8...@gamma.logic.tuwien.ac.at
Re: Please unblock xen/4.1.3~rc1+hg-20120614.a9c0a89c08f2-4
On Sat, Jul 14, 2012 at 12:55:18 +0200, Julien Cristau wrote: > On Sun, Jul 1, 2012 at 20:28:54 +0200, Bastian Blank wrote: > > > * Fix build-arch target. > > > From the build log: > dpkg-buildpackage: warning: debian/rules must be updated to support the > 'build-arch' and 'build-indep' targets (at least 'build-arch' seems to be > missing) > and then it uses debian/rules build instead. So probably not fixed > enough? > > Also the built-using substvar should probably be passed as a parameter > to dh_gencontrol rather than manually playing with debhelper files > directly. > > Unblocked anyway... > *sigh* so there was both a plain mail to the list and a bug, I replied to the former, and didn't notice the latter. Yay for wasted time. Closing now. Cheers, Julien signature.asc Description: Digital signature
Bug#680729: marked as done (unblock: google-perftools/2.0-3)
Your message dated Tue, 17 Jul 2012 19:57:38 +0200
with message-id <20120717175738.gb7...@radis.cristau.org>
and subject line Re: Bug#680729: unblock: google-perftools/2.0-3
has caused the Debian Bug report #680729,
regarding unblock: google-perftools/2.0-3
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.)
--
680729: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=680729
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: unblock
Please unblock package google-perftools
The package in unstable fixes the following issues, which would be of use
for users and us.
* debian/patches/20120708_ppc_ftbfs.patch: Imported Ubuntu's patch, fixing
a build failure on powerpc, derived from the upstream:
http://code.google.com/p/gperftools/issues/detail?id=431
Thanks to James Page . (Closes: #680305)
* debian/control: Bumped up to libunwind8-dev for Build-Depends.
(Closes: #680724)
Regards,
Daigo
unblock google-perftools/2.0-3
-- System Information:
Debian Release: 6.0.5
APT prefers stable
APT policy: (990, 'stable'), (500, 'stable-updates'), (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores)
Locale: LANG=ja_JP.UTF-8, LC_CTYPE=ja_JP.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
diff -u google-perftools-2.0/debian/control google-perftools-2.0/debian/control
--- google-perftools-2.0/debian/control
+++ google-perftools-2.0/debian/control
@@ -2,7 +2,7 @@
Section: libs
Priority: optional
Maintainer: Daigo Moriwaki
-Build-Depends: cdbs, autoconf, automake1.9, libtool, patchutils, debhelper (>= 9.0.0), binutils, libunwind7-dev [amd64]
+Build-Depends: cdbs, autoconf, automake1.9, libtool, patchutils, debhelper (>= 9.0.0), binutils, libunwind8-dev [amd64]
Build-Conflicts: autoconf2.13, automake1.4
Standards-Version: 3.9.3
Homepage: http://code.google.com/p/gperftools/
diff -u google-perftools-2.0/debian/changelog google-perftools-2.0/debian/changelog
--- google-perftools-2.0/debian/changelog
+++ google-perftools-2.0/debian/changelog
@@ -1,3 +1,14 @@
+google-perftools (2.0-3) unstable; urgency=low
+
+ * debian/patches/20120708_ppc_ftbfs.patch: Imported Ubuntu's patch, fixing
+a build failure on powerpc, derived from the upstream:
+http://code.google.com/p/gperftools/issues/detail?id=431
+Thanks to James Page . (Closes: #680305)
+ * debian/control: Bumped up to libunwind8-dev for Build-Depends.
+(Closes: #680724)
+
+ -- Daigo Moriwaki Sun, 08 Jul 2012 18:08:36 +0900
+
google-perftools (2.0-2) unstable; urgency=low
* Some include files were left out of the package.
only in patch2:
unchanged:
--- google-perftools-2.0.orig/debian/patches/20120708_ppc_ftbfs.patch
+++ google-perftools-2.0/debian/patches/20120708_ppc_ftbfs.patch
@@ -0,0 +1,45 @@
+Description: Resolve issue with FTBFS on 32bit ppc platform
+ .
+ NoBarrier versions for Atomic64 can be implemented on PPC32
+Origin: http://code.google.com/p/gperftools/issues/detail?id=431
+
+Index: google-perftools/src/base/atomicops-internals-linuxppc.h
+===
+--- google-perftools.orig/src/base/atomicops-internals-linuxppc.h 2012-06-27 09:25:34.879532000 +0100
google-perftools/src/base/atomicops-internals-linuxppc.h 2012-07-04 21:18:36.974406885 +0100
+@@ -369,14 +369,20 @@
+ return *ptr;
+ }
+
+-#ifdef __PPC64__
+-
+-// 64-bit Versions.
+-
++// NoBarrier versions for Atomic64 can be implemented on PPC32
+ inline void NoBarrier_Store(volatile Atomic64 *ptr, Atomic64 value) {
+ *ptr = value;
+ }
+
++inline Atomic64 NoBarrier_Load(volatile const Atomic64 *ptr) {
++ return *ptr;
++}
++
++
++#ifdef __PPC64__
++
++// 64-bit Versions.
++
+ inline void Acquire_Store(volatile Atomic64 *ptr, Atomic64 value) {
+ *ptr = value;
+ // This can't be _lwsync(); we need to order the immediately
+@@ -390,10 +396,6 @@
+ *ptr = value;
+ }
+
+-inline Atomic64 NoBarrier_Load(volatile const Atomic64 *ptr) {
+- return *ptr;
+-}
+-
+ inline Atomic64 Acquire_Load(volatile const Atomic64 *ptr) {
+ Atomic64 value = *ptr;
+ _lwsync();
--- End Message ---
--- Begin Message ---
On Sun, Jul 8, 2012 at 19:50:23 +0100, Adam D. Barratt wrote:
> On 08.07.2012 10:46, Daigo Moriwaki wrote:
> >The package in unstable fixes the following issues, which would be
> >of use
> >for users and us.
>
> Unfortunately, unblocking it is not possible at the moment.
>
> > * debian/patches/20120708_ppc_ftbfs.patch: Imported Ubun
Bug#681910: marked as done (RM: zoph/0.8.0.1-1.1)
Your message dated Tue, 17 Jul 2012 19:43:38 +0200 with message-id <20120717174338.ga7...@radis.cristau.org> and subject line Re: Bug#681910: RM: zoph/0.8.0.1-1.1 has caused the Debian Bug report #681910, regarding RM: zoph/0.8.0.1-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.) -- 681910: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=681910 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: release.debian.org User: release.debian@packages.debian.org Usertags: rm Severity: normal X-Debbugs-CC: 678...@bugs.debian.org Zope requires substantial changes (in a new upstream) to be fit for release with Wheezy. There is interest in doing this, but I am suggesting to the release team that it will not happen in time within the criteria for freeze exceptions, and therefore to remove it from testing. A package in wheezy-backports seems the most sensible way to proceed IMO. If an exception is to be granted at a later stage then a removal now is not a death sentence. -- Jonathan Wiltshire j...@debian.org Debian Developer http://people.debian.org/~jmw 4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC 74C3 5394 479D D352 4C51 --- End Message --- --- Begin Message --- On Tue, Jul 17, 2012 at 18:09:32 +0100, Jonathan Wiltshire wrote: > Package: release.debian.org > User: release.debian@packages.debian.org > Usertags: rm > Severity: normal > X-Debbugs-CC: 678...@bugs.debian.org > > Zope requires substantial changes (in a new upstream) to be fit for > release with Wheezy. There is interest in doing this, but I am > suggesting > to the release team that it will not happen in time within the criteria > for freeze exceptions, and therefore to remove it from testing. A > package > in wheezy-backports seems the most sensible way to proceed IMO. > removal hint added. Cheers, Julien signature.asc Description: Digital signature --- End Message ---
Bug#681911: typo
Argh, the body should say "Version 2.7.103-4 contains fixes for ..." ^ EMOARCOFFEE -Kees -- Kees Cook@debian.org -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120717173328.gc28...@outflux.net
Re: lesstif2 multiarch conversion
On Tue, Jul 17, 2012 at 10:52 AM, Julien Cristau wrote: > On Tue, Jul 17, 2012 at 10:22:01 -0400, Michael Gilbert wrote: > >> I'm trying to be as reactive as I can about breakages I cause >> (although I admit that 've been too trigger-happy with openjpeg and >> I'll not do that anymore), and we have quite a bit of time until the >> release (looking at 650 rc bugs right now). >> > Just because there are a lot of RC bugs left doesn't mean it's ok to > waste our time with (comparatively) unimportant stuff. Quite the > opposite, arguably. I think there are lots of people looking forward to a high quality wine experience with the wheezy release, and lots of others looking forward to an ia32-libs-less release. We've got three packages blocking the happiness of all those people in testing right now: openjpeg, lesstif2, and sane-backends. That may seem unimportant compared to the massive list of rc issues, but it's important to enough people that I think its worthwhile. So anyway, apologies for continuing to be abrasive, but I want wheezy to be the best release it can be. 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: http://lists.debian.org/CANTw=MNwjPA9sFL_r=c=UQorUY1S66_f9PePnrFdt=1uuey...@mail.gmail.com
Bug#681911: unblock: apparmor/2.7.103-4
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package apparmor Version 2.7.103-3 contains fixes for an RC bug[1] and a piuparts failure. Debdiff attached. Thanks! -Kees [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=679597 [2] http://piuparts.debian.org/sid/source/a/apparmor.html unblock apparmor/2.7.103-4 -- System Information: Debian Release: wheezy/sid APT prefers precise-updates APT policy: (500, 'precise-updates'), (500, 'precise-security'), (500, 'precise') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-26-generic (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 diff -Nru apparmor-2.7.103/debian/apparmor-profiles.dirs apparmor-2.7.103/debian/apparmor-profiles.dirs --- apparmor-2.7.103/debian/apparmor-profiles.dirs 2012-06-28 22:17:27.0 -0700 +++ apparmor-2.7.103/debian/apparmor-profiles.dirs 2012-06-29 01:24:51.0 -0700 @@ -1 +1,3 @@ /etc/apparmor.d/local +/etc/apparmor.d/abstractions/ubuntu-browsers.d +/etc/apparmor.d/abstractions diff -Nru apparmor-2.7.103/debian/changelog apparmor-2.7.103/debian/changelog --- apparmor-2.7.103/debian/changelog 2012-06-29 00:43:20.0 -0700 +++ apparmor-2.7.103/debian/changelog 2012-07-16 11:54:14.0 -0700 @@ -1,3 +1,12 @@ +apparmor (2.7.103-4) unstable; urgency=low + + * debian/apparmor-profiles.dirs: add directories we might collide +with apparmor on during purge. + * debian/patches/fix-network-rule-support.patch: handle lack of +networking features correctly (Closes: 679597). + + -- Kees Cook Mon, 16 Jul 2012 11:52:42 -0700 + apparmor (2.7.103-3) unstable; urgency=low * debian/control: drop deprecated XS-Python-Version (Closes: 673062). diff -Nru apparmor-2.7.103/debian/patches/fix-network-rule-support.patch apparmor-2.7.103/debian/patches/fix-network-rule-support.patch --- apparmor-2.7.103/debian/patches/fix-network-rule-support.patch 1969-12-31 16:00:00.0 -0800 +++ apparmor-2.7.103/debian/patches/fix-network-rule-support.patch 2012-07-16 11:52:23.0 -0700 @@ -0,0 +1,20 @@ +Description: handle missing network mediation support. +Author: John Johansen +Bug-Debian: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=679597 + +Index: apparmor-debian/parser/parser_main.c +=== +--- apparmor-debian.orig/parser/parser_main.c 2012-06-28 22:17:27.433492000 -0700 apparmor-debian/parser/parser_main.c 2012-07-16 11:51:23.742020178 -0700 +@@ -1182,7 +1182,10 @@ + write_cache = 0; + skip_read_cache = 1; + return; +- } ++ } else if (strstr(flags_string, "network")) ++ kernel_supports_network = 1; ++ else ++ kernel_supports_network = 0; + + /* + * Deal with cache directory versioning: diff -Nru apparmor-2.7.103/debian/patches/series apparmor-2.7.103/debian/patches/series --- apparmor-2.7.103/debian/patches/series 2012-06-28 22:17:27.0 -0700 +++ apparmor-2.7.103/debian/patches/series 2012-07-16 11:50:18.0 -0700 @@ -9,3 +9,4 @@ abstractions-ubuntu-browsers.patch pass-compiler-flags.patch non-linux.patch +fix-network-rule-support.patch
Bug#681910: RM: zoph/0.8.0.1-1.1
Package: release.debian.org User: release.debian@packages.debian.org Usertags: rm Severity: normal X-Debbugs-CC: 678...@bugs.debian.org Zope requires substantial changes (in a new upstream) to be fit for release with Wheezy. There is interest in doing this, but I am suggesting to the release team that it will not happen in time within the criteria for freeze exceptions, and therefore to remove it from testing. A package in wheezy-backports seems the most sensible way to proceed IMO. If an exception is to be granted at a later stage then a removal now is not a death sentence. -- Jonathan Wiltshire j...@debian.org Debian Developer http://people.debian.org/~jmw 4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC 74C3 5394 479D D352 4C51 -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/f5834ba87e966ca8781dfc49c9213593@localhost
Bug#681871: marked as done (unblock: accountsservice/0.6.21-6)
Your message dated Tue, 17 Jul 2012 18:40:41 +0200 with message-id <20120717164041.gz7...@radis.cristau.org> and subject line Re: Bug#681871: unblock: accountsservice/0.6.21-6 has caused the Debian Bug report #681871, regarding unblock: accountsservice/0.6.21-6 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.) -- 681871: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=681871 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: unblock Please unblock package accountsservice, it fixes an important security issue: - CVE-2012-2737 http://bugs.debian.org/679429 The patch is available here for the review: http://goo.gl/nw4Rl Thanks for considering, regards. unblock accountsservice/0.6.21-6 -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-3-amd64 (SMP w/1 CPU core) 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 Tue, Jul 17, 2012 at 15:45:27 +0200, Alessio Treglia wrote: > Package: release.debian.org > Severity: normal > User: release.debian@packages.debian.org > Usertags: unblock > > Please unblock package accountsservice, it fixes an important security issue: > - CVE-2012-2737 >http://bugs.debian.org/679429 > > The patch is available here for the review: http://goo.gl/nw4Rl > Thanks for considering, regards. > > unblock accountsservice/0.6.21-6 > Unblocked. Cheers, Julien signature.asc Description: Digital signature --- End Message ---
Re: Report from the first tests of d-i beta 1 candidate images
On Tue, 2012-07-17 at 14:45 +0200, Cyril Brulebois wrote: > Cyril Brulebois (17/07/2012): > > some time to try kde/xfce/lxde/server installations, and possibly report > > some more bugs. Given the images are going to be re-built at some point, > > I think the pointer to the (known broken) images will be kept somewhere > > in #debian-boot's topic, to avoid confusion with later builds. > > Thankfully cdimage has a HEADER.html mechanism, so I've added a warning > there, here's the URL: > http://cdimage.debian.org/cdimage/.wheezy_di_beta1_build1/ Installing from debian-wheezy-DI-b1-amd64-i386-netinst.iso in a Xen guest I get: ┌─┌┤ [!!] Configure the package manager ├┐┐ │ │ │ │ │ apt configuration problem │ │ │ An attempt to configure apt to install additional packages from the │ │ │ CD failed. │ │ │ │ │ │ │ │ │ │ └─└──┘ Looking in /var/log/syslog I see: Jul 17 15:46:42 apt-setup: 'Debian GNU/Linux wheezy-DI-b1 _Wheezy_ - Official Snapshot Multi-architecture amd64/i386 NETINST #1 20120715-10:55' Jul 17 15:46:42 apt-setup: Copying package lists... Jul 17 15:46:42 apt-setup: ^MReading Package Indexes... 0% ^M Jul 17 15:46:42 apt-setup: ^MReading Package Indexes... Done^M Jul 17 15:46:42 apt-setup: Jul 17 15:46:42 apt-setup: ^MReading Translation Indexes... 0%^M Jul 17 15:46:42 apt-setup: ^MReading Translation Indexes... Done^M Jul 17 15:46:42 apt-setup: Jul 17 15:46:42 apt-setup: E Jul 17 15:46:42 apt-setup: : Jul 17 15:46:42 apt-setup: Failed to link /var/lib/apt/cdroms.list to /var/lib/apt/cdroms.list~ - link (17: File exists) Jul 17 15:46:42 apt-setup: Jul 17 15:48:58 apt-setup: /usr/lib/apt-setup/generators/40cdrom backed up /var/lib/apt doesn't seem to exist in the installer environment. But /target/var/lib/apt does so I guess this refers to that: ~ # ls /target/var/lib/apt -l -rw-r--r--1 root root 321 Jul 17 15:46 cdroms.list -rw-r--r--1 root root 321 Jul 17 15:53 cdroms.list.new -rw-r--r--1 root root 321 Jul 17 15:45 cdroms.list~ -rw-r--r--1 root root 658 Jul 17 15:46 extended_states drwxr-xr-x3 root root 16384 Jul 17 15:53 lists drwxr-xr-x3 root root 4096 Jul 17 15:43 mirrors drwxr-xr-x2 root root 4096 Jun 29 14:00 periodic This doesn't seem to be anything Xen specific here. Ian. -- Ian Campbell Current Noise: Wolves In The Throne Room - Thuja Magus Imperium It is not best to swap horses while crossing the river. -- Abraham Lincoln -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1342540582.16704.9.ca...@zakaz.uk.xensource.com
Re: Collaborative maintenance of mime-support (was Re: Using FreeDesktop MIME entries directly in mime-support).
Answering to my own mail. On Tue, 2012-07-17 at 05:38 +, Laszlo Boszormenyi (GCS) wrote: > On Tue, 2012-07-17 at 09:27 +0900, Charles Plessy wrote: > > 2) Install in Alioth's collab-maint a git repository made with the --debsnap > >option of git-import-dscs, unless we try to go deeper in time ? Set up > >commits emails to go to the PTS. > I've created an empty git collab-maint repository on Alioth, still not > visible over the web interface. As I know, it just need some time. It is now visible: http://anonscm.debian.org/gitweb/?p=collab-maint/mime-support.git;a=summary Empty at the moment. I used git-debimport , the result is at GitHub for review: https://github.com/gcsideal/mime-support If it's OK, I'll rebase to git.debian.org . Regards, Laszlo/GCS signature.asc Description: This is a digitally signed message part
Re: lesstif2 multiarch conversion
On Tue, Jul 17, 2012 at 10:22:01 -0400, Michael Gilbert wrote: > I'm trying to be as reactive as I can about breakages I cause > (although I admit that 've been too trigger-happy with openjpeg and > I'll not do that anymore), and we have quite a bit of time until the > release (looking at 650 rc bugs right now). > Just because there are a lot of RC bugs left doesn't mean it's ok to waste our time with (comparatively) unimportant stuff. Quite the opposite, arguably. Cheers, Julien signature.asc Description: Digital signature
Re: lesstif2 multiarch conversion
On Tue, Jul 17, 2012 at 6:01 AM, Cyril Brulebois wrote: > As I already said elsewhere, bumping debhelper and enabling multiarch is > what I consider invasive changes, with possible breakages in the reverse > dependencies, which one might only notice long after they are > introduced. Even for the sake of getting rid of ia32-libs, that seems > way too late for me. What if these changes could be done without a debhelper bump? The lesstif2 patch is not bumping debhelper (see attached), and #680887 in openjpeg could have been solved in a different way that would not have bumped debhelper (the arch-dependent files could be excluded from dh_stripping). I'm trying to be as reactive as I can about breakages I cause (although I admit that 've been too trigger-happy with openjpeg and I'll not do that anymore), and we have quite a bit of time until the release (looking at 650 rc bugs right now). Best wishes, Mike lesstif2_multiarch.diff Description: Binary data
Bug#681885: unblock: ivykis/0.30.1-2
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: freeze-exception
Please unblock package ivykis
While a new upstream version, it's a bug-fix release, containing
important upstream fixes (none reported to Debian, so no bug numbers
at present), and a minor packaging fix.
The most important of these are explained in the changelog aswell, but
for convenience, I'll repeat them here, with a bit more information
added to make it easier to decide whether to unblock the package.
The fixes are:
- 0.30 (currently in testing) introduced a regression, that could
easily result in a deadlock when under moderate load. The situation
and the fix is - I believe - well explained in the comment in
iv_work.c (see the attached debdiff)
- The kqueue polling method had an uninitialized variable, which lead
to strange situations - including possible assertions - on
kFreeBSD. (fix in iv_method_kqueue.c)
- Various minor/possible memory leak fixes, best explained by
upstream commit messages:
https://github.com/buytenh/ivykis/commit/3124a2c6b082054ee6418a195327c6e7b20529f3
https://github.com/buytenh/ivykis/commit/d785caf58b25d2304d1aba9439fe20a5a76d76ee
- A workaround for an event registration problem, triggered by
syslog-ng. Without this workaround, it's fairly inconvenient to
register fds with ivykis, and the application would need to go to
great lengths to ensure everything is proper. A needless dance,
since ivykis - with this fix - can do the same thing more
efficiently.
- And last but not least, ivykis Breaks/Replaces libsyslog-ng-dev,
because former versions (including 3.3.5 currently in testing &
unstable) included a patched ivykis, and installed its headers
too. Starting with 3.3.6, syslog-ng will stop doing that, and use the
ivykis package instead.
However, after ivykis 0.30.1-2 was uploaded to unstable, syslog-ng
3.3.5.90 (a 3.3.6 RC) was released, and 3rd party Debian packages
were made for that release too.
To make the life of users of those packages, and my own, I lowered
the Breaks/Replaces to << 3.3.5.90~ (from the former << 3.3.6~).
It's a trivial fix that does not affect Debian at all, but it'd be
nice to have nevertheless.
There are currently no packages in Debian that either depend or
build-depend on ivykis, therefore I'd consider the above changes
no-risk and very safe. We've also went to great lengths with upstream
to make sure that 0.30.1 is suitable for Debian Stable, and that every
fix in it is well justified.
(The debdiff also has a bit of noise, as 0.30-1 had two patches
cherry-picked from upstream, which have been integrated in the new
version.)
unblock ivykis/0.30.1-2
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-1-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/bash
--
|8]
diff -Nru ivykis-0.30/configure.ac ivykis-0.30.1/configure.ac
--- ivykis-0.30/configure.ac 2012-06-22 18:23:52.0 +0200
+++ ivykis-0.30.1/configure.ac 2012-07-02 21:14:58.0 +0200
@@ -1,5 +1,5 @@
AC_PREREQ(2.59)
-AC_INIT([ivykis], [0.30], [libivykis-disc...@lists.sourceforge.net])
+AC_INIT([ivykis], [0.30.1], [libivykis-disc...@lists.sourceforge.net])
AC_CONFIG_SRCDIR([lib/iv_main.c])
AC_CONFIG_HEADER(config.h)
AM_INIT_AUTOMAKE([foreign])
diff -Nru ivykis-0.30/debian/changelog ivykis-0.30.1/debian/changelog
--- ivykis-0.30/debian/changelog 2012-06-23 09:06:12.0 +0200
+++ ivykis-0.30.1/debian/changelog 2012-07-05 12:50:27.0 +0200
@@ -1,3 +1,19 @@
+ivykis (0.30.1-2) unstable; urgency=low
+
+ * Ligthen the Breaks/Replaces on libsyslog-ng-dev, and B/R on versions
+prior to 3.3.5.90 instead of 3.3.6.
+
+ -- Gergely Nagy Thu, 05 Jul 2012 12:49:32 +0200
+
+ivykis (0.30.1-1) unstable; urgency=low
+
+ * New upstream bugfix release:
++ Fix a possible deadlock situation, introduced in 0.30.
++ Work around iv_fd_register_try() being called without handlers
+ (triggered by syslog-ng)
+
+ -- Gergely Nagy Tue, 03 Jul 2012 20:13:39 +0200
+
ivykis (0.30-1) unstable; urgency=low
* New upstream release.
diff -Nru ivykis-0.30/debian/control ivykis-0.30.1/debian/control
--- ivykis-0.30/debian/control 2012-06-23 09:06:12.0 +0200
+++ ivykis-0.30.1/debian/control 2012-07-05 12:50:27.0 +0200
@@ -29,8 +29,8 @@
Section: libdevel
Architecture: any
Depends: libivykis0 (= ${binary:Version}), ${misc:Depends}
-Breaks: libsyslog-ng-dev (<< 3.3.6~)
-Replaces: libsyslog-ng-dev (<< 3.3.6~)
+Breaks: libsyslog-ng-dev (<< 3.3.5.90~)
+Replaces: libsyslog-ng-dev (<< 3.3.5.90~)
Description: Development libraries, header files and docs for libivykis
Contains the header files, documentation, examples and static
libraries for use in developing applications th
Re: BinNMU changelog handling for Multi-Arch: same packages
On Tue, 2012-07-17 at 14:25:18 +0200, Philipp Kern wrote: > On Fri, Jul 13, 2012 at 09:07:00AM +0200, Raphael Hertzog wrote: > > On Thu, 12 Jul 2012, Philipp Kern wrote: > > > I just verified a build in stable and get a bunch of these: > > > > > > dpkg-source --after-build hello-2.6 > > > parsechangelog/debian: warning: hello-2.6/debian/changelog(l1): unknown > > > key-value Binary-only > > > LINE: hello (2.6-1+b1) unstable; urgency=low, binary-only=yes > > > parsechangelog/debian: warning: unknown information field 'Binary-Only' > > > in input data in parsed version of changelog > > > dpkg-buildpackage: binary and diff upload (original source NOT included) > > > > > > If we add that, dpkg in all supported suites should at least do the right > > > thing and ignore it. Oh and forgot to comment on this, those key-values are warned upon because they are unknown but they are ignored and harmless on older dpkg scripts. > I presume there are no other RC bugfixes for dpkg/stable pending at the > moment? Sorry actually there is at least one, #679641 fixed in unstable now. thanks, guillem -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120717125934.gb15...@gaara.hadrons.org
Re: BinNMU changelog handling for Multi-Arch: same packages
On Tue, 2012-07-17 at 14:25:18 +0200, Philipp Kern wrote: > On Fri, Jul 13, 2012 at 09:07:00AM +0200, Raphael Hertzog wrote: > > On Thu, 12 Jul 2012, Philipp Kern wrote: > > > > #681292 against sbuild. Feel free to clone it if necessary. > > > I just verified a build in stable and get a bunch of these: > > > > > > dpkg-source --after-build hello-2.6 > > > parsechangelog/debian: warning: hello-2.6/debian/changelog(l1): unknown > > > key-value Binary-only > > > LINE: hello (2.6-1+b1) unstable; urgency=low, binary-only=yes > > > parsechangelog/debian: warning: unknown information field 'Binary-Only' > > > in input data in parsed version of changelog > > > dpkg-buildpackage: binary and diff upload (original source NOT included) > > > > > > If we add that, dpkg in all supported suites should at least do the right > > > thing and ignore it. > > I'm happy to prepare a stable update to fix this. Would you accept it? > > I presume there are no other RC bugfixes for dpkg/stable pending at the > moment? Could you prepare the diff and post it here? No there are not, and I could prepare it yes, but I'm not sure there's any point anyway as this alone (in wheezy) will not solve the binNMU+multiarch case anyway, and as it's been said I think it's too late for the other possible fixes. > (I'd currently tend to accept it, however I'm not yet sure of all the > consequences of this change.) This change in itself should not have any consequence as it should not affect the normal build if the value is not being used, or maybe you are referring to *when* the value is being used? regards, guillem -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120717125319.ga15...@gaara.hadrons.org
Re: Report from the first tests of d-i beta 1 candidate images
Cyril Brulebois (17/07/2012): > some time to try kde/xfce/lxde/server installations, and possibly report > some more bugs. Given the images are going to be re-built at some point, > I think the pointer to the (known broken) images will be kept somewhere > in #debian-boot's topic, to avoid confusion with later builds. Thankfully cdimage has a HEADER.html mechanism, so I've added a warning there, here's the URL: http://cdimage.debian.org/cdimage/.wheezy_di_beta1_build1/ > I'm not sure whether we want to use this delay to possibly merge a new > busybox with the s390x fix prepared by Aurélien Jarno. > > http://bugs.debian.org/681760 Mentioned there as well. Mraw, KiBi. signature.asc Description: Digital signature
Bug#681398: marked as done (release.debian.org: maintainer (both Debian and upstream lost intrest) see #627174)
Your message dated Tue, 17 Jul 2012 14:32:25 +0200 with message-id <20120717123225.ge18...@spike.0x539.de> and subject line Re: Bug#681398: release.debian.org: maintainer (both Debian and upstream lost intrest) see #627174 has caused the Debian Bug report #681398, regarding release.debian.org: maintainer (both Debian and upstream lost intrest) see #627174 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.) -- 681398: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=681398 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: release.debian.org Severity: wishlist The Debian/upstream maintainer says: "SD has fallen from my priorities, and to have it be worth keeping in Debian at this point, I think someone else will need to step up and work on maintenance upstream." I've asked in #debian-perl but noone has expressed an interest so I propose removing it. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash --- End Message --- --- Begin Message --- On Thu, Jul 12, 2012 at 09:46:01PM +0100, Nicholas Bamber wrote: > The Debian/upstream maintainer says: > > "SD has fallen from my priorities, and to have it be worth keeping in > Debian at this point, I think someone else will need to step up and work > on maintenance upstream." > > I've asked in #debian-perl but noone has expressed an interest so I propose > removing it. I've added a removal hint based on #627174. As Adam said: If nobody cares about it remaining in Debian, it should also be removed from unstable. If somebody steps up and fixes #627174 it can also be readded to testing, if it's within 20 days of the removal. Kind regards Philipp Kern signature.asc Description: Digital signature --- End Message ---
Bug#680622: marked as done (unblock: goobox/3.0.1-5)
Your message dated Tue, 17 Jul 2012 14:33:48 +0200 with message-id <20120717123348.gf18...@spike.0x539.de> and subject line Re: Bug#680622: unblock: goobox/3.0.1-5, was Re: Bug#680622: unblock: goobox/3.0.1-4 has caused the Debian Bug report #680622, regarding unblock: goobox/3.0.1-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.) -- 680622: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=680622 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: release.debian.org User: release.debian@packages.debian.org Usertags: freeze-exception Severity: normal Please unblock package goobox Essentially 3.0.1-4 is 3.0.1-1 (from April 20th) with a few translation fixes applied. However, the road was a little bumpy, thus 3.0.1-4 closes an RC bug (namely #679554). It has (finally) build on all architectures. The long history: *) 3.0.1-1.1 was an NMU which did not work *) 3.0.2 reverted the NMU, updated a few translations and run into a FTBS on mipsel (679552). *) 3.0.3 avoided the FTBS by pregenerating the man pages on mipsl, however, the FTBS now appears on ia64 and amd64 as well *) 3.0.4 avoided those FTBS by pregenerating the man pages on all architectures except the uploading one. The full changelog of these versions (3.0.2 was before the freeze, but I include it nevertheless): goobox (3.0.1-4) unstable; urgency=high * Urgency high due to RC fix (2nd try) * Until sp is fixed generate man pages only on build machine (currently i386 chroot) and ship pregenerated ones otherwise. closes: #679554. -- Helge Kreutzmann Fri, 06 Jul 2012 19:05:12 +0200 goobox (3.0.1-3) unstable; urgency=high * Urgency high due to RC fix * Until sp is fixed on mipsel (see 679552), ship pregenerated translated man pages for mipsel, closes: #679554. -- Helge Kreutzmann Thu, 05 Jul 2012 19:46:19 +0200 goobox (3.0.1-2) unstable; urgency=medium * Revert broken NMU, closes: #679313. * This reopens: #677246. Since no bug report until just before the release happend, people requiring this fix will need to backport goobox after the release of Wheezy. Sorry. * po/fr.po updated from upstream git with msgcat. * help/es/es.po updated from upstream git with msgcat. * po/es.po updated from upstream git with msgcat. * po/pl.po updated from upstream git with msgcat. * po/sl.po updated from upstream git with msgcat. -- Helge Kreutzmann Fri, 29 Jun 2012 10:35:53 +0200 unblock goobox/3.0.1-4 -- Dr. Helge Kreutzmann deb...@helgefjell.de Dipl.-Phys. http://www.helgefjell.de/debian.php 64bit GNU powered gpg signed mail preferred Help keep free software "libre": http://www.ffii.de/ signature.asc Description: Digital signature --- End Message --- --- Begin Message --- On Thu, Jul 12, 2012 at 10:32:07PM +0200, Helge Kreutzmann wrote: > unblock goobox/3.0.1-5 Done, thanks. Kind regards Philipp Kern signature.asc Description: Digital signature --- End Message ---
Bug#681810: marked as done (unblock: python-pylibacl/0.5.1-1.1)
Your message dated Tue, 17 Jul 2012 14:19:31 +0200 with message-id <20120717121931.gb18...@spike.0x539.de> and subject line Re: Bug#681810: unblock: python-pylibacl/0.5.1-1.1 has caused the Debian Bug report #681810, regarding unblock: python-pylibacl/0.5.1-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.) -- 681810: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=681810 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: unblock Please unblock package python-pylibacl Fixes RC bug #680858. Package is currently in delay/2. unblock python-pylibacl/0.5.1-1.1 diff -Nru python-pylibacl-0.5.1/debian/changelog python-pylibacl-0.5.1/debian/changelog --- python-pylibacl-0.5.1/debian/changelog 2012-05-13 16:47:19.0 -0400 +++ python-pylibacl-0.5.1/debian/changelog 2012-07-16 14:34:17.0 -0400 @@ -1,3 +1,13 @@ +python-pylibacl (0.5.1-1.1) unstable; urgency=low + + * Non-maintainer upload. + * Drop python3-sphinx as an alternate build-depend to python-sphinx to fix +FTBFS (Closes: #680858) +- The package only builds and installs html documentation for the python + version anyway, so python3-sphinx as a build-dep is clearly wrong + + -- Scott Kitterman Mon, 16 Jul 2012 14:34:07 -0400 + python-pylibacl (0.5.1-1) unstable; urgency=low * New upstream version: bugfixes for refcount leaks and possible diff -Nru python-pylibacl-0.5.1/debian/control python-pylibacl-0.5.1/debian/control --- python-pylibacl-0.5.1/debian/control 2012-05-13 16:47:19.0 -0400 +++ python-pylibacl-0.5.1/debian/control 2012-07-16 14:34:35.0 -0400 @@ -6,7 +6,7 @@ python (>= 2.6.6-3~), python-all-dev (>= 2.6.6-3~), python-all-dbg, python3-all, python3-all-dev, python3-all-dbg, libacl1-dev, python-setuptools, python3-setuptools, - python-sphinx (>= 1.0.7+dfsg) | python3-sphinx + python-sphinx (>= 1.0.7+dfsg) Standards-Version: 3.9.3 Homepage: http://pylibacl.k1024.org/ Vcs-Browser: http://git.k1024.org/debian-pylibacl.git --- End Message --- --- Begin Message --- On Mon, Jul 16, 2012 at 02:46:50PM -0400, Scott Kitterman wrote: > unblock python-pylibacl/0.5.1-1.1 Done, thanks. Kind regards Philipp Kern signature.asc Description: Digital signature --- End Message ---
Bug#681552: marked as done (unblock: python-csa/0.1.0-1.1)
Your message dated Tue, 17 Jul 2012 14:22:05 +0200
with message-id <20120717122205.gc18...@spike.0x539.de>
and subject line Re: Bug#681552: unblock: python-csa/0.1.0-1.1
has caused the Debian Bug report #681552,
regarding unblock: python-csa/0.1.0-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.)
--
681552: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=681552
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: unblock
Please unblock package python-csa
Fixes two RC bugs, 595848 and 665039.
unblock python-csa/0.1.0-1.1
diff -Nru python-csa-0.1.0/debian/changelog python-csa-0.1.0/debian/changelog
--- python-csa-0.1.0/debian/changelog 2012-03-30 12:52:19.0 -0400
+++ python-csa-0.1.0/debian/changelog 2012-07-14 01:30:58.0 -0400
@@ -1,3 +1,17 @@
+python-csa (0.1.0-1.1) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * Redo last NMU that maintainer overwrote:
+- Add python-tk to build-depends to fix FTBFS (Closes: #595848) and to
+ depends to it will run
+- Remove failing override of dh_auto_test (because test_csa.py is no
+ longer shipped)
+ * Set MPLCONFIGDIR to debiam/temp in debian/rules so that the directory
+location is writeable when built on a buildd and then remove on clean
+(Closes: #665039)
+
+ -- Scott Kitterman Sat, 14 Jul 2012 01:28:54 -0400
+
python-csa (0.1.0-1) unstable; urgency=low
* New upstream version (Closes: #597299)
diff -Nru python-csa-0.1.0/debian/control python-csa-0.1.0/debian/control
--- python-csa-0.1.0/debian/control 2012-03-30 12:59:48.0 -0400
+++ python-csa-0.1.0/debian/control 2012-07-13 01:14:28.0 -0400
@@ -9,12 +9,13 @@
, python-nose
, python-numpy
, python-matplotlib
+ , python-tk
Standards-Version: 3.9.3
Homepage: http://software.incf.org/software/csa
Package: python-csa
Architecture: all
-Depends: ${python:Depends}, ${misc:Depends}, python-numpy, python-matplotlib
+Depends: ${python:Depends}, ${misc:Depends}, python-numpy, python-matplotlib, python-tk
Description: Connection-Set Algebra (CSA) implemented in Python
The CSA library provides elementary connection-sets and operators for
combining them. It also provides an iteration interface to such
diff -Nru python-csa-0.1.0/debian/rules python-csa-0.1.0/debian/rules
--- python-csa-0.1.0/debian/rules 2012-03-30 12:52:19.0 -0400
+++ python-csa-0.1.0/debian/rules 2012-07-14 01:28:51.0 -0400
@@ -1,12 +1,10 @@
#!/usr/bin/make -f
-override_dh_auto_test:
-ifeq ($(filter nocheck,$(DEB_BUILD_OPTIONS)),)
- set -e; \
- for python in $(shell pyversions -r); do \
- $$python /usr/bin/nosetests ../../tests/test_csa.py; \
- done
-endif
+export MPLCONFIGDIR=$(CURDIR)/debian/temp
%:
dh $@
+
+override_dh_auto_clean:
+ dh_auto_clean
+ rm -rf $(CURDIR)/debian/temp
--- End Message ---
--- Begin Message ---
On Sat, Jul 14, 2012 at 01:42:14AM -0400, Scott Kitterman wrote:
> unblock python-csa/0.1.0-1.1
Done, thanks.
Kind regards
Philipp Kern
signature.asc
Description: Digital signature
--- End Message ---
Bug#681804: marked as done (unblock: python-pyxattr/0.5.1-1.1)
Your message dated Tue, 17 Jul 2012 14:18:40 +0200 with message-id <20120717121840.ga18...@spike.0x539.de> and subject line Re: Bug#681804: unblock: python-pyxattr/0.5.1-1.1 has caused the Debian Bug report #681804, regarding unblock: python-pyxattr/0.5.1-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.) -- 681804: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=681804 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: unblock Please unblock package python-pyxattr Fixes RC Bug #680859. Currently in delay/2. unblock python-pyxattr/0.5.1-1.1 diff -Nru python-pyxattr-0.5.1/debian/changelog python-pyxattr-0.5.1/debian/changelog --- python-pyxattr-0.5.1/debian/changelog 2012-05-16 15:00:20.0 -0400 +++ python-pyxattr-0.5.1/debian/changelog 2012-07-16 13:32:03.0 -0400 @@ -1,3 +1,13 @@ +python-pyxattr (0.5.1-1.1) unstable; urgency=low + + * Non-maintainer upload. + * Drop python3-sphinx as an alternate build-depend to python-sphinx to fix +FTBFS (Closes: #680859) +- The package only builds and installs html documentation for the python + version anyway, so python3-sphinx as a build-dep is clearly wrong + + -- Scott Kitterman Mon, 16 Jul 2012 13:29:41 -0400 + python-pyxattr (0.5.1-1) unstable; urgency=low * New upstream bug-fix release, fixing reference leaks and potential diff -Nru python-pyxattr-0.5.1/debian/control python-pyxattr-0.5.1/debian/control --- python-pyxattr-0.5.1/debian/control 2012-05-16 15:00:20.0 -0400 +++ python-pyxattr-0.5.1/debian/control 2012-07-16 13:29:34.0 -0400 @@ -6,7 +6,7 @@ python (>= 2.6.6-3~), python-all-dev (>= 2.6.6-3~), python-all-dbg, python3-all, python3-all-dev, python3-all-dbg, libattr1-dev, python-setuptools, python3-setuptools, - python-sphinx (>= 1.0.7+dfsg) | python3-sphinx + python-sphinx (>= 1.0.7+dfsg) Standards-Version: 3.9.3 Homepage: http://pyxattr.k1024.org/ Vcs-Browser: http://git.k1024.org/debian-pyxattr.git --- End Message --- --- Begin Message --- On Mon, Jul 16, 2012 at 03:25:02PM -0400, Scott Kitterman wrote: > On Monday, July 16, 2012 08:58:56 PM Philipp Kern wrote: > > On Mon, Jul 16, 2012 at 01:49:17PM -0400, Scott Kitterman wrote: > > > Fixes RC Bug #680859. Currently in delay/2. > > Given the maintainer's response in the bug report, I suggest that you > > reschedule that to 0-days. > Done. Unblocked, thanks. Kind regards Philipp Kern signature.asc Description: Digital signature --- End Message ---
Re: BinNMU changelog handling for Multi-Arch: same packages
On Fri, Jul 13, 2012 at 09:07:00AM +0200, Raphael Hertzog wrote: > On Thu, 12 Jul 2012, Philipp Kern wrote: > > > #681292 against sbuild. Feel free to clone it if necessary. > > I just verified a build in stable and get a bunch of these: > > > > dpkg-source --after-build hello-2.6 > > parsechangelog/debian: warning: hello-2.6/debian/changelog(l1): unknown > > key-value Binary-only > > LINE: hello (2.6-1+b1) unstable; urgency=low, binary-only=yes > > parsechangelog/debian: warning: unknown information field 'Binary-Only' in > > input data in parsed version of changelog > > dpkg-buildpackage: binary and diff upload (original source NOT included) > > > > If we add that, dpkg in all supported suites should at least do the right > > thing and ignore it. > I'm happy to prepare a stable update to fix this. Would you accept it? I presume there are no other RC bugfixes for dpkg/stable pending at the moment? Could you prepare the diff and post it here? (I'd currently tend to accept it, however I'm not yet sure of all the consequences of this change.) Kind regards Philipp Kern signature.asc Description: Digital signature
debian-installer-netboot-images upgrade path ?
Le vendredi, 6 juillet 2012 00.04:00, Didier Raboud a écrit : > the installation paths are not > version-specific: /usr/lib/debian-installer/images/amd64/… so I was about > to add Replaces and Breaks against the -6.0- versions. But does this make > sense? Would we not rather version-specify the paths (like > /usr/lib/debian-installer/7.0/amd64/) to ensure co-installability ? > > a) Add replaces+breaks ? > b) Version-specify the paths ? It seems I forgot the above issue for the latest upload of debian-installer- netboot-images. a) seems the most straightforward path forward but I think b) is the way to go (but more disruptive); opinions ? OdyX signature.asc Description: This is a digitally signed message part.
Bug#681871: unblock: accountsservice/0.6.21-6
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package accountsservice, it fixes an important security issue: - CVE-2012-2737 http://bugs.debian.org/679429 The patch is available here for the review: http://goo.gl/nw4Rl Thanks for considering, regards. unblock accountsservice/0.6.21-6 -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-3-amd64 (SMP w/1 CPU core) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120717134527.8779.81879.reportbug@Aspire-1410
Bug#681869: marked as done (unblock: django-notification/0.1.5-2)
Your message dated Tue, 17 Jul 2012 13:24:54 +0200 with message-id <50054b86.7020...@thykier.net> and subject line Re: Bug#681869: unblock: django-notification/0.1.5-2 has caused the Debian Bug report #681869, regarding unblock: django-notification/0.1.5-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.) -- 681869: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=681869 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: unblock X-Debbugs-CC: j...@debian.org Please unblock package django-notification to fix grave RC bug #681588 (import fails) A patch is in that bug log though Clint has made a maintainer upload since my NMU notification. -- Jonathan Wiltshire j...@debian.org Debian Developer http://people.debian.org/~jmw 4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC 74C3 5394 479D D352 4C51 --- End Message --- --- Begin Message --- On 2012-07-17 13:18, Jonathan Wiltshire wrote: > Package: release.debian.org > Severity: normal > User: release.debian@packages.debian.org > Usertags: unblock > X-Debbugs-CC: j...@debian.org > > Please unblock package django-notification > to fix grave RC bug #681588 (import fails) > > A patch is in that bug log though Clint has made a maintainer upload > since my NMU notification. > Thanks for the heads up; unblocked. ~Niels--- End Message ---
Bug#681864: [Pkg-telepathy-maintainers] Bug#681864: unblock (pre-approval): telepathy-mission-control-5/1:5.12.1-2
On 17/07/12 11:02, Laurent Bigonville wrote: > • Stop using deprecated telepathy-glib symbols. (Jonny) With my upstream hat on, I'd have preferred this change not to be committed to the upstream 5.12.x stable branch... The other two changes described in NEWS are the parts of the diff that touch src/mcd-account-manager-default.c and src/mcd-dispatcher.c (and possibly tests/, but that doesn't contribute to the binary package). I think both need fixing for wheezy, either with 5.12.1 or by backporting them. Another option would be to revert "Stop using deprecated...", release 5.12.2 upstream, and package *that* for wheezy. S -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/50054c5e.5050...@debian.org
Bug#681817: marked as done (Unblock freeglut/2.6.0-4)
Your message dated Tue, 17 Jul 2012 13:15:48 +0200 with message-id <50054964.3080...@thykier.net> and subject line Re: Bug#681817: Unblock freeglut/2.6.0-4 has caused the Debian Bug report #681817, regarding Unblock freeglut/2.6.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.) -- 681817: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=681817 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: unblock Please unblock package freeglut_2.6.0-4. The version fixes 2 bugs: #681513 (was introduced by me in the last upload) and #430160 (an old one, the patch appeared in BTS recently). Diff is attached. unblock freeglut/2.6.0-4 Thanks. Anton freeglut.diff Description: Binary data --- End Message --- --- Begin Message --- On 2012-07-16 21:43, Anton Gladky wrote: > Package: release.debian.org > Severity: normal > User: release.debian@packages.debian.org > Usertags: unblock > > Please unblock package freeglut_2.6.0-4. > > The version fixes 2 bugs: #681513 (was introduced by me in the last upload) > and > #430160 (an old one, the patch appeared in BTS recently). Diff is attached. > > unblock freeglut/2.6.0-4 > > Thanks. > > Anton Unblocked, thanks for the fixes. ~Niels--- End Message ---
Bug#681869: unblock: django-notification/0.1.5-2
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock X-Debbugs-CC: j...@debian.org Please unblock package django-notification to fix grave RC bug #681588 (import fails) A patch is in that bug log though Clint has made a maintainer upload since my NMU notification. -- Jonathan Wiltshire j...@debian.org Debian Developer http://people.debian.org/~jmw 4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC 74C3 5394 479D D352 4C51 -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/c99bad1c539f139be80276b0334742bf@localhost
Re: Bug#634538: Fixing 634538 for Wheezy
On 13/07/12 19:29, Noël Köthe wrote: Hello Mehdi, Am Mittwoch, den 11.07.2012, 13:59 +0200 schrieb Mehdi Dogguy: We would like to 634538 fixed for Wheezy. Unfortunately, the changes brought by tcpreplay/3.4.4-1 are quite large [1] and we are not able to unblock the package for Wheezy. Would it be possible to prepare an upload targeting testing-proposed-updates and versioned 3.4.3-2+wheezy1? I just uploaded tcpreplay 3.4.3-2+wheezy1 to testing-proposed-updates. maybe it fits the requirements better. I thought about cleanup a bit more (Standards-Version, lintian warnings,...) but reduced it mostly to fixing the RC bug. Thanks! FTR, Luk approved the version that was uploaded to testing-proposed-updates. Cheers. -- Mehdi Dogguy مهدي الدڤي http://dogguy.org/ -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/500548d2.3030...@dogguy.org
Bug#681858: marked as done (unblock: wajig/2.7.3)
Your message dated Tue, 17 Jul 2012 12:51:14 +0200
with message-id <500543a2.10...@thykier.net>
and subject line Re: Bug#681858: unblock: wajig/2.7.3
has caused the Debian Bug report #681858,
regarding unblock: wajig/2.7.3
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.)
--
681858: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=681858
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: freeze-exception
Please unblock package wajig
This change contains 2 simple and 'risk-free' fixes:
see http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=681309.
-- System Information:
Debian Release: wheezy/sid
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.2.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_ZA.UTF-8, LC_CTYPE=en_ZA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
diff -Nru wajig-2.7.2/debian/changelog wajig-2.7.3/debian/changelog
--- wajig-2.7.2/debian/changelog 2012-07-16 23:25:33.0 +0200
+++ wajig-2.7.3/debian/changelog 2012-07-12 12:41:11.0 +0200
@@ -1,3 +1,11 @@
+wajig (2.7.3) unstable; urgency=low
+
+ * NEWUPGRADES: a bug introduced in 2.5 made this subcommand illegal;
+Closes: #681309
+ * STATUSSEARCH: same case as above
+
+ -- Tshepang Lekhonkhobe Thu, 12 Jul 2012 12:11:46 +0200
+
wajig (2.7.2) unstable; urgency=low
* For some reason, some temp/build files ended up in the source package :(
diff -Nru wajig-2.7.2/src/wajig.py wajig-2.7.3/src/wajig.py
--- wajig-2.7.2/src/wajig.py 2012-07-16 23:25:33.0 +0200
+++ wajig-2.7.3/src/wajig.py 2012-07-12 12:37:04.0 +0200
@@ -26,7 +26,7 @@
import commands
import perform
-VERSION = "2.7.2"
+VERSION = "2.7.3"
def main():
@@ -679,7 +679,7 @@
function = commands.statusmatch
parser_statusmatch = subparsers.add_parser("statusmatch",
parents=[parser_teach],
- aliases=["statussearch status-search status-match"],
+ aliases="statussearch status-search status-match".split(),
description=function.__doc__)
parser_statusmatch.add_argument("pattern")
parser_statusmatch.set_defaults(func=function)
@@ -713,7 +713,7 @@
function = commands.toupgrade
parser_toupgrade = subparsers.add_parser("toupgrade",
- aliases=["newupgrades new-upgrades to-upgrade"],
+ aliases="newupgrades new-upgrades to-upgrade".split(),
description=function.__doc__)
parser_toupgrade.set_defaults(func=function)
--- End Message ---
--- Begin Message ---
On 2012-07-17 11:05, Tshepang Lekhonkhobe wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: freeze-exception
>
> Please unblock package wajig
>
> This change contains 2 simple and 'risk-free' fixes:
> see http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=681309.
>
Unblocked, thanks for the fix.
~Niels--- End Message ---
Bug#681859: marked as done (unblock: lazygal/0.7.4-1)
Your message dated Tue, 17 Jul 2012 12:48:26 +0200 with message-id <500542fa.20...@thykier.net> and subject line Re: Bug#681859: unblock: lazygal/0.7.4-1 has caused the Debian Bug report #681859, regarding unblock: lazygal/0.7.4-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.) -- 681859: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=681859 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: unblock -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Please unblock package lazygal, this is new upstream release, which only fixes grave bug #681724. It was caused by missing file in upstream tarball, the new version just reintroduces it back. Diff between those two versions is attached. unblock lazygal/0.7.4-1 Thanks - -- Michal Čihař | http://cihar.com | http://blog.cihar.com - -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.1.10-1.16-desktop (SMP w/2 CPU cores; PREEMPT) Locale: LANG=cs_CZ.UTF-8, LC_CTYPE=cs_CZ.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCAAGBQJQBSi1AAoJEGo39bHX+xdNCJ0QAJbVldrbYwSFvryUOLr8Lf91 RrZqtFSxVJXM3htfol2+nrFtdrT8AR2hbEcDYYr7pwQI8YmUoIYPN6Q9l5uAFGWb 71qA9oaXRzPKfZWPYL4yfc4PGRF9527RNK2j5vepRcPdic71WxjS3jSH+cv6jKAL 9X7AUzO2dAaUffc0b4eFkEKe0QIMSKItOWVt20maYTv5jweUTgdTXqIJFcSXBQqK kD9vTx1E4C0u00SjcFoH/Ibu0aG15683g1XsOWc3VxNRzXQehe2JpDEN9cWlbt1v mk5+O8UjRA2i/QDUfHTYprDuADPbNMZkGMktYT4BomRSpyGrONoHLuI96GKB1MUy 4eePkIjO4jc3+1SnIR9JGPFuuv8j5N2iOrv+0wHbDOdhoosOQt/5FLsQU4nnChPm oMyhlWrDMK+jJWfcYZ4T3ufCAGJK4/Ro2x+zoXMYkFlIh+mCi6wWv5nnNEQ2DyqP kjY+GUthxIzwOxX2RWfAWHzBZjEKdxJqWPwAYUzWHGUn917PQ+mIDZFKsltBz4Ij 1OSp2c9vVr6aUJhPIObziQnYZ8PmEYRA8dxQ6TqzmW4jabZeb3LZBhYio6ELOAqT QL2yCQXyGKONUL+hPhtdVmCyb+P5xZvIBeW/0En5YeRCGkktWR2y0iOXzPpYwClt LeXU+j5mU9BO/jN+fsW4 =Pvia -END PGP SIGNATURE- diff -ruNp lazygal-0.7.3/ChangeLog lazygal-0.7.4/ChangeLog --- lazygal-0.7.3/ChangeLog 2012-06-29 16:22:02.0 +0200 +++ lazygal-0.7.4/ChangeLog 2012-07-16 07:36:47.0 +0200 @@ -1,3 +1,6 @@ +Lazygal 0.7.4 (2012-07-16) + * add missing lazygal/defaults.conf in source tarball + Lazygal 0.7.3 (2012-06-29) * fix album picture link on win32 * add --force-gen-pages diff -ruNp lazygal-0.7.3/ChangeLog-full lazygal-0.7.4/ChangeLog-full --- lazygal-0.7.3/ChangeLog-full 2012-06-29 16:24:14.0 +0200 +++ lazygal-0.7.4/ChangeLog-full 2012-07-16 07:36:49.0 +0200 @@ -1,4 +1,8 @@ +Lazygal 0.7.4 (2012-07-16) + * set version to 0.7.4 + Lazygal 0.7.3 (2012-06-29) + * set version to 0.7.3 * update TODO * update french translation * fix album picture link on win32 diff -ruNp lazygal-0.7.3/lazygal/defaults.conf lazygal-0.7.4/lazygal/defaults.conf --- lazygal-0.7.3/lazygal/defaults.conf 1970-01-01 01:00:00.0 +0100 +++ lazygal-0.7.4/lazygal/defaults.conf 2012-07-16 07:32:55.0 +0200 @@ -0,0 +1,32 @@ +[runtime] +quiet = No +debug = No +check-all-dirs = No + +[global] +destdir = . +force-gen-pages = No +clean-destination = No +dir-flattening-depth = No +puburl = No +theme = default + +[webgal] +default-style = default +webalbumpic-bg = transparent +webalbumpic-type = messy +webalbumpic-size = 200x150 +image-size = small=800x600,medium=1024x768 +thumbnail-size = 150x113 +thumbs-per-page = 0 +sort-medias = exif +sort-subgals = dirname +original = No +original-baseurl = No +original-symlink = No +dirzip = No +jpeg-quality = 85 +jpeg-optimize = Yes +jpeg-progressive = Yes +publish-metadata = Yes +keep-gps = No diff -ruNp lazygal-0.7.3/lazygal/__init__.py lazygal-0.7.4/lazygal/__init__.py --- lazygal-0.7.3/lazygal/__init__.py 2012-06-29 16:19:11.0 +0200 +++ lazygal-0.7.4/lazygal/__init__.py 2012-07-16 07:33:12.0 +0200 @@ -58,7 +58,7 @@ def get_hg_rev(): return '' -__version__ = '0.7.3' +__version__ = '0.7.4' hg_rev = get_hg_rev() if hg_rev: __version__ += '+hg' + hg_rev diff -ruNp lazygal-0.7.3/PKG-INFO lazygal-0.7.4/PKG-INFO --- lazygal-0.7.3/PKG-INFO 2012-06-29 16:25:13.0 +0200 +++ lazygal-0.7.4/PKG-INFO 2012-07-16 07:41:22.0 +0200 @@ -1,6 +1,6 @@ -Metadata-Version: 1.0 +Metadata-Version: 1.1 Name: lazygal -Version: 0.7.3 +Version: 0.7.4 Summary: Static web gallery generator Home-page: http://sousmonlit.dyndns.org/~niol/playa/oss/projects/lazygal Author: Alexandre Rossi --- End Me
Bug#681448: unblock: nsd3/3.2.11-1
On 2012-07-13 10:37, Ondřej Surý wrote: > Package: release.debian.org > Severity: normal > User: release.debian@packages.debian.org > Usertags: unblock > > Please unblock package nsd3 > > Since this version will be the next supported I would like to push > latest upstream, which: > > - add support for TLSA RR type > - add support for ECDSA (Elliptic Curve algorithms) in DNSSEC > > Both of these will hopefully used in upcoming years: > > - EC algorithms have nice properties of being smaller and faster, so > people will rollover to them once the support in DNSSEC validators is > prevalent > - TLSA allows certificate pinning (and even Debian would benefit from > that as you can add trust anchor on the fly for self-signed CAs and certs). > We hope to see support in browsers/MTAs/MUAs etc. start to growing as > the protocol is almost a standard (in RFC-Editor queue for those who > knows what that means :)). > > > The upstream release also includes few minor fixes in IXFR code > and new zone stats, which I haven't enabled since it's a new code. > (I could cherry-pick these two main mentioned features, but I feel > it's not worth it as NSD3 has no rev-deps and the codebase is stable.) > > unblock nsd3/3.2.11-1 > > [...] Hi, The changes sums up to: 79 files changed, 2907 insertions(+), 2130 deletions(-) Which is way more than I can sanely review. Can you generate a manual debdiff where you filter out the auto-generated files (e.g. configlexer.c)? That might give a better view of what is happening. I also noticed this gbp.conf change, which was probably unintented. """ -debian-branch = debian-sid +debian-branch = debian-backports """ -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/50054265.1080...@thykier.net
Re: Report from the first tests of d-i beta 1 candidate images
Cyril Brulebois, le Tue 17 Jul 2012 11:37:50 +0200, a écrit : > I think I'd rather avoid uploading a new d-i at this point, and just > get new images built once the gnome bugs are fixed. Christian, maybe you could call for fixing the translations of the installation manual, so we can upload it to get it onto the beta1 images? Samuel -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120717102145.GB4800@type
Bug#681864: unblock (pre-approval): telepathy-mission-control-5/1:5.12.1-2
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: freeze-exception Hi, I really would like to see telepathy-mission-control-5 5.12.1 being released with Wheezy. The current version in testing/unstable is crashing in numerous occasions and this seems fixed in the experimental version. The version in experimental has been built on all architectures. Before uploading it to unstable I would like to get the approval of the release team. telepathy-mission-control 5.12.1 (2012-07-11) = Fixes: • Stop using deprecated telepathy-glib symbols. (Jonny) • fdo#51842 - fix access to freed memory. (Xavier) • fix existing channel dispatching after using present/delegate. (Jonny) https://bugs.freedesktop.org/show_bug.cgi?id=51842 ChangeLog | 82 +++ INSTALL |9 Makefile.in | 17 + NEWS |9 config.guess | 49 ++-- config.sub | 65 +++-- configure | 20 - configure.ac |2 debian/changelog |7 debian/gbp.conf |4 depcomp | 74 +- doc/reference/mission-control-plugins/html/McpAccountManager.html |2 doc/reference/mission-control-plugins/html/McpDispatchOperation.html |2 doc/reference/mission-control-plugins/html/McpRequest.html |6 doc/reference/mission-control-plugins/html/annotation-glossary.html |2 doc/reference/mission-control-plugins/html/api-index-full.html |2 doc/reference/mission-control-plugins/html/ch01.html |4 doc/reference/mission-control-plugins/html/ch02.html |4 doc/reference/mission-control-plugins/html/ch03.html |4 doc/reference/mission-control-plugins/html/ch04.html |4 doc/reference/mission-control-plugins/html/index.html |2 doc/reference/mission-control-plugins/html/mission-control-plugins-McpAccountStorage.html | 105 +++-- doc/reference/mission-control-plugins/html/mission-control-plugins-McpDispatchOperationPolicy.html | 60 + doc/reference/mission-control-plugins/html/mission-control-plugins-McpRequestPolicy.html | 54 +--- doc/reference/mission-control-plugins/html/mission-control-plugins-Plugin-loader-and-global-functions.html |6 doc/reference/mission-control-plugins/html/object-tree.html |2 install-sh | 29 +- ltmain.sh |4 missing | 53 src/mcd-account-manager-default.c |2 src/mcd-channel.c | 26 +- src/mcd-connection.c | 24 +- src/mcd-dispatcher.c | 29 ++ src/mcd-manager.c | 14 - tests/twisted/dispatcher/redispatch-channels.py | 112 ++ tests/twi
Re: lesstif2 multiarch conversion
Hi, Michael Gilbert (15/07/2012): > Given the reservations expressed lately with respect to multiarch > conversions, I would like to request advance feedback on a possible > lesstif2 nmu enabling multiarch. This is bug #677788, which is one of > the final blockers for ia32-libs. There is already a patch created by > Peter Samuelson that I would like to apply and upload. > > Would the release team be willing to consider this? here's my understanding on the current situation. Other release team members are more than welcome to ACK/NACK any bits. As I already said elsewhere, bumping debhelper and enabling multiarch is what I consider invasive changes, with possible breakages in the reverse dependencies, which one might only notice long after they are introduced. Even for the sake of getting rid of ia32-libs, that seems way too late for me. For the record, even multiarch support in dpkg was way too late, but it was still uploaded more than 4 months ago; furthermore, the dpkg side wasn't even needed to make packages multiarch-ready; so please don't complain if you didn't manage to get packages uploaded before the freeze. On a related note, there's still no dpkg support for coinstallibility of binNMU'd packages, and we already said we wouldn't consider such a patch anyway, because it's just way too late. As sad as it is, it looks to me like ia32-libs will go away in wheezy+1. Mraw, KiBi. signature.asc Description: Digital signature
Report from the first tests of d-i beta 1 candidate images
Hi -boot/-cd, Steve prepared candidate images for d-i beta 1, which I've started testing in virtual machines. Unfortunately the default desktop install (gnome) seems badly broken. So far, I didn't even manage to get a gdm3 prompt: #681830, #681837, #681855. http://bugs.debian.org/681830 http://bugs.debian.org/681837 http://bugs.debian.org/681855 So I'll delay d-i beta 1 until those bugs are fixed. That should buy us some time to try kde/xfce/lxde/server installations, and possibly report some more bugs. Given the images are going to be re-built at some point, I think the pointer to the (known broken) images will be kept somewhere in #debian-boot's topic, to avoid confusion with later builds. I'm not sure whether we want to use this delay to possibly merge a new busybox with the s390x fix prepared by Aurélien Jarno. http://bugs.debian.org/681760 Given the m-i-t fun lately, I think I'd rather avoid uploading a new d-i at this point, and just get new images built once the gnome bugs are fixed. Mraw, KiBi. signature.asc Description: Digital signature
Bug#681859: unblock: lazygal/0.7.4-1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Please unblock package lazygal, this is new upstream release, which only fixes grave bug #681724. It was caused by missing file in upstream tarball, the new version just reintroduces it back. Diff between those two versions is attached. unblock lazygal/0.7.4-1 Thanks - -- Michal Čihař | http://cihar.com | http://blog.cihar.com - -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.1.10-1.16-desktop (SMP w/2 CPU cores; PREEMPT) Locale: LANG=cs_CZ.UTF-8, LC_CTYPE=cs_CZ.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCAAGBQJQBSi1AAoJEGo39bHX+xdNCJ0QAJbVldrbYwSFvryUOLr8Lf91 RrZqtFSxVJXM3htfol2+nrFtdrT8AR2hbEcDYYr7pwQI8YmUoIYPN6Q9l5uAFGWb 71qA9oaXRzPKfZWPYL4yfc4PGRF9527RNK2j5vepRcPdic71WxjS3jSH+cv6jKAL 9X7AUzO2dAaUffc0b4eFkEKe0QIMSKItOWVt20maYTv5jweUTgdTXqIJFcSXBQqK kD9vTx1E4C0u00SjcFoH/Ibu0aG15683g1XsOWc3VxNRzXQehe2JpDEN9cWlbt1v mk5+O8UjRA2i/QDUfHTYprDuADPbNMZkGMktYT4BomRSpyGrONoHLuI96GKB1MUy 4eePkIjO4jc3+1SnIR9JGPFuuv8j5N2iOrv+0wHbDOdhoosOQt/5FLsQU4nnChPm oMyhlWrDMK+jJWfcYZ4T3ufCAGJK4/Ro2x+zoXMYkFlIh+mCi6wWv5nnNEQ2DyqP kjY+GUthxIzwOxX2RWfAWHzBZjEKdxJqWPwAYUzWHGUn917PQ+mIDZFKsltBz4Ij 1OSp2c9vVr6aUJhPIObziQnYZ8PmEYRA8dxQ6TqzmW4jabZeb3LZBhYio6ELOAqT QL2yCQXyGKONUL+hPhtdVmCyb+P5xZvIBeW/0En5YeRCGkktWR2y0iOXzPpYwClt LeXU+j5mU9BO/jN+fsW4 =Pvia -END PGP SIGNATURE- diff -ruNp lazygal-0.7.3/ChangeLog lazygal-0.7.4/ChangeLog --- lazygal-0.7.3/ChangeLog 2012-06-29 16:22:02.0 +0200 +++ lazygal-0.7.4/ChangeLog 2012-07-16 07:36:47.0 +0200 @@ -1,3 +1,6 @@ +Lazygal 0.7.4 (2012-07-16) + * add missing lazygal/defaults.conf in source tarball + Lazygal 0.7.3 (2012-06-29) * fix album picture link on win32 * add --force-gen-pages diff -ruNp lazygal-0.7.3/ChangeLog-full lazygal-0.7.4/ChangeLog-full --- lazygal-0.7.3/ChangeLog-full 2012-06-29 16:24:14.0 +0200 +++ lazygal-0.7.4/ChangeLog-full 2012-07-16 07:36:49.0 +0200 @@ -1,4 +1,8 @@ +Lazygal 0.7.4 (2012-07-16) + * set version to 0.7.4 + Lazygal 0.7.3 (2012-06-29) + * set version to 0.7.3 * update TODO * update french translation * fix album picture link on win32 diff -ruNp lazygal-0.7.3/lazygal/defaults.conf lazygal-0.7.4/lazygal/defaults.conf --- lazygal-0.7.3/lazygal/defaults.conf 1970-01-01 01:00:00.0 +0100 +++ lazygal-0.7.4/lazygal/defaults.conf 2012-07-16 07:32:55.0 +0200 @@ -0,0 +1,32 @@ +[runtime] +quiet = No +debug = No +check-all-dirs = No + +[global] +destdir = . +force-gen-pages = No +clean-destination = No +dir-flattening-depth = No +puburl = No +theme = default + +[webgal] +default-style = default +webalbumpic-bg = transparent +webalbumpic-type = messy +webalbumpic-size = 200x150 +image-size = small=800x600,medium=1024x768 +thumbnail-size = 150x113 +thumbs-per-page = 0 +sort-medias = exif +sort-subgals = dirname +original = No +original-baseurl = No +original-symlink = No +dirzip = No +jpeg-quality = 85 +jpeg-optimize = Yes +jpeg-progressive = Yes +publish-metadata = Yes +keep-gps = No diff -ruNp lazygal-0.7.3/lazygal/__init__.py lazygal-0.7.4/lazygal/__init__.py --- lazygal-0.7.3/lazygal/__init__.py 2012-06-29 16:19:11.0 +0200 +++ lazygal-0.7.4/lazygal/__init__.py 2012-07-16 07:33:12.0 +0200 @@ -58,7 +58,7 @@ def get_hg_rev(): return '' -__version__ = '0.7.3' +__version__ = '0.7.4' hg_rev = get_hg_rev() if hg_rev: __version__ += '+hg' + hg_rev diff -ruNp lazygal-0.7.3/PKG-INFO lazygal-0.7.4/PKG-INFO --- lazygal-0.7.3/PKG-INFO 2012-06-29 16:25:13.0 +0200 +++ lazygal-0.7.4/PKG-INFO 2012-07-16 07:41:22.0 +0200 @@ -1,6 +1,6 @@ -Metadata-Version: 1.0 +Metadata-Version: 1.1 Name: lazygal -Version: 0.7.3 +Version: 0.7.4 Summary: Static web gallery generator Home-page: http://sousmonlit.dyndns.org/~niol/playa/oss/projects/lazygal Author: Alexandre Rossi
Bug#681858: unblock: wajig/2.7.3
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: freeze-exception
Please unblock package wajig
This change contains 2 simple and 'risk-free' fixes:
see http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=681309.
-- System Information:
Debian Release: wheezy/sid
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.2.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_ZA.UTF-8, LC_CTYPE=en_ZA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
diff -Nru wajig-2.7.2/debian/changelog wajig-2.7.3/debian/changelog
--- wajig-2.7.2/debian/changelog 2012-07-16 23:25:33.0 +0200
+++ wajig-2.7.3/debian/changelog 2012-07-12 12:41:11.0 +0200
@@ -1,3 +1,11 @@
+wajig (2.7.3) unstable; urgency=low
+
+ * NEWUPGRADES: a bug introduced in 2.5 made this subcommand illegal;
+Closes: #681309
+ * STATUSSEARCH: same case as above
+
+ -- Tshepang Lekhonkhobe Thu, 12 Jul 2012 12:11:46 +0200
+
wajig (2.7.2) unstable; urgency=low
* For some reason, some temp/build files ended up in the source package :(
diff -Nru wajig-2.7.2/src/wajig.py wajig-2.7.3/src/wajig.py
--- wajig-2.7.2/src/wajig.py 2012-07-16 23:25:33.0 +0200
+++ wajig-2.7.3/src/wajig.py 2012-07-12 12:37:04.0 +0200
@@ -26,7 +26,7 @@
import commands
import perform
-VERSION = "2.7.2"
+VERSION = "2.7.3"
def main():
@@ -679,7 +679,7 @@
function = commands.statusmatch
parser_statusmatch = subparsers.add_parser("statusmatch",
parents=[parser_teach],
- aliases=["statussearch status-search status-match"],
+ aliases="statussearch status-search status-match".split(),
description=function.__doc__)
parser_statusmatch.add_argument("pattern")
parser_statusmatch.set_defaults(func=function)
@@ -713,7 +713,7 @@
function = commands.toupgrade
parser_toupgrade = subparsers.add_parser("toupgrade",
- aliases=["newupgrades new-upgrades to-upgrade"],
+ aliases="newupgrades new-upgrades to-upgrade".split(),
description=function.__doc__)
parser_toupgrade.set_defaults(func=function)
Re: Please give back firebird2.5 on ia64
-=| Cyril Brulebois, 03.07.2012 14:19:40 +0200 |=- > redirecting to ia64@buildd.d.o + wb team: Thanks. (two weeks later) Is there anything I can do to help with this? Original request below: > Damyan Ivanov (03/07/2012): > > Due to #679680 in libatomic-ops-dev, firebird2.5 failed to build on > > ia64. > > > > The bug is fixed in version 7.3~alpha1+git20120701-1, but I am not > > sure what would be the best way to ensure that it is present on the > > buildd. Adding a versioned build-dependency would mean firebird2.5 > > won't be buildable in wheezy (and it built before with the wheezy > > version if libatomic-ops-dev), and I can't figure out the --dep-wait > > wb usage. > > > > In any case, the give-back command would be: > > > > wb gb firebird2.5_2.5.2~svn+54698.ds4-1 . ia64 signature.asc Description: Digital signature
