Builds for pykcs11 in Ubuntu Noble

154 of 54 results
[FULLYBUILT] s390x build of pykcs11 1.5.14-1build1 in ubuntu noble PROPOSED
Build started on bos01-s390x-017 and finished taking 4 minutes — see the log
[FULLYBUILT] s390x build of pykcs11 1.5.14-1build1 in ubuntu noble PROPOSED
Build started on bos01-s390x-017 and finished taking 4 minutes — see the log
[FULLYBUILT] riscv64 build of pykcs11 1.5.14-1build1 in ubuntu noble PROPOSED
Build started on bos03-riscv64-114 and finished taking 23 minutes — see the log
[FULLYBUILT] riscv64 build of pykcs11 1.5.14-1build1 in ubuntu noble PROPOSED
Build started on bos03-riscv64-114 and finished taking 23 minutes — see the log
[FULLYBUILT] ppc64el build of pykcs11 1.5.14-1build1 in ubuntu noble PROPOSED
Build started on bos01-ppc64el-012 and finished taking 4 minutes — see the log
[FULLYBUILT] ppc64el build of pykcs11 1.5.14-1build1 in ubuntu noble PROPOSED
Build started on bos01-ppc64el-012 and finished taking 4 minutes — see the log
[FULLYBUILT] armhf build of pykcs11 1.5.14-1build1 in ubuntu noble PROPOSED
Build started on bos01-arm64-037 and finished taking 3 minutes — see the log
[FULLYBUILT] armhf build of pykcs11 1.5.14-1build1 in ubuntu noble PROPOSED
Build started on bos01-arm64-037 and finished taking 3 minutes — see the log
[FULLYBUILT] arm64 build of pykcs11 1.5.14-1build1 in ubuntu noble PROPOSED
Build started on bos01-arm64-039 and finished taking 3 minutes — see the log
[FULLYBUILT] arm64 build of pykcs11 1.5.14-1build1 in ubuntu noble PROPOSED
Build started on bos01-arm64-039 and finished taking 3 minutes — see the log
[FULLYBUILT] amd64 build of pykcs11 1.5.14-1build1 in ubuntu noble PROPOSED
Build started on lcy02-amd64-003 and finished taking 2 minutes — see the log
[FULLYBUILT] amd64 build of pykcs11 1.5.14-1build1 in ubuntu noble PROPOSED
Build started on lcy02-amd64-003 and finished taking 2 minutes — see the log
[FULLYBUILT] s390x build of pykcs11 1.5.14-1 in ubuntu noble PROPOSED
Build started on bos02-s390x-004 and finished taking 5 minutes — see the log
[FULLYBUILT] s390x build of pykcs11 1.5.14-1 in ubuntu noble PROPOSED
Build started on bos02-s390x-004 and finished taking 5 minutes — see the log
[FULLYBUILT] riscv64 build of pykcs11 1.5.14-1 in ubuntu noble PROPOSED
Build started on bos03-riscv64-020 and finished taking 24 minutes — see the log
[FULLYBUILT] riscv64 build of pykcs11 1.5.14-1 in ubuntu noble PROPOSED
Build started on bos03-riscv64-020 and finished taking 24 minutes — see the log
[FULLYBUILT] ppc64el build of pykcs11 1.5.14-1 in ubuntu noble PROPOSED
Build started on bos01-ppc64el-009 and finished taking 4 minutes — see the log
[FULLYBUILT] ppc64el build of pykcs11 1.5.14-1 in ubuntu noble PROPOSED
Build started on bos01-ppc64el-009 and finished taking 4 minutes — see the log
[FULLYBUILT] armhf build of pykcs11 1.5.14-1 in ubuntu noble PROPOSED
Build started on bos02-arm64-060 and finished taking 8 minutes — see the log
[FULLYBUILT] armhf build of pykcs11 1.5.14-1 in ubuntu noble PROPOSED
Build started on bos02-arm64-060 and finished taking 8 minutes — see the log
[FULLYBUILT] arm64 build of pykcs11 1.5.14-1 in ubuntu noble PROPOSED
Build started on bos02-arm64-040 and finished taking 10 minutes — see the log
[FULLYBUILT] arm64 build of pykcs11 1.5.14-1 in ubuntu noble PROPOSED
Build started on bos02-arm64-040 and finished taking 10 minutes — see the log
[FULLYBUILT] amd64 build of pykcs11 1.5.14-1 in ubuntu noble PROPOSED
Build started on lcy02-amd64-091 and finished taking 3 minutes — see the log
[FULLYBUILT] amd64 build of pykcs11 1.5.14-1 in ubuntu noble PROPOSED
Build started on lcy02-amd64-091 and finished taking 3 minutes — see the log
[FULLYBUILT] s390x build of pykcs11 1.5.13-1 in ubuntu noble PROPOSED
Build started on bos02-s390x-010 and finished taking 5 minutes — see the log
[FULLYBUILT] s390x build of pykcs11 1.5.13-1 in ubuntu noble PROPOSED
Build started on bos02-s390x-010 and finished taking 5 minutes — see the log
[FULLYBUILT] riscv64 build of pykcs11 1.5.13-1 in ubuntu noble PROPOSED
Build started on bos03-riscv64-057 and finished taking 24 minutes — see the log
[FULLYBUILT] riscv64 build of pykcs11 1.5.13-1 in ubuntu noble PROPOSED
Build started on bos03-riscv64-057 and finished taking 24 minutes — see the log
[FULLYBUILT] ppc64el build of pykcs11 1.5.13-1 in ubuntu noble PROPOSED
Build started on bos01-ppc64el-001 and finished taking 4 minutes — see the log
[FULLYBUILT] ppc64el build of pykcs11 1.5.13-1 in ubuntu noble PROPOSED
Build started on bos01-ppc64el-001 and finished taking 4 minutes — see the log
[FULLYBUILT] armhf build of pykcs11 1.5.13-1 in ubuntu noble PROPOSED
Build started on bos02-arm64-008 and finished taking 7 minutes — see the log
[FULLYBUILT] armhf build of pykcs11 1.5.13-1 in ubuntu noble PROPOSED
Build started on bos02-arm64-008 and finished taking 7 minutes — see the log
[FULLYBUILT] arm64 build of pykcs11 1.5.13-1 in ubuntu noble PROPOSED
Build started on bos02-arm64-021 and finished taking 9 minutes — see the log
[FULLYBUILT] arm64 build of pykcs11 1.5.13-1 in ubuntu noble PROPOSED
Build started on bos02-arm64-021 and finished taking 9 minutes — see the log
[FULLYBUILT] amd64 build of pykcs11 1.5.13-1 in ubuntu noble PROPOSED
Build started on lcy02-amd64-027 and finished taking 3 minutes — see the log
[FULLYBUILT] amd64 build of pykcs11 1.5.13-1 in ubuntu noble PROPOSED
Build started on lcy02-amd64-027 and finished taking 3 minutes — see the log
[FULLYBUILT] s390x build of pykcs11 1.5.12-2build1 in ubuntu noble PROPOSED
Build started on bos01-s390x-011 and finished taking 5 minutes — see the log
[FULLYBUILT] s390x build of pykcs11 1.5.12-2build1 in ubuntu noble PROPOSED
Build started on bos01-s390x-011 and finished taking 5 minutes — see the log
[FULLYBUILT] riscv64 build of pykcs11 1.5.12-2build1 in ubuntu noble PROPOSED
Build started on riscv64-qemu-lgw01-005 and finished taking 45 minutes — see the log
[FULLYBUILT] riscv64 build of pykcs11 1.5.12-2build1 in ubuntu noble PROPOSED
Build started on riscv64-qemu-lgw01-005 and finished taking 45 minutes — see the log
[FULLYBUILT] ppc64el build of pykcs11 1.5.12-2build1 in ubuntu noble PROPOSED
Build started on bos02-ppc64el-029 and finished taking 5 minutes — see the log
[FULLYBUILT] ppc64el build of pykcs11 1.5.12-2build1 in ubuntu noble PROPOSED
Build started on bos02-ppc64el-029 and finished taking 5 minutes — see the log
[FULLYBUILT] armhf build of pykcs11 1.5.12-2build1 in ubuntu noble PROPOSED
Build started on bos02-arm64-032 and finished taking 8 minutes — see the log
[FULLYBUILT] armhf build of pykcs11 1.5.12-2build1 in ubuntu noble PROPOSED
Build started on bos02-arm64-032 and finished taking 8 minutes — see the log
[FULLYBUILT] arm64 build of pykcs11 1.5.12-2build1 in ubuntu noble PROPOSED
Build started on bos02-arm64-030 and finished taking 9 minutes — see the log
[FULLYBUILT] arm64 build of pykcs11 1.5.12-2build1 in ubuntu noble PROPOSED
Build started on bos02-arm64-030 and finished taking 9 minutes — see the log
[FULLYBUILT] amd64 build of pykcs11 1.5.12-2build1 in ubuntu noble PROPOSED
Build started on lcy02-amd64-038 and finished taking 4 minutes — see the log
[FULLYBUILT] amd64 build of pykcs11 1.5.12-2build1 in ubuntu noble PROPOSED
Build started on lcy02-amd64-038 and finished taking 4 minutes — see the log
[FULLYBUILT] s390x build of pykcs11 1.5.12-2 in ubuntu mantic PROPOSED
Build started on bos02-s390x-001 and finished taking 3 minutes — see the log
[FULLYBUILT] riscv64 build of pykcs11 1.5.12-2 in ubuntu mantic PROPOSED
Build started on riscv64-qemu-lgw01-065 and finished taking 24 minutes — see the log
[FULLYBUILT] ppc64el build of pykcs11 1.5.12-2 in ubuntu mantic PROPOSED
Build started on bos02-ppc64el-005 and finished taking 10 minutes — see the log
[FULLYBUILT] armhf build of pykcs11 1.5.12-2 in ubuntu mantic PROPOSED
Build started on bos02-arm64-076 and finished taking 9 minutes — see the log
[FULLYBUILT] arm64 build of pykcs11 1.5.12-2 in ubuntu mantic PROPOSED
Build started on bos02-arm64-008 and finished taking 10 minutes — see the log
[FULLYBUILT] amd64 build of pykcs11 1.5.12-2 in ubuntu mantic PROPOSED
Build started on lcy02-amd64-029 and finished taking 2 minutes — see the log
154 of 54 results