How to remove the large directory after build ?
by Jian Lee
Hello,everybody!
My koji server has setup ok. but the mock dir is more and more large. How to
remove it ?
I mean if koji has this feature,I doesn't to do it myself. Is anyone can
help me ?
my mock directory info :
------------------------------------
651M gtes11.2-build-10-9
18M gtes11.2-build-13-10
5.6M gtes11.2-build-15-15
549M gtes11.2-build-1-6
5.5M gtes11.2-build-16-15
18M gtes11.2-build-18-18
18M gtes11.2-build-19-18
579M gtes11.2-build-21-20
560M gtes11.2-build-22-20
3.5G gtes11.2-build-23-26
548M gtes11.2-build-2-6
567M gtes11.2-build-3-6
583M gtes11.2-build-5-9
562M gtes11.2-build-6-9
670M gtes11.2-build-9-9
6.2M gtes11.3-build-24-28
6.1M gtes11.3-build-25-28
637M gtes11.3-build-26-30
609M gtes11.3-build-28-30
3.5G gtes11.3-build-30-30
3.0G gtes11.3-build-31-30
1.8G gtes11.3-build-32-32
1.8G gtes11.3-build-34-32
583M gtes11.3-build-35-33
562M gtes11.3-build-37-33
888M gtes11.3-build-39-34
852M gtes11.3-build-40-34
408M moblin2-build-41-38
417M moblin2-build-42-39
==================================
Thanks!
--
李建
msn lijian.gnu(a)gmail.com
14 years, 10 months
Makefile.common problem
by Toshio Kuratomi
This ticket was filed in infrastructure's trac. I've been told this is
actually where it should go::
https://fedorahosted.org/fedora-infrastructure/ticket/1412
Makefile.common currently causes build failures when doing "make local"
with a package containing a noarch subpackage.
The problem is on line 38: LOCALARCH := $(if $(shell grep -i
'^BuildArch:.*noarch' $(SPECFILE)), noarch, $(shell uname -m))
First, it cannot grep noarch in this way now, second, there should be
$(shell rpm --eval %{_arch}) instead of $(shell uname -m).
As discussed on #fedora-devel with Toshio and Adam Jackson, this should
be now probably changed to plain: LOCALARCH := $(shell rpm --eval %{_arch})
For noarch only packages this means they'll be built in a $arch
directory, but that's not an issue IMHO.
...it would be nice to fix this soon, I indeed spent some time looking
around what happens to find out why my noarch subpackages fail locally
and build fine in Koji -- would like to spare this time for others;)
14 years, 11 months
mock and sha256 rpms
by Mike McLean
If you use mock for building, then you may be in the position of having
the main system rpm use sha256 checksums (e.g. on F11) but create
chroots that contain an older rpm that does not.
If you create a source rpm using the newer rpm and pass it to mock to
build in a chroot with an older rpm, you will get an error like the
following:
> DEBUG util.py:256: error: unpacking of archive failed on file /builddir/build/SOURCES/INIT.2008-02-02.tgz;4a1e5c21: cpio: MD5 sum mismatch
> DEBUG util.py:319: Child returncode was: 1
I think the simplest way to work around this is to have mock pass
--nomd5 to rpm when installing the srpm in the chroot.
Of course, this is dropping an integrity check, so could possibly add a
check outside the chroot to verify this data. Granted, I'm not sure what
the best way to do that is.
Thoughts? Concerns?
14 years, 11 months
ActionNotAllowed: admin permission required
by Lester Pimentel
Hi all -
I'm fighting with getting koji configured and running on a single
machine to test it out on. Stepping through this wiki:
http://fedoraproject.org/wiki/Koji/ServerHowTo
Configuring it for ssl auth, I've gotten down to installing kojihub
and when I try to do something like adding a user through koji, I get:
[kojiadmin@testmachine ~]$ koji add-user kojira
ActionNotAllowed: admin permission required
Here's what my users look like in the koji db:
id | name | password | status | usertype | krb_principal
----+-------------------------
---+----------+--------+----------+---------------
10 | koji | | 0 | 0 |
12 | kojiadmin | | 0 | 1 |
Any ideas on what I could be missing? Is this an ssl authentication error or database related?
Thanks,
Lester
14 years, 11 months
Which RPM does mergerepo prefer?
by Jitesh Shah
Hi,
I have attached an external repo to a build tag (Just trying out some
hand-built RPMs). Now, if an RPM is present *both* in the build tag as
well as the external repo, which one does mergerepos pick?
Is the decision based on version comparison (the greater version wins),
or does the one in the build tag always get preference over the external
repo (irrespective of the version)?
If it is the latter, how do I tell mergerepos to prefer external repo
over the build tag? (or atleast use version comparisons rather than
preferring build tag)
Jitesh
14 years, 11 months
One build for multiple platforms?
by Steve Traylen
Hi,
I thinking that the answer is that it is not currently possible but is
there any arrangement of configuration
to allow a build on say centos4 and centos5 concurrently.
A build tartget that has a fork to two buildroots and destination
tags. Both would need to work
for the overall task to work.
Steve
--
Steve Traylen
14 years, 11 months
[PATCH] koji: Look at tail of build/root.log
by Kedar Sovani
A lot of times the purpose of looking at the build logs is to look at the error
which usually appear at the end of the log. Provide a mechanism to look at the tail
instead of downloading the entire log. (offset = -2000 is probably reasonable
enough as a default?)
Unsure if it applies to a wider usecase.
Please consider for inclusion.
Signed-Off-by: Kedar Sovani <kedars(a)marvell.com>
--- ./www/kojiweb/taskinfo.chtml.orig 2009-04-27 11:41:35.000000000 +0200
+++ ./www/kojiweb/taskinfo.chtml 2009-05-03 10:06:55.000000000 +0200
@@ -287,7 +287,11 @@
<th>Output</th>
<td>
#for $filename in $output
- <a href="getfile?taskID=$task.id&name=$urllib.quote($filename)">$filename</a><br/>
+ <a href="getfile?taskID=$task.id&name=$urllib.quote($filename)">$filename</a>
+ #if $filename == 'build.log' or $filename == 'root.log'
+ (<a href="getfile?taskID=$task.id&name=$urllib.quote($filename)&offset=-2000">tail</a>)
+ #end if
+ <br/>
#end for
#if $task.state not in ($koji.TASK_STATES.CLOSED, $koji.TASK_STATES.CANCELED, $koji.TASK_STATES.FAILED) and \
$task.method in ('buildSRPMFromSCM', 'buildArch', 'createrepo')
14 years, 11 months
RE: PATCH] koji: Look at tail of build/root.log
by Kedar Sovani
No takers?
Kedar.
> -----Original Message-----
> Date: Mon, 4 May 2009 14:16:35 +0530
> From: Kedar Sovani <kedars(a)marvell.com>
> Subject: [PATCH] koji: Look at tail of build/root.log
> To: fedora-buildsys-list(a)redhat.com
> Message-ID: <20090504084635.GA4975(a)linux-dev.marvell.com>
> Content-Type: text/plain; charset=us-ascii
>
> A lot of times the purpose of looking at the build logs is to look at the
> error
> which usually appear at the end of the log. Provide a mechanism to look at
> the tail
> instead of downloading the entire log. (offset = -2000 is probably
> reasonable
> enough as a default?)
>
> Unsure if it applies to a wider usecase.
>
> Please consider for inclusion.
>
> Signed-Off-by: Kedar Sovani <kedars(a)marvell.com>
>
> --- ./www/kojiweb/taskinfo.chtml.orig 2009-04-27 11:41:35.000000000
> +0200
> +++ ./www/kojiweb/taskinfo.chtml 2009-05-03 10:06:55.000000000 +0200
> @@ -287,7 +287,11 @@
> <th>Output</th>
> <td>
> #for $filename in $output
> - <a
> href="getfile?taskID=$task.id&name=$urllib.quote($filename)">$filename</a>
> <br/>
> + <a
> href="getfile?taskID=$task.id&name=$urllib.quote($filename)">$filename</a>
> + #if $filename == 'build.log' or $filename == 'root.log'
> + (<a
> href="getfile?taskID=$task.id&name=$urllib.quote($filename)&offset=-
> 2000">tail</a>)
> + #end if
> + <br/>
> #end for
> #if $task.state not in ($koji.TASK_STATES.CLOSED,
> $koji.TASK_STATES.CANCELED, $koji.TASK_STATES.FAILED) and \
> $task.method in ('buildSRPMFromSCM', 'buildArch',
> 'createrepo')
>
>
>
14 years, 11 months
ActionNotAllowed: policy violation - but why?
by Steve Traylen
Hi,
I was reliably building on a tag before but now receive
ActionNotAllowed: policy violation
and can't seem shake it or understand why for a particular package
Is is possible
to get an explanation?
http://skoji.cern.ch/koji/taskinfo?taskID=2918
This is following a build as CN=straylen
koji build --nowait dist-centos4 ../SRPMS/mpich-1.2.7p1-2.el4.src.rpm
My permissions.
id | name | password | status | usertype | krb_principal
----+----------+----------+--------+----------+---------------
1 | straylen | | 0 | 0 |
and user_id=1 does not appear in user_perms . i.e I am
a boring user.
The package has been added.
koji list-pkgs --tag=dist-centos4 --package=mpich
Package Tag Extra Arches Owner
----------------------- ----------------------- ---------------- ---------------
mpich dist-centos4 straylen
Thanks again for the help.
Steve
--
Steve Traylen
14 years, 11 months
