Re: Fwd: tzdata-2011d in volatile
On Tue, Mar 22, 2011 at 01:26:41PM +0100, Philipp Kern wrote: Dear Glibc maintainers, Hi, we just received the following request for 2011d in lenny-volatile and squeeze-updates. Could you prepare the uploads? I should have a bit of time tonight to work on that, unless Clint does it before. I have already something ready (but currently a too bad connection to do something else than mail). However I have to say I am a bit lost with volatile, updates and so on. If I understand correctly, we should have a new version in lenny-volatile and squeeze-updates, and in fine also in lenny and squeeze. What are the required uploads to reach this state, which suites to target and in which case should I include a .orig.tar.gz with the upload? Thanks for your help. Cheers, Aurelien Thanks Philipp Kern Return-path: bounce-debian-volatile=phil+debian=philkern...@lists.debian.org Envelope-to: pkern+deb...@thrall.0x539.de Delivery-date: Tue, 22 Mar 2011 12:42:08 +0100 Received: from localhost ([127.0.0.1]) by thrall.0x539.de with esmtp (Exim 4.72) (envelope-from bounce-debian-volatile=phil+debian=philkern...@lists.debian.org) id 1Q1zyS-0006Z3-DI for pkern+deb...@thrall.0x539.de; Tue, 22 Mar 2011 12:42:08 +0100 X-Spam-Flag: NO X-Spam-Score: -4.099 X-Spam-Level: X-Spam-Status: No, score=-4.099 tagged_above=-99 required=5.31 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, DKIM_SIGNED=0.1, RCVD_IN_DNSWL_MED=-2.3, T_DKIM_INVALID=0.01, T_RP_MATCHES_RCVD=-0.01] autolearn=ham Authentication-Results: thrall.0x539.de (amavisd-new); dkim=softfail (fail, body has been altered) header.i=@gmail.com Authentication-Results: thrall.0x539.de (amavisd-new); domainkeys=softfail (fail, message has been altered) header.from=gokden...@gmail.com Received: from thrall.0x539.de ([127.0.0.1]) by localhost (thrall.0x539.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sN5mqUpVpJSZ for pkern+deb...@thrall.0x539.de; Tue, 22 Mar 2011 12:42:07 +0100 (CET) Received: from tanaris.0x539.de ([2a01:4f8:121:3a3::4e2e:6774]) by thrall.0x539.de with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.72) (envelope-from bounce-debian-volatile=phil+debian=philkern...@lists.debian.org) id 1Q1zyR-0006Yx-Ob for pkern+deb...@thrall.0x539.de; Tue, 22 Mar 2011 12:42:07 +0100 Received: from liszt.debian.org ([82.195.75.100]) by tanaris.0x539.de with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.69) (envelope-from bounce-debian-volatile=phil+debian=philkern...@lists.debian.org) id 1Q1zyU-00050I-2o for phil+deb...@philkern.de; Tue, 22 Mar 2011 12:42:10 +0100 Received: from localhost (localhost [127.0.0.1]) by liszt.debian.org (Postfix) with QMQP id 1DC7F13A5527; Tue, 22 Mar 2011 11:42:08 + (UTC) Old-Return-Path: gokden...@gmail.com X-Original-To: lists-debian-volat...@liszt.debian.org Delivered-To: lists-debian-volat...@liszt.debian.org Received: from localhost (localhost [127.0.0.1]) by liszt.debian.org (Postfix) with ESMTP id E60BA13A4F82 for lists-debian-volat...@liszt.debian.org; Tue, 22 Mar 2011 11:25:34 + (UTC) X-Virus-Scanned: at lists.debian.org with policy bank en-lt X-Amavis-Spam-Status: No, score=-3 tagged_above=-1 required=5.3 tests=[BAYES_00=-2, RCVD_IN_DNSWL_LOW=-1] autolearn=no Received: from liszt.debian.org ([127.0.0.1]) by localhost (lists.debian.org [127.0.0.1]) (amavisd-new, port 2525) with ESMTP id sdCpZ23bJ7fb for lists-debian-volat...@liszt.debian.org; Tue, 22 Mar 2011 11:25:27 + (UTC) X-policyd-weight: using cached result; rate: -6.9 Received: from mail-bw0-f47.google.com (mail-bw0-f47.google.com [209.85.214.47]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN smtp.gmail.com, Issuer Google Internet Authority (not verified)) by liszt.debian.org (Postfix) with ESMTPS id D1EB813A47C1 for debian-volat...@lists.debian.org; Tue, 22 Mar 2011 11:25:18 + (UTC) Received: by bwz10 with SMTP id 10so5535434bwz.6 for debian-volat...@lists.debian.org; Tue, 22 Mar 2011 04:25:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:user-agent:mime-version:to :subject:content-type:content-transfer-encoding; bh=a1rM3dTlByslQ/K+zLhxPHPrUwTiYK/oV7rrBZz8mWo=; b=JzhMPa/OK0HRhuRkU//7Dcwr0SuOk73jRW5ql1Qe9dEZW9LGTz+q02CuBXaK7PZKo5 dvOMsVkLhGtikbKgAg76Li3ZBSAkMj1Y8JiyYfZh5MAky5CdaZDTK2cKmpEVWp+/uD74 yFgpbiI+udZAf9k77gc+QHhrb2SATc89ClsP8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding;
Re: Fwd: tzdata-2011d in volatile
On Wed, 2011-03-23 at 19:31 +0100, Aurelien Jarno wrote: On Tue, Mar 22, 2011 at 01:26:41PM +0100, Philipp Kern wrote: we just received the following request for 2011d in lenny-volatile and squeeze-updates. Could you prepare the uploads? I should have a bit of time tonight to work on that, unless Clint does it before. I have already something ready (but currently a too bad connection to do something else than mail). Thanks. However I have to say I am a bit lost with volatile, updates and so on. If I understand correctly, we should have a new version in lenny-volatile and squeeze-updates, and in fine also in lenny and squeeze. What are the required uploads to reach this state, which suites to target and in which case should I include a .orig.tar.gz with the upload? Taking the easy one first :-) volatile Target either lenny-volatile or oldstable; the latter means you can re-use the upload for ftp-master. This should include the .orig.tar.gz ftp-master == lenny: Target lenny or oldstable. squeeze: Target squeeze or stable; SRM will then add it to squeeze-updates. As a general rule, when you're uploading the same upstream version to multiple distributions at the same time only one of them should include the .orig.tar.gz; otherwise queued on ftp-master will helpfully silently delete the second and subsequent uploads before they even reach dak. In this case I'd suggest including the .orig.tar.gz in the lenny upload, so that you can simply re-upload that to volatile. As an added note to the above, same time is potentially a period lasting several days. If, for example, you'd uploaded the unstable package yesterday, the .orig.tar.gz would still be visible on http://incoming.debian.org/ and should not be included. In summary for this upload: - volatile - lenny-volatile or oldstable, include .orig - lenny - lenny or oldstable, include .orig - squeeze - squeeze or stable, don't include .orig Hope that helped. Regards, Adam -- To UNSUBSCRIBE, email to debian-glibc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1300910099.8249.160.ca...@hathi.jungle.funky-badger.org
Re: Fwd: tzdata-2011d in volatile
On Wed, Mar 23, 2011 at 07:54:59PM +, Adam D. Barratt wrote: On Wed, 2011-03-23 at 19:31 +0100, Aurelien Jarno wrote: On Tue, Mar 22, 2011 at 01:26:41PM +0100, Philipp Kern wrote: we just received the following request for 2011d in lenny-volatile and squeeze-updates. Could you prepare the uploads? I should have a bit of time tonight to work on that, unless Clint does it before. I have already something ready (but currently a too bad connection to do something else than mail). Thanks. However I have to say I am a bit lost with volatile, updates and so on. If I understand correctly, we should have a new version in lenny-volatile and squeeze-updates, and in fine also in lenny and squeeze. What are the required uploads to reach this state, which suites to target and in which case should I include a .orig.tar.gz with the upload? Taking the easy one first :-) volatile Target either lenny-volatile or oldstable; the latter means you can re-use the upload for ftp-master. This should include the .orig.tar.gz ftp-master == lenny: Target lenny or oldstable. squeeze: Target squeeze or stable; SRM will then add it to squeeze-updates. As a general rule, when you're uploading the same upstream version to multiple distributions at the same time only one of them should include the .orig.tar.gz; otherwise queued on ftp-master will helpfully silently delete the second and subsequent uploads before they even reach dak. In this case I'd suggest including the .orig.tar.gz in the lenny upload, so that you can simply re-upload that to volatile. As an added note to the above, same time is potentially a period lasting several days. If, for example, you'd uploaded the unstable package yesterday, the .orig.tar.gz would still be visible on http://incoming.debian.org/ and should not be included. In summary for this upload: - volatile - lenny-volatile or oldstable, include .orig - lenny - lenny or oldstable, include .orig - squeeze - squeeze or stable, don't include .orig Hope that helped. Thanks a lot for the clear explanations, it something I'll keep preciously for the next uploads. I have uploaded tzdata 2011d to volatile, lenny and squeeze, I hope everything will be fine. Aurelien -- Aurelien Jarno GPG: 1024D/F1BCDB73 aurel...@aurel32.net http://www.aurel32.net -- To UNSUBSCRIBE, email to debian-glibc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110323224411.ga8...@hall.aurel32.net
Fwd: tzdata-2011d in volatile
Dear Glibc maintainers, we just received the following request for 2011d in lenny-volatile and squeeze-updates. Could you prepare the uploads? Thanks Philipp Kern ---BeginMessage--- Hi, tzdata-2011d includes an update to Turkish daylight saving time change. The day the DST is applied was postponed for one day, from Mar 27th, to Mar 28th 2011. Further information is available at posts: http://article.gmane.org/gmane.comp.time.tz/3658 http://article.gmane.org/gmane.comp.time.tz/3662 Can you publish tzdata-2011d-1 package for lenny and squeeze ? -- Gökdeniz Karadağ -- To UNSUBSCRIBE, email to debian-volatile-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4d888717.5000...@gmail.com ---End Message--- signature.asc Description: Digital signature
