Contributors mailing list archives

Browse archives


Re: OCA Repositories in Odoo Apps Store

Camptocamp SA, Yannick Payot
- 11/06/2020 14:40:50
Seems we will have some manual job to do to restore some repository.

The warnings are either:

1. <module>: The license LGPL-3 conflicts with one of its dependencies. Please make sure that you comply with the licenses compatibility. See our FAQ at .
2. Module <module> already exists for another serie. Please select a free module name or use the right account and this repository: <not an OCA repository>
3. <module>: unmet dependency <another_module> for series 13.0. Dependency might be invalid.
(4. No module found in repository ssh://<repo>.git#13.0.
Each module needs to be in a separate folder at the root of the repository, even if there is only one module.
If you have all the files of your module at the root of your repository, you need to create a new folder with the name of your module and move all the files in it.) -> This one is just normal
(5. <module>: Module not installable) -> The module is most likely "installable": False

In #2 I recognize some OCA contributors that might have forked a module and registered it by mistake. But it requires us to reclaim them. We already did it in the past and Odoo helped us on that.

We definitely need to dispatch the work there, the board shouldn't be the ones that handle it. It can be delegated to PSC IMO. In most cases (licences and dependencies) they can check it.

Simone, do you know if we can extract the list of errors easily?


On Tue, 9 Jun 2020 at 07:31, Simone Orsi <> wrote:

I'll do a round of checks but we have soooo many repos and modules that is very hard to get the full picture of their status at glance.

@Fekete: do you have a list of modules/repo/branch you specifically detected?

AFAIK this can be due to a bunch of reasons: branch not registered, scan of repo failed.

The 1st reason depends on the fact that the process is still manual and Odoo does not ease this process at all.
There's a WIP proof of concept here to try to automate the process.
If anyone wants to help Alexey with it, I'm sure it will be appreciated ;)

The 2nd may depend on errors when parsing some files (eg: rst docs).

Meanwhile, if you notice a module or a repo is missing, please let us know.


On Mon, Jun 8, 2020 at 11:21 PM Daniel Reis <> wrote:

I got hold of the OCA app credentials, and there are a lot of warning to deal with.
I'll go through them.

You're welcome to ask me about any particular repo, if you want.


On 08/06/2020 20:56, Frederik Kramer wrote:
Or probably strategy enforcement ;-) Who knows. But i am with Holger to
double check and to make sure that OCA is not doeing anything wrong

Best Frederik

Am Montag, den 08.06.2020, 19:52 +0000 schrieb Holger Brunn:

> > Except mistake or bugs, the company seems filter the apps she wants

> to show.


> so let's assume one of the first two and reach out to see what's

> going on. A 

> mistake/glitch/whatever on the submitting (so our) side also isn't

> impossible, 

> so let's ask the people busy with that to double check.


> In the past I made the mistake to mark some of my cooler modules as 

> dependencies, which they were because they don't do anything on their

> own, but 

> that got them hidden in the app store. Maybe we also have different

> visibility 

> rules at play between odoo sa and oca?


> ---




> _______________________________________________

> Mailing-List:

> Post to:

> Unsubscribe:

Dr.-Ing. Frederik Kramer
initOS GmbH
An der Eisenbahn 1
21224 Rosengarten
Phone:  +49 4105 56156-12
Fax:    +49 4105 56156-10
Mobil:  +49 179 3901819
Dr.-Ing. Frederik Kramer & Dipl.-Ing. (FH) Torsten Francke

Sitz der Gesellschaft: Rosengarten – Klecken
Amtsgericht Tostedt, HRB 205226
Steuer-Nr: 15/200/53247
USt-IdNr.: DE815580155

Post to:

Post to:

Post to: