Active Topics

 



Notices


Reply
Thread Tools
Raimu's Avatar
Posts: 139 | Thanked: 181 times | Joined on Nov 2011 @ Oulu, Finland
#561
Yeah, looks like the package got stuck after build.
 

The Following User Says Thank You to Raimu For This Useful Post:
Saturn's Avatar
Posts: 1,648 | Thanked: 2,122 times | Joined on Mar 2007 @ UNKLE's Never Never Land
#562
Originally Posted by Raimu View Post
Yeah, looks like the package got stuck after build.
Yes, the build was correct but it never got to the repo:
https://garage.maemo.org/builder/fre.../cleven_2.5-1/

There is not much I can do in such situation. Sorry.
 

The Following 6 Users Say Thank You to Saturn For This Useful Post:
Posts: 1,397 | Thanked: 2,126 times | Joined on Nov 2009 @ Dublin, Ireland
#563
 

The Following 2 Users Say Thank You to ivgalvez For This Useful Post:
Saturn's Avatar
Posts: 1,648 | Thanked: 2,122 times | Joined on Mar 2007 @ UNKLE's Never Never Land
#564
OK, increased the build number and resent to the autobuilder.

The result was even worse this time and might help better understand the issue:
https://garage.maemo.org/builder/fre.../cleven_2.5-2/
 
Posts: 3,074 | Thanked: 12,960 times | Joined on Mar 2010 @ Sofia,Bulgaria
#565
@Saturn:
Please find here the drivers in question, NFC if that will appear in package interface, anyway, .deb should be enough for you to test/tweak/whatever.

EDIT:
package is in extras-devel http://maemo.org/packages/package_in...28.10-power50/

Last edited by freemangordon; 2012-04-17 at 19:43.
 

The Following 3 Users Say Thank You to freemangordon For This Useful Post:
Raimu's Avatar
Posts: 139 | Thanked: 181 times | Joined on Nov 2011 @ Oulu, Finland
#566
Well, that's one error message a little opaque to interpret. In the meantime I'll just help myself to the .deb file from here: https://garage.maemo.org/builder/fre...2.5-1/results/
 

The Following User Says Thank You to Raimu For This Useful Post:
Posts: 3,074 | Thanked: 12,960 times | Joined on Mar 2010 @ Sofia,Bulgaria
#567
Originally Posted by Saturn View Post
OK, increased the build number and resent to the autobuilder.

The result was even worse this time and might help better understand the issue:
https://garage.maemo.org/builder/fre.../cleven_2.5-2/
You can try to re-upload the same version again, most-probably it will work this time
 

The Following 3 Users Say Thank You to freemangordon For This Useful Post:
Saturn's Avatar
Posts: 1,648 | Thanked: 2,122 times | Joined on Mar 2007 @ UNKLE's Never Never Land
#568
Originally Posted by freemangordon View Post
You can try to re-upload the same version again, most-probably it will work this time
Done and you are right it worked..
 

The Following 3 Users Say Thank You to Saturn For This Useful Post:
Saturn's Avatar
Posts: 1,648 | Thanked: 2,122 times | Joined on Mar 2007 @ UNKLE's Never Never Land
#569
Originally Posted by freemangordon View Post
@Saturn:
Please find here the drivers in question, NFC if that will appear in package interface, anyway, .deb should be enough for you to test/tweak/whatever.

EDIT:
package is in extras-devel http://maemo.org/packages/package_in...28.10-power50/
I have some questions on how to depend on it properly. if you prefer we can start a new thread dedicated to those wireless modules.

Since this package depends on KP50 if I add it on cleven's dependencies it will pull also the KP50 stuff on a cleven update/installation.

Do you want me to have a cleven version for each new KP or you have a better idea?

Thanks already.

Last edited by Saturn; 2012-04-17 at 20:33.
 

The Following User Says Thank You to Saturn For This Useful Post:
Posts: 3,074 | Thanked: 12,960 times | Joined on Mar 2010 @ Sofia,Bulgaria
#570
No need for a new thread.

Well, indeed, depending on that package will pull KP50 too, but you can make another(dummy) package too and depend on either dummy package or this one. And there is no need cleven to depend on the exact version of the package(use ">=" in debian/control), that way when a new KP enters repos some day, I will build a new version of linux-backports-modules-power and it should be automatically pulled on kernel upgrade. Or if you have a better solution I am OK with it.

Or you can pull that one and rebuild it against stock kernel (just a few modifications are needed) if bleeding-edge drivers work on stock kernel. I can do it too of course (but not today ).

Actually I am not .deb packaging guru, so any piece of advice is welcome
 

The Following 5 Users Say Thank You to freemangordon For This Useful Post:
Reply

Tags
aircrack, cleven, reaver


 
Forum Jump


All times are GMT. The time now is 12:01.