| === nesda is now known as ialmeida | ||
| bdrung | cryfs 0.11.3-5 fails to build on ppc64el due to not enough memory (bug #2019853). Can we give the builders more memory? | 10:59 |
|---|---|---|
| -ubottu:#launchpad- Bug 2019853 in cryfs (Ubuntu) "cryfs 0.11.3-5 fails to build on ppc64el" [Undecided, New] https://launchpad.net/bugs/2019853 | 10:59 | |
| cjwatson | bdrung: I doubt it's a question of physical memory (they get 16GB). From the log it looks more like mlock | 11:00 |
| cjwatson | IIRC upgrading the builders to jammy will help with that | 11:00 |
| cjwatson | (due to systemd changes) | 11:00 |
| bdrung | can you elaborate your reasoning what the problem with mlock is and why jammy could help? | 11:03 |
| cjwatson | The reason I suspect mlock is that the build log mentions it. And mlock failing is usually not helped by increasing available system memory - mlock has a much more restricted available pool. | 11:23 |
| cjwatson | The systemd thing is a vague memory though. | 11:26 |
| cjwatson | Possibly wrong. systemd 852b62507b22c0a986032a2c9fa9cc464a5b7bd2 looks relevant, but that's in 251 which was post-jammy. | 11:27 |
| cjwatson | But in any case, if a test is showing that insufficient lockable memory is available, that's probably something that should be fixed in the distro - not something we should hack around specifically on builders, since that would just make the test environment less realistic. | 11:28 |
| cjwatson | If it's just a matter of keeping up with current distro configuration, we can do that (hence my comment about jammy), but I don't think we should have something like a tweak for LimitMEMLOCK= just for builders. | 11:29 |
| === philroche_ is now known as philroche | ||
| surfzoid | Hi, | 18:57 |
| surfzoid | my soft, QtVsPlayer need QT>=5.15, my raspberry is under dedian bulleeyes, so ubuntu focal, to get qt5.15 i use https://launchpad.net/~savoury1/+archive/ubuntu/qt-5-15 in my ppa dependancies, it's perfect when build the machine: https://launchpadlibrarian.net/666494585/buildlog.txt.gz but why, when build the binaries, launchpad downgrade qt to 5.12 | 19:01 |
| surfzoid | :https://launchpadlibrarian.net/666495311/buildlog_ubuntu-focal-arm64.qtvsplayer_1.0.41~202305161847~ubuntu20.04.1_BUILDING.txt.gz | 19:01 |
| sarnold | surfzoid: my *guess* is that savoury1 has decided to not publish aarch64 binaries for whatever reason | 19:06 |
| sarnold | https://launchpad.net/~savoury1/+archive/ubuntu/qt-5-15/+sourcepub/12647572/+listing-archive-extra | 19:06 |
| sarnold | pyqt5 (5.15.4+dfsg-1~20.04.sav1) focal; urgency=medium | 19:06 |
| sarnold | * Build for amd64 only due several BDs not on Focal i386 Launchpad whitelist | 19:06 |
| sarnold | maybe ask him if he could add aarch64 packages? | 19:07 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!