Re: alternatives DB corruption
Am Mi, 20.07.2011, 14:40 schrieb Raphael Hertzog: > On Wed, 20 Jul 2011, Michael Neuffer wrote: >> > The database file is corrupted. What did you do to corrupt it? Is >> there a >> > reliable way to corrupt it? >> >> Yes, by editing it by hand. :-) > > So there's no bug in update-alternatives at least. No, not that I know of. >> I had to do it a few weeks earlier to remove >> some alternatives that were corrupted by a broken package. >> (Things that constantly using unstable can do to you...) > > Hum, that should not happen. You should always be able to > update-alternatives to fix stuff. Not when you manage to get into circular dependencies. >> I had to edit and fix alternatives manually every now and then over the >> past 15 years or so and never had (major) problems with that. Maybe I >> was >> just lucky so far. > > You won't have to do this in the future, update-alternatives no longer > allows installation of broken alternatives and fixes stuff itself for most > cases. When did that change get rolled out? >> > It lacks lots of empty lines at the end. Each alternative should have >> a >> > set of line like this: >> > [...] >> Yes I removed them. I wasn't aware that they were significant. > > *shrug* :-) >> The file format unfortunately isn't documented in the man page. > > Because it's not meant to be edited with anything else than > update-alternatives... Maybe a warning in the manpage would be good. Manually fixing up dpkg status & info files becomes an ingrained habit over the years. The Debian & Ubuntu bleeding egde will cut you every now and then with problems that force manual intervention. >> Is there a way to find out how many empty lines are missing where? > > I documented the format above... Yes thank you for that. > in your specific case you need 15 lines > in total (master + priority + 13 slaves). You already have 4 lines so you > need 11 empty lines after. Thanks! I'll give it a shot when I'm back home. Currently I don't have my laptop with me. Cheers Mike -- To UNSUBSCRIBE, email to debian-dpkg-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/fe5cbc05f677d24daa0ffbd19f1632a7.squir...@www.neuffer.com
Re: alternatives DB corruption
Hi Raphael Am Mi, 20.07.2011, 12:16 schrieb Raphael Hertzog: > please use the mailing list debian-dpkg@lists.debian.org next time. I've added a Cc: to the list. > On Wed, 20 Jul 2011, Michael Neuffer wrote: >> I have ad "db" file which seems to be corrupt and i can't figure out >> what is wrong. > > The database file is corrupted. What did you do to corrupt it? Is there a > reliable way to corrupt it? Yes, by editing it by hand. :-) I had to do it a few weeks earlier to remove some alternatives that were corrupted by a broken package. (Things that constantly using unstable can do to you...) I had to edit and fix alternatives manually every now and then over the past 15 years or so and never had (major) problems with that. Maybe I was just lucky so far. > It lacks lots of empty lines at the end. Each alternative should have a > set of line like this: > > > > > ... > > > Yet your last alternative only has 4 lines: > > /usr/lib/x86_64-linux-gnu/mesa/ld.so.conf > 500 > > /usr/lib/x86_64-linux-gnu/xorg/x11-extra-modules > Yes I removed them. I wasn't aware that they were significant. The file format unfortunately isn't documented in the man page. Is there a way to find out how many empty lines are missing where? Cheers Mike -- To UNSUBSCRIBE, email to debian-dpkg-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/710f483c8257d57dba121e528ccb4edb.squir...@www.neuffer.com
Re: Bits from the dpkg team
On 03/26/2010 01:49 AM, Guillem Jover wrote: We are planning to split dselect from the dpkg source tree in the nearish future, once libdpkg API has stabilized a bit. It's currently in maintenance mode and needs someone who cares and actually use the thing. I know quite a number of people who are using dselect and who actually pinned dpkg in order to be to prevent breakage. The current status is not good. Maybe I'm just a odd Debian Oldtimer, but so far I haven't seen anything that could really replace dselect in terms of ease of use and ability to run on a console over slow lines. Especially if you quickly want to see which new packages entered the distribution, which changed and which you have pinned due to various conflicts and problems that appear when tracking unstable. Cheers Mike -- To UNSUBSCRIBE, email to debian-dpkg-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4bac6b05.9050...@neuffer.info
Bug#150135: galeon-common: tries to open non-existant file
Quoting Erich Schubert ([EMAIL PROTECTED]): > reassign 150135 dpkg > thanks > > > Setting up galeon-common (1.2.5-1) ... > > Failed to open `/etc/gconf/schemas/galeon.schemas': No such file or > > directory > > dpkg: error processing galeon-common (--configure): > > subprocess post-installation script returned error exit status 1 > > I think dpkg is broken somehow: the file IS in the galeon-common-package. > > dpkg -c galeon-common_1.2.5-1_all.deb | grep schema > [...] ./etc/gconf/schemas/galeon.schemas > > I've seen this problem before, it must come from dpkg's conffile > mechanism. If you "dpkg --purge galeon galeon-common galeon-nautilus" > and then install galeon again it should work fine. > I don't know how to reproduce it. I didn't have galeon installed. After a purge of galeon-common galeon-nautilus and a reinstall it worked just fine. > (Note that the file was in the galeon package itself before, maybe > moving conffiles from one package to another doesn't work properly?) > > Do you know what the previous version of galeon was that you had > installed? The last one that was in unstable yesterday. Cheers Mike -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: dpkg-scanlibs
Quoting Radovan Garabik ([EMAIL PROTECTED]): > On Sun, Feb 25, 2001 at 10:29:43PM -0600, Jon Nelson wrote: > > > On Sun, Feb 25, 2001 at 10:03:58PM -0600, Jon Nelson wrote: > > > > I only see one problem with dpkg-scanlibs.py: it uses tabs > > > > tabs are evil, wichert! Every editor under the sun uses different tab > > > > settings. Use spaces, my man. > [...] > > 4 in everything else. Most of the Python community seems to prefer > > either 2 or 4, and rarely 8. So what? If it is done with spaces it is > > unimportant, but done with tabs it's vital. > > so nothing :-) > the problem is not in tabs by themselves, but arises when > you mix tabs and spaces. > E.g. you configure your editor to use 2 spaces per tab, and you > add some code, but do not use tab to indent it, but spaces > (or your editor inserts spaces automatically when you press tab) > but python interpreter considers tab to be 8 spaces... yuck > the solution is: choose either tabs or spaces, but > be _consistent_, and because there is no ambiguity with spaces, > spaces are preferred. You will never be able to get this consistent. A space or tab will always sneak in, screw you and you won't even be able to find it easily. Mike
