public inbox for cygwin-apps-cvs@sourceware.org
help / color / mirror / Atom feed
From: Jon Turney <jturney@sourceware.org>
To: cygwin-apps-cvs@sourceware.org
Subject: [calm - Cygwin server-side packaging maintenance script] branch master, updated. 20230209-5-gb3b21d1
Date: Sun, 12 Feb 2023 19:09:54 +0000 (GMT)	[thread overview]
Message-ID: <20230212190954.5E1EB3858D1E@sourceware.org> (raw)




https://sourceware.org/git/gitweb.cgi?p=cygwin-apps/calm.git;h=b3b21d19d11cd8bec59f803131d7e6f22a42df1b

commit b3b21d19d11cd8bec59f803131d7e6f22a42df1b
Author: Jon Turney <jon.turney@dronecode.org.uk>
Date:   Sun Feb 12 12:36:57 2023 +0000

    Improve hint parser error for embedded double quote

https://sourceware.org/git/gitweb.cgi?p=cygwin-apps/calm.git;h=a3f8b56cee6f20db1298cf60cf7c968999483752

commit a3f8b56cee6f20db1298cf60cf7c968999483752
Author: Jon Turney <jon.turney@dronecode.org.uk>
Date:   Tue Feb 7 15:14:46 2023 +0000

    Give deploy status feedback into scallywag
    
    Also: isolate each individual deploy, by putting them in a subdirectory
    of stagingdir named after the job id.

https://sourceware.org/git/gitweb.cgi?p=cygwin-apps/calm.git;h=573e4d526dad7bc8c417d6313b356208d71c752f

commit 573e4d526dad7bc8c417d6313b356208d71c752f
Author: Jon Turney <jon.turney@dronecode.org.uk>
Date:   Mon Feb 6 15:49:48 2023 +0000

    Always remove files from stagingdir
    
    We want different treatment for files which are manually uploaded (into
    homedir) and files which arrive from the build service deployer (into
    stagingdir)
    
    Broken manual uploads were left in place so they can be inspected and
    manually fixed by someone.
    
    Currently, broken build deploys will also hang around forever, but they
    are expected to be "correct", and the initator of the build has no
    access to the stagingdir to fix things. Instead make them get
    automatically removed.

https://sourceware.org/git/gitweb.cgi?p=cygwin-apps/calm.git;h=2f302f55238672b84e7dd1f960043d67a18ea91c

commit 2f302f55238672b84e7dd1f960043d67a18ea91c
Author: Jon Turney <jon.turney@dronecode.org.uk>
Date:   Tue Jan 17 14:39:07 2023 +0000

    Revise maintainers module
    
    The data ordered by package name is the one we use the most often, so
    make that the primary form.
    
    Also use mtime_cache for the result of parsing cygwin-pkg-maint.
    
    v2:
    Fix mkgitolite and reports
    
    Keep maintainers in a list, not a set, because we need "first named
    maintainer".


Diff:
---


                 reply	other threads:[~2023-02-12 19:09 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20230212190954.5E1EB3858D1E@sourceware.org \
    --to=jturney@sourceware.org \
    --cc=cygwin-apps-cvs@sourceware.org \
    /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).