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 350510 - Jhbuild should tell me when I need to re-run bootstrap
Jhbuild should tell me when I need to re-run bootstrap
Status: RESOLVED FIXED
Product: jhbuild
Classification: Infrastructure
Component: general
unspecified
Other Linux
: Normal normal
: ---
Assigned To: James Henstridge
Jhbuild QA
Depends on:
Blocks:
 
 
Reported: 2006-08-09 00:46 UTC by Federico Mena Quintero
Modified: 2008-06-22 19:49 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Federico Mena Quintero 2006-08-09 00:46:29 UTC 
Pyrex was added relatively recently to the bootstrap meta-module.  This is needed, for example, to build dbus-python.

I hand't run "jhbuild bootstrap" for ages, so my build environment didn't have pyrex in it.  Dbus-python was thus unbuildable.

Jhbuild should tell me when its build environment is outdated and I need to run "jhbuild bootstrap" again.
Comment 1 Marc-Andre Lureau 2007-07-07 16:52:21 UTC 
Hi,

would it be enough to check that the installed date of the different bootstrap dependency packages are newer than the bootstrap moduleset file itself?

(btw, pyrex has been removed by Elijah the 4/4/2007)
Comment 2 Frederic Peters 2008-06-22 19:49:35 UTC 
I finally implemented this feature.

2008-06-22  Frederic Peters  <fpeters@0d.be>

        * jhbuild/commands/base.py: check if the bootstrap moduleset has
        been updated before running build and buildone commands, and notify
        the user he may want to run jhbuild bootstrap if that is the case.
        (closes: #350510)