On Wed, Sep 26, 2018 at 02:13:47PM +0200, Sebastien Marie wrote:
> On Tue, Sep 25, 2018 at 04:53:54PM +0100, Stuart Henderson wrote:
> > >
> > > A possible way could be:
> > > - having a sub-package -libstd on lang/rust (which would be empty or
> > > almost)
> > > - add RUN_DEPENDS+=lang/rust,-li
On Tue, Sep 25, 2018 at 04:53:54PM +0100, Stuart Henderson wrote:
> >
> > A possible way could be:
> > - having a sub-package -libstd on lang/rust (which would be empty or almost)
> > - add RUN_DEPENDS+=lang/rust,-libstd to port using rustc
> >
> > when lang/rust is updated, the subpackage rust-l
On 2018/09/25 16:50, Sebastien Marie wrote:
> On Mon, Sep 24, 2018 at 09:20:34PM +0100, Stuart Henderson wrote:
> > On 2018/09/24 09:04, Sebastien Marie wrote:
> > > Hi,
> > >
> > > Here an update for lang/rust 1.29.1.
> > >
> > > It is a security update (only -current is affected).
> >
> > Hi,
On Mon, Sep 24, 2018 at 09:20:34PM +0100, Stuart Henderson wrote:
> On 2018/09/24 09:04, Sebastien Marie wrote:
> > Hi,
> >
> > Here an update for lang/rust 1.29.1.
> >
> > It is a security update (only -current is affected).
>
> Hi, I'm wondering if we need to bump REVISION for ports built with
On 2018/09/24 09:04, Sebastien Marie wrote:
> Hi,
>
> Here an update for lang/rust 1.29.1.
>
> It is a security update (only -current is affected).
Hi, I'm wondering if we need to bump REVISION for ports built with rust
(firefox, librsvg, etc) to ensure that they're updated for people running
pk
Hi,
Here an update for lang/rust 1.29.1.
It is a security update (only -current is affected).
ChangeLog:
https://github.com/rust-lang/rust/blob/stable/RELEASES.md#version-1291-2018-09-25
The standard library's str::repeat function contained an out of
bounds write caused by an i
