Pungi doesn't create usable media anymore with F17 + updates
by Jos Vos
Hi,
When using pungi on a F17 system with all updates applied, it seems
to work fine when I only use the F17 release repo in the config file,
but it creates useless media when I also include the F17 updates repo.
Then, when booting the DVD, it times out after a long time when spawning
the shell on tty2 and after selecting the keyboard it runs into a Python
exception.
Are these known problems and what can I do about it? My main goal is
to create media to install an up-to-date F17 from (only) DVD.
Otherwise I'll file a bug with all details
Thx,
--
-- Jos Vos <jos(a)xos.nl>
-- X/OS Experts in Open Systems BV | Phone: +31 20 6938364
-- Amsterdam, The Netherlands | Fax: +31 20 6948204
11 years, 2 months
回复: kojibuilder could not init mock buildroot
by 深蓝
there is no log kojibuilder4 DIR /var/lib/mock is empty!
------------------ 原始邮件 ------------------
发件人: "Mike McLean";
发送时间: 2012年9月14日(星期五) 凌晨3:38
收件人: "buildsys";
主题: Re: kojibuilder could not init mock buildroot
On 09/13/2012 04:57 AM, 深蓝 wrote:
> I don‘t known why kojibuild4 not working ! this is error infomations
Have you looked at the logs? In this case the error message is probably
mistaken. I'd look at root.log or mockoutput.log
--
buildsys mailing list
buildsys(a)lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/buildsys
11 years, 2 months
kojibuilder could not init mock buildroot
by 深蓝
I don‘t known why kojibuild4 not working ! this is error infomations
Namekojibuilder4
ID4
Archesmips64el
Capacity16.0
Task Load1.50
Description
Comment
Enabled? (disable)
Ready?
Last Update2012-09-14 00:53:08
Channels createrepo
default
Active Buildroots No buildroots
Edit host
Result BuildrootError: could not init mock buildroot, mock exited with status 1; see build.log for more information
------------------ 原始邮件 ------------------
发件人: "Thomas"<alphacc(a)gmail.com>;
发送时间: 2012年9月13日(星期四) 凌晨0:32
收件人: "Discussion of Fedora build system"<buildsys(a)lists.fedoraproject.org>;
主题: Re: How do I remove a package from koji?
I need to clarify why *I* need to delete package.
It is mainly because I have many users and people don't read the docs.
So I end up with these kind of packages (from today logs) :
"qpid-cpp-mrg"
../build/SRPMS/m4-1.4.8-2.src.rpm
/llinux/cern/slc5X/updates/SRPMS/libpng-1.2.10-15.el5_7.src.rpm
So for me it is relevant to have a way to delete packages and
hopefully one day it will make it to koji cli :)
--
Thomas
--
buildsys mailing list
buildsys(a)lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/buildsys
11 years, 2 months
回复: How do I remove a package from koji?
by 深蓝
thanks!
------------------ 原始邮件 ------------------
发件人: "Mike McLean";
发送时间: 2012年9月12日(星期三) 晚上10:27
收件人: "buildsys";
主题: Re: How do I remove a package from koji?
On 09/06/2012 02:10 AM, 深蓝 wrote:
> How do I remove a package from koji?
>
> i want remove some old package from koji ,i already remove ervery tag in koji!
So let's clarify first. Do you want to remove a package or a build?
Builds (i.e. the result of a build task) are removed by running koji-gc
regularly. You can read more about garbage collection here:
https://fedoraproject.org/wiki/Koji/GarbageCollection
If you're too impatient for that, you can call the deleteBuild xmlrpc
handler directly.
In Koji, the term package refers to an unversioned package name, i.e.
simply kernel or glibc. These are simply references in a name index
table and there is no official mechanism to remove them.
--
buildsys mailing list
buildsys(a)lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/buildsys
11 years, 2 months
Koji+fedpkg: download sources to build SRPM
by John Morris
Hi,
In order for koji to build from git, it must retrieve sources from the
lookaside cache. I believe that's the only reason the 'fedpkg' package
is required in a build target's 'srpm-build' group.
The default fedpkg.conf installed by the RPM is configured with the
Fedora lookaside server URLs. Of course that doesn't work in my shop,
where we run our own koji infra.
I hacked koji to pull the host's /etc/fedpkg.conf file into the mock
chroot, the same way koji does out of the box with /etc/hosts. The
patch is attached.
Koji and the Fedora packaging tools have been great tools for us. We're
using koji, mock, sigul, fedpkg and other components. It's been a
little frustrating at times, though, frequently dealing with what seems
like configuration data that's hardcoded into the source.
I'm guessing that addressing that is low-priority, since the main
consumers of these tools are the users of the Fedora build
infrastructure. I occasionally get the bug to 'fix' stuff. Most
recently, I set up a subclassed fedpkg tool that works with the
peculiarities of our configuration (configuration locations, branch
nomenclature, etc.). It turned out to be a bit hairy, and it wouldn't
be tough to fix fedpkg. Would patches be welcome? It would be pretty
valuable to have private instances supported a little better.
Thanks-
John
--- koji-1.7.0/koji/__init__.py~ 2012-05-31 14:05:43.000000000 -0500
+++ koji-1.7.0/koji/__init__.py 2012-08-31 17:48:54.411897132 -0500
@@ -1266,6 +1266,9 @@
etc_hosts = file('/etc/hosts')
files['etc/hosts'] = etc_hosts.read()
etc_hosts.close()
+ fedpkg_conf = file('/etc/rpkg/fedpkg.conf')
+ files['etc/rpkg/fedpkg.conf'] = fedpkg_conf.read()
+ fedpkg_conf.close()
mavenrc = ''
if opts.get('maven_opts'):
mavenrc = 'export MAVEN_OPTS="%s"\n' % '
'.join(opts['maven_opts'])
11 years, 2 months