Hi Ian,
Am Sun, Dec 15, 2024 at 11:56:36AM +0000 schrieb Ian Jackson:
> I wasn't clear, evidently. Let me restate:
>
> I'm strongly of the opinion that the package should *not* be removed.
> My concern is that some people may disapprove of this package.
> You'll surely be aware that other packages that make the system behave
> in a more "traditional" way have been the subject of unwarranted
> removals, and other kinds of intensely unpleasant political difficulty.
>
> In this case I'm not aware of any actual opposition, so my
> apprehension is merely precautionary.
I would assume than nobody will mind inside the Fonts team but since my
gut feeling might be wrong I will perfectly respect your doubt about
this.
> > I initially followed my `gbp import-dsc` habit (and should have known
> > its not the best choice in this case :-() and thus recreated the history
> > from dgit. The repository in Salsa now contains the complete dgit
> > history.
>
> Thanks.
You are welcome.
> > 1. You subscribe the package directly in tracker
> > 2. I can move the package to the debian/ team and set you as
> > Maintainer
>
> I think given what I said above about some people possibly disagreeing
> with the package's existence, 2 is probably best.
I've just removed the repository and called
dgit --gbp push-source
... and as I realised later I did so inside the repository which had the
old fonts team mentioned ... aaaargh! I will do some subsequent upload
to fix this. I simply had to recreate the repository since I have no
permissions to remove from font-team and went to the wrong local clone
when uploading. My `dcut rm` was to late to cancel the upload.
> > Thanks again for your quick response (which is unfortunately a very
> > rare exception for ITS bugs)
>
> I have quite a few packages which have been around for a very long
> time, and which generally require changes very rarely. Sometimes
> those changes are done by NMUs; personally, if I find myself
> interacting with a package rarely, I don't prioritise improving the
> development workflow.
That's understandable.
> So, your contributions to improving the workflow, git setup, etc., are
> very much appreciated.
Thanks a lot for your support. I remember a few (vocal) people had
problems when I suggested to move all packages to Salsa. Now I want to
know how many packages are really affected by resistance of the
maintainer.
> (FTR, if you do the upload with dgit, you're welcome to do it as a
> "team upload" rather than an NMU.)
Thank you and sorry for the broken upload in the first place.
> > I'm fine to learn more so I will do so once we clarified the best
> > option in what team the package should be maintained.
>
> Of course. I'm happy to advise if you get into any difficulties.
> (I'm also often around on irc, where I'm Diziet.)
Unfortunately IRC is not my prefered medium - but it should work
via IRC-Matrix bridge.
I'll let you know when I've fixed the team issue
Andreas.
--
https://fam-tille.de
