<feed xmlns='http://www.w3.org/2005/Atom'>
<title>apt/apt-pkg/deb/deblistparser.cc, branch 1.0.9.5</title>
<subtitle>Debians commandline package manager</subtitle>
<id>https://git.kalnischkies.de/apt/atom?h=1.0.9.5</id>
<link rel='self' href='https://git.kalnischkies.de/apt/atom?h=1.0.9.5'/>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/'/>
<updated>2014-10-08T15:48:44Z</updated>
<entry>
<title>Update Status field values handling</title>
<updated>2014-10-08T15:48:44Z</updated>
<author>
<name>Guillem Jover</name>
<email>guillem@debian.org</email>
</author>
<published>2014-09-01T14:09:48Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=9227645d6d355f9f4332f400b8d58c8fa8f1e899'/>
<id>urn:sha1:9227645d6d355f9f4332f400b8d58c8fa8f1e899</id>
<content type='text'>
Remove long obsolete (hold, hold-reinstreq, removal-failed) or just
wrong (post-inst-failed vs postinst-failed) values, that have been
autoconverted by dpkg at run-time to their new equivalents, so there
should not be any such instance in any recent system (removal-failed
since dpkg 1.1.4 in Apr 1996, hold and hold-reinstreq since dpkg
1.2.0 in May 1996). dpkg even stopped doing the mapping in 1.15.4
and 1.15.8 respectively.

At the same time sort the list in the same order as they appear in
the dpkg code.
</content>
</entry>
<entry>
<title>implement the updated build profile spec</title>
<updated>2014-10-06T12:43:48Z</updated>
<author>
<name>josch</name>
<email>j.schauer@email.de</email>
</author>
<published>2014-08-19T08:29:29Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=ac81c0f9b79351258d3a29212f7fda312e5afeb5'/>
<id>urn:sha1:ac81c0f9b79351258d3a29212f7fda312e5afeb5</id>
<content type='text'>
</content>
</entry>
<entry>
<title>support versioned provides as implemented by dpkg</title>
<updated>2014-08-26T18:49:48Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2014-08-16T14:33:46Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=40faab46c4d5fa766c80090f0fdb54120dbb37f2'/>
<id>urn:sha1:40faab46c4d5fa766c80090f0fdb54120dbb37f2</id>
<content type='text'>
APT supported versioned provides for a long while in an attempt to get
it working with rpm. While this support is old, we can be relatively
sure that it works as versioned provides are used internally to make
Multi-Arch:foreign work.

Previous versions of apt will print a warning indicating that the
versioned provides is ignored, so that something which "Provides: foo (=
2)" doesn't provide anything.

Note that dpkg does allow only a equals-relation in the provides line
as anything else is deemed too complex. apt doesn't support anything
else either and such a support would require potentially big changes.

Closes: 758153
</content>
</entry>
<entry>
<title>Fix debListParser to accept "no" as a value for the Multi-Arch field</title>
<updated>2014-08-24T16:43:07Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>jak@debian.org</email>
</author>
<published>2014-08-24T16:43:07Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=8f617600aeb931574baf0b53617e7759baa3f370'/>
<id>urn:sha1:8f617600aeb931574baf0b53617e7759baa3f370</id>
<content type='text'>
Seems this was missed somehow.

Closes: #759099
</content>
</entry>
<entry>
<title>handle moved mmap after UniqFindTagWrite call</title>
<updated>2014-07-07T15:19:29Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2014-07-07T15:19:29Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=4ea471ecb013d188d03a5c3efb9b21e58ef56065'/>
<id>urn:sha1:4ea471ecb013d188d03a5c3efb9b21e58ef56065</id>
<content type='text'>
A call to UniqFindTagWrite can trigger the need for a bigger mmap, which
is usually done by moving it, but with this move all pointers into it
become invalid (and have to be remapped). The compiler calculates the
pointer before the execution of the call though, so it tries to store
the returned value at the old location, resulting in a segfault.
We solve this by use of a temprorary variable as we did in the other
instances of this problem before.

Closes: #753941
</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>
</feed>
