Am 20.02.2023 15:07 schrieb Joost van Baal-Ilić:
See https://ddtp.debian.org/ and https://wiki.debian.org/DDTP
This feels much better then the wiki
https://www.debian.org/international/l10n/ddtp.en.html
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
] will try to prepare the packaging for Debian this time. The
next Debian release is minimum 2 years away so I have enough time. ;)
Kind
Christian Buhtz
[1] -- <https://github.com/bit-team/backintime>
[2] -- <https://tracker.debian.org/pkg/backintime>
[3] -- <https://github.com/bit-
Hello Jonathan,
thank you for the reply.
Am 13.11.2024 12:15 schrieb Jonathan Carter:
This was discussed at the Python BoF at DebConf in ROK earlier this
year.
OK, nice to know that there was a discussion before. Did I missed the
announcement of the results of this discussion in this mailing
ce myself to the community. Which
place would be the best for it? The Debian Python Mailinglist or
anywhere else? Or a link to a Debian Wiki Entry?
Best regards,
Christian Buhtz
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
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
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)
p if it is linked on the team wiki page.
Kind
Christian Buhtz
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
ckage.deb") or do you separate into "python3-mya.deb"
and "python3-myb.deb"?
Kind
Christian Buhtz
[1] --
<https://packaging.python.org/en/latest/glossary/#term-Distribution-Package>
[2] --
<https://packaging.python.org/en/latest/glossary/#term-Import-Package>
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
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
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
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?
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
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
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
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
d Debian package (e.g. "python3-pyfakefs")?
Kind
Christian Buhtz
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
://salsa.debian.org/jmw/pkg-backintime/-/blob/debian/debian/control
But I'm not able to find the German (or any other translated) version in
the source repo.
Is this done on the fly in the back somehow?
btw: I'm upstream maintainer of that package.
Kind
Christian Buhtz
is an automatic mechanism that the translations are
marked as outdated when the original source (e.g. the control file on
salsa) is modified. Correct?
Kind
Christian Buhtz
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
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
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
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.
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
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
ckage.
The fabulous Fabio Fantoni still opened an NMU for that package.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033829
Would be great of some of you could have a look at it.
Kind
Christian Buhtz
for
the package?
Is there a defined process how this should be done?
Thanks in advance.
Christian Buhtz
[1] -- <https://tracker.debian.org/pkg/backintime>
[2] -- <https://bugs.debian.org/1033829>
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
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
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
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
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 &&
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
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
] will try to prepare the packaging for Debian this time. The
next Debian release is minimum 2 years away so I have enough time. ;)
Kind
Christian Buhtz
[1] -- <https://github.com/bit-team/backintime>
[2] -- <https://tracker.debian.org/pkg/backintime>
[3] -- <https://github.com/bit-
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
to
be contained in the deb file I assume.
Thanks in advance
Christian Buhtz
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
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
maybe its content is
outdated and not relevant anymore?
Kind
Christian Buhtz
finished yet but it explains some packaging issues
and use cases with examples.
<https://codeberg.org/buhtz/tech-demo-python-packaging>
When this repo is "finished" and well reviewed by the Python community I
will start a similar repo with demos about Debian Python Packaing. T
Package: wnpp
Severity: wishlist
X-Debbugs-Cc: debian-python@lists.debian.org
* Package name: python3-pytermgui
Version : 7.7.0
Upstream Author : Balázs Cene
* URL : https://ptg.bczsalba.com/
* License : MIT
Programming Lang: Python
Description : Python
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
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
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
ial
upload. But I suspect this is a long way. So on short view that repo
will be for practicing only. Am I allowed to create such a repo in my
position?
Kind
Christian
[1] -- <https://codeberg.org/buhtz/hyperorg>
^
I L <https://wiki.debian.org/DSC-DEFINITION>
L <https://wiki.debian.org/PackagingWithGit/GitDpm/ImportDsc>
Please let me know if there is another "channel" where I should open
such requests.
Thanks in advance
Christian Buhtz
that to "debian/main"?
It might be that the existing toolchain is not yet able to adapt to it.
Do we have an open ticket somewhere that I can monitor?
Thanks
Christian Buhtz
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
Dear Simon,
thanks for drawing that big picture for me.
That info goes to my Zettelkasten.
Kind
Christian Buhtz
Close via
https://wiki.debian.org/Python/GitPackaging?action=diff&rev1=97&rev2=98
scussion at MoinWiki to improve the
handling of headings and page titles [2]. The later should not be part
of the TOC.
Best Regards,
Christian Buhtz
[1] -- <https://wiki.debian.org/Python/GitPackaging#Policies>
[2] -- <https://github.com/moinwiki/moin/issues/1648>
cribed but it is not totally clear for new users what they are about
or what the implications are. Any recommendations from DPT about that?
Just select all?
A more broad question: I never used tokens before. I do use SSH keys
when accessing Codeberg, GitHub or something else. Are this tokens a
replacement for SSH keys? Should I prefer one of this two methods?
Thanks in advance
Christian Buhtz
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
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
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.
time/common/
/usr/share/doc/backintime/qt/
Thanks in advance.
Best regards,
Christian Buhtz
[1] -- <https://tracker.debian.org/pkg/backintime>
used more
productive into other problems.
Who decide which Python version is introduced in Debian? Isn't there a
council for heavy decisions like this?
Regards,
Christian Buhtz
Am 13.11.2024 11:04 schrieb PICCA Frederic-Emmanuel:
do we know how long we will have to fix all the FTBFS and autopkg
Hello,
I was not sure which list is appropriate for this question. Because of
that I try it here because I am quit familiar with this community.
To my understanding of the policy the license file of package should be
installed into
/usr/share/doc//LICENSE
How to handle it if a project
Hello Stefano,
thank you for your reply.
Am 18.11.2024 13:55 schrieb Stefano Rivera:
To my understanding of the policy the license file of package should
be
installed into
/usr/share/doc//LICENSE
It's spelled: /usr/share/doc//copyright
To my understand the "copyright" file is somethin
Hello Andrey,
Thank you for the reply.
Am 18.11.2024 15:26 schrieb Andrey Rakhmatullin:
On Mon, Nov 18, 2024 at 01:41:34PM +, c.bu...@posteo.jp wrote:
To my understand the "copyright" file is something Debian specific.
This does not exist in my upstream project but is "generated" by my
Deb
Dear Andrey,
Am 25.12.2024 20:56 schrieb Andrey Rakhmatullin:
https://github.com/search?q=repo%3Acogent3%2Fcogent3%20loky&type=code
Sending URLs only is quit annoying to all other list members and not an
answer.
I know the details and that there are reasons why this package depend on
the o
Hello,
I am a Python developer and upstream maintainer.
I am not much experience when it comes to distro packaging.
This is just an example of a case I often do observe. And I always ask
myself why this happens.
Am 25.12.2024 18:47 schrieb Andreas Tille:
the new version of python-cogent needs
Hello,
is it OK to remove the Wiki page "Python/Dead Batteries"?
<https://wiki.debian.org/Python/Dead%20Batteries>
Some vetos or good reasons to keep it?
Regards,
Christian Buhtz
68 matches
Mail list logo
