GNU bug report logs - #78663
Apostrophe 2.6.3 depends on GTK+3 while upstream uses GTK4

Previous Next

Package: guix;

Reported by: H Rovol <hanfeifei2020 <at> outlook.com>

Date: Sun, 1 Jun 2025 14:26:03 UTC

Severity: normal

Done: H Rovol <hanfeifei2020 <at> outlook.com>

To reply to this bug, email your comments to 78663 AT debbugs.gnu.org.
There is no need to reopen the bug first.

Toggle the display of automated, internal messages from the tracker.

View this report as an mbox folder, status mbox, maintainer mbox

Report forwarded to bug-guix <at> gnu.org:
bug#78663; Package guix. (Sun, 01 Jun 2025 14:26:03 GMT) Full text and rfc822 format available.
Acknowledgement sent to H Rovol <hanfeifei2020 <at> outlook.com>:
New bug report received and forwarded. Copy sent to bug-guix <at> gnu.org. (Sun, 01 Jun 2025 14:26:04 GMT) Full text and rfc822 format available.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: H Rovol <hanfeifei2020 <at> outlook.com>
To: "bug-guix <at> gnu.org" <bug-guix <at> gnu.org>
Subject: Apostrophe 2.6.3 depends on GTK+3 while upstream uses GTK4
Date: Sun, 1 Jun 2025 14:20:19 +0000

Hello maintainers,

I noticed that the current `apostrophe` package (2.6.3) still depends on 
GTK+3 (`gtk+@3.24.43`) and `libhandy`, while the upstream version has 
migrated to GTK4 (`gtk <at> 4.16.13`)

This could cause a runtime error:

        TypeError: gobject `apostrophe+application+Application' doesn't support property `application_id'

Because the program expects GTK4 semantics, which GTK+3 does not support.

Upstream change reference:
        > https://gitlab.gnome.org/World/apostrophe
        > - GTK4 and GLib development packages: libgtk-4-dev libglib2.0-dev (Line 47 in README.md)
Guix version: guix (GNU Guix) d3334af3958caad3617df5aa9ebe08c76285f345 (x86_64-linux)

Thanks for your work!
Best,
Rovol
Information forwarded to bug-guix <at> gnu.org:
bug#78663; Package guix. (Sun, 01 Jun 2025 16:13:03 GMT) Full text and rfc822 format available.

Message #8 received at 78663 <at> debbugs.gnu.org (full text, mbox):

From: H Rovol <hanfeifei2020 <at> outlook.com>
To: "78663 <at> debbugs.gnu.org" <78663 <at> debbugs.gnu.org>
Subject: bug#78663: close
Date: Sun, 1 Jun 2025 16:12:46 +0000

Hello maintainers,

The bug was caused by a mistake on my end (confusing version 2.6.3 with 3.0.0). Please consider this issue closed.

Best,
Rovol
Reply sent to H Rovol <hanfeifei2020 <at> outlook.com>:
You have taken responsibility. (Sun, 01 Jun 2025 17:18:02 GMT) Full text and rfc822 format available.
Notification sent to H Rovol <hanfeifei2020 <at> outlook.com>:
bug acknowledged by developer. (Sun, 01 Jun 2025 17:18:02 GMT) Full text and rfc822 format available.

Message #13 received at 78663-done <at> debbugs.gnu.org (full text, mbox):

From: H Rovol <hanfeifei2020 <at> outlook.com>
To: "78663-done <at> debbugs.gnu.org" <78663-done <at> debbugs.gnu.org>
Subject: Resolved: bug#78663
Date: Sun, 1 Jun 2025 17:17:00 +0000

Hello maintainers,

After further investigation, I confirm this issue was caused by
my misinterpretation of the dependency chain. The actual problem
has been addressed by submitting a new patch for Apostrophe 3.2.0.

Please close this issue. Thank you for your attention.

Best regards,
Rovol
This bug report was last modified 5 days ago.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.