Re: less than useful dselect/dpkg error msg
On Sun, 16 Nov 1997, Bill Leach wrote: > I do know that dpkg does not pay any attention to the "hold" status in > the admin file when executed directly (which makes sense to me). That is because you will have to supply the -O option to dpkg if you want it to pay attention to that flag (which can be 'install', 'uninstall' or 'hold'). From 'dpkg --help': -O|--selected-only Skip packages not selected for install/upgrade Dselect's ftp method (the only one I use) always calls dpkg with -iGREOB . Remco -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: less than useful dselect/dpkg error msg
Hamish wrote: Something like that. I agree that "not ready for configuration" is not the best message. Perhaps you could file a bug against dpkg? Checked and there already is one filed. Thanks, best, -bill Get free e-mail and a permanent address at http://www.netaddress.com -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: less than useful dselect/dpkg error msg
Hey Dale: me: > > are pretty much useless. This sort of error message reminds > > me of Red Hat's RPM! > Ooooh, that was nasty ;-) Yes, and it is only one that has actually USED RPM that can truely appreciate just HOW nasty that remark was. That is, one that has used RPM and has since used dselect/ dpkg! The Debian package management system is amazing to the point of being almost unbelievable. Between a PC and an Amiga (debian-m68k) I have probably made about every mistake that one can make. I have yet (looking around for some real wood to knock on) to render a machine unbootable. I did mess up an m68k machine enough that I decided it was not worth further fooling around and just reinstalled (and yes it was a libc6 upgrade). As this particular upgrade was from the hamm distribution, I am still not sure if the problem should be considered a bug or not (assuming of course that it is not some unique problem with my machine) but dselect downgrades some packages everytime it runs unless those packages are placed on hold status. In my second installation attempt, I only let dselect install the minimum necessary software and then used dpkg to upgrade everything that had been installed to the latest versions (again following Scott's mini-HOWTO). Then I set ALL packages to hold using dselect. Until I figure this out, I will keep all packages set to hold and individually select packages for installation and upgrade. But even then I probably should watch to be sure that during the upgrade a package is not downgraded. I doubt that there are any packages left that will break the system if a downgrade does occur however. The 'less than useful' error message is the strange (IMHO) way that dpkg has for telling me that the package can not be configured because it is already configured. I do know that dpkg does not pay any attention to the "hold" status in the admin file when executed directly (which makes sense to me). best, -bill > > > > What causes this sort of information free error message? > > Does dpkg honor the 'hold' status in the status file when it > > is placed there by dselect (that is when dpkg is run manually from the > > command line)? > > > I'm not conversant with dpkg internals enough to tell you where that "less > than useful" error message originates. Was the package really on Hold > status? > As far as I can tell, dpkg honors the hold in the status file, unless you > include --force-hold as an option on the command line. (It can't tell > whether dselect put the Hold there, or some editor, but that is another issue) > > Luck, > > Dwarf > -- > _-_-_-_-_-_- _-_-_-_-_-_-_- > >aka Dale Scheetz Phone: 1 (904) 656-9769 > Flexible Software 11000 McCrackin Road >e-mail: [EMAIL PROTECTED] Tallahassee, FL 32308 Get free e-mail and a permanent address at http://www.netaddress.com -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: less than useful dselect/dpkg error msg
Bill Leach wrote: > Receiving error messages such as the following: > > Linux# dpkg --configure fvwm2 >dpkg: error processing fvwm2 (--configure): >package fvwm2 is not ready for configuration >cannot configure (current status `installed') > Errors were encountered while processing: >fvwm2 > Linux# > > are pretty much useless. This sort of error message reminds > me of Red Hat's RPM! > > What causes this sort of information free error message? What it means is that fvwm2 is already configured. A package that is installed must of already been configured. > Does dpkg honor the 'hold' status in the status file when it > is placed there by dselect (that is when dpkg is run manually from the > command line)? I don't believe so, I believe it changes it. - Craig -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: less than useful dselect/dpkg error msg
On Sun, Nov 16, 1997 at 10:06:53PM +, Bill Leach wrote: > OK, that was probably the case as fvwm2 is now working. However, I do think > that it would be more useful is dselect/ > dpkg reported "configured". > > Linux# dpkg --configure fvwm2 > dpkg: error processing fvwm2 (--configure): > package fvwm2 is not ready for configuration > cannot configure (current status `installed') > Errors were encountered while processing: > fvwm2 > > To me, that seems to be saying that fvwm2 still needs configuration but there > is something wrong. Now I admit > that this is no doubt due in part to my own ignorance. I suspect now that if > the package was not configured that the parenthetical statement would read > something like: > (current status 'unpacked') -- yes? Something like that. I agree that "not ready for configuration" is not the best message. Perhaps you could file a bug against dpkg? Hamish -- Hamish Moffatt, StudIEAust [EMAIL PROTECTED], [EMAIL PROTECTED] Student, computer science & computer systems engineering.3rd year, RMIT. http://hamish.home.ml.org/ (PGP key here) CPOM: [* ] 59% Your train has been cancelled due to defective government at Spring Street.. -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: less than useful dselect/dpkg error msg
OK, that was probably the case as fvwm2 is now working. However, I do think that it would be more useful is dselect/ dpkg reported "configured". Linux# dpkg --configure fvwm2 dpkg: error processing fvwm2 (--configure): package fvwm2 is not ready for configuration cannot configure (current status `installed') Errors were encountered while processing: fvwm2 To me, that seems to be saying that fvwm2 still needs configuration but there is something wrong. Now I admit that this is no doubt due in part to my own ignorance. I suspect now that if the package was not configured that the parenthetical statement would read something like: (current status 'unpacked') -- yes? best, -bill Get free e-mail and a permanent address at http://www.netaddress.com -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: less than useful dselect/dpkg error msg
On Sat, 15 Nov 1997, Bill Leach wrote: > Receiving error messages such as the following: > > Linux# dpkg --configure fvwm2 >dpkg: error processing fvwm2 (--configure): >package fvwm2 is not ready for configuration >cannot configure (current status `installed') > Errors were encountered while processing: >fvwm2 > Linux# > > are pretty much useless. This sort of error message reminds > me of Red Hat's RPM! Ooooh, that was nasty ;-) > > What causes this sort of information free error message? > Does dpkg honor the 'hold' status in the status file when it > is placed there by dselect (that is when dpkg is run manually from the > command line)? > I'm not conversant with dpkg internals enough to tell you where that "less than useful" error message originates. Was the package really on Hold status? As far as I can tell, dpkg honors the hold in the status file, unless you include --force-hold as an option on the command line. (It can't tell whether dselect put the Hold there, or some editor, but that is another issue) Luck, Dwarf -- _-_-_-_-_-_- _-_-_-_-_-_-_- aka Dale Scheetz Phone: 1 (904) 656-9769 Flexible Software 11000 McCrackin Road e-mail: [EMAIL PROTECTED] Tallahassee, FL 32308 _-_-_-_-_-_- If you don't see what you want, just ask _-_-_-_-_-_-_- -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: less than useful dselect/dpkg error msg
On Sun, Nov 16, 1997 at 05:50:46AM +, Bill Leach wrote: > Receiving error messages such as the following: > Linux# dpkg --configure fvwm2 >dpkg: error processing fvwm2 (--configure): >package fvwm2 is not ready for configuration >cannot configure (current status `installed') > Errors were encountered while processing: >fvwm2 > Linux# > > are pretty much useless. This sort of error message reminds > me of Red Hat's RPM! > > What causes this sort of information free error message? > Does dpkg honor the 'hold' status in the status file when it > is placed there by dselect (that is when dpkg is run manually from the > command line)? The error message is less than friendly but there is no mention of hold status; simply, it says that fvwm2 is not ready for configuration because it is already installed. installed implies configured. That is, the package needs no further processing by dpkg, and you can't configure a package that has already been configured (or not through dpkg at least). As I understand it, hold means do not upgrade. dselect will tell tell dpkg to ignore upgrades to the package, and I guess dpkg-ftp would also ignore them. But "dpkg -i " will do it anyway. Hamish -- Hamish Moffatt, StudIEAust [EMAIL PROTECTED], [EMAIL PROTECTED] Student, computer science & computer systems engineering.3rd year, RMIT. http://hamish.home.ml.org/ (PGP key here) CPOM: [* ] 59% The opposite of a profound truth may well be another profound truth. --Bohr -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
less than useful dselect/dpkg error msg
Receiving error messages such as the following: Linux# dpkg --configure fvwm2 dpkg: error processing fvwm2 (--configure): package fvwm2 is not ready for configuration cannot configure (current status `installed') Errors were encountered while processing: fvwm2 Linux# are pretty much useless. This sort of error message reminds me of Red Hat's RPM! What causes this sort of information free error message? Does dpkg honor the 'hold' status in the status file when it is placed there by dselect (that is when dpkg is run manually from the command line)? best, -bill Get free e-mail and a permanent address at http://www.netaddress.com -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
