dockyard-tools

This is just to bring us all up to date as to the current status of things, 
remind everybody how things work, and what steps you should go through to 
troubleshoot a 'problem' before assuming something is broken. 

dydbupdate updates the unstable (and potentially, the stable, if forced) 
dytools pkg database with the current pkg version, cksum, srpmkey (i.e. which 
source RPM this pkg comes from) and the package's current status (that thing 
nobody bothers to update).

dymv2stable copies unstable (dockyard-devel) packages to stable (dockyard), 
compares cksums (to make sure the file we just copied is the one we knew 
about in dockyard-devel), then updates the databases.

Now for the useful information.  If you don't know what a valid cmdline looks 
like for either of these, here are samples:

dydbupdate --srpmkey ark-config-tools -s T -v ark-config tools
dydbupdate --srpmkey nvidia -s T -v --tree contrib nvidia

--srpmkey adds an entry in the srpm database for this package under that key.
-s T sets the status to Tested.
-v gives verbose output (actually without this you get NO output)
--tree contrib determines that this package goes in the contrib tree.
(--tree will also be used for x86_64 I believe)

In the event that you realize a package has no stable db entry, you can 
specify one by adding the --stable flag.  (this should probably be done FROM 
that directory with the full filename rather than just the packagename, 
otherwise it'll most likely grab the unstable pkgname)

dymv2stable is easier

dymv2stable -b -v ark-config-tools
dymv2stable -b -v --tree contrib nvidia

for those of you who don't see the need to update the status after testing, 
you'll likely want to use the -b flag, as this enables 'batch' mode, and 
removes the warning prompts you will get.
-v gives kooky little hash progress bars
--tree designates which tree this goes to.

NOW for the fun stuff

IF you attempt to dymv2stable something and things simply blow up, it says 
your cksums don't match, or anything of the sort.. the FIRST thing you should 
do is run 'getstatus'.  This polls the 2 databases and shows you what IT 
thinks the state of the union is.

you MUST provide an architecture for this.. it's not smart enough to poll for 
all archs.. so

getstatus -a i586 ark-config-tools

will show you what dockyard-tools thinks the proper files are for each.  IF 
there is no file entry for either or both, THIS is your problem!!!  
dymv2stable relies on these entries to explain reality, so if there is 
nothing here, it gets overly confused and is likely to run away and cry.

At this point you should run dydbupdate to get these fields populated, THEN 
you should be able to perform the move.  Downside is.. if you don't get the 
stable entry done correctly, and it reflects the unstable file, it WILL still 
move the file over, but it will NOT remove the old file (cause it doesn't 
know about it anymore).. so you will have to check on this and do it 
manually.

That's pretty much it.  If you don't understand why we're doing this, or think 
you do and know of a better way, pls let me know.. but for now this is 
getting the job done (and I am pretty sure I've got it fixed to delete the 
old file now, bero)

Cirnath