Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 928635 - net-mail/courier-imap-5.2.6-r1 fails with cannot find ${D}${ROOT}/usr/lib64/courier-imap when running fperms in postinst
Summary: net-mail/courier-imap-5.2.6-r1 fails with cannot find ${D}${ROOT}/usr/lib64/c...
Status: UNCONFIRMED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Tupone Alfredo
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-04-05 12:48 UTC by Dirk Tilger
Modified: 2024-04-06 07:26 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
Patch against the ebuild to make it work properly when ROOT is set (0001-net-mail-courier-imap-portage-takes-care-of-ROOT.patch,913 bytes, patch)
2024-04-05 12:48 UTC, Dirk Tilger
Details | Diff
build.log without the patch (courier-imap-5.2.6-r1.build.log.xz,15.00 KB, application/x-xz)
2024-04-06 07:09 UTC, Dirk Tilger
Details
Use chmod instead of fperms (0001-net-mail-courier-imap-portage-takes-care-of-ROOT.patch,919 bytes, patch)
2024-04-06 07:26 UTC, Dirk Tilger
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Dirk Tilger 2024-04-05 12:48:32 UTC
Created attachment 889518 [details, diff]
Patch against the ebuild to make it work properly when ROOT is set

net-mail/courier-imap-5.2.6-r1 fails to find ${D}${ROOT}/usr/lib64/courier-imap when running fperms in postinst, however ${ROOT} is handled by portage and the ebuild in this case doesn't have to treat it specially.

I forgot to keep the build.log. If you need it let me know.
Comment 1 Mike Gilbert gentoo-dev 2024-04-05 14:15:11 UTC
Comment on attachment 889518 [details, diff]
Patch against the ebuild to make it work properly when ROOT is set

fperms always operates on ${D}, so your patch is not valid.

The fperms call should be replaced with chmod.
Comment 2 Dirk Tilger 2024-04-06 07:09:19 UTC
Created attachment 889555 [details]
build.log without the patch
Comment 3 Dirk Tilger 2024-04-06 07:10:46 UTC
(In reply to Mike Gilbert from comment #1)
> fperms always operates on ${D}, so your patch is not valid.

${D} isn't the problem. ${ROOT} is. I've attached the build.log so you can see the problem yourself.
Comment 4 Dirk Tilger 2024-04-06 07:26:27 UTC
Created attachment 889556 [details, diff]
Use chmod instead of fperms

Now I got it. There were two problems in the ebuild and I fixed the wrong one.