From: Alexey Gladkov <legion@kernel.org>
To: kbd@lists.linux.dev, Steffen Nurpmeso <steffen@sdaoden.eu>
Subject: Re: kbd 2.9.0: build error (under fakeroot(1) environment)
Date: Tue, 9 Sep 2025 17:24:09 +0200 [thread overview]
Message-ID: <aMBGmTfQO-ukr9GP@example.org> (raw)
In-Reply-To: <20250909134533._bzZjw_N@steffen%sdaoden.eu>
On Tue, Sep 09, 2025 at 03:45:33PM +0200, Steffen Nurpmeso wrote:
> Hello.
>
> My distribution (CRUX) updated to 2.9.0, and the build failed via
>
> cp: failed to preserve ownership for /tmp/.pkgmk/pkg/usr/share/kbd/keymaps/i386/qwertz/sr-latin.map.gz: Operation not supported
>
> Thing is that this seems to only work for real root user, but that
> is not who is doing it, really.
cp -a is used in the makefile. The -a means no dereference and preserve
links and other attributes. This should not be a problem if you have
the same user.
> Problem is also that the build system uses "set -e", and cp(1) will exit
> error no matter what (-f etc) after the above.
>
> From my superficial BSD-style-simple-filesystem-usage point of
> view symbolic links have no attributes to preserve, but that
> sounds dick. Maybe it is a GNU coreutils cp(1) "exaggeration" to
> say and fail for the above for a symbolic link, as it seems to be
> only about ownership, not whatever attribute or security context,
> however, still.
You can try to change "cp -a" by "cp -dPR". Maybe this will help with
fakeroot.
> In data/Makefile.* a lot of work is done after these "cp -a"s,
> i wonder why beyond $(IGNORE_KEYMAPS) anything that is a symbolic
> link is not "simply" $(LN_S)d after $(DESTDIR) has been populated,
> as it is cd(1) entered for work anyway? Ie, some kind of
> $(SYMLINK_KEYMAPS) or something.
I didn't understand your point.
Among the keymaps, there are symlinks to change the keymap name.
Previously, when compressing keymaps, symlinks were dereferenced and
a copy of the keymap appeared instead of the symlink.
I don't want to create symlinks in Makefile at the time of install. This
is really hard to maintain.
>
> Thank you!!
> And Ciao! from Germany,
>
> --steffen
> |
> |Der Kragenbaer, The moon bear,
> |der holt sich munter he cheerfully and one by one
> |einen nach dem anderen runter wa.ks himself off
> |(By Robert Gernhardt)
>
--
Rgrds, legion
next prev parent reply other threads:[~2025-09-09 15:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-09 13:45 kbd 2.9.0: build error (under fakeroot(1) environment) Steffen Nurpmeso
2025-09-09 15:24 ` Alexey Gladkov [this message]
2025-09-09 21:18 ` Steffen Nurpmeso
2025-09-10 9:59 ` Alexey Gladkov
2025-09-10 12:37 ` Steffen Nurpmeso
2025-09-19 15:16 ` Alexey Gladkov
2025-09-20 15:57 ` Steffen Nurpmeso
2025-09-20 16:22 ` bug#79433: " Paul Eggert
2025-09-20 20:43 ` Steffen Nurpmeso
2025-09-21 16:57 ` Paul Eggert
2025-09-22 16:21 ` Steffen Nurpmeso
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=aMBGmTfQO-ukr9GP@example.org \
--to=legion@kernel.org \
--cc=kbd@lists.linux.dev \
--cc=steffen@sdaoden.eu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.