On Monday, March 10, 2025 10:47:00 AM MST Soren Stoutner wrote:
> I am on to another problem with Redmine. The current build produces the
> following error during rake:
>
> Errno::EACCES: Permission denied @ rb_sysopen - /usr/share/redmine/public/
> assets/.manifest.json (Errno::EACCES)
>
> https://salsa.debian.org/ruby-team/redmine/-/jobs/7230217#L7507
>
> In previous versions of Redmine (5.x) there is no /usr/share/redmine/public/
> assets/.manifest.json file. In fact, in my production 5.1.3+ds-6 instance,
> there is no /usr/ share/redmine/public/assets/ directory and no
> .manifest.json file anywhere under /usr/ share/redmine.
>
> To get rid of a previous build error I had to manually add the
> /usr/share/redmine/public/ assets directory to redmine 6.0.3+ds-3.
>
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1099906
>
> It isn’t clear to me if the root cause of the problem is a change in the
> Redmine 5.x to Redmine 6.x transition, or a change in the recent update of
> Rake (or something else). I’m going to spend some time digging into this,
> but as I don’t know anything about .manifest.json files I thought I might ask
> here first to see if anyone knows anything about them off the top of their
> heads.
As a partial answer, I was able to bypass this error by creating an empty .manifest.json in postinst.
https://salsa.debian.org/ruby-team/redmine/-/blob/master/debian/redmine.postinst?ref_type=heads#L51-52
This seems a bit hacky, as I have no idea why an empty copy of this file is sufficient, but I don’t really know what is looking for this file and what it does with the information it finds there.
If shipping an empty .manifest.json is the correct solution, I would imagine it would make more sense to move its creation to debian/rules instead of handling it in postinst. Any feedback would be appreciated.
--
Soren Stoutner
soren@debian.org
Attachment:
signature.asc
Description: This is a digitally signed message part.