On Mon, 06 Apr 2020 13:03:25 -0700 Scarlett Moore <[email protected]> wrote: [...] > Hi Thomas, > Can you please instead give maintenance to the entire KDE packaging > team: Maintainer: Debian Qt/KDE Maintainers > <[email protected]>
I'll be *very* happy to hand over packaging to the debian-qt-kde team. Not sure, if there is any specific action required for this on my behalf. In case I need to make a new upload changing maintainership, I've put the sponsor of the last few uploads (Lisandro) in CC (although I see you've already participated in the discussion, so I assume you're subscribed). > Also we need the following answered: > 1) is he using some local repository for packaging? if so, let's > import it > 2) no repository? then we need to agree whether we want a debian-only > repository, or a gbp one; based on that, I can create either, and > push it > > > See thread here: > https://alioth-lists.debian.net/pipermail/pkg-kde-talk/2020-April/003019.html The situation is somewhat messy, indeed, I'm afraid. Up until recently, the packaging was managed inside our upstream repo at https://cgit.kde.org/rkward.git/tree/debian?id=db9a55efb0a8da429b8ff8385d1051aad568dea5 This was then removed (perhaps a bit prematurely) at https://cgit.kde.org/rkward.git/commit/?id=a622376242962cdc8f63898f4df3df90322075bd because that is what Scarlett copied into https://salsa.debian.org/qt-kde-team/extras/rkward as the initial revision. Unfortunately, the story does not end there, because I have prepared (and Lisandro sponsored) one more patch release (https://metadata.ftp-master.debian.org/changelogs//main/r/rkward/rkward_0.7.0b-2_changelog) in order to fix an FTBFS, as I failed to reach Scarlett in a timely manner. This latest release is not reflected in any revision control system, as far as I am aware. DO NOTE that the debian-directory is the current upstream repo is *not* the official debian packaging, and does not share its commit history but rather it is aimed at providing nightly builds at Launchpad PPAs. The path of the official packaging was debian-official. As a further hint, note that several of the current lintian problems. (as well as the 0.7.0b-2 patches) have been addressed in the latest upstream release. So if you are looking into fixing those, consider packaging 0.7.1, instead. I hope this clears up the situation well enough. Please keep me in CC in case of further questions, as I am not subscribed. Regards Thomas > > Thank you! > Scarlett > > -- https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-kde-talk
