Debian Package Tracker

general

source: debci (main)
version: 1.13
maintainer: Debian CI team [DMD]
uploaders: Paul Gevers [DMD] – Antonio Terceiro [DMD]
arch: all
std-ver: 4.1.4
VCS: Git (Browse, QA)

versions [more versions can be listed by madison] [old versions available from snapshot.debian.org]

[pool directory]

oldstable: 0.10.3
stable: 1.5.1
testing: 1.13
unstable: 1.13

versioned links

0.10.3: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
1.5.1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
1.13: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]

binaries

debci
debci-collector
debci-worker

action needed

Marked for autoremoval on 13 November due to rabbitmq-server: #910623 high

Version 1.13 of debci is marked for autoremoval from testing on Tue 13 Nov 2018. It depends (transitively) on rabbitmq-server, affected by #910623. You should try to prevent the removal by fixing these RC bugs.

Created: 2018-10-09 Last update: 2018-10-17 15:08

Debci reports failed tests (log) high

Debci reports test failures (log).

The tests ran in 0h 1m 57s

Last run: 2018-10-17 11:30:27

Previous status: fail

Created: 2018-09-26 Last update: 2018-10-17 14:26

1 bug tagged patch in the BTS normal

The BTS contains patches fixing 1 bug, consider including or untagging them.

Created: 2018-10-01 Last update: 2018-10-17 15:09

Depends on packages which need a new maintainer normal

The packages that debci depends on which need a new maintainer are:

schroot (#900874)
- Depends: schroot

Created: 2018-06-06 Last update: 2018-10-17 12:41

1 new commit since last upload, time to release? normal

vcswatch reports that this package seems to have new commits in its VCS but has not yet updated debian/changelog. You should consider updating the Debian changelog and uploading this new version into the archive.

Here are the relevant commit logs:

commit 2bee4565a6312ec0985f35a47e774bd9b3bd021b
Author: Antonio Terceiro <terceiro@debian.org>
Date:   Sun Sep 23 19:53:42 2018 -0300

    lxc/create-testbed: avoid cleaning up valid containers
    
    Sometimes, the creation of a new testbed fails for various reasons (some
    essential package) breaks debootstrap, or something fails to download.
    Those failures are already handled by autopkgtest-build-lxc: the old
    container is only replaced by the new one in case of success.  In that
    case, it's OK for debci to just keep using the older container since it
    will be upgraded before running any tests anyway.
    
    The only case where we indeed want to remove containers is when the
    customizations needed by debci are not successfully applied.

Created: 2018-09-24 Last update: 2018-10-16 19:09

lintian reports 1 warning normal

Lintian reports 1 warning about this package. You should make the package lintian clean getting rid of them.

Created: 2018-09-10 Last update: 2018-09-10 05:02

Standards version of the package is outdated. wishlist

The package should be updated to follow the last version of Debian Policy (Standards-Version 4.2.1 instead of 4.1.4).

Created: 2018-08-11 Last update: 2018-09-14 01:22

news

[rss feed]