public inbox for cygwin-apps-cvs@sourceware.org
help / color / mirror / Atom feed
From: jturney@sourceware.org
To: cygwin-apps-cvs@sourceware.org
Subject: [calm - Cygwin server-side packaging maintenance script] branch master, updated. bc6fd68b03e262b18b5dc6079fb609ac0b181e84
Date: Wed, 23 Mar 2016 13:09:00 -0000	[thread overview]
Message-ID: <20160323130909.54626.qmail@sourceware.org> (raw)




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

commit bc6fd68b03e262b18b5dc6079fb609ac0b181e84
Author: Jon Turney <jon.turney@dronecode.org.uk>
Date:   Wed Mar 23 10:26:55 2016 +0000

    Ignore packages marked as OBSOLETE in cygwin-pkg-maint
    
    Update tests appropriately

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

commit e7eb9c334ff2db9b4a622959b74126d5880ef52d
Author: Jon Turney <jon.turney@dronecode.org.uk>
Date:   Mon Mar 21 20:37:40 2016 +0000

    Remove shell script, do everything in python
    
    Have I mentioned lately how much I hate shell scripts...
    
    v2:
    Backup existing .ini file, rather than overwriting it
    Add an option to control where we look for setup executable
    
    v3:
    Use shutil.move rather than os.rename for case when /tmp isn't on the
    same filesystem as release area


Diff:
---
 calm.py |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/calm.py b/calm.py
index 6cbc690..f1b6b2d 100755
--- a/calm.py
+++ b/calm.py
@@ -185,7 +185,7 @@ def main(args):
 
                     # replace setup.ini
                     logging.warning("moving %s to %s" % (tmpfile.name, inifile))
-                    os.rename(tmpfile.name, inifile)
+                    shutil.move(tmpfile.name, inifile)
 
                     # compress and re-sign
                     for ext in ['.ini', '.bz2']:


                 reply	other threads:[~2016-03-23 13: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=20160323130909.54626.qmail@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).