September 2009 - openSUSE Software Management

[softwaremgmt] Autoenable-feature for services
by J. Daniel Schmidt 18 Oct '10

18 Oct '10

Hi, I'd like to discuss a new feature for (NU) Services. A service can contain multiple repos and they may change over time. All these changes are automatically apllied to the system during a refresh of the service. But one thing is missing IMHO. All new repos always remain disabled and have to be enabled manually. In the registration process we therefore enable each repo one by one. The server has no way to tell the client what repos should be enabled in his opinion. And the client has no possibility to change the policy to always enable repos in services. I'd recommend to add a new property to the repo definition in the repoindex.xml: enable="1". Repos tagged like this should be enabled (of course only in the opinion of the server). When a service gets added on a client the service should get a new parameter: autoenable=<value> in its service file (zypper needs to support it). The value might be one of: all = automatically enable all repos that the server has remote = automatically enable all repos that are tagged with enable="1" none = no automatic enabling - default (if missing), to be backward compatible By this, the authority still remains on the client. The client can decide what policy he wants to use. And the change of the policy is per service, so changing the policy for one service does not change for all services. This would be a nice feature for services as you could add one service that you trust (maybe you administer it yourself) and then forget about it, as the repos will always adapt automatically. I had short conversations with Duncan MacVicar and Marcus Meissner about this topic today but now want to open it for a discussion. What do you think? Are there better ways to do this? Are there side-effects or security issues? Ciao, Daniel -- J. Daniel Schmidt <jdsn(a)suse.de> SUSE Linux Products GmbH Research & Development Maxfeldstr. 5 GF: Markus Rex, HRB 16746 (AG Nürnberg) D-90409 Nürnberg -- To unsubscribe, e-mail: opensuse-softwaremgmt+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-softwaremgmt+help(a)opensuse.org

2 2

[softwaremgmt] setup own repo
by Elmar Stellnberger 16 Sep '09

16 Sep '09

Trying to set up an own repo I have run into the problem of zypper not accepting my private key signature. Following the instructions at http://en.opensuse.org/Secure_Installation_Sources I should have successfully created all necessary files: cd <repository directory> createrepo . gpg -a --detach-sign repodata/repomd.xml gpg -a --export <your key id> > repodata/repomd.xml.key ls repodata/ filelists.xml.gz primary.xml.gz repomd.xml.asc repomd.xml.key other.xml.gz repomd.xml repomd.xml.asc.oss However zypper refuses to use my repo: > zypper refresh --force Xorg-anc Forcing raw metadata refresh Retrieving repository 'Xorg-anc' metadata [error] Repository 'Xorg-anc' is invalid. File /var/tmp/TmpFile.OGmlRL doesn't contain public key data Please check if the URIs defined for this repository are pointing to a valid repository. Skipping repository 'Xorg-anc' because of the above error. Could not refresh the repositories because of errors. Searching for similar errors on the web I have found out that zypper might have a problem with my gpg version. The oss repos repomd.xml.asc.oss starts like the following -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) while my own repomd.xml.asc looks like this: -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (GNU/Linux) ..... Will I have to use an elder gpg version or should I try sth. else? -- To unsubscribe, e-mail: opensuse-softwaremgmt+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-softwaremgmt+help(a)opensuse.org

2 9

[softwaremgmt] rypper - extension for managing multiple repositories via zypper
by Adam Spiers 16 Sep '09

16 Sep '09

Hi all, Such is the value of the openSUSE Build Service from my perspective that I now have over 40 repositories registered on my main SUSE machine! I found that zypper was slightly awkward for managing this number of repositories, so I found a few hours of spare time to knock up the following; hope it's of use to somebody. Patches welcome! http://adamspiers.org/computing/rypper Here is an extract from the documentation for those reading this offline on their Blackberries :-) =head1 NAME rypper - extension for managing multiple repositories via zypper =head1 SYNOPSIS # See complete usage documentation rypper --help # list all disabled repos rypper -d # list all enabled repos with autorefresh off rypper -e -R # list all repos which have anything to do with KDE rypper -x kde # list priority and URIs for all repos whose alias contains 'home:' rypper -a home: l -pu # enable autorefresh on all OpenSUSE Build Service repos rypper -u download.opensuse.org -R mr -r # remove all repos on external USB HDD mounted on /media/disk rypper -u /media/disk rr =head1 DESCRIPTION rypper is a wrapper around zypper for performing repository operations in batch. It allows selection of which repositories to operate on via a number of different repository selection specifiers. The zypper commands which can be wrapped are: removerepo, rr Remove specified repository. modifyrepo, mr Modify specified repository. refresh, ref Refresh all repositories. clean Clean local caches. Additionally, the zypper pseudo-command 'l' can be used to list matching repos. There are a number of options controlling the output format; run C<rypper --help> for details. If no zypper command is provided, it defaults to the 'l' pseudo-command, trying to intelligently choose which fields to display, e.g. omitting any which were included in the repo selection parameters. -- To unsubscribe, e-mail: opensuse-softwaremgmt+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-softwaremgmt+help(a)opensuse.org

2 2

[softwaremgmt] Power Outage
by ml-admin＠opensuse.org 11 Sep '09

11 Sep '09

Broadcast message from ml-admin(a)opensuse.org (/dev/pts/0) at 07:30 GMT ... The system is going down for halt NOW! -- To unsubscribe, e-mail: opensuse-softwaremgmt+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-softwaremgmt+help(a)opensuse.org

1 0