Re: src:mypy: Split public modules from mypy package

[Andreas Tille]

On Mon, Nov 13, 2017 at 05:06:26PM +, Ghislain Vaillant wrote:
> Could you push this update please?

Done.  Thanks for your work on this

  Andreas.

-- 
http://fam-tille.de

Re: [Outreachy] Hi all!

[Andreas Tille]

On Mon, Nov 13, 2017 at 06:27:12PM +0200, ka lou wrote:
> 
> I did download the source package (and then build the binary packages) , it
> is quite complete except from the /tests directory.

The directory debian/tests is *only* in the source package and it
belongs there.

> Maybe because Linux Mint shares some repos with the Debian distribution ,
> however not the unstable one? That is curious :)

I do not know Linux Mint but I admit I would be astonished if it would
share something that is about internal Debian development.

> I had an extended look to the previous months of discussion in the mailing
> list but i didn't found any mention on the Debian Med policy.
> Thank you it was exactly what i was looking for.

My bad.  I probably point to it so frequently that I simply think I have
done it.

Kind regards

   Andreas.

-- 
http://fam-tille.de

Re: src:mypy: Split public modules from mypy package

[Ghislain Vaillant]

Hi Michel,

Mypy cannot be updated to 0.550 in Debian atm, because our version of 
psutil is too low (bug filed).


Meanwhile, I have pushed an update (0.540-2) implementing the split of 
modules and command-line packages. I have also added a -doc package, 
since a trip to NEW was required anyway.


I have not focused on the tests too much yet. Upstream is using a weird 
format which pytest does not recognize. The runtests.py script they are 
using also yielded some obscure errors.


Could you push this update please?

https://anonscm.debian.org/cgit/debian-med/mypy.git

Thanks,
Ghis


On 30/10/17 16:42, Michael Crusoe wrote:
Perfect. With the faster releases schedule feel free to push a new 
release whenever!


I should add a README.source about wanting to get more of their tests 
under autopkgtest


(You can find a couples issues on their GitHub repository about this. My 
username here is mr-c)


Pe 30 oct. 2017 17:38, "Ghislain Vaillant" > a scris:


No problem. Version 0.550 is just around the corner, so I'll take
the opportunity of a new release to implement the necessary changes.

Ghis


On 30/10/17 16:07, Michael Crusoe wrote:

Hey  Ghislain,

Thank you for bringing this issue to my attention. A great plan,
go for it!

Sorry for the delay, your email just now is the first I've seen
of this proposal.

Pe 30 oct. 2017 17:00, "Ghislain Vaillant"  >> a scris:

     Hi Michael,

     Could you please acknowledge the following bug report I
recently
     raised for src:mypy, and whether you are happy with myself
     implementing the necessary change?

     I am a d-med member myself, but would rather ask first due
to the
     nature of the change. Plus, it will involve a trip to the
NEW queue.
     FYI, I am also implementing the same split for src:yapf,
which the
     Python language server is also depending on.

     Cheers,
     Ghis


     On Fri, 20 Oct 2017 10:59:35 +0100 Ghislain Antony Vaillant
     
>> wrote:

         Package: src:mypy
         Severity: wishlist

         Dear Michael,

         src:mypy currently produces a single binary package
providing
         both the
         main command line interface and the public modules.
However, the
         latter
         is a dependency of integration plugins for flake8
(flake8-mypy)
         and the
         Python language server (pyls-mypy), both of which are
in the
         process of
         being packaged.

         The Debian Python policy stipulates that public modules be
         provided in a
         separate binary package, or install standalone Python
         applications under
         /usr/share/${app} [1].

         Please consider packaging the public modules into a
separate
         python3-mypy binary package and have mypy depend on it.
If you can't
         find the time, I'd be happy to do it as I am also a
member of d-med.

         [1]

https://www.debian.org/doc/packaging-manuals/python-policy/ch-module_packages.html



>

         Cheers,
         Ghis

         -- System Information:
         Debian Release: stretch/sid
            APT prefers artful
            APT policy: (500, 'artful')
         Architecture: amd64 (x86_64)
         Foreign Architectures: i386

         Kernel: Linux 4.13.0-16-generic (SMP w/8 CPU cores)
         Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8
(charmap=UTF-8),
         LANGUAGE=en_GB:en (charmap=UTF-8)
         Shell: /bin/sh linked to /bin/dash
         Init: systemd (via /run/systemd/system)

Re: [Outreachy] Hi all!

[ka lou]

Dear Andreas ,

thank you! I will move forward and implement all your suggestions.

I did download the source package (and then build the binary packages) , it
is quite complete except from the /tests directory.
Maybe because Linux Mint shares some repos with the Debian distribution ,
however not the unstable one? That is curious :)

I had an extended look to the previous months of discussion in the mailing
list but i didn't found any mention on the Debian Med policy.
Thank you it was exactly what i was looking for.

Kind regards,
Kate

On Mon, Nov 13, 2017 at 5:17 PM, Andreas Tille  wrote:

> Dear Kate,
>
> On Mon, Nov 13, 2017 at 04:44:18PM +0200, ka lou wrote:
> > Dear all!
> >
> > Another fast update regarding my latest efforts to start with testing
> > debian packages:)
> >
> > As i mentioned in my last email , i successfully managed to build the
> above
> > mentioned packages from source (i.e tophat, bwa) and produce the desired
> > *.deb file.
> >
> > However , i still fail to have a *\debian\tests directory inside either
> of
> > these packages.
>
> This directory is insite the source package.  It is just inside the
> source you downloaded (if you have no to old version for whatever reason
> - just make sure you download the source package from unstable.  There
> is nothing you need to create - but something that exists and where you
> can learn from.
>
> > After some online research , i believe the problem is the fact that i am
> > running a linux machine and my /etc/apt/sources.list does not have a
> > deb-src repository.
>
> Well, yes, than you can not follow the `apt-get source` advise but you
> can alternatively go to
>
> https://tracker.debian.org
>
> seek for the source package, specifically the *.dsc file, copy the link
> to the *.dsc file and do
>
> dget 
>
> I wonder how you managed to build the binary packages without having
> the source package ...
>
> > I did try to add such a repository , but i had problems with the keys
> > validation.
>
> You should be more verbose what exact problem you have.  Just post the
> line you typed and the result you got here to get better help.
>
> > I will continue my research, however if anyone knows some helpful
> tutorial
> > on how to properly setup a debian repository in LInux mint,
> >  or has any other idea of what the problem might be it will be really
> > helpful!! (Maybe it means that i should run sbuild after all?)
>
> The Debian Med policy which I'm frequently pointing to contains some
> essential readings:
>
>https://debian-med.alioth.debian.org/docs/policy.html#readings
>
> Hope this helps
>
>Andreas.
>
> --
> http://fam-tille.de
>
>

Re: [Outreachy] Hi all!

[Andreas Tille]

Dear Kate,

On Mon, Nov 13, 2017 at 04:44:18PM +0200, ka lou wrote:
> Dear all!
> 
> Another fast update regarding my latest efforts to start with testing
> debian packages:)
> 
> As i mentioned in my last email , i successfully managed to build the above
> mentioned packages from source (i.e tophat, bwa) and produce the desired
> *.deb file.
> 
> However , i still fail to have a *\debian\tests directory inside either of
> these packages.

This directory is insite the source package.  It is just inside the
source you downloaded (if you have no to old version for whatever reason
- just make sure you download the source package from unstable.  There
is nothing you need to create - but something that exists and where you
can learn from.
 
> After some online research , i believe the problem is the fact that i am
> running a linux machine and my /etc/apt/sources.list does not have a
> deb-src repository.

Well, yes, than you can not follow the `apt-get source` advise but you
can alternatively go to

https://tracker.debian.org

seek for the source package, specifically the *.dsc file, copy the link
to the *.dsc file and do

dget 

I wonder how you managed to build the binary packages without having
the source package ...

> I did try to add such a repository , but i had problems with the keys
> validation.

You should be more verbose what exact problem you have.  Just post the
line you typed and the result you got here to get better help.
 
> I will continue my research, however if anyone knows some helpful tutorial
> on how to properly setup a debian repository in LInux mint,
>  or has any other idea of what the problem might be it will be really
> helpful!! (Maybe it means that i should run sbuild after all?)

The Debian Med policy which I'm frequently pointing to contains some
essential readings:

   https://debian-med.alioth.debian.org/docs/policy.html#readings

Hope this helps

   Andreas.

-- 
http://fam-tille.de

Re: [Outreachy] Hi all!

[ka lou]

Dear all!

Another fast update regarding my latest efforts to start with testing
debian packages:)

As i mentioned in my last email , i successfully managed to build the above
mentioned packages from source (i.e tophat, bwa) and produce the desired
*.deb file.

However , i still fail to have a *\debian\tests directory inside either of
these packages.

After some online research , i believe the problem is the fact that i am
running a linux machine and my /etc/apt/sources.list does not have a
deb-src repository.
I did try to add such a repository , but i had problems with the keys
validation.

I will continue my research, however if anyone knows some helpful tutorial
on how to properly setup a debian repository in LInux mint,
 or has any other idea of what the problem might be it will be really
helpful!! (Maybe it means that i should run sbuild after all?)

Thank you all again
Kate

Re: EDFbrowser 1.61 (new version available)

[Teunis van Beelen]

Hi Andreas,

Unfortunately I don't have any automated tests for EDFbrowser.
The reason is, is that all code is tightly integrated with the gui, so no
scripting is possible.
(Yes, with the knowledge and experience I have now, I should have done it
different...)
Also, setting up all those tests requires time as well.
Extracting parts of the code to create those tests is going to require
considerable time, time which I don't have.
The only good solution would be to refactor EDFbrowser which takes even
more time.

Kind Regards,

Teunis



On Mon, Nov 13, 2017 at 1:07 PM, Andreas Tille  wrote:

> Hi Teunis,
>
> On Wed, Nov 01, 2017 at 04:11:24PM +0100, Teunis van Beelen wrote:
> > EDFbrowser 1.61 is available at:
> >
> > https://www.teuniz.net/edfbrowser/
>
> Thanks for the hint.  I updated the packaging in Git.  However, I
> hesitated with the upload since I wonder whether you might like to
> provide a test we could use to verify the functionality.  We are trying
> to equip every package which an autopkgtest and since you are upstream
> you have probably some kind of test you could provide.
>
> Kind regards
>
>   Andreas.
>
> --
> http://fam-tille.de
>



-- 
"C'è qualcosa nella nebbia! Qualcosa nella nebbia ha preso John Lee!"

Re: EDFbrowser 1.61 (new version available)

[Andreas Tille]

Hi Teunis,

On Wed, Nov 01, 2017 at 04:11:24PM +0100, Teunis van Beelen wrote:
> EDFbrowser 1.61 is available at:
> 
> https://www.teuniz.net/edfbrowser/

Thanks for the hint.  I updated the packaging in Git.  However, I
hesitated with the upload since I wonder whether you might like to
provide a test we could use to verify the functionality.  We are trying
to equip every package which an autopkgtest and since you are upstream
you have probably some kind of test you could provide.

Kind regards

  Andreas.

-- 
http://fam-tille.de