[12:05] <kalon33> hello all, I think there's trouble with PPA publishing...
[12:06] <kalon33> I've some packages waiting to be published after building for one hour now, and some are marked as pending...
=== Nigel_ is now known as G
=== Guest40987 is now known as issyl0
[14:13] <Laney> how can i determine in the api if a publication record was caused by a copy from a previous distroseries?
[14:14] <Laney> given an SPPH
[16:43] <Philip5> maybe slightly off topic but anyway, after i updated to oneiric and use pbuider and make a new container with create then is pulls repositories from both i386 and amd64 sources even though i create a amd chroot. anyone experienced this too?
[16:44] <Philip5> are there any changes to pbuilder or is this a bug? maybe i miss something??
[16:44] <Philip5> a amd64 chroot...
=== micahg_ is now known as micahg
[17:30] <geser> Philip5: might be related to multi-arch (being able to install i386 and amd64 debs)
[17:31] <Philip5> geser: i figured that too now when i did some reading
[18:44] <jbendotnet> I'm tryig to compile nginx on lucid with debug support, but it's erroring when I try
[18:44] <jbendotnet> http://pastie.org/2707192
[18:51] <geser> you sure you try to install the right -dbg package? from the name and version you try to install nginx-dbg from the archive while the latest nginx package in e.g. oneiric build now a nginx-light-dbg package
[19:04] <jbendotnet> ahh
[19:04] <jbendotnet> obviously!~
[19:05] <jbendotnet> geser: so something like aptitude install nginx-dbg-1.0.8-0ppa1~lucid ?
[19:09] <geser> did you check that the source package for it, does really build a nginx-dbg package?
[19:11] <geser> which ppa is it you use?
[19:16] <jbendotnet> geser: https://launchpad.net/nginx
[19:19] <geser> jbendotnet: install either nginx-light-dbg or nginx-full-dbg depending on if you use nginx-light or nginx-full (there is no nginx-dbg anymore, see https://launchpad.net/~nginx/+archive/stable/+sourcepub/1970439/+listing-archive-extra)
[19:20] <jbendotnet> geser: I still get problems, tried that first - hmm
[19:23] <geser> the same problem or an other one?
[19:31] <jbendotnet> http://pastie.org/2707433
[19:32] <jbendotnet> I tried removing nginx-light, but that failed as well
[19:32] <jbendotnet> geser: cause it wents to remove nginx completely
[19:34] <geser> if you have nginx-light installed then install nginx-light-dbg (nginx-light and nginx-full differ in the set of included modules)
[19:35] <jbendotnet> geser: removed nginx then reinstalled
[19:36] <jbendotnet> geser: am a bit rusty
[19:36] <jbendotnet> sorry
[19:36] <jbendotnet> (I blame my broken ankle affecting my brain
=== jtr is now known as jtr__
=== ampelbein_ is now known as Ampelbein
[23:47] <micahg> lifeless: do you know anything about syncs not reaching -changes or being horribly delayed, I syncd stuff about 18 hours ago and it still hasn't shown up on the list
[23:48] <wgrant> micahg: eg?
[23:48] <micahg> wgrant: using syncpackage which uses the new sync API
[23:48] <wgrant> Yes, but which packages?
[23:49] <micahg> wgrant: https://launchpad.net/~micahg/+synchronised-packages
[23:55] <arand> I have a package in my PPA, in status FULLYBUILT_PENDING, and has been so for about 12h, is there something up with publication on lp? since I noticed the distro-info i386 package of ubuntu also looking like it's in a similar state, or is this completely unrelated?
[23:56] <lifeless> arand: PPA and main archive have different publisher instances (are on different machines) so likely unrelated
[23:57] <arand> The ppa package is kinda unimportant, just using it for syncsource script testing, but I found it unusual though..