<feed xmlns='http://www.w3.org/2005/Atom'>
<title>apt/test/libapt, branch 1.9.4</title>
<subtitle>Debians commandline package manager</subtitle>
<id>https://git.kalnischkies.de/apt/atom?h=1.9.4</id>
<link rel='self' href='https://git.kalnischkies.de/apt/atom?h=1.9.4'/>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/'/>
<updated>2019-09-19T09:11:18Z</updated>
<entry>
<title>Fix use of GTest to adjust for GTest 1.9</title>
<updated>2019-09-19T09:11:18Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>julian.klode@canonical.com</email>
</author>
<published>2019-09-19T09:02:44Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=25006573002971500d1501331716e9ca348f815f'/>
<id>urn:sha1:25006573002971500d1501331716e9ca348f815f</id>
<content type='text'>
GTest 1.9 uses a variable defined in the parent directory, thus
failing to configure. Configure the project in the parent directory
instead.
</content>
</entry>
<entry>
<title>Add initial support for parsing patterns into parse trees</title>
<updated>2019-08-15T11:50:03Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>julian.klode@canonical.com</email>
</author>
<published>2019-08-14T12:38:26Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=690ff4c3e44e7063ebde2557b7c0087ab720b894'/>
<id>urn:sha1:690ff4c3e44e7063ebde2557b7c0087ab720b894</id>
<content type='text'>
Introduce a parser for patterns that generates a parse tree. The
language understood by the parser is:

pattern = '?'TERM
        | '?'TERM '(' pattern (',' pattern)* ','? ')'
        | WORD
        | QUOTED-WORD
TERM    = [0-9a-zA-Z-]
WORD    = [0-9a-ZA-Z-.*^$\[\]_\\]
QUOTED_WORD = "..."		# you know what I mean

This language is context free, which is a massive simplification
from aptitude's language, where ?foo(bar) could have two different
meanings depending on whether ?foo takes an argument or not.
</content>
</entry>
<entry>
<title>Adjust code for missing includes/using std::string</title>
<updated>2019-06-12T13:02:55Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>julian.klode@canonical.com</email>
</author>
<published>2019-06-12T11:47:46Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=82b881caafa0c82b20db3900f8b76cebd8a393a4'/>
<id>urn:sha1:82b881caafa0c82b20db3900f8b76cebd8a393a4</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Make APT::StringView public</title>
<updated>2019-06-11T12:45:55Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>julian.klode@canonical.com</email>
</author>
<published>2019-02-04T18:50:16Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=a6e86d51a0e32cdc91f2902b0d6b483af884dcca'/>
<id>urn:sha1:a6e86d51a0e32cdc91f2902b0d6b483af884dcca</id>
<content type='text'>
</content>
</entry>
<entry>
<title>CMake: Enforce "override" use on overriden methods</title>
<updated>2019-05-06T14:29:40Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>julian.klode@canonical.com</email>
</author>
<published>2019-05-06T14:29:40Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=3bec42fdf01eb3f7403876979023ad952228ee73'/>
<id>urn:sha1:3bec42fdf01eb3f7403876979023ad952228ee73</id>
<content type='text'>
This ensures that we do not accidentally stop overriding a
method because it's signature changed in an API break.
</content>
</entry>
<entry>
<title>Merge libapt-inst into libapt-pkg</title>
<updated>2019-05-06T10:14:04Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>julian.klode@canonical.com</email>
</author>
<published>2019-05-06T09:40:08Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=dfe2511e31f232a8a8880eba40af40d1deb0e49c'/>
<id>urn:sha1:dfe2511e31f232a8a8880eba40af40d1deb0e49c</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Merge branch 'pu/refuseunsignedlines' into 'master'</title>
<updated>2019-02-01T14:40:06Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>jak@debian.org</email>
</author>
<published>2019-02-01T14:40:06Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=d5dcc2e9d3008b57c3fae0bcb5b1c2a197f5430c'/>
<id>urn:sha1:d5dcc2e9d3008b57c3fae0bcb5b1c2a197f5430c</id>
<content type='text'>
Fail if InRelease or Release.gpg contain unsigned lines

See merge request apt-team/apt!45</content>
</entry>
<entry>
<title>Step over empty sections in TagFiles with comments</title>
<updated>2019-02-01T13:51:56Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2019-02-01T13:51:56Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=5caa8cac3bc0ffa8b5360f3e5d5c84e710eb394b'/>
<id>urn:sha1:5caa8cac3bc0ffa8b5360f3e5d5c84e710eb394b</id>
<content type='text'>
Implementing a parser with recursion isn't the best idea, but in
practice we should get away with it for the time being to avoid
needless codechurn.

Closes: #920317 #921037
</content>
</entry>
<entry>
<title>Refuse files with lines unexpectedly starting with a dash</title>
<updated>2019-01-28T19:45:02Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2019-01-28T19:45:02Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=9b840b59cc80a072e14b8adc9d76669a7a50ab87'/>
<id>urn:sha1:9b840b59cc80a072e14b8adc9d76669a7a50ab87</id>
<content type='text'>
We support dash-encoding even if we don't really work with files who
would need it as implementations are free to encode every line, but
otherwise a line starting with a dash must either be a header we parse
explicitly or the file is refused. This is against the RFC which says
clients should warn on such files, but given that we aren't expecting
any files with dash-started lines to begin with this looks a lot like a
we should not continue to touch the file as it smells like an attempt to
confuse different parsers by "hiding" headers in-between others.

The other slightly more reasonable explanation would be an armor header
key starting with a dash, but no existing key does that and it seems
unlikely that this could ever happen. Also, it is recommended that
clients warn about unknown keys, so new appearance is limited.
</content>
</entry>
<entry>
<title>Fail instead of warn for unsigned lines in InRelease</title>
<updated>2019-01-23T18:10:47Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2019-01-23T16:47:49Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=3734cceb44b02ca4d5ee3c6f5cbfe1e12f17cffb'/>
<id>urn:sha1:3734cceb44b02ca4d5ee3c6f5cbfe1e12f17cffb</id>
<content type='text'>
The warnings were introduced 2 years ago without any reports from the
wild about them actually appearing for anyone, so now seems to be an as
good time as any to switch them to errors.

This allows rewritting the code by failing earlier instead of trying to
keep going which makes the diff a bit hard to follow but should help
simplifying reasoning about it.

References: 6376dfb8dfb99b9d182c2fb13aa34b2ac89805e3
</content>
</entry>
</feed>
