bringing python-django-registration back into testing, dfsg issues
Hello python-django-registration has been removed from testing, and since it's an useful package I'd like to bring it back into it. There is a new upstream release, and there was already some work done in git to package it, but it was failing because upstream has added a new dependency on https://pypi.org/project/confusable_homoglyphs/ The problem with the latter is that it includes two files from the unicode consortium: http://www.unicode.org/Public/UNIDATA/Scripts.txt http://www.unicode.org/Public/security/latest/confusables.txt which, if my understanding of https://www.unicode.org/copyright.html is correct aren't DFSG, but could be redistributed. I have two questions on how to proceed. 1) I've pushed to git a patch to make confusable_homoglyphs optional: it seems to be working, but it's still missing proper warning of the user that that specific protection is disabled. I would add both a runtime warning and a .NEWS. Do you think it is ok to upload the package like this? 2) Even if the answer to 1 is yes, I can also try to package confusable_homoglyphs: upstream can download the files from the unicode consortium if they aren't available: do you think it's better to use that ability and package the file in contrib, or just put everything in non-free? Personally, the latter sounds quite easier, and I would be strongly tempted by it. -- Elena ``of Valhalla'' 🧛 signature.asc Description: PGP signature
Re: Bug#1007025: git-multimail 1.6.0 package review
Hi On Sat, Sep 24, 2022 at 3:34 PM Bo YU wrote: > > Hi, > On Thu, Sep 22, 2022 at 02:12:07PM -0400, Antoine Beaupré wrote: > >On 2022-09-22 19:43:24, Jeroen Ploemen wrote: > >> On Thu, 22 Sep 2022 12:35:12 -0400 > >> Antoine Beaupré wrote: > >> > >>> I think the simplest solution is not to rewrite the launcher, but to > >>> rename it. So in debian/rules, you would simply do: > >>> > >>> override_dh_auto_install: > >>> dh_auto_install > >>> mv debian/git-multimail/usr/bin/git_multimail.py > >>> debian/git-multimail/usr/bin/git-multimail > >> > >> Antoine, IIRC the git_multimail.py file upstream installs into > >> /usr/bin is not a launcher but a full copy of the module as installed > >> into /usr/lib/python3. The code in that file auto-detects whether > >> it's run as a program. > > > >Oh. I misunderstood that, sorry. > [...] > > Thanks all and please let me know if any issues. I have sent the PR and whcih was merged: https://github.com/git-multimail/git-multimail/pull/224 The latest version git-multimail debian package is here: https://mentors.debian.net/package/git-multimail/ Thanks again.:) > > -- > Regards, > -- >Bo YU >
Re: bringing python-django-registration back into testing, dfsg issues
On Mon, 26 Sept 2022 at 19:18, Elena ``of Valhalla'' Grandi < valha...@debian.org> wrote: > http://www.unicode.org/Public/UNIDATA/Scripts.txt > http://www.unicode.org/Public/security/latest/confusables.txt > which, if my understanding of https://www.unicode.org/copyright.html is > correct aren't DFSG, but could be redistributed. > Given they sit under Public aren't they DATA FILES and subject to https://www.unicode.org/license.txt That license seems very BSD 3-Clause-ish. I suppose it comes down to what "Further specification" means. Does it mean license.txt overrules copyright.html? You could ask debian-legal for guidance. Do you think it is ok to upload the package like this? > It's not ideal but if the result is you cannot use those confusables then its the only way forward. > 2) Even if the answer to 1 is yes, I can also try to package > confusable_homoglyphs: upstream can download the files from the unicode > consortium if they aren't available: do you think it's better to use > that ability and package the file in contrib, or just put everything in > non-free? > > Personally, the latter sounds quite easier, and I would be strongly > tempted by it. > I have a similar problem with SNMP MIBs (thanks IETF). They're not even redistributable so I have a contrib mibs-downloader package. If the system can do it itself, that's ok but it needs to be something that the user knows is happening. I have had issues with WordPress before where it has links in some of the themes. So in summary: * See if license.txt is the actual license and its DFSG free (I think it could be) * If not, I'd package the files in a separate archive - Craig -- > Elena ``of Valhalla'' > > 🧛 >
join the team
Hello guys! I hereby request my membership as a team member! I already keep some packages with the team, and I'm willing to help in any way I can! My salsa login is: nilsonfsilva I have read the team policies and I agree! Thanks! Nilson F. Silva
