Page 1 of 2 12 LastLast
Results 1 to 10 of 15

Thread: Critical zypper bug

  1. #1

    Angry Critical zypper bug

    I don't know why but sometimes zypper (v1.4.5) removes some of the installed packages before upgrading them. Actually it removes it even before downloading a newer version. I just wonder what a stupid ****** implemented this behavior. I wish something awful happens to him.
    An hour ago I tried to update few packages, among those were sysconfig, firefox and yast. Guess what? Zypper removed those before downloading newer versions. Due to a temporary network connection loss zypper could not download packages and quit leaving me without firefox, without yast and, what's even worse, without sysconfig package which contains essential system scripts such as ifup, ifdown etc (so my network went down completely without a possibility to restore). It's a big luck there was no new package of rpm (or it would be removed by zypper too) so I could just download those packages with my second PC and reinstall them from a memory stick.
    Now I'm interested where should I file this bug, because without a doubt it's a critical one.

  2. #2
    Join Date
    Aug 2008
    Location
    Seattle, WA
    Posts
    1,376

    Default Re: Critical zypper bug

    It may actually be by design, but the place to report is

    https://bugzilla.novell.com/index.cgi

  3. #3
    Kevin Miller NNTP User

    Default Re: Critical zypper bug

    On 09/07/2010 12:36 PM, chief sealth wrote:
    >
    > It may actually be by design, but the place to report is
    >
    > https://bugzilla.novell.com/index.cgi


    This came up when 11.2 came out (maybe earlier?). Long story short,
    there is an option in sysconfig to download all before
    patching/replacing in case something goes wonky. I don't remember where
    it is exactly but it's been something I've been meaning to enable, just
    haven't gotten around to it yet.

    Don't know why it's not the default behavior.

    ....Kevin
    --
    Kevin Miller - http://www.alaska.net/~atftb
    Juneau, Alaska
    In a recent survey, 7 out of 10 hard drives preferred Linux
    Registered Linux User No: 307357, http://counter.li.org

  4. #4
    Join Date
    Jan 2009
    Location
    43.009 N, 73.172 W
    Posts
    189

    Default Re: Critical zypper bug

    Quote Originally Posted by chief_sealth View Post
    It may actually be by design, but the place to report is
    I can't, for the life of me, understand why that behavior would be by design. If so, the design is flawed.

  5. #5
    Chris Maaskant NNTP User

    Default Re: Critical zypper bug

    Kevin Miller wrote:

    > This came up when 11.2 came out (maybe earlier?). Long story short,
    > there is an option in sysconfig to download all before
    > patching/replacing in case something goes wonky. I don't remember where
    > it is exactly but it's been something I've been meaning to enable, just
    > haven't gotten around to it yet.


    You can configure this in /etc/zypp/zypp.conf
    I have it set like this:

    ## Commit download policy to use as default.
    ##
    ## DownloadOnly, Just download all packages to the local cache.
    ## Do not install. Implies a dry-run.
    ##
    ## DownloadInAdvance, First download all packages to the local cache.
    ## Then start to install.
    ##
    ## DownloadInHeaps, Similar to DownloadInAdvance, but try to split
    ## the transaction into heaps, where at the end of
    ## each heap a consistent system state is reached.
    ##
    ## DownloadAsNeeded Alternating download and install. Packages are
    ## cached just to avid CD/DVD hopping. This is the
    ## traditional behaviour.
    ##
    ## <UNSET> If a value is not set, empty or unknown, we pick
    ## some sane default.
    ##
    commit.downloadMode = DownloadInAdvance

    --
    Chris Maaskant

  6. #6
    Join Date
    Aug 2008
    Location
    Seattle, WA
    Posts
    1,376

    Default Re: Critical zypper bug

    Try editing '/etc/zypp/zypp.conf' and set

    commit.downloadMode = DownloadInAdvance

    This should set zypper to download all packages before installing them.

  7. #7
    Kevin Miller NNTP User

    Default Re: Critical zypper bug

    On 09/07/2010 01:36 PM, Chris Maaskant wrote:
    > Kevin Miller wrote:
    >
    >> This came up when 11.2 came out (maybe earlier?). Long story short,
    >> there is an option in sysconfig to download all before
    >> patching/replacing in case something goes wonky. I don't remember where
    >> it is exactly but it's been something I've been meaning to enable, just
    >> haven't gotten around to it yet.

    >
    > You can configure this in /etc/zypp/zypp.conf
    > I have it set like this:


    snip

    Thanks - that's the one. I just changed mine...

    --
    Kevin Miller - http://www.alaska.net/~atftb
    Juneau, Alaska
    In a recent survey, 7 out of 10 hard drives preferred Linux
    Registered Linux User No: 307357, http://counter.li.org

  8. #8

    Default Re: Critical zypper bug

    Quote Originally Posted by Chris Maaskant View Post
    ## Commit download policy to use as default.
    ##
    ## DownloadOnly, Just download all packages to the local cache.
    ## Do not install. Implies a dry-run.
    ##
    ## DownloadInAdvance, First download all packages to the local cache.
    ## Then start to install.
    ##
    ## DownloadInHeaps, Similar to DownloadInAdvance, but try to split
    ## the transaction into heaps, where at the end of
    ## each heap a consistent system state is reached.
    ##
    ## DownloadAsNeeded Alternating download and install. Packages are
    ## cached just to avid CD/DVD hopping. This is the
    ## traditional behaviour.
    Notice none of them is "removes it even before downloading a newer version".

  9. #9
    Join Date
    Jul 2009
    Location
    Rockyford Alberta Canada
    Posts
    1,362

    Default Re: Critical zypper bug

    Oops! The writer of the zypper code missed a few lesson plans, failed check and balances 101 which states that "Never presume that a prior stage has completed successfully until it has been checked". If the installation can't proceed until the old has been removed, a good programming practice is to rename or move the old someplace safe so there is a copy that can be restored. We are talking a live system here!
    When your up to your a** in Alligators it's pretty hard to remember you intended to drain the swamp (author unknown)

  10. #10

    Default Re: Critical zypper bug

    Please report bug on bugzilla (ensure that it is not already reported), thanks!

Page 1 of 2 12 LastLast

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •