=== maclin1 is now known as maclin === Ursinha-afk_ is now known as Ursinha === Ursinha is now known as Guest82331 === maclin1 is now known as maclin === cprov_ is now known as cprov === psivaa_ is now known as psivaa === czchen_ is now known as czchen === broder_ is now known as broder === Guest82331 is now known as Ursinha === Ursinha is now known as ursula1234 === yena_ is now known as yena === ursula1234 is now known as Ursinha === jefferai_ is now known as jefferai === elijah_ is now known as elijah === jamesh_ is now known as jamesh [10:50] Is bos01 having a sad or something? [12:08] Laney: apparently nova-compute had segfaulted on several ppc64el compute nodes - IS has recovered it [12:11] cjwatson: Indeed, seems that the instances are picking up builds again, thanks [13:39] <__marco> Good afternoon (UTC+1). I recreated a qemu package but the ppa page says always that a new version is available [13:40] <__marco> 2.0.0+dfsg-2ubuntu1.19 vs 2.0.0+dfsg-2ubuntu1.20 [13:40] <__marco> the *ubuntu1.19 is the latest relased [14:00] __marco: Yes, it's currently not pocket-aware so it doesn't distinguish 2.0.0+dfsg-2ubuntu1.19 in -updates from 2.0.0+dfsg-2ubuntu1.20 in -proposed [14:00] I think it's still worth knowing that there's a newer version on its way though [14:01] Depends what you're doing [14:04] you should also use nextver~myppa1 instead of just nextver, for ppa builds, generally [14:08] <__marco> dobey: https://launchpad.net/~marco-giusti/+archive/ubuntu/qemu I think I already do [14:08] <__marco> 2.0.0+dfsg-2ubuntu1.19vde1 [14:11] __marco: no, that's current version plus appended string. should use 1.20~vde1 there instead (but that is still older than 1.20) [14:11] <__marco> cjwatson: Yes, I am definitely interested in new versions. Is there a notify mechanism? [14:12] __marco: Not directly in Launchpad; the best you can do that I can think of is subscribe to trusty-changes@lists.ubuntu.com and filter. [14:12] <__marco> dobey: I am following https://help.launchpad.net/Packaging/PPA/BuildingASourcePackage#versioning but I did not yet explored the Ubuntu packaging guide [14:12] dobey: That depends on semantics. Neither is objectively better in all cases. [14:13] <__marco> cjwatson: no problems. I did not aware of it [14:13] backport of 1.20 => 1.20~, 1.19 plus extra patches => 1.19 or 1.19+ [14:13] <__marco> anyway, thanks both [14:13] well, 1.19vde1 conflicts with the possibility of an update in ubuntu being 1.19.1 for example [14:14] <__marco> it is ubuntu1.19 [14:14] <__marco> I don't think will be a ubuntu1.19.1 even [14:14] <__marco> ever* [14:16] in this specific case perhaps not, but i'm talking about the general case [14:26] dobey: no, it doesn't [14:26] $ dpkg --compare-versions 1.19vde1 lt 1.19.1; echo $? [14:26] 0 [14:27] if that were a problem then Ubuntu's "append ubuntu1 etc." versioning scheme would be broken relative to Debian in a way that it is not [14:27] oh [19:28] hello, is it intended that one can enable support for ppc64el? [19:28] ... for personal PPAs [20:41] ricotz: http://blog.launchpad.net/ppa/ppas-for-ppc64el <- yes [20:51] Laney, ah, ok [22:18] Hello, does Launchpad support PPC packages? [22:18] for PPA's [22:18] ki7mt: ppc64el, but not 32-bit powerpc yet. [22:18] Hopefully soon. [22:20] ki7mt: I went into some detail on http://blog.launchpad.net/ppa/ppas-for-ppc64el about what the blockers are [22:22] Hi guys, ok, thanks. I had someone ask me about ppc64 package support, and to be honest, ppc is a bit out of my Wheelhouse. [22:25] ki7mt: ppc64el is easy, just hit "Change details" on your PPA. Ubuntu doesn't support plain ppc64, and LP doesn't support 32-bit powerpc PPAs yet. [22:26] wgrant, Would ppc64el work with: [ uname -r = 4.2.0-16-powerpc64-smp ] boxe, it's G5 iMac running Ubuntu-Mate I believe. [22:26] ki7mt: That's 32-bit powerpc (just with a 64-bit kernel), which we don't have PPA support for yet. [22:27] wgrant, Ok, thanks for the help. [22:30] wgrant, If I enable the ppc64el under "Change Details", do I need to bump the PPA version to generate the package? [22:32] ki7mt: Builds won't automatically be created. You can either upload a new version or copy the package over itself to create the new builds. [22:33] wgrant, ok, thanks.