Discussion:
New release of mock soon
Miroslav Suchý
2017-12-15 10:48:12 UTC
Permalink
Hi,
I plan to resolve few mock issues next week and do the release before Christmas.
The plan is not to enable karma, so you will not be surprised by new version of mock on your stable servers.

If you have some patch in your private branch then now is the right time to send the PR.

Mirek
_______________________________________________
buildsys mailing list -- ***@lists.fedoraproject.org
To unsubscribe send an email to buildsys-***@lists.
Dennis Gregorovic
2017-12-15 16:00:43 UTC
Permalink
Hi Miroslav. Thank you for the heads up. Do you have a list of
changes that will included in the release? Are there plans to test
the new release with Koji or other tools that depend on mock before
enabling karma?

Cheers
-- Dennis
Post by Miroslav Suchý
Hi,
I plan to resolve few mock issues next week and do the release before Christmas.
The plan is not to enable karma, so you will not be surprised by new version of mock on your stable servers.
If you have some patch in your private branch then now is the right time to send the PR.
Mirek
_______________________________________________
--
Dennis Gregorovic
Manager, PnT DevOps
Red Hat
***@redhat.com T: +1-978.392.3112 M: +1-617.901.9799
_______________________________________________
buildsys mailing list -- ***@lists.fedoraproject.org
To unsubscribe send an email to builds
Miroslav Suchý
2017-12-18 07:35:34 UTC
Permalink
Post by Dennis Gregorovic
Hi Miroslav. Thank you for the heads up. Do you have a list of
changes that will included in the release?
Just a list of commits since last tag:
https://github.com/rpm-software-management/mock/commits/devel
Of course, once released there will be release notes as usual.
Post by Dennis Gregorovic
Are there plans to test
the new release with Koji or other tools that depend on mock before
enabling karma?
I do not operate Koji. So I do not know. I *hope* that someone tests with Koji.
My team is testing it with Copr, I am doing running regular mock tests (included in mock itself), providing release
notes and these heads up.

But AFAIK fedora infra decided to stay with mock 1.3.4:
https://koji.fedoraproject.org/koji/buildinfo?buildID=1007638
I am not really sure why.

Mirek
_______________________________________________
buildsys mailing list -- ***@lists.fedoraproject.org
To unsubscribe send an
Neal Gompa
2017-12-18 11:19:30 UTC
Permalink
Post by Miroslav Suchý
Post by Dennis Gregorovic
Hi Miroslav. Thank you for the heads up. Do you have a list of
changes that will included in the release?
https://github.com/rpm-software-management/mock/commits/devel
Of course, once released there will be release notes as usual.
Post by Dennis Gregorovic
Are there plans to test
the new release with Koji or other tools that depend on mock before
enabling karma?
I do not operate Koji. So I do not know. I *hope* that someone tests with Koji.
My team is testing it with Copr, I am doing running regular mock tests (included in mock itself), providing release
notes and these heads up.
https://koji.fedoraproject.org/koji/buildinfo?buildID=1007638
I am not really sure why.
It was because the private tmpfs /tmp thing from nspawn broke Koji builds.

This is now fixed[1] in Koji 1.15, so Fedora Infrastructure has no
reason to remain on 1.3.4.

[1]: https://pagure.io/koji/pull-request/602


--
真実はいつも一つ！/ Always, there's only one truth!
_______________________________________________
buildsys mailing list -- ***@lists.fedoraproject.org
To unsubscribe send an emai
Kevin Fenzi
2017-12-18 19:18:40 UTC
Permalink
Post by Neal Gompa
Post by Miroslav Suchý
Post by Dennis Gregorovic
Hi Miroslav. Thank you for the heads up. Do you have a list of
changes that will included in the release?
https://github.com/rpm-software-management/mock/commits/devel
Of course, once released there will be release notes as usual.
Post by Dennis Gregorovic
Are there plans to test
the new release with Koji or other tools that depend on mock before
enabling karma?
I do not operate Koji. So I do not know. I *hope* that someone tests with Koji.
My team is testing it with Copr, I am doing running regular mock tests (included in mock itself), providing release
notes and these heads up.
https://koji.fedoraproject.org/koji/buildinfo?buildID=1007638
I am not really sure why.
It was because the private tmpfs /tmp thing from nspawn broke Koji builds.
This is now fixed[1] in Koji 1.15, so Fedora Infrastructure has no
reason to remain on 1.3.4.
[1]: https://pagure.io/koji/pull-request/602
no.

nspawn still does not work for a bunch of things koji does, some known,
some unknown.

https://pagure.io/releng/issue/6967

kevin
Miroslav Suchý
2017-12-19 08:04:05 UTC
Permalink
Post by Kevin Fenzi
Post by Neal Gompa
Post by Miroslav Suchý
Post by Dennis Gregorovic
Hi Miroslav. Thank you for the heads up. Do you have a list of
changes that will included in the release?
https://github.com/rpm-software-management/mock/commits/devel
Of course, once released there will be release notes as usual.
Post by Dennis Gregorovic
Are there plans to test
the new release with Koji or other tools that depend on mock before
enabling karma?
I do not operate Koji. So I do not know. I *hope* that someone tests with Koji.
My team is testing it with Copr, I am doing running regular mock tests (included in mock itself), providing release
notes and these heads up.
https://koji.fedoraproject.org/koji/buildinfo?buildID=1007638
I am not really sure why.
It was because the private tmpfs /tmp thing from nspawn broke Koji builds.
This is now fixed[1] in Koji 1.15, so Fedora Infrastructure has no
reason to remain on 1.3.4.
[1]: https://pagure.io/koji/pull-request/602
no.
nspawn still does not work for a bunch of things koji does, some known,
some unknown.
https://pagure.io/releng/issue/6967
It is better to set
config_opts['use_nspawn'] = False
This way, you will get all new fixes and you will use the old chroot.

Mirek
Tomáš Kopeček
2017-12-19 11:16:00 UTC
Permalink
Post by Kevin Fenzi
Post by Neal Gompa
Post by Miroslav Suchý
Post by Dennis Gregorovic
Hi Miroslav. Thank you for the heads up. Do you have a list of
changes that will included in the release?
https://github.com/rpm-software-management/mock/commits/devel
Of course, once released there will be release notes as usual.
Post by Dennis Gregorovic
Are there plans to test
the new release with Koji or other tools that depend on mock before
enabling karma?
I do not operate Koji. So I do not know. I *hope* that someone tests with Koji.
My team is testing it with Copr, I am doing running regular mock tests (included in mock itself), providing release
notes and these heads up.
https://koji.fedoraproject.org/koji/buildinfo?buildID=1007638
I am not really sure why.
It was because the private tmpfs /tmp thing from nspawn broke Koji builds.
This is now fixed[1] in Koji 1.15, so Fedora Infrastructure has no
reason to remain on 1.3.4.
[1]: https://pagure.io/koji/pull-request/602
no.
nspawn still does not work for a bunch of things koji does, some known,
some unknown.
I've fixed only very basic issue, but we're not able to build e.g.
livemedia images at all as these depend on loopback devices, and yes, I
also sometimes hit some random weird issues, which are not tracked yet,
as I wasn't able to reproduce them.
Post by Kevin Fenzi
https://pagure.io/releng/issue/6967
kevin
_______________________________________________
--

Tomas Kopecek <***@redhat.com>
Release Engineering Development, RedHat
_______________________________________________
buildsys mailing list -- ***@lists.fedoraproject.org
To unsubscribe send an email to buildsys-***@lists.fedorapr
John Florian
2017-12-19 18:03:46 UTC
Permalink
Post by Tomáš Kopeček
Post by Kevin Fenzi
Post by Neal Gompa
Post by Miroslav Suchý
Post by Dennis Gregorovic
Hi Miroslav. Thank you for the heads up. Do you have a list of
changes that will included in the release?
https://github.com/rpm-software-management/mock/commits/devel
Of course, once released there will be release notes as usual.
Post by Dennis Gregorovic
Are there plans to test
the new release with Koji or other tools that depend on mock before
enabling karma?
I do not operate Koji. So I do not know. I *hope* that someone tests with Koji.
My team is testing it with Copr, I am doing running regular
mock tests (included in mock itself), providing release
notes and these heads up.
https://koji.fedoraproject.org/koji/buildinfo?buildID=100763
8
I am not really sure why.
It was because the private tmpfs /tmp thing from nspawn broke Koji builds.
This is now fixed[1] in Koji 1.15, so Fedora Infrastructure has no
reason to remain on 1.3.4.
[1]: https://pagure.io/koji/pull-request/602
no.
nspawn still does not work for a bunch of things koji does, some known,
some unknown.
I've fixed only very basic issue, but we're not able to build e.g.
livemedia images at all as these depend on loopback devices, and yes, I
also sometimes hit some random weird issues, which are not tracked yet,
as I wasn't able to reproduce them.
I am successfully building livemedia images with koji-1.14 and only
needed to `koji edit-tag f25-build -x mock.new_chroot=False`. I'll
admit I haven't tried rebasing my custom spin on F27 yet, but I
wouldn't think that'd make a difference.
_______________________________________________
buildsys mailing list -- ***@lists.fedoraproject.org
To unsubscribe
Tomáš Kopeček
2017-12-20 11:49:03 UTC
Permalink
Post by John Florian
Post by Tomáš Kopeček
Post by Kevin Fenzi
Post by Neal Gompa
Post by Miroslav Suchý
Post by Dennis Gregorovic
Hi Miroslav. Thank you for the heads up. Do you have a list of
changes that will included in the release?
https://github.com/rpm-software-management/mock/commits/devel
Of course, once released there will be release notes as usual.
Post by Dennis Gregorovic
Are there plans to test
the new release with Koji or other tools that depend on mock before
enabling karma?
I do not operate Koji. So I do not know. I *hope* that someone tests with Koji.
My team is testing it with Copr, I am doing running regular
mock tests (included in mock itself), providing release
notes and these heads up.
https://koji.fedoraproject.org/koji/buildinfo?buildID=100763
8
I am not really sure why.
It was because the private tmpfs /tmp thing from nspawn broke Koji builds.
This is now fixed[1] in Koji 1.15, so Fedora Infrastructure has no
reason to remain on 1.3.4.
[1]: https://pagure.io/koji/pull-request/602
no.
nspawn still does not work for a bunch of things koji does, some known,
some unknown.
I've fixed only very basic issue, but we're not able to build e.g.
livemedia images at all as these depend on loopback devices, and yes, I
also sometimes hit some random weird issues, which are not tracked yet,
as I wasn't able to reproduce them.
I am successfully building livemedia images with koji-1.14 and only
needed to `koji edit-tag f25-build -x mock.new_chroot=False`. I'll
admit I haven't tried rebasing my custom spin on F27 yet, but I
wouldn't think that'd make a difference.
Yes, it shouldn't change for new_chroot=False - problems are with
nspawn-based approach.
Post by John Florian
_______________________________________________
--

Tomas Kopecek <***@redhat.com>
Release Engineering Development, RedHat
_______________________________________________
buildsys mailing list -- ***@lists.fedoraproject.org
To unsubscribe send an ema

Loading...