[csw-maintainers] cannot upload update of class action script texhash package
Dagobert Michelsen
dam at opencsw.org
Tue Feb 19 15:22:01 CET 2013
Hi Maciej,
Am 19.02.2013 um 15:19 schrieb Maciej (Matchek) Bliziński <maciej at opencsw.org>:
> 2013/2/19 pfelecan <pfelecan at opencsw.org>:
>> Here is the debug output --- BTW, when running csw-upload-pkg, the debug
>> option is not mentionned in the usage...
>
> Is it not? I'm getting:
>
> maciej at login [login]:~ > csw-upload-pkg --help | grep debug
> -d, --debug
>
> Where did you expect to see it?
>
>> pfelecan at login [login]:~ > csw-upload-pkg --debug
>> staging/build-19.Feb.2013/* 2>&1 | tee ~/logs/csw-upload-pkg
> (...)
>> DEBUG:root:Calling: ['/opt/csw/lib/python/csw/../../bin/custom-pkgtrans',
>
> Here we are. It expects it to be in /opt/csw/lib/bin/custom-pkgtrans,
> and it's not there.
>
> But hang on... the pkgtrans step is never done on login, it should
> not, it cannot be done on login because we're now running ldd as part
> of package indexing. Did you disable checkpkg during the package
> build stage? Or did you not do build it on the buildfarm? Or did you
> run GAR in such a way that it didn't call checkpkg?
As Peter used
mgar package-<pkgname>
to rebuild just a single package I am afraid it does not call checkpkg. Most certainly
it will also not work to call it individually due to the package interdependencies.
Thoughts?
@Peter: You could try to checkpkg it manually, but I doubt it would work.
Best regards
-- Dago
--
"You don't become great by trying to be great, you become great by wanting to do something,
and then doing it so hard that you become great in the process." - xkcd #896
More information about the maintainers
mailing list