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 637118 - Detect tarball patch changes and warn or alert user
Detect tarball patch changes and warn or alert user
Status: RESOLVED OBSOLETE
Product: jhbuild
Classification: Infrastructure
Component: general
unspecified
Other All
: Normal enhancement
: ---
Assigned To: Jhbuild maintainers
Jhbuild QA
Depends on:
Blocks:
 
 
Reported: 2010-12-13 03:15 UTC by Craig Keogh
Modified: 2021-05-17 15:50 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Craig Keogh 2010-12-13 03:15:21 UTC 
Say the following occurred:
1. User tries to build WebKit (currently from 1.3.7 tarball), it fails.
2. The module file is updated to include a patch which fixes 1. above. The tarball is left at WebKit 1.3.7.
3. Next day, user tries to build WebKit. Still fails as the WebKit untar has already occurred.

The user should be warned or alerted. The user should be informed on what to do to remedy the situation.

One may ask 'why not detect if patch has been applied, if not then apply'. But what if the patch in 2. above replaces a patch. You'd have to reverse the old patch then apply the new patch. That sounds like a lot of work, a warning will probably suffice.
Comment 1 Matthias Clasen 2010-12-16 01:39:02 UTC 
For build slaves it would be much better if jhbuild would just wipe the directory and start over
Comment 2 GNOME Infrastructure Team 2021-05-17 15:50:44 UTC 
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/jhbuild/-/issues/108.