Bug#627698: gourmet fails to (re)init database
Juergen Kosel juergen.ko...@gmx.de writes: Package: gourmet Version: 0.15.6-1 Severity: important Hello, Hi, another user on my machine tried to use gourmet. gourmet terminates with the following output: [...] ls -l ~caro/.gourmet/ insgesamt 96 -rw-r--r-- 1 caro caro 405 11. Sep 2009 guiprefs drwxr-xr-x 2 caro caro 4096 11. Sep 2009 html_plugins -rw-r--r-- 1 caro caro 84992 11. Sep 2009 recipes.db To use gourmet files from your home directory ? Christian -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#627698: gourmet fails to (re)init database
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello, Am 05.08.2011 09:39, schrieb Christian Marillat: Juergen Kosel juergen.ko...@gmx.de writes: Package: gourmet Version: 0.15.6-1 Severity: important Hello, Hi, another user on my machine tried to use gourmet. gourmet terminates with the following output: [...] ls -l ~caro/.gourmet/ insgesamt 96 -rw-r--r-- 1 caro caro 405 11. Sep 2009 guiprefs drwxr-xr-x 2 caro caro 4096 11. Sep 2009 html_plugins -rw-r--r-- 1 caro caro 84992 11. Sep 2009 recipes.db To use gourmet files from your home directory ? Yes, at least in the home directory ~caro is the old database located. And gourmet was not told by commandline which database to open, when it failed. Greetings Juergen -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iD8DBQFOPAwm5JgLPmj5988RAvbuAKDy/0kYbKrCAzwlgCVBDFAmqajk5QCfZaa8 yuEEl1J+H+o4G14KmwtvYLA= =6Vmw -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#627698: gourmet fails to (re)init database
Juergen Kosel juergen.ko...@gmx.de writes: [...] ls -l ~caro/.gourmet/ insgesamt 96 -rw-r--r-- 1 caro caro 405 11. Sep 2009 guiprefs drwxr-xr-x 2 caro caro 4096 11. Sep 2009 html_plugins -rw-r--r-- 1 caro caro 84992 11. Sep 2009 recipes.db To use gourmet files from your home directory ? Yes, at least in the home directory ~caro is the old database located. And gourmet was not told by commandline which database to open, when it failed. Then as you can see you don't have rights to write these files and thus update the database fail. You must do a chown -R user .gourmet. Christian -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#627698: gourmet fails to (re)init database
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello,
Am 05.08.2011 19:36, schrieb Christian Marillat:
Juergen Kosel juergen.ko...@gmx.de writes:
[...]
ls -l ~caro/.gourmet/
insgesamt 96
-rw-r--r-- 1 caro caro 405 11. Sep 2009 guiprefs
drwxr-xr-x 2 caro caro 4096 11. Sep 2009 html_plugins
-rw-r--r-- 1 caro caro 84992 11. Sep 2009 recipes.db
To use gourmet files from your home directory ?
soory, I misunderstood your question.
Yes, at least in the home directory ~caro is the old database located.
And gourmet was not told by commandline which database to open, when it
failed.
Then as you can see you don't have rights to write these files and thus
update the database fail.
Loggedin as user caro in working directory /home/caro lead to the buggy
behaviopur, as in the attchment.
Greetings
Juergen
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iD8DBQFOPDAD5JgLPmj5988RAi8mAKCCYGxSpeIa6O5ThFpfIVMdo3SApwCcDepa
Iy+ep+ksByWFNW7b0sl9apE=
=ca9N
-END PGP SIGNATURE-
caro@acer-ilzleite:~$ whoami
caro
caro@acer-ilzleite:~$ gourmet
Database older than 0.14.7 -- updating 0.14.5
Traceback (most recent call last):
File /usr/bin/gourmet, line 35, in module
gourmet.GourmetRecipeManager.startGUI()
File /usr/share/gourmet/gourmet/GourmetRecipeManager.py, line 715, in
startGUI
r=RecGui(splash_label=splash.label)
File /usr/share/gourmet/gourmet/GourmetRecipeManager.py, line 918, in
__init__
GourmetApplication.__init__(self, splash_label=splash_label)
File /usr/share/gourmet/gourmet/GourmetRecipeManager.py, line 114, in
__init__
self.setup_recipes() # Setup recipe database
File /usr/share/gourmet/gourmet/GourmetRecipeManager.py, line 204, in
setup_recipes
self.rd = recipeManager.default_rec_manager()
File /usr/share/gourmet/gourmet/recipeManager.py, line 131, in
default_rec_manager
return get_recipe_manager(**dbargs)
File /usr/share/gourmet/gourmet/recipeManager.py, line 126, in
get_recipe_manager
return RecipeManager(**args)
File /usr/share/gourmet/gourmet/backends/db.py, line 1756, in __init__
RecData.__init__(self,*args,**kwargs)
File /usr/share/gourmet/gourmet/backends/db.py, line 165, in __init__
self.update_version_info(gourmet.version.version)
File /usr/share/gourmet/gourmet/backends/db.py, line 484, in
update_version_info
self.add_column_to_table(self.recipe_table,('yields',Float(),{}))
File /usr/share/gourmet/gourmet/backends/db.py, line 891, in
add_column_to_table
coltyp = coltyp.dialect_impl(self.db.dialect).get_col_spec()
AttributeError: 'Float' object has no attribute 'get_col_spec'
caro@acer-ilzleite:~$ pwd
/home/caro
Bug#627698: gourmet fails to (re)init database
Package: gourmet
Version: 0.15.6-1
Severity: important
Hello,
another user on my machine tried to use gourmet.
gourmet terminates with the following output:
gourmet
Database older than 0.14.7 -- updating 0.14.5
Traceback (most recent call last):
File /usr/bin/gourmet, line 35, in module
gourmet.GourmetRecipeManager.startGUI()
File /usr/share/gourmet/gourmet/GourmetRecipeManager.py, line 715, in
startGUI
r=RecGui(splash_label=splash.label)
File /usr/share/gourmet/gourmet/GourmetRecipeManager.py, line 918, in
__init__
GourmetApplication.__init__(self, splash_label=splash_label)
File /usr/share/gourmet/gourmet/GourmetRecipeManager.py, line 114, in
__init__
self.setup_recipes() # Setup recipe database
File /usr/share/gourmet/gourmet/GourmetRecipeManager.py, line 204, in
setup_recipes
self.rd = recipeManager.default_rec_manager()
File /usr/share/gourmet/gourmet/recipeManager.py, line 131, in
default_rec_manager
return get_recipe_manager(**dbargs)
File /usr/share/gourmet/gourmet/recipeManager.py, line 126, in
get_recipe_manager
return RecipeManager(**args)
File /usr/share/gourmet/gourmet/backends/db.py, line 1756, in __init__
RecData.__init__(self,*args,**kwargs)
File /usr/share/gourmet/gourmet/backends/db.py, line 165, in __init__
self.update_version_info(gourmet.version.version)
File /usr/share/gourmet/gourmet/backends/db.py, line 484, in
update_version_info
self.add_column_to_table(self.recipe_table,('yields',Float(),{}))
File /usr/share/gourmet/gourmet/backends/db.py, line 891, in
add_column_to_table
coltyp = coltyp.dialect_impl(self.db.dialect).get_col_spec()
AttributeError: 'Float' object has no attribute 'get_col_spec'
ls -l ~caro/.gourmet/
insgesamt 96
-rw-r--r-- 1 caro caro 405 11. Sep 2009 guiprefs
drwxr-xr-x 2 caro caro 4096 11. Sep 2009 html_plugins
-rw-r--r-- 1 caro caro 84992 11. Sep 2009 recipes.db
Greetings
Juergen
-- System Information:
Debian Release: 6.0.1
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.38-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=de_DE@euro, LC_CTYPE=de_DE@euro (charmap=ISO-8859-15)
Shell: /bin/sh linked to /bin/dash
Versions of packages gourmet depends on:
ii python 2.6.6-3+squeeze6 interactive high-level object-orie
ii python-central 0.6.16+nmu1 register and build utility for Pyt
ii python-glade2 2.17.0-4 GTK+ bindings: Glade support
ii python-gtk2 2.17.0-4 Python bindings for the GTK+ widge
ii python-imaging 1.1.7-2 Python Imaging Library
ii python-poppler 0.12.1-1+b1 Poppler Python bindings
ii python-reportlab2.4-4ReportLab library to create PDF do
ii python-sqlalchemy 0.6.3-3 SQL toolkit and Object Relational
Versions of packages gourmet recommends:
ii python-gnome2 2.28.1-1 Python bindings for the GNOME desk
ii python-gtkspell 2.25.3-7 Python bindings for the GtkSpell l
gourmet suggests no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
