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

Thread: Tumbleweed update

  1. #1
    Join Date
    Aug 2011
    Location
    Monnickendam, The Netherlands
    Posts
    129

    Default Tumbleweed update

    What about this?

    Code:
    Problem: SuSEfirewall2-3.6.378-2.1.noarch conflicts with firewalld provided by firewalld-0.5.1-1.1.noarch
     Solution 1: Following actions will be done:
      deinstallation of firewalld-0.5.1-1.1.noarch
      deinstallation of firewalld-lang-0.5.1-1.1.noarch
     Solution 2: deinstallation of SuSEfirewall2-3.6.378-1.1.noarch
     Solution 3: keep obsolete SuSEfirewall2-3.6.378-1.1.noarch
    The following product is going to be upgraded:
    openSUSE Tumbleweed 20180311-0 -> 20180312-0

  2. #2
    Join Date
    Jan 2018
    Location
    Canada
    Posts
    193

    Default Re: Tumbleweed update

    firewalld has replaced SuSEfirewall2 so select 2, or 3 if you are not sure.

    If you don't use the default configuration you should use yast to set up firewalld, or at least review the settings.

    Use the yast services manager to make sure SuSEfirewall2 services are stopped and disabled, and that firewalld is enabled and started.

    When everything looks good you can use yast to find all SuSEfirewall2 installed packages and remove them.

  3. #3
    Join Date
    Oct 2008
    Location
    Glasgow, Scotland
    Posts
    1,277

    Default Re: Tumbleweed update

    SuSEfirewall2 has become obsolete and replaced with firewalld. Choose option 2.
    --
    slàinte mhath,
    rayH

    ~ knowing the right answer is easier than knowing the right question.

  4. #4
    Join Date
    Aug 2010
    Location
    Chicago suburbs
    Posts
    15,685
    Blog Entries
    3

    Default Re: Tumbleweed update

    I went with option 2 when I saw that. But I know there was a move toward replacing SuSEFirewall2 with firewalld, so it seemed the sensible option.
    openSUSE Leap 15.3; KDE Plasma 5.18.6;

  5. #5
    Join Date
    Aug 2011
    Location
    Monnickendam, The Netherlands
    Posts
    129

    Default Re: Tumbleweed update

    Thanks all, i did not now that.....

    GJ

  6. #6
    Join Date
    Jun 2008
    Location
    UK
    Posts
    5,500

    Default Re: Tumbleweed update

    Quote Originally Posted by GJElde View Post
    What about this?

    Code:
    Problem: SuSEfirewall2-3.6.378-2.1.noarch conflicts with firewalld provided by firewalld-0.5.1-1.1.noarch
     Solution 1: Following actions will be done:
      deinstallation of firewalld-0.5.1-1.1.noarch
      deinstallation of firewalld-lang-0.5.1-1.1.noarch
     Solution 2: deinstallation of SuSEfirewall2-3.6.378-1.1.noarch
     Solution 3: keep obsolete SuSEfirewall2-3.6.378-1.1.noarch
    The following product is going to be upgraded:
    openSUSE Tumbleweed 20180311-0 -> 20180312-0
    It's a bug! See this Factory ML thread refers and the last post from the maintainer of the packages.

    PS. AFAIK they were to be run in parallel.
    Leap 42.3 (ext4, KDE Plasma 5.8.7) ~ stable
    Manjaro (ext4, Xfce) ~ rolling updates
    Tumbleweed (ext4, KDE Plasma5) ~ managed updates via "Tumbleweed Snapshots" service.

  7. #7
    Join Date
    Aug 2010
    Location
    Chicago suburbs
    Posts
    15,685
    Blog Entries
    3

    Default Re: Tumbleweed update

    Quote Originally Posted by consused View Post
    It's a bug!
    It seems to be more an argument than a bug. And the argument is not yet settled.
    openSUSE Leap 15.3; KDE Plasma 5.18.6;

  8. #8

    Default Re: Tumbleweed update

    There are some strnage things going on with the firewall in TW. I don't believe this is all clear in the open what's going on here. You can't have both firewalls running.

    For example firewalld can't be configured from CLI-YaST. Take care to allow all necessary services in firewalld. Otherwise you might end up locked-out (if machine managed headless, had that yesterday...)
    Kind regards

    raspu

  9. #9
    Join Date
    Jun 2008
    Location
    UK
    Posts
    5,500

    Default Re: Tumbleweed update

    Quote Originally Posted by nrickert View Post
    It seems to be more an argument than a bug. And the argument is not yet settled.
    Argument about what exactly? I'll let you worry about that on the ML.

    IMO such conflicts shouldn't present to the user at "zypper dup" time, that is the bug. Whatever results hopefully will be resolved before Leap 15's final release. At least there is a bug report now to focus any arguments or discussions.

    Well "run in parallel" may not be achievable, but parallel availability - yes, at least as mutually exclusive services.
    Leap 42.3 (ext4, KDE Plasma 5.8.7) ~ stable
    Manjaro (ext4, Xfce) ~ rolling updates
    Tumbleweed (ext4, KDE Plasma5) ~ managed updates via "Tumbleweed Snapshots" service.

  10. #10
    Join Date
    Aug 2010
    Location
    Chicago suburbs
    Posts
    15,685
    Blog Entries
    3

    Default Re: Tumbleweed update

    My understanding is that both could be installed, but only one of them could be allowed to run.

    Apparently someone decided that this conflict could be avoided by creating a package conflict (so that only one could be installed). And there seems to be a disagreement as to whether that was an appropriate way to solve the problem.

    This is what I gather from reading the bug report and the mailing list messages.

    Personally, I'm not too much concerned. Since "firewalld" seems to be the proposed future, I just go with that when there's a conflict.
    openSUSE Leap 15.3; KDE Plasma 5.18.6;

Page 1 of 2 12 LastLast

Posting Permissions

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