apt, branch 1.2.3

Release 1.2.3

2016-02-10T17:02:45Z

Build system messed up the 1.2.2 commit by not updating the .po files properly, so they are now.

test: use our special downloaded dir for 'source' result

2016-02-10T13:17:06Z

Otherwise the test run as root fails seeing the W: Can't drop privileges for downloading as file 'foo_1.tar.gz' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied) warning in a command which isn't supposed to warn. One trivial test, two fixups and still counting… Git-Dch: Ignore

accept any tarball compression in 814139 testcase

2016-02-10T12:50:40Z

Travis still uses a dpkg version which defaults to gz and as which compression is picked isn't all to important as long as one is just accept any. Git-Dch: Ignore

test that seeking to a position earlier in the file works

2016-02-10T12:31:12Z

This tests the fix for #812994, #813000 Gbp-Dch: ignore

get dpkg lock in build-dep if cache was invalid again

2016-02-10T12:03:00Z

Regression introduced in a249b3e6fd798935a02b769149c9791a6fa6ef16, which in the case of an invalid cache would build the first part unlocked and later pick up the (still unlocked) cache for further processing, so the system got never locked and apt would end up complaining about being unable to release the lock at shutdown. The far more common case of having a valid cache worked as expected and hence covered up the problem – especially as tests who would have noticed it are simulations only, which do not lock. Closes: 814139 Reported-By: Balint Reczey Reported-By: Helmut Grohne on IRC

Set seekpos to 0 after reopening files in Seek()

2016-02-10T11:48:37Z

If we just reopened the file, we also need to reset the current seek position when we reset the buffer, otherwise the code will not try to seek to the position given to Skip (from 0), but will try to seek to old offset + the position given to skip. Closes: #812994, #813000

Release 1.2.2

2016-02-04T21:53:21Z

Use some semantically more correct buffer operations

2016-02-04T17:34:42Z

When writing into the buffer write to free() bytes starting at getend(), instead of buffersize_max bytes at get() -> get() is a read pointer. This makes no difference in practice though, as we reset the buffer before the call, so start = end = 0. Gbp-Dch: ignore

test: Fix apt-key tests to work with current gpg 2.1

2016-02-04T17:13:05Z

Correctly report write errors when flushing buffered writer

2016-02-04T17:00:42Z

We cannot just return false without setting an error, as InternalWrite does not set one itself.