tag 576270 + unreproducible
thanks
Failed to reproduce this:
- installing the 0.86 packages from testing and upgrading
to unstable works.
- installing the 0.88 packages from testing and upgrading
to unstable works.
- installing the 0.86 packages from testing and installing
the 0.88 in unstable works.
>Almost wrote same problem because the symptom matches, but the reason
>is different. The Python files from sugar-toolkit are there, but
>__init__.py is missing so the "sugar" package isn't recognized:
I could imagine this happens when a conflict in the python-sugar-0.xx packages
was missing such that the new version was unpacked before the old one was
removed. but looking at the current packages in testing and unstable, the
conflicts are ok. would it be possible that a conflict was missing in the past
for one upload?
> r...@xo15-minimal:~# dpkg -S /usr/share/pyshared/sugar/__init__.py
> python-sugar-0.88: /usr/share/pyshared/sugar/__init__.py
>
> The problem probably is two packages (python-sugar-0.88 and
> python-sugar-toolkit-0.88) sharing the same namespace (package "sugar").
right, but python-sugar-toolkit depends on python-sugar and the __init__.py is
correctly installed in the python-sugar package. I don't see any problem with
this. Or did some version of an python-sugar-toolkit package ship the
__init__.py file?
> I've filed a ticket [1] upstream to avoid this issue for future
> releases
I don't think this is an upstream problem.
This could be either a bug in python-central, or a missing conflict in some
earlier version of the sugar packages.
I'd suggest to build with (env var) DH_PYCENTRAL=include-links; the packages are
arch dependent anyway, and you avoid the symlinking at install time.
Matthias
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
