[00:06] <nacc> Pharaoh_Atem: sigh, http://trac.roundcube.net/ticket/1490544
[00:06] <nacc> not packaged yet either, will need to figure that out tmrw
[00:08] <slangasek> nacc: pictor, your patch is against a stale version; there's a 2.35-0ubuntu1 package that you're in the changelog of
[00:08] <nacc> slangasek: ha! ok ... let me check that, sorry
[00:10] <slangasek> nacc: likewise, simplesamlphp is against a stale version
[00:11] <slangasek> nacc: and I would dearly love for further debdiffs to be in a bug per package instead of in one bug report with 800 tasks... at some point LP is going to flip the table on us
[00:12] <nacc> slangasek: ok, i can do that from now on ... sorry
[00:12] <nacc> slangasek: so looks like roundcube 1.2 (current at beta) is teh only version that supports php7 ... similar issue as drupal7, afaict
[00:14] <nacc> kirkland: for the pictor upload (2.35-0ubuntu1) why did you keep php5 compat in the control file? there is no php5-imagick, e.g., in xenial
[00:14] <nacc> kirkland: are you ok if we drop that compat?
[00:18] <slangasek> nacc: my view is that if it's in universe and it doesn't support php7, it's expendable and can be cut from release.  I am not, however, the product manager for Ubuntu Server.  From an archive/release POV, I'm perfectly willing to take a roundcube beta into the release instead, if a) someone is willing to do the work to prepare that package and make it work, b) upstream isn't going to yell at us for
[00:18] <slangasek>  including their beta, c) any requests for an update ...
[00:18] <slangasek> ... from the beta to the final release post-16.04 follow the SRU process
[00:22] <nacc> slangasek: yep, understood. I think there are a class of applications that simply aren't going to be updated; but roundcube is making progress it seems like. I'll take a look at the packaging requirements tmrw
[00:23] <nacc> slangasek: updated simplesamlphp debdiff
[00:23] <nacc> slangasek: pictor may be fine as-is, depends on what kirkland wants to do
[00:24] <slangasek> nacc: the | php5 stuff shouldn't break the package, if there were no changes to the actual contents
[00:27] <nacc> slangasek: it shows up in http://people.canonical.com/~ubuntu-archive/nbs.html
[00:27] <nacc> and i was aksed to fix that
[00:27] <slangasek> nacc: well, when we remove php5 from the archive, it will not show up there anymore ;)
[00:28] <nacc> won't it? the pictor package will still depend on php | php5, php-imagick | php5-imagick ?
[00:28] <slangasek> nacc: this is a limitation of nbs, it doesn't know how to unpick alternative dependencies
[00:28] <nacc> slangasek: ah ok, i wasn't sure, yeah, it's purely an alternative for that one
[00:29] <nacc> the others are real and fixed in today's set of patches
[00:29] <slangasek> if that's the only remaining revdep of php5-imagick, and pictor depends php-imagick | php5-imagick, we can pull it already
[00:29] <nacc> yep, afaict that's it and how it is
[00:30] <slangasek> nacc: php5-imagick removed from xenial
[00:44] <slangasek> doko: python3.5 - why bump libmpdec_version instead of removing this check from the testsuite? why is python hard-coding a requirement of a matching minor version of libmpdec?
[00:51] <nacc> slangasek: thanks!
[01:36] <slangasek> nacc: should simplesamlphp's bin/memcacheSync.php have been updated?
[02:57] <karstensrage> hi
[02:57] <karstensrage> how does something from debian packaging get into ubuntu
[02:57] <karstensrage> for example if a debian package is new
[02:58] <karstensrage> how would it get into 14.04?
[03:02] <infinity> karstensrage: You wouldn't, 14.04 is a stable release.
[03:02] <infinity> karstensrage: But we can get it into 16.04
[03:03] <infinity> (And then you could perhaps request a backport)
[03:04] <karstensrage> how do i do that
[03:04] <karstensrage> has 16.04 synced to debian yet?
[03:06] <infinity> karstensrage: I don't know what package you're asking about...
[03:10] <karstensrage> can i pm?
[03:11] <infinity> Public conversations work fine.
[03:11] <Unit193> Because of your asking, I requested a sync. :3
[03:12]  * Unit193 waits for the day infinity kills him. :D
[03:17] <karstensrage> infinity, https://packages.debian.org/testing/libs/libufpidentity1
[03:17] <karstensrage> there is another one coming too, but its stuck in mentors
[03:18] <karstensrage> hi Unit193
[03:19] <infinity> karstensrage: Synced to 16.04
[03:19] <karstensrage> it is?
[03:19] <infinity> karstensrage: When the mentors one clears Debian NEW, let me know and I'll grab that too.
[03:19] <karstensrage> alright? can i see that?
[03:19] <karstensrage> and how do i ask for a backport for 14.04?
[03:20] <karstensrage> thank you so much
[03:20] <infinity> https://launchpad.net/ubuntu/+source/identity4c/1.0-1
[03:20] <infinity> karstensrage: To request backports, you need to talk to the backports folks.
[03:21] <infinity> karstensrage: https://wiki.ubuntu.com/UbuntuBackports
[03:22] <karstensrage> ok thank you
[03:29] <karstensrage> infinity, how long do i have for clearing Debian New
[03:29] <infinity> karstensrage: Well, we release 16.04 in under a month.  So, that long.
[03:29] <karstensrage> hmmm
[03:30] <karstensrage> ill do my best
[03:42] <karstensrage> oh infinity did that pull in the devel package too?
[03:42] <karstensrage> dev package?
[03:44] <karstensrage> oh yes
[03:44] <karstensrage> i see thank you
[03:56] <karstensrage> whats a good candidate for the reasoning part?
[03:56] <karstensrage> just want new functionality on 14.04?
[03:56] <karstensrage> and possibly 12.04 since there are still machines out there that havent updated?
[05:25] <ilhami> hey
[05:25] <ilhami> Has OTA 10 been released yet by Canonical?
[06:14] <slangasek> nacc: so, the simplesamlphp diff switches a dep to php-mhash, which doesn't exist?
[06:14] <slangasek> nacc: but neither does php5-mhash
[06:17] <infinity> slangasek: mhash is builtin to all SAPIs (for both 5 and 7.0)
[06:17] <infinity> So that's a useless dep.
[06:19] <slangasek> ok, so it was probably a legacy provides
[09:13] <LocutusOfBorg> hi folks, do you have any news about glibc/binutils/powerpc breakage?
[09:14] <LocutusOfBorg> ginggs, I found your chat, but I didn't see any answer :(
[10:03] <infinity> LocutusOfBorg: What glibc/binutils/powerpc breakage?
[10:04] <LocutusOfBorg> infinity, nobody can install fpc on powerpc
[10:04] <LocutusOfBorg> simple as that
[10:04] <infinity> And this is glibc's fault somehow?
[10:04] <LocutusOfBorg> ginggs, did some debugging
[10:04] <LocutusOfBorg> the postinst script has a command that triggers a SEGFAULT
[10:05] <LocutusOfBorg> and downgrading glibc fixes the issue
[10:05] <LocutusOfBorg> let me find the bits, just a second
[10:05] <LocutusOfBorg> [17:20:25] <ginggs> doko, infinity, LocutusOfBorg: I've confirmed the
[10:05] <LocutusOfBorg> problem with installing fpc 3 on powerpc is related to glibc 2.23.
[10:05] <LocutusOfBorg> After downgrading  libc6*, gcc* and locales, fp-compiler installs just
[10:05] <LocutusOfBorg> fine. Any ideas?
[10:06] <LocutusOfBorg> "I get the same access violation just running 'fpcmkcfg-3.0.0'.
[10:06] <LocutusOfBorg> And even just asking for help segfaults."
[10:06] <infinity> Hrm.  No ideas, but I can look into it later.
[10:07] <LocutusOfBorg> you can just call that "fpcmkcfg-3.0.0 -h" command
[10:07] <infinity> Right.  I'll give it a stab later.  It's almost certainly fpc's fault, not glibc's, but I'll need to dig and sort out why to prove that theory. :P
[10:07] <LocutusOfBorg> the problem is: fpc doesn't build on powerpc anymore because it depends on itself
[10:07] <Unit193> zigo: python-googleapi has a few incompatibilities with the python-oauth2client now in xenial.
[10:07] <infinity> (And it needs fixing either way)
[10:08] <LocutusOfBorg> https://launchpad.net/ubuntu/+source/fpc
[10:08] <zigo> Unit193: Oh... :/
[10:08] <infinity> LocutusOfBorg: Yeah, I know, I have the build log open.
[10:08] <LocutusOfBorg> thanks!
[10:08] <infinity> LocutusOfBorg: Like I said, I'll look later.
[10:08] <Unit193> zigo: New upstream fixes it at least..
[10:08] <infinity> LocutusOfBorg: I'd like to understand why it broke before I just go and rebootstrap it.
[10:08] <LocutusOfBorg> I'm happy to fix fpc sure, but I think I won't be able to do it alone, right?
[10:08] <infinity> Cause if it's using internal symbols or something, it should stop.
[10:08] <LocutusOfBorg> thanks a lot, funny enough it was working with the older glibc :)
[10:08] <LocutusOfBorg> thanks for giving a shot!
[10:09] <ginggs> infinity: thanks. FWIW with the new glibc, I was able to install fpc 2.6.4 from wily but building 3.0.0 failed with the same access violation at 99% :(
[10:09] <zigo> Unit193: I'm not the maintainer of it, so maybe you could ping Laszlo Boszormenyi, he's usually very responsive.
[10:09] <zigo> (and maintains a lot of stuff there...)
[10:09] <LocutusOfBorg> that fpc has important fPIC fixes on arm* I need them, because they are a big regression compared with 2.6.4, and fixes hedgewars
[10:09] <Unit193> Unfortunately and more importantly to me, broke gcalcli too. ;/
[10:10] <infinity> LocutusOfBorg: Ahh, well, wouldn't want hedgewars to be broken. ;)
[10:10] <LocutusOfBorg> yeah, nothing is more imporant in life than games :)
[10:10] <infinity> LocutusOfBorg: I'm about to take a long weekend, but I might poke fpc when bored.
[10:10] <infinity> I vaguely recall the last time I rummaged around in fpc's guts.
[10:10] <LocutusOfBorg> thanks! and happy Easter, I'll be taking a rest too :)
[10:11] <LocutusOfBorg> s/rest/helpwifeincookingalotofstuffforeaster/
[12:30] <mterry> doko: no they aren't stuck anymore, thanks
[12:42] <Laney> Anyone know where I can find langpack generation logs?
[12:42] <Laney> or another way that I can get a list of packages that have their translations put in there
[12:50] <Laney> aha I found mapping.txt
[14:05] <superm1> infinity: since beta2 is out no concerns from me in unblocking that mysql-5.7 out of proposed
[14:05] <superm1> i can sort out fallout in the myth* stuff now
[14:20] <Skuggen> superm1: Nice. We also need to fix some test failures with dbconfig-common for it (and redmine, but I'm guessing those can also be traced to dbconfig)
[14:30] <ginggs> doko: julia has been FTBFS on armhf for several weeks, I've just tried downgrading to gcc-5 5.3.1-3ubuntu1 (where I know I definitely built before) and it builds fine. What can I do further?
[14:31] <hikiko> infinity, slangasek ping
[14:32] <hikiko> Program received signal SIGPIPE, Broken pipe.
[14:32] <hikiko> 0x00007f82e0535417 in __libc_writev (fd=50, vector=
[14:32] <hikiko>     at ../sysdeps/unix/sysv/linux/writev.c:49
[14:32] <hikiko> the x crash
[14:33] <hikiko> compiz didn't crash it crashes later because of x
[14:33] <superm1> Skuggen: http://paste.ubuntu.com/15496370/
[14:33] <superm1> Skuggen: that's with the stuff in proposed, not sure where that header is supposed to be coming from
[14:34] <Skuggen> Hm. Could you check what's in include/mysql/mysql? There's some mess with the header layout the devs haven't gotten around to clean up yet (though I don't think it should have been moved)
[14:34] <hikiko> sorry :)
[14:35] <hikiko> wrong signal
[14:35] <hikiko> that's earlier :p
[14:35] <superm1> Skuggen: looks to be in that directory
[14:35] <superm1> http://paste.ubuntu.com/15496401/
[14:37] <Skuggen> superm1: But it used to work in 5.6? From what I can see in the source the file is in the same place for 5.6.28
[14:37] <superm1> Skuggen: never caused build failures previously
[14:37] <superm1> so maybe the path declared in /usr/include/mysql/mysql/client_plugin.h changed?
[14:42] <superm1> Skuggen: from what i see in 5.5 (on 14.04 box) client_plugin.h wasn't included in /usr/include/mysql/mysql.h, so that's the part that's newer
[14:42] <superm1> don't have a 5.6 handy ATM
[14:43] <Skuggen> Ah, no it's not included in 5.6
[14:44] <Skuggen> https://github.com/ltangvald/mysql-5.6/blob/master/include/mysql.h
[14:46] <Skuggen> If you add include/mysql on the include path, does it work?
[14:47] <superm1> yes that works
[14:48] <superm1> the part that broke for me was this is how a configure script was testing things
[14:51] <Skuggen> Yeah, it's kind of a mess the way the includes are structured right now :|
[15:10] <nacc> slangasek: ah sorry, thanks for catching that!
[15:14] <nacc> slangasek: we can probably do a best effort here, if you're ok with an addition fix for simplesamlphp to suggest `phpenmod -s cli memcache`, iiuc
[15:14] <nacc> Pharaoh_Atem: --^ is that rigth?
[15:27] <nacc> Pharaoh_Atem: and independently, how well do you know horde? :)
[15:28] <nacc> Pharaoh_Atem: nm on the latter
[16:17] <barry> slangasek: i think we should ignore pbgenomicconsensus amd64.  retries don't help but local adt-runs in xenial-proposed chroots always pass for me
[16:17] <barry> slangasek: then there's python-pbh5tools; pretty much same deal
[16:30] <nacc> slangasek: re: LP: 1562060, i tested that the roundcube 1.2~beta installs and seems to run (I don't have an IMAP server setup so can't test it further)
[16:49] <karstensrage> infinity, how come it looks everything has been published but when i search for the package here https://launchpad.net/ubuntu/xenial it doesnt show up?
[16:50] <karstensrage> infinity, also do i have to woo some sponsor for a backport bug or are they just picked up eventually?
[17:21] <nacc> karstensrage: hrm? https://launchpad.net/ubuntu/xenial/+search?text=libufpidentity1
[17:23] <nacc> slangasek: fyi, I think with LP: #1562090 just filed, the horde stuff stuck in proposed should pass its tests
[17:23] <nacc> i'll keep working through the rest of horde
[17:34] <Pharaoh_Atem> nacc: on the former, that looks right to me
[17:34] <nacc> Pharaoh_Atem: ok, will send a patch, thanks
[17:35] <Pharaoh_Atem> on the latter, I have little clue about Horde :/
[18:54] <jdstrand> cjwatson: fyi (I don't need anything right now), bug #1562118
[20:15] <slangasek> hikiko: did you get a full backtrace under gdb of the crash? 'bt full'.  also are you sure it was the SIGPIPE that killed the process, and that X didn't handle that SIGPIPE later?
[20:19] <slangasek> barry: pbgenomicconsensus, you probably can't reproduce the failure because you're testing with different versions of packages than what the autopkgtest infrastructure does.  I'm guessing you're doing a run with -proposed versions of packages, rather than using python-pysam 0.7.7-1ubuntu1 like the log shows?  So, it's possible to skip this test failure for python-setuptools since we know python-set
[20:19] <slangasek> uptools isn't the cause, but please follow up on ...
[20:19] <slangasek> ... python-pysam because this indicates real bugginess currently in xenial
[20:34] <nacc> slangasek: looks like moodle is similar to drupal and others ... working on it now, had to fix the watch file too :/
[21:07] <slangasek> barry: there, pbgenomicconsensus no longer a failed test ;)
[21:07] <slangasek> nacc: hehe, enjoy...
[21:08] <slangasek> nacc: LP: #1562090 uploaded, which horde tests do we want retried once that's published?
[21:09] <nacc> slangasek: sorry, we'll need that one and the others i submitted today, wnat me to give you the list? I think i subscribed you to all of htem?
[21:09] <nacc> turba is the big one, it seems like (affecting a bunch of other packages that is)
[21:10] <slangasek> nacc: if you subscribed me then the list is in my inbox.  ok, from your earlier comment I understood that 1562090 was the only one needed for unblocking, but yes I had seen the turba failures and wondered how -passwd was going to unblock that.  I'll have a look, though I'm actually off today so no promises that I'll get through the stack before Monday
[21:10] <nacc> slangasek: it's ok, i just  wanted to let you know they were taken care of :)
[21:11] <nacc> slangasek: i'd rather you didn't work today and relaxed!
[21:13] <slangasek> nacc: I relax better with fewer incoming tasks in my inbox ;-)
[21:14] <nacc> slangasek: uhh, unlikely! although on my last check, we were down to 350 packages! these bigger frameworks slow me down, obviously, as pulling in a new version is not the easiest thing
[21:17] <barry> slangasek: magic!
[21:18] <slangasek> barry: python-pbh5tools still broken though, also points to pysam, so retrying with -proposed pysam there as well.  So maybe this unblocks it without hinting, but then python-pysam still needs attention to get it migrated
[21:20] <barry> slangasek: ack
[22:53] <Umeaboy> Hi!
[22:53] <Umeaboy> I made a bugreport about E173 not being able to connect in Xenial.
[22:53] <Umeaboy> Sorry.
[22:54] <Umeaboy> In Wily.
[22:54] <Umeaboy> It works on Xenial.
[22:54] <Umeaboy> Can someone please push an update of NetworkManager and Policykit from Xenial to Wily?
[22:55] <Umeaboy> The problem is at the window to enter the pin code.
[22:55] <Umeaboy> It just won't accept it even thou it's entirely correct.
[23:45] <cjwatson> jdstrand: yeah, hoping to have time to sort that out pretty soon