[Touch-packages] [Bug 1926964] [NEW] missing libapt-pkg4.12 dependency

Public bug reported: It seems python-apt from ubuntu precise ESM made it into the old precise-security repo. Unfortunately, it depends on libapt-pkg4.12 (>= 0.8.16~exp12ubuntu10.28), which is not available. The following packages have unmet dependencies: python-apt : Depends: libapt-pkg4.12 (>=

[Touch-packages] [Bug 1823053] Re: wpasupplicant 2.6 w/ openssl 1.1.1 triggers TLSv1.3 version intolerance on WPA2-Enterprise networks on Cosmic and Disco

It seems this is also applicable to ubuntu bionic since openssl 1.1.1 landed in bionic-updates. We have bionic clients that cannot connect to the enterprise wifi because they attempt TLS 1.3. Recompiling openssl with the "no-tls1_3" Configure option fixes the problem. See also

[Touch-packages] [Bug 1745463] Re: Disabling systemd-resolved breaks dhclient resolvconf integration

I quite agree with @GeekSmith here. We disabled systemd-resolved on bionic and install ifupdown instead since we install this on server that have a static configuration and we don't want systemd-resolved to modify anything in the resolv.conf file. Only during the initial installation time of the

[Touch-packages] [Bug 1745463] Re: Disabling systemd-resolved breaks dhclient resolvconf integration

Just clarifying that we don't use the resolvconf package either, but just a plain static /etc/resolv.conf file. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1745463

[Touch-packages] [Bug 1811861] Re: incorrect permissions on /var/log after debootstrap

Sorry for the noise, it seems this is not related to rsyslog after all. In our install process we are moving /var/log to another partition (mounted in /data/) and then symlink it to /var/log. Permissions are set up properly and work while the system is running. When the system is rebooted though

[Touch-packages] [Bug 1811861] Re: incorrect permissions on /var/log after debootstrap

Actually, it looks like this is already fixed in cosmic. Can this be ported to bionic as well? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/1811861 Title: incorrect

[Touch-packages] [Bug 1811861] [NEW] incorrect permissions on /var/log after debootstrap

Public bug reported: we are debootstrapping a full bionic distribution into a directory. After debootstrapping the permissions on /var/log are incorrect, causing rsyslog to fail because it cannot write into the directory to create the various files. Also, in the postinst of the rsyslog package I