#155 qbittorrent update
Opened a month ago by lkocman. Modified a week ago

cousin_luigi would like tou update qbittorrent however the update requires newer boost1.76.

This can be parallely offered just like we do for boost1.75 and other boost versions.


Metadata Update from @lkocman:
- Custom field SUSE Jira - SUSE Linux Enterprise adjusted to https://jira.suse.com/browse/PED-8134

a month ago

Please reference jsc#PED-8134 in the submission to SUSE:SLE-15-SP6G:GA.

Well unless you find a way to work with boost.175 which is be available as a standalone package.

@lkocman well, it seems to build only with 1.76.

Problem is, it's still in beta. Unsure if it will be released in time for incusion. Should I wait to send boost 1.76 to backports until it's actually necessary? Or should future security updates also be taken into consideration?

@alois I did agree with PM that we'd add boost1.76 to openSUSE:Backports:SLE-15-SP6 so feel free to submit it there together with updates to the torrent client. add it, we can always release maintenance update for it later.

Hello Alois,

we plan to have RC code-submission deadline on this Wednesday
https://en.opensuse.org/openSUSE:Roadmap#Schedule_for_openSUSE_Leap_15.6

I'd prefer not to add any new packages past this deadline. So please hurry up in case that you want 1.76 paralelly avialable in Leap 15.6.

Thank you very much for your understanding.

Lubos

@lkocman You're right, but it's not tardiness, just cold feet.

Boost 1.76 is ancient, released 3 years ago: who's going to take care of security problems that might arise?
Also a couple of weeks ago Adam Majer said he was going to look into the possibility of backporting the required methods to 1.75, but I haven't heard anything from him.

What do you recommend?

SEems like we have all done against boost175! thank you for all the work! https://build.opensuse.org/project/show/home:alois:leap156boost175

Maybe just one concern regarding licensing. Our legaldb currently expect that main package has all licenses combined ... I've waived it as okay, but please be aware.

Screenshot_from_2024-04-19_15-11-41.png

Hehe I see that Adam Mayer was bit impatient when he asked me about including it :)

@lkocman Yes, I'm sorry I didn't explain things to him more clearly.
I worried that in case of a security hole I could not backport the fix from 5.x nor upgrade the package.
Now I will simply send a MR when the time comes.

Thanks again

I'm not sure what to do about libtorrent-rasterbar: would it be better to switch everything (meaning stable qbittorrent 4.x and btfs) to boost 1.75 now or in a future MR?

Login to comment on this ticket.

Metadata
Attachments 1