@aklapper Yes, thanks for the link. I did the search for duplicates, but it's hard. I'll close as duplicate.
When searching for a program that is installed in more than one version, e.g. the snaps netbeans
and netbeans-dev
, and their names share a large common prefix, e.g. Apache Netbeans
followed by the part of the name which allows keeping the them appart 15
and (development)
, one cannot be sure which one to select in the search result.
Search for a program which has has a long common prefix in the name matching the name of another program.
Only the first ~13 characters are visible in names in the search results cards (see screenshot).
The cards should allow to distinguish the programs with the need to open "Details" which opens the software center.
When searching for a program that is installed in more than one version, e.g. the snaps netbeans
and netbeans-dev
, and their names share a large common prefix, e.g. Apache Netbeans
followed by the part of the name which allows keeping the them appart 15
and (development)
, one cannot be sure which one to select in the search result.
Search for a program which has has a long common prefix in the name matching the name of another program.
Only the first ~13 characters are visible in names in the search results cards (see screenshot).
The cards should allow to distinguish the programs with the need to open "Details" which opens the software center.
Builds jhbuild
and tests the default module set. The current build result can be found at https://gitlab.gnome.org/krichter/jhbuild/pipelines/33232. There're the following issues:
jhbuild bootstrap
fails due to jhbuild bootstrap: Repository=gnome.org not found for module id=m4-common. Possible repositories are ragel, igj, sqlite, expat, cmake, launchpad, gnome-http, python, cairo, sourceware, libproxy, pkgconfig, tango, ftp.gnu.org, tukaani.org, git.gnome.org, xorg, sourceforge, xmlsoft, dbus
which is probably a bugjhbuild build --nodeps
fails due to *** Error during phase configure of gtk-doc: ########## Error running meson --prefix /root/jhbuild/install --libdir lib --buildtype=debugoptimized /root/jhbuild/checkout/gtk-doc *** [7/208]
I'm grateful for advice how to fix these issues.
According to README.rst
the first setup step is bst build flatpak-runtimes.bstbst build flatpak-runtimes.bst
. Here's what happened on a fresh Ubuntu 21.10:
$ bst build flatpak-runtimes.bst
[--:--:--][][] STATUS Cache usage recomputed: 7B / infinity (0%)
[--:--:--][][] START Build
[--:--:--][][] START Loading elements
[00:00:08][][] SUCCESS Loading elements
[--:--:--][][] START Resolving elements
[00:00:01][][] FAILURE Resolving elements
[00:00:10][][] FAILURE Build
freedesktop-sdk.bst:components/icu.bst [line 37 column 11]: Unexpected key: use-lfs$ bst build flatpak-runtimes.bst
[--:--:--][][] STATUS Cache usage recomputed: 7B / infinity (0%)
[--:--:--][][] START Build
[--:--:--][][] START Loading elements
[00:00:08][][] SUCCESS Loading elements
[--:--:--][][] START Resolving elements
[00:00:01][][] FAILURE Resolving elements
[00:00:10][][] FAILURE Build
freedesktop-sdk.bst:components/icu.bst [line 37 column 11]: Unexpected key: use-lfs
Experienced with 23c70a97. I'm also experiencing this on branch gnome-42
/with b075d3c2.
@akitouni Thanks. I do understand the meaning of the instructions in README.rst
now. "To build a runtime locally, for debugging:" seems like the first thing to do, but following the linked build instructions is. Knowing that I don't know how to make that more clear, I guess it's just me.
@hadess The job seems to be scheduled weekly (maybe after your comment): https://gitlab.gnome.org/GNOME/jhbuild/-/pipeline_schedules.
My MR is basically a QA of jhbuilds function to build GNOME applications from source in a GitLab CI pipeline. I developed it because I never over the course of 10 years managed to build a GNOME end user program like gedit
with jhbuild
due to build errors.
Not every erroneous user behavior can be preempted in a software and not every system can be supported. jhbuild
works on development states of dependencies. However, I don't think that there's a good overview on what is working and what not - yesterday I started a build of the default moduleset an a fresh Ubuntu 21.10 and was missing 5 system dependencies and encountered 3 build errors. librest
apparently can't be build with meson.
I don't whether https://gitlab.gnome.org/GNOME/gnome-build-meta has the same purpose as jhbuild
and is intended to replace it. If this is the case or probable or there's no need identified among GNOME especially jhbuild devs to have stable moduleset, then this MR can be closed as well.
According to README.rst
the first setup step is bst build flatpak-runtimes.bstbst build flatpak-runtimes.bst
. Here's what happened on a fresh Ubuntu 21.10:
$ bst build flatpak-runtimes.bst
[--:--:--][][] STATUS Cache usage recomputed: 7B / infinity (0%)
[--:--:--][][] START Build
[--:--:--][][] START Loading elements
[00:00:08][][] SUCCESS Loading elements
[--:--:--][][] START Resolving elements
[00:00:01][][] FAILURE Resolving elements
[00:00:10][][] FAILURE Build
freedesktop-sdk.bst:components/icu.bst [line 37 column 11]: Unexpected key: use-lfs$ bst build flatpak-runtimes.bst
[--:--:--][][] STATUS Cache usage recomputed: 7B / infinity (0%)
[--:--:--][][] START Build
[--:--:--][][] START Loading elements
[00:00:08][][] SUCCESS Loading elements
[--:--:--][][] START Resolving elements
[00:00:01][][] FAILURE Resolving elements
[00:00:10][][] FAILURE Build
freedesktop-sdk.bst:components/icu.bst [line 37 column 11]: Unexpected key: use-lfs
Experienced with 23c70a97. I'm also experiencing this on branch gnome-42
/with b075d3c2.
I hope you don't mind me linking a workaround for those who cannot downgrade easily: https://askubuntu.com/a/1378583/173287. It describes how to extract a PKCS#8 CA certificate and specify ca
explicitly in the client config file. This allowed me to make the import with PKCS#12 certificate work. This might be an indicator that your suspicion is correct @stas.bucik .