https://bugzilla.redhat.com/show_bug.cgi?id=827167
Gary Gatling <gsgatlin(a)ncsu.edu> changed:
What |Removed |Added
----------------------------------------------------------------------------
Blocks|177841 (FE-NEEDSPONSOR) |
--- Comment #16 from Gary Gatling <gsgatlin(a)ncsu.edu> ---
Greetings, Attempt #3 at a package.
http://install.linux.ncsu.edu/pub/yum/itecs/public/bumblebee/fedora17/spe...
http://install.linux.ncsu.edu/pub/yum/itecs/public/bumblebee/fedora17/SRP...
I got rid of conditional build stuff since the stack smashing is a real bug.
Instead there is a patch now for that.
I still get warnings with rpmlint but I think they are ok to ignore?
bumblebee.x86_64: W: only-non-binary-in-usr-lib
I think this is ok becuase of
https://bugzilla.redhat.com/show_bug.cgi?id=794777
If this is in fact a problem, does anyone know of a workaround for a unit-file?
bumblebee.x86_64: W: no-manual-page-for-binary bumblebee-bugreport
Yeah, they didn't provide a man page for this binary upstream.
bumblebee.x86_64: W: dangerous-command-in-%trigger ln
bumblebee.x86_64: W: dangerous-command-in-%trigger ln
My understanding is that this is the proper way to do what I'm trying to do...
I need to change where a symlink points, but only if another package:
bumblebee-nvidia is installed. So thats why I used triggers. If there is a
better way to do this does anyone know what it is?
1 packages and 0 specfiles checked; 0 errors, 4 warnings.
Kind of stuck on things with VirtualGL but I did want to fix the problems this
bumblebee package has. Further suggestions welcome.
--
You are receiving this mail because:
You are on the CC list for the bug.