Your message dated Mon, 29 Jul 2024 15:20:28 +0000
with message-id <[email protected]>
and subject line Bug#1077494: fixed in libyang3 3.1.0+dfsg-4
has caused the Debian Bug report #1077494,
regarding libyang3-dev has an undeclared file conflict
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 [email protected]
immediately.)
--
1077494: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1077494
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: libyang3-dev
Version: 3.1.0+dfsg-3
Severity: serious
User: [email protected]
Usertags: fileconflict
Control: affects -1 + libyang-dev libyang2-dev
libyang3-dev has an undeclared file conflict. This may result in an
unpack error from dpkg.
The files
* /usr/lib/x86_64-linux-gnu/libyang.so
* /usr/lib/x86_64-linux-gnu/pkgconfig/libyang.pc
are contained in the packages
* libyang-dev/1.0.225-1.1 as present in bullseye
* libyang2-dev
* 2.1.148-0.1 as present in trixie|unstable
* 2.1.30-2 as present in bookworm
* libyang3-dev/3.1.0+dfsg-3 as present in unstable
These packages can be unpacked concurrently, because there is no
relevant Replaces or Conflicts relation. Attempting to unpack these
packages concurrently results in an unpack error from dpkg, because none
of the packages installs a diversion for the affected files.
Kind regards
The Debian Usr Merge Analysis Tool
This bug report has been automatically filed with no human intervention.
The source code is available at https://salsa.debian.org/helmutg/dumat.
If the filing is unclear or in error, don't hesitate to contact
[email protected] for assistance.
--- End Message ---
--- Begin Message ---
Source: libyang3
Source-Version: 3.1.0+dfsg-4
Done: Daniel Baumann <[email protected]>
We believe that the bug you reported is fixed in the latest version of
libyang3, 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 [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Daniel Baumann <[email protected]> (supplier of updated
libyang3 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 [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Mon, 29 Jul 2024 15:29:51 +0200
Source: libyang3
Architecture: source
Version: 3.1.0+dfsg-4
Distribution: sid
Urgency: medium
Maintainer: Daniel Baumann <[email protected]>
Changed-By: Daniel Baumann <[email protected]>
Closes: 1077494
Changes:
libyang3 (3.1.0+dfsg-4) sid; urgency=medium
.
* Uploading to sid.
* Adding missing conflicts/replaces to libyang-dev and libyang2-dev
(Closes: #1077494).
Checksums-Sha1:
fce0cde372eacde1e0bb5360e1207194fade5c52 2193 libyang3_3.1.0+dfsg-4.dsc
640fe7ae9b5bafa47d58b2d374d6d57d1c864e7e 3296
libyang3_3.1.0+dfsg-4.debian.tar.xz
02f0720da1061c70aafea6b9645ac9dbfe47114a 10624
libyang3_3.1.0+dfsg-4_amd64.buildinfo
Checksums-Sha256:
06ebc547426cebbf22fb52003be983e3debfc8c667ffc09a610c94f83ddc58af 2193
libyang3_3.1.0+dfsg-4.dsc
e627024c63bf236fc03bf71f2b925195967f8d8383d19389eb8a0a385f3d86da 3296
libyang3_3.1.0+dfsg-4.debian.tar.xz
b52741edc500265a27e279a0b9076b8734d46538e423010a15df8f040169abe2 10624
libyang3_3.1.0+dfsg-4_amd64.buildinfo
Files:
0f1588cab7ea00b37f604230351e342a 2193 libs optional libyang3_3.1.0+dfsg-4.dsc
62dfbbb2132015d6adf5d4455de5bf81 3296 libs optional
libyang3_3.1.0+dfsg-4.debian.tar.xz
b9227d311a536509ff1bce1442537535 10624 libs optional
libyang3_3.1.0+dfsg-4_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEgTbtJcfWfpLHSkKSVc8b+YaruccFAmanmoUACgkQVc8b+Yar
ucc66g//eqB0YMdp6nvhrExYNxEwTQD46S8+Fcp0E4912JWD0UkKRKEt3BL3zUFw
WDEfvQ6kgA4MXVOvFE8UMCrkwSDW7ThwgWtk28FZIiE9hhQ5dx+B+9mFKfSBtBSq
jfLqClKpn+Xi3Su1w3pqeTUCwF0aBYs12RKhe+Om0Zdkno0gh9ytYtzdNUniP/hw
WDCypJd5sg57yeXTcGZ8QdBxo3biXfOZQ3r+nkfrKMrVA8NKERO45tyH2rN13sHJ
ZdfX4ImikN8I/84wjtG2vNu7/+msEVpK2y53xIS+mJruKZaC6/9QbmlEiARY8MAC
MtGo/+PUIWx764Vt6WLO0J++Jbf9lVjNJsllAqramBuDTncnvdS1pEAcbehGySCw
J6Elv30mDD5Gu6Ey3aHqErHQ7UfVmVs1VR08eKy6kRhCdq9MuVe63prBtXrvKulg
1LS4smyr6z4ojavKsf7BtgKwAgES4qCYQr2Z3kAEH6ZfOTwb7s70RKaejXDy1Pm2
fiokTr8H+IpncfjgYAmuqo+WgmeNetkX4vRT7qQdlJP4YU0y0UHgRYFSyZjJ+IjO
xCBpWF84OmPfSB4PeEgpuJKiGKehhgeRLD1ZyN+2fTlVv2Vfmez/uFNMqNHpy/HT
OKFRj8mZoaNC3Pt53uTS9HfU3dPobkM/FWtJ7XX0cj9Fw7TreFM=
=s+go
-----END PGP SIGNATURE-----
pgp6S0kIGZKdh.pgp
Description: PGP signature
--- End Message ---
