[11:21] <nickoe> Is it possible to fetch the package build dsc from a PPA?
[11:22] <jtaylor> nickoe: click on view package details on the ppa page
[11:25] <nickoe> jtaylor: I don't see a buildscript
[11:25] <jtaylor> you want to fetch a dsc during a package build? thats not possible
[11:26]  * nickoe is not entirely familiar in building deb packages nor the ubuntu way of doing so
[11:26] <jtaylor> packages are usually built in environments without network
[11:26] <nickoe> I just want to be able to create my own ppa by forking and fixing another ones. But I am not really on ubuntu, but I have a debian machine nearby.
[11:26] <jtaylor> beyond the repository of course
[11:27] <jtaylor> so you just want to get the build files of the already existing ppa?
[11:27] <nickoe> How can I acomplish that my objective?
[11:30] <nickoe> jtaylor:
[11:30] <jtaylor> ^
[11:31] <nickoe> jtaylor: yes, kind of.
[11:31] <jtaylor> then view package details is what you want
[11:31] <jtaylor> get the dsc link and do: dget -ux <link>
[11:32] <nickoe> I have read some in the docs of setting up a PPA, but as I read you need to have the dsc file that as I understand it is like a PKGBUILD for debian stuff
[11:33] <jtaylor> no the dsc file is more a description of what a package contains
[11:33] <jtaylor> its used by dget to download what is needed
[11:33] <nickoe> ok
[11:33] <jtaylor> the equivalent to PKGBUILD is debian/rules + a bunch of other files in debian7
[11:34] <nickoe> Just trying to figure out what debian pkg contains dget
[11:34] <yofel> devscripts
[11:34] <jtaylor> devscripts
[11:34] <jtaylor> just type it in a terminal and it will tell you
[11:35] <nickoe> jtaylor: nah, not really, it did not suggest it, but yes, I am installing devscripts now
[11:46] <nickoe> jtaylor: I can't figure out what the format of the link should be it is not ppa:username/ppaname  nor the ppa's sources list link.'
[11:47] <jtaylor> its the link of the dsc file in the details page of the ppa
[11:47] <jtaylor> you can expand the package with the little arrow
[11:47] <jtaylor> apt-get source works too if you have the ppa activated
[11:48] <nickoe> ok, not it is downloading stuff
[11:48] <nickoe> I don't have the ppa activated here
[11:49] <nickoe> it contains too  old packages, so it was kind of useless to add it
[11:50] <nickoe> jtaylor: To do like a testing ppa, does one need to upload from my workstation to the ppa every time or can lanuchpad auto fetch new sources and make a new debs?
[11:52] <jtaylor> nickoe: you normally build locally until its right and then upload
[11:53] <nickoe> yes, that is true of course for initial setup. But can lp fetch new sourcs i.e weekly, or daily or when a new revision is pushed to a lp hosted project?
[11:55] <jtaylor> that is a daily build recipe
[11:55] <jtaylor> unfortunately unless its original source is in bzr its inconvinient
[11:55] <jtaylor> and breaks form time to time, (which is why I'm here, mine is broken ...)
[11:56] <nickoe> The original source is in bzr on lp
[11:56] <jtaylor> thats makes things easy
[11:56] <nickoe> jtaylor: when did yours start to break?
[11:56] <jtaylor> when upstream added utf-8 filenames
[11:56] <jtaylor> nickoe: see the recipe down there: https://code.launchpad.net/~jtaylor/+recipe/ipython-daily
[11:56] <nickoe> how long time ago was that?
[11:56] <jtaylor> yesterday
[11:57] <jtaylor> the jist is put in the upstream repo and merge your debian repo into it
[11:57] <jtaylor> google should find docs for it
[11:58] <nickoe> ok
[11:58] <nickoe> BUt first I need to get this build with latest head
[12:06] <nickoe> So in deb systems you dont have a single script that fetches the proper source and then runs the build commands?
[12:10] <wgrant> nickoe: Not quite.
[12:11] <nickoe> wgrant: How on earth does people do package management then?
[12:11] <wgrant> A Debian sourc epackage is a .dsc plus the files that it references.
[12:11] <wgrant> Normally the .dsc references a *.debian.tar.* and a *.orig.tar.*
[12:11] <wgrant> The orig.tar.* is usually the upstream source release tarball
[12:12] <wgrant> You extract the .dsc with 'dpkg-source -x', which will give you the unpacked upstream source, with the debian.tar.* unpacked into debian/, and any patches from the debian.tar.* applied to the upstream source.
[12:13] <wgrant> you reconstruct the debian.tar.* and .dsc with 'dpkg-buildpackage -S'
[12:14] <wgrant> Packages aren't allowed to reference external resources on the Internet, as that would then mean that a change to an external website could break the distro.
[12:20] <nickoe> But I really just want to create my ppa, so it should refeerence a bzr on lp, and I guess I need to make a recipe on lp to fetch the soruces.
[12:20] <nickoe> So locally, I guess I just use bzr branch lp:poject
[12:21] <wgrant> What do you want to put in your PPA?
[12:21] <nickoe> and then I set up the dsc stuff here?
[12:21] <wgrant> Recipes are a good solution to some problems, but they're rarely a good way to get started if you have no experience with Debian-style packaging.
[12:21] <nickoe> dayli build or if possible build for each rev
[12:21] <nickoe> Well first I will have it build locally
[12:22] <nickoe> so now I have checked out the src from bzr here
[12:22]  * nickoe is currently looking at https://wiki.debian.org/IntroDebianPackaging#Introduction_to_Debian_Packaging
[12:27] <nickoe> wgrant: the dch --create gives my username@hostname as the user is this desired?
[12:28] <wgrant> nickoe: It'll use the DEBEMAIL envvar if it is set
[12:28] <wgrant> Or EMAIL, I think
[12:29] <nickoe> DEBEMAIL works
[12:34] <jtaylor> whats this error about: https://launchpadlibrarian.net/163708425/buildlog.txt.gz
[12:34] <jtaylor> no support for utf-8 filenames?
[12:38] <nickoe> wgrant: "The final file we need is debian/source/format, and it should contain the version number for the format of the source package, which is "3.0 (quilt)". "    What exactly does this mean?
[12:39] <wgrant> nickoe: The source format basically describes the files referenced by the .dsc
[12:39] <nickoe> just a specification for the way  we package the deb?
[12:39] <nickoe> ok
[12:39] <wgrant> 3.0 (quilt) is what I described earlier, with an orig.tar.gz and a debian.tar.gz
[12:39] <nickoe> great
[12:40] <wgrant> 3.0 (native) is for packags where Debian is upstream, so there's just one tar.gz, not separate Debian and upstream files
[12:40] <wgrant> 2.0 was never really a thing, and 1.0 is mostly obsolete.
[12:40] <wgrant> (the "quilt" in the name refers to the quilt patch system)
[12:42] <nickoe> wgrant: trying to build, with magic debuild, http://dpaste.com/1570278/
[12:42] <nickoe> So I should name my bzr checkout as kicad-ppa.orig?
[12:42] <wgrant> Daily builds are a slightly messy case
[12:43] <wgrant> Because you're building form a VCS repository, there isn't an upstream release tarball.
[12:43] <wgrant> So 3.0 (quilt) doesn't really make sense.
[12:43] <wgrant> People often use 3.0 (native) in that case
[12:44] <wgrant> Anyway, I've just come from 24 hours of planes, so I need to wander off for a bit.
[12:44] <nickoe> ok, but for now I just want to build it locally anyway.
[12:45] <wgrant> Right ,but you can't build a 3.0 (quilt) without an upstream release tarball -- and one doesn't exist, since you're building from a VCS snapshot, not a release.
[12:46] <nickoe> wgrant: I changed to 3.0 (native)
[12:46] <nickoe> the one ppa I try to fork uses just 1.0 in source/format
[13:12] <nickoe> Now it is building, lets see how it goes
[13:13] <nickoe> that will take quite some time on this shity processor
[21:15] <jtaylor> whats this error about: https://launchpadlibrarian.net/163708425/buildlog.txt.gz
[21:15] <jtaylor> no support for utf-8 filenames?
[21:47] <nickoe> jtaylor: isn't it more like python that fails there?
[21:47] <nickoe> I remember that I had to specify encoding with a fancy string even to be able to use unicode in comments
[21:48] <lifeless> jtaylor: bzr supports utf8 filenames just fine
[21:48] <nickoe> jtaylor: is lp running any python scrupts?
[21:48] <lifeless> jtaylor: problem there is the locale is set to C
[21:48] <nickoe> yes, bzr but not python
[21:48] <jtaylor> so how to fix?
[21:48] <lifeless> jtaylor: bzr also supports shift-JIS etc - it doesn't assume utf8 encoding for filenames, it looks for the locale defined encoding to use.
[21:48] <lifeless> jtaylor: set the right locale.
[21:48] <jtaylor> I see it not reaching anything I have control over
[21:49] <jtaylor> in the recipe?
[21:49] <lifeless> jtaylor: probably bug filing time then :)
[21:49] <lifeless> on launchpad itself, not bzr
[21:49] <jtaylor> thats why I'm here
[21:50] <nickoe> the python error for it is more like, SyntaxError: Non-ASCII character '\xc3' in file test.py on line 1, but no encoding declared; see http://www.python.org/peps/pep-0263.html for details    and that is only with python2
[21:50] <jtaylor> so its a launchpad bug and not something I can change?
[21:50] <nickoe> jtaylor: I dunno, I am not knowledagable in lp as such, you helped me earlier :)
[21:50] <jtaylor> I know the error you get it all the time with LANG=C, C.UTF-8 already everywhere in the debian/rules
[21:54] <jtaylor> how likely is it this will even get fixed?
[21:55] <jtaylor> because if I have to ask upstream to rebase their tree, I'd rather do it now instead of waiting a few weeks in limbo
[22:05] <lifeless> jtaylor: I don't know, you'd need to ask an LP developer
[22:05] <lifeless> like wgrant or cprov
[22:24] <jose> wgrant: hey,a round?