July 2008 - Zypp Development - openSUSE Mailing Lists

[zypp-devel] How to get "zypper" to work in an Autoyast post-install script?
by Wil Decius 22 Jul '08

22 Jul '08

I execute a number of post-install scripts in an AutoYast setup. No problems except for one ... <listentry> <filename>001_REPO_SETUP</filename> <interpreter>shell</interpreter> <source><![CDATA[#!/bin/tcsh cd /etc/zypp mv repos.d repos.d.D mkdir -p repos.d.R ln -sf repos.d.R repos.d /usr/bin/zypper ar -t yast2 http://download.opensuse.org/distribution/11.0/repo/oss/ "OSS" >& tmp.txt ]]></source> </listentry> After install & boot, I see > ls -ald /etc/zypp/repos.d* lrwxrwxrwx 1 root root 15 2008-07-22 08:49 /etc/zypp/repos.d -> repos.d.R/ drwxr-xr-x 2 root root 4096 2008-07-22 08:46 /etc/zypp/repos.d.D/ drwxr-xr-x 2 root root 4096 2008-07-22 08:49 /etc/zypp/repos.d.R/ but, > ls -al /etc/zypp/repos.d/* > shows no repos created. Checking in > cat tmp.txt Specified local path does not exist or is not accessible. @ shell the script works just fine, populating the "repos.d" dir with the new "*.repo" definition file. > ls -al /etc/zypp/repos.d/ > zypper ar -t yast2 http://download.opensuse.org/distribution/11.0/repo/oss/ "OSS" Adding repository 'OSS' [done] Repository 'OSS' successfully added Enabled: Yes Autorefresh: No URI: http://download.opensuse.org/distribution/11.0/repo/oss/ > ls -al /etc/zypp/repos.d/ -rw-r--r-- 1 root root 138 2008-07-22 09:30 OSS.repo Why won't zypper used in the autoyast-script populate the dir? Guess is that something's not ready/installed @ that point in install ... but what? Wil -- To unsubscribe, e-mail: zypp-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: zypp-devel+help(a)opensuse.org

1 1

[zypp-devel] Re: fallback mirrors (was: [opensuse-factory] update-mirrors out of sync - please remove these hazardous sites from the list/redirectors)
by Peter Poeml 21 Jul '08

21 Jul '08

Hi Rajko, I'm posting this followup to the zypp-devel list, since it better fits there than on opensuse-factory. On Fri, Jun 20, 2008 at 12:34:50PM +0200, Peter Poeml wrote: > > Client that can use failover mirrors can have list of mirrors already included > > out of the box, so if redirector is offline in the moment of installation, > > that list can be used. It can be obsolete, but if client has ability to > > switch to another mirror it will find good one in the list. > > Yes, that would be one way to deal with the "Internet gone fishing" or > "Redirector gone fishing" situation during installation. > > Feel free to add it to the wiki page. Thanks for adding this bit to the wiki page. [1] I added the following note about security. ''Moreover, for security reasons it might be more reasonable to preconfigure clients only with one or two "trusted" mirrors, and not with the full list. It might be preferrable to delay updates on the client until the origin server is reachable again, rather than exposing the client to rogue mirrors.'' It is noteworthy that the origin server (download.opensuse.org) does not redirect for metadata and signatures to any mirror, so the clients always get those critical files from the origin site. If clients are using mirrors directly, the tradeoff is that they are less secure. Peter [1] http://en.opensuse.org/Libzypp/Failover -- Contact: admin(a)opensuse.org (a.k.a. ftpadmin(a)suse.com) #opensuse-mirrors on freenode.net Info: http://en.opensuse.org/Mirror_Infrastructure SUSE LINUX Products GmbH Research & Development

1 0

[zypp-devel] Travelling ...
by kkaempf＠suse.de 21 Jul '08

21 Jul '08

>From Monday, July 14th, until Monday, July 21st, I will be on a business travel and not be able to respond to mails in a timely manner. In urgent cases, please call my cell phone. Klaus -- To unsubscribe, e-mail: zypp-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: zypp-devel+help(a)opensuse.org

1 0

[zypp-devel] [Fwd: Re: [softwaremgmt] opensuse updater]
by Thomas Goettlicher 21 Jul '08

21 Jul '08

A happy user wants to thank for the great improvements in the package management. Honor to whom honor is due. -------- Forwarded Message -------- > From: manchette <manchette(a)free.fr> > Hello Thomas, > > By the way, i'm using suse everyday since v. 9.3 and let me tell you > Suse 10.3/11 is the best progress in quality i've seen since then. > I'm amazed and almost sure such an improvement between two versions is > not that common on the market. > Mostly due to the improvement of the package management in yast/zypper > in Suse 11. > openSUSE 11 is now such a delight , so please forward my congratulations > to all the team behind these package management improvements. > > Thanks for what you just said above helps me to understand better the > open suse updater (osu) applet . > The idea of a button calling yast to solve missing dependencies from > the opensuse updater applet seems excellent. > Are you sure all problems are coming from dependencies only ? I had many > times an update problem with firefox for example. > I'm convinced open suse updater is a gigantic idea , specially for > newbies, and it'd be too bad not to polish it so that people continue to > use it, even more now that the update process is so quick with the BIG > plus in package management since 10.3. > > > Fabrice -- To unsubscribe, e-mail: zypp-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: zypp-devel+help(a)opensuse.org

1 0

[zypp-devel] Detecting non-synced repos
by Duncan Mac-Vicar P. 15 Jul '08

15 Jul '08

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I have implemented the basics for feature #301904, which calls for having a way to detect that a repository may be outdated. http://en.opensuse.org/Standards/Rpm_Metadata#Outdated_Metadata_Hint I am citing what I documented there: Joe user has an update repo pointing to a mirror directly (no redirector). The mirror goes out of sync (however it is still reachable). He does not receive any warning, and meanwhile the main repo has lot of updates. The server will have a hint on how often the metadata is regenerated due to a change. The client could detect this and hint the user that the metadata has not been updated since long time. It is responsibility of the server then to update the timestamp of the files if there are no changes in the expire time the repo administrator decided for his own repo. The value is only a hint. The user should be able to disable or alter it. (global in zypp.conf and per repo in the .repo file) Implementation An attribute "expire" is added to repomd section: <repomd expire="100000"> <data type="primary"> <location href="repodata/primary.xml.gz"/> <timestamp>342423423</> Originally in the first proposal, the timestamp was another attribute, but now I calculate it as the newer timestamp of all the resources listed in the repomd.xml file. This enhances zypp::Repository class API as follows: zypp::Date Repository::generatedTimestamp() const; zypp::Date Repository::suggestedExpirationTimestamp() const; bool Repository::maybeOutdated() const; This can be used by applications to check whether a repository is "dead". However we could as well implement easier hooks for applications to receive a report, or signal. The actual implementation is to read the values from repomd.xml and merge them in the .solv file as an extra attributes from the extra non-solvable number -1. (which is tricky, as if there are deltarpms for example, there will be a deltarpm data in position -1, but we don't care as the rpm reader don't look at them ), may be Michael Matz can comment if my approach is ok. And of course, there is a testcase. Any feedback on how to mature this, welcome. Duncan -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iEYEARECAAYFAkh4EMEACgkQzR62qWZ+QtGhpwCgmcugRResmxRlSmcOjGWegtl4 DswAoK+DIcsfuXdovOtziwgND+4Ie18D =+PSa -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: zypp-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: zypp-devel+help(a)opensuse.org

5 5

[zypp-devel] Travelling ...
by kkaempf＠suse.de 14 Jul '08

14 Jul '08

>From Monday, July 14th, until Monday, July 21st, I will be on a business travel and not be able to respond to mails in a timely manner. In urgent cases, please call my cell phone. Klaus -- To unsubscribe, e-mail: zypp-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: zypp-devel+help(a)opensuse.org

1 0

[zypp-devel] new IRC channel #zypp-failover on freenode
by Peter Poeml 14 Jul '08

14 Jul '08

Hi, regarding discussion and work on Gerards GSoC project, Gerard and me thought it would be a good idea to meet on an IRC channel on freenode for it. The #zypp channel is a bit hard to read, with all the automated messages. Feel free to join! Peter -- "WARNING: This bug is visible to non-employees. Please be respectful!" SUSE LINUX Products GmbH Research & Development

2 2

[zypp-devel] packageKit - Feature Matrix
by Lukas Ocilka 11 Jul '08

11 Jul '08

Hi, I've found this link http://www.packagekit.org/pk-matrix.html at http://en.opensuse.org/Feature_Wishlist#Better_Package_Management It compares several packageKit backends and their features. Have a nice day Lukas -- Lukas Ocilka, YaST Developer (xn--luk-gla45d) ----------------------------------------------------------------- Ano, ano. Moudry rozkaz. Sam jsem nemel v tech gratulacich jasno.

1 0

[zypp-devel] Fedora to upgrade RPM to 4.6
by Klaus Kaempf 10 Jul '08

10 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: zypp-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: zypp-devel+help(a)opensuse.org

3 2

[zypp-devel] Re: follow up in managing repositories
by Duncan Mac-Vicar Prett 01 Jul '08

01 Jul '08

Dirk Mueller wrote: > Very interesting idea indeed, and would satisfy all needs I can think of. It > might however cause some headache in case the list flips between two > repositories regularly and the user has to re-approve each GPG key/repo > signature. > Only if the user deleted the keys from the rpm database or did not import them. We don't remove keys when removing a repository (because one key could be used to sign multiple repositories) Duncan -- To unsubscribe, e-mail: zypp-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: zypp-devel+help(a)opensuse.org

1 0