Re: [Bug 1501651] Re: ARM chroot issues: fatal error: rt_sigaction failure
On Thu, Nov 12, 2015 at 5:35 PM, Chris J Arges <1501...@bugs.launchpad.net> wrote: > Per our discussion, Michael will handle the Xenial upload, and I can SRU > where necessary. > Is it possible to SRU to trusty and vivid? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to golang in Ubuntu. https://bugs.launchpad.net/bugs/1501651 Title: ARM chroot issues: fatal error: rt_sigaction failure To manage notifications about this bug go to: https://bugs.launchpad.net/snapcraft/+bug/1501651/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1501651] Re: ARM chroot issues: fatal error: rt_sigaction failure
** Changed in: snapcraft Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1501651 Title: ARM chroot issues: fatal error: rt_sigaction failure To manage notifications about this bug go to: https://bugs.launchpad.net/snapcraft/+bug/1501651/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1497108] Re: snapcraft run leaves multiple snappy loop partitions
** Also affects: multipath-tools (Ubuntu) Importance: Undecided Status: New ** Description changed: - When I run snapcraft run, it boots the snappy kvm but leaves two loop - devices behind: + The bug seems to be in kpartx and long path handling + sergiusens@lindon:~/source/launchpad.net/snapcraft$ cd / + sergiusens@lindon:/$ sudo kpartx -avs ^C + sergiusens@lindon:/$ sudo losetup -a + [sudo] password for sergiusens: + sergiusens@lindon:/$ sudo kpartx -avs /home/sergiusens/source/launchpad.net/snapcraft/examples/godd/images/15.04.img + add map loop0p1 (252:0): 0 8192 linear /dev/loop0 8192 + add map loop0p2 (252:1): 0 131072 linear /dev/loop0 16384 + add map loop0p3 (252:2): 0 2097152 linear /dev/loop0 147456 + add map loop0p4 (252:3): 0 2097152 linear /dev/loop0 2244608 + add map loop0p5 (252:4): 0 3272704 linear /dev/loop0 4341760 + sergiusens@lindon:/$ sudo losetup -a + /dev/loop0: [2050]:7872194 (/home/sergiusens/source/launchpad.net/snapcraft/examples/godd/images/15.04.img) + sergiusens@lindon:/$ sudo kpartx -ds /home/sergiusens/source/launchpad.net/snapcraft/examples/godd/images/15.04.img + sergiusens@lindon:/$ sudo losetup -a + /dev/loop0: [2050]:7872194 (/home/sergiusens/source/launchpad.net/snapcraft/examples/godd/images/15.04.img) - $ losetup -a + + What follows is the snapcraft specific report + When I run snapcraft run, it boots the snappy kvm but leaves two loop devices behind: + + $ losetup -a /dev/loop0: []: (/home/elopio/workspace/canonical/snapcraft/trunk/examples/downloader-with-wiki-parts/image/15.04.img) /dev/loop1: []: (/home/elopio/workspace/canonical/snapcraft/trunk/examples/downloader-with-wiki-parts/image/15.04.img) Tested in vivid and wily To reproduce: bzr branch lp:snapcraft cd snapcraft cd examples/downloader-with-wiki-parts ./../../bin/snapcraft assemble ./../../bin/snapcraft run $ apt-cache policy ubuntu-device-flash ubuntu-device-flash: - Instalita: 0.31-0ubuntu1 - Kandidato: 0.31-0ubuntu1 - Version table: - *** 0.31-0ubuntu1 0 - 500 http://ppa.launchpad.net/snappy-dev/tools-proposed/ubuntu/ vivid/main amd64 Packages - 500 http://ppa.launchpad.net/snappy-dev/tools/ubuntu/ vivid/main amd64 Packages - 100 /var/lib/dpkg/status - 0.20-0ubuntu1 0 - 500 http://cr.archive.ubuntu.com/ubuntu/ vivid/universe amd64 Packages + Instalita: 0.31-0ubuntu1 + Kandidato: 0.31-0ubuntu1 + Version table: + *** 0.31-0ubuntu1 0 + 500 http://ppa.launchpad.net/snappy-dev/tools-proposed/ubuntu/ vivid/main amd64 Packages + 500 http://ppa.launchpad.net/snappy-dev/tools/ubuntu/ vivid/main amd64 Packages + 100 /var/lib/dpkg/status + 0.20-0ubuntu1 0 + 500 http://cr.archive.ubuntu.com/ubuntu/ vivid/universe amd64 Packages ** Summary changed: - snapcraft run leaves multiple snappy loop partitions + Long paths are not handled correctly when deleting partition mappings -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to multipath-tools in Ubuntu. https://bugs.launchpad.net/bugs/1497108 Title: Long paths are not handled correctly when deleting partition mappings To manage notifications about this bug go to: https://bugs.launchpad.net/snapcraft/+bug/1497108/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 1318027] Re: Go binaries cannot be stripped
On Mon, May 19, 2014 at 11:13 AM, James Page james.p...@ubuntu.com wrote: If I remember correctly, the stripping on gc built binaries was only problematic on armhf - the general upstream advice was 'don't strip - it breaks stuff' so we disabled it. That was with 1.1 - things may have moved on with 1.2 of golang Yeah, default debian rules for stripping worked fine with gc golang (at least for nuntium) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to golang in Ubuntu. https://bugs.launchpad.net/bugs/1318027 Title: Go binaries cannot be stripped To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-4.9/+bug/1318027/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
