Bug 18484 - hylafax+-client should conflict with mgetty-sendfax
Summary: hylafax+-client should conflict with mgetty-sendfax
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal major
Target Milestone: ---
Assignee: Thomas Spuhler
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 18413
  Show dependency tree / graph
 
Reported: 2016-05-18 21:33 CEST by Charles Edwards
Modified: 2016-05-20 17:53 CEST (History)
3 users (show)

See Also:
Source RPM: hylafax+-5.5.8-2.mga6
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Charles Edwards 2016-05-18 21:33:55 CEST 
hylafax+-client can be installed independently of hylafax+.

Both hylafax+-client and hylafax+ contain files that Conflict with mgetty-sendfax
but Only hylafax+ carries a Conflicts.

The Conflicts should be moved|added to hylafax+-client

As it stands now when doing a net install both hylafax+-client and mgetty-sendfax
are auto selected.
The conflict then causes the Mga6 install to fail.
Charles Edwards 2016-05-18 21:34:19 CEST

CC: (none) => cae

William Kenney 2016-05-19 00:05:12 CEST

CC: (none) => wilcal.int

Marja Van Waes 2016-05-19 09:49:35 CEST

CC: (none) => marja11
Assignee: bugsquad => thomas

Marja Van Waes 2016-05-19 19:46:29 CEST

Blocks: (none) => 18413

Comment 1 Thomas Spuhler 2016-05-20 17:38:02 CEST 
I am going to add the conflict for the time being. I wonder why these programs are pulled in when doing a net install. These programs should't be automatically installed.
$ urpmq --whatrequires mgetty-sendfax
mgetty-sendfax

mgetty has no maintainer and hasn't had any new releases since 2010. I wonder how many security issues have not been resolved. I thin we should it make obsolete in mga7

Status: NEW => ASSIGNED

Comment 2 Thomas Spuhler 2016-05-20 17:53:27 CEST 
done

Status: ASSIGNED => RESOLVED
Resolution: (none) => FIXED
Note You need to log in before you can comment on or make changes to this bug.