-
-
Notifications
You must be signed in to change notification settings - Fork 59
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
mate-control-center 1.26.0 build fails if glib is < 2.66 #655
Comments
Which distro is using glib <=2.66 ? |
https://pkgs.org/search/?q=glib
I had to build my packages reverting 71c7563. |
I am in doubt that all those distros will get an update by distro package maintainers. |
Btw. why not open a PR which use old and new code with a glib check? |
You're right, @raveit65. Let's face it: Ubuntu LTS releases have never (that I know of) upgraded desktop environment packages much beyond the initial release of the LTS. It's simply the antithesis to the LTS release idea to include a newer major version of the MATE desktop in an already-produced LTS release. The closest that we have thus far is this unstable MATE PPA, which targets Ubuntu MATE 21.04 Hirsute Hippo -- which is not an LTS release. |
Again, why not opening a PR with
instead of removing new code in your builds? |
I ran into this building MATE Desktop 1.26 for Ubuntu 20.04. I have submitted this simple PR: But, I think Linux Mint will want to ship MATE Desktop 1.26 which is currently using Ubuntu 20.04 as the base OS. So, I have got a simple patch that enables @raveit65 Would you prefer I submit a PR that uses |
@flexiondotorg |
g_bookmark_file_set_modified_date_time is used in libslab/bookmark-agent.c which sets the last time the bookmark for uri was last modified. g_bookmark_file_set_modified_date_time is only available in glibc 2.66 and newer.
Because commit 71c7563, mate-control-center 1.26.0 only builds with glib >= 2.66. According to GTK documentation, g_bookmark_file_set_modified_date_time is available only in glib >= 2.66.
The text was updated successfully, but these errors were encountered: