Bug#601738: unblock: iceweasel/3.5.15-1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package iceweasel 3.5.14-1 was unblocked and due to migrate in 2 days, but there is a zero-day vulnerability fix that needed to be pushed, and that happened in 3.5.15-1. This is the only change besides the version number. You may want to boost urgency as well. Thanks unblock iceweasel/3.5.15-1 -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20101029064924.4476.75132.report...@jigen.glandium.org
Bug#601739: unblock: iceape/2.0.10-1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package iceape 2.0.9-1 was unblocked and due to migrate in 4 days, but there is a zero-day vulnerability fix that needed to be pushed, and that happened in 2.0.10-1. This is the only change besides the version number. You may want to boost urgency as well. Thanks unblock iceape/2.0.10-1 -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20101029065005.4507.64564.report...@jigen.glandium.org
Please unblock ia32-libs/20101012
Hi, A lesson we learned from Lenny is that ia32-libs is hardly security supportable if the libraries it contained aren't as much up to date as their 'normal' stable versions as possible. In the ideal situation we would release with a ia32-libs being completely up to date with the normal package versions, and the closer we get to that ideal the better security supportable it will be. Therefore I ask to please unblock 20101012 for squeeze. As far as I could check the recently updated libraries all have that version (or a slightly newer one) also present in squeeze. I would consider releasing ia32-libs with a 2009 version to be of grave concern to the security team about its supportability for the squeeze lifetime. Thanks, Thijs -- 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/c992aefa8bac125f642837c69a9c6ed1.squir...@wm.kinkhorst.nl
Re: Please unblock ia32-libs/20101012
On Fri, Oct 29, 2010 at 10:26:50 +0200, Thijs Kinkhorst wrote: > Hi, > > A lesson we learned from Lenny is that ia32-libs is hardly security > supportable if the libraries it contained aren't as much up to date as > their 'normal' stable versions as possible. In the ideal situation we > would release with a ia32-libs being completely up to date with the normal > package versions, and the closer we get to that ideal the better security > supportable it will be. Therefore I ask to please unblock 20101012 for > squeeze. > > As far as I could check the recently updated libraries all have that > version (or a slightly newer one) also present in squeeze. > > I would consider releasing ia32-libs with a 2009 version to be of grave > concern to the security team about its supportability for the squeeze > lifetime. > See #596899. AFAICT wine is still unbuildable with this version. Cheers, Julien signature.asc Description: Digital signature
Re: Please unblock ia32-libs/20101012
On Fri, Oct 29, 2010 at 10:26:50AM +0200, Thijs Kinkhorst wrote: > A lesson we learned from Lenny is that ia32-libs is hardly security > supportable if the libraries it contained aren't as much up to date as > their 'normal' stable versions as possible. In the ideal situation we > would release with a ia32-libs being completely up to date with the normal > package versions, and the closer we get to that ideal the better security > supportable it will be. Therefore I ask to please unblock 20101012 for > squeeze. It was the maintainer's decision to do changes way post-freeze that might not be suitable for squeeze. It is still possible to update the old one in squeeze with newer packages without the packaging changes or fix the remaining issues with ia32-libs in unstable. (The versioning is a tad crazy for that, though.) Kind regards, Philipp Kern signature.asc Description: Digital signature
Bug#596899: unblock: ia32-libs/20100914
On Mon, Oct 25, 2010 at 08:16:41PM +0200, Julien Cristau wrote: > > You can't build 32bit packages for amd64 in a 32bit chroot. That results > > in the wrong arch and wrong dependencies. > But you can use i386 packages on amd64 in a 32bit chroot. That results > in much less crack smoking all around. It's also plain wrong considering that we do exactly that. The buildds run amd64 with linux32. Kind regards, Philipp Kern signature.asc Description: Digital signature
exception for package: abiword
Hello Release Team, There are ugly crash bugs in current abiword (2.8.2) that have been dealt with in later releases. I'm proposing an an exception to see that that the latest version is included in squeeze. The katest abiword has now been uploaded to the FTP archive's queue (2010-10-28; delayed/2). Jari [Related] The update of abiword was discussed in #debian-release 2010-10-20 12:46 (Josselin Mouette) with regards to the status of goffice being solved first. This appears to be done according to https://buildd.debian.org/status/package.php?p=goffice&suite=unstable Source: abiword Version: 2.8.6-0.1 Distribution: unstable Urgency: low Maintainer: Jari Aalto Date: Wed, 20 Oct 2010 14:46:20 +0300 Closes: 498285 520424 552575 569272 577733 580346 586245 Changes: abiword (2.8.6-0.1) unstable; urgency=low . [ Jari Aalto ] * Non-maintainer upload. * New upstream release. Fixes: - Can't open password protected ODT files (Closes: #577733). - Scrolling with cursor keys is slow (important; Closes: #498285). - Crash on occasions when importing OpenDocument files. - Crash when trying to print (important; Closes: #580346). - Crash on accessing Tools -> Thesaurus menu (normal; Closes: #569272). - Crash on saving as PDF (normal; Closes: #520424). - Crash on trying to access Help (normal: Closes: #586245). - Crash on 3 MiB RTF file (normal; Closes: #552575); * debian/control - (Standards-Version): Update to 3.9.1. * debian/patches - (fixes/svn-backports.diff): Remove. Obsoleted by new release - (fixes/mime-types.diff): Refresh. Move abiword.desktop changes to separate diff. - (fixes/mime-types-desktop.diff): New file. . [ Hideki Yamane (Debian-JP) ] * debian/rules - (CC, CXX): Remove variables. - (LDFLAGS): New variable. Move content from --as-needed from CC, CXX variable. See bug #577871 for details. * debian/control - (Build-Depends): Add flex, bison. -- 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/87aalxiduh@picasso.cante.net
Bug#596899: unblock: ia32-libs/20100914
Philipp Kern writes: > On Mon, Oct 25, 2010 at 08:16:41PM +0200, Julien Cristau wrote: >> > You can't build 32bit packages for amd64 in a 32bit chroot. That results >> > in the wrong arch and wrong dependencies. >> But you can use i386 packages on amd64 in a 32bit chroot. That results >> in much less crack smoking all around. > > It's also plain wrong considering that we do exactly that. The buildds run > amd64 with linux32. > > Kind regards, > Philipp Kern The i386 buildds run a amd64 kernel with i386 userspace and they build packages for i386. This was about building 32bit packages for *amd64*. MfG Goswin -- 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/877hh19rrz@frosties.localdomain
Bug#601638: marked as done (please unblock libidn/1.18-1)
Your message dated Fri, 29 Oct 2010 13:15:01 +0200 with message-id <20101029111501.gv3...@radis.liafa.jussieu.fr> and subject line Re: Bug#601638: please unblock libidn/1.18-1 has caused the Debian Bug report #601638, regarding please unblock libidn/1.18-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.) -- 601638: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=601638 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Owner: Simon Josefsson please unblock libidn/1.18-1 it has been in unstable since 15 Feb 2010 and wasn't built on mips and mipsel until a month ago Date: Mon, 15 Feb 2010 13:36:58 +0100 Source: libidn Binary: idn libidn11-dev libidn11 libidn11-java Architecture: source i386 all Version: 1.18-1 Distribution: unstable Urgency: low Maintainer: Anibal Monsalve Salazar Changed-By: Simon Josefsson Description: idn- Command line and Emacs interface to GNU Libidn libidn11 - GNU Libidn library, implementation of IETF IDN specifications libidn11-dev - Development files for GNU Libidn, an IDN library libidn11-java - Java port of the GNU Libidn library, an IDN implementation Changes: libidn (1.18-1) unstable; urgency=low . [ Simon Josefsson ] * New upstream version. * libidn11.symbols: Fix based on upstream changes. * Moved from experimental to unstable after testing. signature.asc Description: Digital signature --- End Message --- --- Begin Message --- On Thu, Oct 28, 2010 at 12:48:26 +1100, Aníbal Monsalve Salazar wrote: > Package: release.debian.org > Severity: normal > User: release.debian@packages.debian.org > Usertags: unblock > Owner: Simon Josefsson > > please unblock libidn/1.18-1 > > it has been in unstable since 15 Feb 2010 and wasn't built on mips and > mipsel until a month ago > But it doesn't seem to fix any critical bugs, and has way too many changes at this point. So no. Cheers, Julien signature.asc Description: Digital signature --- End Message ---
Bug#601764: unblock: fuss-launcher/0.5-1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: freeze-exception Please unblock package fuss-launcher fuss-launcher (0.5-1) unstable; urgency=low * Port to new Xapian API. Closes: #601760 -- Enrico Zini Fri, 29 Oct 2010 12:55:13 +0200 It looks like a new upstream version but it only contains that fix. I am one of the upstreams :) unblock fuss-launcher/0.5-1 -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/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/20101029112639.13559.68708.report...@localhost
Re: Please unblock vzctl
On 29/10/2010 07:19, Ola Lundqvist wrote:
> Hi Release team
>
> I (with help of others) have corrected a number of important bugs and one
> release critial issue for the vzctl package. You can see the changes below.
>
There is:
--- vzctl-3.0.24/etc/init.d/initd-functions.in
+++ vzctl-3.0.24/etc/init.d/initd-functions.in
@@ -85 +85,26 @@
+vzdaemon_start()
+{
+ case DISTR in
I guess you meant "case $DISTR in"?
I do wonder if this code was tested…
vzdaemon_stop suffers from the same typo, fwiw.
>
> I consider all the above important for the next stable release.
> The only one that is more on a "good to have" basis is #597555 but I
> still consider that as important to avoid potential data corruption.
>
I consider the above as critical.
Regards,
--
Mehdi Dogguy مهدي الدڤي
http://dogguy.org/
--
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4ccab120.4080...@dogguy.org
Bug#601764: marked as done (unblock: fuss-launcher/0.5-1)
Your message dated Fri, 29 Oct 2010 13:37:31 +0200 with message-id <4ccab1fb.5070...@dogguy.org> and subject line Re: Bug#601764: unblock: fuss-launcher/0.5-1 has caused the Debian Bug report #601764, regarding unblock: fuss-launcher/0.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.) -- 601764: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=601764 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: freeze-exception Please unblock package fuss-launcher fuss-launcher (0.5-1) unstable; urgency=low * Port to new Xapian API. Closes: #601760 -- Enrico Zini Fri, 29 Oct 2010 12:55:13 +0200 It looks like a new upstream version but it only contains that fix. I am one of the upstreams :) unblock fuss-launcher/0.5-1 -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash --- End Message --- --- Begin Message --- On 29/10/2010 13:26, Enrico Zini wrote: > Package: release.debian.org > Severity: normal > User: release.debian@packages.debian.org > Usertags: freeze-exception > > Please unblock package fuss-launcher > > fuss-launcher (0.5-1) unstable; urgency=low > > * Port to new Xapian API. Closes: #601760 > > -- Enrico Zini Fri, 29 Oct 2010 12:55:13 +0200 > > It looks like a new upstream version but it only contains that fix. I am > one of the upstreams :) > Unblocked. Thanks for you work, -- Mehdi Dogguy مهدي الدڤي http://dogguy.org/ --- End Message ---
Re: exception for package: abiword
On 29/10/2010 10:48, Jari Aalto wrote:
>
> Hello Release Team,
>
> There are ugly crash bugs in current abiword (2.8.2) that have been
> dealt with in later releases.
>
> I'm proposing an an exception to see that that the latest version is
> included in squeeze. The katest abiword has now been uploaded to the
> FTP archive's queue (2010-10-28; delayed/2).
>
> Jari
>
> [Related]
>
> The update of abiword was discussed in #debian-release 2010-10-20 12:46
> (Josselin Mouette) with regards to the status of goffice being solved
> first. This appears to be done according to
> https://buildd.debian.org/status/package.php?p=goffice&suite=unstable
>
goffice is compiled on all arches (almost)… yes. But, I'm not sure yet we will
accept it in Squeeze.
Regards,
--
Mehdi Dogguy مهدي الدڤي
me...@{dogguy.org,debian.org}
--
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4ccab70e.7020...@debian.org
Re: Upload pre-approval for shorewall/4.4.11.6-2
On 29/10/2010 04:22, Roberto C. Sánchez wrote: > Release team, > > I would like approval to upload shorewall/4.4.11.6-2. Please see the > attached diff for all of the changes. > It looks ok. Please go ahead with the upload and let us know once the pacakge has been uploaded and accepted. (Please upload shorewall *only*) Regards, -- Mehdi Dogguy مهدي الدڤي http://dogguy.org/ -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4ccab7c5.20...@dogguy.org
Re: exception for package: abiword
Le vendredi 29 octobre 2010 à 13:59 +0200, Mehdi Dogguy a écrit : > > The update of abiword was discussed in #debian-release 2010-10-20 12:46 > > (Josselin Mouette) with regards to the status of goffice being solved > > first. This appears to be done according to > > https://buildd.debian.org/status/package.php?p=goffice&suite=unstable > goffice is compiled on all arches (almost)… yes. But, I'm not sure yet we will > accept it in Squeeze. It is not necessary. The new goffice package includes symbol files and will not block abiword when it has built everywhere. -- .''`. : :' : “You would need to ask a lawyer if you don't know `. `' that a handshake of course makes a valid contract.” `--- J???rg Schilling -- 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/1288354635.7807.4.ca...@meh
Re: exception for package: abiword
On 29/10/2010 14:17, Josselin Mouette wrote:
> Le vendredi 29 octobre 2010 à 13:59 +0200, Mehdi Dogguy a écrit :
>>> The update of abiword was discussed in #debian-release 2010-10-20
>>> 12:46 (Josselin Mouette) with regards to the status of goffice
>>> being solved first. This appears to be done according to
>>> https://buildd.debian.org/status/package.php?p=goffice&suite=unstable
>
>> goffice is compiled on all arches (almost)… yes. But, I'm not sure
>> yet we will accept it in Squeeze.
>
> It is not necessary. The new goffice package includes symbol files and
> will not block abiword when it has built everywhere.
>
Oh that's nice :) I should have checked that by myself. So, let's wait
until Abiword hits the archive and get the usual testing in sid… then, we
will unblock it for Squeeze if all is ok.
If the maintainer if ok with the NMU, why is it in delayed/2? Couldn't you
reschedule it to delayed/0?
Regards,
--
Mehdi Dogguy مهدي الدڤي
me...@{dogguy.org,debian.org}
--
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4ccabd68.6000...@debian.org
Re: New clamav upstream version: Should it go into squeeze?
Hi, On Wed, Oct 27, 2010 at 1:10 PM, Julien Cristau wrote: > On Tue, Oct 26, 2010 at 23:18:47 +0200, Moritz Muehlenhoff wrote: > >> Since the planned way to keep clamav updated in Squeeze will be by >> updating to the latest current clamav stable release, the same should >> naturally apply during the freeze? >> > Yes. Please unblock 'libclamunrar' to have it in sync with current 'clamav'. Thanks -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/aanlktinc6c4jhep=b6daduy1qgoy5q1gzea4zs7xc...@mail.gmail.com
Re: Please unblock vzctl
Hi Mehdi
Thanks. Will upload a new corrected version now.
It was tested, but for some reason I did not catch this one.
Best regards,
// Ola
Quoting "Mehdi Dogguy" :
On 29/10/2010 07:19, Ola Lundqvist wrote:
Hi Release team
I (with help of others) have corrected a number of important bugs and one
release critial issue for the vzctl package. You can see the changes below.
There is:
--- vzctl-3.0.24/etc/init.d/initd-functions.in
+++ vzctl-3.0.24/etc/init.d/initd-functions.in
@@ -85 +85,26 @@
+vzdaemon_start()
+{
+ case DISTR in
I guess you meant "case $DISTR in"?
I do wonder if this code was tested…
vzdaemon_stop suffers from the same typo, fwiw.
I consider all the above important for the next stable release.
The only one that is more on a "good to have" basis is #597555 but I
still consider that as important to avoid potential data corruption.
I consider the above as critical.
Regards,
--
Mehdi Dogguy مهدي الدڤي
http://dogguy.org/
--
--- Inguza Technology AB --- MSc in Information Technology
/ o...@inguza.comAnnebergsslingan 37\
| o...@debian.org 654 65 KARLSTAD|
| http://inguza.com/Mobile: +46 (0)70-332 1551 |
\ gpg/f.p.: 7090 A92B 18FE 7994 0C36 4FE4 18A1 B1CF 0FE5 3DD9 /
---
--
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/20101029141607.141049k2bq020...@webmail.inguza.net
Bug#601773: release.debian.org: unblock: fusionforge/5.0.2-4
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Hi,
I'd like to request an unblock for fusionforge/5.0.2-4, which is just a
cherry-pick of two bugfixes from upstream. The first one is actually a
fix for a regression introduced by 5.0.2-3 (#601573), where a check for
validity of a variable was done before the variable was defined. The
second is a fix for yet another after-effect of the gforge->fusionforge
rename: the users used by NSS and the MTA integration were previously
gforge_nss and gforge_mta, and they're now fusionforge_nss/mta.
Actually, they're ${db_user}_nss and _mta, which amounts to
fusionforge_* on new installations but stays gforge_* on upgrades. This
patch completes the transition so whatever the value is, it's the same
everywhere it's used. This fixes email forwarding (including
mailing-lists) and shell authentication (which unbreaks the source
control tools that need SSH).
Debdiff follows: 7 files changed, 55 insertions(+), 16 deletions(-).
Thanks,
Roland.
diff -u fusionforge-5.0.2/deb-specific/create-mailing-lists.pl fusionforge-5.0.2/deb-specific/create-mailing-lists.pl
--- fusionforge-5.0.2/deb-specific/create-mailing-lists.pl
+++ fusionforge-5.0.2/deb-specific/create-mailing-lists.pl
@@ -47,12 +47,12 @@
my ($group_list_id, $listname, $user_name, $password, $description, $is_public) ;
my ($tmp) ;
+ ($group_list_id, $listname, $user_name, $password, $description, $is_public)= @array ;
next if $listname eq '' ;
next if $listname eq '.' ;
next if $listname eq '..' ;
next if $listname !~ /^[a-z0-9\-_\.]*$/ ;
- ($group_list_id, $listname, $user_name, $password, $description, $is_public)= @array ;
my $cmd = "/usr/sbin/newlist -q $listname $user_na...@$sys_users_host $password >/dev/null 2>&1" ;
#print "cmd = <$cmd>\n" ;
system ($cmd) ;
@@ -125,12 +125,12 @@
my ($group_list_id, $listname, $user_name, $password, $description, $is_public) ;
my ($tmp) ;
+ ($group_list_id, $listname, $user_name, $password, $description, $is_public)= @array ;
next if $listname eq '' ;
next if $listname eq '.' ;
next if $listname eq '..' ;
next if $listname !~ /^[a-z0-9\-_\.]*$/ ;
- ($group_list_id, $listname, $user_name, $password, $description, $is_public)= @array ;
my $cmd = "/usr/lib/mailman/bin/change_pw -l $listname >/dev/null 2>&1" ;
system ($cmd) ;
diff -u fusionforge-5.0.2/deb-specific/install-postfix.sh fusionforge-5.0.2/deb-specific/install-postfix.sh
--- fusionforge-5.0.2/deb-specific/install-postfix.sh
+++ fusionforge-5.0.2/deb-specific/install-postfix.sh
@@ -75,8 +75,8 @@
# keep it in an appropriate position, where \"appropriate\" is defined by you.
pgsql_gforge_users_hosts = unix:/var/run/postgresql
-pgsql_gforge_users_user = gforge_mta
-pgsql_gforge_users_password = gforge_mta
+pgsql_gforge_users_user = ${sys_dbuser}_mta
+pgsql_gforge_users_password = ${sys_dbuser}_mta
pgsql_gforge_users_dbname = $sys_dbname
pgsql_gforge_users_domain = users.$domain_name
pgsql_gforge_users_query = SELECT email FROM mta_users WHERE login = '\''%u'\''
diff -u fusionforge-5.0.2/deb-specific/install-db.sh fusionforge-5.0.2/deb-specific/install-db.sh
--- fusionforge-5.0.2/deb-specific/install-db.sh
+++ fusionforge-5.0.2/deb-specific/install-db.sh
@@ -115,7 +115,7 @@
rm -f $cur
cur=$(mktemp /tmp/$pattern)
- perl -e "open F, \"${pg_hba_dir}/pg_hba.conf.gforge-new\" or die \$!; undef \$/; \$l=; \$l=~ s/^### BEGIN GFORGE BLOCK -- DO NOT EDIT.*### END GFORGE BLOCK -- DO NOT EDIT\$/### BEGIN GFORGE BLOCK -- DO NOT EDIT\nlocal $db_name $db_user md5\nlocal $db_name gforge_nss trust\nlocal $db_name gforge_mta md5\n### END GFORGE BLOCK -- DO NOT EDIT/ms; print \$l;" > $cur
+ perl -e "open F, \"${pg_hba_dir}/pg_hba.conf.gforge-new\" or die \$!; undef \$/; \$l=; \$l=~ s/^### BEGIN GFORGE BLOCK -- DO NOT EDIT.*### END GFORGE BLOCK -- DO NOT EDIT\$/### BEGIN GFORGE BLOCK -- DO NOT EDIT\nlocal $db_name $db_user md5\nlocal $db_name ${db_user}_nss trust\nlocal $db_name ${db_user}_mta md5\n### END GFORGE BLOCK -- DO NOT EDIT/ms; print \$l;" > $cur
cat $cur > ${pg_hba_dir}/pg_hba.conf.gforge-new
rm -f $cur
@@ -148,7 +148,7 @@
fi
if su -s /bin/sh postgres -c "/usr/bin/psql template1" 1> $tmp1 2> $tmp2 <<-EOF
SET LC_MESSAGES = 'C' ;
-CREATE USER gforge_nss WITH PASSWORD 'gforge_nss' ;
+CREATE USER ${db_user}_nss WITH PASSWORD '${db_user}_nss' ;
EOF
then
rm -f $tmp1 $tmp2
@@ -166,7 +166,7 @@
fi
if su -s /bin/sh postgres -c "/usr/bin/psql template1" 1> $tmp1 2> $tmp2 <<-EOF
SET LC_MESSAGES = 'C' ;
-CREATE USER gforge_mta WITH PASSWORD 'gforge_mta' ;
+CREATE USER ${db_user}_mta WITH PASSWORD '${db_user}_mta' ;
EOF
then
rm -f $tmp1 $tmp2
diff -u fusionforge-5.0.2/utils/install-nsspgsql.sh fusionforge-5.0.2/utils/install-nsspgsql.sh
--- fusionforge-5.0.2/utils/install-nsspgsql.sh
+++ fusionforge-5.0.2/utils/install-nsspgsql.sh
@@ -59,7 +59,7 @@
### NSS Configuration for Gforge
#-
Bug#601775: unblock: libice/2:1.0.6-2
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please consider unblocking package libice Relevant fix you might want to push into squeeze: | * Cherry-pick from upstream: | + 0001-Set-the-close-on-exec-flag-for-listening-sockets.patch: | Stop leaking listening sockets by setting the close on exec flag on | them. Thanks to Kalle Olavi Niemitalo (Closes: #538248). | [From upstream 1967c04c0] There's some infortunate noise in the diff, which was already present in git when I wondered about cherry-picking this patch, but Mehdi seemed OK with it. unblock libice/2:1.0.6-2 Thanks for your time. Mraw, KiBi. -- 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/20101029133521.7455.14663.report...@talisker
Bug#601775: marked as done (unblock: libice/2:1.0.6-2)
Your message dated Fri, 29 Oct 2010 15:43:05 +0200 with message-id <4ccacf69.2000...@dogguy.org> and subject line Re: Bug#601775: unblock: libice/2:1.0.6-2 has caused the Debian Bug report #601775, regarding unblock: libice/2:1.0.6-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.) -- 601775: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=601775 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please consider unblocking package libice Relevant fix you might want to push into squeeze: | * Cherry-pick from upstream: | + 0001-Set-the-close-on-exec-flag-for-listening-sockets.patch: | Stop leaking listening sockets by setting the close on exec flag on | them. Thanks to Kalle Olavi Niemitalo (Closes: #538248). | [From upstream 1967c04c0] There's some infortunate noise in the diff, which was already present in git when I wondered about cherry-picking this patch, but Mehdi seemed OK with it. unblock libice/2:1.0.6-2 Thanks for your time. Mraw, KiBi. --- End Message --- --- Begin Message --- On 29/10/2010 15:35, Cyril Brulebois wrote: > Package: release.debian.org > Severity: normal > User: release.debian@packages.debian.org > Usertags: unblock > > Please consider unblocking package libice > > Relevant fix you might want to push into squeeze: > | * Cherry-pick from upstream: > | + 0001-Set-the-close-on-exec-flag-for-listening-sockets.patch: > | Stop leaking listening sockets by setting the close on exec flag on > | them. Thanks to Kalle Olavi Niemitalo (Closes: #538248). > | [From upstream 1967c04c0] > Unblocked. Mraw, -- Mehdi Dogguy مهدي الدڤي http://dogguy.org/ --- End Message ---
Re: [Debian] Re: Please unblock vzctl
Mehdi,
Thanks for reporting that! It's my bug :( and I am also unsure
how this went unnoticed.
Fixed in vzctl git:
http://git.openvz.org/?p=vzctl;a=commit;h=3527cc269bb51d48e0f511fbf7a807ad56c223d5
On 10/29/2010 04:16 PM, Ola Lundqvist wrote:
Hi Mehdi
Thanks. Will upload a new corrected version now.
It was tested, but for some reason I did not catch this one.
Best regards,
// Ola
Quoting "Mehdi Dogguy" :
On 29/10/2010 07:19, Ola Lundqvist wrote:
Hi Release team
I (with help of others) have corrected a number of important bugs
and one
release critial issue for the vzctl package. You can see the changes
below.
There is:
--- vzctl-3.0.24/etc/init.d/initd-functions.in
+++ vzctl-3.0.24/etc/init.d/initd-functions.in
@@ -85 +85,26 @@
+vzdaemon_start()
+{
+ case DISTR in
I guess you meant "case $DISTR in"?
I do wonder if this code was tested…
vzdaemon_stop suffers from the same typo, fwiw.
I consider all the above important for the next stable release.
The only one that is more on a "good to have" basis is #597555 but I
still consider that as important to avoid potential data corruption.
I consider the above as critical.
Regards,
--
Mehdi Dogguy مهدي الدڤي
http://dogguy.org/
--
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4ccac76f.3040...@openvz.org
Bug#601780: unblock: freeimage/3.10.0-3
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package freeimage. This version uses external libs instead of embedded copies for everything but tiff, and updates the embedded tiff to the latest version in sid. There's some hacking involved to work around the lack of a configure step in the freeimage build, and the lack of itxt in our libpng. I tried to keep the changes minimal though, so hopefully this can go in after some time in sid. The debdiff is noisier than it needs to be because the original version had crlf linebreaks. http://people.debian.org/~jcristau/freeimage_qa.diff is a cleaned up version. unblock freeimage/3.10.0-3 Cheers, Julien signature.asc Description: Digital signature
Re: exception for package: abiword
On 29/10/2010 16:05, tony mancill wrote:
> On 10/29/2010 05:26 AM, Mehdi Dogguy wrote:
>>
>> If the maintainer if ok with the NMU, why is it in delayed/2?
>> Couldn't you reschedule it to delayed/0?
>
> I uploaded to delayed/2 because Jari and I are in different timezones
> and I thought there might be some need for coordination prior to the
> package entering sid. As soon as I have access to my workstation (on
> the bus right now), I'll cancel that upload and upload again to
> delayed/0.
>
ok, thanks.
BTW, "dcut reschedule foo_1.2-1.1_all.changes 0-day" is enough. No need to
cancel your upload.
Regards,
--
Mehdi Dogguy مهدي الدڤي
me...@{dogguy.org,debian.org}
--
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4ccadd6a.3060...@debian.org
Re: exception for package: abiword
On 10/29/2010 05:26 AM, Mehdi Dogguy wrote: > On 29/10/2010 14:17, Josselin Mouette wrote: >> Le vendredi 29 octobre 2010 à 13:59 +0200, Mehdi Dogguy a écrit : The update of abiword was discussed in #debian-release 2010-10-20 12:46 (Josselin Mouette) with regards to the status of goffice being solved first. This appears to be done according to https://buildd.debian.org/status/package.php?p=goffice&suite=unstable >> >>> goffice is compiled on all arches (almost)… yes. But, I'm not sure >>> yet we will accept it in Squeeze. >> >> It is not necessary. The new goffice package includes symbol files and >> will not block abiword when it has built everywhere. >> > > Oh that's nice :) I should have checked that by myself. So, let's wait > until Abiword hits the archive and get the usual testing in sid… then, we > will unblock it for Squeeze if all is ok. > > If the maintainer if ok with the NMU, why is it in delayed/2? Couldn't you > reschedule it to delayed/0? I uploaded to delayed/2 because Jari and I are in different timezones and I thought there might be some need for coordination prior to the package entering sid. As soon as I have access to my workstation (on the bus right now), I'll cancel that upload and upload again to delayed/0. Thank you, tony signature.asc Description: OpenPGP digital signature
Bug#601773: marked as done (release.debian.org: unblock: fusionforge/5.0.2-4)
Your message dated Fri, 29 Oct 2010 15:59:13 +0100
with message-id <1288364353.30602.91.ca...@hathi.jungle.funky-badger.org>
and subject line Re: Bug#601773: release.debian.org: unblock:
fusionforge/5.0.2-4
has caused the Debian Bug report #601773,
regarding release.debian.org: unblock: fusionforge/5.0.2-4
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.)
--
601773: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=601773
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Hi,
I'd like to request an unblock for fusionforge/5.0.2-4, which is just a
cherry-pick of two bugfixes from upstream. The first one is actually a
fix for a regression introduced by 5.0.2-3 (#601573), where a check for
validity of a variable was done before the variable was defined. The
second is a fix for yet another after-effect of the gforge->fusionforge
rename: the users used by NSS and the MTA integration were previously
gforge_nss and gforge_mta, and they're now fusionforge_nss/mta.
Actually, they're ${db_user}_nss and _mta, which amounts to
fusionforge_* on new installations but stays gforge_* on upgrades. This
patch completes the transition so whatever the value is, it's the same
everywhere it's used. This fixes email forwarding (including
mailing-lists) and shell authentication (which unbreaks the source
control tools that need SSH).
Debdiff follows: 7 files changed, 55 insertions(+), 16 deletions(-).
Thanks,
Roland.
diff -u fusionforge-5.0.2/deb-specific/create-mailing-lists.pl fusionforge-5.0.2/deb-specific/create-mailing-lists.pl
--- fusionforge-5.0.2/deb-specific/create-mailing-lists.pl
+++ fusionforge-5.0.2/deb-specific/create-mailing-lists.pl
@@ -47,12 +47,12 @@
my ($group_list_id, $listname, $user_name, $password, $description, $is_public) ;
my ($tmp) ;
+ ($group_list_id, $listname, $user_name, $password, $description, $is_public)= @array ;
next if $listname eq '' ;
next if $listname eq '.' ;
next if $listname eq '..' ;
next if $listname !~ /^[a-z0-9\-_\.]*$/ ;
- ($group_list_id, $listname, $user_name, $password, $description, $is_public)= @array ;
my $cmd = "/usr/sbin/newlist -q $listname $user_na...@$sys_users_host $password >/dev/null 2>&1" ;
#print "cmd = <$cmd>\n" ;
system ($cmd) ;
@@ -125,12 +125,12 @@
my ($group_list_id, $listname, $user_name, $password, $description, $is_public) ;
my ($tmp) ;
+ ($group_list_id, $listname, $user_name, $password, $description, $is_public)= @array ;
next if $listname eq '' ;
next if $listname eq '.' ;
next if $listname eq '..' ;
next if $listname !~ /^[a-z0-9\-_\.]*$/ ;
- ($group_list_id, $listname, $user_name, $password, $description, $is_public)= @array ;
my $cmd = "/usr/lib/mailman/bin/change_pw -l $listname >/dev/null 2>&1" ;
system ($cmd) ;
diff -u fusionforge-5.0.2/deb-specific/install-postfix.sh fusionforge-5.0.2/deb-specific/install-postfix.sh
--- fusionforge-5.0.2/deb-specific/install-postfix.sh
+++ fusionforge-5.0.2/deb-specific/install-postfix.sh
@@ -75,8 +75,8 @@
# keep it in an appropriate position, where \"appropriate\" is defined by you.
pgsql_gforge_users_hosts = unix:/var/run/postgresql
-pgsql_gforge_users_user = gforge_mta
-pgsql_gforge_users_password = gforge_mta
+pgsql_gforge_users_user = ${sys_dbuser}_mta
+pgsql_gforge_users_password = ${sys_dbuser}_mta
pgsql_gforge_users_dbname = $sys_dbname
pgsql_gforge_users_domain = users.$domain_name
pgsql_gforge_users_query = SELECT email FROM mta_users WHERE login = '\''%u'\''
diff -u fusionforge-5.0.2/deb-specific/install-db.sh fusionforge-5.0.2/deb-specific/install-db.sh
--- fusionforge-5.0.2/deb-specific/install-db.sh
+++ fusionforge-5.0.2/deb-specific/install-db.sh
@@ -115,7 +115,7 @@
rm -f $cur
cur=$(mktemp /tmp/$pattern)
- perl -e "open F, \"${pg_hba_dir}/pg_hba.conf.gforge-new\" or die \$!; undef \$/; \$l=; \$l=~ s/^### BEGIN GFORGE BLOCK -- DO NOT EDIT.*### END GFORGE BLOCK -- DO NOT EDIT\$/### BEGIN GFORGE BLOCK -- DO NOT EDIT\nlocal $db_name $db_user md5\nlocal $db_name gforge_nss trust\nlocal $db_name gforge_mta md5\n### END GFORGE BLOCK -- DO NOT EDIT/ms; print \$l;" > $cur
+ perl -e "open F, \"${pg_hba_dir}/pg_hba.conf.gforge-new\" or die \$!; undef \$/; \$l=; \$l=~ s/^### BEGIN GFORGE BLOCK -- DO NOT EDIT.*### END GFORGE BLOCK -- DO NOT EDIT\$/### BEGIN GFORGE BLOCK -- DO NOT EDIT\nlocal $db_name $db_user md5\nlocal $db_name ${db_user}_nss trust\nlocal $db_name ${db_user}_mta md5\n### END GFORGE BLOCK -- DO NOT EDIT/ms;
Re: dash situation
Hi, Apologies for the late reply on this. For some reason I thought it had been replied to earlier but realised it hadn't whilst tidying up my mail. On Sun, 2010-09-19 at 16:44 +0200, Helmut Grohne wrote: > * #546528: This seems to be "only" a policy violation and I have not >found any reports about practical problems. If this is not to be >fixed, it would be an option to tag this squeeze-ignore. The bug log has an alternative suggestion regarding just making the preinst use a /bin/bash shebang, on the basis that bash is still (and probably always will be) essential. This seems so simple that I'm sure there must be a catch somewhere; I just haven't worked out what it is yet. :-) > * #538822: Must be addressed in some way. Since it only hits upgrading >users that followed README.Debian, those users could be told to >revert that change via release-notes. I'd prefer if we could find a solution that DTRT here without requiring intervention from users. Noting the manual solution in the release notes wouldn't be the end of the world, however. > * #582952: This one involves either fixing a lot of packages or >shipping a non-POSIX shell by default. Both of which are bad and >probably breaking a lot of unrelated stuff. Shipping a non-POSIX dash >seems to be slightly better to me as this hasn't bothered us so >far[1]. LINENO isn't part of the SUSv3 Shell Command Language as specified in Policy. The description of the variable therein explicitly states that it "specifies the effects of the variable only for systems supporting the User Portability Utilities option" and Policy does not require UP to be supported. In any case, this issue is resolved in squeeze and sid already. 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/1288369637.30602.718.ca...@hathi.jungle.funky-badger.org
Re: Upload pre-approval for shorewall/4.4.11.6-2
On Fri, Oct 29, 2010 at 02:02:13PM +0200, Mehdi Dogguy wrote: > On 29/10/2010 04:22, Roberto C. Sánchez wrote: > > Release team, > > > > I would like approval to upload shorewall/4.4.11.6-2. Please see the > > attached diff for all of the changes. > > > > It looks ok. Please go ahead with the upload and let us know once the > pacakge has been uploaded and accepted. (Please upload shorewall *only*) > Uploaded. Only shorewall. I have spoken to the main upstream author and asked that he just provide patches for individual packages, rather than a new upstream release of all the packages. Thanks for the unblock. Regards, -Roberto -- Roberto C. Sánchez http://people.connexer.com/~roberto http://www.connexer.com signature.asc Description: Digital signature
Re: [Debian] Re: Please unblock vzctl
Hi Kir
When I tested this it was obvious that this did not work as well as it should.
I have applied two more patches to make it work as it should. This problem must
have been masked by the other problem.
A bugreport will be sent shortly.
Best regards,
// Ola
On Fri, Oct 29, 2010 at 05:09:03PM +0400, Kir Kolyshkin wrote:
> Mehdi,
>
> Thanks for reporting that! It's my bug :( and I am also unsure
> how this went unnoticed.
>
> Fixed in vzctl git:
> http://git.openvz.org/?p=vzctl;a=commit;h=3527cc269bb51d48e0f511fbf7a807ad56c223d5
>
> On 10/29/2010 04:16 PM, Ola Lundqvist wrote:
>> Hi Mehdi
>>
>> Thanks. Will upload a new corrected version now.
>>
>> It was tested, but for some reason I did not catch this one.
>>
>> Best regards,
>>
>> // Ola
>>
>> Quoting "Mehdi Dogguy" :
>>> On 29/10/2010 07:19, Ola Lundqvist wrote:
Hi Release team
I (with help of others) have corrected a number of important bugs
and one
release critial issue for the vzctl package. You can see the
changes below.
>>>
>>> There is:
>>>
>>> --- vzctl-3.0.24/etc/init.d/initd-functions.in
>>> +++ vzctl-3.0.24/etc/init.d/initd-functions.in
>>> @@ -85 +85,26 @@
>>> +vzdaemon_start()
>>> +{
>>> + case DISTR in
>>>
>>> I guess you meant "case $DISTR in"?
>>> I do wonder if this code was tested…
>>>
>>> vzdaemon_stop suffers from the same typo, fwiw.
>>>
I consider all the above important for the next stable release.
The only one that is more on a "good to have" basis is #597555 but I
still consider that as important to avoid potential data corruption.
>>>
>>> I consider the above as critical.
>>>
>>> Regards,
>>>
>>> --
>>> Mehdi Dogguy مهدي الدڤي
>>> http://dogguy.org/
>>>
>>>
>>
>>
>>
>
>
--
--- Inguza Technology AB --- MSc in Information Technology
/ o...@inguza.comAnnebergsslingan 37\
| o...@debian.org 654 65 KARLSTAD|
| http://inguza.com/Mobile: +46 (0)70-332 1551 |
\ gpg/f.p.: 7090 A92B 18FE 7994 0C36 4FE4 18A1 B1CF 0FE5 3DD9 /
---
--
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/20101029170732.ga30...@inguza.net
Re: [Debian] Re: Please unblock vzctl
Hi Mehdi
I'm now re-requesting to unblock vzctl.
I have uploaded an updated version with a correction to the problem
you noted. This correction was not enough though. So I have applied a few
more things.
1) The init script return with error 1 when already started or already stopped.
This makes the debian postinst and prerm scripts to fail.
2) The status command fails.
3) The start-stop-daemon is called with wrong arguments.
I have applied a patch that solve these problems. They are all critical issues
as I understand it.
This is now also reported upstream to be included there.
http://bugzilla.openvz.org/show_bug.cgi?id=1685
vzctl (3.0.24-9) unstable; urgency=high
* Correction of the solution of #600455 in last upload. Applied patch
from upstream. Thanks to Kir Kolyshkin for fast support.
This patch allows vzeventd to be started.
* Addtional corrections for vzeventd init function:
Makes sure that init script do not return error when already started.
Make sure the mandatory status command works.
The start-stop-daemon was called with wrong arguments. Fixed now.
-- Ola Lundqvist Fri, 29 Oct 2010 18:02:11 +0200
Thanks in advance,
// Ola
On Fri, Oct 29, 2010 at 07:07:32PM +0200, Ola Lundqvist wrote:
> Hi Kir
>
> When I tested this it was obvious that this did not work as well as it should.
> I have applied two more patches to make it work as it should. This problem
> must
> have been masked by the other problem.
>
> A bugreport will be sent shortly.
>
> Best regards,
>
> // Ola
>
> On Fri, Oct 29, 2010 at 05:09:03PM +0400, Kir Kolyshkin wrote:
> > Mehdi,
> >
> > Thanks for reporting that! It's my bug :( and I am also unsure
> > how this went unnoticed.
> >
> > Fixed in vzctl git:
> > http://git.openvz.org/?p=vzctl;a=commit;h=3527cc269bb51d48e0f511fbf7a807ad56c223d5
> >
> > On 10/29/2010 04:16 PM, Ola Lundqvist wrote:
> >> Hi Mehdi
> >>
> >> Thanks. Will upload a new corrected version now.
> >>
> >> It was tested, but for some reason I did not catch this one.
> >>
> >> Best regards,
> >>
> >> // Ola
> >>
> >> Quoting "Mehdi Dogguy" :
> >>> On 29/10/2010 07:19, Ola Lundqvist wrote:
> Hi Release team
>
> I (with help of others) have corrected a number of important bugs
> and one
> release critial issue for the vzctl package. You can see the
> changes below.
>
> >>>
> >>> There is:
> >>>
> >>> --- vzctl-3.0.24/etc/init.d/initd-functions.in
> >>> +++ vzctl-3.0.24/etc/init.d/initd-functions.in
> >>> @@ -85 +85,26 @@
> >>> +vzdaemon_start()
> >>> +{
> >>> + case DISTR in
> >>>
> >>> I guess you meant "case $DISTR in"?
> >>> I do wonder if this code was tested…
> >>>
> >>> vzdaemon_stop suffers from the same typo, fwiw.
> >>>
>
> I consider all the above important for the next stable release.
> The only one that is more on a "good to have" basis is #597555 but I
> still consider that as important to avoid potential data corruption.
>
> >>>
> >>> I consider the above as critical.
> >>>
> >>> Regards,
> >>>
> >>> --
> >>> Mehdi Dogguy مهدي الدڤي
> >>> http://dogguy.org/
> >>>
> >>>
> >>
> >>
> >>
> >
> >
>
> --
> --- Inguza Technology AB --- MSc in Information Technology
> / o...@inguza.comAnnebergsslingan 37\
> | o...@debian.org 654 65 KARLSTAD|
> | http://inguza.com/Mobile: +46 (0)70-332 1551 |
> \ gpg/f.p.: 7090 A92B 18FE 7994 0C36 4FE4 18A1 B1CF 0FE5 3DD9 /
> ---
>
--
--- Inguza Technology AB --- MSc in Information Technology
/ o...@inguza.comAnnebergsslingan 37\
| o...@debian.org 654 65 KARLSTAD|
| http://inguza.com/Mobile: +46 (0)70-332 1551 |
\ gpg/f.p.: 7090 A92B 18FE 7994 0C36 4FE4 18A1 B1CF 0FE5 3DD9 /
---
--
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/20101029193523.ga1...@inguza.net
Bug#598835: unblock: mina2/2.0.0+dfsg-1
On Thu, 2010-10-28 at 22:58 +0200, Damien Raude-Morvan wrote: > Le samedi 23 octobre 2010 15:06:13, Adam D. Barratt a écrit : > > > >>* Enable rxtx support: > > > >> - d/control: Add Build-Depends on librxtx-java. [...] > > > If this is too much for squeeze, I can disable this rxtx support again as > > > reverse-depends of mina2 doesn't use this feature. > > > > Sorry, but yes, if the feature hasn't been enabled previously and isn't > > used by any of the r-deps, I'd prefer that it stay disabled for Squeeze. > > I plan to upload a mina2 2.0.0+dfsg-1.1 to t-p-u with this change dropped. Is > this okay for you ? Assuming that the intention was for 2.0.0+dfsg-1 to stay blocked in unstable with the feature enabled, a tpu version would need to be lower; e.g. 2.0.0+dfsg-1~squeeze1. 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/1288383266.30602.2168.ca...@hathi.jungle.funky-badger.org
Bug#601780: unblock: freeimage/3.10.0-3
On Fri, Oct 29, 2010 at 16:24:54 +0200, Julien Cristau wrote: > unblock freeimage/3.10.0-3 > I had a stupid typo in -3 causing ftbfs on 32bit archs, so make that -4. Thanks, Julien signature.asc Description: Digital signature
Bug#600458: unblock: nss-pam-ldapd/0.7.11
On Sun, 2010-10-17 at 13:11 +0200, Philipp Kern wrote: > On Sun, Oct 17, 2010 at 12:54:05PM +0200, Arthur de Jong wrote: > > I have another pending change that fixes a problem when nslcd would hang > > under certain circumstances (using TLS and seeing a certain type of > > network problem during a search). This change is a little larger and was > > the result of missing a last part of #596983. > > > > It involves setting a timeout on the socket when closing the connection > > and ensuring that in all places that the connection is closed the same > > function is executed. It is a workaround for a bug in OpenLDAP when used > > with GnuTLS. The relevant change can be seen here: > > > > http://arthurdejong.org/viewvc/nss-pam-ldapd/nss-pam-ldapd/nslcd/myldap.c?r1=1276&r2=1275&pathrev=1276 > > (except the changes from line 690 onwards because they are specific to > > changes in the trunk) > > > > Do you want me to prepare an upload to unstable with the above change? > > Two issues in one bug report is a bit annoying. Please let the above > version migrate first. Since 0.7.11 migrated to testing I've uploaded a version 0.7.12 to unstable that fixes the remaining disconnect problems. > Workarounds like these are really hard to judge IMHO. But as the line 690+ > changes are irrelevant you can go ahead. The diff should be minimal. Only the first part of the diff (to nslcd.c) applies the actual timeout setting and only just before closing the connection. When that code hits no useful data should be sent over the connection anyway. The other changes just replace the call to ldap_unbind() with a call to do_close() which ensures that unbinds are done the same way in every case. If you need more background feel free to ask. Thanks for your work. -- -- arthur - adej...@debian.org - http://people.debian.org/~adejong -- signature.asc Description: This is a digitally signed message part
Bug#601814: unblock: vinagre/2.30.3-1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: freeze-exception Please unblock package vinagre This new upstream stable release only contains updated translations [1] and no code changes. I also kept the packaging related changes to a minimum and simply bumped the Standards-Version to 3.9.1. Would be nice to have the updated translations in squeeze. Cheers, Michael unblock vinagre/2.30.3-1 [1] http://git.gnome.org/browse/vinagre/log/?h=gnome-2-30 -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (200, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.36-trunk-686 (SMP w/1 CPU core) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.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/20101029230033.2920.48078.report...@pluto.milchstrasse.xx
Bug#601820: RM: ntop/3:3.3-14
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: rm -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Myself and Ludovico Cavedon are the new co-maintainers of the ntop package. The current state of ntop in Debian is not good. Squeeze is about to ship with the same version that was found in Lenny. The orig tarball for this release was a beta release, and is no longer distributed by upstream. We have concerns about being able to offer security support for this version for the lifetime of Squeeze, and we also feel it is not worth the effort. For this reason, we would like to request removal of Squeeze. We plan to offer the new 4.0.3 version of ntop for Squeeze users as soon as possible. Quoting my co-maintainer: > If you want ntop and run "apt-get install ntop" and it is installable, > you end up running 3.3, probably without even knowing that you are > running a version that is even older than lenny. > If it is not, you look for that, and find 4.0 on backports. We feel that it is best if users did not have the option of using this package. This old package is simply not worth the time and the effort. Please remove ntop from testing. Thanks, Jordan Metzmeier -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iQIcBAEBCAAGBQJMy14jAAoJEKj/C3qNthmTntgP/RaPF2TUcRLu3phYN2Cq34Yo wXndjTsyh3UN8FI/niTkZ73CnRm/7ZtgrRlfS2dVss93GYm5P1OcfgkUp7wMvwKM B+ZwDQglttM+9Q2sk8Nredw32pPKhPzzvQHnU+dmOLZ+jbQqXmQeZaFW0eEheg3+ ReN7JBdkKL6vhnCIdCihRJal1qJt04kZNcCrvZb0SuYVi39kX/HEgm8YUNAe1+gj X+fD2Pdcb35JOfaIKuTbKawoWCtQtXBl+7gdc30kQiCsujgTs1xagcsW9qFX0OCa cQEC6XrUNfbWLIPg5gMDuYuGEIqI33SxpdfAn0Do63QwkYi3XCapbWJqq2qXemYl 4MAEmYQaa2jsLp18nVPJQFYiqf17SfNFuJsTJEL7UV/+pT0upBwneF77Sbk9KhV0 zrhBjPCwidZ/Xn57wqj34SXJ0gXNi29uFiysvkazGNcUHQtDOGPfiSPcrkotCM18 iOcxlW6LKtUUO8qef8ldmTbTS0r7pSOY1eIryANJlQ3U+cIJ7cSPE5eGaQsmzxBi 1JVWs3BOhBeAKn6WdU3HTqdPpoH17QLyCKJo252YUJ5mCgkWunmy+uUQWOnIvCrv RvUVYi+oLq1b2cxpM1HrEGWET5Dos6mMjKZZgk5rz4aQjtqlGiWxPt4SfZjoFlMS hHaxYn8R9LPHV7fFfhoa =6kgp -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20101029235209.7564.70323.report...@debtop.local
Bug#599307: unblock: jblas/1.1.1-1
On Tue, 2010-10-19 at 08:36 +0200, Julien Cristau wrote: > On Mon, Oct 18, 2010 at 22:39:29 +0200, Soeren Sonnenburg wrote: Dear Julien, > > I finally got an answer and small patch (attached) from upstream Re this > > issue. Shall I prepare jblas 1.1.1-2 that includes this patch? > > > Yes. jblas 1.1.1-2 is now sitting in unstable for ten days without bug reports http://qa.debian.org/excuses.php?package=jblas - could you please help it transition to testing now? > Cheers, > Julien Thanks, Soeren -- For the one fact about the future of which we can be certain is that it will be utterly fantastic. -- Arthur C. Clarke, 1962 signature.asc Description: This is a digitally signed message part
