mbeh...@debian.org wrote:
>I think we have seen and still see with usrmerge how difficult and cumbersome
>the resolution of an initially as simple presented project turned out. I
>understand the answer of Scott directed in that way, at least this is a
>reservation of mine.
For the record, usrmerge
Hi Ian,
Am 23.06.24 um 20:32 schrieb Ian Jackson:
Micha Lenk writes ("Re: Summary of the current state of the tag2upload
discussion"):
In general our traditional approach of handling source packages is,
we upload upstream's source achive plus our modifications (patches)
and instructions how to
On Sunday, June 23, 2024 1:55:00 PM EDT Russ Allbery wrote:
> Scott Kitterman writes:
> > On Sunday, June 23, 2024 11:43:47 AM EDT Russ Allbery wrote:
> >> You are entitled to believe that my analysis is wrong. You are not
> >> entitled to claim that I didn't do the work that I did, quite publicl
* Russ Allbery: " Re: Summary of the current state of the tag2upload
discussion" (Sun, 23 Jun 2024 10:55:00 -0700):
> So rather than attacking me, you were insinuating attacks on other people.
> I'm not sure that's any better.
Sorry, I am unable to see a personal attack whatsoever when reading
Micha Lenk writes ("Re: Summary of the current state of the tag2upload
discussion"):
> In general our traditional approach of handling source packages is,
> we upload upstream's source achive plus our modifications (patches)
> and instructions how to build it (the packaging). Our tooling
> (basic
Scott Kitterman writes:
> On Sunday, June 23, 2024 11:43:47 AM EDT Russ Allbery wrote:
>> You are entitled to believe that my analysis is wrong. You are not
>> entitled to claim that I didn't do the work that I did, quite publicly
>> and openly, right here on this mailing list for everyone to se
On Sunday, June 23, 2024 1:16:38 PM EDT Russ Allbery wrote:
> Scott Kitterman writes:
> > On Sunday, June 23, 2024 11:48:09 AM EDT Russ Allbery wrote:
> >> As mentioned in the summary, I believe we've found a resolution to this
> >> problem provided that the FTP team is willing to implement the pr
Scott Kitterman writes:
> On Sunday, June 23, 2024 11:48:09 AM EDT Russ Allbery wrote:
>> As mentioned in the summary, I believe we've found a resolution to this
>> problem provided that the FTP team is willing to implement the protocol
>> I described in dak, which Ansgar seemed supportive of. T
On Sunday, June 23, 2024 11:43:47 AM EDT Russ Allbery wrote:
> Scott Kitterman writes:
> > I think that can work both ways. I am old enough to have seen many
> > instances of some new hotness coming along and any objection to it being
> > swept aside because it was clear that the people objecting
On Sunday, June 23, 2024 11:48:09 AM EDT Russ Allbery wrote:
> Scott Kitterman writes:
> > First, as I understand the position of the FTP Masters involved in this
> > discussion (for clarity, I'm a non-delegated member of the FTP Team
> > (i.e. FTP Assistant)), their view is that determining if an
Scott Kitterman writes:
> First, as I understand the position of the FTP Masters involved in this
> discussion (for clarity, I'm a non-delegated member of the FTP Team
> (i.e. FTP Assistant)), their view is that determining if an upload is
> from a person authorized to upload to the Debian archiv
Scott Kitterman writes:
> I think that can work both ways. I am old enough to have seen many
> instances of some new hotness coming along and any objection to it being
> swept aside because it was clear that the people objecting just didn't
> understand why the new hotness was so wonderful and w
On Sunday, June 23, 2024 10:57:26 AM EDT Russ Allbery wrote:
> Simon Richter writes:
> > The difference is the expectation that the delegates will continue to
> > perform this work and therefore need to deal with the long term
> > impact. One-time contributions are welcomed as long as they are a n
On Sunday, June 23, 2024 10:46:33 AM EDT Russ Allbery wrote:
> Matthias Urlichs writes:
> > On 23.06.24 04:45, Russ Allbery wrote:
> >> that just feels wrong to me. Rude. Dismissive. And self-defeating
> >> for Debian as a whole.
> >
> > 100% agree. Though again: that *feels* rude and dismissi
Simon Richter writes:
> The difference is the expectation that the delegates will continue to
> perform this work and therefore need to deal with the long term
> impact. One-time contributions are welcomed as long as they are a net
> positive, but not all of them are, and some take up hundreds of
Matthias Urlichs writes:
> On 23.06.24 04:45, Russ Allbery wrote:
>> that just feels wrong to me. Rude. Dismissive. And self-defeating
>> for Debian as a whole.
> 100% agree. Though again: that *feels* rude and dismissive. I'm *not*
> ascribing *intent* to be rude or dismissive to anybody her
Marco d'Itri writes ("Re: [RFC] General Resolution to deploy tag2upload"):
> 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
On 23.06.24 04:45, Russ Allbery wrote:
Blocking people's work beause it's actively dangerous, sure, sometimes we
have to do that and it sucks but it may make sense. But blocking people's
work because it didn't solve a larger problem than they wanted to solve,
or cared more about backward compati
18 matches
Mail list logo
