[arch-dev-public] Moving DB scripts live

Eric Bélanger snowmaniscool at gmail.com
Thu Sep 3 20:37:00 EDT 2009


On Mon, Aug 3, 2009 at 10:30 PM, Aaron Griffin<aaronmgriffin at gmail.com> wrote:
> On Mon, Aug 3, 2009 at 4:38 PM, Eric Bélanger<snowmaniscool at gmail.com> wrote:
>> On Mon, Aug 3, 2009 at 7:05 PM, Aaron Griffin<aaronmgriffin at gmail.com> wrote:
>>> On Mon, Aug 3, 2009 at 6:03 PM, Eric Bélanger<snowmaniscool at gmail.com> wrote:
>>>> On Thu, Jul 30, 2009 at 1:16 PM, Aaron Griffin<aaronmgriffin at gmail.com> wrote:
>>>>> On Thu, Jul 30, 2009 at 12:04 PM, Allan McRae<allan at archlinux.org> wrote:
>>>>>> Aaron Griffin wrote:
>>>>>>>
>>>>>>> So, we have "any" support and split package support sitting in the DB
>>>>>>> scripts in /arch-new
>>>>>>>
>>>>>>> I'd like to move this live soon. What do you all think? Can you test
>>>>>>> normal packaging with these to confirm there's no major regressions?
>>>>>>>
>>>>>>
>>>>>> I just used these to upload abs to [testing] then move it to [extra] and
>>>>>> everything went fine.  One think that may be an issue, /arch-new/db-testing
>>>>>> uploaded both i686 and x86_64 (which I guess is needed to handle the "any"
>>>>>> arch), but /arch-new/testing2x had to be ran for i686 and x86_64.  Does that
>>>>>> handle "any" packages?  It is 3am here so I have not checked myself...
>>>>>
>>>>> Was just talking to Thomas about this - I don't think testing2x was
>>>>> changed to work this way.
>>>>
>>>> I guess that it's not fixed yet.  There seem to be 'any' support in
>>>> db-move however. Is that completed? Can I use it to move an 'any'
>>>> package from testing to extra?
>>>
>>> Yep, it should work fine.
>>>
>>
>> It seem to have worked fine.  BTW, why don't we create testing2coreany
>> and testing2extraany scripts?  It would be be more convenient than
>> using db-move directely.
>>
>> Probably we would want to combine all these scripts into a single one
>> that would take care of all arches. Maybe this would work (untested):
>>
>> ================
>> #!/bin/bash
>>
>> if [ $# -le 0 ]; then
>>    echo "usage: $(basename 0) <packagename> [<packagename> [<packagename ...]]"
>>    exit 0
>> fi
>>
>> for pkg in $@; do
>>    echo "==> Moving package '$pkg'"
>>    $(dirname $0)/db-move "$pkg" "testing" "core" "i686"
>>    $(dirname $0)/db-move "$pkg" "testing" "core" "x86_64"
>>    $(dirname $0)/db-move "$pkg" "testing" "core" "any"
>> done
>> ====================
>>
>> And similar for testing2extra.
>
> I'll look into it if no one else wants to - if you want, you may be
> able to make a dummy repo in there (thought the dir will require an
> admin) to play with so you can test this on gerolde. If not, you can
> always check out via git and change svn locations and whatnot
>

I haven't had time to look into this further. Anyone is free to look
into it. I'm just bumping the thread so we don't forget it for the
next dbscript release.


More information about the arch-dev-public mailing list