'Twas brillig, and simple w8 at 19/04/12 17:58 did gyre and gimble: > 2012/4/19 D.Morgan <dmorga...@gmail.com>: >> On Thu, Apr 19, 2012 at 2:37 PM, simple w8 <simpl...@gmail.com> wrote: >>> 2012/4/19 nicolas vigier <bo...@mars-attacks.org>: >>>> On Thu, 19 Apr 2012, D.Morgan wrote: >>>> >>>>> Hi, >>>>> >>>>> please push java-1.7.0-openjdk it fixes various CVE >>>> >>>> Submitted. >>>> >>> >>> If you click in kmenu -> Development->"OpenJDK Policy Tool" nothing >>> happens because the file /usr/bin/policytool does not exist. >> >> thank you for this feedback, i will take a look. > > There are problems also in avaho packages. > For example file /lib/systemd/system/avahi-daemon.service belongs to > package avahi, shouldnt belong to package avahi-daemon?
[colin@jimmy code (master)]$ rpm -qf /lib/systemd/system/avahi-daemon.s* /etc/init.d/avahi-daemon avahi-0.6.30-6.mga2 avahi-0.6.30-6.mga2 avahi-0.6.30-6.mga2 So the systemd unit and the sysvinit script are in the same package. This seems fine to me. [colin@jimmy code (master)]$ rpm -q avahi-daemon package avahi-daemon is not installed I don't have avahi-daemon installed... [colin@jimmy code (master)]$ rpm -qa | grep avahi libavahi-client3-0.6.30-6.mga2 lib64avahi-client3-0.6.30-6.mga2 lib64avahi-common-devel-0.6.30-6.mga2 lib64avahi-compat-libdns_sd-devel-0.6.30-6.mga2 lib64avahi-gobject0-0.6.30-6.mga2 lib64avahi-core7-0.6.30-6.mga2 lib64avahi-ui-devel-0.6.30-6.mga2 lib64avahi-glib1-0.6.30-6.mga2 lib64avahi-compat-libdns_sd1-0.6.30-6.mga2 lib64avahi-ui1-0.6.30-6.mga2 lib64avahi-common3-0.6.30-6.mga2 lib64avahi-glib-devel-0.6.30-6.mga2 avahi-0.6.30-6.mga2 lib64avahi-client-devel-0.6.30-6.mga2 lib64avahi-ui-gtk3_0-0.6.30-6.mga2 libavahi-common3-0.6.30-6.mga2 libavahi-glib1-0.6.30-6.mga2 And no package appears to provide this: [colin@jimmy code (master)]$ rpm -q --whatprovides avahi-daemon no package provides avahi-daemon [colin@jimmy code (master)]$ urpmq -r avahi-daemon No package named avahi-daemon So not sure what you're talking about here. > Also the files: > /usr/bin/avahi-discover-standalone > /usr/share/applications/avahi-discover.desktop > /usr/share/avahi/interfaces/avahi-discover.ui > > belong to package avahi-x11 but where is the exec file > /usr/bin/avahi-discover that the file > /usr/share/applications/avahi-discover.desktop asks to run? Looks like a bug in the .desktop file to me... it should probably run the standalone binary. > Its in package avahi-python... > > ]# urpmq -l avahi-python > /usr/bin/avahi-bookmarks > /usr/bin/avahi-discover > /usr/lib/python2.7/site-packages/avahi/ServiceTypeDatabase.py > /usr/lib/python2.7/site-packages/avahi/__init__.py > /usr/lib/python2.7/site-packages/avahi/__init__.pyc > /usr/lib/python2.7/site-packages/avahi/__init__.pyo > /usr/lib/python2.7/site-packages/avahi_discover > /usr/lib/python2.7/site-packages/avahi_discover/__init__.py > /usr/lib/python2.7/site-packages/avahi_discover/__init__.pyc > /usr/lib/python2.7/site-packages/avahi_discover/__init__.pyo > /usr/share/man/man1/avahi-bookmarks.1.xz > /usr/share/man/man1/avahi-discover.1.xz > > as you see there are several files packaged in wrong packages Yup, This is mostly an example tho' rather than anything practically useful. Still it should be fixed IMO. Please open a bug. -- Colin Guthrie colin(at)mageia.org http://colin.guthr.ie/ Day Job: Tribalogic Limited http://www.tribalogic.net/ Open Source: Mageia Contributor http://www.mageia.org/ PulseAudio Hacker http://www.pulseaudio.org/ Trac Hacker http://trac.edgewall.org/