Re: broken link to cdrecord on win
Hello, On Wed, Apr 11, 2007 at 12:28:05PM +1000, Carlos wrote: > I just noticed that the link to cdrecord on > http://www.debian.org/CD/faq/#dvd is not working. > > I found this alternative one, but I am not sure if it is the best one: > > http://smithii.com/cdrtools IMHO we should consider removing references to cdrtools in favour of wodim, Debian's fork of the software. Also, I don't think a lot of people will use the command-line cdrecord under Windows/Mac OS, so I'll also completely remove these references unless someone screams now. :) Cheers, Richard -- __ _ |_) /| Richard Atterer | GnuPG key: 888354F7 | \/¯| http://atterer.net | 08A9 7B7D 3D13 3EF2 3D25 D157 79E6 F6DC 8883 54F7 ¯ '` ¯ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: followup: jigdo template mdsum mismatch??
On Sun, Apr 08, 2007 at 05:37:22PM -0300, Carlos Carvalho wrote: > This is a bug in jigdo-file, for not ignoring the option when used with a > md5sum command, since the man page says "All options are silently ignored > if they are not applicable to the current command." I agree - I'll file a bug report so I don't forget about this. Richard -- __ _ |_) /| Richard Atterer | GnuPG key: 888354F7 | \/¯| http://atterer.net | 08A9 7B7D 3D13 3EF2 3D25 D157 79E6 F6DC 8883 54F7 ¯ '` ¯ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: missing files in .jigdo are not missing?
On Sun, Apr 08, 2007 at 07:16:18PM -0300, Carlos Carvalho wrote: > I'm still trying to create .iso using jigdo-mirror. Removing > --no-check-files from the default made it proceed, however some CDs > and DVDs don't build because it complains about missing files. > > How can one see which files are missing? I took the list from the > jigdo of one of the CDs that doesn't build, because it says there's > one missing, and verified that all do exist in the specified location. You can output a list of missing files using the "jigdo-file print-missing" command. Since no-one else appears to have problems, it seems that the .jigdo file is OK. I'm not sure what the problem at your side could be. jigdo-file will calculate the md5sum of files before copying them to the image, so even if the file is there and its name appears to be correct, it will not be copied over if its content doesn't match. Cheers, Richard -- __ _ |_) /| Richard Atterer | GnuPG key: 888354F7 | \/¯| http://atterer.net | 08A9 7B7D 3D13 3EF2 3D25 D157 79E6 F6DC 8883 54F7 ¯ '` ¯ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Bug#418688: d-i: Points to "Sarge" in sources.list
On Wed, 11 Apr 2007, Frans Pop wrote: > On Wednesday 11 April 2007 14:01, Luis Matos wrote: > > Why the installer does not has only the version-codename in the > > sources.list? > > The Etch installer _does_ only put code names in the sources.list. I'm very glad to hear that. I wonder, while we are at it, why don't we remove all the symlinks (save the "stable" one) in the dists directory on install CDs: /cdrom/dists# ls -l total 2 dr-xr-xr-x 4 root root 2048 2007-04-07 13:29 etch lr-xr-xr-x 1 root root4 2007-04-07 13:29 frozen -> etch lr-xr-xr-x 1 root root4 2007-04-07 13:29 stable -> etch lr-xr-xr-x 1 root root4 2007-04-07 13:29 testing -> etch lr-xr-xr-x 1 root root4 2007-04-07 13:29 unstable -> etch Would you help me to convince debian-cd maintainers that those symlinks should be removed? Last time I tried I was told they were there "just in case", but I fail to see how we could need a "frozen" symlink at all. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Bug#418688: d-i: Points to "Sarge" in sources.list
On Wednesday 11 April 2007 13:37, Santiago Vila wrote: > /cdrom/dists# ls -l > total 2 > dr-xr-xr-x 4 root root 2048 2007-04-07 13:29 etch > lr-xr-xr-x 1 root root4 2007-04-07 13:29 frozen -> etch > lr-xr-xr-x 1 root root4 2007-04-07 13:29 stable -> etch > lr-xr-xr-x 1 root root4 2007-04-07 13:29 testing -> etch > lr-xr-xr-x 1 root root4 2007-04-07 13:29 unstable -> etch > > Would you help me to convince debian-cd maintainers that those > symlinks should be removed? Last time I tried I was told they were > there "just in case", but I fail to see how we could need a "frozen" > symlink at all. The installer _does_ still need the suite links even if we don't put them in the sources.list anymore. I also don't know what frozen does there though, but I would guess that was used during the Sarge release process. pgpD5npaTuQZx.pgp Description: PGP signature
Re: Bug#418688: d-i: Points to "Sarge" in sources.list
On Wed, 11 Apr 2007, Frans Pop wrote: > On Wednesday 11 April 2007 13:37, Santiago Vila wrote: > > /cdrom/dists# ls -l > > total 2 > > dr-xr-xr-x 4 root root 2048 2007-04-07 13:29 etch > > lr-xr-xr-x 1 root root4 2007-04-07 13:29 frozen -> etch > > lr-xr-xr-x 1 root root4 2007-04-07 13:29 stable -> etch > > lr-xr-xr-x 1 root root4 2007-04-07 13:29 testing -> etch > > lr-xr-xr-x 1 root root4 2007-04-07 13:29 unstable -> etch > > > > Would you help me to convince debian-cd maintainers that those > > symlinks should be removed? Last time I tried I was told they were > > there "just in case", but I fail to see how we could need a "frozen" > > symlink at all. > > The installer _does_ still need the suite links even if we don't put them > in the sources.list anymore. Hmm, *all* of them? Would "stable" not be enough? Would not we have a bug somewhere if the installer failed when only the stable -> etch symlink exists? > I also don't know what frozen does there though, but I would guess that > was used during the Sarge release process. sarge was already "testing" before it was released, not "frozen". -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: missing files in .jigdo are not missing?
Richard Atterer ([EMAIL PROTECTED]) wrote on 11 April 2007 12:24: >On Sun, Apr 08, 2007 at 07:16:18PM -0300, Carlos Carvalho wrote: >> I'm still trying to create .iso using jigdo-mirror. Removing >> --no-check-files from the default made it proceed, however some CDs >> and DVDs don't build because it complains about missing files. >> >> How can one see which files are missing? I took the list from the >> jigdo of one of the CDs that doesn't build, because it says there's >> one missing, and verified that all do exist in the specified location. > >You can output a list of missing files using the "jigdo-file print-missing" >command. After posting I discovered it appears in the logs. Here's an example for the source.dvd, I can send you the complete list if necessary: Found 5935 of the 5943 files required by the template Copied input files to temporary file `image.tmp' - repeat command and supply mor e files to continue 2007-04-09 20:25:38: 8 parts still missing from image 20:25:41 URL:http://us.cdimage.debian.org/cdimage/snapshot/Debian/pool/main/a/ar abtex/arabtex_3.11.orig.tar.gz [582121/582121] -> "arabtex_3.11.orig.tar.gz" [1] 20:25:46 URL:http://us.cdimage.debian.org/cdimage/snapshot/Debian/pool/main/g/gs oap/gsoap_2.7.6d.orig.tar.gz [5866490/5866490] -> "gsoap_2.7.6d.orig.tar.gz" [1] 20:26:01 URL:http://us.cdimage.debian.org/cdimage/snapshot/Debian/pool/main/b/bo s/bos_1.1.orig.tar.gz [20395114/20395114] -> "bos_1.1.orig.tar.gz" [1] 20:26:46 URL:http://us.cdimage.debian.org/cdimage/snapshot/Debian/pool/main/c/cm -super/cm-super_0.3.3.orig.tar.gz [67064131/67064131] -> "cm-super_0.3.3.orig.ta r.gz" [1] 20:26:57 URL:http://us.cdimage.debian.org/cdimage/snapshot/Debian/pool/main/b/bo ost/boost_1.33.1.orig.tar.gz [14358143/14358143] -> "boost_1.33.1.orig.tar.gz" [ 1] 20:26:57 URL:http://us.cdimage.debian.org/cdimage/snapshot/Debian/pool/main/a/ar chzoom/archzoom_0.5.1-1.diff.gz [108481/108481] -> "archzoom_0.5.1-1.diff.gz" [1 ] 20:28:00 URL:http://us.cdimage.debian.org/cdimage/snapshot/Debian/pool/main/b/be neath-a-steel-sky/beneath-a-steel-sky_0.0372.orig.tar.gz [69379952/69379952] -> "beneath-a-steel-sky_0.0372.orig.tar.gz" [1] 20:28:01 URL:http://us.cdimage.debian.org/cdimage/snapshot/Debian/pool/main/b/ba ycomepp/baycomepp_0.10.orig.tar.gz [474619/474619] -> "baycomepp_0.10.orig.tar.g z" >Since no-one else appears to have problems, it seems that the .jigdo file >is OK. I'm not sure what the problem at your side could be. Maybe it's just that no-one *notices* it. At first I put maxMissing=0, on the assumption that we're a full mirror and so we should have everything. However this breaks already for the first architecture, because 2 out of 3 dvds and some cds don't complete for alpha. >jigdo-file will calculate the md5sum of files before copying them to >the image, so even if the file is there and its name appears to be >correct, it will not be copied over if its content doesn't match. I checked some of the filenames and size (not checksums) and what comes from us.cdimage matches with what we have. Also, during the build process at least two full updates of our mirror were done, so it's not a problem of us being behind the latest version. Therefore, if they differ there's a problem. We have testing and unstable also, so there should be nothing that us.cdimage uses that we don't have. I agree that the problem may not be in jigdo but in the iso image itself using something different. How can we investigate the issue? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: missing files in .jigdo are not missing?
On Wed, Apr 11, 2007 at 11:09:14AM -0300, Carlos Carvalho wrote: >Richard Atterer ([EMAIL PROTECTED]) wrote on 11 April 2007 12:24: > >On Sun, Apr 08, 2007 at 07:16:18PM -0300, Carlos Carvalho wrote: > >> I'm still trying to create .iso using jigdo-mirror. Removing > >> --no-check-files from the default made it proceed, however some CDs > >> and DVDs don't build because it complains about missing files. > >> > >> How can one see which files are missing? I took the list from the > >> jigdo of one of the CDs that doesn't build, because it says there's > >> one missing, and verified that all do exist in the specified location. > > > >You can output a list of missing files using the "jigdo-file print-missing" > >command. > >After posting I discovered it appears in the logs. Here's an example >for the source.dvd, I can send you the complete list if necessary: > >Found 5935 of the 5943 files required by the template >Copied input files to temporary file `image.tmp' - repeat command and supply >mor >e files to continue >2007-04-09 20:25:38: 8 parts still missing from image >20:25:41 >URL:http://us.cdimage.debian.org/cdimage/snapshot/Debian/pool/main/a/ar >abtex/arabtex_3.11.orig.tar.gz [582121/582121] -> "arabtex_3.11.orig.tar.gz" >[1] >20:25:46 >URL:http://us.cdimage.debian.org/cdimage/snapshot/Debian/pool/main/g/gs >oap/gsoap_2.7.6d.orig.tar.gz [5866490/5866490] -> "gsoap_2.7.6d.orig.tar.gz" >[1] >20:26:01 >URL:http://us.cdimage.debian.org/cdimage/snapshot/Debian/pool/main/b/bo >s/bos_1.1.orig.tar.gz [20395114/20395114] -> "bos_1.1.orig.tar.gz" [1] >20:26:46 >URL:http://us.cdimage.debian.org/cdimage/snapshot/Debian/pool/main/c/cm >-super/cm-super_0.3.3.orig.tar.gz [67064131/67064131] -> >"cm-super_0.3.3.orig.ta >r.gz" [1] >20:26:57 >URL:http://us.cdimage.debian.org/cdimage/snapshot/Debian/pool/main/b/bo >ost/boost_1.33.1.orig.tar.gz [14358143/14358143] -> "boost_1.33.1.orig.tar.gz" >[ >1] >20:26:57 >URL:http://us.cdimage.debian.org/cdimage/snapshot/Debian/pool/main/a/ar >chzoom/archzoom_0.5.1-1.diff.gz [108481/108481] -> "archzoom_0.5.1-1.diff.gz" >[1 >] >20:28:00 >URL:http://us.cdimage.debian.org/cdimage/snapshot/Debian/pool/main/b/be >neath-a-steel-sky/beneath-a-steel-sky_0.0372.orig.tar.gz [69379952/69379952] >-> >"beneath-a-steel-sky_0.0372.orig.tar.gz" [1] >20:28:01 >URL:http://us.cdimage.debian.org/cdimage/snapshot/Debian/pool/main/b/ba >ycomepp/baycomepp_0.10.orig.tar.gz [474619/474619] -> >"baycomepp_0.10.orig.tar.g >z" Which jigdo file(s) are you using - the etch release? If so, I've already generated working ISO images locally using those same jigdos. > > >Since no-one else appears to have problems, it seems that the .jigdo file > >is OK. I'm not sure what the problem at your side could be. > >Maybe it's just that no-one *notices* it. At first I put maxMissing=0, >on the assumption that we're a full mirror and so we should have >everything. However this breaks already for the first architecture, >because 2 out of 3 dvds and some cds don't complete for alpha. > > >jigdo-file will calculate the md5sum of files before copying them to > >the image, so even if the file is there and its name appears to be > >correct, it will not be copied over if its content doesn't match. > >I checked some of the filenames and size (not checksums) and what >comes from us.cdimage matches with what we have. Also, during the >build process at least two full updates of our mirror were done, so >it's not a problem of us being behind the latest version. Therefore, >if they differ there's a problem. We have testing and unstable also, >so there should be nothing that us.cdimage uses that we don't have. > >I agree that the problem may not be in jigdo but in the iso image >itself using something different. How can we investigate the issue? I've got access to the files on both snapshot servers, so I can check if needed. -- Steve McIntyre, Cambridge, UK.[EMAIL PROTECTED] Who needs computer imagery when you've got Brian Blessed? signature.asc Description: Digital signature
Re: missing files in .jigdo are not missing?
Steve McIntyre ([EMAIL PROTECTED]) wrote on 11 April 2007 15:24: >Which jigdo file(s) are you using - the etch release? Yes. >If so, I've already generated working ISO images locally using those >same jigdos. Me too, I've generated *all* images. But about 30 files had to be pulled from us.cdimage because jigdo-file didn't want the local ones. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: missing files in .jigdo are not missing?
On Wed, Apr 11, 2007 at 12:01:32PM -0300, Carlos Carvalho wrote: >Steve McIntyre ([EMAIL PROTECTED]) wrote on 11 April 2007 15:24: > >Which jigdo file(s) are you using - the etch release? > >Yes. > > >If so, I've already generated working ISO images locally using those > >same jigdos. > >Me too, I've generated *all* images. But about 30 files had to be >pulled from us.cdimage because jigdo-file didn't want the local ones. They worked for me locally, so I guess that means your local mirror probably has a few broken files. -- Steve McIntyre, Cambridge, UK.[EMAIL PROTECTED] Armed with "Valor": "Centurion" represents quality of Discipline, Honor, Integrity and Loyalty. Now you don't have to be a Caesar to concord the digital world while feeling safe and proud. signature.asc Description: Digital signature
Re: missing files in .jigdo are not missing?
Steve McIntyre ([EMAIL PROTECTED]) wrote on 11 April 2007 16:08: >On Wed, Apr 11, 2007 at 12:01:32PM -0300, Carlos Carvalho wrote: >>Steve McIntyre ([EMAIL PROTECTED]) wrote on 11 April 2007 15:24: >> >Which jigdo file(s) are you using - the etch release? >> >>Yes. >> >> >If so, I've already generated working ISO images locally using those >> >same jigdos. >> >>Me too, I've generated *all* images. But about 30 files had to be >>pulled from us.cdimage because jigdo-file didn't want the local ones. > >They worked for me locally, so I guess that means your local mirror >probably has a few broken files. OK, I'll refresh them from the upstream mirror. Thanks. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
DUTH mirror
Hi, I'd like to inform you that ftp.duth.gr is also mirroring the CD and DVD images. They are available via FTP, HTTP and rsync. The URLs are ftp://ftp.duth.gr/debian-cd/ http://ftp.duth.gr/debian-cd/ rsync://ftp.duth.gr/debian-cd/ Regards, Adamantios -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: broken link to cdrecord on win
On 4/11/07, Richard Atterer <[EMAIL PROTECTED]> wrote: Hello, On Wed, Apr 11, 2007 at 12:28:05PM +1000, Carlos wrote: > I just noticed that the link to cdrecord on > http://www.debian.org/CD/faq/#dvd is not working. > > I found this alternative one, but I am not sure if it is the best one: > > http://smithii.com/cdrtools IMHO we should consider removing references to cdrtools in favour of wodim, Debian's fork of the software. Also, I don't think a lot of people will use the command-line cdrecord under Windows/Mac OS, so I'll also completely remove these references unless someone screams now. :) I agree in that few people would be interested in command-line windows burning... I myself checked the link just out of curiosity of seeing the win port of cdrecord... But just today I found this interesting program that might be worth including in the FAQ (being GPL): Project: http://sourceforge.net/projects/cdrtfe Home Page: http://home.arcor.de/kerberos002/cdrtfe/index_en.html "A small burning application for Windows. cdrtfe is a frontend for the cdrtools (cdrecord, mkisofs, readcd, cdda2wav), Mode2CDMaker and VCDImager. It can burn data disks (CD and DVD), Audio CDs, XCDs, (S)VCDs and DVD-Video disks." Interestingly, it comes with all the needed programs bundled in an installable "Setup.exe" I haven't tried it myself, though. But if it works it would deffinitelly be the option to recomentd over the proprietary ones. If no one around there has tested it and you want me to, just drop me an email. I can test it at my work laptop. Carlos Cheers, Richard -- __ _ |_) /| Richard Atterer | GnuPG key: 888354F7 | \/¯| http://atterer.net | 08A9 7B7D 3D13 3EF2 3D25 D157 79E6 F6DC 8883 54F7 ¯ '` ¯
