Arch Linux

reztho

Member

Registered: 2007-12-16

Posts: 44

[Solved] Request for checking a bug in libarchive/makepkg

Some days ago I uploaded a new package to AUR called dataplot. It compiles perfectly. It doesn't have any problem related to how the PKGBUILD is made.

But there is something strange. If you compile it and install the resulting package, check the group and user owners of the files/directories in /usr/share/dataplot. Here I have:  30123:19254, when it should be root:root.

I suspect the problem is with libarchive; maybe makepkg or pacman too, but I don't know.

I would like some of you try to compile it and see if this happens to you too, so I can open a bug in firespray knowing it isn't an isolated situation.

Last edited by reztho (2009-06-26 20:09:33)

arkham

Member

From: Stockholm

Registered: 2008-10-26

Posts: 516

Website

Re: [Solved] Request for checking a bug in libarchive/makepkg

That pkgbuild is such a mess..
Anyway, use chown -R root:root to set the correct ownership.

---

"I'm Winston Wolfe. I solve problems."

~ Need moar games? [arch-games] ~ [aurcheck] AUR haz updates? ~

reztho

Member

Registered: 2007-12-16

Posts: 44

Re: [Solved] Request for checking a bug in libarchive/makepkg

I've made a lot of packages and I've never had to set up user/groups owners.

Yes, that works, but there is no coherent reason for that behaviour. If you check your pkg directory you will see the owner/user of those files is the user you used for running makepkg, not those non-existant id's.

Last edited by reztho (2009-06-26 19:59:47)

reztho

Member

Registered: 2007-12-16

Posts: 44

Re: [Solved] Request for checking a bug in libarchive/makepkg

Epic fail ... The source code is compressed with those id's. Those non-existant user/group id's will be obtained inside the fakeroot. Solved.

Last edited by reztho (2009-06-26 20:12:38)

Allan

Pacman

From: Brisbane, AU

Registered: 2007-06-09

Posts: 11,413

Website

Re: [Solved] Request for checking a bug in libarchive/makepkg

I guess you are using "cp" rather than "install"...

---

PGP Key: F99FFE0FEAE999BD

reztho

Member

Registered: 2007-12-16

Posts: 44

Re: [Solved] Request for checking a bug in libarchive/makepkg

Just plain bsdtar which is the same as cp, of course. That's the reason.

But I've never used install for setting the user/group owner and I'm sure most of the PKGBUILDs doesn't use it for that too. It's just the first source code I see which isn't compressed with the 0:0 id's (root:root) and that's why I was confused at first.

Edit: My fault again... "install" will use the user/group owner of the current process ("root" inside the fakeroot) so actually there is no need to point them out explicitly. I learnt a lot today.

Last edited by reztho (2009-06-27 15:57:52)