From 1be510f9529cb082f802408b472a77d074b394c0 Mon Sep 17 00:00:00 2001 From: Nicolas Vigier Date: Sun, 14 Apr 2013 13:46:12 +0000 Subject: Add zarb MLs html archives --- zarb-ml/mageia-dev/2011-August/007646.html | 91 ++++++++++++++++++++++++++++++ 1 file changed, 91 insertions(+) create mode 100644 zarb-ml/mageia-dev/2011-August/007646.html (limited to 'zarb-ml/mageia-dev/2011-August/007646.html') diff --git a/zarb-ml/mageia-dev/2011-August/007646.html b/zarb-ml/mageia-dev/2011-August/007646.html new file mode 100644 index 000000000..f274b2b8f --- /dev/null +++ b/zarb-ml/mageia-dev/2011-August/007646.html @@ -0,0 +1,91 @@ + + + + [Mageia-dev] clamav is in updates_testing but QA team got no update request + + + + + + + + + +

[Mageia-dev] clamav is in updates_testing but QA team got no update request

+ Buchan Milne + bgmilne at staff.telkomsa.net +
+ Mon Aug 29 12:28:48 CEST 2011 +

+
+ +
On Sunday, 28 August 2011 01:38:51 Luis Daniel Lucio Quiroz wrote:
+> Le Dimanche 28 Août 2011 00:19:12 Samuel Verschelde a écrit :
+> > There seems to be an update candidate for clamav, it's been in
+> > updates_testing for one month or more, but I can't find any bug report in
+> > bugzilla assigned to QA team (qa-bugs at ml.mageia.org) which means it will
+> > never reach updates.
+> > 
+> > There are probably other packages in updates_testing for Mageia 1 without
+> > any bug report passed to QA. Ultimately I would like to have a
+> > correspondance table to be able to find them. This would probably mean to
+> > develop a tool for that and slightly adapt the updates procedure, but we
+> > would also benefit from the rigorous match between packages in
+> > updates_testing and update bug reports, so less forgotten packages when
+> > pushing to updates.
+> > 
+> > Best regards
+> > 
+> > Samuel Verschelde
+> 
+> I did push that clamav,
+> but since i couldnt enter into buziglla i couldnt do ticket.  Yes i did try
+> asking sysadmins to reset my password, but it seems my account has
+> problems.
+
+Password resets done by admins for privileged users was broken if the admin 
+used https://identity.mageia.org to do the reset, but was fixed in trunk 
+(available at https://identity-trunk.mageia.org). I have merged this fix into 
+live, so it now works at https://identity.mageia.org .
+
+Regards,
+Buchan
+
+ + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ -- cgit v1.2.1