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 313147 - Prominently mention http://live.gnome.org/JhbuildIssues
Prominently mention http://live.gnome.org/JhbuildIssues
Status: RESOLVED OBSOLETE
Product: jhbuild
Classification: Infrastructure
Component: general
unspecified
Other All
: Normal enhancement
: ---
Assigned To: James Henstridge
Jhbuild QA
Depends on:
Blocks:
 
 
Reported: 2005-08-10 18:09 UTC by Olav Vitters
Modified: 2021-05-17 15:49 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Olav Vitters 2005-08-10 18:09:40 UTC
http://live.gnome.org/JhbuildIssues contains a list of fixes for common jhbuild
problems. As it is on the wiki, it should usually be very up-to-date. It could
be added to the README, but I'd really like a more visible place. Ideally
whenever jhbuild fails it should show a short message mentioning the wiki page.

Suggested message:
Solutions to common jhbuild problems can be found at
http://live.gnome.org/JhbuildIssues

It is a bit too long, I'd like 80 chars maximum so it fits on one line.

The page doesn't just list problems within modules. It also explains missing
packages, etc (it is not meant to work around bugs in a module).
Comment 1 James Henstridge 2005-08-22 09:44:43 UTC
My main problem with this page is that people might treat it as a bug tracker
(it seems that some people have already added what are essentially bug reports
there).

I've already got a bug tracker for jhbuild, as do the modules that jhbuild
builds.  I'm sure most of these developers don't want yet another place to
search for bug reports.
Comment 2 Thierry Moisan 2005-11-03 01:12:51 UTC
A message has been added so that people on this page thatknow that this is not a
bug report place.
Comment 3 Owen Taylor 2007-09-28 15:54:01 UTC
I think a lot of the stuff on those pages reflects underlying dependency management problems. If someone is jhbuilding on Debian, jhbuild should make sure that libtiff4-dev is installed before trying to build GTK+. (And in fact, before starting to build anything to avoid having to babysit the build.)
Comment 4 Craig Keogh 2007-12-22 10:50:24 UTC
FYI tinderbox output provides a helper link to the Gnome Live! wiki (see bug 437144).
Comment 5 Dan Winship 2009-12-04 15:31:35 UTC
rather than linking to JhbuildIssues directly, you should be able to specify a help URI as a node/attribute in the moduleset file. Eg, for the gnome-shell moduleset we'd link to "http://live.gnome.org/GnomeShell#building" instead (or possibly a new subpage) since the common problems for gnome-shell building are different from the common problems for the standard gnome jhbuild module.
Comment 6 Dimitri John Ledkov 2010-04-28 15:01:00 UTC
well ok but modulesets include other modulesets quite often then you will end up with a bunch of links thrown at you, discouraging to look at any of them.... =)
Comment 7 Tshepang Lekhonkhobe 2010-11-22 20:04:16 UTC
The problem with that page is that it quickly gets outdated. I'm not sure if it's good to keep around, especially because it's so easy to report bugs, as well as to pop into IRC.
Comment 8 GNOME Infrastructure Team 2021-05-17 15:49:02 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/93.