On Thu, Mar 30, 2006 at 12:30:47PM +0200, Marco d'Itri wrote:
> On Mar 30, Julian Gilbey <[EMAIL PROTECTED]> wrote:
> 
> > Right, I've now upgraded to the unstable version (0.088-2), rebooted
> > and I ***STILL*** get the error message.
> *And* useful information in NEWS.Debian.

Oh, didn't think to read this.  Again, a Joe User isn't likely to read
stuff like this about a system-tools package.  Something as
fundamental to the system as udev should either work out of the box or
use debconf to get answers to necessary questions.

> > Perhaps the package should just have fixed cd-aliases.rules (which is
> > a conffile anyhow) rather than leaving the broken rules file and
> > introducing another one?
> No, because it's a different file which works in a different way.

OK.

> > Also, the default installation of a package should *NOT* give error
> > messages: I haven't touched any of the udev configuration files or
> > anything.
> The default installation does not, but at least for a while (until %e
> will work) I will not automatically change an existing configuration.

But my installation *does* give this error!  (Unless you mean the
default installation in 0.088.)

> > Finally, /etc/udev/rules.d/cd-aliases.rules *still* has %e in it, and
> > I have no /etc/udev/rules.d/z75_cd-aliases-generator.rules.
> It will be created after the first reboot, as long as you enable
> creation of persistent CD aliases.

I don't know how to "enable creation of persistent CD aliases".

> > Ah, I think I see the "bug": in the postinst, you only modify the
> > /etc/udev/rules.d directory if none of the package's known symlinks
> > are already present.  But then you are stuffed: when you fix stuff in
> This is a feature.

A user who installs version 0.4 of a package, makes no local
modifications, and then simlpy upgrades 0.4 -> 0.5 -> 0.6 should have
a functionally identical system to a user who installs 0.6 in the
first place.  That is not happening here.

   Julian


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to