Re: Bug#846366: ITP: bcc -- Command line tools for BPF Compiler Collection (BCC)

2016-12-01 Thread Ritesh Raj Sarraf
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On Wed, 2016-11-30 at 22:40 +0100, Christian Seiler wrote: > > many thanks for the explanation, so from a technical point of > > view there is no package naming conflict, although it is somewhat > > counter-intuitive to end up with a source-package "

Re: Bug#846366: ITP: bcc -- Command line tools for BPF Compiler Collection (BCC)

2016-11-30 Thread Ben Hutchings
On Thu, 2016-12-01 at 00:56 +0530, Ritesh Raj Sarraf wrote: > Hello Karsten, > > On Wed, 2016-11-30 at 20:05 +0100, Karsten Merker wrote: > > Hello, > > > > bcc is a package (and executable) name that is already in use for > > another program in Debian. From https://packages.debian.org/sid/bcc: >

Re: Bug#846366: ITP: bcc -- Command line tools for BPF Compiler Collection (BCC)

2016-11-30 Thread Christian Seiler
On 11/30/2016 10:32 PM, Karsten Merker wrote: > On Thu, Dec 01, 2016 at 12:56:14AM +0530, Ritesh Raj Sarraf wrote: >> On Wed, 2016-11-30 at 20:05 +0100, Karsten Merker wrote: >>> bcc is a package (and executable) name that is already in use for >>> another program in Debian. From https://packages.d

Re: Bug#846366: ITP: bcc -- Command line tools for BPF Compiler Collection (BCC)

2016-11-30 Thread Ritesh Raj Sarraf
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hello Karsten, On Wed, 2016-11-30 at 20:05 +0100, Karsten Merker wrote: > Hello, > > bcc is a package (and executable) name that is already in use for > another program in Debian. From https://packages.debian.org/sid/bcc: I'm aware of it. bcc is a

Bug#846366: ITP: bcc -- Command line tools for BPF Compiler Collection (BCC)

2016-11-30 Thread Ritesh Raj Sarraf
Package: wnpp Severity: wishlist Owner: Ritesh Raj Sarraf * Package name: bcc Version : 0.2.0 Upstream Author : IO Visor Project (https://github.com/iovisor) * URL : https://github.com/iovisor/bcc * License : Apache 2.0 Programming Lang: C, Python Descripti