-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Ludwig Nussel schrieb:
> On Tuesday 09 May 2006 10:05, Rauch Christian wrote:
>> I had a look at y2pmbuild and got it working by now, though there remain
>> some questions to me:
>>
>> 1. When I build a few packages at once, which rely upon, the packages
>> are written to the repository and createrepo/create_package_descr is
>> called. (I can see this in the output). Though the next package fails,
>> because it can't find the previously built package. When I take out the
>> sources for the already built package and run y2pmbuild again, the next
>> package builds and so on. Can this be solved? Is it a matter of config?
> 
> That's supposed to work automatically if url_repository is set correctly.
> 

Just tried things from beginning, but it does not work. The previous 2
packages are built correctly and appear in my repository.

Then build of the third package starts and complains about missing
packages. See the following output:

> using settings:
> datadirs: .
> languages: english
> output dir: ./setup/descr/
> is not a directory: ignoring
> extra_provides: not specified
> WARNING: this means all provides like /bin/sh will be missing
> find: warning: you have specified the -maxdepth option after a
> non-option argument -name, but options are not positional (-maxdepth
> affects tests specified before it as well as those specified after
> it).  Please specify options before other arguments.
>
>  done
> processed 6 packages
> now recoding to UTF-8: packages packages.DU packages.en
> /work/sources/10.0 /work/sources/10.0
> /work/sources/10.0
> /work/sources/10.0 /work/sources/10.0
> WARNING: spec file misses 'norootforbuild'
> aaa_base not in BuildRequires, adding default packages
> Welcome to the YaST2 Package Manager!
> This tool is meant for debugging purpose only.
>
> root dir set to /work/build/.root.10.0
> running from system no
> ATTENTION: this is a one way ticket. Resetting this to true has not
> effect!
> initializing installation sources ...
> initializing target ...
> rebuilding RPM database
> ..................................................... ok
> reading RPM database
> ........................................................ ok
> Known sources:
> 0: [x] file:/work/repository/10.0/ (file:/work/repository/10.0)
> [autorefresh]
> 1: [x] SUSE LINUX Version 10.0 (file:/work/dist/opensuse/10.0/)
> 2: [x] oc2pus (SUSE LINUX 10.0)
> (file:/srv/ftp/repositories/suser-oc2pus/10.0/)
> 3: [x] supplementary GNOME 2.12 update
> (file:/srv/ftp/supplementary/GNOME/update_for_10.0/yast-source/)
> 4: [x] file:/work/repository/10.0// (file:/work/repository/10.0/)
> [autorefresh]
> debug disabled
> package g-wrap-devel is not available.
> package g-wrap is not available.
> package Guppi-devel is not available.
> package Guppi is not available.

<bunch of packages gets installed>
Then configure of the following software fails, because it cannot find
these packages.

the file setup/descr/packages in my repository contains the entries
for the packages built already, and the rpms are in their folders.

This is my /etc/y2pmbuild/dists_common:

repository="/work/repository/$BUILD_DIST"
regen_repository="plain"
url_repository="file:$repository"
extra_copy=""
buildrootbase="/work/build/"
rpm_sign_name="Rauch Christian <[EMAIL PROTECTED]>"
rpm_sign_key="/etc/y2pmbuild/signkey.asc"

and my /etc/y2pmbuild/dists/10.0:
<snipped default packages (unchanged)>
url_opensuse="file:/work/dist/opensuse/10.0/"
url_oc2pus="file:/srv/ftp/repositories/suser-oc2pus/10.0/"
url_gnomeupdate="file:/srv/ftp/supplementary/GNOME/update_for_10.0/yast-source/"
url_updates="file:/work/repository/10.0/"
add_sources="opensuse oc2pus gnomeupdate updates "
regen_repository="yum"
regen_repository="plain"
regen_repository="ul"
# vim:syntax=sh


Any idea about this?

Regards,
Christian
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)

iD8DBQFEYIxKayhvFxrDZlkRAgVTAJ9CmiBnHrBa6Tc7q/RM9AJ0NQb0wQCfb1dF
MVQmbEBBRQ3WG73NypCzOg0=
=qi3N
-----END PGP SIGNATURE-----

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to