[08:48] hi. so what's the matter with symlinks on windows? i have a project with *1* symlink which i'm willing to delete right now and make a new version -- but won't that 1 create and 2 then remove that on 'pull' on the win machine and still fail in step 1? === Spads_ is now known as Spads [09:21] ok. bzr is wise enough to replay in one big step, so this works. thanks === alexlist is now known as alexlist` [16:10] Im trying to build a package.. when I use checkinstall everything works great. but I want to build it with the intent of putting it on my ppa.. anyhow when I use bzr builddeb -- -us -uc, I get error at the end, take a look here: http://paste.ubuntu.com/8408128/ .. I just dont get it.. Hopefully someone can give me a pointer or two.. [16:16] Well, that's nothing to do with builddeb, or bzr for that matter. 's just compiler warnings/errors. === zyga is now known as tarman [16:21] fullermd_, umm what can I do? anything ? [16:21] it works fine when I use chdeckinstall and make a nice deb file.. but I need it to package for my private ppa. [16:22] Fix the b0rked C code :) [16:22] I was thuinkjing it was the rules file.. [16:22] broken code? its hexchat. compiles just fine.. its the dev 2.11.0 version.. [16:23] just doesnt compile with bzr issued [16:25] Then something in the build process is using different warn flags. [16:26] im still pretty new to this.. anyway to debug that and see whats being passed to display that? [16:29] That way out of my baliwick. Something in the chain of makefiles or invocations. [16:31] fullermd_, thank you anyhow... and yes it seems to do the same thing in anything that I build that I know build with checkinstall or just reg. make.. [16:33] Yes, there's a lot of terribly b0rked an insecure C out there :) [16:36] so your saying bzr is more picky then everything else? [16:38] It's nothing at all to do with bzr. bzr doesn't know anything about any compiling of anything. It MAY be something embedded in builddeb. [16:40] fullermd_, yea I figured that too. I understand bzr is just a main function calling.. im thinking its the mh_make making the rules thats causing the problem.. [16:40] not sure though [16:40] seems to have problems with debian/rules area [16:41] And what I know about debian build processes could be written in 72 point type on one side of a grain of rice... [16:42] debian seems much more easier.. this is for ubuntu that seems to be picky about alot of crap. [16:42] even though they both use deb packages [16:42] and are based of the same concept [16:43] Obviously, the fix is to install a real *BSD O:-} [16:46] call me stupid but what does BSD mean? yes ill still new to all this [16:46] Oh, I'm just trolling a little. [16:47] I been working with computers since 1980 (commodore64) then PC later years.. but only messed with linux a short time. [16:47] I been a windows person for some many years.. [17:29] fullermd_, I managed to get one test project to work. I compiled qbittorrent 3.2.0alpha with no problems. [17:29] using the bzr package way [21:24] Just occasionally, I wish it was possible to have multiple independent bzr workdirs/branches in the same physical directory, each maintaining separate sets of files [23:03] LeoNerd: hou [23:03] how do you suppose it should look on commandline? [23:04] also; howdy :-) [23:25] Hmmm, yeah it'd be quite awkward I'm sure :)