On Tue, Jan 4, 2022 at 2:44 AM Ian McInerney via devel
<devel@lists.fedoraproject.org> wrote:
>>
>> Did you run the build for lxqt-wallet? I see that there is a commit in 
>> distgit that bumps the version to 1.0.0, but I can't find an associated 
>> build in Koji for that version. I actually think that commit to lxqt-wallet 
>> needs to be reverted though, and instead just a rebuild for lxqt-wallet is 
>> needed. The upstream release still has version 3.2.2 as its most recent 
>> version (which is the current version we package), and does not appear to 
>> follow the standard lxqt release schedule/versioning system.
>>
>
> I have reverted this commit in rawhide now, so lxqt-wallet is back to version 
> 3.2.2.
>

Thanks for catching this. That might because of my bulk updating
script did not exclude it when pushing. I'll be more careful on this.

> I suggest that you modify every lxqt spec file to not glob the soname version 
> for their exported libraries in the files section and instead have the 
> version defined in the spec file as a global. That would fail then build when 
> an soname bump occurs and the packager isn't aware of it, preventing these 
> types of unannounced bump problems in the future when updating a lot of 
> packages at once.

Sure, I will take a look at all those spec files in my earliest convenience.

Thanks again for looking into these!


-- 
Ziqian SUN (Zamir)
z...@fedoraproject.org
GPG : 1D86 6D4A 49CE 4BBD 72CF FCF5 D856 6E11 F2A0 525E
Want to know more about Fedora?
Visit https://fedoraproject.org/wiki/
_______________________________________________
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Reply via email to