Bug 3182 - Msec Monthly/Manual Checks complete instantly and don't update when they were last run.
Summary: Msec Monthly/Manual Checks complete instantly and don't update when they were...
Status: RESOLVED INVALID
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 2
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL: https://bugs.mageia.org/show_bug.cgi?...
Whiteboard: MGA1TOO
Keywords:
Depends on:
Blocks:
 
Reported: 2011-10-25 15:02 CEST by claire robinson
Modified: 2013-10-24 09:13 CEST (History)
2 users (show)

See Also:
Source RPM: msec-0.80.10-2.3.mga1.src.rpm
CVE:
Status comment:


Attachments

Description claire robinson 2011-10-25 15:02:56 CEST
Description of problem:

This bug has been created to allow an update candidate for msec/msec-gui to be validated. Please see also bug 2255.

Both monthly and manual checks complete instantly and neither update when they were last run. I don't think they are actually doing anything.

This is the same in release version and also the update candidate.


Version-Release number of selected component (if applicable):


Currently msec-0.80.10-2.3.mga1.src.rpm
Florian Hubold 2011-10-25 18:05:28 CEST

CC: (none) => doktor5000

Manuel Hiebel 2011-10-30 02:05:54 CET

Assignee: bugsquad => dmorganec

Comment 1 Marja Van Waes 2012-02-01 07:54:37 CET
Pinging, because nothing has happened with this report for more than 3 months, it still has the status NEW or REOPENED.

etc.

CC: (none) => marja11

Comment 2 Marja Van Waes 2012-07-06 15:05:45 CEST
Please look at the bottom of this mail to see whether you're the assignee of this  bug, if you don't already know whether you are.


If you're the assignee:

We'd like to know for sure whether this bug was assigned correctly. Please change status to ASSIGNED if it is, or put OK on the whiteboard instead.

If you don't have a clue and don't see a way to find out, then please put NEEDHELP on the whiteboard.

Please assign back to Bug Squad or to the correct person to solve this bug if we were wrong to assign it to you, and explain why.

Thanks :)

**************************** 

@ the reporter and persons in the cc of this bug:

If you have any new information that wasn't given before (like this bug being valid for another version of Mageia, too, or it being solved) please tell us.

@ the reporter of this bug

If you didn't reply yet to a request for more information, please do so within two weeks from now.

Thanks all :-D
Comment 3 claire robinson 2012-07-06 18:44:19 CEST
Valid in mga2 so adding MGA1TOO

Version: 1 => 2
Whiteboard: (none) => MGA1TOO

Comment 4 James Kerr 2013-04-15 16:15:04 CEST
I don't think that this is a bug (or it has been fixed).

By default there are no checks set to be run manually or monthly. If you set a check to manual or monthly (in msec-gui Periodic Checks page), then the check can be run from the msec-gui Overview page and the last run date is updated (when you re-open msec-gui).
Comment 5 James Kerr 2013-04-15 16:28:19 CEST
Sorry, I should have added - I've tested this in Mageia 2 and in cauldron.
D Morgan 2013-09-18 00:00:29 CEST

Assignee: dmorganec => bugsquad

Comment 6 Manuel Hiebel 2013-10-22 12:19:08 CEST
This message is a reminder that Mageia 2 is nearing its end of life.
Approximately one month from now Mageia will stop maintaining and issuing updates for Mageia 2. At that time this bug will be closed as WONTFIX (EOL) if it remains open with a Mageia 'version' of '2'.

Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version prior to Mageia 2's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Mageia 2 is end of life.  If you would still like to see this bug fixed and are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia.

Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete.

-- 
The Mageia Bugsquad
Comment 7 claire robinson 2013-10-24 09:13:43 CEST
Confirming what James found in comment 4. Nothing is set to run monthly. Once something is then it works as expected. Closing as invalid.

Status: NEW => RESOLVED
Resolution: (none) => INVALID


Note You need to log in before you can comment on or make changes to this bug.