Hi All,
On Fri, Jan 31, 2020 at 04:28:34PM +, Sudip Mukherjee wrote:
> On Fri, Jan 31, 2020 at 4:11 PM Ben Hutchings wrote:
> >
> > On Wed, 2020-01-15 at 12:50 +, Sudip Mukherjee wrote:
> > > Hi Jonathan,
> > >
>
> >
> > So on balance I support moving libbpf out to a separate source
On Fri, Jan 31, 2020 at 4:11 PM Ben Hutchings wrote:
>
> On Wed, 2020-01-15 at 12:50 +, Sudip Mukherjee wrote:
> > Hi Jonathan,
> >
> > On Wed, Jan 15, 2020 at 06:12:05AM +, Jonathan Nieder wrote:
> > > retitle 948041 libbpf-dev: please build from
> > > https://github.com/libbpf/libbpf
>
On Wed, 2020-01-15 at 12:50 +, Sudip Mukherjee wrote:
> Hi Jonathan,
>
> On Wed, Jan 15, 2020 at 06:12:05AM +, Jonathan Nieder wrote:
> > retitle 948041 libbpf-dev: please build from
> > https://github.com/libbpf/libbpf
> > reassign 948041 libbpf-dev
> > merge 942903 948041
> > quit
> >
On Sun, 19 Jan 2020 22:32:22 -0800 Andrii Nakryiko
wrote:
> Libbpf releases are only loosely synchronized with kernel releases,
> and it's only due to current convention we established within
> community. There is nothing preventing multiple releases of libbpf
> between two releases of kernel. So
On Sat, Jan 18, 2020 at 7:48 AM Bastian Blank wrote:
>
> On Wed, Jan 15, 2020 at 12:50:16PM +, Sudip Mukherjee wrote:
> > On Wed, Jan 15, 2020 at 06:12:05AM +, Jonathan Nieder wrote:
> > > I agree --- if upstream development were happening in
> > > https://github.com/libbpf/libbpf then
On Wed, Jan 15, 2020 at 12:50:16PM +, Sudip Mukherjee wrote:
> On Wed, Jan 15, 2020 at 06:12:05AM +, Jonathan Nieder wrote:
> > I agree --- if upstream development were happening in
> > https://github.com/libbpf/libbpf then this would be a no-brainer. It
> > appears to instead be a mirror
Hi Jonathan,
On Wed, Jan 15, 2020 at 06:12:05AM +, Jonathan Nieder wrote:
> retitle 948041 libbpf-dev: please build from https://github.com/libbpf/libbpf
> reassign 948041 libbpf-dev
> merge 942903 948041
> quit
>
> Hi,
>
> Julia Kartseva wrote:
> > On Sun, 12 Jan 2020 09:51:55 +0100
retitle 948041 libbpf-dev: please build from https://github.com/libbpf/libbpf
reassign 948041 libbpf-dev
merge 942903 948041
quit
Hi,
Julia Kartseva wrote:
> On Sun, 12 Jan 2020 09:51:55 +0100 Bastian Blank wrote:
>> Why should we? If the upstream developers decide to maintain it
>>
On Sun, 12 Jan 2020 09:51:55 +0100 Bastian Blank wrote:
> But updating independently does not provide any benefit. As the kernel
> repo is still upstream, all upstream chnages will flow into the Debian
> archive. An extra package will always lag behind, as changes needs to
> flow from kernel
Hi Sudip
On Sun, Jan 12, 2020 at 12:28:20AM +, Sudip Mukherjee wrote:
> On Fri, Jan 03, 2020 at 08:23:58PM +, Sudip Mukherjee wrote:
> > > What are the benefits of doing so?
> > The only benefit will be that we will be able to update the libraries
> > irrespective of kernel update. libbpf
X-Debbugs-Cc: debian-de...@lists.debian.org
On Fri, Jan 03, 2020 at 08:23:58PM +, Sudip Mukherjee wrote:
> On Fri, Jan 3, 2020 at 7:49 PM Bastian Blank wrote:
> >
> > Hi Marco
> >
> > On Fri, Jan 03, 2020 at 06:59:36PM +0100, Marco d'Itri wrote:
> > > On Jan 03, Sudip Mukherjee wrote:
> > >
On Fri, Jan 3, 2020 at 7:49 PM Bastian Blank wrote:
>
> Hi Marco
>
> On Fri, Jan 03, 2020 at 06:59:36PM +0100, Marco d'Itri wrote:
> > On Jan 03, Sudip Mukherjee wrote:
> > > Do we package libbpf from their github repo independent of the kernel
> > > update? Then we will need to remove the
Hi Marco
On Fri, Jan 03, 2020 at 06:59:36PM +0100, Marco d'Itri wrote:
> On Jan 03, Sudip Mukherjee wrote:
> > Do we package libbpf from their github repo independent of the kernel
> > update? Then we will need to remove the libbpf building bits from the
> > Debian kernel source and create a
On Fri, Jan 3, 2020 at 6:15 PM Marco d'Itri wrote:
>
> On Jan 03, Sudip Mukherjee wrote:
>
> > Do we package libbpf from their github repo independent of the kernel
> > update? Then we will need to remove the libbpf building bits from the
> > Debian kernel source and create a separate package
On Jan 03, Sudip Mukherjee wrote:
> Do we package libbpf from their github repo independent of the kernel
> update? Then we will need to remove the libbpf building bits from the
> Debian kernel source and create a separate package for libbpf.
This is what some of the upstream libbpf developers
Package: src:linux
Severity: wishlist
X-Debbugs-Cc: debian-de...@lists.debian.org, debian-kernel@lists.debian.org
libbpf source has moved to a separate github repo but keeps the kernel
as the true/first source, and updating github repo when release is ready.
In Steve's word the problem they faced
16 matches
Mail list logo
