December 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] [ANNOUNCE] ZYpp source repositories on gitorious.org/opensuse
by Duncan Mac-Vicar Prett 11 Dec '09

11 Dec '09

The ZYpp repositories previously published at git.opensuse.org repositories are now available on http://gitorious.org/opensuse http://gitorious.org/opensuse/sat-solver http://gitorious.org/opensuse/libzypp http://gitorious.org/opensuse/zypper http://gitorious.org/opensuse/zypp-utils (previously zypp/tools) http://gitorious.org/opensuse/libzypp-bindings http://gitorious.org/opensuse/libzypp-testsuite http://gitorious.org/opensuse/zypp-dialogsolver http://gitorious.org/opensuse/cmpi-zypp http://gitorious.org/opensuse/zypp-zmd-backend (previously zypp/backend) There is an initial opensuse-zypp team defined with access to those repositories. To switch you only need to edit your .git/config origin remote If before it was git@git.opensuse.org:projects/zypp/zypper.git Now it would be: git@gitorious.org:opensuse/zypper.git The repositories in git.opensuse.org are still accessible, but you can't push to them anymore. They will stay there until no repositories are left on that machine. Gitorious provides feeds for each repository pushes, and per each branch commits. To make it easier to follow the overall project, I have created this feed which merges various feeds and make the titles more similar to the old mails: http://pipes.yahoo.com/pipes/pipe.info?_id=36dc1dc1c0380cca92df9ddaa5b6e26d In the next days we will look for a solution to mail those feed updates to the commits mailing list. -- Duncan Mac-Vicar P. - Engineering Manager, YaST SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) -- To unsubscribe, e-mail: opensuse-softwaremgmt+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-softwaremgmt+help(a)opensuse.org

1 0

[softwaremgmt] Re: RFC: enhancerepo 0.4.0
by Duncan Mac-Vicar Prett 10 Dec '09

10 Dec '09

On Wednesday 09 December 2009 17:40:50 Jordi Massaguer Pla wrote: > Hi Duncan, > > I am attaching a new patch. Basically it adds the functionality to split > or merge any of the xmls in the repodata. > > We use this functionality in order to filter some rpms and its data > associated, so that we distribute only the updates associated to the > rpms we provide support of. > > See attached patches for version 0.3.2 . Could they be applied to the > 0.4.0? Your split-updates patch was merged long time ago :-) It is just missing from the command line help, I will fix that -- Duncan Mac-Vicar P. - Engineering Manager, YaST SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) -- To unsubscribe, e-mail: opensuse-softwaremgmt+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-softwaremgmt+help(a)opensuse.org

1 0

[softwaremgmt] RFC: enhancerepo 0.4.0
by Duncan Mac-Vicar Prett 08 Dec '09

08 Dec '09

Hey guys I just uploaded to home:dmacvicar what I would like to be enhancerepo 0.4.0 This release has lot of refactorings, bugfixes and new testcases as a result of the feedback of the Linkat guys (Jordi & Jordi) and also from Michael Calmer who works in our SLE migration process. Before release I want to wait a small time-window to collect some feedback. I do not plan to fix all issues, as I already have a TODO list for 0.4.1, but depending on the feedback I may hold releasing it. Changes: * Various delta and update generation bugfixes: * improved logger support * --split-updates, patch by Jordi Massaguer Pla * primary data generation (EXPERIMENTAL, don't use it yet) * allows to generate metadata to a separate directory * product metadata generation extracted from *-release rpm packages * benchmark feature * speed improvements * lot of testcases to avoid regressions TODO for 0.4.1 - finish switching xml parsing and creation to nokogiri, to speedup - experiment with primary metadata support Things you can do with enhancerepo: * take a rpmmd repository (created by createrepo) and add disk usage information, expiry info, keywords * take a rpmmd repository containing various versions of some package, and generate any level of deltarpms and generate deltainfo.xml automatically * take a rpmmd repository containing various versions of some package, and generate patches grouping the packages per fix/issue, automatically generating the patch description from the changelog, including bug and security references * more... If you want the latest code, it can be run from the source tree: bin/enhancerepo --help Get it from: git clone git://gitorious.org/opensuse/enhancerepo.git -- To unsubscribe, e-mail: opensuse-softwaremgmt+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-softwaremgmt+help(a)opensuse.org

1 0