| 2022-10-19 00:35:28 |
Haw Loeung |
bug |
|
|
added bug |
| 2022-10-19 00:35:39 |
Haw Loeung |
bug |
|
|
added subscriber The Canonical Sysadmins |
| 2022-10-19 00:35:47 |
Haw Loeung |
summary |
charm build - exclude i386 and armhf |
charm build - exclude i386 and armhf architectures |
|
| 2022-10-19 02:06:50 |
niphon.npy |
bug |
|
|
added subscriber niphon.npy |
| 2022-10-19 02:06:57 |
niphon.npy |
removed subscriber niphon.npy |
|
|
|
| 2022-10-19 02:07:06 |
niphon.npy |
bug |
|
|
added subscriber niphon.npy |
| 2022-10-19 02:07:14 |
niphon.npy |
removed subscriber niphon.npy |
|
|
|
| 2022-10-19 16:20:36 |
Haw Loeung |
description |
Hi,
I've just set up a new charm recipe for the autocert charm. When requesting a build, the i386 and armhf builds fail. It isn't just a specific series, but for all:
kinetic - https://launchpad.net/~autocert-charmers/autocert-charm/+charm/autocert/+build/4232/+files/buildlog_charm_ubuntu_kinetic_i386_autocert_BU
ILDING.txt.gz
xenial - https://launchpad.net/~autocert-charmers/autocert-charm/+charm/autocert/+build/4209/+files/buildlog_charm_ubuntu_xenial_i386_autocert_BUI
LDING.txt.gz
bionic - https://launchpad.net/~autocert-charmers/autocert-charm/+charm/autocert/+build/4215/+files/buildlog_charm_ubuntu_bionic_i386_autocert_BUI
LDING.txt.gz
jammy - https://launchpad.net/~autocert-charmers/autocert-charm/+charm/autocert/+build/4226/+files/buildlog_charm_ubuntu_jammy_i386_autocert_BUIL
DING.txt.gz
focal - https://launchpad.net/~autocert-charmers/autocert-charm/+charm/autocert/+build/4221/+files/buildlog_charm_ubuntu_focal_amd64_autocert_BUI
LDING.txt.gz
Looking at the build logs, for i386, it's failing on the "charmcraft" snap not supporting this architecture:
"""
error: snap "charmcraft" is not available on stable for this architecture
(i386) but exists on other architectures (amd64, arm64, armhf, ppc64el,
s390x).
"""
For armhf:
xenial - https://launchpad.net/~autocert-charmers/autocert-charm/+charm/autocert/+build/4211/+files/buildlog_charm_ubuntu_xenial_armhf_autocert_BU
ILDING.txt.gz
focal - https://launchpad.net/~autocert-charmers/autocert-charm/+charm/autocert/+build/4222/+files/buildlog_charm_ubuntu_focal_armhf_autocert_BUI
LDING.txt.gz
jammy - https://launchpad.net/~autocert-charmers/autocert-charm/+charm/autocert/+build/4228/+files/buildlog_charm_ubuntu_jammy_armhf_autocert_BUI
LDING.txt.gz
kinetic - https://launchpad.net/~autocert-charmers/autocert-charm/+charm/autocert/+build/4234/+files/buildlog_charm_ubuntu_kinetic_armhf_autocert_B
UILDING.txt.gz
That's failing because of the "charm" snap:
"""
Parts processing error: Error installing snap 'charm' from channel 'latest/stable'.
"""
Can we exclude these two architectures by default to avoid the noisy fail to build emails? Also the unnecessary bump in revnos when publishing to the charm store? |
Hi,
I've just set up a new charm recipe for the autocert charm. When requesting a build, the i386 and armhf builds fail. It isn't just a specific series, but for all:
kinetic - https://launchpad.net/~autocert-charmers/autocert-charm/+charm/autocert/+build/4232/+files/buildlog_charm_ubuntu_kinetic_i386_autocert_BUILDING.txt.gz
xenial - https://launchpad.net/~autocert-charmers/autocert-charm/+charm/autocert/+build/4209/+files/buildlog_charm_ubuntu_xenial_i386_autocert_BUILDING.txt.gz
bionic - https://launchpad.net/~autocert-charmers/autocert-charm/+charm/autocert/+build/4215/+files/buildlog_charm_ubuntu_bionic_i386_autocert_BUILDING.txt.gz
jammy - https://launchpad.net/~autocert-charmers/autocert-charm/+charm/autocert/+build/4226/+files/buildlog_charm_ubuntu_jammy_i386_autocert_BUILDING.txt.gz
focal - https://launchpad.net/~autocert-charmers/autocert-charm/+charm/autocert/+build/4221/+files/buildlog_charm_ubuntu_focal_amd64_autocert_BUILDING.txt.gz
Looking at the build logs, for i386, it's failing on the "charmcraft" snap not supporting this architecture:
"""
error: snap "charmcraft" is not available on stable for this architecture
(i386) but exists on other architectures (amd64, arm64, armhf, ppc64el,
s390x).
"""
For armhf:
xenial - https://launchpad.net/~autocert-charmers/autocert-charm/+charm/autocert/+build/4211/+files/buildlog_charm_ubuntu_xenial_armhf_autocert_BUILDING.txt.gz
focal - https://launchpad.net/~autocert-charmers/autocert-charm/+charm/autocert/+build/4222/+files/buildlog_charm_ubuntu_focal_armhf_autocert_BUILDING.txt.gz
jammy - https://launchpad.net/~autocert-charmers/autocert-charm/+charm/autocert/+build/4228/+files/buildlog_charm_ubuntu_jammy_armhf_autocert_BUILDING.txt.gz
kinetic - https://launchpad.net/~autocert-charmers/autocert-charm/+charm/autocert/+build/4234/+files/buildlog_charm_ubuntu_kinetic_armhf_autocert_BUILDING.txt.gz
That's failing because of the "charm" snap:
"""
Parts processing error: Error installing snap 'charm' from channel 'latest/stable'.
"""
Can we exclude these two architectures by default to avoid the noisy fail to build emails? Also the unnecessary bump in revnos when publishing to the charm store? |
|
| 2022-10-20 07:09:44 |
Guruprasad |
tags |
|
buildd-manager |
|
| 2022-10-21 04:40:04 |
Haw Loeung |
description |
Hi,
I've just set up a new charm recipe for the autocert charm. When requesting a build, the i386 and armhf builds fail. It isn't just a specific series, but for all:
kinetic - https://launchpad.net/~autocert-charmers/autocert-charm/+charm/autocert/+build/4232/+files/buildlog_charm_ubuntu_kinetic_i386_autocert_BUILDING.txt.gz
xenial - https://launchpad.net/~autocert-charmers/autocert-charm/+charm/autocert/+build/4209/+files/buildlog_charm_ubuntu_xenial_i386_autocert_BUILDING.txt.gz
bionic - https://launchpad.net/~autocert-charmers/autocert-charm/+charm/autocert/+build/4215/+files/buildlog_charm_ubuntu_bionic_i386_autocert_BUILDING.txt.gz
jammy - https://launchpad.net/~autocert-charmers/autocert-charm/+charm/autocert/+build/4226/+files/buildlog_charm_ubuntu_jammy_i386_autocert_BUILDING.txt.gz
focal - https://launchpad.net/~autocert-charmers/autocert-charm/+charm/autocert/+build/4221/+files/buildlog_charm_ubuntu_focal_amd64_autocert_BUILDING.txt.gz
Looking at the build logs, for i386, it's failing on the "charmcraft" snap not supporting this architecture:
"""
error: snap "charmcraft" is not available on stable for this architecture
(i386) but exists on other architectures (amd64, arm64, armhf, ppc64el,
s390x).
"""
For armhf:
xenial - https://launchpad.net/~autocert-charmers/autocert-charm/+charm/autocert/+build/4211/+files/buildlog_charm_ubuntu_xenial_armhf_autocert_BUILDING.txt.gz
focal - https://launchpad.net/~autocert-charmers/autocert-charm/+charm/autocert/+build/4222/+files/buildlog_charm_ubuntu_focal_armhf_autocert_BUILDING.txt.gz
jammy - https://launchpad.net/~autocert-charmers/autocert-charm/+charm/autocert/+build/4228/+files/buildlog_charm_ubuntu_jammy_armhf_autocert_BUILDING.txt.gz
kinetic - https://launchpad.net/~autocert-charmers/autocert-charm/+charm/autocert/+build/4234/+files/buildlog_charm_ubuntu_kinetic_armhf_autocert_BUILDING.txt.gz
That's failing because of the "charm" snap:
"""
Parts processing error: Error installing snap 'charm' from channel 'latest/stable'.
"""
Can we exclude these two architectures by default to avoid the noisy fail to build emails? Also the unnecessary bump in revnos when publishing to the charm store? |
Hi,
I've just set up a new charm recipe for the autocert charm. When requesting a build, the i386 and armhf builds fail. It isn't just a specific series, but for all:
kinetic - https://launchpad.net/~autocert-charmers/autocert-charm/+charm/autocert/+build/4232/+files/buildlog_charm_ubuntu_kinetic_i386_autocert_BUILDING.txt.gz
xenial - https://launchpad.net/~autocert-charmers/autocert-charm/+charm/autocert/+build/4209/+files/buildlog_charm_ubuntu_xenial_i386_autocert_BUILDING.txt.gz
bionic - https://launchpad.net/~autocert-charmers/autocert-charm/+charm/autocert/+build/4215/+files/buildlog_charm_ubuntu_bionic_i386_autocert_BUILDING.txt.gz
jammy - https://launchpad.net/~autocert-charmers/autocert-charm/+charm/autocert/+build/4226/+files/buildlog_charm_ubuntu_jammy_i386_autocert_BUILDING.txt.gz
focal - https://launchpad.net/~autocert-charmers/autocert-charm/+charm/autocert/+build/4221/+files/buildlog_charm_ubuntu_focal_amd64_autocert_BUILDING.txt.gz
Looking at the build logs, for i386, it's failing on the "charmcraft" snap not supporting this architecture:
"""
error: snap "charmcraft" is not available on stable for this architecture
(i386) but exists on other architectures (amd64, arm64, armhf, ppc64el,
s390x).
"""
For armhf:
xenial - https://launchpad.net/~autocert-charmers/autocert-charm/+charm/autocert/+build/4211/+files/buildlog_charm_ubuntu_xenial_armhf_autocert_BUILDING.txt.gz
focal - https://launchpad.net/~autocert-charmers/autocert-charm/+charm/autocert/+build/4222/+files/buildlog_charm_ubuntu_focal_armhf_autocert_BUILDING.txt.gz
jammy - https://launchpad.net/~autocert-charmers/autocert-charm/+charm/autocert/+build/4228/+files/buildlog_charm_ubuntu_jammy_armhf_autocert_BUILDING.txt.gz
kinetic - https://launchpad.net/~autocert-charmers/autocert-charm/+charm/autocert/+build/4234/+files/buildlog_charm_ubuntu_kinetic_armhf_autocert_BUILDING.txt.gz
That's failing because of the "charm" snap:
"""
Parts processing error: Error installing snap 'charm' from channel 'latest/stable'.
"""
Can we exclude these two architectures by default to avoid the noisy fail to build emails? |
|
| 2022-10-21 08:31:57 |
Colin Watson |
tags |
buildd-manager |
lp-charms |
|
| 2022-10-21 08:32:02 |
Colin Watson |
launchpad: status |
New |
Triaged |
|
| 2022-10-21 08:32:05 |
Colin Watson |
launchpad: importance |
Undecided |
Low |
|
