[00:31] how can i view all the bugs for a particular tag regardless of package? it seems the tag links in a particular bug are package-specific. [02:44] wxl: Use the tag field on https://launchpad.net/bugs/+bugs?advanced=1 for all of LP, or https://launchpad.net/ubuntu/+bugs?advanced=1 for all Ubuntu packages. === LocutusOfBorg is now known as mdelaus === mdelaus is now known as Locutusofborg [13:45] o/ . i'm not certain this is the right place to ping, but I have gotten more than one message like https://paste.ubuntu.com/p/RSdgh8svcH/ [13:45] Subject: lists.debian.org has received bounces from you [13:45] to my smoser@ubuntu.com email which forwards to a "gmail + addressing" address. [14:00] smoser: Nothing to do with Launchpad [14:00] IS runs email [14:01] cjwatson: in the past i'd have asked in #is (or opened an rt) [14:01] what do i do since that is not available to me now? [14:01] smoser: #canonical-sysadmin [14:02] smoser: or rt@ubuntu.com [14:02] thank you. [14:02] np [14:43] what does it mean in Build status "Failed to build on lgw01-amd64-036" [14:49] lgw01-amd64-036 is the name of a builder [14:49] You very likely don't care about that [14:49] The interesting bit is that it failed, and the build log which should be linked from the build page [14:52] cjwatson: what am I looking for in the build log? https://launchpadlibrarian.net/436558291/buildlog_ubuntu-bionic-amd64.nnn_2.6-1~ubuntu18.04.1~ppa1_BUILDING.txt.gz [14:52] cjwatson:nevermind I think I found it [14:52] it says I don't have a public key [14:53] which is weird because I did both the ssh and pgp keys [14:53] nhasian: there's a bunch of compilation errors at the bottom that look like your issue [14:54] nhasian: the key thing just looks like a warning [14:54] I generally like to start reading build failure logs from the bottom up - first identify the core issue, then look backwards for causes [14:56] Right, the public key bit there is not relevant. [14:57] Looks like some ncurses-related backporting problem [15:01] So the problem is that the nnn package you were backporting relies on the libncurses*-dev package merge that happened as a result of https://bugs.debian.org/840429 [15:01] Debian bug 840429 in libtinfo-dev "Please explain " Packages should not build-depend on this package. "" [Normal,Fixed] [15:02] I think you need to change libncurses-dev to libncursesw5-dev in debian/control (reverting to what was used in an earlier version of the nnn package) to cope with that [15:03] So grab your source package back from https://launchpad.net/~nhasian/+archive/ubuntu/nnn/+packages if you don't have it already, unpack it, edit debian/control, use "dch -i" to add another entry to the top of debian/changelog explaining the change, build source package, upload [16:45] cjwatson: thaks I feel I'm very close to getting this right. So I edited debian/control and also ran dch -i to explain the changes. Then I use debuild and then dput correct? [16:47] make sure to use debuild -S, and then I'd generally advise running debdiff between the old and new .dsc files to make sure the changes are as you expect [16:47] and then dput on the .changes, yes [16:50] cjwatson: when I try to debuild it says error: Unmet build dependencies: libncurses5w-dev [16:52] ah I think it should be libncurses5-dev [17:03] nhasian: I gave you the right package name above [17:04] nhasian: libncursesw5-dev, not either of libncurses5w-dev or libncurses5-dev [17:19] is this causing the fatal error when trying to debuild "dpkg-source: error: Version number suggests Ubuntu changes, but Maintainer: does not have Ubuntu address" [17:27] I changed the maintainer line to my ubuntu address and the debuild compelted successfully. used dput to upload new version to launchpad. Lets see if the build completes this time [20:11] cjwatson: thanks to your help, I was finally able to publish the latest version of nnn to my launchpad PPA. [20:19] I'm still scratching my head trying to figure out how you were able to tell from looking at the building log that I needed libncursesw5-dev.