You are not logged in.
This happened after the upgrade to systemd 241.0-1 (and continues in 241.7-2):
root@bank ~# systemctl daemon-reload Integer 241 in '241 (241.7-2-arch)' followed by non-digit
Integer 241 in '241 (241.7-2-arch)' followed by non-digit
Is this specifically a package issue or something with systemd?
Offline
I got the same issue.
Updated about an hour ago.
Offline
The version number change is deliberate: https://git.archlinux.org/svntogit/pack … a789ea922a
And it seems that there are a few things that try to parse that string using means that break with the additional info.
Last edited by V1del (2019-02-22 11:59:30)
Offline
I am not getting any such message. Are you trying tab completion? Thats what appears to be so from your first line.
Offline
I am not getting any such message. Are you trying tab completion? Thats what appears to be so from your first line.
Nope, no tab completed, although I do have
sdr
expand to
systemctl daemon-reload
with fish abbreviations.. maybe that triggered it.
Offline
So why dont u try run 'systemctl daemon-reload' directly and check if it still shows the message
Offline
amish wrote:I am not getting any such message. Are you trying tab completion? Thats what appears to be so from your first line.
Nope, no tab completed, although I do have
sdr
expand to
systemctl daemon-reload
with fish abbreviations.. maybe that triggered it.
I am also running fish, so maybe it's fish related.
Offline
I am also running fish, so maybe it's fish related.
https://github.com/fish-shell/fish-shel … tl.fish#L1
Edit:
What is `$systemd_version` set to?
Last edited by loqs (2019-02-22 17:11:49)
Offline
Duckbuster wrote:I am also running fish, so maybe it's fish related.
https://github.com/fish-shell/fish-shel … tl.fish#L1
Edit:
What is `$systemd_version` set to?
~> set -l systemd_version (systemctl --version | string match "systemd*" | string replace -r "\D*(\d+)" '$1')
~> echo $systemd_version
241 (241.7-2-arch)
Offline
I can duplicate it by installing fish and typing "systemctl <TAB>", please submit an upstream bug to have them fix this.
(Maybe even use a shell like bash or zsh that comes with proper completions written and maintained by the package itself.)
Managing AUR repos The Right Way -- aurpublish (now a standalone tool)
Offline
I can duplicate it by installing fish and typing "systemctl <TAB>", please submit an upstream bug to have them fix this.
(Maybe even use a shell like bash or zsh that comes with proper completions written and maintained by the package itself.)
Thank you for the confirmation. Filed https://github.com/fish-shell/fish-shell/issues/5689.
And I'll stick with fish, I enjoy a shell that out of the box does 99% of the things I need
Offline
Fixed upstream, tagged for the 3.1.0 milestone.
Offline
My obvious biases are showing, aren't they?
You are nevertheless encouraged to submit an Arch bug report asking for this fix to be backported -- who knows when the 3.1.0 milestone will be released?
Managing AUR repos The Right Way -- aurpublish (now a standalone tool)
Offline
OT - Dont get offended but I dont think Arch linux is supposed to back port such trivial bug. Otherwise if everyone starts asking for backport of minor bugs we will have mountain of bug reports.
This can be easily fixed by affected users:
https://github.com/fish-shell/fish-shel … 63f9714b48
Backports are generally to be done only when its critical bug and/or upstream has delayed release long enough
So we should not encourage generating bug report in this case. Peace
Last edited by amish (2019-02-23 01:00:55)
Offline
OT - Dont get offended but I dont think Arch linux is supposed to back port such trivial bug. Otherwise if everyone starts asking for backport of minor bugs we will have mountain of bug reports.
This can be easily fixed by affected users:
https://github.com/fish-shell/fish-shel … 63f9714b48Backports are generally to be done only when its critical bug and/or upstream has delayed release long enough
So we should not encourage generating bug report in this case. Peace
Yeah but reading that link you posted this sounds like an issue Arch brought on it's self so it should be fixed.
Offline
Yeah but reading that link you posted this sounds like an issue Arch brought on it's self so it should be fixed.
What? This was broken, and then fixed, by upstream. How, exactly, did Arch bring this on itself?
Offline