Package Base Details: oss-nonfree

Git Clone URL: (read-only)
Keywords: oss
Submitter: alexdw
Maintainer: alexdw
Last Packager: alexdw
Votes: 14
Popularity: 0.055015
First Submitted: 2013-06-23 13:17
Last Updated: 2017-05-06 14:01

Latest Comments

alexdw commented on 2017-02-13 23:49

Updated (4.2_2017-1) for new release - OSS v4.2 Build 2017:

Now working again with Arch kernel 4.8.

alexdw commented on 2016-12-21 23:54

Note: This does not work with Arch kernel 4.8 with default configuration due to new CONFIG_HARDENED_USERCOPY feature being enabled. Workaround would be to compile a custom kernel with CONFIG_HARDENED_USERCOPY disabled or alternately use oss or oss-git, which include a patch to avoid this issue (a similar patch does not appear to be possible for oss-nonfree as that code seems to be precompiled).

alexdw commented on 2016-06-14 23:34

Updated (4.2_2011-3) with a patch to allow compilation with 4.6 kernels.

alexdw commented on 2015-05-27 21:48

OSS appears to be broken again in latest (4.0.4) kernel. If I have time over the weekend I'll try to work out a patch for it.

alexdw commented on 2015-05-07 20:44

Updated (4.2_2011-2) with patch by "oss117" from OSS forums:
This should fix the compile error for 4.x kernels (tested as working for 4.0.1).

alexdw commented on 2015-03-01 23:35

Updated (4.2_2011-1) for build 2011.

bernd_b commented on 2014-11-23 15:41

When click to "Download tarball" I get the following link:

Shouldn't there be something like "libflashsupport-.." behind it?

alexdw commented on 2014-10-05 23:20

I think the libflashsupport-oss issue should be fixed - all three (oss-nonfree, oss, oss-git) now have their own respective libflashsupport packages.

I wasn't able to solve the permissions warnings though - seems to be for oss-nonfree only so I'm guessing something to do with the way the source file archive? As mentioned before it seems to work fine for me despite the warnings.

alexdw commented on 2014-09-09 05:30

@nuc: Thanks for checking and posting back. Yes I noticed it was a bit odd now that AUR does not allow all 3 of the base packages to have a "libflashsupport-oss".

The reason why I left it as "libflashsupport-oss" in optdepends is I thought this would allow any of the 3 "libflashsupport-oss" to work, though thinking again you probably always want the one associated with the base package so I'll have a look at changing it in the way you suggest.

I'm not sure about what is causing those warnings (I get them too but osstest seems to work), whether it's a new feature in AUR/makepkg or a change in file permissions in the OSS source archive. Nor do I know how to resolve them - do I need to change the directory permissions in the package somehow? I'll have a look at this while checking out the "libflashsupport-oss" issue.

Again I'm travelling for work so it will be Friday before I can make any of these fixes.

nuc commented on 2014-09-08 23:50

Hi, thanks for the update. Some issues though:
libflashsupport-oss is in optdepends but it should be libflashsupport-oss-nonfree.

Also I needed to manually remove libflashsupport-oss first because it obviously pulls in oss, which in turn conflicts to oss-nonfree. So maybe oss-nonfree should also conflict to libflashsupport-oss (and oss to libflashsupport-oss-nonfree)?
Kind of a mess :/

Also I got those warnings after updating:
Warning: directory permissions differ for / usr / lib / oss / build /
Filesystem: 755 package: 2755
Warning: directory permissions differ for / usr / lib / oss / lib /
Filesystem: 755 package: 2755
Warning: directory permissions differ for / usr / lib / oss / etc /
Filesystem: 755 package: 2755
Warning: directory permissions differ for / usr / lib / oss / scripts /
Filesystem: 755 package: 2755
Warning: directory permissions differ for / usr / lib / oss / cuckoo /
Filesystem: 755 package: 2755

It *think* it installed properly though.

All comments