> Von: Gianfranco Costamagna [mailto:locutusofb...@debian.org]
> [Snip]
>> Ah, I see. I assumed that the patch editor would cut the lower part in same
>> fashion as git/svn would do. Fixed.
>
> nack
> .
> logdata-anomaly-miner (0.0.2-1) unstable; urgency=low
> .
> * Initial inclusion of logdata-an
> Von: Gianfranco Costamagna [mailto:locutusofb...@debian.org]
>
> Hi,
>
> new issues:
>
> please change python-dev to python-all (you have an arch:all package here)
Changed the Build-Depends, binary depends are now generated by dh_python2.
> patches have useless description, please make a real
Comparing with nginx, I also changed:
$ diff -urN ../logdata-anomaly-miner-0.0.2/debian/postinst debian/postinst
--- ../logdata-anomaly-miner-0.0.2/debian/postinst 2016-06-08
10:23:13.0 +
+++ debian/postinst 2016-06-09 14:24:33.437584218 +
@@ -23,12 +23,15 @@
analysi
> 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
> 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 (whe
> 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
> 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
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
only the debian/ stuff is
stored
Does that make sense?
> apt-get install check-all-the-things -t experimental
>
> $ check-all-the-things
>
> [...Snip]
This is not lost, will respond to it in next iteration (the native/non-native
package decision seems to affect some of those issues
Hello,
After start of packaging and the release of the first 3 versions after port
from java to python, I am still looking for a mentor for package inclusion.
I have written fixes for open points from first review but there are still
some questions open, where I am not sure, how to address them.
Hi,
I tried to address the issues from the first review for V0.0.0 at
http://mentors.debian.net/package/logdata-anomaly-miner, the changes are now
in the V0.0.2~pre0 package uploaded.
But still there are some points not completely clear to me:
Issues from https://www.debian.org/doc/debian-polic
11 matches
Mail list logo
