-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 01/28/2016 11:52 AM, John Florian wrote:
Oh, now my light bulb has a glow, dim it may be but it's not
utter
darkness any more. Tags in general in Koji are hard to understand
since they can take on so many uses.
Let's start from scratch. Here's what I am hoping to accomplish:
All builds initially are dumped into fN-candidates. These get
mashed into a repo, but I rarely use it -- it's mostly proof the
build can succeed at all. (Though, I'm now becoming aware of
scratch/test builds from HEAD via Koji so perhaps fN-candidates is
unnecessary.) If I want to actually try a build out, I "promote"
it by untagging from fN-candidates and tagging it with fN-testing.
If functional testing proves it good, then I'll promote again by
untagging from fn-testing and tagging with fN-released.
In the Fedora Project sense, I don't have any distinction between
"base" and "updates". They're effectively squashed into my
fN-released as we've no need for anything but the newest
functionally tested version.
So, if IUYC, I should have my fN-build inherit from fN-released.
Am I correct?
Will I be able to change my inheritance hierarchy for f21 & f22 or
will I have to wait and change my model once I start supporting
f23? -- buildsys mailing list buildsys(a)lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/buildsys@lists.fedoraproject.org
Can you list the inheritance of your various tags without the
- --reverse argument?
- - Jay
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.14 (GNU/Linux)
iQEcBAEBAgAGBQJWqkhuAAoJEMzORChHoQ3aHPQIAMWR8cZ3o7JPSX75PGmvGnls
6a7pzb6FMR3TjOFvf19moy5NH1hXcVXbkb+EdrtySrV3X4UZnerYGOI2OZaOct6q
Th//y6rphN7ZwiQOPfjH3iM2i6LHEu4BmmG6Ivu6NAO1rvCk+TNqAccbQFJq+mGo
p0WvZt+1MUEYQN5gqg/YxDfiqLxkDdAOA7Y2EmYfRLzjmms5ePkwhSIEAf6oQMsW
EeOJXlVu9xQN5LA3qW1BZ/QGqXVbXLdzJJJcmL91Z/zlrZwkqK/CY97LjeTsAIxp
827od8vaLB1U7+YF3uV8aSAhSiKMFGSXGE8d5UZcxN6ABksGP72V48InBhz9AaA=
=fZ68
-----END PGP SIGNATURE-----