Christoph Berg [2013-05-06 18:27 -0700]:
> The pgdg repositories are (now) using the default priority, so apt
> will prefer the pgdg packages over the native ones. It just isn't
> smart enough to figure out that the raring package would have worked.
Right, I think I figured out something like this in a followup
comment. I forgot that pgdg already has version 141 of p-common.
> Martin: What do you think about generating the logrotate config at
> install (configuration) time so we can drop the fixed logrotate
> depends/breaks? Using "ucf" for generated files in /etc/ is pretty
> easy to do, the open question would be how to detect that logrotate
> was just upgraded and that we need to re-generate the file. Maybe with
> a trigger on /usr/sbin/logrotate? Or is that too much magic? (Are we
> aware of other packages that have this problem?)
It's too much magic for my taste. With conffiles there's so much that
can go wrong, and one often runs into situations where they cannot be
updated automatically.
But in the end I don't think that this is such a big problem; the
non-LTS releases are really not a good thing to deploy PostgreSQL on,
especially now that from 13.04 on they are only supported for 9
months. So perhaps the right answer for now is just "don't do that
then"?
Martin
--
Martin Pitt | http://www.piware.de
Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)
