apt-zeroconf

ImportError: No module named aptzeroconf.daemon

Bug #398560 reported by Amr Hassan
44
This bug affects 6 people
Affects Status Importance Assigned to Milestone
apt-zeroconf
In Progress
Critical
Jeremy Austin-Bardo
apt-zeroconf 0.5.2

Bug Description

This happens after installing apt-zeroconf from ppa, I was able to reproduce it with dpkg-reconfigure apt-zeroconf

amr@gort:~$ sudo dpkg-reconfigure apt-zeroconf
 * Stopping apt-zeroconf APT proxy
pidfile /var/run/apt-zeroconf.pid does not exist. Daemon not running?
                                                                         [ OK ]
 * Starting apt-zeroconf APT proxy
Traceback (most recent call last):
  File "/usr/bin/apt-zeroconf", line 44, in <module>
    from aptzeroconf.daemon import Daemon
ImportError: No module named aptzeroconf.daemon
                                                                         [ OK ]

Package: 0.5.1 on ubuntu jaunty

Revision history for this message
Jeremy Austin-Bardo (ausimage) wrote :

Looks like there was some package issues with this one :/ I believe have solved the issue and the change will be in 0.5.2 when released.

Changed in apt-zeroconf:
assignee: nobody → Jeremy Austin-Bardo (ausimage)
importance: Undecided → Critical
milestone: none → 0.5.2
status: New → Fix Committed
Revision history for this message
Jeremy Austin-Bardo (ausimage) wrote :

K... Further investigation shows that the problem lies in debian packaging side of things. For whatever reason, when apt-zeroconf is run by debian package management its seems to not find the module in question. I will see if I can find a package expert to assist with tracking the source of the issue.

Changed in apt-zeroconf:
status: Fix Committed → In Progress
Revision history for this message
Josh Holland (jshholland) wrote :

Could it be something to do with the relocation of /usr/lib/python/site-packages to /usr/lib/python/dist-packages?

Revision history for this message
Alan Pope 🍺🐧🐱 🦄 (popey) wrote :

Any update on this? apt-zeroconf is broken in karmic.

Revision history for this message
andrew1056 (andrew-oke) wrote :

I can confirm it's broken on karmic with the same error as well.

Revision history for this message
Hugo Alvarado (hugo102) wrote :

I always use apt-zeroconf, and it works well. I just installed in Karmic it from my apt-zeroconf_0.4.1_all.deb.

At first it did not work but it turns out something changed in pyinotify, but it can be “fixed” by editing the apt.py file, look for the pyinotify.EventsCodes.IN_MOVED_TO
around line 53 and change it to
pyinotify.IN_MOVED_TO

Do this for the other 3 lines, and restart apt-zeroconf. As always, make your checks

Revision history for this message
Claudiux (claudiux) wrote :

To fix it, it's easy :
cd /etc
sudo ln -s azc/apt-zeroconf.conf
sudo /etc/init.d/apt-zeroconf restart

Revision history for this message
Christian Schürer-Waldheim (quincunx) wrote :

So the path in config.py should be patched.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.