Back to bug 21565

Who When What Removed Added
luigiwalser 2017-08-18 23:59:33 CEST Whiteboard MGA6TOO, MGA5TOO
Blocks 20211
luigiwalser 2017-08-19 00:09:49 CEST See Also https://bugs.mageia.org/show_bug.cgi?id=21525
marja11 2017-08-19 07:42:51 CEST CC marja11
Assignee bugsquad luis.daniel.lucio
mageia 2017-08-19 18:40:05 CEST Assignee luis.daniel.lucio qa-bugs
CC mageia
luigiwalser 2017-08-19 19:24:02 CEST Version Cauldron 6
Whiteboard MGA6TOO, MGA5TOO has_procedure
luigiwalser 2017-08-22 18:45:07 CEST See Also https://bugs.mageia.org/show_bug.cgi?id=21525
Blocks 21525
lewyssmith 2017-08-25 15:32:19 CEST CC lewyssmith
lewyssmith 2017-08-25 15:39:54 CEST Whiteboard has_procedure has_procedure advisory
herman.viaene 2017-08-30 14:24:39 CEST CC herman.viaene
luigiwalser 2017-09-01 03:29:10 CEST Summary cacti new security issue CVE-2017-12927 cacti new security issues CVE-2017-12927 and CVE-2017-12928
Whiteboard has_procedure advisory has_procedure advisory feedback
LpSolit 2017-09-06 16:09:02 CEST Whiteboard has_procedure advisory feedback
Keywords advisory, feedback, has_procedure
luigiwalser 2017-09-07 15:14:16 CEST Summary cacti new security issues CVE-2017-12927 and CVE-2017-12928 cacti new security issues CVE-2017-12927 and CVE-2017-12978
luigiwalser 2017-10-20 17:13:36 CEST Summary cacti new security issues CVE-2017-12927 and CVE-2017-12978 cacti new security issues CVE-2017-12927, CVE-2017-12978, and CVE-2017-15194
Assignee qa-bugs mageia
CC qa-bugs
luigiwalser 2017-11-26 19:12:46 CET Summary cacti new security issues CVE-2017-12927, CVE-2017-12978, and CVE-2017-15194 cacti new security issues CVE-2017-12927, CVE-2017-12978, CVE-2017-15194, CVE-2017-16641, CVE-2017-1666[01], CVE-2017-16785
luigiwalser 2018-02-02 18:17:28 CET Status comment 404 issue in update candidate, should be updated again
luigiwalser 2018-03-27 03:44:44 CEST Whiteboard MGA6TOO
Version 6 Cauldron
luigiwalser 2019-01-02 01:23:32 CET Whiteboard MGA6TOO
Version Cauldron 6
mhrambo3501 2019-11-06 13:15:36 CET Resolution --- OLD
CC mrambo
Status NEW RESOLVED

Back to bug 21565