libdb.so.3 woody upgrade failure-bug - Please help.
Hi - (Would a/the Debian developer with responsibility for the problem causing package please respond to this? Thank you! :) ) Thanks everyone for the great work on Debian! (This isn't a demand - just a plea for help!) I believe a serious problem exists: My requests are: Immediately: 1. Would someone please provide a reply email with a workaround for this bug? 2. Would someone please get this bug fixed? In the longer term: 3. Would someone care to develop a system to prevent this kind of bug? TIA! (I am posting this to debian-user so P -> W upgraders see proposed solutions. I am posting this to debian-devel so a developer who might be able to fix this becomes aware of this issue. I am posting this to debian-kde since any persons new to Debian via interest in installing the new KDE 2.2 will need to get at least a W/testing system installed in order to be able to install KDE 2.2 for Debian.) ** ** The detaiils: I believe a serious problem exists: There is a problem preventing the upgrade from Potato to Woody, and this problem appears to have existed for almost 3 weeks at least. I would think that such a case would be considered a severe bug. It is very bad to have _all_ people trying to install a clean W/Testing system to encounter such a bug. This bug probably requires many hours for each user to search for and implement a fix. I think it really hurts Debian, since it prevents people from trying out Woody/testing, putting a bottleneck in the debugging effort. I am not a Debian developer, I am trying to do this dist-upgrade. I do not know where to submit this as a bug, I hope (and am depending on you, dear reader) someone will get this submitted to the proper authority. In a larger sense, though: Would it be possible for such a bug (the submission of a package that breaks the P -> W upgrade) to be automatically detected, and prevent any such breaking package from going from Unstable -> W? Could a script be run against each .deb package, before it is moved from unstable to testing, that tries to do the upgrade from P -> W, and flags the package as unacceptable if the upgrade is unsuvessful, and notifies the package maintainer of that fact? ** ** The details: Some History: From: http://lists.debian.org/debian-user/2001/debian-user-200108/threads.html potato to sid upgrade error 32 broken pipe http://lists.debian.org/debian-user/2001/debian-user-200108/msg00019.html error message with "libdb.so.3" http://lists.debian.org/debian-user/2001/debian-user-200108/msg00269.html From: http://lists.debian.org/debian-user/2001/debian-user-200108/thrd5.html libdb.so.3 http://lists.debian.org/debian-user/2001/debian-user-200108/msg01986.html In essence, the problem is: 1. Starting from a basic Potato system (no tasks selected from tasksel during the install, and merely ~5MB of packages installed automatically at the end of the P install process): 2. Change /etc/apt/sources.list stable -> testing 3. apt-get update 4. apt-get dist-upgrade (or, (the latest suggestion on this problem) apt-get upgrade libdb2 , as shown here, suggested by: http://lists.debian.org/debian-user/2001/debian-user-200108/msg03112.html ) fails. ** ** Here's what I last tried: debian:/lib# l libdb* -rw-r--r--1 root root 237944 Aug 19 06:30 libdb-2.1.3.so lrwxrwxrwx1 root root 15 Aug 19 17:15 libdb.so.2 -> libdb1-2.1.3.so lrwxrwxrwx1 root root 14 Aug 19 17:15 libdb.so.3 -> libdb-2.1.3.so -rw-r--r--1 root root50848 Aug 19 06:30 libdb1-2.1.3.so lrwxrwxrwx1 root root 15 Aug 19 17:15 libdb1.so.2 -> libdb1-2.1.3.so debian:/lib# apt-get upgrade libdb2 . . Preparing to replace libreadline4 4.1-1 (using .../libreadline4_4.2-5_i386.deb) ... perl: error while loading shared libraries: libdb.so.3: cannot open shared object file: No such file or directory . . debian:/lib# l libdb* lrwxrwxrwx1 root root 15 Aug 19 18:31 libdb.so.2 -> libdb1-2.2.3.so lrwxrwxrwx1 root root 14 Aug 19 18:31 libdb.so.3 -> libdb.so.3.old -rw-r--r--1 root root50884 Jul 27 13:42 libdb1-2.2.3.so lrwxrwxrwx1 root root 15 Aug 19 18:31 libdb1.so.2 -> libdb1-2.2.3.so >From my user (not develpoer) level perspective it appears that maybe: The upgrade of libdb2 is failing because libdb.so.3 points to a non existent file at the time when libdb.so.3 must point to a real file. *
Re: libdb.so.3 woody upgrade failure-bug; & apt/preferences favoring testing
Thanks Anthony for your prompt & informative reply! --- Anthony Towns wrote: > > 1. Would someone please provide a reply email with a workaround for this > > bug? > > There are two db2 problems: > one is an upgrade ordering problem, > which is fixed by apt-get install'ing libc6 and db2 before anything > else (especially perl). > The other is a compatibility problem with > libdb.so.3 which is (was) a symlink to libdb2.so.something, and evidently > shouldn't've been. > Both these have been fixed recently, and are currently > being built for all arches. So, whwn can a person, wanting to, do a clean upgrade to Woody/testing? It sound like you are saying the upgrade ordering problem has a work around that can be applied now. I.e.: 1. Install base Potato. 2. Update /etc/sources.list: stable -> testing. 3. apt-get update 4. apt-get install libc6 5. apt-get install libdb2 before taking any other upgrade actions. Is that correct? But, how about the compatibility problem? Is it OK to today complete the upgrade by doing: 6. apt-get dist-upgrade ? Or, is it necessary to wait until the packages being built become available? If the latter, specifically: 1. When do you estimate these packages will become available? 2. If these packages are going to first appear in Unstable, and not migrate to testing for (as I understand it) at least 2 weeks of not having had any changes, then what, specifically, would be the procedure to accomplish this upgrade (without upgrading entirely to Unstable) once the packages become available in Unstable? (I.e., what is a complete, specific, procedure for getting the necessary packages installed?) (Would it involve something similar to the procedure in: http://lists.debian.org/debian-kde/2001/debian-kde-200108/msg00156.html quoted here (Of course, in the case of our task here, we would be using the packages relevent to this problem, not "kde", as in this following examle) ): * You'll have to install it from "unstable". A brief howto: + Add "unstable" lines to your /etc/apt/sources.list + Create a /etc/apt/preferences file that favours "testing", e.g. Package: * Pin: release a=testing Pin-Priority: 777 Package: * Pin: release a=unstable Pin-Priority: 333 + "apt-get -t unstable install kde" Note that the resulting system would be considered, er, unstable. * Also, what specific package(s) are we waiting for that we will need to install from unstable? Thanks! :) __ Do You Yahoo!? Make international calls for as low as $.04/minute with Yahoo! Messenger http://phonecard.yahoo.com/
Re: Potato to woody problem
Thanks dman for you response on this issue. ... But, ... (I'm in the process of learning about this now - would you please help me out?) --- dman <[EMAIL PROTECTED]> wrote: > On Mon, Aug 20, 2001 at 10:38:07AM -0400, Brian Schramm wrote: > | I changed the references in my apt/sources.list to point to woody. > | > | I then did a > | apt-get update > | apt-get install apt-utils debconf > | apt-get dist-upgrade > | > | When I did the apt-get install apt-utils debconf it told me to type Yes, > | do as I say! to upgrade the pearl system. I did that and now I keep > | getting a perl: error while loading shared libraries: libdb.so.3 > | > | How do I get by this? > > The correct solution to this is to > > apt-get install libdb2 > > since that package provides libdb.so.3. 1. Are you _sure_ installing the libdb2 package ___that W/testing currently points to___ will solve this problem? I think this problem has existed for several weeks, and no package that could fix it would be in W/t yet. (It would still be in unstable, if even there as of now.) See, for instance, the replies to: http://lists.debian.org/debian-devel/2001/debian-devel-200108/msg01318.html > (A quick search on packages.debian.org shows that) I did not get that result. My search for libdb.so.3 yielded: ** Debian package contents search results FILE PACKAGE lib/libdb.so.3 base/libc6 usr/lib/debug/libdb.so.3devel/libc6-dbg ** So, shouldn't it be libc6 is the package, not libdb2? Thanks for your effort. I'm in the process of learning about packages now. Would you please provide me some clarification on these two points? Your input on this mattter is greatly appreciated! :) __ Do You Yahoo!? Make international calls for as low as $.04/minute with Yahoo! Messenger http://phonecard.yahoo.com/
How to upgrade stable -> testing today, avoiding the libdb.so.3 bug.
Hi Ben,
Thanks for your great work!
I see you've got a very important bug marked closed:
libdb2 breakage when upgrading from potato to woody
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=107636&repeatmerged=yes
Would you kindly take a moment to give us the procedure of
how to upgrade stable -> testing today, avoiding the libdb.so.3 bug?
("today", so we are able to do this upgrade without
having to wait for updates to propagate from unstable to testing.)
Several list readers have been very helpful with replies on this topic
already.
(See:
libdb.so.3 woody upgrade failure-bug - Please help.
http://lists.debian.org/debian-user/2001/debian-user-200108/msg03557.html
Potato to woody problem
http://lists.debian.org/debian-user/2001/debian-user-200108/msg03612.html
)
I'm greatful for their work monitoring the lists and answering questions
(Thanks! :) ) and suspect they probably have the gist of it correct.
But, since there have been some, perhaps crucial, differences
in their suggestions, I think it could save many upgraders many hours
of some trial & error if you (someone who should be _certain_ about all
the details) would give us an exact procedure.
Your help here would enable the Debian community to put more time into
progress rather than re-searching & some trial & error.
Judging from the # of bugs I've seen you've closed I'm sure you're
very busy.
Would you please take a moment, though, to provide a short, but _specific_,
_complete_ procedure for accomplishing a s -> t upgrade, as of today?
(Something along the lines of:
1. Install a minimal Potato system (no packages selected from the
automatic Tasksel that runs during install. Merely the ~5 MB of
debs the installer puts in on its own. And don't put _anything_
else in.)
2. Change /etc/sources.list: stable -> testing .
3. apt-get update
4. - Now here's what I'm not sure _exactly_ what should come next.
Do we need to ftp down some debs first?
(And if so, put them where?
/var/cache/apt/archives ?)
Do we need to "dpkg -(something)" some specific packages?
(What exact package names?)
Do we need to "apt-get install" some specific packages?
(What exact package names? libc6? libdb2? dpkg?)
Or, would it be better to do an apt-get using preferences,
similar to what is described in:
http://lists.debian.org/debian-kde/2001/debian-kde-200108/msg00156.html ?
(And, if so, what are the exact steps & files to dl, configure, and install
using which commands?)
Do we then do an "apt-get dist-upgrade"
Something else???
)
Thank you so much for your help. :)
Also, when
1. by time (as in days) and
2. by process (perhaps as in "when the packages are automatically moved
from unstable to testing")
should we be able to skip the procedure you provided above,
and just do a straight "apt-get dist-upgrade"
to successfully accomplish the upgrade?
Lastly, to provide some foundation for understanding as we do the
above installation steps:
In just a few sentences, what was the cause(s) of the bug?
(Perhaps something like: "Libs __ were moved from package _ to ___,
and some dependencies were overlooked when that was initially done.")
Thanks again for your time and great work! :)
__
Do You Yahoo!?
Make international calls for as low as $.04/minute with Yahoo! Messenger
http://phonecard.yahoo.com/
Re: How to upgrade stable -> testing today, avoiding the libdb.so.3 bug.
Err, I think I would rather have titled that message: "How to accomplish a fresh install of today's Woody system." rather than "How to upgrade ...", because I the procedure I gave there (and want) is about doing a fresh install. Of course, the answer is relevant to doing an upgrade of an existing system, nontheless, I suppose. __ Do You Yahoo!? Make international calls for as low as $.04/minute with Yahoo! Messenger http://phonecard.yahoo.com/
Re: How to upgrade stable -> testing today, avoiding the libdb.so.3 bug.
Thanks Ben for your prompt reply! :) --- Ben Collins <[EMAIL PROTECTED]> wrote: > Actually, to do a fresh install of woody, you download the woody > boot-floppies, and install woody. That's pretty simple, right? :) > > I don't suggest upgrading to woody yet. Wait a day or two for the new > glibc and libdb2 to make their way into testing. Yes, dl'ing and installing woody directly would be great, if it would work. In fact, that is what I tried about a week ago, but I found, IIamC, apparently, a crucial file was missing, and thus that option is not at all possible. Perhaps I am wrong about this, but it seems that the "base" file is not present on the ftp site, and that without that file it is impossible to do a direct installation of testing. *** *** Looking in http://http.us.debian.org/debian/dists/testing/main/disks-i386/current the "base" file is not present, whereas it is present in http://http.us.debian.org/debian/dists/potato/main/disks-i386/current/ Also http://http.us.debian.org/debian/dists/potato/main/disks-i386/current/README.txt mentions base2_2.tgz, whereas http://http.us.debian.org/debian/dists/testing/main/disks-i386/current/README.txt doesn't. I am doing the install starting from floppies. This works for installing stable, using base2_2.tgz and drivers.tgz, and dl'ing the rest over a modem. I tried doing a "woody" install, using the woody files, but I strongly recall that the installer program asked for the (nonexistent) base image file, so there was no way to complete the install.. Perhaps I am not recalling my experience correctly, and/or have made an error, but it was because of that problem that I had to, for the goal of getting a testing system installed, go back to doing a stable install, then trying to upgrade this to testing. :( *** *** So, that is why I am asking you about how to do the upgrade, not a direct testing install. :) I had tried to be very precise in my questions in the first post of this thread. I think all those questions are important, and I would greatly appreciate it if you would take a few minutes to answer them. I do think your effort would be repaid many times over in saving time for the Debian community, especially for those trying to install a fresh working woody system today. :) One of the __main reasons__ for writing the request was to enable people to get a woody system up _now_. I.e., exactly to _avoid_ having to "Wait a day or two for the new glibc and libdb2 to make their way into testing." 0. Do you think it will only take a day or two for the files to get into testing? My understanding (gleaned from I don't recall where) is that it takes two _weeks_ for the files to be moved to testing from unstable, correct? I know you said "I don't suggest upgrading to woody yet." 1. Why is that? 2. Would you please, nonetheless, answer the questions in my original mail, and allow us the possibility of doing the upgrade now, guided by the (likely) most knowledgeable authority on the topic (you), should we prefer to try doing a fresh woody install now? :) Thank you very much for reconsidering your respone. :) __ Do You Yahoo!? Make international calls for as low as $.04/minute with Yahoo! Messenger http://phonecard.yahoo.com/
Erroneous out of space msg & fs corruption on W>S then KDE install
During a KDE install I get an err msg saying out of disk space. There was plenty of space on the disk, and I seem to recall seeing a similar msg on -user, -kde or -devel in about the past day. So I just wanted to post this in case others start to see a problem like this. I have a 3 week old woody system with KDE. I decided to upgrade it to Sid so I could get the "kde" metapackage, because woody only had the "kdebase" package. As root I did: apt-get update apt-get upgrade which went fine. I changed /etc/apt/sources.list to point to sid apt-get update apt-get dist-upgrade At some point here I got: Preparing to replace kdelibs3 4:2.2.2-5 (using .../kdelibs3_4%3a2.2.2-11_i386.deb) ... Unpacking replacement kdelibs3 ... Preparing to replace ark 4:2.2.2-5 (using .../ark_4%3a2.2.2-8.1_i386.deb) ... Unpacking replacement ark ... Errors were encountered while processing: /var/cache/apt/archives/kdelibs3-bin_4%3a2.2.2-11_i386.deb E: Sub-process /usr/bin/dpkg returned an error code (1) debian:~/upgrade# exit I continued on: Script started on Thu Jan 31 02:09:19 2002 debian:~/upgrade# exitapt-get dist-upgrade Reading Package Lists... 0% Reading Package Lists... 0% Reading Package Lists... 1% Reading Package Lists... Done Building Dependency Tree... 0% Building Dependency Tree... 0% Building Dependency Tree... 0% Building Dependency Tree... 50% Building Dependency Tree... 50% Building Dependency Tree... Done You might want to run `apt-get -f install' to correct these. Sorry, but the following packages have unmet dependencies: kdelibs3: Depends: kdelibs3-bin but it is not installed or kdelibs-bin E: Unmet dependencies. Try using -f. debian:~/upgrade# apt-get dist-upgrade [EMAIL PROTECTED] [EMAIL PROTECTED] Reading Package Lists... 0% Reading Package Lists... 100% Reading Package Lists... Done Building Dependency Tree... 0% Building Dependency Tree... 0% Building Dependency Tree... 50% Building Dependency Tree... 50% Building Dependency Tree... Done Correcting dependencies... Done Calculating Upgrade... Done The following NEW packages will be installed: kdelibs3-bin libglib1.3-12 libslp1 35 packages upgraded, 3 newly installed, 0 to remove and 0 not upgraded. 63 packages not fully installed or removed. Need to get 0B/43.4MB of archives. After unpacking 1568kB will be used. Do you want to continue? [Y/n] y I continued on again: Preparing to replace kdebase-doc 4:2.2.1.0-6 (using .../kdebase-doc_4%3a2.2.2-13_all.deb) ... Unpacking replacement kdebase-doc ... Errors were encountered while processing: /var/cache/apt/archives/kdebase-libs_4%3a2.2.2-13_i386.deb E: Sub-process /usr/bin/dpkg returned an error code (1) debian:~/upgrade# apt-get -f dist-upgrade[2P dist-upgrade Reading Package Lists... 0% Reading Package Lists... 0% Reading Package Lists... 1% Reading Package Lists... Done Building Dependency Tree... 0% Building Dependency Tree... 0% Building Dependency Tree... 0% Building Dependency Tree... 50% Building Dependency Tree... 50% Building Dependency Tree... Done You might want to run `apt-get -f install' to correct these. Sorry, but the following packages have unmet dependencies: kdebase: Depends: kdebase-libs (= 4:2.2.2-13) but 4:2.2.1.0-6 is installed konqueror: Depends: kdebase-libs (= 4:2.2.2-13) but 4:2.2.1.0-6 is installed E: Unmet dependencies. Try using -f. debian:~/upgrade# apt-get dist-upgrade [EMAIL PROTECTED] dist-upgrade install Reading Package Lists... 0% Reading Package Lists... 100% Reading Package Lists... Done Building Dependency Tree... 0% Building Dependency Tree... 0% Building Dependency Tree... 50% Building Dependency Tree... 50% Building Dependency Tree... Done Correcting dependencies... Done The following extra packages will be installed: kdebase-libs 1 packages upgraded, 0 newly installed, 0 to remove and 19 not upgraded. 81 packages not fully installed or removed. Need to get 0B/1649kB of archives. After unpacking 483kB will be used. Do you want to continue? [Y/n] y (Reading database ... 24526 files and directories currently installed.) Preparing to replace kdebase-libs 4:2.2.1.0-6 (using .../kdebase-libs_4%3a2.2.2-13_i386.deb) ... Unpacking replacement kdebase-libs ... Setting up update (2.11-4) ... Setting up cpio (2.4.2-40) ... and that worked fine. I then started KDE & web browsed, that worked fine. I checked my df & had about 280MB free I then did apt-get install kde It said 0 packages upgraded, 53 newly installed, 0 to remove and 19 not upgraded. Need to get 17.0MB of archives. After unpacking 52.8MB will be used. Do you want to continue? [Y/n] y I think this process had some problem I can't recall. I think I then continued again, and here is where I got the error msg about being out of space, which should not have occurred since the estim
KDE-Debian HowTo for KDE2 & Debian3=Woody X86. Ver 0.22
It can be found here: http://lists.debian.org/debian-kde/2002/debian-kde-200202/msg00097.html This howto is in an early release form: It is not complete, but contains much useful information. I hope to update this once or twice per week, and will post it to the debian-kde list. :) __ Do You Yahoo!? Send FREE Valentine eCards with Yahoo! Greetings! http://greetings.yahoo.com
Mixing Debian releases the easy way - HowTo - questions
I'm trying to put together a howto, and could use your input. I've assembled a procedure, and some references- do you have any suggestions? My persoal goal is to have the procedure to run a Woody system, with all the latest KDE packages pulled from Sid. But, this procedure could be used for many packages other than KDE. The 1st level goal here is to have a way to: install a Woody system set up some method, such as APT::Default-Release "testing"; or pinning Use that method to pull the "kde" metapackage, "kde", from unstable Have a way to do apt-get update; apt-get upgrade that will get everything upgraded from their proper locations, ie: upgrade all the installed & depended kde packages from unstable, as appropriate upgrade any other woody packages from woody, as appropriate What is the best, or at least very good, (simple to comprehend, setup, do; as powerful as necessary; reliable) way to do this? I am particularly concerned about ensuring apt-get upgrade works properly, and simply - ie, not having extra-normal things to do for the person doing the upgrade. >From the following references section, it seems that the immediately following procedure might do this, but I have some concerns: /etc/apt/apt.conf gets the following line: APT::Default-Release "testing"; [Note: On my several months old Woody install, in /etc/apt I have no file called apt.conf . I do have there a directory apt.conf.d that has one file in it: 70debconf In this case, what I exactly need to do is create the file /etc/apt/apt.conf, and put in it only the following line, correct? APT::Default-Release "testing";] And, to install a package do: apt-get install /unstable [in my case: apt-get install kde/unstable] is a very simple way to get the correct packages installed. My main as yet unanswered concern is: Will that also do the upgrade of packages properly? (The asnwer to that was not clear to me. The question may have been triggered by comments from Chris Halls, below.) That's my main question. What's the answer? [The "Mixing Debian releases the easy way" HowTo will be a component of my KDE-Debian HowTo for KDE2 & Debian3=Woody X86. Recent version here: http://lists.debian.org/debian-kde/2002/debian-kde-200202/msg00097.html Gustavo: A definitive version of this topic should also probably be put into the APT HowTo: http://www.debian.org/doc/manuals/apt-howto/index.en.html You could probably do a whole chapter on pinning & APT::Default-Release and how to pull packages, and apt-get upgrade properly, replacing your current section 3.7. :) ] Robert & Donald: Please see my questions to you, below. References (these are slightly edited, mostly deletions for conciseness): == == From: Grant Bowman <[EMAIL PROTECTED]> Subject: Pinning Unstable: Woody use of Evolution For all those that are using Woody but would like to sometimes run a few packages from Sid, this fix works like a charm. /etc/apt/preferences Package: * Pin: release a=unstable Pin-Priority: 50 /etc/apt/sources.list deb http://http.us.debian.org/debian unstable main contrib non-free What will these lines do? Pinning the priority of unstable to 50 makes it so that these packages are never automatically selected for upgrade. The sources.list line is needed so that packages that are not in woody are installed with `apt-get evolution` (for example). Dependencies are handled correctly and the system remains on Woody packages with the exceptions of the explicitly loaded ones. === From: Christoph Martin <[EMAIL PROTECTED]> Subject: apt-show-versions apt-show-versions is a script which eases maintenance of mixed stable/testing or testing/unstable systems. While beeing able to update the packages from your *main* distribution with apt-get upgrade it is quite difficult to do the same for the *not-main* packages. While you can use the pinning feature of apt if these are only a few it is quite annoying to put all the package names in apt/preferences which should be pinned. Like in one of my installation where I have 247 packages from stable and 229 from testing. Try apt-show-versions | fgrep /testing | wc to see how many packages you have from testing or apt-show-versions -u to see a list of packages which are upgradeable either to stable or testing or unstable or apt-get install `apt-show-versions -u -b | fgrep unstable` to upgrade all unstable packages to their newest versions. == From: Robert McQueen <[EMAIL PROTECTED]> Subject: Mixing Debian releases the easy way As w
Re: Mixing Debian releases the easy way - HowTo - questions
--- tluxt <[EMAIL PROTECTED]> wrote: > I am particularly concerned about ensuring apt-get upgrade works properly, > and simply - ie, > not having extra-normal things to do for the person doing the upgrade. > > > From the following references section, it seems that the immediately > following procedure might do this, but I have some concerns: > > /etc/apt/apt.conf gets the following line: > APT::Default-Release "testing"; > ... > > And, to install a package do: > apt-get install /unstable > [in my case: > apt-get install kde/unstable] > > is a very simple way to get the correct packages installed. > > My main as yet unanswered concern is: > Will that also do the upgrade of packages properly? I could have been clearer there. I might better have said: Will the above procedure allow upgrades to be done properly by doing: apt-get update apt-get upgrade [Also: will apt (or other) programs that show what programs are installed on the system work properly with the above procedure?] > That's my main question. What's the answer? __ Do You Yahoo!? Send FREE Valentine eCards with Yahoo! Greetings! http://greetings.yahoo.com
Re: Mixing Debian releases the easy way - HowTo - questions
Donald - Thanks! :)I hope you don't mind me forwarding this to Chris and the list. (If I have correctly interpreted your disposition, I suspect you don't mind.) He did some interesting tests that IIRC he just sent to everyone, so IIRC you got a copy from him too. I thought he might find your comments informative. See also other comments & questions below. (I'd suggest you send your answers to the list, so everyone can benefit from them. :) ) Chris - I thought you might find some of this info useful. --- "Donald R. Spoon" <[EMAIL PROTECTED]> wrote: > tluxt wrote: > == > > > > Re: How pull packages from unstable to a Woody system? > > From: "Donald R. Spoon" <[EMAIL PROTECTED]> > > > > The subject of "pinning" has been discussed several times late last year ... > OOPS! This next paragraph should have been #7. > > > 6. If you want to install a SPECIFIC package from "unstable" just run > > "apt-get -t unstable install ". In the case of > > installing kghostview from unstable the command would be "apt-get -t > > unstable install kghostview". > > > > There are other methods and other recommended "Pin-Priority" numbers > > discussed in the previously mentioned messages. You might want to > > review them to see all your options. All I can say is this particular > > method has worked quite well for me during the last 2-3 months. > > > > Donald: Does this do the "apt-get upgrade" properly? > > > == > > Yes. It will "upgrade" and EXISING package on your system plus any > dependencies. IT WILL NOT INSTALL A PACKAGE THAT ISN'T ALREADY > INSTALLED! There is one 'caveat"...see the NOTE below. Hmm. So, that looks problematic, if (as I guess I am) this howto is being written for someone not highly familiar with using the apt tools. What do you suggest be done for that case (or is that just a hopeless case, might as well not bother to write a howto for such a person)? > NOTE: I have occasionally had some problems with a few KDE packages > that have made it into "testing" but still depended on some external > packages remaining in "unstable". These would not install untill I > installed the required dependencies from "unstable". What is the kind of error message you got that let you know there was such a problem? Then, how did you solve it? > The current > pinning system will treat the "source" of a package being upgraded as > the "source" for meeting any dependencies. As long as you keep your KDE > stuff current from "unstable" then you should be OK on this account. I > have noticed some "drift" over time in this regard, and you have to keep > on top of it. In this context, please define what you mean by 'drift'. How does one 'keep on top of it'? > > IMHO, there is "no way" you will ever get to where you want to be for > the following reasons: What do you mean by 'where you want to be'? If you are right, then what would you suggest is the plan of action that should be followed? > > 1. "Woody" (testing) is undergoing CONSTANT changes! I recently did an > "apt-get dist-upgrade" from Potato to Woody and it installed about 200+ > new packages. When I do my almost daily "apt-get upgrade" on my system, > I have noticed anywhere from 20 to 60 "new" packages being installed. > That is almost EVERY DAY (most certainly EVERY WEEK), and is a > SIGNIFICANT portion of the ENTIRE INSTALL!! There is still a LOT of > "tweaking" going on. This includes the "apt-get" program! The bottom > line is anything you put into your "HOWTO" will be outdated quite soon. > This situation will NOT change due to the basic philosophy of Debian > development. Woody, despite having a name, IS NOT THE "OFFICIAL" > RELEASE yet, and will have rough edges. > >2. A good understanding of just how the APT series of packages work > and how the relate to dpkg and dselect will solve most install problems. > It does some things very well, but it certainly DOESN'T cover every > possibility that comes up. If you limit your "HOWTO" to just apt-get > procedures, then you are doing the equivalent of tying one arm behind > your back. I frequently find myself going into dselect to get some info > on what has caused a "hang" or other problem with an install. Over th
John "Maddog" Hall for the Annual Linux Showcase (ALS) 11/8-10 (video)
Check it out: http://168.103.109.171/ Thanks to Bay Area Debian, Linux & other volunteers for helping. Now, hop on a plane & get yourself out here! :) __ Do You Yahoo!? Find a job, post your resume. http://careers.yahoo.com
Come to ALS Debian BOF Thurs 11/8 6-8 PM Oakland, CA, USA, Earth
The (San Francisco) Bay Area Debian group invites you to attend the Debian BOF at the Annual Linux Showcase technical converence. This is the largest technical Linux conference in the USA (says Maddog). The technical talks and exhibits are all free. http://www.linuxshowcase.com/bofschedule.html The meeting format is open. There is no planned talk at this time. It would be nice to hear progress reports on Woody, and other projects. A discussion of new ways to improve or grow Debian would be good also. So, hop on a plane & get on out here! :) __ Do You Yahoo!? Find a job, post your resume. http://careers.yahoo.com
Error upgrading to woody: mv: cannot create file `/etc/exim/exim.conf'
Starting from a (IIRC) rather basic potato system, I did (essentially): change sources.list to point to testing apt-get update apt-get dist-upgrade I got the following error after much stuff had installed: Preparing to replace exim 3.12-10 (using .../archives/exim_3.31-1_i386.deb) ... mv: cannot create regular file `/etc/exim/exim.conf': No such file or directory dpkg: error processing /var/cache/apt/archives/exim_3.31-1_i386.deb (--unpack): subprocess pre-installation script returned error exit status 1 Starting MTA: exim. Preparing to replace gettext-base 0.10.35-13 (using .../gettext-base_0.10.39-2_i386.deb) ... Unpacking replacement gettext-base ... Selecting previously deselected package groff-base. Unpacking groff-base (from .../groff-base_1.17-3_i386.deb) ... Moving /etc/tmac.man.local to /etc/groff/man.local. Replacing files in old package groff ... Errors were encountered while processing: /var/cache/apt/archives/exim_3.31-1_i386.deb E: Sub-process /usr/bin/dpkg returned an error code (1) debian:/var/cache/apt# In fact, the directory: /etc/exim does not exist. I found Subject: Re: dist-upgrade from stable to testing http://lists.debian.org/debian-user/2001/debian-user-200108/msg02377.html Date: Tue, 14 Aug 2001 08:35:28 -0500 Which said: " On Tue, Aug 14, 2001 at 12:20:57AM -0600, Phil Reardon wrote: > On Monday 13 August 2001 11:36 pm, John Galt wrote: > > mkdir /etc/exim then rerun apt-get dist-upgrade... You won't have to > > re-download the 166M, BTW. > > > > On Mon, 13 Aug 2001, Phil Reardon wrote: > > >After apt-get update, apt-get dist-upgrade to testing, I got a successful > > >download of 166 MB. But during the install/config, I saw this message: > > > > > >mv: cannot create regjular file '/etc/exim/exim.conf' ; No such file or > > >directory. > > > .(stuff removed) > > Thanks, John: > > I tried creating the exim directory and even did a touch exim.conf there. > Then I did apt-get dist-upgrade again and it complained of unmet dependencies > and recommended apt-get -f install. I did that too, and then things > proceeded okay. I think I have Woody now! This is also fixed in exim 3.32-1 in unstable, by the way. exim (3.32-1) unstable; urgency=low [...] * debian/preinst: create /etc/exim before moving exim.conf (Closes: #106659, #107657) [...] -- Mark Baker <[EMAIL PROTECTED]> Wed, 8 Aug 2001 23:34:04 +0100 -- Colin Watson [EMAIL PROTECTED] " In my /v/c/a/a I have: @debian:/var/cache/apt/archives$ ls -al exim* -rwxr-xr-x1 root root 650710 Jun 9 19:45 exim_3.12-10.1_i386.deb -rwxr-xr-x1 root root 650572 May 2 2000 exim_3.12-10_i386.deb -rwxr-xr-x1 root root 746472 Apr 11 17:28 exim_3.22-4_i386.deb -rwxr-xr-x1 root root 747228 Jul 18 16:50 exim_3.31-1_i386.deb -rwxr-xr-x1 root root 748988 Aug 14 17:30 exim_3.32-2_i386.deb @debian:/mnt/hda11/var/cache/apt/archives$ My Question: I don't know enough about Debian to know if this is a bug - would you please enlighten me? The msg from CW said, on 8/14, that exim 3.32-1 fixes this. I have exim 3.32-2 in my cache. Q: Since it is over 2 weeks past 8/14, shouldn't my dist-upgrade be using 3.32, which, presumably, has this bug fixed? Why is dist-upgrade using 3.31-1? Now, I did try a dist-upgrade to unstable a week or two ago, and perhaps that's how 3.32-2 got there. (That dist-upgrade was on another system.) I thought that after less than about 2 weeks the packages migrate from unstable to testing. So, that should be done now, therefore. Also, if this _is_ a bug that's not submitted yet, I don't know enough yet about the bug tracking system, etc., to properly submit this. So, I hope _you_, dear reader, will submit this bug to the system, if it is indeed a current, non-submitted bug. Thanks! :) __ Do You Yahoo!? Get email alerts & NEW webcam video instant messaging with Yahoo! Messenger http://im.yahoo.com
Re: Error upgrading to woody: mv: cannot create file `/etc/exim/exim.conf'
--- "der.hans" <[EMAIL PROTECTED]> wrote: > That does fix it. Ran into it somewhere the other day. > > Yes, this is a bug. Thanks for the confirmation. I have just done that fix, and I think (after having several more errors, but just redoing "apt-get dist-upgrade" several times), I may have succeeded in getting upgraded to woody. (At least my final a-g d-u did nothing but return me to a prompt, so I guess it thinks there is nothing left to do. -- I hope that's a positive result. :~? ) > Look at at reportbug for how to submit them. > > Look at http://bugs.debian.org/ for info on bugs for a > particular package. > > At http://bugs.debian.org/exim you'll find bug #108237 under "Important bugs > - resolved" which is a report for the bug you found. You'll also that bug > #109948 under "Minor bugs - resolved" is actually for the same prob. > > I think most people will agree the most important thing is to report the bug > and make sure the subject is descriptive so that others running into the bug > see that it's already been reported. > > BTW, it's great that you researched the prob and found the solution on your > own. Thanks for the info about how to submit the bugs. But, the point I was trying to make with my prior message is that I don't currently have the time to do the learning involved to determine if the fact I'm getting this error is indeed a bug, given that a previious poster said this should have been resolved by now. So, I'm hoping that someone who is responsible for this kind of error will see this and be able to use my info to determine if indeed a bug still exists currently. I hope this helps someone. Thanks! :) __ Do You Yahoo!? Get email alerts & NEW webcam video instant messaging with Yahoo! Messenger http://im.yahoo.com
HowTo install X on Woody today - Please help, thanks :)
What is the way to properly install X (to prepare for KDE) on a Woody system today? (I have just done an upgrade to W from a basic (no X) potato.) On the Woody page it says: "Expected major upgrades, by the time woody releases, include . . . XFree86 4.0" Does that mean woody has _only_ X4, or both X3 & X4? Should I use tasksel, or apt-get? If apt-get, what command would I use to find out what package name to use to apt-get X? I've seen notes on debian-x list about problems with the current X packages: new XFree86 packages may be stalled temporarily http://lists.debian.org/debian-x/2001/debian-x-200108/msg00100.html ALERT: XFree86 4.1.0-3 maintainer scripts hosed; please wait for 4.1.0-4 http://lists.debian.org/debian-x/2001/debian-x-200108/msg00126.html Also, IIRC, on the KDE list it was mentioned that the tasksel, or task packages, (like the X task?) were being currently redone in woody, and may not work properly right now. Is that correct? (And if so, shouldn't that info be on the woody page: http://www.debian.org/releases/testing/ ?) "" Subject: ALERT: XFree86 4.1.0-3 maintainer scripts hosed; please wait for 4.1.0-4 From: Branden Robinson <[EMAIL PROTECTED]> Date: Thu, 30 Aug 2001 22:12:40 -0500 Folks might want to wait for 4.1.0-4. I'm preparing it now. Several bugs have already been filed; no one needs to add to them. The problem is understood, and the fix has been written and tested. If you already have 4.1.0-3 installed successfully, there is nothing to worry about. "" If I do _not_ want to wait for it to move from unstable to testing, what do I do? Can I just dl the 4.1.0-4 deb and force it to install? How? Or, would I be better off getting the 4.1.0-3 instaalled? If so, how would I do that? Is the tasksel program working for install of the complete X system? Does Woody have only X 4, or also X 3 packages? Wouldn't it be a great idea to put some notes about the status of the highly important packages (like X) on the Woody install page: http://www.debian.org/releases/testing/ so that people wanting to try woody wouldn't have to search through the mail lists for important info like this? If so, who should that be pointed out to: the package developer, or the person maintaining the woody web page? Thanks! :) __ Do You Yahoo!? Get email alerts & NEW webcam video instant messaging with Yahoo! Messenger http://im.yahoo.com
Re: HowTo install X on Woody today - Please help, thanks :)
Thanks James! - A few follow ups: --- "James A. Treacy" <[EMAIL PROTECTED]> wrote: > On Tue, Sep 04, 2001 at 01:52:59AM -0700, tluxt wrote: > > What is the way to properly install X (to prepare for KDE) on a Woody > > system today? > > > 2. apt-get update && apt-get install x-window-system Tasksel is broken under woody, I found. It won't install any X option - basic or complete. What specifically should go in place of "x-window-system" above? (I looked on http://packages.debian.org/testing/x11/ , but - Wow! Too much raw data!) What commands does one use to get what tasksel refers to as the most comprehensive set of packages for the X install? > > If I do _not_ want to wait for it to move from unstable to testing, > > what do I do? > wait, grab the packages from unstable, or move to unstable. If the packages have not yet migrated to woody, but I wish to try them anyway on woody, how can I find out myself (without being told) what packages I'd need to get from unstable to do the X install? what's the/a good way to dl all those needed X packages from unstable? apt-get -d .. ?(And, how do I tell it to get from Un, not Te?) > > Can I just dl the 4.1.0-4 deb and force it to install? > > How? > > > Use dpkg -i. See man dpkg for details. > > > Or, would I be better off getting the 4.1.0-3 instaalled? > > If so, how would I do that? > > > Read the debian-x mailing list archives, or ask there. Ok, debian-x readers - any suggestions? > > Wouldn't it be a great idea to put some notes about the status > > of the highly important packages (like X) on the Woody install page: > > http://www.debian.org/releases/testing/ > > so that people wanting to try woody wouldn't have to search through > > the mail lists for important info like this? This is an example of how the Debian Testing page http://www.debian.org/releases/testing/ is way behind on providing essential info about the current issues in getting a testing system up & running. :( I know this is a volunteer organization. I'd like to encourage someone who is able to spend .5 or 1 hour to write a quick "Installing debian testing HowTo" or FAQ that would enable people to avoid having to search the lists & docs for hours on end for info about how to just get a basic X system up on Woody! I think such a document would be a big help in speeding up the development of Debian testing! Also, is the debian-testing list broken? I sent the original message in this thread to that list, but the mailing list page http://lists.debian.org/devel.html lists no messages there later than April! :( Thanks for everyones' great work! :) __ Do You Yahoo!? Get email alerts & NEW webcam video instant messaging with Yahoo! Messenger http://im.yahoo.com
Re: HowTo install X on Woody today - Please help, thanks :)
Thanks again! - A few more questions: (Essentially: x-window-system isn't right?) --- "James A. Treacy" <[EMAIL PROTECTED]> wrote: > On Tue, Sep 04, 2001 at 06:45:29PM -0700, tluxt wrote: > > --- "James A. Treacy" <[EMAIL PROTECTED]> wrote: > > > On Tue, Sep 04, 2001 at 01:52:59AM -0700, tluxt wrote: > > > > What is the way to properly install X (to prepare for KDE) on a Woody > > > > system today? > > > > > > > 2. apt-get update && apt-get install x-window-system > > > > Tasksel is broken under woody, I found. It won't install any X option - > > basic or complete. > > > The command above does not use tasksel. The x-window-system package is > simply a dummy package that depends on the packages providing X. I wasn't as clear as possible. I knew the above was an apt command, not tasksel. That was a comment about my experience with tasksel. I have tried: apt-get update apt-get install x-window-system My result was: debian:/var/cache/apt# apt-get install x-window-system Reading Package Lists... Done Building Dependency Tree... Done E: Couldn't find package x-window-system So, what's the source of the problem? Is "apt-get install x-window-system" not the correct command? Or, something else? == Previously I had tried tasksel, on both of the X selections. Here is the result for one attempt: debian:/var/cache/apt# tasksel Building Dependency Tree... Done Package task-x-window-system has no available version, but exists in the database. This typically means that the package was mentioned in a dependency and never uploaded, has been obsoleted or is not available with the contents of sources.list E: Package task-x-window-system has no installation candidate == > > What commands does one use to get what tasksel refers to as the > > most comprehensive set of packages for the X install? > > > 'apt-cache show x-window-system' and look at the Depends line. > Installing all those packages will do the same thing as (a properly > working) x-window-system package will. 'apt-cache show x-window-system' said something like (IIRC): not found There is no file starting "x-window..." in my /v/c/a/a. For your reference: == debian:/var/cache/apt/archives# ls x* xaw3dg_1.3-6.9potato1_i386.deb xbase-clients_3.3.6-11potato32_i386.deb xbase-clients_4.0.3-4_i386.deb xbooks_3.3.6-1_all.deb xcontrib_3.3.3.1-0.1_i386.deb xdm_3.3.6-11potato32_i386.deb xext_3.3.6-11potato32_i386.deb xf86setup_3.3.6-11potato32_i386.deb xfonts-100dpi_3.3.6-2_all.deb xfonts-100dpi_4.0.3-4_all.deb xfonts-75dpi_3.3.6-2_all.deb xfonts-75dpi_4.0.3-4_all.deb xfonts-base_3.3.6-2_all.deb xfonts-base_4.0.3-4_all.deb xfonts-cjk_3.3.6-2_all.deb xfonts-cyrillic_3.3.6-2_all.deb xfonts-pex_3.3.6-2_all.deb xfonts-scalable_3.3.6-2_all.deb xfonts-scalable_4.0.3-4_all.deb xfree86-common_3.3.6-11potato32_all.deb xfree86-common_4.0.3-4_all.deb xfree86-common_4.1.0-2_all.deb xfs_3.3.6-11potato32_i386.deb xlib6g-dev_3.3.6-11potato32_i386.deb xlib6g_3.3.6-11potato32_i386.deb xlib6g_4.0.3-4_all.deb xlib6g_4.1.0-2_all.deb xlibmesa3_4.0.3-4_i386.deb xlibs_4.0.3-4_i386.deb xlibs_4.1.0-2_i386.deb xmanpages_3.3.6-2_all.deb xmh_3.3.6-11potato32_i386.deb xnest_3.3.6-11potato32_i386.deb xpm4g_3.4k-5_i386.deb xproxy_3.3.6-11potato32_i386.deb xprt_3.3.6-11potato32_i386.deb xserver-common_3.3.6-11potato32_i386.deb xserver-common_4.0.3-4_i386.deb xserver-sis_0.990907-2_i386.deb xserver-svga_3.3.6-11potato32_i386.deb xserver-vga16_3.3.6-11potato32_i386.deb xserver-xfree86_4.0.3-4_i386.deb xsm_3.3.6-11potato32_i386.deb xterm_3.3.6-11potato32_i386.deb xutils_4.0.3-4_i386.deb xvfb_3.3.6-11potato32_i386.deb xviddetect_0.3-4_all.deb debian:/var/cache/apt/archives# exit == > > what's the/a good way to dl all those needed X packages from unstable? > > apt-get -d .. ?(And, how do I tell it to get from Un, not Te?) > > > To get the packages, try: > s/stable/unstable/ in /etc/apt/sources.list > apt-get update > apt-get install x-window-system > If the x-window-system is broken, then > apt-get install x-window-system-core lbxproxy libdps1-dbg \ > libdps-dev libxaw7-dbg libxaw7-dev proxymngr twm xfs xfwp \ > xlibmesa3-dbg xlibmesa-dev xlibosmesa3-dbg xlibosmesa-dev \ > xlibs-dbg xlibs-dev xnest xprt xspecs xterm xvfb > Make sure you then undo the changes to /etc/apt/sources.list > and apt-get update when done. I'm gonna hold off on doing this till I get your reply on the above. > > > This is an example of how the Debian Tes
What's the best way to pull a package from unstable to a Woody system?
I want a method that will not cause apt to get confused about this and other sw once I install the Sid package. Specifically: I have kghostview installed on the woody system. That sw has a malfunction, and from the bug report info on kghostview I see that Sid has a newer package that might fix the problem. So, how do I get that Sid kghostview on properly, without confusing apt? Also, where (if anywhere) is the appropriate doc that I could have read that explains this concept? Thank you! PS: I know there is something about "pinning", but right now I want to have (if possible) a less involved way of accomplishing this task. So, is there a way to do it without pinning? === I was unable to get kghostview to open a file. I then saw on: http://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=kghostview Grave functionality bugs - resolved (A list of all such bugs used to be available). #122050: kghostview: cannot open ps/pdf (SIGSEGV) Package: kghostview; Severity: grave; Reported by: "Raphael Derosso Pereira - DephiNit" <[EMAIL PROTECTED]>; Done: "Ivan E. Moore II" <[EMAIL PROTECTED]>. which looked similar to my error. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=122050&repeatmerged=yes had a resolution comment from Ivan saying: 2.2.2 works We see in http://packages.debian.org/cgi-bin/search_packages.pl?keywords=kghostview&searchon=names&subword=1&version=all&release=all Debian package search results Release Package (size) testing kghostview 4:2.1.1-6 (121.6k) PostScript viewer for KDE. unstable kghostview 4:2.2.2-6 (160.9k) PostScript viewer for KDE. Responses 1-2 shown, out of total of 2. So, what's the method to get that 4:2.2.2-6 installed on my Woody system? __ Do You Yahoo!? Great stuff seeking new owners in Yahoo! Auctions! http://auctions.yahoo.com
Re: What's the best way to pull a package from unstable to a Woody system?
--- Scott Henson <[EMAIL PROTECTED]> wrote: > > Use the pinning feature of apt. In /etc/apt/preferences, enter > > > > Package: kghostview > > Pin: release a=unstable > > Pin-Priority: 200 > > Acctually you can pin the entire unstable distribution. Add the > unstable deb sources in your sources.list Then create the above > mentioned file. then add this: > > Package: * > Pin: realease a=unstable > Pin-Priority: 50 > > That way you can apt-get anything from unstable whenever you want it. How, in that scenario, does one cause something to be gotten from unstable, rather than stable? And vice versa? Ie, what specific apt-get command would be used? Thanks! __ Do You Yahoo!? Great stuff seeking new owners in Yahoo! Auctions! http://auctions.yahoo.com
Re: What's the best way to pull a package from unstable to a Woody system?
--- Ron Johnson <[EMAIL PROTECTED]> wrote: > On Sun, 2002-01-27 at 22:58, tluxt wrote: > > I want a method that will not cause apt to get confused about this and > > other sw once I install the Sid package. > > > > Specifically: I have kghostview installed on the woody system. That > > sw has a malfunction, and from the bug report info on kghostview I see > that > > Sid has a newer package that might fix the problem. > > > > So, how do I get that Sid kghostview on properly, without confusing apt? > > > > Also, where (if anywhere) is the appropriate doc that I could have read > > that explains this concept? > > > > Thank you! > > > > PS: I know there is something about "pinning", but right now I want > > to have (if possible) a less involved way of accomplishing this task. > > So, is there a way to do it without pinning? > > I created 2 sources.list files: > # dir source* > lrwxrwxrwx root root 18 Jan 27 18:33 sources.list -> sources.list.woody > -rw-r--r-- root root 516 Jan 27 16:05 sources.list.sid > -rw-r--r-- root root 588 Jan 26 19:46 sources.list.woody > > Of course, each sources.list.* refers to the relevant distribution > directories. So, when I want to grab something from sid, I soft > link sources.list -> sources.list.sid, do "apt-get update", and > grab what I want. Then, soft link back to sources.list.woody and > "apt-get update". > > If you are only grabbing the same few pkgs out of sid, you could > easily script it. Thanks for the info! I am concerned, though, that this method might somehow confuse apt: It wouldn't know, after you switched the sources.list, that it used to be pointing to the other distribution. Then, if there are package depends, it might start pulling in packages that conflict with other packages. Do you know for sure that your method wouldn't cause apt to get confused? If so, how do you know? If not, how can we find out the answer to that question? :) __ Do You Yahoo!? Great stuff seeking new owners in Yahoo! Auctions! http://auctions.yahoo.com
Re: What's the best way to pull a package from unstable to a Woody system?
--- Osamu Aoki <[EMAIL PROTECTED]> wrote: > On Sun, Jan 27, 2002 at 09:51:52PM -0800, tluxt wrote: > > --- Scott Henson <[EMAIL PROTECTED]> wrote: > > > > Use the pinning feature of apt. In /etc/apt/preferences, enter > > > > Package: kghostview > > > > Pin: release a=unstable > > > > Pin-Priority: 200 > > > > > > Package: * > > > Pin: realease a=unstable > > > Pin-Priority: 50 > > > > > > That way you can apt-get anything from unstable whenever you want it. > > > > How, in that scenario, does one cause something to be gotten from > unstable, > > rather than stable? And vice versa? > > Ie, what specific apt-get command would be used? > > # apt-get install packagename/unstable > > This get package from unstable. If some dependency requitres another > package from unstable, list that package too. > > "--target unstable" also exists but I never used. Read "man apt-get"! > > Also document installed by "apt-howto" are useful. > > Oh, my web page below also has some hints. Cheers :) > + My debian quick-reference, http://qref.sourceforge.net/quick/ + ThankS! I found your quick reference very informative also! That document should definitely be linked from http://www.debian.org/doc/ddp under the users manuals section. You should definitely email the Debian web maintiners, http://lists.debian.org/debian-www/2002/debian-www-200201/threads.html and request that your document be put onto the Debian website, and have a link put on that page. You have my support for so doing. Also, I ran across the "apt-howto" earlier today, and that also ought to be linked from the same place. (I'll have to email that person also with the same suggestion.) === Hey, debian-www folks: Can you get those two docs up on the DDP page, without me having to create a wishlist bug? __ Do You Yahoo!? Great stuff seeking new owners in Yahoo! Auctions! http://auctions.yahoo.com
