| 2017-06-07 11:29:37 |
Sergio Schvezov |
bug |
|
|
added bug |
| 2017-06-07 11:37:54 |
Sergio Schvezov |
branch linked |
|
lp:~sergiusens/click/schroot_configuration_overlay_detection |
|
| 2017-06-07 11:42:35 |
Launchpad Janitor |
branch linked |
|
lp:~ci-train-bot/click/click-ubuntu-artful-2790 |
|
| 2017-06-07 21:35:18 |
Launchpad Janitor |
click (Ubuntu): status |
New |
Fix Released |
|
| 2017-06-09 18:04:38 |
Leo Arias |
description |
The kernel changed the module name from overlayfs to overlay, this needs to be taken into consideration when creating the chroot. |
The kernel changed the module name from overlayfs to overlay, this needs to be taken into consideration when creating the chroot.
[Impact]
When trying to create the chroot, it fails like this:
Processing triggers for sgml-base (1.26+nmu4ubuntu1) ...
E: 10mount: mount: wrong fs type, bad option, bad superblock on click-ubuntu-sdk-14.04-armhf,
E: 10mount: missing codepage or helper program, or other error
E: 10mount:
E: 10mount: In some cases useful info is found in syslog - try
E: 10mount: dmesg | tail or so.
E: click-ubuntu-sdk-14.04-armhf-06293574-400d-48f5-8eb2-b74b8af77b72: Chroot setup failed: stage=setup-start
Command returned 1: schroot -c click-ubuntu-sdk-14.04-armhf -- env DEB_HOST_ARCH_BITS=32 DEB_BUILD_ARCH=amd64 DEB_TARGET_ARCH_ENDIAN=little DEB_BUILD_ARCH_ABI
=base DEB_TARGET_ARCH_BITS=32 DEB_TARGET_ARCH_LIBC=gnu DEB_BUILD_GNU_SYSTEM=linux-gnu DEB_HOST_ARCH_OS=linux DEB_TARGET_MULTIARCH=arm-linux-gnueabihf DEB_TARG
ET_ARCH_OS=linux DEB_HOST_ARCH_LIBC=gnu DEB_BUILD_GNU_TYPE=x86_64-linux-gnu DEB_BUILD_ARCH_OS=linux DEB_TARGET_GNU_SYSTEM=linux-gnueabihf DEB_BUILD_ARCH_BITS=
64 DEB_HOST_ARCH_ABI=eabihf DEB_BUILD_GNU_CPU=x86_64 DEB_BUILD_ARCH_ENDIAN=little DEB_HOST_ARCH=armhf DEB_BUILD_ARCH_LIBC=gnu DEB_TARGET_GNU_TYPE=arm-linux-gn
ueabihf DEB_HOST_MULTIARCH=arm-linux-gnueabihf DEB_TARGET_GNU_CPU=arm DEB_HOST_GNU_TYPE=arm-linux-gnueabihf DEB_HOST_GNU_CPU=arm DEB_TARGET_ARCH_CPU=arm DEB_B
UILD_MULTIARCH=x86_64-linux-gnu DEB_HOST_GNU_SYSTEM=linux-gnueabihf DEB_TARGET_ARCH_ABI=eabihf DEB_TARGET_ARCH=armhf DEB_HOST_ARCH_ENDIAN=little DEB_HOST_ARCH
_CPU=arm DEB_BUILD_ARCH_CPU=amd64 cmake .. -DCLICK_MODE=on -DINSTALL_TESTS=off
ERROR
This makes the autopkgtests fail, so it's blocking #1693226.
[Test Case]
Run the click autopkgtests in artful.
Check that there are no errors related to the wrong fs type.
[Regression Potential]
Fixing this for artful could make it fail in previous versions.
However, this was found by the autopkgtests, so as long as the chroot tests pass in the other revisions the fix is correct.
[Other Info]
Click is now longer in active development. These tests were failing for a long time. In here we are just trying to make a small change on the name of the python module so it doesn't conflict with python3-click which is in active development and needed by snapcraft in #1692102. |
|
| 2017-06-09 18:05:52 |
Leo Arias |
description |
The kernel changed the module name from overlayfs to overlay, this needs to be taken into consideration when creating the chroot.
[Impact]
When trying to create the chroot, it fails like this:
Processing triggers for sgml-base (1.26+nmu4ubuntu1) ...
E: 10mount: mount: wrong fs type, bad option, bad superblock on click-ubuntu-sdk-14.04-armhf,
E: 10mount: missing codepage or helper program, or other error
E: 10mount:
E: 10mount: In some cases useful info is found in syslog - try
E: 10mount: dmesg | tail or so.
E: click-ubuntu-sdk-14.04-armhf-06293574-400d-48f5-8eb2-b74b8af77b72: Chroot setup failed: stage=setup-start
Command returned 1: schroot -c click-ubuntu-sdk-14.04-armhf -- env DEB_HOST_ARCH_BITS=32 DEB_BUILD_ARCH=amd64 DEB_TARGET_ARCH_ENDIAN=little DEB_BUILD_ARCH_ABI
=base DEB_TARGET_ARCH_BITS=32 DEB_TARGET_ARCH_LIBC=gnu DEB_BUILD_GNU_SYSTEM=linux-gnu DEB_HOST_ARCH_OS=linux DEB_TARGET_MULTIARCH=arm-linux-gnueabihf DEB_TARG
ET_ARCH_OS=linux DEB_HOST_ARCH_LIBC=gnu DEB_BUILD_GNU_TYPE=x86_64-linux-gnu DEB_BUILD_ARCH_OS=linux DEB_TARGET_GNU_SYSTEM=linux-gnueabihf DEB_BUILD_ARCH_BITS=
64 DEB_HOST_ARCH_ABI=eabihf DEB_BUILD_GNU_CPU=x86_64 DEB_BUILD_ARCH_ENDIAN=little DEB_HOST_ARCH=armhf DEB_BUILD_ARCH_LIBC=gnu DEB_TARGET_GNU_TYPE=arm-linux-gn
ueabihf DEB_HOST_MULTIARCH=arm-linux-gnueabihf DEB_TARGET_GNU_CPU=arm DEB_HOST_GNU_TYPE=arm-linux-gnueabihf DEB_HOST_GNU_CPU=arm DEB_TARGET_ARCH_CPU=arm DEB_B
UILD_MULTIARCH=x86_64-linux-gnu DEB_HOST_GNU_SYSTEM=linux-gnueabihf DEB_TARGET_ARCH_ABI=eabihf DEB_TARGET_ARCH=armhf DEB_HOST_ARCH_ENDIAN=little DEB_HOST_ARCH
_CPU=arm DEB_BUILD_ARCH_CPU=amd64 cmake .. -DCLICK_MODE=on -DINSTALL_TESTS=off
ERROR
This makes the autopkgtests fail, so it's blocking #1693226.
[Test Case]
Run the click autopkgtests in artful.
Check that there are no errors related to the wrong fs type.
[Regression Potential]
Fixing this for artful could make it fail in previous versions.
However, this was found by the autopkgtests, so as long as the chroot tests pass in the other revisions the fix is correct.
[Other Info]
Click is now longer in active development. These tests were failing for a long time. In here we are just trying to make a small change on the name of the python module so it doesn't conflict with python3-click which is in active development and needed by snapcraft in #1692102. |
The kernel changed the module name from overlayfs to overlay, this needs to be taken into consideration when creating the chroot.
[Impact]
When trying to create the chroot, it fails like this:
Processing triggers for sgml-base (1.26+nmu4ubuntu1) ...
E: 10mount: mount: wrong fs type, bad option, bad superblock on click-ubuntu-sdk-14.04-armhf,
E: 10mount: missing codepage or helper program, or other error
E: 10mount:
E: 10mount: In some cases useful info is found in syslog - try
E: 10mount: dmesg | tail or so.
E: click-ubuntu-sdk-14.04-armhf-06293574-400d-48f5-8eb2-b74b8af77b72: Chroot setup failed: stage=setup-start
Command returned 1: schroot -c click-ubuntu-sdk-14.04-armhf -- env DEB_HOST_ARCH_BITS=32 DEB_BUILD_ARCH=amd64 DEB_TARGET_ARCH_ENDIAN=little DEB_BUILD_ARCH_ABI
=base DEB_TARGET_ARCH_BITS=32 DEB_TARGET_ARCH_LIBC=gnu DEB_BUILD_GNU_SYSTEM=linux-gnu DEB_HOST_ARCH_OS=linux DEB_TARGET_MULTIARCH=arm-linux-gnueabihf DEB_TARG
ET_ARCH_OS=linux DEB_HOST_ARCH_LIBC=gnu DEB_BUILD_GNU_TYPE=x86_64-linux-gnu DEB_BUILD_ARCH_OS=linux DEB_TARGET_GNU_SYSTEM=linux-gnueabihf DEB_BUILD_ARCH_BITS=
64 DEB_HOST_ARCH_ABI=eabihf DEB_BUILD_GNU_CPU=x86_64 DEB_BUILD_ARCH_ENDIAN=little DEB_HOST_ARCH=armhf DEB_BUILD_ARCH_LIBC=gnu DEB_TARGET_GNU_TYPE=arm-linux-gn
ueabihf DEB_HOST_MULTIARCH=arm-linux-gnueabihf DEB_TARGET_GNU_CPU=arm DEB_HOST_GNU_TYPE=arm-linux-gnueabihf DEB_HOST_GNU_CPU=arm DEB_TARGET_ARCH_CPU=arm DEB_B
UILD_MULTIARCH=x86_64-linux-gnu DEB_HOST_GNU_SYSTEM=linux-gnueabihf DEB_TARGET_ARCH_ABI=eabihf DEB_TARGET_ARCH=armhf DEB_HOST_ARCH_ENDIAN=little DEB_HOST_ARCH
_CPU=arm DEB_BUILD_ARCH_CPU=amd64 cmake .. -DCLICK_MODE=on -DINSTALL_TESTS=off
ERROR
This makes the autopkgtests fail, so it's blocking bug #1693226.
[Test Case]
Run the click autopkgtests in artful.
Check that there are no errors related to the wrong fs type.
[Regression Potential]
Fixing this for artful could make it fail in previous versions.
However, this was found by the autopkgtests, so as long as the chroot tests pass in the other revisions the fix is correct.
[Other Info]
Click is now longer in active development. These tests were failing for a long time. In here we are just trying to make a small change on the name of the python module so it doesn't conflict with python3-click which is in active development and needed by snapcraft in bug #1692102. |
|
| 2017-06-14 08:04:28 |
Łukasz Zemczak |
nominated for series |
|
Ubuntu Zesty |
|
| 2017-06-14 08:04:28 |
Łukasz Zemczak |
bug task added |
|
click (Ubuntu Zesty) |
|
| 2017-06-14 08:04:28 |
Łukasz Zemczak |
nominated for series |
|
Ubuntu Yakkety |
|
| 2017-06-14 08:04:28 |
Łukasz Zemczak |
bug task added |
|
click (Ubuntu Yakkety) |
|
| 2017-06-14 08:05:49 |
Łukasz Zemczak |
description |
The kernel changed the module name from overlayfs to overlay, this needs to be taken into consideration when creating the chroot.
[Impact]
When trying to create the chroot, it fails like this:
Processing triggers for sgml-base (1.26+nmu4ubuntu1) ...
E: 10mount: mount: wrong fs type, bad option, bad superblock on click-ubuntu-sdk-14.04-armhf,
E: 10mount: missing codepage or helper program, or other error
E: 10mount:
E: 10mount: In some cases useful info is found in syslog - try
E: 10mount: dmesg | tail or so.
E: click-ubuntu-sdk-14.04-armhf-06293574-400d-48f5-8eb2-b74b8af77b72: Chroot setup failed: stage=setup-start
Command returned 1: schroot -c click-ubuntu-sdk-14.04-armhf -- env DEB_HOST_ARCH_BITS=32 DEB_BUILD_ARCH=amd64 DEB_TARGET_ARCH_ENDIAN=little DEB_BUILD_ARCH_ABI
=base DEB_TARGET_ARCH_BITS=32 DEB_TARGET_ARCH_LIBC=gnu DEB_BUILD_GNU_SYSTEM=linux-gnu DEB_HOST_ARCH_OS=linux DEB_TARGET_MULTIARCH=arm-linux-gnueabihf DEB_TARG
ET_ARCH_OS=linux DEB_HOST_ARCH_LIBC=gnu DEB_BUILD_GNU_TYPE=x86_64-linux-gnu DEB_BUILD_ARCH_OS=linux DEB_TARGET_GNU_SYSTEM=linux-gnueabihf DEB_BUILD_ARCH_BITS=
64 DEB_HOST_ARCH_ABI=eabihf DEB_BUILD_GNU_CPU=x86_64 DEB_BUILD_ARCH_ENDIAN=little DEB_HOST_ARCH=armhf DEB_BUILD_ARCH_LIBC=gnu DEB_TARGET_GNU_TYPE=arm-linux-gn
ueabihf DEB_HOST_MULTIARCH=arm-linux-gnueabihf DEB_TARGET_GNU_CPU=arm DEB_HOST_GNU_TYPE=arm-linux-gnueabihf DEB_HOST_GNU_CPU=arm DEB_TARGET_ARCH_CPU=arm DEB_B
UILD_MULTIARCH=x86_64-linux-gnu DEB_HOST_GNU_SYSTEM=linux-gnueabihf DEB_TARGET_ARCH_ABI=eabihf DEB_TARGET_ARCH=armhf DEB_HOST_ARCH_ENDIAN=little DEB_HOST_ARCH
_CPU=arm DEB_BUILD_ARCH_CPU=amd64 cmake .. -DCLICK_MODE=on -DINSTALL_TESTS=off
ERROR
This makes the autopkgtests fail, so it's blocking bug #1693226.
[Test Case]
Run the click autopkgtests in artful.
Check that there are no errors related to the wrong fs type.
[Regression Potential]
Fixing this for artful could make it fail in previous versions.
However, this was found by the autopkgtests, so as long as the chroot tests pass in the other revisions the fix is correct.
[Other Info]
Click is now longer in active development. These tests were failing for a long time. In here we are just trying to make a small change on the name of the python module so it doesn't conflict with python3-click which is in active development and needed by snapcraft in bug #1692102. |
The kernel changed the module name from overlayfs to overlay, this needs to be taken into consideration when creating the chroot.
[Impact]
When trying to create the chroot, it fails like this:
Processing triggers for sgml-base (1.26+nmu4ubuntu1) ...
E: 10mount: mount: wrong fs type, bad option, bad superblock on click-ubuntu-sdk-14.04-armhf,
E: 10mount: missing codepage or helper program, or other error
E: 10mount:
E: 10mount: In some cases useful info is found in syslog - try
E: 10mount: dmesg | tail or so.
E: click-ubuntu-sdk-14.04-armhf-06293574-400d-48f5-8eb2-b74b8af77b72: Chroot setup failed: stage=setup-start
Command returned 1: schroot -c click-ubuntu-sdk-14.04-armhf -- env DEB_HOST_ARCH_BITS=32 DEB_BUILD_ARCH=amd64 DEB_TARGET_ARCH_ENDIAN=little DEB_BUILD_ARCH_ABI
=base DEB_TARGET_ARCH_BITS=32 DEB_TARGET_ARCH_LIBC=gnu DEB_BUILD_GNU_SYSTEM=linux-gnu DEB_HOST_ARCH_OS=linux DEB_TARGET_MULTIARCH=arm-linux-gnueabihf DEB_TARG
ET_ARCH_OS=linux DEB_HOST_ARCH_LIBC=gnu DEB_BUILD_GNU_TYPE=x86_64-linux-gnu DEB_BUILD_ARCH_OS=linux DEB_TARGET_GNU_SYSTEM=linux-gnueabihf DEB_BUILD_ARCH_BITS=
64 DEB_HOST_ARCH_ABI=eabihf DEB_BUILD_GNU_CPU=x86_64 DEB_BUILD_ARCH_ENDIAN=little DEB_HOST_ARCH=armhf DEB_BUILD_ARCH_LIBC=gnu DEB_TARGET_GNU_TYPE=arm-linux-gn
ueabihf DEB_HOST_MULTIARCH=arm-linux-gnueabihf DEB_TARGET_GNU_CPU=arm DEB_HOST_GNU_TYPE=arm-linux-gnueabihf DEB_HOST_GNU_CPU=arm DEB_TARGET_ARCH_CPU=arm DEB_B
UILD_MULTIARCH=x86_64-linux-gnu DEB_HOST_GNU_SYSTEM=linux-gnueabihf DEB_TARGET_ARCH_ABI=eabihf DEB_TARGET_ARCH=armhf DEB_HOST_ARCH_ENDIAN=little DEB_HOST_ARCH
_CPU=arm DEB_BUILD_ARCH_CPU=amd64 cmake .. -DCLICK_MODE=on -DINSTALL_TESTS=off
ERROR
This makes the autopkgtests fail, so it's blocking bug #1693226.
[Test Case]
Run the click autopkgtests.
Check that there are no errors related to the wrong fs type.
[Regression Potential]
Fixing this for artful could make it fail in previous versions.
However, this was found by the autopkgtests, so as long as the chroot tests pass in the other revisions the fix is correct.
[Other Info]
Click is now longer in active development. These tests were failing for a long time. In here we are just trying to make a small change on the name of the python module so it doesn't conflict with python3-click which is in active development and needed by snapcraft in bug #1692102. |
|
| 2017-06-14 08:11:25 |
Łukasz Zemczak |
click (Ubuntu Zesty): status |
New |
Fix Committed |
|
| 2017-06-14 08:11:27 |
Łukasz Zemczak |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2017-06-14 08:11:28 |
Łukasz Zemczak |
bug |
|
|
added subscriber SRU Verification |
| 2017-06-14 08:11:31 |
Łukasz Zemczak |
tags |
|
verification-needed |
|
| 2017-06-14 08:17:11 |
Łukasz Zemczak |
click (Ubuntu Yakkety): status |
New |
Fix Committed |
|
| 2017-06-19 15:47:53 |
Łukasz Zemczak |
tags |
verification-needed |
verification-done-yakkety verification-done-zesty |
|
| 2017-06-19 15:48:39 |
Launchpad Janitor |
click (Ubuntu Zesty): status |
Fix Committed |
Fix Released |
|
| 2017-06-19 15:48:46 |
Łukasz Zemczak |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2017-06-19 15:49:07 |
Launchpad Janitor |
click (Ubuntu Yakkety): status |
Fix Committed |
Fix Released |
|
