[GNC] [GNC-dev] Bugs.gnucash.org Up and Running

[Derek Atkins]

On Fri, July 6, 2018 11:59 am, John Ralls wrote:
>
>> I suspect I could write a script using the Perl interface that would
>> search for any references like this, and possibly hand-modify the SQL
>> tables that need adjusting.   If nothing else I can look for any comment
>> references to bugzilla.gnome.org <http://bugzilla.gnome.org/> or a bug#
>> that's not in the database.
>>
>> Actually, I can probably do that in the json!  So there are 361 bugs
>> that
>> have a reference to "show_bug.cgi".  Only 287 of those reference
>> bugzilla.gnome.org/show_bug.cgi
>> <http://bugzilla.gnome.org/show_bug.cgi>.
>>
>> Searching for "Bug # xxx" which wasn't imported is going to be harder.
>>
>> I'm not sure what to change the bugzilla.gnome.org
>> <http://bugzilla.gnome.org/> references to...
>
> I assume that you mean you don’t know what to change bugzilla.gnome.org
> <http://bugzilla.gnome.org/> references to when they refer to a bug that
> we didn’t import to bugs.gnucash.org <http://bugs.gnucash.org/>. I suppose
> that there are two alternatives: We can import those bugs too or just
> leave the links as-is. I don’t think that we want to import them. (The
> third alternative, find their gitlab instances, will likely apply only to
> a very few of them: Only open bugs being actively worked on or identified
> as still a serious problem were migrated.)

Yes.

I can easily change local references.

I don't know how to modify references to bugs we didn't import.

> It’s worth noting that Gnome missed their date for shutting down new bugs,
> too. https://bugzilla.gnome.org/enter_bug.cgi?classification=__all
> <https://bugzilla.gnome.org/enter_bug.cgi?classification=__all> still
> lists *lots* of projects.

Interesting..

> Regards,
> John Ralls

-derek

-- 
       Derek Atkins                 617-623-3745
       derek at ihtfp.com             www.ihtfp.com
       Computer and Internet Security Consultant