Re: Docu: Need help to understand section about package creation

2024-03-20 Thread Andrey Rakhmatullin
On Wed, Mar 20, 2024 at 09:32:34PM +, c.bu...@posteo.jp wrote:
> Hello,
> 
> in order to improve the documentation I need to understand some parts.
> But I am stuck. I don't get it what the authors trying to explain.
> 
> It is about "Creating a new package" section:
> https://wiki.debian.org/Python/GitPackaging#Creating_a_new_package
> 
> The second paragraph points to dsc-file creation described here:
> https://wiki.debian.org/PackagingWithGit/GitDpm/Initialize
As I said before, we no longer use git-dpm and git-dpm-specific
documentation is no longer relevant. One should use git-buildpackage which
is described on https://wiki.debian.org/PackagingWithGit.

> The third paragraph is a list of shell commands that do not work in my
> case. For example "uscan" don't work because it does not know what and
> where to download. Of course I understand that.
Yes, uscan doesn't make sense in that context.

-- 
WBR, wRAR


signature.asc
Description: PGP signature


Re: Docu: Need help to understand section about package creation

2024-03-20 Thread c . buhtz

Thanks for the reply.

Am 20.03.2024 22:43 schrieb Andrey Rakhmatullin:

As I said before, we no longer use git-dpm and git-dpm-specific
documentation is no longer relevant.


OK, then someone should remove it from the DPT packaging wiki page.


One should use git-buildpackage which
is described on https://wiki.debian.org/PackagingWithGit.


What is the difference to https://wiki.debian.org/Python/GitPackaging ?

Am I working on the wrong and out-dated wiki page here?


Yes, uscan doesn't make sense in that context.


I know that. But I don't know how to solve and I don't see in the wiki 
how to solve.




Docu: Need help to understand section about package creation

2024-03-20 Thread c.buhtz
Hello,

in order to improve the documentation I need to understand some parts.
But I am stuck. I don't get it what the authors trying to explain.

It is about "Creating a new package" section:
https://wiki.debian.org/Python/GitPackaging#Creating_a_new_package

The second paragraph points to dsc-file creation described here:
https://wiki.debian.org/PackagingWithGit/GitDpm/Initialize

The third paragraph is a list of shell commands that do not work in my
case. For example "uscan" don't work because it does not know what and
where to download. Of course I understand that.

I assume I need a dsc file?

It seems that my understanding problem is the second paragraph and the
dsc-page it is linking, too.

For example the first paragraph on the page
"/PackagingWithGit/GitDpm/Initialize" is impossible to understand for
newbies. What is it talking about? There is the term "git-dpm" 
pointing to "/PackagingWithGit/GitDpm/" (now after I edit that page
myself). But I am not sure what "git-dpm" is and how much of that big
page I should work on to make that "uscan" command run.

Kind
Christian



Re: Wiki: Setup the environment, e.g. "salsa" script / Request to review modified docs

2024-03-20 Thread Andreas Tille
Hi Brian,

Am Wed, Mar 20, 2024 at 10:59:34AM +1100 schrieb Brian May:
> Andreas Tille  writes:
> 
> > As someone who touched a lot of packages (>2000) I've always used quilt
> > successfully and have seen quilt patches used by the majority of all
> > those packages.  This is not only true for DPT than generally in Debian.
> > Considering quilt as not recommended is definitely not matching the
> > reality and should not be written in Wiki.
> 
> gbp pq is just another way of quilt patches. The debian/patches written
> by gbp pq are compatable with quilt. The patches written to by quilt can
> be read using gbp pq import.
> 
> While gbp pq has a patch queue stored in git, you probably don't want to
> push this to a shared repo.
> 
> But: If you create patches with quilt, and then import and export them
> using gbp pq you might find that gbp pq wants to make minor/trivial
> changes to the unchanged patch files. Which can be irritating when
> making security patches, etc. Maybe this is why the practise is not
> recommended?

Thanks a lot for the explanation.  So the Wiki should be changed in this
direction it should include this explanation.  In any case creating the
impression quilt should not be used does not reflect reality.

Kind regards
   Andreas.

-- 
https://fam-tille.de



Re: Wiki: Setup the environment, e.g. "salsa" script / Request to review modified docs

2024-03-20 Thread c . buhtz
Sorry, guys but I don't understand nearly nothing of what you explain 
here because I don't know the tool chain nor the process. But I hope you 
all do.


I modified the section:
https://wiki.debian.org/Python/GitPackaging#Policies

Feel free to improve my modification.
But please keep the target audience of this wiki page in mind. Keep it 
short and simple. Background infos and reationals should go into another 
document (e.g. a policy or DPT guide).


Kind
Christian Buhtz



Re: matplotlib

2024-03-20 Thread Andrey Rakhmatullin
On Wed, Mar 20, 2024 at 10:32:04AM +0900, ciel wrote:
> Alexandre-san,
> 
> Sorry, it seems like I cannot contribute this because (at least) I'm
> pretty not sure if I can transplant this line properly:
> 
> ```
> ifeq (,$(findstring nocheck,$(DEB_BUILD_OPTIONS)))
> echo "backend  : TkAgg" > matplotlibrc
> ```
This doesn't need to be translated, but can be used as is.

-- 
WBR, wRAR


signature.asc
Description: PGP signature


Bug#1067248: ITP: pytest-jupyter -- Pytest plugins for Jupyter libraries and extensions

2024-03-20 Thread Julian Gilbey
Package: wnpp
Severity: wishlist
Owner: Julian Gilbey 
X-Debbugs-Cc: debian-de...@lists.debian.org, debian-python@lists.debian.org

* Package name: pytest-jupyter
  Version : 0.9.1
* URL : https://github.com/jupyter-server/pytest-jupyter
* License : BSD-3-clause and Expat
  Programming Lang: Python
  Description : Pytest plugins for Jupyter libraries and extensions

  This set of pytest plugins are used for testing Jupyter.
  It includes an echo kernel to speed up testing.  It uses pytest-tornasync
  internally for async test suite running, and may not be compatible with
  pytest-asyncio.

This package is a new requirement for the package tests for
jupyter-client and jupyter-server (newer versions of these packages
that have not yet been packaged).

It will be maintained within the Debian Python Team.