Bug#1069248: RFS: ruby-mdl/0.13.0-5 -- Markdown lint tool - transitional dummy package
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "ruby-mdl": * Package name : ruby-mdl Version : 0.13.0-5 Upstream contact : ["p...@ipom.com"] * URL : https://github.com/markdownlint/markdownlint * License : MIT * Vcs : https://salsa.debian.org/nbehrnd/ruby-mdl Section : text The source builds the following binary packages: markdownlint - Markdown lint tool ruby-mdl - Markdown lint tool - transitional dummy package To access further information about this package, please visit the following URL: https://mentors.debian.net/package/ruby-mdl/ Alternatively, you can download the package with 'dget' using this command: dget -x https://mentors.debian.net/debian/pool/main/r/ruby-mdl/ruby-mdl_0.13.0-5.dsc Changes since the last upload: ruby-mdl (0.13.0-5) unstable; urgency=medium . * increment to new Debian Policy 4.7.0 Regards,
Re: Looking for sponsor with update for Debian package
@Loren As an sponsored maintainer and hence subscriber to this mailing list, I think a subject line with a specific ticket number, package name and -- in the particular case -- the acronym RFS would ease to follow up the progress of your work. Ideally it were the template reaching level 4 / Find a sponsor[1] offers. Inferring from your message filed by Sun, 21 Jan 2024 02:29:20 -0800 your work relates to rpm[2] with its RFA[3] (and hence, an existing ticket) I fetched a fork by ``` git clone http://www.north-winds.org/git/rpm.git ``` File `/debian/changelog` for your new version 4.18.2+dfsg-1 does not explicitly mention to close (including the corresponding ticket numbers, and a `closes: #NNN`) one of the bugs currently (15:10 UTC +1) listed on https://bugs.debian.org/cgi-bin/pkgreport.cgi?repeatmerged=no=rpm. If your work addressed them, may you amend accordingly the changelog file? Are you member of the pkg-rpm-team? If not, and if the package now were maintained by you, a successful upload to Debian likely might require an update of debian/control, in lines of `Vcs-Browser:` and `Vcs-Git:`. Best regards, Norwid [1] https://mentors.debian.net/intro-maintainers/ [2] https://tracker.debian.org/pkg/rpm [3] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923352
Bug#1056362: RFS: ruby-mdl/0.13.0-4 -- Markdown lint tool - transitional dummy package
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "ruby-mdl": * Package name : ruby-mdl Version : 0.13.0-4 Upstream contact : ["p...@ipom.com"] * URL : https://github.com/markdownlint/markdownlint * License : MIT * Vcs : https://salsa.debian.org/nbehrnd/ruby-mdl Section : text The source builds the following binary packages: markdownlint - Markdown lint tool ruby-mdl - Markdown lint tool - transitional dummy package To access further information about this package, please visit the following URL: https://mentors.debian.net/package/ruby-mdl/ Alternatively, you can download the package with 'dget' using this command: dget -x https://mentors.debian.net/debian/pool/main/r/ruby-mdl/ruby-mdl_0.13.0-4.dsc Changes since the last upload: ruby-mdl (0.13.0-4) unstable; urgency=medium . * lint control file * improve manpage by provision of examples of application Regards,
Bug#1055886: RFS: ruby-mdl/0.13.0-3 -- Markdown lint tool - transitional dummy package
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "ruby-mdl": * Package name : ruby-mdl Version : 0.13.0-3 Upstream contact : ["p...@ipom.com"] * URL : https://github.com/markdownlint/markdownlint * License : MIT * Vcs : https://salsa.debian.org/nbehrnd/ruby-mdl Section : text The source builds the following binary packages: markdownlint - Markdown lint tool ruby-mdl - Markdown lint tool - transitional dummy package To access further information about this package, please visit the following URL: https://mentors.debian.net/package/ruby-mdl/ Alternatively, you can download the package with 'dget' using this command: dget -x https://mentors.debian.net/debian/pool/main/r/ruby-mdl/ruby-mdl_0.13.0-3.dsc Changes since the last upload: ruby-mdl (0.13.0-3) unstable; urgency=medium . * address manpage problem - capitalize TH entry in manpage - provide manpages for ruby-mdl and mdl - add suggest to update mandb after removal of ruby-mdl Regards,
Bug#1055430: RFS: ruby-mdl/0.13.0-2 -- Markdown lint tool - transitional dummy package
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "ruby-mdl": * Package name : ruby-mdl Version : 0.13.0-2 Upstream contact : ["p...@ipom.com"] * URL : https://github.com/markdownlint/markdownlint * License : MIT * Vcs : https://salsa.debian.org/nbehrnd/ruby-mdl Section : text The source builds the following binary packages: markdownlint - Markdown lint tool ruby-mdl - Markdown lint tool - transitional dummy package To access further information about this package, please visit the following URL: https://mentors.debian.net/package/ruby-mdl/ Alternatively, you can download the package with 'dget' using this command: dget -x https://mentors.debian.net/debian/pool/main/r/ruby-mdl/ruby-mdl_0.13.0-2.dsc Changes since the last upload: ruby-mdl (0.13.0-2) unstable; urgency=medium . * Source only upload for migration to testing Regards,
Bug#1053575: RFS: ruby-mdl/0.13.0-1 -- Markdown lint tool
On Sat, 4 Nov 2023 19:02:02 +0100 Tobias Frost wrote: > Am Wed, Nov 01, 2023 at 11:55:29PM +0100 schrieb Norwid Behrnd: > > Your transitional package needs to Depends: on the new package. > Thank you for spotting my omission. The current upload to https://mentors.debian.net/package/ruby-mdl/#upload-5 by time stamp 2023-11-05 13:24 now equally mentions `markdownlint` as dependency for the transitional dummy package `ruby-mdl`.
Re: Bug#1053575: RFS: ruby-mdl/0.13.0-4 -- Markdown lint tool
> What is wrong with just adding mdl as a new binary package in the existing > source package? By the conventions of the Ruby team,[1] the name `ruby-mdl` conveys the idea the binary provides only a library. For them, the binary however provides an application conventionally named without the prefix `ruby-`; hence their recommendation to rename both the binary as well as files in the pristine-tar branch.[2] Was the collection of mdl "as new" into a separate folder and eventual pristine git repository (without the trouble of ruby-mdl history) an error on my side? I thought the simultaneous presence of some files "ruby-mdl*.*" and of files "mdl*.*" (and perhaps some not yet correctly renamed ones) confusing and hence opted-in for what appeared to me to be a clean cut. [1] https://wiki.debian.org/Teams/Ruby/Packaging/Conventions [2] Antonio Terceiro, October 07, 2023
Re: Bug#1053575: RFS: ruby-mdl/0.13.0-4 -- Markdown lint tool
On Mon, 23 Oct 2023 10:34:22 +0200 Bastian Germann wrote: > So, where is that mdl package that ruby-mdl depends on with the new version? Following an advice by Antonio Terceiro,[1] the intention is dummy / transition package ruby-mdl https://mentors.debian.net/package/ruby-mdl/ https://mentors.debian.net/debian/pool/main/r/ruby-mdl/ruby-mdl_0.12.0-4.dsc relays to the new, functionally updated mdl https://mentors.debian.net/package/mdl/ https://mentors.debian.net/debian/pool/main/m/mdl/mdl_0.13.0-1.dsc Regards, Norwid [1] root of the discussion: https://lists.debian.org/debian-ruby/2023/10/msg2.html
Bug#1054258: RFS: mdl/0.13.0-1 -- Markdown lint tool
Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package "mdl": * Package name : mdl Version : 0.13.0-1 Upstream contact : ["p...@ipom.com"] * URL : https://github.com/markdownlint/markdownlint * License : MIT * Vcs : https://salsa.debian.org/nbehrnd/mdl Section : text The source builds the following binary packages: mdl - Markdown lint tool To access further information about this package, please visit the following URL: https://mentors.debian.net/package/mdl/ Alternatively, you can download the package with 'dget' using this command: dget -x https://mentors.debian.net/debian/pool/main/m/mdl/mdl_0.13.0-1.dsc Changes for the initial release: mdl (0.13.0-1) unstable; urgency=medium . * rename package (formerly `ruby-mdl`, now `mdl`) because it is an application * New upstream version 0.13.0, i.e. * added Sarif output * fixed rules MD007, MD027 * changed rules MD009, MD033 * new rules MD055, MD056, MD057 Regards,
Bug#1053575: RFS: ruby-mdl/0.13.0-1 -- Markdown lint tool
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "ruby-mdl": * Package name : ruby-mdl Version : 0.13.0-1 Upstream contact : ["p...@ipom.com"] * URL : https://github.com/markdownlint/markdownlint * License : MIT * Vcs : https://salsa.debian.org/nbehrnd/ruby-mdl Section : text The source builds the following binary packages: ruby-mdl - Markdown lint tool To access further information about this package, please visit the following URL: https://mentors.debian.net/package/ruby-mdl/ Alternatively, you can download the package with 'dget' using this command: dget -x https://mentors.debian.net/debian/pool/main/r/ruby-mdl/ruby-mdl_0.13.0-1.dsc Changes since the last upload: ruby-mdl (0.13.0-1) unstable; urgency=medium . * New upstream version 0.13.0, i.e. * added SARIF output * fixed rules MD007, MD027 * changed rules MD009, MD033 * new rules MD055, MD056, MD057 Regards,
Re: Bug#1030265: RFS: ruby-mdl/0.12.0-3 -- Markdown lint tool
> Oif, the man page itself shouldn't be renamed. As the executable in $PATH > is "mdl", the man page should be named so. There was the attempt to resolve the name issue by renaming the package. Given the freeze a couple of days ahead, the suggest received however was to defer this *for now*,[1] or to risk that the package won't be considered to enter stable. Thus this, and a few other things (e.g., still the «failed to analyze the VCS repository» is seen, share of the maintainership with the Ruby Team) remain on my todo, though they better are addressed for the time after Q2/Q3 of 2023, provided `bookworm` was released. Thank you for your sponsorship. [1] https://lists.debian.org/debian-ruby/2023/01/msg00058.html
Re: Bug#1029186: reply: RFS: libcommons-validator-java/1:1.7-1 [Team] -- ease and speed development and maintenance of validation rules
Postscript: If you already edit `debian/changelog` (`UNRELEASED` -> `unstable`), the trailing spaces in this file equally can be removed in the same session, too.
Re: Bug#1029186: reply: RFS: libcommons-validator-java/1:1.7-1 [Team] -- ease and speed development and maintenance of validation rules
Hello Min Sun, is there a particular reason why you opt for / stick to distribution `UNRELEASED` for a package already monitored by the tracker?[1] It is the entry e.g., `dch -i` puts into file `/debian/changelog` when you start to work on a new version (increment) of a package. After all other other work on your side is done, an eventual change to the string `unstable` (then lower case only) is one of the keys necessary to let results of your work enter branch `unstable`, and later `testing`, etc. Regards, Norwid [1] https://tracker.debian.org/pkg/libcommons-validator-java
Re: Bug#1030307: RFS: posixsignalmanager/0.3-2 -- posix signal handling for qt
> So long for a library, change the name. It might be better to rename the package after bookworm became stable. My intent is to rename `ruby-mdl` into `markdownlint`; like `posixsignalmanager`, it is a package accepted into `testing` a couple of days ago. The recommendation I received was to stick with the odd name *for now*, and to defer attempts to rename the package, or else face the possibility that neither one form (i.e., old name, or new name) would ship.[1] Because the soft-freeze of `bookworm` merely is a few days ahead (February 12).[2] With these options ahead, I choose to stick (for now) with the name already introduced. It might be the safer choice for Christoph, too. Regards, Norwid [1] https://lists.debian.org/debian-ruby/2023/01/msg00058.html [2] https://release.debian.org/testing/freeze_policy.html
Bug#1030265: RFS: ruby-mdl/0.12.0-3 -- Markdown lint tool
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "ruby-mdl": * Package name : ruby-mdl Version : 0.12.0-3 Upstream contact : ["p...@ipom.com"] * URL : https://github.com/markdownlint/markdownlint * License : MIT * Vcs : https://salsa.debian.org/nbehrnd/ruby-mdl Section : text The source builds the following binary packages: ruby-mdl - Markdown lint tool To access further information about this package, please visit the following URL: https://mentors.debian.net/package/ruby-mdl/ Alternatively, you can download the package with 'dget' using this command: dget -x https://mentors.debian.net/debian/pool/main/r/ruby-mdl/ruby-mdl_0.12.0-3.dsc Changes since the last upload: ruby-mdl (0.12.0-3) unstable; urgency=medium . * correct maintainership and address * correct upstream/metadata, addresses * provide two scripts to collect contributor list debian/copyright * use consistently ruby-mdl in/by man page to refer to the package * move package from section ruby to section text Regards, Norwid
RFH about/towards ruby-mdl 0.12.0-3
Hello, when packaging `markdownlint`[0] -- an application implemented in Ruby -- I committed some errors. After provision of the source-only upload, and its eventual transition as `ruby-mdl` into `testing`, it was time to improve this package for a new upload,[1] "Upload #1" (uploaded by 2023-01-28 17:03). However, this still is problematic; as an application, the package were better named `markdownlint`, than `ruby-mdl`. By now, I equally grasp why `lintian` equally recommends an improvement here. Ideally, I would like to rename the package name with the same upload as accounting for internal changes (debian/control, debian/upstream/metadata, etc) while retaining the package in Debian testing, including its lineage; but so far fail. * From askubuntu[2] I inferred it would suffice to replace the entry `ruby-mdl` for `Package` in /debian/control by `markdownlint`. With the changes of "upload #1" plus the new entry `markdownlint` in /debian/control, the run with `dpkg-buildpackage` fails. * On https://wiki.debian.org/RenamingPackages, Debian Wiki (last modified 2020-04-04 16:06:11) describes with "Transition package method" one could write a dummy package. Can one of you please indicate to a more verbose example than the one then on display? Based on a read of the man pages about `dpkg-name` I was not able to change to run ``` dpkg-name ruby-mdl_0.12.0-3_all.deb ``` with an altered control file to obtain `markdownlint-0.12.0-3_all.deb`. Is there an other assistant in `dpkg` (or elsewhere) to obtain the wanted adjustment? Or, do you recommend to file a RFS for `ruby-mdl-0.12.0-3` now, and to adjust the name in a subsequent version (then only about the package's name), perhaps after `bookworm` was released as `stable`? With regards, Norwid [0] https://github.com/markdownlint/markdownlint [1] https://mentors.debian.net/package/ruby-mdl/ [2] https://askubuntu.com/questions/437005/how-to-rename-deb-package
Bug#1029033: RFS: ruby-mdl/0.12.0-2 -- Markdown lint tool
Sorry, this was a misunderstanding on my side. In upload #3, with reference to the documentation, the adjustment of the changelog and provision of the new tag now are the only two intentional changes to the data.
Re: Bug#1029033: RFS: ruby-mdl/0.12.0-2 -- Markdown lint tool
On Sun, 22 Jan 2023 20:30:44 +0100 Bastian Germann wrote: > This is not a "Source only upload" as claimed by d/changelog. > The sequence of events here: 0) `dch -i` for an increment of the counter 1) change of the entry about maintainership in the /debian/control file 2) addition of two assistance scripts debian/git_report.sh and debian/simpler_list.py I assumed (by Daniel Leidert's email) as not required, though perceived as useful for later updates (only after `bookworm` is published as `stable`) 3) run `dpkg-buildpackage` followed by `linitian`. As anticipated, `lintian` now reports as a warning uploader and maintainer are the same; however, no report of an error. The newly build .deb installed well (by `sudo dpkg -i`) in an instance of Xubuntu 22.04 which is separate from the Linux Debian 12/bookworm used to prepare the package 4) back in Linux Debian 12/bookworm, `dpkg-buildpackage --changes-option=-S` on basis of "How to make a source-only upload" by https://wiki.debian.org/SourceOnlyUpload, 5) `git add .`, `git commit -m`, and `git push` to the repository on salsa 6) `debsign` signature of the new .changes file, and `dput mentors` to provide the mentors page with a new upload. After about 10 min and reception of the of "the upload was accepted" email, I filed for a RFS. Neither on Saturday, nor today does step 2) appear to me as an error. The same page reports ``` If you like debuild command, you can do: $ debuild -S ``` So far, I understood this instruction as "this is not necessary because the previously issued `dpkg-buildpackage --changes-option=-S` already prepares the source code". Regards, Norwid erroneous.
Re: Bug#1027919: RFS: dinit/0.16.0-1 -- [ITP] Service monitoring / "init" system
Hello Mobin, -- this is an off-list reply -- On Sun, 22 Jan 2023 13:30:24 +0330 Mobin wrote: > I send a new upload to mentors but seems like I do something "wrong". I > think Debian BTS have a retitle system for bugs. No? > though I can't be a sponsor for your package (no working knowledge of C++, .and. first time packager) I glanced over the files accessible with dget -x https://mentors.debian.net/debian/pool/main/d/dinit/dinit_0.16.0-1.dsc Because `dinit` is not yet in Debian, I suggest a change in the file `/debian/changelog` because this (not yet) links back to the bug tracking number which states your intent to package this program. To illustrate how this entry could look like, I attach a screen photo of your `changelog` file, and the one I use for my current RFS about `ruby-mdl`. A two, by yesterday I assume my upload #2 (for `ruby-mdl`) is better than the former one. This is why, after I received the email `ACCEPTED on mentors (unstable)`, I followed the link https://mentors.debian.net/sponsors/rfs-howto/ the email contains. The page has the string `Send the completed template below by email` which I double-clicked for using this message as prepared/as it showed up in my mail client. In my perspective, since your first upload (January 4th) and now, there was both considerable work (many less points addressed by `lintian` now) .and. three are about weeks, it is not too annoying for a gentle reminder. There still are a couple of days before the soft freeze for `bookworm` starts.[1] Regards, Norwid [1] https://release.debian.org/testing/freeze_policy.html 8>< attachment(s) 2023-01-22T11.33.03 -- screenshots dinit.png 2023-01-22T11.34.28 -- screenshots ruby-mdl.png 8><
Bug#1029361: RFS: ruby-mdl/0.12.0-2 -- Markdown lint tool
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "ruby-mdl": * Package name : ruby-mdl Version : 0.12.0-2 Upstream contact : ["p...@ipom.com"] * URL : https://github.com/markdownlint/markdownlint * License : MIT * Vcs : https://salsa.debian.org/nbehrnd/ruby-mdl Section : ruby The source builds the following binary packages: ruby-mdl - Markdown lint tool To access further information about this package, please visit the following URL: https://mentors.debian.net/package/ruby-mdl/ Alternatively, you can download the package with 'dget' using this command: dget -x https://mentors.debian.net/debian/pool/main/r/ruby-mdl/ruby-mdl_0.12.0-2.dsc Changes since the last upload: ruby-mdl (0.12.0-2) unstable; urgency=medium . * Source only upload for migration to testing Regards, Norwid Behrnd
Bug#1029033: RFS: ruby-mdl/0.12.0-2 -- Markdown lint tool
@Bastian The point you addressed has been forwarded to the subscribers of the Debian Ruby list. The root of the thread is https://lists.debian.org/debian-ruby/2023/01/msg00032.html Regards, Norwid
Bug#1029033: RFS: ruby-mdl/0.12.0-2 -- Markdown lint tool
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "ruby-mdl": * Package name : ruby-mdl Version : 0.12.0-2 Upstream contact : ["p...@ipom.com"] * URL : https://github.com/markdownlint/markdownlint * License : MIT * Vcs : https://salsa.debian.org/nbehrnd/ruby-mdl Section : ruby The source builds the following binary packages: ruby-mdl - Markdown lint tool To access further information about this package, please visit the following URL: https://mentors.debian.net/package/ruby-mdl/ Alternatively, you can download the package with 'dget' using this command: dget -x https://mentors.debian.net/debian/pool/main/r/ruby-mdl/ruby-mdl_0.12.0-2.dsc Changes since the last upload: ruby-mdl (0.12.0-2) unstable; urgency=medium . * Source only upload for migration to testing Regards, -- Norwid Behrnd
metadata entry "changelog"
Dear mentors, I would like to improve an existing Debian package. Based on the typical pattern and name convention of a project based on GitHub, entry `Changelog:` in file `debian/upstream/metadata` currently points to an address normally used to present individual releases. The anticipated pattern of the line then should be ``` Changelog: https://github.com/markdownlint/markdownlint/releases ``` Though not explicit about functionality added, or bugs corrected, the project currently maintains only a list version tags (vide supra). The address above does not contain the wanted information. ``` https://github.com/markdownlint/markdownlint/tags ``` My question to you: * Is there precedent of filling the line in `metadata` by ``` Changelog: https://github.com/markdownlint/markdownlint/tags ``` instead (maybe with `Tags` instead of `Changelog`), or * do you recommend to populate ``` http://github.com/markdownlint/markdownlint/releases ``` (post-hoc) to eventually close the gap to package the project for Debian? Regards, -- Norwid Behrnd
separat, Re: Bug#1028048: RFS: d11amp/0.61-1 -- Oldskool MP3 player
Sehr geehrter Herr Dettbarn, On Fri, 6 Jan 2023 10:44:57 +0100 Thomas Dettbarn wrote: > It would be AWESOME if you could add it to your ever growing collection of > packages. > Hopefully, it will evoke a sense of nostalgia in one user or the other. :) > zwar kann ich für `d11amp` nicht Sponsor sein -- erst gestern mit `ruby-mdl` / `markdownlint` bin ich erstmals von der mentor-Suchseite in die Warteschleife von https://ftp-master.debian.org/new.html vorgerückt -- aber `d11amp` war mir dennoch mit den zahlreichen package uploads auf https://mentors.debian.net/package/d11amp/ ein wertvolles Beispiel, wie die einzelnen Hilfsdateien «Debian-gerecht» vorzubereiten sind. Deshalb möchte ich mich bei Ihnen mit dem Hinweis auf das Diagramm «Processing Times for the NEW Queue» unter der Adresse https://people.debian.org/~roehling/new_queue/ bedanken; möglicherweise ist dieser Überblick auch für Sie interessant. In diesem Sinne wünsche ich Ihnen viel Erfolg, einen Sponsor zu finden um bald `d11amp` im package tracker zu sehen. Mit freundlichem Gruss, Norwid Behrnd
Bug#1027904: RFS: ruby-mdl/0.12.0-1 [ITP] -- Markdown lint tool
Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package "ruby-mdl": * Package name : ruby-mdl Version : 0.12.0-1 Upstream contact : ["p...@ipom.com"] * URL : https://github.com/markdownlint/markdownlint * License : MIT * Vcs : https://salsa.debian.org/nbehrnd/ruby-mdl Section : ruby The source builds the following binary packages: ruby-mdl - Markdown lint tool To access further information about this package, please visit the following URL: https://mentors.debian.net/package/ruby-mdl/ Alternatively, you can download the package with 'dget' using this command: dget -x https://mentors.debian.net/debian/pool/main/r/ruby-mdl/ruby-mdl_0.12.0-1.dsc Changes for the initial release: ruby-mdl (0.12.0-1) unstable; urgency=medium . * Initial release (Closes: #1026114) Regards,
Re: Tool to cobvert PyPI package into .deb?
The compilation on https://wiki.debian.org/AutomaticPackagingTools equally mentions `python3-stdeb`. Maybe this offers a working alternative to pypi2deb. Regards, Norwid On Mon, 2 Jan 2023 21:51:22 + Barry wrote: > > On 2 Jan 2023, at 21:41, Danial Behzadi دانیال بهزادی > > wrote: > > > > Doesn't Debian helper for Python do exactly this? 樂 > I thought that the dh_ tools are used as part of the rules for a package. > > But i want to give the name of a package on PyPI and have the debian source > package created. > > Barry > > > > > در 2 ژانویهٔ 2023 21:06:18 (UTC)، Barry Scott > > نوشت: > >> > >> I found the pypi2deb package but it does not work. > >> > >> For example: > >> > >> $ py2dsp xml-preferences > >> /usr/bin/py2dsp:163: DeprecationWarning: There is no current event loop > >> loop = asyncio.get_event_loop() > >> E: py2dsp py2dsp:167: 'releases' > >> > >> The problem is that its loading meta data from PyPI and thinks there is a > >> field called 'releases' but it does not exist. > >> > >> I see the same issue with requests. > >> > >> Is there a tool that does work? > >> > >> Or is there a work flow I can follow turn a PyPI package into a debian > >> package? > >> > >> Barry > >> > >>
