15.3 as well please, do send update mails to the update mailing list
for 15.3 as well please. There were already a few updates on 15.3 but the updates list archive shows only stuff about leap 15.2 updates. Please dont think so low and care so little for this hybrid kind of leap 15.3 with its SLES bastardisation. This whole leap 15.3 adventure more and more smells like considering it the unloved sibling of god knows whom or what. :(
Am 04.06.21 um 16:17 schrieb cagsm:
for 15.3 as well please. There were already a few updates on 15.3 but the updates list archive shows only stuff about leap 15.2 updates.
Please dont think so low and care so little for this hybrid kind of leap 15.3 with its SLES bastardisation. This whole leap 15.3 adventure more and more smells like considering it the unloved sibling of god knows whom or what.
:(
Leap 15.3, KDE, fresh installation except /home. No problems, so far:-) Thanks to openSUSE. Peter
On Fri, Jun 04, 2021 at 04:17:52PM +0200, cagsm wrote:
for 15.3 as well please. There were already a few updates on 15.3 but the updates list archive shows only stuff about leap 15.2 updates.
Please dont think so low and care so little for this hybrid kind of leap 15.3 with its SLES bastardisation. This whole leap 15.3 adventure more and more smells like considering it the unloved sibling of god knows whom or what.
regular 15.3 notices are being sent out. They are hiding occasionaly as "openSUSE Backports SLE-15-SP3" too, I need to report those as openSUSE Leap 15.3 too. I need to figure out a way to announce the SLE imported updates. Currently I am much more worried and more focused on that this SLE imported update repo is having inconsistencies. Ciao, Marcus
On Sat, Jun 5, 2021 at 2:24 PM Marcus Meissner <meissner@suse.de> wrote:
They are hiding occasionaly as "openSUSE Backports SLE-15-SP3" too, I need to report those as openSUSE Leap 15.3 too. I need to figure out a way to announce the SLE imported updates. Currently I am much more worried and more focused on that this SLE imported update repo is having inconsistencies.
Is the current zypper lu and packagekit updater applet inconsistency the symptom of this problem? It never occurred to me that packagekit and zypper get their update information from different places spaces metadatas?
<https://paste.opensuse.org/61298387> https://paste.opensuse.org/61298387
ty
On 05.06.2021 16:07, cagsm wrote:
On Sat, Jun 5, 2021 at 2:24 PM Marcus Meissner <meissner@suse.de> wrote:
They are hiding occasionaly as "openSUSE Backports SLE-15-SP3" too, I need to report those as openSUSE Leap 15.3 too. I need to figure out a way to announce the SLE imported updates. Currently I am much more worried and more focused on that this SLE imported update repo is having inconsistencies.
Is the current zypper lu and packagekit updater applet inconsistency the symptom of this problem? It never occurred to me that packagekit and zypper get their update information from different places spaces metadatas?
"zypper lu" checks package versions. "zypper lp" checks patch database. Update applet (at least that I have before me - gpk-update-viewer) combines both information. As long as you are using only default repositories you are not supposed to see anything except patches. Any updated package listed by "zypper lu" should belong to some patch listed by "zypper lp".
On Sat, Jun 5, 2021 at 3:15 PM Andrei Borzenkov <arvidjaar@gmail.com> wrote:
"zypper lu" checks package versions. "zypper lp" checks patch database. Update applet (at least that I have before me - gpk-update-viewer) combines both information.
interesting. so far i have almost like 100% of my time only used zypper up zypper up right now doesnt do anything. all "up"(up = updates? packages?) applied i guess.
As long as you are using only default repositories you are not supposed to see anything except patches. Any updated package listed by "zypper lu" should belong to some patch listed by "zypper lp".
i have rarely used zypper lp and zypper patch. right now zypper lp lists that bash stuff that the packagekit updater also fusses about. i am always using default repositories. what is it supposed to mean that one should only see patches nothing else. heck i have never used zypper lp or patch so far. Was i wrong all my opensuse experience in the past? when i issue a zypper patch right now, it kinda outputs a mile long conflicting packages and patches output or something, about readline etc or something. i didnt explore further and i didnt apply that patch or resolve any conflicts it asks me for a decision at the bottom of this lengthy conflict text. what now? is the mere usage of zypper up not sufficient? or do zypper patch (zypper lp) also include everything that a zypper up would bring in? thank you.
On 05.06.2021 16:44, cagsm wrote:
On Sat, Jun 5, 2021 at 3:15 PM Andrei Borzenkov <arvidjaar@gmail.com> wrote:
"zypper lu" checks package versions. "zypper lp" checks patch database. Update applet (at least that I have before me - gpk-update-viewer) combines both information.
interesting. so far i have almost like 100% of my time only used zypper up zypper up right now doesnt do anything.
bor@leap15:~> sudo zypper up [sudo] password for root: Loading repository data... Reading installed packages... The following 4 items are locked and will not be changed by any action: Available: kernel-firmware pavucontrol ucode-amd ucode-intel The following 4 packages are going to be upgraded: MozillaThunderbird python3-py yast2 yast2-logs 4 packages to upgrade. Overall download size: 53.4 MiB. Already cached: 0 B. After the operation, additional 10.7 KiB will be used. Continue? [y/n/v/...? shows all options] (y): n bor@leap15:~>
all "up"(up = updates? packages?) applied i guess.
May be. yast2 appeared in the last hours. Others I did not apply intentionally. Notice that there is no bash because there are no updated packages, just patch info.
As long as you are using only default repositories you are not supposed to see anything except patches. Any updated package listed by "zypper lu" should belong to some patch listed by "zypper lp".
i have rarely used zypper lp and zypper patch. right now zypper lp lists that bash stuff that the packagekit updater also fusses about.
i am always using default repositories. what is it supposed to mean that one should only see patches nothing else. heck i have never used zypper lp or patch so far. Was i wrong all my opensuse experience in the past?
It is up to you. Patches include additional information like CVE numbers that you can query before installation, this information is not directly available for updated packages. Although right now almost every "see this link for additional information" for Leap 15.3 patches ends up with "you do not have permissions to view this bug". End result is the same. When you "install" patch you at the end just install packages.
when i issue a zypper patch right now, it kinda outputs a mile long conflicting packages and patches output or something, about readline etc or something. i didnt explore further and i didnt apply that patch or resolve any conflicts it asks me for a decision at the bottom of this lengthy conflict text.
what now? is the mere usage of zypper up not sufficient? or do zypper patch (zypper lp) also include everything that a zypper up would bring in?
When (if) the problem with patches imported from SLE is solved, "zypper patch" should be sufficient. As long as you do not have any additional repositories.
On 05/06/2021 15.44, cagsm wrote:
i have rarely used zypper lp and zypper patch. right now zypper lp lists that bash stuff that the packagekit updater also fusses about.
i am always using default repositories. what is it supposed to mean that one should only see patches nothing else. heck i have never used zypper lp or patch so far. Was i wrong all my opensuse experience in the past?
For the "official distribution", ie, not using any external or extra repositories, you only need patches. However, the moment you add any other repository - say packman, say Mozilla from OBS - that is not enough, because close to none publish patches. That was the situation till 15.2. -- Cheers / Saludos, Carlos E. R. (from 15.2 x86_64 at Telcontar)
On Sat, Jun 5, 2021 at 3:15 PM Andrei Borzenkov <arvidjaar@gmail.com> wrote:
"zypper lu" checks package versions. "zypper lp" checks patch database. Update applet (at least that I have before me - gpk-update-viewer) combines both information.
while we are at it ;) learning terminology of this kde plasma desktop stuff and all, if you help to explain, what is that update popups are called on my kde plasma desktop? I kind of remebered packagekit updater or something from past KDE, but apparently there are things named plasmoid little addons or whatever these days I have learnt. As the popup and its (right click) config window in the try icon bar (proper name?) come up with a very brief configuration window, but I see nor real applications names except for "software update settings - plasma" it its title. I see no menu on this window, no copyright or project or developers or teams name or anything. I cant yet name all these parts of linux kde plasma gui properly at all I guess. zypper se packagkit also lists me that name as a package as being installed on this 15.3 system, maybe thats just a intermediate layer any more? kde "start menu" doesnt list me hits when i try to go for packagekit, guess no gui component of packagekit any more. Or what I knew as packagekit applet from older suse releases was never named that way to begin with? ty.
On 05.06.2021 17:08, cagsm wrote:
On Sat, Jun 5, 2021 at 3:15 PM Andrei Borzenkov <arvidjaar@gmail.com> wrote:
"zypper lu" checks package versions. "zypper lp" checks patch database. Update applet (at least that I have before me - gpk-update-viewer) combines both information.
while we are at it ;) learning terminology of this kde plasma desktop stuff and all, if you help to explain, what is that update popups are called on my kde plasma desktop? I kind of remebered packagekit
I do not know.
updater or something from past KDE, but apparently there are things named plasmoid little addons or whatever these days I have learnt. As the popup and its (right click) config window in the try icon bar (proper name?) come up with a very brief configuration window, but I see nor real applications names except for "software update settings - plasma" it its title. I see no menu on this window, no copyright or project or developers or teams name or anything. I cant yet name all these parts of linux kde plasma gui properly at all I guess.
zypper se packagkit also lists me that name as a package as being installed on this 15.3 system, maybe thats just a intermediate layer any more? kde "start menu" doesnt list me hits when i try to go for packagekit, guess no gui component of packagekit any more. Or what I knew as packagekit applet from older suse releases was never named that way to begin with?
packagekitd is backend. It provides D-Bus interface which is used by various user facing GUI. PackageKit project includes simple GUI (gpk-update-viewer) which is launched e.g. on Xfce (and GNOME) to perform installation. "g" in the name stands for "GTK" (or may be "GNOME"), under KDE it is some native implementation. Even gpk-update-viewer does not perform periodical checks, something else is used to refresh repositories and call gpk-update-viewer as needed (package-update-indicator or gnome-software).
On Sat, Jun 5, 2021 at 4:22 PM Andrei Borzenkov <arvidjaar@gmail.com> wrote:
while we are at it ;) learning terminology of this kde plasma desktop stuff and all, if you help to explain, what is that update popups are called on my kde plasma desktop? I kind of remebered packagekit I do not know.
I think i kinda found the rpm that contains this called: plasma5-pk-updates rpm -qi plasma5-pk-updates-0.3.2-bp153.1.28.x86_64 Name : plasma5-pk-updates Version : 0.3.2 Release : bp153.1.28 Architecture: x86_64 Install Date: Wed 28 Apr 2021 08:06:44 PM CEST Group : System/Packages Size : 246065 License : GPL-3.0-or-later Signature : RSA/SHA256, Sat 06 Mar 2021 12:00:40 PM CET, Key ID 9c214d4065176565 Source RPM : plasma5-pk-updates-0.3.2-bp153.1.28.src.rpm Build Date : Sat 06 Mar 2021 12:00:25 PM CET Build Host : hci-cnode2-m1 Relocations : (not relocatable) Packager : https://bugs.opensuse.org Vendor : openSUSE URL : https://www.kde.org/ Summary : Software Update Manager for Plasma Description : Plasma applet for software updates using PackageKit. Distribution: SUSE Linux Enterprise 15 SP3 === the "start menu" of kde plasma, is apparently named "Application Launcher" (triggered via Alt+F1), the lower bar area is apparently named "Task Manager" or panel or such? Or it has panels? ty.
On 6/5/21 10:37 PM, cagsm wrote:
On Sat, Jun 5, 2021 at 2:24 PM Marcus Meissner <meissner@suse.de> wrote:
They are hiding occasionaly as "openSUSE Backports SLE-15-SP3" too, I need to report those as openSUSE Leap 15.3 too. I need to figure out a way to announce the SLE imported updates. Currently I am much more worried and more focused on that this SLE imported update repo is having inconsistencies.
Is the current zypper lu and packagekit updater applet inconsistency the symptom of this problem? It never occurred to me that packagekit and zypper get their update information from different places spaces metadatas?
This is certainly possible, "patch" updates get additional metadata that tumbleweed updates and updates from additional repo's don't get. -- Simon Lees (Simotek) http://simotek.net Emergency Update Team keybase.io/simotek SUSE Linux Adelaide Australia, UTC+10:30 GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B
participants (6)
-
Andrei Borzenkov -
cagsm -
Carlos E. R. -
Marcus Meissner -
Peter McD -
Simon Lees