Arch Linux User Repository

AFAIK, Yaourt downloads the sources in a temporary directory, performs the build, installs the package and throws everything away. Next time you want to update your kernel, you'll have to download everything again. That's a waste of bandwidth and server load!

For zen0 i get ping error like many times before so i think server problems. I willl try to build Vbox on kernel without "CONFIG_LOCALVERSION_AUTO" And as you saying yaourt maybe not best idea for this package but if i not use it for updating it works just like makepkg and pacman -U so no reason not to use

The GIT server was overloaded again and eventually crashed. Devs are restarting it now..

First of all, according to your config, it appears that you are using 2.6.36-zen0. The current version is 2.6.36-zen2. I suppose the PKGBUILD did not update the tree? I'm not sure but it might be related to the fact that you use yaourt or that the server is overloaded again or that the server is getting more RAM right now (hopefully). Nevertheless, no matter how comfortable yaourt is, I can not recommend to use it with this package. The package is not and never will be intended to be used that way. Sorry for that. As for your VBox issue, I supposed that having "CONFIG_LOCALVERSION_AUTO" enabled was the reason for your problem. I've just tried it myself and my kernel release name now looks like "2.6.36-zen2-blubb-00229-g64a22e4". Running /etc/rc.d/vbox setup still works. I use virtualbox-ose though. I'm not sure what is wrong, sorry. :/

As for yaourt i will still use it because it's great for other aur pakckages ( or at least i did't find better one), and it can install this package so for now i stick with it. I'am using virtualbox_bin PKGBUILD from AUR for vbox and "/etc/rc.d/vboxdrv setup" script for installing modules As fior config here it is , but i can say that it's lightly modified original arch linux config so nothing special, didn't have time to create new one for this http://paste2.org/p/1121994

I really, really do not recommend to use yaourt for this package. As for your third point, it'd be great if you could upload your config so that I can check, what's wrong. VBox works perfectly fine over here.

First of all good work on this PKBUILD. Second when i installed it with yaourt i get that i installed kernel26-zen , but i don't get information that zen-kernel is installed so i will always need to remeber about this package and it don't update when i use yaourt --devel (like mplayer-svn aur package or deluge-svn ) which is great way to update development packages. Third when i try to compile vbox module i get Makefile:170: *** Error: /usr/src/linux (version 2.6.36-zen0-ARCH-20101112-stable) does not match the current kernel (version 2.6.36-zen0-ARCH-20101112-stable-00217-ga3dd510). Stop. cp: nie można wykonać stat na `/tmp/vboxdrv-Module.symvers': Nie ma takiego pliku ani katalogu Makefile:105: *** Error: /usr/src/linux (version 2.6.36-zen0-ARCH-20101112-stable) does not match the current kernel (version 2.6.36-zen0-ARCH-20101112-stable-00217-ga3dd510). Stop. cp: nie można wykonać stat na `/tmp/vboxdrv-Module.symvers': Nie ma takiego pliku ani katalogu Makefile:101: *** Error: /usr/src/linux (version 2.6.36-zen0-ARCH-20101112-stable) does not match the current kernel (version 2.6.36-zen0-ARCH-20101112-stable-00217-ga3dd510). Stop. so i think maybe you change something in naming to get it working ?

Looking at the kernel26-lts package, which can be found in the core repository, I noticed that the package and file names of my package were wrong, so I've renamed them. The PKGBUILD now also installs the System.map file which might be interesting for debugging purposes. See the ChangeLog for a complete list of changes.

Unfortunately it appears that the tree is currently broken and all developers are offline. I created the _no_update option for such cases so that the user has the abilitly to revert to a stable tree. As a temporary solution you can uncomment the _no_update option in the PKGBUILD. Then navigate to src/zen-sources/ and run "git checkout -b tmp master~1". When the issue is resolved, run "git checkout master; git branch -D tmp" and unset the _no_update option. I'm sorry for that, but as this is a live repository, things can and will(!) break from time to time.

Added a workaround so that the AUR shows the correct package description.