Your message dated Fri, 22 Sep 2023 10:14:56 -0400
with message-id <fb5213affe74da66b4f8e6e0fa82f0cb29fe6622.ca...@debian.org>
and subject line Re: Bug#1051994: RFS: inkscape-textext/1.9.0-1 -- Re-editable 
LaTeX graphics for Inkscape
has caused the Debian Bug report #1051994,
regarding RFS: inkscape-textext/1.9.0-1 -- Re-editable LaTeX graphics for 
Inkscape
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.)


-- 
1051994: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051994
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sponsorship-requests
Severity: normal
X-Debbugs-Cc: aeru...@aerusso.net

Dear mentors,

I am looking for a sponsor for my package "inkscape-textext"

 * Package name    : inkscape-textext
   Version         : 1.9.0-1
   Upstream Author : Jan Winkler <encela...@posteo.de>
 * URL             : https://textext.github.io/textext
 * License         : BSD-3-clause
 * Vcs             : https://salsa.debian.org/aerusso-guest/textext
   Section         : graphics
   Description     : Re-editable LaTeX graphics for Inkscape

TexText is a Python plugin for the vector graphics editor Inkscape
providing the possibility to add and re-edit LaTeX generated SVG
elements to your drawing.

 Key features
 . Windows/Linux/MacOS support
 . LaTeX generated SVG elements can be re-edited later
 . Multi-line editor with syntax highlighting
 . Compilation with PdfLaTeX, XeLaTeX or LuaLaTex
 . Interoperable scaling in TexText and Inkscape
 . Font size match with Inkscape text
 . Customizable TeX preamble (additional packages, parskip, parindent, etc.)
 . Colorization via TeX commands/Inkscape is kept after re-editing
 . Alignment anchor of the produced output
 . Preview images

It builds the binary packages:

  inkscape-textext - Re-editable LaTeX graphics for Inkscape
  inkscape-textext-doc - Re-editable LaTeX graphics for Inkscape (documentation)

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

  https://mentors.debian.net/package/inkscape-textext/

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

  dget -x 
https://mentors.debian.net/debian/pool/main/i/inkscape-textext/inkscape-textext_1.9.0-1.dsc

Changes since the last upload:

 inkscape-textext (1.9.0-1) experimental; urgency=medium
 .
   * New upstream release
   * Refresh patches
   * Update debian/copyright
   * Bump standards version (no changes required)
   * Drop support for inkscape <1.3, matching upstream
   * Simplify build scripts
   * Validate upstream signatures
   * Relax architecture dependencies

This upload is primarily to track upstream releases.  Most notably, upstream 
has dropped support for
inkscape <1.3, and I am tracking that change here.

Best,
Antonio Russo

Attachment: OpenPGP_0xB01C53D5DED4A4EE.asc
Description: OpenPGP public key

Attachment: OpenPGP_signature.asc
Description: OpenPGP digital signature


--- End Message ---
--- Begin Message ---
On Fri, 22 Sep 2023 07:55:41 -0600 Antonio Russo <aeru...@aerusso.net> wrote:
> On 2023-09-22 07:29, Boyuan Yang wrote:
> > 
> > You claimed that you are trying to validate upstream signatures, yet your 
> > .dsc file as presented
> > on mentors.debian.net does not include tarball signature at all. Lintian is 
> > also complaining
> > orig-tarball-missing-upstream-signature inkscape-textext_1.9.0.orig.tar.xz. 
> > Do you want to try
> > to fix this problem, or let us upload the current version as-is first?
> > 
> > Thanks,
> > Boyuan Yang
> 
> Hello,
> 
> Thanks for looking at this!  Upstream does not release signed tarballs as far 
> as I can tell.  They
> sign git tags.  I am using pgpmode=git for uscan.  Is this the correct way to 
> handle this?
> 
> I have confirmed that uscan fails if I change upstream/signing-key.asc to 
> another key :
> 
> > gpgv: Signature made Wed Jul 26 03:24:55 2023 MDT
> > gpgv:                using RSA key 32746E27876C1E5418BBBF7F7A9964831E98EED5
> > gpgv: Can't check signature: No public key
> > uscan die: OpenPGP signature did not verify. at 
> > /usr/share/perl5/Devscripts/Uscan/Output.pm line 77.
> 
> I assume that means it is actually verifying the signature.
> 
> Should I add a lintian override to capture this situation?

I think lintian only cares tarball-level signature. Adding a lintian override 
should be okay.

Now I am uploading the current version first. The lintian-related fix can be 
placed in any
later upload. We are handling packages in Experimental now, so being sloppy a 
little bit
does not matter.

Thanks,
Boyuan Yang

Attachment: signature.asc
Description: This is a digitally signed message part


--- End Message ---

Reply via email to