On Ter, 2012-07-17 at 20:31 +0200, Nicolas Chauvet wrote:
> +* Tue Jul 17 2012 Nicolas Chauvet <kwizart(a)gmail.com> - 10:17-8
> +- rebuild for kernel kernel-3.4.5-2.fc17
Hi, as a better solution , Could we push VirtualBox-4.1.18-1 and
VirtualBox-kmod-4.1.18-1 to stable, before start building all new
To have akmod-VirtualBox-4.1.18-1.fc17.x86_64 in stable .
Sérgio M. B.
I just check and
repoquery --releasever=15 \* | grep -i mame
repoquery --releasever=15 -ql sdlmame-data-roms-0:0120-3.fc11.noarch
yum provides */robby.zip
No Matches found
Have this rom is good, for everyone test quickly the frontends.
So if no reason to not have it, I'd like have it again :)
Sérgio M. B.
I've been looking at what it will take to get the USBIP kernel modules
into kmod-staging, and it's just a added line. However, the official
source of the USBIP userspace is also in linux-staging.
To me, it seems like it would make more sense to split the userspace
into a separate package as it doesn't need to track the kernel module,
and it sure doesn't make sense to update it every time we push a new
SUSE has just grabbed the source for the userspace from kernel git (see
https://build.opensuse.org/package/view_file?file=usbip.spec&package=usbi..., line 36), and I'm tempted to follow their example.
Does anyone have an opinion one way or another? If not, I'll open a bug
report asking kmod-staging to build the kernel modules and a review
request for the userspace.