From: gottlieb@nyu.edu
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] trouble installing cups
Date: Tue, 17 Sep 2013 11:17:49 -0400 [thread overview]
Message-ID: <87d2o7pjdu.fsf@nyu.edu> (raw)
In-Reply-To: <20130917102225.3eaeb02b@digimed.co.uk> (Neil Bothwick's message of "Tue, 17 Sep 2013 10:22:25 +0100")
On Tue, Sep 17 2013, Neil Bothwick wrote:
> On Mon, 16 Sep 2013 21:23:50 -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.
>>
>> This part I knew, but would have expected to hear that config files
>> have new versions
>
> You would if upgrading. But you are reinstalling the same version so
> portage assumes you have already dealt with any config updates and don't
> want to be bothered again.
>
> Remember when we had to go through loads of updates over again when
> revdep-rebuild rebuilt a package with lots of config files. This avoids
> that behaviour, --noconfmem brings it back.
Understood. Thanks for the explanation.
allan
prev parent reply other threads:[~2013-09-17 15:18 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
2013-09-17 1:23 ` gottlieb
2013-09-17 9:22 ` Neil Bothwick
2013-09-17 15:17 ` gottlieb [this message]
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=87d2o7pjdu.fsf@nyu.edu \
--to=gottlieb@nyu.edu \
--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