[opensuse-factory] leap15.0 - some messages during "zypper dup"
I ran a zypper dup on a xen guest and noticed a few messages, I thought they might be of interest to someone: (424/774) Installing: klogd-1.4.1-lp150.2.3.x86_64 ...............[done] Additional rpm output: /var/tmp/rpm-tmp.5lyOph: line 14: /var/adm/fillup-templates/syslog.del: No such file or directory fillup: Exception in ../SRC/services.c, line 348 concerning file not opened /var/tmp/rpm-tmp.5lyOph: line 36: /var/adm/fillup-templates/syslog.del: No such file or directory fillup: Exception in ../SRC/services.c, line 348 concerning file not opened Failed to try-restart klogd.service: Operation refused, unit klogd.service may be requested by dependency only (it is configured to refuse manual start/stop). See system logs and 'systemctl status klogd.service' for details. (476/774) Installing: kbd-2.0.4-lp150.4.1.x86_64 ....................................[done] Additional rpm output: SysV service kbdsettings does not exist, skipping Updating /etc/sysconfig/console ... Updating /etc/sysconfig/keyboard ... /var/tmp/rpm-tmp.zeOhE0: line 62: /var/adm/fillup-templates/keyboard.del: No such file or directory /var/tmp/rpm-tmp.zeOhE0: line 62: /var/adm/fillup-templates/keyboard.del: No such file or directory fillup: Exception in ../SRC/services.c, line 348 concerning file not opened Created symlink /etc/systemd/system/multi-user.target.wants/kbdsettings.service -> /usr/lib/systemd/system/kbdsettings.service. (478/774) Installing: ca-certificates-2+git20170807.10b2785-lp150.4.2.noarch ..........[done] Additional rpm output: p11-kit: couldn't complete writing file: /var/lib/ca-certificates/openssl/CFCA_EV_ROOT.pem: No such file or directory p11-kit: 'destination != NULL' not true at p11_save_symlink_in (714/774) Installing: syslog-service-2.0-lp150.2.3.noarch .............................[done] Additional rpm output: /var/tmp/rpm-tmp.RRzemz: line 11: /var/adm/fillup-templates/syslog.del: No such file or directory fillup: Exception in ../SRC/services.c, line 348 concerning file not opened /var/tmp/rpm-tmp.RRzemz: line 33: /var/adm/fillup-templates/syslog.del: No such file or directory fillup: Exception in ../SRC/services.c, line 348 concerning file not opened Updating /etc/sysconfig/boot ... Failed to try-restart klog.service: Operation refused, unit klog.service may be requested by dependency only (it is configured to refuse manual start/stop). See system logs and 'systemctl status klog.service' for details. (718/774) Installing: syslog-ng-3.12.1-lp150.3.5.x86_64 ..............................[done] Additional rpm output: warning: /etc/syslog-ng/syslog-ng.conf created as /etc/syslog-ng/syslog-ng.conf.rpmnew /var/tmp/rpm-tmp.eFDQDE: line 18: /var/adm/fillup-templates/syslog.del: No such file or directory /var/tmp/rpm-tmp.eFDQDE: line 18: /var/adm/fillup-templates/syslog.del: No such file or directory fillup: Exception in ../SRC/services.c, line 348 concerning file not opened Updating /etc/sysconfig/syslog ... (718/774) Installing: syslog-ng-3.12.1-lp150.3.5.x86_64 ...............................[done] Additional rpm output: warning: /etc/syslog-ng/syslog-ng.conf created as /etc/syslog-ng/syslog-ng.conf.rpmnew /var/tmp/rpm-tmp.eFDQDE: line 18: /var/adm/fillup-templates/syslog.del: No such file or directory /var/tmp/rpm-tmp.eFDQDE: line 18: /var/adm/fillup-templates/syslog.del: No such file or directory fillup: Exception in ../SRC/services.c, line 348 concerning file not opened Updating /etc/sysconfig/syslog ... I also noticed the initrd being rebuilt twice, with this error: dracut-install: ERROR: installing '/usr/lib/udev/rules.d/54-before-scsi-sg3_id.rules/usr/lib/udev/rules.d/11-dm-parts.rules' dracut: /usr/lib/dracut/dracut-install -D /var/tmp/dracut.UuWGUc/initramfs -a /usr/lib/udev/rules.d/54-before-scsi-sg3_id.rules/usr/lib/udev/rules.d/11-dm-parts.rules I'm opening a bugreport on the latter. -- Per Jessen, Zürich (1.8°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Per Jessen wrote:
I also noticed the initrd being rebuilt twice, with this error:
dracut-install: ERROR: installing '/usr/lib/udev/rules.d/54-before-scsi-sg3_id.rules/usr/lib/udev/rules.d/11-dm-parts.rules' dracut: /usr/lib/dracut/dracut-install -D /var/tmp/dracut.UuWGUc/initramfs -a /usr/lib/udev/rules.d/54-before-scsi-sg3_id.rules/usr/lib/udev/rules.d/11-dm-parts.rules
I'm opening a bugreport on the latter.
https://bugzilla.opensuse.org/show_bug.cgi?id=1080991 -- Per Jessen, Zürich (1.8°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Per Jessen wrote:
Per Jessen wrote:
I also noticed the initrd being rebuilt twice, with this error:
dracut-install: ERROR: installing '/usr/lib/udev/rules.d/54-before-scsi-sg3_id.rules/usr/lib/udev/rules.d/11-dm-parts.rules' dracut: /usr/lib/dracut/dracut-install -D /var/tmp/dracut.UuWGUc/initramfs -a /usr/lib/udev/rules.d/54-before-scsi-sg3_id.rules/usr/lib/udev/rules.d/11-dm-parts.rules
I'm opening a bugreport on the latter.
Hmm, I had seen those, too, when examining the nvidia black screen issue. In my case it came from install_items+= instructions which were defined like install_items+="/some/path" Seems they got concatenated without spaces, at least the error went away when I changed it to install_items+=" /some/path " -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Wed, 2018-02-14 at 14:05 +0100, Per Jessen wrote:
I ran a zypper dup on a xen guest and noticed a few messages, I thought they might be of interest to someone:
(424/774) Installing: klogd-1.4.1-lp150.2.3.x86_64 ...............[done] Additional rpm output: /var/tmp/rpm-tmp.5lyOph: line 14: /var/adm/fillup-templates/syslog.del: No such file or directory fillup: Exception in ../SRC/services.c, line 348 concerning file not opened
This type of error was just fixed with RPM 4.14.1 (some macros needed a fix for the /var/adm/fillup-templates to /usr/share/ move. Since this is a fix in macros, packages making use of this macro will need to be rebuilt (the macros are expanded at build time, not at install time) Cheers Dominique
Dominique Leuenberger / DimStar wrote:
On Wed, 2018-02-14 at 14:05 +0100, Per Jessen wrote:
I ran a zypper dup on a xen guest and noticed a few messages, I thought they might be of interest to someone:
(424/774) Installing: klogd-1.4.1-lp150.2.3.x86_64 ...............[done] Additional rpm output: /var/tmp/rpm-tmp.5lyOph: line 14: /var/adm/fillup-templates/syslog.del: No such file or directory fillup: Exception in ../SRC/services.c, line 348 concerning file not opened
This type of error was just fixed with RPM 4.14.1 (some macros needed a fix for the /var/adm/fillup-templates to /usr/share/ move.
Since this is a fix in macros, packages making use of this macro will need to be rebuilt (the macros are expanded at build time, not at install time)
Okay, thanks for the explanation. These look a little odd to me: (424/774) Installing: klogd-1.4.1-lp150.2.3.x86_64 ...............[done] Additional rpm output: [snip] Failed to try-restart klogd.service: Operation refused, unit klogd.service may be requested by dependency only (it is configured to refuse manual start/stop). (714/774) Installing: syslog-service-2.0-lp150.2.3.noarch .............................[done] Additional rpm output: [snip] Failed to try-restart klog.service: Operation refused, unit klog.service may be requested by dependency only (it is configured to refuse manual start/stop). -------- Anyway, apart from this, leap15 build128.1 as a minimal xen guest looks good. ipv4 and ipv6 both work, all the basic stuff. The 'dup' went fine, there was only that slight hiccup in dracut/kpartx, but it didn't cause any problems and was easily fixed. -- Per Jessen, Zürich (2.6°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 15/02/18 00:05, Per Jessen wrote:
I ran a zypper dup on a xen guest and noticed a few messages, I thought they might be of interest to someone:
Sorry, Per, just noticed what you wrote. Why the "zypper dup" in Leap 15.0? Is Leap 15 now also subject to the condition that one only uses 'zypper dup' to update its files just as required in Tumbleweed? I've been using the standard 'zypper refresh', 'zypper patch', 'zypper up' on Leap 15.0. [pruned] BC -- Always be nice to people on your way up -- you'll see the same people on your way down. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 2018-02-16 07:42, Basil Chupin wrote:
On 15/02/18 00:05, Per Jessen wrote:
I ran a zypper dup on a xen guest and noticed a few messages, I thought they might be of interest to someone:
Sorry, Per, just noticed what you wrote.
Why the "zypper dup" in Leap 15.0? Is Leap 15 now also subject to the condition that one only uses 'zypper dup' to update its files just as required in Tumbleweed?
Because the exception is "Beta phase". While the distribution is Beta, new images appear. If there are new images, do a "dup". :-) Beta works like a rolling distro.
I've been using the standard 'zypper refresh', 'zypper patch', 'zypper up' on Leap 15.0.
Then you are doing it wrong :-) Once it is released, then stop using dup. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
On 16/02/18 21:06, Carlos E. R. wrote:
On 2018-02-16 07:42, Basil Chupin wrote:
On 15/02/18 00:05, Per Jessen wrote:
I ran a zypper dup on a xen guest and noticed a few messages, I thought they might be of interest to someone: Sorry, Per, just noticed what you wrote.
Why the "zypper dup" in Leap 15.0? Is Leap 15 now also subject to the condition that one only uses 'zypper dup' to update its files just as required in Tumbleweed? Because the exception is "Beta phase". While the distribution is Beta, new images appear. If there are new images, do a "dup". :-)
Beta works like a rolling distro.
And where are these words of wisdom chiselled for all to see?
I've been using the standard 'zypper refresh', 'zypper patch', 'zypper
up' on Leap 15.0. Then you are doing it wrong :-)
Not the first time I would be doing something wrong...
Once it is released, then stop using dup.
Once it is released it is too late... Oh, I see what you mean! :-) BC -- Always be nice to people on your way up -- you'll see the same people on your way down. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Saturday, 2018-02-17 at 17:12 +1100, Basil Chupin wrote:
On 16/02/18 21:06, Carlos E. R. wrote:
On 2018-02-16 07:42, Basil Chupin wrote:
On 15/02/18 00:05, Per Jessen wrote:
I ran a zypper dup on a xen guest and noticed a few messages, I thought they might be of interest to someone: Sorry, Per, just noticed what you wrote.
Why the "zypper dup" in Leap 15.0? Is Leap 15 now also subject to the condition that one only uses 'zypper dup' to update its files just as required in Tumbleweed? Because the exception is "Beta phase". While the distribution is Beta, new images appear. If there are new images, do a "dup". :-)
Beta works like a rolling distro.
And where are these words of wisdom chiselled for all to see?
Ha ha :-) Dunno, they might. :-?
I've been using the standard 'zypper refresh', 'zypper patch', 'zypper
up' on Leap 15.0. Then you are doing it wrong :-)
Not the first time I would be doing something wrong...
Once it is released, then stop using dup.
Once it is released it is too late...
Oh, I see what you mean! :-)
Ok! :-) - -- Cheers, Carlos E. R. (from openSUSE 42.3 x86_64 "Malachite" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlqIeEYACgkQtTMYHG2NR9WMqACggNCOUlreItqKe0syiqkpuUv3 qRIAoJiidp6Zmo/tBKKbvLiWpa8Fpxyn =eVZB -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Saturday, 17 February 2018 07:12:51 CET Basil Chupin wrote:
On 16/02/18 21:06, Carlos E. R. wrote:
On 2018-02-16 07:42, Basil Chupin wrote:
On 15/02/18 00:05, Per Jessen wrote:
I ran a zypper dup on a xen guest and noticed a few messages, I thought
they might be of interest to someone: Sorry, Per, just noticed what you wrote.
Why the "zypper dup" in Leap 15.0? Is Leap 15 now also subject to the condition that one only uses 'zypper dup' to update its files just as required in Tumbleweed?
Because the exception is "Beta phase". While the distribution is Beta, new images appear. If there are new images, do a "dup". :-)
Beta works like a rolling distro.
And where are these words of wisdom chiselled for all to see?
I just looked if I would be able to find it on a wiki page but no success. But a hint to better understand why `zypper dup` applies here similar to Tumbleweed: Every release of openSUSE Tumbleweed is a *build* of the repository at this point in time which can be considered a new version of the distribution itself. When you are upgrading your Tumbleweed installation you go from let's say 20180221 to 20180224, which is an upgrade from one version to another replacing the repository content of your pool repos, e.g. "oss" with a new set of packages. With `zypper dup` you ask to look for the most recent package version and install that over your old version. Within the development process of Leap 15.0 that is the same, e.g. from build 0123 to 0276. *After* release of a product, say openSUSE Leap 42.3, the content of the pool repos, e.g. again "oss" is never replaced. Only new versions are published over the "Update" repo which is hardly ever used for openSUSE Tumbleweed for example. This is where you apply `zypper up` to say that you *only* want to have these maintenance updates. In a properly configured system calling `zypper dup` can always work regardless of your underlying distribution. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 27/02/18 09:06, Oliver Kurz wrote:
On 16/02/18 21:06, Carlos E. R. wrote:
On 2018-02-16 07:42, Basil Chupin wrote:
On 15/02/18 00:05, Per Jessen wrote:
I ran a zypper dup on a xen guest and noticed a few messages, I thought they might be of interest to someone: Sorry, Per, just noticed what you wrote.
Why the "zypper dup" in Leap 15.0? Is Leap 15 now also subject to the condition that one only uses 'zypper dup' to update its files just as required in Tumbleweed? Because the exception is "Beta phase". While the distribution is Beta, new images appear. If there are new images, do a "dup". :-)
Beta works like a rolling distro. And where are these words of wisdom chiselled for all to see? I just looked if I would be able to find it on a wiki page but no success. But a hint to better understand why `zypper dup` applies here similar to Tumbleweed: Every release of openSUSE Tumbleweed is a *build* of the repository at this point in time which can be considered a new version of the distribution itself. When you are upgrading your Tumbleweed installation you go from let's say 20180221 to 20180224, which is an upgrade from one version to another replacing the repository content of your pool repos, e.g. "oss" with a new set of packages. With `zypper dup` you ask to look for the most recent package version and install that over your old version. Within the development process of Leap 15.0 that is the same, e.g. from build 0123 to
On Saturday, 17 February 2018 07:12:51 CET Basil Chupin wrote: 0276. *After* release of a product, say openSUSE Leap 42.3, the content of the pool repos, e.g. again "oss" is never replaced. Only new versions are published over the "Update" repo which is hardly ever used for openSUSE Tumbleweed for example. This is where you apply `zypper up` to say that you *only* want to have these maintenance updates. In a properly configured system calling `zypper dup` can always work regardless of your underlying distribution.
Thank you, Oliver, for this explanation. BC -- Always be nice to people on your way up -- you'll see the same people on your way down. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (6)
-
Basil Chupin -
Carlos E. R. -
Dominique Leuenberger / DimStar -
Oliver Kurz -
Per Jessen -
Peter Suetterlin