From: Zac Medico <zmedico@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] repoman - I cannot handle it...
Date: Sat, 20 Oct 2007 11:47:16 -0700 [thread overview]
Message-ID: <471A4D34.3070205@gentoo.org> (raw)
In-Reply-To: <200710201445.56961.corsair@gentoo.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Markus Rothe wrote:
> So if I want to mark for example sys-devel/gcc-4.1.2 stable on ppc64 I call
> mp.sh like this: mp.sh ppc64 sys-devel/gcc-4.1.2 "Stable on ppc64"
If that mp.sh script fails then you have keyworded an ebuild but it
hasn't been committed. If you're cvs tree is left in that state and
you move on to other packages, repoman will see those keywords in
it's dependency checks it treat them the same as if they had really
been committed, which can lead to invalid results. Perhaps your
mp.sh script should clean up after itself if the commit fails.
Zac
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.7 (GNU/Linux)
iD8DBQFHGk0z/ejvha5XGaMRArk9AJ42vBDcYe1eayhWRAaTNB5Fgop1FgCfU9yg
vqENF1g6ZoKw0sq99k8ZJmY=
=HleO
-----END PGP SIGNATURE-----
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2007-10-20 19:00 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-20 12:45 [gentoo-dev] repoman - I cannot handle it Markus Rothe
2007-10-20 18:47 ` Zac Medico [this message]
2007-10-20 21:35 ` Markus Rothe
2007-10-20 21:55 ` Jeroen Roovers
2007-10-21 18:49 ` Markus Rothe
2007-10-21 21:42 ` [gentoo-dev] " Christian Faulhammer
2007-10-21 19:06 ` [gentoo-dev] " Ciaran McCreesh
2007-10-22 1:06 ` Jeroen Roovers
2007-10-22 1:18 ` Ciaran McCreesh
2007-10-21 10:44 ` [gentoo-dev] " Steve Long
2007-10-21 11:35 ` Marius Mauch
2007-10-21 13:08 ` Marijn Schouten (hkBst)
2007-10-21 14:49 ` Elias Pipping
2007-10-21 22:13 ` [gentoo-dev] " Steve Long
2007-10-22 1:36 ` Marius Mauch
2007-10-22 1:47 ` Ciaran McCreesh
2007-10-22 7:24 ` [gentoo-dev] " Steve Long
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=471A4D34.3070205@gentoo.org \
--to=zmedico@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