Bug#683367: unblock: ffgtk/0.8.1-2
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: freeze-exception Please unblock package ffgtk 0.8.1-2 which fixes an FTBFS induced by changes in libcapi20-dev upstream. I've also taken the liberty to update the watch file to make it work again despite upstream blocking straight access to directories now. Debdiff is attached for your kind review. diff --git a/debian/changelog b/debian/changelog index 047070f..0825a42 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,10 @@ +ffgtk (0.8.1-2) unstable; urgency=low + + * add patch to compile ffgtk against libcapi v3.25. Closes: #680813 + * unbreak the watch file, upstream disallows direct directory access now + + -- Rolf Leggewie f...@rolf.leggewie.biz Fri, 20 Jul 2012 14:57:12 +0800 + ffgtk (0.8.1-1) unstable; urgency=low * initial release. Closes: #602723, LP: #522644. diff --git a/debian/control b/debian/control index d3dde38..9e31ba5 100644 --- a/debian/control +++ b/debian/control @@ -4,7 +4,7 @@ Priority: extra Maintainer: Rolf Leggewie f...@rolf.leggewie.biz Uploaders: Jan-Michael Brummer jan.brum...@tabos.org Build-Depends: debhelper (= 7.0.50~), libxml2-dev, libcurl4-gnutls-dev, - libspandsp-dev, intltool, libtool, libsndfile-dev, libcapi20-dev (= 3.22), + libspandsp-dev, intltool, libtool, libsndfile-dev, libcapi20-dev (= 1:3.24), libdbus-glib-1-dev, libebook1.2-dev, libgnome-keyring-dev, libasound2-dev, libspeex-dev, libspeexdsp-dev, libpulse-dev, libnotify-dev, dh-autoreconf, libgtk-3-dev | libgtk2.0-dev diff --git a/debian/patches/build-with-i4l-v3.25.patch b/debian/patches/build-with-i4l-v3.25.patch new file mode 100644 index 000..5f8525b --- /dev/null +++ b/debian/patches/build-with-i4l-v3.25.patch @@ -0,0 +1,20 @@ +Description: build successfully against version 3.25 of isdnutils +Author: Jan-Michael Brummer +Bug-Debian: http://bugs.debian.org/680813 +Forwarded: not-needed, latest ffgtk upstream does not need this anymore +Last-Update: 2012-07-20 + +--- ffgtk-0.8.1.orig/ffgtk/faxophone/faxophone.c ffgtk-0.8.1/ffgtk/faxophone/faxophone.c +@@ -1538,7 +1538,10 @@ struct sSession *faxophoneInit( struct s + + if ( psSession == NULL ) { + if ( pnHost != NULL ) { +- setHostName( pnHost ); ++ capi20ext_set_driver( fritzbox ); ++ capi20ext_set_host( ( char * ) pnHost ); ++ capi20ext_set_port( 5031 ); ++ capi20ext_set_tracelevel( 0 ); + } + + nApplId = capiInit( nController ); diff --git a/debian/patches/series b/debian/patches/series index 26c8ab4..cba2577 100644 --- a/debian/patches/series +++ b/debian/patches/series @@ -1 +1,2 @@ po-files.patch +build-with-i4l-v3.25.patch diff --git a/debian/watch b/debian/watch index 9a83286..de64fbc 100644 --- a/debian/watch +++ b/debian/watch @@ -1,2 +1,2 @@ version=3 -http://www.tabos.org/ffgtk/download/ffgtk-(.*)\.tar\.bz2 +http://www.tabos.org/ffgtk/download.php .*/ffgtk-(.*)\.tar\.bz2
Bug#661078: britney: ignore additional packages in Sources index
Hi, Niels Thykier ni...@thykier.net writes: On 2012-02-24 01:22, Ansgar Burchardt wrote: I would like to include additional packages referenced by Built-Using in the Sources index[1] at some undefined point in the future. This might confuse britney which would need to just ignore them. Ansgar [1] http://bugs.debian.org/657212 In light of our IRC chat in #d-ftp today and the asumption that the Only-Extra-Source field will be implemented, I believe I have a trivial patch that will work[1]. There is an updated test for it in the britney2-tests[2] (the new repository announced today - not the old one). The patch is backwards compatible and could be applied before the extra sources appear in the Sources files (and without updating any of the unrelated existing tests). I remembered we don't have overrides and thus no Priority or Section fields for the extra sources. As even the current values for overrides aren't that useful (most source packages have Priority: source), I had an alternative idea: Instead of introducing a new field, use Priority: optional for regular sources and Priority: extra for the extra sources introduced by Built-Using. At least the latter would also go to Section: source. This would also fix #626394 (Priority: source in Sources). 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/87ehns8k1x@deep-thought.43-1.org
Bug#661078: britney: ignore additional packages in Sources index
On 2012-07-31 09:30, Ansgar Burchardt wrote: Hi, [...] I remembered we don't have overrides and thus no Priority or Section fields for the extra sources. As even the current values for overrides aren't that useful (most source packages have Priority: source), I had an alternative idea: Instead of introducing a new field, use Priority: optional for regular sources and Priority: extra for the extra sources introduced by Built-Using. At least the latter would also go to Section: source. This would also fix #626394 (Priority: source in Sources). Ansgar Short: Sounds good to me. AFAICT, we don't use Priority for any thing in Britney, so it won't cause a lot of issues. The only thing is that Britney does not include Priority in the control files she writes. However, I believe she is the only consumer of those control files. If we assume Priority: optional if the field is missing, this should not be an issue[1]. If you change the value of the source field, that should also be fine. I see it is written to the HeidiResult file, but I think that particular column is stripped by another of our scripts before it is passed on (I think we use that column to strip out our faux packages). ~Niels [1] The filtering would ensure that she would never write a Priority: extra source in the control files, so the assumption should be reasonable. -- 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/50179349.2020...@thykier.net
Bug#683243: unblock: keystone/2012.1.1-2
tags 683243 + moreinfo thanks On 2012-07-30 07:19, Thomas Goirand wrote: Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Dear Release Team, The new Keystone package, currently available in SID, contains reviewed Debconf templates and lots of translations, thanks to the work of Bubulle. Please unblock keystone/2012.1.1-2. Thanks in advance, Thomas Goirand (zigo) Hi, It seems like the new version introduces #683337? ~Niels -- 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/5017953f.9000...@thykier.net
Processed: Re: Bug#683243: unblock: keystone/2012.1.1-2
Processing commands for cont...@bugs.debian.org: tags 683243 + moreinfo Bug #683243 [release.debian.org] unblock: keystone/2012.1.1-2 Added tag(s) moreinfo. thanks Stopping processing here. Please contact me if you need assistance. -- 683243: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=683243 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.134372282317556.transcr...@bugs.debian.org
Bug#683299: marked as done (unblock: open-vm-tools/2:8.8.0+2012.05.21-724730-3)
Your message dated Tue, 31 Jul 2012 10:24:39 +0200 with message-id 20120731082439.gh5...@halon.org.uk and subject line Closing has caused the Debian Bug report #683299, regarding unblock: open-vm-tools/2:8.8.0+2012.05.21-724730-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.) -- 683299: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=683299 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 2:8.8.0+2012.05.21-724730-2 would have migrated in time, 2:8.8.0+2012.05.21-724730-3 fixes the FTBFS of the dkms module. -- Address:Daniel Baumann, Donnerbuehlweg 3, CH-3012 Bern Email: daniel.baum...@progress-technologies.net Internet: http://people.progress-technologies.net/~daniel.baumann/ ---End Message--- ---BeginMessage--- Maintainer refuses to justify changes. Closing. Neil -- signature.asc Description: Digital signature ---End Message---
Bug#683342: unblock: e2fsprogs/1.42.5-1
On 2012-07-31 00:39, Theodore Y. Ts'o wrote: Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package e2fsprogs This fixes a number of fairly serious bugs: * It fixes a foreign multiarch bug (#678395), and multiarch is a release goal * It fixes a bug (#682592) which could cause logsave to hang in /etc/init.d/checkroot * It fixes a bug which could cause a file system to be checked on every single boot, despite the file system appearing clean There are a number of other bugs fixed; see the changelog for more details. unblock e2fsprogs/1.42.5-1 [...] Hi, Not sure if you are aware of it, but d-i has requested us to hold all udebs for now. So it may be a while before you get a final answer on this request. Also (in answer to your other email), I believe it is fine with requesting them already now so we are aware of them. :) Anyhow, I gave it a short look and... * All debian patches appear to have been removed. By the looks they were fetched from upstream so I guess they were backports that are no longer needed? (I am asking because there is no mention of them in d/changelog as far as I can tell) * Did you intend to include tune2fs.8.in.bak e2fsck.8.in.bak? ~Niels -- 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/50179746.5090...@thykier.net
Bug#683351: marked as done (unblock: desktop-base/7.0.2)
Your message dated Tue, 31 Jul 2012 10:33:32 +0200 with message-id 5017985c.4070...@thykier.net and subject line Re: Bug#683351: unblock: desktop-base/7.0.2 has caused the Debian Bug report #683351, regarding unblock: desktop-base/7.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.) -- 683351: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=683351 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 desktop-base people seem to not like dconf. diff attached. unblock desktop-base/7.0.2 -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-1-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 -- .''`. Paul Tagliamonte paul...@debian.org : :' : Proud Debian Developer `. `'` 4096R / 8F04 9AD8 2C92 066C 7352 D28A 7B58 5B30 807C 2A87 `- http://people.debian.org/~paultag diff -Nru desktop-base-7.0.1/debian/changelog desktop-base-7.0.2/debian/changelog --- desktop-base-7.0.1/debian/changelog 2012-07-29 19:23:09.0 -0400 +++ desktop-base-7.0.2/debian/changelog 2012-07-30 19:43:22.0 -0400 @@ -1,3 +1,10 @@ +desktop-base (7.0.2) unstable; urgency=low + + * Droped the ${misc:Depends}, as Yves-Alexis pointed out, it drags in dconf +without a reason. + + -- Paul Tagliamonte paul...@debian.org Mon, 30 Jul 2012 19:43:20 -0400 + desktop-base (7.0.1) unstable; urgency=low [ Eshat Cakar ] diff -Nru desktop-base-7.0.1/debian/control desktop-base-7.0.2/debian/control --- desktop-base-7.0.1/debian/control 2012-07-14 21:18:58.0 -0400 +++ desktop-base-7.0.2/debian/control 2012-07-30 19:41:47.0 -0400 @@ -17,7 +17,7 @@ Package: desktop-base Architecture: all -Depends: ${misc:Depends}, librsvg2-common +Depends: librsvg2-common Pre-Depends: dpkg (= 1.15.7.2~) Suggests: gnome | kde-standard | xfce4 | wmaker Description: common files for the Debian Desktop signature.asc Description: Digital signature ---End Message--- ---BeginMessage--- On 2012-07-31 02:30, Paul Tagliamonte wrote: Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package desktop-base people seem to not like dconf. diff attached. unblock desktop-base/7.0.2 [...] Unblocked, thanks. ~Niels---End Message---
Bug#683142: unblock: bdii/5.2.12-1
sön 2012-07-29 klockan 12:46 +0200 skrev Niels Thykier: On 2012-07-29 06:47, Mattias Ellert wrote: Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: freeze-exception unblock bdii/5.2.12-1 Hi! The bdii package was removed from testing due to an RC bug, together with the packages that depends on it. The 5.2.12-1 update fixes the RC bug (bug #663444). I would like to request a freeze exception for this update to allow the bdii package and the packages depending on it to be part of the release. Mattias Why did you include a new upstream release in this? It makes it harder for us to review and reduces the chance for you to get the unblock? Does this upstream release have important bug fixes, if so what are they? I had been preparing an update to a new upstream release for a long time before finally making the upload. On several occasions I have completed a potential update and then looked at the BTS and thought that I should fix that RC bug before doing the upload. Since fixing the RC bug was not trivial this always ment that I held off doing the upload. I finally did fix the RC bug. The fixed package compared to the last package I prepared and did not upload was really just fixing the RC bug. The changes in the package between the previous upload and the new one are very minor. It is true that if you list the files changed the list is not short, but most of the changed files are in the debian directory. These changes are there to do the fix of the RC bug, fix some lintian warnings and update the copyright file to the new recommended format. The changes to the patches are just dropping the parts of the patches that were accepted upstream and rebasing the remaining parts. For the changes to the upstream itself, i.e. the files outside the debian directory. These are mainly changes to the default configuration to reduce the memory consumption and to add support for IPv6. --- bdii-5.2.5/debian/bdii.preinst +++ bdii-5.2.12/debian/bdii.preinst @@ -0,0 +1,16 @@ +#!/bin/sh + +set -e + +if [ $1 = upgrade ] ; then +if dpkg --compare-versions $2 lt 5.2.12 ; then +# Old versions with slapd configs listed in conffiles + if [ -w /var/lib/dpkg/info/bdii.conffiles ] ; then + sed -e /bdii-slapd.conf/d -e /bdii-top-slapd.conf/d \ + -i /var/lib/dpkg/info/bdii.conffiles + fi + rm -f /etc/bdii/bdii-slapd.conf /etc/bdii/bdii-top-slapd.conf +fi +fi + +#DEBHELPER# I think dpkg-maintscript-helper rm_conffile is what you want to be policy compliant, but I could be wrong. Yes this is probably a better idea. I was very happy when I managed to write a maintainer script that solved the RC bug. But looking at the code in the dpkg-maintscript-helper script I realize that there are corner cases that are not properly handled by by script. I haven't read the full diff, so there are possibly more issues lurking in it. In its current state, I am not inclined to grant an exception. ~Niels PS: urgency=high is no effect when the package is not in testing (in case you weren't aware of it) I was not aware. However, the package was in testing until 2 days before I did the upload. The fact the package was removed made the update very urgent - and then the urgency is ignored because it was removed Well... I don't make the rules. I can make another update using the dpkg-maintscript-helper script instead of my own not-so-great fix. If you truly do not want to take advantage of the fixes for memory usage and IPv6 support I could also upload a version where I backport the fix for the RC bug to the 5.2.5 version. But I personally think using the new version would be better. Let me know what you think is petter. Mattias signature.asc Description: This is a digitally signed message part
Re: [Pkg-ia32-libs-maintainers] Bug#679671: ia32-libs-i386: depends on removed package libdb4.8
On 2012-07-18 13:34, Goswin von Brederlow wrote: [...] There are still 2 problems remaining: lestiff2 (patch in BTS) and cyrus-sasl (needs a sourcefull upload to fix binNMU / multiarch problem). A patched version of lesstif2 appears to have been uploaded. To my knowledge it caused mtink to FTBFS, which has been fixed (see #683316). There have also been noticed issues with gromacs and cmucl, but these appear to be unrelated to the multi-arch conversion[1]. I have CC'ed Peter Samuelson, who have been conducting most of the lesstif2 rdep rebuilds. It is my understanding that lesstif2 is the last M-A conversion needed for ia32-libs. Assuming the changes to lesstif2 and mtink are reasonable, cyrus-sasl just needs a no-change upload and ia32-libs is good to go. [...] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=677762 The number of issues have gone down but not far enough yet. Most critical and trivial there is: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=650777 That one prevents ia32-libs-gtk to be installable with a dependency on libgnomecanvas and 3rd party binaries still depend on that. [...] It seems like most of those bugs are libraries needing converted to M-A (i.e. usr/lib - usr/lib/$MADIR) and #650777 is the exception. What do we lose if only the trivial bugs are fixed? By trivial I mean only patches that add Multi-Arch: $val fields like #650777 (so no moving of libraries from usr/lib to usr/lib/$MADIR). ~Niels [1] The gromacs issue appears to be #680825, which was filed before the M-A conversion. cmulc allegedly to have a broken build-arch setup; not sure if a bug has been reported for that yet. -- 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/50179f3f.3050...@thykier.net
Bug#683299: unblock: open-vm-tools/2:8.8.0+2012.05.21-724730-3
Daniel, if the git commits don't give any more detail/explanation than the changelog, then they still don't help. You know changelog entries and git commit messages can be more than just one line... On Tue, Jul 31, 2012 at 03:30:10 +0200, Daniel Baumann wrote: From 1c91cfeedd6fc2b80050b1293e59d3dc343672eb Mon Sep 17 00:00:00 2001 From: Daniel Baumann daniel.baum...@progress-technologies.net Date: Sat, 30 Jun 2012 02:45:02 +0200 Subject: [PATCH 2/9] Loading modules through kmod instead of initscript. --- debian/local/open-vm-tools.kmod |2 ++ debian/open-vm-tools.init | 10 -- debian/rules|1 + 3 files changed, 3 insertions(+), 10 deletions(-) create mode 100644 debian/local/open-vm-tools.kmod This still doesn't explain why the change is necessary, and what was wrong with the old code. And if it is, which I would be willing to believe if given some sort of explanation, it seems to be missing a package dependency on kmod. From d1dd753db76334a896b91ac312c34470448dc252 Mon Sep 17 00:00:00 2001 From: Daniel Baumann daniel.baum...@progress-technologies.net Date: Sat, 30 Jun 2012 03:43:42 +0200 Subject: [PATCH 4/9] Removing old dpkg trigger for update-initramfs. ... because? Cheers, Julien signature.asc Description: Digital signature
Re: unlock mmass*
Hello Julien, On Tue, Jul 31, 2012 at 12:11:22AM +0200, Julien Cristau wrote: On Mon, Jul 30, 2012 at 22:52:03 +0200, Filippo Rusconi wrote: How could we manage to have that new package in Debian stable ? I would not mind removing from unstable the current version so that a new upload of version 5.1.0-2 would succeed. Or upload to another place ? http://www.debian.org/doc/manuals/developers-reference/pkgs.html#t-p-u Thanks for suggesting this. I had done that procedure for a release-critical bug fix, but I was skeptical about doing it for a small improvement to the packaging of the software. Great, I'll do that, then. Cheers, Filippo -- Filippo Rusconi, PhD - public crypto key C78F687C @ pgp.mit.edu Researcher at CNRS and Debian Developer lopi...@debian.org Author of ``massXpert'' at http://www.massxpert.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/20120731091205.GA5856@licorne
Bug#683376: unblock: openttd/1.2.2-1 or openttd/1.2.1-2
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package openttd. Recently, upstream developers have discovered a security problem in most versions of OpenTTD, including the one in testing. For squeeze/stable, a fixed package has been sent to the security team this morning. For testing, I intend to get the fix in through unstable (given that the versions in testing and unstable are identical right now). I see two options here: 1. Include the next upstream version 1.2.2 in testing. I would prefer this option, because: - 1.2.2 will include a number of useful bugfixes for users. - 1.2.2 will include only bugfixes, so the risk of introducing breakage is minimal. - 1.2.2 will probably be included in Ubuntu 12.10, so including it in Debian will allow multiplayer games between Debian wheezy and Ubuntu 12.10. Note that 1.2.2 has not been released by upstream yet, it's still undergoing testing. unblock openttd/1.2.2-1 2. Backport just the security fix and upload this as 1.2.1-2. unblock openttd/1.2.1-2 If you think option 1 is acceptable, I'll prepare the packages as soon as upstream releases 1.2.2. If you would rather go for option 2, I'll start preparing packages right away. Thanks, Matthijs -- 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/20120731084720.16516.26085.report...@grubby.stderr.nl
Bug#683299: unblock: open-vm-tools/2:8.8.0+2012.05.21-724730-3
[ CCing da-manager@ to make sure they know that you still fail in maintaining your packages properly ] Hi, so yet again you managed to make a mess of open-vm-tools short time before a release. open-vm-tools is essential for a lot of people, running thousands of machines running Debian in a vmware environment - and not in a simple desktop virtualization. So I think you should finally pass the package into the hands of somebody who is willing to maintain it properly and test changes early enough to ensure they make their way into the next release. Actually I'm wondering if you even have a proper environment to test the package properly. On 07/31/2012 03:30 AM, Daniel Baumann wrote: On 07/31/2012 01:50 AM, Daniel Baumann wrote: there's nothing i can do about it except asking you to unblock said version, which i did. almost.. in addition to what the other people on the thread[0] already said.. here are the individual git commits as patches attached, constituting the complete diff between wheezy and sid. the actual diff for anything that wasn't unblocked/freeze-exempted before already, is patch 8 only (and patch 9 for the changelog entry). [0] http://lists.debian.org/debian-release/2012/07/msg01706.html To add some of my comments to your changelog: + * Switching to xz compression. Why? Is this really release critical? + * Loading modules through kmod instead of initscript. The initscript way was always ugly, but it is known to work. Why change it short before the release? I doubt its well tested enough. + * Adding sleep during restart in initscript. Why one second? Is it enough? Is there a proper way instead of sleeping? + * Removing old dpkg trigger for update-initramfs. See above. How can you be sure it was well enough tested? + * Updating GPL boilerplate in copyright file. Well, seems the copyright file was buggy, so yes, I guess this change makes sense. + * Calling dh_dkms with version argument (Closes: #677503). + [ Thijs Kinkhorst ] + * Updating dkms.conf to make modules build again, thanks to H.A.J. +Koster (Closes: #679886). These two look like the only real fixes which need to be done at this point of time before the release. Probably you should upload a package with these three changes, send excuses for your behaviour to the release team and ask them in a nice way to accept the changes. Of course you should document why they are necessary and send the patches. Like everybody else does. If you are not willing to do so, please orphan the package so somebody who has the time to maintain it and who is able to fix bugs during the freeze in a manner which would be appropriate for a Debian developer (and which is far far far away from what you are showing here). Best regards, Bernd -- Bernd ZeimetzDebian GNU/Linux Developer http://bzed.dehttp://www.debian.org GPG Fingerprint: ECA1 E3F2 8E11 2432 D485 DD95 EB36 171A 6FF9 435F -- 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/5017a04d.3040...@debian.org
Bug#683376: unblock: openttd/1.2.2-1 or openttd/1.2.1-2
tags 683376 + moreinfo thanks On 2012-07-31 10:47, Matthijs Kooijman wrote: Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package openttd. Recently, upstream developers have discovered a security problem in most versions of OpenTTD, including the one in testing. For squeeze/stable, a fixed package has been sent to the security team this morning. For testing, I intend to get the fix in through unstable (given that the versions in testing and unstable are identical right now). I see two options here: [...] If you think option 1 is acceptable, I'll prepare the packages as soon as upstream releases 1.2.2. If you would rather go for option 2, I'll start preparing packages right away. Thanks, Matthijs Hi, We cannot really make this decision without knowing what we are looking at. Please include a debdiff for each option showing the differences between the version in testing and the version that option would provide. ~Niels -- 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/5017a302.6070...@thykier.net
Processed: Re: Bug#683376: unblock: openttd/1.2.2-1 or openttd/1.2.1-2
Processing commands for cont...@bugs.debian.org: tags 683376 + moreinfo Bug #683376 [release.debian.org] unblock: openttd/1.2.2-1 or openttd/1.2.1-2 Added tag(s) moreinfo. thanks Stopping processing here. Please contact me if you need assistance. -- 683376: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=683376 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.13437263554078.transcr...@bugs.debian.org
Bug#683377: unblock: xen/4.1.3~rc1+hg-20120614.a9c0a89c08f2-5
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock xen/4.1.3~rc1+hg-20120614.a9c0a89c08f2-5. It makes it possible to do real upgrades and fixes some other problems. xen (4.1.3~rc1+hg-20120614.a9c0a89c08f2-5) unstable; urgency=low [ Ian Campbell ] * Set tap device MAC addresses to fe:ff:ff:ff:ff:ff (Closes: #671018) * Only run xendomains initscript if toolstack is xl or xm (Closes: #680528) [ Bastian Blank ] * Actually build-depend on new enough version of dpkg-dev. * Add xen-sytem-* meta-packages. We are finally in a position to do automatic upgrades and this package is missing. (closes: #681376) -- Bastian Blank wa...@debian.org Sat, 28 Jul 2012 10:23:26 +0200 unblock xen/4.1.3~rc1+hg-20120614.a9c0a89c08f2-5 -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.4-trunk-686-pae (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (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/20120731093405.28852.74259.report...@minihammer.waldi.eu.org
Re: unlock mmass*
Greetings Debian release Managers, following my previous mails about mmass [0], I would like to perform an upload of version 5.1.0-2 (currently in testing is version 5.1.0-1). The debdiff is the following: debdiff mmass_5.1.0-1.dsc mmass_5.1.0-2.dsc diff -Nru mmass-5.1.0/debian/changelog mmass-5.1.0/debian/changelog --- mmass-5.1.0/debian/changelog2012-05-24 15:09:18.0 +0200 +++ mmass-5.1.0/debian/changelog2012-07-31 11:20:18.0 +0200 @@ -1,3 +1,11 @@ +mmass (5.1.0-2) testing-proposed-updates; urgency=low + + * Fix the debian/start-script so as to pass the argument to the mmass +program. This is important because otherwise it cannot be possible to +run the mmass program with a file name to load at start. + + -- Filippo Rusconi lopi...@debian.org Mon, 30 Jul 2012 14:42:43 +0200 + mmass (5.1.0-1) unstable; urgency=low * New upstream release implementing, amongst others, a suggestion that I diff -Nru mmass-5.1.0/debian/start-script mmass-5.1.0/debian/start-script --- mmass-5.1.0/debian/start-script 2012-05-24 15:09:18.0 +0200 +++ mmass-5.1.0/debian/start-script 2012-07-31 11:20:18.0 +0200 @@ -1,5 +1,5 @@ #!/bin/sh export PYTHONPATH=/usr/lib/mmass/mspy/${PYTHONPATH:+:$PYTHONPATH} -exec python /usr/share/mmass/mmass.py +exec python /usr/share/mmass/mmass.py $@ Could you please authorize me to upload that new package to testing-proposed-updates ? Thank you for your kind attention, Cheers, Filippo [0] http://lists.debian.org/debian-release/2012/07/msg01463.html -- Filippo Rusconi, PhD - public crypto key C78F687C @ pgp.mit.edu Researcher at CNRS and Debian Developer lopi...@debian.org Author of ``massXpert'' at http://www.massxpert.org signature.asc Description: Digital signature
Bug#683376: unblock: openttd/1.2.2-1 or openttd/1.2.1-2
Hi Niels, We cannot really make this decision without knowing what we are looking at. Please include a debdiff for each option showing the differences between the version in testing and the version that option would provide. Ok, I'll do so as soon as upstream releases the 1.2.2 RC1, which should be identical or at least very similar to the final 1.2.2 release. Thanks for looking into this! Gr. Matthijs signature.asc Description: Digital signature
Bug#683315: unblock: yagf/0.9.1-3
Hi, We can't unblock something that hasn't been upload yet... Sponsor has uploaded the package. Regards, Boris -- 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/497951343728...@web27f.yandex.ru
Re: gscan2pdf freeze exception
On 29 July 2012 12:57, Niels Thykier ni...@thykier.net wrote: According to the BTS, #682818 also affects the version in testing. If so, could you please wait till 1.0.4-4 has migrated. This makes the diff much easier for me to review. Would you also unfreeze uploads which fix important bugs (I'm looking at 680158[1])? Regards Jeff [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=680158 -- 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/cacg2wbz_quec4vwd+bcn40jkjdvvgqmxxunu0gdnsur5wt+...@mail.gmail.com
Re: gscan2pdf freeze exception
On 2012-07-31 12:08, Jeffrey Ratcliffe wrote: On 29 July 2012 12:57, Niels Thykier ni...@thykier.net wrote: According to the BTS, #682818 also affects the version in testing. If so, could you please wait till 1.0.4-4 has migrated. This makes the diff much easier for me to review. Would you also unfreeze uploads which fix important bugs (I'm looking at 680158[1])? Regards Jeff [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=680158 fixes for severity: important bugs in packages of priority: optional or extra, only when this can be done via unstable; Source: http://release.debian.org/wheezy/freeze_policy.html So, in the particular case, yes. Can I ask you to file an unblock bug for that (with a debdiff)? Unblock requests on d-release@l.d.o are harder for us to keep track of. ~Niels -- 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/5017bd5c.6060...@thykier.net
Bug#683383: unblock: boxshade/3.3.1-7
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package boxshade because RC bug #683375 was fixed. Please see debdiff below to see the changes. unblock boxshade/3.3.1-7 Kind regards and thanks for your work as release team Andreas. diff -Nru boxshade-3.3.1/debian/changelog boxshade-3.3.1/debian/changelog --- boxshade-3.3.1/debian/changelog 2012-01-07 09:14:53.0 +0100 +++ boxshade-3.3.1/debian/changelog 2012-07-31 11:25:01.0 +0200 @@ -1,3 +1,11 @@ +boxshade (3.3.1-7) unstable; urgency=low + + * debian/install: Make sure boxshade executable will be installed +in the proper location +Closes: #683375 (LP: #1017188) + + -- Andreas Tille ti...@debian.org Tue, 31 Jul 2012 11:17:22 +0200 + boxshade (3.3.1-6) unstable; urgency=low [ Mathieu Malaterre ] diff -Nru boxshade-3.3.1/debian/install boxshade-3.3.1/debian/install --- boxshade-3.3.1/debian/install 2012-01-07 09:07:52.0 +0100 +++ boxshade-3.3.1/debian/install 2012-07-31 11:18:41.0 +0200 @@ -1,5 +1,5 @@ debian/bin usr -boxshade usr/lib +boxshade usr/lib/boxshade *.grp etc/boxshade *.par etc/boxshade *.sim etc/boxshade -- System Information: Debian Release: 6.0.5 Architecture: i386 (i686) Kernel: Linux 2.6.36-xenU-4814-i386 (SMP w/1 CPU core) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (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/2012073511.2288.32545.report...@mail.an3as.eu
Bug#683387: unblock: transmission/2.52-3
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package transmission Latest upload has a backported fix for a security vulnerability[0] Cheers [0] http://seclists.org/fulldisclosure/2012/Jul/348 unblock transmission/2.52-3 -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (100, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.4-trunk-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=pt_BR.UTF-8 (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/20120731115219.29864.91203.reportbug@inertia.local
Bug#683243: unblock: keystone/2012.1.1-2
On 07/31/2012 04:20 PM, Niels Thykier wrote: tags 683243 + moreinfo thanks On 2012-07-30 07:19, Thomas Goirand wrote: Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Dear Release Team, The new Keystone package, currently available in SID, contains reviewed Debconf templates and lots of translations, thanks to the work of Bubulle. Please unblock keystone/2012.1.1-2. Thanks in advance, Thomas Goirand (zigo) Hi, It seems like the new version introduces #683337? ~Niels Hi, Indeed, this needs to be fixed, we're working on it and I'll update #683337 accordingly. I don't think that this version introduces it though, I believe it was there already. Thomas -- 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/5017c8ac.8050...@debian.org
Bug#683315: marked as done (unblock: yagf/0.9.1-3)
Your message dated Tue, 31 Jul 2012 12:59:18 +0100 with message-id dc8953297b8bad895a684aa4cc883...@mail.adsl.funky-badger.org and subject line Re: Bug#683315: unblock: yagf/0.9.1-3 has caused the Debian Bug report #683315, regarding unblock: yagf/0.9.1-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.) -- 683315: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=683315 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 X-Debbugs-Cc: jac...@debian.org Please unblock package yagf Fixes not RC bug #682102 unblock yagf/0.9.1-3 diff -Nru yagf-0.9.1/debian/changelog yagf-0.9.1/debian/changelog --- yagf-0.9.1/debian/changelog 2012-06-10 15:47:59.0 +0300 +++ yagf-0.9.1/debian/changelog 2012-07-30 19:52:17.0 +0300 @@ -1,3 +1,11 @@ +yagf (0.9.1-3) unstable; urgency=low + + * debian/control was updated: +changed dependency of yagf package from cuneiform | tesseract-ocr to +tesseract-ocr | cuneiform. (Closes: #682102) + + -- Boris Pek tehnic...@mail.ru Mon, 30 Jul 2012 19:51:55 +0300 + yagf (0.9.1-2) unstable; urgency=low * debian/rules was updated: diff -Nru yagf-0.9.1/debian/control yagf-0.9.1/debian/control --- yagf-0.9.1/debian/control 2012-06-10 15:47:42.0 +0300 +++ yagf-0.9.1/debian/control 2012-07-30 19:52:17.0 +0300 @@ -12,7 +12,7 @@ Package: yagf Architecture: any Depends: ${misc:Depends}, ${shlibs:Depends}, - cuneiform | tesseract-ocr + tesseract-ocr | cuneiform Recommends: xsane Description: graphical interface for cuneiform and tesseract YAGF is a graphical interface for cuneiform and tesseract text recognition ---End Message--- ---BeginMessage--- On 31.07.2012 10:56, Boris Pek wrote: Hi, We can't unblock something that hasn't been upload yet... Sponsor has uploaded the package. Unblocked; thanks. Regards, Adam---End Message---
Bug#683383: marked as done (unblock: boxshade/3.3.1-7)
Your message dated Tue, 31 Jul 2012 13:01:13 +0100 with message-id 5ecde0164d1bff7ab8388b51f4938...@mail.adsl.funky-badger.org and subject line Re: Bug#683383: unblock: boxshade/3.3.1-7 has caused the Debian Bug report #683383, regarding unblock: boxshade/3.3.1-7 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 683383: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=683383 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 boxshade because RC bug #683375 was fixed. Please see debdiff below to see the changes. unblock boxshade/3.3.1-7 Kind regards and thanks for your work as release team Andreas. diff -Nru boxshade-3.3.1/debian/changelog boxshade-3.3.1/debian/changelog --- boxshade-3.3.1/debian/changelog 2012-01-07 09:14:53.0 +0100 +++ boxshade-3.3.1/debian/changelog 2012-07-31 11:25:01.0 +0200 @@ -1,3 +1,11 @@ +boxshade (3.3.1-7) unstable; urgency=low + + * debian/install: Make sure boxshade executable will be installed +in the proper location +Closes: #683375 (LP: #1017188) + + -- Andreas Tille ti...@debian.org Tue, 31 Jul 2012 11:17:22 +0200 + boxshade (3.3.1-6) unstable; urgency=low [ Mathieu Malaterre ] diff -Nru boxshade-3.3.1/debian/install boxshade-3.3.1/debian/install --- boxshade-3.3.1/debian/install 2012-01-07 09:07:52.0 +0100 +++ boxshade-3.3.1/debian/install 2012-07-31 11:18:41.0 +0200 @@ -1,5 +1,5 @@ debian/bin usr -boxshade usr/lib +boxshade usr/lib/boxshade *.grp etc/boxshade *.par etc/boxshade *.sim etc/boxshade -- System Information: Debian Release: 6.0.5 Architecture: i386 (i686) Kernel: Linux 2.6.36-xenU-4814-i386 (SMP w/1 CPU core) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash ---End Message--- ---BeginMessage--- On 31.07.2012 12:15, Andreas Tille wrote: Please unblock package boxshade because RC bug #683375 was fixed. Unblocked; thanks. Regards, Adam---End Message---
Advise on next steps concerning upload and unblock request
Hi, I'm one of the maintainers of the ownCloud package [1]. We have ownCloud 4.0.4 in testing and 4.0.5 (which fixes RC #681138) in unstable. Just a few minutes ago upstream released 4.0.6 with fixes to some security issues (besides other fixes). Shall I ask for unblock of 4.0.5 and a few days later for 4.0.6? Or can we agree to got for 4.0.6 right away. I think we have to go for 4.0.6 as I'll classify the security issues as RC. Please find the upstream changelog here: http://owncloud.org/releases/Changelog Upstream diff v4.0.4..v4.0.5: https://gitorious.org/owncloud/owncloud/commit/d163fe02cd05c30a223c757b138acd8a35f898f3/diffs/10bf36a6ae022f54797d12ab756ad78e4a9ffe5a Upstream diff v4.0.5..v4.0.6: https://gitorious.org/owncloud/owncloud/commit/10bf36a6ae022f54797d12ab756ad78e4a9ffe5a/diffs/aa60771736b230d82d472a3443f262f7158842ad Thanks a lot and take care, Thomas [1] - http://packages.qa.debian.org/o/owncloud.html -- 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/1343734065.5017c13176...@office.tmit.eu
Bug#683387: marked as done (unblock: transmission/2.52-3)
Your message dated Tue, 31 Jul 2012 13:03:18 +0100 with message-id ae033b99c4589824720c50f227da6...@mail.adsl.funky-badger.org and subject line Re: Bug#683387: unblock: transmission/2.52-3 has caused the Debian Bug report #683387, regarding unblock: transmission/2.52-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.) -- 683387: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=683387 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 transmission Latest upload has a backported fix for a security vulnerability[0] Cheers [0] http://seclists.org/fulldisclosure/2012/Jul/348 unblock transmission/2.52-3 -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (100, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.4-trunk-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash ---End Message--- ---BeginMessage--- On 31.07.2012 12:52, Leo 'costela' Antunes wrote: Please unblock package transmission Latest upload has a backported fix for a security vulnerability[0] Unblocked; thanks. Regards, Adam---End Message---
Re: debdiff for automake1.7_1.7.9-9.1+squeeze1
On 31.07.2012 04:40, Eric Dorland wrote: Proposed stable update for automake1.7. Please go ahead; thanks. Regards, Adam -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/3f4e18fa00e6e0ac612be71262cc7...@mail.adsl.funky-badger.org
Re: debdiff for automake1.9_1.9.6+nogfdl-3.1+squeeze1
On 31.07.2012 04:12, Eric Dorland wrote: * Adam D. Barratt (a...@adam-barratt.org.uk) wrote: On Sun, 2012-07-29 at 23:24 -0400, Eric Dorland wrote: Proposed stable update for automake1.9. This looks like the patches that are already in stable? +automake1.9 (1.9.6+nogfdl-3.1) unstable; urgency=high Err whoops, attached the wrong diff. Here's the right one. Thanks. Please go ahead. 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/2d9847362cc29eefc7595b912a215...@mail.adsl.funky-badger.org
Bug#683392: unblock: nvidia-graphics-drivers-legacy-96xx/96.43.20-6
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package nvidia-graphics-drivers-legacy-96xx Only translation and documentation updates. debdiff --diffstat ...-5.dsc ...-6.dsc | filterdiff -x '*.po*' attached. unblock nvidia-graphics-drivers-legacy-96xx/96.43.20-6 -- System Information: Debian Release: wheezy/sid APT prefers stable APT policy: (800, 'stable'), (700, 'testing'), (600, 'unstable'), (500, 'stable-updates'), (130, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=C, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash diffstat for nvidia-graphics-drivers-legacy-96xx-96.43.20 nvidia-graphics-drivers-legacy-96xx-96.43.20 NEWS| 19 ++- changelog | 29 ++--- control | 39 +-- control.models |5 +- po/cs.po| 52 ++ po/da.po| 53 +++ po/de.po| 60 +++ po/fr.po| 61 po/it.po| 52 ++ po/pl.po| 58 ++ po/ru.po| 55 po/sk.po| 52 ++ po/sv.po| 54 +++ po/templates.pot| 45 ++ rules |2 - xserver-xorg-video-nvidia.templates | 18 +- 16 files changed, 612 insertions(+), 42 deletions(-) diff -Nru nvidia-graphics-drivers-legacy-96xx-96.43.20/debian/NEWS nvidia-graphics-drivers-legacy-96xx-96.43.20/debian/NEWS --- nvidia-graphics-drivers-legacy-96xx-96.43.20/debian/NEWS 2012-06-30 12:13:40.0 +0200 +++ nvidia-graphics-drivers-legacy-96xx-96.43.20/debian/NEWS 2012-07-12 08:15:15.0 +0200 @@ -1,13 +1,16 @@ nvidia-graphics-drivers-legacy-96xx (96.43.20-5) unstable; urgency=low - The NVIDIA legacy 96xx driver has not been updated to support the current - Xserver and is therefore no longer usable. For graphics adapters that are - not supported by a newer nvidia driver generation the only possibility is to - use the nouveau driver. + Nvidia Corporation has not updated the legacy 96xx driver to support + current X servers, so this driver is no longer usable. For graphics + adapters that are not supported by a newer Nvidia driver generation, + the best option is to use the free Nouveau driver. - In order to switch to the nouveau driver, please uninstall all nvidia - driver packages and *purge* (just removing is insufficient) the - nvidia-kernel-common package. Also remove all nvidia specific configuration - from /etc/X11/xorg.conf (and xorg.conf.d/). + To switch to the Nouveau driver, please uninstall all Nvidia driver + packages, remove all Nvidia-specific configuration from + /etc/X11/xorg.conf (and xorg.conf.d/), and *purge* the + nvidia-kernel-common package - just removing it is insufficient. + + The Nouveau driver (xserver-xorg-video-nouveau) should work without + needing any specific xorg.conf settings. -- Andreas Beckmann deb...@abeckmann.de Thu, 28 Jun 2012 16:36:17 +0200 diff -Nru nvidia-graphics-drivers-legacy-96xx-96.43.20/debian/changelog nvidia-graphics-drivers-legacy-96xx-96.43.20/debian/changelog --- nvidia-graphics-drivers-legacy-96xx-96.43.20/debian/changelog 2012-06-30 13:11:06.0 +0200 +++ nvidia-graphics-drivers-legacy-96xx-96.43.20/debian/changelog 2012-07-31 13:15:41.0 +0200 @@ -1,14 +1,33 @@ +nvidia-graphics-drivers-legacy-96xx (96.43.20-6) unstable; urgency=low + + [ Andreas Beckmann ] + * Debconf template reviewed by debian-l10n-english@. + * Update NEWS and long descriptions accordingly. + + [ Debconf translations ] + * Czech (cs): Michal Simunek (Closes: #683066) + * Danish (da): Joe Hansen (Closes: #682382) + * French (fr): Julien Patriarca (Closes: #682499) + * German (de): Martin Eberhard Schauer(Closes: #682855) + * Italian (it): Dario Santamaria (Closes: #683118) + * Polish (pl): Michał Kułach (Closes: #682325) + * Russian (ru): Yuri Kozlov (Closes: #682130) + * Slovak (sk): Ivan Masár (Closes: #682009) + * Swedish (sv): Martin Bagge (Closes: #682568) + + -- Andreas Beckmann deb...@abeckmann.de Tue, 31 Jul 2012 13:15:41 +0200 + nvidia-graphics-drivers-legacy-96xx (96.43.20-5) unstable; urgency=low - * Turn into transitional packages. The 96xx legacy driver has
Bug#683299: unblock: open-vm-tools/2:8.8.0+2012.05.21-724730-3
On 07/31/2012 11:07 AM, Bernd Zeimetz wrote: so yet again you managed to make a mess of open-vm-tools short time before a release. i didn't. please read the whole thread carefully, thank you. + * Switching to xz compression. Why? smaller package size. Is this really release critical? this is part of the -2 upload before the freeze (as everything else except the last dkms ftbfs fix), it's a regular maintainer upload. + * Loading modules through kmod instead of initscript. The initscript way was always ugly, but it is known to work. Why change it short before the release? because it's better and less error prone. I doubt its well tested enough. it is. + * Adding sleep during restart in initscript. Why one second? because it sometimes fails to restart if there's no sleep. Is it enough? yes. Is there a proper way instead of sleeping? to the best of my knowledge, this is the proper way these days on how do deal with these sort of things in sysvinit initscripts. + * Removing old dpkg trigger for update-initramfs. See above. How can you be sure it was well enough tested? dpkg dropped support for update-initramfs triggers in debian/*triggers, the trigger file therefore is entirely useless. you need to call update-initramfs in postinst manually, like the package already does since a long time. -- Address:Daniel Baumann, Donnerbuehlweg 3, CH-3012 Bern Email: daniel.baum...@progress-technologies.net Internet: http://people.progress-technologies.net/~daniel.baumann/ -- 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/5017d0c3.4060...@progress-technologies.net
Bug#683299: unblock: open-vm-tools/2:8.8.0+2012.05.21-724730-3
On 07/31/2012 02:34 PM, Daniel Baumann wrote: On 07/31/2012 11:07 AM, Bernd Zeimetz wrote: so yet again you managed to make a mess of open-vm-tools short time before a release. i didn't. please read the whole thread carefully, thank you. Yes you did, as several people tried to explain to you already. But I'm not going to bother myself with that anymore, assuming that you will manage to do an upload according to the rules of the release team asap. -- Bernd ZeimetzDebian GNU/Linux Developer http://bzed.dehttp://www.debian.org GPG Fingerprint: ECA1 E3F2 8E11 2432 D485 DD95 EB36 171A 6FF9 435F -- 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/5017d4db.9070...@debian.org
Bug#683400: freeze-exception for live-debconfig
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: freeze-exception On 07/31/2012 02:51 PM, Luca Falavigna wrote: I checked with Release Team, and they prefer to have written communication for upload approvals, so they asked if you could send a request to debian-release@lists.d.o anyway. done hereby (not sure if opening a freeze-exception bug is that accurate for this sort of request, but i didn't found anything more suitable, and bts is preferable over plain mails on the list). live-debconfig contains the stand-alone parts from live-config that's needed for 'build-time' configuration of systems, including live systems and lxc systems. it was split out from live-config due to popular demand, see ftp-masters thread for the history why it was in src:live-config in the first place rather than it's own src package (beginning of june). live-debconfig however is in NEW now since some days, and i need to know if ftp-masters will process the package so that it can go to unstable first, and eventually and if RM agrees, go to wheezy. if not, i will need to stuff the contend back into src:live-config. ftp-masters however say, that they need RM consent to even let it to unstable first (which actually confuses me a bit, since other completely new packages, e.g. crtools, were processed just fine and are now in unstable). at debconf, luk said that he agrees to have the package in unstable first, and then go from there and see, if it can go to wheezy at a later point (which is ok, since we'll need a few translation/documentation-update uploads of that package anyway before we consider asking for an unblock). so.. does the release-team allow ftp-master to process that package? unrelated to that, but similar: we'll intend to upload another new package, live-examples, that will carry the configuration trees for live-build for the official debian-live images for wheezy (see e.g. http://live.debian.net/gitweb/?p=config-gnome-desktop.git). do you need/want a seperate request for that too in order to allow ftp-masters to process the package (in advance, or afterwards?), or should i just upload the package normally? -- Address:Daniel Baumann, Donnerbuehlweg 3, CH-3012 Bern Email: daniel.baum...@progress-technologies.net Internet: http://people.progress-technologies.net/~daniel.baumann/ -- 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/5017d9b5.90...@progress-technologies.net
Bug#683299: unblock: open-vm-tools/2:8.8.0+2012.05.21-724730-3
On 07/31/2012 10:59 AM, Julien Cristau wrote: This still doesn't explain why the change is necessary, and what was wrong with the old code. And if it is, which I would be willing to believe if given some sort of explanation, it seems to be missing a package dependency on kmod. for the 'why' part i've think i covered in my response to Bernd a few minutes ago, if you need more, feel free to ask. regarding the kmod depends.. kmod is like linux kernel packages, there should be no depends against it as it will otherwise mean that kmod (which is quasi-essential, it's being pulled in during debootstrap) would be hard-enforced upon chroots and lxc systems, where you don't or can't use kernel modules anyway (within the chroot/container). having said that, kmod should be in recommends. do you want me to upload that right now already, or would you prefere waiting until (if at all) open-vm-tools migrate? -- Address:Daniel Baumann, Donnerbuehlweg 3, CH-3012 Bern Email: daniel.baum...@progress-technologies.net Internet: http://people.progress-technologies.net/~daniel.baumann/ -- 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/5017df94.6020...@progress-technologies.net
Bug#683299: unblock: open-vm-tools/2:8.8.0+2012.05.21-724730-3
On Tue, Jul 31, 2012 at 14:34:11 +0200, Daniel Baumann wrote: + * Adding sleep during restart in initscript. Why one second? because it sometimes fails to restart if there's no sleep. Is it enough? yes. Based on what? If the system is under load, what guarantees that it won't take more time? Is there a proper way instead of sleeping? to the best of my knowledge, this is the proper way these days on how do deal with these sort of things in sysvinit initscripts. Nope. The proper way is for stop to not return until it's actually stopped. Cheers, Julien signature.asc Description: Digital signature
Bug#683299: unblock: open-vm-tools/2:8.8.0+2012.05.21-724730-3
On Tue, Jul 31, 2012 at 14:34:11 +0200, Daniel Baumann wrote: + * Switching to xz compression. Why? smaller package size. Which is particularly important for this package because...? And using the -9 option (which is recommended against by the xz documentation) because...? Cheers, Julien signature.asc Description: Digital signature
Bug#683299: unblock: open-vm-tools/2:8.8.0+2012.05.21-724730-3
On 07/31/2012 03:40 PM, Julien Cristau wrote: Based on what? tests on my computer. If the system is under load, what guarantees that it won't take more time? as often there are no guarantees, but i tested it under quite some cpu and IO load, and it worked for me. regarding testing migration.. even if it wouldn't help in 100% of all cases, it's better to have it safer in most cases, the current testing package does not have a sleep at all. Nope. The proper way is for stop to not return until it's actually stopped. it does that. but again, it's safer in some cases to have the sleep, just to be on the safe side. -- Address:Daniel Baumann, Donnerbuehlweg 3, CH-3012 Bern Email: daniel.baum...@progress-technologies.net Internet: http://people.progress-technologies.net/~daniel.baumann/ -- 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/5017e18c.1030...@progress-technologies.net
Bug#683299: unblock: open-vm-tools/2:8.8.0+2012.05.21-724730-3
On 07/31/2012 03:41 PM, Julien Cristau wrote: Which is particularly important for this package because...? And using the -9 option (which is recommended against by the xz documentation) because...? i'm definitely not going to re-iterate what all the people said about using xz compression, feel free to watch the debconf talk and look at the various threads on the debian mailinglists should you require more information why and how it's beneficial to use xz in debian. -- Address:Daniel Baumann, Donnerbuehlweg 3, CH-3012 Bern Email: daniel.baum...@progress-technologies.net Internet: http://people.progress-technologies.net/~daniel.baumann/ -- 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/5017e1fe.3060...@progress-technologies.net
Bug#683334: unblock: libcrypt-ssleay-perl/0.58-2 (pre-approval request)
On Mon, Jul 30, 2012 at 10:47:49PM +0200, Salvatore Bonaccorso wrote: Note, I just first would like to get a pre-approval, if the change is okay to be passed to wheezy. Attached is the debdiff against 0.58-1 currently in wheezy and unstable. ACK. Kind regards Philipp Kern signature.asc Description: Digital signature
Bug#683342: unblock: e2fsprogs/1.42.5-1
On Tue, Jul 31, 2012 at 10:28:54AM +0200, Niels Thykier wrote: Also (in answer to your other email), I believe it is fine with requesting them already now so we are aware of them. :) Since udeb's have been held, I guess this point is moot in any case. :-) Just for the record, none of these changes should be user visible from a d-i perspective, although of course any change has testing impliciations. Anyhow, I gave it a short look and... * All debian patches appear to have been removed. By the looks they were fetched from upstream so I guess they were backports that are no longer needed? (I am asking because there is no mention of them in d/changelog as far as I can tell) Well, technically speaking they came from upstream first (e2fsprogs gets developed with an upstream-first policy), and then I pull them into debian/patches when I make interim releases of the debian package between upstream releases. So yes, all of these commits are reflected upstream. (Each of the debian patches references the upstream commit id's for easier tracking, BTW.) * Did you intend to include tune2fs.8.in.bak e2fsck.8.in.bak? Argh, no, I didn't. Thanks for pointing that out. Unfortunately, it's in the upstream release tarball which has already been published and GPG signed, so it's too late to fix this now. My script for generating the release tarball needs some tweaking so that these files (left over from a patch application) get filtered out automatically. I have a .gitignore entry which is why I didn't notice them, sigh. - Ted -- 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/20120731164010.gb32...@thunk.org
Bug#682482: unblock: glpi/0.83.31-1
On Mon, Jul 30, 2012 at 02:49:50PM +0200, Niels Thykier wrote: On 2012-07-23 10:56, Pierre Chifflier wrote: Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Hi, GLPI 0.83.31 (micro-fix based on 0.83.3) is an important security release, fixing two CVEs: CVE-2012-4002: Bug #3704: CSRF prevention step 1 Bug #3707: CSRF prevention step 2 CVE-2012-4003: Bug #3705: Security XSS for few items https://forge.indepnet.net/projects/glpi/versions/771 Note: the diff from 0.83.2-1 (current testing) is pretty big, but almost all the patch is made of fixes in many files. Trying to backport would make no sense imho since it would bring almost everything, and make future maintenance even harder. Please allow GLPI 0.83.31 in testing. Regards, Pierre unblock glpi/0.83.31-1 Hi, I am afraid that diff is too much for me to review. I have tried a couple of times now and there is lot in there I expect is unrelated changes. I understand that due to #3707, the security fix only will still be a huge diff. That said, it is not the Html::closeForm() (i.e. CSRF step 2) that I choke on. So I would be would be interested in seening the diff with only the security fixes. ~Niels Hi, I agree that the diff is pretty big, and that splitting only the security fixes is hard (and would make maintenance almost impossible). I used a few commands to extract a trimmed version of the patch: git df upstream/0.83.2..upstream/0.83.31 glpi_0.83.31_raw.diff cat glpi_0.83.31_raw.diff | filterdiff -x '*locales*' -x '*htmlawed*' \ -x '*glpi-0.83.1-empty.sql*' -x '*update*' glpi_0.83.31_filtered.diff to exclude the changes related to locales and similar. I did not attach the patch to this mail, it is still 200kB. The stripped diff still makes 5300 lines out of the ~9000 original. It also appears that it does not only include calls to Html::closeForm() but also checks on HTTP_REFERRER (and exemption on some pages with DO_NOT_CHECK_HTTP_REFERER), and addition of CURRENTCSRFTOKEN. I know that there are rules for the freeze, but I do not feel many choices here: - keep a vulnerable version for wheezy. Not good. I may try to maintain something in -backports, but that would still mean having a vulnerable version by default. - try to backport only the security corrections in the current version in testing. Honestly, I do not think I will be able to do that, so if this is decided I will ask for some help. Additionally, since the submission of this ticket, version 0.83.4 was released with some new fixes (not tagged as security, but #3800 also concerns HTTP_REFERER for ex.). Regards, Pierre -- 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/20120731180808.gf14...@mail.wzdftpd.net
Bug#683334: unblock: libcrypt-ssleay-perl/0.58-2 (pre-approval request)
Hi Philipp On Tue, Jul 31, 2012 at 05:15:10PM +0200, Philipp Kern wrote: On Mon, Jul 30, 2012 at 10:47:49PM +0200, Salvatore Bonaccorso wrote: Note, I just first would like to get a pre-approval, if the change is okay to be passed to wheezy. Attached is the debdiff against 0.58-1 currently in wheezy and unstable. ACK. Great, many thanks! I would like to delay the upload to unstable just a bit, to first answer to a concern raised in #622917 in message 41[1] by Jakub Wilk. I would like to first have a look at this, before uploading to unstable. [1]: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=622917#41 Will try to do so later in the evening. Kind regards Salvatore signature.asc Description: Digital signature
Bug#683392: unblock: nvidia-graphics-drivers-legacy-96xx/96.43.20-6
On Tue, 2012-07-31 at 14:25 +0200, Andreas Beckmann wrote: Please unblock package nvidia-graphics-drivers-legacy-96xx Only translation and documentation updates. I debated grumbling about the changes to -5's existing changelog, but I guess the meaning hasn't changed. This change to debian/rules doesn't appear to have been mentioned in the changelog: override_dh_makeshlibs: - dh_makeshlibs -Xvdpau/libvdpau_nvidia.so -Xtls/libnvidia-tls.so -- -c0 + DPKG_GENSYMBOLS_CHECK_LEVEL=0 dh_makeshlibs -Xvdpau/libvdpau_nvidia.so -Xtls/libnvidia-tls.so -- -c0 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/1343759589.1551.3.ca...@jacala.jungle.funky-badger.org
Re: [Pkg-ia32-libs-maintainers] Bug#679671: ia32-libs-i386: depends on removed package libdb4.8
On Tue, Jul 31, 2012 at 11:02:55AM +0200, Niels Thykier wrote: A patched version of lesstif2 appears to have been uploaded. To my knowledge it caused mtink to FTBFS, which has been fixed (see #683316). There have also been noticed issues with gromacs and cmucl, but these appear to be unrelated to the multi-arch conversion[1]. [...] [1] The gromacs issue appears to be #680825, which was filed before the M-A conversion. Yes, it is. gromacs builds correctly with the multiarch lesstif2 as long as cmake is downgraded to 2.8.8-3, which avoids #680825/#681428. That bug is waiting on a new cmake upload -- would it be acceptable to the RT to remove gromacs from testing, allowing lesstif2 to migrate, and then re-admitting a binNMU'ed gromacs after cmake is updated? Assuming the lesstif and (as-yet-unavailable) cmake migrations themselves are allowed, of course. -- Nicholas Breen nbr...@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/20120731185914.gj9...@ofb.net
Re: [Pkg-ia32-libs-maintainers] Bug#679671: ia32-libs-i386: depends on removed package libdb4.8
[Nicholas Breen] That bug is waiting on a new cmake upload -- would it be acceptable to the RT to remove gromacs from testing, allowing lesstif2 to migrate, and then re-admitting a binNMU'ed gromacs after cmake is updated? Assuming the lesstif and (as-yet-unavailable) cmake migrations themselves are allowed, of course. There is no need to remove gromacs in order for lesstif2 to migrate. There's no SONAME bump or anything. The issue only came up at all, because we needed to make sure the new lesstif2 does not add any new FTBFS in other packages. Peter -- 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/20120731194557.ge4...@p12n.org
Bug#683436: unblock: aroarfw/0.1~beta4-5
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package aroarfw This update only removes Philipp from the maintainer list, as he had already requested. unblock aroarfw/0.1~beta4-5 -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-3-amd64 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (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/20120731200229.4289.50091.report...@srv1.linux-dev.org
Bug#683437: unblock: ckport/0.1~rc0-3
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package ckport This update only removes Philipp from the maintainers list, as he had already requested, to do so. unblock ckport/0.1~rc0-3 -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-3-amd64 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (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/20120731200338.4350.77832.report...@srv1.linux-dev.org
Bug#683440: unblock: muroard/0.1.10-2
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package muroard This update removes Philipp - as requested - as maintainer. unblock muroard/0.1.10-2 -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-3-amd64 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (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/20120731200633.4464.60338.report...@srv1.linux-dev.org
Bug#683439: unblock: muroar/0.1.8-2
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package muroar It removes - as requested - Philipp as maintainer and also adds an important upstream patch (01-env-home-validation) to add validation of $HOME. unblock muroar/0.1.8-2 -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-3-amd64 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (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/20120731200534.4400.19671.report...@srv1.linux-dev.org
Bug#683441: unblock: otrs2/3.1.7+dfsg1-3
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package otrs2 I have added an upstream patch to fix the postmaster module with IMAPTLS mailboxes: * Add backported upstream patch 27-imaptls-more-than-one-email. Using IMAPTLS will purge all e-mails, if more than one is located in the inbox. This is because of newer Mail::IMAPClient module versions return an array reference insteaf of an array on the -message action. unblock otrs2/3.1.7+dfsg1-3 -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-3-amd64 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (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/20120731200809.4519.4688.report...@srv1.linux-dev.org
Bug#683436: marked as done (unblock: aroarfw/0.1~beta4-5)
Your message dated Tue, 31 Jul 2012 21:07:05 +0100 with message-id 1343765225.1551.4.ca...@jacala.jungle.funky-badger.org and subject line Re: Bug#683436: unblock: aroarfw/0.1~beta4-5 has caused the Debian Bug report #683436, regarding unblock: aroarfw/0.1~beta4-5 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 683436: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=683436 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 aroarfw This update only removes Philipp from the maintainer list, as he had already requested. unblock aroarfw/0.1~beta4-5 -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-3-amd64 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash ---End Message--- ---BeginMessage--- On Tue, 2012-07-31 at 22:02 +0200, Patrick Matthäi wrote: Please unblock package aroarfw This update only removes Philipp from the maintainer list, as he had already requested. Unblocked. Regards, Adam---End Message---
Bug#683442: unblock: fglrx-driver/1:12-6+point-1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package fglrx-driver As already discussed in: http://lists.debian.org/debian-release/2012/07/msg01145.html fglrx-driver could be unblocked now. AMD just released a point release for Debian to fix the open issues. unblock fglrx-driver/1:12-6+point-1 -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-3-amd64 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (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/20120731201254.4585.91024.report...@srv1.linux-dev.org
Bug#683437: marked as done (unblock: ckport/0.1~rc0-3)
Your message dated Tue, 31 Jul 2012 21:12:02 +0100 with message-id 1343765522.1551.6.ca...@jacala.jungle.funky-badger.org and subject line Re: Bug#683437: unblock: ckport/0.1~rc0-3 has caused the Debian Bug report #683437, regarding unblock: ckport/0.1~rc0-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.) -- 683437: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=683437 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 ckport This update only removes Philipp from the maintainers list, as he had already requested, to do so. unblock ckport/0.1~rc0-3 -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-3-amd64 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash ---End Message--- ---BeginMessage--- On Tue, 2012-07-31 at 22:03 +0200, Patrick Matthäi wrote: Please unblock package ckport This update only removes Philipp from the maintainers list, as he had already requested, to do so. Unblocked. Regards, Adam---End Message---
Bug#683440: marked as done (unblock: muroard/0.1.10-2)
Your message dated Tue, 31 Jul 2012 21:11:16 +0100 with message-id 1343765476.1551.5.ca...@jacala.jungle.funky-badger.org and subject line Re: Bug#683440: unblock: muroard/0.1.10-2 has caused the Debian Bug report #683440, regarding unblock: muroard/0.1.10-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.) -- 683440: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=683440 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 muroard This update removes Philipp - as requested - as maintainer. unblock muroard/0.1.10-2 -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-3-amd64 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash ---End Message--- ---BeginMessage--- On Tue, 2012-07-31 at 22:06 +0200, Patrick Matthäi wrote: Please unblock package muroard This update removes Philipp - as requested - as maintainer. Unblocked. Regards, Adam---End Message---
Bug#683392: unblock: nvidia-graphics-drivers-legacy-96xx/96.43.20-6
On 2012-07-31 20:33, Adam D. Barratt wrote: override_dh_makeshlibs: - dh_makeshlibs -Xvdpau/libvdpau_nvidia.so -Xtls/libnvidia-tls.so -- -c0 + DPKG_GENSYMBOLS_CHECK_LEVEL=0 dh_makeshlibs -Xvdpau/libvdpau_nvidia.so -Xtls/libnvidia-tls.so -- -c0 Most packages are empty transitionals now after commenting out the files in .install, but I didn't delete the .symbols - and -c0 wasn't enough to silence dh_makeshlibs w.r.t. missing symbols (because my .pbuilderrc sets DPKG_GENSYMBOLS_CHECK_LEVEL=4). Andreas -- 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/50183bb3.3070...@abeckmann.de
Bug#683445: Consider including GMSH into Wheezy
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please, consider including GMSH into Wheezy. GMSH is a mesh generator, which is used for preparation of meshes for different simulation and modelling tasks. Unfortunately it is affected by a license issue because of opencascade license GPL-incompatibility #617931, like some other packages, which are still in Wheezy. But the license question has a chance to be some day resolved. It will be pity, if the next stable release will loose such important for scientists and engineers package. Thanks. Anton -- 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/CALF6qJnj6OO1ctDZUvPaR9_vVmHXbY0FfQW6+q=nzuxta8h...@mail.gmail.com
Bug#683446: unblock: libqt4pas/2.5-7
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: freeze-exception Please unblock package libqt4pas Rev7 only contains adjustments on the package's symbols file to build on more (now all) architectures. It does not introduce any new issue and is therefore safe to accept for Wheezy. unblock libqt4pas/2.5-7 -- System Information: Debian Release: wheezy/sid Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.5.0-6-generic (SMP w/2 CPU cores) -- 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/20120731204535.31672.16873.reportbug@sirius
Bug#683446: unblock: libqt4pas/2.5-7
On Tue, 2012-07-31 at 22:45 +0200, Matthias Klumpp wrote: Please unblock package libqt4pas Rev7 only contains adjustments on the package's symbols file to build on more (now all) architectures. From a scan of the diff, all of the changes appear to be hurd-i386 related? Given that wheezy won't include any packages on that architecture, such changes aren't suitable for an unblock. It does not introduce any new issue and is therefore safe to accept for Wheezy. Non-sequitur. The freeze policy doesn't consist of does not introduce any new issue. 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/1343768563.1551.10.ca...@jacala.jungle.funky-badger.org
Re: debdiff for automake1.10_1.10.3-1+squeeze1
On Mon, 2012-07-30 at 19:00 +0100, Adam D. Barratt wrote: On Sun, 2012-07-29 at 22:24 -0400, Eric Dorland wrote: Proposed stable update for automake1.10. +automake1.10 (1:1.10.3-1+squeeze1) stable; urgency=low + + * lib/am/distdir.am: Backport fix for CVE-2012-3386 Temporary worldwide +write permissions during make distcheck. (Closes: #681117) + + -- Eric Dorland e...@debian.org Sun, 29 Jul 2012 21:22:49 -0400 Please go ahead; thanks. For the record, this was uploaded and I've just flagged it for acceptance in to p-u. 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/1343768894.1551.11.ca...@jacala.jungle.funky-badger.org
Bug#683446: marked as done (unblock: libqt4pas/2.5-7)
Your message dated Tue, 31 Jul 2012 23:08:15 +0200 with message-id caknhny8gw4qm1oyj0umuowmy07co22lfxjamkj9tvhq5wvm...@mail.gmail.com and subject line Re: Bug#683446: unblock: libqt4pas/2.5-7 has caused the Debian Bug report #683446, regarding unblock: libqt4pas/2.5-7 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 683446: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=683446 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 libqt4pas Rev7 only contains adjustments on the package's symbols file to build on more (now all) architectures. It does not introduce any new issue and is therefore safe to accept for Wheezy. unblock libqt4pas/2.5-7 -- System Information: Debian Release: wheezy/sid Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.5.0-6-generic (SMP w/2 CPU cores) ---End Message--- ---BeginMessage--- Hi! Okay, if Hurd is not important, we can close this report as invalid. (I don't care about Hurd also, but probably others did) Sorry for the noise! Regards, Matthias 2012/7/31 Adam D. Barratt a...@adam-barratt.org.uk: On Tue, 2012-07-31 at 22:45 +0200, Matthias Klumpp wrote: Please unblock package libqt4pas Rev7 only contains adjustments on the package's symbols file to build on more (now all) architectures. From a scan of the diff, all of the changes appear to be hurd-i386 related? Given that wheezy won't include any packages on that architecture, such changes aren't suitable for an unblock. It does not introduce any new issue and is therefore safe to accept for Wheezy. Non-sequitur. The freeze policy doesn't consist of does not introduce any new issue. Regards, Adam ---End Message---
NEW changes in proposedupdates
Processing changes file: automake1.10_1.10.3-1+squeeze1_amd64.changes ACCEPT Processing changes file: bind9_9.7.3.dfsg-1~squeeze6_amd64.changes ACCEPT Processing changes file: bind9_9.7.3.dfsg-1~squeeze6_armel.changes ACCEPT Processing changes file: bind9_9.7.3.dfsg-1~squeeze6_i386.changes ACCEPT Processing changes file: bind9_9.7.3.dfsg-1~squeeze6_ia64.changes ACCEPT Processing changes file: bind9_9.7.3.dfsg-1~squeeze6_kfreebsd-amd64.changes ACCEPT Processing changes file: bind9_9.7.3.dfsg-1~squeeze6_kfreebsd-i386.changes ACCEPT Processing changes file: bind9_9.7.3.dfsg-1~squeeze6_mips.changes ACCEPT Processing changes file: bind9_9.7.3.dfsg-1~squeeze6_mipsel.changes ACCEPT Processing changes file: bind9_9.7.3.dfsg-1~squeeze6_powerpc.changes ACCEPT Processing changes file: bind9_9.7.3.dfsg-1~squeeze6_s390.changes ACCEPT Processing changes file: bind9_9.7.3.dfsg-1~squeeze6_sparc.changes ACCEPT -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1swjop-0004h0...@franck.debian.org
Processed: block 682906 with 683053
Processing commands for cont...@bugs.debian.org: block 682906 with 683053 Bug #682906 [release.debian.org] unblock: python-defaults/2.7.3-2 682906 was not blocked by any bugs. 682906 was not blocking any bugs. Added blocking bug(s) of 682906: 683053 thanks Stopping processing here. Please contact me if you need assistance. -- 682906: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=682906 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.13437708687942.transcr...@bugs.debian.org
Bug#683452: unblock: phpunit-selenium/1.2.6-3
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Dear release team, I ask for a freeze exception for phpunit-selenium/1.2.6-3 This upload introduces a README.Debian file with vital information for using this set of classes. The attached file was produced using debdiff phpunit-selenium_1.2.6-2.dsc phpunit-selenium_1.2.6-3.dsc phpunit-selenium_1.2.6-2:1.2.6-3.diff Thanks -- Luis Uribe http://eviled.org diff -Nru phpunit-selenium-1.2.6/debian/changelog phpunit-selenium-1.2.6/debian/changelog --- phpunit-selenium-1.2.6/debian/changelog 2012-05-31 00:25:31.0 -0500 +++ phpunit-selenium-1.2.6/debian/changelog 2012-07-31 15:00:26.0 -0500 @@ -1,3 +1,12 @@ +phpunit-selenium (1.2.6-3) unstable; urgency=low + + * debian/README.Debian +Adding file + * debian/control +Adding DM-Upload-Allowed + + -- Luis Uribe a...@eviled.org Tue, 31 Jul 2012 14:44:17 -0500 + phpunit-selenium (1.2.6-2) unstable; urgency=low * Replaces: phpunit ( 3.6) and Depends: phpunit (= 3.6) (Closes: #675275). diff -Nru phpunit-selenium-1.2.6/debian/control phpunit-selenium-1.2.6/debian/control --- phpunit-selenium-1.2.6/debian/control 2012-05-31 00:25:31.0 -0500 +++ phpunit-selenium-1.2.6/debian/control 2012-07-31 15:00:26.0 -0500 @@ -7,6 +7,7 @@ Build-Depends-Indep: php-pear Standards-Version: 3.9.3 Homepage: https://github.com/sebastianbergmann/phpunit-selenium +DM-Upload-Allowed: yes Vcs-Git: git://git.debian.org/pkg-php/phpunit-selenium.git Vcs-Browser: http://git.debian.org/?p=pkg-php/phpunit-selenium.git diff -Nru phpunit-selenium-1.2.6/debian/README.Debian phpunit-selenium-1.2.6/debian/README.Debian --- phpunit-selenium-1.2.6/debian/README.Debian 1969-12-31 19:00:00.0 -0500 +++ phpunit-selenium-1.2.6/debian/README.Debian 2012-07-31 15:00:26.0 -0500 @@ -0,0 +1,35 @@ +In order to run test that uses phpunit-selenium you need to download the +Selenium Server from http://seleniumhq.org/download/ (the actual supported +version of the server is 2.23) and start it with: + + java -jar selenium-server-standalone-X.XX.X.jar + +The Selenium Server receives Selenium commands from your tests and +interprets them, and reports back the results of running those tests. + +An example phpunit test: +?php +require_once 'PHPUnit/Extensions/SeleniumTestCase.php'; + +class Example extends PHPUnit_Extensions_SeleniumTestCase +{ + function setUp() + { +$this-setBrowser(*firefox); +$this-setBrowserUrl(http://www.debian.org/;); + } + + function testMyTestCase() + { +$this-open(/); +$this-assertTrue($this-isTextPresent(debian)); + } +} +? + +For this test to run, you have to install iceweasel and make a link +from /usr/bin/firefox to /usr/bin/iceweasel (You may want to save a +copy of the script originally installed in /usr/bin/firefox) + +You can find documentation about how to write tests at +http://seleniumhq.org/docs/05_selenium_rc.html \ No newline at end of file signature.asc Description: Digital signature
Bug#683453: unblock: mirror/2.9-62
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package mirror Trivial bugfix to add a missing dependency. Debdiff attached. unblock mirror/2.9-62 -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-3-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash diff -Nru mirror-2.9/debian/changelog mirror-2.9/debian/changelog --- mirror-2.9/debian/changelog 2012-05-15 13:15:21.0 + +++ mirror-2.9/debian/changelog 2012-07-31 21:42:12.0 + @@ -1,3 +1,9 @@ +mirror (2.9-62) unstable; urgency=low + + * *Really* add the libperl4-corelibs-perl dependency. Closes: #683448. + + -- Steve McIntyre 93...@debian.org Tue, 31 Jul 2012 22:42:02 +0100 + mirror (2.9-61) unstable; urgency=low * Add Depends on libperl4-corelibs-perl. Closes: #667893. Thanks to diff -Nru mirror-2.9/debian/control mirror-2.9/debian/control --- mirror-2.9/debian/control 2012-01-23 19:57:47.0 + +++ mirror-2.9/debian/control 2012-07-31 21:41:16.0 + @@ -8,7 +8,7 @@ Package: mirror Architecture: all -Depends: ${perl:Depends}, netbase, patch, ${misc:Depends} +Depends: ${perl:Depends}, netbase, patch, ${misc:Depends}, libperl4-corelibs-perl Recommends: mailx, fping Suggests: at, cron Description: keeps FTP archives up-to-date
Bug#683453: marked as done (unblock: mirror/2.9-62)
Your message dated Tue, 31 Jul 2012 22:53:09 +0100 with message-id 1343771589.1551.13.ca...@jacala.jungle.funky-badger.org and subject line Re: Bug#683453: unblock: mirror/2.9-62 has caused the Debian Bug report #683453, regarding unblock: mirror/2.9-62 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.) -- 683453: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=683453 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 mirror Trivial bugfix to add a missing dependency. Debdiff attached. unblock mirror/2.9-62 -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-3-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash diff -Nru mirror-2.9/debian/changelog mirror-2.9/debian/changelog --- mirror-2.9/debian/changelog 2012-05-15 13:15:21.0 + +++ mirror-2.9/debian/changelog 2012-07-31 21:42:12.0 + @@ -1,3 +1,9 @@ +mirror (2.9-62) unstable; urgency=low + + * *Really* add the libperl4-corelibs-perl dependency. Closes: #683448. + + -- Steve McIntyre 93...@debian.org Tue, 31 Jul 2012 22:42:02 +0100 + mirror (2.9-61) unstable; urgency=low * Add Depends on libperl4-corelibs-perl. Closes: #667893. Thanks to diff -Nru mirror-2.9/debian/control mirror-2.9/debian/control --- mirror-2.9/debian/control 2012-01-23 19:57:47.0 + +++ mirror-2.9/debian/control 2012-07-31 21:41:16.0 + @@ -8,7 +8,7 @@ Package: mirror Architecture: all -Depends: ${perl:Depends}, netbase, patch, ${misc:Depends} +Depends: ${perl:Depends}, netbase, patch, ${misc:Depends}, libperl4-corelibs-perl Recommends: mailx, fping Suggests: at, cron Description: keeps FTP archives up-to-date ---End Message--- ---BeginMessage--- On Tue, 2012-07-31 at 22:46 +0100, Steve McIntyre wrote: Please unblock package mirror Trivial bugfix to add a missing dependency. Debdiff attached. Unblocked; thanks. Regards, Adam---End Message---
Bug#683299: unblock: open-vm-tools/2:8.8.0+2012.05.21-724730-3
On Tue, Jul 31, 2012 at 03:47:42PM +0200, Daniel Baumann wrote: On 07/31/2012 03:41 PM, Julien Cristau wrote: Which is particularly important for this package because...? And using the -9 option (which is recommended against by the xz documentation) because...? i'm definitely not going to re-iterate what all the people said about using xz compression, feel free to watch the debconf talk and look at the various threads on the debian mailinglists should you require more information why and how it's beneficial to use xz in debian. To quote the manual page: | For example, decompressing a file created with xz -9 currently requires | 65 MiB of memory. I don't think that's agreed upon. If anything default options should be used. But then Julien did ask you the question why it's needed and you avoided it. That makes a useful discussion pretty hard. Kind regards Philipp Kern signature.asc Description: Digital signature
Bug#683299: unblock: open-vm-tools/2:8.8.0+2012.05.21-724730-3
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 07/31/2012 03:45 PM, Daniel Baumann wrote: On 07/31/2012 03:40 PM, Julien Cristau wrote: Based on what? tests on my computer. As it was already explained to you before the release of Squeeze, this is far far far away from proper testing for a package like open-vm-tools. It should be tested on current (and maybe even older) ESX instalations. Ballooning, live-migrations, snapshots with quiesce option and all the other nice features need to work before it should be released as stable. If the system is under load, what guarantees that it won't take more time? as often there are no guarantees, but i tested it under quite some cpu and IO load, and it worked for me. regarding testing migration.. even if it wouldn't help in 100% of all cases, it's better to have it safer in most cases, the current testing package does not have a sleep at all. Why not add a proper way to handle it instead of a broken workaround? Nope. The proper way is for stop to not return until it's actually stopped. it does that. but again, it's safer in some cases to have the sleep, just to be on the safe side. So you've patched your kill(1) to block until the process is gone? Luckily this patch did not make it into Debian. - -- Bernd ZeimetzDebian GNU/Linux Developer http://bzed.dehttp://www.debian.org GPG Fingerprint: ECA1 E3F2 8E11 2432 D485 DD95 EB36 171A 6FF9 435F -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBCAAGBQJQGG1fAAoJEOs2Fxpv+UNfhi8P/29kD5WcWIOHC4375Ob9I5ZR BAvC5mOnjnrvRgZRn5lFS5QH0Qs7+VCW7dGBwpgOV8+ZXvP653u4B/ska99Ut5GR gqgc7d7s5T1U71XDuTQvMGzbb7uVYEntYmKVfOyYsTDobeUMTO33BX4JqDU9OxMr JtYNutHuSCR8KlNBYYkr8Xvh3+ZU8Z/iZsuTNtYb9cw/G0yy2RYRb+b3uQpf+Jw2 NP/HbLzpPZAkmbPUnIUiTQ+gTcYe6JV1pjugnhy4VDHuin/O3+LlSOLutz3WT7gz sIGyWohbk9SFgQHAgiedLum43miRb5e8/sew8y44A8o8kBRCEElSNLnVMYHwshCx WDedWe/+7hDb8mUBOyf5tmegE8cT9LtR7q8bl4WESIiDDSDPY7s6TqEZcNkzkVc4 CV7TqWXRofELeF/znMOVcFnvgAT/f4C2rojRrGGwihYvbIt6du+K7yejWqFShhCt rbJgK3TV7CuvRGnDE4NOvKGCCLr9OaG4T/xev9PT7BhBsELYgDUkRNS6Vv2gJxZI 0tOs5BzWkZgUP82dPrIEdoZR1M8tshY2BmMnrQkrnZenTZbFh7JOLyPB1lcT7Xvh G56gvUnzC15WCLrp8RE+nup7vIgUBN9ddXkntdajhPgdygBrOXF5+qJrcDmQEm4b v2WGFCJah/2rCBWfm0GK =J106 -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/50186d66.8040...@debian.org
Bug#682736: unblock: vmware-manager/0.2.0-2
On Sat, 28 Jul 2012 15:15:49 +0100, Adam D. Barratt writes: On Wed, 2012-07-25 at 18:27 +1000, Alexander Zangerl wrote: Please unblock package vmware-manager the version in unstable fixes rc bug #680481, which is a file name conflict between the packages vmm and vmware-manager: both provide a program named vmm, and the man page is causing the clash. the fix consists of vmware-manager switching to use /usr/bin/vwm (note: w). Are vwm and vmm supposed to be identical, other than the name change? The version of vmm shipped in -2 appears to include new changes which are then not carried over in to vmw: no, that's not the case but seems a problem invented by debdiff: the package is git-hosted and -built and for some weird reason debdiff hands out all kinds of weird deltas here... attached you'll find a diff -ub between files from the binary packages: vmm from the 0.2.0-1 and the renamed 0.2.0-2 vwm, which shows that apart from renaming vmm into vwm in the POD sections nothing has been changed. regards az --- alt/usr/bin/vmm 2012-05-14 13:00:05.0 +1000 +++ neu/usr/bin/vwm 2012-07-08 19:42:57.0 +1000 @@ -2,32 +2,32 @@ # POD {{{ =head1 NAME -vmm - Manage VMware virtual machines +vwm - Manage VMware virtual machines =head1 SYNOPSIS - vmm command [options] + vwm command [options] =over =item BGlobal syntax: - vmm command [-f] [-v+] [-w seconds] [@profile] + vwm command [-f] [-v+] [-w seconds] [@profile] =item BCommand specific syntax: - vmm clone [-o pool] [-c count] [-a datastore...] [-l folder] source vm new vm name - vmm deploy [synonym of 'clone'] - vmm df [-h] [datastore...] - vmm host [maintenance|restore|restart|shutdown|disconnect|reconnect] hosts... - vmm list [-d col1,col2... | perl string] [-t title] [vm|datastore|host|pool|template][s] [patterns...] - vmm migrate [-p low|normal|high] [-o pool] vms... host - vmm move [-o pool] vms... datastore - vmm setpool low|normal|high cpu|mem|all pools... - vmm show [vm|datastore|host|pool] [items...] - vmm snapshot [-t title] vms... - vmm state on|off|suspend|reboot|shutdown|restart|standby vms... - vmm version + vwm clone [-o pool] [-c count] [-a datastore...] [-l folder] source vm new vm name + vwm deploy [synonym of 'clone'] + vwm df [-h] [datastore...] + vwm host [maintenance|restore|restart|shutdown|disconnect|reconnect] hosts... + vwm list [-d col1,col2... | perl string] [-t title] [vm|datastore|host|pool|template][s] [patterns...] + vwm migrate [-p low|normal|high] [-o pool] vms... host + vwm move [-o pool] vms... datastore + vwm setpool low|normal|high cpu|mem|all pools... + vwm show [vm|datastore|host|pool] [items...] + vwm snapshot [-t title] vms... + vwm state on|off|suspend|reboot|shutdown|restart|standby vms... + vwm version =back @@ -108,7 +108,7 @@ =item Bversion Display various version informaiton about the connected vServer and local API. -This command is the default if no actual command is specified (i.e. just running 'vmm' with nothing else specified). +This command is the default if no actual command is specified (i.e. just running 'vwm' with nothing else specified). =back @@ -134,16 +134,16 @@ Specifies which profile to use when addressing the vServer. This can be an entry within the config file or the URL (with optional login details) e.g. - vmm version @cluster1 - vmm version @cluster2 - vmm version @https://cluster1.acme.edu - vmm version @https://usern...@cluster1.acme.edu - vmm version @https://username:passw...@cluster1.acme.edu + vwm version @cluster1 + vwm version @cluster2 + vwm version @https://cluster1.acme.edu + vwm version @https://usern...@cluster1.acme.edu + vwm version @https://username:passw...@cluster1.acme.edu Examples 1 and two assume 'custer1' and 'customer2' have been defined in the examples file (see EXAMPLES). The further examples specify the connection information on the command line. Specifying the password from the command line is exceptionally silly and should be avoided. -If username and/or password is omitted (such as in examples 3 and 4 above) they will be prompted for when vmm is run. +If username and/or password is omitted (such as in examples 3 and 4 above) they will be prompted for when vwm is run. =item B-c @@ -228,8 +228,8 @@ =back Force continue if an error occurs. -Normaly if an error occurs vmm will stop processing any operations specified on the command line. -If this flag is enabled vmm will continue operation as if no error occured. +Normaly if an error occurs vwm will stop processing any operations specified on the command line. +If this flag is enabled vwm will continue operation as if no error occured. =item B--human @@ -268,7 +268,7 @@ =back Dry run mode. -When enabled vmm will continue as normal but no actual call to the VMware VServer is made. +When enabled vwm will continue as normal but no actual call to the VMware VServer is made. =item B--folder @@ -414,69 +414,69 @@ =over -=item Bvmm
Re: Freeze exception for texlive-extra 2012.20120611-2
Dear release managers, now that texlive-extra 2012.20120611-2 is accepted into unstable and there the second day, I ask once more for freeze exception: On Mo, 30 Jul 2012, Norbert Preining wrote: Dear Release managers, I would like to ask for a freeze exception for texlive-extra 2012.20120611-2 The only change made in this release is a fix for a incorrect info file, that when run through (g)install-info, under certain circumstances (that is not clear by now) creates garbeld UTF8 output in the /usr/share/info/dir file. The short term solution is fixing the problematic info file, and this is what this upload does. It adds another patch under debian/patches that fixes the info file, plus adds a line in the debian/patches/series file plus a change log entry. That is all. The first bug report on strange dir files is #555620 Ian Zimmerman tracked it down to broken info files, and submitted two bug reports, one against texlive-font-utils shipping the problematic info file #683201, and one against texinfo that (g)install-info should be more robust wrt to errors #683204. Obviously the second one cannot be fixed so easily and quickly, so I decided to at least make sure that in the currently available packges the info/dir file is not created with garbled content. I attach the full debdiff to this email. There are other changes that creeped into the debdiff, due to our packaging of the texlive-{base,extra,doc,lang} package in the same repository, but they only related to other packages and are not evaluated (changes in tpm2deb.cfg), plus a call to dh_lintian in rules. Thanks a lot Norbert Norbert Preiningpreining@{jaist.ac.jp, logic.at, debian.org} JAIST, Japan TeX Live Debian Developer DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094 SCRONKEY (n.) Something that hits the window as a result of a violent sneeze. --- Douglas Adams, The Meaning of Liff diff -Nru texlive-extra-2012.20120611/debian/changelog texlive-extra-2012.20120611/debian/changelog --- texlive-extra-2012.20120611/debian/changelog 2012-06-11 12:02:00.0 +0900 +++ texlive-extra-2012.20120611/debian/changelog 2012-07-30 11:09:18.0 +0900 @@ -1,3 +1,10 @@ +texlive-extra (2012.20120611-2) unstable; urgency=low + + * fix broken mf2pt1 info file that triggered broken info/dir file +under certain circumstances (Closes: #683201) + + -- Norbert Preining prein...@debian.org Mon, 30 Jul 2012 11:08:33 +0900 + texlive-extra (2012.20120611-1) unstable; urgency=low * new upstream checkout (TL2012 release) diff -Nru texlive-extra-2012.20120611/debian/patches/fix-mf2pt1-info texlive-extra-2012.20120611/debian/patches/fix-mf2pt1-info --- texlive-extra-2012.20120611/debian/patches/fix-mf2pt1-info 1970-01-01 09:00:00.0 +0900 +++ texlive-extra-2012.20120611/debian/patches/fix-mf2pt1-info 2012-07-30 11:06:59.0 +0900 @@ -0,0 +1,17 @@ +--- + texmf/doc/info/mf2pt1.info |2 +- + 1 file changed, 1 insertion(+), 1 deletion(-) + +Index: texlive-extra-2012.20120611/texmf/doc/info/mf2pt1.info +=== +--- texlive-extra-2012.20120611.orig/texmf/doc/info/mf2pt1.info 2012-04-01 08:11:11.0 +0900 texlive-extra-2012.20120611/texmf/doc/info/mf2pt1.info 2012-07-30 11:06:28.760202853 +0900 +@@ -2,7 +2,7 @@ + + INFO-DIR-SECTION TeX + START-INFO-DIR-ENTRY +-* mf2pt1:: Produce PostScript Type 1 fonts from Metafont source ++* mf2pt1: (mf2pt1). Produce PostScript Type 1 fonts from Metafont source + END-INFO-DIR-ENTRY + +*mf2pt1*: Produce PostScript Type 1 fonts from Metafont source diff -Nru texlive-extra-2012.20120611/debian/patches/series texlive-extra-2012.20120611/debian/patches/series --- texlive-extra-2012.20120611/debian/patches/series 2012-05-21 09:29:59.0 +0900 +++ texlive-extra-2012.20120611/debian/patches/series 2012-07-30 11:06:59.0 +0900 @@ -1 +1,2 @@ fix-scripts +fix-mf2pt1-info diff -Nru texlive-extra-2012.20120611/debian/rules texlive-extra-2012.20120611/debian/rules --- texlive-extra-2012.20120611/debian/rules 2012-06-11 12:29:38.0 +0900 +++ texlive-extra-2012.20120611/debian/rules 2012-07-30 11:14:00.0 +0900 @@ -1,7 +1,7 @@ #!/usr/bin/make -f # # debian/rules file for texlive-extra -# $Id: rules.in 5480 2012-05-16 01:30:56Z preining $ +# $Id: rules.in 5626 2012-07-29 14:17:10Z preining $ PACKAGES=texlive-bibtex-extra texlive-extra-utils texlive-font-utils texlive-formats-extra texlive-generic-extra texlive-math-extra texlive-plain-extra texlive-latex-extra texlive-fonts-extra texlive-music texlive-games
Bug#683472: unblock: xen-api/1.3.2-10
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package xen-api The current version in Wheezy suffers from a wrong default PAM setting of PAM, giving access to XAPI to any account on th server, as per: http://lists.xen.org/archives/html/xen-api/2012-07/msg00059.html Relevant diff: http://anonscm.debian.org/gitweb/?p=pkg-xen/xen-api.git;a=commitdiff;h=c75c43b2fd6ab55113023e6f9b6510f5cdd3573e So, please unblock xen-api/1.3.2-10 ASAP. Cheers, Thomas -- 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/20120801021906.12107.82020.report...@buzig.gplhost.com
Bug#683299: unblock: open-vm-tools/2:8.8.0+2012.05.21-724730-3
On 08/01/2012 12:29 AM, Philipp Kern wrote: I don't think that's agreed upon. If anything default options should be used. i don't think so, see debconf bofh. the bottom line is that -9 compresses better than -6, and that -9 is not a problem on amd64 and i386, see debconf talk for more information. open-vm-tools are only built on amd64 and i386 anyway, architectures which are both considered to be 'fast' architectures. -- Address:Daniel Baumann, Donnerbuehlweg 3, CH-3012 Bern Email: daniel.baum...@progress-technologies.net Internet: http://people.progress-technologies.net/~daniel.baumann/ -- 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/50189901.7020...@progress-technologies.net
Bug#683299: unblock: open-vm-tools/2:8.8.0+2012.05.21-724730-3
On 08/01/2012 01:42 AM, Bernd Zeimetz wrote: tests on my computer. As it was already explained to you before the release of Squeeze, this is far far far away from proper testing for a package like open-vm-tools. It should be tested on current (and maybe even older) ESX instalations. Ballooning, live-migrations, snapshots with quiesce option and all the other nice features need to work before it should be released as stable. i don't see the connection to adding a 'sleep 1' for safety, anyhow.. regarding testing migration.. even if it wouldn't help in 100% of all cases, it's better to have it safer in most cases, the current testing package does not have a sleep at all. Why not add a proper way to handle it instead of a broken workaround? ..please do share your knowledge of the proper way then and help making debian better (bug report plus patch would be appreciated). -- Address:Daniel Baumann, Donnerbuehlweg 3, CH-3012 Bern Email: daniel.baum...@progress-technologies.net Internet: http://people.progress-technologies.net/~daniel.baumann/ -- 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/50189a46.3050...@progress-technologies.net
Bug#682736: unblock: vmware-manager/0.2.0-2
On Wed, 2012-08-01 at 09:55 +1000, Alexander Zangerl wrote: On Sat, 28 Jul 2012 15:15:49 +0100, Adam D. Barratt writes: Are vwm and vmm supposed to be identical, other than the name change? The version of vmm shipped in -2 appears to include new changes which are then not carried over in to vmw: no, that's not the case but seems a problem invented by debdiff: the package is git-hosted and -built and for some weird reason debdiff hands out all kinds of weird deltas here... debdiff is displaying it because it's what's in the source package: adsb@franck:~$ dpkg-source -x ftp/pool/contrib/v/vmware-manager/vmware-manager_0.2.0-1.dsc v-m1 [...] adsb@franck:~$ dpkg-source -x ftp/pool/contrib/v/vmware-manager/vmware-manager_0.2.0-2.dsc v-m2 [...] adsb@franck:~$ diff -adNru v-m1 v-m2 | diffstat [...] vmm | 19 vwm | 1382 ++ 8 files changed, 1414 insertions(+), 16 deletions(-) If you think debdiff is buggy, please file appropriate bug reports. The above agrees with what is shows, however. 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/1343798528.1551.18.ca...@jacala.jungle.funky-badger.org
Bug#682736: unblock: vmware-manager/0.2.0-2
On 01.08.2012 06:22, Adam D. Barratt wrote: adsb@franck:~$ dpkg-source -x ftp/pool/contrib/v/vmware-manager/vmware-manager_0.2.0-1.dsc v-m1 [...] adsb@franck:~$ dpkg-source -x ftp/pool/contrib/v/vmware-manager/vmware-manager_0.2.0-2.dsc v-m2 [...] adsb@franck:~$ diff -adNru v-m1 v-m2 | diffstat [...] vmm | 19 vwm | 1382 ++ 8 files changed, 1414 insertions(+), 16 deletions(-) If you think debdiff is buggy, please file appropriate bug reports. The above agrees with what is shows, however. Similarly, as an example: adsb@franck:~$ diff -adNru v-m2/v{m,w}m | grep = -file = ($cfgfile ? $cfgfile : \*DATA), # Read defaults from __DATA__ section if we cant find a default file. -default = 'global', - -fallback = 'global', -nocase = 1, -allowempty = 1, - -handle_trailing_comment = 1, 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/27cce14229ef24aeeae4b9e7fae030fe@localhost