[00:42] LordOfTime: now I am again [00:46] micahg: i emailed one of the people who was testing on the package 'boinc' with the SRU and stuff, got a response I'd like to share with you [00:46] want me to forward the email, or just pastebin it [00:47] fwd is fine micahg at ubuntu [00:51] ugh, system blew up [00:51] micahg: forwarded to ya [00:54] LordOfTime: hrm...ok, if it's really broken, we can SRU .27 I think [00:54] that's not the Debian dev, i should point out, that guy won't respond via email :/ [00:55] but this one is one of the guys who's been working on the bug before I even got to it [00:55] but yeah, thougth you should see that response there [00:55] .24, afaict in Debian, was replaced with .25 almost a day after .25 was released upstream [00:55] and that seems to have fixed most of the crap that was exploding :/ [00:55] * micahg wishes someone would've escorted that into precise [00:55] but yeah, i'll leave this to your judgement [00:56] heh [00:56] i think .25 came out after the last freeze... [00:56] or something [00:56] *shrugs* [00:56] wow, boinc isn't even in testing ATM :-/ [00:57] RAOF: so, we have reports that the version of boinc in precise is totally broken, it's been suggested to SRU .27 as supposedly the version we have was never released to the public [00:57] okay, system implosion, restart time [00:57] * LordOfTime initiates emergency powerdown [00:57] micahg: SRU requirements for packages that don't work at all are pretty low ;) [00:58] RAOF: right, the thing is I don't use the package, so I'm not sure it's true or not :) [00:59] Ah, fun. [00:59] when LordOfTime comes back, we can ask for some verification of the claims [01:14] hm? [01:14] sorry, system explosivity [01:14] * LordOfTime hates Windows, but needed it to fix something in a dev environment [01:18] LordOfTime: is boinc on precise actually broke as claimed? [01:18] micahg: i'd have to double check, i know that it was exploding earlier, but i havent downloaded the repos version (been busy recovering my packaging stuff first). i'm not at my precise environment right now, i'm on a god-awful Windows system, so i'll have to get back to you on that [01:18] (feel free to email me a reminder, i'd appreciate that) [01:19] i won't be at my Ubuntu box until tomorrow [01:19] (about 12 hours from now) [01:19] LordOfTime: sure, no rush, thanks [01:20] mhm [01:20] UGH, windows server systems are awful === jbicha is now known as Guest10547 [10:11] how does one quickly figure out why a package is in main? [10:27] check its rdepends in main, or check the seeds [10:27] reverse-depends or seeded-in-ubuntu [10:27] * Laney high fives tumbleweed [10:28] 118 rdepends which one is the main one ._. [10:29] -c main [10:30] oh nice [10:30] thx === yofel_ is now known as yofel === mhall119_ is now known as mhall119 [16:18] micahg: the person who i've emailed (the response of which i forwarded to you) was able to say that the repos version and the version in your PPA do not work according to that person. I am unfortunately stuck in a strange situation where the package won't even install on my end, claiming dependencies are broken even when they are available for installation [16:18] (the boinc sru thing) [16:18] (from repos) [16:18] hrm [16:19] but granted, my system's still a work-in-progress, and I can't even access my BOINC projects :/ [16:19] so... [16:19] *shrugs* [16:20] * LordOfTime blames Verizon internet being stupid [16:36] hey micahg, random question, but how can I subscribe to all bugs for [given package] [16:36] in Ubuntu on LP? [16:37] LordOfTime: on the main package page, "subscribe to bug mail" on the upper right [16:39] oh, speak of the devil... [16:39] * LordOfTime didnt redalize for the 'nginx' package in ubuntu, the 'nginx' team is notified on new bugs [16:39] that saves me some subscribing :P [19:47] micahg: I'm swearing at 12.04 right now me is one very disgruntled bird at the moment [19:47] lots of issues with 12.04 installation [19:48] eagles0513875: sorry to hear that, please make sure they're filed and hopefully 12.04.1 will be better [19:48] micahg: my issue is mainly related to graphics [19:48] * micahg knows very little about the installer (there's #ubuntu-installer) [19:49] i need nomodeset on grub but if i can't even get to grub to temporarily add that to boot and change it in the grub configuration on the system the system is useless, and the other very annoying issue is when using the live cd it installs grub on the MBR of the usb device instead of the MBR on the hard disk [19:49] oddly though if i use net install this doesn't occur [19:49] /me joins ubuntu-installer and calls it a night === jalcine is now known as jacky === pawdro_ is now known as pawdro [20:35] Hey guys, I'm having some strange key errors when trying to backport a package. [20:36] dput gives me this error: http://paste.welcloud.de/show/NMHlSxhLQ8qsyOgyuf9U/ [20:37] you must first sign the changes file [20:37] And somewhere in the log of pbuilder I've found this: http://paste.welcloud.de/show/Y3Jw4NhEr4Tk9d4nKCNt/ [20:37] with debsign [20:37] and you need to upload the _source.changes, not _amd64 [20:37] But I thought debuild -S -sd did that. [20:37] oh, local [20:37] nm [20:38] it should [20:38] maybe it didn't find your key [20:38] do you have one? [20:38] http://paste.welcloud.de/show/c0GnJ4nOHKTJE4mZjQKj/ [20:38] Yes [20:38] that log signed the source changes [20:38] not the amd64 changs [20:39] which you tried to dput [20:39] So after bpuilder I need to sign the packages? [20:41] yay! [20:41] debsign did the trick. :) [20:42] Okay, one other thing: I want to use this package for building another one. [20:43] pbuilder says that it has mounted my local archive, but it doesn't seem to use the package. [20:43] pbuilder-satisfydepends-dummy: Depends: autotools-dev (>= 20100122.1) but 20090611.1 is to be installed. [20:44] But the archive it mounted: I: Mounting /home/daniel/.building/cache/archive [20:44] did you run apt-get update in a D* script? [20:44] D*? [20:45] a pbuilder hook script run before the package build [20:45] I don't think so. [20:46] I followed this steps: https://wiki.ubuntu.com/PbuilderHowto#Building_With_Local_Packages [20:46] http://wiki.debian.org/PbuilderTricks#How_to_include_local_packages_in_the_build [20:48] I did this: pbuilder update --override-config --configfile ~/.pbuilderrc [20:48] But now my packages is unstrusted [20:49] mm, I sign my archive and import my key in my D hook script [20:50] you can tell pbuilder to allow untrusted packages [20:50] though it might not be a good idea [20:50] So I better add a hook for importing my key? [20:51] does it override the apt trusted keys? [20:51] you could login to the pbuilder and apt-key add if not [20:52] Shouldn't be a script doing 'sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys ....' be enough? [20:55] wouldn't importing the entire keyring take a while? [21:01] Hello there I have a question about uploading fixes to branches. (bzr branch lp:~foo)so I checkout branch then make fix(spelling) to branch then push (bzr push lp:~bobweaver/foo/spellingcheck) Now if I would like to make a new change to foo say a picture do I have to go get the source all over again and start from scratch ? [21:02] like bzr branch lp:~foo (make changes ) bzr commit -m then bzr push lp:~bobweaver/foo/added-pictures [21:03] si the question ius do I have to get new branch every time I want to make change to branch ? [21:03] s|si |so [21:04] it's often easier that way [21:04] or, you can specify a previous merge must go first when proposing your merge [21:05] well, doing 2 merge proposals off the base at once if they touch the same files, just makes more work for the merger [21:06] because they have to go though and look at each thing in the change log ? [21:07] I should be touching changelog everything I touch a branch correct ? [21:07] do you have a bug for each change? [21:08] yup [21:08] but sometimes there is a alot bugs wraped into one [21:08] like spelling [21:09] I guess that I will be more to the point I did something wrong and am trying to fix :) I tried to do it all at once http://bazaar.launchpad.net/~josephjamesmills/ubuntu-packaging-guide/ubuntu-packaging-guide/view/head:/debian/changelog not a good idea [21:11] Why is my package still untrusted, even if I add my keyring using APTKEYRINGS? [21:12] or do you think that that is better off with diff patches if there is no bug. Or should I file bug and wait for it to get approved then fix and then merge branch's ? thanks again for your time [22:05] what's the way to propose an MP for upstream casper? in the past, what i've done is create an actual debdiff and subscribed ubuntu-sponsors to a bug, but in this case, i have a bzr branch and MP i'd like to submit instead of a debdiff [22:07] achiang: have it based on ubuntu:casper, then "bzr lp-propose-merge", it'll automatically end up on the sponsoring queue [22:07] stgraber: neato. thanks. [22:07] stgraber: i have a partial fix for LP: #855556 [22:23] stgraber: hm. http://pastebin.ubuntu.com/995025/ [22:26] achiang: ah right, you'll also need to push you branch to lp first: bzr push lp:~achiang/ubuntu/quantal/casper/bug-855556 for example [22:27] stgraber: d'oh. :)