public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Justin Lecher (jlec)" <jlec@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] gentoo-x86 commit in dev-python/unidecode: metadata.xml ChangeLog
Date: Thu,  4 Jun 2015 07:28:41 +0000 (UTC)	[thread overview]
Message-ID: <20150604072841.55DA4A19@oystercatcher.gentoo.org> (raw)

jlec        15/06/04 07:28:41

  Modified:             metadata.xml ChangeLog
  Log:
  Add pypi to remote-id in metadata.xml
  
  (Portage version: 2.2.20/cvs/Linux x86_64, signed Manifest commit with key E9402A79B03529A2!)

Revision  Changes    Path
1.7                  dev-python/unidecode/metadata.xml

file : http://sources.gentoo.org/viewvc.cgi/gentoo-x86/dev-python/unidecode/metadata.xml?rev=1.7&view=markup
plain: http://sources.gentoo.org/viewvc.cgi/gentoo-x86/dev-python/unidecode/metadata.xml?rev=1.7&content-type=text/plain
diff : http://sources.gentoo.org/viewvc.cgi/gentoo-x86/dev-python/unidecode/metadata.xml?r1=1.6&r2=1.7

Index: metadata.xml
===================================================================
RCS file: /var/cvsroot/gentoo-x86/dev-python/unidecode/metadata.xml,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- metadata.xml	13 Apr 2015 08:28:42 -0000	1.6
+++ metadata.xml	4 Jun 2015 07:28:41 -0000	1.7
@@ -8,4 +8,7 @@
   <longdescription lang="en">
 This is a Python port of the Text::Unidecode Perl (<pkg>dev-perl/Text-Unidecode</pkg> module
 </longdescription>
+  <upstream>
+    <remote-id type="pypi">Unidecode</remote-id>
+  </upstream>
 </pkgmetadata>



1.40                 dev-python/unidecode/ChangeLog

file : http://sources.gentoo.org/viewvc.cgi/gentoo-x86/dev-python/unidecode/ChangeLog?rev=1.40&view=markup
plain: http://sources.gentoo.org/viewvc.cgi/gentoo-x86/dev-python/unidecode/ChangeLog?rev=1.40&content-type=text/plain
diff : http://sources.gentoo.org/viewvc.cgi/gentoo-x86/dev-python/unidecode/ChangeLog?r1=1.39&r2=1.40

Index: ChangeLog
===================================================================
RCS file: /var/cvsroot/gentoo-x86/dev-python/unidecode/ChangeLog,v
retrieving revision 1.39
retrieving revision 1.40
diff -u -r1.39 -r1.40
--- ChangeLog	13 Apr 2015 08:28:42 -0000	1.39
+++ ChangeLog	4 Jun 2015 07:28:41 -0000	1.40
@@ -1,6 +1,9 @@
 # ChangeLog for dev-python/unidecode
 # Copyright 1999-2015 Gentoo Foundation; Distributed under the GPL v2
-# $Header: /var/cvsroot/gentoo-x86/dev-python/unidecode/ChangeLog,v 1.39 2015/04/13 08:28:42 jlec Exp $
+# $Header: /var/cvsroot/gentoo-x86/dev-python/unidecode/ChangeLog,v 1.40 2015/06/04 07:28:41 jlec Exp $
+
+  04 Jun 2015; Justin Lecher <jlec@gentoo.org> metadata.xml:
+  Add pypi to remote-id in metadata.xml
 
   13 Apr 2015; Justin Lecher <jlec@gentoo.org> -unidecode-0.04.16.ebuild,
   metadata.xml:





             reply	other threads:[~2015-06-04  7:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-04  7:28 Justin Lecher (jlec) [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-01-16 17:20 [gentoo-commits] gentoo-x86 commit in dev-python/unidecode: metadata.xml ChangeLog Jeroen Roovers (jer)
2013-10-20 19:25 Stanislav Ochotnicky (sochotnicky)

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=20150604072841.55DA4A19@oystercatcher.gentoo.org \
    --to=jlec@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