- openSUSE Software Management

[softwaremgmt] a broad appeal to fix opensuse's package-management's repository/redirector failure & recovery mechasnism
by grantksupport＠operamail.com 02 Oct '14

02 Oct '14

In my experience, package management's routine failure to find/use a 'healthy' repository is a long-standing production problem. I'm requesting a fix. Here's a summary: I run Opensuse 13.1 on numerous machines lsb_release -rd Description: openSUSE 13.1 (Bottle) (x86_64) Release: 13.1 Current count is ~200. The machines are installed at multiple locations around the globe. They're connected to the 'net via a variety of different networks providers. Some of the machines are directly connected to the 'net, some are behind LAN routers, switches & firewalls. Package management for all of the machines is handled exclusively via zypper cli. Each machine has a common core of repositories defined in /etc/zypp/repos.d, and frequently has a number of additional @openSUSE dev (!'home') repos defined. In ALL cases, the default install of repos sets have been installed with the meta-director as baseurl, baseurl=http://download.opensuse.org/... Regular package maintenance consists of zypper clean --all zypper (d)up The maintenance frequency is nominally 1/wk, often 1/dy, and in devs' cases, often more frequent. In virtually ALL cases, the update process regularly fails @ retrieving/refreshing the repos' (meta)data. For example, a typical result is: ... Checking whether to refresh metadata for KDE4-Extra-Unstable Retrieving: repomd.xml .......................................................................................[error] File '/repodata/repomd.xml' not found on medium 'http://download.opensuse.org/repositories/KDE:/Unstable:/Extra/KDE_Current_…' Abort, retry, ignore? [a/r/i/? shows all options] (a): ... This occurs occassionally for any/all repos, whether the standard distribution repos (security, update, etc), core DM (e.g. KDE*) additional repos, or the more 'esoteric' !home OBS-hosted repos (e.g., security:netfilter). The failure rate for overall update/upgrade process attempts is, very roughly, ~15%. The error is NON-recoverable. 'Abort' & 'retry' *never* work. Chats @ IRC re: the issue typically result in the same '(non)responses' : "wait", "works for me", "prove it", etc. The ONLY solution(s) that work are: (1) wait some random amount of time -- typically hours, occassionally days -- until the system magically heals itself, (2) visit the download.opensuse.org link for the repo, click 'details' for a target page, identify a specific working/available repo for the package(s) of interest, and manually edit baseurl= for the problematic repo. Neither is tenable for a reliable operating environment. It is simply unmanageable in either a single, local or widely-distributed environment. (2) is further confounded by the fact that, at any given time, a previously-working, manually-selected repo may, itself, fail, requiring -- yet again -- another manual intervention. Within the scope of our environment, no other distro's package management system has anywhere near the failure rate demonstrated here. (We've ~600+ other machines running a mix of Centos, Fedora, Debian & Ubuntu). This has been occurring for literally years, across multiple openSUSE versions, and remains unaddressed. I know, without any doubt, that others experience similar/frequent failures -- it's been a frequent discussion with our partners, as well as in openSUSE* IRC channels. This needs a fix. As to what, specifically, that fix can/should be -- I'm unclear. If a solution already exists, I'm unaware. One idea -- a fallback mechanism *within* a repos' definition would be useful For example, allow in a given repo's def'n, having multiple, numbered baseurls baseurl1=http://direct/url/to/specific/site/1/... baseurl2=http://direct/url/to/specific/site/2/... baseurl3=http://download.opensuse.org/... ... baseurlN=http://direct/url/to/specific/site/3/... and add fuction to zypper so that for each repo, the baseurls would be tried in order for any given failure. By adding, e.g., a failcount2abort=X to either/both a given repo's defn, or /etc/zypp(er).conf, the overall process could be terminated if there were "X" # of subsequent fails, indicating a likely systemic problem requiring further intervention. I'd appreciate hearing from "those responsible for keeping the redirector & repos working" re: * acknowledgement, or refusal thereof, of the failure issue * clarification as to why it occurs in the first place * ideas/suggestions as to what can/should be done to fix it Thanks. Grant -- To unsubscribe, e-mail: opensuse-softwaremgmt+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-softwaremgmt+owner(a)opensuse.org

2 1

[softwaremgmt] Marketing Jur�dico | Newsletter Inrise Consultoria | Edi��o 31 | Ano 06
by Inrise Consultoria 18 Feb '13

18 Feb '13

1 0

[softwaremgmt] Marketing Jur�dico | Newsletter Inrise Consultoria | Edi��o 27 | Ano 05
by Inrise RH 18 Sep '12

18 Sep '12

1 0

[softwaremgmt] Situation and what's expected/needed for 12.3?
by Cristian Morales Vega 25 Aug '12

25 Aug '12

Software Center, Appstream, Matthias Klumpp GSoC... I'm lost. First, will any of this be provided as an official update for 12.2 or are we aiming to 12.3? Then do we still have some problems with the packagekit zypp backend and zypp itself? (http://lists.opensuse.org/opensuse-factory/2011-11/msg01549.html). Plus it seems there is a need for some changes in the backend with the latest PackageKit (http://blog.tenstral.net/2012/08/appstream-distro-howto.html). Or is Matthias doing that for the zypp backend? So, could somebody please summarize the current situation for openSUSE? If somebody wanted to help, where should he start looking? -- To unsubscribe, e-mail: opensuse-softwaremgmt+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-softwaremgmt+owner(a)opensuse.org

3 8

[softwaremgmt] Makeup mirror suppliers shared photos with you
by Makeup mirror suppliers 21 Jul '12

21 Jul '12

Dear: We have obtained your name and address from internet search,I know you sell fashion and promotion item,and we are writing to inquire whether you would be willing to establish business relations with us. We have been manufacturing promotion gift for many years now.our main products have makeup mirror,cosmetic brush,hair comb/brush,manicure sets, bottle opener,measuring tape etc.At present we are interested in extending our overseas market and would appreciate your respond. Considering our competitive prices and high quality,we expect to establish a long-term partnership With you. We look forward to your early reply. Thanks Best Regards! ------------------------------------ Ike Sale Manager Ningbo Yinzhou Victy Craft Factory

1 0

[softwaremgmt] led display Suppliers shared photos with you
by led display Suppliers 10 Jun '12

10 Jun '12

Dear Mr/Miss, Still be puzzling about looking for best led display supplier? Now it will be miles easier working with KEROSA! Here you can find competitive price and excellent quality with a best mix. We"ve been in led display career for many years. We know your market and your country well. Our business is flexible which something is more likely to be a friend chat. We never waste your time. Our conversation will be very efficient base on our good communication. Please reply as soon as possible .if you are working on some led display project. We are ready to make you a satisfied offer! Samuel Shezhen Krosa Techology Co.,Ltd. Address: Building 3,Park,Guanguang road,Bao"an District,Shenzhen,China. post 518000

1 0

[softwaremgmt] Software Center
by Duncan Mac-Vicar P. 02 Mar '12

02 Mar '12

Hi, I was trying to figure out what is missing to get the software center in a "usable" state now that coolo added the metadata to the repositories. http://en.opensuse.org/openSUSE:GSOC_2011/SoftwareCenter - I copied http://download.opensuse.org/factory/repo/oss/suse/setup/descr/appdata.xml to data/app-stream - installed gnome-packagekit intltool python-distutils-extra po4a python-piston-mini After editing the Gtk css files I can make the app to start. However I have been unable to get this step: ./utils/update-software-center --appstream-only --local to succeed. Anyone has? -- Duncan Mac-Vicar P. - http://www.suse.com/ SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) Maxfeldstraße 5, 90409 Nürnberg, Germany -- To unsubscribe, e-mail: opensuse-softwaremgmt+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-softwaremgmt+owner(a)opensuse.org

2 3

[softwaremgmt] zypper does not "see" packages in repo
by Darin Perusich 23 Feb '12

23 Feb '12

Hello, I wasn't sure which mailing list would best address this but seeing it's zypper related, zypp-devel and softwaremgmt seemed appropriate. I have 2 local yum/rpm-md repositories which I'm using to deploy packages internally at my employer, opensuse 11.3 and 12.1 systems. Both repos have been functioning as expected but after upgrading one system from 11.3 ->12.1 earlier i'm seeing some odd behavior. When I add new packages to the 12.1 repo, update it with createrepo, and run zypper refresh the new packages are not viable and I can't install/list/search those package. On the repo server I've removed the repodata files and reran createrepo to regenerate them. All files have 0644 permissions and the dirs' 755, all owned by root, I can browser to and download the w/a browser fine. On the client I've removed all the repos and added only this one. I've unset my http_proxy values so zypper makes a direct connection to the server. I've run "zypper clean -a" to purge the cache as well as removed the raw files under /var/cache/zypp/{packages,raw,solv}/. Also the /var/cache/zypp/raw/local-repo/repodata/ *primary.xml.gz doesn't contain any entry for new packages I've added. I'm totally at a loose as to what's happening here, any thoughts on where to look next? -- Later, Darin -- To unsubscribe, e-mail: opensuse-softwaremgmt+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-softwaremgmt+owner(a)opensuse.org

1 0

[softwaremgmt] Updating openSUSE 11.4 killed the network
by Paulo Motta 26 May '11

26 May '11

Hi All, yesterday I was updating my LiveUSB openSUSE 11.4 and network stopped working, does anybody had this issue ? it happened both on 32 and 64 bits versions and I am using KDE. thanks in advance -- Paulo Motta -- "Qualquer tecnologia suficientemente avançada é indistinguível da mágica" - Arthur C. Clarke -- To unsubscribe, e-mail: opensuse-softwaremgmt+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-softwaremgmt+help(a)opensuse.org

2 1

[softwaremgmt] satsolver-bindings now separate from libsatsolver
by Klaus Kaempf 02 Feb '11

02 Feb '11

Hi, to provide better support for bindings to the satsolver library, the application layer library and the bindings have been split off from libsatsolver. The new repository location for sat-solver-bindings is at git://gitorious.org/opensuse/sat-solver-bindings.git libsatsolver itself remains at git://gitorious.org/opensuse/sat-solver.git There are no changes to functionality or package contents. This split allows to update and maintain the bindings seperately from satsolver and to provide better bindings on older distributions. This will allow us to better support users of satsolver-bindings like Kiwi and MeeGo (through libzypp bindings) across a range of distributions. 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