=== yofel_ is now known as yofel
[09:03] <alourie> good morning
[09:44] <Daviey> gema: do you have an update when building from lucid-proposed should be disabled?
[09:45] <Daviey> (morning btw)
[10:03] <gema> Daviey: jibel and patrick are on it, you should be asking them
[10:04] <Daviey> gema: thanks... jibel or patrick?
[10:05] <gema> Daviey: jibel is your best bet, given timezones
[10:14] <Daviey> It might come to a point where the release team just to select a date.
[10:15] <gema> Daviey: ack, I will talk to jibel
[10:15] <Daviey> thanks.
[10:16] <jibel> Daviey, your best bet is to ask the release manager
[10:19] <Daviey> jibel: seriously?  I asked towards the end of last week, How much time the QA team wanted to have images built from just -updates for.
[10:20] <Daviey> I'm trying to co-ordinate the release.. and take your input :)
[10:23] <jibel> Daviey, Seriously. automated tests of dailies are running and I'm currently verifying packages in -proposed that are in main
[10:23] <jibel> Daviey, it should be ok by Wednesday
[10:24] <Daviey> jibel: Okay, so this has already been communicated to the release team?
[10:25] <jibel> Daviey, automated tests yes, was part of last meeting status. SRU testing done by Wednesday, no.
[10:26] <Daviey> jibel: Great, ok - so if we switch to building from just -updates on Wednesday, you'll be happy?
[10:27] <jibel> Daviey, Wednesday evening yes
[10:27] <jibel> I'll be happy
[10:27] <Daviey> super
[10:27] <Daviey> thans
[10:27] <Daviey> +k
[13:54] <brendand> jibel - we're seeing problems with resolve.conf in hardware certification
[13:54] <brendand> jibel, failing to resolve domain names in the preseed is the issue
[13:55] <jibel> brendand, with precise I suppose ?
[13:57] <brendand> jibel - oh yes. seemingly only on desktop too. i didn't have any issue running tests on servers
[13:57] <jibel> stgraber, ^
[13:57] <brendand> jibel - this is a known one, right?
[13:58] <brendand> jibel, isn't stgraber in canada? he'll be online soon i guess?
[13:58] <jibel> brendand, there are several issues with the transition to resolvconf. This is the first I hear of with a preseed
[13:58] <jibel> he'll be online soon
[13:59] <brendand> jibel - any relevant bug numbers?
[13:59]  * stgraber waves
[14:00] <stgraber> brendand: is that when doing a netinstall? the installer failing at the kernel install step?
[14:01] <jibel> brendand, bug 922491 bug 923685 bug 924734 but they are all issues during upgrade
[14:01] <ubot4> Launchpad bug 922491 in resolvconf (Ubuntu Precise) (and 1 other project) "lucid to precise server upgrade: resolvconf failed to upgrade: cp cannot create regular file `/run/resolvconf/resolv.conf': No such file or directory (affects: 1) (heat: 6)" [High,Fix released] https://launchpad.net/bugs/922491
[14:01] <ubot4> Launchpad bug 923685 in resolvconf (Ubuntu Precise) (and 1 other project) "New resolver package overwrites manually created resolv.conf on server (affects: 4) (dups: 1) (heat: 26)" [Critical,Triaged] https://launchpad.net/bugs/923685
[14:01] <ubot4> Launchpad bug 924734 in resolvconf (Ubuntu Precise) (and 1 other project) "/etc/resolv.conf empty after upgrade from Oneiric (dup-of: 923685)" [High,Confirmed] https://launchpad.net/bugs/924734
[14:01] <brendand> stgraber - no, failing in the preseed late command
[14:01] <brendand> stgraber, it looks like we need to customize the resolve.conf and it is getting overwritten
[14:02] <brendand> # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
[14:02] <brendand> #     DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
[14:02] <stgraber> brendand: right, we've got a few reports of resolv.conf getting emptied in d-i, it's pretty high on my todo list for the day
[14:03] <brendand> failing is the wrong word though. some commands are failing because of not resolving domain names. but the install is succesful afaik
[14:03] <stgraber> brendand: currently my guess is netcfg messing with it somehow, the actual resolvconf code is AFAICS doing the right thing ...
[14:11] <brendand> stgraber, any chance this doesn't happen every time you install, or should it be repeatable?
[14:12] <brendand> https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/923685 sounds similar but we don't see it on servers
[14:12] <ubot4> Launchpad bug 923685 in resolvconf (Ubuntu Precise) (and 1 other project) "New resolver package overwrites manually created resolv.conf on server (affects: 4) (dups: 1) (heat: 26)" [Critical,Triaged]
=== bladernr_afk is now known as bladernr_
[14:24] <stgraber> brendand: the d-i issue is very reproducable, as in, I never saw an install succeed with my current setup
[14:24] <stgraber> brendand: bug 923685 is only for upgrades, doesn't affect clean installs
[14:24] <ubot4> Launchpad bug 923685 in resolvconf (Ubuntu Precise) (and 1 other project) "New resolver package overwrites manually created resolv.conf on server (affects: 4) (dups: 1) (heat: 26)" [Critical,Triaged] https://launchpad.net/bugs/923685
[14:25] <stgraber> brendand: bug 926447 is the d-i issue
[14:25] <ubot4> Launchpad bug 926447 in resolvconf (Ubuntu) "New resolvconf interacts badly with something in installs (affects: 1) (heat: 8)" [Critical,New] https://launchpad.net/bugs/926447
[15:04] <stgraber> brendand: I'm looking into the d-i weirdness now, hopefully it's the same issue that's affecting you though in a slightly different way
=== meetingology` is now known as meetingology
[15:50] <PaoloRotolo> Hi all!
=== kalosaurusrex is now known as albrigha
=== _salem` is now known as _salem
=== _salem is now known as salem_
=== kalosaurusrex is now known as albrigha
=== kalosaurusrex is now known as albrigha
=== salem_ is now known as _salem
=== koolhead17 is now known as koolhead17|zzZZ