Hello fellow maintainers, Many of you were not happy with the way submitpkg worked. It used to take only catalognames as arguments, and expect all packages to reside in a specified directory. This behavior is now changed; from now on, submitpkg takes direct package paths (relative or absolute), and processes just the given files, with no additional magic.
There are checks done to the file set, for example, if there is a i386 package present, submitpkg expects there to be a corresponding sparc package too. This makes it harder to make While this holds true for most packages, and missing the sparc package is a bug, there are legitimate cases such as the Acrobat reader, which is only available for the Intel architecture. When such package needs releasing, the --force option can be used to push the package despite failing checks. The new version of CSWcswutils (containing submitpkg) has been installed on the login host. If you run into any issues running submitpkg, please let me know. Thanks, Maciej _______________________________________________ maintainers mailing list [email protected] https://lists.opencsw.org/mailman/listinfo/maintainers .:: This mailing list's archive is public. ::.
