You are not logged in.

#1 Re: Creating/Maintaining Packages » [SOLVED] i686/community/netbeans/. New 11.0 version is out. » Yesterday 16:04:05

levi wrote:

There should be a way to find it it's already tried to build it already and failed and for what reasons, but I've forgotten how to get to that, unfortunately.

There is the build list with all the fancy filtering options available.
You can find it via -> Build Master (right hand side, under "Development") -> Build List (there are also some other useful shortcut links to filtered build lists on that page.)


#3 Re: Creating/Maintaining Packages » recurrent problem with plasma dependency loop » 2019-03-20 08:28:35

most probably, plasma-workspace misses some other dependencies, also (but I will check). forcing it to build will overwrite that check (and also break the cycle). What *sould* happen is:
Either plasma-workspace or kde-cli-tools is built first. If it fails, the other will be tried, too.

#4 Re: Creating/Maintaining Packages » "double-conversion 3.1.2" breaks ABI backward compatibility » 2019-03-08 14:29:19

ldd also reports indirectly linked libraries e.g. "$binary1 -> $library1 -> $library2" (there, only $library1 would need to be rebuilt).
have a look at lddtree or 'objdump -x' to see more

#5 Re: Creating/Maintaining Packages » "double-conversion 3.1.2" breaks ABI backward compatibility » 2019-03-08 12:53:34

according to the buildmaster's database only vtk and qt5-base are linked against - so I will only reschedule those and see what happens smile

#6 Re: Creating/Maintaining Packages » "double-conversion 3.1.2" breaks ABI backward compatibility » 2019-03-08 12:40:48

I'm in favour of rescheduling.
Which packages need to be recompiled? (How do we find out?)

#7 Re: Building » archlinux dual iso » 2019-03-08 11:32:22

You need to build it on an x86_64 machine (e.g. not from within archlinux32).
There exist archiso32 and archiso-dual in [releng] - one for each type of iso.
(This could be optimized, though ...)


#8 Re: Building » [SOLVED] x265 build failure holds back Plasma updates » 2019-03-08 11:29:52

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.

#9 Re: Building » [SOLVED] x265 build failure holds back Plasma updates » 2019-03-08 08:00:21

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

#10 Re: Installation » What constitutes an i686? AMD K6-2+ is not one? » 2019-03-08 07:20:36

I linked it in the intro "Have a look at the required cpu flags to decide which architecture is the right one for you."
But you're, right, a link in the sidebar would be nice, too - maybe under "Documentation"?

#11 Re: Installation » What constitutes an i686? AMD K6-2+ is not one? » 2019-03-07 09:12:51

there is now an overview page detailing the difference between the architectures - but as you can see, sse2 should not be in i686, but still is at several points sad

#12 Re: Installation » What constitutes an i686? AMD K6-2+ is not one? » 2019-03-07 07:46:44

nontheless, we should document (preferably on the front page) what processors will work with the i686 branch and which require the i486 branch.
abaumann: Am I right, that the difference is cmov, sse, sse2 which are required on i686 but may be lacking on i486?

#13 Re: Pacman / Pacman Upgrades » [SOLVED] cannot resolve jdk10-openjdk dependencies » 2019-03-07 07:41:48

jre10-openjdk and jre10-openjdk-headles versions *-1.2 are now in [extra] - I hope, I didn't break anything by moving them big_smile

#14 Re: Building » [SOLVED] x265 build failure holds back Plasma updates » 2019-03-07 07:38:40

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

#15 Re: Mirrors » Mirror Pool » 2019-03-07 07:28:49

that's a design problem of
this fqdn resolves to all (active) mirrors of ours, but there is (currently) no mechanism in place to distribute a valid certificate, so most mirrors simply show their default cert ...
we're open to suggestions smile

#16 Re: Pacman / Pacman Upgrades » [SOLVED] libsasl (2.1.27-1.0) breaks dependency 'libsasl=2.1.26' » 2019-02-14 05:30:53

ah, yes, I see - the move cyrus-sasl is also too old ... the right one is still stuck on the build list, I'll have a look why that is the case.


#18 Re: Kernel & Hardware » How to install linux-ck without compiling? » 2019-02-13 05:42:35

I see two possibilities there:
Either compile the packages you need yourself from aur (preferably with devtools32 from [releng] on or ask the maintainers of linux-ck if they are willing to provide i686 packages, too.


#19 Re: Pacman / Pacman Upgrades » [SOLVED] libsasl (2.1.27-1.0) breaks dependency 'libsasl=2.1.26' » 2019-02-13 05:37:30

hmm, I'll need to check a few lines in the buildmaster - it appears, that the version information was ignored.
I moved cyrus-sasl* to stable

#21 Re: Creating/Maintaining Packages » extra/firefox » 2019-02-10 09:10:31

I'll give it a try - but that machine does not have too much ram (it must be an i686 vm to allow for skipping systemd-nspawn) - andreas: do you have a slave running on i686 with 3-4GB RAM? Then you could try to build with "-s :without_systemd_nspawn:"

#22 Re: Mirrors » Online Mirrorlist » 2019-02-10 08:58:08

I fixed reflector - abaumann, I'll look into why you don't have push rights ... you should now have the necessary rights.

btw: we moved to, but$subdir/ should now be$subdir/ for certain subdirs (e.g. mirrors, buildmaster)

sry for the trouble - I didn't have these urls in mind when migrating.

#23 Re: Creating/Maintaining Packages » extra/firefox » 2019-02-08 05:38:12

jonathon wrote:

Could your build host be running out of RAM?

That's possible for some, but not all build slaves.
E.g. nlopc46 and nlopc43 have 64 and 32GB memory respectively.
I can schedule firefox on one of those to make sure it was tried to build there.

Any other options I need to set on the host?

#24 Re: Creating/Maintaining Packages » extra/firefox » 2019-02-07 05:20:10

there are builds scheduled and failing
I didn't have a look into them yet, sry


#25 Re: Mirrors » Online Mirrorlist » 2019-02-04 21:02:16

That was me. Your mirror appeared inactive and I sent you an email on 2018-10-03 but got no response, so I just assumed you moved along. Thus I removed the mirror from the mirrorlist.

I reverted that commit now.


Board footer

Powered by FluxBB