AW: Bug#813096: ITP: logdata-anomaly-miner -- lightweight tool for log checking, log analysis

2016-06-09 Thread Fiedler Roman
> Von: Piotr Ożarowski [mailto:pi...@debian.org] > > [Fiedler Roman, 2016-06-09] > > > is AMiner and AMinerRemoteControl symlinked in /usr/bin/? > > > (you can use debian/logdata-anomaly-miner.links to do that) > > > > Currently they are not symlinked. I took the same approach as with > > e.g. /us

Re: Bug#813096: ITP: logdata-anomaly-miner -- lightweight tool for log checking, log analysis

2016-06-09 Thread Piotr Ożarowski
[Fiedler Roman, 2016-06-09] > > is AMiner and AMinerRemoteControl symlinked in /usr/bin/? > > (you can use debian/logdata-anomaly-miner.links to do that) > > Currently they are not symlinked. I took the same approach as with > e.g. /usr/lib/apt/methods/http or /usr/lib/eject/dmcrypt-get-device > w

Re: Bug#813096: ITP: logdata-anomaly-miner -- lightweight tool for log checking, log analysis

2016-06-09 Thread Fiedler Roman
> Von: Piotr Ożarowski [mailto:pi...@debian.org] > > [Fiedler Roman, 2016-06-09] > > > * install into /usr/lib/logdata-anomaly-miner/ and dh_python2 will pick > > > it up without any overrides, additional options, etc. > > > > So I guess, before that (where dh_python2 refused to operate at all),

Re: Bug#813096: ITP: logdata-anomaly-miner -- lightweight tool for log checking, log analysis

2016-06-09 Thread Piotr Ożarowski
[Fiedler Roman, 2016-06-09] > > * install into /usr/lib/logdata-anomaly-miner/ and dh_python2 will pick > > it up without any overrides, additional options, etc. > > So I guess, before that (where dh_python2 refused to operate at all), > using /usr/lib/aminer as a shorthand - as the package name

AW: Bug#813096: ITP: logdata-anomaly-miner -- lightweight tool for log checking, log analysis

2016-06-09 Thread Fiedler Roman
> Von: Piotr Ożarowski [mailto:pi...@debian.org] > > just a quick reply: > > * private dir is the right call, do not install into dist-packages > (only "python-*" binary packages should install there) OK, done. > * install into /usr/lib/logdata-anomaly-miner/ and dh_python2 will pick > it u

Re: Maintenance of pydap

2016-06-09 Thread Sandro Tosi
On Thu, Jun 2, 2016 at 3:49 PM, Ghislain Vaillant wrote: > Hi Sandro, > > I engaged with the pydap community and I can confirm that the project > has moved on from the old 2.x API. Since pydap 3.x is now using a new > namespace (pydap instead of dap), then both package versions should be > co-inst

AW: Bug#813096: ITP: logdata-anomaly-miner -- lightweight tool for log checking, log analysis

2016-06-09 Thread Fiedler Roman
> Von: Gianfranco Costamagna [mailto:locutusofb...@debian.org] > Hi, > > (answering where I can!) >> Moving the code to "/usr/lib/python2.7/dist-packages/aminer" in fact allows >> dh_python2 to extract the version information: >> >> Depends: python:any (<< 2.8), python:any (>= 2.7.5-5~), python-tz

Re: Bug#813096: ITP: logdata-anomaly-miner -- lightweight tool for log checking, log analysis

2016-06-09 Thread Piotr Ożarowski
just a quick reply: * private dir is the right call, do not install into dist-packages (only "python-*" binary packages should install there) * install into /usr/lib/logdata-anomaly-miner/ and dh_python2 will pick it up without any overrides, additional options, etc. * use dh --with python2 or

Re: Bug#813096: ITP: logdata-anomaly-miner -- lightweight tool for log checking, log analysis

2016-06-09 Thread Gianfranco Costamagna
Hi, (answering where I can!) >Moving the code to "/usr/lib/python2.7/dist-packages/aminer" in fact allows >dh_python2 to extract the version information: > >Depends: python:any (<< 2.8), python:any (>= 2.7.5-5~), python-tz, >init-system-helpers (>= 1.18~) > >(Remark: Is there any reason to rest

Re: Bug#813096: ITP: logdata-anomaly-miner -- lightweight tool for log checking, log analysis

2016-06-09 Thread Fiedler Roman
Hi Gianfranco, hello Python devs, Introduction for debian-python members: Gianfranco is giving me great assistance in the mentoring process to get the logdata-anomaly-miner package included to Debian. There were some issues, we are not completely sure, how to sort them out, any help on that wo