Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.kernel > #59646 > unrolled thread

Iproute2 for Debian testing and backports

Started byStephen Hemminger <stephen@networkplumber.org>
First post2017-12-13 22:30 +0100
Last post2017-12-17 15:00 +0100
Articles 10 — 3 participants

Back to article view | Back to linux.debian.kernel

Contents

  Iproute2 for Debian testing and backports Stephen Hemminger <stephen@networkplumber.org> - 2017-12-13 22:30 +0100
    Re: Iproute2 for Debian testing and backports Alexander Wirt <formorer@formorer.de> - 2017-12-14 08:30 +0100
      Re: Iproute2 for Debian testing and backports Alexander Wirt <formorer@formorer.de> - 2017-12-14 08:50 +0100
      Re: Iproute2 for Debian testing and backports Stephen Hemminger <stephen@networkplumber.org> - 2017-12-14 09:00 +0100
      Re: Re: Iproute2 for Debian testing and backports Luca Boccassi <bluca@debian.org> - 2017-12-16 00:50 +0100
        Re: Iproute2 for Debian testing and backports Alexander Wirt <formorer@formorer.de> - 2017-12-16 09:10 +0100
          Re: Iproute2 for Debian testing and backports Luca Boccassi <bluca@debian.org> - 2017-12-16 16:30 +0100
            Re: Iproute2 for Debian testing and backports Alexander Wirt <formorer@formorer.de> - 2017-12-16 17:20 +0100
              Re: Iproute2 for Debian testing and backports Luca Boccassi <bluca@debian.org> - 2017-12-17 14:50 +0100
                Re: Iproute2 for Debian testing and backports Alexander Wirt <formorer@formorer.de> - 2017-12-17 15:00 +0100

#59646 — Iproute2 for Debian testing and backports

FromStephen Hemminger <stephen@networkplumber.org>
Date2017-12-13 22:30 +0100
SubjectIproute2 for Debian testing and backports
Message-ID<uWmLg-63a-7@gated-at.bofh.it>
Iproute2 gains new features every release to keep up with the upstream kernel.

How do I request that iproute for Debian testing (buster) and backports (stretch-backports)
be kept in sync?  
			kernel		iproute
sid			4.14		4.9
buster			4.13		4.9
stretch-backports	4.13		4.9
stretch			4.9		4.9

Do you need resources to be applied to Debian maintenance for this?

[toc] | [next] | [standalone]

#59649

FromAlexander Wirt <formorer@formorer.de>
Date2017-12-14 08:30 +0100
Message-ID<uWw7T-40l-1@gated-at.bofh.it>
In reply to#59646
On Wed, 13 Dec 2017, Stephen Hemminger wrote:

> Iproute2 gains new features every release to keep up with the upstream kernel.
> 
> How do I request that iproute for Debian testing (buster) and backports (stretch-backports)
> be kept in sync?  
> 			kernel		iproute
> sid			4.14		4.9
> buster			4.13		4.9
> stretch-backports	4.13		4.9
> stretch			4.9		4.9
> 
> Do you need resources to be applied to Debian maintenance for this?
Yes, we need more manpower. 

Alex

[toc] | [prev] | [next] | [standalone]

#59650

FromAlexander Wirt <formorer@formorer.de>
Date2017-12-14 08:50 +0100
Message-ID<uWwrg-497-5@gated-at.bofh.it>
In reply to#59649
On Wed, 13 Dec 2017, Stephen Hemminger wrote:

> On Thu, 14 Dec 2017 08:26:07 +0100
> Alexander Wirt <formorer@formorer.de> wrote:
> 
> > On Wed, 13 Dec 2017, Stephen Hemminger wrote:
> > 
> > > Iproute2 gains new features every release to keep up with the upstream kernel.
> > > 
> > > How do I request that iproute for Debian testing (buster) and backports (stretch-backports)
> > > be kept in sync?  
> > > 			kernel		iproute
> > > sid			4.14		4.9
> > > buster			4.13		4.9
> > > stretch-backports	4.13		4.9
> > > stretch			4.9		4.9
> > > 
> > > Do you need resources to be applied to Debian maintenance for this?  
> > Yes, we need more manpower. 
> > 
> > Alex
> 
> I am not an official Debian maintainer but could make a tree on github that was ready to go.
> David could also feed any Cumulus patches back in.
Thanks, I will try to give the packaging a shot in the weekend. 

Alex

[toc] | [prev] | [next] | [standalone]

#59651

FromStephen Hemminger <stephen@networkplumber.org>
Date2017-12-14 09:00 +0100
Message-ID<uWwrg-497-7@gated-at.bofh.it>
In reply to#59649
On Thu, 14 Dec 2017 08:26:07 +0100
Alexander Wirt <formorer@formorer.de> wrote:

> On Wed, 13 Dec 2017, Stephen Hemminger wrote:
> 
> > Iproute2 gains new features every release to keep up with the upstream kernel.
> > 
> > How do I request that iproute for Debian testing (buster) and backports (stretch-backports)
> > be kept in sync?  
> > 			kernel		iproute
> > sid			4.14		4.9
> > buster			4.13		4.9
> > stretch-backports	4.13		4.9
> > stretch			4.9		4.9
> > 
> > Do you need resources to be applied to Debian maintenance for this?  
> Yes, we need more manpower. 
> 
> Alex

I am not an official Debian maintainer but could make a tree on github that was ready to go.
David could also feed any Cumulus patches back in.

[toc] | [prev] | [next] | [standalone]

#59678

FromLuca Boccassi <bluca@debian.org>
Date2017-12-16 00:50 +0100
Message-ID<uX7TQ-2IG-3@gated-at.bofh.it>
In reply to#59649

[Multipart message — attachments visible in raw view] — view raw

On Thu, 14 Dec 2017, Alexander Wirt wrote:
> On Wed, 13 Dec 2017, Stephen Hemminger wrote:
> 
> > Iproute2 gains new features every release to keep up with the
upstream kernel.
> > 
> > How do I request that iproute for Debian testing (buster) and
backports (stretch-backports)
> > be kept in sync?  
> > 			kernel		iproute
> > sid			4.14		4.9
> > buster			4.13		4.9
> > stretch-backports	4.13		4.9
> > stretch			4.9		4.9
> > 
> > Do you need resources to be applied to Debian maintenance for this?
> Yes, we need more manpower. 
> 
> Alex

Hello Alex,

In case you'd like some help in maintaining iproute2, I'll happily
volunteer. I could give you a hand keeping up with new releases. We
rely heavily on iproute2 at $work so it's a win-win.

And I worked with Stephen in the past, so if he breaks something
upstream I know where to find him :-P

Kind regards,
Luca Boccassi

[toc] | [prev] | [next] | [standalone]

#59681

FromAlexander Wirt <formorer@formorer.de>
Date2017-12-16 09:10 +0100
Message-ID<uXfHI-7SZ-1@gated-at.bofh.it>
In reply to#59678

[Multipart message — attachments visible in raw view] — view raw

On Fri, 15 Dec 2017, Luca Boccassi wrote:

> On Thu, 14 Dec 2017, Alexander Wirt wrote:
> > On Wed, 13 Dec 2017, Stephen Hemminger wrote:
> > 
> > > Iproute2 gains new features every release to keep up with the
> upstream kernel.
> > > 
> > > How do I request that iproute for Debian testing (buster) and
> backports (stretch-backports)
> > > be kept in sync?  
> > > 			kernel		iproute
> > > sid			4.14		4.9
> > > buster			4.13		4.9
> > > stretch-backports	4.13		4.9
> > > stretch			4.9		4.9
> > > 
> > > Do you need resources to be applied to Debian maintenance for this?
> > Yes, we need more manpower. 
> > 
> > Alex
> 
> Hello Alex,
> 
> In case you'd like some help in maintaining iproute2, I'll happily
> volunteer. I could give you a hand keeping up with new releases. We
> rely heavily on iproute2 at $work so it's a win-win.
> 
> And I worked with Stephen in the past, so if he breaks something
> upstream I know where to find him :-P
Your help is really welcome, do you have an alioth account? 

Alex

[toc] | [prev] | [next] | [standalone]

#59684

FromLuca Boccassi <bluca@debian.org>
Date2017-12-16 16:30 +0100
Message-ID<uXmzv-3UH-11@gated-at.bofh.it>
In reply to#59681

[Multipart message — attachments visible in raw view] — view raw

On Sat, 2017-12-16 at 09:01 +0100, Alexander Wirt wrote:
> On Fri, 15 Dec 2017, Luca Boccassi wrote:
> 
> > On Thu, 14 Dec 2017, Alexander Wirt wrote:
> > >  On Wed, 13 Dec 2017, Stephen Hemminger wrote:
> > >  
> > >  > Iproute2 gains new features every release to keep up with the
> > 
> > upstream kernel.
> > >  > 
> > >  > How do I request that iproute for Debian testing (buster) and
> > 
> > backports (stretch-backports)
> > >  > be kept in sync?  
> > >  > 			kernel		iproute
> > >  > sid			4.14		4.9
> > >  > buster			4.13		4.9
> > >  > stretch-backports	4.13		4.9
> > >  > stretch			4.9		4.9
> > >  > 
> > >  > Do you need resources to be applied to Debian maintenance for
> > > this?
> > >  Yes, we need more manpower. 
> > >  
> > >  Alex
> > 
> > Hello Alex,
> > 
> > In case you'd like some help in maintaining iproute2, I'll happily
> > volunteer. I could give you a hand keeping up with new releases. We
> > rely heavily on iproute2 at $work so it's a win-win.
> > 
> > And I worked with Stephen in the past, so if he breaks something
> > upstream I know where to find him :-P
> 
> Your help is really welcome, do you have an alioth account? 
> 
> Alex

Yes I do (DD :-) )

I propose the following:

- upload 4.13 to sid, let it migrate to buster
- upload 4.13 to stretch-backports
- upload 4.14 to sid, and block it on 883558 so that it enters buster
at the same time as the kernel

I could start having a look at 4.13 tomorrow-ish.

How does this plan sound?

Thanks!

Kind regards,
Luca Boccassi

[toc] | [prev] | [next] | [standalone]

#59685

FromAlexander Wirt <formorer@formorer.de>
Date2017-12-16 17:20 +0100
Message-ID<uXnlU-4sY-7@gated-at.bofh.it>
In reply to#59684

[Multipart message — attachments visible in raw view] — view raw

On Sat, 16 Dec 2017, Luca Boccassi wrote:

Hi, 

*snip* 

> > Your help is really welcome, do you have an alioth account? 
> > 
> > Alex
> 
> Yes I do (DD :-) )
argh, my bad. Since pkg-iproute is collab-maint you should already be able to
commit. 
> 
> I propose the following:
> 
> - upload 4.13 to sid, let it migrate to buster
> - upload 4.13 to stretch-backports
> - upload 4.14 to sid, and block it on 883558 so that it enters buster
> at the same time as the kernel
> 
> I could start having a look at 4.13 tomorrow-ish.
> 
> How does this plan sound?
Sounds like a great plan, please go ahead. 

Thanks a lot
Alex

[toc] | [prev] | [next] | [standalone]

#59692

FromLuca Boccassi <bluca@debian.org>
Date2017-12-17 14:50 +0100
Message-ID<uXHui-1g2-7@gated-at.bofh.it>
In reply to#59685

[Multipart message — attachments visible in raw view] — view raw

On Sat, 2017-12-16 at 17:14 +0100, Alexander Wirt wrote:
> On Sat, 16 Dec 2017, Luca Boccassi wrote:
> 
> Hi, 
> 
> *snip* 
> 
> > > Your help is really welcome, do you have an alioth account? 
> > > 
> > > Alex
> > 
> > Yes I do (DD :-) )
> 
> argh, my bad. Since pkg-iproute is collab-maint you should already be
> able to
> commit. 
> > 
> > I propose the following:
> > 
> > - upload 4.13 to sid, let it migrate to buster
> > - upload 4.13 to stretch-backports
> > - upload 4.14 to sid, and block it on 883558 so that it enters
> > buster
> > at the same time as the kernel
> > 
> > I could start having a look at 4.13 tomorrow-ish.
> > 
> > How does this plan sound?
> 
> Sounds like a great plan, please go ahead. 
> 
> Thanks a lot
> Alex

4.13 seems to be working fine on my Stretch laptop, tried a few
route/link/addr/vrf commands.
One patch to drop, one to refresh (fuzz), nothing else to do for now.

Is it OK if I add myself to Uploaders?

If so I'll push the changes to Alioth and then upload 4.13.0-1.

BTW I'm hit by 851291/869191 so I'll avoid committing to pristine-tar
for now, don't want to commit an unreproducible tarball. I'll check
what xz options are being used upstream.

-- 
Kind regards,
Luca Boccassi

[toc] | [prev] | [next] | [standalone]

#59693

FromAlexander Wirt <formorer@formorer.de>
Date2017-12-17 15:00 +0100
Message-ID<uXHDX-1kJ-1@gated-at.bofh.it>
In reply to#59692

[Multipart message — attachments visible in raw view] — view raw

On Sun, 17 Dec 2017, Luca Boccassi wrote:

> On Sat, 2017-12-16 at 17:14 +0100, Alexander Wirt wrote:
> > On Sat, 16 Dec 2017, Luca Boccassi wrote:
> > 
> > Hi, 
> > 
> > *snip* 
> > 
> > > > Your help is really welcome, do you have an alioth account? 
> > > > 
> > > > Alex
> > > 
> > > Yes I do (DD :-) )
> > 
> > argh, my bad. Since pkg-iproute is collab-maint you should already be
> > able to
> > commit. 
> > > 
> > > I propose the following:
> > > 
> > > - upload 4.13 to sid, let it migrate to buster
> > > - upload 4.13 to stretch-backports
> > > - upload 4.14 to sid, and block it on 883558 so that it enters
> > > buster
> > > at the same time as the kernel
> > > 
> > > I could start having a look at 4.13 tomorrow-ish.
> > > 
> > > How does this plan sound?
> > 
> > Sounds like a great plan, please go ahead. 
> > 
> > Thanks a lot
> > Alex
> 
> 4.13 seems to be working fine on my Stretch laptop, tried a few
> route/link/addr/vrf commands.
> One patch to drop, one to refresh (fuzz), nothing else to do for now.
This are great news. 
> 
> Is it OK if I add myself to Uploaders?
yeah of course. 
> 
> If so I'll push the changes to Alioth and then upload 4.13.0-1.
> 
> BTW I'm hit by 851291/869191 so I'll avoid committing to pristine-tar
> for now, don't want to commit an unreproducible tarball. I'll check
> what xz options are being used upstream.
No problem. 

Alex

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.kernel

csiph-web