After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 794254 - build: Also call it 2.28.0 in meson.build
build: Also call it 2.28.0 in meson.build
Status: RESOLVED DUPLICATE of bug 794252
Product: atk
Classification: Platform
Component: general
unspecified
Other All
: Normal normal
: ---
Assigned To: ATK maintainer(s)
ATK maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2018-03-12 09:53 UTC by Dominique Leuenberger
Modified: 2018-03-12 11:02 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
build: Also call it 2.28.0 in meson.build (646 bytes, patch)
2018-03-12 09:53 UTC, Dominique Leuenberger 		none Details | Review

Description Dominique Leuenberger 2018-03-12 09:53:20 UTC 
configure.ac specifies the version to be 2.28.0, meson 2.28.
The meson build script though expects a 3-part version. Currently the build fails with:

[   43s] Build machine cpu: x86_64
[   43s] 
[   43s] meson.build:17:0: ERROR: Index 2 out of bounds of array of size 2.
[   43s] 
[   43s] A full log can be found at /home/abuild/rpmbuild/BUILD/atk-2.28.0/build/meson-logs/meson-log.txt
[   43s] error: Bad exit status from /var/tmp/rpm-tmp.ww2HQr (%build)
Comment 1 Dominique Leuenberger 2018-03-12 09:53:26 UTC 
Created attachment 369569 [details] [review]
build: Also call it 2.28.0 in meson.build
Comment 2 Emmanuele Bassi (:ebassi) 2018-03-12 10:56:02 UTC 
Dupe of bug 794252, but the approach in attachment 369569 [details] [review] is correct.

It'll probably need a 2.28.0.1 release, though.

*** This bug has been marked as a duplicate of bug 794252 ***
Comment 3 Alejandro Piñeiro Iglesias (IRC: infapi00) 2018-03-12 11:02:56 UTC 
(In reply to Emmanuele Bassi (:ebassi) from comment #2)
> Dupe of bug 794252, but the approach in attachment 369569 [details] [review] [review]
> is correct.
> 
> It'll probably need a 2.28.0.1 release, though.

Yes, I will roll a new one later.