November 2011 - Zypp Development - openSUSE Mailing Lists

[zypp-devel] Zypp 12.1 maintenance infrastructure
by Michael Andres 20 Dec '11

20 Dec '11

Hi. After 12.1 is released it's time to set up the maintenance infrastructure. Today I'll start with creating the OBS project for maintaining 12.1 zypp: obs://zypp:Code12_1-Branch Source: git@github.com:openSUSE/ Branch: SuSE-Code-12_1-Branch Feeds: openSUSE:12.1:Update:Test The project will be tested on and fed from Jenkins ZYPP-HEAD node until a ZYPP-12.1 node is available. Gitwise I'd like to stay on master until urgent 12.1 bugs are fixed and released. -- cu, Michael Andres +------------------------------------------------------------------+ Key fingerprint = 2DFA 5D73 18B1 E7EF A862 27AC 3FB8 9E3A 27C6 B0E4 +------------------------------------------------------------------+ Michael Andres SUSE LINUX Products GmbH, Development, ma(a)suse.de GF:Jeff Hawn,Jennifer Guild,Felix Imendörffer, HRB16746(AG Nürnberg) Maxfeldstrasse 5, D-90409 Nuernberg, Germany, ++49 (0)911 - 740 53-0 +------------------------------------------------------------------+ -- To unsubscribe, e-mail: zypp-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: zypp-devel+owner(a)opensuse.org

2 3

[zypp-devel] Adding git version tags for libzypp/zypper
by Michael Andres 29 Nov '11

29 Nov '11

Dear fellow hackers. It was frequently requested to tag the libzypp/zypper versions in git. Today I continued the work Dominik began and updated all the version tags in in git for libzypp (zypper will follow). == To keep them up to date in the future, I updated the 'howto' in the VERSION.cmake files in our branches: # - MOST IMPORTANT: # - Before you submitt to git: # - Remember the new version in 'LAST RELEASED:' # - State the new version in the changes file by adding a line # "- version MAJOR.MINOR.PATCH (COMPATMINOR)" # - Commit changes and version files together in a separate # commit using -m 'changes MAJOR.MINOR.PATCH (COMPATMINOR)' # - Tag the above commit with 'MAJOR.MINOR.PATCH' using # -m "tagging MAJOR.MINOR.PATCH". Dare not to follow these steps ;) == mkChangelog To ease the above procedure, I also updated the mkChangelog script. !!! It expects no files being added to the index, as we want a single commit containing changes and version file only. If files other than changes and version are added, the script does a dryrun (mkChangelog -n) and just lists all commits done since the last release. The script is quite simple: - If you did not yet change the version, it will offer to edit the version file, if you want to. - It will prepare an new changes entry containing all commit summaries since the last release. If the version differs from the last one, a '- version...' entry is also added. The changes file will then be loaded into your EDITOR, so you can beautify the entry. - Done editing you're prompted to either - abort: losing the changes - continue: keep changes unsubmitted, come back later - submitt: commit the changes and tag the commit in case the version was increased, otherwise commit without tag. Don't be afraid, nothing gets pushed automatically. But if you push, don't forget to 'push --tags' as well. -- cu, Michael Andres +------------------------------------------------------------------+ Key fingerprint = 2DFA 5D73 18B1 E7EF A862 27AC 3FB8 9E3A 27C6 B0E4 +------------------------------------------------------------------+ Michael Andres SUSE LINUX Products GmbH, Development, ma(a)suse.de GF:Jeff Hawn,Jennifer Guild,Felix Imendörffer, HRB16746(AG Nürnberg) Maxfeldstrasse 5, D-90409 Nuernberg, Germany, ++49 (0)911 - 740 53-0 +------------------------------------------------------------------+ -- To unsubscribe, e-mail: zypp-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: zypp-devel+owner(a)opensuse.org

1 0

[zypp-devel] RFC zypper addlock --repo
by Michael Andres 24 Nov '11

24 Nov '11

Hi. Bnc#732027 reveals a flaw in zypper addlock --repo <repo> ... This command will lock all matching packages in <repo>, i.e. prevent them from being installed. But in addition to this (or instead of) you may want to lock already installed packages originating from this repo as well. I suppose this is the more interesting usecase, and I'm think this should be the default for --repo. So what about adding 2 new addlock options: addlock --repo locks in repo and installed from repo ++ addlock --from-repo locks installed from repo ++ addlock --repo-only locks in repo -- cu, Michael Andres +------------------------------------------------------------------+ Key fingerprint = 2DFA 5D73 18B1 E7EF A862 27AC 3FB8 9E3A 27C6 B0E4 +------------------------------------------------------------------+ Michael Andres SUSE LINUX Products GmbH, Development, ma(a)suse.de GF:Jeff Hawn,Jennifer Guild,Felix Imendörffer, HRB16746(AG Nürnberg) Maxfeldstrasse 5, D-90409 Nuernberg, Germany, ++49 (0)911 - 740 53-0 +------------------------------------------------------------------+ -- To unsubscribe, e-mail: zypp-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: zypp-devel+owner(a)opensuse.org

3 5

[zypp-devel] using other config with zypper
by Rieke, Manuel 10 Nov '11

10 Nov '11

Thank you for your Help I noticed this Parameter as well, but it does not work for me: # zypper lr No repositories defined. Use the 'zypper addrepo' command to add one or more repositories. # zypper-own --config /opt/zypper-own/etc/zypp/zypp.conf ar /media/SLE-11-SP1-SDK-DVD-x86_64.02.001/ sles11sdk Adding repository 'sles11sdk' [done] Repository 'sles11sdk' successfully added Enabled: Yes Autorefresh: No URI: dir:///media/SLE-11-SP1-SDK-DVD-x86_64.02.001 # zypper lr # | Alias | Name | Enabled | Refresh --+-----------+-----------+---------+-------- 1 | sles11sdk | sles11sdk | Yes | No Thanks again Manuel On 11/10/2011 10:52 AM, Martin Vidner wrote: > On Thu, Nov 10, 2011 at 10:26:04AM +0100, Rieke, Manuel wrote: >> Hi mvidner, >> >> on http://en.opensuse.org/openSUSE:Zypper_development i've read, that >> you are one of the zypper developer. > > Hi Manuel, > > it is better to ask the zypp mailing list (in Cc). > >> Perhaps you could help me with one problem: I want to use 2 versions of >> Zypper on one machine, because I modified the second version. If there >> are problems with my version, i want to use the official one (SLES 11 >> SP1, zypper 1.3.7) without reinstall it. >> >> So I build my own rpm with a different name of zypper. The Installation >> works perfectly and it runs as it shoud. >> >> The problem are the same configfiles of both versions. Is it possible to >> use an other configuration directory for my version? > > zypper --config /usr/local/etc/myspecialzypper.conf command --options args > > Please consider reading the fine manual: man zypper, searching for > "config" reveals this as the second hit. > >> >> Thanks for your help >> >> Regards >> >> Manuel Rieke -- To unsubscribe, e-mail: zypp-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: zypp-devel+owner(a)opensuse.org

2 1

[zypp-devel] Re: using other config with zypper
by Martin Vidner 10 Nov '11

10 Nov '11

On Thu, Nov 10, 2011 at 10:26:04AM +0100, Rieke, Manuel wrote: > Hi mvidner, > > on http://en.opensuse.org/openSUSE:Zypper_development i've read, that > you are one of the zypper developer. Hi Manuel, it is better to ask the zypp mailing list (in Cc). > Perhaps you could help me with one problem: I want to use 2 versions of > Zypper on one machine, because I modified the second version. If there > are problems with my version, i want to use the official one (SLES 11 > SP1, zypper 1.3.7) without reinstall it. > > So I build my own rpm with a different name of zypper. The Installation > works perfectly and it runs as it shoud. > > The problem are the same configfiles of both versions. Is it possible to > use an other configuration directory for my version? zypper --config /usr/local/etc/myspecialzypper.conf command --options args Please consider reading the fine manual: man zypper, searching for "config" reveals this as the second hit. > > Thanks for your help > > Regards > > Manuel Rieke -- Martin Vidner, YaST developer http://en.opensuse.org/User:Mvidner Kuracke oddeleni v restauraci je jako fekalni oddeleni v bazenu

1 0