The access bug was due to old beta v5 databases. Once new databases were
created then everything works fine. So no more access problem.
Fabien, Stephane,
Can you finish getting these patches merged? I see a number of people in the
forum trying to use 'bdist-rpm' target to generate packages
There is no problem on the branch with the installation/operational patches.
Everything works from that perspective.
However, there is a bug relating to 'bdist_rpm' installs that is still
unresolved: https://bugs.launchpad.net/openobject-server/+bug/331024
And the gist of that bug is that
I think they are still problems on this bug and branches. So I don't think it's
merged. (or at least partially)
m2f
--
http://www.openobject.com/forum/viewtopic.php?p=33645#33645
m2f
greno wrote:
... So this patch should be available in bzr trunk very soon. ...
Is this now in place? There have been a lot of infrastructure changes in the
past few days but I don't see any attributed directly to greno.
Regards,
Geoff
Seath Solutions Ltd
All issues in the branch for the server have been resolved on Saturday. And
the client as well. So now the branch needs merged with the trunk and then
everybody should have access.
Regards,
Gerry
m2f
--
Status:
Stephane has created a branch for my installation patch and I've tested this
branch and everything tested ok. So now the next step is for Stephane to test
in their environment and then merge the branch into the trunk. So this patch
should be available in bzr trunk very soon.
Thank you greno, very nice work.
I target rh-based like centos and rhel, so this kind of thing is very important
to me. Thank you very much!
Just thinking now, no one has ever asked me to work on a deb-based box
(although I'm sure they are out there).
Regards, Paul
greno wrote:
I'm going to outline some patches that improve the installation and
operational experience for Linux users that I've submitted for inclusion in
OpenERP.
These look like such useful, important and (dare I say) uncontroversial patches
that I am surprised Tiny has not
we will integrate it before the next release.
m2f
--
http://www.openobject.com/forum/viewtopic.php?p=33086#33086
m2f
___
Tinyerp-users mailing list
fabien wrote:
we will integrate it before the next release.
That's great to hear!
greno wrote:
...I've been working with the Python Distutils SIG to get patches for a new
comand 'bdist_deb' adopted for Distutils
And let's hope Gerry gets this agreed in time, too. I hope that Fabien's
gegard wrote:
fabien wrote:
we will integrate it before the next release.
That's great to hear!
greno wrote:
...I've been working with the Python Distutils SIG to get patches for a new
comand 'bdist_deb' adopted for Distutils
And let's hope Gerry gets this agreed in time,
greno wrote:
... the patches that I submitted should be applied immediately and not be
held waiting for anything ...
Is there anything you know of that would prevent Tiny from putting them
straight into the trunk now?
(I know that they should not put them into any patch release of version
gegard wrote:
greno wrote:
... the patches that I submitted should be applied immediately and not be
held waiting for anything ...
Is there anything you know of that would prevent Tiny from putting them
straight into the trunk now?
No. I have the latest trunk and the patches work
Is the instance name, as applied to your init scripts compatible with
/sbin/chkconfig and /sbin/service ?
The following probably isn't going to work:
/sbin/chkconfig --level 345 openerp instance7 on
/sbin/service openerp instance7 start
--phil
Of course it will work.
service openerp-server start
service openerp-server start devel
Regards,
Gerry
m2f
--
http://www.openobject.com/forum/viewtopic.php?p=33136#33136
m2f
Good deal. I hadn't really looked far enough to see if that was a supported
nomenclature, just popped into my head as a possible sticking point.
Again, good work!
--phil
m2f
--
I'm going to outline some patches that improve the installation experience for
Linux users that I've submitted for inclusion in OpenERP.
A number of things inspired me to develop these patches not the least of
which was all the newbie, first-time, user pain that was seen in the
Here is what the typical RPM generation process looks like with the patches:
$ python setup.py bdist_rpm
/usr/lib/python2.5/distutils/dist.py#58;263#58; UserWarning#58; Unknown
distribution option#58; 'console'
nbsp; warnings.warn#40;msg#41;
running bdist_rpm
creating build
creating
And the RPM installaton using the patches looks like this:
# yum localinstall
/home/greno/build/python-dist/openerp-server-5.0.0-3_1759/dist/openerp-server-5.0.0-3_1759.noarch.rpm
Loading fastestmirror plugin
Loading installonlyn plugin
Setting up Local Package Process
Examining
And here is how you control the server instance with the patches:
# /etc/init.d/openerp-server start
Starting openerp-server#58;nbsp; nbsp; nbsp; nbsp; nbsp; nbsp; nbsp;
nbsp; nbsp; nbsp; nbsp; nbsp; nbsp; nbsp; nbsp; nbsp; nbsp;
nbsp;#91;nbsp; OKnbsp; #93;
# /etc/init.d/openerp-server status
whow, very nice work Gerry, I hope it will included very, very soon.
www.veritos.nl
m2f
--
http://www.openobject.com/forum/viewtopic.php?p=33068#33068
m2f
21 matches
Mail list logo
