warning: filesystem: local (2023.09.18-1.0) is newer than core (2023.01.31-1.0)

Effect: you can not log in.
The SSHd child runs on 100% CPU doing something.
This happens on i486, i686 and pentium4 equally.

# pacman -Syyuu base
# pacman -S pandoc
# pandoc
pandoc: error while loading shared libraries: libHSzip-archive-0.4.1-FOOm53qGfUr2AB1Oel9iH4-ghc8.10.2.so: cannot open shared object file: No such file or directory

python-setuptools-scm 7.1.0-4.1 as found in the repo is missing the dependencies python-packaging and python-setuptools, which breaks the build of many other packages.

From a fresh install just now:

The /usr/lib/python3.10/site-packages folder is full of dozens of files, but there is little in the 3.11 folder. Some examples: gajim yt-dlp zippy samba.

This seems to affect most new packages that I install, so it is by no means limited to just the examples.

Nov 06 08:04:01 eurohp1 systemd[1]: Starting IPv4 Packet Filtering Framework… Nov 06 08:04:01 eurohp1 iptables-restore[287]: Another app is currently holding the xtables lock. Perhap>
Nov 06 08:04:01 eurohp1 systemd[1]: iptables.service: Main process exited, code=exited, status=4/NOPERMI>
Nov 06 08:04:01 eurohp1 systemd[1]: iptables.service: Failed with result ‘exit-code’.
Nov 06 08:04:01 eurohp1 systemd[1]: Failed to start IPv4 Packet Filtering Framework.

Works when starting iptables later manually.

This is security relevant as not having a firewall after startup puts the system at risk.

The following tests FAILED:

       91 - s2n_pq_kem_hybrid_kat_test (Failed)
      145 - s2n_session_ticket_test (Failed)
      154 - s2n_stuffer_network_order_test (Failed)
      184 - s2n_x509_validator_test (Failed)

https://github.com/aws/s2n-tls/issues/2405 https://github.com/aws/s2n-tls/issues/2406 https://github.com/aws/s2n-tls/issues/2404

3 are known upstream too.

The current version of sddm (0.19.0-9.0) depends on the previous version of Qt (5.15.8). After updating Qt, sddm crashes with an incompatible Qt library error.

build
running build_py
npm WARN npm npm does not support Node.js v15.9.0
npm WARN npm You should probably upgrade to a newer version of node as we
npm WARN npm can't make any promises that npm will work with this version.
npm WARN npm Supported releases of Node.js are the latest release of 6, 8, 9, 10, 11, 12, 13.
npm WARN npm You can find the latest version at https://nodejs.org/

> sphinx_rtd_theme@0.5.1 preinstall /build/python-sphinx_rtd_theme/src/sphinx_rtd_theme-0.5.1
> bin/preinstall.js

Traceback (most recent call last):
  File "/build/python-sphinx_rtd_theme/src/sphinx_rtd_theme-0.5.1/setup.py", line 86, in <module>
    setup(
  File "/usr/lib/python3.9/site-packages/setuptools/__init__.py", line 153, in setup
    return distutils.core.setup(**attrs)
  File "/usr/lib/python3.9/distutils/core.py", line 148, in setup
    dist.run_commands()
  File "/usr/lib/python3.9/distutils/dist.py", line 966, in run_commands
    self.run_command(cmd)
  File "/usr/lib/python3.9/distutils/dist.py", line 985, in run_command
    cmd_obj.run()
  File "/usr/lib/python3.9/distutils/command/build.py", line 135, in run
    self.run_command(cmd_name)
  File "/usr/lib/python3.9/distutils/cmd.py", line 313, in run_command
    self.distribution.run_command(command)
  File "/usr/lib/python3.9/distutils/dist.py", line 985, in run_command
    cmd_obj.run()
  File "/build/python-sphinx_rtd_theme/src/sphinx_rtd_theme-0.5.1/setup.py", line 22, in run
    subprocess.run(['npm', 'install'], check=True)
  File "/usr/lib/python3.9/subprocess.py", line 524, in run
    raise CalledProcessError(retcode, process.args,
subprocess.CalledProcessError: Command '['npm', 'install']' died with <Signals.SIGSEGV: 11>.
==> ERROR: A failure occurred in build().
    Aborting...
==> ERROR: Build failed, check /var/lib/archbuild/staging-pentium4/abaumann/build

still linked against icu67.

Same here, I cannot believe that somebody is actually using thunderbird on Archlinux32 anymore.

Triggered rebuild, doesn’t build currently.

no task description

b3da2fc1c25065a1bd09f9930eeed1d11dc312e4 only updated half the package - we’re missing:

- update the logo
- update the url (?)
- only if both are done: updating the hash on top of the PKGBUILD

vboxdrv module is missing making virtualbox unusable.

I’m currently running kernel 5.9.0-1.0-pae but it doesn’t seem to be there in any version

[tutorial ] Saved pickle file: citations.pickle
[tutorial ] Exception occurred:
[tutorial ] File “/usr/lib/python2.7/site-packages/sphinx/environment/init.py”, line 152, in dump
[tutorial ] pickle.dump(env, f, pickle.HIGHEST_PROTOCOL)
[tutorial ] MemoryError
[tutorial ] The full traceback has been saved in /tmp/sphinx-err-kSNZ9A.log, if you want to report the issue to the developers.
[tutorial ] Please also report this if it was a user error, so that a better error message can be provided next time.
[tutorial ] A bug report can be filed in the tracker at . Thanks!
Build finished. The built documents can be found in /build/sagemath-doc/src/sage-8.1/src/doc/html/ja/tutorial
/startdir/PKGBUILD: line 79: 2540 Segmentation fault (core dumped) python2 sage_setup/docbuild –no-pdf-links -k all html
==> ERROR: A failure occurred in build().

  Aborting...

==> ERROR: Build failed, check /data/archbuild/staging-i686/copy/build

Bing Cache

Attached to Project: Archlinux32
Opened by Andreas Baumann - 10.05.2019
FS#70 - chromium needs SSE2

chromium starts, but every page it loads ends in “Aw snap” and on the console:

Check failed: cpu.has_sse2().

Google Cache

FS#68 : dmd rebuild results in gen_man segfault
Opened by Andreas Baumann - 01.05.2019. FS#68 - dmd rebuild results in gen_man segfault. make: Entering directory ‘/build/dmd/src/dmd/docs’ …

Starting check()… WARNING [pifpaf.drivers] `psutil.Popen(pid=2683, status=’terminated’)` is already gone, sending SIGKILL to its process group
WARNING [pifpaf.drivers] `psutil.Popen(pid=2671, status=’terminated’)` is already gone, sending SIGKILL to its process group
WARNING [pifpaf.drivers] `psutil.Popen(pid=2669, status=’terminated’)` is already gone, sending SIGKILL to its process group
ERROR [pifpaf] Error while running command: [b’/usr/bin/pg_ctl’, ‘-w’, ‘-o’, ‘-k /tmp/tmp5_5e9_hy -p 5432 -h “127.0.0.1”‘, ‘start’]
createdb: could not connect to database template1: could not connect to server: No such file or directory
Is the server running locally and accepting
connections on Unix domain socket “/run/postgresql/.s.PGSQL.5432”? ERROR: A failure occurred in check().
Aborting…
ERROR: Build failed, check /data/archbuild/staging-i686/arch32/build

Disabling tests for now.

  Comments (1)
  Related Tasks (0/0)

Admin
Andreas Baumann commented on 15.02.2018 16:56

Didn’t pifpaf itself had problems building? Maybe it’s a pifpaf issue..

Bing cache

Attached to Project: Archlinux32
Opened by Jeff Hodd - 11.07.2019
Last edited by Andreas Baumann - 09.08.2019
FS#82 - [glibc] ld warning: /usr/lib32/ld-linux.so.2: corrupt GNU_PROPERTY_TYPE (5) size: 0

All software builds are producing this warning. Some builds are failing because of the error return on linking. I’m also seeing failures on LD_PRELOADs.

/bin/ld: warning: /usr/lib/ld-linux.so.2: corrupt GNU_PROPERTY_TYPE (5) size: 0

Easy to reproduce. Just build this program:

# test.c
# Compiled with ‘gcc test.c’ int main() {

  return 0;

}

This was reported at bugs.archlinux.org (reference https://bugs.archlinux.org/task/63015) where it was closed and considered fixed if built using the –enable-cet flag. I built glibc with the –enable-cet flag, but am still seeing the failures, so not fixed.
Closed by Andreas Baumann
09.08.2019 11:44
Reason for closing: Fixed

  Comments (6)
  Related Tasks (0/0)

Jeff Hodd commented on 16.07.2019 03:29

I’ve narrowed down the glibc upgrade to glibc-2.29-1.26 -> glibc-2.29-1.27. The error doesn’t occur with glibc-2.29-1.26. There were 3 changes made to the arch32 PKGBUILD for the glibc-2.29-1.27 release. One of them caused this issue.
Admin
Andreas Baumann commented on 16.07.2019 05:33

There is another thing which can change: the toolchain.
This GNU_PROPERTY error is something the compiler emits (we think it’s CET stuff, but it’s badly
documented). Binutils ld seems not to like this ELF section.

The error is the same as in:

https://bugs.archlinux.org/task/63015

What’s puzzling me: –enable-cet is there in glibc, gcc, binutils (just not for i486, as CET doesn’t\
work for older CPUs).

Commit: 09d03cbd4c57b8eabfadd22b67929d958b2409d7 and d57a456faa674c24e8869a26a14c497c95accf1f in
glibc are mine, they try to change stack alignment and handling of SSE for pentium4 for Java, also without effect.
Admin
Andreas Baumann commented on 16.07.2019 05:35

About linker warnings being turned to errors (as for compiler warnings turned to errors): this
is something the DEVELOPER should do, NOT the PACKAGER. Released software should:
- NOT include asserts
- NOT include debug code
- NOT include code only used for running tests
- NOT use -Werror
- NOT use -Wl,–fatal-warnings

See for instance extra-cmake-modules-5.59.0-ld-no-fatal-warning.patch.
Jeff Hodd commented on 16.07.2019 21:50

I knew about the cet issue. Did quite abit of looking around to get some insight into it (even looked at the code - elf-properties.c - and it looks like the Elf_Internal_Note description size is coming back with a value of 0. the other possibility is that (size % 4) is something other than 0 which is less likely). From what i could gather, cet is supposed to be enabled in the latest builds of glibc for i686 even though, as you pointed out, it’s not well documented. I did do a 2.29-4 i686 build with cet enabled and it made no difference vis-a-vis the warning. I also checked the upstream diff between 2.29-1.26 and 2.29-1.27 and noticed the addition of –enable-static-pie and thought maybe position independent executables may explain it. Did another glibc build with static pie disabled and that made no difference. Am about to go back and check the diff again and see what else may have changed.

I did check the CMakeLists.txt file for my failing build and it uses -Werror and -Wl,–fatal-warnings so I will remove those. But that doesn;t actually fix the underlying issue of the warning which we shouldn;t be seeing.

It is up to the developer, but too often one has to show that a change fixes an issue before you’ll get any attention. I may not be THE developer for this particular package, but I am A developer (in general), so I don;t feel uncomfortable making code changes.

I’ll keep looking around for differences between the 1.26 and 1.27 builds.
Jeff Hodd commented on 16.07.2019 22:15

if (note->descsz < 8 || (note->descsz % align_size) != 0)

  {

bad_size:

    _bfd_error_handler
(_("warning: %pB: corrupt GNU_PROPERTY_TYPE (%ld) size: %#lx"),
 abfd, note->type, note->descsz);
    return FALSE;
  }

The warning is printing out the description size - and that’s 0.

Apparently it’s supposed to be >= 8 and divisible by 4:

unsigned int align_size = bed->s->elfclass == ELFCLASS64 ? 8 : 4;

I am assuming that arch32 doesn’t support ELFCLASS64.
Jeff Hodd commented on 22.07.2019 17:13

https://bbs.archlinux32.org/viewtopic.php?id=2770

Google Cache

on fresh install file /usr/lib/libbfd.so lacks header “/* GNU ld script */” so I see complains on terminal

All versions of mldonkey crash in arch32 updated. (segmentation fault and core dumped)

Attached to Project: Archlinux32
Opened by Andreas Baumann - 07.02.2019
FS#63 - nodejs crashes in libuv when cleaning up FSReqCallback

Program terminated with signal SIGSEGV, Segmentation fault.
#0 0×00945919 in node::fs::FSReqCallback::~FSReqCallback() ()
[Current thread is 1 (Thread 0xb5614880 (LWP 2013))]
(gdb) bt
#0 0×00945919 in node::fs::FSReqCallback::~FSReqCallback() ()
#1 0×00937274 in node::fs::FSReqAfterScope::~FSReqAfterScope() ()
#2 0x0093767d in node::fs::AfterInteger(uv_fs_s*) ()
#3 0xb7e910e0 in uv.work_done () from /usr/lib/libuv.so.1
#4 0xb7e9526e in ?? () from /usr/lib/libuv.so.1
#5 0xb7ea51f8 in uv.io_poll () from /usr/lib/libuv.so.1
#6 0xb7e95c51 in uv_run () from /usr/lib/libuv.so.1
#7 0x00905d37 in node::Start(v8::Isolate*, node::IsolateData*, std::vector, std::allocator >, std::allocator, std::allocator > > > const&, std::vector, std::allocator >, std::allocator, std::allocator > > > const&) ()
#8 0×00903655 in node::Start(int, char**) ()
#9 0x008acef1 in main ()

This affects gyp, vault and probably some other packages, depending whether those callbacks are used or not.

  Comments (1)
  Related Tasks (0/0)

Admin
Andreas Baumann commented on 07.02.2019 09:36

See also mailing list thread:

https://lists.archlinux.org/pipermail/arch-ports/2018-November/000835.html

Google Code

yes, confirmed, that’s because python 3.11 is the only package building and being
published to stable, the python modules need bootstrapping (since months).

experienced when building buildbot-www

/bin/sh: line 1: 4744 Segmentation fault (core dumped) yarn install –pure-lockfile

Very easy to reproduce. lldb version 10.0.0, just try to run any binary.

[aeden@arch32 bin]$ lldb $(which date)
(lldb) target create “/usr/bin/date” Current executable set to ‘/usr/bin/date’ (i386).
(lldb) run
error: failed to launch or debug process
(lldb)

Attached to Project: Archlinux32
Opened by Andreas Baumann - 14.04.2018
Last edited by Andreas Baumann - 16.04.2018
FS#36 - texlive-core: SSE2 required

(4/5) Updating TeXLive format files… PANIC: unprotected error in call to Lua API (CPU with SSE2 required)
fmtutil [ERROR]: running `luajittex -ini -jobname=luajittex -progname=luajittex luatex.ini /null’ return status 1
fmtutil [ERROR]: return error due to options –strict
error: command failed to execute correctly
(5/5) Updating TeXLive font maps…

So, the problem seems to be in lua itself?

Bing Cache