[csw-maintainers] Did I just break something?

[Peter Bonivart]

On Sun, May 12, 2013 at 7:41 PM, Peter Bonivart <bonivart at opencsw.org> wrote:
> bonivart at login[build.2013-05-12]$ csw-upload-pkg pm_hook* pm_log* pm_test*
> Processing 6 file(s). Please wait.
> Checking 6 package(s) against catalog unstable sparc SunOS5.10
> Checking 6 package(s) against catalog unstable i386 SunOS5.10
> Checking 3 package(s) against catalog unstable sparc SunOS5.11
> WARNING:root:Not saving an error for CSWpmlogany.
> WARNING:root:Not saving an error for CSWpmlogany.
> WARNING:root:Not saving an error for CSWpmlogany.
> WARNING:root:Not saving an error for CSWpmlogany.
> WARNING:root:Not saving an error for CSWpmlogany.
> WARNING:root:Not saving an error for CSWpmlogany.
> WARNING:root:Not saving an error for CSWpmlogany.
> WARNING:root:Not saving an error for CSWpmlogany.
> WARNING:root:Not saving an error for CSWpmlogany.
> WARNING:root:Not saving an error for CSWpmhooklexwrap.
> WARNING:root:Not saving an error for CSWpmhooklexwrap.
> Checking 6 package(s) against catalog unstable i386 SunOS5.11
> Checks failed for catalogs:
>   - sparc SunOS5.11
>     pm_hook_lexwrap-0.24,REV=2013.05.12-SunOS5.10-all-CSW.pkg.gz
>     pm_log_any-0.15,REV=2013.05.12-SunOS5.10-all-CSW.pkg.gz
>     pm_testdeep-0.110,REV=2013.05.12-SunOS5.10-all-CSW.pkg.gz
> To see errors, run:
>   /home/bonivart/opencsw/.buildsys/v2/bin/checkpkg --catalog-release
> unstable --os-release SunOS5.11 --catalog-architecture sparc
> d71e8ae17cb5a5706b26b0ed73fe4398 2fab102e3fe5e962bee48f98120dea18
> 6bb16854c24e0ec63046cdde3f707d59
> Packages have not been submitted to the unstable catalog.

More info. I think it started with me being lazy and not selecting
which packages to upload, instead I just ran "csw-upload-pkg *" in my
staging dir where I already had 18 previously uploaded packages. I
expected it to skip those based on the checksum and it didn't upload
them but it did check the whole set of 24 packages which is
understandable depending on how you view it. Anyway, at the end I got
some kind of server timeout and tried again, I think the first error
caused the new packages not to be properly added to the 5.11 catalogs
and now it claims (by running the above command) I have file
collisions which I obviously didn't have before trying to upload.