rebuilding WebServices / GNUTLS on 9

Maciej Bliziński maciej at
Tue May 1 21:30:24 CEST 2018

On Tue, May 01, 2018 at 09:09:32PM +0200, Dagobert Michelsen via maintainers wrote:
> Hi Riccardo,
> > Am 01.05.2018 um 09:42 schrieb Riccardo Mottola <rmottola at>:
> > 
> > Hi,
> > 
> > I was rebuilding WebServices, of which now all libraries are up-to-date:
> > 
> > I get this on Solaris 10s:
> > 
> > CHECKPKG_OVERRIDES_CSWgnustep-webservices += surplus-dependency|CSWperformance
> > CHECKPKG_OVERRIDES_CSWgnustep-webservices += dependency-on-nonexistent-package|CSWperformance
> > 
> > Why not existent? it is installed!

pkgdb doesn't care about what's installed on your machine. It does care about
what is in the catalog (as represented in the database).

Have a browse around here:

Look at the content of the catalogs you're interested in -- probably 'unstable',
because that's where the packages go after you build them.

Also, take a look here:

This is a list of all the .pkg.gz files that feature 'performance' as the

Overall tip how to deal with mess in pkgdb, if you managed to create some:

pkgdb will warn you about errors it has detected in the package, or potential
problems that might result if you upload the package to pkgdb. But you can
override any and all errors that it shows. So, you may, if you like, force an
upload of a package. If there's a sequence of steps that require you to have
some sort of an inconsistent state, feel free to use overrides, and finally
arrive at a consistent state.

A word of warning: the errors that pkgdb shows you are the only way in which
pkgdb can communicate to you that there are problems, there is no second level
protection. So, you have the freedom to take all the steps to arrive at a
consistent state, but you also have the possibility of leaving the database in
an inconsistent state -- in which case the automation will no longer write the
new catalog to disk, and package releases will stop. Dago knows where to look
for logs from catalog generation.

Dago: do you care to add a link to those logs from

> > 
> > application CSWperformance                   performance - GNUstep data utility library
> Ugh, that is probably another artefact from my attempt to clean up the mess around
> CSWPerformance / CSWperformance. I’ll need to understand the design of pkgdb better,
> maybe Maciej still remember and can shed some light on it.

My brain has garbage-collected most of intimate knowledge of pkgdb, but I still
remember the main ideas: there's a table which holds serialized metadata of each
.pkg.gz file, and there are relations which match every .pkg.gz file to a
catalog (arch+osrel+name_of_catalog).

Hope it helps,

More information about the maintainers mailing list