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

classic Classic list List threaded Threaded
7 messages Options
Reply | Threaded
Open this post in threaded view
|

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

Richard Ullger-2
On Fri, 29 Jun 2018, 23:13 John Ralls, <[hidden email]> wrote:

> We've completed the migration of Bugzilla to https://bugs.gnucash.org and
> we're ready to resume normal bug ops there. The updates on
> bugzilla.gnome.org are still running (after 2 hours not quite halfway
> done), but that doesn't affect using https://bugs.gnucash.org.
>
> There's one change since yesterday's announcement: We've shortened the
> pseudo-addresses for bugmail:
>
> Group                         Elements
> [hidden email]             Backend-SQL, Backend-XML, Budgets, Build
> System,
>                               Business, Currency and Commodity, Engine,
> Python
>                               Bindings, Scheduled Transactions
> [hidden email]    Documentation, Translations, Website
> [hidden email]          General
> [hidden email]             Import-AqBanking, Import-CSV, Import-OFX,
> Import-
>                               Other, Import-QIF, Import-QSF, TXF Export
> [hidden email]            MacOS
> [hidden email]          Check Printing, Reports
> [hidden email]               Register, Regist-2, User Interface General
> [hidden email]          Windows
> [hidden email]         Everything
>
> For now we've adopted the Gnome skin for familiarity, but we'd love to
> have someone who's artistically inclined to design us a GnuCash-specific
> one!
>
> Regards,
> John Ralls
>

John,

Some links are pointing back to gnome bugzilla.

See comment 3 on https://bugs.gnucash.org/show_bug.cgi?id=796665

I assume Gnucash bugs in gnome bugzilla will disappear at some point.

Regards,

Richard
_______________________________________________
gnucash-user mailing list
[hidden email]
To update your subscription preferences or to unsubscribe:
https://lists.gnucash.org/mailman/listinfo/gnucash-user
If you are using Nabble or Gmane, please see https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
-----
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.
Reply | Threaded
Open this post in threaded view
|

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

Derek Atkins
Richard,

Richard Ullger <[hidden email]> writes:

> John,
>
> Some links are pointing back to gnome bugzilla.
>
> See comment 3 on https://bugs.gnucash.org/show_bug.cgi?id=796665

The reason for this is that the commentor (YOU!) explicity put in the
URL instead of using the appropriate shorthand "Bug #796665".

At this point I know of no way to fix this.

> I assume Gnucash bugs in gnome bugzilla will disappear at some point.

It's unclear what will happen.  I was under the impression that it would
remain in read-only mode for a while, but it's possible it may
disappear.

> Regards,
>
> Richard

> Please remember to CC this list on all your replies.
> You can do this by using Reply-To-List or Reply-All.

-derek

--
       Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
       Member, MIT Student Information Processing Board  (SIPB)
       URL: http://web.mit.edu/warlord/    PP-ASEL-IA     N1NWH
       [hidden email]                        PGP key available
_______________________________________________
gnucash-user mailing list
[hidden email]
To update your subscription preferences or to unsubscribe:
https://lists.gnucash.org/mailman/listinfo/gnucash-user
If you are using Nabble or Gmane, please see https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
-----
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.
Reply | Threaded
Open this post in threaded view
|

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

John Ralls-2


> On Jul 6, 2018, at 6:49 AM, Derek Atkins <[hidden email]> wrote:
>
> Richard,
>
> Richard Ullger <[hidden email]> writes:
>
>> John,
>>
>> Some links are pointing back to gnome bugzilla.
>>
>> See comment 3 on https://bugs.gnucash.org/show_bug.cgi?id=796665
>
> The reason for this is that the commentor (YOU!) explicity put in the
> URL instead of using the appropriate shorthand "Bug #796665".
>
> At this point I know of no way to fix this.
>

That said, references to non-gnucash bugs using the shorthand will probably get a bad URL because we didn’t copy all of Gnome’s database. There’s no reasonable way to fix that either.

That’s also unlikely to be the only kind of stale URLs in the bug database. The internet has changed a lot over the last 17 years (the oldest bug, 58566, was opened 2001-08-05).

Regards,
John Ralls


_______________________________________________
gnucash-user mailing list
[hidden email]
To update your subscription preferences or to unsubscribe:
https://lists.gnucash.org/mailman/listinfo/gnucash-user
If you are using Nabble or Gmane, please see https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
-----
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.
Reply | Threaded
Open this post in threaded view
|

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

Derek Atkins-3
John,

On Fri, July 6, 2018 10:43 am, John Ralls wrote:

>
>
>> On Jul 6, 2018, at 6:49 AM, Derek Atkins <[hidden email]> wrote:
>>
>> Richard,
>>
>> Richard Ullger <[hidden email]> writes:
>>
>>> John,
>>>
>>> Some links are pointing back to gnome bugzilla.
>>>
>>> See comment 3 on https://bugs.gnucash.org/show_bug.cgi?id=796665
>>
>> The reason for this is that the commentor (YOU!) explicity put in the
>> URL instead of using the appropriate shorthand "Bug #796665".
>>
>> At this point I know of no way to fix this.
>>
>
> That said, references to non-gnucash bugs using the shorthand will
> probably get a bad URL because we didn’t copy all of Gnome’s database.
> There’s no reasonable way to fix that either.
>
> That’s also unlikely to be the only kind of stale URLs in the bug
> database. The internet has changed a lot over the last 17 years (the
> oldest bug, 58566, was opened 2001-08-05).

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 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.

Searching for "Bug # xxx" which wasn't imported is going to be harder.

I'm not sure what to change the bugzilla.gnome.org references to...

> Regards,
> John Ralls

-derek

--
       Derek Atkins                 617-623-3745
       [hidden email]             www.ihtfp.com
       Computer and Internet Security Consultant

_______________________________________________
gnucash-user mailing list
[hidden email]
To update your subscription preferences or to unsubscribe:
https://lists.gnucash.org/mailman/listinfo/gnucash-user
If you are using Nabble or Gmane, please see https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
-----
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.
Reply | Threaded
Open this post in threaded view
|

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

John Ralls-2


> On Jul 6, 2018, at 8:30 AM, Derek Atkins <[hidden email]> wrote:
>
> John,
>
> On Fri, July 6, 2018 10:43 am, John Ralls wrote:
>>
>>
>>> On Jul 6, 2018, at 6:49 AM, Derek Atkins <[hidden email]> wrote:
>>>
>>> Richard,
>>>
>>> Richard Ullger <[hidden email]> writes:
>>>
>>>> John,
>>>>
>>>> Some links are pointing back to gnome bugzilla.
>>>>
>>>> See comment 3 on https://bugs.gnucash.org/show_bug.cgi?id=796665
>>>
>>> The reason for this is that the commentor (YOU!) explicity put in the
>>> URL instead of using the appropriate shorthand "Bug #796665".
>>>
>>> At this point I know of no way to fix this.
>>>
>>
>> That said, references to non-gnucash bugs using the shorthand will
>> probably get a bad URL because we didn’t copy all of Gnome’s database.
>> There’s no reasonable way to fix that either.
>>
>> That’s also unlikely to be the only kind of stale URLs in the bug
>> database. The internet has changed a lot over the last 17 years (the
>> oldest bug, 58566, was opened 2001-08-05).
>
> 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.)

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.

Regards,
John Ralls

_______________________________________________
gnucash-user mailing list
[hidden email]
To update your subscription preferences or to unsubscribe:
https://lists.gnucash.org/mailman/listinfo/gnucash-user
If you are using Nabble or Gmane, please see https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
-----
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.
Reply | Threaded
Open this post in threaded view
|

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

Derek Atkins-3

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
       [hidden email]             www.ihtfp.com
       Computer and Internet Security Consultant

_______________________________________________
gnucash-user mailing list
[hidden email]
To update your subscription preferences or to unsubscribe:
https://lists.gnucash.org/mailman/listinfo/gnucash-user
If you are using Nabble or Gmane, please see https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
-----
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.
Reply | Threaded
Open this post in threaded view
|

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

Geert Janssens-4
Op vrijdag 6 juli 2018 18:14:08 CEST schreef 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.
>
Depends on how much effort we're willing to spend.

You can query the db for all variations of bug #<number>, bug <number> and
bugzilla.gnome.org/show_bug.cgi.

The first two formats when referring to gnucash bugs can be left as they are.
The third format when referring to gnucash bugs can be rewritten to
bug #<number>

If the bugs don't refer to a gnucash bug you could try to find a
gitlab.ngome.org url in the last few comments on the bug on bugzilla.gnome.org
and substitute that in our comments. If no gitlab.gnome.org url is found in
the bug, just replace it with the bugzilla.gnome.org url. There's not
alternative in that case (this last option is needed for the first two
formats, as our bug db doesn't have these bugs).

Geert


_______________________________________________
gnucash-user mailing list
[hidden email]
To update your subscription preferences or to unsubscribe:
https://lists.gnucash.org/mailman/listinfo/gnucash-user
If you are using Nabble or Gmane, please see https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
-----
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.