Hi again, Cyril Brulebois <cy...@debamax.com> (2018-12-07): > setup.py doesn't seem to have been updated regarding that data file, > stored in the data_files variable and used in the same way in 3.1.3-1 > and in 3.2.3-1, so I suspect the tooling might have changed (at least > python3-setuptools seems to have been updated several times, without > much details in its debian/changelog). > > I think I won't dig into it much more, and just ACK the image move from > one package to another through the proposed Breaks/Replaces > relationship. > > I'll set up a chroot-based test case, upgrading from older electrum & > python3-electrum packages, checking they fail to upgrade to sid's > packages; then redo this with fixed packages. I'll post the final patch > and upload (possibly to DELAYED) once I'm done with testing.
I can't seem able to trigger a practical issue with the following steps,
with repo1 having 3.1.3-1 in the buster distribution, which I install
first, and 3.2.3-1 in the sid distribution, which I upgrade to later:
sudo debootstrap buster buster-amd64 http://mirror.home/debian
rsync -av repo1 buster-amd64/tmp
sudo chroot buster-amd64
echo 'deb [trusted=yes] file:///tmp/repo1 buster main' >
/etc/apt/sources.list.d/electrum.list
apt-get update
apt-get -y install python3-electrum electrum --no-install-recommends
echo 'deb [trusted=yes] file:///tmp/repo1 sid main' >
/etc/apt/sources.list.d/electrum.list
apt-get update
apt-get -y install electrum
A dpkg feature seems triggered:
Preparing to unpack .../electrum_3.2.3-1_all.deb ...
Unpacking electrum (3.2.3-1) over (3.1.1-1) ...
=> Replaced by files in installed package python3-electrum (3.1.1-1) ...
Preparing to unpack .../python3-electrum_3.2.3-1_all.deb ...
Unpacking python3-electrum (3.2.3-1) over (3.1.1-1) ...
Setting up python3-electrum (3.2.3-1) ...
Processing triggers for mime-support (3.61) ...
Setting up electrum (3.2.3-1) ...
And that seems to happen because of a Replaces relationship the other
way around:
$ dpkg --info python3-electrum_3.2.3-1_all.deb | grep Replaces:
Replaces: electrum, python-electrum
which might be responsible for this (with some debug on the dpkg side):
root@wodi:/tmp/repo1/pool/main/e/electrum# dpkg -D440 -i *3.2.3*
(Reading database ... 11134 files and directories currently installed.)
Preparing to unpack electrum_3.2.3-1_all.deb ...
Unpacking electrum (3.2.3-1) over (3.1.3-1) ...
D000040: does_replace new=electrum:all old=python3-electrum:all (0:3.1.3-1)
D000040: does_replace ... no
D000040: does_replace new=python3-electrum:all old=electrum:all (0:3.2.3-1)
D000400: does_replace ... found old, version <none>
D000040: does_replace ... yes
Replaced by files in installed package python3-electrum (3.1.3-1) ...
Preparing to unpack python3-electrum_3.2.3-1_all.deb ...
Unpacking python3-electrum (3.2.3-1) over (3.1.3-1) ...
[…]
I'm told electrum is an undocumented Tails feature, so I'll probably
disable it for the time being; at least until the maintainer comments on
this bug report.
Cheers,
--
Cyril Brulebois -- Debian Consultant @ DEBAMAX -- https://debamax.com/
signature.asc
Description: PGP signature
