/srv/irclogs.ubuntu.com/2015/09/23/#ubuntu-devel.txt

catbus1Hi, when will be 14.04.4 released? I don't find it on https://wiki.ubuntu.com/TrustyTahr/ReleaseSchedule00:32
sarnoldcatbus1: if 12.04 LTS serves as a guide, february looks likely https://wiki.ubuntu.com/PrecisePangolin/ReleaseSchedule00:35
=== G__ is now known as g
=== g is now known as G
=== imcleod is now known as imcleod_zzz
pittiGood morning05:09
pittijdstrand: a "problem" only insofar that there was a looong test request queue05:09
pittijdstrand: the KDE package tests take awfully long, and we got several hundreds of them yesterday, so a lot to catch up with05:10
pittibah, yesterday the queue was at 250, now at 340, what happened05:10
pittiah, more KDE uploads05:11
pittijdstrand: so, it'll catch up eventually05:11
tjaaltonso is mesa stuck in proposed because of the freeze or something else?05:24
tjaaltonok found it in update_excuses.html, but why doesn't http://autopkgtest.ubuntu.com search show any hits?05:33
tjaaltonsigh arm is slow05:37
pittitjaalton: see scrollback from 20 mins ago05:37
pittitjaalton: there's also the libopengl-perl regression05:38
tjaaltonwhich failed three days ago too05:40
tjaaltonso not really a regression05:40
tjaaltonin mesa at leaset05:40
tjaalton*caused by05:40
tjaaltonthough failed for some other reason, now the deps can't be fulfilled05:42
pitti libgl1-mesa-glx : Breaks: libopengl-perl (< 0.6704+dfsg-2) but 0.6704+dfsg-1 is to be installed05:43
tjaaltonoh :)05:43
tjaaltonyeah let's sync that then05:43
pittitjaalton: https://tracker.debian.org/news/707796 ? looks sensible05:44
tjaaltonyes, forgot the breaks got added recently05:44
tjaaltonis there a way to test these locally first?05:46
pittiso, I added a second worker on each arm machine05:47
pittiwhile this slows down individual tests, this will be a net win on throughput, I do the same on the ppc64el boxes05:47
pittitjaalton: build and install it in a wily-proposed schroot?05:48
tjaaltonah05:48
zygagood morning05:50
dholbachgood morning06:14
seb128hey dholbach06:18
dholbachsalut seb12806:20
pittiinfinity: please let me know if you want me to disable testing on armhf temporarily, the backlog is huge (about a day, I'd say)06:27
pittiinfinity: if you want to build beta images today or so06:27
infinitypitti: Disabling armhf wouldn't hurt, yeah.06:29
pittiinfinity: okay06:29
pittiseb128, Saviq: ^ FYI06:29
Saviq tx06:30
seb128pitti, thanks06:30
pittidone06:32
pittinext britney run should stop showing/caring about armhf06:32
pittiinfinity: ok, lots of valid candidates now06:50
=== nudtrobert1 is now known as nudtrobert
seb128wgrant, cjwatson, still no wily langpack update, do you know if webops did an export retry yesterday?06:54
* pitti also overrides the boottest regressions while he's at it06:56
wgrantseb128: 2015-09-22 16:46:06 INFO    Registered the language pack.07:00
wgrantLooks there to me.07:01
pittiyes, it's on https://translations.launchpad.net/ubuntu/wily/+language-packs07:01
pittiseb128: want me to start a manual cron run?07:01
pitti(for wily it usually runs Friday, as we expect the exports on Thu)07:02
seb128pitti, yes please, I would like to have those on the beta image07:25
=== tsdgeos_ is now known as tsdgeos
=== athairus is now known as athairuzzz
pittiseb128: https://launchpad.net/ubuntu/wily/+queue?queue_state=1 is getting the uploads; is there something which you expect in particualr?08:20
seb128pitti, I was just checking the -fr source08:22
seb128yes, I was looking to know if evo/eds-3.16 were included08:22
seb128the .po are in the source08:22
seb128let's see if that ends up in the binary08:22
seb128pitti, looking good08:31
seb128let's see if we can get the langpack updates approved for beta, that would be nice08:31
pittiseb128: I was going to accept them now08:33
seb128danke08:34
seb128can you approved unity-control-center (fix for blutooth pairing) and user-setup (fix for autologin on new installs) as well? ;-)08:34
pittiinfinity: ^ hm, is that alright?08:34
pittiI just realized the beta is already tomorrow, not next week08:35
seb128yeah, I got confused by the wiki calendar08:35
seb128I though the freeze was tomorrow08:35
pittiseb128: so, I'm not sure how frozen we are; if I get a green light from the RT I can approve the langpacks and the others08:37
seb128pitti, thanks08:37
seb128let's see08:37
seb128I'm still unsure why we freeze things like that rather than just getting in proposed and blocking migration08:38
seb128like those langpacks could already build08:38
seb128they are going to be in before release in any case08:38
cjwatsonthe reason there's still a short freeze even on -proposed is to avoid people complaining that they needed to build their urgent fix but it FTBFS due to junk in -proposed08:39
cjwatsonthat doesn't seem to apply to langpacks though08:39
pittiI asked in #u-release08:40
cjwatsonthat said, there's no -proposed block in place at the moment08:40
pitticjwatson: the disabled ("cleaning") lgw builders with the "ongoing neutron problem investigation" is still ongoing, I take it?08:48
pittihttps://launchpad.net/builders/lgw01-11/+edit is a bit confusing08:48
pittias the builder seems to be enabled, but in "cleaning"08:48
pittithen again, lots of other builders are also in "cleaning" and haven't built anything for a week and don't have this note08:50
pittihttps://launchpad.net/builders/lcy01-08/+history -> last build on Sep 1808:50
cjwatsonpitti: Occasionally we run into incidents where the reset request gets lost for one reason or another; it has nothing to do with the previous neutron problem.08:53
cjwatsonpitti: disable/enable typically clears these up; I'll do that now.08:53
pitticjwatson: ok, good to know for the next time; thanks08:54
cjwatsonpitti: But "haven't built anything for a week" is just because we have plenty of builder capacity now - the whole build farm has been clean more recently than that.08:54
pittiso in general that's safe as long as the builder is marked as enabled?08:54
cjwatsonpitti: Well, best leave it to LP folks in case there's some known incident08:54
pitticjwatson: ah, ok; (and BTW, this is amazing!)08:54
cjwatsonBut normally should be08:54
pittiack08:54
cjwatsonpitti: should all be unstuck now08:56
cjwatsonNice for the special case of being able to build all your language packs in parallel, I suppose :)08:57
=== hikiko-lpt is now known as hikiko
FourDollarsIs it possible to revoke 1.4.10-1ubuntu1 of https://launchpad.net/ubuntu/+source/modemmanager? It didn't fix any issue.09:43
pittiFourDollars: the only way is to upload an -1ubuntu2 with the change reverted09:45
pittiFourDollars: or in this case, an -1wily1 (or anything which is bigger than 1ubuntu) so that the next time it auto-syncs09:46
FourDollarspitti: OK. I see. Thanks for your information.09:46
pitti1-1+build109:46
pittiFourDollars: 1.4.10-1+build1 is a better version number; it's clearer, and bigger than 1ubuntu109:47
FourDollarspitti: I agree.09:47
FourDollars@BinLi Could you help to do this for wily first? ^^09:48
udevbotError: "BinLi" is not a valid command.09:48
FourDollarsBinLi: Could you help to do this for wily first? ^^09:48
FourDollarspitti: BTW, what is the next version after 1.4.10-1+build1 if we want to fix some issue?09:52
pittiFourDollars: 1+ubuntu1, I figure09:53
FourDollarspitti: Thx.09:53
pittiFourDollars: OTOH, if the last version isn't actually a regression, just a no-op, you don't need to bother much09:53
pittiFourDollars: would just be nice to somehow remember that this can be synced at the next occasion, instead of merged09:53
FourDollarspitti: OK.09:54
=== nudtrobert1 is now known as nudtrobert
FourDollarspitti: Thx for your information again. :)09:55
pittitjaalton: ah, new libopengl-perl works again, so mesa propagated10:25
tjaaltonpitti: yeah10:30
BinLiFourDollars: ok10:38
pittiPSA: I have to reconstruct http://autopkgtest.ubuntu.com/ again, results will come back in the next hour or two; sorry11:25
tjaaltonpitti: hey, would adding some udev rules for steam controllers belong to systemd?11:59
=== DW-10297 is now known as Teduardo
=== pat_ is now known as Guest88770
=== imcleod_zzz is now known as imcleod
pittitjaalton: what do they do?12:43
tjaaltonpitti: good question, the bug doesn't have it attached12:45
tjaaltonhttps://bugs.launchpad.net/ubuntu/+source/steam/+bug/149865512:45
ubottuLaunchpad bug 1498655 in systemd (Ubuntu) "Steam Controller support: need read-write access to Valve-owned input event device nodes." [Undecided,New]12:45
tjaaltonbut looks like systemd got added already12:45
mdeslaurpitti, tjaalton: one sec, I'll attach it, I extracted it to take a look12:46
tjaaltonok good12:46
mdeslaurattached12:48
jdstrandpitti: ok, thanks for getting back to me :)12:55
jdstrandpitti: and hello :)12:55
pittihey jdstrand, how are you?12:55
pittijdstrand: FTR, I temporarily disabled armhf in britney to not block final beta; and the arm queue is down to 68 now12:55
jdstrandpitti: I'm doing well, yourself?12:56
jdstrandpitti: re britney, ok, thanks12:56
pittijdstrand: quite fine, thank you12:56
pittiwrestling with britney still :)12:57
jdstrand(it looks like the 3 packages I was looking at all migrated)12:57
jdstrandheh12:57
jdstrandwell, don't let me distract you! :)12:57
sil2100pitti: hey, checked the langpacks generated by langpack-o-matic manually here locally and all seems ok, I have the UITK updated po files etc.12:59
sil2100pitti: I'll modify the cron.daily.rtm script now12:59
sil2100pitti: just one question - in the old cron.daily.rtm, after the ./import command, there's also a call to ./merge-touch-upstream-translations13:00
sil2100What does that script do?13:00
sil2100Is it required?13:00
sil2100Since I never really ran it before, the resulting tarballs are just good13:00
pittisil2100: this was for the time when we didn't have translations in the ubuntu (or RTM) packages, only in trunk13:00
sil2100Aaah13:00
sil2100Ok, so I can just get rid of that13:00
pittisil2100: and IIRC this was down to one or two projects anyway, no? it started out with 15 projects to pull translations for13:00
pitticool13:00
=== dholbach_ is now known as dholbach
seb128quadrispro, pitti, should we sync the new libmtp from debian for wily? it seems to mostly fix bugs and add device ids13:24
pittiseb128: sounds good to me; libmtp hardly grows actual features13:25
pittiseb128: did you actually mean sync? i. e. did upstream take our "add arale device" patch?13:59
pittiseb128: and bq?13:59
seb128pitti, https://packages.qa.debian.org/libm/libmtp/news/20150605T162243Z.html14:00
pittiyay14:00
sil2100pitti: https://code.launchpad.net/~sil2100/langpack-o-matic/new_overlay_cron/+merge/272111 - this would need the multi merge branch to land as well :)14:03
pittisil2100: yay, thanks14:04
pittisil2100: I haven't yet done the previous MP, sorry; it now looks even more complicated than before, I'll see to making this easier14:05
sil2100Oh, I need to correct one thing in it14:05
pittisil2100: or merge it if you carefully tested it with two and multiple tarballs14:05
pittibut right now it's rather hard to understand14:05
sil2100I used it for merging 3 tarballs and it worked14:06
pittiok14:06
pittiso then maybe I'll just merge this "blindly", and rewrite the damn thing from scratch14:06
sil2100At least, I got the proper langpacks from langpack-o-matic ;p14:06
sil2100It's not so complicated, I'm doing the exact steps you did just sequentially, one argument after another14:07
pittisil2100: yeah, wasn't blaming you really -- this script is horrible14:07
pittiall this find/copying stuff around is massively overkill14:07
pittisil2100: your idea with cat'ing the mappings to .merged and sort -u at the end is nice, and so much easier14:07
pittiwith that we can just untar all tarballs on top of each other14:08
sil2100Thanks, actually yeah, we might get rid of the find call that way even now I suppose14:09
sil2100Well, let's do that later :)14:09
rbasakinfinity: I've just uploaded new backports for docker.io, to trump the existing packages in -proposed for some upgrade issues that kickinz1 found. They're fixed in Wily and re-backported.14:13
pittisil2100: I'm trying to spot what you changed in the ./import line14:15
pitti+find pkgs/ -name changelog -exec sed -i 's/ 15.04;/ vivid;/' "{}" \;14:16
pittisil2100: ^ that looks like a debugging leftover? shouldn't that be s!pkgs!$dir/sources-touch! or something like that?14:16
sil2100Argh!14:16
sil2100Yes!14:16
sil2100uh!14:16
pittisil2100: oh, I see it: $TAR → $TARM, of course14:17
pittithat's what I like about PRs on github, the actually changed chars have a stronger color14:17
tewardif a package is compiled with sse2 instruction set support but not sse support, is that a bug that should be filed?  (generic question based off a discussion in #ubuntu-bugs right now)14:29
seb128mardy, thanks for eds oauth refresh patch, that fixes my indicator-datetime not listing calendar events, I backported the fix to wily ;-)14:34
mardyseb128: oh, thanks for that!14:35
seb128yw!14:35
seb128it's funny that you filed that bug/patch today, I started looking at why my calendar was buggy yesterday and filed some upstream bugs with valgrind logs14:35
seb128just backported some fixes from Milan for those and your patch as well14:36
rbasakteward: I think that depends on what we define to be the minimum instruction set that we support. I'm not sure where that might be documented.14:38
rbasakdoko might know maybe? ^14:38
melodiehi14:39
melodieI have installed Bento Openbox Remix in a very old laptop, Compaq Presario 920 with a proc amd athlon XP 2000+, which as the sse flag but no sse2 flag and a few programms don't start there but crash. Is it a bug or are they expected to not work with a non sse2 capable proc? This is glxgears and glxinfo14:41
melodie$ LANG=C glxinfo14:41
melodiename of display: :014:41
melodieIllegal instruction (core dumped)14:41
melodie(for example)14:41
highvoltage1/win 1214:43
ryaoIs the SRU process used for kernel updates in both LTS releases and non-LTS releases or just LTS releases?14:52
cjwatsonryao: Both (although the kernel is a special case for SRUs, https://wiki.ubuntu.com/KernelTeam/KernelUpdates)14:54
tewardrbasak: it's related to melodie's issue15:07
tewardrbasak: i know that for an instruction set to be supported on any given system the CPU needs to support it, but that doesn't answer the ultimate question of minimum supported instruction set.  If that's documented somewhere, great, if not, well then meh15:08
melodieteward, it seems for now, that only glxgears and glxinfo can't start and spit a 'core dump illegal instruction' message.15:09
melodieI have tried several programs so far15:09
rbasakI suspect the minimum supported set is known by someone somewhere.15:10
melodieincluding pcmanfm, xchat, synaptic, sakura, libreoffice writer15:10
seb128cyphermox, would https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1498805 be one for you or for infinity?15:10
rbasakJust not by me.15:10
ubottuLaunchpad bug 1498805 in usb-modeswitch (Ubuntu Wily) "Please merge usb-modeswitch 2.2.5+repack0-1 from Debian unstable/testing - current 2.2.3 version in Wily has regressions with lots of Huawei modems" [High,Triaged]15:10
seb128it claims that the 2.2.3 update in wily regressed things15:10
rbasakMaybe ask the ubuntu-devel ML?15:10
tewardrbasak: indeed, I may.  melodie: perhaps ask the ML?15:11
tewardrbasak: fwiw i don't ever really have any issues, my proc supports sse and sse2 as well as probably others.  Modern processors are modern :)15:12
melodieteward, I am unsure if I should suscribe there... do you think you could ask the question?15:12
tewardI don't think I'm subbed either15:12
melodiethen I guess I should :)15:15
melodiejust one more for the todo list15:15
melodie:)15:15
melodiehumm15:15
melodieyes that's the point, "minimum set supported"15:16
cyphermoxseb128: it's for anyone who wants to tackle it. It involves looking at the diff between the versions of the tcl program, and re-doing those in our C rewrite15:18
cyphermoxthe regression might be something else, like interaction with systemd15:19
seb128k15:20
seb128cyphermox, well, I was mostly pointing it so it's doesn't get un-noticed15:20
seb128I tagged it rls-w-incoming as well15:20
cyphermoxI would suggest someone very familiar with systemd take a look, in case, even before doing any other update :/15:21
melodiethanks, I have to quit now15:21
seb128cyphermox, that means pitti? ;-)15:21
sil2100pitti: hmmmm15:21
cyphermoxseb128: not necessarily, but I'm afraid I might not be the best person to look at it15:21
seb128k, no worry15:22
cyphermoxas I recall, it was already "fixed" to deal with systemd and udev in the "new way", but maybe something's still off15:22
tewarddid the latest galculator get on the beta2 image or no?15:22
teward(see #ubuntu-bugs, and poke phillw or melodie for more details)15:22
sil2100pitti: so I tested the cron script that I prepared just now, and I think there might be something wrong with the tarballs we get through the +latest-*-language-pack link15:22
sil2100pitti: since when I manually downloaded the tarballs from LP through the webbrowser and ran ./import, the resulting packages had proper UITK .po files - but when I run the cron script, those are missing as in your case15:24
sil2100pitti: looking into that now15:24
pittisil2100: wow -- so I'm not seeing ghosts?15:24
sil2100pitti: it's really really strange! Since the cron script does the same things I did manually, with the only difference being how the tarballs got downloaded15:25
sil2100I'm downloading them now here to see if that's really the case15:25
cyphermoxpitti: can you ping me when you have a moment, we can team up against usb-modeswitch and see what might be wrong with the version in wily before we consider updating?15:27
tewardtjaalton: ping, if you're around15:28
tewardif not someone else who knows the galculator package will do15:28
pitticyphermox: we are mostly non-overlapping (no time any more today, sorry); what's wrong with it?15:28
pitticyphermox: I fixed a few segfaults earlier in wily which made it work at least for me15:28
cyphermoxnot always running the switching for huawei modem15:28
cyphermoxif you say it works for you, perhaps this is limited to huawei15:29
cyphermoxin which case I won't need your help :)15:29
sil2100pitti: oh, wait, I think I see the potential problem15:29
sil2100Let me test (will take a while)15:29
pitticyphermox: I actually have a huawei stick too, I just never used it (except for testing this, like twice a year)15:29
tjaaltonteward: ?15:30
cyphermoxpitti: ok15:30
cyphermoxwell, not today is fine too15:30
pitticyphermox: so this is triggered via udev rules, right?15:31
cyphermoxyes15:31
pitticyphermox: the main gotcha I'm aware of is that udev rules must never try to launch a process into the background15:31
pittiit'll just get killed after a second or so15:31
tewardtjaalton: galculator complaints, apparently, but it's a proxy report of a problem.  last activity was yesterday, now ubuntu-bug supposedly doesn't see the package as an actual package from the repos15:31
pitticyphermox: but under systemd it should trigger usb_modeswitch@.service, does it?15:32
cyphermoxpitti: maybe, I don't recall15:32
cyphermoxin any case, I'll debug it here15:32
tewardtjaalton: any idea why it wouldn't be read as official, etc. with trying to report new bugs?15:32
cyphermoxI may have a huawei modem around somewhere15:32
pitticyphermox: so what's really worrying is that the whole /lib/udev/usb_modeswitch runs in teh backgroud15:32
ryaocjwatson: Thanks.15:32
pitticyphermox: that cries for race conditions and getting killed prematurely15:32
tewardtjaalton: since you last synced it, i thought i'd bug you first.15:33
pitticyphermox: we had a similar problem with ifup@.service, if DHCP took more than 3 seconds or so it was killed15:33
* teward is attempting to reproduce now15:33
cyphermoxyes, it runs the usb-modeswitch service15:33
tjaaltonteward: what's the issue? ubuntu-bug galculator seems to work here15:34
tjaaltondon't even have it installed15:34
tewardtjaalton: phillw reported that "in paper mode, you cannot type anything in"15:34
tewardtjaalton: he tried ubuntu-bug and it said it wasn't an official package15:34
tewardagain i'm trying to repro (but my VMs died >.<)15:34
tjaaltonthe old version perhaps?15:35
tjaaltoni've never used it myself, synced because it was on the sponsor queue15:35
tewardtjaalton: ack.  may just say manually file, and then do apport-collect15:35
tewardor w/e it is to get the apport data15:36
* teward has it written somewhere15:36
tjaaltonso how to init paper mode?15:36
tjaaltonoh got it15:36
tjaaltonseems to work here15:36
tewardcrud i need to redownload the iso >.<15:36
tewardstupid corruption >.>15:36
tjaaltonubuntu-bug not doing it's thing probably means something is out-of-date15:37
tewardtjaalton: indeed15:37
tjaaltonso first upgrade to current wily and try again..15:37
tjaaltonit's fine here15:37
tewardack15:38
tewardtjaalton: looks like you're off the hook, phillw's gonna poke ianlorin about it, but i'm still going to see if I can reproduce with the beta 2 iso15:39
tewardafter it redownloads xD15:39
tjaaltoni have wily on four systems, it's fine :P15:39
tewardindeed.  i have power-user'd 14.04 on this laptop, but VMs galore for the other versions xD15:40
rbasakstgraber: I've re-uploaded kimchi with the debian/copyright fix. Diff is: http://paste.ubuntu.com/12531981/15:43
stgraberrbasak: thanks15:58
=== athairuzzz is now known as athairus
catbus1Hi, anyone know when 14.04.4 will be released?18:35
jtayloris there a good way to disable the grub quick_boot? grubs save_env is buggy and often ends up waiting for user input when it fails18:45
jtaylorwithout a timeout18:45
jtaylorvery annoying with a headless server18:45
jtayloronly thing I see in the source is a compile time option or editing the etc/grub.d files ..18:47
cjwatsonGRUB_RECORDFAIL_TIMEOUT in /etc/default/grub18:49
jtaylorcjwatson: doesn't work18:50
jtayloror at least assuming it has a default that is not infinity18:50
jtaylorits not the grub menu that is the problem, save_env fails which then seemingly goes into some code that does not have a timeout attached18:50
jtaylorbug 1311247 bts18:55
ubottubug 1311247 in grub2 (Ubuntu) "[Grubenv] error: malformed file, press any key to continue" [High,Fix released] https://launchpad.net/bugs/131124718:55
jtaylorthe fix released should get removed18:55
cjwatsoncyphermox: ^-18:57
cjwatsonneeds actual analysis, reproduction recipe with recent Ubuntu releases, etc. rather than just saying "grub's save_env is buggy"18:57
cjwatsonperhaps better to file a new bug rather than piling onto an existing one18:57
jtaylorprobably, but having a workaround in that bug is useful because thats what you find with google18:58
jtaylorthe other stuff is questionable18:58
jtaylore.g. changing the default entry used18:59
cjwatsonwell, except that you've just stuck a workaround in that bug which will probably persist on people's systems forever because conffiles18:59
cjwatsoneven after the bug is long fixed18:59
cyphermoxjtaylor; perhaps it would indeed be best to file a new bug18:59
cyphermoxthat one was indeed showing a "malformed file" error, and seemed to be because of the blocklists, maybe there's something else19:00
cyphermoxthough I agree it needs an SRU19:01
jtaylorsure, what do you need to debug it?19:01
jtaylornote I'm using 14.0419:01
cyphermoxso you're not on grub2 ending with -21?19:01
jtaylor2.02~beta2-9ubuntu1.319:02
cyphermoxit's a little confusing on that bug because I read at least one comments says they're already on the right version for that fix19:02
cyphermoxok19:02
jtaylorthe first partition starts at block 63 btw, I know that sometimes causes issues19:03
cjwatsoncyphermox: I don't believe this fix was ever SRUed to trusty19:04
cyphermoxcjwatson: no, it wasn't19:04
cjwatsonso that may be all there is to it19:04
cyphermoxthat's the problem19:04
cyphermoxyes19:04
cyphermoxjust got lost in the noise of new rush things coming it :/19:05
jtaylorah there is a fix, I can test that quickly19:06
jtaylormissed that changelog entry in the huge bug ..19:06
jtaylorwow grub takes long to build oO19:32
jtaylorcyphermox: the patch from -21 backported solves my issue19:43
sil2100pitti: hey! If anything, I pushed the required change to the cron branch of langpack-o-matic and now everything seems to work as expected ;) UITK translations present ;p19:54
nelhage!regression-alert21:23
ubottubdmurray, cjwatson, Daviey, didrocks, doko, infinity, jdstrand, pitti, RAOF, Riddell, ScottK, seb128, skaet, slangasek, SpamapS, stgraber: reporting regression in a stable release update; investigate severity, start an incident report, perhaps have the package blacklisted from the archive21:23
nelhagebug #1499075; python 3.4 SRU broke botocore and awscli in Trusty21:23
ubottubug 1499075 in python3.4 (Ubuntu) "python3.4.3 SRU breaks awscli" [Undecided,New] https://launchpad.net/bugs/149907521:23
nelhagelooks like the SRU went out with bug #134895421:23
ubottubug 1348954 in python3-defaults (Ubuntu) "update Python3 for trusty" [Undecided,New] https://launchpad.net/bugs/134895421:23
mdeslaursmoser: ^21:42
mdeslaursmoser: perhaps a awscli fix is required there ^21:42
nelhageYeah, following the rabbit hole further it looks like the fix probably has to go into botocore.21:43
broderi just dropped https://launchpadlibrarian.net/218689089/python-botocore_0.29.0%2Brepack-2ubuntu0.1.debdiff on the bug21:45
broderit seems like it would be nice if the behavior change in python3.4 could be reverted though?21:45
brodersurely botocore isn't the only package using inspect21:45
sarnoldthough having a differnt behaviour than other python 3.4.1 or later environments might also lead to bugs21:47
mdeslauryeah, I'm conflicted on that as well21:48
mdeslaurit's the SRU team's call21:48
broderhmm, probably, though my suspicion is that _not_ throwing an exception seems less likely cause problems? but hard to say21:48
sarnoldit might be worth poking barry too: https://launchpad.net/bugs/1499075  https://launchpad.net/bugs/134895421:49
ubottuLaunchpad bug 1499075 in python3.4 (Ubuntu Trusty) "python3.4.3 SRU breaks awscli" [Critical,Confirmed]21:49
ubottuLaunchpad bug 1348954 in python3-defaults (Ubuntu) "update Python3 for trusty" [Undecided,New]21:49
Unit193robert_ancell: Now that /etc/lightdm/lightdm.conf isn't edited by anything, can you install the example file ( /usr/share/doc/lightdm/lightdm.conf.gz currently) there?21:52
=== juliank0 is now known as juliank
robert_ancellUnit193, the convention for Debian / Ubuntu packages is to install example configuration into /usr/share/doc21:52
robert_ancellUnit193, and putting a file in /etc/ gets a bit confusing when upgrading packages (it will prompt you to replace any local changes with the package provided one)21:53
mdeslaurbroder: debdiff looks good, did you test it?21:57
Unit193robert_ancell: https://packages.debian.org/sid/i386/lightdm/filelist but yes I did think of the second part, wouldn't be ideal.21:58
brodermdeslaur: i've tested it locally off sbuild21:58
broderi'm...a bit rusty at the processes :)21:59
Unit193(Usually you have a config file in /etc/ to edit, you don't usually have to create it.  Leads people to hunt down config files in /usr/share/ and edit.)21:59
mdeslaurbroder: ok, I'll upload it to the queue for the sru team, one sec22:00
mdeslaurnelhage, broder: I've upladed the python-botocore fix for approval by the sru team and I've asked in #ubuntu-release22:11
* mdeslaur -> away22:11
dokobroder, mdeslaur, there was some discussion what the best thing would to be. but afaicr, the expectation to have that the same behaviour as with the upstream version would be better22:51

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!