I have the yarrow's iso files on my HD in a RH9 system. Let's say I want to upgrade selected packages using an "apt-get install" pointing to my iso-mounted files, how do I do it?
i.e I mount the iso into some /mnt/yarrow1, /mnt/yarrow 2 etc..
Then what is the complete procedure to make my apt look into my own HD to upgrade packages. Can anybody redirect me to the correct resource or some literature hanging on the web? Thanks.
Assume also that I do not wish to burn CDs! I do not want to use apt-cdrom. Thanks.
With kind regards,
Didier.
--- PhD student
Singapore Synchrotron Light Source (SSLS) 5 Research Link, Singapore 117603
Email: slsbdfc at nus dot edu dot sg \or\ didierbe at sps dot nus dot edu dot sg Website: http://ssls.nus.edu.sg
On Fri, 2003-11-21 at 10:02, Didier Casse wrote:
I have the yarrow's iso files on my HD in a RH9 system. Let's say I want to upgrade selected packages using an "apt-get install" pointing to my iso-mounted files, how do I do it?
i.e I mount the iso into some /mnt/yarrow1, /mnt/yarrow 2 etc..
Then what is the complete procedure to make my apt look into my own HD to upgrade packages. Can anybody redirect me to the correct resource or some literature hanging on the web? Thanks.
Assume also that I do not wish to burn CDs! I do not want to use apt-cdrom. Thanks.
I just updated a RH9 system to FC1 by writing the bootdisk image to a floppy and directing the installer to the hd partition containing the iso's. It's working fine now...
I'm not sure, but maybe grub can boot those disk images as well?
Klaasjan,
Do you have the time to write out a mini-howto on that? I have a feeling that your instruction can help a few people following in your footsteps, and who may not have the opportunity to figure out a working solution by themselves.
Me, I need one that can reliably do it from 5000km away. It'll be loop-mounted ISOs, apt-get and similar craziness, I think. Or I need to book a flight. 8-) Either way, I'm not the target audience, but I'm close. ACME@cl says that CL can do it with just apt-get, and that's incredibly interesting.
- bish
Klaasjan Brand wrote:
On Fri, 2003-11-21 at 10:02, Didier Casse wrote:
I have the yarrow's iso files on my HD in a RH9 system. Let's say I want to upgrade selected packages using an "apt-get install" pointing to my iso-mounted files, how do I do it?
i.e I mount the iso into some /mnt/yarrow1, /mnt/yarrow 2 etc..
Then what is the complete procedure to make my apt look into my own HD to upgrade packages. Can anybody redirect me to the correct resource or some literature hanging on the web? Thanks.
Assume also that I do not wish to burn CDs! I do not want to use apt-cdrom. Thanks.
I just updated a RH9 system to FC1 by writing the bootdisk image to a floppy and directing the installer to the hd partition containing the iso's. It's working fine now...
I'm not sure, but maybe grub can boot those disk images as well?
On Fri, 21 Nov 2003, bishop wrote:
Klaasjan,
Do you have the time to write out a mini-howto on that? I have a feeling that your instruction can help a few people following in your footsteps, and who may not have the opportunity to figure out a working solution by themselves.
Me, I need one that can reliably do it from 5000km away. It'll be loop-mounted ISOs, apt-get and similar craziness, I think. Or I need to book a flight. 8-) Either way, I'm not the target audience, but I'm close. ACME@cl says that CL can do it with just apt-get, and that's incredibly interesting.
Ok, since you need a remote upgrade then apt/yum/up2date is needed. For apt you basically need to create a local repository of the RPMS. Suppose you have the iso's mounted in /mnt/yarrow1, /mnt/yarrow2 and /mnt/yarrow3, I'd probably do it somewhat like this (watch out for typos and thinkos, I wrote this from top of my head so not tested.. ): mkdir -p /var/tmp/fedora/RPMS.core cd /var/tmp/fedora/RPMS.core ln -s /mnt/yarrow1/Fedora/RPMS/* . ln -s /mnt/yarrow2/Fedora/RPMS/* . ln -s /mnt/yarrow3/Fedora/RPMS/* . genbasedir --bloat /var/tmp/fedora
The add that to your sources.list: "file://var/tmp fedora core" Check that it works (no errors in output) by running "apt-get update" and then you should be ready to roll: apt-get install kernel (choose suitable one from the output) apt-get dist-upgrade
..and there it is, if all goes well. Note that there's a packaging issue which prevents a fully updated RHL 9 from being updated to FC 1 cleanly: Latest RH errata has these packages: perl-CGI 2:1.804-88.3 perl-CPAN 2:1.804-88.3 perl-DB_File 2:1.804-88.3
..and FC1 has this: [pmatilai@chip]$ rpm -q --obsoletes perl perl-Digest-MD5 perl-MIME-Base64 perl-libnet perl-Storable perl-CGI <= 2:2.81-88 perl-CPAN <= 2:1.61-88 perl-DB_File <= 2:1.804-88
Meaning that those three packages don't get obsoleted by the new perl package although they should, otherwise there are file conflicts. To get around that do "rpm -e perl-CGI perl-CPAN perl-DB_File" before running dist-upgrade. Nothing *bad* will happen if you dont remove those first, you just wont be able to run the upgrade before you do.
- Panu -
On 21/11/03, at 14:51 +0200, Panu Matilainen pmatilai@welho.com babbled:
Ok, since you need a remote upgrade then apt/yum/up2date is needed. For apt you basically need to create a local repository of the RPMS. Suppose you have the iso's mounted in /mnt/yarrow1, /mnt/yarrow2 and /mnt/yarrow3, I'd probably do it somewhat like this (watch out for typos and thinkos, I wrote this from top of my head so not tested.. ): mkdir -p /var/tmp/fedora/RPMS.core cd /var/tmp/fedora/RPMS.core ln -s /mnt/yarrow1/Fedora/RPMS/* . ln -s /mnt/yarrow2/Fedora/RPMS/* . ln -s /mnt/yarrow3/Fedora/RPMS/* . genbasedir --bloat /var/tmp/fedora
The add that to your sources.list: "file://var/tmp fedora core" Check that it works (no errors in output) by running "apt-get update" and then you should be ready to roll: apt-get install kernel (choose suitable one from the output) apt-get dist-upgrade
This is exactly what I was looking for. Thanks Panu. ;-p
With kind regards,
Didier.
--- PhD student
Singapore Synchrotron Light Source (SSLS) 5 Research Link, Singapore 117603
Email: slsbdfc at nus dot edu dot sg \or\ didierbe at sps dot nus dot edu dot sg Website: http://ssls.nus.edu.sg
Hi,
Last year I submitted a bug through bugzilla.redhat.com, which affects recode-3.6-9 in Fedore Core 1. A recommended patch is also attached. It has still a status NEW, so it seems for me nothing happened until now. Is it possible to make the bug handling process faster? The package, I would like to submit, requires recode.
New packages: I'm a bit confused now how to contribute new packages. On fedora.us I can read, it will be merged with fedora.redhat and the package naming guideline applies only to fedora.us. On fedora.redhat there are information about a future Extra, Alternative ... repository structure and a modified package naming concept (latter is in the mailing list)... What to do then? Is it better to wait for finishing the merging, or to submit to fedora.us?
Zoli
On 21/11/03, at 14:51 +0200, Panu Matilainen pmatilai@welho.com babbled:
On Fri, 21 Nov 2003, bishop wrote:
Klaasjan,
Do you have the time to write out a mini-howto on that? I have a feeling that your instruction can help a few people following in your footsteps, and who may not have the opportunity to figure out a working solution by themselves.
Me, I need one that can reliably do it from 5000km away. It'll be loop-mounted ISOs, apt-get and similar craziness, I think. Or I need to book a flight. 8-) Either way, I'm not the target audience, but I'm close. ACME@cl says that CL can do it with just apt-get, and that's incredibly interesting.
Ok, since you need a remote upgrade then apt/yum/up2date is needed. For apt you basically need to create a local repository of the RPMS. Suppose you have the iso's mounted in /mnt/yarrow1, /mnt/yarrow2 and /mnt/yarrow3, I'd probably do it somewhat like this (watch out for typos and thinkos, I wrote this from top of my head so not tested.. ): mkdir -p /var/tmp/fedora/RPMS.core cd /var/tmp/fedora/RPMS.core ln -s /mnt/yarrow1/Fedora/RPMS/* . ln -s /mnt/yarrow2/Fedora/RPMS/* . ln -s /mnt/yarrow3/Fedora/RPMS/* . genbasedir --bloat /var/tmp/fedora
The add that to your sources.list: "file://var/tmp fedora core"
Must be a typo error from you. I think that the correct expression is:
----------------------------- rpm file:/var/tmp fedora core -----------------------------
With kind regards,
Didier
--- PhD student
Singapore Synchrotron Light Source (SSLS) 5 Research Link, Singapore 117603
Email: slsbdfc at nus dot edu dot sg \or\ didierbe at sps dot nus dot edu dot sg Website: http://ssls.nus.edu.sg
On Fri, 2003-11-21 at 13:02, bishop wrote:
Klaasjan,
Do you have the time to write out a mini-howto on that? I have a feeling that your instruction can help a few people following in your footsteps, and who may not have the opportunity to figure out a working solution by themselves.
I believe it's already documented in the RH installation guide. IMO it's not that hard to do: just use the boot floppy and select "hard drive" when asked for installation source. After that you can select a partition and enter the path where the ISO files are.
Me, I need one that can reliably do it from 5000km away. It'll be loop-mounted ISOs, apt-get and similar craziness, I think. Or I need to book a flight. 8-) Either way, I'm not the target audience, but I'm close. ACME@cl says that CL can do it with just apt-get, and that's incredibly interesting.
Creating your own repository is documented all over the net: http://www.dragonsdawn.net/~gordon/red-hat-apt-repository-howto/
On 21/11/03, at 15:13 +0100, Klaasjan Brand kjb@dds.nl babbled:
Creating your own repository is documented all over the net: http://www.dragonsdawn.net/~gordon/red-hat-apt-repository-howto/
Close to it. This is the formal type usable by others. I wanted to create a more private one to upgrade specific packages in my distro. This gives some insights but Paul's reply is to the point. Thanks for the help Klaasjan.
With kind regards,
Didier.
--- PhD student
Singapore Synchrotron Light Source (SSLS) 5 Research Link, Singapore 117603
Email: slsbdfc at nus dot edu dot sg \or\ didierbe at sps dot nus dot edu dot sg Website: http://ssls.nus.edu.sg
devel@lists.stg.fedoraproject.org
-
bishop -
Didier Casse -
Klaasjan Brand -
Michel Alexandre Salim -
Panu Matilainen -
Zoltan Kota