FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > ArchLinux > ArchLinux Development

 
 
LinkBack Thread Tools
 
Old 10-28-2009, 09:44 AM
Allan McRae
 
Default changes needed in db-scritps - Was: The docs/!docs thing again

Eric Bélanger wrote:

Yes, that's what we're supposed to do; it was probably an oversight.
Splitting big docs like this will be easy once the new makepkg with
multi-arch support for split package will be out (assuming the
dbscripts can handle it).



The dbscripts do not handle that. They also do not handle only
uploading one or some packages from a split package (pkgrel can now be
overridden and a selection of packages updated).


Allan
 
Old 10-28-2009, 10:22 AM
Eric Bélanger
 
Default changes needed in db-scritps - Was: The docs/!docs thing again

On Wed, Oct 28, 2009 at 6:44 AM, Allan McRae <allan@archlinux.org> wrote:
> Eric Bélanger wrote:
>>
>> Yes, that's what we're supposed to do; it was probably an oversight.
>> Splitting big docs like this *will be easy once *the new makepkg with
>> multi-arch support for split package will be out (assuming the
>> dbscripts can handle it).
>>
>
> The dbscripts do not handle that. *They also do not handle only uploading
> one or some packages from a split package (pkgrel can now be overridden and
> a selection of packages updated).
>
> Allan
>
>

They also can't handle split packages with different pkgver or pkgrel.
So they'll need a major maintainance update indeed. There is a
pending dbscripts update. Maybe we should release it before starting
to work on them to support the new features in the upcoming makepkg.
 
Old 10-28-2009, 05:56 PM
Aaron Griffin
 
Default changes needed in db-scritps - Was: The docs/!docs thing again

On Wed, Oct 28, 2009 at 6:22 AM, Eric Bélanger <snowmaniscool@gmail.com> wrote:
> On Wed, Oct 28, 2009 at 6:44 AM, Allan McRae <allan@archlinux.org> wrote:
>> Eric Bélanger wrote:
>>>
>>> Yes, that's what we're supposed to do; it was probably an oversight.
>>> Splitting big docs like this *will be easy once *the new makepkg with
>>> multi-arch support for split package will be out (assuming the
>>> dbscripts can handle it).
>>>
>>
>> The dbscripts do not handle that. *They also do not handle only uploading
>> one or some packages from a split package (pkgrel can now be overridden and
>> a selection of packages updated).
>>
>> Allan
>>
>>
>
> They also can't handle split packages with different pkgver or pkgrel.
> So they'll need a major maintainance update indeed. *There is a
> pending dbscripts update. *Maybe we should release it before starting
> to work on them to support the new features in the upcoming makepkg.

I think everything is in there and live in /arch-test/

Can I get one or two "go aheads" to move it live? Then we can work on
this malarky.

As for the db-scripts changes here - we simply need to be able to grok
info internal to the other functions, yes?
 
Old 10-28-2009, 09:05 PM
Eric Bélanger
 
Default changes needed in db-scritps - Was: The docs/!docs thing again

On Wed, Oct 28, 2009 at 2:56 PM, Aaron Griffin <aaronmgriffin@gmail.com> wrote:
> On Wed, Oct 28, 2009 at 6:22 AM, Eric Bélanger <snowmaniscool@gmail.com> wrote:
>> On Wed, Oct 28, 2009 at 6:44 AM, Allan McRae <allan@archlinux.org> wrote:
>>> Eric Bélanger wrote:
>>>>
>>>> Yes, that's what we're supposed to do; it was probably an oversight.
>>>> Splitting big docs like this *will be easy once *the new makepkg with
>>>> multi-arch support for split package will be out (assuming the
>>>> dbscripts can handle it).
>>>>
>>>
>>> The dbscripts do not handle that. *They also do not handle only uploading
>>> one or some packages from a split package (pkgrel can now be overridden and
>>> a selection of packages updated).
>>>
>>> Allan
>>>
>>>
>>
>> They also can't handle split packages with different pkgver or pkgrel.
>> So they'll need a major maintainance update indeed. *There is a
>> pending dbscripts update. *Maybe we should release it before starting
>> to work on them to support the new features in the upcoming makepkg.
>
> I think everything is in there and live in /arch-test/
>
> Can I get one or two "go aheads" to move it live? Then we can work on
> this malarky.

I've been using /arch-test/ since you set it up. I haven't encountered
any problems. You'll also need to add the sourceballs and source
cleanup scripts to the cron jobs.

>
> As for the db-scripts changes here - we simply need to be able to grok
> info internal to the other functions, yes?
>
 
Old 10-28-2009, 09:58 PM
Aaron Griffin
 
Default changes needed in db-scritps - Was: The docs/!docs thing again

On Wed, Oct 28, 2009 at 5:05 PM, Eric Bélanger <snowmaniscool@gmail.com> wrote:
> On Wed, Oct 28, 2009 at 2:56 PM, Aaron Griffin <aaronmgriffin@gmail.com> wrote:
>> On Wed, Oct 28, 2009 at 6:22 AM, Eric Bélanger <snowmaniscool@gmail.com> wrote:
>>> On Wed, Oct 28, 2009 at 6:44 AM, Allan McRae <allan@archlinux.org> wrote:
>>>> Eric Bélanger wrote:
>>>>>
>>>>> Yes, that's what we're supposed to do; it was probably an oversight.
>>>>> Splitting big docs like this *will be easy once *the new makepkg with
>>>>> multi-arch support for split package will be out (assuming the
>>>>> dbscripts can handle it).
>>>>>
>>>>
>>>> The dbscripts do not handle that. *They also do not handle only uploading
>>>> one or some packages from a split package (pkgrel can now be overridden and
>>>> a selection of packages updated).
>>>>
>>>> Allan
>>>>
>>>>
>>>
>>> They also can't handle split packages with different pkgver or pkgrel.
>>> So they'll need a major maintainance update indeed. *There is a
>>> pending dbscripts update. *Maybe we should release it before starting
>>> to work on them to support the new features in the upcoming makepkg.
>>
>> I think everything is in there and live in /arch-test/
>>
>> Can I get one or two "go aheads" to move it live? Then we can work on
>> this malarky.
>
> I've been using /arch-test/ since you set it up. I haven't encountered
> any problems. *You'll also need to add the sourceballs and source
> cleanup scripts to the cron jobs.

Ok, I'll do the move soon. How often should the sourceball cleanup
run? As often as the package cleanup?
 
Old 10-28-2009, 11:54 PM
Eric Bélanger
 
Default changes needed in db-scritps - Was: The docs/!docs thing again

On Wed, Oct 28, 2009 at 6:58 PM, Aaron Griffin <aaronmgriffin@gmail.com> wrote:
> On Wed, Oct 28, 2009 at 5:05 PM, Eric Bélanger <snowmaniscool@gmail.com> wrote:
>> On Wed, Oct 28, 2009 at 2:56 PM, Aaron Griffin <aaronmgriffin@gmail.com> wrote:
>>> On Wed, Oct 28, 2009 at 6:22 AM, Eric Bélanger <snowmaniscool@gmail.com> wrote:
>>>> On Wed, Oct 28, 2009 at 6:44 AM, Allan McRae <allan@archlinux.org> wrote:
>>>>> Eric Bélanger wrote:
>>>>>>
>>>>>> Yes, that's what we're supposed to do; it was probably an oversight.
>>>>>> Splitting big docs like this *will be easy once *the new makepkg with
>>>>>> multi-arch support for split package will be out (assuming the
>>>>>> dbscripts can handle it).
>>>>>>
>>>>>
>>>>> The dbscripts do not handle that. *They also do not handle only uploading
>>>>> one or some packages from a split package (pkgrel can now be overridden and
>>>>> a selection of packages updated).
>>>>>
>>>>> Allan
>>>>>
>>>>>
>>>>
>>>> They also can't handle split packages with different pkgver or pkgrel.
>>>> So they'll need a major maintainance update indeed. *There is a
>>>> pending dbscripts update. *Maybe we should release it before starting
>>>> to work on them to support the new features in the upcoming makepkg.
>>>
>>> I think everything is in there and live in /arch-test/
>>>
>>> Can I get one or two "go aheads" to move it live? Then we can work on
>>> this malarky.
>>
>> I've been using /arch-test/ since you set it up. I haven't encountered
>> any problems. *You'll also need to add the sourceballs and source
>> cleanup scripts to the cron jobs.
>
> Ok, I'll do the move soon. How often should the sourceball cleanup
> run? As often as the package cleanup?
>

No. For reasons explained in the patch comment, weekly is frequent
enough for the source cleanup cronjob. For the regular souceballs cron
job set it to run every 8 hrs as before. As it hadn't ran for a while,
it'll have some catch up to do. If it's too slow or too resource
expensive, we could have it run less often (1 or 2 times per day).
I'll keep an eye on it. And perhaps profile it when time will permits.
 

Thread Tools




All times are GMT. The time now is 03:54 AM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright ©2007 - 2008, www.linux-archive.org