RPM

Report dependency loops at optional log level

Registered by Jeff Johnson

     Change: loop-detection-optional-loglevel
     Purpose: Report dependency loops at optional log level
     Reason: Mandriva has many dependency loops by intentetion,
                     especially due to it's library package policies.
                     For now we want to be able to not display these as errors,
                     but rather as debug-level messages by default, or at any
                     other log level defined by %_loop_detection_loglevel.

Blueprint information

Status:
Started
Approver:
Jeff Johnson
Priority:
Medium
Drafter:
None
Direction:
Needs approval
Assignee:
None
Definition:
Review
Series goal:
Accepted for 5.4
Implementation:
Needs Code Review
Milestone target:
None
Started by
Jeff Johnson

Related branches

Sprints

Whiteboard

Not sure about other distributions and upstream, but for ROSA/Mandriva this is really useful.

Stating "useful" without supporting arguments isn't helpful in blueprint: its equivalent to +1.

Disabling an error message instead of fixing packaging LOOP's (and pretending that the
problem is too hard so only detection is useful/possible) was the state of this patch several
years ago. There's no need to carry bandaid patches for vendors incapable/unready for
the process to fix/maintain their packaging LOOP's several years later. Nor is disabling
an error message anyplace close to a "fix".

(?)

Work Items

Nearby

This blueprint contains Public information 
Everyone can see this information.
Edit subscription

Subscribers

No subscribers.