Recently libsolv upstream has released 0.7.0 which includes soname bump.
Only incompatible changes are:
Only users in Fedora of libsolv are:
None of them need any changes, just a simple rebuild.
I would like to update libsolv in F28 and F29 to this version. Do you have any objections or concerns about this?
Would there be any reason to believe that Fedora's users might be using libsolv for some purpose we are not aware of?
And if so, can we carry the original libsolv as a compat-libsolv subpackage for the duration of F29's life?
Well, hard to say. There are not many tools exist in the world which use libsolv. Only one comes to my mind -- zypper. However, this libsolv release came out exactly to fulfil its requirements.
I think if people use it, then they are using bindings. And in that case we can't ship compat version of them.
I think we can safely assume that all users of libsolv are are known. (We can ignore users of python bindings). So this should be safe as long as everything is done in one update.
+1
I still don't see any justification for why this needs to be done in a stable release, so consider me -1 on this one.
Due to the non-unanimous vote, I will put this on Monday's agenda.
Metadata Update from @bowlofeggs: - Issue tagged with: meeting
We will discuss this in the FESCo meeting Monday at 15:00UTC in #fedora-meeting-1 on irc.freenode.net.
I think that further discussion is no longer needed because the rebased libsolv got to stable already: libsolv-0.7.1-1.fc28 (Sat Nov 10) libsolv-0.7.1-1.fc29 (Wed Nov 7)
@zbyszek approached to me and asked to put some clarification here why the update got pushed to stable:
There were quite some number of votes (only +1's) within a week. Then there were no -1 votes and I went ahead and pushed update to stable. IIUC FESCo policy correctly if no -1 was given within a week, the ticket is approved.
What is left to discuss? If we want to discuss the wiki documentation of the current process, it should IMHO happen in a separate ticket with a matching title.
I'd just close this as Accepted (+6, 0, -1). (And consider any amendments to the process separately.)
Metadata Update from @bowlofeggs: - Issue close_status updated to: Accepted - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.