<feed xmlns='http://www.w3.org/2005/Atom'>
<title>apt/apt-pkg, branch 2.1.12</title>
<subtitle>Debians commandline package manager</subtitle>
<id>https://git.kalnischkies.de/apt/atom?h=2.1.12</id>
<link rel='self' href='https://git.kalnischkies.de/apt/atom?h=2.1.12'/>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/'/>
<updated>2020-11-06T09:51:06Z</updated>
<entry>
<title>Do not immediately configure m-a: same packages in lockstep</title>
<updated>2020-11-06T09:51:06Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>julian.klode@canonical.com</email>
</author>
<published>2020-10-08T09:50:19Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=2b13473a9b9947f55a0871d146e4fee456b0af60'/>
<id>urn:sha1:2b13473a9b9947f55a0871d146e4fee456b0af60</id>
<content type='text'>
In LP#835625, it was reported that apt did not unpack multi-arch
packages in the correct order, and dpkg did not like that. The fix
also made apt configure packages together, which is not strictly
necessary.

This turned out to cause issues now, because of dependencies on
libc6:i386 that caused immediate configuration of that to not
work.

Work around the issue by not configuring multi-arch: same packages
in lockstep if they have the immediate flag set. This will be the
pseudo-essential set, and given how essential works, we mostly need
the native arch to work correctly anyway.

LP: #1871268
Regression-Of: 30426f4822516bdd26528aa2e6d8d69c1291c8d3
</content>
</entry>
<entry>
<title>Do not produce late error if immediate configuration fails, just warn</title>
<updated>2020-10-21T09:47:29Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>julian.klode@canonical.com</email>
</author>
<published>2020-10-21T09:47:29Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=998a17d7e6f834c341f198ca5b6df2f27e18df38'/>
<id>urn:sha1:998a17d7e6f834c341f198ca5b6df2f27e18df38</id>
<content type='text'>
We are seeing more and more installations fail due to immediate
configuration issues related to libc6. Immediate configuration is
supposed to ensure that an essential package is configured immediately,
just in case some other packages use a part of the essential package
that only works if that package is configured.

This used to be a warning, it was turned into an error in some commit I
can't remember right now, but importantly, the error missed a return,
which means that ordering completed succesfully and packages were being
installed anyway; and after all that happened successfully, we'd print
an error at the end and exit with an error code, which is not super
useful.

Revert the error back to a warning such that the behavior stays the same
but we do not fail (unless we mess up ordering which then gets caught by
a consistency check later on.

Closes: #953260
Closes: #972552
LP: #1871268
</content>
</entry>
<entry>
<title>acquire: Do not hide _errror messages in Fail()</title>
<updated>2020-08-11T06:57:47Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>julian.klode@canonical.com</email>
</author>
<published>2020-08-11T06:56:39Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=626b7ccc8cec120f789ef89c2d5d28b8b6d67a04'/>
<id>urn:sha1:626b7ccc8cec120f789ef89c2d5d28b8b6d67a04</id>
<content type='text'>
If we have errors pending, always log them with our failure
message to provide more context.
</content>
</entry>
<entry>
<title>Default Acquire::AllowReleaseInfoChange::Suite to "true"</title>
<updated>2020-08-10T13:39:33Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>julian.klode@canonical.com</email>
</author>
<published>2020-08-10T13:39:33Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=64b45e294f0c6931a9b57ae6cc99ecded8f6a2d3'/>
<id>urn:sha1:64b45e294f0c6931a9b57ae6cc99ecded8f6a2d3</id>
<content type='text'>
Closes: #931566
</content>
</entry>
<entry>
<title>Merge branch 'master' into 'master'</title>
<updated>2020-08-04T10:16:36Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>jak@debian.org</email>
</author>
<published>2020-08-04T10:16:36Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=63c0657ea54c9268bc1855d5eac92bc636532bd6'/>
<id>urn:sha1:63c0657ea54c9268bc1855d5eac92bc636532bd6</id>
<content type='text'>
Support marking all newly installed packages as automatically installed

See merge request apt-team/apt!110</content>
</entry>
<entry>
<title>Merge branch 'pu/less-slaves' into 'master'</title>
<updated>2020-08-04T10:12:30Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>jak@debian.org</email>
</author>
<published>2020-08-04T10:12:30Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=11530bab64efd4b4fc46de7833533cea9c69f521'/>
<id>urn:sha1:11530bab64efd4b4fc46de7833533cea9c69f521</id>
<content type='text'>
Remove master/slave terminology

See merge request apt-team/apt!124</content>
</entry>
<entry>
<title>Replace whitelist/blacklist with allowlist/denylist</title>
<updated>2020-08-04T10:12:11Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>julian.klode@canonical.com</email>
</author>
<published>2020-07-14T14:34:20Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=7d8bb855487d6821b0cd6bf5d2270ed8fda3d1a3'/>
<id>urn:sha1:7d8bb855487d6821b0cd6bf5d2270ed8fda3d1a3</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Merge branch 'pu/apt-key-deprecated' into 'master'</title>
<updated>2020-08-04T10:07:10Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>jak@debian.org</email>
</author>
<published>2020-08-04T10:07:10Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=1afe7c8b874abb61cde591e0241b967ef1b99991'/>
<id>urn:sha1:1afe7c8b874abb61cde591e0241b967ef1b99991</id>
<content type='text'>
Fully deprecate apt-key, schedule removal for Q2/2022

See merge request apt-team/apt!119</content>
</entry>
<entry>
<title>Reorder config check before result looping for SRV parsing debug</title>
<updated>2020-07-02T16:57:11Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2020-06-30T08:11:09Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=1bfc0907c987758529bcdc4ebfb34364702a2d8b'/>
<id>urn:sha1:1bfc0907c987758529bcdc4ebfb34364702a2d8b</id>
<content type='text'>
It isn't needed to iterate over all results if we will be doing nothing
anyhow as it isn't that common to have that debug option enabled.
</content>
</entry>
<entry>
<title>Add dependency points in the resolver also to providers</title>
<updated>2020-07-02T16:57:11Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2020-06-19T16:49:11Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=1f910d94add8f20ebfa5999a7795e678a4af0826'/>
<id>urn:sha1:1f910d94add8f20ebfa5999a7795e678a4af0826</id>
<content type='text'>
We were traditionally adding points for some dependency types to the
real package, but we should also do it for providers of that package to
help the resolver especially if the real package is for some reason not
tagged for removal yet/anymore.

While at it we ensure that the points are only attributed once for each
package as especially with versioned provides a package can nowadays
provide another many times and would hence acquire a lot of points.
</content>
</entry>
</feed>
