Ran
|
Jobs
1
|
Files
293
|
Run time
47s
|
Badge
Embed ▾
README BADGES
|
push
travis-ci
<a href="https://github.com/tarantool/tarantool/commit/<a class=hub.com/tarantool/tarantool/commit/e38d2762cd1950ed3bbb70306350cbc441c2a938">e38d2762c<a href="https://github.com/tarantool/tarantool/commit/e38d2762cd1950ed3bbb70306350cbc441c2a938">">debian: don&#39;t install systemd service file twice It fixes the following errors during tarantool installation from packages on debian / ubuntu: ``` Unpacking tarantool (1.9.1.23.gacbd91c-1) ... dpkg: error processing archive /var/cache/apt/archives/tarantool_1.9.1.23.gacbd91c-1_amd64.deb (--unpack): trying to overwrite &#39;/lib/systemd/system/tarantool.service&#39;, which is also in package tarantool-common 1.9.1.23.gacbd91c-1 ``` The problem is that tarantool.service file was shipped with tarantool-common and tarantool packages both. It is the regression after </a><a class="double-link" href="https://github.com/tarantool/tarantool/commit/<a class="double-link" href="https://github.com/tarantool/tarantool/commit/8925b8622f381378684de633e917229051e3482f">8925b8622</a>">8925b8622</a><a href="https://github.com/tarantool/tarantool/commit/e38d2762cd1950ed3bbb70306350cbc441c2a938">. The way to avoid installing / enabling the service file within tarantool package is to pass `--name` option to dh_systemd_enable, but do not pass the service file name. In that case dh_systemd_enable does not found the service file and does not enforce existence of the file. Hope there is less hacky way to do so, but I don't found one at the moment.
38246 of 46904 relevant lines covered (81.54%)
912612.6 hits per line
ID | Job ID | Ran | Files | Coverage | |
---|---|---|---|---|---|
3 | 12466.3 (TARGET=coverage) | 293 |
81.54 |
Travis Job 12466.3 |
Coverage | ∆ | File | Lines | Relevant | Covered | Missed | Hits/Line |
---|