[opensuse-factory] Where can I find the package nss-mdns?
I will update avahi and libgphoto2 to verify if the bug 239719 was resolved (as it appear in bugzilla), and then I update avahi and the dependents packages, but I could'nt find the package nss-mdns required by avahi-0.6.17-3.i586, because I got: # rpm -Uvh avahi-0.6.17-3.i586.rpm error: Failed dependencies: nss-mdns is needed by avahi-0.6.17-3.i586 Where can I find the package nss-mdns? Thanks --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Hi,
Where can I find the package nss-mdns?
You cannot find it anywhere, this is a new package that is still missing from the factory tree. Since quite some time actually, at least since 20070221. That's when avahi started to require it: http://lists.opensuse.org/opensuse-commit/2007-02/msg00716.html Furthermore, the avahi.spec file says: # Not really required, but many tools expect nss-mdns installed: Requires: nss-mdns I wonder why a package should be allowed to require a package that is not really required... Anyway, you don't need to update avahi in order to verify whether the digikam crash is fixed because avahi has not even been touched in order to fix this. The problem has been fixed by removing mDNS support from libgphoto2. Andreas Hanke -- Der GMX SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen! Ideal für Modem und ISDN: http://www.gmx.net/de/go/smartsurfer --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
2007/3/4, andreas.hanke@gmx-topmail.de <andreas.hanke@gmx-topmail.de>:
Hi,
Where can I find the package nss-mdns?
You cannot find it anywhere, this is a new package that is still missing from the factory tree. Since quite some time actually, at least since 20070221. That's when avahi started to require it:
http://lists.opensuse.org/opensuse-commit/2007-02/msg00716.html
Furthermore, the avahi.spec file says:
# Not really required, but many tools expect nss-mdns installed: Requires: nss-mdns
I wonder why a package should be allowed to require a package that is not really required...
Anyway, you don't need to update avahi in order to verify whether the digikam crash is fixed because avahi has not even been touched in order to fix this. The problem has been fixed by removing mDNS support from libgphoto2.
I have updated libgphoto2, but it do'nt works with my cam (Canon Powershot G2). As I see, I mean that I must go back to OSS 10.2 with mDNSResponder (without avahi) for download the pictures from my cam. Thanks --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Sun, Mar 04, 2007 at 11:25:18AM -0300, Juan Erbes wrote:
2007/3/4, andreas.hanke@gmx-topmail.de <andreas.hanke@gmx-topmail.de>:
Hi,
Where can I find the package nss-mdns?
You cannot find it anywhere, this is a new package that is still missing from the factory tree. Since quite some time actually, at least since 20070221. That's when avahi started to require it:
http://lists.opensuse.org/opensuse-commit/2007-02/msg00716.html
Furthermore, the avahi.spec file says:
# Not really required, but many tools expect nss-mdns installed: Requires: nss-mdns
I wonder why a package should be allowed to require a package that is not really required...
Anyway, you don't need to update avahi in order to verify whether the digikam crash is fixed because avahi has not even been touched in order to fix this. The problem has been fixed by removing mDNS support from libgphoto2.
I have updated libgphoto2, but it do'nt works with my cam (Canon Powershot G2).
As I see, I mean that I must go back to OSS 10.2 with mDNSResponder (without avahi) for download the pictures from my cam.
This is probably the permission bug, that showed up again, since HAL/udev again emits their events in yet another order. Ciao, Marcus --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
2007/3/4, Marcus Meissner <meissner@suse.de>:
On Sun, Mar 04, 2007 at 11:25:18AM -0300, Juan Erbes wrote:
2007/3/4, andreas.hanke@gmx-topmail.de <andreas.hanke@gmx-topmail.de>:
Hi,
Where can I find the package nss-mdns?
You cannot find it anywhere, this is a new package that is still missing from the factory tree. Since quite some time actually, at least since 20070221. That's when avahi started to require it:
http://lists.opensuse.org/opensuse-commit/2007-02/msg00716.html
Furthermore, the avahi.spec file says:
# Not really required, but many tools expect nss-mdns installed: Requires: nss-mdns
I wonder why a package should be allowed to require a package that is not really required...
Anyway, you don't need to update avahi in order to verify whether the digikam crash is fixed because avahi has not even been touched in order to fix this. The problem has been fixed by removing mDNS support from libgphoto2.
I have updated libgphoto2, but it do'nt works with my cam (Canon Powershot G2).
As I see, I mean that I must go back to OSS 10.2 with mDNSResponder (without avahi) for download the pictures from my cam.
This is probably the permission bug, that showed up again, since HAL/udev again emits their events in yet another order.
I will try to change the permisions by hand, but when type the command, I got: chmod 666 /dev/bus/usb/005/003 chmod: no se puede acceder a «/dev/bus/usb/005/003»: No existe el fichero o el directorio I have launched udevmonitor in other konsole, and I see that the device was removed: (see bottom): UEVENT[1173019526.280169] add@/devices/pci0000:00/0000:00:10.3/usb5/5-2 ACTION=add DEVPATH=/devices/pci0000:00/0000:00:10.3/usb5/5-2 SUBSYSTEM=usb SEQNUM=1700 PRODUCT=4a9/3055/1 TYPE=255/255/255 UEVENT[1173019526.280304] add@/devices/pci0000:00/0000:00:10.3/usb5/5-2/usbdev5.3_ep00 ACTION=add DEVPATH=/devices/pci0000:00/0000:00:10.3/usb5/5-2/usbdev5.3_ep00 SUBSYSTEM=usb_endpoint SEQNUM=1701 MAJOR=254 MINOR=10 UEVENT[1173019526.284239] add@/devices/pci0000:00/0000:00:10.3/usb5/5-2/5-2:1.0 ACTION=add DEVPATH=/devices/pci0000:00/0000:00:10.3/usb5/5-2/5-2:1.0 SUBSYSTEM=usb SEQNUM=1702 PRODUCT=4a9/3055/1 TYPE=255/255/255 INTERFACE=255/255/255 MODALIAS=usb:v04A9p3055d0001dcFFdscFFdpFFicFFiscFFipFF UEVENT[1173019526.284345] add@/devices/pci0000:00/0000:00:10.3/usb5/5-2/5-2:1.0/usbdev5.3_ep81 ACTION=add DEVPATH=/devices/pci0000:00/0000:00:10.3/usb5/5-2/5-2:1.0/usbdev5.3_ep81 SUBSYSTEM=usb_endpoint SEQNUM=1703 MAJOR=254 MINOR=11 UEVENT[1173019526.284401] add@/devices/pci0000:00/0000:00:10.3/usb5/5-2/5-2:1.0/usbdev5.3_ep02 ACTION=add DEVPATH=/devices/pci0000:00/0000:00:10.3/usb5/5-2/5-2:1.0/usbdev5.3_ep02 SUBSYSTEM=usb_endpoint SEQNUM=1704 MAJOR=254 MINOR=12 UEVENT[1173019526.284457] add@/devices/pci0000:00/0000:00:10.3/usb5/5-2/5-2:1.0/usbdev5.3_ep83 ACTION=add DEVPATH=/devices/pci0000:00/0000:00:10.3/usb5/5-2/5-2:1.0/usbdev5.3_ep83 SUBSYSTEM=usb_endpoint SEQNUM=1705 MAJOR=254 MINOR=13 UEVENT[1173019526.284512] add@/class/usb_device/usbdev5.3 ACTION=add DEVPATH=/class/usb_device/usbdev5.3 SUBSYSTEM=usb_device SEQNUM=1706 MAJOR=189 MINOR=514 UDEV [1173019526.381378] add@/class/usb_device/usbdev5.3 UDEV_LOG=3 ACTION=add DEVPATH=/class/usb_device/usbdev5.3 SUBSYSTEM=usb_device SEQNUM=1706 MAJOR=189 MINOR=514 UDEVD_EVENT=1 DEVNAME=/dev/bus/usb/005/003 UDEV [1173019527.220683] add@/devices/pci0000:00/0000:00:10.3/usb5/5-2 UDEV_LOG=3 ACTION=add DEVPATH=/devices/pci0000:00/0000:00:10.3/usb5/5-2 SUBSYSTEM=usb SEQNUM=1700 PRODUCT=4a9/3055/1 TYPE=255/255/255 UDEVD_EVENT=1 UDEV [1173019527.224615] add@/devices/pci0000:00/0000:00:10.3/usb5/5-2/usbdev5.3_ep00 UDEV_LOG=3 ACTION=add DEVPATH=/devices/pci0000:00/0000:00:10.3/usb5/5-2/usbdev5.3_ep00 SUBSYSTEM=usb_endpoint SEQNUM=1701 MAJOR=254 MINOR=10 UDEV [1173019527.663041] add@/devices/pci0000:00/0000:00:10.3/usb5/5-2/5-2:1.0 UDEV_LOG=3 ACTION=add DEVPATH=/devices/pci0000:00/0000:00:10.3/usb5/5-2/5-2:1.0 SUBSYSTEM=usb SEQNUM=1702 PRODUCT=4a9/3055/1 TYPE=255/255/255 INTERFACE=255/255/255 MODALIAS=usb:v04A9p3055d0001dcFFdscFFdpFFicFFiscFFipFF UDEVD_EVENT=1 UDEV [1173019527.666913] add@/devices/pci0000:00/0000:00:10.3/usb5/5-2/5-2:1.0/usbdev5.3_ep81 UDEV_LOG=3 ACTION=add DEVPATH=/devices/pci0000:00/0000:00:10.3/usb5/5-2/5-2:1.0/usbdev5.3_ep81 SUBSYSTEM=usb_endpoint SEQNUM=1703 MAJOR=254 MINOR=11 UDEVD_EVENT=1 DEVNAME=/dev/usbdev5.3_ep81 UDEV [1173019527.670562] add@/devices/pci0000:00/0000:00:10.3/usb5/5-2/5-2:1.0/usbdev5.3_ep02 UDEV_LOG=3 ACTION=add DEVPATH=/devices/pci0000:00/0000:00:10.3/usb5/5-2/5-2:1.0/usbdev5.3_ep02 SUBSYSTEM=usb_endpoint SEQNUM=1704 MAJOR=254 MINOR=12 UDEVD_EVENT=1 DEVNAME=/dev/usbdev5.3_ep02 UDEV [1173019527.675574] add@/devices/pci0000:00/0000:00:10.3/usb5/5-2/5-2:1.0/usbdev5.3_ep83 UDEV_LOG=3 ACTION=add DEVPATH=/devices/pci0000:00/0000:00:10.3/usb5/5-2/5-2:1.0/usbdev5.3_ep83 SUBSYSTEM=usb_endpoint SEQNUM=1705 MAJOR=254 MINOR=13 UDEVD_EVENT=1 DEVNAME=/dev/usbdev5.3_ep83 UEVENT[1173019675.321478] remove@/devices/pci0000:00/0000:00:10.3/usb5/5-2/5-2:1.0/usbdev5.3_ep81 ACTION=remove DEVPATH=/devices/pci0000:00/0000:00:10.3/usb5/5-2/5-2:1.0/usbdev5.3_ep81 SUBSYSTEM=usb_endpoint SEQNUM=1707 MAJOR=254 MINOR=11 UEVENT[1173019675.321580] remove@/devices/pci0000:00/0000:00:10.3/usb5/5-2/5-2:1.0/usbdev5.3_ep02 ACTION=remove DEVPATH=/devices/pci0000:00/0000:00:10.3/usb5/5-2/5-2:1.0/usbdev5.3_ep02 SUBSYSTEM=usb_endpoint SEQNUM=1708 MAJOR=254 MINOR=12 UEVENT[1173019675.321638] remove@/devices/pci0000:00/0000:00:10.3/usb5/5-2/5-2:1.0/usbdev5.3_ep83 ACTION=remove DEVPATH=/devices/pci0000:00/0000:00:10.3/usb5/5-2/5-2:1.0/usbdev5.3_ep83 SUBSYSTEM=usb_endpoint SEQNUM=1709 MAJOR=254 MINOR=13 UEVENT[1173019675.321695] remove@/devices/pci0000:00/0000:00:10.3/usb5/5-2/5-2:1.0 ACTION=remove DEVPATH=/devices/pci0000:00/0000:00:10.3/usb5/5-2/5-2:1.0 SUBSYSTEM=usb SEQNUM=1710 PRODUCT=4a9/3055/1 TYPE=255/255/255 INTERFACE=255/255/255 MODALIAS=usb:v04A9p3055d0001dcFFdscFFdpFFicFFiscFFipFF UEVENT[1173019675.321770] remove@/class/usb_device/usbdev5.3 ACTION=remove DEVPATH=/class/usb_device/usbdev5.3 SUBSYSTEM=usb_device SEQNUM=1711 MAJOR=189 MINOR=514 --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
andreas.hanke@gmx-topmail.de píše v Ne 04. 03. 2007 v 12:36 +0100:
Hi,
Where can I find the package nss-mdns?
You cannot find it anywhere, this is a new package that is still missing from the factory tree. Since quite some time actually, at least since 20070221. That's when avahi started to require it:
You can get one from GNOME:UNSTABLE Build Service, if you cannot find it elsewhere-
http://lists.opensuse.org/opensuse-commit/2007-02/msg00716.html
Furthermore, the avahi.spec file says:
# Not really required, but many tools expect nss-mdns installed: Requires: nss-mdns
I wonder why a package should be allowed to require a package that is not really required...
avahi-daemon and avahi-dnsconfd don't require it. But for example avahi-bookmarks (from the same package) expects, that .local domain is resolved (otherwise you will end with unresolvable domains). Other programs also silently expect nss-mdns present (e. g. banshee). And package mDNSResponder had it in the main package. -- Best Regards / S pozdravem, Stanislav Brabec software developer --------------------------------------------------------------------- SUSE LINUX, s. r. o. e-mail: sbrabec@suse.cz Lihovarská 1060/12 tel: +420 284 028 966 190 00 Praha 9 fax: +420 284 028 951 Czech Republic http://www.suse.cz/ --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Hi,
avahi-daemon and avahi-dnsconfd don't require it.
But for example avahi-bookmarks (from the same package) expects, that .local domain is resolved (otherwise you will end with unresolvable domains).
In this case it is a circular dependency. Not actually in the rpm "Requires" sense (because nss-mdns does not have "Requires: avahi"), but http://0pointer.de/lennart/projects/nss-mdns/ says: "nss-mdns will not work unless Avahi is running! That makes Avahi essentially a hard dependency of nss-mdns." If the packages really need each other, it might be a better idea to ship them in the same source tarball (but that would have to be handled upstream). Andreas Hanke -- Der GMX SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen! Ideal für Modem und ISDN: http://www.gmx.net/de/go/smartsurfer --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Mon, Mar 05, 2007 at 02:12:43PM +0100, andreas.hanke@gmx-topmail.de wrote:
If the packages really need each other, it might be a better idea to ship them in the same source tarball (but that would have to be handled upstream).
Not really. This does not mean that they need a specific version of each other. Robert -- Robert Schiele Dipl.-Wirtsch.informatiker mailto:rschiele@gmail.com "Quidquid latine dictum sit, altum sonatur."
participants (5)
-
andreas.hanke＠gmx-topmail.de -
Juan Erbes -
Marcus Meissner -
Robert Schiele -
Stanislav Brabec