From: tornaria <tornaria@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: isl: update to 0.22.1
Date: Sun, 28 Feb 2021 01:06:33 +0100 [thread overview]
Message-ID: <20210228000633.aan80mIHWImhSunxs0IwQ2nOowIogtaDYWtyrhRGDk0@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-24424@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 3644 bytes --]
New comment by tornaria on void-packages repository
https://github.com/void-linux/void-packages/pull/24424#issuecomment-787207372
Comment:
> Is it fine to revbump just `cloog` instead?
I think so. What 99-pkglint is doing is:
- it realizes that the soname for the library in this package has changed from `libisl.so.10` to `libisl.so.23`, but you haven't updated `common/shlibs` to match.
- because of that, it runs `xbps-query -Rs libisl.so -p shlib-requires` to find packages that shlib-require `libisl.so.10` and suggests that you revbump them, so they are recompiled against `libisl.so.23`.
However note:
```
$ xbps-query -Rs libisl.so -p shlib-requires
avr-gcc-9.3.0_1: libisl.so.19 (https://alpha.de.repo.voidlinux.org/current)
cloog-0.18.4_2: libisl.so.10 (https://alpha.de.repo.voidlinux.org/current)
cross-aarch64-linux-gnu-0.34_1: libisl.so.19 (https://alpha.de.repo.voidlinux.org/current)
cross-aarch64-linux-musl-0.34_2: libisl.so.19 (https://alpha.de.repo.voidlinux.org/current)
cross-arm-linux-gnueabi-0.34_1: libisl.so.19 (https://alpha.de.repo.voidlinux.org/current)
cross-arm-linux-gnueabihf-0.34_1: libisl.so.19 (https://alpha.de.repo.voidlinux.org/current)
cross-arm-linux-musleabi-0.34_2: libisl.so.19 (https://alpha.de.repo.voidlinux.org/current)
cross-arm-linux-musleabihf-0.34_2: libisl.so.19 (https://alpha.de.repo.voidlinux.org/current)
cross-arm-none-eabi-gcc-9.3.0_1: libisl.so.19 (https://alpha.de.repo.voidlinux.org/current)
cross-armv7l-linux-gnueabihf-0.34_1: libisl.so.19 (https://alpha.de.repo.voidlinux.org/current)
cross-armv7l-linux-musleabihf-0.34_2: libisl.so.19 (https://alpha.de.repo.voidlinux.org/current)
cross-i686-linux-musl-0.34_2: libisl.so.19 (https://alpha.de.repo.voidlinux.org/current)
cross-i686-pc-linux-gnu-0.34_1: libisl.so.19 (https://alpha.de.repo.voidlinux.org/current)
cross-mips-linux-musl-0.34_1: libisl.so.19 (https://alpha.de.repo.voidlinux.org/current)
cross-mips-linux-muslhf-0.34_1: libisl.so.19 (https://alpha.de.repo.voidlinux.org/current)
cross-mipsel-linux-musl-0.34_1: libisl.so.19 (https://alpha.de.repo.voidlinux.org/current)
cross-mipsel-linux-muslhf-0.34_1: libisl.so.19 (https://alpha.de.repo.voidlinux.org/current)
cross-or1k-none-elf-gcc-10.2.0_1: libisl.so.19 (https://alpha.de.repo.voidlinux.org/current)
cross-powerpc-linux-gnu-0.34_1: libisl.so.19 (https://alpha.de.repo.voidlinux.org/current)
cross-powerpc-linux-musl-0.34_1: libisl.so.19 (https://alpha.de.repo.voidlinux.org/current)
cross-powerpc64-linux-gnu-0.34_1: libisl.so.19 (https://alpha.de.repo.voidlinux.org/current)
cross-powerpc64-linux-musl-0.34_2: libisl.so.19 (https://alpha.de.repo.voidlinux.org/current)
cross-powerpc64le-linux-gnu-0.34_1: libisl.so.19 (https://alpha.de.repo.voidlinux.org/current)
cross-powerpc64le-linux-musl-0.34_2: libisl.so.19 (https://alpha.de.repo.voidlinux.org/current)
cross-powerpcle-linux-gnu-0.34_1: libisl.so.19 (https://alpha.de.repo.voidlinux.org/current)
cross-powerpcle-linux-musl-0.34_1: libisl.so.19 (https://alpha.de.repo.voidlinux.org/current)
cross-x86_64-linux-musl-0.34_1: libisl.so.19 (https://alpha.de.repo.voidlinux.org/current)
```
You see here that only `cloog` shlib-requires `libisl.so.10`, the compilers require `libisl.so.19`.
If you want to be sure:
```
$ xbps-query -Rs libisl.so.10 -p shlib-requires
cloog-0.18.4_2: libisl.so.10 (https://alpha.de.repo.voidlinux.org/current)
```
I think if you just update the one line in `common/shlibs` for `isl` (keeping the line for `isl15` intact), the error should go away. You should also revbump cloog, but nothing else.
Could you try that?
prev parent reply other threads:[~2021-02-28 0:06 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-22 18:22 [PR PATCH] " dkwo
2020-08-22 18:38 ` pullmoll
2020-08-23 9:06 ` dkwo
2020-08-23 12:41 ` pullmoll
2020-08-23 12:49 ` pullmoll
2020-10-02 8:18 ` pullmoll
2020-10-02 8:18 ` [PR PATCH] [Closed]: " pullmoll
2020-10-17 13:41 ` dkwo
2021-01-25 16:39 ` dkwo
2021-02-24 12:41 ` tornaria
2021-02-24 13:58 ` dkwo
2021-02-24 14:22 ` dkwo
2021-02-24 15:12 ` dkwo
2021-02-27 22:08 ` dkwo
2021-02-28 0:06 ` tornaria [this message]
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=20210228000633.aan80mIHWImhSunxs0IwQ2nOowIogtaDYWtyrhRGDk0@z \
--to=tornaria@users.noreply.github.com \
--cc=ml@inbox.vuxu.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).