Hi DEVs/TUs, I don't using virtualbox since months and now who my desktop is dead I can't build it on my laptop @1.7Ghz. It spend more time. Then I want to know if someone of you want to adopt virtualbox packages.
It is out-of-date but I've all pkgbuilds ready to work.
packages are: virtualbox-additions virtualbox-modules virtualbox-ose virtualbox-ose-additions virtualbox-ose-additions-modules dev86 iasl xalan-c xerces-c
Thanks, best regards
Hi Andrea, I'm not sure if i can take this package for me or not. I'm a new arch user. Not a dev, not even TU. That's my doubt. Can i try to assume this package or not? I'm not sure about the rules here. Hugo Doria, told me that i could participate on this list. It's a public list, ok. But on your message, you said "Hi DEVs/TUs", and that's why i became confused.
Blessed be
2008/9/15 Andrea Scarpino bash.lnx@gmail.com
Hi DEVs/TUs, I don't using virtualbox since months and now who my desktop is dead I can't build it on my laptop @1.7Ghz. It spend more time. Then I want to know if someone of you want to adopt virtualbox packages.
It is out-of-date but I've all pkgbuilds ready to work.
packages are: virtualbox-additions virtualbox-modules virtualbox-ose virtualbox-ose-additions virtualbox-ose-additions-modules dev86 iasl xalan-c xerces-c
Thanks, best regards
-- Andrea `BaSh` Scarpino Arch Linux Trusted User Linux User: #430842
On Tue, Sep 16, 2008 at 8:24 AM, Marcelo Cavalcante kalibslack@gmail.com wrote:
Hi Andrea, I'm not sure if i can take this package for me or not. I'm a new arch user. Not a dev, not even TU. That's my doubt. Can i try to assume this package or not? I'm not sure about the rules here. Hugo Doria, told me that i could participate on this list. It's a public list, ok. But on your message, you said "Hi DEVs/TUs", and that's why i became confused.
This list is opened for everyone. But you need to be TU to maintain a package in [community]. You can adopt packages from unsupported though. If noone adopts these VirtualBox packages they will be, probably, dropped to AUR. Feel free to adopt it in this case.
BTW, Adopt some packages in AUR, make a good work and apply to be a TU too. Lets raise the number of brazilians here. We shall take over the [community] world. MUUUUUU-ha-ha-ha.
-- Hugo
2008/9/16 Marcelo Cavalcante kalibslack@gmail.com:
Hi Andrea, I'm not sure if i can take this package for me or not. I'm a new arch user. Not a dev, not even TU. That's my doubt. Can i try to assume this package or not? I'm not sure about the rules here. Hugo Doria, told me that i could participate on this list. It's a public list, ok. But on your message, you said "Hi DEVs/TUs", and that's why i became confused.
Hi Marcelo, if you aren't DEV or TU you cannot adopt packages who are in [community] repository.
Btw, gcarrier has adopted VirtualBox and related packages. Thanks for your help.
Got it... Thanks anyway Andrea.
I'll follow Hugo's hint.
Take Care
2008/9/16 Andrea Scarpino bash.lnx@gmail.com
2008/9/16 Marcelo Cavalcante kalibslack@gmail.com:
Hi Andrea, I'm not sure if i can take this package for me or not. I'm a new arch
user.
Not a dev, not even TU. That's my doubt. Can i try to assume this package
or
not? I'm not sure about the rules here. Hugo Doria, told me that i could participate on this list. It's a public list, ok. But on your message,
you
said "Hi DEVs/TUs", and that's why i became confused.
Hi Marcelo, if you aren't DEV or TU you cannot adopt packages who are in [community] repository.
Btw, gcarrier has adopted VirtualBox and related packages. Thanks for your help.
-- Andrea `BaSh` Scarpino Arch Linux Trusted User Linux User: #430842
On Tue, Sep 16, 2008 at 2:33 PM, Andrea Scarpino bash.lnx@gmail.com wrote:
Hi Marcelo, if you aren't DEV or TU you cannot adopt packages who are in [community] repository.
Btw, gcarrier has adopted VirtualBox and related packages. Thanks for your help.
-- Andrea `BaSh` Scarpino Arch Linux Trusted User Linux User: #430842
Go gcarrier!
On Tue, Sep 16, 2008 at 17:29, Anders Bergh anders1@gmail.com wrote:
Go gcarrier!
Going to 2.0 right now :)
On Thu, Sep 18, 2008 at 01:44, Geoffroy Carrier geoffroy.carrier@koon.fr wrote:
On Tue, Sep 16, 2008 at 17:29, Anders Bergh anders1@gmail.com wrote:
Go gcarrier!
Going to 2.0 right now :)
I will keep it i686 for now. I updated arch=() to reflect that. I will still be an improvement over current situation, but I'm ready to do whatever needed by people getting involved in a x86_64 "port" and with my vmware-server issues, I'd love to support it.
On Wed, Sep 17, 2008 at 9:30 PM, Geoffroy Carrier geoffroy.carrier@koon.fr wrote:
On Thu, Sep 18, 2008 at 01:44, Geoffroy Carrier geoffroy.carrier@koon.fr wrote:
On Tue, Sep 16, 2008 at 17:29, Anders Bergh anders1@gmail.com wrote:
Go gcarrier!
Going to 2.0 right now :)
I will keep it i686 for now. I updated arch=() to reflect that. I will still be an improvement over current situation, but I'm ready to do whatever needed by people getting involved in a x86_64 "port" and with my vmware-server issues, I'd love to support it.
Do you need help with x86-64 testing?
There are a couple of issues with the current pkgbuild, in case you dont have the notify flag, you should check the messages there.
Regards,
On Fri, Sep 19, 2008 at 16:09, Leonardo Andrés Gallego leonardo@archlinux-es.org wrote:
Do you need help with x86-64 testing?
There are a couple of issues with the current pkgbuild, in case you dont have the notify flag, you should check the messages there.
It seems to need more than testing: it appears to require a looot of 32 bits libraries. But I might be wrong, or this could have changed. Feel free to run tests anyway!
Packaging 32 bits libs for 64 bits systems fails my vision of what arch linux should stay. But that's not a definitive choice, if general opinion goes for it I'm ready to help :)
aur-general@lists.archlinux.org