Debian Bug Tracking System schrieb:
Actually, you are using the previous version of the package. I thought i
have solved this problem in version 1:2.2r2-2, but i have checked
anyway. It works well using last version of kernel-patch-squashfs
package (1:2.2r2-2), using exactly the same command line as yours.
That version of the package isn't available in Sarge.
Hence this is still a bug in Debian Sarge. If it is fixed at all, it
must be fixed in Sarge.
IMHO, this bug has three possible courses of action:
1) Close it with a "wontfix" tag.
2) Correct it in Sarge, and let that correction make its way into the
next Sarge update. The bug should be kept Open until that correction is
actually done.
3) Don't fix it, but document the problem in README.Debian (or maybe
even in the package description). Again, keep the bug Open until the
docs made it into the archives for the next upgrade.
Assessment:
#1 isn't bad, since then the bug is documented and anybody with a
problem with squashfs can come here and look. I think that #3 is better
because it places the information in a place that's easier to find for
the administrator.
#3 technically violates Debian policy AFAIK, but I think an exception
can be made for documentation that's technically incapable of
introducing bugs into the system.
#2 is a violation AFAIK, too, since it's not a security fix. It could be
argued that an exception should be made for it, since the fix is small,
fixes an obvious problem, and doesn't have visible ramifications.
(Assuming that that Debian's current 2.6.8 is indeed kernel.org's
2.6.8.1 - that's just my tentative diagnosis from the bug report and
should be checked before it is accepted as "official" and acted upon! I
lack the knowledge to check, else I'd have done it right away.)
Maybe you should upgrade to this version which is available in Etch or
Sid, and doesn't need a lot of installation dependancies.
Etch definitely isn't an option. These are internet servers, with
customer websites on them. Stability is far more important than slight
improvements in package handling.
Regards,
Jo
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
