From: "Fabian Groffen" <grobian@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/portage:prefix commit in: pym/portage/
Date: Thu, 1 Mar 2012 20:32:44 +0000 (UTC) [thread overview]
Message-ID: <1330633872.86fd28940bd83d1f59622adc90cf79712b061952.grobian@gentoo> (raw)
commit: 86fd28940bd83d1f59622adc90cf79712b061952
Author: Lucian Poston <lucianposton <AT> gmail <DOT> com>
AuthorDate: Thu Mar 1 20:31:12 2012 +0000
Commit: Fabian Groffen <grobian <AT> gentoo <DOT> org>
CommitDate: Thu Mar 1 20:31:12 2012 +0000
URL: http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commit;h=86fd2894
_get_global: reference correct variable
---
pym/portage/data.py | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/pym/portage/data.py b/pym/portage/data.py
index be0c853..23734f4 100644
--- a/pym/portage/data.py
+++ b/pym/portage/data.py
@@ -115,7 +115,7 @@ def _get_global(k):
portage_gid = 0
# PREFIX LOCAL: we need to fix this one day to distinguish prefix vs non-prefix
writemsg(colorize("BAD",
- _("portage: '%s' user or '%s' group missing." % (_get_global('_portage_uname'), _get_global('_portage_grpname')))) + "\n", noiselevel=-1)
+ _("portage: '%s' user or '%s' group missing." % (_get_global('_portage_username'), _get_global('_portage_grpname')))) + "\n", noiselevel=-1)
writemsg(colorize("BAD",
_(" In Prefix Portage this is quite dramatic")) + "\n", noiselevel=-1)
writemsg(colorize("BAD",
next reply other threads:[~2012-03-01 20:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-01 20:32 Fabian Groffen [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-05-18 19:46 [gentoo-commits] proj/portage:prefix commit in: pym/portage/ Fabian Groffen
2017-12-12 8:13 Fabian Groffen
2013-01-27 21:51 Fabian Groffen
2012-10-02 11:59 Fabian Groffen
2012-09-30 11:10 Fabian Groffen
2012-09-30 11:10 Fabian Groffen
2012-01-18 7:58 Fabian Groffen
2011-12-14 15:29 Fabian Groffen
2011-12-10 12:55 Fabian Groffen
2011-12-10 12:12 Fabian Groffen
2011-12-10 12:06 Fabian Groffen
2011-12-09 20:39 Fabian Groffen
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=1330633872.86fd28940bd83d1f59622adc90cf79712b061952.grobian@gentoo \
--to=grobian@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