@cascardo thanks for the debdiffs! I noticed that the nbd package is patchless (run 'what-patch' in the source directory to check this) but you added a patches via quilt. As much as I prefer quilt over patchless source packages, can you change it back to patchless and apply the patches directly to the source?
Here's a good example of how it should be done with the commit description and origin in the changelog itself: https://launchpad.net/ubuntu/+source/nbd/1:3.7-1ubuntu0.1 Sorry for the busy work :/ ** Changed in: nbd (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: nbd (Ubuntu Bionic) Status: New => Incomplete ** Changed in: nbd (Ubuntu Bionic) Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo) ** Changed in: nbd (Ubuntu Artful) Importance: Undecided => Medium ** Changed in: nbd (Ubuntu Artful) Status: New => Incomplete ** Changed in: nbd (Ubuntu Artful) Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1772024 Title: linux 4.13.0-42.47 ADT test failure with linux 4.13.0-42.47 (nbd- smoke-test) Status in linux package in Ubuntu: In Progress Status in nbd package in Ubuntu: Fix Released Status in linux source package in Trusty: New Status in nbd source package in Trusty: New Status in linux source package in Xenial: New Status in nbd source package in Xenial: New Status in linux source package in Artful: New Status in nbd source package in Artful: Incomplete Status in linux source package in Bionic: New Status in nbd source package in Bionic: Incomplete Status in linux source package in Cosmic: In Progress Status in nbd source package in Cosmic: Fix Released Bug description: [Impact] nbd-server will crash when a client connects to it, if it was started without a server name. It may also leak fds if fork fails. [Test Case] Running the server with an empty config file and an image on the command line, and then starting a local client will crash the server. After the fix, it doesn't crash anymore, and a filesystem may be created and used after that. [Regression Potential] The fix also implies a small package change, to use quilt. It has built just fine and many tests have been run on top of those packages and no failure seemed to be the result of those userspace changes, but known failures in the kernel driver. Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful/artful/amd64/l/linux/20180518_040741_b3b54@/log.gz i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful/artful/i386/l/linux/20180518_050911_b3b54@/log.gz ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful/artful/ppc64el/l/linux/20180518_040734_b3b54@/log.gz s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful/artful/s390x/l/linux/20180518_035527_b3b54@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1772024/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
