Re: bug in tar 1.14-2.1

Hi mollo, On Sunday, 19 Mar 2006, you wrote: > On Tue, 7 Mar 2006 15:19:58 +0100 > using tar 1.14-2.1 > > fw:/home/mathieu# tar --rmt-command=/usr/sbin/rmt -cvf > '[EMAIL PROTECTED]:/home/mathieu/test.tgz' /etc tar: > [EMAIL PROTECTED]:/home/mathieu/test.tgz: Cannot open: Input/output > error ta

Re: bug in tar 1.14-2.1

Hi Andi, On Monday, 27 Mar 2006, you wrote: > * Martin Zobel-Helas ([EMAIL PROTECTED]) [060324 16:00]: > > Looks like just rebuilding the security version resolves that error, for > > whatever reason. Julien and me just cross checked that and got the same > > result. >

Status of Debian Sarge R2

Hi, the purpose of this mail is to make sure we all have the same idea what's currently missing. If you disagree or if there are more things to say about, please just answer. All packages which we currently consider for R2 are listed at [1]. Packages still RC buggy in R2 -.-.-.-.-.-.-.-.-.-.-.-.-

Re: libapache2-request-perl security upgrade broken

Hi Cyril, On Monday, 03 Apr 2006, you wrote: > (FYI: running sarge with security upgrades, without proposed-updates, on > i386) > When trying to upgrade to the latest libapache2-request-perl > (2.04-dev-1sarge2) > I've got a broken dep on perl >= 5.8.4-8sarge4, but perl 5.8.4-8sarge3 only > is a

Re: Preparation of the next stable Debian GNU/Linux update (V)

Hi Frank, On Sunday, 09 Apr 2006, you wrote: > On Wed, Apr 05, 2006 at 05:58:17PM +0200, Martin Zobel-Helas wrote: > > fai stable2.8.4all source > > fai updates 2.8.4sarge1 all source > > > > Fixes three problems > > This ex

Re: draft of announcement for sarge r2

Hi Kevin, > On another topic, why isn't wzdftpd (DSA 1006) included in the release > announcement? It is listed as OK on the wiki page > http://wiki.debian.org/DebianReleases/PointReleases > but not listed at all on the release preparation page > http://release.debian.org/stable/3.1/3

Re: draft of announcement for sarge r2

Hi, On Friday, 14 Apr 2006, you wrote: > * Andreas Barth ([EMAIL PROTECTED]) [060414 17:14]: > > * Andreas Barth ([EMAIL PROTECTED]) [060412 11:07]: > > > as we're now directly moving towards sarge r2, we drafted an > > > announcement. Please see the attachement for more details. We will > > > not

Re: draft of announcement for sarge r2

Hi Filipus, > Hum, if 1000-2 is accepted and I understand correctly that 5.8.4-8sarge4 > won't make it in r2, does that mean that #360900 will propagate to r2? Perl 5.8.4-8sarge4 wi enter r2 with the point release. > OK, I somehow expected this answer, but your draft refers to this page > and

Re: sarge upgrade - linux, grub conflict

Dear Bastian Blank, > The attached patch is a port of my original patch to the version in > sarge. > diff -u grub-0.95+cvs20040624/debian/changelog > grub-0.95+cvs20040624/debian/changelog > --- grub-0.95+cvs20040624/debian/changelog > +++ grub-0.95+cvs20040624/debian/changelog > @@ -1,3 +1,9 @@

Re: gcc 4.1 or not

Hi Andi, On Wednesday, 10 May 2006, you wrote: > there were some requests, e.g. by Martin Michlmayr to the release team > whether we could switch gcc to 4.1 or not for etch. As we're heading to I know, tbm tried to build all packages on mips*. It would be intersting to know, how other architectu

Re: bits from the release team: release goals, python, X.org, amd64, timeline

Hi Andreas, On Wed, May 31, 2006 at 08:45:12PM +0200, Andreas Barth <[EMAIL PROTECTED]> wrote: > Hi, > > * Fabrice Lorrain ([EMAIL PROTECTED]) [060531 00:28]: > > I've a vague memory of a general "consensus" on "let's see how it works > > during the sarge era" for volatile.debian.net. > > > >

Re: devmapper in sarge r3

Hi Roger, On Sun, Jun 11, 2006 at 12:22:08AM +0100, Roger Leigh <[EMAIL PROTECTED]> wrote: > I uploaded a devmapper update to stable-proposed-updates just prior to > the release of r2, but it missed the deadline by a few days. > > It's marked on > http://wiki.debian.org/DebianReleases/PointRelea

Timeline for r3

Hi, to keep everyone in the loop i would like to discuss my current plans for the r3 timeline. We have no fixed "freeze" date for r3 yet, but i currently plan to freeze one or two weeks after the pending 2.6 kernel update is pushed by the security team. If this is not enough time for the porters,

Re: Timeline for r3

Hi security-team, > I currently consider #373854 as RC for r3, and ask the security team to > either update it with another DSA or to tell us if we should fix it via > proposed-updates. I also recently became aware off #374733, #375120, #373581 and #373980 (all package libfreetype6, in connection

Re: timezone variable not set correctly, bug blocking LSB Conformance

Hi Aurelien, On Mon, Jul 03, 2006 at 06:44:16AM +0200, Aurelien Jarno <[EMAIL PROTECTED]> wrote: > Hi SRM team! > > Would such a fix to the glibc be accepted for a stable release? i would be first interested, which LSB versions are effected by this. I don't see any need for fixing newer LSB is

LSB 3.1 status for etch?

Hi guys, as LSB 3.1 compatibility is one of the pet release goals for etch, it would be nice to have some overview of what still needs to be fixed in etch for LSB 3.1 compatibility. Could you please rerun the test-suite on current etch or give me a hint how to do it on my own? Greetings Martin

Re: Timeline for r3

Hi, okay with me. On Fri, Jul 07, 2006 at 06:31:57PM +0200, Frans Pop <[EMAIL PROTECTED]> wrote: > On Friday 30 June 2006 23:08, Frans Pop wrote: > > Dann has today uploaded the kernel udeb packages for all arches, except > > for AMD64 (as that has not yet been released by the security team). >

Re: LSB 3.1 status for etch?

Hi Jeff, On Thu, Jul 06, 2006 at 05:09:35PM CEST, Jeff Licquia <[EMAIL PROTECTED]> wrote: > On Tue, 2006-07-04 at 00:35 +0200, Martin Zobel-Helas wrote: > > as LSB 3.1 compatibility is one of the pet release goals for etch, it > > would be nice to have some overview of w

Re: LSB 3.1 status for etch?

Hi Petter, On Tue, Jul 11, 2006 at 09:57:00AM +0200, Petter Reinholdtsen <[EMAIL PROTECTED]> wrote: > > [Martin Zobel-Helas, 2006-07-10] > > Thanks for the information. I currently do not find the time to run > > the tests myself, so i will wait for your results. Plea

Re: Bug#378714: vlan: installing package breaks proxy-arp config [sarge]

Hi Loïc, On Tue, Jul 18, 2006 at 05:25:20PM +0200, Loïc Minier <[EMAIL PROTECTED]> wrote: > This is #330673. > > From the 1.9-1 changelog: > * Fix /etc/network/if-up.d/ip to not set rp_filter to 1 when it isn't > configured. (Closes: #330673) [debian/ip-if-up] > > I'm willing to prepar

Please accept packages to proposed-updates

Hi ftpmasters/assistants, find below a list of packages (and their version) which are currently in queue/p-u-new where the stable release team thinks they are okay, so please accepted them for proposed-updates. cscope/15.5-1.1sarge1 gnupg/1.4.1-1.sarge4 horde2/2.2.8-1sarge3 horde3/3.0.4-4sarge4 k

Re: Please accept packages to proposed-updates

Hi all, On Tue, Jul 25, 2006 at 06:40:25PM -0300, Otavio Salvador <[EMAIL PROTECTED]> wrote: > Julien Danjou <[EMAIL PROTECTED]> writes: > > > On Tue, Jul 25, 2006 at 11:19:24PM +0200, Loïc Minier wrote: > >> I don't see "vlan" in there, but I uploaded it a week ago, and never > >> got any AC

Re: Please accept packages to proposed-updates (Round 2)

Hi AJ, On Tue, Jul 25, 2006 at 11:02:46PM +0200, Martin Zobel-Helas <[EMAIL PROTECTED]> wrote: > find below a list of packages (and their version) which are currently in > queue/p-u-new where the stable release team thinks they are okay, so > please accepted them for proposed-upd

Packages awaiting proposed-updates moderation

Hi, for those who wonder why their package did not yet hit proposed-updates, they want to have a look on [1] and [2]. The backlog we had is now decreasing, d-i builds should have been started by now. Greetings Martin [1] http://lists.debian.org/debian-devel-announce/2006/06/msg7.html [2] h

Re: Shadow updates for sarge (was: )Re: Packages awaiting proposed-updates moderation)

Hi, > Given that I'm away for 3 weeks from now, I leave all this in the > hands of my co-maintainer, Nicolas François (nekral on IRC). Please > get in touch with him for ANY issue related to shadow (please CC me or > [EMAIL PROTECTED]). His mail address is CC'ed > to this mail and he is mentioned

Re: Preparation of the next stable Debian GNU/Linux update (I)

Hi Rene, On Thu, Aug 24, 2006 at 08:24:35PM +0200, Rene Engelhard <[EMAIL PROTECTED]> wrote: > Martin Zobel-Helas wrote: > > Accepted Packages > > - > > > > These packages will be installed into the stable Debian distribution > >

Re: Preparation of the next stable Debian GNU/Linux update (I)

Hi Kevin, On Fri, Aug 25, 2006 at 09:59:53AM -0700, Kevin B. McCarty <[EMAIL PROTECTED]> wrote: > Martin Zobel-Helas wrote: > > > > mozilla-thunderbird-devstable1.0.2-2.sarge1.0.7 alpha arm > > hppa i386 ia64 m68k mips mipsel powerpc s390 sparc

Re: mailman 2.1.5-8sarge3: screwup between security and maintainer upload

> Imho, it's more useful to upload 2.1.5-8sarge4 and only bump the > version number to get the new version built for all architectures into > the archive. Please go ahead. Greetings Martin -- Martin Zobel-Helas GPG Key-ID:0x5d64f870 Debian Developer

Re: vim-vimoutliner to stable-proposed-updates?

broken), but i don't see a reason ATM to fix a normal bug in the next point release. So no, i don't see this this as a valid candidate. Sorry. Greetings Martin -- Martin Zobel-Helas GPG Key-ID:0x5d64f870 Debian DevelopereMail Privat:

Meeting Minutes from the latest SRM meeting

ere skipped for this meeting however. - Tracking RC bugs for stable on bts.turmzimmer.net Andi will work on that. -- Martin Zobel-Helas GPG Key-ID:0x5d64f870 Debian DevelopereMail Privat: [EMAIL PROTECTED] Debian Stable Release

Preparation of the next stable Debian GNU/Linux update (I)

Preparation of Debian GNU/Linux 3.1r4 = An up-to-date version is at . We are preparing the next revision of the current stable Debian distribution (sarge) and will frequently send reports so people can actually comme

Re: Preparation of the next stable Debian GNU/Linux update (I)

Hi Matthijs, > Hi, > > What about #375494 and #377047, those are security bugs in the current > stable distribution (Sarge) and according to the Security Team it > didn't warrant an upload. Although it has a CVE so I think it's worth > an upload to stable. > > What do you think ? If you are the

Preparation of the next stable Debian GNU/Linux update (II)

. They have the final power to accept a package or not. If you want to comment on this list, please send a mail to the debian release mailing list . Last updated 2006/09/22 15:29 MET -- Martin Zobel-Helas GPG Key-ID:0x5d64f870 Debian Developer

Re: Preparation of the next stable Debian GNU/Linux update (II)

Hi Roger, On Sat, Sep 23, 2006 at 12:07:58AM +0100, Roger Leigh <[EMAIL PROTECTED]> wrote: > Please could you make sure that devmapper is included in the next > stable update? It was supposed to be included in the last update, but > for some reason was omitted. please go ahead and upload. Greet

Bug#397939: Proposal: Packages must have a working clean target

Package: debian-policy Severity: important Hi, during the last months i had to review several packages. Quite a number of packages were not buildable two times (eg. "unrepresentable changes to source"). Most of these packages used svn-buildpackage or cvs-buildpackage. This bug is quite annoying

[Call-for-Testing] open-iscsi from experimental

Hi, as the open-iscsi interface in kernel 2.6.18 changed we will need a newer version of open-iscsi in testing as soon as 2.6.18 hit testing. I recently NMUed open-iscsi to close two RC bugs and needed to use a new major upstream version, to get it proper working with kernel 2.6.18. I therefor upl

Preparation of the next stable Debian GNU/Linux update (I)

ages also still in the pipeline to be accepted Greetings Martin -- Martin Zobel-Helas GPG Key-ID:0x5d64f870 Debian DevelopereMail Privat: [EMAIL PROTECTED] Debian Stable Release Manager eMail Debian: [EMAIL PROTECTED] signature.asc Description: Digital signature

Re: ttf-junicode

On Tue Dec 26, 2006 at 11:59:55 +0100, Gürkan Sengün wrote: > hello > > >>is it possible to let this version go into testing. > >>it improves the font in many ways, here's the upstream > >>changelog: > > > >I'm not keen to unblock it as it's a new upstream version with lots > >of > >changes... >

Re: ttf-junicode

On Tue Dec 26, 2006 at 19:04:43 +0100, Gürkan Sengün wrote: > On 2006-12-26 14:11:39 +0100 Martin Zobel-Helas <[EMAIL PROTECTED]> wrote: > > > On Tue Dec 26, 2006 at 11:59:55 +0100, Gürkan Sengün wrote: > >> hello > >> > >>>> is it possible to l

Re: Timezone update for sarge

Hi, On Thu Feb 08, 2007 at 07:15:06 +0100, Aurelien Jarno wrote: > The problem is fixed in sarge-proposed-update with glibc version > 2.3.2.ds1-22sarge5 since the end of November. > I would like to know if the stable release team is planning to do > something to update the glibc in Sarge. Yes

Bug#410788: debian-archive-keyring: Please include Etch Stable Release Key

Package: debian-archive-keyring Version: 2006.11.22 Severity: important Tags: patch Hi Michael, could you please include the following attached key (ID ADB11277)? This is needed, as the Stable Release Managers will sign Etch with this key, as soon as Etch is released. Greetings Martin -- Syste

Re: Release Team meeting?

h my DSA hat on: It would make sense to have someone from the DSA team present during that IRC meeting, as architecture qualification has a direct impact on our hardware and resource planning. Could you set up a doodle for that, and keep us posted? Cheers, Martin -- Martin Zobel-Helas

Re: sparc qualification for Wheezy

e an UltraSparc II porterbox, and we are considering decommissioning our single remaining UltraSparc II buildd machine. Maybe it would be a good idea to officially drop US II support from wheezy since we won't have hardware to test issues on. Cheers, Martin -- Martin Zobel-Helas | Debian Syste

Re: sparc qualification for Wheezy

e issues did *not* show up. Especially USIII liked to be a problem child > as > the specs were never released by sun. It got better with USIV again... So some > state like 'not officially supported, but should just work' is probably the > best > for USII. if tha

Re: On the (ab)use of the Urgency field

How would this work? Will you modify the script to look for such cases? britney can set a flag called "age-days X", which means that the page needs to be at least X days old in unstable before it may migrate into testing (with a bit of more magic...). At least it was like this when

Re: Request unblock for aiccu 20070115-15.1

ation > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=670971 > > Please consider this packages for Wheezy, thanks. As usual sponsor for Reinier, i ACK this request. Cheers, Martin -- Martin Zobel-Helas | Debian System Administrator Debian & GNU/Linux Developer |

DSA concerns for jessie architectures

with proposals regarding the hardware Debian should buy. We encourage the porter community to actively assist DSA with the resolution of the above noted concerns regarding various ports. Thanks, Martin Zobel-Helas Debian System Administration Team -- "It pays to be obvious, especially if you h

Re: Bits from the release team (freeze time line)

liably but are probably not replacable if > one > dies. They could use more memory and it'd be helpful if they booted from SATA > (so that we can source new disks if/when the current PATA disks die). also, ball and rem currently sit in a a 4U case, which occupies (togeth

Bug#736168: pu: package samhain/2.8.3a-1

uploaded, before the point release? Once i see the package in p-u, i am willing to install it on some project machines, so we can test it. It might take until the weekend, though. Martin -- Martin Zobel-Helas Debian System Administrator Debian & GNU/Linux Devel

Preparation of the next stable Debian GNU/Linux update

Preparation of Debian GNU/Linux 4.0r1 = An up-to-date version is at . We are preparing the next revision of the current stable Debian distribution (sarge) and will frequently send reports so people can actually comme

Preparation of the next stable Debian GNU/Linux update

Preparation of Debian GNU/Linux 4.0r1 = An up-to-date version is at . We are preparing the next revision of the current stable Debian distribution (etch) and will frequently send reports so people can actually commen

<    1   2   3