Mark Geisert writes:
> I'd like to re-spin the latest version of cygutils, that is, upload
> newer files with the same release number (1.4.16-5). Is this
> possible, or do we now always change the release# when uploading?
Re-spin == re-release, so you need to increase the release number.
Test
On Sat, 28 Aug 2021 at 09:09, Mark Geisert wrote:
>
> HI all,B
> I'd like to re-spin the latest version of cygutils, that is, upload newer
> files with the same release number (1.4.16-5). Is this possible, or do we
> now always change the release# when uploading?
> Thanks,
I'm pretty sure this
HI all,B
I'd like to re-spin the latest version of cygutils, that is, upload newer
files with the same release number (1.4.16-5). Is this possible, or do we
now always change the release# when uploading?
Thanks,
..mark
On 18/10/2020 18:44, Brian Inglis wrote:
On 2020-10-17 09:52, Brian Inglis wrote:
Could be due to problems with cygwin-git-package pushes, but I have a few
updated packages to upload, and cygport uploads are now failing:
Hi folks,
Something else going on here since successful tzcode, tzdata
On 2020-10-17 09:52, Brian Inglis wrote:
> Could be due to problems with cygwin-git-package pushes, but I have a few
> updated packages to upload, and cygport uploads are now failing:
Hi folks,
Something else going on here since successful tzcode, tzdata uploads!
Trying to upload curl packages
Could be due to problems with cygwin-git-package pushes, but I have a few
updated packages to upload, and cygport uploads are now failing:
$ cygport tzcode.cygport upload
>>> Uploading tzcode-2020c-1.x86_64
>>> Running lftp sftp://cygwin:@cygwin.com
cd: Fatal error: max-retries exceeded
> > OK, works. Can lftp or cygport be configured so that lftp does not ask
> > for a password? Or to use sftp instead?
>
> I don't know of any configuration for lftp to turn off that behaviour
> (which is arguably a defect in lftp), but that's probably something you
> could investigate for
chrieb Jon Turney:
>>>>>> On 27/03/2020 10:17, Thomas Wolff wrote:
>>>>>>> How does cygport upload work?
>>>>>>> I previously uploaded with sftp but cygport apparently runs lftp and it
>>>>>>> asks me for a passwor
Am 27.03.2020 um 17:27 schrieb Jon Turney:
On 27/03/2020 16:15, Thomas Wolff wrote:
Am 27.03.2020 um 16:41 schrieb Jon Turney:
On 27/03/2020 14:35, Thomas Wolff wrote:
Am 27.03.2020 um 13:21 schrieb Jon Turney:
On 27/03/2020 10:17, Thomas Wolff wrote:
How does cygport upload work?
I
On 27/03/2020 16:15, Thomas Wolff wrote:
Am 27.03.2020 um 16:41 schrieb Jon Turney:
On 27/03/2020 14:35, Thomas Wolff wrote:
Am 27.03.2020 um 13:21 schrieb Jon Turney:
On 27/03/2020 10:17, Thomas Wolff wrote:
How does cygport upload work?
I previously uploaded with sftp but cygport
Am 27.03.2020 um 16:41 schrieb Jon Turney:
On 27/03/2020 14:35, Thomas Wolff wrote:
Am 27.03.2020 um 13:21 schrieb Jon Turney:
On 27/03/2020 10:17, Thomas Wolff wrote:
How does cygport upload work?
I previously uploaded with sftp but cygport apparently runs lftp
and it asks me for a password
On 27/03/2020 14:35, Thomas Wolff wrote:
Am 27.03.2020 um 13:21 schrieb Jon Turney:
On 27/03/2020 10:17, Thomas Wolff wrote:
How does cygport upload work?
I previously uploaded with sftp but cygport apparently runs lftp and
it asks me for a password.
This just seems to be a thing lftp does
Am 27.03.2020 um 13:21 schrieb Jon Turney:
On 27/03/2020 10:17, Thomas Wolff wrote:
How does cygport upload work?
I previously uploaded with sftp but cygport apparently runs lftp and
it asks me for a password.
This just seems to be a thing lftp does.
If the key isn't coming from ssh-agent
On 27/03/2020 10:17, Thomas Wolff wrote:
How does cygport upload work?
I previously uploaded with sftp but cygport apparently runs lftp and it
asks me for a password.
This just seems to be a thing lftp does.
If the key isn't coming from ssh-agent, it always asks for a passphrase.
If the key
How does cygport upload work?
I previously uploaded with sftp but cygport apparently runs lftp and it
asks me for a password.
Thomas
On Mon, 2015-06-01 at 04:04 -0400, Andrew Schulman wrote:
A more precise regex is
[0-9a-f]{2}(:[0-9a-f]{2}){15}|SHA256:[A-Za-z0-9+/=]{43}
I've committed this change to my upload branch at
https://github.com/andrex-e-schulman/cygport.git.
Also in that branch, I've added
Any thoughts on a better regex or on keeping compatibility with other
systems?
Right, OK. See the attached revised patch, which uses
[0-9a-f]{2}(:[0-9a-f]{2}){15}|SHA256:.{44}
to detect the key fingerprint. The left side is the same as now, for pre-6.8
systems, which use MD5
On Sun, 2015-05-24 at 12:32 -0400, Andrew Schulman wrote:
Since the latest update to openssh, ssh-keygen's output format for key
fingerprints has changed. The default hash algorithm is now base64-encoded
SHA256 instead of MD5, and the hash name precedes its value, like
On Sun, 2015-05-24 at 12:32 -0400, Andrew Schulman wrote:
Since the latest update to openssh, ssh-keygen's output format for key
fingerprints has changed. The default hash algorithm is now base64-encoded
SHA256 instead of MD5, and the hash name precedes its value, like
Since the latest update to openssh, ssh-keygen's output format for key
fingerprints has changed. The default hash algorithm is now base64-encoded
SHA256 instead of MD5, and the hash name precedes its value, like
SHA256:lvRrjAXmEhzDp5kQqzelsei8s5hXJ+zLaqJ2yiGXmYc
This breaks the current
I have created an upload branch in cygport git based on master with
Andrew's upload work for further testing.
I'm still undecided on $arch/!ready vs. $arch/release/$package/!ready.
Thoughts?
--
Yaakov
On 2/12/2015 11:42 PM, Yaakov Selkowitz wrote:
I have created an upload branch in cygport git based on master with
Andrew's upload work for further testing.
I'm still undecided on $arch/!ready vs. $arch/release/$package/!ready.
Thoughts?
$arch/release/$package/!ready
should avoid the
On 2/12/2015 11:42 PM, Yaakov Selkowitz wrote:
I have created an upload branch in cygport git based on master with
Andrew's upload work for further testing.
I'm still undecided on $arch/!ready vs. $arch/release/$package/!ready.
Thoughts?
$arch/release/$package/!ready
should avoid
I have created an upload branch in cygport git based on master with
Andrew's upload work for further testing.
FWIW, I've been using it to upload my packages since the last update on Jan. 17,
and before that too, with no problems.
I always keep my ssh keys loaded in a running ssh-agent, so I've
On Thu, 2015-02-12 at 20:23 -0500, Andrew Schulman wrote:
I have created an upload branch in cygport git based on master with
Andrew's upload work for further testing.
FWIW, I've been using it to upload my packages since the last update on Jan.
17,
and before that too, with no problems.
busy at the moment, but it sounds like a good idea to me.
I have an implementation of this ready at
https://github.com/andrex-e-schulman/cygport. What's new compared to
upstream git:
* New upload command (cygport up).
Minor nit: This should be `cygport upload' to be in line with the
other
Minor nit: This should be `cygport upload' to be in line with the
other cygport commands. Alternatively, cygport could introduce a
two-letter abbreviation scheme, for instance:
cygport download- cygport dl or (rcs-like) co
cygport prep- cygport pr
On 2014-07-07 20:14, Andrew Schulman wrote:
Yaakov, would you consider adding an 'upload' command to cygport, that
would handle the uploading details? That would take away the last bit of
manual work in a routine package update.
I'm a bit busy at the moment, but it sounds like a good
On 2014-07-07 20:14, Andrew Schulman wrote:
Using cygport, I think that packaging has become quite easy now.
That's always been my goal. :-)
Except for one thing: the upload step. Maintainers still have to go
through the procedure at
https://sourceware.org/cygwin-apps/package-upload.html.
Using cygport, I think that packaging has become quite easy now. At least,
once the cygport script is built and working, updating a package to a new
release is as easy as updating the version number in the cygport script,
then running 'cygport ... download all'.
Except for one thing: the upload
On Mon, Jul 07, 2014 at 09:14:29PM -0400, Andrew Schulman wrote:
Using cygport, I think that packaging has become quite easy now. At least,
once the cygport script is built and working, updating a package to a new
release is as easy as updating the version number in the cygport script,
then
31 matches
Mail list logo
