[13:35] <MasterPiece> Hey, https://launchpadlibrarian.net/206657628/buildlog_ubuntu-trusty-amd64.bison_2.7-6_BUILDING.txt.gz
[13:36] <MasterPiece> What is the problem?!!!
[13:37] <mapreri> MasterPiece: "Found files in /usr/local (must be in /usr)." ← not sure if that's the critical error, but it's not nice for sure.
[13:40] <MasterPiece> mapreri, Can you tell me a clue about how can I fix it? I think this is related to "install" file, is it?
[13:40] <mapreri> MasterPiece: it really depends your package. are the source somewhere i can easily look at? (a vcs?)
[13:41] <MasterPiece> Yes, it is bison source code
[13:41] <MasterPiece> https://launchpad.net/bison
[13:42] <mapreri> MasterPiece: i mean, the packaging code.
[13:42] <mapreri> the /debian directory
[13:43] <MasterPiece> mapreri, Yes, https://launchpad.net/~salehi/+archive/ubuntu/bison2/+packages
[13:43] <MasterPiece> direct link : https://launchpad.net/~salehi/+archive/ubuntu/bison2/+files/bison_2.7-6.debian.tar.gz
[13:44] <mapreri> i dgetted the dsc
[13:45] <MasterPiece> mapreri, I'm sorry, I can't understand "dgetted" means
[13:46] <mapreri> MasterPiece: `dget -u https://launchpad.net/~salehi/+archive/ubuntu/bison2/+files/bison_2.7-6.dsc`
[13:47] <mapreri> MasterPiece: btw, you call `./configure`, without passing anything at it. that way you end up having everything in /usr/local. thus, i suggest you to change that to dh_auto_configure and do a s#/usr/local#/usr# in the install file
[13:48] <mapreri> dh_auto_configure will take care of passing the right options to ./configure
[13:49] <mapreri> i'd also suggest you to find some spare time to move to the dh sequencer, instead of the old rules style. it tends to be more readable and maintainable, letting dh do all the magic. see the bison rules file, for example: https://sources.debian.net/src/bison/2:3.0.2.dfsg-2/debian/rules/
[13:51] <MasterPiece> mapreri, Can I copy that?
[13:51] <mapreri> MasterPiece: you can, just i don't know if it will work without any modification.
[13:54] <MasterPiece> mapreri, Thank you, now, I'm in locally building & test :)
[13:54] <MasterPiece> I'll upload it soon :)
[13:58] <wgrant> MasterPiece: bison's been packaged in Debian for about 20 years, so it has pretty robust packaging already. Any reason you didn't reuse that?
[14:50] <MasterPiece> wgrant, I know that, but in Trusty Tahr which is LTS, the 2.7 version is not available and our researchers source files, depends on 2.7.1 version, So, I have to package it to ourself
[15:36] <wgrant> MasterPiece: But that doesn't mean you have to rewrite the debian directory yourself. You can just take that from the current package and tweak it slightly to make it work on 2.7.1.
[15:36] <wgrant> Or, indeed, just use https://launchpad.net/ubuntu/+source/bison/2:2.7.1.dfsg-1
[15:38] <MasterPiece> wgrant, that is only available in "Sid" , I need it in trusty Tahr
[15:39] <wgrant> The binaries linked from that page will install fine on trusty if you try.
[15:39] <wgrant> And even if they didn't, it would be a trivial matter to rebuild them -- far easier than repackaging the source from scratch.
[15:44] <MasterPiece> wgrant, How can I repackage https://launchpad.net/ubuntu/+source/bison/2:2.7.1.dfsg-1 ??
[15:50] <MasterPiece> wgrant, I have to download the .orig.tar.gz and .debian.tar.gz and change some of file to build for trusty?
[15:50] <MasterPiece> wgrant, So, whats happened to CopyRight of debian/* files? :D
[15:51] <MasterPiece> Hey, Who have an idea?
[16:15] <MasterPiece> wgrant, Nice Job :) Thank you
[16:15] <MasterPiece> https://launchpad.net/~salehi/+archive/ubuntu/bison2/+packages
[16:35] <MasterPiece> Ohhh, nNoooOOoo,
[16:36] <MasterPiece> Why version 3 downloaded in this log :
[16:36] <MasterPiece> https://launchpadlibrarian.net/206667606/buildlog_ubuntu-trusty-amd64.rcssserver_15.2.2-2_BUILDING.txt.gz
[16:37] <MasterPiece> although I specified bison version as following :
[16:37] <MasterPiece> libbison-dev (= 2:2.7.1.dfsg-1), bison (= 2:2.7.1.dfsg-1)
[16:37] <MasterPiece> I added bison2 as the ppa dependency
[18:51] <ki7mt> Hello All, quick question. When creating a Team in LP, is there a way to make the Owner of a team be the Team itself, or does this need or be an individual LP user?
[20:03] <ki7mt> Looks like it worked as we needed it too, the Team is now the Owner of the Team :-) .. hope that does not create so strange do-loop :-)