mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #1746] Building rpm - what's going wrong? #1183
Labels
No labels
LTS merge
LTS merge
bug
bug
converted-to-discussion
doc-todo
documentation
duplicate
enhancement
file-transfer
firecfg
firejail-in-firejail
firetools
graphics
help wanted
information_old
installation
invalid
modif
moved
needinfo
networking
notabug
notourbug
old-version
overlayfs
packaging
profile-request
pull-request
question
question_old
removal
runtime-permissions
sandbox-ipc
security
stale
wiki
wiki
wontfix
wordpress
workaround
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/firejail#1183
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Fred-Barclay on GitHub (Jan 21, 2018).
Original GitHub issue: https://github.com/netblue30/firejail/issues/1746
I'm trying to figure out why
make rpmsalways fails, and I've hit a bit of a roadblock (granted, my lack of knowlege about rpms isn't contributing to my efforts 😁 ).Currently building goes something like this:
The /tmp/tmp.SOMEVALUE/SRPMS and RPMS directories are being created, but no rpm is being build in them.
I've traced the errors back to
e470524, at which point the faulty builds begin. This commit removed the man pagefirejail-configfrom the repo. Generally speaking, building rpms was successful for all earlier commits.platform/rpm/mkrpm.sh hasn't been edited since before this point, so I believe the problem is not in the rpm portion of the build process. @netblue30 how do you build the .rpms for release on sourceforge?
Full output of build for current state is https://gitlab.com/snippets/1694579
Full output of build for the commit for which the build began failing is https://gitlab.com/snippets/1694580
Full output of the last commit with a good build is https://gitlab.com/snippets/1694581
See also #1583
Cheers!
Fred
@netblue30 commented on GitHub (Jan 23, 2018):
To answer a question from an older thread, I build the official rpm packages on a CentOS 7. First I remove /etc/firejail directory (sudo rm -fr /etc/firejail), I install firejail (sudo make install-strip), then I create the rpm by running platform/rpm/old-mkrpm.sh script. The package is placed by the script in user home directory.
I couldn't get platform/rpm/mkrpm.sh running. It works on some Fedora versions, for me on CentOS it doesn't. The regular ./configure && make && sudo make install works fine on CentOS 6 and 7 and any Fedora.
@reinerh commented on GitHub (Jan 23, 2018):
@Fred-Barclay the firejail-config.5.gz error should have been fixed by
b66676c.I think the other error you are seeing now is another regression that was introduced.
It sounds like it is installing some files (during "make install") that are not added to the packaging, so it aborts the build.
But I'm not an rpm expert, so I'm not really sure...
@reinerh commented on GitHub (Jan 23, 2018):
In the .spec file there is indeed nothing in the %files section that matches those files...
@reinerh commented on GitHub (Jan 23, 2018):
@Fred-Barclay Can you please check if
59fb1d9fimproves something?@SkewedZeppelin commented on GitHub (Jan 23, 2018):
@reinerh here are some results on Fedora 27
^outputs an RPM, not sure what is in it
^fails and doesn't create RPM
@reinerh commented on GitHub (Jan 23, 2018):
@SpotComms thanks for testing. What errors are now still remaining? Can you please post them?
@Fred-Barclay commented on GitHub (Jan 23, 2018):
@reinerh On Fedora 26 (Korora 26 specifically),
./configure --prefix=/usr && make rpms && sudo yum install firejail-0.9.53-1.x86_64.rpmworks perfectly!@SkewedZeppelin commented on GitHub (Jan 23, 2018):
@Fred-Barclay I don't think that RPM is the full thing/proper though. As
./configure && make rpmscompletes much quicker thanmake(actually compiling all the programs). I wonder if it is just including the existing /usr/bin/firejail, etc. in it. The profiles in it however do seem update to date.Edit: I extracted the RPM and hashed some of the files and they are indeed different from the existing install (0.9.52 from Sourceforge/netblue)
@Fred-Barclay commented on GitHub (Jan 23, 2018):
Do you mean from a previous installation of firejail? If so, that's not the case here - it's a brand-new Korora install.
@SkewedZeppelin commented on GitHub (Jan 23, 2018):
Okay I think it is indeed fixed 🎉 , thanks @reinerh.
@Fred-Barclay make rpms wasn't actually outputting any gcc output, so I wasn't sure if it was actually being compiled. But I just compared and
make rpmsdoes take a few seconds longer thanmake, implying that it is actually compiling everything.I guess we can close this now.
@Fred-Barclay commented on GitHub (Jan 23, 2018):
I believe that's because of the
--quietflag in https://github.com/netblue30/firejail/blob/master/platform/rpm/mkrpm.sh#L39. If you remove it you should see everything compiling.Thanks @reinerh ! 🎉