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

Re: Bug#1023083: ITP: libquazip1-qt5 -- Qt/C++ wrapper over minizip - Version 1 (Qt5)



Hello Nilesh,

On 10/29/22 11:39 PM, Nilesh Patra wrote:
> On Sun, Oct 30, 2022 at 03:12:18AM +0000, Ben Westover wrote:
>> On 10/29/22 1:20 PM, Filippo Rusconi wrote:
>>> On Tue, Sep 13, 2022 at 03:40:13PM +0000, Ben Westover wrote:
>>>> On 9/13/22 8:28 AM, Filippo Rusconi wrote:
>>>>>> I'd support any attempt to move the current libquazip[1] away
>>>>>> from Debian Med team where it is just by chance since it was a
>>>>>> dependency of some of our packages.  It does not make any sense to
>>>>>> maintain it inside the Debian Med team and I would love to hand it
>>>>>> over.  All maintainers except me do not respond to pings any more
>>>>>> and thus can be droped from the list of Uploaders.
>>>>>
>>>>> I understand that, let's take it away from Debian Med and put it in Debian at
>>>>> large. Ben, if you would do the update, then I'd go over it and upload it. That
>>>>> would be very good.
>
> If you want to take it out of debian-med team, the right way is to * ask * the
> med-team to transfer it somewhere else. What you are trying to do here is considered
> as a hostile takeover.

You're replying to an old message by Filippo; I'm not *trying* to do
anything. I have already explained to Filippo that this is not the
correct way to do that.

>>>> As stated above, the existing QuaZip *0.9* package (libquazip) and my
>>>> new QuaZip *1.3* package (libquazip1-qt6) are unrelated. While they are
>>>> both QuaZip packages, they are separate since QuaZip 0.x and 1.x are
>>>> supposed to coexist, much like Qt5 and Qt6. The orphaning of libquazip
>>>> is unrelated to my new libquazip1-qt6 being uploaded. My new package is
>>>> outside of any team.
>>>> The correct procedure here is to orphan libquazip, and anyone who is
>>>> interested can adopt it.
>
> Why should the package be orphaned?

The actual maintainers have said that they wish it to be. Read through
the threads [1] and [2] and see the message [3].

>>>> Again, my new package libquazip1-qt6 is not
>>>> related to the existing libquazip package or the Med Team.
>
> There are already some changes committed to git for version 1.1 in the med team
> package. If we happened to miss seeing this ITP, we might have ended up stepping
> on your toes.

Again, the Med Team has asked me to create a new package instead of
attempting to use their WIP 1.1 code. 0.x is supposed to be pacakged
separately from 1.x.

Please read the all messages of the last bug at [3] for full context.
Also FYI, libquazip1-qt6 already exists; we've already gone through that
whole thing. This is just an otherwise identical package for Qt5.

Thanks,
--
Ben Westover

[1]
https://alioth-lists.debian.net/pipermail/debian-med-packaging/2022-August/102963.html
[2]
https://alioth-lists.debian.net/pipermail/debian-med-packaging/2022-September/103264.html
[3] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019507#42
[4] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019507

Attachment: OpenPGP_signature
Description: PGP signature


Reply to: