[arch-dev-public] Need someone with root power on gerolde

[Thayer Williams]

On Mon, Nov 24, 2008 at 8:31 AM, Aaron Griffin <aaronmgriffin at gmail.com> wrote:
> On Mon, Nov 24, 2008 at 10:00 AM, Thayer Williams <thayerw at gmail.com> wrote:
>> On Mon, Nov 24, 2008 at 7:40 AM, Aaron Griffin <aaronmgriffin at gmail.com> wrote:
>>> On Mon, Nov 24, 2008 at 9:38 AM, Thayer Williams <thayerw at gmail.com> wrote:
>>>> On Mon, Nov 24, 2008 at 12:06 AM, Eric Bélanger
>>>> <belanger at astro.umontreal.ca> wrote:
>>>>> On Mon, 24 Nov 2008, Thayer Williams wrote:
>>>>>
>>>>>> On Sun, Nov 23, 2008 at 10:29 PM, Aaron Griffin <aaronmgriffin at gmail.com>
>>>>>> wrote:
>>>>>>>
>>>>>>> On Sun, Nov 23, 2008 at 11:51 PM, Thayer Williams <thayerw at gmail.com>
>>>>>>> wrote:
>>>>>>>>
>>>>>>>> On Sat, Nov 22, 2008 at 11:37 PM, Eric Bélanger
>>>>>>>> <belanger at astro.umontreal.ca> wrote:
>>>>>>>>>
>>>>>>>>> Copying new files to '/srv/ftp//extra/os/x86_64/'
>>>>>>>>> /bin/chmod: changing permissions of
>>>>>>>>> `/srv/ftp//extra/os/x86_64//extra.db.tar.gz': Operation not permitted
>>>>>>>>> /bin/chmod: changing permissions of
>>>>>>>>> `/srv/ftp//extra/os/x86_64//extra.db.tar.gz.old': Operation not
>>>>>>>>> permitted
>>>>>>>>> Cleaning staging dir
>>>>>>>>> error: repo lock doesn't exist... something went terribly wrong!
>>>>>>>>
>>>>>>>> Did I pick a bad night to update packages?  I received the same error
>>>>>>>> when using /arch/db-extra64 and now those packages have gone AWOL.
>>>>>>>
>>>>>>> Actually, the chmod errors should be harmless (I removed the || return
>>>>>>> 1). Please test /arch-new/* if you get a chance.
>>>>>>>
>>>>>>
>>>>>> Running the new db-scripts generates:
>>>>>>
>>>>>> [thayer at gerolde ~]$ /arch-new/db-extra64
>>>>>> error: db generation is already in progress (started by thayer)
>>>>>> 0022
>>>>>>
>>>>>>
>>>>>
>>>>> remove the hidden lock file in /srv/tmp
>>>>
>>>> Thanks, Eric I didn't see this until this morning, but it appears
>>>> someone has already removed it.  However, the x86_64 packages I pushed
>>>> last night are stilling missing in action.  They were cleared from
>>>> ~/staging when I initially ran the /arch/ db scripts, but they're
>>>> still not listed in the repos. Is there something else I need to
>>>> refresh/update?
>>>
>>> Well, in that case, I probably blew them up. See if they're in
>>> /srv/package-cleanup
>>>
>>
>> Nah, they aren't there either.
>>
>> What if I just rebuild the packages, scp them to ~/staging and then
>> run the new db script? These are all trivial non-binary packages so it
>> wouldn't take much effort to do so.
>
> Yep, that's really all the scripts to anyway. Do the svn mojo, scp to
> gerolde, check md5sums, and I think that's it.
>

Cool, I think that took care of it!