Re: Bug with sev: grave while new package waiting
Hello, >please check if rebuilding works with the version in experimental, in that case >you will need to do something like =5.9, and compute that value at runtime, >rather than hardcoding it >(so a binNMU will work). please fix the stuff I pointed in the rfs, and discard the qt commit. Qt folks told me that stuff should probably auto-fix when qt will finish building, so this bug is not worth the effort in fixing it. (and meh, using experimental is a source of similar breakages anyway) G.
Re: Bug with sev: grave while new package waiting
>> "libqt5core5a (<<5.10)" this will make it uninstallable when 5.10 goes in >> unstable... >> isn't it better to just make it compatible with new qt stack? I don't want >> to make qt folks >> sad. >hm, maybe i'm misunderstanding the problem, but i thought the applet >only works with the qt version it was compiled with. is it even possible >to build a package for unstable with a library from experimental? or is >there a way to make it compatible with both versions? please check if rebuilding works with the version in experimental, in that case you will need to do something like =5.9, and compute that value at runtime, rather than hardcoding it (so a binNMU will work). see src:virtualbox-ext-pack to see how you can feed such values from rules file. And please get in touch with qt folks, maybe they already have something to do that. G. signature.asc Description: PGP signature
Re: Bug with sev: grave while new package waiting
Hi, On 03/15/2018 01:05 PM, Gianfranco Costamagna wrote: > Hello, >> Thanks, i've added some commits and specified the qt version and pushed >> everything to salsa. > > > please also address the stuff on RFS bug i already pushed those changes a few weeks ago ;) > and... > --with=autoreconf > isn't this useless too? ah, yes, you're right. pushed. > "libqt5core5a (<<5.10)" this will make it uninstallable when 5.10 goes in > unstable... > isn't it better to just make it compatible with new qt stack? I don't want to > make qt folks > sad. hm, maybe i'm misunderstanding the problem, but i thought the applet only works with the qt version it was compiled with. is it even possible to build a package for unstable with a library from experimental? or is there a way to make it compatible with both versions? cheers, muri signature.asc Description: OpenPGP digital signature
Re: Bug with sev: grave while new package waiting
Hello, >Thanks, i've added some commits and specified the qt version and pushed >everything to salsa. please also address the stuff on RFS bug and... --with=autoreconf isn't this useless too? "libqt5core5a (<<5.10)" this will make it uninstallable when 5.10 goes in unstable... isn't it better to just make it compatible with new qt stack? I don't want to make qt folks sad. G.
Re: Bug with sev: grave while new package waiting
Hi, On 03/15/2018 10:48 AM, Gianfranco Costamagna wrote: > Hello, > >> there is a bug with severity: grave in usbguard, because of a libqt5 >> version incompatibility (#892045) and there is already a new version of >> usbguard waiting to be sponsored. Should i fix the bug in the new >> version or should i fix it in the version thats already in the archive? > > > I'm taking the new version, feel free to fix it on top of the new one. > (the new version has some issues, so maybe we will do only one upload) Thanks, i've added some commits and specified the qt version and pushed everything to salsa. cheers, muri signature.asc Description: OpenPGP digital signature
Re: Bug with sev: grave while new package waiting
Hello, >there is a bug with severity: grave in usbguard, because of a libqt5 >version incompatibility (#892045) and there is already a new version of >usbguard waiting to be sponsored. Should i fix the bug in the new >version or should i fix it in the version thats already in the archive? I'm taking the new version, feel free to fix it on top of the new one. (the new version has some issues, so maybe we will do only one upload) G.
