On 2011-02-13 10:08 +0100, Daniel Baumann wrote:
> On 02/13/2011 09:57 AM, Sven Joachim wrote:
>> What is the point of syslinux/syslinux-common breaking all previous
>> versions of each other
>
> bootloaders (syslinux) and modules (syslinux-common) need to match.
That's ensured by the strict versioned dependency. I also understand
that syslinux-common may need to break older versions of syslinux which
did not have such a strict dependency (though the version in squeeze
has, so it's only relevant for unsupported upgrades from older
versions, and you could restrict the Breaks to versions which did not
have the strict dependency).
What I do not understand at all is why syslinux has to break older
versions of syslinux-common when it already depends on the current one.
> although it happens rarely that modules of the previous version don't
> work with the next versions bootloaders, it's not guaranted to work and
> the strong declared relations ensure your system stays bootable.
>
> also, see changelog with the referenced bugs for more information.
If you're talking about #497992/#497996, the solution is to have
versioned Replaces. Or do you mean some other bug?
Regards,
Sven
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
