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

2018-07-06 Thread Geert Janssens 
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  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...
> > 
> > I assume that you mean you don’t know what to change bugzilla.gnome.org
> >  references to when they refer to a bug that
> > we didn’t import to 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 #, bug  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 #

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
gnucash-user@gnucash.org
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.

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

2018-07-06 Thread 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  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...
>
> I assume that you mean you don’t know what to change bugzilla.gnome.org
>  references to when they refer to a bug that
> we didn’t import to 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
>  still
> lists *lots* of projects.

Interesting..

> Regards,
> John Ralls

-derek

-- 
   Derek Atkins 617-623-3745
   de...@ihtfp.com www.ihtfp.com
   Computer and Internet Security Consultant

___
gnucash-user mailing list
gnucash-user@gnucash.org
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.

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

2018-07-06 Thread John Ralls 


> On Jul 6, 2018, at 8:30 AM, Derek Atkins  wrote:
> 
> John,
> 
> On Fri, July 6, 2018 10:43 am, John Ralls wrote:
>> 
>> 
>>> On Jul 6, 2018, at 6:49 AM, Derek Atkins  wrote:
>>> 
>>> Richard,
>>> 
>>> Richard Ullger  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...

I assume that you mean you don’t know what to change bugzilla.gnome.org 
 references to when they refer to a bug that we 
didn’t import to 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 
 still lists 
*lots* of projects.

Regards,
John Ralls

___
gnucash-user mailing list
gnucash-user@gnucash.org
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.

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

2018-07-06 Thread Derek Atkins 
John,

On Fri, July 6, 2018 10:43 am, John Ralls wrote:
>
>
>> On Jul 6, 2018, at 6:49 AM, Derek Atkins  wrote:
>>
>> Richard,
>>
>> Richard Ullger  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
   de...@ihtfp.com www.ihtfp.com
   Computer and Internet Security Consultant

___
gnucash-user mailing list
gnucash-user@gnucash.org
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.

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

2018-07-06 Thread John Ralls 


> On Jul 6, 2018, at 6:49 AM, Derek Atkins  wrote:
> 
> Richard,
> 
> Richard Ullger  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
gnucash-user@gnucash.org
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.

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

2018-07-06 Thread Derek Atkins 
Richard,

Richard Ullger  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
   warl...@mit.eduPGP key available
___
gnucash-user mailing list
gnucash-user@gnucash.org
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.

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

2018-07-06 Thread Richard Ullger 
On Fri, 29 Jun 2018, 23:13 John Ralls,  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
> c...@gnucash.bugs Backend-SQL, Backend-XML, Budgets, Build
> System,
>   Business, Currency and Commodity, Engine,
> Python
>   Bindings, Scheduled Transactions
> documentat...@gnucash.bugsDocumentation, Translations, Website
> gene...@gnucash.bugs  General
> imp...@gnome.bugs Import-AqBanking, Import-CSV, Import-OFX,
> Import-
>   Other, Import-QIF, Import-QSF, TXF Export
> ma...@gnucash.bugsMacOS
> repo...@gnucash.bugs  Check Printing, Reports
> u...@gnucash.bugs   Register, Regist-2, User Interface General
> wind...@gnucash.bugs  Windows
> all-b...@gnucash.bugs 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
gnucash-user@gnucash.org
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.