[Touch-packages] [Bug 1668285] Re: [SRU] Update apt/xenial to 1.2.20

2017-04-25 Thread Launchpad Bug Tracker
This bug was fixed in the package apt - 1.2.20

---
apt (1.2.20) xenial; urgency=medium

  * Microrelease covering fixes of 1.4~rc2 (LP: #1668285)

  [ David Kalnischkies ]
  * don't install new deps of candidates for kept back pkgs
  * keep Release.gpg on untrusted to trusted IMS-Hit (Closes: 838779)
(LP: #1657440)
  * reset HOME, USER(NAME), TMPDIR & SHELL in DropPrivileges (Closes: 842877)
  * add TMP/TEMP/TEMPDIR to the TMPDIR DropPrivileges dance
  * let {dsc,tar,diff}-only implicitly enable download-only
  * don't show update stats if cache generation is disabled
  * don't lock dpkg in 'apt-get clean'
  * don't lock dpkg in update commands
  * avoid validate/delete/load race in cache generation
  * remove 'old' FAILED files in the next acquire call (Closes: 846476)
  * stop rred from leaking debug messages on recovered errors (Closes: #850759)

  [ Paul Wise ]
  * show output as documented for APT::Periodic::Verbose 2 (Closes: 845599)

  [ John R. Lenton ]
  * bash-completion: Only complete understood file paths for install
(LP: #1645815)

  [ Lukasz Kawczynski ]
  * Honour Acquire::ForceIPv4/6 in the https transport

  [ Julian Andres Klode ]
  * basehttp: Only read Content-Range on 416 and 206 responses (LP: #1657567)
  * Only merge acquire items with the same meta key (Closes: #838441)
  * Do not package names representing .dsc/.deb/... files (Closes: #854794)
  * Don't use -1 fd and AT_SYMLINK_NOFOLLOW for faccessat()
Thanks to James Clarke for debugging these issues

 -- Julian Andres Klode   Mon, 27 Feb 2017 15:29:18
+0100

** Changed in: apt (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1668285

Title:
  [SRU] Update apt/xenial to 1.2.20

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  Fix Released

Bug description:
  [Impact]
  Subset of bug #1668280 basically, to the extend the apply to 1.2. This is a 
far saner amount of changes than in 1.3.5, because we don't have the 
installation ordering changes as the new installation ordering was introduced 
in 1.3.

[ David Kalnischkies ]
* don't install new deps of candidates for kept back pkgs
* keep Release.gpg on untrusted to trusted IMS-Hit (Closes: 838779)
  (LP: #1657440)
* reset HOME, USER(NAME), TMPDIR & SHELL in DropPrivileges (Closes: 842877)
* add TMP/TEMP/TEMPDIR to the TMPDIR DropPrivileges dance
* let {dsc,tar,diff}-only implicitly enable download-only
* don't show update stats if cache generation is disabled
* don't lock dpkg in 'apt-get clean'
* don't lock dpkg in update commands
* avoid validate/delete/load race in cache generation
* remove 'old' FAILED files in the next acquire call (Closes: 846476)
* stop rred from leaking debug messages on recovered errors (Closes: 
#850759)

[ Paul Wise ]
* show output as documented for APT::Periodic::Verbose 2 (Closes: 845599)

[ John R. Lenton ]
* bash-completion: Only complete understood file paths for install
  (LP: #1645815)

[ Lukasz Kawczynski ]
* Honour Acquire::ForceIPv4/6 in the https transport

[ Julian Andres Klode ]
* basehttp: Only read Content-Range on 416 and 206 responses (LP: #1657567)
* Only merge acquire items with the same meta key (Closes: #838441)
* Do not package names representing .dsc/.deb/... files (Closes: #854794)
* Don't use -1 fd and AT_SYMLINK_NOFOLLOW for faccessat()
  Thanks to James Clarke for debugging these issues

  [Test case]
  Mentioned launchpad bugs have their own test case sections. The rest is 
checked in the CI, so we should just do some updates upgrades and check that 
everything works.

  [Regression Potential]
  In #1668280, about 80% of the code changes are covered by test cases. This 
leaves out most code changes that are not covered, so code coverage should be 
higher, reducing the regression potential enormously.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1668285] Re: [SRU] Update apt/xenial to 1.2.20

2017-03-16 Thread Julian Andres Klode
I've been doing a middle-large upgrade today, alongside some other more
focused tests, and everything seems to have worked fine. Let's mark this
as verified.

** Tags removed: verification-needed
** Tags added: verification-done

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1668285

Title:
  [SRU] Update apt/xenial to 1.2.20

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  Fix Committed

Bug description:
  [Impact]
  Subset of bug #1668280 basically, to the extend the apply to 1.2. This is a 
far saner amount of changes than in 1.3.5, because we don't have the 
installation ordering changes as the new installation ordering was introduced 
in 1.3.

[ David Kalnischkies ]
* don't install new deps of candidates for kept back pkgs
* keep Release.gpg on untrusted to trusted IMS-Hit (Closes: 838779)
  (LP: #1657440)
* reset HOME, USER(NAME), TMPDIR & SHELL in DropPrivileges (Closes: 842877)
* add TMP/TEMP/TEMPDIR to the TMPDIR DropPrivileges dance
* let {dsc,tar,diff}-only implicitly enable download-only
* don't show update stats if cache generation is disabled
* don't lock dpkg in 'apt-get clean'
* don't lock dpkg in update commands
* avoid validate/delete/load race in cache generation
* remove 'old' FAILED files in the next acquire call (Closes: 846476)
* stop rred from leaking debug messages on recovered errors (Closes: 
#850759)

[ Paul Wise ]
* show output as documented for APT::Periodic::Verbose 2 (Closes: 845599)

[ John R. Lenton ]
* bash-completion: Only complete understood file paths for install
  (LP: #1645815)

[ Lukasz Kawczynski ]
* Honour Acquire::ForceIPv4/6 in the https transport

[ Julian Andres Klode ]
* basehttp: Only read Content-Range on 416 and 206 responses (LP: #1657567)
* Only merge acquire items with the same meta key (Closes: #838441)
* Do not package names representing .dsc/.deb/... files (Closes: #854794)
* Don't use -1 fd and AT_SYMLINK_NOFOLLOW for faccessat()
  Thanks to James Clarke for debugging these issues

  [Test case]
  Mentioned launchpad bugs have their own test case sections. The rest is 
checked in the CI, so we should just do some updates upgrades and check that 
everything works.

  [Regression Potential]
  In #1668280, about 80% of the code changes are covered by test cases. This 
leaves out most code changes that are not covered, so code coverage should be 
higher, reducing the regression potential enormously.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1668285] Re: [SRU] Update apt/xenial to 1.2.20

2017-03-08 Thread Chris J Arges
Hello Julian, or anyone else affected,

Accepted apt into xenial-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/apt/1.2.20 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!

** Changed in: apt (Ubuntu Xenial)
   Status: In Progress => Fix Committed

** Tags added: verification-needed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1668285

Title:
  [SRU] Update apt/xenial to 1.2.20

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  Fix Committed

Bug description:
  [Impact]
  Subset of bug #1668280 basically, to the extend the apply to 1.2. This is a 
far saner amount of changes than in 1.3.5, because we don't have the 
installation ordering changes as the new installation ordering was introduced 
in 1.3.

[ David Kalnischkies ]
* don't install new deps of candidates for kept back pkgs
* keep Release.gpg on untrusted to trusted IMS-Hit (Closes: 838779)
  (LP: #1657440)
* reset HOME, USER(NAME), TMPDIR & SHELL in DropPrivileges (Closes: 842877)
* add TMP/TEMP/TEMPDIR to the TMPDIR DropPrivileges dance
* let {dsc,tar,diff}-only implicitly enable download-only
* don't show update stats if cache generation is disabled
* don't lock dpkg in 'apt-get clean'
* don't lock dpkg in update commands
* avoid validate/delete/load race in cache generation
* remove 'old' FAILED files in the next acquire call (Closes: 846476)
* stop rred from leaking debug messages on recovered errors (Closes: 
#850759)

[ Paul Wise ]
* show output as documented for APT::Periodic::Verbose 2 (Closes: 845599)

[ John R. Lenton ]
* bash-completion: Only complete understood file paths for install
  (LP: #1645815)

[ Lukasz Kawczynski ]
* Honour Acquire::ForceIPv4/6 in the https transport

[ Julian Andres Klode ]
* basehttp: Only read Content-Range on 416 and 206 responses (LP: #1657567)
* Only merge acquire items with the same meta key (Closes: #838441)
* Do not package names representing .dsc/.deb/... files (Closes: #854794)
* Don't use -1 fd and AT_SYMLINK_NOFOLLOW for faccessat()
  Thanks to James Clarke for debugging these issues

  [Test case]
  Mentioned launchpad bugs have their own test case sections. The rest is 
checked in the CI, so we should just do some updates upgrades and check that 
everything works.

  [Regression Potential]
  In #1668280, about 80% of the code changes are covered by test cases. This 
leaves out most code changes that are not covered, so code coverage should be 
higher, reducing the regression potential enormously.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1668285] Re: [SRU] Update apt/xenial to 1.2.20

2017-02-27 Thread Julian Andres Klode
Uploaded now.

** Also affects: apt (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

** Changed in: apt (Ubuntu Xenial)
   Status: New => Incomplete

** Changed in: apt (Ubuntu Xenial)
   Status: Incomplete => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1668285

Title:
  [SRU] Update apt/xenial to 1.2.20

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  In Progress

Bug description:
  [Impact]
  Subset of bug #1668280 basically, to the extend the apply to 1.2. This is a 
far saner amount of changes than in 1.3.5, because we don't have the 
installation ordering changes as the new installation ordering was introduced 
in 1.3.

[ David Kalnischkies ]
* don't install new deps of candidates for kept back pkgs
* keep Release.gpg on untrusted to trusted IMS-Hit (Closes: 838779)
  (LP: #1657440)
* reset HOME, USER(NAME), TMPDIR & SHELL in DropPrivileges (Closes: 842877)
* add TMP/TEMP/TEMPDIR to the TMPDIR DropPrivileges dance
* let {dsc,tar,diff}-only implicitly enable download-only
* don't show update stats if cache generation is disabled
* don't lock dpkg in 'apt-get clean'
* don't lock dpkg in update commands
* avoid validate/delete/load race in cache generation
* remove 'old' FAILED files in the next acquire call (Closes: 846476)
* stop rred from leaking debug messages on recovered errors (Closes: 
#850759)

[ Paul Wise ]
* show output as documented for APT::Periodic::Verbose 2 (Closes: 845599)

[ John R. Lenton ]
* bash-completion: Only complete understood file paths for install
  (LP: #1645815)

[ Lukasz Kawczynski ]
* Honour Acquire::ForceIPv4/6 in the https transport

[ Julian Andres Klode ]
* basehttp: Only read Content-Range on 416 and 206 responses (LP: #1657567)
* Only merge acquire items with the same meta key (Closes: #838441)
* Do not package names representing .dsc/.deb/... files (Closes: #854794)
* Don't use -1 fd and AT_SYMLINK_NOFOLLOW for faccessat()
  Thanks to James Clarke for debugging these issues

  [Test case]
  Mentioned launchpad bugs have their own test case sections. The rest is 
checked in the CI, so we should just do some updates upgrades and check that 
everything works.

  [Regression Potential]
  In #1668280, about 80% of the code changes are covered by test cases. This 
leaves out most code changes that are not covered, so code coverage should be 
higher, reducing the regression potential enormously.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp