Comment 10 for bug 7337

* Adrian Bunk schrieb am 07.08.04, um 16:57 Uhr:
> On Fri, Aug 06, 2004 at 08:24:16PM -0600, Bdale Garbee wrote:
> > Adrian Bunk <email address hidden> writes:
> >
> > > severity 263136 grave
> >
> > Grave? Surely you jest.
>
> It's an issue that should definitely fixed before Debian 3.1 .

Yes, this issue should be discussed, but i do not see a simply way to
solve it.

One reason for keeping major 250 in sarge is that it is allmost sure
that sarge wont ship (at release-time) a kernel, which uses 212, and
the dvb-driver-source-package (for 2.4-users) also uses 250. So
just changing makedev to use would 212 break the device-generation for
most users of sarge. (At least a long as they use a kernel <=2.6.7 or
the dvb-driver-source-package in sarge.)

Ok, there are also reasons to change it, because it is clear that some
sarge-users would like to use a kernel >=2.6.8, but i do not see how
this change can be made without breaking the dvb-device-generation for
the other sarge-users.

Note: I am the (co-)maintainer of the packages linuxtv-dvb,
linuxtv-dvb-apps and vdr, which all rely on the correct
dvb-device-generation, as they use "makedev dvb" in their postinst.

There is also at least one other package, which uses it in its
postinst: dvbtune

Regards,
Thomas

--
Thomas Schmidt
:wq