Hi all,
This patch should work for Hardy and support a seamless upgrade path as
well.
>From reading #33394, I see that it tries to explain away modifying the
metapackage on the grounds that it implies official support for what's
listed therein. That sounds suspect, at best. If someone can point me to
a public document, created prior to today hopefully, that shows this to
be the case, this point will be moot. Support status is implied by which
section of the pool a package is in. Furthermore, I'd advocate that the
Intrepid Ibex release move toward syslog-ng as the default logging
agent; and if that means supporting syslog-ng, so be it. I'd advocate
that; it's first-class software. If necessary, I'll start putting some
notes in a specification draft.
Further mootification of existing concerns:
1.) This patch does not specifically mention syslog-ng in the metapackage
package lists; rather, it works off of the fact that both syslog-ng and
sysklogd are part of the system-log-daemon virtual package. This is
implementation inspecific, so I have yet to see how confusion will arise given
the way that package managers behave. Look for yourself and try it out.
2.) On a more serious note, the existing design makes it difficult and
risky to control package lists by means of configuration management
software. The reason for this is that apt and dpkg are likely to force
the user into an interactive mode whereby using --yes or --force may be
insufficient to make it non-interactive. Nobody really should have to
use --force in an automated script anyhow, and especially not
DPkg::Options::={"--force-all"} to get this resolved. This is a killer
for large deployments of Ubuntu.
Also, I really don't want to force the package manager to do something
that it doesn't want to do. Imagine --force or --force-all being applied
by dpkg or apt to a whole suite of unrelated packages. This could happen
if ``apt-get -f install'' or ``dpkg --configure --all'' was needed to be
run before-hand. Apt, by means of its implied state resolution behavior
could apply forceful behavior wholesale to a bunch of things where it
shouldn't, especially if it is called from a CMS like Puppet or
CFEngine.
In short, this makes managing packages as such safer because of not
using a sledgehammer to do a ball-peen's work.
I'd really like to see this patch incorporated before the Hardy release:
It's rather non-invasive. This has been affecting me since Dapper! Maybe
we can channel our frustrations at
https://blueprints.edge.launchpad.net/ubuntu/+spec/syslog-improvements
after the Hardy release.
Cheers,
Matt
** Attachment added: "Attached is a patch that makes ubuntu-meta sane with
respect to sysklogd and system-logging-daemon."
http://launchpadlibrarian.net/12172686/ubuntu-meta-sysklogd-and-system-logging-daemon-coexistence.patch
--
ubuntu-minimal should support recommends (was: syslog-ng causes ubuntu-minimal
to be removed.)
https://bugs.launchpad.net/bugs/42555
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
