Re: builders->ftp uploads defunct
On 22/04/2024 20:58, Jakub Bogusz wrote: Since Saturday new packages don't appear in th-test. Could it be fixed? ENOSPC on ftp disk and stale locks... fixed. -- Arkadiusz Miśkiewicz, arekm / ( maven.pl | pld-linux.org ) ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: [packages/python3] python points to python3 now
On 25/03/2024 10:22, Jan Palus wrote:
On 25.03.2024 11:05, arekm wrote:
commit d073fb40c26996aedc0c52fdea5af8b596e4f395
Author: Arkadiusz Miśkiewicz
Date: Mon Mar 25 09:58:15 2024 +0100
python points to python3 now
python3.spec | 4
1 file changed, 4 insertions(+)
---
diff --git a/python3.spec b/python3.spec
index 503d98b..686f876 100644
--- a/python3.spec
+++ b/python3.spec
@@ -669,6 +669,9 @@ install -p Tools/patchcheck/reindent.py
$RPM_BUILD_ROOT%{_bindir}/pyreindent%{py
%{__mv} $RPM_BUILD_ROOT%{py_incdir}/pyconfig.h
$RPM_BUILD_ROOT%{py_libdir}/config-%{py_platform}/pyconfig.h
%{__sed}
-e's#@PREFIX@#%{_prefix}#g;s#@PY_VER@#%{py_ver}#g;s#@PY_ABI@#%{py_platform}#g'
%{SOURCE1} > $RPM_BUILD_ROOT%{py_incdir}/pyconfig.h
+# python points to python3 now
+ln -s python3 $RPM_BUILD_ROOT%{_bindir}/python
+
I guess all those packages that still meet `ipoldek what-requires
/usr/bin/python`
might not be happy about it.
I'm not sending these changes to builders to see what other devs will say.
(the intention was to break these packages and get them dropped (or
fixed) on case by case basis, if problems occur)
--
Arkadiusz Miśkiewicz, arekm / ( maven.pl | pld-linux.org )
___
pld-devel-en mailing list
pld-devel-en@lists.pld-linux.org
http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: TEST build ERRORS: test.spec
On 05/02/2024 02:02, Jan Palus wrote: I've tried to replicate the env (i686 VM, XFS) but without success. Not sure if it's block device driver? XFS? or something else? Can't do much more without ability to reproduce. Any ideas are welcome. All builders run on the same physical machine as VMs under proxmox 8.1: pve-manager/8.1.4/ec5affc9e41f1d79 (running kernel: 6.5.11-8-pve) Each builder uses two physical SSD disks (crucial: x32 - mx200, i686 - mx300, x86_64 - mx500). SSD are available to VMs as passthru. VMs have soft RAID1 setup inside, xfs fs on top of that. It's basically old hardware setup migrated from 3 different physical machines into one with proxmox. Providing disk directly to VM seems to be a key to reproduce the problem (as I was unable to reproduce it on the same machine when VM visible disk was backed by just qcow2 file). Disks used default options (so no cache, no discard, no io thread, no skip replication, async io - io_uring). Virtio interface. But I noticed that enabling discard on these hard disks (in proxmox->VM->Hardware->Hard disk) makes problem go away. So enabled on all builders. -- Arkadiusz Miśkiewicz, arekm / ( maven.pl | pld-linux.org ) ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: New packages not available on ftp
On 02/02/2024 00:14, Jan Palus wrote: None of packages built today on builders is available on ftp. Can someone check? Something bad happened on ep09 machine (which is main ftp machine; doesn't let ssh in; disconnects). No idea who else beside RMF has access to console on this VM. -- Arkadiusz Miśkiewicz, arekm / ( maven.pl | pld-linux.org ) ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
PLD New Rescue Th-20231129
https://github.com/pld-linux-org/pld-new-rescue/releases/tag/th-current-20231129 Based on Th main 20231129 tree. kernel 6.5.5 glibc 2.38 rpm 4.17.1.1 openssl 3.1.4 -- Arkadiusz Miśkiewicz, arekm / ( maven.pl | pld-linux.org ) ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: Wrong time (Re: DISTFILES: freetype: freetype-2.13.1.tar.xz freetype-doc-2.13.1.tar.xz ft2demos-2.13.1.tar.xz)
On 26.06.2023 10:31, atler wrote: On 26.06.2023 11:24, atler wrote: Request by: atler Files fetched: 1 ALREADY GOT: https://download.savannah.gnu.org/releases/freetype/freetype-2.13.1.tar.xz e4c3f0d8453a2a7993ae784912d6f19a freetype-2.13.1.tar.xz STORED: https://download.savannah.gnu.org/releases/freetype/freetype-doc-2.13.1.tar.xz 9eaaf193b0493297d92cd435cd850598 freetype-doc-2.13.1.tar.xz Size: 2173864 bytes ALREADY GOT: https://download.savannah.gnu.org/releases/freetype/ft2demos-2.13.1.tar.xz d76ec9572d018591a502bfdce312010f ft2demos-2.13.1.tar.xz Not that it bothers me much but looks like it was "11:24 CEST" somewhere while it should have been "10:17 CEST": Fixed date (on cvs...) -- Arkadiusz Miśkiewicz, arekm / ( maven.pl | pld-linux.org ) ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: GitHub key needs an update
On 24.03.2023 12:42, Jan Palus wrote: That's expected and GitHub host key needs an update, see: https://github.blog/2023-03-23-we-updated-our-rsa-ssh-host-key/ Updated. -- Arkadiusz Miśkiewicz, arekm / ( maven.pl | pld-linux.org ) ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
lists test
123... -- Arkadiusz Miśkiewicz, arekm / ( maven.pl | pld-linux.org ) ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: rust on carme-x32
On 20.01.2023 22:04, Jakub Bogusz wrote: On Thu, Jan 19, 2023 at 09:14:51AM +0100, Arkadiusz Miśkiewicz via pld-devel-en wrote: On 18.01.2023 16:08, Jakub Bogusz wrote: Could rust be installed on carme-x32? I'd like to (try to) fix mozjs102 build (required for new gjs), but I cannot install rust myself because of x86_64 packages requirements. Should be available now. I need cargo as well (requires 64-bit curl, libgit2 and openssl libs). Installed. -- Arkadiusz Miśkiewicz, arekm / ( maven.pl | pld-linux.org ) ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: rust on carme-x32
On 18.01.2023 16:08, Jakub Bogusz wrote: Could rust be installed on carme-x32? I'd like to (try to) fix mozjs102 build (required for new gjs), but I cannot install rust myself because of x86_64 packages requirements. Should be available now. -- Arkadiusz Miśkiewicz, arekm / ( maven.pl | pld-linux.org ) ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: x32 builder has network access
On 18.01.2023 09:56, Jan Palus wrote: On 18.01.2023 07:54, Arkadiusz Miśkiewicz via pld-devel-en wrote: On 17.01.2023 12:23, Jan Palus wrote: Noticed during build of kodi-addon-inputstream-adaptive that contrary to x86_64 and i686, x32 builder downloaded external sources successfully: bind was installed there and seems that even if there is no access to /etc/resolv.conf glibc fallbacks to querying 127.0.0.1:53 Uninstalled. The best would be to change UID of "builder" user used inside of chroot and drop all outgoing packets coming from it at iptables level. Or perhaps modify pld-builder to make each rpmbuild invocation in a new network namespace via `unshare -n -c`. That would effectively cut whole network for the process. We can try that... commited. -- Arkadiusz Miśkiewicz, arekm / ( maven.pl | pld-linux.org ) ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: x32 builder has network access
On 17.01.2023 12:23, Jan Palus wrote: Noticed during build of kodi-addon-inputstream-adaptive that contrary to x86_64 and i686, x32 builder downloaded external sources successfully: bind was installed there and seems that even if there is no access to /etc/resolv.conf glibc fallbacks to querying 127.0.0.1:53 Uninstalled. The best would be to change UID of "builder" user used inside of chroot and drop all outgoing packets coming from it at iptables level. -- Arkadiusz Miśkiewicz, arekm / ( maven.pl | pld-linux.org ) ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
udev-core R >= 4.15
udev-core change: -Requires: uname(release) >= 3.13 +Requires: uname(release) >= 4.15 Is this true requirement? I mean docs say: " README: say kernel 4.15 is the minimum recommended After various long discussions (https://lists.freedesktop.org/archives/systemd-devel/2022-March/047587.html, https://lwn.net/Articles/889610/), there is no clear answer what the minimum version should be. Bumping the version above 3.15 doesn't allow us to make any significant simplifications (unless we went *much* higher). In particular, even renameat2() is not fully supported with latest kernel versions, e.g. nfs still doesn't have it. And the bpf stuff is optional anyway. So let's just say that 4.15 is what we recommend, because it provides fairly complete cgroups-v2, but without any removals of compat in the code." and "+Kernel versions below 4.15 have significant gaps in functionality and +are not recommended for use with this version of systemd. Taint flag +'old-kernel' will be set. Systemd will most likely still function, but +upstream support and testing are limited." so looks like it should work on older kernels but there could be problems. Is there really some problem with udev-core that needs forcing >= 4.15? (I'm still using vserver 4.9 kernels) -- Arkadiusz Miśkiewicz, arekm / ( maven.pl | pld-linux.org ) ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: DISTFILES: qt6: ERRORS: qt-everywhere-src-6.3.2.tar.xz
On 30.10.2022 18:08, Jan Palus wrote: On 24.10.2022 09:17, Jan Palus wrote: On 24.10.2022 09:13, atler wrote: Request by: atler wget -nv --no-iri --user-agent=PLD/distfiles -O ./tmp/c988e5de-3fbe-4f8d-9c0e-892a6cc71ea2/bc928a9897698ec397b11c3dbff40e53/qt-everywhere-src-6.3.2.tar.xz https://download.qt.io/official_releases/qt/6.3/6.3.2/single/qt-everywhere-src-6.3.2.tar.xz: Cannot write to ???./tmp/c988e5de-3fbe-4f8d-9c0e-892a6cc71ea2/bc928a9897698ec397b11c3dbff40e53/qt-everywhere-src-6.3.2.tar.xz??? (Success). Can someone have a look what's that about? Noticed it before for larger sources like firefox but usually retry succeeded. qt6 on the other hand fails consistently. Also fails with `dropin` script after transferring ~264M: firefox-106.0.2.source.tar.xz54% 264MB 5.1MB/s 00:42 ETA scp: write remote "./firefox-106.0.2.source.tar.xz": Failure scp: failed to upload file firefox-106.0.2.source.tar.xz to . dropin is on cvs and there was no free space there. Added some. -- Arkadiusz Miśkiewicz, arekm / ( maven.pl | pld-linux.org ) ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: [packages/rpm-build-tools] builder: don't bother going back to original $(pwd) at the end of script
On 31.08.2022 11:27, Jan Rękorajski wrote: Where will it land now? If you want to protect against landing in non-existing directory you can use '[ -d "$__PWD" ] && cd "$__PWD"' I really prefer to be staying in the same directory where I launched the script in. Do you include (via source/dot) this script in some other script? -- Arkadiusz Miśkiewicz, arekm / ( maven.pl | pld-linux.org ) ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: RFC: shell completions policy change?
On 14.07.2022 16:38, Jakub Bogusz wrote:
As more and more packages are getting bash/zsh completions, separate
completions packages are becoming useless (harder to find, even not suggested).
My proposal:
1) add %{bash_compdir}, %{zsh_compdir} and maybe %{fish_compdir} (and upper
level) dirs to filesystem package and package bash/zsh[/fish] completion
files just with commands (existing bash-/zsh-[/fish-] packages to be merged and
obsoleted). [preferred]
Fortunately completion files don't have shebangs, which would generate
bash/zsh dependencies.
+1
2) at least add Suggests for completions packages in packages with
commands to complete
-1
--
Arkadiusz Miśkiewicz, arekm / ( maven.pl | pld-linux.org )
___
pld-devel-en mailing list
pld-devel-en@lists.pld-linux.org
http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: [packages/php-dirs] Rel 2; base on /etc/php directories since these always exist (while binaries are optional)
On 29.06.2022 18:38, Elan Ruusamäe wrote: > On 24.06.2022 11:42, arekm wrote: > >> commit 8b8822b9a17c06cd1d3f0b803e6a9830c962353e >> Author: Arkadiusz Miśkiewicz >> Date: Fri Jun 24 10:42:47 2022 +0200 >> >> Rel 2; base on /etc/php directories since these always exist >> (while binaries are optional) > yet /etc/phpXY may be just some *.rpmsave or *~ files from removed > installation Which shouldn't be a problem for that script as it checks other things, too. -- Arkadiusz Miśkiewicz, arekm / ( maven.pl | pld-linux.org ) ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: packages missing on carme (x86_64)
On 24.05.2022 13:00, Jan Palus wrote: > $ rpm -q git-core sudo > package git-core is not installed > package sudo is not installed installed again -- Arkadiusz Miśkiewicz, arekm / ( maven.pl | pld-linux.org ) ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
gitlab on cvs machine
Hi. Is gitlab on cvs machine used by anyone for anything? It only eats resources otherwise. -- Arkadiusz Miśkiewicz, arekm / ( maven.pl | pld-linux.org ) ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
lwn.net 3 years subscription and missing Szymon Siwek
Hello. Does anyone have contact with Szymon Siwek ? Our lwn.net subscription is going to expire and we want to renew it. He was participating but it seems that he doesn't use it since 2019. In case we won't be able to contact him we are looking for one person who is interested in 3 years lwn.net subcription for ~148PLN (1$/month). Deadline is tomorrow. -- Arkadiusz Miśkiewicz, arekm / ( maven.pl | pld-linux.org ) ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: PLD mail/requests problems
On 18.01.2022 20:16, Jakub Bogusz wrote: > On Tue, Jan 18, 2022 at 07:25:16PM +0100, Jan Rękorajski wrote: >> On Tue, 18 Jan 2022, Arkadiusz Miśkiewicz via pld-devel-en wrote: >> >>> On 17.01.2022 18:37, Jakub Bogusz wrote: >>>> On Sun, Jan 16, 2022 at 09:41:05PM +0100, Jakub Bogusz wrote: >>>>> - distfiles fetch request don't seem to be handled (since a few days) or >>>>> no >>>>> mail report is sent (both for requester nor pld-commit list) >>>> >>>> It seems distfiles are not fetching anything new at all (both by git or >>>> manual mail requests), and reports are not sent. >>>> >>>>> - I don't get any build logs since yesterday >>>>> >>>>> - only some (http) build requests are handled (one per ? hours) >>>> >>>> This one seems partially solved: ignored requests fail because of >>>> missing files on distfiles - but again, I don't get any mail reports >>>> about failed build from src builder. >>> >>> disk was fully filled on MX due to some spammers. >> >> There is still something wrong. I'm not getting any response from >> failed(?) requests. >> >> Ex. trying to build the kernel from head does not yield any response, not >> even build failure. Like the build request went to /dev/null. > > 404 Not Found > (/distfiles/by-md5/d/5/d571392436365678b420e4dece216514/patch-5.16.1.xz) > > (I've just sent fetchsrc request for kernel.spec to fix it) > > But why src builder doesn't send failure notifications? > > To nie to? Jan 18 20:11:30 b postfix/cleanup[22147]: CD0C749BA03: message-id=<16169.1642533...@distfiles.pld-linux.org> Jan 18 20:11:30 b postfix/local[22186]: B1EFA49BA01: to=, relay=local, delay=3.3, delays=3.3/0/0/0.03, dsn=2.0.0, status=sent (forwarded as CD0C749BA03) Jan 18 20:11:30 b postfix/qmgr[20373]: CD0C749BA03: from=, size=1215, nrcpt=1 (queue active) Jan 18 20:11:31 b postfix/smtp[30218]: CD0C749BA03: to=, orig_to=, relay=mail.qboosh.pl[217.73.31.61]:25, delay=0.59, delays=0.03/0.06/0.36/0.14, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as D20EB1A26DA9) Jan 18 20:11:31 b postfix/qmgr[20373]: CD0C749BA03: removed (data też była rozjechana o kilka minut wstecz na mxie) -- Arkadiusz Miśkiewicz, arekm / ( maven.pl | pld-linux.org ) ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: [packages/perl-IO-Socket-SSL] Rel 2; use system default ssl version and cipher list (from fc).
On 05.01.2022 19:22, Jan Palus wrote: >> ++# Use system-wide default cipher list to support use of system-wide >> ++# crypto policy (#1076390, #1127577, CPAN RT#97816) >> ++# https://fedoraproject.org/wiki/Changes/CryptoPolicy >> ++SSL_cipher_list => 'PROFILE=SYSTEM', > > Where is this PROFILE SYSTEM defined in PLD? With this patch ddclient > started to fail on every https call: > > Failed to set SSL cipher list error:0AB9:SSL routines::no cipher match It's some fedora thing. I guess we should just use system default (not sure how to tell that there). -- Arkadiusz Miśkiewicz, arekm / ( maven.pl | pld-linux.org ) ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
php pear deps not generating
Hi. Is anything new needed with rpm 4.16 to get php pear deps filled? I'm testing build on php-pear-Archive_Tar.spec and php.req/prov are not used and thus no pear() deps gets generated. -- Arkadiusz Miśkiewicz, arekm / ( maven.pl | pld-linux.org ) ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: [packages/iputils] - epoch 3 (s20190709 > 20210722), BR: pkgconfig
W dniu 07.12.2021 o 21:05, qboosh pisze: > commit 3a2973d1fda11d4c2c73488d06ab1c940768ce15 > Author: Jakub Bogusz > Date: Tue Dec 7 21:05:33 2021 +0100 > > - epoch 3 (s20190709 > 20210722), BR: pkgconfig Hmm. My initial plan was to keep sXYZ scheme but: [arekm@ixion ~]$ rpmvercmp s20190709 20210722 s20190709 < 20210722 [arekm@ixion ~]$ rpmvercmp 20210722 s20190709 20210722 > s20190709 [arekm@ixion ~]$ rpm --version RPM version 4.16.1.3 You say otherwise, why? -- Arkadiusz Miśkiewicz, arekm / ( maven.pl | pld-linux.org ) ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: TEST build OK: openjdk8.spec
W dniu 25.11.2021 o 10:27, Jan Palus pisze: > On 25.11.2021 06:10, PLD th-x86_64 builder wrote: >> openjdk8.spec (test): OK >> >> --- openjdk8.spec:test: >> not upgrading >> Build-Time: user:3197.59s sys:651.63s real:1129.22s (faults io:14177 >> non-io:93385165) > > Supposedly build took about ~20m, while email with confirmation came > after ~9h. Is there any issue with openjdk8 remaining or is it builder > related? builder related, cron was stopped. -- Arkadiusz Miśkiewicz, arekm / ( maven.pl | pld-linux.org ) ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: TEST build OK: openjdk8.spec - openjdk 8 and 9 hangs on glibc 2.34 in vserver guest
W dniu 24.11.2021 o 21:30, Jan Palus pisze: > I suppose this is the commit to be blamed for this regression: > > https://sourceware.org/git/?p=glibc.git;a=commitdiff;h=f13fb81ad3159543741e9132685335002a6d5df2 > > glibc 2.33 used to look at /proc too, but it no longer does in 2.34. Yes, f13fb81ad3159543741e9132685335002a6d5df2 is the first bad commit commit f13fb81ad3159543741e9132685335002a6d5df2 Author: Adhemerval Zanella Date: Thu Mar 25 14:04:37 2021 -0300 linux: Remove /proc/cpuinfo fallback on alpha and sparc There is no much gain in fallback to cpuinfo if sysfs is no present, usually on restricted environment neither will be present. It also simplifies the code and make all architecture use the sched_getaffinity as the sysfs fallback. Checked on sparc64-linux-gnu. sysdeps/unix/sysv/linux/alpha/getsysstats.c | 38 - sysdeps/unix/sysv/linux/getsysstats.c | 22 + sysdeps/unix/sysv/linux/sparc/getsysstats.c | 38 - 3 files changed, 1 insertion(+), 97 deletions(-) delete mode 100644 sysdeps/unix/sysv/linux/alpha/getsysstats.c delete mode 100644 sysdeps/unix/sysv/linux/sparc/getsysstats.c glibc people will reintroduce fallback (but based on /proc/stat). In mean time sysfs got mounted on builders and I also saw your changes to make multiprocessor default in openjdk 8 -- Arkadiusz Miśkiewicz, arekm / ( maven.pl | pld-linux.org ) ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: TEST build OK: openjdk8.spec - openjdk 8 and 9 hangs on glibc 2.34 in vserver guest
W dniu 24.11.2021 o 14:00, Arkadiusz Miśkiewicz pisze: > W dniu 22.10.2021 o 11:37, Jan Palus pisze: >> On 22.10.2021 10:44, Jan Rękorajski wrote: >>> Ah, it wasn't icedtea but openjdk8 that was installed on i686 and x86_64. >>> I'm uninstalling it and blocking in poldek on builders so that we have >>> only openjdk11 installable there. >> >> Currently openjdk8 requires either JDK 1.7 or 1.8 for build, I guess we >> can patch it and try to build with openjdk11, no guarantees it would >> work though. Not sure what is the difference but I had no issues >> building openjdk8 1.8.0.312 with openjdk8 1.8.0.302 and glibc 2.34 on >> x86_64, aarch64 and armv7hnl. I'll try to reproduce in fresh VM. > > For me our openjdk8 from ftp hangs on just doing "java -version". Not > always. Sometimes I need to run that 5-10 times but I do get the hang > easily. kernel 4.9.194, glibc 2.34, x86_64, vserver guest > > while (true); do date; java -version; done > > openjdk version "1.8.0_302-ga" > OpenJDK Runtime Environment (build 1.8.0_302-ga-1) > OpenJDK 64-Bit Server VM (build 25.302-b1, mixed mode) > > Build Date : pon, 2 sie 2021, 16:46:33 More fun with that. working system, glibc 2.34, on any kernel mkdir /test/ rsync -avPH / /test/ --exclude /test/ --exclude /proc --exclude /sys mount /proc /test/proc -o bind chroot /test/; java -version - hangs at some retry mkdir -p /test/sys/devices/system/cpu chroot /test/; java -version - no hangs (so proc is mounted but /sys is not; just dir exists) -- Arkadiusz Miśkiewicz, arekm / ( maven.pl | pld-linux.org ) ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: TEST build OK: openjdk8.spec - openjdk 8 and 9 hangs on glibc 2.34 in vserver guest
W dniu 22.10.2021 o 11:37, Jan Palus pisze: > On 22.10.2021 10:44, Jan Rękorajski wrote: >> Ah, it wasn't icedtea but openjdk8 that was installed on i686 and x86_64. >> I'm uninstalling it and blocking in poldek on builders so that we have >> only openjdk11 installable there. > > Currently openjdk8 requires either JDK 1.7 or 1.8 for build, I guess we > can patch it and try to build with openjdk11, no guarantees it would > work though. Not sure what is the difference but I had no issues > building openjdk8 1.8.0.312 with openjdk8 1.8.0.302 and glibc 2.34 on > x86_64, aarch64 and armv7hnl. I'll try to reproduce in fresh VM. For me our openjdk8 from ftp hangs on just doing "java -version". Not always. Sometimes I need to run that 5-10 times but I do get the hang easily. kernel 4.9.194, glibc 2.34, x86_64, vserver guest while (true); do date; java -version; done openjdk version "1.8.0_302-ga" OpenJDK Runtime Environment (build 1.8.0_302-ga-1) OpenJDK 64-Bit Server VM (build 25.302-b1, mixed mode) Build Date : pon, 2 sie 2021, 16:46:33 Doing the same on kernel 5.15.2 (VM on proxmox) and -version works. 4.4.279 on vserver host, glibc 2.34 - works. 4.4.279 butin vserver guest, glibc 2.34 hangs. 4.4.279 but glibc 2.33 in vserver guest - works. openjdk9-9.0.4.12-1.x86_64 also hangs in vserver guest with glibc 2.34 openjdk10-10.0.2.13-1.x86_64 works openjdk11-11.0.13-1.x86_64 works So vserver guest + glibc 2.34 + openjdk 8 and 9 is hanging on futexes. Easy way of testing if you don't have glibc 2.34 installed: - install openjdk8 from ftp (--nofollow --nodeps can be useful to prevent in dragging latest nss and thus glibc 2.3 - only working "java" binary is needed) - copy 2.34 *.so libs to some path - patchelf --set-interpreter /path/to/glibc-2.34-test-libs/ld-linux-x86-64.so.2 /usr/lib64/jvm/openjdk8-1.8.0.302/bin/java - run: while (true); do date; LD_LIBRARY_PATH=/path/to/glibc-2.34-test-libs/ java -version; done ps. builders stopped using vservers on 7 november 2021 and use 5.x kernels -- Arkadiusz Miśkiewicz, arekm / ( maven.pl | pld-linux.org ) ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: carme: indexes broken
W dniu 17.11.2021 o 09:40, Elan Ruusamäe pisze: > ➔ sudo poldek --update --upa poldek --clean-whole done -- Arkadiusz Miśkiewicz, arekm / ( maven.pl | pld-linux.org ) ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: samba 4.15.2 symbol version mismatch
W dniu 11.11.2021 o 22:34, Adam Osuchowski pisze: > Samba 4.15.2-1 from th-test requires SAMBA_4.13.9 symbol rm /usr/lib64/libsmbldap.so.2 ldconfig not sure why rpm does leaves it in such way > > > root@pldtest1:~# rpm -q samba > samba-4.15.2-1.x86_64 > root@pldtest1:~# smbd > smbd: /usr/lib64/samba/libsamba-security-samba4.so: version `SAMBA_4.13.9' > not found (required by /usr/lib64/libsmbldap.so.2) > smbd: /usr/lib64/samba/libreplace-samba4.so: version `SAMBA_4.13.9' not found > (required by /usr/lib64/libsmbldap.so.2) > smbd: /usr/lib64/samba/libsmbd-shim-samba4.so: version `SAMBA_4.13.9' not > found (required by /usr/lib64/libsmbldap.so.2) > smbd: /usr/lib64/samba/libsamba-debug-samba4.so: version `SAMBA_4.13.9' not > found (required by /usr/lib64/libsmbldap.so.2) > root@pldtest1:~# winbindd > winbindd: /usr/lib64/samba/libsamba-security-samba4.so: version > `SAMBA_4.13.9' not found (required by /usr/lib64/libsmbldap.so.2) > winbindd: /usr/lib64/samba/libreplace-samba4.so: version `SAMBA_4.13.9' not > found (required by /usr/lib64/libsmbldap.so.2) > winbindd: /usr/lib64/samba/libsmbd-shim-samba4.so: version `SAMBA_4.13.9' not > found (required by /usr/lib64/libsmbldap.so.2) > winbindd: /usr/lib64/samba/libsamba-debug-samba4.so: version `SAMBA_4.13.9' > not found (required by /usr/lib64/libsmbldap.so.2) > root@pldtest1:~# objdump -p /usr/lib64/libsmbldap.so.2 | grep -A6 'Version > References' > Version References: > required from libsamba-security-samba4.so: > 0x07275469 0x00 13 SAMBA_4.13.9 > required from libreplace-samba4.so: > 0x07275469 0x00 12 SAMBA_4.13.9 > required from libsmbd-shim-samba4.so: > 0x07275469 0x00 11 SAMBA_4.13.9 > ___ > pld-devel-en mailing list > pld-devel-en@lists.pld-linux.org > http://lists.pld-linux.org/mailman/listinfo/pld-devel-en > -- Arkadiusz Miśkiewicz, arekm / ( maven.pl | pld-linux.org ) ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: TEST build ERRORS: onedrive.spec
W dniu 11.11.2021 o 12:07, Jan Rękorajski pisze: > This should do the trick (if I didn't mess up poldek options) > > make-request -t -c 'rm -f /spools/ready/* ; poldek --mkidxz -s > /spools/ready ; poldek --up' > > Basically builders have a local spool with most recently built > packages and this on rare occasions goes out of sync. Or just resend any small package from latest tag (I usually send alien.spec for that) because rebuilding package causes poldek indexes regeneration in /spools/ready. -- Arkadiusz Miśkiewicz, arekm / ( maven.pl | pld-linux.org ) ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
PLD New Rescue Th-20211017
PLD New Rescue Th-20211017 is there. Based on PLD Th main tree as of 20211017. https://github.com/pld-linux-org/pld-new-rescue/releases/tag/th-current-2021017 -- Arkadiusz Miśkiewicz, arekm / ( maven.pl | pld-linux.org ) ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: [packages/ca-certificates] Rel 6; make sure we don't include expired certs
W dniu 01.10.2021 o 20:27, Jakub Bogusz pisze: > On Fri, Oct 01, 2021 at 12:36:20PM +0200, arekm wrote: >> commit 0818a4328225cca2d41e43f0fa816f38bb3cbe69 >> Author: Arkadiusz Miśkiewicz >> Date: Fri Oct 1 12:36:07 2021 +0200 >> >> Rel 6; make sure we don't include expired certs > > Unfortunately ix86 `date` doesn't know y2038+... > > | date: invalid date 'Oct 25 08:25:55 2043 GMT' > > Jan, what was the reason behind --disable-year2038 in coreutils? Enabling that and date on ix86 parses such date correctly (with coreutils 9.0). -- Arkadiusz Miśkiewicz, arekm / ( maven.pl | pld-linux.org ) ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
https://osv.dev/ and pld ftp
New report: https://srcbuilder.pld-linux.org/~pldth/qa.php?q=main-vuln matching main ftp archive against https://osv.dev/ database, updated daily -- Arkadiusz Miśkiewicz, arekm / ( maven.pl | pld-linux.org ) ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: [packages/kernel] - drop unneeded excludes (rpm 4.16 handles these differently from rpm 5)
W dniu 16.12.2020 o 10:36, Arkadiusz Miśkiewicz pisze:
> W dniu 16.12.2020 o 10:14, Elan Ruusamäe pisze:
>> On 15.12.2020 18:05, arekm wrote:
>>
>>> %exclude %{_kernelsrcdir}/scripts/mod
>>> -%exclude %{_kernelsrcdir}/scripts/module-common.lds
>>
>> what do you mean?
>>
>> rpm 4.16 does prefix match and rpm5 does glob match?
>>
>> ie that
>>
>> %{_kernelsrcdir}/scripts/mod
>>
>> matches also
>>
>> %{_kernelsrcdir}/scripts/module-common.lds
>>
>> on 4.16?
>>
>>
>> does your change make .spec inclusive to 4.16-only now?
>
> %exclude non-existsing-file seems to pass on 4.16 while fail on 5.
>
>
> Similar thing - %doc with not existing file succeeds on 4.16.
>
Another one. Non existing %ghost also doesn't cause build failure and
results in unpackaged files (if soname gets new version while spec has
old one as ghost).
--
Arkadiusz Miśkiewicz, arekm / ( maven.pl | pld-linux.org )
___
pld-devel-en mailing list
pld-devel-en@lists.pld-linux.org
http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: rpm4 on carme*
W dniu 22.11.2020 o 17:00, Jan Palus pisze: > * adding to the list of invalid chars in Obsoletes: '/' (msmtp: Obsoletes: > /usr/lib/sendmail) > > * python-Cython built with rpm.org has weird unsatisfied R: > python2.7dist(setuptools) / python3.8dist(setuptools) Could these be https://rpm.org/user_doc/boolean_dependencies.html that are not handled by poldek ? And "/" could be forbidden due to that. -- Arkadiusz Miśkiewicz, arekm / ( maven.pl | pld-linux.org ) ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: missing mail logs form th-x86_64 [SOLVED: th-x86_64: strange runtime linker failure]
W dniu 13.11.2020 o 10:36, Jan Palus via pld-devel-en pisze: > On 13.11.2020 08:55, Arkadiusz Miśkiewicz wrote: >> W dniu 10.11.2020 o 20:03, Jakub Bogusz pisze: >> >>> >>> Problem solved by `mount -t proc proc /proc`. >>> There were some stale /proc contents, most likely rsynced from some live >>> system in 2009 (that's why /proc/self/exe points to rsync). >> >> Builders no longer run in vservers. kernel 5.9 on them. proc wasn't >> mounted properly after this migration (which is now fixed) > > Could you also check if /dev/shm is mounted? I suppose that's why > firefox is failing now: > > 0:40.96 sl = self._semlock = _multiprocessing.SemLock( > 0:40.96 OSError: [Errno 38] Function not implemented It's mounted since my previous mail (was also broken, like proc). -- Arkadiusz Miśkiewicz, arekm / ( maven.pl | pld-linux.org ) ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: carme-x32
W dniu 31.08.2020 o 21:43, Jakub Bogusz via pld-devel-en pisze: > seems dead? > > $ ssh-carme-x32 > Connection closed by 193.239.45.154 port 22 > > glibc 2.31 bug https://sourceware.org/bugzilla/show_bug.cgi?id=26248 Upgrade to 2.32 fixed the problem. -- Arkadiusz Miśkiewicz, arekm / ( maven.pl | pld-linux.org ) ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: [packages/shadow] - shadow puts everything into /bin and /sbin - that's ok but provide symlinks for old (pwdutils) loc
On 07/01/2020 17:06, Jakub Bogusz wrote:
> On Tue, Jan 07, 2020 at 01:36:44PM +0100, arekm wrote:
>> commit 2bb4da0ffecbbc08e6e25336b3e1e012b7cd61a5
>> Author: Arkadiusz Miśkiewicz
>> Date: Tue Jan 7 13:36:34 2020 +0100
>>
>> - shadow puts everything into /bin and /sbin - that's ok but provide
>> symlinks for old (pwdutils) locations
> [...]
>> +# compatibility with old locations (and pwdutils)
>> +install -d $RPM_BUILD_ROOT%{_bindir}
>> +for f in chage chfn chsh expiry faillog gpasswd newgrp newgidmap passwd
>> newuidmap sg; do
>> + ln -s /bin/${f} $RPM_BUILD_ROOT%{_bindir}/${f}
>> +done
>> +install -d $RPM_BUILD_ROOT%{_sbindir}
>> +for f in chgpasswd chpasswd groupadd groupdel groupmems groupmod grpck
>> grpconv grpunconv logoutd newusers pwck pwconv pwunconv useradd userdel
>> usermod vigr vipw; do
>> + ln -s /sbin/${f} $RPM_BUILD_ROOT%{_sbindir}/${f}
>> +done
>> +
> [...]
>> +%attr(4755,root,root) /bin/chfn
>> %attr(4755,root,root) %{_bindir}/chfn
>> +%attr(4755,root,root) /bin/chsh
>> %attr(4755,root,root) %{_bindir}/chsh
>> +%attr(4755,root,root) /bin/expiry
>> %attr(4755,root,root) %{_bindir}/expiry
>> +%attr(4755,root,root) /bin/gpasswd
>> %attr(4755,root,root) %{_bindir}/gpasswd
>> +%attr(4755,root,root) /bin/passwd
>> %attr(4755,root,root) %{_bindir}/passwd
>> +%attr(4755,root,root) /bin/chage
>> %attr(4755,root,root) %{_bindir}/chage
>> +%attr(755,root,root) /bin/faillog
>> %attr(755,root,root) %{_bindir}/faillog
>> +%attr(4755,root,root) /bin/newgrp
>> %attr(4755,root,root) %{_bindir}/newgrp
>> +%attr(755,root,root) /bin/sg
>> %attr(755,root,root) %{_bindir}/sg
>> +%attr(755,root,root) /sbin/chgpasswd
>> %attr(755,root,root) %{_sbindir}/chgpasswd
>> +%attr(755,root,root) /sbin/chpasswd
>> %attr(755,root,root) %{_sbindir}/chpasswd
>> +%attr(755,root,root) /sbin/groupadd
>> %attr(755,root,root) %{_sbindir}/groupadd
>> +%attr(755,root,root) /sbin/groupdel
>> %attr(755,root,root) %{_sbindir}/groupdel
>> +%attr(755,root,root) /sbin/groupmems
>> %attr(755,root,root) %{_sbindir}/groupmems
>> +%attr(755,root,root) /sbin/groupmod
>> %attr(755,root,root) %{_sbindir}/groupmod
> [...]
>
> Uhhh, please, no.
It's ugly but I don't see any other solution that would work.
> Either go traditional way and distribute binaries over directories (like
> in coreutils),
To goal is not to diverge from upstream.
or maybe it's time to go merged-/usr distro-wide?
>
> Are there still any profits from using local / with network or host shared
> /usr?
Does it matter for this case?
The only goal of symlinks it to have this package working in current PLD
which has hardcoded /usr paths to some of these binaries.
--
Arkadiusz Miśkiewicz, arekm / ( maven.pl | pld-linux.org )
___
pld-devel-en mailing list
pld-devel-en@lists.pld-linux.org
http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
