From: David Stacey <drstacey@tiscali.co.uk>
To: cygwin-apps@cygwin.com
Subject: Re: calm: Unable to upload poco-1.7.5
Date: Wed, 07 Sep 2016 23:15:00 -0000 [thread overview]
Message-ID: <7dc20c28-38fd-6331-bc1c-78c8bb09db5e@tiscali.co.uk> (raw)
In-Reply-To: <fab20eb3-e70b-b975-9ceb-fd47793e0447@dronecode.org.uk>
On 07/09/16 22:47, Jon Turney wrote:
> On 07/09/2016 19:30, David Stacey wrote:
>> I'm trying to upload poco-1.7.5 and delete poco-1.6.1-2. Part of this
>> involves removing the directory libpoco31, as there has been an ABI
>> bump, and this is where I'm failing.
>>
>> I've tried creating empty '-libpoco31-1.6.1-2.tar.xz' and '-setup.hint'
>> files (in a bid to delete both), but calm won't let me remove a
>> setup.hint file. So I tried a setup.hint just containing 'skip:' and
>> deleting the lib package as before, but that didn't work. Finally, I
>> tried creating a '-libpoco31' directory, but calm wouldn't take that
>> either.
>>
>> Please could you advise how I should delete older 'lib' sub-packages
>> that are no longer required.
>
> Sorry for the inconvenience.
>
> At the moment, there is no good way of completely removing a package,
> even when nothing depends on it.
>
> For the moment, if you leave libpoco31-1.6.1-2 and the corresponding
> source-package alone, you should be able to proceed with your upload.
>
> I'll make a note to clean up libpoco31 when the 'good way' of doing
> that is implemented.
Thank you for your help, Jon. I've done as you requested, leaving
libpoco31-1.6.1-2 and its source package behind. These can be removed
the next time someone has a tidy up.
>> Secondly, I'm trying to upload the noarch package 'poco-doc'. calm isn't
>> taking this, despite creating a '/noarch/!ready' file. I'm not getting
>> any helpful message from calm regarding this one - it eats the !ready
>> cookie, but doesn't upload the files. I've obviously made some mistake
>> with this one, but I can't spot it.
>
> It looks like these were not moved as that was part of the save calm
> run as your other failures above.
>
> calm will not move any of your uploaded package if there is a problem
> with any of them (it seems that to do otherwise could lead to an
> unexpected package set)
OK, thanks for clarifying.
> I set this to be re-tried and it seems to have succeeded.
Thanks for giving it a poke. Yes, I confirm that it has been uploaded.
Dave.
prev parent reply other threads:[~2016-09-07 23:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-07 18:30 David Stacey
2016-09-07 21:48 ` Jon Turney
2016-09-07 23:15 ` David Stacey [this message]
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=7dc20c28-38fd-6331-bc1c-78c8bb09db5e@tiscali.co.uk \
--to=drstacey@tiscali.co.uk \
--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).