<feed xmlns='http://www.w3.org/2005/Atom'>
<title>apt/apt-pkg, branch 1.9.10</title>
<subtitle>Debians commandline package manager</subtitle>
<id>https://git.kalnischkies.de/apt/atom?h=1.9.10</id>
<link rel='self' href='https://git.kalnischkies.de/apt/atom?h=1.9.10'/>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/'/>
<updated>2020-02-16T11:46:09Z</updated>
<entry>
<title>Revert "Add a Packages-Require-Authorization Release file field"</title>
<updated>2020-02-16T11:46:09Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>julian.klode@canonical.com</email>
</author>
<published>2020-02-16T10:45:05Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=9cc0e2cab7c83ede99e21c70f248d884b8930983'/>
<id>urn:sha1:9cc0e2cab7c83ede99e21c70f248d884b8930983</id>
<content type='text'>
This experiment did not turn out sensibly, as some servers do not
accept credentials when none are expected and fail, so you cannot
mirror such a repository.

This reverts commit c2b9b0489538fed4770515bd8853a960b13a2618.
</content>
</entry>
<entry>
<title>policy: Add SetPriority() methods</title>
<updated>2020-02-16T10:46:29Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>julian.klode@canonical.com</email>
</author>
<published>2020-02-16T10:40:07Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=2c1f718bb2b0d64a14ab53d323704f034b69c13a'/>
<id>urn:sha1:2c1f718bb2b0d64a14ab53d323704f034b69c13a</id>
<content type='text'>
These allow overriding priorities, however, pins set by SetPriority
for package files will be overriden by calls to InitDefaults().
</content>
</entry>
<entry>
<title>Fix remaining usec vs sec time-delta calculation typos</title>
<updated>2020-02-06T13:25:28Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2020-02-06T13:25:28Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=ef50424be1586b91a99d28bf5108f3999cc908fb'/>
<id>urn:sha1:ef50424be1586b91a99d28bf5108f3999cc908fb</id>
<content type='text'>
While moving to a more stable clock in 79b61ae I typoed the microsecond
calculation part and copied it all over the place… Julian fixed the
first two instances in 089e6271 and Trent reported the apt-ftparchive
instances leaving one instance in progress (invisible for user though).

A bit ironic that in an attempt to stop "confusing (and amusing) users"
I managed to hide a typo for close to two years doing just that…
Sadly we can't really test this as while "apt-ftparchive generate /dev/null"
is a great interactive test, it is hard to teach our test framework that
the output is "reasonably below an hour" (usually 0s, but on busy test
systems it is perhaps longer…).

Thanks: Trent W. Buck for initial patch
Closes: #950776
References: 79b61ae7673eb6213493e2cb202f0d70c390932d,
 089e627153781ae7c320a5a0724c6c70d684b689
</content>
</entry>
<entry>
<title>patterns: test for empty terms, reject them</title>
<updated>2020-02-03T11:55:54Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>julian.klode@canonical.com</email>
</author>
<published>2020-02-03T11:15:07Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=404771d0ec11f26a0b631018719e2918a049455b'/>
<id>urn:sha1:404771d0ec11f26a0b631018719e2918a049455b</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Correctly stop parsing short form arguments on space, also on ?</title>
<updated>2020-02-03T11:55:54Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>julian.klode@canonical.com</email>
</author>
<published>2020-02-01T16:33:08Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=11a40ab11f72f85e905bdba4d3274870fbcaeaee'/>
<id>urn:sha1:11a40ab11f72f85e905bdba4d3274870fbcaeaee</id>
<content type='text'>
we have to stop parsing on space so that things like ~ramd64 | ~rall
work correctly.

aptitude does not stop parsing on ?, but we'll do as it gets very
confusing otherwise if you write stuff like ~ramd64?name(foo), and
it resolves to ?and(?architecture(amd64?name), (foo))...
</content>
</entry>
<entry>
<title>patterns: Implement parsing of (...) groups</title>
<updated>2020-02-03T11:55:54Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>julian.klode@canonical.com</email>
</author>
<published>2020-02-01T16:21:40Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=8886ea163032fb8bf64211a94c5dc252a4572a9c'/>
<id>urn:sha1:8886ea163032fb8bf64211a94c5dc252a4572a9c</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Implement | as or</title>
<updated>2020-02-03T11:55:54Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>julian.klode@canonical.com</email>
</author>
<published>2020-02-01T16:12:35Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=d6f38436a229dc4421e77b58bf42d07bdb28b808'/>
<id>urn:sha1:d6f38436a229dc4421e77b58bf42d07bdb28b808</id>
<content type='text'>
</content>
</entry>
<entry>
<title>patterns: Allow rendering patterns as patterns instead of json-ish</title>
<updated>2020-02-03T11:55:54Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>julian.klode@canonical.com</email>
</author>
<published>2020-02-01T16:11:19Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=cfec457d599373e6014b1f4472f48d5f989d76a5'/>
<id>urn:sha1:cfec457d599373e6014b1f4472f48d5f989d76a5</id>
<content type='text'>
</content>
</entry>
<entry>
<title>patterns: Parse sequence of patterns as ?and</title>
<updated>2020-02-03T11:55:54Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>julian.klode@canonical.com</email>
</author>
<published>2020-01-28T21:38:46Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=250119362e44599aad7e75462fa4298ad1ab1ad9'/>
<id>urn:sha1:250119362e44599aad7e75462fa4298ad1ab1ad9</id>
<content type='text'>
</content>
</entry>
<entry>
<title>patterns: Allow bare words only in arguments</title>
<updated>2020-02-03T11:55:54Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>julian.klode@canonical.com</email>
</author>
<published>2020-01-28T22:06:08Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=ebe5f39bfbb64921d5d31e0a6e49287356a5e6e2'/>
<id>urn:sha1:ebe5f39bfbb64921d5d31e0a6e49287356a5e6e2</id>
<content type='text'>
This changes the syntax from approximately

	expr = unary
	unary = '!'? primary
	primary = pattern | short-pattern | word | quoted-word
	pattern = '?' name [ '(' expr [',' expr]* ')' ]
	short-pattern = ~ name | ~name expr
to:

        primary = pattern | short-pattern
        argument = word | quoted-word | expr
        pattern = '?' name [ '(' argument [',' argument]* ')' ]
        short-pattern = ~ name | ~name argument
</content>
</entry>
</feed>
