[csw-maintainers] Buildfarm setup - documentation

[Maciej Bliziński]

On Sat, Oct 05, 2013 at 11:04:03AM +0200, Peter FELECAN wrote:
> "Maciej (Matchek) Bliziński" <maciej at opencsw.org> writes:
>  $ opencsw/.buildsys/v2/bin/pkgdb initdb 2>&1 | tee -a /tmp/pkgdb.log
> ERROR:root:Could not create table <class 'models.CatalogGenData'>: Row size too large. The maximum row size for the used table type, not counting BLOBs, is 65535. You have to change some columns to TEXT or BLOBs
> Traceback (most recent call last):
>   File "opencsw/.buildsys/v2/bin/pkgdb", line 709, in <module>
>     main()
>   File "opencsw/.buildsys/v2/bin/pkgdb", line 457, in main
>     dbc.CreateTables()
>   File "/export/home/peter/opencsw/.buildsys/v2/lib/python/database.py", line 164, in CreateTables
>     table.createTable(ifNotExists=True)
>   File "/opt/csw/lib/python/site-packages/sqlobject/main.py", line 1414, in createTable
>     constraints = conn.createTable(cls)
>   File "/opt/csw/lib/python/site-packages/sqlobject/dbconnection.py", line 510, in createTable
>     self.query(createSql)
>   File "/opt/csw/lib/python/site-packages/sqlobject/dbconnection.py", line 414, in query
>     return self._runWithConnection(self._query, s)
>   File "/opt/csw/lib/python/site-packages/sqlobject/dbconnection.py", line 327, in _runWithConnection
>     val = meth(conn, *args)
>   File "/opt/csw/lib/python/site-packages/sqlobject/dbconnection.py", line 411, in _query
>     self._executeRetry(conn, conn.cursor(), s)
>   File "/opt/csw/lib/python/site-packages/sqlobject/mysql/mysqlconnection.py", line 121, in _executeRetry
>     raise OperationalError(ErrorMessage(e))
> sqlobject.dberrors.OperationalError: Row size too large. The maximum row size for the used table type, not counting BLOBs, is 65535. You have to change some columns to TEXT or BLOBs
 
Hm. This happens when you try to initialize the database and create the
tables, not when you try to insert any data.

Is this the old code or the new code?

If it's the new code, then it's a bug. But I haven't been able to
reproduce it.

If it's the old code, then it's what I mentioned earlier: It's not the
instructions we don't have, it's the code we don't have.

> >> and, BTW I dare to disagree with the idea that
> >> cswutils should not contain pkgdb and it must be run from mgar. The use
> >> case for which I care is when the database server is not the building
> >> machine.
> >
> > There are two separate issues:
> >
> > 1. what there is
> > 2. what there ought to be
> >
> > Maybe it'd be better for some reason if pkgdb worked from /opt/csw/bin
> > (issue 2), but it currently doesn't (issue 1). So if you try running
> > the one from /opt/csw/bin, it will likely fail.
> 
> I understand. However, I gave you an user case where is better to have
> it packaged. What do you think? It's just a question of packaging the
> right and update stuff. What the heck, we have packaged thousands of
> projects but we cannot package our own tools?

We either should package them well or not package them at all. Packaging
them well requires additional time and effort, which we simply don't
have. Is running "svn up" really that hard?

Can we please remove the "install cswutils" line from the instructions?

https://sourceforge.net/apps/trac/gar/browser/csw/mgar/pkg/opencsw-manual/trunk/files/for-maintainers/buildfarm-setup.rst#L166

Maciej
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
URL: <http://lists.opencsw.org/pipermail/maintainers/attachments/20131005/3556a948/attachment.asc>