Bug 707783 - Broken dependency on deprecated hal
Broken dependency on deprecated hal
Status: CLOSED RAWHIDE
Product: Fedora
Classification: Fedora
Component: xfce4-cddrive-plugin (Show other bugs)
rawhide
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Christoph Wickert
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2011-05-25 18:39 EDT by Christoph Wickert
Modified: 2011-05-25 18:41 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 698656
Environment:
Last Closed: 2011-05-25 18:41:58 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Christoph Wickert 2011-05-25 18:39:59 EDT
+++ This bug was initially created as a clone of Bug #698656 +++

Description of problem:
Since HAL has been deprecated upstream for 3 years, Fedora is removing it from the
distribution:

https://fedoraproject.org/wiki/Features/HalRemoval

The hal package is already deprecated and blocked from composes for rawhide.

Therefore, there are some broken dependencies for your package now:

xfce4-cddrive-plugin-0.0.1-4.fc15.x86_64 requires libhal.so.1
xfce4-cddrive-plugin-0.0.1-4.fc15.x86_64 requires libhal-storage.so.1
xfce4-cddrive-plugin-0.0.1-4.fc15.x86_64 requires hal

If these dependencies cannot be removed, this package should probably be
deprecated as well:

https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life

Version-Release number of selected component (if applicable):
xfce4-cddrive-plugin-0.0.1-4.fc15
Comment 1 Christoph Wickert 2011-05-25 18:41:58 EDT
I have no intentions to fix this because the plugin is dead upstream. I have retired it in package-db and marked it dead.package in git.

I filed a rel-eng ticket to block this from rawhide at
https://fedorahosted.org/rel-eng/ticket/4753

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