Your message dated Fri, 12 Nov 2021 11:49:08 +0000
with message-id <e1mlv3m-000e2q...@fasolo.debian.org>
and subject line Bug#998634: fixed in sssd 2.5.2-5
has caused the Debian Bug report #998634,
regarding sssd: Please switch libsemanage1-dev BD to libsemanage-dev
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.)


-- 
998634: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998634
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sssd
Version: 2.4.1-2
Severity: important

Hello,

I'm planning in the following days to upload a new version of libsemange
to unstable.

This new version has bumped the soname, I used this occasion to rename
the -dev package from libsemanage1-dev to libsemanage-dev so it matches
the .pc file and library name.

I tried to rebuild the package and it's building fine with the new
version.

You'll have to adjust the BD at that moment I upload the new version.

Kind regards,

Laurent Bigonville

-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 
'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 5.14.0-3-amd64 (SMP w/8 CPU threads)
Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_BE:fr
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: SELinux: enabled - Mode: Permissive - Policy name: refpolicy

--- End Message ---
--- Begin Message ---
Source: sssd
Source-Version: 2.5.2-5
Done: Timo Aaltonen <tjaal...@debian.org>

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

Debian distribution maintenance software
pp.
Timo Aaltonen <tjaal...@debian.org> (supplier of updated sssd 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: Mon, 08 Nov 2021 21:17:29 +0200
Source: sssd
Built-For-Profiles: noudeb
Architecture: source
Version: 2.5.2-5
Distribution: unstable
Urgency: medium
Maintainer: Debian SSSD Team <pkg-sssd-de...@alioth-lists.debian.net>
Changed-By: Timo Aaltonen <tjaal...@debian.org>
Closes: 998634
Changes:
 sssd (2.5.2-5) unstable; urgency=medium
 .
   * control: Fix libsemanage-dev build-dep. (Closes: #998634)
Checksums-Sha1:
 9546f337573e5ef08421dd97c3eb6d65626a9afe 4956 sssd_2.5.2-5.dsc
 50d27c0c88e86b7a67bb697f08fcf57c5f521dd8 38096 sssd_2.5.2-5.debian.tar.xz
 5755f7fea4fa0aeae319c357b07aab4c3ca2ade4 9764 sssd_2.5.2-5_source.buildinfo
Checksums-Sha256:
 4935edb13dfba5dfc1a76c6313b1eb554eff30434a2d7f636145ea6581b8ce29 4956 
sssd_2.5.2-5.dsc
 7d9946a82a9c57e43e53d52d076bd3a1a4ef01fa638aae78cfa2dfc7fdc25501 38096 
sssd_2.5.2-5.debian.tar.xz
 9cb69530cff13a0ace952e8639ba991e80099cee52fde4ff11d1f63f9f8117e4 9764 
sssd_2.5.2-5_source.buildinfo
Files:
 8408e0d6e3db4aa3acc2fab3e247e95a 4956 utils optional sssd_2.5.2-5.dsc
 125ccc1e350cfb0722dd119de96313e6 38096 utils optional 
sssd_2.5.2-5.debian.tar.xz
 cda44f644485cf498aa1cea49d7c2cea 9764 utils optional 
sssd_2.5.2-5_source.buildinfo

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

iQIzBAEBCgAdFiEEdS3ifE3rFwGbS2Yjy3AxZaiJhNwFAmGJd9sACgkQy3AxZaiJ
hNyXWxAAjQqHuXBAZOhAxunJAx0n7mBkq1OBNwSUG8d9m8ssio+g+6f2mpQpZbj5
g4ZNg0AapRqlQSRRaE2Cpk+XqBnfh66paD33SJ1QQJS1mR1gYmKYmVeCdBZeQJSM
AAjMbRtB/9YbN0Dg9l41pzIU/+PDPJ4OJeu+e6+hy+olaZIo5oDghYSxUubJe3z2
Yl5qfKP7umulL/2i20mj0+kJ1c4X5IKXL2Cdo94qPIDkeEXS114XQ4bd19mMMa3/
qXLhfZ5b6oL9zWmDfs5KOD0b0DD7/gH19PNA3VCAbBy2Vol7mgvkkATuJIy65TwQ
n3k5jH55QcXlBdE4xtsv6jraFaGaWBvO1leuOWwwzBNsEBUs9h1XghSY4mmrHfIB
BzOU+xKaHDx7R6BlR3+FEeOE1VrSsB/s8Ran2opFRk6s9OEv3Um4o0gXr/flIc+y
rb33aPiD86YOozIQF0qw3yrl+m/3TFXM7MFGh+rJBlmQDZLRYBsUqRru/0T7p0bO
wRKSsNs9tyAp/8wlWlFMu7jAsl0hZJTTjViXfBrmlmAkoDgvxyk3B7x39sXwo5Ob
ieqgYQO4TrKsMiXUV7zwetrKT/QzNaWdTKrC1pQcR8mUH+BkDIbXBcMiUCdC/L6B
NxC05YpCUm+N+xu/sZqbuQ9Xr/mZXukOINQWK6GR9DWfoV0u4ug=
=B5td
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to