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

Bug#917436: marked as done (cpufreqd: Please switch Build-Depends to libsensors-dev from libsensors4-dev)

Your message dated Sat, 08 Jul 2023 10:35:51 +0000
with message-id <E1qI5I7-0052wo-DG@fasolo.debian.org>
and subject line Bug#917436: fixed in cpufreqd 2.4.2-4
has caused the Debian Bug report #917436,
regarding cpufreqd: Please switch Build-Depends to libsensors-dev from libsensors4-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 owner@bugs.debian.org
immediately.)


-- 
917436: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917436
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Source: cpufreqd
Version: 2.4.2-2
Severity: wishlist
User: aurel32@debian.org
Usertags: libsensors-dev-transition

Dear maintainer,

cpufreqd build-depends on libsensors4-dev, the development package
from lm-sensors. For historical reasons the development package is
versioned. Following the transition of the library to libsensors5,
it makes sense to rename the development package to libsensors-dev.

In that regard a "Provides: libsensors-dev" has been added. Given
cpufreqd uses a non-versioned Build-Depends it is already safe
to transition your package to use libsensors-dev instead of
libsensors4-dev.

There is no urgency (yet) to do the change, but it would be nice if
you can piggyback that change in the next upload. It should just be
a matter of running:

  sed -i -e 's/libsensors4-dev/libsensors-dev/g' debian/control

Thanks,
Aurelien

--- End Message ---
--- Begin Message --- 
Source: cpufreqd
Source-Version: 2.4.2-4
Done: Aurelien Jarno <aurel32@debian.org>

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

Debian distribution maintenance software
pp.
Aurelien Jarno <aurel32@debian.org> (supplier of updated cpufreqd 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: SHA512

Format: 1.8
Date: Sat, 08 Jul 2023 12:20:49 +0200
Source: cpufreqd
Architecture: source
Version: 2.4.2-4
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group <packages@qa.debian.org>
Changed-By: Aurelien Jarno <aurel32@debian.org>
Closes: 917436
Changes:
 cpufreqd (2.4.2-4) unstable; urgency=medium
 .
   * QA upload.
   * Switch Build-Depends to libsensors-dev from libsensors4-dev (Closes:
     #917436).
Checksums-Sha1:
 9bdd0976deb5de309905469ee9212c11d21f19e3 1874 cpufreqd_2.4.2-4.dsc
 49a1b8667022cf2d3eb66707c379a56bc026c56a 12008 cpufreqd_2.4.2-4.debian.tar.xz
 5e2a347d5ee58e962d21d69937a2f15c97c76623 6020 cpufreqd_2.4.2-4_source.buildinfo
Checksums-Sha256:
 01c03936a46606ff7d8a12cceb8a8495f75d541285c7592003a058254e3687b5 1874 cpufreqd_2.4.2-4.dsc
 bbf6ca5121696906e557882eb93547c831dcebf349f5fb3936dc2b89d3f4d698 12008 cpufreqd_2.4.2-4.debian.tar.xz
 2bcad158b70b58660107a8a25f007ca889696a47d01eaaba778afbab1f0058d0 6020 cpufreqd_2.4.2-4_source.buildinfo
Files:
 732b7c7fe087dd91a309c63d6fc9cdd9 1874 admin optional cpufreqd_2.4.2-4.dsc
 08767c03e3d2624f870e6708a3e9efbf 12008 admin optional cpufreqd_2.4.2-4.debian.tar.xz
 b5ab0035aeba689b77358f5505c45048 6020 admin optional cpufreqd_2.4.2-4_source.buildinfo

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

iQIzBAEBCgAdFiEEUryGlb40+QrX1Ay4E4jA+JnoM2sFAmSpOUEACgkQE4jA+Jno
M2txLA//VpLKDqmvWcTXHgYwfJBtinyY/NyY1+yD6D4JGeOYDb6Sh0M0f2RYMDDw
up70+DI1rlI0fCw4EhhQDjxFxFN2D8EfU6MYU1rMl5vNDGrCHZPPMtcVGKL1ETCc
vXH3cjze+uCXWNG0w0p0yZpbFXWl7NIbA032pRGddnRYzGlVG4mdKJFmkBnWh/aH
/LS/LmeZGTx6PxJseJny496Gt6mzaB3KEGR5eGx+JORXyp0Bi10/5DZArZTFXxyp
s3KGB9UM/Ji4zjzUzkYlCks4Oww/6Ma0VM8goFGeEH2+lCozSDHOzPBmSCyAP5pN
//dCuAGXjBTh0GgsM31afm7FEBQsWYBUybSTXTtb4mT8N3fNU32v1v9jBR9PrvFv
t4f/6ZpgJDzqVoQn6Nw28/YeMIpps+DLB4mQSBbtwmaXJXGQD89lW1hs1btk2uem
1tgrVsLu5SPw+uDB00pT413szfAKBtEMrW7aMLWzpFc1paWnT5mfP4dIgnUnGl1A
RGTWCQ7DHkbXVmVv3bTfzHfvgcgWj8dRDH62tQgkvU/GxKnuV+s4fjYkhIzKBF1U
Di/wqoOsQtrPAiTFmQ7edMoUoq32JEqIQwmF+Ij1FBJaeqQ2CX/Q2Xdf0l4n56CW
Z6lZA9UU+yfYZ45PlMHUYSMV4wjKWjP+ojTlKDG57mdC6jguK1A=
=YU+x
-----END PGP SIGNATURE-----

--- End Message ---
Reply to: