<feed xmlns='http://www.w3.org/2005/Atom'>
<title>apt/apt-pkg/deb/deblistparser.cc, branch 1.1.exp1</title>
<subtitle>Debians commandline package manager</subtitle>
<id>https://git.kalnischkies.de/apt/atom?h=1.1.exp1</id>
<link rel='self' href='https://git.kalnischkies.de/apt/atom?h=1.1.exp1'/>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/'/>
<updated>2014-06-18T10:41:11Z</updated>
<entry>
<title>remove the Section member from package struct</title>
<updated>2014-06-18T10:41:11Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2014-06-13T06:35:32Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=7a66977486804d46d5860f568cbd80f54f0c42d0'/>
<id>urn:sha1:7a66977486804d46d5860f568cbd80f54f0c42d0</id>
<content type='text'>
A version belongs to a section and has hence a section member of its
own. A package on the other hand can have multiple versions from
different sections. This was "solved" by using the section which was
parsed first as order of sources.list defines, but that is obviously a
horribly unpredictable thing.

We therefore directly remove this struct member to free some space and
mark the access method as deprecated, which is told to return the
section of the 'newest' known version, which is at least predictable,
but possible not what it returned before – but nobody knows.

Users are way better of with the Section() as returned by the version
they are dealing with. It is likely the same for all versions of a
package, but in the few cases it isn't, it is important (like packages
moving from main/* to contrib/* or into oldlibs …).
</content>
</entry>
<entry>
<title>cleanup datatypes mix used in binary cache</title>
<updated>2014-06-18T10:41:11Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2014-06-12T10:22:45Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=4ad8619bb1f0bf777d17c568bb7a6cf7f30aac34'/>
<id>urn:sha1:4ad8619bb1f0bf777d17c568bb7a6cf7f30aac34</id>
<content type='text'>
We had a wild mixture of (unsigned) int, long and long long here without
much sense, so this commit adds a few typedefs to get some sense in the
typesystem and ensures that a ID isn't sometimes computed as int, stored
as long and compared with a long long… as this could potentially bite us
later on as the size of the archive only increases over time.
</content>
</entry>
<entry>
<title>parse and retrieve multiple Descriptions in one record</title>
<updated>2014-05-09T11:06:27Z</updated>
<author>
<name>David Kalnischkies</name>
<email>kalnischkies@gmail.com</email>
</author>
<published>2013-08-18T20:20:25Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=ffe3c68e494efc1c2c4d748fa9d69e150867e5c2'/>
<id>urn:sha1:ffe3c68e494efc1c2c4d748fa9d69e150867e5c2</id>
<content type='text'>
It seems unlikely for now that proper archives will carry multiple
Description-* stanzas in the Packages (or Translation-*) file, but
sometimes apt eats its own output as shown by the usage of the CD team
and it would be interesting to let apt output multiple translations
e.g. in 'apt-cache show'.
</content>
</entry>
<entry>
<title>WIP local deb install</title>
<updated>2014-04-28T07:59:33Z</updated>
<author>
<name>Michael Vogt</name>
<email>mvo@ubuntu.com</email>
</author>
<published>2014-04-25T22:00:51Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=0d29b9d4368284782862c7b507c47002b79ddb27'/>
<id>urn:sha1:0d29b9d4368284782862c7b507c47002b79ddb27</id>
<content type='text'>
</content>
</entry>
<entry>
<title>abstract version hash comparison a bit</title>
<updated>2014-03-13T12:58:46Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2014-03-12T16:55:08Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=68134bda8868a8614edf137aad7e9be61cd2a6ee'/>
<id>urn:sha1:68134bda8868a8614edf137aad7e9be61cd2a6ee</id>
<content type='text'>
In #737085 we see that apt can be confused if informations about
versions only differ slightly. This commit adds a way of at least adding
a few more data points with the next abi break to help a bit with it.

Git-Dch: Ignore
</content>
</entry>
<entry>
<title>factor out parsing of MultiArch flag</title>
<updated>2014-03-13T12:58:46Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2014-03-12T15:53:44Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=e33dbfe5cea09b2124be8db5a6ae0eb82ad7e9c5'/>
<id>urn:sha1:e33dbfe5cea09b2124be8db5a6ae0eb82ad7e9c5</id>
<content type='text'>
Git-Dch: Ignore
</content>
</entry>
<entry>
<title>cleanup headers and especially #includes everywhere</title>
<updated>2014-03-13T12:58:45Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2014-03-05T21:11:25Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=453b82a388013e522b3a1b9fcd6ed0810dab1f4f'/>
<id>urn:sha1:453b82a388013e522b3a1b9fcd6ed0810dab1f4f</id>
<content type='text'>
Beside being a bit cleaner it hopefully also resolves oddball problems
I have with high levels of parallel jobs.

Git-Dch: Ignore
Reported-By: iwyu (include-what-you-use)
</content>
</entry>
<entry>
<title>fix -Wmissing-field-initializers warnings</title>
<updated>2014-03-13T12:58:45Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2014-02-25T21:22:41Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=67c3067f1a615fd6ff0b332c2a526d052442913d'/>
<id>urn:sha1:67c3067f1a615fd6ff0b332c2a526d052442913d</id>
<content type='text'>
Reported-By: gcc
Git-Dch: Ignore
</content>
</entry>
<entry>
<title>support DEB_BUILD_PROFILES and -P for build profiles</title>
<updated>2014-03-13T12:58:44Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2014-02-25T13:26:18Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=ce7f128c020e1347f91c6074238fc5da58c5df71'/>
<id>urn:sha1:ce7f128c020e1347f91c6074238fc5da58c5df71</id>
<content type='text'>
Inspired by the rest of the patch in 661537, but abstract the
parsing of various ways of setting the build profiles more so it can
potentially be reused and all apt parts have the same behaviour.

Especially config options, cmdline options and environment will not be
combined as proposed as this isn't APTs usual behaviour and dpkg doesn't
do it either, so one overrides the other as it normally does.
</content>
</entry>
<entry>
<title>implement BuildProfileSpec support as dpkg has in 1.17.2</title>
<updated>2014-03-13T12:57:34Z</updated>
<author>
<name>Johannes Schauer</name>
<email>j.schauer@email.de</email>
</author>
<published>2014-02-24T23:12:20Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=565ded7b65240b25ad8551789ac388c8ce72b1f4'/>
<id>urn:sha1:565ded7b65240b25ad8551789ac388c8ce72b1f4</id>
<content type='text'>
Build-dependencies are now able to include a &lt;profile.foo …&gt;
specification limiting usage similar to already supported [arch …].
More details: https://wiki.debian.org/BuildProfileSpec

Closes: 661537
</content>
</entry>
</feed>
