I tried to do my daily zypper dup today, and I was happy to see kernel-desktop-3.11.1-28.1 is available. But when I tried to run the update the update stopped 1t 100% when installing the newer kernel.
So I did a CTRL+C and tried again. I saw the following error:
(pango-querymodules-64:7734): GLib-GObject-CRITICAL **: gtype.c:2720: You forgot to call g_type_init()
(pango-querymodules-64:7734): GLib-CRITICAL **: g_once_init_leave: assertion `result != 0' failed
(pango-querymodules-64:7734): GLib-GObject-WARNING **: cannot retrieve class for invalid (unclassed) type `<invalid>'
(pango-querymodules-64:7734): GLib-GObject-CRITICAL **: g_enum_get_value: assertion `G_IS_ENUM_CLASS (enum_class)' failed
(pango-querymodules-64:7734): Pango-WARNING **: Engine reported invalid script value 2
Some reading showed that this was related to the mkinitrd script. So I tried to run it and I got:
linux-6c9j:/boot # mkinitrd
Kernel image: /boot/vmlinuz-3.11.0-27.g0a1c41f-desktop
Initrd image: /boot/initrd-3.11.0-27.g0a1c41f-desktop
KMS drivers: i915
(pango-querymodules-64:7734): GLib-GObject-CRITICAL **: gtype.c:2720: You forgot to call g_type_init()
(pango-querymodules-64:7734): GLib-CRITICAL **: g_once_init_leave: assertion `result != 0' failed
(pango-querymodules-64:7734): GLib-GObject-WARNING **: cannot retrieve class for invalid (unclassed) type `<invalid>'
(pango-querymodules-64:7734): GLib-GObject-CRITICAL **: g_enum_get_value: assertion `G_IS_ENUM_CLASS (enum_class)' failed
(pango-querymodules-64:7734): Pango-WARNING **: Engine reported invalid script value 2
Also, the initrd and vmlinuz symlinks were set to kernel-desktop-3.11.1-28.1, but there was no vmlinuz image. I manually deleted the symlinks and set them to the correct kernel version, 3.11-0-27. I was able to reboot fine, but hen I try to create an initrd for 3.7.10-1 I get the same error.
The issue appears, from the thread, to be related to the pango-tools package. Downgrading to pango-tools 1.34.1-3.11 allowed me to run mkinitrd correctly.
So, the questionis, how do I let the devs and package managers know this?
Just did a plain zypper dup, and I didn’t see that kernel version at all. I had kernel-desktop-3.11.1-28.1.gfeffbf9.x86_64 already installed without issue, plus three older ones.
Hmm, I thought the default number kept was only three. Did it change on 12.3 or Tumbleweed?
Out of curiosity, what version of pango-tools do you have?
It is very strange, and I suppose interesting, that I am able to run mkinitrd after downgrading, but you had no problem at all. It is possible the kernel was upgraded BEFORE pango-tools on your system.
My system is OK now, but I would like to track this down as I cannot keep the older pango-tools for ever. It is possible there is another issue which is masked by pango-tools. BTW, does mkinitrd run without errors on your system? (I know, “don’t hurt my precious…”, no need for any risk you are not comfortable with.)
Ignore that comment, just remembered why mine is different. I’m now running with btrfs and Snapper on the root file system. On mine with PC BIOS that forces me to use a separate /boot partition, since btrfs is currently a non-bootable file system.
In that situation and for those interested, YaST SM still only keeps three kernels showing as installed, but the fourth and subsequent need to be physically removed from /boot. FWIW rpm -q kernel-desktop reports all those present in /boot.
The problem is not mkinitrd but pango-querymodules-64. mkinitrd calls this because it’s needed for plymouth to be put into the initrd. If you uninstall plymouth, mkinitrd should work fine.
I would suggest to try “zypper dup --from Tumbleweed”, hopefully that would fix it. You can run “pango-querymodules-64” manually to check if it works afterwards. And please post which packages get updated, maybe that will provide a clue to the cause of the issue.
Mine was installed during the big upgrade to Tumbleweed. IIRC then it booted without some branding package changes installed, and I recall no openSUSE branding at KDE login. That was also with the previous kernel. I recall a subsequent plain zypper dup re-installed the branding, without any noticeable issues, and there has been plenty of zypper dup activity since, with kernel update, as I install the extra multimedia packages I use, plus Packman updates.
So, try zypper dup --from Tumbleweed to fix, but you may need to subsequently and optionally re-install some packages.
I have had no dependency issues. I ran zypper dup --from Tumbleweed and I verified pango-querymodules-64 works. I also verified mkinitrd runs correctly. I did get an error though. When gnome-icon-theme-extras is instaled from Tumbleweed I get the same exact errors as above. When I installed it from the openSUSE repository I did not get any errors. The version in the openSUSE repository looks newer, it is gnome-icon-theme-extras-3.6.2-2.1.1.noarch, while the Tumbleweed version is gnome-icon-theme-extras-3.6.2-2.1.noarch.
I got the full openSUSE theme experience, too. lol!
But as of now it looks “fixed” from my standpoint–I have a newer version of gnome-icon-theme-extras. However, there does seem to be a dependency issue with the gnome packages. I would be willing to find it, but I do not know how to proceed.
2013-09-26 07:51:35|install|kbackup|0.8-6.8|x86_64||KDE:Extra|c22e231807e8204952d4c1073ce9af461f4671192f0b0b92fbb01a9f27dcadba|
2013-09-26 07:51:35|install|kwave|0.8.10-2.66|x86_64||KDE:Extra|c6514ac9def5a91fef6641d5d86bdf9fdb83c8fd6bb0a38284848c6cf799223e|
2013-09-26 07:58:11|install|pango-tools|1.34.1-3.11|x86_64|root@linux-6c9j.site|Tumbleweed|99a98e514d230131bc271d68c597122c055532cc|
2013-09-26 07:58:11|install|pango-tools-32bit|1.34.1-3.11|x86_64|root@linux-6c9j.site|Tumbleweed|dfdd504e45600403f4e3c887248be1baa96c0d26|
2013-09-26 08:07:49|install|pango-tools|1.32.5-3.4.2|x86_64|root@linux-6c9j.site|openSUSE Current updates|d94d69b78fc3e913196dcb7d34e04edf801e425afb7360e56d4e914c3a753e2e|
2013-09-26 11:26:43|remove |avahi-autoipd|0.6.31-2.29|x86_64|root@linux-6c9j.site|
2013-09-26 11:26:44|install|branding-openSUSE|12.3-3.3|noarch||Tumbleweed|bf3a6baee0d1acbcc44876f2082031e9ec725f68efe768d3831f921d854ef361|
2013-09-26 11:26:44|install|gfxboot-branding-openSUSE|12.3-3.3|noarch||Tumbleweed|ee38430346b2552b3f5990f946d19fdf672f9524e47694c56f29e57f22a24953|
2013-09-26 11:26:44|install|gimp-branding-openSUSE|12.3-3.3|noarch||Tumbleweed|2eef36e2395b2b84f027dbc82a306572e3ac9a22bd775927a4f33ac4aba2796f|
# 2013-09-26 11:26:45 gnome-icon-theme-extras-3.6.2-2.1.noarch.rpm installed ok
# Additional rpm output:
#
# (gtk-update-icon-cache:2191): GLib-GObject-CRITICAL **: gtype.c:2720: You forgot to call g_type_init()
#
# (gtk-update-icon-cache:2191): GLib-GObject-CRITICAL **: gtype.c:2720: You forgot to call g_type_init()
#
# (gtk-update-icon-cache:2191): GLib-GObject-CRITICAL **: g_type_interface_add_prerequisite: assertion `G_TYPE_IS_INTERFACE (interface_type)' failed
#
# (gtk-update-icon-cache:2191): GLib-CRITICAL **: g_once_init_leave: assertion `result != 0' failed
#
# (gtk-update-icon-cache:2191): GLib-GObject-CRITICAL **: g_type_add_interface_static: assertion `G_TYPE_IS_INSTANTIATABLE (instance_type)' failed
#
# (gtk-update-icon-cache:2191): GLib-CRITICAL **: g_once_init_leave: assertion `result != 0' failed
#
# (gtk-update-icon-cache:2191): GLib-GObject-CRITICAL **: g_object_new: assertion `G_TYPE_IS_OBJECT (object_type)' failed
# /var/tmp/rpm-tmp.8hXO9I: line 5: 2191 Segmentation fault /usr/bin/gtk-update-icon-cache --quiet --force "/usr/share/icons/${ICON_THEME}"
#
2013-09-26 11:26:45|install|gnome-icon-theme-extras|3.6.2-2.1|noarch||Tumbleweed|0e0d3656f3987c634c0644cd257ba320c23eafeef5c70e9268a0326e27f70fc6|
# 2013-09-26 11:26:47 grub2-branding-openSUSE-12.3-3.3.noarch.rpm installed ok
# Additional rpm output:
# Generating grub.cfg ...
# Found theme: /boot/grub2/themes/openSUSE/theme.txt
# Found linux image: /boot/vmlinuz-3.11.1-28.gfeffbf9-desktop
# Found initrd image: /boot/initrd-3.11.1-28.gfeffbf9-desktop
# Found linux image: /boot/vmlinuz-3.11.0-27.g0a1c41f-desktop
# Found initrd image: /boot/initrd-3.11.0-27.g0a1c41f-desktop
# Found linux image: /boot/vmlinuz-3.7.10-1.16-desktop
# Found memtest image: /boot/memtest.bin
# No volume groups found
# done
#
2013-09-26 11:26:47|install|grub2-branding-openSUSE|12.3-3.3|noarch||Tumbleweed|4a4086428a43b74b59e5ee709c877fd23873176dbaee814676106530e9cc999b|
2013-09-26 11:26:47|install|ksshaskpass|0.5.3-2.2|x86_64||Tumbleweed|d8a1c0a3c0679194fd376c2bf422bdd331799a15|
2013-09-26 11:26:47|install|libdbusmenu-qt2-32bit|0.9.2-3.4|x86_64||Tumbleweed|9ad730c5634e1f16dc0168691b3e55685d08e28c686720eda73f3ba1902909ed|
2013-09-26 11:26:47|install|libepub0|0.2.1-2.2|x86_64||Tumbleweed|a67588ac1fe8bf90cdb7b5adaa4cfd76f5c7cee5c921f96752e27c2aadb78be5|
2013-09-26 11:26:47|install|libglib-2_0-0|2.36.4-5.1|x86_64||Tumbleweed|97fa5263758edfe5c08bb79db7734e9914130896a0ecba5b0a0669f41f1a1579|
2013-09-26 11:26:47|install|libqca2-32bit|2.0.3-2.3|x86_64||Tumbleweed|d9b434b7c8edd0d4eea1ddd034c47118130e9479565119610639b87ab284b7e6|
2013-09-26 11:26:47|install|libqimageblitz4|0.0.6-2.1|x86_64||Tumbleweed|019ce4e789ce27e2d925b711e1ad497f654708ab2a5c6c17310a51caf055e822|
2013-09-26 11:26:48|install|libqjson0|0.8.1-2.1|x86_64||Tumbleweed|6b7056d40839dc8b128daa296691286fb2cb84dab290784bd0ea1cd99a06d986|
2013-09-26 11:26:48|install|plasmoid-quickaccess|0.8.1-4.2|x86_64||Tumbleweed|1d06c3e30f6ae3b214c2eeb41e411d5b846bdb7f|
# 2013-09-26 11:27:07 plymouth-branding-openSUSE-12.3-3.3.noarch.rpm installed ok
# Additional rpm output:
#
# Kernel image: /boot/vmlinuz-3.11.0-27.g0a1c41f-desktop
# Initrd image: /boot/initrd-3.11.0-27.g0a1c41f-desktop
# KMS drivers: i915
# Root device: /dev/disk/by-id/ata-M4-CT512M4SSD2_000000001249091F73FB-part6 (/dev/sda6) (mounted on / as ext4)
# Resume device: /dev/disk/by-id/ata-M4-CT512M4SSD2_000000001249091F73FB-part5 (/dev/sda5)
# Kernel Modules: thermal_sys thermal processor fan scsi_dh scsi_dh_alua scsi_dh_rdac scsi_dh_emc scsi_dh_hp_sw video button i2c-algo-bit drm drm_kms_helper i915 xhci-hcd hid-logitech-dj libcrc32c xor zlib_deflate raid6_pq btrfs crc32c-intel
# Features: acpi kms plymouth block usb btrfs resume.userspace resume.kernel
#
# Kernel image: /boot/vmlinuz-3.11.1-28.gfeffbf9-desktop
# Initrd image: /boot/initrd-3.11.1-28.gfeffbf9-desktop
# KMS drivers: i915
# Root device: /dev/disk/by-id/ata-M4-CT512M4SSD2_000000001249091F73FB-part6 (/dev/sda6) (mounted on / as ext4)
# Resume device: /dev/disk/by-id/ata-M4-CT512M4SSD2_000000001249091F73FB-part5 (/dev/sda5)
# Kernel Modules: thermal_sys thermal processor fan scsi_dh scsi_dh_alua scsi_dh_rdac scsi_dh_emc scsi_dh_hp_sw video button i2c-algo-bit drm drm_kms_helper i915 xhci-hcd hid-logitech-dj libcrc32c xor zlib_deflate raid6_pq btrfs crc32c-intel
# Features: acpi kms plymouth block usb btrfs resume.userspace resume.kernel
#
# Kernel image: /boot/vmlinuz-3.7.10-1.16-desktop
# Initrd image: /boot/initrd-3.7.10-1.16-desktop
# KMS drivers: i915
# Root device: /dev/disk/by-id/ata-M4-CT512M4SSD2_000000001249091F73FB-part6 (/dev/sda6) (mounted on / as ext4)
# Resume device: /dev/disk/by-id/ata-M4-CT512M4SSD2_000000001249091F73FB-part5 (/dev/sda5)
# Kernel Modules: thermal_sys thermal processor fan scsi_dh scsi_dh_alua scsi_dh_rdac scsi_dh_emc scsi_dh_hp_sw video button i2c-algo-bit drm drm_kms_helper i915 xhci-hcd hid-logitech-dj libcrc32c zlib_deflate btrfs crc32c-intel
# Features: acpi kms plymouth block usb btrfs resume.userspace resume.kernel
#
2013-09-26 11:27:07|install|plymouth-branding-openSUSE|12.3-3.3|noarch||Tumbleweed|aae1cb37fa951279063addef3b812a12b0978e3e5c3393ce3e6bb58100748312|
2013-09-26 11:27:07|install|screen|4.0.4-3.1|x86_64||Tumbleweed|b7e0a465e0dffe9886af65ecf8281697b846b0a9b2212d8a8ca24d8d3eb92550|
2013-09-26 11:27:07|install|susegreeter-branding-openSUSE|12.3-3.3|noarch||Tumbleweed|208d6e5b93410d31f7697cf59dd7a12b3deb9afe056fdc861c4106d5525f9b8c|
2013-09-26 11:27:08|install|synaptiks|0.8.1-3.1|noarch||Tumbleweed|830f29dfb58a0cf7b4897d8eb4125ac66cb0842667a70daf58c15f008d692c18|
2013-09-26 11:27:08|install|wallpaper-branding-openSUSE|12.3-3.3|noarch||Tumbleweed|96ba2571b58d2833e39d49751848fec26e894789e767a60583954233dc448bdc|
2013-09-26 11:27:08|install|yast2-qt-branding-openSUSE|12.3-3.3|noarch||Tumbleweed|f1d6c423a827355dfdb27e377b3ccd44e4d6cfc4e2876bda721c0a7042ad5589|
2013-09-26 11:27:08|install|kdebase4-openSUSE|12.3-2.12|x86_64||Tumbleweed|149bd62c7a5c8e5a89b581eca82af7847b4dab622c1d552bb82d68ffc6851327|
2013-09-26 11:27:09|install|libavahi-common3|0.6.31-2.29|x86_64||Tumbleweed|b89a07d30b73185f77ee9f3c455e1340c3db0b74795b888f7086e7c49b2e112f|
2013-09-26 11:27:09|install|libdbusmenu-qt2|0.9.2-3.4|x86_64||Tumbleweed|0678022b086738b96c8e681b2cd9a4401e6246c13f9a93fd5e0d72bca6fe51f7|
2013-09-26 11:27:09|install|libgthread-2_0-0|2.36.4-5.1|x86_64||Tumbleweed|f37238e4de70b56b04a01f94f7f643b104b0e5b6f5e7c4bd6c2a93419b98c4ea|
2013-09-26 11:27:09|install|libgobject-2_0-0|2.36.4-5.1|x86_64||Tumbleweed|40b8a931f6db689bf72f6a4945d546c18272d23135f77ca072d8b7b369864f3e|
2013-09-26 11:27:09|install|libgmodule-2_0-0|2.36.4-5.1|x86_64||Tumbleweed|113d2620604e1dd8f7b573ebcde387266eb04c1442f15ee9d048ffbe867cdd78|
2013-09-26 11:27:09|install|libkgapi1|2.0.1-2.2|x86_64||Tumbleweed|c7259874bc5eb0203b8f0f7e83dc1d19ba0524ab|
2013-09-26 11:27:09|install|choqok|1.4-3.1|x86_64||Tumbleweed|439f46db0d3df37efc07c4ae7f98bf81071d2c8b|
2013-09-26 11:27:10|install|ksplashx-branding-openSUSE|12.3-3.3|noarch||Tumbleweed|fa6066e5e1ede8791f6237c4728e7a1eb4c3c8c992800be84b0d5940ae2d231a|
2013-09-26 11:27:10|install|ksplash-qml-branding-openSUSE|12.3-3.3|noarch||Tumbleweed|89d73dd61ff3a66180dada1030f12fbf2059d573b18246e3f77acde0a7817509|
2013-09-26 11:27:10|install|libavahi-core7|0.6.31-2.29|x86_64||Tumbleweed|c977793de687fc9c40845b93c161d427f7a9b56171033f1c17d5114f8230d29a|
2013-09-26 11:27:10|install|libavahi-client3|0.6.31-2.29|x86_64||Tumbleweed|e39c597a027d6a75e16f1bba46b9c81edfb52d4f37c16ae1342961c40a7742ce|
2013-09-26 11:27:10|install|libavahi-glib1|0.6.31-2.2|x86_64||Tumbleweed|ad4d4824ff11523cc29e3aeef82633df1fa56d68c8f2411bb6a659f26fc3c137|
2013-09-26 11:27:10|install|libopencv2_4|2.4.6.1-2.7|x86_64||Tumbleweed|042beb5cea3ad062abd0089b1e6911f8ab955becaed599c40b2001e6dde83868|
2013-09-26 11:27:10|install|pango-tools|1.34.1-3.11|x86_64||Tumbleweed|99a98e514d230131bc271d68c597122c055532cc|
2013-09-26 11:27:11|install|glib2-tools|2.36.4-5.1|x86_64||Tumbleweed|bb534e31b44ea384917b002f8722aa214cf63a9ab3e16fe548a84546aaae539d|
# 2013-09-26 11:27:11 avahi-0.6.31-2.29.x86_64.rpm installed ok
# Additional rpm output:
# Updating /etc/sysconfig/avahi...
# Updating /etc/sysconfig/security...
# redirecting to systemctl try-restart avahi-daemon
# redirecting to systemctl try-restart avahi-dnsconfd
#
2013-09-26 11:27:11|install|avahi|0.6.31-2.29|x86_64||Tumbleweed|5825e8fdf6374e034a523cf2e80e81354425393d5c3b053cb8c579f39396b1d2|
2013-09-26 11:27:11|install|libdns_sd|0.6.31-2.29|x86_64||Tumbleweed|c50b188cdfdaa48cb4dbc93c363d12819fa6cdf39903ea248b6b12ea83e85091|
2013-09-26 11:27:11|install|gio-branding-openSUSE|12.3-2.4|noarch||Tumbleweed|1efbc63ff2754c499f6b396c2bb826574c2e0fdaa3ff92187eeab6e9574b83a0|
2013-09-26 11:27:11|install|libgio-2_0-0|2.36.4-5.1|x86_64||Tumbleweed|6ec3bae5eed022f2334f3e0f599391e00b4df269dbb81d0fcfa53ea7c530cc37|
2013-09-26 11:27:11|install|libpackagekit-glib2-16|0.8.7-2.49|x86_64||Tumbleweed|6d80d53c5cea8d2878a5bccf51e348bfa9e59d1aba81db90aef37ed25a1f50e0|
2013-09-26 11:27:11|install|PackageKit-gtk3-module|0.8.7-2.49|x86_64||Tumbleweed|8e71b97f8e67a96b505e9db902bdd4bb5abd55a195ed3669e0c81e30f6fbd24d|
2013-09-26 11:27:11|install|gstreamer|1.0.7-3.6|x86_64||Tumbleweed|cc75bc3cb0eed091a4054fdad834e86300ce5f78|
2013-09-26 11:27:12|install|glib2-devel|2.36.4-5.1|x86_64||Tumbleweed|fd1c9d057b7bdd457dc65ca2dfec488272eeed51a5c9bae64490363331a7e0c6|
2013-09-26 11:27:12|install|PackageKit-gstreamer-plugin|0.8.7-2.49|x86_64||Tumbleweed|d936892f6f32e42a9397b00c8d534ca972c1f6ff013d67c96ab2a7117b632998|
2013-09-26 11:27:12|install|PackageKit-browser-plugin|0.8.7-2.49|x86_64||Tumbleweed|a7c57e2c5f33d9b5f888187c2897131ee76cc6cb4d4fcf9697f2c02f895d9fa7|
2013-09-26 11:27:12|install|PackageKit-backend-zypp|0.8.7-2.49|x86_64||Tumbleweed|08f17f9f0d2ae59b63fbe9666afbcd3f0856f2cf0219e200c75ecb69900a15ec|
2013-09-26 11:27:12|install|libgstreamer-1_0-0|1.0.7-3.6|x86_64||Tumbleweed|c8574bfb82b6a75c0469506dc29b014e0522bfe5|
# 2013-09-26 11:27:13 PackageKit-0.8.7-2.49.x86_64.rpm installed ok
# Additional rpm output:
# Updating /etc/sysconfig/packagekit-background...
# Unknown media type in type 'all/all'
# Unknown media type in type 'all/allfiles'
# Unknown media type in type 'uri/mms'
# Unknown media type in type 'uri/mmst'
# Unknown media type in type 'uri/mmsu'
# Unknown media type in type 'uri/pnm'
# Unknown media type in type 'uri/rtspt'
# Unknown media type in type 'uri/rtspu'
#
2013-09-26 11:27:13|install|PackageKit|0.8.7-2.49|x86_64||Tumbleweed|960c065a2d444c1cd567427a0ae38be8723ab1ffa7f2944231a4ecefc526a38d|
2013-09-26 11:27:13|install|gstreamer-lang|1.0.7-3.6|noarch||Tumbleweed|5b95c6fa1df83e3a4f24f499da69056761cb1806|
2013-09-26 11:28:37|install|gnome-icon-theme-extras|3.6.2-2.1.1|noarch|root@linux-6c9j.site|openSUSE Current OSS|4d9801225ab0bb42ef0c9d9179b393f814ece11a7a0567ceff48287a8a3fc992|
ebreiss@linux-6c9j:/var/log/zypp>
Yeah, right. That issue with some gnome branding packages is there for a while already. Some of them have a newer version in 12.3-update, so zypper dup wants to switch to them which causes other packages to be downgraded to the 12.3 versions as well (libgio and libglib f.e.; those got upgraded for you to Tumbleweed now again AFAICS)…
And I think that caused your problem because of some incompatible libraries.
I would suggest to change the priority of the Tumbleweed repo (and Packman if you use that) to 98 while leaving the 12.3/openSUSE-Current repos at 99. Then a standard “zypper dup” should give you no more problems.
There are small problems with branding packages on KDE as well, and your explanation is fine. However, Tumbleweed is designed and tested by the maintainer, Greg K-H, to work with the standard repos. Using upstream branding on Tumbleweed isn’t seen as a problem. He has been asked on several occasions about repos, priorities, and use of --from. The answers are always consistent: expect package levels to flow between Tunbleweed and standard repos i.e. that’s normal; don’t change repo priorities; and use plain zypper dup. Those are the circumstances that are supported until he says otherwise.
I’ve used a higher priority for Packman in the past, even on Tumbleweed, but sometimes they have overstepped and interfered with DE components. So I now use default priorities on Tumbleweed, even for Packman.
So, why when you claim not to use this version are you still giving contrary advice here, and reopening old discussions?
Where did I reopen old discussions?
I’m giving contrary advice here to fix people’s problems!
Apparently it’s not tested in the way people use it.
Right now “zypper dup” with standard priorities does cause problems (because of those gnome/gtk/gio/whatever openSUSE branding packages).
And this should be discussed on the opensuse-factory mailinglist, as I already wrote a few times.
I don’t care that much to already have done this myself (except for the python-kde4 breakage). But why should I, if even people using Tumbleweed (that includes you) can’t be bothered to do that?
Yes, ok, I again will write an email, but this has to wait (at least) until next week…
By advising the use of repo priorities, you are in conflict with the Tumbleweed maintainer’s previous guidance. Or was it just intended as a “temporary bandage”, but not clearly stated as such? How will other users know the difference?
Tumbleweed has been running since 11.4 or thereabouts, with more or less the same methodology, and occasionally there are temporary blips. Past discussions took place here with some contribution from Greg on how best to run it, including the use of default priorities and which form of dup to use, and [for him] there was more on the factory mailing list.
Perhaps it’s you that needs to do some research here and there, as a non Tumbleweed user. Then go to the source and get the guidance changed if you think we are all going about it the wrong way. In the meantime, some of us seem to be managing ok as it is.
Not looking for a huge debate here, but on G+ Greg mentioned “zypper dup --from Tumbleweed” as a good option to make sure that f.e. KDE packages all come from the same repo. I’ve been a TW user from the beginning, and there have been occasions that ‘zypper dup’ would result in moving away from TW except for the kernel and some other packages, where the --from TW performed the update nicely. When I mentioned this on G+ Greg responded that such situtations should not, but probably could occur.
Within a context that’s sitting on G+. What’s G+? My guess is yet another mailing list interface?
I’ve been a TW user from the beginning, and there have been occasions that ‘zypper dup’ would result in moving away from TW except for the kernel and some other packages, where the --from TW performed the update nicely. When I mentioned this on G+ Greg responded that such situtations should not, but probably could occur.
As have I, and at the beginning --from was the recommended way to install the first upgrade, but much later he moved away from that. KDE or Gnome wasn’t in the repo at the beginning though.
You will also remember a long thread about a situation that in the end required --from to get a Tumbleweed kernel upgrade to install. It’s sometimes useful for blips, and probably better as a temporary solution than raising repo priorities (lest we forget that and get screwed by it on a later dup). However --from threw up problems recently when I tried it to do an upgrade, and the plain dup worked but a few packages went back to standard repo with no serious effects.
