Your message dated Sun, 19 May 2024 17:05:55 +0000
with message-id <e1s8jyt-00hpkl...@fasolo.debian.org>
and subject line Bug#1060608: fixed in libnitrokey 3.7-2
has caused the Debian Bug report #1060608,
regarding libnitrokey: Please switch Build-Depends to systemd-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.)


-- 
1060608: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060608
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libnitrokey
Version: 3.7-1.1
Severity: normal
User: pkg-systemd-maintain...@lists.alioth.debian.org
Usertags: systemd-dev

Hi,

your package libnitrokey declares a Build-Depends on systemd and/or
udev.

In most cases, this build dependency is added to get the paths that
are defined in udev.pc or systemd.pc (via pkgconfig).

Since systemd_253-2 [1], these two pkgconfig files have been split
into a separate package named systemd-dev. This package is arch:all,
so even available on non-Linux architectures, which will simplify the
installation of upstream provided service files / udev rules.

To not make existing source packages FTBFS, the systemd and udev
package have a Depends: systemd-dev. This dependency will be removed
at some point though before trixie is released. Once this happens,
this issue will be bumped to RC.

Please update your build dependencies accordingly at your earliest
convenience.

If all you need is the systemd.pc or udev.pc pkgconfig file, please
replace any systemd or udev Build-Depends with systemd-dev. In most
cases that should be sufficient. If your package needs further
resources from systemd or udev to build successfully, it's fine to
keep those Build-Depends in addition to systemd-dev.

To ease stable backports, a version of systemd with those changes is
provided via bookworm-backports.

In case you have further questions, please contact the systemd team
at <pkg-systemd-maintain...@lists.alioth.debian.org>.

On behalf of the systemd team, Michael

[1]
https://salsa.debian.org/systemd-team/systemd/-/merge_requests/196 

--- End Message ---
--- Begin Message ---
Source: libnitrokey
Source-Version: 3.7-2
Done: Patryk Cisek <pat...@debian.org>

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

Debian distribution maintenance software
pp.
Patryk Cisek <pat...@debian.org> (supplier of updated libnitrokey 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: Sun, 19 May 2024 09:02:22 -0700
Source: libnitrokey
Binary: libnitrokey-common libnitrokey-dev libnitrokey3 libnitrokey3-dbgsym
Architecture: source all amd64
Version: 3.7-2
Distribution: unstable
Urgency: medium
Maintainer: Patryk Cisek <pat...@debian.org>
Changed-By: Patryk Cisek <pat...@debian.org>
Description:
 libnitrokey-common - architecture independent files for libnitrokey
 libnitrokey-dev - library to communicate with Nitrokey stick devices 
(development)
 libnitrokey3 - library to communicate with Nitrokey stick devices
Closes: 1060608
Changes:
 libnitrokey (3.7-2) unstable; urgency=medium
 .
   * Switching Build-Depends from udev to systemd-dev (Closes: #1060608)
Checksums-Sha1:
 c78639ca22fd5d9983d052bae6f15539594fd8a0 1741 libnitrokey_3.7-2.dsc
 56dad396d202ebfecec4e0fc39753e102446afc0 4872 libnitrokey_3.7-2.debian.tar.xz
 d5cdfc7a38f21ca70238ba6e2202d38106cf5a61 6268 libnitrokey-common_3.7-2_all.deb
 3fa1a32ab7031cf53ba79e6488c5d5b5ed97af1e 39644 libnitrokey-dev_3.7-2_amd64.deb
 bed2bc9d26a2a5f023318942b4a317fbf8579d7a 4295776 
libnitrokey3-dbgsym_3.7-2_amd64.deb
 79473d20dea8a1f2d6d50e720e954f472af300be 263292 libnitrokey3_3.7-2_amd64.deb
 0174c1f8479ae4d2070a914f60048e266e7d2362 9964 libnitrokey_3.7-2_amd64.buildinfo
Checksums-Sha256:
 ca94c2531bbb673d3b6bc9655e3cf05c909b23e8427917bd904e50bd804ba609 1741 
libnitrokey_3.7-2.dsc
 5caa647339a18a0a55aaeac6cf2b683b5aff30b961cf2d20ae9517f202d3a8b4 4872 
libnitrokey_3.7-2.debian.tar.xz
 fe1187b43580c15dae0f86192f40031ab4f73c988877085f595ec47ae3bd4cec 6268 
libnitrokey-common_3.7-2_all.deb
 587b70f5b461c5c5e8f1bc66f25d476a092b2ffa6ef32e6befd927cd6b819aba 39644 
libnitrokey-dev_3.7-2_amd64.deb
 89dc8af12c96b7977cebe9b0bf981e7e8da0c495382ef6660154fee9ea8b39a8 4295776 
libnitrokey3-dbgsym_3.7-2_amd64.deb
 ebd0c663ee65c4d52944c0837e06d4d26ee4817c145226ef075b3a60ca662154 263292 
libnitrokey3_3.7-2_amd64.deb
 243b7cbc1f1c67aa1837438a72d1f3f51027871dc0a46ae27101db81bfbd2480 9964 
libnitrokey_3.7-2_amd64.buildinfo
Files:
 9b2c5ea51c406bd370e42602fca278fa 1741 libs optional libnitrokey_3.7-2.dsc
 61dd93b483379b156376881d644a4453 4872 libs optional 
libnitrokey_3.7-2.debian.tar.xz
 9eaf8caed7b9afa4e43dd425e1fa5120 6268 libs optional 
libnitrokey-common_3.7-2_all.deb
 5afae3a6018db6774bdbf2925b05ffc0 39644 libdevel optional 
libnitrokey-dev_3.7-2_amd64.deb
 7e1331fde318565dfffc871edaf6eec0 4295776 debug optional 
libnitrokey3-dbgsym_3.7-2_amd64.deb
 3a407c5b718eb03c6f7f25d96fe81dd2 263292 libs optional 
libnitrokey3_3.7-2_amd64.deb
 8e44097b088a103a4104fdc8093b3d36 9964 libs optional 
libnitrokey_3.7-2_amd64.buildinfo

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

iQFGBAEBCgAwFiEEWOLp/jzhNNGOMgPUXJhqlBtsgvUFAmZKLbYSHHBhdHJ5a0Bk
ZWJpYW4ub3JnAAoJEFyYapQbbIL1CrgIAK5zjIdhp921mvt1tWhWVJsk3aDOX3AH
AFBhy4L/m+UZNSTc2eK0+y5LBPlSerTSrPErhy8/GW+UKqS2WbpAbwll1gcx8ks0
RV8STvCkyBr6aCtC4dzx4HRjjZYY5I1oZOu5qXYZ6mFNTTv0xq6o1EMwN1bKGowm
QN0AWnqBSflwNXYhJ20z6odid7dIQexUJ+6LeNEpJBfLSEz9f0SK1IjIqP5ET7Ch
dG3XzheLtCK2WdAcmK8af9j7/4Ru7oDlmLzUahvyNjrXZ5kJdKxlc6LAgD/gtSnG
XC571gftFCt5hoyGgxAk/x9d3trb2Al8Vlw63us0xuzehXBemj9IhrY=
=yzZS
-----END PGP SIGNATURE-----

Attachment: pgp1kRIqQHw6O.pgp
Description: PGP signature


--- End Message ---

Reply via email to