Steve Langasek wrote: > On Mon, May 30, 2005 at 12:56:22PM +0200, Jonas Smedegaard wrote: > >>On 30-05-2005 10:17, Steve Langasek wrote: > > >>>I realize that debian-edu-config is something of a special case, because of >>>its narrow application. I don't think that Debian-Edu should get a free >>>pass for violating policy, but I also don't think that there's much risk of >>>this issue affecting people who aren't installing debian-edu explicitly, so >>>it doesn't seem to make much difference to their net experience whether >>>deiban-edu-config is allowed in sarge or not. So unless someone else on the >>>release team objects, I think I'm going to tag this bug sarge-ignore. > > >>So for the upgrade path from sarge to etch you want maybe 30+ quite >>popular packages to weed out bugreports caused by chain-reactions of >>installing this package? > > > How does including the package in sarge make any difference to the number of > bugs (mis-)reported against these other packages? The Skolelinux users are > still going to be installing it and modifying these conffiles; people who > are not Skolelinux users are still not going to. > > >>I agree that debian-edu is a special case, but don't see your point in >>that being a good excuse for ignoring policy: Debian-edu-* packages are >>expected only to be useful in the Skolelinux Debian-derived >>distribution. It is a goal of debian-edu to be able to create Skolelinux >>solely from officially released Debian packages but that goal is not yet >>reached so a few more packages having to be added unofficially shouldn't >>be a big deal. > > > What other packages does Skolelinux depend on for sarge that are not in > Debian?
ltsp j2re1.4 -- Finn-Arne Johansen [EMAIL PROTECTED] http://bzz.no/ Debian-edu developer -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
