Re: Ampache Freeze exception
On Mon, 16 Aug 2010 23:15:32 -0500 Charlie Smotherman cj...@cableone.net wrote: Dear Release Team, I have prepared a updated version of ampache which fixes RC bugs #593181, and #593182. Attached is a diff of the proposed changes. http://mentors.debian.net/debian/pool/main/a/ampache/ampache_3.5.4-7.dsc Best regards Charlie Smotherman -Build-Depends: debhelper (= 7.0.50), po-debconf +Build-Depends: debhelper (= 7.0.50), po-debconf, quilt (= 0.46-7) Standards-Version: 3.9.1 Package: ampache diff -Nru ampache-3.5.4/debian/patches/debian-changes-3.5.4-7 ampache-3.5.4/debian/patches/debian-changes-3.5.4-7 --- ampache-3.5.4/debian/patches/debian-changes-3.5.4-7 1969-12-31 18:00:00.0 -0600 +++ ampache-3.5.4/debian/patches/debian-changes-3.5.4-7 2010-08-16 22:24:38.0 -0500 @@ -0,0 +1,390 @@ +Description: Upstream changes introduced in version 3.5.4-7 + This patch has been created by dpkg-source during the package build. + Here's the last changelog entry, hopefully it gives details on why + those changes were made: You've used dpkg-source to create the patch and then specified quilt as a Build-Depends? Yet in the actual source package, you've still declared source format 3.0 (quilt). You don't add a build-depends on quilt when using dpkg-source in quilt mode unless you are doing some unusual stuff with quilt - this package doesn't. http://wiki.debian.org/Projects/DebSrc3.0#Doesa3.0.28quilt.29sourcepackageneedtobuild-dependonquilt.3F That leaves you with all the .pc content in the diff. http://man.he.net/man1/dpkg-source Ask your sponsor or on debian-mentors if you're unsure but this diff is a mess. Source Format 3.0 was meant to avoid the need to add an entire patch system merely to fix release-critical bugs - you've missed the point somewhere. -- Neil Williams = http://www.data-freedom.org/ http://www.linux.codehelp.co.uk/ http://e-mail.is-not-s.ms/ pgpUjJZpyIEXk.pgp Description: PGP signature
Please unblock git-buildpackage 0.5.4
Hi, please unblock the above version. It fixes a nasty bug regarding dsc imports (which didn't get reported to the bts though): * [f63c4ed] git-import-dsc: Don't add superfluous parents to imports on the Debian branch. Only set a parent on the first import per upstream version. has doc updates: * [407b614] docs: Drop git_load_dirs reference we're not using it anymore. * [dbc7fe3] docs: We don't only support .gz tarballs And minor updates: * [88afa61] git-dch: Pass --multimaint-merge on to dch (Closes: #586165) * [e8b6b49] gbp-pq: Use the maintainer of the Debian package as fallback patch author * [af2a435] gbp-pull: Don't update already up to date branches Since this is a leaf package with no reverse dependencies it should be safe. Cheers, -- Guido -- 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/20100817065045.ga31...@bogon.sigxcpu.org
Re: [Pkg-openldap-devel] OpenLDAP upload to unstable.
On Aug 17, 2010, at 12:24 AM, Adam D. Barratt wrote:
On Mon, 2010-08-16 at 17:03 +0200, Matthijs Mohlmann wrote:
On Aug 14, 2010, at 5:13 PM, Adam D. Barratt wrote:
On Tue, 2010-08-10 at 23:44 +0200, Matthijs Möhlmann wrote:
+ # TODO: Now we are doing something that is not allowed by
policy but it
+ # has to be done.
+ sed -i -e s|^SLAPD_CONF=.*|SLAPD_CONF=\${SLAPD_CONF}\|
/etc/default/slapd
That comment immediately make me think uh oh, although I don't
currently have a better alternative to suggest that wouldn't leave
people with a broken system after the upgrade.
A broken system is worse then a policy violation in this case. A solution to
this problem is to move the etc/default/slapd file to usr/share/slapd and let
ucf handle this.
Would this not just replace the policy violation with giving users the
chance to break their own system by rejecting the proposed update to the
configuration? :)
Regards,
Adam
That's true. I think that is something for after the release of squeeze.
Regards,
Matthijs Möhlmann
--
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/c9c01343-ed0b-432a-9847-05b00a450...@cacholong.nl
please give back shogun on mipsel
Hi, shogun fails to build on mipsel (150 minute inactivity timeout compiling a .cxx file of size 5.6MB: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=592748 https://buildd.debian.org/fetch.cgi?pkg=shogunarch=mipselver=0.9.3-3stamp=1280601617file=logas=raw Would it be possible to reschedule a build on a bigger machine (more memory?). Thanks, Soeren -- For the one fact about the future of which we can be certain is that it will be utterly fantastic. -- Arthur C. Clarke, 1962 signature.asc Description: This is a digitally signed message part
Unblock request for debian-archive-keyring/2010.08.15
Hi, please unblock debian-archive-keyring/2010.08.15. debian-archive-keyring (2010.08.15) unstable; urgency=low . * Team upload. * Add Squeeze Stable Release Key (ID: B98321F9). (Closes: #540890) * Add a DEBIAN/md5sums file to the non-udeb package. (Closes: #534934) * Move to debian-archive-removed-keys.gpg: - Debian Archive Automatic Signing Key (4.0/etch) - Etch Stable Release Key - Debian-Volatile Archive Automatic Signing Key (4.0/etch) This includes changes to binary files. Maybe we should switch to jetring at some point. Also this package will get a backport to lenny-p-u. Kind regards, Philipp Kern -- 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/4c6a3ab4.6050...@debian.org
wesnoth-1.8 freeze exception
Hi! Please allow wesnoth-1.8 (1:1.8.3-3) to move over to squeeze. The update now finally contains the unversioned wesnoth and wesnoth-core packages for transitional purpose (#586291) and to ease upgrades to later upstream versions. It also addresses the broken .desktop files (#588712). The diff[1] is not the tinies but it contains the development that I was doing over the last few months and was only recently able to finalize it. Thanks for considering it, Rhonda [1] http://git.debian.org/?p=pkg-games/wesnoth.git;a=commitdiff;h=debian/1.8.3-3;hp=debian/1.8.3-1 -- Lediglich 11 Prozent der Arbeitgeber sind der Meinung, dass jeder Mensch auch ein Privatleben haben sollte. -- http://www.karriere.at/artikel/884/ -- 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/20100817075659.ga19...@anguilla.debian.or.at
Re: uboot-envtools and uboot-mkimage
Le lundi 16 août 2010 à 23:25 +0100, Martin Michlmayr a écrit : * Per Andersson avtob...@gmail.com [2010-08-16 23:15]: Regarding uboot-mkimage and the proposed NMU or adoption. Is it Now that we have u-boot in Debian, maybe uboot-mkimage can be generated from the u-boot source package. u-boot, uboot-envtools and uboot-mkimage could be generated from the same source package, yes. Also, I'm not convinced that we should add an option in Debian that has not been approved in Debian. Is this option even necessary? If I understand correctly what you're trying to do, you can achieve the same by pading the image before running mkimage over it. Does this not work? (not been approved in upstream, you mean?) Well, yes, we can achieve the same thing by padding the image before running mkimage over it, it should work just the same, but it's still something related to u-boot images, and I don't really see why it shouldn't go there. Maybe I should ask upstream, maybe I should do the padding myself before the mkimage call, at several places. signature.asc Description: This is a digitally signed message part
Re: Freeze exception: foomatic-filters 4.0.5
Julien Cristau wrote: On Thu, Aug 12, 2010 at 10:27:32 +0200, Didier 'OdyX' Raboud wrote: So it is IMHO safe to allow on the Debian side too. What do you think ? Ignoring the upstream changes for a moment, I'm uncomfortable with the packaging overhaul. What does make you so uncomfortable ? A big part of the debian/ diff is the changelog merge; the debian/control file sees some minor updates; the debian/rules sees a rewrite towards dh7 (which is way simpler now, but keeps the weirdies of Lenny's); the various maintainer scripts see minor updates too. All in all, it seems me safe and sound (taking apart the dpkg-vendor thing below). Also you're using dpkg-vendor in postinst, which IMO is not appropriate (dpkg-vendor is in dpkg-dev, and the vendor is known at package build time anyway, so you shouldn't need it there). Nice catch. I must confess I hadn't thought for a second that dpkg-vendor wouldn't be necessarily available on user machines. As I forked from the master packaging tree anyway, getting rid of this for an eventual squeeze version is not a problem. I'll rework this on the master tree for squeeze+1 for sure. Lots of buffers with a static size in this code btw, it makes baby Jesus cry. At the very least people should learn sizeof or #define instead of having to remember all the places they need to change the size of the buffers. Things like pdf_count_pages make me think shell code injection, but I don't know what privileges it's running with or if it controls the file name. You had answers from upstream on those ones, it's not something I really have control on. Not knowing anything about cups or this package, can you quickly explain why cups page accounting is something we want in squeeze? Quoting upstream again: the ps_accounting is to get the true number of pages into /var/log/cups/page_log and to make quotas working (you can set page quotas for users in CUPS). It is not required to have printing work correctly but here and there users are complaining that multiple-page jobs are considered one-page in page_log. The experience of Ubuntu shows that it does not break anything. The bugs of the switchover to Foomatic 4.0.x are fixed. So you can activate it by default without problem. So my opinion is that its something good to have in Squeeze, but I can understand that it might be felt too risky. So three solutions IMHO: i) keep foomatic-filters in lenny-style, with Chris as maintainer (basically foomatic-* MIA), no update towards Squeeze; ii) upload foomatic-filters 4.0.5-* with the dpkg-vendor thing removed but with ps_accounting default enabled; iii) upload foomatic-filters 4.0.5-* with the dpkg-vendor thing removed but _without_ the ps_accounting default change; What do you think ? Cheers, OdyX -- 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/i4djs5$i2...@dough.gmane.org
Re: my kde plans for this weekend
On 2010-08-16, Julien Cristau jcris...@debian.org wrote: --cxfMsoqvp1jUizWj Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Aug 16, 2010 at 23:40:59 +, Sune Vuorela wrote: On 2010-08-16, Julien Cristau jcris...@debian.org wrote: src: kdebase-workspace 4:4.4.5-3 around 5 days old =3D20 There's a bunch of debian/changelog changes in there that don't make a lot of sense, shuffling/merging entries around. The other changes look fine. kdebindings 4:4.4.5-2 around 9 days old, rc bug fixes. =3D20 Some more changelog shuffling. Unblocked anyway. =20 We found some lost changelog entries during our svn2git migration. =20 Well it's not just lost changelog entries. Things like this: @@ -689,14 +726,12 @@ =20 * Update installed files. =20 - -- Debian Qt/KDE Maintainers debian-qt-...@lists.debian.org Sun, 31 Au= g 2008 17:07:28 +0200 - -kdebase-workspace (4:4.1.0-3) experimental; urgency=3Dlow + +++ Changes by Armin Berres: =20 * Install konqueror as x-www-browser alternative (Closes: #495746). * Add manpages for konquror, kfmclient and keditbookmarks. =20 - -- Armin Berres armin+deb...@space-based.de Thu, 21 Aug 2008 11:35:14 = +0200 + -- Debian Qt/KDE Maintainers debian-qt-...@lists.debian.org Sun, 31 Au= g 2008 17:07:28 +0200 =20 kdebase-workspace (4:4.1.0-2) experimental; urgency=3Dlow =20 make one wonder what was actually uploaded. The current changelog should show the *actual* history of the uploads, due to branching and merging (and lack of), our svn history didn't actually fully match the 'real' history, and this has been corrected. http://git.debian.org/?p=pkg-kde/kde-sc/kdebase-workspace.git;a=commitdiff;h=55ee0ca2c27b00b383acd23fbd397a9910b9e30d is the full changeset of actually correcting the history. for example, 4:4.1.0-3 has never existed except temporarily in svn. Maybe we should have documented the bugfixing in the changelog better in the changelog, but it didn't happen. /Sune -- 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/slrni6kl4u.rvp.nos...@sshway.ssh.pusling.com
Re: my kde plans for this weekend
On Tue, Aug 17, 2010 at 09:21:34 +, Sune Vuorela wrote: The current changelog should show the *actual* history of the uploads, due to branching and merging (and lack of), our svn history didn't actually fully match the 'real' history, and this has been corrected. http://git.debian.org/?p=pkg-kde/kde-sc/kdebase-workspace.git;a=commitdiff;h=55ee0ca2c27b00b383acd23fbd397a9910b9e30d is the full changeset of actually correcting the history. for example, 4:4.1.0-3 has never existed except temporarily in svn. Maybe we should have documented the bugfixing in the changelog better in the changelog, but it didn't happen. Yes, that would have been nice. Unblocked. Cheers, Julien signature.asc Description: Digital signature
Re: festival recommends change: request/advice
On Mon, Aug 16, 2010 at 21:07:44 -0500, Kumar Appaiah wrote: Thanks for the response. The problem with making Alsa default is this: the method I am aware of to get Alsa used is by feeding the festival output to aplay. Now, I can easily install a festival.scm (Attached for your reference) and ship it with the package. However, this would mean that I *must* depend on alsa-utils, which may or may not be a good thing (you may wish to comment on this). OK, that sucks, nevermind then. What would the release team opinion be? I don't think moving oss-compat from Depends to Recommends is worth it on its own. If you have other important bugfixes in the queue then maybe you can squeeze this in, otherwise I think we can live with the current package. Cheers, Julien signature.asc Description: Digital signature
Re: Unblock request for debian-archive-keyring/2010.08.15
On Tue, Aug 17, 2010 at 09:31:00 +0200, Philipp Kern wrote: Hi, please unblock debian-archive-keyring/2010.08.15. debian-archive-keyring (2010.08.15) unstable; urgency=low . * Team upload. * Add Squeeze Stable Release Key (ID: B98321F9). (Closes: #540890) * Add a DEBIAN/md5sums file to the non-udeb package. (Closes: #534934) * Move to debian-archive-removed-keys.gpg: - Debian Archive Automatic Signing Key (4.0/etch) - Etch Stable Release Key - Debian-Volatile Archive Automatic Signing Key (4.0/etch) There's a bunch of changes not mentioned in changelog: - Uploaders removed - use of debhelper - md5 - sha256 checksums Unblocked, though. Cheers, Julien signature.asc Description: Digital signature
Re: Freeze exception for sssd?
[Petter Reinholdtsen] When the freeze was announced, I was working on an updated sssd package with code to automatically detect the configuration settings during installation, to have this included in Squeeze. The freeze caught us a bit by surprise, but this new autodetection code is now working, and it would be very good to have it included in Squeeze. Any release manager got time to provide input on this request? Happy hacking, -- Petter Reinholdtsen -- 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/2fltymtjyyp@login2.uio.no
Processed: tagging 592421
Processing commands for cont...@bugs.debian.org: tags 592421 + moreinfo Bug #592421 [release.debian.org] unblock: groovy/1.7.4-1 Added tag(s) moreinfo. thanks Stopping processing here. Please contact me if you need assistance. -- 592421: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=592421 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.128204335629510.transcr...@bugs.debian.org
Processed: closing 592228
Processing commands for cont...@bugs.debian.org: close 592228 Bug#592228: unblock: software-center/2.0.7debian4 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug closed, send any further explanations to Julian Andres Klode j...@debian.org thanks Stopping processing here. Please contact me if you need assistance. -- 592228: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=592228 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.128204346730800.transcr...@bugs.debian.org
Re: Freeze exception for sssd?
On 08/13/2010 07:40 AM, Petter Reinholdtsen wrote: If the new autodetection do not work, the sites will be no worse off than before, where the the old static default configuration had to be manually replaced after installation. So the new version make the package better for some sites, and leave the others in the same situation as they used to be in - having to replace the config with their sites settings after installation. This new version will work out of the box for more sites than before, which was zero, but I know it will not work out of the box for all sites, and accept that as it work for the sites I am involved in. :) I would love to get it working for more sites, but suspect that will have to wait for squeeze+1. :( I still have to align with Russ' reasoning. The SRV handling looks totally wrong. To do it this way just to accommodate a certain broken site does not look like technical excellence to me. Sorry. Kind regards, Philipp Kern -- 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/4c6a7e99.10...@debian.org
Re: Freeze exception: dokuwiki (several bugs)
Le jeudi 12 août 2010, Mehdi Dogguy a écrit : On 0, Tanguy Ortolo tanguy+deb...@ortolo.eu wrote: Sorry for this complexity. To sum up, here is what I have, from the most to the least important: * #592593: serious, small addition to debian/rules and documentation; * #592656: important, corrects one path in debian/postinst; * #592653: normal, corrects one path used twice in debian/postinst; * #592651: wishlist [l10n], updates the German debconf translation. Please upload these changes and notify us when the package is accepted. Done. This is the version 0.0.20091225c-8 currently in unstable. As I said in another reply, it contains one more change: an important update of the debian/copyright, to explain the license (MIT) of a file, and what we do with it (stripping it as it is not recompilable with free tools). Do you think you can unblock it so that it reaches Squeeze? Regards, -- Tanguy Ortolo signature.asc Description: Digital signature
Re: Freeze exception: roaraudio, muroard, libao
On Mon, Aug 16, 2010 at 09:07:37PM +0200, Patrick Matth??i wrote: It is not oss-only; roaraudio just fucks up in the current code base if there is ONLY alsa available. Could you be more specific please? One of the biggest motiviations for removing OSS is to get rid of the need for the OSS compatibility bodges which cause all sorts of pain for ALSA. -- 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/20100817122208.ga2...@sirena.org.uk
Re: Freeze exception for sssd?
[Philipp Kern] I still have to align with Russ' reasoning. The SRV handling looks totally wrong. To do it this way just to accommodate a certain broken site does not look like technical excellence to me. Sorry. Well, the options at this time is to (1) release sssd without any automatic configuration (version 1.2.1-1), ensuring it require manual configuration at all sites or (2) updating the version in testing with the version in unstable (version 1.2.1-3) which will work for Debian Edu and site I am working (uio.no) while leaving other sites to still require other sites to do manual configuration. The algorithm I implemented will work for sites only providing SRV entries as well as those like uio.no where service specific DNS aliases are used for unix clients but not windows clients, instead of only working for sites where the SRV entries are used for the unix clients. The alternative algorithm proposed by Ross will fail for sites using SRV records for windows clients and DNS aliases for unix clients, and this seem like a bad idea to me. The implemented algorithm seem to work for mit.edu too (just test using /usr/lib/sssd/generate-config mit.edu), but I do can only look at the values and they seem to make sense to me. I do not really know if those settings really are the correct ones without a mit.edu account. :) Finding an algorithm that will work for more sites would be great, but seem unlikely at this time in the release cycle, and thus I believe it is not really an option. Implementing a algorithm that fail for the only sites I know is not really an option for me. :) Happy hacking, -- Petter Reinholdtsen -- 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/20100817123442.ge13...@login2.uio.no
Re: festival recommends change: request/advice
Dear Julien, On Tue, Aug 17, 2010 at 11:52:25AM +0200, Julien Cristau wrote: On Mon, Aug 16, 2010 at 21:07:44 -0500, Kumar Appaiah wrote: Thanks for the response. The problem with making Alsa default is this: the method I am aware of to get Alsa used is by feeding the festival output to aplay. Now, I can easily install a festival.scm (Attached for your reference) and ship it with the package. However, this would mean that I *must* depend on alsa-utils, which may or may not be a good thing (you may wish to comment on this). OK, that sucks, nevermind then. What would the release team opinion be? I don't think moving oss-compat from Depends to Recommends is worth it on its own. If you have other important bugfixes in the queue then maybe you can squeeze this in, otherwise I think we can live with the current package. That sounds sane. Thanks for the review. Kumar -- Skyhook Where is 'bavaria' proper? I thought it was austria. -- Seen on #Linux -- 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/20100817130744.gd22...@bluemoon.alumni.iitm.ac.in
Freeze exception: man-db 2.5.7-4
I just uploaded this: man-db (2.5.7-4) unstable; urgency=low * Backport from trunk: - Fix a regression introduced in 2.5.7 when running catman in some locales, most notably in the C locale: while converting the output to UTF-8, iconv was run after the compressor rather than before it (closes: #593350, LP: #615045). -- Colin Watson cjwat...@debian.org Tue, 17 Aug 2010 14:54:04 +0100 In my view this is a serious bug, and I'd like to see this fix accepted into squeeze. Thanks, -- Colin Watson [cjwat...@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/20100817140643.gb12...@riva.ucam.org
Re: Moodle package update request
On Mon, Aug 16, 2010 at 10:19 PM, Mehdi Dogguy me...@dogguy.org wrote: On 08/16/2010 10:55 PM, Tomasz Muras wrote: So this is case 2) for me. But now the problem I'm facing is that I've added dfsg already, so I can't go back to the numbering without it! I understand that what I did: removing .swf in rules and adding dfsg didn't make too much of a sense. Maybe the cleanest way out of it now is to remove .swf from source package? I want to package them separately anyway in contrib (and one possibly in non-free). If the license is ok, then there is no need to repackage the source. But, it you're going to repackage the source, I'll wait for the next upload to unblock moodle. Thanks Mehdi, I will repackage the source this time. I will also need to deal with new security vulnerability - I will let you know once I finish. cheers, Tomek -- 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/aanlktimscft9+1vg5qx87jofblyxh80xe07qumt+a...@mail.gmail.com
initramfs-tools 0.98
It contains several worthwile fixes for Squeeze and most importantly full fills the new initramfs policy. please unblock. signature.asc Description: Digital signature
Re: Freeze exception for sssd?
On 08/17/2010 02:34 PM, Petter Reinholdtsen wrote: Well, the options at this time is to (1) release sssd without any automatic configuration (version 1.2.1-1), ensuring it require manual configuration at all sites or (2) updating the version in testing with the version in unstable (version 1.2.1-3) which will work for Debian Edu and site I am working (uio.no) while leaving other sites to still require other sites to do manual configuration. I do see (3) adhere to standards and prefer SRV records, requiring manual configurations on sites that screwed up. Could you enlighten me how this affects Debian Edu in general? I do realize that uio.no might not work with this setup. I cannot see SRV entries on _ldap._tcp.mit.edu, so that's an entirely bogus argument. (I.e. it would still work with the order of the checks reversed.) Kind regards, Philipp Kern -- 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/4c6aa1a9.8050...@debian.org
Bug#593264: Future unblock: libdevel-ebug-perl/0.49-3
Hi Mehdi! On Tue, Aug 17, 2010 at 05:17:08AM +0200, Mehdi Dogguy wrote: On 08/16/2010 09:05 PM, Salvatore Bonaccorso wrote: Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: freeze-exception Hi Release Team! Please unblock package libdevel-ebug-perl Please go ahead and let us know once the package has been accepted. Gregor Herrmann (gregoa) uploaded it for me and the package was accpeted. Bests Salvatore signature.asc Description: Digital signature
Re: Freeze exception for sssd?
[Philipp Kern] I do see (3) adhere to standards and prefer SRV records, requiring manual configurations on sites that screwed up. This is really false dichtonomy, as it is not a question of adhering to standards, but which setup should have priority regarding these standards. For uio.no, Windows and Active Directory got priority for the SRV records, and Linux machines can not use these to locate the LDAP and Kerberos servers. IF they try, they get the AD LDAP server and the AD Kerberos server, and the AD LDAP server do not contain the required LDAP objects needed by NSS. This will be the case for many sites, as most sites have more Windows clients than Linux clients. Windows got the SRV records in DNS, and Linux machines will not get them if they tried. So a different alternative is needed to be able to automatically configure both Linux and Windows clients, I choose to use the setup currently in place here at the university of Oslo, where Linux machines got DNS CNAMEs and AD got SRV records. Could you enlighten me how this affects Debian Edu in general? I do realize that uio.no might not work with this setup. The sssd package for Debian Edu will probably work with both if the main-server is Squeeze based, but will not work if the server is Lenny based, as some of the SRV records were not present or incorrect (unused, untested, bug discovered while working on the Squeeze version) in Lenny. Happy hacking, -- Petter Reinholdtsen -- 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/20100817150446.ga6...@login1.uio.no
Bug#593264: marked as done (Future unblock: libdevel-ebug-perl/0.49-3)
Your message dated Tue, 17 Aug 2010 17:44:07 +0200 with message-id 4c6aae47.7030...@dogguy.org and subject line Re: Bug#593264: Future unblock: libdevel-ebug-perl/0.49-3 has caused the Debian Bug report #593264, regarding Future unblock: libdevel-ebug-perl/0.49-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.) -- 593264: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=593264 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: freeze-exception Hi Release Team! Please unblock package libdevel-ebug-perl libdevel-ebug-perl FTBFS when building with libyaml-syck-perl which entered testing yesterday, 1.12. See [1]. [1] http://bugs.debian.org/593012 0.49-3 contains now a fix for the failing test, so that it passes again the tests during build. Would it be possible to add a freeze-exception or do you would like to have something other changed? libdevel-ebug-perl is not yet uploaded. Please find attached a debdiff for the upload. unblock libdevel-ebug-perl/0.49-3 Thanks in advance for your time. Bests Salvatore -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.26-2-amd64 (SMP w/8 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash diffstat for libdevel-ebug-perl-0.49 libdevel-ebug-perl-0.49 changelog | 16 control |9 +++ copyright | 33 ++ patches/fix_593012_ftbfs_yaml_syck_1_12.patch | 26 patches/series|1 5 files changed, 67 insertions(+), 18 deletions(-) diff -Nru libdevel-ebug-perl-0.49/debian/changelog libdevel-ebug-perl-0.49/debian/changelog --- libdevel-ebug-perl-0.49/debian/changelog2010-05-16 17:24:33.0 +0200 +++ libdevel-ebug-perl-0.49/debian/changelog2010-08-16 20:52:01.0 +0200 @@ -1,3 +1,19 @@ +libdevel-ebug-perl (0.49-3) unstable; urgency=low + + * Add myself to Uploaders. + * Add fix_593012_ftbfs_yaml_syck_1_12.patch patch to fix FTBFS with +libyaml-syck-perl 1.12 (Closes: #593012). + * Refresh debian/copyright: Explicitly refer to GPL-1 license text in +common-licenses as by Debian Policy 3.9.1. + * debian/control: +- Drop alternate Build-Depends on perl (= 5.10) | libmodule-build-perl + as stable has already the required versions and oldstable is gone. +- Remove Build-Depends-Indep on perl and add perl to Build-Depends for + Module::Build. + * Bump Standards-Version to 3.9.1. + + -- Salvatore Bonaccorso salvatore.bonacco...@gmail.com Mon, 16 Aug 2010 20:51:57 +0200 + libdevel-ebug-perl (0.49-2) unstable; urgency=low [ gregor herrmann ] diff -Nru libdevel-ebug-perl-0.49/debian/control libdevel-ebug-perl-0.49/debian/control --- libdevel-ebug-perl-0.49/debian/control 2010-05-16 17:23:38.0 +0200 +++ libdevel-ebug-perl-0.49/debian/control 2010-08-16 20:50:08.0 +0200 @@ -1,8 +1,8 @@ Source: libdevel-ebug-perl Section: perl Priority: optional -Build-Depends: debhelper (= 7.3.7~), perl (= 5.10) | libmodule-build-perl -Build-Depends-Indep: perl, libtest-expect-perl, +Build-Depends: debhelper (= 7.3.7~), perl +Build-Depends-Indep: libtest-expect-perl, libdevel-stacktrace-perl, libproc-background-perl, libstring-koremutake-perl, libclass-accessor-chained-perl, libmodule-pluggable-perl, libpadwalker-perl, libyaml-syck-perl, netbase, libtest-pod-perl, libyaml-perl @@ -10,8 +10,9 @@ Uploaders: Martín Ferrari tin...@debian.org, gregor herrmann gre...@debian.org, Jose Luis Rivas ghostba...@gmail.com, - Ansgar Burchardt ans...@43-1.org -Standards-Version: 3.8.4 + Ansgar Burchardt ans...@43-1.org, + Salvatore Bonaccorso salvatore.bonacco...@gmail.com +Standards-Version: 3.9.1 Homepage: http://search.cpan.org/dist/Devel-ebug/ Vcs-Svn: svn://svn.debian.org/pkg-perl/trunk/libdevel-ebug-perl/ Vcs-Browser: http://svn.debian.org/viewsvn/pkg-perl/trunk/libdevel-ebug-perl/ diff -Nru libdevel-ebug-perl-0.49/debian/copyright libdevel-ebug-perl-0.49/debian/copyright --- libdevel-ebug-perl-0.49/debian/copyright2010-05-16 16:39:46.0 +0200 +++ libdevel-ebug-perl-0.49/debian/copyright2010-08-16 20:41:30.0 +0200 @@ -3,25 +3,30 @@ Source: http://search.cpan.org/dist/Devel-ebug/ Name: Devel-ebug
Re: Freeze exception: man-db 2.5.7-4
On 08/17/2010 04:06 PM, Colin Watson wrote: I just uploaded this: man-db (2.5.7-4) unstable; urgency=low * Backport from trunk: - Fix a regression introduced in 2.5.7 when running catman in some locales, most notably in the C locale: while converting the output to UTF-8, iconv was run after the compressor rather than before it (closes: #593350, LP: #615045). -- Colin Watson cjwat...@debian.org Tue, 17 Aug 2010 14:54:04 +0100 Unblocked. 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/4c6aaef3.90...@dogguy.org
Re: Freeze exception: dokuwiki (several bugs)
On 08/17/2010 02:22 PM, Tanguy Ortolo wrote: Do you think you can unblock it so that it reaches Squeeze? Unblocked. 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/4c6ab079.3090...@debian.org
Re: Ampache Freeze exception
On Tue, 2010-08-17 at 07:59 +0100, Neil Williams wrote:
On Mon, 16 Aug 2010 23:15:32 -0500
Charlie Smotherman cj...@cableone.net wrote:
Dear Release Team,
I have prepared a updated version of ampache which fixes RC bugs
#593181, and #593182. Attached is a diff of the proposed changes.
http://mentors.debian.net/debian/pool/main/a/ampache/ampache_3.5.4-7.dsc
Best regards
Charlie Smotherman
-Build-Depends: debhelper (= 7.0.50), po-debconf
+Build-Depends: debhelper (= 7.0.50), po-debconf, quilt (= 0.46-7)
Standards-Version: 3.9.1
Package: ampache
diff -Nru ampache-3.5.4/debian/patches/debian-changes-3.5.4-7
ampache-3.5.4/debian/patches/debian-changes-3.5.4-7
--- ampache-3.5.4/debian/patches/debian-changes-3.5.4-7
1969-12-31 18:00:00.0 -0600 +++
ampache-3.5.4/debian/patches/debian-changes-3.5.4-7 2010-08-16
22:24:38.0 -0500 @@ -0,0 +1,390 @@ +Description: Upstream
changes introduced in version 3.5.4-7
+ This patch has been created by dpkg-source during the package build.
+ Here's the last changelog entry, hopefully it gives details on why
+ those changes were made:
You've used dpkg-source to create the patch and then specified quilt as
a Build-Depends? Yet in the actual source package, you've still
declared source format 3.0 (quilt). You don't add a build-depends on
quilt when using dpkg-source in quilt mode unless you are doing some
unusual stuff with quilt - this package doesn't.
http://wiki.debian.org/Projects/DebSrc3.0#Doesa3.0.28quilt.29sourcepackageneedtobuild-dependonquilt.3F
That leaves you with all the .pc content in the diff.
http://man.he.net/man1/dpkg-source
Ask your sponsor or on debian-mentors if you're unsure but this diff is
a mess. Source Format 3.0 was meant to avoid the need to add an entire
patch system merely to fix release-critical bugs - you've missed the
point somewhere.
Neil,
Sorry, thanks for the education, attached is a new diff.
http://mentors.debian.net/debian/pool/main/a/ampache/ampache_3.5.4-7.dsc
Charlie
diff -Nru ampache-3.5.4/debian/ampache.postinst ampache-3.5.4/debian/ampache.postinst
--- ampache-3.5.4/debian/ampache.postinst 2010-08-01 23:06:51.0 -0500
+++ ampache-3.5.4/debian/ampache.postinst 2010-08-15 22:17:57.0 -0500
@@ -26,9 +26,8 @@
}
apache_install() {
-webserver=$1
-if [ -d /etc/$webserver/conf.d ] [ ! -h /etc/$webserver/conf.d/ampache.conf ]; then
-ln -s $AMP /etc/$webserver/conf.d/ampache.conf
+if [ ! -f /etc/apache2/conf.d/ampache.conf ] [ ! -h /etc/apache2/conf.d/ampache.conf ]; then
+ln -s $AMP /etc/apache2/conf.d/ampache.conf
if [ -f $ELCAMP ]; then
rm -f $ELCAMP
fi
diff -Nru ampache-3.5.4/debian/changelog ampache-3.5.4/debian/changelog
--- ampache-3.5.4/debian/changelog 2010-08-12 10:28:47.0 -0500
+++ ampache-3.5.4/debian/changelog 2010-08-17 06:52:04.0 -0500
@@ -1,3 +1,14 @@
+ampache (3.5.4-7) unstable; urgency=high
+
+ * Adjusted symlink creation in debian/postinst so it now works.
+Closes: #593181
+ * Upstream neglected to comment out the require once for
+/modules/pearxmlrpc/rpc.php which causes the inital login after the
+completion of the web installer to fail due to php not being able to find
+/modules/pearxmlrpc/rpc.php. Closes: #593182
+
+ -- Charlie Smotherman cj...@cableone.net Sun, 17 Aug 2010 06:51:29 -0500
+
ampache (3.5.4-6) unstable; urgency=high
* Setting urgency to high as this fixes an RC bug.
diff -Nru ampache-3.5.4/debian/patches/debian-changes-3.5.4-7 ampache-3.5.4/debian/patches/debian-changes-3.5.4-7
--- ampache-3.5.4/debian/patches/debian-changes-3.5.4-7 1969-12-31 18:00:00.0 -0600
+++ ampache-3.5.4/debian/patches/debian-changes-3.5.4-7 2010-08-17 07:46:31.0 -0500
@@ -0,0 +1,43 @@
+Description: Upstream changes introduced in version 3.5.4-7
+ This patch has been created by dpkg-source during the package build.
+ Here's the last changelog entry, hopefully it gives details on why
+ those changes were made:
+ .
+ ampache (3.5.4-7) unstable; urgency=high
+ .
+ * Adjusted symlink creation in debian/postinst so it now works.
+ Closes: #593181
+ * Upstream neglected to comment out the require once for
+ /modules/pearxmlrpc/rpc.php which causes the inital login after the
+ completion of the web installer to fail due to php not being able to find
+ /modules/pearxmlrpc/rpc.php. Closes: #593182
+ .
+ The person named in the Author field signed this changelog entry.
+Author: Charlie Smotherman cj...@cableone.net
+Bug-Debian: http://bugs.debian.org/593181
+Bug-Debian: http://bugs.debian.org/593182
+
+---
+The information above should follow the Patch Tagging Guidelines, please
+checkout http://dep.debian.net/deps/dep3/ to learn about the format. Here
+are templates for supplementary fields that you might want to add:
+
+Origin: vendor|upstream|other, url of original patch
+Bug: url in
Re: updated packages for squeeze
On Tue, 2010-08-17 at 00:16 +0200, Julien Cristau wrote: On Sun, Aug 15, 2010 at 13:15:59 +0200, Arthur de Jong wrote: cvsd (1.0.19) UNRELEASED; urgency=low I'd avoid the package format change if possible. The rest sounds fine. I thought there weren't any meaningful differences between 1.0 (native) and 3.0 (native)? Anyway, I'll switch back to 1.0 (keeping the debian/source/format file) and upload to unstable. nss-pam-ldapd (0.7.8) UNRELEASED; urgency=low Seems ok. I'm not sure about modifying nsswitch.conf, but the devil is probably in the details. The postinst and postrm of libnss-ldapd already do this (that is also where the code to do the actual modification came from so it should be well tested). A discussion on whether this is ok can be found here: http://lists.debian.org/debian-devel/2007/02/msg00076.html Please request translations early though, if not already done. I've asked for an English review first (which gave very useful feedback) and will send out a call for translations shortly. In the mean time I'll upload the changes above so people can test. python-stdnum (0.2-1) UNRELEASED; urgency=low Will probably remove it, then. That is probably the best, please remove python-stdnum from squeeze. Thanks for the reply and thanks for all the hard work. -- -- arthur - adej...@debian.org - http://people.debian.org/~adejong -- signature.asc Description: This is a digitally signed message part
Re: Permission to upload gtg_0.2.4-3 [UPLOADED]
Il 11/08/2010 0.38, Philipp Kern ha scritto: You can go ahead with the upload. Please ping us when it got accepted. Uploaded, and accepted. Thanks! -- .''`. : :' : Luca Falavigna dktrkr...@debian.org `. `' `- signature.asc Description: OpenPGP digital signature
Re: Bug#506809: oolite: new upstream release (1.73)
Ludovic Brenta wrote: Any objections, please raise your hand. We're in the begining of a GNUstep transition, which is unfortunately blocked by serious issues on hppa. As the release team is unlikely to approve a new upstream release at this point, any eventual problems in oolite must be addressed with an upload of the present version to t-p-u. So I suggest to upload this new release to experimental, not sid. (But feel free to consult with -release (CCed)). -- 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/87mxslchru.gnus_not_unix!%ya...@gnu.org
Re: please give back shogun on mipsel
On 08/17/2010 09:16 AM, Soeren Sonnenburg wrote: Hi, shogun fails to build on mipsel (150 minute inactivity timeout compiling a .cxx file of size 5.6MB: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=592748 I also see that your package FTBFS on kfreebsd-i386 and hppa. It's killed while generating the documentation. Do you intend to fix those failures as well? You could you change your packaging so that documentation is not generated on buildds. It's a workaround but also a way to save some resources on buildds since arch:all packages are not uploaded when built there. Would it be possible to reschedule a build on a bigger machine ? We can't choose the buildd. I'll give it back and see what will happen. 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/4c6abfb6.3080...@dogguy.org
Re: Bug#506809: oolite: new upstream release (1.73)
On 08/17/2010 06:42 PM, Yavor Doganov wrote: Ludovic Brenta wrote: Any objections, please raise your hand. We're in the begining of a GNUstep transition, which is unfortunately blocked by serious issues on hppa. As the release team is unlikely to approve a new upstream release at this point, any eventual problems in oolite must be addressed with an upload of the present version to t-p-u. So I suggest to upload this new release to experimental, not sid. (But feel free to consult with -release (CCed)). Could you send a diff please? Is the new upstream an almost complete rewrite of the sources? If the diff is big, then, yes, we would prefer to stick with the current version. 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/4c6ac1d5.20...@dogguy.org
Re: Permission to upload gtg_0.2.4-3 [UPLOADED]
On 08/17/2010 06:03 PM, Luca Falavigna wrote: Il 11/08/2010 0.38, Philipp Kern ha scritto: You can go ahead with the upload. Please ping us when it got accepted. Uploaded, and accepted. Unblocked. Kind regards, Philipp Kern -- 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/4c6ac92e.8070...@debian.org
Re: Ampache Freeze exception
On Tue, 2010-08-17 at 11:15 -0500, Charlie Smotherman wrote: [...] On Mon, 16 Aug 2010 23:15:32 -0500 Charlie Smotherman cj...@cableone.net wrote: I have prepared a updated version of ampache which fixes RC bugs #593181, and #593182. Attached is a diff of the proposed changes. [...] http://mentors.debian.net/debian/pool/main/a/ampache/ampache_3.5.4-7.dsc Please go ahead and let us know once the package has been accepted. 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/1282067772.6943.97.ca...@kaa.jungle.aubergine.my-net-space.net
RFC: SQLite3 in Squeeze
Hi Release Team, There's a problem with SQLite3 3.7.0 in Squeeze. The version in testing (3.6.23.1-4) was suitable to release. Next major upstream version (3.7.0) was released, which was uploaded to unstable. Then freeze happened. The latest release came with problems, like slow song change with Banshee (reported as #591298 [1]). In that bugreport I noted that v3.7.0 has a database corruption issue as well and I'm waiting for v3.7.0.1 to be released. Then I had to travel for some days. The bad thing is, that Iain Lane was so disappointed with the slow Banshee song change that he prepared an NMU of SQLite3 with a backported fix of that slowness. Julien Cristau uploaded his NMU, with high urgency. Both of them ignored the fact that there's an unfixed database corruption issue in that NMU. The bad thing is, somehow 3.7.0-1.1 migrated to Squeeze, even if it was not affected by this bug. As 3.7.0.1 was released (fixing an other performance regression and the potential database corruption), I have uploaded it to unstable and it's ready to migrate. The problem is, the performance regression hit by Banshee is still present. While it would be good to have 3.7.0.1-1 in testing, it's still not suitable to release because of the latter problem. What should I do? I don't have package version 3.6.23.1-4 anymore and I don't know when this bug will be fixed or if it will be easily backportable. Regards, Laszlo/GCS [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=591298 -- 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/1282067389.3511.266.ca...@julia.gcs.org.hu
Bug#593377: unblock: ziproxy/3.1.3-1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: freeze-exception Hi Release Team, Please unblock package ziproxy This upload fixes two RC bugs. The last changelog entry reads as follows: ziproxy (3.1.3-1) unstable; urgency=low . * New upstream release (LP: #569611) * debian/patches/02_ziproxy_3.1.1_speedup.diff - Removed, merged upstream. * debian/preinst - Removed, old command moved to postinst (Closes: #566589) - Thanks piuparts ;-) * debian/control - Standards-Version updated * Disabled Nameservers option (Closes: #591417) (LP: #539874) - Thanks to all in 591417@ and the upstream! - debian/README.Debian - Reason for it added. - New patch: debian/02_off_nameservers_opt.diff The diff with the current version in testing is quite huge 93 files changed, 8255 insertions(+), 2698 deletions(-) but 3.1.1-1 was granted a freeze exception and the diff [1] 3.1.1-1/3.1.3-1 is totally reasonable. [1] http://people.debian.org/~mehdi/ziproxy.diff unblock ziproxy/3.1.3-1 Regards, -- Mehdi Dogguy -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/4 CPU cores) 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/20100817175506.3156.70921.report...@localhost.localdomain
Please let ydpdict 1.0.0-2 into testing
Hello, Please let ydpdict 1.0.0-2 into testing. Compared with the version already there (1.0.0-1) it has: - a fix for an importrant bug - a fix for another bug (severity=normal), but with a trivial fix - documentation updates - changed the DEB_BUILD_OPTS parsing to match what the policy suggests Attaching the full interdiff. -- Marcin Owsiany porri...@debian.org http://marcin.owsiany.pl/ GnuPG: 1024D/60F41216 FE67 DA2D 0ACA FC5E 3F75 D6F6 3A0D 8AA0 60F4 1216 diff -u ydpdict-1.0.0/debian/changelog ydpdict-1.0.0/debian/changelog --- ydpdict-1.0.0/debian/changelog +++ ydpdict-1.0.0/debian/changelog @@ -1,3 +1,20 @@ +ydpdict (1.0.0-2) unstable; urgency=medium + + * Cherry-picking some upstream fixes for squeeze +- documentation updates +- license text update and copyright clarification +- copyright year updates +- a fix for severity=important segfault with newer libao library caused by + an uninitialized data structure field (closes: #591464) +- a fix for buggy sample file path computation (closes: #592067) - it is + severity normal, but I chose to include it because it is a trivial, + extremely low risk change + * Bumping Standards-Version to 3.9.1. Necessary changes were: +- clarify the non-freeness of the package in debian/copyright +- use the policy-suggested makefile snippet for handling noopt + + -- Marcin Owsiany porri...@debian.org Sat, 07 Aug 2010 17:33:10 +0100 + ydpdict (1.0.0-1) unstable; urgency=low * New upstream version diff -u ydpdict-1.0.0/debian/copyright ydpdict-1.0.0/debian/copyright --- ydpdict-1.0.0/debian/copyright +++ ydpdict-1.0.0/debian/copyright @@ -1,6 +1,9 @@ This package was debianized by Marcin Owsiany porri...@debian.org on Fri, 28 May 2004 15:37:17 +0200 +This package is not part of Debian GNU/Linux because it depends on non-free +dictionary files distributed by Young Digital Planet to be useful. + It was downloaded from http://toxygen.net/ydpdict/ Copyright and author information: @@ -11,18 +14,25 @@ Copyright 2004-2007 Marcin Owsiany porri...@debian.org + adpcm.c and adpcm.h: + Copyright (C) 1999 Stanley J. Brooks sta...@megsinet.net License information: - ydpdict jest wydany na licencji GPL w wersji 2, która jest dostępna - w pliku COPYING. Wszelkie poprawki wysłane do autora na licencji innej - niż GPL w wersji 2 zostaną odrzucone. Brak informacji o licencji będzie - traktowany jak przyjęcie licencji kodu, który jest poprawiany. - + ydpdict jest wydany na licencji GPL w wersji 2 (treść w języku angielskim + dostępna w pliku COPYING). Wszelkie poprawki wysłane do autora na licencji + innej niż GPL w wersji 2 zostaną odrzucone. Brak informacji o licencji + będzie traktowany jak przyjęcie licencji kodu, który jest poprawiany. + Wyjątkiem są pliki adpcm.c i adpcm.h autorstwa Stanley'a J. Brooksa wydane + na licencji LGPL w wersji 2. + Unofficial translation: - ydpdict is distributed under GPL version 2 license, which is available in the - COPYING file. Any fixes sent to the author covered by a license other than - GPL version 2 will be rejected. No information about a license will be + ydpdict is distributed under GPL version 2 license (English text is available + in the COPYING file). Any fixes sent to the author covered by a license other + than GPL version 2 will be rejected. No information about a license will be treated as accepting the license of the code being fixed. + An exception are the files adpcm.c and adpcm.h by Stanley J. Brooks, + distributed under LGPL version 2 license. -On Debian systems, see /usr/share/common-licenses/GPL-2 for the full license text. +On Debian systems, see /usr/share/common-licenses/GPL-2 for the full GPL 2 license text. +On Debian systems, see /usr/share/common-licenses/LGPL-2 for the full LGPL 2 license text. diff -u ydpdict-1.0.0/debian/control ydpdict-1.0.0/debian/control --- ydpdict-1.0.0/debian/control +++ ydpdict-1.0.0/debian/control @@ -3,7 +3,7 @@ Priority: optional Maintainer: Marcin Owsiany porri...@debian.org Build-Depends: debhelper (= 5), libncursesw5-dev, libydpdict2-dev, libao-dev, pkg-config -Standards-Version: 3.7.3 +Standards-Version: 3.9.1 Homepage: http://toxygen.net/ydpdict/ Package: ydpdict diff -u ydpdict-1.0.0/debian/rules ydpdict-1.0.0/debian/rules --- ydpdict-1.0.0/debian/rules +++ ydpdict-1.0.0/debian/rules @@ -11,7 +11,7 @@ DEB_BUILD_GNU_TYPE ?= $(shell dpkg-architecture -qDEB_BUILD_GNU_TYPE) CFLAGS += -g -ifneq (,$(findstring noopt,$(DEB_BUILD_OPTIONS))) +ifneq (,$(filter noopt,$(DEB_BUILD_OPTIONS))) CFLAGS += -O0 else CFLAGS += -O2 only in patch2: unchanged: --- ydpdict-1.0.0.orig/README +++ ydpdict-1.0.0/README @@ -5,19 +5,21 @@ Program, którego dokumentację w tej chwili czytasz, służy do obsługi multimedialnych słowników angielsko-polskiego, polsko-angielskiego, niemiecko-polskiego i polsko-niemieckiego Collinsa. Oryginalne pakiety -
Re: RFC: SQLite3 in Squeeze
On Tue, Aug 17, 2010 at 07:49:49PM +0200, Laszlo Boszormenyi wrote: While it would be good to have 3.7.0.1-1 in testing, it's still not suitable to release because of the latter problem. What should I do? I don't have package version 3.6.23.1-4 anymore and I don't know when this bug will be fixed or if it will be easily backportable. While you'll have to play some games with version numbering, does the source package for 3.6.23.1-4 on snapshot [1] help? 1: http://snapshot.debian.org/package/sqlite3/3.6.23.1-4/ -- Jonathan Wiltshire 4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC 74C3 5394 479D D352 4C51 signature.asc Description: Digital signature
Re: please give back shogun on mipsel
On Tue, 2010-08-17 at 18:58 +0200, Mehdi Dogguy wrote: On 08/17/2010 09:16 AM, Soeren Sonnenburg wrote: Hi, shogun fails to build on mipsel (150 minute inactivity timeout compiling a .cxx file of size 5.6MB: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=592748 I also see that your package FTBFS on kfreebsd-i386 and hppa. It's killed while generating the documentation. Do you intend to fix those failures as well? Sure, but these failures are failures of doxygen 1.7.1 - not the g++ timeout compiling a too big file as is the case on mipsel. You could you change your packaging so that documentation is not generated on buildds. I was actually attempting this in my last upload by putting Architecture all for both doc packages and telling cdbs to only do things in build-indep: not sure why it does not work. It's a workaround but also a way to save some resources on buildds since arch:all packages are not uploaded when built there. Sure I would love to have this. Nevertheless, the FTBS's on the other archs are caused by doxygen for which I've filed bugs #593317, #591648 - that look similar to me but no idea why it is failing at different stages... Would it be possible to reschedule a build on a bigger machine ? We can't choose the buildd. I'll give it back and see what will happen. trial and error then :( Regards, Thanks, Soeren -- For the one fact about the future of which we can be certain is that it will be utterly fantastic. -- Arthur C. Clarke, 1962 signature.asc Description: This is a digitally signed message part
Re: initramfs-tools 0.98
On Tue, 2010-08-17 at 16:42 +0200, maximilian attems wrote:
It contains several worthwile fixes for Squeeze and
most importantly full fills the new initramfs policy.
please unblock.
A quick question on the diff:
+# Common case: /sbin/init is present
+if [ ! -x ${rootmnt}/sbin/init ]; then
+ # ... if it's not available search for valid init
+ if [ -z ${init} ] ; then
+ for inittest in /sbin/init /etc/init /bin/init /bin/sh; do
+ if validate_init ${inittest}; then
+ init=$inittest
+ break
+ fi
+ done
+ fi
+
+ # No init on rootmount
+ if ! validate_init ${init} ; then
+ panic No init found. Try passing init= bootarg.
+ fi
fi
So far as I can see, if /sbin/init is present and executable, but $init
is set to something else, then the init which will be executed is not
checked via validate_init(). If so then should the no init on
rootmount block be moved outside of the if block?
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/1282069037.7563.62.ca...@kaa.jungle.aubergine.my-net-space.net
Re: RFC: SQLite3 in Squeeze
On 08/17/2010 07:49 PM, Laszlo Boszormenyi wrote: I don't have package version 3.6.23.1-4 anymore. Out of curiosity, don't use a $VCS to maintain the source package? 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/4c6ad490.4010...@dogguy.org
Re: Please let ydpdict 1.0.0-2 into testing
On Sun, 2010-08-15 at 19:36 +0100, Marcin Owsiany wrote: Please let ydpdict 1.0.0-2 into testing. Compared with the version already there (1.0.0-1) it has: - a fix for an importrant bug - a fix for another bug (severity=normal), but with a trivial fix - documentation updates - changed the DEB_BUILD_OPTS parsing to match what the policy suggests Unblocked. 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/1282070357.8054.6.ca...@kaa.jungle.aubergine.my-net-space.net
Freeze exception: python-defaults 2.6.5-13
Please unblock python-defaults 2.6.5-13. It fixes some important bugs related to dh_python2 and pycompile (+ some policy/docs changes) -- Piotr Ożarowski Debian GNU/Linux Developer www.ozarowski.pl www.griffith.cc www.debian.org GPG Fingerprint: 1D2F A898 58DA AF62 1786 2DF7 AEF6 F1A2 A745 7645 signature.asc Description: Digital signature
Freeze exception: python3-defaults 3.1.2-6
Please unblock python3-defaults 3.1.2-6. It fixes some important bugs
related to dh_python3 and py3compile.
--
Piotr Ożarowski Debian GNU/Linux Developer
www.ozarowski.pl www.griffith.cc www.debian.org
GPG Fingerprint: 1D2F A898 58DA AF62 1786 2DF7 AEF6 F1A2 A745 7645
diff -Nru python3-defaults-3.1.2/debian/changelog
python3-defaults-3.1.2/debian/changelog
--- python3-defaults-3.1.2/debian/changelog 2010-07-28 22:49:13.0
+0200
+++ python3-defaults-3.1.2/debian/changelog 2010-08-13 23:29:29.0
+0200
@@ -1,3 +1,23 @@
+python3-defaults (3.1.2-6) unstable; urgency=low
+
+ [ Matthias Klose ]
+ * Substitution variables for control files always start with a `python3'
+prefix (python:Versions - python3:Versions, python:Provides -
+python3:Provides).
+ * Generate dependencies on python3 (= 3.1.2-6~).
+
+ [ Piotr Ożarowski ]
+ * py3compile: do not hang if interpreters are not started in the same order
+as they're used
+ * dh_python3: pass shallow=False to cmpfiles to make sure file comparison
+works as expected
+
+ [ Scott Kitterman ]
+ * Us X-Python3-Version for Python 3 instead of XS-Python-Version (which
+should just be used for Python)
+
+ -- Piotr Ożarowski pi...@debian.org Fri, 13 Aug 2010 23:27:45 +0200
+
python3-defaults (3.1.2-5) unstable; urgency=medium
* Add README.PyDist to python3-doc package
diff -Nru python3-defaults-3.1.2/debian/py3versions.py
python3-defaults-3.1.2/debian/py3versions.py
--- python3-defaults-3.1.2/debian/py3versions.py2010-06-07
21:58:26.0 +0200
+++ python3-defaults-3.1.2/debian/py3versions.py2010-08-13
23:27:05.0 +0200
@@ -164,8 +164,8 @@
pass
def extract_pyversion_attribute(fn, pkg):
-read the debian/control file, extract the XS-Python-Version
-field; check that XB-Python-Version exists for the package.
+read the debian/control file, extract the X-Python3-Version
+field.
version = None
sversion = None
@@ -180,21 +180,16 @@
section = 'Source'
elif line.startswith('Package: ' + pkg):
section = pkg
-elif line.startswith('XS-Python-Version:'):
+elif line.startswith('X-Python3-Version:'):
if section != 'Source':
-raise ValueError('attribute XS-Python-Version not in Source
section')
+raise ValueError('attribute X-Python3-Version not in Source
section')
sversion = line.split(':', 1)[1].strip()
-elif line.startswith('XB-Python-Version:'):
-if section == pkg:
-version = line.split(':', 1)[1].strip()
if section == None:
raise ControlFileValueError('not a control file')
if pkg == 'Source':
if sversion == None:
-raise MissingVersionValueError('missing XS-Python-Version in
control file')
+raise MissingVersionValueError('missing X-Python3-Version in
control file')
return sversion
-if version == None:
-raise MissingVersionValueError('missing XB-Python-Version for package
`%s' % pkg)
return version
def requested_versions_bis(vstring, version_only=False):
@@ -239,7 +234,7 @@
help='print the supported python3 versions',
action='store_true', dest='supported')
parser.add_option('-r', '--requested',
- help='print the python3 versions requested by a build;
the argument is either the name of a control file or the value of the
XS-Python-Version attribute',
+ help='print the python3 versions requested by a build;
the argument is either the name of a control file or the value of the
X-Python3-Version attribute',
action='store_true', dest='requested')
parser.add_option('-i', '--installed',
help='print the installed supported python3 versions',
@@ -276,7 +271,7 @@
% (program, fn))
sys.exit(1)
except MissingVersionValueError:
-sys.stderr.write(%s: missing XS-Python-Version in control
file, fall back to supported versions\n \
+sys.stderr.write(%s: missing X-Python3-Version in control
file, fall back to supported versions\n \
% program)
vs = supported_versions(opts.version_only)
else:
diff -Nru python3-defaults-3.1.2/debpython/debhelper.py
python3-defaults-3.1.2/debpython/debhelper.py
--- python3-defaults-3.1.2/debpython/debhelper.py 2010-07-25
16:19:18.0 +0200
+++ python3-defaults-3.1.2/debpython/debhelper.py 2010-08-13
23:42:02.0 +0200
@@ -80,7 +80,7 @@
elif line.startswith('Source:'):
self.source_name = line[7:].strip()
elif source_section and line.startswith('X-Python3-Version:'):
-
Re: [Pkg-openldap-devel] OpenLDAP upload to unstable.
On Tue, 2010-08-17 at 09:18 +0200, Matthijs Mohlmann wrote:
On Aug 17, 2010, at 12:24 AM, Adam D. Barratt wrote:
On Mon, 2010-08-16 at 17:03 +0200, Matthijs Mohlmann wrote:
On Aug 14, 2010, at 5:13 PM, Adam D. Barratt wrote:
On Tue, 2010-08-10 at 23:44 +0200, Matthijs Möhlmann wrote:
+ # TODO: Now we are doing something that is not allowed by
policy but it
+ # has to be done.
+ sed -i -e
s|^SLAPD_CONF=.*|SLAPD_CONF=\${SLAPD_CONF}\| /etc/default/slapd
That comment immediately make me think uh oh, although I don't
currently have a better alternative to suggest that wouldn't leave
people with a broken system after the upgrade.
A broken system is worse then a policy violation in this case. A solution
to
this problem is to move the etc/default/slapd file to usr/share/slapd and
let
ucf handle this.
Would this not just replace the policy violation with giving users the
chance to break their own system by rejecting the proposed update to the
configuration? :)
That's true. I think that is something for after the release of squeeze.
Ok. Please go ahead with the upload to unstable.
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/1282071380.8293.41.ca...@kaa.jungle.aubergine.my-net-space.net
Re: please give back shogun on mipsel
On 08/17/2010 08:10 PM, Soeren Sonnenburg wrote: I also see that your package FTBFS on kfreebsd-i386 and hppa. It's killed while generating the documentation. Do you intend to fix those failures as well? Sure, but these failures are failures of doxygen 1.7.1 - not the g++ timeout compiling a too big file as is the case on mipsel. Yes, but if you want shogun to migrate, you'll have to fix those failures as well. Do you prefer a proper bug report? You could you change your packaging so that documentation is not generated on buildds. I was actually attempting this in my last upload by putting Architecture all for both doc packages and telling cdbs to only do things in build-indep: not sure why it does not work. Yes, that's a known issue with CDBS (if I'm not mistaken). csound maintainers had to deal with it (with the help of Jonas) and they ended up with something like: -build-indep: build-indep-stamp -build-indep-stamp: + +install/libcsound64-doc:: build-doxygen-stamp +build-doxygen-stamp: doxygen touch $@ 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/4c6adb10.2090...@dogguy.org
Re: Freeze exception: foomatic-filters 4.0.5
On Tue, Aug 17, 2010 at 11:13:47 +0200, Didier 'OdyX' Raboud wrote: Julien Cristau wrote: On Thu, Aug 12, 2010 at 10:27:32 +0200, Didier 'OdyX' Raboud wrote: So it is IMHO safe to allow on the Debian side too. What do you think ? Ignoring the upstream changes for a moment, I'm uncomfortable with the packaging overhaul. What does make you so uncomfortable ? A freeze is not the time to rewrite debian/rules and maintainer scripts. [...] So three solutions IMHO: i) keep foomatic-filters in lenny-style, with Chris as maintainer (basically foomatic-* MIA), no update towards Squeeze; ii) upload foomatic-filters 4.0.5-* with the dpkg-vendor thing removed but with ps_accounting default enabled; iii) upload foomatic-filters 4.0.5-* with the dpkg-vendor thing removed but _without_ the ps_accounting default change; What do you think ? I guess I'm fine with any of those. Cheers, Julien signature.asc Description: Digital signature
Freeze exception: manpages-fr
Dear release team,
I'd like to ask for a freeze exception regarding the manpages-fr package,
which produces two arch all binary packages containing manpages.
The main change of this version is the switch to a new upstream which is
taking care of the French translation of the upstream manpages. This
allows the new Debian package to focus only on the translation of the
changes introduced in the Debian manpages.
It also provide an update of the French translations.
Here are the changelog entries for this new version:
[ Denis Barbier ]
* Switch to perkamon. French translations of manpages are now managed
outside of Debian, the manpages-fr package ensures that those
translations are synced with manpages{,-dev} Debian packages.
* debian/source/format: Use 3.0 (quilt), source tarball is now
composed of 4 tarballs; the main one contains a single Makefile,
upstream perkamon is a component, and manpages and manpages-dev
Debian packages provide a component.
* debian/copyright: Updated to mention new source.
* New version: based on Debian manpages 3.25-1 and perkamon 3.25-1.
* debian/control: Remove Replaces: manpages-fr (= 2.31.1),
this version is older than the one in oldstable.
* debian/control: Add Breaks and Replaces manpages-fr-extra ( 20100723),
pthread_*.3 pages have been moved from glibc-doc into manpages-dev.
* debian/rules: File rewritten to use perkamon.
* debian/watch: Also track perkamon sources.
[ Nicolas FRANCOIS (Nekral) ]
* debian/control: Bump dependency on po4a (= 0.39)
* debian/control: Standards-Version: bumped to 3.8.4. No changes.
* debian/control: Added ${misc:Depends} to the dependencies.
The package has been prepared here:
http://alioth.debian.org/~nekral-guest/packages/manpages-fr/
The debdiff of the source package is huge because of the build system
change, but the package produces the same manpages. You can find attached
the debdiffs of the binary packages.
(These changes have been reviewed and are caused by the new upstream (i.e.
English) version (new manpages, some pages moved to different sections))
Best Regards,
--
Nekral
[The following lists of changes regard files as different if they have
different names, permissions or owners.]
Files in second .deb but not in first
-
-rw-r--r-- root/root /usr/share/man/fr/man7/iso_8859-13.7.gz
-rw-r--r-- root/root /usr/share/man/fr/man7/math_error.7.gz
-rw-r--r-- root/root /usr/share/man/fr/man7/udplite.7.gz
lrwxrwxrwx root/root /usr/share/man/fr/man7/iso-8859-10.7.gz -
iso_8859-10.7.gz
lrwxrwxrwx root/root /usr/share/man/fr/man7/iso-8859-11.7.gz -
iso_8859-11.7.gz
lrwxrwxrwx root/root /usr/share/man/fr/man7/iso-8859-13.7.gz -
iso_8859-13.7.gz
lrwxrwxrwx root/root /usr/share/man/fr/man7/iso-8859-14.7.gz -
iso_8859-14.7.gz
lrwxrwxrwx root/root /usr/share/man/fr/man7/iso-8859-15.7.gz -
iso_8859-15.7.gz
lrwxrwxrwx root/root /usr/share/man/fr/man7/iso-8859-16.7.gz -
iso_8859-16.7.gz
lrwxrwxrwx root/root /usr/share/man/fr/man7/iso-8859-2.7.gz -
iso_8859-2.7.gz
lrwxrwxrwx root/root /usr/share/man/fr/man7/iso-8859-3.7.gz -
iso_8859-3.7.gz
lrwxrwxrwx root/root /usr/share/man/fr/man7/iso-8859-4.7.gz -
iso_8859-4.7.gz
lrwxrwxrwx root/root /usr/share/man/fr/man7/iso-8859-5.7.gz -
iso_8859-5.7.gz
lrwxrwxrwx root/root /usr/share/man/fr/man7/iso-8859-6.7.gz -
iso_8859-6.7.gz
lrwxrwxrwx root/root /usr/share/man/fr/man7/iso-8859-7.7.gz -
iso_8859-7.7.gz
lrwxrwxrwx root/root /usr/share/man/fr/man7/iso-8859-8.7.gz -
iso_8859-8.7.gz
lrwxrwxrwx root/root /usr/share/man/fr/man7/iso-8859-9.7.gz -
iso_8859-9.7.gz
lrwxrwxrwx root/root /usr/share/man/fr/man7/iso_8859_10.7.gz -
iso_8859-10.7.gz
lrwxrwxrwx root/root /usr/share/man/fr/man7/iso_8859_11.7.gz -
iso_8859-11.7.gz
lrwxrwxrwx root/root /usr/share/man/fr/man7/iso_8859_13.7.gz -
iso_8859-13.7.gz
lrwxrwxrwx root/root /usr/share/man/fr/man7/iso_8859_14.7.gz -
iso_8859-14.7.gz
lrwxrwxrwx root/root /usr/share/man/fr/man7/iso_8859_15.7.gz -
iso_8859-15.7.gz
lrwxrwxrwx root/root /usr/share/man/fr/man7/iso_8859_16.7.gz -
iso_8859-16.7.gz
lrwxrwxrwx root/root /usr/share/man/fr/man7/iso_8859_2.7.gz -
iso_8859-2.7.gz
lrwxrwxrwx root/root /usr/share/man/fr/man7/iso_8859_3.7.gz -
iso_8859-3.7.gz
lrwxrwxrwx root/root /usr/share/man/fr/man7/iso_8859_4.7.gz -
iso_8859-4.7.gz
lrwxrwxrwx root/root /usr/share/man/fr/man7/iso_8859_5.7.gz -
iso_8859-5.7.gz
lrwxrwxrwx root/root /usr/share/man/fr/man7/iso_8859_6.7.gz -
iso_8859-6.7.gz
lrwxrwxrwx root/root /usr/share/man/fr/man7/iso_8859_7.7.gz -
iso_8859-7.7.gz
lrwxrwxrwx root/root /usr/share/man/fr/man7/iso_8859_8.7.gz -
iso_8859-8.7.gz
lrwxrwxrwx root/root /usr/share/man/fr/man7/iso_8859_9.7.gz -
iso_8859-9.7.gz
lrwxrwxrwx root/root /usr/share/man/fr/man7/latin10.7.gz - iso_8859-16.7.gz
lrwxrwxrwx root/root /usr/share/man/fr/man7/latin2.7.gz - iso_8859-2.7.gz
Re: Freeze exception: foomatic-filters 4.0.5
Julien Cristau wrote: On Tue, Aug 17, 2010 at 11:13:47 +0200, Didier 'OdyX' Raboud wrote: Julien Cristau wrote: On Thu, Aug 12, 2010 at 10:27:32 +0200, Didier 'OdyX' Raboud wrote: So it is IMHO safe to allow on the Debian side too. What do you think ? Ignoring the upstream changes for a moment, I'm uncomfortable with the packaging overhaul. What does make you so uncomfortable ? A freeze is not the time to rewrite debian/rules and maintainer scripts. I very much know this, but the rewrite was already done and tested (locally) before the freeze, by which I got surprised, thinking I had until late august to get this uploaded (but I'm not ranting, that's perfectly fine). Not being at the benefit of full upload rights also adds delays. So three solutions IMHO: i) keep foomatic-filters in lenny-style, with Chris as maintainer (basically foomatic-* MIA), no update towards Squeeze; ii) upload foomatic-filters 4.0.5-* with the dpkg-vendor thing removed but with ps_accounting default enabled; iii) upload foomatic-filters 4.0.5-* with the dpkg-vendor thing removed but _without_ the ps_accounting default change; What do you think ? I guess I'm fine with any of those. Okay, I'll go on with ii) and getting foomatic-filters uploaded to unstable with the dpkg-vendor thing removed. If that is needed, I'd be perfectly fine with a 10 days delay before the transition. I'll reply to this thread when the upload is done. Thanks for your time for this review ! OdyX -- 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/i4enr3$au...@dough.gmane.org
Re: Freeze exception: python3-defaults 3.1.2-6
Hi, On Tue, 2010-08-17 at 20:47 +0200, Piotr Ożarowski wrote: Please unblock python3-defaults 3.1.2-6. It fixes some important bugs related to dh_python3 and py3compile. debpython/debhelper.py appears to be continuing to fallback to XS-Python-Version if X-Python3-Version is not set. Is that intentional, given the changes to py3versions to make it ignore the older name? Also, dh_python3 has made --quiet off by default in this upload but I didn't spot this in the changelog. 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/1282073426.8293.285.ca...@kaa.jungle.aubergine.my-net-space.net
Re: Planned changes to iceweasel/iceape vs. freeze
Hi, On Mon, Aug 09, 2010 at 04:06:15PM +0200, Mike Hommey wrote: - Possibly remove the libmozillainterfaces-java package. It is apparently unused, not really maintained upstream (it's even being removed from current trunk, in favor of a separate repository if a maintainer shows up), and more importantly, not tested. On top of removing javaxpcom as mentioned above, I would like to get rid of python-xpcom as generated from xulrunner. I already have a package mostly ready for a separated python-xpcom (ITP: #591894), for which I made sure the same codebase as the one embedded in xulrunner is going to be used, and that Luke Faraone already tested with Browse.activity from the olpc stack, cf. http://lists.alioth.debian.org/pipermail/debian-olpc-devel/2010-August/002905.html Would the release team allow me to upload this new package to unstable with the intended goal to have it included in squeeze (or not, if the olpc stack is to be left out of squeeze), in place of the currently xulrunner-generated package ? Cheers, 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/20100817193141.ga31...@glandium.org
Re: Freeze exception: python-defaults 2.6.5-13
On Tue, 2010-08-17 at 20:45 +0200, Piotr Ożarowski wrote: Please unblock python-defaults 2.6.5-13. It fixes some important bugs related to dh_python2 and pycompile (+ some policy/docs changes) A few quick comments: + source package. Similarly, ttX-Python3-Version/tt is used to + specify the versions of Python 3 supported by the package. When not + specified, they defaults to all currently supported Python (or Python 3) + versions. That should be they default to. +read the debian/control file, extract the XS-Python-Version or +XS-Python-Version field; check that XB-Python-Version exists for the +package. Presumably one of those XS-Python-Versions should be X-Python-Version. [dh_python2.1] +\fB\-v\fR, \fB\-\-verbose\fR +turn verbose mode one s/one/on/ +\fB\-X\fR REGEXPR, \fB\-\-exclude\fR=\fIREGEXPR\fR +exclude items that match given REGEXPR. You may use +this optionmultiple times to build up a list of things +to exclude. s/optionmultiple/option multiple/ [pyclean.1] +\fB\-v\fR, \fB\-\-verbose\fR +turn verbose more one s/more one/mode on/ Finally, as with python3-defaults, the change of --quiet to be off by default isn't mentioned in the changelog afaics. Let me know if you'd like to correct any or all of those in a -14 upload, otherwise I'll just unblock -13. 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/1282074468.8293.416.ca...@kaa.jungle.aubergine.my-net-space.net
Re: Freeze exception: python3-defaults 3.1.2-6
[Adam D. Barratt, 2010-08-17] On Tue, 2010-08-17 at 20:47 +0200, Piotr Ożarowski wrote: Please unblock python3-defaults 3.1.2-6. It fixes some important bugs related to dh_python3 and py3compile. debpython/debhelper.py appears to be continuing to fallback to XS-Python-Version if X-Python3-Version is not set. Is that intentional, given the changes to py3versions to make it ignore the older name? yes, that was the previous behaviour and I didn't want to break existing packages Also, dh_python3 has made --quiet off by default in this upload but I didn't spot this in the changelog. actually it's *on* by default now (--verbose is set to False by default) -- Piotr Ożarowski Debian GNU/Linux Developer www.ozarowski.pl www.griffith.cc www.debian.org GPG Fingerprint: 1D2F A898 58DA AF62 1786 2DF7 AEF6 F1A2 A745 7645 -- 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/20100817193435.gf20...@piotro.eu
Re: please give back shogun on mipsel
On Tue, 2010-08-17 at 20:55 +0200, Mehdi Dogguy wrote: On 08/17/2010 08:10 PM, Soeren Sonnenburg wrote: I also see that your package FTBFS on kfreebsd-i386 and hppa. It's killed while generating the documentation. Do you intend to fix those failures as well? Sure, but these failures are failures of doxygen 1.7.1 - not the g++ timeout compiling a too big file as is the case on mipsel. Yes, but if you want shogun to migrate, you'll have to fix those failures as well. Do you prefer a proper bug report? You could you change your packaging so that documentation is not generated on buildds. I was actually attempting this in my last upload by putting Architecture all for both doc packages and telling cdbs to only do things in build-indep: not sure why it does not work. Yes, that's a known issue with CDBS (if I'm not mistaken). csound maintainers had to deal with it (with the help of Jonas) and they ended up with something like: -build-indep: build-indep-stamp -build-indep-stamp: + +install/libcsound64-doc:: build-doxygen-stamp +build-doxygen-stamp: doxygen touch $@ OK thanks, I've uploaded a new version with exactly that workaround. Nevertheless, even if shogun compiles now, python-numpy and atlas are dependencies that still need to migrate first... Regards, Soeren -- For the one fact about the future of which we can be certain is that it will be utterly fantastic. -- Arthur C. Clarke, 1962 signature.asc Description: This is a digitally signed message part
Re: Bug#506809: oolite: new upstream release (1.73)
Mehdi Dogguy writes: On 08/17/2010 06:42 PM, Yavor Doganov wrote: Ludovic Brenta wrote: Any objections, please raise your hand. We're in the begining of a GNUstep transition, which is unfortunately blocked by serious issues on hppa. As the release team is unlikely to approve a new upstream release at this point, any eventual problems in oolite must be addressed with an upload of the present version to t-p-u. So I suggest to upload this new release to experimental, not sid. (But feel free to consult with -release (CCed)). Could you send a diff please? Is the new upstream an almost complete rewrite of the sources? If the diff is big, then, yes, we would prefer to stick with the current version. 1671 files changed, 786590 insertions(+), 68558 deletions(-) I'll upload to experimental, then. My other questions re: the Uploaders field remain. -- Ludovic Brenta. -- 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/87zkwlrpzu@ludovic-brenta.org
Re: Please approve request-tracker3.8 changes
On 08/06/2010 04:53 PM, Philipp Kern wrote: On 08/06/2010 10:34 AM, Dominic Hargreaves wrote: As you can see, these are mostly documentation fixes and tidy-ups, with a feature addition which fixes an security bug (#475730). I plan to finalise work on this last issue this weekend and I'd be grateful if you could approve its transition into testing once it's been uploaded. I'd also be interested in knowing whether I should wait for another round of translation updates (#475730 includes a new Debconf template), or whether I should upload it ASAP and then upload again with further translation updates later. I would prefer two uploads. The change summary looks ok to me, however you will need to followup once it's uploaded (for putting the unblock in after looking at the diff). It would've helped if you actually did this. Anyway: unblocked now. Kind regards, Philipp Kern -- 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/4c6aeb5e.8000...@debian.org
Re: Freeze exception (python-pylibacl, python-pyxattr)?
On Tue, Aug 17, 2010 at 09:27:18AM +0200, Philipp Kern wrote: Iustin, sorry for not coming back to you earlier. Not a problem, I was on vacation :) On 08/07/2010 12:36 PM, Iustin Pop wrote: Oh, these are old conflicts from etch (IIRC) from when the python policy was to generate separate packages for each Python version, and I just changed them to Breaks according to the policy 3.9.0. I guess they can be dropped completely, but I wanted to do that only after squeeze. Did I misread the policy regarding when to use conflicts/breaks? I don't think you should change those old Conflicts to Breaks, though. The issue is not transient and there is nothing to upgrade to. I have to admit that this new policy requirement was new to me, but considering that we had some trouble ensuring proper upgrade paths when Breaks were used, Conflicts seem more appropriate to leave. I see. But FWIW we do not support skipping stable releases. So if you are certain that they were not in Lenny (and already conflicted against), then you can just drop it. Yes, Lenny has the 0.4.0 version of pyxattr, and the conflict is against 0.2.1-1.1. Similar for pylibacl. In this case, I will prepare a new upload to unstable, which removes the Replaces and Breaks entirely. I'll ping this thread again once the usual 10-day have passed and the packages would otherwise be ready for migration. thank you! iustin signature.asc Description: Digital signature
Re: Please approve request-tracker3.8 changes
On 08/17/2010 10:04 PM, Philipp Kern wrote: On 08/06/2010 04:53 PM, Philipp Kern wrote: On 08/06/2010 10:34 AM, Dominic Hargreaves wrote: As you can see, these are mostly documentation fixes and tidy-ups, with a feature addition which fixes an security bug (#475730). I plan to finalise work on this last issue this weekend and I'd be grateful if you could approve its transition into testing once it's been uploaded. I'd also be interested in knowing whether I should wait for another round of translation updates (#475730 includes a new Debconf template), or whether I should upload it ASAP and then upload again with further translation updates later. I would prefer two uploads. The change summary looks ok to me, however you will need to followup once it's uploaded (for putting the unblock in after looking at the diff). It would've helped if you actually did this. My apologies, now it popped up in my mail, despite a search being unable to find it. rtfm now unblocked, too. Cheers and sorry, Philipp Kern -- 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/4c6aebe6.9060...@debian.org
IRC Release Team Meeting on Mon, Aug 23rd, 20 UTC
Dear fellow developers, the Release Team will hold an IRC meeting at #debian-release on irc.debian.org on Monday, August 23rd, at 20 UTC. The following agenda was proposed for the meeting: 1) What will be the release architectures for squeeze? (hppa, kfreebsd-*, sparc and mips had concerns raised about their releasability.) 2) Which transitions are left for squeeze? What's their current state? 3) Release Team meeting 2-3 October in Paris: Who's going? 4) What's the state of the Release Notes? 5) Any other business? We will try to work with a soft deadline of 1h and a hard one of 1,5h. Later items on the list might be postponed to a later meeting. Kind regards, Philipp Kern on behalf of the Debian Release Team signature.asc Description: Digital signature
Re: initramfs-tools 0.98
On Tue, Aug 17, 2010 at 07:17:17PM +0100, Adam D. Barratt wrote:
On Tue, 2010-08-17 at 16:42 +0200, maximilian attems wrote:
It contains several worthwile fixes for Squeeze and
most importantly full fills the new initramfs policy.
please unblock.
A quick question on the diff:
+# Common case: /sbin/init is present
+if [ ! -x ${rootmnt}/sbin/init ]; then
+ # ... if it's not available search for valid init
+ if [ -z ${init} ] ; then
+ for inittest in /sbin/init /etc/init /bin/init /bin/sh; do
+ if validate_init ${inittest}; then
+ init=$inittest
+ break
+ fi
+ done
+ fi
+
+ # No init on rootmount
+ if ! validate_init ${init} ; then
+ panic No init found. Try passing init= bootarg.
+ fi
fi
So far as I can see, if /sbin/init is present and executable, but $init
is set to something else, then the init which will be executed is not
checked via validate_init(). If so then should the no init on
rootmount block be moved outside of the if block?
yes this is on purpose, the common case should be a single stat call
and no more overhead.
dracut doesn't validate init at all thus it never became an issue
in fedora for dracut that /sbin/init may or not be exec, see commit
e7daaf7fdf80ba63626515ca3e3e3054aaac0417 in initramfs-tools git [1]
repo for the systemd details, which got enhanced later by this fast path.
thanks.
[1] git://git.debian.org/git/kernel/initramfs-tools.git
--
maks
--
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/20100817194945.ge1...@baikonur.stro.at
Re: Freeze exception: python3-defaults 3.1.2-6
On Tue, 2010-08-17 at 21:34 +0200, Piotr Ożarowski wrote: [Adam D. Barratt, 2010-08-17] debpython/debhelper.py appears to be continuing to fallback to XS-Python-Version if X-Python3-Version is not set. Is that intentional, given the changes to py3versions to make it ignore the older name? yes, that was the previous behaviour and I didn't want to break existing packages ok Also, dh_python3 has made --quiet off by default in this upload but I didn't spot this in the changelog. actually it's *on* by default now (--verbose is set to False by default) Ah, yes. It's still not documented though :) Anyway, unblocked. 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/1282076634.8293.692.ca...@kaa.jungle.aubergine.my-net-space.net
Re: Freeze exception: roaraudio, muroard, libao
reflum, On Tue, 2010-08-17 at 13:22 +0100, Mark Brown wrote: On Mon, Aug 16, 2010 at 09:07:37PM +0200, Patrick Matth??i wrote: It is not oss-only; roaraudio just fucks up in the current code base if there is ONLY alsa available. Could you be more specific please? One of the biggest motiviations for removing OSS is to get rid of the need for the OSS compatibility bodges which cause all sorts of pain for ALSA. Patrick and I talked about this a bit more and I found a solution which makes everyone happy I hope: we remove the OSS backend completly and use the libao plugin and because of this use OSS or ALSA or whatever is selected by libao. This removes all depends on the actual soundsystem completly from the package. The package is unchanged expect a small patch updating a single line in the configuration header and one line in the Makefile. If this is ok with you we will upload by tomorrow I guess. -- Philipp. (Rah of PH2) signature.asc Description: This is a digitally signed message part
Freeze exception: eric_4.4.7-1
Hi team I would like to ask if there is a possibility to make a freeze exception for eric_4.4.7-1 which is a bug fix release since version 4.4.6. Thanks in advance Gudjon -- 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/201008172246.32185.gud...@gudjon.org
Bug#593395: unblock: adonthell-data/0.3.4.cvs.20080529+dfsg-3
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package adonthell-data. It fixes a FTBFS. unblock adonthell-data/0.3.4.cvs.20080529+dfsg-3 Cheers, Moritz -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-686 (SMP w/1 CPU core) Locale: LANG=C, lc_ctype=de_de.iso-8859...@euro (charmap=ISO-8859-15) Shell: /bin/sh linked to /bin/bash -- 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/20100817204406.9054.4975.report...@localhost.localdomain
Re: IRC Release Team Meeting on Mon, Aug 23rd, 20 UTC
On Tue, Aug 17, 2010 at 09:52:34PM +0200, Philipp Kern wrote: sparc had concerns raised about [its] releasability http://release.debian.org/squeeze/arch_qualify.html indicates the number of porters and upstream support is questionable by being yellow, but other than that there is no real explanation. It would be good if this was clarified, so that we know what you guys actually expect. -- 2. That which causes joy or happiness. -- 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/20100817211344.ga9...@entuzijast.net
Re: Freeze exception: eric_4.4.7-1
On 08/17/2010 10:46 PM, Gudjon I. Gudjonsson wrote: Hi team I would like to ask if there is a possibility to make a freeze exception for eric_4.4.7-1 which is a bug fix release since version 4.4.6. Would you mind providing a diff? 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/4c6b021b.7020...@debian.org
Freeze exception: eric_4.4.7-1 (missing debdiff added)
Hi team I would like to ask if there is a possibility to make a freeze exception for eric_4.4.7-1 which is a bug fix release since version 4.4.6. The debdiff is attached. Thanks in advance Gudjon diff -Nru eric-4.4.6/changelog eric-4.4.7/changelog --- eric-4.4.6/changelog 2010-07-04 09:59:42.0 +0200 +++ eric-4.4.7/changelog 2010-08-01 17:15:20.0 +0200 @@ -1,5 +1,9 @@ Change Log -- +Version 4.4.7: +- bug fixes +- added code to adjust the cursor flash time of the editor to the global settings + Version 4.4.6: - bug fixes diff -Nru eric-4.4.6/debian/changelog eric-4.4.7/debian/changelog --- eric-4.4.6/debian/changelog 2010-07-09 22:13:49.0 +0200 +++ eric-4.4.7/debian/changelog 2010-08-17 22:57:26.0 +0200 @@ -1,3 +1,10 @@ +eric (4.4.7-1) unstable; urgency=low + + * New upstream release + * Bump standards version to 3.9.1 + + -- Gudjon I. Gudjonsson gud...@gudjon.org Thu, 12 Aug 2010 09:48:37 +0200 + eric (4.4.6-1) unstable; urgency=low * New upstream release diff -Nru eric-4.4.6/debian/control eric-4.4.7/debian/control --- eric-4.4.6/debian/control 2010-07-09 22:13:49.0 +0200 +++ eric-4.4.7/debian/control 2010-08-17 22:57:26.0 +0200 @@ -9,7 +9,7 @@ python-sip-dev , qt4-dev-tools, libqt4-dev, python-qt4-dev #, python-kde4 XS-Python-Version: =2.5 -Standards-Version: 3.9.0 +Standards-Version: 3.9.1 Homepage: http://eric-ide.python-projects.org/ Vcs-Svn: svn://svn.debian.org/svn/python-apps/packages/eric/trunk/ Vcs-Browser: http://svn.debian.org/viewsvn/python-apps/packages/eric/trunk/ diff -Nru eric-4.4.6/debian/patches/03_disable-update-warning.patch eric-4.4.7/debian/patches/03_disable-update-warning.patch --- eric-4.4.6/debian/patches/03_disable-update-warning.patch 2010-03-29 00:17:28.0 +0200 +++ eric-4.4.7/debian/patches/03_disable-update-warning.patch 2010-08-17 22:57:25.0 +0200 @@ -1,4 +1,5 @@ Index: eric-4.4.1/eric/UI/UserInterface.py +Disables upgrade of eric outside the Debian package system === --- eric-4.4.1.orig/eric/UI/UserInterface.py 2010-03-26 20:40:23.0 +0100 +++ eric-4.4.1/eric/UI/UserInterface.py 2010-03-26 20:42:03.0 +0100 diff -Nru eric-4.4.6/eric/APIs/Python/eric4.api eric-4.4.7/eric/APIs/Python/eric4.api --- eric-4.4.6/eric/APIs/Python/eric4.api 2010-05-24 14:04:27.0 +0200 +++ eric-4.4.7/eric/APIs/Python/eric4.api 2010-08-01 12:56:13.0 +0200 @@ -4531,6 +4531,7 @@ eric4.QScintilla.Printer.Printer.formatPage?4(painter, drawing, area, pagenr) eric4.QScintilla.Printer.Printer?1(mode = QPrinter.ScreenResolution) eric4.QScintilla.QsciScintillaCompat.QSCINTILLA_VERSION?4() +eric4.QScintilla.QsciScintillaCompat.QsciScintillaCompat.UserSeparator?7 eric4.QScintilla.QsciScintillaCompat.QsciScintillaCompat.charAt?4(pos) eric4.QScintilla.QsciScintillaCompat.QsciScintillaCompat.clearAllIndicators?4(indicator) eric4.QScintilla.QsciScintillaCompat.QsciScintillaCompat.clearAlternateKeys?4() @@ -4556,10 +4557,12 @@ eric4.QScintilla.QsciScintillaCompat.QsciScintillaCompat.extendSelectionWordRight?4() eric4.QScintilla.QsciScintillaCompat.QsciScintillaCompat.findFirstTarget?4(expr_, re_, cs_, wo_, begline = -1, begindex = -1, endline = -1, endindex = -1, ws_ = False) eric4.QScintilla.QsciScintillaCompat.QsciScintillaCompat.findNextTarget?4() +eric4.QScintilla.QsciScintillaCompat.QsciScintillaCompat.focusOutEvent?4(event) eric4.QScintilla.QsciScintillaCompat.QsciScintillaCompat.foldExpandedAt?4(line) eric4.QScintilla.QsciScintillaCompat.QsciScintillaCompat.foldFlagsAt?4(line) eric4.QScintilla.QsciScintillaCompat.QsciScintillaCompat.foldHeaderAt?4(line) eric4.QScintilla.QsciScintillaCompat.QsciScintillaCompat.foldLevelAt?4(line) +eric4.QScintilla.QsciScintillaCompat.QsciScintillaCompat.getCursorFlashTime?4() eric4.QScintilla.QsciScintillaCompat.QsciScintillaCompat.getEndStyled?4() eric4.QScintilla.QsciScintillaCompat.QsciScintillaCompat.getEolIndicator?4() eric4.QScintilla.QsciScintillaCompat.QsciScintillaCompat.getFileName?4() @@ -4588,6 +4591,7 @@ eric4.QScintilla.QsciScintillaCompat.QsciScintillaCompat.replaceTarget?4(replaceStr) eric4.QScintilla.QsciScintillaCompat.QsciScintillaCompat.scrollVertical?4(lines) eric4.QScintilla.QsciScintillaCompat.QsciScintillaCompat.setCurrentIndicator?4(indicator) +eric4.QScintilla.QsciScintillaCompat.QsciScintillaCompat.setCursorFlashTime?4(time) eric4.QScintilla.QsciScintillaCompat.QsciScintillaCompat.setEolModeByEolString?4(eolStr) eric4.QScintilla.QsciScintillaCompat.QsciScintillaCompat.setIndentationGuideView?4(view) eric4.QScintilla.QsciScintillaCompat.QsciScintillaCompat.setIndicator?4(indicator, sline, sindex, eline, eindex) @@ -4595,6 +4599,7 @@ eric4.QScintilla.QsciScintillaCompat.QsciScintillaCompat.setLexer?4(lex = None) eric4.QScintilla.QsciScintillaCompat.QsciScintillaCompat.setStyleBits?4(bits)
Bug#593395: marked as done (unblock: adonthell-data/0.3.4.cvs.20080529+dfsg-3)
Your message dated Tue, 17 Aug 2010 23:47:19 +0200 with message-id 4c6b0367.60...@dogguy.org and subject line Re: Bug#593395: unblock: adonthell-data/0.3.4.cvs.20080529+dfsg-3 has caused the Debian Bug report #593395, regarding unblock: adonthell-data/0.3.4.cvs.20080529+dfsg-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.) -- 593395: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=593395 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package adonthell-data. It fixes a FTBFS. unblock adonthell-data/0.3.4.cvs.20080529+dfsg-3 Cheers, Moritz -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-686 (SMP w/1 CPU core) Locale: LANG=C, lc_ctype=de_de.iso-8859...@euro (charmap=ISO-8859-15) Shell: /bin/sh linked to /bin/bash ---End Message--- ---BeginMessage--- On 08/17/2010 10:44 PM, Moritz Muehlenhoff wrote: Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package adonthell-data. It fixes a FTBFS. Unblocked. Cheers, -- Mehdi Dogguy مهدي الدڤي http://dogguy.org/ ---End Message---
Re: Freeze exception: eric_4.4.7-1
On 08/17/2010 11:41 PM, Mehdi Dogguy wrote: Would you mind providing a diff? Oh. Your message came after I replied. Sorry! -- 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/4c6b03f2.3060...@debian.org
Bug#593406: unblock: flashrom/0.9.2+r1141-2
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: freeze-exception Please unblock package flashrom This fixes quite a number of (upstream) issues which could potentially brick a machine or at least make the BIOS flashing fail in various ways on certain hardware. Changelog below: flashrom (0.9.2+r1141-2) unstable; urgency=high * Drop alpha and netbsd-alpha from the arch list for now (builds fail). + Keeping urgency=high due to high-priority fixes in the last upload, in order to allow those fixes to migrate to testing. + It's unclear how well alpha (if at all) is supported upstream at this point. There's a compile-time #error in the upstream code breaking the build intentionally on alpha right now. Alpha support will be re-enabled as soon as this has been sorted out upstream, but it may take quite a while. -- Uwe Hermann u...@debian.org Tue, 17 Aug 2010 00:50:27 +0200 flashrom (0.9.2+r1141-1) unstable; urgency=high * New upstream release. Urgency high due to multiple critical bugfixes that could potentially brick the PC (or worse: laptop) of users. Other important fixes include: + Properly writing Atmel AT25 chips would fail on some SPI controllers. + Fix breakage with brick-potential on various non-x86 architectures. + Fix broken reads on Winbond W25x16, especially on some ICH SPI chipsets. + Fix write failure on 3COM NICs with parallel flash. + Fix byte merge related corruption on some VIA chipsets. + Fix some format string bugs. + Fix hard hang on some recent (e.g. QM57) Intel chipsets. * Install new upstream udev rules file to allow users to use flashrom without root permissions on some (USB-based) programmers. * Standards-Version: 3.9.1 (no changes required). * debian/copyright: Updates. -- Uwe Hermann u...@debian.org Sun, 15 Aug 2010 19:07:19 +0200 unblock flashrom/0.9.2+r1141-2 Thanks, Uwe. -- http://hermann-uwe.de | http://sigrok.org http://randomprojects.org | http://unmaintained-free-software.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/20100817215259.ga...@greenwood
Bug#593410: unblock: skype4py/1.0.31.0-2
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: freeze-exception Please unblock package skype4py. The new version adds missing dependency (#592490), fixes FTBFS (#592728) and a potential crash (#578327). unblock skype4py/1.0.31.0-2 -- Jakub Wilk signature.asc Description: Digital signature
Re: IRC Release Team Meeting on Mon, Aug 23rd, 20 UTC
On Tue, Aug 17, 2010 at 11:13:44PM +0200, Josip Rodin wrote: On Tue, Aug 17, 2010 at 09:52:34PM +0200, Philipp Kern wrote: sparc had concerns raised about [its] releasability http://release.debian.org/squeeze/arch_qualify.html indicates the number of porters and upstream support is questionable by being yellow, but other than that there is no real explanation. It would be good if this was clarified, so that we know what you guys actually expect. Well, for upstream support there is: at the bottom of the page. According to doko sparc32 code generation is unmaintained upstream, and he doesn't want to step up to maintain it any longer. Furthermore I found the following thread dated back to 2007: http://lists.debian.org/debian-sparc/2007/07/msg00049.html So far nobody stepped up to provide us with a working sparc64 port. I know that aurel32 did some work on zee.debian.org, but was hurt by bad RAM in that box (AFAIR). What we are currently struggling with are build failures that happen on one class of the builders, while not happening on the other, and IIRC this is happening vice-versa. Hopefully others can fill in the gaps I left here. Kind regards, Philipp Kern signature.asc Description: Digital signature
RE: IRC Release Team Meeting on Mon, Aug 23rd, 20 UTC
will try to have time to join =) Date: Tue, 17 Aug 2010 21:52:34 +0200 From: pk...@debian.org To: debian-release@lists.debian.org CC: debian-h...@lists.debian.org; debian-sp...@lists.debian.org; debian-m...@lists.debian.org; debian-...@lists.debian.org; debian-b...@lists.debian.org; debian-proj...@lists.debian.org; debian-secur...@lists.debian.org; debian-ad...@lists.debian.org Subject: IRC Release Team Meeting on Mon, Aug 23rd, 20 UTC Dear fellow developers, the Release Team will hold an IRC meeting at #debian-release on irc.debian.org on Monday, August 23rd, at 20 UTC. The following agenda was proposed for the meeting: 1) What will be the release architectures for squeeze? (hppa, kfreebsd-*, sparc and mips had concerns raised about their releasability.) 2) Which transitions are left for squeeze? What's their current state? 3) Release Team meeting 2-3 October in Paris: Who's going? 4) What's the state of the Release Notes? 5) Any other business? We will try to work with a soft deadline of 1h and a hard one of 1,5h. Later items on the list might be postponed to a later meeting. Kind regards, Philipp Kern on behalf of the Debian Release Team
Re: IRC Release Team Meeting on Mon, Aug 23rd, 20 UTC
On Wed, Aug 18, 2010 at 12:29:27AM +0200, Philipp Kern wrote: On Tue, Aug 17, 2010 at 11:13:44PM +0200, Josip Rodin wrote: On Tue, Aug 17, 2010 at 09:52:34PM +0200, Philipp Kern wrote: sparc had concerns raised about [its] releasability http://release.debian.org/squeeze/arch_qualify.html indicates the number of porters and upstream support is questionable by being yellow, but other than that there is no real explanation. It would be good if this was clarified, so that we know what you guys actually expect. Well, for upstream support there is: at the bottom of the page. According to doko sparc32 code generation is unmaintained upstream, and he doesn't want to step up to maintain it any longer. Furthermore I found the following thread dated back to 2007: http://lists.debian.org/debian-sparc/2007/07/msg00049.html So far nobody stepped up to provide us with a working sparc64 port. I know that aurel32 did some work on zee.debian.org, but was hurt by bad RAM in that box (AFAIR). This problem has been solved by disabling half of the RAM. The port is progressing with 69% of the packages built. Patches have been sent to the BTS, some of them are merged. In any case, this will clearly not be ready for squeeze, but is likely to be ready for squeeze + 1. The thing is that, despite the sparc32 toolchain being deprecated upstream, a lot of packages are not sparc64 ready. -- Aurelien Jarno GPG: 1024D/F1BCDB73 aurel...@aurel32.net http://www.aurel32.net -- 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/20100817231234.gg15...@hall.aurel32.net
Re: RFC: SQLite3 in Squeeze
Hi, Laszlo Boszormenyi g...@debian.hu writes: There's a problem with SQLite3 3.7.0 in Squeeze. The version in testing (3.6.23.1-4) was suitable to release. Next major upstream version (3.7.0) was released, which was uploaded to unstable. Then freeze happened. The latest release came with problems, like slow song change with Banshee (reported as #591298 [1]). This might also be the cause of failures in the test suite of libdbd-sqlite3-perl (#59 [0]): --8---cut here---start-8--- # Failed test at t/08_busy.t line 101. # Your testing environment might be too slow to pass this test: DBD::SQLite::db do failed: disk I/O error at t/08_busy.t line 100, READER line 1. # Failed test at t/08_busy.t line 101. # Your testing environment might be too slow to pass this test: DBD::SQLite::db do failed: disk I/O error at t/08_busy.t line 100, READER line 2. # Looks like you failed 2 tests of 23. t/08_busy.t .. # Waiting for child... (4520) # Child starting... (4521) # Child exiting... (4521) DBD::SQLite::db do failed: disk I/O error at t/28_schemachange.t line 57. # Failed test 'DROP TABLE table1' # at t/28_schemachange.t line 57. # Error: 'disk I/O error' DBD::SQLite::db do failed: disk I/O error at t/28_schemachange.t line 58. # Failed test 'CREATE TABLE table2 (id INTEGER NOT NULL, name CHAR (64) NOT NULL)' # at t/28_schemachange.t line 58. # Error: 'disk I/O error' # Looks like you failed 2 tests of 9. t/28_schemachange.t .. --8---cut here---end---8--- This still happens with sqlite3 3.7.0.1-1 as well. Regards, Ansgar [0] http://bugs.debian.org/59 -- 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/87fwycvahj@marvin.43-1.org
Bug#593410: marked as done (unblock: skype4py/1.0.31.0-2)
Your message dated Wed, 18 Aug 2010 06:42:36 +0200 with message-id 4c6b64bc.1080...@dogguy.org and subject line Re: Bug#593410: unblock: skype4py/1.0.31.0-2 has caused the Debian Bug report #593410, regarding unblock: skype4py/1.0.31.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.) -- 593410: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=593410 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: freeze-exception Please unblock package skype4py. The new version adds missing dependency (#592490), fixes FTBFS (#592728) and a potential crash (#578327). unblock skype4py/1.0.31.0-2 -- Jakub Wilk signature.asc Description: Digital signature ---End Message--- ---BeginMessage--- On 08/18/2010 12:18 AM, Jakub Wilk wrote: Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: freeze-exception Please unblock package skype4py. The new version adds missing dependency (#592490), fixes FTBFS (#592728) and a potential crash (#578327). Changing to 3.0 source format is undesired during freeze, but anyway… unblock skype4py/1.0.31.0-2 Unblocked. Regards, -- Mehdi Dogguy مهدي الدڤي http://dogguy.org/ ---End Message---
Re: Freeze for LLVM packages
On Tue, 2010-08-17 at 02:09 +0200, Arthur Loiret wrote:
2010/8/16, Adam D. Barratt a...@adam-barratt.org.uk:
On Sun, 2010-08-15 at 22:21 +0200, Arthur Loiret wrote:
2010/8/15, Adam D. Barratt a...@adam-barratt.org.uk:
On Thu, 2010-08-12 at 19:01 +0200, Arthur Loiret wrote:
- Rename the current llvm source package to llvm-2.6 and
replace binaries by versioned binaries. Thus, it is allowed to have
two versions in the archive (the 2.7 version is already versioned),
just like GCC.
My primary question is what does this gain us for Squeeze? I can see
that it could make future maintenance easier when llvm 2.8 hits the
archive, but that's not going to the case for Squeeze.
[...]
So far as I can see, the current packages are already co-installable,
albeit under the names llvm and llvm-2.7; that's not as clean as
might be preferable, but it would work.
[...]
In other words, here is what I want for squeeze:
[snip llvm-defaults explanation]
Thanks, that fits with what I'd expected.
As I said, my primary concern from a release point of view is whether
there are good reasons for doing the changes now, rather than waiting
for squeeze+1.
Very most users want to use 2.7 rather that 2.6. It would just make
their life easier by just asking them to install llvm-dev and use
unversioned binaries.
Has the current configuration confused people that you know of or is
this more of a of course people want to use the latest version by
default?
As I already said, those changes are smooth for the archive.
For unstable, most probably. For testing we're looking at adding two
new source packages and updating the {build-,}dependencies of some
others and rebuilding them; all of that carries some risk, even if it
should be small.
On a related note, the version of at least the llvm binary package would
also need to be greater than the current 2.6-9. apt won't view llvm_0.1
as requiring an upgrade from an already installed package of a higher
version.
The llvm-defaults 0.1 source package builds 2.7-1 binaries, see
debian/rules.
Ah, yes; I should have expected that when you mentioned it was based on
gcc-defaults. :-) (Having the source versioned in a way that allows the
source and binary versions to stay in sync seems more obvious imho,
but...)
This package still needs a bit of work, but not on this
side.
Ah, I'd assumed everything was basically ready to go and just waiting to
be uploaded. How much is a bit of work? One issue I did notice is
that llvm-defaults is missing a build-dependency on m4 (having tried
building it in a clean(ish) chroot).
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/1282108396.8293.4930.ca...@kaa.jungle.aubergine.my-net-space.net
Re: RM: openntpd from squeeze
On 10/08/10 21:46, Julien Cristau wrote: Please file a serious bug against it documenting why it's not releasable. I'll add a remove hint. Cheers, Julien Filed, #593429. Thanks! Greetings, Dererk -- BOFH excuse #60: system has been recalled signature.asc Description: OpenPGP digital signature
Bug#593377: marked as done (unblock: ziproxy/3.1.3-1)
Your message dated Wed, 18 Aug 2010 02:23:10 -0300 with message-id 4c6b6e3e.1030...@debian.org and subject line Re: Bug#593377: unblock: ziproxy/3.1.3-1 has caused the Debian Bug report #593377, regarding unblock: ziproxy/3.1.3-1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 593377: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=593377 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: freeze-exception Hi Release Team, Please unblock package ziproxy This upload fixes two RC bugs. The last changelog entry reads as follows: ziproxy (3.1.3-1) unstable; urgency=low . * New upstream release (LP: #569611) * debian/patches/02_ziproxy_3.1.1_speedup.diff - Removed, merged upstream. * debian/preinst - Removed, old command moved to postinst (Closes: #566589) - Thanks piuparts ;-) * debian/control - Standards-Version updated * Disabled Nameservers option (Closes: #591417) (LP: #539874) - Thanks to all in 591417@ and the upstream! - debian/README.Debian - Reason for it added. - New patch: debian/02_off_nameservers_opt.diff The diff with the current version in testing is quite huge 93 files changed, 8255 insertions(+), 2698 deletions(-) but 3.1.1-1 was granted a freeze exception and the diff [1] 3.1.1-1/3.1.3-1 is totally reasonable. [1] http://people.debian.org/~mehdi/ziproxy.diff unblock ziproxy/3.1.3-1 Regards, -- Mehdi Dogguy -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash ---End Message--- ---BeginMessage--- -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 17-08-2010 14:55, Mehdi Dogguy wrote: [...] Please unblock package ziproxy This upload fixes two RC bugs. The last changelog entry reads as follows: ziproxy (3.1.3-1) unstable; urgency=low . * New upstream release (LP: #569611) * debian/patches/02_ziproxy_3.1.1_speedup.diff - Removed, merged upstream. * debian/preinst - Removed, old command moved to postinst (Closes: #566589) - Thanks piuparts ;-) * debian/control - Standards-Version updated * Disabled Nameservers option (Closes: #591417) (LP: #539874) - Thanks to all in 591417@ and the upstream! - debian/README.Debian - Reason for it added. - New patch: debian/02_off_nameservers_opt.diff The diff with the current version in testing is quite huge 93 files changed, 8255 insertions(+), 2698 deletions(-) but 3.1.1-1 was granted a freeze exception and the diff [1] 3.1.1-1/3.1.3-1 is totally reasonable. [1] http://people.debian.org/~mehdi/ziproxy.diff unblock ziproxy/3.1.3-1 Unblocked. Kind regards, - -- Felipe Augusto van de Wiel (faw) Debian. Freedom to code. Code to freedom! -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkxrbjwACgkQCjAO0JDlykbW1gCcCqUEsbEiP1BqmCRrxIYNnVLZ dXMAoMO3Va+/z4CwnhUVKhknlMfXpPwX =Mvp4 -END PGP SIGNATURE- ---End Message---
Bug#592878: Bug#592871: libapache-dbi-perl_1.07-1+lenny1 does not actually apply the patch it contains
Hi, Adam D. Barratt a...@adam-barratt.org.uk writes: On Sat, 2010-08-14 at 00:35 +0900, Ansgar Burchardt wrote: A typo in debian/rules prevented the patches from being applied (there is QUILT_STAMPN instead of QUILT_STAMPFN). After adding the missing F the patches are applied and the fix for #568534 is really included. Release team, can we upload a fix to stable so the patch from +lenny1 gets applied? The proposed diff is attached and two present, but previously not applied patches are applied by this: the fix for #568534 and a correction of the hashbang for a perl script installed as an example. Oops. *looks for a brown paper bag for not spotting that originally* Please go ahead. Done. Regards, Ansgar -- 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/877hjov6py@marvin.43-1.org
Re: IRC Release Team Meeting on Mon, Aug 23rd, 20 UTC
On 18.08.2010 00:29, Philipp Kern wrote: On Tue, Aug 17, 2010 at 11:13:44PM +0200, Josip Rodin wrote: On Tue, Aug 17, 2010 at 09:52:34PM +0200, Philipp Kern wrote: sparc had concerns raised about [its] releasability http://release.debian.org/squeeze/arch_qualify.html indicates the number of porters and upstream support is questionable by being yellow, but other than that there is no real explanation. It would be good if this was clarified, so that we know what you guys actually expect. Well, for upstream support there is: at the bottom of the page. According to doko sparc32 code generation is unmaintained upstream, and he doesn't want to step up to maintain it any longer. I hacked the driver to default to -mcpu=v9 in 32bit mode. This seems to work okish, exposing the atomic builtins for sparc. however this requires some work/changes in packages which make hard coded assumptions about the availability of these builtins. I don't plan to work on this. most testing for the sparc toolchain upstream is done on sparc64-linux and other sparc platforms. Again, I do not intend to work on any sparc issues myself. Matthias -- 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/4c6b72ad.4040...@debian.org
Re: Freeze for LLVM packages
On 18.08.2010 07:13, Adam D. Barratt wrote: On Tue, 2010-08-17 at 02:09 +0200, Arthur Loiret wrote: 2010/8/16, Adam D. Barratta...@adam-barratt.org.uk: On Sun, 2010-08-15 at 22:21 +0200, Arthur Loiret wrote: 2010/8/15, Adam D. Barratta...@adam-barratt.org.uk: On Thu, 2010-08-12 at 19:01 +0200, Arthur Loiret wrote: - Rename the current llvm source package to llvm-2.6 and replace binaries by versioned binaries. Thus, it is allowed to have two versions in the archive (the 2.7 version is already versioned), just like GCC. My primary question is what does this gain us for Squeeze? I can see that it could make future maintenance easier when llvm 2.8 hits the archive, but that's not going to the case for Squeeze. [...] So far as I can see, the current packages are already co-installable, albeit under the names llvm and llvm-2.7; that's not as clean as might be preferable, but it would work. [...] In other words, here is what I want for squeeze: [snip llvm-defaults explanation] Thanks, that fits with what I'd expected. As I said, my primary concern from a release point of view is whether there are good reasons for doing the changes now, rather than waiting for squeeze+1. yes, get the preferred version, when installing llvm. 2.6 is a legacy version, and probably should be removed for squeeze once all packages build with 2.7. making this change now makes a possible removal of a legacy llvm-2.6 package easier. Matthias -- 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/4c6b7522.3020...@debian.org
