Oh, this is slightly embarrassing: THe reason it failed is that I forgot to update apt-transport-https in trusty and xenial.
After upgrading apt-transport-https, auth.conf.d support is working correctly in both 1.0.1ubuntu2.21 in trusty-proposed, and 1.2.30 in xenial-proposed. ** Tags removed: verification-failed-trusty verification-failed-xenial verification-needed ** Tags added: verification-done verification-done-trusty verification-done-xenial ** Description changed: [Impact] Backport auth.conf.d support to allow specifying per-repository authentication data in separate files, so packages can setup authenticated repositories. [Regression potential] We ignore errors from opening auth.conf.d files, so regressions can only occur when parsing a file fails, in which case apt would exit with an error. [Test case] The test suite provides autopkgtests for auth.conf.d which creates an auth.conf.d file and checks that it is successfully used; so we can check if those passed. Except on trusty- do it manually there, by adding a file for a private ppa, and then running update. + + - make sure to upgrade apt-transport-https on trusty & xenial... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1811120 Title: Backport auth.conf.d To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1811120/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
