I am currently out of town, but if anybody else is working on the packages, the packaging in X11:LXQt:git should work for most of what changes are happening with 2.0, if you need references
On 4/17/24 08:56, Shawn W Dunn wrote:
I am currently out of town, but if anybody else is working on the packages, the packaging in X11:LXQt:git should work for most of what changes are happening with 2.0, if you need references
Just as a heads up, I just noticed that even in the git repo, I didn't actually fully fix the issues from upstream. By default, LXQt is putting it's cmake related files for -devel subpackages in %{_datadir}/cmake which isn't really where they belong. They should be living in %{_qt6_cmakedir}/%{name} (expands out to /usr/lib64/cmake/package_name) just to stay consistent with what most other cmake projects use. I did patch this in libqt6xdg, with the following patch that should be relatively easily ported to the rest of things. This is probably something we should do now, rather than later, before submitting up to Factory for 2.0.0
On 4/17/24 15:07, Shawn W Dunn wrote:
On 4/17/24 08:56, Shawn W Dunn wrote:
I am currently out of town, but if anybody else is working on the packages, the packaging in X11:LXQt:git should work for most of what changes are happening with 2.0, if you need references
Just as a heads up, I just noticed that even in the git repo, I didn't actually fully fix the issues from upstream. By default, LXQt is putting it's cmake related files for -devel subpackages in %{_datadir}/cmake which isn't really where they belong. They should be living in %{_qt6_cmakedir}/%{name} (expands out to /usr/lib64/cmake/package_name) just to stay consistent with what most other cmake projects use.
I did patch this in libqt6xdg, with the following patch that should be relatively easily ported to the rest of things.
This is probably something we should do now, rather than later, before submitting up to Factory for 2.0.0 Ah. Never mind. This actually breaks things. In other packages. I'll revoke what I've submitted so far, and resubmit clean.
we're going to need to do a fair bit of testing on this release before pushing to Factory, upstreama decision to release with some components still requiring Qt5 components to remain coinstalled is probably going to bite us On April 17, 2024 10:56:31 AM CDT, Shawn W Dunn <sfalken@cloverleaf-linux.org> wrote:
I am currently out of town, but if anybody else is working on the packages, the packaging in X11:LXQt:git should work for most of what changes are happening with 2.0, if you need references
My understanding was that they will release all of them, just step by step (for some reason). But I'm not 100% sure. I checked some of your submissions and they looked fine on a first glance. I'm not sure about the libsysstat though. We had libsysstat-qt5. Shouldnt we have used the changes file from there to show some kind of continuum? In any case: if you are happy with everything feel free to accept and forward (or someone else from team). On Thu, Apr 18, 2024 at 4:16 PM Shawn W Dunn <sfalken@cloverleaf-linux.org> wrote:
we're going to need to do a fair bit of testing on this release before pushing to Factory, upstreama decision to release with some components still requiring Qt5 components to remain coinstalled is probably going to bite us
On April 17, 2024 10:56:31 AM CDT, Shawn W Dunn <sfalken@cloverleaf-linux.org> wrote:
I am currently out of town, but if anybody else is working on the packages, the packaging in X11:LXQt:git should work for most of what changes are happening with 2.0, if you need references
they've announced that qterminal is going to be on its own release cadence this time around, and that the remaining components will be staying on Qt5 until the 2.1 release, which might be a while. I dropped the -qt suffix on libsysstat because it doesn't really make any sense to keep it nothing in the release requires the Qt5 version, and the likelihood that we'd need to worry about keeping Qt5 around, then have Qt6 for the next number of years, and then keep -Qt6, and a potential -Qt7 package version around is just not very likely On April 19, 2024 12:41:17 PM CDT, Michael Vetter <mvetter@suse.com> wrote:
My understanding was that they will release all of them, just step by step (for some reason). But I'm not 100% sure. I checked some of your submissions and they looked fine on a first glance. I'm not sure about the libsysstat though. We had libsysstat-qt5. Shouldnt we have used the changes file from there to show some kind of continuum? In any case: if you are happy with everything feel free to accept and forward (or someone else from team).
On Thu, Apr 18, 2024 at 4:16 PM Shawn W Dunn <sfalken@cloverleaf-linux.org> wrote:
we're going to need to do a fair bit of testing on this release before pushing to Factory, upstreama decision to release with some components still requiring Qt5 components to remain coinstalled is probably going to bite us
On April 17, 2024 10:56:31 AM CDT, Shawn W Dunn <sfalken@cloverleaf-linux.org> wrote:
I am currently out of town, but if anybody else is working on the packages, the packaging in X11:LXQt:git should work for most of what changes are happening with 2.0, if you need references
I'm not opposed to keeping the -qtX suffixes, if others feel strongly about it, but in general, I don't like changing the names at the distribution level, away from what upstream publishes them as, when there's no particularly good reason to do so. and this major release and base library change seems like a good time to rectify some of that On April 19, 2024 12:41:17 PM CDT, Michael Vetter <mvetter@suse.com> wrote:
My understanding was that they will release all of them, just step by step (for some reason). But I'm not 100% sure. I checked some of your submissions and they looked fine on a first glance. I'm not sure about the libsysstat though. We had libsysstat-qt5. Shouldnt we have used the changes file from there to show some kind of continuum? In any case: if you are happy with everything feel free to accept and forward (or someone else from team).
On Thu, Apr 18, 2024 at 4:16 PM Shawn W Dunn <sfalken@cloverleaf-linux.org> wrote:
we're going to need to do a fair bit of testing on this release before pushing to Factory, upstreama decision to release with some components still requiring Qt5 components to remain coinstalled is probably going to bite us
On April 17, 2024 10:56:31 AM CDT, Shawn W Dunn <sfalken@cloverleaf-linux.org> wrote:
I am currently out of town, but if anybody else is working on the packages, the packaging in X11:LXQt:git should work for most of what changes are happening with 2.0, if you need references
I'm not talking about the -qt suffix. I'm talking about the changes file. Compare https://build.opensuse.org/request/show/1168684 with https://build.opensuse.org/projects/X11:LXQt/packages/libsysstat-qt5/files/l... Since its still from the same upstream repo I believe we should keep the changes file. Not create a new one. On Fri, Apr 19, 2024 at 8:40 PM Shawn W Dunn <sfalken@cloverleaf-linux.org> wrote:
I'm not opposed to keeping the -qtX suffixes, if others feel strongly about it, but in general, I don't like changing the names at the distribution level, away from what upstream publishes them as, when there's no particularly good reason to do so. and this major release and base library change seems like a good time to rectify some of that
On April 19, 2024 12:41:17 PM CDT, Michael Vetter <mvetter@suse.com> wrote:
My understanding was that they will release all of them, just step by step (for some reason). But I'm not 100% sure. I checked some of your submissions and they looked fine on a first glance. I'm not sure about the libsysstat though. We had libsysstat-qt5. Shouldnt we have used the changes file from there to show some kind of continuum? In any case: if you are happy with everything feel free to accept and forward (or someone else from team).
On Thu, Apr 18, 2024 at 4:16 PM Shawn W Dunn <sfalken@cloverleaf-linux.org> wrote:
we're going to need to do a fair bit of testing on this release before pushing to Factory, upstreama decision to release with some components still requiring Qt5 components to remain coinstalled is probably going to bite us
On April 17, 2024 10:56:31 AM CDT, Shawn W Dunn <sfalken@cloverleaf-linux.org> wrote:
I am currently out of town, but if anybody else is working on the packages, the packaging in X11:LXQt:git should work for most of what changes are happening with 2.0, if you need references
On 4/19/24 23:50, Michael Vetter wrote:
I'm not talking about the -qt suffix. I'm talking about the changes file. Compare https://build.opensuse.org/request/show/1168684 with https://build.opensuse.org/projects/X11:LXQt/packages/libsysstat-qt5/files/l...
Since its still from the same upstream repo I believe we should keep the changes file. Not create a new one.
Done, SR 1169370
participants (2)
-
Michael Vetter -
Shawn W Dunn