Re: a few comments on the release notes

* peter green ([EMAIL PROTECTED]) [061116 01:19]: 1: the doc-base thing seems to have been copied straight from the sarge notes, iirc this was caused by the old version of doc-base in woody so it shouldn't be an issue for sarge-etch upgrades. Can anyone confirm/refute this. 2: the aptitude

dash 0.5.3-4 for etch

Hi, dash version 0.5.3-4 is fine for etch, please let it migrate. $ w3m -dump http://ftp-master.debian.org/testing/update_excuses.html.gz | grep -A5 dash * dash (0.5.3-3 to 0.5.3-4) + Maintainer: Gerrit Pape + 22 days old (needed 10 days) + Not touching package, as

rrdtool

On Thu, Nov 16, 2006 at 04:57:31AM -0800, Steve Langasek wrote: We have not yet reached a point where we believe there should be a hard freeze of updates into etch, but we ask your continued support by avoiding uploads that are likely to introduce regressions or be disruptive to other packages

Re: testing d-i Release Candidate 1 and more release adjustments

On Thu, 2006-11-16 at 04:57 -0800, Steve Langasek wrote: Release goals and etch-ignores == After a mailing list discussion about release-criticality and policy, we've decided to include fixing bashisms as a release goal. This means that if packages have bugs

preparation for 2.6.18-6 kernel upload on monday 20th of november 2006.

Hi, ... As you may know, or not, we are waiting for the abi-breaking 2.6.18-6 to be uploaded for pushing the 2.6.18 kernel into etch. It seems 2.6.18.3 is announced for saturday, so this would mean a natural tentative schedule of let's say monday the 20th of november 2006 as upload date. Is

Re: testing d-i Release Candidate 1 and more release adjustments

On Thu, Nov 16, 2006 at 10:00:48AM -0800, Thomas Bushnell BSG wrote: Release goals and etch-ignores == After a mailing list discussion about release-criticality and policy, we've decided to include fixing bashisms as a release goal. This means that if

Re: preparation for 2.6.18-6 kernel upload on monday 20th of november 2006.

Sven Luther [EMAIL PROTECTED] writes: Hi, ... As you may know, or not, we are waiting for the abi-breaking 2.6.18-6 to be uploaded for pushing the 2.6.18 kernel into etch. It seems 2.6.18.3 is announced for saturday, so this would mean a natural tentative schedule of let's say monday the

Re: Bug#398922: advi: Installs arch-independent files in /usr/lib

Steve Langasek [EMAIL PROTECTED] wrote: This particular kind of FHS violation (arch-indep code in arch-dep directory) is not generally RC, because there are no significant functional problems as a result of mis-identifying files as arch-dependent that aren't. Then please clarify this in the

Re: freeze upstream releases

On Thu, 2006-11-16 at 18:43 -0800, Steve Langasek wrote: On Thu, Nov 16, 2006 at 02:33:24PM +0100, Bart Martens wrote: About this message: http://lists.debian.org/debian-devel-announce/2006/11/msg4.html You wrote: We do expect to freeze the full archive soon now that the

Handling RC doesn't build documentation bugs

Dear release team, in the last couple of weeks, I've tried to keep an eye on FTBFS bugs that involve failed attempts to create documentation, and provided a couple of patches for this. Due to real-life time constraints, I've promised myself to no longer visit http://bts.turmzimmer.net/ and care

Package maintainers: please consider freezing your debconf templates now....

(please respect Reply-to to avoid cluttering 3 lists at the same time) To make the work of the French l10n team easier I do a daily survey of changes to debconf templates that trigger translation updates needs. I'm currently seeing changes to 1 or 2 packages *every day*. Most of these are