[csw-maintainers] [csw-devel] SF.net SVN: gar:[15079] csw/mgar/pkg/libserf/trunk/Makefile

Dagobert Michelsen dam at opencsw.org
Sun Jul 17 16:33:28 CEST 2011

Hi Rupert,

Am 17.07.2011 um 16:13 schrieb rupert THURNER:
> for three reasons:
> 1. it did not build with the package split
> 2. it is a very small package and it adds complexity

Splitting off devel is a real good idea, and taking back an already splitted package
is a real bad idea.

> 3. something broke serf support in subversion a couple of months ago
>     and with my restricted knowledge i was not able to upgrade subversion and serf.
> i removed the libserf0-0 obsolete, and now it complains about libserf-devel:
> $ csw-upload-pkg pkgs/17.Jul.2011/libserf*
> Processing 3 file(s). Please wait.
> Checking 2 package(s) against catalog unstable sparc SunOS5.9
> Checking 2 package(s) against catalog unstable i386 SunOS5.9
> Checking 2 package(s) against catalog unstable sparc SunOS5.10
> Checking 2 package(s) against catalog unstable i386 SunOS5.10
> All checks successful. Proceeding.
> Inserting libserf1_0 (i386 SunOS5.9) into catalog unstable i386 SunOS5.10
> Inserting libserf_devel_stub (all SunOS5.9) into catalog unstable i386 SunOS5.10
> CRITICAL:root:Response: 406 {"error_message": "There already is a package with that pkgname: CSWlibserf-devel"}
> Traceback (most recent call last):
>   File "/opt/csw/bin/csw-upload-pkg", line 596, in <module>
>     uploader.Upload()
>   File "/opt/csw/bin/csw-upload-pkg", line 172, in Upload
>     self._InsertIntoCatalog(filename, arch, osrel, file_metadata)
>   File "/opt/csw/bin/csw-upload-pkg", line 375, in _InsertIntoCatalog
>     raise RestCommunicationError("%s - HTTP code: %s" % (url, http_code))
> __main__.RestCommunicationError: http://buildfarm.opencsw.org/releases/catalogs/unstable/i386/SunOS5.10/f227ae44170d9dd97d60e1c1c6c934e4/ - HTTP code: 406

For obsoletiong the prio package to the stub must be removed manually for now.

> in general i'd prefer less complex recipies, which are easy upgradable even by non-experts ... like me  :)

True. But please keep in mind that I just recently updated libserf and usually not
introduce complexity for fun:

The interesting thing is that you can really take out much of the real complexity
like handling post-configure-libtool and fiddling with pathes in 1.0:

I'll happily renew my offer from last time: If you are working on a package
I recently updated please ask me on any issues and I explain them so you can
take over the package cleanly and you can maintain it in the future. I am unhappy
if you just rip out stuff and try to release the resulting packages without

I rebuild and released the package resulting from the latest revision to unstable
for your convenience:

-rw-r--r--   1 dam      csw        45074 Jul 17 16:30 libserf1_0-1.0.0,REV=2011.07.17-SunOS5.9-i386-CSW.pkg.gz
-rw-r--r--   1 dam      csw        48050 Jul 17 16:28 libserf1_0-1.0.0,REV=2011.07.17-SunOS5.9-sparc-CSW.pkg.gz
-rw-r--r--   1 dam      csw        23700 Jul 17 16:30 libserf_dev-1.0.0,REV=2011.07.17-SunOS5.9-i386-CSW.pkg.gz
-rw-r--r--   1 dam      csw        23469 Jul 17 16:27 libserf_dev-1.0.0,REV=2011.07.17-SunOS5.9-sparc-CSW.pkg.gz
-rw-r--r--   1 dam      csw         5077 Jul 17 16:30 libserf_devel_stub-1.0.0,REV=2011.07.17-SunOS5.9-all-CSW.pkg.gz

Best regards

  -- Dago

More information about the maintainers mailing list