From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin-apps@cygwin.com
Subject: Re: calm: cygwin package upload report from sourceware.org for Thomas Wolff
Date: Fri, 29 Mar 2019 18:26:00 -0000 [thread overview]
Message-ID: <1ef81318-a573-b64e-306c-5ec0b16a77ce@SystematicSw.ab.ca> (raw)
In-Reply-To: <3fb315b7-1160-1ef4-7e64-d5f99e0dcd99@towo.net>
On 2019-03-29 12:11, Thomas Wolff wrote:
> I've repeatedly tried to upload a new package, with the two discussed
> modifications in packaging, and the last response was this:
>
> Am 29.03.2019 um 19:02 schrieb cygwin-no-reply@cygwin.com:
>> ERROR: package 'mintty' version '3.0.0-1' is most recent non-test version, but
>> version '2.9.9-0' is curr:
>> ERROR: install packages from source package 'mintty' have non-unique current
>> versions 3.0.0-1 (mintty-debuginfo), 2.9.9-0 (mintty)
>> ERROR: error while validating merged x86 packages for Thomas Wolff
>> ERROR: package 'mintty' version '3.0.0-1' is most recent non-test version, but
>> version '2.9.9-0' is curr:
>> ERROR: install packages from source package 'mintty' have non-unique current
>> versions 3.0.0-1 (mintty-debuginfo), 2.9.9-0 (mintty)
>> ERROR: error while validating merged x86_64 packages for Thomas Wolff
>> SUMMARY: 6 ERROR(s)
> Should I upload mintty-3.0.0-1.hint files with
> curr: 3.0.0.1
> prev: 2.9.9.0
> ?
If used, that should be:
curr: 3.0.0-1
prev: 2.9.9-0
Check your ${P}/${P}-${V}/${P}-${V}-{R}.${ARCH}/dist/${P}/** hints and tars all
have the same ${P}-${V}-{R} i.e. mintty-3.0.0-1.
The issue may be, as explained, that 2.9.9-0 is treated as a test release.
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
next prev parent reply other threads:[~2019-03-29 18:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190329180211.86521.99579@sourceware.org>
2019-03-29 18:11 ` Thomas Wolff
2019-03-29 18:26 ` Brian Inglis [this message]
2019-03-29 18:41 ` Jon Turney
[not found] ` <46f4cc2f-7d4e-e252-2c38-edc6528875b5@dronecode.org.uk>
2019-03-29 18:42 ` Thomas Wolff
2019-03-29 19:06 ` Brian Inglis
[not found] <20190328181150.86521.29849@sourceware.org>
2019-03-28 18:27 ` Thomas Wolff
2019-03-28 18:36 ` Achim Gratz
2019-03-28 20:12 ` Corinna Vinschen
2019-03-29 18:42 ` Jon Turney
2019-03-28 18:39 ` Marco Atzeri
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=1ef81318-a573-b64e-306c-5ec0b16a77ce@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--cc=cygwin-apps@cygwin.com \
/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).