Re: Dealing better with CD releases
Thilo Six wrote the following on 15.04.2009 22:20
> Mattias Wadenstein wrote the following on 15.04.2009 19:18
>
>> On Wed, 15 Apr 2009, Luk Claes wrote:
>>
>>> Steve McIntyre wrote:
>>>> Hi folks,
>>>>
>>>> At the moment we have problems when we do releases including new
>>>> CD/DVD images, as you'll see from mailing list complaints about broken
>>>> links each time. Simon Paillard and I had some discussion about this
>>>> today on #debian-www and I've come up with a workflow that will
>>>> improve things, I think (see 2c below). Please feel free to point out
>>>> what I've missed... :-)
>>>>
>>>> 1. The Problem
>>>>
>>>> We generate new CDs and DVDs for each point release. These are
>>>> published in the release area of cdimage.debian.org[1]. The image
>>>> filenames and the top-level directory are versioned for clarity, and
>>>> we add a "current" symlink in the debian-cd directory that points to
>>> ^^^^^^^
>>>> the most recent version. We move old trees of images into the archive
>>>> area[2] as each new build is published, We then prune most of the old
>>>> ISO images so we don't waste too much space - older images can be
>>>> recreated in the future using jigdo if necessary.
>>>> d. Other ideas?
>>> Can't we link to the 'current' images on the webpages?
>> Then you can link to the directory with isos for a particular arch and
>> type: http://cdimage.debian.org/debian-cd/current/amd64/iso-cd/
>>
>> But not to an actual iso, due to the version number being included there:
>>
>> http://cdimage.debian.org/debian-cd/current/amd64/iso-cd/debian-501-amd64-CD-1.iso
>>
>> /Mattias Wadenstein
>>
>>
> How about a directory with links to current isos dricetly then?
>
> current $ ls -l
> total 0
> lrwxrwxrwx 1 USER USER 37 2009-04-15 22:18 current-stable-ARCH-1.iso ->
> ../ARCH/ISO/debian-501-amd64-CD-1.iso
> lrwxrwxrwx 1 USER USER 37 2009-04-15 22:18 current-stable-ARCH-2.iso ->
> ../ARCH/ISO/debian-501-amd64-CD-2.iso
>
>
But that approach obviously puts some more work on you Steve as you would
have to rebuild the files:
MD5SUMS
MD5SUMS.sign
SHA1SUMS
SHA1SUMS.sign
with the appropriate file names i guess. Maybe in that same directory.
--
bye Thilo
key: 0x4A411E09
Reply to: