On Fri, Jun 07, 2019 at 09:03:18PM -0700, Russ Allbery wrote:
> This isn't just for us; it's also for the upstreams involved. It can be
> demoralizing and frustrating to be pulled into negative discussions about
> something you care about, and people have limited capacity to react
> gracefully to
Paul Wise writes:
> On Sat, Jun 8, 2019 at 10:09 AM Russ Allbery wrote:
>> Please let us have internal conversations without using them to
>> prematurely pick fights with external maintainers.
> It definitely wasn't my intention to pick a fight.
Yeah, I didn't think that part was intentional si
On Sat, Jun 8, 2019 at 10:09 AM Russ Allbery wrote:
> Please let us have internal conversations without using them to
> prematurely pick fights with external maintainers.
It definitely wasn't my intention to pick a fight.
I strongly disagree with hiding upstream problems from upstream
developers
Paul Wise writes:
> That was me. I apologise for the confusion I generated. I get annoyed at
> people who don't CC the right people when sending mail. In this case I
> probably should have sent you Federico direct mail pointing at the
> archives instead.
This is called snitch-tagging in other fo
On Sat, Jun 8, 2019 at 4:48 AM Julian Andres Klode wrote:
> On Fri, Jun 07, 2019 at 03:36:08PM -0500, Federico Mena Quintero wrote:
> > On Fri, 2019-06-07 at 11:48 +0800, Julian Andres Klode wrote:
> >
> > Why am I getting BCCed on this? Is this low-key unsolicited
> > complaining like in https://
On Fri, 2019-06-07 at 22:48 +0200, Julian Andres Klode wrote:
> I did not BCC you, someone must have bounced it to you. You might
> want to look at your mail headers to see how it got to you. I don't
> even know your email address (well now I do...). I hope whoever did
> it will step forward.
You
On Fri, 2019-06-07 at 11:48 +0800, Julian Andres Klode wrote:
Why am I getting BCCed on this? Is this low-key unsolicited
complaining like in https://mastodon.social/@juliank/102226793499538013
?
> seeing that Federico Mena Quintero has taken over bzip2 development
> and is in the process of po
Hi,
On Fri, Jun 07, 2019 at 09:54:01AM +0200, Xavier wrote:
> Le 07/06/2019 à 09:48, Mo Zhou a écrit :
> > On 2019-06-06 21:44, Boyuan Yang wrote:
> >> I do remember there's still some source packages / binary packages in
> >> Debian
> >> using the bzip2 format. If we are going to do that (which
On Fri, Jun 07, 2019 at 03:36:08PM -0500, Federico Mena Quintero wrote:
> On Fri, 2019-06-07 at 11:48 +0800, Julian Andres Klode wrote:
>
> Why am I getting BCCed on this? Is this low-key unsolicited
> complaining like in https://mastodon.social/@juliank/102226793499538013
I did not BCC you, som
Le 07/06/2019 à 09:48, Mo Zhou a écrit :
> Hi Boyuan,
>
> On 2019-06-06 21:44, Boyuan Yang wrote:
>> I do remember there's still some source packages / binary packages in Debian
>> using the bzip2 format. If we are going to do that (which looks reasonable,
>> BTW), a serious archive-wide scan shou
Hi Boyuan,
On 2019-06-06 21:44, Boyuan Yang wrote:
> I do remember there's still some source packages / binary packages in Debian
> using the bzip2 format. If we are going to do that (which looks reasonable,
> BTW), a serious archive-wide scan should be made in advance to see how great
> the impac
Am 06.06.19 um 23:35 schrieb Julian Andres Klode:
> Hi folks,
>
> seeing that Federico Mena Quintero has taken over bzip2 development
> and is in the process of porting it to Rust[1], we should consider
> removing bzip2 support from apt, dpkg, etc. following the release
> of buster.
Reading https
Hi!
On Thu, 2019-06-06 at 23:35:28 +0200, Julian Andres Klode wrote:
> seeing that Federico Mena Quintero has taken over bzip2 development
> and is in the process of porting it to Rust[1], we should consider
> removing bzip2 support from apt, dpkg, etc. following the release
> of buster.
Argh. :(
On Thu, Jun 06, 2019 at 05:44:27PM -0400, Boyuan Yang wrote:
> 在 2019-06-06四的 23:35 +0200，Julian Andres Klode写道：
> > Hi folks,
> >
> > seeing that Federico Mena Quintero has taken over bzip2 development
> > and is in the process of porting it to Rust[1], we should consider
> > removing bzip2 suppo
On Thu, Jun 06, 2019 at 05:44:27PM -0400, Boyuan Yang wrote:
> 在 2019-06-06四的 23:35 +0200，Julian Andres Klode写道：
> > seeing that Federico Mena Quintero has taken over bzip2 development
> > and is in the process of porting it to Rust[1], we should consider
> > removing bzip2 support from apt, dpkg,
在 2019-06-06四的 23:35 +0200，Julian Andres Klode写道：
> Hi folks,
>
> seeing that Federico Mena Quintero has taken over bzip2 development
> and is in the process of porting it to Rust[1], we should consider
> removing bzip2 support from apt, dpkg, etc. following the release
> of buster.
>
> My unders
Hi folks,
seeing that Federico Mena Quintero has taken over bzip2 development
and is in the process of porting it to Rust[1], we should consider
removing bzip2 support from apt, dpkg, etc. following the release
of buster.
My understanding is that having APT depend on a library written in
Rust sev
17 matches
Mail list logo
