Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

OBS: How to check for needed rebuilds? #2

Open
carstene1ns opened this issue Feb 16, 2016 · 4 comments
Open

OBS: How to check for needed rebuilds? #2

carstene1ns opened this issue Feb 16, 2016 · 4 comments
Labels
OBS Related to our packages on the Open Build Service

Comments

@carstene1ns
Copy link
Member

Currently, the builds of Player and liblcf(0) stay the same until someone rebuilds them manually.
Distribution packages are updated in the meantime.
For most shared libraries it makes no difference as the api does not change (i.e. recent SDL updates)
However, ICU will insert it's version information and this forces us to do a rebuild after each ICU update.

For Arch Linux this needs to increment the $pkgrel in the PKGBUILD and I pay attention for updates to the ICU package, so Player will not be 'broken' for long hopefully.
But this needs to be taken care of for the other distributions as well.

@fdelapena
Copy link

Wow, aren't ICU package changes ABI compatible even between pkgrel changes? This looks pretty nonsense 😩
How is liblcf/player breaking when this happens? Is it not possible to require a version or later like pkg-config do but for distro packages configuration? 😞
I don't remember a mass package rebuild in distros I use because of this... strange.
Some distros have a package update monitor system... in case of requiring this, it should be distro (and version) specific.

@Ghabry
Copy link
Member

Ghabry commented Feb 17, 2016

ICU appends the version number to all function calls.

This can be disabled globally via U_DISABLE_RENAMING but the system lib must be compiled with this

Could you check the exported symbols on Debian and Fedora?

@fdelapena
Copy link

Fedora:

$ strings /usr/lib64/libicui18n.so | grep ucsdet_detect
ucsdet_detect_54
ucsdet_detectAll_54

However, ICU major version shouldn't change in non-rolling distros.
I guess this issue only happens in rolling. e.g. openSUSE tumbleweed and Arch and only around every 6 months, current schedule is in the ICU homepage below the table of contents (right side):

2015-10-07  56 Release (56.1)
2016-01-30  57 Milestone 1 (tag only)
2016-03-09  57 Release Candidate
2016-03-23  57 Release (57.1)

But I guess this particular issue has nothing to do with carstene1ns mentions.

@carstene1ns
Copy link
Member Author

Another issue is expired signatures, like #13 mentioned.
Maybe a "cron job" with monthly (or whenever the signatures expire) rebuild is sufficient for now.

@carstene1ns carstene1ns changed the title How to check for needed rebuilds? OBS: How to check for needed rebuilds? Jan 11, 2023
@carstene1ns carstene1ns added the OBS Related to our packages on the Open Build Service label Jan 11, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
OBS Related to our packages on the Open Build Service
Development

No branches or pull requests

3 participants