Bug#981794: RFS: gftools/0.5.2+dfsg-1 [ITP] -- Google Fonts Tools

2021-06-03 Thread Romain Porte
03/06/2021 09:27, Tobias Frost :
> On Wed, Jun 02, 2021 at 11:57:51PM +0200, Romain Porte wrote:
>> Hi tobi,
>>
>> On Wed, 02 Jun 2021 17:02:06 +0200 Tobias Frost  wrote:
>>
>> I have fixed this issue by renaming the dependency to the correct name
>> (python3-ots instead of python3-opentype-sanitizer). New package version
>> has just been signed and uploaded to mentors [1]. The commit that
>> provides the fix was also pushed to the Salsa repository [2].
>>
> Thanks for the quick update!
>
> The package seems good, beside d/copyright:
> - Copyright years are missing
> - d/copyright is incomplete/inaccurate:
> for example: file bin/gftools-fix-ascii-fontmetadata.py has:
> # Copyright 2013 The Font Bakery Authors.
> # Copyright 2017 The Google Font Tools Authors
> (- optional: Its customary to say "Apache-2.0", not "Apache-2" as license
>identifier in d/copyright, this is also the SPDX identifier for it.)
>
> So, after you've reviewed and updated c/copyright, ping me again.

Thanks for the review, new proposal sent to mentors (#7) and commits
pushed to salsa to fix all of the listed issues.


> (Note: I'm usually not sponsoring python, but as this package blocks other 
> RFSs,
> I'm doing an exception here. If someone with more experience in this field 
> wants
> to chime in, I'd be happy.)

I usually work with the Python team, but to me this package makes more
sense to be in the Debian Fonts team. I think I applied all of the good
practises enforced by the Debian Python team on their packages, so there
should not be any issues even from a Python perspective.

Thanks in advance for the review/upload and cheers,

Romain.



Bug#989424: marked as done (RFS: radsecproxy/1.8.2-4~bpo10+1 -- RADIUS protocol proxy supporting RadSec)

2021-06-03 Thread Debian Bug Tracking System
Your message dated Thu, 3 Jun 2021 18:54:19 +0200
with message-id 
and subject line Re: RFS: radsecproxy/1.8.2-4~bpo10+1 -- RADIUS protocol proxy 
supporting RadSec
has caused the Debian Bug report #989424,
regarding RFS: radsecproxy/1.8.2-4~bpo10+1 -- RADIUS protocol proxy supporting 
RadSec
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.)


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

Package: sponsorship-requests
Severity: normal

Dear mentors,

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

 * Package name: radsecproxy
   Version : 1.8.2-4~bpo10+1
   Upstream Author : Fabian Mauchle 
 * URL : https://radsecproxy.github.io/
 * License : BSD-3-clause
 * Vcs : https://salsa.debian.org/debian/radsecproxy
   Section : net

It builds those binary packages:

  radsecproxy - RADIUS protocol proxy supporting RadSec

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


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

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

  dget -x 
https://mentors.debian.net/debian/pool/main/r/radsecproxy/radsecproxy_1.8.2-4~bpo10+1.dsc


Changes since the last upload:

 radsecproxy (1.8.2-4~bpo10+1) buster-backports; urgency=medium
 .
   * Rebuild for buster-backports.

Grüße,
Sven!



OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
uploaded. thanks for providing the backports package!--- End Message ---


Bug#988484: Bug#974678: ITP: openh264 -- H.264 encoding and decoding

2021-06-03 Thread Sam Hartman
> "Bastian" == Bastian Germann  writes:

Bastian> There are H.264 patents that are applicable. I do not know
Bastian> how the existing H.264 implementations in Debian handle
Bastian> this, e.g. x264 or ffmpeg. According to the legal FAQ,
Bastian> these seem to be ignored.

I suspect you meant to say that there are H.264 patents that may be
applicable and that Debian should evaluate this risk using its normal
proocesses and policies for looking at software patents.

THOSE PROCESSES DO NOT INVOLVE debian-legal.  Discussing patents in a
public forum may result in speculative communication--like the assertion
above where you said that patents are applicable and where you probably
meant to say that the patents may be applicable--being produced in
response to allegations of patent infringement.
That harms Debian.
Thus, we have a policy that we discuss patents only in privileged
communication.
See https://www.debian.org/legal/patent


and if you are concerned about a specific patent risk, write to
pate...@debian.org.


signature.asc
Description: PGP signature


Bug#989424: RFS: radsecproxy/1.8.2-4~bpo10+1 -- RADIUS protocol proxy supporting RadSec

2021-06-03 Thread Sven Hartge

Package: sponsorship-requests
Severity: normal

Dear mentors,

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

 * Package name: radsecproxy
   Version : 1.8.2-4~bpo10+1
   Upstream Author : Fabian Mauchle 
 * URL : https://radsecproxy.github.io/
 * License : BSD-3-clause
 * Vcs : https://salsa.debian.org/debian/radsecproxy
   Section : net

It builds those binary packages:

  radsecproxy - RADIUS protocol proxy supporting RadSec

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


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

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

  dget -x 
https://mentors.debian.net/debian/pool/main/r/radsecproxy/radsecproxy_1.8.2-4~bpo10+1.dsc


Changes since the last upload:

 radsecproxy (1.8.2-4~bpo10+1) buster-backports; urgency=medium
 .
   * Rebuild for buster-backports.

Grüße,
Sven!



OpenPGP_signature
Description: OpenPGP digital signature


Bug#981794: RFS: gftools/0.5.2+dfsg-1 [ITP] -- Google Fonts Tools

2021-06-03 Thread Tobias Frost
On Wed, Jun 02, 2021 at 11:57:51PM +0200, Romain Porte wrote:
> Hi tobi,
> 
> On Wed, 02 Jun 2021 17:02:06 +0200 Tobias Frost  wrote:
> 
> I have fixed this issue by renaming the dependency to the correct name
> (python3-ots instead of python3-opentype-sanitizer). New package version
> has just been signed and uploaded to mentors [1]. The commit that
> provides the fix was also pushed to the Salsa repository [2].
>

Thanks for the quick update!

The package seems good, beside d/copyright:
- Copyright years are missing
- d/copyright is incomplete/inaccurate:
for example: file bin/gftools-fix-ascii-fontmetadata.py has:
# Copyright 2013 The Font Bakery Authors.
# Copyright 2017 The Google Font Tools Authors
(- optional: Its customary to say "Apache-2.0", not "Apache-2" as license
   identifier in d/copyright, this is also the SPDX identifier for it.)

So, after you've reviewed and updated c/copyright, ping me again.

(Note: I'm usually not sponsoring python, but as this package blocks other RFSs,
I'm doing an exception here. If someone with more experience in this field wants
to chime in, I'd be happy.)

Cheers,
-- 
tobi