Re: "debian/main" support or ticket open?

[Agathe Porte]

Hi,

2024-03-15 10:16 CET, Simon McVittie:
> On Fri, 15 Mar 2024 at 08:10:55 +, c.bu...@posteo.jp wrote:
> > To my knowledge in context of DPT and Salsa the branch name "debian/master"
> > is used. When creating a new package are there any technical reasons not
> > renaming that to "debian/main"?
>
> […]
>
> If there is going to be any change to this branch
> name, then I think it should be to debian/latest as per
>  (which is the name used
> in various other teams like GNOME), not debian/main.

I am guilty of having used `debian/latest` in multiple of my packages
inside the DPT by following DEP-14, because I prefered it to the DPT
branch name and I use DEP-14 in all my other packages.

> When the GNOME team switched from debian/master to debian/latest, it
> was a coordinated change applied to every package maintained by the team.

Do we know if this was automated by a tool/script, or if this was a
manual effort by multiple people? I would be happy to help update our
current DPT policy to use DEP-14 and perform the migration.

Best regards,

Agathe.

Re: Suggesting change in DPT policy

[Agathe Porte]

Hi,

2024-02-27 09:06 CET, Andreas Tille:
> I probably should have reviewed the DPT policy on Maintainership[3] more
> carefully. In other teams, it's common for the Maintainer to be set to
> the team, so I assumed it was just an oversight when I made this
> change[4] when touching the package to fix RC bug #1058177.  However, I
> I was pointed immediately about the fact that I was mistaken according
> to the current DPT policy.

I also have been bitten by this recently. I assumed that the package was
DPT maintained because it was in the DPT namespace on Salsa.
But it was not. And I got a message after my upload.

If the package was outside of DPT, I would have created a bug instead
for the maintainer to handle. I do not understand the point of
Uploader: DPT compared to individually maintained packages.

So, +1 for this.

Re: Bug#1042439: ITP: ppft -- Distributed and parallel Python

[Agathe Porte]

Hi Julian,

2023-07-28 10:57 CEST, Julian Gilbey:
> Package: wnpp
> Severity: wishlist
> Owner: Julian Gilbey 
> X-Debbugs-Cc: debian-de...@lists.debian.org, Debian Python Team 
> 
>
> * Package name: ppft
>   Version : 1.7.6.7+dfsg
>   Upstream Contact: Mike McKerns 
> * URL : https://github.com/uqfoundation/ppft
> * License : BSD-3-clause
>   Programming Lang: Python
>   Description : Distributed and parallel Python
>
> […]
>
> It is a dependency of pathos, which is a useful framework that I've
> started using.
>
> I will maintain it within the Debian Python Team.

I packaged it before by mistake and RM'ed it before the freeze. You can
still find the source package `python-ppft` inside the DPT:
https://salsa.debian.org/python-team/packages/python-ppft

Hope it is helpful (remove myself from uploaders if you re-upload,
thanks).

But I see you already uploaded.

Agathe.

Re: New uploader needed for python-colorama

[Agathe Porte]

Hi,

2023-08-31 11:21 CEST, Agathe Porte:
> 2023-08-29 21:17 CEST, Ileana Dumitrescu:
> > I am happy to be the uploader for python-colorama. I just pushed an update
> > to salsa, but as a DM, I require an initial sponsor to upload and allow me
> > the upload permissions for future releases.
>
> Thanks!
> I can sponsor and edit the DM list, I will look into it.

Done, thanks again.

Agathe.

Re: Bug#1042443: ITP: pathos -- Framework for heterogeneous parallel computing

[Agathe Porte]

Hi Julian,

2023-07-28 10:59 CEST, Julian Gilbey:
> Package: wnpp
> Severity: wishlist
> Owner: Julian Gilbey 
> X-Debbugs-Cc: debian-de...@lists.debian.org, Debian Python Team 
> 
>
> * Package name: pathos
>   Version : 0.3.1
>   Upstream Contact: Mike McKerns 
> * URL : https://github.com/uqfoundation/pathos
> * License : BSD-3-clause
>   Programming Lang: Python
>   Description : Framework for heterogeneous parallel computing
>
> […]
>
>
> This is a package I've started using; it provides a very effective
> framework for parallel computing, allowing for constructs that the
> standard Python library does not support.
>
> I will maintain it within the Debian Python Team.

Like python-ppft, this was already packaged in the Python team but not
uploaded: https://salsa.debian.org/python-team/packages/python-pathos

Maybe you can find inspiration in it. I think we should only keep one of
the two repos in the DPT because it can be confusing to have the same
package twice.

Agathe.

Re: New uploader needed for python-colorama

[Agathe Porte]

Hi Ileana,

2023-08-29 21:17 CEST, Ileana Dumitrescu:
> I am happy to be the uploader for python-colorama. I just pushed an update
> to salsa, but as a DM, I require an initial sponsor to upload and allow me
> the upload permissions for future releases.

Thanks!
I can sponsor and edit the DM list, I will look into it.

Best regards,

Agathe.

New uploader needed for python-colorama

[Agathe Porte]

Hi team,

I removed myself from the uploaders of python-colorama while fixing a
bug. I did not know that this was not acceptable in a team-maintained
package where one real human-being still needs to be listed as uploader,
per Debian policy.

Since I am not using the package nor have packages that depend on it, I
am kindly asking if someone can add themselves to the uploaders list of
the package and re-upload.

The package is up-to-date, lintian-clean and IMO low maintainance.

Thanks in advance,

Agathe.

Re: Should cocotb & pyuvm be under Electronics or Python team ?

[Agathe Porte]

Hi Ahmed,

2023-07-23 02:04 CEST, أحمد المحمودي:
>   I am currently working on packages for cocotb [1] & pyuvm [2], both
>   are Python packages, that are used for verification (simulation) of
>   VHDL/*Verilog models, ie. their scope is electronics. Do I am
>   wondering whether to package them under Electeonics team or Python
>   team.

For choosing the team, it depends on which expertise you want the team
which holds the package to have. For pure Python software, I would say
that the expertise of the Debian Python Team is more useful.

>   Also, I've set the Section source control field to 'electronics', yet
>   lintian complained that since the binary package names are
>   python3-{cocotb/pyuvm}, then the section should be 'python'. Should I
>   ignore/override that ? Or should I modifybthe Section field to
>   'python' ?

>From my quick look at cocotb’s documentation [3], it seems to ship at
least one binary in $PATH named `cocotb-config`. Here is how it could be
packaged:

- `cocotb` srcpkg in `electronics` section;
- `python3-cocotb` binpkg in `python` section, containing the library;
- `cocotb` binpkg in `electronics` section, Depends on `python3-cocotb`
  and contains the executables.

Same advice would apply for pyuvm, which I did not look at.

> [1] ITP: https://bugs.debian.org/1041288
> [2] ITP: https://bugs.debian.org/1041285
[3] https://docs.cocotb.org/en/stable/quickstart.html

Bug#1011608: ITP: python-flit-scm -- A PEP 518 build backend that uses setuptools_scm and flit

[Agathe Porte]

Package: wnpp
Severity: wishlist
Owner: Agathe Porte 
X-Debbugs-Cc: debian-de...@lists.debian.org, debian-python@lists.debian.org, 
deb...@microjoe.org

* Package name: python-flit-scm
  Version : 1.5.0
  Upstream Author : Will Da Silva 
* URL : https://gitlab.com/WillDaSilva/flit_scm
* License : MIT
  Programming Lang: Python
  Description : A PEP 518 build backend that uses setuptools_scm and flit

This package makes setuptools_scm compatible with flit. It is a
dependency of python-exceptiongroup that is ITP #1011552.

I intent to maintain this package under the umbrella of the Debian
Python Team.

Bug#1011552: ITP: python-exceptiongroup -- backport of the BaseExceptionGroup and ExceptionGroup classes from Python 3.11

[Agathe Porte]

Package: wnpp
Severity: wishlist
Owner: Agathe Porte 
X-Debbugs-Cc: debian-de...@lists.debian.org, debian-python@lists.debian.org, 
deb...@microjoe.org

* Package name: python-exceptiongroup
  Version : 1.0.0~rc7
  Upstream Author : Alex Grönholm 
* URL : https://github.com/agronholm/exceptiongroup
* License : MIT + PSFLv2
  Programming Lang: Python
  Description : backport of the BaseExceptionGroup and ExceptionGroup 
classes from Python 3.11

This library contains backport of BaseException for Python versions
before 3.11. Since 3.11 is not released yet and that new software [1] is
already using this compat layer, I think we should package it even in
release-candidate form.

[1] It is required for python-cattrs source package update.

I intent to maintain this package under the umbrella of the Debian
Python Team.

Re: Bug#1006663: ITP: python-pyrcb2 -- A powerful asynchronous IRC bot library

[Agathe Porte]

Hi Sandro,

01/03/2022 21:07, Sandro Tosi :

I need it to properly package an IRC bot designed for the
DPT itself.

please share your ideas for such bot here, before installing it the
irc channels, thanks

The bot is already present: rfsbot. It is used to add and remove 
packages from the RFS list in the topic without having to manually 
copy/paste the whole topic and make mistakes.


Its source code is available here: 
https://salsa.debian.org/microjoe/rfsbot (when Salsa is back up). If it 
could be hosted by the DPT instead of on my own server, that would be great.


Bests,

Agathe.