Please update Ninja from Debian
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| | ninja-build (Ubuntu) |
Undecided
|
Unassigned | ||
Bug Description
Ubuntu has version 1.3.4 of Ninja. This is very old. Debian has version 1.5.1 even in testing. It has not migrated to Ubuntu proper for some reason, probably because uploads newer than 1.3.4 are NMUs.
Please update Ninja to the version in Debian. This is preventing new versions of Meson from getting into the archive as it has a requirement of >= 1.5 for Ninja.
Thanks,
Related branches
- Ubuntu branches: Pending requested 2015-07-12
-
Diff: 7508 lines (+2552/-2357)78 files modified.clang-format (+25/-0)
.gitignore (+10/-1)
.pc/00bootstrap.patch/bootstrap.py (+0/-163)
.pc/01configure.patch/configure.py (+0/-447)
.pc/applied-patches (+0/-3)
.pc/asciidoc.patch/doc/manual.asciidoc (+0/-917)
RELEASING (+23/-7)
bootstrap.py (+9/-12)
configure.py (+23/-15)
debian/changelog (+29/-0)
debian/control (+3/-3)
debian/copyright (+12/-14)
debian/patches/00bootstrap.patch (+0/-20)
debian/patches/01configure.patch (+0/-26)
debian/patches/asciidoc.patch (+0/-102)
debian/patches/series (+0/-3)
doc/manual.asciidoc (+55/-28)
misc/bash-completion (+37/-19)
misc/ninja-mode.el (+14/-4)
misc/ninja.vim (+5/-3)
misc/ninja_syntax.py (+21/-23)
misc/write_fake_manifests.py (+219/-0)
misc/zsh-completion (+45/-4)
platform_helper.py (+17/-5)
src/build.cc (+53/-36)
src/build.h (+8/-4)
src/build_log.cc (+42/-23)
src/build_log.h (+11/-4)
src/build_log_perftest.cc (+6/-1)
src/build_log_test.cc (+47/-6)
src/build_test.cc (+326/-28)
src/clean.cc (+2/-2)
src/clean_test.cc (+30/-6)
src/debug_flags.cc (+19/-0)
src/debug_flags.h (+31/-0)
src/depfile_parser.cc (+53/-38)
src/depfile_parser.in.cc (+3/-3)
src/depfile_parser_perftest.cc (+77/-0)
src/depfile_parser_test.cc (+17/-2)
src/deps_log.cc (+105/-25)
src/deps_log.h (+14/-3)
src/deps_log_test.cc (+89/-1)
src/disk_interface.cc (+110/-25)
src/disk_interface.h (+23/-3)
src/disk_interface_test.cc (+64/-5)
src/edit_distance.cc (+1/-0)
src/explain.cc (+0/-15)
src/explain.h (+0/-27)
src/graph.cc (+70/-60)
src/graph.h (+22/-11)
src/graph_test.cc (+29/-4)
src/hash_map.h (+5/-2)
src/includes_normalize_test.cc (+1/-1)
src/line_printer.cc (+47/-4)
src/line_printer.h (+20/-0)
src/manifest_parser.cc (+23/-19)
src/manifest_parser.h (+1/-1)
src/manifest_parser_perftest.cc (+118/-0)
src/manifest_parser_test.cc (+143/-0)
src/metrics.cc (+2/-0)
src/msvc_helper-win32.cc (+10/-9)
src/msvc_helper.h (+3/-2)
src/msvc_helper_main-win32.cc (+13/-3)
src/msvc_helper_test.cc (+26/-10)
src/ninja.cc (+111/-10)
src/parser_perftest.cc (+0/-77)
src/state.cc (+4/-2)
src/state.h (+2/-1)
src/subprocess-posix.cc (+34/-25)
src/subprocess-win32.cc (+21/-9)
src/subprocess.h (+3/-2)
src/subprocess_test.cc (+17/-2)
src/test.cc (+2/-2)
src/test.h (+1/-1)
src/util.cc (+107/-23)
src/util.h (+7/-0)
src/util_test.cc (+31/-0)
src/version.cc (+1/-1)
| Hans Joachim Desserud (hjd) wrote : | #1 |
| tags: | added: upgrade-software-versionp |
| tags: |
added: upgrade-software-version removed: upgrade-software-versionp |
| Hans Joachim Desserud (hjd) wrote : | #2 |
I've now created a branch where I've merged in the latest changes from Debian with the Ubuntu ones.
Attached is the output of `bzr diff -r tag:1.5.1-0.1` from my suggested branch, since I noticed I couldn't attach files in the merge proposal. I have to admit I don't understand why several files are marked as renamed when the names haven't actually changed. Please let med know if this is unexpected and due to my merge somehow.
The attachment "ubuntu-delta.diff" seems to be a debdiff. The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff. If the attachment isn't a patch, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team.
[This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issue please contact him.]
| tags: | added: patch |
| Chris Coulson (chrisccoulson) wrote : | #4 |
Could somebody please do a test build of Oxide before this gets uploaded?
| Sebastien Bacher (seb128) wrote : | #5 |
(unsubscribing the sponsors from the bug, the merge request is already in the review queue, no need to have the bug as well)
| Iain Lane (laney) wrote : | #6 |
I looked to upload this just now. I followed the request in comment #4 to build oxide with it. The oxide build fails with an unrelated error.
FAILED: /usr/bin/
| Hans Joachim Desserud (hjd) wrote : | #7 |
Looks like bug 1496743 mentioned in the previous comment has been fixed. However, in the meantime it looks like oxide now fails to build against qt5.5, so an attempted rebuild would presumably fail similarly. See bug 1500767 for details.
| Timo Jyrinki (timo-jyrinki) wrote : | #8 |
Hey! The Qt 5.5 is not yet in Ubuntu, I just filed the bug to state that Qt 5.5 also can't land (to wily+1) until Oxide builds against it among else. So just ignore that part for the time being.
| Jussi Pakkanen (jpakkane) wrote : | #9 |
Is this now ok to land? It has been stuck in the queue for quite a long time and the only remaining issue is not Ninja's fault (the current version of Ninja would fail the rebuild in a similar way).
| Hans Joachim Desserud (hjd) wrote : | #10 |
Timo: Oh. I thought it had already landed and that a rebuild of oxide would now fail. Sorry about that.
| Launchpad Janitor (janitor) wrote : | #11 |
Status changed to 'Confirmed' because the bug affects multiple users.
| Changed in ninja-build (Ubuntu): | |
| status: | New → Confirmed |
| Daniel Holbach (dholbach) wrote : | #12 |
<dholbach> chrisccoulson, Laney, seb128, Mirv: you all commented on https:/
<ubottu> Launchpad bug 1473680 in ninja-build (Ubuntu) "Please update Ninja from Debian" [Undecided,
<seb128> dholbach, none from me
<Mirv> dholbach: no objections
<chrisccoulson> dholbach, none from me
| Jussi Pakkanen (jpakkane) wrote : | #13 |
Since this did not get into wily, could we get it into xenial now that the gates are open again?
| Martin Pitt (pitti) wrote : | #14 |
Uploaded the merge, thanks! @Jussi: Can we please get this delta into Debian? It's entirely appropriate and desirable to run tests during package build for Debian too, there's no reason why this should be an Ubuntu delta.
| Changed in ninja-build (Ubuntu): | |
| status: | Confirmed → Fix Committed |
Hello Jussi,
Jussi Pakkanen [2015-10-26 20:41 -0000]:
> Since this did not get into wily, could we get it into xenial now that
> the gates are open again?
I uploaded the merge. Can we please get this delta into Debian? It's
entirely appropriate and desirable to run tests during package build
for Debian too, there's no reason why this should be an Ubuntu delta.
Thanks,
Martin
--
Martin Pitt | http://
Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)
| Jussi Pakkanen (jpakkane) wrote : | #16 |
Thanks for the upload. The main reason why the delta is not in Debian is that the maintainer seems to be MIA.
| Launchpad Janitor (janitor) wrote : | #17 |
This bug was fixed in the package ninja-build - 1.5.1-0.1ubuntu1
---------------
ninja-build (1.5.1-0.1ubuntu1) xenial; urgency=medium
* Merge from Debian unstable. (Fixes LP: #1473680)
Remaining changes:
- Run the tests at build time
ninja-build (1.5.1-0.1) experimental; urgency=medium
[Mickaël Guerin]
* Non-maintainer upload.
* New upstream release. Closes: #767813
* Fixed lintian warnings. Closes: #750585, #750583
[Jussi Pakkanen]
* Took Mickaël's packaging changes and got them reviewed
in mentors and fixed the issues raised.
ninja-build (1.3.4-1.2) unstable; urgency=medium
* Non-maintainer upload.
* Add gnukfreebsd.patch to fix platform detection on gnukfreebsd 9 and later.
Thanks to Steven Chamberlain for the patch. (Closes: #717364)
-- Hans Joachim Desserud <email address hidden> Sun, 12 Jul 2015 15:04:44 +0200
| Changed in ninja-build (Ubuntu): | |
| status: | Fix Committed → Fix Released |
| Hans Joachim Desserud (hjd) wrote : | #18 |
\o/ Thanks for uploading.
>The main reason why the delta is not in Debian is that the maintainer seems to be MIA.
The patch has been (attempted) forwarded in https:/


Thanks for reporting this issue.
>It has not migrated to Ubuntu proper for some reason, probably because uploads newer than 1.3.4 are NMUs.
It's because the Ubuntu package contains some Ubuntu-specific patches. Normally packages are synced straight from Debian, but if they have been patched, someone will need to manually merge them in Ubuntu (see https:/ /wiki.ubuntu. com/UbuntuDevel opment/ Merging for more information). You can tell by the version number "1.3.4-1.1ubuntu1" which contains the ubuntu-suffix at the end that it has some Ubuntu-specific patches.
Looks like only a small patch on the Ubuntu-side though, so I might try merging this.