<feed xmlns='http://www.w3.org/2005/Atom'>
<title>apt/doc/examples, branch 1.6_alpha7</title>
<subtitle>Debians commandline package manager</subtitle>
<id>https://git.kalnischkies.de/apt/atom?h=1.6_alpha7</id>
<link rel='self' href='https://git.kalnischkies.de/apt/atom?h=1.6_alpha7'/>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/'/>
<updated>2018-01-03T17:55:41Z</updated>
<entry>
<title>document https options in new apt-transport-https manpage</title>
<updated>2018-01-03T17:55:41Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2017-11-22T23:58:00Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=c28682430a27f75ceb8cc8dff78b3a560fd68399'/>
<id>urn:sha1:c28682430a27f75ceb8cc8dff78b3a560fd68399</id>
<content type='text'>
Same reasoning as with the previous commit for http with the added
benefit of moving the hard to discover and untranslated example config
into a manpage which could be translated.
</content>
</entry>
<entry>
<title>Add rapid "happy eyeballs" connection fallback (RFC 8305)</title>
<updated>2018-01-03T14:31:36Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>jak@debian.org</email>
</author>
<published>2018-01-02T21:15:50Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=3bbd328396745d0dd6c5585935040082a2c41e3e'/>
<id>urn:sha1:3bbd328396745d0dd6c5585935040082a2c41e3e</id>
<content type='text'>
Try establishing connections in alternating address families in
rapid intervals of 250 ms, adding more connections to the wait
list until one succeeds (RFC 8305, happy eyeballs 2).

It is important that WaitAndCheckErrors() waits until it has
a successful connection, a time out, or all connections failed
- otherwise the timing between tries might be wrong, and the
final long wait might exit early because one connection failed
without trying the others. Timing wise, this only works correctly
on Linux, as select() counts down there. But we rely on that in
some other places too, so this is not the time to fix that.

Timeouts are only reported in the final long wait - the short
inner waits are expected to time out more often, and multiple
times, we do not want to report them.

Closes: #668948
LP: #1308200
Gbp-Dch: paragraph
</content>
</entry>
<entry>
<title>Print syscall number and arch to stderr when trapped by seccomp</title>
<updated>2017-10-25T22:02:33Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>jak@debian.org</email>
</author>
<published>2017-10-25T21:16:09Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=39656a6f79e48f86d31c53a939481c07aceca352'/>
<id>urn:sha1:39656a6f79e48f86d31c53a939481c07aceca352</id>
<content type='text'>
This should help debugging crashes. The signal handler is a C++11
lambda, yay! Special care has been taken to only use signal handler
-safe functions inside there.
</content>
</entry>
<entry>
<title>Sandbox methods with seccomp-BPF; except cdrom, gpgv, rsh</title>
<updated>2017-10-22T21:38:31Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>jak@debian.org</email>
</author>
<published>2017-10-22T21:34:03Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=32bcbd73e0988d2d2237690ffae33b4f5cc5ff81'/>
<id>urn:sha1:32bcbd73e0988d2d2237690ffae33b4f5cc5ff81</id>
<content type='text'>
This reduces the number of syscalls to about 140 from about
350 or so, significantly reducing security risks.

Also change prepare-release to ignore the architecture lists
in the build dependencies when generating the build-depends
package for travis.

We might want to clean up things a bit more and/or move it
somewhere else.
</content>
</entry>
<entry>
<title>show a warning for Debian shutting down FTP services</title>
<updated>2017-07-26T17:09:04Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2017-07-14T11:49:33Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=054243fd0febfef5f1ba89f61eed0e6a34c6a25f'/>
<id>urn:sha1:054243fd0febfef5f1ba89f61eed0e6a34c6a25f</id>
<content type='text'>
We detect the effected sources by matching Release info – that has
potential by-catch of repositories which have incorrect field values,
but those are better fixed now anyhow. The bigger incorrectness is that
this message will not only be printed for the Debian services itself but
also for all mirrors not under Debian control but serving Debian like more
local/private mirrors which will not (directly) shutdown. It is likely
through that many of them will follow suite with less visible
announcements or break downright if their upstream source disappears, so
having false-positives here seems benefitial for the user in the end.
</content>
</entry>
<entry>
<title>Switch from /org to /srv in example apt-ftparchive configuration</title>
<updated>2017-07-12T21:59:39Z</updated>
<author>
<name>Paul Wise</name>
<email>pabs@debian.org</email>
</author>
<published>2017-07-12T21:31:05Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=da2dd028d94df4abc453dd3821f5ae47fc1f919c'/>
<id>urn:sha1:da2dd028d94df4abc453dd3821f5ae47fc1f919c</id>
<content type='text'>
/org has been obsoleted by /srv for many years on debian.org hosts.
</content>
</entry>
<entry>
<title>fix various typos reported by codespell &amp; spellintian</title>
<updated>2017-07-08T12:55:29Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2017-07-08T12:45:26Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=4a9c136bdb1ec8e73e104738a923e08786c521ef'/>
<id>urn:sha1:4a9c136bdb1ec8e73e104738a923e08786c521ef</id>
<content type='text'>
Reported-By: codespell &amp; spellintian
Gbp-Dch: Ignore
</content>
</entry>
<entry>
<title>ask for releaseinfo change interactively in apt</title>
<updated>2017-06-28T17:18:47Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2017-05-28T15:44:11Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=24b5bc4e41ed527799a9fa01dec9c29294d0a3f2'/>
<id>urn:sha1:24b5bc4e41ed527799a9fa01dec9c29294d0a3f2</id>
<content type='text'>
If we have a user sitting around we can let 'apt' ask the user for a
confirmation rather than print errors at the end and require the user to
figure out which commandline flags are needed to confirm the changes
non-interactively.
</content>
</entry>
<entry>
<title>error in update on Release information changes</title>
<updated>2017-06-28T17:18:47Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2017-04-12T15:39:06Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=081fbea14d12f79c8d91ce4fe1f1004c7bc08656'/>
<id>urn:sha1:081fbea14d12f79c8d91ce4fe1f1004c7bc08656</id>
<content type='text'>
The value of Origin, Label, Codename and co can be used in user
configuration from apts own pinning to unattended upgrades.
A repository changing this values can therefore have serious effects on
the behaviour of apt and other tools using these values.

In a first step we will generate error messages for these changes now
explaining the need for explicit confirmation and provide config options
and commandline flags to accept them.
</content>
</entry>
<entry>
<title>Introduce Acquire::AllowTLS to turn off TLS support</title>
<updated>2017-06-28T15:34:51Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>jak@debian.org</email>
</author>
<published>2017-06-28T15:17:37Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=147ac0fc90d972a11f5e91521ba3d385015b5945'/>
<id>urn:sha1:147ac0fc90d972a11f5e91521ba3d385015b5945</id>
<content type='text'>
As requested by Henrique de Moraes Holschuh, here comes
an option to disable TLS support. If the option is set
to false, the internal TLS layer is disabled.
</content>
</entry>
</feed>
