OK, it looks like this is going to get fixed in the kernel. Closing this here.
In case the kernel fix won't make feel free to re-open the discussion.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Closed #1682.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/1682#event-5167721940___
Rpm-maint mailing list
I can reproduce the problem with fscrypt on my ext4 /home partition:
```
$ mount | grep "/boot"
/dev/sda1 on /boot type ext4 (rw,relatime,data=ordered)
```
Steps to reproduce:
[Step A]
Make sure fscrypt is installed and set up.
[Step B]
Create base test directory:
```
cd ~
mkdir test_rpm
cd
As I said, it might have something to do with the encrypted file systems I use
(luks and fscrypt). Maybe I can take the time this week to test this a bit more.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
> If you are lucky, observe error on some locations
It'd be helpful to mention some example(s) of such locations.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
My guess is that it is wrongly assumed that the size of a symbolic link equals
the length of the path that the symbolic link points to.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
I Initially submitted this bug at
[bugzilla.redhat.com](https://bugzilla.redhat.com/show_bug.cgi?id=1953372).
**Description of problem:**
On my Arch Linux (5.10.16-arch1-1) I cannot build a simple spec file (see
attachment at the bottom) depending the directory from which the package is
being
