- openSUSE Software Management

[softwaremgmt] Fedora to upgrade RPM to 4.6
by Klaus Kaempf 09 Jul '08

09 Jul '08

Announcement: https://www.redhat.com/archives/fedora-devel-list/2008-July/msg00477.html Full changelog: http://wiki.rpm.org/Releases/4.5.90 Most interesting change from our POV: - %{_topdir} now defaults to $(HOME)/rpmbuild/, /usr/src/redhat/ is no more. - Rpm now supports "arch dependencies", so eg. foo-devel dependencies can be expressed correctly. Please wait for FPC recommendations on the subject, this needs a mass rebuild to be usable. - Rpm now collects pkg-config and libtool dependencies automatically. Initially only provides will be created to avoid creating unsolvable dependencies though. Klaus --- SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-softwaremgmt+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-softwaremgmt+help(a)opensuse.org

1 0

Re: [softwaremgmt] How /etc/zypp/vendors.d works?
by Stefan Schubert 08 Jul '08

08 Jul '08

Funny, Klaus Kaempf has had almost the same request. So I have added: ## ## Defining directory for equivalent vendors ## ## One file in this directory reflects a group of equivalent vendors. e.G.: ## e.G. (filename is "nvidia" but could be any other name): ## ------------------------- file contains begin ----------------------- ## [main] ## ## vendors = nvidia,suse,opensuse ## ## ------------------------- file contains end ----------------------- ## Libzypp makes an string comparision whereas the beginning of the ## strings are compared only. e.G. vendor "opensuse11.0" is compatible to "opensuse". ## ## Valid values: A directory ## Default value: {configdir}/vendors.d ## # vendordir = /etc/zypp/vendors.d Christian Morales Vega schrieb: > 2008/7/8 Stefan Schubert <schubi(a)suse.de <mailto:schubi@suse.de>>: > > Christian Morales Vega schrieb: > > From my installed Packman packages, some use vedor string > > "http://packman.links2linux.de", some use > "packman.links2linux.de <http://packman.links2linux.de>", > > and one of them uses "Packman". Recently an update changed the > vendor > > from "http://packman.links2linux.de" to "packman.links2linux.de > <http://packman.links2linux.de>" and > > so zypper up -t package didn't see it. > > In /etc/zypp/zypp.conf can be read: > > ## > > ## Defining directory for equivalent vendors > > ## > > ## Valid values: A directory > > ## Default value: {configdir}/vendors.d > > ## > > # vendordir = /etc/zypp/vendors.d > > > > So, can I make libzypp interpret the three string like a single > > vendor? If so, how? I create the vendors.d dir (since the rpm > package > > doesn't) and... what I'm exactly supposed to put inside it? > > > Yes, that's a good question about a bad ducumentation. I have > added some > comments: > > ## > ## Defining directory for equivalent vendors > ## > ## One file in this directory reflects a group of equivalent > vendors. e.G.: > ## e.G. (filename = nvidia): > ## ------------------------- file contains begin > ----------------------- > ## [main] > ## > ## vendors = nvidia,suse,opensuse > ## > ## ------------------------- file contains end ----------------------- > ## > ## Valid values: A directory > ## Default value: {configdir}/vendors.d > ## > # vendordir = /etc/zypp/vendors.d > > Now is clearer, thanks. But, the comma separated strings must be the > full vendor string? > If a vendor is "Star Trek films" and another vendor is "Star Wars > films". A vendors file with "vendors = Star Trek,Star Wars" whould > make both vendors equivalents, or I need to use "vendors = Star Trek > films,Star Wars films"? > I ask because official packages use "SUSE LINUX Products GmbH, > Nuernberg, Germany". Since this vendor string has commas... there is > some way to make another vendor equivalent to the official one? > > > > Between, is /etc/zypp/zypp.conf updated? I though patchrpm were not > > used anymore, but zypp.conf still contains a "download.use_patchrpm" > > example. > > > Hm, there is some code in libzypp which asks for this flag. > mls, ma should know if it is still supported. As far I know it is not > supported anymore. > > I only asked in case the file was outdated and the vendors.d function > wasn't available anymore. Isn't really important. > -- ******************************************************************************* Stefan Schubert SUSE LINUX GmbH - Maxfeldstrasse 5 - D-90409 Nuernberg, Germany e-mail: schubi(a)suse.de ------------------------------------------------------------------------------- SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-softwaremgmt+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-softwaremgmt+help(a)opensuse.org

1 0

[softwaremgmt] How /etc/zypp/vendors.d works?
by Christian Morales Vega 08 Jul '08

08 Jul '08

>From my installed Packman packages, some use vedor string "http://packman.links2linux.de", some use "packman.links2linux.de", and one of them uses "Packman". Recently an update changed the vendor from "http://packman.links2linux.de" to "packman.links2linux.de" and so zypper up -t package didn't see it. In /etc/zypp/zypp.conf can be read: ## ## Defining directory for equivalent vendors ## ## Valid values: A directory ## Default value: {configdir}/vendors.d ## # vendordir = /etc/zypp/vendors.d So, can I make libzypp interpret the three string like a single vendor? If so, how? I create the vendors.d dir (since the rpm package doesn't) and... what I'm exactly supposed to put inside it? Between, is /etc/zypp/zypp.conf updated? I though patchrpm were not used anymore, but zypp.conf still contains a "download.use_patchrpm" example. -- To unsubscribe, e-mail: opensuse-softwaremgmt+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-softwaremgmt+help(a)opensuse.org

2 1

[softwaremgmt] zypper dup ignores repo priorities, it's supposed to do so?
by Christian Morales Vega 26 Jun '08

26 Jun '08

$ grep -H prio /etc/zypp/repos.d/* | sort -n -t = -k 2 /etc/zypp/repos.d/home_RedDwarf.repo:priority=1 /etc/zypp/repos.d/nvidia.repo:priority=10 /etc/zypp/repos.d/openSUSE_Tools.repo:priority=20 /etc/zypp/repos.d/openSUSE-11.0-Updates.repo:priority=50 /etc/zypp/repos.d/openSUSE-DVD 11.0.repo:priority=50 /etc/zypp/repos.d/repo-debug.repo:priority=50 /etc/zypp/repos.d/repo-non-oss.repo:priority=50 /etc/zypp/repos.d/repo-oss.repo:priority=50 /etc/zypp/repos.d/education.repo:priority=70 /etc/zypp/repos.d/games.repo:priority=70 /etc/zypp/repos.d/packman.repo:priority=90 I have wormux-0.8-1.7 from games and SDL_gfx-2.0.16-138.1 from repo-oss installed. A zypper up -t package wants to update wormux to wormux-0.8-1.8, good. But zypper dup wants to update both wormux and SDL_gfx to SDL_gfx-2.0.17-2.1. So zypper dup ignores repository priorities. Bug or expected behavior? -- To unsubscribe, e-mail: opensuse-softwaremgmt+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-softwaremgmt+help(a)opensuse.org

1 0

[softwaremgmt] OneClickInstall ymp sample
by Jinu Mathew Joy 24 Jun '08

24 Jun '08

Hi, I am trying out the OneClickInstall feature available in OpenSUSE 11.0. I wanted to try out OCI by writing a ymp configuration to install a given package from a ZYPP source available in our network. Lets say I want an OCI conf to install the package 'zoo' (http://dist.blr.novell.com/opensuse11/RC4/i386/suse/i586/zoo-2.10-975.1.i58…) available on the zypp repo "http://dist.blr.novell.com/opensuse11/RC4/i386/". Can I get a sample ymp to get the 'zoo' package installed using OCI ? Thanks, -Jinu -- To unsubscribe, e-mail: opensuse-softwaremgmt+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-softwaremgmt+help(a)opensuse.org

2 2

[softwaremgmt] One Click Install for more distros
by Martin Vidner 21 May '08

21 May '08

Hi people, on Fosscamp, Michael of Ubuntu wondered if we could have a standardized one click installation that upstream authors and ISVs could use regardless of the distribution. I understood that currently Ubuntu/Debian have only "apt URLs"[1] that look like apt:mutt apt:mutt?section=universe Following the principle that simple things should be simple, I tried a minimal ymp file to mimic "apt:mutt": <metapackage xmlns="http://opensuse.org/Standards/One_Click_Install"> <group> <software> <item> <name>mutt</name> </item> </software> </group> </metapackage> $ /sbin/OneClickInstallUI `pwd`/mutt.ymp (In 11.0 B3 it makes yast complain about missing widgets, because of the missing repositories section, but eventually it installs mutt fine) The Standards page[2] is outdated, the ISV page[3] seems to have an up-to-date specification of the format. We already talked about the general idea 2 months ago: [4] [1] http://tombuntu.com/index.php/2007/10/22/the-apturl-protocol-handler-in-ubu… [2] http://en.opensuse.org/Standards/One_Click_Install [3] http://en.opensuse.org/One_Click_Install/ISV [4] http://lists.opensuse.org/opensuse-softwaremgmt/2008-03/msg00000.html -- Martin Vidner, YaST developer http://en.opensuse.org/User:Mvidner Kuracke oddeleni v restauraci je jako fekalni oddeleni v bazenu -- 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: zypper questions (alias vs. name and other issues)
by Jan Kupec 16 Apr '08

16 Apr '08

i'm forwarding answers to some zypper question as they seem to be FAQ. I'll put some of them to man page/wiki, but some point to issues that need to be fixed. Frank Sundermeyer wrote: > Hi Jan, > > I am maintaining the zypper chapter for the openSUSE 11.0 manual. There > are some things I haven't fully understood and I hope you can help me. sure :O) > I am using 11.0 Alpha 3+ with zypper 0.10.5. > > > If I add > > http://download.opensuse.org/distribution/SL-OSS-factory/inst-source/ > (Main Repository (OSS)) > > with _YaST_ (via Software Repositories -> Community Repositories) it > shows up like this (shortened the URl): > > bourbaki:~ # zypper repos > # | Ena | Ref |Type | Alias | Name > --+-----+-----+-------+--------------------------+-------------------- > 1 | Yes | Yes | yast2 | openSUSE-DVD 11.0 | openSUSE-DVD 11.0 > 2 | Yes | Yes | yast2 | http://.../inst-source/ | Main Repository (OSS) > > > 1. Question: What exactly is the "Name"? Why is the URl listed under > Alias? Alias is both a shorthand for Name and a unique identifier of the repository. While Alias is not exposed to the user by YaST (there's no need to), it is used in zypper in the repository handling commands and in --repo option as one way to specify the repository (the other two way are by number in the 'zypper repos' list and by URI. YaST currently internally uses URI as the Alias which is a bit unfortunate and creates confusion for zypper newbies. I'll ask YaST folks to use something different instead (e.g. "repoX" where X would be a unique number). > If I delete this very repository by URl > > bourbaki:~ # zypper rr > http://download.opensuse.org/distribution/SL-OSS-factory/inst-source/ > * Removing repository 'Main Repository (OSS)' > Repository 'Main Repository (OSS)' has been removed. > > everything is fine. <cut> > If I manually add the same repository from above with > > bourbaki:~ # zypper ar > http://download.opensuse.org/distribution/SL-OSS-factory/inst-source/ "foobar" > * Adding repository 'foobar' > Repository 'foobar' successfully added > Enabled: Yes > Autorefresh: No > URL: > http://download.opensuse.org/distribution/SL-OSS-factory/inst-source/ > > It shows up quite differently: > > bourbaki:~ # zypper repos > # | Enabled | Refresh | Type | Alias | Name > --+---------+---------+-------+-------------------+------------------ > 1 | Yes | Yes | yast2 | openSUSE-DVD 11.0 | openSUSE-DVD 11.0 > 2 | Yes | No | NONE | foobar | foobar Yes, zypper currently has no way to specify the Name when adding repository (except for adding it via a .repo file) and when no Name is known, the alias is shown instead of it. The Alias is always required. > hmm. If I > > bourbaki:~ # zypper ar --check > http://download.opensuse.org/repositories/home:/thomas-schraitle/openSUSE_F… > toms > * Adding repository 'toms' > Repository 'toms' successfully added > Enabled: Yes > Autorefresh: No > URL: > http://download.opensuse.org/repositories/home:/thomas-schraitle/openSUSE_F… > > bourbaki:~ # zypper repos > # | Enabled | Refresh | Type | Alias | Name > --+---------+---------+--------+-------------------+------------------ > 1 | Yes | Yes | yast2 | openSUSE-DVD 11.0 | openSUSE-DVD 11.0 > 2 | Yes | No | rpm-md | toms | toms > > the official name of the Repository is _not_ used, although it is > specified in > http://download.opensuse.org/repositories/home:/thomas-schraitle/openSUSE_F…: > > [home_thomas-schraitle] > name=Thomas Schraitle's Home Project (openSUSE_Factory) AFAIK, placement of .repo files to the reporitory root has not (yet) been established as a standard. Zypper can't just detect them and take whatever name it can get from them. If it's not a standard, people are free to put any .repo files in their repos. However it would be a good idea to support this! Any opinions/information from the software management people? > 3. Questions: > Alias and Name are the same - is this a bug? What exactly is "Name"? See above. > How can I turn on Autorefresh with zypper? zypper modifyrepo --refresh <alias|#|URI> > How do I determine a repository's URl? old way: 'zypper -v repos' I recently changed this (for zypper 0.11.1), see zypper help repos. new way: 'zypper repos -u' or 'zypper repos -d' > Should'nt zypper be able to determine the repository type > automatically? (it is listed as NONE since I did not specified it > with "-t yast2") Yes but it depends on what you want. You can tell zypper to 'probe' repository when adding it, but you can also add it without accessing the internet at all. You decide either by editing /etc/zypp/zypp.conf (see 'repo.add.probe' item; affects also YaST) or by specifying --check or --no-check option to the addrepo command. If the repository is not probed or checked when adding it, it will get probed when you will try to use it for the first time (with some other command like refresh or install). Then, if the type of the repository is figured out, it will get stored and you will see the type in the repo list. (Note however that the 'plaindir' can be automatically figured out, if you want to use it, you have to use --type plaindir). BTW i noticed we use --nocheck instead of --no-check. I'll correct that to be consistent with other boolean options. (already done). > However removing with zypper rr by URl _and_ Alias works, when the > repositoty is added with zypper and not by YaST. It should work for both. <cut> > (YaST adds an "_1" to an already existing alias but hides this from the > user (the "_1" is not shown in the Configured Software repositories > Overview) - this is IMHO a very bad solution) I'm not sure.. YaST users should not care what alias has been used. As for notifying the user about adding the very same repo twice, we need to invent another means to do this. We are already thinking of this. > Terminology: When adding a repository with zypper, I need to specify > * URl > * Alias > when adding a repository with YaST, I need to specify > * Repository name (actually the alias) No no, it really is the Name in this case! The Name is whathever you want to name it. Alias is used only internally by YaST. > * URl > > 5. Question: Is it possible to use the same terms in YaST and zypper? Hmm.. i don't know. For zypper as a command line tool the alias is a means to manipulate the repos. YaST users manipulate them by clicking in the GUI. Name servers in both YaST and zypper as an arbitrary/descriptive string for the user. It is just a label, has no other meaning. > 6. More questions: > How do I specify URls to cd, dvd, network sources, local directory? > Neither the man page nor zypper's help output provide any hints Hm.. thanx for pointing this out. I will document it both in man page and the wiki. For now, see http://en.opensuse.org/Libzypp/API/Url. Cheers, jano see also: https://bugzilla.novell.com/show_bug.cgi?id=373167 https://bugzilla.novell.com/show_bug.cgi?id=364391 -- To unsubscribe, e-mail: opensuse-softwaremgmt+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-softwaremgmt+help(a)opensuse.org

1 0

[softwaremgmt] ymp files on the command line?
by Lars Behrens 14 Apr '08

14 Apr '08

Hi there, anyone knowing of a way to use ymp-files on the commandline? Couldn't find something on the net... As I have a bunch of clients here, it would be great if I could use one-click-install via script. Cheerz, Lars -- To unsubscribe, e-mail: opensuse-softwaremgmt+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-softwaremgmt+help(a)opensuse.org

5 8

[softwaremgmt] makedeltarpm makes large deltas
by polk ghusegh 07 Apr '08

07 Apr '08

I see that to keep up to date with factory I am required to download >1GB on each new sync. I pay for bandwidth so I wanted to create some delta rpms on a weekly basis on a server I have access to which has no bandwidth restrictions (which I could sync to factory). I then planned to update my system from that deltarpm server on a weekly basis for, I would guess, a few 100 MBs at most. My problem is that for example makedeltarpm -vv mozilla-xulrunner181-1.8.1.12-4.x86_64.rpm mozilla-xulrunner190-1.8.99.5-2.x86_64.rpm mozilla-xulrunner.delta yields a delta with around the same size as the rpms. This is true for all those I tried, am I misusing the makedeltarpm program or is this expected, or is this the result of the transition to lzma compression for factory rpms? I am running from the 11.0 alpha3 64bit CD with some packages updated to factory (eg, zypper, yast), deltarpm = 3.4 ____________________________________________________________________________________ You rock. That's why Blockbuster's offering you one month of Blockbuster Total Access, No Cost. http://tc.deals.yahoo.com/tc/blockbuster/text5.com -- To unsubscribe, e-mail: opensuse-softwaremgmt+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-softwaremgmt+help(a)opensuse.org

3 2

[softwaremgmt] YMP for other distributions.
by Benji Weber 26 Mar '08

26 Mar '08

Greetings All, I recently noticed that an Ubuntu specification ThirdPartyApt[0] very similar to YMP[1]. I have since contacted the specification authors - Jerome Haltom and Scott Ritchie to enquire about the possibility of cooperating and using the same file format. Both were been interested in this possibility. Hopefully they will be subscribed to this list now. Using the same file format would make things easier for ISVs as they can write one instructions file which will do the "right thing" whichever distribution the user is using, and also do not need to learn multiple formats for doing exactly the same thing. Almost all information that can be defined in a .apt file can be defined in a .ymp (the opposite is not the case). The main difference in the proposed .apt specification is the handling of keys. It was proposed that .apt files were signed with the same key as the repository. I do not see this adds any security, and it does prevent some of the benefits we've seen with YMP by limiting its use to only the original software vendor. - Third party web based software catalogues - Reducing the length of How-Tos/Tutorials by removing complex package management instructions. - Creating YMPs for ISV packages when they are not interested in working with you to create their own (e.g. skype) Would not be possible. YMP already provides the flexibility to specify instructions for different distributions in one file. One can specify something like: <group distversion="openSUSE 10.3">...</group> <group distversion="Ubuntu 8.04">...</group> Packman[2] already make use of this to specify instructions for both openSUSE 10.3 and 10.2 in one file. There is a proof of concept implementation of a YMP client implementation for Ubuntu by one of the klik team. Video[3] Source[4]. In order to ensure that YMP can be used by Ubuntu and other distributions it may be possible to make some minor changes to the specification. At present it is possible to make minor changes without breaking backwards compatibility with 10.3. However, as more people start implementing the specification this will likely become impossible, so we should nail down any changes that are required now. Another thing to consider is whether we require a method of versioning the YMP file, incase we need to make more significant changes in the future. In terms of the data required for the mechanism to function, the only data that must be specified in a YMP file at present are: - Repository URLs - Package names The key question is whether we can specify enough information in a YMP yet to uniquely identify a Debian repository. At present one can supply the URL of the repository, and optionally: - An uri of the product within the repository to use. - The format of the repository. e.g. minimally <repository> <url>http://example.com</url> Maximally <repository recommended="true" format="yast" producturi="someaddon"> <url>http://example.com</url> Is there more information required to identify any Debian repository? Another point to consider if others implement the specification is we can no longer assume that a <group> with no distversion specified is intended for openSUSE, if other distributions implement ths specification. This means that the buildservice generated YMPs etc will have to explicitly specify the distribution they are intended for. Perhaps we could define some fallback generic distversions like "rpm" or "lsb desktop 3". There is also the question of how to distribute the public key for a debian repository. As I understand it debian repositories do not normally contain the public key as in most openSUSE repositories[5]. The .apt format proposal has the public key included in the file. This is one possibility, although in my opinion it would be better to have it available in the repositories like openSUSE, this would allow other mechanisms for adding the repository to locate the key as well. Bear in mind that one of the requirements is to keep the file format as simple as possible, the less information that is mandatory in the file the better. While we're contemplating modifications to the format I would like to add an optional "version" attribute to the software item tag. This was really only left out as an oversight and is necessary to ensure that the version of the software the user wanted is actually the one he or she gets. There is a bug report open that this is required for. Is there any other information that might be required to uniquely identify a package? Perhaps the vendor?. So - to Scott and Jerome, could you review the two specifications and point out any information you require which can not be specified with YMP. Most importantly whether repositories can be uniquely identified. It would be great to have comments,advice,and discussion from others as well. It would be best to identify problems as soon as possible. __ [0] https://wiki.ubuntu.com/ThirdPartyApt [1] http://en.opensuse.org/Standards/One_Click_Install [2] http://packman.links2linux.de [3] http://video.google.de/videoplay?docid=494315634277751745 [4] http://code.google.com/p/klikclient/source/ (ympclient subdirectory) [5] http://en.opensuse.org/Secure_Installation_Sources#The_.22repomd.22_or_.22Y… -- Benjamin Weber -- To unsubscribe, e-mail: opensuse-softwaremgmt+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-softwaremgmt+help(a)opensuse.org

3 3