stgraber | anyone desktopy around who would be kind enough to fix indicator-power to stop bringing all of click, click-apparmor, ... on all Ubuntu desktop installs? | 01:41 |
---|---|---|
stgraber | (that's before I just go and revert the package by hand breaking the daily release stuff in the process) | 01:42 |
stgraber | I'll upload the revert in 15min. | 01:47 |
cyphermox | stgraber: still around? | 02:09 |
cyphermox | mountall: mount /sys/fs/pstore [338] terminated with status 32 | 02:09 |
cyphermox | mountall: Filesystem could not be mounted: /sys/fs/pstore | 02:09 |
cyphermox | do you know what this is? ^^^ | 02:09 |
cyphermox | stgraber: please hold off if it's not too late | 02:10 |
cyphermox | (re indicator-power | 02:10 |
didrocks | stgraber: what are you trying to fix exactly? | 02:13 |
didrocks | does it impact the dashboard/user experience? | 02:13 |
didrocks | we have click in main, so it's not an issue with main/universe | 02:13 |
didrocks | the next iso should build successfully, right? | 02:13 |
didrocks | even if click isn't that useful yet on the desktop | 02:13 |
Noskcaj | roaksoax, kirkland: Perhaps we should make testdrive community run rather than canonical run, since it's not canonical maintained or in "main" | 02:16 |
Noskcaj | Plus i've found a guy who's willing to convert it to gtk3 | 02:17 |
jbicha | testdrive is not run by canonical | 02:18 |
roaksoax | Noskcaj: it is community run nobody pays us to work on it | 02:19 |
roaksoax | i did it on my own free time | 02:19 |
Noskcaj | roaksoax, sorry, remove the canonical copyright | 02:19 |
cyphermox | stgraber: ignore my question about pstore, I just saw your lxc upload | 02:19 |
roaksoax | Noskcaj: the canonical copytight belongs there cause yhe projrct was modified aftrr i started at canonical | 02:20 |
jbicha | and if you're interested in gtk3, see https://code.launchpad.net/~jbicha/testdrive/port-to-gtk3/+merge/72369 | 02:20 |
roaksoax | hence the copyright | 02:20 |
jbicha | I won't have time to work on it any more | 02:20 |
Noskcaj | jbicha, DanChapman has nearly finished the gtk3 port, he said it should be done this week | 02:21 |
stgraber | didrocks: we're after feature freeze and that change pulls a dozen new packages on my system | 02:25 |
stgraber | cyphermox: I was just about to point it out :) unfortunately you'll need to manually apply the fix to your existing containers | 02:26 |
didrocks | stgraber: I think we should try to check if this shouldn't be considered as a noop | 02:26 |
cyphermox | right, and to the template used to create the containers | 02:26 |
didrocks | it's safe | 02:26 |
didrocks | it doesn't impact user experience | 02:26 |
didrocks | basically, we're just doing more work for nothing | 02:26 |
didrocks | and bringing pain to touch people | 02:27 |
stgraber | didrocks: well, I don't think it's a good idea to install extra packages offering extra APIs when we don't need to, it's making our images bigger and opening some new doors for potential security issues | 02:27 |
didrocks | stgraber: we should see one converged world IMHO, but I'm surprized that slept in | 02:28 |
didrocks | is this a direct dep? | 02:28 |
didrocks | I'm seeing in debian/control: | 02:29 |
didrocks | + liburl-dispatcher1-dev | 02:29 |
didrocks | nothing click*able | 02:29 |
stgraber | didrocks: indicator-power directly depends on some liburl stuff which brings in click indirectly | 02:29 |
didrocks | ah ok, so that one | 02:29 |
cyphermox | didrocks: https://code.launchpad.net/~mathieu-tl/otto/fix-mountall-pstore-hang/+merge/185612 | 02:29 |
didrocks | I just checked it's in main | 02:29 |
didrocks | do you feel it's that important to fix? | 02:30 |
didrocks | how critical is it in your opinion? | 02:30 |
didrocks | if you can test this indicator-power on the phone without this dep and it doesn't regress anything, this will be helpful | 02:31 |
stgraber | it's: indicator-power DEPENDS on liburl-dispatcher1-dev DEPENDS on liburl-dispatcher1 RECOMMENDS url-dispatcher DEPENDS on upstart-app-launch DEPENDS on click | 02:31 |
didrocks | so if it's the case, please upload the revert and bring that to the Vcs if possible | 02:31 |
didrocks | yeah, long chain of deps ;) | 02:31 |
stgraber | well, my position is, it's a change that brings an extra 10 packages on our default install without a freeze-exception (not that I'd grant one anyway), so it's a violation of the freeze and should be reverted. | 02:32 |
stgraber | also those packages currently have a standing FFe because they're touch-only | 02:33 |
didrocks | stgraber: can we think in term of user impact? | 02:33 |
stgraber | bringing them on the desktop would mean no more feature changes to any of them without a separate FFe | 02:33 |
didrocks | stgraber: didn't slacker_nl and lukasz discussed during vUDS about those common components? | 02:34 |
stgraber | didrocks: I don't see the user impact if the work had been done properly so that the indicator only integrates with touch stuff when it's actually running on touch | 02:34 |
didrocks | stgraber: can you test that? | 02:34 |
didrocks | before reverting | 02:34 |
didrocks | so that we don't break the baseline | 02:34 |
stgraber | didrocks: I'm sure that the revert will make it work no worse than it did this morning and the image was promoted back then, we'll just get back to having one non-working menu entry in the indicator | 02:35 |
didrocks | stgraber: but we're still regressing if that's the case | 02:35 |
didrocks | so we can put that on the list of things to look at | 02:36 |
didrocks | ensuring that it's working without it | 02:36 |
didrocks | and then, doing the revert | 02:36 |
didrocks | it sounds more sensible to me | 02:36 |
didrocks | than breaking for non critical issues compared to all other breakages we have | 02:36 |
didrocks | (as this one is a noop) | 02:36 |
stgraber | to be honnest, I care a whole lot more about us pushing extra unwanted packages on everyone's machine past feature freeze than breaking a single entry in our experimental images which didn't work in this morning's image anyway and hasn't been pushed to any actual user yet | 02:37 |
didrocks | stgraber: I think we should all work to be successful on the phone rather than trying to break something without testing | 02:38 |
didrocks | but anyway, your pick | 02:38 |
stgraber | which is why I'll upload the revert, if you disagree with that, I'll be happy to have a discussion with the rest of the release team about it | 02:38 |
didrocks | stgraber: can you at least please merge that back upstream? | 02:38 |
stgraber | I know exactly what I'll "break" on the phone, since I have a device next to me currently running the binary I'm about to revert the archive to | 02:38 |
stgraber | didrocks: and how do I do that? I suspect it's going to be much more complicated than my patch -p1 -R, won't it? | 02:39 |
didrocks | stgraber: you can still upload directly | 02:40 |
didrocks | stgraber: but please apply your patch to a branch that you propose upstream | 02:41 |
stgraber | ok, uploaded (that uploaded is very simply a patch -p1 -R of the previous one, except for debian/changelog) | 02:41 |
didrocks | stgraber: can you please paste the branch so that I can approve it? | 02:42 |
stgraber | didrocks: hmm, the VCS branch for that source is wrong... well, I guess /13.04/13.10/ will do the trick | 02:43 |
didrocks | stgraber: bzr branch lp:indicator-power? | 02:43 |
* didrocks checks | 02:43 | |
didrocks | stgraber: lp:indicator-power seems to contain the latest: indicator-power (12.10.6+13.10.20130913-0ubuntu1) saucy; urgency=low | 02:44 |
didrocks | right? | 02:44 |
stgraber | yeah, it's just the Vcs field that's wrong | 02:45 |
stgraber | the project trunk is right at least | 02:45 |
didrocks | stgraber: oh, feel free to fix it ;) | 02:45 |
didrocks | bonus point to bump the Standards-Version, I guess upstream won't ever do it :) | 02:45 |
stgraber | sorry, I don't care nearly enough to make a second commit | 02:46 |
stgraber | https://code.launchpad.net/~stgraber/indicator-power/revert-20130913/+merge/185613 | 02:46 |
didrocks | stgraber: approved, thanks | 02:47 |
=== freeflying_away is now known as freeflying | ||
=== freeflying is now known as freeflying_away | ||
=== freeflying_away is now known as freeflying | ||
=== ^oVeRMiND^ is now known as oVeRMiND | ||
ari-tczew | hello. I've got a problem with DSO linking. FTBFS log: http://paste.ubuntu.com/6105990/ (../src/libudt.so: undefined reference to `pthread*) ../src/Makefile: http://paste.ubuntu.com/6105984/ I was trying to move -lpthread in another place in line 29, but still doesn't work. can anyone help me? | 12:34 |
ari-tczew | err, above is mentioned ../app/Makefile | 12:35 |
=== Nisstyre-laptop is now known as nisstyre | ||
infinity | ari-tczew: See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=722958 for both my patch, and an educational discussion about the two ways you could have fixed it (you may find the latter useful for future similar bugs). | 20:14 |
ubottu | Debian bug 722958 in udt "udt: Fails to build with --as-needed linker option (patch)" [Important,Open] | 20:14 |
* cjwelborn is bored | 20:19 | |
* cjwelborn is bored | 20:20 | |
ari-tczew | infinity: so you mean to replace -lpthread with -pthread? | 20:41 |
infinity | ari-tczew: As I pointed out in the bug, there are two ways to fix it. I went with -pthread when I uploaded to Ubuntu though, yes. | 21:29 |
infinity | ari-tczew: (Obviously nothing for you to do here, since I already fixed it, just thought I'd point it out for educational reasons) | 21:29 |
susy41y | hello everyone | 21:43 |
susy41y | can ask what is the topic room? | 21:43 |
susy41y | hello | 21:47 |
ari-tczew | infinity: got it, thank you | 21:52 |
GuidoPallemans | anyone from the site can explain why I get this error? http://imgur.com/9t8ZdMD | 22:02 |
GuidoPallemans | Hey guys, I'm still getting an error trying to upload an app: http://imgur.com/9t8ZdMD | 22:12 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!