Hello,As I said before, we no longer use git-dpm and git-dpm-specific
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 myYes, uscan doesn't make sense in that context.
case. For example "uscan" don't work because it does not know what and
where to download. Of course I understand that.
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.
Yes, uscan doesn't make sense in that context.
Am 20.03.2024 22:43 schrieb Andrey Rakhmatullin:
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
?
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
Hello again,
the problem persists.
I don't have the right information in the wiki. So I don't know how to >proceed with creating a package.
Can someone point me into the right direction please.
I have the repo on Salsa. But it is empty. And the commands
described in "Creating a new package" don't help me to fill it up.
Thanks in advance,
Christian Buhtz
On 2024-03-20 22:32 <c.buhtz@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
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
<br>I have the repo on Salsa. But it is empty. And the commands<br>described in "Creating a new package" don't help me to fill it up.<br><br>Thanks in advance,<br>Christian Buhtz<br><br>On 2024-03-20 22:32 <c.buhtz@posteo.jp> wrote:<br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #729fcf; padding-left: 1ex;"><div dir="auto">Hello,<br><br>in order to improve the documentation I need to understand some parts.<br>But I am stuck. I don't get it
</pre></blockquote></div></body></html> ------6ZIE85JF8EP6XQ6USOQZ0EEU9SLOW6--
I don't have a good solution to Wiki pages yet since the article logic
needs some major editing.
I can see that https://wiki.debian.org/Python/GitPackaging#Creating_a_new_package is
indeed poorly written:
*) It still
[...]
For newcomers, I believe they will get lost at the very first line on https://wiki.debian.org/Python/GitPackaging#Creating_a_new_package
If you really want a readily-available better documentation, consider
reading the official documentation of git-buildpackage at https://honk.sigxcpu.org/projects/git-buildpackage/manual-html/ .
After you understand that, merge the remaining useful information from https://wiki.debian.org/Python/GitPackaging to get a thorough
understanding.
Perhaps a hint to my Live packaging workshop
https://debconf23.debconf.org/talks/34-live-packaging-workshop/
If some want to have more information you can read
https://ddp-team.pages.debian.net/dpb/BuildWithGBP.pdf in German
This document is not Python related. The section about Python is empty.
See section 15 at PDF page 65.
New Maintainer Guide:
https://www.debian.org/doc/manuals/maint-guide/
Starting with Debian packaging isn't a easy thing and there is *not* the
one way to do it right. And there are for sure hundreds of HowTos out
there. You will need to try a few of them and chose in the end the
workflow that fit's best for you.
git-buildpackage is one of the high level tools that can and should
packaging tasks easier, to use it effective you will need to know what
it is doing under the hood, means you need to be familiar with the low
level tools that getting called by gbp.
On Friday, 29 March 2024 09:52:14 CET Carsten Schoenert wrote:
Starting with Debian packaging isn't a easy thing and there is *not* the
one way to do it right. And there are for sure hundreds of HowTos out
there. You will need to try a few of them and chose in the end the
workflow that fit's best for you.
The problem with this advice is that for the Debian Python Team, there probably aren't many ways to "do it right". Instead, as I understand it, there
will be very few ways that people tolerate, as recent discussion on this list has indicated.
In the end, I did my usual thing and distilled the documentation's prose down to a concise workflow to remind me of what I might need to do if I were to start packaging something else. In fact, I wrote the following for the Moin 2.0 packages and then made use of it for the other package:
git branch -c master upstream
git checkout -b debian/master
<introduce debian directory here>
git add debian
git commit
<introduce upstream tag here, if you want to avoid hassle with Salsa>
git push origin <upstream tag>
gbp buildpackage --git-debian-branch=debian/master \
--git-upstream-tag='upstream/%(version)s' --git-builder=sbuild
P.S. The argument made about needing to understand what happens "under the hood" is something of an indictment of the way technology is developed these days. A tool that is meant to simplify something should present its own coherent level of abstraction; deferring to lower-level mechanisms is something that the Git developers and community like to do, which is why the usability of Git is the subject of occasional jokes and somewhat more infrequent attempts to wrap it in more usable interfaces.
As I understand it, the current
problem we have is more about the wiki being less organized than
there not being sufficient resources or them not being easily
accessible to everyone.
BTW: I posted my way on how I created a new Python package for Debian
in the German Debian forum extensively and in length last year while
DC [1]. Because I also know were starters typically struggle with and
I was in the need to introduce a new Python package as a dependency
for another package.
I'm unsure if Christian did follow my steps
[...]
[1] https://debianforum.de/forum/viewtopic.php?t=187764
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 350 |
Nodes: | 16 (2 / 14) |
Uptime: | 10:46:18 |
Calls: | 7,625 |
Files: | 12,793 |
Messages: | 5,686,543 |