[opensuse] Bad update info?
Yesterday I clicked on my automatic update widget (opensuse 13.1, kde 4.11.5) and I got this error: nothing provides libseccomp.so.2()(64bit) needed by systemd-210-40.1.x86_64 OK, so I waited and tried again today. Same result. I have opensuse-2016-137 sitting in queue but until it gets fixed "up there" somewhere, I cannot install it. What's the next step? Thanks, Fred -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 02/09/2016 08:50 AM, Stevens wrote:
Yesterday I clicked on my automatic update widget (opensuse 13.1, kde 4.11.5) and I got this error:
nothing provides libseccomp.so.2()(64bit) needed by systemd-210-40.1.x86_64
OK, so I waited and tried again today. Same result. I have opensuse-2016-137 sitting in queue but until it gets fixed "up there" somewhere, I cannot install it. What's the next step?
Thanks, Fred
Yes, I know I can go find that dependency but that kinda negates the idea of a "one click" install. The one who put the package update together should have caught the problem before it got shoved out. IMHO, of course. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2016-02-09 15:50, Stevens wrote:
Yesterday I clicked on my automatic update widget (opensuse 13.1, kde 4.11.5) and I got this error:
nothing provides libseccomp.so.2()(64bit) needed by systemd-210-40.1.x86_64
The systemd-210 update breaks several things in 13.1, don't apply it. See <https://lists.rosenauer.org/pipermail/evergreen/2016-February/001631.html> for more details. Also <https://bugzilla.suse.com/show_bug.cgi?id=965475> Perhaps you have to create another bugzilla for this one. :-? -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
Anyone know if this has been fixed yet, or where I can check to ascertain the progress? I see there have been new log entries to the bug report, but nothing new yet in the evergreen ML. Thanks, --Phil * Carlos E. R. <robin.listas@telefonica.net> [2016-02-09 09:02]:
On 2016-02-09 15:50, Stevens wrote:
Yesterday I clicked on my automatic update widget (opensuse 13.1, kde 4.11.5) and I got this error:
nothing provides libseccomp.so.2()(64bit) needed by systemd-210-40.1.x86_64
The systemd-210 update breaks several things in 13.1, don't apply it.
See <https://lists.rosenauer.org/pipermail/evergreen/2016-February/001631.html> for more details.
Also <https://bugzilla.suse.com/show_bug.cgi?id=965475>
Perhaps you have to create another bugzilla for this one. :-?
-- Philip Amadeo Saeli psaeli@zorodyne.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* Philip Amadeo Saeli <psaeli@zorodyne.com> [02-11-16 17:00]:
Anyone know if this has been fixed yet, or where I can check to ascertain the progress? I see there have been new log entries to the bug report, but nothing new yet in the evergreen ML.
Thanks,
--Phil
* Carlos E. R. <robin.listas@telefonica.net> [2016-02-09 09:02]:
On 2016-02-09 15:50, Stevens wrote:
Yesterday I clicked on my automatic update widget (opensuse 13.1, kde 4.11.5) and I got this error:
nothing provides libseccomp.so.2()(64bit) needed by systemd-210-40.1.x86_64
The systemd-210 update breaks several things in 13.1, don't apply it.
See <https://lists.rosenauer.org/pipermail/evergreen/2016-February/001631.html> for more details.
Also <https://bugzilla.suse.com/show_bug.cgi?id=965475>
Perhaps you have to create another bugzilla for this one. :-?
On my 13.1 server, I have: rpm -q --last systemd systemd-210-40.1.x86_64 Fri 05 Feb 2016 08:56:01 AM EST from: openSUSE-13.1-Update and have not noticed a problem -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 02/11/2016 05:30 PM, Patrick Shanahan wrote:
On my 13.1 server, I have: rpm -q --last systemd systemd-210-40.1.x86_64 Fri 05 Feb 2016 08:56:01 AM EST from: openSUSE-13.1-Update
and have not noticed a problem
Exactly the same here. -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2016-02-11 23:30, Patrick Shanahan wrote:
On my 13.1 server, I have: rpm -q --last systemd systemd-210-40.1.x86_64 Fri 05 Feb 2016 08:56:01 AM EST from: openSUSE-13.1-Update
and have not noticed a problem
I have not updated my 13.1 machines till I learn more. The bug affects named, and I use it. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
On 11/02/16 23:51, Carlos E. R. wrote:
On 2016-02-11 23:30, Patrick Shanahan wrote:
On my 13.1 server, I have: rpm -q --last systemd systemd-210-40.1.x86_64 Fri 05 Feb 2016 08:56:01 AM EST from: openSUSE-13.1-Update
and have not noticed a problem
I have not updated my 13.1 machines till I learn more. The bug affects named, and I use it.
I don't know if it's related to this update but I don't have another explanation. I have an external IDE drive attached via USB and not set to automount, but listed in fstab. Been mounting it regularly from within Dolphin on this 13.1 installation for the last couple of years, but the other day, after having done the systemd update and rebooted in the interim, it outright refused to mount from Dolphin or anywhere else. After another reboot it was fine. I often suspend the laptop to RAM so I had resumed from suspend on that occasion, don't know if that was relevant. I'm not aware of any other update or configuration that could have caused it, and so far the problem hasn't occurred again. gumb -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thursday, 2016-02-11 at 15:59 -0600, Philip Amadeo Saeli wrote:
Anyone know if this has been fixed yet, or where I can check to ascertain the progress? I see there have been new log entries to the bug report, but nothing new yet in the evergreen ML.
On the bug report. - -- Cheers, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAla9EOsACgkQtTMYHG2NR9XpIACgkcvOgzsjfj+EFHUVkYTJXBN4 YSsAn19UKIeWCb9GvlBItM0h+QaeXR/q =P7Wo -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (6)
-
Anton Aylward -
Carlos E. R. -
gumb -
Patrick Shanahan -
Philip Amadeo Saeli -
Stevens