https://bugs.kde.org/show_bug.cgi?id=461358

--- Comment #13 from Oded Arbel <o...@geek.co.il> ---
(In reply to Nate Graham from comment #12)
> Regardless, the fix is in the packages for Plasma 5.27, so if you're using
> the packages for 5.26.something, you won't have it yet.

Apologies for the bug spam on this reportedly fixed issue, but I'm still having
problems trying to verify the fix, even though I believe I'm running the
correct build, that should include fbe608b1cd11e1b609f0f251c4d6e494cc52a5d0:

---8<---
$ kwin_wayland -v
kwin 5.26.80
---8<---

AFAIK, 5.26.80 is the pre-release version for 5.27.0, so the version I'm
running is what will be packaged as 5.27 on release and should already contain
the fix. Does that seem reasonable?

In regards to the previous conversion (after which my configuration has not
changed, but I did run some updates from the
http://archive.neon.kde.org/unstable repository), I think there's an issue with
the Neon CI - I've looked at
https://build.neon.kde.org/view/3%20unstable%20%E2%98%A3%20git%20master/job/jammy_unstable_kde_kwin/
- which is clearly labeled as "unstable git master" and that is currently
building Neon packages with the version specification of 5.26.4, even though
the logs show it is pulling from git master. Looking at
https://invent.kde.org/neon/kde/kwin/-/blob/Neon/unstable/debian/changelog , I
can see that "Neon CI" (I assume its the CI bot) recently "released" 5.26.4.

On my system it looks like this:
---8<---
$ TZ=utc ls -g --time-style=long-iso /usr/bin/kwin_wayland
-rwxr-xr-x 1 root 1702304 2022-12-01 01:02 /usr/bin/kwin_wayland
$ dpkg -l kwin-wayland
# ...
ii  kwin-wayland   4:5.26.4+p22.04+tunstable+git20221201.0102-0 amd64       
KDE window manager, wayland version, PREVIEW release
$ kwin_wayland -v
kwin 5.26.80
---8<---

Unfortunately, this is not the first time I've seen such package version
mishaps on Neon CI, and I don't expect this to be the last. Maybe that should
be taken care of as part of as the Automation & Systematization goal?

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to