<feed xmlns='http://www.w3.org/2005/Atom'>
<title>apt, branch 1.3.5</title>
<subtitle>[no description]</subtitle>
<id>https://git.osdyson.ru/apt/atom?h=1.3.5</id>
<link rel='self' href='https://git.osdyson.ru/apt/atom?h=1.3.5'/>
<link rel='alternate' type='text/html' href='https://git.osdyson.ru/apt/'/>
<updated>2017-02-27T14:25:21Z</updated>
<entry>
<title>Release 1.3.5</title>
<updated>2017-02-27T14:25:21Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>jak@debian.org</email>
</author>
<published>2017-02-27T14:25:21Z</published>
<link rel='alternate' type='text/html' href='https://git.osdyson.ru/apt/commit/?id=a69b2560b8e882300df658b5505cc9490ab410d1'/>
<id>urn:sha1:a69b2560b8e882300df658b5505cc9490ab410d1</id>
<content type='text'>
</content>
</entry>
<entry>
<title>CMake: Install statvfs.h to include/sys, not just include/</title>
<updated>2017-02-22T15:53:46Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>jak@debian.org</email>
</author>
<published>2016-08-22T20:28:45Z</published>
<link rel='alternate' type='text/html' href='https://git.osdyson.ru/apt/commit/?id=8b191eac9fbf7669b0e2b9abe2bba02d85f67af6'/>
<id>urn:sha1:8b191eac9fbf7669b0e2b9abe2bba02d85f67af6</id>
<content type='text'>
We are including sys/statvfs.h, not statvfs.h, so make sure our
dummy in the correct spot.

(cherry picked from commit c050f4fa30ccda637f3e05edddf750b768c8590d)
</content>
</entry>
<entry>
<title>Don't use -1 fd and AT_SYMLINK_NOFOLLOW for faccessat()</title>
<updated>2017-02-22T15:53:46Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>jak@debian.org</email>
</author>
<published>2017-02-11T21:17:08Z</published>
<link rel='alternate' type='text/html' href='https://git.osdyson.ru/apt/commit/?id=21242490e80dadb167a64c1815c08e1d2258fb61'/>
<id>urn:sha1:21242490e80dadb167a64c1815c08e1d2258fb61</id>
<content type='text'>
-1 is not an allowed value for the file descriptor, the only
allowed non-file-descriptor value is AT_FDCWD. So use that
instead.

AT_SYMLINK_NOFOLLOW has a weird semantic: It checks whether
we have the specified access on the symbolic link. It also
is implemented only by glibc on Linux, so it's inherently
non-portable. We should just drop it.

Thanks: James Clarke for debugging these issues
Reported-by: James Clarke &lt;jrtc27@jrtc27.com&gt;
(cherry picked from commit 25f54c960d7a4ceca7bd3e21f87baf48d6cbc2d3)
</content>
</entry>
<entry>
<title>Do not package names representing .dsc/.deb/... files</title>
<updated>2017-02-22T15:53:46Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>jak@debian.org</email>
</author>
<published>2017-02-10T21:39:00Z</published>
<link rel='alternate' type='text/html' href='https://git.osdyson.ru/apt/commit/?id=83e6e1a8fc942668f9a01906cb8349fb70a45b3d'/>
<id>urn:sha1:83e6e1a8fc942668f9a01906cb8349fb70a45b3d</id>
<content type='text'>
In the case of build-dep and other commands where a file can be
passed we must make sure not to normalize the path name as that
can have odd side effects, or well, cause the operation to do
nothing.

Test for build-dep-file is adjusted to perform the vcard check
once as "vcard" and once as "VCard", thus testing that this
solves the reported bug.

We inline the std::transform() and optimize it a bit to not
write anything in the common case (package names are defined
to be lowercase, the whole transformation is just for names
that should not exist...) to counter the performance hit of
the added find() call (it's about 0.15% more instructions
than with the existing transform, but we save about 0.67%
in writes...).

Closes: #854794
(cherry picked from commit 85ee4036c68d8ecd2c973d413a17aca81380900b)
</content>
</entry>
<entry>
<title>Only merge acquire items with the same meta key</title>
<updated>2017-02-22T15:53:46Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>jak@debian.org</email>
</author>
<published>2017-01-25T02:38:59Z</published>
<link rel='alternate' type='text/html' href='https://git.osdyson.ru/apt/commit/?id=d2749c845954fc1ea38133b050ee49d6f6544235'/>
<id>urn:sha1:d2749c845954fc1ea38133b050ee49d6f6544235</id>
<content type='text'>
Since the introduction of by-hash, two differently named
files might have the same real URL. In our case, the files
icons-64x64.tar.gz and icons-128x128.tar.gz of empty tarballs.

APT would try to merge them and end with weird errors because
it completed the first download and enters the second stage for
decompressing and verifying. After that it would queue a new item
to copy the original file to the location, but that copy item would
be in the wrong stage, causing it to use the hashes for the
decompressed item.

Closes: #838441
(cherry picked from commit 7b78e8bef1fc9de22d826db1db9df25f97d3710c)
</content>
</entry>
<entry>
<title>COPYING.GPL: Update to recent version (address, LGPL name)</title>
<updated>2017-02-22T15:53:46Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>jak@debian.org</email>
</author>
<published>2017-01-28T13:03:44Z</published>
<link rel='alternate' type='text/html' href='https://git.osdyson.ru/apt/commit/?id=e87c862cbd3aee8200f9752a0023ff53312e6dbd'/>
<id>urn:sha1:e87c862cbd3aee8200f9752a0023ff53312e6dbd</id>
<content type='text'>
Just copied over from common-licenses. Seems we missed to do
that earlier.

Gbp-Dch: ignore
(cherry picked from commit 84285d17bab32a0ceafe31a5b2be61cc4f520b42)
</content>
</entry>
<entry>
<title>travis: Do not build documentation in root job</title>
<updated>2017-02-22T15:53:46Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>jak@debian.org</email>
</author>
<published>2017-01-24T18:28:51Z</published>
<link rel='alternate' type='text/html' href='https://git.osdyson.ru/apt/commit/?id=92ec321709d5da32cf2de04dbf897137ead7bb6b'/>
<id>urn:sha1:92ec321709d5da32cf2de04dbf897137ead7bb6b</id>
<content type='text'>
This speeds up testing things as root, which is good, because
we usually test as user.

Gbp-Dch: ignore
(cherry picked from commit 17dadc40aefbbdd002b864edd157e4795e54fba3)
</content>
</entry>
<entry>
<title>travis: Run test suites for root and user in separate build jobs</title>
<updated>2017-02-22T15:53:46Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>jak@debian.org</email>
</author>
<published>2017-01-17T20:35:33Z</published>
<link rel='alternate' type='text/html' href='https://git.osdyson.ru/apt/commit/?id=e12dbcbaf486d176762d82f75307b9f5dfa66752'/>
<id>urn:sha1:e12dbcbaf486d176762d82f75307b9f5dfa66752</id>
<content type='text'>
This hopefully cuts down on the test time. Optimally, we'd just have
one build job and parallize, but that requires a tty or something,
probably due to GNU parallel?

Gbp-Dch: ignore
(cherry picked from commit 9b7c71f145e51c2d655ef09fca434d02db08331d)
</content>
</entry>
<entry>
<title>basehttp: Only read Content-Range on 416 and 206 responses</title>
<updated>2017-02-22T15:53:46Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>jak@debian.org</email>
</author>
<published>2017-01-18T19:39:27Z</published>
<link rel='alternate' type='text/html' href='https://git.osdyson.ru/apt/commit/?id=b5d0e1be09fd07e693bae8046848059f578d029f'/>
<id>urn:sha1:b5d0e1be09fd07e693bae8046848059f578d029f</id>
<content type='text'>
This fixes issues with sourceforge where the redirector includes
such a Content-Range in a 302 redirect. Since we do not really know
what file is meant in a redirect, let's just ignore it for all
responses other than 416 and 206.

Maybe we should also get rid of the other errors, and just ignore
the field in those cases as well?

LP: #1657567
(cherry picked from commit 4759a702081297bde66982efed8b2b7fd39ca27c)
</content>
</entry>
<entry>
<title>stop rred from leaking debug messages on recovered errors</title>
<updated>2017-02-22T15:53:46Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2017-01-19T03:14:08Z</published>
<link rel='alternate' type='text/html' href='https://git.osdyson.ru/apt/commit/?id=d0a345d4a41802e9129b78d70aabd6239a3c651a'/>
<id>urn:sha1:d0a345d4a41802e9129b78d70aabd6239a3c651a</id>
<content type='text'>
rred can fail for a plentory of reasons, but its failure is usually
recoverable (Ign lines) so it shouldn't leak unrequested debug messages
to an observing user.

Closes: #850759
(cherry picked from commit 2984d7aec37e09b473c7b99f43d20622c25dc99d)
</content>
</entry>
</feed>
