https://launchpad.net/~kunda1
Volunteer Packagers Needed for the PPA
Re: Volunteer Packagers Needed for the PPA
Alone you go faster. Together we go farther
Please mark thread [Solved]
Want to contribute back to FC? Checkout:
'good first issues' | Open TODOs and FIXMEs | How to Help FreeCAD | How to report Bugs
Please mark thread [Solved]
Want to contribute back to FC? Checkout:
'good first issues' | Open TODOs and FIXMEs | How to Help FreeCAD | How to report Bugs
Re: Volunteer Packagers Needed for the PPA
@yorik am I really wrong that build is done from Salsa Debian Freecad daily? So It's mainly fix build from there as I didn't notice that there is no building stuff in automatically imported git on launchpad
Re: Volunteer Packagers Needed for the PPA
Done!
This is the code used for the ppa AFAICS: https://code.launchpad.net/~freecad-mai ... it/freecad it seems in sync with the FreeCAD master code...
Re: Volunteer Packagers Needed for the PPA
@yorik may I ask you if it is in relation with this thread and fix the annoyance?
Re: Volunteer Packagers Needed for the PPA
Is this PPA available just to build upstream git as there is this Freecad PPA based on https://git.launchpad.net/freecad (It only builds releases). As that is used for debian directory. Just asking as there should not be double effort on this and determine relationship..yorik wrote: ↑Mon Jul 18, 2022 12:19 pmThis is the code used for the ppa AFAICS: https://code.launchpad.net/~freecad-mai ... it/freecad it seems in sync with the FreeCAD master code...
Re: Volunteer Packagers Needed for the PPA
I don't really know if there is any relationship at all between the launchpad git and the debian salsa git. I believe not, each of them syncs with our FreeCAD master code independently. Only, debian makes builds at specific times, while normally the PPA should build daily, or so.
- adrianinsaval
- Veteran
- Posts: 5553
- Joined: Thu Apr 05, 2018 5:15 pm
Re: Volunteer Packagers Needed for the PPA
This looks like it would be the relevant files for packaging: https://git.launchpad.net/freecad/tree/?h=ppa/daily
- wandererfan
- Veteran
- Posts: 6326
- Joined: Tue Nov 06, 2012 5:42 pm
- Contact:
Re: Volunteer Packagers Needed for the PPA
This is the LP repo with the debian rules and control files:
https://git.launchpad.net/freecad is an import of the Git repository at https://salsa.debian.org/science-team/freecad.
This is the LP repo with the current FC source:
https://git.launchpad.net/~freecad-main ... it/freecad is an import of the Git repository at https://github.com/FreeCAD/FreeCAD.git.
The debian dir from the first gets inserted into the second for the daily build.
- adrianinsaval
- Veteran
- Posts: 5553
- Joined: Thu Apr 05, 2018 5:15 pm
Re: Volunteer Packagers Needed for the PPA
and where is this kind of stuff setup? Is there a script that gets executed on a schedule in launchpad? the whole process is very obscure to outsiders.wandererfan wrote: ↑Tue Jul 26, 2022 1:20 pm The debian dir from the first gets inserted into the second for the daily build.
Speaking of which, I have an idea to make the daily ppa have correct full version information, in the FreeCAD-Bundle repo a source tarball with correct full version info is created every 4 hours (the conda builds use these), this is done here with a script that writes the version info and then makes a commit with it before doing
Code: Select all
git archive HEAD -o ../freecad_source.tar.gz
- wandererfan
- Veteran
- Posts: 6326
- Joined: Tue Nov 06, 2012 5:42 pm
- Contact:
Re: Volunteer Packagers Needed for the PPA
I don't know how the scheduling part works.adrianinsaval wrote: ↑Tue Jul 26, 2022 1:48 pm and where is this kind of stuff setup? Is there a script that gets executed on a schedule in launchpad? the whole process is very obscure to outsiders.
The source gets built by running git-build-recipe against a Launchpad "recipe". This builds a source tree that combines the debian stuff with the FC source, then makes a source tar ball and dsc file. After that it runs debuild against the tar ball to produce the package files.
The source tree produces a good FC executable using the usual CMake + make process. The problem is somewhere in the rules and control files that control debuild, but that's as far as I got.
My notes to myself are attached.
- Attachments
-
- packagingNotes.txt
- (1.89 KiB) Downloaded 82 times