Bug 2041567 - Please branch and build xpad in epel8
Summary: Please branch and build xpad in epel8
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: xpad
Version: 36
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kevin Fenzi
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-01-17 17:50 UTC by Markus Muckhoff
Modified: 2023-05-25 19:29 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-05-25 19:29:21 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Markus Muckhoff 2022-01-17 17:50:52 UTC
Please branch and build xpad in epel8.

Comment 1 Markus Muckhoff 2022-01-25 14:39:14 UTC
Will you be able to branch and build xpad in epel8?

Comment 2 Ben Cotton 2022-02-08 21:06:13 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 36 development cycle.
Changing version to 36.

Comment 3 Moacyr Prado 2022-02-15 15:06:33 UTC
Will you be able to branch and build xpad in epel9?

Comment 4 Kevin Fenzi 2022-02-19 19:52:31 UTC
Alas, xpad needs gtksourceview3.. and thats not available in epel9/centos-9-stream. ;( 

configure: error: Package requirements (gtksourceview-3.0 >= 3.10) were not met

Can you file a request for that package to be branched for epel9? or I can do so if you prefer.

Comment 5 Markus Muckhoff 2022-02-28 10:44:46 UTC
Dear all,

I filed a ticket (#20591569) requesting to build gtksourceview3 in epel8 / epel9.

Regards
Markus

Comment 6 Markus Muckhoff 2022-02-28 10:48:27 UTC
The correct ticket number is #2059156 (without the trailing 9).

Comment 7 Kevin Fenzi 2022-06-11 18:49:32 UTC
So, newer xpad needs gtksourceview4... which is available in rhel9. Sadly, however, gtksourceview4-devel is not. ;( 

Aldo, it now needs libappindicator-devel.

Comment 8 Markus Muckhoff 2022-08-12 08:24:25 UTC
gtksourceview4-devel is now available in epel8 and epel9. So libappindicator-devel remains as needed dependency in epel8.

I filed a ticket (#2117860) for that.

Regards
Markus

Comment 9 Markus Muckhoff 2022-08-24 15:15:21 UTC
As far as I can understand the answer in Ticket #2117934 there already is a libappindicator-gtk3-devel package in the CBR for epel 8.

So, everything needed to build the package may already be there.

Comment 10 Markus Muckhoff 2022-08-29 12:27:16 UTC
Please note the last comments from the tickets #2117934 and #2117860 from Tomas Popela

Comment 11 Carl George 🤠 2022-08-30 02:30:48 UTC
Please see bug 2117860 comment 5.  xpad doesn't appear to actually need libappindicator-devel or libappindicator-gtk3-devel to build.  Upstream switched to libayatana-appindicator, which is not yet packed in Fedora or EPEL 8.  Removing that build requirement from the rawhide spec file has no effect on a rawhide build.  Building the same spec file for epel8 reveals a different error.

+ autoreconf --force --install
autopoint: *** The AM_GNU_GETTEXT_VERSION declaration in your configure.ac
               file requires the infrastructure from gettext-0.21 but this version
               is older. Please upgrade to gettext-0.21 or newer.

Alternatively, the spec file from the f36 branch, which is on version 5.3.0 and doesn't have the libappindicator-devel build requirement, builds just fine for epel8.  I'd recommend proceeding with that instead.

Comment 12 Kevin Fenzi 2022-08-30 03:27:13 UTC
ok, that all makes sense. 

This request sort of got diverged... it was orig for epel8, but then a epel9 request got mixed in. ;) 

On epel8... I think things are not looking good. I can build against libappindicator-gtk3-devel fine, but then it fails with the gettext version being too old. Patching that out gets to:

Package dependency requirement 'glib-2.0 >= 2.58' could not be satisfied.
Package 'glib-2.0' has version '2.56.4', required version is '>= 2.58'

so, we need an newer glib2. :(

epel9 looks much better. Gettext still needs patching, but then things build fine. 

So, I will request the epel9 branch now.

Comment 13 Kevin Fenzi 2022-08-30 03:28:33 UTC
I thought about doing an older version on epel8, but... not sure how great that will be. No way to update versions, so I would be on the hook to backport fixes. ;(

Comment 14 Ben Cotton 2023-04-25 18:23:15 UTC
This message is a reminder that Fedora Linux 36 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 36 on 2023-05-16.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '36'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 36 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 15 Ludek Smid 2023-05-25 19:29:21 UTC
Fedora Linux 36 entered end-of-life (EOL) status on 2023-05-16.

Fedora Linux 36 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of Fedora Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.