Re: Uscan: watch and changelog

Dear Paul, thanks for your feedback. On 2024-03-31 17:17 Paul Boddie wrote: > then the developers claim that they didn't have time to document That is the advantage when doing FOSS. You do have the time. There is not boss or customer behind your back. Teh problem in FOSS is just the priorities

Re: Uscan: watch and changelog

Dear Soren, my primary intention is always to improve Debian. That also involves a better image to the public and potential new users and contributors. On 2024-03-29 13:42 Soren Stoutner wrote: > Much of Debian’s documentation is not written for people > who are new to the topic, but for people

Re: Uscan: watch and changelog

On 2024-03-29 11:29 Soren Stoutner wrote: > One of the interesting things about uscan This is that kind of "big picture" explanations that should be written to the Wiki. Texts like this are the missing link between man pages, references and policy documents. Thanks in advance

Re: Uscan: watch and changelog

On 2024-03-29 18:07 Carsten Schoenert wrote: > Am 29.03.24 um 17:39 schrieb c.bu...@posteo.jp: > > On 2024-03-29 16:23 Carsten Schoenert > > wrote: > >> You need to use "opts=mode=git, ...", see the man page of uscan. > > > > Are you sure. > > Of course I'm sure, I've tested the snippets

Re: Uscan: watch and changelog

Dear Carsten, thank for your reply and your patience with me. :) On 2024-03-29 16:23 Carsten Schoenert wrote: > You need to use "opts=mode=git, ...", see the man page of uscan. Are you sure. For example this watch file do not use "opts="

Re: Uscan: watch and changelog

On 2024-03-29 19:26 Andrey Rakhmatullin wrote: > On Fri, Mar 29, 2024 at 02:05:41PM +, c.bu...@posteo.jp wrote: > > The Wiki page is not > > up-2-date > What's wrong with it? I was not clear in my initial mail, where I only wrote that "Uscan don't work

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

On 2024-03-29 15:34 weepingclown wrote: > 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. Correct. The information is there. But the linkage between them

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

On 2024-03-29 14:48 Carsten Schoenert wrote: > 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

Uscan: watch and changelog

X-Post: Hi, try to get uscan working with an upstream repo hosted at Codeberg.org (Forgejo based). The Wiki page is not up-2-date and I try to figuring out how it works to update that page. Uscan don't

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

On 2024-03-29 09:52 Carsten Schoenert wrote: > New Maintainer Guide: > https://www.debian.org/doc/manuals/maint-guide/ That document itself points to a new rewritten "tutorial" in its first paragraph. I suggest to remove one of

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

Dear Boyuan Yang, Thanks for your feedback. > I can see that > https://wiki.debian.org/Python/GitPackaging#Creating_a_new_package is > indeed poorly written: > > *) It still > [...] I agree to your list of aspects that need to be improved. It seems you really understood the "workflow" of a

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

On 2024-03-29 07:48 Andreas Tille wrote: > Perhaps a hint to my Live packaging workshop > > https://debconf23.debconf.org/talks/34-live-packaging-workshop/ Also not Python (but Go?) related but I will check it out.

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

Dear Metchtilde, Thanks for the reply. On 2024-03-29 08:28 Mechtilde wrote: > 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

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

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"

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

On 2024-03-20 22:55 c.bu...@posteo.jp wrote: > 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 > ? I think this is a

Docu: Need help to understand section about package creation

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

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

Dear Nicholas, thanks for the reply. On 2024-03-15 20:13 Nicholas D Steeves wrote: > Christian, have you filed an ITP (intent to package) yet? If not, > please do so as soon as you can. > > https://wiki.debian.org/ITP No I have not because it is to much pressure. I am testing and playing

PyQt6 backport for oldstable?

Hello, might there be a realistic chance that PyQt6 will be released in the "oldstable-backports" repo? Upstream-Support of PyQt5 is off. But there are some "oldstable" users out there not able to upgrade to PyQt6 or depending applications. Kind Christian

Re: debian/watch: How to watch version tags and what to capture?

Dear IOhannes, thanks for your reply and your thoughts. On 2023-09-17 11:11 IOhannes m zmölnig (Debian/GNU) wrote: > i get your point that you want the information fast, but it seems you > are just using some arbitrary constraint that fits your personal need. > it appears that for "most"

Re: debian/watch: How to watch version tags and what to capture?

Dear Étienne, On 2023-09-17 10:53 Étienne Mollier wrote: > $ reportbug tracker.debian.org thanks for pointing this out. Sometimes it is to easy. I am not new to Debian but always forget about "pseudo packages".

Re: debian/watch: How to watch version tags and what to capture?

Hello, maybe it depends on my non-nativ English that I'm not able to make myself clear. On 2023-09-17 09:56 Mechtilde Stehmann wrote: > What do you expect? As I told. Information just in time. Within in a delay of 1 or 2 hours the tracker/dashboard should inform about the new release. If this

Re: debian/watch: How to watch version tags and what to capture?

Dear Felix, thanks for the reply. On 2023-09-17 09:13 Felix Zielcke wrote: > Tracker needs a bit of time to > update all the infos shown. 1-2 days aren't unusual and not directly a > bug in it. Is there a bug tracker for the tracker? The term "tracker" indicates just in time and not two days.

Re: debian/watch: How to watch version tags and what to capture?

Dear Metchilde, thanks for reply. On 2023-09-17 08:51 Mechtilde Stehmann wrote: > Am 17.09.23 um 08:35 schrieb c.bu...@posteo.jp: > > Might it just be that "uscan" doesn't run every day on the Debian > > servers? :) > > > > I tried to reproduce it on my local machine. But there the new > >

Re: debian/watch: How to watch version tags and what to capture?

Might it just be that "uscan" doesn't run every day on the Debian servers? :) I tried to reproduce it on my local machine. But there the new version is recognized without problems. $ uscan --verbose uscan info: uscan (version 2.21.3+deb11u1) See uscan(1) for help uscan info: Scan watch files in

debian/watch: How to watch version tags and what to capture?

Hello together, do I get it right that the syntax of the debain/watch file do use regex? https://repo .*/v?(\d.*)@ARCHIVE_EXT@ When an application do use version tages like "v1.4.0" and based on my knowledge and experiments on regex101.com this won't work. Am I right? There is also a

German Debian Forum : How to do packaging ("HowTo: Wie paketiert man eine Python Bibliothek?")

Hello, I would like to inform about that in the German Debian Forum is a thread explaining how to package a python library for official Debian. https://debianforum.de/forum/viewtopic.php?t=187764 Kind Christian

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

Dear Carsten, thanks for your feedback, your kind words and your patience with my frustration. :) I was thinking about what it is what bothers me here. It is not that "the work" isn't done or bugs not fixed. It is that there is no reaction; zero; total silence. The current Debian release is

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

Hello, On 2023-06-12 10:40 Jonathan Carter wrote: > Adding DPT to at least uploaders and having the package VCS in the > python-team namespace would probably be a good idea, but that's up to > Jonathan Wiltshire. I have to state that after 5 weeks of waiting there is no reaction from Jonathan

Re: xlsxwriter: How to change homepage url

Dear Scott On 2021-09-15 10:59 Scott Talbert wrote: > so that would need to be sorted out. This sounds like a task that should be taken by someone more experienced then me.

Re: xlsxwriter: How to change homepage url

Thanks for the reply's. On 2021-09-15 09:02 Scott Talbert wrote: > It seems that this package should probably be fully moved and adopted > into the Debian Python Team - it seems to have been partially done. I would say the salsa project is outdated because the version number in setup.py does

xlsxwriter: How to change homepage url

Hello, this is about the "xlsxwriter" package [1] and this one year old bug report about defect "homepage" url [2]. I am new in the neighborhood and think this is a good issue to learn something about the Debian internals. So where does the "homepage" url in the "link" box on the right side of

Request to join the team by Christian Buhtz

Dear team members, I want to introduce myself and also to request joining the team. > Why you want to join the team I want to package feedparser [1][2]. The main reason is my own software (not yet released [3]) depends on it. I am in good contact with the upstream maintainer for years and he