Re: mixing stable and testing
On Mon, Jan 26, 2004 at 06:31:24PM -0800, David Rothenberger wrote: I obviously want to track stable (since this server needs to be secure), but there are a few packages that I want from testing or unstable. How to do this? Hi Dave, from those at debian-on-high, it is recommended to follow your tract. On stable, which is the recommended one for production systems, is known to be 'a bit old', you have 2 good optinons: backports and source. backports is a unofficial site that makes debs of certain popular (admin) packages. then there is the debian source packages. the idea that both of these is to compile a package against stable libraries to produce something that can be installed on a stable system and not require you to install testing or unstable debs which would require you to upgrade the dependencies to testing/unstable deb and thus mess with you stable system. This message from the recent archives should be helpful: http://lists.debian.org/debian-user/2004/debian-user-200401/msg06198.html IIUC, that messages describes how to install binary packages. In fact, the whole thread seemed to focus on that. The Debian Reference (section 6.4.10) suggests that it's better to compile from source packages, so you don't end up upgrading libc, for example. Is this really true? HTH -Kev signature.asc Description: Digital signature
Re: mixing stable and testing
On Monday 26 January 2004 09:12 pm, David Rothenberger wrote: I obviously want to track stable (since this server needs to be secure), but there are a few packages that I want from testing or unstable. How to do this? This message from the recent archives should be helpful: http://lists.debian.org/debian-user/2004/debian-user-200401/msg06198.html Adam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: mixing stable and testing
I obviously want to track stable (since this server needs to be secure), but there are a few packages that I want from testing or unstable. How to do this? This message from the recent archives should be helpful: http://lists.debian.org/debian-user/2004/debian-user-200401/msg06198.html IIUC, that messages describes how to install binary packages. In fact, the whole thread seemed to focus on that. The Debian Reference (section 6.4.10) suggests that it's better to compile from source packages, so you don't end up upgrading libc, for example. Is this really true? Dave -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: mixing stable and testing
On Monday 26 January 2004 09:31 pm, David Rothenberger wrote: The Debian Reference (section 6.4.10) suggests that it's better to compile from source packages, so you don't end up upgrading libc, for example. Is this really true? Upgrading libc on stable with libc on testing could easily break a good portion of your system. One of the reasons aptitude was suggested was because you can view the dependencies before they are downloaded and make sure something critical (like libc) won't be affected. If you prefer to install from source, you could use apt-get -t testing source instead of apt-get -t testing install to get source packages instead. I am not experienced enough with Debian to give a recommendation - try searching the archives. Adam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: mixing stable and testing
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Mon, Jan 26, 2004 at 06:12:32PM -0800, David Rothenberger wrote: I obviously want to track stable (since this server needs to be secure), but there are a few packages that I want from testing or unstable. How to do this? Short answer: You don't. Long answer: Mixing stable with testing is usually a bad idea once testing starts having newer libraries than stable (as is the case most for most of testing's lifepsan). Mixing with unstable is pretty much a no-no with stable. The way to get around this is to go check out http://www.backports.org/ to find backports (packages compiled for the older versions). If you can't find it there, look for sources compiled for stable on http://www.apt-get.org/ for the packages you want. If all else fails, upgrade to testing or unstable as soon as your comfortable with Debian. But I don't understand how this will interact with APT. That is, suppose I get the sources, compile, and install the resulting binary package. What happens when the package is updated in testing/unstable? Will apt-get or dselect get me the updated _source_ package? The binary package? Or will I have to manually track the package myself. apt will get the newest version available unless you use apt pinning (if you don't know exactly how Debian dependencies work, this is not the solution you are working for and it *will* burn you badly sooner or later (and probably sooner, rather than later)); or if you use aptitude to mark a package as held (it will stick to that version instead of moving to something newer, you're probably doing something wrong if you have to mark anything held if you're not using stable). Similarly, what happens if it's updated in stable? Will my package from testing/unstable be replaced? Only if the version number is greater. I know there's something, probably in the Developers section, on http://debian.org/ that explains the Debian versioning policy. This should also give you a pretty good idea how apt and dpkg interpret version numbers. Do I need to pin the package in my apt configuration? No. When you're pinning, you're playing around with how apt does dependency and version handling. This is a Bad Thing unless you know what you're doing and have some clue as to what the ramifications are for your system. Finally, should I delete the binary package I built once it's installed or should I stash it somewhere? Stash it. I would run apt-get autoclean every once in a while to delete old versions of the package archives laying around (you'll keep the .debs for the installed packages with autoclean, you'll keep none of them if you use clean instead). - -- .''`. Paul Johnson [EMAIL PROTECTED] : :' : `. `'` proud Debian admin and user `- Debian - when you have better things to do than fix a system -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFAFd6aUzgNqloQMwcRAkavAKC35UB3xs8W+2Ffx6OvzzqBoyBL2ACeN2Zf SwswDQ6wdL6i+10qAfyp5zc= =4VuA -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: mixing stable and testing
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Mon, Jan 26, 2004 at 06:31:24PM -0800, David Rothenberger wrote: IIUC, that messages describes how to install binary packages. In fact, the whole thread seemed to focus on that. The Debian Reference (section 6.4.10) suggests that it's better to compile from source packages, so you don't end up upgrading libc, for example. Is this really true? Yes. You should be able to do this with apt, even. Just add lines for testing and/or unstable, but only the deb-src lines. Then, when you want to build a package from testing or unstable, as root... # apt-get -b build-dep package # apt-get -b source package This can get complex, and in cases where packages needed to build are in unstable, but not stable, it Just Won't Work. I would double-check http://www.backports.org/ and http://www.apt-get.org/ to make sure there isn't a source with prebuilt packages already first. - -- .''`. Paul Johnson [EMAIL PROTECTED] : :' : `. `'` proud Debian admin and user `- Debian - when you have better things to do than fix a system -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFAFd9kUzgNqloQMwcRApcjAJ4ryAX81YNKYQRQ3frJqi97DPfM8ACg1oMl m9rGQ8Yvq7pGEU1jXUGjrqI= =TCaC -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: mixing stable and testing debian packages.
* Louie Miranda [EMAIL PROTECTED] [030926 09:06]: Is it possible to mix stable and testing deb packages?. Theoreticaly yes, practicaly maybe. Many packages from testing depend on packages, which don't exist in stable, or on newer ones, so updating some components to testing may lead you very fast to a system, where many core-components come from testing. Additionaly you should know, that testing is not supported by Debians Security Team, so you should subscribe the debian-security-announce list, and keep an eye on vulnerable packages you have installed. It might even be possible, that you need to install a package from unstable, to fix a problem in testing fast. I mean, ex: I have libc6 2.2.5-11.5 and i want to make it libc6 2.3.1-1 As I said: libc6 is such a core component. You might want to search on www.apt-get.org or www.backports.org for packages from testing or unstable, backport to stable, before you start playing with your system. Now, im confused. Btw, if im going to put the testing distribution on /etc/apt/sources.list will my apt-* tools fixed this problem? And whats the correct configuration to get testing deb packages. If you tell apt a source for testing packages, it will be able to fix most problems. Due to the process of unstable becoming testing, it is possible, that a package in testing depends on an other package, which isn't part of testing yet. I mean like this: deb http://http.us.debian.org/debian stable main contrib non-free Whats the url and will i change stable to testing?. If you haven't found a backport, and still want packages from testing you can try the following: - add a new deb ... line to your /etc/apt/sources.list replacing stable with testing. - Since apt will take the newest package avaible you need to tell apt, that you prefer stable over testing. - So create a file /etc/apt/apt.conf containing the line: 'APT::Default-Release testing;' - run apt-get update to update you database of avaible packages - when you call apt-get it will install packages from stable and follow dependcies within stable - when you call apt-get install packagename/testing it will install the package from unstable, and tries to follow dependcies within stable - when you call apt-get -t testing apt-get will get everything from testing, use it with caution! Yours sincerely Alexander PS: All this is mentioned in the apt-howto. pgp0.pgp Description: PGP signature
Re: mixing stable and testing
On Sun, Sep 07, 2003 at 01:28:57AM -0400, Travis Crump wrote: # dpkg --force-remove-essential --force-remove-reinstreq --force-depends -r syslog-ng # dpkg -i metalog_0.7beta-3_i386.deb use force options with extreme care, but they are occasionally useful...(Only one of the force options is needed, but I am not sure which ;)) That did it! :) Thanks. -- Vikki RoemerHomepage: http://neuromancer.homelinux.com/ Registered Linux user #280021 http://counter.li.org/ Two things are infinite: the universe and human stupidity; and I'm not sure about the universe. -- A. Einstein PGP fingerprint: 0A3E 0AE4 CCD9 FF31 B4BB C859 2DE1 B1D8 5CE0 1578 Keyserver: http://pgp.mit.edu/ -BEGIN GEEK CODE BLOCK- Version: 3.12 GAT d-(?) s: a--- C(++) UL P+ L+++ E W++ N+ o? K- w--() O? M? V?(-) PS+(+++) PE(++) Y+ PGP++ t+@ 5 X-() R*(?) tv-- b+++(++) DI+ D--(?) G e-(*)+ h! r% x? --END GEEK CODE BLOCK-- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: mixing stable and testing
On Fri, Sep 05, 2003 at 01:14:02PM +1000, Russell Shaw wrote: In same directory: dpkg-source -x metalog_0.7beta-3.dsc cd metalog_0.7beta dpkg-buildpackage -us -uc -rfakeroot cd .. dpkg -i metalog_0.7beta-3_i386.deb Ok, I did all that, but when I try to run dpkg -i, I get the following output: neuromancer:~# dpkg -i metalog_0.7beta-3_i386.deb dpkg: regarding metalog_0.7beta-3_i386.deb containing metalog: syslog-ng conflicts with system-log-daemon metalog provides system-log-daemon and is to be installed. dpkg: error processing metalog_0.7beta-3_i386.deb (--install): conflicting packages - not installing metalog Errors were encountered while processing: metalog_0.7beta-3_i386.deb neuromancer:~# How can I uninstall syslog-ng and install metalog? dpkg won't let me uninstall syslog-ng before I install metalog because a plethora of packages depend on system-log-daemon. TIA. -- Vikki RoemerHomepage: http://neuromancer.homelinux.com/ Registered Linux user #280021 http://counter.li.org/ Yes, but every time I try to see things your way, I get a headache. PGP fingerprint: 0A3E 0AE4 CCD9 FF31 B4BB C859 2DE1 B1D8 5CE0 1578 Keyserver: http://pgp.mit.edu/ -BEGIN GEEK CODE BLOCK- Version: 3.12 GAT d-(?) s: a--- C(++) UL P+ L+++ E W++ N+ o? K- w--() O? M? V?(-) PS+(+++) PE(++) Y+ PGP++ t+@ 5 X-() R*(?) tv-- b+++(++) DI+ D--(?) G e-(*)+ h! r% x? --END GEEK CODE BLOCK-- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: mixing stable and testing
Vikki Roemer wrote: On Fri, Sep 05, 2003 at 01:14:02PM +1000, Russell Shaw wrote: In same directory: dpkg-source -x metalog_0.7beta-3.dsc cd metalog_0.7beta dpkg-buildpackage -us -uc -rfakeroot cd .. dpkg -i metalog_0.7beta-3_i386.deb Ok, I did all that, but when I try to run dpkg -i, I get the following output: neuromancer:~# dpkg -i metalog_0.7beta-3_i386.deb dpkg: regarding metalog_0.7beta-3_i386.deb containing metalog: syslog-ng conflicts with system-log-daemon metalog provides system-log-daemon and is to be installed. dpkg: error processing metalog_0.7beta-3_i386.deb (--install): conflicting packages - not installing metalog Errors were encountered while processing: metalog_0.7beta-3_i386.deb neuromancer:~# How can I uninstall syslog-ng and install metalog? dpkg won't let me uninstall syslog-ng before I install metalog because a plethora of packages depend on system-log-daemon. Maybe apt-get will work. cp metalog_0.7beta-3_i386.deb /var/cache/apt/archives apt-get install -t testing metalog -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: mixing stable and testing
Vikki Roemer wrote: On Fri, Sep 05, 2003 at 01:14:02PM +1000, Russell Shaw wrote: In same directory: dpkg-source -x metalog_0.7beta-3.dsc cd metalog_0.7beta dpkg-buildpackage -us -uc -rfakeroot cd .. dpkg -i metalog_0.7beta-3_i386.deb Ok, I did all that, but when I try to run dpkg -i, I get the following output: neuromancer:~# dpkg -i metalog_0.7beta-3_i386.deb dpkg: regarding metalog_0.7beta-3_i386.deb containing metalog: syslog-ng conflicts with system-log-daemon metalog provides system-log-daemon and is to be installed. dpkg: error processing metalog_0.7beta-3_i386.deb (--install): conflicting packages - not installing metalog Errors were encountered while processing: metalog_0.7beta-3_i386.deb neuromancer:~# How can I uninstall syslog-ng and install metalog? dpkg won't let me uninstall syslog-ng before I install metalog because a plethora of packages depend on system-log-daemon. TIA. # dpkg --force-remove-essential --force-remove-reinstreq --force-depends -r syslog-ng # dpkg -i metalog_0.7beta-3_i386.deb use force options with extreme care, but they are occasionally useful...(Only one of the force options is needed, but I am not sure which ;)) pgp0.pgp Description: PGP signature
Re: mixing stable and testing
On Mon, Sep 01, 2003 at 04:27:36PM -0800, Greg Madden wrote: You would need to setup a /etc/apt/preferences file, add testing to yor sources.list, and use pinning. Even so libc6 (upgrade) will be a depend on anythig from Testing. For what you want, it may be safer/easier to use 'apt-source' and build the few packages you want. If you are lucky there won't be any depends or only a couple that you will have to also build. You may need to run 'apt-get build-dep' in order to build your package, you would get an error message to this effect. Um, ok, another stupid newbie question: how do I build a package from source? I downloaded metalog's source, but the package won't build if I use dpkg -b metalog-dir -- it comes up with errors in the DEBIAN/control file. Am I going about it the right way? I've compiled programs before, I've just never compiled a *package*. TIA. -- Vikki RoemerHomepage: http://neuromancer.homelinux.com/ Registered Linux user #280021 http://counter.li.org/ Good day for a change of scene. Repaper the bedroom wall. PGP fingerprint: 0A3E 0AE4 CCD9 FF31 B4BB C859 2DE1 B1D8 5CE0 1578 Keyserver: http://pgp.mit.edu/ -BEGIN GEEK CODE BLOCK- Version: 3.12 GAT d-(?) s: a--- C(++) UL P+ L+++ E W++ N+ o? K- w--() O? M? V?(-) PS+(+++) PE(++) Y+ PGP++ t+@ 5 X-() R*(?) tv-- b+++(++) DI+ D--(?) G e-(*)+ h! r% x? --END GEEK CODE BLOCK-- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: mixing stable and testing
On Thu, Sep 04, 2003 at 01:36:21PM -0400, Vikki Roemer wrote: On Mon, Sep 01, 2003 at 04:27:36PM -0800, Greg Madden wrote: You would need to setup a /etc/apt/preferences file, add testing to yor sources.list, and use pinning. Even so libc6 (upgrade) will be a depend on anythig from Testing. For what you want, it may be safer/easier to use 'apt-source' and build the few packages you want. If you are lucky there won't be any depends or only a couple that you will have to also build. You may need to run 'apt-get build-dep' in order to build your package, you would get an error message to this effect. Um, ok, another stupid newbie question: how do I build a package from source? I downloaded metalog's source, but the package won't build if I use dpkg -b metalog-dir -- it comes up with errors in the DEBIAN/control file. Am I going about it the right way? I've compiled programs before, I've just never compiled a *package*. Definitely don't use 'dpkg -b'. This seems to be quite a common mistake, but that's for low-level use by debian/rules scripts only (and possibly experts doing very strange things, although I must say I can't remember ever needing it). Instead, install the devscripts and fakeroot packages and run 'debuild'. You probably want the -uc and -us flags too so that it doesn't prompt you for a GPG signature. Cheers, -- Colin Watson [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: mixing stable and testing
Vikki Roemer wrote: On Mon, Sep 01, 2003 at 04:27:36PM -0800, Greg Madden wrote: You would need to setup a /etc/apt/preferences file, add testing to yor sources.list, and use pinning. Even so libc6 (upgrade) will be a depend on anythig from Testing. For what you want, it may be safer/easier to use 'apt-source' and build the few packages you want. If you are lucky there won't be any depends or only a couple that you will have to also build. You may need to run 'apt-get build-dep' in order to build your package, you would get an error message to this effect. Um, ok, another stupid newbie question: how do I build a package from source? I downloaded metalog's source, but the package won't build if I use dpkg -b metalog-dir -- it comes up with errors in the DEBIAN/control file. Am I going about it the right way? I've compiled programs before, I've just never compiled a *package*. http://packages.debian.org/testing/admin/metalog.html Download source: http://ftp.debian.org/debian/pool/main/m/metalog/metalog_0.7beta-3.dsc http://ftp.debian.org/debian/pool/main/m/metalog/metalog_0.7beta.orig.tar.gz http://ftp.debian.org/debian/pool/main/m/metalog/metalog_0.7beta-3.diff.gz In same directory: dpkg-source -x metalog_0.7beta-3.dsc cd metalog_0.7beta dpkg-buildpackage -us -uc -rfakeroot cd .. dpkg -i metalog_0.7beta-3_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: mixing stable and testing
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Monday 01 September 2003 04:03 pm, Vikki Roemer wrote: Hi I was wondering if it's possible to run a few testing apps on a (otherwise) stable system. See, I'm running a server so I don't want to run testing, per se, but I want metalog and testing's gnupg (I'm having problems with stable's gnupg and my keyring, so I'm hoping going back to testing's gnupg will solve all my problems). So I was wondering if it would be possible to do that, considering that testing and stable have different libc versions. TIA, and apologies for the stupid newbie question. -- Vikki RoemerHomepage: http://neuromancer.homelinux.com/ Registered Linux user #280021 http://counter.li.org/ You would need to setup a /etc/apt/preferences file, add testing to yor sources.list, and use pinning. Even so libc6 (upgrade) will be a depend on anythig from Testing. For what you want, it may be safer/easier to use 'apt-source' and build the few packages you want. If you are lucky there won't be any depends or only a couple that you will have to also build. You may need to run 'apt-get build-dep' in order to build your package, you would get an error message to this effect. - -- Greg Madden Debian GNU/Linux -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE/U+QEk7rtxKWZzGsRAkNYAJsFII7hg1P+CVac4Omw6y06cPszmwCgnIMp cjpWB2cx7/aWp1jAOwsIfJE= =afRa -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
