public inbox for
 help / color / mirror / Atom feed
From: Libor Ukropec <>
Subject: Re: [ITA] duplicity
Date: Tue, 12 Apr 2022 21:24:33 +0200	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Dne 12.04.2022 v 15:10 Jon Turney napsal(a):
> On 12/04/2022 01:09, Libor Ukropec wrote:
>>  > Run cygport ... all with --debug flag which enables shell tracing
>> I'll answer it myself. If the cygport is given the filename *without* 
>> ".cygport" extension, it executes, but wrongly detects the PVR - 
>> NAME/VERSION/RELEASE. When I provided full name, it works as I'd 
>> expected. I think this deserves improvement.
> Yeah, there's some wonkiness in handling that, I'm not sure why.
>>> 1. regarding python-fasteners:
>>> Dne 08.04.2022 v 1:44 Brian Inglis napsal(a):
>>>  > Run cygport ... all with --debug flag which enables shell tracing
>>>  > throughout and redirect all output &> debug.log for review.
>>> Output for command `cygport --debug python-fasteners download all 
>>> check &> debug.log`
>>> is here, if you can deduct from it something useful:
>>> (it is quite long, I do not want to paste it directly into the email)
>>> Also it is unknown to me, how the new repository can be added into 
>>> the;pf=git/cygwin-packages so 
>>> I can execute the tests in the playground too.
> I think this already exists?

It is my fault that I combined two packages into one thread. I want two 
things - adopt duplicity for which the repository already exists (only 
the BUILD_REQUIRES had to be added + version increase) but for the more 
recent duplicity version a new package is required: python-fasteners - 
not yet in the cygwin and here I struggled and didn't know how to add a 
new repository.

For the python-fasteners I'll kick off new "[ITP] python-fasteners 
0.16.3" thread.

> Please keep this up-to-date with your changes.
> I've added you as the maintainer for duplicity, so you should now be 
> able to upload packages and push there.

Thank you, will have to wait for python-fasteners approval.
> Thanks!

  reply	other threads:[~2022-04-12 19:25 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-06 22:10 Libor Ukropec
2022-04-06 23:40 ` Brian Inglis
2022-04-07 19:39   ` Libor Ukropec
2022-04-07 22:26     ` Libor Ukropec
2022-04-07 23:44       ` Brian Inglis
2022-04-10 18:26         ` Libor Ukropec
2022-04-12  0:09           ` Libor Ukropec
2022-04-12 13:10             ` Jon Turney
2022-04-12 19:24               ` Libor Ukropec [this message]
2022-04-12 16:56             ` Achim Gratz

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:

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

  git send-email \ \ \ \

* 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).