Bug#1042362: RFS: streamlink/6.0.0-1 -- CLI for extracting video streams from various websites to a video player
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "streamlink" for a new upstream version 6.0.0. * Package name: streamlink Version : 6.0.0-1 Upstream Author : Streamlink Team * URL : https://streamlink.github.io/ * License : BSD-2-clause, Apache-2.0, MIT/Expat, SIL-OFL-1.1 Section : python It builds those binary packages: python3-streamlink - Python module for extracting video streams from various websites python3-streamlink-doc - CLI for extracting video streams from various websites (documentation) streamlink - CLI for extracting video streams from various websites to a video player To access further information about this package, please visit the following URL: https://mentors.debian.net/package/streamlink Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/s/streamlink/streamlink_6.0.0-1.dsc Changes since the last upload to unstable: streamlink (6.0.0-1) unstable; urgency=medium * d/upstream/signing-key.asc: update upstream key * New upstream version 6.0.0 * d/patches: update patches * d/control: add new dependency python3-pytest-trio * d/rules: streamlink manpage: use CW font instead of C * d/rules: remove unused inclusion of pkg-info.mk * d/rules: fix duplicate doc assets * Upload to unstable -- Alexis Murzeau Mon, 24 Jul 2023 23:56:25 +0200 streamlink (5.5.1-1~exp1) experimental; urgency=medium * New upstream version 5.5.1 * d/patches: update patches * d/patches,control: use furo theme instead of sphinx-rtd-theme * d/patches,control: use fork-awesome as a replacement for font-awesome * d/s/lintian-overrides: remove obsolete override about a test file -- Alexis Murzeau Sat, 20 May 2023 19:52:43 +0200 Regards, -- Alexis Murzeau PGP: B7E6 0EBB 9293 7B06 BDBC 2787 E7BD 1904 F480 937F OpenPGP_signature Description: OpenPGP digital signature
Bug#1042361: RFS: texlive-bin/2023.20230311.66589-3 -- TeX Live: Package split
Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package "texlive-bin": * Package name : texlive-bin Version : 2023.20230311.66589-3 Upstream contact : k...@freefriends.org * URL : https://www.tug.org/texlive/ * License : MIT, TeX-Live, GPL-2+ * Vcs : https://github.com/debian-tex/texlive-bin Section : tex The source builds the following binary packages: texlive-binaries - Binaries for TeX Live texlive-binaries-sse2 - Binaries for TeX Live (the JIT part) libkpathsea6 - TeX Live: path search library for TeX (runtime part) libkpathsea-dev - TeX Live: path search library for TeX (development part) libptexenc1 - TeX Live: pTeX encoding library libptexenc-dev - TeX Live: ptex encoding library (development part) libsynctex2 - TeX Live: SyncTeX parser library libsynctex-dev - TeX Live: SyncTeX parser library (development part) libtexlua53 - transitional package (lib) libtexlua53-5 - TeX Live: Lua 5.3, modified for use with LuaTeX libtexlua53-dev - transitional package (dev) libtexlua-dev - TeX Live: Lua 5.3, modified for use with LuaTeX (development part) libtexluajit2 - TeX Live: LuaJIT, modified for use with LuaJITTeX libtexluajit-dev - TeX Live: LuaJIT, modified for use with LuaJITTeX (development part) To access further information about this package, please visit the following URL: https://mentors.debian.net/package/texlive-bin/ Alternatively, you can download the package with 'dget' using this command: dget -x https://mentors.debian.net/debian/pool/main/t/texlive-bin/texlive-bin_2023.20230311.66589-3.dsc Changes since the last upload: texlive-bin (2023.20230311.66589-3) experimental; urgency=medium . * Split luajit based binaries into texlive-binaries-sse2 to make TL usable on non sse2 capable CPU's at all (Closes: #1041148). Regards, -- Hilmar Preusse -- sigmentation fault signature.asc Description: PGP signature
Bug#1036751: RFS: mini-httpd/1.30-4 [ITA] -- Small HTTP server
Hi Alexandru, For brevity I've omitted the parts that look good. Alexandru Mihail writes: > RobMcCool's copyright was traced from a git repository which > imported NCSA httpd (which was verified to be precise). > Multiple commits by RobMcCool on HEAD > show his contributions on the files specified here. Thank you you have the right idea about writing how you established copyright. That said, what you've written is impossible, because Rob McCool's work was 1993-1994, but git's first release was in 2005 ;) Also, please revise the text to explain what "verified to be precise" means. Grammatically, it sounds like you verified that the tags in the repository match the WayBack Machine's copies of release tarballs. Did you verify that Jef Poskanzer didn't make edits? If Jef Poskanzer made edits, they would most likely be under the mini-httpd project license, thus the effective license would be BSD-2-clause. A simple solution would be claim these files are BSD-2-clause, but to note that htpasswd* contain (or are mostly) NCSA licensed, and then shift the NCSA licence text into the Comment section of Files: htpasswd.* If you run lintian without shifting the license text you'll learn why I recommend it. \cut this/ > The files are under the NCSA license which qualifies as DFSG > compatible after inquiry (specifically, from the license text: > > "This code is in the public domain. Specifically, we give to the > public > domain all rights for future licensing of the source code, all resale > rights, and all publishing rights" > > From DSFGLicenses's Q on DebianWiki: > > "Software placed in the public domain has all the freedoms > required by the DFSG, and is free software." /cut this\ I'm still not certain that this wiki contributor's position is legally sound everywhere in the world. For a counter example see: https://opensource.stackexchange.com/questions/9871/why-is-there-no-public-domain-licensing-in-europe > git repository: https://github.com/TooDumbForAName/ncsa-httpd/ Note: If you provide a link that isn't on Debian infrastructure then you'll also need to summarise what it contains (for various reasons that I can explain if you're interested). It may be worth noting that someone else can use this to verify if the htpasswd.* copy in mini-httpd corresponds to the NCSA copy. > debian-legal thread: > https://lists.debian.org/debian-legal/2023/07/msg1.html > DFSGLicenses: https://wiki.debian.org/DFSGLicenses / \ Nice, but cut the last line of /this\ Thanks again for reading this page, as well as for sharing the story of how it inspired you to contribute to Debian! :) > Is my TLDR still a bit TL ? I was trying not to leave out anything > related to discussion on debian-legal or how we traced everything back > to RobMcCool. Thank you for your attention to detail, and yes, still too long. There has been far more discussion at this bug than at debian-legal... > Did i get the right field ? > > "6.6. Comment > > Formatted text, no synopsis: this field can provide additional > information. For example, it might quote an e-mail from upstream > justifying why the license is acceptable to the main archive, or an > explanation of how this version of the package has been forked from a > version known to be DFSG-free, even though the current upstream version > is not. " > > Sounded like a good fit. You're right, yes, that's the one :) > Replying to previous untackled mail: >>Wow, that's wonderful (and unexpected) news! I hope negotiations go > well. > > Thanks, me too :) I'll have to complete the new maintainer process here > (and actually have an upload by my mentor (you!) before I can discuss > matters more firmly with higher-ups. There's no rush; your patience and > attention to detail are very appreciated btw :) Thanks :) >>My key is on both the Debian keyring and public servers >> >> https://wiki.debian.org/DebianKeyring >> https://keys.openpgp.org/ >> and maybe also here >> http://pgp.mit.edu/ > > OK, thanks, I'll have to find a good place for my key too, then. I confirmed your signature on this email. Here are some key-related resources: https://wiki.debian.org/Keysigning https://wiki.debian.org/Keysigning/Coordination Best, Nicholas P.S. Please consider trimming the irrelevant quotation from correspondences on the BTS. It's a top-posting convention that takes up a lot of space and waste time (since we're an in-line posting community) https://bugs.debian.org/1036751 signature.asc Description: PGP signature
Bug#1031284: RFS: wl-mirror/0.12.2-1 [ITP] -- output-mirroring tool for wlroots-based Wayland desktops
This package looks good, I've just sponsored an upload with an amd64 build. Best of luck with source NEW, -- Simon Quigley si...@tsimonq2.net tsimonq2 on LiberaChat and OFTC @tsimonq2:linuxdelta.com on Matrix 5C7A BEA2 0F86 3045 9CC8 C8B5 E27F 2CF8 458C 2FA4 OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1042092: RFS: wsclean/3.1-4 [RC] [Team] -- Fast generic widefield interferometric imager
Package: sponsorship-requests Severity: important Dear mentors, I am looking for a sponsor for my package "wsclean": * Package name : wsclean Version : 3.1-4 Upstream contact : [fill in name and email of upstream] * URL : https://gitlab.com/aroffringa/wsclean/ * License : BSD-3-Clause, GPL-3.0+ * Vcs : https://salsa.debian.org/debian-astro-team/wsclean Section : science The source builds the following binary packages: wsclean - Fast generic widefield interferometric imager wsclean-dev - Fast generic widefield interferometric imager (development files) To access further information about this package, please visit the following URL: https://mentors.debian.net/package/wsclean/ Alternatively, you can download the package with 'dget' using this command: dget -x https://mentors.debian.net/debian/pool/main/w/wsclean/wsclean_3.1-4.dsc Changes since the last upload: wsclean (3.1-4) unstable; urgency=medium . * Team upload. * Add fix-gcc-13.patch to fix gcc-13 build issues. (Closes: #1037899) -- Regards, -- Bo YU signature.asc Description: PGP signature
Bug#1034282: BUG1041595,RFS: ukui-app-widget
Hi, 在 2023-07-24星期一的 16:54 +0800，xibowen写道： > Hi ,Boyuan > > I have fixed all of the issue submitted above, and have uploaded the latest > to mentors. > URL：https://mentors.debian.net/package/ukui-app-widget/ Your package has a COPYING file under root dir with LGPL-2.1 contents, yet most other source files and debian/copyright file claims that the project is under GPL. Can you work with upstream to determine the overall license of this project? Is it GPL or LGPL? * If the project in whole is using GPL, please replace the COPYING file with GPL contents, and use the most appropriate GPL version (v2 or v3) for you. That selection must be kept in sync with debian/copyright information. * If the project in whole is using LGPL, please correct information in debian/copyright, and update the header of any source files if necessary. Thanks, Boyuan Yang signature.asc Description: This is a digitally signed message part
