Bug#608462: unblock: wiliki/0.5.3-1.1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock wiliki/0.5.3-1.1 for squeeze. Thanks to NMU by Yamane-san, a bug tagged squeeze-will-remove has been fixed. Indeed it's quite old but recent versions would be packaged for the next release. Changelog: wiliki (0.5.3-1.1) unstable; urgency=high * Non-maintainer upload with maintainer's ACK. * debian/control - set "Build-Depends: gauche-dev", not gauche to fix configure works (Closes: #608210) -- Hideki Yamane Thu, 30 Dec 2010 00:10:12 +0900 Regards, -- YAEGASHI Takeshi unblock: wiliki/0.5.3-1.1 -- 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/aanlkti=0yg63uscvnfkvbrt8xobu2x2yk3uggnalo...@mail.gmail.com
NEW changes in proposedupdates
Processing changes file: splashy_0.3.13-3+lenny1_amd64.changes ACCEPT -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1pyucy-0006xy...@franck.debian.org
Re: Bug#608347: libtbb2-dbg: Segfault at _dl_relocate_object() dl-reloc.c:242 0x00007ffff7de9b03
Dear Neil and Roberto, Thank you for looking so quickly into this. Here are instructions on how to reproduce the bug: 1) For source code we will use one of the examples that come with the library. To obtain the example install package tbb-examples. 2) Following the instructions in /usr/share/doc/tbb-examples/README.debian, we will make a copy of the examples source to a directory where we have write permissions: cd ~ cp -r /usr/share/doc/tbb-examples/ . cd tbb-examples find . -name '*.gz'| xargs gunzip cd examples 3) The README.debian file now calls to execute "make" to build all examples. Unfortunately the Makefiles shipped with the examples have not been debianized, so they will fail because the directory structure in debian is not the same one that you get when you install directly from http://www.threadingbuildingblocks.org/file.php?fid=77, which is what the current Makefiles expect (this is a separate bug that should be filed against package tbb-examples), so instead, we will fix the Makefile for one of the examples: cd parallel_for/tachyon perl -p -i -e "s/-ltbb_debug/\/usr\/lib\/debug\/usr\/lib\/libtbb.so.2/g" Makefile 4) We will make and try the release version: make release ./tachyon.tbb We get some Usage output 5) Now the debug version: make clean make debug ./tachyon.tbb We get a Segmentation fault My guess is that the libraries in debug mode need to be compiled with some switch in g++ but unfortunately I don't know what it is. Thank you. Regards, Jorge On Thu, Dec 30, 2010 at 2:33 AM, Neil Williams wrote: > On Wed, 29 Dec 2010 22:06:52 -0500 > Roberto C. Sánchez wrote: > > > I am curious as to whether the release team thinks that #608347 > > (quoted below) is really RC. Do I need to target the fix for this to > > go into Squeeze? > > I've tried a simple test program to replicate the results but I don't > know enough about the library to get it to compile. > > Is there a snippet of C code which can be compiled with a simple: > > $ gcc -o test -ltbb test.c > > ? > > (Preferably a sample which just #include's the appropriate headers and > doesn't have to initialise too much other stuff.) > > It doesn't seem fair to seek judgement on the importance of the bug > report without being able to reproduce the problem or find out whether > the problem actually exists on other systems than that of the submitter. > > > > When linking against the tbb debug libraries from the package, a > > > segmentation fault occurs at initialization time: > > It would be very useful to have a test case piece of code from the > original use case too. > > -- > > > Neil Williams > = > http://www.linux.codehelp.co.uk/ > >
Re: Permission to upload oaklisp_1.3.3-3.1 (NMU)
Thanks! (In fact I'm already prepping a fix which includes your patch along with a AMD64 FTBS fix, albeit a 32-bit one.) --Barak. -- 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/e1pyrz9-00040j...@port-kdr.hamilton.local
Permission to upload oaklisp_1.3.3-3.1 (NMU)
Hi Barak, I'm attaching debdiff of a proposed NMU for your oaklisp package, fixing bug #608376. If Release Team finds it good, I plan to upload it to DELAYED/7 to give you some time to upload a fixed package on your own (we're approaching New Year's Eve, hence the longer delay). Release Team, would you grant an unblock request for proposed 1.3.3-3.1 upload? Thanks! -- .''`. : :' : Luca Falavigna `. `' `- diff -u oaklisp-1.3.3/debian/control oaklisp-1.3.3/debian/control --- oaklisp-1.3.3/debian/control +++ oaklisp-1.3.3/debian/control @@ -3,7 +3,7 @@ Priority: extra Maintainer: Barak A. Pearlmutter Standards-Version: 3.8.1 -Build-depends: oaklisp, debhelper (>= 7), texlive-latex-base, texlive-latex-extra +Build-depends: oaklisp, debhelper (>= 7), texlive-latex-base, texlive-latex-extra, texlive-fonts-recommended Homepage: http://oaklisp.alioth.debian.org/ Vcs-Cvs: :pserver:anonym...@cvs.alioth.debian.org:/cvsroot/oaklisp Vcs-Browser: http://alioth.debian.org/plugins/scmcvs/cvsweb.php/?cvsroot=oaklisp diff -u oaklisp-1.3.3/debian/changelog oaklisp-1.3.3/debian/changelog --- oaklisp-1.3.3/debian/changelog +++ oaklisp-1.3.3/debian/changelog @@ -1,3 +1,11 @@ +oaklisp (1.3.3-3.1) unstable; urgency=medium + + * Non-maintainer upload. + * Build-depend on texlive-fonts-recommended to provide support for +ptmr7t font, fix FTBFS (Closes: #608376). + + -- Luca Falavigna Thu, 30 Dec 2010 23:39:19 +0100 + oaklisp (1.3.3-3) unstable; urgency=low * include home page in control file signature.asc Description: OpenPGP digital signature
Re: Please unblock schroot 1.4.16-1
On Thu, 2010-12-30 at 15:38 +, Roger Leigh wrote: > On Wed, Dec 08, 2010 at 08:44:48PM +, Adam D. Barratt wrote: > > As discussed on IRC, it's a shame that this resulted in a new > > translatable (and currently untranslated) string, although the fact that > > the string should rarely be seen and is in the program translation > > rather than a debconf template mitigates this slightly. > > I've allowed a fortnight for translation updates to come back, and > made a new release (1.4.17-1) containing five translation updates > and an additional RC bugfix. Please could you unblock this to > allow it into squeeze? Unblocked; thanks. Regards, Adam -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1293740050.3190.559.ca...@hathi.jungle.funky-badger.org
Re: Accepted gnumed-client 0.7.10-2 (source all)
On Thu, 2010-12-30 at 20:52 +0100, Julien Cristau wrote: > On Thu, Dec 30, 2010 at 20:45:10 +0100, Andreas Tille wrote: > > > On Thu, Dec 30, 2010 at 08:39:29PM +0100, Julien Cristau wrote: > > > On Thu, Dec 30, 2010 at 19:32:06 +, Andreas Tille wrote: > > > > > > > gnumed-client (0.7.10-2) testing-proposed-updates; urgency=low > > > > . > > > Why does this contain the 0.8.5-1 changelog entry? That looks broken. > > > > Because package version 0.8.5-1 was released previosely and I intended > > to keep a full record of all released packages in the changelog. > > That makes no sense. The 0.7.10-2 package doesn't contain the changes > from 0.8.5-1, why should it contain its changelog? More to the point, it's going to make the BTS believe that 0.7.10-2 is a direct descendent of 0.8.5-1 and contains any bugs present in the latter version, which is clearly not the case. The previous intermingling of 0.7.10-1 in the unstable changelog is also broken; the packages are not descended from each other, the changelog should not claim that they are. 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/1293739867.3190.543.ca...@hathi.jungle.funky-badger.org
Re: Accepted gnumed-client 0.7.10-2 (source all)
On Thu, Dec 30, 2010 at 08:39:29PM +0100, Julien Cristau wrote: > On Thu, Dec 30, 2010 at 19:32:06 +, Andreas Tille wrote: > > > gnumed-client (0.7.10-2) testing-proposed-updates; urgency=low > > . > Why does this contain the 0.8.5-1 changelog entry? That looks broken. Because package version 0.8.5-1 was released previosely and I intended to keep a full record of all released packages in the changelog. Kind regards Andreas. PS: Package just uploaded to t-p-u. -- 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/20101230194510.ga28...@an3as.eu
Re: Accepted gnumed-client 0.7.10-2 (source all)
On Thu, Dec 30, 2010 at 20:45:10 +0100, Andreas Tille wrote: > On Thu, Dec 30, 2010 at 08:39:29PM +0100, Julien Cristau wrote: > > On Thu, Dec 30, 2010 at 19:32:06 +, Andreas Tille wrote: > > > > > gnumed-client (0.7.10-2) testing-proposed-updates; urgency=low > > > . > > Why does this contain the 0.8.5-1 changelog entry? That looks broken. > > Because package version 0.8.5-1 was released previosely and I intended > to keep a full record of all released packages in the changelog. That makes no sense. The 0.7.10-2 package doesn't contain the changes from 0.8.5-1, why should it contain its changelog? Cheers, Julien signature.asc Description: Digital signature
Re: Accepted gnumed-client 0.7.10-2 (source all)
On Thu, Dec 30, 2010 at 19:32:06 +, Andreas Tille wrote: > gnumed-client (0.7.10-2) testing-proposed-updates; urgency=low > . Why does this contain the 0.8.5-1 changelog entry? That looks broken. Cheers, Julien signature.asc Description: Digital signature
Bug#607525: marked as done (RM: minitube/1.1-1)
Your message dated Thu, 30 Dec 2010 20:26:52 +0100 with message-id <20101230192652.ga18...@dogguy.org> and subject line Re: Bug#606670: Bug#607525: RM: minitube/1.1-1 has caused the Debian Bug report #607525, regarding RM: minitube/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.) -- 607525: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=607525 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: rm -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Please remove minitube from testing pending a new upstream. The maintainer approves and will seek to get it into volatile instead, because of the unstable API - see #606670. - -- System Information: Debian Release: 6.0 APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iQIcBAEBAgAGBQJNDgZKAAoJEFOUR53TUkxRlq0P/2e/Cd6IqBRlWsVAcPAwudQi fHuALKyCP9dB5agrWfnpHGYXiLIa80pgWiBs59O0jKyme0u3BF4U5aTG5wvInZM+ mAR1IEudYvb3ECRlaFGOe7wnefcJFqMv4uNjT802UR3TdjflqdZ0vhUkcpxegoGs xgJUqe8avhfisQlo/uGfj66Lw9mBmv9qhEvnmyzhlyIMeSHg6PB8+kq90g8gZfNY LwtuXG5slOeZE0KBf3w4sboA3UR7l+AJEoHhs6VaGenwwARDHcKI2+StJPf2NgLM z9Lj5K/vNKnt0Fjq00W9K+9kz1YATO7++Npjybavc9vnOLe2Sz9RdbpF5KybUWyM T13fTTOk1mSKB3GfhkWxRVzIRNYUa4//nWZ8o0zAVKxY3cESyhYsXgjsA6rY6ZJW rBDRfgWpfCOsypMxSCy6YvY8bXsJT1bnUngI7bPcbVLlP+nZSDE6o59eYXAlDdeB phiEpxiC3NAtB4PdVa+87ndsueRA0U8jjOzydaWjB6AOeoGhE6ng2XUHeqiycfeZ wLmljyyk5zxhpU3AO1J5fKPZ5TKwb0BxJr1dDxec8hzwmH+PucvmqYbPZZU2yh75 T2ZG1fEvBr6KZSVtp5HYD2gQMoEfaY9J6As19O72FV6JtM4oF5luWyo/+dBkU7IY YX5mCLAgrw7PBwBdAGTw =9FVw -END PGP SIGNATURE- --- End Message --- --- Begin Message --- On 0, Jakob Haufe wrote: > On Sun, 19 Dec 2010 15:04:13 + > "Adam D. Barratt" wrote: > > > As a side-effect, it will not be possible to include packages which are > > not part of the corresponding stable release. If we remove minitube > > from Squeeze now, further updates once Squeeze is stable would then need > > to be made via backports, rather than volatile. > > > > I have no particular preference which route is taken, but thought it was > > worth spelling out the consequences. > > I would either like to see a freeze exception for 1.3 or, if that's not > possible, a removal of 1.1. Releasing Squeeze with 1.1 makes no sense for me. > > But it's up to the release team to decide on this. > I've added a removal hint for it. Even if we have -updates available, I'm not sure that it should be used for such software. Changes that have been applied between 1.1 and 1.3 are not negligible. It could be tricky to accept such update during stable's lifetime. Regards, -- Mehdi Dogguy --- End Message ---
Bug#608221: marked as done (RM: youtube-dl/2010.12.09-1)
Your message dated Thu, 30 Dec 2010 20:14:37 +0100 with message-id <4d1cda1d.1020...@dogguy.org> and subject line Re: Bug#608221: RM: youtube-dl/2010.12.09-1 has caused the Debian Bug report #608221, regarding RM: youtube-dl/2010.12.09-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.) -- 608221: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=608221 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: rm -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Please hint youtube-dl out of testing as the maintainer has stated it "not suitable for release" (see #608176, which has been opened to stop it migrating to testing again). - -- System Information: Debian Release: 6.0 APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iQIcBAEBAgAGBQJNGky9AAoJEFOUR53TUkxRCZUP/256kDDNLvfs8x24yi3/Ev2M 0G91Y0YMMWHoKG8pGV/+5rKKxdCsvZITjotC5Z/Dg7PgKCEpyr1iZHnSihSy9F9V l8gMUxLIDyxDApvbhNgv5osaX6SvUyl78AVQC927RCn+b468Frqgif5PYmEXk9Zt VRJKq1oHSNr/g2JqYMR0Ud/993XGNaqTabmXtMzHJIQu8Bo78XppWEvNwTTcTj9P qGzZkecdOPiokj10W8eKZVkJMp4S1h/WoAeiyEZ7SGX3jbr4g5WwLFD7rlmcFuTH PbCz0A+LIw9vegNbW6AIzHVZwpg+b6VuPAwmxyLgYFRP9O2N2em0bWWZORDAnM2Z JhpEr4Bfn8aGqMEt7o6ux3y1shDQaJTN09y16O62IfCBCZMgjPAC+L5HlLUBqOfG NhzxXlchnX7kQFjQVZsLTmS0jUclwfgNmC0Oi2N40WBMvDFM1hFROZhJOGNihDg1 sJ2Gf0OPb5Io06XAE6zyJXhHN9R3J1OytwtlrYpLVNUlonSX+Bp/iWocuDOz1VeW Q7iWfE/UcFl8PzLX9RrKemTO1BuMdUiOfgEKgTXE/P2RuyVAtPhOOJTcqMAD2ThB VKcKn5U4PUJNe7TDN9yRrulFjwmcc4lhaHxAA1fMIg7jvxYGuEtyZ+x9zGx/EKjH vxQfHFBJ4FYzc9WoL24l =9Kjm -END PGP SIGNATURE- --- End Message --- --- Begin Message --- On 12/28/2010 09:46 PM, Jonathan Wiltshire wrote: > Package: release.debian.org > Severity: normal > User: release.debian@packages.debian.org > Usertags: rm > > Please hint youtube-dl out of testing as the maintainer has stated it > "not suitable for release" (see #608176, which has been opened to stop it > migrating to testing again). > Removal hint added. Regards, -- Mehdi Dogguy مهدي الدڤي http://dogguy.org/ --- End Message ---
Re: Bug#606719: "Normal" kernel being before the Xen hypervisor in Squeeze
Hello, On Sunday 19 December 2010 12:47:15 Colin Watson wrote: > On Sun, Dec 12, 2010 at 11:48:56AM +0100, Thomas Schmidt wrote: > > Am Sonntag, den 12.12.2010, 14:18 +0800 schrieb Thomas Goirand: > > > For me, it's a grave regression that can put a production environment > > > into big troubles, and it would deserved a RC for me, but because: > > > - of Julien's opinion > > > - that the RT should have the final word > > > - that I respect this view > > > - that delaying Squeeze just for this might not be a good idea > > > - not everyone really cares much about Xen in Debian > > > > > > ... then I sent my report as a wishlist as requested. > > > > I also agree that this needs to be resolved before the release and in my > > opinion this bugs severity should be at least important, if not critical > > because it will "break" Xen dom0 functionality of existing systems when > > they are upgraded from Lenny to Squeeze. > > > > Of course this could be "fixed" by the user of the package by selecting > > an appropriate GRUB_DEFAULT value, but this is likely to break if new > > kernel versions are installed. > > > > The appropriate fix is very simple, just rename /etc/grub.d/20_linux_xen > > to /etc/grub.d/09_linux_xen or some other number in the range of 06-09. > > I'd prefer this to be decided upstream. What do people on grub-devel > think? It does make some sense that the default should be to use Xen if > it's present, IMO. > > (See http://bugs.debian.org/606719 for the full history of this bug.) Any update on this? I have also run into this issue Regards, -- Łukasz Oleś -- 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/201012301925.07473.lukaszo...@gmail.com
Re: Bug#605662: upgrade-reports: removing splashy prevents booting (#512951)
On Thu, 2010-12-30 at 18:48 +0100, Julien Cristau wrote: > On Sun, Dec 12, 2010 at 23:25:08 +0100, Simon Paillard wrote: > > > Dear splashy maintainers, could you upload a 0.3.13-3+lenny1 in > > stable-proposed-updates based on 0.3.13-3 patched with > > 02_lsb-base-logging.sh_bug512951.diff ? > > http://www.debian.org/doc/developers-reference/pkgs.html#upload-stable > > (or I can take care of the NMU) > > > Please prepare/test a NMU, and send a diff to debian-release when ready. It's already in p-u-new; I sincerely hope it was well tested before upload. It'll be in p-u with the next dinstall. 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/1293733315.3190.42.ca...@hathi.jungle.funky-badger.org
Re: Bug#605662: upgrade-reports: removing splashy prevents booting (#512951)
On Sun, Dec 12, 2010 at 23:25:08 +0100, Simon Paillard wrote: > Dear splashy maintainers, could you upload a 0.3.13-3+lenny1 in > stable-proposed-updates based on 0.3.13-3 patched with > 02_lsb-base-logging.sh_bug512951.diff ? > http://www.debian.org/doc/developers-reference/pkgs.html#upload-stable > (or I can take care of the NMU) > Please prepare/test a NMU, and send a diff to debian-release when ready. Cheers, Julien signature.asc Description: Digital signature
Re: Bug#608347: libtbb2-dbg: Segfault at _dl_relocate_object() dl-reloc.c:242 0x00007ffff7de9b03
On Wed, Dec 29, 2010 at 22:06:52 -0500, Roberto C. Sánchez wrote: > I am curious as to whether the release team thinks that #608347 (quoted > below) is really RC. Do I need to target the fix for this to go into > Squeeze? > If the dbg package is indeed unusable then that's a grave bug in that package. It can probably get a squeeze-ignore tag at this point though, but if it's easy enough to fix then I think we should do that. Cheers, Julien signature.asc Description: Digital signature
Re: Suggest to remove visualboyadvance from squeeze
On Thu, Dec 30, 2010 at 02:51:56 -0600, Steve M. Robbins wrote: > ... due to #607598 > I looked at that bug a couple of days ago, and it seemed like a 10 minutes job to fix. Why is removal better? Cheers, Julien signature.asc Description: Digital signature
Re: Please unblock schroot 1.4.16-1
On Wed, Dec 08, 2010 at 08:44:48PM +, Adam D. Barratt wrote:
> On Tue, 2010-12-07 at 17:31 +, Roger Leigh wrote:
> > I've made a new upload of schroot to unstable which fixes a few
> > security- and upgrade-related bugs. The bulk of the changes are
> > documentation (manual pages, release notes and changelogs). The
> > code changes are tiny, but are important to have to upgrade from
> > lenny cleanly and fully document security issues and program
> > behaviour.
>
> Unblocked; thanks.
>
> As discussed on IRC, it's a shame that this resulted in a new
> translatable (and currently untranslated) string, although the fact that
> the string should rarely be seen and is in the program translation
> rather than a debconf template mitigates this slightly.
I've allowed a fortnight for translation updates to come back, and
made a new release (1.4.17-1) containing five translation updates
and an additional RC bugfix. Please could you unblock this to
allow it into squeeze?
Changes:
http://git.debian.org/?p=buildd-tools/schroot.git;a=commitdiff;h=debian/schroot-1.4.17-1;hp=debian/schroot-1.4.16-1
Changes with generated files included:
http://git.debian.org/?p=buildd-tools/schroot.git;a=commitdiff;h=distribution/schroot-1.4.17;hp=distribution/schroot-1.4.16
Many thanks,
Roger
schroot (1.4.17-1) unstable; urgency=low
* New upstream stable release.
* 15killprocs: Don't kill processes in other sessions
(Closes: #608054). Compare full chroot path in addition to device
and inode numbers, since the device and inode are not sufficiently
unique (they are shared between non-cloned sessions such as for
directory type chroots).
* Updated translations:
- da (Closes: #606305). Thanks to Joe Hansen.
- de (Closes: #606245). Thanks to Holger Wansing.
- fr (Closes: #606394). Thanks to Thomas Blein.
- it. Thanks to Vincenzo Campanella.
- zh_CN. Thanks to Ji ZhengYu.
--
.''`. Roger Leigh
: :' : Debian GNU/Linux http://people.debian.org/~rleigh/
`. `' Printing on GNU/Linux? http://gutenprint.sourceforge.net/
`-GPG Public Key: 0x25BFB848 Please GPG sign your mail.
diff --git a/NEWS b/NEWS
index 8fa9bba..bdc5677 100644
--- a/NEWS
+++ b/NEWS
@@ -1,12 +1,16 @@
NEWS-*- outline -*-
-Welcome to schroot 1.4.16. Please read these release notes carefully.
+Welcome to schroot 1.4.17. Please read these release notes carefully.
Full installation instructions are provided in the INSTALL file. The
README file also contains more specific notes regarding building and
configuration.
+* Major changes in 1.4.17:
+
+ None.
+
* Major changes in 1.4.16:
1) Chroot naming restrictions introduced in 1.4.0 have been relaxed
diff --git a/debian/changelog b/debian/changelog
index 19022bf..fdb1c7f 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,20 @@
+schroot (1.4.17-1) unstable; urgency=low
+
+ * New upstream stable release.
+ * 15killprocs: Don't kill processes in other sessions
+(Closes: #608054). Compare full chroot path in addition to device
+and inode numbers, since the device and inode are not sufficiently
+unique (they are shared between non-cloned sessions such as for
+directory type chroots).
+ * Updated translations:
+- da (Closes: #606305). Thanks to Joe Hansen.
+- de (Closes: #606245). Thanks to Holger Wansing.
+- fr (Closes: #606394). Thanks to Thomas Blein.
+- it. Thanks to Vincenzo Campanella.
+- zh_CN. Thanks to Ji ZhengYu.
+
+ -- Roger Leigh Wed, 29 Dec 2010 16:41:30 +
+
schroot (1.4.16-1) unstable; urgency=low
* New upstream stable release.
diff --git a/etc/setup.d/15killprocs b/etc/setup.d/15killprocs
index 619035e..1f246b0 100755
--- a/etc/setup.d/15killprocs
+++ b/etc/setup.d/15killprocs
@@ -40,28 +40,35 @@ do_kill_all()
info "Killing processes run inside $1"
ls /proc | egrep '^[[:digit:]]+$' |
while read pid; do
+ # Check if process root are the same device/inode as chroot
+ # root (for efficiency)
if [ /proc/"$pid"/root -ef "$1" ]; then
-exe=$(readlink /proc/"$pid"/exe || true)
-info "Killing left-over pid $pid (${exe##$1})"
-info " Sending SIGTERM to pid $pid"
+ # Check if process and chroot root are the same (may be
+ # different even if device/inode match).
+ root=$(readlink /proc/"$pid"/root || true)
+ if [ "$root" = "$1" ]; then
+ exe=$(readlink /proc/"$pid"/exe || true)
+ info "Killing left-over pid $pid (${exe##$1})"
+ info " Sending SIGTERM to pid $pid"
-/bin/kill -TERM "$pid" 2>/dev/null
+ /bin/kill -TERM "$pid" 2>/dev/null
-count=0
-max=5
-while [ -d /proc/"$pid" ]; do
-count=$(( $count + 1 ))
-info " Waiting for pid $pid to shut down... ($count/$max)"
-sleep 1
-# Wait for $max seco
Re: sbuild in squeeze
On Thu, Dec 30, 2010 at 11:48:30AM +, Roger Leigh wrote: > On Wed, Dec 29, 2010 at 10:42:23AM +0100, Philipp Kern wrote: > I've cherry-picked all of the required changes and put them here for > your approval (diff also attached against debian/sbuild-0.60.0-2): > > http://git.debian.org/?p=buildd-tools/sbuild.git;a=shortlog;h=refs/heads/sbuild-squeeze > > This is about as minimal as it's possible to make and still have it > non-broken. > > I'll need to do some testing since cherry-picking like this might have > resulted in some needed changes being missed out. But the number of > features being changed is small and discrete, so testing should be > simple and definitive to prove it's working. Once I'm convinced it's > working correctly, may I upload this to testing-proposed-updates? Testing summary: sbuild: - format v1 and v3 (quilt) source packages fetch, unpack and build [OK] - chroot usage with and without namespace qualifiers for clonable and non-clonable chroot types [OK] [all cloning/purging operations work on correct chroot and purging correctly skipped for clonable chroots] utilities: - sbuild-distupgrade [OK] - sbuild-unhold [OK] - sbuild-apt [OK] - sbuild-hold [OK] - sbuild-update [OK] - sbuild-checkpackages [OK] - sbuild-shell [OK] - sbuild-upgrade [OK] - sbuild-clean [OK] - sbuild-stats [OK] All the above tested using chroots with and without namespace qualifiers; debug output used to confirm correct chroot selection [they all use the same core library code to do this, so not tested for every single possible combination; the setup code has been tested in all combinations] - sbuild-createchroot creates valid and working schroot 1.4 configuration [OK] schroot setup scripts - 25nssdatabases copes with comments [OK] I'm satisfied that all the core functionality is working correctly. Regards, Roger -- .''`. Roger Leigh : :' : Debian GNU/Linux http://people.debian.org/~rleigh/ `. `' Printing on GNU/Linux? http://gutenprint.sourceforge.net/ `-GPG Public Key: 0x25BFB848 Please GPG sign your mail. signature.asc Description: Digital signature
Bug#608320: unblock: wiliki/0.5.3-1.1
On Wed, December 29, 2010 21:35, Hideki Yamane wrote: > Please unblock wiliki package, debdiff is here. I've been having a closer look at this package, and I do wonder whether we should be shipping it in Squeeze at all. Despite apparent active upstream development (the last release was a little over two weeks ago) the Debian package has, prior to your NMU, seen one upload since the release of Sarge, and none at all since well before the Etch release. It also has a very low popcon count and bugs - admittedly not many, but even so - with trivial patches open for several years with no maintainer comment. 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/03546a66c808c2344c6f79a05db26869.squir...@adsl.funky-badger.org
Re: sbuild in squeeze
On Wed, Dec 29, 2010 at 10:42:23AM +0100, Philipp Kern wrote:
> Hi Roger,
>
> On Mon, Nov 08, 2010 at 12:10:23PM +, Roger Leigh wrote:
> > sbuild in squeeze has been neglected for some time, and it contains
> > quite a large number of bugs and deficiencies. This was mainly due
> > to the fact that I couldn't devote a huge amount of time to Debian
> > during my PhD, and I only found the time to begin addressing this
> > properly over the last two weeks. The version in unstable now fixes
> > 34 bugs present in squeeze:
>
> sorry that this issue was neglected so long. However the changes are
> massive, which was one of the reasons we were overwhelmed by it. As
> this point in the freeze we cannot accept such an update anymore, too.
> Given that sbuild is still moving in unstable is an indicator for us
> to err on the side of caution.
[...]
> On v3 support: that's definitely needed. You listed two patches in
> <20101115210839.gj15...@codelibre.net>. If that's sufficient, that
> would be reasonable for a targetted fix for squeeze.
OK.
> What's needed to be able to use sbuild's functionality with the stable
> schroot?
sbuild needs to be aware of schroot namespaces. I've been through all
the changes and pulled out the needed changes. This needs changes to
the chroot code and the utility programs. There's also a change to the
25nssdatabases script to stop it breaking with schroot 1.4.
I've cherry-picked all of the required changes and put them here for
your approval (diff also attached against debian/sbuild-0.60.0-2):
http://git.debian.org/?p=buildd-tools/sbuild.git;a=shortlog;h=refs/heads/sbuild-squeeze
This is about as minimal as it's possible to make and still have it
non-broken.
I'll need to do some testing since cherry-picking like this might have
resulted in some needed changes being missed out. But the number of
features being changed is small and discrete, so testing should be
simple and definitive to prove it's working. Once I'm convinced it's
working correctly, may I upload this to testing-proposed-updates?
Regards,
Roger
--
.''`. Roger Leigh
: :' : Debian GNU/Linux http://people.debian.org/~rleigh/
`. `' Printing on GNU/Linux? http://gutenprint.sourceforge.net/
`-GPG Public Key: 0x25BFB848 Please GPG sign your mail.
diff --git a/bin/sbuild-apt b/bin/sbuild-apt
index f9ea814..c868a09 100755
--- a/bin/sbuild-apt
+++ b/bin/sbuild-apt
@@ -48,7 +48,7 @@ if ($command eq "apt-get") {
"Bad command $command. Allowed commands: apt-get or apt-cache\n");
}
-my $session = setup($chroot, $conf) or die "Chroot setup failed";
+my $session = setup('source', $chroot, $conf) or die "Chroot setup failed";
$session->run_apt_command(
{ COMMAND => [$command, @ARGV],
diff --git a/bin/sbuild-checkpackages b/bin/sbuild-checkpackages
index 00a47ce..663a61d 100755
--- a/bin/sbuild-checkpackages
+++ b/bin/sbuild-checkpackages
@@ -74,7 +74,7 @@ my $chroot = $ARGV[0];
setlocale(LC_COLLATE, "POSIX");
$ENV{'LC_COLLATE'} = "POSIX";
-my $session = setup($chroot, $conf) or die "Chroot setup failed";
+my $session = setup('source', $chroot, $conf) or die "Chroot setup failed";
check_packages($session, $mode);
diff --git a/bin/sbuild-clean b/bin/sbuild-clean
index b7e65ab..41c6785 100755
--- a/bin/sbuild-clean
+++ b/bin/sbuild-clean
@@ -108,7 +108,7 @@ foreach (@ARGV) {
my $chroot = Sbuild::Utility::get_dist($_);
-my $session = setup($ARGV[0], $conf) or die "Chroot setup failed";
+my $session = setup('source', $chroot, $conf) or die "Chroot setup failed";
if ($conf->get('CLEAN')) {
print "Performing clean.\n";
diff --git a/bin/sbuild-createchroot b/bin/sbuild-createchroot
index 8c76b3b..9e3211c 100755
--- a/bin/sbuild-createchroot
+++ b/bin/sbuild-createchroot
@@ -158,6 +158,9 @@ $conf->set('INCLUDE', add_items($conf->get('INCLUDE'),
"debfoster"));
my $suite = $ARGV[0];
+# Create the target directory in advance so abs_path (which is buggy)
+# won't fail. Remove if abs_path is replaced by something better.
+makedir($ARGV[1], 0700);
my $target = abs_path($ARGV[1]);
my $mirror = $ARGV[2];
my $script = undef;
@@ -249,7 +252,7 @@ my $chrootname = "${suite}-" . $conf->get('ARCH') . "-sbuild";
if (-d "/etc/schroot/chroot.d") {
# TODO: Don't hardcode path
my $SCHROOT_CONF =
- new File::Temp( TEMPLATE => "$chrootname.XX",
+ new File::Temp( TEMPLATE => "$chrootname-XX",
DIR => "/etc/schroot/chroot.d",
UNLINK => 0)
or die "Can't open schroot configuration file: $!\n";
@@ -259,12 +262,9 @@ if (-d "/etc/schroot/chroot.d") {
[$chrootname]
type=directory
description=Debian $suite/$arch autobuilder
-location=$target
-priority=3
+directory=$target
groups=root,sbuild
root-groups=root,sbuild
-run-setup-scripts=true
-run-exec-scripts=true
EOF
my ($personality, $personality_message);
diff --git a/bin/sbuild-distupgrade b/bin/sbuild-distupgrade
index 5e8cad7..115497e 100755
--- a/bin/sbuild-distupg
Re: Bug#544588: dovecot-antispam: should have a versioned dovecot dependency
re-send to the correct address… On 12/30/2010 12:45 PM, Mehdi Dogguy wrote: > On 12/30/2010 10:44 AM, Reinhard Tartler wrote: >> Since this is AFAIUI the (only) issue why the package has been >> removed from squeeze, would the RT please consider an unblock of >> dovecot-antispam_1.2+20090702-1+b2? >> > > It has been out of testing for (almost) two months. It's a bit late to > re-include it I'm afraid. > > Regards, > -- 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/4d1c7150.40...@debian.org
Bug#544588: dovecot-antispam: should have a versioned dovecot dependency
The following message is a courtesy copy of an article that has been posted to gmane.linux.debian.devel.bugs.general,gmane.linux.debian.devel.release,gmane.linux.debian.devel.wb-team as well. On Mon, Nov 01, 2010 at 17:08:07 (CET), Clint Adams wrote: > severity 564682 serious > quit > > On Sun, Oct 17, 2010 at 08:50:36AM +1030, Ron wrote: >> I'll have a chat to Jaldhar about final plans for squeeze. So far we've >> been somewhat running on the promise of a stable ABI "coming soon". >> I'll see what news there is with that. Merging the packages is surely > > Since the dovecot-antispam in squeeze is completely useless with > the dovecot in squeeze, something should be flagged RC. AFAIUI, this issue can be fixed by a binNMU nmu dovecot-antispam_1.2+20090702-1 . ALL . -m 'Rebuild against dovecot 1.2.15, Closes: #544588' Since this is AFAIUI the (only) issue why the package has been removed from squeeze, would the RT please consider an unblock of dovecot-antispam_1.2+20090702-1+b2? Thanks! -- Gruesse/greetings, Reinhard Tartler, KeyID 945348A4 -- 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/87mxnn3891@faui44a.informatik.uni-erlangen.de
Re: Bug#608347: libtbb2-dbg: Segfault at _dl_relocate_object() dl-reloc.c:242 0x00007ffff7de9b03
On Wed, 29 Dec 2010 22:06:52 -0500 Roberto C. Sánchez wrote: > I am curious as to whether the release team thinks that #608347 > (quoted below) is really RC. Do I need to target the fix for this to > go into Squeeze? I've tried a simple test program to replicate the results but I don't know enough about the library to get it to compile. Is there a snippet of C code which can be compiled with a simple: $ gcc -o test -ltbb test.c ? (Preferably a sample which just #include's the appropriate headers and doesn't have to initialise too much other stuff.) It doesn't seem fair to seek judgement on the importance of the bug report without being able to reproduce the problem or find out whether the problem actually exists on other systems than that of the submitter. > > When linking against the tbb debug libraries from the package, a > > segmentation fault occurs at initialization time: It would be very useful to have a test case piece of code from the original use case too. -- Neil Williams = http://www.linux.codehelp.co.uk/ pgp1MFuPPwfnC.pgp Description: PGP signature
Bug#608355: marked as done (unblock: console-setup/1.66)
Your message dated Thu, 30 Dec 2010 10:41:08 +0100 with message-id <4d1c53b4.5080...@dogguy.org> and subject line Re: Bug#608355: unblock: console-setup/1.66 has caused the Debian Bug report #608355, regarding unblock: console-setup/1.66 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.) -- 608355: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=608355 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 console-setup This upload is a wording/translation fix meant mostly for D-I. In several translations, the keymap variants were still mentioned while the original strings no longer had any mention of the variant. A general cleaning of translations was made to ave them consistent with the original English string in that matter. unblock console-setup/1.66 -- System Information: Debian Release: 6.0 APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-686 (SMP w/2 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash --- End Message --- --- Begin Message --- On 12/30/2010 08:05 AM, Christian Perrier wrote: > Package: release.debian.org > Severity: normal > User: release.debian@packages.debian.org > Usertags: unblock > > Please unblock package console-setup > Unblocked. Regards, -- Mehdi Dogguy مهدي الدڤي http://dogguy.org/ --- End Message ---
Suggest to remove visualboyadvance from squeeze
... due to #607598 -S signature.asc Description: Digital signature
can remove youtube-dl from squeeze
... according to maintainer: #608176 -Steve signature.asc Description: Digital signature
Re: Bug#608190: /etc/gnumed/gnumed-client.conf has wrong database name
On Wed, Dec 29, 2010 at 11:28:15PM +0100, Mehdi Dogguy wrote: > > But, the diff attached looks confusing since there is a changelog entry > for 0.8.5-1 which is in unstable only… and the 0.7.10-2 entry is > targetting unstable, instead of testing. I just changed my local changelog to testing-proposed-updates which I forgot when creating the diff. I'll upload today evening. Kind regards 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/20101230074719.ga2...@an3as.eu
