[Bug 831716] Moving legacy code out of perl-JSON-RPC breaks Bugzilla

2016-08-04 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=831716 Paul Roubekas changed: What|Removed |Added CC||paul@orthogroup.holdings --- Comment #

[Bug 831716] Moving legacy code out of perl-JSON-RPC breaks Bugzilla

2016-08-04 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=831716 --- Comment #12 from Emmanuel Seyman --- (In reply to Paul Roubekas from comment #11) > > Can't locate JSON/RPC/Legacy/Server/CGI.pm in @INC (you may need to > install the JSON::RPC::Legacy::Server::CGI module) (@INC contains: Paul, I beli

[Bug 831716] Moving legacy code out of perl-JSON-RPC breaks Bugzilla

2016-08-04 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=831716 Paul Roubekas changed: What|Removed |Added CC||paul@orthogroup.holdings --- Comment #

[Bug 831716] Moving legacy code out of perl-JSON-RPC breaks Bugzilla

2012-07-20 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=831716 Fedora Update System changed: What|Removed |Added Status|ON_QA |CLOSED Resolution|---

[Bug 831716] Moving legacy code out of perl-JSON-RPC breaks Bugzilla

2012-07-11 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=831716 --- Comment #9 from Fedora Update System --- perl-JSON-RPC-1.03-2.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/perl-JSON-RPC-1.03-2.fc17 -- You are receiving this mail because: You are on the CC li

[Bug 831716] Moving legacy code out of perl-JSON-RPC breaks Bugzilla

2012-07-02 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=831716 Fedora Update System changed: What|Removed |Added Status|MODIFIED|ON_QA --- Comment #8 from Fedora

[Bug 831716] Moving legacy code out of perl-JSON-RPC breaks Bugzilla

2012-07-01 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=831716 --- Comment #7 from Fedora Update System --- perl-JSON-RPC-1.03-1.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/perl-JSON-RPC-1.03-1.fc17 -- You are receiving this mail because: You are on the CC li

[Bug 831716] Moving legacy code out of perl-JSON-RPC breaks Bugzilla

2012-06-16 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=831716 --- Comment #6 from Emmanuel Seyman --- Folks, here's the game plan to be implemented soon. * Update to 1.03 * Merge back the legacy implementation in the main package * Split the different server implementations in their own packages The main

[Bug 831716] Moving legacy code out of perl-JSON-RPC breaks Bugzilla

2012-06-15 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=831716 --- Comment #5 from Petr Pisar --- (In reply to comment #3) > (In reply to comment #2) > > This is wrong approach on Fedora. It should check for perl modules, not for > > RPM packages. > > This is exactly what Bugzilla does. It looks for JSON::R

[Bug 831716] Moving legacy code out of perl-JSON-RPC breaks Bugzilla

2012-06-14 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=831716 Emmanuel Seyman changed: What|Removed |Added Status|NEW |ASSIGNED --- Comment #4 from Emmanuel

[Bug 831716] Moving legacy code out of perl-JSON-RPC breaks Bugzilla

2012-06-14 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=831716 --- Comment #3 from Frédéric Buclin --- (In reply to comment #2) > This is wrong approach on Fedora. It should check for perl modules, not for > RPM packages. This is exactly what Bugzilla does. It looks for JSON::RPC. This is supposed to mean t

[Bug 831716] Moving legacy code out of perl-JSON-RPC breaks Bugzilla

2012-06-13 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=831716 Petr Pisar changed: What|Removed |Added CC||ppi...@redhat.com --- Comment #2 from Petr

[Bug 831716] Moving legacy code out of perl-JSON-RPC breaks Bugzilla

2012-06-13 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=831716 --- Comment #1 from Frédéric Buclin --- To be clear: I know that the legacy code is available in two separate packages and that both are needed for Bugzilla to work. What I'm asking for is for checksetup.pl to be aware of this split and ask for t