<feed xmlns='http://www.w3.org/2005/Atom'>
<title>apt/prepare-release, branch 1.4_beta4</title>
<subtitle>Debians commandline package manager</subtitle>
<id>https://git.kalnischkies.de/apt/atom?h=1.4_beta4</id>
<link rel='self' href='https://git.kalnischkies.de/apt/atom?h=1.4_beta4'/>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/'/>
<updated>2016-08-29T13:42:06Z</updated>
<entry>
<title>test, travis: Quieter testing with a new -qq mode</title>
<updated>2016-08-29T13:42:06Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>jak@debian.org</email>
</author>
<published>2016-08-19T18:37:28Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=30ea7a60404ee53393235827202968393951d106'/>
<id>urn:sha1:30ea7a60404ee53393235827202968393951d106</id>
<content type='text'>
Introduce a new -qq mode for our integration test framework,
and make travis use it.

The new -qq mode sets MSGLEVEL to 1. In MSGLEVEL=1, no messages
are generated for passed tests, and all testcase filenames are
printed in the same line.

Also install first in travis, do not ls the installed output
and run the install with chronic, so we only get output if it
failed.

Gbp-Dch: ignore
</content>
</entry>
<entry>
<title>prepare-release: Use equivs and gdebi-core for travis deps</title>
<updated>2016-08-19T14:49:18Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>jak@debian.org</email>
</author>
<published>2016-08-18T12:56:36Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=ecb8e9d77faf1940c0defb78f0078f66562373b7'/>
<id>urn:sha1:ecb8e9d77faf1940c0defb78f0078f66562373b7</id>
<content type='text'>
Our previous hack did not really support or groups and other
more advanced dependency types. This hack basically removes
build profiles, and the @-type depends for tests, and otherwise
converts the deps to a package which is then installed via
gdebi.
</content>
</entry>
<entry>
<title>add the gpg-classic variant to the gpgv/gnupg or-group</title>
<updated>2016-08-17T07:52:32Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2016-08-16T13:46:19Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=19fdf93d7363261227811a62157063081b9f1a5d'/>
<id>urn:sha1:19fdf93d7363261227811a62157063081b9f1a5d</id>
<content type='text'>
We need to support partial upgrades anyhow, so we have to deal with the
different versions and your tests try to ensure that we do, so we
shouldn't make any explicit higher requirements.
</content>
</entry>
<entry>
<title>prepare-release: Switch over to CMake, set version in CMakeLists.txt</title>
<updated>2016-08-10T14:17:19Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>jak@debian.org</email>
</author>
<published>2016-08-08T20:12:16Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=66eae02467da6304025d7becc878306a0cd92011'/>
<id>urn:sha1:66eae02467da6304025d7becc878306a0cd92011</id>
<content type='text'>
Teach the prepare-release script about the version new locations
and also set the version in CMakeLists, as that is better than
reading it from the changelog: CMake would not rerun automatically
otherwise if the version changed.

Gbp-Dch: ignore
</content>
</entry>
<entry>
<title>prepare-release: Also search for libraries in CMake locations</title>
<updated>2016-08-06T20:35:54Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>jak@debian.org</email>
</author>
<published>2016-08-06T17:07:22Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=cc1b834fe966d40206d148e1f27f0502463ac69f'/>
<id>urn:sha1:cc1b834fe966d40206d148e1f27f0502463ac69f</id>
<content type='text'>
With this change, the 'library' command looks for a library libX
in the directories: build/bin, */X, X.

This allows it to find the library when building with the
upcoming CMake backend, which places the libraries in a sub
directory of the build tree with the same name as the source
tree.

For example, if building in 'build/', the apt-pkg library
will be available at 'build/apt-pkg/libapt-pkg.so.5.0'.

In case there are multiple instances of a library,
the newest one will be used.

Gbp-Dch: ignore
</content>
</entry>
<entry>
<title>prepare-release: ignore newer version symbols</title>
<updated>2016-06-04T18:45:07Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2016-06-04T18:45:07Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=382704d532b9a02237fe5706592858bbffec3862'/>
<id>urn:sha1:382704d532b9a02237fe5706592858bbffec3862</id>
<content type='text'>
The script takes the version from the changelog, but if it lacks behind
and the symbols file already includes symbols tagged for the next
version the helper prints incorrect lines as NEW for these symbols, but
ideally it shouldn't print them at all as the symbol is already dealt
with.

Git-Dch: Ignore
</content>
</entry>
<entry>
<title>prepare-release: travis: Ignore build profiles in build-depends</title>
<updated>2016-01-03T13:26:07Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>jak@debian.org</email>
</author>
<published>2016-01-03T13:24:51Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=2c80abf922e948f8c96537faf1fa36cccd80e8d9'/>
<id>urn:sha1:2c80abf922e948f8c96537faf1fa36cccd80e8d9</id>
<content type='text'>
This aids our introduction of lz4, which we do not want to impose
as an additional requirement for bootstrappers.

Gbp-Dch: ignore
</content>
</entry>
<entry>
<title>check library was built before comparing with symbols file</title>
<updated>2015-12-13T16:46:49Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2015-12-07T15:26:01Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=f09dfdbcbffe0605babd1217da92f2d8fd8552e8'/>
<id>urn:sha1:f09dfdbcbffe0605babd1217da92f2d8fd8552e8</id>
<content type='text'>
Git-Dch: Ignore
</content>
</entry>
<entry>
<title>use pre-build hook to check for pre-export execution</title>
<updated>2015-11-27T12:06:15Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2015-11-27T12:06:15Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=a95619d0ee778632cdad5bcf698a4bb88fab5676'/>
<id>urn:sha1:a95619d0ee778632cdad5bcf698a4bb88fab5676</id>
<content type='text'>
Git-Dch: Ignore
</content>
</entry>
<entry>
<title>update manpage last-modified from git via pre-export hook</title>
<updated>2015-11-25T14:20:10Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2015-11-22T18:02:13Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=ab5b1d0d31b2fbdc4896f8a107611ff056d6a668'/>
<id>urn:sha1:ab5b1d0d31b2fbdc4896f8a107611ff056d6a668</id>
<content type='text'>
Never updating this information is wrong, updating it automatically
isn't super correct either, but it seems conventional to have it and
updating it more often than needed seems better than updating it never.

Git-Dch: Ignore
</content>
</entry>
</feed>
