[05:15] micahg: I would describe the change correctly (not as no change) in debian/changelog, but still use the buildX revision since syncing over it in the future is the right course of action. [05:17] ScottK: right, but shouldn't update-maintainer be run since the build-deps are changing in which case it really should be an ubuntu version? [05:18] micahg: I see buildX as more about what you want to have happen. In this case it's fine. Changing the maintainer would be correct, but I don't think is a big deal. [05:20] ScottK: I see it more of what it is (i.e. a no change rebuild), maybe we should try to get this per-arch rebuild stuff addressed at UDS-O [05:20] micahg: It's a question of cost versus benefit. In this case the cost of being pedantically correct exceeds the benefit. [05:20] I might be being too uptight about it, idk [05:20] micahg: It's a judgement call. [05:21] In any case, versioning build-deps as a guard against misbuilding due to archive skew is a good practice. [06:11] good morning [06:13] good morning dholbach :) [06:13] hi porthose === dholbach_ is now known as dholbach === sresu_ is now known as sresu === sresu_ is now known as sresu [12:53] ffff [12:53] hi === yofel_ is now known as yofel [14:19] hello === sresu is now known as sre-su [14:55] hi hakermania === JontheEchidna is now known as ui === ui is now known as JontheEchidna === dholbach_ is now known as dholbach [16:28] one thing that annoys me about bzr is that when you look at a merge commit, it shows a bunch of modifications as if you did them, instead of them coming in because of the merge. Is there a way to fix that? [16:40] psusi: commit with --author foo? [18:22] ScottK, siretart, happy 0x7db [18:22] o/ === sresu is now known as sre-su [19:40] hmm, firmware-b43-installer does something nasty - during installation, if it detects chipset that isn't supported, it aborts installation and leaves package in the unconfigured state esentially ensuring that people are going to ask "why can't they install anything" (which isn't true - but they get error every time they install something when dpkg tries to configure firmware-b43-installer and [19:40] fails) [21:23] n [21:43] m [22:04] lol [22:06] :) [22:07] ;) [22:24] hi, how can i force the installer to install depends? [22:25] depends should be installed automaticlaly [22:25] yes should.. ^^ [22:25] but I got only the message that this packages are not found [22:26] cybertron: then maybe you don't have the packages [22:26] how are you installing? [22:27] micahg: hm perhaps wrong named? libsfml-system for e.g. [22:27] Laney: dpkg -i [22:27] apt-get -f install [22:28] * micahg usually fires up aptitude after a dpkg -i that fails to get the dependencies [22:28] k ill try [22:28] and atm i got problems with links and dont know why [22:28] so resources files will be searched in the wrong directory if the programm starts [22:29] but one hour ago it works fine [22:34] Laney: i have the deb packet localy so apt-get wont work [22:35] specify it on the same dpkg -i line then [22:35] cybertron: dpkg -i doesn't make any attempt to find packages you don't give it directly. it just tells you that they're missing [22:37] ebroder: right, but how can it force to install them? or tell me another way to install it [22:37] cybertron: if you have the debs locally, what Laney said. if not, use dpkg -i. then run apt-get -f install [22:40] bdrung: any objections to my merging that syncpackage-681693 u-d-t branch? I'd like to base other branches off it. [22:40] k so i have to do it with twi commands [22:41] tumbleweed: i didn't find the time to review it. due to its size i need some time for reviewing. [22:41] bdrung: ok, I'll hold back [22:42] cybertron: there's also gdebi, which i like to use because it can do this in one command, but it's not installed by default anymore [22:42] tumbleweed: ping me again at the weekend [22:42] bdrung: sure, thanks (review is appreciated, and also good motiviation) [22:42] tumbleweed: today i worked on libkibi ;) [22:43] yeah, I guessed that's where your time was being spent [22:43] release coming up? [22:44] tumbleweed: i hope so. i pushed the current version to my ppa: https://launchpad.net/~bdrung/+archive/ppa [22:45] any idea why cant fine my external resources anymore? so if i start my tool it dont find the images anymore [22:46] anyone know how to attach patches to sf.net reports? [22:46] Laney: iirc there's usually a separate tracker for attaching patches [22:46] Laney: patches are separate kinds of sf.net reports, but I thought thye could all take attachments? [22:46] yes there's an attachment bit [22:47] forget it got it... ^^ [22:47] -t [22:47] but I can't figure out how to add one... ebroder: any pointers? [22:48] ah, tracker>patches [22:48] Laney: i think you have to be a member of the project or something to create attachments on bug reports, but i think anyone with an sf account can open a "patch tracker" item? [22:48] * Laney found it, hooray for intuitive UIs! [22:49] * ebroder is really glad that the world is largely moving away from sf as a hosting solution [22:50] launchpad is definitively better than sf, even if they only support bzr. [22:50] github is better than sf, even though it's nominally just code hosting [22:54] hm i wrote a .desktop file for the menu, but if i start it a short window blinks and ends [22:57] is there any chance to see an error msg? [23:12] tumbleweed: i found a nice test case: kibi_format_memory_size_for_display(655360) [23:12] :D [23:52] bdrung: around? [23:52] ari-tczew: yes [23:53] bdrung: I just installed u-d-t daily and trying to handle with pbuilder-dist natty. now should do I use it without sudo ? [23:54] ari-tczew: yes, it should be used without sudo [23:55] bdrung: $ pbuilder-dist natty create Error: Cannot create results directory "/home/ari/pbuilder/natty_result/" [23:55] chmod ? [23:56] ari-tczew: can you remove ~/pbuilder and try again? [23:56] bdrung: hmm.. it requires reintroduce all distros. I guess it's necessary for sudo change? [23:57] ari-tczew: then don't do it. then use chmod. [23:57] * micahg would guess that root owns stuff, so chown would be more appropriate [23:59] $ sudo chown ari -R pbuilder [23:59] works fine