[00:18] bug 67384 [00:18] Launchpad bug 67384 in openoffice.org-amd64 "Openoffice keeps crashing" [Undecided,New] https://launchpad.net/bugs/67384 [00:18] woo, ubotu is back === victor__ is now known as victor_ [03:23] hi all, probably otish, but not sure of a better place: if i grab the 'linux' source package ( https://launchpad.net/ubuntu/+source/linux ), does that build the restricted binary packages, or just clean ones? === boomer` is now known as boomer === andres__ is now known as ^4nDr3s [05:04] Hmm, Debian unstable's dpkg refuse to work on the hardy partition. This is going to be tricky... [05:09] minghua: What evil are you trying to commit? [05:10] Fujitsu: Nah, I am completely an innocent victim here. [05:10] Fujitsu: Just bitten by bug #201673. [05:10] Launchpad bug 201673 in glibc "Hardy: "invalid pointer: 0xb7ef4b70" no program will start." [Critical,Confirmed] https://launchpad.net/bugs/201673 [05:14] minghua: You could always manually extract the file in question. [05:15] You can't just mount up your hardy root and dpkg -x a working libc to it? [05:15] * LaserJock was going to mention something about hijacking [05:15] perhaps it's a little late in the evening for that though [05:15] * Fujitsu sends iwj after LaserJock. [05:16] Fujitsu: Yeah, I think that's what I'm going to do. [05:16] minghua: send iwj after me? :( [05:16] RAOF: Using which dpkg? [05:17] minghua: Sid's, presumably, since Hardy's will be linked to a broken libc :) [05:17] RAOF: Exactly. That's why I said "Debian unstable's dpkg refuse to work on the hardy partition" at the beginning. [05:18] RAOF: "dpkg: syntax error: unknown group `mlocate' in statoverride file" is the error message. [05:19] minghua: I think we may be talking past each other. Sid's dpkg presumably works in Sid, right? [05:19] That's probably a symptom, not the problem [05:19] NSS looks busted in Hardy due to the latest glibc upload. [05:19] So, you boot into Debian, mount hardy's root to /media/please-fix-my-root, and dpkg -x libc6_version_that_works.deb /media/please-fix-my-root, right? [05:20] RAOF: "dpkg --root=/mnt --install libc6_2.7-5ubuntu2_i386.deb" in unstable gives the error message above. [05:20] minghua: Ah, you're trying to do something better than me. I was just trying to get you a working libc.so.6, so you could use hardy's dpkg again :) [05:20] RAOF: Okay, dpkg -x directly, I didn't think of that. Thanks, I'll have a look. [05:21] * TheMuso just realized that it will likely break the buildds as well. [05:25] why was libc changed this late in the cycle though I have to wonder? [05:25] these are more of the behaviors you'd expect before alpha1 etc [05:26] Yeah, I think the QA procedure (if there was one) is completely thrown out of the window on this one. [05:26] Such things by no means help us attracting testers. [05:27] Yay for complete conjecture. [05:27] * RAOF likes to think that this was meant to be a useful bug fix :) [05:27] StevenK: By "conjecture" you are referring to my comments? [05:27] minghua: I am [05:27] well it appears that not everyone upgrading is affected though. i've just spoken to a few folks that weren't affected [05:27] hm [05:28] i certainly don't look forward to having to reboot, find a live disk, and try to solve this on my system though. [05:28] StevenK: Sorry I don't quite understand. Whose conjecture do you mean? Glibc uploader's? Mine? [05:29] minghua: Your conjecture. [05:29] StevenK: Which is? [05:29] minghua: That the QA procedure was ignored [05:30] well, the QA procedure here certainly doesn't seem to have included requesting a FFe... [05:30] StevenK: True, it's all my guess. But I hope you can understand my bitterness. [05:34] Blink. My gutsy laptop managed to switch back to gdm from usplash while shutting down [05:34] StevenK: Oh, you haven't seen that before? Happened not infrequently for me (but it seems fixed now). [05:35] RAOF: Nope [05:37] StevenK: I get that when X freezes on shutdown and I have to manually kill it to make the shutdown continue [05:38] It switched back, I thought, "Wow, that was very fast", typed in my username, hit enter, it switched back to usplash, and I went "Oh. It hasn't shut down yet" [05:46] slangasek: Is the "update-alternative sticks at manual status" thing mentioned in bug #199030 a bug (i.e., can be fixed in some preinst/postinst scripts)? Or is it something more sinister? [05:46] Launchpad bug 199030 in scim "Can't close SCIM" [High,Fix released] https://launchpad.net/bugs/199030 [05:48] minghua: can be fixed in a future preinst/postinst [05:49] slangasek: Thanks. Probably not worth it though (I believe the problematic setting only existed in one version, unfortunately it's the version shipped in alpha6). [06:09] nixternal: geeze dude, you had to blog it? [06:10] "malloc this and malloc that everywhere" -- helpful. [06:10] Not. === macd_ is now known as macd [06:28] Why must building Xorg git be so annoying. Also, I'd like the forum universe to stop suggesting that installing the nvidia drivers with envy as the first port of call for any form of problem with graphics. [06:29] Heh [06:31] (sorry for repost) probably otish, but not sure of a better place: if i grab the 'linux' source package (https://launchpad.net/ubuntu/+source/linux ), does that build the restricted binary packages, or just clean ones? [06:35] kgoetz: No, it doesn't. l-u-m and l-r-m are built from their own source packages. [06:35] RAOF: thanks. i was filing a bug on something that may not be redistributable, so i wanted to be sure [06:46] Heh. Nice to see ScottK standing up against CoC slapping. [07:13] good morning [07:15] dholbach: good morning [07:16] hiya boomer [07:16] o/ [07:17] heya :P === shoragan_ is now known as shoragan === \sh_away is now known as \sh [08:11] <\sh> hmm...are we switching back from compiz to metacity and it's new composit world order? ;) [08:16] \sh: And sacrifice Compiz's instability!? Sounds silly. [08:17] argh [08:17] heya Fujitsu :) [08:18] <\sh> Fujitsu: well, seeing kde4 kwin and compositing ... I really don't know what's stability ;) [08:18] Hiya emgent. [08:18] emgent: Were you at the meeting? [08:19] security meeting ? [08:19] Yeah. [08:20] Yes, but I had to leave before the end .. Small problems at home [08:20] <\sh> oh damn...security meeting...my time schedule is too packed in the moment I think [08:21] My topic have been sent to the next meeting [08:21] 6am + being sick == forgetting to attend, sorry. [08:22] ubuntu-pentest team will be start quickly [08:23] I just finally completing "anateater" [08:26] Fujitsu, yesterday kees try to find you about motu-swat [08:26] emgent: I saw the ping, yeah. [08:26] * Fujitsu reads the context. [08:26] meeting log is avaiable [08:26] emgent: What was the motu-swat item? [08:27] membership to join in this team [08:27] What do you mean? [08:27] (and where's the agenda these days?) [08:28] https://wiki.ubuntu.com/SecurityTeam/Meeting [08:28] MOTU-SWAT membership (postposed until motu-swat admins are available) [08:29] What about membership? The requirements? [08:30] Fujitsu, i dont know, it's a keescook topic [08:31] emgent: Ah, thanks. [08:32] Fujitsu, anyway i know who request membership [08:32] Nicolas Valcárcel (nxvl) (nvalcarcel) [08:32] and Andrea Corbellini (andrea-bs) === emgent is now known as emgent`work [09:10] hi, can someone help me to fix the upgrade-disaster in my hardy installation ? [09:11] it died after the new glibc installation. [09:12] cprov, glibc broken: https://launchpad.net/bugs/201673 [09:12] Launchpad bug 201673 in glibc "Hardy: "invalid pointer: 0xb7ef4b70" no program will start." [Critical,Confirmed] [09:13] cprov, anyway for hardy please join #ubuntu+1 [09:13] emgent`work, thanks [09:13] np === emgent`work changed the topic of #ubuntu-motu to: Masters of the Universe: https://wiki.ubuntu.com/MOTU | Want to get involved with the MOTUs? https://wiki.ubuntu.com/MOTU/Contributing | https://wiki.ubuntu.com/FeatureFreeze is underway. Review your changes. | Let's clear http://people.ubuntu.com/~ubuntu-archive/NBS/ for Alpha 6! | hardy glibc broken: https://launchpad.net/bugs/201673 [09:17] Haha, I was *just* about to hit yes on aptitude [09:17] * Laney runs far, far away === \sh is now known as \sh_away === \sh_away is now known as \sh === \sh is now known as \sh_away === \sh_away is now known as \sh === \sh is now known as \sh_away === Scientus_ is now known as Scientus === wolfger_ is now known as wolfger === \sh_away is now known as \sh === \sh is now known as \sh_away === \sh_away is now known as \sh === \sh is now known as \sh_away === \sh_away is now known as \sh [10:35] Is there a debian policy for naming meta-packages? [10:37] most metapackages in ubuntu seem to be named xxx-desktop [10:52] persia: FYI ... Got internet connection at home. So I will be able to smash more bugs and FTBFS now. :-D [10:57] Can someone 'give back' evolution-rss? [11:03] <\sh> anyone has a clue of openbox? [11:09] glibc breakage, right before a freeze/ tasty. [11:10] <\sh> old news... [11:10] <\sh> fix is already uploaded :) [11:10] \sh: there is a big problem now :P [11:11] new glibc FBTFS, bacause try to build with old glibc broken :) [11:11] \sh: i just got home [11:11] <\sh> emgent: the bug is LDFLAGS, the very same bug as with wine 0.9.55 [11:12] yes i saw launchpad bug :P [11:12] i have to go, see you later :) [11:12] <\sh> emgent: I wonder who was the dude who introduced those LDFLAG changes for the dpkg-buildpackage [11:13] \sh: They hit a couple of my packages too, which was infuriating. [11:16] <\sh> Fujitsu: it took us 4 weeks actually to find out that wine doesn't like our LDFLAGS...and now glibc...for me a reason to not introduce newly untested flags [11:18] hi jono [11:18] hey Hobbsee [11:20] <\sh> grmpf...I can't work now... [11:26] <\sh> bah [11:27] <\sh> nice..libc6 ftbfs again...unable to apply some patches... [11:30] It's being dealt with [11:31] \sh: Newly untested flags? They look to be fine in the general case, it's just wine and glibc which are not normal pieces of software that don't work [11:31] DktrKranz2: How did you get on with that example? [11:34] <\sh> StevenK: well, after wine 0.9.54 was out those LDFLAGS were introduced, eventually without any further testing...and now glibc, which wasn't tested, too... [11:34] <\sh> StevenK: so I say, untested flags [11:43] <\sh> StevenK: and yes, I know this can give us speed improvements, but without test-building the whole archive, and see what breaks, this was a change which was really adventure-like [11:46] hi folks [11:46] hi sistpoty|work :P [11:46] hi emgent [12:06] I'm using this "apt-get --simulate dist-upgrade" to get the list of packages available for upgrading but it only gives me the package name and version. Is there an easy way to also get the short description of each package? [12:06] anu buildd admins here? [12:07] slytherin: try #ubuntu-devel [12:07] slytherin: If you want them to rebuild stuff due to libc6 breakage, don't bother :) [12:08] slytherin: Common procedure in these situations (with massive build failures and such) is to retry everything that failed to build within the last X hours. [12:08] soren: No. It is evolution-rss plugin. Looks like just wrong timing for builds caused FTBFS on non-i386 arch. [12:09] <\sh> soren: no. 1 task: make glibc running again ;) [12:11] \sh: It's building as we speak. [12:11] slytherin: Er.. That's what I'm referring to? [12:11] <\sh> soren: you don't mean 2.7-9ubuntu2? [12:11] * Fujitsu looks with confusion at https://edge.launchpad.net/ubuntu/+source/glibc/2.7-9ubuntu2/+build/539089. Is it needing to be built, currently building, or finished building? [12:11] \sh: Yes? [12:12] <\sh> soren: lp said: FTBFS because of a patch which can't be applied...so I think someone is working on 2.7-9ubuntu3 [12:12] \sh: No. [12:12] \sh: No, ubuntu2 now builds OK. [12:12] soren: Oh. But AFAIK, this is not the failure in last 24 hours. It is there for last 3 days at least. [12:12] \sh: It breaks because the buildd's had the broken libc6. [12:12] slytherin: Oh, ok. [12:13] \sh: So it's a buildd issue now. No new glibc is needed. We'll just rebuild 9ubuntu2 and all will be well. [12:13] <\sh> soren: ah so it's just a task of buildd sysadmin to inject a new one which needs to be build with a running system ;) [12:13] <\sh> soren: btw...the bugger is really the dpkg upload from 2008-02-11 ;) with the introduced change to compiler flags [12:13] \sh: I know. [12:13] *shrug* [12:13] :) [12:15] <\sh> soren: seriously: when we start to rebuild all stuff against this new dpkg-buildpackage world order, we will see, that some apps won't run anymore...hopefully it's not much...but we should have tested it before this change went public [12:15] <\sh> well..somehow I'm annoyed, because I can't do my work right now...building packages for the company on hardy fails ;) [12:15] Er... We're in a development cycle. We develop stuff and see what happens. [12:16] Some things break at runtime, and others at compiletime. It's really hard to test automatically for the former, which is what these two cases were. [12:16] The two cases that I hit were the latter, which made things much easier :) [12:18] <\sh> soren: yes...that is not the problem...but introducing some flags which are changing runtime behaviour needs to be better tested before the change...even in a devel cycle. [12:19] <_ruben> having troubles compiling iscsitarget-source .. cant find any filed bugs for it, or perhaps im looking in the wrong place .. gutsy gibbon desktop (as test, want run another test on server later on) [12:19] <\sh> runtime errors are evil...and if the software developer is not at fault, the distro folks are, always ;) /me included... [12:19] * \sh is really bored [12:21] <_ruben> ok, am blind, there's a bug filed for it afterall [12:33] I'm using this "apt-get --simulate dist-upgrade" to get the list of packages available for upgrading but it only gives me the package name and version. Is there an easy way to also get the short description of each package? [12:38] If I update create a patch for configure.in, what is the way to get configure regenerated while building the package? [12:41] promag: apt-get --simulate dist-upgrade |grep Inst|cut -f2 -d' '|xargs apt-cache show|egrep 'Desc|Pack' [12:45] promag: apt-get --simulate dist-upgrade |xargs wajig whatis [12:45] promag: the latter is better if you have wajig installed... [12:54] Hey [12:55] dholbach: I am trying to fix evolution-scalix package. I am patching configure.in. How do I generate configure script in build process? [12:56] slytherin: I'd recommend what seb128 said in #ubuntu-devel [12:56] dholbach: Can you elaborate more? [12:59] mok0: ty [13:02] When I use debuild -S -sa to update a package, it yells that that pyqt is not installed... first time I encounter such a thing... any idea ? [13:02] (it just happens of course for a package that need pyqt) [13:03] huats: you don't have pyqt installed? [13:03] <\sh> huats: if build-dep says it needs pyqt you should have installed it on your system... [13:04] yeah I that is what I figued out also... I am just suprised it is needed for debuild -S -sa [13:05] huats: use dpkg-buildpackage directly then [13:06] ok [13:06] mok0: thanks [13:10] <\sh> huats: hmm...clean rule uses a python script which needs pyqt e.g.? [13:14] \sh: I'll check === cpro1 is now known as cprov [13:31] so ... any chance for a firefox3 beta4 package in the repo? [13:32] DaveMorris: yes. It looks good, but I haven't uploaded it since glibc is broken now. [13:33] DktrKranz2: hi :) you are noticing everything. wicked. (opencv). btw read the comment by Sarah on streamtuner? [13:34] hellboy195: I did [13:35] DktrKranz2: I'll readd it and that's all :) === thekorn_ is now known as thekorn [13:36] hellboy195: IIRC, she said she didn't remove it intentionally, so it seems it can be re-enabled. [13:36] it should not bring in troubles, that's why I was unsure of it. [13:36] * Hobbsee blames MoM [13:37] DktrKranz2: but then the sync blocker is: Move yelp and xmms from Suggests to Recommends <-- do de merge or wait for a debian update if I report the changes back? [13:37] I didn't see any good point to remove it, unless some troubles with buildd or whatever [13:37] Hobbsee: a pleasure to see you here :) You know. Our different timezones ,.. :) [13:38] :) [13:38] * Hobbsee is always here. [13:38] * Hobbsee may be afk though. [13:38] Hobbsee: ^^ true. btw, I use DaD ;) [13:38] hellboy195: are changes really important to justify an upload now? [13:39] if so, we can sync it in intrepid, the important part is to inform Debian guys about interesting changes. [13:39] DktrKranz2: hmm we can wait for intrepid. But report now back to them? [13:39] yes [13:39] :) [13:40] the freeze is not in yet... [13:40] so you can still get it uploaded [13:40] Be sure to check if it hasn't been reported before, and to see if it is good for them (IIRC, it seems so) [13:41] DktrKranz2: yeah I always check ;) [13:41] Hobbsee: it isn't that important. Ah and thx for the supertuxkart ACK [13:41] yay, supertux :) [13:42] DktrKranz2: aren't there discussions here in ubuntu and in debian to remove xmms from the repo? [13:42] Hobbsee: Are you one of the buildd admins? [13:43] slytherin: yes === tb1 is now known as tbf [13:44] Hobbsee: can you give back evolution rss? As per my understanding it has build failure due to wrong timing on non-i386 arch. [13:44] slytherin: given back [13:45] Hobbsee: thanks. [13:45] hellboy195: IIRC, yes. Not sure about progress, though. [13:45] DktrKranz2: well this isn't a real problem. I advice debian folks to replace xmms with xmms2 then if it's stable :) [13:46] there are several plugins still depending on xmms [13:47] DktrKranz2: yeah. I won't get removed in the *near* future I suppose [13:48] oh Hobbsee: can you fiddle with buildd timeouts as well? [13:49] sistpoty|work: i can't cancel builds, so probably not. [13:49] sistpoty|work: one day, launchpad will actually implement that in the UI, then yes. [13:50] Hobbsee: heh, ok... seems like I still need to ping infinity then (though I've not yet managed to be up when he is) to make ghc6 build on sparc (it produces no output for a few hours, so gets killed, but the build would otherwise be fine) [13:51] sistpoty|work: i'd say so [13:51] sistpoty|work: i'm limited on wha'ts in the UI - so only reprioing, giving back, etc. [13:51] i can mark the buildds as dead, or add more too, iir [13:51] c [13:52] ah, k :( [13:52] the rest is Lamont/infinity's domain [13:52] sistpoty|work: Er... Just make it say something? [13:53] hellboy195: probably it will, but not for Lenny, I guess [13:54] sistpoty|work: I don't think expecting builds to be hanging if they don't say anything for hours on end is an unreasonable heuristic. [13:54] We'll see [13:54] soren: it's just a ghc6->gcc invocation (with gcc taking a few hours then). so that would not be too easy, and it would imho be wrong, as the build itself is not buggy (just the timeout too small) [13:55] soren: I don't say anything against the heuristic, just that the timeout is too small ;) [13:55] sistpoty|work: axiom for instance has a loop in its debian/rules that says "I'm still running" or something. [13:55] sistpoty|work: How long is it? Two hours? [13:55] soren: about 9 hours on spooky (but spooky is not the fastest sparc) [13:56] sistpoty|work: The timeout is 9 hours? [13:56] soren: the timeout is 1 hour 30 or s.th., but the longest gcc invocation of my test build took 9 hours [13:57] sistpoty|work: If I have to wait more than a couple hours for the buildd's to figure out that a build has hung, I'll be quite annoyed, I think. [13:57] hellboy195: re bug 201185, is there a way to limit URL to be < 80 chars? [13:57] Launchpad bug 201185 in opencv "Merge opencv 1.0.0-4 from Debian(Unstable)" [Wishlist,Confirmed] https://launchpad.net/bugs/201185 [13:57] (cosmetic) [13:58] DktrKranz2: hmm I already thought about it. I think I can delete the url and only name the patch and the contributor? [13:58] soren: OTOH adding s.th. that circumvents the heuristic would... *erm* be counterproductive as well (if the build would really hang)? [13:58] hellboy195: if it's cvs/svn, you may name revision number [13:59] DktrKranz2: I'll take car [13:59] *cre [13:59] *care xD [13:59] :) [13:59] sistpoty|work: That's a good point, too. [13:59] soren: anyway, I'd rather like a buildd admin handle the issue, and if the advice from him is to produce output, I can always do that then ;) [13:59] hellboy195: it's too early for you to take a car :) [14:00] Does dash support 'if' conditional blocks that we usually use in bash? [14:00] slytherin: yes [14:01] sistpoty|work: Do you see anything wrong with this block? [14:01] if [ $EAPI_MINOR_VERSION -gt 10 ]; then [14:01] EVO_imagesdir="`pkg-config --variable=imagesdir evolution-shell`" [14:01] else [14:02] slytherin: not in the if/then block... does it produce some error? [14:02] sistpoty|work: I am now thinking if there is some problem with variable declaration. Something wrong with comparison [14:02] Well, if EAPI_MINOR_VERSION is not set, the syntax is broken. [14:03] DktrKranz2: untrue ;) [14:03] slytherin: yes, what soren wrote [14:03] hellboy195: really? So it's just us who need to be 18? [14:04] DktrKranz2: yep. Here in Austria you could start with 17 and in the USA even with 16 [14:04] DktrKranz2: and I have the driving license since july 2007 ;) [14:04] heh :) [14:04] c u later [14:05] you too [14:05] see you DktrKranz2 [14:08] Why the heck I can not compare a float with an integer? :-( [14:09] In which language? [14:09] slytherin: FLOORVAL=$(echo $FLOAT | cut -d'.' -f 1) [14:09] slytherin: ^ [14:09] maybe that ^ [14:10] In posix shell? [14:10] soren: bash. Actually I am trying to fix a build failure in which I have to compare evolution version installed to see if it is greater than certain value. [14:10] slytherin: though of course you might want to use bc to really work with floats [14:10] bash doesn't know about floating point [14:10] slytherin: Use dpkg --compare-versions? [14:10] soren: Don't think it will be possible. I am patching configure script [14:11] slytherin: What's the problem, you're trying to solve? [14:11] slytherin: I guess the only way is to split the version string in separate substrings (as a version might have more '.' in it) [14:13] soren: since evolution 2.12, there is no pkg-config --modversion evolution-shell-$version (where $version is evolution version). There is only pkg-config --modversion evolution-shell. So I am trying to fix that part in configure script [14:15] slytherin: if you know for certain, that there can be only one point, you can use echo "${some_version} >= 2.12" | bc -q [14:15] (and check the exit value) [14:16] sistpoty|work: I am not certain about that. :-( [14:16] (bleh... the output of course) [14:18] what if I compare them as string? ex. "$var" -gt "2.10" ? [14:18] I can not do that. :-( [14:19] slytherin: wouldn't work for 2.100 vs. 2.2 for example === Scientus_ is now known as Scientus [14:42] hi [14:42] how can I recover the files in /var/lib/dpkg? [14:45] Does this: https://wiki.ubuntu.com/FreezeExceptionProcess apply also to universe? [14:45] <\sh> Prezu: yes [14:45] \sh: ok, thanks [14:55] so ... any chance for a firefox3 beta4 package in the gutsy64 repo? === dholbach_ is now known as dholbach [15:09] <\sh> slavik: if then only as backport...and only with a handful luck [15:10] :( [15:11] <\sh> slavik: ask asac or any other member of ubuntu-mozilla team [15:12] is there a good place to ask? [15:15] slavik: yes the backport will be planned once ff3b4 hits hardy [15:16] slavik: the ff3b3 final backport is basically ready at the moment, I'd like to do one more upgrade test before sending them off for upload [15:21] jdong: will it be avail today for amd64? :P [15:40] does anyone know how I can recover the file /var/lib/dpkg/available? slangasek? [15:42] slavik: all backports are built for all architectures [15:42] RainCT, check https://answers.launchpad.net/dpkg/+question/12631 [15:42] RainCT: apt-cache dumpavail and dpkg --update-avail perhaps [15:42] jdong: I am sure that the 32bit repo has beta3, I reinstalled 64bit gutsy and the repo shows alpha8 [15:43] Lamego, geser: thanks [15:43] firefox-3.0 | 3.0~b3~cvs20080101t1000+nobinonly-0ubuntu1~gutsy1 | gutsy-backports/universe | source, amd64, i386, powerpc [15:44] slavik: ^^ the archive reports it's available on all 3 archs [15:44] ScottK: did you take a look at Bug #179790? [15:44] Launchpad bug 179790 in tinyerp-server "postgresql listens on :5432" [Undecided,Confirmed] https://launchpad.net/bugs/179790 [15:44] хмм [15:45] http://us.archive.ubuntu.com/ubuntu/ is my repo ... [15:46] ok, weird ... [15:46] why would synaptic only show alpha8? [15:50] persia, ping [15:51] With qa.ubuntuwire.com down, is there another site that hosts similar information? [16:00] cody-somerville: oh, about the ghc6 merge... I've briefly looked over the proposed upstream patch, and it should be fine... however it would imho be good, if you could rebuild a few i386 libraries with the new ghc6 in wrong order to see if there is an ABI breakage [16:02] sistpoty|work, Okay. Do you know if I use my PPA, will it use my ghc6 package? [16:02] sistpoty|work, Or will I have to follow the wiki tutorial on how to utilize local packages in builds? [16:02] cody-somerville: no idea actually, but I guess you could find that out in the build log? [16:02] * cody-somerville nods. [16:04] sistpoty|work, I'll do that right now. [16:04] cody-somerville: excellent, thanks! [16:04] dholbach: around? [16:05] hellboy195: yes [16:06] dholbach: you remember that you unsubscribed u-u-s from circuslinux? [16:06] hellboy195: which bug number? [16:06] dholbach: bug #198796 [16:06] Launchpad bug 198796 in circuslinux "Please sync circuslinux 1.0.3-22 from Debian(Unstable)" [Unknown,Fix released] https://launchpad.net/bugs/198796 [16:07] dholbach: that was a mistake ;) [16:07] dholbach: you should ACK it and subscribe archive-admins :) [16:08] hellboy195: I unsubscribed uus because DktrKranz2 asked you to look into syncing the package [16:08] you're free to subscribe uus to the bug again [16:09] is the corrupt libc6 in the archive fixed? [16:09] mok0: yes [16:09] ubuntu2 should fix it [16:09] hellboy195: somebody in the team will take care of it [16:09] hellboy195: I'm looking into something else right now - if nobody did it until tomorrow morning I'll do it [16:09] 2.7-9ubuntu2? [16:10] mok0: yes, that's what I'm running here [16:10] dholbach: yes BUTI transformed the bug report to a sync long before you unsubscribed ;) [16:10] *BUT [16:10] Hmm, that's not yet available from where I'm syncing from [16:10] hellboy195: sorry for that then [16:11] dholbach: thx [16:11] hellboy195: no need to get blocked on me :) [16:11] dholbach: ^^. no I just wanted to ask if it was a mistake of yours or mine [16:11] ok [16:12] hey Scott [16:13] can you explain me what you mean on bug 193605 [16:13] Launchpad bug 193605 in conduit "Feature Freeze Exception request for Conduit 0.3.8" [Undecided,Confirmed] https://launchpad.net/bugs/193605 [16:13] huats: In debian/changelog there are several references to using internal copies of various packages. [16:14] huats: This is generally bad because it's 2X the code for security support. [16:14] huats: So you aren't just asked for a new conduit version, you are also adding double copies of a bunch of things. [16:14] dholbach: then I'm resubscribing u-u-s :) [16:15] alright [16:15] huats: Which may be reasonable to do if it provides something really wonderful [16:15] ok [16:15] sistpoty|work, What would be a few good packages to include in this test? [16:15] huats: So I'd like to know (in the bug) how taking this on would really enhance the end user experiend. [16:15] siretart, Are there any in particular you think may have problems, etc.? [16:16] RainCT: Do you have some time to work on an archive testing problem with me? [16:16] cody-somerville: haskell libraries, that need other haskell libraries as build-dependency (apt-cache rdepends ghc6 | grep lib will give lots to pick from) [16:17] cody-somerville: in particular, haskell-opengl and gtk2hs are bad candidates, since these have object splitting disabled in the ubuntu delta. all others with other haskell libs as build-deps should be fine [16:18] siretart, Okay. I'll build haskell-opnegl and gtk2hs in my ppa with the merged ghc6 package :) [16:19] cody-somerville: nope, not these two, these don't use object-splitting :P [16:19] sistpoty|work, Okay. I understand you now. [16:20] :) [16:20] sistpoty|work, Ugh... FTBFS due to chroot issues :/ [16:20] ScottK honnestly I don't know, this is a question that I think need to be asked upstream [16:20] cody-somerville: heh [16:21] sistpoty|work, Actually, I think it is a known bug. [16:21] ScottK2: did you take a look at Bug #179790? [16:21] Launchpad bug 179790 in tinyerp-server "postgresql listens on :5432" [Undecided,Confirmed] https://launchpad.net/bugs/179790 [16:22] ScottK2, Hobbsee, TheMuso, norsetto (who doesn't seem to be around): we should really make a decision about the gfortran transition... [16:23] scottk, scottl2 Checked the last clamav release 0.93rc1 no security bugfixes found just bugfixes or enhancements [16:29] Is it okay for a universe package to suggest a multiverse package? [16:30] cody-somerville: yes [16:31] sistpoty|work: I've said go for it in at least one bug. We've started, so we should press on. [16:31] sistpoty|work, if you guys decide on a positive note one of my bug reports gets closed :-) [16:32] ScottK2: ok, I just don't want to overrule s.o. in motu-release since we're talking about a transition here [16:32] Sure [16:32] cody-somerville, I dont mind you doing the merge for gnumeric. Please go ahead. and thanks for the initiative [16:33] sistpoty|work: If I understand it though we've already started this transition, so our choices are part done or maybe complete, right? [16:33] tuxmaniac, Are you sure? You're welcome to do it. [16:33] ScottK2: or revert it (though since iirc ~50% are done, this would seem like the worst option for me) [16:34] sistpoty|work: Right. So forward is really the only thing to do IMO [16:34] ScottK2: same here, and imho best to keep as close to unstable as possible (i.e. even drawing new upstreams in)... but I guess this might be debatable [16:35] sistpoty|work: My suggestion is stop debating and start fixing. [16:35] heh [16:36] I'll file a bug listing all affected packages tonight [16:36] cody-somerville, I will give it a shot. Looks like its gonna be some fun and learning. [16:38] tuxmaniac, Okay. I've done the merge myself so if you change your mind please let me know. === pochu is now known as dxdx === dxdx is now known as pochu [16:44] My sbuilder fails because it cannot see my ~/.gnupg directory. I can I solve this problem? [16:51] Heya gang [16:54] Hobbsee: Can you please give back evolution-jescs? [16:55] slytherin: what is wrong with evo-jescs ? [16:56] huats: FTBFS on non0i386 arch [16:56] huats: just problem with timing of build. Should build now [16:57] slytherin: ok [16:57] slytherin: i was wondering since I am the last updater :) [16:57] thanks for the explanation [16:58] hi bddebian [16:58] Hi sistpoty|work [17:10] * sistpoty|work heads home [17:10] cya === \sh is now known as \sh_away [17:15] scottk, Scottk2 Checked the last clamav release 0.93rc1 no security bugfixes found just bugfixes or enhancements [17:15] leonel: Thanks === Adri2000_ is now known as Adri2000 [17:31] !freezeexception [17:31] Sorry, I don't know anything about freezeexception - try searching on http://ubotu.ubuntu-nl.org/factoids.cgi [17:31] bah [17:32] !FFE [17:32] Sorry, I don't know anything about ffe - try searching on http://ubotu.ubuntu-nl.org/factoids.cgi [17:32] Laney: :P [17:32] Does anything have to be done after a FFe for a sync from Debian is confirmed? [17:33] Laney: bug number? [17:33] hellboy195: bug 201494 [17:33] Launchpad bug 201494 in ubuntu "[FFe] Please sync xmonad-contrib (0.6-4) from debian unstable" [Wishlist,Confirmed] https://launchpad.net/bugs/201494 [17:34] Laney: the 2nd Motu should have subscribed to ubuntu-archive [17:36] wow, we reached the 200000th bug? [17:36] hellboy195: motu-release doesn't necessarily do all the same checks ubuntu-universe-sponsors would do. So if they didn't then uus should be subscribed to review it. [17:36] ScottK: Just said what I experienced personally :) thx [17:38] Hmm, but is there anything to review for a sync? [17:39] that the package builds fine, installs fine, works fine, doesn't introduce regressions or new dependencies in main... [17:39] for example :) [17:41] :P [17:41] So I should subscribe u-u-s then? [17:41] (I did already build + test it) [17:43]