Can't install libudev-dev in classic

device
1

Howdy!

This morning I installed Ubuntu Core on a raspberry pi 3 and as usual did ‘sudo classic’ and tried building all my stuff.

Ran into a dependency problem:

libudev-dev : Depends: libudev1 (= 229-4ubuntu16) but
229-4ubuntu16+ppa2 is to be installed

I’m not sure where that funky libudev1 came from.

Anyone know what’s going on?

Here’s a little more info.

(classic)buildbot@rbb-ubu1604pi3-1:~$ cat
/etc/apt/sources.list.d/ubuntu-raspi2-ubuntu-ppa-zesty.list
deb http://ppa.launchpad.net/ubuntu-raspi2/ppa/ubuntu xenial main
# deb-src http://ppa.launchpad.net/ubuntu-raspi2/ppa/ubuntu xenial main
(classic)buildbot@rbb-ubu1604pi3-1:/var/log/apt$ sudo apt update
...
All packages are up to date.

(classic)buildbot@rbb-ubu1604pi3-1:~$ sudo apt install libudev-dev
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 libudev-dev : Depends: libudev1 (= 229-4ubuntu16) but
229-4ubuntu16+ppa2 is to be installed
E: Unable to correct problems, you have held broken packages.

(classic)buildbot@rbb-ubu1604pi3-1:~$ apt-cache policy libudev1
libudev1:
  Installed: 229-4ubuntu16+ppa2
  Candidate: 229-4ubuntu16+ppa2
  Version table:
 *** 229-4ubuntu16+ppa2 100
        100 /var/lib/dpkg/status
     229-4ubuntu16 500
        500 http://ports.ubuntu.com/ubuntu-ports xenial-updates/main
armhf Packages
     229-4ubuntu10 500
        500 http://ports.ubuntu.com/ubuntu-ports xenial-security/main
armhf Packages
     229-4ubuntu4 500
        500 http://ports.ubuntu.com/ubuntu-ports xenial/main armhf Packages
3

There is a conflict between what is in the Ubuntu archive and what is in the ubuntu-image PPA used to construct the core snap.

You can easily avoid this conflict by running the following two commands inside the classic environment:

echo "deb http://archive.ubuntu.com/ubuntu/ xenial-proposed restricted main universe" > /etc/apt/sources.list.d/ubuntu-proposed.list
echo "deb http://ppa.launchpad.net/snappy-dev/image/ubuntu xenial main" > /etc/apt/sources.list.d/ubuntu-image-ppa.list

Afterwards a apt-get update should get everything back working.

4

This is caused by Bug #1659195 “resolver regression on ubuntu-core from #1636912” : Bugs : systemd package : Ubuntu :confused:

5

@slangasek Steve, any chance we can get a fix for the above issue introduced by a patch in Ubuntu’s systemd?

6

@slangasek Steve, any chance we can get a fix for the above issue
introduced by a patch in Ubuntu’s systemd?

I’ve followed up on the bug report. If we can get some direction on a
reproducer for this issue, we should be able to make quick work of it.