Bug#592055: xpdf: freeze exception
Hi, On Sat, Aug 07, 2010 at 05:08:04PM +0100, Neil McGovern wrote: ... Please upload and then re-prod us when it hits unstable for an unblock. unblock xpdf/2.03-10 == background summary == After NMU of poppler and recent prod, finally xpdf 2.03-9 which fixed many security issues of xpdf has migrated to testing. Thanks. I just uploaded 2.03-10 package to archive. This package was mostly updated by me and Michael to close bugs: 200610 280460 426502 437529 501661 589425 589542 589650 593565 an many other documentation/comment and dependency clean ups. These include 2 important bug fixes. #589542 [i| |☺] [xpdf] xpdf.desktop file disappeared #589650 [i| |☺] [xpdf] non-clean upgrade path from xpdf-reader: leaves broken /usr/share/doc/xpdf - xpdf-common (dangling) The git repo is at: Vcs-Browser: http://git.debian.org/?p=collab-maint/xpdf.git Vcs-Git: git://git.debian.org/collab-maint/xpdf.git Please note tag for previous upload was osamu/debian/3.02-9 $ git diff -r osamu/debian/3.02-9..master|diffstat|tail -1 24 files changed, 217 insertions(+), 187 deletions(-) I think you checked a0721684b11a78566482467064ceb28503dbb820 and gave us OK to upload. Let me summarize some changes since then. * 2745a9b3f4b78075f5f3f71da99d00014713c6b This fixed typo to correct zxpdf symlink * cd349f4b046ecad26e37d262d78fca876ba5c3bf I reverted some changes I considered bad. One change was one committed after your inspection. The other was one before. (See detail in commit log) Thanks Osamu PS: I now realize bug #386433 was not closed by upload since its record was in git changelog but not in debian changelog. This was indeed fixed in upload. -- 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/20100821053947.ga30...@debian.org
Bug#592055: xpdf: freeze exception
Hi.
On 08/21/2010 02:39 AM, Osamu Aoki wrote:
On Sat, Aug 07, 2010 at 05:08:04PM +0100, Neil McGovern wrote:
...
Please upload and then re-prod us when it hits unstable for an unblock.
unblock xpdf/2.03-10
That should have been xpdf/3.02-10.
== background summary ==
After NMU of poppler and recent prod, finally xpdf 2.03-9 which fixed
(...)
Just to make sure, Osamu meant 3.02-{9,10} in his mail.
Thanks,
--
Rogério Brito : rbr...@{ime.usp.br,gmail.com} : GPG key 1024D/7C2CAEB8
http://rb.doesntexist.org : Packages for LaTeX : algorithms.berlios.de
DebianQA: http://qa.debian.org/developer.php?login=rbrito%40ime.usp.br
--
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/4c6f6b2b.3070...@ime.usp.br
Bug#592055: xpdf: freeze exception
Sorry...
On Sat, Aug 21, 2010 at 02:59:07AM -0300, Rogério Brito wrote:
Hi.
On 08/21/2010 02:39 AM, Osamu Aoki wrote:
On Sat, Aug 07, 2010 at 05:08:04PM +0100, Neil McGovern wrote:
...
Please upload and then re-prod us when it hits unstable for an unblock.
unblock xpdf/2.03-10
unblock xpdf/3.02-10
That should have been xpdf/3.02-10.
Yes.
== background summary ==
After NMU of poppler and recent prod, finally xpdf 2.03-9 which fixed
3.02-9
(...)
Just to make sure, Osamu meant 3.02-{9,10} in his mail.
Thanks.
--
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/20100821072528.ga30...@debian.org
Bug#472377: scribble: uses obsolete version specification in conflicts
On 2008-03-23 Anthony Towns a...@azure.humbug.org.au wrote: Package: scribble Version: 1.10-2 scribble specifies: ] Replaces: scrabble ( 1.10) ] Conflicts: scrabble ( 1.10) These should be =, as per policy 7.1: ] The relations allowed are `', `=', `=', `=' and `' for strictly ] earlier, earlier or equal, exactly equal, later or equal and strictly ] later, respectively. The deprecated forms `' and `' were used to ] mean earlier/later or equal, rather than strictly earlier/later, so they ] should not appear in new packages (though `dpkg' still supports them). Hello, could we please get this fixed for squeeze? dpkg 1.15.8.4 introduced additional warnings that are triggered on every apt-get update: -- Replacing available packages info, using /var/cache/apt/available. warning, in file '/var/cache/apt/available' near line 621485 package 'scribble': `Replaces' field, reference to `scrabble': `' is obsolete, use `=' or `' instead warning, in file '/var/cache/apt/available' near line 621486 package 'scribble': `Conflicts' field, reference to `scrabble': `' is obsolete, use `=' or `' instead Information about 29960 package(s) was updated. -- Afaiui dpkg 1.15.8.4 is targeted for squeeze. I tend to think it might be a good idea to save our users this error message by fixing scribble. Cc-ing -release to get confirmation that a minimal fix would be acceptable for sqeeze. thanks, cu 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/20100821072346.ga11...@downhill.g.la
Re: Bug#472377: scribble: uses obsolete version specification in conflicts
On Sat, 2010-08-21 at 09:23 +0200, Andreas Metzler wrote: ] Replaces: scrabble ( 1.10) ] Conflicts: scrabble ( 1.10) These should be =, as per policy 7.1: [...] -- Replacing available packages info, using /var/cache/apt/available. warning, in file '/var/cache/apt/available' near line 621485 package 'scribble': `Replaces' field, reference to `scrabble': `' is obsolete, use `=' or `' instead [...] Cc-ing -release to get confirmation that a minimal fix would be acceptable for sqeeze. That should be fine. 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/1282378115.11502.4312.ca...@kaa.jungle.aubergine.my-net-space.net
Bug#593774: marked as done (unblock: libmoose-perl/1.09-2)
Your message dated Sat, 21 Aug 2010 09:23:07 +0100
with message-id
1282378988.19892.22.ca...@kaa.jungle.aubergine.my-net-space.net
and subject line Re: Bug#593774: unblock: libmoose-perl/1.09-2
has caused the Debian Bug report #593774,
regarding unblock: libmoose-perl/1.09-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.)
--
593774: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=593774
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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Please unblock package libmoose-perl, version 1.09-2.
The -2 upload adds a patch by Niko Tyni to deal with the FTBFS
on ia64; the change is actually a one-line patch (debdiff attached).
Thanks in advance,
gregor
unblock libmoose-perl/1.09-2
- -- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (990, 'unstable'), (500, 'experimental'), (500, 'testing'), (500,
'stable')
Architecture: i386 (i686)
Kernel: Linux 2.6.35-rc5.201007141816
Locale: LANG=C, LC_CTYPE=de_AT.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
iQIcBAEBCAAGBQJMbu/XAAoJELs6aAGGSaoGINwQALnvxNGWMN7KA4r/v4PcEIVI
KJdUB7m9T0Vt6jdW6spr71xcoiUDxU9fcjiGHVmtT7dxMhnNOA/7Ntgkje1+2snK
KPp7pdBAr9FLP3EtyB7JwjmXbnkHezi9+vbV4WqeVtrW46XV/X4gFzqM8pxH+LZU
Nx46I1gHRdQC7C9J32QIuDe4Y4mOrrN/XXWfVmqdRQzuJNwF4Uh+DRtb9rGJvD/d
+XXDZEJzGbllUFd48ct0D8X6qqjdnM73njaleXASh4oFl+Wyf9sJi4X83FGA5FL+
BU39kI4WHKkmfMkZpPeBLCWaiDxtuTbbnRn2gBH3PfRZbwBqQiVuvHXm9QTcyBLE
J3UWxIKKqTMkCyALa6Gwh1bYd6ijceMiZ7E5RwrBvTskASxCqA0JmxlAeP+fF2Aa
/TVrZ+xYPtomSEkAuAUAnudkYXyaHJ6GCgMot3lGTgINzIfYvgZVbIyer/WSX2g2
69gSNVT0xKHRyMV5c6l0fTXA0ovL2ofH5WXRWKV2J0KUNrqbrL14vmvwPMngpQAv
RnP02++1Pyc1oR3dy2f1GYlGvX/j30IfXh+pQqJb/ZXaw7S6/OKcTohMSQZhTvir
BcEx0xUXyTZTwg1DQAgS67VuEFUZ5L2miuulAw+cgj9oDjQ5tgY4RI0QrymatGer
mAKtRC7c2TkSBpXCb8Du
=nX0l
-END PGP SIGNATURE-
diff -Nru libmoose-perl-1.09/debian/changelog libmoose-perl-1.09/debian/changelog
--- libmoose-perl-1.09/debian/changelog 2010-07-27 20:23:15.0 +0200
+++ libmoose-perl-1.09/debian/changelog 2010-08-20 22:18:38.0 +0200
@@ -1,3 +1,12 @@
+libmoose-perl (1.09-2) unstable; urgency=low
+
+ * Add patch 0001-Work-around-a-numification-problem-on-ia64.patch:
+explicitly numify before doing numeric comparsions as a workaround for a
+numification problem on ia64 (closes: #588118). Thanks to Niko Tyni for
+the analysis and the patch!
+
+ -- gregor herrmann gre...@debian.org Fri, 20 Aug 2010 22:18:02 +0200
+
libmoose-perl (1.09-1) unstable; urgency=low
* New upstream release.
diff -Nru libmoose-perl-1.09/debian/patches/0001-Work-around-a-numification-problem-on-ia64.patch libmoose-perl-1.09/debian/patches/0001-Work-around-a-numification-problem-on-ia64.patch
--- libmoose-perl-1.09/debian/patches/0001-Work-around-a-numification-problem-on-ia64.patch 1970-01-01 01:00:00.0 +0100
+++ libmoose-perl-1.09/debian/patches/0001-Work-around-a-numification-problem-on-ia64.patch 2010-08-20 22:17:26.0 +0200
@@ -0,0 +1,29 @@
+From d6b18c1a4296d6c0c2ac8460a0e6af4560d2a079 Mon Sep 17 00:00:00 2001
+From: Niko Tyni nt...@debian.org
+Date: Fri, 20 Aug 2010 13:32:31 -0600
+Subject: [PATCH] Work around a numification problem on ia64
+
+As seen in http://bugs.debian.org/588118, the numeric comparison
+seems to trigger a bug in perl 5.10.1 on the ia64 architecture.
+
+Explicitly numifying before comparing seems to work around this.
+---
+ lib/Moose/Meta/TypeConstraint.pm |2 +-
+ 1 files changed, 1 insertions(+), 1 deletions(-)
+
+diff --git a/lib/Moose/Meta/TypeConstraint.pm b/lib/Moose/Meta/TypeConstraint.pm
+index 1c8f3de..700f77f 100644
+--- a/lib/Moose/Meta/TypeConstraint.pm
b/lib/Moose/Meta/TypeConstraint.pm
+@@ -135,7 +135,7 @@ sub equals {
+
+ my $other = Moose::Util::TypeConstraints::find_type_constraint($type_or_name) or return;
+
+-return 1 if $self == $other;
++return 1 if (0+$self == 0+$other);
+
+ if ( $self-has_hand_optimized_type_constraint and $other-has_hand_optimized_type_constraint ) {
+ return 1 if $self-hand_optimized_type_constraint == $other-hand_optimized_type_constraint;
+--
+1.7.1
+
diff -Nru libmoose-perl-1.09/debian/patches/series libmoose-perl-1.09/debian/patches/series
--- libmoose-perl-1.09/debian/patches/series 1970-01-01 01:00:00.0 +0100
+++ libmoose-perl-1.09/debian/patches/series 2010-08-20 22:16:51.0 +0200
@@ -0,0 +1 @@
Re: RFC: SQLite3 in Squeeze
On Wed, 2010-08-18 at 16:53 +0200, Mehdi Dogguy wrote: On 08/18/2010 04:34 PM, Julien Cristau wrote: Sounds like we should go back to 3.6.x in testing and sid. If we go that way, we will have to rebuild some packages [1] (red ones). I think we should run forward and ship the upcoming v3.7.1 with Squeeze. On Wed, 2010-08-18 at 12:57 +0900, Ansgar Burchardt wrote: This might also be the cause of failures in the test suite of libdbd-sqlite3-perl (#59 [0]): [...] [0] http://bugs.debian.org/59 It is, at least it builds with sqlite3 version 3.6.23.1 in the same environment. On the other hand, I have found a slowness and can reproduce it with a test case. Contacted upstream and waiting for an answer. On Wed, 2010-08-18 at 19:10 +0200, Mike Hommey wrote: If only sqlite had a symbols file... Will have. Regards, Laszlo/GCS -- 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/1282380361.3511.355.ca...@julia.gcs.org.hu
mysql-proxy unblock
Hi all,
I just did an NMU to fix a few mysql-proxy issues. I confirmed that my
patch fixes the FTBFS properly by building the package on
smetana.debian.org. Version 0.8.0 is better than the version in
squeeze because it ships the rw-splitting.lua script (and others) in
the deb (instead of just the source package), which is probably one of
the most important use-cases for mysql-proxy and it would be a shame
to not have it in squeeze. The source package could use a fair bit of
cleanup, I will likely join the mysql team post-squeeze to help out
with it and other things.
p...@chianamo:~$ debdiff mysql-proxy_0.8.0-1{,.1}.dsc
diff -u mysql-proxy-0.8.0/debian/changelog mysql-proxy-0.8.0/debian/changelog
--- mysql-proxy-0.8.0/debian/changelog
+++ mysql-proxy-0.8.0/debian/changelog
@@ -1,3 +1,12 @@
+mysql-proxy (0.8.0-1.1) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * Clean up after upstream build system properly
+ * Fix FTBFS on sparc (Closes: #575246)
+ * Correctly version the libevent build-dependency
+
+ -- Paul Wise p...@debian.org Sat, 21 Aug 2010 08:29:43 +
+
mysql-proxy (0.8.0-1) unstable; urgency=low
* New upstream release.
diff -u mysql-proxy-0.8.0/debian/control mysql-proxy-0.8.0/debian/control
--- mysql-proxy-0.8.0/debian/control
+++ mysql-proxy-0.8.0/debian/control
@@ -3,7 +3,7 @@
Priority: extra
Maintainer: Debian MySQL Maintainers pkg-mysql-ma...@lists.alioth.debian.org
Uploaders: Norbert Tretkowski no...@debian.org
-Build-Depends: debhelper (= 5), autotools-dev, libmysqlclient-dev,
liblua5.1-dev, pkg-config, libglib2.0-dev, libevent-dev, check
+Build-Depends: debhelper (= 5), autotools-dev, libmysqlclient-dev,
liblua5.1-dev, pkg-config, libglib2.0-dev, libevent-dev (= 1.4),
check
Standards-Version: 3.8.3
Homepage: http://forge.mysql.com/wiki/MySQL_Proxy
Vcs-Browser: http://svn.debian.org/wsvn/pkg-mysql/mysql-proxy/
diff -u mysql-proxy-0.8.0/debian/rules mysql-proxy-0.8.0/debian/rules
--- mysql-proxy-0.8.0/debian/rules
+++ mysql-proxy-0.8.0/debian/rules
@@ -45,7 +45,7 @@
rm -f build-stamp
# Add here commands to clean up after the build process.
- #$(MAKE) distclean
+ [ ! -f Makefile ] || $(MAKE) distclean
rm -f config.sub config.guess
dh_clean
only in patch2:
unchanged:
--- mysql-proxy-0.8.0.orig/src/my_rdtsc.h
+++ mysql-proxy-0.8.0/src/my_rdtsc.h
@@ -30,7 +30,7 @@
#define C_MODE_START G_BEGIN_DECLS
#define C_MODE_END G_END_DECLS
typedef guint64 ulonglong;
-
+#include sys/types.h
/**
This structure contains the characteristics of all the supported timers.
[No CC required, I read -release]
--
bye,
pabs
http://wiki.debian.org/PaulWise
--
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/aanlkti=qub5104ecwiojnshht3evsg6ni7kn=zqka...@mail.gmail.com
Re: Possibility of getting an up-to-date version of Wine into Squeeze
On Sat, Aug 21, 2010 at 04:02:37AM +0200, Ove Kaaven wrote: Den 21. aug. 2010 03:01, skrev Svante Signell: Please take this request seriously. Even if Squeeze is frozen, distributing the same version (1.0.x) of Wine as Lenny does not look good! People are trying to help out! I wouldn't hold much hope. These are the options: 1. Get wine-gecko built on Debian. Apparently gcc-mingw32 4.4.4 did not solve all the problems with it, gcc-mingw32 would apparently have to be upgraded all the way to 4.5.0 to build a fully working package. Not sure if the release team will accept that, and even if they did, packaging Wine 1.2 for squeeze will, by now, be a rush job that may result in a package with serious problems. Have you had a chance to take a look at my packages? I took the time to separate each patch out so that you'd be able to integrate them into your git tree without to much trouble. Note that building wine-gecko also requires an updated version of mingw-w64 (used to produce an updated replacement for mingw32-runtime). You've convinced me as far as requiring wine-gecko is concerned, which, given the new build environment involved, means pushing for release in squeeze is unrealistic. The one thing I do hope now is that you'll accept the various offers of help you've received so that squeeze+1 can have a current version of Wine when it comes out! Regards, Stephen -- 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/20100821085511.ga18...@sk2.org
Re: freeze exception for qemu-kvm package
On Fri, 2010-08-20 at 00:01 +0400, Michael Tokarev wrote: I'm asking for a freeze exception for the package named qemu-kvm, and a companion transitional package kvm, which were in -unstable for 10 days already. Current package in testing is 0.12.4+dfsg-1. The unstable currently has0.12.5+dfsg-1. Unblocked. Regards, Adam -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1282382240.19892.293.ca...@kaa.jungle.aubergine.my-net-space.net
Freeze exception for gdc-4.3
I'd like a freeze exception for gdc-4.3-1.060-4.3.5-1. Fixes #577598 and all D software can now build on sparc (closing #475857, and about a dozen others like it). Regards -- Iain Buclaw *(p e ? p++ : p) = (c 0x0f) + '0';
Bug#593817: unblock: maint-guide/1.2.22
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: freeze-exception Please unblock package maint-guide This upload correct facts on documentation content and change all the content from traditional encoding to UTF-8 (bug: #490161). Although it is a wishlist bug, it is about time to use utf-8. unblock maint-guide/1.2.22 -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100821085824.ga31...@debian.org
Re: Possibility of getting an up-to-date version of Wine into Squeeze
Den 21. aug. 2010 10:55, skrev Stephen Kitt: On Sat, Aug 21, 2010 at 04:02:37AM +0200, Ove Kaaven wrote: Den 21. aug. 2010 03:01, skrev Svante Signell: Please take this request seriously. Even if Squeeze is frozen, distributing the same version (1.0.x) of Wine as Lenny does not look good! People are trying to help out! I wouldn't hold much hope. These are the options: 1. Get wine-gecko built on Debian. Apparently gcc-mingw32 4.4.4 did not solve all the problems with it, gcc-mingw32 would apparently have to be upgraded all the way to 4.5.0 to build a fully working package. Not sure if the release team will accept that, and even if they did, packaging Wine 1.2 for squeeze will, by now, be a rush job that may result in a package with serious problems. Have you had a chance to take a look at my packages? I took the time to separate each patch out so that you'd be able to integrate them into your git tree without to much trouble. I'll take a look when the time comes. Until gcc-mingw32 is updated, there's not much that can be done anyway. Note that I already did some preliminary work a while ago (including a complete wine-gecko package, just waiting for a working compiler), and have had some long-term plans for the Wine package itself, and probably not in the direction you might expect or have worked on. So I might not have use for such patches, but we'll see when it finally becomes possible to update Wine. For now, I suggest working on a working gcc-mingw32, if anything. Note that building wine-gecko also requires an updated version of mingw-w64 (used to produce an updated replacement for mingw32-runtime). My own wine-gecko package does not need this. (Though if mingw32-runtime were to be updated, its build system could be simplified a bit, I guess.) -- 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/4c6f9c83.6070...@arcticnet.no
Re: Python 3 support in Squeeze
* Piotr Ożarowski (pi...@debian.org) [100821 00:45]: Please note that in most (all?) cases 2to3 tool (which converts python2.X code to python3.X one) will have to be used (again, no new upstream versions) so patching the code in Squeeze (security bugs, etc.) will not have to be done twice (at least in most cases). In that case, one of the pre-conditions would be to add an appropriate README that tells NMUers (security team et al) what to do to avoid double patching. Otherwise, please wait for a couple more days for a full answer. Andi -- 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/20100821093952.gc15...@mails.so.argh.org
Re: mysql-proxy unblock
On Sat, Aug 21, 2010 at 17:02:44 +0800, Paul Wise wrote: Hi all, I just did an NMU to fix a few mysql-proxy issues. Unblocked. Cheers, Julien signature.asc Description: Digital signature
Bug#593610: release.debian.org: freeze exception pre-approval: qorganizer
On Thu, Aug 19, 2010 at 19:15:38 +0300, Eugene V. Lyubimkin wrote: Qorganizer has priority 'optional' and losing data sounds like important bug for me. Can I upload new upstream patch release 3.1.5 (current is 3.1.4)? Please upload and get back to us when the package is accepted in the archive. Cheers, Julien signature.asc Description: Digital signature
Re: freeze exception for gcc-4.5 (i386, amd64 only)
2010/8/20, Ludovic Brenta ludo...@ludovic-brenta.org: Arthur Loiret aloi...@debian.org writes: Are you saying that we are developing an operating system which is not suitable for active development, or that it shouldn't be made suitable for active development? I think he meant that stable is not the place for active development of the operating system and I agree with that. Like I said earlier, the presence of gcc-4.5 in Squeeze does not bother me. What bothers me is replacing some core libraries like libgcc1 and libstdc++ with versions from gcc-4.5. There is no regression in the runtime libraries tests, and they run very fine with our current testing distribution. You can try by yourself if you don't believe so. Also, although I really don't know how common this is, I know people who use stable for active development, by obligation. OK, then they use the stable compiler, by obligation :) gcc-4.5 is not stable: it is in experimental and has not even reached unstable yet. gcc-4.4 is stable. Upstream GCC version 4.5.0 has been released in mid april, and GCC 4.5.1 has less serious regression than GCC 4.4.4. Please explain why do you think gcc-4.5 isn't stable. Now, to be clear, what nice things would gcc-4.5 bring to our users? Right: gcc-4.5 is nice to have, maybe even very, very nice to have, but it does not fix any RC bugs and _might_ introduce some due to replacing important libraries from gcc-4.4. So, I support the release manager's decision not to include gcc-4.5 in Squeeze. Same thing again: it has been tested and works well. I understand your bad feeling about this, but it has no reason to be. Arthur. -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/aanlkti=xohjlyjj6tk=kvagpwuhcftpzw1mscxs-e...@mail.gmail.com
Re: freeze exception for gcc-4.5 (i386, amd64 only)
On Fri, Aug 20, 2010 at 19:33:12 +0200, Arthur Loiret wrote: Now, to be clear, what nice things would gcc-4.5 bring to our users? There is a complete list here [0], but those ones are, in my opinion, very nice: - The new link time optimiser. - Improved C++0x support. - Plugins support. My understanding is that lto in 4.5 is not quite there yet. Not that I've tried it or anything. Cheers, Julien signature.asc Description: Digital signature
Re: freeze exceptions: qpdf, tiff
Julien Cristau jcris...@debian.org wrote: On Fri, Aug 20, 2010 at 16:27:13 -0400, Jay Berkenbilt wrote: For qpdf, this is a new upstream version that is binary compatible with the old one. qpdf is isolated in the dependency tree (no other packages depend on it), and I am upstream, so I can definitely vouch for the fact that the changes were relatively minor and should be very safe. I see new API but no shlibs bump? New API doesn't require a shlibs bump. Changed or removed API requires a shlibs bump. 2.2.0 adds several new functions. The only function that changed incompatibly was QPDFWriter::disableIncompatbleEncryption(float), which is a private method in the QPDFWriter object. No external code could call that method, so it can't be an unresolved symbol anywhere, so changing it does not require a shlibs bump. I use libtool to manage the shlibs. CURRENT,REVISION,AGE for 2.2.0 is 4,0,1. For 2.1.5, it was 3,4,0. This is consistent with new API having been added but no callable API having been changed or removed. To be absolutely certain, I built qpdf 2.1.5 from source, swapped its native libqpdf.so.3.0.4 with a copy of libqpdf.so.3.1.0 (renamed to libqpdf.os.3.4), and ran qpdf's very thorough test suite. The 2.1.5 qpdf's test suite passes when run with the 2.2.0 qpdf's shared library with the exception of the fact that the test suite reports incomplete coverage on the new API (which is, of course, not exercised by the 2.1.5 test suite). So (assuming you trust the thoroughness of the qpdf test suite), this also confirms that the ABI has not been broken. Are you seeing something different from this? If so, please let me know. I'm also interested to know what you're using to determine whether there are ABI changes. Thanks for being so thorough. -- Jay Berkenbilt q...@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/20100821090836.0290813736.qww314...@soup
choqok 0.9.81-2
Hello. I just uploaded choqok 0.9.81-2, which makes no changes except to correct a missing dependency (Bug #593537). Please allow this package to enter squeeze. Thanks. noah signature.asc Description: Digital signature
Re: freeze exceptions: qpdf, tiff
On Sat, Aug 21, 2010 at 09:08:36 -0400, Jay Berkenbilt wrote: Julien Cristau jcris...@debian.org wrote: On Fri, Aug 20, 2010 at 16:27:13 -0400, Jay Berkenbilt wrote: For qpdf, this is a new upstream version that is binary compatible with the old one. qpdf is isolated in the dependency tree (no other packages depend on it), and I am upstream, so I can definitely vouch for the fact that the changes were relatively minor and should be very safe. I see new API but no shlibs bump? New API doesn't require a shlibs bump. Changed or removed API requires a shlibs bump. Err. New API is what shlibs is for. Changed or removed API requires a SONAME and package name change. Cheers, Julien signature.asc Description: Digital signature
Re: choqok 0.9.81-2
On Sat, 2010-08-21 at 08:39 -0400, Noah Meyerhans wrote: Hello. I just uploaded choqok 0.9.81-2, which makes no changes except to correct a missing dependency (Bug #593537). Please allow this package to enter squeeze. Unblocked. Regards, Adam -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1282398058.19892.1789.ca...@kaa.jungle.aubergine.my-net-space.net
Re: What to do about libtest-harness-perl?
[re-ordered] On Wed, 2010-08-18 at 23:02 +0100, nicho...@periapt.co.uk wrote: Quoting Adam D. Barratt a...@adam-barratt.org.uk: On Sun, 2010-08-15 at 15:43 +0100, nicho...@periapt.co.uk wrote: The differences between 3.21 and 3.22 are more substantial. From what I can see however the area of the bug was being worked on almost right up until the release. In other words it looks to me as if the patch forms a large part of what happened between 3.21 and 3.22. [...] The bug concerns how the prove utility handles testing scripts directly. Anyway other members of the Debian Perl group will want to express an opinion. Did any of them do so and simply fail to Cc -release? :-) The group definitely knows about the issue. What other information apart from opinions would be of use? I only mentioned it because you said they would want to express their opinion. ;-) Looking through the upstream diff, I had a couple of queries / comments: Why has Build.PL become NotBuild.PL? lib/TAP/Parser/Grammar.pm: -For purposes for forward compatability, any result which does not match the +For purposes for forward compatibility, any result which does not match the should be purposes of 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/1282399382.19892.1922.ca...@kaa.jungle.aubergine.my-net-space.net
Re: approval of OOo 3.2.1-6
On Sat, Aug 21, 2010 at 15:12:03 +0200, Rene Engelhard wrote: Hi, please unblock openoffice.org/1:3.2.1-6. unblocked. Cheers, Julien signature.asc Description: Digital signature
Bug#593817: marked as done (unblock: maint-guide/1.2.22)
Your message dated Sat, 21 Aug 2010 15:25:42 +0100 with message-id 20100821142542.gp2...@radis.liafa.jussieu.fr and subject line Re: Bug#593817: unblock: maint-guide/1.2.22 has caused the Debian Bug report #593817, regarding unblock: maint-guide/1.2.22 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.) -- 593817: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=593817 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 maint-guide This upload correct facts on documentation content and change all the content from traditional encoding to UTF-8 (bug: #490161). Although it is a wishlist bug, it is about time to use utf-8. unblock maint-guide/1.2.22 -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash ---End Message--- ---BeginMessage--- On Sat, Aug 21, 2010 at 17:58:24 +0900, Osamu Aoki wrote: unblock maint-guide/1.2.22 Done. Cheers, Julien signature.asc Description: Digital signature ---End Message---
Re: Bug#593627: java-common: please use openjdk as default jdk on powerpcspe
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 2010-08-19 19:40, Sebastian Andrzej Siewior wrote: Package: java-common Version: 0.39 Severity: wishlist Tags: patch sid User: debian-powerpc...@breakpoint.cc Usertags: powerpcspe openjdk is built and seems to work :) Sebastian Hi Personally I am okay with doing it and it is the intention of the Java Team to make openjdk the default on all architectures. The question is if we should do it now or after Squeeze (CC'ed the release team) for their comments. ~Niels -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEAREIAAYFAkxv3w0ACgkQVCqoiq1YlqwaPwCgiBn35OUchzcwhAZNAFSo7Fk/ ENwAnAxg6Y8nH5ID7svLbRY6AVdzwDLl =jgd+ -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/4c6fdf0e.6090...@thykier.net
Bug#593843: unblock: gthumb/3:2.11.5-3
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: freeze-exception
I uploaded gthumb 2.11.5-3 in sid, which fixes RC bug #593813 . The bug is
already fixed upstream (the version in experimental, 2.11.90), and I backported
the fix from there.
The patch is tiny, attaching it to this message.
It would be nice to have this in Squeeze. Thank you :)
unblock gthumb/3:2.11.5-3
--
. ''`. Debian developer | http://wiki.debian.org/DavidPaleino
: :' : Linuxer #334216 --|-- http://www.hanskalabs.net/
`. `'` GPG: 1392B174 | http://deb.li/dapal
`- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174
Author: Paolo Bacchilega pao...@src.gnome.org
Description: fix photo comments loss when upgrading from 2.10
Bug: http://bugzilla.gnome.org/show_bug.cgi?id=626893
Bug-Debian: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=593813
Comment: Patch backported by David Paleino da...@debian.org, using the
following git commits:
- http://git.gnome.org/browse/gthumb/commit/?id=b80580d3341d2b050bf59fdc42973ed28e93bc54
- http://git.gnome.org/browse/gthumb/commit/?id=08fcb249ec7e6f2daaf99f50ece6612cfa5a272c
- http://git.gnome.org/browse/gthumb/commit/?id=66bc3971668f06970594c55c777b5f628882c4e9
---
extensions/exiv2_tools/exiv2-utils.cpp | 99 +--
extensions/exiv2_tools/gth-metadata-provider-exiv2.c | 23 +++-
extensions/exiv2_tools/main.c| 14 ++
po/POTFILES.skip |2
4 files changed, 107 insertions(+), 31 deletions(-)
--- gthumb.orig/extensions/exiv2_tools/exiv2-utils.cpp
+++ gthumb/extensions/exiv2_tools/exiv2-utils.cpp
@@ -57,6 +57,14 @@ const char *_DATE_TAG_NAMES[] = {
NULL
};
+const char *_LAST_DATE_TAG_NAMES[] = {
+ Exif::Image::DateTime,
+ Xmp::exif::DateTime,
+ Xmp::xmp::ModifyDate,
+ Xmp::xmp::MetadataDate,
+ NULL
+};
+
const char *_ORIGINAL_DATE_TAG_NAMES[] = {
Exif::Photo::DateTimeOriginal,
Xmp::exif::DateTimeOriginal,
@@ -132,11 +140,11 @@ const char *_ORIENTATION_TAG_NAMES[] = {
};
const char *_DESCRIPTION_TAG_NAMES[] = {
+ Iptc::Application2::Caption,
+ Xmp::dc::description,
Exif::Photo::UserComment,
Exif::Image::ImageDescription,
- Xmp::dc::description,
Xmp::tiff::ImageDescription,
- Iptc::Application2::Caption,
Iptc::Application2::Headline,
NULL
};
@@ -263,24 +271,15 @@ set_file_info (GFileInfo *info,
static void
-set_attribute_from_tagset (GFileInfo *info,
- const char *attribute,
- const char *tagset[])
-{
- GObject *metadata;
- int i;
- char*key;
- char*description;
- char*formatted_value;
- char*raw_value;
- char*type_name;
-
- metadata = NULL;
- for (i = 0; tagset[i] != NULL; i++) {
- metadata = g_file_info_get_attribute_object (info, tagset[i]);
- if (metadata != NULL)
- break;
- }
+set_attribute_from_metadata (GFileInfo *info,
+ const char *attribute,
+ GObject*metadata)
+{
+ char *key;
+ char *description;
+ char *formatted_value;
+ char *raw_value;
+ char *type_name;
if (metadata == NULL)
return;
@@ -292,6 +291,7 @@ set_attribute_from_tagset (GFileInfo *i
raw, raw_value,
value-type, type_name,
NULL);
+
set_file_info (info,
attribute,
description,
@@ -303,6 +303,26 @@ set_attribute_from_tagset (GFileInfo *i
static void
+set_attribute_from_tagset (GFileInfo *info,
+ const char *attribute,
+ const char *tagset[])
+{
+ GObject *metadata;
+ int i;
+
+ metadata = NULL;
+ for (i = 0; tagset[i] != NULL; i++) {
+ metadata = g_file_info_get_attribute_object (info, tagset[i]);
+ if (metadata != NULL)
+ break;
+ }
+
+ if (metadata != NULL)
+ set_attribute_from_metadata (info, attribute, metadata);
+}
+
+
+static void
set_string_list_attribute_from_tagset (GFileInfo *info,
const char *attribute,
const char *tagset[])
@@ -336,9 +356,32 @@ set_string_list_attribute_from_tagset (G
static void
set_attributes_from_tagsets (GFileInfo *info)
{
- set_attribute_from_tagset (info, general::datetime, _DATE_TAG_NAMES);
+ set_attribute_from_tagset (info, general::datetime, _LAST_DATE_TAG_NAMES);
+ if (g_file_info_get_attribute_object (info, general::datetime) == NULL)
+ set_attribute_from_tagset (info, general::datetime, _ORIGINAL_DATE_TAG_NAMES);
+
set_attribute_from_tagset (info, general::description, _DESCRIPTION_TAG_NAMES);
set_attribute_from_tagset (info, general::title, _TITLE_TAG_NAMES);
+
+ /* if iptc::caption and iptc::headline are different use iptc::headline
+ * to set general::title, if not already set. */
+
+ if (g_file_info_get_attribute_object (info, general::title) == NULL) {
+ GObject *iptc_caption;
+ GObject *iptc_headline;
+
+ iptc_caption = g_file_info_get_attribute_object (info, Iptc::Application2::Caption);
+ iptc_headline = g_file_info_get_attribute_object (info, Iptc::Application2::Headline);
+
+ if ((iptc_caption != NULL)
+
Re: libsoqt3-20 is linked against Qt 4 (should be Qt 3)
On Sat, Aug 21, 2010 at 02:52:48AM +0200, Gerhard Dirschl wrote: Package: libsoqt3-20 Version: 1.4.2~svn20090224-2 libsoqt3 should be linked against Qt 3 but actually it is linked against Qt 4 (apart from the suffix, there is no difference between libsoqt3 and libsoqt4). Wow. This was broken perhaps as long ago as March 2009 and no-one noticed until now. Must not be an important package :-) Dear Debian-Release: SoQt is a library that provides Qt widgets for a visualization library (Coin). When I first packaged it, Qt was version 3. In early days of Qt4, it seemed important to provide SoQt for both Qt3 and Qt4. So I modified the soqt source package to produce both libsoqt3-20 (Qt3 version) and libsoqt4-20 (Qt4 version). This worked in the Lenny version. In March 2009, I updated the soqt sources and apparently broke this so that libsoqt3-20 also links against Qt4. :-) Since I'm not quite sure of the freeze timelines, I'd like your advice. First, it's clear that libsoqt3-20 (and libsoqt3-dev) shouldn't be released as-is. Is it possible to remove those two binary packages from testing while keeping the others (e.g. libsoqt4-20)? If so, I'd suggest that can be done immediately. Regardless of the above, I can prepare a new upload. I can see a few options: 1. Fix present source package to build libsoqt3-20 properly. That may take me a couple of weeks to get to. 2. Use present source package, removing libsoqt3-20 and libsoqt3-dev. This option takes a couple of days. 3. Package new upstream (1.5.0 released March 2010) that provides improved support for Qt4. This will take me a couple of weeks. Option #3 is my preference. If I have to invest the time to figure out what went wrong with linking to Qt3 and fix it, I'd prefer to also update the source at the same time. Given that SoQt is a minor library, I'd consider it low risk for the archive. If the release team feels otherwise, I can work with the present sources. Please advise whether an upload in 2 weeks (option #1) will make it into the next release or whether I should instead choose option #2. Thanks, -Steve signature.asc Description: Digital signature
Bug#579795: apt transition
On Fri, Apr 30, 2010 at 21:57:45 +0200, Michael Vogt wrote: This is a bit of a meta binNMU request. The apt team wants to upload a new version with a ABI break to unstable. The version is currently in experimental and requires rebuilds of the packages that depend on libapt-pkg-libc6.9-6-4.8. What is the best way forward to keep the disruption as low as possible for the archive? Ideally after the upload of apt to unstable the binNUMs would follow relatively quickly for important packages like aptitude, python-apt, libept etc. We're (finally) getting ready to start this. Can you provide an outline of the changes you want to get in? Cheers, Julien signature.asc Description: Digital signature
Re: freeze exceptions: qpdf, tiff
Julien Cristau jcris...@debian.org wrote: I hope you will not take it the wrong way that I'm continuing to argue this point. We share a common goal of ensuring that this change is safe and will not cause problems, and I appreciate that you have to act in a policing role about this issue. I also appreciate that many developers don't understand the subtleties of what constitutes a breaking ABI change. In the case of qpdf, it seems as though we disagree on whether the changes are safe. If I have made a mistake, I will surely correct it, but at this point, I still don't believe that I have introduced an incompatible change to the library's ABI, and I really don't want to artificially and needlessly increase the SONAME as that is disruptive to my users. So I continue the discussion below. I see new API but no shlibs bump? New API doesn't require a shlibs bump. Changed or removed API requires a shlibs bump. Err. New API is what shlibs is for. Changed or removed API requires a SONAME and package name change. How is what you're saying different from what I'm saying? I interpreted shlibs bump to mean changing the SONAME. Do you mean something different? You say Changed or removed API requires SONAME and package name change, and I agree. But I don't believe that I have introduced any changed or removed API. Adding new API is not a reason to increase the SONAME. This happens all the time. The reason for this is that the SONAME needs to change when there's a reason that OLD applications linked originally with the OLD library can't continue to work with the NEW library. In other words, you should be able to upgrade the shared library without breaking existing applications. Having new callable methods appear in the shared library will not interfere with existing applications as long as existing symbols can be resolved in the same way. There's no expectation that executables linked with the new library will work with the old library. That's why adding new API doesn't require changing the SONAME. Do you disagree with my understanding of when the SONAME has to change, or do you disagree with my analysis that none of the things that require an SONAME change have happened? Or have I just done a poor job of explaining why my changes are compatible and have unwitting led you to a false conclusion? If our communication is clear but we disagree on one of these issues, can we get someone else to weigh in? Isn't this what the technical committee is for? A good discussion of this issue can be found here: http://tldp.org/HOWTO/Program-Library-HOWTO/shared-libraries.html Fundamentally though, you can usually tell by comparing the header files and the list of exported symbols from the libraries. The only changes that could even possibly be considered worthy of causing an SONAME change are the addition of two new private data members to the end of QPDF_Stream and the change to a private member function of QPDFWriter. However, QPDF_Stream is a private class to the library: its header is not installed, no actual instances of the class are ever exposed to the users of the library, and no classes are derived from QPDF_Stream. Therefore, addition of new data members to the end of the object can't cause breakage of existing applications. And the method that changed in QPDFWriter is private. It can't be called from outside the QPDFWriter class, so this is safe too. If there's any doubt, you can run nm -D --demangle on the old and new shared libraries, observe that the only method that disappeared from the old is QPDFWriter::disableIncompatbleEncryption(float), and then verify by looking at QPDFWriter.hh in 2.1.5 that this was in fact a private method. I designed QPDF's APIs the way they are in significant part to make it possible to make certain types of changes without breaking binary compatibility. -- Jay Berkenbilt q...@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/20100821105320.0290889916.qww314...@soup
Re: freeze exceptions: qpdf, tiff
Seems we're just talking past each other. On Sat, Aug 21, 2010 at 10:53:20 -0400, Jay Berkenbilt wrote: I interpreted shlibs bump to mean changing the SONAME. Do you mean something different? I wasn't talking about the library's SONAME, I was talking about the shlibs control file from your package (as documented in policy §8.6, and used by dpkg-shlibdeps). Cheers, Julien signature.asc Description: Digital signature
Re: Unblock request: Cherokee
On Wed, 2010-08-18 at 18:40 -0500, Gunnar Wolf wrote:
Squeeze currently has version 1.0.4-1 of the Cherokee webserver. This
version suffers from a series of SSL/TLS problems (worst of all is
that it just won't work with Firefox).
I am uploading version 1.0.8-1 - Upstream's release notices since
1.0.4 include:
[...]
So, as you can see, the NEW characteristics are quite minor - Most of
what has been added are FIXes.
There's also some changes that weren't mentioned, unless I missed them -
for instance, the addition of an AJAX upload control,
admin/{Backup,Login}.py and CTK/XMLRPCProxy.py
Many of those changes appear to be interconnected, so it's probable
they're support covered by one of the changes you mentioned.
In any case, the changes look sane enough; unblocked.
Regards,
Adam
--
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/1282404163.19892.2384.ca...@kaa.jungle.aubergine.my-net-space.net
Re: udeb unblocks: netcfg, libdebian-installer
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Adam D. Barratt a...@adam-barratt.org.uk writes: busybox recently migrated to testing; this new version apparently has an incompatibility with the netcfg version currently in testing, so we were asked by Aurelien whether it would be possible to migrate netcfg as well. netcfg is on the cannot automatically migrate without approval udeb list and, in order to migrate it, the new version of libdebian-installer (which is also on the needs approval list) would also have to migrate at the same time. ack for netcfg and libdebian-installer. - -- O T A V I OS A L V A D O R - - E-mail: ota...@debian.org UIN: 5906116 GNU/Linux User: 239058 GPG ID: CDFC6E4F Home Page: http://otavio.ossystems.com.br - - Microsoft sells you Windows ... Linux gives you the whole house. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Processed by Mailcrypt 3.5.9 http://mailcrypt.sourceforge.net/ iQIcBAEBCAAGBQJMb/ONAAoJEOtw/vPN/G5P7PsQAMvk7w6OKHdNlY7feguPQnrx Rns/iZiKVntuA+AjoHPb2obJmj+XFZ4SSj5hvww1Qyn0mFgjiXxzu0Y6iuqimaZ0 OQKK/XGZ/pZashfdajd+xKqLs69s6j8KDNj15ge+ub/wIAz/neNop5AXpmSeoP2E /YYqt3YHlauqVcz9+Ut/FnEXK8rliUJlkU3ibxgWYMj8xcwD799zPimWM/E4i4QQ zXX5Ey/fGlw/dKXAMEOu9sTOWMtGyl+n7MiXBMFkE0bZuOk20PQ6rowQ9TRdchuh 4tNP6AX7dXeQUVtD73PtH1c6S+YN4qv9KX/nQIPNXbgiscJSL/a2u6M6RmuB01ae aYLNoX5R2Zd/2eW24qqm8dF6LYJFWEINU/CNrkXjr1uxbOnVJpqX1zw2CMriRFyu fvovWi4howgRu7Hirfby2pyycBzxxGdDTIJtrryMjvCBTlImTO/Xahu6Rc3Fzv54 v1bxyPShQgBRPWpQsvtUGwv1HekYAQMDUrsYwsB/Gwmz2JpRCkEEz0KgxZmq0NAA 66+9+d2MXFU1AFp3BTwHe1jejWqU0LwM+ouJcjaGur6Lt6d30aFirOMKfU55bGhm ejXm/TFrErU1kVZ9hbVtvSIj/bOyWtI/YWffsTF2YlReMq+jMPluUiTMy/+DJdEs 2F9b8Y2Sd1beFpav+8q2 =9UnZ -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/87mxsg6kiy@neumann.lab.ossystems.com.br
Re: libsoqt3-20 is linked against Qt 4 (should be Qt 3)
On Sat, 2010-08-21 at 09:36 -0500, Steve M. Robbins wrote: libsoqt3 should be linked against Qt 3 but actually it is linked against Qt 4 (apart from the suffix, there is no difference between libsoqt3 and libsoqt4). [...] First, it's clear that libsoqt3-20 (and libsoqt3-dev) shouldn't be released as-is. Is it possible to remove those two binary packages from testing while keeping the others (e.g. libsoqt4-20)? If so, I'd suggest that can be done immediately. No; the packages will only get removed from testing when either the binary packages no longer exist in unstable or the source package is removed from testing. Regardless of the above, I can prepare a new upload. I can see a few options: 1. Fix present source package to build libsoqt3-20 properly. That may take me a couple of weeks to get to. 2. Use present source package, removing libsoqt3-20 and libsoqt3-dev. This option takes a couple of days. 3. Package new upstream (1.5.0 released March 2010) that provides improved support for Qt4. This will take me a couple of weeks. Given that nothing in the archive uses the Qt3 libraries, either of #1 or #2 should be ok. Hopefully a fix could be found more quickly though. :) [...] If the release team feels otherwise, I can work with the present sources. Please advise whether an upload in 2 weeks (option #1) will make it into the next release or whether I should instead choose option #2. How large is the diff between 1.4.2 and 1.5.0? Given that it would represent a year of development relative to unstable, I'm guessing it might be quite large. :-/ 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/1282405420.19892.2504.ca...@kaa.jungle.aubergine.my-net-space.net
Bug#593850: unblock: libktoblzcheck/1.28-1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: freeze-exception Please unblock package libktoblzcheck Reasons: - upstream released some days ago - upstream update contains *only* following changes: + quarterly update of bankdata.txt (origin: Deutsche Bundesbank) + bugfix for one check method Thanks in advance, Micha unblock libktoblzcheck/1.28-1 -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100821153024.4462.66203.report...@ian.lenk.info
Re: udeb unblocks: netcfg, libdebian-installer
On Sat, 2010-08-21 at 12:41 -0300, Otavio Salvador wrote: ack for netcfg and libdebian-installer. Thanks; both unblocked. Regards, Adam -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1282406121.25491.30.ca...@kaa.jungle.aubergine.my-net-space.net
Re: freeze exceptions: qpdf, tiff
Julien Cristau jcris...@debian.org wrote: Seems we're just talking past each other. On Sat, Aug 21, 2010 at 10:53:20 -0400, Jay Berkenbilt wrote: I interpreted shlibs bump to mean changing the SONAME. Do you mean something different? I wasn't talking about the library's SONAME, I was talking about the shlibs control file from your package (as documented in policy §8.6, and used by dpkg-shlibdeps). AH! (*strikes head on forehead*) Oops... Thanks for catching that. My mistake. I so thoroughly missed the point that I interpreted shlibs bump as SONAME change. Of course shlibs makes sure you have a new enough version of the library package. I will fix it, re-upload, and re-request a freeze exception. Thanks for setting me straight, and sorry for the confusion. -- Jay Berkenbilt q...@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/20100821120054.0290808079.qww314...@soup
Bug#593843: unblock: gthumb/3:2.11.5-3
On Sat, 2010-08-21 at 16:29 +0200, David Paleino wrote:
I uploaded gthumb 2.11.5-3 in sid, which fixes RC bug #593813 . The bug is
already fixed upstream (the version in experimental, 2.11.90), and I
backported
the fix from there.
The patch is tiny, attaching it to this message.
const char *_DESCRIPTION_TAG_NAMES[] = {
+ Iptc::Application2::Caption,
+ Xmp::dc::description,
Exif::Photo::UserComment,
Exif::Image::ImageDescription,
- Xmp::dc::description,
Xmp::tiff::ImageDescription,
- Iptc::Application2::Caption,
I'm hoping those aren't exported anywhere near gthumb-dev :-)
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/1282406439.25491.60.ca...@kaa.jungle.aubergine.my-net-space.net
Bug#593850: marked as done (unblock: libktoblzcheck/1.28-1)
Your message dated Sat, 21 Aug 2010 17:08:00 +0100 with message-id 1282406880.25491.102.ca...@kaa.jungle.aubergine.my-net-space.net and subject line Re: Bug#593850: unblock: libktoblzcheck/1.28-1 has caused the Debian Bug report #593850, regarding unblock: libktoblzcheck/1.28-1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 593850: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=593850 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 libktoblzcheck Reasons: - upstream released some days ago - upstream update contains *only* following changes: + quarterly update of bankdata.txt (origin: Deutsche Bundesbank) + bugfix for one check method Thanks in advance, Micha unblock libktoblzcheck/1.28-1 ---End Message--- ---BeginMessage--- On Sat, 2010-08-21 at 17:30 +0200, Micha Lenk wrote: Please unblock package libktoblzcheck Reasons: - upstream released some days ago - upstream update contains *only* following changes: + quarterly update of bankdata.txt (origin: Deutsche Bundesbank) + bugfix for one check method Unblocked. Regards, Adam ---End Message---
Bug#593843: unblock: gthumb/3:2.11.5-3
On Sat, 21 Aug 2010 17:00:39 +0100, Adam D. Barratt wrote:
On Sat, 2010-08-21 at 16:29 +0200, David Paleino wrote:
I uploaded gthumb 2.11.5-3 in sid, which fixes RC bug #593813 . The bug is
already fixed upstream (the version in experimental, 2.11.90), and I
backported the fix from there.
The patch is tiny, attaching it to this message.
const char *_DESCRIPTION_TAG_NAMES[] = {
+ Iptc::Application2::Caption,
+ Xmp::dc::description,
Exif::Photo::UserComment,
Exif::Image::ImageDescription,
- Xmp::dc::description,
Xmp::tiff::ImageDescription,
- Iptc::Application2::Caption,
I'm hoping those aren't exported anywhere near gthumb-dev :-)
Ehm, no :)
Thank you for looking,
David
--
. ''`. Debian developer | http://wiki.debian.org/DavidPaleino
: :' : Linuxer #334216 --|-- http://www.hanskalabs.net/
`. `'` GPG: 1392B174 | http://deb.li/dapal
`- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174
signature.asc
Description: PGP signature
Please consider migrating gearman-interface 0.13.2-2 to testing
Hello Debian Release Team, and thank you for your hard work! I am the maintainer for the gearman-interface source package. I hope that you will consider migrating v0.13.2-2 of gearman-interface and its associated binaries, python-gearman.libgearman and python3-gearman.libgearman, into testing, rather than dropping them. Currently the version in testing has this grave bug: http://bugs.debian.org/cgi-bin/bugreport.cgi?archive=nobug=593642 0.13.2-2 was recently uploaded to unstable, and fixes the problem, which is purely a build issue. It has this changelog: * debian/rules: moving tarball .c files out of the way so swig will rebuild and ship the .py files. (Closes: #593642) * add description of gearman to long description (quiets lintian) * Removing unnecessary build depends on ruby/rubygems * Version build-dep on python3 * change python:Provides to python3:Provides * re-enable dh_usrlocal * Added watch file Because the python3 change adds a versioned build dependency on python3 (= 3.1.2-6~), it will have to wait for python3 3.1.2-6 to migrate into testing, which I see, has already been granted an exception and should be migrated in 3 days. please cc: me on any replies as I am not subscribed to debian-release. Thank you for your time, -- Clint Byrum -- 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/ab857f62-2c96-417b-9826-01052ba4e...@ubuntu.com
Bug#593843: marked as done (unblock: gthumb/3:2.11.5-3)
Your message dated Sat, 21 Aug 2010 17:30:11 +0100
with message-id
1282408211.26197.19.ca...@kaa.jungle.aubergine.my-net-space.net
and subject line Re: Bug#593843: unblock: gthumb/3:2.11.5-3
has caused the Debian Bug report #593843,
regarding unblock: gthumb/3:2.11.5-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.)
--
593843: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=593843
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
I uploaded gthumb 2.11.5-3 in sid, which fixes RC bug #593813 . The bug is
already fixed upstream (the version in experimental, 2.11.90), and I backported
the fix from there.
The patch is tiny, attaching it to this message.
It would be nice to have this in Squeeze. Thank you :)
unblock gthumb/3:2.11.5-3
--
. ''`. Debian developer | http://wiki.debian.org/DavidPaleino
: :' : Linuxer #334216 --|-- http://www.hanskalabs.net/
`. `'` GPG: 1392B174 | http://deb.li/dapal
`- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174
Author: Paolo Bacchilega pao...@src.gnome.org
Description: fix photo comments loss when upgrading from 2.10
Bug: http://bugzilla.gnome.org/show_bug.cgi?id=626893
Bug-Debian: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=593813
Comment: Patch backported by David Paleino da...@debian.org, using the
following git commits:
- http://git.gnome.org/browse/gthumb/commit/?id=b80580d3341d2b050bf59fdc42973ed28e93bc54
- http://git.gnome.org/browse/gthumb/commit/?id=08fcb249ec7e6f2daaf99f50ece6612cfa5a272c
- http://git.gnome.org/browse/gthumb/commit/?id=66bc3971668f06970594c55c777b5f628882c4e9
---
extensions/exiv2_tools/exiv2-utils.cpp | 99 +--
extensions/exiv2_tools/gth-metadata-provider-exiv2.c | 23 +++-
extensions/exiv2_tools/main.c| 14 ++
po/POTFILES.skip |2
4 files changed, 107 insertions(+), 31 deletions(-)
--- gthumb.orig/extensions/exiv2_tools/exiv2-utils.cpp
+++ gthumb/extensions/exiv2_tools/exiv2-utils.cpp
@@ -57,6 +57,14 @@ const char *_DATE_TAG_NAMES[] = {
NULL
};
+const char *_LAST_DATE_TAG_NAMES[] = {
+ Exif::Image::DateTime,
+ Xmp::exif::DateTime,
+ Xmp::xmp::ModifyDate,
+ Xmp::xmp::MetadataDate,
+ NULL
+};
+
const char *_ORIGINAL_DATE_TAG_NAMES[] = {
Exif::Photo::DateTimeOriginal,
Xmp::exif::DateTimeOriginal,
@@ -132,11 +140,11 @@ const char *_ORIENTATION_TAG_NAMES[] = {
};
const char *_DESCRIPTION_TAG_NAMES[] = {
+ Iptc::Application2::Caption,
+ Xmp::dc::description,
Exif::Photo::UserComment,
Exif::Image::ImageDescription,
- Xmp::dc::description,
Xmp::tiff::ImageDescription,
- Iptc::Application2::Caption,
Iptc::Application2::Headline,
NULL
};
@@ -263,24 +271,15 @@ set_file_info (GFileInfo *info,
static void
-set_attribute_from_tagset (GFileInfo *info,
- const char *attribute,
- const char *tagset[])
-{
- GObject *metadata;
- int i;
- char*key;
- char*description;
- char*formatted_value;
- char*raw_value;
- char*type_name;
-
- metadata = NULL;
- for (i = 0; tagset[i] != NULL; i++) {
- metadata = g_file_info_get_attribute_object (info, tagset[i]);
- if (metadata != NULL)
- break;
- }
+set_attribute_from_metadata (GFileInfo *info,
+ const char *attribute,
+ GObject*metadata)
+{
+ char *key;
+ char *description;
+ char *formatted_value;
+ char *raw_value;
+ char *type_name;
if (metadata == NULL)
return;
@@ -292,6 +291,7 @@ set_attribute_from_tagset (GFileInfo *i
raw, raw_value,
value-type, type_name,
NULL);
+
set_file_info (info,
attribute,
description,
@@ -303,6 +303,26 @@ set_attribute_from_tagset (GFileInfo *i
static void
+set_attribute_from_tagset (GFileInfo *info,
+ const char *attribute,
+ const char *tagset[])
+{
+ GObject *metadata;
+ int i;
+
+ metadata = NULL;
+ for (i = 0; tagset[i] != NULL; i++) {
+ metadata = g_file_info_get_attribute_object (info, tagset[i]);
+ if (metadata != NULL)
+ break;
+ }
+
+ if (metadata != NULL)
+ set_attribute_from_metadata (info, attribute, metadata);
+}
+
+
+static void
set_string_list_attribute_from_tagset (GFileInfo *info,
const char *attribute,
const char *tagset[])
@@ -336,9 +356,32 @@ set_string_list_attribute_from_tagset (G
static void
set_attributes_from_tagsets (GFileInfo *info)
{
- set_attribute_from_tagset (info, general::datetime, _DATE_TAG_NAMES);
Bug#593858: unblock: markupsafe/0.9.2-2
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: freeze-exception Please unblock package markupsafe 0.9.2-2 closes #591953 (+ some other minor packaging changes) unblock markupsafe/0.9.2-2 -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores) Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- Piotr Ożarowski Debian GNU/Linux Developer www.ozarowski.pl www.griffith.cc www.debian.org GPG Fingerprint: 1D2F A898 58DA AF62 1786 2DF7 AEF6 F1A2 A745 7645 signature.asc Description: Digital signature
Bug#593861: future unblock: xserver-xorg-video-openchrome/0.2.904+svn842-1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: freeze-exception Please unblock package xserver-xorg-video-openchrome I'm in the process of adopting the package, and was planning to upload to experimental only, but the previous maintainer Raphael Geissert suggested (see [1]) that I upload first the version he prepared which include some bug fix from upstream, and get a freeze exception for it. 1: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=583501#22 The current packaging is on debian's git [2], the only changes I plan on top of that are an update to the standards version (to 3.9.1, with no impact) and the changes needed to adopt it. 2: http://git.debian.org/?p=pkg-xorg/driver/xserver-xorg-video-openchrome.git Thanks, Julien Viard de Galbert unblock xserver-xorg-video-openchrome/0.2.904+svn842-1 -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores) Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100821170430.11970.1671.report...@scarabee.l-antre
Bug#593864: unblock: sqlalchemy/0.6.3-2
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: freeze-exception
Please unblock package sqlalchemy
it closes 591954 (RC bug)
unblock sqlalchemy/0.6.3-2
diff -u sqlalchemy-0.6.3/debian/control sqlalchemy-0.6.3/debian/control
--- sqlalchemy-0.6.3/debian/control
+++ sqlalchemy-0.6.3/debian/control
@@ -4,10 +4,10 @@
Maintainer: Piotr Ożarowski pi...@debian.org
Uploaders: Debian Python Modules Team
python-modules-t...@lists.alioth.debian.org
Build-Depends: debhelper (= 5.0.38),
- python-all-dev (= 2.6.5-2~), python3-all-dev (= 3.1.2-1~),
+ python-all-dev (= 2.6.5-2~), python3-all-dev (= 3.1.2-6~),
python-setuptools (= 0.6b3-1~), python3-setuptools
Build-Depends-Indep: python-sphinx (= 0.6), python-mako
-Standards-Version: 3.9.0
+Standards-Version: 3.9.1
Homepage: http://www.sqlalchemy.org/
Vcs-Svn: svn://svn.debian.org/python-modules/packages/sqlalchemy/trunk
Vcs-Browser:
http://svn.debian.org/viewsvn/python-modules/packages/sqlalchemy/trunk/
@@ -85,7 +85,7 @@
Package: python3-sqlalchemy
Architecture: all
-Depends: ${python:Depends}, ${misc:Depends}
+Depends: ${python3:Depends}, ${misc:Depends}
Suggests: python-sqlalchemy-doc
Description: SQL toolkit and Object Relational Mapper for Python 3
SQLAlchemy is an SQL database abstraction library for Python.
diff -u sqlalchemy-0.6.3/debian/changelog sqlalchemy-0.6.3/debian/changelog
--- sqlalchemy-0.6.3/debian/changelog
+++ sqlalchemy-0.6.3/debian/changelog
@@ -1,3 +1,11 @@
+sqlalchemy (0.6.3-2) unstable; urgency=low
+
+ * Use ${python3:Depends} in python3-sqlalchemy package (closes: 591954)
+- minimum python3-all-dev version bumped to 3.1.2-6~
+ * Standards-Version bumped to 3.9.1 (no changes needed)
+
+ -- Piotr Ożarowski pi...@debian.org Sat, 21 Aug 2010 19:05:08 +0200
+
sqlalchemy (0.6.3-1) unstable; urgency=low
* New upstream release
signature.asc
Description: Digital signature
please unblock whois 5.0.7
whois (5.0.7) unstable; urgency=medium * Added new IPv4 allocations. * Added the .xn--j6w193g (.香港, Hong Kong), .xn--kprw13d (.台湾, Taiwan) and .xn--kpry57d (.台灣, Taiwan) TLD servers. * Updated the .bd, .bo, .cm, .co, .cu, .dz, .gr, .hk, .lb, .ni, .rw, .tw and .tz TLD servers. -- Marco d'Itri m...@linux.it Mon, 09 Aug 2010 00:58:21 +0200 -- ciao, Marco signature.asc Description: Digital signature
Re: Please consider migrating gearman-interface 0.13.2-2 to testing
On Sat, 2010-08-21 at 09:17 -0700, Clint Byrum wrote: * debian/rules: moving tarball .c files out of the way so swig will rebuild and ship the .py files. (Closes: #593642) So far as I can see, this: [ -f python/libgearman.c.orig ] || [ -f python/libgearman.c ] mv -f python/libgearman.c python/libgearman.c.orig || true will attempt the mv if python/libgearman.c.orig exists but python/libgearman.c does not; was that intentional? * add description of gearman to long description (quiets lintian) * Removing unnecessary build depends on ruby/rubygems * Version build-dep on python3 * change python:Provides to python3:Provides * re-enable dh_usrlocal Why was the override added in the first place? * Added watch file 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/1282416347.26197.767.ca...@kaa.jungle.aubergine.my-net-space.net
Re: please unblock whois 5.0.7
On Sat, Aug 21, 2010 at 19:22:03 +0200, Marco d'Itri wrote: whois (5.0.7) unstable; urgency=medium Unblocked. Cheers, Julien signature.asc Description: Digital signature
jobs for website rebuilds of the release notes?
Hello, I've started working on release notes for squeeze, in preparation for being able to send out a call for upgrade tests, and according to Martin Michlmayr, these changes are being reflected already on http://www.debian.org/releases/lenny/releasenotes (though not propagated to all hosts bearing that name - I can't see the changes myself). So apparently there's a cronjob regenerating these pages from the release notes trunk. Does anyone know where that job is? Can I get access to it in order to get the lenny release notes generation pointed at the right branch, and to set up output for http://www.debian.org/releases/testing/releasenotes? Thanks, -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developerhttp://www.debian.org/ slanga...@ubuntu.com vor...@debian.org signature.asc Description: Digital signature
udeb unblock: partman-base [Re: udeb unblocks: netcfg, libdebian-installer]
On 08/21/2010 05:41 PM, Otavio Salvador wrote: Adam D. Barratt a...@adam-barratt.org.uk writes: busybox recently migrated to testing; this new version apparently has an incompatibility with the netcfg version currently in testing, so we were asked by Aurelien whether it would be possible to migrate netcfg as well. netcfg is on the cannot automatically migrate without approval udeb list and, in order to migrate it, the new version of libdebian-installer (which is also on the needs approval list) would also have to migrate at the same time. ack for netcfg and libdebian-installer. What about partman-base (and rescue which Christian kind of acked)? Cheers Luk -- 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/4c7039bc.30...@debian.org
Re: Bug#593627: java-common: please use openjdk as default jdk on powerpcspe
On Sat, Aug 21, 2010 at 04:13:34PM +0200, Niels Thykier wrote: Personally I am okay with doing it and it is the intention of the Java Team to make openjdk the default on all architectures. The question is if we should do it now or after Squeeze (CC'ed the release team) for their comments. I'd suggest after squeeze would probably be preferred. Thanks, Neil -- A. Because it breaks the logical sequence of discussion Q. Why is top posting bad? gpg key - http://www.halon.org.uk/pubkey.txt ; the.earth.li A40F862E -- 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/20100821203319.gh17...@halon.org.uk
Bug#593887: unblock: testng/5.11+dfsg-2
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: freeze-exception Please unblock testng. It fixes bug #593040 (RC, FTBFS: tests failed). unblock testng/5.11+dfsg-2 -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.35.2-melech+ (SMP w/2 CPU cores; PREEMPT) Locale: LANG=sv_SE.UTF-8, LC_CTYPE=sv_SE.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/20100821210550.23180.45843.report...@better.bindows.net
Re: udeb unblock: partman-base [Re: udeb unblocks: netcfg, libdebian-installer]
On 08/21/2010 10:40 PM, Luk Claes wrote: On 08/21/2010 05:41 PM, Otavio Salvador wrote: Adam D. Barratt a...@adam-barratt.org.uk writes: busybox recently migrated to testing; this new version apparently has an incompatibility with the netcfg version currently in testing, so we were asked by Aurelien whether it would be possible to migrate netcfg as well. netcfg is on the cannot automatically migrate without approval udeb list and, in order to migrate it, the new version of libdebian-installer (which is also on the needs approval list) would also have to migrate at the same time. ack for netcfg and libdebian-installer. What about partman-base (and rescue which Christian kind of acked)? Got an ack from otavio on IRC. Cheers Luk -- 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/4c704331.4010...@debian.org
Bug#593887: marked as done (unblock: testng/5.11+dfsg-2)
Your message dated Sat, 21 Aug 2010 22:28:20 +0100 with message-id 1282426101.26197.1747.ca...@kaa.jungle.aubergine.my-net-space.net and subject line Re: Bug#593887: unblock: testng/5.11+dfsg-2 has caused the Debian Bug report #593887, regarding unblock: testng/5.11+dfsg-2 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 593887: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=593887 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 testng. It fixes bug #593040 (RC, FTBFS: tests failed). unblock testng/5.11+dfsg-2 -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.35.2-melech+ (SMP w/2 CPU cores; PREEMPT) Locale: LANG=sv_SE.UTF-8, LC_CTYPE=sv_SE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash ---End Message--- ---BeginMessage--- On Sat, 2010-08-21 at 23:05 +0200, Marcus Better wrote: Please unblock testng. It fixes bug #593040 (RC, FTBFS: tests failed). Unblocked. Regards, Adam ---End Message---
nodejs 0.2.0 supported upstream as a stable version
Hi, the nodejs package has seen a lot of evolutions through the 0.1.x releases. As promised by upstream author Ryan Dahl, version 0.2 will be supported on its own branch, without API changes. Unfortunately it's been released after squeeze freeze, however i (with advice from my mentor Dave Beckett) think it would be much better if nodejs 0.2.0-1 was allowed to go into squeeze. I don't attach debdiff between 0.1.102-1 and 0.2.0-1, since the changes are only upstream changes. Kind regards, Jérémy Lal -- 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/4c70445d.9020...@edagames.com
Re: nodejs 0.2.0 supported upstream as a stable version
On Sat, Aug 21, 2010 at 23:25:49 +0200, Jérémy Lal wrote: I don't attach debdiff between 0.1.102-1 and 0.2.0-1, since the changes are only upstream changes. This doesn't follow. If you want us to consider the update, then please send the diff you're considering. Cheers, Julien signature.asc Description: Digital signature
strongswan update to 4.4.x
Dear release team, The 4.4.x upstream series of strongswan fixes many issues of the 4.3.x series which is currently in Squeeze. Unfortunately, due to real life constraints on my part coupled with upstream packaging changes that required a few tries to get right on the Debian package side, I didn't manage to update it in time for the freeze. However, many current strongswan users ask for a 4.4.x version in Squeeze, and I agree that this is much preferrable to the current version in testing. See e.g.: #506320: strongswan: include directives error and ikev2 #569550: strongswan: Please include attr plugin #593768: strongswan: 4.4.1 unavailable in testing notwhistanding a freeze- exception request Additional upstream changes in 4.4.0 include: * The ipsec pki utility, easing PKI/X.509 handling. * farp and dhcp plugins for better road-warrior integration into internal network services. Please add an exception for strongswan to allow 4.4.x into testing/Squeeze, as it greatly improves usability over the 4.3.x series. PS: An upload (hopefully) fixing the FTBFS (which never happened on my systems) is pending. I intend to upload on Monday after verifying another fix. best regards, Rene signature.asc Description: This is a digitally signed message part.
Re: Bug#387688: Add gnupg as apt dependency in Squeeze to be able to solve #387688 in Squeeze+1?
* Philipp Kern [2010-08-15 13:30 +0200]: On Fri, Aug 13, 2010 at 01:37:15AM +0200, Carsten Hey wrote: currently apt depends on debian-archive-keyring which depends on gnupg. It has been proposed to remove the latter dependency in #387688, this would save about 5 MB of disk space in a sid debootstrap. I'm still not sure if I buy this argument. After all it would leave the debootstrap without apt (which is the current default behaviour, I know). In the meantime apt has been added to base packages for debootstrap's buildd variant. How useful is this, really? My wording was not as clear as it should have been :) Neither apt's nor debian-archive-keyring's dependencies influence the size of a Debian chroot with only essential and build-essential packages installed. I was talking about a rather minimal Debian installation _with_ apt. Two examples for such installations are the chroot environments created by the debootstrap variants minbase and buildd. Let's look into this in more detail: Currently the Installed-Size: of apt and its non-Required: yes dependencies is 12,624 (6,904 + 5,720) kB: apt 5,244 libstdc++61,204 debian-archive-keyring 60 gpgv396 (required for verifying signatures) ¯ needed dependencies 6,904 gnupg 5,176 libusb-0.1-4 96 libreadline6356 readline-common 92 ¯ superfluous dependencies 5,720 By removing the (currently indirect) apt dependencies on gnupg and libusb-0.1-4 and making apt depend on gpgv (or gpgv | gpgv-tiny) instead, 5272 kB could be saved. There are ways to accomplish this for Squeeze+1, how it could be done seems to be nothing that needs to be discussed before Squeeze is released. To save additional 448 kB by removing the dependency on libreadline (of course not by default, but only if the user chooses this) there seem to be two ways: * Build a new package gpgv-tiny, configured with --without-readline. gpgv-tiny without gnupg-tiny would be pretty useless unless apt and debian-archive-keyring remove their gnupg dependency. If the gnupg maintainer decide to build gpgv-tiny, it should IMHO be done after apt's gnupg dependency has been removed. * Teach gpgv to dlopen() libreadline and use it only if it is available (suggested by Florian Weimer in #592902). Using dlopen would have obvious advantages, but this would require adding a patch to the Debian package unless it would be accepted upstream. As explained, the minimal disk usage of apt and its non-essential dependencies could be dropped easily from currently 12,624 to 6,904 kB. After Debian's possible future switch to Tdeps it would be 3,119 kB. There are ways to further reduce the disk usage of a nearly minimal Debian installation without requiring the user to do the work her/himself and without negatively influencing a non-minimal installation. Reducing disk usage about a half megabyte or two megabytes is not much, but many small reductions combined lead to significant less disk usage. An imaginary debootstrap variant 'tiny' that, e.g., would install debconf-english instead of debconf-l18n (this saves 1,516 kB) and gpgv-tiny instead of gpgv, that would not need to install gnupg and so on, could create such a minimal installation plus apt. This combined with the biggest saving of disk usage, having tdebs in Debian and not installing them, would lead to a rather small but usable Debian chroot. What's the use case? The obvious use cases are: * Installation on systems where disk space is limited. * People with slow or traffic limited internet connections would be happy to save traffic when they create a build chroot or similar. Being able to create small but usable Debian chroots could also lead to less obvious use cases being more reasonable than they are now. One possible example is creating an unstable chroot just to run a single program not available in stable. (Still your other remarks look sane, and AFAIK a dependency on gnupg has been committed into apt.) Yes, the dependency is already in experimental. Regards Carsten -- 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/20100821224613.ga28...@foghorn.stateful.de
Bug#593858: marked as done (unblock: markupsafe/0.9.2-2)
Your message dated Sun, 22 Aug 2010 00:16:34 +0100 with message-id 20100821231634.gw2...@radis.liafa.jussieu.fr and subject line Re: Bug#593858: unblock: markupsafe/0.9.2-2 has caused the Debian Bug report #593858, regarding unblock: markupsafe/0.9.2-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.) -- 593858: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=593858 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 markupsafe 0.9.2-2 closes #591953 (+ some other minor packaging changes) unblock markupsafe/0.9.2-2 -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores) Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- Piotr Ożarowski Debian GNU/Linux Developer www.ozarowski.pl www.griffith.cc www.debian.org GPG Fingerprint: 1D2F A898 58DA AF62 1786 2DF7 AEF6 F1A2 A745 7645 signature.asc Description: Digital signature ---End Message--- ---BeginMessage--- On Sat, Aug 21, 2010 at 18:59:21 +0200, Piotr Ożarowski wrote: 0.9.2-2 closes #591953 (+ some other minor packaging changes) unblock markupsafe/0.9.2-2 Unblocked. A bit weird to see no changes needed on the standards-version bump, when the previous line of the changelog is one that's requested by new policy. Also the description changes aren't mentioned in the changelog. Cheers, Julien signature.asc Description: Digital signature ---End Message---
Request for pre-approval of cyrus-sasl2 upload
Release Team, I would like to request pre-approval to upload cyrus-sasl2 (2.1.23.dfsg1-6) to sid, with the goal of having it migrate to squeeze. Please note that a very important point about this request is that the -6 package would have to pass through NEW. (Please see the attached diffstat and compressed diff for the gory details, as what follows is a narrative description of the situation.) This is the associated changelog entry: cyrus-sasl2 (2.1.23.dfsg1-6) unstable; urgency=low * Merge cyrus-sasl2 and cyrus-sasl2-heimdal source packages (Closes: #568358) + Build against new heimdal-multidev (Closes: #591147) * Properly detect presence of Heimdal (Closes: #590912); thanks tremendously to Russ Allbery for the patch Of the bug closures, #568358 is severity normal (but has significant positive security implications for the life of Squeeze), and then #591147 is severity grave and #590912 is severity serious. Additionally, #582040 (also severity grave) was closed in an NMU, but its propogation is being held up by the other two RC bugs. I will focus my comments on #568358 as the others are self explanatory. Several years ago, it was requested that version of the SASL GSSAPI modules compiled against the Heimdal Kerberos library be provided. At the time, the only modules available were compiled against MIT Kerberos. Users desiring Heimdal versions had to rebuild the package themselves. Part of the reason for that was that it was not possible to simultaneously install the Hiemdal and MIT Kerberos -dev packages, preventing the building of both sets of modules from a single source package. The solution at the time was to add a second source package (cyrus-sasl2-heimdal). This was less than optimal, but the only available option. This has resulted in some major annoyances: - Any upload of cyrus-sasl2 or cyrus-sasl2-heimdal must be accompanied by a source-ful upload of the other package, carrying the same source version (this impacts both NMUs and security uploads) - The debian/ directories must be manually kept in sync Today, thanks to the avilability of the heimdal-multidev and krb5-multidev packages, it is possible to have the MIT and Heimdal Kerberos -dev libraries concurrently installed. This makes it possible to build against both from within one source package. Merging the two source packages into one would eliminate both of these issues. Having both of these issues persist through the life of Squeeze would, IMHO, be a Bad Thing(TM). Regards, -Roberto -- Roberto C. Sánchez http://people.connexer.com/~roberto http://www.connexer.com cyrus-sasl2_consolidation.diff.gz Description: Binary data README.Debian-NMU | 11 -- changelog |9 + control | 29 + cyrus-sasl2-heimdal-dbg.postrm| 10 + cyrus-sasl2-heimdal-dbg.preinst | 10 + libsasl2-modules-gssapi-heimdal.dirs |2 libsasl2-modules-gssapi-heimdal.install |1 libsasl2-modules-gssapi-heimdal.lintian-overrides |2 patches/0024_allow_detection_of_heimdal.dpatch| 22 patches/00list|1 rules | 114 -- sample/Makefile |7 - 12 files changed, 172 insertions(+), 46 deletions(-) signature.asc Description: Digital signature
Freeze exception for llvm/2.6-9.1
Dear Release Team, I've uploaded a few days ago to DELAYED/5 a NMU of llvm (2.6-9.1) that should be granted a freeze exception. It fixes three bugs (incl. 2 RC) and a few Lintian/Piuparts checks. The last changelog entry is: llvm (2.6-9.1) unstable; urgency=low * Non-maintainer upload. * llvm-runtime: - replace Conflicts with previous version by Breaks - add explicit set -e in maintainer scripts - properly remove llvm.binfmt in prerm script * llvm-dev: - install vim files in /usr/share/vim/addons, add README.Debian (Closes: #593190) - add dependency to libffi-dev (Closes: #573368) * libllvm-ocaml-dev: - apply Sylvain Le Gall's patch to fix META filename (Closes: #583475) - add suggestion to ocaml-findlib * Add debian/source/format -- Stéphane Glondu glo...@debian.org Thu, 19 Aug 2010 18:53:44 +0200 The full diff is available at: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=593624 NB: The package has still 2 days to spend in the DELAYED queue. I'm not sure when this request should have been sent... Cheers, -- Stéphane -- 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/4c70abef.6070...@debian.org
