[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1024883: marked as done (Reconsider versioned dependencies of libpinyin-data)



Your message dated Fri, 6 Jan 2023 07:16:34 +0100
with message-id <d79931b9-c061-566f-137b-c020a2e8b636@debian.org>
and subject line Re: Bug#1024883: Reconsider versioned dependencies of libpinyin-data
has caused the Debian Bug report #1024883,
regarding Reconsider versioned dependencies of libpinyin-data
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
1024883: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024883
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: src:libpinyin
Version: 2.7.92-2

Hi all!

Upstream made a SONAME bumb:

https://github.com/libpinyin/libpinyin/commit/2f52299e

While I don't really understand the reason for it, the resulting paperwork in Debian is now done.

At the transition bug we had this conversation:

On 2022-11-26 15:44, Sebastian Ramacher wrote:
On 2022-11-25 14:52:12 +0100, Gunnar Hjalmarsson wrote:
I notice that libpinyin has not yet migrated, even though the 2
days delay is over. Is that because Britney waits for the
dependencies to be migration ready too, or is it because this bug
is not closed yet?

It has not migrated yet because the shared library packages have
strictly versioned dependency on libpinyin-data. Hence, migrating
libpinyin to testing would currently render some packages
uninstallable in testing.

Ideally, this dependency would be relaxed if possible so that this
won't be an issue for the next libpinyin transition. For this one,
all the reverse dependencies and libpinyin need to migrate together.

I take it that Sebastian talks about:

Depends: libpinyin-data (= ${binary:Version})

in libpinyin15 and libzhuyin15.

Question: Would it be an option to change those dependencies to not be versioned in order to make future transitions easier, or are there reasons for keeping it as it is?

--
Cheers,
Gunnar

--- End Message ---
--- Begin Message ---
Closing with "wontfix" as a conclusion of previous discussion.

--
Gunnar

--- End Message ---

Reply to: