From glen at pld-linux.org Fri Apr 3 20:09:09 2020 From: glen at pld-linux.org (=?UTF-8?Q?Elan_Ruusam=c3=a4e?=) Date: Fri, 3 Apr 2020 21:09:09 +0300 Subject: libc 2.31/i686: operation not permitted for preserving timestamps In-Reply-To: References: Message-ID: is this fix for this problem? - https://github.com/pld-linux/util-linux/commit/67a912cd50464cae095fbdb7b3cf90daf495fb90 - http://lists.pld-linux.org/mailman/pipermail/pld-devel-en/2020-March/025883.html On 16.03.2020 23:46, Elan Ruusam?e wrote: > i've got reports that cp -a (or just cp --preserve=timestamps) fails > on i686 and glibc 2.31 > > > from strace i've grabbed such error: > > > ?????? utimensat_time64(4, NULL, [{tv_sec=1584393052, tv_nsec=0} /* > 2020-03-16T23:10:52+0200 */, {tv_sec=1584393052, tv_nsec=0} /* > 2020-03-16T23:10:52+0200 */], 0) = -1 EPERM (Operation not permitted) > > > i believe it's related to large inode on fd=4 and glibc just reports > it incorrectly > > > ``` > + ls -ldi locale-archive > /var/tmp/glibc-localedb-2.30.0-root-root/usr/lib/locale > ??? 790264 drwxr-xr-x 2 root root???? 4096 Mar 16? 2020 > /var/tmp/glibc-localedb-2.30.0-root-root/usr/lib/locale > 4379091441 -rw-r--r-- 1 root root 13754080 Mar 16? 2020 locale-archive > + cp '--preserve=timestamps' locale-archive > /var/tmp/glibc-localedb-2.30.0-root-root/usr/lib/locale > cp: preserving times for > '/var/tmp/glibc-localedb-2.30.0-root-root/usr/lib/locale/locale-archive': > Operation not permitted > > ``` > From arekm at maven.pl Fri Apr 3 20:47:03 2020 From: arekm at maven.pl (=?UTF-8?Q?Arkadiusz_Mi=c5=9bkiewicz?=) Date: Fri, 3 Apr 2020 20:47:03 +0200 Subject: libc 2.31/i686: operation not permitted for preserving timestamps In-Reply-To: References:

Message-ID: <2ed90d66-b1a0-aaf3-cb5e-5fb69d6a6797@maven.pl> On 03/04/2020 20:09, Elan Ruusam?e wrote: > is this fix for this problem? > > - > https://github.com/pld-linux/util-linux/commit/67a912cd50464cae095fbdb7b3cf90daf495fb90 > > > - > http://lists.pld-linux.org/mailman/pipermail/pld-devel-en/2020-March/025883.html No. Do you use systemd-nspawn for starting something and running cp inside? Is that cp test on vm/bare metal + kernel + just userspace directly? -- Arkadiusz Mi?kiewicz, arekm / ( maven.pl | pld-linux.org ) From hawk at pld-linux.org Mon Apr 6 22:40:21 2020 From: hawk at pld-linux.org (Marcin Krol) Date: Mon, 6 Apr 2020 22:40:21 +0200 Subject: [packages/samba] - up to 4.12.0; ceph disabled (likely ceph.spec update needed) In-Reply-To: References:

Message-ID: <5E8B93B5.1000308@pld-linux.org> Feel free to merge updated ceph from TLD. Or use it as starting point for your own spec (with systemd support etc.) https://git.tld-linux.org/?p=packages/ceph.git;a=summary Note: ceph is now x64 only, x86 is officially not supported anymore. Also frontend is not being build (downloads "to be build" components from network). M. On 25-Mar-20 18:55, arekm wrote: > commit a3afb33496b0ed8868cc2a5c0fd81890786efb13 > Author: Arkadiusz Mi??kiewicz > Date: Wed Mar 25 18:55:17 2020 +0100 > > - up to 4.12.0; ceph disabled (likely ceph.spec update needed) From glen at pld-linux.org Sat Apr 18 08:32:22 2020 From: glen at pld-linux.org (=?UTF-8?Q?Elan_Ruusam=c3=a4e?=) Date: Sat, 18 Apr 2020 09:32:22 +0300 Subject: libc 2.31/i686: operation not permitted for preserving timestamps In-Reply-To: <2ed90d66-b1a0-aaf3-cb5e-5fb69d6a6797@maven.pl> References:

<2ed90d66-b1a0-aaf3-cb5e-5fb69d6a6797@maven.pl> Message-ID: <187022cc-beeb-3643-e508-760d815a7b5a@pld-linux.org> On 4/3/20 9:47 PM, Arkadiusz Mi?kiewicz wrote: > On 03/04/2020 20:09, Elan Ruusam?e wrote: >> is this fix for this problem? >> >> - >> https://github.com/pld-linux/util-linux/commit/67a912cd50464cae095fbdb7b3cf90daf495fb90 >> >> >> - >> http://lists.pld-linux.org/mailman/pipermail/pld-devel-en/2020-March/025883.html > No. > > Do you use systemd-nspawn for starting something and running cp inside? > > Is that cp test on vm/bare metal + kernel + just userspace directly? > it's inside docker, as noted in earlier post: - http://lists.pld-linux.org/mailman/pipermail/pld-devel-en/2020-March/025887.html - here's full build log attemting to? build base image: https://gitlab.com/pld-linux/pld/-/jobs/480110124 the reproducer is pretty straight forward, and i don't think it matters what is the host kernel. it fails in that cloud and fails in docker for mac (O) ``` $ docker run --rm -it registry.gitlab.com/pld-linux/pld/i686 at sha256:832f004cc28798aafd758a7e6aa867681f1f860ac22b341dc8a2183a75a53e36 bash [root at 6aff3df5fe9a /]# uname -a Linux 6aff3df5fe9a 4.19.76-linuxkit #1 SMP Thu Oct 17 19:31:58 UTC 2019 x86_64 Intel(R)_Core(TM)_i7-7700HQ_CPU_ at _2.80GHz PLD Linux [root at 6aff3df5fe9a /]# rpm -q glibcglibc-2.30-3.i686 [root at 6aff3df5fe9a /]# cp -a /var/lib/rpm/ /tmp/rpm1 [root at 6aff3df5fe9a /]# poldek --up -u glibc-2.31-5.i686 --noask th::packages.ndir.gz [16.6M (8.1M/s)] th::packages.ndir.dscr.gz [2.2M (2.2M/s)] th::packages.ndir.gz [16.3M (7.7M/s)] th::packages.ndir.dscr.gz [1.1M (1.1M/s)] Loading [pndir]th... Loading [pndir]th... 28925 packages read Processing dependencies... glibc-2.30-3.i686 obsoleted by glibc-2.31-5.i686 glibc-2.31-5.i686 marks glibc-ld-2.31-5.i686 (cap glibc-ld = 6:2.31-5) ?glibc-ld-2.30-3.i686 obsoleted by glibc-ld-2.31-5.i686 There are 2 packages to install (1 marked by dependencies), 2 to remove: U glibc-(2.30-3 => 2.31-5).i686? glibc-ld-(2.30-3 => 2.31-5).i686 This operation will use 138.5KB of disk space. Need to get 3.2MB of archives (3.2MB to download). [1/2] th::glibc-ld-2.31-5.i686.rpm [401.1K (401.1K/s)] [2/2] th::glibc-2.31-5.i686.rpm [2.8M (1.8M/s)] Executing pm-command.sh --upgrade -vh --root / --define _check_dirname_deps 1... Preparing... ########################################### [100%] ?? 1:glibc-ld ########################################### [ 50%] ?? 2:glibc ########################################### [100%] [root at 6aff3df5fe9a /]# cp -a /var/lib/rpm/ /tmp/rpm2 cp: preserving times for '/tmp/rpm2/__db.001': Operation not permitted cp: preserving times for '/tmp/rpm2/__db.002': Operation not permitted cp: preserving times for '/tmp/rpm2/__db.003': Operation not permitted cp: preserving times for '/tmp/rpm2/__db.004': Operation not permitted cp: preserving times for '/tmp/rpm2/__db.005': Operation not permitted cp: preserving times for '/tmp/rpm2/__db.006': Operation not permitted cp: preserving times for '/tmp/rpm2/Arch': Operation not permitted cp: preserving times for '/tmp/rpm2/Basenames': Operation not permitted cp: preserving times for '/tmp/rpm2/Conflictname': Operation not permitted cp: preserving times for '/tmp/rpm2/DB_CONFIG': Operation not permitted cp: preserving times for '/tmp/rpm2/Dirnames': Operation not permitted cp: preserving times for '/tmp/rpm2/Filedigests': Operation not permitted cp: preserving times for '/tmp/rpm2/Filepaths': Operation not permitted cp: preserving times for '/tmp/rpm2/Group': Operation not permitted cp: preserving times for '/tmp/rpm2/Installtid': Operation not permitted cp: preserving times for '/tmp/rpm2/Name': Operation not permitted cp: preserving times for '/tmp/rpm2/Nvra': Operation not permitted cp: preserving times for '/tmp/rpm2/Obsoletename': Operation not permitted cp: preserving times for '/tmp/rpm2/Os': Operation not permitted cp: preserving times for '/tmp/rpm2/Packagecolor': Operation not permitted cp: preserving times for '/tmp/rpm2/Packages': Operation not permitted cp: preserving times for '/tmp/rpm2/Providename': Operation not permitted cp: preserving times for '/tmp/rpm2/Pubkeys': Operation not permitted cp: preserving times for '/tmp/rpm2/Release': Operation not permitted cp: preserving times for '/tmp/rpm2/Requirename': Operation not permitted cp: preserving times for '/tmp/rpm2/Seqno': Operation not permitted cp: preserving times for '/tmp/rpm2/Sha1header': Operation not permitted cp: preserving times for '/tmp/rpm2/Sigmd5': Operation not permitted cp: preserving times for '/tmp/rpm2/Sourcepkgid': Operation not permitted cp: preserving times for '/tmp/rpm2/Triggername': Operation not permitted cp: preserving times for '/tmp/rpm2/Version': Operation not permitted cp: preserving times for '/tmp/rpm2/log/log.0000000001': Operation not permitted cp: preserving times for '/tmp/rpm2/log': Operation not permitted cp: preserving times for '/tmp/rpm2/tmp': Operation not permitted cp: preserving times for '/tmp/rpm2': Operation not permitted [root at 6aff3df5fe9a /]# ... ``` note: registry.gitlab.com/pld-linux/pld/i686 at sha256:832f004cc28798aafd758a7e6aa867681f1f860ac22b341dc8a2183a75a53e36 is current alias for registry.gitlab.com/pld-linux/pld/i686:latest From arekm at maven.pl Sat Apr 18 08:49:12 2020 From: arekm at maven.pl (=?UTF-8?Q?Arkadiusz_Mi=c5=9bkiewicz?=) Date: Sat, 18 Apr 2020 08:49:12 +0200 Subject: libc 2.31/i686: operation not permitted for preserving timestamps In-Reply-To: <187022cc-beeb-3643-e508-760d815a7b5a@pld-linux.org> References:

<2ed90d66-b1a0-aaf3-cb5e-5fb69d6a6797@maven.pl> <187022cc-beeb-3643-e508-760d815a7b5a@pld-linux.org> Message-ID: On 18/04/2020 08:32, Elan Ruusam?e wrote: > > On 4/3/20 9:47 PM, Arkadiusz Mi?kiewicz wrote: >> On 03/04/2020 20:09, Elan Ruusam?e wrote: >>> is this fix for this problem? >>> >>> - >>> https://github.com/pld-linux/util-linux/commit/67a912cd50464cae095fbdb7b3cf90daf495fb90 >>> >>> >>> >>> - >>> http://lists.pld-linux.org/mailman/pipermail/pld-devel-en/2020-March/025883.html >>> >> No. >> >> Do you use systemd-nspawn for starting something and running cp inside? >> >> Is that cp test on vm/bare metal + kernel + just userspace directly? >> > it's inside docker, as noted in earlier post: > > - > http://lists.pld-linux.org/mailman/pipermail/pld-devel-en/2020-March/025887.html > > > - here's full build log attemting to? build base image: > > > https://gitlab.com/pld-linux/pld/-/jobs/480110124 > > > the reproducer is pretty straight forward, and i don't think it matters > what is the host kernel. it fails in that cloud and fails in docker for > mac (O) > > > ``` > > $ docker run --rm -it > registry.gitlab.com/pld-linux/pld/i686 at sha256:832f004cc28798aafd758a7e6aa867681f1f860ac22b341dc8a2183a75a53e36 > bash What happens if you start docker also with --security-opt seccomp=unconfined ? And with libseccomp 2.4.3 but without above option? -- Arkadiusz Mi?kiewicz, arekm / ( maven.pl | pld-linux.org ) From baggins at pld-linux.org Sat Apr 18 10:02:20 2020 From: baggins at pld-linux.org (Jan =?utf-8?Q?R=C4=99korajski?=) Date: Sat, 18 Apr 2020 10:02:20 +0200 Subject: libc 2.31/i686: operation not permitted for preserving timestamps In-Reply-To: <187022cc-beeb-3643-e508-760d815a7b5a@pld-linux.org> References:

<2ed90d66-b1a0-aaf3-cb5e-5fb69d6a6797@maven.pl> <187022cc-beeb-3643-e508-760d815a7b5a@pld-linux.org> Message-ID: <20200418080220.GA2085@starbug> On Sat, 18 Apr 2020, Elan Ruusam?e wrote: > > On 4/3/20 9:47 PM, Arkadiusz Mi?kiewicz wrote: > > On 03/04/2020 20:09, Elan Ruusam?e wrote: > >> is this fix for this problem? > >> > >> - > >> https://github.com/pld-linux/util-linux/commit/67a912cd50464cae095fbdb7b3cf90daf495fb90 > >> > >> > >> - > >> http://lists.pld-linux.org/mailman/pipermail/pld-devel-en/2020-March/025883.html > > No. > > > > Do you use systemd-nspawn for starting something and running cp inside? > > > > Is that cp test on vm/bare metal + kernel + just userspace directly? > > > it's inside docker, as noted in earlier post: > > - > http://lists.pld-linux.org/mailman/pipermail/pld-devel-en/2020-March/025887.html > > - here's full build log attemting to? build base image: > > > https://gitlab.com/pld-linux/pld/-/jobs/480110124 > > > the reproducer is pretty straight forward, and i don't think it matters > what is the host kernel. it fails in that cloud and fails in docker for > mac (O) A copy-paste of the error message into Google gives me this: https://github.com/bitnami/bitnami-docker-laravel/issues/102 Try running the container with 'privileged: true' -- Jan R?korajski | PLD/Linux SysAdm | bagginspld-linux.org | http://www.pld-linux.org/ From glen at pld-linux.org Sat Apr 18 16:44:29 2020 From: glen at pld-linux.org (=?UTF-8?Q?Elan_Ruusam=c3=a4e?=) Date: Sat, 18 Apr 2020 17:44:29 +0300 Subject: libc 2.31/i686: operation not permitted for preserving timestamps In-Reply-To: <20200418080220.GA2085@starbug> References:

<2ed90d66-b1a0-aaf3-cb5e-5fb69d6a6797@maven.pl> <187022cc-beeb-3643-e508-760d815a7b5a@pld-linux.org> <20200418080220.GA2085@starbug> Message-ID: <3ceb4033-a061-5a2b-094c-774ceb7ab969@pld-linux.org> On 4/18/20 11:02 AM, Jan R?korajski wrote: > A copy-paste of the error message into Google gives me this: > > https://github.com/bitnami/bitnami-docker-laravel/issues/102 > > Try running the container with 'privileged: true' it fits as a workaround, but not as a solution. and is obviously rather big regression. ``` $ docker run --privileged --rm -it registry.gitlab.com/pld-linux/pld/i686 at sha256:832f004cc28798aafd758a7e6aa867681f1f860ac22b341dc8a2183a75a53e36 bash [root at fa15404db2db /]# poldek --up -u glibc-2.31-5.i686 --noask th::packages.ndir.gz [16.6M (3.7M/s)] th::packages.ndir.dscr.gz [2.2M (680.0K/s)] th::packages.ndir.gz [16.3M (8.0M/s)] th::packages.ndir.dscr.gz [1.1M (1.1M/s)] Loading [pndir]th... Loading [pndir]th... 28925 packages read Processing dependencies... glibc-2.30-3.i686 obsoleted by glibc-2.31-5.i686 glibc-2.31-5.i686 marks glibc-ld-2.31-5.i686 (cap glibc-ld = 6:2.31-5) ?glibc-ld-2.30-3.i686 obsoleted by glibc-ld-2.31-5.i686 There are 2 packages to install (1 marked by dependencies), 2 to remove: U glibc-(2.30-3 => 2.31-5).i686? glibc-ld-(2.30-3 => 2.31-5).i686 This operation will use 138.5KB of disk space. Need to get 3.2MB of archives (3.2MB to download). [1/2] th::glibc-ld-2.31-5.i686.rpm [401.1K (401.1K/s)] [2/2] th::glibc-2.31-5.i686.rpm [2.8M (2.8M/s)] Executing pm-command.sh --upgrade -vh --root / --define _check_dirname_deps 1... Preparing... ########################################### [100%] ?? 1:glibc-ld ########################################### [ 50%] ?? 2:glibc ########################################### [100%] [root at fa15404db2db /]# cp -a /var/lib/rpm/ /tmp/rpm1 [root at fa15404db2db /]# ``` From qboosh at pld-linux.org Sat Apr 25 16:40:24 2020 From: qboosh at pld-linux.org (Jakub Bogusz) Date: Sat, 25 Apr 2020 16:40:24 +0200 Subject: poldek th-x32 glibc upgrade problem [builder-th-x32@pld-linux.org: ERRORS: COMMAND] Message-ID: <20200425144024.GA27420@mail> Why poldek ignores glibc-2.31-5.x86_64 upgrade, even when specified explicitly on command line? (I started with "-n th-all -Uvg glibc", then tried to add more and more explicit package names... but in each case third arch glibc (base) package is ignored and upgrade fails). make-request -b th-x32 -c 'poldek -n th-all -Uvg glibc-2.31-5.x32 glibc-2.31-5.x86_64 glibc-2.31-5.i686 glibc-headers-2.31-5.x32 glibc-devel-2.31-5.x86_64 glibc-devel-2.31-5.i686 glibc-devel-2.31-5.x32 glibc-misc-2.31-5.x32' ----- Forwarded message from PLD th-x32 builder ----- X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on mail.qboosh.pl X-Spam-Level: X-Spam-Status: No, score=-0.0 required=5.0 tests=AWL,BAYES_00, DNS_FROM_AHBL_RHSBL,FH_DATE_PAST_20XX,SUBJ_ALL_CAPS autolearn=no version=3.2.5 X-Original-To: pld at qboosh.pl X-Entity-Ref-ID: 1db2b888-15e5-40dc-8e53-43e928caf59f From: PLD th-x32 builder To: qboosh at pld-linux.org X-PLD-Builder: th-x32 Cc: pld-logs-th at lists.pld-linux.org Date: Sat, 25 Apr 2020 14:35:15 +0000 Subject: ERRORS: COMMAND COMMAND (): FAILED --- COMMAND:: Build-Time: user:12.38s sys:6.49s real:18.92s (faults io:0 non-io:1501190) *** buildlog for COMMAND Loading [pndir]th... Loading [pndir]th... Loading [pndir]th-x86_64... Loading [pndir]th-i686... 65598 packages read Processing dependencies... glibc-2.31-1.i686 obsoleted by glibc-2.31-5.i686 glibc-2.31-5.i686 marks glibc-ld-2.31-5.i686 (cap glibc-ld = 6:2.31-5) glibc-ld-2.31-1.i686 obsoleted by glibc-ld-2.31-5.i686 glibc-2.31-1.x32 obsoleted by glibc-2.31-5.x32 glibc-devel-2.31-1.x32 obsoleted by glibc-devel-2.31-5.x32 glibc-devel-2.31-5.x32 marks glibc-devel-utils-2.31-5.x32 (cap glibc-devel-utils = 6:2.31-5) glibc-devel-utils-2.31-1.x32 obsoleted by glibc-devel-utils-2.31-5.x32 greedy upgrade glibc-devel-2.31-1.x86_64 to 2.31-5.x86_64 (unresolved glibc-devel-utils = 6:2.31-1) glibc-devel-2.31-1.x86_64 obsoleted by glibc-devel-2.31-5.x86_64 glibc-devel-2.31-5.x86_64 marks glibc-libcrypt-2.31-5.x86_64 (cap glibc-libcrypt(x86_64) = 6:2.31-5) glibc-libcrypt-2.31-1.x86_64 obsoleted by glibc-libcrypt-2.31-5.x86_64 glibc-devel-2.31-1.i686 obsoleted by glibc-devel-2.31-5.i686 greedy upgrade glibc-static-2.31-1.x32 to 2.31-5.x32 (unresolved glibc-devel = 6:2.31-1) glibc-static-2.31-1.x32 obsoleted by glibc-static-2.31-5.x32 glibc-devel-2.31-5.i686 marks glibc-libcrypt-2.31-5.i686 (cap glibc-libcrypt(i686) = 6:2.31-5) glibc-libcrypt-2.31-1.i686 obsoleted by glibc-libcrypt-2.31-5.i686 glibc-devel-2.31-5.x32 marks glibc-libcrypt-2.31-5.x32 (cap glibc-libcrypt(x32) = 6:2.31-5) glibc-libcrypt-2.31-1.x32 obsoleted by glibc-libcrypt-2.31-5.x32 glibc-headers-2.31-1.x32 obsoleted by glibc-headers-2.31-5.x32 glibc-misc-2.31-1.x32 obsoleted by glibc-misc-2.31-5.x32 There are 13 packages to install (7 marked by dependencies), 13 to remove: U glibc-2.31.(1 => 5).i686 glibc-2.31.(1 => 5).x32 U glibc-devel-2.31.(1 => 5).i686 glibc-devel-2.31.(1 => 5).x32 U glibc-devel-utils-2.31.(1 => 5).x32 U glibc-headers-2.31.(1 => 5).x32 glibc-ld-2.31.(1 => 5).i686 U glibc-libcrypt-2.31.(1 => 5).i686 U glibc-libcrypt-2.31.(1 => 5).x32 glibc-misc-2.31.(1 => 5).x32 U glibc-static-2.31.(1 => 5).x32 A glibc-devel-2.31-5.x86_64 glibc-libcrypt-2.31-5.x86_64 This operation will use 1.6KB of disk space. Need to get 8.3MB of archives. Executing pm-command.sh --upgrade -vh --root / --define _check_dirname_deps 1... Preparing... ################################################## error: Install/Erase problems: file /usr/share/doc/glibc-2.31/NEWS.gz from install of glibc-2.31-5.i686 conflicts with file from package glibc-2.31-1.x86_64 file /usr/share/doc/glibc-2.31/NEWS.gz from install of glibc-2.31-5.x32 conflicts with file from package glibc-2.31-1.x86_64 Begin-PLD-Builder-Info Build-Time: user:12.38s sys:6.49s real:18.92s (faults io:0 non-io:1501190) End-PLD-Builder-Info ----- End forwarded message ----- -- Jakub Bogusz http://qboosh.pl/ From baggins at pld-linux.org Sat Apr 25 22:20:55 2020 From: baggins at pld-linux.org (Jan =?utf-8?Q?R=C4=99korajski?=) Date: Sat, 25 Apr 2020 22:20:55 +0200 Subject: poldek th-x32 glibc upgrade problem [builder-th-x32@pld-linux.org: ERRORS: COMMAND] In-Reply-To: <20200425144024.GA27420@mail> References: <20200425144024.GA27420@mail> Message-ID: <20200425202055.GB2077@starbug> On Sat, 25 Apr 2020, Jakub Bogusz wrote: > Why poldek ignores glibc-2.31-5.x86_64 upgrade, even when specified explicitly on command > line? > > (I started with "-n th-all -Uvg glibc", then tried to add more and more > explicit package names... but in each case third arch glibc (base) package is ignored > and upgrade fails). > > > make-request -b th-x32 -c 'poldek -n th-all -Uvg glibc-2.31-5.x32 glibc-2.31-5.x86_64 glibc-2.31-5.i686 glibc-headers-2.31-5.x32 glibc-devel-2.31-5.x86_64 glibc-devel-2.31-5.i686 glibc-devel-2.31-5.x32 glibc-misc-2.31-5.x32' > > ----- Forwarded message from PLD th-x32 builder ----- > > X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on mail.qboosh.pl > X-Spam-Level: > X-Spam-Status: No, score=-0.0 required=5.0 tests=AWL,BAYES_00, > DNS_FROM_AHBL_RHSBL,FH_DATE_PAST_20XX,SUBJ_ALL_CAPS autolearn=no version=3.2.5 > X-Original-To: pld at qboosh.pl > X-Entity-Ref-ID: 1db2b888-15e5-40dc-8e53-43e928caf59f > From: PLD th-x32 builder > To: qboosh at pld-linux.org > X-PLD-Builder: th-x32 > Cc: pld-logs-th at lists.pld-linux.org > Date: Sat, 25 Apr 2020 14:35:15 +0000 > Subject: ERRORS: COMMAND > > COMMAND (): FAILED > > --- COMMAND:: > Build-Time: user:12.38s sys:6.49s real:18.92s (faults io:0 non-io:1501190) > > > > *** buildlog for COMMAND > Loading [pndir]th... > Loading [pndir]th... > Loading [pndir]th-x86_64... > Loading [pndir]th-i686... > 65598 packages read > Processing dependencies... > glibc-2.31-1.i686 obsoleted by glibc-2.31-5.i686 > glibc-2.31-5.i686 marks glibc-ld-2.31-5.i686 (cap glibc-ld = 6:2.31-5) > glibc-ld-2.31-1.i686 obsoleted by glibc-ld-2.31-5.i686 > glibc-2.31-1.x32 obsoleted by glibc-2.31-5.x32 > glibc-devel-2.31-1.x32 obsoleted by glibc-devel-2.31-5.x32 > glibc-devel-2.31-5.x32 marks glibc-devel-utils-2.31-5.x32 (cap glibc-devel-utils = 6:2.31-5) > glibc-devel-utils-2.31-1.x32 obsoleted by glibc-devel-utils-2.31-5.x32 > greedy upgrade glibc-devel-2.31-1.x86_64 to 2.31-5.x86_64 (unresolved glibc-devel-utils = 6:2.31-1) > glibc-devel-2.31-1.x86_64 obsoleted by glibc-devel-2.31-5.x86_64 > glibc-devel-2.31-5.x86_64 marks glibc-libcrypt-2.31-5.x86_64 (cap glibc-libcrypt(x86_64) = 6:2.31-5) > glibc-libcrypt-2.31-1.x86_64 obsoleted by glibc-libcrypt-2.31-5.x86_64 > glibc-devel-2.31-1.i686 obsoleted by glibc-devel-2.31-5.i686 > greedy upgrade glibc-static-2.31-1.x32 to 2.31-5.x32 (unresolved glibc-devel = 6:2.31-1) > glibc-static-2.31-1.x32 obsoleted by glibc-static-2.31-5.x32 > glibc-devel-2.31-5.i686 marks glibc-libcrypt-2.31-5.i686 (cap glibc-libcrypt(i686) = 6:2.31-5) > glibc-libcrypt-2.31-1.i686 obsoleted by glibc-libcrypt-2.31-5.i686 > glibc-devel-2.31-5.x32 marks glibc-libcrypt-2.31-5.x32 (cap glibc-libcrypt(x32) = 6:2.31-5) > glibc-libcrypt-2.31-1.x32 obsoleted by glibc-libcrypt-2.31-5.x32 > glibc-headers-2.31-1.x32 obsoleted by glibc-headers-2.31-5.x32 > glibc-misc-2.31-1.x32 obsoleted by glibc-misc-2.31-5.x32 > There are 13 packages to install (7 marked by dependencies), 13 to remove: > U glibc-2.31.(1 => 5).i686 glibc-2.31.(1 => 5).x32 > U glibc-devel-2.31.(1 => 5).i686 glibc-devel-2.31.(1 => 5).x32 > U glibc-devel-utils-2.31.(1 => 5).x32 > U glibc-headers-2.31.(1 => 5).x32 glibc-ld-2.31.(1 => 5).i686 > U glibc-libcrypt-2.31.(1 => 5).i686 > U glibc-libcrypt-2.31.(1 => 5).x32 glibc-misc-2.31.(1 => 5).x32 > U glibc-static-2.31.(1 => 5).x32 > A glibc-devel-2.31-5.x86_64 glibc-libcrypt-2.31-5.x86_64 > This operation will use 1.6KB of disk space. > Need to get 8.3MB of archives. > Executing pm-command.sh --upgrade -vh --root / --define _check_dirname_deps 1... > Preparing... ################################################## > error: Install/Erase problems: > file /usr/share/doc/glibc-2.31/NEWS.gz from install of glibc-2.31-5.i686 conflicts with file from package glibc-2.31-1.x86_64 > file /usr/share/doc/glibc-2.31/NEWS.gz from install of glibc-2.31-5.x32 conflicts with file from package glibc-2.31-1.x86_64 > Begin-PLD-Builder-Info > Build-Time: user:12.38s sys:6.49s real:18.92s (faults io:0 non-io:1501190) > > End-PLD-Builder-Info Maybe open a bug for poldek? https://github.com/poldek-pm/poldek/issues -- Jan R?korajski | PLD/Linux SysAdm | bagginspld-linux.org | http://www.pld-linux.org/ From baggins at pld-linux.org Sun Apr 26 11:00:06 2020 From: baggins at pld-linux.org (Jan =?utf-8?Q?R=C4=99korajski?=) Date: Sun, 26 Apr 2020 11:00:06 +0200 Subject: poldek th-x32 glibc upgrade problem [builder-th-x32@pld-linux.org: ERRORS: COMMAND] In-Reply-To: <20200425202055.GB2077@starbug> References: <20200425144024.GA27420@mail> <20200425202055.GB2077@starbug> Message-ID: <20200426090006.GC2077@starbug> On Sat, 25 Apr 2020, Jan R?korajski wrote: > On Sat, 25 Apr 2020, Jakub Bogusz wrote: > > > Why poldek ignores glibc-2.31-5.x86_64 upgrade, even when specified explicitly on command > > line? > > > > (I started with "-n th-all -Uvg glibc", then tried to add more and more > > explicit package names... but in each case third arch glibc (base) package is ignored > > and upgrade fails). > > > > > > make-request -b th-x32 -c 'poldek -n th-all -Uvg glibc-2.31-5.x32 glibc-2.31-5.x86_64 glibc-2.31-5.i686 glibc-headers-2.31-5.x32 glibc-devel-2.31-5.x86_64 glibc-devel-2.31-5.i686 glibc-devel-2.31-5.x32 glibc-misc-2.31-5.x32' [...] > > Maybe open a bug for poldek? > > https://github.com/poldek-pm/poldek/issues > Copy-pasted your report into https://github.com/poldek-pm/poldek/issues/10 Let's see what the author will say. -- Jan R?korajski | PLD/Linux SysAdm | bagginspld-linux.org | http://www.pld-linux.org/