Re: review for pipenv/2022.10.12-1
Thanks for taking over! I totally lost interest in maintaining that package and kind of neglected it because of the vendoring and the package itself or rather its upstream. Anyways, I thought I've orphaned it long time ago (maybe I forgot to do that). So thank you for taking over, I'm sure a lot of users will be happy! Cheers, Bastian -- Dr. Bastian Venthur https://venthur.de Debian Developer venthur at debian org
Re: Asking for help Poetry
Hi Emmanuel, I find it amazing that you went through all the hassle of un-bundeling and actually packaging all the dependencies for poetry! Good job and thank you very much for your efforts! Bastian -- Dr. Bastian Venthur https://venthur.de Debian Developer venthur at debian org
Re: upstream python concerns, python3-full package for bullseye
On 12.02.21 01:11, Thomas Goirand wrote: I understand that upstream python guys probably think the way to consume python stuff is through venv, pip, and setuptools. I have a very different view on this, and probably I'm not alone. We (Debian people) indeed prefer if our user can enjoy a packaged versions of things if they are available (and that's not specific to Python). In such a packaged environment, venv and distutils are useless, as the distribution is taking care of all what these tools would do without apt or dpkg. I do prefer my system to *not* have venv support, for example. Being a Debian Developer myself, I have to disagree here. I *wish* I could just install everything via the Debian Packaging System, but the reality for most relevant Python packages is very different: packages are either outdated or do not exist in Debian -- heck, even PIP is outdated in a way that you actually have to `pip install -U pip` in order to use it properly due to the recent manylinux change. So at work, were we use Python, we basically use only Debian's minimal image and install a naked Python + pip. Then we upgrade pip to make it usable and then install every python package via pip. Cheers, Bastian -- Dr. Bastian Venthur https://venthur.de Debian Developer venthur at debian org
Re: Asking for help Poetry
Hi, I see some updates on the salsa repository, any chance we can get this package ready before the next freeze so we'll have it in the next stable release? Cheers, Bastian On 29.06.20 06:04, Scott Kitterman wrote: On June 29, 2020 3:08:53 AM UTC, Emmanuel Arias wrote: Hi, I'm working on poetry packaging, I created on salsa de repository [0]. Note that there are many packages that are not in Debian like cachy, cleo, etc. I RFS python-cachy [1] and now I'm working on cleo, which depends on clikit that is not on Debian (if I search correctly). Bastian Venthur note me that pienv, pip have vendors folder with the dependencies but looking on poetry that _vendor folder is empty. So, looking for I more experienced opinion, do you think that we would try convince to upstream to make available vendors on the release (if that is necessary) or we need to package all the missing dependencies? Definitely they should be packaged. At least for pip none of the vendored libs are used in Debian's package. Fortunately upstream supports use of system libs with only minor patching. Scott K -- Dr. Bastian Venthur http://venthur.de Debian Developer venthur at debian org
Re: [RFC] Dropping Python2 support for my package
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Am 12.01.19 um 16:49 schrieb Andrey Rahmatullin: > On Sat, Jan 12, 2019 at 04:39:44PM +0100, Bastian Venthur wrote: >>>> The question is: if I drop Python2 support, what happens with >>>> the package names? Should I simply provide the >>>> python3-debianbts and drop python-debianbts, or shall I >>>> attempt some kind of migration to make the python-debianbts >>>> the new default package name for Python3? >>> >>> just drop the python-debianbts binary, without doing any kind >>> of strange migration, and keep the name python-debianbts for >>> the python3 package, as the Debian Python Policy states. >> >> I think there's an error in your advice and I can't figure out >> what you mean. You're suggesting to drop *and* to keep the >> python-debianbts package :) Can you please clarify? > Drop binary python-debianbts package, keep the source package name > as python-debianbts. > > Or were you asking about shipping the py3 module inside the > python-debianbts binary package? We don't do that. > > Thanks! - -- Dr. Bastian Venthur https://venthur.de Debian Developer venthur at debian org -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEh5WvLkoaTvugaKRJjoiVRNmFAA0FAlw6DhQACgkQjoiVRNmF AA07yRAAyHk8QZgk/GcDmINyrz1JfA9LyNFJCtBWzNxA9h8heZDQ0+YjJo5Nv9u6 9GNmq4OujP9yBEI7zTqROnI95sLJfSAQSOP2u+EWEji5e6gS7C/bQedhOIfjpX6O x9TMyI6wRfX0yN1A/sT8C/iA0Wku8afyEV81cNA5aLmZx2EKo+hpPaV4nkYaVFbH O/GBcrsqAxP591XsBFo5MhRS4mvCdBL5hM2pLCf8cdBAWjO/yYOPAFJuW+P7Q6Wu J700Dh8WDQQb/t/eudOiOihORwfBJPrgtiF+IH2zXIn6kLGNmqNNZEw6n9bnn/m4 srNYFY9oTaXjdYVzTCB1cRVhXMva2jxR7WKCYaWRDLsyK+EfZhATE9iRRO0S7waG y1BgKpCY4SkCGgH5vYIr20FpvYNUptYmQh/ZCDbl1guDfS0Lzy1h0ZDasOjbCt2L hl6Yqidphh1LdryZoOfrSCex5sj8mBOnpfeVxZyHQMpoULvSnx/+F/2wASIbWxTR 551rY6gy2B5rm2YGk1rGaN/OF44jhx8K8NoFB6uCsteOlFuR9Ll8wEFLIPqL8GSE 5EMgmuoNnMpFfhV8EIeASWfKbVor8RQwLcdoYYDuq9vXaMQ3loRflla5Y0+CVKtl SLWtx79FN/mfxaA2AMU3QxmgKJMkQXyKZ8fu+lHwQYFjMzJ7ix4= =xxSc -END PGP SIGNATURE-
Re: [RFC] Dropping Python2 support for my package
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Am 12.01.19 um 16:32 schrieb Mattia Rizzolo: > On Sat, Jan 12, 2019 at 04:28:26PM +0100, Bastian Venthur wrote: >> The question is: if I drop Python2 support, what happens with the >> package names? Should I simply provide the python3-debianbts and >> drop python-debianbts, or shall I attempt some kind of migration >> to make the python-debianbts the new default package name for >> Python3? > > just drop the python-debianbts binary, without doing any kind of > strange migration, and keep the name python-debianbts for the > python3 package, as the Debian Python Policy states. I think there's an error in your advice and I can't figure out what you mean. You're suggesting to drop *and* to keep the python-debianbts package :) Can you please clarify? Thanks! - -- Dr. Bastian Venthur https://venthur.de Debian Developer venthur at debian org -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEh5WvLkoaTvugaKRJjoiVRNmFAA0FAlw6CjQACgkQjoiVRNmF AA3TNA//eKN0UMeJ6iQDwwVs6cH/s+j3qcx4AfXCAaDuOrY3++BDZk03jKRlCu7a 357Tq1k0MOlAJ0w6sT4xqp4+4/9/Hf/nS2TnB0y4fvE/mLfkJiwMMCVh1eS6Hwu2 L0qiMf65aHOV3Jr5roWfVU35dXBE5PoTPJGP5ZgKVRQ/kJeD58oNORu70SnMhHyu a2qbyDVtc64mhq7uq8beylPd4H9lLRfras95EwKH+U9SAF8a9hh1H7a+Lxpb91mx 8ZarUQziSX2xMiOCtGPi2RDEJBdC4mVIfizQD536Aznp7OerRzkKwpW2aSLOJU2X rBlm96mGH79ekvt+pQbh+1PqsnA5feb96bWVq4CwCFCrhCcz7C1rFy4aN3LFNoIx vBGdpwRKdY6CColddqY2Yj73IebF9gMNrOybM69Q0xDvEOQVGTWP29yuKUdOQoKp FslNIATxITml4HpTBmI0Mh8wDMoNq7q47d0XzmmGvESbN+7gqR9XCBqvaBb7EALG XDNPBo55Zflgh82GpRbKcSV888pESTsYviZrtlpMFHIDH9kztaThTFX0eygZUPik 5Se+yKBpdB5BChVQznhemFTcKZcmvar1Eb1Hn9wKLUFZTlHs9Ecxu8uK5kAXN6Eq EGKJBSsto/RrmLC46WQaDbEDylzPRSAVBnkcAP+se0lTqTzulgA= =w1LF -END PGP SIGNATURE-
[RFC] Dropping Python2 support for my package
Hi, I'm about to drop Python2 support for python-debianbts. Currenty the source package produces two packages: python-debianbts and python3-debianbts. The question is: if I drop Python2 support, what happens with the package names? Should I simply provide the python3-debianbts and drop python-debianbts, or shall I attempt some kind of migration to make the python-debianbts the new default package name for Python3? Thanks for your hints! Bastian -- Dr. Bastian Venthur https://venthur.de Debian Developer venthur at debian org
Re: Safest way to set python3 as default for `python`
Hi Matthias, thanks for the reply and the explanation. Cheers, Bastian
Safest way to set python3 as default for `python`
Hi, sorry if this question has been asked before. What is the currently recommended way to make `python` point to `python3`? I'd like to have it set on a system default level if possible. Cheers, Bastian -- Dr. Bastian Venthur http://venthur.de Debian Developer venthur at debian org
Request to join the DMPT, PAPT and Salsa Groups
Hi, I'd like to join the Python applications and Python modules teams. I'm a Python user myself and would like to help maintaining a healthy Python ecosystem within Debian. I've read the team policy and accept it. My salsa account is `venthur`. Cheers, Bastian -- Dr. Bastian Venthur http://venthur.de Debian Developer venthur at debian org
Interest in packaging python-dotenv?
Dear Python-modules team, is anyone interested (or already working on) packaging python-dotenv? From all *dotenv packages it is currently the most famous one for python. It allows for using .env files in python and provides a command line tool: https://github.com/theskumar/python-dotenv Cheers, Bastian
Re: Kivy packages at Debian
Hi Thomas, thank you very much for your effort to keep the Debian and Ubuntu packages in sync. I handed the kivy package over to the DPMT team (CC). Cheers, Bastian Am 25.01.2015 um 15:24 schrieb Thomas Pietrowski: > Hello, > > my name is Thomas-Karl Pietrowski. I'm working for the kivy project on > the Ubuntu packages. I found many differences between on my and your > packages, which now are also landing in Ubuntu. > If you are interested you can take a look at the latest debian/* files > at https://github.com/kivy/kivy/tree/pkg-debian-daily . > > Regards > -- Bastian Venthur http://venthur.de Debian Developer venthur at debian org -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/54c607ee.6040...@debian.org
Re: Could you take over my package Kivy?
Hi Vincent, sorry for not replying to your mail. It was sitting in my inbox for ages and I was too busy to decide what to do with it until I eventually forgot about it. Anyways, thank you very much for taking care of the package! Bastian Am 10.11.2014 um 10:33 schrieb Vincent Cheng: > Hi Bastian, > > On Sun, Nov 9, 2014 at 8:30 AM, Bastian Venthur wrote: > >> Dear Python team, >> >> I'm currently unable to maintain the kivy package properly, as I am >> busy writing my Ph.D. Could I kindly ask you to take over this package? > > I'd be glad to take the role as an uploader for kivy and maintain it > under the DPMT's umbrella. In fact I had suggested this a while ago in > #737351, but you never replied, so I just assumed that you weren't > interested in team maintenance at all. Glad to see that I was > mistaken! > > Regards, > Vincent > > -- Bastian Venthur http://venthur.de Debian Developer venthur at debian org -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/m3q12t$u57$1...@ger.gmane.org
Could you take over my package Kivy?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dear Python team, I'm currently unable to maintain the kivy package properly, as I am busy writing my Ph.D. Could I kindly ask you to take over this package? https://packages.qa.debian.org/k/kivy.html Cheers, Bastian - -- Bastian Venthur http://venthur.de Debian Developer venthur at debian org -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBAgAGBQJUX5aSAAoJEI6IlUTZhQANm6cQAJqUW8pzqcIA3fY6znhRdZK2 7qJupFro4167v5lVghfHHUmek8vI167ZFnqgnv8YPRhpVGDFJvZs8roLv263hJjl KgIAXiytCeP3GyzhaxWNTiQG9l5CmmCfitVZ1VZllXpXoD6O3sMK1VYnRn5oWhuf N2zzs03vQlBT2qwy+VYxj7RuMcQNdrqVMWmGMOO0A0Ma+XkLYq9i3uTkv2v7Exwd y4F86op4t18VKqQgebFLK2NiyjOgIIqdXuPrkG7C3RCG2eu2VpSfwrvAzVA96KNh tj+u0TY3Hm1UMR4uDDqok9WXwds5nXf0qjPUDeQF533C9Do7xTv2Y+m2uSHCRX8Z nIv6njU1CfrVhmsF3lngXRjVxY5n4+qLcOe/Gxqv/Sszyh639DcrLSOuspEau5yM f97M86FfVzSG12SamqlFt+xRWLlRD6HesDtHf1ZfDtSWOzQaQRXfS15ArP6snIbB gchMqCt1hUdRMScv2y3sd6g7DMVYSeXAl00Gwf8mfK51XrwhgGrLaFAxW3Lepb1E RuJdmcVFkoqmMM9q9wrC2O4Vj4gqQN/bDu09Tg6ijm0+fGuL3efz0q0nKjWa3qXA NrP3x4pe7odgixvDWqdJM/dNm08l2YSFtiGo6IriSeqRDm/dXUZppFnE0CFCrCng WDzqY9LZaT6fY+XII5Ta =Dhx3 -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/m3o4qj$v5m$1...@ger.gmane.org
Re: No minutes from Debconf Python BoF?
Am 14.08.2010 15:34, schrieb Guy Hulbert: > On Sat, 2010-14-08 at 15:14 +0200, Bastian Venthur wrote: >> The minutes are currently polished by the participants of the BoF and >> will be published afterwards. > > Why do minutes need to be "polished" ... ? Maybe polished isn't the correct term. What I meant was: reviewed by all attendees to check if everyone agrees with what's in that document (i.e. what has been discussed during the BoF). Cheers, Bastian -- Bastian Venthur http://venthur.de Debian Developer venthur at debian org -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/i466eo$vv...@dough.gmane.org
Re: No minutes from Debconf Python BoF?
Hi, The minutes are currently polished by the participants of the BoF and will be published afterwards. Cheers, Bastian Am 14.08.2010 09:09, schrieb Sandro Tosi: > Hello, > there was a BoF[1] about the plans for python in squeeze+1 but no > minutes was sent to the list: 8 days are passed, so we have waited > (while others, like perl team, sent it moments after the bof). > > [1] http://penta.debconf.org/dc10_schedule/events/696.en.html > > I think it's important to have such notes sent to the public and be > discussed openly, and not reduced to the audience of a room in a > conference not everyone could attend. > > Regards, -- Bastian Venthur http://venthur.de Debian Developer venthur at debian org -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/i464qv$q8...@dough.gmane.org
Re: Bug#543689: please upload python2.6 to unstable
On 12.01.2010 03:08, Mr. Foobarra wrote: > (CC'd, since it is not obvious to the casual bystander if Matthias > reads bug reports or mailing lists) > > Dear Mr. Klose, > > I have grown woefully tired of watching respected developers ask > nicely, tiptoe around, get angry, ask again after waiting a few > weeks, and continue to make every attempt to give you every benefit > of the doubt. This upload is way overdue and was requested formally > in the BTS August 26, 2009 - with no response from you. The information is there, it is unfortunately just well hidden: http://lists.debian.org/debian-release/2009/12/msg00207.html Cheers, Bastian -- Bastian Venthur http://venthur.de Debian Developer venthur at debian org -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Final updates for this Python Policy revision
Omer Zak schrieb: > On Sat, 2009-12-12 at 14:27 +0100, Bastian Venthur wrote: >> Ben Finney schrieb: >>> anatoly techtonik writes: >>> >>>> The policy is under GPL license which is kind of ridiculous to prevent >>>> citing Debian Policy in private talks. >>> Why is it ridiculous? Is it any more ridiculous to put a policy document >>> under GPL than any other document? >> Quoting the second paragraph from the copyright notice: >> >> "This manual is free software; you can redistribute it..." >> >> so this *manual* is free *software*. Really?! >> >> For me this wording shows clearly that this license does not fit to >> documentation since it was obviously made for software. > > The policy prescribes procedures to be followed by people who package > Python packages for Debian, isn't it so? > Couldn't we then consider it to be software, to be executed by the > people who perform the packaging (to be considered as hardware, for this > purpose alone)? I wouldn't go so far and see documentation as software. Apart from that I agree that it is important to clarify what one can do with this documentation (quote, modify, redistribute, etc.) and under which rules this has to happen. For example, when I quote a paragraph of the documentation in an email, do I have to provide a copy of the GPL along with the quote? Because technically I redistribute parts of that work. Cheers, Bastian -- Bastian Venthur http://venthur.de Debian Developer venthur at debian org -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Final updates for this Python Policy revision
Ben Finney schrieb: > anatoly techtonik writes: > >> The policy is under GPL license which is kind of ridiculous to prevent >> citing Debian Policy in private talks. > > Why is it ridiculous? Is it any more ridiculous to put a policy document > under GPL than any other document? Quoting the second paragraph from the copyright notice: "This manual is free software; you can redistribute it..." so this *manual* is free *software*. Really?! For me this wording shows clearly that this license does not fit to documentation since it was obviously made for software. Cheers, Bastian -- Bastian Venthur http://venthur.de Debian Developer venthur at debian org -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Bug#496544: RFS: reportbug-ng (closes RC #496544)
Hi all, haven't looked at the bugreport yet, since I was on vacation the last two weeks and returned just yesterday evening. But since the release team decided that rng is 'unfit for release' and blocked rng, it won't enter testing even if you NMU the bug. Cheers, Bastian Serafeim Zanikolas schrieb: > Dear all, > > I need sponsorship for a NMU that closes RC bug #496544 of the native package > reportbug-ng. Do I have to ask for a release freeze, or would that be the > sponsor? > > This NMU fixes the breakage of bug-triage (#496536; potentially other as > well). > > I attach the patch with the changes (all of which are required for fixing the > RC bug). > > http://www.cs.man.ac.uk/~zanikols/deb/reportbug-ng_1.1+nmu1.dsc > > Cheers, > Serafeim > > -- Bastian Venthur http://venthur.de Debian Developer venthur at debian org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
