=== Mapley is now known as rainbowdash^
=== rainbowdash^ is now known as ^rainbowdash
=== ^rainbowdash is now known as Mapley
=== freeflying is now known as freeflying_away
=== henrix_ is now known as henrix
[04:04] <Azendale> how hard is to it get a new stable version of a package in trusty at this point?
[04:09] <Azendale> I'm trying to make a ejabberd juju charm, and in the latest stable version they switch to the yaml format for the config file. So, if I use an older version, I'll probably need to take a couple of hours to build an Augeas lens that won't be of much help when the new stable version ends up in Ubuntu. I'm not in a rush to have the charm ready, I don't mind if it is only available on Trusty
[04:19] <JanC> Azendale: probably depends on whether it's available in Debian
[04:21] <Azendale> JanC: It looks like the package is also in debian, it looks like they have version 2.1.11-1, the ejabberd site says 13.10 is the latest stable version
[04:22] <JanC> they changed version numbering?
[04:24] <Azendale> JanC: It looks like it. http://www.ejabberd.im/ejabberd-13.10 says that "ejabberd 2.1.x support is discontinued" and mentions 13.03 and 13.06 as previous releases
[04:25] <Azendale> JanC: So it would have to be updated in debian first I assume?
[04:26] <JanC> that would be the easiest way, yes
[08:20] <maxiaojun> http://packages.ubuntu.com should defaults to saucy now?
[09:14] <tumbleweed> maxiaojun: I waved that at Rhonda, and she's fixed it
[09:52] <pippo> salve
[09:52] <jkitchen> obey
=== funkyHat1 is now known as funkyHat
[11:38] <fhf> Hi guys. Sorry to bother you but I have a problem with packaging python software. I follow this quide: http://developer.ubuntu.com/packaging/html/packaging-new-software.html and there is an error http://paste.ubuntu.com/6393308/ with setup.py: http://paste.ubuntu.com/6393305/ anyone know how to package it propertly?
[11:50] <cjwatson> fhf: Looks like resources/fbmessenger.png doesn't exist.  Is the path written in setup.py wrong?
[11:54] <fhf> cjwatson: its confusing becouse file is there already. I have tried moving and changing path in setup.py but without success ls -lR: http://paste.ubuntu.com/6393363/
[11:59] <cjwatson> fhf: That's indeed confusing.  Unfortunately I don't have a lot of time right now as I need to pack, but perhaps if you put your source package so far up for download somewhere, somebody else would be able to download it, reproduce the failure, and figure out what's going on.
[11:59] <cjwatson> (I suspect it will be reasonably easy for somebody experienced to sort out that way)
[12:00] <fhf> cjwatson: I'm trying to pack fbmessenger from https://github.com/oconnor663/fbmessenger/
[12:00] <cjwatson> Failing that you might try applying strace and see what file it's actually looking for and in what working directory
[12:00] <cjwatson> Yeah, don't talk directly to me, I'm going now :)
[12:00] <fhf> ok anyway thanks ;)
=== freeflying_away is now known as freeflying
[15:22] <fhf> join #ubuntu-pl-loco
[15:23] <fhf> damn typo
[19:07] <Noskcaj> When should automake 1.14 be ready for stuff to build against? A number of FTBFS packages need it
[19:13] <slangasek> why would it not be ready now?
[19:22] <Noskcaj> slangasek, A number of packages FTBFS because they say they need it. I assume it's something in autoreconf. i'll find an example
[19:26] <Noskcaj> https://launchpadlibrarian.net/155725612/buildlog_ubuntu-trusty-i386.lbzip2_2.3-1_FAILEDTOBUILD.txt.gz
[19:38] <slangasek> Noskcaj: that package has a buggy versioned dep on automake.
[19:39] <slangasek> (it's missing an epoch, so *all* versions of automake satisfy it)
[19:39] <Noskcaj> ok. Thanks for the info. I think i saw the issue elsewhere, but the same cause.
[19:44] <Noskcaj> Can someone rebuild xfce4-whiskermenu-plugin on arm64? The chroot broke
=== freeflying is now known as freeflying_away
=== freeflying_away is now known as freeflying
=== freeflying is now known as freeflying_away
=== freeflying_away is now known as freeflying