From: Neil Bothwick <neil@digimed.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] trouble installing cups
Date: Tue, 17 Sep 2013 00:39:38 +0100 [thread overview]
Message-ID: <20130917003938.0735c735@hactar.digimed.co.uk> (raw)
In-Reply-To: <874n9kqu4q.fsf@nyu.edu>
[-- Attachment #1: Type: text/plain, Size: 494 bytes --]
On Mon, 16 Sep 2013 18:28:05 -0400, gottlieb@nyu.edu wrote:
> So I reinstalled cups but /etc/cups/cupd.conf was not changed and still
> has its old date and contents. The merge looks clean (output below)
/etc/ is CONFIG_PROTECTed. Also, portage knows if you are reinstalling
the same version of the same package and does not try to update the
configs again. To change this, run the emerge with --noconfmem and then
run *-update.
--
Neil Bothwick
IBM: Itty Bitty Mentality
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2013-09-16 23:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-16 22:28 [gentoo-user] trouble installing cups gottlieb
2013-09-16 23:39 ` Neil Bothwick [this message]
2013-09-17 1:23 ` gottlieb
2013-09-17 9:22 ` Neil Bothwick
2013-09-17 15:17 ` gottlieb
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=20130917003938.0735c735@hactar.digimed.co.uk \
--to=neil@digimed.co.uk \
--cc=gentoo-user@lists.gentoo.org \
/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