mohanboddu added a new comment to an issue you are following:
``
>>Jan 12 09:44:50 <lsedlar> mboddu, question about
https://pagure.io/releng/issue/7227 new repositories for modular[-updates[-testing]]: what
is the pungi work needed? meeting minutes says there should be something in progress, but
I'm not aware of anything
Jan 12 09:44:57 <fm-releng> pungi.compose.status.change -- pungi-koji compose
of Fedora-26-updates-testing-20180112.0 started
https://kojipkgs.fedoraproject.org/compose/updates/Fedora-26-updates-test...
Jan 12 09:45:23 <fm-releng> pungi.compose.status.change -- pungi-koji compose of
Fedora-27-updates-testing-20180112.0 started
https://kojipkgs.fedoraproject.org/compose/updates/Fedora-27-updates-test...
Jan 12 09:45:36 <+mboddu> lsedlar: puiterwijk told me about it
Jan 12 09:45:45 «--- praiskup (praiskup@nat/redhat/x-monfxamldrtsaagv) has Quit (Quit:
Leaving)
Jan 12 09:45:49 <+mboddu> puiterwijk: ^ any idea?
Jan 12 09:46:14 »» +mboddu wonders if I understood it wrong and goes back and checks
Jan 12 09:46:24 <puiterwijk> lsedlar: I was told by dgilmore that the modularity
folks are working on new patches to make mixed traditional/modular repos
Jan 12 09:48:39 <lsedlar> puiterwijk, thanks, I know about the mixing work, just did
not realize it would be a solution for this ticket
Jan 12 09:49:05 <puiterwijk> lsedlar: Well, it wasmore that if we want to build new
repo contents, we need a tool to generate those repos.
Jan 12 09:49:17 <puiterwijk> I'm not going to build repos by hand...
Jan 12 09:49:57 <fm-releng> pagure.issue.new -- sharkcz opened a new ticket
releng#7264: "failed composes due content of the ppc64/ppc64le installer image bigger
than 2GB"
https://pagure.io/releng/issue/7264
Jan 12 09:50:03 <lsedlar> puiterwijk, my initial understanding was that it should
use the existing modular composes, just ship them to a different location
Jan 12 09:50:15 ---» jamesturner246 (~jamesturn(a)lancing.inf.susx.ac.uk) has Joined
#fedora-releng
Jan 12 09:50:33 <puiterwijk> lsedlar: oh. That isn't the feeling I got from when
Matthew explained it, so I might've misunderstood things there
Jan 12 09:50:47 <puiterwijk> Basically, they said they wanted it mixed in with the
standard repos.
Jan 12 09:51:16 <puiterwijk> lsedlar: So what you're saying is that they want
the xact same repos that Bodhi's been able to generate for a while now, just in a
different location?
Jan 12 09:52:13 <lsedlar> puiterwijk, maybe not, I don't know; the way you
describe it would also be possibility
Jan 12 09:52:40 <puiterwijk> If they want the same repos as we have just in a
different place, that's trivial.
Jan 12 09:52:59 <puiterwijk> And actually, looking at the examples Matthew provided,
that might be what they want...
Jan 12 09:53:01
<puiterwijk> fedora/linux/releases/28/Everything/x86_64/os/Packages
Jan 12 09:53:03
<puiterwijk> fedora/linux/releases/28/Everything/x86_64/modular/Packages
Jan 12 09:53:28 <jkaluza> puiterwijk: they need to get some RPMs from classic fedora
koji_tag and on top of that use some RPMs from a module
Jan 12 09:53:33 <jkaluza> modules
Jan 12 09:53:42 <puiterwijk> jkaluza: in the same yum repos? Or to the side?
Jan 12 09:53:43 <jkaluza> puiterwijk: those from modules should replace the ones
which are in fedora koji tag
Jan 12 09:53:48 <jkaluza> puiterwijk: in the same repo
Jan 12 09:53:54 <puiterwijk> jkaluza: okay, then we need the pungi work
Jan 12 09:53:58 <jkaluza> contyk: ^ am I right?
Jan 12 09:54:19 <puiterwijk> Since right now we can only generate fully-traditional
or fully-modular repos, nothing with "traditional except where it's in a
module"
Jan 12 09:54:29 <jkaluza> not a true I think, there is that hybrid compose
Jan 12 09:54:44 <jkaluza> but according to contyk there are some problems with it,
but I already forgot what exactly
Jan 12 09:54:59 »» contyk reads the backlog
Jan 12 09:55:02 <puiterwijk> Is there? I was under the impression that because of
how you guys abused the variants file, it totally ignores the entire koji tag in the pungi
config
Jan 12 09:55:21 <puiterwijk> (ab)used* (my personal opinion/feeling from having to
do bodhi+pungi)
Jan 12 09:55:39 <lsedlar> jkaluza, the patches for hybrid composes are not yet in
upstream, so there is still more work to do
Jan 12 09:55:57 <puiterwijk> Right. Thatis the work I was talking about, and
that's what I'd heard
Jan 12 09:55:59 <contyk> I don't think we want a hybrid compose in Fedora
Jan 12 09:56:00 <jkaluza> lsedlar: ah, I thought they are upstream
Jan 12 09:56:10 <contyk> the /os dir should be pure rpms, /modular should be just
modules
Jan 12 09:56:15 <puiterwijk> contyk: but... that seems to be what was asked?
Jan 12 09:56:17 <puiterwijk> Huh.
Jan 12 09:56:25 <contyk> puiterwijk: where exactly?
Jan 12 09:56:30 <jkaluza> contyk: then please correct me, because from what we have
discussed last week it seemed like you want to have single repo :)
Jan 12 09:56:32 <puiterwijk> jkaluza, contyk: can I ask to fight this out amongst
eachother?
Jan 12 09:56:36 <puiterwijk> contyk: look at jkaluza's statement
Jan 12 09:56:48 <contyk> oh, sorry, right, the paths... it's technically a
single repo
Jan 12 09:56:50 <puiterwijk> 3. 2. 1. FIGHT!
Jan 12 09:56:56 <contyk> but two separate dirs
Jan 12 09:57:08 »» jkaluza is starting to be lost
Jan 12 09:57:16 <puiterwijk> contyk: but they can be generated in two different
composes? Or do they come from the same pungi run?
Jan 12 09:57:16 <contyk> and I think we discussed that we would do two separate
composes and then merge them
Jan 12 09:57:24 <contyk> puiterwijk: ^
Jan 12 09:57:33 <contyk> if that's possible
Jan 12 09:57:34 <jkaluza> contyk: should we have single repodata containing both
classic RPMs + modules on top of them?
Jan 12 09:57:52 <fm-releng> pagure.git.receive -- lsedlar pushed 21 commits to
fork/lsedlar/pungi (pkgset-tag-refactor)
https://pagure.io/fork/lsedlar/pungi/branch/pkgset-tag-refactor
Jan 12 09:57:55 <jkaluza> contyk: classic RPMs == RPMs coming from f2x koji_tag
Jan 12 09:57:55 <puiterwijk> contyk: okay. So you want a traditional compose, a
modular compose (just like we have now), and just shove the output of the modular one
aside the traditional one, in a way that the repodata and Packages are not overlapping but
close?
Jan 12 09:58:23 <puiterwijk> i.e.:
Jan 12 09:58:25
<puiterwijk> fedora/linux/releases/28/Everything/x86_64/os/Packages
Jan 12 09:58:27
<puiterwijk> fedora/linux/releases/28/Everything/x86_64/os/repodata
Jan 12 09:58:29
<puiterwijk> fedora/linux/releases/28/Everything/x86_64/modular/Packages
Jan 12 09:58:31
<puiterwijk> fedora/linux/releases/28/Everything/x86_64/modular/repodata
Jan 12 09:58:33 <puiterwijk> Is that what you want?
Jan 12 09:58:35 <fm-releng> pagure.pull-request.comment.added -- lsedlar commented
on PR #798 on pungi
https://pagure.io/pungi/pull-request/798#comment-42758
Jan 12 09:58:38 »» jkaluza understands that he does not want this
Jan 12 09:58:39 <contyk> I think so, yes
Jan 12 09:58:49 <jkaluza> ok, I've been wrong all the time then :)
Jan 12 09:58:53 <fm-releng> pagure.pull-request.comment.added -- lsedlar commented
on PR #798 on pungi
https://pagure.io/pungi/pull-request/798#comment-42759
Jan 12 09:58:54 <fm-releng> pagure.pull-request.closed -- lsedlar closed (without
merging) pull request #798 on pungi
https://pagure.io/pungi/pull-request/798
Jan 12 09:58:58 <jkaluza> but fortunately did not talk with anyone about this :)
Jan 12 09:59:00 <puiterwijk> jkaluza: okay, so you're saying that what contyk
says is correct?
Jan 12 09:59:04 <contyk> the motivation is that you should be able to disable
modules and use traditional Fedora
Jan 12 09:59:29 <puiterwijk> Okay. In that case, it's literally just a syncing
destination path difference... That's simple enough to do
Jan 12 09:59:40 <contyk> personally I would be fine with two separate composes but I
wasn't behind this proposal
Jan 12 09:59:46 <contyk> yeah
Jan 12 09:59:47 <puiterwijk> contyk: I am going to guess we won't get a
fedora/linux/releases/28/Workstation/x86_64/modular/repodata?
Jan 12 09:59:48 <jkaluza> puiterwijk: contyk is the leader here, I was just
discussing that with him over the coffee last week and had an impresion that we were
discussing he wants to merge those two repositories together
Jan 12 10:00:06 <puiterwijk> jkaluza: okay. Thanks for confirming that you lost :P
Jan 12 10:00:06 <jkaluza> puiterwijk: but he probably just wants them to appear in
single compose, but still as two repositories
Jan 12 10:00:12 <jkaluza> puiterwijk: yes :)
Jan 12 10:00:22 <puiterwijk> jkaluza: oh? He just said he's expecting two
composes merged?
Jan 12 10:00:25 <contyk> jkaluza: we do but not necessarily in Fedora context :)
Jan 12 10:01:20 <contyk> you guys are confusing me
Jan 12 10:01:22 <contyk> :P
Jan 12 10:02:04 <jkaluza> that's what I'm goot at
Jan 12 10:02:07 <jkaluza> *good
Jan 12 10:02:12 <contyk> I think we want to be shipping a single compose
Jan 12 10:02:20 <contyk> this single compose could be created by merging two
separate composes
Jan 12 10:02:26 <contyk> one modular, one traditional
Jan 12 10:02:55 <contyk> the two parts should probably have separate repodata so
that you can disable modules and use non-modular tools to work with your RPMs
Jan 12 10:03:14 <contyk> does that make sense?
Jan 12 10:03:29 <jkaluza> yes
Jan 12 10:03:40 <jkaluza> it's what puiterwijk showed in his example, I think
Jan 12 10:04:37 <fm-releng> pagure.git.receive -- lsedlar pushed 33 commits to
fork/lsedlar/pungi (mixed-variant)
https://pagure.io/fork/lsedlar/pungi/branch/mixed-variant
Jan 12 10:06:16 <puiterwijk> contyk: not exactly. Do you want two composes but in
the same output dir, or actually one pungi run? In my terminology, one "pungi
run" == "one compose"
Jan 12 10:06:23 <fm-releng> pungi.compose.status.change -- pungi-koji compose of
Fedora-Epel-7-updates-testing-20180112.0 just finished
https://kojipkgs.fedoraproject.org/compose/updates/Fedora-Epel-7-updates-...
Jan 12 10:06:35 «--- asamalik (asamalik@nat/redhat/x-aoeqpdtaieqmuwnu) has Quit (Ping
timeout: 240 seconds)
Jan 12 10:07:04 <contyk> puiterwijk: two repos under one dir
Jan 12 10:07:12 <contyk> puiterwijk: two pungi runs at least
Jan 12 10:07:21 <contyk> puiterwijk: three if the merge is another pungi run, two if
not
Jan 12 10:07:28 <puiterwijk> Okay.
Jan 12 10:07:33 <puiterwijk> The merge won't be done by Pungi
Jan 12 10:07:36 <puiterwijk> Just a crude python script :)
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/7227