[Group.of.nepali.translators] [Bug 1838045] [NEW] Header check ignore --kernelsourcedir
Public bug reported: In Ubuntu 16.04/Xenial the dkms command (2.2.0.3-2ubuntu11.7) ignores the provided kernel source directory and then fails by not finding the headers. This was fixed upstream in 2.2.0.3-5 and landed in 18.04/Bionic. Proposing to backport the additional line of code into Xenial. +[ ! -z "$ksourcedir_fromcli" ] && DIR=$kernel_source_dir ** Affects: dkms (Ubuntu) Importance: Medium Status: Fix Released ** Affects: dkms (Ubuntu Xenial) Importance: Medium Assignee: Stefan Bader (smb) Status: In Progress ** Also affects: dkms (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: dkms (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: dkms (Ubuntu Xenial) Status: New => In Progress ** Changed in: dkms (Ubuntu Xenial) Assignee: (unassigned) => Stefan Bader (smb) ** Changed in: dkms (Ubuntu) Status: In Progress => Fix Released ** Changed in: dkms (Ubuntu) Assignee: Stefan Bader (smb) => (unassigned) -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1838045 Title: Header check ignore --kernelsourcedir Status in dkms package in Ubuntu: Fix Released Status in dkms source package in Xenial: In Progress Bug description: In Ubuntu 16.04/Xenial the dkms command (2.2.0.3-2ubuntu11.7) ignores the provided kernel source directory and then fails by not finding the headers. This was fixed upstream in 2.2.0.3-5 and landed in 18.04/Bionic. Proposing to backport the additional line of code into Xenial. +[ ! -z "$ksourcedir_fromcli" ] && DIR=$kernel_source_dir To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1838045/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1668771] Re: [SRU] systemd-resolved negative caching for extended period of time
** No longer affects: systemd (Ubuntu Xenial) -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1668771 Title: [SRU] systemd-resolved negative caching for extended period of time Status in systemd: New Status in systemd package in Ubuntu: In Progress Status in systemd source package in Bionic: Fix Committed Status in systemd source package in Disco: Fix Committed Status in systemd source package in Eoan: In Progress Bug description: [Impact] * If a DNS lookup returns SERVFAIL, systemd-resolved seems to cache the result for very long (infinity?). I have to restart systemd- resolved to have the negative caching purged. * After SERVFAIL DNS server issue has been resolved, chromium/firefox still returns DNS error despite host can correctly resolve the name. [Test Case] * If a lookup returns SERVFAIL systemd-resolved will cache the result for 30s (See 201d995), however, there are several use cases on which this condition is not acceptable (See #5552 comments) and the only workaround would be to disable cache entirely or flush it , which isn't optimal. * Configure /etc/systemd/resolved.conf as follows: Cache=yes (default) * Restart systemd-resolved (systemctl restart systemd- resolved.service) * Run a host/getent command against a entry that will return SERVFAIL and check the journalctl output to see that the reply gets served from cache. root@systemd-disco:/home/ubuntu# host www.no-record.cl Host www.montemar.cl not found: 2(SERVFAIL) root@systemd-disco:/home/ubuntu# journalctl -u systemd-resolved -n -- Logs begin at Fri 2019-07-12 18:09:42 UTC, end at Tue 2019-07-23 15:10:17 UTC. -- Jul 23 15:10:10 systemd-disco systemd-resolved[1282]: Transaction 6222 for on scope dns on ens3/* now complete with Jul 23 15:10:10 systemd-disco systemd-resolved[1282]: Sending response packet with id 61042 on interface 1/AF_INET. Jul 23 15:10:10 systemd-disco systemd-resolved[1282]: Freeing transaction 6222. Jul 23 15:10:17 systemd-disco systemd-resolved[1282]: Got DNS stub UDP query packet for id 53580 Jul 23 15:10:17 systemd-disco systemd-resolved[1282]: Looking up RR for www.no-record.cl IN A. Jul 23 15:10:17 systemd-disco systemd-resolved[1282]: RCODE SERVFAIL cache hit for www.no-record.cl IN A Jul 23 15:10:17 systemd-disco systemd-resolved[1282]: Transaction 58570 for < www.no-record.cl IN A> on scope dns on ens3/* now complete with scope dns on ens3/. Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Using feature level UDP for transaction 22382. Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Sending query packet with id 22382. Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Processing incoming packet on transaction 22382 (rcode=SERVFAIL). Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Server returned error: SERVFAIL Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Not caching negative entry for: www.metaklass.org IN A, cache mode set to no-negative Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Transaction 22382 for on scope dns on ens3/ now complete with from network (unsigned). Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Sending response packet with id 31060 on interface 1/AF_INET. The following patch https://github.com/systemd/systemd/pull/13047 implements the required changes. [Other Info] Note that systemd in Eoan is being upgraded to upstream 242, so I am not adding this to Eoan now, as I don't want to disturb the merge. If needed after the merge, I'll add to Eoan. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1668771/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1838061] [NEW] linux-azure-edge: -proposed tracker
Public bug reported: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- variant: debs ** Affects: kernel-sru-workflow Importance: Undecided Status: New ** Affects: kernel-sru-workflow/automated-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/certification-testing Importance: Medium Assignee: Canonical Hardware Certification (canonical-hw-cert) Status: Invalid ** Affects: kernel-sru-workflow/prepare-package Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-security Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-updates Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/security-signoff Importance: Medium Assignee: Canonical Security Team (canonical-security) Status: New ** Affects: kernel-sru-workflow/verification-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux-azure-edge (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux-azure-edge (Ubuntu Xenial) Importance: Medium Status: Confirmed ** Tags: kernel-release-tracking-bug kernel-release-tracking-bug-live kernel-sru-cycle-2019.07.01-10 xenial ** Also affects: kernel-sru-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/certification-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-security Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-updates Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/security-signoff Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/verification-testing Importance: Undecided Status: New ** Tags added: kernel-release-tracking-bug xenial ** Also affects: linux-azure-edge (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux-azure-edge (Ubuntu Xenial) Status: New => Confirmed ** Changed in: kernel-sru-workflow/automated-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/automated-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/certification-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/certification-testing Assignee: (unassigned) => Canonical Hardware Certification (canonical-hw-cert) ** Changed in: kernel-sru-workflow/certification-testing Status: New => Invalid ** Changed in: kernel-sru-workflow/prepare-package Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-meta Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/promote-to-proposed Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: (unassigned) => Ubuntu Stable Release Updates Team (ubuntu-sru) ** Changed in: kernel-sru-workflow/promote-to-security Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/promote-to-security Assignee: (unassigned) => Ubuntu Stable Release Updates Team (ubuntu-sru) ** Changed in: kernel-sru-workflow/promote-to-updates
[Group.of.nepali.translators] [Bug 1837632] Re: xenial/linux-azure: 4.15.0-1052.57 -proposed tracker
** Changed in: kernel-sru-workflow/stakeholder-signoff Status: Confirmed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1837632 Title: xenial/linux-azure: 4.15.0-1052.57 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: Confirmed Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow stakeholder-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1837630 (trusty/linux-azure) derivatives: bug 1837629 (azure-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834954 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Ready for Release phase-changed: Friday, 26. July 2019 17:50 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Pending -- ready to copy trackers: trusty/linux-azure: bug 1837630 xenial/linux-azure-edge: bug 1834946 xenial/linux-azure/azure-kernel: bug 1837629 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1837632/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1800566] Re: Make reset_devices parameter default for kdump and decouple kdump systemd service from the KDUMP_CMDLINE_APPEND
** Changed in: makedumpfile (Ubuntu Cosmic) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1800566 Title: Make reset_devices parameter default for kdump and decouple kdump systemd service from the KDUMP_CMDLINE_APPEND Status in makedumpfile package in Ubuntu: In Progress Status in makedumpfile source package in Trusty: Won't Fix Status in makedumpfile source package in Xenial: Confirmed Status in makedumpfile source package in Bionic: Confirmed Status in makedumpfile source package in Cosmic: Won't Fix Status in makedumpfile source package in Disco: Confirmed Status in makedumpfile source package in Eoan: In Progress Bug description: [Impact] * Kdump does not configure by default the crash kernel to perform a device reset by default, by passing the "reset_devices" parameter. Also, the systemd service "kdump-tools-dump" is tightly-coupled with KDUMP_CMDLINE_APPEND and it shouldn't, to prevent user confusion. * Kernel has the "reset_devices" parameter that drivers can opt-in, and perform special activity in case this parameter is parsed from command-line. For example, in kdump kernels it hints the drivers that they are booting from a non-healthy condition and needs to issue some form of reset to the adapter, like clearing DMA mapping in their firmware for example. Users currently (kernel v5.2) are: aacraid, hpsa, ipr, megaraid_sas, mpt3sas, smartpqi, xenbus. This should be enabled by default in the kdump config file to be added in the kdump kernel command-line for all versions. * The systemd service"kdump-tools-dump" is responsible for triggering the execution of the makedumpfile tool ultimately. Kdump from Xenial+ releases rely on systemd as their init system, so this service is the way to trigger the kdump mechanism. Currently it is configured as any other parameter in KDUMP_CMDLINE_APPEND, meaning if user decides to change the line they need to remember adding the systemd service back. It's not really a parameter that should be easily manipulated in kdump line, since there's no use for it except to instruct systemd to load kdump; the only reasonable case for removing it is to debug kdump itself. [Test Case] 1) Deploy a Disco VM e.g. with uvt-kvm 2) Install the kdump-tools package 3) Run `kdump-config test`and check for the 'reset_devices' parameter: $ kdump-config test ... kexec command to be used: /sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0 nr_cpus=1 systemd.unit=kdump-tools.service irqpoll nousb ata_piix.prefer_ms_hyperv=0" /var/lib/kdump/vmlinuz Also, by changing the KDUMP_CMDLINE_APPEND we can see "systemd.unit =kdump-tools.service" to be removed. [Regression Potential] The regression potential is low, since it doesn't need any changes in makedumpfile code and we're only adding a parameter on the crash kernel command-line. The risks are related with bad behavior with the kernel when using "reset_devices", like if the driver has bugs in this path. It's considered safer to have the option (and this way prevent problems for booting a unhealthy kernel with potential stuck DMAs in the devices) than not having it. Regarding the other change, about the systemd service, it'll only affect users the are debugging kdump itself and it has no known regression potential. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1800566/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1834072] Re: Puppet agent using 100% CPU, in sched_yield() loop. Looks like an issue with ruby2.3 which has been fixed but not yet made it into Ubuntu.
** No longer affects: ruby2.3 (Ubuntu) -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1834072 Title: Puppet agent using 100% CPU, in sched_yield() loop. Looks like an issue with ruby2.3 which has been fixed but not yet made it into Ubuntu. Status in ruby2.3 source package in Xenial: Fix Committed Status in ruby2.3 package in Debian: Fix Released Bug description: [Impact] Ruby processes can sometimes get stuck in a loop consuming 100% CPU, as described upstream and in the debian bug report. It has most commonly been seen in the puppet agent. [Test Case] It's not easy to reproduce. It has been suggested that this script eventually reproduces the problem: while nice -n19 /opt/puppetlabs/puppet/bin/ruby sched_yield_loop.rb; do :; done Where sched_yield_loop.rb comes from "https://bugs.debian.org/cgi- bin/bugreport.cgi?att=1;bug=876377;filename=sched_yield_loop.rb;msg=22" I personally haven't seen it happen with the script, but maybe it could take days. [Regression Potential] Races with threads can be hard to reproduce, and so can regressions. Patch has been applied upstream and to debian for more than a year now. [Other Info] Bionic has ruby 2.5.1 and it has this fix already, as do all later ubuntu releaes. [Original Description] Ubuntu 16.04 ruby 2.3.1-2~16.04.12 kernel 4.4.0-148-generic We've noticed an issue across multiple servers where puppet agent will seem to get stuck and consume 100% CPU for days or weeks on end until manually killed. root@ps-prod-jenkins-qa-ui02:~# ps aux|grep -i puppe[t] root 1412 0.0 0.2 143716 38680 ?Ssl Jun11 0:39 /usr/bin/ruby /usr/bin/puppet agent root 34884 74.4 0.3 286848 53724 ?Rs Jun23 1141:44 puppet agent: applying configuration root 111481 94.1 0.3 288572 54996 ?Rs Jun18 8642:32 puppet agent: applying configuration root 128479 54.8 0.3 286744 53596 ?Rs 10:30 250:17 puppet agent: applying configuration Strace shows it in a sched_yield() loop: root@ps-prod-jenkins-qa-ui02:~# strace -p 34884 -c strace: Process 34884 attached ^Cstrace: Process 34884 detached % time seconds usecs/call callserrors syscall -- --- --- - - 100.000.002130 0123189 sched_yield -- --- --- - - 100.000.002130123189 total Some googling shows this is a common issue which was supposedly fixed/backported to ruby 2.3: https://tickets.puppetlabs.com/browse/PA-1743 https://bugs.ruby-lang.org/issues/13794 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876377 The following open Ubuntu bugs look to be having the same issue and suggest that this fix made it into Debian but never made it into Ubuntu: https://bugs.launchpad.net/ubuntu/+source/pcs/+bug/1783161 https://bugs.launchpad.net/ubuntu/+source/pcs/+bug/1772998 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/xenial/+source/ruby2.3/+bug/1834072/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1556783] Re: ruby2.3 test failures on s390x
** No longer affects: ruby2.3 (Ubuntu) -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1556783 Title: ruby2.3 test failures on s390x Status in ruby2.3 package in Ubuntu: Fix Released Status in ruby2.3 source package in Xenial: Fix Released Bug description: seen with https://launchpad.net/ubuntu/+source/ruby2.3/2.3.0-4/+build/9302935 test_thread.rb ...Fstderr output is not empty bootstraptest.tmp.rb:4:in `initialize': can't create Thread: Resource temporarily unavailable (ThreadError) from bootstraptest.tmp.rb:4:in `new' from bootstraptest.tmp.rb:4:in `block (2 levels) in ' from bootstraptest.tmp.rb:3:in `each' from bootstraptest.tmp.rb:3:in `map' from bootstraptest.tmp.rb:3:in `block in ' from bootstraptest.tmp.rb:2:in `times' from bootstraptest.tmp.rb:2:in `' uncommon.mk:581: recipe for target 'yes-btest-ruby' failed make[1]: *** [yes-btest-ruby] Error 1 make[1]: Leaving directory '/<>' dh_auto_test: make -j4 test returned exit code 2 debian/rules:53: recipe for target 'build-arch' failed make: *** [build-arch] Error 2 dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ruby2.3/+bug/1556783/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1556783] Re: ruby2.3 test failures on s390x
** Also affects: ruby2.3 (Ubuntu) Importance: Undecided Status: New ** Changed in: ruby2.3 (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1556783 Title: ruby2.3 test failures on s390x Status in ruby2.3 package in Ubuntu: Fix Released Status in ruby2.3 source package in Xenial: Fix Released Bug description: seen with https://launchpad.net/ubuntu/+source/ruby2.3/2.3.0-4/+build/9302935 test_thread.rb ...Fstderr output is not empty bootstraptest.tmp.rb:4:in `initialize': can't create Thread: Resource temporarily unavailable (ThreadError) from bootstraptest.tmp.rb:4:in `new' from bootstraptest.tmp.rb:4:in `block (2 levels) in ' from bootstraptest.tmp.rb:3:in `each' from bootstraptest.tmp.rb:3:in `map' from bootstraptest.tmp.rb:3:in `block in ' from bootstraptest.tmp.rb:2:in `times' from bootstraptest.tmp.rb:2:in `' uncommon.mk:581: recipe for target 'yes-btest-ruby' failed make[1]: *** [yes-btest-ruby] Error 1 make[1]: Leaving directory '/<>' dh_auto_test: make -j4 test returned exit code 2 debian/rules:53: recipe for target 'build-arch' failed make: *** [build-arch] Error 2 dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ruby2.3/+bug/1556783/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
