Bug#695450: unblock: context-doc-nonfree/2012.06.27-2
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Dear release managers, I am asking for a freeze exception for context-doc-nonfree 2012.06.27-2 which fixes a RC bug wrt placement of files under /usr/share/texmf/doc. The same happened in cm-super-minimal and was fixed there with an NMU and freeze-exempted (see bug #577635). The only change is that it stops shipping files in /usr/share/texmf/doc because this is a symlink to /usr/share/doc/texmf, and thus it depends on the order of installation of alqalam and tex-common if it really becomes a symlink or not. More details are discussed in the bug report #577635 of cm-super-minimal that had the same problems. The debdiff is minimal, here it it: diff -Nru context-doc-nonfree-2012.06.27/debian/changelog context-doc-nonfree-2012.06.27/debian/changelog --- context-doc-nonfree-2012.06.27/debian/changelog 2012-06-28 00:04:10.0 +0900 +++ context-doc-nonfree-2012.06.27/debian/changelog 2012-12-08 17:49:48.0 +0900 @@ -1,3 +1,10 @@ +context-doc-nonfree (2012.06.27-2) unstable; urgency=high + + * do not ship documentation in /usr/share/texmf/doc, as this is +a symlink (Closes: #695447) + + -- Norbert Preining prein...@debian.org Sat, 08 Dec 2012 17:49:16 +0900 + context-doc-nonfree (2012.06.27-1) unstable; urgency=low * new download from the web pages, more complete, and keep directory diff -Nru context-doc-nonfree-2012.06.27/debian/rules context-doc-nonfree-2012.06.27/debian/rules --- context-doc-nonfree-2012.06.27/debian/rules 2012-06-27 23:37:44.0 +0900 +++ context-doc-nonfree-2012.06.27/debian/rules 2012-12-08 17:49:48.0 +0900 @@ -21,9 +21,9 @@ dh_testroot dh_clean dh_installdirs usr/share/doc/$(package) \ - usr/share/texmf/doc/context/ - cp -a base $(instbase)/usr/share/texmf/doc/context/ - dh_link usr/share/texmf/doc/context/base usr/share/doc/$(package)/base + usr/share/doc/texmf/context/ + cp -a base $(instbase)/usr/share/doc/texmf/context/ + dh_link usr/share/doc/texmf/context/base usr/share/doc/$(package)/base dh_installdocs dh_installchangelogs dh_compress -X.pdf Thus, I would like to ask for an unblock. unblock context-doc-nonfree/2012.06.27-2 Thanks a lot and all the best Norbert -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.7.0-rc8+ (SMP w/4 CPU cores; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20121208092443.13931.36179.reportbug@localhost.localdomain
Bug#695451: unblock: alqalam/0.2-6
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Dear release managers, I am asking for a freeze exception for alqalam 0.2-6 which fixes a RC bug wrt placement of files under /usr/share/texmf/doc. The same happened in cm-super-minimal and was fixed there with an NMU and freeze-exempted (see bug #577635). The only change is that it stops shipping files in /usr/share/texmf/doc because this is a symlink to /usr/share/doc/texmf, and thus it depends on the order of installation of alqalam and tex-common if it really becomes a symlink or not. More details are discussed in the bug report #577635 of cm-super-minimal that had the same problems. The debdiff is minimal, here it it: diff -Nru alqalam-0.2/debian/changelog alqalam-0.2/debian/changelog --- alqalam-0.2/debian/changelog2012-11-21 13:34:55.0 +0900 +++ alqalam-0.2/debian/changelog2012-12-08 17:48:59.0 +0900 @@ -1,3 +1,10 @@ +alqalam (0.2-6) unstable; urgency=high + + * don't install documents into /usr/share/texmf/doc as this is a symlink +(see bug #577635 of cm-super-minimal) (Closes: #695446) + + -- Norbert Preining prein...@debian.org Sat, 08 Dec 2012 17:48:25 +0900 + alqalam (0.2-5) unstable; urgency=low * add myself to the uploaders diff -Nru alqalam-0.2/debian/links alqalam-0.2/debian/links --- alqalam-0.2/debian/links2012-11-21 13:34:55.0 +0900 +++ alqalam-0.2/debian/links2012-12-08 17:48:59.0 +0900 @@ -1 +1 @@ -usr/share/doc/alqalam usr/share/texmf/doc/latex/alqalam +usr/share/doc/alqalam usr/share/doc/texmf/latex/alqalam Thus, I would like to ask for an unblock. unblock alqalam/0.2-6 Thanks a lot and all the best Norbert -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.7.0-rc8+ (SMP w/4 CPU cores; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20121208092450.12963.42345.reportbug@localhost.localdomain
Bug#695430: unblock: gnome-shell/3.4.2-4
Le samedi 08 décembre 2012 à 03:35 +0100, Niels Thykier a écrit : unblock gnome-shell/3.4.2-4 Unblocked, thanks. Thank you. Note that this will require unblocking gjs for it to migrate, too (updated shlibs). -- .''`. Josselin Mouette : :' : `. `' `- -- 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/1354958704.9305.1.camel@tomoyo
Bug#687916: Zabbix: 1.8.11-1__to__2.0.2+dfsg-4
On Sat, 8 Dec 2012 19:15:36 Yves-Alexis Perez wrote: I didnd't see the debdiff, but I'm not sure that's something they'll really want to migrate at that time of the freeze. I'm attaching the diff (1.8.11-1/testing :: 2.0.2+dfsg-4/unstable) but I doubt if it'll be helpful: with more than 200 commits we rewrote ~85% of debian/* contents. Regards, Dmitry. zabbix_1.8.11-1__to__2.0.2-4.diff.gz Description: GNU Zip compressed data
Bug#689588: Please unblock cracklib2/2.8.19-2
retitle 689588 unblock: cracklib2/2.8.19-2 thanks Dear release managers, please unblock cracklib2/2.8.19-2 that I uploaded to unstable. See the debdiff that is already attached to the bug. The change is minimal and backward compatible. The test suite runs without problems with all supported Python versions (2.6, 2.7, 3.2). Best regards Jan -- Jan Dittberner - Debian Developer GPG-key: 4096R/558FB8DD 2009-05-10 B2FF 1D95 CE8F 7A22 DF4C F09B A73E 0055 558F B8DD http://ddportfolio.debian.net/ - http://people.debian.org/~jandd/ signature.asc Description: Digital signature
Processed: Please unblock cracklib2/2.8.19-2
Processing commands for cont...@bugs.debian.org: retitle 689588 unblock: cracklib2/2.8.19-2 Bug #689588 [release.debian.org] pre-approve unblock: cracklib2/2.8.19-2 Changed Bug title to 'unblock: cracklib2/2.8.19-2' from 'pre-approve unblock: cracklib2/2.8.19-2' thanks Stopping processing here. Please contact me if you need assistance. -- 689588: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=689588 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.135496594829691.transcr...@bugs.debian.org
Bug#687916: unblock: zabbix/1:2.0.2+dfsg-4
On Mon, Oct 1, 2012 at 20:07:07 +0200, Moritz Mühlenhoff wrote: For stable-security backporting security issues wasn't feasible due to a lack of continued upstream support for 1.8.x and invasive/complex changes. This shouldn't happen again. If there's no commitment from upstream to support a long term branch it should rather be removed from testing. Dmitry, is there such a commitment for 2.0.x for wheezy's lifetime? Cheers, Julien signature.asc Description: Digital signature
Bug#687666: unblock pre-approval: qt4-x11/4:4.8.2-3
On Fri, Sep 14, 2012 at 18:05:02 -0300, Lisandro Damián Nicanor Pérez Meyer wrote: Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please consider to pre-approve the unblock package qt4-x11 Hi RT! The purpose of this mail is to ask for pre-approval of a new upload of qt4-x11 in order to solve RC bug #669278. Short story: this bug is caused by the circular dependency between qdbus and libqt4-dbus. It was solved by: - adding libqtdbus4 [0] to hold the stuff that libqt4-dbus will normally provide. - make libqt4-dbus depend on qdbus and libqtdbus4. - the symbols file of libqtdbus4 depends on libqt4-dbus to ensure that a dependency on libqt4-dbus ensures qdbus is installed, also on rebuilt packages. Why are libqt4-dbus and qdbus separate packages in the first place? What happens the day libQtDBus changes SONAME? Cheers, Julien signature.asc Description: Digital signature
Re: Bug#593141: Bug#653582: ruby-hpricot: FTBFS on ia64: ruby crashes while running tests
On Fri, Dec 07, 2012 at 10:21:57PM +0100, Stephan Schreiber wrote: I took a look at this a few weeks ago. The problem is the code in the cont.c file which implements continuations. A thread saves its own stack and its thread context itself while it is running. The ruby programmers believe that that the saved info can be used by another thread to switch over. They are wrong! This is simply ill-formed code; wrong usage of the makecontext()/swapcontext() functions. It is a miracle that it works on other architectures - on sparc it did after doing some dirty tricks. The problem causes crashes which are almost impossible to understand with the debugger. The code was written in 2007 and made a lot of trouble until now; when you take a look to cont.c, you are see some really weird code fragments - dirty hacks to workaround some fundamental design flaws. I'm not satisfied with the code quality of the ruby project at all; I don't understand how it could be included in a ruby version that is for production use. So the continuations and perhaps some related threading features are broken - very advanced and new features in Ruby. I think a fix is feasable for platforms which use makecontext()/swapcontext() - as Linux is (rather than Windows Win32 functions). What can be implememnted is that a thread switches to another context/stack; the initial context/stack is saved after that. The thread switches back to the initial context/stack finally. This means: - The performance becomes worse due to additional context switches. I think it isn't that bad; the ruby code copies over huge portions of memory in its implementation all the time; the entire original code is a huge performance penalty (if it wouldn't crash). I don't believe that the additional context switches makes it noticeable worse. - The patch would be a real patch bomb. It would remove a lot of mess for (not working) ia64 workarounds and the most recent sparc patches of Debian as well. The patch replaces a lot of code of cont.c. - The patch would change the implementation for all Debian archs, not only ia64. I appreciate comments on that. Sounds good to me. It will be awesome if you could do that! :-) I would say let's get that patch written, test it, make sure it doesn't break anything, and them we can talk to upstream. I am not comfortable with carrying such a huge patch on the Debian package, since I do not have much experience of such low-level stuff. For now I'd prefer the 'wheezy-ignore' rather than removing the ia64 ruby package. Looks like this should be the way to go. -- Antonio Terceiro terce...@debian.org signature.asc Description: Digital signature
Processed: Re: Bug#691640: unblock: nss-pam-ldapd/0.8.10-3
Processing control commands: tag -1 moreinfo Bug #691640 [release.debian.org] unblock: nss-pam-ldapd/0.8.10-3 Added tag(s) moreinfo. -- 691640: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=691640 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.b691640.13549762582422.transcr...@bugs.debian.org
Bug#691640: unblock: nss-pam-ldapd/0.8.10-3
Control: tag -1 moreinfo On Sat, Oct 27, 2012 at 23:05:06 +0200, Arthur de Jong wrote: +@@ -97,39 +85,27 @@ static inline void tio_tv_prepare(struct + deadline-tv_usec=0; + return; + } +- tio_tv_add(deadline,timeout); ++ deadline-tv_sec+=timeout/1000; ++ deadline-tv_sec+=(timeout%1000)*1000; Looks to me like the second line should set tv_usec, not tv_sec Cheers, Julien signature.asc Description: Digital signature
Re: Bug#593141: Bug#653582: ruby-hpricot: FTBFS on ia64: ruby crashes while running tests
Control: tag 653582 wheezy-ignore Control: tag 593141 wheezy-ignore On Sat, Dec 8, 2012 at 11:11:56 -0300, Antonio Terceiro wrote: On Fri, Dec 07, 2012 at 10:21:57PM +0100, Stephan Schreiber wrote: For now I'd prefer the 'wheezy-ignore' rather than removing the ia64 ruby package. Looks like this should be the way to go. Agreed. Cheers, Julien signature.asc Description: Digital signature
Bug#687916: unblock: zabbix/1:2.0.2+dfsg-4
Hi Julien, On Sun, 9 Dec 2012 00:45:28 Julien Cristau wrote: On Mon, Oct 1, 2012 at 20:07:07 +0200, Moritz Mühlenhoff wrote: For stable-security backporting security issues wasn't feasible due to a lack of continued upstream support for 1.8.x and invasive/complex changes. This shouldn't happen again. If there's no commitment from upstream to support a long term branch it should rather be removed from testing. Dmitry, is there such a commitment for 2.0.x for wheezy's lifetime? Yes, I believe there is but I'm not sure how to support it with evidence. First of all I feel that Moritz' statement regarding upstream support for 1.8.x may be a bit inaccurate. As you can see from http://www.zabbix.com/rn2.0.4.php last released Zabbix 1.8.15 was published on 2012-08-20 so I'm not sure if we can already declare lack of continued upstream support for 1.8.x. Just today I was looking into old CVEs to close in stable as per discussion in #683273. I found that whenever CVE was reported to upstream using bug tracker they commit corresponding fix into dedicated branch that later got merged into trunk and 1.8 branches so it's not that difficult to isolate the changes. Of course when upstream applied security fix to version 1.8.11 it may be not too easy to backport it to 1.8.2 but I suspect this problem is not unique to Zabbix. I have very limited experience with security fixes in Zabbix (and in Debian in general) so please don't take my words as granted without feedback from Christoph and Moritz who are far more experienced that I am. However to put this situation to proper context I'd like to mention mysql- workbench package (maintained by yours truly) where upstream doesn't have public VCS at all. Backporting fixes is only possible by reverse-engineering new tarballs releases by comparing huge changesets and trying to make sense of changes. To make matters worse upstream is not updating changelog accurate enough so you can imagine the challenges. I believe Zabbix is much better in that regards. We can't be sure how well Zabbix will be supporting 1.8.x in the future. Obviously they've switched focus to Zabbix 2.0.x and that makes it better for us to upgrade to 2.0. While we can't be sure regarding future support for 1.8 and backporting fixes was proven to be challenging (according to feedback from Christoph and Moritz) I think we're all agree that 1.8 is better to be removed from testing to minimise the risks and the maintenance burden. (I think at the moment security fixes are applied to 2.0 first, so even the delay before fix will be applicable to 1.8 is bad enough.) Personally I hope that unblocking 2.0 may be considered as current version in unstable was remarkably free of troubles but that's just my inexperienced opinion. I think Christoph is quite excited about the idea of maintaining Zabbix in backports so the tough decision regarding Zabbix' destiny in Debian is with you. :) Thank you. Regards, Dmitry. -- 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/201212090141.46740.only...@member.fsf.org
Bug#691293: marked as done (unblock: mosh/1.2.3-1)
Your message dated Sat, 8 Dec 2012 15:59:03 +0100
with message-id 20121208145903.gn5...@radis.cristau.org
and subject line Re: Bug#691293: unblock: mosh/1.2.3-1
has caused the Debian Bug report #691293,
regarding unblock: mosh/1.2.3-1
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
691293: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=691293
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,
We respectfully request that you unblock mosh 1.2.3-1 and include it
in the wheezy release. A debdiff from mosh 1.2.2-1 is available at
http://mosh.mit.edu/mosh_1.2.2-1_to_mosh-1.2.3-1.debdiff.txt .
mosh 1.2.3 is an upstream microrelease that fixes several issues we
learned about during the first six months of widespread use. It is
well-tested and has passed the regressions tests.
Most prominently, mosh now links against OpenSSL and uses OpenSSL's
implementation of AES. Previously, Mosh 1.2.2 shipped its own AES
reference implementation for licensing reasons. The reference
implementation has been criticized for possible timing leakage, and it
is preferable to avoid shipping a duplicate cipher implementation.
Mosh 1.2.3 also includes several robustness fixes, including increased
resilience when transiting problematic NATs and VPNs and compatibility
with the KDE konsole and dual-stack IPv4/v6 sshds.
More security and robustness improvements are listed in the changelog.
I regret the lateness of this upstream release in the wheezy freeze
cycle. But given the expected lifetime of wheezy as a stable release,
upstream would much rather be supporting 1.2.3 instead of 1.2.2 for
the long term. We appreciate your consideration of our request.
unblock mosh/1.2.3-1
---End Message---
---BeginMessage---
On Tue, Oct 23, 2012 at 18:44:11 -0400, Keith Winstein wrote:
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Hello,
We respectfully request that you unblock mosh 1.2.3-1 and include it
in the wheezy release. A debdiff from mosh 1.2.2-1 is available at
http://mosh.mit.edu/mosh_1.2.2-1_to_mosh-1.2.3-1.debdiff.txt .
mosh 1.2.3 is an upstream microrelease that fixes several issues we
learned about during the first six months of widespread use. It is
well-tested and has passed the regressions tests.
Most prominently, mosh now links against OpenSSL and uses OpenSSL's
implementation of AES. Previously, Mosh 1.2.2 shipped its own AES
reference implementation for licensing reasons. The reference
implementation has been criticized for possible timing leakage, and it
is preferable to avoid shipping a duplicate cipher implementation.
Mosh 1.2.3 also includes several robustness fixes, including increased
resilience when transiting problematic NATs and VPNs and compatibility
with the KDE konsole and dual-stack IPv4/v6 sshds.
More security and robustness improvements are listed in the changelog.
I regret the lateness of this upstream release in the wheezy freeze
cycle. But given the expected lifetime of wheezy as a stable release,
upstream would much rather be supporting 1.2.3 instead of 1.2.2 for
the long term. We appreciate your consideration of our request.
unblock mosh/1.2.3-1
This is on the too big side, but unblocked anyway.
One comment though:
@@ -361,11 +396,25 @@
/* close file descriptors */
if ( !verbose ) {
/* Necessary to properly detach on old versions of sshd (e.g.
RHEL/CentOS 5.0). */
-fclose( stdin );
-fclose( stdout );
-fclose( stderr );
+int nullfd;
+
+nullfd = open( /dev/null, O_RDWR );
+if ( nullfd == -1 ) {
+ perror( dup2 );
+ exit( 1 );
+}
+
+if ( dup2 ( nullfd, STDIN_FILENO ) 0 ||
+ dup2 ( nullfd, STDOUT_FILENO ) 0 ||
+ dup2 ( nullfd, STDERR_FILENO ) 0 ) {
+ perror( dup2 );
+ exit( 1 );
+}
}
+ char utmp_entry[ 64 ] = { 0 };
+ snprintf( utmp_entry, 64, mosh [%d], getpid() );
+
/* Fork child process */
pid_t child = forkpty( master, NULL, child_termios, window_size );
This hunk seems to leak nullfd?
Cheers,
Julien
signature.asc
Description: Digital signature
---End Message---
Bug#692074: marked as done (unblock: procps/1:3.3.5-1)
Your message dated Sat, 8 Dec 2012 16:03:40 +0100 with message-id 20121208150340.go5...@radis.cristau.org and subject line Re: Bug#692074: unblock: procps/1:3.3.5-1 has caused the Debian Bug report #692074, regarding unblock: procps/1:3.3.5-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.) -- 692074: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=692074 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 procps procps 3.3.5-1 is blocked because libproc1 is new. The problem is that the oldest libproc0 will not work with 3.3.5-1 because the API changed. This means current if you install procps 3.3.4 with libproc0 3.3.4 you have an unbootable system. Critical bug 691847 is against procps 3.3.4 but I'd like this cleared up. unblock procps/1:3.3.5-1 -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-3-amd64 (SMP w/2 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash diff -Nru procps-3.3.4/configure procps-3.3.5/configure --- procps-3.3.4/configure 2012-10-29 22:04:42.0 +1100 +++ procps-3.3.5/configure 2012-10-30 22:24:28.0 +1100 @@ -1,6 +1,6 @@ #! /bin/sh # Guess values for system-dependent variables and create Makefiles. -# Generated by GNU Autoconf 2.69 for procps-ng 3.3.4. +# Generated by GNU Autoconf 2.69 for procps-ng 3.3.5. # # Report bugs to pro...@freelists.org. # @@ -590,8 +590,8 @@ # Identity of this package. PACKAGE_NAME='procps-ng' PACKAGE_TARNAME='procps-ng' -PACKAGE_VERSION='3.3.4' -PACKAGE_STRING='procps-ng 3.3.4' +PACKAGE_VERSION='3.3.5' +PACKAGE_STRING='procps-ng 3.3.5' PACKAGE_BUGREPORT='pro...@freelists.org' PACKAGE_URL='http://gitorious.org/procps' @@ -1359,7 +1359,7 @@ # Omit some internal or obsolete options to make the list less imposing. # This message is too long to be a string in the A/UX 3.1 sh. cat _ACEOF -\`configure' configures procps-ng 3.3.4 to adapt to many kinds of systems. +\`configure' configures procps-ng 3.3.5 to adapt to many kinds of systems. Usage: $0 [OPTION]... [VAR=VALUE]... @@ -1429,7 +1429,7 @@ if test -n $ac_init_help; then case $ac_init_help in - short | recursive ) echo Configuration of procps-ng 3.3.4:;; + short | recursive ) echo Configuration of procps-ng 3.3.5:;; esac cat \_ACEOF @@ -1559,7 +1559,7 @@ test -n $ac_init_help exit $ac_status if $ac_init_version; then cat \_ACEOF -procps-ng configure 3.3.4 +procps-ng configure 3.3.5 generated by GNU Autoconf 2.69 Copyright (C) 2012 Free Software Foundation, Inc. @@ -2039,7 +2039,7 @@ This file contains any messages produced by compilers while running configure, to aid debugging if configure makes a mistake. -It was created by procps-ng $as_me 3.3.4, which was +It was created by procps-ng $as_me 3.3.5, which was generated by GNU Autoconf 2.69. Invocation command line was $ $0 $@ @@ -2857,7 +2857,7 @@ # Define the identity of the package. PACKAGE='procps-ng' - VERSION='3.3.4' + VERSION='3.3.5' cat confdefs.h _ACEOF @@ -16644,7 +16644,7 @@ # report actual input values of CONFIG_FILES etc. instead of their # values after options handling. ac_log= -This file was extended by procps-ng $as_me 3.3.4, which was +This file was extended by procps-ng $as_me 3.3.5, which was generated by GNU Autoconf 2.69. Invocation command line was CONFIG_FILES= $CONFIG_FILES @@ -16711,7 +16711,7 @@ cat $CONFIG_STATUS _ACEOF || ac_write_fail=1 ac_cs_config=`$as_echo $ac_configure_args | sed 's/^ //; s/[\\\`\$]//g'` ac_cs_version=\\ -procps-ng config.status 3.3.4 +procps-ng config.status 3.3.5 configured by $0, generated by GNU Autoconf 2.69, with options \\\$ac_cs_config\\ diff -Nru procps-3.3.4/debian/changelog procps-3.3.5/debian/changelog --- procps-3.3.4/debian/changelog 2012-10-29 22:36:52.0 +1100 +++ procps-3.3.5/debian/changelog 2012-10-30 22:36:28.0 +1100 @@ -1,3 +1,12 @@ +procps (1:3.3.5-1) unstable; urgency=low + + * New upstream version + * bumped SONAME of packages Closes: #691847 + * Stop SIGFPE on vmstat at times Closes: #677903 + * Upstream took freebsd bug patch + + -- Craig Small csm...@debian.org Tue, 30 Oct 2012 22:26:52 +1100 + procps (1:3.3.4-1) unstable; urgency=low * New upstream version diff -Nru
Bug#693387: Pre-approval for unblock: sysvinit/2.88dsf-33
Control: retitle -1 Pre-approval for unblock: sysvinit/2.88dsf-35 On Thu, Nov 15, 2012 at 22:32:19 +, Roger Leigh wrote: The attached debdiff includes a correction to the init script dependencies for the three bootclean scripts. (#677097) You don't need pre-approval for RC bug fixes, you can just go ahead and upload... Cheers, Julien signature.asc Description: Digital signature
Processed: Re: Bug#693387: Pre-approval for unblock: sysvinit/2.88dsf-33
Processing control commands: retitle -1 Pre-approval for unblock: sysvinit/2.88dsf-35 Bug #693387 [release.debian.org] Pre-approval for unblock: sysvinit/2.88dsf-33 Changed Bug title to 'Pre-approval for unblock: sysvinit/2.88dsf-35' from 'Pre-approval for unblock: sysvinit/2.88dsf-33' -- 693387: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=693387 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.b693387.135497926522526.transcr...@bugs.debian.org
Bug#693550: unblock: mame/0.146-5
On Sat, Nov 17, 2012 at 20:46:15 +0100, Emmanuel Kasper wrote: Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package mame Dear Release Team The mame package available in testing crashes on Pentium IV due to the abuse of gcc optimize flags in the packaging code. This has been reported in the launchpad bug 1063993 and fixed in mame/0.146-5. Why does this change it to -mtune=generic instead of just nothing at all? mame/0.146-5 also adds support for DEB_BUILD_OPTIONS=parallel which might help the build infrastructure, as mame can monopolize a buildd up to 6 hours. Finally, mame/0.146-5 includes minor changes in the default configuration file, as we want to revert an unfortunate commit which slipped through. (debdiff will be included, but right now it is treated as spam by bugs-master.debian.org ...) This one needs more details because I don't know what it's trying to fix, and what impact it has. Also there's a change to readme.debian which is not listed in the changelog. Cheers, Julien signature.asc Description: Digital signature
Re: Update on state of Mono for Wheezy
On Wed, 2012-08-08 at 18:38 +0100, Jo Shields wrote: = Bug#682284: mono-runtime: SIGSEGV while executing native code on armhf[0] = This got solved via: 2) remove armhf as an architecture for Mono, in the end. CVE-2012-3543 came along just afterwards and things seem to have fallen off the radar a little after that. :-( Currently, wheezy still has a version of mono that generates armhf binaries. requiring a sourceful upload of src:mono plus an arch-specific removal on a bunch of arch:any packages plus some sourceful uploads on packages maintained by other teams which generate Mono-related packages, typically very large messy packages from the -med or -science teams. I've been having a look this afternoon at what would be required to migrate the new mono package. britney says that a number of binary packages get broken on armhf: source activiz.net: libactiviz.net-cil source fsgateway: fsgateway source mod-mono: libapache2-mod-mono source gdcm: libgdcm-cil libvtkgdcm-cil source mummy: libkitware-mummy-runtime1.0-cil source mono-fuse: libmono-fuse-cil source virtuoso-opensource: libvirtuoso5.5-cil A dak rm dry run reveals no runtime issues which removals for the above would cause, but: Checking reverse dependencies... # Broken Build-Depends: activiz.net: libkitware-mummy-runtime1.0-cil gdcm: libactiviz.net-cil The packages listed above are the only non-arch:all packages produced by activiz.net, fsgateway, mod-mono and mono-fuse so a straight binary removal should work okay; the build-dependencies should ensure the binaries don't re-appear. virtuoso-opensource produces a bunch of other binaries, but a simple architecture changing sourceful upload (as for s390) should suffice. mummy also produces the mummy binary, so would need a sourceful upload to drop the -cil package. It has a libunwind dependency so would also need a tpu due to the libunwind8 mess. :-( For added fun, the package is in sync between testing and unstable, so would need an unstable upload first followed by an appropriately versioned tpu. gdcm has a new upstream in unstable so would also need an eventual fix to go via tpu. 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/1354981560.19225.24.ca...@jacala.jungle.funky-badger.org
Bug#694617: unblock (pre-approval): konsole/4:4.8.4-2
Alle venerdì 7 dicembre 2012, Niels Thykier ha scritto: On 2012-11-28 13:31, Pino Toscano wrote: Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Hi, I would like to upload konsole 4:4.8.4-2 with the following two changes: - konsole-dbg recommends kdelibs5-dbg - backport an upstream patch to simplify/fix the search of executables; upstream recommended us to provide it, he fixed that while working on another bug Attached the current diff out of the packaging repo of the changes above. Thanks, -- Pino Hi, Please go ahead and let us know when it has been rebuilt on the relevant architectures. Thank you; it has been uploaded a couple of hours ago, and built fine everywhere. Thanks, -- Pino Toscano signature.asc Description: This is a digitally signed message part.
Bug#695236: marked as done (unblock: axis/1.4-16.1)
Your message dated Sat, 08 Dec 2012 16:33:07 +
with message-id 1354984387.19225.28.ca...@jacala.jungle.funky-badger.org
and subject line Re: Bug#695236: unblock: axis/1.4-16.1
has caused the Debian Bug report #695236,
regarding unblock: axis/1.4-16.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.)
--
695236: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=695236
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 axis
Thanks to Alberto Fernández Martínez inf...@gmail.com
CVE-2012-5784 (=bug #692650) was fixed and I just sponsered
his NMU. Debdiff is attached.
unblock axis/1.4-16.1
-- System Information:
Debian Release: 6.0.6
Architecture: i386 (i686)
Kernel: Linux 2.6.36-xenU-4814-i386 (SMP w/1 CPU core)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
diff -Nru axis-1.4/debian/changelog axis-1.4/debian/changelog
--- axis-1.4/debian/changelog 2011-11-08 05:58:09.0 +0100
+++ axis-1.4/debian/changelog 2012-12-05 17:51:30.0 +0100
@@ -1,3 +1,10 @@
+axis (1.4-16.1) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * Fix CVE-2012-5784 (Closes: #692650)
+
+ -- Alberto Fernández Martínez inf...@gmail.com Wed, 5 Dec 2012 17:28:00 +0100
+
axis (1.4-16) unstable; urgency=low
* Add missing dependency on libcommons-httpclient-java
diff -Nru axis-1.4/debian/patches/06-fix-CVE-2012-5784.patch axis-1.4/debian/patches/06-fix-CVE-2012-5784.patch
--- axis-1.4/debian/patches/06-fix-CVE-2012-5784.patch 1970-01-01 01:00:00.0 +0100
+++ axis-1.4/debian/patches/06-fix-CVE-2012-5784.patch 2012-11-17 18:54:16.0 +0100
@@ -0,0 +1,304 @@
+Description: Validates the hostname requested is the same in the certificate in ssl-connections
+ Fixes CVE-2012-5784, validates hostname certificate in SSL connections.
+ Backported from http-client 4, and from Apache Synapse (plus some bugfixes).
+
+Author: Alberto Fernandez inf...@gmail.com
+Bug-Debian: http://bugs.debian.org/692650
+Forwarded: no
+
+
+
+--- axis-1.4.orig/src/org/apache/axis/components/net/JSSESocketFactory.java
axis-1.4/src/org/apache/axis/components/net/JSSESocketFactory.java
+@@ -19,6 +19,8 @@ import org.apache.axis.utils.Messages;
+ import org.apache.axis.utils.XMLUtils;
+ import org.apache.axis.utils.StringUtils;
+
++import javax.net.ssl.SSLException;
++import javax.net.ssl.SSLSession;
+ import javax.net.ssl.SSLSocket;
+ import javax.net.ssl.SSLSocketFactory;
+ import java.io.BufferedWriter;
+@@ -28,7 +30,15 @@ import java.io.OutputStream;
+ import java.io.OutputStreamWriter;
+ import java.io.PrintWriter;
+ import java.net.Socket;
++import java.security.cert.Certificate;
++import java.security.cert.CertificateParsingException;
++import java.security.cert.X509Certificate;
++import java.util.Arrays;
++import java.util.Collection;
+ import java.util.Hashtable;
++import java.util.Iterator;
++import java.util.LinkedList;
++import java.util.List;
+
+
+ /**
+@@ -41,6 +51,10 @@ import java.util.Hashtable;
+ */
+ public class JSSESocketFactory extends DefaultSocketFactory implements SecureSocketFactory {
+
++// This is a a sorted list, if you insert new elements do it orderdered.
++private final static String[] BAD_COUNTRY_2LDS =
++{ac, co, com, ed, edu, go, gouv, gov, info,
++lg, ne, net, or, org};
+ /** Field sslFactory */
+ protected SSLSocketFactory sslFactory = null;
+
+@@ -187,6 +201,255 @@ public class JSSESocketFactory extends D
+ if (log.isDebugEnabled()) {
+ log.debug(Messages.getMessage(createdSSL00));
+ }
++verifyHostName(host, (SSLSocket) sslSocket);
+ return sslSocket;
+ }
++/**
++ * Verifies that the given hostname in certicifate is the hostname we are trying to connect to
++ * http://www.cvedetails.com/cve/CVE-2012-5783/
++ * @param host
++ * @param ssl
++ * @throws IOException
++ */
++
++ private static void verifyHostName(String host, SSLSocket ssl)
++ throws IOException {
++ if (host == null) {
++ throw new IllegalArgumentException(host to verify was null);
++ }
++
++ SSLSession session = ssl.getSession();
++ if (session == null) {
++// In our experience this only happens under IBM 1.4.x when
++// spurious (unrelated) certificates show up in the server's chain.
++// Hopefully this will unearth the real problem:
++ InputStream in =
Bug#695234: marked as done (unblock: commons-httpclient/3.1-10.1)
Your message dated Sat, 08 Dec 2012 16:37:04 +
with message-id 1354984624.19225.29.ca...@jacala.jungle.funky-badger.org
and subject line Re: Bug#695234: unblock: commons-httpclient/3.1-10.1
has caused the Debian Bug report #695234,
regarding unblock: commons-httpclient/3.1-10.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.)
--
695234: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=695234
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 commons-httpclient
Thanks to Alberto Fernández Martínez inf...@gmail.com
CVE-2012-5783 (= bug #692442) was closed and I just uploaded
his NMU. Debdiff is attached to the bug report.
unblock commons-httpclient/3.1-10.1
-- System Information:
Debian Release: 6.0.6
Architecture: i386 (i686)
Kernel: Linux 2.6.36-xenU-4814-i386 (SMP w/1 CPU core)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
diff -Nru commons-httpclient-3.1/debian/changelog commons-httpclient-3.1/debian/changelog
--- commons-httpclient-3.1/debian/changelog 2011-08-30 19:13:26.0 +0200
+++ commons-httpclient-3.1/debian/changelog 2012-12-05 17:44:48.0 +0100
@@ -1,3 +1,10 @@
+commons-httpclient (3.1-10.1) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * Fix CVE-2012-5783 (Closes: #692442)
+
+ -- Alberto Fernández Martínez inf...@gmail.com Wed, 5 Dec 2012 17:28:00 +0100
+
commons-httpclient (3.1-10) unstable; urgency=low
[ Damien Raude-Morvan ]
diff -Nru commons-httpclient-3.1/debian/patches/06_fix_CVE-2012-5783.patch commons-httpclient-3.1/debian/patches/06_fix_CVE-2012-5783.patch
--- commons-httpclient-3.1/debian/patches/06_fix_CVE-2012-5783.patch 1970-01-01 01:00:00.0 +0100
+++ commons-httpclient-3.1/debian/patches/06_fix_CVE-2012-5783.patch 2012-11-17 18:01:18.0 +0100
@@ -0,0 +1,371 @@
+Description: Validates the hostname requested is the same in the certificate in ssl-connections
+ Fixes CVE-2012-5783, validates hostname certificate in SSL connections.
+ Backported from http-client 4, and from Apache Synapse (plus some bugfixes).
+
+Author: Alberto Fernandez inf...@gmail.com
+Bug-Debian: http://bugs.debian.org/692442
+Forwarded: no
+
+
+--- commons-httpclient-3.1.orig/src/java/org/apache/commons/httpclient/protocol/SSLProtocolSocketFactory.java
commons-httpclient-3.1/src/java/org/apache/commons/httpclient/protocol/SSLProtocolSocketFactory.java
+@@ -31,11 +31,23 @@
+ package org.apache.commons.httpclient.protocol;
+
+ import java.io.IOException;
++import java.io.InputStream;
+ import java.net.InetAddress;
+ import java.net.Socket;
+ import java.net.UnknownHostException;
+
++import javax.net.ssl.SSLException;
++import javax.net.ssl.SSLSession;
++import javax.net.ssl.SSLSocket;
+ import javax.net.ssl.SSLSocketFactory;
++import java.security.cert.Certificate;
++import java.security.cert.CertificateParsingException;
++import java.security.cert.X509Certificate;
++import java.util.Arrays;
++import java.util.Collection;
++import java.util.Iterator;
++import java.util.LinkedList;
++import java.util.List;
+
+ import org.apache.commons.httpclient.ConnectTimeoutException;
+ import org.apache.commons.httpclient.params.HttpConnectionParams;
+@@ -55,6 +67,11 @@ public class SSLProtocolSocketFactory im
+ */
+ private static final SSLProtocolSocketFactory factory = new SSLProtocolSocketFactory();
+
++// This is a a sorted list, if you insert new elements do it orderdered.
++private final static String[] BAD_COUNTRY_2LDS =
++{ac, co, com, ed, edu, go, gouv, gov, info,
++lg, ne, net, or, org};
++
+ /**
+ * Gets an singleton instance of the SSLProtocolSocketFactory.
+ * @return a SSLProtocolSocketFactory
+@@ -79,12 +96,14 @@ public class SSLProtocolSocketFactory im
+ InetAddress clientHost,
+ int clientPort)
+ throws IOException, UnknownHostException {
+-return SSLSocketFactory.getDefault().createSocket(
++Socket sslSocket = SSLSocketFactory.getDefault().createSocket(
+ host,
+ port,
+ clientHost,
+ clientPort
+ );
++verifyHostName(host, (SSLSocket) sslSocket);
++return sslSocket;
+ }
+
+ /**
+@@ -124,16 +143,19 @@ public class SSLProtocolSocketFactory im
+ }
+ int timeout = params.getConnectionTimeout();
+ if (timeout == 0) {
+-return createSocket(host,
Processed: user release.debian....@packages.debian.org, tagging 694108, tagging 694109
Processing commands for cont...@bugs.debian.org: user release.debian@packages.debian.org Setting user to release.debian@packages.debian.org (was a...@adam-barratt.org.uk). tags 694108 - pending + confirmed Bug #694108 [release.debian.org] unblock: kfreebsd-8/8.3-6 Removed tag(s) pending. Bug #694108 [release.debian.org] unblock: kfreebsd-8/8.3-6 Added tag(s) confirmed. tags 694109 - pending + confirmed Bug #694109 [release.debian.org] unblock: kfreebsd-9/9.0-10 Removed tag(s) pending. Bug #694109 [release.debian.org] unblock: kfreebsd-9/9.0-10 Added tag(s) confirmed. thanks Stopping processing here. Please contact me if you need assistance. -- 694108: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=694108 694109: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=694109 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.13549859692574.transcr...@bugs.debian.org
Bug#674634: marked as done (transition: celt)
Your message dated Sat, 08 Dec 2012 16:59:26 + with message-id 1354985966.19225.30.ca...@jacala.jungle.funky-badger.org and subject line Re: Bug#674634: transition: celt has caused the Debian Bug report #674634, regarding transition: celt 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.) -- 674634: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=674634 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: transition Hi, We'd like to remove the celt package from the distro for the Wheezy release. CELT was an experimental codec from Xiph, and that work has now been merged into the Opus codec which is about to be ratified as an IETF standard. As a result of that, upstream is no longer maintaining celt at all, and being an experimental codec, no two releases of it were ever bitstream compatible with each other (and only one release was ever made that even maintained API compatibility with prior versions). All packages using it at the time knew and accepted that this would be the situation with it while it evolved ... The version that Debian currently is shipping we tried to get consensus on people agreeing to consider it an interoperability snapshot before squeeze, but in the end that never actually happened in practice and other distros shipped other incompatible versions of it anyway. So we (meaning myself, upstream, and anyone else who has discussed this with us in detail) see little value in continuing to ship this, and plenty of opportunity for Harm. Apps using it in Debian will only be interoperable with the Debian releases of themselves, there will be no security support, and it will just further fragment the codec space, at a time when there is a real standard alternative people should be looking at for the future. I'd have moved on this sooner, but it's only been in the last few days that we actually had enough certainty about the IETF process concluding to really know what the foreseeable future of all this was going to be. I've already been actively talking to upstreams of the affected packages to be sure we might actually pull this off in the time we have remaining, and I'm sure enough that this will be possible now to really propose a formal course of action for Wheezy. We've been planning for this in general terms for years now, but nothing could actually move until the IETF did. And now they have. Death, taxes, and bad timing. Anyhow, this actually should be fairly simple, being an experimental codec almost everything already has support for only optionally enabling it. So we just need sourceful uploads of packages to turn it off - then celt can safely be removed. Some of the deps have already been updated to remove it, the remaining ones as of yesterday were: # Broken Depends: gst-plugins-bad0.10: gstreamer0.10-plugins-bad jack-audio-connection-kit: jackd1 jackd2: jackd2 libjack-jackd2-0 mangler: libventrilo3-0 opal: libopal3.10.4 [amd64 armel armhf i386 ia64 kfreebsd-amd64 kfreebsd-i386 mips mipsel powerpc s390 s390x sparc] roaraudio: libroar2 roaraudio Opal I've been told will remove it with its next upload. Mangler appears to be under control, details here: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=674244 gst, I've spoken to upstream and this is a no-brainer, but I still need to get a ping back from slomo about updating the package. jack should be just disable the option too, but I'm still chasing its Debian maintainer for confirmation of doing it. Worst case I should be able to do a trivial NMU myself. Roar, I've been assured by its upstream is likewise easy to just disable support for it - but the-me is giving me some pointless pushback ... I'll NMU that too when the time comes if really needed if this is the final blocker. There shouldn't be any other flow on from this so far as I know. Some of these packages may enable Opus support instead, but doing so is not a prerequisite for us being able to remove celt for Wheezy. Thanks! Ron ---End Message--- ---BeginMessage--- On Sat, 2012-05-26 at 18:38 +0930, Ron wrote: We'd like to remove the celt package from the distro for the Wheezy release. That finally happened a few weeks ago (modulo the embedded copy in mumble); closing. Regards, Adam---End Message---
Bug#687666: unblock pre-approval: qt4-x11/4:4.8.2-3
On Sat 08 Dec 2012 10:59:44 Julien Cristau escribió: On Fri, Sep 14, 2012 at 18:05:02 -0300, Lisandro Damián Nicanor Pérez Meyer wrote: Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please consider to pre-approve the unblock package qt4-x11 Hi RT! The purpose of this mail is to ask for pre-approval of a new upload of qt4-x11 in order to solve RC bug #669278. Short story: this bug is caused by the circular dependency between qdbus and libqt4-dbus. It was solved by: - adding libqtdbus4 [0] to hold the stuff that libqt4-dbus will normally provide. - make libqt4-dbus depend on qdbus and libqtdbus4. - the symbols file of libqtdbus4 depends on libqt4-dbus to ensure that a dependency on libqt4-dbus ensures qdbus is installed, also on rebuilt packages. Why are libqt4-dbus and qdbus separate packages in the first place? libqt4-dbus used to ship both the library and qdbus, an application. As part of the multiarchification of Qt4, they needed to become separate packages. What happens the day libQtDBus changes SONAME? It will not in wheezy. And we are already working in a proper transition for stuff that currently depends on libqt4-dbus just because they actually need qdbus. So for Jessie we will eliminate libqtdbus4. And, by the way we mangled the symbols files, no package should depend on libqtdbus4 ever (symbols point to libqt4-dbus). Kinds regards, Lisandro. -- 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.
NEW changes in stable-new
Processing changes file: xen_4.0.1-5.5_amd64.changes ACCEPT Processing changes file: xen_4.0.1-5.5_i386.changes ACCEPT Processing changes file: iceape_2.0.11-17_amd64.changes ACCEPT Processing changes file: iceape_2.0.11-17_armel.changes ACCEPT Processing changes file: iceape_2.0.11-17_i386.changes ACCEPT Processing changes file: iceape_2.0.11-17_ia64.changes ACCEPT Processing changes file: iceape_2.0.11-17_kfreebsd-amd64.changes ACCEPT Processing changes file: iceape_2.0.11-17_kfreebsd-i386.changes ACCEPT Processing changes file: iceape_2.0.11-17_mips.changes ACCEPT Processing changes file: iceape_2.0.11-17_mipsel.changes ACCEPT Processing changes file: iceape_2.0.11-17_powerpc.changes ACCEPT Processing changes file: iceape_2.0.11-17_s390.changes ACCEPT Processing changes file: iceape_2.0.11-17_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/e1tho26-0005oz...@franck.debian.org
Bug#695471: unblock: bootchart2/0.14.4-2
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Hello RT, I just uploaded bootchart2/0.14.4-2 to unstable. This upload fixes RC bug #694403 -- the package shipped a systemd unit, but no classic initscript. I'm attaching a git diff -- please note that this is a particular initscript, since starting it effectively *stops* the daemon -- and that's why it's started after all the other services (i.e. stop collecting boot info as soon as all other initscripts did their job). unblock bootchart2/0.14.4-2 Thanks, David -- . ''`. Debian developer | http://wiki.debian.org/DavidPaleino : :' : Linuxer #334216 --|-- http://www.hanskalabs.net/ `. `'` GPG: 1392B174 | http://deb.li/dapal `- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174 diff --git a/debian/bootchart2.bootchart-done.init b/debian/bootchart2.bootchart-done.init new file mode 100644 index 000..da3f590 --- /dev/null +++ b/debian/bootchart2.bootchart-done.init @@ -0,0 +1,58 @@ +#! /bin/sh + +### BEGIN INIT INFO +# Provides: bootchart2 +# Required-Start:$remote_fs $all +# Required-Stop: +# Default-Start: 1 2 3 4 5 +# Default-Stop: +# Short-Description: Stop bootchartd +# Description: This script stops the bootchartd daemon after the +#system booted. +### END INIT INFO + +# Author: David Paleino da...@debian.org + +# Do NOT set -e + +# PATH should only include /usr/* if it runs after the mountnfs.sh script +PATH=/sbin:/usr/sbin:/bin:/usr/bin +DESC=boot process analyser +NAME=bootchartd +DAEMON=/sbin/$NAME +DAEMON_ARGS= +PIDFILE=/var/run/$NAME.pid +SCRIPTNAME=/etc/init.d/bootchart2 + +# Exit if the package is not installed +[ -x $DAEMON ] || exit 0 + +# Read configuration variable file if it is present +[ -r /etc/bootchartd.conf ] . /etc/bootchartd.conf + +# Load the VERBOSE setting and other rcS variables +. /lib/init/vars.sh + +# Define LSB log_* functions. +# Depend on lsb-base (= 3.0-6) to ensure that this file is present. +. /lib/lsb/init-functions + +case $1 in + start) + [ $VERBOSE != no ] log_daemon_msg Stopping $DESC $NAME + $DAEMON stop + case $? in + 0|1) [ $VERBOSE != no ] log_end_msg 0 ;; + 2) [ $VERBOSE != no ] log_end_msg 1 ;; + esac + ;; + stop|restart|force-reload) + # do nothing + ;; + *) + echo Usage: $SCRIPTNAME start 2 + exit 3 + ;; +esac + +: diff --git a/debian/changelog b/debian/changelog index 9876687..a769a35 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,10 @@ +bootchart2 (0.14.4-2) unstable; urgency=low + + * Acknowledge NMU. + * Provide also an initscript (Closes: #694403) + + -- David Paleino da...@debian.org Sat, 08 Dec 2012 19:35:08 +0100 + bootchart2 (0.14.4-1.1) unstable; urgency=low * Non-maintainer upload. diff --git a/debian/rules b/debian/rules index 0b97af1..158f0dc 100755 --- a/debian/rules +++ b/debian/rules @@ -13,3 +13,8 @@ override_dh_installchangelogs: override_dh_auto_test: +override_dh_installinit: + dh_installinit \ + --name=bootchart-done \ + --no-start \ + --update-rcd-params=start 99 1 2 3 4 5 6 . stop 99 0 . signature.asc Description: PGP signature
Re: Bug#682247: unblock: libanyevent-i3-perl/0.12-1
Hi, Michael Stapelberg stapelb...@debian.org writes: Dear release team: I want to upload a new version of libanyevent-i3-perl to testing-proposed-updates which is the same version as currently in testing + commits http://code.stapelberg.de/git/AnyEvent-I3/commit/?id=79798dc40cc25379507355b67d7f88802668a75b http://code.stapelberg.de/git/AnyEvent-I3/commit/?id=d082a57d47eb15d257c0c14de8ace10db72a5050 http://code.stapelberg.de/git/AnyEvent-I3/commit/?id=a122bde5d5d3b6d61701d8286e4b21b4f047193b As previously discussed, these commits make for a much better scripting experience without breaking anything else. Given that they are released for over two months and there were no bugreports, I consider them stable. It has been pointed out to me that I should provide a debdiff of my proposed upload, so find one attached. Do you approve this upload to t-p-u? -- Best regards, Michael libanyevent-i3-perl.debdiff Description: Binary data
Re: Bug#693208: clang unable to link trivial test program on armhf
On Mon, 26 Nov 2012 13:25:12 +0100 Sylvestre Ledru sylves...@debian.org wrote: Regarding the current clang packages in the repositories (3.0 in testing, 3.1 in unstable), you would have to add an epoch to downgrade clang to 3.0 in unstable with a fix and then have to fix migrated to testing. This would also fix the issue above, but epochs are, well, not beautiful... What is your opinion regarding those issues? I don't know. It is why I asked to the release team for guidance. IMO, the correct way to deal with this is to prepare an upload of clang 3.0-7 (currently in testing is 3.0-6) which includes *ONLY* the fix necessary for closing this bugreport. I have looked at both versions (3.0-6 and 3.2~rc3), but I can’t say for sure which change it is. Afterwards, generate a debdiff between clang_3.0-6.dsc and clang_3.0-7.dsc and attach it to this bugreport, asking the release team for approval to upload it to testing-proposed-updates. See also: http://www.debian.org/doc/manuals/developers-reference/pkgs.html#t-p-u http://release.debian.org/wheezy/freeze_policy.html -- Best regards, Michael -- 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/20121208222413.69963...@midna.rag.lan
Bug#690655: marked as done (RM: openvas2 [wheezy] -- RoM; abandoned-upstream)
Your message dated Sat, 08 Dec 2012 23:57:50 +0100 with message-id 50c3c5ee.6050...@thykier.net and subject line Re: Bug#690655: RM: openvas2 [wheezy] -- RoM; abandoned-upstream has caused the Debian Bug report #690655, regarding RM: openvas2 [wheezy] -- RoM; abandoned-upstream 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.) -- 690655: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=690655 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: release.debian.org Version: N/A Priority: grave Tags: rm I would like to request the Release Managers to remove *all* of the OpenVAS 2.x packages from the current testing distribution. This includes the following packages: - libopenvas2 / libopenvas2-dev (version 2.0.4-2.1) - libopenvasnasl2 / libopenvasnasl2-dev (version 2.0.2-2.1) - openvas-client (version 2.0.5-1.1) - openvas-plugins-base / openvas-plugins-dfsg (version 1:20100705-2) - openvas-server / openvas-server-dev (version 2.0.3-6) In addition, please also remove the following package: - harden-remoteaudit: it depends on openvas-server (I have sent a bug to the package to update this dependency) Support for OpenVAS 2 was discontinued last year [2]. Providing OpenVAS 2 to our Debian 'stable' users in our upcoming release is not really a good idea. Even though the scanner/client works 'as it is', users will not be able to download new plugins for this release from the OpenVAs servers and it will not be possible for them to find recent vulnerabilities in hosts they scan. For the last 2 years I have provided experimental versions of OpenVAS 3, which seem to have not received to much attention from users. In any case since that version is also going to be discontinued upstream. Since the latest OpenVAS release is version 5 [1] (released May this year) I will work towards providing OpenVAS 5 in our unstable distribution. And, once available, will try to make backports available for Wheezy too. Removing the OpenVAS 2 packages from testing simplifies handling upgrades to the newer version and also installations of the backports of OpenVAS 5 packages in Wheezy. Regards Javier signature.asc Description: Digital signature ---End Message--- ---BeginMessage--- On 2012-12-08 05:00, Niels Thykier wrote: [...] I have added a removal hint for these packages (except openvas-plugins-base, which wasn't in testing). I also added RC bugs against packages that didn't have one already to ensure they don't re-enter testing by accident. For reference that would be #695439, #695440 and #695441. [...] ... and packages removed, closing. Thanks, ~Niels---End Message---
Bug#694617: marked as done (unblock (pre-approval): konsole/4:4.8.4-2)
Your message dated Sun, 09 Dec 2012 00:01:06 +0100
with message-id 50c3c6b2.7070...@thykier.net
and subject line Re: Bug#694617: unblock (pre-approval): konsole/4:4.8.4-2
has caused the Debian Bug report #694617,
regarding unblock (pre-approval): konsole/4:4.8.4-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.)
--
694617: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=694617
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,
I would like to upload konsole 4:4.8.4-2 with the following two
changes:
- konsole-dbg recommends kdelibs5-dbg
- backport an upstream patch to simplify/fix the search of executables;
upstream recommended us to provide it, he fixed that while working
on another bug
Attached the current diff out of the packaging repo of the changes
above.
Thanks,
--
Pino
diff --git a/debian/changelog b/debian/changelog
index 5afb9a2..bf56122 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,15 @@
+konsole (4:4.8.4-2) UNRELEASED; urgency=low
+
+ [ Lisandro Damián Nicanor Pérez Meyer ]
+ * konsole-dbg now recommends kdelibs5-dbg.
+
+ [ Pino Toscano ]
+ * Backport upstream commit e48cee6cca742a5bdb3daf6fa0b7c76073217faa to avoid
+looking up executables when an absolute path is specified; patch
+upstream_No-need-to-lookup-executable-PATH-when-absolute-path.patch.
+
+ -- Debian Qt/KDE Maintainers debian-qt-...@lists.debian.org Tue, 23 Oct 2012 18:29:05 -0300
+
konsole (4:4.8.4-1) unstable; urgency=low
* New upstream release.
diff --git a/debian/control b/debian/control
index 755aaf2..2daa69c 100644
--- a/debian/control
+++ b/debian/control
@@ -34,6 +34,7 @@ Priority: extra
Depends: ${misc:Depends}, konsole (= ${binary:Version})
Breaks: kdebase-dbg ( 4:4.6.80)
Replaces: kdebase-dbg ( 4:4.6.80)
+Recommends: kdelibs5-dbg
Description: debugging symbols for the KDE X terminal emulator
This package contains debugging files used to investigate problems with
binaries included in the KDE X terminal emulator.
diff --git a/debian/patches/series b/debian/patches/series
index 93acb4d..5047970 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -1,2 +1,3 @@
one_profile_per_window.diff
debian-T-addition.diff
+upstream_No-need-to-lookup-executable-PATH-when-absolute-path.patch
diff --git a/debian/patches/upstream_No-need-to-lookup-executable-PATH-when-absolute-path.patch b/debian/patches/upstream_No-need-to-lookup-executable-PATH-when-absolute-path.patch
new file mode 100644
index 000..4d2d53c
--- /dev/null
+++ b/debian/patches/upstream_No-need-to-lookup-executable-PATH-when-absolute-path.patch
@@ -0,0 +1,30 @@
+From e48cee6cca742a5bdb3daf6fa0b7c76073217faa Mon Sep 17 00:00:00 2001
+From: Jekyll Wu adap...@gmail.com
+Date: Thu, 1 Nov 2012 11:57:42 +0800
+Subject: [PATCH] No need to lookup executable PATH when absolute path is
+ given (cherry picked from commit
+ d12aead588ec09359633eb9de5f9ac2b2a7e1e06)
+
+---
+ src/Session.cpp |5 +
+ 1 file changed, 5 insertions(+)
+
+diff --git a/src/Session.cpp b/src/Session.cpp
+index 732858d..cf325b0 100644
+--- a/src/Session.cpp
b/src/Session.cpp
+@@ -369,6 +369,11 @@ QString Session::checkProgram(const QString program)
+ if (exec.isEmpty())
+ return QString();
+
++QFileInfo info(exec);
++if (info.isAbsolute() info.exists() info.isExecutable()) {
++return exec;
++}
++
+ exec = KRun::binaryName(exec, false);
+ exec = KShell::tildeExpand(exec);
+ QString pexec = KStandardDirs::findExe(exec);
+--
+1.7.10.4
+
---End Message---
---BeginMessage---
On 2012-12-08 16:59, Pino Toscano wrote:
[...]
Thank you; it has been uploaded a couple of hours ago, and built fine
everywhere.
Thanks,
Unblocked, thanks.
~Niels---End Message---
Bug#694913: marked as done (unblock: im-config/0.19)
Your message dated Sun, 09 Dec 2012 00:15:58 +0100 with message-id 50c3ca2e.9060...@thykier.net and subject line Re: Bug#694913: unblock: im-config/0.19 has caused the Debian Bug report #694913, regarding unblock: im-config/0.19 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.) -- 694913: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=694913 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 im-config Applications started by dbus do not get proper keyboard input for CJK locales as reported in http://bugs.debian.org/694446. The proper functioning input capability with input method is essential for CJK environment and this must be fixed before the release. In order to fix this problem, setting of environment variables must be set before dbus by moving its code execution from im-launch to 70im-config_launch and daemons needs to be started after dbus via im-launch as in 0.18. This new split behavior is realized by changing all pre-set configuration files as the following: * set environment variables if $IM_CONFIG_PHASE=1 * start daemon programs if $IM_CONFIG_PHASE=2 70im-config_launch and im-launch are changed to use this new feature. The debdiff against the package in testing is attached. unblock im-config/0.19 -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (10, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.6-trunk-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash diff -Nru im-config-0.18/70im-config_launch im-config-0.19/70im-config_launch --- im-config-0.18/70im-config_launch 2012-08-11 15:55:23.0 +0900 +++ im-config-0.19/70im-config_launch 2012-11-29 00:12:41.0 +0900 @@ -11,6 +11,32 @@ IMLAUNCH=/usr/bin/im-launch +# If already tweaked, keep hands off :-) +# If im-config is removed but not purged, keep hands off :-) +if [ -z $XMODIFIERS ] \ + [ -z $GTK_IM_MODULE ] \ + [ -z $QT_IM_MODULE ] \ + [ -z $QT4_IM_MODULE ] \ + [ -z $CLUTTER_IM_MODULE ] \ + [ -r /usr/share/im-config/xinputrc.common ]; then +IM_CONFIG_PHASE=1 +export IM_CONFIG_PHASE +# initialize all im-config common functions and parameters +. /usr/share/im-config/xinputrc.common +# source the first found configuration file +if [ -r $IM_CONFIG_XINPUTRC_USR ]; then +. $IM_CONFIG_XINPUTRC_USR +elif [ -r $IM_CONFIG_XINPUTRC_SYS ]; then +. $IM_CONFIG_XINPUTRC_SYS +fi +# always export variables even for manual configuration. +export XMODIFIERS +export GTK_IM_MODULE +export QT_IM_MODULE +export QT4_IM_MODULE +export CLUTTER_IM_MODULE +fi + # Change $STARTUP string to im-launch while keeping the old $STARTUP string # as its arguments if [ -x $IMLAUNCH ]; then diff -Nru im-config-0.18/data/20_ibus.rc im-config-0.19/data/20_ibus.rc --- im-config-0.18/data/20_ibus.rc 2011-12-10 22:41:37.0 +0900 +++ im-config-0.19/data/20_ibus.rc 2012-11-28 23:22:48.0 +0900 @@ -1,9 +1,12 @@ # start IBus # vim: set sts=4 expandtab: +if [ $IM_CONFIG_PHASE = 2 ]; then # start IBus daemon /usr/bin/ibus-daemon --daemonize --xim +fi +if [ $IM_CONFIG_PHASE = 1 ]; then # set variables for the plain XIM XMODIFIERS=@im=ibus @@ -49,4 +52,4 @@ break fi done - +fi diff -Nru im-config-0.18/data/22_fcitx.rc im-config-0.19/data/22_fcitx.rc --- im-config-0.18/data/22_fcitx.rc 2011-12-10 22:41:32.0 +0900 +++ im-config-0.19/data/22_fcitx.rc 2012-11-28 23:22:48.0 +0900 @@ -1,9 +1,12 @@ # start fcitx # vim: set sts=4 expandtab: +if [ $IM_CONFIG_PHASE = 2 ]; then # start fcitx daemon /usr/bin/fcitx +fi +if [ $IM_CONFIG_PHASE = 1 ]; then # set variables for the plain XIM XMODIFIERS=@im=fcitx @@ -50,4 +53,4 @@ break fi done - +fi diff -Nru im-config-0.18/data/24_uim.rc im-config-0.19/data/24_uim.rc --- im-config-0.18/data/24_uim.rc 2012-08-25 11:07:35.0 +0900 +++ im-config-0.19/data/24_uim.rc 2012-11-28 23:22:48.0 +0900 @@ -1,9 +1,12 @@ # start uim # vim: set sts=4 expandtab: +if [ $IM_CONFIG_PHASE = 2 ]; then # start uim-xim daemon /usr/bin/uim-xim +fi +if [ $IM_CONFIG_PHASE = 1 ]; then # set variables for the plain XIM XMODIFIERS=@im=uim @@ -66,4 +69,4 @@ done CLUTTER_IM_MODULE=xim - +fi diff -Nru
Bug#695483: unblock: usb-modeswitch-data/20120815-2
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package usb-modeswitch-data 20120815-2. I backported only
the device additions and updates from 20121109 as released in
experimental.
The changelog is as follows and the backporting patch is attached.
usb-modeswitch-data (20120815-2) unstable; urgency=low
.
* Backport 20121109 upstream device updates:
+ New devices
[0421:0632] Nokia CS-7M-01
[05c6:1000:uMa=StrongRising] StrongRising device
[1004:6156] LG LUU-2110TI
[1004:61aa] LG VL600
[1004:6327] LG L-03D LTE/3G
[106c:3b14] Option Beemo / Pantech P4200 LTE
[12d1:14ba] Huawei E173u-2, E177
[12d1:151a] Huawei E392u-12
[12d1:1526] Vodafone / Huawei K3772
[12d1:155b] Huawei E171
[12d1:1f11] Vodafone / Huawei K3773
[1410:7001] Novatel Generic MiFi 2372 / Vodafone MiFi 2372
[19d2:0083] ZTE MF110 (Variant)
[19d2:1523] ZTE MF591 TMobile
[19d2:1542] ZTE MF190J
[1bbb:000f] ETCOM E300
[1ee8:0054] Onda MW875UP
[1fac:0150] Franklin Wireless U600
[1fac:0151] Franklin Wireless U600
× Device updates (see Changelog for details)
[0421:0627] Nokia CS-18
[0e8d:0002:uPr=MT] MediaTek MT6276M
[1199:0fff] Sierra devices (specific driver)
[12d1:1446] Huawei, newer modems
[12d1:14d1] Vodafone / Huawei K3770
[12d1:14fe] T-Mobile NL (Huawei E352)
[12d1:1505] Huawei EC156, Huawei E372u-8
[12d1:1c0b] Huawei E173s
[12d1:1da1] Huawei ET8282, Huawei ET127
[16d8:6803] C-motech D-50 (aka CDU-680, CNU-680)
[19d2:0154] ZTE MF190 (Variant) and others
[19d2:1175] Vodafone / ZTE K3770-Z
[19d2:1216] ZTE MF192+
[19d2:2000] ZTE devices
[1ab7:5700] Hummer DTM5731, Aircard 901
[1bbb:f000] Alcatel X200/X200L/X060S, Archos G9 3G Key
[1ee8:0013] Onda MW833UP
[1ee8:0040] Onda MW836UP-K
[21f5:1000] StrongRising (China Telcom), Air FlexiNet
See previous justifications for usb-modeswitch-data unblocks in #680679
and #690960, the argument line is unchanged. :-)
Cheers,
OdyX
unblock usb-modeswitch-data/20120815-2
Description: Backport all device updates from upstream 20121109.
diff --git a/40-usb_modeswitch.rules b/40-usb_modeswitch.rules
index efc05b2..a38cdc8 100644
--- a/40-usb_modeswitch.rules
+++ b/40-usb_modeswitch.rules
@@ -54,6 +54,9 @@ ATTRS{idVendor}==0421, ATTRS{idProduct}==0627, RUN+=usb_modeswitch '%b/%k'
# Nokia CS-19
ATTRS{idVendor}==0421, ATTRS{idProduct}==062c, RUN+=usb_modeswitch '%b/%k'
+# Nokia CS-7M-01
+ATTRS{idVendor}==0421, ATTRS{idProduct}==0632, RUN+=usb_modeswitch '%b/%k'
+
# Nokia CS-21M-02
ATTRS{idVendor}==0421, ATTRS{idProduct}==0637, RUN+=usb_modeswitch '%b/%k'
@@ -81,7 +84,7 @@ ATTRS{idVendor}==04e8, ATTRS{idProduct}==f000, RUN+=usb_modeswitch '%b/%k'
# AVM Fritz!Wlan USB Stick N
ATTRS{idVendor}==057c, ATTRS{idProduct}==84ff, RUN+=usb_modeswitch '%b/%k'
-# Celot K-300, Quirky Option devices, Vertex Wireless 100 Series, Option GlobeTrotter GX0201, Older Option devices, Samsung SGH-Z810, Prolink P2000 CDMA, Celot CT-680, AnyDATA devices, Bless UC165
+# Prolink P2000 CDMA, Samsung SGH-Z810, Older Option devices, Vertex Wireless 100 Series, AnyDATA devices, Bless UC165, Option GlobeTrotter GX0201, Celot K-300, Celot CT-680
ATTRS{idVendor}==05c6, ATTRS{idProduct}==1000, RUN+=usb_modeswitch '%b/%k'
# HSDPA USB modem from dealextreme
@@ -345,9 +348,15 @@ ATTRS{idVendor}==1004, ATTRS{idProduct}==613f, RUN+=usb_modeswitch '%b/%k'
# LG L-07A
ATTRS{idVendor}==1004, ATTRS{idProduct}==614e, RUN+=usb_modeswitch '%b/%k'
+# LG LUU-2110TI
+ATTRS{idVendor}==1004, ATTRS{idProduct}==6156, RUN+=usb_modeswitch '%b/%k'
+
# LG AD600
ATTRS{idVendor}==1004, ATTRS{idProduct}==6190, RUN+=usb_modeswitch '%b/%k'
+# LG VL600
+ATTRS{idVendor}==1004, ATTRS{idProduct}==61aa, RUN+=usb_modeswitch '%b/%k'
+
# LG L-02C LTE
ATTRS{idVendor}==1004, ATTRS{idProduct}==61dd, RUN+=usb_modeswitch '%b/%k'
@@ -357,6 +366,9 @@ ATTRS{idVendor}==1004, ATTRS{idProduct}==61e7, RUN+=usb_modeswitch '%b/%k'
# LG L-08C (NTT docomo)
ATTRS{idVendor}==1004, ATTRS{idProduct}==61eb, RUN+=usb_modeswitch '%b/%k'
+# LG L-03D LTE/3G
+ATTRS{idVendor}==1004, ATTRS{idProduct}==6327, RUN+=usb_modeswitch '%b/%k'
+
# Huawei E630
ATTRS{idVendor}==1033, ATTRS{idProduct}==0035, RUN+=usb_modeswitch '%b/%k'
@@ -369,6 +381,9 @@ ATTRS{idVendor}==106c, ATTRS{idProduct}==3b05, RUN+=usb_modeswitch '%b/%k'
# UTStarcom UM185E (distributor Alltel)
ATTRS{idVendor}==106c, ATTRS{idProduct}==3b06, RUN+=usb_modeswitch '%b/%k'
+# Option Beemo / Pantech P4200 LTE
+ATTRS{idVendor}==106c, ATTRS{idProduct}==3b14, RUN+=usb_modeswitch '%b/%k'
+
# Sagem F@ST 9520-35-GLR
ATTRS{idVendor}==1076, ATTRS{idProduct}==7f40, RUN+=usb_modeswitch '%b/%k'
@@ -417,6 +432,9 @@ ATTRS{idVendor}==12d1, ATTRS{idProduct}==14b5, RUN+=usb_modeswitch '%b/%k'
# Vodafone (Huawei)
Bug#695483: marked as done (unblock: usb-modeswitch-data/20120815-2)
Your message dated Sun, 09 Dec 2012 00:33:04 +0100
with message-id 50c3ce30.7070...@thykier.net
and subject line Re: Bug#695483: unblock: usb-modeswitch-data/20120815-2
has caused the Debian Bug report #695483,
regarding unblock: usb-modeswitch-data/20120815-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.)
--
695483: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=695483
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 usb-modeswitch-data 20120815-2. I backported only
the device additions and updates from 20121109 as released in
experimental.
The changelog is as follows and the backporting patch is attached.
usb-modeswitch-data (20120815-2) unstable; urgency=low
.
* Backport 20121109 upstream device updates:
+ New devices
[0421:0632] Nokia CS-7M-01
[05c6:1000:uMa=StrongRising] StrongRising device
[1004:6156] LG LUU-2110TI
[1004:61aa] LG VL600
[1004:6327] LG L-03D LTE/3G
[106c:3b14] Option Beemo / Pantech P4200 LTE
[12d1:14ba] Huawei E173u-2, E177
[12d1:151a] Huawei E392u-12
[12d1:1526] Vodafone / Huawei K3772
[12d1:155b] Huawei E171
[12d1:1f11] Vodafone / Huawei K3773
[1410:7001] Novatel Generic MiFi 2372 / Vodafone MiFi 2372
[19d2:0083] ZTE MF110 (Variant)
[19d2:1523] ZTE MF591 TMobile
[19d2:1542] ZTE MF190J
[1bbb:000f] ETCOM E300
[1ee8:0054] Onda MW875UP
[1fac:0150] Franklin Wireless U600
[1fac:0151] Franklin Wireless U600
× Device updates (see Changelog for details)
[0421:0627] Nokia CS-18
[0e8d:0002:uPr=MT] MediaTek MT6276M
[1199:0fff] Sierra devices (specific driver)
[12d1:1446] Huawei, newer modems
[12d1:14d1] Vodafone / Huawei K3770
[12d1:14fe] T-Mobile NL (Huawei E352)
[12d1:1505] Huawei EC156, Huawei E372u-8
[12d1:1c0b] Huawei E173s
[12d1:1da1] Huawei ET8282, Huawei ET127
[16d8:6803] C-motech D-50 (aka CDU-680, CNU-680)
[19d2:0154] ZTE MF190 (Variant) and others
[19d2:1175] Vodafone / ZTE K3770-Z
[19d2:1216] ZTE MF192+
[19d2:2000] ZTE devices
[1ab7:5700] Hummer DTM5731, Aircard 901
[1bbb:f000] Alcatel X200/X200L/X060S, Archos G9 3G Key
[1ee8:0013] Onda MW833UP
[1ee8:0040] Onda MW836UP-K
[21f5:1000] StrongRising (China Telcom), Air FlexiNet
See previous justifications for usb-modeswitch-data unblocks in #680679
and #690960, the argument line is unchanged. :-)
Cheers,
OdyX
unblock usb-modeswitch-data/20120815-2
Description: Backport all device updates from upstream 20121109.
diff --git a/40-usb_modeswitch.rules b/40-usb_modeswitch.rules
index efc05b2..a38cdc8 100644
--- a/40-usb_modeswitch.rules
+++ b/40-usb_modeswitch.rules
@@ -54,6 +54,9 @@ ATTRS{idVendor}==0421, ATTRS{idProduct}==0627, RUN+=usb_modeswitch '%b/%k'
# Nokia CS-19
ATTRS{idVendor}==0421, ATTRS{idProduct}==062c, RUN+=usb_modeswitch '%b/%k'
+# Nokia CS-7M-01
+ATTRS{idVendor}==0421, ATTRS{idProduct}==0632, RUN+=usb_modeswitch '%b/%k'
+
# Nokia CS-21M-02
ATTRS{idVendor}==0421, ATTRS{idProduct}==0637, RUN+=usb_modeswitch '%b/%k'
@@ -81,7 +84,7 @@ ATTRS{idVendor}==04e8, ATTRS{idProduct}==f000, RUN+=usb_modeswitch '%b/%k'
# AVM Fritz!Wlan USB Stick N
ATTRS{idVendor}==057c, ATTRS{idProduct}==84ff, RUN+=usb_modeswitch '%b/%k'
-# Celot K-300, Quirky Option devices, Vertex Wireless 100 Series, Option GlobeTrotter GX0201, Older Option devices, Samsung SGH-Z810, Prolink P2000 CDMA, Celot CT-680, AnyDATA devices, Bless UC165
+# Prolink P2000 CDMA, Samsung SGH-Z810, Older Option devices, Vertex Wireless 100 Series, AnyDATA devices, Bless UC165, Option GlobeTrotter GX0201, Celot K-300, Celot CT-680
ATTRS{idVendor}==05c6, ATTRS{idProduct}==1000, RUN+=usb_modeswitch '%b/%k'
# HSDPA USB modem from dealextreme
@@ -345,9 +348,15 @@ ATTRS{idVendor}==1004, ATTRS{idProduct}==613f, RUN+=usb_modeswitch '%b/%k'
# LG L-07A
ATTRS{idVendor}==1004, ATTRS{idProduct}==614e, RUN+=usb_modeswitch '%b/%k'
+# LG LUU-2110TI
+ATTRS{idVendor}==1004, ATTRS{idProduct}==6156, RUN+=usb_modeswitch '%b/%k'
+
# LG AD600
ATTRS{idVendor}==1004, ATTRS{idProduct}==6190, RUN+=usb_modeswitch '%b/%k'
+# LG VL600
+ATTRS{idVendor}==1004, ATTRS{idProduct}==61aa, RUN+=usb_modeswitch '%b/%k'
+
# LG L-02C LTE
ATTRS{idVendor}==1004, ATTRS{idProduct}==61dd, RUN+=usb_modeswitch '%b/%k'
@@ -357,6 +366,9 @@ ATTRS{idVendor}==1004, ATTRS{idProduct}==61e7, RUN+=usb_modeswitch
Re: Candidates for removal from testing (results)
On 2012-11-30 12:55, Niels Thykier wrote: [...] While slightly overdue; the results were 0 removals! \o/ --8-- removals.txt --8-- # #668740/#668740 remove dsc-statistics/201203250530-1 Downgraded. # #692623 remove fossil/1:1.22.1-1 Fixed in sid and wheezy (via t-p-u) # #683012/#683013 remove gnome-dvb-daemon/1:0.2.8-1 Still open, but caused by an ABI affecting multiple packages. This one should not have been on the list originally; poor manual filtering (sorry for that). # #677650 remove unhide.rb/13-1 [...] Fix in sid already unblocked. In order news, the tools for finding RC buggy leaf packages says we have run out of leaf packages (for now at least). So there will be no new list today. Hopefully it stays that way :) Thank you, ~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/50c3d451.2010...@thykier.net
Bug#695488: unblock: python-mock/0.8.0-3
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package python-mock
This upload resolved RC bug #694296, python-mock-doc: missing
Breaks+Replaces: python-mock ( 0.7.2).
Debdiff attached.
unblock python-mock/0.8.0-3
diff -Nru python-mock-0.8.0/debian/changelog python-mock-0.8.0/debian/changelog
--- python-mock-0.8.0/debian/changelog 2012-06-04 14:34:13.0 -0400
+++ python-mock-0.8.0/debian/changelog 2012-11-30 17:02:09.0 -0500
@@ -1,3 +1,12 @@
+python-mock (0.8.0-3) unstable; urgency=low
+
+ * Team upload.
+ * debian/control: python-mock-doc needs to Break/Replace
+python-mock ( 0.7.2) to ensure clean upgrades from squeeze
+to wheezy. Thanks to Andreas Beckmann (Closes: #694296).
+
+ -- Andrew Starr-Bochicchio a...@debian.org Fri, 30 Nov 2012 17:02:02 -0500
+
python-mock (0.8.0-2) unstable; urgency=low
* Add mock.egg-info/PKG-INFO to d/clean to allow two builds in a row
diff -Nru python-mock-0.8.0/debian/control python-mock-0.8.0/debian/control
--- python-mock-0.8.0/debian/control 2012-05-31 06:06:31.0 -0400
+++ python-mock-0.8.0/debian/control 2012-11-30 16:43:24.0 -0500
@@ -48,6 +48,8 @@
Section: doc
Architecture: all
Depends: ${misc:Depends}, ${sphinxdoc:Depends}
+Breaks: python-mock ( 0.7.2)
+Replaces: python-mock ( 0.7.2)
Description: Mocking and Testing Library (Documentation)
mock provides a core mock.Mock class that is intended to reduce the
need to create a host of trivial stubs throughout your test suite.
