Re: bulky-but-brainless updates 2001.05.26

Pushing back the barriers of Sadness (

Date: Sat, 26 May 2001 23:37:02 +0100
------^^^  ------------^^^^^^^^

but not as bad at Matt...

Date: Sun, 27 May 2001 02:53:43 +0100 (BST)
------^^^  ------------^^^^^^^^

), Jonathan writes:

> But I found a nasty problem. I sucked down the new ark code. Noticed the 
> problem with the new pickle format, so I ditched all my xmla's and ran:
> 
>      ark package reveal --redo arkbase
> 
> To update to the new code. However, this rebuilds a bunch of the xmla's 
> with the old code, then switches part way through the process to the new 
> code, which tries to read them in and barfs.

Another possible hack is to use sidai/package-utils/arkbase-update
and tweak the line...

ARKPKG='ark package'

to be something that will run *out of your fresh source tree*.

> I'm hitting a new bug with the rhlinux changes that I can't track down 
> though. An attempt to reveal a package is complaining about "no such 
> thing: .../ia32-rhlinux.xml", but I'm sure (find&grep sure) that there 
> aren't any references to rhlinux in my team directory. It seems to barf 
> during dependency checking/evaluation. Ideas?

Something lingering in a pickle file?  I tried to be pretty
thorough with 'M-x tags-search rhlinux' before committing.

> On an unrelated note: I also made some local changes to only show 
> exception tracebacks if the verbose flag has been set. ...

Yes, I'll go with that.

> ... , but I've discovered that the glasli1 team is no
> longer bootable with the extensive changes to sidai over
> the last few months.

Yurk; pls advise!

> I'm also having some difficulty getting my head around sidai. I like the 
> policies generally, but sometimes I can't figure out what the policy is 
> to decide if I like it ;-)

Hey, demand-driven documentation...

> For instance: how is ark-diffing-deploy meant to work? Once I've looked 
> at the diffs and satisfied myself that it's what I want to do. How do I 
> push them through? [Takes me back to OUR days...]

I normally do it through sidai/package-utils/ark-invasive.
At the end, it will invite you to

echo '# if happy with what you see, you could finish the job with:'
echo $ARKPKG reveal --force-reveal $HOSTS $CONHOSTS --use-deps=min $VERBOSE $pkgs

(basically, just 'reveal' with --force-reveal set)

Incidentally, I'm musing on some tweaks to
diffing-deploys...  First, I would like them to chat less.
Second, I would like the reveal to do nothing (much) unless
something really changed (so we don't restart
sendmail/syslog/whatever unnecessarily).  I'm thinking of
changing the diffs to do something like

   diff old new || touch /.-ark-deploy/foo-config/.ark-reveal-needed

and then the reveal acting accordingly.

Will