Freeze exception request: radioclk

radioclk (1.0.ds1-8) unstable; urgency=low * Debconf translation upload only: + Japanese (Hideki Yamane (Debian-JP)). (Closes: #554111) -- Paul Martin Sat, 28 Aug 2010 17:52:06 +0100 -- Paul Martin signature.asc Description: Digital signature

Re: Freeze exception: mingetty 1.08-2

On Sat, Sep 25, 2010 at 09:51:05AM +0100, Adam D. Barratt wrote: > On Sat, 2010-09-25 at 01:46 +0100, Paul Martin wrote: > > I've just uploaded mingetty 1.08-2 with just a fix for critical > > security bug #597382. Apart from the changelog entry, there are no > > o

Freeze exception: mingetty 1.08-2

I've just uploaded mingetty 1.08-2 with just a fix for critical security bug #597382. Apart from the changelog entry, there are no other changes than the diff attached to the bug report. -- Paul Martin signature.asc Description: Digital signature

Freeze exception: mingetty 1.07-2 (correction)

My mistake: it appears that 1.08-1 never got uploaded. I've applied the patch against 1.07 and uploaded again. -- Paul Martin signature.asc Description: Digital signature

Re: request for exception for popt

rs are sure that they don't need the localization information, mainly error messages. (Thanks to Frans Pop for bringing this to my attention.) -- Paul Martin <[EMAIL PROTECTED]> Wed, 25 Jun 2008 07:25:34 +0100 $ dpkg --contents deb/popt/libpopt0-udeb_1.14-4_i386.udeb drwxr-xr-x

Please look at bug #279965

hes are in the BTS. Your advice, please. -- Paul Martin <[EMAIL PROTECTED]> signature.asc Description: Digital signature

Re: logrotate 3.7-2 and m68k

instead of just `cc', and yes, I've set > CC. How do I make the logrotate build system use the right compiler? Strange. I used "export CC=gcc-3.0" when compiling (using dpkg-buildpackage), and it worked. Is gcc-3.4 definitely going to be in sarge[m68k]? -- Paul Martin <[EMAIL PROTECTED]>

Re: logrotate 3.7-2 and m68k

On Mon, Aug 02, 2004 at 01:43:00PM +0200, Jeroen van Wolffelaar wrote: > On Mon, Aug 02, 2004 at 12:25:26PM +0100, Paul Martin wrote: > > The m68k buildd was choking on logrotate due to a gcc internal error in > > gcc-3.3. I've been pestered into ensuring that 3.7 gets

logrotate 3.7-2 and m68k

inary-only upload on crest using gcc-3.0 and uploaded it to incoming today. As the changelog shows "low" priority, what's the chances of logrotate_3.7-2_m68k.deb getting into sarge? (Logrotate is "Priority: important") -- Paul Martin <[EMAIL PROTECTED]> signature.asc Description: Digital signature