clone 404919 -1
reassign 404919 kernel-patch-bootsplash
retitle 404919 kernel-patch-bootsplash is obsolete and should not be shipped
reassign -1 linux-patch-bootsplash
retitle -1 linux-patch-bootsplash should replace kernel-patch-bootsplash
severity -1 important
thanks

On Fri, Dec 29, 2006 at 07:35:10AM +0100, Michael Ablassmeier wrote:
> both linux-patch-bootsplash and kernel-patch-bootsplash ship
> `/usr/src/kernel-patches/all/apply/bootsplash' but do not conflict or
> add a diversion, thus fail to be installed on the same environment:

>  dpkg: error processing 
> /var/cache/apt/archives/linux-patch-bootsplash_2.6.18-1_all.deb (--unpack):
>   trying to overwrite `/usr/src/kernel-patches/all/apply/bootsplash', which 
> is also in package kernel-patch-bootsplash
>  dpkg-deb: subprocess paste killed by signal (Broken pipe)
>  Errors were encountered while processing:
>   /var/cache/apt/archives/linux-patch-bootsplash_2.6.18-1_all.deb
>  E: Sub-process /usr/bin/dpkg returned an error code (1)

> i think linux-patch-bootsplash should replace kernel-patch-bootsplash? is 
> there
> any reason for having this package twice with different versions in the
> archive?

Nope, the linux-patch-bootsplash changelog makes it clear that this package
supersedes kernel-patch-bootsplash, and the kernel-patch-bootsplash package
in testing is for an older version of the kernel.

So kernel-patch-bootsplash should be dropped from the release (and from the
archive, AFAICS?), and linux-patch-bootsplash should Replace:
kernel-patch-bootsplash.  The latter is not release-critical, because
kernel-patch-bootsplash wasn't in sarge and won't be in etch (I'm tagging it
for immediate removal from testing).

Thanks,
-- 
Steve Langasek                   Give me a lever long enough and a Free OS
Debian Developer                   to set it on, and I can move the world.
[EMAIL PROTECTED]                                   http://www.debian.org/


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to