Hallo Peymaneh,

Peymaneh <peyma...@posteo.net> (2022-12-11):
> I am very sorry about that.
> I uploaded a new revision declaring breaks/replaces relations.

No worries at all!

I was in the middle of dealing with other packages so I didn't patch it
out myself at the time (only filed this bug report), but your fix looks
good to me, thanks.

> masterminds-sprig was on of the first Go libraries I have packaged.
> When I re-read the Go Team conventions[1] over a year later, I had the
> impression the impression that former naming was not correct and that
> I should my beginners mistake, but I might have been overeager 🥴

I can definitely understand the feeling. :) I might be overcautious in
the opposite direction when it comes to changing package names, as that
might mean another trip to NEW, and chasing all packages depending (at
build time and/or at run time) on the old package names, which I suppose
means more work than the status quo (i.e. not renaming).


Tschüss!
-- 
Cyril Brulebois -- Debian Consultant @ DEBAMAX -- https://debamax.com/

Attachment: signature.asc
Description: PGP signature

Reply via email to