[00:04] <greg-g> secretlondon: what about just cc-by?
[00:05] <greg-g> that version is making more headway in adoption (from what I've seen)
[00:06] <greg-g> (for blogs by prominent people in academia, and educational resources also)
[00:07] <greg-g> ie: the OpenCourseWare project I work with is all CC-BY (and the code is BSD)
[00:07] <secretlondon> greg-g by is okay, but in free content land we generally prefer by-sa
[00:07] <secretlondon> wikipedia says best practice is to dual license everything as by-sa and gfdl (which is what i do)
[00:08] <greg-g> I thought there was something funky about the gfdl (I don't know what specifically, just a memory I have that I can't place)
[00:09] <secretlondon> greg-g wikipedia would like to move to cc-by-sa tbh.
[00:10] <greg-g> gotcha
[00:10] <secretlondon> the prob with the gfdl is "invariant sections" which are non free, curiously the only docs I've ever seen with invariant sections have been from the free software foundation
[00:10] <greg-g> thats what it was
[00:11] <greg-g> I thought it had to do something with what the FSF was doing, but I wasn't sure so I didn't point any fingers :)
[00:11] <greg-g> wow, move the "to do" to the right place in that sentence
[00:13] <secretlondon> debian sees that as non free
[00:13] <secretlondon> the prob with wikipedia is that once you decide on a license you are kinda stuck with it
[00:13] <greg-g> right
[00:15] <secretlondon> we need the fsf to co-operate as we'd like greater interoperability between the gfdl and cc-by-sa
[00:15] <secretlondon> this is easier said than done
[00:16] <greg-g> heh
[00:16] <greg-g> I can imagine
[00:16] <howapt> all these acronyms really get me going
[00:17] <howapt> please dont stop
[00:17] <greg-g> well, if you have any ideas this summer than you want an insider's view on from CC, let me know, I'll be interning there
[00:21] <secretlondon> greg-g cool!
[00:23] <greg-g> secretlondon: yeah :)  "community development" is what I'll be doing :)
[00:24] <secretlondon> COOL
[00:43] <zyx386> hi
[00:43] <zyx386> what about this bug?
[00:43] <zyx386> #204757
[00:44] <zyx386> i have this problem to
[00:47] <hggdh> bug 204757
[00:52] <bdmurray> zyx386: which problem there seem to be 2 separate bugs in that report, one regarding exim4 and one regarding virtualbox-ose.
[02:43]  * Hobbsee wonders when the bugsquad will write documentation, or mails to the mailing list, on how they view that MOTU should use launchpad for workflow bugs.
[02:45] <artfwo> why cannot a MOTU bug just be tagged with a "motu-workflow" tag?
[02:47] <Hobbsee> artfwo: because tags are evil, can't be set when filing a bug on the standard UI, add to the tag cloud, mainly.
[02:48] <Hobbsee> and, iirc, aren't shown on the email interface either.
[02:48] <Hobbsee> if they are in the bugmail, i don't think they're in the headers, which makes filtering harder.
[02:48] <artfwo> yep, indeed
[02:49] <Hobbsee> if those bugs actually got fixed, then yes, that probably is a decent solution - if the bugsquad could cope with having bugs it was specifically not to touch, which i've already been told demoralises new bugsquadees, because they can't touch everything, and do what they like to it.
[02:53] <artfwo> Hobbsee: do you have an url with an example motu bug?
[02:54] <Hobbsee> artfwo: https://bugs.launchpad.net/ubuntu/+source/secvpn/+bug/154730
[02:54] <Hobbsee> artfwo: for more, check things with ubuntu-archive or ubuntu-universe-sponsors subscribed.
[04:03] <bdmurray> Hobbsee: tags do show up in bug e-mail headers now in the X-Launchpad-Bug-Tags header to be exact
[04:03] <Hobbsee> bdmurray: ahh, this must be new.  that's a good start.
[04:04] <bdmurray> yeah, it came out one of the last couple of releases
[04:05] <ScottK> Can tags be added via the email interface?
[04:06] <bdmurray> ScottK: it looks like it 'tag foo bar' or 'tag -foo'
[04:07] <ScottK> Then if it was agreed, it's be trivial to do for syncs since those are mostly done with requestsync, but most other workflow bugs are hand written.
[04:08] <ScottK> If we all agreed that the priority was for making things easy for new triagers at the expense of making more work for developers, I don't see any problem with a tag approach.
[10:15] <thekorn> good morning
[10:16] <james_w> hi thekorn
[10:16] <thekorn> bdmurray, can you please renew my ubuntu-bugcontrol membership
[10:16] <thekorn> hey james_w
[12:51] <askand> Hello, I uploaded a patch to solve a bug on launchpad, what is the next step?
[12:51] <ScottK> askand: What bug?
[12:52] <askand> ﻿ScottK:  bug 89936
[12:52]  * ScottK looks
[12:54] <ScottK> askand: Why do you change meddelande to mail?
[12:55] <ScottK> It seems that you've undone the translation.
[12:56] <askand> ﻿ScottK: hm no..mail is used in Sweden to but it can be used as both plural an singular as opposit to meddelande that has to have meddelanden to be plural
[12:56] <ScottK> I see.
[12:57] <ScottK> askand: First, for those of us who don't speak Swedish it'd be good to note in the bug why you changed the string (what you just told me).
[12:58] <askand> ﻿ ScottK: ok will do, well the reason I changed the string is not that I think mail is better or something but it works good and does not make the program crash
[12:58] <ScottK> askand: Second, the next step would be to integrate the patch into a package update and produce a debdiff.  Are you interested in learning how to do that?
[12:58] <askand> ﻿ ScottK: indeed, eager to learn :)
[12:59] <ScottK> askand: Then you should join #ubuntu-motu and ask for help with that there.  That's a more appropriate channel for packaging discussions.
[12:59] <askand> ﻿ScottK: thanks
[13:35] <rio> https://bugs.launchpad.net/ubuntu/hardy/+source/libgphoto2/+bug/228154 -- Martin wrote he put the fixed version in hardy-proposed, but http://archive.ubuntu.com/ubuntu/pool/main/libg/libgphoto2/ doesn't have it :/
[13:35] <ogra> rio, patience is golden ;)
[13:36] <ogra> it was uploaded less than 1h ago, give it time to build and propagate
[13:36] <rio> time's money :P
[13:36] <ogra> heh
[14:13] <mrooney> hmm, does this affect Ubuntu: http://lists.debian.org/debian-security-announce/2008/msg00152.html
[14:14] <james_w> mrooney: yes, you can expect more information soon.
[14:14] <mrooney> okay, thanks
[14:15] <ogra> fix was uploadeed already, packages are building
[14:15] <mrooney> oh, how impressive
[14:15] <ogra> the USN should come out during the day
[14:17] <ccooke> mm
[14:17] <ccooke> The tool on the Debian link to detect bad keys doesn't work on Hardy
[14:18] <ccooke> I'm looking at it to see why
[14:32] <jarlath> When I've gone as far as I can helping a reporter complete a report, what should I do next? I have such a case here https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/223191
[14:58] <james_w> ccooke:  "close is not a valid DB_File macro at
[14:58] <james_w> /home/pkern/dowkd.pl line 51" ?
[15:00] <ccooke> james_w: that's the problem. Close isn't implemented in DB_File
[15:00] <james_w> ccooke: I just saw that on debian-security@, I haven't tried it myself yet.
[15:00] <james_w> presumably someone will post a fix there.
[15:07] <ccooke> http://paste.ubuntu.com/11851/ - patch for dowkd.pl
[15:08] <ccooke> ... except it isn't the right patch. Doh!
[15:08] <ccooke> Hmm. Looks like it'll be equivalent, anyway.
[15:25] <bddebian> Boo
[15:26] <ogra> bee
[15:26] <bddebian> ;-)
[15:29] <qense> hello
[17:57] <SwedeMike> oki, so openssh-server_1%3a4.6p1-5ubuntu0.3_i386.deb seems to be broken, known problem?
[17:57] <SwedeMike> emplate #4 in /var/lib/dpkg/tmp.ci/templates has a duplicate field "template" with new value "ssh/vulnerable_host_keys". Probably two templates are not properly separated by a lone newline.
[17:58] <seb128> SwedeMike: is that gutsy? in which case yes
[17:58] <SwedeMike> 7.10
[17:58] <SwedeMike> ok.
[17:58] <SwedeMike> goodie.
[17:58] <seb128> SwedeMike: that's being worked
[17:58] <SwedeMike> thanks.
[17:58] <Pici> Is there a bug # for that issue?
[17:59] <seb128> Pici: not sure, that has been mentioned several times on #ubuntu-devel but they didn't give bug numbers
[17:59] <Pici> seb128: Yeah, I looked in that scrollback too
[18:01] <seb128> bug #230003
[18:04] <Pici> seb128: great, thanks.
[18:04] <greg-g> (don't answer if you don't have time/whatever): is that just a 386 issue, it installed fine for me but I'm on amd64
[18:04] <Pici> greg-g: On Gutsy?
[18:04] <greg-g> oh, thats gutsy, nevermind
[18:05]  * greg-g missed the first word of the title of the bug, good job greg-g 
[18:05] <greg-g> :)
[18:06] <seb128> SwedeMike, Pici: they uploaded a gutsy-security fixed version now
[18:06] <Pici> seb128: darn, I *just* had changed the #Ubuntu topic
[18:07] <SwedeMike> seb128: yeah, installed it, seems fine.
[18:07] <SwedeMike> let's see if my laptop works well as well
[18:08] <SwedeMike> seems to work fine as well
[19:17] <rpedro__> hello
[19:17] <marnanel> hello
[19:17] <rpedro__> :)
[19:19] <thekorn_>  /nick thekorn
[19:19] <thekorn_> urgh
[19:19] <bdmurray> heh
[19:19] <rpedro__> I have since the dist-upgrade to hardy, very slow performance in the gnome apps' file open/save dialog, and the alt-f2 Run dialog
[19:20] <rpedro__> they take more than a few seconds after they display, to become usable, which wasn't the case before
[19:21] <rpedro__> I want to report a bug, but don't know exactly what to file it under... :)
[19:26] <qense> Were all the SSH keys in launchpad removed from the profiles?
[19:28] <jdavies> qense: no
[19:29] <Pici> As I understand it, not all ssh keys are comprimised
[19:31] <jdavies> Pici: that didn't stop the alioth guys rm'ing them from existence :)
[19:31] <LimCore> Pici: I wonder how big amount is
[19:32] <thekorn> oh dear, this explains why bzr push/pull does not work for me
[19:32] <qense> your key is vulnerable too!
[19:59] <LimCore> dsa bug... how could this happen
[21:18] <Pici> Hrm.. I guess LP did delete my key.
[21:19] <geser> Pici: your ssh-key? see the openssl USN
[21:21] <Pici> geser: I did, but ssh-vulnkey didnt tell me I was comprimised, and those should have been the same keys.  Oh well.
[21:22] <Nafallo> or the openssh USN :-)
[21:37] <gnomefreak> ssh-vulnkey and -a told me no command found
[21:48] <geser> gnomefreak: openssh-client from -security already installed?
[22:44] <Fallenou> hi, i wanna know if someone experienced a bug like mine : when pluging an ethernet wire , nothing appears in dmesg (no eth link up 100Mbps full-duplex message) and can do nothing with network interface.
[22:45] <Fallenou> i posted this bug : https://bugs.launchpad.net/ubuntu/+bug/230099
[22:45] <asac> Fallenou: gnome/kde?
[22:45] <Fallenou> gnome
[22:45] <Fallenou> but even if i try in a term i got nothing
[22:45] <asac> Fallenou: go to system -> adminstration -> network ... and set your devices to "roaming mode"
[22:45] <Fallenou> with ifconfig, dhclient etc ...
[22:46] <asac> Fallenou: do you use network-manager?
[22:46] <asac> if so, go the "roaming mode" path
[22:46] <asac> at best try that first
[22:46] <Fallenou> yes it is in roaming mode
[22:46] <Fallenou> i tried roaming mode, dhcp mode, static ip mode
[22:46] <Fallenou> but it does not detect when i plug a wire anyway
[22:47] <Fallenou> even if my network configuration is wrong (which is not i did nothing special), it should print something in dmesg when i plug a wire
[22:47] <Fallenou> i tested the same on my laptop under hardy too and it works well
[22:48] <bdmurray> Fallenou: Have you tried checking it with ethtool?
[22:48] <Fallenou> no :o
[22:48] <asac> Fallenou: what are you running? gutsy?
[22:48] <Fallenou> asac < everything is explained in the bug i posted
[22:48] <Fallenou> i am using hardy
[22:49] <Fallenou> it works on feisty, gutsy and windows XP
[22:49] <Fallenou> bddebian < don't know how to use it to check :o
[22:49] <Fallenou> bdmurray * sorry
[22:49] <bdmurray> Fallenou: 'sudo ethtool eth0'
[22:50] <Fallenou> bdmurray do i have to plug the wire to check this ?
[22:50] <bdmurray> It will show whether or not a link is detected
[22:51] <bdmurray> The results of the wire connected and not connected would be interesting
[22:51] <Fallenou> ok i'm gonna test this with and without a wire and post it to launchpad
[22:51] <bdmurray> great thanks!
[22:51] <Fallenou> i'm testing( so i'm gonna disconnect :p)
[22:51] <Fallenou> i'll be back right after the test :)
[22:51] <Fallenou> see you soon
[22:51] <asac> Fallenou: 1st you need to know if you are running network-manager
[22:51] <asac> :(
[22:52] <asac> well ... do what bdmurray says ;)
[22:52] <Fallenou> asac < how to know that ?
[22:52] <bdmurray> asac: Will n-m interfere with ethtool?
[22:52] <Fallenou> i'm running gnome with nb-applet
[22:52] <Fallenou> nm-applet*
[22:53] <asac> Fallenou: yeah. then you definitly need to configure your interfaces as "roaming" ... otherwise nm will not manage your devices at all
[22:53] <asac> paste your /etc/network/interfaces to be sure after that
[22:54] <asac> then run sudo /etc/dbus-1/events.d/25NetworkManager restart
[22:54] <Fallenou> i do all this before testing ethtool ? or after ?
[22:54] <asac> wait a while, plug-in your network device ... wait ... plug out
[22:54] <asac> then post your /var/log/syslog to the bug too
[22:55] <asac> Fallenou: is independent from ethtool i would say
[22:55] <Fallenou> ok
[22:55] <Fallenou> i'm gonna do what you say, so
[22:55] <asac> ethtool just dumps your interface settings
[22:56] <Fallenou> see you in 5 min :p
[23:03] <Fallenou> i'm back
[23:04] <Fallenou> nothing changes in ethtool when i plug a wire
[23:04] <Fallenou> samething in /var/log/syslog
[23:04] <Fallenou> i'm gonna paste everything anyway ...
[23:06] <asac> Fallenou: the idea was to restart network manager ;)
[23:07] <asac> if you did that please attach syslog to bug
[23:07] <Fallenou> yes i restarted the network manager
[23:07] <asac> Fallenou: stupid question ... if you right click on the nm-applet ... is networking enabled ?
[23:07] <Fallenou> yes it is
[23:07] <asac> ok
[23:07] <asac> syslog is the way to go then
[23:08] <Fallenou> http://launchpadlibrarian.net/14504557/syslog-while-pluging-in
[23:09] <asac> well .. thats not the complete syslog
[23:09] <Fallenou> no you want all of it ?
[23:09] <asac> yes
[23:09] <asac> often this is enough, but sometimes there are gems elsewhere ;)
[23:10] <asac> especially i want the full restart cycle ;)
[23:10] <Fallenou> ok i upload the entire file
[23:12] <Fallenou> http://launchpadlibrarian.net/14504616/syslog
[23:13] <Fallenou> you have some logs about me pluggin in my USB key to get the content of the log uploaded on the web ^^
[23:13] <asac> Fallenou: right on top network manager successfully connects
[23:13] <asac> hmm well it tries to
[23:14] <Fallenou> all before May 14 23:30:55 fixe avahi-daemon[5378]: Registering HINFO record with values 'I686'/'LINUX'. ?
[23:15] <Fallenou> yea i see it in the log .... i 'm missing something ...
[23:15] <asac> Fallenou: i suspect that your dhcp server is not running
[23:15] <Fallenou> hum don't you think it would be a good idea to reboot with the wire plugged and to paste sur syslog without any command ?
[23:16] <asac> Fallenou: does it work if you boot with wire plugged`?
[23:17] <Fallenou> no it didn't :o
[23:17] <asac> anyway ... you don't get an ip
[23:17] <Fallenou> i can try again but i never managed to make it work
[23:17] <asac> the interface is up properly
[23:17] <Fallenou> where do you see that i don't get an ip ?
[23:17] <asac> where are you connected to? eth0 or eth1?
[23:17] <Fallenou> (it is correct but i don't find it in the log)
[23:17] <Fallenou> asac < well i don't really know :p since my system can't tell me where a wire is connected
[23:18] <Fallenou> i plug randomly the ethernet cable
[23:18] <asac> yeah thats what you see in log
[23:18] <asac> search for "now has a link" term
[23:19] <asac> thats when NM detects that your port has a wire plugged in
[23:19] <Fallenou> May 14 23:30:55 fixe avahi-daemon[5378]: Registering new address record for 157.159.43.64 on eth0.IPv4.
[23:19] <Fallenou> it is my good ip
[23:19] <asac> thats a fallback ip
[23:19] <Fallenou> it worked no ?
[23:19] <asac> no
[23:19] <Fallenou> no that's my ip actually
[23:19] <asac> avahi is something else
[23:19] <Fallenou> the ip the dhcp is to give me
[23:20] <Fallenou> with this mac adress
[23:20] <asac> that calls for trouble
[23:20] <asac> i mean thats a zero conf ip ... a dhcp server shouldn't hand that out
[23:20] <Fallenou> 157.159.*.* is my university network
[23:21] <Fallenou> 43 is my VLAN
[23:21] <Fallenou> and 64 my number on the local network
[23:21] <asac> hmm
[23:21] <Fallenou> i'm sure it's my ip
[23:21] <Fallenou> 100%
[23:21] <Fallenou> * [Fallenou] (n=Fallen@sionneau-lap.maisel.int-evry.fr): void brain(void) { }
[23:21] <Fallenou> look at where i'm speaking you from :p
[23:22] <Fallenou> since i'm on my laptop it's a different ip but nearly the same
[23:22] <Fallenou> fallen@laptop:~$ host sionneau-lap.maisel.int-evry.fr
[23:22] <Fallenou> sionneau-lap.maisel.int-evry.fr has address 157.159.43.45
[23:27] <Fallenou> asac < any idea ? :x
[23:27] <asac> no ... i guess you have no dhcp setup ;)
[23:27] <asac> and this avahi thing is broken
[23:28] <asac> does network manager believe you are connected when that avahi-daemon gets your IP ?
[23:28] <Fallenou> i think no but i'm not sure :o
[23:29] <Fallenou> i'm gonna try rebooting with wire plugged ....
[23:29] <Fallenou> and copy the syslog and everything :p
[23:30] <Fallenou> see you in 5 min
[23:37] <Fallenou> i got something interesting ...
[23:37] <Fallenou> a normal boot with wired plugged before switching on the computer : http://pastebin.com/m35c57248
[23:38] <Fallenou> this time ethtool says is HAS a wire :)
[23:38] <Fallenou> but the ip adress is ... wrong o_o
[23:43] <Fallenou> asac understand something ? :p me i don't :(
[23:44]  * asac looking
[23:45] <asac> Fallenou: your problem really is dhclient: No DHCPOFFERS received.
[23:45] <asac> and then avahi kicks in
[23:45] <Fallenou> yes
[23:45] <asac> 00:32:27 fixe avahi-autoipd(eth1)[6151]: Found user 'avahi-autoipd'
[23:45] <Fallenou> but dhcp should give me an ip ... :(
[23:45] <asac> most likely you don't have a dhcp driven network then
[23:46] <Fallenou> sure i have
[23:46] <asac> but something avahi driven ;)
[23:46] <Fallenou> it works with dhcp on my laptop
[23:46] <Fallenou> it works with dhcp with windows XP
[23:46] <asac> could you get a log from there?
[23:46] <Fallenou> it worked with dhcp on gutsy and feisty
[23:46] <Fallenou> what ?
[23:47] <asac> from a working gutsy setup for instance
[23:47] <asac> to compare
[23:47] <asac> maybe avahi just works there ;)
[23:47] <Fallenou> i don't have any gutsy setup
[23:47] <Fallenou> but i can give you a log from my laptop :)
[23:47] <Fallenou> which use the same wire cable (plugged in the same wall socket)
[23:48] <Fallenou> the only difference is the mac adress :p
[23:48] <asac> Fallenou: and that is what?
[23:49] <asac> hardy 2?
[23:49] <Fallenou> yes hardy :)
[23:49] <Fallenou> May 14 00:36:51 laptop dhclient: bound to 157.159.43.45 -- renewal in 39941 seconds.
[23:49] <Fallenou> May 14 00:36:51 laptop dhclient: DHCPOFFER of 157.159.43.45 from 157.159.43.1
[23:50] <Fallenou> got somethings like that
[23:51] <Fallenou> i am pasting the entire syslog, but it's complex since i oftent disconnect reconnect the wire to test on the other computer =)
[23:51] <Fallenou> anyway here it is : http://pastebin.com/mb8eb0c2