Dear Jonathan,
> >Debian's Dictionary is in a weird order; "Thank You" is right next to
> >the definition of "Entitlement"
>
> Sorry this wasn't a helpful message.
(I'm a little behind on this thread alas but I just wanted to thank
you for following up with this retraction.)
Best wishes,
--
Seth Arnold schrieb:
> It doesn't help that the distributions in general want to support Firefox
> on more platforms than the Rust team supports as tier-1 platforms. A
> constant cadence of updates every six weeks is faster than anything else
> excepting the Linux kernel. It's a lot of work.
Why
On Thu, Nov 08, 2018 at 03:12:38PM +0100, Adam Borowski wrote:
On Thu, Nov 08, 2018 at 08:39:30AM -0500, Michael Stone wrote:
On Wed, Nov 07, 2018 at 06:45:14PM -0800, Seth Arnold wrote:
> It doesn't help that the distributions in general want to support Firefox
> on more platforms than the
On Thu, Nov 08, 2018 at 08:39:30AM -0500, Michael Stone wrote:
> On Wed, Nov 07, 2018 at 06:45:14PM -0800, Seth Arnold wrote:
> > It doesn't help that the distributions in general want to support Firefox
> > on more platforms than the Rust team supports as tier-1 platforms. A
> > constant cadence
On Wed, Nov 07, 2018 at 06:45:14PM -0800, Seth Arnold wrote:
It doesn't help that the distributions in general want to support Firefox
on more platforms than the Rust team supports as tier-1 platforms. A
constant cadence of updates every six weeks is faster than anything else
excepting the Linux
On Wed, Nov 07, 2018 at 11:07:09AM -0800, Josh Triplett wrote:
> Rust is stable. Thank you for your contributions helping it work on more
> architectures, but "does not have first-tier support for every
> architecture ever" is not a component of "stabilize".
Hello Josh, I can't speak for anyone
On Thu, Nov 08, 2018 at 06:28:29AM +0900, Mike Hommey wrote:
> On Wed, Nov 07, 2018 at 01:21:44PM -0800, Josh Triplett wrote:
> > > I have worked with the Rust upstream sources
> > > well enough to know these issues. You have a regression in Rust 1.25 and
> > > you will have a very hard time
On Wed, Nov 07, 2018 at 01:21:44PM -0800, Josh Triplett wrote:
> > I have worked with the Rust upstream sources
> > well enough to know these issues. You have a regression in Rust 1.25 and
> > you will have a very hard time trying to bisect the issues simply because
> > you cannot even build 1.25
On Wed, Nov 07, 2018 at 08:47:53PM +0100, John Paul Adrian Glaubitz wrote:
> On 11/7/18 8:07 PM, Josh Triplett wrote:
> >> Well, I wouldn't bet on that. I know that a lot of people have the
> >> feeling that rewriting everything in Rust will solve all problems
> >> in software we have nowadays but
Hello!
On 11/7/18 8:07 PM, Josh Triplett wrote:
>> Well, I wouldn't bet on that. I know that a lot of people have the
>> feeling that rewriting everything in Rust will solve all problems
>> in software we have nowadays but that's not the case. Rewriting large
>> projects is associated with a high
On Wed, Nov 07, 2018 at 11:53:06AM +0100, John Paul Adrian Glaubitz wrote:
> Hello!
>
> > librsvg has rewritten substantial fractions of its code upstream in
> > Rust. It won't be the last such library or package to do so.
>
> Well, I wouldn't bet on that. I know that a lot of people have the
>
Hi Josh,
I agree with most of you message, specially that we cannot keep using
librsvg-in-c forever, but a couple of things:
2018-11-06 06:02 Josh Triplett:
librsvg has rewritten substantial fractions of its code upstream in
Rust. It won't be the last such library or package to do so. librsvg
Hi,
2018-11-06 14:19 Jeremy Bicha:
It looks like we will want to have a librsvg-c source package to build
the older librsvg for architectures that don't support Rust yet.
While the Debian GNOME team could maintain librsvg-c's packaging
alongside librsvg, I'd be happier if someone who cares
Hello!
> librsvg has rewritten substantial fractions of its code upstream in
> Rust. It won't be the last such library or package to do so.
Well, I wouldn't bet on that. I know that a lot of people have the
feeling that rewriting everything in Rust will solve all problems
in software we have
On Sat, Nov 3, 2018 at 5:54 PM John Paul Adrian Glaubitz
wrote:
> I'm really annoyed and disappointed by this move and feel really let down by
> this
> behavior. No heads up, no coordination, no nothing.
There was some coordination but the coordination was for release
architectures. The
On Tue, Nov 06, 2018 at 11:58:57AM +0100, John Paul Adrian Glaubitz wrote:
On 11/6/18 11:51 AM, Holger Levsen wrote:
Also, you wrote a mail to d-d-a that rust is now running on 14 archs, so
I was utterly surprised about your mail a few hours later blaming
someone who uploaded a rust library.
On Tue, Nov 06, 2018 at 12:37:30PM +, Jonathan Dowland wrote:
On Tue, Nov 06, 2018 at 11:58:57AM +0100, John Paul Adrian Glaubitz wrote:
Well, if it wasn't for me, we'd probably be shipping the 2.40-version of
librsrv in Debian Buster and Firefox would be missing on a couple of
release
On Sun, Nov 4, 2018 at 2:30 PM Jeremy Bicha wrote:
> On Sun, Nov 4, 2018 at 11:33 AM Ben Hutchings wrote:
> > I do like the proposal of adding a librsvg-c for just the architectures
> > that don't have Rust (yet).
>
> This sounds reasonable. Thanks Samuel for the suggestion. Any
> volunteers to
Hi,
2018-11-04 17:32 Ben Hutchings:
On Sun, 2018-11-04 at 13:15 +0100, Manuel A. Fernandez Montecelo wrote:
For example RISC-V / riscv64 will probably not have LLVM ready at least
until the LLVM stable released next March.
There are enough languages whose implementation depends on LLVM that
On Tue, Nov 06, 2018 at 11:58:57AM +0100, John Paul Adrian Glaubitz wrote:
Well, if it wasn't for me, we'd probably be shipping the 2.40-version of
librsrv in Debian Buster and Firefox would be missing on a couple of
release architectures.. But I guess the phrase "Thank you" doesn't exist
in
On 2018-11-06 11:08, Holger Levsen wrote:
> > I also bootstrapped the Rust compiler and helped fixing issues on armel,
> > mips, mipsel, mips64el. Those are "strange" ports for you? Ok.
>
> no (except armel..)
I'm running Debian armel on, I don't know, 1000 or 2000 devices.
(Not myself, customers
> There's no point dancing around the person's identity if you're going to
> bring -devel into this. All it does it cost the rest of us a small
> amount of effort to bother looking it up. Instead I think it would be
> both more polite and more effective to name them directly, AND ensure to
> CC
Le mardi 06 novembre 2018 à 11:58:57+0100, John Paul Adrian Glaubitz a écrit :
> On 11/6/18 11:51 AM, Holger Levsen wrote:
> > please get of your high horse.
> >
> > I'm not sure it is said anywhere that one has to care about ports and/or
> > some pet projects.
>
> This isn't about caring about
On Sat, Nov 03, 2018 at 10:53:12PM +0100, John Paul Adrian Glaubitz
wrote:
With this mail, I would like to protest the uncoordinated upload of the
rustified version of libsrvg to unstable. The maintainer of the package
There's no point dancing around the person's identity if you're going to
On Tue, Nov 06, 2018 at 11:58:57AM +0100, John Paul Adrian Glaubitz wrote:
> I also bootstrapped the Rust compiler and helped fixing issues on armel,
> mips, mipsel, mips64el. Those are "strange" ports for you? Ok.
no (except armel..)
but as said, you just wrote a mail to d-d-a that rust has
On 11/6/18 11:51 AM, Holger Levsen wrote:
> please get of your high horse.
>
> I'm not sure it is said anywhere that one has to care about ports and/or
> some pet projects.
This isn't about caring about ports, this is about being respectful to
each other.
> Also, you wrote a mail to d-d-a that
On Tue, Nov 06, 2018 at 02:43:44AM +0100, John Paul Adrian Glaubitz wrote:
> >> Why would I need to communicate that?
> > Because coordination needs involvement from all
> If the maintainer of a package doesn't understand which reverse
> dependencies his package has, he shouldn't be the
John Paul Adrian Glaubitz wrote:
> >> Why would I need to communicate that?
> > Because coordination needs involvement from all
>
> If the maintainer of a package doesn't understand which reverse
> dependencies his package has, he shouldn't be the maintainer of
> his package.
This is not a
>> Why would I need to communicate that?
> Because coordination needs involvement from all
If the maintainer of a package doesn't understand which reverse
dependencies his package has, he shouldn't be the maintainer of
his package.
I don't understand why you are defending his behavior. It's
> Instead of putting all the blame on the GNOME team, maybe you could
> have expressed your concerns during the months that librsvg was still
> in experimental? Or maybe you could have said "Rust is now available
> on all release architectures, but please talk to us before uploading a
> rustified
On Sun, 2018-11-04 at 22:05 +0100, Michael Biebl wrote:
> Am 04.11.18 um 20:30 schrieb Jeremy Bicha:
> > On Sun, Nov 4, 2018 at 11:33 AM Ben Hutchings wrote:
> > > I do like the proposal of adding a librsvg-c for just the architectures
> > > that don't have Rust (yet).
> >
> > This sounds
Am 04.11.18 um 20:30 schrieb Jeremy Bicha:
> On Sun, Nov 4, 2018 at 11:33 AM Ben Hutchings wrote:
>> I do like the proposal of adding a librsvg-c for just the architectures
>> that don't have Rust (yet).
>
> This sounds reasonable. Thanks Samuel for the suggestion. Any
> volunteers to maintain
On Sun, Nov 4, 2018 at 11:33 AM Ben Hutchings wrote:
> I do like the proposal of adding a librsvg-c for just the architectures
> that don't have Rust (yet).
This sounds reasonable. Thanks Samuel for the suggestion. Any
volunteers to maintain this new old package?
Thanks,
Jeremy Bicha
On Sun, 2018-11-04 at 13:15 +0100, Manuel A. Fernandez Montecelo wrote:
> Hi,
>
> 2018-11-04 01:13 Ben Hutchings:
> > On Sat, 2018-11-03 at 23:46 +0100, Adam Borowski wrote:
[...]
> > > A regression of this scale shouldn't be done lightly. So what about
> > > reverting it now so things don't
Hi,
2018-11-04 01:13 Ben Hutchings:
On Sat, 2018-11-03 at 23:46 +0100, Adam Borowski wrote:
> The maintainer of the package knows very well that
> this particular package has a huge number of reverse dependencies and would
cause
> a lot of problems with non-Rust targets now. He also knows
Mattia Rizzolo, le dim. 04 nov. 2018 10:40:01 +0100, a ecrit:
> On Sat, Nov 03, 2018 at 09:04:49PM -0400, Jeremy Bicha wrote:
> > What is the actual consequence of the latest librsvg being unbuildable
> > on those arches? The old binaries won't automatically be removed
> > there, right?
>
> In
On Sat, Nov 03, 2018 at 09:04:49PM -0400, Jeremy Bicha wrote:
> It sounds to me like you're saying that to fix librsvg being out of
> date on 11 arches, we need to make it out of date on every
> architecture.
"out of date" has a specific meaning in the context of buildds: it means
that the latest
Jeremy Bicha, le sam. 03 nov. 2018 21:04:49 -0400, a ecrit:
> On Sat, Nov 3, 2018 at 6:47 PM Adam Borowski wrote:
> > Perhaps we should quickly upload a revert, using the last good version of
> > librsvg, before things degrade? Effectively removing librsvg on 11 archs
> > (not counting
On Sat, Nov 3, 2018 at 6:47 PM Adam Borowski wrote:
> Perhaps we should quickly upload a revert, using the last good version of
> librsvg, before things degrade? Effectively removing librsvg on 11 archs
> (not counting non-official ones) stops any GUI there. Including proverbial
> fvwm.
It
On Sat, 2018-11-03 at 23:46 +0100, Adam Borowski wrote:
> On Sat, Nov 03, 2018 at 10:53:12PM +0100, John Paul Adrian Glaubitz wrote:
> > With this mail, I would like to protest the uncoordinated upload of the
> > rustified
> > version of libsrvg to unstable.
"Uncoordinated upload" is a term
On Sat, Nov 03, 2018 at 10:53:12PM +0100, John Paul Adrian Glaubitz wrote:
> With this mail, I would like to protest the uncoordinated upload of the
> rustified
> version of libsrvg to unstable. The maintainer of the package knows very well
> that
> this particular package has a huge number of
Hello!
With this mail, I would like to protest the uncoordinated upload of the
rustified
version of libsrvg to unstable. The maintainer of the package knows very well
that
this particular package has a huge number of reverse dependencies and would
cause
a lot of problems with non-Rust targets
42 matches
Mail list logo
