Re: Updating khal to fix RC bug #1023341
Quoting Daniele Tricoli (2022-12-16 20:03:09) > Hello Jonas, > > On 16/12/2022 15:10, Jonas Smedegaard wrote: > [CUT] > > > I will have a closer look now, then get back to you. > > Oh, many thanks! :) > > > Ususally when I "look" at a package I routinely update it as well. > > I like this approach, it keep all the stuff clean. > > > Would you prefer that I roll back whatever changes I do during my > > "looking at it" and guide you to gain same understanding as me? > > Because if your interest is simply to get khal updated then > > simpler for me is do (hopefully) all myself and only tell you without > > leaving room for you to redo and potentially learn more from that DIY > > experience. I am happy to do that slower process - I find it fun to > > collaborate (am just not very used to it), so please do tell if you are > > eager to learn. :-) > > I would love to learn, but please don't roll back your changes, time is > our most precious resource. :) > > I made a copy of my local clone and I dropped all the new commits you > made, so I will be able to use the DIY approach. :) > I must confess that I peeked at the new commits while I was searching > the commit I had to halt the dropping, so I already know that repacking > is not needed anymore, but for me the mystery about the release 0.10.4 > remains and I'm eager to learn about it... if you have the time to > explain. :) I am happy to elaborate more. Let me guess: What is still a mystery to you is PKG-INFO file in older releases? Seems I only _after_ last release corrected the watch file to fetch from true source at Github. If I guessed wrong and it was something else, then please just ask. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ * Sponsorship: https://ko-fi.com/drjones [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Re: Updating khal to fix RC bug #1023341
Quoting Jonas Smedegaard (2022-12-16 15:10:43) > Hi Daniele, and others, > > Quoting Daniele Tricoli (2022-12-16 07:16:24) > > I tried to update khal to block the autoremoval from testing (due > > #1023341) but it's not clear to me how to import metadata used to parse > > the package version with uscan¹ during repack of the tarball. > > > > PKG-INFO and the egg.info directory are on salsa¹ upstream branch but > > I'm not able to see them in the upstream tarballs (I looked also the > > commit on salsa with hash ba53a6bfb845ab4df3d5298f91f323b070084f4b): > > also PKG-INFO in the root of the repository is a news to me. > > > > How can I put them in the repacked tarball? In d/watch is indicated that > > for update the classic uscan invocation (through gbp) is used. > > > > The only way I can think of is to manually repack (AFAIK uscan doesn't > > support adding files before the invocation of mk-origtargz)... but it > > not seems that this was the procedure used according documentation on > > d/watch. > > > > AFAIU this mechanism was introduced to fix #1002406.³ > > > > Jonas do you have the time to explain? > > I will have a closer look now, then get back to you. > > Ususally when I "look" at a package I routinely update it as well. > Would you prefer that I roll back whatever changes I do during my > "looking at it" and guide you to gain same understanding as me? > Because if your interest is simply to get khal updated then > simpler for me is do (hopefully) all myself and only tell you without > leaving room for you to redo and potentially learn more from that DIY > experience. I am happy to do that slower process - I find it fun to > collaborate (am just not very used to it), so please do tell if you are > eager to learn. :-) As you might have noticed by now, I took the liberty of releasing my changes when I understood what was going on - because by then I had a functioning package ready for upload. It was multiple layers of cause for confusion: First layer: Upstream uses setuptools-scm to resolve release version, which is bad because it makes assumptions about things outside of the project - specifically it interacts with VCS (meta)data and assumed that is not replaced by that of another distro by the time the project is built. So our packaging patches away the use of setuptools-scm. Second layer: Our replacement involved grep'ing for upstream release version from file PKG-INFO which, as you correctly point out, is missing from upstream tarball. It was however included in previous upstream tarball, so this is an upstream change. So our replacement needed to be adjusted (to now instead grep CHANGELOG). Third layer: Debian build routines call clean target regardless if patches are applied or unapplied. Our patch affects dh_auto_clean so our replacement is extended with checking if patch is applied and skipping dh_auto_clean when it isn't. This makes it appear as if our "clean" target succeeds easily leading to the wrong assumption (at least for me) that it must be something upstream that fails - something mysteriously looking for a missing PKG-INFO file... Hope that was understandable. I have now updated our replacement routines plus a range of other householding changes, and released the new packaging release. Thanks a lot for bringing it to my attention. In fact I had old work lying around locally from July 30th that had stalled at that exact same failure, so I myself was evidently baffled as well (and then got distracted by something else), despite my having introduced the patch myself. ...so I have now also sprinkled a few comments in debian/rules file, to aid future baffld Debian maintainers. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ * Sponsorship: https://ko-fi.com/drjones [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Re: Updating khal to fix RC bug #1023341
Hi Daniele, and others, Quoting Daniele Tricoli (2022-12-16 07:16:24) > I tried to update khal to block the autoremoval from testing (due > #1023341) but it's not clear to me how to import metadata used to parse > the package version with uscan¹ during repack of the tarball. > > PKG-INFO and the egg.info directory are on salsa¹ upstream branch but > I'm not able to see them in the upstream tarballs (I looked also the > commit on salsa with hash ba53a6bfb845ab4df3d5298f91f323b070084f4b): > also PKG-INFO in the root of the repository is a news to me. > > How can I put them in the repacked tarball? In d/watch is indicated that > for update the classic uscan invocation (through gbp) is used. > > The only way I can think of is to manually repack (AFAIK uscan doesn't > support adding files before the invocation of mk-origtargz)... but it > not seems that this was the procedure used according documentation on > d/watch. > > AFAIU this mechanism was introduced to fix #1002406.³ > > Jonas do you have the time to explain? I will have a closer look now, then get back to you. Ususally when I "look" at a package I routinely update it as well. Would you prefer that I roll back whatever changes I do during my "looking at it" and guide you to gain same understanding as me? Because if your interest is simply to get khal updated then simpler for me is do (hopefully) all myself and only tell you without leaving room for you to redo and potentially learn more from that DIY experience. I am happy to do that slower process - I find it fun to collaborate (am just not very used to it), so please do tell if you are eager to learn. :-) > P.S. Jonas I don't know if you are subscribed to this list, so I'm > adding you to CC. Thanks, I am indeed not subscribed to the list, so please keep me cc'd in this thread. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ * Sponsorship: https://ko-fi.com/drjones [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Re: Move python-pytest-asyncio to debian-python-team shared repository?
Hi Julian and other Pythonistas, Quoting Julian Gilbey (2022-05-27 00:44:22) > Currently python-pytest-asyncio is maintained just by you. I wonder > whether you would be willing to move this to the Debian Python Team's > shared repository on salsa and transfer the maintainership to the > team, with you as primary uploader? I would prefer to let go: Feel free to adopt pytest-asyncio and python-mock. Kind regards, - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Re: rdflib: FTBFS: dh_auto_test: error: pybuild --test --test-nose -i python{version} -p "3.10 3.9" returned exit code 13
Quoting Andreas Tille (2022-02-24 11:06:58) > Control: tags -1 confirmed > Control: tags -1 help > > Hi Jonas, > > > Please consider releasing rdflib v6 which in my brief testing is > > compatible with pyparser v3. > > I tried to follow your suggestion to upgrade rdflib to version 6 in Git. > Unfortunately I'm stumbling upon a different issue in the new test > suite[1]. I recommend to discuss upgrade to v6 at bug#995675 instead of here. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
request to join python team
Hi, I would like to join the Debian Python team, to help maintain the khal package. My Salsa login is js. I have read https://salsa.debian.org/python-team/tools/python-modules/blob/master/policy.rst and accept it. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Re: [Pkg-javascript-devel] Jupyter project packaging effort
Hi Julien, Great that you are improving some packages. I have a hard time understanding what you are trying to say in your post below, however... Quoting Julien Puydt (2020-10-18 09:55:27) [ long rant about how proper packaging is hard and may fail ] > Help is welcome, Did I understand your message correctly, or did I miss something? - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Re: [Pkg-javascript-devel] npm2deb in debian
Quoting Jérémy Lal (2014-05-03 16:55:35) Le samedi 03 mai 2014 à 15:55 +0200, Leo Iannacone a écrit : Hello there, I'm looking for a sponsor for npm2deb: http://anonscm.debian.org/gitweb/?p=pkg-javascript/npm2deb.git some python developer around? Note that i'm all right with reviewing and uploading it, but it'd be very nice if a debian-python developer had a look at the python packaging part. Jérémy. (Please keep discussion into pkg-javascript-devel or cc to it) If acceptable to use CDBS, I can review and help maintain the packaging. - Jonas -- * Jonas Smedegaard - idealist Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Re: [Pkg-icecast-devel] what package name to decide
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sun, 22 Jan 2006 00:18:57 +0100 Rakotomandimby Mihamina [EMAIL PROTECTED] wrote: I want to Debian package the little shout-python software: http://icecast.org/download.php (in the midle of the page) The upstream tarball is: http://downloads.us.xiph.org/releases/libshout/shout-python-0.2.tar.gz What name should I give to it? - libhsout-python ? - python-shout ? - shout-python ? Even though the software is promoted as shout-python, the actual Python module seems to be named just shout, so I believe the correct name is python-shout (and python2.3-shout, python2.4-shout and so on). But why do you ask this mailinglist? You are most welcome to join the group and have the package group-maintained, if that's what you want. I just must warn you if you are in the process of becoming an official Debian developer that your work as part of a group may require some convincing to be included in your application. I will back you up if interested. You could also consider having it group-maintained by the Alioth group pkg-xiph... Regards, - Jonas - -- * Jonas Smedegaard - idealist og Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ - Enden er nær: http://www.shibumi.org/eoti.htm -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFD0u8vn7DbMsAkQLgRAvYkAKCizciCj/rrLfhV7vECDld1JDjtqgCfXfJh nzjkGBlL7f6i4rX/HRmye9A= =sDlx -END PGP SIGNATURE-
