/srv/irclogs.ubuntu.com/2009/06/30/#ubuntu-desktop.txt

=== rickspencer3-afk is now known as rickspencer3
=== YokoZar1 is now known as YokoZar
rickspencer3robert_ancell: I'm running Karmic on my desktop from a live usb01:04
rickspencer3seems weirdly fast01:04
robert_ancellI didn't notice much of a speed improvement but I haven't changed to ext4 though01:05
rickspencer3should have exported my mailbox first :/01:06
=== WelshDragon is now known as YDdraigGoch
pittiGood morning07:02
robert_ancellpitti, do you know how/why 90_relibtoolize.patch is regenerated in libwnck?07:27
pittirobert_ancell: hey07:27
robert_ancellpitti, hi#07:27
pittirobert_ancell: not in that package in particular; does it look different than other similar patches?07:27
pittihi-sharp, nice07:28
pittias for the "why", no07:28
pittirobert_ancell: if it's not necessary any more, just drop it07:28
pittirobert_ancell: sometimes they are regenerated for some more obscure reasons like making -Wl,--as-needed actually work, and so on07:29
pittirobert_ancell: perhaps check with Seb once he comes online?07:29
robert_ancellpitti, running autoreconf, autoconf, libtoolize doesn't seem to make a very similar patch.  Not sure what it's doing so can't drop it!07:29
robert_ancellwill ask seb though07:29
pittirobert_ancell: which files does it touch ATM?07:30
pitti(lsdiff)07:30
robert_ancelllibwnck-2.26.1/aclocal.m407:31
robert_ancelllibwnck-2.26.1/config.guess07:31
robert_ancelllibwnck-2.26.1/config.h.in07:31
robert_ancelllibwnck-2.26.1/config.sub07:31
robert_ancelllibwnck-2.26.1/configure07:31
robert_ancelllibwnck-2.26.1/doc/Makefile.in07:31
robert_ancelllibwnck-2.26.1/gtk-doc.make07:31
robert_ancelllibwnck-2.26.1/INSTALL07:31
robert_ancelllibwnck-2.26.1/libwnck/Makefile.in07:31
robert_ancelllibwnck-2.26.1/ltmain.sh07:31
robert_ancelllibwnck-2.26.1/Makefile.in07:31
robert_ancellChangelog says "relibtoolize to avoid the amd64 rpath issue"07:31
pittiah07:32
pittiso there's the reason07:32
pittirobert_ancell: are you on i386 or amd64?07:32
robert_ancelli38607:33
pittirobert_ancell: I can do an amd64 build for you if you need one for testing07:39
robert_ancellpitti, thanks, shouldn't need it though, will use ppa if need to build on different arch07:41
pittiok; let me know, though, the turnaround for builing/testing rpath/ etc. might be faster07:42
crevettehello hello08:28
tjaaltonshould there be a script or something to migrate users from the FUSA applet in hardy to what it was replaced with?08:30
pittitjaalton: I thought we had that, as an interactive upgrade hook?08:34
pitti(in intrepid)08:34
tjaaltonpitti: how about hardy-> jaunty?08:34
tjaaltonif it isn't in jaunty anymore, what about hardy -> next LTS?08:34
tjaaltonhrm, lunch, bbl ->08:35
pittitjaalton: it should still be there08:36
seb128hello there08:36
didrocksmorning seb128 and pitti08:37
seb128hey didrocks pitti08:37
pittihey seb12808:37
pittimoin didrocks08:37
seb128didrocks, how are you?08:37
seb128hey pitti08:37
didrocksseb128: fine, thanks :) I get to sleep very early compared to you, viewing the backlog ;)08:38
didrocksand you?08:38
seb128good, I didn't work late for a while now but there was just nothing to watch on TV yesterday and I had things I wanted to do ;-)08:38
seb128didrocks, would you be interested to look at getting mutter packaged for ubuntu?08:39
pittididrocks: BTW, currently working on automatic dependency calculation for distutils-auto08:39
pittiseb128: is this the comparative of "mutt"? :-)08:39
didrocksseb128: yes. I take half of my day off. That's a thing I can have a look :-)08:39
didrockspitti: great! "quickly release" will be able to do something useful then :)08:40
seb128didrocks, excellent08:40
pittididrocks: after that, I'll add a script to create debian/*08:40
seb128I will have a look to gjs so we can aim at having gnome-shell in a ppa before GUADEC08:41
seb128pitti, no, it's the wm part of gnome-shell08:41
didrocksseb128: GUADEC is next week?08:41
pittioh, yet another window manager?08:41
pitticompiz is no more?08:41
didrockspitti: no gnome-shell doesn't work with compiz08:41
pitti(ugh)08:42
didrocks(that was a FUD in the gnome-devel ml)08:42
seb128pitti, GNOME never used compiz08:42
seb128didrocks, this weekend, ie starting on saturday08:42
seb128I'm traveling to go there on friday, there is the opening party in the evening08:43
didrocksseb128: hope you will enjoy it... should be easy in a paradisian country ;)08:43
seb128;-)08:43
seb128thanks08:43
pittimmm Gran Canaria08:43
seb128I'm not sure it's paradisian, it's an island and not really a fancy one I think08:43
seb128it's mainly sun and swimming pools I guess08:44
didrocksseb128: in the meantime, I'm going to Nantes for RMLL... not as attractive in every cases ^^08:44
seb128istanbul was probably nicer to see as a city08:44
seb128have fun there08:44
didrocksthanks08:44
seb128I might prefer Nantes, I'm not a big fan of too warm countries, especially when you go for work and not to stay in the swimming pool during the afternoon08:45
didrockssure, when it's too warm, it's difficult to be effective at work08:45
seb128well they will probably have cold air inside buildings08:46
seb128ie what you need to come back with a cold08:46
didrocksexactly...08:46
seb128anyway I'm sure it will be fun and I'm looking forward going there ;-)08:46
crevetteseb128, and you're an expert in getting cold08:46
crevette(hello)08:46
crevette:)08:46
didrockshey crevette08:46
pittiwe all are *sigh*08:47
crevettehey hey didrocks08:47
seb128lut huats08:47
seb128lut crevette08:47
didrocksplop huats08:47
crevettesalut seb128 & pitti & huats & anyone here :)08:47
pittibonjour crevette08:49
pittiseb128: retracers all failed (python-apt api issue), I'll fix it later08:52
seb128ok08:53
seb128pitti, not sure if you plan to do sru today but could you look at the pidgin yahoo fix for jaunty?08:56
pittisure08:56
pittithat's urgent, I'll process it right now08:57
seb128thanks08:57
seb128the number of duplicates tell us that yahoo is quite used, so we better have to make sure it works correctly in empathy too08:58
robert_ancelldidrocks, can you enable the quickly ppa from https://launchpad.net/~quickly?08:58
seb128hey robert_ancell08:58
robert_ancellseb128, hey seb08:58
seb128robert_ancell, had a good day? busy on updates? ;-)08:59
robert_ancellseb128, packaging question: was updating libwnck and not sure how to regenerate 90_relibtoolize.patch. Any ideas?08:59
robert_ancellI found http://people.dooz.org/~lool/debian/relibtoolize but it looks overly complicate09:00
robert_ancelld09:00
seb128autoreconf09:00
loolrobert_ancell: It's relatively complex and out of date09:00
seb128hey lool09:00
loolrobert_ancell: It did allow me to create smaller diffs than what autoreconf will do09:00
robert_ancelllool, is it needed? It seems to build ok without it09:01
loolBasically autoreconf might run more stuff than strictly necesasry and will run the latest version of tools09:01
loole.g. it might run automake 1.10 even if you have 1.9 and upstream uses 1.909:01
loolSo it will create big diffs (MBs)09:01
seb128I tend to not bother nowadays and use autoreconf which does the job09:01
loolrobert_ancell: The safest thing is autoreconf (-fi)09:01
robert_ancellok09:02
loolI agree with seb128, most of the time that's fine09:02
seb128robert_ancell,   * 90_relibtoolize.patch: relibtoolize to avoid the amd64 rpath issue.09:02
robert_ancellyes, what does that mean...09:02
loolI know that if I only touch autoconf, I can get away with aclocal/autoconf09:02
seb128robert_ancell, I'm not really familiar with that and not sure how to check if that's still an issue in the current upstream tarball09:02
loolBut that's already guessing the tools more than you want09:02
pittiwe could just do an amd64 build without the patch and check if they get rpaths09:02
seb128robert_ancell, it means that the library shouldn't have a rpath on amd64 but it does due to buggy autotools versions09:02
robert_ancellhmm09:03
seb128the easier way to check if that's still an issue is what pitti said but you need an amd64 install09:03
pittiseb128: meh, the pidgin upload refers to bug 389332, which is obviously wrong09:04
seb128robert_ancell, http://wiki.debian.org/RpathIssue09:04
ubottuLaunchpad bug 389332 in libclass-trait-perl "Please merge libclass-trait-perl (0.22-4)(universe) from debian unstable" [Undecided,Fix released] https://launchpad.net/bugs/38933209:04
pittiLaney: ^09:04
seb128pitti, bug #38932209:04
ubottuLaunchpad bug 389322 in pidgin "Yahoo server authentication changed: Pidgin =<2.5.6 will not connect to Yahoo! servers." [Undecided,In progress] https://launchpad.net/bugs/38932209:04
pittiLaney: what is the real bug? could you do another upload with the right number?09:04
pittiah09:04
pittiseb128: thanks09:04
seb128pitti, Laney doesn't have upload right that needs sponsoring, I can reupload with right number if you want09:05
pittiseb128: if you have it ready, would be appreaciated; otherwise I'll download/reupload09:05
pittiugh, what a patch09:05
pitti3000 lines??09:05
tjaaltonpitti: do you have any idea what it's called?09:05
pittitjaalton: unfortunately not; mvo knows09:06
tjaaltonmvo: hey, what script does the migration from the old FUSA to the new one? it's not running on our environment and I'd like to find out why09:06
robert_ancellpitti, can you build lp:~robert-ancell/libwnck/ubuntu and see if it has an rpath issue?09:07
seb128tjaalton, /usr/share/gnome-panel/migrate-fusa-config.py09:07
tjaaltonseb128: ooh, thanks09:07
didrocksrobert_ancell: I will at the end of the week. We will have a first beta available then09:07
tjaaltonmvo: got it already09:07
mvotjaalton: the notice about it is in /var/lib/update-notifier/user.d/09:07
pittirobert_ancell: doing09:07
mvotjaalton: oh, sorry - we did not do a notice for it, we just ran it :)09:08
tjaaltonmvo: ok, figures.. it's disabled here09:08
pittirobert_ancell: shall I drop 90_relibtoolize.patch?09:08
tjaaltonupdate-notifier that is09:08
robert_ancellpitti, I deleted it on my branch09:08
tjaaltonbut maybe there's a better way to disable the usual popups09:09
mvotjaalton: the fusa-script was added via autorun and a gconf key09:09
loolseb128: Oh and morning BTS, sorry missed yours :)09:09
pittirobert_ancell: still here; I delete it locally for testing09:09
seb128pitti, pidgin reuploaded with right bug number09:09
pittiseb128: merci09:10
robert_ancellpitti, check you have 2.26.2, I have pushed my changes now09:10
pittirobert_ancell: ah, I had .109:10
pittimeh, since when does bzr+ssh:// lag?09:10
seb128robert_ancell, did you read the debian wiki url I copied before?09:11
robert_ancellseb128, yes09:11
seb128robert_ancell, you might want to use a rpath call in rules rather than running autotools09:11
pittirobert_ancell: got it; started test build09:12
robert_ancellseb128, it appears to have been built with the 2.2.6 which shouldn't have the problem according to the wiki page09:14
seb128robert_ancell, indeed where 2.26.1 was built using 1.509:16
pitti$ chrpath /usr/lib/libwnck-1.so.22.3.2009:16
pitti/usr/lib/libwnck-1.so.22.3.20: no rpath or runpath tag found.09:16
seb128$ grep VERSION= libwnck-2.26.1/ltmain.sh libwnck-2.26.2/ltmain.sh09:16
seb128libwnck-2.26.1/ltmain.sh:VERSION=1.5.2609:16
seb128libwnck-2.26.2/ltmain.sh:VERSION=2.2.609:16
pittirobert_ancell: dropping the patch should be fine then09:16
seb128\o/09:17
robert_ancellpitti, thanks.  I guess it is safe to go with no patch09:17
robert_ancell:)09:17
seb128no relibtoolize change++09:17
pittirobert_ancell: you'll merge/pull that branch into ~u-desktop?09:17
robert_ancellpitti, yes09:17
seb128pitti, is gvfs-gdu-volume-monitor crashing all the time for you too?09:19
pittiseb128: apparently ye09:19
pittis09:19
seb128(process:13370): libgdu-WARNING **: Couldn't call GetAll() to get properties for /: Launch helper exited with unknown return code 12709:19
robert_ancellseb128, can you update the versions tool? thanks09:20
seb128robert_ancell, done09:21
pittiseb128: I have that, too, and "invalid (NULL) pointer instance" and "Couldn't get daemon properties"09:22
* seb128 investigates09:22
pittiseb128: I wonder why we don't have a d-bus .service for gdu09:23
pittithe gphoto one has one as well09:23
pittibut well, apparently it does run, otherwise it couldn't crash09:24
pittiseb128: SRUs processed, thanks09:24
seb128pitti, gvfs: /usr/share/dbus-1/services/org.gtk.Private.GduVolumeMonitor.service09:24
seb128?09:24
robert_ancellcheers seb128, now it's a lot more red... !09:24
seb128pitti, thanks for the processing09:24
seb128robert_ancell, we need to split this page rather than having a "+" imho09:25
pittiseb128: ah, it's in gvfs; the gphoto one is in -backends09:25
seb128pitti, yeah, the gphoto one is optional where the disk one is required09:25
robert_ancellseb128, why split? What I want to do is have tags to toggle, i.e. gnome, karmic, kde, ... and autogenerate the lists09:26
pittiseb128: usually, a gvfs-mount -l spawns them all again09:26
pittiseb128: but for me that fails immediately09:26
pitti(gvfs-mount:21806): GVFS-RemoteVolumeMonitor-WARNING **: invoking IsSupported() failed for remote volume monitor with dbus name org.gtk.Private.GduVolumeMonitor: org.freedesktop.DBus.Error.Spawn.ChildSignaled: Process /usr/lib/gvfs/gvfs-gdu-volume-monitor received signal 1109:26
seb128pitti, well the gdu monitors crash on start09:27
robert_ancellSo we would probably look at the page with karmic+gnome+ubuntu-desktop tags and others may use other combinations09:27
pittihm, it crashed a lot in the previous versions as well, but now it's immediate09:27
seb128robert_ancell, I find the page less useful that what it could be, I'm not interested by many things there, some are in universe etc09:27
seb128robert_ancell, I think it would be better to have a list for this team and one for contributors, motus, etc09:27
robert_ancellseb128, do you mean the page when expanded?09:28
pittiat least it's easy to gdb, it crashes immediately09:28
seb128pitti, right, I'm rather concerned about the helper message I'm wondering was is displaying it the string is not a gvfs one09:28
seb128robert_ancell, the page expended or not09:28
robert_ancellseb128, everyone's interest is going to be different.  There's always trouble when defining where each team ends09:28
seb128robert_ancell, well the thing is that clicking on "+" mix those extra components in the middle of the standard list09:29
seb128robert_ancell, ie you can't point motus easily to the extra components09:29
robert_ancellseb128, yes, that is where I think having a tag system will work better09:30
seb128how would it work?09:30
huatshello everyone !09:31
robert_ancellhuats, hi09:31
huatsseb128, robert_ancell, crevette o/09:31
robert_ancellseb128, we have tags along the top of the page which act like toggle buttons09:31
robert_ancellyou chose which ones are enabled and packages with that tag are shown09:31
seb128robert_ancell, hum, that would work for me yes, if you know how to do that ;-)09:31
robert_ancellcan do09:32
seb128cool09:32
seb128pitti,09:33
seb128$ devkit-disks --show-info /dev/sda109:33
seb128Cannot find device with major:minor 8:1: Launch helper exited with unknown return code 12709:33
pittiah09:33
pittimy bug then, apparently09:33
seb128or I'm using that command wrongly?09:33
pittino, indeed it crashes now09:33
pittidevkit-disks --dump -> same09:34
pittithe d-bus backend isn't running09:34
seb128iz kit bog09:34
seb128(devkit-disks:14751): devkit-disks-WARNING **: Couldn't enumerate devices: Launch helper exited with unknown return code 12709:34
seb128right09:34
pittiodd, it didn't change in over a week09:34
seb128devkit-daemon is running09:34
pittiright, wrong kit09:35
pittiyou need /usr/lib/devicekit-disks/devkit-disks-daemon09:35
seb128that is not running09:35
pittidk-disks doesn't even use devicekit any more09:35
seb128/usr/lib/devicekit-disks/devkit-disks-daemon: error while loading shared libraries: libgudev-1.0.so.0: cannot open shared object file: No such file or directory09:35
seb128doh09:35
pittiaaah09:35
pittithat was the udev upload yesterday09:35
pittiapparently it needs a rebuild due to changed library path09:36
pittierm, no09:36
pittiitz Keybuk bug09:36
pitti$ dpkg -L libgudev-1.0-009:36
seb128libgudev-1.0.so.0 => not found09:36
pitti-> empty09:36
seb128Scoooooootttttt09:36
* pitti pokes09:36
pitti-dev is empty as well09:37
seb128Keybuk, ^09:37
pittiasac: ^ just in case your network-manager doesn't build09:37
pittiKeybuk: could you please bzr push your udev branch?09:37
pittibzr is at 143-209:37
tjaaltonI'd like to disallow the users to restart/shutdown the machine, and I understood it should be possible by poking polkit.. But the docs are a bit sketchy on that :/09:39
pittiKeybuk: hm, there is no debian/libgudev*.install -- that might be it?09:39
asacthanks for the heads up09:39
pittitjaalton: in karmic that's currently a bit hard; in jaunty you should be able to use polkit-gnome-authorization (it's also in the admin menu)09:40
* asac remembers to not dist-upgrade just now09:40
pittitjaalton: however, for local users it hardly makes sense -- they can just press the power button?09:40
pittior sysrq09:40
tjaaltonpitti: yes, it's just a matter of giving the gun or pulling the trigger ;)09:41
Keybukpitti: I get a .deb in my working directory09:41
seb128Keybuk, empty deb?09:41
pittiKeybuk: right, but it's empty (jusr doc)09:41
pittiKeybuk: forgot to bzr add the libgudev*.install files?09:42
Keybukoh maybe09:43
Keybukwould have wiped them too09:43
pittiargh devhelp broken :(09:43
* Keybuk hates packaging with bzr09:43
KeybukI'm about -> <- this far from just giving up and doing it the old fashioned away again09:43
Keybukpitti: uploaded one that should fix that09:47
pittiKeybuk: thanks09:47
seb128Keybuk, thanks09:47
seb128hey rodrigo_09:47
rodrigo_morning09:47
pittiKeybuk: eww, aren't they installed into usr/lib, not /lib?09:48
Keybukpitti: no idea09:48
pitti--libdir=/usr/lib \09:48
pitti$ cat debian/libgudev-1.0-0.install09:48
Keybukthat's the way Kay said to do it ;)09:48
pittilib/libgudev*.so.* usr/lib09:48
Keybukwill see what the build does09:48
pittiright, but the .install expects them in /lib09:49
Keybukyeah you're right09:51
* Keybuk fixes the wildcard "pkgconfig" include too09:52
Keybukand the wildcard /usr/include ;)09:52
pittithank you09:53
pittiKeybuk: what's wrong with /usr/include?09:53
Keybukpitti: that'd include everything in /usr/include09:54
Keybuklike other files that udev makes09:54
pittiah, for libudev09:54
pittiKeybuk: btw, did Kay already show kayfs to you? ("devfs is back")09:55
pittihe showed me at LinuxTag, looks pretty nice09:55
pittiinit=/bin/sh -> takes 0.6 seconds and has a correctly populated /dev09:55
pittiit's called "devtmpfs", IIRC09:56
Keybukyeah :)09:56
KeybukI'm not convinced by it though09:56
Keybukgrr10:00
Keybuknow I just modified files in the build directory and lost them when I rebuilt10:00
* Keybuk wonders when bzr is going to make his life easier10:01
Keybukright now, it just makes everything four times harder10:01
seb128Keybuk, not true it makes sponsoring easier ;-)10:02
Keybukseb128: disagree strongly10:02
Keybukgrabbing someone's debdiff and applying it was easy10:03
seb128well I find easy to review a bzr for incremental changes than a serie of debdiff on a launchpad bug10:03
seb128well the issue is when you start having new version updates and comment and go through several iterations10:03
seb128it's not easy to diff the debdiff to see the changes10:03
Keybukbzr's output is just a patch too10:04
seb128where it's easy to read the commits10:04
Keybukexcept I have to work harder to get that patch10:04
seb128I find easier to bzr pull than to open launchpad, download a file, apply it, etc10:04
Keybukyou only know to bzr pull because they gave you the URL to pull from10:05
Keybukhow is that any different from them giving the URL of the debdiff?10:05
Keybukexcept that with the debdiff approach, the URL gives you exactly what you need to review10:05
Keybukand you don't need to go through hoops to get it10:05
Keybukthe bzr command to "show me the changes that this URL would bring to my branch" is still delightfully obtuse10:05
seb128different workflow I expect10:06
Keybukgedit URL > bzr diff -r ancestor:. URL10:06
Laneypitti, seb128: Ugh. Typo. Sorry10:06
seb128I usually sponsor desktop packages and they are in ubuntu-desktop/component/ubuntu10:06
seb128not to mention that we usually have new versions and only the debian directory in bzr so debdiff don't really work, or you need a debian directory diff and download the tarball10:07
seb128anyway no point to discuss for hours, it works fine for sponsoring for most people on this channel but different people have different workflows10:08
pittimeh, x freeze and fsck10:09
=== pochu_ is now known as pochu
seb128Laney, want to work on the pidgin 2.5.8 update for karmic? ;-)10:21
Laneyaaaaaah pidgin10:21
* Laney runs screaming10:21
Laneywhat's new there?10:22
seb128some bug fixed apparently, debian already did the upgrade, it should be easy enough10:22
seb128either reapply your previous merge diff on it and just do the update10:22
Laneyalright I'll have a look tonight10:22
seb128thanks10:22
LaneyI'm going to give up on Hardy unless you have found another distro which has done the work10:24
LaneyI just requested the backport instead10:24
didrocksseb128: before going back to home and working on mutter. What do you prefer for this package dh5, dh7 or cdbs? (I know that you are a fan of cdbs ;))10:30
seb128hum no, can't find a distribution doing that backport10:31
seb128didrocks, your call but dh7 or cdbs are nicer10:31
didrocksseb128: ok, it's maybe the time to try dh7, be indulgent so ;)10:31
seb128I will have to learn it too ;-)10:32
seb128but it's a good occasion10:32
didrocksexactly :-)10:32
seb128bbl10:34
Laneydh7 is very nice to use10:35
Laneymakes cdbs go away imho10:35
pittior, at least, considerably simpler10:46
pittididrocks: \o/10:51
pitti$ test/auto.py -v T.test_requires10:51
pittiautomatic requires ... ok10:51
pittididrocks: from that it should not be too hard to figure out the automatic package dependencies10:51
didrockspitti: congrats ^^10:53
chrisccoulsonanyone working on the control-center update?12:05
pittididrocks: I'm about to change the spec from "./setup.py debian" to "python-distutils-mkdebian"; would that be alright for you?12:06
pittididrocks: I want to avoid putting Debian specific stuff into the upstream distutils-extra12:06
seb128chrisccoulson, no12:06
chrisccoulsoncool, i'll take that one then if that ok12:06
chrisccoulson** if thats ok12:07
seb128good12:07
chrisccoulsonthanks:)12:07
* pitti hugs chrisccoulson12:07
seb128thank you for working on it ;-)12:07
pittididrocks: https://wiki.ubuntu.com/DesktopTeam/Specs/Karmic/AutomagicPythonBuildSystem?action=diff&rev2=15&rev1=14 in particular12:07
* chrisccoulson hugs pitti12:07
seb128let's get some food though it's so warm there that I'm not hungry12:09
pittiseb128: ice cream!12:11
seb128pitti, good idea for after lunch ;-)12:11
chrisccoulsonis everyone enjoying hot weather? it was raining very heavily here on my drive to work this morning12:14
hyperaircould someone in the desktop team advise me about the best way to go about bug #214420 ? as i understand it, usershare owner only = false'12:17
ubottuLaunchpad bug 214420 in nautilus-share "nautilus-share can't share ntfs/fat32 folders" [Undecided,New] https://launchpad.net/bugs/21442012:17
=== mvo is now known as mv
=== mv is now known as mvo
hyperair+was supposed to be a security measure12:18
hyperairi mean usershare owner only = true12:18
pittino idea about that, I'm afraid; slangasek understands samba and might be able to help12:18
hyperairi'll wait for his input then12:22
asaclool: you remember the passphras for pkg-mozilla-maintainers ?12:31
asac(mailing list)12:31
asaclool: could you allow asac@ubuntu.com to send there and moderate the last three mails i sent ;)? thanks!!12:31
didrockspitti: please, you can change. I will adapt my code later :)12:36
pittididrocks: ok, thanks12:37
didrockspitti: yeah, python-distutils-mkdebian makes sense :)12:37
pittididrocks: I actually renamed it to python-mkdebian now12:37
pittisince it works with any setup.py generated .egg-info, not just distutils or even just distutils-auto12:38
pittiyay being generic :)12:38
pitti.egg-info is an existing standard, which I just use as input for generating the debianization12:38
pittianyway, lunch o'clock12:38
asacenjoy12:39
didrockspitti: great ;) looking at those egg-info stuff is on my schedule too… ;)12:39
didrockspitti: have a good lunch!12:40
* didrocks jumps on mutter packaging12:40
seb128hyperair, not sure about this usershare issue either12:47
seb128hyperair, btw if you work on nautilus-share could you have a look at switching it to gtkbuilder?12:47
hyperairseb128: okay, i'll take a look at it.12:47
hyperairpatches welcome though =p12:47
hyperairseb128: when will glade be phased out?12:48
seb128thanks12:48
seb128I might have a look, I already did some patches for other applications12:48
loolasac: Are these direct messages?  Perhaps you can subscribe to the list with all addresses you use and disable delivery12:48
seb128well I expect it will still be installed by default in karmic but not in karmic+112:48
seb128but reducing the rdepends list would be nice12:48
loolasac: I'm happy to hand you admin and/or moderator permissions; I'd like to avoid maintaining black/whitelists12:48
loolasac: nothing in queue for pkg-mozilla-maintainers@lists.alioth.debian.org actually13:00
asachmm13:03
seb128mvo, hey13:03
asacis that on auto reject?13:03
asaclool: oh ;) ... it was a different mailing list ;)13:04
asacthe moz-extmaintainers ;)13:04
loolDon't know about that one :)13:04
seb128mvo, do you think you could update libgksu to the current debian version?13:04
seb128mvo, you know the package better than me and I'm a bit busy with GNOME3 things before desktop summit13:05
mvoseb128: sure, I was sure that someone else did the merge, but I'm probably wrong13:05
seb128mvo, there is no hurry but kov applied my gtkbuilder change so it would be nice to have in karmic ;-)13:05
mvo!13:05
seb128mvo, the most recent upload is not from you right, let me know if you are too busy I will put that on my todolist for later, I pinged you because I know you worked on this one before and know it a bit13:06
mvoseb128: no prob, I can do the merge13:08
* seb128 hugs mvo13:08
mvoseb128: I ported g-a-i to gtkbuilder today, you have been inspiring13:08
mvo:)13:08
seb128mvo, \o/13:10
=== MacSlow is now known as MacSlow|lunch
wiwarhow to switch off  "Mirror Screens" ("System"->"Preferences"->"Screen Resolution") option with configuration files ?13:40
seb128what do you mean by configuration files there?  why not using the tool?13:42
wiwar> why not using the tool? <    Because It doesn't save it's settings. Each time I should set them again, and that settinngs doesn't affect on output13:48
seb128wiwar, could you describe what you do exactly and the issue you get?13:50
wiwarseb128, I am trying to setup triplehead configuration. Here is my config - http://pastebin.com/m988061113:53
wiwarThe issue i get - left and central monitors show identical images13:53
seb128wiwar, is your issue with the dialog that it fails to apply your changes or that those are not applied after next login?13:54
wiwar"Mirror Screens" is selected and I am unable to deselect it13:54
seb128you might want to open an upstream bug on bugzilla.gnome.org13:55
wiwarFirst I deselect this option, then press "apply" button, then close dialog. When I open dialog again - option is still checked13:55
seb128I doubt many people have 3 screens to test such configs so it would not be surprising if it didn't get lot of testing13:56
seb128the configuration is written as monitors.xml in .config13:56
hyperairseb128: i'm working on the glade->gtkbuilder transition now. what's the gtkbuilder version of glade_xml_new(FILE, "first_widget", GETTEXT_PACKAGE)? the reference page on library.gnome.org only says how to deal with no GETTEXT_PACKAGE14:09
hyperairhmmmm maybe strings are already translated? =\14:10
seb128hyperair, http://library.gnome.org/devel/gtk/stable/gtk-migrating-GtkBuilder.html14:17
hyperairseb128: i'm already staring at that!14:17
hyperairseb128: but it only shows the alternative for glade_xml_new(FILE,"first_widget",NULL) <-- note the NULL as opposed to GETTEXT_PACKAGE14:18
hyperairseb128: if GtkBuilder automatically translates the strings, that's a different case14:18
seb128you have a translation domain different from the software one?14:18
seb128translations should be working out of the bug as for any other string using gettext14:20
hyperairah then it's fine14:21
=== MacSlow|lunch is now known as MacSlow
* hyperair attempts to compile14:28
pittirickspencer3, didrocks: wrt. the version number and generating debian/changelog, how is the workflow? does version in setup.py get bumped on "release", or immediately after "release"? what should python-mkdebian do if that version already exists in debian/changelog?14:35
rickspencer3pitti: I would think you would increment the version, and then release14:36
kenvandinepitti, i would vote for bumping it after release14:36
kenvandine:)14:36
rickspencer3hehe14:36
kenvandinelook at what gnome does14:36
kenvandinefirst commit after a release is bumping the version14:36
* kenvandine rather likes that model14:36
pittiusually you bump immediately after and set it to "UNRELEASED", and "release" sets UNRELEASED -> karmic14:36
kenvandinepitti, that is my preference14:37
kenvandinepedro_, good morning14:37
pittiso, should python-mkdebian bail out with an error if not "UNRELEASED" and setup.py version == debian/changelog versin?14:37
rickspencer3pitti: I'm not clear on how it is different for the user ... are you suggesting that your script incrememnts the version number after a release?14:37
pedro_morning kenvandine14:37
pittirickspencer3: no, the build system doesn't ever touch setup.py14:38
pittihey pedro_14:38
pedro_hello pitti14:38
rickspencer3so the user has to increment it at *some point* before they release14:38
pittirickspencer3: it's probably a moot point, since debian/changelog cannot actually get "sensible" entries unless we are using proper version control14:38
rickspencer3we could do a commit before release if that would help14:39
didrockspitti: rickspencer3 also proposed that quickly release version_number can bump the release in setup.py if not done before14:39
pittiseb128: ah, gdu-monitor works again with current udev14:39
pittididrocks, rickspencer3: ok, easier questions: (1) should python-mkdebian error out if you try to call it on the same version twice? (2) do you want to use the UNRELEASED schema, or just keep it at "karmic" all the time?14:40
rickspencer3pitti: I think it should error out, at least for the first iteration14:41
rickspencer3seems simpler to me14:41
didrockspitti: python-mkdebian touches the changelog entry?14:41
pittirickspencer3: that would imply keeping it at UNRELEASED, and then something has to call dch -r14:41
pittididrocks: well, if no changelog exists, we dch --create, that's easy14:41
rickspencer3oh, I was thinking the script just bails and the user starts over14:42
pittibut I wonder what should happen if it already exists14:42
pittirickspencer3: well, you might want to build several test debs until you release14:42
pittiwell14:42
pittiI think I keep it very easy for now14:42
didrockshum. I prefer UNRELEASED too. But I'm unsure for python-mkdebian question14:42
pittidon't use UNRELEASED, and just do nothing if the changelog entry already existsi14:42
pittiif we need something more elaborate, we can bolt that on later14:42
pittithat way it will never fail14:43
rickspencer3pitti: right14:43
pittiand release management is entirely up to quickly14:43
didrocksok, we will see then what people ask for :)14:43
rickspencer3right, quickly could detect the error and do something14:43
pittihttp://bazaar.launchpad.net/%7Epython-distutils-extra-hackers/python-distutils-extra/debian/changes making good progress :)14:43
rickspencer3simple is good14:43
pittirickspencer3: in that simple model there wouldn't ever be an error14:44
pittii. e. python-mkdebian knows nothing about the concept of a "release"14:44
pittibut of course we need to track it somewhere, e. g. you can't upload the same version twice14:44
didrockspitti: python-mkdebian just read the changelog to detect the version according to setup.py, add dch -i if not the same and build the package?14:45
rickspencer3pitti: quickly could detect it *first* before it kicks off the script14:45
pittilet's see how that will work out14:45
pittididrocks: right14:45
didrockspitti: for uploading, this is really on quickly side, I think.14:45
didrocksso, quickly has to detect it as it is the link with launchpad14:45
pittididrocks: I agree, makes things less complicated and less prone to inconsistencies14:45
pittididrocks: well, if I were you, a "quickly release" or "quickly upload" would just bump the version after a successful upload14:46
didrockspitti: that's possible, but how to guess that user wants going from  3.0 to 3.1, or 3.5, or even 4.0 ? (no real example included) ;)14:47
pittididrocks: oh, do you care? I thought you'd just start with 1 and then just count upwards14:48
didrockspitti: ok, let's do that in a first approach14:48
pittididrocks: if you want more elaborate major/minor, you just have to ask or --version then, I guess14:48
pitti"quickly release-management" (is this simple and fun? :-) )14:49
didrockspitti: will see that for quickly 0.2, let's just bump for the moment ;)14:50
=== evanrmurphy_ is now known as evanrmurphy
rickspencer3didrocks: we should get quickly into a ppa by Friday it possible14:56
rickspencer3what should I prioritize between now and then? fixing the tutorial up?14:57
didrocksrickspencer3: yes, fixing the tutorial. I will finish the release command.14:58
didrocksI'm currently working on the mutter packaging. I will then work on quickly to polish those little things :)14:58
didrocksand then release 0.1~alpha in the ppa14:59
pittididrocks.fork()14:59
didrockspitti: ahah ;)15:00
didrockscurrently, it's more didrocks.laptop.pbuilder.karmic.make_distcheck()15:01
SiDiEAGAIN, pitti15:03
pittididrocks, rickspencer3: so, changelog looks pretty boring, but it works: http://paste.ubuntu.com/206975/15:03
pittiSiDi: hello?15:03
SiDipitti: nevermind :p EAGAIN is an error code for when you cant get a process when fork'ing15:04
pittiSiDi: oh, I see :)15:05
didrockspitti: this is only in the case where the user only "quickly release" if she/he "quickly release something very interesting", quickly will change it in the changelog.15:05
vladzurhi, somebody know how edit HD videos? (m2ts)15:05
pittididrocks: oh, are you saying that you want to maintain debian/changelog yourself?15:05
pittididrocks: by default, mkdebian will put in "new release" right now, so that it also works independently of quickly15:05
pittididrocks: but I can add a parameter for a changelog entry if you want me15:06
didrockspitti: it would be awesome ;)15:06
pittididrocks: (in the next version, I want to get this working with a simple approach first)15:06
pittiI'll add optparse to it later, then15:06
didrocksperfect, let's just write it somewhere to remember later15:07
pitti        # TODO: add CLI option to specify changelog15:07
pitti^ done15:07
didrocks:)15:08
didrockshum, mutter seems to require a updated clutter version. The configure is ok, but it FTBFS with incompatible pointer type…15:09
seb128didrocks, should be easy to change?15:10
didrocksseb128: if I look deeper, it's more a function call error (not the god signature): guint is expected and gfloat is given15:11
seb128didrocks, do you use a tarball or git?15:12
didrocksseb128: git, they didn't roll tarball for mutter15:12
seb128oh15:12
didrocksseb128: last taggued version in the git branch is still a metacity package also15:13
seb128better to use current git15:14
seb128those are not aimed at karmic proper but to a gnome-shell ppa for now anyway15:14
didrocksseb128: yes. I just have to fix this FTBFS and see if transtyping from gfloat to guint is harmless in this case :)15:15
pittiNow running lintian...15:19
pittiW: jockey: binary-without-manpage usr/bin/jockey-gtk15:19
pittiW: jockey: binary-without-manpage usr/bin/jockey-kde15:19
pittiE: jockey: extended-description-is-empty15:19
pittinot too bad for a completely autogenerated package15:19
idorock89hi i wanted to ask about empathy15:20
idorock89will it have google video chat and msn video chat in time for karmic?15:21
artirgoogle video chat (jingle) already works15:23
didrocksseb128: I think that's a warning transformed in a error. I infer that launching autogen.sh on a non official version which calls gnome-autogen.sh enables a --debug or --enable-debug option when configuring. Are you aware about this and how to desactivate it when running autogen.sh?15:24
Zdraidorock89: MSN video/audio is being worked, difficult to say if that will be ready for karmic, but upstream is close to get it done AFAIK15:25
Zdraidorock89: and google video is already done15:25
Zdraidorock89: since latest release of gabble15:25
idorock89Zdra: wow really didnt see a blog post about it on any planet.15:26
idorock89Zdra: so i can video chat from empathy 2.27.4 to windows user using gmail video chat ?15:26
Zdraidorock89: I think, yes15:27
idorock89Zdra: ok.really cool.15:27
artiranother "cool" thing is that if u have 2.27.* and other guy has 2.26 and u try to do a videochat with him, his empathy will crash :P15:28
Zdraidorock89: you need telepathy-gabble 0.7.30 released yesterday15:28
seb128didrocks, is -Werror set?15:28
didrocksseb128: yes. I try to pass --disable-debug to autogen.sh, without success15:30
seb128didrocks, -Werror is probably defined in configure.in somewhere15:31
seb128just drop it before running autogen15:31
didrocksseb128: ok. I was thinking of a better way with options handled by autogen.sh, but well… ;) let's try to seek in configure.in15:32
idorock89artir: and did u try it with someone on windows using gmail video chat?15:34
artirnope15:34
artirjust empathy to empathy15:34
Ampelbeinseb128: hi. do you think bug #256041 is worth a SRU? Provided that the fix gets in karmic of course.15:39
ubottuLaunchpad bug 256041 in gnome-panel "gnome-panel crashes when clicking launcher on second screen" [Medium,Triaged] https://launchpad.net/bugs/25604115:39
didrocksseb128: well, that works for easy casting thing. Now, it seems there is an error with an external function: http://pastebin.com/m6bd1388a)15:42
* didrocks will poke upstream ;)15:42
seb128didrocks, upstream is on on irc.gnome.org15:47
seb128Ampelbein, there is no duplicate for the bug so it doesn't seem a frequent user complain15:47
seb128Ampelbein, but otherwise could be a candidate for a sru yes15:47
didrocksseb128: yep, I'm already there. Seems that's because of an old clutter lib15:48
seb128didrocks, they use clutter 0.8 or 0.9?15:48
didrocksseb128: clutter-0.9.4 is needed15:49
seb128didrocks, it's in universe enjoy the update ;-)15:49
didrocksseb128: I was sure you were about telling that ;-)15:49
seb128hehehe15:50
didrocksseb128: upstream also told me that there is a whole bunch of changes just pulling right now. So, I'm waiting for an hour ;)15:51
seb128didrocks, you can probably do the clutter update during that time ;-)15:52
didrocks:p15:52
seb128didrocks, your work is really appreciated btw in case I don't tell it enough ;-)15:52
didrocksseb128: thanks ;-)15:53
mvoand another app ported to gtkbuilder: update-manager16:04
pitti\o/16:04
pittiI ported jockey yesterday16:04
mvofortunately hardy python-gtk2 supports it16:04
mvoso even the release upgrader can be ported :)16:04
mvostill some more to go (gdebi, langauge-selector, software-properties, synaptic), but fortunately its pretty trivial16:05
seb128yeah, I did libgksu and nautilus-sendto yesterday16:05
mvosweet16:06
=== seb128_ is now known as seb128
dobeypitti: ping16:17
pittihey dobey16:17
dobeypitti: does the .examples file in debian/ need to match the binary pkg name, or the source?16:17
pittidobey: binary (that's true for all debhelper files)16:18
dobeypitti: ok. just wondering because the two comments in REVU from you didn't line up exactly :)16:18
dobeypitti: and what's the Vcs-Bzr: syntax? lp:project works?16:20
pittidobey: it points to the https://code.launchpad.net/... page with the branch, if you use bzr for packaging16:21
pittiwith that, other developers know if/where to commit changes16:21
dobeyok16:21
dobeyi'll leave it out for now then. as there are still some changes that need to be done for that16:22
asacawe: there atm?16:28
aweasac: yea16:28
asacawe: do you think we should just track tags for connman or upload latest git?16:29
asacseems there is a lot of activity in the past 6 weeks (since last tag)16:30
awebut no new tag?16:30
asacand most likely the -gnome bits need the latest anyway16:30
asacawe: no new tag for 6 weeks yes16:30
awesounds like we have no choice then16:31
asacand maybe 120 commits or something ;)16:31
mvompt: I looked at bug #377697 and it seems like update-manager should not be auto-opend if running on battery16:38
ubottuLaunchpad bug 377697 in update-manager "update manager should warn about laptop running on battery when installing big updates" [Wishlist,Fix committed] https://launchpad.net/bugs/37769716:38
mvompt: does that sound right to you?16:38
mpthmmm16:39
mptmvo, that would mean you were never notified if you only ever work on battery (and charge it while suspended/off)16:40
mvoyes16:40
mptso, maybe not :-)16:40
didrocksseb128: clutter upstream removed a bunch of symbols without bumping the soname (between 0.9.2 and 0.9.4). the library is still named libclutter-glx-0.9.so.0. What do you think we should do?16:41
mvompt: ok16:41
seb128didrocks, no rdepends -> upgrade16:41
seb128didrocks, you can ask upstream about it but they will probably say that 0.9 is unstable and has no stability guaranty16:42
didrocksok, let's be afraid in seing the number of rdepends ;)16:43
seb128lol16:43
seb128none? ;-)16:43
didrocksexactly ;-)16:44
didrocks\o/16:44
* didrocks wonders why he checks API compatibility before performing rdepends ;)16:44
seb128lol16:45
seb128because for stable updates you don't want to break api16:45
didrocksseb128: yes, for third-party apps, right? (even if there are no rdepends)16:46
seb128didrocks, indeed16:46
pittiKeybuk: bzr push in udev please16:48
* pitti currently wrestles with a gtk-doc FTBFS16:49
Keybukpitti: pushed16:49
pittiKeybuk: it seems that you somehow did some magic to the tree to actually build; here it fails on a missing version.xml16:50
pittiI start with a clean bzr, then gtkdocize --copy, then autoreconf -fvi16:50
Keybukthe magic is in debian/rules16:51
pittiKeybuk: I'll add --fail-missing to dh_install and add the missing bits, FYI16:51
Keybukpitti: that'll fail the entire build16:51
pitti(such as the consolekit helper)16:51
Keybukdue to the way it does udebs16:51
KeybukI think I also deliberately miss things out16:51
pittiKeybuk: I just see debian/rules tarball?16:51
Keybukpitti: right, that makes the tarball16:52
Keybukdebian/rules package makes the source package16:52
pittiah, and then you untar this into . ?16:52
Keybukright16:52
Keybukwell, I unpack that source package and build from there16:52
pittihm, unpacking the tarball leaves a huge bzr diff (probably from git pull after 143)16:54
Keybuksure16:54
Keybuk'tis what you'd expect16:54
* pitti reverts that and hopes for the bets16:55
pittibest, too16:55
Keybukreverts which bit?16:55
pittiwell, I did "tar xzf ../udev_143.orig.tar.gz --str=1" into the bzr tree16:55
Keybukoh16:55
Keybukdon't do that ;)16:55
pittibut that restores the files to 143 release16:55
Keybukjust bzr get the source tree16:55
pittiit doesn't use bzr-buildpackage, nor patches, so how else would I get an actually buildable source tree under bzr control?16:56
Keybukthis was so much easier when all we had to do was "apt-get source" :)16:56
Keybukpitti: you can't16:56
pittierm16:56
Keybukthe bzr tree is unbuildable16:56
pittibut how else do I do, test, and commit several changes?16:56
pittihm16:56
Keybukbut you can make a source package from it16:56
Keybukunpack the source package16:56
Keybukand test that16:57
pittimeh, that's hilarious16:57
KeybukI agree16:57
Keybukbzr fail16:57
pittirevision control+autoconf fail, rather16:57
pittithey really hate each other16:57
* Keybuk looks forlornly at his multi-year-open bugs against bzr that prevent a buildable udev from being checked in16:57
Keybukit's nothing to do with autoconf16:57
Keybukautoconf is just fine with revision control, cf. upstart16:57
Keybukit's make vs. revision control16:58
Keybukor more accurately, bzr's inability to apply any common sense to timestamps16:58
pittiwell, why wouldn't I be able to autoreconf and build the bzr tree?16:58
pittithis should just work..16:58
Keybukbecause then dpkg complains about things like the test/ subdirectory16:58
Keybukwhich only exists in bzr16:58
pittino16:58
Keybukthat's a dpkg issue ;)16:58
pittimake fails16:59
Keybukmake works here16:59
pittiit stumbles over a missing version.xml for gtk-doc16:59
pittiwhich apparently gets magically generated in the tarball16:59
Keybukoh16:59
Keybukright16:59
Keybukthat's a gtk-doc issue16:59
Keybukwhich is broken16:59
Keybukit doesn't even support out-of-tree builds properly ffs16:59
pittibut it works with the uploaded udev17:00
Keybukright, because the tarball has the extra magic files you need17:00
pitti(which incidentally ships pre-made version.xml files)17:00
Keybukbut you can't put those files into the bzr tree, because bzr screws up timestamps17:00
pittiif I copy them from the tarball, it works17:00
pittibut why would I in the first place?17:00
Keybukbecause that's the right thing to do17:00
pittiit should just build version.xml from .in at build17:00
Keybukgtk-doc doesn't do that17:01
pittieither by make, or by autoreconf17:01
Keybukbecause of the out-of-tree build17:01
Keybukit's broken ;)17:01
Keybuksee above17:01
pittiah, that's why you have to do make all dist?17:01
Keybukyou got it :)17:01
pitti*ugh*17:01
Keybuktell me about it17:01
pittiKeybuk: ok, thanks for the heads-up17:01
Keybukideally, what I'd do would be17:02
Keybukbzr pull from git to update to a new release17:02
Keybukthen import the tarball over the top, to add all of the missing files17:02
Keybukthen pull from that into the ubuntu tree17:02
Keybukto pull from git head, I'd just pull directly17:02
Keybukthat should cause automake to regenerate all the files anyway, and commit them along with the merge17:03
Keybuk*but*17:03
KeybukI can't pull from git, because bzr-git can't read the udev git repo17:03
Keybuk(to be fair, even bzr fast-import has issues on a near weekly basis)17:03
KeybukI can't import the tarball, because bzr doesn't apply sane timestamp logic, so you end up in a rebuild death spiral17:03
seb128didrocks, \o/ new clutter ;-)17:03
Keybukso I sit here, in my little house of fail17:03
Keybukoh, and then I'd do dpkg-buildpackage (or bzr-buildpackage) to make the source package17:04
Keybukbut that doesn't work either, because of the things that are in git but not in the tarball17:04
Keybukand dpkg goes nuts about them17:04
Keybukpitti: it occurs that if it's obvious that a particular file (version.xml) doesn't exist17:07
Keybukwe could have a debian/rules snippet to do everything required to make it17:07
Keybukand have other things depend on it17:07
pittiright17:07
Keybukand could get rid of the clean-tree things then17:07
Keybukwhich are "throw away everything I forgot to commit plz"17:07
pittiKeybuk: I'm in the middle of figuring out the magic incantatino to turn a bzr checkout into a buildable tree17:07
Keybukpitti: it's the bits at the top of tarball17:07
pittiKeybuk: I'd like to add that as debian/rules prep or so17:07
Keybukthough you need to not use autogen.sh17:08
pittino17:08
Keybukgtkdocize --copy17:08
pittiautogen.sh is broken17:08
Keybukautoreconf --install17:08
pittiright17:08
Keybukmake distclean17:08
Keybuk./configure --enable-gtk-doc17:08
Keybukmake all dist17:08
Keybukhmm17:08
Keybukactually omitting the make distclean will work if not using autogen.sh17:08
Keybukgtkdocize --copy17:08
Keybukautoreconf --install17:08
Keybuk./configure --enable-gtk-doc17:08
Keybukmake all dist17:09
Keybuk;)17:09
pittikdocize --copy17:09
pittiautoreconf -fvi17:09
pittirm -rf autom4te.cache/17:09
pitti./configure --enable-gtk-doc17:09
pittimake all dist17:09
pittimake distclean17:09
pitti(plus the missing "gt")17:09
KeybukNO!17:09
Keybuknever use autoreconf -f17:09
Keybukever17:09
Keybukever17:09
Keybukever17:09
KeybukBAD PITTI!17:09
pitti*shrug* it's a clean tree17:09
* pitti removes the -f, I don't particularly care17:09
Keybukmake all dist distclean would work ;)17:09
Keybukpitti: putting -f in there is a bad habit to get into17:10
Keybukautoreconf shouldn't even *have* a -f17:10
Keybukautoreconf -f really means "forcibly update everything auto-* related to the latest version, whether or not it'll work"17:10
pittiKeybuk: nope, that's still not it17:12
pittiwarning: failed to load external entity "../version.xml"17:12
pitti../libudev-docs.xml:10: parser error : Failure to process entity version17:12
pitti$ find -name version.xml17:12
pitti./build-deb/extras/gudev/docs/version.xml17:12
pitti./build-deb/libudev/docs/version.xml17:12
pittibut not in the root tree17:12
Keybukerr17:12
Keybukwhy were you in build-deb to begin with?17:12
pittidistclean might wipe it?17:12
Keybukoh, maybe17:12
pittiI wasn't17:12
pittiI did above steps in root, then buildpackage17:12
Keybukof course, if you don't "distclean" you can't build17:13
Keybukyou'll get "source directory is configured, wah wah sky is falling"17:13
pittibut how did it ever go into the orig.tar.gz then?17:13
pittiah, make dist17:13
Keybukyou can see how I got to the point where I just make a source package from bzr17:14
Keybukunpack it elsewhere17:14
Keybukand build and test that17:14
Keybuk;)17:14
pittiKeybuk: I think I'm at the point where I'd just add a workaround for the gtk-doc breakage17:14
pittiliek copying version.xml in debian/rules17:14
Keybuk;)17:16
Keybukthere must be a makefile rule to build it17:17
Keybuktrouble is that it always looks in $(srcdir) for it, never $(builddir)17:17
Keybukotherwise how does it end up in build-deb/ ?17:17
didrocksseb128: hehe :-)17:20
brycegood morning everyone17:22
pittihey bryce17:22
seb128hey bryce17:23
didrockshello bryce17:25
rickspencer3team meeting in four minutes17:26
seb128meeting'o'clock!17:29
rickspencer3https://wiki.ubuntu.com/DesktopTeam/Meeting/2009-06-3017:30
rickspencer3asac: ArneGoetje bryce ccheney awe seb128 pitti Riddell17:30
ArneGoetjehere17:31
* rickspencer3 taps gavel17:31
seb128hello17:31
awehey17:31
asachi17:31
bryceheya17:31
rickspencer3kenvandine:17:31
rickspencer3shall we start? is this a quorum?17:32
pittiken@vandine.org: hey... having irc issues17:32
seb128yes, pitti is around he was writing on some other channel some seconds ago17:32
pittiFYI17:32
rickspencer3heh17:32
rickspencer3ok, let's roll17:33
* rickspencer3 refreshes to check for new agenda items17:33
rickspencer3outstanding items from last meeting17:33
* pitti smuggles in a "GDM" topic17:33
rickspencer3paper cuts: they got 10 fixed last week, seemed to be a success, so great17:34
rickspencer3pitti: np, I'll that to the discussion section17:34
kenvandinesorry folks... technical difficulties :)17:34
rickspencer3awe: did you review the audio spec for TheMuso?17:35
aweyea... i'll send him comments before this evening's meeting17:35
rickspencer3sweet17:35
rickspencer3two announcements:17:35
rickspencer31. if you haven't booked travel for the sprint, please do so today17:36
rickspencer32. a few of us are traveling to Desktop Summit17:36
rickspencer3I'm leaving tomorrow, a few are leaving on Thursday, right?17:36
seb128rickspencer3, "today"? is there any hurry?17:36
rickspencer3like robert_ancell is leaving Thursday17:36
* seb128 still not decided between sucking flight options17:36
seb128I'm travelling on friday for desktop summit17:37
rickspencer3seb128: "today" was probably unnecessarily dramatic, but it does get more expensive for some of us if we wait to long17:37
seb128I'm travelling on friday for desktop summit, landing in the afternoon17:37
seb128rickspencer3, ok17:37
kenvandinerickspencer3, yeah... mine jumped $200 over night while i thought about it..17:37
kenvandinebooked now17:37
rickspencer3kenvandine: is arriving next Tuesday17:37
rickspencer3Riddell: when are you ariving?17:37
kenvandinerickspencer3, arriving monday afternoon17:37
rickspencer3kenvandine: ack, thanks17:38
rickspencer3kenvandine: partner update?17:38
kenvandineyeah17:39
kenvandineso ubuntuone packages are still being worked, dobey did a bit of a re-org to properly manage the packaging feedback he got in revu17:39
kenvandinethat should be updated in revu today, hopefully we can get that reviewed quickly17:40
kenvandinedx team still hasn't communicated their iteration plans yet, but I do know fusa changes will land end of week17:40
kenvandineat least all the basic functionality needed for the new GDM17:40
kenvandinewe need to decide if we want to go ahead and ship it with the new GDM17:40
kenvandineseb128, thoughts?17:40
seb128speaking about dxteam, apparently they wrote a new applet rather than adapting the gdm one?17:41
pittiwhy oh why?17:41
kenvandinei hadn't heard that... i knew it was a big change17:41
kenvandineusing the dbus menus17:41
seb128hum, ted is not around and I guess that's a question for him rather17:41
kenvandinewe can talk to him about that17:42
kenvandinethey did the dbus menus work17:42
kenvandinewhich should be nice17:42
seb128"dbus menu"?17:42
seb128what is that?17:42
kenvandinemight have required enough change to start over17:42
kenvandineso apps can export menus to other apps17:42
artirhttps://launchpad.net/dbusmenu17:42
kenvandineover dbus17:42
rickspencer3is there ambiguity regarding shipping new GDM?17:42
seb128how is that revelent to fuse and gdm update?17:43
=== dpm is now known as dpm-afk
kenvandineseb128, new fusa uses it17:43
seb128this dbusmenu things seems a different topic17:43
pittiI think new gdm is almost ready to go17:43
seb128well that's a technical decision from them not a justification to fork upstream imho17:43
kenvandineso it might have been enough work to just start over... i guess17:43
kenvandinenot sure17:43
kenvandineyeah17:43
kenvandinerickspencer3, i don't think it is a question... it is more "are we ready next week"17:43
kenvandineor right after guadec :)17:44
seb128especially that ted was speaking about using different namespacing for the applet17:44
seb128so requiring another user configuration migration on upgrade17:44
kenvandinesigh17:44
kenvandineok... we need to talk to him17:44
seb128yeah17:44
kenvandinehe didn't mention that part to me :)17:44
seb128otherwise new gdm: help is welcome to fix upgrade issues17:44
seb128and pitti says there is a blocker gpm issue too17:44
kenvandinealso, the ubuntuone karmic integration spec is approved17:45
pittiseb128: well, not really a "blocker" for uploading gdm17:45
seb128upgrade issue being that we can't restart gdm on upgrade because that would close running sessions17:45
kenvandineso we will have more MIRs coming, as the code is written17:45
seb128but the banner is broken until restart17:45
pittiseb128: I meant the weird session saving dialog17:45
seb128pitti, that's not my main concern, the concern is that gdm is not working until reboot17:45
seb128it just displays a banner error17:46
rickspencer3seb128: pitti: can we not live with gdm not working until reboot for the time being, for alpha users?17:46
seb128and clicking ok makes the same error come back17:46
pittirickspencer3: WFM17:46
seb128rickspencer3, yeah we can17:46
kenvandineok, i think that is all i have...17:46
seb128upload is mainly blocked on the fusa update right now17:46
rickspencer3so can we accelerate moving gdm out of the ppa and document the workaround?17:46
rickspencer3ah17:47
seb128without the patched fusa there is no way to reboot or stop your machine since we patch gnome-panel to not list those actions by default17:47
pittiseb128: I don't think we should care about that; can't we just use the upstream fusa for the time being?17:47
rickspencer3so shall kenvandine organize syncronizing those uploads, without blocking on finishing gdm?17:47
pittioh, eww17:47
seb128we could drop that patch meanwhile too if required17:47
pittiseb128: *nod*17:47
kenvandinerickspencer3, i can do that17:48
kenvandineshould we block on migration for fusa?17:48
seb128I'm not very comfortable uploading the new gdm just before traveling17:48
kenvandineor is migration not that important?17:48
rickspencer3ACTION: kenvandine to organize uploading new FUSA applet and new GDM, document workarounds17:48
seb128I can do that next week when coming back from GUADEC17:48
kenvandineseb128, lets do it right after we return17:48
pittiseb128: I'm not going, I can care about that if you wnat me to17:48
pittilike, care for the fallout17:48
kenvandinepitti, that is great :)17:48
pittibut well, next week would suffice17:48
seb128pitti, ok, let's discuss that after meeting and upload tomorrow if we will comfortable17:49
kenvandinefusa changes will land at the end of this week17:49
pitticool17:49
seb128extra people installing the ppa version would be welcome17:49
seb128just to confirm it somewhat works for several users17:49
rickspencer3who volunteers?17:49
seb128it's in the ubuntu-desktop ppa17:49
hggdhwill do17:49
rickspencer3to  try the gdm in the ppa?17:49
rickspencer3o/17:49
pittirunning for several days, no probs except http://bugzilla.gnome.org/show_bug.cgi?id=58522817:49
ubottuGnome bug 585228 in gnome-power-manager "immediately suspends on startup when lid is closed" [Major,Unconfirmed]17:49
rickspencer3not too many volunteers :)17:50
seb128ok good, I think we have everything we need there17:50
pedro_I'll help with that as well17:50
rickspencer3kenvandine: are you running new gdm?17:50
kenvandinenot anymore17:50
kenvandinei had a VM with it17:50
kenvandinebut it got whacked17:50
Riddellrickspencer3: I'm arriving tomorrow evening17:50
artirseb128: tried it too in virtualbox, it works17:50
kenvandinei can get it going again17:50
rickspencer3ok, three of us should suffice though17:50
seb128yeah, we will do with what we have17:50
jcastroshould I do a call for testin the new GDM?17:51
kenvandinejcastro, not really great timing...17:51
seb128jcastro, I think the some people volunteering here will be enough17:51
kenvandinesince we are all leaving :)17:51
rickspencer3ACTION: hggdh, rickspencer3, pedro_ to install new gdm from ubuntu-desktop ppa, report serious problems to seb128 and/or kenvandine17:51
jcastrook17:51
seb128but thanks17:51
rickspencer3jcastro: but you could try it yourself17:51
rickspencer3kenvandine: was that the whole partner update?17:52
kenvandinerickspencer3, yup, the acceptance tests haven't changed17:52
kenvandinewell, updated... no new info :)17:52
rickspencer3hmm17:52
rickspencer3ok17:52
kenvandinewhat did i miss?17:52
rickspencer3thanks kenvandine17:52
kenvandineok :)17:52
rickspencer3Riddell: Kubuntu update?17:52
RiddellKubuntu: KDE 4.3 RC 1 is in progress and will start uploading tonight17:53
RiddellArora is now the default browser (pre-empting big discussion just started by suse on the topic)17:53
RiddellKubuntu Tutorials Day was a big success, see logs https://wiki.kubuntu.org/KubuntuTutorialsDay17:53
RiddellNew council members vote is now under way17:53
Riddellis all17:54
rickspencer3Riddell: how is the netbook version going?17:54
* rickspencer3 wants to try17:54
Riddellscott created the seeds, it's waiting on the changes to the image building scripts to get merged in for images17:54
rickspencer3sweet!17:54
Riddelland also on a settings package, currently it won't actually do anything different17:54
rickspencer3oh?17:55
Riddelltonio is working on that17:55
asacRiddell: can we remove konqueror now? or do you still need it installed?17:55
Riddellasac: it's still needed, it'll still be on the CDs for this release at least17:55
Riddellbaby steps17:55
asacRiddell: so you have now two browsers by default17:56
asacwhats up there?17:56
asaci know that there is something difficult ongoing, but two browsers by default sounds really odd.17:56
Riddellwell politics and fanboys, removing Konqueror will get us flamed by various people (we have two file managers anyway)17:56
Tm_TKonqueror is not something one can remove without flaming17:57
Tm_Tnor without issues in overall17:57
rickspencer3but having two applications that do the same thing because of fan boys doesn't sound very user-centric17:57
asachow does the user experience look like? what will be used by default if you click on a http link?17:57
asachow can the user switch the default17:57
seb128why can't use who want to use it install it from universe or something?17:58
Riddellarora currently, there's a System Settings module for default apps17:58
Tm_Tasac: it's all in the systemsettings, clearly labeled17:58
asacRiddell: cant that be done in a way that installs konqueror on demand?17:58
asace.g. when user select "konqueror" as default browser, it gets automatically installed17:58
asaclike codecs etc.?17:58
Riddellit could.. but this is controvertial enough without upsetting more people17:59
seb128maybe we should install empathy and pidgin by default in ubuntu ;-)18:00
asacok... but to understand, you only have one "webbrowser" menu entry in "applications" (if something like that exists on kde) ... and userr configures what that means in system settings?18:00
Riddellasac: right18:00
asacor are there both browser in the menu?18:00
seb128(to avoid people complaining about us switching)18:00
rickspencer3ok, this sounds like a good discussion for #kubuntu-devel18:00
asacRiddell: do both at least us the same webkit lib?18:01
Riddellasac: no, that's the main problem with konqueror18:01
asac(to not duplicate seucitry=18:01
Riddellbut we can't get rid of khtml, it's part of kdelibs18:01
asacok. maybe we can review this later this cycle ;)18:02
asacmoving on?18:03
rickspencer3ACTION: ALL - provide feedback and help regarding Kubuntu browsers to Riddel in #kubuntu-devel18:03
rickspencer3thanks Riddell18:03
rickspencer3bryce: quick x update?18:03
brycesire18:04
bryceer sure18:04
bryce * Merge Status:18:04
bryce   + Mostly waiting on upstream releases at this point.18:04
bryce   + 12 packages need merge/sync, out of 92 updates since Jaunty18:04
bryce   + 7 packages have upstream releases but not yet in Debian18:04
bryce   + -fglrx and -nvidia completed PPA testing.  Now in Ubuntu.18:04
bryce   + mesa, xorg merges completed git staging.  Now in Ubuntu18:04
bryce   + A new xserver RC is available.  Will be merged soonish.18:04
bryce   + git snapshots of -ati/KMS, & -nouveau/KMS are in PPAs18:04
* rickspencer3 in awe of bryce's typing speed18:04
brycetjaalton just did the mesa and xorg uploads a few minutes ago, so y'all will be getting those soon18:05
bryce * X.org in Karmic is working well18:05
bryce   + 2069 total open X bugs, down 38 since last week18:05
bryce   + KMS on -intel is now on by default; relatively few bugs are being18:05
bryce     reported about it.18:05
rickspencer3great news about KMS18:05
pittiI just fixed hal to not conflict with new xorg, so please don't complain :)18:05
asacis the "lock up on screen powersave" bug fixed for i965?18:05
brycethis past week I've been arm deep in bugs, and things "feel" fairly stable.  At the moment -nvidia feels the buggiest of our drivers, but that's nothing new18:06
bryceasac, bug#?18:06
bryceasac, generally we've been keeping the launchpad bug states for -intel really well up to date lately, so the lp bug status on that is probably accurate18:06
asacbryce: mdz had the same bug i think18:07
asacso i didnt file one18:07
kenvandinei thought mdz filed it18:07
asacyes he filed18:07
kenvandinei have the same problem18:07
asacthats why i didnt ;)18:07
kenvandineme too :)18:07
brycewell, we can talk more on specific bugs off-meeting, but in general it appears this latest -intel is doing quite well18:07
kenvandineok18:08
pittibryce: wrt, xorg-edgers, do you want to continue keeping it at the current pace? if so, shouldn't we just upload new versions to karmic directly, to get more testing?18:08
rickspencer3that's great news18:08
brycepoor mdz ;-)18:08
asacbryce: doing quite well? it locks up my laptop if i dont type for a few minutes ;)18:08
asacjust kiddig18:08
seb128bug #38835718:08
ubottuLaunchpad bug 388357 in xserver-xorg-video-intel "[i965] X freeze on karmic after resume from full screen application: i915_gem_retire_work_handler() / finish_task_switch()" [Unknown,Confirmed] https://launchpad.net/bugs/38835718:08
seb128I think that's this one18:08
kenvandineasac, we just have to work faster :)18:08
rickspencer3asac: that was unkind ;)18:08
pitti-intel still freezes a lot for me after suspends, and DPMS off, and dpms off seems to kill it completely, but I'll follow up with that with upstream18:08
brycepitti, yes - in fact that's what we've been doing.  We've uploaded several things from xorg-edgers the past couple weeks18:09
asacpitti: if i suspend and close the lid quickly it freezes because its the powersave thing going on18:09
asacif i wait until its suspended -> no problem18:09
rickspencer3this seems like much better shape than even the end of Jaunty, where we had hard to reproduce freezing bugs during normal use18:09
bryceasac, ah yes; that one is reported upstream and has high priority for a fix, so I'm waiting for a patch from upstream as the next step18:09
asacok ... /me keeps powersave disabled then18:10
rickspencer3thanks for the update bryce18:10
bryceasac, they asked for newer debugging tools, which I packaged, although doesn't appear mdz has run them, so if anyone is interested in pushing that bug forward, that's something you could work on18:10
brycebut we can talk post-meeting on bugs18:10
asack18:10
rickspencer3also, you all should see the bug report for -intel graphics that bryce is producing ... it gives quite a good overview of the current bug situation18:11
brycerickspencer3, should I post those reports to a public location?18:11
rickspencer3bryce: wouldn't hurt, i suppose18:11
brycemaybe I'll turn it into a web page; it's getting kind of unwieldy as it is18:12
* rickspencer3 nods18:12
rickspencer3put it on a cron job, and set an auto email to Yingying18:12
brycehehe18:12
brycewell I like to do some housecleaning before sending it out.  ;-)18:12
rickspencer3perhaps some people would be interested in seeing the tools that you use to create such reports18:12
bryceanyway, that's it for X18:13
brycesure18:13
rickspencer3thanks bryce18:13
rickspencer3ArneGoetje: translations update?18:13
ArneGoetje * Message sharing in Rosetta is done, translations in Jaunty and Karmic are shared now.18:13
ArneGoetje * Imports have started for Karmic.18:13
ArneGoetje * Contacted Kubuntu developers and asked them to review the current Kubuntu related translation templates in Rosetta. Based on their feedback, the Ubuntu Translation Coordinators team needs to approve new templates, disable obsolete ones and rename templates that have been moved.18:13
ArneGoetje * After the first round of imports is done, and Kubuntu translations are in reasonable shape we will generate initial language-packs for Karmic (hopefully next week).18:13
ArneGoetje[done]18:14
rickspencer3ArneGoetje: in general are we ahead of the curve or behind the curve in terms of translations compared to previous releases?18:14
ArneGoetjeI think behind what was planned, due to message sharing development going on. But still not too late.18:15
rickspencer3ok18:15
rickspencer3thanks for the update ArneGoetje18:15
ArneGoetjenp18:15
rickspencer3pitti: GDM?18:15
pittialready covered18:16
pittiwas about when to upload the new one18:16
rickspencer3ok18:16
pittiI like to see that land RSN, so that DX team/themes etc. can be developed18:16
kenvandinepitti, i just saw a snag... dbusmenu will need to get uploaded too... new package18:16
kenvandineREVU, MIR, etc18:16
pittiRiddell: any progress on bug 339313?18:16
pittithis seems to be stuck somehow18:16
ubottuLaunchpad bug 339313 in ubuntu-release-notes "Kubuntu Jaunty: Cannot Connect To Wireless Network with WEP shared key" [Undecided,Fix released] https://launchpad.net/bugs/33931318:16
Riddellpitti: well the new plasmoid is in so it's working as best as it can18:17
RiddellI can ask at GCDS when is a good time to take a new snapshot and do another update18:17
pittiRiddell: is that the "ppa package which works better" you referred to?18:17
pittii. e. is that fixed now?18:17
Riddellyes18:17
pitticool18:17
Riddellso it works now for far more people, but still some situations where it doesn't seem to18:18
rickspencer3moving on18:19
rickspencer3looks like the burndown chart is working, please don't forget to change the status of items when they are done18:19
rickspencer3I think I may tweak it to add a "prediction line"18:19
rickspencer3next is a discussion topic: PPAs versus archives18:20
asac___(/me back ... IRC gateway failed)18:20
rickspencer3I have two, possibly invalid, concerns:18:20
rickspencer31. It seems that moving some things from PPAs to universe has taken longer than predicted for some components ... making me concerned that we will find ourselves very behind if we wait too long18:21
seb128urg, wrong click18:21
rickspencer32. It seems that with PPAs, we are all running and testing a different desktop, which seems suboptimal from a testing POV, but also means that things may appear "done" when they are in PPAs, which may be premature18:22
rickspencer3so my question is ...18:22
seb128(what was 1?)18:22
rickspencer3(10:21:16 AM) rickspencer3: 1. It seems that moving some things from PPAs to universe has taken longer than predicted for some components ... making me concerned that we will find ourselves very behind if we wait too long18:22
seb128thanks18:22
rickspencer3so my question is ....18:22
asac___i agree that we should do most stuff directly in archive18:22
rickspencer3is there product in PPAs now that should be in archives?18:22
rickspencer3thoughts?18:23
asac___with a few exceptions: transitions that will cause unnecessary breakage on developers desktops18:23
seb128dunno if there is things in ppa to move right now18:23
seb128but I've discussed recently the xorg edger ppa with pitti and I feel it's suboptimal too18:23
rickspencer3I know about GDM, FFA 3.5, and xorg-edgers18:23
seb128I'm rather in favor of snapshoting versions directly to karmic if they are candidate to land there anyway18:23
pittiwell, there's two cases18:24
rickspencer3I know that FF3.5 won't be ready for the archives until alpha 418:24
asac___yeah. ffox 3.5 (the app) itself is in archive ... its just that i do the first transition steps in ppa to provide karmic users with a more or less smooth transition18:24
pittistuff like the new U1 packages need to stay in PPAs until they are ready for upload and reviewed in REVU18:24
rickspencer3asac: ok, great18:24
* rickspencer3 directs my last comment to all three asacs18:24
bryceerf, the whole reason for doing the ppa's was due to complaints about stuff going directly into the archive without suitable testing18:24
pittifor newer versions like X.org or ffox, I agree that direct karmic uploads would be better18:24
* rickspencer3 now knows hos asac gets so much done18:24
seb128bryce, I don't think we should aim at having unstable stable18:25
brycepitti, why is this?18:25
seb128it just slow us down18:25
pittibryce: well, it doesn't particularly matter whether the version I revert to came from a PPA or from karmic?18:25
bryceseb128, how does it slow you down?18:25
seb128it diverts testing efforts18:25
pitti(in case it breaks)18:25
seb128you get bugs about different versions18:25
seb128you have to fix issues in 2 places when there is new changes required18:25
rickspencer3I think xorg was a special case for Karmic, in a way, as there was some sensitivity regarding intel after Jaunty18:26
brycehmm, I really don't agree, I don't see the problems you guys are describing18:26
seb128you don't see users reporting bugs about different versions?18:26
seb128and me and pitti not running the same versions and not having the same issues?18:26
bryceit is little extra effort fixing things in both places, and it saves being endlessly pinged on IRC by people having problems with the newest stuff18:26
bryceseb128, no I'm saying it's not a huge concern to me that people are reporting bugs about different versions18:27
rickspencer3also, when x breaks, it becomes rather pressing for the user, even if they are a developer, and this impacts bryce quite abit18:27
seb128people not ready for running unstable versions should stay on jaunty18:27
brycealready I get people reporting bugs with a lot of different versions, aside from PPA18:27
seb128rickspencer3, you could say the same for glib, gtk, firefox, evolution, etc18:27
seb128linux18:28
seb128libc18:28
asac___seb128: we do that18:28
asac___we have -daily ppas18:28
bryceseb128, I disagree18:28
rickspencer3seb128: could be, I don't know ... but I know that bryce spends a huge amount of time helping people troubleshoot x18:28
asac___also we do staging for -security updates ... and now the ffox 35 transition18:28
bryceseb128, there are many people who want to run karmic to be able to test some classes of software, but who do not like it when the whole system breaks from under them18:28
rickspencer3bryce: when are you planning to move all the karmic stuff into karmic archives?18:28
bryceothers like having the system break from under them... so they install edgers and work with us on bugs18:29
seb128so we should have ppa for pulseaudio too to not break sound, and for linux to not break whatever etc etc etc18:29
seb128well, so we are back to my question from the other day, is edger meant to be candidate versions for karmic or crack of the day?18:29
pittibryce: so xorg-edgers is essentially autobuilt and not tested?18:29
seb128some people told me to test upgrades there because those are candidate for karmic18:30
pittibryce: so perhaps a compromise would be to just upload snapshots more often then?18:30
seb128I'm fine with having crack of the days ppa for hackers18:30
brycerickspencer3, general rule is as upstream puts out their final releases we merge into ubuntu, and just keep rolling the git snapshots18:30
rickspencer3bryce: it seems that perhaps edgers has served it's purpose for Karmic, and it's time to start focusing on the archives18:31
brycepitti, xorg-edgers is *where* the testing is done.  but yeah, stuff is not expected to be tested before it's uploaded there18:31
pittiso we are still all encouraged to have it enabled?18:32
brycerickspencer3, but that's exactly what's going on...  this week we uploaded -fglrx, -nvidia, xorg, and mesa.  xserver is coming soon too18:32
rickspencer3bryce: ok18:32
seb128so I'm running karmic but I'm not testing what is useful and that bothers me somewhat18:32
pittiI guess for the full fun we also need to use the daily kernel images then, to get i915 updates18:32
brycerickspencer3, we still need xorg-edgers to make it easy for people to test upstream for bug debugging purposes, which will enable us to cherrypick fixes18:33
rickspencer3I think that X was actually handled quite well given the Jaunty issues ... and I didn't mean for this to overly focus on bryce's work18:33
rickspencer3so perhaps bryce, pitti, and seb128 can discuss a mutually satisfactory course of action ... but18:33
rickspencer3are there *other* PPAs that we should be thinking of as well?18:33
pittiI'm mainly interested in when I should stop using xorg-edgers18:33
seb128not that I know about18:33
brycepitti, alpha-318:34
pittiI'd like to test as early as possible what will go into karmic18:34
pittibryce: ah, thanks18:34
seb128I'm mainly interest to know why I should be adding ppas to my sources.list to be testing karmic18:34
seb128but right that's a out of meeting discussion18:34
brycealpha-3 is where we're going to shift focus over more to stabilization, and most all the key X bits will be in place by then18:34
pittibryce: I hope we'll also get .31 by then18:34
pittithat should help (or break :) ) a lot18:35
bryceyeah that's the other thing... a lot of the X stuff has kernel dependencies now with KMS, that's easier and safer to deal with in a PPA18:35
rickspencer3ok18:36
pittibryce: My fingers are itching to DKMSify i915 for git head testing :)18:36
pittibut I guess we could just as well use the kernel PPA18:36
rickspencer3I think we ran a tad past the meeting time18:36
rickspencer3are there action items to take out of the PPA/archive discussion?18:37
seb128I would say "no" looking at the discussion18:37
asac___essence for meseems to be that main testing should be done in real archive and if you ask all desktop team members to enable a PPA you probably do something wrong ;)18:37
pittifor me, it was "keep xorg-edgers until alpha-3 and disable it afterwards"18:37
seb128asac____ ++18:38
seb128I think there is something wrong if people using karmic are not testing karmic ....18:38
asac___ppas make sense for me for voluntarily staging and to prepare bits that you dont want to get tested by all ;)18:38
seb128ie what is the point to run the unstable version if your feedback is about outdated versions anyway18:38
rickspencer3but so far as I can tell, with a few exceptions that is what has been happening18:38
asac___(and for non-motus for getting things reviewed)18:38
pittiI thought that was precisely what xorg-edgers is?18:38
pitti(not recommended to all karmic users)?18:38
pittiasac___: for review it's fine, *nod* (although REVU is better)18:39
pittilike, the U1 packages18:39
asac___pitti: yes. lets phrase different: ppa is good if you want to provide packages to users while its undergooing review in revu18:40
asac___;)18:40
rickspencer3ACTION: All: run edgers until alpha 3, and then disable18:41
rickspencer3any other business?18:41
asac_yes. anyone running jaunty or any other stable release?18:41
rickspencer3asac_: I'm running Jaunty as we speak18:42
asac_if so, please enable the https://edge.launchpad.net/~ubuntu-mozilla-security/+archive/ppa ... i always need more testers for our security bits18:42
* rickspencer3 clicks18:42
asac_only bits that would go out to end users usually go there ... so its safe18:42
* awe clicks18:42
pittijaunty? wasn't that an Ubuntu release we did a million years ago? :-)18:42
asac_if you update daily and report in case suddenly firefox brakes, let me know quickly18:42
asac_otherwise no need to confirm or anything18:43
brycepitti, I've excised it from my brain already18:43
asac_thanks!18:43
pittithanks all18:43
brycethanks18:43
rickspencer3ACTION: ALL install mozilla security update, report problems to asac18:43
rickspencer3bye all!18:43
rickspencer3thanks18:43
=== asac____ is now known as asac
* rickspencer3 taps gavel18:43
asac_thanks18:43
asac_everybody going to desktop summit: enjoy your trip!18:43
seb128thanks18:43
awesee ya18:44
pittihave fun, guys!18:44
seb128need to reboot my laptop brb18:44
ArneGoetjethanks18:44
pittidinner o'clock, will come back later to unbreak apport retracers18:44
seb128re18:46
seb128bryce, pitti: I've nothing against having edger ppas, the things if that we start having a gtk-edger, devicekit-edger, xorg-edger, etc everybody will have a different mix of versions and nobody test karmic proper, ie what we ship to our users18:47
seb128and sometime issues come from a specific versions combination and you don't notice you break karmic because you are running some edger version not having the issue18:48
bryceseb128, I don't think you understand how fragile X can be sometimes, and how badly it can break from just updating a driver to a git snapshot18:50
bryceand when it does break, I get people coming out of the woodwork bugging me about the problem... it gets overwhelming very quickly18:51
seb128hum, not sure how I should take that18:51
seb128you think I don't understand what sort of breakages we can have and the implications?18:51
seb128I didn't say to upload random git crack to karmic18:51
brycefrom my perspective doing the extremely unstable stuff in PPAs helps, since only those who are good at reporting problems test it, and can give good feedback (and shut it off if the issues are too bad)18:51
brycexorg-edgers == random git crack18:52
seb128well I don't get why I'm being asked to run xorg-edger until alpha3 then18:52
seb128I don't want to run git crack, I want to give feedback on karmic18:52
seb128I'm fine with ppa having crack of the day as firefox has18:53
seb128and usually we ask users to try thing there to confirm a specific bug has been fixed18:53
seb128but I don't think we should encourage all the team members to run edger18:53
bryceseb128, I'd agree18:55
seb128bryce, ok, good, I think we have the same opinion18:56
seb128I just had the impression that we were encouraged to all run edger18:56
bryceI was surprised to see rickspencer3 set it as a task for everyone; I would rather that people only run xorg-edgers if they are okay with spending the time to report bugs and deal with issues that might crop up18:56
seb128it might just be me who misunderstood though18:56
rickspencer3I can remove that for sure18:56
rickspencer3I guess it should be for people who want to18:56
seb128but pitti has been advertising it too18:56
brycerickspencer3, thanks yes18:56
rickspencer3seb128: no the action item said All18:56
rickspencer3but it should have said "consider running" or "if you are running", etc...18:57
seb128as said before I think edger ppa should be for people interested by debugging crack of the day for the said component18:57
seb128ie I would not recommend everybody to run daily gtk snapshots there, most people don't care about doing the upstream job for gtk18:57
seb128anyway seems we are on agreement on that, only people interested run edger versions and all is fine ... time for diner ;-)18:58
bryceviolent agreement again apparently ;-)18:59
mclasen_seb128: running daily gtk snapshots is entirely harmless...19:00
mclasen_compared to X19:01
bryceif some of this is coming from the emails I sent out last week to test fglrx and nvidia, both of which were being staged in xorg-edgers at the time, note that both got uploaded to karmic the next day, once we had a few positive test cases.  And the -intel I asked people to test already was in karmic.19:04
brycethe main reason I asked fglrx and nvidia users to test xorg-edgers was since a lot of them were on jaunty, and there really isn't a way to give them newer drivers aside from ppas19:05
rickspencer3seb128: kenvandine: I presume that FUSA will be broken now that I am on gdm-new?19:13
* rickspencer3 logs out19:14
kenvandineyes19:14
dobeyhrmm, i think i might need some help with the ubuntuone-client packaging19:17
dobeyand pitti is probably gone for the day19:17
kalon33kenvandine, about new gdm, do you have an idea of when fusa will be patched to correct it's broken state ? Or will gnome-panel be unpatched to provide logout facilities until then ?19:19
kenvandinekalon33, end of the week19:20
kenvandinewell the code will be ready19:20
kenvandineprobably updated to karmic next week19:20
kenvandinerickspencer3, but you should be using gdm not gdm-new19:20
kalon33kenvandine, so new GDM will land at the same time in karmic or the fix will be in desktop-team PPA ?19:21
kenvandinesame time19:21
kenvandinethe goal is to land them both in karmic together19:21
kalon33without a transition period (for instance between the moment when the code will be ready and the next week) ?19:23
kalon33in a ppa ?19:23
kenvandineundetermined as of now19:25
kalon33kenvandine, thanks for your answers, will test new GDM now, as I can switch off manually ;)19:26
kenvandinecool19:27
kenvandinethx19:27
dobeykenvandine: are you knowledgeable enough to help me with the packaging? :)19:28
kenvandineshould be19:28
kenvandinewhat do you need?19:28
dobeydealing with http://revu.ubuntuwire.com/p/ubuntuone-client19:28
dobeytrying to figure out hwo to do the split exactly19:29
* kenvandine looks19:29
kalon33kenvandine, you're welcome, I know testing is quite important, and as I have the sufficient knowledge... have a nice evening :)19:30
kenvandinedobey, so where are the package sources?19:30
dobeykenvandine: the tarball?19:30
kenvandineno, the packaging19:31
dobeykenvandine: lp:~dobey/ubuntu/karmic/ubuntuone-client/karmic19:35
kenvandinethx19:35
seb128re19:37
seb128mclasen_, yeah maybe gtk was not a good example, I was just picking a library used by quite some application, ie if gtk has a crasher commit quite some users would notice19:38
dobeykenvandine: mostly, i'm not sure where some separation should be, as most all of the code depends on gnomekeyring python bindings, whicn unfortunately pulls in most of gnome due to the way it's packaged19:44
kenvandinewell for the "not depending on gnome" case that is hard... but we can surely split out the python stuff into python-ubuntuone-client19:45
kenvandinethe python library that is19:45
kenvandinedobey, give me a few19:46
dobeykenvandine: right, though i'm not entirely sure what belongs there either, since ubuntuone.u1sync is just for u1sync to use (which I think should be a separate package), and the syncdaemon stuff is almost entirely just code only the syncdaemon itself should be using19:47
dobeyie, a python-ubuntuone-client doesn't really make sense to me19:48
kenvandinehang on... my box is hanging here.. it does that when writing a usb image19:49
dobeyheh19:49
hggdhseb128, I will email you a sample of the evolution apport hook working (it will have real data)20:40
seb128hggdh, can't you have a simple testsuite example, ie the function called on an IP and comparing the result to a known result?20:41
hggdhseb128, yes, will do, then20:42
seb128thanks20:42
seb128walters, hey20:44
seb128walters, I'm having a look to the gobject-introspection 0.6.1 to 0.6.3 update20:44
seb128walters, there is a new libgirepository-everything-1.0.so, do you recommend splitting that as a new library?20:45
seb128I'm not sure what it's used for exactly20:45
pittidobey: I'm back for some minutes20:52
dobeypitti: hey, kenvandine is helping me20:53
pittiah, great20:53
dobeypitti: you might be able better answer my conffiles question though20:53
dobeypitti: does debhelper just automatically make anything in /etc a conffile now or something?20:54
pittidobey: it has done that forever already20:54
seb128not now that has always been the case20:54
pittiusually you never need to write a debian/conffiles20:54
dobeyeww20:54
dobeyso it makes /etc/xdg/autostart files be conffiles?20:54
seb128yes20:55
pittiright20:55
dobey:(20:55
pittidobey: do they need to be? can't we ship them in /usr/share?20:55
seb128cf xdg and d-d-l emails from Josselin about using usr20:55
dobeyseb128: yes, that's only ONE example though20:55
pitti/usr/share/gnome/autostart/ has some stuff20:55
seb128we shipped those in etc for a reason, to let sysadmin change those easily to not start20:55
dobeybut /usr/share/gnome/autostart is wrong (it's not an xdg place)20:55
pittignome-session-splash, libcanberra-login, and polkit-gnome-auth use it20:56
pittibut *shrug*, I don't particularly care20:56
dobeybut regardless, there's lots of stuff in /etc/ which shouldn't be considered conf files20:56
pittiI usually use whatever upstream does20:56
seb128gnome-session read files in both locations20:56
pittidobey: *nod*20:56
dobeyyes, gnome-session does i'm sure20:56
dobeybut i don't want to argue about the location of autostart files. i was just making an example20:57
seb128what is the issue?20:58
waltersseb128: well i'm unhappy about its existence =/  but basically i'd just ship it with the main package21:00
waltersseb128: it's a library of test functions that bindings can use, basically BuildRequiresTests if you know what i mean21:00
seb128I don't know about BuildRequiresTests but I'm fine shipping that in gobject-introspection21:01
seb128thanks21:01
seb128walters, btw do you follow gnome-shell too?21:02
waltersseb128: yeah21:02
waltersseb128: the main thing to do for that is get introspection support in gtk and pango, and then we don't need to depend on gir-repository21:03
seb128walters, apparently Clutter-0.9.gir is required to build mutter, do you know where than can be find, current gir-repository use 0.821:03
waltersseb128: clutter needs to be built with introspection for 0.921:03
waltersthat's where we're tryign to get to, where the libraries themselves build introspection data21:04
seb128so the gir is in clutter proper and not gir-repository?21:04
waltersyeah21:04
waltersgir-repository is the old way, it's like a dependency inversion black hole21:04
seb128yeah, that makes sense, we had discussion about that at UDS21:04
didrocksFYI, I have a similar discussion with owen on #gnome-shell right now :)21:05
seb128I will join #gnome-shell I think21:05
* hyperair yawns. nautilus-share porting to gtkbuilder complete =D21:13
seb128hyperair, good job!21:20
hyperairseb128: thanks =)21:20
hyperairit would have been completed faster if gtkbuilder didn't insist on creating the dummy parent window when the ui is loaded21:21
hyperairoh well21:21
seb128asac: do you plan to move libmozjs to a system path this cycle?21:21
seb128_re21:26
seb128_dsl disconnected21:26
seb128_I was saying21:26
seb128_asac: do you plan to move libmozjs to a system path this cycle?21:26
seb128_hyperair, what did you do about the weird script to do changes in the .glade?21:26
seb128_ I had a quick look yesterday and that + all the debian patche stopped me and I decided to work on nautilus-sendto rather21:26
seb128_ walters, btw do you have an opinion about gjs packaging too? ;-)21:26
seb128_ walters, would you split libgjs.so and libgjs-gi.so in proper libraries? and where should go /usr/lib/gjs-1.0/*.so if we do things this way?21:26
seb128_ lool, pitti, can you bump the gdm build score?21:26
hyperairseb128_: unhooked it from the build system.21:27
pittiseb128_, lool: doing21:27
seb128_hyperair, ok makes sense I think21:27
hyperairseb128_: it's not needed since the introductino of the system icon patch21:27
hyperairseb128_: the fix.pl was meant to mangle the pathnames of the custom icons. i tossed those away, heheh =p21:27
hyperairfolder-remote looks very much better than those ugly icons it shipped with21:27
seb128_pitti, thanks, the xorg managed to break gdm and didn't notice until people start complaining so having it fixed quickly would be appreciated ;-)21:27
pittiseb128_: done, but still clogged21:27
pittiright, I saw21:27
pittieww, doesn't help21:28
pittihttps://edge.launchpad.net/builders21:28
seb128_xorg +guys21:28
pittithey are all down21:28
seb128_great21:28
seb128_why do that always happen when you need a quick build?21:28
pittisee #u-devel21:29
seb128_thanks21:30
pittiseb128_: does that affect gdm-new as well?21:31
seb128_pitti, I didn't check yet but I doubt it21:32
pitticool21:32
pittiok, seems my patch to unbreak apport retracers works21:33
seb128_pitti, in fact new gdm has the issue too ...21:34
seb128_pitti, basically easy to fix, just change the xserver path in gdm.conf to /usr/bin/X21:34
seb128_pitti, it's still /usr/X11R6/bin/X21:34
pittijust to know what to do when I boot my machine tomorrow morning :)21:35
=== seb128_ is now known as seb128
=== seb128 is now known as seb128_
chrisccoulsonseb128_ - i just noticed that bug 282403 still has an open intrepid task whilst going through some of my work for my MOTU application. i think it should be closed as WONTFIX for intrepid. do you agree?21:42
ubottuLaunchpad bug 282403 in fast-user-switch-applet "Cannot shutdown or restart when more than one user is logged in" [Medium,Fix released] https://launchpad.net/bugs/28240321:42
seb128_chrisccoulson, seems correct21:42
chrisccoulsonthanks, i'll close that one21:42
=== seb128_ is now known as seb128
* hyperair wonders where bdefreese disappeared to =\21:50
pittiseb128: ah, is that StandardXServer=/usr/X11R6/bin/X ?22:16
seb128pitti, yes22:16
* pitti locally changes to /usr/bin/X22:16
pittimerci22:17
seb128de rien!22:17
pittiseb128: so, I hope the retracers will survive a bit22:17
seb128pitti, they are running now?22:17
seb128I've been too busy to look at those recently22:17
seb128or too lazy ;-)22:18
pittiseb128: the i386 survived for about 10 retracers22:18
pittiI'm currently rolling out the new versions from apport-retracer PPA22:18
seb128good start22:18
pittithen I'll restart22:18
loolseb128: I can't bump build scores I'm afraid22:18
pittiseb128: it just stoppped because the chroot changed underneath it, not because of an actual bug22:18
seb128lool, ok, I was not sure if you were buildd admin22:19
* pitti sees seb128's new gdm upload and cranks up build score22:19
seb128pitti, danke22:20
seb128lool, the buildds didn't like your debian workaround, ie the xserver-xorg build-depends22:20
pittiseb128: 0ubuntu4 put down to 0 again, so that they don't build in vain22:21
pittibut now we can just twiddle thumbs until the security builds finish22:21
seb128pitti, thanks22:21
pittiI'm sure it's openoffice and linux22:21
seb128pitti, linux only according to what kees said22:22
seb128;-)22:22
pittiseb128: guess what builds it first -- armel and lpia..22:24
pittigo mobile!22:24
kalon33;)22:25
seb128pitti, yeah, armel is where I read the ftfbs error before22:25
=== kalon33_ is now known as kalon33
seb128pitti, and the winner is, lpia!22:29
kalon33;)22:29
seb128"X server : /usr/bin/X"22:29
seb128good, it worked22:29
pitti\o/22:29
pittiseb128: yeah, it usually is22:29
pittilpia is blazingly fast for some reason22:29
pitti$ rm */lock22:29
pittithere, retracers should be alive again22:29
* pitti knocks on wood22:30
seb128rock on22:30
loolWow it was months if not years I touched this22:30
kalon33seb128, Sorry, I didn't checked yet, is this bug occurs with new GDM (from desktop-team PPA) ?22:30
seb128lool, well, ubuntu just got the xserver change which dropped the X11R6 compatibility thing22:31
pittikalon33: yes, same problem22:31
seb128lool, and they didn't test if gdm was broken before uploading ...22:31
pittikalon33: just edit /etc/gdm/gdm.conf and fix the path22:31
loolEh22:31
pittikalon33: StandardXServer=/usr/bin/X22:31
seb128or wait for the update22:32
seb128I updated both karmic and ppa22:32
loolI should have implemented that autoconf option, but it was old gdm and I knew it wouldn't go upstream; I guess this stayed for new gdm22:32
seb128lool, right, I used the easy way I changed the fallback case in the configure22:32
kalon33thanks both pitti and seb128 ;)22:33
seb128lool, ie it fallback to /usr/bin/X now22:33
seb128hum, bug #10495722:35
ubottuLaunchpad bug 104957 in gdm "users with no password can't log in with gdm" [Undecided,Incomplete] https://launchpad.net/bugs/10495722:35
loolOh funny I tried that today22:36
pittifeature!22:36
loolI ran passwd -d on an user and I could login on a tty but not on gdm22:37
seb128http://launchpadlibrarian.net/28548736/gdm_2.20.10-0ubuntu4.debdiff22:37
loolI saw that the PAM setup is different, I checked securetty, but didn't know how to set it up22:37
seb128the user suggests adding a nopassword group to the system for that22:37
loolEek22:37
seb128I'm waiting for pitti or $security to comment22:37
pittiwell, frankly, it should just work22:38
pittiyou can log into ttys, etc.22:38
pittipasswd and user-setup should just plainly refuse to have no password22:38
pittibecause that is a nightmare22:38
pittiautologin is okay22:38
pittibut open accounts, possibly on computers with ssh enabled, are a pain22:38
seb128that probably still doesn't solve the gnome-keyring issue either22:40
loolI think the tty needs to be in securetty22:41
loolAnd gdm is probably using an odd tty22:42
loolPerhaps redirecting stdin/stdout for instance22:42
dobeyyay22:46
dobeyi hope i don't have to make any more changes to the packaging for a while22:46
pittidobey: reviewing storage-protocol ATM22:54
pittithanks for fixing22:54
pittidobey: uploaded22:58
pittidobey: waiting for the -client now22:58
pittisleep o'clock, see you tomorrow!22:58
pittikenvandine: ^ FYI22:58
kalon33pitti, good night23:02
chrisccoulsonhmmmm, "what I like least in Ubuntu"23:16
chrisccoulsonnot sure how to answer that :-/23:16
seb128chrisccoulson, ignore it?23:25
chrisccoulsoni was just thinking that23:25
chrisccoulsonthats the only thing i've got left to answer now ;)23:25
seb128not bad23:26
seb128enough work there, night everybody23:27
chrisccoulsongood night23:27
=== jono_ is now known as jono

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