(it seems that the first time i sent the email, it was lost. I resend it, sorry if you receive it twice).
Hey Erich, Just a small patch for rapt: http://gvallee.free.fr/oscar/rapt.patch. The problem i had with the /etc/apt/sources.list file for the image was just because i am sometimes stupid. ;-) Anyway, it works fine now with Debian sarge. I also have a new script to automatically download .deb packages. The script is available here: http://gvallee.free.fr/oscar/get_deb_packages (it should be possible to use it that way: ./get_deb_packages /tftpboot/distro/debian-3.1-i386). I don't think i will have the time to work on OoD during the two next weeks but i will try then to see if my script and rapt work well together (and therefore have an pretty good mechanism for the creation of a local repository for .deb packages and a mechanism to create an image based on a local repository). Best regards, Le Samedi 6 Mai 2006 05:37, Erich Focht a écrit : > Hi Geoffroy, > > On Saturday 06 May 2006 07:16, Geoffroy VALLEE wrote: > > I played a little bit with rapt and it is almost working. > > > > I made some modifications (to find the correct codename) and now the > > following command mostly works: > > ./rapt --repo ftp://ftp.debian.org/debian/ stable main non-free > > contrib --installroot /tmp/img install less > > this line should have been: > > ./rapt --repo ftp://ftp.debian.org/debian/+stable+main+non-free+contrib \ > --installroot /tmp/img install less > > So the repository name should have the rest of the words, which would be > added in the select.list file added and separated by "+" signs. > > I actually expected that it would be called: > ftp://ftp.debian.org/debian/+sarge+main+non-free+contrib > because I expected that the first word after the URL is the codename. Is > "sarge" and "stable" the same thing? > > > The image is created but the generated /etc/apt/sources.list file (in the > > image) is not valid, i have "deb 1 .". I will try to fix that tomorrow. > > Hmmm, that worked with the example I've sent foirst (ubuntu). But take > care: rapt creates a temporary select.list file (even in the image) and > backs up the file it finds. The temporary select.list file will be removed > after the apt-get job is done (in the image). > > The problem of could be solved with the URL repositories, as with rpms. You > can install the whole cluster from remote repos if you have access to the > internet. And, by the way: you can specify multiple --repo arguments. In > that case I think all repositories will be considered. So you could have a > small local repository and some normal debian mirror in addition. > > There is an issue with debootstrap: currently the packages are downloaded > from somewhere, not from the local repository. The reason is that I don't > know how to produce a correct Release file in the local repository, the > Packages file is not enough... If you have an idea...? > > BTW: with the Ubuntu CD you have a quite limited set of .deb files which > can serve as basis for a local repository. Sorry that I mention ubuntu so > often, but it is the debian-alike distro which I can handle here most > easilly. > > Thanks for looking into this! > > Best regards, > Erich > > > Anyway, I will try to send you a patch tomorrow (hopefully), i have > > currently a very ugly work around that i have to fix. > > > > I also have a question: we assume currently that before to use OSCAR all > > binary packages are copied in /tftpboot/distro... But for Debian it is a > > kind of painfull to do that (something like 14 CDs and difficult to know > > which sub-set of CDs is necessary). When we create an image, the needed > > packages are then available (in /var/cache/apt/archives/) but instead to > > have to repository -> image, we have in that case image -> repository. At > > the same time we need to have the local repository for packages used to > > create the image, at least for compute node update. > > Any thought about that? > > > > Thanks again Erich. :-) > > > > Le Vendredi 5 Mai 2006 17:17, Erich Focht a écrit : > > > On Friday 05 May 2006 20:01, Geoffroy Vallée wrote: > > > > Hey Erich, > > > > > > > > You are the man! :-) It is exactly what OoD needs, thanks a lot. > > > > > > > > I will try to play with rapt this week-end and if i can help you to > > > > finish rapt, just tell me. > > > > > > Cool, my experience with debian is really very very limited. I'll try > > > to add stuff to packman, to get rid of that in first place. > > > > > > > For your question about the version number of Debian, there is > > > > a /etc/lsb-release file in testing but it not gives the release > > > > number of Debian but the release number of the supported LSF. > > > > Typically you will find something like: > > > > LSB Version: > > > > core-2.0-noarch:core-3.0-noarch:core-3.1-noarch:core-2.0-ia32:core-3. > > > >0-ia > > > > 32:core-3.1-ia32:cxx-2.0-noarch:cxx-3.0-noarch:cxx-3.1-noarch:cxx-2.0 > > > >-ia32 > > > > > > > >:cxx-3.0-ia32:cxx-3.1-ia32:graphics-2.0-noarch:graphics-3.0-noarch:gra > > > >:phic > > > > > > > >s-3.1-noarch:graphics-2.0-ia32:graphics-3.0-ia32:graphics-3.1-ia32:des > > > >ktop -3.1-noarch:desktop-3.1-ia32 > > > > > > ??? Is this the content of the lsb-release file? I wonder why are there > > > several versions of packages listed? > > > > > > Oh, the ubuntu lsb-release file has a DISTRIB_CODENAME=breezy line... > > > So maybe we should search in several places. > > > > > > We need a way to detect the distro codename of a repository, be it > > > local or remote. This is a bit of a problem, especially if the > > > repository is remote. > > > > > > From which package does /etc/debian-release come from? How exactly do > > > the lines for stable and testing look like? And what is the > > > relationship between these numbers and the codenames? Can you please > > > list the codenames (sarge, etc) and the corresponding version numbers? > > > That's quite important, current rapt (from repo-apt) only looks into > > > the lsb-release file and that might not even work with sarge. > > > > > > Thanks in advance, > > > best regards, > > > Erich > > > > > > > Furthermore, the management of the Debian version is kind of > > > > atypical: - a stable version has a version number, this number is > > > > available from /etc/debian-release. > > > > - a testing version may not have a version number but the > > > > name "testing/unstable" (testing/unstable is the same regarding > > > > Debian releases). A version number is set to testing by the release > > > > manager typically at code freeze time. > > > > > > > > I plan to support only stable, so typically my idea is currently to > > > > say: if /etc/debian-version is 3.1 it is ok, if not this Debian > > > > release is not supported. > > > > > > > > If you want i can look at that during the week-end. > > > > > > > > Thanks again Erich. > > > > > > > > Le Vendredi 5 Mai 2006 12:54, Erich Focht a écrit : > > > > > Hi Geoffroy, > > > > > > > > > > I have a prototype of a wrapper to apt-get which has similar > > > > > functionality like yume. You can download it from: > > > > > http://home.arcor.de/efocht/oscar/rapt > > > > > > > > > > > > > > > Usage: ./rapt OPTIONS [APT-GET_OPTIONS] > > > > > > > > > > Call apt-get with _only_ the repositories passed on the command > > > > > line . OPTIONS can be: > > > > > --repo URL : repository which should be included in apt actions > > > > > (multiple --repo options are possible). > > > > > --installroot DIR : install/remove packages to/from image DIR > > > > > --export : create httpd configuration for local repositories > > > > > --unexport : delete httpd configuration for local repositories > > > > > --listexp : list exported local repositories > > > > > --prepare : generate repodata for local repositories > > > > > --help : this help information > > > > > --verbose : verbose output > > > > > > > > > > APT-GET_OPTIONS are options to be passed to the apt-get command. > > > > > > > > > > > > > > > > > > > > The repositories have special format, but it is quite similar to > > > > > yume. > > > > > > > > > > What I tried until now (on an ubuntu system): > > > > > > > > > > rapt --repo http://ftp.uni-kl.de/pub/linux/ubuntu/+breezy+main \ > > > > > --installroot /tmp/img install apache-mpm-worker > > > > > > > > > > (this runs debootstrap (from a standard repository, not yet from > > > > > what I asked for) into the image /tmp/img). > > > > > > > > > > > > > > > rapt --repo /tftpboot/distro/ubuntu-5.10-i386 --prepare > > > > > > > > > > Builds metadata cache (Packages files) for the .deb packages copied > > > > > to /tftpboot/distro/... > > > > > > > > > > > > > > > rapt --repo /tftpboot/distro/ubuntu-5.10-i386 --export > > > > > > > > > > Exports the local repository via http (apache must be installed!). > > > > > > > > > > > > > > > rapt --repo /tftpboot/distro/ubuntu-5.10-i386 --installroot > > > > > /tmp/img \ --yes install apache2-mpm-worker > > > > > > > > > > Installs apache2 into the image. > > > > > > > > > > > > > > > The functionality for calling rapt from the clients is not yet > > > > > complete, the repository renaming (from file: to http: must be > > > > > improved), but this is almost done, too. > > > > > > > > > > I have basic problems with detecting the debian codename for a > > > > > particular repository, therefore currently the codename is read out > > > > > of the /etc/lsb-release file (I hope sarge has that, too). If you > > > > > know a better method to detect sarge/sid/whatever, please tell me. > > > > > Until then mixed distros will not be supported. > > > > > > > > > > If this is okay, I think we could proceed to integrate rapt into > > > > > packman in an easy way (similar to yume, as rapt can now handle > > > > > chroots correctly). > > > > > > > > > > Best regards, > > > > > Erich -- Geoff ------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid0709&bid&3057&dat1642 _______________________________________________ Oscar-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/oscar-devel
