From: Linux for blind general discussion <blinux-list@redhat.com>
To: blinux-list@redhat.com
Subject: Re: apt-get error with espeakup
Date: Thu, 22 Nov 2018 13:18:09 +0000 [thread overview]
Message-ID: <CAO2sX3214zcCLtNRpPH3Tucg8QAASF-6q=N6hR0d6DLR1LkokA@mail.gmail.com> (raw)
In-Reply-To: <CAOdwYiRVQK0mxCwSjeCOx1p9J2bSbMNSLj2eEgSh8dNCj2F9xw@mail.gmail.com>
For what it's worth, installation and removal scripts are stored in
/var/lib/dpkg/info, are named after the package they belong to and
have the following extensions:
.preinst: pre installation.
.postinst: post installation.
.prerm: pre removal.
.postrm: post removal.
and the .list files in those directories list all the files on the
system that belong to that page.
removing a script that failed will cause dpkg to ignore it the next
time you attempt the package operation that ran the script, but I'm
not sure this is advisable if you plan to try compiling the package
your trying to remove from source.
Also, removing a package's entry from /var/lib/dpkg/status will render
it invisible to apt/dpkg/most apt frontends, but again, not sure if
advisable, and errors in the status file will make apt/dpkg refuse to
do anything until its fixed.
Messing with this stuff is quite hackerish, and even if it solves the
immediate problem, there's no guarantee it won't cause bigger problems
down the line.
--
Sincerely,
Jeffery Wright
Bachelor of Computer Science
President Emeritus, Nu Nu Chapter, Phi Theta Kappa.
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion [this message]
` Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAO2sX3214zcCLtNRpPH3Tucg8QAASF-6q=N6hR0d6DLR1LkokA@mail.gmail.com' \
--to=blinux-list@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).