[00:02] ScottK: yeah, I have a much easier time with .doc files than .pdf [00:02] although I did get a nice macro'ized doc file the other day and sent it back and the person said that it was 75 pages of junk ;-) [01:52] hi all [01:52] i'm making a package for hardy [01:53] but I want a backport for gutsy too [01:53] how do I name the backport? [01:53] !backports > matteo [01:54] tnx [01:55] are there plans to ship an svn snapshot of Network Manager 0.7 if 0.7 final isn't released in time for Hardy, or is the fallback plan to ship 0.6.5? I haven't found any relevant info in the nm-ifupdown-death-match blueprint. [01:58] mgunes: I believe that the current thinking is that 0.7 is not going to be more useful than 0.6 by the time Hardy needs to stabilise, but we're still looking into it. [01:59] RAOF, that's what I was thinking; thanks. [02:02] can I tell dh_installman to compress manpages? [02:02] dh_compress should do that [02:02] (I think) [02:03] man dh_compress suggests that it will do it by default. [02:06] RAOF: somethig suggests me that I have to run it after dh_installman [02:07] Probably, yes. Otherwise the man pages you want to compress won't be where dh_compress is looking. [02:07] just before dh_builddeb should be fine [02:10] isn't stupid to compress a manpage of 1.5kb? [02:11] it should be against the policy [02:11] "By default, dh_compress compresses files that debian policy mandates should be compressed, namely all files in usr/share/info, usr/share/man, usr/X11R6/man, files in usr/share/doc that are larger than 4k in size" [02:12] It is not against the policy. [02:13] it may not [02:13] but it's stupid [02:13] Note the "all files in /usr/share/man" part. [02:13] and 1.5 file will be 4k on disk [02:13] Not necessarily. [02:13] ah right [02:14] smart FS like reiser and XFS will move them into the inode [02:14] Ding! [02:14] ;) [02:16] is a bad practice use -jX in the makefile? [02:16] it can overload the buildd [02:16] or the buildd compiles a package at time? [02:18] I'm pretty sure some packages already do parallel-builds (maybe some java packages?). [02:21] mysql uses -jX in it's building [02:22] $(MAKE) -j$(fgrep -c processor /proc/cpuinfo) [02:22] that will work under bash [02:22] but not in make [02:22] any hint? [02:24] matteo: Set a make variable to $(shell fgrep -c processor /proc/cpuinfo) ? [02:24] $(MAKE) -j$(shell fgrep -c processor /proc/cpuinfo) [02:24] yes, found in the docs [02:24] http://theoryx5.uwinnipeg.ca/gnu/make/make_81.html#SEC80 [02:25] * LaserJock kicks his DSL [02:25] go faster! [02:32] matteo: mysql-dfsg-5.0 uses: [02:32] MAKE_J = -j$(shell grep -c processor.* /proc/cpuinfo) [02:32] ifeq (${MAKE_J}, -j0) [02:32] MAKE_J = -j1 [02:32] endif [02:35] mm [02:35] that could be flacked [02:35] let's say a PCu has an ID written in lowercase [02:35] model name : AMD Athlon(tm) 64 X2 Dual Core Processor 4400+ [02:36] and it reads: [02:36] model name : AMD Athlon(tm) 64 X2 Dual Core processor 4400+ [02:36] grep will find twice the values [02:36] grep -c ^processor /proc/cpuinfo [02:36] that is better IMHO [02:36] yeah [02:36] Debdiff's welcome? :) [02:37] E: aacplusenc_0.14_source.changes: bad-distribution-in-changes-file hardy [02:37] can I ignore it? [02:38] yep, it means you're not running hardy [02:38] i'm running hardy [02:38] so it doesn't recognize it as a valid release [02:39] hmm, that's odd [02:39] LaserJock: People shouldn't ignore that, they should install the most recent version of lintian (available in -backports) IMHO. [02:41] minghua: well, I would encourage it, but if it's really important it shouldn't go in -backports [02:41] apt-cache policy lintian [02:41] 500 http://it.archive.ubuntu.com hardy/main Packages [02:41] It's important for developers. [02:41] that's not a backport [02:41] Developers should have a hardy chroot anyway. [02:41] I'm just saying no lintian errors should be ignored. [02:42] If you use gutsy, get the lintian in -backports. [02:42] minghua: well, I disagree slightly, but it is important I agree [02:42] minghua: he's using Hardy he said [02:43] LaserJock: Yes, I am aware of that. I have no explanation to matteo's problem [02:44] i use hardy, and I have a gutsy chroot [02:48] matteo: you weren't in the gutsy chroot? [02:48] no [02:48] i'm at home [02:50] btw, my package is the AAC+ encoder discussed in the forum [02:50] and now packaged into medibuntu [02:52] matteo: What is your lintian version anyway? [02:52] 1.23.42 [02:53] That doesn't sound right... [02:53] $ fgrep hardy /usr/share/lintian/checks/lintian.desc [02:53] distribution should be one of hardy, gutsy, feisty, edgy or dapper. [02:53] I take that back. 1.23.42 is indeed the hardy version. [02:56] matteo: maybe you should check your changelog entry to make sure there's not a typo [02:57] http://pastebin.ca/868056 [02:58] seems fine to me [03:00] weird [03:01] indeed [03:01] btw, 04:01 AM here [03:01] gnite [03:02] http://ppa.launchpad.net/teknoraver/ubuntu/pool/main/a/aacplusenc/aacplusenc_0.14.tar.gz [03:02] this is the package [03:02] if someone will try to figure out the lintian mistery [07:05] Hi all === fabbione is now known as thegodfather [08:31] win 15 [08:31] damn [08:31] lose 19 [09:11] Goooooooooooooooooooood morning Ubuntu lovers! [09:11] * Hobbsee hides under a rock, away from mpt, here too [09:12] hey Hobbsee [09:12] hiya seb128! [09:14] morning other canonicalites. [09:24] * pitti hugs Hobbsee [09:24] * Hobbsee hugs pitti back [09:25] * ion_ unhugs both pitti and Hobbsee [09:25] * Hobbsee gives ion_ the boot [10:05] gpocentek: any news on gnumeric? [10:06] slangasek: I uploaded it 2 hours after you asked me last time [10:06] ah, hmm [10:06] and I installed it from the repos, so I guess it's ok [10:07] slangasek: is there a problem with the package? [10:07] gpocentek: no, I was just misreading the NBS info for goffice :) [10:07] apparently libgoffice-0-5 only depends on itself and can be removed now :) [10:11] ok :) [10:16] hi [10:27] do you know if it exist any tool that allow to find out (and then install) all the build-dependencies of a package which is not debianized yet? I mean get all the libblabla-dev required at build time? [10:32] psicus78: Try asking on #debian-motu [10:35] gouki: #ubuntu-motu maybe? [10:36] dholbach: I just asked, thanks! [10:50] hi all [11:06] lool: hi, are you online ? [11:07] mantiena-baltix: I am [11:07] pitti: hey, do you know if nvidia-glx-config is used anymore? I'd guess restricted-manager has replaced that? [11:08] seems that it was last changed in edgy [11:09] lool: I have few questions about updating cheesy package [11:09] lool: I saw you comments at bug #180624 [11:09] Launchpad bug 180624 in cheese "cheese new upstream version 0.3.0" [Undecided,Incomplete] https://launchpad.net/bugs/180624 [11:12] lool: I wanna to package new cheesy version - 2.21.5 for testing uses (I have about 30 ubuntu users, which have webcams and wanna test ;) ) [11:13] mantiena-baltix: Sure [11:13] mantiena-baltix: Are you Steve? Or what's your name? :) [11:14] lool: so, which would be the easiest way to update cheese package ? [11:14] mantiena-baltix: If you followed the discussion on the bug report, there are a couple of things missing from the initial effort by Steve [11:14] lool: no, I'm not Steve, which reported that bug [11:14] lool: yea, I noticed that === Keybuk_ is now known as Keybuk [11:15] lool: last comment from Steve was: [11:16] Steve Stalcup wrote on 2008-01-18: [11:16] Hi Loïc, It seems there is a new version available. I have corrected everything except for the patches, which seem to be Ubuntu specific. [11:18] lool: is this true ? You wrote about more problems in your comment, maybe Steve was attached updated interdiff ? [11:20] tjaalton: it's not advertised anywhere any more [11:20] tjaalton: except for the package description, I think [11:20] pitti: ok, I'll remove it then [11:20] tjaalton: yes, r-m is the prefered method, it works better, too [11:21] tjaalton: great [11:26] mantiena-baltix: (Sorry, i'm in the middle of another conversation) [11:27] mantiena-baltix: My very last comment in the bug, comment #13, explains how to update the first of the two patches which needs updating [11:28] mantiena-baltix: The first patch is an easy one, so if you're familiar with updating patches, it should be an easy job; if you're not, perhaps you can read the wiki pages on patch systems which I've outlined in the bug report [11:28] mantiena-baltix: When one of Steve or you updates the first patch, I'll check how the other patch (which is much harder) compares to the new upstream and guide you folks into updating it [11:31] lool: I understand all your comments about patches, but I ask are there more problems in last interdiff ( AFAIK http://launchpadlibrarian.net/11198342/cheese_0.3.0-0ubuntu1.interdiff.gz ) [11:31] pitti: please give-back: haskell-alut. Thanks. [11:32] mantiena-baltix: To my knowledge, the last interdiff was pretty good apart of porting of the patches [11:32] mantiena-baltix: There were other minor spurious changes which I'd prefer not seeing, but these were acceptable [11:33] mantiena-baltix: But this was against an older release of cheese; in the mean time a newer one came out, and it might desirable to rebase the changes on the new upstream [11:33] Albeit I am happy to sponsor the intermediate one === stu1 is now known as stub [11:36] lool: btw, could you tell me how to work with these interdiff files ? I did apt-get source cheese from hardy and manually downloaded latest cheese source (2.21.5) and interdiff.gz, how to include improvements from interdiff.gz ? [11:40] mantiena-baltix: gzip ../path/to/interdiff | patch -p1 [11:40] mantiena-baltix: The interdiff is between the current diff in hardy (which is against 0.2.4) and the diff by Steve (0.3.0 I think); you should first apply his interdiff as a patch to the initial diff or as a patch against the hardy source tree (it should work I think), and then uupdate to the new upstream [11:40] usually [11:40] erm, gzip -cd [11:41] or gunzip -c :-P [11:41] or zcat [11:41] you win! [11:41] * lool cooks zpatch [11:42] mantiena-baltix: If you don't succeed, poke me again and I'll provide the commands [11:43] so, I will use gunzip -c , right ? [11:44] mantiena-baltix: zcat is what you want here ;) [11:44] mantiena-baltix: But it all boils down to gzip uncompressing a file and piping the result to patch [11:44] ian_brasil: Hi! I've sent you a few e-mails, have you recieved them? [11:45] nope...don't think so [11:45] yea, I understand this [11:46] ian_brasil: I'm happy to resend them if you priv-msg me your prefered address. === Sp4rKY is now known as Sp4rKy [12:29] lool: so, it seems I finished update, excluding hildon.patch [12:42] dholbach: yeah! Don't know what happened there. === \sh_away is now known as \sh [12:46] how long does pbuilder install take on average? [12:46] depends how fast your net connection is [12:46] i have dsl [12:47] its my first venture into package building, i've always just done tarballs [12:47] should be fun [12:50] lool: still online ? [13:11] mantiena-baltix: Yup [13:15] lool: look at ftp.akl.lt/baltix-linux/Baltix-Ubuntu-packages/gutsy/cheese/ [13:24] zul: how come the xen source package includes the version number? [13:24] mantiena-baltix: Couple of things first: 0.3.0-0ubuntu1 wasn't uploaded, so it would be best to merge the two changelog entries as to have one changelog entry per upload [13:24] Riddell: this for hardy? [13:24] mantiena-baltix: Next, you should use -0ubuntu1 for the Ubuntu revision of new upstream releases [13:24] zul: yes [13:25] mantiena-baltix: The -1 revision is usually reserved for Debian [13:25] Riddell: typo [13:25] zul: it's been doing it for some time [13:25] mantiena-baltix: Bad things can happen if you don't as I think this is used to decide whether the package comes from Debian or not (if you don't have ubuntu in your version string, the package will be merged from Debian I think) [13:27] lool: ok, I forgot it [13:28] mantiena-baltix: Now let me review the 0.3.0 -> 2.21.5 diff... [13:28] Riddell: its something we inherited from debian way back in feisty it can probably be dropped for hardy so its just xen [13:29] mantiena-baltix: In the mean time, I recommend you attach your work, especially the diff, in the bug report; this way, nobody else will redo the same work you already did in the mean time [13:29] lool: wait I minute I will add lithuanian translation into .desktop file [13:29] mantiena-baltix: It's not critical for Ubuntu; translations are usually handled by Rosetta anyway (I think); you might want to send it upstream directly, and we will get it with the next release [13:30] lool: it is enough to attach only .diff.gz (without interdiff) to bugreport ? [13:31] mantiena-baltix: I think at this point it's easier to attach your interdiff; please mention the changes you did relative to the last published interdiff though [13:31] mantiena-baltix: Err your *diff* [13:31] Not your /interdiff/; sorry, typo [13:32] lool: lithuanian translation is critical to lithuanians ;) I'm doing gutsy backport, where cheese is not in main, so, not handled by Rosetta [13:33] mantiena-baltix: Do you mind if we move to #ubuntu-motu as to not flood this chan with universe packages' stuff? :) [13:33] mantiena-baltix: I meant it's not critical to do it in the source package; I think you can do it in Rosetta as well [13:33] lool: ;) AFAIK cheese is in main now ;) btw, I got a build error during building package [13:33] mantiena-baltix: But I'll happy to review it if you do :) [13:33] mantiena-baltix: Wow, indeed [13:34] dh_installdirs -pcheese [13:34] dh_installdocs -pcheese ./README ./NEWS ./AUTHORS [13:34] cp: cannot stat `TODO': No such file or directory [13:34] dh_installdocs: command returned error code 256 [13:34] make: *** [binary-install/cheese] Error 1 [13:34] mantiena-baltix: We can stay here then :-P [13:35] mantiena-baltix: This TODO file was probably dropped upstream but the packaging tries to install it; remove it from the list of docs to install and mention it in changelog [13:35] stupid build system... [13:35] ;) [13:36] mantiena-baltix: Concerning your changes; you properly catched the new librsvg2-dev build-dep, but you mention it was "missing"; it wasn't really missing since the previous version didn't require it -- in the process of the 0.3.0 review, we discovered the package was lacking build-deps (even the current hardy version), hence the mention of "missing" build-dep [13:37] lool: so, librsvg is new build-dep ? [13:37] mantiena-baltix: Exactly, it's simply a new requirement [13:38] mantiena-baltix: You can simply mention "Add a librsvg2-dev (>= 2.18) build-dep" for example [13:38] mantiena-baltix: It's really nitpicking at this point; but since we're at it... ;) [13:39] mantiena-baltix: I just noticed something about the dependencies [13:39] mantiena-baltix: If you diff README between 0.3.0 and 2.21.5, you'll see: [13:39] - - gstreamer-plugins-good-0.10 >= 0.10.15 [13:39] + - gstreamer-plugins-good-0.10 >= 0.10.6 [13:39] In the dependencies [13:40] mantiena-baltix: As you can see, cheese has a gstreamer0.10-plugins-good dependency, but it's unversionned; could you please use the version mentionned in the new README? [13:40] I've noticed this, I think these changes were made by uupdate [13:40] benc: Btw, there’s a fixed nvidia_connected attached to bug #182237. [13:40] mantiena-baltix: Also, what about the "pango" requirement in configure.ac? [13:40] Launchpad bug 182237 in linux-restricted-modules-2.6.24 "restricted manager does not recognize nvidia 8600M GT on hardy" [High,Confirmed] https://launchpad.net/bugs/182237 [13:41] mjg59: ping [13:41] calc: Hi [13:41] mjg59: i am playing with resume on my laptop in 64bit mode and I think I may have gotten further [13:41] Mm? [13:41] mjg59: if i set 3 > /proc/sys/kernel/acp_video_flags it will resume at console [13:42] Right. That's because it's executing the code natively rather than in x86emu. [13:42] lool: whan problems can be with pango ? libgtk2.0-dev depends on pango-dev [13:42] mjg59: but if i add that to a file in /etc/acpi/suspend.d/ and then try to resume i get a blank X window (black screen with a cursor) [13:42] mjg59: is there something i need to do to get X to come back correctly? [13:42] benc: Did my message get though? :-) [13:43] mjg59: i tried disabling save vbe state, post video, and use dpms but i got the black screen/cursor issue [13:43] calc: Figure out why it's not coming back correctly and fix the driver? :) [13:43] mantiena-baltix: It's currently true that libgtk2.0-dev depends on pango-dev but you can't rely on that: first, cheese *directly* needs pango, second, imagine the version of the pango build-dep in cheese is higher than the gtk -> pango dep [13:43] mjg59: ah so its a bug in the driver at that point? [13:43] calc: Fundamentally, failure to resume video is a bug in the driver at any point [13:43] mjg59: when its black like that i can switch VTs to console and console still works ok [13:43] mantiena-baltix: In general, you need to map upstream checks to build-dependencies as close as possible [13:43] mjg59: ok [13:44] mantiena-baltix: Do you mind if I attach the diff I grabbed from you to the bug report and note down the remarks I made above to not let them bitrot in an IRC log? :) [13:44] mjg59: there is/was a bug in Ubuntu where it won't turn on the screen if acpi_video_flags isn't set to non-0 [13:44] mjg59: for even console video [13:44] ion_: don't think so [13:44] calc: Yes. That's because x86emu is broken. [13:44] (somehow) [13:44] benc: There’s a fixed nvidia_connected attached to bug #182237. [13:44] Launchpad bug 182237 in linux-restricted-modules-2.6.24 "restricted manager does not recognize nvidia 8600M GT on hardy" [High,Confirmed] https://launchpad.net/bugs/182237 [13:45] mjg59: would that affect even i386 resumes? it wasn't resuming even on i386 to a console before i set that flags file [13:45] lool: sorry, I don't understand your last message :( [13:46] calc: We had working i386 resume on your system before [13:47] calc: does it help if you close the lid and reopen it? That fixes the "fails to turn on the screen" bug for me. [13:47] or "fixes". [13:47] mantiena-baltix: Do you mind if I summarize what we just discussed in the bug report now? [13:48] mjg59: yea it works in gutsy but is broken in hardy along with several other users here at hardy sprint [13:48] calc: That's probably the change from acpi-support to pm-utils [13:49] I'll be there tomorrow [13:49] Mithrandir: hmm not sure i can try that again, though changing /proc/sys/kernel/acpi_video_flags to 3 works fine on i386, but comes back with a mostly dead X on 64bit [13:49] mjg59: cool :) [13:49] * calc hugs mjg59 [13:49] lool: I'm making new diff.gz now, which includes your wishes ;) [13:49] mjg59: acpi-support is still installed on hardy but maybe its not using it? [13:49] acpi-support is installed but not used for suspendresume [13:50] mjg59: ah ok [13:50] mantiena-baltix: Cool [13:50] mjg59: i guess that could explain why changing /etc/defaults/acpi-support didn't change anything for me [13:51] Yeah [13:51] I need to clean that up [13:51] mjg59: i believe all the affected users here are using i945 intergrated video [13:51] mjg59: me, robert collins, and i forgot who the other person i heard was having trouble [13:52] mjg59: is pm-utils user configurable? [13:52] Yes, but not as trivially [13:52] ok [13:52] Check the quirks in /usr/share/hal/something/fdi/bonghits/misc/other [13:53] heh nice dirname ;) [13:53] Haha [13:56] lool: btw, Do you think, that cheese can depend on gstreamer (>= 0.10.15) and gstreamer-plugins-base-0.10 >= 0.10.15, but gstreamer-plugins-good-0.10 >= 0.10.6 ? [13:57] lool: isn't this strange version (0.10.6) simply a mistake in new README ? [13:57] I think mjg59 means /usr/share/hal/fdi/information/10freedesktop/ [13:57] :) [13:58] I think I prefered that directory name when it included 'bonghits' [13:59] As in, "You'll need some to send patches to files underneath this directory' [13:59] StevenK: well he'd be in the position to make that happen :D [14:01] mantiena-baltix: I think the previous version was a mistake [14:01] mantiena-baltix: I guess they copied the gstreamer-plugins-base-0.10 version for gstreamer-plugins-good-0.10 [14:01] mantiena-baltix: We certainly don't have gstreamer0.10-plugins-good 0.10.15: the latest version is 0.10.6 [14:02] lool: ya, I just noticed this ;) Btw, why we need to use gstreamer 0.10.15 ? cheese compiles fine with 10.14 ;) [14:04] bbia testing s2ram stuff [14:04] mantiena-baltix: It might be runtime features [14:05] mantiena-baltix: Or simply to prevent people from running cheese which this version as the combination might have bugs fixed in the new release -- it's pretty bad to add such dependencies, but many upstreams do [14:13] lifeless: deb http://ddebs.ubuntu.com hardy main restricted [14:13] mjg59: do we have s2ram? [14:13] mjg59: i don't see it installed on the hardy cd or in apt-cache [14:14] calc: No [14:14] calc: Hmm I think it's supposed to be in uswsusp, but I only see s2disk and both [14:14] It's explicitly not built [14:14] It turns out that having three different ways of triggering suspend to RAM that use different pathways and different quirks is mad [14:14] lool: look at new diff.gz in ftp.akl.lt/baltix-linux/Baltix-Ubuntu-packages/gutsy/cheese/ [14:15] lool: no s2* are installed on the cd [14:17] so i need to modify /usr/share/hal/fdi/information/10freedesktop/20-video-quirk-pm-toshiba.fdi for my particular laptop? [14:17] Yes [14:17] Then hal probably needs restarting [14:17] Note that we're slightly different to upstream - a bunch of quirks are enabled by default [14:17] mjg59: what do i use to dump what hal sees for my laptop? [14:17] lshal [14:18] See /usr/lib/hal/scripts/foo/bar/hal-system-power-suspend-linux [14:19] mantiena-baltix: Could you please attach it to the bug report? I'll make my comments them directly [14:19] s/them/there [14:19] * lool needs coffee [14:19] OK, I just compile them before attaching, ok ? [14:19] Btw, There are nothing to translate in https://translations.edge.launchpad.net/ubuntu/hardy/+source/cheese :( [14:19] mantiena-baltix: Sure [14:20] pitti: thanks [14:22] mantiena-baltix: I just discussed this with pitti (thanks pitti!), and two things are needed for it to appear [14:22] mantiena-baltix: First, it needs to be rebuilt since its promotion to main [14:22] mantiena-baltix: that will happen after I sponsor the new cheese for example [14:24] mantiena-baltix: Second, we need to patch cheese's .desktop file to have a X-Ubuntu-Gettext-Domain [14:24] mantiena-baltix: Forget about the second thing: it's done automatically in CDBS packages using gnome.mk [14:24] mantiena-baltix: So you should see the translations imported after the next build [14:24] ;) [14:25] mantiena-baltix: Can you please attach your diff to the bug? Or I can do it if you prefer [14:27] hmm it died, oh well i'll beat on it later [14:27] lool: I prefer you ;) [14:27] mantiena-baltix: What's your name? are you subscribed to the bug report? [14:27] Mantas Kriaučiūnas? [14:29] Yes, I'm subscribed through Baltix-members team ;) [14:29] lool: you should use UTF for my surname [14:29] as in ISO-8859-1 there re no č or ū [14:30] o/c [14:31] um, he /did/ use UTF for your surname? :) [14:49] lool: hey, I already translated 40% of cheese-lt.po ;) [14:50] mantiena-baltix: I've sent my review [14:50] i uploaded my source to my ppa and i got an acceptance email but i can't see anything on the launchpad site. anyone got any ideas? [14:51] Aloha: see #launchpad for ppa support [14:51] Hobbsee, thnx! [15:02] lool: it seems fix_desktop.patch doesn't work :( [15:02] maybe it should be against desktop.in.in, not against desktop.in ? [15:03] mantiena-baltix: Indeed! [15:03] mantiena-baltix: I didn't notice the new file [15:04] lool: btw, new cheese package (without hildon patch) doesn't work in gustsy at all :( [15:29] mjg59: i must be confused as i can't determine how pm-utils suspends a system [15:30] mjg59: it appears to call /usr/sbin/pm-suspend which calls the nonexistant s2ram? [15:30] <\sh> hmm..can someone look why last upload of ipe (from yesterday) and gnucash (from one hour ago) isn't showing up in hardy? [15:32] mantiena-baltix: What do you mean with "doesn't work"? [15:33] lool: I see only grey background, but nothin from my webcam :( [15:33] seb128: I received some words from danw that some fixes are still flowing in libsoup and he wants to up a tarball next WE for 21.90 [15:33] mantiena-baltix: Did the older release work for you? [15:34] looks like pm-suspend calls into /usr/lib/pm-utils/functions pm_main which uses s2ram or blindly just suspends by writing mem to /sys [15:34] but i have to be misreading this or why would that likely ever work [15:35] mjg59: ping? [15:35] calc: if your version of pm-utils is the same as debians that's indeed the case [15:36] sjoerd: you mean it just blindly tries to write mem to /sys/power/state ? [15:36] sjoerd: so this hal stuff doesn't even get used because s2ram isn't included in ubuntu (!?) [15:37] calc: it tries to use s2ram, if that's not available it writes mem to /sys/power/state [15:37] Not sure what happens with the quirks if uswsusp isn't installed [15:37] calc: Hi [15:37] pm-suspend doesn't call s2ram [15:37] Which then writes to /sys/power/state, yes [15:37] lool: ok [15:38] mjg59: it calls pm_main which calls do_suspend which tries to use s2ram [15:38] Yes, but if s2ram isn't there it's fine [15:38] mjg59: so if a machine has any kind of quirks its hosed? [15:38] No [15:38] Quirks are called on resume [15:38] mjg59: since as far as i can tell none of the quirks are used unless s2ram is installed [15:38] lool: there is no hurry anyway, the dav code is not ready to be used yet [15:38] mjg59: oh hmm [15:38] calc: Check the hooks [15:39] lool: 0.24, backported from hardy works fine, 0.3 - doesn't work, same problems like in 2.21.5 [15:40] lool: maybe this is because in gutsy is gstreamer 0.10.14, not 0.15, which is "officially" needed according to devs [15:41] mjg59: i am confused as to where the pm-suspend exported args (if not using s2ram) end up getting parsed/used [15:41] The hooks [15:41] mantiena-baltix: Could be [15:41] <\sh> pitti, ping missing packages and I didn't receive neither an error message nor a positive ack from LP [15:42] mjg59: those are the files in eg /usr/lib/pm-utils/sleep.d/99video ? [15:42] \sh: which source? [15:42] Yes [15:42] mjg59: ok [15:42] <\sh> pitti, ipe from yesterday and gnucash (about one hour ago) [15:42] what channel deals with packaging (.deb) again? [15:43] some master of the universe thing... forgot ..ubuntu-motu ? [15:43] https://edge.launchpad.net/ubuntu/+source/ipe [15:43] \sh: ^ it's not there at all [15:43] yeah that's it [15:43] \sh: sure that you uploaded it? [15:44] <\sh> pitti, Successfully uploaded ipe_6.0pre30-1ubuntu1.dsc to upload.ubuntu.com. [15:44] \sh: hm; cprov, any idea? [15:44] <\sh> pitti, the same .upload file for gnucash [15:44] <\sh> pitti, while octave2.9 from yesterday worked :( [15:45] <\sh> pitti, should I reupload? [15:45] pitti: let me check [15:46] pitti: (Ubuntu Core Developers : no @ found in email address part.) [15:46] hah [15:46] \sh: ^ [15:47] mjg59: ah i understand how it works now :) [15:47] mjg59: thanks for the help :) [15:47] * calc goes back to beating his laptop [15:47] <\sh> pitti, oh well...it's wrong anyways... [15:47] <\sh> cprov, this could be worth a "reject email" ;) [15:47] <\sh> cprov, hiding this error leads to confusion ;) [15:48] who would receive those ? === Amaranth_ is now known as Amaranth [15:48] <\sh> cprov, the uploader? [15:49] we can't find out who is the uploader if the changesfile is broken, maybe when we have authenticated upload backend, but not now [15:49] cprov: Can't you tell from the signature, even if the data is useless? [15:49]