=== slangase` is now known as slangasek [01:28] Did a test sync of cairo, seems to fix the segfault that I keep on hitting. In Ubuntu it's stuck on an old git snapshot. [01:31] !info libcairo2 vivid [01:31] !info libcairo2 unstable [01:31] libcairo2 (source: cairo): The Cairo 2D vector graphics library. In component main, is optional. Version 1.13.0~20140204-0ubuntu1 (vivid), package size 537 kB, installed size 1467 kB [01:31] libcairo2 (source: cairo): Cairo 2D vector graphics library. In component main, is optional. Version 1.14.0-2.1 (unstable), package size 780 kB, installed size 1630 kB [01:38] Unit193: I think it should be processed by seb128. [05:29] Unit193: note the changes from the last merge: https://launchpad.net/ubuntu/+source/cairo/1.12.10-1ubuntu1 [05:30] but yeah, definitely talk to seb128 [05:33] Logan_: Right, one is a git commit and another is an additional dep that's been added since. === not_phunyguy is now known as phunyguy [07:55] Logan_, Is --parallel enough of a reason to not sync latexila? [07:55] what about the recommends/suggests? [07:56] I didn't see a need for them, but i think i should contact matttbe before syncing [07:57] good call :) [12:42] xnox: are you planning to merge/sync cryptsetup soon? [12:43] seems like you included alot of ubuntu changes into debian yet :) [17:39] hi there, when running autopkgtests, do you reckon it would make sense to export some standard variables like HOME, XDG_* , etc so that tests that write files to those locations can proceed without issues? In a whole bunch of KF5 and Plasma 5 tests, I've had to manually export dirs in each of the tests which is super annoying ... === rcj is now known as Guest48642 [18:29] is it appropriate to suggest a prerelease package for Inkscape for Vivid? [18:29] the current version is 0.48, and there is a 0.91pre3 pre-release which is 3 years newer. [18:30] It would be nice to have inkscape and inkscape0.91 (the same as there used to be multiple wine packages), but this may be out of taste for ubuntu [18:30] there's a ppa that includes nightly builds, but that is ... well, nightly builds are different than having a development build. [18:31] Experimental has 0.91. [18:31] (similarly, why the hell does 14.10 have Wine 1.7? 1.7 is a development branch, and there is no wine 1.6 available)) [18:31] Unit193: there's an Experimental repo? [18:31] Debian, upstream. [18:31] ah [20:56] Is there a way i can find out why UDD branches aren't in sync with the current version? [20:57] http://package-import.ubuntu.com/status/ [21:02] bzrlib.plugins.builddeb.upstream.pristinetar.PristineTarError fails a number of xubuntu's packages, is there something xfce/bluesabre could do to help avoid that? [21:10] Give up on UDD? ;-) [21:12] heh [21:12] Though in that case it's possible that an updated pristine-tar backport might help. Not currently sure what the UDD host is running. [21:16] cjwatson, Until i get some upload rights, UDD is by far the best way to package i've found. If you could backport pristine-tar, that would be great [21:19] UDD is all but unmaintained, I'm afraid, so major problems are unlikely to be fixed. [21:20] cjwatson, I don't know much about coding, but is there anything i can do to help with it? [21:21] Looks like package-import == jubany is running precise, so that would be pristine-tar 1.20ubuntu1. [21:21] How much would be fixed by updating the host to more current packages? [21:21] pristine-tar might be improved, but I doubt much else would change [21:22] Might be worth trying to isolate the particular pristine-tar failures in packages you care about (they may be isolatable by grabbing the bzr branch and trying to use pristine-tar directly) and working out whether they correspond to fixes that have been made since 1.20 that could be SRUed to precise [21:24] ok [21:25] How should i run pristine-tar? i've not used it before [21:36] cjwatson, package-import can't just be upgraded to 14.04? [21:37] Noskcaj: why don't you just upload debdiff instead creating enormous bazaar branches? [21:37] ari-tczew, because it's easier to work with the vcs [21:38] Noskcaj: IIRC you have internet connection, so I think it's easier to upload small debdiff debian -> ubuntu than gigantic branch [21:39] (if example is merge from Debian) [21:40] yeah, but with smaller sized packages (less than 10mb branch) it is IMO a beter workflow to use the bzr [21:41] Noskcaj: ok, you say something about vcs. do you mean gnome packages, or every package? [21:42] i was meaning the bzr vcs [21:42] gnome stuff is often desktop team vcs, which is a bit different [21:42] and ubuntu-gnome is going to be using git by the end of the cycle [21:44] Noskcaj: I expect the problem would be QAing it; I don't think it has a staging site [21:44] (but I know relatively little about it) [21:51] Noskcaj: I don't know what would be easier to use bzr, at least on sponsoring site, but it's only IMHO. [21:57] Noskcaj: what about your MOTU? is the discussion still going on mails?