[opensuse-factory] New package submission to factory
Hi, I started pushing the first required packages for GNU Health to Factory, but they get immediately declined: Comment: 'Application:ERP:Tryton:3.8' is not a valid devel project of openSUSE:Factory - please pick one of the existent How can we fix this? Thanks Axel -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Wed, 2016-07-20 at 21:50 +0200, Axel Braun wrote:
Hi,
I started pushing the first required packages for GNU Health to Factory, but they get immediately declined: Comment: 'Application:ERP:Tryton:3.8' is not a valid devel project of openSUSE:Factory - please pick one of the existent
How can we fix this?
There are several ways: * Find a suitable devel project where this all can fit in (there are currently 170 devel projects known...) * if *REALLY* nothing fits or there is a good reason to yet use another devel project, it needs to be registered... I am not sure if 'Application:ERP:*' gives me the impression I would find anything relating to 'GNU Health' in there, but looking what Tryton is, ERP seems to match well.. What I don't like about your chosen project namespace is the fact that there is a version number in it... so you really intend to move this to a different devel project every so often? That's not very friendly to anybody, least to eventual users subscribing to the repository... as they can't just follow it and receive updates to new versions. In order to register a new devel project, you will have to create a pull request against: https://github.com/openSUSE/osc-plugin-factory/blob/master/osc-check_so urce.py#L250 Cheers, Dominique
Morning all,
Gesendet: Mittwoch, 20. Juli 2016 um 22:23 Uhr Von: "Dominique Leuenberger / DimStar"
An: opensuse-factory@opensuse.org Betreff: Re: [opensuse-factory] New package submission to factory On Wed, 2016-07-20 at 21:50 +0200, Axel Braun wrote:
I started pushing the first required packages for GNU Health to Factory, but they get immediately declined: Comment: 'Application:ERP:Tryton:3.8' is not a valid devel project of openSUSE:Factory - please pick one of the existent
How can we fix this?
There are several ways: * Find a suitable devel project where this all can fit in (there are currently 170 devel projects known...) * if *REALLY* nothing fits or there is a good reason to yet use another devel project, it needs to be registered...
I am not sure if 'Application:ERP:*' gives me the impression I would find anything relating to 'GNU Health' in there, but looking what Tryton is, ERP seems to match well..
Indeed: Tryton is an OpenSource ERP System - some years ago forked from OpenERP (nowadays called odoo). GNU Health extends the functionality to the medical sector, it is build on top of Tryton and adds specific modules to Tryton, while using a set of standard Tryon modules, server and Frontend as well.
What I don't like about your chosen project namespace is the fact that there is a version number in it... so you really intend to move this to a different devel project every so often? That's not very friendly to anybody, least to eventual users subscribing to the repository... as they can't just follow it and receive updates to new versions.
If you are using this ERP, you stay within one major release. Several major releases (currently 3.0/3.2/3.4/3.6/3.8/4.0) are maintianed in parallel, every 1-2 month a set of fixes is released. Thats why we have a version in the directory tree, to keep consistency. GNU Health is tied to a specific version of Tryton, in this case GNU Health 3.0 -> Tryton 3.8 A mix of modules between major versions is deadly - and the number one problem for people installing from source. So the plan is to release current GNU Health to Factory - and Leap 42.2 if not alread too late. When next GNU Health is released in January 2017 (version 3.2 based on Tryton 4.2) it will be build and tested in ERP:Tryton:4.2, and submitted from there to Factory Submission to an existing devel project seems not to be a feasible option. Different technologies are used (Python/Nodejs) and I dont see that I can keep the consistency within a major release.
In order to register a new devel project, you will have to create a pull request against: https://github.com/openSUSE/osc-plugin-factory/blob/master/osc-check_so urce.py#L250
Will go for this! Thanks Axel -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 07/21/2016 04:09 PM, Axel Braun wrote:
Morning all,
Gesendet: Mittwoch, 20. Juli 2016 um 22:23 Uhr Von: "Dominique Leuenberger / DimStar"
An: opensuse-factory@opensuse.org Betreff: Re: [opensuse-factory] New package submission to factory On Wed, 2016-07-20 at 21:50 +0200, Axel Braun wrote:
I started pushing the first required packages for GNU Health to Factory, but they get immediately declined: Comment: 'Application:ERP:Tryton:3.8' is not a valid devel project of openSUSE:Factory - please pick one of the existent
How can we fix this?
There are several ways: * Find a suitable devel project where this all can fit in (there are currently 170 devel projects known...) * if *REALLY* nothing fits or there is a good reason to yet use another devel project, it needs to be registered...
I am not sure if 'Application:ERP:*' gives me the impression I would find anything relating to 'GNU Health' in there, but looking what Tryton is, ERP seems to match well..
Indeed: Tryton is an OpenSource ERP System - some years ago forked from OpenERP (nowadays called odoo). GNU Health extends the functionality to the medical sector, it is build on top of Tryton and adds specific modules to Tryton, while using a set of standard Tryon modules, server and Frontend as well.
What I don't like about your chosen project namespace is the fact that there is a version number in it... so you really intend to move this to a different devel project every so often? That's not very friendly to anybody, least to eventual users subscribing to the repository... as they can't just follow it and receive updates to new versions.
If you are using this ERP, you stay within one major release. Several major releases (currently 3.0/3.2/3.4/3.6/3.8/4.0) are maintianed in parallel, every 1-2 month a set of fixes is released. Thats why we have a version in the directory tree, to keep consistency.
GNU Health is tied to a specific version of Tryton, in this case GNU Health 3.0 -> Tryton 3.8 A mix of modules between major versions is deadly - and the number one problem for people installing from source.
So the plan is to release current GNU Health to Factory - and Leap 42.2 if not alread too late. When next GNU Health is released in January 2017 (version 3.2 based on Tryton 4.2) it will be build and tested in ERP:Tryton:4.2, and submitted from there to Factory
Generally people would do something along the lines of creating something like ERP:Tryton:Factory which contains the current version that has been pushed to openSUSE:Factory then before you update to 4.4 you copy all the packages from ERP:Tryton:Factory into ERP:Tryton:4.2, the alternative is creating ERP:Tryton:4.0/4.2/4.4 and then copy the version you want in openSUSE first into ERP:Tryton:Factory from wherever you create it, i'm lead to believe changing devel repo's all the time is complex and likely to break things
Will go for this! Thanks Axel
Cheers -- Simon Lees (Simotek) http://simotek.net Emergency Update Team keybase.io/simotek SUSE Linux Adeliade Australia, UTC+9:30 GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B
On Thu, 2016-07-21 at 08:39 +0200, Axel Braun wrote:
What I don't like about your chosen project namespace is the fact that there is a version number in it... so you really intend to move this to a different devel project every so often? That's not very friendly to anybody, least to eventual users subscribing to the repository... as they can't just follow it and receive updates to new versions.
If you are using this ERP, you stay within one major release. Several major releases (currently 3.0/3.2/3.4/3.6/3.8/4.0) are maintianed in parallel, every 1-2 month a set of fixes is released. Thats why we have a version in the directory tree, to keep consistency.
GNU Health is tied to a specific version of Tryton, in this case GNU Health 3.0 -> Tryton 3.8 A mix of modules between major versions is deadly - and the number one problem for people installing from source.
So the plan is to release current GNU Health to Factory - and Leap 42.2 if not alread too late. When next GNU Health is released in January 2017 (version 3.2 based on Tryton 4.2) it will be build and tested in ERP:Tryton:4.2, and submitted from there to Factory
Which will get you back to square one then: ERP:Tryton:4.2 will not be a registered devel project... You might want to make your prj setup a bit different: ERP:Tryton => the PACKAGES you want to submit - this would be the devel prj ERP:Tryton:3.8 => what you work on for now and 'offer' to users. Funnel all submissions through ERP:Tryton to Factory and 42.2 ERP:Tryton:4.2 => you can start working in parallel, users can start testing. At the point this is ready, you submit stuff to ERP:Tryton and from there again to openSUSE:Factory Like this, you don't have to run after new devel project registration every so often. What do you think? Cheers, Dominique
Gesendet: Donnerstag, 21. Juli 2016 um 11:15 Uhr Von: "Dominique Leuenberger / DimStar"
An: opensuse-factory@opensuse.org Betreff: Re: Aw: Re: [opensuse-factory] New package submission to factory On Thu, 2016-07-21 at 08:39 +0200, Axel Braun wrote:
What I don't like about your chosen project namespace is the fact that there is a version number in it... so you really intend to move this to a different devel project every so often? That's not very friendly to anybody, least to eventual users subscribing to the repository... as they can't just follow it and receive updates to new versions.
If you are using this ERP, you stay within one major release. Several major releases (currently 3.0/3.2/3.4/3.6/3.8/4.0) are maintianed in parallel, every 1-2 month a set of fixes is released. Thats why we have a version in the directory tree, to keep consistency.
GNU Health is tied to a specific version of Tryton, in this case GNU Health 3.0 -> Tryton 3.8 A mix of modules between major versions is deadly - and the number one problem for people installing from source.
So the plan is to release current GNU Health to Factory - and Leap 42.2 if not alread too late. When next GNU Health is released in January 2017 (version 3.2 based on Tryton 4.2) it will be build and tested in ERP:Tryton:4.2, and submitted from there to Factory
Which will get you back to square one then: ERP:Tryton:4.2 will not be a registered devel project...
You might want to make your prj setup a bit different:
ERP:Tryton => the PACKAGES you want to submit - this would be the devel prj
ERP:Tryton:3.8 => what you work on for now and 'offer' to users. Funnel all submissions through ERP:Tryton to Factory and 42.2
ERP:Tryton:4.2 => you can start working in parallel, users can start testing. At the point this is ready, you submit stuff to ERP:Tryton and from there again to openSUSE:Factory
Like this, you don't have to run after new devel project registration every so often.
What do you think?
Sounds like a plan. I like the idea from Simon to create ERP:Tryton:Factory, to make it even more visible what will go to openSUSE:FActory. Can the packages in ERP:Tryton:Factory be linked to ERP:Tryton:3.8, or should they be copied? Cheers Axel -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (3)
-
Axel Braun
-
Dominique Leuenberger / DimStar
-
Simon Lees