> On May 20, 2018, at 6:55 AM, Derek Atkins <de...@ihtfp.com> wrote: > > Hi, > > I blew away the migration DB and tried to load the full set of bugs, but > I've run into a dependency problem. I've got 185 bugs that can't sort > dependencies. The first one is interesting: > > https://bugzilla.gnome.org/show_bug.cgi?id=89813 > > This gnucash bug was closed as a duplicate of: > > https://bugzilla.gnome.org/show_bug.cgi?id=67416 > > Small problem is that 67416 is not a gnucash bug, it's a gnome-print bug, > so I'm not pulling it in the migration. > > This is only the first of the list (I've included the full list of > gnucash-bug(dependency) below; I've not gone through the whole list. > > So.... What should I do about this? I can pull in the dependent bug (and > just change the product to gnucash). Or I can manually change it out to > be a NOTGNUCASH with a see-also (and hope that nobody touches it on > gnome-BZ)? Or I can manually remove the dependency (with the same "wont > change" hope)? > > Comments? Suggestions?
I’d go for the second choice: Close out the gnucash bug as “not gnucash” and put the URL of the Gnome bug in see-also. You could guard against the eventual demise of bugzilla.gnome.org <http://bugzilla.gnome.org/> by using a wayback machine URL, e.g. https://web.archive.org/web/20141226164846/https://bugzilla.gnome.org/show_bug.cgi?id=364946 <https://web.archive.org/web/20141226164846/https://bugzilla.gnome.org/show_bug.cgi?id=364946>, though some earlier bugs like 67416 seem not to be archived. Regards, John Ralls _______________________________________________ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
