Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#53466 - [primus] 20151110-7 incorrect sed syntax breaks primusrun

Attached to Project: Community Packages
Opened by Jeb Rosen (jebrosen) - Sunday, 26 March 2017, 19:59 GMT
Last edited by Jan Alexander Steffens (heftig) - Monday, 27 March 2017, 17:51 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Jan Alexander Steffens (heftig)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

Line 33 of the PKGBUILD: "sed -e '/^PRIMUS_libGL=/cPRIMUS_libGL=/usr/\\$LIB/primus' \" is incorrect.
The \\ sequence is in single quotes, so it is passed to sed as \\$, creating the line:

PRIMUS_libGL=/usr/\$LIB/primus

The correct line does not have a \ in it. An example corrected line 33 is as follows:
sed -e '/^PRIMUS_libGL=/cPRIMUS_libGL=/usr/\$LIB/primus' \
This task depends upon

Closed by  Jan Alexander Steffens (heftig)
Monday, 27 March 2017, 17:51 GMT
Reason for closing:  Works for me
Additional comments about closing:  Reopen if more details are available
Comment by Sven-Hendrik Haase (Svenstaro) - Monday, 27 March 2017, 12:23 GMT
Jan, I think this was introduced by you. Could you take a look?
Comment by Jan Alexander Steffens (heftig) - Monday, 27 March 2017, 16:56 GMT
I do very much expect the backslash to be there. Why do you think it's broken?
Comment by Jeb Rosen (jebrosen) - Monday, 27 March 2017, 17:36 GMT
I misunderstood something; this fix is actually incorrect. Removing the \, as someone suggested in IRC, actually ends up running the program on integrated graphics and not through primus. According to one user, it did prevent error messages and appeared to "fix" their issues, which is why I reported it. Reading the logs again, I suspect they did not have certain package versions installed that they claimed they had, or there were other scripts or configs interfering.

Loading...