I'm not sure my main point was understood. Quite apart from all links pointing 
to the old database, where each bug report ends with a link to the report in 
the new database, the two links I mentioned are wrong. The both point to a bug 
number that is different from the visible text. The visible text bug number is 
right, but if you click on the link it takes you to a different numbered bug.

I'm pretty sure it was bad copy/pasting by somebody, because they two both take 
you to the _same_ wrong bug number.

> From: David Cousens <davidcous...@bigpond.com>
> 
> I think this arises because the shift to https://bugs.gnucash.org 
> occurred after the release of V3.2 so https://bugzilla.gnome.org was
> the active reporting system at the time of the release which is why the
> links point there. 
> 
> Those bugs are all duplicated into https://bugs.gnucash.org so you can
> just search for them using the id. 
> 
> Alternatively the format of the links is the same, so if you open the
> link in a new tab from the News page, then substitute bugs.gnucash.org
> for bugzilla.gnucash.org in the address bar and hit enter it will take
> you to the bug in the new bugs.gnucash.org site.

-- 
Stan Brown
the_stan_br...@fastmail.fm
http://BrownMath.com
http://OakRoadSystems.com/

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

Reply via email to