[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#897359: marked as done (libmarco-private1 is marked Multi-Arch: same but is not coinstallable)



Your message dated Thu, 05 Jul 2018 13:41:11 +0000
with message-id <E1fb4VT-0009ue-Mu@fasolo.debian.org>
and subject line Bug#897359: fixed in marco 1.20.2-1
has caused the Debian Bug report #897359,
regarding libmarco-private1 is marked Multi-Arch: same but is not coinstallable
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
897359: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897359
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: libmarco-private1
Version: 1.20.1-1
Severity: normal

Dear Maintainer,

Trying to install the amd64 and i386 versions of this package results in the 
following error:

# apt-get install libmarco-private1:amd64 libmarco-private1:i386
[...]
Unpacking libmarco-private1:i386 (1.20.1-1) ...
dpkg: dependency problems prevent configuration of libmarco-private1:i386:
 libmarco-private1:amd64 (1.20.1-1) breaks libmarco and is installed.
  libmarco-private1:i386 (1.20.1-1) provides libmarco.

dpkg: error processing package libmarco-private1:i386 (--configure):
 dependency problems - leaving unconfigured
Processing triggers for libc-bin (2.27-3) ...
Errors were encountered while processing:
 libmarco-private1:i386
E: Sub-process /usr/bin/dpkg returned an error code (1)

So the source of the issue seems to be that libmarco-private1:
* Provides the libmarco virtual package
* Breaks + Replaces the libmarco virtual package

Apt seems to consider that this means libmarco-private1:amd64 breaks 
libmarco-private1:i386 through the libmarco virtual package which prevents them 
from being coinstalled.

One strange thing is that, if I understand 7.6.1 of the Debian Policy Manual 
correctly, Breaks + Replaces is not supposed to be used on virtual packages:
http://www.chiark.greenend.org.uk/doc/debian-policy/policy.html/ch-relationships.html#s7.6.1

| For this usage of Replaces, virtual packages (see Virtual packages - Provides, 
| Section 7.5) are not considered when looking at a Replaces field. The packages 
| declared as being replaced must be mentioned by their real names.

Maybe that's why Apt is confused in this multi-arch configuration.


Note that, based on 7.6.2, the usual pattern would be to Provides + Conflicts + 
Replaces on a virtual package:

|  In this situation, the package declared as being replaced can be a virtual 
|  package, so for example, all mail transport agents (MTAs) would have the 
|  following fields in their control files:
|
|     Provides: mail-transport-agent
|     Conflicts: mail-transport-agent
|     Replaces: mail-transport-agent
|
| ensuring that only one MTA can be unpacked at any one time

Seems like something to try to see if it fixes the issue.


-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.15.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages libmarco-private1 depends on:
ii  libatk1.0-0               2.28.1-1
ii  libc6                     2.27-3
ii  libcairo-gobject2         1.15.10-3
ii  libcairo2                 1.15.10-3
ii  libcanberra-gtk3-0        0.30-6
ii  libcanberra0              0.30-6
ii  libgdk-pixbuf2.0-0        2.36.11-2
ii  libglib2.0-0              2.56.1-2
ii  libgtk-3-0                3.22.29-3
ii  libgtop-2.0-11            2.38.0-2
ii  libice6                   2:1.0.9-2
ii  libpango-1.0-0            1.42.0-1
ii  libpangocairo-1.0-0       1.42.0-1
ii  libsm6                    2:1.2.2-1+b3
ii  libstartup-notification0  0.12-5
ii  libx11-6                  2:1.6.5-1
ii  libxcomposite1            1:0.4.4-2
ii  libxcursor1               1:1.1.15-1
ii  libxdamage1               1:1.1.4-3
ii  libxext6                  2:1.3.3-1+b2
ii  libxfixes3                1:5.0.3-1
ii  libxinerama1              2:1.1.3-1+b3
ii  libxpresent1              1.0.0-2+b10
ii  libxrandr2                2:1.5.1-1
ii  libxrender1               1:0.9.10-1

libmarco-private1 recommends no packages.

libmarco-private1 suggests no packages.

-- no debconf information

--- End Message ---
--- Begin Message ---
Source: marco
Source-Version: 1.20.2-1

We believe that the bug you reported is fixed in the latest version of
marco, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 897359@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Mike Gabriel <sunweaver@debian.org> (supplier of updated marco package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Thu, 05 Jul 2018 14:14:12 +0200
Source: marco
Binary: marco marco-common libmarco-private1 libmarco-dev
Architecture: source
Version: 1.20.2-1
Distribution: unstable
Urgency: medium
Maintainer: Debian+Ubuntu MATE Packaging Team <debian-mate@lists.debian.org>
Changed-By: Mike Gabriel <sunweaver@debian.org>
Description:
 libmarco-dev - library for Marco window manager (development files)
 libmarco-private1 - library for Marco window manager
 marco      - lightweight GTK+ window manager for MATE
 marco-common - lightweight GTK+ window manager for MATE (common files)
Closes: 897359
Changes:
 marco (1.20.2-1) unstable; urgency=medium
 .
   * New upstream release.
   * debian/control:
     + Update Vcs-*: fields. Package has been migrated to salsa.debian.org.
     + Bump Standards-Version: to 4.1.4. No changes needed.
     + Drop from P (libmarco-private0): libmarco. (Closes: #897359).
     + Drop pkg-mate-team Alioth mailing list from Uploaders: field.
   * debian/copyright:
     + Make Upstream-Name: field's value more human readable.
     + Update Upstream-Contact: field.
     + Update Source: field. Use secure URLs.
   * debian/upstream/metadata:
     + Add file. Be compliant with DEP-12 proposal.
     + Use Martin's address as Contact: address.
   * debian/patches:
     + Drop all patches. Applied upstream now.
Checksums-Sha1:
 9f4d4db26754026f2cf2bc2c6ee34eff07556f6c 2644 marco_1.20.2-1.dsc
 7e34ceb634e218573196cbb3060546462a139570 1135416 marco_1.20.2.orig.tar.xz
 11e15e560654c0f81092b0babf51ed5b4ba1f2db 10236 marco_1.20.2-1.debian.tar.xz
 de5d6b828c189381d8e12a2c9190d405d90ebbf4 16366 marco_1.20.2-1_source.buildinfo
Checksums-Sha256:
 24f53c55955e7667f5096c4ec8b6268b2ff45ea9fc4dd1e03e876603babe295e 2644 marco_1.20.2-1.dsc
 a163ee2679daf5467230046323714062e0e8de5ca4f1725c76c622f33475912e 1135416 marco_1.20.2.orig.tar.xz
 06ae55332d494c06851e7cc0906d24cc273f6caff66ebad6e32c8e84b7860570 10236 marco_1.20.2-1.debian.tar.xz
 3c1d48de979d2b041ce3be4757d1951f10e679012c50406d5cbfcd2f71b4d47c 16366 marco_1.20.2-1_source.buildinfo
Files:
 1f7f958a7867418e0a65587bd8e247f8 2644 x11 optional marco_1.20.2-1.dsc
 261883346ce35c5751002fa162a18b4a 1135416 x11 optional marco_1.20.2.orig.tar.xz
 32725df303b11c275d8d28d4fa52e759 10236 x11 optional marco_1.20.2-1.debian.tar.xz
 09f8517e89e3503421788ded8970f6c6 16366 x11 optional marco_1.20.2-1_source.buildinfo

-----BEGIN PGP SIGNATURE-----

iQJJBAEBCAAzFiEEm/uu6GwKpf+/IgeCmvRrMCV3GzEFAls+GewVHHN1bndlYXZl
ckBkZWJpYW4ub3JnAAoJEJr0azAldxsxDbYQAJaZ1T2dSlmeIoYsXImhGXZUg0Xw
Dve4BBFcVK6vlhWIWhr4Zbo75dmWv6sUarTWdLn0sTs5UyHfmnKksdXXVgKU/ZMf
3sFkOlksbxTUFPRHZ/F+bpXy0F3iOi8YXweTiirMxGfTzG+kSNK9yhW1pCG5kVjW
h4RSp5+0PGJZ+A3C/MD0IPrF/u4kGr66z0oyOicHM55iP5yj1rcn6lsI6Q+v+m/n
bUvsOaip/qSCcto2NkAsZhn3wF4NcfnNntc+YFZRGt+v6OrxOpJqud2k/hauvPYG
wiFE9/vm4scwI5arr2pI6+06A80QagBHBZL1GkB+QipnfNX1N9WCaJD2wdFgb8iE
+UMHvYDIDa/v2NrltSG2EvYi0D9pkMfFiGPu8SONTIzlsurgQel+61OPP+2ZVPwj
WwOuFOSCZVDgjPIzf+khsUxFc/o+mTdBXJJixi1c8ZBYsdYMfUCdUIi0J4QkrAaO
Ac8YpAk78/xeCa7HLYhOepcux6j+xLvJ+f3jgjm2/uDOr4DJcEP/vmdlJbIfvUc6
vlbN8Y2eeqzW/BYQxJZ7GEtQzwlZDj1nFHPJenVgnWeOC3MaqQR/QDdi+XZp3V7y
kbheUXf+YJ3CsepV/ybSqh+kemf5jC/MI+3QojSGrOq6M06myzaIkg33XzkCyJFO
K5+p3Ei17vIdL+C3
=XD4d
-----END PGP SIGNATURE-----

--- End Message ---

Reply to: