So the situation is that the old cron (https://launchpad.net/ubuntu/+source/cron/3.0pl1-124ubuntu2/+build/4287213/+files/cron_3.0pl1-124ubuntu2_amd64.deb) just ships the symlink in the .deb, and the new cron ships the plain file, and dpkg apparently refuses to replace a symlink with a file. This is currently not handled in the maintainer scripts at all, so we need to add some upgrade logic.
-- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cron in Ubuntu. https://bugs.launchpad.net/bugs/1566333 Title: trusty → xenial upgrade fails to upgrade /etc/init.d/cron Status in cron package in Ubuntu: In Progress Status in cron source package in Xenial: In Progress Bug description: Upgrading from trusty to xenial is meant to replace "/etc/init.d/cron -> /lib/init/upstart-job" with a real file /etc/init.d/cron. This works fine in a schroot, but in a container or a VM you end up with lrwxrwxrwx 1 root root 21 Feb 9 2013 /etc/init.d/cron -> /lib/init/upstart-job -rwxr-xr-x 1 root root 3049 Feb 17 18:25 /etc/init.d/cron.dpkg-new Reproducer: - start trusty container or VM - echo 'deb http://archive.ubuntu.com/ubuntu xenial main restricted universe multiverse' | sudo tee /etc/apt/sources.list - sudo apt update - sudo apt-get install -y cron To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cron/+bug/1566333/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
