[00:01] doko: thanks a lot for your comments on bug #192887 ! [00:01] Launchpad bug 192887 in ubuntu "FeatureFreeze exception request for sun-javadb" [Wishlist,New] https://launchpad.net/bugs/192887 [00:46] * sistpoty is off to bed [00:46] gn8 everyone [01:22] Heya gang [01:23] hey bddebian [01:23] Hello protonchris [02:08] sistpoty: done, and yes i can give back [02:09] slytherin: (done) [02:09] geser: i have backscroll and highlights. it's OK [02:09] Hobbsee: Howdie :) [02:12] RAOF: good luck! hope you find that before release! [02:12] hey RAOF [02:12] annoying that most people have left before i got to respond to them, though [02:13] git bisect: 10 revisions to go. [02:13] RAOF: Out of how many? [02:14] 20 :) [02:14] It seems to have been introduced pretty quickly after 1.4 was released. [02:15] I would have liked to test git head first, but that seems to be a real pain to build. [02:25] RAOF: woot! keep going :) [02:33] git bisect: 5 to go. [02:34] RAOF: you're an animal :) [02:34] Well, not really. That's a single data point (yay binary search!) [02:53] git bisect: 2 to go. I hope these results aren't invalidated by another bug I'm running into while testing :/ [02:57] * Czessi-m is away: Gone away for now. [02:57] Czessi-m: Thanks very much for that: very useful :( [02:57] * Czessi-m is away: Gone away for now. [02:57] !away > Czessi-m [02:57] * Czessi-m is back. [02:57] ...and Ubutu can get an automated reply message :) [02:58] sorry, wrong checkbox select in konversation [02:59] :) [03:00] Why don't we remove that feature from our Konversation builds? It's useless. [03:05] because people occasionallyl like it? [03:05] But those people are wrong, and should be shunned. [03:05] There are non-Ubuntu IRC channels. [03:06] * RAOF wills this git revision to build. Build, damnit! [03:11] * RAOF hates on X developers commiting code that doesn't build. [03:12] haha [03:13] you mean you want *building* code? sheesh, you're asking a lot! [03:13] It would make it easier for me to help them, yes :P [03:16] :P [03:16] heya gang [03:41] Woo. One more good build. [03:43] RAOF: How many revisions could it be in now? [03:44] 2, apparently. [03:44] 2 to check, at least. Having to skip a bunch of revisions that didn't build hasn't helped. [03:44] Hah! Actually, _none_. [03:45] Right. Time to update that bug. [03:46] Between a working revision and a known bad revision there are 4 revisions that fail to build. [03:46] RAOF: try harder, then. === FlannelKing is now known as Flannel [06:24] Anyone willing to sponsor FTBFS fix for sugar-pippy-activity? [08:09] Aww, curses. The binary blob doesn't work with xserver git. [08:26] any universe sponsors here? [08:27] slytherin: You're after sugar-pippy-activity? [08:27] RAOF: :-) [08:28] Want to give me a URL? [08:28] RAOF: bug 204363 [08:28] Launchpad bug 204363 in sugar-pippy-activity "[patch] Fix for FTBFS" [Undecided,Confirmed] https://launchpad.net/bugs/204363 [08:29] * RAOF 's system is now decidedly non-Hardy. But, man, xorg 1.5 is fast. [08:31] RAOF: How did the bisecting go? [08:32] StevenK: Not bad, not well. There are 4 git revisions which fail to build between the last known-good revision and the first known-bad revision. [08:32] Also, I can't reproduce that bug on my system with the git xserver, because the binary blob doesn't work on the git xserver. [08:34] RAOF: Got an Intel machine you can test on? [08:35] Fujitsu: Umm, not really. [08:35] It suddenly occurs to me that there's a macbook sitting opposite me... [08:36] So, technically, I *could* fire up a livecd on there, build xorg git, and give it a whirl. [08:36] Hm, I could try DRM2 at the same time :) [08:36] If not, I can test it. [08:37] That'd probably be easier. [08:37] Do you have an i386 deb? [08:37] Building the stack on a livecd doesn't sound like a barrel of monkeys. [08:37] Not really, no. [08:38] I've got an i386 deb of libdrm git, but I've been doing all this on the bare filesystem (on an LVM snapshot, to preserve my root). [08:38] morning folks :) [08:38] persia: around? [08:39] Fujitsu: To build xserver git you need to check out a new x11proto-input, you'll need libdrm git, and mesa git. [08:40] I *could* build you packages of all this for you, if you want, but it's probably easier for you to do so? [08:41] RAOF: Right, I can build all that myself, and am on LVM. [08:42] If you tell me where to get the stuff, and and craziness needed to build. [08:43] Fujitsu: You'll need: git://anongit.freedesktop.org/git/mesa/mesa (to pass to the --with-mesa-source configure option of xserver) === rraphink is now known as raphink [08:44] * Fujitsu snapshots and modifies fstab. [08:44] You may well need to build a newer intel driver: git://anongit.freedesktop.org/git/xorg/driver/xf86-video-intel [08:44] ...which will need: git://anongit.freedesktop.org/git/xorg/lib/libpciaccess [08:44] Oh dear, OK. [08:45] You'll need git://anongit.freedesktop.org/git/xorg/proto/inputproto to build the xserver [08:45] And git://anongit.freedesktop.org/git/mesa/drm also, both to build the xserver and to get the new intel drm module. [08:46] Do I just git clone those? [08:46] Yup. [08:46] You might want to use my PPA package of libdrm, though. You'll need to grab the source to build the intel DRM module (I don't build that), but the rest should be easier. [08:47] Oh, and then you'll actually need xserver git: git://anongit.freedesktop.org/git/xorg/xserver [08:48] So... that's 6, or did I miss one? [08:48] No, that's it. [08:50] You _may_ have to copy xserver/hw/xfree86/common/xf86cvt.c from a different xserver source package in order to build properly; I'm not sure if that was something wrong on my end or if it's a problem with git. [08:51] It's really very easy to build xserver git. [08:52] Heh. [08:53] On the plus side, you'll get to try out DRM2, TTM, and all that goodness :) [08:53] No insane (ie. non ./configure; make; make install) build systems? [08:54] No. It's all autotools. And ./autogen.sh calls configure, so you can just call that. [08:54] Aha, thanks. [08:55] What's new in DRM2 and TTM? [08:55] Compiz + opengl doesn't suck any more; EXA is blazing fast. [08:55] Basically, all the rendering glitches go away and everything gets magically faster. [08:57] Here's the xserver autogen line you probably want to use (replacing Temp/mesa with where you've cloned mesa git): ./autogen.sh --prefix=/usr --enable-xorg --with-mesa-source=$HOME/Temp/mesa ... [08:57] ... --with-default-font-path="/usr/share/fonts/X11/misc,/usr/share/fonts/X11/cyrillic,/usr/share/fonts/X11/100dpi/:unscaled,/usr/share/fonts/X11/75dpi/:unscaled,/usr/share/fonts/X11/Type1,/usr/share/fonts/X11/100dpi,/usr/share/fonts/X11/75dpi,/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType" --with-serverconfig-path=/etc/X11/xserver --with-rgb-path=/etc/X11/rgb --enable-freetype --with-xkb-path=/usr/share/X11/xkb ... [08:57] ... --with-xkb-output=/var/lib/xkb [08:57] Hm. Maybe I just want to pastebin that :) [08:57] http://www.paste2.org/p/16797 [09:00] * Fujitsu waits for xserver to clone, then reboots and hopes he snapshotted things properly. [09:01] Heh. [09:01] I plan to blow away this install at some point anyway, so I'm not so totally concerned there :) [09:04] slytherin: Any tests I could perform on that package? [09:06] Do I need FreezeExceptions atm for bug fix syncs from Debian? [09:13] pkern: Not unless they introduce new features. [09:14] RAOF: ok [09:18] RAOF: Do I actually build mesa, or just point xserver at it? [09:18] Fujitsu: Just point xserver at it... [09:18] Fujitsu: Actually, no. You'll need to build it, won't you. [09:19] Because you'll actually be _using_ mesa for your 3d. [09:19] Aha, indeed. [09:20] Hm... I'm not sure precisely which branch you'll want. ./autogen.sh --disable-glut should apparently work to build it, though. [09:20] I was just trying to find out what I needed for GLUT. [09:20] GLUT only builds you the xdemos, you probably don't care about it too much. [09:21] Ah. Right. [09:34] Hi folks; I am about to request syncs for elisa* packages in version 0.3.5 which were completely broken a couple of weeks ago and for which I got green light to push 0.3.4; 0.3.5 is just a followup release with some bug fixes from upstream and only affects some modules [09:34] If you think I need a formal exception, please ack #204555 :) [09:35] lool: If it's only a bugfix release, no approval is required. [09:36] Ok; /me carries on to ubuntu-archive [09:38] RAOF: Is xserver meant to take ages to configure, with no output? [09:38] (And thanks:) [09:38] s/:/! [09:54] RAOF: Sorry I was away. You can only try it if you have sugar environment installed. [10:54] good morning, MOTUs [10:55] I've got a question on the PackageUpdate wiki page... [10:55] step 4 instructs me to copy the packaging into the new source, but I don't have those files at this point... just the dsc I've downloaded [10:57] can somebody point me the right direction on this? I assume it's because I didn't dget the source? [10:57] wolfger: yes [10:57] dget downloads all files [10:58] dsc, orig.tar.gz, diff.gz [10:58] and with dget -x ... it will also unpack the sources [10:59] ok, thanks [11:03] Fujitsu: Sorry. No, xserver too a while to configure for me, but it spewed the usual copious autotools verbiage at me. [11:04] RAOF: I ended up having the wrong automake, I believe. [11:04] Oh. Right. [11:04] RAOF: It's building now. [11:04] Yay! [11:04] I thought I filed a bug against it for 1.10 support, and it was fixed? [11:04] 1.10 worked. [11:04] I had 1.7, I think. [11:04] Ah. Crazy old versions :) [11:04] Indeed. [11:06] Fujitsu: Good luck. I'm off to sleep. [11:07] Night RAOF. [11:07] Thanks for trying to get rid of that bug. [11:07] Enlightened self-interest. Yay open source! === asac_ is now known as asac [11:08] Indeed. === \sh_away is now known as \sh [11:58] Hey [11:59] <\sh> moins [11:59] <\sh> hmm..ports.ubuntu.com is slow today :( [12:00] Hi \sh [12:00] \sh: I need you :) [12:00] <\sh> sebner: well I needed my sleep first ;) so I just woke up ;) [12:00] <\sh> just working down my todo [12:01] \sh: ^^. nvm. if you have time bug #196878 [12:01] Launchpad bug 196878 in xmoto "Modified .desktop for easier use with submenus" [Undecided,Fix released] https://launchpad.net/bugs/196878 [12:02] <\sh> sebner: what's up with that? [12:03] \sh: you introduced a xmoto-edit.desktop -> 1) it doesn't show up in the applications menu 2) upstream doesn't have plans for it. sispoty told me ... [12:03] RAOF: any more luck? [12:04] <\sh> sebner: hmmm..no..there was another package named xmoto-edit at some time, could be a left over [12:04] <\sh> sebner: xmoto-edit but was removed [12:05] \sh: fine. than I can sync new xmoto version from debian :) [12:05] <\sh> sebner: just make sure that the .desktop files are valide....test them before with desktop-file-validate [12:06] \sh: already done ;) [12:06] <\sh> sebner: cool [12:06] <\sh> oh that's I word we are not able to say anymore since we have a nick named cool ,-> [12:06] <\sh> s/I/a [12:06] hrhr [12:06] \sh: I would have asked you yesterday if you were online ^^ [12:07] <\sh> sebner: I wanted to do some things after work but I was so tired, that I slept away when I came home and layed down [12:07] \sh: np ;) [12:09] Hobbsee, RAOF: After building and installing all the bits, I have no DRI. :( [12:11] hoi RainCT [12:13] * jdong has seeded 85GiB worth of beta desktop ISOs :) [12:13] that's the first time I've went over 100 for a seeding ratio :) [12:14] Can anyone please tell me how can I use rsync to update ISO? [12:14] jdong: ah you reminded me on seeding the hardy final. thx :) === doko_ is now known as doko [12:51] Hi I try to create a vlc pakage using the --enable-mediacontrol-python-bindings setting... and i get a permission problem for /usr/lib/python2.5/site-packages/vlc.so [12:51] any ideas? [12:52] HEya gang [12:52] heya bddebian [12:53] Hello sebner [12:54] Hobbsee: Are you still around? [12:54] noone? [12:55] elmargol: vlc is in Main. You might have more luck in #ubuntu-devel. [12:55] thx [12:57] ScottK: ish [12:57] Hobbsee: Would you please ack Bug #204597 [12:57] Launchpad bug 204597 in dkim-milter "FFe for dkim-milter 2.5.1" [Undecided,New] https://launchpad.net/bugs/204597 [12:58] Hi bddebian! [12:58] Heya geser [13:06] ScottK: would you ack bug #202518 and bug #203919 for me? [13:06] Launchpad bug 202518 in audacious "[FFe] Please sync audacious 1.5.0-1 from Debian(Unstable)" [Undecided,New] https://launchpad.net/bugs/202518 [13:06] Launchpad bug 203919 in audacious-plugins "[FFe] Please sync audacious-plugins 1.5.0-1 from Debian(Unstable)" [Wishlist,New] https://launchpad.net/bugs/203919 [13:06] Give me a few minutes and I'll have a look. [13:07] ScottK: thx :) [13:10] \sh: already testing nexuiz debian packages? :P [13:11] <\sh> sebner: It's on my todo list on point 6 :) and I worked down to point 3 :) [13:13] \sh: fine. fine :) [13:20] sebner: "Pulseaudio-by-default is broken so we should sync it" isn't really a good reason. [13:21] sebner: I think you need to go look at the impact of dropping the Ubuntu changes and explain it better. I'd also like to see a description of the testing you've done. [13:23] sebner: From reading the bug, all I know is "Someone said pulse-audio-by-default is broken." [13:23] ScottK: oh. sry if it's not clear. I tested it. Do you also want to see screenshots? [13:24] sebner: I don't see anywhere in the bug where it says you tested it. [13:24] sebner: Good text is always better than screenshots. While a picture is worth 1000 words, that does make it 1000 times more complicated to understand. [13:24] sebner: Also did you test if pulse-audio-by-default is broken? [13:25] ScottK: yes. both. all. :) Otherwise I wouldn't have changed it to a sync. Sry for not documenting it [13:25] sebner: I noticed a whole stack of FFes in my inbox from you that I haven't had time to digest yet. I'd encourage you to go back on all of them and make sure you describe the testing that was done. [13:26] sebner: Now that we're past beta and moving toward RC, we will get pickier about testing and verification. [13:27] sebner: Also, with the FFe's you're filing for RC bug fixes, it's probably worth a look (if you didn't) to see if the bug fix can be extracted and applied to our current package rather than jumping to the new upstream. [13:27] ScottK: yeah sure. audacious is an exception. Most of the other FFe never had remaining ubuntu changes and does have RC bugs [13:27] Even the ones with RC bug fixes need testing. [13:28] ScottK: understood. I will (again) go through all FFe's I filed. Do I attach some words to audacious now? [13:32] sebner: Only if you want me to ack it. [13:32] ScottK: ^^ [13:32] * sebner in on the way [13:36] emgent: uploaded #202422 [13:36] bug #202422 [13:36] Launchpad bug 202422 in smarty "CVE-2008-1066 smarty allows attackers to call arbitrary PHP functions via templates" [Medium,Fix committed] https://launchpad.net/bugs/202422 [13:36] ScottK: f5, please [13:37] emgent: I am not going to push to soyuz until monday though [13:37] ScottK: may I also copy this text to the plugins? [13:37] emgent: thanks! [13:38] sebner: If you tested them the same. [13:39] ScottK: ok [13:44] sebner: Audacious and plugins approved. [13:45] ScottK: thank you and sry again. :( Will keep that in mind for the future [13:46] hoi siretart [13:46] hoi sistpoty [13:46] hi folks [13:47] hi sebner [13:47] sebner: so you're spamming motu-release again :P [13:47] sistpoty: sry. ScottK already told me. Won't do in future [13:47] Just after intensive checks [13:47] sebner: heh, if the there are good fixes we should pick up, there's nothing wrong ;) [13:48] sistpoty: Would you please ack Bug #204597 [13:48] Launchpad bug 204597 in dkim-milter "FFe for dkim-milter 2.5.1" [Undecided,New] https://launchpad.net/bugs/204597 [13:48] sistpoty: yeah but maybe we can extract that fix instead of always jumping to new upstream [13:48] * sebner is now doing intensive investigations [13:49] sebner: Now that Beta is out, reverse merging is generally preferred, as it is often safer (although jumping may be appropriate sometimes) [13:49] persia: :) it's my first beta phase ^^ [13:50] sebner: What you're doing is very good. We're just doing some education along the way. Keep it up. [13:50] ScottK: btw, for graphicsmagick. Just attach the links. like http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2007-4985 [13:50] ImageMagick before 6.3.5-9 allows context-dependent attackers to cause a denial of service via a crafted image file that triggers (1) an infinite loop in the ReadDCMImage function, related to ReadBlobByte function calls; or (2) an infinite loop in the ReadXCFImage function, related to ReadBlobMSBLong function calls. (http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2007-4985) [13:50] sebner: Understood. That's why you get pointers rather than complaints :) Thanks a lot for chasing the RC bugs. [13:51] ScottK: acked [13:51] sebner: If you look, you'll see there's a specific place for cve links on the right where you just input the cve number. [13:51] sistpoty: Thanks [13:51] ScottK: ah. great thank you. never used that before :) [13:52] sistpoty: and also sry to you for such a bad documentation on audacious. Though we talked about it. Nevertheless. sry. [13:52] sebner: heh, no need to apologize [13:54] Well, a clear style and documentation is always important :) [13:54] * sistpoty just switched to kde4 and seriously considers switching back to kde3 *g* [13:55] sistpoty: or even better. to gnome :P [13:55] :P [13:56] persia: np. I also want a *better* ubuntu though I'm not using any software which is on ubuntuwire and has RC bugs :) [13:57] sebner: Gnome is better only if you happen to like Gnome. Not all of us feel that way. [13:57] sistpoty: yeah, it's a bit like that... [13:57] sistpoty: kde4 is for enthusiasts at this point IMO, not actual use. [13:58] ScottK: yeah. because of that I used ":P" which means that's only a joke :) [13:58] Hobbsee: well, it's nice and everything and I don't have real big problems, but it feels somehow unorganized (maybe I'm just too used to kde3 *g*) [13:59] sebner: Understood. If I thought you were serious you'd have got a much grumpier reply. [14:01] ScottK: ^^. Nevertheless I should avoid to joking in english. It's simple not working [14:04] Hi I have new candidate https://bugs.edge.launchpad.net/ubuntu/+source/easycrypt/+bug/203145 that has got an ack for its release freeze bug https://bugs.edge.launchpad.net/bugs/204073 does it need any more action from me please [14:04] Launchpad bug 204073 in easycrypt "FeatureFreeze Exceptions for easycrypt-0.2.2.8" [Undecided,Confirmed] [14:05] StevenHarperUK: You have an approved Feature Freeze exception. It's still up to you to get an upload sponsored. [14:05] Hobbsee: please give back haskell-edison on sparc, thanks! [14:05] Its already in hardy - is an upload sponsored a different thing [14:06] it new candidate [14:06] *its a [14:06] siretart: Ping. I'd like to discuss SE Linux packages when you have a moment. [14:07] StevenHarperUK: I'm confused. It's already uploaded? [14:07] ScottK2: what's up? [14:07] 0.2.2.6 is already in hardy - I need to get 0.2.2.8 up during the freeze [14:07] siretart: Did you see manoj being upset that we forked the SE Linux packages yesterday? [14:07] sistpoty: done [14:07] Hobbsee: thanks! [14:08] as TrueCrypt 5.1 has Finally been released, so it actaully works on Hardy [14:08] siretart: I thought when we talked about SE Linux at UDS there was consensus not to do that, but we seem to have. [14:08] 0.2.2.6 doesnt work on Hardy at all [14:08] 0.2.2.8 does perfectly [14:08] I thought I had to get a Feature Freeze exception to get it updated [14:08] I have done that [14:08] Is there now another step? [14:09] StevenHarperUK: Yes. It has to be uploaded. For that you need sponsorship since IIRC you aren't a MOTU. [14:09] ScottK2: well, I *think* it went like this: Manoj updated his packages pretty late, and was pretty unresponsive when the tresys guys worked on selinux in ubuntu [14:10] Right. He was practically MIA for a while. [14:10] ScottK2: OTOH, manoj was offered help in packaging, which he rejected [14:10] StevenHarperUK: The sponsor queue has been unfortunately lagging the past few weeks. If you've an approved FFe, it's very likely to get uploaded, but it may take a bit more time. [14:10] ScottK2:how do I get sponsorship? [14:10] persia: does it require an action from me? [14:10] StevenHarperUK: Put a .diff.gz in the bug if it's not there already and subscribe ubuntu-universe-sponsors if it's not done already. [14:11] Thats all done [14:11] siretart: I think he just got really busy with work and was not paying attention to Debian for a while. [14:11] StevenHarperUK: Then no. Nothing more you need to do [14:11] siretart: So now he's back and about to upload current packages to Debian. [14:11] he already did [14:12] debian is ATM more uptodate than ubuntu [14:12] siretart: In setools we did a wholesale renaming of binary packages (he hasn't uploaded that one yet). [14:13] <\sh> StevenHarperUK: can you add a debdiff to bug #203145 ? I don't like this interdiff stuff ;) [14:13] Launchpad bug 203145 in easycrypt "Candidate revision easycrypt_0.2.2.8-0ubuntu1" [Wishlist,In progress] https://launchpad.net/bugs/203145 [14:13] ScottK2: and IIUC, he doesn't intend to pick up that change [14:13] <\sh> StevenHarperUK: and assign the bug to me...I'll take care about it [14:13] siretart: I'm concerned in setools because with the package renaming we have either a forked package and an upset DD or we rebase on Manoj work once he uploads it. [14:13] \sh: You really want a debdiff for a new upstream? Why not the diff.gz? [14:13] siretart: That's my understanding. [14:13] <\sh> persia: or this...but I don't see a diff.gz [14:14] siretart: So I think maintaining a permanent diff is not a good plan. [14:14] ScottK2: well, you guys also replaced his packaging with cdbs, right? [14:14] \sh: its an interdiff [14:14] <\sh> StevenHarperUK: then please add a diff.gz [14:14] siretart: You guys doesn't include me. [14:14] But yes. [14:14] StevenHarperUK: Do note that the process has changed, and diff.gz files are now requested (and yes, the documentation is out of date) [14:14] ScottK2: ah, sorry. ok [14:14] persia: whats the command to generate that please [14:14] <\sh> StevenHarperUK: debuild -S -sa ? ;) [14:14] siretart: My thought is to go through and merge from Debian and rip out the gratuitous changes. [14:14] StevenHarperUK: I typically use `debuild -S -sa` [14:15] siretart: But I'm concerned about doing it late. Since you were involved in the UDS discussion, I wanted your perspective. [14:15] <\sh> persia: I thought there was already a debian pkg available ;) [14:16] persia: I do this >debuild -S -sa -kD330E9E8BEE08F9E -I\.svn -tc already [14:16] \sh: Not for that upstream. It's Ubuntu local. [14:16] ScottK2: well, it was done just around FeatureFreeze. IIRC, the packages have been tested even FF in the ubuntu-hardened PPA, and got uploaded in time [14:16] persia: how does that make a diff againsta previous version? [14:16] StevenHarperUK: Then you should have an updated -0ubuntu1.diff.gz in the parent directory. [14:16] so I don't have the impression that this change was unreasonably late [14:16] <\sh> StevenHarperUK: so upload the .diff.gz from the package you created [14:16] siretart: If not for all the package renaming, I'd just wait and do it at the start of Intrepid. [14:16] k [14:17] siretart: It'd be late to revert the cdbs stuff now it my concern [14:17] ScottK2: FWIW, the energy spent on the iscsi-related as far too late in the release cycle [14:17] Agreed. [14:17] ScottK2: and not really an option, IMO [14:18] his packaging does heavily rely on his way of using tla. it is totally unreasonable to get familiar with that way of packaging just for the selinux packages [14:18] siretart: For this cycle on selinux I'm a lot less concerned about package content alignment with Debian than I am package naming. [14:18] Yes, but this was already considered at UDS. [14:18] I remember you showing me some of his packages. [14:19] TBH, the way the ubuntu selinux packages are maintained really scares me [14:20] I mean the bzr branch. that's really scary [14:20] but as long the guys keep on working on that, I won't tell them how to use bzr [14:20] I don't see a lot of other packages by the guy whose name is in the changelog, so I don't know about that either. [14:22] siretart: The big concern I have is keeping relations good between Debian and Ubuntu. I know manoj packages are hard to deal with, but I think that's the price of being downstream. [14:22] \sh: its done now diff.gz uploaded - LP#203145 [14:23] ScottK2: I do hope that the tresys guys are again at UDS in Prague. We should discuss this in person there [14:23] \sh: Is that ok [14:23] siretart: So you'd be against changing packages for Hardy to realign with Debian? [14:24] depends on what you mean with 'realign'ing [14:25] siretart: At a minimum, I'd like to get the package namespace aligned so we don't end up carrying transitional packages for multiple releases. [14:25] ScottK2: that sounds indeed reasonable [14:25] With the idea that we'd rebase to a mimimal diff from Debian in Intrepid. [14:26] \sh: do you have everything for the easycrypt package now? [14:26] As soon as manoj uploads setools then, I'll look at that difference and mail ubuntu-devel. We can pick it up there. [14:26] siretart: ^^^ [14:27] yes, sounds like a plan [14:27] \sh: I cannot assign the bug to you : I dont know what your LP name is [14:27] persia: does bug 203145look complete enough now please [14:27] Launchpad bug 203145 in easycrypt "Candidate revision easycrypt_0.2.2.8-0ubuntu1" [Wishlist,In progress] https://launchpad.net/bugs/203145 [14:29] StevenHarperUK: I'd encourage more detail in the description, but all the necessary bits are there, and the right teams are subscribed. [14:29] persia: So more of an explanation : add another comment?? [14:30] No. Edit the description to explain about the update, etc. [14:30] Too many comments tend to get lost after a while. [14:30] ok [14:32] persia: Thanks I have done that - I didn't realise you could edit the description [14:32] StevenHarperUK: Ah. That explains it :) [14:32] persia: it all makes sense! [14:33] persia: thanks for telling me more - I have to go now the wife want me to tidy up the house [14:34] StevenHarperUK: Thanks for working with us to get your updates in, so we don't have to poll upstream so much. === algo is now known as algos === larala is now known as Qtpaxa [14:53] gpocentek, ping [14:56] ScottK | Hobbsee: bug #196073 needs another ack [14:56] Launchpad bug 196073 in libpciaccess "Please sync from libpciaccess from Debian unstable" [Wishlist,New] https://launchpad.net/bugs/196073 [14:58] * ScottK2 looks [15:00] sistpoty: I asked for test results. [15:01] cody-somerville: pong [15:02] ScottK2: ok, thanks [15:02] tjaalton: ^^ [15:02] In a debdiff for main: Shouldn't Original-Maintainer be the Debian developer and Maintainer be Ubuntu Core Developers? [15:02] sistpoty: Now that we're past beta, I think we need that for all FFe's. [15:03] hefe_bia: Yes. See https://wiki.ubuntu.com/DebianMaintainerField [15:04] ScottK2: well, I assume from everyone filing an FFe to have the package tested actually, but having something written to the bug report would make some sense, yes [15:05] Well I guess it depends on who it is to some extent, but I think they ought to say it. It's actually listed in the FFe page as a required element. [15:05] ScottK2: thanks [15:06] ScottK2: *nod* [15:06] * persia believes everyone should provide test results, even if they have a strong track record for perfect updates [15:06] sistpoty: Is there an easy way to find if there's been a soname change without building a package? [15:07] ScottK2: looking at debian/control... but of course no SONAME change doesn't always guarantee that there shouldn't be a SONAME change ;) [15:07] sistpoty: I'm packaging a new upstream and I need to tell if there should be. [15:08] ScottK2: You need to review the ABI manually, pretty much. [15:08] I'm doing clamav 0.93 RC1 so I can be ready if they release before we do. [15:08] ScottK2: If the upstream is well behaved, the SONAME is defined in the build system, but few upstreams should be trusted implicitly. [15:08] ScottK2: well, you'll need to build the new shared object, but of course grab the shared object from the old deb for diffing [15:08] sistpoty, persia, and broonie: Thanks. No shortcuts then. Of I go .... [15:09] For ClamAV sgran may already know the answer. [15:09] ScottK2: Depending on the code, you might be able to write a script that examines the code for public objects and their formats, but it's typically easier to build :) [15:09] oh, persia: you know some bits about java in ubuntu, don't you? I'm pretty clueless about bug #193386 [15:09] Launchpad bug 193386 in ubuntu "Feature Freeze Exception for glassfishv2" [Undecided,New] https://launchpad.net/bugs/193386 [15:09] broonie: He told me that since Lenny is getting it's first touch of frost, he wasn't touching release candidates anymore. Hopefully I get this right and he can just use it when the time comes (we cooperate pretty closely). [15:10] Err. I've been hiding from that bug for weeks :) [15:10] heh [15:10] persia: They're playing nice with it. I would appreciate it if you'd give them a good review. [15:10] I don't have a quick answer, although I have a fair backlog of email from upstream about it. I'm going to bed soon, but will be sure to comment in the morning. [15:11] ScottK2, persia: actually I'm not really asking for a review right now, but rather if the package would fit in the archive (of course then, if the FFe is granted, we'd need to review the package) [15:12] ScottK2: I'd agree. I'm fairly happy with Nitya. My objection was mostly that I didn't see the point of Sun-branded derby vs. vanilla upstream. That seems to have been resolved in favor of JavaDB for Hardy, so at this point I don't have specific objections, and just need to review it. [15:12] For intrepid, I'm hoping someone packages Apache derby so we can drop JavaDB (as I have had several people report that there are no functional patches, just branding and licensing changes). [15:13] (unfortunately, my Java Packaging is not yet at a point where my first package is acceptable enough to submit, so it likely needs to be someone else) [15:15] sistpoty: Ah. In that case, the main issue is whether we want to have both GlassFish 1 and GlassFish 2 in the archive. It is a new upstream version, but the transition isn't easy, and applications need to be ported. We don't have any reverse dependencies, but Sun doesn't think users should have to switch if they don't feel like it (or at least that was the state before I fell behind in my email, and I'm still not caught up). [15:16] persia: ok, so it's not really completely overlapping with s.th. in the archive, right? [15:16] From what I understand, the packages have been arranged to work in parallel, and there has been testing on hardy by Sun Quality Engineering, so it should be safe. [15:16] Right now the choice is glassfish 1. The decision would be do we offer the glassfish2 choice or not, right? [15:16] No. There ought be no overlap except in mindshare. [15:16] RIght. It's a matter of whether we offer the choice. [15:17] ok, I guess I don't have a problem granting the FFe itself [15:17] The alternative I was hoping for (although my unplanned absence made this hard) was to have only glassfish 2, and an entry in the release notes. [15:17] however the hard part will be to get the package reviewed then [15:17] I think it's very late for that. [15:17] (galssfish 2 only) === gary4gar is now known as cool [15:17] Yes. Far too late for that. [15:17] gal/gla [15:18] A month ago, it might have been possible, but my activity has been insufficient for about that period of time :( [15:19] hm... so what do we do with this FFe? *shrug* [15:19] * jdong kneels down before confessions. [15:19] I just wrote the most evil python script in the history of mankind. [15:20] sistpoty: I say approve it. [15:20] an automatic sysv to upstart converter [15:20] ScottK2: ok [15:21] sistpoty: I acked first, so you have to approve ;-) [15:21] heh [15:21]