public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ryan Hill <rhill@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: Uncoordinated changes
Date: Tue, 16 Feb 2016 16:55:45 -0600	[thread overview]
Message-ID: <20160216165545.4ad457cf@tundra.gateway.pace.com> (raw)
In-Reply-To: CAGfcS_nugLucJy1HxROQAoAm9drOno1r_rt6fWafQBPTNcZ3uw@mail.gmail.com

[-- Attachment #1: Type: text/plain, Size: 1497 bytes --]

On Sun, 14 Feb 2016 10:58:10 -0500
Rich Freeman <rich0@gentoo.org> wrote:

> Well, if debugging is your only concern, on the system you're going to
> debug from:
> touch herds.xml

Don't do that.

rhill@tundra /usr/portage/dev-util/creduce $ repoman

RepoMan scours the neighborhood...
[INFO] checking package dev-util/creduce
Traceback (most recent call last):
  File "/usr/lib/python-exec/python3.4/repoman", line 37, in <module>
    repoman_main(sys.argv[1:])
  File "/usr/lib64/python3.4/site-packages/repoman/main.py", line 104, in
repoman_main qatracker, can_force = scanner.scan_pkgs(can_force)
  File "/usr/lib64/python3.4/site-packages/repoman/scanner.py", line 281, in
scan_pkgs self.pkgmeta.check(xpkg, checkdir, checkdirlist, self.repolevel)
  File
"/usr/lib64/python3.4/site-packages/repoman/checks/ebuilds/pkgmetadata.py",
line 165, in check self.repoman_settings)) File
"/usr/lib64/python3.4/site-packages/repoman/checks/herds/herdbase.py", line
111, in get_herd_base os.path.join(repoman_settings["PORTDIR"],
"metadata/herds.xml")) File
"/usr/lib64/python3.4/site-packages/repoman/checks/herds/herdbase.py", line 73,
in make_herd_base target=_HerdsTreeBuilder())) File
"/usr/lib64/python3.4/xml/etree/ElementTree.py", line 1187, in parse
tree.parse(source, parser) File
"/usr/lib64/python3.4/xml/etree/ElementTree.py", line 605, in parse self._root
= parser.close() xml.etree.ElementTree.ParseError: no element found: line 1,
column 0




-- 

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 951 bytes --]

  reply	other threads:[~2016-02-16 22:56 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-11 20:15 [gentoo-dev] Uncoordinated changes Patrick Lauer
2016-02-12  1:34 ` Rich Freeman
2016-02-12 19:11   ` Paul Varner
2016-02-12  7:48 ` Michał Górny
2016-02-12  9:07   ` Patrick Lauer
2016-02-12 11:16     ` Rich Freeman
2016-02-12 22:02     ` Michał Górny
2016-02-13 21:47       ` Raymond Jennings
2016-02-13 22:44         ` Rich Freeman
2016-02-14  0:58           ` Raymond Jennings
2016-02-14  1:16             ` Rich Freeman
2016-02-14  3:55               ` Raymond Jennings
2016-02-14 10:33               ` [gentoo-dev] herds.xml removal (was: Re: Uncoordinated changes) Ulrich Mueller
2016-02-14 15:30               ` [gentoo-dev] Uncoordinated changes Patrick Lauer
2016-02-14 15:58                 ` Rich Freeman
2016-02-16 22:55                   ` Ryan Hill [this message]
2016-02-17  1:51                     ` [gentoo-dev] " Rich Freeman
2016-02-14 18:30       ` [gentoo-dev] " Patrick Lauer
2016-02-14 11:37 ` Patrick Lauer
2016-02-14 12:18   ` Rich Freeman
2016-02-14 18:44     ` Andreas K. Hüttel
2016-02-14 18:53       ` Patrick Lauer
2016-02-14 18:59         ` Ciaran McCreesh
2016-02-15  3:24         ` Daniel Campbell
2016-02-14 13:15   ` Kent Fredric
2016-02-14 14:37   ` Michał Górny

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=20160216165545.4ad457cf@tundra.gateway.pace.com \
    --to=rhill@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