All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jean Delvare <jdelvare@suse.de>
To: "Ondřej Lysoněk" <olysonek@redhat.com>
Cc: linux-hwmon@vger.kernel.org, Aurelien Jarno <aurelien@aurel32.net>
Subject: Re: libsensors soname bump
Date: Mon, 17 Dec 2018 11:59:02 +0100	[thread overview]
Message-ID: <20181217115902.15e538fe@endymion> (raw)
In-Reply-To: <3799b201-38f9-d74f-273d-f819736dcfb6@redhat.com>

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

Gentoo have picked it but it is still in testing:
https://packages.gentoo.org/packages/sys-apps/lm_sensors

You'll know better than I do about Fedora.

For openSUSE, I have packaged lm-sensors 3.5.0 but with a patch
reverting the undue soname change. I used "4.5.0" instead. I intend to
carry this patch for as long as I have to. This goes against our policy
of sticking to upstream as much as possible, but in this specific case,
I consider it the least of 2 evils.

Thanks,
-- 
Jean Delvare
SUSE L3 Support

  reply	other threads:[~2018-12-17 10:59 UTC|newest]

Thread overview: 13+ 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 [this message]
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
2018-12-17 12:06           ` Ondřej Lysoněk
2018-12-17 10:48   ` Jean Delvare
2018-12-18 17:06 ` Ondřej Lysoněk
2018-12-18 17:06   ` Ondřej Lysoněk
2018-12-19 15:10   ` Jean Delvare
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=20181217115902.15e538fe@endymion \
    --to=jdelvare@suse.de \
    --cc=aurelien@aurel32.net \
    --cc=linux-hwmon@vger.kernel.org \
    --cc=olysonek@redhat.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.