Bug#425742: gnome-session: deleting liferea from the session manually solved hanging for me

2007-06-07 Thread Balazs Ree
Package: gnome-session Version: 2.18.2-1 Followup-For: Bug #425742 I am suffering from a similar case after a recent upgrade: session freezes after the splash screen pops up. Recently I realized that in my case the liferea application caused the problem. If I manually deleted liferea from my

Bug#373710: change back /lib/python2.4/site-packages to /lib/python

2006-06-18 Thread Balazs Ree
.) -- Balazs Ree --- debian/rules 2006-06-18 13:45:43.0 +0200 +++ /tmp/rules 2006-06-18 13:30:37.0 +0200 @@ -84,7 +84,7 @@ # Install Zope and remove *.pyc cd z $(PYTHONBIN) install.py install \ - --skip-build --prefix $(DEBIAN)/usr/lib/zope$(ZVER) + --skip-build --home $(DEBIAN

Bug#373710: zope2.9: zopectl test broken due to: ZOPE_HOME is not exported from zopectl, runzope skeletons

2006-06-15 Thread Balazs Ree
Package: zope2.9 Version: 2.9.3-2 Severity: normal ... and this, combined with the fact that Debian changed the distribution path /lib/python to /lib/python2.4/site-packages, makes it impossible to run tests from zopectl with instances created with these skeletons. This is because Zope startup

Bug#342894: zope-cmfmember: Not the same package version + please upgrade

2005-12-11 Thread Balazs Ree
Package: zope-cmfmember Severity: important The version of CMFMember in this package is not really 1.1b5 as the debian package information states but 1.0b5 (1.0 beta5). Also, this version does not work with Plone 2.1 so please upgrade the package to upstream version 1.1b2 (1.1-beta2). This is

Bug#341529: zope3: init.d bug: zeo instances not started

2005-12-01 Thread Balazs Ree
Package: zope3 Version: 3.1.0-3 Severity: normal Please consider the following patch. --- debian/zopeZVER.init.in 2005-12-01 08:25:58.495475902 +0100 +++ /tmp/zopeZVER.init.in 2005-12-01 08:29:08.234884902 +0100 @@ -26,7 +26,7 @@ if [ -n $ZEOSERVERS ]; then cd

Bug#341526: zope2.7: init.d bug: zeo instances not started

2005-11-30 Thread Balazs Ree
Package: zope2.7 Version: 2.7.8-1 Severity: normal Please consider the following patch. --- debian/zopeZVER.init.in 2005-12-01 08:25:58.495475902 +0100 +++ /tmp/zopeZVER.init.in 2005-12-01 08:29:08.234884902 +0100 @@ -26,7 +26,7 @@ if [ -n $ZEOSERVERS ]; then

Bug#341527: zope2.8: init.d bug: zeo instances not started

2005-11-30 Thread Balazs Ree
Package: zope2.8 Version: 2.8.3-1 Severity: normal Please consider the following patch. --- debian/zopeZVER.init.in 2005-12-01 08:25:58.495475902 +0100 +++ /tmp/zopeZVER.init.in 2005-12-01 08:29:08.234884902 +0100 @@ -26,7 +26,7 @@ if [ -n $ZEOSERVERS ]; then

Bug#325315: zsh-beta: broken symlinks after last update, zsh cannot start

2005-08-27 Thread Balazs Ree
Package: zsh-beta Version: 4.3.0-dev-1+20050823-1 Severity: important After the last update zsh did not start up and as a consequence I was even unable to log in as root (as I use zsh for root as well) when trying to fix the problem. After the update, I realized that /etc/alternatives/zsh and

Bug#305854: zope2.7: 2.7.5-2 confirmed

2005-05-02 Thread Balazs Ree
anything, unless someone would want to manually symlink test.py out to some other location and run it from there, but as the designated way is now to run test.py via zopectl, this should not be a big worry. IMO.) Balazs Ree -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject

Bug#304458: zope-testcase: cannot import ZopeTestCase with zope2.7 multi-product-dir setup

2005-04-13 Thread Balazs Ree
Package: zope-testcase Version: 0.9.0-1 Severity: normal I use zope2.7 with a multi-product dir setup, i.e. both the product paths (and libs) in /usr/lib/zope2.7 and /usr/lib/zope are searched and this is properly configured in zope.conf and working correctly in zope. But when it comes to