On Sun, Jan 20, 2019 at 07:36:57PM +0100, Felix Salfelder wrote:
> On Sun, Jan 20, 2019 at 07:33:44PM +0100, Mattia Rizzolo wrote:
> > Then if you don't mind I'd still keep my NMU as it is and let it enter
> > unstable. The only thing is that you'd find yourself to integrate it
> > into your own t
On Sun, Jan 20, 2019 at 05:03:27PM +0100, Felix Salfelder wrote:
> On Sun, Jan 20, 2019 at 04:34:28PM +0100, Mattia Rizzolo wrote:
> > If it's only about sponsoring I'm happy to help, but I don't really want
> > to play with symbols at this time…
>
> my preferred solution will be to accept the dpk
On Sun, Jan 20, 2019 at 04:34:28PM +0100, Mattia Rizzolo wrote:
> If it's only about sponsoring I'm happy to help, but I don't really want
> to play with symbols at this time…
my preferred solution will be to accept the dpkg-shlibdeps warnings, as
described in the manual. it will be more tricky to
Hi,
On Sun, Jan 20, 2019 at 03:44:55PM +0100, Felix Salfelder wrote:
> thanks for your commitment. I have prepared 0.0.2-2 in the
> pkg-electronics team repo, looking for a sponsor. we are now discussing
> issues with toolchains [2], ETA unknown.
I see that the discussion there has moved on to so
On Sun, Jan 20, 2019 at 01:55:18PM +0100, Mattia Rizzolo wrote:
> I've prepared an NMU for gnucap-python (versioned as 0.0.2-1.1) and
> uploaded it to DELAYED/2. Please feel free to tell me if I
> should delay it longer.
Dear Mattia.
thanks for your commitment. I have prepared 0.0.2-2 in the
pkg-
5 matches
Mail list logo
