Re: jigdo: how to keep an iso up to date?

[Richard Atterer]

On Sun, Aug 11, 2002 at 11:08:53PM +0200, Arjen Verweij wrote:
> it should be possible to keep iso images up to date using jigdo as
> well. My question is, how to go about this. I can't find any
> documentation that describes this, but maybe I am overlooking
> something?

This is nicely described in the jigdo HOWTO, see
.

Cheers,

  Richard

-- 
  __   _
  |_) /|  Richard Atterer |  CS student at the Technische  |  GnuPG key:
  | \/¯|  http://atterer.net  |  Universität München, Germany  |  0x888354F7
  ¯ '` ¯


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: jigdo: how to keep an iso up to date?

[Arjen Verweij]

Ahh. I see. No idea what happened I have read the mini-howto, but it must 
have been too swift. My apologies. I had attempted in
windows to update my image, because my HD on my
router is too small. At first it didn't work, it scanned the entire image
and said it had found 0 files. 

The howto presented a vital clue, stating you have to mount it as a
loopback device. I have no idea what that is, but I knew I hadn't mounted
the iso. So I tried again using Daemon-Tools (another quality piece of
German software ;) ) and it worked like a charm.

I know mentioning "that other OS" on a list like this is like blasphemy in
a church, but maybe other M$ jigdo users can benefit from it. Of course
you can share the iso over samba then mount the iso from the share in
Linux but I don't like scanning 650MB of data over 10Mbit BNC =)

Thank you for your swift replies.

Best regards,

Arjen Verweij


On Sun, 11 Aug 2002, wickedsun wrote:

> This is my first post on this list, so hi everybody.
> 
> It took me a while to figure it out too, the documentation is not giving
> much attention to it, but there is some info on the jigdo site (See the FAQ)
> 
> 
> You have to redownload the template everytime you want to update your image,
> mount your CD image and make jigdo look for packages installed on it.
> 
> After it is done scanning the CD (or image), it will download the packages
> that have been updated.
> 
> You have to remember to delete the .template and the .jigdo before you try
> to update. If you dont, the program will automatically use those files
> instead of downloading the new ones.
> 
> I hope this helps!
> 
> Charles

On Sun, 11 Aug 2002, Richard Atterer wrote:

> This is nicely described in the jigdo HOWTO, see
> .
>
> Cheers,
>
>  Richard


> 
> ---Original Message---
> From: Arjen Verweij
> Date: Sunday, August 11, 2002 17:36:57
> To: [EMAIL PROTECTED]
> Subject: jigdo: how to keep an iso up to date?
> Hi,
> 
> I have managed to dload the NON-US iso image for Debian 3.0 on my
> sturdy 80kbit/s link using jigdo. According to the website of Richard
> Atterer it should be possible to keep iso images up to date using jigdo as
> well. My question is, how to go about this. I can't find any documentation
> that describes this, but maybe I am overlooking something?
> 
> Maybe one of you knows the answer.
> 
> Best regards,
> 
> Sphere.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: sarge CDs

[Philip Hands]

On Thu, 2002-08-08 at 08:26, Anthony Towns wrote:
> On Wed, Aug 07, 2002 at 12:30:34PM +0100, Philip Hands wrote:
> > OK -- I'll sort out an automated thing for sarge on open, just as soon
> > as I've got my act together and worked out what went wrong with half the
> > DVDs for woody.
> 
> Hrm? I thought we were going to move to raff for the extra speed and
> space? (Since we were going to do this months ago, I'd rather avoid
> putting that move off too much further...)

Well, it might be nice, but how can I do non-US CDs on raff?

Even if I don't publish the non-US CDs, I'd need a non-US mirror so that
I could make the CD1's, which presumably has the potential to involve
the people who run raff in patent or DMCA issues.

> > Presumably, the new CDs should use the debian-installer floppies, as
> > mentioned by Tollef.
> 
> If they're ready; it'd be better to have unbootable CDs up sooner than
> d-i CDs later.

OK.

Cheers, Phil.
-- 
Say no to software patents!  http://petition.eurolinux.org/

|)|  Philip Hands [+44 (0)20 8530 9560]http://www.hands.com/
|-|  HANDS.COM Ltd.http://www.uk.debian.org/
|(|  10 Onslow Gardens, South Woodford, London  E18 1NE  ENGLAND



signature.asc
Description: This is a digitally signed message part

Re: don't match checksum in template data

[Nelson Suniaga]

On Sat, 2002-08-10 at 13:03, Richard Atterer wrote: 
Hello Nelson,

I'm not sure about the source of the problem - you are the 
first
person to report something like that. What version of 
jigdo-lite are
you using, and on what kernel?
Sorry for the lack of information 8-) 
the Jigdo version is the last: 0.6.8 I'm using for now 
Debian Woody Unstable, dated April 15, 2002 using now the 
kernel 2.4.18-k7 (got a AMD Athlon 950) 
the date for all the dics (and .raw files) that I have 
it's not the same: 
1. 15-04-2002 
2. 29-03-2002 
3. 29-04-2002 
4. idem 
5. idem 
6. idem 
7. idem 
8. 15-04-2002 

how do you figure out it, APT has a lot of files holded. 
On Fri, Aug 09, 2002 at 08:36:41PM -0400, Nelson Suniaga 
 wrote:
> Yes, I got a .iso.tmp image (why still it has a .tmp > extension?),

Because it isn't finished yet. Once all the data has been 
written to
it, it is renamed to just ".iso".

> `/mnt/iso/pool/main/g/gnome-libs/libgnome32_1.4.1.4-3_i386.deb'
> does not match checksum in template data

That is weird. It means that when jigdo read in that .deb 
for the
first time to find out its checksum, the checksum matched, 
but when it
later wanted to write the .deb to the .iso.tmp file, the 
checksum no
longer matched.
Exactly! that's very strange, it's just like someone o 
some thing change the numbers inside the file after the 
process reading. 

> Really I can't get it, can someone explain me this? ah...! almost I
> forget it: all those files with wrong checksums are differents
> everytime that I run jigdo-lite...

Very strange indeed. Are you sure the CD/harddisc 
containing /mnt/iso
does not have read errors?
my hard disc it's some old (Samsung with 6 GB) but anyway, 
how I can know if my disc it's possesed with bad spirits 
or bad sectors? I did it a resizing to the partitions, 
cause it didn't has enough space for the iso image... the 
image it must will be created on /opt/tmp 
Filesystem   1k-blocks  Used Available Use% 
Mounted on /dev/hda5  2583624   2062476 
   468620  82% / /dev/hda6   514144388736 
   114968  78% /home /dev/hda7  1391380 
   654852722392  48% /opt /dev/hda1 
 1627368   1503172124196  93% /win 
what do you think about it? 
Ah...! almost forget it: 128MB on RAM. 
> and other thing: if I run jigdo-lite like a "normal user" the
> .iso.tmp image is not generated completely (only 13 MB) but if I am
> root then I get a file of 678 MB

"Interesting." :-/

> This happen also with the US jigdo and template files, just the
> message it's different:
> > Not downloading .template file - `woody-i386-1.template' > already present

This message means that the template data matches the 
checksum that is
listed in the .jigdo file...

> Found 375 of the 1352 files required by the
> template
> zstream.cc:282: Assertion failed, `dataUnc > 0 || (status > ==
> Z_STREAM_END || status == Z_OK)'

...but this indicates that the template data is corrupted.

I cannot imagine how this could possibly be a bug in jigdo 
- it may be
bad RAM, a broken HD... :-|

> Question 1 : I must or not use that image?

Whether you need CD 1 or CD 1_NONUS is your decision. Our
recommendation to end users is to use 1_NONUS. jigdo 
should be able to
download both.
Yeah, I can understand that, Jigdo download both, but none 
it's totally created. 
> Question 2 : What happen with the DEBs with wrong md5sum after of
> the installation???

As long as there are .debs with wrong md5sums, the 
.iso.tmp will never
be finished; if you burn the .iso.tmp file instead of a 
final .iso
file to CD-R, then the installation will break in weird 
and wonderful
ways.

Sorry, I cannot really help you!
Cheers,

   Richard
Well... maybe the answer would be to wait another release 
of Jigdo (0.7.0 perhaps...? 8-) 
Anyway, thanks so much for all, now I know that it's not 
me, it's other thing... it's something unknown  8-) 

-- 
   __   _
   |_) /|  Richard Atterer |  CS student at the 
Technische  |  GnuPG key:
   | \/¯|  http://atterer.net  |  Universität München, 
Germany  |  0x888354F7
   ¯ '` ¯

-- 
To UNSUBSCRIBE, email to 
[EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact 
[EMAIL PROTECTED]


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]