=== signed8bit is now known as signed8bit_Zzz
=== veebers2 is now known as veebers
=== signed8bit_Zzz is now known as signed8bit
=== signed8bit is now known as signed8bit_Zzz
=== signed8bit_Zzz is now known as signed8bit
=== signed8bit is now known as signed8bit_Zzz
[09:36] <DLange> hey, seems launchpads oops on login with a new "Ubuntu One" user
[09:37] <DLange> OOPS-2a0aa5c5c76f9e2e22eec3792b6854c7, OOPS-f796a40101593cd8a82ccaeef474ba0a and OOPS-bb7136c86865fee389f6366f551afd43 was me
[09:37] <ubot5> https://oops.canonical.com/?oopsid=OOPS-2a0aa5c5c76f9e2e22eec3792b6854c7
[09:37] <ubot5> https://oops.canonical.com/?oopsid=OOPS-f796a40101593cd8a82ccaeef474ba0a
[09:37] <ubot5> https://oops.canonical.com/?oopsid=OOPS-bb7136c86865fee389f6366f551afd43
[09:38] <DLange> to these ^ I can identify with the same "Ubuntu One" OpenID but can't see them (rights issue).
[10:22] <nacc> interesting question about a debian srcpkg's publishing history: https://launchpad.net/debian/+source/isc-dhcp/+publishinghistory; 4.2.2.dfsg.1-5 was published twice into debian/sid (2012-04-29 and 2013-01-19) and additionally the second publication came after 4.2.4-4 in debian/sid. Versions going backwards is not necessarily unseen -- but having the same version show up twice in the same series/pocket is
[10:22] <nacc> new to me.
[10:58] <cjwatson> wgrant: Could you have a look at DLange's question above?  Seems to be something to do with SSO accounts created for an email address that previously had an auto-created Person row due to an auto-import of a Debian package
=== dpm is now known as dpm-lunch
=== signed8bit_Zzz is now known as signed8bit
=== dpm-lunch is now known as dpm
=== sakrecoer is now known as sakrecoer_
=== JanC is now known as Guest24709
=== JanC_ is now known as JanC
=== sidi_ is now known as sidi
=== pavlushka_ is now known as Guest91131
=== Guest91131 is now known as pavlushka
[21:47] <dobey> wgrant: is it me, or is ppa binary publishing extremely slow lately?
[21:53] <dirtside> Random question: if I hypothetically have the same package available from multiple sources (say, two PPAs), then "apt-cache showpkg [packagename]" will list the various versions that are available, and the lists files (on my local system) that contain the versions' metadata. If my goal is to find out which PPA each version came from, what's the simplest way to do that? The lists file typically has a very long name that seems to include a normalized versio
[21:53] <dobey> apt-cache policy ?
[21:54] <dirtside> :o
[21:54] <dirtside> nifty, thanks
[21:56] <dirtside> So at least that provides the repository archive root URL, which is a lot easier to figure out the PPA name from, since PPAs always map to ppa.launchpad.net URLs the same way, right? ppa:FOO/BAR always maps to ppa.launchpad.net/FOO/BAR/ubuntu ?
[21:57] <dobey> i don't recall
[21:57] <cjwatson> Yes
[21:57] <dobey> but something like that yes
[21:58] <dirtside> and when I run apt-cache policy, it lists a number before each deb line... most of them are "500" but a few are "100". I'm guessing this is some kind of priority level, with higher numbers having higher priority?
[22:02] <cjwatson> "man apt_preferences" explains those
[22:03] <dirtside> cool, thanks. So many apt commands...