Processed: Re: Bug#608689: RM: pytris -- security issues; abandoned upstream

2011-01-03 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: retitle 608689 RM: pytris -- RoM; security issues; abandoned upstream Bug #608689 [pytris] RM: pytris -- security issues; abandoned upstream Changed Bug title to 'RM: pytris -- RoM; security issues; abandoned upstream' from 'RM: pytris --

Bug#608744: unblock: mercurial-server/1.1-1

2011-01-03 Thread Teodor
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: freeze-exception Please unblock package mercurial-server. The two RC bugs for this package were fixed so it should get back for inclussion in Debian 6.0 (squeeze). Thanks unblock

Bug#608754: unblock: corosync/1.2.1-4

2011-01-03 Thread Guido Günther
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock corosync 1.2.1-4 with this single change: * [2ebaf59] Move corosync start out of rcS since we want to be able to log to syslog and rsyslog isn't started in rcS. (Closes:

Bug#608805: unblock: gmorgan/0.27-2

2011-01-03 Thread Bart Martens
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock gmorgan 0.27-2. The only change: * debian/rules: Replace po/Makefile.in.in. Closes: #583466. -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org

(future unblock) RFS: mobile-broadband-provider-info (updated package)

2011-01-03 Thread Bhavani Shankar R
Dear mentors, I am looking for a sponsor for the new version 20110103-1 of my package mobile-broadband-provider-info. It builds these binary packages: mobile-broadband-provider-info - database of mobile broadband service providers The package appears to be lintian clean. Rationale for freeze

Bug#608818: unblock: syslog-ng/3.1.3-2

2011-01-03 Thread Moritz Muehlenhoff
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package syslog-ng. It fixes a kfreebsd-specific security issue w/o CVE. unblock syslog-ng/3.1.3-2 -- System Information: Debian Release: 6.0 APT prefers unstable APT

Bug#608819: unblock: vlc/1.1.3-1squeeze1

2011-01-03 Thread Moritz Muehlenhoff
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package vlc. It fixes CVE-2010-3907. unblock vlc/1.1.3-1squeeze1 -- System Information: Debian Release: 6.0 APT prefers unstable APT policy: (500, 'unstable')

Bug#608820: unblock: xfig/1:3.2.5.b-1.1

2011-01-03 Thread Moritz Muehlenhoff
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package xfig. It fixes CVE-2010-4262. unblock xfig/1:3.2.5.b-1.1 -- System Information: Debian Release: 6.0 APT prefers unstable APT policy: (500, 'unstable')

Bug#608827: unblock: tenshi/0.11-2

2011-01-03 Thread Ignace Mouzannar
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: freeze-exception Hello, I'd be glad if you could unblock tenshi/0.11-2. The upload would fix the following RC bug: #606789 (and duplicate #605240) I have attached the relevant debdiff of the

Clarification request regarding translation updates

2011-01-03 Thread Thijs Kinkhorst
Hi, The release team has sent a (in my reading) pretty unambiguous statement to DDA that only uploads that fix RC bugs will be unblocked. However, I've seen a number of unblocks for translation updates since. So it's unclear to me now whether I should be uploading updates for Debconf po

Re: Clarification request regarding translation updates

2011-01-03 Thread Julien Cristau
On Mon, Jan 3, 2011 at 21:35:56 +0100, Thijs Kinkhorst wrote: Hi, The release team has sent a (in my reading) pretty unambiguous statement to DDA that only uploads that fix RC bugs will be unblocked. However, I've seen a number of unblocks for translation updates since. So it's unclear

Bug#608744: marked as done (unblock: mercurial-server/1.1-1)

2011-01-03 Thread Debian Bug Tracking System
Your message dated Mon, 03 Jan 2011 22:23:44 +0100 with message-id 4d223e60.1080...@dogguy.org and subject line Re: Bug#608744: unblock: mercurial-server/1.1-1 has caused the Debian Bug report #608744, regarding unblock: mercurial-server/1.1-1 to be marked as done. This means that you claim that

Bug#608744: unblock: mercurial-server/1.1-1

2011-01-03 Thread Teodor MICU
Hi, 2011/1/3 Mehdi Dogguy me...@dogguy.org: I think it's too late to get it back in Squeeze. What would be the risk of including this package with no release critical bugs into 6.0? There are packages with RC bugs that are ignored and still allowed to be released with 6.0, but a package with

Processed: RM bug severity

2011-01-03 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: severity 608740 normal Bug #608740 [release.debian.org] RM: pytris -- RoM; security issues; abandoned upstream Severity set to 'normal' from 'grave' severity 608689 normal Bug #608689 [ftp.debian.org] RM: pytris -- RoM; security issues;

Re: (future unblock) RFS: mobile-broadband-provider-info (updated package)

2011-01-03 Thread Jonathan Wiltshire
On Mon, Jan 03, 2011 at 10:12:29PM +0530, Bhavani Shankar R wrote: I am looking for a sponsor for the new version 20110103-1 of my package mobile-broadband-provider-info. If the release team will indicate that there is any chance of this getting into Squeeze, I'll happily make a one-time upload

Bug#608847: unblock: kdebase-workspace/4:4.4.5-6

2011-01-03 Thread Modestas Vainius
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: freeze-exception Please unblock package kdebase-workspace Hello, this revision documents (in README.Debian) a workaround for quite annoying bug and fixes the crash on kFreeBSD that was caused by

Re: (future unblock) RFS: mobile-broadband-provider-info (updated package)

2011-01-03 Thread Bhavani Shankar R
On Tue, Jan 4, 2011 at 3:33 AM, Jonathan Wiltshire j...@debian.org wrote: On Mon, Jan 03, 2011 at 10:12:29PM +0530, Bhavani Shankar R wrote: I am looking for a sponsor for the new version 20110103-1 of my package mobile-broadband-provider-info. If the release team will indicate

Bug#608861: unblock: firmware-nonfree/0.28

2011-01-03 Thread Ben Hutchings
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package firmware-nonfree. This includes several important fixes for network hardware: - Added firmware patches for some Realtek network controllers that allow them to

Re: (future unblock) RFS: mobile-broadband-provider-info (updated package)

2011-01-03 Thread Richard Laager
On Tue, 2011-01-04 at 10:52 +0530, Bhavani Shankar R wrote: as the README says its safe to update the package at any stage. Isn't this basically the same as saying, We don't introduce bugs in our software.? If they put the wrong information into this package, wouldn't that break your mobile

Re: (future unblock) RFS: mobile-broadband-provider-info (updated package)

2011-01-03 Thread Paul Tagliamonte
On Tue, Jan 4, 2011 at 1:29 AM, Richard Laager rlaa...@wiktel.com wrote: On Tue, 2011-01-04 at 10:52 +0530, Bhavani Shankar R wrote: as the README says its safe to update the package at any stage. Isn't this basically the same as saying, We don't introduce bugs in our software.? If they put

Re: (future unblock) RFS: mobile-broadband-provider-info (updated package)

2011-01-03 Thread Paul Tagliamonte
FWIW, this package was unblocked a few times already, IIRC. I think Paul Wise sponsored one of them, unless I'm going crazy ( which there Sorry for the quick double post. Here's the thread. pabs uploaded -- http://lists.debian.org/debian-mentors/2010/11/msg00143.html medhi unblocked --

Re: (future unblock) RFS: mobile-broadband-provider-info (updated package)

2011-01-03 Thread Bhavani Shankar R
On Tue, Jan 4, 2011 at 11:59 AM, Richard Laager rlaa...@wiktel.com wrote: On Tue, 2011-01-04 at 10:52 +0530, Bhavani Shankar R wrote: as the README says its safe to update the package at any stage. Isn't this basically the same as saying, We don't introduce bugs in our software.? If they put