Update requests for packages built by Manjaro developers

[Zesko]

@GaVenga

Now testing: 253.2-1 from Arch stable

It is already in the unstable branch.

$ systemctl --version
systemd 253 (253.2-1-manjaro)

[Yochanan]

@GaVenga

253.2-1 from Arch stable

@Zesko

It is already in the unstable branch.

Indeed. It was in Manjaro unstable before it was in Arch stable.

@GaVenga Before fiddling around with Arch packages, make sure you’re up to date on Manjaro first.

[GaVenga]

Gnome-shell-extension “Dash-To-Panel”
New virgin on GitHupe

Release GNOME 44 maintenance 3 · home-sweet-gnome/dash-to-panel

[Yochanan]

Sorry, are you running GNOME 44? Do you need some maintenance?

Since I’m testing GNOME 44, I already updated it last week in the 44 branch.

[GaVenga]

@Yochanan

are you running GNOME 44

Not running, but testing
You are faster than light (you know Perry Rhodan?)
Btw.: V56 is running on Gnome43 too - good for our 2 monitor PC - former Vs were “unstable”

[Yochanan]

Well, since 56 is also compatible with GNOME 43, I’ve pushed it now.

[cscs]

plasma-theme-minisforum is entirely out of date and incompatible now.

(depends on plasma5-themes-breath)

Example here:

Cannot progress with system updates - "plasma5-themes-breath" dependancy

I’m currently using a Minisforum UM700 Manjaro Edition as my daily driver. I just updated to the 6.9.0-1 kernel, and I have 767 updates to install; however, the GUI updater keeps failing, and when I try updating via terminal, this is what I get: sudo pacman -Syu [sudo] password for zacharyb: :: Synchronizing package databases… core is up to date extra is up to date community is up to date multilib is up to date :: Starting full system upgrade… :: Replace baloo5 with extra/baloo? [Y/n] …

[cscs]

Plasma packages related slimbook are in a similar state.

Example here:

Dependency error on latest update

Ah, had not realized there were even more packages involved. This should probably be brought to the attention of packager people @Yochanan @philm I really do not know whats contained in that package. But I might guess its also not compatible with plasma6. For now you will either need to wait, or bite the bullet and remove them.

Its beginning to look like a lot of these OEM/partnership packages are specifically being missed.
Which is probably not very desirable.

[cscs]

peruse has dated plasma5 deps and should be updated or removed.

[Yochanan]

@cscs

peruse

It’s unmaintained and nothing requires it. I’ll drop it from the repos.

[cscs]

I guess octopi needs some love too?

Octopi doesn't start after qtermwidget upgrade

octopi octopi: error while loading shared libraries: libqtermwidget5.so.1: cannot open shared object file: No such file or directory

[Yochanan]

@cscs

plasma-theme-minisforum

@cscs

Plasma packages related slimbook

The old incompatible OEM theme packages were dropped from the repos earlier.

@cscs

octopi

It’s is fixed now.

[pheiduck]

@Yochanan spectre-meltdown-checker has a False positive for CVE-2017-5715 on linux 6.9, retpoline not recognized · Issue #490 · speed47/spectre-meltdown-checker · GitHub

The Reporter also added a solution for Linux 6.9.x
RETPOLINE check needs to be replaced by this:

grep -q '^CONFIG_\(MITIGATION_\)\?RETPOLINE=y'

I am not sure how fast the maintainer of the project will be to add this fix.
Not a April fool but it was reported on 4/1

[Yochanan]

@pheiduck

spectre-meltdown-checker

First of all, that’s packaged by Manjaro, not Arch. Note I moved your reply to the proper thread.

@pheiduck

…[it] has a false positive…

That’s an upstream issue, not a packaging issue.

I’m going to drop it from repos. No one knows what it is, it’s no longer properly maintained and it’s obviously causing confusion.

Problem solved.

[Teo]

I found it was a really nice tool.

[Yochanan]

Not anymore, apparently. Either way, it’s just a script, download it and run it. No need for it to be packaged.

This is not a place for discussion. The thread is designed for one reason and one reason only.

Off-topic discussion may self-destruct with no warning.

[pheiduck]

It does not hurt for me to not have it installed on the system. If I need it I will grab the script.

[Aragorn]

@Yochanan

I’m going to drop it from repos. No one knows what it is, it’s no longer properly maintained and it’s obviously causing confusion.

1. It is an optional requirement — functionally, not packaging-wise — for kinfocenter, and possibly for similar tools in other desktop environments.

2. Considering that I received an update for it only a few days ago, I’d say that it is still being maintained.

3. I did not install this package myself. It was pushed onto my system during one of the updates — possibly about two or three years ago — so the Manjaro team must have considered it essential at the time.

[Teo]

It still shows a lot of stuff. Maybe not the newest vulnerabilities (last update to git about a year ago, although the manjaro package was updated at least 5 times in that period?), but many older ones. I too vote for leaving it. Maybe not installed by default but in the repos. And maybe with a note in the description about the 1 false positive it gives. And problem solved.

[pheiduck]

And at least now, the CVE numbers are incorrect as Linux has an own CA.