Transitioning to dhcp3

2008-01-13 Thread Andrew Pollock
Hello, Now that the v2 DHCP packages have been removed, we need to transition the DHCP v3 packages to that name. I've never done something like this before, and rather than trying to be clever and buggering it all up, I'd rather seek some advice from the outset. So here I am. What is the best w

Unblock request for mantis (was: Re: Is mantis still not supportable by the support team? (was: Re: Unblock request for mantis))

2008-01-13 Thread Patrick Schoenfeld
Hi, I would like to request the unblocking of mantis so that it can enter lenny as I now got the okay of the Security team (which was a condition as Andreas Barth and Mark 'HE' Brockschmidt explained to me). See below for Moritz Muehlenhoffs statement about security support for mantis in lenny.

Re: Is mantis still not supportable by the support team? (was: Re: Unblock request for mantis)

2008-01-13 Thread Moritz Muehlenhoff
Patrick Schoenfeld wrote: > So given the current situation could the security team please consider > supporting mantis in the upcoming release of lenny? Yes, we can do that. Cheers, Moritz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [

Re: Is mantis still not supportable by the support team? (was: Re: Unblock request for mantis)

2008-01-13 Thread Patrick Schoenfeld
Hi Moritz, sorry for my late reply; I wanted to confer with Thijs on this first, because we were in contact on this earlier already and also I wanted to act before replying. On Sun, Dec 09, 2007 at 11:31:47PM +0100, Moritz Muehlenhoff wrote: > We're swamped in email. I understand that. Sorry if

Re: libapache2-mod-perl2 stable update for CVE-2007-1349

2008-01-13 Thread Moritz Muehlenhoff
Roberto C Sánchez wrote: >> Unfortunately the vulnerability described above is not important enough >> to get it fixed via regular security update in Debian stable. It does >> not warrant a DSA. >>=20 >> However it would be nice if this could get fixed via a regular point upda= > te[1]. > > Just c

Re: hint for vice/1.22-2

2008-01-13 Thread Laszlo Boszormenyi
Hi all involved, On Sun, 2008-01-13 at 12:54 +0100, Philipp Kern wrote: > Please contact d-release next time to get the issue resolved. Will do. > Not arch:all (architecture independent) but arch:any (as it's > architecture dependent), but yes. The s390 porter noted to remove the > not-for-us.

Re: hint for vice/1.22-2

2008-01-13 Thread Philipp Kern
On Sun, Jan 13, 2008 at 12:24:00PM +0100, Laszlo Boszormenyi wrote: > On Sat, 2008-01-12 at 13:30 -0800, Steve Langasek wrote: > > On Sat, Jan 12, 2008 at 09:26:59PM +0100, Laszlo Boszormenyi wrote: > > That's not how hinting works. > Thought so, but couldn't get porters to remove the false depend

Re: hint for vice/1.22-2

2008-01-13 Thread Luk Claes
Laszlo Boszormenyi wrote: > Hi Steve, > > On Sat, 2008-01-12 at 13:30 -0800, Steve Langasek wrote: >> On Sat, Jan 12, 2008 at 09:26:59PM +0100, Laszlo Boszormenyi wrote: >> That's not how hinting works. > Thought so, but couldn't get porters to remove the false dependency. > >> But that seems un

Re: hint for vice/1.22-2

2008-01-13 Thread Laszlo Boszormenyi
Hi Steve, On Sat, 2008-01-12 at 13:30 -0800, Steve Langasek wrote: > On Sat, Jan 12, 2008 at 09:26:59PM +0100, Laszlo Boszormenyi wrote: > That's not how hinting works. Thought so, but couldn't get porters to remove the false dependency. > But that seems unlikely to happen, since you've removed