[Bug 1811120] Re: Backport auth.conf.d

[Julian Andres Klode]

The auth.conf.d support in trusty and xenial does not seem to be working
for https repos at least. Gotta re-investigate, it was working when I
committed it, and xenial has a test case for it, so odd.

** Tags removed: verification-needed-trusty verification-needed-xenial
** Tags added: verification-failed-trusty verification-failed-xenial

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1811120

Title:
  Backport auth.conf.d

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Trusty:
  Fix Committed
Status in apt source package in Xenial:
  Fix Committed
Status in apt source package in Bionic:
  Fix Released
Status in apt source package in Cosmic:
  Fix Released
Status in apt source package in Disco:
  Fix Released

Bug description:
  [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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1811120/+subscriptions