While following this guide: http://fedoraproject.org/wiki/How_to_create_a_Fedora_install_ISO_for_testing..., I've received an interesting error:
$ mock -r goose-sketchy-x86_64 --shell INFO: mock.py version 1.1.18 starting... State Changed: init plugins INFO: selinux disabled State Changed: start State Changed: lock buildroot State Changed: shell <mock-chroot>[root@pilgrim /]# pungi -G -C -B --flavor=GoOSe --ver=sketchy -c /root/pungi-x86_64.ks Warning: Reusing existing destination directory. Traceback (most recent call last): File "/usr/bin/pungi", line 216, in <module> main() File "/usr/bin/pungi", line 86, in main mypungi._inityum() # initialize the yum object for things that need it File "/usr/lib/python2.6/site-packages/pypungi/__init__.py", line 166, in _inityum del self.ayum.prerepoconf AttributeError: prerepoconf
A couple things to note:
pungi was built by me from the latest that seemed to work with something equivalent to CentOS6.0 on our koji server -
pungi-2.0.22-1.gl6.noarch.
Here are the mock and yum versions as well:
mock-1.1.18-1.el6.noarch yum-3.2.29-22.el6.centos.noarch
I did have a look through the mock logs to no avail.
Any thoughts?
Anything else I can provide, please just let me know.
Thanks,
Clint
For F17 , we have a new tool which obsolete (as I understand) pungi, which is lorax . Lorax is discussed in anaconda-devel-list@redhat.com ML .
Hope that help something.
On Thu, 2012-03-01 at 10:17 -0700, Clint Savage wrote:
While following this guide: http://fedoraproject.org/wiki/How_to_create_a_Fedora_install_ISO_for_testing..., I've received an interesting error:
$ mock -r goose-sketchy-x86_64 --shell INFO: mock.py version 1.1.18 starting... State Changed: init plugins INFO: selinux disabled State Changed: start State Changed: lock buildroot State Changed: shell <mock-chroot>[root@pilgrim /]# pungi -G -C -B --flavor=GoOSe--ver=sketchy -c /root/pungi-x86_64.ks Warning: Reusing existing destination directory. Traceback (most recent call last): File "/usr/bin/pungi", line 216, in <module> main() File "/usr/bin/pungi", line 86, in main mypungi._inityum() # initialize the yum object for things that need it File "/usr/lib/python2.6/site-packages/pypungi/__init__.py", line 166, in _inityum del self.ayum.prerepoconf AttributeError: prerepoconf
A couple things to note:
pungi was built by me from the latest that seemed to work with something equivalent to CentOS6.0 on our koji server -
pungi-2.0.22-1.gl6.noarch.
Here are the mock and yum versions as well:
mock-1.1.18-1.el6.noarch yum-3.2.29-22.el6.centos.noarch
I did have a look through the mock logs to no avail.
Any thoughts?
Anything else I can provide, please just let me know.
Thanks,
Clint
buildsys mailing list buildsys@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/buildsys
Unfortunately, I don't know that this helps atm as I'm trying to build isos similar to RHEL 6.
I will definitely look into Lorax. I read about it some recently.
Thanks Sérgio,
Clint
2012/3/15 Sérgio Basto sergio@serjux.com:
For F17 , we have a new tool which obsolete (as I understand) pungi, which is lorax . Lorax is discussed in anaconda-devel-list@redhat.com ML .
Hope that help something.
On Thu, 2012-03-01 at 10:17 -0700, Clint Savage wrote:
While following this guide: http://fedoraproject.org/wiki/How_to_create_a_Fedora_install_ISO_for_testing..., I've received an interesting error:
$ mock -r goose-sketchy-x86_64 --shell INFO: mock.py version 1.1.18 starting... State Changed: init plugins INFO: selinux disabled State Changed: start State Changed: lock buildroot State Changed: shell <mock-chroot>[root@pilgrim /]# pungi -G -C -B --flavor=GoOSe --ver=sketchy -c /root/pungi-x86_64.ks Warning: Reusing existing destination directory. Traceback (most recent call last): File "/usr/bin/pungi", line 216, in <module> main() File "/usr/bin/pungi", line 86, in main mypungi._inityum() # initialize the yum object for things that need it File "/usr/lib/python2.6/site-packages/pypungi/__init__.py", line 166, in _inityum del self.ayum.prerepoconf AttributeError: prerepoconf
A couple things to note:
pungi was built by me from the latest that seemed to work with something equivalent to CentOS6.0 on our koji server -
pungi-2.0.22-1.gl6.noarch.
Here are the mock and yum versions as well:
mock-1.1.18-1.el6.noarch yum-3.2.29-22.el6.centos.noarch
I did have a look through the mock logs to no avail.
Any thoughts?
Anything else I can provide, please just let me know.
Thanks,
Clint
buildsys mailing list buildsys@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/buildsys
-- Sérgio M. B.
-- buildsys mailing list buildsys@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/buildsys
On 3/15/12 7:29 PM, Sérgio Basto wrote:
For F17 , we have a new tool which obsolete (as I understand) pungi, which is lorax . Lorax is discussed inanaconda-devel-list@redhat.com ML .
Lorax does not replace pungi. Lorax replaces 'buildinstall' which is something pungi used to call, and now pungi calls into lorax.
On 3/1/12 9:17 AM, Clint Savage wrote:
File "/usr/lib/python2.6/site-packages/pypungi/__init__.py", line166, in _inityum del self.ayum.prerepoconf AttributeError: prerepoconf
A couple things to note:
pungi was built by me from the latest that seemed to work with something equivalent to CentOS6.0 on our koji server -
pungi-2.0.22-1.gl6.noarch.
Here are the mock and yum versions as well:
mock-1.1.18-1.el6.noarch yum-3.2.29-22.el6.centos.noarch
I did have a look through the mock logs to no avail.
Any thoughts?
Anything else I can provide, please just let me know.
That line was added to fix https://bugzilla.redhat.com/show_bug.cgi?id=609247
This may not apply to RHEL6 though, what happens if you comment out the offending line in the pungi code?
On Fri, Mar 16, 2012 at 4:07 PM, Jesse Keating jkeating@j2solutions.net wrote:
On 3/1/12 9:17 AM, Clint Savage wrote:
File "/usr/lib/python2.6/site-packages/pypungi/__init__.py", line 166, in _inityum del self.ayum.prerepoconf AttributeError: prerepoconf
A couple things to note:
pungi was built by me from the latest that seemed to work with something equivalent to CentOS6.0 on our koji server -
pungi-2.0.22-1.gl6.noarch.
Here are the mock and yum versions as well:
mock-1.1.18-1.el6.noarch yum-3.2.29-22.el6.centos.noarch
I did have a look through the mock logs to no avail.
Any thoughts?
Anything else I can provide, please just let me know.
That line was added to fix https://bugzilla.redhat.com/show_bug.cgi?id=609247
This may not apply to RHEL6 though, what happens if you comment out the offending line in the pungi code?
Jesse,
I've actually done one better and put a try/except around it. Seems to me that's a smarter thing to do anyway. It works fine that way, I just didn't understand what 'self.ayum.prerepoconf' is or why it's there. The pungi code is not completely understandable to me, this seems like an appropriate fix, however. I'd be happy to send a patch up to pungi if others thought it would be useful.
Cheers,
Clint
Clint
On 3/16/12 3:11 PM, Clint Savage wrote:
Jesse,
I've actually done one better and put a try/except around it. Seems to me that's a smarter thing to do anyway. It works fine that way, I just didn't understand what 'self.ayum.prerepoconf' is or why it's there. The pungi code is not completely understandable to me, this seems like an appropriate fix, however. I'd be happy to send a patch up to pungi if others thought it would be useful.
"prerepoconf" is an attribute to the "ayum" object that is part of the pungi class object (self). "ayum" is a yum object instance. Yum code of a certain era would create the 'prerepoconf' attribute under certain scenarios when the object is instantiated, and this would cause problems for how pungi was making use of the yum object, so the solution was to remove the attribute. I don't know if it is still an issue with current day yum objects and pungi, I haven't been working on that code for years.
On Mon, Mar 19, 2012 at 3:44 PM, Jesse Keating jkeating@j2solutions.net wrote:
On 3/16/12 3:11 PM, Clint Savage wrote:
Jesse,
I've actually done one better and put a try/except around it. Seems to me that's a smarter thing to do anyway. It works fine that way, I just didn't understand what 'self.ayum.prerepoconf' is or why it's there. The pungi code is not completely understandable to me, this seems like an appropriate fix, however. I'd be happy to send a patch up to pungi if others thought it would be useful.
"prerepoconf" is an attribute to the "ayum" object that is part of the pungi class object (self). "ayum" is a yum object instance. Yum code of a certain era would create the 'prerepoconf' attribute under certain scenarios when the object is instantiated, and this would cause problems for how pungi was making use of the yum object, so the solution was to remove the attribute. I don't know if it is still an issue with current day yum objects and pungi, I haven't been working on that code for years.
- jlk
Yeah, I kind of wondered if that's where it fit. I do think it's still something that is needed, especially in older versions. I have backported my fix into a version I'm using. It can be found at http://kojiweb.gooselinux.org/koji/buildinfo?buildID=2442 if anyone is interested in this fix. I will eventually get around to properly sending it upstream just to make sure the fix is in place.
Chers,
Clint
buildsys@lists.fedoraproject.org
-
Clint Savage -
Jesse Keating -
Sérgio Basto