Re: morph's abandoned packages (list)

hi! On Sat, Mar 30, 2024 at 8:20 AM Thomas Goirand wrote: > > On 3/29/24 21:18, Timo Röhling wrote: > > Hi Thomas, > > > > * Thomas Goirand [2024-03-17 23:09]: > >> Anyone is welcome to join, it's just that I'm using git tag workflow, > >> so it doesn't fit in the DPT, but that's the only thing.

Re: morph's abandoned packages (list)

On 3/29/24 21:18, Timo Röhling wrote: Hi Thomas, * Thomas Goirand [2024-03-17 23:09]: Anyone is welcome to join, it's just that I'm using git tag workflow, so it doesn't fit in the DPT, but that's the only thing. I am not familiar with that workflow and could not find any documentation. Can y

Re: Uscan: watch and changelog

I agree. Much of Debian’s documentation is not written for people who are new to the topic, but for people who already know the information and just want to be reminded about some of the tricky parts. Anything you can do to improve the documentation would be greatly appreciated. On Friday, Mar

Re: morph's abandoned packages (list)

Hi Thomas, * Thomas Goirand [2024-03-17 23:09]: Anyone is welcome to join, it's just that I'm using git tag workflow, so it doesn't fit in the DPT, but that's the only thing. I am not familiar with that workflow and could not find any documentation. Can you give me a quick overview what I shou

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: Seeking a small group to package Apache Arrow (was: Bug#970021: RFP: apache-arrow -- cross-language development platform for in-memory analytics)

Hi, Am 25.03.24 um 19:17 schrieb Julian Gilbey: * Reading and writing file formats (like CSV, Apache ORC, and Apache Parquet) liborcus supports this (Apache Parquet) if built with Apache Arrow. And thus makes LibreOffice being able to handle it. I didn't invest any time in Apache Ar

Re: Seeking a small group to package Apache Arrow (was: Bug#970021: RFP: apache-arrow -- cross-language development platform for in-memory analytics)

On Mon, 2024-03-25 at 18:17 +, Julian Gilbey wrote: > > > So this is a plea for anyone looking for something really helpful to > do: it would be great to have a group of developers finally package > this!  There was some initial work done (see the RFP bug report for > details: https://bugs.de

Re: Uscan: watch and changelog

On Friday, March 29, 2024 10:16:56 AM MST c.bu...@posteo.jp wrote: > There is no "opts=". So again. Why would you suggest to use "opts="? I want to > learn. I don't want to fight. One of the interesting things about uscan is there are often multiple different ways to connect to an upstream sourc

Re: Updated package list with packages open for adoption (Was: morph's abandoned packages (list))

On 2024-03-28 Andreas Tille wrote: [...] > ? #1065221 O: py7zr -- pure Python 7-zip library >rdepends: recoll (Kartik Mistry ) > calibre (YOKOTA Hiroshi , > Martin Pitt , > Nicholas D Steeves ) > Hint: This package is lagging quite beh

Re: Uscan: watch and changelog

On Friday, 29 March 2024 17:39:04 CET c.bu...@posteo.jp wrote: > > 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=" > https://sources.debian.org/src/backintime/1.4.3-

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 before

Re: Uscan: watch and changelog

Am 29.03.24 um 17:39 schrieb c.bu...@posteo.jp: 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. Of course I'm sure, I've tested the snippets before

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=" https://sources.debian.org/src/backintime/1.4.3-1/debian/

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 w

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 is

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 new

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

Hi, As an addendum, there is also dedicated wiki pages[0] intended to be of help to newcomers. Not saying that solves everything mentioned before, but it does help quite a lot. As I understand it, the current problem we have is more about the wiki being less organized than there not being suffi

Re: Uscan: watch and changelog

Am 29.03.24 um 15:05 schrieb c.bu...@posteo.jp: I assume I have not yet understood the purpose of the changelog in context of uscan. What do I miss? This is "debian/watch": version=4 # RegEx in Perl dialect https://codeberg.org/buhtz/hyperorg/archive/v(\d+).(\d+).(\d+).tar.gz This is a dummy

Re: Uscan: watch and changelog

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? -- WBR, wRAR signature.asc Description: PGP signature

Re: Uscan: watch and changelog

On Fri, Mar 29, 2024 at 07:21:48PM +0500, Andrey Rakhmatullin wrote: > > I assume I have not yet understood the purpose of the changelog in > > context of uscan. What do I miss? > It needs debian/changelog to know the current upstream version of the > package. (also this is answered explicitly in u

Re: Uscan: watch and changelog

On Fri, Mar 29, 2024 at 02:05:41PM +, c.bu...@posteo.jp wrote: > X-Post: > > Hi, > > try to get uscan working with an upstream repo hosted at Codeberg.org > (Forgejo based). > > The Wiki page is not

New upstream version for python-pint

Dear Thomas and Ondřej, a couple of packages that I maintain are impacted by an RC bug in python-pint (#1067318). I think that an update to the to the latest pint version 0.23 should be sufficient to fix the issue. If you agree, I would like prepare the package for the new upstream version in

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 w

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

Hello Paul, Am 29.03.24 um 13:49 schrieb Paul Boddie: 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

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

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 f

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 them

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

Am 29.03.24 um 08:51 schrieb c.bu...@posteo.jp: This document is not Python related. The section about Python is empty. See section 15 at PDF page 65. This isn't really needed yet, packaging Debian packages is technically always the same. You seems to have a general problem to understand what

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

Hello everyone, first some general information. As I understand the information from the python-team in the wiki is to inform special handlin here. Newcommers should first read the New Maintainer Guide and the Developer Reference You want a "complete" description about packaging also for new

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 newb

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 pa