[03:12] <AmmarZuma11> hi
[03:12] <AmmarZuma11> playig launchpad?
[08:06] <vi01et> wgrant: hello! last week i ask to fix my account login error because of my openstack account. do you remember me?
[14:18] <kuldeep> Hello, i create an account "kuldeepdhaka"   create PPA "madresistor".  now i want to build my packages "libbox0", "libreplot" etc and make them available under "madresistor".
[14:19] <kuldeep> the video https://www.youtube.com/watch?v=_bG-SXNX9Ww is for bzr. my packages will be build from git, (code here https://gitlab.com/madresistor)  anyone can help me understand the launchpad mechanism on how to add my packages? :)
[14:20] <kuldeep> (and build them and make them available)
[14:36] <kuldeep> anyone?
[14:36] <cjwatson> kuldeep: You'll want to first arrange for your repositories to be imported into Launchpad's git hosting (https://help.launchpad.net/VcsImports), and then you can use a git recipe to build them, much like the system for bzr (https://help.launchpad.net/Packaging/SourceBuilds)
[14:38] <kuldeep> ok, i will import the git repo.
[14:40] <kuldeep> "Make sure the project is registered in Launchpad"  shall i register madresistor as a project? (or just go on without it)
[14:40] <kuldeep> cjwatson, ^
[14:42] <kuldeep> or should i register "box0" as a project?
[14:46] <cjwatson> I have no idea about the structure of your project.
[14:47] <kuldeep> ok, "Mad Resistor" is the organisation, "Box0" is a project/product of "Mad Resistor".
[14:47] <kuldeep> cjwatson, make sense? ^
[14:47] <cjwatson> box0 would be a more appropriate match for a Launchpad project, then.
[14:47] <kuldeep> ok
[14:48] <cjwatson> madresistor could be a "project group" in Launchpad if you needed it, but that usually isn't necessary.
[14:50] <kuldeep> that can be done later
[14:57] <kuldeep> https://code.launchpad.net/+code-imports/+new  "**Name:**" "This will be used in the branch or repository URL to identify the import. Examples: main, trunk."   i have no experience with any git VCS. should i enter "master" in that input box?
[14:58] <kuldeep> cjwatson, ^ :)
[14:59] <kuldeep> *i have no experience with any VCS other than git
[15:02] <cjwatson> kuldeep: For git-to-git imports it should typically just be the repository name, so in this case "box0".
[15:02] <cjwatson> (The text was written for *-to-bzr imports, which are per-branch rather than per-repository, so it needs a bit of work.)
[15:03] <kuldeep> im importing https://gitlab.com/madresistor/libbox0
[15:04] <kuldeep> cjwatson, i guess you want to say "libbox0" right?
[15:04] <cjwatson> Sure, libbox0 if that's what you're importing.
[15:06] <kuldeep> i confused the Project and  Name field.  Project should have be the project that i created "box0"  and "libbox0" should be in the field Name to tell the git repository name.
[15:07] <cjwatson> What?
[15:07] <cjwatson> Oh, probably.
[15:08] <kuldeep> importing code :D
[15:08] <cjwatson> You could argue for libbox0 being a separate project, but whatever.
[15:09] <kuldeep> the words are very related, so thing get confusing.
[15:10] <kuldeep> ok, i have imported the git repo. i can see the commits.
[15:14] <kuldeep> cjwatson, maybe i forgot to tell that, Box0 contain a C library (libbox0), GUI programs (box0-studio-qt and liab-studio-qt - both need libbox0).   so the structure i made seems wrong.
[15:15] <cjwatson> honestly it doesn't matter that much if it's mainly for a recipe.
[15:17] <kuldeep> cjwatson, yes, but i dont want to build up confusing things right from start. i will take the effort do it nicely in the first go. :)
[15:18] <cjwatson> I tend to think of one-project-per-upstream-repository as a decent rule of thumb.
[15:28] <kuldeep> cjwatson, ok, i will just register "libbox0" as a project. later i can do project group on the name of "Box0" or "Mad Resistor".
[15:33]  * kuldeep confused with git "branch" and lp "branch" word usage.
[15:35] <cjwatson> they should be synonymous, except that there might be a few places where LP uses "branch" where it means "branch or repository"
[15:37] <cjwatson> (going out for a while now)
[15:37] <kuldeep> ok
[15:47] <kuldeep> https://code.launchpad.net/libbox0/+configure-code     "There are 2 errors."  but no error being shown. :/
[15:50] <kuldeep> im using the option "Import a Git repository hosted somewhere else"
[15:54] <kuldeep> now it just worked. :)  (from another tab.)
[16:07] <kuldeep> now this is another fact i came to know: i need a team to make PPA "Every individual and team in Launchpad can have one or more PPAs, each with its own URL. "  https://help.launchpad.net/Packaging/PPA
[16:08] <kuldeep> i cannot describe the hard time im going through.
[16:09] <kuldeep> all i just wanted to have was: fetch the gitlab code, build the binaries for ubuntu and store them.
[16:09] <nacc> kuldeep: you don't need a team to have a ppa, your lp user has ppas as well
[16:09] <nacc> afaik
[16:11] <kuldeep> whole ecosystem is mixed up. source-code-mgmt + ubutntu-ppa = launchpad.net.  why couldn't they be two seperate things? just simply let me keep my build my ppa's.
[16:11] <kuldeep> *build my binaries
[16:12] <kuldeep> thank, i cannot delete the project that i created. because no project deletion code has been done. lol
[16:16] <kuldeep> nacc, that what i had done earlier, a PPA "madresistor" but then these extra element of source-code-mgmt confused me. i had hard time figuring out that the whole thing is poorly though out.
[16:16] <kuldeep> *thought
[16:17] <nacc> source code mgmt and ppas are separate
[16:17] <nacc> afaict
[16:17] <nacc> unless you are using recipes, which are explicitly a way to tie them together
[16:20] <dobey> well, the source management and PPA are still separate things
[16:20] <dobey> a recipe is just a statement of "please take this one and put it into a package in the other
[16:21] <kuldeep> nacc, yes but for newcommer its a nightmare. im not familar with the terms at all
[16:21] <nacc> dobey: good point
[16:22] <nacc> kuldeep: which terms? did you read the online documentation?
[16:22] <kuldeep> nacc, i read the online documentation and looking at it, git is being treated as step child.
[16:22] <dobey> git support in launchpad was only very recently added
[16:23] <nacc> kuldeep: well, lp only relatively recently added git suport
[16:23] <nacc> what dobey said :)
[16:23] <dobey> launchpad itself is over 10 years old; git repository support is something that only really happened this year
[16:24] <dobey> if you don't want to use recipes, you can create and sign source packages yourself, and then upload them manually to your PPA with dput
[16:24] <kuldeep> i have an lp.net account, what is the most straight forward way to build packages for ubuntu.
[16:25] <dobey> to use recipes, you must import the code onto launchpad.net into either a git repo or a bzr branch
[16:25] <nacc> kuldeep: do you want them 'automatically' built or 'manually' request them to build?
[16:25] <nacc> what dobey just listed off are those two options, imo, (in the opposite order)
[16:25] <dobey> i don't know if you can import to private git repos without creating projects though
[16:26] <dobey> nacc: well no, recipes can be set to automatic or manual :)
[16:26] <kuldeep> dobey, do i need to create a "project" for that? (or i can just use import it under my account as git repo)
[16:26] <nacc> dobey: ah :)
[16:27] <kuldeep> also, i want to automatically build new package when a new commit is pushed. (or once everyday if new commit are there) - whichever, im fine
[16:27] <dobey> kuldeep: i don't know enough to answer that exactly. i /think/ you have a single personal git repo, and you can't import to it, which would mean the need to create projects
[16:29] <kuldeep> https://gitlab.com/madresistor/libbox0 https://gitlab.com/madresistor/box0-studio-qt  https://gitlab.com/madresistor/libreplot   and a few other.  (all git repo, and each repo will be a "{}.deb" file for ubuntu)
[16:29] <kuldeep> dobey, that detail is enough?
[16:31] <dobey> no, you need to define how to build the packages from the source inside a debian/ dir in each project
[16:31] <dobey> that can be on the master branch or on a different packaging branch
[16:32] <nacc> right, recipes/lp-git-integration doen't solve that you still need to package up your source (afaict)
[16:33] <kuldeep> ok, i will put them under "ubuntu-ppa" branch (branch as in `git branch`) and we can later do a temporary merge before building. right?
[16:33] <dobey> the recipe can have an instruction to merge a packaging branch
[16:33] <kuldeep> ok.
[16:34] <dobey> another option you might want to look at is building snaps instead of debs, with snapcraft (https://snapcraft.io)
[16:34] <dobey> which can also be done automatically on launchpad.net, and is somewhat less involved than building debs
[16:36] <kuldeep> i will stick with ppa for the moment. my aim is ubuntu package.  (i have already confused myself with many other options)
[16:37] <kuldeep> dobey, (minor query: any possibilty that i can delete the project "Box0" and "libbox0" that i created? - looking a issue raised it says no such facility implemented)
[16:38] <dobey> no, you can't delete projects
[16:39] <kuldeep> dobey, can i build ubuntu packages without having to create any project? (import the gitlab git code under my account and build the ppa from git code under my account)
[16:39] <dobey> as i said earlier, i don't think so
[16:39] <kuldeep> *create any project (project as in "Mozilla Firefox" https://launchpad.net/firefox)?
[16:39] <kuldeep> dobey, ok
[16:39] <dobey> and to be accurate, even with a project the code import would still be "under your account"
[16:41] <kuldeep> so, i will be forced to use lp.net to use recipe facility?
[16:43] <kuldeep> i mean, i have to maintain another project page just for having a ppa. :/
[16:45] <dobey> i'm not going to argue with you
[16:46] <kuldeep> dobey, im not trying to argue, im simply trying to understand what can be done in a easy straightforward way to get my package to ubuntu.
[16:46] <kuldeep> spending hour on this, and still no outcome make me sad.
[16:46] <kuldeep> *hours
[16:47] <dobey> you don't really have to "maintain" anything
[16:47] <kuldeep> will be back after food.
[16:47] <dobey> you're making it much harder than it is
[16:48] <kuldeep> dobey, ok, after food, i can a clean approch.
[16:48] <kuldeep> thank you for helping everyone
[18:32] <cjwatson> we can delete (well, technically hide) projects on request.  https://answers.launchpad.net/launchpad/+addquestion
[18:34] <kuldeep> cjwatson, ok
[18:34] <kuldeep> well, now i can resume on the work.
[18:34] <kuldeep> dobey, :)
[18:35] <cjwatson> and indeed, from where you are the main thing you need to do is to prepare actual packaging files, i.e. debian/*; those can live in a separate branch or even in a separate repository if you like
[18:37] <kuldeep> ok
[18:37] <cjwatson> dobey is correct that you need a project to host a code import from another site (although not to push a repository directly to LP)
[18:37] <cjwatson> in the new year maybe I'll see if I can hunt down a reason for that, since it doesn't seem to be an especially well-founded restriction
[18:39] <cjwatson> as for the documentation, there are definitely gaps where git isn't mentioned and should be; happy to receive pointers to problems so that we can fix them (https://bugs.launchpad.net/launchpad/+filebug is fine for that)
[18:40] <cjwatson> in terms of development effort we regard git as a first-class citizen though, since bzr isn't getting much love any more
[18:50] <kuldeep> i have a project https://launchpad.net/libbox0 and PPA https://launchpad.net/~kuldeepdhaka/+archive/ubuntu/box0
[18:53] <kuldeep> now as cjwatson wasid i need to have debian/* files.
[23:37] <rlaager> I'm trying to help a colleague setup a Launchpad account. He created an account, confirmed his email. He can login to Ubuntu One, but when trying to login to Launchpad, after clicking "Yes, log me in", it fails with the Launchpad crash page "something went wrong".
[23:48] <kuldeep> finally i have https://gist.github.com/kuldeepdhaka/79f3b0b59e3d504abe73000909b958a4  (additionally: `changelog` file is empty and `compact` file content "9")
[23:48] <kuldeep> dobey, cjwatson nacc ^
[23:50] <cjwatson> rlaager: Can you raise a ticket on https://answers.launchpad.net/launchpad/+addquestion with the OOPS ID they should have got?
[23:51] <cjwatson> kuldeep: That's a start.  You can use the dch(1) tool to deal with debian/changelog, and that should be debian/compat (short for compatibility level) not debian/compact.
[23:51] <kuldeep> im still curious how will the libbox0 and libbox0-dev will be divided.   my cmake script will generate a makefile, and `make install` will install header and binary at once
[23:51] <rlaager> cjwatson: Done: https://answers.launchpad.net/launchpad/+question/407771
[23:51] <cjwatson> kuldeep: You can use https://anonscm.debian.org/cgit/users/cjwatson/libpipeline.git/ if you want an example of a simple library package.
[23:51] <nacc> kuldeep: that's specified by debian/libbox0.* files and debian/libbox0-dev.* files
[23:52] <nacc> e.g. libbox0.install
[23:52] <cjwatson> (Obviously everything outside debian/ will be different, and there'll be various differences in detail.)
[23:53] <kuldeep> cjwatson, thanks, will look into it
[23:53] <cjwatson> And as nacc says.
[23:53] <nacc> kuldeep: this may help: .launchpad.net/launchpad/+question/407771
[23:53] <nacc> bah
[23:54] <nacc> https://www.debian.org/doc/manuals/maint-guide/dother.en.html
[23:54] <nacc> kuldeep: --^
[23:55]  * cjwatson goes back to amateur music typesetting
[23:57] <nacc> kuldeep: and as cjwatson pointed you to, looking at other library source packages is probably a good reference, especially if all they generate is a lib and lib-dev like yours