Re: Collection of packaging notes
On Fri, Nov 10, 2023 at 6:15 AM Christophe Marin wrote: > > Hello, > > On mercredi 1 novembre 2023 11:55:08 CET Christophe Marin wrote: > > Hello, > > > > With various alpha coming out soon, here are the notes added to my packages > > when I started packaging snapshots and still present. > > > > I now merged the frameworks and plasna packages in our openSUSE KDE repo to > see how the build behave. The frameworks builds went fine, but I can't say the > same about plasma. > > Some background: > For openSUSE, we want to give users the opportunity to choose when they want > to > migrate to plasma 6. The plasma packages won't be coinstallable, but they will > coexist for a while. > You're really asking for hard mode, aren't you? :) > From a packaging pov, we also make use of the CMake config name rather than > the corresponding -devel package when we need some build dependencies. > In most cases, the CMake config name will persist, even if the distro package > name > changes or upstream code moves to a different place. > > 3 different issues appeared with plasma 6 alpha: > > - The CMake config names are identical for certain core libraries: > KDecoration2, KPipeWire, KScreenLocker, KsysGuard, LayerShellQt, > LibKWorkspace, > LibTaskManager (and Breeze but it's slightly less problematic) > The versions emitted aren't the same, so you can use version ranges, e.g.: # kf5 version BuildRequires: (cmake(KPipeWire) >= 5.26 with cmake(KPipeWire) < 5.27.80) # kf6 version BuildRequires: cmake(KPipeWire) >= 5.27.80 > - The CMake config files for DBus interface are not versioned: > KRunnerAppDBusInterface, KWinDBusInterface, KSMServerDBusInterface, > ScreenSaverDBusInterface > This should not be a problem since the devel packages shouldn't be co-installable in any circumstance. > - The libksysguard libraries soversion weren't bumped. It's not only a > problem for > building plasma 5 and plasma 6. KSysguard is also an optional dependency > for kdevelop. > Well, okay, this is an issue. You'll also run into this with KUserFeedback. -- 真実はいつも一つ！/ Always, there's only one truth!
Re: Collection of packaging notes
Am Freitag, 10. November 2023, 12:36:09 CET schrieb Jonathan Riddell: > On Fri, 10 Nov 2023 at 10:55, Christophe Marin wrote: > > > - The libksysguard libraries soversion weren't bumped. It's not only a > > problem for > > building plasma 5 and plasma 6. KSysguard is also an optional dependency > > for kdevelop. > > I've bumped the soversions in libksysguard now. (I'll look at doing the > KFification for kuserfeedback too.) > > I've also release noted that ksysguard the app is dead and should be > removed from distros, it hasn't been released for over 2 years and hasn't > been ported. The Ksysguard dependency of kdevelop mentioned here is libksysguard which has a CMake name of ksysguard confusingly. > Jonathan David
Re: Collection of packaging notes
On Fri, 10 Nov 2023 at 10:55, Christophe Marin wrote: > 3 different issues appeared with plasma 6 alpha: > > - The CMake config names are identical for certain core libraries: > KDecoration2, KPipeWire, KScreenLocker, KsysGuard, LayerShellQt, > LibKWorkspace, > LibTaskManager (and Breeze but it's slightly less problematic) > > - The CMake config files for DBus interface are not versioned: > KRunnerAppDBusInterface, KWinDBusInterface, KSMServerDBusInterface, > ScreenSaverDBusInterface > As discussed on Matrix our assumption is that Plasma 5 and 6 aren't packaged together, a single version of Plasma should be packaged only with the same version. > - The libksysguard libraries soversion weren't bumped. It's not only a > problem for > building plasma 5 and plasma 6. KSysguard is also an optional dependency > for kdevelop. > I've bumped the soversions in libksysguard now. (I'll look at doing the KFification for kuserfeedback too.) I've also release noted that ksysguard the app is dead and should be removed from distros, it hasn't been released for over 2 years and hasn't been ported. Jonathan
Re: Collection of packaging notes
Hello, On mercredi 1 novembre 2023 11:55:08 CET Christophe Marin wrote: > Hello, > > With various alpha coming out soon, here are the notes added to my packages > when I started packaging snapshots and still present. > I now merged the frameworks and plasna packages in our openSUSE KDE repo to see how the build behave. The frameworks builds went fine, but I can't say the same about plasma. Some background: For openSUSE, we want to give users the opportunity to choose when they want to migrate to plasma 6. The plasma packages won't be coinstallable, but they will coexist for a while. >From a packaging pov, we also make use of the CMake config name rather than the corresponding -devel package when we need some build dependencies. In most cases, the CMake config name will persist, even if the distro package name changes or upstream code moves to a different place. 3 different issues appeared with plasma 6 alpha: - The CMake config names are identical for certain core libraries: KDecoration2, KPipeWire, KScreenLocker, KsysGuard, LayerShellQt, LibKWorkspace, LibTaskManager (and Breeze but it's slightly less problematic) - The CMake config files for DBus interface are not versioned: KRunnerAppDBusInterface, KWinDBusInterface, KSMServerDBusInterface, ScreenSaverDBusInterface - The libksysguard libraries soversion weren't bumped. It's not only a problem for building plasma 5 and plasma 6. KSysguard is also an optional dependency for kdevelop. Christophe
Re: libkexiv2, libkdcraw (Re: Collection of packaging notes)
On Fri, Nov 3, 2023 at 12:57 PM Albert Astals Cid wrote: > El dimecres, 1 de novembre de 2023, a les 13:25:42 (CET), Friedrich W. H. > Kossebau va escriure: > > Am Mittwoch, 1. November 2023, 11:55:08 CET schrieb Christophe Marin: > > > With various alpha coming out soon, here are the notes added to my > > > packages > > > when I started packaging snapshots and still present. > > > > Thanks for the report. > > > > Everyone: > > Could we perhaps establish some wiki page where such things could be > > tracked? > > > I don't particularly think wiki pages are good for tracking issues, we > have > issue trackers for that ;) > > I've proposed elsewhere to re-use the release-service issue tracker, but > honestly I've no idea if anyone can create issues here > https://invent.kde.org/teams/release-service/issues/-/issues/ > or only team members, if it's only team members, it's not a great place to > put > things i guess unless we add lots of folks to the team (which i'm not > against > but they may be). > I have now created https://invent.kde.org/teams/release-service/qt6-mega-release to help keep the issues here separate from the ones you've been using to track and manage the Gear releases. Issues can be created by anyone, but certain actions on those issues - such as moving them around the board, labelling them, etc. do require membership of the group at the reporter or developer level. See https://docs.gitlab.com/ee/user/permissions.html for more information on this. Cheers, Ben > > Cheers, > Albert > > > > - Non frameworks modules installing libKF*.so > > > libkexiv2 (libKF6KExiv2.so) > > > > Any code ideas for naming it, given there is already a number suffix, > coming > > from the library that is wrapped? > > > > Similar need also for libkomparediff2, where the 2 is referring to > diffing 2 > > things, not a version number. > > > > > libkdcraw (libKF6KDcraw.so) > > > > I have an old patch locally somehow never finished, will brush up as MR > > tonight hopefully. (promised in > https://invent.kde.org/graphics/libkdcraw/-/ > > merge_requests/9#note_646025 ) > > > > Cheers > > Frriedrich > > > > >
Re: libkexiv2, libkdcraw (Re: Collection of packaging notes)
El dimecres, 1 de novembre de 2023, a les 13:25:42 (CET), Friedrich W. H. Kossebau va escriure: > Am Mittwoch, 1. November 2023, 11:55:08 CET schrieb Christophe Marin: > > With various alpha coming out soon, here are the notes added to my > > packages > > when I started packaging snapshots and still present. > > Thanks for the report. > > Everyone: > Could we perhaps establish some wiki page where such things could be > tracked? I don't particularly think wiki pages are good for tracking issues, we have issue trackers for that ;) I've proposed elsewhere to re-use the release-service issue tracker, but honestly I've no idea if anyone can create issues here https://invent.kde.org/teams/release-service/issues/-/issues/ or only team members, if it's only team members, it's not a great place to put things i guess unless we add lots of folks to the team (which i'm not against but they may be). Cheers, Albert > > - Non frameworks modules installing libKF*.so > > libkexiv2 (libKF6KExiv2.so) > > Any code ideas for naming it, given there is already a number suffix, coming > from the library that is wrapped? > > Similar need also for libkomparediff2, where the 2 is referring to diffing 2 > things, not a version number. > > > libkdcraw (libKF6KDcraw.so) > > I have an old patch locally somehow never finished, will brush up as MR > tonight hopefully. (promised in https://invent.kde.org/graphics/libkdcraw/-/ > merge_requests/9#note_646025 ) > > Cheers > Frriedrich
Re: libkexiv2, libkdcraw (Re: Collection of packaging notes)
Am Mittwoch, 1. November 2023, 13:25:42 CET schrieb Friedrich W. H. Kossebau: > Am Mittwoch, 1. November 2023, 11:55:08 CET schrieb Christophe Marin: > > - Non frameworks modules installing libKF*.so > > libkexiv2 (libKF6KExiv2.so) > > Any code ideas for naming it, given there is already a number suffix, coming > from the library that is wrapped? > > Similar need also for libkomparediff2, where the 2 is referring to diffing 2 > things, not a version number. MR: https://invent.kde.org/graphics/libkexiv2/-/merge_requests/25 > > libkdcraw (libKF6KDcraw.so) > > I have an old patch locally somehow never finished, will brush up as MR > tonight hopefully. (promised in https://invent.kde.org/graphics/libkdcraw/-/ > merge_requests/9#note_646025 ) MR: https://invent.kde.org/graphics/libkdcraw/-/merge_requests/12 Both with list of further MRs to adapt known-to-me consumers Cheers Friedrich
Re: Collection of packaging notes
> > If not, then why not fix any misnaming while we change names anyway. > Go for it :) Jonathan
Re: Collection of packaging notes
Am Mittwoch, 1. November 2023, 13:30:03 CET schrieb Jonathan Riddell: > One quick question, is naming non-frameworks libKF6foo really a problem we > need to fix? Given all the other issues... What is in a name... usually some semantics. We could also call random libraries libdsafwef or libPlasmaFoo (while unrelated to Plasma), would that be a good idea? If not, then why not fix any misnaming while we change names anyway. Cheers Friedrich
Re: Collection of packaging notes
Thanks for your e-mail. It covers more than Frameworks so I'm including release-team@ too. One quick question, is naming non-frameworks libKF6foo really a problem we need to fix? Given all the other issues... Jonathan On Wed, 1 Nov 2023 at 10:55, Christophe Marin wrote: > Hello, > > With various alpha coming out soon, here are the notes added to my > packages > when I started packaging snapshots and still present. > > I'm well aware that some of these modules won't be present in the first > releases. > > First, the most annoying issue: > Plasma still didn't bump all their libraries soname. That's a major > annoyance > for packagers. > > - Conflicting files (not mentioned in the other thread) > kcm_trash.desktop is installed by both kio (kf5) and kio-extras (kf6) > > - Conflicting translation catalog names: > plasma-integration (plasmaintegration5) > kuserfeedback > > - Misnamed libraries: > kmail-account-wizard (liblibaccountwizard.so) > ktextaddons (liblibvoskspeechtotext.so) > > - Non frameworks modules installing libKF*.so > ktextaddons (various libraries) > konqueror (libKF6Konq.so) > libksane (libKF5Sane5.so) > kweathercore (libKF6KWeatherCore.so) > libktorrent (libKF5Torrent.so) > libkexiv2 (libKF6KExiv2.so) > libkdcraw (libKF6KDcraw.so) > baloo-widgets (libKF6BalooWidgets.so) > kmoretools (libKF6MoreTools.so) > libkscreen (libKF6Screen.so, libKF6ScreenDpms.so) > > - Wrong install location for knewstuff files: > khangman > kturtle > > - Wrong install location for CMake files: > qqc2-breeze-style (still uses KF5QQC2BreezeStyle) > > - old install location: > kalgebra (/usr/share/katepart5. Note: syntax-highlighting won't ignore the > file, but it's not the default location) > ksystemlog (/usr/share/kxmlgui5/ksystemlog) > > - Modules still using QQC1: > kdeplasma-addons (applets/fifteenPuzzle) > > - build dependency issues: > plasma5support (links and requires QtGui but doesn't search for it at > build > time) > kinfocenter (requires kpackage at build time but doesn't seem to need it) > > > Christophe > > > >
libkexiv2, libkdcraw (Re: Collection of packaging notes)
Am Mittwoch, 1. November 2023, 11:55:08 CET schrieb Christophe Marin: > With various alpha coming out soon, here are the notes added to my packages > when I started packaging snapshots and still present. Thanks for the report. Everyone: Could we perhaps establish some wiki page where such things could be tracked? > - Non frameworks modules installing libKF*.so > libkexiv2 (libKF6KExiv2.so) Any code ideas for naming it, given there is already a number suffix, coming from the library that is wrapped? Similar need also for libkomparediff2, where the 2 is referring to diffing 2 things, not a version number. > libkdcraw (libKF6KDcraw.so) I have an old patch locally somehow never finished, will brush up as MR tonight hopefully. (promised in https://invent.kde.org/graphics/libkdcraw/-/ merge_requests/9#note_646025 ) Cheers Frriedrich
Collection of packaging notes
Hello, With various alpha coming out soon, here are the notes added to my packages when I started packaging snapshots and still present. I'm well aware that some of these modules won't be present in the first releases. First, the most annoying issue: Plasma still didn't bump all their libraries soname. That's a major annoyance for packagers. - Conflicting files (not mentioned in the other thread) kcm_trash.desktop is installed by both kio (kf5) and kio-extras (kf6) - Conflicting translation catalog names: plasma-integration (plasmaintegration5) kuserfeedback - Misnamed libraries: kmail-account-wizard (liblibaccountwizard.so) ktextaddons (liblibvoskspeechtotext.so) - Non frameworks modules installing libKF*.so ktextaddons (various libraries) konqueror (libKF6Konq.so) libksane (libKF5Sane5.so) kweathercore (libKF6KWeatherCore.so) libktorrent (libKF5Torrent.so) libkexiv2 (libKF6KExiv2.so) libkdcraw (libKF6KDcraw.so) baloo-widgets (libKF6BalooWidgets.so) kmoretools (libKF6MoreTools.so) libkscreen (libKF6Screen.so, libKF6ScreenDpms.so) - Wrong install location for knewstuff files: khangman kturtle - Wrong install location for CMake files: qqc2-breeze-style (still uses KF5QQC2BreezeStyle) - old install location: kalgebra (/usr/share/katepart5. Note: syntax-highlighting won't ignore the file, but it's not the default location) ksystemlog (/usr/share/kxmlgui5/ksystemlog) - Modules still using QQC1: kdeplasma-addons (applets/fifteenPuzzle) - build dependency issues: plasma5support (links and requires QtGui but doesn't search for it at build time) kinfocenter (requires kpackage at build time but doesn't seem to need it) Christophe
