Bug#684961: unblock: rpm/4.10.0-5
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Please unblock package rpm, it includes single patch from Fedora to allow setup of Fedora 17 (and future Fedora 18 and RHEL7) chroots. This is really not a critical fix, but will improve compatibility with other Linux vendors. The only change in the package is adding this patch: http://anonscm.debian.org/gitweb/?p=collab-maint/rpm.git;a=blob;f=debian/patches/rpm-4.9.1.2-rpmlib-filesystem-check.patch Debdiff attached as well. unblock rpm/4.10.0-5 Thanks - -- Michal Čihař | http://cihar.com | http://blog.cihar.com - -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.1.10-1.16-desktop (SMP w/2 CPU cores; PREEMPT) Locale: LANG=cs_CZ.UTF-8, LC_CTYPE=cs_CZ.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCAAGBQJQK05dAAoJEGo39bHX+xdNQ3MP/i5fIRmrWfx1G6eb2Sje222G spLNiFH3wmXBCBzAcKluy9cEUoPIa7DihjXzD9r/UjeFVWndEVt7ZCAWtxAB8GcW jPfGboiOL/Bz4k/a5KSNusFWF+lsUjyFGKh72jaSpCtewZmjY2Cm+qVwgJo01dgl KaxOKY4Hz4TFHs5XkLuDTY7gYTI0HZ/0ukaaQU/KVQ+AcYxhAY339sotDHsABQy6 AS3fnbq4v3suXglo8J/g1+0ejCk/J47KhoiKKK80YDHOUlIbFmpmUNaXnJ0JHU0D lQN+T2PrAXSnQZ4gLfT/sKXgvykWBFIKZXUdmCzQCA4cU05MlLVhoapQfUIGZP8M Wwk1v+2XxxDJB2bHEHPNCs99P4BfeG/GPSELtXFAnYFqs53BFzfdUOygNM3YgyDS w3sAyQgAKtrNlFvOrWmyutlxYQo0qpmED8jTEjz/oWhhChrEB37Pq9LM/DfBfjEK rvT6AeOiuO+tNhpU7YUakof9DOKxnx6v68OgPz6QLIg5K7K1WzdHe364OEoL67Ua E1cKMyf0pN0AK4UlE/2nhHRODGNOoFdNsyjOuxmBQ3eMrll55SA9z490Ug3ZXktS KkYJquPjFJLM7Yhk7L13I1Xuue161qG3VyR5C2wSEU4H1ZJpwDwN/4x33+D4DxtE B9X0vRcBJdCY/TGx5FXW =tcWN -END PGP SIGNATURE- diff -Nru rpm-4.10.0/debian/changelog rpm-4.10.0/debian/changelog --- rpm-4.10.0/debian/changelog 2012-06-25 14:29:22.0 +0200 +++ rpm-4.10.0/debian/changelog 2012-08-15 09:05:37.0 +0200 @@ -1,3 +1,10 @@ +rpm (4.10.0-5) unstable; urgency=low + + * Added patch from Fedora to support X-CheckUnifiedSystemdir +(Closes: #683759). + + -- Michal Čihař ni...@debian.org Wed, 15 Aug 2012 09:05:26 +0200 + rpm (4.10.0-4) unstable; urgency=low * Lower librpm - rpm-common dependency to recommends as there actually diff -Nru rpm-4.10.0/debian/patches/rpm-4.9.1.2-rpmlib-filesystem-check.patch rpm-4.10.0/debian/patches/rpm-4.9.1.2-rpmlib-filesystem-check.patch --- rpm-4.10.0/debian/patches/rpm-4.9.1.2-rpmlib-filesystem-check.patch 1970-01-01 01:00:00.0 +0100 +++ rpm-4.10.0/debian/patches/rpm-4.9.1.2-rpmlib-filesystem-check.patch 2012-08-15 09:05:37.0 +0200 @@ -0,0 +1,128 @@ +Description: Add Fedora compatible rpm builtin provides +Origin: vendor, http://pkgs.fedoraproject.org/cgit/rpm.git/plain/rpm-4.9.1.2-rpmlib-filesystem-check.patch +Forwarded: not-needed +--- a/lib/depends.c b/lib/depends.c +@@ -459,6 +459,108 @@ + return rc; + } + ++/* ++ * Temporary support for live-conversion of the filesystem hierarchy ++ * mailto: k...@redhat.com, har...@redhat.com ++ * https://fedoraproject.org/wiki/Features/UsrMove ++ * ++ * X-CheckUnifiedSystemdir: ++ * /bin, /sbin, /lib, /lib64 -- /usr ++ * ++ * X-CheckUnifiedBindir: ++ * /usr/sbin - /usr/bin ++ * ++ * X-CheckMultiArchLibdir: ++ * /usr/lib64 /usr/lib/platform tuple (e.g. x86_64-linux-gnu) ++ * ++ * This code is not needed for new installations, it can be removed after ++ * updates from older systems are no longer supported: Fedora 19 / RHEL 8. ++ */ ++ ++static int CheckLink(const char *dir, const char *root) ++{ ++char *d = NULL; ++struct stat sbuf; ++int rc = 0; ++ ++if (!root) ++ root = /; ++ ++rasprintf(d, %s%s, root, dir); ++if (!d) { ++ rc = -1; ++ goto exit; ++} ++ ++/* directory or symlink does not exist, all is fine */ ++if (lstat(d, sbuf) 0) { ++ rc = 1; ++ goto exit; ++} ++ ++/* if it is a symlink, all is fine */ ++if (S_ISLNK(sbuf.st_mode)) ++ rc = 1; ++ ++exit: ++free(d); ++return rc; ++} ++ ++static int CheckFilesystemHierarchy(rpmds * dsp, const char *root) ++{ ++static const char *dirs[] = { bin, sbin, lib, lib64 }; ++int check; ++int i; ++rpmds ds; ++int rc = 0; ++ ++for (i = 0; i sizeof(dirs) / sizeof(dirs[0]); i++) { ++ check = CheckLink(dirs[i], root); ++ if (check 0) { ++ rc = -1; ++ goto exit; ++ } ++ ++ if (check == 0) ++ goto exit; ++} ++ds = rpmdsSingle(RPMTAG_PROVIDENAME, ++ rpmlib(X-CheckUnifiedSystemdir), 1, ++ RPMSENSE_EQUAL); ++rpmdsMerge(dsp, ds); ++rpmdsFree(ds); ++ ++check = CheckLink(usr/lib64, root); ++if (check 0) { ++rc = -1; ++goto exit; ++} ++if (check 0) { ++ ds = rpmdsSingle(RPMTAG_PROVIDENAME, ++ rpmlib(X-CheckMultiArchLibdir), 1, ++ RPMSENSE_EQUAL); ++ rpmdsMerge(dsp,
Bug#683976: marked as done (unblock: libpgjava/9.1-901-2)
Your message dated Wed, 15 Aug 2012 09:47:19 +0200 with message-id 502b5407.6020...@thykier.net and subject line Re: Bug#683976: unblock: libpgjava/9.1-901-2 has caused the Debian Bug report #683976, regarding unblock: libpgjava/9.1-901-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.) -- 683976: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=683976 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 libpgjava Version 9.1-901-2 has been uploaded to unstable to address bug #659324 by providing transitional packages. These transitional packages are needed in Wheezy to support upgrading since the binary packages have been renamed. A full debdiff is provided below. Note that the new version is currently (as of 5th August 2012) in the new queue, due to the new binary packages. Thanks, Andy unblock libpgjava/9.1-901-2 debdiff libpgjava_9.1-901-1.dsc libpgjava_9.1-901-2.dsc diff -Nru libpgjava-9.1-901/debian/changelog libpgjava-9.1-901/debian/changelog --- libpgjava-9.1-901/debian/changelog 2012-01-03 22:46:10.0 + +++ libpgjava-9.1-901/debian/changelog 2012-07-30 22:55:34.0 +0100 @@ -1,3 +1,10 @@ +libpgjava (9.1-901-2) unstable; urgency=low + + * Provide transitional package libpg-java (closes: #659324) + * Bump standards version to 3.9.3 (no changes). + + -- Andrew Ross ubu...@rossfamily.co.uk Fri, 20 Jul 2012 21:09:40 -0400 + libpgjava (9.1-901-1) unstable; urgency=low * New upstream release. (closes: #645854) diff -Nru libpgjava-9.1-901/debian/control libpgjava-9.1-901/debian/control --- libpgjava-9.1-901/debian/control2012-01-06 17:56:16.0 + +++ libpgjava-9.1-901/debian/control2012-07-21 15:20:17.0 +0100 @@ -6,7 +6,7 @@ Andrew Ross ubu...@rossfamily.co.uk Build-Depends: debhelper (= 7.0.50~), java-gcj-compat-dev, ant, javahelper (=0.32~) Build-Depends-Indep: libxerces2-java, default-jdk, default-jdk-doc -Standards-Version: 3.9.2 +Standards-Version: 3.9.3 Vcs-Svn: svn://svn.debian.org/svn/pkg-java/trunk/libpgjava Vcs-Browser: http://svn.debian.org/wsvn/pkg-java/trunk/libpgjava Homepage: http://jdbc.postgresql.org/ @@ -16,9 +16,9 @@ Depends: ${java:Depends}, ${misc:Depends} Recommends: ${java:Recommends} Suggests: postgresql (= 8.2) -Conflicts: libpgjava (= 7.4.7-3), libpg-java (= 8.4-702-1) +Conflicts: libpgjava (= 7.4.7-3), libpg-java (= 9.1-901-1) Provides: libpgjava, libpg-java -Replaces: libpgjava, libpg-java +Replaces: libpgjava, libpg-java (= 9.1-901-1) Description: Java database (JDBC) driver for PostgreSQL Java classes for communication with the PostgreSQL 7.2 up to 9.1 database backend (local or remote) using JDBC. This package contains two Java archives @@ -40,3 +40,13 @@ supports JDBC 4.0 and SSL (for JDK 1.6 and up). . This package contains the documentation. + +Package: libpg-java +Architecture: all +Section: oldlibs +Priority: extra +Depends: libpostgresql-jdbc-java, ${misc:Depends} +Description: Transitional package for libpostgresql-jdbc-java + This is a transitional package for libpg-java, and can be safely removed + after the installation is complete. + ---End Message--- ---BeginMessage--- On 2012-08-14 22:24, Andrew Ross wrote: On 11/08/12 13:18, Niels Thykier wrote: On 2012-08-05 23:48, Andrew Ross wrote: Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package libpgjava Version 9.1-901-2 has been uploaded to unstable to address bug #659324 by providing transitional packages. These transitional packages are needed in Wheezy to support upgrading since the binary packages have been renamed. A full debdiff is provided below. Note that the new version is currently (as of 5th August 2012) in the new queue, due to the new binary packages. Thanks, Andy unblock libpgjava/9.1-901-2 [...] Seems fine at first glance; please let us know when it has been accepted. ~Niels OK, it's been accepted now and is in the pool. Thanks, Andy Unblocked, thanks. ~Niels---End Message---
Bug#683344: unblock: cciss-vol-status/1.09-3
On 2012-07-31 00:16, Christian Hofstaedtler wrote: Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package cciss-vol-status The version in sid adds new hardware support (and closes #680310 for this), which I was only made aware of after the freeze. (The build process now also uses dpkg-buildflags.) unblock cciss-vol-status/1.09-3 Thank you, -ch Hi, debhelper compat 9 bumps are generally not accepted post freeze. If hardening flags is important for this package, consider using dpkg-buildflags directly or possibly /usr/share/dpkg/buildflags.mk... ~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/502b5923.4030...@thykier.net
Bug#684963: unblock: bouncycastle/1.44+dfsg-3.1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 During recent rebuilt testing in wheezy, FTBFS where recorded for wagon2 (#684841), jenkins (#684826), jenkins-ssh-cli-auth (#684829) and jenkins-instance-identity (#684815). The root cause of this issue is that the version of bouncycastle in testing does not include maven artifacts; this is included in the version in unstable (from 1.44+dfsg-3 onwards) but due to a new upstream release (1.46) which only builds for Java 6+ this addition has never migrated to testing due to build failures on archs which don't use openjdk (kfreebsd-* and hurd-i386). I'd like permission to target an upload of 1.44+dfsg-3 direct to testing to resolve this issue - debdiff attached. unblock bouncycastle/1.44+dfsg-3.1 - -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.5.0-10-generic (SMP w/8 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCAAGBQJQK1nCAAoJEL/srsug59jDiakP/3sNfhJnNdER7htrx7BxkEHz hQe0T82aB4+otTaE7hTjtvHT9ynd6u7WOTdywkQa07cUONE3mBY5M7EMux8Udoiz rrhZjjj+z0Nzs9UZkr7aoR+mmtjnYzsYVIzWG4TGcXS87HOiC58XrI15xs/RTiBE eva36tGCsen8jN9I4ZzUZ5bjPAgHa0F7nRDgMRuGzikbbF1UTdiN+9OGSiWFTVya mlJ5Ci3RXABg9kgVFXXqsMek5a12FKNC6Bc2aRDu9spRa/3oY560kjB+m+1E1it7 o6HQnh07aHnHYexmoN1JVOYak8yU9hex7GP036iKlHI8hVTSA8KnPHhghB3v7p3u XwLbEU6HKAD5s7p1983tH9PUHrfEZsfW0h05z8rb8gTUqRbBemglZpynUsXirvMr FNMhBuBKqnUFOrAmOFVDs1J4pxiVktdxRyUdQMR2deyADlcJCRtf0xfkzxaJl6Wy xndJX7sb7jE2Eq7gvQF09l0pJ4OUx5jy6T//jmWxzIUkrGWR+MFqRGzEdAxnvvDm qdTIR370iRFBXWlWir7LsPLzuTQTmlLb/KHXj6/byP8FyuzeNq0ZehLclgqiss0y 5qU8h7Sj3XrANmdZC/aavK0z9Bwgp+kiiRT8CybNOBE6eS2MAauT7FtvNFTcCcm2 RDaLTla9lZ40ZAEvsI0u =whjC -END PGP SIGNATURE- diff -u bouncycastle-1.44+dfsg/debian/rules bouncycastle-1.44+dfsg/debian/rules --- bouncycastle-1.44+dfsg/debian/rules +++ bouncycastle-1.44+dfsg/debian/rules @@ -32,7 +32,8 @@ # bcprov binary-install/libbcprov-java:: build/libbcprov-java - install -m 644 $(builddir)/jars/bcprov-jdk14-*.jar debian/libbcprov-java/usr/share/java/bcprov.jar + mh_installpoms -plibbcprov-java + mh_installjar -plibbcprov-java -l debian/poms/bcprov.pom $(builddir)/jars/bcprov-jdk14-*.jar ln -sf ../bcprov.jar debian/libbcprov-java/usr/share/java/gcj-endorsed/bcprov.jar touch debian/libbcprov-java/etc/java/security/security.d/2000-org.bouncycastle.jce.provider.BouncyCastleProvider binary-install/libbcprov-java-doc:: @@ -40,19 +41,22 @@ # bcmail binary-install/libbcmail-java:: build/libbcmail-java - install -m 644 $(builddir)/jars/bcmail-jdk14-*.jar debian/libbcmail-java/usr/share/java/bcmail.jar + mh_installpoms -plibbcmail-java + mh_installjar -plibbcmail-java -l debian/poms/bcmail.pom $(builddir)/jars/bcmail-jdk14-*.jar binary-install/libbcmail-java-doc:: mv -i $(builddir)/javadoc/bcmail debian/libbcmail-java-doc/usr/share/doc/libbcmail-java-doc/api # bcpg binary-install/libbcpg-java:: build/libbcpg-java - install -m 644 $(builddir)/jars/bcpg-jdk14-*.jar debian/libbcpg-java/usr/share/java/bcpg.jar + mh_installpoms -plibbcpg-java + mh_installjar -plibbcpg-java -l debian/poms/bcpg.pom $(builddir)/jars/bcpg-jdk14-*.jar binary-install/libbcpg-java-doc:: mv -i $(builddir)/javadoc/bcpg debian/libbcpg-java-doc/usr/share/doc/libbcpg-java-doc/api # bctsp binary-install/libbctsp-java:: build/libbctsp-java - install -m 644 $(builddir)/jars/bctsp-jdk14-*.jar debian/libbctsp-java/usr/share/java/bctsp.jar + mh_installpoms -plibbctsp-java + mh_installjar -plibbctsp-java -l debian/poms/bctsp.pom $(builddir)/jars/bctsp-jdk14-*.jar binary-install/libbctsp-java-doc:: mv -i $(builddir)/javadoc/bctsp debian/libbctsp-java-doc/usr/share/doc/libbctsp-java-doc/api @@ -90,0 +95,11 @@ + +POMS=bcprov bcpg bcmail bctsp +UPSTREAM_VERSION=$(shell dpkg-parsechangelog | sed -rne 's,^Version: ([^-]+).*,\1,p' | sed 's/\+dfsg//') + +get-orig-pom: + mkdir -p debian/poms + for pom in $(POMS); do \ + wget -O debian/poms/$${pom}.pom -U NoAgent-1.0 \ + http://repo1.maven.org/maven2/org/bouncycastle/$${pom}-jdk14/$(UPSTREAM_VERSION)/$${pom}-jdk14-$(UPSTREAM_VERSION).pom ; \ + done ; + diff -u bouncycastle-1.44+dfsg/debian/changelog bouncycastle-1.44+dfsg/debian/changelog --- bouncycastle-1.44+dfsg/debian/changelog +++ bouncycastle-1.44+dfsg/debian/changelog @@ -1,3 +1,28 @@ +bouncycastle (1.44+dfsg-3.1) testing; urgency=low + + * Target upload for testing to enable maven artifacts and fix up +FTBFS in a number of other rbd's. + + -- James Page james.p...@ubuntu.com Wed, 15 Aug 2012 08:59:20 +0100 + +bouncycastle (1.44+dfsg-3) unstable; urgency=low + + * Team upload. + + [Niels Thykier] + * Changed the section of the gcj packages to java. + * Replaced B-D on default-jdk-builddep with
Bug#683367: unblock: ffgtk/0.8.1-2
Control: tags -1 moreinfo On 2012-07-31 08:53, Rolf Leggewie wrote: 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. This package appear to be brand new? If so, it is too late for Wheezy. Sorry, ~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/502b5a7c.4050...@thykier.net
Processed: Re: Bug#683367: unblock: ffgtk/0.8.1-2
Processing control commands: tags -1 moreinfo Bug #683367 [release.debian.org] unblock: ffgtk/0.8.1-2 Added tag(s) moreinfo. -- 683367: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=683367 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.b683367.134501850518630.transcr...@bugs.debian.org
Re: [Pkg-ia32-libs-maintainers] Bug#679671: ia32-libs-i386: depends on removed package libdb4.8
On 2012-07-31 11:02, Niels Thykier wrote: 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). [...] 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. mtink is in testing, cyrus-sasl2 is fixed in sid with an unblock. lesstif2 does not have an unblock, but assuming it got one, it could migrate with the next Britney run. [...] 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 [...] I would still like to get an idea of what needs the last packages unfixed packages. Having reviewed some of the bugs, I realized that some of them have no patches, liborbit2 seems to invovle plugins that will most likely entangle unrelated packages, at least libbonobo has an unanswered interesting question... ~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/502b62a7.2070...@thykier.net
Re: Request for update of package capi4hylafax
On 2012-08-14 09:30, Joachim Wiedorn wrote: Hallo, I took over the package capi4hylafax a very short time before freeze and my first package still need some fixes. Could you please allow updating the package in testing? Compared with version 01.03.00.99.svn.300-17 (in testing) the updated package have this changes: capi4hylafax (1:01.03.00.99.svn.300-18) unstable; urgency=low * Add postinst script to update logfile name and path in /etc/hylafax/config.faxCAPI. Closes: #647164 * Fix udev warning: create symlink /dev/faxCAPI with init script and remove udev rules file. Closes: #684741 * Only suggest contrib package isdnactivecards. Closes: #682135 -- Joachim Wiedorn ad_deb...@joonet.de Mon, 13 Aug 2012 17:57:37 +0200 I know these are all normal bugs, but especially the problem with the logfile (#647164) should be solved, because on small systems this could induce to full harddisk partition. So this bugfix would be important for all users in the next stable Wheezy. The other both bugs give always irritating warnings to users and should also be solved. I would be very appreciated if you allow this update. --- Have a nice day. Joachim (Germany) Hi, We would need to see the source debdiff between the current version in testing and the one you are proposed (which does not appear to be in unstable) before we can determine if the changes are reasonable. I'd personally recommend that you filed an unblock with the debdiff as bugs are easier for us to keep track of (remember to mention you want a pre-upload approval else the reviewer will get confused). ~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/502b6965.6070...@thykier.net
Processed: Re: Bug#681864: unblock: telepathy-mission-control-5/1:5.12.1-2
Processing commands for cont...@bugs.debian.org: # Upload accepted on 2012-08-10 retitle 681864 unblock: telepathy-mission-control-5/1:5.12.1-2 Bug #681864 [release.debian.org] unblock (pre-approval): telepathy-mission-control-5/1:5.12.1-2 Changed Bug title to 'unblock: telepathy-mission-control-5/1:5.12.1-2' from 'unblock (pre-approval): telepathy-mission-control-5/1:5.12.1-2' thanks Stopping processing here. Please contact me if you need assistance. -- 681864: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=681864 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.134502254916103.transcr...@bugs.debian.org
Bug#681864: unblock: telepathy-mission-control-5/1:5.12.1-2
# Upload accepted on 2012-08-10 retitle 681864 unblock: telepathy-mission-control-5/1:5.12.1-2 thanks On Tue, 17 Jul 2012 at 12:02:32 +0200, Laurent Bigonville wrote: Fixes: • Stop using deprecated telepathy-glib symbols. (Jonny) This is not needed, but is reverted by the patch that Laurent added before uploading. • fdo#51842 - fix access to freed memory. (Xavier) This is Debian bug #683151, telepathy-mission-control-5: Random crashes due to access to freed memory, severity serious. It's the change to src/mcd-account-manager-default.c. • fix existing channel dispatching after using present/delegate. (Jonny) In particular this fixes the handover of IM conversations between Empathy and GNOME Shell (Debian bug #683565, which I've just upgraded to important). The changes in src/mcd-dispatcher.c fix this; the changes to tests/ extend a regression test to simulate more interactions between Empathy and Shell. I attach a hopefully-easier-to-read diff, between the version currently in wheezy and the version in sid, after the debian/patches are applied (i.e. what actually gets compiled), and excluding files generated by Autotools, pre-generated documentation and the patch in debian/patches itself. Of the excluded files, config.guess, config.sub and doc/.../html are regenerated during the build. Commands used to generate this diff: apt-get source telepathy-mission-control-5=1:5.12.0-2 apt-get source telepathy-mission-control-5=1:5.12.1-2 diff -Nur telepathy-mission-control-5-5.12.{0,1} | filterdiff -p1 \ -x .pc/\* \ -x config.guess -x config.sub -x INSTALL -x configure -x depcomp \ -x missing -x install-sh -x ltmain.sh \ -x debian/patches/\*.patch \ -x doc/reference/mission-control-plugins/html/\* \ filtered.diff Regards, S diff -Nur telepathy-mission-control-5-5.12.0/ChangeLog telepathy-mission-control-5-5.12.1/ChangeLog --- telepathy-mission-control-5-5.12.0/ChangeLog 2012-04-02 23:55:00.0 +0100 +++ telepathy-mission-control-5-5.12.1/ChangeLog 2012-07-11 11:56:17.0 +0100 @@ -1,3 +1,85 @@ +commit e824493e533f7c4ea9ae9066fb29b3298d9a8aa8 +Author: Xavier Claessens xavier.claess...@collabora.co.uk +Date: 2012-07-11 12:49:04 +0200 + +Prepare 5.12.1 release + +commit 57d7c6360f04d8bc65320c42a5d8929fa3e3bc25 +Author: Xavier Claessens xavier.claess...@collabora.co.uk +Date: 2012-07-11 12:14:11 +0200 + +Copy telepathy.am from telepathy-glib + +It make sure make -j3 maintainer-foo works + +commit 0daa22ca3858138aee10f8bf46a07fd15c1fcf49 +Author: Xavier Claessens xavier.claess...@collabora.co.uk +Date: 2012-07-09 12:35:01 +0200 + +McdAccountManagerDefault: Fix a possible double free + +If the account is already in the hashtable, g_hash_table_insert() +will set @removed as value, but free it since the key already in +the table is kept. + +https://bugs.freedesktop.org/show_bug.cgi?id=51842 + +commit 150c89d45c6b7d5a2d10bc36cff5689ea1ca72d8 +Author: Will Thompson will.thomp...@collabora.co.uk +Date: 2012-04-05 17:10:18 +0100 + +dispatch test: make sure Ensure-ing channels after delegation/presenting works + +commit 54f4fd22c09a342bb58da978b5a055e45f968897 +Author: Jonny Lamb jonny.l...@collabora.co.uk +Date: 2012-07-06 16:50:08 +0100 + +dispatcher: set channel state back to DISPATCHED after delegating presenting + +_mcd_client_proxy_handle_channels sets the McdChannel state to +HANDLER_INVOKED, but when we were calling this in both delegate and +present operations, the state was not being set back to the DISPATCHED +state afterwards. + +The state being wrong meant that dispatching a channel after if had +been delegated or presented would not happen, as MC thought we were +still waiting for a handler response. + +Signed-off-by: Jonny Lamb jonny.l...@collabora.co.uk + +commit c8ae24ffd03297d097b553997eda3807f1505748 +Author: Jonny Lamb jonny.l...@collabora.co.uk +Date: 2012-07-06 16:49:55 +0100 + +dispatcher: add more debug output when delegating channels + +Signed-off-by: Jonny Lamb jonny.l...@collabora.co.uk + +commit 3d35096f9ccc69b8c3067ed85102694eda4a2855 +Author: Will Thompson will.thomp...@collabora.co.uk +Date: 2012-04-05 16:56:35 +0100 + +Modernize dispatcher/redispatch-channels.py a little + +commit 88642511bb9c6f66d2fe4aae1550893eb0d781b2 +Author: Jonny Lamb jonny.l...@collabora.co.uk +Date: 2012-04-03 11:13:55 -0400 + +stop using deprecated tp-glib functions + +tp_*_call_when_ready were replaced by tp_proxy_prepare_async a while +ago. + +Signed-off-by: Jonny Lamb jonny.l...@collabora.co.uk + +commit edd10ce2948b29859006ca1e149e68097a3bd21b +Author: Jonny Lamb jonny.l...@collabora.co.uk +Date: 2012-04-02 18:58:07 -0400 + +start working on version 5.12.1 + +Signed-off-by: Jonny Lamb jonny.l...@collabora.co.uk + commit aeba9f785227e07bf26b14822b1b288041297910 Author:
Bug#684414: unblock (pre-approval): libspectre/0.2.7-1
On 2012-08-09 20:12, Pino Toscano wrote: Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: freeze-exception Hi, yesterday a new bugfix version of libspectre, 0.2.7, has been released. This version quite small in the actual changes it brings, while fixing a couple of issues. [...] The changes are the following: - configure.ac, libspectre/spectre-version.h: bump the version to 0.2.7 - libspectre/Makefile.am, test/Makefile.am: fix the automake build system to handle own CFLAGS properly and not ignore user-specified ones (like the Debian ones) - libspectre/ps.c as written in NEWS, fixes two crashes than can happen when %%Pages: or %%Page: comments are missing in the document or when %%Pages: comment is present but it's invalid. On the Debian side, other than the usual new upstream release, I would need to just add export V=1 in debian/rules to have the build system output the compilation commands used. I think it should be mostly harmless overall for wheezy, hence I'm asking for a pre-approval (and then unblock) before uploading it to unstable. Thanks, Sounds fine with me. Please go ahead and let us know when it has been accepted in sid. ~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/502b6ab9.8010...@thykier.net
Processed: Re: Bug#684910: unblock: fcitx/1:4.2.4.1-4
Processing control commands: tags -1 moreinfo Bug #684910 [release.debian.org] unblock: fcitx/1:4.2.4.1-4 Added tag(s) moreinfo. -- 684910: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684910 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.b684910.134502295418367.transcr...@bugs.debian.org
Bug#684910: unblock: fcitx/1:4.2.4.1-4
Control: tags -1 moreinfo On 2012-08-14 17:49, Aron Xu wrote: Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock fcitx/1:4.2.4.1-4. This version fixes a crash when loading input method wrappers that does not specify an icon of it. Also we are moving the keyboard module (fcitx-keyboard.so) from fcitx-module-x11 to the general fcitx-modules as it does provide some useful features when there is no X, as fcitx-module-x11 depends on fcitx-modules, such move would not cause breakage. You are moving files between two coinstallable packages with no Breaks/Replaces? That smells like it will break on upgrades... ~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/502b6be3.7080...@thykier.net
Allow ocfs2-tools 1.6.4-2 into wheezy
Dear release team, I have uploaded a new revision of ocfs2-tools to unstable which fixes bug #682517 (inability to launch the ocfs2console GUI): http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=682517 The fix (thanks Sébastien Villemot) is straight-forward: drop a bad Debian/Ubuntu specific patch, as can be seen from the attached debdiff. Could you please let this new version migrate into wheezy? Thanks, Jeremy diff -Nru ocfs2-tools-1.6.4/debian/changelog ocfs2-tools-1.6.4/debian/changelog --- ocfs2-tools-1.6.4/debian/changelog 2012-04-18 09:16:36.0 +0200 +++ ocfs2-tools-1.6.4/debian/changelog 2012-08-15 09:32:32.0 +0200 @@ -1,3 +1,10 @@ +ocfs2-tools (1.6.4-2) unstable; urgency=low + + * Remove popen2-ignore-depreciation-warn.patch: it has the opposite effect, +turning deprecation warnings into errors (Closes: #682517, LP: #923754). + + -- Jeremy Lainé jeremy.la...@m4x.org Wed, 15 Aug 2012 09:31:09 +0200 + ocfs2-tools (1.6.4-1) unstable; urgency=low * New upstream release. Closes: #669023. diff -Nru ocfs2-tools-1.6.4/debian/patches/popen2-ignore-depreciation-warn.patch ocfs2-tools-1.6.4/debian/patches/popen2-ignore-depreciation-warn.patch --- ocfs2-tools-1.6.4/debian/patches/popen2-ignore-depreciation-warn.patch 2011-03-25 16:48:30.0 +0100 +++ ocfs2-tools-1.6.4/debian/patches/popen2-ignore-depreciation-warn.patch 1970-01-01 01:00:00.0 +0100 @@ -1,18 +0,0 @@ -Description: Ignore the depreciation warning that popen2 will raise when it is imported. - Pending conversion to subprocess module. -Author: Dave Walker (Daviey) davewal...@ubuntu.com -Bug: https://launchpad.net/bugs/655548 a/ocfs2console/ocfs2console -+++ b/ocfs2console/ocfs2console -@@ -13,6 +13,11 @@ - # - import warnings - warnings.filterwarnings(error) -+ -+# Ignore the depreciation warning that popen2 will raise when it is imported. -+# FIXME: Pending conversion to subprocess module. -+warnings.simplefilter(ignore, DeprecationWarning) -+ - try: - import gtk - except Exception, e: diff -Nru ocfs2-tools-1.6.4/debian/patches/series ocfs2-tools-1.6.4/debian/patches/series --- ocfs2-tools-1.6.4/debian/patches/series 2012-04-18 09:02:42.0 +0200 +++ ocfs2-tools-1.6.4/debian/patches/series 2012-08-15 09:41:00.0 +0200 @@ -5,7 +5,6 @@ shorten-manpage-lines.patch ld-no-add-needed.diff ld-as-needed.diff -popen2-ignore-depreciation-warn.patch ocfs2-controld-pcmk-id.patch format-security.patch ocfs2-controld-headers.patch
Bug#684975: unblock: dokuwiki/dokuwiki_0.0.20120125b-1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Please unblock package dokuwiki Current version in testing 0.0.20120125a-1 has a security flaw #683378. There is a new upstream version, 0.0.20120125b, which fixes this and only this. I am not convinced that this fits into the release policy, since it does not fix an RC bug, only a security one. Additionally, it consists in a new upstream version, which adds to this uncertainty regarding the policy. For this reason I have not uploaded it to unstable yet. Attached it a debdiff of the updated package, please advice. unblock dokuwiki/dokuwiki_0.0.20120125b-1 Regards, - -- Tanguy Ortolo -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCgAGBQJQK3WjAAoJEOryzVHFAGgZIZcQAI2FAkfA1VfwMayzJeOMwmye asHVV2eTQq4IeNyGnAMoV+lBbT6RwTxgnH7IwJWQcasWe3J47lmkRVDgi6mk/Eq9 +pk0qLuQQP1pte56flth0vrBhZ/1XCg2YVSFLLhoUSBwtxg5EPL1BjL8MFCU7ba3 4k22TFhLGZLK1tqH9r/o5Nh9xdmoE6mldKSBkmDhZqd8BoFdvVd5RmwcdtpmYpCw 9+ywAE61gj1DTg7m/4SzRtfrJ0rh+9cKVveNc08SsvG1hlcw/qJWlCcbDwagkrwF 9rZ3vGjZV87sSpR2SBdJQz9SswcArKm7r2YUqQ6I1dNvKu7UkX3T6E13MQJa/pZ3 LxhEV8ITREyvAU1/0+vLSjxpa66hUx/pMwuobIHrSkAd7XWlEptnu2g+uLrDHcd/ vInKyCQq83K3OsKsf3c3wVPdWQRwOaYnFOci4t1ud0g8swhPpUaAHKZTKUb74Wmd AbD3x7t7EgFZb+OkthHUyW8Hm0g9Rr9+zFoh56OcCmJlz8FJQVRD3L5cb4cs/6UN 1WssfA0+BFe/vNT6qEeceUNuSAOa8yfTflm4N8FVv7kX7q7KQ80HxP75yJ4HKGh9 Q2FAz55N05Z0SeiQhnQi6rODZaEmauWn/oDjOvI8kr4i3uVwhp975egM+g1j2CIr aJ9tF4198Bh2hwFRwsY0 =w/oh -END PGP SIGNATURE- diff -Nru dokuwiki-0.0.20120125a/debian/changelog dokuwiki-0.0.20120125b/debian/changelog --- dokuwiki-0.0.20120125a/debian/changelog 2012-05-05 14:28:26.0 +0200 +++ dokuwiki-0.0.20120125b/debian/changelog 2012-08-15 11:59:25.0 +0200 @@ -1,3 +1,11 @@ +dokuwiki (0.0.20120125b-1) unstable; urgency=high + + * New upstream bugfix release: sanitize a POST parameter that could be used +to inject artitrary HTML and JavaScript, leading to an XSS vulnerability. +(CVE-2012-0283) (Closes: #683378) + + -- Tanguy Ortolo tanguy+deb...@ortolo.eu Wed, 15 Aug 2012 11:46:36 +0200 + dokuwiki (0.0.20120125a-1) unstable; urgency=high * New upstream bugfix release: properly escape an error messages that could diff -Nru dokuwiki-0.0.20120125a/doku.php dokuwiki-0.0.20120125b/doku.php --- dokuwiki-0.0.20120125a/doku.php 2012-04-19 12:12:33.0 +0200 +++ dokuwiki-0.0.20120125b/doku.php 2012-07-13 13:13:57.0 +0200 @@ -7,7 +7,7 @@ */ // update message version -$updateVersion = 36.1; +$updateVersion = 36.2; // xdebug_start_profiling(); diff -Nru dokuwiki-0.0.20120125a/inc/template.php dokuwiki-0.0.20120125b/inc/template.php --- dokuwiki-0.0.20120125a/inc/template.php 2012-04-19 12:09:54.0 +0200 +++ dokuwiki-0.0.20120125b/inc/template.php 2012-07-13 13:13:57.0 +0200 @@ -1151,7 +1151,7 @@ echo 'div class=panelHeader'.NL; echo 'h3'; $tabTitle = ($NS) ? $NS : '['.$lang['mediaroot'].']'; -printf($lang['media_' . $opened_tab], 'strong'.$tabTitle.'/strong'); +printf($lang['media_' . $opened_tab], 'strong'.hsc($tabTitle).'/strong'); echo '/h3'.NL; if ($opened_tab === 'search' || $opened_tab === 'files') { media_tab_files_options(); diff -Nru dokuwiki-0.0.20120125a/lib/exe/ajax.php dokuwiki-0.0.20120125b/lib/exe/ajax.php --- dokuwiki-0.0.20120125a/lib/exe/ajax.php 2012-04-19 12:09:54.0 +0200 +++ dokuwiki-0.0.20120125b/lib/exe/ajax.php 2012-07-13 13:13:57.0 +0200 @@ -13,7 +13,6 @@ header('Content-Type: text/html; charset=utf-8'); - //call the requested function if(isset($_POST['call'])){ $call = $_POST['call']; @@ -204,7 +203,7 @@ global $conf; global $NS; -$NS = $_POST['ns']; +$NS = cleanID($_POST['ns']); if ($_POST['do'] == 'media') { tpl_mediaFileList(); } else { diff -Nru dokuwiki-0.0.20120125a/VERSION dokuwiki-0.0.20120125b/VERSION --- dokuwiki-0.0.20120125a/VERSION 2012-04-19 12:12:33.0 +0200 +++ dokuwiki-0.0.20120125b/VERSION 2012-07-13 13:13:57.0 +0200 @@ -1 +1 @@ -2012-01-25a Angua +2012-01-25b Angua
Bug#684414: marked as done (unblock (pre-approval): libspectre/0.2.7-1)
Your message dated Wed, 15 Aug 2012 12:51:39 +0200 with message-id 502b7f3b.90...@thykier.net and subject line Re: Bug#684414: unblock (pre-approval): libspectre/0.2.7-1 has caused the Debian Bug report #684414, regarding unblock (pre-approval): libspectre/0.2.7-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.) -- 684414: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684414 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: freeze-exception Hi, yesterday a new bugfix version of libspectre, 0.2.7, has been released. This version quite small in the actual changes it brings, while fixing a couple of issues. The full source diff between 0.2.6 and 0.2.7 is: ChangeLog| 333 +-- Makefile.in | 104 - NEWS | 10 aclocal.m4 | 2501 -- config.guess | 263 +- config.sub | 204 +- configure| 3339 ++- configure.ac |4 depcomp | 238 ++ install-sh | 544 +++-- libspectre/Makefile.am | 12 libspectre/Makefile.in | 201 +- libspectre/ps.c | 12 libspectre/spectre-version.h |6 ltmain.sh| 4051 --- missing | 145 - test/Makefile.am | 19 test/Makefile.in | 123 - 18 files changed, 7840 insertions(+), 4269 deletions(-) but most of the changes are autoconf/automake/libtool-related stuff; stripping those and stripping the ChangeLog (output of `git log`) and NEWS files, what is left is: configure.ac |4 ++-- libspectre/Makefile.am | 12 ++-- libspectre/ps.c | 12 +++- libspectre/spectre-version.h |6 +++--- test/Makefile.am | 19 +-- 5 files changed, 31 insertions(+), 22 deletions(-) which is also attached. The changes are the following: - configure.ac, libspectre/spectre-version.h: bump the version to 0.2.7 - libspectre/Makefile.am, test/Makefile.am: fix the automake build system to handle own CFLAGS properly and not ignore user-specified ones (like the Debian ones) - libspectre/ps.c as written in NEWS, fixes two crashes than can happen when %%Pages: or %%Page: comments are missing in the document or when %%Pages: comment is present but it's invalid. On the Debian side, other than the usual new upstream release, I would need to just add export V=1 in debian/rules to have the build system output the compilation commands used. I think it should be mostly harmless overall for wheezy, hence I'm asking for a pre-approval (and then unblock) before uploading it to unstable. Thanks, -- Pino --- libspectre-0.2.6/configure.ac +++ libspectre-0.2.7/configure.ac @@ -2,7 +2,7 @@ m4_define([spectre_major_version], [0]) m4_define([spectre_minor_version], [2]) -m4_define([spectre_micro_version], [6]) +m4_define([spectre_micro_version], [7]) m4_define([spectre_version], [spectre_major_version.spectre_minor_version.spectre_micro_version]) @@ -25,7 +25,7 @@ ## increment any time the source changes; set to ## 0 if you increment CURRENT -LT_REVISION=6 +LT_REVISION=7 ## increment if any interfaces have been added; set to 0 ## if any interfaces have been changed or removed. removal has --- libspectre-0.2.6/libspectre/Makefile.am +++ libspectre-0.2.7/libspectre/Makefile.am @@ -1,9 +1,3 @@ -INCLUDES = \ - -I$(top_builddir) \ - -I$(srcdir) \ - -I$(top_srcdir) \ - $(SPECTRE_CFLAGS) - EXTRA_DIST=spectre-version.h.in lib_LTLIBRARIES = libspectre.la @@ -47,5 +41,11 @@ spectre-utils.c \ $(gv_sources) +libspectre_la_CFLAGS = \ + -I$(top_builddir) \ + -I$(srcdir) \ + -I$(top_srcdir) \ + $(SPECTRE_CFLAGS) + libspectre_la_LIBADD = $(LIB_GS) libspectre_la_LDFLAGS = -version-info @VERSION_INFO@ -no-undefined --- libspectre-0.2.6/libspectre/ps.c +++ libspectre-0.2.7/libspectre/ps.c @@ -597,6 +597,8 @@ if (maxpages 0) { doc-pages = (struct page *) PS_calloc(maxpages, sizeof(struct page)); +if (!doc-pages) +maxpages = 0; CHECK_MALLOCED(doc-pages); } } @@ -1002,14 +1004,14 @@ section_len += line_len; } +if (maxpages == 0) { +
please include circos 0.61-3 in stable release
Hi, I would like to ask to take into account circos 0.61-3 in stable release (if package is considered). The fix in 0.61-3 fixes a bug preventing correct usage of the package (missing dependency in Depends). Thanks Olivier -- osal...@debian.org -- gpg key id: 4096R/326D8438 (keyring.debian.org) Key fingerprint = 5FB4 6F83 D3B9 5204 6335 D26D 78DC 68DB 326D 8438
Request for update of package capi4hylafax (with debdiff)
Hallo, [now with debdiff as attachment] I took over the package capi4hylafax a very short time before freeze and my first package still need some fixes. Could you please allow updating the package in testing? Compared with version 01.03.00.99.svn.300-17 (in testing) the updated package have this changes: capi4hylafax (1:01.03.00.99.svn.300-18) unstable; urgency=low * Add postinst script to update logfile name and path in /etc/hylafax/config.faxCAPI. Closes: #647164 * Fix udev warning: create symlink /dev/faxCAPI with init script and remove udev rules file. Closes: #684741 * Only suggest contrib package isdnactivecards. Closes: #682135 -- Joachim Wiedorn ad_deb...@joonet.de Mon, 13 Aug 2012 17:57:37 +0200 I know these are all normal bugs, but especially the problem with the logfile (#647164) should be solved, because on small systems this could induce to full harddisk partition. So this bugfix would be important for all users in the next stable Wheezy. The other both bugs give always irritating warnings to users and should also be solved. I would be very appreciated if you allow this update. --- Have a nice day. Joachim (Germany) capi4hylafax-debdiff.log.gz Description: GNU Zip compressed data
Re: BinNMU breaks QT4
Lisandro, am Tue, Aug 14, 2012 at 09:07:34PM -0300 hast du folgendes geschrieben: On the other hand, IMPOV, if it's RC, the real bug it's on the buildds/dpkg, and it should be RC too. the buildds really don't have anything to do with it. Maybe the infrastructure should prevent people from doing binNMUs, but given that the non-multiarch use was fixed by them it wouldn't be that great. Kind regards Philipp Kern signature.asc Description: Digital signature
Re: BinNMU breaks QT4
On Mié 15 Aug 2012 08:52:55 Philipp Kern escribió: Lisandro, am Tue, Aug 14, 2012 at 09:07:34PM -0300 hast du folgendes geschrieben: On the other hand, IMPOV, if it's RC, the real bug it's on the buildds/dpkg, and it should be RC too. the buildds really don't have anything to do with it. Maybe the infrastructure should prevent people from doing binNMUs, but given that the non-multiarch use was fixed by them it wouldn't be that great. Thanks Philipp for the data :-) -- http://mx.grulic.org.ar/lurker/message/20081108.174208.4f42e55c.es.html Así se corrobora el software legal en Argentina Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/ signature.asc Description: This is a digitally signed message part.
Bug#684975: unblock: dokuwiki/dokuwiki_0.0.20120125b-1
Control: tags -1 + confirmed On 15.08.2012 11:10, Tanguy Ortolo wrote: Please unblock package dokuwiki Current version in testing 0.0.20120125a-1 has a security flaw #683378. There is a new upstream version, 0.0.20120125b, which fixes this and only this. I am not convinced that this fits into the release policy, since it does not fix an RC bug, only a security one. Additionally, it consists in a new upstream version, which adds to this uncertainty regarding the policy. For this reason I have not uploaded it to unstable yet. Attached it a debdiff of the updated package, please advice. Given the tiny size of the diff, I'd be prepared to accept this if it's uploaded soon; 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/199e020cd7560561d275c337b7ff3...@mail.adsl.funky-badger.org
Processed: Re: Bug#684975: unblock: dokuwiki/dokuwiki_0.0.20120125b-1
Processing control commands: tags -1 + confirmed Bug #684975 [release.debian.org] unblock: dokuwiki/dokuwiki_0.0.20120125b-1 Added tag(s) confirmed. -- 684975: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684975 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.b684975.13450344878607.transcr...@bugs.debian.org
Re: Allow ocfs2-tools 1.6.4-2 into wheezy
On 15.08.2012 10:47, Jeremy Lainé wrote: I have uploaded a new revision of ocfs2-tools to unstable which fixes bug #682517 (inability to launch the ocfs2console GUI): http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=682517 The fix (thanks Sébastien Villemot) is straight-forward: drop a bad Debian/Ubuntu specific patch, as can be seen from the attached debdiff. Could you please let this new version migrate into wheezy? Unblocked; thanks. Regards, Adam -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/df7134b0b1f2f2247c34e24190833...@mail.adsl.funky-badger.org
Bug#684961: marked as done (unblock: rpm/4.10.0-5)
Your message dated Wed, 15 Aug 2012 13:49:47 +0100 with message-id 1ee570a4e01912cad993f13556a9e...@mail.adsl.funky-badger.org and subject line Re: Bug#684961: unblock: rpm/4.10.0-5 has caused the Debian Bug report #684961, regarding unblock: rpm/4.10.0-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.) -- 684961: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684961 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 rpm, it includes single patch from Fedora to allow setup of Fedora 17 (and future Fedora 18 and RHEL7) chroots. This is really not a critical fix, but will improve compatibility with other Linux vendors. The only change in the package is adding this patch: http://anonscm.debian.org/gitweb/?p=collab-maint/rpm.git;a=blob;f=debian/patches/rpm-4.9.1.2-rpmlib-filesystem-check.patch Debdiff attached as well. unblock rpm/4.10.0-5 Thanks - -- Michal Čihař | http://cihar.com | http://blog.cihar.com - -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.1.10-1.16-desktop (SMP w/2 CPU cores; PREEMPT) Locale: LANG=cs_CZ.UTF-8, LC_CTYPE=cs_CZ.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCAAGBQJQK05dAAoJEGo39bHX+xdNQ3MP/i5fIRmrWfx1G6eb2Sje222G spLNiFH3wmXBCBzAcKluy9cEUoPIa7DihjXzD9r/UjeFVWndEVt7ZCAWtxAB8GcW jPfGboiOL/Bz4k/a5KSNusFWF+lsUjyFGKh72jaSpCtewZmjY2Cm+qVwgJo01dgl KaxOKY4Hz4TFHs5XkLuDTY7gYTI0HZ/0ukaaQU/KVQ+AcYxhAY339sotDHsABQy6 AS3fnbq4v3suXglo8J/g1+0ejCk/J47KhoiKKK80YDHOUlIbFmpmUNaXnJ0JHU0D lQN+T2PrAXSnQZ4gLfT/sKXgvykWBFIKZXUdmCzQCA4cU05MlLVhoapQfUIGZP8M Wwk1v+2XxxDJB2bHEHPNCs99P4BfeG/GPSELtXFAnYFqs53BFzfdUOygNM3YgyDS w3sAyQgAKtrNlFvOrWmyutlxYQo0qpmED8jTEjz/oWhhChrEB37Pq9LM/DfBfjEK rvT6AeOiuO+tNhpU7YUakof9DOKxnx6v68OgPz6QLIg5K7K1WzdHe364OEoL67Ua E1cKMyf0pN0AK4UlE/2nhHRODGNOoFdNsyjOuxmBQ3eMrll55SA9z490Ug3ZXktS KkYJquPjFJLM7Yhk7L13I1Xuue161qG3VyR5C2wSEU4H1ZJpwDwN/4x33+D4DxtE B9X0vRcBJdCY/TGx5FXW =tcWN -END PGP SIGNATURE- diff -Nru rpm-4.10.0/debian/changelog rpm-4.10.0/debian/changelog --- rpm-4.10.0/debian/changelog 2012-06-25 14:29:22.0 +0200 +++ rpm-4.10.0/debian/changelog 2012-08-15 09:05:37.0 +0200 @@ -1,3 +1,10 @@ +rpm (4.10.0-5) unstable; urgency=low + + * Added patch from Fedora to support X-CheckUnifiedSystemdir +(Closes: #683759). + + -- Michal Čihař ni...@debian.org Wed, 15 Aug 2012 09:05:26 +0200 + rpm (4.10.0-4) unstable; urgency=low * Lower librpm - rpm-common dependency to recommends as there actually diff -Nru rpm-4.10.0/debian/patches/rpm-4.9.1.2-rpmlib-filesystem-check.patch rpm-4.10.0/debian/patches/rpm-4.9.1.2-rpmlib-filesystem-check.patch --- rpm-4.10.0/debian/patches/rpm-4.9.1.2-rpmlib-filesystem-check.patch 1970-01-01 01:00:00.0 +0100 +++ rpm-4.10.0/debian/patches/rpm-4.9.1.2-rpmlib-filesystem-check.patch 2012-08-15 09:05:37.0 +0200 @@ -0,0 +1,128 @@ +Description: Add Fedora compatible rpm builtin provides +Origin: vendor, http://pkgs.fedoraproject.org/cgit/rpm.git/plain/rpm-4.9.1.2-rpmlib-filesystem-check.patch +Forwarded: not-needed +--- a/lib/depends.c b/lib/depends.c +@@ -459,6 +459,108 @@ + return rc; + } + ++/* ++ * Temporary support for live-conversion of the filesystem hierarchy ++ * mailto: k...@redhat.com, har...@redhat.com ++ * https://fedoraproject.org/wiki/Features/UsrMove ++ * ++ * X-CheckUnifiedSystemdir: ++ * /bin, /sbin, /lib, /lib64 -- /usr ++ * ++ * X-CheckUnifiedBindir: ++ * /usr/sbin - /usr/bin ++ * ++ * X-CheckMultiArchLibdir: ++ * /usr/lib64 /usr/lib/platform tuple (e.g. x86_64-linux-gnu) ++ * ++ * This code is not needed for new installations, it can be removed after ++ * updates from older systems are no longer supported: Fedora 19 / RHEL 8. ++ */ ++ ++static int CheckLink(const char *dir, const char *root) ++{ ++char *d = NULL; ++struct stat sbuf; ++int rc = 0; ++ ++if (!root) ++ root = /; ++ ++rasprintf(d, %s%s, root, dir); ++if (!d) { ++ rc = -1; ++ goto exit; ++} ++ ++/* directory or symlink does not exist, all is fine */ ++if (lstat(d, sbuf) 0) { ++ rc = 1; ++ goto exit; ++} ++ ++/* if it is a symlink, all is fine */ ++if (S_ISLNK(sbuf.st_mode)) ++ rc = 1; ++ ++exit: ++free(d); ++
Processed: Re: Bug#684950: pu: package clamav/0.97.5+dfsg-6~squeeze1
Processing control commands: tag -1 + pending Bug #684950 [release.debian.org] pu: package clamav/0.97.5+dfsg-6~squeeze1 Added tag(s) pending. -- 684950: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684950 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.b684950.134503529214320.transcr...@bugs.debian.org
Bug#684950: pu: package clamav/0.97.5+dfsg-6~squeeze1
Control: tag -1 + pending On 14.08.2012 23:55, Scott Kitterman wrote: Fixes a severe regression in 0.97.5 (compared to 0.97.3 in squeeze now). Also include packaging improvements to correctly purge packages. This should go into stable-updates ASAP as the package there currently suffers from the regression and then into the next point release when it happens. Flagged for acceptance; thanks. We can look at stable-updates once at least the majority of architectures are available. 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/1fff91348a80fa8af12e5f3346ea8...@mail.adsl.funky-badger.org
Bug#684955: marked as done (unblock: phpmyadmin/4:3.4.11.1-1 (security issue))
Your message dated Wed, 15 Aug 2012 13:53:36 +0100 with message-id 3767996ddd658f7050c4a9b70e994...@mail.adsl.funky-badger.org and subject line Re: Bug#684955: unblock: phpmyadmin/4:3.4.11.1-1 (security issue) has caused the Debian Bug report #684955, regarding unblock: phpmyadmin/4:3.4.11.1-1 (security issue) 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.) -- 684955: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684955 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 Hi, Please unblock package phpmyadmin: it fixes two cross site scripting issues and nothing else. The diff to db_structure.js may be a bit hard to read, but it adds escapeHTML() calls to two parameters. unblock phpmyadmin/4:3.4.11.1-1 Thanks, Thijs Title: phpMyAdmin 3.4.11 - Documentation diff -Nru phpmyadmin-3.4.11/ChangeLog phpmyadmin-3.4.11.1/ChangeLog --- phpmyadmin-3.4.11/ChangeLog 2012-04-14 11:42:20.0 + +++ phpmyadmin-3.4.11.1/ChangeLog 2012-08-12 13:38:18.0 + @@ -1,6 +1,9 @@ phpMyAdmin - ChangeLog == +3.4.11.1 (2012-08-12) +- [security] Fixed XSS vulnerabilities, see PMASA-2012-4 + 3.4.11.0 (2012-04-14) - bug #3486970 [import] Exception on XML import - bug #3488777 [navi] $cfg['ShowTooltipAliasTB'] and blank names in navigation diff -Nru phpmyadmin-3.4.11/Documentation.html phpmyadmin-3.4.11.1/Documentation.html --- phpmyadmin-3.4.11/Documentation.html 2012-04-14 11:42:20.0 + +++ phpmyadmin-3.4.11.1/Documentation.html 2012-08-12 13:38:18.0 + @@ -9,7 +9,7 @@ - +phpMyAdmin 3.4.11.1 - Documentation @@ -17,7 +17,7 @@ phpMyAdmin -3.4.11 +3.4.11.1 Documentation diff -Nru phpmyadmin-3.4.11/Documentation.txt phpmyadmin-3.4.11.1/Documentation.txt --- phpmyadmin-3.4.11/Documentation.txt 2012-04-14 11:42:20.0 + +++ phpmyadmin-3.4.11.1/Documentation.txt 2012-08-12 13:38:18.0 + @@ -1,4 +1,4 @@ -phpMyAdmin 3.4.11 Documentation +phpMyAdmin 3.4.11.1 Documentation * Top * Requirements diff -Nru phpmyadmin-3.4.11/README phpmyadmin-3.4.11.1/README --- phpmyadmin-3.4.11/README 2012-04-14 11:42:20.0 + +++ phpmyadmin-3.4.11.1/README 2012-08-12 13:38:18.0 + @@ -1,7 +1,7 @@ phpMyAdmin - Readme === -Version 3.4.11 +Version 3.4.11.1 A set of PHP-scripts to manage MySQL over the web. diff -Nru phpmyadmin-3.4.11/RELEASE-DATE-3.4.11 phpmyadmin-3.4.11.1/RELEASE-DATE-3.4.11 --- phpmyadmin-3.4.11/RELEASE-DATE-3.4.11 2012-04-14 11:42:20.0 + +++ phpmyadmin-3.4.11.1/RELEASE-DATE-3.4.11 1970-01-01 00:00:00.0 + @@ -1 +0,0 @@ -Sat Apr 14 11:41:12 UTC 2012 diff -Nru phpmyadmin-3.4.11/RELEASE-DATE-3.4.11.1 phpmyadmin-3.4.11.1/RELEASE-DATE-3.4.11.1 --- phpmyadmin-3.4.11/RELEASE-DATE-3.4.11.1 1970-01-01 00:00:00.0 + +++ phpmyadmin-3.4.11.1/RELEASE-DATE-3.4.11.1 2012-08-12 13:38:18.0 + @@ -0,0 +1 @@ +Sun Aug 12 13:37:09 UTC 2012 diff -Nru phpmyadmin-3.4.11/debian/changelog phpmyadmin-3.4.11.1/debian/changelog --- phpmyadmin-3.4.11/debian/changelog 2012-04-18 10:28:38.0 + +++ phpmyadmin-3.4.11.1/debian/changelog 2012-08-13 13:25:51.0 + @@ -1,3 +1,10 @@ +phpmyadmin (4:3.4.11.1-1) unstable; urgency=high + + * New upstream security release. +- Fixes cross site scripting [PMASA-2012-4]. + + -- Thijs KinkhorstMon, 13 Aug 2012 13:24:09 + + phpmyadmin (4:3.4.11-1) unstable; urgency=low * New upstream release. diff -Nru phpmyadmin-3.4.11/js/db_structure.js phpmyadmin-3.4.11.1/js/db_structure.js --- phpmyadmin-3.4.11/js/db_structure.js 2012-04-14 11:42:20.0 + +++ phpmyadmin-3.4.11.1/js/db_structure.js 2012-08-12 13:38:18.0 + @@ -1,6 +1,6 @@ function PMA_adjustTotals(a){var b=a.closest("tr");a=b.find(".tbl_rows");var d=b.find(".tbl_size");b=parseInt(a.text());a.text("0");d.text("-");if(!isNaN(b)){$total_rows_td=$("#tbl_summary_row").find(".tbl_rows");a=parseInt($total_rows_td.text());isNaN(a)||$total_rows_td.text(a-b)}a=$("#tbl_summary_row").find(".tbl_size");a.text(a.text().replace(/^/,"~"))} -$(document).ready(function(){$(".truncate_table_anchor").live("click",function(a){a.preventDefault();var b=$(this);a="TRUNCATE
NEW changes in stable-new
Processing changes file: clamav_0.97.5+dfsg-6~squeeze1_i386.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/e1t1d07-0001jw...@franck.debian.org
Bug#684988: unblock: libio-async-loop-glib-perl/0.20-2
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Please unblock package libio-async-loop-glib-perl. unblock libio-async-loop-glib-perl/0.20-2 0.20-2 fixes RC bug #680806. The upload adds a patch provided by upstream that removes the assumption that POLLHUP would work reliably -- which it doesn't. Upstream bug: https://rt.cpan.org/Public/Bug/Display.html?id=78891 Changelog: libio-async-loop-glib-perl (0.20-2) unstable; urgency=low * Add patch pollhup.patch: remove declaration that IO::Async::Loop::Glib can handle on_hangup. POLLHUP is not reliable to detect that the reader has closed their end of a pipe. Thanks to Paul Evans (upstream author) for the patch. (Closes: #680806) -- gregor herrmann gre...@debian.org Wed, 15 Aug 2012 15:12:49 +0200 Complete debdiff attached. Thank in advance, gregor -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCAAGBQJQK6V1AAoJELs6aAGGSaoGU8MQAJ+3En+cYOor7VVPCkle6rq1 3Sbq5ftzf0nNTyh2HBrex3FeFkjf0LZcsnulkvz2cxa/WByQHGVP3GMe9LmOi9GG bRspMxa6y4TNJaeuDtOB34Z97IzZgl8SnZGcjFqY1JR2OmozxG8ke65ptI8g3Nal Z6Co4WrlwlC6c2fO9FeO8CG8Fwfc3pqZFowwD3EXhp91OxbbFhUtiFbmJfL2kd5E 2Q28MQugIVhUjwYS2YEFDG4nNmHiszdDmPNE+eFYBQDW1mmuoS7gvuHyFRNqCjPw lnDUt/vbanR9Nu87qoa4Q95QgovMJECxqkbN771kSbljIF4/PdUrM5EzlusG/jS6 YRNHEsE6Oo9TunEuMTR2Opt0dHdxqPnS9h5zO5VBfBEP/dzV0KvMFxf3Ml32yAJU Ly8nzmL49CXWEI0KUVtc9ynsS2Uz2/jakXMc8mgfsrEigxrFm1aptgWgksy75mr1 Kr7OZUVP2EHuLQafn6uQWxuoZGQ7TXz0F2cezgeyf3Jg5BVhIgi1TFVZ/GIRcb2j gfRAWaxOkxJIUV4396LbsZPFXmaabJYQmmGO970CBu36kFaUGRUGppb5CwpDRMcL qH8R9dYp99s8jO4X0vZ/kp8+vhyW8V7KczHU26aOTJDSlQQv244bfTRDFBaRIkA2 NpuWHeBCbJSkBo9x+56Y =s2eq -END PGP SIGNATURE- diff -Nru libio-async-loop-glib-perl-0.20/debian/changelog libio-async-loop-glib-perl-0.20/debian/changelog --- libio-async-loop-glib-perl-0.20/debian/changelog 2011-09-18 18:23:28.0 +0200 +++ libio-async-loop-glib-perl-0.20/debian/changelog 2012-08-15 15:16:32.0 +0200 @@ -1,3 +1,12 @@ +libio-async-loop-glib-perl (0.20-2) unstable; urgency=low + + * Add patch pollhup.patch: remove declaration that IO::Async::Loop::Glib +can handle on_hangup. POLLHUP is not reliable to detect that the +reader has closed their end of a pipe. Thanks to Paul Evans (upstream +author) for the patch. (Closes: #680806) + + -- gregor herrmann gre...@debian.org Wed, 15 Aug 2012 15:12:49 +0200 + libio-async-loop-glib-perl (0.20-1) unstable; urgency=low * Team upload. diff -Nru libio-async-loop-glib-perl-0.20/debian/patches/pollhup.patch libio-async-loop-glib-perl-0.20/debian/patches/pollhup.patch --- libio-async-loop-glib-perl-0.20/debian/patches/pollhup.patch 1970-01-01 01:00:00.0 +0100 +++ libio-async-loop-glib-perl-0.20/debian/patches/pollhup.patch 2012-08-15 15:16:32.0 +0200 @@ -0,0 +1,22 @@ +Description: remove IaLoop::Glib's declaration that it can handle on_hangup + [The bug] comes from an expectation on my part hat POLLHUP was actually + reliable across operating systems, to detect that the reader has closed + their end of a pipe. Turns out this really isn't the case at all. +Origin: upstream, RT#78891 +Bug: http://rt.cpan.org/Public/Bug/Display.html?id=78891 +Bug-Debian: http://bugs.debian.org/680806 +Author: Paul Evans leon...@leonerd.org.uk +Reviewed-by: gregor herrmann gre...@debian.org +Last-Update: 2012-08-15 + +--- a/lib/IO/Async/Loop/Glib.pm b/lib/IO/Async/Loop/Glib.pm +@@ -13,7 +13,7 @@ + + # Only Linux is known always to be able to report EOF conditions on + # filehandles using POLLHUP +-use constant _CAN_ON_HANGUP = ( $^O eq linux ); ++#use constant _CAN_ON_HANGUP = ( $^O eq linux ); + + use base qw( IO::Async::Loop ); + IO::Async::Loop-VERSION( '0.33' ); diff -Nru libio-async-loop-glib-perl-0.20/debian/patches/series libio-async-loop-glib-perl-0.20/debian/patches/series --- libio-async-loop-glib-perl-0.20/debian/patches/series 1970-01-01 01:00:00.0 +0100 +++ libio-async-loop-glib-perl-0.20/debian/patches/series 2012-08-15 15:16:32.0 +0200 @@ -0,0 +1 @@ +pollhup.patch
Copyright issue in rush_1.7+dfsg-1.
Hallo all, the initial release of rush_1.7+dfsg-1 happened a year ago. The package has a minute user base, but when I returned to the package recently I happened to notice that there was a clear mistake in the recording of copyright terms for one of the files. The published package claims GPL, whereas a scrutiny of the text reveals a custom license, very close to a public domain attribution, intended to allow linking with LGPL. My sponsor Sven Hoexter suggests that this might be classified as a release critical deviation. Presently he has uploaded the package to experimental while we await guidance from this list. However, the updated packaging rush_1.7+dfsg-2, which I have uploaded to debian.mentors.net, happens to also address the hardened build of the contained binary executables. It is a priori not obvious that this composite package update would qualify for inclusion in the upcoming release, this late in the process. Personally I regard the hardening valuable to a security relevant service like GNU Rush, so I now seek conclusive advice on this matter, as to the prospects of unblocking the package and getting it into testing. The debdiff between the published package and my proposed update is included in this message. As said, the full package is deposited at experimental since a week's time. I am writing this query encouraged by my sponsor Sven Hoexter. Best regards, Mats Erik Andersson, DM changelog | 19 +++ control |5 +++-- copyright | 56 +++- rules |5 + 4 files changed, 70 insertions(+), 15 deletions(-) diff -Nru rush-1.7+dfsg/debian/changelog rush-1.7+dfsg/debian/changelog --- rush-1.7+dfsg/debian/changelog 2011-07-06 17:48:31.0 +0200 +++ rush-1.7+dfsg/debian/changelog 2012-08-02 20:47:09.0 +0200 @@ -1,3 +1,22 @@ +rush (1.7+dfsg-2) unstable; urgency=low + + * Hardened builds: ++ debian/rules: Set compiler flags using dpkg-buildflags. ++ debian/control: Build depends on dpkg-dev (= 1.15.7). + * debian/control: Standards 3.9.3, no changes. + * debian/copyright: ++ Update to valid URL in format specification. ++ Remove commata in file lists. ++ Insert conditions of two public-domain attributions. ++ Add plus character in standalone license's names + GPL-2+ and GPL-3+. Express terms of the former. ++ The file po/Makefile.in.in was mistakenly named as + using GPL. In fact, the file uses a custom license, + implicitly public domain like. The conditions of use + are now copied verbatim. + + -- Mats Erik Andersson mats.anders...@gisladisker.se Thu, 02 Aug 2012 20:45:15 +0200 + rush (1.7+dfsg-1) unstable; urgency=low * Initial release. (Closes: #515198) diff -Nru rush-1.7+dfsg/debian/control rush-1.7+dfsg/debian/control --- rush-1.7+dfsg/debian/control 2011-07-06 17:48:31.0 +0200 +++ rush-1.7+dfsg/debian/control 2012-08-02 18:47:29.0 +0200 @@ -2,8 +2,9 @@ Section: shells Priority: extra Maintainer: Mats Erik Andersson mats.anders...@gisladisker.se -Build-Depends: debhelper (= 8.0.0), dh-autoreconf, autopoint -Standards-Version: 3.9.2 +Build-Depends: debhelper (= 8.0.0), dh-autoreconf, autopoint, + dpkg-dev (= 1.15.7) +Standards-Version: 3.9.3 Homepage: http://puszcza.gnu.org.ua/projects/rush/ Package: rush diff -Nru rush-1.7+dfsg/debian/copyright rush-1.7+dfsg/debian/copyright --- rush-1.7+dfsg/debian/copyright 2011-06-14 21:12:14.0 +0200 +++ rush-1.7+dfsg/debian/copyright 2012-08-02 19:50:32.0 +0200 @@ -1,4 +1,4 @@ -Format: http://anonscm.debian.org/viewvc/dep/web/deps/dep5.mdwn?revision=174 +Format: http://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ Upstream-Name: GNU rush Upstream-Contact: Sergey Poznyakoff g...@gnu.org.ua Source: http://puszcza.gnu.org.ua/projects/rush/ @@ -9,15 +9,10 @@ Copyright: 2008-2010, Sergey Poznyakoff g...@gnu.org.ua License: GPL-3+ -Files: build-aux/*, gnu/*, m4/* +Files: build-aux/* gnu/* m4/* Copyright: 1992-2010, Free Software Foundation, Inc. License: GPL-3+ -Files: build-aux/install-sh -Copyright: Free Software Foundation -Comment: The major part is copyrighted by the X Consortium; see below -License: public-domain - Files: build-aux/mdate-sh Copyright: 1995-2010, Free Software Foundation, Inc. 1995, Ulrich Drepper drep...@gnu.ai.mit.edu @@ -31,8 +26,15 @@ Files: gnu/alloca.c Copyright: D A Gwyn License: public-domain + (Mostly) portable public-domain implementation -- D A Gwyn + . + This implementation of the PWB library alloca function, + which is used to allocate space off the run-time stack so + that it is automatically reclaimed upon procedure exit, + was inspired by discussions with J. Q. Johnson of Cornell. + J.Otto Tennant j...@cray.com contributed the Cray support. -Files: po/*.po, po/rush.pot +Files: po/*.po po/rush.pot Copyright: 2010, Free Software Foundation, Inc. 2009-2010, Sergey
Bug#684991: Please allow uploading ejabberd 2.1.10-3 to Wheezy
Package: release.debian.org User: release.debian@packages.debian.org Usertags: freeze-exception Severity: normal Please allow uploading of ejabberd-2.1.10-3 into Wheezy which fixes three important bugs. One of this bugs, #654853 has been fixed upstream in 2.1.11, and the fixes for #664034 and #670307 have been integrated into the Debian package for 2.1.11, so we intended to fix them all by uploading that Debian package. Unfortunately, the upload did not happen before the freeze, so we're stuck with 2.1.10. Since all these important important bugs apply to 2.1.10, I've implemented fixes for them in the existing 2.1.10 package and hereby ask for the permission to upload the new package. diff -u ejabberd-2.1.10/debian/changelog ejabberd-2.1.10/debian/changelog --- ejabberd-2.1.10/debian/changelog +++ ejabberd-2.1.10/debian/changelog @@ -1,3 +1,16 @@ +ejabberd (2.1.10-3) unstable; urgency=low + + [ Konstantin Khomoutov ] + * Provide custom implementation of xmerl_regexp:sh_to_awk/1 +(closes: #670307). + * Add use_dpkg_buildflags.patch (thanks to Simon Ruderich, +closes: #664034). + * Add relax-digest-uri-handling.patch (closes: #654853). + * Add Slovak translation (thanks to Slavko, closes: #647115). + * Add Italian translation (thanks to Beatrice Torracca, closes: #682987). + + -- Konstantin Khomoutov flatw...@users.sourceforge.net Sun, 20 May 2012 14:51:12 +0400 + ejabberd (2.1.10-2) unstable; urgency=low [ Gerfried Fuchs ] diff -u ejabberd-2.1.10/debian/patches/series ejabberd-2.1.10/debian/patches/series --- ejabberd-2.1.10/debian/patches/series +++ ejabberd-2.1.10/debian/patches/series @@ -1,4 +1,7 @@ +use_dpkg_buildflags.patch +ejabberd_regexp.patch mod_admin_extra.patch captcha.patch fix_examples.patch reopen-log.patch +relax-digest-uri-handling.patch only in patch2: unchanged: --- ejabberd-2.1.10.orig/debian/patches/ejabberd_regexp.patch +++ ejabberd-2.1.10/debian/patches/ejabberd_regexp.patch @@ -0,0 +1,95 @@ +Description: Provide custom replacement for xmerl_regexp:sh_to_awk/1 + Erlang R15 dropped support for its old regular expressions library + (implemented as the regexp module) and replaced it with a new, + PCRE-based, implementation (implemented as the re module). + This transition lost the regexp:sh_to_awk/1 function which, given + a glob-style expression commonly used in POSIX shells to match + filenames, would produce a regular expression specification with + the equivalent semantics. The ejabberd upstream tried to combat + this situation [1] by using xmerl_regexp:sh_to_awk/1. + This introduced an implicit dependency on the erlang-xmerl library + which has been the cause for a Debian bug #670307. + Depending on erlang-xmerl has two problems: + 1) It's a 1.5M library otherwise not used by ejabberd code while +the function itself is rather straightforward to implement. + 2) The implementation of xmerl_regexp:sh_to_awk/1 has certain +flaws (incorrect parsing of bracketed expressions, not escaping +match repetition counts). + As a result, a custom implementation of sh_to_awk/1 is provided, + which works almost like xmerl_regexp:sh_to_awk/1 but fixes its flaws. + 1. https://support.process-one.net/browse/EJAB-921 +Author: Konstantin Khomoutov flatw...@users.sourceforge.net +Forwarded: no +Last-Update: 2012-06-04 +--- +This patch header follows DEP-3: http://dep.debian.net/deps/dep3/ +--- a/src/ejabberd_regexp.erl b/src/ejabberd_regexp.erl +@@ -26,6 +26,7 @@ + + -module(ejabberd_regexp). + -compile([export_all]). ++-import(lists, [reverse/1, member/2]). + + exec(ReM, ReF, ReA, RgM, RgF, RgA) - + try apply(ReM, ReF, ReA) +@@ -66,7 +67,56 @@ + A - A + end. + +-sh_to_awk(ShRegExp) - +-case exec(xmerl_regexp, sh_to_awk, [ShRegExp], regexp, sh_to_awk, [ShRegExp]) of +- A - A ++sh_to_awk(Pattern) when is_list(Pattern) - ++fnmatch_char(Pattern, [$(,$^]). ++ ++fnmatch_char([], Acc) - ++lists:reverse([$$,$)|Acc]); ++fnmatch_char([Ch|Tail], Acc) - ++case Ch of ++ $\\ - ++ fnmatch_char(Tail, [$\\,$\\|Acc]); ++ $[ - ++ fnmatch_bexp_first(Tail, [Ch|Acc]); ++ $? - ++ fnmatch_char(Tail, [$.|Acc]); ++ $* - ++ fnmatch_char(Tail, [$*,$.|Acc]); ++ _ - ++ case lists:member(Ch, ^.+{}()$|\\) of ++ true - ++ fnmatch_char(Tail, [Ch,$\\|Acc]); ++ false - ++ fnmatch_char(Tail, [Ch|Acc]) ++ end ++end. ++ ++fnmatch_bexp_first([], _) - ++{error, unclosed_be}; ++fnmatch_bexp_first([Ch|Tail], Acc) - ++case Ch of ++ $] - ++ {error, empty_be}; ++ $! - ++ fnmatch_bexp_next(Tail, false, [$^|Acc]); ++ $\\ - ++ fnmatch_bexp_next(Tail, true, Acc); ++ _ - ++ fnmatch_bexp_next(Tail, false, [Ch|Acc]) ++end. ++ ++fnmatch_bexp_next([], _, _) - ++{error, unclosed_be}; ++fnmatch_bexp_next([Ch|Tail], true, Acc) - ++fnmatch_bexp_next(Tail,
Bug#682908: Is this a done deal?
So is this settled? Emacs wheezy won't get Emacs 24? Ancient Emacs version in Debian for another two more years unless you use backports? What should be done about security flaws? http://permalink.gmane.org/gmane.emacs.devel/152457 I think there is still time to get Emacs into wheezy. It's a widely used package, so I think there is still time during the freeze cycle to test it. Matter of fact, I'm currently testing the 24 package I backported into *squeeze*, and it's working beautifully. - Jordi G. H. -- 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/caphs2gzyus-u57zso2n9y1-jp5xwibca-09nyzq2wetnsfm...@mail.gmail.com
Bug#684991: Please allow uploading ejabberd 2.1.10-3 to Wheezy
Forgot to mention inclusion of two debconf translations: Slovak and Italian. -- 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/20120815183107.940e7fb4669da09c33dc2...@domain007.com
Bug#682908: Is this a done deal?
On 15.08.2012 15:21, Jordi Gutiérrez Hermoso wrote: So is this settled? Emacs wheezy won't get Emacs 24? Ancient Emacs version in Debian for another two more years unless you use backports? Emacs 24 appears not to have been released upstream until less than three weeks before the freeze. The package wasn't uploaded to the Debian archive until the day before the freeze. Neither of those things argues for including a major new version in the release. What should be done about security flaws? http://permalink.gmane.org/gmane.emacs.devel/152457 Erm, they should be fixed, clearly. I'm not sure I understand your point though, as there appears to be a tiny patch for emacs 23 linked from that URL. I think there is still time to get Emacs into wheezy. It's a widely used package, so I think there is still time during the freeze cycle to test it. The point of the freeze isn't to test new things. It's to fix the serious (enough) bugs we have in the packages already in testing and make sure everything works well together to produce a quality release. Adding new software after the freeze doesn't seem to help towards those goals. 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/274955215eeac079d8f2ce2ba8f9e...@mail.adsl.funky-badger.org
Bug#682908: Is this a done deal?
On 15 August 2012 10:47, Adam D. Barratt a...@adam-barratt.org.uk wrote: On 15.08.2012 15:21, Jordi Gutiérrez Hermoso wrote: So is this settled? Emacs 24 appears not to have been released upstream until less than three weeks before the freeze. So it's a done deal, then? Ancient Emacs in Debian for two more years unless you use backports? - Jordi G. H. -- 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/CAPHS2gy+eEo7h7KaA-nUgtp2zMha-3Ye2D3XL57d-d_=rmk...@mail.gmail.com
Bug#682908: Is this a done deal?
On Wed, 15 Aug 2012 10:51:49 -0400 Jordi Gutiérrez Hermoso jord...@octave.org wrote: On 15 August 2012 10:47, Adam D. Barratt a...@adam-barratt.org.uk wrote: On 15.08.2012 15:21, Jordi Gutiérrez Hermoso wrote: So is this settled? Emacs 24 appears not to have been released upstream until less than three weeks before the freeze. So it's a done deal, then? Ancient Emacs in Debian for two more years unless you use backports? I fail to see how a release which was considered current by upstream only three weeks before the deadline for the freeze can be considered ancient by anyone. It's not a lot of time to get a major upstream version packaged and tested. Backports exists to allow for packages which are updated at points where there wasn't enough time to get the new version into the release. -- Neil Williams = http://www.linux.codehelp.co.uk/ pgpdiaYehd3Mr.pgp Description: PGP signature
Bug#682908: Is this a done deal?
On 15 August 2012 11:09, Neil Williams codeh...@debian.org wrote: On Wed, 15 Aug 2012 10:51:49 -0400 Jordi Gutiérrez Hermoso jord...@octave.org wrote: On 15 August 2012 10:47, Adam D. Barratt a...@adam-barratt.org.uk wrote: On 15.08.2012 15:21, Jordi Gutiérrez Hermoso wrote: So is this settled? Emacs 24 appears not to have been released upstream until less than three weeks before the freeze. So it's a done deal, then? Ancient Emacs in Debian for two more years unless you use backports? I fail to see how a release which was considered current by upstream only three weeks before the deadline for the freeze can be considered ancient by anyone. It's not a lot of time to get a major upstream version packaged and tested. Emacs 24 has been in pre-release mode for close to a year, widely tested, widely used. Lots of external elisp code was assuming that it was already for 24, even if upstream hadn't made a release. In a sense, Emacs goes through its own freeze cycle, and was about one year long. So by the time Debian stable gets the next version of Emacs, the codebase will be about three years old. Anyways, this doesn't answer my question, which I've asked thrice. Here it goes again: is this a done deal, and we're getting an ancient (yes, ancient) Emacs version for wheezy? - Jordi G. H. -- 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/CAPHS2gwRYA4kUkv0Jbk9-5Q-AXA=-uk1bffqugud7kdf6jm...@mail.gmail.com
Bug#685000: unblock: libio-async-perl/0.51-3
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Please unblock package libio-async-perl: unblock libio-async-perl/0.51-3 0.51-3 fixes the RC bug #680790. It adds a patch from upstream, that's already included in 0.51_001, 0.51_002 and 0.52. Changelog entry: libio-async-perl (0.51-3) unstable; urgency=low * Add patch subsecond.patch, backported from upstream: subsecond timer tests are skipped unless unit-tests require them, since they are not reliable for all Loop implementations. Thanks to Paul LeoNerd Evans (upstream author) for pointing me to the fix. (Closes: #680790) -- gregor herrmann gre...@debian.org Wed, 15 Aug 2012 17:55:42 +0200 Full debdiff attached. Thanks in advance, gregor -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCAAGBQJQK8syAAoJELs6aAGGSaoGs28P/RBt7DQM2c3rvHk+ucc/zkxh dEZaPOaO0f57GxfEAxCcXPj4MDoWswknPvPSg39DH4eidewLeOuz597QATcfE2Qd s0dD0Lc8+V1ASx4oSVDl+L2SGGQXtFc+tOyDBy7uMckMzJt5UZDbSvmq/ZR2y2lM HNvZaK1G8HHhIwU2J9usJ+AnlB+qnC5mR3zyPlbBFB9nrt+d3tVxAjoFvFvJiECS 3r+QtdLw2H4NF6OGAXMAh98pG9meLG27cHycuQ2Y4LwdUvkjQ+VSUwafdxvaGvXF Wn6rWS3tkQ5yEIeBhymp2xTDfBvRAi6UrK3syMMkdIhLgQV7QlMdaNfF+SWRTetV +Kf2NP6WCtwSPG6/4eJf5zMIyFmntGJM7YYi+ZjYEUrNPf7dwodURjcaYI6ORFlG QS8sWu27Jq5vJ3CMXi/e4aQxA9rif5J/+qrPgcSMDSZed5BvNege1HVcl6dKdeuv wPP2gADCbJNrOrFV+zoi0vrhxvzJd+hB7cYXde0Mx67r7Di3bzGuAp3DTr4i+ROj 0ntb6mOILp2DBQ2VKkqWAXnwhHV+VPCp5jpF3jRM+pXRSupVWG9cLN6bIbLgpTxm 21Ap3E4WgE4aElGys5xwxOhgmaM/ig0FqR26Q8i7L6VG4ny6p3DRUkA757Hd+FgC IXUDEER6quPGdSUcSMBq =bgCT -END PGP SIGNATURE- diff -Nru libio-async-perl-0.51/debian/changelog libio-async-perl-0.51/debian/changelog --- libio-async-perl-0.51/debian/changelog 2012-07-08 23:19:29.0 +0200 +++ libio-async-perl-0.51/debian/changelog 2012-08-15 17:56:05.0 +0200 @@ -1,3 +1,12 @@ +libio-async-perl (0.51-3) unstable; urgency=low + + * Add patch subsecond.patch, backported from upstream: subsecond timer +tests are skipped unless unit-tests require them, since they are not +reliable for all Loop implementations. Thanks to Paul LeoNerd Evans +(upstream author) for pointing me to the fix. (Closes: #680790) + + -- gregor herrmann gre...@debian.org Wed, 15 Aug 2012 17:55:42 +0200 + libio-async-perl (0.51-2) unstable; urgency=low * Team upload. diff -Nru libio-async-perl-0.51/debian/patches/series libio-async-perl-0.51/debian/patches/series --- libio-async-perl-0.51/debian/patches/series 1970-01-01 01:00:00.0 +0100 +++ libio-async-perl-0.51/debian/patches/series 2012-08-15 17:56:05.0 +0200 @@ -0,0 +1 @@ +subsecond.patch diff -Nru libio-async-perl-0.51/debian/patches/subsecond.patch libio-async-perl-0.51/debian/patches/subsecond.patch --- libio-async-perl-0.51/debian/patches/subsecond.patch 1970-01-01 01:00:00.0 +0100 +++ libio-async-perl-0.51/debian/patches/subsecond.patch 2012-08-15 17:56:05.0 +0200 @@ -0,0 +1,73 @@ +Origin: upstream, http://bazaar.leonerd.org.uk/perl/IO-Async/, r1044 +Bug: https://rt.cpan.org/Ticket/Display.html?id=78892 +Bug-Debian: http://bugs.debian.org/680790 +Reviewed-by: gregor herrmann gre...@debian.org +Applied-Upstream: yes, in bzr and since 0.51_001 + +revno 1044 +From: Paul LeoNerd Evans leon...@leonerd.org.uk +Date: Tue 2012-06-26 23:58:58 +0100 +Branch-Nick: IO-Async +Subject: Allow Loops to declare for unit-test purposes that they can't + handle subsecond timers accurately, so skip the counter tests + +--- + lib/IO/Async/Loop.pm |4 + lib/IO/Async/LoopTests.pm | 32 ++-- + 2 files changed, 22 insertions(+), 14 deletions(-) + +--- a/lib/IO/Async/Loop.pm b/lib/IO/Async/Loop.pm +@@ -16,6 +16,10 @@ + # Base value but some classes might override + use constant _CAN_ON_HANGUP = 0; + ++# Some Loop implementations do not accurately handle sub-second timers. ++# This only matters for unit tests ++use constant _CAN_SUBSECOND_ACCURATELY = 1; ++ + use Carp; + + use IO::Socket (); # empty import +--- a/lib/IO/Async/LoopTests.pm b/lib/IO/Async/LoopTests.pm +@@ -464,21 +464,25 @@ + } +} 1.5, 2.5, 'loop_once(5) while waiting for timer'; + +- # Check that short delays are achievable in one -loop_once call +- foreach my $delay ( 0.001, 0.01, 0.1 ) { +- my $done; +- my $count = 0; +- my $start = time; +- +- $loop-enqueue_timer( delay = $delay, code = sub { $done++ } ); +- +- while( !$done ) { +- $loop-loop_once( 1 ); +- $count++; +- last if time - $start 5; # bailout +- } ++ SKIP: { ++ skip Unable to handle sub-second timers accurately, 3 unless $loop-_CAN_SUBSECOND_ACCURATELY; ++ ++ # Check that short delays are achievable in one -loop_once call ++ foreach my $delay ( 0.001, 0.01, 0.1 ) { ++ my $done; ++ my $count = 0; ++ my $start = time; ++ ++
Bug#682908: Is this a done deal?
On Wed, Aug 15, 2012 at 11:27:07AM -0400, Jordi Gutiérrez Hermoso wrote: Emacs 24 has been in pre-release mode So... not actually released then. Anyways, this doesn't answer my question, which I've asked thrice. Here it goes again: is this a done deal, and we're getting an ancient (yes, ancient) Emacs version for wheezy? You've had your answer. Please don't post on this subject again. Neil -- signature.asc Description: Digital signature
Bug#682908: Is this a done deal?
On 15 August 2012 12:52, Neil McGovern ne...@debian.org wrote: On Wed, Aug 15, 2012 at 11:27:07AM -0400, Jordi Gutiérrez Hermoso wrote: Emacs 24 has been in pre-release mode So... not actually released then. Just because the Emacs devs are ultra-conservative. 24 has been in use by large swaths of the Emacs community for a long time. Anyways, this doesn't answer my question, which I've asked thrice. Here it goes again: is this a done deal, and we're getting an ancient (yes, ancient) Emacs version for wheezy? You've had your answer. Please don't post on this subject again. No, I have not. I still have not had a clear answer that there is no way to get a modern Emacs into wheezy. Just please say yes if this is the case. Thanks, - Jordi G. H. -- 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/CAPHS2gzO20UKRvxhjTagL_SsrHM79AOPj=dnvdgxuxniqs0...@mail.gmail.com
Bug#682740: nmu: python-gevent_0.13.6-1+b1
Package: release.debian.org Followup-For: Bug #682740 This bug is still present, and a binNMU should fix it. I've updated the package's bug (#645833) with the most recent error message, which is: import gevent __main__:1: UserWarning: libevent version mismatch: system version is '2.0.19-stable' but this gevent is compiled against '2.0.16-stable' -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing'), (100, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-3-amd64 (SMP w/12 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.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/20120815171941.42924.42055.report...@zomm.kitwarein.com
Bug#684913: (pre-)unblock: cupt/2.5.9
On 2012-08-14 19:34, Adam D. Barratt wrote: Please go ahead, thanks. Thanks, Adam. Uploaded. -- Eugene V. Lyubimkin aka JackYF, JID: jackyf.devel(maildog)gmail.com C++ GNU/Linux userspace developer, Debian Developer -- 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/20120815180004.GB4945@r500-debian
Bug#685000: marked as done (unblock: libio-async-perl/0.51-3)
Your message dated Wed, 15 Aug 2012 19:54:32 +0100 with message-id 1345056872.16998.0.ca...@jacala.jungle.funky-badger.org and subject line Re: Bug#685000: unblock: libio-async-perl/0.51-3 has caused the Debian Bug report #685000, regarding unblock: libio-async-perl/0.51-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.) -- 685000: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=685000 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 libio-async-perl: unblock libio-async-perl/0.51-3 0.51-3 fixes the RC bug #680790. It adds a patch from upstream, that's already included in 0.51_001, 0.51_002 and 0.52. Changelog entry: libio-async-perl (0.51-3) unstable; urgency=low * Add patch subsecond.patch, backported from upstream: subsecond timer tests are skipped unless unit-tests require them, since they are not reliable for all Loop implementations. Thanks to Paul LeoNerd Evans (upstream author) for pointing me to the fix. (Closes: #680790) -- gregor herrmann gre...@debian.org Wed, 15 Aug 2012 17:55:42 +0200 Full debdiff attached. Thanks in advance, gregor -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCAAGBQJQK8syAAoJELs6aAGGSaoGs28P/RBt7DQM2c3rvHk+ucc/zkxh dEZaPOaO0f57GxfEAxCcXPj4MDoWswknPvPSg39DH4eidewLeOuz597QATcfE2Qd s0dD0Lc8+V1ASx4oSVDl+L2SGGQXtFc+tOyDBy7uMckMzJt5UZDbSvmq/ZR2y2lM HNvZaK1G8HHhIwU2J9usJ+AnlB+qnC5mR3zyPlbBFB9nrt+d3tVxAjoFvFvJiECS 3r+QtdLw2H4NF6OGAXMAh98pG9meLG27cHycuQ2Y4LwdUvkjQ+VSUwafdxvaGvXF Wn6rWS3tkQ5yEIeBhymp2xTDfBvRAi6UrK3syMMkdIhLgQV7QlMdaNfF+SWRTetV +Kf2NP6WCtwSPG6/4eJf5zMIyFmntGJM7YYi+ZjYEUrNPf7dwodURjcaYI6ORFlG QS8sWu27Jq5vJ3CMXi/e4aQxA9rif5J/+qrPgcSMDSZed5BvNege1HVcl6dKdeuv wPP2gADCbJNrOrFV+zoi0vrhxvzJd+hB7cYXde0Mx67r7Di3bzGuAp3DTr4i+ROj 0ntb6mOILp2DBQ2VKkqWAXnwhHV+VPCp5jpF3jRM+pXRSupVWG9cLN6bIbLgpTxm 21Ap3E4WgE4aElGys5xwxOhgmaM/ig0FqR26Q8i7L6VG4ny6p3DRUkA757Hd+FgC IXUDEER6quPGdSUcSMBq =bgCT -END PGP SIGNATURE- diff -Nru libio-async-perl-0.51/debian/changelog libio-async-perl-0.51/debian/changelog --- libio-async-perl-0.51/debian/changelog 2012-07-08 23:19:29.0 +0200 +++ libio-async-perl-0.51/debian/changelog 2012-08-15 17:56:05.0 +0200 @@ -1,3 +1,12 @@ +libio-async-perl (0.51-3) unstable; urgency=low + + * Add patch subsecond.patch, backported from upstream: subsecond timer +tests are skipped unless unit-tests require them, since they are not +reliable for all Loop implementations. Thanks to Paul LeoNerd Evans +(upstream author) for pointing me to the fix. (Closes: #680790) + + -- gregor herrmann gre...@debian.org Wed, 15 Aug 2012 17:55:42 +0200 + libio-async-perl (0.51-2) unstable; urgency=low * Team upload. diff -Nru libio-async-perl-0.51/debian/patches/series libio-async-perl-0.51/debian/patches/series --- libio-async-perl-0.51/debian/patches/series 1970-01-01 01:00:00.0 +0100 +++ libio-async-perl-0.51/debian/patches/series 2012-08-15 17:56:05.0 +0200 @@ -0,0 +1 @@ +subsecond.patch diff -Nru libio-async-perl-0.51/debian/patches/subsecond.patch libio-async-perl-0.51/debian/patches/subsecond.patch --- libio-async-perl-0.51/debian/patches/subsecond.patch 1970-01-01 01:00:00.0 +0100 +++ libio-async-perl-0.51/debian/patches/subsecond.patch 2012-08-15 17:56:05.0 +0200 @@ -0,0 +1,73 @@ +Origin: upstream, http://bazaar.leonerd.org.uk/perl/IO-Async/, r1044 +Bug: https://rt.cpan.org/Ticket/Display.html?id=78892 +Bug-Debian: http://bugs.debian.org/680790 +Reviewed-by: gregor herrmann gre...@debian.org +Applied-Upstream: yes, in bzr and since 0.51_001 + +revno 1044 +From: Paul LeoNerd Evans leon...@leonerd.org.uk +Date: Tue 2012-06-26 23:58:58 +0100 +Branch-Nick: IO-Async +Subject: Allow Loops to declare for unit-test purposes that they can't + handle subsecond timers accurately, so skip the counter tests + +--- + lib/IO/Async/Loop.pm |4 + lib/IO/Async/LoopTests.pm | 32 ++-- + 2 files changed, 22 insertions(+), 14 deletions(-) + +--- a/lib/IO/Async/Loop.pm b/lib/IO/Async/Loop.pm +@@ -16,6 +16,10 @@ + # Base value but some classes might override + use constant _CAN_ON_HANGUP = 0; + ++# Some Loop implementations do not accurately handle sub-second timers. ++# This only matters for unit tests ++use constant _CAN_SUBSECOND_ACCURATELY = 1; ++ + use Carp; + + use IO::Socket (); # empty import +--- a/lib/IO/Async/LoopTests.pm
Bug#684988: marked as done (unblock: libio-async-loop-glib-perl/0.20-2)
Your message dated Wed, 15 Aug 2012 19:56:44 +0100 with message-id 1345057004.16998.2.ca...@jacala.jungle.funky-badger.org and subject line Re: Bug#684988: unblock: libio-async-loop-glib-perl/0.20-2 has caused the Debian Bug report #684988, regarding unblock: libio-async-loop-glib-perl/0.20-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.) -- 684988: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684988 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 libio-async-loop-glib-perl. unblock libio-async-loop-glib-perl/0.20-2 0.20-2 fixes RC bug #680806. The upload adds a patch provided by upstream that removes the assumption that POLLHUP would work reliably -- which it doesn't. Upstream bug: https://rt.cpan.org/Public/Bug/Display.html?id=78891 Changelog: libio-async-loop-glib-perl (0.20-2) unstable; urgency=low * Add patch pollhup.patch: remove declaration that IO::Async::Loop::Glib can handle on_hangup. POLLHUP is not reliable to detect that the reader has closed their end of a pipe. Thanks to Paul Evans (upstream author) for the patch. (Closes: #680806) -- gregor herrmann gre...@debian.org Wed, 15 Aug 2012 15:12:49 +0200 Complete debdiff attached. Thank in advance, gregor -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCAAGBQJQK6V1AAoJELs6aAGGSaoGU8MQAJ+3En+cYOor7VVPCkle6rq1 3Sbq5ftzf0nNTyh2HBrex3FeFkjf0LZcsnulkvz2cxa/WByQHGVP3GMe9LmOi9GG bRspMxa6y4TNJaeuDtOB34Z97IzZgl8SnZGcjFqY1JR2OmozxG8ke65ptI8g3Nal Z6Co4WrlwlC6c2fO9FeO8CG8Fwfc3pqZFowwD3EXhp91OxbbFhUtiFbmJfL2kd5E 2Q28MQugIVhUjwYS2YEFDG4nNmHiszdDmPNE+eFYBQDW1mmuoS7gvuHyFRNqCjPw lnDUt/vbanR9Nu87qoa4Q95QgovMJECxqkbN771kSbljIF4/PdUrM5EzlusG/jS6 YRNHEsE6Oo9TunEuMTR2Opt0dHdxqPnS9h5zO5VBfBEP/dzV0KvMFxf3Ml32yAJU Ly8nzmL49CXWEI0KUVtc9ynsS2Uz2/jakXMc8mgfsrEigxrFm1aptgWgksy75mr1 Kr7OZUVP2EHuLQafn6uQWxuoZGQ7TXz0F2cezgeyf3Jg5BVhIgi1TFVZ/GIRcb2j gfRAWaxOkxJIUV4396LbsZPFXmaabJYQmmGO970CBu36kFaUGRUGppb5CwpDRMcL qH8R9dYp99s8jO4X0vZ/kp8+vhyW8V7KczHU26aOTJDSlQQv244bfTRDFBaRIkA2 NpuWHeBCbJSkBo9x+56Y =s2eq -END PGP SIGNATURE- diff -Nru libio-async-loop-glib-perl-0.20/debian/changelog libio-async-loop-glib-perl-0.20/debian/changelog --- libio-async-loop-glib-perl-0.20/debian/changelog 2011-09-18 18:23:28.0 +0200 +++ libio-async-loop-glib-perl-0.20/debian/changelog 2012-08-15 15:16:32.0 +0200 @@ -1,3 +1,12 @@ +libio-async-loop-glib-perl (0.20-2) unstable; urgency=low + + * Add patch pollhup.patch: remove declaration that IO::Async::Loop::Glib +can handle on_hangup. POLLHUP is not reliable to detect that the +reader has closed their end of a pipe. Thanks to Paul Evans (upstream +author) for the patch. (Closes: #680806) + + -- gregor herrmann gre...@debian.org Wed, 15 Aug 2012 15:12:49 +0200 + libio-async-loop-glib-perl (0.20-1) unstable; urgency=low * Team upload. diff -Nru libio-async-loop-glib-perl-0.20/debian/patches/pollhup.patch libio-async-loop-glib-perl-0.20/debian/patches/pollhup.patch --- libio-async-loop-glib-perl-0.20/debian/patches/pollhup.patch 1970-01-01 01:00:00.0 +0100 +++ libio-async-loop-glib-perl-0.20/debian/patches/pollhup.patch 2012-08-15 15:16:32.0 +0200 @@ -0,0 +1,22 @@ +Description: remove IaLoop::Glib's declaration that it can handle on_hangup + [The bug] comes from an expectation on my part hat POLLHUP was actually + reliable across operating systems, to detect that the reader has closed + their end of a pipe. Turns out this really isn't the case at all. +Origin: upstream, RT#78891 +Bug: http://rt.cpan.org/Public/Bug/Display.html?id=78891 +Bug-Debian: http://bugs.debian.org/680806 +Author: Paul Evans leon...@leonerd.org.uk +Reviewed-by: gregor herrmann gre...@debian.org +Last-Update: 2012-08-15 + +--- a/lib/IO/Async/Loop/Glib.pm b/lib/IO/Async/Loop/Glib.pm +@@ -13,7 +13,7 @@ + + # Only Linux is known always to be able to report EOF conditions on + # filehandles using POLLHUP +-use constant _CAN_ON_HANGUP = ( $^O eq linux ); ++#use constant _CAN_ON_HANGUP = ( $^O eq linux ); + + use base qw( IO::Async::Loop ); + IO::Async::Loop-VERSION( '0.33' ); diff -Nru libio-async-loop-glib-perl-0.20/debian/patches/series libio-async-loop-glib-perl-0.20/debian/patches/series --- libio-async-loop-glib-perl-0.20/debian/patches/series 1970-01-01 01:00:00.0 +0100 +++ libio-async-loop-glib-perl-0.20/debian/patches/series 2012-08-15 15:16:32.0
Bug#684063: marked as done (unblock: denemo/0.9.2-2)
Your message dated Wed, 15 Aug 2012 13:26:39 -0600 with message-id 20120815192639.GJ19694@localhost and subject line Re: Bug#684063: unblock: denemo/0.9.2-2 has caused the Debian Bug report #684063, regarding unblock: denemo/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.) -- 684063: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684063 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 denemo denemo/0.9.2-2 fixes: #665520 Including individual glib headers no longer supported #683563 Enable hardened build flags denemo (0.9.2-2) unstable; urgency=low * glib-single-include.diff Patch added in order to include glib.h instead of individual header. Thanks to Michael Biebl for his help to fix this bug (closes: 665520). * debian/control - New maintainer address. Thanks to Jan Hauke Rahm for his sponsorships. - Standards Version updated to 3.9.3: No changes required. * Denemo now uses security hardening build flags (closes: 683563) - debian/compat, and debian/control build dependency on debhelper, raised to 9 in order to set environment variables listed by dpkg-buildflags by default. - format_error_strings.diff patch added to format error strings safely. Debdiff (against denemo/0.9.2-1 which is in testing) attached. unblock denemo/0.9.2-2 diff -Nru denemo-0.9.2/debian/changelog denemo-0.9.2/debian/changelog --- denemo-0.9.2/debian/changelog 2011-10-04 16:35:55.0 -0600 +++ denemo-0.9.2/debian/changelog 2012-08-02 14:25:25.0 -0600 @@ -1,3 +1,19 @@ +denemo (0.9.2-2) unstable; urgency=low + + * glib-single-include.diff Patch added in order to include glib.h +instead of individual header. Thanks to Michael Biebl for his help to +fix this bug (closes: 665520). + * debian/control +- New maintainer address. Thanks to Jan Hauke Rahm for his sponsorships. +- Standards Version updated to 3.9.3: No changes required. + * Denemo now uses security hardening build flags (closes: 683563) +- debian/compat, and debian/control build dependency on debhelper, + raised to 9 in order to set environment variables listed by + dpkg-buildflags by default. +- format_error_strings.diff patch added to format error strings safely. + + -- Josue Abarca jmasli...@debian.org Fri, 27 Jul 2012 23:37:51 -0600 + denemo (0.9.2-1) unstable; urgency=low * New upstream release diff -Nru denemo-0.9.2/debian/compat denemo-0.9.2/debian/compat --- denemo-0.9.2/debian/compat 2011-10-04 16:35:55.0 -0600 +++ denemo-0.9.2/debian/compat 2012-08-02 14:25:25.0 -0600 @@ -1 +1 @@ -7 +9 diff -Nru denemo-0.9.2/debian/control denemo-0.9.2/debian/control --- denemo-0.9.2/debian/control 2011-10-04 16:35:55.0 -0600 +++ denemo-0.9.2/debian/control 2012-08-02 14:25:25.0 -0600 @@ -1,15 +1,15 @@ Source: denemo Section: sound Priority: optional -Maintainer: Josue Abarca jmasli...@debian.org.gt +Maintainer: Josue Abarca jmasli...@debian.org DM-Upload-Allowed: yes -Build-Depends: debhelper (= 7.0.50~), guile-1.8-dev, +Build-Depends: debhelper (= 9), guile-1.8-dev, libaubio-dev, portaudio19-dev, libfftw3-dev, libgtk2.0-dev, libxml2-dev, libsamplerate0-dev, automake, libtool, libgtksourceview2.0-dev, libfluidsynth-dev, autoconf, automake1.11, libsmf-dev (= 1.3), autopoint, librsvg2-dev, dh-autoreconf Build-Conflicts: autoconf2.13, automake1.4 -Standards-Version: 3.9.2 +Standards-Version: 3.9.3 Vcs-Git: git://anonscm.debian.org/collab-maint/denemo.git Vcs-Browser: http://anonscm.debian.org/gitweb/?p=collab-maint/denemo.git Homepage: http://www.denemo.org diff -Nru denemo-0.9.2/debian/patches/format_error_strings.diff denemo-0.9.2/debian/patches/format_error_strings.diff --- denemo-0.9.2/debian/patches/format_error_strings.diff 1969-12-31 18:00:00.0 -0600 +++ denemo-0.9.2/debian/patches/format_error_strings.diff 2012-08-02 14:25:25.0 -0600 @@ -0,0 +1,26 @@ +Description: This patch adds string literals + to format error strings in the g_print function. This is required by + -Werror=format-security to avoid format string attacks. This pacth + was backported in order to be able to use security hardening build + flags via dpkg-buildflags. + +Origin: upstream, http://git.savannah.gnu.org/gitweb/?p=denemo.git;a=commitdiff;h=e17c5abd +Author: Jeremiah Benham jjben...@chicagoguitar.com +Bug-Debian: http://bugs.debian.org/683563 +Last-Update: 2012-08-02 +
cdimage.debian.org down?
Hi, Title says it all. Where to find weekly built netinst isos (or unstable)? -- 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/1345061939.25812.1.ca...@hp.my.own.domain
Re: cdimage.debian.org down?
On Wed, 2012-08-15 at 22:18 +0200, Svante Signell wrote: Title says it all. Where to find weekly built netinst isos (or unstable)? It seems to work fine for me. In any case, the Release Team aren't responsible for cdimage.d.o. See http://www.debian.org/CD/faq/ for more appropriate contact points; debian-cd@ would probably have been a reasonable starting point. 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/1345063000.16998.5.ca...@jacala.jungle.funky-badger.org
Bug#682908: Is this a done deal?
On Wed, 15 Aug 2012 13:15:44 -0400 Jordi Gutiérrez Hermoso jord...@octave.org wrote: On 15 August 2012 12:52, Neil McGovern ne...@debian.org wrote: On Wed, Aug 15, 2012 at 11:27:07AM -0400, Jordi Gutiérrez Hermoso wrote: Emacs 24 has been in pre-release mode So... not actually released then. Just because the Emacs devs are ultra-conservative. 24 has been in use by large swaths of the Emacs community for a long time. Doesn't matter. That version was not released until three weeks before the Debian freeze and did not get uploaded so could not be tested within Debian. That version was not ready for a stable Debian release as it failed to meet Debian quality requirements, despite upstream testing. This very bug report starts with a patch for architecture-specific problems which would have been release-critical, indicating that upstream did not release a version of emacs24 which was acceptable for immediate adoption within Debian. This is quite common, few upstreams have the resources to test on all Debian architectures. Therefore, the use of 24 in the community is irrelevant - the version of emacs24 released so close to the Debian freeze date was *not* suitable for Debian and needed specific work by the maintainer at DebConf to fix. (Thanks to Rob for doing the work.) The fixed version would need testing but there is now no time to get that into Wheezy. Anyways, this doesn't answer my question, which I've asked thrice. Here it goes again: is this a done deal, and we're getting an ancient (yes, ancient) Emacs version for wheezy? You've had your answer. Please don't post on this subject again. No, I have not. I still have not had a clear answer that there is no way to get a modern Emacs into wheezy. Just please say yes if this is the case. Three different people in Debian have already told you that emacs24 will not be in Wheezy. Adding more complaints is not going to encourage anyone to change their minds. emacs23 is in Wheezy and cannot be considered ancient as it was the modern emacs up until a few short weeks before the deadline. The chance to get emacs24 into wheezy has come and gone. emacs24 was not released early enough by upstream to be uploaded into Debian. When it was released by upstream, it was not ready for inclusion into Debian testing without the patch provided by the maintainer, which took time to develop. The upstream release date was just too close to the Debian freeze date. There was not enough time to get the upstream release packaged, fixed and tested within Debian, so there is now no route for emacs24 to get into Wheezy. Important fixes from 24 could be backported to 23 and those may well be approved by the release team, so work with the emacs maintainer. Adam has already pointed this out. The Debian freeze deadline was announced a year in advance, if this was such a pressing issue, you could have started working with the Debian maintainer and upstream months ago to push for an earlier release of 24 and an earlier upload to Debian - maybe by pushing pre-releases of 24 into experimental. The current Debian maintainer has already indicated that he is happy with not having 24 in Wheezy due to the lack of time for testing and the release critical bug in the original emacs24 release which he had to patch. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=682908#13 This is my final contribution to this bug - I don't even use emacs. I'm just trying to help the release team concentrate on more useful parts of the freeze rather than repeatedly answering the same question with the same answer. The decision has been made, emacs24 was not and is not ready for inclusion into Wheezy, the window for it to be considered has closed. Wheezy will have emacs23, not emacs24 but emacs24 is certainly a candidate for backports. -- Neil Williams = http://www.linux.codehelp.co.uk/ pgp44LrIDdRoJ.pgp Description: PGP signature
Bug#682908: Is this a done deal?
On 15 August 2012 16:42, Neil Williams codeh...@debian.org wrote: Three different people in Debian have already told you that emacs24 will not be in Wheezy. No, actually, you're the first person to outright say it Thanks. - Jordi G. H. -- 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/CAPHS2gxynUQuqtT3=cDswkUfQ6apE2z2Z2p03uxJFq=jycm...@mail.gmail.com
NEW changes in stable-new
Processing changes file: clamav_0.97.5+dfsg-6~squeeze1_amd64.changes REJECT -- 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/e1t1ke6-gf...@franck.debian.org
Bug#685019: unblock: denemo/0.9.2-3
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package denemo The last changes are based in the feedback that I got from: #684063 unblock: denemo/0.9.2-2 denemo/0.9.2-3 fixes: #665520 Including individual glib headers no longer supported #683563 Enable hardened build flags (Current version in testing: 0.9.2-1) denemo (0.9.2-3) unstable; urgency=low * Set the environment variables listed by dpkg-buildflags using a less intrusive approach: - debian/rules override_dh_auto_configure added to set the environment variables listed by dpkg-buildflags. - debian/compat changed from 9 to 7 - debian/control debhelper build dependency version reverted from 9 to 7.0.50~ denemo (0.9.2-2) unstable; urgency=low * glib-single-include.diff Patch added in order to include glib.h instead of individual header. Thanks to Michael Biebl for his help to fix this bug (closes: 665520). * debian/control - New maintainer address. Thanks to Jan Hauke Rahm for his sponsorships. - Standards Version updated to 3.9.3: No changes required. * Denemo now uses security hardening build flags (closes: 683563) - debian/compat, and debian/control build dependency on debhelper, raised to 9 in order to set environment variables listed by dpkg-buildflags by default. - format_error_strings.diff patch added to format error strings safely. Debdiff (against denemo/0.9.2-1 which is in testing) attached. unblock denemo/0.9.2-3 -- System Information: Debian Release: wheezy/sid Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=es_GT.utf8, LC_CTYPE=es_GT.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash diff -Nru denemo-0.9.2/debian/changelog denemo-0.9.2/debian/changelog --- denemo-0.9.2/debian/changelog 2011-10-04 16:35:55.0 -0600 +++ denemo-0.9.2/debian/changelog 2012-08-14 07:44:27.0 -0600 @@ -1,3 +1,31 @@ +denemo (0.9.2-3) unstable; urgency=low + + * Set the environment variables listed by dpkg-buildflags using +a less intrusive approach: +- debian/rules override_dh_auto_configure added to set the + environment variables listed by dpkg-buildflags. +- debian/compat changed from 9 to 7 +- debian/control debhelper build dependency version reverted + from 9 to 7.0.50~ + + -- Josue Abarca jmasli...@debian.org Tue, 13 Aug 2012 17:08:04 -0600 + +denemo (0.9.2-2) unstable; urgency=low + + * glib-single-include.diff Patch added in order to include glib.h +instead of individual header. Thanks to Michael Biebl for his help to +fix this bug (closes: 665520). + * debian/control +- New maintainer address. Thanks to Jan Hauke Rahm for his sponsorships. +- Standards Version updated to 3.9.3: No changes required. + * Denemo now uses security hardening build flags (closes: 683563) +- debian/compat, and debian/control build dependency on debhelper, + raised to 9 in order to set environment variables listed by + dpkg-buildflags by default. +- format_error_strings.diff patch added to format error strings safely. + + -- Josue Abarca jmasli...@debian.org Fri, 27 Jul 2012 23:37:51 -0600 + denemo (0.9.2-1) unstable; urgency=low * New upstream release diff -Nru denemo-0.9.2/debian/control denemo-0.9.2/debian/control --- denemo-0.9.2/debian/control 2011-10-04 16:35:55.0 -0600 +++ denemo-0.9.2/debian/control 2012-08-14 07:44:27.0 -0600 @@ -1,7 +1,7 @@ Source: denemo Section: sound Priority: optional -Maintainer: Josue Abarca jmasli...@debian.org.gt +Maintainer: Josue Abarca jmasli...@debian.org DM-Upload-Allowed: yes Build-Depends: debhelper (= 7.0.50~), guile-1.8-dev, libaubio-dev, portaudio19-dev, libfftw3-dev, libgtk2.0-dev, @@ -9,7 +9,7 @@ libgtksourceview2.0-dev, libfluidsynth-dev, autoconf, automake1.11, libsmf-dev (= 1.3), autopoint, librsvg2-dev, dh-autoreconf Build-Conflicts: autoconf2.13, automake1.4 -Standards-Version: 3.9.2 +Standards-Version: 3.9.3 Vcs-Git: git://anonscm.debian.org/collab-maint/denemo.git Vcs-Browser: http://anonscm.debian.org/gitweb/?p=collab-maint/denemo.git Homepage: http://www.denemo.org diff -Nru denemo-0.9.2/debian/patches/format_error_strings.diff denemo-0.9.2/debian/patches/format_error_strings.diff --- denemo-0.9.2/debian/patches/format_error_strings.diff 1969-12-31 18:00:00.0 -0600 +++ denemo-0.9.2/debian/patches/format_error_strings.diff 2012-08-14 07:44:27.0 -0600 @@ -0,0 +1,26 @@ +Description: This patch adds string literals + to format error strings in the g_print function. This is required by + -Werror=format-security to avoid format string attacks. This pacth + was backported in order to be able to use security hardening build + flags via dpkg-buildflags. + +Origin: upstream, http://git.savannah.gnu.org/gitweb/?p=denemo.git;a=commitdiff;h=e17c5abd +Author: Jeremiah Benham
Bug#682908: Is this a done deal?
On Wed, Aug 15, 2012 at 04:44:38PM -0400, Jordi Gutiérrez Hermoso wrote: On 15 August 2012 16:42, Neil Williams codeh...@debian.org wrote: Three different people in Debian have already told you that emacs24 will not be in Wheezy. No, actually, you're the first person to outright say it Bullshit. [1] and [2] had a clear conclusion. [3] told you that there's no reason to add it. There was exactly no reason for four other followups of yours. And no, we're not saying we're having an ancient version of emacs in wheezy like you want us to. We have a *suitable*[4] version in wheezy. [1] 20120727095257.ga4...@spike.0x539.de [2] 87fw8dgshe@trouble.defaultvalue.org [3] 274955215eeac079d8f2ce2ba8f9e...@mail.adsl.funky-badger.org [4] By our guidelines, by any means. signature.asc Description: Digital signature
Bug#685021: unblock: redeclipse/1.2-3
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Hello, Please unblock the package redeclipse, the version currently in unstable is a security update which should go into Wheezy, see http://bugs.debian.org/684143 Thanks. unblock redeclipse/1.2-3 -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (900, 'testing'), (800, 'unstable'), (300, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120815214404.32560.67389.reportbug@mas
Bug#685021: marked as done (unblock: redeclipse/1.2-3)
Your message dated Wed, 15 Aug 2012 22:54:43 +0100 with message-id 1345067683.16998.6.ca...@jacala.jungle.funky-badger.org and subject line Re: Bug#685021: unblock: redeclipse/1.2-3 has caused the Debian Bug report #685021, regarding unblock: redeclipse/1.2-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.) -- 685021: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=685021 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 Hello, Please unblock the package redeclipse, the version currently in unstable is a security update which should go into Wheezy, see http://bugs.debian.org/684143 Thanks. unblock redeclipse/1.2-3 -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (900, 'testing'), (800, 'unstable'), (300, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash ---End Message--- ---BeginMessage--- On Wed, 2012-08-15 at 23:44 +0200, Martin Erik Werner wrote: Please unblock the package redeclipse, the version currently in unstable is a security update which should go into Wheezy, see http://bugs.debian.org/684143 Unblocked; thanks. Regards, Adam---End Message---
Supercollider in wheezy
Dear Relase Team, I write to fix the issue of supercollider in wheezy. Current SC in testing is upstream version 3.4.5. Current in sid is 3.5.3. The version in wheezy has a FTBFS bug (#674386), so we need to get rid of that. Options are: 1. Upload a fix via tpu. 2. Migrate 3.5.3 to wheezy (we had uploaded 3.5.2 before the freeze, but it didn't migrate because it didn't build in some archs. More details later). 3. Remove sc from wheezy. We would like to avoid option 3, and we favor option 2. At [1] there is a description of the changes since the uploaded 3.5.2 version before the freeze and the current version in unstable. We would prefer the 3.5 series over the 3.4 series for the following reasons: * SC 3.4.x relied optionally on a third-party java-based kit (SwingOSC) to provide for building user interface widgets. (This provides standard server- and addon-management interfaces as well as user-made GUIs. It's not compulsory to have GUIs but it's typically assumed in tutorials and the official book.) This was never packaged for debian, so the provision is kinda incomplete. SC 3.5 includes a QT-based widget system which provides all of this functionality and with the same programming interface. It's very nice. * The GEdit plugin sced has been updated to support GEdit version 3, which is what is in wheezy. (We previously just deactivated the gedit plugin in wheezy which is a shame as it's a recommended editor for beginners.) * The old and overgrown SCons build system has been removed in favour of Cmake. Requires much less downstream packaging effort. * User config files are moved to a much more XDG-friendly location: instead of ~/share/supercollider it's now ~/.local/share/SuperCollider and ~/.config/SuperCollider. (Old config is detected and migration info is output.) * Other changes, detailed in http://doc.sccode.org/Guides/News-3_5.html If a migration of sc from sid to testing is unacceptable, we can upload a fix to t-p-u. However, g++ 4.7 ICEs while building 3.4. Therefore, the fix would have to include a build-dependency on gcc/g++ 4.6 and force its use in debian/rules, besides the fix for the build failure. Full diff attached. [1] http://lists.alioth.debian.org/pipermail/pkg-multimedia-maintainers/2012-July/028351.html -- Saludos, Felipe Sateler wheezy.diff Description: Binary data
NEW changes in stable-new
Processing changes file: clamav_0.97.5+dfsg-6~squeeze1_amd64.changes REJECT Processing changes file: clamav_0.97.5+dfsg-6~squeeze1_armel.changes REJECT Processing changes file: clamav_0.97.5+dfsg-6~squeeze1_ia64.changes REJECT Processing changes file: clamav_0.97.5+dfsg-6~squeeze1_kfreebsd-amd64.changes REJECT Processing changes file: clamav_0.97.5+dfsg-6~squeeze1_kfreebsd-i386.changes REJECT Processing changes file: clamav_0.97.5+dfsg-6~squeeze1_mips.changes REJECT Processing changes file: clamav_0.97.5+dfsg-6~squeeze1_mipsel.changes REJECT Processing changes file: clamav_0.97.5+dfsg-6~squeeze1_s390.changes REJECT Processing changes file: clamav_0.97.5+dfsg-6~squeeze1_sparc.changes REJECT -- 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/e1t1lry-0005y0...@franck.debian.org
NEW changes in stable-new
Processing changes file: clamav_0.97.5+dfsg-6~squeeze1_amd64.changes ACCEPT Processing changes file: clamav_0.97.5+dfsg-6~squeeze1_armel.changes ACCEPT Processing changes file: clamav_0.97.5+dfsg-6~squeeze1_ia64.changes ACCEPT Processing changes file: clamav_0.97.5+dfsg-6~squeeze1_kfreebsd-amd64.changes ACCEPT Processing changes file: clamav_0.97.5+dfsg-6~squeeze1_kfreebsd-i386.changes ACCEPT Processing changes file: clamav_0.97.5+dfsg-6~squeeze1_mips.changes ACCEPT Processing changes file: clamav_0.97.5+dfsg-6~squeeze1_mipsel.changes ACCEPT Processing changes file: clamav_0.97.5+dfsg-6~squeeze1_s390.changes ACCEPT Processing changes file: clamav_0.97.5+dfsg-6~squeeze1_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/e1t1m1x-rc...@franck.debian.org
Bug#683367: unblock: ffgtk/0.8.1-2
Niels, thank you for having a look at this request. On 15.08.2012 16:14, Niels Thykier wrote: Control: tags -1 moreinfo On 2012-07-31 08:53, Rolf Leggewie wrote: Please unblock package ffgtk 0.8.1-2 which fixes an FTBFS induced by changes in libcapi20-dev upstream. This package appear to be brand new? If so, it is too late for Wheezy. You are right, the package entered unstable only a few days before the freeze, after waiting for sponsorship for almost half a year. The package entered NEW about a week or ten days before the freeze and miraculously made it into unstable in time for the freeze. The RC bug was not the doing of ffgtk but things broke through an upload of the isdnutils package. The ffgtk package was uploaded RC-bugs free and only broke through no fault of its own by the introduction of a new libcapi20-dev version on June 30. That being grounds for an exclusion from Wheezy wouldn't seem just. I kindly ask you to reconsider. Regards Rolf -- 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/502c36f3.3040...@rolf.leggewie.biz
Bug#685036: unblock: scim-anthy/1.2.7-5
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: freeze-exception Please unblock package scim-anthy version 1.2.7-5 It has been reported to us that the configuration setup for scim-anthy crashes for some users (bug 682601 and 680988). This is due to the recent transition in the package from gtk2 to gtk3. We've also included build-flag hardening in this upload. Please consider scim-anthy/1.2.7-5 for Wheezy. -- 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/20120816002428.14237.51348.report...@www.google-analytics.com