Re: How to install older python version on Debian

2021-03-26 Thread Geert Stappers
On Fri, Mar 26, 2021 at 09:55:03AM +0800, Robbi Nespu wrote:
> Dear Debian Python,
> 
> I would like to install older python (version 3.6) on my venv environment
> 
> $ inxi -S
> System:
>   Host: debian
> Kernel: 5.10.0-4-amd64 x86_64
>   bits: 64
>Desktop: KDE Plasma 5.20.5
> Distro: Debian GNU/Linux bullseye/sid
> 
> (venv)$ python --version
> Python 3.9.2
> 
> on fedora I can easily do something like this[1], but on debian I wondering
> how I can achieve the same thing, as it look like and I guess older python
> are not available directly on repository
> 
> $ sudo apt-cache pkgnames python3.
> python3.9-venv
> python3.9-examples
> python3.9-full
> python3.9-dbg
> python3.9-dev
> python3.9-doc
> python3.9
> python3.9-minimal
> 
> If my guest are right. Could you suggest me a solution how to have multiple
> python version so I can load inside venv?
> 
> [1] https://robbinespu.gitlab.io/blog/2019/07/23/Python-36-with-VirtualEnv/
> 

As I understand the question is it

} What is the equivalent of
}   sudo dnf install python36
} so that I can do
}   virtualenv --python=/usr/bin/python3.6 foo
}   source foo/bin/activate




Groeten
Geert Stappers
-- 
Silence is hard to parse



Re: Salsa access

2021-03-04 Thread Geert Stappers
On Wed, Mar 03, 2021 at 03:43:47PM -0500, Louis-Philippe Véronneau wrote:
> On 2021-03-03 07 h 44, Stephan Lachnit wrote:
> > Dear team members,
> > 
> > boolean.py is a python package that just landed in Unstable.
> > I would like to transfer the repo from my namespace to the team namespace,
> > since the team is also named as maintainer.
> > 
> > Can someone give me maintainer access so I can move it?
> 
> Hi!
> 
> If you intend to maintain the package in the Team, you need to follow this 
> procedure:
> 
> https://salsa.debian.org/python-team/tools/python-modules/-/blob/master/policy.rst#joining-the-team
> 


And karma bonus points for reporting back.



Re: How to watch pypi.org, example

2020-10-05 Thread Geert Stappers
On Sun, Oct 04, 2020 at 10:53:47PM -0400, Scott Kitterman wrote:
> On Sunday, October 4, 2020 10:24:22 PM EDT Paul Wise wrote:
> > On Sun, Oct 4, 2020 at 3:29 PM Fioddor Superconcentrado wrote:
> > > I've packaged a project provided via https://pipi.org and I wanted to
> > > create a debian/watch file but pipi.org publishes the tarball behind a
> > > strange url like
> > I would suggest using the upstream git repo instead of the PyPi tarballs.
> 
> I think that's a different argument.
> 
> There is a pypi redirector for Debian watch files.  Something like this works 
> (this is from the pyspf package):
> 
> https://pypi.debian.net/pyspf/pyspf-([0-9][0-9t\.\-]*).tar.gz
> 
> This currently works, but no guarantee for how long:
> 
> https://pypi.python.org/packages/source/x/@PACKAGE@/@PACKAGE@@ANY_VERSION@@ARCHIVE_EXT@
 
https://pypi.python.org/packages/source/x/@PACKAGE@/@PACKAGE@-@ANY_VERSION@@ARCHIVE_EXT@



And learning is also learning from examples.



stappers@paddy:~
$ cd packaging_dir/
stappers@paddy:packaging_dir
$ debcheckout pyspf
declared git repository at
https://salsa.debian.org/python-team/modules/pyspf.git
git clone https://salsa.debian.org/python-team/modules/pyspf.git pyspf
...
Cloning into 'pyspf'...
remote: Enumerating objects: 1039, done.
remote: Counting objects: 100% (1039/1039), done.
remote: Compressing objects: 100% (368/368), done.
remote: Total 1039 (delta 612), reused 943 (delta 551), pack-reused 0
Receiving objects: 100% (1039/1039), 237.12 KiB | 415.00 KiB/s, done.
Resolving deltas: 100% (612/612), done.
stappers@paddy:packaging_dir
$ cd pyspf
stappers@paddy:packaging_dir/pyspf
$ cat debian/watch 
version=3
https://pypi.debian.net/pyspf/pyspf-([0-9][0-9t\.\-]*).tar.gz
stappers@paddy:packaging_dir/pyspf
$ 



Regards
Geert Stappers
-- 
Silence is hard to parse



Re: python3- preffix

2020-10-04 Thread Geert Stappers
On Sun, Oct 04, 2020 at 05:39:16PM +0200, Fioddor Superconcentrado wrote:
> Hi again.
> 
> Debian's packaging documentation requires the packages containing python3
> apps to be renamed with a python3 suffix. I do so in debian/control file.
> Now I can put that prefix to the source too or not. If I do so then I get a
> lintian warning source-package-encodes-python-version but if I don't I get
> a conflict warning.
> 
> I've renamed the downloaded tarball with the prefix because the build
> toolchain expected it. But I left the extracted directory's name untouched.
> 
> What's the canonical way?

Same way as we have learnt walking.

 
> Thanks in advanced.

Yes, also beginners can run out of credit.


Regards
Geert Stappers
-- 
Silence is hard to parse



Re: How to watch pypi.org

2020-10-04 Thread Geert Stappers
On Sun, Oct 04, 2020 at 05:28:57PM +0200, Fioddor Superconcentrado wrote:
> I've packaged a project provided via https://pipi.org and I wanted to
> create a debian/watch file but pipi.org publishes the tarball behind a
> strange url like
> 
> https://files.pythonhosted.org/packages/d6/72/9848a2d631dad70d7ea582540f0619e1a7ecf31b3a117de9d9f2b6b28029/django-settings-export-1.2.1.tar.gz
> 
> I guess pypi.org is a common source of python code so perhaps there's
> already a solution for this.

Quoting the manual page of uscan.
(  uscan is the utility reads debian/watch for watching. )


   PyPI
   For PyPI based projects, pypi.debian.net runs a redirector
   which allows a simpler form of URL. The format below will
   automatically be rewritten to use the redirector with the watch
   file:

 version=4
 https://pypi.python.org/packages/source/// \
 -(.+)\.tar\.gz debian uupdate

   For cfn-sphere, set the watch file as:

 version=4
 https://pypi.python.org/packages/source/c/cfn-sphere/ \
 cfn-sphere-([\d\.]+).tar.gz debian uupdate

   Please note, you can still use normal functionalities of uscan
   to set up a watch file for this site without using the
   redirector.

 version=4
 opts="pgpmode=none" \
 https://pypi.python.org/pypi/cfn-sphere/ \
 https://pypi.python.org/packages/.*/.*/.*/\
 cfn-sphere-([\d\.]+).tar.gz#.* debian uupdate


 
> Thanks in advanced.

Looking forward to something like "OK, that works"


Regards
Geert Stappers
-- 
Silence is hard to parse



Re: New here. Hi

2020-10-04 Thread Geert Stappers
On Sun, Oct 04, 2020 at 05:20:30PM +0200, Fioddor Superconcentrado wrote:
> Hi all.
> 
> I'm new to the list and to Debian packaging overall.

Welcome


> I hope my coming questions are not too stupid.
> 
> Read you soon.

 
Regards
Geert Stappers
-- 
Silence is hard to parse



Re: Request to join Python Modules Team

2020-07-15 Thread Geert Stappers
On Wed, Jul 15, 2020 at 05:32:58PM -0300, Emmanuel Arias wrote:
> Geert,
> 
> it's more easy and polite ping to admins and ask for the status of
> the request.
> 
> IMHO it's not so funny to ask "Who is waiting on who?"
> 
> Why do we have to wait 75 hours?

75 =  3 days (of 24 hours) plus 3 hours
But actual a value for getting the discussion started.


Other proposals welcome.




In case
> Why do we have to wait 75 hours?
is
> Why do we have to wait?

One volunteer should not let another volunteer waiting.
One volunteer should allow another volunteer time to respond.


In case
> Why do we have to wait 75 hours?
is
> Do you know that I'm waiting?

Ay, that is indeed what not should happen.
Please retransmit the request.


Groeten
Geert Stappers
-- 
Silence is hard to parse



Re: Request to join Python Modules Team

2020-07-15 Thread Geert Stappers


Hello,


On Wed, Jul 15, 2020 at 12:02:07PM +0200, Ondrej Novy wrote:
> Hi,
> 
> út 14. 7. 2020 v 23:18 odesílatel Geert Stappers 
> napsal:
> 
> > And please enlighten me (and us (through the mailinglist))
> > what is holding back
> >  https://lists.debian.org/debian-python/2020/07/msg00057.html
> 
> 
> huh, this is a bit rude. This is volunteering project and you are trying to
> give me (us) some deadlines or what?

Acknowledge on how my request is recieved.  Rewording in the make.


Yes, this is a volunteering project.   (said the volunteer)

  Imaging you are the person that wants to join this cool project.
  You made some effort to apply for membership and sent in the request.
  Then you wait humblely. Humble as you are, you wait another day.
  On third day you start wondering "Is asking again expressing
  that you care or is it pushing the people you want to join?"


Thing I'm aiming for is a guideline for
when to retransmit a join request.


I admit that I yesterday did misread 
https://lists.debian.org/debian-python/2020/07/maillist.html
that https://lists.debian.org/debian-python/2020/07/msg00057.html
wasn't unanswered for a long time.

As person who wants to help with enabling fellow volunteers,
I would like to know more about the proces of an application
such as https://lists.debian.org/debian-python/2020/07/msg00057.html
(It was not wise from me to use negative words as "holding back")

It is good see that Sudip Mukherjee is now team member.
( https://lists.debian.org/debian-python/2020/07/msg00072.html )



Groeten
Geert Stappers
-- 
Silence is hard to parse



Re: Request to join Python Modules Team

2020-07-14 Thread Geert Stappers
On Wed, Jul 08, 2020 at 12:42:12PM +0200, Ondrej Novy wrote:
> Hi,
> 
> ne 5. 7. 2020 v 18:46 odesílatel  napsal:
> 
> > Whenever things get stalled it is good to ask:
> >
> >Who is waiting on who?
> >
> 
> We have a rule between admins we are processing join request after few days
> to give everyone chance to give their opinions.
> 
> In this particular case it was my fault and overlooked that email.
> 
> > I volunteer to be part of "Some administrator".
> > 
> cool. Current admins needs to agree, so: @piotr, @stefanor, @kitterman,
> @bzed: your opinions please?

For what it is worth: Wiki addition
https://wiki.debian.org/Teams/PythonModulesTeam/HowToJoin?action=diff=23=22
is from me, it says currently:

  Do known that it is okay to ask after 75 hours
  ''Who is waiting on who?''.


> > Debian tradition I will be re-introducing is sending "done messages".
> >
> no need to re-introduce, I'm always sending welcome message :)

I what to help with sending those welcome messages (which implies
accepting the work that comes with it)

And please enlighten me (and us (through the mailinglist))
what is holding back
 https://lists.debian.org/debian-python/2020/07/msg00057.html


Groeten
Geert Stappers
-- 
Silence is hard to parse


signature.asc
Description: PGP signature


[PATCH] Tell source location of policy.

2020-07-05 Thread Geert Stappers
From: Geert Stappers 

---
 debian/python-policy.dbk | 13 +
 1 file changed, 13 insertions(+)

diff --git a/debian/python-policy.dbk b/debian/python-policy.dbk
index 875b281..b62cd03 100644
--- a/debian/python-policy.dbk
+++ b/debian/python-policy.dbk
@@ -1201,6 +1201,19 @@ Build-Depends: python3-all-dev (= 3.2)

   
 
+
+
+  This document
+  
+   Source of this document is
+   debian/python-policy.dbk in git repository
+   https://salsa.debian.org/cpython-team/python3-defaults;
+   >Salsa cpython team  python3 defaults.
+  
+  
+   Discuss with debian-python mailing list your changes.
+  
+
 
 

python-policy source

2020-07-05 Thread Geert Stappers


Hi,

Where to find the source of python-policy?



It it not (yet?) at Salsa


https://salsa.debian.org/search?utf8=%E2%9C%93=false=_ref==python-policy
https://salsa.debian.org/search?utf8=%E2%9C%93=false=_ref==packaging-manuals
> 
> I have reread [3] https://www.debian.org/doc/packaging-manuals/python-policy/
> 

Regards
Geert Stappers
-- 
Silence is hard to parse



Re: Request to join Python Modules Team

2020-07-05 Thread Geert Stappers
On Sat, Jul 04, 2020 at 09:19:56AM -0300, Emmanuel Arias wrote:
> El sáb., 4 de jul. de 2020 a la(s) 04:17, Sao I Kuan escribió:
> > On Fri, Apr 10, 2020 at 6:22 PM Sao I Kuan  wrote:
> > > On Fri, Apr 10, 2020 at 6:16 PM Sao I Kuan  wrote:
> > > >
> > > > Hiya o/,
> > > >
> > > > I would like to join the Python Modules Team.
> > > >
> > > > I'm a newcomer into Debian from this March, and doing the packaging
> > > > which is COVID-19 related, with COVID-19 Biohackathon[0].
> > > >
> > > > [0] https://lists.debian.org/debian-devel-announce/2020/03/msg00010.html
> > > >
> > > > Now I'm trying to packaging the new python application idseq-bench[1]
> > > > (which will be team-maintained inside debian-med), which needs a
> > > > module smart_open[2]. I think [2] could be team maintained inside
> > > > DPMT.
> > > >
> > > > [1] https://github.com/chanzuckerberg/idseq-bench
> > > > [2] https://github.com/RaRe-Technologies/smart_open
> > > >
> > > > I read the Debian Python Policy[3].
> > > >
> > > > [3] https://www.debian.org/doc/packaging-manuals/python-policy/
> > >
> > > I now found and accept the DPMT Policy[4]. My Salsa handle is 
> > > @sikuan-guest.
> > >
> > > [4] 
> > > https://salsa.debian.org/python-team/tools/python-modules/-/blob/master/policy.rst
> >
> > Ping o/ Or am I missing any necessary information?
> >
> > My Salsa handle was changed to @sikuan.
> > Thank you!
> >
> 
> Hi,
> 
> You just need to be patient.

To a certain degree is being patient good.
It is all about working together, reaching a common goal.


Whenever things get stalled it is good to ask:

   Who is waiting on who?


> Some administrator from the team will join you.

I volunteer to be part of "Some administrator".

Please grant me, account "stappers" at  debian.org and at Salsa,
to privilege to allow people the Python teams.

I have reread [3] https://www.debian.org/doc/packaging-manuals/python-policy/



Debian tradition I will be re-introducing is sending "done messages".



Regards
Geert Stappers
-- 
Silence is hard to parse


signature.asc
Description: PGP signature


Re: Offer to help with packaging

2020-07-05 Thread Geert Stappers
Control: retitle -1 ITP: python-language-server -- Python implementation of the 
Language Server Protocol

On Sun, Jul 05, 2020 at 05:55:58PM +0200, Geert Stappers wrote:
> Control: retitle -1 RFP: python-language-server -- Python implementation of 
> the Language Server Protocol

Oops.

Copy and paste error now fixed.



Re: Offer to help with packaging

2020-07-05 Thread Geert Stappers
Control: retitle -1 RFP: python-language-server -- Python implementation of the 
Language Server Protocol
Control: owner -1 Pablo Mestre 
Control: subscribe -1

On Sat, Jul 04, 2020 at 09:29:36AM -0300, Emmanuel Arias wrote:
> Hi,
> 
> 
> On Thu, Jul 2, 2020 at 12:48 AM Pablo Mestre  wrote:
> 
> > Hi
> >
> > El 7/1/20 a las 10:58 PM, Nicholas D Steeves escribió:
> > > Awesome, thank you :-) I expect it will be a popular package too!
> > [.]
> > > If you're committed to packaging python lsp, then set yourself as the
> > > owner of #96360, and retitle it, replacing "RFP" with "ITP".
> > Yes, I committed to packaging
> > > If the absence of a python-jsonrpc-server package is a blocker for
> > > #963605, and you want to work on it, then file an ITP for
> > > python-jsonrpc-server, set yourself as owner, and also set up a blocks
> > > relationship between the two bugs.
> >
> > You mean
> >
> > Control: block 946035 by -1
> > Control: block #[newcode] by -1
> >
> > Something like this?
> >
> 
> yes go ahead.
> 
> I don't see the ITP for python-jsonrpc-server. Do you need some help?
> 

I felt the need to show how to do it.



> > >
> > > Tools for doing this more conveniently are "bts" from devscripts, and
> > > "reportbug" for filing the ITP.  IIRC bts requires an MTA (mail
> > > transport agent) and for this I'd recommend msmtp-mta, because most
> > > people find it easier to configure authentication with it than with
> > > Postfix, Exim, etc.
> > >
> > > If you'd like to do it manually for now, see:
> > >   https://www.debian.org/Bugs/server-control
> >
> > Ok
> >
> > Thanks for all
> >
> > P.
> >

@Pablo 

My intension is to help.
I'm aware you didn't asked for the BTS update I did.

Do know that the Bug Tracking System information on #963605
can be easily updated again.


Regards
Geert Stappers
-- 
Silence is hard to parse



Re: Problem with reprotest-kernel, my build attempt fails

2020-05-18 Thread Geert Stappers
On Sun, May 17, 2020 at 05:22:49PM +0200, Evangelos Ribeiro Tzaras wrote:
> On 5/14/20 9:11 PM, Evangelos Ribeiro Tzaras wrote:
> > On 5/14/20 8:47 PM, Geert Stappers wrote:
> >> On Thu, May 14, 2020 at 07:27:26PM +0200, Evangelos Ribeiro Tzaras wrote:
> >>> Hello,
> >>>
> >>> I have a problem with reprotest on a python package I am building
> >>> and was recently made aware of this mailinglist.
> >>>
> >>> Can anyone tell me what's going on, how I can further debug my issue or
> >>> ideally how I should fix the issue of a failing reprotest-kernel build?
> >>>
> >>> Thanks in advance
> >>>
> >>>
> >>>  Forwarded Message 
> >>> Subject: Problem with reprotest-kernel
> >>> Date: Thu, 14 May 2020 15:44:21 +0200
> >>> From: Evangelos Ribeiro Tzaras 
> >>> To: debian-python@lists.debian.org
> >>>
> >>> Hello,
> >>>
> >>> I need some help with a failing reprotest-kernel (other reprotest works)
> >>> build (both on CI and locally). My package python3-pyzbar provides
> >>> bindings for libzbar0.
> >>> The failure occurs while running the build-time tests for
> >>> build-experiment-1.
> >>>
> >>> Effectively the ImportError is raised here:
> >>> ctypes.util.find_library('zbar') returns None in build-experiment-1
> >>> (testbed still works).
> >>
> >> My first impression would be a missing build dependency.
> >>
> > 
> > Maybe I am missing something obvious, but why would the build (and the
> > failing test) succeed in the testbed if a dependency were missing?
> > 
> 
> After some further investigation, I have figured out a solution.
> Changing the build dependency to the -dev package (from libzbar0 to
> libzbar-dev) has fixed the failing reprotest-kernel job. I tried this
> out after reading that ctypes.util.find_library is usually used to
> lookup build-time dependencies rather than run-time dependencies.
> 
> Local builds and other reprotest variations work fine without the -dev
> package. Can someone share some insight into why reprotest-kernel needs
> the -dev package?
> 
> Thanks in advance
> 

> Can someone share some insight into why reprotest-kernel needs the -dev 
> package?
} Can someone share some insight into why building reprotest-kernel needs the 
-dev package?

 -dev is a naming convention

Those packages contain the development files.  (stuff that the compiler needs)


Regards
Geert Stappers
-- 
Silence is hard to parse



Re: Disparaging people's motivation to contribute to Debian

2020-05-16 Thread Geert Stappers
> as what I originally wanted to say.
> 
> Does it make more sense now?

Yes.  All fine now.   And not fine.  It will never be "all fine"


My point:  Let go, let go



Re: Fwd: Problem with reprotest-kernel

2020-05-14 Thread Geert Stappers
On Thu, May 14, 2020 at 09:11:51PM +0200, Evangelos Ribeiro Tzaras wrote:
> On 5/14/20 8:47 PM, Geert Stappers wrote:
> > On Thu, May 14, 2020 at 07:27:26PM +0200, Evangelos Ribeiro Tzaras wrote:
> >> Hello,
> >>
> >> I have a problem with reprotest on a python package I am building
> >> and was recently made aware of this mailinglist.
> >>
> >> Can anyone tell me what's going on, how I can further debug my issue or
> >> ideally how I should fix the issue of a failing reprotest-kernel build?
> >>
> >> Thanks in advance
> >>
> >>
> >> Subject: Problem with reprotest-kernel
> >> Date: Thu, 14 May 2020 15:44:21 +0200
> >> From: Evangelos Ribeiro Tzaras 
> >> To: debian-python@lists.debian.org
> >>
> >> Hello,
> >>
> >> I need some help with a failing reprotest-kernel (other reprotest works)
> >> build (both on CI and locally). My package python3-pyzbar provides
> >> bindings for libzbar0.
> >> The failure occurs while running the build-time tests for
> >> build-experiment-1 [1].
> >>
> >> Effectively the ImportError is raised here [2]:
> >> ctypes.util.find_library('zbar') returns None in build-experiment-1
> >> (testbed still works).
> > 
> > My first impression would be a missing build dependency.
> >
> 
> Maybe I am missing something obvious, but why would the build (and the
> failing test) succeed in the testbed if a dependency were missing?
 
Good question. Sadly I can't tell what the differences are between
the testbed and the non-testbed. Hopefully is the answer to the
original problem in making the non-testbed more like the testbed.


 
> >> So far I found out that uname -a prints 4.9.0-12-amd64 for testbed and
> >> 2.6.69-12-amd64 for build-experiment-1. On a local build I have seen
> >> some "FATAL: kernel too old" messages[3], but they don't show up in the
> >> logs[4], so I am wondering if it also happens on the CI but also does
> >> not show in the logs.
> >>
> >> A quick ddg search yielded [5] . Can anyone give me any insights?
> >> Because I feel disabling the kernel variation (without fully
> >> understanding the issue) is not the winning move here :)
> >>
> >> Thanks in advance
> >>
> >> [1] https://salsa.debian.org/devrtz/pyzbar/-/jobs/738921#L1116
> >> [2] 
> >> https://salsa.debian.org/devrtz/pyzbar/-/blob/master/pyzbar/zbar_library.py#L63
> >> [3] https://fortysixandtwo.eu/img/reprotest_kernel_too_old.png
> >> [4] https://fortysixandtwo.eu/img/reprotest_too_old_not_in_log.png
> >> [5] 
> >> http://debian.2.n7.nabble.com/Bug-928921-reprotest-kernel-too-old-SIGSEGV-td4512112.html
> >>


Regards
Geert Stappers

P.S.
I'm on both mailinglists, no need to CC me.
-- 
Silence is hard to parse



Re: Fwd: Problem with reprotest-kernel

2020-05-14 Thread Geert Stappers
On Thu, May 14, 2020 at 07:27:26PM +0200, Evangelos Ribeiro Tzaras wrote:
> Hello,
> 
> I have a problem with reprotest on a python package I am building
> and was recently made aware of this mailinglist.
> 
> Can anyone tell me what's going on, how I can further debug my issue or
> ideally how I should fix the issue of a failing reprotest-kernel build?
> 
> Thanks in advance
> 
> 
>  Forwarded Message 
> Subject: Problem with reprotest-kernel
> Date: Thu, 14 May 2020 15:44:21 +0200
> From: Evangelos Ribeiro Tzaras 
> To: debian-python@lists.debian.org
> 
> Hello,
> 
> I need some help with a failing reprotest-kernel (other reprotest works)
> build (both on CI and locally). My package python3-pyzbar provides
> bindings for libzbar0.
> The failure occurs while running the build-time tests for
> build-experiment-1 [1].
> 
> Effectively the ImportError is raised here [2]:
> ctypes.util.find_library('zbar') returns None in build-experiment-1
> (testbed still works).

My first impression would be a missing build dependency.


> So far I found out that uname -a prints 4.9.0-12-amd64 for testbed and
> 2.6.69-12-amd64 for build-experiment-1. On a local build I have seen
> some "FATAL: kernel too old" messages[3], but they don't show up in the
> logs[4], so I am wondering if it also happens on the CI but also does
> not show in the logs.
> 
> A quick ddg search yielded [5] . Can anyone give me any insights?
> Because I feel disabling the kernel variation (without fully
> understanding the issue) is not the winning move here :)
> 
> Thanks in advance
> 
> [1] https://salsa.debian.org/devrtz/pyzbar/-/jobs/738921#L1116
> [2] 
> https://salsa.debian.org/devrtz/pyzbar/-/blob/master/pyzbar/zbar_library.py#L63
> [3] https://fortysixandtwo.eu/img/reprotest_kernel_too_old.png
> [4] https://fortysixandtwo.eu/img/reprotest_too_old_not_in_log.png
> [5] 
> http://debian.2.n7.nabble.com/Bug-928921-reprotest-kernel-too-old-SIGSEGV-td4512112.html
> 


Groeten
Geert Stappers
-- 
Silence is hard to parse



Re: python packaging manual for a beginner

2020-04-07 Thread Geert Stappers


Preamble  'foo' and 'bar' are placeholders.
( https://en.wikipedia.org/wiki/Metasyntactic_variable )

On Tue, Apr 07, 2020 at 08:13:02PM +0200, Alex Mestiashvili wrote:
> Hi Debian Python folks,
> 
> Is there a good entry point for a newbie who wants to package a python
> module? I am looking for a tool similar to dh-make-perl. In the past
> I've been using stdeb as far as I remember, but it is somehow painful
> compared to other dh-make-x helpers.
> A link with step-by-step instructions would be also helpful. Sorry but I
> am unable to find Debian documentation suitable for a newcomer.

I do hope that this message yields posting like

  Take  package  python-foo,  replace the foo stuff with you bar


Regards
Geert Stappers
Added  'python' to the Subject
-- 
Silence is hard to parse



Re: I'll be offline for an indefinite period

2019-09-21 Thread Geert Stappers
On Sat, Sep 21, 2019 at 07:13:32PM +0200,   wrote:
> Hello,
> 
>  Unfortunately, I will be offline for an indefinite period. 

A man got to do what a man got to do.
So face what you have to face.
Thank you for reminding that there is life out side  libre software life.

I looking forward to your return.


> I maintain those packages in python team: wikitrans, pyfribidi, okasha, 
> and python-uinput.
> 
> okasha in git has a fix and needs to be uploaded.



Groeten
Geert Stappers
DD
-- 
Leven en laten leven



Re: Bug#940811: ITP: python-simplenote -- Python3 API wrapper for the Simplenote web service

2019-09-21 Thread Geert Stappers
Control: retitle -1 ITP: python-simplenote -- Python3 API wrapper for the 
Simplenote web service
On Thu, Sep 19, 2019 at 11:09:14PM -0700, Stefan van der Walt wrote:
> On Thu, Sep 19, 2019, at 22:53, Geert Stappers wrote:
> > On Thu, Sep 19, 2019 at 10:43:48PM -0700, Stefan van der Walt wrote:
> > > * Package name: python-simplenote
> > >   Programming Lang: Python
> > >   Description : Python API wrapper for the Simplenote web service
> > 
> > Python or Python3?
> > Please provide clearity.
> 
> I was planning on building only for Python 3 to support nvpy, which also now 
> runs on 3.

Okay.
"3" is now in the description.

I'm not sure if the 3 should/must goto into package name.

Hence the Cc  to the Python mailinglist for asking advice.


Groeten
Geert Stappers
-- 
Leven en laten leven



Re: Python package maintainer request for joining Salsa team

2019-07-17 Thread Geert Stappers
Think "improve bus factor"

On Tue, Jul 16, 2019 at 09:14:44AM -0300, Ondrej Novy wrote:
> út 16. 7. 2019 v 2:44 odesílatel Geert Stappers napsal:
> 
> > While Arthur is given priveleges for writting on  salsa.debian.org
> > could the humble person doing that, become less humble and tell about
> > the process?
> >
> 
> sorry but I don't get it. Arthur asked me in person yesterday how to get
> access to team. I explained it to him, he sent email and I added him to
> team. So what process should we tell him about?

The process that should be told is weather it is OK (or not) that
any DD member is allowed to (or may) add new members to the Salsa team.

Which privileges the new member gets initially.

What checks are needed.

If the salsa  web interface is right tool,
or that script "foo" is the preferred.

Where to communicate that it is (being) processed.


Groeten
Geert Stappers
-- 
Leven en laten leven


signature.asc
Description: PGP signature


Re: Python package maintainer request for joining Salsa team

2019-07-15 Thread Geert Stappers
On Mon, Jul 15, 2019 at 04:34:45PM -0300, Arthur Diniz wrote:
> * Why you want to join the team:
> Maintain a package from a friend  within
> the team and help maintain any orphan packages.
> 
> * Your Salsa login:
> @arthurbdiniz-guest
> 
> * A statement that you have read
> https://salsa.debian.org/python-team/tools/python-modules/blob/master/policy.rst
> and that you accept it.
> 
> I have read all the python-module team participation policies
> and agree with all the guidelines.
> 
> Cheers,
> 
> Arthur Diniz

Arthur Diniz is OK.
See https://lists.debian.org/debian-cloud/2019/05/msg9.html
and the follow-ups.


While Arthur is given priveleges for writting on  salsa.debian.org
could the humble person doing that, become less humble and tell about
the process?

It is for improving the busfactor of the Python team.


Regards
Geert Stappers
DD
-- 
Leven en laten leven



Re: Looking for projects to work on

2019-06-10 Thread Geert Stappers
On Mon, Jun 10, 2019 at 08:39:39PM +0530, Manas Kashyap wrote:
> On Mon, Jun 10, 2019 at 4:43 AM Paul Wise  wrote:
> > On Sun, Jun 9, 2019 at 11:54 PM Manas Kashyap wrote:
> > > I have been looking on any issue or currently in progress project
> > > to work on , with a little mentoring i think i can finish the
> > > project and also help in maintaining it .
> >
> > If you have some experience with Python & Django, there is always work
> > to do on the Debian package tracker. There are bugs and feature
> > requests tagged as suitable for newcomers and most of the features not
> > tagged that way don't need large amounts of code to complete. The
> > contributing documentation is quite comprehensive:
> >
> > https://tracker.debian.org/
> > https://qa.pages.debian.net/distro-tracker/contributing.html
> >
> Thank you so much ,
> But currently, i am looking for some Debian packages where i can contribute
> to clear my python skills .
 

FWIW   "Debian packaging" and  "Python" are two different work areas.


Back to
> > > I have been looking on any issue or currently in progress project
> > > to work on , with a little mentoring i think i can finish the
> > > project and also help in maintaining it .


Find at https://wiki.debian.org/how-can-i-help information
about the how-can-i-help program.


Groeten
Geert Stappers
-- 
Leven en laten leven



Re: Example of packaged Django web application

2019-05-02 Thread Geert Stappers
On Thu, May 02, 2019 at 11:36:56AM +0100, Neil Williams wrote:
> On Thu, 2 May 2019 12:12:47 +0200 Olivier wrote:
> 
> > Hello,
> > 
> > I've read this [1] document but it doesn't include any example yet.
> > 
> > 1. Do you know any Django application that is already packaged for
> > either Stretch or Buster ?
> 
> https://tracker.debian.org/pkg/lava is one.
> 
> The problem is that this is much, much more than a Django application.
> The lava-server package contains & deploys a web UI from a set of
> django apps configured together. Questions about that package are best
> sent upstream: https://git.lavasoftware.org/lava/pkg-lava-debian
> 
> You may get more examples this way:
> $ apt-cache rdepends python3-django|grep -v python3
> Reverse Depends:
>   freedombox
>   lava-server
>   graphite-web
>   dicoweb
>   autoradio
> 
> > 2. How about adding in this Wiki page, a link to this example ?
> 
> For the reasons above, the lava-server package isn't the easiest to
> parse. I'm not aware of a hello-world type django package. The one
> listed on the draft page was subsequently turned into lava-server but
> then has been refactored several times and expanded in multiple
> directions.
>  
> > [1] https://wiki.debian.org/DjangoPackagingDraft
> 
> The page itself is very old - 6 years with the Draft suffix and plenty
> of TODO items. It mentions south migrations which don't happen anymore
> with django from stretch or buster. The whole page is badly out of date.
> 
> I don't know if any of the above packages ever looked at the draft
> during packaging. I know that the lava-server package no longer follows
> that draft in any meaningful manner. The page is still tied in with
> changes to Django from django 1.2 to 1.3. The best thing for this page
> might be that it gets deleted or at least edited to have a warning that
> it is horribly out of date.

Or better: replace the page with what this thread  yeilds


Groeten
Geert Stappers
-- 
Leven en laten leven



Re: cssutils salsa PR review or permission update

2019-01-19 Thread Geert Stappers
On Thu, Jan 17, 2019 at 02:27:35PM +0100, Martin Pitt wrote:
> Hello Pythoneers,
 
Hi All,

Here a freshman to the Python Team.
( freshman as in https://en.wikipedia.org/wiki/Freshman )


> The other day I worked a bit on the cssutils package (I'm a co-maintainer). 
> But
> then I noticed that since the salsa migration I can't commit to the official
> packaging git any more, so I sent a PR instead:
> 
>   
> https://salsa.debian.org/python-team/modules/cssutils/merge_requests/1/commits
> 
> Does the Python modules team receive notifications about these? I don't mind
> much working through PRs, or perhaps it's possible to add me as a committer 
> for
> cssutils on the salsa repo? I just wouldn't like to upload a new version
> and leave the VCS out of date.
> 
> Thanks for any suggestions,
> 

According the Salsa web interface was the merge request granted.

Several other questions from the original poster remain.

* What tell we to new / wannabe  contributors?
  If it is "Send a join request as stated on the wiki", please say so
* Where to notification on the  new merge requests?
* What about commit privileges for a single git repository?


Groeten
Geert Stappers
-- 
Leven en laten leven


signature.asc
Description: PGP signature


Re: Please add 'stappers' to PAPT, 200

2019-01-13 Thread Geert Stappers
On Sun, Jan 13, 2019 at 12:11:56AM +0100, Ond??ej Nový wrote:
> Hi,
> 
> Dmitry Shachnev pí??e v So 12. 01. 2019 v 20:34 +0300:
> > Looks like you were added to DPMT but not PAPT:
> 
> yes, sorry, my mistake. Fixed.
> 

Yes, works.
Thanks


Cheers
Geert Stappers



Re: Please add 'stappers' to PAPT, 403

2019-01-12 Thread Geert Stappers
On Wed, Jan 09, 2019 at 02:13:00PM +0100, Ondrej Novy wrote:
> Hi,
> 
> pá 4. 1. 2019 v 22:16 odesílatel Geert Stappers napsal:
> 
> > Could you please add my account to  PAPT and/or the python-team?
> >
> 
> welcome :)
> 

Thanks

Tried it today:


$ git push --all
Username for 'https://salsa.debian.org': stappers
Password for 'https://stapp...@salsa.debian.org': 
remote: You are not allowed to push code to this project.
fatal: unable to access
'https://salsa.debian.org/python-team/applications/pelican.git/': The
requested URL returned error: 403
$ 



What to do to get beyond that HTTP 403 Forbidden?


I'm also happy with email like

* Works for me
* Works for me, however I do use SSH
* FWIW I do also get that 403


Groeten
Geert Stappers
-- 
Leven en laten leven


signature.asc
Description: PGP signature


About to upload pelican

2019-01-05 Thread Geert Stappers
Control: tag +pending

On Fri, Jan 04, 2019 at 11:50:57PM +0100, Geert Stappers wrote:
> On Sat, Jan 05, 2019 at 12:58:49AM +0300, Dmitry Shachnev wrote:
> > On Fri, Jan 04, 2019 at 10:16:20PM +0100, Geert Stappers wrote:
> > >
> > > I would like to create 
> > > https://salsa.debian.org/python-team/applications/pelican
> > > or would like to have that git repo created and have write privilege to 
> > > it.
> > 
> > FWIW, that repo already exists.
> 
> What a nice surprise
> 

It even has the correct VCS fields.

So the thing to do is uploading.

Because it will enable `debcheckout pelican`  without errors.


Cheers
Geert Stappers



Re: Please add 'stappers' to PAPT

2019-01-04 Thread Geert Stappers
On Sat, Jan 05, 2019 at 12:58:49AM +0300, Dmitry Shachnev wrote:
> Hi Geert!

Hi Dmitry,
Hi Python list,
Hi Bugreport 917468,


> On Fri, Jan 04, 2019 at 10:16:20PM +0100, Geert Stappers wrote:
> > Hello,
> >
> > Here Debian Developer 'stappers'.
> >
> > I'm working on https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917468
> > which is about fixing the VCS field of the Python package 'pelican'
> >
> > I would like to create 
> > https://salsa.debian.org/python-team/applications/pelican
> > or would like to have that git repo created and have write privilege to it.
> 
> FWIW, that repo already exists.

What a nice surprise

 
> And reading bug #917468 log, you were trying to migrate SVN to Git yourself,
> which is not needed since all PAPT repos were migrated automatically.
> 
> (Of course your request to join the team is still valid.)
> 

Yes, I would like to join the team.



Groeten
Geert Stappers
-- 
Leven en laten leven


signature.asc
Description: PGP signature


Please add 'stappers' to PAPT

2019-01-04 Thread Geert Stappers
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256


Hello,

Here Debian Developer 'stappers'.

I'm working on https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917468
which is about fixing the VCS field of the Python package 'pelican'

I would like to create https://salsa.debian.org/python-team/applications/pelican
or would like to have that git repo created and have write privilege to it.

I have read 
https://salsa.debian.org/python-team/tools/python-modules/blob/master/policy.rst
and did read on this mailinglist that it is under update. I do agree with
with the content and intention of it.

I'm fairly new to git-buildpackage.

I subscribed to -python@l.d.o.


Could you please add my account to  PAPT and/or the python-team?


Regards
Geert Stappers
-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJcL80DAAoJECE10SPYwZvsqy4QALDjJMRf+MvE/56dCJPM5EJG
k2F2K6rg6GxALPUwdecC/FaITie2ERn9lInkuHw+6AlINX8KT6KwCGBqT2EZIdsq
bE4pcfwvZclzmnuit4lQixggrRzY+xEFfTROcRToJCL+qmAXQJ/dhk1GoQPDV9O9
/ndRDiy3rV41Js7DgtuRjEmXhobOligzy5Ht0wgXAscGzUz+9AknMgpRRJWIkspl
GIprdhOlATZyCJFV43Weqw6ybKf5bSl4COD3/jIIOWZBdhyfdK+jXVuGxWrI2P88
TYJyMisRJSYNcNDgtbMxtyZr4icgFdJtOkRm+ijfDlzIt57ysOGGxt5/2cb7VQgY
6DU+uBrykb3H4pCRMB5n6zO5HkCmVN2KoeqrsVQy19F4F8x1QHzYTDUdi9IqH/6X
wpV4BKCNAZAC6Bqyknh/1fgqpOcW7fY9Vt3h8/owjWz/5EKDivMbC3iA7OWNuTVp
XIcqvhaayvvX7OW7lKeHg9rVdvgje0YRGBpN6TSUxVnsyw0sOGaNv69oc1/oat2P
IrJ3JURccmEh2CBl1D4fKa35MRqXf6M6hUTC+uHaeUy8+gTcdURb1RP8rRKXa3t5
AIGTKexg5CV6i2pXwrJL2k4iLCCZP4GLxuzrCTgBnRVUaStS+DJ9PHOFEBG0XcGB
cZybTTR96HFviR4L80yB
=/JEx
-END PGP SIGNATURE-



Re: reference package python3 PAPT

2018-12-25 Thread Geert Stappers
On Sun, Dec 23, 2018 at 05:52:22PM -0500, Scott Kitterman wrote:
> On Sunday, December 23, 2018 05:22:07 PM Geert Stappers wrote:
> > Hi,
> > 
> > Which PAPT package is a fairly good shape to be used as reference
> > for bringing another PAPT package in better shape?
> > 
> > 
> > Context:
> > I'm new to PAPT and would like to have some examples packages.
> 
> I think pymilter-milters is in pretty good shape (as of the version I just 
> uploaded), keeping in mind it's still python2 and if your upstream supports 
> it, you should try to go python3.

Thank you,  it got me started.

And I have updated the subject line with the intention
that more possible reference packages are being reported.


Groeten
Geert Stappers
Who cautiously begins to understand that there is nothing really special
about packaging Python applications. But still in doubt.
-- 
Leven en laten leven



reference package

2018-12-23 Thread Geert Stappers


Hi,

Which PAPT package is a fairly good shape to be used as reference
for bringing another PAPT package in better shape?


Context:
I'm new to PAPT and would like to have some examples packages.


Groeten
Geert Stappers
DD
-- 
Leven en laten leven



Re: Adoption for python-gd, looking for sponsors

2004-06-08 Thread Geert Stappers
On Tue, Jun 08, 2004 at 11:13:47AM +0200, Fabio Tranchitella wrote:
 Hi, I'm interested in adoptiong python-gd but I'm not (yet) a DD.
 I'm started my application process few weeks ago and my first official
 package (phpldapadmin) is already in unstable.
 
 I'm looking for someone interested in sponsoring me to adopt python-gd.
 
 I've packaged python-gd adding supports also for older version of Python
 (closing bug #223580) because actually the package supports only
 python2.3. Now it builds three binary packages (python2.1-gd,
 python2.2-gd and python2.3-gd and a dummy package python-gd).
 
 My work is available on http://www.kobold.it/python-gd/
 
 Thanks in advance,

Have you contacted debian-python@lists.debian.org ?
( they are now reading your RFS )

 F.

Cheers
Geert Stappers