public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin-apps@cygwin.com
Subject: Re: git repositories for cygwin packaging - please test
Date: Mon, 16 Nov 2020 15:54:47 -0700	[thread overview]
Message-ID: <c670d8c4-1833-d682-bf1d-43cab2d56738@SystematicSw.ab.ca> (raw)
In-Reply-To: <6fb2aeb0-d68b-40ab-acb9-1586fbf581a5@dronecode.org.uk>

On 2020-11-16 15:16, Jon Turney wrote:
> On 16/11/2020 21:54, Brian Inglis wrote:
>> On 2020-05-27 16:27, Jon Turney wrote:
>>> On 04/08/2019 21:08, Jon Turney wrote:
>>>> To remedy this lack, using the same ssh key you use for sftp package upload, 
>>>> package maintainers can now also push to git repositories, like so:
>>>
>>> Package maintainers may have noticed that the output from pushing to these 
>>> git repositories now includes a line like:
>>>
>>> "remote: scallywag: build nnn queued"
>>>
>>> This is a *prototype* of a system to automatically build the packages, where 
>>> the results appear (some time later) at [1] (URL subject to change)
>>>
>>> [1] https://cygwin.com/cgi-bin2/jobs.cgi
>>
>>> To allow experimentation without messing up the version history unnecessarily:
>>>
>>> - All package repositories allow the maintainer(s) to create, push, rewind 
>>> and delete a branch named 'playground'.
>>>
>>> - An additional package repository called 'playground' exists, that all 
>>> maintainers can do anything to.
>>
>> Could anyone please check and advise if the attached .git/config will allow me 
>> to push to the playground repo and later branch for testing, or demo the 
>> appropriate .git/config entries or git config commands to do so properly?
> 
> To push to the playground repo, I generally just use 'git push 
> ssh://cygwin@cygwin.com/git/cygwin-packages/playground.git -f'.

Thanks, the -f did it, but I've "-f'ed" myself a lot with git, so avoid it.

> The URLs in that config don't look quite right, since they seem to have hostname 
> of just 'cygwin'?

My ~/.ssh/config has "host" names for orgs and systems, but some programs 
(git?/lftp?/sftp?/?) get confused if you use those in other connection strings: 
"what do you mean 'cygwin@cygwin.com@cygwin@cygwin.com.com'", but your git 
command also worked without complaints.

>> Is there any way to move tags to a later commit once pushed?
>> I have one in wget that can't be deleted or forced because of the hook fallthru.
> 
> tags don't have any particular significance, at the moment.
> 
> I removed the wget '1.20.3-2' tag for you.

Cheers, thanks!
I will wait until finished changing and reviews before pushing tags in future.

>> Finally are there other CI jobs.cgi?params=... other than id, e.g. 
>> jobs.cgi?by=Brian+Inglis?
> 
> Not at this time.  I agree it would be nice if you could filter by the various 
> columns.
> 
> The jobs.cgi script script is tiny (see [1]), if you want to make improvements.
> 
> [1] https://cygwin.com/git/?p=cygwin-apps/scallywag.git;a=blob;f=jobs.cgi

Not at this time. Would bloat up your tiny script! ;^>

-- 
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.
[Data in binary units and prefixes, physical quantities in SI.]

  reply	other threads:[~2020-11-16 22:54 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-04 20:08 Jon Turney
2019-08-05  2:03 ` Ken Brown
2019-08-08 13:47 ` Andrew Schulman via cygwin-apps
2019-08-08 14:04 ` Andrew Schulman via cygwin-apps
2019-08-08 17:09   ` Ken Brown
2019-08-09 16:12     ` Jon Turney
2019-08-09 19:12       ` Ken Brown
2019-08-13 11:55         ` Jon Turney
2019-08-09 16:00 ` Jon Turney
2019-08-09 20:58 ` Brian Inglis
2019-08-13 11:55 ` Jon Turney
2019-08-19 18:36 ` Achim Gratz
2020-05-27 22:27 ` Jon Turney
2020-05-28 11:51   ` szgyg
2020-06-04 16:01   ` Ken Brown
2020-06-04 20:33     ` Brian Inglis
2020-06-09 13:26       ` Jon Turney
2020-06-09 22:44         ` Brian Inglis
2020-08-06 20:20   ` Jon Turney
2020-08-06 21:04     ` Ken Brown
2020-08-07 19:42     ` Achim Gratz
2020-08-07 22:05       ` Ken Brown
2020-08-08  4:26         ` ASSI
2020-08-16 18:05         ` Jon Turney
2020-08-23 21:01   ` Jon Turney
2020-08-26 22:00     ` Ken Brown
2020-08-30 15:00       ` Jon Turney
2020-08-30 15:22         ` Ken Brown
2020-08-30 15:46           ` Jon Turney
2020-08-30 17:25             ` Ken Brown
2020-08-30 20:06               ` Jon Turney
2020-11-12 21:30             ` Jon Turney
2020-08-30 16:44         ` ASSI
2020-08-30 20:08           ` Jon Turney
2020-10-04 10:26           ` Achim Gratz
2020-10-25 18:10             ` Jon Turney
2021-05-09 14:39     ` Jon Turney
2021-06-22 19:52       ` Jon Turney
2021-06-23  4:22         ` Brian Inglis
2022-07-05 13:12         ` Jon Turney
2023-02-18 16:21           ` Jon Turney
2023-02-18 17:43             ` Ken Brown
2023-02-18 18:40               ` Jon Turney
2020-11-16 21:54   ` Brian Inglis
2020-11-16 22:16     ` Jon Turney
2020-11-16 22:54       ` Brian Inglis [this message]
2020-11-17 19:21     ` Achim Gratz
2020-05-29 14:40 ` Alexey Sokolov
2020-06-07 15:06   ` Hamish McIntyre-Bhatty

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=c670d8c4-1833-d682-bf1d-43cab2d56738@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).