You are not logged in.
I was trying to install the notify-osd-customizable package from aur, but I'm running in a conflict because both packages "provides" notification-daemon.
I don't know how to deal when two packages provides the same package. I've read the pacman man and wiki, but I haven't being able to solve the problem =/
Any help/feedback is welcome :)
Geeks & Linux Atelier
An eye for an eye ... ends in making everybody blind -- Mahatma Gandhi
dotfiles
Offline
In this case you could recompile awesome from ABS and remove the provides='notification-daemon' from the pkgbuild. Since awesome provides a notification module which is optional, it doesn't need the provides line. EDIT: OOPS it seems awesome isn't in abs yet.
Last edited by MOPSTER (2012-05-13 03:31:35)
Offline
same problem here! +1
Offline
If you don't want to wait for ABS to be updated, you can just download the files and PKGBUILD:
Offline
Since awesome provides a notification module which is optional, it doesn't need the provides line.
Actually, it kinda does - consider why both awesome and notify-osd-* provide the metapackage notification-daemon; if it didn't provide that, you'd have to edit the PKGBUILD to provide it if you just wanted to use awesome's built-in module.
It's kinda damned-if-you-do, damned-if-you-don't, unless the maintainer breaks the upstream package and provides naughty as a separate package - maybe something to bug report?
{edit}I feature-requested it - https://bugs.archlinux.org/task/29874{/edit}
Last edited by ZekeSulastin (2012-05-13 16:13:55)
Offline
I used to edit the PKGBUILD for the provides line when it was in the aur since back then it didn't provide a notification-daemon eventhough I could use naughty. I do agree with the separate package thing though, choice is always nice.
Offline
If you don't want to wait for ABS to be updated, you can just download the files and PKGBUILD:
Thanks to point it out. If you use yaourt,
yaourt -G awesomedo the work (pretty handy, even if you don't use it on an everyday basis).
MOPSTER wrote:Since awesome provides a notification module which is optional, it doesn't need the provides line.
Actually, it kinda does - consider why both awesome and notify-osd-* provide the metapackage notification-daemon; if it didn't provide that, you'd have to edit the PKGBUILD to provide it if you just wanted to use awesome's built-in module.
It's kinda damned-if-you-do, damned-if-you-don't, unless the maintainer breaks the upstream package and provides naughty as a separate package - maybe something to bug report?
{edit}I feature-requested it - https://bugs.archlinux.org/task/29874{/edit}
Thanks, I'm following the 'bug' now, and I -obviously- voted ![]()
Geeks & Linux Atelier
An eye for an eye ... ends in making everybody blind -- Mahatma Gandhi
dotfiles
Offline
I was trying to install the notify-osd-customizable package from aur, but I'm running in a conflict because both packages "provides" notification-daemon.
It conflict because notify-osd-customizable conflict with notification-daemon (provide doesn't conflict).
Remove the conflict inside aur package and this will work correctly. You can test with the real notification-daemon which doesn't conflict or xfce4-notifyd.
Offline
Yep, you're right. I removed the "conflicts" and now it worked fine. I still don't understand why the official package needs that though...
Geeks & Linux Atelier
An eye for an eye ... ends in making everybody blind -- Mahatma Gandhi
dotfiles
Offline