<feed xmlns='http://www.w3.org/2005/Atom'>
<title>apt/debian, branch 1.3_pre3</title>
<subtitle>Debians commandline package manager</subtitle>
<id>https://git.kalnischkies.de/apt/atom?h=1.3_pre3</id>
<link rel='self' href='https://git.kalnischkies.de/apt/atom?h=1.3_pre3'/>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/'/>
<updated>2016-08-04T08:25:36Z</updated>
<entry>
<title>Release 1.3~pre3</title>
<updated>2016-08-04T08:25:36Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>jak@debian.org</email>
</author>
<published>2016-08-04T08:25:36Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=c69e82559b29171f0dfc66abc8ac236d74f7201e'/>
<id>urn:sha1:c69e82559b29171f0dfc66abc8ac236d74f7201e</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Release 1.3~pre2</title>
<updated>2016-07-08T12:34:37Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>jak@debian.org</email>
</author>
<published>2016-07-08T12:33:44Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=b8c465aa89406d6bba17e8ecf04710eae2c71d08'/>
<id>urn:sha1:b8c465aa89406d6bba17e8ecf04710eae2c71d08</id>
<content type='text'>
Yes, we might still add new features to 1.3 or break some more
stuff. Stay tuned!
</content>
</entry>
<entry>
<title>Add kernels with "+" in the package name to APT::NeverAutoRemove</title>
<updated>2016-07-08T06:44:05Z</updated>
<author>
<name>Andrew Patterson</name>
<email>andrew.patterson@hpe.com</email>
</author>
<published>2016-07-06T19:40:16Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=130176bcb6ce65c98d5692196c55cc18b4c210e0'/>
<id>urn:sha1:130176bcb6ce65c98d5692196c55cc18b4c210e0</id>
<content type='text'>
Escape "+" in kernel package names when generating APT::NeverAutoRemove
list so it is not treated as a regular expression meta-character.

[Changed by David Kalnischkies: let test actually test the change]

Closes: #830159
</content>
</entry>
<entry>
<title>Release 1.3~pre1</title>
<updated>2016-07-07T18:39:03Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>jak@debian.org</email>
</author>
<published>2016-07-07T18:38:00Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=4bdf29d39c401ac479f6486469328fa648f9feab'/>
<id>urn:sha1:4bdf29d39c401ac479f6486469328fa648f9feab</id>
<content type='text'>
</content>
</entry>
<entry>
<title>eipp: let apt make a plan, not make stuff plane</title>
<updated>2016-06-29T10:17:41Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2016-06-29T07:16:53Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=8e99b22c31eb47d0422e9a69e83dc99bb315ded8'/>
<id>urn:sha1:8e99b22c31eb47d0422e9a69e83dc99bb315ded8</id>
<content type='text'>
Julian noticed on IRC that I fall victim to a lovely false friend by
calling referring to a 'planer' all the time even through these are
machines to e.g. remove splinters from woodwork ("make stuff plane").
The term I meant is written in german in this way (= with a single n)
but in english there are two, aka: 'planner'.

As that is unreleased code switching all instances without any
transitional provisions. Also the reason why its skipped in changelog.

Thanks: Julian Andres Klode
Gbp-Dch: Ignore
</content>
</entry>
<entry>
<title>eipp: provide the internal planer as an external one</title>
<updated>2016-06-27T09:57:12Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2016-05-28T13:40:59Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=f74d99c6a78caafdc6e32d8cb135683b7154795c'/>
<id>urn:sha1:f74d99c6a78caafdc6e32d8cb135683b7154795c</id>
<content type='text'>
Testing the current implementation can benefit from being able to be
feed an EIPP request and produce a fully compliant response. It is also
a great test for EIPP in general.
</content>
</entry>
<entry>
<title>eipp: implement version 0.1 of the protocol</title>
<updated>2016-06-27T09:43:09Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2016-05-14T16:07:12Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=7b197262212f49b3b355b1124edf2ba9adb73411'/>
<id>urn:sha1:7b197262212f49b3b355b1124edf2ba9adb73411</id>
<content type='text'>
The very first step in introducing the "external installation planer
protocol" (short: EIPP) as part of my GSoC2016 project.

The description reads: APT-based tools like apt-get, aptitude, synaptic,
… work with the user to figure out how their system should look like
after they are done installing/removing packages and their dependencies.
The actual installation/removal of packages is done by dpkg with the
constrain that dependencies must be fulfilled at any point in time (e.g.
to run maintainer scripts).

Historically APT has a super micro-management approach to this task
which hasn't aged that well over the years mostly ignoring changes in
dpkg and growing into an unmaintainable mess hardly anyone can debug and
everyone fears to touch – especially as more and more requirements are
tacked onto it like handling cycles and triggers, dealing with
"important" packages first, package sources on removable media, touch
minimal groups to be able to interrupt the process if needed (e.g.
unattended-upgrades) which not only sky-rocket complexity but also can
be mutually exclusive as you e.g. can't have minimal groups and minimal
trigger executions at the same time.
</content>
</entry>
<entry>
<title>add myself to Uploaders</title>
<updated>2016-06-27T09:43:09Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2016-06-27T06:52:47Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=a523cb7f26e0eae7df8e7ea4c386f954049480aa'/>
<id>urn:sha1:a523cb7f26e0eae7df8e7ea4c386f954049480aa</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Add a apt suggests powermgmt-base</title>
<updated>2016-06-27T09:22:32Z</updated>
<author>
<name>Nicolas Le Cam</name>
<email>niko.lecam@gmail.com</email>
</author>
<published>2016-06-22T18:55:18Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=6de1059e140ba227130ffea5fd3b37cb324a0605'/>
<id>urn:sha1:6de1059e140ba227130ffea5fd3b37cb324a0605</id>
<content type='text'>
debian/apt.apt-compat.cron.daily is using on_ac_power utility
</content>
</entry>
<entry>
<title>Use the ConditionACPower feature of systemd in the apt-daily service</title>
<updated>2016-06-27T09:22:02Z</updated>
<author>
<name>Nicolas Le Cam</name>
<email>niko.lecam@gmail.com</email>
</author>
<published>2016-06-22T19:39:38Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=51d659e7d8cdce59f910eceeee68e2c2afdb70d4'/>
<id>urn:sha1:51d659e7d8cdce59f910eceeee68e2c2afdb70d4</id>
<content type='text'>
.. instead of hardcoding the functionnality in the apt.systemd.daily
script.

Also make the compatibility cron job provide the same functionnality
for systems that do not use systemd.

Closes: #827930
</content>
</entry>
</feed>
