Re: kde-spectacle removed from kde-standard dependencies on sid/amd64
Le vendredi 28 février 2025, 20:07:08 UTC+1 shiroaz...@qq.com a écrit : > Hello, Hi, > I have noticed that today's sid upgrade has removed the `kde-spectacle` > dependency from `kde-standard` on the amd64 architecture. I have verified > this > by checking the package information at > https://packages.debian.org/sid/kde-standard, and it appears that only the > architectures [alpha, ia64, mips64el, > riscv64] now require `kde-spectacle`. yes this is intentional. Spectacle is now part of Plasma and will be pulled by Plasma 6.3.2 which I’ve uploaded earlier today and has 2 NEW packages pending reviews by the FTP Masters. So this is only transitory and I could have handled the transition more transparently. In the meantime you’re welcome to simply install kde-spectacle in case APT removed it automatically and you need it. The change is for all architectures. I’d guess the difference you’re seeing is due to some architectures not having the new version of kde-standard yet. Happy hacking, -- Aurélien
disconect
Disconect
Re: KDEPIM with SQLite3
Hi. yaros - 28.02.25, 08:50:31 MEZ: > Dnia sobota, 21 grudnia 2024 22:59:05 CET Dietz Pröpper pisze: > Howdy, […] > New akonadi installed today (24.12.2-1), but still no luck with db > migration: Thanks for reporting. I saw that Merlin reported a Debian issue about the migrator crashing: akonadi-server: Segmentation fault when using akonadi-db-migrator https://bugs.debian.org/1098891 https://bugs.debian.org/1098894 Hmmm, duplicate? First one has a strace, so maybe merge the later with the first one? I wonder whether Bug#1034561: akonadi-server: Switch default Akonadi backend to SQLite https://bugs.debian.org/1034561 would be good to consider for Trixie. This could save a lot of new Debian users who start with Trixie from trying to migrate later. While the migrator appears to crash currently, I am using SQLite3 engine on several systems with very light Akonadi load and one system with heavy duty Akonadi load (more than a million of mails). It works. Best, -- Martin
Re: KDEPIM with SQLite3
Dnia sobota, 21 grudnia 2024 22:59:05 CET Dietz Pröpper pisze: Howdy, Frank Mehnert: > I tried the migration from MySQL to Sqlite3 and failed: > > I upgraded everything to current unstable. > I started `akonadi-db-migrator --newengine sqlite`. > The assistant started and executed all steps, then tried to finish and > aborted with a core dump. MySQL is still running. Same here. As a side note, I also installed akonadi-backend-sqlite, but still a core dump. Regards, Dietz New akonadi installed today (24.12.2-1), but still no luck with db migration: yaros@DebYan:~$ akonadi-db-migrator --newengine sqlite Stopping Akonadi service... Backup file /home/yaros/.config/akonadi/akonadiserverrc.bkp already exists. Overwrite? [(y)es/(N)o] y Reading datadir from the MariaDB server failed. Got the following error when executing the 'mysql' command line client ERROR 1049 (42000): Unknown database 'mysql' FATAL ERROR: Upgrade failed org.kde.pim.akonadiserver: Running DB initializer org.kde.pim.akonadiserver: DB initializer done org.kde.pim.akonadiserver: Running DB initializer Naruszenie ochrony pamięci (zrzut pamięci)
Re: KDEPIM with SQLite3
Martin Steigerwald - 28.02.25, 10:13:54 MEZ: > I saw that Merlin reported a Debian issue about the migrator crashing: > > akonadi-server: Segmentation fault when using akonadi-db-migrator > > https://bugs.debian.org/1098891 > > https://bugs.debian.org/1098894 > > Hmmm, duplicate? First one has a strace, so maybe merge the later with > the first one? Another thing: On quick search I did not find an upstream¹ report about this issue. Would someone of you consider to look a bit more thoroughly whether there is one and if not report one and paste the link here? I think an upstream report is okay to do since 24.12.2 is really the most recent stable version of KDEPIM. That would help. It might be good to run the migrator in a gdb session for the report. On a segmentation fault there usually is a kernel log entry. That may also help to pinpoint roughly in which file the segmentation fault happened. [1] https://bugs.kde.org Thank you, -- Martin
