* Andreas Henriksson <andr...@fatal.se> [241025 08:56]:
> > I wanted to check if anyone knows any better techniques or mechanisms
> > than trying to remember to run this command manually before working on
> > a package?
> 
> I would very much prefer if it was possible in Debian to not allow
> the archive to get out of sync with packaging git repo (for example
> when it lives under salsa.debian.org/debian which uploaders should have
> access to already).
 
While I understand the sentiment, ...

> That would probably also require some "tag to upload" solution to be
> implemented first I presume.

..., I don't think this would be necessary in the first place, and
also there are a number of practical problems, plus the
policy/mandate problem mentioned by Andrey.

I'm just not seeing the duality of "the archive is the truth"
("preferred form of modication" or whatever people want to call it)
and "git is the truth" can really be made work.

It can work within limited workflows, where maintainers / maintainer
teams agree to mostly follow one or the other, and try to keep the
other side in sync, but it will never be a 100% thing.

If we want the 100% solution, IMO we cannot continue with the
duality. I guess someone who knows more about distributed systems
theory probably could explain on theoretical grounds why it can't
work (or why I'm wrong).

Best,
Chris

Reply via email to