-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 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? 2. With SUSE 10.1, Repositories should be signed. How exactly can this be done and is it possible to automate this with y2pmbuild? 3. In general, is it possible to start a certain script after a build has been finished? 4. Is there any documentation available for y2pmbuild? Neither in the y2pmsh nor in y2pmsh-debuginfo in SUSE 10.0 is any documentation. The articles found on opensuse.org are helpfull, but they do not contain that much information. Regards, Rauch Christian -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFEYE1SayhvFxrDZlkRAuExAJ9cJ5HNcWTgn0JE/3j0GeEoQDaXdACfc5LB cLAkqwH42CHIe3jtKoQM7uU= =Wok6 -----END PGP SIGNATURE-----
Hello, Rauch Christian wrote:
2. With SUSE 10.1, Repositories should be signed. How exactly can this be done and is it possible to automate this with y2pmbuild?
http://en.opensuse.org/Secure_Installation_Sources and I don't know yet a way to automate it with y2pmbuild. But it's not really worth trying, as password for your private key is requested at signing. I sign the repository only just before testing or uploading. Bye, -- CzP http://peter.czanik.hu/
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Peter Czanik schrieb:
Hello,
Rauch Christian wrote:
2. With SUSE 10.1, Repositories should be signed. How exactly can this be done and is it possible to automate this with y2pmbuild?
http://en.opensuse.org/Secure_Installation_Sources and I don't know yet a way to automate it with y2pmbuild. But it's not really worth trying, as password for your private key is requested at signing. I sign the repository only just before testing or uploading. Bye,
Thanks for this link. Went there, done that. :) I will try if everything works as supposed, when I get my hands on 10.1 Final and then post a quick summary here. Thanks, Christian -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFEYIYXayhvFxrDZlkRApPgAJ4mNyCSBs5JCh86NvzI/UurrxvzIACeKI2Q e5fSDdRhIJH4KXYR8H8KW7A= =CEss -----END PGP SIGNATURE-----
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.
2. With SUSE 10.1, Repositories should be signed. How exactly can this be done and is it possible to automate this with y2pmbuild?
3. In general, is it possible to start a certain script after a build has been finished?
Not officially. Although if you set regen_repository=ul and $create_package_descr to a custom script it should achieve the desired effect. UTSL :-)
4. Is there any documentation available for y2pmbuild? Neither in the y2pmsh nor in y2pmsh-debuginfo in SUSE 10.0 is any documentation. The articles found on opensuse.org are helpfull, but they do not contain that much information.
Feel free to extend them. cu Ludwig -- (o_ Ludwig Nussel //\ SUSE LINUX Products GmbH, Development V_/_ http://www.suse.de/
-----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.
repository is set correctly and is in the list of packages to install. I'm currently trying again, but I guess, it will be the same.
3. In general, is it possible to start a certain script after a build has been finished?
Not officially. Although if you set regen_repository=ul and $create_package_descr to a custom script it should achieve the desired effect. UTSL :-)
Nice idea. :) I will give this a try.
cu Ludwig
thanks, Christian -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFEYIa3ayhvFxrDZlkRAtbRAJ0ZdgDXbJ09ZL1ruuCQaffpQSVzQQCfXrq6 8Td6C/kWsk45H/ltRBPC7NM= =M8VY -----END PGP SIGNATURE-----
-----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 <info@rauch-webdesign.de>" 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-----
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Rauch Christian schrieb:
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.
Ok, command back. Even if I start y2pmbuild again, it does not work either. I have to call createrepo by hand in the repository, then it works and my packages are found. After this I have an additional directory "repodata". So calling createrepo from y2pmbuild either does not work or I have misconfigured something... Investigating further.. Christian -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFEYI/QayhvFxrDZlkRAsjIAJ9Y1j0KoFg6VCkx2ZiGcjh6roPo0gCfQ5LQ WErKwA1oDQTldWmYeCGTw5o= =kcem -----END PGP SIGNATURE-----
On Tuesday 09 May 2006 14:34, Rauch Christian wrote:
[...] regen_repository="yum" regen_repository="plain" regen_repository="ul"
This is bourne shell which means $regen_repository will be set to "ul" after the last line. I see for reason for using anything else than "yum" for 10.0. cu Ludwig -- (o_ Ludwig Nussel //\ SUSE LINUX Products GmbH, Development V_/_ http://www.suse.de/
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Ludwig Nussel schrieb:
On Tuesday 09 May 2006 14:34, Rauch Christian wrote:
[...] regen_repository="yum" regen_repository="plain" regen_repository="ul"
This is bourne shell which means $regen_repository will be set to "ul" after the last line.
Ok, this explains things... I will update http://en.opensuse.org/How_to_setup_a_build_server then, because it states atm in #4 the following: | regen_repository="plain" | regen_repository="ul"
I see for reason for using anything else than "yum" for 10.0.
cu Ludwig
Thanks, Christian -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFEYJaiayhvFxrDZlkRAmszAJ0VPHUJEJWuVHzQ/TvJFP6Duyl7kACfQUTU +9HMhlY+uEgDbfRna0nTh9I= =+Ffk -----END PGP SIGNATURE-----
participants (3)
-
Ludwig Nussel -
Peter Czanik -
Rauch Christian