Merge lp:~unity-team/qtmir/inline-gles-quilt into lp:qtmir
| Status: | Rejected |
|---|---|
| Rejected by: | Michał Sawicz on 2016-04-06 |
| Proposed branch: | lp:~unity-team/qtmir/inline-gles-quilt |
| Merge into: | lp:qtmir |
| Diff against target: |
262 lines (+234/-0) 5 files modified
debian/bileto_convert_to_gles (+13/-0) debian/gles-patches/convert-to-gles.patch (+203/-0) debian/gles-patches/series (+1/-0) tests/CMakeLists.txt (+6/-0) tests/convert-to-gles.sh (+11/-0) |
| To merge this branch: | bzr merge lp:~unity-team/qtmir/inline-gles-quilt |
| Related bugs: |
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| Robert Bruce Park (community) | 2016-03-24 | Disapprove on 2016-03-31 | |
| Unity8 CI Bot | continuous-integration | 2016-03-24 | Needs Fixing on 2016-03-30 |
| Gerry Boland | tentative | 2016-03-24 | Pending |
|
Review via email:
|
|||
This proposal supersedes a proposal from 2016-03-11.
Commit Message
Inline GLES packaging
Description of the Change
Experimenting with having GLES debian/ dir inlined in same trunk, and experimenting with train building gles package for you.
control.gles and rules.gles are copied verbatim from lp:qtmir/gles
=====
I've now employed quilt to do this, and added a test that runs in the non-gles tree.
| Unity8 CI Bot (unity8-ci-bot) wrote : | # |
FAILED: Continuous integration, rev:454
No commit message was specified in the merge proposal. Click on the following link and set the commit message (if you want a jenkins rebuild you need to trigger it yourself):
https:/
https:/
Executed test runs:
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
Click here to trigger a rebuild:
https:/
| Unity8 CI Bot (unity8-ci-bot) wrote : | # |
PASSED: Continuous integration, rev:455
https:/
Executed test runs:
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
Click here to trigger a rebuild:
https:/
| Unity8 CI Bot (unity8-ci-bot) wrote : | # |
PASSED: Continuous integration, rev:456
https:/
Executed test runs:
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
Click here to trigger a rebuild:
https:/
| Unity8 CI Bot (unity8-ci-bot) wrote : | # |
PASSED: Continuous integration, rev:457
https:/
Executed test runs:
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
Click here to trigger a rebuild:
https:/
| Unity8 CI Bot (unity8-ci-bot) wrote : | # |
PASSED: Continuous integration, rev:459
https:/
Executed test runs:
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
Click here to trigger a rebuild:
https:/
| Unity8 CI Bot (unity8-ci-bot) wrote : | # |
PASSED: Continuous integration, rev:460
https:/
Executed test runs:
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
Click here to trigger a rebuild:
https:/
| Gerry Boland (gerboland) wrote : | # |
+sed --in-place 's/qtmir/
this will edit more than just the package names in the changelog. Example:
- * Depend on same-version qtmir-{
+ * Depend on same-version qtmir-gles-
- * Migration of qtmir from the legacy Mir API
+ * Migration of qtmir-gles from the legacy Mir API
Could you make the sed replace a bit more strict, to prevent this?
I'm also a giant fan of explaining non-obvious things with a comment or readme - please add a readme to explain the purpose of the *.gles and bileto scripts.
Also, is editing "debian/copyright" necessary? Upstream name always being "qtmir" strikes me as more correct.
Looks fine to me otherwise.
| Robert Bruce Park (robru) wrote : | # |
On Mon, Mar 21, 2016 at 7:55 AM, Gerry Boland
<email address hidden> wrote:
> Could you make the sed replace a bit more strict, to prevent this?
Can do.
> I'm also a giant fan of explaining non-obvious things with a comment or readme - please add a readme to explain the purpose of the *.gles and bileto scripts.
On it.
> Also, is editing "debian/copyright" necessary? Upstream name always being "qtmir" strikes me as more correct.
Well I wrote the script to minimize the diff against the existing
qtmir-gles package, eg, the existing qtmir-gles already defines
"Upstream-Name: qtmir-gles" in its debian/copyright.
Now that you mention it, since the field is called "Upstream" Name, it
does seem more correct to leave it as just qtmir, but that will
introduce a packaging diff when this code goes live.
--
robru
| Robert Bruce Park (robru) wrote : | # |
Ok fixed sed, let me know if the comment is clear enough.
This is safe to merge as-is however the train implementation of this isn't in production yet so you have to keep maintaining lp:qtmir/gles for the time being.
| Unity8 CI Bot (unity8-ci-bot) wrote : | # |
FAILED: Continuous integration, rev:461
https:/
Executed test runs:
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
FAILURE: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
Click here to trigger a rebuild:
https:/
| Unity8 CI Bot (unity8-ci-bot) wrote : | # |
FAILED: Continuous integration, rev:461
https:/
Executed test runs:
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
deb: https:/
FAILURE: https:/
SUCCESS: https:/
deb: https:/
FAILURE: https:/
SUCCESS: https:/
deb: https:/
FAILURE: https:/
Click here to trigger a rebuild:
https:/
| Gerry Boland (gerboland) wrote : | # |
Tentative approval. Approach is good.
Already the build dependencies here are out of date, so this will need refreshing at land-time.
Would be cool to auto-generate the control.gles file from the control file, as build-dep changes are something easily forgotten in the gles file. But this will as first step.
| Robert Bruce Park (robru) wrote : | # |
Yeah it's difficult for me to identify which differences are because lp:qtmir/gles is languishing and which are the necessary changes for gles to actually work.
I like saviq's idea to use a patch instead of duplicating the files but i don't have enough knowledge of gles to produce the correct patch. This branch currently is just "merge lp:qtmir/gles into here" and doesn't make any attempt at reducing the delta.
| Robert Bruce Park (robru) wrote : | # |
Drop vcs-bzr/
Also the sed is wrong, needs a space after qtmir-gles (my fault though)
Why do you drop --fail-missing? High chance of building empty packages there.
| Unity8 CI Bot (unity8-ci-bot) wrote : | # |
FAILED: Continuous integration, rev:462
https:/
Executed test runs:
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
FAILURE: https:/
FAILURE: https:/
FAILURE: https:/
FAILURE: https:/
FAILURE: https:/
FAILURE: https:/
Click here to trigger a rebuild:
https:/
- 463. By Michał Sawicz on 2016-03-30
-
Fix sed line and drop gles-specific Vcs headers
| Michał Sawicz (saviq) wrote : | # |
> Why do you drop --fail-missing? High chance of building empty packages there.
Because we're still installing the whole thing and only packaging a small part of it. With --fail-missing dpkg will complain that we're not packaging all the installed files.
| Michał Sawicz (saviq) wrote : | # |
Oh and fixed the other bits, thanks!
| Robert Bruce Park (robru) wrote : | # |
Wouldn't it then be more correct to delete the unnecessary files and keep --fail-missing?
Dropping --fail-missing terrifies me, I've seen to many packages be built empty and nobody noticed until it's too late.
| Unity8 CI Bot (unity8-ci-bot) wrote : | # |
FAILED: Continuous integration, rev:463
https:/
Executed test runs:
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
FAILURE: https:/
FAILURE: https:/
FAILURE: https:/
FAILURE: https:/
FAILURE: https:/
FAILURE: https:/
Click here to trigger a rebuild:
https:/
| Robert Bruce Park (robru) wrote : | # |
Hmmm, tried running this in the staging train, not sure what happened to quilt here:
https:/
+ su citrain-
+ QUILT_PATCHES=
+ quilt push -a
No series file found
I guess you need to export QUILT_PATCHES.
| Robert Bruce Park (robru) wrote : | # |
Also it's not entirely clear to me that your test makes sense, because if "quilt push -a" fails, that means bileto_
Unless you're intending that test to be run locally by devs before it goes into a silo.
| Robert Bruce Park (robru) wrote : | # |
Ok, I've started iterating on this in the ci train staging instance which has the new GLES magic live, see here:
https:/

FAILED: Continuous integration, rev:453 /code.launchpad .net/~robru/ qtmir/inline- gles/+merge/ 288732/ +edit-commit- message
No commit message was specified in the merge proposal. Click on the following link and set the commit message (if you want a jenkins rebuild you need to trigger it yourself):
https:/
https:/ /unity8- jenkins. ubuntu. com/job/ lp-qtmir- ci/104/ /unity8- jenkins. ubuntu. com/job/ build-0- fetch/879 /unity8- jenkins. ubuntu. com/job/ build-1- sourcepkg/ release= vivid+overlay/ 895 /unity8- jenkins. ubuntu. com/job/ build-1- sourcepkg/ release= xenial/ 895 /unity8- jenkins. ubuntu. com/job/ build-2- binpkg/ arch=amd64, release= vivid+overlay/ 893 /unity8- jenkins. ubuntu. com/job/ build-2- binpkg/ arch=amd64, release= vivid+overlay/ 893/artifact/ output/ *zip*/output. zip /unity8- jenkins. ubuntu. com/job/ build-2- binpkg/ arch=amd64, release= xenial/ 893 /unity8- jenkins. ubuntu. com/job/ build-2- binpkg/ arch=amd64, release= xenial/ 893/artifact/ output/ *zip*/output. zip /unity8- jenkins. ubuntu. com/job/ build-2- binpkg/ arch=armhf, release= vivid+overlay/ 893 /unity8- jenkins. ubuntu. com/job/ build-2- binpkg/ arch=armhf, release= vivid+overlay/ 893/artifact/ output/ *zip*/output. zip /unity8- jenkins. ubuntu. com/job/ build-2- binpkg/ arch=armhf, release= xenial/ 893 /unity8- jenkins. ubuntu. com/job/ build-2- binpkg/ arch=armhf, release= xenial/ 893/artifact/ output/ *zip*/output. zip /unity8- jenkins. ubuntu. com/job/ build-2- binpkg/ arch=i386, release= vivid+overlay/ 893 /unity8- jenkins. ubuntu. com/job/ build-2- binpkg/ arch=i386, release= vivid+overlay/ 893/artifact/ output/ *zip*/output. zip /unity8- jenkins. ubuntu. com/job/ build-2- binpkg/ arch=i386, release= xenial/ 893 /unity8- jenkins. ubuntu. com/job/ build-2- binpkg/ arch=i386, release= xenial/ 893/artifact/ output/ *zip*/output. zip
Executed test runs:
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
Click here to trigger a rebuild: /unity8- jenkins. ubuntu. com/job/ lp-qtmir- ci/104/ rebuild
https:/