You are not logged in.

#1 2021-01-31 21:06:50

jetfrog28
Member
Registered: 2018-08-25
Posts: 17

[Solved] Push qt5-webengine 5.15.2-3.0 to testing?

After a full upgrade with testing repos enabled, qt5-webengine 5.15.2-1.0 fails with:

libre2.so.8: cannot open shared object file: No such file or directory

Installing qt5-webengine 5.15.2-3.0 from the staging repos seems to fix it, and I haven't encountered any problems yet.  The package has been in staging since 2020-12-24.  Is there any reason it hasn't been pushed?  I didn't see any mention of it on the bugtracker or in forum posts, but I don't know if those are the only places I should be looking.

Last edited by jetfrog28 (2021-02-01 08:49:24)

Offline

#2 2021-02-01 06:54:09

deep42thought
Administrator
From: Jena, Germany
Registered: 2017-06-17
Posts: 617

Re: [Solved] Push qt5-webengine 5.15.2-3.0 to testing?

I'll move qt5-webengine from [staging] to [testing], lets hope, that not too much other packages break smile

Offline

#3 2021-02-01 08:48:17

jetfrog28
Member
Registered: 2018-08-25
Posts: 17

Re: [Solved] Push qt5-webengine 5.15.2-3.0 to testing?

Thanks! (And thanks for everything you do, I'm really grateful to be able to use this distro).  Hope it goes smoothly.

I'm curious, when do packages normally get moved from [staging] to [testing]?  Is it done manually every time, or is there a level of automation?

Offline

#4 2021-02-01 08:55:47

deep42thought
Administrator
From: Jena, Germany
Registered: 2017-06-17
Posts: 617

Re: [Solved] Push qt5-webengine 5.15.2-3.0 to testing?

They're moved automatically, when all dependencies are available (or can be moved simultanously) and no replaced package is still needed in the target repository (this also checks the version to some degree, and more importantly the linking, which is not visible to pacman). Moving from [testing] to [core]/[extra] is similar, except, that the packages must be reported as good or must have been in testing a few days.

The problem with this approach (and the reason, why we have to implement the "timeout") is, that "high-level" packages can block moving of their dependencies:

Imagine package foo and bar depending on libbar. libbar receives an update and thus foo and bar are also recompiled upstream. If foo fails to build due to some unrelated issue, then libbar will not be moved to [testing], because it would break package foo in [testing].

Offline

#5 2021-02-01 19:52:51

jetfrog28
Member
Registered: 2018-08-25
Posts: 17

Re: [Solved] Push qt5-webengine 5.15.2-3.0 to testing?

That makes sense.  Thanks for the info.

Offline

Board footer

Powered by FluxBB