Discussion:
[Dev] Update of web site code (parabolaweb)
Johannes Krampf
2011-11-29 16:17:23 UTC
Permalink
Hello everyone,

these days I finally managed to merge changes from archweb to
parabolaweb and I published the results at
https://www.johkra.net/gitweb/ .

I would like to help bringing this work forward and hopefully result
in resolving issue 210 [1]. How could I provide further help?

Thanks,

Johannes

[1] https://bugs.parabolagnulinux.org/bugs/issue210
Nicolás Reynolds
2011-11-29 17:56:07 UTC
Permalink
Post by Johannes Krampf
Hello everyone,
these days I finally managed to merge changes from archweb to
parabolaweb and I published the results at
https://www.johkra.net/gitweb/ .
I would like to help bringing this work forward and hopefully result
in resolving issue 210 [1]. How could I provide further help?
great! can you test it locally? otherwise i can pull your changes after
thursday...
--
Salud!
Nicolás Reynolds,
xmpp:***@kiwwwi.com.ar
omb:http://identi.ca/fauno

OTR: C0CB1F0F 01DB5E18 2D634C2A A4626858 E7C7C3A2

http://parabolagnulinux.org
http://endefensadelsl.org

"Freedom [...] is messy" ~ Eben Moglen
Johannes Krampf
2011-11-29 18:58:35 UTC
Permalink
Post by Nicolás Reynolds
Post by Johannes Krampf
Hello everyone,
these days I finally managed to merge changes from archweb to
parabolaweb and I published the results at
https://www.johkra.net/gitweb/ .
I would like to help bringing this work forward and hopefully result
in resolving issue 210 [1]. How could I provide further help?
great! can you test it locally? otherwise i can pull your changes after
thursday...
I have *not* tested it well enough. I suffered from
https://bugs.archlinux.org/task/23228 and couldn't load the fixtures
to test with data. I tested the rest by clicking through the pages and
checking links.

Since I'm not very experienced with Django and the error message is
not concrete enough, I do not understand what exactly is going wrong.
I actually hoped you might know more about this. Do you?
Luke T.Shumaker
2011-11-30 02:41:02 UTC
Permalink
At Tue, 29 Nov 2011 19:58:35 +0100,
Post by Johannes Krampf
Post by Nicolás Reynolds
Post by Johannes Krampf
Hello everyone,
these days I finally managed to merge changes from archweb to
parabolaweb and I published the results at
https://www.johkra.net/gitweb/ .
I would like to help bringing this work forward and hopefully result
in resolving issue 210 [1]. How could I provide further help?
great! can you test it locally? otherwise i can pull your changes after
thursday...
I have *not* tested it well enough. I suffered from
https://bugs.archlinux.org/task/23228 and couldn't load the fixtures
to test with data. I tested the rest by clicking through the pages and
checking links.
Since I'm not very experienced with Django and the error message is
not concrete enough, I do not understand what exactly is going wrong.
I actually hoped you might know more about this. Do you?
Even setting up the old version, I get that error too. Also, it (the
old version) 404s on "/media/*".

So, I have not really been able to test it, but I've added 2 commits.
The first is a bunch of whitespace changes to make future merging
cleaner.
The second is to remove bin/ and lib/, which are set up by virtualenv;
surely we don't want to track those.

https://gitorious.org/parabolaweb/parabolaweb

~ Luke Shumaker
Nicolás Reynolds
2011-11-30 14:04:35 UTC
Permalink
Post by Luke T.Shumaker
At Tue, 29 Nov 2011 19:58:35 +0100,
Post by Johannes Krampf
Post by Nicolás Reynolds
Post by Johannes Krampf
Hello everyone,
these days I finally managed to merge changes from archweb to
parabolaweb and I published the results at
https://www.johkra.net/gitweb/ .
I would like to help bringing this work forward and hopefully result
in resolving issue 210 [1]. How could I provide further help?
great! can you test it locally? otherwise i can pull your changes after
thursday...
I have *not* tested it well enough. I suffered from
https://bugs.archlinux.org/task/23228 and couldn't load the fixtures
to test with data. I tested the rest by clicking through the pages and
checking links.
Since I'm not very experienced with Django and the error message is
not concrete enough, I do not understand what exactly is going wrong.
I actually hoped you might know more about this. Do you?
Even setting up the old version, I get that error too. Also, it (the
old version) 404s on "/media/*".
So, I have not really been able to test it, but I've added 2 commits.
The first is a bunch of whitespace changes to make future merging
cleaner.
The second is to remove bin/ and lib/, which are set up by virtualenv;
surely we don't want to track those.
https://gitorious.org/parabolaweb/parabolaweb
i recommend both of you to test it with sqlite3. we're using postgresql on the
server. this because luke had problems with mysql...
--
Salud!
Nicolás Reynolds,
xmpp:***@kiwwwi.com.ar
omb:http://identi.ca/fauno

OTR: C0CB1F0F 01DB5E18 2D634C2A A4626858 E7C7C3A2

http://parabolagnulinux.org
http://endefensadelsl.org

"Freedom [...] is messy" ~ Eben Moglen
Luke T.Shumaker
2011-11-30 22:41:14 UTC
Permalink
At Wed, 30 Nov 2011 11:04:35 -0300,
[1 <text/plain; utf-8 (quoted-printable)>]
Post by Luke T.Shumaker
At Tue, 29 Nov 2011 19:58:35 +0100,
Post by Johannes Krampf
Post by Nicolás Reynolds
Post by Johannes Krampf
Hello everyone,
these days I finally managed to merge changes from archweb to
parabolaweb and I published the results at
https://www.johkra.net/gitweb/ .
I would like to help bringing this work forward and hopefully result
in resolving issue 210 [1]. How could I provide further help?
great! can you test it locally? otherwise i can pull your changes after
thursday...
I have *not* tested it well enough. I suffered from
https://bugs.archlinux.org/task/23228 and couldn't load the fixtures
to test with data. I tested the rest by clicking through the pages and
checking links.
Since I'm not very experienced with Django and the error message is
not concrete enough, I do not understand what exactly is going wrong.
I actually hoped you might know more about this. Do you?
Even setting up the old version, I get that error too. Also, it (the
old version) 404s on "/media/*".
So, I have not really been able to test it, but I've added 2 commits.
The first is a bunch of whitespace changes to make future merging
cleaner.
The second is to remove bin/ and lib/, which are set up by virtualenv;
surely we don't want to track those.
https://gitorious.org/parabolaweb/parabolaweb
i recommend both of you to test it with sqlite3. we're using postgresql on the
server. this because luke had problems with mysql...
So far I've had tried (and had errors with)
* MySQL/InnoDB (won't work, will require patch if we want it to)
* MySQL/MyISAM (mostly works, idk why)
* sqlite3 (doesn't work, idk why)

To clarify/document:

Parabolaweb does not work with MySQL InnoDB. (Which is odd, because
the local_settings.py.example distributed with archweb explicitly sets
the engine to InnoDB)

Running `./manage.py migrate` will raise an error `1005' (Couldn't
create table) with an errno 121. Errno 121 is undocumented, but
appears to be related to validating references.

This is easily remedied by switching MySQL to MyISAM or another
engine.
DATABASES = {
'default': {
'ENGINE' : 'django.db.backends.mysql',
...
'OPTIONS' : {'init_command': 'SET storage_engine=MyISAM'},
},
}

After some research, this is my analysis of what is causing the issue,
but I may be wrong:

This is because InnoDB does some more advanced things with
references. This is normally identified as a feature.

However, this causes a bug in Django < 1.4. (parabolaweb/archweb use
Django 1.3)
In previous versions of Django, fixtures with forward references
(i.e. relations to rows that have not yet been inserted into the
database) would fail to load when using the InnoDB storage
engine. This was due to the fact that InnoDB deviates from the SQL
standard by checking foreign key constraints immediately instead of
deferring the check until the transaction is committed. This problem
has been resolved in Django 1.4. Fixture data is now loaded with
foreign key checks turned off; foreign key checks are then
re-enabled when the data has finished loading, at which point the
entire table is checked for invalid foreign key references and an
IntegrityError is raised if any are found.
Which appears to exactly describe the error I was having.

After switching to MySQL MyISAM I got farther.
I ran into the same problem that Johannes did
(https://bugs.archlinux.org/task/23228),
By replacing the command
$ ./manage.py loaddata */fixtures/*.json
with
$ for file in */fixtures/*.json; do ./manage.py loaddata $file; done
in order to still load all the other fixtures.

From there the only problem seemed to be that '/media/*' URLs (static
files) would 404. I'd now guess that this is caused by something
misconfigured in local_settings.py, not an external dependency.

When I tried with sqlite3, setting it up was identical to setting it
up with MySQL MyISAM. However, when I ran the server I got 500 (server
ViewDoesNotExist: Could not import packages.views. Error was: cannot
import name SignoffSpecification
Happy Hacking!
~ Luke Shumaker
Luke T.Shumaker
2011-11-30 22:46:25 UTC
Permalink
At Wed, 30 Nov 2011 17:41:14 -0500,
Post by Luke T.Shumaker
When I tried with sqlite3, setting it up was identical to setting it
up with MySQL MyISAM. However, when I ran the server I got 500 (server
ViewDoesNotExist: Could not import packages.views. Error was: cannot
import name SignoffSpecification
Oops, I forgot to attatch the file

~ Luke Shumaker
Johannes Krampf
2011-11-30 23:00:07 UTC
Permalink
Just a short note: If you set debug to True in local settings, media
URLs should work automatically.

My tests were done with sqlite3, I got the same errors with innodb as
Luke. I haven't tried with postgres or myisam. I could successfully
run the server, but I had no fixtures loaded for my limited tests.
Post by Luke T.Shumaker
At Wed, 30 Nov 2011 17:41:14 -0500,
Post by Luke T.Shumaker
When I tried with sqlite3, setting it up was identical to setting it
up with MySQL MyISAM. However, when I ran the server I got 500 (server
ViewDoesNotExist: Could not import packages.views. Error was: cannot
import name SignoffSpecification
Oops, I forgot to attatch the file
~ Luke Shumaker
 File "/srv/http/web-env/lib/python2.7/site-packages/django/core/servers/basehttp.py", line 283, in run
   self.result = application(self.environ, self.start_response)
 File "/srv/http/web-env/lib/python2.7/site-packages/django/contrib/staticfiles/handlers.py", line 68, in __call__
   return self.application(environ, start_response)
 File "/srv/http/web-env/lib/python2.7/site-packages/django/core/handlers/wsgi.py", line 272, in __call__
   response = self.get_response(request)
 File "/srv/http/web-env/lib/python2.7/site-packages/django/core/handlers/base.py", line 169, in get_response
   response = self.handle_uncaught_exception(request, resolver, sys.exc_info())
 File "/srv/http/web-env/lib/python2.7/site-packages/django/core/handlers/base.py", line 218, in handle_uncaught_exception
   return callback(request, **param_dict)
 File "/srv/http/web-env/lib/python2.7/site-packages/django/utils/decorators.py", line 93, in _wrapped_view
   response = view_func(request, *args, **kwargs)
 File "/srv/http/web-env/lib/python2.7/site-packages/django/views/defaults.py", line 31, in server_error
   return http.HttpResponseServerError(t.render(Context({})))
 File "/srv/http/web-env/lib/python2.7/site-packages/django/template/base.py", line 123, in render
   return self._render(context)
 File "/srv/http/web-env/lib/python2.7/site-packages/django/template/base.py", line 117, in _render
   return self.nodelist.render(context)
 File "/srv/http/web-env/lib/python2.7/site-packages/django/template/base.py", line 744, in render
   bits.append(self.render_node(node, context))
 File "/srv/http/web-env/lib/python2.7/site-packages/django/template/base.py", line 757, in render_node
   return node.render(context)
 File "/srv/http/web-env/lib/python2.7/site-packages/django/template/loader_tags.py", line 127, in render
   return compiled_parent._render(context)
 File "/srv/http/web-env/lib/python2.7/site-packages/django/template/base.py", line 117, in _render
   return self.nodelist.render(context)
 File "/srv/http/web-env/lib/python2.7/site-packages/django/template/base.py", line 744, in render
   bits.append(self.render_node(node, context))
 File "/srv/http/web-env/lib/python2.7/site-packages/django/template/base.py", line 757, in render_node
   return node.render(context)
 File "/srv/http/web-env/lib/python2.7/site-packages/django/template/defaulttags.py", line 437, in render
   url = reverse(view_name, args=args, kwargs=kwargs, current_app=context.current_app)
 File "/srv/http/web-env/lib/python2.7/site-packages/django/core/urlresolvers.py", line 391, in reverse
   *args, **kwargs)))
 File "/srv/http/web-env/lib/python2.7/site-packages/django/core/urlresolvers.py", line 312, in reverse
   possibilities = self.reverse_dict.getlist(lookup_view)
 File "/srv/http/web-env/lib/python2.7/site-packages/django/core/urlresolvers.py", line 229, in _get_reverse_dict
   self._populate()
 File "/srv/http/web-env/lib/python2.7/site-packages/django/core/urlresolvers.py", line 220, in _populate
   lookups.appendlist(pattern.callback, (bits, p_pattern))
 File "/srv/http/web-env/lib/python2.7/site-packages/django/core/urlresolvers.py", line 167, in _get_callback
   raise ViewDoesNotExist("Could not import %s. Error was: %s" % (mod_name, str(e)))
ViewDoesNotExist: Could not import packages.views. Error was: cannot import name SignoffSpecification
Luke T.Shumaker
2011-12-01 03:02:34 UTC
Permalink
At Thu, 1 Dec 2011 00:00:07 +0100,
Post by Johannes Krampf
Just a short note: If you set debug to True in local settings, media
URLs should work automatically.
So is it nescessary to set DEBUG=True in order for /media to work? That
sounds like a bug. How is DEBUG set on the main server?
Post by Johannes Krampf
My tests were done with sqlite3, I got the same errors with innodb as
Luke. I haven't tried with postgres or myisam. I could successfully
run the server, but I had no fixtures loaded for my limited tests.
Now I've tried MySQL MyISAM with DEBUG=true, and discovered that I get
the same stacktrace as I did with sqlite3, so that appears to be
something else I fouled up in between (sqlite3 was the last thing I
did yesterday).

~ Luke Shumaker
Nicolás Reynolds
2011-12-01 04:35:52 UTC
Permalink
Post by Luke T.Shumaker
At Thu, 1 Dec 2011 00:00:07 +0100,
Post by Johannes Krampf
Just a short note: If you set debug to True in local settings, media
URLs should work automatically.
So is it nescessary to set DEBUG=True in order for /media to work? That
sounds like a bug. How is DEBUG set on the main server?
Post by Johannes Krampf
My tests were done with sqlite3, I got the same errors with innodb as
Luke. I haven't tried with postgres or myisam. I could successfully
run the server, but I had no fixtures loaded for my limited tests.
Now I've tried MySQL MyISAM with DEBUG=true, and discovered that I get
the same stacktrace as I did with sqlite3, so that appears to be
something else I fouled up in between (sqlite3 was the last thing I
did yesterday).
we are using debug=false and

## location for saving dev pictures
MEDIA_ROOT = '/srv/http/web/media/'

## web url for serving image files
MEDIA_URL = 'http://parabolagnulinux.org/media/'

but we aren't using the virtualenv nor the pip packages.
--
Salud!
Nicolás Reynolds,
xmpp:***@kiwwwi.com.ar
omb:http://identi.ca/fauno

OTR: C0CB1F0F 01DB5E18 2D634C2A A4626858 E7C7C3A2

http://parabolagnulinux.org
http://endefensadelsl.org

"Freedom [...] is messy" ~ Eben Moglen
Luke T.Shumaker
2011-12-01 04:50:34 UTC
Permalink
OK, I got the old version working great with MySQL MyISAM. I have two
comments about it:
* As far as I can tell, DEBUG needs to be true for /media to
work. WTF?
* Bug: `media/silhouette.png' should be at
`media/devs/silhouette.png'

I then upgraded it to the Johannes'/my new version. This version is
NOT ready to be deployed. Everything works great, except viewing a
single package, for which it 500s. This does appear to be a bug with
our code.

Info/Stack trace:
http://dpaste.com/664189/ (before deps update)
http://dpaste.com/664190/ (after deps update)
(that's cool, it gave me a button to click to automagically post it to
dpaste)

Steps to be taken when upgrading:
* git pull/checkout
* remove .pyc files (cause weird bugs if they don't get purged)
* $ ./manage.py migrate
* $ for file in */fixtures/*.json; do ./manage.py loaddata $file; done
* pip install -r requirements_prod.txt
This is to update Django and other deps, but doesn't appear to be
nescessary. What changed:
* Django 1.3 => 1.3.1
* pyinotify (new)
* pytz 2011c => 2011n

I'll go ahead and move silhouette.png in my copy, and try to fix the
package pages.

My copy: https://gitorious.org/parabolaweb/parabolaweb

~ Luke Shumaker

PS: In my test configuration, I have the environment in a separate
directory (/srv/http/web-env, where the install is at
/srv/http/web). I'm guessing from a few stray files in git that on the
server you set up the environment in the same directory. Since I
removed the stray files from git in my, they will be deleted when you
pull. That would be bad. Migrating the environment to a separate
directory before then would probably be a good idea. (To be clear, I'm
not saying you should change because I deleted the files, I'm saying
you should change because you should have the env separate)

At Wed, 30 Nov 2011 22:02:34 -0500,
Post by Luke T.Shumaker
At Thu, 1 Dec 2011 00:00:07 +0100,
Post by Johannes Krampf
Just a short note: If you set debug to True in local settings, media
URLs should work automatically.
So is it nescessary to set DEBUG=True in order for /media to work? That
sounds like a bug. How is DEBUG set on the main server?
Post by Johannes Krampf
My tests were done with sqlite3, I got the same errors with innodb as
Luke. I haven't tried with postgres or myisam. I could successfully
run the server, but I had no fixtures loaded for my limited tests.
Now I've tried MySQL MyISAM with DEBUG=true, and discovered that I get
the same stacktrace as I did with sqlite3, so that appears to be
something else I fouled up in between (sqlite3 was the last thing I
did yesterday).
~ Luke Shumaker
Luke T.Shumaker
2011-12-01 06:33:15 UTC
Permalink
At Thu, 1 Dec 2011 01:35:52 -0300,
Post by Nicolás Reynolds
we are using debug=false and
## location for saving dev pictures
MEDIA_ROOT = '/srv/http/web/media/'
## web url for serving image files
MEDIA_URL = 'http://parabolagnulinux.org/media/'
That's really weird then, I have no idea why I have to set debug=true
for it to work for us.
Post by Nicolás Reynolds
but we aren't using the virtualenv nor the pip packages.
That's great, because I was worried that me removing the outdated
virtualenv files that were wrongfully put into git would cause a
problem.

At Wed, 30 Nov 2011 23:50:34 -0500,
Post by Nicolás Reynolds
OK, I got the old version working great with MySQL MyISAM. I have two
* As far as I can tell, DEBUG needs to be true for /media to
work. WTF?
* Bug: `media/silhouette.png' should be at
`media/devs/silhouette.png'
I then upgraded it to the Johannes'/my new version. This version is
NOT ready to be deployed. Everything works great, except viewing a
single package, for which it 500s. This does appear to be a bug with
our code.
I'll go ahead and move silhouette.png in my copy, and try to fix the
package pages.
I think I've done this. As far as I can tell, my version is running
great, with no problems that I can tell.
Post by Nicolás Reynolds
My copy: https://gitorious.org/parabolaweb/parabolaweb
* git pull/checkout
* remove .pyc files (cause weird bugs if they don't get purged)
* $ ./manage.py migrate
* $ for file in */fixtures/*.json; do ./manage.py loaddata $file; done
* pip install -r requirements_prod.txt
This is to update Django and other deps, but doesn't appear to be
* Django 1.3 => 1.3.1
* pyinotify (new)
* pytz 2011c => 2011n
I know you're not managing them with pip, but I'd check to make sure
that pacman has those versions installed.

Also make sure that the symlink at media/admin_media is right.

~ Luke Shumaker
Johannes Krampf
2011-12-01 07:49:00 UTC
Permalink
Post by Luke T.Shumaker
At Wed, 30 Nov 2011 23:50:34 -0500,
Post by Luke T.Shumaker
OK, I got the old version working great with MySQL MyISAM. I have two
 * As far as I can tell, DEBUG needs to be true for /media to
   work. WTF?
You only have to set DEBUG to True if you use the integrated server
(./manage.py runserver) for media to work correctly.

On a real deployment you would use Django with wsgi and have your web
server manage serving of static files.
Post by Luke T.Shumaker
Post by Luke T.Shumaker
I then upgraded it to the Johannes'/my new version. This version is
NOT ready to be deployed. Everything works great, except viewing a
single package, for which it 500s. This does appear to be a bug with
our code.
The stacktraces look like bugs in the template markup which I have
introduced when merging. I'll have a look at it this evening, thanks
for your testing!
Luke T.Shumaker
2011-12-01 12:31:55 UTC
Permalink
At Thu, 1 Dec 2011 08:49:00 +0100,
Post by Johannes Krampf
Post by Luke T.Shumaker
At Wed, 30 Nov 2011 23:50:34 -0500,
Post by Luke T.Shumaker
OK, I got the old version working great with MySQL MyISAM. I have two
 * As far as I can tell, DEBUG needs to be true for /media to
   work. WTF?
You only have to set DEBUG to True if you use the integrated server
(./manage.py runserver) for media to work correctly.
On a real deployment you would use Django with wsgi and have your web
server manage serving of static files.
Post by Luke T.Shumaker
Post by Luke T.Shumaker
I then upgraded it to the Johannes'/my new version. This version is
NOT ready to be deployed. Everything works great, except viewing a
single package, for which it 500s. This does appear to be a bug with
our code.
The stacktraces look like bugs in the template markup which I have
introduced when merging. I'll have a look at it this evening, thanks
for your testing!
I've already fixed it.

My copy: https://gitorious.org/parabolaweb/parabolaweb

~ Luke Shumaker
Nicolás Reynolds
2011-12-01 13:13:41 UTC
Permalink
Post by Johannes Krampf
Post by Luke T.Shumaker
At Wed, 30 Nov 2011 23:50:34 -0500,
Post by Luke T.Shumaker
OK, I got the old version working great with MySQL MyISAM. I have two
 * As far as I can tell, DEBUG needs to be true for /media to
   work. WTF?
You only have to set DEBUG to True if you use the integrated server
(./manage.py runserver) for media to work correctly.
On a real deployment you would use Django with wsgi and have your web
server manage serving of static files.
Post by Luke T.Shumaker
Post by Luke T.Shumaker
I then upgraded it to the Johannes'/my new version. This version is
NOT ready to be deployed. Everything works great, except viewing a
single package, for which it 500s. This does appear to be a bug with
our code.
The stacktraces look like bugs in the template markup which I have
introduced when merging. I'll have a look at it this evening, thanks
for your testing!
I'll summary changes we have done so far to rebrand the site:

* Change "arch ?linux" strings to "Parabola GNU/Linux-libre" (this is done in
templates, site name should be used)

* Change "devs" for "hackers" (we like it more :P)

* Remove AUR mentions

* Download page redirects to wiki (easier to update)

* Add "flag as unfree" and "report bug" links to our bug tracker

Please check there's no downgrade in this areas

Thanks for your work!
--
Salud!
Nicolás Reynolds,
xmpp:***@kiwwwi.com.ar
omb:http://identi.ca/fauno

OTR: C0CB1F0F 01DB5E18 2D634C2A A4626858 E7C7C3A2

http://parabolagnulinux.org
http://endefensadelsl.org

"Freedom [...] is messy" ~ Eben Moglen
Luke T.Shumaker
2011-12-02 02:02:38 UTC
Permalink
At Thu, 1 Dec 2011 10:13:41 -0300,
Post by Nicolás Reynolds
* Change "arch ?linux" strings to "Parabola GNU/Linux-libre" (this is done in
templates, site name should be used)
I believe that all references to Arch have been replaced, but it's
possible that we missed one. (grep isn't helpfull, it's still used in
css/classnames, and can refer to architecture) "Parabola" is hardcoded
in many places, should we change it to use a tag?
Post by Nicolás Reynolds
* Change "devs" for "hackers" (we like it more :P)
Definately has changed.
Post by Nicolás Reynolds
* Remove AUR mentions
`grep -i 'aur' .` returns nothing
Post by Nicolás Reynolds
* Download page redirects to wiki (easier to update)
Definately.
Post by Nicolás Reynolds
* Add "flag as unfree" and "report bug" links to our bug tracker
They're there.
Post by Nicolás Reynolds
Please check there's no downgrade in this areas
Thanks for your work!
~ Luke Shumaker
Johannes Krampf
2011-12-02 18:26:28 UTC
Permalink
Hello everyone,

I fixed bug tracker URLs (introduced in my merge) and some spelling in
the README Luke updated so kindly for parabolaweb. (See
https://www.johkra.net/gitweb/?p=parabolaweb-johkra.git;a=summary )

Luke: Why is the symlink for admin_media needed?

Remaining issues I know of:
* Download links for packages do not work. (404)
* migrate doesn't work with sqlite unless you change one migration.
(Remove the drop index statement for the index referenced in the error
message.)
* InnoDB doesn't work (see earlier messages)
* groups.json fails to load

Did I miss anything? I'll have a look at the first one, what should we
do about the others? Should we fix them before updating the main page?

- Johannes
Nicolás Reynolds
2011-12-02 18:29:44 UTC
Permalink
Post by Johannes Krampf
Hello everyone,
I fixed bug tracker URLs (introduced in my merge) and some spelling in
the README Luke updated so kindly for parabolaweb. (See
https://www.johkra.net/gitweb/?p=parabolaweb-johkra.git;a=summary )
Luke: Why is the symlink for admin_media needed?
* Download links for packages do not work. (404)
* migrate doesn't work with sqlite unless you change one migration.
(Remove the drop index statement for the index referenced in the error
message.)
* InnoDB doesn't work (see earlier messages)
* groups.json fails to load
Did I miss anything? I'll have a look at the first one, what should we
do about the others? Should we fix them before updating the main page?
if they don't hit postgresql i'd said you don't spend time on it :P

the download links should point to
https://repo.parabolagnulinux.org/$repo/os/$arch/$pkgfile
--
Salud!
Nicolás Reynolds,
xmpp:***@kiwwwi.com.ar
omb:http://identi.ca/fauno

OTR: C0CB1F0F 01DB5E18 2D634C2A A4626858 E7C7C3A2

http://parabolagnulinux.org
http://endefensadelsl.org

"Freedom [...] is messy" ~ Eben Moglen
Johannes Krampf
2011-12-02 18:49:23 UTC
Permalink
Post by Nicolás Reynolds
Post by Johannes Krampf
[...]
Luke: Why is the symlink for admin_media needed?
OK, the link is to correct a symlink.
Post by Nicolás Reynolds
if they don't hit postgresql i'd said you don't spend time on it :P
Indeed, I have not yet looked at postgres.
Post by Nicolás Reynolds
the download links should point to
https://repo.parabolagnulinux.org/$repo/os/$arch/$pkgfile
Done, even though it is a hack.
Luke T.Shumaker
2011-12-02 21:50:24 UTC
Permalink
At Fri, 2 Dec 2011 19:49:23 +0100,
Post by Johannes Krampf
Post by Nicolás Reynolds
Post by Johannes Krampf
[...]
Luke: Why is the symlink for admin_media needed?
OK, the link is to correct a symlink.
Post by Nicolás Reynolds
if they don't hit postgresql i'd said you don't spend time on it :P
Indeed, I have not yet looked at postgres.
Post by Nicolás Reynolds
the download links should point to
https://repo.parabolagnulinux.org/$repo/os/$arch/$pkgfile
Done, even though it is a hack.
I've merged your code (I'd also fixed a few things since you
pulled mine). Both of our code is now in the parabola.org repo.

Also, when possible I've used '//parabolagnulinux.org' (or whatever
domain) for the *.parabolagnulinux.org addresses, instead of giving
`http:' or `https:'. Why hardcode something when you can just let the
browser do the right thing?

~ Luke Shumaker
Johannes Krampf
2011-12-03 12:09:29 UTC
Permalink
Are we using postgres on the server? If not, we should. Everything
works just fine with postgres.

Anyway, I introduced some small changes to the fixtures to workaround
the groups problem and add the mips64el architecture. Furthermore, I
merged the latest archweb changes. (For now in my repo.)
Luke T.Shumaker
2011-12-03 19:22:39 UTC
Permalink
At Sat, 3 Dec 2011 13:09:29 +0100,
Post by Johannes Krampf
Are we using postgres on the server? If not, we should. Everything
works just fine with postgres.
AFAIK, yes, the server uses postres.
Post by Johannes Krampf
Anyway, I introduced some small changes to the fixtures to workaround
the groups problem and add the mips64el architecture. Furthermore, I
merged the latest archweb changes. (For now in my repo.)
I just pushed it to the parabolaweb repo.

Also, attatched is my .git/config, it makes pushing/pulling easier.

~ Luke Shumaker
Nicolás Reynolds
2011-12-02 22:22:55 UTC
Permalink
Post by Johannes Krampf
Post by Nicolás Reynolds
Post by Johannes Krampf
[...]
Luke: Why is the symlink for admin_media needed?
OK, the link is to correct a symlink.
Post by Nicolás Reynolds
if they don't hit postgresql i'd said you don't spend time on it :P
Indeed, I have not yet looked at postgres.
Post by Nicolás Reynolds
the download links should point to
https://repo.parabolagnulinux.org/$repo/os/$arch/$pkgfile
Done, even though it is a hack.
send me a ssh pubkey (gpg signed is better :) so you can have push access to the repo
--
Salud!
Nicolás Reynolds,
xmpp:***@kiwwwi.com.ar
omb:http://identi.ca/fauno

OTR: C0CB1F0F 01DB5E18 2D634C2A A4626858 E7C7C3A2

http://parabolagnulinux.org
http://endefensadelsl.org

"Freedom [...] is messy" ~ Eben Moglen
Nicolás Reynolds
2011-12-05 01:56:52 UTC
Permalink
Post by Nicolás Reynolds
send me a ssh pubkey (gpg signed is better :) so you can have push access to the repo
GPG-key: https://www.johkra.net/johannes.krampf.gpg_pub
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
iF4EABEIAAYFAk7Z/WcACgkQX9mcc7q4PtHtpwD9H4g6dG0FtGb99hBJ9PCuxgMP
8tLimiBdpBNTDVCdVVQBAMmhrB/wTumUDJj8hkgOTV/M1gxtIzky4UG7ECcxqnI1
=+une
-----END PGP SIGNATURE-----
you have push permission now :D
--
Salud!
Nicolás Reynolds,
xmpp:***@kiwwwi.com.ar
omb:http://identi.ca/fauno

OTR: C0CB1F0F 01DB5E18 2D634C2A A4626858 E7C7C3A2

http://parabolagnulinux.org
http://endefensadelsl.org

"Freedom [...] is messy" ~ Eben Moglen
Luke T.Shumaker
2011-12-02 21:28:14 UTC
Permalink
At Fri, 2 Dec 2011 19:26:28 +0100,
Post by Johannes Krampf
Hello everyone,
I fixed bug tracker URLs (introduced in my merge) and some spelling in
the README Luke updated so kindly for parabolaweb. (See
https://www.johkra.net/gitweb/?p=parabolaweb-johkra.git;a=summary )
Luke: Why is the symlink for admin_media needed?
The symlink is already there, but it may not point to the right
place. Just confirm that the setup hasn't changed, and the target is
still in the same place on the server.
Post by Johannes Krampf
* Download links for packages do not work. (404)
* migrate doesn't work with sqlite unless you change one migration.
(Remove the drop index statement for the index referenced in the error
message.)
* InnoDB doesn't work (see earlier messages)
This is an upstream problem with Archweb. The solution is to upgrade
parabolaweb to Django 1.4 (from 1.3.1)
Post by Johannes Krampf
* groups.json fails to load
This is an upstream problem with Archweb, but I don't know what causes it.
Post by Johannes Krampf
Did I miss anything? I'll have a look at the first one, what should we
do about the others? Should we fix them before updating the main page?
- Johannes
Nicolás Reynolds
2011-12-05 02:13:49 UTC
Permalink
Post by Johannes Krampf
Hello everyone,
these days I finally managed to merge changes from archweb to
parabolaweb and I published the results at
https://www.johkra.net/gitweb/ .
I would like to help bringing this work forward and hopefully result
in resolving issue 210 [1]. How could I provide further help?
I've updated parabolaweb on the server! Also I pulled changes on my local copy
and while merging I found a missing "Arch" string. You can pull from
git://kiwwwi.com.ar/parabolaweb

I had to fix the admin_media symlink to the one in the django package. I also
submitted a bug report about css, you should have received email.

Thanks you both!
--
Salud!
Nicolás Reynolds,
xmpp:***@kiwwwi.com.ar
omb:http://identi.ca/fauno

OTR: C0CB1F0F 01DB5E18 2D634C2A A4626858 E7C7C3A2

http://parabolagnulinux.org
http://endefensadelsl.org

"Freedom [...] is messy" ~ Eben Moglen
Luke T.Shumaker
2011-12-05 04:04:05 UTC
Permalink
At Sun, 4 Dec 2011 23:13:49 -0300,
Post by Nicolás Reynolds
Post by Johannes Krampf
Hello everyone,
these days I finally managed to merge changes from archweb to
parabolaweb and I published the results at
https://www.johkra.net/gitweb/ .
I would like to help bringing this work forward and hopefully result
in resolving issue 210 [1]. How could I provide further help?
I've updated parabolaweb on the server! Also I pulled changes on my local copy
and while merging I found a missing "Arch" string. You can pull from
git://kiwwwi.com.ar/parabolaweb
You have to pull from 'git://kiwwwi.com.ar/parabolaweb/' or it
won't work. The trailing slash is important :P
Post by Nicolás Reynolds
I had to fix the admin_media symlink to the one in the django
package.
I've just updated the parabolaweb.install to take care of the
symlink. I've also changed the symlink in git.
Post by Nicolás Reynolds
I also
submitted a bug report about css, you should have received email.
I've just fixes to the CSS, and a few other fixes to git.
Post by Nicolás Reynolds
Thanks you both!
--
Salud!
Nicolás Reynolds,
omb:http://identi.ca/fauno
OTR: C0CB1F0F 01DB5E18 2D634C2A A4626858 E7C7C3A2
http://parabolagnulinux.org
http://endefensadelsl.org
"Freedom [...] is messy" ~ Eben Moglen
Loading...