Hi,

I posted this twice earlier, but it did not show up because the error message 
it moving it a tad more than 60KB which makes it require moderator approval 
(which may well be delayed because of the holiday weekend in the US). So, here 
is a repost. Hopefully, someone can get to it before the 24-hour clock on the 
fpaste runs out (I do not see how to increase that time.)


I am the package maintainer of SLiM, the Simple Login Manager. While trying to 
take care of an automated BZ request, I decided to look into also updating the 
package.

Because upstream is not very responsive, as the author is sadly indisposed for 
the long-term, I moved the code to github at 
https://github.com/maitra/slim-fork  after having  made some of the corrections 
(suggested earlier here) which make the package compile without error. And also 
bumped up the cmakeminimum which is what triggered the BZ request.

However, when I go to build the RPM with the spec file, I get an error.

THe spec file is here: https://paste.centos.org/view/96e6b7db

However, I get an error which does not show up when I do the compilation 
outside the spec file, which is really perplexing to me so my guess is that the 
problem is with the spec file, and I wonder if anyone more knowledgable on SPEC 
files can give me some suggestions.

Here are the errors I get when I run rpmbuild -bb slim.spec.

https://paste.centos.org/view/8f71e2c5

I do not understand why these errors do not show up when I compile the package 
(outside of the SPEC file).

Many thanks again for any help, and best wishes,
Ranjan
-- 
_______________________________________________
users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/[email protected]
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Reply via email to