/srv/irclogs.ubuntu.com/2013/05/17/#ubuntu-devel.txt

=== tumbleweed_ is now known as tumbleweed
=== stokachu_ is now known as stokachu
stokachucjwatson: would you be able to weigh in on bug 1172101 when you have time00:46
stokachucjwatson: i keep thinking there was a reason why this wasn't done yet00:46
infinitystokachu: I believe that should Just Work, since d-i images are built with overwriting turned on, so that'll just overwrite the busybox-provided wget.00:53
infinitystokachu: But simple enough to test.  Grab the d-i sources, build your new wget, toss the udeb in extra-udebs, and build d-i to see what you get.00:53
stokachuinfinity: ah ok, i wasn't sure if there was a political reason for not doing it00:54
infinitys/extra-udebs/localudebs/00:54
stokachuill do some tests to make sure it works00:54
infinityI can't think of any political reasons against, since we don't include wget in our default images at all.00:54
stokachucool sounds good, thanks man00:54
infinityNow, including wget.udeb in the default images would be a different discussion.00:54
=== BenC- is now known as BenC
=== Ursinha is now known as Ursinha-afk
=== mnepton is now known as mneptok
=== _salem is now known as salem_
=== salem_ is now known as _salem
=== _salem is now known as salem_
=== salem_ is now known as _salem
=== _salem is now known as salem_
=== achiang` is now known as achiang
=== salem_ is now known as _salem
=== Guest3570 is now known as kirkland
=== kirkland is now known as Guest50630
pittiGood morning05:33
=== kirkland_ is now known as kirkland
pittixnox: did you see anything odd with the new udev on your setup?06:11
=== Guest65132 is now known as Zic
gesercould someone do a give-back of file-roller on i386 and amd64 please? looks like LP lost track of those builds (no build log available)06:33
pittihmm07:00
pittiNo builds for 'file-roller' found in the Saucy release - it may have been built in a former release.07:00
pittioh, -proposed07:00
pittigeser: done07:01
geserthanks07:02
mlankhorstdoes pbuilder allow you to keep the chroot if a build fails, so you can inspect what happens?07:06
gesermlankhorst: sort of, you can have a hook which drops you into a shell to investigate07:07
gesersee /usr/share/doc/pbuilder/examples/C10shell07:08
mlankhorstah07:08
mlankhorstcd /tmp/buildd/*/debian/..07:08
mlankhorstthat's actually quite smart..07:08
Mirvmitya57: hi! thanks for the qtchooser sync! I've a plan now for the saucy uploads, see http://pastebin.ubuntu.com/5666894/07:18
mitya57Mirv: what does "synced but pkg transition" mean?07:20
Mirvmitya57: means that the packaging is in sync with Debian, but Ubuntu has an additional package transition from raring that needs eg Replaces:07:21
Mirvsince Debian never had 5.0.107:21
mitya57OK, sounds nice. Please subscribe me to the sync requests if you'll be doing any07:22
Mirvmitya57: ok, I will, unless some coredev helps me in doing syncs directly07:23
mitya57Mirv: by the way, qtdoc is currently useless, as documentation should be built in each module07:26
mitya57I'm planning to look at qtbase documentation when I have some time07:26
Mirvmitya57: I noticed that it indeed gives quite a skeleton of documentation out07:27
mitya57yes, but only a skeleton07:27
Mirvso not worth that much, even though with that Qt Creator gets Qt5 documentation topic07:27
Mirvthere are some examples et cetera07:27
Mirvbut no API docs07:27
mitya57API docs is the most useful thing :)07:29
=== doko_ is now known as doko
geserinfinity: as you are TIL for vim: can I grab the vim merge from you or do you plan to do it yourself?07:46
tjaaltonthe manual partitioner of the installer has no option to resize ntfs volumes?07:47
tjaaltonsaucy installer doesn't seem to recognize win807:47
=== megha is now known as hack
=== hack is now known as baba
infinitygeser: I'll pick it up.  I'd prefer to retain TIL on it.08:07
infinity@pilot out08:07
=== udevbot changed the topic of #ubuntu-devel to: Ubuntu 13.04 released | Archive: open | Devel of Ubuntu (not support or app devel) | build failures -> http://qa.ubuntuwire.com/ftbfs/ | #ubuntu for support and discussion of hardy -> raring | #ubuntu-app-devel for app development on Ubuntu http://wiki.ubuntu.com/UbuntuDevelopment | See #ubuntu-bugs for http://bit.ly/lv8soi | Patch Pilots: seb128
seb128@pilot out08:07
=== udevbot changed the topic of #ubuntu-devel to: Ubuntu 13.04 released | Archive: open | Devel of Ubuntu (not support or app devel) | build failures -> http://qa.ubuntuwire.com/ftbfs/ | #ubuntu for support and discussion of hardy -> raring | #ubuntu-app-devel for app development on Ubuntu http://wiki.ubuntu.com/UbuntuDevelopment | See #ubuntu-bugs for http://bit.ly/lv8soi | Patch Pilots:
seb128ups, forgot that yesterday08:07
Laneymfisch: pretty sure it's supposed to be 14 & 19 UTC currently08:11
Laneytumbleweed: confirm/deny?08:12
geserinfinity: ok, I just noticed that we probably can drop the delta to add liblaunchpad-integration to the help menu as liblaunchpad-integration got removed since raring08:13
Laneyah, came up on the ML08:16
zequencediwic: I linked two branches to this bug report https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/116363808:43
ubottuLaunchpad bug 1163638 in pulseaudio (Ubuntu) "pulseaudio fails to release card to jack" [Undecided,Confirmed]08:43
zequencediwic: I've test built them, so they seem to work ok08:43
zequencediwic: Would you mind looking at if the patches are well applied?08:43
zequence..and documented08:44
zequencelp:~zequence/+junk/pulseaudio.precise08:44
zequence lp:~zequence/+junk/pulseaudio.quantal08:44
diwiczequence, ok08:45
diwiczequence, have you also tested the result to make sure the handover actually works now?08:47
zequencediwic: Only on quantal, and only on a virtual install. I need to do more testing08:48
zequencebut, initially, it seems to work the way it's supposed to08:49
diwiczequence, nitpick: "Let's pulseaudio let go" <- bad wording in changelog08:49
zequenceAh, I think I wrote them one too many times :)08:49
diwiczequence, also on SRUs I think it's always .x, i e not 1:2.1-0ubuntu5 but 1:2.1-0ubuntu4.108:51
diwiczequence, it's correct in the precise one but not the quantal one08:51
zequenceok08:51
=== gusch is now known as gusch|away
zequencediwic: If that's all you can think of, then I'll happily redo both branches with those changes then08:55
diwiczequence, that and proper testing08:55
zequencejack people will be thoroughly happy once the fix is out08:55
zequenceit's one of the most common problems users face, so should make some channels a lot more silent for a while :)08:56
diwiczequence, sounds good :-)08:56
=== rajaniemi.freenode.net changed the topic of #ubuntu-devel to: Ubuntu 13.04 released | Archive: open | Devel of Ubuntu (not support or app devel) | build failures -> http://qa.ubuntuwire.com/ftbfs/ | #ubuntu for support and discussion of hardy -> raring | #ubuntu-app-devel for app development on Ubuntu http://wiki.ubuntu.com/UbuntuDevelopment | See #ubuntu-bugs for http://bit.ly/lv8soi | Patch Pilots: seb128
=== sraue_ is now known as sraue
Laneybad ircd09:37
=== Laney changed the topic of #ubuntu-devel to: Ubuntu 13.04 released | Archive: open | Devel of Ubuntu (not support or app devel) | build failures -> http://qa.ubuntuwire.com/ftbfs/ | #ubuntu for support and discussion of hardy -> raring | #ubuntu-app-devel for app development on Ubuntu http://wiki.ubuntu.com/UbuntuDevelopment | See #ubuntu-bugs for http://bit.ly/lv8soi | Patch Pilots:
rbasakIf in Launchpad an Ubuntu package does not have a SF upstream linked as an upstream project, am I supposed to "register" this in Launchpad in order to make upstream bug tracker functionality work properly? Or is there some other way to do it? It's not clear to me whether "registration" in LP is necessary (whatever that means), or there's some other way to "link" the upstream that isn't hosted on LP.09:46
* rbasak asks in #launchpad09:49
tumbleweedyou can just put the bug URL in the report, and it'll track it, but it can't be added as a task.09:50
rbasakYeah, but it would be nice to know how to do it "properly". I've left bugs like that before, so it would be nice to learn how to do it right this time round.09:51
diwicuhm, I seem to have a directory /home/<user>/.local/share/sounds without execute permissions, so I can't view the directory. This is weird. Any of you running saucy and can do a quick check if you have that too?09:53
diwicI have no idea who could have created it09:54
diwici e what program09:54
geserdiwic: same here: drw-------09:55
diwicgeser, thanks. Do you have any idea of how one can figure out how it got there? It's causing libcanberra to malfunction09:56
seb128diwic, drwxr-xr-x for me09:57
seb128created on april 1909:57
diwicseb128, any contents in it?09:58
seb128no, empty10:00
gesermy directory got last changed/modified on 2013-05-1510:02
seb128diwic, I can confirm, it's getting created on login if it doesn't exist and with the permission rw-10:02
seb128diwic, I just tried with a test user, rm it, log in, the directory is created before you start anything10:02
diwicseb128, okay, thanks, is there a smart way to figure out what process creates it?10:03
seb128diwic, not that I know about10:04
cjwatsonstrace -f or systemtap or something10:05
seb128cjwatson, strace what process?10:05
seb128something on login create that dir, the goal is to figure out what process something is ;-)10:05
cjwatsonstrace -f the display manager :)10:05
cjwatson(not from X ...)10:05
cjwatsonwell, maybe that doesn't work with upstart user sessions10:06
geserseb128, diwic: could it be the last upload of gnome-settings-daemon? the diff mentions a "sounds" directory10:06
cjwatsonsomething like systemtap should be able to do it, not that I really know how to drive it yet10:06
seb128geser, I was looking into that yes10:06
diwicgeser, thanks, will have a look10:06
rbasakThe answer was to do the registration. Looks like the upstream project must get an entry in the LP namespace, and then the Ubuntu package can be linked to it and all the nice integration then works.10:06
seb128geser, diwic:10:07
seb128debian/patches/git_sound_not_polling.patch:+        if (g_mkdir_with_parents(p, 0600) == 0)10:07
diwicyep10:07
seb128geser, diwic: https://git.gnome.org/browse/gnome-settings-daemon/commit/?h=gnome-3-6&id=75b8bae1e71199ea7b19769be1c4f423722dffc710:07
diwicthat must be it10:07
seb128is the commit I backported10:07
seb128that bug comment #2 describe the issue10:08
Laneys/6/7/ probably10:09
seb128seems like they screwed that backport10:09
seb128https://git.gnome.org/browse/gnome-settings-daemon/tree/plugins/sound/gsd-sound-manager.c?h=gnome-3-610:09
seb128https://git.gnome.org/browse/gnome-settings-daemon/tree/plugins/sound/gsd-sound-manager.c?h=gnome-3-810:09
seb128has 70010:09
seb128I will upload a fix and report it upstream10:09
seb128diwic, do you have a lp bug number for the issue?10:09
Laneyhttps://git.gnome.org/browse/gnome-settings-daemon/commit/?id=b97a62f56d7f3187c9ab516c8f3c2aa6785665c610:09
Laneyjust needs to be push to 3-6 too I guess10:09
Laneypushedd10:10
diwicseb128, no, I was just testing a new version of PulseAudio and discovered this10:10
Laneyargh10:10
seb128Laney, want to take care of it?10:10
seb128Laney, upload/ping upstream?10:10
diwicupstream fixed it with https://git.gnome.org/browse/gnome-settings-daemon/commit/?id=b97a62f56d7f3187c9ab516c8f3c2aa6785665c610:11
Laneyhttps://bugzilla.gnome.org/show_bug.cgi?id=694134#c610:11
ubottuGnome bug 694134 in general "g-s-d sets an inotify watch on ~/.local/share/sounds, which normally does not exist.. and causes polling" [Normal,Resolved: fixed]10:11
seb128diwic, Laney snapped you ;-)10:11
diwicseb128, Laney thanks for fixing it. The result is otherwise that testing speakers in gnome sound settings does not work.10:12
seb128diwic, the sound panel is also unhappy and goes in an infine loop trying to update the timestamp if you try to change a sound effect10:13
LaneyI can upload that cherry-pick, but perhaps we should take care to fix existing broken ones too?10:13
seb128Laney, it's only in saucy for people who didn't have the directory before and it has been in there for less than a week10:13
seb128Laney, not sure how many users that set includes ... I guess it wouldn't hurt to add a temporary chmod call to that path in saucy though10:14
Laneyyou could probably do something with g_access/g_chmod without too much difficulty10:15
Laneywill do it soon10:15
seb128right10:15
seb128Laney, you are on it then? just ping if you need a peer review or something10:16
Laneysure, cheers10:16
cjwatsonseb128: looks like c2esp could be synced from experimental?10:29
cjwatsoninfinity: would be nice to have a debhelper merge when you get a chance10:29
seb128cjwatson, it can yes ... are you syncing it or should I?10:30
cjwatsonseb128: doesn't really matter I guess, doing now10:32
=== gusch|away is now known as gusch
seb128cjwatson, right, I just didn't want to dup the action, thanks ;-)10:32
seb128well I guess whoever would have tried second would just have got a "nothing to sync"10:32
=== Mez_ is now known as Mez
Laneydiwic: uploaded gnome-settings-daemon, thanks for reporting!11:27
=== MacSlow is now known as MacSlow|lunch
seb128tsdgeos, hey, are you on ubuntu-devel list? tkamppeter emailed it about mupdf/poppler11:33
=== mmrazik is now known as mmrazik|afk
loolseb128, tsdgeos: just a heads up: you might want to followup on the thread for the PDF rendering backend for Touch printing stack that Till just started on -devel; e.g. maintenance wise, quality wise etc.12:00
loolseb128: ah I saw you've seen it already12:00
looland pinged tsdgeos :-)12:01
* lool is so half-an-hour late12:01
seb128lool, yeah, thanks, I'm planning also to follow with "do we have any benchmark showing the performance difference?", because so far it seems it's marketing speech from upstream without facts check12:01
loolseb128: you mean the lightweightness claims?  yeah12:02
loolI wonder whether we could throw a bunch of PDFs at both and compare rendering too12:02
lool(or crashes  :-)12:02
diwicLaney, thanks for the swift handling :-)12:08
zygahi, is jockey supposed to work with precise and -lts-{quantal,raring} kernel?12:08
tvosspmcgowan, ping12:20
pmcgowanhey tvoss12:20
=== MacSlow|lunch is now known as MacSlow
=== mmrazik|afk is now known as mmrazik
rbasakWhat's the current best practice for the pocket in debian/changelog for an SRU? Eg. precise, precise-proposed or precise-updates? All work now, right?12:46
cjwatsonI wouldn't use -updates.  Either precise or precise-proposed is fine.  I've been drifting towards the former.12:47
pittirbasak: no, not precise-updates12:47
pittirbasak: as for precise vs precise-proposed, they behave the same now12:47
rbasakOK. I'll use just precise then. Thanks!12:47
rbasak(precise-proposed always felt a bit wrong as it doesn't actually end up there)12:47
pittistrictly speaking it also doesn't land in "precise", but in "precise-updates"; but it eliminates the difference between pre- and post-release uploads, so it's nice12:49
=== wedgwood_away is now known as wedgwood
cjwatsonprecise might either refer to the suite (== release pocket) or to the series as a whole, so that part doesn't bother me12:51
=== greyback is now known as greyback|lunch
tsdgeostkamppeter: why on -devel and not in ubuntu-phone ?13:30
ogra_or both (since it affects both)13:30
tsdgeoslool: tsdgeos_work@xps:/home/tsdgeos/okularfiles/pdf$ ls -l *.pdf | wc -l13:31
tsdgeos140413:31
=== henrix_ is now known as henrix
tsdgeos"is the only free software which allows filling and saving PDF form"13:33
tsdgeosoh really?13:34
* tsdgeos looks at poppler13:34
tsdgeosogra_: can you forward me the original email so i can answer to it? (me was not subscribed to -devel) (me hides)13:35
ogra_tsdgeos, done ... its also in the archives on lists.ubuntu.com indeed13:37
tsdgeosogra_: sure, i've read it there13:39
ogra_ah13:39
tsdgeosbut for a proper answer i need the mail on my mail client13:40
tsdgeosso headers match, etc13:40
ogra_hmm, i forwarded as attachment ... might not help ...13:40
tsdgeoslet's see :)13:41
ogra_bounced now13:41
=== greyback|lunch is now known as greyback
ogra_that should have proper headers13:41
tsdgeosogra_: second forward better, tx13:45
=== kentb-out is now known as kentb
=== francisco is now known as Guest99200
looltsdgeos: this is mainly a convergence topic as printing isn't top priority for touch phones/tablets; -devel seems fine to discuss common topics14:16
tsdgeosok, mail subject is "Ubuntu Touch:" didn't mention much on convergence on the content either14:19
tkamppetertsdgeos, the missing capability of the Ubuntu desktop to fill forms is then probably caused by the GUI frontends, like evince.14:29
tsdgeosno clue about evince, in okular we save forms, of course there are bugs, all software has bugs unfortunately :/14:35
sladentkamppeter: I'll reply later.  I've been using mupdf for rendering for the last decade, as it produces better results.  It is GPL, whether that's an issue having it as part of the API used by end-user apps14:36
=== _salem is now known as salem_
tsdgeossladen: do you have any hard data for taht other than a feeling?14:40
tsdgeosi'd like to see it :-)14:40
tsdgeoslol, it's cool how pdf.js tells me that http://www.acquerra.com.au/poppler/img_0.pdf won't prbably work when opening it :D14:40
sladentsdgeos: works for me14:42
tsdgeoswhat works?14:42
sladentsdgeos: http://www.acquerra.com.au/poppler/img_0.pdf  works for me [in Firefox, with pdf.js]14:43
tsdgeosyou don't get a nice warning at the top?14:43
tsdgeosare you on ff21?14:43
tsdgeosdo you see the 3 ducks on the right?14:44
sladentsdgeos: firefox 20.0+build1-0ubuntu0.12.04.314:48
tsdgeosthey problably introduced the warning in ff2114:49
=== jml_ is now known as jml
sladentsdgeos: what is the warning about?  PDF-1.7 or duplicate trailers, or something else?14:53
tsdgeossladen: it just says "This document may not be shown properly"14:54
tsdgeoswhich is correct14:54
stgraberstokachu: alright, looking at your bugs now, sorry for the delay14:55
stokachustgraber: no worries, thanks for the help14:56
sladentsdgeos: seems the version poppler does equally badly (in a different way)14:57
tsdgeossladen: works fine here, can you get a screenshot?14:57
sladentsdgeos: 0.18.4-1ubuntu3.1  it's old though14:58
tsdgeoslol14:58
sladentsdgeos: so you likely will not care14:58
tsdgeosno need for a screenshot then14:58
=== francisco is now known as Guest36497
sladen~,15:07
tkamppetertsdgeos, sladen, which PDF library does ff21 use? Poppler, MuPDF, Ghostscript, or did they write their own from scratch?15:09
tsdgeostkamppeter: pdf.js15:09
tkamppetertsdgeos, is this a complete PDF interpreter, not using any external library?15:09
tsdgeoswell, it's using firefox15:10
tsdgeos:D15:10
tsdgeosthat's a quite big "external library"15:10
sladentkamppeter: $browser.$canvas implementation15:10
cjwatsonhttps://mozillalabs.com/en-US/pdfjs/ "without native code assistance"15:10
tkamppetertsdgeos, so the Firefox browser contains a complete PDF interpreter/renderer (at least from version 21 on)?15:10
tsdgeosyes15:11
tsdgeosit has for a while15:11
tsdgeosit's not that good15:11
tsdgeosbut they know it15:11
tsdgeoswhich is the first step to fixing it15:11
sladenno, pdf.js (a bunch of ECMAScript) contains a complete interpreter15:11
ogra_how about chromium (given there are plans to switch to it by default now)15:11
sladenit simply does   var canvas = document.createElement('canvas');  and then draws into that15:12
tsdgeosogra_: chromium has no pdf rendeer15:12
ogra_right15:12
tsdgeoschrome has15:12
tsdgeosbut it's not free soft15:12
ogra_can chromium use the external one15:12
tkamppetertsdgeos, and now they think it is reasonably good and so they started to make it be used by default?15:12
tsdgeoschromium can use pdf.js15:12
tsdgeosafter all it's js :D15:12
ogra_heh15:12
sladenogra_: fire up pdf.js in Chromium...15:12
LaneyI wouldn't say we're at the stage of planning to switch to Chromium yet15:13
tsdgeostkamppeter: i don't think it's reasonably good but that's my opinion15:13
LaneyFWIW15:13
sladenogra_:  chromium-browser http://mozilla.github.io/pdf.js/web/viewer.html15:19
sladenogra_: (and it's faster than in FF)15:20
psusicjwatson: just wanted to make sure you did get the parted merge bundle I sent.. I know you're busy but it's been over a week so I thought I'd check...15:23
ogra_sladen, a wet sponge is faster than FF15:23
barrybdmurray, ping15:26
Laneyhighvoltage: stgraber: I just noticed that edubuntu has some Xsession.d scripts which look as if they may be crufty, FYI15:29
stgraberLaney: ah?15:30
Laneymaybe, maybe not, but they caught my eye :-)15:30
Laney25edubuntu-menus looks curious15:30
bdmurraybarry: hey15:32
stgraberLaney: is that edubuntu-menus?15:33
Laneyya15:34
cjwatsonpsusi: I did, UDS was in that week15:35
cjwatsonWhich means not a lot else happens :)15:36
stgraberLaney: right, that package is no longer shipped in Edubuntu and was replaced by edubuntu-menueditor+desktop-profile15:37
tkamppetertsdgeos, about the filled forms see https://bugzilla.gnome.org/show_bug.cgi?id=695615 and bug 1153517.15:37
barrybdmurray: hi.  so over in python-dev, we've got some interesting theories about the pyc corruption problem.  question for you.  from the evidence you've seen, are the pyc files permanently corrupted or do they self repair?  i think we're seeing permanent corruptions, such that users have to take active role in fixing things (e.g. remove the .pyc and re-bytecompile it)15:37
ubottuGnome bug 695615 in PDF "evince does not save filled PDF forms" [Critical,Unconfirmed]15:37
Laneystgraber: can we remove? :-)15:37
barrybdmurray: can you confirm?15:37
ubottubug 1153517 in poppler (Ubuntu) "evince does not save filled PDF forms" [High,Triaged] https://launchpad.net/bugs/115351715:37
=== slangase` is now known as slangasek
LaneyI'm simply going through all of the Xsession.d scripts ATM so don't have information like that available (OK, I could have checked ...)15:37
stgraberLaney: yep, I just checked, not seeded and no rdepends (just a conflict with ubuntustudio-menu), I'll kill it from the archive now (haven't tried that new power yet ;))15:38
Laneyphwoar15:38
bdmurraybarry: yes, from the bugs I've read of the people who've sorted it out they had to do it manually15:38
Laneythe other edubuntu one in edubuntu-live looks like it could become a job15:39
barrybdmurray: okay, thanks.  guido outlined a scenario where the files could be temporarily corrupted, but should self repair.  i think he's on to something, but we still haven't identified the entire problem.  i still think i might have a fix though15:39
stgraberLaney: 1 package successfully removed.15:41
Laney*archive catches on fire*15:42
=== gusch is now known as gusch|away
tsdgeostkamppeter: i don't do evince development15:43
tsdgeosbut yeah the fact that we major release old of poppler is not good15:44
tsdgeosbesides the fact that we still don't use libopenjpeg15:44
tsdgeosbut i've decided to not fight that battle anymore and accept we don't care about having good supported jpeg2000 rendering in pdf in ubuntu15:45
seb128tsdgeos, we would ship new poppler if there was15:47
seb128- a reliable release schedule15:47
tsdgeosthere is15:47
tsdgeosthere as always been15:47
seb128- upstream stopped breaking ABI and changing soname forcing us into transitions15:47
tsdgeoswe don't break ABI15:47
seb128well, you bump sonames15:48
tsdgeosit's people that use headers we don't support15:48
tsdgeossoname of the internal library15:48
tsdgeosnoone is supposed to use15:48
tsdgeosyet people use them15:48
seb128don't make it public then?15:48
tsdgeosthey are not15:48
seb128if it's not supposed to be used15:48
seb128they are installed in /usr/lib15:48
=== mmrazik is now known as mmrazik|afk
seb128and the .h are installed15:48
tsdgeosyou use the --install-xpdf-headers swtich15:48
seb128which is an option provided by upstream ;-)15:49
tsdgeosthat clearly says they are unsupported15:49
psusicjwatson: ok, I figured, just wanted to be sure the mail wasn't lost15:49
tsdgeos"Install unsupported xpdf headers."15:49
tsdgeosyou can't blame us if we change unsupported things15:49
tsdgeoscan you?15:49
tsdgeoswell you can15:49
tsdgeosbut not that i care :D15:49
seb128tsdgeos, reality is15:50
seb128$ apt-cache rdepends libpoppler28 | wc -l15:50
seb1282415:50
tsdgeosseb128: and please don't spread fud about not reliable schedule15:50
tsdgeosseb128: as said, that's not our problem15:51
seb128tsdgeos, I need to find my old email back, some years ago I emailed about that, and somebody from upstream replied my that poppler was not aligned on GNOME or Ubuntu schedule and have no intention to be15:51
seb128so maybe that was that15:51
tsdgeossure15:51
seb128schedule is reliable but not working for us15:51
tsdgeoswe have no intention to align to gnome or ubuntu15:51
seb128ok15:51
tsdgeoswhy would we do that stupid thing?15:51
seb128so don't complain that we can't ship the current version ;-)15:51
seb128because most distros are aligned on those schedules15:52
seb128and it would make you have more current versions in distros15:52
tsdgeos:D15:52
tsdgeosyou really believe that?15:52
seb128yes15:52
tsdgeosyou've been working on ubuntu for too much D:15:52
psusiaren't we behind by more than one release though?15:52
seb128psusi, no15:52
seb128current is 0.22 and we have 0.2015:52
psusiahh, ok then15:53
tsdgeosseb128: yes you are, 13.04 ships something that was released on October15:53
tsdgeoswhile 0.22 was released on December15:53
tsdgeosthat seems pretty out of sync to me15:53
seb128tsdgeos, where can I find the 0.24 schedule?15:53
psusitsdgeos: that's not that long ago ;)15:53
tsdgeosseb128: on the wiki15:53
seb128"the wiki"15:54
* seb128 goes the.wiki.com15:54
seb128k, found ity15:54
seb128http://freedesktop.org/wiki/Software/poppler15:54
tsdgeosalso know "as google"15:54
Nafalloseb128: wikipedia is likely "the wiki" these days, fwiw :-)15:54
tsdgeos"poppler 0.24 schedule"15:54
seb128I guess we could go for 0.24 this time15:54
seb128do you plan to change your private soname between now and 0.24? (I guess you do)15:55
tsdgeosyou mean 0.22 and 0.24?15:55
tsdgeossure15:55
tsdgeos0.23.1 already changed it15:55
psusihrm... debian is still on 0.18, even in unstable15:55
tsdgeosand we'll be changing it if needed15:56
Laneyit's probably the most pressing thing causing distros not to want to update as often as they might15:56
tsdgeosseb128: can you elaborate on the problem of changing the soname? i mean archlinux gets to use newest poppler release all the time, what's the catch in our side?15:57
seb128tsdgeos, we need to rebuild all rdepends to pick the new soname15:57
seb128which includes libreoffice15:57
Laneyperhaps it would be profitable to investigate why people are using private things and try to provide public API?15:57
seb128which doesn't build atm in saucy with the current toolchain15:57
seb128tsdgeos, so it means we can't even update poppler atm, until we fix libreoffice's build15:57
seb128the transition will get stucked otherwise15:58
tsdgeosseb128: ok, so we have bigger problems :D15:58
seb128well, libreoffice is being worked15:58
tsdgeosLaney: well, i'm not going to go out there chasing random people15:58
seb128but while that's not solved, I can't update poppler15:58
tsdgeosif people feel the need of a stable api we have a nice mailing list where we don't eat people15:58
tsdgeosmost of times :D15:58
psusiI'm confused... are you saying poppler provides two libs, and one is supposed to be internal and subject to frequent abi breakage?16:00
tsdgeoswe provide 4 libs16:01
tsdgeos3 of those we stable api (qt, glib and purec++ apis)16:01
tsdgeosand the internal one use by those 316:01
tsdgeoswhose abi/api changes as we see fit16:02
psusiI see... and people keep going direct to the internal library eh?  I wonder why...16:03
seb128but which is still installed in /usr/lib16:03
seb128with a proper soname versioning16:03
seb128as a public library16:03
seb128and its name is "libpoppler" not libpoppler-private16:03
tsdgeosso?16:04
seb128so people don't see that it's private16:04
seb128it's just like any other library16:04
psusiso it's not very obvious that it's private ;)16:04
tsdgeosyou don't get it's headers unless you agree to install unsupported16:04
seb128so they use it16:04
seb128well, distro use the configure flag that you provide16:04
tsdgeosand btw16:04
tsdgeoslibpoppler-private-dev16:04
seb128you shouldn't provide it if it's not supported16:04
tsdgeos;-)16:04
tsdgeosthat's the package name16:04
tsdgeosin ubuntu16:04
tsdgeostells you something?16:05
seb128right, debian did that change recently16:05
tsdgeoswonder why ;-)16:05
seb128because the upstream naming was not giving the message16:05
seb128because you guys don't?16:05
Laneyit's not all that many packages to be fair16:05
tsdgeosbecause the debian packager is "one of us"16:05
seb128Laney, no, but it includes libreoffice :p16:05
tsdgeosand he gets it16:05
tsdgeosseb128: i can change the library name to16:06
LaneyI'm talking about if there was a push to get people off the private lib16:06
seb128sure, if everybody gets it wrong, blame it on everybody16:06
tsdgeoslibpopplerprivatedontuseitoryoulldie16:06
tsdgeosand people will still use it16:06
seb128easier than trying to think if you maybe could help them16:06
tsdgeosseb128: i can't help them16:06
tsdgeosi have no time to help them16:06
tsdgeosso they have to help themselves16:06
tsdgeosif they want16:06
psusiso bottom line is that the fact that people still use this lib and it breaks abi a lot adds some resistance to keeping up to date on the very latest upstream, but hopefully saucy will get updated once this problem with libreoffice is sorted, right?16:06
tsdgeosto keep using headers that change all the time16:07
tsdgeosthere's not much i can do16:07
seb128psusi, to 0.22 yes, because it seems like 0.23 is going to change soname on the way again and we don't want to go through a transition every time that happens during the unstable cycle16:08
Laneythere's some scary beasts in there like tex though16:08
seb128tsdgeos, you shouldn't have provided that unsupported configure option of installing those .h to start16:08
seb128but oh well16:08
tsdgeosseb128: blame redhat16:08
seb128that's done16:08
tsdgeosthey started poppler16:08
tsdgeosnot me16:08
seb128well, without that we would still have to use xpdf for things I guess16:09
tsdgeosbesides you distros would have done it anyway16:09
seb128which apparently you, as poppler upstream would prefer16:09
seb128but yeah, as a distro we prefer using poppler only16:09
cjwatsontransitions wouldn't be so horrible if not for libreoffice being in there16:09
tsdgeosso don't blame me for doing waht you wanted16:09
tsdgeosthat's kind of nasty16:09
tsdgeosbut you install the headers!16:09
tsdgeosbut we would have installed them anyway if you didn't!16:10
psusitsdgeos: I think seb is just lamenting the status quo outloud, rather than really blaming you16:10
tsdgeospsusi: well "<seb128> tsdgeos, you shouldn't have provided that unsupported configure option of installing those .h to start"16:11
tsdgeosdoesn't seem general lamenting :D16:12
Laneyaaaaaaaaaanyway16:12
seb128tsdgeos, I'm just responding to you blaming us for using an option upstream provides :p16:12
seb128but yeah, anyway16:12
LaneyAs long as software is using it we don't really have a choice16:12
=== gusch|away is now known as gusch
tsdgeosanyway it's friday 6pm16:12
tsdgeosbye guys16:12
seb128life would be easier if upstream poppler made their private library not-so-private and supported a stabler api for it16:13
Laneybonne nuit16:13
seb128stgraber, pitti: could you mark https://code.launchpad.net/~jm-leddy/ubuntu/raring/lupin/fix-670096/+merge/162189 merged or rejected (not sure which one is right, it was targetting raring but got uploaded to saucy)16:37
stgraberseb128: done16:40
seb128stgraber, thanks16:40
seb128stgraber, can you put https://code.launchpad.net/~fehwalker/ubuntu/precise/cobbler/lp1001846/+merge/151352 as work in progress?16:40
stgraberseb128: done16:42
seb128stgraber, thanks16:42
seb128one day we should really get that acl issue fixed...16:42
seb128stgraber, can you set https://code.launchpad.net/~kentb/ubuntu/raring/ledmon/dell-pcie-ssd-fix_lp1174386/+merge/161696 as merged as well?16:59
stgraberdone17:01
seb128thanks17:02
=== sil2100_ is now known as sil2100
=== iulian is now known as Guest36841
=== mhall119_ is now known as mhall119
stgraberstokachu: bug 1094319 is missing the SRU paperwork19:38
ubottubug 1094319 in gnome-keyring (Ubuntu Quantal) "p11-kit: couldn't load module: /usr/lib/i386-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: /usr/lib/i386-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: cannot open shared object file: No such file or directory" [Undecided,New] https://launchpad.net/bugs/109431919:38
stokachustgraber: even though thats just a piggyback?19:38
stokachustgraber: i can add it real quick if required19:38
stgraberstokachu: yes, every bug listed in the debdiff needs to have a reason why it's being SRUed, a testcase and some risk analysis19:39
stgraberstokachu: and that last point will be very important when we're talking about splititng the package and introducing a new binary package post-release19:39
stokachuk gimme a minute ill have it updated19:40
stgraber(as in, will upgrades from precise => quantal => raring work, did you check that the breaks/replaces/provides are setup properly so we won't get install time file conflicts, ...)19:40
stokachustgraber: ive done the rdepends testing19:41
stgraberthe current bug report only sounds like an annoyance (spamming the console), so I think the SRU team will want a bit more than that as a reason to introduce a new binary package19:41
stokachustgraber: ive updated the description for the sru19:42
stokachustgraber: as far as I can tell regressions should be minimal19:42
stokachuno hardcoded library paths etc19:42
=== francisco is now known as Guest85075
stgraberstokachu: diff looks reasonable, test build worked and the binary packages contain what they should, uploaded both packages to the queue20:53
infinity*blink*21:01
infinityUnity has decided that firefox and pidgin are the same application group.21:01
infinityThey both show up in the same Alt-` group.21:01
infinityHas anyone else seen this madness? :P21:01
cody-somervilleinfinity: I've seen things like that before, yea. One time it even decided one of my windows didn't exist at all anymore even though it clearly was still there.21:26
=== wedgwood is now known as wedgwood_away
=== salem_ is now known as _salem
stokachustgraber: thanks22:53
straemerI created a patch for the reddit webapp a while ago that's still in a "needs review" state, would someone be able to review it?23:22
straemerLink: https://code.launchpad.net/~straemer/ubuntu/quantal/unity-webapps-reddit/fix-for-1059882/+merge/15134723:22
straemerSorry, my computer crashed there. Did anyone say anything regarding getting my merge request reviewed?23:29
sarnoldstraemer: sorry, no one replied..23:33
robrustraemer, your MP is based against the ubuntu quantal package, which is incorrect. In order to make a change against quantal, it first needs to be fixed in Saucy and then SRU'd back to raring and then quantal (SRU is an intensive review process to make sure your changes won't break anything). please rebase your MP against lp:unity-webapps-reddit23:50
straemerrobru: I made the patch long enough ago that quantal would have been the relevant version at the time23:51
robrustraemer, yikes, sorry to hear that. still, lp:unity-webapps-reddit is where it needs to go to today.23:52
robrustraemer, actually, even back then it was still a mistake to propose an MP against a packaging branch. at the time you would have wanted to MP into lp:webapps-applications (which was the upstream trunk that housed *all* of the apps), but now they've been separated into individual projects, so lp:unity-webapps-reddit is the correct place today.23:55

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