[Bug 633504] New: packagekit / kupdateapplet - if a repo has refresh disabled and is unavailable, **no** updates work
https://bugzilla.novell.com/show_bug.cgi?id=633504 https://bugzilla.novell.com/show_bug.cgi?id=633504#c0 Summary: packagekit / kupdateapplet - if a repo has refresh disabled and is unavailable, **no** updates work Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: libzypp AssignedTo: zypp-maintainers@forge.provo.novell.com ReportedBy: jnelson-suse@jamponi.net QAContact: qa@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.8) Gecko/20100723 SUSE/3.6.8-0.1.1 Firefox/3.6.8 I have a number of repos defined, several of which are internal. These internal repositories have refreshed turned *off*. However, when going through packagekit, apparently libzypp ignores this and tries to refresh them anyway. Since they are not always available, this causes a problem and *no* updates come through, rendering the entire "keep my system up to date" process totally broken. 1. libzypp should not try to refresh repos that have refresh set to no. 2. a not-available repository should not cause total packagekit failure. Reproducible: Always Steps to Reproduce: 1. 2. 3. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=633504 https://bugzilla.novell.com/show_bug.cgi?id=633504#c1 --- Comment #1 from Jon Nelson <jnelson-suse@jamponi.net> 2011-03-10 13:35:46 UTC --- Still a problem with openSUSE 11.4 kpackagekit doesn't even let me disable the "origin" (repo) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=633504 https://bugzilla.novell.com/show_bug.cgi?id=633504#c Duncan Mac-Vicar <dmacvicar@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P2 - High CC| |dmacvicar@novell.com -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=633504 https://bugzilla.novell.com/show_bug.cgi?id=633504#c2 --- Comment #2 from Jon Nelson <jnelson-suse@jamponi.net> 2011-03-24 20:11:18 UTC --- ping? packagekit *forcing* a refresh despite refresh being disabled is clearly a bug. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=633504 https://bugzilla.novell.com/show_bug.cgi?id=633504#c3 Michael Andres <ma@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |INVALID --- Comment #3 from Michael Andres <ma@suse.com> 2012-07-06 16:01:26 CEST --- Well, if a repo is enabled it has to be used. If it is not available, it is a failure. Even if auto-refresh is disabled, any application can request a forced refresh and libzypp will also refresh if metadata are not available at all (*e.g. after a 'zypper clean'. If the repos should not be used at all, it has to be disabled. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com