After installation, the transifex package gives some instructions. Following them leads to a python exception : ---------------------------------------------------------------------- Plus d'information sur le paquetage transifex-1.0.0-5.mga1.noarch To finish the initialization of transifex you will need to go on /usr/share/transifex ./manage.py txcreatedirs ./manage.py txcreatenoticetypes ./manage.py syncdb --noinput ./manage.py migrate to start the transifex server, you will have to use ./manage.py runserver 8088 ---------------------------------------------------------------------- [root@localhost ~]# cd /usr/share/transifex/ [root@localhost transifex]# ./manage.py txcreatedirs Error creating /var/lib/transifex/scratchdir: File exists Creating /var/lib/transifex/scratchdir/storage_files Creating /var/log/transifex [root@localhost transifex]# ./manage.py txcreatenoticetypes Creating or updating notice types Traceback (most recent call last): File "./manage.py", line 20, in <module> execute_manager(settings) File "/usr/lib/python2.7/site-packages/django/core/management/__init__.py", line 438, in execute_manager utility.execute() File "/usr/lib/python2.7/site-packages/django/core/management/__init__.py", line 379, in execute self.fetch_command(subcommand).run_from_argv(self.argv) File "/usr/lib/python2.7/site-packages/django/core/management/base.py", line 191, in run_from_argv self.execute(*args, **options.__dict__) File "/usr/lib/python2.7/site-packages/django/core/management/base.py", line 220, in execute output = self.handle(*args, **options) File "/usr/lib/python2.7/site-packages/django/core/management/base.py", line 351, in handle return self.handle_noargs(**options) File "/usr/share/transifex/../transifex/txcommon/management/commands/txcreatenoticetypes.py", line 20, in handle_noargs create_notice_types() File "/usr/share/transifex/../transifex/txcommon/management/commands/txcreatenoticetypes.py", line 9, in create_notice_types n["description"], n["default"]) File "/usr/lib/python2.7/site-packages/notification/models.py", line 179, in create_notice_type notice_type = NoticeType.objects.get(label=label) File "/usr/lib/python2.7/site-packages/django/db/models/manager.py", line 132, in get return self.get_query_set().get(*args, **kwargs) File "/usr/lib/python2.7/site-packages/django/db/models/query.py", line 344, in get num = len(clone) File "/usr/lib/python2.7/site-packages/django/db/models/query.py", line 82, in __len__ self._result_cache = list(self.iterator()) File "/usr/lib/python2.7/site-packages/django/db/models/query.py", line 273, in iterator for row in compiler.results_iter(): File "/usr/lib/python2.7/site-packages/django/db/models/sql/compiler.py", line 680, in results_iter for rows in self.execute_sql(MULTI): File "/usr/lib/python2.7/site-packages/django/db/models/sql/compiler.py", line 735, in execute_sql cursor.execute(sql, params) File "/usr/lib/python2.7/site-packages/django/db/backends/util.py", line 34, in execute return self.cursor.execute(sql, params) File "/usr/lib/python2.7/site-packages/django/db/backends/sqlite3/base.py", line 234, in execute return Database.Cursor.execute(self, query, params) django.db.utils.DatabaseError: no such table: notification_noticetype
CC: (none) => misc
Source RPM: (none) => transifex
Bug assigned to the package maintainer.
Assignee: bugsquad => misc
Pinging, because nothing has happened with this report for more than 3 months, it still has the status NEW or REOPENED. @ Misc Please set status to ASSIGNED if you think this bug was assigned correctly. If for work flow reasons you can't do that, then please put OK on the whiteboard instead. Don't change anything if you want to be pinged by me in this report again ;)
CC: (none) => marja11
3-monthly ping
Please look at the bottom of this mail to see whether you're the assignee of this bug, if you don't already know whether you are. If you're the assignee: We'd like to know for sure whether this bug was assigned correctly. Please change status to ASSIGNED if it is, or put OK on the whiteboard instead. If you don't have a clue and don't see a way to find out, then please put NEEDHELP on the whiteboard. Please assign back to Bug Squad or to the correct person to solve this bug if we were wrong to assign it to you, and explain why. Thanks :) **************************** @ the reporter and persons in the cc of this bug: If you have any new information that wasn't given before (like this bug being valid for another version of Mageia, too, or it being solved) please tell us. @ the reporter of this bug If you didn't reply yet to a request for more information, please do so within two weeks from now. Thanks all :-D
Assignee: misc => bugsquad
This message is a reminder that Mageia 1 is nearing its end of life. In approximately 25 days from now, Mageia will stop maintaining and issuing updates for Mageia 1. At that time this bug will be closed as WONTFIX (EOL) if it remains open with a Mageia 'version' of '1'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version prior to Mageia 1's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Mageia 1 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete. -- Mageia Bugsquad
Mageia 1 changed to end-of-life (EOL) status on ''1st December''. Mageia 1 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Mageia please feel free to click on "Version" change it against that version of Mageia and reopen this bug. Thank you for reporting this bug and we are sorry it could not be fixed. -- Mageia Bugsquad
Status: NEW => RESOLVEDResolution: (none) => WONTFIX