On 2015-09-12 09:30, Dmitry Smirnov wrote:
> Yes I did. And I remember we've already discussed that. :)
Ah, OK, I was/am really mentally away from this stuff :~)
Btw.: Is there a current list of missing Odoo dependencies?
I assume, that some JS libraries are still missing, right?
On Saturday 12 September 2015 15:57:15 W. Martin Borgert wrote:
> Ah, OK, I was/am really mentally away from this stuff :~)
Likewise.
> Btw.: Is there a current list of missing Odoo dependencies?
> I assume, that some JS libraries are still missing, right?
With package like Odoo one almost
also sprach Dmitry Smirnov [2015-05-06 18:30 +0200]:
> I'm leaving packaging in almost finished state -- as per TODO
> there are only few non-DFSG issues left. Also Bootswatch themes
> are full of "privacy-breach" issues and have to be packaged
> separately anyway.
Where is
On Friday 11 September 2015 20:22:26 martin f krafft wrote:
> also sprach Dmitry Smirnov [2015-05-06 18:30 +0200]:
> > I'm leaving packaging in almost finished state -- as per TODO
> > there are only few non-DFSG issues left. Also Bootswatch themes
> > are full of
also sprach Dmitry Smirnov [2015-09-11 21:34 +0200]:
> > Has there been any progress made on the side of Odoo,
>
> No, they've never replied to me and I'm not happy with their bug
> handling either. :(
By "their bug handling" you mean that your 12 reported bugs
basically
On Friday 11 September 2015 22:13:44 martin f krafft wrote:
> By "their bug handling" you mean that your 12 reported bugs
> basically received no responses in months? Or is there something
> else going on?
>
> https://github.com/odoo/odoo/issues/created_by/onlyjob
Yeah, pretty much this plus at
On 2015-09-11 20:22, martin f krafft wrote:
> Has there been any progress made on the side of Odoo, or by
> Martin/Ben?
I only started, but got distracted by/busy with other things
and cannot work on Odoo packaging in the near future. I did
package, however, both python-oerplib and
On Saturday 12 September 2015 00:04:50 W. Martin Borgert wrote:
> Dmitry, you did some major rework of the repository in
> http://anonscm.debian.org/cgit/collab-maint/odoo.git, right?
> (I remember, that it was full-source, before.)
Yes I did. And I remember we've already discussed that. :)
--
On 11-Sep-2015, martin f krafft wrote:
> Has there been any progress made on the side of Odoo, or by
> Martin/Ben?
I'm no longer working with Odoo. I was motivated by working with Odoo
heavily at a previous job, but do not have that job now, so am
unlikely to work further on Odoo packaging.
--
Just to let everybody know that I am no longer working on Odoo packaging.
I'm disappointed in upstream, their bug handling and CLA; Odoo looks promising
but it is full of bugs and spaghetti code issues and its loose dependencies
(when activation of one module enables dependency modules that
(including the bug report this time, apologies for the repeat)
On 17-Apr-2015, Dmitry Smirnov wrote:
On Tue, 13 Jan 2015 10:27:27 Aaron Bohy wrote:
I am part of the Odoo team working on packaging and we are
currently working on an Odoo 8.0 package for the Debian archive.
Good to know that
On Fri, 17 Apr 2015 17:44:47 Ben Finney wrote:
Yes, Debian Policy §4.13 says Debian packages should not install these
“convenience copies” of third-party code. The third-party code should
instead be installed by a separate Debian package made from the source
for that code, and dependent
Hi Aaron,
On Tue, 13 Jan 2015 10:27:27 Aaron Bohy wrote:
I am part of the Odoo team working on packaging and we are currently
working on an Odoo 8.0 package for the Debian archive.
Good to know that you guys are interested to bring Odoo to Debian.
Here is our work so far:
Dear Martin,
I am part of the Odoo team working on packaging and we are currently
working
on an Odoo 8.0 package for the Debian archive.
Here is our work so far: https://mentors.debian.net/package/odoo
There are still some lintian errors or warnings.
Many of them are due to the fact that
Preliminary work is here:
http://anonscm.debian.org/gitweb/?p=collab-maint/odoo.git
Any help appreciated, e.g. with:
* remove non-sources from source tree
* package embedded JavaScript libraries separately
* implement use of dbconfig-common?
--
To UNSUBSCRIBE, email to
15 matches
Mail list logo