Re: build-and-upload: autopkgtest fails
On 18-04-05 07:53:57, Cédric Boutillier wrote: > On Wed, Apr 04, 2018 at 10:56:31PM +0200, Georg Faerber wrote: > > flock: failed to execute mispipe: No such file or directory > > mispipe is in the moreutils package. Do you have it installed? It is > recommended by debci. Thanks, this made the setup part work (I still believe that this is quite similar to autopkgtest-build-lxc). However, running build-and-upload after this leads to the same result: [...] autopkgtest [09:41:33]: version 5.2 autopkgtest [09:41:33]: host debian; command line: /usr/bin/autopkgtest /home/georg/code/debian/ruby-team/build-area/ruby-sequel_5.7.0-1.dsc -- lxc autopkgtest-unstable-amd64 autopkgtest [09:41:53]: testbed dpkg architecture: amd64 autopkgtest [09:41:54]: testbed running kernel: Linux 4.15.0-1-amd64 #1 SMP Debian 4.15.4-1 (2018-02-18) autopkgtest [09:41:54]: source /home/georg/code/debian/ruby-team/build-area/ruby-sequel_5.7.0-1.dsc Cannot execute /bin/sh blame: /home/georg/code/debian/ruby-team/build-area/ruby-sequel_5.7.0-1.dsc badpkg: rules extract failed with exit code 126 autopkgtest [09:41:54]: ERROR: erroneous package: rules extract failed with exit code 126 [...] Cheers, Georg signature.asc Description: Digital signature
Re: ruby-gettext-setup: FTBFS
Hi, On 18-04-04 23:58:32, Hleb Valoshka wrote: > On 4/4/18, Georg Faerber wrote: > > ruby-gettext-setup FTBFS now, with errors like > > > > /usr/lib/ruby/vendor_ruby/gettext/tools/parser/ruby.rb:50:in `gsub': > > invalid byte sequence in US-ASCII (ArgumentError) > > > > See #894829 for details. > > > > /usr/lib/ruby/vendor_ruby/gettext/tools/parser/ruby.rb is UTF-8 file, > it contains japanese letters (こんにちは世界), of course these letters > can't be processed in C locale. > > So you either patch it to remove UTF-8 characters or run tests in > C.UTF-8. Please go ahead and feel free to fix the package; I failed to do so yesterday, but I've to admit, I didn't spent much time. Also, my local setup is currently broken. > I don't think that the last ruby-gettext update introduced a > regression as in the previous version it had a terrible insecure > parser for ruby strings: > begin; s = eval(s); rescue Exception; end I don't get the relation between "no regression" and "previous version had a terrible insecure parser". > Now it has a proper one. No doubt -- thanks for your work and the upload. The point I was trying to make: Let's work together, better (in the future). For example: Before uploading such a change, communicate about it especially if it introduces a breaking change. Cheers, Georg signature.asc Description: Digital signature
Re: build-and-upload: autopkgtest fails
On Thu, Apr 05, 2018 at 09:49:02AM +0200, Georg Faerber wrote: > On 18-04-05 07:53:57, Cédric Boutillier wrote: > > On Wed, Apr 04, 2018 at 10:56:31PM +0200, Georg Faerber wrote: > > > flock: failed to execute mispipe: No such file or directory > > > > mispipe is in the moreutils package. Do you have it installed? It is > > recommended by debci. > > Thanks, this made the setup part work (I still believe that this is > quite similar to autopkgtest-build-lxc). it is. the container creation part it just a call to `sudo debci setup`, which in turn basically just calls autopkgtest-build-lxc. > However, running > build-and-upload after this leads to the same result: > > [...] > autopkgtest [09:41:33]: version 5.2 > autopkgtest [09:41:33]: host debian; command line: /usr/bin/autopkgtest > /home/georg/code/debian/ruby-team/build-area/ruby-sequel_5.7.0-1.dsc -- lxc > autopkgtest-unstable-amd64 > autopkgtest [09:41:53]: testbed dpkg architecture: amd64 > autopkgtest [09:41:54]: testbed running kernel: Linux 4.15.0-1-amd64 #1 SMP > Debian 4.15.4-1 (2018-02-18) > autopkgtest [09:41:54]: source > /home/georg/code/debian/ruby-team/build-area/ruby-sequel_5.7.0-1.dsc > Cannot execute /bin/sh ^ this is very weird does the autopkgtest-unstable-amd64 lxc container work fine otherwise? e.g. $ sudo lxc-ls -f NAME STATE AUTOSTART GROUPS IPV4 IPV6 autopkgtest-stable-amd64 STOPPED 0 - -- autopkgtest-testing-amd64 STOPPED 0 - -- autopkgtest-unstable-amd64 STOPPED 0 - -- $ sudo lxc-copy -n autopkgtest-unstable-amd64 -N test $ sudo lxc-start -n test $ sudo lxc-attach -n test root@test:/# /bin/sh -c 'echo hello' hello root@test:/# exit exit $ sudo lxc-stop -n test $ sudo lxc-destroy -n test Destroyed container test $ signature.asc Description: PGP signature
Re: build-and-upload: autopkgtest fails
Hi Antonio, I hoped you would jump in here, as I'm quite clueless what this is about, or what is wrong: On 18-04-05 08:10:09, Antonio Terceiro wrote: > On Thu, Apr 05, 2018 at 09:49:02AM +0200, Georg Faerber wrote: > > On 18-04-05 07:53:57, Cédric Boutillier wrote: > > > On Wed, Apr 04, 2018 at 10:56:31PM +0200, Georg Faerber wrote: > > > > flock: failed to execute mispipe: No such file or directory > > > > > > mispipe is in the moreutils package. Do you have it installed? It > > > is recommended by debci. > > > > Thanks, this made the setup part work (I still believe that this is > > quite similar to autopkgtest-build-lxc). > > it is. the container creation part it just a call to `sudo debci > setup`, which in turn basically just calls autopkgtest-build-lxc. Thanks for clarification. > > However, running > > build-and-upload after this leads to the same result: > > > > [...] > > autopkgtest [09:41:33]: version 5.2 > > autopkgtest [09:41:33]: host debian; command line: /usr/bin/autopkgtest > > /home/georg/code/debian/ruby-team/build-area/ruby-sequel_5.7.0-1.dsc -- lxc > > autopkgtest-unstable-amd64 > > autopkgtest [09:41:53]: testbed dpkg architecture: amd64 > > autopkgtest [09:41:54]: testbed running kernel: Linux 4.15.0-1-amd64 #1 SMP > > Debian 4.15.4-1 (2018-02-18) > > autopkgtest [09:41:54]: source > > /home/georg/code/debian/ruby-team/build-area/ruby-sequel_5.7.0-1.dsc > > Cannot execute /bin/sh > > ^ this is very weird Yes, it is. Especially, because it works if called manually.. > does the autopkgtest-unstable-amd64 lxc container work fine otherwise? > e.g. > > [...] All of this works as expected.. Thanks for your help, Georg signature.asc Description: Digital signature
Re: build-and-upload: autopkgtest fails
Hi all, On 18-04-05 13:18:56, Georg Faerber wrote: > On 18-04-05 08:10:09, Antonio Terceiro wrote: > > On Thu, Apr 05, 2018 at 09:49:02AM +0200, Georg Faerber wrote: > > > However, running > > > build-and-upload after this leads to the same result: > > > > > > [...] > > > autopkgtest [09:41:33]: version 5.2 > > > autopkgtest [09:41:33]: host debian; command line: /usr/bin/autopkgtest > > > /home/georg/code/debian/ruby-team/build-area/ruby-sequel_5.7.0-1.dsc -- > > > lxc autopkgtest-unstable-amd64 > > > autopkgtest [09:41:53]: testbed dpkg architecture: amd64 > > > autopkgtest [09:41:54]: testbed running kernel: Linux 4.15.0-1-amd64 #1 > > > SMP Debian 4.15.4-1 (2018-02-18) > > > autopkgtest [09:41:54]: source > > > /home/georg/code/debian/ruby-team/build-area/ruby-sequel_5.7.0-1.dsc > > > Cannot execute /bin/sh > > > > ^ this is very weird > > Yes, it is. Especially, because it works if called manually.. After some more debugging with Antonio on IRC, I suspect this is due to apparmor: [ +0.357028] audit: type=1400 audit(1522939203.328:120): apparmor="DENIED" operation="mount" info="failed type match" error=-13 profile="lxc-container-default-cgns" name="/sys/fs/cgroup/unified/" pid=14741 comm="systemd" fstype="cgroup2" srcname="cgroup2" flags="rw, nosuid, nodev, noexec" [ +0.55] audit: type=1400 audit(1522939203.328:121): apparmor="DENIED" operation="mount" info="failed type match" error=-13 profile="lxc-container-default-cgns" name="/sys/fs/cgroup/unified/" pid=14741 comm="systemd" fstype="cgroup2" srcname="cgroup2" flags="rw, nosuid, nodev, noexec" My apparmor knowledge is still quite limited, so the following might be wrong, but: - Disabling apparmor, restarting lxc (and rebooting as well, just to make sure) didn't made this work. - I suspect the setup / script is broken at least on unstable, and on testing as well, I guess. I'll debug this further, but still would be happy to take more pointers.. :) Cheers, Georg signature.asc Description: Digital signature
Re: build-and-upload: autopkgtest fails
On 18-04-05 16:47:26, Georg Faerber wrote: > On 18-04-05 13:18:56, Georg Faerber wrote: > > On 18-04-05 08:10:09, Antonio Terceiro wrote: > > > On Thu, Apr 05, 2018 at 09:49:02AM +0200, Georg Faerber wrote: > > > > However, running > > > > build-and-upload after this leads to the same result: > > > > > > > > [...] > > > > autopkgtest [09:41:33]: version 5.2 > > > > autopkgtest [09:41:33]: host debian; command line: /usr/bin/autopkgtest > > > > /home/georg/code/debian/ruby-team/build-area/ruby-sequel_5.7.0-1.dsc -- > > > > lxc autopkgtest-unstable-amd64 > > > > autopkgtest [09:41:53]: testbed dpkg architecture: amd64 > > > > autopkgtest [09:41:54]: testbed running kernel: Linux 4.15.0-1-amd64 #1 > > > > SMP Debian 4.15.4-1 (2018-02-18) > > > > autopkgtest [09:41:54]: source > > > > /home/georg/code/debian/ruby-team/build-area/ruby-sequel_5.7.0-1.dsc > > > > Cannot execute /bin/sh > > > > > > ^ this is very weird > > > > Yes, it is. Especially, because it works if called manually.. > > After some more debugging with Antonio on IRC, I suspect this is due to > apparmor: > > [ +0.357028] audit: type=1400 audit(1522939203.328:120): apparmor="DENIED" > operation="mount" info="failed type match" error=-13 > profile="lxc-container-default-cgns" name="/sys/fs/cgroup/unified/" pid=14741 > comm="systemd" fstype="cgroup2" srcname="cgroup2" flags="rw, nosuid, nodev, > noexec" > [ +0.55] audit: type=1400 audit(1522939203.328:121): apparmor="DENIED" > operation="mount" info="failed type match" error=-13 > profile="lxc-container-default-cgns" name="/sys/fs/cgroup/unified/" pid=14741 > comm="systemd" fstype="cgroup2" srcname="cgroup2" flags="rw, nosuid, nodev, > noexec" > > My apparmor knowledge is still quite limited, so the following might be > wrong, but: > > - Disabling apparmor, restarting lxc (and rebooting as well, just to > make sure) didn't made this work. > - I suspect the setup / script is broken at least on unstable, and on > testing as well, I guess. > > I'll debug this further, but still would be happy to take more > pointers.. :) Hm, maybe the above is not correct: - Setting all lxc profiles to complain mode, lead to: [ +0.357471] audit: type=1400 audit(1522941246.693:197): apparmor="ALLOWED" operation="mount" info="failed type match" error=-13 profile="lxc-container-default-cgns" name="/sys/fs/cgroup/unified/" pid=21615 comm="systemd" fstype="cgroup2" srcname="cgroup2" flags="rw, nosuid, nodev, noexec" with the same result as above. - Adding lxc.aa_profile = unconfined to the container config resulted in no audit log in dmesg, but no success either. Cheers, Georg signature.asc Description: Digital signature
