From: Stanislav Ochotnicky <sochotnicky@gmail.com>
To: gentoo-qa@lists.gentoo.org
Cc: gentoo-soc@lists.gentoo.org
Subject: [gentoo-qa] Re: [GSoC-status] Collagen - database schema and further changes
Date: Fri, 31 Jul 2009 11:44:44 +0200 [thread overview]
Message-ID: <20090731094410.GA19452@w0rm> (raw)
In-Reply-To: <20090725225012.GA7943@w0rm>
[-- Attachment #1: Type: text/plain, Size: 2278 bytes --]
Wow,
another week behind me. And quite productive one if you ask me.
I recently pushed yesterday's changes to public repo (so far
only devel branch which might get rebased so thread carefully :-)
). There is a lot of cleanup work to be done, but I can say that
we have base working now.
So what exactly was going on over the last week? I fixed
bunch of bugs (and two remaining I plan to fix today). You
can see more information about that at redmine bug tracker on
gentooexperimental.org. Once I fix remaining bugs I plan to add more
to bugtracker :-)
Some work went into making tinderboxes able to recover from problems
so that they can run without supervision. All around exception
handling and error logging is not perfect but a lot better then a
week ago.
I also started filling up database with information yesterday. It went
even smoother then I expected, I only had few typos in my code :-) All
in all it took about 2 hours to make it all work.
I have three more ebuild candidates for fixing (not confirmed yet):
* dev-java/kaffe doesn't list x11-libs/libXtst in DEPEND
* x11-lib/libXaw is missing x11-libs/libXext and x11-proto/xextproto
in DEPEND
* games-roguelike/tome ebuilds all have typo in ebuilds. Can you spot
it?
I'll give you short example so you don't have to look it up:
DEPEND="${REDEPEND}
x11-misc/makedepend"
For a moment I actually thought that portage has some bug because it
didn't return proper DEPEND packages...Until I saw that typo later on.
Maybe this could be checked in repoman somehow?
So moving on to plan for today and the next week:
* report bugs for mentioned ebuilds
* fix main bugs remaining in collagen
* start to refactor code to make it more pretty for later audit :-)
* start creating web interface for file database using Django
So long and thanks for all the fish,
--
Stanislav Ochotnicky
Working for Gentoo Linux http://www.gentoo.org
Implementing Tree-wide collision checking and provided files database
http://soc.gentooexperimental.org/projects/show/collision-database
Blog: http://inputvalidation.blogspot.com/search/label/gsoc
jabber: sochotnicky@gmail.com
icq: 74274152
PGP: https://dl.getdropbox.com/u/165616/sochotnicky-key.asc
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2009-07-31 9:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-26 12:51 [gentoo-qa] [GSoC-status] Collagen - database schema and further changes Stanislav Ochotnicky
2009-07-03 15:41 ` [gentoo-qa] " Stanislav Ochotnicky
2009-07-09 21:36 ` Stanislav Ochotnicky
2009-07-17 13:39 ` Stanislav Ochotnicky
2009-07-25 22:50 ` Stanislav Ochotnicky
2009-07-31 9:44 ` Stanislav Ochotnicky [this message]
2009-08-07 8:12 ` Stanislav Ochotnicky
[not found] ` <20090807081410.GB29277@w0rm.ynet.sk>
2009-08-15 21:10 ` Stanislav Ochotnicky
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090731094410.GA19452@w0rm \
--to=sochotnicky@gmail.com \
--cc=gentoo-qa@lists.gentoo.org \
--cc=gentoo-soc@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox