Re: Stable 6.0.2.1 images broken?
- To: shirish शिरीष <shirishag75@gmail.com>
- Cc: debian-cd@lists.debian.org
- Subject: Re: Stable 6.0.2.1 images broken?
- From: Steve McIntyre <steve@einval.com>
- Date: Fri, 1 Jul 2011 01:05:33 +0100
- Message-id: <[🔎] 20110701000532.GA32014@einval.com>
- In-reply-to: <BANLkTikL5CDJ0+3MV-5dV4SQ+tkrEaw-pg@mail.gmail.com>
- References: <20110628191310.GA11652@tiikeri.vuoristo.local> <BANLkTi=N7Cb0Zgo65UjXMOCjLmPsbns1KA@mail.gmail.com> <20110628220547.GW32014@einval.com> <BANLkTikL5CDJ0+3MV-5dV4SQ+tkrEaw-pg@mail.gmail.com>
On Fri, Jul 01, 2011 at 12:57:17AM +0530, shirish शिरीष wrote:
>In-line :-
>
>2011/6/29 Steve McIntyre <steve@einval.com>:
>> On Wed, Jun 29, 2011 at 02:32:49AM +0530, shirish शिरीष wrote:
>>>
>>>I don't think so. I downloaded the DVD image via jigdo and I had the
>>>older one downloaded through jigdo as well .
>>>
>>>The only difference between this image and the last image is of 314
>>>files (amd64 arch) . If it was wheezy, I would assume that the
>>>difference between files would have been much larger. I am not sure
>>>though why its 314 files, they said 150/160 odd packages being
>>>changed. I do know that sometimes some meta-package may have 3
>>>individual packages, some binary, some binary-common and some
>>>binary-data, maybe that's the change. Also maybe the changes they had
>>>said may just be in main and not of other archives (contrib and
>>>non-free) where the package change policies may be more relaxing.
>>
>> The number (150/160) will be the number of source packages
>> updated. The number you're seeing and reporting will be the number of
>> binary packages. By my count, across all architectures and source
>> there were 8109 updated files in the pool. That's counting the files
>> in the diff that I use for generating the update CDs/DVDs.
>
>Dear Steve,
> First of all thank you for your quick and articulate reply. The
>geek/curious in me likes to know such things ;)
:-) Happy to oblige...
>Another thing to note is I removed the CC to other lists as my reply
>might just be additional noise which they might not be interested in.
Cool.
>>>One has to keep in mind, that this has made sure that the weekly
>>>images aren't there on time. See for instance
>>>http://cdimage.debian.org/cdimage/weekly-builds/amd64/jigdo-dvd/
>>>
>>>The last image is still reflecting the one done on 20th June ,
>>
>> Correct. When I'm working on a (point) release, I disable the daily
>> and weekly builds so as not to cause confusion or congestion on the
>> build machine.
>
>umm..... when can we expect the weekly builds to be back on ?
They'll happen again automatically next Monday morning (i.e. as
normal); the cron job was re-enabled once the release was out.
--
Steve McIntyre, Cambridge, UK. steve@einval.com
There's no sensation to compare with this
Suspended animation, A state of bliss
Reply to: