Re: OK to create a new package in "python-team/packages/"

Dear Stefano, thanks for the advice. Am 03.04.2024 16:48 schrieb Stefano Rivera: If you do create a repo and then never upload the package, please delete/archive the repo when you're done. Done. Personally, I usually get the package ready to upload before creating a git repo in the team.

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

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 o

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

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 a

Salsa: Setup tokens

Hello, this is not a regular support message. I was not able to find clear information in the wiki or somewhere else. Please point me to it if exist. My intention is to improve the related wiki pages about it. The command "salsa create_repo" do not work because of a missing SALSA_TOKEN. Tech

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

Hello together, I still struggle with the docs but also improving them. First of all please review my modifications to make sure there are no misleading errors in the content. I restructured the "Policy" section [1]. I shortened and rephrased the text. I also added a sub section "Setup and co

Re: Feature Request (docu): Define "dsc-file"

Close via https://wiki.debian.org/Python/GitPackaging?action=diff&rev1=97&rev2=98

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

Dear Simon, thanks for drawing that big picture for me. That info goes to my Zettelkasten. Kind Christian Buhtz

Re: Feature Request (docu): Define "dsc-file"

Thanks for all your answers. Am 15.03.2024 11:07 schrieb Andreas Tille: Please try a web search for instance with the terms [...] which brought several helpful links. Alternatively you can ask ChatGPT, Gemini or the LLM of your choice I am a bit shocked about that advise. For what was Hyper

"debian/main" support or ticket open?

Hello, my question is technically only. I don't want to troll or start a discussion. So please just say yes or no. ;) 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/

Feature Request (docu): Define "dsc-file"

Hi, this is a feature request to someone who has access and the knowledge to improve. Description of the problem: The second paragraph in tell me about importing a "dsc-file" without explaining what a dsc-file is or why I

OK to create a new package in "python-team/packages/"

Hi, for practicing packaging I start again with the docu and stumbled across this paragraph: It tells me to create a package in "python-team/packages/". I ask myself if I am allowed to and if it is a "good" idea? Te

Re: Spinx help needed

It is always hard to follow such threads. It is unclear if this message is about the Sphinx package itself or a package that do use Sphinx in its build process. There are two bug numbers in the CC fields. But the mail miss links to the bug reports or other information giving more context. Thi

How to provide AppStream data by upstream?

Hello, imagine an upstream project providing an AppStream data file (foobar.metainfo.xml) and it is a full qualified Python project using state of the art build system (pyproject.toml, setuptools or something similiar, src-layout). Should the foobar.metainfo.xml file be a part of the upstrea

AppStream examples

Hello, as upstream maintainer want to start providing AppStream meta data for the package. I can create an XML file. But I also want to know and check how this will look like in real world. I never used a "Software Center". The question is how can I check the "rendering" of an AppStream XML

Re: Recommended way of installing system-wide python application and libraries

Hello Ivan, I am not an expert in Python Packaging and also not in Debian-specific Packaging of Python stuff. So please take my advice with care. But I do have some experience and did a lot of experiments. When it comes to pure Python Packaging I would suggest my demo repository. It is not f

Wiki "AppStyleGuide": Not clear to new users

Hello, related to https://wiki.debian.org/Python/AppStyleGuide There are several problems with that page. It is to short to be a single instance. Just add it as a section to the "LibraryStyleGuide" and rename it to "StyleGuide". This would help against to much fractioning of the documentation

Wiki "LibraryStyleGuide": pyproject.toml not mentioned

Hello, related to https://wiki.debian.org/Python/LibraryStyleGuide The "pyproject.toml" file is not mentioned here. But it is current recommended way (and central file) to do python packaging. If it is not possible to use that file in context of debian packaging this also should be mentioned

Wiki: How to discuss problems and improvements

Hello, to me it is not clear how to discuss problems and improvements of the wiki. There is no dedicated mailing list to that topic. I assume this mailing list here should not polluted with stuff like this. In the footer of the wiki (e.g. https://wiki.debian.org/Python/FAQ) is a ling to a wik

Do unit tests on Debian Servers/Build system?

Hello, I try to understand some basics about debian packaging Python applications and the upload and test process. My question in short: When (at which time point in the process of packaging python applications for Debian) do the Python unit tests run? I know about the Salsa instance. Maintai

Re: [backintime] I'll package the next release

Dear Carsten, thanks for your reply. Am 15.09.2023 11:19 schrieb Carsten Schoenert: the DPT isn't the maintainer of this package, you are aware of this? DPT = Debian Python Team ? Yes I'm aware of this. But to my knowledge the list is not restricted to DPT package topics. Do you have tal

[backintime] I'll package the next release

Hello together, I hope different from the past this announcement will work this time. Last time I announced the will to package something ("feedparser") but someone else did it without communication. Back In Time [1][2] will have a new upstream release [3] in the next days. I [4] will try to

Re: How to realize different test categories?

Hello Timo, thanks for reply. Am 28.07.2023 14:56 schrieb Timo Röhling: I had a look at the backintime sources, and I noticed that you First of all: I haven't nothing. :D I'm not the founder of backintime (BIT) just the 3rd generation maintainer trying to modernize an over 15 year old pytho

Re: [backintime] Switch the maintainer to "Debian Python Team (DPT)"

Dear Simon, thanks for your thougths. Am 28.07.2023 14:44 schrieb Simon McVittie: The other angle this could be approached from is as an upstream developer: IMHO this is the only angle it should be approached from because it is upstreams responsibility and Debian shouldn't waste resources an

How to realize different test categories?

Hello, I'm upstream maintainer (but not founder) of "backintime". I realized that most of the tests in my test suite are integration or system tests which are impossible to handle by Debians build server and testing system (how do you name it?). My package do use something like "./configure &&

Re: [backintime] Switch the maintainer to "Debian Python Team (DPT)"

Dear Carsten, thanks for taking time and replying. Am 28.07.2023 11:53 schrieb Carsten Schoenert: you really should read the Social Contract/DFSG, the Debian policy and the Developers reference a few times. I'll do. There is no rule that any DD or DM *must* do something in Debian, so you pr

Re: [backintime] Switch the maintainer to "Debian Python Team (DPT)"

Dear Mechtilde, thanks for taking time to reply. Am 28.07.2023 07:31 schrieb Mechtilde: Did you try to build the last released version? What are your problems to build backintime? At upstream I have no problems to build and test it because I'm upstream. ;) But in my understanding the probl

Re: how to properly split up into python3-foo and foo-util package?

Am 12.07.2023 13:25 schrieb Andrey Rakhmatullin: On Wed, Jul 12, 2023 at 11:05:57AM +, c.bu...@posteo.jp wrote: You build two Debian packages (deb-files) out of one source tarball? Interesting to know that this is possible. It's definitely possible and I would expect any good guide to menti

Re: how to properly split up into python3-foo and foo-util package?

Dear Christoph, I'm sure I can not help you but I'm asking because I want to learn. Do you have a link to your repository? What do you mean by the terms "simple Python package" and "two packages"? These terms do not exists in Python context. Python do differentiate between "Distribution Packa

[backintime] Switch the maintainer to "Debian Python Team (DPT)"

Dear Python Team, dear Jonathan, first of all, please take my congratulations for the Debian 12 release yesterday. I'm member of the upstream maintenance team of "Back In Time" [1]. In short: I would like to switch its Debian Maintainer to "Debian Python Team (DPT)". I'm a little concerned

NMU: backintime

Hello, I know we are in a Freeze and all of you have a lot to do. So I make it short. Please consider that NMU. I'm part of upstream maintainer team "backintime". I wasn't able to establish contact with Jonathan Wiltshire (jmw) who is the Debian Maintainer of that package. The fabulous Fabio

Re: Unittests writing to HOME (backintime)

Dear Andrey, thank you for the reply. Am 29.03.2023 11:40 schrieb Andrey Rakhmatullin: The usual solution is AFAIK to set a temporary $HOME inside d/rules though. I was looking into https://salsa.debian.org/jmw/pkg-backintime/-/blob/debian/debian/rules I don't see creation of a HOME or

Re: BTS: What are Unclassified bugs?

Thanks for your reply. Am 29.03.2023 11:35 schrieb Andrey Rakhmatullin: One example is the backintime package https://bugs.debian.org/cgi-bin/pkgreport.cgi?repeatmerged=no&src=backintime (I don't see the word "Unclassified" on that page) Yes it is gone. Bug is closed or modified. Can't figur

Re: BTS: Merging bugs not working because of "forwarded" to upstream bug

Dear Hilmar, thanks for the reply. Am 29.03.2023 10:33 schrieb preusse: Do, what it says: the forwarded value must be equal for both bugs. The system should do what I say: merge. :D Looking into the BTS's own bug tracker it seems it has no effect when opening a bug report about that.

BTS: Merging bugs not working because of "forwarded" to upstream bug

Hello, I try to understand a problem with the Bug Tracking System. I tried to merge two bugs because one is a duplicate. I send to control@ merge 985631 985256 I also tried the other way around switching the numbers. But I got back that message that I don't understand. The link to the u

BTS: What are Unclassified bugs?

Hello, I couldn't find a mailing list specific to the Bug Tracking System. In the bugs summary list for a specific package I can find "Unclassified" bugs. But what is "Unclassified"? Looking into other (not "Unclassified") bugs all have a "severity", some are "confirmed" some not. So a missi

Unittests writing to HOME (backintime)

Hello, I assume this topic is not specific to one package but to the whole python packaging universe. There is "backintime" which unittests do write to $HOME. I'm one of the new upstream maintainers and know that this isn't a good idea. It will take time to fix this. About that problem ther

Re: Location of translations for package description

Dear Joost, thanks for the reply. I understand there is a project doing this manually. Am 20.02.2023 15:07 schrieb Joost van Baal-Ilić: See https://ddtp.debian.org/ and https://wiki.debian.org/DDTP for information on the translation infrastructure for package descriptions. Puh... How do I s

Location of translations for package description

Hello, there is a German package description https://packages.debian.org/de/bookworm/backintime-common this is also available in English https://packages.debian.org/en/bookworm/backintime-common It seems to me that the English version is extracted from the control file https://salsa.debian.or

Re: How should upstream document/communicate none-Python dependencies?

Thanks for your reply. Am 02.02.2023 14:46 schrieb Jeremy Stanley: with https://pypi.org/project/bindep which is effectively a manifest of distribution package names and a grammar for indicating Awesome. The upstream maintainers have to create a binddep.txt file. And the distro maintainers do

How should upstream document/communicate none-Python dependencies?

Hello, I'm part of upstream maintainer team of "backintime" (BIT). A modern Python project (which BIT is currently not) would specify dependencies and other build related information's into a pyproject.toml file. But some Python applications (e.g. BIT) do have non-Python dependencies to speci

Re: What is this about the metainfo-file?

Please let me add one additional thought. It seems easy to me to extract he meta data (via importlib.metadata) from a python project that suites to the python packaging standards (providing a pyproject.toml, setup.cfg and things like that). In that case it seems easy to have a debian-python-p

What is this about the metainfo-file?

Hello, I try to understand the "metainfo" file I was pointed to by an "AppStream hint". https://appstream.debian.org/sid/main/issues/backintime-qt.html There are some links pointing to freedesktop.org. There is also appstream.debian.org. I read that and got the keys of that concept. But I

Docu about Salsa workflow

Hello, sorry for asking. I'm looking or the right document explaining the workflows on Salsa. Am I on the right way here: https://wiki.debian.org/Teams/PythonTeam ? Most projects on Salsa do have three branch names. I need an explanation of them and how they interact. Kind Christian

Re: How do you create entry-points for Python applications?

Dear Scott, thanks for the reply. Am 19.12.2022 06:25 schrieb Scott Kitterman: Pybuild using the pyproject plugin will build a wheel and then install the necessary files in the package using the installer module. The entry point scripts are in the wheel, just like an upstream built wheel. Do

Re: How do you create entry-points for Python applications?

Am 18.12.2022 23:03 schrieb Danial Behzadi دانیال بهزادی: AFAIK Debian helper for Python handles this ;) Yes, but how? Does it ignore the pip-default-entry-point-scripts? Does it create its own script? Do you have to explicit write a script?

How do you create entry-points for Python applications?

Hello, a python application isn't a binary but a script. So to invoke such an application there need to be a shell script somewhere in PATH that invoke that script via python3 interpreter. Imagine an application with a GUI (qt, tikinter, gtk, ...). On the upstream site modern python projects

Re: Python 3.11 for bookworm?

Am 13.12.2022 10:15 schrieb Timo Röhling: One remaining problem is the unmaintained nose package [...] done some work patching up nose This question is just for my learning: Why is nose patched? Upstream nose is unmaintained for years. I understand that you cannot drop nose from Debian in th

pyfakefs: Outdate version was migrated today

Hello folks, my question is not critic but just learning purpose. Because in the Debian universe I always assume that there is a good reason behind each activity, no matter if I understand it or not. Here is one I don't understand. Today (9th December '22) pyfakefs 4.6.3 was migrated [1] into

Python distributions with multiple packages

Hello, today I found out that it is possible to create a Python "Distribution Package" [1] (e.g. a whl-file) that contain more then one "Importable Packages" [2]. So you can do "pip3 install mydistropackage" and after that you can do "import mya" and "import myb". Are you aware of any pack

dh_python or pybuild

Hello, I am not sure if I misunderstand something or if the documentation is inconsistent. The PythonPolicy https://www.debian.org/doc/packaging-manuals/python-policy/ tells me that dh_python should be the preferred tool for packaging (https://www.debian.org/doc/packaging-manuals/python-polic

Wiki: Debian Python Policy docu not on team site

Hello, this is about the wiki page of that team. https://wiki.debian.org/Teams/PythonTeam I accidentally found the "Debian Python Policy documentation". https://www.debian.org/doc/packaging-manuals/python-policy/ Looks nice and very important for new team members. Maybe it would help if it is

Difference between "python-debian team" and "Debian Python Team"

Hello together, what are the differences between this two salsa groups? https://salsa.debian.org/python-team https://salsa.debian.org/python-debian-team As a novice in debian python packaging it extremely confuses me. And I have impression that "team sites" in salsa (e.g. the two links above)

Re: xlsxwriter: How to change homepage url

Dear Emmanuel, Am 15.09.2021 21:36 schrieb Emmanuel Arias: Looking in the salsa repo [0], it is very old. And that shouldn't happen. I can updated to the last unstable version tonight/tomorrow. Just to improve my knowledge about Debian processes: What does it mean to update the salsa repo to

Re: Python style guide checker (formerly called pep8)

Am 12.09.2021 10:23 schrieb Geert Stappers: In which package is a pep8 code style checker? Upstream "pep8" was renamed to "pycodestyle". So look at https://tracker.debian.org/pkg/pycodestyle

feedparser: New packaging

Dear list members, dear Mr. Millon, I am interested in packaging “feedparser” (https://tracker.debian.org/pkg/feedparser) for Debian. I addressed Mr. Millon directly because he is named as "uploader" for that package. The "maintainer" is the "Debian Python Team". So is this list the right pla