Bug#1023083: ITP: libquazip1-qt5 -- Qt/C++ wrapper over minizip - Version 1 (Qt5)
Am Sun, Oct 30, 2022 at 09:09:55AM +0530 schrieb Nilesh Patra: > > >>> 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. Not really since I frequently expressed that I would love to get rid of this package that's way out of our scope. I just was to lazy to orphan it formally. > > >> The correct procedure here is to orphan libquazip, and anyone who is > > >> interested can adopt it. > > Why should the package be orphaned? Since it creates work nobody in our team is volunteering to do. > > >> 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. IMHO the best we could do is revert all those changes which never lead to a buildable package and orphan it in the status its currently in. > If we happened to miss seeing this ITP, we might have ended up stepping > on your toes. I would have warmly welcomed any volunteer who takes this package. ;-P Kind regards Andreas. -- http://fam-tille.de
Bug#1023083: ITP: libquazip1-qt5 -- Qt/C++ wrapper over minizip - Version 1 (Qt5)
On 10/30/22 09:38, Ben Westover wrote: Hello Nilesh, 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. Had you simply linked the bug report/alioth-list mails in your original ITP, it'd have prevented this admittedly un-necessary correspondence. It was not clear at all in the original ITP bug as to what the entire situation is, but I understand now. Thanks for working on it! -- Best, Nilesh
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 +, Ben Westover wrote: >> On 10/29/22 1:20 PM, Filippo Rusconi wrote: >>> On Tue, Sep 13, 2022 at 03:40:13PM +, 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 OpenPGP_signature Description: PGP signature
Bug#1023083: ITP: libquazip1-qt5 -- Qt/C++ wrapper over minizip - Version 1 (Qt5)
On Sun, Oct 30, 2022 at 03:12:18AM +, Ben Westover wrote: > On 10/29/22 1:20 PM, Filippo Rusconi wrote: > > On Tue, Sep 13, 2022 at 03:40:13PM +, 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. > >> 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? > >> 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. -- Best, Nilesh signature.asc Description: PGP signature
Bug#1023083: ITP: libquazip1-qt5 -- Qt/C++ wrapper over minizip - Version 1 (Qt5)
Package: wnpp X-Debbugs-Cc: debian-de...@lists.debian.org Owner: Ben Westover Severity: wishlist * Package name: libquazip1-qt5 Version : 1.3 Upstream Author : Sergey A. Tachenov * URL : https://github.com/stachenov/quazip * License : zlib, LGPL-2.1 with static linking exception Programming Lang: C, C++ Description : Qt/C++ wrapper over minizip - Version 1 (Qt5) QuaZip is the C++ wrapper for Gilles Vollant's ZIP/UNZIP package (AKA Minizip) using Trolltech's Qt library. While quazip is already packaged in Debian, it's version 0.9.1. The author of quazip has stated that versions 1.x are meant to be used alongside 0.x and not as an upgrade/replacement, like how Qt5 is still packaged alongside Qt6. This package is for versions 1.x of quazip built for Qt5. I'm packaging it at the request of Filippo Rusconi (context below). I do not plan to package this inside a team, unless one expresses interest. I will need a sponsor at first as I'm only a DM. Thanks, -- Ben Westover On 10/29/22 1:20 PM, Filippo Rusconi wrote: > Greetings, Ben, > > On Tue, Sep 13, 2022 at 03:40:13PM +, Ben Westover wrote: >> Hello, >> >> 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. >> >> 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. Again, my new package libquazip1-qt6 is not >> related to the existing libquazip package or the Med Team. > > Yes, certainly. However, we have to support libquazip1.3 as a Qt5- and > Qt6-built > library. I would suggest that we make this package (Ben's) or the other > (Debian > med's) support both Qt libraries' versions. > > This would be pretty similar to what I have proposed for QCustomPlot ([0] any > comment about it, not a single comment about my previous emails, by the way). > > Ben, would you do this or would you accept pull requests ? > > Sincerely, > Filippo > > 0. https://salsa.debian.org/science-team/qcustomplot/-/tree/qt5-and-qt6 OpenPGP_signature Description: PGP signature
