Skip Menu |

This queue is for tickets about the Gtk2-GladeXML CPAN distribution.

Report information
The Basics
Id: 107572
Status: resolved
Priority: 0/
Queue: Gtk2-GladeXML

People
Owner: XAOC [...] cpan.org
Requestors: KAPPA [...] cpan.org
Cc: SLAFFAN [...] cpan.org
AdminCc:

Bug Information
Severity: Normal
Broken in: 1.007
Fixed in: (no value)



Subject: Wrong dependencies in META.yml, installation with CPAN clients fails
CPAN Meta spec 1.3 didn't have configure phase dependencies and cpanminus (and CPAN.pm) fails to install this dist. I attach a new META.yml upgraded to 1.4 with configure_requires.
Subject: META.yml
--- abstract: 'Create user interfaces directly from Glade XML files.' author: - unknown configure_requires: ExtUtils::Depends: '0.300' ExtUtils::PkgConfig: '1.000' build_requires: Glib: '1.020' Gtk2: '1.000' dynamic_config: 1 generated_by: 'ExtUtils::MakeMaker version 6.44, CPAN::Meta::Converter version 2.142690' license: gpl_2 meta-spec: url: http://module-build.sourceforge.net/META-spec-v1.4.html version: '1.4' name: Gtk2-GladeXML version: '1.007'
On Tue Oct 06 09:10:48 2015, KAPPA wrote: Show quoted text
> CPAN Meta spec 1.3 didn't have configure phase dependencies and > cpanminus (and CPAN.pm) fails to install this dist. > > I attach a new META.yml upgraded to 1.4 with configure_requires.
The git repository for Gtk2::GladeXML was archived a while ago by the GNOME admins due to inactivity. We would need to ask for it to be reinstated in order to apply this patch. Is it worth the effort?
06 Eki 2015 Sal, 18:22:48 tarihinde, XAOC yazdı: Show quoted text
> On Tue Oct 06 09:10:48 2015, KAPPA wrote:
> > CPAN Meta spec 1.3 didn't have configure phase dependencies and > > cpanminus (and CPAN.pm) fails to install this dist. > > > > I attach a new META.yml upgraded to 1.4 with configure_requires.
> > > The git repository for Gtk2::GladeXML was archived a while ago by the > GNOME admins due to inactivity. We would need to ask for it to be > reinstated in order to apply this patch. Is it worth the effort?
Does GNOME admins' decision prevent us from uploading a new version of this dist? Also, this change updates an old but useful package to the standards of the current CPAN. Sounds like a worthwhile activity.
On Tue Oct 06 19:06:23 2015, KAPPA wrote: Show quoted text
> Does GNOME admins' decision prevent us from uploading a new version of > this dist?
Absolutely. GladeXML was deprecated by the upstream developers [1] in 2009. Is there any valid reason you don't want/you can't to switch to using Gtk2::Builder[2]? [1] https://mail.gnome.org/archives/devel-announce-list/2009-May/msg00003.html [2] http://gtk2-perl.sourceforge.net/doc/pod/Gtk2/Builder.html
06 Eki 2015 Sal, 20:05:11 tarihinde, XAOC yazdı: Show quoted text
> On Tue Oct 06 19:06:23 2015, KAPPA wrote:
> > Does GNOME admins' decision prevent us from uploading a new version > > of > > this dist?
> > Absolutely. GladeXML was deprecated by the upstream developers [1] in > 2009. Is there any valid reason you don't want/you can't to switch to > using Gtk2::Builder[2]? > > [1] https://mail.gnome.org/archives/devel-announce-list/2009- > May/msg00003.html > [2] http://gtk2-perl.sourceforge.net/doc/pod/Gtk2/Builder.html
Switching to GtkBuilder requires resources. It may be planned but right now, libglade works ok and Gtk2::GladeXML works ok if only has some minor problems when installing from CPAN. The proposed change is more about CPAN and its client ecosystem than about Gtk/GNOME. I suppose that we are able to fix it without bothering GNOME people. I am ready to upload and co-maintain this.
On Wed Oct 07 06:21:22 2015, KAPPA wrote: Show quoted text
> Switching to GtkBuilder requires resources. It may be planned but > right now, libglade works ok and Gtk2::GladeXML works ok if only has > some minor problems when installing from CPAN.
Unarchiving and updating Gtk2::GladeXML also requires resources; not only Gtk-Perl project resources, but Gnome sysadmin resources. Show quoted text
> The proposed change is more about CPAN and its client ecosystem than > about Gtk/GNOME. I suppose that we are able to fix it without > bothering GNOME people. I am ready to upload and co-maintain this.
IMO comaint isn't really an option here; that would mean we (the Gtk-Perl project) were open to to expending resources on software that was effectively abandoned by the upstream developers over 6 years ago. For people who are already using Gtk-Perl, and more importantly, people who might want to use it in the future, the way forward is to use Gtk2::Builder instead of Gtk2::GladeXML. You should take this fact into account for your future project planning. So, from here, what I will do is I will ask the Gnome sysadmins to unarchive Gtk2::GladeXML. If I get push access to the Gtk2::GladeXML repo, I'll apply your updated meta file; in addition, I will clearly mark the module as deprecated in favor of Gtk2::Builder, and do a "final" release for this module. I will also clearly state in the POD that any code that is using Gtk2::GladeXML should be migrated to Gtk2::Builder, and not to expect any more releases for Gtk2::GladeXML. From that point on, the only changes that will be accepted will be patches for changes made by the upstream Gnome libglade project; seeing as how the Gnome devs aren't making any more releases for libglade, I don't expect any new changes to Gtk2::GladeXML. If I don't get push access, or if I do get a chance to make a release and you want more changes past that point, what I recommend you do is to fork the module from Git, and create a new module on CPAN, making it explicitly clear that 1) the upstream library for this module is deprecated, and 2) that you are the sole point of support for that module, not the Gtk-Perl project. If you do decide to fork and release to CPAN, do not use the Gtk2:: toplevel namespace; Gtk2::Ex:: would be more appropriate. You could also use something like pinto to build a private CPAN repo to publish your forked module, if you don't feel like going through the work of supporting a module on CPAN. I'll update this ticket once I hear back from the Gnome sysadmins.
On Fri Oct 09 12:41:32 2015, XAOC wrote: Show quoted text
> On Wed Oct 07 06:21:22 2015, KAPPA wrote:
> > Switching to GtkBuilder requires resources. It may be planned but > > right now, libglade works ok and Gtk2::GladeXML works ok if only has > > some minor problems when installing from CPAN.
> > Unarchiving and updating Gtk2::GladeXML also requires resources; not > only Gtk-Perl project resources, but Gnome sysadmin resources. >
> > The proposed change is more about CPAN and its client ecosystem than > > about Gtk/GNOME. I suppose that we are able to fix it without > > bothering GNOME people. I am ready to upload and co-maintain this.
> > IMO comaint isn't really an option here; that would mean we (the Gtk- > Perl project) were open to to expending resources on software that was > effectively abandoned by the upstream developers over 6 years ago. For > people who are already using Gtk-Perl, and more importantly, people > who might want to use it in the future, the way forward is to use > Gtk2::Builder instead of Gtk2::GladeXML. You should take this fact > into account for your future project planning. > > So, from here, what I will do is I will ask the Gnome sysadmins to > unarchive Gtk2::GladeXML. > > If I get push access to the Gtk2::GladeXML repo, I'll apply your > updated meta file; in addition, I will clearly mark the module as > deprecated in favor of Gtk2::Builder, and do a "final" release for > this module. I will also clearly state in the POD that any code that > is using Gtk2::GladeXML should be migrated to Gtk2::Builder, and not > to expect any more releases for Gtk2::GladeXML. From that point on, > the only changes that will be accepted will be patches for changes > made by the upstream Gnome libglade project; seeing as how the Gnome > devs aren't making any more releases for libglade, I don't expect any > new changes to Gtk2::GladeXML. > > If I don't get push access, or if I do get a chance to make a release > and you want more changes past that point, what I recommend you do is > to fork the module from Git, and create a new module on CPAN, making > it explicitly clear that 1) the upstream library for this module is > deprecated, and 2) that you are the sole point of support for that > module, not the Gtk-Perl project. > > If you do decide to fork and release to CPAN, do not use the Gtk2:: > toplevel namespace; Gtk2::Ex:: would be more appropriate. > > You could also use something like pinto to build a private CPAN repo > to publish your forked module, if you don't feel like going through > the work of supporting a module on CPAN. > > I'll update this ticket once I hear back from the Gnome sysadmins.
Thanks for the details. For some background, Kappa submitted this as part of the CPAN Pull Request challenge, for which he was assigned my Biodiverse software for October. The Biodiverse GUI has been in development since about 2005, although the git repo only contains changes from 2010. https://github.com/shawnlaffan/biodiverse/ If the full git history of Gtk2::GladeXML is not needed to update the Meta.yml file then gitpan might be of use. https://github.com/gitpan/Gtk2-GladeXML That said, the META.yml problem is not a big issue for my use case. The Biodiverse installation instructions make it clear that Gtk2::GladeXML needs two cpanm calls. I also have an open issue to shift across to Gtk2::Builder, so this ticket is more impetus to do so. https://github.com/shawnlaffan/biodiverse/issues/413 Regards, Shawn.
On Fri Oct 09 17:57:42 2015, SLAFFAN wrote: Show quoted text
> If the full git history of Gtk2::GladeXML is not needed to update the > Meta.yml file then gitpan might be of use. > https://github.com/gitpan/Gtk2-GladeXML
We have read-only access to the "official" repos hosted on gnome.org, which has the commit history that gitpan doesn't. Repo is here: https://git.gnome.org/browse/archive/perl-Gtk2-GladeXML/ I'd like to see if I can get read-write access to the repo. After I'm done deprecating the module, if I can't push my changes to the official repo, I can send a final patch to the mailing list that can then be applied to a clone of the "official" repo as the "last official update". Show quoted text
> That said, the META.yml problem is not a big issue for my use case. > The Biodiverse installation instructions make it clear that > Gtk2::GladeXML needs two cpanm calls.
Yeah, I do want to try and get this going so I can mark the module as deprecated on CPAN, which is where most people find it. I also want to announce the deprecation to the list, as before it was sort of "understood", but I'm realizing now that it should be explicit. Show quoted text
> I also have an open issue to shift across to Gtk2::Builder, so this > ticket is more impetus to do so. > https://github.com/shawnlaffan/biodiverse/issues/413
I have a feeling you're not alone here, hence the desire to post to the list about it. FWIW, all of the modules that use GTK+2/Gnome2 libraries are no longer actively maintained, although the main Perl Gtk2 module does see updates, not many of the other modules do. You may want to take a look at your project's list of dependencies with this in mind.
On Fri Oct 09 18:59:32 2015, XAOC wrote: Show quoted text
> On Fri Oct 09 17:57:42 2015, SLAFFAN wrote:
> > If the full git history of Gtk2::GladeXML is not needed to update the > > Meta.yml file then gitpan might be of use. > > https://github.com/gitpan/Gtk2-GladeXML
> > We have read-only access to the "official" repos hosted on gnome.org, > which has the commit history that gitpan doesn't. > > Repo is here: https://git.gnome.org/browse/archive/perl-Gtk2-GladeXML/ > > I'd like to see if I can get read-write access to the repo. After I'm > done deprecating the module, if I can't push my changes to the > official repo, I can send a final patch to the mailing list that can > then be applied to a clone of the "official" repo as the "last > official update". >
> > That said, the META.yml problem is not a big issue for my use case. > > The Biodiverse installation instructions make it clear that > > Gtk2::GladeXML needs two cpanm calls.
> > Yeah, I do want to try and get this going so I can mark the module as > deprecated on CPAN, which is where most people find it. I also want > to announce the deprecation to the list, as before it was sort of > "understood", but I'm realizing now that it should be explicit. >
> > I also have an open issue to shift across to Gtk2::Builder, so this > > ticket is more impetus to do so. > > https://github.com/shawnlaffan/biodiverse/issues/413
> > I have a feeling you're not alone here, hence the desire to post to > the list about it. > > FWIW, all of the modules that use GTK+2/Gnome2 libraries are no longer > actively maintained, although the main Perl Gtk2 module does see > updates, not many of the other modules do. You may want to take a > look at your project's list of dependencies with this in mind.
Thanks. I also know I need to shift to Gtk3 at some stage, but that's not for discussion in this ticket. Regards, Shawn.
Update from the gnome.org sysadmin ticket to get the repo unarchived; Comment # 1 on bug 756307 from Andrea Veri I'm not sure what the policy with these kind of requests is to be honest. I'm CCing Javier as he might be able to provide us an answer as he's currently one of the members of the GNOME release team.
Hi everybody, We were able to get this Git repo unarchived, and have formally announced the deprecation of this module (Gtk2::GladeXML) in [1], [2], and [3]; the deprecation commit is currently waiting in a GitLab merge request [4]. The fix to Makefile.PL to generate a correct META.[json|yml] was made in commit b6c899b7 [5], which has been pushed to 'master', and also has been tested on a Debian Stretch (7.x) system by installing the unpacked tarball via cpanminus. Do you both want to keep this ticket open until the META changes are released with the last commits to this module in December 2020, or can we close this ticket now? Thanks! [1] Deprecation announcement: https://tinyurl.com/y4u6b33f [2] Full list of deprecated modules and their replacements: https://tinyurl.com/yxhmmu49 [3] Deprecation patches (1st round, more to come): https://tinyurl.com/yy7zq2d5 [4] https://gitlab.gnome.org/GNOME/perl-gtk2-gladexml/-/merge_requests/1 [5] https://gitlab.gnome.org/GNOME/perl-gtk2-gladexml/-/commit/b6c899b7f09fb14dad53b7dca36430713fee3607
Closing is fine by me. Shawn. On Thu Oct 15 02:01:34 2020, XAOC wrote: Show quoted text
> Hi everybody, > > We were able to get this Git repo unarchived, and have formally > announced the deprecation of this module (Gtk2::GladeXML) in [1], [2], > and [3]; the deprecation commit is currently waiting in a GitLab merge > request [4]. > > The fix to Makefile.PL to generate a correct META.[json|yml] was made > in commit b6c899b7 [5], which has been pushed to 'master', and also > has been tested on a Debian Stretch (7.x) system by installing the > unpacked tarball via cpanminus. > > Do you both want to keep this ticket open until the META changes are > released with the last commits to this module in December 2020, or can > we close this ticket now? > > Thanks! > > [1] Deprecation announcement: https://tinyurl.com/y4u6b33f > [2] Full list of deprecated modules and their replacements: > https://tinyurl.com/yxhmmu49 > [3] Deprecation patches (1st round, more to come): > https://tinyurl.com/yy7zq2d5 > [4] https://gitlab.gnome.org/GNOME/perl-gtk2-gladexml/- > /merge_requests/1 > [5] https://gitlab.gnome.org/GNOME/perl-gtk2-gladexml/- > /commit/b6c899b7f09fb14dad53b7dca36430713fee3607
Marking ticket as 'resolved'. Thanks!