Ubuntu
command-not-found package

Builds for command-not-found in Ubuntu Xenial

  1. Xenial (16.04)
  2. Builds
1 → 75 of 77 results First • Previous • • Last
[FULLYBUILT] s390x build of command-not-found 0.3ubuntu16.04.2 in ubuntu xenial PROPOSED
Build started on z13-002 and finished taking 2 minutes — see the log
[FULLYBUILT] s390x build of command-not-found 0.3ubuntu16.04.2 in ubuntu xenial PROPOSED
Build started on z13-002 and finished taking 2 minutes — see the log
[FULLYBUILT] ppc64el build of command-not-found 0.3ubuntu16.04.2 in ubuntu xenial PROPOSED
Build started on bos01-ppc64el-012 and finished taking 1 minute — see the log
[FULLYBUILT] ppc64el build of command-not-found 0.3ubuntu16.04.2 in ubuntu xenial PROPOSED
Build started on bos01-ppc64el-012 and finished taking 1 minute — see the log
[FULLYBUILT] powerpc build of command-not-found 0.3ubuntu16.04.2 in ubuntu xenial PROPOSED
Build started on denneed02 (powerpc) and finished taking 4 minutes — see the log
[FULLYBUILT] powerpc build of command-not-found 0.3ubuntu16.04.2 in ubuntu xenial PROPOSED
Build started on denneed02 (powerpc) and finished taking 4 minutes — see the log
[FULLYBUILT] i386 build of command-not-found 0.3ubuntu16.04.2 in ubuntu xenial PROPOSED
Build started on lcy01-23 and finished taking 2 minutes — see the log
[FULLYBUILT] i386 build of command-not-found 0.3ubuntu16.04.2 in ubuntu xenial PROPOSED
Build started on lcy01-23 and finished taking 2 minutes — see the log
[FULLYBUILT] armhf build of command-not-found 0.3ubuntu16.04.2 in ubuntu xenial PROPOSED
Build started on kishi19 (highbank) and finished taking 5 minutes — see the log
[FULLYBUILT] armhf build of command-not-found 0.3ubuntu16.04.2 in ubuntu xenial PROPOSED
Build started on kishi19 (highbank) and finished taking 5 minutes — see the log
[FULLYBUILT] arm64 build of command-not-found 0.3ubuntu16.04.2 in ubuntu xenial PROPOSED
Build started on bos01-arm64-008 and finished taking 9 minutes — see the log
[FULLYBUILT] arm64 build of command-not-found 0.3ubuntu16.04.2 in ubuntu xenial PROPOSED
Build started on bos01-arm64-008 and finished taking 9 minutes — see the log
[FULLYBUILT] amd64 build of command-not-found 0.3ubuntu16.04.2 in ubuntu xenial PROPOSED
Build started on lcy01-11 and finished taking 4 minutes — see the log
[FULLYBUILT] amd64 build of command-not-found 0.3ubuntu16.04.2 in ubuntu xenial PROPOSED
Build started on lcy01-11 and finished taking 4 minutes — see the log
[FULLYBUILT] s390x build of command-not-found 0.3ubuntu16.04.1 in ubuntu xenial PROPOSED
Build started on z13-018 and finished taking 1 minute — see the log
[FULLYBUILT] s390x build of command-not-found 0.3ubuntu16.04.1 in ubuntu xenial PROPOSED
Build started on z13-018 and finished taking 1 minute — see the log
[FULLYBUILT] ppc64el build of command-not-found 0.3ubuntu16.04.1 in ubuntu xenial PROPOSED
Build started on bos01-ppc64el-029 and finished taking 1 minute — see the log
[FULLYBUILT] ppc64el build of command-not-found 0.3ubuntu16.04.1 in ubuntu xenial PROPOSED
Build started on bos01-ppc64el-029 and finished taking 1 minute — see the log
[FULLYBUILT] powerpc build of command-not-found 0.3ubuntu16.04.1 in ubuntu xenial PROPOSED
Build started on denneed04 (powerpc) and finished taking 2 minutes — see the log
[FULLYBUILT] powerpc build of command-not-found 0.3ubuntu16.04.1 in ubuntu xenial PROPOSED
Build started on denneed04 (powerpc) and finished taking 2 minutes — see the log
[FULLYBUILT] i386 build of command-not-found 0.3ubuntu16.04.1 in ubuntu xenial PROPOSED
Build started on lgw01-37 and finished taking 2 minutes — see the log
[FULLYBUILT] i386 build of command-not-found 0.3ubuntu16.04.1 in ubuntu xenial PROPOSED
Build started on lgw01-37 and finished taking 2 minutes — see the log
[FULLYBUILT] armhf build of command-not-found 0.3ubuntu16.04.1 in ubuntu xenial PROPOSED
Build started on kishi10 (highbank) and finished taking 4 minutes — see the log
[FULLYBUILT] armhf build of command-not-found 0.3ubuntu16.04.1 in ubuntu xenial PROPOSED
Build started on kishi10 (highbank) and finished taking 4 minutes — see the log
[FULLYBUILT] arm64 build of command-not-found 0.3ubuntu16.04.1 in ubuntu xenial PROPOSED
Build started on magic (arm64) and finished taking 3 minutes — see the log
[FULLYBUILT] arm64 build of command-not-found 0.3ubuntu16.04.1 in ubuntu xenial PROPOSED
Build started on magic (arm64) and finished taking 3 minutes — see the log
[FULLYBUILT] amd64 build of command-not-found 0.3ubuntu16.04.1 in ubuntu xenial PROPOSED
Build started on lgw01-58 and finished taking 1 minute — see the log
[FULLYBUILT] amd64 build of command-not-found 0.3ubuntu16.04.1 in ubuntu xenial PROPOSED
Build started on lgw01-58 and finished taking 1 minute — see the log
[FULLYBUILT] s390x build of command-not-found 0.3ubuntu16.04 in ubuntu xenial PROPOSED
Build started on z13-022 and finished taking 7 minutes — see the log
[FULLYBUILT] s390x build of command-not-found 0.3ubuntu16.04 in ubuntu xenial PROPOSED
Build started on z13-022 and finished taking 7 minutes — see the log
[FULLYBUILT] ppc64el build of command-not-found 0.3ubuntu16.04 in ubuntu xenial PROPOSED
Build started on bos01-ppc64el-016 and finished taking 2 minutes — see the log
[FULLYBUILT] ppc64el build of command-not-found 0.3ubuntu16.04 in ubuntu xenial PROPOSED
Build started on bos01-ppc64el-016 and finished taking 2 minutes — see the log
[FULLYBUILT] powerpc build of command-not-found 0.3ubuntu16.04 in ubuntu xenial PROPOSED
Build started on fisher02 (powerpc) and finished taking 5 minutes — see the log
[FULLYBUILT] powerpc build of command-not-found 0.3ubuntu16.04 in ubuntu xenial PROPOSED
Build started on fisher02 (powerpc) and finished taking 5 minutes — see the log
[FULLYBUILT] i386 build of command-not-found 0.3ubuntu16.04 in ubuntu xenial PROPOSED
Build started on lgw01-49 and finished taking 4 minutes — see the log
[FULLYBUILT] i386 build of command-not-found 0.3ubuntu16.04 in ubuntu xenial PROPOSED
Build started on lgw01-49 and finished taking 4 minutes — see the log
[FULLYBUILT] armhf build of command-not-found 0.3ubuntu16.04 in ubuntu xenial PROPOSED
Build started on kishi17 (highbank) and finished taking 9 minutes — see the log
[FULLYBUILT] armhf build of command-not-found 0.3ubuntu16.04 in ubuntu xenial PROPOSED
Build started on kishi17 (highbank) and finished taking 9 minutes — see the log
[FULLYBUILT] arm64 build of command-not-found 0.3ubuntu16.04 in ubuntu xenial PROPOSED
Build started on twombly (arm64) and finished taking 9 minutes — see the log
[FULLYBUILT] arm64 build of command-not-found 0.3ubuntu16.04 in ubuntu xenial PROPOSED
Build started on twombly (arm64) and finished taking 9 minutes — see the log
[FULLYBUILT] amd64 build of command-not-found 0.3ubuntu16.04 in ubuntu xenial PROPOSED
Build started on lgw01-59 and finished taking 4 minutes — see the log
[FULLYBUILT] amd64 build of command-not-found 0.3ubuntu16.04 in ubuntu xenial PROPOSED
Build started on lgw01-59 and finished taking 4 minutes — see the log
[FULLYBUILT] s390x build of command-not-found 0.3ubuntu16.04~pre2 in ubuntu xenial PROPOSED
Build started on z13-019 and finished taking 2 minutes — see the log
[FULLYBUILT] s390x build of command-not-found 0.3ubuntu16.04~pre2 in ubuntu xenial PROPOSED
Build started on z13-019 and finished taking 2 minutes — see the log
[FULLYBUILT] ppc64el build of command-not-found 0.3ubuntu16.04~pre2 in ubuntu xenial PROPOSED
Build started on bos01-ppc64el-023 and finished taking 2 minutes — see the log
[FULLYBUILT] ppc64el build of command-not-found 0.3ubuntu16.04~pre2 in ubuntu xenial PROPOSED
Build started on bos01-ppc64el-023 and finished taking 2 minutes — see the log
[FULLYBUILT] powerpc build of command-not-found 0.3ubuntu16.04~pre2 in ubuntu xenial PROPOSED
Build started on denneed01 (powerpc) and finished taking 5 minutes — see the log
[FULLYBUILT] powerpc build of command-not-found 0.3ubuntu16.04~pre2 in ubuntu xenial PROPOSED
Build started on denneed01 (powerpc) and finished taking 5 minutes — see the log
[FULLYBUILT] i386 build of command-not-found 0.3ubuntu16.04~pre2 in ubuntu xenial PROPOSED
Build started on lgw01-59 and finished taking 2 minutes — see the log
[FULLYBUILT] i386 build of command-not-found 0.3ubuntu16.04~pre2 in ubuntu xenial PROPOSED
Build started on lgw01-59 and finished taking 2 minutes — see the log
[FULLYBUILT] armhf build of command-not-found 0.3ubuntu16.04~pre2 in ubuntu xenial PROPOSED
Build started on kishi10 (highbank) and finished taking 7 minutes — see the log
[FULLYBUILT] armhf build of command-not-found 0.3ubuntu16.04~pre2 in ubuntu xenial PROPOSED
Build started on kishi10 (highbank) and finished taking 7 minutes — see the log
[FULLYBUILT] arm64 build of command-not-found 0.3ubuntu16.04~pre2 in ubuntu xenial PROPOSED
Build started on bos01-arm64-006 and finished taking 5 minutes — see the log
[FULLYBUILT] arm64 build of command-not-found 0.3ubuntu16.04~pre2 in ubuntu xenial PROPOSED
Build started on bos01-arm64-006 and finished taking 5 minutes — see the log
[FULLYBUILT] amd64 build of command-not-found 0.3ubuntu16.04~pre2 in ubuntu xenial PROPOSED
Build started on lgw01-56 and finished taking 3 minutes — see the log
[FULLYBUILT] amd64 build of command-not-found 0.3ubuntu16.04~pre2 in ubuntu xenial PROPOSED
Build started on lgw01-56 and finished taking 3 minutes — see the log
[FULLYBUILT] s390x build of command-not-found 0.3ubuntu16.04~pre1 in ubuntu xenial PROPOSED
Build started on z13-019 and finished taking 2 minutes — see the log
[FULLYBUILT] s390x build of command-not-found 0.3ubuntu16.04~pre1 in ubuntu xenial PROPOSED
Build started on z13-019 and finished taking 2 minutes — see the log
[FULLYBUILT] ppc64el build of command-not-found 0.3ubuntu16.04~pre1 in ubuntu xenial PROPOSED
Build started on bos01-ppc64el-022 and finished taking 2 minutes — see the log
[FULLYBUILT] ppc64el build of command-not-found 0.3ubuntu16.04~pre1 in ubuntu xenial PROPOSED
Build started on bos01-ppc64el-022 and finished taking 2 minutes — see the log
[FULLYBUILT] powerpc build of command-not-found 0.3ubuntu16.04~pre1 in ubuntu xenial PROPOSED
Build started on denneed04 (powerpc) and finished taking 4 minutes — see the log
[FULLYBUILT] powerpc build of command-not-found 0.3ubuntu16.04~pre1 in ubuntu xenial PROPOSED
Build started on denneed04 (powerpc) and finished taking 4 minutes — see the log
[FULLYBUILT] i386 build of command-not-found 0.3ubuntu16.04~pre1 in ubuntu xenial PROPOSED
Build started on lcy01-14 and finished taking 2 minutes — see the log
[FULLYBUILT] i386 build of command-not-found 0.3ubuntu16.04~pre1 in ubuntu xenial PROPOSED
Build started on lcy01-14 and finished taking 2 minutes — see the log
[FULLYBUILT] armhf build of command-not-found 0.3ubuntu16.04~pre1 in ubuntu xenial PROPOSED
Build started on kishi05 (highbank) and finished taking 7 minutes — see the log
[FULLYBUILT] armhf build of command-not-found 0.3ubuntu16.04~pre1 in ubuntu xenial PROPOSED
Build started on kishi05 (highbank) and finished taking 7 minutes — see the log
[FULLYBUILT] arm64 build of command-not-found 0.3ubuntu16.04~pre1 in ubuntu xenial PROPOSED
Build started on magic (arm64) and finished taking 7 minutes — see the log
[FULLYBUILT] arm64 build of command-not-found 0.3ubuntu16.04~pre1 in ubuntu xenial PROPOSED
Build started on magic (arm64) and finished taking 7 minutes — see the log
[FULLYBUILT] amd64 build of command-not-found 0.3ubuntu16.04~pre1 in ubuntu xenial PROPOSED
Build started on lcy01-09 and finished taking 3 minutes — see the log
[FULLYBUILT] amd64 build of command-not-found 0.3ubuntu16.04~pre1 in ubuntu xenial PROPOSED
Build started on lcy01-09 and finished taking 3 minutes — see the log
[FULLYBUILT] s390x build of command-not-found 0.3ubuntu15.10.1 in ubuntu xenial RELEASE
Build started on z13-019 and finished taking 2 minutes — see the log
[FULLYBUILT] ppc64el build of command-not-found 0.3ubuntu15.10.1 in ubuntu wily PROPOSED
Build started on fisher04 (powerpc) and finished taking 3 minutes — see the log
[FULLYBUILT] powerpc build of command-not-found 0.3ubuntu15.10.1 in ubuntu wily PROPOSED
Build started on sagari (powerpc) and finished taking 4 minutes — see the log
[FULLYBUILT] i386 build of command-not-found 0.3ubuntu15.10.1 in ubuntu wily PROPOSED
Build started on lgw01-17 and finished taking 2 minutes — see the log
[FULLYBUILT] armhf build of command-not-found 0.3ubuntu15.10.1 in ubuntu wily PROPOSED
Build started on kishi12 (highbank) and finished taking 5 minutes — see the log
1 → 75 of 77 results First • Previous • • Last