We've got a problem here ... to keep the binaries aligned through breaks it
would need
cross breaking, right?
I mean, python-afl 0.5-3 breaks python3-afl << 0.5-3 (and vice versa) to
prevent the described problem:
python3-afl 0.5-3 couldn't be installed wrongfully at the side of python-afl
0.2.1-1 with that (and
vice versa).
But that needs further action because that cross breaking prevents updating w/o
previous uninstall:
<cut>
$ sudo dpkg -i svn/build-area/python{,3}-afl_0.5-3_amd64.deb
{...}
python-afl breaks python3-afl (<< 0.5-3)
python3-afl (version 0.2.1-1) is present and installed.
{...}
python3-afl breaks python-afl (<< 0.5.3)
python-afl (version 0.2.1-1) is present and installed.
</cut>
Better, versioned cross-*dependencies* of the binaries? Like,
<cut>
$ sudo dpkg -i svn/build-area/python3-afl_0.5-3_amd64.deb
{...}
dpkg: dependency problems prevent configuration of python3-afl:
python3-afl depends on python-afl (= 0.5-3); however:
Version of python-afl on system is 0.2.1-1.
</cut>
Not the ultimate rationale of having different binaries, but ... did I missed
something?
Daniel
--
4096R/DF5182C8
46CB 1CA8 9EA3 B743 7676 1DB9 15E0 9AF4 DF51 82C8
LPI certified Linux admin (LPI000329859 64mz6f7kt4)
http://www.danielstender.com/blog/
