<feed xmlns='http://www.w3.org/2005/Atom'>
<title>apt/apt-pkg/cacheset.cc, branch 2.3.4</title>
<subtitle>Debians commandline package manager</subtitle>
<id>https://git.kalnischkies.de/apt/atom?h=2.3.4</id>
<link rel='self' href='https://git.kalnischkies.de/apt/atom?h=2.3.4'/>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/'/>
<updated>2021-04-25T14:25:57Z</updated>
<entry>
<title>Count uninstallable packages in "not upgraded"</title>
<updated>2021-04-25T14:25:57Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2021-03-06T13:12:01Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=f90b892e6acc0ca725811ef0dd9be3fed66c444f'/>
<id>urn:sha1:f90b892e6acc0ca725811ef0dd9be3fed66c444f</id>
<content type='text'>
If a first step of the solver can figure out that a package is
uninstallable it might reset the candidate so that later steps are
prevented from exploring this dead end. While that helps the resolver it
can confuse the display of the found solution as this will include an
incorrect count of packages not upgraded in this solution.

It was possible before, but happens a fair bit more with the April/May
resolver changes last year so finally doing proper counting is a good
idea.

Sadly this is a bit harder than just getting the number first and than
subtracting the packages we upgraded from it as the user can influence
candidates via the command line and a package which could be upgraded,
but is removed instead shouldn't count as not upgraded as we clearly did
something with it. So we keep a list of packages instead of a number
which also help in the upgrade cmds as those want to show the list.

Closes: #981535
</content>
</entry>
<entry>
<title>Check satisfiability for versioned provides, not providing version</title>
<updated>2020-05-19T09:22:19Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2020-05-19T09:20:28Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=dcd920e99df964d320e18ac133d575d4151deb85'/>
<id>urn:sha1:dcd920e99df964d320e18ac133d575d4151deb85</id>
<content type='text'>
References: dcdfb4723a9969b443d1c823d735e192c731df69
</content>
</entry>
<entry>
<title>Support negative dependencies in VCI::FromDependency</title>
<updated>2020-05-18T13:55:36Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2020-05-16T08:52:11Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=dcdfb4723a9969b443d1c823d735e192c731df69'/>
<id>urn:sha1:dcdfb4723a9969b443d1c823d735e192c731df69</id>
<content type='text'>
The important change is adding IsIgnoreable() as it will deal with
self-conflicts and such, but while we are at it lets sprinkle in some
refactoring.
</content>
</entry>
<entry>
<title>Reinstate * wildcards</title>
<updated>2020-05-04T10:48:56Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>julian.klode@canonical.com</email>
</author>
<published>2020-05-04T10:23:50Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=75f59b16312523ab3deb995c48e8c8ae07586c23'/>
<id>urn:sha1:75f59b16312523ab3deb995c48e8c8ae07586c23</id>
<content type='text'>
Reinstate * wildcards as they are safe to use, but do not allow any
other special characters such as ? or [].

Notably, ? would overlap with patterns, and [] might overlap with
future pattern extensions (alternative bracketing style), it's also
hard to explain.

Closes: #953531
LP: #1872200
</content>
</entry>
<entry>
<title>cacheset: Fix -Wdeprecated-copy warnings</title>
<updated>2020-02-26T17:59:39Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>julian.klode@canonical.com</email>
</author>
<published>2020-02-26T17:46:06Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=62ca61ff4ac794f9c42335d8286343149d4313d1'/>
<id>urn:sha1:62ca61ff4ac794f9c42335d8286343149d4313d1</id>
<content type='text'>
Remove the operator= from Container_iterator, as it was basically
just the default anyway, and add copy constructors to *Interface
that match their operator=.

Tried adding copy constructor to Container_iterator, but that only
made things worse.
</content>
</entry>
<entry>
<title>Implement short patterns (patterns starting with ~)</title>
<updated>2020-02-03T11:55:54Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>julian.klode@canonical.com</email>
</author>
<published>2020-01-20T13:14:49Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=fd43b1694f1382a3a47f5dc546ebe3d39fcd6e7d'/>
<id>urn:sha1:fd43b1694f1382a3a47f5dc546ebe3d39fcd6e7d</id>
<content type='text'>
Also make pattern detector in cacheset and private's list accept
such patterns. We probably should just try to parse and see if it
is a (start of a) pattern.
</content>
</entry>
<entry>
<title>apt(8): Disable regular expressions and fnmatch</title>
<updated>2020-01-15T21:19:17Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>julian.klode@canonical.com</email>
</author>
<published>2020-01-15T21:01:54Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=21cb4a9e513ccb6f376fbcaf67957c4851cbbe32'/>
<id>urn:sha1:21cb4a9e513ccb6f376fbcaf67957c4851cbbe32</id>
<content type='text'>
This is the first step. Next step will be to add warnings to
apt-get and then remove support there as well.
</content>
</entry>
<entry>
<title>Add pattern tree parser infra and connect with cacheset and apt list</title>
<updated>2019-08-15T18:21:34Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>julian.klode@canonical.com</email>
</author>
<published>2019-08-15T09:47:00Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=08b61197f418883ea20563e2251fb60779c0ba87'/>
<id>urn:sha1:08b61197f418883ea20563e2251fb60779c0ba87</id>
<content type='text'>
This adds a transformation from parse tree into a CacheFilter and
connects it with cachesets and the apt list command.
</content>
</entry>
<entry>
<title>Remove deprecated cacheset methods</title>
<updated>2019-06-14T12:28:35Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>julian.klode@canonical.com</email>
</author>
<published>2019-06-14T12:28:35Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=a15f2d0deeb90ce79903823e9317d4fa3e47acff'/>
<id>urn:sha1:a15f2d0deeb90ce79903823e9317d4fa3e47acff</id>
<content type='text'>
This mostly turns them private and then overrides the public
version with the switch, as recommended.
</content>
</entry>
<entry>
<title>cacheset: Remove simple cases of deprecated code</title>
<updated>2019-05-06T13:02:38Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>julian.klode@canonical.com</email>
</author>
<published>2019-05-06T13:02:38Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=f6d7e21b7ba31f396d4e8c8e8a0b5b31562afb5b'/>
<id>urn:sha1:f6d7e21b7ba31f396d4e8c8e8a0b5b31562afb5b</id>
<content type='text'>
This is missing the ones that are still actively used in
cacheset.cc, we need to clean those up too, but they are
obviously more tricky.
</content>
</entry>
</feed>
