Hi Rolf, * Christoph Biedl ([email protected]) [121226 21:55]: > Rolf Leggewie wrote...
> > As I've written in this ticket before, this is not a bug in isdnutils. > > I'm afraid there is no good solution at the moment and I'm not aware of > > anyone working on this in the kernel or udev. > Now if you reject, the ISDN subsystem is broken at least on all > installations that use udev or are newly installed. The logical > consequence then is to consider isdnutils unfit for release and remove > it from wheezy. I doubt that this is your intention. > > For the time being the > > administrator needs to make sure the devices are created. > > So you want each isdnutils user to manually hack some mknod statements > into the bootup scripts as you consider it a bad idea providing that > as package maintainer? Seriously? How should we continue from here? Frankly speaking, though I agree the best solution would be to fix kernel and udev, I don't believe this will happen during the freeze. The second-best solution seems to fix isdnutils. So, as you explicitly disagree with the fix, the options are: 1. You convince Christoph to have it not fixed (or at least, to not care enough anymore to stick to this topic) 2. Christoph convinces you to have it fixed (if it would be ok for you, I would be happy to upload the fix, and I hope I could convince Christoph to take over ongoing responsibility for the patch) 3. The only other way allowed by the constitution if there is a serious disagreement would be an escalation to the tech ctte. I would hope this could be prevented however. Which way do you think we should continue? Andi -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
