I'm afraid thus is the third time I've tried to get koji working to submit packages for EPEL and Fedora, and once again I'm stuck. I've activated a fresh Fedora 23 build, gotten my bugzillas and credentials working, but cannot make even a scratch rebuild if an existing Fedora SRPM for proof of concept test.
What base OS are people using for Koji packaging? I've built up roughly 200 SRPM kits that I publish at github.com, and I'd really like to be able to publish some of my old favorites to EPEL and Fedora.
Nico Kadel-Garcia Email: nkadel@gmail.com Sent from iPhone
On 10 Dec 2015 1:53 a.m., "Nico Kadel-Garcia" nkadel@gmail.com wrote:
I'm afraid thus is the third time I've tried to get koji working to
submit packages for EPEL and Fedora, and once again I'm stuck. I've activated a fresh Fedora 23 build, gotten my bugzillas and credentials working, but cannot make even a scratch rebuild if an existing Fedora SRPM for proof of concept test.
What base OS are people using for Koji packaging? I've built up roughly
200 SRPM kits that I publish at github.com, and I'd really like to be able to publish some of my old favorites to EPEL and Fedora.
Nico do you mean the OS to run *koji* on or the client side to submit jobs to fedoras koji instance?
So far as I recall koji in Fedora land runs current - ie F23 at this time.
As a packager I use F23 for the client, but that is essentially only because I find Fedora a better desktop OS for me. Since the client only really does a login event and pushes an srpm it should be pretty much distro agnostic.
Also if you mean submitting to Fedora koji keep in mind these packages have to be suitable for EPEL/Fedora as per their policies (legal side of things if only scratch).
From the context, sounds like he just wants to run the koji client.
Have you followed these docs? https://wiki.centos.org/HowTos/CommunityBuildSystem https://wiki.centos.org/HowTos/CentosPackager
On Thu, Dec 10, 2015 at 2:52 AM, James Hogarth james.hogarth@gmail.com wrote:
On 10 Dec 2015 1:53 a.m., "Nico Kadel-Garcia" nkadel@gmail.com wrote:
I'm afraid thus is the third time I've tried to get koji working to
submit packages for EPEL and Fedora, and once again I'm stuck. I've activated a fresh Fedora 23 build, gotten my bugzillas and credentials working, but cannot make even a scratch rebuild if an existing Fedora SRPM for proof of concept test.
What base OS are people using for Koji packaging? I've built up roughly
200 SRPM kits that I publish at github.com, and I'd really like to be able to publish some of my old favorites to EPEL and Fedora.
Nico do you mean the OS to run *koji* on or the client side to submit jobs to fedoras koji instance?
So far as I recall koji in Fedora land runs current - ie F23 at this time.
As a packager I use F23 for the client, but that is essentially only because I find Fedora a better desktop OS for me. Since the client only really does a login event and pushes an srpm it should be pretty much distro agnostic.
Also if you mean submitting to Fedora koji keep in mind these packages have to be suitable for EPEL/Fedora as per their policies (legal side of things if only scratch).
CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
Err, wait, you said for EPEL and Fedora,... that would be this doc. https://fedoraproject.org/wiki/Using_the_Koji_build_system
On Thu, Dec 10, 2015 at 4:42 PM, Mike McLean mikem@imponderable.org wrote:
From the context, sounds like he just wants to run the koji client. Have you followed these docs? https://wiki.centos.org/HowTos/CommunityBuildSystem https://wiki.centos.org/HowTos/CentosPackager
On Thu, Dec 10, 2015 at 2:52 AM, James Hogarth james.hogarth@gmail.com wrote:
On 10 Dec 2015 1:53 a.m., "Nico Kadel-Garcia" nkadel@gmail.com wrote:
I'm afraid thus is the third time I've tried to get koji working to
submit packages for EPEL and Fedora, and once again I'm stuck. I've activated a fresh Fedora 23 build, gotten my bugzillas and credentials working, but cannot make even a scratch rebuild if an existing Fedora SRPM for proof of concept test.
What base OS are people using for Koji packaging? I've built up roughly
200 SRPM kits that I publish at github.com, and I'd really like to be able to publish some of my old favorites to EPEL and Fedora.
Nico do you mean the OS to run *koji* on or the client side to submit jobs to fedoras koji instance?
So far as I recall koji in Fedora land runs current - ie F23 at this time.
As a packager I use F23 for the client, but that is essentially only because I find Fedora a better desktop OS for me. Since the client only really does a login event and pushes an srpm it should be pretty much distro agnostic.
Also if you mean submitting to Fedora koji keep in mind these packages have to be suitable for EPEL/Fedora as per their policies (legal side of things if only scratch).
CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
On Thu, Dec 10, 2015 at 4:46 PM, Mike McLean mikem@imponderable.org wrote:
Err, wait, you said for EPEL and Fedora,... that would be this doc. https://fedoraproject.org/wiki/Using_the_Koji_build_system
The legal side of things is good: I'm trying to submit python modules from pypi.python.org to support an RPM for the AWS command line interface, with the maintainer's buy-in, and a whole stack of other python modules.
I followed the directions very precisely, much like the last several times I tried to use koji. I got further this time by starting with Fedora 23, but I get this:
[nkadel@nkadel-f23 python-py2pack-srpm]$ koji --debug build --scratch f24 rpmbuild/SRPMS/python-py2pack-0.4.10-0.1.fc23.src.rpm successfully connected to hub Uploading srpm: rpmbuild/SRPMS/python-py2pack-0.4.10-0.1.fc23.src.rpm 2015-12-11 06:44:40,176 [DEBUG] koji: Fast upload: rpmbuild/SRPMS/python-py2pack-0.4.10-0.1.fc23.src.rpm to cli-build/1449834279.915154.ARnbTyKE/python-py2pack-0.4.10-0.1.fc23.src.rpm 2015-12-11 06:44:40,721 [DEBUG] koji: Fast upload: rpmbuild/SRPMS/python-py2pack-0.4.10-0.1.fc23.src.rpm complete. 40476 bytes in 0.3 seconds
Created task: 12151626 Task info: http://koji.fedoraproject.org/koji/taskinfo?taskID=12151626 Watching tasks (this may be safely interrupted)... 12151626 build (f24, python-py2pack-0.4.10-0.1.fc23.src.rpm): open (buildvm-24.phx2.fedoraproject.org) Traceback (most recent call last): File "/usr/bin/koji", line 6733, in <module> rv = locals()[command].__call__(options, session, args) File "/usr/bin/koji", line 955, in handle_build return watch_tasks(session, [task_id], quiet=build_opts.quiet) File "/usr/bin/koji", line 456, in watch_tasks changed = task.update() File "/usr/bin/koji", line 361, in update self.info = self.session.getTaskInfo(self.id, request=True) File "/usr/lib/python2.7/site-packages/koji/__init__.py", line 1577, in __call__ return self.__func(self.__name,args,opts) File "/usr/lib/python2.7/site-packages/koji/__init__.py", line 1952, in _callMethod iter(arg) TypeError: 'int' object is not iterable
[nkadel@nkadel-f23 python-py2pack-srpm]$ koji --debug build --scratch f24 rpmbuild/SRPMS/python-py2pack-0.4.10-0.1.fc23.src.rpm
BTW why don't you just ask package maintainer to update to the new version? You can find maintainers in pkgdb or ask zodbot [1]
Cheers, Alan
[1] https://admin.fedoraproject.org/pkgdb/package/python-py2pack/ <apevec> .whoowns python-py2pack <zodbot> apevec: hguemar (orphan in Fedora EPEL)
On 11 Dec 2015 12:01, "Nico Kadel-Garcia" nkadel@gmail.com wrote:
On Thu, Dec 10, 2015 at 4:46 PM, Mike McLean mikem@imponderable.org
wrote:
Err, wait, you said for EPEL and Fedora,... that would be this doc. https://fedoraproject.org/wiki/Using_the_Koji_build_system
The legal side of things is good: I'm trying to submit python modules from pypi.python.org to support an RPM for the AWS command line interface, with the maintainer's buy-in, and a whole stack of other python modules.
I followed the directions very precisely, much like the last several times I tried to use koji. I got further this time by starting with Fedora 23, but I get this:
[nkadel@nkadel-f23 python-py2pack-srpm]$ koji --debug build --scratch f24 rpmbuild/SRPMS/python-py2pack-0.4.10-0.1.fc23.src.rpm successfully connected to hub Uploading srpm: rpmbuild/SRPMS/python-py2pack-0.4.10-0.1.fc23.src.rpm 2015-12-11 06:44:40,176 [DEBUG] koji: Fast upload: rpmbuild/SRPMS/python-py2pack-0.4.10-0.1.fc23.src.rpm to
cli-build/1449834279.915154.ARnbTyKE/python-py2pack-0.4.10-0.1.fc23.src.rpm
2015-12-11 06:44:40,721 [DEBUG] koji: Fast upload: rpmbuild/SRPMS/python-py2pack-0.4.10-0.1.fc23.src.rpm complete. 40476 bytes in 0.3 seconds
Created task: 12151626 Task info: http://koji.fedoraproject.org/koji/taskinfo?taskID=12151626 Watching tasks (this may be safely interrupted)... 12151626 build (f24, python-py2pack-0.4.10-0.1.fc23.src.rpm): open (buildvm-24.phx2.fedoraproject.org) Traceback (most recent call last): File "/usr/bin/koji", line 6733, in <module> rv = locals()[command].__call__(options, session, args) File "/usr/bin/koji", line 955, in handle_build return watch_tasks(session, [task_id], quiet=build_opts.quiet) File "/usr/bin/koji", line 456, in watch_tasks changed = task.update() File "/usr/bin/koji", line 361, in update self.info = self.session.getTaskInfo(self.id, request=True) File "/usr/lib/python2.7/site-packages/koji/__init__.py", line 1577, in __call__ return self.__func(self.__name,args,opts) File "/usr/lib/python2.7/site-packages/koji/__init__.py", line 1952, in _callMethod iter(arg) TypeError: 'int' object is not iterable
That's a known long standing koji bug...
Just open the task URL in a browser to see the status.
Going by the above it appears to have been successfully submitted fit building.