[csw-maintainers] please review gdb's recipe; catalog and ISA issues

[Maciej (Matchek) Bliziński]

2012/7/26 Peter FELECAN <pfelecan at opencsw.org>
>
> The previous versions contained for all platforms:
>
> gdb 7.2,REV=2011.01.21 CSWgdb

The version might be the same, but the svr4 packages could be
different. csw-upload-pkg tries to keep things constant: if they were
the same, they stay the same. If they were different, they stay
different.

I think the dublin catalog contains the previous state of the unstable
catalog. You can check the md5 sums using the rest interface, e.g.:

function get_md5 {
curl -s \
  "http://buildfarm.opencsw.org/pkgdb/rest/catalogs/$2/$3/$4/catalognames/$1/" \
  | python -c "import json, sys; print json.loads(sys.stdin.read())['md5_sum']"
}

for arch in sparc i386; do
  for os_rel in 9 10 11; do
    printf "%06s %02s " "$arch" "$os_rel"
    get_md5 gdb dublin "$arch" "SunOS5.$os_rel"
  done
done

If you run this script, you'll get:

 sparc  9 7971e31461b53638d7813407fab4765b
 sparc 10 09cccf8097e982dadbd717910963e378
 sparc 11 09cccf8097e982dadbd717910963e378
  i386  9 538eadd41b92393c0a65bf320defb3eb
  i386 10 c989477b46f213cd3cad5f8bc94a2afd
  i386 11 c989477b46f213cd3cad5f8bc94a2afd

Which shows that versions in the 5.9 catalogs are different from
versions in the 5.10 catalog.

If the behavior of csw-upload-pkg was surprising, maybe it was because
of too much magic? I think we talked about this, and the suggestions
from maintainers were to have csw-upload-pkg do what it's currently
doing.

Maciej