[6.0 trunk] setup stops with missing file(s)

here is the second error..

/usr/lib/python2.6/distutils/dist.py:266: UserWarning: Unknown
distribution option: 'console'
  warnings.warn(msg)

On 10. 02. 11 14:17, Vinay Rana (openerp) wrote:
> ** Changed in: openobject-server
> Importance: Undecided => Medium
>
> ** Changed in: openobject-server
> Status: New => Confirmed
>
> ** Changed in: openobject-server
> Assignee: (unassigned) => OpenERP's Framework R&D (openerp-dev-framework)
>
I don't want to be too intrusive, but this kind of merges should never
happen! The error is too big, and 100% blocking! I provided a patch, not
sure it complains with the "plan", but at lest it repairs the "damage".
Playing with whole folders can be dangerous :-)

Yes I dont get it, I appreciate all of the free software and others hard work but Ubuntu is a widely used platform for OpenERP. And how someone can continually commit changes that breaks entire installations makes me wonder. Over the past moth theres been at least 3 times when code was committed that made previous installations unusable.

A solution is being prepared at https://code.launchpad.net/~openerp-dev/openobject-server/trunk-bug-715667-vmt

The new setup.py should work on *nix platforms and work will be done so that the py2exe option works also. Apologies for the inconvenience, we understand the situation is not very comfortable for the easy_install/pip users.

On 24. 02. 11 15:35, Vo Minh Thu (OpenERP) wrote:
> A solution is being prepared at https://code.launchpad.net/~openerp-dev
> /openobject-server/trunk-bug-715667-vmt
>
> The new setup.py should work on *nix platforms and work will be done so
> that the py2exe option works also. Apologies for the inconvenience, we
> understand the situation is not very comfortable for the
> easy_install/pip users.
>
> ** Changed in: openobject-server
> Status: Confirmed => In Progress
>
lol

this is not an "inconvenience" this was a BIG error...

and fixing it after two weeks, another one ;) well, not sure it was
fixed yet. wait and see...

Bogdan,

From my point of view, there are a lot of things that are to be done, even only considering the 'openerp' as a module and clean packaging goal. The fact we can't do all of them shouldn't prevent us from moving forward, one step at a time.

We have to constantly make a balance between keeping things as-is, so that people don't have to change anything to their setup, and moving things so they are better in the future. We try hard to not brake things but sometimes it has to happen. As I said, we apology for the inconvenience we put on you.

By the way, there is no promise it works on the linked branch, the branch is not yet ready to be merged. But if you feel you can make any suggestion, it is there ready for you to try.

Cheers

Le 24/02/11 16:10, Bogdan Stanciu a écrit :
> lol
>
> this is not an "inconvenience" this was a BIG error...
>
> and fixing it after two weeks, another one ;) well, not sure it was
> fixed yet. wait and see...

Please keep in mind that we are talking about the trunk branch. Trunk,
as in 'development' version, not as in 'stable' version.

We try our best to keep trunk usable on day-to-day, and we have the
continuous integration server running all testsuites on all commits on
test.openobject.com, like for stable branches, but these kinds of
breakages are bound to happen from time to time on trunk. As Thu was
explaining, sometimes it's necessary to do a clean cut, and face the
consequences.

We really appreciate that you take the time to report the issues that
our testsuites don't catch, so we can improve them. As you guessed, the
server's setup.py is not part of the routine tests we were currently
running, as it is mostly provided as a convenience tool for python
developers, and not currently the recommended way of installing OpenERP
Server. We definitely plan to improve this in our testsuites, though.

For your information, we are also creating feature branches and merge
proposals for reviewing all internal developments, so if you are
interested in helping review daily developments, feel free to subscribe
to the merge proposals notification on ~openerp branches, and add your
valuable feedback at an earlier stage :-)

Thanks!

"and not currently the recommended way of installing OpenERP
Server."

What is the recommended way of installing the server?

It wasnt that bad, but the best way to use it is by branching the folder and then using python openerp-server.py to start the server. This does not require installation which is probably why they did not notice the error. By doing it this way, you can pull updates and it automatically updates your server. For the modules you use symbolic links. Thanks for patching the bug.

While I agree that we do not expect trunk version to be as stable as released versions, but I think a good practice in software engineering is to ensure that the trunk should be free of regression issues as much as possible. I suggest that we have this following in place:

1. A clear/visible tags in trunk for non-regression issues (of the modules responsible by OpenERP SA, of course): this is intended for people to use the latest in trunk without too much troubles (they focus on their local development/new features rather than working on the problems resulting from the publisher/editor). This should be visible in the launchpad so people knows which one to update to.

2. Any regression issues reported by the test server should be treated with high priority: who breaks it, fix it. This can be and should be enforce among OpenERP SA development teams.

3. A more thorough automatic tests that cover everything from clean setup/start of the server. The reasons I ask for this was that many times, I found problems after restarting the servers, and not during the upgrading modules, which is very annoying.

I thought this was a minor missing files error, but upon checking further the current branch is not usable. It has several folders missing like the postgres connection folders so even without doing install the branch cant be used. Stuck on revision 3350. Thanks for your attention.

Hi Kyle,

Could you provide more detailed info on how to update from the trunk?
You wrote "the best way to use it is by branching the folder " but if I try to do that I receive an error [ bzr: ERROR: Not a branch: "/usr/share/pyshared/openerp-server/" ]
Does this ring a bell? Am I trying to sync the wrong dir?
Using the command bzr pull. Or is this the wrong command?
Thanks for some more info on this.
Hope that after succeeding I have more success with webdav. Can't get that to work...

I will help you, but in the future please keep bug reports relevant to bug reports. Every time we type a message, it is sent to everyone in the mailing list so they do not want to hear about questions.

The answer is, the path you specified above is probably your installation directory. When you get the sources from launchpad you branch them at the same time they are downloaded like this

bzr branch lp:openobject-server server
This creates the branched folder. When we use bzr pull we are asking for updated changes. By doing this, we do not have to install the software, and can get updates easily. If we have a problem with a version like the current trunk we do

bzr revert --revision 3350
which in my opinion is the only revision working right now. The newest one reported in the bug here, has many missing files and is unusable currently.

When you run the application you do not do python setup.py install. you go to the bin directory and do python openerp-server.py

if you have your own configuration file then you add --conf=/path/toconfig. This should tell you everything you need to know to get it working.

Thanks Kyle! I'll refrain from raising questions in future following your suggestion...(Had the intention to mail you off line but no email address available here(?)...

just tested this morning sudo python setup.py install - seems this problem still exists. when will it be fixed?

Yes you are correct it is non functioning. Even if you used python directly instead of installing the trunk is still broken because the Postgres connection folders and files are missing. I would recommend that you use this branch instead. lp:openobject-server/6.0

A revamped setup.py file was commited in trunk revision 3375 and should correct any problem introduced by the bin to openerp renaming. Although it was on our TODO-list, thanks a lot for reporting and commenting on this bug.