<feed xmlns='http://www.w3.org/2005/Atom'>
<title>apt/apt-pkg/deb, branch 1.0.9.4</title>
<subtitle>Debians commandline package manager</subtitle>
<id>https://git.kalnischkies.de/apt/atom?h=1.0.9.4</id>
<link rel='self' href='https://git.kalnischkies.de/apt/atom?h=1.0.9.4'/>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/'/>
<updated>2014-11-28T15:15:39Z</updated>
<entry>
<title>fix PTY interaction on linux and kfreebsd</title>
<updated>2014-11-28T15:15:39Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2014-11-17T23:59:39Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=299aea924ccef428219ed6f1a026c122678429e6'/>
<id>urn:sha1:299aea924ccef428219ed6f1a026c122678429e6</id>
<content type='text'>
We run dpkg on its own pty, so we can log its output and have our own
output around it (like the progress bar), while also allowing debconf
and configfile prompts to happen.

In commit 223ae57d468fdcac451209a095047a07a5698212 we changed to
constantly reopening the slave for kfreebsd. This has the sideeffect
though that in some cases slave and master will lose their connection on
linux, so that no output is passed along anymore. We fix this by having
always an fd referencing the slave open (linux), but we don't use it
(kfreebsd).

Failing to get our PTY up and running has many (bad) consequences
including (not limited to, nor all at ones or in any case) garbled ouput,
no output, no logging, a (partial) mixture of the previous items, …
This commit is therefore also reshuffling quiet a bit of the creation
code to get especially the output part up and running on linux and the
logging for kfreebsd.

Note that the testcase tries to cover some cases, but this is an
interactivity issue so only interactive usage can really be a good test.

Closes: 765687
</content>
</entry>
<entry>
<title>close leaking slave fd after setting up pty magic</title>
<updated>2014-11-28T15:15:39Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2014-11-17T14:06:35Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=9fc0b435593839de47098212f0ae5f15b6263099'/>
<id>urn:sha1:9fc0b435593839de47098212f0ae5f15b6263099</id>
<content type='text'>
The fd moves out of scope here anyway, so we should close it properly
instead of leaking it which will tickle down to dpkg maintainer scripts.

Closes: 767774
</content>
</entry>
<entry>
<title>use 'best' hash for source authentication</title>
<updated>2014-11-10T16:23:29Z</updated>
<author>
<name>David Kalnischkies</name>
<email>kalnischkies@gmail.com</email>
</author>
<published>2013-08-18T21:27:24Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=3a2b39ee602dd5a98b8fdaee2f1c8e0b13a276e2'/>
<id>urn:sha1:3a2b39ee602dd5a98b8fdaee2f1c8e0b13a276e2</id>
<content type='text'>
Collect all hashes we can get from the source record and put them into a
HashStringList so that 'apt-get source' can use it instead of using
always the MD5sum.

We therefore also deprecate the MD5 struct member in favor of the list.

While at it, the parsing of the Files is enhanced so that records which
miss "Files" (aka MD5 checksums) are still searched for other checksums
as they include just as much data, just not with a nice and catchy name.

This is a cherry-pick of 1262d35 with some dirty tricks to preserve ABI.

LP: 1098738
</content>
</entry>
<entry>
<title>Fix incorrect comparison between signed/unsigned</title>
<updated>2014-10-23T18:32:01Z</updated>
<author>
<name>Michael Vogt</name>
<email>mvo@debian.org</email>
</author>
<published>2014-10-23T18:32:01Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=28460cb27846b2437010b08adf10bde18e370974'/>
<id>urn:sha1:28460cb27846b2437010b08adf10bde18e370974</id>
<content type='text'>
Git-Dch: ignore
</content>
</entry>
<entry>
<title>Use sysconf(_SC_ARG_MAX) to find the size of Dpkg::MaxArgBytes</title>
<updated>2014-10-23T18:19:32Z</updated>
<author>
<name>Michael Vogt</name>
<email>mvo@debian.org</email>
</author>
<published>2014-10-23T18:19:32Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=a3cada6abc42a2966c427a3b0731977ecfa7edcb'/>
<id>urn:sha1:a3cada6abc42a2966c427a3b0731977ecfa7edcb</id>
<content type='text'>
Instead of hardcoding Dpkg::MaxArgBytes find out about it using
the sysconf(_SC_ARG_MAX) call.
</content>
</entry>
<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>generalize Acquire::GzipIndex</title>
<updated>2014-09-21T08:18:03Z</updated>
<author>
<name>Michael Vogt</name>
<email>mvo@debian.org</email>
</author>
<published>2014-09-21T08:18:03Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=b0f4b486e6850c5f98520ccf19da71d0ed748ae4'/>
<id>urn:sha1:b0f4b486e6850c5f98520ccf19da71d0ed748ae4</id>
<content type='text'>
</content>
</entry>
<entry>
<title>rework PTY magic to fix stair-stepping on kfreebsd</title>
<updated>2014-09-08T19:05:11Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2014-09-08T19:05:11Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=223ae57d468fdcac451209a095047a07a5698212'/>
<id>urn:sha1:223ae57d468fdcac451209a095047a07a5698212</id>
<content type='text'>
A pty slave we have got from openpty can only be used for one dpkg
child, if we give it to a second child on kfreebsd setting TIOCSCTTY
fails causing the output to be stair-stepped from now on.

By switching the code to creating a master and opening a new slave in
the child for each child we can fix this glitch, so that at least the
master remains stable.

Closes: 759684
</content>
</entry>
<entry>
<title>fix progress report for upgrade and reinstall</title>
<updated>2014-09-08T16:44:24Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2014-09-08T15:14:17Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=4c559e97ba4cc0d3a2995b7c451e606539d2f1be'/>
<id>urn:sha1:4c559e97ba4cc0d3a2995b7c451e606539d2f1be</id>
<content type='text'>
APT treats upgrades like installs and dpkg is very similar in this, but
prints still a slightly different processing message indicating that it
is really an upgrade which we hadn't parsed so far, but this wasn't
really visible as we quickly moved on to a 'known' state.

More problematic was the reinstall case as apt hadn't recognized this
for the package name detection, so that reinstalls had no progress since
we introduced MultiArch.
</content>
</entry>
</feed>
