[opensuse] Reopen bug or create a new
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, My question is, what is the desirable method, when I have a clue that a bug fix created another bug. So the fix eventually fixed the issue, but created another one. I reported bnc#398315, what was about repos' changes were saved when I hit abort in the installer. Now it wouldn't be saved even I hit OK and proceed. Should I add another comment to the resolved fixed bug report, or create a new one? TIA. Tamas -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iEYEARECAAYFAkmdxSwACgkQsuVyj8v2Zy4FDQCfbpeaTWfec9JnqXSBBJsgCDaC wK4An2GuOus81esyMMXPi8DXkL3B4MIT =MRPt -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thu, Feb 19, 2009 at 3:46 PM, Tamas Sarga <tamas.sarga2@gmail.com> wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi,
My question is, what is the desirable method, when I have a clue that a bug fix created another bug. So the fix eventually fixed the issue, but created another one. I reported bnc#398315, what was about repos' changes were saved when I hit abort in the installer. Now it wouldn't be saved even I hit OK and proceed. Should I add another comment to the resolved fixed bug report, or create a new one?
I would re-open it in this case. Being on the receiving end of these reports, it helps to know that the recent work is the first place to look for the source of the bug. Greg -- Greg Freemyer Litigation Triage Solutions Specialist http://www.linkedin.com/in/gregfreemyer First 99 Days Litigation White Paper - http://www.norcrossgroup.com/forms/whitepapers/99%20Days%20whitepaper.pdf The Norcross Group The Intersection of Evidence & Technology http://www.norcrossgroup.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Greg Freemyer wrote:
On Thu, Feb 19, 2009 at 3:46 PM, Tamas Sarga <tamas.sarga2@gmail.com> wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi,
My question is, what is the desirable method, when I have a clue that a bug fix created another bug. So the fix eventually fixed the issue, but created another one. I reported bnc#398315, what was about repos' changes were saved when I hit abort in the installer. Now it wouldn't be saved even I hit OK and proceed. Should I add another comment to the resolved fixed bug report, or create a new one?
I would re-open it in this case. Being on the receiving end of these reports, it helps to know that the recent work is the first place to look for the source of the bug.
Greg
Thanks for the quick answer. I added a comment, I don't have reopen permission. Cheers, Tamas -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iEYEARECAAYFAkmd1GIACgkQsuVyj8v2Zy7SvwCgorAGavD3+a4FnKVS/M6bBfGl FDsAoKR6G3fQ9HlFDc13iNAY06bQn9gX =9ZzR -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (2)
-
Greg Freemyer -
Tamas Sarga