public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Mark Hessling <mark.rexx.org@gmail.com>
To: cygwin-apps@cygwin.com
Subject: Questions on my first package update
Date: Wed, 3 Nov 2021 07:26:50 +1000	[thread overview]
Message-ID: <4d053cca-f3a9-dd37-1552-e3b4ae132a47@gmail.com> (raw)

As this is my first update on a package I released a few years ago, I
have a couple of questions please.

I upgraded the regina-rexx package today and received warnings in the
calm email:

INFO: package 'regina-rexx': sdesc ends with '.'
INFO: package 'regina-rexx': sdesc ends with '.'
INFO: package 'libregina-devel': sdesc ends with '.'
INFO: package 'libregina': sdesc ends with '.'

The packages uploaded fine, but when I do a search for the packages via
https://cygwin.com/cgi-bin2/package-grep.cgi?grep=regina&arch=x86_64 the
updated packages don't show a description whereas the initial version
did. eg:

  * libregina-devel-3.8.2-1
    <https://cygwin.com/cgi-bin2/package-cat.cgi?file=x86_64%2Flibregina-devel%2Flibregina-devel-3.8.2-1&grep=regina> -
    libregina-devel: An ANSI compliant Rexx Interpreter. Development
    libraries and headers. (installed binaries and support files)
  * libregina-devel-3.9.4-1
    <https://cygwin.com/cgi-bin2/package-cat.cgi?file=x86_64%2Flibregina-devel%2Flibregina-devel-3.9.4-1&grep=regina> -
  * libregina-3.8.2-1
    <https://cygwin.com/cgi-bin2/package-cat.cgi?file=x86_64%2Flibregina%2Flibregina-3.8.2-1&grep=regina> -
    libregina: An ANSI compliant Rexx Interpreter. Runtime libraries.
    (installed binaries and support files)
  * libregina-3.9.4-1
    <https://cygwin.com/cgi-bin2/package-cat.cgi?file=x86_64%2Flibregina%2Flibregina-3.9.4-1&grep=regina> -

Would this lack of description be due to the warnings and if so can I
rebuild and upload the packages again after removing the trailing '.'
from the SUMMARY fields in the cygport file ?

Once I sort this out I'll send out the announcment email.

Thanks, Mark

-- 
------------------------------------------------------------------------
* Mark Hessling, mark@rexx.org http://www.rexx.org/
* Author of THE, a Free XEDIT/KEDIT editor and, Rexx/SQL, Rexx/CURL, etc.
* Maintainer of Regina Rexx interpreter
* Use Rexx? join the Rexx Language Association: https://www.rexxla.org/ 
------------------------------------------------------------------------


             reply	other threads:[~2021-11-02 21:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-02 21:26 Mark Hessling [this message]
2021-11-02 23:27 ` Jon Turney
2021-11-03  5:19   ` Mark Hessling

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4d053cca-f3a9-dd37-1552-e3b4ae132a47@gmail.com \
    --to=mark.rexx.org@gmail.com \
    --cc=cygwin-apps@cygwin.com \
    --cc=mark@rexx.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).