Repo coherency e.i. oneTBB.

bartus · 2021-12-17 15:34:52

Doesn't Arch have any cooldown time for new package landing in the repo, preventing repo decoherence when dependency got updated but packages relying on those still expect deprecated features? I know there's one for link-time dependencies mainly `sogrep` but lately, after `tbb:2021` has landed in repo some packages shipped in Arch repo still have references to dropped `tbb::atmoic` in their headers e.g: usd, cgal.

lahwaacz · 2021-12-17 17:24:44

Arch's cgal package is heavily outdated at its current version 4.14.3... And CGAL even considers its dependency on TBB as optional. Do you have a better example?

mpan · 2021-12-17 17:26:32

If a package on a properly updated system is broken, because it requires an older version of a dependency or a dependency that doesn’t exist in the repos, that is a bug and should be reported, so the maintainers could fix it. In particular if a dependency has been dropped, but a package still depends on it, it’s an omission that should be addressed.

Repos containing older versions would not solve that problem, as there would be no way to install them without causing a partial upgrade.

progandy · 2021-12-17 17:33:25

lahwaacz wrote:

Arch's cgal package is heavily outdated at its current version 4.14.3...

As of today, there is a rebuild in community-testing for that package.

The next prusa-slicer release (2.4) will probably allow the upgrade to cgal 5.x, though. openscad should support building with the new cgal already.

No idea what happened with tbb, though. Most packages that depend on it were rebuilt ~2 weeks ago.
Edit: "Prepare for Python 3.10 rebuild" is in the git for usd. The overlap with that might have caused this oversight.

Last edited by progandy (2021-12-17 17:38:18)

lahwaacz · 2021-12-17 18:54:37

W.r.t. what happened to tbb: some of its updates were likely not pushed to the repo by, since the database from 2021/11/29 contains tbb-2020.3-1, but the git repo contains 4 more versions before the tbb-2021.4.0-2 hit the repo due to the Python 3.10 rebuild. I guess it was by mistake and the breakage due to tbb is just because "the version jumped too much"...

Scimmia · 2021-12-17 23:11:02

Since the OP doesn't seem to be doing it, I'll just point out that the complaint in this thread is invalid.

https://bugs.archlinux.org/task/73063

bartus · 2021-12-17 23:34:32

Scimmia wrote:

...complaint in this thread is invalid.

Yes, sorry for the confusion, it was my bug report witch I too hastily asserted to be cgal fault.

Besides that I assume there's no contingency plan other than relying on the bug reports

Last edited by bartus (2021-12-17 23:38:34)

Arch Linux

#1 2021-12-17 15:34:52

Repo coherency e.i. oneTBB.

#2 2021-12-17 17:24:44

Re: Repo coherency e.i. oneTBB.

#3 2021-12-17 17:26:32

Re: Repo coherency e.i. oneTBB.

#4 2021-12-17 17:33:25

Re: Repo coherency e.i. oneTBB.

#5 2021-12-17 18:54:37

Re: Repo coherency e.i. oneTBB.

#6 2021-12-17 23:11:02

Re: Repo coherency e.i. oneTBB.

#7 2021-12-17 23:34:32

Re: Repo coherency e.i. oneTBB.

Board footer