GNOME Bugzilla – Bug 554565
dependency on unreleased ptlib (2.4.2)
Last modified: 2008-10-27 16:08:13 UTC
http://svn.gnome.org/viewvc/ekiga?view=revision&revision=7126 bumped ptlib and opal dependencies to unreleased versions; this logically broke the buildbots (see <http://jhbuild.bxlug.be:8080/ekiga>). Once again, there are rules about GNOME external dependencies, listed at the top of this page http://live.gnome.org/TwoPointTwentythree/ExternalDependencies, and it would be really nice to act according to them.
An user reports a bug in Ekiga. The bug in Ekiga is actually a bug in OPAL/PTLIB. The bug fix in OPAL/PTLIB seems to be good, but unfortunately, it breaks the API. I have two choices : a) I adapt the API in Ekiga, bump the deps, and ask the user to confirm the bug is fixed. b) I do not adapt the API in Ekiga and do not bump the deps and I release 3.0.1 with the bug inside. I prefer a). You prefer b). What can we do ?
It looks like you misunderstood the bug report; I am not arguing against fixing bugs (that doesn't make sense). <http://live.gnome.org/TwoPointTwentythree/ExternalDependencies> has: > If you want to add a new dependency or want one of the minimum versions > updated, make a good case for it on desktop-devel-list (this may only > require a few sentences). So I would prefer you just do that.
Such things unfortunately happen with each release. I do not think it is very convenient to mail d-d-l and argue to increase the minimum versions. I have never seen anybody do it. Is that a common practice ?
I had a quick check for last month and there were at least two queries to update an external dependency: - gtk-vnc: http://mail.gnome.org/archives/desktop-devel-list/2008-September/msg00056.html - rarian: http://mail.gnome.org/archives/desktop-devel-list/2008-September/msg00080.html
I will try to find somebody who can take care of all those GNOME-specific rules and manage releases. You seem to be very well informed and to track Ekiga very closely. Would you accept that task ?
I am tracking ekiga just like other modules, insuring they keep building so users are not at pain when they try jhbuild; and whenever there is a problem I inform the module maintainers. Most often they deal themselves with asking desktop-devel-list for approval (I checked back and it looks like I only asked once for dbus-glib as the bump was required by NetworkManager which is not formally part of the GNOME stack); and I feel they are at a better place since they know best the implications of such bumps. Fox exeample In this specific case I would only get to "Fixed OPAL API breakage and raised requirements accordingly" and wouldn't be able to explain what was fixed. This is why I do not think of myself as the right person for that job.
ptlib 2.4.2 and opal 3.4.2 are now available on download.gnome.org, and jhbuild modulesets have been updated; closing this bug report.