September 2020 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1175967] zypper dup from Tumbleweed 20200824 -> 20200826 fails
by bugzilla_noreply＠suse.com 01 Sep '20

01 Sep '20

https://bugzilla.suse.com/show_bug.cgi?id=1175967 https://bugzilla.suse.com/show_bug.cgi?id=1175967#c12 --- Comment #12 from Benjamin Zeller <bzeller(a)suse.com> --- (In reply to Fabian Vogt from comment #11) > 2020-08-27 14:19:07 <1> linux-xkgz(10495) [libsolv] PoolImpl.cc(logSat):125 > job: install rpm.i586 > 2020-08-27 14:19:07 <1> linux-xkgz(10495) [libsolv] PoolImpl.cc(logSat):125 > - job Rule #98281: > 2020-08-27 14:19:07 <1> linux-xkgz(10495) [libsolv] PoolImpl.cc(logSat):125 > rpm-4.14.2.1-5.1.i586 [4294] (w1) > 2020-08-27 14:19:07 <1> linux-xkgz(10495) [libsolv] PoolImpl.cc(logSat):125 > rpm-4.15.1-6.2.i586 [84879] (w2) > 2020-08-27 14:19:07 <1> linux-xkgz(10495) [libsolv] PoolImpl.cc(logSat):125 > rpm-4.14.2.1-5.1.i586 [119820]I > > That looks a bit suspicious to me, maybe a lock? I actually have the same in my dup (leap in that case) logs, seems that rule is injected to make sure rpm stays on the system: 2020-08-25 09:37:04 <1> linux-2ggq(4238) [libsolv] PoolImpl.cc(logSat):125 - job Rule #90752: 2020-08-25 09:37:04 <1> linux-2ggq(4238) [libsolv] PoolImpl.cc(logSat):125 rpm-4.14.1-lp152.17.5.x86_64 [54810] (w1) 2020-08-25 09:37:04 <1> linux-2ggq(4238) [libsolv] PoolImpl.cc(logSat):125 rpm-4.14.1-lp152.17.5.x86_64 [84582]I (w2) This would be a example for a lock (keyword erase): 2020-08-25 09:37:04 <1> linux-2ggq.suse(4238) [libsolv] PoolImpl.cc(logSat):125 job: erase texlive-afm2pl-bin-debuginfo-2017.20170520.svn44143-lp152.15.2.x86_64 2020-08-25 09:37:04 <1> linux-2ggq.suse(4238) [libsolv] PoolImpl.cc(logSat):125 - job Rule #90753: 2020-08-25 09:37:04 <1> linux-2ggq.suse(4238) [libsolv] PoolImpl.cc(logSat):125 !texlive-afm2pl-bin-debuginfo-2017.20170520.svn44143-lp152.15.2.x86_64 [24111] (w1) -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1175967] zypper dup from Tumbleweed 20200824 -> 20200826 fails
by bugzilla_noreply＠suse.com 01 Sep '20

01 Sep '20

https://bugzilla.suse.com/show_bug.cgi?id=1175967 https://bugzilla.suse.com/show_bug.cgi?id=1175967#c11 --- Comment #11 from Fabian Vogt <fvogt(a)suse.com> --- (In reply to Benjamin Zeller from comment #9) > From you log I was not able to see anything that would hold back rpm from > being installed. But you sure have a lot of orphaned packages in that dup > run. Did you recently remove any older repositories that maybe could'Ve > messed up dependencies? Those orphans are probably because of the full rebuild. > I just did a upgrade of my laptop system from 20200314-0 -> 20200829-0 which > also did run through without any issues, so it does not seem to be a general > issue. > > We can leave the bug open until next week Michael comes back, maybe he has a > idea what could've caused this. 2020-08-27 14:19:07 <1> linux-xkgz(10495) [libsolv] PoolImpl.cc(logSat):125 job: install rpm.i586 2020-08-27 14:19:07 <1> linux-xkgz(10495) [libsolv] PoolImpl.cc(logSat):125 - job Rule #98281: 2020-08-27 14:19:07 <1> linux-xkgz(10495) [libsolv] PoolImpl.cc(logSat):125 rpm-4.14.2.1-5.1.i586 [4294] (w1) 2020-08-27 14:19:07 <1> linux-xkgz(10495) [libsolv] PoolImpl.cc(logSat):125 rpm-4.15.1-6.2.i586 [84879] (w2) 2020-08-27 14:19:07 <1> linux-xkgz(10495) [libsolv] PoolImpl.cc(logSat):125 rpm-4.14.2.1-5.1.i586 [119820]I That looks a bit suspicious to me, maybe a lock? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1175967] zypper dup from Tumbleweed 20200824 -> 20200826 fails
by bugzilla_noreply＠suse.com 01 Sep '20

01 Sep '20

https://bugzilla.suse.com/show_bug.cgi?id=1175967 https://bugzilla.suse.com/show_bug.cgi?id=1175967#c10 --- Comment #10 from Benjamin Zeller <bzeller(a)suse.com> --- I wonder, did you install this machine maybe recently from a really old iso file? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1175967] zypper dup from Tumbleweed 20200824 -> 20200826 fails
by bugzilla_noreply＠suse.com 01 Sep '20

01 Sep '20

https://bugzilla.suse.com/show_bug.cgi?id=1175967 https://bugzilla.suse.com/show_bug.cgi?id=1175967#c9 Benjamin Zeller <bzeller(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ma(a)suse.com Flags| |needinfo?(ma(a)suse.com) --- Comment #9 from Benjamin Zeller <bzeller(a)suse.com> --- >From you log I was not able to see anything that would hold back rpm from being installed. But you sure have a lot of orphaned packages in that dup run. Did you recently remove any older repositories that maybe could'Ve messed up dependencies? I just did a upgrade of my laptop system from 20200314-0 -> 20200829-0 which also did run through without any issues, so it does not seem to be a general issue. We can leave the bug open until next week Michael comes back, maybe he has a idea what could've caused this. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1175268] [glibc2.32] kbuild build failure
by bugzilla_noreply＠suse.com 01 Sep '20

01 Sep '20

https://bugzilla.suse.com/show_bug.cgi?id=1175268 Dirk Mueller <dmueller(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |CONFIRMED -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1175268] [glibc2.32] kbuild build failure
by bugzilla_noreply＠suse.com 01 Sep '20

01 Sep '20

https://bugzilla.suse.com/show_bug.cgi?id=1175268 https://bugzilla.suse.com/show_bug.cgi?id=1175268#c9 --- Comment #9 from Dirk Mueller <dmueller(a)suse.com> --- I need more time in figuring out how to workaround that problem. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1175268] [glibc2.32] kbuild build failure
by bugzilla_noreply＠suse.com 01 Sep '20

01 Sep '20

https://bugzilla.suse.com/show_bug.cgi?id=1175268 https://bugzilla.suse.com/show_bug.cgi?id=1175268#c8 Dirk Mueller <dmueller(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |Andreas.Stieger(a)gmx.de --- Comment #8 from Dirk Mueller <dmueller(a)suse.com> --- so this is a new regression due to the bison 3.7.1 update that happens to be in the same staging: ------------------------------------------------------------------- Tue Aug 18 20:45:28 UTC 2020 - Andreas Stieger <andreas.stieger(a)gmx.de> - GNU bison 3.7.1: * YYPRINT macro is deprecated * --graph will generate a *.gv file by default * Add Counterexample Generation feature * Add File prefix mapping feature * Various bug fixes and behavior changes -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1175967] zypper dup from Tumbleweed 20200824 -> 20200826 fails
by bugzilla_noreply＠suse.com 01 Sep '20

01 Sep '20

https://bugzilla.suse.com/show_bug.cgi?id=1175967 https://bugzilla.suse.com/show_bug.cgi?id=1175967#c8 --- Comment #8 from Dirk S. <al13808(a)alte-leipziger.de> --- I've upgraded rpm to the latestest version with --nodeps. This has broken zypper because my zypper version depended on librpm.so.8 instead of 9. I was forced to use rpm to update zypper. After some work caused by the dependencies I am finally able to update again. I don't know if I should request to close the case because the cause of the problem is still unknown. Maybe you should provide an updated rpm with zstd compression included but depending on librpm.so.8 as additional package. I've got a snapshot of Tumbleweed-20190512 on an other partition as emergency system. I am not sure if it is possible to update this system easy otherwise. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1175800] Unable to install HP OMEN Notebook with Ryzen 7
by bugzilla_noreply＠suse.com 01 Sep '20

01 Sep '20

https://bugzilla.suse.com/show_bug.cgi?id=1175800 https://bugzilla.suse.com/show_bug.cgi?id=1175800#c10 David Diaz <dgonzalez(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Installation |Kernel Assignee|yast2-maintainers(a)suse.de |kernel-bugs(a)opensuse.org QA Contact|jsrain(a)suse.com |qa-bugs(a)suse.de --- Comment #10 from David Diaz <dgonzalez(a)suse.com> --- (In reply to Berthold Gunreben from comment #9) > unfortunately, during installation I had no network connection. Now with > borkenmodules=drm I could install. So, since `brokenmodules` is a "Comma-separated list of modules that will not be loaded during initialization"[1] I fear there is nothing in the YaST side we can do to this regard. I'm going to reassign the bug report to the Kernel component to see if they can do something or maybe give us some help. Thanks. [1] https://en.opensuse.org/SDB:Linuxrc -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1170232] New: Kernel spec self obsoletes
by bugzilla_noreply＠novell.com 01 Sep '20

01 Sep '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1170232 Bug ID: 1170232 Summary: Kernel spec self obsoletes Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-maintainers(a)forge.provo.novell.com Reporter: dcermak(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The kernel spec file contains a whole lot of self-obsoletes, which is pointed out by rpmlint: kernel-default.x86_64: W: self-obsoletion kernel-bigsmp <= 3.1 obsoletes kernel-bigsmp = 3.1 kernel-default.x86_64: W: self-obsoletion kernel-bigsmp-base <= 3.1 obsoletes kernel-bigsmp-base = 3.1 kernel-default-devel.x86_64: W: self-obsoletion kernel-bigsmp-devel <= 3.1 obsoletes kernel-bigsmp-devel = 3.1 kernel-default.x86_64: W: self-obsoletion kernel-desktop <= 4.3 obsoletes kernel-desktop = 4.3 kernel-default.x86_64: W: self-obsoletion kernel-desktop-base <= 4.3 obsoletes kernel-desktop-base = 4.3 kernel-default-devel.x86_64: W: self-obsoletion kernel-desktop-devel <= 4.3 obsoletes kernel-desktop-devel = 4.3 kernel-default.x86_64: W: self-obsoletion kernel-ec2 <= 4.4 obsoletes kernel-ec2 = 4.4 kernel-default.x86_64: W: self-obsoletion kernel-ec2-base <= 4.4 obsoletes kernel-ec2-base = 4.4 kernel-default-devel.x86_64: W: self-obsoletion kernel-ec2-devel <= 4.4 obsoletes kernel-ec2-devel = 4.4 kernel-default.x86_64: W: self-obsoletion kernel-smp <= 2.6.17 obsoletes kernel-smp = 2.6.17 kernel-default.x86_64: W: self-obsoletion kernel-trace <= 3.13 obsoletes kernel-trace = 3.13 kernel-default.x86_64: W: self-obsoletion kernel-trace-base <= 3.13 obsoletes kernel-trace-base = 3.13 kernel-default-devel.x86_64: W: self-obsoletion kernel-trace-devel <= 3.13 obsoletes kernel-trace-devel = 3.13 kernel-default.x86_64: W: self-obsoletion kernel-xen <= 4.4 obsoletes kernel-xen = 4.4 kernel-default.x86_64: W: self-obsoletion kernel-xen-base <= 4.4 obsoletes kernel-xen-base = 4.4 kernel-default-devel.x86_64: W: self-obsoletion kernel-xen-devel <= 4.4 obsoletes kernel-xen-devel = 4.4 The package obsoletes itself. This is known to cause errors in various tools and should thus be avoided, usually by using appropriately versioned Obsoletes and/or Provides and avoiding unversioned ones. Packages should not self-obsolete, as this breaks rpm and causes bugs like this one: https://bugzilla.redhat.com/show_bug.cgi?id=1824102. Not sure why this works with zypper, but it shouldn't. -- You are receiving this mail because: You are on the CC list for the bug.

2 10