On Tue, Feb 09, 2021 at 06:01:15PM +0100, Eberhard Beilharz wrote: > Can someone PLEASE help me getting move this forward? > > I created #980120 where someone suggested: "Have you contacted with > the current maintainer for those packages...? If there's no response, > we may also consider other methods." I did, but there's been no > response, and then there's been no response on that bug either... Ouch, I can see it'd be annoying to hear mostly silence given that you first tried to get in touch no later than November. I'll try to help just because it came across my inbox, though bear in mind I'm not part of the input method team. Firstly though, a bit of expectation management - it is too late for the latest version to be in Debian 11 bullseye I'm afraid. That doesn't mean you can't work on it in the meantime, and bullseye users could still install the latest if you end up getting it uploaded to backports. https://release.debian.org/bullseye/freeze_policy.html > > I'm a member of the Keyman project (https://keyman.com/). We noticed > > that the Debian package repos still contain Keyman 11 whereas the > > current stable version is 13, and version 14 is around the corner. What > > can/need we do to update the packages to a newer version in the Debian > > package repos? Ok, so it appears to be a simple matter of the initial uploader not having time to work on this package since Jan 2019. Strictly speaking, an RFH is reserved for the maintainer to file - for future reference I would have filed an ordinary bug against ibus-keyman with priority "wishlist" to request a new version. It's great that you've managed to find the packaging repo on salsa, but note that maintainers are not required to monitor its Merge Requests. Just skimming debian/control (not a review) I can see you've done your research, so given you seem to be willing to collaborate on the packaging side, I suggest following the salvaging process: https://www.debian.org/doc/manuals/developers-reference/pkgs.en.html#package-salvaging > Open a bug with the severity "important" against the package in > question, expressing the intent to take over maintainership of the > package. For this, the title of the bug should start with ITS: > package-name. You may alternatively offer to only take co-maintenance > of the package. When you file the bug, you must inform all > maintainers, uploaders and if applicable the packaging team explicitly > by adding them to X-Debbugs-CC. I strongly suggest keeping the team maintenance, just adding yourself to Uploaders. You then have to wait 3 weeks, but since byang is aware of the situation, they may choose to give you permission earlier if they wish. The next step, assuming you hear no response (a good outcome) is to build the new version you have made and [Publish] your package to mentors. Then you can probably ask byang to be your [Sponsor] or find another willing volunteer. They will almost certainly ask you to make some minor changes, so just republish and hopefully by then you'll also have full access to the git repo. [Publish]: https://mentors.debian.net/intro-maintainers/ [Sponsor]: https://mentors.debian.net/sponsors/ Good luck, all the best, -- Phil Morrell (emorrp1)
Attachment:
signature.asc
Description: PGP signature