Bug#917448: razorqt: Please switch Build-Depends to libsensors-dev from libsensors4-dev

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Bug#917448: razorqt: Please switch Build-Depends to libsensors-dev from libsensors4-dev

Manuel A. Fernandez Montecelo-2
Hi,

2018-12-27 18:53 Aurelien Jarno:

>Source: razorqt
>Version: 0.5.2-4
>Severity: minor
>User: [hidden email]
>Usertags: libsensors-dev-transition
>
>Dear maintainer,
>
>razorqt 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. As
>razorqt uses a versioned build-depends, it is not enough to replace
>libsensors4-dev by libsensors-dev in debian/control. However the
>current build-depends version being satisfied in oldstable, it is safe
>to just drop the version, and replace it by a simple build-depends
>on libsensors-dev.
>
>Would it be possible to do that in the next upload?

For when is this scheduled, post-freeze?

I had plans (hopes?) to drop the package without any more uploads by the
time that Qt4 was removed, which not sure if it will happen in this
cycle, probably not.

But this package is dead upstream for years, I only didn't ask for
removal because it's got 100~200 users, presumably it's useful for some
of them (and I use it from time to time in several systems), and by not
removing it's easier to do emergency fixes if needed.


Cheers.
--
Manuel A. Fernandez Montecelo <[hidden email]>

Reply | Threaded
Open this post in threaded view
|

Bug#917448: razorqt: Please switch Build-Depends to libsensors-dev from libsensors4-dev

Aurelien Jarno-2
Hi Manuel,

On 2018-12-27 19:26, Manuel A. Fernandez Montecelo wrote:

> Hi,
>
> 2018-12-27 18:53 Aurelien Jarno:
> > Source: razorqt
> > Version: 0.5.2-4
> > Severity: minor
> > User: [hidden email]
> > Usertags: libsensors-dev-transition
> >
> > Dear maintainer,
> >
> > razorqt 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. As
> > razorqt uses a versioned build-depends, it is not enough to replace
> > libsensors4-dev by libsensors-dev in debian/control. However the
> > current build-depends version being satisfied in oldstable, it is safe
> > to just drop the version, and replace it by a simple build-depends
> > on libsensors-dev.
> >
> > Would it be possible to do that in the next upload?
>
> For when is this scheduled, post-freeze?
Technically this can be done as soon as the two packages using
versioned build-dependency on libsensors4-dev (razorqt and wmtemp) have
been changed. Now I don't plan to push that more than necessary, so I'll
send a reminder something like 6 months before the *Bullseyes* freeze,
if these two packages haven't been changed at that time.

In short you have plenty of time.

Cheers,
Aurelien

--
Aurelien Jarno                          GPG: 4096R/1DDD8C9B
[hidden email]                 http://www.aurel32.net

signature.asc (849 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Bug#917448: razorqt: Please switch Build-Depends to libsensors-dev from libsensors4-dev

Manuel A. Fernandez Montecelo-2
2018-12-27 20:57 Aurelien Jarno:

>Hi Manuel,
>
>> For when is this scheduled, post-freeze?
>
>Technically this can be done as soon as the two packages using
>versioned build-dependency on libsensors4-dev (razorqt and wmtemp) have
>been changed. Now I don't plan to push that more than necessary, so I'll
>send a reminder something like 6 months before the *Bullseyes* freeze,
>if these two packages haven't been changed at that time.
>
>In short you have plenty of time.

OK, so if you don't mind the wait, I think that I'd better wait for a
few months to see if the usage drops dramatically (e.g. when the new
release), or if Qt4 is finally removed, which I thought that it would
happen by now.  In any case, I'd like to get it removed before Bullseye
is released; and if it becomes a problem for libsensors for any reason,
I can fix it more actively.

It's not too much work, but I'd like to avoid to give the impression
that this package is alive by uploading after several years; but at the
same time I am still reluctant to remove it from the archive...

--
Manuel A. Fernandez Montecelo <[hidden email]>