You are not logged in.

#1 2019-03-05 19:01:33

aliemjay
Member
Registered: 2018-11-17
Posts: 15

[SOLVED] x265 build failure holds back Plasma updates

Hi devs,

The latest commit to x265: https://git.archlinux32.org/archlinux32 … 0bb6b262df,
reverted the previous commit that disables assembly code (accidentally?) causing build failure and Plasma is now stuck in build-list for more than a week  because of that.

I hope this get fixed soon,
Thanks!

Last edited by aliemjay (2019-03-10 15:38:39)

Offline

#2 2019-03-05 21:39:10

levi
Moderator
From: UK
Registered: 2018-06-16
Posts: 243

Re: [SOLVED] x265 build failure holds back Plasma updates

Given the git server reporting that change was made 5 days ago, that shouldn't be the sole cause of build failures since more than a week ago.  But the build server sometimes barfs, so it might have been failing at random for more than two days previous to this change.

At least it's only the pkgbuild needing patching.  That should be easier to revert.

I'll note that the change also eliminates a PFX mnemonic which perhaps was thought to be the only non i686 command (I'm not overly familiar with x86 assembly myself).  I was under the impression that too new mnemonics don't cause build failures too; I thought they only came up when people tried to run them.  Perhaps something else is causing build failures?

Offline

#3 2019-03-06 03:24:10

aliemjay
Member
Registered: 2018-11-17
Posts: 15

Re: [SOLVED] x265 build failure holds back Plasma updates

I can confirm that this commit is the sole cause of build failure as I have just reverted it and built successfully.

Offline

#4 2019-03-06 05:11:10

levi
Moderator
From: UK
Registered: 2018-06-16
Posts: 243

Re: [SOLVED] x265 build failure holds back Plasma updates

Seems I was misinformed.  Thanks for testing.

Offline

#5 2019-03-07 07:38:40

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

Re: [SOLVED] x265 build failure holds back Plasma updates

I reverted part of the patch. Lets see if x265 builds now smile

Offline

#6 2019-03-07 15:52:48

aliemjay
Member
Registered: 2018-11-17
Posts: 15

Re: [SOLVED] x265 build failure holds back Plasma updates

very nice :-)

x265 built successfully but there is another issue though,

kfilemetadata now fails to build and the recent log shows that it installs "ki18n-5.54" in the build environment while the latest and the ONLY version available is "ki18n-5.55" and was built 3 weeks ago ( https://www.archlinux32.org/packages/i686/extra/ki18n/ )!
Please note that this version mismatch is the cause of build failure because v5.15 kde apps expect v5.55 plasma framework.

So, Why and how do build servers get outdated packages? Why are exact version dependencies not specified UPSTREAM so we can avoid these bugs and necessary manual intervention?

Last edited by aliemjay (2019-03-07 16:01:46)

Offline

#7 2019-03-07 17:25:20

levi
Moderator
From: UK
Registered: 2018-06-16
Posts: 243

Re: [SOLVED] x265 build failure holds back Plasma updates

kfilemetadata doesn't explicitly express a package dependency at all on ki18n, so that include must be coming from some different build configuration I guess.

Exact version dependencies don't tend to be written in unless they're absolutely known to be absolutely required because in any case they tend to fail to get updated at the right time, and cause this kind of issue, although as I say above in this case it's not actually written in the package dependencies.  We currently have a number of bad version dependencies on optional dependencies between firefox-developer-edition internationalised editions and the core package (core package too old) and nvidia-390xx-utils optionally required by various nvidia-390xx-* packages but it's too new.  But these are optional dependencies so the version dependency can only be viewed as advice at best.

Offline

#8 2019-03-08 08:00:21

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

Re: [SOLVED] x265 build failure holds back Plasma updates

oh, damn, the mirror which buildknecht and buildknecht2 use is outdated ...

Offline

#9 2019-03-08 11:19:15

aliemjay
Member
Registered: 2018-11-17
Posts: 15

Re: [SOLVED] x265 build failure holds back Plasma updates

Thanks a lot for your time :-)

Just a quick question,
Can the build system handle dependencies with exact version regarding scheduling and build order?
Because I have an idea and want to know how easy it is to implement.

Offline

#10 2019-03-08 11:29:52

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

Re: [SOLVED] x265 build failure holds back Plasma updates

it can and should.
The problem here was, that the build slave installed outdated packages, because it used an outdated mirror. This is something which the buildmaster cannot possibly detect/prevent.

Offline

#11 2019-03-08 12:31:41

aliemjay
Member
Registered: 2018-11-17
Posts: 15

Re: [SOLVED] x265 build failure holds back Plasma updates

This can be prevented if exact version dependencies were provided in the first place!

I'll suggest a possible solution for that in a new post.

Offline

#12 2019-03-08 17:29:36

levi
Moderator
From: UK
Registered: 2018-06-16
Posts: 243

Re: [SOLVED] x265 build failure holds back Plasma updates

Well, it would fall over with a slightly more clear error message, but still wouldn't point to the root cause, if you're doing what I think you're doing.

Offline

#13 2019-03-10 15:51:58

aliemjay
Member
Registered: 2018-11-17
Posts: 15

Re: [SOLVED] x265 build failure holds back Plasma updates

Fixing "dependencies" error is straightforward. Additionally, it would also prevent hard-to-debug mixing of incompatible versions that would otherwise pass the build silently (e.g https://bbs.archlinux32.org/viewtopic.php?id=2628) . as well as saving build slave time smile

sry for the delay.

Offline

#14 2019-03-10 20:11:52

levi
Moderator
From: UK
Registered: 2018-06-16
Posts: 243

Re: [SOLVED] x265 build failure holds back Plasma updates

Straightforward, but something the needs updaating every time there's a new version of the dependent package no?

Offline

#15 2019-03-10 22:08:37

aliemjay
Member
Registered: 2018-11-17
Posts: 15

Re: [SOLVED] x265 build failure holds back Plasma updates

I don't have strong opinion about that but...

my idea is to set versions only for dependencies that belong to qt5, kde-framework, plasma, kde-apps groups. These groups have the property that the version number is the same for all member packages, they are updated together from upstream and have strict version requirements ( especially for plasma )... That enables us to update version numbers only for those groups and it should apply for all member packages ( by mangle-pkgbuild at common-functions, for example )

Offline

Board footer

Powered by FluxBB