From: "Ondřej Lysoněk" <olysonek@redhat.com>
To: lm-sensors@vger.kernel.org
Cc: Aurelien Jarno <aurelien@aurel32.net>,
Jean Delvare <jdelvare@suse.de>,
linux-hwmon@vger.kernel.org
Subject: Re: libsensors soname bump
Date: Mon, 17 Dec 2018 13:06:38 +0100 [thread overview]
Message-ID: <7b96e7c3-11d6-a06f-53a6-1d61be31c3b3@redhat.com> (raw)
In-Reply-To: <20181217112713.jvobrvrmxpkfeshi@aurel32.net>
Hi lm-sensors list,
We're currently considering reverting the undue libsensors soname change
that happened in lm_sensors 3.5.0 (see below, the whole thread should be
available on spinics [1]). Would that pose a major problem for anyone?
Thanks!
[1] https://www.spinics.net/lists/linux-hwmon/msg04837.html
Best regards
Ondřej Lysoněk
On 17. 12. 18 12:27, Aurelien Jarno wrote:
> On 2018-12-17 11:59, Jean Delvare wrote:
>> On Mon, 17 Dec 2018 11:35:46 +0100, Ondřej Lysoněk wrote:
>>> I mean, I would love to revert the soname change, however doing so now
>>> seems like a bad thing to do - people may have already adopted
>>> lm_sensors 3.5.0. So I'd like to avoid reverting the change unless there
>>> is a good justification to do so.
>>
>> It's not in Debian yet:
>> https://packages.debian.org/sid/lm-sensors
>
> It's available in the experimental suite with the soname change:
> https://packages.debian.org/experimental/lm-sensors
>
> And it's waiting for a transition slot to rebuild all the
> reverse dependencies in sid:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915790
>
> So on the Debian side, there is still time to revert the soname change.
>
> Aurelien
>
next prev parent reply other threads:[~2018-12-17 12:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-16 11:43 libsensors soname bump Jean Delvare
2018-12-17 9:46 ` Ondřej Lysoněk
2018-12-17 10:35 ` Ondřej Lysoněk
2018-12-17 10:59 ` Jean Delvare
2018-12-17 11:27 ` Aurelien Jarno
2018-12-17 11:48 ` Ondřej Lysoněk
2018-12-17 12:06 ` Ondřej Lysoněk [this message]
2018-12-17 10:48 ` Jean Delvare
2018-12-18 17:06 ` Ondřej Lysoněk
2018-12-19 15:10 ` Jean Delvare
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7b96e7c3-11d6-a06f-53a6-1d61be31c3b3@redhat.com \
--to=olysonek@redhat.com \
--cc=aurelien@aurel32.net \
--cc=jdelvare@suse.de \
--cc=linux-hwmon@vger.kernel.org \
--cc=lm-sensors@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).