You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Title the ipv6_only field is not created by the initial SQL setup
Priority urgent Status resolved
Superseder Nosy List dagobert, floeff, jcpunk, poeml, rhertzog
Assigned To Keywords
I followed the instructions from the manual to setup the database
(http://www.mirrorbrain.org/docs/installation/debian/#install-postgresql):
sudo su - mirrorbrain
gunzip -c /usr/share/doc/mirrorbrain/sql/schema-postgresql.sql.gz | psql -U
mirrorbrain mirrorbrain
gunzip -c /usr/share/doc/mirrorbrain/sql/initialdata-postgresql.sql.gz | psql -U
mirrorbrain mirrorbrain
But the schema-postgresql.sql.gz doesn't contain the ipv6_only field and yet the
schema version is set as if it were the case. So I had to fix the schema myself
with:
echo "ALTER TABLE server ADD COLUMN ipv6_only boolean NOT NULL default 'f';" |
psql -U mirrorbrain mirrorbrain
Without this, mirrorbrain would not work at all.
Note that I use the Debian package of mirrorbrain:
$ dpkg -s mirrorbrain
Package: mirrorbrain
Status: install ok installed
Priority: extra
Section: web
Installed-Size: 280
Maintainer: Peter Poeml poeml@cmdline.net
Architecture: amd64
Version: 2.17.0-1
Depends: adduser
Description: MirrorBrain is a scalable download redirector and Metalink generator.
I was using the 2.17.0 tarball. My suggestion was adding this field to the schema
upgrade script which you also provided for older versions. After altering the
table it looks good for me now.
However, it took me a while to figure out what was wrong as the code just bailed
out in the relational mapping code.
Issue migrated (2015-06-05) from old issue tracker http://mirrorbrain.org/issues/issue119
msg418 (view) Author: rhertzog Date: 2013-02-25.16:03:48
I followed the instructions from the manual to setup the database
(http://www.mirrorbrain.org/docs/installation/debian/#install-postgresql):
sudo su - mirrorbrain
gunzip -c /usr/share/doc/mirrorbrain/sql/schema-postgresql.sql.gz | psql -U
mirrorbrain mirrorbrain
gunzip -c /usr/share/doc/mirrorbrain/sql/initialdata-postgresql.sql.gz | psql -U
mirrorbrain mirrorbrain
But the schema-postgresql.sql.gz doesn't contain the ipv6_only field and yet the
schema version is set as if it were the case. So I had to fix the schema myself
with:
echo "ALTER TABLE server ADD COLUMN ipv6_only boolean NOT NULL default 'f';" |
psql -U mirrorbrain mirrorbrain
Without this, mirrorbrain would not work at all.
Note that I use the Debian package of mirrorbrain:
$ dpkg -s mirrorbrain
Package: mirrorbrain
Status: install ok installed
Priority: extra
Section: web
Installed-Size: 280
Maintainer: Peter Poeml poeml@cmdline.net
Architecture: amd64
Version: 2.17.0-1
Depends: adduser
Description: MirrorBrain is a scalable download redirector and Metalink generator.
msg421 (view) Author: floeff Date: 2013-03-14.16:30:29
Can confirm this for the Ubuntu 11.10 packages. Same problem, same fix that helped.
msg424 (view) Author: jcpunk Date: 2013-04-19.19:07:58
Looks like this was fixed in the source tree:
http://svn.mirrorbrain.org/viewvc/mirrorbrain?view=revision&revision=8292
msg440 (view) Author: poeml Date: 2014-01-02.23:38:56
Indeed, this bug had already been fixed a while ago, but no release was done, so it
slept in the source trunk.
Big sorry about that.
I'll close the report. (Thanks for it.) I'm confident that the next release is near...
msg474 (view) Author: dagobert Date: 2014-01-25.18:09:07
The issue also hit me now, can you please add the new field to the version migration
sql script?
msg480 (view) Author: poeml Date: 2014-01-27.21:00:22
Dagobert, the field should already be added automatically if you use the SVN trunk. See
http://svn.mirrorbrain.org/viewvc/mirrorbrain/trunk/mb/mb/conn.py?r1=8198&r2=8267
Were you still be hit by the issue, or were you using the last released codebase?
msg482 (view) Author: dagobert Date: 2014-01-27.21:15:31
I was using the 2.17.0 tarball. My suggestion was adding this field to the schema
upgrade script which you also provided for older versions. After altering the
table it looks good for me now.
However, it took me a while to figure out what was wrong as the code just bailed
out in the relational mapping code.
msg483 (view) Author: dagobert Date: 2014-01-27.21:18:01
Ah, never mind, I now saw the upgrading code is actually already in trunk.
msg513 (view) Author: poeml Date: 2014-02-02.12:35:26
Fixed in 2.18.0. Thanks everyone!
(end of migrated issue)
The text was updated successfully, but these errors were encountered: