Re: gcc-defaults, gcc-3.3, gcc-3.4 for testing

2005-04-01 Thread Steve Langasek
Hi Matthias,

On Sat, Mar 26, 2005 at 01:50:02PM +0100, Matthias Klose wrote:
 gcc-3.3 and gcc-3.4 were addressed in

   http://lists.debian.org/debian-release/2005/03/msg00027.html

 the gcc-3.3 changes (compared to -8) include two m68k specific fixes
 concerning wrong generation of code, and one hppa64 related update
 (PR19697). more on the other noise in the update in a separate
 message.

Does in a separate message mean there's more information about these
changes coming?

 the interesting gcc-3.4 changes (compared to -6), affecting libgcc1,
 include an update of libunwind to version 0.98.4 (Fix a typo in
 _ReadSLEB.c which caused hangs when throwing exceptions from Intel
 ICC-compiled programs). All other changes relate to binary packages,
 which are not used by default.

gcc-3.4 approved.

 gcc-defaults, currently in incoming, not yet built for arm, adds a new
 convenience package libgcj-dev, which makes dependencies for depending
 packages easier to manage. Packages using gcj -C (byte compiling)
 should (build-)depend on gcj, packages compiling to native code,
 should (build-)depend on libgcj-dev. surprised by the speed this new
 binary package entered unstable, it should go to testing as well not
 to block other packages now depending on it.

Also approved.

Thanks,
-- 
Steve Langasek
postmodern programmer


signature.asc
Description: Digital signature


Re: suggestions for packages to force to testing for security fixes

2005-04-01 Thread Steve Langasek
On Wed, Mar 30, 2005 at 09:06:39PM -1000, Joey Hess wrote:
 Packages that have a security fix blocked by arm only:

 ltris 1.0.6-1.1 needed, have 1.0.6-1 for CAN-2005-0825 
 racoon 1:0.5-5 needed, have 0.3.3-7 for CAN-2005-0398 

Force hints (but not force-hint hints) added.  Feel free to do these
yourself, y'know. :)

 Packages that are blocked by arm and m68k:

 epiphany-browser 1.4.8-2 needed, have 1.4.7-3 for CAN-2005-0238 

Also pushed in because m68k has been uploaded; otherwise I would've waited.

 lsh-utils 2.0-1 needed, have 1.4.2-8.2 for CAN-2005-0389
 lsh-utils 2.0.1-1 needed, have 1.4.2-8.2 for CAN-2005-0814 
   (Also has a RC bug though.)

yeah, that doesn't sound like a win yet (though it's also built on m68k).

 smail 3.2.0.115-7 needed, have 3.2.0.115-5.1 for CAN-2005-0892 
   (The RC bug 301428 should not block this fix from sarge.)

Also pushed in, now that it's built on m68k and I've had a chance to look at
301428.

 Packages that are frozen:

 netkit-telnet 0.17-28 needed, have 0.17-26 for DSA-697-1
   0.17-27 consisted of misc other changes, but
   0.17-28 only fixed the security hole (which is quite a bad one)

0.17-29 is tentatively approved; still needs to age and get built
everywhere.

-- 
Steve Langasek
postmodern programmer


signature.asc
Description: Digital signature


init.d script dependencies for etch?

2005-04-01 Thread Lars Wirzenius
The traditional way of ordering init.d scripts is to have two-digit
numbers for the symlinks in /etc/rc*d directories. It seems pretty clear
to me that a dependency based scheme would work better here. Switching
from one to the other could, I think, be done gradually, given
sufficient magic and hair, but it is a big change that is going to touch
a great many packages.

I would like to work on making this happen for etch. I don't have an
implementation yet, let alone a plan for how to do it, and I won't start
work until after sarge is released, so this is just a heads-up for the
release team.

Anyone who wants to tell me this is a really bad idea, or has
suggestions on the implementation, please mail me in private or take
this thread to -devel. Thanks.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



mimedefang should go into sarge

2005-04-01 Thread Christoph Martin
Hi folks,

for no 36 days there is a version of mimedefang which fixes an important
bug. Through a wrong patch it was searching for on of its configuration
files in the wrong location. It did not go into testing because of the
missing build on arm. Please help it getting into sarge.

Thanks

Christoph
--

Christoph Martin, EDV der Verwaltung, Uni-Mainz, Germany
 Internet-Mail:  [EMAIL PROTECTED]
  Telefon: +49-6131-3926337
  Fax: +49-6131-3922856


signature.asc
Description: OpenPGP digital signature


Security Fix for openssl in sarge

2005-04-01 Thread Christoph Martin
Hi folks,

in sarge there is a version of openssl which lacks the security fix
CAN-2004-0975. A corrected version is in sarge for three months now
where only this problem is fix. openssl is frozen, but please push it
into testing to have that fix in sarge.

Thanks
Christoph
--

Christoph Martin, EDV der Verwaltung, Uni-Mainz, Germany
 Internet-Mail:  [EMAIL PROTECTED]
  Telefon: +49-6131-3926337
  Fax: +49-6131-3922856


signature.asc
Description: OpenPGP digital signature


PostgreSQL stalled [was: Re: Release update: debian-installer, kernels, infrastructure, freeze, etch, arm]

2005-04-01 Thread Martin Pitt
Hi Debian Release team!

Andreas Barth [2005-04-01 15:48 +0200]:
 In the meantime, if you have a release-critical bugfix for sarge that is
 being held out of testing *only* by a missing arm build, please contact
 the release team so that we can arrange to push the package in if
 appropriate.

Indeed I have such a package. PostgreSQL failed to build on arm and
m68k some 30 days ago due to a broken xserver-common package; I
notified the buildd teams about this, m68k is already sorted out now.
But it would really be nice to get the sid version into Sarge, I only
do bugfixes for some time now.

Can you please push this a bit?

Thanks in advance and have a nice day,

Martin


-- 
Martin Pitt   http://www.piware.de
Ubuntu Developerhttp://www.ubuntulinux.org
Debian Developer http://www.debian.org


signature.asc
Description: Digital signature


Re: please make libkrb53 priority 'standard', since nfs-utils depends on it

2005-04-01 Thread Chip Salzenberg
According to Steve Langasek:
 Chip, how are things looking now for nfs-utils?

So far, no worries.

 I remember seeing a new RC bug on it after you sent in your original
 request.  Has that been taken care of?

That'd be #294959.  I don't recommend fixing it for sarge, as a fix
will involve playing with the boot-up sequence.  I'd prefer a don't
do that note in the documentation - Don't mark NFSv4 filesystems
'auto' in fstab.
-- 
Chip Salzenberg- a.k.a. -[EMAIL PROTECTED]
 Open Source is not an excuse to write fun code
then leave the actual work to others.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: Security Fix for openssl in sarge

2005-04-01 Thread Steve Langasek
Hi Christoph,

On Fri, Apr 01, 2005 at 05:23:04PM +0200, Christoph Martin wrote:
 in sarge there is a version of openssl which lacks the security fix
 CAN-2004-0975. A corrected version is in sarge for three months now
 where only this problem is fix. openssl is frozen, but please push it
 into testing to have that fix in sarge.

Approved for testing.

Thanks,
-- 
Steve Langasek
postmodern programmer


signature.asc
Description: Digital signature


Re: mimedefang should go into sarge

2005-04-01 Thread Steve Langasek
Christoph,

On Fri, Apr 01, 2005 at 05:20:00PM +0200, Christoph Martin wrote:
 for no 36 days there is a version of mimedefang which fixes an important
 bug. Through a wrong patch it was searching for on of its configuration
 files in the wrong location. It did not go into testing because of the
 missing build on arm. Please help it getting into sarge.

For non-RC bugfixes, we would appreciate it if you would use the announced
website, http://www.wolffelaar.nl/~sarge/, to let us know about these
issues.

Thanks,
-- 
Steve Langasek
postmodern programmer


signature.asc
Description: Digital signature