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
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:
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:
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
Reference Issues
#1682
What does this fix?
The man page of `stat()` mentions that for symbolic links the length of the
pointed-to path is stored in `stat.st_size`. However, as reported
[here](https://github.com/rpm-software-management/rpm/issues/1682) and
Thank you for the responses! I understand the problem(s) of this pull request.
I have two questions:
1. Why is the archive size calculated in advance in the first place? Is this
some kind of sanity check or is it required somewhere?
2. Would it be possible, in case the size check fails, to give
