Bug 3277

Summary:	scheduler.py: inconsistent use of tabs and spaces in indentation
Product:	Mageia	Reporter:	Xuo <xuoy>
Component:	RPM Packages	Assignee:	Anne Nicolas <ennael1>
Status:	RESOLVED WONTFIX	QA Contact:
Severity:	minor
Priority:	Normal	CC:	juergen.harms, marja11, r.h.michel+mageia
Version:	1	Keywords:	Triaged
Target Milestone:	---
Hardware:	i586
OS:	Linux
Whiteboard:
Source RPM:	sectool	CVE:
Status comment:

Description Xuo 2011-11-06 15:21:55 CET

Hi,

The cron.weekly script returns :
/usr/share/sectool/scheduler/scheduler.py: inconsistent use of tabs and spaces in indentation

As the script is quite long ans as I don't know too much python, I couldn't find the uncorrect line.

Regards.

Xuo.

Comment 1 Renaud Michel 2011-11-06 19:32:04 CET

I have seen the bug too.
Grep tells me that a single line has tabs instead of spaces, line 780 (as of version 0.9.3-1.1.mga1).
That is the line with
self.environ.update( LANG = os.getenv("LANG", "en_US.utf8"),

CC: (none) => r.h.michel+mageia

Comment 2 Manuel Hiebel 2011-11-07 01:02:54 CET

Hi, thanks for reporting this bug.
Assigned to the package maintainer.

Keywords: (none) => Triaged
Assignee: bugsquad => ennael1

Comment 3 Manuel Hiebel 2011-11-29 23:19:01 CET

*** Bug 3530 has been marked as a duplicate of this bug. ***

CC: (none) => juergen.harms

Comment 4 Juergen Harms 2011-11-30 09:14:33 CET

Here is another item in the error messages from cron (cron.daily)
/etc/cron.daily/tmpwatch:
error: bad time argument /tmp/.XIM-unix

Comment 5 Marja Van Waes 2012-03-14 21:54:44 CET

Pinging, because nothing has happened with this report for more than 3 months, it still has the status NEW or REOPENED.


@ ennael

Please set status to ASSIGNED if you think this bug was assigned correctly. If for work flow reasons you can't do that, then please put OK on the whiteboard instead.

CC: (none) => marja11

Comment 6 Manuel Hiebel 2012-11-05 16:51:13 CET

This message is a reminder that Mageia 1 is nearing its end of life. 
In approximately 25 days from now, Mageia will stop maintaining and issuing 
updates for Mageia 1. At that time this bug will be closed as WONTFIX (EOL) if it 
remains open with a Mageia 'version' of '1'.

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 1'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 1 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.

--
Mageia Bugsquad

Comment 7 Manuel Hiebel 2012-12-02 14:31:17 CET

Mageia 1 changed to end-of-life (EOL) status on ''1st December''. Mageia 1 is no 
longer maintained, which means that it will not receive any further security or 
bug fix updates. As a result we are closing this bug. 

If you can reproduce this bug against a currently maintained version of Mageia 
please feel free to click on "Version" change it against that version of Mageia and reopen this bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

--
Mageia Bugsquad

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