Hi,
On 6/22/24 04:40, Russ Allbery wrote:
I am frequently told that Debian is a do-ocracy: the people who are
willing to do the work have wide latitude over how that work is done. One
of the implications of that is that delegates don't get to force other
people to do their work in arbitrarily
Micha Lenk writes:
> thank you, Russ, for summarizing the discussion so far. As far as it
> represents the tag2upload proponents point of view, I think it is a fair
> summary of what was said so far. A few aspects seem to be missing from
> my point of view, so I'd like to share my own opinion (
Hi all,
thank you, Russ, for summarizing the discussion so far. As far as it
represents the tag2upload proponents point of view, I think it is a fair
summary of what was said so far. A few aspects seem to be missing from my
point of view, so I'd like to share my own opinion (I don't know whether
ijack...@chiark.greenend.org.uk wrote:
> In this message I discuss in some detail five packaging workflows.
I am more familiar with the gbp patches-unapplied workflow: can you
point us to some educationlly relevant example repositories using the
git-debrebase workflows?
(Maybe without dgit, to mak
On 19.06.24 23:49, Salvo Tomaselli wrote:
But if by mistake one upstream adds a proprietary file in git and then removes
it… we can't distribute the whole .git directory as is.
True – but what we *can* do is to add a "debian/source/strip-blobs"
file, then run "git filter-repo --strip-blobs-wit
Ian Jackson writes:
> Russ Allbery writes ("Re: [RFC] General Resolution to deploy tag2upload"):
>> So yes, you're right, the git-debrebase example is not nearly as
>> interesting as I had thought because the tooling works differently than
>> I had realized.
> As ever, it's all more complicated
Matthias Urlichs writes ("Re: Summary of the current state of the tag2upload
discussion"):
> On 22.06.24 07:36, Soren Stoutner wrote:
> > 1. Maintain a complete history of the source of Debian packages in Git,
> > including their Git history.
> > 2. Create the source packages in a controlled, ce
Russ Allbery writes ("Summary of the current state of the tag2upload
discussion"):
> Again, this summary is only my opinion. I am not a tag2upload maintainer,
> nor is the draft GR my GR. I cannot speak for any of the parties involved
> here, only for myself.
As one of the tag2upload developers
Russ Allbery writes ("Re: [RFC] General Resolution to deploy tag2upload"):
> So yes, you're right, the git-debrebase example is not nearly as
> interesting as I had thought because the tooling works differently than I
> had realized.
As ever, it's all more complicated than you thought (and than yo
On 22.06.24 07:36, Soren Stoutner wrote:
1. Maintain a complete history of the source of Debian packages in Git,
including their Git history.
2. Create the source packages in a controlled, centralized environment.
3. Eliminate the need for a fat client or any special Debian tooling on the
DD’s
10 matches
Mail list logo
