Re: Multiple, non-concurrent repositories?
2010/3/30 Brian Ryans brian.l.ry...@gmail.com You replied to me personally, instead of the list. This fixes that. Quoting Rogerio Luz Coelho on 2010-03-27 20:39:07: You can use pinnig ... you are looking for the origin keys in Pinning to accomplish this. Put all the sources in the sources.list file and creae a /etc/apt/preferences list that looks something like: Package: * Pin: origin HomeRepo.com Pin-Priority: 850 Package: * Pin: origin DebRepo.com Pin-Priority: 750 Rogerio Everything's working so far with only the main repo pinned at 750. Would I have to pin all the Debian entries (backports, security, volatile) at 750 as well, or are they not relevant? I have no backports, security, volatile in my home repository, obviously. No only the repos you use should be pinned. But remember that IF you you backports, security etc... from the internet at any time then you have to adequate this in your Pin, or they will be pinned with auto values and that may conflict with local repos it it is not put into account ... as to your case I would use the lowest pinning possible for local repos , read man apt_preferences for the gory details :) Rogerio
Re: Multiple, non-concurrent repositories?
You replied to me personally, instead of the list. This fixes that. Quoting Rogerio Luz Coelho on 2010-03-27 20:39:07: You can use pinnig ... you are looking for the origin keys in Pinning to accomplish this. Put all the sources in the sources.list file and creae a /etc/apt/preferences list that looks something like: Package: * Pin: origin HomeRepo.com Pin-Priority: 850 Package: * Pin: origin DebRepo.com Pin-Priority: 750 Rogerio Everything's working so far with only the main repo pinned at 750. Would I have to pin all the Debian entries (backports, security, volatile) at 750 as well, or are they not relevant? I have no backports, security, volatile in my home repository, obviously. -- _ Brian Ryans 8B2A 54C4 E275 8CFD 8A7D 5D0B 0AD0 B014 C112 13D0 . ( ) ICQ UIN: 43190205 | Mail/MSN/Jabber: brianlry...@gmail.com ..: X ASCII Ribbon Campaign Against HTML mail and v-cards: asciiribbon.org / \ Any technology distinguishable from magic is insufficiently advanced signature.asc Description: Digital signature
Re: Multiple, non-concurrent repositories?
You replied to me personally, instead of the list. This fixes that. Quoting Rogerio Luz Coelho on 2010-03-27 20:39:07: You can use pinnig ... you are looking for the origin keys in Pinning to accomplish this. Put all the sources in the sources.list file and creae a /etc/apt/preferences list that looks something like: Package: * Pin: origin HomeRepo.com Pin-Priority: 850 Package: * Pin: origin DebRepo.com Pin-Priority: 750 Rogerio Everything's working so far with only the main repo pinned at 750. Would I have to pin all the Debian entries (backports, security, volatile) at 750 as well, or are they not relevant? I have no backports, security, volatile in my home repository, obviously. -- _ Brian Ryans 8B2A 54C4 E275 8CFD 8A7D 5D0B 0AD0 B014 C112 13D0 . ( ) ICQ UIN: 43190205 | Mail/MSN/Jabber: brianlry...@gmail.com ..: X ASCII Ribbon Campaign Against HTML mail and v-cards: asciiribbon.org / \ Any technology distinguishable from magic is insufficiently advanced signature.asc Description: Digital signature
Multiple, non-concurrent repositories?
I don't have Internet access from home for my laptop, so I access it from a friend's house. At home, I have a Lenny repo set up using reprepro (I'll call it homeRepo), and things install from there okay. When I have network access, I install packages from the official Debian repositories (here called debRepo), so packages can never be installed from both homeRepo and debRepo at the same time. that's all good. My problem lies in the fact that I have to edit my sources.list and update the package lists each time I change sites, so that I have access to that site's repository. I've checked the documentation, without success, for a way, without having to change config files every time I change sites, to specify Install package foobar, preferably from debRepo, but if debRepo doesn't work, then install from homeRepo, and only if homeRepo doesn't work, then give standard failure message. I've made some progress in figuring out how to do this, but my method still has a few snags: leave _both_ the homeRepo and debRepo entries uncommented in my sources.list. The snag here comes when I see a DSA, see if I need to upgrade, and if so, update safe-upgrade -- I get (expected) errors that homeRepo can't be found and every package in homeRepo is marked Untrusted until I update from home. (unexpected, but that's another thread) I am aware of 'aptitude install package=version' and 'package/archive'. Something that just struck me as I was composing this mail: Would it be a more effective solution to my problem (than what I'm currently using) to change homeRepo's archive name from 'lenny' to something else, then when I want to install a package from homeRepo, do 'aptitude install foopackage/somethingelse'? The way I see it, though, it wouldn't settle the update issue. As an aside, the homeRepo is mainly intended for installing packages until I can get to a network connection, at which time they'll be upgraded on my next upgrade run. -- _ Brian Ryans 8B2A 54C4 E275 8CFD 8A7D 5D0B 0AD0 B014 C112 13D0 . ( ) ICQ UIN: 43190205 | Mail/MSN/Jabber: brianlry...@gmail.com ..: X ASCII Ribbon Campaign Against HTML mail and v-cards: asciiribbon.org / \ Any technology distinguishable from magic is insufficiently advanced signature.asc Description: Digital signature
