Hi all,
as mentioned in #691160, in some cases APT fails to provide a clean
upgrade path from python-pyatspi to python-pyatspi2.
Since both packages are binary-compatible, the python-pyatspi2 package
should never have existed in the first place, but it’s a bit late for
that. I think the easiest way to make APT’s job easier is to remove the
current python-pyatspi package. Hence we can have 2 scenarios.
A:
1. Make python-pytaspi an empty package depending on
python-pyatspi2.
2. Make the conflict a versioned one.
3. Remove the Provides in python-pyatspi2.
B:
1. Remove python-pyatspi from the at-spi source package.
2. Rename python-pyatspi2 to python-pyatspi.
3. Make python-pyatspi2 an empty package depending on
python-pyatspi.
In both cases this needs a synchronized upload of at-spi and pyatspi2.
A11y maintainers: what are your thoughts?
Release team: would you accept such a change for wheezy?
Cheers,
--
.''`. Josselin Mouette
: :' :
`. `'
`-
--
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/1351784057.710.10.camel@tomoyo
