[Solved]systemd kills boot up till version 252.1-2-arch

Morta · 2022-12-16 19:31:56

sd-encrypt is needed when you have two volume. I’m same opinion the bootloader is not the problem. It’s really in systemd

seth · 2022-12-16 21:05:39

	rootwait	[KNL] Wait (indefinitely) for root device to show up.
			Useful for devices that are detected asynchronously
			(e.g. USB and MMC devices).

You're not supposed to end in an emergency shell if you correctly added that, the kernel will just wait.
In doubt (also) https://wiki.archlinux.org/title/System … te_machine

Morta · 2022-12-17 08:04:44

Morta wrote:

git tag
001
002
003
004
005
006
007
008
009
010
011
012
013
014
015
016
017
018
019
020
021
022
023
024
I have this list as git tag command. How I know which is systemd252.1-2 and the other systemd252.2-1 to add a good commit and bad commit
I did following
git clone https://github.com/archlinux/svntogit-packages.git
git tag
git bisect good 4bbea20
git bisect bad 5ad540c
cd trunk
makepkg -efsi 
makepkg fails with meson error. What I did wrong?

Why I can’t build systemd with this?

seth · 2022-12-17 08:16:26

Instead of quoting your entire previous post for no reason, read https://bbs.archlinux.org/viewtopic.php?id=57855

Morta · 2022-12-19 15:36:58

[morta@lapt0p trunk]$ makepkg -efsi 
==> Making package: systemd 252.1-2 (Mon 19 Dec 2022 04:35:47 PM CET)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> WARNING: Using existing $srcdir/ tree
==> Starting build()...
+ exec meson setup --prefix /usr --libexecdir lib --sbindir bin --buildtype plain --auto-features enabled --wrap-mode nodownload -D b_lto=true -D b_pie=true systemd-stable build -Dversion-tag=252.1-2-arch -Dshared-lib-tag=252.1-2 -Dmode=release -Dgnu-efi=true -Dima=false -Dlibidn2=true -Dlz4=true -Dman=true -Ddbuspolicydir=/usr/share/dbus-1/system.d -Ddefault-dnssec=no -Ddefault-hierarchy=unified -Ddefault-kill-user-processes=false -Ddefault-locale=C.UTF-8 -Dlocalegen-path=/usr/bin/locale-gen -Ddns-over-tls=openssl -Dfallback-hostname=archlinux -Dnologin-path=/usr/bin/nologin '-Dntp-servers=0.arch.pool.ntp.org 1.arch.pool.ntp.org 2.arch.pool.ntp.org 3.arch.pool.ntp.org' '-Ddns-servers=1.1.1.1#cloudflare-dns.com 9.9.9.9#dns.quad9.net 8.8.8.8#dns.google 2606:4700:4700::1111#cloudflare-dns.com 2620:fe::9#dns.quad9.net 2001:4860:4860::8888#dns.google' -Drpmmacrosdir=no -Dsysvinit-path= -Dsysvrcnd-path= -Dsbat-distro=arch '-Dsbat-distro-summary=Arch Linux' -Dsbat-distro-pkgname=systemd -Dsbat-distro-version=252.1 -Dsbat-distro-url=https://archlinux.org/packages/core/x86_64/systemd/

ERROR: Neither directory contains a build file meson.build.
==> ERROR: A failure occurred in build().
    Aborting...

It's fails because of no meson.install file? What I have to do?

Last edited by Morta (2022-12-19 15:37:44)

seth · 2022-12-19 16:02:49

Did you clone the entire repo?
Please use asp, https://wiki.archlinux.org/title/Arch_B … _using_Git

Morta · 2022-12-19 16:03:30

Yes. I didn't found the link for only systemd

Morta · 2022-12-19 16:07:57

When I do

asp export systemd
asp update systemd
asp checkout systemd

I got following error

fatal: not a git repository (or any parent up to mount point /)
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).

Morta · 2022-12-19 16:12:06

Same error with meson.install like above

asp checkout systemd 
cd systemd
git bisect good 4bbea20
git bisect bad 5ad540c
cd trunk
makepkg -efsi

Are the bisect token correct. I got from the github packege should be systemdv252.1 and v252.2?

Last edited by Morta (2022-12-19 16:17:56)

seth · 2022-12-19 16:28:00

D'oohh - you're bisecting the systemd-package, not systemd.
(Sorry I didn't pay attention to what you're actually doing there)

You want to bisect https://aur.archlinux.org/packages/systemd-git

Morta · 2022-12-19 16:43:48

[morta@lapt0p systemd-git]$ git bisect start
Already on 'master'
Your branch is up to date with 'origin/master'.
status: waiting for both good and bad commits
[morta@lapt0p systemd-git]$ git bisect good 9f32d686e3b8a03479c389bef6fb343dda274686 
status: waiting for bad commit, 1 good commit known
[morta@lapt0p systemd-git]$ git bisect bad a02f5ef8147e4dcdb837fee135e6383fbce39132
a02f5ef8147e4dcdb837fee135e6383fbce39132 is the first bad commit
commit a02f5ef8147e4dcdb837fee135e6383fbce39132
Author: Yurii Kolesnykov <root@yurikoles.com>
Date:   Mon Oct 17 03:47:43 2022 +0300

    sync with testing/systemd
    
    Signed-off-by: Yurii Kolesnykov <root@yurikoles.com>

 .SRCINFO                                       | 20 +++++++--------
 0001-Use-Arch-Linux-device-access-groups.patch | 35 ++++++++++----------------
 PKGBUILD                                       | 28 ++++++++++++---------
 3 files changed, 39 insertions(+), 44 deletions(-)
[morta@lapt0p systemd-git]$ makepkg -efsi 
==> Making package: systemd-git 252.r60865.9df82722f6-1 (Mon 19 Dec 2022 05:43:03 PM CET)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> WARNING: Using existing $srcdir/ tree
==> Starting pkgver()...
/tmp/systemd-git/PKGBUILD: line 58: cd: systemd: No such file or directory
==> ERROR: A failure occurred in pkgver().
    Aborting...

Seems not to work?!

Morta · 2022-12-19 17:05:48

Ok. I got it.

[morta@5erver systemd-git]$ cd systemd/
[morta@5erver systemd]$ git bisect start
status: waiting for both good and bad commits
[morta@5erver systemd]$ git bisect good b622e95 
status: waiting for bad commit, 1 good commit known
[morta@5erver systemd]$ git bisect bad  7dbbb39
Bisecting: 1176 revisions left to test after this (roughly 10 steps)
[5cdc7c89cb437eb46fb24ad62b9792c1b8aa4d69] test-network: rename tun99 and tap99
[morta@5erver systemd]$ makepkg -rsi

I have 10 steps for bisect. I built first package. How I can bisect a step forward when this package works?

Last edited by Morta (2022-12-19 17:10:43)

seth · 2022-12-19 17:15:23

git bisect help

Morta · 2022-12-19 17:58:22

Ok the first build has the error in it. What should I do now?

I did bisect next but is not necessary because is in it. How I is the code to git revert the first commit? . git bisect help didn't helped me...

Morta · 2022-12-19 19:34:40

Ok I have to choose if it's bad or good

That is the result

git bisect bad
3ec3ae68d2cea32461d779645a737d57160631bf is the first bad commit
commit 3ec3ae68d2cea32461d779645a737d57160631bf
Author: Zbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl>
Date:   Thu May 19 09:50:48 2022 +0200

    basic/strv: add optimizable version of strv_push/consume/extend
    
    This will be helpful in cases where we are repeatedly adding entries
    to a long strv and want to skip the iteration over old entries leading
    to quadratic behaviour.
    
    Note that we don't want to calculate the length if not necessary, so
    the calculation is delayed until after we've checked that value is not
    NULL.

 src/basic/strv.c     | 30 ++++++++++++++++++------------
 src/basic/strv.h     | 24 +++++++++++++++++++++---
 src/test/test-strv.c | 43 +++++++++++++++++++++++++++++++++++++++++++
 3 files changed, 82 insertions(+), 15 deletions(-)

I have 10 bad chooses and after all it's dosen't work

How I can do it?

git revert 3ec3ae68d2cea32461d779645a737d57160631bf doesn't work

Last edited by Morta (2022-12-19 19:57:35)

cfr · 2022-12-20 02:20:23

What do you mean it doesn't work? I'm not really familiar with doing this, but hasn't that identified the 'first bad commit'? That's what git bisect is supposed to do, isn't it?

Morta · 2022-12-20 06:22:28

Yes but the build without the bad commit doesn’t work?! Have to revert manually?

seth · 2022-12-20 08:26:52

Yes.
However https://github.com/systemd/systemd/comm … 57160631bf adds and generalizes some string handling routine.
This is probably API/ABI unstable, so might cause trouble if you installed only systemd or systemd-libs, but it's hard to imagine how this would be the breaking commit.
(So honestly, I think you made some mistake during the tests, most likely partial installations of systemd)

Since it introduces an API change, you will also not be able to revert it in isolation.

Morta · 2022-12-21 16:39:23

Ok.

Now I have the problem that I want start at 252.1-2? How I can adjust that start by 252.1-2 on systemd-git? It's hasn't this build version only long token versions? How can I say that should start with this build? Is this automated with bisect for makepkg?

Should that not start with a good one? When I choose a good version and a bad version?

It's build me everytime this version systemd-git 252.r61691.09ed55c26d-1

Last edited by Morta (2022-12-21 17:38:26)

seth · 2022-12-23 23:24:22

"252.1-2" is not a git tag, but the second build of 252.1 (incl. some cherry-picked patches)

[morta@5erver systemd]$ git bisect good b622e95 
status: waiting for bad commit, 1 good commit known
[morta@5erver systemd]$ git bisect bad  7dbbb39

tests between 251 and 252-rc2
The problem isn't where you frame the bisct, but how you perform it.

Ok the first build has the error in it. What should I do now?
I did bisect next but is not necessary because is in it. How I is the code to git revert the first commit? . git bisect help didn't helped me...

Bisection means that you define a start and end, then a commit midway threw is selected, you state whether it's good or bad and that decides which commit is picked next.
You continue that until you found the last good and first bad commit.
https://wiki.archlinux.org/title/Bisect … s_with_Git

Morta · 2022-12-24 14:37:30

I did

git clone https://aur.archlinux.org/systemd-git.git
cd systemd-git

git clone https://github.com/systemd/systemd.git
cd systemd
git bisect start
git bisect good b622e95 v251
git bisect bad 9ca1efb v252.rc2
cd ..
makepkg -efsi

First build ok
systemd-git-252.r.09ed55c-1-x86_64.pkg.tar.zst

Do not function!
cd systemd
git bisect bad
makpkg -efsi

I got following error:

[morta@5erver systemd-git]$ makepkg -efsi
==> Making package: systemd-git 252.r.09ed55c-1 (Sat 24 Dec 2022 01:28:51 PM CET)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> WARNING: Using existing $srcdir/ tree
==> Starting pkgver()...
error: object directory /home/morta/build/systemd-git/systemd/objects does not exist; check .git/objects/info/alternates
fatal: bad object HEAD
error: object directory /home/morta/build/systemd-git/systemd/objects does not exist; check .git/objects/info/alternates
==> Removing existing $pkgdir/ directory...
==> Starting build()...
+ exec meson setup --prefix /usr --libexecdir lib --sbindir bin --buildtype plain --auto-features enabled --wrap-mode nodownload -D b_lto=true -D b_pie=true systemd build -Dversion-tag=252.r.09ed55c-1-arch -Dshared-lib-tag=252.r.09ed55c-1 -Dmode=release -Dgnu-efi=true -Dima=false -Dlibidn2=true -Dlz4=true -Dman=true -Ddbuspolicydir=/usr/share/dbus-1/system.d -Ddefault-dnssec=no -Ddefault-hierarchy=unified -Ddefault-kill-user-processes=false -Ddefault-locale=C.UTF-8 -Dlocalegen-path=/usr/bin/locale-gen -Ddns-over-tls=openssl -Dfallback-hostname=archlinux -Dnologin-path=/usr/bin/nologin '-Dntp-servers=0.arch.pool.ntp.org 1.arch.pool.ntp.org 2.arch.pool.ntp.org 3.arch.pool.ntp.org' '-Ddns-servers=1.1.1.1#cloudflare-dns.com 9.9.9.9#dns.quad9.net 8.8.8.8#dns.google 2606:4700:4700::1111#cloudflare-dns.com 2620:fe::9#dns.quad9.net 2001:4860:4860::8888#dns.google' -Drpmmacrosdir=no -Dsysvinit-path= -Dsysvrcnd-path= -Dsbat-distro=arch '-Dsbat-distro-summary=Arch Linux' -Dsbat-distro-pkgname=systemd-git -Dsbat-distro-version=252.r.09ed55c -Dsbat-distro-url=https://archlinux.org/packages/core/x86_64/systemd-git/
Directory already configured.

Just run your build command (e.g. ninja) and Meson will regenerate as necessary.
If ninja fails, run "ninja reconfigure" or "meson setup --reconfigure"
to force Meson to regenerate.

If build failures persist, run "meson setup --wipe" to rebuild from scratch
using the same options as passed when configuring the build.
To change option values, run "meson configure" instead.

ERROR: Build directory has been generated with Meson version 0.64.1, which is incompatible with the current version 1.0.0.
==> ERROR: A failure occurred in build().
    Aborting...

Why?

seth · 2022-12-24 17:22:08

Because

ERROR: Build directory has been generated with Meson version 0.64.1, which is incompatible with the current version 1.0.0.

Why you're using different meson versions for different builds is kinda beyond me. You probably updated the system inbetween builds??
Get rid of the meson build dir or start over (ie. build everything w/ meson 1.0.0)

Morta · 2022-12-25 06:08:29

You are right!

Morta · 2022-12-25 13:38:01

I get following error to build with meson. I can't build with v.1.0.0.

This meson log is comming after two git bisect bad
https://0x0.st/o5E2.txt

I have a timeout by building mountpoint and actually there is the problem

How I can achieve my goal?

Last edited by Morta (2022-12-25 13:39:52)

Morta · 2023-01-02 17:01:26

https://github.com/systemd/systemd/issues/25893

So how I can solve this issue when no one helps?!

Arch Linux

#51 2022-12-16 19:31:56

Re: [Solved]systemd kills boot up till version 252.1-2-arch

#52 2022-12-16 21:05:39

Re: [Solved]systemd kills boot up till version 252.1-2-arch

#53 2022-12-17 08:04:44

Re: [Solved]systemd kills boot up till version 252.1-2-arch

#54 2022-12-17 08:16:26

Re: [Solved]systemd kills boot up till version 252.1-2-arch

#55 2022-12-19 15:36:58

Re: [Solved]systemd kills boot up till version 252.1-2-arch

#56 2022-12-19 16:02:49

Re: [Solved]systemd kills boot up till version 252.1-2-arch

#57 2022-12-19 16:03:30

Re: [Solved]systemd kills boot up till version 252.1-2-arch

#58 2022-12-19 16:07:57

Re: [Solved]systemd kills boot up till version 252.1-2-arch

#59 2022-12-19 16:12:06

Re: [Solved]systemd kills boot up till version 252.1-2-arch

#60 2022-12-19 16:28:00

Re: [Solved]systemd kills boot up till version 252.1-2-arch

#61 2022-12-19 16:43:48

Re: [Solved]systemd kills boot up till version 252.1-2-arch

#62 2022-12-19 17:05:48

Re: [Solved]systemd kills boot up till version 252.1-2-arch

#63 2022-12-19 17:15:23

Re: [Solved]systemd kills boot up till version 252.1-2-arch

#64 2022-12-19 17:58:22

Re: [Solved]systemd kills boot up till version 252.1-2-arch

#65 2022-12-19 19:34:40

Re: [Solved]systemd kills boot up till version 252.1-2-arch

#66 2022-12-20 02:20:23

Re: [Solved]systemd kills boot up till version 252.1-2-arch

#67 2022-12-20 06:22:28

Re: [Solved]systemd kills boot up till version 252.1-2-arch

#68 2022-12-20 08:26:52

Re: [Solved]systemd kills boot up till version 252.1-2-arch

#69 2022-12-21 16:39:23

Re: [Solved]systemd kills boot up till version 252.1-2-arch

#70 2022-12-23 23:24:22

Re: [Solved]systemd kills boot up till version 252.1-2-arch

#71 2022-12-24 14:37:30

Re: [Solved]systemd kills boot up till version 252.1-2-arch

#72 2022-12-24 17:22:08

Re: [Solved]systemd kills boot up till version 252.1-2-arch

#73 2022-12-25 06:08:29

Re: [Solved]systemd kills boot up till version 252.1-2-arch

#74 2022-12-25 13:38:01

Re: [Solved]systemd kills boot up till version 252.1-2-arch

#75 2023-01-02 17:01:26

Re: [Solved]systemd kills boot up till version 252.1-2-arch

Board footer