Hi Marc, On Sa, 2015-06-27 at 23:23 +0200, Marc Haber wrote: (...) > If I recall correctly, mini-buildd 0.8 did not use reprepro, and the > reprepro backend was only introduced in mini-buildd 0.9. If that is > correct, I fully understand why the update procedure from 0.8x > outlined in the Admin Guide, using the import-08x script does not work > for my 0.9 installation.
yes, I fear that's so. > I happen to have an old 0.9 installation, and would like to know how > to get my old packages imported into the new 1.0.7 installation. The > reprepro home was moved from $HOME/rep to HOME/repositories/REPOID, > and the new 1.0 fully ignores what was in the old repositories. > > >From looking at the import-08x script, which only seems to do the > import into reprepro, there is no need to put the package in some > mini-buildd database. > > If that is correct: Is it possible to pull in the old repository via > reprepro's Mirroring / Updating mechanism (see > /usr/share/doc/reprepro/manual.html) or would you recommend adapting > import-08x to import-09x iterating through all source and binary > packages to manually poke them into the new reprepro structure? Ftr, as a general notion, mini-buildd is slave to the reprepro database; it does not store any package information by itself (albeit some last builds/last packages data that is used for informational purposes only). So basically, any manual *package* manipulation using reprepro should be no (technical) problem at all, giving you some options. Maybe some remarks to the import-08x script: As 0.8.x (i.e., mini-dinstall) allowed multiple versions per distribution it iterates over them, and also sorts them by version to get the rollback dists right. In your situation you might simplify your import procedure by just discarding the rollback distributions (chances are, btw, that your 0.9 repo does not have rollback dists at all). I have never used the "Mirroring / Updating" feature of reprepro myself; form the manual however I assume this requires changing the reprepro config of mini-buildd manually, so I would rather not recommend this. Otoh, if you know that feature very well and want to use it (else your toes curl), and I am correct that it only requires an *additional* config file "updates" and the auto-generated config files are not touched, and doing some sort of "one-time-update" with mini-buildd stopped -- I think this will also work fine. mini-buildd will of course, happily discard all your local config changes eventually. uff, hope this helps at all ;). I guess there is no alternative to some dry testing until you find the method you prefer... S -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
