There is a real regression between the debmirror for intrepid release (20070123ubuntu1) and jaunty release (20070123ubuntu3). I'm using a script to mirror hardy, intrepid and now jaunty for i386 and amd64, is working quite well on intrepid doing is mirroring job ... but since i use since yesterday another machine with jaunty the script stop on debmirrors errors .. Errors: dists/jaunty-backports/main/debian-installer/binary-amd64/Packages.bz2 missing Etc ...
For testing i tried chanhing protocol http to rsync and using 3 different sources but no way .. Tow different behavior for the same script there is really a modification between the tow versions ... i guess when the final jaunty repo is up it'll work .. but for the next release (KK) if i want to prepare my repo it won't be possible with debmirror if i want the nework install part for all my releases. Here my script ... ** Attachment added: "maj-ubuntu2.sh" http://launchpadlibrarian.net/25873437/maj-ubuntu2.sh -- missing main/debian-installer in repo causes debmirror to fail https://bugs.launchpad.net/bugs/34376 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
