Debian Package Tracker - google-compute-image-packages

general

source: google-compute-image-packages (main)
version: 20181206-2
maintainer: Lucas Kanashiro [DMD]
uploaders: Google Cloud Team [DMD]
arch: all any
std-ver: 4.3.0
VCS: Git (Browse, QA)

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

[pool directory]

stable-bpo: 20181206-2~bpo9+1
testing: 20181206-2
unstable: 20181206-2

versioned links

20181206-2~bpo9+1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
20181206-2: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]

binaries

google-compute-engine
google-compute-engine-oslogin
python3-google-compute-engine

action needed

Depends on packages which need a new maintainer normal

The packages that google-compute-image-packages depends on which need a new maintainer are:

json-c (#844452)
- Depends: libjson-c3
- Build-Depends: libjson-c-dev

Created: 2018-12-22 Last update: 2019-01-17 14:55

0 new commits since last upload, time to upload? normal

vcswatch reports that this package seems to have a new changelog entry (version 20181206-3, distribution UNRELEASED) and new commits in its VCS. You should consider whether it's time to make an upload.

Here are the relevant commit messages:

None

https://salsa.debian.org/api/v4/projects/debian%2Fgoogle-compute-image-packages API request failed: 404 Not Found at /srv/qa.debian.org/data/vcswatch/vcswatch line 386.

Created: 2019-01-03 Last update: 2019-01-16 21:59

lintian reports 15 warnings normal

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

Created: 2019-01-12 Last update: 2019-01-12 05:41

Build log checks report 2 warnings low

Build log checks report 2 warnings

Created: 2018-12-22 Last update: 2018-12-22 22:53

testing migrations

This package will soon be part of the auto-json-c transition. You might want to ensure that your package is ready for it. You can probably find supplementary information in the debian-release archives or in the corresponding release.debian.org bug.

news

[rss feed]

[2019-01-16] Accepted google-compute-image-packages 20181206-2~bpo9+1 (source amd64 all) into stretch-backports (Lucas Kanashiro)
[2019-01-16] Accepted google-compute-image-packages 20181206-1~bpo9+1 (source amd64 all) into stretch-backports, stretch-backports (Bastian Blank)
[2019-01-08] google-compute-image-packages 20181206-2 MIGRATED to testing (Debian testing watch)
[2019-01-03] Accepted google-compute-image-packages 20181206-2 (source amd64 all) into unstable (Lucas Kanashiro)
[2019-01-01] google-compute-image-packages 20181206-1 MIGRATED to testing (Debian testing watch)
[2018-12-27] google-compute-image-packages 20180905-2 MIGRATED to testing (Debian testing watch)
[2018-12-26] Accepted google-compute-image-packages 20181206-1 (source amd64 all) into unstable (Lucas Kanashiro)
[2018-12-22] Accepted google-compute-image-packages 20180905-2 (source amd64 all) into unstable, unstable (Lucas Kanashiro)

bugs [bug history graph]

all: 0

links

homepage
lintian (0, 15)
buildd: logs, checks, clang, reproducibility
popcon
debci
browse source code
edit tags