Qt6 packaging: dependency lock out
Hi, I am Daniel Schurmann, a developer of the Mixxx DJ software. We are currently working on porting Mixxx to Qt6 and in order to support this, I am maintaining backports of your Qt packages for Ubuntu: https://launchpad.net/~daschuer/+archive/ubuntu/qt6-backports I am now working on updating the packages to upstream 6.2.3. unfortunately, I am locked out due to a dependency issue around the virtual package qt6-base-abi. Some packages, for instance https://packages.debian.org/de/experimental/libqt6svg6 from qtsvg have a qt6-base-abi (= 6.2.2) and a libqt6core6 (>=6.2.2) from qtbase which provides qt6-base-abi. During the update I need to build and install qtbuild first, but I cannot install the new package without uninstalling all other qt6 packages due to the fixed version in qt6-base-abi (= 6.2.2) Is this the desired behavior? For my understanding qt6-base-abi 6.2.3 includes 6.2.2. and since qtsvg is an independent source tree there shouldn't be any issue rectifying the exact abi. The other issue is that the additional libqt6core6 (>=6.2.2) dependency destroys the reason for the virtual package. For my understanding it is provided to allow any other future package to be a drop in replacement for libqt6core6. But that will not work if there are packages depending on libqt6core6 explicitly. How can we fix both issues? Is there a way to see the reason both packages are picked up by the debian helpers? Thank you for your help. Best regards, Daniel
Bug#1005134: Adding fwupd and plasma-discover-backend-fwupd as default packages to install on KDE to prompt the user for firmware updates
On 07 Feb 2022 17:36:53 + mYnDstrEAm wrote: > Please add fwupd and plasma-discover-backend-fwupd as a default package https://bugs.debian.org/1003973 is a/the bug where default installation of fwupd is discussed. > included on Debian12/KDE. This would make "Discover" show available firmware > updates. There would be a tray notification about available updates on KDE > and updating firmware can be integrated into the updating process. The plasma-discover-backend-fwupd package is already a suggest of plasma-discover, so possibly a recommends instead is requested here? I'll leave that and a possible reassignment of this bug up to the maintainers, but please don't make too hard to install KDE without discover. signature.asc Description: This is a digitally signed message part.
Processed: Re: Bug#1005134: Adding fwupd and plasma-discover-backend-fwupd as default packages to install on KDE to prompt the user for firmware updates
Processing control commands: > reassign -1 plasma-discover Bug #1005134 [src:meta-kde] Adding fwupd and plasma-discover-backend-fwupd as default packages to install on KDE to prompt the user for firmware updates Bug reassigned from package 'src:meta-kde' to 'plasma-discover'. Ignoring request to alter found versions of bug #1005134 to the same values previously set Ignoring request to alter fixed versions of bug #1005134 to the same values previously set -- 1005134: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005134 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1005134: Adding fwupd and plasma-discover-backend-fwupd as default packages to install on KDE to prompt the user for firmware updates
control: reassign -1 plasma-discover Hi, Le mardi 8 février 2022, 14:18:22 CET Diederik de Haas a écrit : > On 07 Feb 2022 17:36:53 + mYnDstrEAm wrote: > > Please add fwupd and plasma-discover-backend-fwupd as a default package > > https://bugs.debian.org/1003973 is a/the bug where default installation of > fwupd is discussed. Yes, that was also recommended by upstream on the KDE Distributions mailing list. > > included on Debian12/KDE. This would make "Discover" show available > > firmware updates. There would be a tray notification about available > > updates on KDE and updating firmware can be integrated into the updating > > process. > The plasma-discover-backend-fwupd package is already a suggest of > plasma-discover, so possibly a recommends instead is requested here? > I'll leave that and a possible reassignment of this bug up to the > maintainers, but please don't make too hard to install KDE without > discover. Yes, that’s the plan for 5.24. Not marking it pending since I’ve not actually pushed the change to Salsa just yet. The update is pending Frameworks 5.90 upload which I’m also making progress on. Happy hacking, -- Aurélien
