[arch-multilib] Permission to move package into multilib

Brad Fanella bradfanella at archlinux.us
Tue Oct 5 20:02:14 EDT 2010


On Tue, Oct 5, 2010 at 4:43 PM, Ionuț Bîru <ibiru at archlinux.org> wrote:
> On 10/06/2010 12:38 AM, Brad Fanella wrote:
>>
>> On Mon, Sep 27, 2010 at 11:04 PM, Brad Fanella<bradfanella at archlinux.us>
>>  wrote:
>>>
>>> On Sun, Sep 26, 2010 at 6:39 PM, Jan Steffens<jan.steffens at gmail.com>
>>>  wrote:
>>>>
>>>> On Mon, Sep 27, 2010 at 1:00 AM, Brad Fanella<bradfanella at archlinux.us>
>>>>  wrote:
>>>>>
>>>>> What is the status of this? Do I have permission to move it to
>>>>> multilib?
>>>>> _______________________________________________
>>>>> arch-multilib mailing list
>>>>> arch-multilib at archlinux.org
>>>>> http://mailman.archlinux.org/mailman/listinfo/arch-multilib
>>>>>
>>>>
>>>> Well, I'd say "yes". The i686 version is already in [community] and it
>>>> adds no dependencies to [multilib].
>>>> _______________________________________________
>>>> arch-multilib mailing list
>>>> arch-multilib at archlinux.org
>>>> http://mailman.archlinux.org/mailman/listinfo/arch-multilib
>>>>
>>>
>>> Sorry, my bad. I forgot to mention that that was more of a two part
>>> question:
>>> 1) May I move it?
>>> 2) If so, may my user have access to multilib so I may do so?
>>>
>>> Thanks,
>>> Brad
>>>
>>
>> I hate to sound rude or pushy, but this bug has been open since
>> September 18th and it could have been fixed in a matter of hours. If
>> someone wants to build it themself, then I have absolutely no problem
>> with that. I just need user permissions for [multilib] if I am going
>> to have to submit it.
>>
>
> i still not see an up to date PKGBUILD committed in community.
>
> http://repos.archlinux.org/wsvn/community/chuck/trunk/PKGBUILD
>
> i said from the beginning that i dislike the idea of bin32-chuck
>
> --
> Ionuț
> _______________________________________________
> arch-multilib mailing list
> arch-multilib at archlinux.org
> http://mailman.archlinux.org/mailman/listinfo/arch-multilib
>

Up-to-date? What part of it is not up-to-date?

I thought we had come to the consensus that it should be created. I
cannot add x86_64 support for it in [community] as the chuck team has
temporarily dropped native 64-bit support for it.

Not that it matters much to me personally. I just want to get all of
this chuck business straightened out.

Thanks,
Brad


More information about the arch-multilib mailing list