Ubuntu
command-not-found package

Builds for command-not-found in Ubuntu Zesty

  1. Zesty (17.04)
  2. Builds
1 → 45 of 45 results First • Previous • Next • Last
[FULLYBUILT] s390x build of command-not-found 0.3ubuntu17.04.2 in ubuntu zesty PROPOSED
Build started on z13-019 and finished taking 2 minutes — see the log
[FULLYBUILT] s390x build of command-not-found 0.3ubuntu17.04.2 in ubuntu zesty PROPOSED
Build started on z13-019 and finished taking 2 minutes — see the log
[FULLYBUILT] ppc64el build of command-not-found 0.3ubuntu17.04.2 in ubuntu zesty PROPOSED
Build started on bos01-ppc64el-024 and finished taking 2 minutes — see the log
[FULLYBUILT] ppc64el build of command-not-found 0.3ubuntu17.04.2 in ubuntu zesty PROPOSED
Build started on bos01-ppc64el-024 and finished taking 2 minutes — see the log
[FULLYBUILT] i386 build of command-not-found 0.3ubuntu17.04.2 in ubuntu zesty PROPOSED
Build started on lcy01-34 and finished taking 2 minutes — see the log
[FULLYBUILT] i386 build of command-not-found 0.3ubuntu17.04.2 in ubuntu zesty PROPOSED
Build started on lcy01-34 and finished taking 2 minutes — see the log
[FULLYBUILT] armhf build of command-not-found 0.3ubuntu17.04.2 in ubuntu zesty PROPOSED
Build started on bos01-arm64-004 and finished taking 3 minutes — see the log
[FULLYBUILT] armhf build of command-not-found 0.3ubuntu17.04.2 in ubuntu zesty PROPOSED
Build started on bos01-arm64-004 and finished taking 3 minutes — see the log
[FULLYBUILT] arm64 build of command-not-found 0.3ubuntu17.04.2 in ubuntu zesty PROPOSED
Build started on bos01-arm64-001 and finished taking 2 minutes — see the log
[FULLYBUILT] arm64 build of command-not-found 0.3ubuntu17.04.2 in ubuntu zesty PROPOSED
Build started on bos01-arm64-001 and finished taking 2 minutes — see the log
[FULLYBUILT] amd64 build of command-not-found 0.3ubuntu17.04.2 in ubuntu zesty PROPOSED
Build started on lcy01-33 and finished taking 2 minutes — see the log
[FULLYBUILT] amd64 build of command-not-found 0.3ubuntu17.04.2 in ubuntu zesty PROPOSED
Build started on lcy01-33 and finished taking 2 minutes — see the log
[FULLYBUILT] s390x build of command-not-found 0.3ubuntu17.04.1 in ubuntu zesty PROPOSED
Build started on z13-019 and finished taking 2 minutes — see the log
[FULLYBUILT] s390x build of command-not-found 0.3ubuntu17.04.1 in ubuntu zesty PROPOSED
Build started on z13-019 and finished taking 2 minutes — see the log
[FULLYBUILT] ppc64el build of command-not-found 0.3ubuntu17.04.1 in ubuntu zesty PROPOSED
Build started on bos01-ppc64el-029 and finished taking 2 minutes — see the log
[FULLYBUILT] ppc64el build of command-not-found 0.3ubuntu17.04.1 in ubuntu zesty PROPOSED
Build started on bos01-ppc64el-029 and finished taking 2 minutes — see the log
[FULLYBUILT] i386 build of command-not-found 0.3ubuntu17.04.1 in ubuntu zesty PROPOSED
Build started on lcy01-36 and finished taking 2 minutes — see the log
[FULLYBUILT] i386 build of command-not-found 0.3ubuntu17.04.1 in ubuntu zesty PROPOSED
Build started on lcy01-36 and finished taking 2 minutes — see the log
[FULLYBUILT] armhf build of command-not-found 0.3ubuntu17.04.1 in ubuntu zesty PROPOSED
Build started on bos01-arm64-003 and finished taking 3 minutes — see the log
[FULLYBUILT] armhf build of command-not-found 0.3ubuntu17.04.1 in ubuntu zesty PROPOSED
Build started on bos01-arm64-003 and finished taking 3 minutes — see the log
[FULLYBUILT] arm64 build of command-not-found 0.3ubuntu17.04.1 in ubuntu zesty PROPOSED
Build started on bos01-arm64-042 and finished taking 2 minutes — see the log
[FULLYBUILT] arm64 build of command-not-found 0.3ubuntu17.04.1 in ubuntu zesty PROPOSED
Build started on bos01-arm64-042 and finished taking 2 minutes — see the log
[FULLYBUILT] amd64 build of command-not-found 0.3ubuntu17.04.1 in ubuntu zesty PROPOSED
Build started on lgw01-16 and finished taking 2 minutes — see the log
[FULLYBUILT] amd64 build of command-not-found 0.3ubuntu17.04.1 in ubuntu zesty PROPOSED
Build started on lgw01-16 and finished taking 2 minutes — see the log
[FULLYBUILT] s390x build of command-not-found 0.3ubuntu17.04.0 in ubuntu zesty PROPOSED
Build started on z13-027 and finished taking 7 minutes — see the log
[FULLYBUILT] s390x build of command-not-found 0.3ubuntu17.04.0 in ubuntu zesty PROPOSED
Build started on z13-027 and finished taking 7 minutes — see the log
[FULLYBUILT] ppc64el build of command-not-found 0.3ubuntu17.04.0 in ubuntu zesty PROPOSED
Build started on bos01-ppc64el-009 and finished taking 2 minutes — see the log
[FULLYBUILT] ppc64el build of command-not-found 0.3ubuntu17.04.0 in ubuntu zesty PROPOSED
Build started on bos01-ppc64el-009 and finished taking 2 minutes — see the log
[FULLYBUILT] powerpc build of command-not-found 0.3ubuntu17.04.0 in ubuntu zesty PROPOSED
Build started on fisher04 (powerpc) and finished taking 5 minutes — see the log
[FULLYBUILT] powerpc build of command-not-found 0.3ubuntu17.04.0 in ubuntu zesty PROPOSED
Build started on fisher04 (powerpc) and finished taking 5 minutes — see the log
[FULLYBUILT] i386 build of command-not-found 0.3ubuntu17.04.0 in ubuntu zesty PROPOSED
Build started on lgw01-35 and finished taking 3 minutes — see the log
[FULLYBUILT] i386 build of command-not-found 0.3ubuntu17.04.0 in ubuntu zesty PROPOSED
Build started on lgw01-35 and finished taking 3 minutes — see the log
[FULLYBUILT] armhf build of command-not-found 0.3ubuntu17.04.0 in ubuntu zesty PROPOSED
Build started on bos01-arm64-030 and finished taking 3 minutes — see the log
[FULLYBUILT] armhf build of command-not-found 0.3ubuntu17.04.0 in ubuntu zesty PROPOSED
Build started on bos01-arm64-030 and finished taking 3 minutes — see the log
[FULLYBUILT] arm64 build of command-not-found 0.3ubuntu17.04.0 in ubuntu zesty PROPOSED
Build started on bos01-arm64-017 and finished taking 4 minutes — see the log
[FULLYBUILT] arm64 build of command-not-found 0.3ubuntu17.04.0 in ubuntu zesty PROPOSED
Build started on bos01-arm64-017 and finished taking 4 minutes — see the log
[FULLYBUILT] amd64 build of command-not-found 0.3ubuntu17.04.0 in ubuntu zesty PROPOSED
Build started on lgw01-38 and finished taking 4 minutes — see the log
[FULLYBUILT] amd64 build of command-not-found 0.3ubuntu17.04.0 in ubuntu zesty PROPOSED
Build started on lgw01-38 and finished taking 4 minutes — see the log
[FULLYBUILT] s390x build of command-not-found 0.3ubuntu16.10.0 in ubuntu yakkety PROPOSED
Build started on z13-009 and finished taking 3 minutes — see the log
[FULLYBUILT] ppc64el build of command-not-found 0.3ubuntu16.10.0 in ubuntu yakkety PROPOSED
Build started on bos01-ppc64el-018 and finished taking 2 minutes — see the log
[FULLYBUILT] powerpc build of command-not-found 0.3ubuntu16.10.0 in ubuntu yakkety PROPOSED
Build started on denneed04 (powerpc) and finished taking 4 minutes — see the log
[FULLYBUILT] i386 build of command-not-found 0.3ubuntu16.10.0 in ubuntu yakkety PROPOSED
Build started on lgw01-27 and finished taking 2 minutes — see the log
[FULLYBUILT] armhf build of command-not-found 0.3ubuntu16.10.0 in ubuntu yakkety PROPOSED
Build started on kishi08 (highbank) and finished taking 6 minutes — see the log
[FULLYBUILT] arm64 build of command-not-found 0.3ubuntu16.10.0 in ubuntu yakkety PROPOSED
Build started on bos01-arm64-022 and finished taking 2 minutes — see the log
[FULLYBUILT] amd64 build of command-not-found 0.3ubuntu16.10.0 in ubuntu yakkety PROPOSED
Build started on lgw01-38 and finished taking 2 minutes — see the log
1 → 45 of 45 results First • Previous • Next • Last