On Tue, Mar 16, 2010 at 10:17 -0500, Mark Allums wrote: > On 3/16/2010 8:28 AM, Wolodja Wentland wrote: > > >The easiest way would be to enforce a strict naming scheme (maybe with > >lintian) so the aforementioned code can stay as simple as it is today.
> In the short run, an easy thing to do is remove -trunk- image and > all corresponding packages, as it is an experimental-grade kernel > that got promoted to Sid by mistake. If .32-3 is working, then > -trunk- is not needed at all. That surely is the easiest (and best IMHO) solution for users that run into this problem, but I rather meant "What is the easiest and best way to prevent things like this in the future". I've just found #568160, which proposes the inclusion of -trunk into the list of already special cased package name substrings in debian/update_grub. I still don't get why the "trunk" part in the package name was not ~trunk or -0, which would convey the meaning of "Has not reached final -1 ABI". -- .''`. Wolodja Wentland <wentl...@cl.uni-heidelberg.de> : :' : `. `'` 4096R/CAF14EFC `- 081C B7CD FF04 2BA9 94EA 36B2 8B7F 7D30 CAF1 4EFC
signature.asc
Description: Digital signature
