Does not allow appstream files

[Michał Sawicz]

With appstream [1] showing up in Ubuntu, acng prevents apt-get update by returning 403 errors for .yml.gz files:

W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/xenial/restricted/dep11/Components-amd64.yml 403 Forbidden file type or location: http://archive.ubuntu.com/ubuntu/dists/xenial/restricted/dep11/Components-amd64.yml.gz
W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/xenial/universe/dep11/Components-amd64.yml 403 Forbidden file type or location: http://archive.ubuntu.com/ubuntu/dists/xenial/universe/dep11/Components-amd64.yml.gz

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: apt-cacher-ng 0.7.26-1
ProcVersionSignature: Ubuntu 3.13.0-77.121-generic 3.13.11-ckt32
Uname: Linux 3.13.0-77-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.19
Architecture: amd64
Date: Fri Feb 19 11:08:51 2016
SourcePackage: apt-cacher-ng
UpgradeStatus: Upgraded to trusty on 2014-06-20 (608 days ago)
modified.conffile..etc.apt.cacher.ng.security.conf: [inaccessible: [Errno 13] Permission denied: '/etc/apt-cacher-ng/security.conf']
mtime.conffile..etc.apt.cacher.ng.acng.conf: 2015-05-06T22:26:51.074192

[Eduard Bloch (edi-gmx)]

Ancient version. There is a fix in Debian.

[Rolf Leggewie (r0lf)]

Eduard, come on, you only uploaded the fix two months ago. Thanks for the fix, though. I will mark this as fix released for xenial, Michał already requested a backport to trusty.

Eduard, it would be nice if you set the Vcs-Git and Vcs-Browser variables in debian/control so that the information about the upstream VCS shows up at https://packages.qa.debian.org/a/apt-cacher-ng.html.

That's where I checked for the necessary patch to backport. What I found is https://alioth.debian.org/scm/browser.php?group_id=100566 but that repo IS indeed ancient. Eduard, where do you publish your upstream interim work nowadays?

[Eduard Bloch (edi-gmx)]

It is the correct repository and far from being ancient. You just need to focus on the right branch, see debian/gbp.conf for details.

I will add some Vcs links though. Actually I thought I already had done that before and never bothered to review debian/control in the last couple of years :-).

[Jean Christophe André (progfou)]

For those who wonder (because of the lack of informative comments for standard _users_...) the fix has been released in upstream version 0.8.8.

Ref. : https://alioth.debian.org/plugins/scmgit/cgi-bin/gitweb.cgi?p=apt-cacher-ng/apt-cacher-ng.git;a=commitdiff;h=c54b88bb28781b13a35c7bbc227066c7c141af9c

[Rolf Leggewie (r0lf)]

attaching untested patch for trusty

[Rolf Leggewie (r0lf)]

Michał, can you compile a package with this patch and see if the problem is fixed for you? If upstream is fixed then this should do it.

[Stefan Bader (smb)]

Rolf, I took the minimal changes and prepared a Precise version of it. Have been testing that on my box which still (no, don't ask) runs Precise and the update of a Xenial desktop succeeded after that being installed.

[Stefan Bader (smb)]

Verified the proposed Trusty patch by setting up a Trusty VM for apt-cacher-ng, then removing the dep11 data (rm /var/lib/apt/lists/*dep11*) from the apt cache, setting the http proxy to the VM and then running apt-get update.
With the current Trusty version, appstream files fail (403 error) and after updating to the proposed package this succeeds.

[Stefan Bader (smb)]

Rolf, are you able to upload apt-cacher-ng or do we need to add sponsors, too? (Because I cannot upload).

[Stefan Bader (smb)]

For now I uploaded the proposed fix for Trusty and Precise to my testing PPA (ppa:smb/testing) in case anybody else wants to test without building the packages on their own.

[Rolf Leggewie (r0lf)]

Stefan, you'd need to upload to precise-proposed.

[Stefan Bader (smb)]

Rolf, I think the upload process was changed back to all supported releases. Which means it does not matter whether the target is <release>-proposed or <release>. It will always go via proposed. Since I did not hear anything back before I prepared both uploads and asked someone to sponsor (who promptly forgot to, need to poke there again). I hope that is ok with you.

[Colin Watson (cjwatson)]

Stefan's assessment of Launchpad's behaviour regarding uploads is correct. It is not necessary to upload explicitly to -proposed.

[Jordi de Wal (jdwal)]

Just to confirm, works fine with Rolf's patch (tested on Trusty). Thanks Stefan taking away the need to build it myself :-).

[Stefan Bader (smb)]

SRU Justification:

Impact: When a new Xenial installation attempts to update its appstream cache with an older version of apt-cacher-ng as its apt proxy, it will fail with error messages about invalid files/locations.

Fix: A small addition to the embedded patterns backported from a newer version of apt-cacher-ng allows to proxy appstream extensions again.

Testcase: Having an apt-cacher-ng proxy enabled for a Xenial system (might require to manually delete the cached files before) apt-get update will expose many 403 errors. After upgrading apt-cacher-ng those will download ok.

[Stefan Bader (smb)]

Not sure about Wily. Potentially it is affected, too.

[Chris J Arges (arges)]

Hello Michał, or anyone else affected,

Accepted apt-cacher-ng into precise-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/apt-cacher-ng/0.7.2-1ubuntu2.2 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

[Chris J Arges (arges)]

Hello Michał, or anyone else affected,

Accepted apt-cacher-ng into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/apt-cacher-ng/0.7.26-1ubuntu0.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

[Chris J Arges (arges)]

Hello Michał, or anyone else affected,

Accepted apt-cacher-ng into wily-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/apt-cacher-ng/0.8.5-1ubuntu0.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

[Steve Beattie (sbeattie)]

Thanks for preparing this fix. I can confirm that the version of apt-cacher-ng in trusty-proposed (0.7.26-1ubuntu0.1) permits the downloading and caching of the appstream files. I'm also able to install and update packages as before. Marking verificaition-done for trusty.

[Stefan Bader (smb)]

Verified again for Precise and Wily as well.

[Launchpad Janitor (janitor)]

This bug was fixed in the package apt-cacher-ng - 0.7.2-1ubuntu2.2

---------------
apt-cacher-ng (0.7.2-1ubuntu2.2) precise; urgency=low

  * Backport changes needed to support AppStream / DEP-11 (LP: #1547431).
  * Backport support for by-hash index files (LP: #1568754).

 -- Stefan Bader <email address hidden> Mon, 11 Apr 2016 15:32:00 +0200

[Chris J Arges (arges)]

The verification of the Stable Release Update for apt-cacher-ng has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

[Launchpad Janitor (janitor)]

This bug was fixed in the package apt-cacher-ng - 0.7.26-1ubuntu0.1

---------------
apt-cacher-ng (0.7.26-1ubuntu0.1) trusty; urgency=medium

  [ Rolf Leggewie ]
  * backport appstream support from upstream (LP: #1547431).

  [Stefan Bader]
  * backport support for by-hash index files (LP: #1568754).

 -- Stefan Bader <email address hidden> Mon, 11 Apr 2016 15:28:48 +0200

[Launchpad Janitor (janitor)]

This bug was fixed in the package apt-cacher-ng - 0.8.5-1ubuntu0.1

---------------
apt-cacher-ng (0.8.5-1ubuntu0.1) wily; urgency=low

  * Support dep11/appstream files (LP: #1547431)
  * Support by-hash index files (LP: #1568754).
  * Also dropped "single-debian-patch" and "auto-commit" from
    debian/source/options as that seemed to prevent properly
    seperated backport patches.

 -- Stefan Bader <email address hidden> Mon, 11 Apr 2016 14:12:10 +0200

[Ryan E Perez (perezry)]

Ran into this same bug using version 0.8.0.3 (Debian Jessie)
Fix for me was to add the following to acng.conf

PfilePatternEx: \.yml.gz$