Re: 3.0r1 iso images ready for testing
Hi Soren, sorry to hear you've been having problems downloading Debian. On Sat, Feb 22, 2003 at 02:59:15PM -0500, Soren Andersen wrote: Debian Stable (3.0, Woody) CDs -- running Jigdo for Windows32 on my Winbox and then burning the CDs. I got as far as CD #3 before the tedium halted that. Also the realization that I was storing obsoleted packages at considerable expenditure of time and effort. 3.0r1 isn't exactly obsoleted! There was a problem by the time 2.2r7 was released, because /that/ release included software that was 1.5 years old... In general, Debian prefers stability over cutting-edge features, at least for stable. Oh, I see that below you sound like you can't find 3.0r1, just 3.0r0. message through and get an answer. Sorry for asking someone to privately CC: me an answer, but, please CC: to somian -AT- pobox -DOT- com. I'll BCC you. BTW, there are services out there which offer you a forwarding email address which expires after a few days. My experience of trying to understand how the PTB at Debian want CD iso's distributed was not very easy. What's a PTB? People that brag? Am I one? :) I like and admire Jigdo, great concept, but what left me frustrated was trying to understand how I could create iso's that contain the *updated* Woody .deb's, not the original release (3.0) .debs. Hm, all you have to do is point your browser at http://www.debian.org/CD/jigdo-cd/index.en.html#which, follow the USA or Europe link which points to jigdo files for 3.0r1, and then pass the URLs of the i386 .jigdo files to jigdo-lite. It would have been just dandy if the author(s) of the somewhat scanty documentation jigdo's own docs are a bit lacking, yes. But fortunately, I've got the jigdo HOWTO as an excuse for that fact; have you looked at http://www.dirac.org/linux/debian/jigdo/ - surely that isn't scanty? had just assumed anyone needing to burn iso's of Debian-Stable is going to want 3.0r1 [or whatever is most recent], not 3.0. But that's not how the instructions seem to have been written. There's big holes ... . So anyway, my question, at last, is: does this thread I have unearthed mean that now, there IS a URL at which I can point Jigdo to get it to, in one easy-to-understand pass, assemble (I think that's the correct term for what Jigdo does) a 3.0r1 .iso set ??? Yes, see above (except you'll have to re-run jigdo-lite for each CD, it can't do the whole set with just one invocation). I'm not sure why you cannot find the information via the website - or is there another problem which prevents you from using these .jigdo files? Anyway, if you can give any suggestions about what changes would improve the website, I'm happy to hear them. I run Debian on a i-x86 platform and JUST need the binary .debs for that architecture (and the sources too, please ...), not the .debs for 15 other architectures as well, ?!? Sure, if you don't want non-i386, then just don't pass the non-i386 .jigdo files to jigdo-lite! In case you've misunderstood this: jigdo-lite takes just one URL (that of the .jigdo file) plus URLs for the Debian/non-US mirrors and then does all the rest of the work itself. It will download the packages on the CD on its own, you don't need to do anything but lean back and wait. 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: 3.0r1 iso images ready for testing
On Sun, 23 Feb 2003 12:45:24 +0100, Richard Atterer
[EMAIL PROTECTED] said:
Hi Soren,
sorry to hear you've been having problems downloading Debian.
Thanks for the sympathy :-).
On Sat, Feb 22, 2003 at 02:59:15PM -0500, Soren Andersen wrote:
Debian Stable (3.0, Woody) CDs -- running Jigdo for Windows32 on my
Winbox and then burning the CDs. I got as far as CD #3 before the tedium
halted that. Also the realization that I was storing obsoleted packages
at considerable expenditure of time and effort.
3.0r1 isn't exactly obsoleted! There was a problem by the time 2.2r7 was
released, because /that/ release included software that was 1.5 years
old... In general, Debian prefers stability over cutting-edge features,
at least for stable.
Oh, I see that below you sound like you can't find 3.0r1, just 3.0r0.
Right. I'll note that I probably didn't do a good job explaining what I
had been having problems with. Since I got my laptop I've been through a
series of life struggles and disruptions to routine and waited so long to
ask for advice on this that I am probably bleary on some of the details
('twas back in early January when I installed and fired up Jigdo-lite to
burn my Debian CDs).
So to confirm: (1) You correctly seemed to have divined that I chose
Jigdo-lite (based as it is on MinGW, not Cygwin, it seemed the more
elegant solution ...) and (2) That it was 3.0r1 that I desired to
assemble as binary .debs for the ix86 architecture. I wasn't worried that
3.0r1 is obsolete, that was a muddle I probably caused for you readers
by confusing wording. I was concerned that *3.0r0* was already too out of
date.
I found myself unable to get a valid Jigdo-lite run trying to target
3.0r1. The exact trouble I had, I unfortunately cannot reconstruct from
memory right now -- it's been too long -- but it was a basic Jigdo
breakdown, i.e. the .jigdo file and the url I pointed towards didn't
match and Jigdo wouldn't do anything, or something like that. It seems to
me that no US Debian Jigdo mirror site existed for assembling 3.0r1 and
I ended up trying the only site that seems available worldwide for that,
I believe it is the one in the .hu country-hierarchy. Something about
that seemed weird to me.
My experience of trying to understand how the PTB at Debian want CD iso's
distributed was not very easy.
What's a PTB? People that brag? Am I one? :)
;-). Powers That Be. Yes, I suppose you are.
I like and admire Jigdo, great concept, but what left me frustrated was
trying to understand how I could create iso's that contain the *updated*
Woody .deb's, not the original release (3.0) .debs.
Hm, all you have to do is point your browser at
http://www.debian.org/CD/jigdo-cd/index.en.html#which, follow the USA
or Europe link which points to jigdo files for 3.0r1, and then pass the URLs
of the i386 .jigdo files to jigdo-lite.
I spent a really long time (3+ hours) reading the Jigdo HOWTO and Jigdo's
own documentation, and reading the Debian.org site that lists URLs, and
yet could not figure out what the URLs were for 3.0r1. Mostly I just
remember the frustration, and going back and forth between a couple of
different Debian.org URLs trying to find some missing link-ish
explanation of something that I just wasn't getting. 's been just too
long, I cannot provide a detailed accounting that would be helpful in
improving things, at this time (I'll have to repeat the whole effort at a
later time and see if I can re-create what led to these feelings of
frustration ;-).
[snip]
I run Debian on a i-x86 platform and JUST need the binary .debs for that
architecture (and the sources too, please ...), not the .debs for 15
other architectures as well,
?!? Sure, if you don't want non-i386, then just don't pass the non-i386
.jigdo files to jigdo-lite!
You are right, I got myself confused by the thread in question (in this
List archive, that I was perusing) and by later efforts I've been making
to create a local 'mirror' of Debian packages via a different means.
Unfairly blamed Jigdo for misbehaving where it has not. Sorry.
In case you've misunderstood this: jigdo-lite takes just one URL (that of
the .jigdo file) plus URLs for the Debian/non-US mirrors and then does
all the rest of the work itself. It will download the packages on the CD
on its own, you don't need to do anything but lean back and wait.
Yes, I misremembered a good part of it, but this is basically what I
finally managed to achieve, for the first 3 CDs. It's just that when I
went to run 'apt' I realized that the CDs I had just burned were already
behind even what was currently installed on my system (configured for me
by a system vendor, i.e., the outfit that sold me the laptop with
GNU-Linux pre-installed), for some packages (pkgs that have been released
in newer revisions since 3.0r0). I had tried to get 3.0r1 but had
somehow ended up with 3.0r0 instead. At least I think so...
I received another message in reply, that
Re: 3.0r1 iso images ready for testing
On Sun, Feb 23, 2003 at 05:11:28PM -0500, Soren Andersen wrote: current today as I write this), the .jigdo file URL that I want to point Jigdo-lite at is: http://us.cdimage.debian.org/jigdo-area/3.0_r1/jigdo/source/debian-update-3.0r1-src.jigdo *if what I wanted was the SOURCES for 3.0r1 -- is this correct?* It depends - the *update* CDs only contain the differences between r0 and r1, not the whole distribution, see http://www.debian.org/CD/faq/#update-cd. But based on what you wrote previously, the update CDs may be the right thing for you. 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: 3.0r1 iso images ready for testing
On Saturday 22 February 2003 07:28 pm, Paul E Condon wrote: Greg Madden wrote: On Saturday 22 February 2003 10:59 am, Soren Andersen wrote: Hello, snip My experience of trying to understand how the PTB at Debian want CD iso's distributed was not very easy. I like and admire Jigdo, great concept, but what left me frustrated was trying to understand how I could create iso's that contain the *updated* Woody .deb's, not the original release (3.0) .debs. It would have been just dandy if the author(s) of the somewhat scanty documentation had just assumed anyone needing to burn iso's of Debian-Stable is going to want 3.0r1 [or whatever is most recent], not 3.0. But that's not how the instructions seem to have been written. There's big holes ... . So anyway, my question, at last, is: does this thread I have unearthed mean that now, there IS a URL at which I can point Jigdo to get it to, in one easy-to-understand pass, assemble (I think that's the correct term for what Jigdo does) a 3.0r1 .iso set ??? A good starting point is http://www.debian.org, and if you follow the links you will find 'list archives' , 'cd iso imagesjigdo' 'Documentation'. i.e. http://www.debian.org/CD/jigdo-cd/ I search for the string 'update' using the 'search this page' function in mozilla. I find one (1) hit: 'updated'. It is in the FAQ AArgh... and has nothing to do with 3.0r1. Where should I really look? Or for what string? Paul There is an 'update' cd image for those not wanting to build a new set of cdroms. snip http://us.cdimage.debian.org/jigdo-area/3.0_r1/jigdo/i386/ -- Greg Madden
Re: 3.0r1 iso images ready for testing
Hi Soren, sorry to hear you've been having problems downloading Debian. On Sat, Feb 22, 2003 at 02:59:15PM -0500, Soren Andersen wrote: Debian Stable (3.0, Woody) CDs -- running Jigdo for Windows32 on my Winbox and then burning the CDs. I got as far as CD #3 before the tedium halted that. Also the realization that I was storing obsoleted packages at considerable expenditure of time and effort. 3.0r1 isn't exactly obsoleted! There was a problem by the time 2.2r7 was released, because /that/ release included software that was 1.5 years old... In general, Debian prefers stability over cutting-edge features, at least for stable. Oh, I see that below you sound like you can't find 3.0r1, just 3.0r0. message through and get an answer. Sorry for asking someone to privately CC: me an answer, but, please CC: to somian -AT- pobox -DOT- com. I'll BCC you. BTW, there are services out there which offer you a forwarding email address which expires after a few days. My experience of trying to understand how the PTB at Debian want CD iso's distributed was not very easy. What's a PTB? People that brag? Am I one? :) I like and admire Jigdo, great concept, but what left me frustrated was trying to understand how I could create iso's that contain the *updated* Woody .deb's, not the original release (3.0) .debs. Hm, all you have to do is point your browser at http://www.debian.org/CD/jigdo-cd/index.en.html#which, follow the USA or Europe link which points to jigdo files for 3.0r1, and then pass the URLs of the i386 .jigdo files to jigdo-lite. It would have been just dandy if the author(s) of the somewhat scanty documentation jigdo's own docs are a bit lacking, yes. But fortunately, I've got the jigdo HOWTO as an excuse for that fact; have you looked at http://www.dirac.org/linux/debian/jigdo/ - surely that isn't scanty? had just assumed anyone needing to burn iso's of Debian-Stable is going to want 3.0r1 [or whatever is most recent], not 3.0. But that's not how the instructions seem to have been written. There's big holes ... . So anyway, my question, at last, is: does this thread I have unearthed mean that now, there IS a URL at which I can point Jigdo to get it to, in one easy-to-understand pass, assemble (I think that's the correct term for what Jigdo does) a 3.0r1 .iso set ??? Yes, see above (except you'll have to re-run jigdo-lite for each CD, it can't do the whole set with just one invocation). I'm not sure why you cannot find the information via the website - or is there another problem which prevents you from using these .jigdo files? Anyway, if you can give any suggestions about what changes would improve the website, I'm happy to hear them. I run Debian on a i-x86 platform and JUST need the binary .debs for that architecture (and the sources too, please ...), not the .debs for 15 other architectures as well, ?!? Sure, if you don't want non-i386, then just don't pass the non-i386 .jigdo files to jigdo-lite! In case you've misunderstood this: jigdo-lite takes just one URL (that of the .jigdo file) plus URLs for the Debian/non-US mirrors and then does all the rest of the work itself. It will download the packages on the CD on its own, you don't need to do anything but lean back and wait. Cheers, Richard -- __ _ |_) /| Richard Atterer | CS student at the Technische | GnuPG key: | \/¯| http://atterer.net | Universität München, Germany | 0x888354F7 ¯ '` ¯
Re: 3.0r1 iso images ready for testing
On Sun, 23 Feb 2003 12:45:24 +0100, Richard Atterer
[EMAIL PROTECTED] said:
Hi Soren,
sorry to hear you've been having problems downloading Debian.
Thanks for the sympathy :-).
On Sat, Feb 22, 2003 at 02:59:15PM -0500, Soren Andersen wrote:
Debian Stable (3.0, Woody) CDs -- running Jigdo for Windows32 on my
Winbox and then burning the CDs. I got as far as CD #3 before the tedium
halted that. Also the realization that I was storing obsoleted packages
at considerable expenditure of time and effort.
3.0r1 isn't exactly obsoleted! There was a problem by the time 2.2r7 was
released, because /that/ release included software that was 1.5 years
old... In general, Debian prefers stability over cutting-edge features,
at least for stable.
Oh, I see that below you sound like you can't find 3.0r1, just 3.0r0.
Right. I'll note that I probably didn't do a good job explaining what I
had been having problems with. Since I got my laptop I've been through a
series of life struggles and disruptions to routine and waited so long to
ask for advice on this that I am probably bleary on some of the details
('twas back in early January when I installed and fired up Jigdo-lite to
burn my Debian CDs).
So to confirm: (1) You correctly seemed to have divined that I chose
Jigdo-lite (based as it is on MinGW, not Cygwin, it seemed the more
elegant solution ...) and (2) That it was 3.0r1 that I desired to
assemble as binary .debs for the ix86 architecture. I wasn't worried that
3.0r1 is obsolete, that was a muddle I probably caused for you readers
by confusing wording. I was concerned that *3.0r0* was already too out of
date.
I found myself unable to get a valid Jigdo-lite run trying to target
3.0r1. The exact trouble I had, I unfortunately cannot reconstruct from
memory right now -- it's been too long -- but it was a basic Jigdo
breakdown, i.e. the .jigdo file and the url I pointed towards didn't
match and Jigdo wouldn't do anything, or something like that. It seems to
me that no US Debian Jigdo mirror site existed for assembling 3.0r1 and
I ended up trying the only site that seems available worldwide for that,
I believe it is the one in the .hu country-hierarchy. Something about
that seemed weird to me.
My experience of trying to understand how the PTB at Debian want CD iso's
distributed was not very easy.
What's a PTB? People that brag? Am I one? :)
;-). Powers That Be. Yes, I suppose you are.
I like and admire Jigdo, great concept, but what left me frustrated was
trying to understand how I could create iso's that contain the *updated*
Woody .deb's, not the original release (3.0) .debs.
Hm, all you have to do is point your browser at
http://www.debian.org/CD/jigdo-cd/index.en.html#which, follow the USA
or Europe link which points to jigdo files for 3.0r1, and then pass the URLs
of the i386 .jigdo files to jigdo-lite.
I spent a really long time (3+ hours) reading the Jigdo HOWTO and Jigdo's
own documentation, and reading the Debian.org site that lists URLs, and
yet could not figure out what the URLs were for 3.0r1. Mostly I just
remember the frustration, and going back and forth between a couple of
different Debian.org URLs trying to find some missing link-ish
explanation of something that I just wasn't getting. 's been just too
long, I cannot provide a detailed accounting that would be helpful in
improving things, at this time (I'll have to repeat the whole effort at a
later time and see if I can re-create what led to these feelings of
frustration ;-).
[snip]
I run Debian on a i-x86 platform and JUST need the binary .debs for that
architecture (and the sources too, please ...), not the .debs for 15
other architectures as well,
?!? Sure, if you don't want non-i386, then just don't pass the non-i386
.jigdo files to jigdo-lite!
You are right, I got myself confused by the thread in question (in this
List archive, that I was perusing) and by later efforts I've been making
to create a local 'mirror' of Debian packages via a different means.
Unfairly blamed Jigdo for misbehaving where it has not. Sorry.
In case you've misunderstood this: jigdo-lite takes just one URL (that of
the .jigdo file) plus URLs for the Debian/non-US mirrors and then does
all the rest of the work itself. It will download the packages on the CD
on its own, you don't need to do anything but lean back and wait.
Yes, I misremembered a good part of it, but this is basically what I
finally managed to achieve, for the first 3 CDs. It's just that when I
went to run 'apt' I realized that the CDs I had just burned were already
behind even what was currently installed on my system (configured for me
by a system vendor, i.e., the outfit that sold me the laptop with
GNU-Linux pre-installed), for some packages (pkgs that have been released
in newer revisions since 3.0r0). I had tried to get 3.0r1 but had
somehow ended up with 3.0r0 instead. At least I think so...
I received another message in reply, that
Re: 3.0r1 iso images ready for testing
On Sun, Feb 23, 2003 at 05:11:28PM -0500, Soren Andersen wrote: current today as I write this), the .jigdo file URL that I want to point Jigdo-lite at is: http://us.cdimage.debian.org/jigdo-area/3.0_r1/jigdo/source/debian-update-3.0r1-src.jigdo *if what I wanted was the SOURCES for 3.0r1 -- is this correct?* It depends - the *update* CDs only contain the differences between r0 and r1, not the whole distribution, see http://www.debian.org/CD/faq/#update-cd. But based on what you wrote previously, the update CDs may be the right thing for you. Richard -- __ _ |_) /| Richard Atterer | CS student at the Technische | GnuPG key: | \/¯| http://atterer.net | Universität München, Germany | 0x888354F7 ¯ '` ¯
Re: 3.0r1 iso images ready for testing
Hello, To start with, sorry about possible multiple breaches of Netiquette, and any possible demanding, annoyed tone which may despite my best efforts, find it's way into this message. Searching for info on how to solve problems with GNU-Linux sometimes involves casting a very wide net and then just hoping for a lucky break. About 45 days ago I began for the first time using Jigdo to create some Debian Stable (3.0, Woody) CDs -- running Jigdo for Windows32 on my Winbox and then burning the CDs. I got as far as CD #3 before the tedium halted that. Also the realization that I was storing obsoleted packages at considerable expenditure of time and effort. Now I've just come across this thread using Goggle (the wide net) and so although I am not subscribed to this List, I am hoping I can get the message through and get an answer. Sorry for asking someone to privately CC: me an answer, but, please CC: to somian -AT- pobox -DOT- com. My experience of trying to understand how the PTB at Debian want CD iso's distributed was not very easy. I like and admire Jigdo, great concept, but what left me frustrated was trying to understand how I could create iso's that contain the *updated* Woody .deb's, not the original release (3.0) .debs. It would have been just dandy if the author(s) of the somewhat scanty documentation had just assumed anyone needing to burn iso's of Debian-Stable is going to want 3.0r1 [or whatever is most recent], not 3.0. But that's not how the instructions seem to have been written. There's big holes ... . So anyway, my question, at last, is: does this thread I have unearthed mean that now, there IS a URL at which I can point Jigdo to get it to, in one easy-to-understand pass, assemble (I think that's the correct term for what Jigdo does) a 3.0r1 .iso set ??? I'd even be willing to contribute to improved documentation on howto do this, if someone would answer, pointing me in the right direction or providing expanded explanation. TIA, Soren A P.S. It would be absolutely super if the PTB could keep someone like me in mind: new-ish Debian GNU-Linux user, not connected to the 'Net from his Debian box (because its a laptop w/ a non-working [yet] Winmodem [softmodem]), who needs to use MSWinblows as an intermediary between his new Debian installation and the Debian package repositories on the Network. I run Debian on a i-x86 platform and JUST need the binary .debs for that architecture (and the sources too, please ...), not the .debs for 15 other architectures as well, involving the running of Jigdo for like 3 consecutive weekends, hours of manually manipulating .iso files (to get them onto CD-Rs/CD-RWs), creating a 2-foot-high stack of CDs in the process, which then require a small moving van to lug from place to place... . -- In a democracy dissent is an act of faith. Like medicine, the test of its value is not in its taste, but in its effect. -- J. W. Fulbright -- http://www.fastmail.fm - A no graphics, no pop-ups email service -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: 3.0r1 iso images ready for testing
On Saturday 22 February 2003 10:59 am, Soren Andersen wrote: Hello, snip My experience of trying to understand how the PTB at Debian want CD iso's distributed was not very easy. I like and admire Jigdo, great concept, but what left me frustrated was trying to understand how I could create iso's that contain the *updated* Woody .deb's, not the original release (3.0) .debs. It would have been just dandy if the author(s) of the somewhat scanty documentation had just assumed anyone needing to burn iso's of Debian-Stable is going to want 3.0r1 [or whatever is most recent], not 3.0. But that's not how the instructions seem to have been written. There's big holes ... . So anyway, my question, at last, is: does this thread I have unearthed mean that now, there IS a URL at which I can point Jigdo to get it to, in one easy-to-understand pass, assemble (I think that's the correct term for what Jigdo does) a 3.0r1 .iso set ??? A good starting point is http://www.debian.org, and if you follow the links you will find 'list archives' , 'cd iso imagesjigdo' 'Documentation'. i.e. http://www.debian.org/CD/jigdo-cd/ There is an 'update' cd image for those not wanting to build a new set of cdroms. snip -- Greg Madden -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: 3.0r1 iso images ready for testing
Greg Madden wrote: On Saturday 22 February 2003 10:59 am, Soren Andersen wrote: Hello, snip My experience of trying to understand how the PTB at Debian want CD iso's distributed was not very easy. I like and admire Jigdo, great concept, but what left me frustrated was trying to understand how I could create iso's that contain the *updated* Woody .deb's, not the original release (3.0) .debs. It would have been just dandy if the author(s) of the somewhat scanty documentation had just assumed "anyone needing to burn iso's of Debian-Stable is going to want 3.0r1 [or whatever is most recent], not 3.0". But that's not how the instructions seem to have been written. There's big holes ... . So anyway, my question, at last, is: does this thread I have unearthed mean that now, there IS a URL at which I can point Jigdo to get it to, in one easy-to-understand pass, assemble (I think that's the correct term for what Jigdo does) a 3.0r1 .iso set ??? A good starting point is http://www.debian.org, and if you follow the links you will find 'list archives' , 'cd iso imagesjigdo' 'Documentation'. i.e. http://www.debian.org/CD/jigdo-cd/ I search for the string 'update' using the 'search this page' function in mozilla. I find one (1) hit: 'updated'. It is in the FAQ "AArgh..." and has nothing to do with 3.0r1. Where should I really look? Or for what string? Paul There is an 'update' cd image for those not wanting to build a new set of cdroms. snip
Re: 3.0r1 iso images ready for testing
On Saturday 22 February 2003 07:28 pm, Paul E Condon wrote: Greg Madden wrote: On Saturday 22 February 2003 10:59 am, Soren Andersen wrote: Hello, snip My experience of trying to understand how the PTB at Debian want CD iso's distributed was not very easy. I like and admire Jigdo, great concept, but what left me frustrated was trying to understand how I could create iso's that contain the *updated* Woody .deb's, not the original release (3.0) .debs. It would have been just dandy if the author(s) of the somewhat scanty documentation had just assumed anyone needing to burn iso's of Debian-Stable is going to want 3.0r1 [or whatever is most recent], not 3.0. But that's not how the instructions seem to have been written. There's big holes ... . So anyway, my question, at last, is: does this thread I have unearthed mean that now, there IS a URL at which I can point Jigdo to get it to, in one easy-to-understand pass, assemble (I think that's the correct term for what Jigdo does) a 3.0r1 .iso set ??? A good starting point is http://www.debian.org, and if you follow the links you will find 'list archives' , 'cd iso imagesjigdo' 'Documentation'. i.e. http://www.debian.org/CD/jigdo-cd/ I search for the string 'update' using the 'search this page' function in mozilla. I find one (1) hit: 'updated'. It is in the FAQ AArgh... and has nothing to do with 3.0r1. Where should I really look? Or for what string? Paul There is an 'update' cd image for those not wanting to build a new set of cdroms. snip http://us.cdimage.debian.org/jigdo-area/3.0_r1/jigdo/i386/ -- Greg Madden -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: 3.0r1 iso images ready for testing
Hello, To start with, sorry about possible multiple breaches of Netiquette, and any possible demanding, annoyed tone which may despite my best efforts, find it's way into this message. Searching for info on how to solve problems with GNU-Linux sometimes involves casting a very wide net and then just hoping for a lucky break. About 45 days ago I began for the first time using Jigdo to create some Debian Stable (3.0, Woody) CDs -- running Jigdo for Windows32 on my Winbox and then burning the CDs. I got as far as CD #3 before the tedium halted that. Also the realization that I was storing obsoleted packages at considerable expenditure of time and effort. Now I've just come across this thread using Goggle (the wide net) and so although I am not subscribed to this List, I am hoping I can get the message through and get an answer. Sorry for asking someone to privately CC: me an answer, but, please CC: to somian -AT- pobox -DOT- com. My experience of trying to understand how the PTB at Debian want CD iso's distributed was not very easy. I like and admire Jigdo, great concept, but what left me frustrated was trying to understand how I could create iso's that contain the *updated* Woody .deb's, not the original release (3.0) .debs. It would have been just dandy if the author(s) of the somewhat scanty documentation had just assumed anyone needing to burn iso's of Debian-Stable is going to want 3.0r1 [or whatever is most recent], not 3.0. But that's not how the instructions seem to have been written. There's big holes ... . So anyway, my question, at last, is: does this thread I have unearthed mean that now, there IS a URL at which I can point Jigdo to get it to, in one easy-to-understand pass, assemble (I think that's the correct term for what Jigdo does) a 3.0r1 .iso set ??? I'd even be willing to contribute to improved documentation on howto do this, if someone would answer, pointing me in the right direction or providing expanded explanation. TIA, Soren A P.S. It would be absolutely super if the PTB could keep someone like me in mind: new-ish Debian GNU-Linux user, not connected to the 'Net from his Debian box (because its a laptop w/ a non-working [yet] Winmodem [softmodem]), who needs to use MSWinblows as an intermediary between his new Debian installation and the Debian package repositories on the Network. I run Debian on a i-x86 platform and JUST need the binary .debs for that architecture (and the sources too, please ...), not the .debs for 15 other architectures as well, involving the running of Jigdo for like 3 consecutive weekends, hours of manually manipulating .iso files (to get them onto CD-Rs/CD-RWs), creating a 2-foot-high stack of CDs in the process, which then require a small moving van to lug from place to place... . -- In a democracy dissent is an act of faith. Like medicine, the test of its value is not in its taste, but in its effect. -- J. W. Fulbright -- http://www.fastmail.fm - A no graphics, no pop-ups email service
Re: 3.0r1 iso images ready for testing
On Saturday 22 February 2003 10:59 am, Soren Andersen wrote: Hello, snip My experience of trying to understand how the PTB at Debian want CD iso's distributed was not very easy. I like and admire Jigdo, great concept, but what left me frustrated was trying to understand how I could create iso's that contain the *updated* Woody .deb's, not the original release (3.0) .debs. It would have been just dandy if the author(s) of the somewhat scanty documentation had just assumed anyone needing to burn iso's of Debian-Stable is going to want 3.0r1 [or whatever is most recent], not 3.0. But that's not how the instructions seem to have been written. There's big holes ... . So anyway, my question, at last, is: does this thread I have unearthed mean that now, there IS a URL at which I can point Jigdo to get it to, in one easy-to-understand pass, assemble (I think that's the correct term for what Jigdo does) a 3.0r1 .iso set ??? A good starting point is http://www.debian.org, and if you follow the links you will find 'list archives' , 'cd iso imagesjigdo' 'Documentation'. i.e. http://www.debian.org/CD/jigdo-cd/ There is an 'update' cd image for those not wanting to build a new set of cdroms. snip -- Greg Madden
Re: 3.0r1 iso images ready for testing
Greg Madden wrote: On Saturday 22 February 2003 10:59 am, Soren Andersen wrote: Hello, snip My experience of trying to understand how the PTB at Debian want CD iso's distributed was not very easy. I like and admire Jigdo, great concept, but what left me frustrated was trying to understand how I could create iso's that contain the *updated* Woody .deb's, not the original release (3.0) .debs. It would have been just dandy if the author(s) of the somewhat scanty documentation had just assumed "anyone needing to burn iso's of Debian-Stable is going to want 3.0r1 [or whatever is most recent], not 3.0". But that's not how the instructions seem to have been written. There's big holes ... . So anyway, my question, at last, is: does this thread I have unearthed mean that now, there IS a URL at which I can point Jigdo to get it to, in one easy-to-understand pass, assemble (I think that's the correct term for what Jigdo does) a 3.0r1 .iso set ??? A good starting point is http://www.debian.org, and if you follow the links you will find 'list archives' , 'cd iso imagesjigdo' 'Documentation'. i.e. http://www.debian.org/CD/jigdo-cd/ I search for the string 'update' using the 'search this page' function in mozilla. I find one (1) hit: 'updated'. It is in the FAQ "AArgh..." and has nothing to do with 3.0r1. Where should I really look? Or for what string? Paul There is an 'update' cd image for those not wanting to build a new set of cdroms. snip
Re: 3.0r1 iso images ready for testing
On Sun, Dec 22, 2002 at 01:29:28PM +1000, jason andrade wrote: On Sun, 22 Dec 2002, Steve McIntyre wrote: None, really - I just tried to fit them into a small number of CDs similar to the potato ones. It would be simple to generate separate CDs (11) for each arch if people would prefer that...? my $0.02 is that it would be better to have a smaller ISO per arch as i think this results in less bandwith needed overall. it also means we can just drop each of the upgrade isos into the 3.0_r1 tree, e.g 3.0_r1/i386/debian-30r1-i386-update-1.iso I'm just about there on creating these. It's quite a lot less space-efficient, as binary-all will appear on all 11 binary discs and it takes up ~54MB on each disc. -- Steve McIntyre, Cambridge, UK.[EMAIL PROTECTED] Support the Campaign for Audiovisual Free Expression: http://www.eff.org/cafe/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: 3.0r1 iso images ready for testing
On Mon, 23 Dec 2002, Steve McIntyre wrote: I'm just about there on creating these. It's quite a lot less space-efficient, as binary-all will appear on all 11 binary discs and it takes up ~54MB on each disc. that's unfortunate, but i suspect the overall bandwidth saved will offset that. regards, -jason -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: 3.0r1 iso images ready for testing
On Sun, Dec 22, 2002 at 01:29:28PM +1000, jason andrade wrote: On Sun, 22 Dec 2002, Steve McIntyre wrote: None, really - I just tried to fit them into a small number of CDs similar to the potato ones. It would be simple to generate separate CDs (11) for each arch if people would prefer that...? my $0.02 is that it would be better to have a smaller ISO per arch as i think this results in less bandwith needed overall. it also means we can just drop each of the upgrade isos into the 3.0_r1 tree, e.g 3.0_r1/i386/debian-30r1-i386-update-1.iso I'm just about there on creating these. It's quite a lot less space-efficient, as binary-all will appear on all 11 binary discs and it takes up ~54MB on each disc. -- Steve McIntyre, Cambridge, UK.[EMAIL PROTECTED] Support the Campaign for Audiovisual Free Expression: http://www.eff.org/cafe/
Re: 3.0r1 iso images ready for testing
On Mon, 23 Dec 2002, Steve McIntyre wrote: I'm just about there on creating these. It's quite a lot less space-efficient, as binary-all will appear on all 11 binary discs and it takes up ~54MB on each disc. that's unfortunate, but i suspect the overall bandwidth saved will offset that. regards, -jason
3.0r1 iso images ready for testing
I've got (what I believe to be) functional update images generated on open now. I'm not sure exactly what needs to be done to make them available via jigdo yet - Phil, can I ask you to take a look at that for me? The ISOs are in /home/stevem/wood-update at the moment. I've generated these using an updated version of the update-cd script that I wrote for potato and I've now checked those changes in. The images are set up to contain: CD1: src all alpha arm hppa i386 ia64 m68k CD2: src all mips mipsel powerpc s390 sparc and each fits OK into 650MB OK. Pasztor, I looked at the dc2 stuff you've written, but I couldn't really understand how to use it to do what I wanted. As Richard said, some English documentation would really help. Maybe for r2... We should really try and generate some DVD jigdos too, but I think open is a little full atm: stevem@open:/home/jigdo-area$ df /home/jigdo-area Filesystem 1k-blocks Used Available Use% Mounted on /dev/md2 94621804 89722732 92508 100% /home Phil, any news on the disk front? Probably best to take that off-list, or onto debian-uk... -- Steve McIntyre, Cambridge, UK.[EMAIL PROTECTED] a href=http://www.rpg-soc.ucam.org/curs/CURS home page/a Can't keep my eyes from the circling sky, Tongue-tied twisted, Just an earth-bound misfit, I... -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: 3.0r1 iso images ready for testing
On Sun, Dec 22, 2002 at 10:58:19AM +1000, jason andrade wrote: On Sat, 21 Dec 2002, Steve McIntyre wrote: Hi Steve, CD1: src all alpha arm hppa i386 ia64 m68k CD2: src all mips mipsel powerpc s390 sparc one query - is there any reason to generate this as two ISO images rather than an upgrade ISO for each architecture which can then be dropped into the existing tree. this would make it a lot smaller for users downloads. i suspect that 75% or more of requests would be for i386 only. None, really - I just tried to fit them into a small number of CDs similar to the potato ones. It would be simple to generate separate CDs (11) for each arch if people would prefer that...? -- Steve McIntyre, Cambridge, UK.[EMAIL PROTECTED] Use Debian GNU/Linux - upgrade your Windoze box today! http://www.debian.org/ Can't keep my eyes from the circling sky, Tongue-tied twisted, Just an earth-bound misfit, I... -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: 3.0r1 iso images ready for testing
On Sun, 22 Dec 2002, Steve McIntyre wrote: None, really - I just tried to fit them into a small number of CDs similar to the potato ones. It would be simple to generate separate CDs (11) for each arch if people would prefer that...? my $0.02 is that it would be better to have a smaller ISO per arch as i think this results in less bandwith needed overall. it also means we can just drop each of the upgrade isos into the 3.0_r1 tree, e.g 3.0_r1/i386/debian-30r1-i386-update-1.iso regards, -jason -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
3.0r1 iso images ready for testing
I've got (what I believe to be) functional update images generated on open now. I'm not sure exactly what needs to be done to make them available via jigdo yet - Phil, can I ask you to take a look at that for me? The ISOs are in /home/stevem/wood-update at the moment. I've generated these using an updated version of the update-cd script that I wrote for potato and I've now checked those changes in. The images are set up to contain: CD1: src all alpha arm hppa i386 ia64 m68k CD2: src all mips mipsel powerpc s390 sparc and each fits OK into 650MB OK. Pasztor, I looked at the dc2 stuff you've written, but I couldn't really understand how to use it to do what I wanted. As Richard said, some English documentation would really help. Maybe for r2... We should really try and generate some DVD jigdos too, but I think open is a little full atm: [EMAIL PROTECTED]:/home/jigdo-area$ df /home/jigdo-area Filesystem 1k-blocks Used Available Use% Mounted on /dev/md2 94621804 89722732 92508 100% /home Phil, any news on the disk front? Probably best to take that off-list, or onto debian-uk... -- Steve McIntyre, Cambridge, UK.[EMAIL PROTECTED] a href=http://www.rpg-soc.ucam.org/curs/CURS home page/a Can't keep my eyes from the circling sky, Tongue-tied twisted, Just an earth-bound misfit, I...
Re: 3.0r1 iso images ready for testing
On Sat, 21 Dec 2002, Steve McIntyre wrote: Hi Steve, CD1: src all alpha arm hppa i386 ia64 m68k CD2: src all mips mipsel powerpc s390 sparc one query - is there any reason to generate this as two ISO images rather than an upgrade ISO for each architecture which can then be dropped into the existing tree. this would make it a lot smaller for users downloads. i suspect that 75% or more of requests would be for i386 only. regards, -jason
Re: 3.0r1 iso images ready for testing
On Sun, Dec 22, 2002 at 10:58:19AM +1000, jason andrade wrote: On Sat, 21 Dec 2002, Steve McIntyre wrote: Hi Steve, CD1: src all alpha arm hppa i386 ia64 m68k CD2: src all mips mipsel powerpc s390 sparc one query - is there any reason to generate this as two ISO images rather than an upgrade ISO for each architecture which can then be dropped into the existing tree. this would make it a lot smaller for users downloads. i suspect that 75% or more of requests would be for i386 only. None, really - I just tried to fit them into a small number of CDs similar to the potato ones. It would be simple to generate separate CDs (11) for each arch if people would prefer that...? -- Steve McIntyre, Cambridge, UK.[EMAIL PROTECTED] Use Debian GNU/Linux - upgrade your Windoze box today! http://www.debian.org/ Can't keep my eyes from the circling sky, Tongue-tied twisted, Just an earth-bound misfit, I...
Re: 3.0r1 iso images ready for testing
On Sun, 22 Dec 2002, Steve McIntyre wrote: None, really - I just tried to fit them into a small number of CDs similar to the potato ones. It would be simple to generate separate CDs (11) for each arch if people would prefer that...? my $0.02 is that it would be better to have a smaller ISO per arch as i think this results in less bandwith needed overall. it also means we can just drop each of the upgrade isos into the 3.0_r1 tree, e.g 3.0_r1/i386/debian-30r1-i386-update-1.iso regards, -jason
