Public bug reported: vsftpd 3.0.3-3ubuntu1 is stuck in xenial-proposed because it's failing its autopkgtests.
The reason for the autopkgtest failure is straightforward; vsftpd is failing to start on installation. $ systemctl status vsftpd.service ● vsftpd.service - vsftpd FTP server Loaded: loaded (/lib/systemd/system/vsftpd.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Mon 2016-03-28 19:55:47 UTC; 7min ago Main PID: 25705 (code=exited, status=2) Mar 28 19:55:47 xenial-i386 systemd[1]: Starting vsftpd FTP server... Mar 28 19:55:47 xenial-i386 systemd[1]: Started vsftpd FTP server. Mar 28 19:55:47 xenial-i386 systemd[1]: vsftpd.service: Main process exited, code=exited, status=2/INVALIDARGUMENT Mar 28 19:55:47 xenial-i386 systemd[1]: vsftpd.service: Unit entered failed state. Mar 28 19:55:47 xenial-i386 systemd[1]: vsftpd.service: Failed with result 'exit-code'. $ Manually running the command from the service file fails with: $ sudo /usr/sbin/vsftpd /etc/vsftpd.conf 500 OOPS: vsftpd: not configured for standalone, must be started from inetd $ This is due to debian/patches/0013-listen.patch, which has caused the daemon to not listen on either ipv4 or ipv6, so it fails to start at all. ** Affects: vsftpd (Ubuntu) Importance: Undecided Assignee: Chris J Arges (arges) Status: New ** Changed in: vsftpd (Ubuntu) Assignee: (unassigned) => Chris J Arges (arges) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to vsftpd in Ubuntu. https://bugs.launchpad.net/bugs/1563027 Title: vsftpd 3.0.3-3ubuntu1 fails to start on installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vsftpd/+bug/1563027/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs