Page 1 of 1

Faulty packages

Posted: 23 Jan 2016, 21:44
by mick1945g
Just recently I have encountered problems with downloaded packages.
Warzone2100 has missing dependency in missing library physfs.so.1 and package search does not find any

VirtualBox builder end up in nonfunctional module with following error in log file:
vboxdrv: unknown symbol contig_page_data (err 0) also activating module produce following:
modprobe: ERROR: could not insert 'vboxdrv': Unknown symbol in module, or unknown parameter (see dmesg)
modprobe: ERROR: could not insert 'vboxnetadp': Unknown symbol in module, or unknown parameter (see dmesg)
modprobe: ERROR: could not insert 'vboxnetflt': Unknown symbol in module, or unknown parameter (see dmesg)
/opt/porteus-scripts/xorg/aufs-remove: line 61: [: /dev/loop15: unary operator expected

and module does not load.

Some package maintainers seems slacky.

Re: Faulty packages

Posted: 23 Jan 2016, 23:12
by francois
VirtualBox builder behaves this way once and a while. This seems to be an upstream problem related to new issues of vbox. Usually, if you wait a few days you should be able to build it.

Re: Faulty packages

Posted: 27 Jan 2016, 06:19
by mick1945g
Actualy problem is also on Your side. gtk-easy-build from ponce.cc installs kernel modules into /lib/modules/3.17.4-porteus/misc instead in .../kernel/misc

Re: Faulty packages

Posted: 28 Jan 2016, 00:57
by brokenman
Line 276 of gtk-easy-build

Code: Select all

cp -a --parents -R /lib/modules/`uname -r`/misc/{vboxdrv.ko,vboxnetadp.ko,vboxnetflt.ko,vboxpci.ko} $BUILD/
It does indeed install these kernel modules to misc which is where they belong. To verify, download the run file from virtualbox and install it manually, then check this path. It may be that virtualbox has changed something that broke gtk-easy-build and I will investigate it soon. For now you can download the run file and isntall it manually which takes less time than building a module.