<feed xmlns='http://www.w3.org/2005/Atom'>
<title>apt/apt-private/private-install.cc, branch 2.2.1</title>
<subtitle>Debians commandline package manager</subtitle>
<id>https://git.kalnischkies.de/apt/atom?h=2.2.1</id>
<link rel='self' href='https://git.kalnischkies.de/apt/atom?h=2.2.1'/>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/'/>
<updated>2021-01-08T12:22:30Z</updated>
<entry>
<title>Only autoremove kernels in apt(8); respect --no-auto-remove</title>
<updated>2021-01-08T12:22:30Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>julian.klode@canonical.com</email>
</author>
<published>2021-01-08T12:22:30Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=5fddde78ad15e1f6160f65465139d2c1e416d047'/>
<id>urn:sha1:5fddde78ad15e1f6160f65465139d2c1e416d047</id>
<content type='text'>
Automatically removing kernels in apt-get could be unexpected, so limit
it to apt for now. To handle --no-auto-remove correctly, rewrite the
hack that makes apt ignore APT::Get::AutomaticRemove options from config
files such that it unsets the option.

This then means we can do FindB("APT::Get::AutomaticRemove", true) as the
default for APT::Get::AutomaticRemove::Kernels and get the behavior we
want: If you set --no-auto-remove, it is respected as that FindB returns
false; if you don't set it, it will be true.
</content>
</entry>
<entry>
<title>Automatically remove unused kernels on dist-upgrade</title>
<updated>2021-01-04T09:54:42Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>julian.klode@canonical.com</email>
</author>
<published>2020-12-17T14:19:53Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=944baec85a7496c1595242a31f6b1b37530451a5'/>
<id>urn:sha1:944baec85a7496c1595242a31f6b1b37530451a5</id>
<content type='text'>
Kernels clutter /boot and /boot is small size, so we need to take
extra care to remove kernels when possible.
</content>
</entry>
<entry>
<title>Apply various suggestions by cppcheck</title>
<updated>2019-07-08T13:51:17Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2019-07-08T13:48:59Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=2b734a7ec429825c7007c1093883229e069d36c7'/>
<id>urn:sha1:2b734a7ec429825c7007c1093883229e069d36c7</id>
<content type='text'>
Reported-By: cppcheck
</content>
</entry>
<entry>
<title>sptr: Remove deprecated smart pointer classes</title>
<updated>2019-02-26T15:31:20Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>julian.klode@canonical.com</email>
</author>
<published>2019-02-26T12:21:07Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=29465ea9555a453ca733280955505de8bfcce935'/>
<id>urn:sha1:29465ea9555a453ca733280955505de8bfcce935</id>
<content type='text'>
Please use the standard C++ variants instead.
</content>
</entry>
<entry>
<title>Introduce APT::Install::Pre-Invoke / Post-Invoke-Success</title>
<updated>2019-02-13T13:06:20Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>julian.klode@canonical.com</email>
</author>
<published>2019-02-13T13:02:12Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=3f3cad74c2abbe3837fa98030c703dd4f5f191dc'/>
<id>urn:sha1:3f3cad74c2abbe3837fa98030c703dd4f5f191dc</id>
<content type='text'>
These will run in our frontends currently, and can show
messages. For the sake of keeping the implementation
complexity low, a non-success variant of Post-Invoke
is not provided.

LP: #1815761
</content>
</entry>
<entry>
<title>Add a "reinstall" command as an alias for "install --reinstall".</title>
<updated>2019-01-27T07:27:33Z</updated>
<author>
<name>Josh Triplett</name>
<email>josh@joshtriplett.org</email>
</author>
<published>2019-01-27T07:27:33Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=0eceebbdfdc2c5e1d677bff95a9ac1ef2f728337'/>
<id>urn:sha1:0eceebbdfdc2c5e1d677bff95a9ac1ef2f728337</id>
<content type='text'>
aptitude has a similar "reinstall" command for precedent.
</content>
</entry>
<entry>
<title>Provide a "autopurge" shortcut</title>
<updated>2018-12-03T16:21:39Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>julian.klode@canonical.com</email>
</author>
<published>2018-12-03T08:19:46Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=14535446557cb8b4125e7badc5e67a9f7790ab53'/>
<id>urn:sha1:14535446557cb8b4125e7badc5e67a9f7790ab53</id>
<content type='text'>
This adds a new "autopurge" command that will is a shortcut for
"autoremove --purge"

Thanks: Michael Vogt for the initial work
</content>
</entry>
<entry>
<title>Add support for dpkg frontend lock</title>
<updated>2018-08-07T13:07:52Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>jak@debian.org</email>
</author>
<published>2017-01-29T12:05:18Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=c2c8b4787b0882234ba2772ec7513afbf97b563a'/>
<id>urn:sha1:c2c8b4787b0882234ba2772ec7513afbf97b563a</id>
<content type='text'>
The dpkg frontend lock is a lock dpkg tries to acquire
except if the frontend already acquires it.

This fixes a race condition in the install command where the
dpkg lock is not held for a short period of time between
different dpkg invocations.

For this reason we also define an environment variable
DPKG_FRONTEND_LOCKED for dpkg invocations so dpkg knows
not to try to acquire the frontend lock because it's held
by a parent process.

We can set DPKG_FRONTEND_LOCKED only if the frontend lock
really is held; that is, if our lock count is greater than 0
- otherwise an apt client not using the LockInner family of
functions would run dpkg without the frontend lock set, but
with DPKG_FRONTEND_LOCKED set. Such a process has a weaker
guarantee: Because dpkg would not lock the frontend lock
either, the process is prone to the existing races, and,
more importantly, so is a new style process.

Closes: #869546

[fixups: fix error messages, add public IsLocked() method, and
 make {Un,}LockInner return an error on !debSystem]
</content>
</entry>
<entry>
<title>Support local files as arguments in show command</title>
<updated>2018-05-11T15:58:46Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2018-04-12T07:59:47Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=6085ab7488326cfed8f82e07eefcbc2dc40d4bea'/>
<id>urn:sha1:6085ab7488326cfed8f82e07eefcbc2dc40d4bea</id>
<content type='text'>
Now that --with-source is supported in show we can go a little further
and add the "syntactic sugar" of supporting deb-files on the commandline
directly to give users an alternative to remembering dpkg -I for deb
files &amp; as a bonus apt also works on changes files.

Most of the code churn is actually to deal with cases probably not too
common in reality like mixing packages and deb-files on the commandline
and getting the right order for these multiple records.

Closes: 883206
</content>
</entry>
<entry>
<title>Support release selector for volatile files as well</title>
<updated>2018-05-11T15:58:46Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2018-01-26T22:33:25Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=ce9223cc4e4ffcc43d17ae97ff8c57fb759a2c49'/>
<id>urn:sha1:ce9223cc4e4ffcc43d17ae97ff8c57fb759a2c49</id>
<content type='text'>
The syntax is a bit awkward, but it is the same as for a package name
and introducing another syntax wouldn't really help usability, so with
apt install ./foo.deb/experimental you will get the dependencies of foo
satisfied by your default release, but if this wouldn't satisfy the
version requirements the candidate for this dependency is switched to
the version from the experimental release. The same applies for apt
build-dep ./foo.dsc/stable-backports which was the initial request.
</content>
</entry>
</feed>
