/srv/irclogs.ubuntu.com/2009/03/11/#ubuntu-devel.txt

_cooper_Hi.00:00
_cooper_I'm about to generate an ubuntu package and found in the PackagingGuide how to name the package.00:02
_cooper_The guide says:00:02
_cooper_"If a Debian package has been changed in Ubuntu, it has ubuntuX (where X is the Ubuntu revision number) appended to the end of the Debian version. So if the Debian hello 2.1.1-1 package was changed by Ubuntu, the version string would be 2.1.1-1ubuntu1. If a package for the application does not exist in Debian, then the Debian revision is 0 (e.g., 2.1.1-0ubuntu1)."00:02
savvas_cooper_: I think this is more of a #ubuntu-motu question :)00:03
savvas(when you ask the question, that is :P)00:03
_cooper_'kay, thanks for the pointer.00:05
evoliohi there, is jaunty going to have a new theme? has that been decided?00:30
directhexwho's on archive admin duty?00:32
persiadirecthex, https://wiki.ubuntu.com/ArchiveAdministration#Archive%20days00:32
directhexRiddell, did you just slash the NEW queue to ribbons?00:33
persiaI think you hit a gap, as it's no longer Tuesday in UTC+0, but it's not yet Wednesday in UTC-600:33
directhexpersia, looking for context on a contextless REJECT00:34
StevenKAh, that's the if uploader == directhex check ...00:35
* StevenK hides00:35
directhexStevenK, damn, i thought only the debian cabal had that00:35
directhexwell, they say a true genius is never appreciated in his own time...00:36
ScottKUnfortunately the ubuntu-archive list archive is lagging badly.00:36
persiaI suspect it's the abovementioned slowness of the list server.  I'm not seeing context for REJECTs that I *know* were sent (because I received other copies).00:36
ScottKYes.  I know because I don't see one I sent.00:36
ScottK... and you were sent a copy of ...00:37
StevenKdirecthex: Exercise patience, I doubt it was contextless00:37
persiaAnd that is 9 hours old.00:37
ScottKYep.00:37
directhexStevenK, james_w got the reject message, and was asking ME if i knew context, so unless there's a follow-up lagging someplace00:38
=== asac_ is now known as asac
pochuslangasek: what do I need to get an UI freeze exception for bug 328606? :)01:02
ubottuLaunchpad bug 328606 in liferea "Liferea shouldn't include actions if notification server doesn't accept them" [Low,Triaged] https://launchpad.net/bugs/32860601:03
Amaranthpochu: how is that a UI freeze exception?01:13
Amaranthpochu: you have to get an exception to fix "the UI accidentally broke"?01:13
pochuAmaranth: don't ask me, I'm the one who thinks it's a bug fix01:14
pochubut some people seem to disagree01:14
TheMusoc01:15
=== mneptok_ is now known as mneptok
ScottKAmaranth: It's more U/I doesn't work so well because someone changed the rules without much notice.01:36
ScottKPretty well amounts to the same thing, but there's no accident involved.01:37
slangasekpochu: doesn't look to me like anything that needs a UI exception.01:43
slangasekpochu: who was saying otherwise?01:43
ScottKslangasek: Does U/I freeze actually apply to Universe (or at least the unseeded parts of Universe)?02:00
ScottKSince the docs/translations teams don't (AFAIK) support those packages, I'm not sure what point it would serve.02:00
slangasekScottK: I don't think it should apply, and wasn't considering it to apply02:01
ScottKRight, I just don't think our docs actually say that.02:02
ScottK(that it doesn't apply)02:02
* ScottK looks02:02
ScottKslangasek: https://wiki.ubuntu.com/UserInterfaceFreeze includes "all user-visible strings in applications", which one might well think inludes Universe.02:04
slangasekScottK: I'm happy to have that amended, though perhaps we should check with the doc team (mdke?) first to make sure that's consistent with their expectations02:05
ScottKmdke: Would adding "...  which are installed by default" to that cause any issues for you?02:06
ScottKIt uses that construction earlier in the page.02:06
=== rgreening_ is now known as rgreening
TheMusopersia: Do you happen to be around now?04:35
TheMusoslangasek: Got an install problem with studio disks, testing on amd64 but will likely affect i386 since its arch independant, a weird conflict issue with ubuntustudio-sounds and gnome-audio, working out how to address this, but likely enough a seed addition to blacklist gnome-audio will be enough.04:37
TheMusopersia: never mind, worked around it.04:42
TheMusoslangasek: If you could respin studio when you get a chance, that would be appreciated, fixed the problem in our seeds, which doesn't require an ubuntustudio-meta upload.04:43
TheMuso666/05:09
LaserJockyikes05:12
* LaserJock wonders what window TheMuso was heading to :-)05:12
slangasekTheMuso: respinning05:14
TheMusoslangasek: thanks05:14
TheMusoLaserJock: lol05:15
AmaranthLaserJock: The channel which must not be named, of course05:16
slangasekTheMuso: and build done05:22
TheMusoslangasek: thanks again.05:23
persiaTheMuso, just back.  You know that germinate doesn't enforce blacklisting for tasks or meta, right?  I'm not sure just blacklisting will work without either adding a Provides: to ubuntustudio-sounds, or extending the Recommends for pulseaudio-module-x1105:37
TheMusopersia: well gnome-audio is no longer on the disk so...05:37
persiaHrm.  Odd.  I remember a similar issue with xfce-panel and MID where it kept showing up.  Anyway, if it works, it works.05:39
TheMusoyeah05:39
TheMusopersia: well the seed change I made fixed the problem to the point where the disk is installing.06:19
persiaExcellent.  That's enough for alpha.  It's probably worth trying a Desktop -> Studio crossgrade at some point to make sure that still works.  I'll see if I can do that this evening.06:20
TheMusook06:21
dholbachgood morning07:06
mdkeScottK2, slangasek: that sounds like it should be ok although I think we do have some documentation for the occasional universe package which would be affected if UI strings were changed late, From a quick review it's quite rare though07:17
pittiGood morning07:17
Amaranth$ ls -lh /var/log/syslog07:51
Amaranth-rw-r----- 1 syslog adm 329M 2009-03-11 02:50 /var/log/syslog07:51
Amaranthcan we make pulseaudio shutup already? :/07:51
pittiAmaranth: can you please file a bug against pulseaudio for that, with some excerpts from the log?}08:12
pittiand maybe discuss with TheMuso08:12
Amaranthyeah, doing that now08:13
pitticertainly sounds worth fixing08:13
AmaranthMar 10 10:33:32 ronin pulseaudio[3715]: alsa-util.c: snd_pcm_avail_update() returned a value that is exceptionally large: 13835058055252444064 bytes (418293347931 ms) Most likely this is a Linux bug. Please report this issue to the ALSA developers.08:13
Amaranthoops, didn't mean to paste that here08:13
pittiwell, it's fine, just one line :)08:14
Amaranthit's that over and over and I though crimsun uploaded a fix for it already08:14
Amaranthah, it's actually bug 34078408:18
ubottuLaunchpad bug 340784 in pulseaudio "[Jaunty] Pulseaudio fills my logfiles." [Undecided,New] https://launchpad.net/bugs/34078408:18
* Amaranth adds a comment08:18
=== tkamppeter__ is now known as tkamppeter
Amaranthlooks like this actually may have already been fixed, the messages stopped right around the time I remember pulseaudio dying and having to restart it08:21
AmaranthTheMuso: Thank you for making pulseaudio shutup about alsa :)08:22
Amaranthor whoever did it08:22
* Amaranth &08:22
tkamppeterpitti, there is still a CUPS SRU for Intrepid which you did not put into -proposed08:23
seb128slomo: are you there?08:25
slomoseb128: yes08:36
seb128slomo: see #ubuntu-desktop log ;-)08:39
pittitkamppeter: oh, I see; added to my TODO list, thanks for the poke08:49
tkamppeterpitti, thanks, this is already waiting for 6 weeks.08:50
KaiL..am I the only one, who needs to give gconf a kick from time to time?08:50
Keybuklool: it didn't so much as drop it09:03
Keybukit was an Ubuntu patch that upstream rejected09:03
Keybukjust use -q/--quiet instead, that's fixed now09:03
pittimvo: I like the current update-manager version number09:07
pitti1:0.100.1, is that really still decimal? :-)09:07
directhexpitti, that version number sucks. there's only one awesome version number in ubuntu, and it's 10.0.1.218+10.0.0.525ubuntu1~hardy1+really9.0.124.0ubuntu209:08
pittimvo: will the next version be 1:0.101.0?09:09
pittidirecthex: yeah, "how to encode the changelog into a version number"09:09
seb128slangasek: is now still a good time to do uploads? ;-)09:09
directhexAKA "epochs hurt"09:09
DktrKranzI hope they don't change their mind again, it can be hard to manage 10.0.1.218+10.0.0.525ubuntu1~hardy1+really9.0.124.0ubuntu2+reallyreally9.0.120.0ubuntu109:10
* pitti eyes at stgraber .. MirrorKit..09:13
mvopitti: I like it too and your idea as well, I think I will switch to this schema09:19
loolKeybuk: Problem is that it breaks packages which used that09:25
loolKeybuk: Like powernowd -- which is still installed on most systems09:25
Keybuklool: powernowd isn't seeded anymore?09:25
Keybukyou just need to merge the seeds09:25
KeybukI have "remove powernowd from the archive" on my todo list09:26
loolKeybuk: It's not seeded but it remains installed on upgrades...09:26
Keybuklool: didn't you use update-manager? :p09:26
Keybukalso the modules powernowd tries to load are all compiled into the kernel now09:26
loolKeybuk: Would update-manager have removed it?09:26
Keybuklool: should have done09:26
loolI used aptitude09:27
KeybukI've been grepping the archive to make sure nothing uses -Q09:27
Keybukonly a few ubuntu-specific things did09:27
loolOk, and these are fixed but you missed powernowd?09:27
KeybukI deliberately ignored powernowd, since it's going away ;)09:29
loolKeybuk: Did you also use the occasion to grep for /sbin/lsmod.09:29
Keybuklool: no, that one's a simple packaging error09:29
loolKeybuk: powernowd and acpid -- which we want to get rid off too -- are using it09:30
Keybukit should be in /bin09:30
loolKeybuk: Some programs hardcode it09:30
Keybuklool: I couldn't find any reference to modprobe in acpid?09:30
loolKeybuk: /sbin/lsmod09:30
Keybukoh09:30
Keybuklike I said09:30
Keybukthat's just a packaging error09:30
Keybuklsmod's always been in /bin in Debian/Ubuntu09:30
KeybukI hadn't noticed it was in sbin upstream09:30
loolKeybuk: The other way around I think09:31
soren?09:31
cjwatsonI think it was moved intentionally in Debian since /sbin isn't on the default path there09:31
loolKeybuk: What I'm saying is that packages are hardcoding /sbin/lsmod and they break with the move09:31
sorenWe want to get rid of acpi?09:31
sorenacpid, I mean?09:31
cjwatsonbut in any case packages should not hardcode the paths to executables09:31
loolsoren: Yes, do you need it?09:31
sorenlool: Err.. yes?09:31
Keybuklool: yes09:31
Keybuklool: and I'm saying the move was an accident09:31
Keybuklool: and I've already got a package to fix that09:31
loolKeybuk: Oh it's an accident in the last upload which you'll revert09:31
Keybuk like I said09:32
Keybuk that's just a packaging error09:32
Keybuk;)09:32
sorenlool: Unless you've got something else that will shut down my system when it receives and acpi shutdown event?09:32
loolKeybuk: I thought it was an ancient packaging error which you corrected in the last upload09:32
Keybukoh, no ;)09:32
loolsoren: Well on the desktop we have hal-hooked-up stuff09:32
sorenlool: Good for you :)09:32
* mvo is deeply anoyed by pycentral telling him there is no Python-Versions field in the package when there clerly is one 09:33
loolKeybuk: Ok, good too hear lsmod will move back after A6 then,09:33
Keybuklool: I decided to go with a symlink09:33
Keybukon the basis that since /sbin/lsmod is the upstream locations, other things might be hard-coding that09:34
loolKeybuk: That's what I'd have suggested too09:34
sorenlool: Oh, so by "get rid of" you just mean "stop seeding on the desktop"?09:34
sorenlool: Not as in "removing from the archive", which seems to be what Keybuk meant wrt. powernowd.09:35
loolsoren: Actually yes, after discussing it with you I remembered it's only for desktops that it was question of droppin git09:35
Keybuklool: I have that backwards, don't I :)09:35
Keybuk/sbin/lsmod is the traditional Debian/Ubuntu location09:35
lool/lib/udev/rules.d/85-regulatory.rules:KERNEL=="regulatory*", ACTION=="change", SUBSYSTEM=="platform", RUN+="/sbin/"09:35
Keybukbut /bin/lsmod is the upstream location09:35
loolhmpf :-(09:35
sorenlool: Ok, no worries then :)09:36
Keybuklool: ?09:36
amitklool: be careful what you write -"droppin git" will cause you many enemies in the kernel team :-p09:36
loolsoren: I'm actually happy that we'll keep it somewhere cause I spent some time cleaning it up and was sad that this was being dropped and hence my work wouldn't be that useful  :-)09:37
loolamitk: Yeah, I almost wrote a joke about git after it09:37
loolbryce: So 60x11-localhost broke login for me09:38
loolbryce: startx returns me to the console; if I move the file away it doesn't anymore09:38
sorenlool: :)09:38
brycelool: update to u1509:38
Keybukwel09:38
loolbryce: Ok, sorry and thanks09:38
Keybukwhy don't we just run gnome-power-manager on servers?09:39
amitklool: we're not affected by git jokes, we just point to bzr vs. speed :)09:39
Keybukor a headless equivalent?09:39
brycelool: no prob, we can blame redhat (bashism vs. dashism)09:39
loolKeybuk: There was no headless equivalent until recently; devicekitpower might change that though09:39
Keybuklool: DK-power only replaces the HAL bit09:39
Keybukyou need a policy agent to make the decisions09:39
mvocould someone with knowledge about initramfs-tools please review my patch for #338563 ?09:40
Keybukmvo: looks sensible09:40
mvothanks Keybuk09:41
brycenight09:43
Keybukbryce: morning09:44
davmor2Guys I just completed a 64bit Ubuntu install from netboot mini.iso and am greeted with a nice little window that says....  Kerneloops-ui  Your system had a kernel failure09:48
loolArchive admins: python-protobuf disappeared from the archive: it used to be in universe and was being promoted to main, then disappeared09:51
loolI don't see it in rmadison in jaunty anymore09:52
pochuslangasek: I think the dx team thought they needed UI freeze exceptions, but I may be wrong09:53
pochuslangasek: at least they tagged the bugs with 'uif-jaunty'09:54
=== mdz_ is now known as mdz
=== ScottK2 is now known as ScottK
tkamppeterAny Python expert here? It is about bugs like bug 335543, a Python app does not find a certain Python library (saying "ImportError in <module>()") but the library is installed. Reinstalling the library helps. This does not only happen to Jockey but also to hal_lpadmin, the system-config-printer tray applet, ... What is the problem here?10:10
ubottuLaunchpad bug 335543 in jockey "jockey-gtk crashed with ImportError in <module>()" [Undecided,New] https://launchpad.net/bugs/33554310:10
DktrKranztkamppeter: it's probably not transitioned for Python 2.6, a rebuild could fix it.10:13
DktrKranztkamppeter: I mean x-kit10:15
tkamppeterDktrKranz: In the mentioned case a reinstall of the existing library package even helps (no rebuild of the package). Can it be that the postinstall scripts of all Python libraries need to get re-run after Python 2.6 installation? This should be automated in the update process.10:18
seb128mvo is looking to similar issues10:19
mvotkamppeter: it looks like bug(s) in python-central10:19
mvotkamppeter: seb128 has a similar issue with bzrtools10:20
DktrKranztkamppeter: python-central has some links, probably new python version modified them a bit, so it can't find Python module anymore until a new installation is performed.10:20
seb128I got things screwed after cleaning python2.4 yesterday10:21
tkamppetermvo, DktrKranz, perhaps you should move bug 335543 to python-central then.10:25
ubottuLaunchpad bug 335543 in jockey "jockey-gtk crashed with ImportError in <module>()" [Undecided,New] https://launchpad.net/bugs/33554310:25
dholbachara: are the "move files around" changes in ldtp in debian already?10:30
pittislangasek: for planning, gnome-themes-ubuntu_0.1_all.deb (which we need to add) is 279 kB10:30
aradholbach: no, but I talked with the debian maintainer and he's going to accept the changes10:31
pittislangasek: that's about the size I recently removed from gnome-themes, so I don't need to have a too bad conscience10:31
=== jussio1 is now known as jussi01
dholbachara: is that going to be part of 1.5.1-1?10:32
dholbachthe thing is: if files move from one package to the other, we need a conflicts/replaces (<< old version) - if we want syncability it'd be nice if we'd have the same versions in the conflicts/replaces10:32
ScottKdholbach: I wanted to mention that I think your idea about more, short MOTU training sessions is a good one.10:34
dholbachScottK: excellent - I was planning to wait a bit longer until everybody had read the proposal and then send a mail to all the people who said "sounds good - count me in" to get planning10:35
ScottKdholbach: Please note there was a distinct lack of 'count me in'.  My Ubuntu time is getting somewhat more limited, so I really can't take on new tasks currently.10:36
dholbachScottK: that's completely fine :)10:36
dholbachI was happy with the feedback I got on the blog post - sounds like this is a more sustainable model. :)10:37
aradholbach: then, you could accept michael's debdiff, that does not include that change, I will send my changes to debian instead. those are not as urgent, but the new upstream version is :)10:37
aradholbach: the only change i do not agree with michael is that he changed site-packages to dist-packages, I would put *-packages, as ldtp can work with python2.5 as well10:38
dholbachara: OK, if Kartik makes those changes in 1.5.1-1 and uses a   Conflicts/Replaces: ldtp (<< 1.5.1-1)   I guess we should be fine with our changes in 1.5.1-0ubuntu110:39
dholbachara: I personally am fine with both, you decide10:40
aradholbach: OK, then you can go ahead, as he already accepted the changes (informally). thanks for your help :)10:42
dholbachara: hum... does he have that package available somewhere? it'd be nice if we could just sync it instead of me guessing and hoping that the changes are going to be equivalent. my concern is the versioned conflicts/replaces - if we pick different version numbers there, we'll have to maintain that diff for another few releases10:44
aradholbach: :-) then, again, just use the michael's version, really (with the python2*/*-packages changes...)10:46
aradholbach: really, the other changes are not that urgent10:46
aradholbach: we can wait for debian10:46
dholbachara: can you please talk to Kartik and make sure that he uses (<< 1.5.1-1) in the conflicts/replaces? :-)10:47
aradholbach: if they are not in jaunty... that's not a problem10:47
aradholbach: sure, will do :)10:47
dholbachara: gracias10:47
aradholbach: danke to you :D10:47
pittimvo: hm, the task <-> assignee mapping in bug 35876 looks backwards to me10:47
ubottuLaunchpad bug 35876 in update-manager "'Downloading package information' and 'building dependency tree' progress dialogs request focus too often" [Low,Confirmed] https://launchpad.net/bugs/3587610:47
dholbachara: de nada :)10:49
pittimvo: realistically I don't think we'll be able to generally fix this in metacity; I just corrected the upstream bug link for metacity10:49
pittimvo: for a local solution, do you think the progress window should just never receive focus? or at least focus_on_map false or so?10:49
dholbachara: done10:57
aradholbach: danke!10:58
dokopitti: can we promote icedtea-6-jre-cacao to main? I'd like to have it for arm and powerpc.11:01
bigoninfinity: hi, do you know how often the chroots are cleaned up on buildd?11:02
pittidoko: sure; done11:12
dokopitti: thanks11:12
pittidoko: btw, is the cacao source still relevant with this?11:12
pittidoko: it's already in main11:13
pitti(icedtea-6-jre-cacao I mean)11:13
dokopitti: no, not exactly, because openjdk has a copy of the cacao source again (cacao is still in universe)11:13
pittidoko: right, I meant if the cacao-oj6 is now redundant and should be removed11:13
dokopitti: but now we can remove the cacao-oj6 package11:13
pittidoko: lp-remove-package.py -u pitti -m 'cacao now built from openjdk-6 source' cacao-oj611:14
pittidoko: does that sound correct?11:14
pittidoko: as a rationale?11:14
dokopitti: sounds ok11:15
* pitti makes a flushing noise11:15
dokotkamppeter: it doesn't make sense to refer to a discussion on irc without including or summarizing it ...11:17
tkamppeterdoko, added.11:22
lamontbigon: how do you mean "cleaned up"?  the chroot is freshly unpacked from a clean tarball every build, and dist-upgraded.  the tarball is freshened "from time to time" (manually)11:27
cjwatsonlamont: he's asking about the latter, because python2.5-minimal is still there and can go away now11:28
cjwatsona dist-upgrade won't do that11:28
lamontcjwatson: right11:28
dokotkamppeter: why should it be a python-central error, if the usb module cannot be imported, which is managed by python-support?11:28
dokoDktrKranz: ^^^11:29
dokomvo: ^^^11:29
seb128doko: speaking about python error apt-get autoremove cleaning python2.4 yesterday on my install and since bzrtools is broken11:30
seb128doko: ie11:30
seb128 LC_ALL=C ls /usr/lib/python2.6/dist-packages/bzrlib/plugins/bzr*11:30
seb128ls: cannot access /usr/lib/python2.6/dist-packages/bzrlib/plugins/bzr*: No such file or directory11:30
dokoseb128: bug report?11:31
rmcbridedoko: pitti: python-protobuf seems to have disappeared from Jaunty. Could this be related to the MIR for protobuf that got promoted yesterday?11:31
tkamppeterdoko, see IRC discussion, bug 33554311:31
ubottuLaunchpad bug 335543 in python-central "jockey-gtk crashed with ImportError in <module>()" [Undecided,New] https://launchpad.net/bugs/33554311:31
seb128doko: what would be useful as extra infos in a bug report?11:32
seb128doko: I think mvo was investigating but I will open a bug if he doesn't11:32
cjwatsonI've filed an RT ticket to have the buildd chroots refreshed, at lamont's suggestion11:32
bigonlamont: well there are some package left behind (like python2.5-minimal) that make some pkg FTBFS11:32
dokotkamppeter: what does this have to do with 291035?11:36
mvodoko: I was refering to the problems that tkamppeter described and a issues that seb128 had with bzrtools. I don't know about usb modules11:37
tkamppeterbug 291035 is also an ImportError which was reported recently (not very well done by the reporter, he hijacked an old, closed bug) and is also an ImportError, looks like his problem was also triggered by Python 2.6.11:38
ubottuLaunchpad bug 291035 in python-central "hal_lpadmin crashed with ImportError in <module>()" [Undecided,Incomplete] https://launchpad.net/bugs/29103511:38
tkamppeterIt has nothing to do with hal-cups-utils (the package correctly requires python-usb) and also not with the case that python-usb is a USB library.11:39
cjwatsonbigon: if packages break with it, they probably ought to use Build-Conflicts?11:42
bigoncjwatson: actually the pkg will ftbfs with all python*-minimal as it need the std lib11:43
bigonand the minimal doesn't provide that11:43
cjwatsonbigon: err, surely that means that it needs to build-depend on the appropriate extra packages, not that -minimal breaks it11:44
cjwatsonsounds like your package is just broken11:44
bigoncjwatson: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=474053 << actually it's that problem11:47
ubottuDebian bug 474053 in python2.5-minimal "python2.5-minimal: looks like Python 2.5, but isn't" [Normal,Open]11:47
cjwatsonbigon: but that bug does not affect build-dependencies. You should build-depend on what you need11:48
cjwatsonthat bug is about where the executable is located (and is a bit debatable anyway; I would be inclined to say that we should not change that in Ubuntu, although it's up to doko) and that cannot possibly affect build-dependencies11:49
bigonthe thing it's that the configure takes the smaller version of python, py2.6 is actually pulled but like py2.5 from python minimal is already there it takes that one11:50
dokobigon: renaming doesn't make much sense. both are pulled, because the -minimal packages recommend the "complete" one11:52
Keybukseb128: I think I fixed the bootchart bug11:53
Keybukat least, it's far more reliable for me now11:53
MacSlowseb128, hey there11:55
MacSlowseb128, today is actually allocated to squash some bugs on notify-osd :)11:56
MacSlowseb128, I'll see how much I can fix11:56
dholbachMacSlow: crashers first!11:57
dholbach:-)11:57
MacSlowdholbach, I know :)11:57
cjwatsonbigon: "takes the least version of python" seems like a rather odd thing to do ...11:57
bigonI don't know why it's done like that..12:03
mvopitti: looking at the bug now12:03
bigondoko: recommended pkg are not pulled on buildd12:04
dokobigon: is python2.5-minimal still installed on the buildd?12:05
bigondoko: yep12:05
dokoinfinity: ^^^ could this be fixed/removed please?12:06
cjwatsondoko: I filed an RT ticket for this already12:07
dokook, thanks12:07
bigoncjwatson: do you have the url of that ticket?12:08
cjwatsonthe relevant RT system is internal so it won't help you12:08
cjwatsonI'll let you know when it's done12:09
bigonok thx12:09
ograKeybuk, is it normal that i dont have any hwclock initscripts at all anymore ? (i still think the babbage passwd thing is related to clock issues, especially since my hwclock is at 01-01-1970)12:11
cjwatsonogra: the kernel is supposed to sync the system clock from the hardware clock itself nowadays. If this isn't working here, that could well be the sort of thing that's quite architecture-specific12:16
ograright12:16
cjwatsonogra: though if the hardware clock is wrong, then the hwclock init scripts wouldn't have made any difference anyway :)12:16
ograand i see on my x86 laptop that pw expiry is set to 1397912:16
ogradays12:16
cjwatsonis it possible that you have multiple rtc devices, only some of which actually work?12:17
Keybukogra: my hardware clock looks generally right to me12:17
ograno, only one and that works if i call hwclock manually12:17
Keybukogra: run /sbin/hwclock --show12:17
ograKeybuk, i ran sudo hwclock12:17
ograand now ran sudo hwclock --systohc and rebooted12:17
ograwhich makes everything function correctly12:18
ograi have ttys12:18
cjwatsonthe kernel's supposed to sync it on shutdown too ...12:18
Keybukcjwatson: no it's not12:18
ograand it depends12:18
cjwatsondo I misremember?12:18
cjwatsonok12:18
ografrom where would it sync it12:18
Keybukthere was an init script on shutdown to do that12:18
ograi.e. if i dont have network attached ...12:18
ograit wouldnt getr a correct time at all12:19
cjwatsonwell, the obvious answer is "the system clock". but if I've misremembered and it doesn't, then the question is moot.12:19
Keybukhah12:19
ograin any case 13979 days from 01 01 1970 definately is expired :)12:20
cjwatsonpresence of the network is a red herring here; that is only relevant for setting the system clock, usually rather later12:20
Keybukright12:20
Keybuksystem clock set from hardware clock on power on12:20
Keybuksystem clock set from network on ifup12:20
Keybukhardware clock set from system clock on shutdown12:20
Keybukexcept I note that the init script is missing here ;)12:20
cjwatsonbut if the system clock is set from the network relative to a completely broken hardware clock, that would certainly break stuff first time round12:20
ograright, but if you need a correct time on first boot and the board only has 01 01 1970 in the hwclock12:20
ograwhere would a correct time come from without net12:20
cjwatsonso does this mean network -> system clock needs to adjust password expiry too?12:21
* cjwatson vomits12:21
Keybukogra: where would a correct time come from at all?12:21
Keybukcjwatson: I don't see what this has to do with password expiry?12:21
cjwatsonKeybuk: ok, I think this is the sequence of events12:21
cjwatson1) system boots; hardware clock says 1970 so system clock is initialised to that12:22
ograKeybuk, if your clock is at 01 01 1970 ... the default expiry value in /etc/shadow seems to be 1397912:22
cjwatson2) casper runs in the initramfs, and among other things it runs adduser and sets some kind of default expiry time12:22
ogra13979/365=38 years12:22
cjwatson3) network comes up and ntp runs12:22
ograwhich means its expired :)12:22
Keybukogra: I have 99999 in my expiry field12:23
ograwrong field ? :=12:23
ogra:)12:23
Keybukno...12:23
Keybukubuntu:...:0:0:99999:7:::12:23
* ogra thought it was the second field12:23
Keybuksecond field is days *before* password may be changed12:23
Keybukthird field is days *after which* password must be changed12:24
ogradays since Jan 1, 1970 that password was last changed12:24
Keybukfields after that12:24
Keybukie. username = ubuntu, pass = ..., last changed = 0, may be changed = 0, must be changed = 9999912:24
cjwatson99999 days == ~ 27 years12:25
ograyeah12:25
Keybukcjwatson: 273 years12:25
ograoh12:25
Keybukso while we will be bitten by this bug, I'm not going to worry about it too much ;)12:25
cjwatsonKeybuk: one of us can't divide12:25
KeybukI'll leave a note about it in my will12:25
cjwatson99999/36512:25
cjwatson27.3945205479452054794512:25
Keybukcjwatson: math 101, if you have ~100,000 and your dividing by order of 100-1000 your answer is going to be >100 and <100012:25
Keybukso it's you :p12:26
ogra99999/36512:26
ogra27312:26
ograKeybuk, is right12:26
cjwatsonoh, grr12:26
cjwatsonmy system is under load and there was a leading 9 to bc's input as a result12:26
cjwatsonwhich showed up rather earlier so I didn't notice ...12:26
cjwatsonfair point on maths 101 :)12:27
ograanyway, setting the hwclock manually solves my tty prob and gives me a different /etc/shadow12:27
Keybukso I agree that this problem looks like it's caused by the system clock being 1970 when adduser is run12:27
ion_In that case, the result should have been 2739. :-P12:27
Keybukbut I don't see why login is behaving that way at all12:27
Keybukthe password still should not be expired12:27
Keybukif it was set in 1970, and is not due to expire until 2243 ...12:27
ograwell, so we might hit a bug somewhere ... all i can say that a proper clock fixes all issues12:29
Keybuk        if (spent->sp_lstchg == 0) {12:30
Keybuk                D(("need a new password"));12:30
Keybuk                *daysleft = 0;12:30
Keybuk                return PAM_NEW_AUTHTOK_REQD;12:30
Keybuk        }12:30
Keybukhah12:30
Keybukhah12:30
Keybukhah12:30
Keybuksomeone special-cased 0 to mean "must change immediately"12:30
ograOH !!! and on a sidenote a fixed clock fixes https://bugs.launchpad.net/gnome-keyring/+bug/32816712:30
ubottuUbuntu bug 328167 in gnome-keyring "gnome-keyring-daemon eating 100% CPU at login in Jaunty" [Medium,Triaged]12:30
ograseb128, ^^^^12:30
Keybukogra: does the hardware clock keep time over a power off?12:31
ograapparently, yes12:31
ograit did for me right now12:31
Keybuksure?12:31
Keybukyou just rebooted12:31
ograno, it took to long and i unplugged power12:31
Keybukoh, wait, this is a live image12:31
ograright, i was lazy12:32
Keybukso the hwclock shutdown script has been removed by casper12:32
cjwatsonheh, so the only valid times for the clock in Ubuntu must be 86400 seconds from epoch or greater12:32
cjwatsonwe could change the kernel to guarantee that12:32
Keybukchanging the kernel to work around a PAM feature sounds like exactly the kind of thing that won't be accepted upstream :-/12:32
cjwatson'cos there are so many systems that desperately need to have their clock set to 1 Jan 1970 at boot12:33
KeybukI did think of a sensible minimum time12:33
Keybukthat the kernel has12:33
Keybukits own build time/date12:33
ograwell, we could set it to 1 instead of 012:33
Keybukogra: then you'll hit the next bit ;)12:33
ograor to some fantasy value12:33
cjwatsonuseradd could explicitly special-case this12:34
Keybukactually, no, you won't12:34
ograright, thats what i mean12:34
cjwatsonif the current time appears to be 0 days, add 112:34
Keybukyes useradd could special-case this12:34
ograwe set the passwd from casper anyway12:34
cjwatsonwill anything care if password-last-changed > current-time?12:34
cjwatsonogra: indeed, but useradd is a better place for the change12:34
ograbut then it will apply everywhere12:35
cjwatsonnot saying it's the best place, but definitely better than casper :)12:35
cjwatsonyes, it wil12:35
cjwatsonl12:35
cjwatsonis that a problem? that sounds like a feature to me12:35
ograwhile we actually only need it in live sessions, no ?12:35
Keybukcjwatson: you get a warning12:35
Keybukbut it returns PAM_SUCCESS12:35
cjwatsonogra: where possible, a design goal for the live CD should be to differ as little as possible from the normal system. If a bug fix is needed in the live CD that doesn't break anything reasonable in the normal system, we should fix the normal system12:36
cjwatsonsince Keybuk has checked that this doesn't break cases where the system clock remains 1 Jan 1970 after boot, I can't think of any reasonable case that this useradd change would break12:37
ograright, understood, though the user handling of the live CD is special anyway, which was the reason for me to think we should fix it there, if it improves anything for a normal system i indeed agree12:37
Keybukdo we care enough about systems with an empty hardware clock, and no network, to deal with the "what is the time mr wolf?" problem12:38
Keybukie. ask the user what time it is ;)12:38
ograugh12:38
ograthat sounds evil12:38
ogralike going back to the 90s :)12:38
* ogra remembers a d-i question in woody ...12:38
ograimho it should just not break ...12:39
cjwatsonogra: we create a special user, yes, but "I ran useradd on a normal system that has a broken clock and can't log in with that new user" sounds like a reasonable enough bug to me too12:39
ograyeah, agreed12:39
Keybukogra: well, those people will just get systems that think they're in 1970 all the time12:41
Keybukit depends whether you think that's breaking or not ;)12:41
ograif the functionallity is given i think thats fine12:41
Keybukand I tend to agree with something cjwatson said12:41
ograif its a desktop system you will notice it immediately12:41
* cjwatson falls over12:42
Keybukthat at least if the clock is 1970, we _know_ what's happened12:42
Keybukwhereas if we set it to some random time like the kernel's own build date, we won't have a clue12:42
ograindeed12:42
cjwatsonand also, users know what's happened; 1970 is a fairly familiar "hardware clock forgot its time" symptom to an entire generation of techies12:42
ograwhat are we discussing here ? (i never disagreed to that one actually)12:44
ograi wouldnt ask the user ... and i wouldnt set it to something random ...12:45
cjwatsonI think Scott is posing a question and then arguing with it himself :-)12:46
cjwatsoni.e. thinking out loud12:46
ograheh, yeah12:46
ograwe might hit filesystem issues though, not sure12:46
ograi.e. enforced fsck12:47
* ogra isnt sure in what other areas of the system 1970 will have any effect12:47
cjwatsonlargely, it shouldn't matter much. Only things that compute time in days are likely to have a problem12:48
cjwatsonfor anything that works in seconds or less (i.e. nearly everything), it's non-zero and positive, so who cares12:48
cjwatsonobviously if the time is inconsistent, e.g. keeps going backwards after power removal, that's a problem12:48
ograright... and fsck will actually only kick in if the clock changes to a proper date12:48
seb128ogra: good to know for the gnome-keyring issue13:02
ograseb128, meh, next reboot its back ... seems i was mislead13:02
ograit probably just dies after some time, i'm monitoring ti atm13:03
=== ssweeny_ is now known as ssweeny
allquixoticHas anyone else started to get Pidgin crashes in latest Jaunty? I gdb'ed it down to libpurple/protocol/msn/notification.c:941, there's a nice pointer1->pointer2->pointer dereference and the first or second one is NULL... it's never checked before it's used :)13:53
allquixoticIt was fine for days, now it's crashing on startup right as MSN connects13:54
Riddellsiretart: libavcodec52 is ending up on the CDs13:54
allquixoticI checked our diff on Pidgin and we don't patch that file so it's in upstream13:54
Riddellsiretart: so is libxine1-ffmpeg13:54
Riddellsiretart: libxine1 should depend on  "libxine1-misc-plugins | libxine1-plugins" as it does in intrepid, it's the wrong way around in jaunty13:57
dholbachallquixotic: did you try asking in #ubuntu-desktop?`people might give you a good answer there13:57
allquixoticdholbach: Are they interested in Jaunty development over there too? Odd to have different development channels13:58
allquixoticI've never been to #ubuntu-desktop before now :)13:58
dholbachallquixotic: there's a lot of individual development channels around here (server, kernel, mobile, desktop, etc.)13:59
Riddellsiretart: changelog tells me we had same problem in intrepid fixed in xine-lib (1.1.14-1ubuntu2)13:59
Riddellsiretart: so I'll make that change now13:59
dholbachallquixotic: thanks for working on pidgin - I'm sure a lot of people will appreciate it13:59
allquixoticdholbach: The bug seems network/thread/code-up related, and C/GLib is right down my alley :) I will have a "fix" that causes it not to crash shortly, but I'd like to at least get someone else to acknowledge the problem :-/ Might just be my weird MSN account having a notification Pidgin doesn't know about, or something14:00
allquixoticFortunately this is the kind of code that someone who isn't an everyday Pidgin hacker can get their head around14:01
dholbachallquixotic: rock on! :)14:01
Riddellasac: I'd like to fix bug 340210 for alpha too14:01
ubottuLaunchpad bug 340210 in network-manager "network-manager should recommend plasma-widget-network-manager" [Undecided,New] https://launchpad.net/bugs/34021014:01
Riddelljust to let you know14:01
asacRiddell: for alpha?14:06
asacRiddell: what is with the -kde thing. can we remove that from the archive?14:07
mterrydholbach: Thanks for the endorsement!  I didn't even notice it until I was adding to the page14:08
seb128allquixotic: you better open pidgin bugs upstream directly there is no ubuntu pidgin hackers14:08
dholbachmterry: no worries :)14:09
Riddellasac: I'm undecided on removing it, the kde 4 version may still have a few scenarios where it doesn't work.  it should move to universe anyway14:11
asacRiddell: well. from what i know the knetworkmanager never became feature complete either14:12
asacRiddell: and seems to be abandoned upstream14:12
asac(for 0.7)14:12
asacRiddell: i would think that if plasma doesnt cover someone cases they can still use -gnome thing14:13
ScottKRiddell: I'd like to suggest it move to the DVD so we have an installation medium with it for the scenario where someone only has wireless and the widget doesn't work (for just one release).14:13
asacScottK: Riddell: is there a particular scenario you have in mind that is broken?14:13
asac(for plasma)14:13
ScottKasac: I think the chances of us getting complete test coverage to know that everything is OK are low.14:14
pittirmcbride: hm, curious; seems it simply vanished inded14:14
asacScottK: well. we know that knetworkmanager is broken ;)14:14
rmcbridepitti: seb128 and cprov are looking into it14:14
ScottKI don't have a specific scenario I KNOW is broken, I just think it's prudent not to totally jump ship from one to another.14:14
asaci wonder if anyone will consider it a loss if we remove it and point them to the official applet if they need more features14:15
ScottKasac: More broken than historically?14:15
asacScottK: definitly more broken than with 0.6; knetworkmanager development for 0.7 seems to have stopped half way (e.g. just wired and basic wireless)14:15
pittirmcbride: seems to be a well-known soyuz bug; either way, seems we need a no-change upload and NEW it again14:16
ScottKRight, but I'm using the 0.7ish one on Intrepid and it generally works.14:16
asacScottK: and plasma ;)?14:16
* ScottK is still on Intrepid, so hasn't used it yet.14:16
asacheh. ok14:16
ScottKI think leaving it on the DVD for one release is low risk and gives a decent fallback should unexpected hardware/scenario specific issues with the new widget pop up.14:17
ScottKIf it doesn't work either, the user is no worse off than if we'd removed it.14:17
siretartRiddell: oh, indeed. thanks!14:20
asacScottK: if users wouldnt report stuff against network-manager i wouldn't care. from that point i would prefer that kde folks report bugs against plasma and then go to network-manager-gnome as a fallback (instead of yet another broken thing).14:21
Riddellsiretart: how do I use this hg thing?14:21
asacjust my suggestions. in the end kubuntu team has to decide.14:21
ScottKUnless we seed network-manager-gnome and all the related depends on the dvd it doesn't really address my issue.  I'm mostsly worried about having and installation media that can be used without users having to resort to hand configuring networks.14:22
ScottKJust my suggestions too.  Up to Riddell.14:23
siretartRiddell: pretty similar to bzr, but use 'hg clone' instead of 'bzr get' to checkout14:26
asacyeah. lets wait for Riddell. i just think that if users can connect somewhere with the current incomplete knetworkmanager, but can't do that with plasma then plasma is just not ready14:27
Riddellsiretart: E: Couldn't find package hg14:27
siretartRiddell: apt-get install mercurial14:27
siretartRiddell: however for such a small and uncontroversial change, I'd suggest to just upload to ubuntu, and I'll import the upload to the branch next time I work on it14:30
siretart(or ping me and I'll do it in a minute)14:30
Riddellsiretart: kubuntu.org/~jriddell/tmp/xine-lib_1.1.16.2-1ubuntu2.debdiff14:32
siretartRiddell: typo: s/whic/which/14:33
siretartRiddell: and that change still seems a bit unnecessary to me, or rather a workaround for a limitiation in the cd creation scripts14:34
siretartRiddell: the other alternative is perfectly valid (as your debdiff demonstrates). Why not respect that libavcodec52 is blacklisted and search for valid package set instead?14:36
cjwatsonsiretart: the CD creation scripts try to mirror what apt will do where possible, and with the dependencies as they are, apt will prefer libxine1-plugins if that package is available14:44
cjwatsonsiretart: I'd support Riddell's change, it looks correct to me14:44
cjwatsonsiretart: remember that apt is used to build the live filesystem, and there's no way to tell it to blacklist a package14:45
cjwatsonso you have to get the dependencies such that apt DTRT, not focus on CD creation14:45
siretartcjwatson: so `apt-get install gxine libavcodec52-` wouldn't work?14:49
siretartappending '-' always worked for me for blacklisting packages14:49
cjwatsonI'm not actually sure. But I don't want to have to go hardcoding lots of stuff like that in livecd-rootfs!14:49
cjwatsonthe stuff in there for Xubuntu is bad enough14:49
cjwatsondependencies should just behave how we want things to be set up by default14:50
cjwatsonlivecd-rootfs> also in tasksel for netboot installs, which would be a lot harder14:50
siretartwell, having a variable $BLACKLISTED_PACKAGES with "libavcodec52-" can't hurt maintainability of livecd-rootfs that badly, I'd imagine...14:51
siretartbut I have to admit that I haven't looked at that too closely yet14:51
cjwatsonI'd really prefer xine-lib to just have the dependencies the right way round for the default install, please14:51
cjwatsonit'll be a lot more fiddly than that in tasksel, trust me14:51
siretartok14:52
seb128siretart: ok, the new gstreamer0.10-ffmpeg seems to be fixing quite some of those crashers14:57
seb128siretart: just letting you know, I did follow up with slomo and on bugs14:57
siretartseb128: excellent.14:59
siretartseb128: perhaps we should syncronise more closely on ffmpeg updates for gstreamer0.10-ffmpeg14:59
siretartseb128: does gstreamer upstream intend to switch to the 0.5 release of ffmpeg?14:59
seb128slomo: ^ do you know?14:59
siretartif yes, we could consider updating ffmpeg to 0.5 in both the package and gst-ffmpeg15:00
ScottKNow that there's an actual release, it would be a shame not to use it.15:03
siretartScottK: does that imply a (granted) freeze exception? ;)15:04
catnaphello - I'm not a developer, but I think I have a good development idea in my mind15:04
siretartactually I have the 0.5 release package ready in my ppa15:04
catnappeople often get annoyded when they're typing something on the screen and some windows suddenly pops up and interupts the typing15:05
ScottKsiretart: No, but if the rdepends were tested and working, I'd defiinitely lean in that direction.15:05
catnapwhy don't we make ubuntu so, that it detects when user is typing15:06
seb128it does that15:06
seb128and that's working most of the time15:06
catnapseb128: that's great news15:07
catnapthis actually occured to me when I was using windows where the problem is much worse15:07
catnapI wonder why they haven't fixed it so far15:07
catnapwhat does ubuntu do, when new windows is about to interupt user?15:08
slomosiretart: yes, gst-ffmpeg already contains ffmpeg 0.5 internally15:08
persiaSo, anyone who hasn't voted for MC already really ought to do so: polls close in 8 hours or so.  https://launchpad.net/~ubuntu-dev/+polls15:08
catnapor does that depend on wether you use kde or genome?15:08
siretartslomo: can you please follow up then in bug #340303 about this? to me it seems then a very good idea to have gst-ffmpeg and ffmpeg-debian in sync15:09
ubottuLaunchpad bug 340303 in ffmpeg "Please sync with upstream release of ffmpeg .5" [Undecided,Triaged] https://launchpad.net/bugs/34030315:09
siretartslomo: ideally we could syncronise on the next ffmpeg update, what do you think?15:11
slomosiretart: you mean sync the next ffmpeg upload from debian?15:12
siretartslomo: that would be too much, I'd think. no I mean the next upstream update15:12
cjwatsonKeybuk: heh, I just noticed that swapoff writes to devices internally in the kernel, as I'm guessing does umount15:12
pitticalc: I try my luck on jaxme now15:13
cjwatsonKeybuk: so swapoff; lvremove is racy and you need swapoff; udevadm settle; lvremove15:13
tomeuhi all, I'm wondering if the https://wiki.ubuntu.com/UserInterfaceFreeze applies to all software or just to stuff that gets installed by default or the translation and documentation team work on15:14
tomeuwe have some bugs that would be better fixed by adding a couple of strings15:14
tomeumaybe should ask this in #ubuntu-motu?15:18
calcpitti: ok15:26
pitticalc: I just tried a xom rebuild for fun, but it still fails (thus isn't fixed with current openjdk)15:27
calcpitti: afaict there are stubs in the svn version that might help, but they didn't all work as is15:27
calcpitti: yea with xom it builds fine on most developer boxes but seems to always fail on the buildd15:27
pitticalc: do you happen to know about maven-ant-helper?15:27
calcpitti: not much other than maven pulls in a bunch of universe depends15:28
pitticalc: no, I don't mean maven2, but maven-ant-helper15:28
pittiDescription: helper scripts for building Maven components with ant15:28
persiatomeu, That question was answered here within the last 24 hours: it only applies to that which is either installed by default or documented on help.ubuntu.com15:28
tomeupersia: so it's ok if I update that page?15:28
calcpitti: oh no not really, i looked at the example package they listed in it and it seems they had to write new build.xml for it, so i was worried i would end up breaking things in undetectable ways15:29
* persia reviews backscroll carefully15:29
tomeuthe point "all user-visible strings in applications and the desktop. " is a bit ambiguous, IMO15:29
kenvandine_wkkees: ping15:29
pitticalc: it just might be a shimmer of hope :)15:29
calcpitti: if you are pretty familiar with ant and maven it probably wouldn't be too hard to convert it over i guess15:29
calcthe only thing i know about either is there is cdbs support for ant, heh15:30
pittiunfortunately I'm neither15:30
pitticalc: so, the worst case for jaxme would be that we just keep building it with gcj, right?15:31
calcpitti: yes, i believe jaxme still builds fine with gcj15:31
pitticalc: it does, I just built it here15:32
pittiI want to compare build logs, and everything15:32
calcpitti: iirc xom still builds with gcj as well, xom just seems to die due a weird out of resources error15:32
persiatomeu, I've updated to reflect what I believe was the agreed change, referencing the log.15:32
pittiit's a recursive stack overflow15:32
calcpitti: oh hmm, i wonder why it sometimes works during build and sometimes doesn't15:33
calcpitti: is it infinite recursion or just recurses too much on the buildd?15:33
pitticalc: infinite, as it looks15:33
calcpitti: hmm :\15:33
pittiI see the same stack frame over and over15:33
tomeulooks awesome, thanks!15:33
pittiit doesn't look like being related to too little RAM or anything like that15:34
calcpitti: fwiw i built on amd64 and the buildd that builds it is i386, not sure if that would be related15:34
calcpitti: i can try rebuilding it on my machine again and see if it still builds ok here, if so there might be some 32/64 bit issue15:34
pitticalc: thanks15:35
pitticalc: ok, I'll continue with jaxme15:35
persiacalc, pitti Do be careful of maven builds.  The current archive maven expects to pull from the internet when building.15:35
calcpersia: ugh!15:35
calcisn't that forbidden in debian policy?15:36
persiaNo.15:36
pittipersia: I don't intend to actually use maven; thanks for the warning15:36
persiaIt's forbidden to use that on a buildd.15:36
pitticalc: in practice yes, because the buildds don't allow it15:36
calcah ok, i thought it had managed to make it into policy15:36
persiaSame as we support end-users pulling from cheeseshop or cpan.15:36
persiaBut we can't do that when building our packages.15:37
pittidoko: why does default-jdk-builddep depend on both default-jdk (openjdk) and java-gcj-compat-dev?15:37
calcpersia: well essentially i am surprised it doesn't support a buildd safe way to build as it is a build tool and other things use it (or maybe... they will use it eventually) ;-)15:38
dokopitti: to build the gcj natively compiled parts15:38
calcso i suppose either nothing currently uses it in the archive or packages have to hack around its tendency to download things15:38
pittidoko: I thought we should get rid of gcj?15:38
calcpitti: you might only need default-jdk depending on what it is15:39
persiacalc, https://wiki.ubuntu.com/JavaTeam/Specs/MavenSupportSpec15:39
calcpersia: thanks for the pointer :)15:39
pittidoko: just wondering how disastrous it would be to leave jaxme build with gcj in jaunty, if all attempts to make it build with openjdk fail15:39
persiacalc, Be warned that the spec is mostly abandoned, in favour of http://wiki.debian.org/Java/MavenRepoSpec (I believe)15:41
calcpersia: ok15:42
stgraberpitti: didn't we decide that anything that wants to sound new must end with "kit" ? :)15:42
ScottKNo doubt with the kitkit to rule them all.15:43
directhexit's a rip-off of BeOS, FYI15:43
* calc is seeing if xom will build or explode for him again15:43
directhexhttp://en.wikipedia.org/wiki/Be_API15:43
pitticalc: wear a helmet15:44
dholbachKITT would rule them all!15:44
calcpitti: built fine here15:44
directhexApplication Kit? OpenGL Kit?15:44
calcpitti: i'm going to create a i386 chroot and see if i can make it explode15:44
calcpitti: when you built it what platform did you try?15:44
pitticalc: just for fun, fancy throwing it into your ppa?15:44
pitticalc: I just retried it on the normal buildds, thus i38615:44
persiapitti, We have a few packages that still build-depend on gcj (and default-jdk *is* gcj in Debian, which encourages that for now)15:44
calcpitti: i think it probably is an i386 issue, so will try building on i386 now15:44
calcpitti: all my systems are installed 64bit so i usually do all my builds that way which would explain the issue if it does just die on i38615:45
pitticalc: at least it would give some reproducibility15:45
calcpitti: yea, will see now15:45
dokopitti: sure, that's an option. does ecj handle it? gcj still provides the fastest alternative for some archs. what I really do want to have is a conditional dependency: if gcj is installed/used, install the corresponding "-gcj" package.15:45
pittidoko: didn't try with ecj, just with java-gcj-compat-dev15:46
pittiand of course with default-jdk15:47
Keybukcjwatson: why is it racy with the lvremove?15:47
Keybukor do you mean swap-on-lv?15:47
dokopitti: this is ecj then15:47
calcYIPEE!15:54
calcmy OOo file chooser patch works!15:54
pitticalc: for unbreaking gvfs, and using fuse?15:56
calcpitti: for forcing OOo to use the fuse path, yea15:56
pittiyay15:56
calcit shows up like this more or less (in debugging)15:56
calcSalGtkFilePicker::getSelectedFiles() - pURI1 = 'sftp://ccheney@127.0.0.1/home/ccheney' - pPATH = '/home/ccheney/.gvfs/sftp for ccheney on 127.0.0.1/home/ccheney' - pURI2 = 'file:///home/ccheney/.gvfs/sftp%20for%20ccheney%20on%20127.0.0.1/home/ccheney'15:56
calci take the file_path then stuff it back into a uri and send it along15:56
pitticalc: I hope you don't have to cobble together the .gvfs path yourself :)15:57
calcpitti: no, i just have to use the file_get_chooser for GFile instead of uri then pull the path out of it, then convert that to a uri then pass it back to OOo15:57
TheMusoAmaranth: thank Daniel, he sorted that out. :)15:58
calctoo bad there is no obvious way to tell the chooser to just return a gvfs fuse uri to begin with15:58
pitticalc: ah, I isolated the "build with java 6" patch from the svn; I'll see how that backports16:00
calcpitti: cool :)16:01
pittiit's just a 39 KB diff commit, so how bad can it be16:01
* pitti sobs16:01
calcheh16:02
calcso now OOo can't save to ftp but i can probably track down the bug in gvfs for that16:02
calci didn't try ftp before since sftp/smb already worked16:03
pitticalc: just ftp, or sftp also?16:03
pittiah, nice16:03
calcplain ftp16:03
pitti*shrug*16:03
calcsftp works, smb works, ftp doesn't16:03
ScottKIt'd be nice if sftp worked on non-gvfs systems.16:03
calcbut OOo is using straight fuse now so fuse just doesn't support something it needs16:03
pitticalc: I'd call that a feature :)16:03
calcpitti: heh yea16:04
calcpitti: tbh i don't know if ftp support ever worked with OOo even in the past when gvfs had otherwise worked for it16:04
Amaranthpitti: that's nothing, the diff from ffmpeg a month ago and ffmpeg 0.5 is 1.2MB16:04
calcbut it should be relatively trivial to find out why it is failing16:04
calcpitti: testing the xom on i386 now16:05
alex-weejany dev know what's happened to Qt in Jaunty to make it not respect fontconfig for hinting?16:08
cjwatsonKeybuk: swapoff/umount triggers change event, lvremove fails because device is busy16:09
cjwatsonI think16:09
cjwatsonand yes, I mean swap on lv16:09
cjwatsonor whatever's-being-umounted on lv16:09
Keybukright16:09
ScottKalex-weej: The move to Qt 4.5 is recent.  You might ask in #kubuntu-devel.16:09
Keybukany fput in the kernel will trigger the inotify ;)16:09
alex-weejscottK: done.ta.16:12
ograKeybuk, so looking at the babbage serial ttys i think they should have the same rules as ttyUSBX, do you want a bug for that ?16:13
Keybukthat means they'd be in "dialout" ?16:13
ograright16:13
Keybukcan you hijack jerone's existing bug and be more useful on it16:13
ograif thats correct for ttyUSB i do think thats fine for any other serial ports as well16:13
ograKeybuk, do you have a number ?16:14
Keybukno, I'm a name, not a number16:15
ogra:P16:15
Keybukbug #34079616:15
ubottuLaunchpad bug 340796 in udev "Add udev rule to allow users to use Freescale VPU on ARM MX51 SoC based devices" [Wishlist,Incomplete] https://launchpad.net/bugs/34079616:15
ografor that bug indeed :)16:15
Keybukmight as well retitle that one just "udev rules for Freescale ARM MX51 based devices"16:15
* ogra adds 16:15
ograyeah, thats for video devices16:16
ograKeybuk, oh, the kernel patches arent upstream yet16:16
ograand are unlikely to get there in time for jaunty i guess16:16
=== svolpe_gerrath is now known as svolpe
Keybukheh16:17
Keybukare they on lkml?16:17
Keybukas long as they've hit there, udev upstream is generally happy16:17
ograi doubt it, amitk only added the patchset to our kernel yesterday and i think he is still working on sanitizing it for us before anyone even thinks about sending tehm upstream16:18
directhex"There was a rumour that, in the wake of the TomTom case, Canonical was seriously considering removing Mono from main and leaving it to multiverse as too dangerous to support (like mp3). I haven’t been able to find any more info either way, asking around. "16:20
directhexyay for boycottnovell :)16:20
soreauHello16:25
slangasekmdke: do you think we should have a whitelist of those universe packages whose UIs wind up in the relevant documentation, or some other way to describe this?16:26
slangasekpochu: ah, I don't know what semantics they're using for that tag, but they don't seem to have requested a UIF :)16:26
slangasek(e)16:27
soreauI know this may not be the correct place to ask but I am having the bug 99908 "The ext3 file system creation in partition # of SCSI (0,0,0) (sda) failed." on both Hardy and Intrepid alternate. Is there any possible way that I can get around this to install ubuntu?16:27
ubottuLaunchpad bug 99908 in ubiquity "The ext3 file system creation in partition #1 of SCSI1 (0,0,0) (sda) failed." [Undecided,Incomplete] https://launchpad.net/bugs/9990816:27
slangasekseb128: middle of the milestone freeze, so not really16:27
=== zul_ is now known as zul
soreauActually, I am having the bug in the alt install, not the gui ubiquity (if they are different)16:27
seb128slangasek: you reply to a question from 8 hours ago?16:27
slangasekpitti: gnome-themes-ubuntu> sounds fine; also rescued some space because libavformat52 had been sneaking in when it shouldn't, and causing problems16:28
seb128slangasek: if that was a "can I upload" I did upload what I wanted to get in beta6 so it's all good from my side ;-)16:28
slangasekseb128: yes, that's what I do when people ask me questions in the middle of the night ;)16:28
seb128slangasek: yeah, I was just not sure about the context16:29
seb128I forgot, the day has been busy ;-)16:29
slangasekok. :)16:30
soreauDoes anyone have a suggestion to this issue I am experiencing?16:30
ograKeybuk, i'm not touching the bug until i have more info from kernel team16:30
cjwatsonsoreau: firstly, I would strongly recommend that you regard your problem as a new bug, not tag along with an existing bug; that error message is general and can have many causes, and conflating lots of bugs into one report makes them less likely to get fixed16:31
cjwatsonsoreau: secondly, we have had some recent (new!) problems in this area. Have you tried with *today's* daily build, since we installed some fixes yesterday?16:31
cjwatsonsoreau: or are you referring to a problem in a stable release of Ubuntu?16:32
soreauOnly with 'stable' releases, 8.04 and 8.10 Alternate cd's16:32
cjwatsonsoreau: can you please file a *new* bug and attach your logs to it? you can extract them by going back to the installer main menu and using the "Save debug logs" item16:33
cjwatsonthen give me the bug number16:33
slangasekRiddell: ah, you fixed the xine-lib issue, great :)16:34
soreauNo, I have grown weary with frustration. I was only wanting to know if there was a quick fix solution. Sorry, but I think I'll try that windows ubuntu installer next.. wubi?16:34
soreaucjwatson: Thanks for your input though16:34
cjwatsonsoreau: um, please?16:34
cjwatsonsoreau: I can't investigate this and answer your question without seeing the logs16:35
cjwatsonsoreau: if I see your logs, there might well be an easy answer for you16:35
cjwatsonbut I can't tell you off the top of my head based on just a general error message16:35
ScottKsoreau: He's the senior developer on installer stuff so you won't get a better shot at an answer.16:36
soreaucjwatson: Well now that I have been trying this so long, I decided to nuke the ntfs partition so am beginning to reinstall windows (not by my choice, all's I wanted to do was make my friends bug ridden xp install a dual boot linux pc)16:36
=== dholbach_ is now known as dholbach
cjwatsonI'm also hoping that soreau might be one instance of a more general problem, in which case I might get to fix it for lots of people for 9.0416:37
soreaucjwatson: But, if it will help you, and the alternate cd is capable of mounting my usb stick (any sane mount/umount command give 'invalid argument' btw) then tell me a list of logs you would like to see and I'll try my best to pastebin them for you16:38
soreaudmesg was polluted with I/O errors so it may even be HW failure which would be puzzling since xp seems to have no such trouble installing16:39
cjwatsonI routinely need /var/log/syslog and /var/log/partman16:40
soreauYes, and what else?16:40
cjwatsonthat's all16:40
cjwatsonsoreau: do you have another computer on the same network that you can ssh into?16:40
cjwatsonor just network-accessible at all, I suppose16:40
soreauYes, but for what purpose?16:41
cjwatsonwell, you can switch to tty2, run the command 'anna-install openssh-client-udeb', and then you can just scp the log files out16:41
soreauThis is only happening on this A45-S120. All my desktop pc's have never had this problem16:41
cjwatsonmuch easier than messing around with USB sticks16:42
soreaucjwatson: Oh, you mean on the problem lappy..16:42
cjwatsonyes16:42
soreaucjwatson: Ok, give me a few moments please16:43
soreaucjwatson: To make sure and clarify, you want the logs after the failure (of course) correct?16:45
cjwatsonyes16:45
soreauok, sec16:45
soreaucjwatson: I have the files but I need help because ifconfig isn't even available (?)16:56
soreauWhat would a usb stick be list as in /dev?16:56
Keybuksd[a-z][0-9]+16:56
ograjust look at the output of the dmesg command after you plugged it in16:57
soreauah yes16:57
calcpitti: yea iirc i got that error when i was trying to backport the changes also16:57
calcpitti: which was when i decided i didn't know enough about what I was doing to keep from breaking things, heh16:57
pitticalc: oh, then it seems that I just duplicated your backporting work16:58
pitticalc: yeah, NFC what this wants to tell me16:58
cjwatsonsoreau: the network should already be up by the time you encounter this bug; you can use the ip command if you need it, things like 'ip addr show'17:00
soreaucjwatson: /var/log/syslog -> http://pastebin.com/m34edc693 /var/log/partman -> http://pastebin.com/m5566d0fb17:03
soreaudoesn't look too good to me17:04
=== fader_ is now known as fader
cjwatsonsoreau: ok, so there are indeed a vast number of input/output errors in there, as you said earlier17:07
soreauyup17:07
cjwatsonsoreau: since you said that XP is fine, it's probably a Linux kernel bug; since it isn't an installer problem as such (the installer is just the victim) it's outside my realm of expertise17:07
soreauokays17:08
cjwatsonsoreau: if it were me I'd start by messing around with the boot options provided in the F6 ("Other Options") menu at the CD boot menu17:08
Keybukreally?17:08
Keybukthose errors are pretty much definitely dead disk17:08
cjwatsonXP being fine tends to suggest that it might be the 1% of cases where it's the driver that's busted17:08
soreaucjwatson: I think I will try this wubi thing. Thanks for looking17:08
Keybukhow would you test the Live CD on XP?17:08
cjwatsonassuming that XP is in fact still fine17:09
* Keybuk is looking at the sr0 I/O errors17:09
cjwatsonKeybuk: (a) this isn't a live CD (b) there are also a slew of I/O errors about sda17:09
Keybukah17:09
cjwatsonsoreau: this is just advice and you're free to ignore it, but I would be surprised if it worked any better. It'll be using the same disk driver17:10
Keybukthere's some odd pnp errors too17:10
soreauKeybuk: The sr0 errors I've seen on several different machines only with 8.10 disks17:10
cjwatsonCDs are the most unreliable allegedly-reliable medium I've ever encountered17:10
Keybukcjwatson: certainly CD+-*Rs :p17:11
cjwatsona speck of dust on the lens causes immense confusion17:11
soreauheh, perhaps there is a reason that's not the first time I've heard that17:11
cjwatsonand the physical media is so cheap nowadays that it's cheaply-*made* too, so gets scratched really easily17:11
soreaucjwatson: How about ubuntu17:11
cjwatsonhmm?17:12
soreaus fancy disk check program?17:12
cjwatsonyou mean the checker on the CD boot menu?17:12
soreauyea17:12
cjwatsonall it does is read through all the files on the CDs and check their checksums17:12
calcpitti: you might try asking on their mailing list but it seems to have very low traffic17:12
calcpitti: other than that i have no clue17:12
soreaucjwatson: Not the entire cd as a whole collectively?17:12
soreauiso image even17:13
cjwatsonin some cases it isn't guaranteed to throw up the same errors; I've seen some anecdotal evidence that read order makes a difference. But in any case it will not solve your problem17:13
cjwatsonsoreau: (a) how would that help? (b) where would you store the checksum that it would compare against? :-)17:13
soreaucjwatson: I have no idea, that's just how it's always worked in my head ;)17:13
cjwatsonsoreau: it's easier and more useful to check at the filesystem level17:14
soreaucjwatson: In any event, after I get the results from this wubi thing I'll let you know17:14
soreauThis is probably the worst nightmare I've ever had attempting to install linux but I blame the crappy hw in this laptop17:17
cjwatsonsoreau: so Keybuk and I are looking at this, and what's happening under the covers is that the kernel has repeated trouble trying to talk to your disk (possibly relatively minor trouble but just lots of it; hard to say) and eventually decides that it's all too hard and disables the disk17:19
slangasekNCommander: you can't recommend libxine1-ffmpeg in xubuntu, its dependencies are blacklisted from CDs by Ubuntu technical board resolution 2007-01-02.17:19
Keybukthe disk errors the kernel is having are DMS related17:20
* NCommander peeks at the seed to see whats pulling it in17:20
slangasekxfmedia17:20
Keybukerr, DMA related17:20
NCommanderew17:20
* NCommander guesses we'll have to drop xfmedia then17:20
TheMusoor remove the recommends17:20
slangasekinstead of dropping xfmedia's recommends: on libxine1-ffmpeg?17:20
NCommanderThe package more or less is useless without it17:20
TheMusoNCommander: how so?17:20
cjwatsonit only seems to be on write. parted manages to *read* the partition table fine17:20
NCommanderUgh, there was a bug on this17:21
NCommanderWe added the recommends to close it17:21
soreaucjwatson: I think it's noteworthy that after this problem rerunning the partitioner shows no partitions but only the main disk and update-dev does nothing to help. Rebooting shows the bootloader has been nuked. After running the xp install disk, it shows all partitions and reinstalling the XP BL to the MBR allows it to at least boot xp again17:23
pitticalc: ok, disabling the test suite work around that weird init.sql problem17:23
soreaucjwatson: If there's any possibility it may be running out of mem as this thing only has like ~230MB or so17:23
cjwatsonsoreau: after this problem, the kernel has entirely disabled access to the disk17:23
soreauWow17:23
cjwatson(until you reboot)17:24
soreauno wonder17:24
slangasekNCommander: so do you want to pull xfmedia from the ship seed, or should I upload xfmedia to drop the recommends?17:24
soreauI wonder why it causes the boatloader on the mbr to disappear or malfunction17:24
cjwatsonsoreau: I think out-of-memory is unlikely as it enabled swap just before the disk problems started; besides 230MB is well over spec for the alternate installer itself (although tight for the Ubuntu desktop)17:24
cjwatsonsoreau: possibly it started writing the partition table but didn't complete the write17:24
calcpitti: disabling test suites might not be a good idea depending on why they fail :)17:24
pitticalc: yeah, it was just a test; I'm bisecting the test suite now to isolate it17:25
calcpitti: iow will it fail with other software too17:25
cjwatsonthe DOS partition table format does not really permit ideal resilience here17:25
calcpitti: ah ok17:25
pitticalc: any luck with xom?17:25
calcpitti: let me see, i started it a bit ago17:25
calcpitti: yea it fails on i386 for me, works on amd64 for me17:25
Keybuksoreau: could you try a boot with libata.dma=0 on the kernel command line?17:25
calcpitti: restarting on i386 to make sure it is consistently failing17:26
soreauKeybuk: Yes, I can but I will need some time17:26
pitticalc: hm, sounds like a java compiler error then?17:26
calcpitti: it seems to consistent pass on amd64 and fail on i38617:26
calcpitti: seems that way to me with my little knowledge of the situation17:26
pitticalc: hm, isn't it arch:all?17:26
pittiweird17:26
cjwatsonsoreau: we're in no rush; I'm going out soon anyway17:27
calcpitti: yea so it would seem to be something related to the openjdk on i38617:27
soreaucjwatson: Thanks for looking into this, I appreciate it FWIW17:27
calcpitti: java code that compiles on amd64 should compile the same on i386 (aiui anyway)17:27
soreauKeybuk: ETA ~30-45mins17:27
NCommanderslangasek, https://bugs.edge.launchpad.net/ubuntu/+source/xfmedia/+bug/307578 - do we have another way to fix this, or is it simply not possible to ship MPEG support out of the box?17:27
ubottuUbuntu bug 307578 in xfmedia "libxine1-ffmpeg not installed with xfmedia" [Medium,Fix released]17:27
Keybuksoreau: np. if you could grab the syslog and put the url here, I'll get beeped :p17:28
slangasekNCommander: you can't ship MPEG support out of the box that relies on libavcodec52.17:28
slangasekNCommander: you could seed totem instead, and then the codec finder would do the work for you :-P17:28
NCommanderugh17:29
calcpitti: when it failed the one time in the past for me i might have been trying it on an i386 chroot then too17:29
* NCommander doesn't even know when we made this seed change17:29
NCommanderslangasek, will dropping it to a Suggests work for you? I don't like changing seeds without talking to the other Xubuntu guys.17:29
calcpitti: i occasionally build for i386 when testing things but not very often, but it is currently looking like it always fails on i386 and always passes on amd6417:29
Keybuk...I really quite like this HP Mini17:29
pitticalc: if it fails building one particular file, maybe you can isolate it, so that upstream has a test case?17:29
Keybukmuch nicer than the Dell17:29
Keybuk</blasphemy>17:30
calcpitti: i'll see what i can find out17:30
slangasekNCommander: yes, I can drop it to a suggests; and 'bzr blame' will tell you when the seed was changed17:30
NCommanderKeybuk, which HP?17:30
pitticalc: having a bug filed about this would be nice, and then we can revert to gcj for jaunty17:30
* calc is also doing gvfs testing since it appears no one has done thorough testing of the fuse layer and needs it to work right for jaunty OOo :-\17:30
KeybukNCommander: "HP Mini"17:30
Keybuk1000 I assume17:30
calcpitti: ok17:30
NCommanderOh, I didn't realize there were multiple ones17:30
slangasekNCommander: actually, the seed itself was changed back in 2008 - I think it's xine that has changed since then17:30
Keybukif there are, we're probably not supposed to know about them or talk about them ;)17:31
calcpitti: i'm headed to lunch now, but i should be back in about an hour17:31
NCommanderI'll drop it to a Suggests, then I'll talk to Cody on what we want to do; I didn't know I was breaking a TB rule with recommending libxine1-ffmpeg17:31
Keybukyou were breaking the law17:32
Keybuknow, we break your legs17:32
Keybuk:p17:32
* NCommander tries to find the TB resolution to cite in the changelog17:33
Keybukgrep for "OMG WE'RE ALL GOING TO JAIL! I REFUSE TO BE YOUR BITCH, JAMES"17:34
NCommanderOddly enough, all that popped up was a quote from House ...17:34
cjwatsonhttp://irclogs.ubuntu.com/2007/01/02/%23ubuntu-meeting.html17:35
RainCTpitti: does the new gnome-power-manager add any nice features?17:39
pittiRainCT: the statistics look fancier :)17:40
pittiRainCT: but by and large, none that spring to your eye17:40
RainCTHeh. I didn't know about the statistics, how can they be accessed from the GUI?17:41
pittiRainCT: right-click on icon -> Energy consumption17:41
RainCTah, so I have to plug out the power cable to get there without using the terminal :P17:42
Turlhi17:43
* Keybuk wonders why so many initramfs scripts grep /proc/cmdline to look for things17:43
TurlI read this on a kernel changelog17:43
Turl  * Set CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE=y for i386/amd64/lpia17:43
Turlwhy the change?17:43
* TheMuso discovers that studio is also shipping libavcodec52, however untangling it from our disks is a bit more difficult.17:43
pittiI just checked, I still get CPU scaling, so it might not be as scary as it looks17:43
KeybukTurl: from ondemand?  because ondemand makes boot slow17:43
keesMacSlow: heya; thanks for looking into the kerneloops breakage.17:44
TurlKeybuk: but ondemand drains my battery :p17:44
keesMacSlow: the bug still shows that kerneloops is "confirmed", should that be flipped to invalid now?17:44
Turlperformance, sorry :p17:44
cjwatsonKeybuk: IIRC, only foo=bar gets passed through as environment variables, not just foo17:44
NCommanderslangasek, http://paste.ubuntu.com/129851/ - here's my debdiff, if its Ok by you, I'll upload this after it finishes test building.17:44
Keybukcjwatson: right, but most of these are looking for that17:44
KeybukTurl: that's ok, it'll be set to ondemand once you've finished booting17:45
TurlKeybuk: ok then, hope my laptop boots even faster :p17:45
pittiKeybuk: scaling_governor is still "ondemand" for me17:45
pittiKeybuk: is that set later in the boot sequence?17:45
slangasekNCommander: mmm, please don't make changes for miscellaneous lintian warnings for an upload in the middle of the milestone freeze17:45
pittiKeybuk: ah, you just said, nevermind17:45
Keybukpitti: well, not yet17:45
MacSlowkees, well the fix in notify-osd to make the kernel oops is pushed upstream (notify-osd), what's missing still is a patch to upstream kerneloops (rather kerneloops-applet) to use a proper gtk+dialog and not a notification17:46
Keybukbut then there's no kernel uploading with it no at ondemand yet either17:46
* NCommander fixes that17:46
MacSlowkees, that's what I'm working on now17:46
pittiKeybuk: hm, I thought I read it in the changelog, and I have -9 now17:46
pittiah, seems not recent enough17:46
KeybukI only see -8.28 on the changes list17:46
TurlKeybuk: -9 -> http://changelogs.ubuntu.com/changelogs/pool/main/l/linux/linux_2.6.28-9.30/changelog17:47
* pitti has 2.6.28-9.29 installed17:47
TheMusoa meta hasn't been uploaded either afaik17:47
slangasekyes it has17:47
slangasekbut -9.30 which has the change FTBFS, seemingly because of m-i-t behavior changes ;)17:47
Keybuk*blink*17:47
TheMusoright launchpad tells me otherwise also17:47
Keybukwhy can't I see that on -changes17:47
TheMusobecause changes is laaaaaaaaaaaaaaagggggyyy?17:48
slangaseks/changes/lists/17:48
Keybukslangasek: oh?17:48
MacSlowkees, might still be tomorrow until I've that patch ready (for discussion) I'd first like to get feedback from the people in #kernel and #ubuntu-kernel on the look of the dialog17:48
TheMusoslangasek: right17:48
Turlanother thing, about bug 337301, any idea when the kernel changes will be out there?17:48
ubottuLaunchpad bug 337301 in xserver-xorg-video-intel "Update to 2.6.3?" [Wishlist,Confirmed] https://launchpad.net/bugs/33730117:48
pittiKeybuk: I saw it on -changes, FWIW17:48
slangasekKeybuk: as far as we got with debugging it yesterday, yes.  I don't know if rtg has a handle on it today17:48
Keybukslangasek: nobody asked me about it17:48
NCommanderslangasek, http://paste.ubuntu.com/129853/ - how's this (followed by a bump-upload of xubuntu-meta once this publishes)17:49
Keybukwhat was the problem?17:49
slangasekNCommander: the debdiff is fine.  why do you think you need to bump xubuntu-meta?17:49
NCommanderslangasek, won't xubuntu-meta ... oh right, I'm an idiot, we're not seeding libxine-ffmpeg directly17:49
slangasekKeybuk: "depmod no workie"17:49
Keybukslangasek: -v17:50
NCommanderignore me, I'm working without enough caffeine17:50
slangasekKeybuk: that's as far as we got yesterday, rtg was still chasing the thread when I left17:50
soreauKeybuk: To verify, is this correct?: file=/cdrom/pressed/ubuntu.seed initrd=/install/initrd.gz libata.dma=0 quiet --17:50
NCommanderslangasek, I just kicked off pbuilder, if its successful, I'll upload if that's fine by you17:50
Keybuksoreau: yes17:50
slangasekNCommander: I would prefer you upload immediately17:51
TheMusolooks like 9.31 was uploaded a while back17:51
KeybukI'm pretty sure I've done multiple kernel builds with the new depmod and had no problems17:51
keesMacSlow: cool great!  I'll excuse myself from this process now.  :)  I just got involved due to doing some packaging cleanups for the MIR, and then trying to debug the regression.  thanks!17:51
soreauKeybuk: Unknown option 'libata.dma=0' ignoring17:51
Keybuksoreau: oh17:52
Keybukslangasek: ohh, was somebody parsing depmod's *output* ? :p17:52
slangasekyes17:52
Keybukoh17:52
Keybukyeah17:52
Keybukthat's totally changed17:52
Keybukwhich is kinda the point, really17:52
slangasekright, I didn't say it was m-i-t's /fault/ :)17:53
Keybukdidn't say you did ;)17:54
Keybukbut I like to know what I've broken17:54
* calc just realized he wasn't hungry, he is actually sick17:54
Keybukeven if it's just so I can say "well, if you will put it there..."17:54
pittiKeybuk: hm, /lib/modules/2.6.28-9-generic/modules.dep doesn't look any different to me; I just have an additional modules.dep.bin now17:54
Keybukpitti: it's missing the /lib/modules/2.6.28-9-generic/ bit17:55
calcpitti: i'll update the xom bug and then i'm off for the day, hopefully i'll be better by tomorrow :)17:55
pittiKeybuk: ah17:55
pitticalc: no progress on the initdb front :(17:55
calcpitti: ok17:56
pitticalc: sick> ugh; get well soon!17:56
calcpitti: thanks :)17:58
* calc updated the xom bug 329903 to indicate it appears to be openjdk's fault17:58
ubottuLaunchpad bug 329903 in xom "xom FTBFS in Jaunty on the i386 buildd but not on personal amd64" [Medium,Confirmed] https://launchpad.net/bugs/32990317:58
slangasekNCommander: I guess you haven't uploaded yet?17:58
* calc off to bed now, if you need me (emergency) call me as I am sick17:59
cody-somervilleslangasek, is this a must do it now emergency?17:59
* NCommander was talking with cody since I got him just before I uploaded18:00
slangasekcody-somerville: it's a "NCommander wanted to do the upload and I can't roll valid xubuntu CDs for the alpha until it's done and published" emergency18:00
cody-somervilleah, Okay.18:00
cody-somervilleI'll de-seed xfmedia from ship18:00
slangasekhrm?18:00
slangasekwhy?18:00
cody-somervilleslangasek, xfmedia is in our ship seed as a courtesy18:01
slangasekah18:01
cody-somervilleslangasek, if people want to use xfmedia, I'd prefer it work for them18:01
cody-somervilleslangasek, so instead of removing the recommends I figure just de-seeding it is the optimal choice18:01
slangasekcody-somerville: ok, fine with me - please unseed :)18:02
* cody-somerville waves his hands and casts some magic.18:02
NCommanderslangasek, side note, its a good thing I test built, the package FTBFS due to the change in the X11 headers itseems.18:02
MacSlowpitti, ping18:02
cody-somervilleNCommander, YOU SHOULD ALWAYS TEST BUILD!18:03
cody-somerville:D18:03
pittihi MacSlow18:03
NCommandercody-somerville, of course. Rule number one of being a MOTU18:03
* cody-somerville hi5s NCommander.18:03
slangasekNCommander: heh, ok18:03
AmaranthNCommander: I thought rule number one of being a MOTU was to worship dholbach18:10
ScottKworship/gang tackle at UDS18:11
cody-somervilleIs it worth it to upgrade to 18mb pipe from 10mb for an extra $40? :S18:13
ScottKI'd go with no.18:14
Turlcody-somerville: I'm in 3mb/256k, don't make me sad :p18:14
JanCthat's 18 millibit?  ;)18:14
* ScottK recently got upgraded from 10Mb to 17Mb or so for the price went down $0.50.18:14
* TheMuso is jellous.18:14
cody-somervilleScottK, you went from 10mb to 17mb and the price *dropped*? What ISP are *you* with?18:15
ScottKVerizon FIOS.  I was an early subscriber and they'd redone the plans.18:15
ScottKI think that's what it was.18:16
cody-somervilleVerizon FIOS, is that ADSL or Cable?18:16
Amaranthmy grandma started with 5mbit cable and went up to 12mbit cable for less money as they upgraded the plans18:16
* TheMuso is currently on 8MB, which is the fastest in this area, unless i wanted to pay rip-off prices to our monopoly telco for faster speeds which aren't a certainty anyway.18:16
Amaranthcody-somerville: It's...fiber18:16
cody-somervilleOh, is fiber better than cable? :P18:17
ScottKDefinitely.18:17
slangasekdietary fiber is better than dietary cable18:17
cody-somervilleSo your 17mb fiber pwn my 18mb cable?18:17
* TheMuso would jump on HFC when he returns to sydney if the prices were reasonable.18:17
* Turl is on ADSL18:18
ScottKcody-somerville: Well mine also comes with a stack of static IPs, so probably.18:18
TurlT_T18:18
cody-somervilleoh wow18:19
Amaranthcody-somerville: also his speed doesn't go down when his neighbor fires up bittorrent18:19
Amaranthwell, I guess that depends on how the system is setup but usually18:20
=== azeem_ is now known as azeem
NCommandercjwatson, is there any chance britney's run of ports could be fixed? It hasn't spit out a new page since 02/19: http://people.ubuntu.com/~ubuntu-archive/testing-ports/jaunty_probs.html18:40
TheMusoNCommander: ouch really?18:40
NCommanderYeah18:40
NCommanderSee the generated date18:40
TheMusois this for CDs, or the archive in general?18:41
NCommanderArchive in general, so we have no up-to-date installability counts.18:41
* TheMuso nods18:41
Turllibdrm-noveau1 is for nvidia cards, right?18:48
Turlon its description it mentions intel instead of nvidia :/18:49
azeemso file a bug18:50
=== JanC_ is now known as JanC
* Turl filled bug 34129418:59
ubottuLaunchpad bug 341294 in libdrm "libdrm-nouveau1 mentions intel instead of nvidia on its description" [Undecided,New] https://launchpad.net/bugs/34129418:59
=== Seeker`_ is now known as Seeker`
Lurepitti: can you explain why such apport crashes are rejected - bug 34126419:34
ubottuBug 341264 on http://launchpad.net/bugs/341264 is private19:34
slangasekpitti: a lot of duplicates on bug #335567 - do you know what's going on there?19:43
ubottuError: Could not parse data returned by Launchpad: The read operation timed out (https://launchpad.net/bugs/335567/+text)19:43
pittislangasek: haven't looked yet, but it's on my radar19:51
slangasekpitti: ok. should it be milestoned for beta?19:52
pittislangasek: doing19:52
slangasekta19:52
pittiLure: because they have an absolutely useless stack trace and outdated packages19:59
pittiLure: in this particular case, the package isn't outdated, but rather nonexisting, hmm19:59
Lurepitti: my system is up to date - and I do not hav gstreamer (Kubuntu)19:59
pittiLure: well, for this particular bug invalidating is probably alright, since there isn't much to be learned from it20:00
pittiLure: but in general, this "None" thing is interesting; can you please file an apport bug and give me the output of "dpkg -s phonon-backend-gstreamer"?20:00
Lurepitti: I am more concerned about that other reports might be lost20:01
Lurepitti: sure20:01
Lurepitti: as I said no phonon-backend-gstreamer installed here, so apport message is correct ;-)20:01
pittiLure: this only happens on "useless stacktrace" && "outdated packages", so I don't think valuable bugs can get logs20:01
pittis/logs$/lost/, duh20:01
pittiLure: hm, sounds like an error with parsing alternative dependencies then20:02
Lurepitti: ok, so should I still submit apport bug?20:02
pittiLure: it's purged?20:02
pittiLure: yes, please20:02
Lurepitti: will check20:02
pittiLure: thanks20:02
* Lure is not sure as I got some gnome depens installed by accident20:02
pittiLure: it's the preferred alternative of "phonon"20:03
pittiDepends: phonon-backend-gstreamer | phonon-backend20:03
pittiI think that's what's confusing apport20:03
Lurepitti: yes, that might be it20:03
* pitti calls it a day20:03
pittigood night everyone20:03
Lurepitti: good nite, and thanks20:04
cr3might it be possible that something changed on jaunty where running debuild now creates files under debian/tmp/usr/local/share instead of debian/tmp/usr/share?20:23
TheMusocr3: are you working with a python package?20:23
cr3TheMuso: yep20:24
TheMusocr3: if so, is it using distutils?20:24
cr3TheMuso: yep again20:24
TheMusocr3: you need to add --install-layout=deb to the setup call I think it is, let me double check that.20:24
TheMusocr3: its part of the python 2.6 transition.20:24
cr3TheMuso: I had that problem in another package, I didn't think that flag also affected the location of share files20:25
cr3TheMuso: thanks for the tip, I know where I need to go from here :)20:25
TheMusocr3: yeah I think it does20:25
TheMusocr3: np20:25
* cr3 needs to go get some coffee, that's where he needs to go20:25
ScottKcr3: TheMuso is correct.  It affects that too.20:44
ScottKThe idea is to get packages installed using just distutils into /usr/local and away from where the packaging system installs stuff.20:45
cr3ScottK: reasonable enough :)20:46
ScottKYes, just slightly painful at the moment.20:46
slangasekcr3, ScottK, TheMuso: hmm, nice discussion; 'zgrep usr/local dists/jaunty/Contents-i386.gz' points to a few bugs that need to be filed20:59
slangasekI can't tell if the python-twisted ones are the fault of distutils though20:59
ScottKslangasek: Probably faster to fix than file.20:59
slangasekthere is that21:00
ScottKI think twisted does some weird stuff in /usr/local, but doko does mind the twisted stuff pretty well.21:00
slangasekwell, it installs binaries to /usr/local/bin, which is a policy violation21:00
ScottKslangasek: Any chance you could pour the output from your zgrep into a wiki page we could point people at?21:02
dokoif there is stuff in /usr/local in packages, then the pkgbinarymangler doesn't work as expected :-/21:02
slangasek... why is it pkgbinarymangler's problem?  or is pkgbinarymangler supposed to abort?21:03
dokoit is21:04
slangasekah21:05
dokoif there's stuff in /usr/local, it's a bug in the apckage of course21:06
ScottKI guess I shouldn't complain since the McDonald's wifi is free, but 2+ minutes for apt-get update is really annoying.21:07
=== nhandler_ is now known as nhandler
davmor2Guys I've just done a freesoftware only install and jockey is asking if I won't to install the nvidia drivers I thought this was disabled in fso version?21:15
mdkeslangasek: I'd like to ask the -doc mailing list, I'll copy you in if that's ok.21:22
slangasekmdke: sounds good21:27
mdkethanks21:27
kirklandsuperm1: i have a couple of dkms issues at play here21:29
kirklandsuperm1: one of which is the fact that i need the headers for the specific kernel that is being compiled against21:29
kirklandsuperm1: (as well as any others that might be booted)21:29
kirklandsuperm1: what do you think of having dkms depend on all of the kernel headers?21:30
kirklandsuperm1: too heavy handed?21:30
slangasekeew21:30
kirklandslangasek: you eew'ing me?21:34
slangasekkirkland: yes. :)21:37
cody-somervilleeww21:37
kirklandslangasek: awesome!  then you can help me figure out how to solve this problem21:37
kirklandslangasek: kvm-source provides a dkms module for kvm21:38
kirklandslangasek: it needs the linux-headers for your kernel to build21:38
kirklandslangasek: how do put this in a debian/control file correctly?21:38
kirklandslangasek: linux-headers is a virtual package that tells you to install one of (*)21:38
kirklandslangasek: nvidia depends on linux-headers | linux-headers-generic21:39
slangasekheh, nvidia's is backwards then21:39
slangasekit's meant to be linux-headers-generic | linux-headers (real package first, virtual package after)21:39
slangasekcf. virtualbox-ose-source21:39
kirklandslangasek: sorry, that's my transcription (not cut and paste)21:39
kirklandslangasek: okay, how do i work linux-headers-server into that mix?21:40
slangasekkirkland: poorly? :)21:40
slangasekkirkland: you could get a set of metapackages that depend on "linux-headers-foo + linux-image-foo" and have an or'ed dep on those21:41
kirklandslangasek: so you don't think linux-image-foo should just depend on linux-headers-foo, and bring it on with it21:42
kirklandslangasek: it would be better to add this layer of another metapackage21:42
slangasekI think it's useful to a lot of people who don't need dkms to be able to install linux-image-foo without the headers21:43
slangasekbut perhaps linux-foo should pull it in21:43
slangasekit already pulls in lrm-foo today, after all21:43
kirklandslangasek: 'twould solve my current issue ....21:44
slangasekand is described as being "complete" :)21:44
kirklandslangasek: are you still thinking on this?  can i ask the kernel folks to do this?  or does a more formal proposal need to be drafted and ratified?21:45
slangasekkirkland: given that the desktop tasks all pull it in by default, and we're talking about also pulling it into server, refactoring so it's pulled in by linux-foo seems perfectly reasonable to me (while also leaving the Recommends: in place for desktop so that we don't also pull in lrm by default)21:47
slangasekkirkland: I don't think it needs to be any more formal than a bug report21:47
kirklandslangasek: i can do that, thanks.21:48
brettalton1kirkland: I was just watching your UDS Jaunty video on YouTube: http://www.youtube.com/watch?v=R-783GBVLIg&feature=channel_page21:48
brettalton1kirkland: and I was wondering, with Jaunty, if I have a 500GB hdd that is mounted as /storage, how would I fully encrypt that it using the same tools you created to encrypt /home?21:48
kirklandbrettalton1: well, you could do that with ecryptfs, but it might make more sense to use a device encryption scheme there21:49
kirklandbrettalton1: if you really want to do it with ecryptfs, you could do:  "sudo mount -t ecryptfs /storage /mnt"21:50
kirklandbrettalton1: you'll go through a few questions, choosing the passphrase, key size, crypto algorithm, etc.21:50
kirklandbrettalton1: then you'll read/write data to /mnt21:51
kirklandbrettalton1: the encrypted data will land in /storage21:51
brettalton1kirkland: sounds easy enough :) what's the difference between ecryptfs and a device encryption scheme? one is through software (ecryptfs) and the other I assume is hardware-related, correct?21:52
kirklandbrettalton1: not at all21:53
kirklandbrettalton1: they're both through software21:53
kirklandbrettalton1: and they're both handled in the kernel21:53
kirklandbrettalton1: ecryptfs encrypts each individual file as a unit21:53
kirklandbrettalton1: device encryption encrypts the entire device as a unit21:53
brettalton1kirkland: ahhhh, okay, so last question: what would I use/do to encrypt the whole device?21:54
kirklandbrettalton1: in this situation, i would use lvm + luks for encryption of that entire device21:54
kirklandbrettalton1: i believe that ecryptfs really shines on per-user encrypted home directories21:54
=== shtylman_ is now known as shtylman
kirklandbrettalton1: even though it can be used for other things21:55
kirklandbrettalton1: https://help.ubuntu.com/community/EncryptedFilesystemLVMHowto21:55
kirklandbrettalton1: it sounds like this is what you're trying to do ... encrypt an entire filesystem21:55
brettalton1kirkland: perfect, I'll research that. I appreciate your time, especially since it's one on one time with an Ubuntu developer :)21:56
brettalton1kirkland: exactly21:56
kirklandbrettalton1: ecryptfs is better at encrypting some subset of the filesystem21:56
brettalton1kirkland: so /home inside /... got it21:56
kirklandbrettalton1: like your home directory, or just one "private" directory inside of your home directory21:56
kirklandbrettalton1: you're welcome.  cheers ;-)21:56
brettalton1kirkland: makes sense, thank you!21:56
directhexecryptfs sounds a lot like encfs21:57
kirklandslangasek: created https://bugs.edge.launchpad.net/ubuntu/+source/linux/+bug/34140522:00
ubottuUbuntu bug 341405 in linux "linux-foo should depend on linux-headers-foo" [High,New]22:00
kirklanddirecthex: it is, but ecryptfs is in the linux kernel;  encfs is entirely userspace22:00
directhexkirkland, is that desirable?22:01
kirklanddirecthex: it is to me22:03
directhexfair enough22:03
kirklandi'm a bit slammed right now, and don't really have the time to defend the strong points of ecryptfs, sorry22:03
kirklandslangasek: https://bugs.edge.launchpad.net/ubuntu/+source/linux/+bug/34140522:06
ubottuUbuntu bug 341405 in linux "linux-foo should depend on linux-headers-foo" [High,New]22:06
kirklandslangasek: you can comment on that, if i've failed to do the justification justice22:07
directhexkirkland, i'm not ranting, i was just curious. i'd heard only of encfs, so wondered what the difference was22:08
kirklanddirecthex: https://wiki.ubuntu.com/EncryptedPrivateDirectory22:09
kirklanddirecthex: search for encfs in that page22:09
kirklanddirecthex: the sourceforge page is no more22:09
kirklanddirecthex: https://answers.edge.launchpad.net/ecryptfs/+question/4630222:10
directhexkirkland, srsly, go back to what you were workign on, don't let me disturb you22:11
kirklanddirecthex: cheers22:12
kirklanddirecthex: come debate it in #ecryptfs on irc.oftc.net, if you're interested in some answers;  there are other maintainers there too22:12
directhexkirkland, not *that* interested, just noticed a small enough gap in my knowledge to ask ;)22:13
kirklanddirecthex: sure.  it's a common question22:14
cjwatsonNCommander: whoops, sorry about that. Looks like I didn't sync the binary Python modules across from the non-ports run properly. I've fixed that and the page is now updated22:34
NCommandercjwatson, thanks, no problem22:35
* NCommander is just beating his head in w.r.t. to GCC22:35
cjwatsonhmm, we seem not to be running maxb's outdate report for all components regularly, for some reason22:36
* maxb really ought to get around to making that include P-a-s information, come to think of it22:37
slangasekok, what keeps launching a separate copy of gnome-power-manager as root on my system?22:38
cjwatsonmaxb: I've updated the relevant cron job to run your script now; sorry about that22:39
cjwatsonapparently we'd run it once and then forgotten about it, or something22:41
Amaranthslangasek: gdm?22:49
slangasekAmaranth: yuck then?22:51
seb128Amaranth: we still use the old gdm codebase there is no reason it should start it22:58
seb128Amaranth: and gdm runs as gdm user22:59
seb128slangasek: it could be dbus activated by something you run under sudo22:59
slangasektwitch22:59
dtchenTheMuso: will need to work logic into removing the notifier hint for #328245, because we can't unconditionally remove it for derivatives not using PulseAudio23:19
TheMusodtchen: point23:19
dtchenseb128: is there a timeline for $GNOME_DESKTOP_SESSION_ID going away (i see it's deprecated)? is there a recommended method of checking if GNOME is the user's active session?23:25
seb128dtchen: I don't think it's going away soon, setting it is cheap and some softwares rely on it23:25
seb128dtchen: check for DESKTOP_SESSION=gnome I guess23:26
dtchenhm, it seems to be 'default' in a default 9.04 install23:27
dtcheni can just check $GNOME_DESKTOP_SESSION_ID being defined, then. thanks.23:28
seb128dtchen: http://bugzilla.gnome.org/show_bug.cgi?id=54288023:29
ubottuGnome bug 542880 in gnome-session "GNOME_DESKTOP_SESSION_ID not set anymore" [Major,Resolved: fixed]23:29
dtchenseb128: right, thanks23:29
seb128dtchen: yeah, do that or verify if gnome-session is running23:29
kirklandsuperm1: let me know what you think about the dkms patch attached to https://bugs.edge.launchpad.net/ubuntu/jaunty/+source/dkms/+bug/34115923:46
ubottuUbuntu bug 341159 in kvm "package kvm-source 1:84+dfsg-0ubuntu7 failed to install/upgrade: " [High,Triaged]23:46
blueyedOFFTOPIC: need some rest? here's some horse porn: http://hellkeyhole.com/horse-porn23:50
Nafalloehrm.23:52
Nafalloplease don't link to porn in this channel...23:52
blueyedNafallo: sry, that's been the channel with the most nicks.. ^^23:52
Nafallowhy would that be relevant?23:53
blueyedmore people that would laugh per posted offtopic link.23:54
Nafalloblueyed: you do realise that link includes some... ehrm... real porn at the bottom, right?23:54
ion_Or more people to get annoyed by it. :-P23:54
blueyedNafallo: sry, haven't realized.. I've not thought about scrolling down after catching up from the floor..23:55
cody-somervillethere is porn right on the right!23:56
LjLand the left! and the top!23:56
blueyedion_: yes, I don't want to disturb at the end.. but the picture itself was so funny after all.23:56
blueyedporn in the bedroom?23:56
ajmitchin other words, pasting that link was a seriously stupid thing to do23:57
cody-somervilleIt isn't even that funny23:57
cody-somervilleFUNNY LINK FAIL23:57
blueyedajmitchm, cody-somerville: I'm still LOLLING about it.. but I get your point. Please execute me, I'm drunk.. ;P23:58
cody-somervilleblueyed, evidently23:58

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!