Actually I should be a bit more precise. Ownership of file was changed without
any issues.
Ownership of folders was not. So the files are replaced but the folders are not,
and that means if you change the ownership of the folders between revisions
of the same ebuild (or next version of the
Are you installing/building with the ebuild command and then merging
with sudo or
something similar?
That may be one reason something like this is happening.
On 2/8/21 5:28 PM, François Bissey wrote:
Hi all,
I discovered an issue in a couple of packages for which sage-on-gentoo
provides
It looks like “--no-same-owner” does work in the end.
However, I bumped into a probably subtle bug in portage.
Before the permission were right I had to un-merge the
package (emerge -C …) first, then merge it again.
It looks like the ownership is not changed if there are files
from a previous
Just for the record so that some root cause of the issue are more clear.
From “man tar”
--no-same-owner
Extract files as yourself (default for ordinary users).
--same-owner
Try extracting files with the same ownership as exists in the
archive (default
Nope, just plain emerge as root.
> On 9/02/2021, at 11:55, Aisha Tammy wrote:
>
> Are you installing/building with the ebuild command and then merging with
> sudo or
> something similar?
> That may be one reason something like this is happening.
>
> On 2/8/21 5:28 PM, François Bissey wrote:
Hi all,
I discovered an issue in a couple of packages for which sage-on-gentoo
provides ebuilds.
Some packages install data directly from a tar command. By that I mean
Makefile.am will a line like
cd $(DESTDIR)$(dbdir) && tar xf $(dist_db_DATA) && rm $(dist_db_DATA)
From a real Makefile at
