Bug#976260: RFS: opentype-sanitizer/8.1.0-1 [ITP] -- tools to validate and sanitize OTF/TTF/WOFF/WOFF2 font files

[Paul Wise]

On Wed, Dec 2, 2020 at 11:45 AM Romain Porte wrote:

>   dget -x 
> https://mentors.debian.net/debian/pool/main/o/opentype-sanitizer/opentype-sanitizer_8.1.0-1.dsc

The package (and upstream) is missing copyright and license
information for all of the test fonts. Some of them contain no license
information, so it isn't clear that they are legal for Debian (and
upstream) to redistribute. There are no source files for any of them,
which could be a violation of DFSG item 2. Some of them are SIL OFL
licensed, with reserved font names, which means that modifying them is
a license violation unless you also rename them. Personally I would
remove the test fonts from the Debian source package.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise

Bug#971890: RFS: tensorwatch/0.9.0-1 [ITP] -- Debug, monitor and visualize for Python Machine Learning

[Adam Borowski]

On Fri, Oct 09, 2020 at 08:09:10AM +0200, Gürkan Myczko wrote:
>  * Package name: tensorwatch
>Version : 0.9.0-1

>  tensorwatch (0.9.0-1) unstable; urgency=medium
>  .
>* Initial release. (Closes: #931009)

autopkgtest [00:34:21]: test autodep8-python3: [---
Testing with python3.8:
Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python3/dist-packages/tensorwatch/__init__.py", line 26, in 

from .embeddings.tsne_utils import get_tsne_components
  File "/usr/lib/python3/dist-packages/tensorwatch/embeddings/tsne_utils.py", 
line 4, in 
from sklearn.manifold import TSNE
ModuleNotFoundError: No module named 'sklearn'
autopkgtest [00:34:22]: test autodep8-python3: ---]


喵!
-- 
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ A white dwarf seeks a red giant for a binary relationship.
⢿⡄⠘⠷⠚⠋⠀
⠈⠳⣄

Bug#973642: marked as done (RFS: fonts-joscelyn/1.012+ds-1 [ITP] -- authentic secretary hand font)

[Debian Bug Tracking System]

Your message dated Wed, 2 Dec 2020 23:55:21 +0100
with message-id <20201202225521.ga18...@angband.pl>
and subject line Re: Bug#973642: RFS: fonts-joscelyn/1.012+ds-1 [ITP] -- 
authentic secretary hand font
has caused the Debian Bug report #973642,
regarding RFS: fonts-joscelyn/1.012+ds-1 [ITP] -- authentic secretary hand font
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
973642: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973642
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package "fonts-joscelyn":

 * Package name: fonts-joscelyn
   Version : 1.012+ds-1
   Upstream Author : Peter S. Baker 
 * URL : https://github.com/psb1558/Joscelyn-font
 * License : OFL-1.1
 * Vcs : https://salsa.debian.org/fonts-team/fonts-joscelyn
   Section : fonts

It builds those binary packages:

  fonts-joscelyn - authentic secretary hand font

To access further information about this package, please visit the 
following URL:


  https://mentors.debian.net/package/fonts-joscelyn/

Alternatively, one can download the package with dget using this 
command:


  dget -x 
https://mentors.debian.net/debian/pool/main/f/fonts-joscelyn/fonts-joscelyn_1.012+ds-1.dsc


Changes for the initial release:

 fonts-joscelyn (1.012+ds-1) unstable; urgency=medium
 .
   * Initial release. (Closes: #966268)

Regards,
--
  Gürkan Myczko
--- End Message ---
--- Begin Message ---
On Mon, Nov 02, 2020 at 07:28:49PM +0100, Gürkan Myczko wrote:
>  * Package name: fonts-joscelyn
>Version : 1.012+ds-1

>  fonts-joscelyn (1.012+ds-1) unstable; urgency=medium
>  .
>* Initial release. (Closes: #966268)

In NEW, although there are some issues:

* no watch version mangling, prohibited embedding -- as pointed out by
  Lintian

* I consider the short desc to be strongly misleading.  When someone says
  "authentic secretary hand font" it evokes a secretary 4.5 centuries
  younger.  People who write by hand a lot have a well-developed
  writing style, and if they're actually paid for readability (as opposed
  to eg. medical professionals[1]), that's a "secretary hand".
  On the other hand, this font is about a _Renaissance_ dude.


Meow!

[1]. Who overhelmingly, in my experience, match the stereotype.
-- 
⢀⣴⠾⠻⢶⣦⠀ Meow!
⣾⠁⢠⠒⠀⣿⡁
⢿⡄⠘⠷⠚⠋⠀ I was born a dumb, ugly and work-loving kid, then I got swapped on
⠈⠳⣄ the maternity ward.--- End Message ---

Bug#973865: RFS: dhcpdump/1.8-3 [ITA] -- Capture dhcp-packets and show for easier checking and debugging

[Baptiste Beauplat]

Hi Peter,

On 12/2/20 10:16 AM, Peter Ji wrote:

You have a number of easy to fix lintian tags. I'd recommend to fix them.>


Thanks for your review, Lintian tags have been fixed in the latest upload.


That's great news! The first time around, I only looked at
mentors.debian.net QA information. Now is time for a bit more in-depth
review. Don't hesitate to ask questions, I'll happy to answer them :)

Note: Read through the entire mail, I have a couple of useful links in
the end.

- debian/changelog:

  It's looking a bit thin. Each and every changes from one version to
another must be documented in this file. For instance you've added the
VCS fields, the Homepage, the Require-Root-Rules in debian/control. That
must be documented along side with every modification you've made.

  Don't hesitate to run a spell checker on the changelog once done. You
have a syntax error with the comma.

- debian/control:

  You can bump the policy to 4.5.1, it was released a couple of days
ago. To see if you have any additional modification see the checklist [1]

  The Homepage field is an URL to upstream sources [2], not the
packaging one.

  You shouldn't need Require-Root-Rule to build that software. I suppose
it's required because you explicitly set the owner/group when installing
the program. Drop that and the R-R-R.

  Once again the spell checking indicates a syntax error. Your "for" is
preceded by a dot.

- debian/copyright:

  The Source, like the Homepage field of debian/control also refers to
the upstream source.

  You are missing a block for the debian/* files. You should list every
authors present in debian/changelog, including yourself.

  You are missing an entry for strsep.c, which license and copyright
holder differs from other sources (man licensecheck).

- debian/NMU-Disclaimer:

  NMU is quite well defined in the developer reference [3]. Unless you
plan on following those outdated guidelines, you can safely drop this file.

- debian/patches:

  Your patch name and description doesn't match the content of the
patch. You are patching different files for different reason and a
separate patch file is needed for each one of them.

  Don't update upstream CHANGES with Debian changelog information. Both
will be installed under /usr/share/doc/ and content should be
respectively separated.

  Don't patch the Makefile with anything related to the Debian
packaging. That should be done in debian/rules.

  You have a trailing whitespace line 108 of the patch file and the
"for" have that previous dot as well.

  Creating a README.Debian with sole content the description of the
package is useless. Please remove it. (also the file should have been
wrap to 80 colons).

- debian/rules:

  You switched to using dh, which is very good, but you are not using
any of the dh helper files. Please have a look at the Debian New
Maintainer Guide [4] to help you move all the content of that file to
debian/{install,manpage,clean,...}. As a thumb rule, if you have any
target not starting by 'execute_{before,after}_dh_' or 'override_dh',
you are not finished with the dh conversion.

- debian/watch:

  The watch file should monitor upstream release [2], not the packaging 
one.


---

I know the list looks long but believe me, it's actually quite feasible
:) You can have a look at dhcping packaging [5]. It's a very similar
package, from the same upstream, that I converted a couple of weeks ago.

Do you know about Debian's Gitlab [6]? While hosting the packaging
source anywhere public is actually quite alright, having it on salsa
does bring out a couple advantages:

- you can create the repository under the debian/ namespace. This will
ease collaborative maintenance by any Debian Developer. (Note that you
will need to ask the repository creation on debian-mentors@lists.debian.org)
- you have access to a nice CI [7] pipeline doing all sort of QA stuff
on you package.
- it's open-source! As opposed to github :)

[1]: 
https://www.debian.org/doc/debian-policy/upgrading-checklist.html#version-4-5-1

[2]: http://www.mavetju.org/unix/general.php
[3]: https://www.debian.org/doc/manuals/developers-reference/
[4]: https://www.debian.org/doc/manuals/maint-guide/
[5]: https://salsa.debian.org/debian/dhcping
[6]: https://salsa.debian.org
[7]: https://salsa.debian.org/salsa-ci-team/pipeline

--
Baptiste Beauplat - lyknode



OpenPGP_signature
Description: OpenPGP digital signature

Re: Trouble with building the opendht package on mipsel

[Matthew Fernandez]

> On Dec 2, 2020, at 10:41, Andrey Rahmatullin  wrote:
> 
> As I've already told you yesterday on IRC, the test succeeds with -O2,
> which is set when building the package.

Furthermore you can actually see a variant of the problem with this test code 
even on non-MIPS:

$ uname -m
x86_64
$ cat - >main.cc  <
int main(void) {
  // a fancy type that needs -mcx16
  struct Foo { unsigned __int128 x; };
  std::atomic y;
  y.is_lock_free();
}
EOT
$ g++ -std=c++11 main.cc 
/tmp/h43jh.o: In function `std::atomic::is_lock_free() const’:
main.cc :(text+0x57): undefined reference to 
`__atomic_is_lock_free’
collect2: error: ld returned 1 exit status
$ echo $?
1
$ g++ -O3 -std=c++11 main.cc 
$ echo $?
0

The compiler can see the atomic and its use are dead code and removes them.

Re: Trouble with building the opendht package on mipsel

[Andrey Rahmatullin]

As I've already told you yesterday on IRC, the test succeeds with -O2,
which is set when building the package.

-- 
WBR, wRAR


signature.asc
Description: PGP signature

Trouble with building the opendht package on mipsel

[Amin Bandali]

Hello debian-mentors,

[ I originally posted this to the pkg-voip-maintainers list; but having
  not gotten a reply there, and asking in #debian-mentors on OFTC about
  where the best place would be to ask this, I was guided here.  So I'm
  posting a copy here as well. ]

I've been working for a while on helping bring up-to-date the version of
Jami in the official Debian repos.  We've made some progress, but I've
run into a seemingly Debian-specific issue that I'm not sure how to work
around, and would appreciate any help I could get.

Context: opendht version 2.1.6-1 fails to build on architectures that
lack atomic support, as reflected in the build logs at
.
As such, I asked upstream to adapt their CMake rules to link against
libatomic when necessary, and upstream versions 2.1.8.1 and later
include that fix.

I have verified that the upstream fix works on a mipsel machine, by
locally bumping the Debian package to latest release, and invoking cmake
and building manually on the terminal.  I see the following output from
CMake, as expected:

-- Performing Test HAVE_CXX_ATOMICS_WITHOUT_LIB
-- Performing Test HAVE_CXX_ATOMICS_WITHOUT_LIB - Failed
-- Looking for __atomic_fetch_add_4 in atomic
-- Looking for __atomic_fetch_add_4 in atomic - found
-- Performing Test HAVE_CXX_ATOMICS_WITH_LIB
-- Performing Test HAVE_CXX_ATOMICS_WITH_LIB - Success

However, it seems that CMake when invoked by the Debian packaging tools
(I tried both `dpkg-buildpackage -us -uc' and `debuild -b -uc -us'),
CMake fails to recognize the need for linking against libatomic, and
somehow mistakenly deduces that linking against libatomic isn't
necessary, when it very much is.  I see:

-- Performing Test HAVE_CXX_ATOMICS_WITHOUT_LIB
-- Performing Test HAVE_CXX_ATOMICS_WITHOUT_LIB - Success

Which looks clearly wrong to me, because later in the build process, it
will fail at the linking stage due to absence of atomics.

To try and find where the issue could be, I basically replaced the
content of the package's `override_dh_auto_configure' in `debian/rules'
with the exact series of commands I run from the terminal (i.e. mkdir
build && cd build && cmake ..), but I still observe the different
behaviour of CMake.

Any thoughts as to what is happening here?  I would appreciate any
pointers/tips on how to proceed with debugging this issue.

Thanks in advance,

-- 
Amin Bandali
Free Software Consultant
Savoir-faire Linux
jami:bandali

Bug#976273: RFS: motor/3.5.1-1 -- ncurses based ide

[Witherking25]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "motor":

 * Package name: motor
   Version : 3.5.1-1
   Upstream Author : 
 * URL : https://github.com/rofl0r/motor
 * License : GPL-2.0+
 * Vcs : [fill in URL of packaging vcs]
   Section : devel

It builds those binary packages:

  motor - ncurses based ide

To access further information about this package, please visit the
following URL:

  https://mentors.debian.net/package/motor/

Alternatively, one can download the package with dget using this command:

  dget -x https://mentors.debian.net/debian/pool/main/m/motor/motor_3.5.1-1.dsc

Changes since the last upload:

 motor (3.5.1-1) unstable; urgency=medium
 .
   * Initial release (Closes: #976263)

Regards,
--
  Witherking25

Bug#976260: almost perfect, and many thanks for packaging this (and gfstools)

[Romain Porte]

Thanks for the positive feedback!

2020-12-02 12:53 CET, Gurkan Myczko:
> looks like meson is missing in build-depends:

Done.

> and the debian/upstream/metadata is easy too:
> Bug-Database: https://github.com/khaledhosny/ots/issues
> Bug-Submit: https://github.com/khaledhosny/ots/issues/new
> Repository: https://github.com/khaledhosny/ots.git
> Repository-Browse: https://github.com/khaledhosny/ots

Done.

New revision has been uploaded on mentors with these changes.

Best regards,

Romain.


signature.asc
Description: PGP signature

Bug#976260: almost perfect, and many thanks for packaging this (and gfstools)

[Gurkan Myczko]

Purging configuration files for libglib2.0-0:amd64 (2.66.3-1) ...
Purging configuration files for libmagic1:amd64 (1:5.39-3) ...
Purging configuration files for man-db (2.9.3-2) ...
Purging configuration files for autoconf (2.69-11.1) ...
Purging configuration files for groff-base (1.22.4-5) ...
E: Build failure (dpkg-buildpackage died)

+--+
| Summary
  |
+--+

Build Architecture: amd64
Build Type: binary
Build-Space: 55808
Build-Time: 1
Distribution: sid
Fail-Stage: build
Host Architecture: amd64
Install-Time: 9
Job: /var/www/debian/mentors/opentype-sanitizer_8.1.0-1.dsc
Machine Architecture: amd64
Package: opentype-sanitizer
Package-Time: 37
Source-Version: 8.1.0-1
Space: 55808
Status: attempted
Version: 8.1.0-1

Finished at 2020-12-02T11:49:59Z
Build needed 00:00:37, 55808k disk space
E: Build failure (dpkg-buildpackage died)

looks like meson is missing in build-depends:
Can't exec "meson": No such file or directory at
/usr/share/perl5/Debian/Debhelp
er/Dh_Lib.pm line 517.

and the debian/upstream/metadata is easy too:
Bug-Database: https://github.com/khaledhosny/ots/issues
Bug-Submit: https://github.com/khaledhosny/ots/issues/new
Repository: https://github.com/khaledhosny/ots.git
Repository-Browse: https://github.com/khaledhosny/ots
Needs work Gürkan Myczko at Dec. 2, 2020, 11:51 a.m.

Bug#976260: RFS: opentype-sanitizer/8.1.0-1 [ITP] -- tools to validate and sanitize OTF/TTF/WOFF/WOFF2 font files

[Romain Porte]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package "opentype-sanitizer":

 * Package name: opentype-sanitizer
   Version : 8.1.0-1
   Upstream Author : Khaled Hosny 
 * URL : https://github.com/khaledhosny/ots
 * License : BSD-3-Clause
 * Vcs : https://salsa.debian.org/fonts-team/opentype-sanitizer
   Section : fonts

It builds those binary packages:

  opentype-sanitizer - tools to validate and sanitize OTF/TTF/WOFF/WOFF2 font 
files

To access further information about this package, please visit the following 
URL:

  https://mentors.debian.net/package/opentype-sanitizer/

Alternatively, one can download the package with dget using this command:

  dget -x 
https://mentors.debian.net/debian/pool/main/o/opentype-sanitizer/opentype-sanitizer_8.1.0-1.dsc

Changes for the initial release:

 opentype-sanitizer (8.1.0-1) unstable; urgency=low
 .
   * Initial release. Closes: #975983

Regards,
--
  Romain Porte

Bug#973865: RFS: dhcpdump/1.8-3 [ITA] -- Capture dhcp-packets and show for easier checking and debugging

[Peter Ji]

 Hi, Baptiste:


>You have a number of easy to fix lintian tags. I'd recommend to fix them.>


Thanks for your review, Lintian tags have been fixed in the latest upload.


Hoping for sponsorship. thanks.

 
Regards,
--
  Peter_Ji

Bug#976256: RFS: python-imgviz/1.2.3+ds-1 -- Image Visualization Tools (Python 3)

[Gürkan Myczko]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "python-imgviz":

 * Package name: python-imgviz
   Version : 1.2.3+ds-1
   Upstream Author : Kentaro Wada
 * URL : https://github.com/wkentaro/imgviz
 * License : BSD-3-clause, MIT
 * Vcs : https://salsa.debian.org/myczko-guest/imgviz
   Section : python

It builds those binary packages:

  python3-imgviz - Image Visualization Tools (Python 3)

To access further information about this package, please visit the
following URL:

  https://mentors.debian.net/package/python-imgviz/

Alternatively, one can download the package with dget using this command:

  dget -x
https://mentors.debian.net/debian/pool/main/p/python-imgviz/python-imgviz_1.2.3+ds-1.dsc

Changes since the last upload:

 python-imgviz (1.2.3+ds-1) unstable; urgency=medium
 .
   * New upstream version.
   * Bump debhelper version to 13.
   * d/control: Added to Python Team.
   * d/upstream/metadata: added.

Regards,
--
  Gürkan Myczko

Bug#976257: RFS: fonts-arapey/0+git20200408-2 -- contemporary modern typeface

[Gürkan Myczko]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "fonts-arapey":

 * Package name: fonts-arapey
   Version : 0+git20200408-2
   Upstream Author : Eduardo Rodríguez Tunni 
 * URL : https://github.com/etunni/arapey
 * License : OFL-1.1
 * Vcs : https://salsa.debian.org/fonts-team/fonts-arapey
   Section : fonts

It builds those binary packages:

  fonts-arapey - contemporary modern typeface

To access further information about this package, please visit the
following URL:

  https://mentors.debian.net/package/fonts-arapey/

Alternatively, one can download the package with dget using this command:

  dget -x
https://mentors.debian.net/debian/pool/main/f/fonts-arapey/fonts-arapey_0+git20200408-2.dsc

Changes since the last upload:

 fonts-arapey (0+git20200408-2) unstable; urgency=medium
 .
   * Source only upload.

Regards,
--
  Gürkan Myczko

Bug#968543: Estate donated in your favor#@%

[Flores Guerrero Eduardo Jose]

-

I have decided to donate my estate to you, for your personal benefits and for 
the wellbeing of the elders and less privileged who need help in your 
community. To get more details please write me on this specified email address: 
aa1...@mtazzo.com



Please stay safe out there.



Yours,

P A