Re: Modularity tooling intro?

2019-06-03 Thread Vít Ondruch
I wish the initiative started with something simple like "get
module-build-macros SRPM out of modulemd YAML" [1].


Vít


[1] https://pagure.io/fm-orchestrator/issue/1217



Dne 03. 06. 19 v 10:03 Adam Samalik napsal(a):
> The local module builds we have documented at the moment [1] should
> work if you have an access to the Fedora infrastructure (==internet
> connection) and your packages are in the Fedora dist-git.
>
> I know that Merlin (merlinm) is working on tooling that allow you to
> do local module builds without relying on any external infrastructure,
> basically the way mock works with standalone packages today. He's
> submitted a talk to Flock [2] about it. I know that not everyone can
> attend, but he's probably a good person to talk to, and if his
> proposal gets accepted, there will be a recording. And the docs should
> get updated, too, when it's ready! So.. it's coming
>
> [1] 
> https://docs.fedoraproject.org/en-US/modularity/making-modules/building-modules-locally/
> [2] https://pagure.io/flock/issue/145
>
> On Sat, Jun 1, 2019 at 1:57 PM Jun Aruga  > wrote:
>
> > However, I want to do it on my own
> infrastructure and hence use the lower-level tooling such as
> mbs-manager/mock and local git repos rather than fedpkg/koji/dist-git.
>
> Sorry I missed your above message.
>
> Maybe you can open the ticket at below repository's issue page.
> https://pagure.io/fm-orchestrator
>
> fm-orchestrator repository is including module-build-service, and
> mbs-manager.
>
> I remember "mbs-build local" command worked for the local build in
> late 2017.
> But I could not find the command now.
>
> --
> Jun Aruga / He - His - Him
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> 
> To unsubscribe send an email to
> devel-le...@lists.fedoraproject.org
> 
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines:
> https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> 
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
>
>
>
> -- 
>
> Adam Šamalík
> ---
> Senior Software Engineer
> Red Hat
>
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


Re: Modularity tooling intro?

2019-06-03 Thread Adam Samalik
The local module builds we have documented at the moment [1] should work if
you have an access to the Fedora infrastructure (==internet connection) and
your packages are in the Fedora dist-git.

I know that Merlin (merlinm) is working on tooling that allow you to do
local module builds without relying on any external infrastructure,
basically the way mock works with standalone packages today. He's submitted
a talk to Flock [2] about it. I know that not everyone can attend, but he's
probably a good person to talk to, and if his proposal gets accepted, there
will be a recording. And the docs should get updated, too, when it's ready!
So.. it's coming

[1]
https://docs.fedoraproject.org/en-US/modularity/making-modules/building-modules-locally/
[2] https://pagure.io/flock/issue/145

On Sat, Jun 1, 2019 at 1:57 PM Jun Aruga  wrote:

> > However, I want to do it on my own
> infrastructure and hence use the lower-level tooling such as
> mbs-manager/mock and local git repos rather than fedpkg/koji/dist-git.
>
> Sorry I missed your above message.
>
> Maybe you can open the ticket at below repository's issue page.
> https://pagure.io/fm-orchestrator
>
> fm-orchestrator repository is including module-build-service, and
> mbs-manager.
>
> I remember "mbs-build local" command worked for the local build in late
> 2017.
> But I could not find the command now.
>
> --
> Jun Aruga / He - His - Him
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
>


-- 

Adam Šamalík
---
Senior Software Engineer
Red Hat
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


Re: Modularity tooling intro?

2019-06-01 Thread Jun Aruga
> However, I want to do it on my own
infrastructure and hence use the lower-level tooling such as
mbs-manager/mock and local git repos rather than fedpkg/koji/dist-git.

Sorry I missed your above message.

Maybe you can open the ticket at below repository's issue page.
https://pagure.io/fm-orchestrator

fm-orchestrator repository is including module-build-service, and mbs-manager.

I remember "mbs-build local" command worked for the local build in late 2017.
But I could not find the command now.

--
Jun Aruga / He - His - Him
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


Re: Modularity tooling intro?

2019-05-31 Thread Neal Gompa
On Fri, May 31, 2019 at 9:57 AM Paul Howarth  wrote:
>
> On Thu, 30 May 2019 13:30:10 +0200
> Miroslav Suchý  wrote:
>
> > Dne 30. 05. 19 v 11:16 Paul Howarth napsal(a):
> > > Any pointers anyone?
> >
> > http://frostyx.cz/posts/how-to-build-modules-in-copr
>
> Thanks, but copr is on Fedora infrastructure and I want to use my own.
>
> Surely it can't be that hard to use module-build-service locally with a
> suitable module.yaml and a pointer to git repos with rpm specs etc. in
> them?
>

I haven't managed it so far. It's also trickier if you have local
infrastructure that works differently than Fedora's, as there's no
real room for supporting alternative systems yet. :(



-- 
真実はいつも一つ!/ Always, there's only one truth!
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


Re: Modularity tooling intro?

2019-05-31 Thread Paul Howarth
On Thu, 30 May 2019 12:44:20 +0200
Jun Aruga  wrote:

> Maybe this is the document.
> https://docs.fedoraproject.org/en-US/modularity/making-modules/
> 
> In my understanding below command executes "mbs-manager" internally.
> I do not run "mbs-manager" command directly.
> 
> ```
> $ fedpkg module-build
> ```

Indeed, but that goes off and builds a module on Fedora infrastructure
and I want to build modules for a local repo instead.

Paul.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


Re: Modularity tooling intro?

2019-05-31 Thread Paul Howarth
On Thu, 30 May 2019 13:30:10 +0200
Miroslav Suchý  wrote:

> Dne 30. 05. 19 v 11:16 Paul Howarth napsal(a):
> > Any pointers anyone?  
> 
> http://frostyx.cz/posts/how-to-build-modules-in-copr

Thanks, but copr is on Fedora infrastructure and I want to use my own.

Surely it can't be that hard to use module-build-service locally with a
suitable module.yaml and a pointer to git repos with rpm specs etc. in
them?

Paul.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


Re: Modularity tooling intro?

2019-05-30 Thread Miroslav Suchý
Dne 30. 05. 19 v 11:16 Paul Howarth napsal(a):
> Any pointers anyone?

http://frostyx.cz/posts/how-to-build-modules-in-copr

-- 
Miroslav Suchy, RHCA
Red Hat, Associate Manager ABRT/Copr, #brno, #fedora-buildsys
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


Re: Modularity tooling intro?

2019-05-30 Thread Jun Aruga
Maybe this is the document.
https://docs.fedoraproject.org/en-US/modularity/making-modules/

In my understanding below command executes "mbs-manager" internally.
I do not run "mbs-manager" command directly.

```
$ fedpkg module-build
```

On Thu, May 30, 2019 at 11:17 AM Paul Howarth  wrote:
>
> Hi everyone,
>
> I have a bunch of packages in a local repo built for various versions
> of Fedora and CentOS, and am looking to build some of them for EL-8.
> Clearly the way to go for an EL-8 add-on repo is to build modules, so
> that it what I'd like to do. However, I want to do it on my own
> infrastructure and hence use the lower-level tooling such as
> mbs-manager/mock and local git repos rather than fedpkg/koji/dist-git.
>
> There's quite a bit of documentation around about building modules but
> what I've found seems to be either out of date (e.g. uses "mbs-build",
> which no longer exists) or is based on fedpkg, which abstracts away the
> lower-level operation and is geared towards Fedora infrastructure.
>
> Is there some documentation somewhere that covers getting started with
> the tools like mbs-manager?
>
> I thought this workshop looked like a good starting point:
> https://github.com/fedora-modularity/workshop
>
> When I discovered that "mbs-build" no longer exists, I tried using
> "mbs-manager" but clearly I'm missing something:
>
> $ mbs-manager build_module_locally --file test-module.yaml -s platform:f30
> 2019-05-30 09:51:04,712 - MainThread - urllib3.util.retry - DEBUG - Converted 
> retries value: 3 -> Retry(total=3, connect=None, read=None, redirect=None, 
> status=None)
> 2019-05-30 09:51:04,863 - MainThread - moksha.hub - WARNING - Cannot find 
> qpid python module. Make sure you have python-qpid installed.
> 2019-05-30 09:51:05,577 - MainThread - MBS.utils.submit - DEBUG - Submitted 
> normal module build for test-module:f30:20190530085105
> Traceback (most recent call last):
>   File "/usr/bin/mbs-manager", line 11, in 
> load_entry_point('module-build-service==2.19.1', 'console_scripts', 
> 'mbs-manager')()
>   File "/usr/lib/python3.7/site-packages/module_build_service/manage.py", 
> line 251, in manager_wrapper
> manager.run()
>   File "/usr/lib/python3.7/site-packages/flask_script/__init__.py", line 417, 
> in run
> result = self.handle(argv[0], argv[1:])
>   File "/usr/lib/python3.7/site-packages/flask_script/__init__.py", line 386, 
> in handle
> res = handle(*args, **config)
>   File "/usr/lib/python3.7/site-packages/flask_script/commands.py", line 216, 
> in __call__
> return self.run(*args, **kwargs)
>   File "/usr/lib/python3.7/site-packages/module_build_service/manage.py", 
> line 167, in build_module_locally
> username, handle, params, stream=str(stream), skiptests=skiptests)
>   File 
> "/usr/lib/python3.7/site-packages/module_build_service/utils/submit.py", line 
> 503, in submit_module_build_from_yaml
> return submit_module_build(username, mmd, params)
>   File 
> "/usr/lib/python3.7/site-packages/module_build_service/utils/submit.py", line 
> 633, in submit_module_build
> mmds = generate_expanded_mmds(db.session, mmd, raise_if_stream_ambigous, 
> default_streams)
>   File "/usr/lib/python3.7/site-packages/module_build_service/utils/mse.py", 
> line 417, in generate_expanded_mmds
> current_mmd = Modulemd.Module.new_from_string(mmd.dumps())
> TypeError: :
> Argument 0 does not allow None as a value
>
> Any pointers anyone?
>
> Paul.
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org



-- 
Jun Aruga / He - His - Him
jar...@redhat.com / IRC: jaruga
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


Modularity tooling intro?

2019-05-30 Thread Paul Howarth
Hi everyone,

I have a bunch of packages in a local repo built for various versions
of Fedora and CentOS, and am looking to build some of them for EL-8.
Clearly the way to go for an EL-8 add-on repo is to build modules, so
that it what I'd like to do. However, I want to do it on my own
infrastructure and hence use the lower-level tooling such as
mbs-manager/mock and local git repos rather than fedpkg/koji/dist-git.

There's quite a bit of documentation around about building modules but
what I've found seems to be either out of date (e.g. uses "mbs-build",
which no longer exists) or is based on fedpkg, which abstracts away the
lower-level operation and is geared towards Fedora infrastructure.

Is there some documentation somewhere that covers getting started with
the tools like mbs-manager?

I thought this workshop looked like a good starting point:
https://github.com/fedora-modularity/workshop

When I discovered that "mbs-build" no longer exists, I tried using
"mbs-manager" but clearly I'm missing something:

$ mbs-manager build_module_locally --file test-module.yaml -s platform:f30
2019-05-30 09:51:04,712 - MainThread - urllib3.util.retry - DEBUG - Converted 
retries value: 3 -> Retry(total=3, connect=None, read=None, redirect=None, 
status=None)
2019-05-30 09:51:04,863 - MainThread - moksha.hub - WARNING - Cannot find qpid 
python module. Make sure you have python-qpid installed.
2019-05-30 09:51:05,577 - MainThread - MBS.utils.submit - DEBUG - Submitted 
normal module build for test-module:f30:20190530085105
Traceback (most recent call last):
  File "/usr/bin/mbs-manager", line 11, in 
load_entry_point('module-build-service==2.19.1', 'console_scripts', 
'mbs-manager')()
  File "/usr/lib/python3.7/site-packages/module_build_service/manage.py", line 
251, in manager_wrapper
manager.run()
  File "/usr/lib/python3.7/site-packages/flask_script/__init__.py", line 417, 
in run
result = self.handle(argv[0], argv[1:])
  File "/usr/lib/python3.7/site-packages/flask_script/__init__.py", line 386, 
in handle
res = handle(*args, **config)
  File "/usr/lib/python3.7/site-packages/flask_script/commands.py", line 216, 
in __call__
return self.run(*args, **kwargs)
  File "/usr/lib/python3.7/site-packages/module_build_service/manage.py", line 
167, in build_module_locally
username, handle, params, stream=str(stream), skiptests=skiptests)
  File "/usr/lib/python3.7/site-packages/module_build_service/utils/submit.py", 
line 503, in submit_module_build_from_yaml
return submit_module_build(username, mmd, params)
  File "/usr/lib/python3.7/site-packages/module_build_service/utils/submit.py", 
line 633, in submit_module_build
mmds = generate_expanded_mmds(db.session, mmd, raise_if_stream_ambigous, 
default_streams)
  File "/usr/lib/python3.7/site-packages/module_build_service/utils/mse.py", 
line 417, in generate_expanded_mmds
current_mmd = Modulemd.Module.new_from_string(mmd.dumps())
TypeError: :
Argument 0 does not allow None as a value

Any pointers anyone?

Paul.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org