enterprise-support team mailing list archive

[ Christian Ehrhardt  <1792728@xxxxxxxxxxxxxxxxxx>]

Yeah sorry for the delay Simon, due to the hickup of the squid3 fix
clashing with the squid4 upload that finally was passing NEW queue and
all that this got lost.

Yes now'd be a good time to start this.

But first lets mark the bug accordingly to its current state.
Due to the bug being fixed for src:squid and not the old src:squid3 the update got lost.

** Also affects: squid (Ubuntu)
   Importance: Undecided
       Status: New

** Also affects: squid (Ubuntu Cosmic)
   Importance: Undecided
       Status: New

** Also affects: squid3 (Ubuntu Cosmic)
   Importance: Undecided
       Status: New

** Also affects: squid (Ubuntu Bionic)
   Importance: Undecided
       Status: New

** Also affects: squid3 (Ubuntu Bionic)
   Importance: Undecided
       Status: New

** No longer affects: squid (Ubuntu Bionic)

** No longer affects: squid3 (Ubuntu Cosmic)

** Changed in: squid3 (Ubuntu)
       Status: New => Invalid

** Changed in: squid3 (Ubuntu Bionic)
       Status: New => Triaged

** Changed in: squid (Ubuntu Cosmic)
       Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Server/Client Support Team, which is subscribed to squid in Ubuntu.
Matching subscriptions: Ubuntu Server/Client Support Team, Ubuntu Server/Client Support Team
https://bugs.launchpad.net/bugs/1792728

Title:
  [apparmor] allow reading squid binary

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