From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/portage:master commit in: pym/portage/sync/modules/svn/
Date: Sun, 18 Jan 2015 18:04:33 +0000 (UTC) [thread overview]
Message-ID: <1421604265.7ca0672d4c95d2e07885460eee9ed41e882faf9f.mgorny@gentoo> (raw)
commit: 7ca0672d4c95d2e07885460eee9ed41e882faf9f
Author: Michał Górny <mgorny <AT> gentoo <DOT> org>
AuthorDate: Sat Jan 17 17:13:09 2015 +0000
Commit: Michał Górny <mgorny <AT> gentoo <DOT> org>
CommitDate: Sun Jan 18 18:04:25 2015 +0000
URL: http://sources.gentoo.org/gitweb/?p=proj/portage.git;a=commit;h=7ca0672d
svn sync: fix the module
Fix the svn sync module since it doesn't work at all right now. More
specifically:
1. add exists() method that checks for the '.svn' directory to determine
whether the repository was checked out already.
2. Fix the initial clone to use valid svn commands. Do not remove
the just-created (in pre_sync()) directory to avoid permission issues,
just run checkout on top of it.
3. Fix the sync method to run update unconditionally to whether the URI
starts with svn:// or not. In fact, remove the whole check since it
doesn't serve any purpose.
---
pym/portage/sync/modules/svn/svn.py | 42 +++++++++++++++----------------------
1 file changed, 17 insertions(+), 25 deletions(-)
diff --git a/pym/portage/sync/modules/svn/svn.py b/pym/portage/sync/modules/svn/svn.py
index 73c4b83..60ead4b 100644
--- a/pym/portage/sync/modules/svn/svn.py
+++ b/pym/portage/sync/modules/svn/svn.py
@@ -24,23 +24,19 @@ class SVNSync(SyncBase):
SyncBase.__init__(self, "svn", "dev-vcs/subversion")
+ def exists(self, **kwargs):
+ '''Tests whether the repo actually exists'''
+ return os.path.exists(os.path.join(self.repo.location, '.svn'))
+
+
def new(self, **kwargs):
if kwargs:
self._kwargs(kwargs)
#initial checkout
- try:
- os.rmdir(self.repo.location)
- except OSError as e:
- if e.errno != errno.ENOENT:
- msg = "!!! existing '%s' directory; exiting." % self.repo.location
- self.logger(self.xterm_titles, msg)
- writemsg_level(msg + "\n", noiselevel=-1, level=logging.ERROR)
- return (1, False)
- del e
svn_root = self.repo.sync_uri
- exitcode = portage.process.spawn_bash(
- "cd %s; exec svn %s" %
- (portage._shell_quote(os.path.dirname(self.repo.location)),
+ exitcode = portage.process.spawn_bash(
+ "cd %s; exec svn co %s ." %
+ (portage._shell_quote(self.repo.location),
portage._shell_quote(svn_root)),
**portage._native_kwargs(self.spawn_kwargs))
if exitcode != os.EX_OK:
@@ -63,19 +59,15 @@ class SVNSync(SyncBase):
if exitcode != os.EX_OK:
return (exitcode, False)
- svn_root = self.repo.sync_uri
-
- if svn_root.startswith("svn://"):
- svn_root = svn_root[6:]
- #svn update
- exitcode = portage.process.spawn_bash(
- "cd %s; exec svn update" % \
- (portage._shell_quote(self.repo.location),),
- **portage._native_kwargs(self.spawn_kwargs))
- if exitcode != os.EX_OK:
- msg = "!!! svn update error; exiting."
- self.logger(self.xterm_titles, msg)
- writemsg_level(msg + "\n", noiselevel=-1, level=logging.ERROR)
+ #svn update
+ exitcode = portage.process.spawn_bash(
+ "cd %s; exec svn update" % \
+ (portage._shell_quote(self.repo.location),),
+ **portage._native_kwargs(self.spawn_kwargs))
+ if exitcode != os.EX_OK:
+ msg = "!!! svn update error; exiting."
+ self.logger(self.xterm_titles, msg)
+ writemsg_level(msg + "\n", noiselevel=-1, level=logging.ERROR)
return (exitcode, False)
next reply other threads:[~2015-01-18 18:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-18 18:04 Michał Górny [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-12-04 20:16 [gentoo-commits] proj/portage:master commit in: pym/portage/sync/modules/svn/ Brian Dolbec
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=1421604265.7ca0672d4c95d2e07885460eee9ed41e882faf9f.mgorny@gentoo \
--to=mgorny@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.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