| Summary: | 4_a3: saned daemon has /home/saned directory in /etc/passwd | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Bit Twister <bittwister2> |
| Component: | RPM Packages | Assignee: | Remco Rijnders <remco> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | bittwister2, dmorganec, eeeemail, fundawang, luis.daniel.lucio, marja11 |
| Version: | Cauldron | Keywords: | Junior_job |
| Target Milestone: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | MGA2TOO | ||
| Source RPM: | sane-1.0.24-3.mga4.src.rpm | CVE: | |
| Status comment: | |||
|
Description
Bit Twister
2011-12-02 02:00:38 CET
Hi, thanks for reporting this bug. As there is no maintainer for this package I added the committers in CC. Keywords:
(none) =>
Junior_job assigning to maintainer CC:
(none) =>
marja11 Trying to ping 41 bug reports in one move, because nothing has happened with them for more than 3 months, they still have the status NEW or REOPENED, there is no "OK" on the Whiteboard and severity and priority are "normal" or higher. Is this one still valid for Mageia 2 rc? If it is and you're the assignee, 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. If it wasn't assigned correctly, please assign back to Bug Squad and explain. (In reply to comment #3) > Is this one still valid for Mageia 2 rc? yes Hi, This bug was filed against cauldron, but we do not have cauldron at the moment. Please report whether this bug is still valid for Mageia 2. Thanks :) Cheers, marja Keywords:
(none) =>
NEEDINFO (In reply to comment #6) > Please report whether this bug is still valid for Mageia 2. still valid. Keywords:
NEEDINFO =>
(none)
Marja Van Waes
2012-05-28 18:29:52 CEST
Whiteboard:
(none) =>
MGA2TOO 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
D Morgan
2013-09-17 23:54:51 CEST
Assignee:
dmorganec =>
bugsquad
Manuel Hiebel
2013-09-18 11:37:27 CEST
Version:
Cauldron =>
2 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
Bit Twister
2013-10-23 14:05:06 CEST
Version:
2 =>
Cauldron clean install + updates Mageia-4-x86_64-DVD.iso
urpmi saned
installing saned-1.0.24-3.mga4.x86_64.rpm xinetd-2.3.15-5.mga4.x86_64.rpm from /var/cache/urpmi/rpms
Preparing... #################################
1/2: xinetd #####
2/2: saned ##########################
Failed to issue method call: No such file or directory
saned daemon still has /home/saned directory in /etc/passwd
Hi Bit Twister, Thank you for your report and your patience. I've made a change to this package in Cauldron, which hopefully addresses this issue. If you have a Cauldron system, please do feel free to test. I'm unsure if this issue is serious enough to fix in Mageia 3 and 4, my feeling says it is not. If you agree, and if the Cauldron package works (which should find its way into Mageia 5), are you ok with us closing this bug report? Assignee:
bugsquad =>
remco (In reply to Remco Rijnders from comment #11) > I'm unsure if this issue is serious enough to fix in Mageia 3 and 4, my > feeling says it is not. I can agree with that. There is an easy workaround if anyone wants to fix it on their system. > If you agree, and if the Cauldron package works > (which should find its way into Mageia 5), are you ok with us closing this > bug report? Tested and urpmi sane and it's home showed up as /etc/sane.d in /etc/passwd. Glad to hear! Thank you again for the report and testing. Status:
NEW =>
RESOLVED |