=== Logan_ is now known as [Live] === daker_ is now known as daker [03:55] anyone familiar with django-openid-auth? i can't figure out why openid.return_to for login.launchpad.net is set to http when my referer is set to https? === Logan_ is now known as log === log is now known as Logan_ === elopio_ is now known as elopio === lool- is now known as lool [12:02] hi, I was trying to create a project on launchpad for libkdcraw, but it tells me that the project name is already taken [12:02] https://launchpad.net/libkdcraw doesn't exist though [12:08] yofel: You should be able to create it now [12:08] ok, thanks! [15:02] wgrant: https://launchpad.net/ark is another case [15:17] Is there a way, when listing dependency versions, to provide a series agnostic version number? [15:27] Like, if I'm building packages with version numbers something like 1.3.1-1ubuntu1ppa1~raring1. How to reference this in a (>= 1.3.1-1) method without adding the raring1 in it. [15:33] Well, (>= 1.3.1-1) is greater-than-or-equal, so that's good enough. [15:33] Depends exactly what your dependency is supposed to mean. [15:33] If you just want "at least this upstream version", then leave it as "(>= 1.3.1)". [15:41] Well, I want to try to say something like (= 1.3.1-1ubuntu1ppa1~any) [15:41] is that possible? [15:54] Dougie187: Exactly what are you trying to express here? [15:55] cjwatson: that I want it to use version 1.3.1-1 of the library, but whatever series is available. [15:55] I'm trying to build packages for static libraries (I didn't write them, so they don't have options for shared libraries) [15:55] You can do "foo (>= 1.3.1-1), foo (<< 1.3.1-1.1)" [15:56] What's << mean? [15:56] But you should think about why/whether the exact packaging revision is important [15:56] Less than [15:56] ok [15:56] See http://www.debian.org/doc/debian-policy/ch-relationships.html [15:57] You should also think about whether -1ubuntu1 and -1ubuntu2 (say) might be different [15:57] In which case you'd want "foo (>= 1.3.1-1ubuntu1), foo (<< 1.3.1-1ubuntu2)" or similar [15:58] Ok [15:58] Thanks [15:58] However I'm slightly confused why static libraries mean you need this - usually things built against static libraries don't depend on those libraries at all, because they effectively include a copy of them [15:58] well, one of them is a static library that is build against another static library [15:59] So library A effectively includes a copy of library B; still no dependency involved there [15:59] And I wanted to build the package knowing which version of the static library it was built with [15:59] That's not an appropriate use of Depends, if that's all it is [15:59] Oh ok [15:59] There's a Built-Using field which can be used to document that kind of thing (although nothing in Ubuntu currently pays attention to it) [15:59] Ok [16:00] http://www.debian.org/doc/debian-policy/ch-relationships.html#s-built-using [16:00] Thanks [16:00] I have to run now though. But I'll read it when I get back === hggdh_ is now known as hggdh