Bug#567669: fixed in apt 0.7.26~exp1 but there were typo
2010/2/20 Osamu Aoki <osamu@debian.org>:
> For simplicity, let's think Python and related packages as an example.
I don't speak python, but i thought the Python-Version control entry
is responsible for taking care of this - or at least there should be some
facility to prevent injury here because - as i said - in a dist-upgrade run
the system is mixed, it would be bad if some python code like the
update-manager (and everything else relaying on python-apt) isn't working…
Same goes for other scripting languages and libraries
(perl and debconf come immediately to my mind - through i don't know
perl either).
Anyway, you are right, some dependencies can't be expressed, like udev
requiring a kernel which doesn't have very old deprecated options enabled,
so leaving the tested path a distribution provides is always risky.
(I thought this is obviously but i am proven wrong every other day)
> Of course, you nor I may not experience this kind of situation by having
> good instinct, but this problem deserves fair attention.
Common sense should be enough, but if we would depend on it the
complete section is useless. ;) So let us state it explicitly to be on
the safe side. What do you think about the following?
<para>Preferences are a strong power in the hands of a system administrator
but they can become also their biggest nightmare if used without care!
APT will not question the preferences so wrong settings will therefore
lead to uninstallable packages or wrong decisions while upgrading packages.
Even more problems will arise if multiple distribution releases are mixed
without a good understanding of the following paragraphs.
+ Packages included in a specific release aren't tested in and
+ therefore doesn't always work as expected in older or newer releases or
+ together with other packages from different releases.
You have been warned.</para>
Best regards,
David Kalnischkies
Reply to: