[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: r1-NON-US in r2 dir?



It's long finished :) Figuring out how to do it faster would have taken me
more time ;).

-- 
I dedicate my life to life

On Wed, 7 Jan 2004, Mark Syms wrote:

> Don't forget that you can use the existing ISO as a source of packages
> by mounting it as a loopback filesystem. This may save you some download
> time.
> 
> On Tue, 2004-01-06 at 23:25, Bart Schouten wrote:
> > Thank you.
> > 
> > The output was:
> > 
> > [Jigdo]
> > Version=1.1
> > Generator=jigdo-file/0.6.8
> > 
> > [Image]
> > Filename=debian-30r1-i386-binary-1_NONUS.iso
> > Template=http://us.cdimage.debian.org/jigdo-area/3.0_r1/jigdo/i386/woody-i386-1_NONUS.template
> > Template-MD5Sum=--2ZBbMUi2Uw5NYh-hqeOw
> > ShortInfo='Debian GNU/Linux 3.0 r1 "Woody" - Official i386 Binary-1_NONUS 
> > CD'
> > Info='Generated on Thu, 19 Dec 2002 00:33:19 +0000'
> > 
> > 
> > So it was an r1 jigdo file. That explains.
> > Also, in reply to Steve McIntyre, the md5sum is that of the r1 iso.
> > 
> > I will try to download it again.
> > 
> > Greetz, 
> > 
> > bart
> > -- 
> > I dedicate my life to life
> > 
> > On Tue, 6 Jan 2004, George Danchev wrote:
> > 
> > > On Tuesday 06 January 2004 20:14, xen@rotmail.nl wrote:
> > > > Hi,
> > > >
> > > > I just used jigdo to download
> > > > http://non-us.cdimage.debian.org/jigdo-area/3.0_r2/jigdo/i386/woody-i386-1_
> > > >NONUS.jigdo which is as you can see in the 3.0_r2 directory, but the
> > > > resulting file was  debian-30r1-i386-binary-1_NONUS.iso
> > > >
> > > > What have I downloaded, exactly? (Or how can I find out?).
> > > 
> > > # zless woody-i386-1_NONUS.jigdo
> > > 
> > > and take a look at section [Image]
> > > Filename= ......
> > > ....
> > > I downloaded this http://non-us.cdimage.debian.org/jigdo-area/3.0_r2/jigdo/
> > > i386/woody-i386-1_NONUS.jigdo  and the filename is:
> > > 
> > > Filename=debian-30r2-i386-binary-1_NONUS.iso
> > > 
> > > btw, the Template= should be done as Relative, not as an Absolute Path... but 
> > > this is not related to your issue.
> > > 
> > > 
> > 
> > 
> > 
> > 
> 



Reply to: