Your message dated Sat, 26 Mar 2022 20:35:49 +0000
with message-id <e1nyd8x-000fpx...@fasolo.debian.org>
and subject line Bug#1008150: fixed in grpc 1.44.0-2
has caused the Debian Bug report #1008150,
regarding libgrpc-dev: library name conflict with libupb-dev: libupb.so*
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 ow...@bugs.debian.org
immediately.)


-- 
1008150: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008150
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libgrpc-dev
Version: 1.44.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install
because it tries to overwrite other packages files.

>From the attached log (scroll to the bottom...):

  Preparing to unpack .../libgrpc-dev_1.44.0-1_amd64.deb ...
  Unpacking libgrpc-dev:amd64 (1.44.0-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libgrpc-dev_1.44.0-1_amd64.deb (--unpack):
   trying to overwrite '/usr/lib/x86_64-linux-gnu/libupb.so', which is also in 
package libupb-dev:amd64 0.0.0~git200730-1
  Errors were encountered while processing:
   /var/cache/apt/archives/libgrpc-dev_1.44.0-1_amd64.deb

upb and grpc seem to be two unrelated projects, unfortunately
grpc/experimental started to use a library name already used by upb.
They use different SOVERSIONs right now, so the conflict is only
on the .so link.

Adding mutual Conflicts is not a valid solution here!


cheers,

Andreas

Attachment: libupb-dev=0.0.0~git200730-1_libgrpc-dev=1.44.0-1.log.gz
Description: application/gzip


--- End Message ---
--- Begin Message ---
Source: grpc
Source-Version: 1.44.0-2
Done: Laszlo Boszormenyi (GCS) <g...@debian.org>

We believe that the bug you reported is fixed in the latest version of
grpc, 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 1008...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Laszlo Boszormenyi (GCS) <g...@debian.org> (supplier of updated grpc 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 ftpmas...@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Wed, 23 Mar 2022 18:32:16 +0100
Source: grpc
Architecture: source
Version: 1.44.0-2
Distribution: experimental
Urgency: medium
Maintainer: Laszlo Boszormenyi (GCS) <g...@debian.org>
Changed-By: Laszlo Boszormenyi (GCS) <g...@debian.org>
Closes: 1008150
Changes:
 grpc (1.44.0-2) experimental; urgency=medium
 .
   * Use DEB_HOST_MULTIARCH for libdir and friends.
   * Make libgrpc-dev conflict with libupb-dev (closes: #1008150).
   * Adjust ruby packaging for new gem2deb versions.
   * Add ruby autopkgtest.
Checksums-Sha1:
 6d3f8ff7139106afb4269aba6ff5313e2a7d252b 2798 grpc_1.44.0-2.dsc
 5d87b160a398a1ff17a5aa200e06638da9494879 19476 grpc_1.44.0-2.debian.tar.xz
Checksums-Sha256:
 04e124ccea39c7de8171a44561e555d483a0959775aedab80187b5d586eb29c5 2798 
grpc_1.44.0-2.dsc
 ab1dbba46abb83585a7a8c81fe301fe6aff8858f8a78e3492c5e36aef0f59c64 19476 
grpc_1.44.0-2.debian.tar.xz
Files:
 3b9811f4488525b23cc8c5f7aa001957 2798 libs optional grpc_1.44.0-2.dsc
 9814940aa175c8d22dad44079b0cbadb 19476 libs optional 
grpc_1.44.0-2.debian.tar.xz

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

iQIzBAEBCgAdFiEEfYh9yLp7u6e4NeO63OMQ54ZMyL8FAmI/dA0ACgkQ3OMQ54ZM
yL91Xw/+KJqOni8aIOg3SyuI9SCTMSw4P1kCaZm/YC9gG/S5Dg/ZwWLeHuT07PSh
eXga/BFBU5ulNusf1HwWwVz0W4QOxyvm1ehQvDSUsdaeyaLSBachcixebAvcFh4f
MMFTo/vWN4twcqKm7+e29w1InC2Tx7rqisrphlz/eaAJSgVCIb6mNOu6SIHr37zb
wMjiie3djzJnHuAlAY4S1A+671yaQQALTohVIlORoCoguplXj5xef6QZrBDvUrpp
J9+lmWQ+BPH4u1yJh+8SZNrfZ1Y5sAqf1t57BAG8/iUC88E6sf/8XbENOz39Z+oD
HHoxdEYDZyVpZKCtzJOSUdlZ/JYc9GljR4KxMQqim28RB7HjlNHOVhOYT8ChXvmK
n/tqhGDZjmSxauKdJoOQOHMnxxokc+BCzcLM1GbujZnV1WI3HEvwjOApSwJDeSfa
qkh/CvdHy3PtChHjsA+Ioo4IBE6/yzQf3OYVfuOgnmvVrS8fz789cJBbVlTFDi97
9k8RvKYD4HMJ4WYZaOUyfEtOmEcqFSQh+UVT99PCyZCxdGi2nmNhmUrLnwVA5xhT
r2nt6NAtFMEE6QG9ugTdvcR1llIolAvMHw8MhaSvnGF4SPvdr1Hv/aKrUOplJHXG
5V30z4jISEIAEYuf6hDZs4oT6IUhxrvVbMd1bjhIP6LhTsdyq8c=
=MiWN
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to