[03:06] <nhasian> I'm confused. It says Rejected File nnn_2.6.orig.tar.gz already exists in Primary Archive for Ubuntu. When a did an apt-cache search in 18.04 it only had an older version and was not up to date.
[03:06] <nhasian> apt-cache showpkg nnn returns only version 1.7 so I'm trying to make a newer build available via PPA
[08:05] <RikMills> morning. how often does LP import new CVE data?
[08:49] <cjwatson> nhasian: By definition orig should be original, that is the exact tarball shipped by upstream.  If it's a new upstream release then it should have a new version number.  If you're building a revision of the packaging then you should be using the same orig tarball with patches on top or whatever, not rebuilding the orig.
[08:49] <cjwatson> RikMills: nightly
[08:50] <RikMills> cjwatson: thanks. the CVE was added late last night, so guess it just missed it by a squeak
[08:50] <cjwatson> RikMills: Yep, it's due to run shortly
[08:50] <RikMills> great. ty
[08:51] <cjwatson> (I say "nightly", actually earlyish morning)
[08:51] <RikMills> It's night somewhere!
[13:53] <nhasian> cjwatson: all I'm trying to do is provide the program nnn version 2.6 to Ubuntu 18.04 users because in the Universe repo it has an older version 1.7. How can I do that?
[13:55] <cjwatson> nhasian: Grab the existing Ubuntu orig.tar.gz from LP and put that in your package's parent directory, then rebuild the package based on that
[13:55] <cjwatson> nhasian: What's the package name?
[13:56] <cjwatson> Oh, literally "nnn"
[13:56] <cjwatson> So grab https://launchpad.net/ubuntu/+archive/primary/+sourcefiles/nnn/2.6-1/nnn_2.6.orig.tar.gz and use that
[13:57] <nhasian> cjwatson: thank you, I will try that now
[13:57] <cjwatson> If you look at https://launchpad.net/ubuntu/+source/nnn you'll see that it exists in Ubuntu, just only in eoan not bionic
[14:03] <nhasian> cjwatson: thank you. this is the first time I try to package anything, as well as create a PPA. so I downloaded it and extracted it. I'm guessing I use debuild and then dput? How do I tell it to package for bionic?
[14:10] <cjwatson> nhasian: I don't totally have time to give personalised packaging help to everyone, unfortunately, but maybe start with https://help.launchpad.net/Packaging/PPA ?
[14:11] <nhasian> I also just read about the backportpackage. am I going about this wrong? should I be using backportpackage instead?
[14:11] <cjwatson> nhasian: So, I was going to suggest that, and you should absolutely start with the packaging from eoan rather than reinventing the wheel yourself (i.e. "pull-lp-source nnn eoan")
[14:12] <cjwatson> nhasian: However, there will be some quirks because the eoan packaging relies on a version of debhelper that isn't in bionic
[14:12] <cjwatson> nhasian: Trying to backport debhelper usually turns out not to be a good idea; a better plan will be to get things working with the debhelper 11 in bionic
[14:12] <cjwatson> This is hopefully not too hard
[14:13] <nhasian> I've been working at this for 2 days. this is day 3 actually. I have read a lot of the launchpad and ppa pages. You are the first person who has actually answered any questions. I was hoping to find some mentor to help guide me. I even asked in our Ubuntu az loco page but didn't find any assistance
[14:20] <cjwatson> nhasian: I would suggest starting with backportpackage since it'll help deal with tedious things like getting the changelog right, but don't tell backportpackage to upload the result for you since you're going to have to make some adjustments
[14:21] <cjwatson> nhasian: Looking at the existing changelog, it doesn't look like it's really using much from debhelper 12, so you can probably just edit debian/control and debian/compat to reduce that to 11
[14:22] <cjwatson> nhasian: Then best practice is to test-build locally (if you don't already have an environment set up, use https://wiki.ubuntu.com/SimpleSbuild)
[14:22] <cjwatson> nhasian: Hopefully that works, and you can then follow the directions on the LP help site to build a source package and upload it
[14:23] <nhasian> cjwatson: thank you for your help
[14:23] <cjwatson> np
[17:12] <nhasian> cjwatson: the first time I used backportpackage it uploaded and was accepted to launchpad. The build failed however because missing build dependencies debhelper >=12. So I ran backportpackage a 2nd time and before pressing Y to upload, I went to the temp folder and changed debian/control and debian/compat to 11 but now it is rejected because it already exists
[17:20] <RikMills> nhasian: you need to increment the most minor packaging revision. e.g. ~ppa1 to ~ppa2
[17:21] <nhasian> RikMills: do I edit a file in the tmp folder to do that before uploading with backportpackage?
[17:24] <RikMills> I have no idea with backportpackage. never used it myself
[17:24]  * RikMills has other methods
[18:02] <ginggs> nhasian: you can also edit the PPA dependencies to Backports, which should include debehlper 12
[18:02] <ginggs> and then just retry the build
[20:09] <cjwatson> nhasian: dch -i should produce a change to debian/changelog for you
[20:09] <cjwatson> I actively recommend against ginggs's approach here for anyone who isn't an expert
[20:10] <cjwatson> forever dealing with support reqs from people who try that approach and get themselves very confused
[20:12] <cjwatson> also you shouldn't run backportpackage more than once on the same thing.  fetch the source package it produced back from Launchpad instead and edit that
[20:13] <cjwatson> backportpackage just produces a starting point
[20:58] <nhasian> cjwatson: thanks again. I will fetch the package from launchpad as you suggested and continue from there to try to get it working
[21:01] <nhasian> while I'm at it, is there a book or something for beginners? I feel like I'm floundering around here
[21:17] <doismellburning> nhasian: I've very much felt the same with packaging, for what it's worth
[21:17] <doismellburning> nhasian: I can't offer _help_, but you're not alone!