/srv/irclogs.ubuntu.com/2012/05/28/#ubuntu-motu.txt

=== Jacky is now known as GLaDOS
=== GLaDOS is now known as Guest12539
=== emma is now known as em
=== Guest12539 is now known as Jacky
=== Adri2000 is now known as Guest74775
jtaylorI'm gone nuke all recommends on blcr-dkms, I'm feed up of deduping the bugs11:12
jtaylorhow could I solve the upgrade issue of users having openmpi installed?11:26
jtaylorI guess only lucid is of concern, the other upgrades have probably weeded out the package already as its broken since natty11:27
directhexwhat's wrong with openmpi?11:28
jtaylorthat it recommends blcr11:28
jtaylorwhich recommends blcr-dkms11:28
jtaylorwhich only works with 2.6.30 kernels11:28
jtaylorthere are hundreds of upgrade failure bugs11:28
jtayloreven though I added a bug pattern in natty :/11:29
jtaylorevery week or two another bug makes it through11:30
directhexblcr-dkms should be more sensitive to kernel versions. i'm sure you can define a range in dkms11:30
jtaylorI never dealt with dkms yet11:30
jtaylorhm dkms failures do not harm installation, silencing it in apport directly should be enough then11:45
tumbleweederm, silencing the bug reports presumably wouldn't make the situation any better. Then we wouldn't even know that we'd forgotten to update/remove it12:26
jtaylorwe already have the bug with the most dupes in the archive to remind us12:28
tumbleweedright, I mean in future releases12:29
jtaylornice we have an ubuntu only openmpi1.5, I wonder when that will start to bitrot12:29
jtayloradded in precise with an depend on blcr  which never worked in precise12:30
jtayloryey testing12:30
tumbleweed:/12:32
Davieyopenmpi1.5 was added for ARM support, i assume you have validated that blcr doesn't work with ARM?12:46
jtaylordoes arm have a 2.6.30 kernel?12:47
jtaylorhm I think -12 even supports 2.6.3412:47
jtaylorDaviey: does blcr work without the kernel module? if yes dropping the recommend would solve a lot of issues for users12:49
rbasakDaviey: hello!12:50
Davieyrbasak: meet jtaylor.. he's looking at openmpil(1.5)12:50
jamespageDaviey, hey12:50
rbasakhello jtaylor!12:50
jtaylorhi12:51
Davieyrbasak: context, http://pb.daviey.com/Usz2/12:52
jtaylorissues is bug 80494312:52
ubottuLaunchpad bug 804943 in blcr (Ubuntu) "blcr kernel module failed to build with kernel 3.0 : configure: error: --with-linux argument '3.0-x' is neither a kernel version string nor a full path" [High,Triaged] https://launchpad.net/bugs/80494312:52
jtaylorpeople installing openmpi get blcr which pulls blcr-dkms which is broken12:52
jtaylorgiven the number of dumplicates and comments users do not know how to deal with that12:53
Davieya reasonable amount of dupes :)12:53
rbasakI've not seen this before12:53
jtaylorI guess openmpi works fine without blcr, so we could just drop the recommends from libcr0 and less users would get this ugly bug12:54
rbasakSee bug 949044 for what I tested. IIRC, I tried this on amd64 and didn't run into the problem you describe.12:54
ubottuLaunchpad bug 949044 in openmpi (Ubuntu) "Basic openmpi hello world fails on arm" [High,Fix released] https://launchpad.net/bugs/94904412:54
rbasakPerhaps I understand it wrong?12:54
jtaylorthe issue is not really openmpi1.5, other mpi implementations also depend on blcr12:55
DavieyI've not looked into it.. but i wonder if a Pre-Depends or Breaks is required.12:55
rbasakSteps to reproduce? Just apt-get install...what?12:55
jtaylorapt-get install blcr-dkms12:55
rbasakNo for the openmpi breakage. What are people trying that pulls in blcr? Sorry I can't see the LP bug - timeout12:56
jtaylorlibcr012:56
jtaylorrecommends blcr-dkms12:56
jtaylormost uses autoinstall recommends12:56
rbasakSo they're installing what which pulls in libcr0?12:56
jtaylorhttp://paste.ubuntu.com/1011215/12:57
rbasakSorry, it would help if I could actually see the bug :-/12:57
jtaylorits got so many dupes lp probably can'T deal with it ;)12:58
rbasakDo we have to fix bugs that we can't see? :-P12:58
jtaylorreally fixing it will be hard, upstream only supports 2.6.3812:59
jtaylorhttps://ftg.lbl.gov/projects/CheckpointRestart/12:59
jtaylorwhat I want to archive is to reduce the collateral damage, I don't think many users really need blcr-dkms but get it installed indirectly12:59
rbasakI can't see the whole picture right now, but it sounds to me like blcr is out of date and should be removed from Debian, and that anything that depends on it needs to be fixed13:01
jtaylorit probably will be removed from debian13:01
jtaylorif not fix turns up soon13:01
jtaylorbut that doesn't help our current situation13:02
rbasakopenmpi1.5 is a temporary "fork" of debian experimental, for people who wanted the ARM support it has. As soon as Debian transitions to openmpi 1.5, the plan is to drop openmpi1.5.13:03
jtaylorgood13:03
rbasakhttps://lists.ubuntu.com/archives/ubuntu-server/2012-April/006245.html13:04
jtaylorI didn't want to imply bad maintenace, its just that so much ubuntu only stuff tends to just bitrot especially complicated stuff like openmpi is hard to handly by motu13:04
jtaylordo does anyone see an issue with just removing libcr0's recommend on blcr-dkms?13:06
jtaylorit should not break anything but save users from an error they might not know how to deal with13:06
rbasakI understand. For openmpi, I'm here to help. Some Canonical partners wanted it for ARM support, and so I'm indirectly sponsored to look after it AIUI.13:07
rbasakI don't see a problem with it, especially as it's broken already anyway, from what I understand.13:07
jtaylork I'll do that then for quantal and precise13:08
rbasakthanks!13:08
jtaylorlucid upgraders will still get the bug13:08
jtaylornot sure how to handle that, removing the recommend in lucid will only help for new installs13:09
jtaylorand -dkms might actually work in lucid13:09
rbasakIs this kind of knowledge something that do-release-upgrade is supposed to take care of?13:09
rbasak(and if so, how does that work for universe?)13:09
jtaylormaybe adding a breaks to the linux package would get it removed in the upgrade?13:11
rbasakI think that's what Daviey was suggesting?13:11
rbasakIt seems a bit horrible though. I'm new to this stuff. Is it possible for us to remove the blcr-dkms package as an exception to Debian?13:12
jtaylorthe other option is just silence apport, the module build failure does not harm the upgrade process itself13:12
jtaylorremoving blcr-dkms will not help on upgrades13:13
jtayloralso it might be useful to some users who install their own kernels, this is the reason its still in debian for now13:13
rbasakI'm just learning this here. Why would it not help with upgrades? If the package is gone and no other packages recommend it, wouldn't do-release-upgrade remove it?13:15
geserLaney: is ghc (from quantal) not working on armel: every haskell-* build on armel seem to fail with "Error: selected processor does not support ARM mode `movw r3,:lower16:stg_CAF_BLACKHOLE_info'" (and more similar ones)13:15
Laneygeser: /every/ build?13:15
jtaylorupgrades to not remove packages13:16
rbasakMy upgrades always do!13:16
jtaylorit might be a user installed package13:16
Laneygeser: maybe ghc itself needs rebuilding (probably syncing) to use the armel toolchain changes13:16
jtaylorhm I'm not very familiar with upgrade procedures either13:16
geserLaney: looks like, just pick some random haskell-* armel build logs to see yourself13:17
jtaylorI though they only remove obsolete libraries13:17
Laneygeser: I saw it for haskell-text and assumed the rest flowed from that13:17
Laneydidn't look too deep13:17
rbasakThat's what I'm thinking. What qualifies as an obsolete library, and wouldn't blcr-dkms fall into this category?13:17
Laneyanyway, you can build-test and sync if you like13:17
tumbleweedrbasak: we also can't remove packages from stable releases13:18
geserLaney: I don't have an armel pbuilder for easy checking13:20
rbasakI didn't think we'd need to. What upgrade are we trying to fix here? An upgrade to Quantal, or an upgrade to something previous? Are you suggesting removing the Suggests in an SRU?13:20
rbasaks/Suggest/Recommends/13:20
tumbleweedupgrades from lucid to precise13:20
Laneygeser: I wouldn't worry about that. If it builds on whatever you have then we can sync it and see if it fixes armel on the buildds.13:21
tumbleweedjtaylor: urgh, at removing the recommends from libcr0, but yes, that sounds like the sane option here13:21
Laneythat or ask someone in #-arm to test for us13:21
tumbleweedrbasak: yes, he's suggesting doing an SRU13:21
DavieyLaney: Are there still no ARM MOTU porter boxes?13:22
Laneyno13:22
geserLaney: I'll test build on amd64 and sync, it can't get worse for armel :) (I hope this doesn't start a new GHC transition)13:22
Laneyit will13:22
Laneybut we're pretty much in one anyway13:22
tumbleweedthere are no MOTU porter boxes at all13:22
Laneythe C arm porterbox is down too13:22
DavieyScott was setting that up, he's had the hardware at least 18 months13:22
jtaylorfiled bug 100552413:24
ubottuLaunchpad bug 1005524 in blcr (Ubuntu) "remove recommends on blcr-dkms" [Undecided,New] https://launchpad.net/bugs/100552413:24
jtayloruploaded to quantal and precise13:42
rbasakthanks!13:47
Laneyjbicha: hey, any reason you didn't mark the arduino-mk rdep of arduino as tested?16:59
jbichaLaney: because I didn't test it, since arduino-mk seemed too difficult for me to use17:06
Laneyok17:07
tumbleweedbdrung: do we really need --vendor= and DEBCHANGE_VENDOR in devscripts? What's wrong with simply exporting DEB_VENDOR?17:18
tumbleweedbdrung: on that topic, on the plane to UDS I did some devscripts back-merging. It's incomplete, though, and still needs further tidying up http://anonscm.debian.org/gitweb/?p=users/stefanor/devscripts.git17:26
tumbleweedplus I want to figure out how necessary all those ubuntu-specific dch options are17:26
geserLaney: the same error when building ghc on armel :( https://launchpadlibrarian.net/106320724/buildlog_ubuntu-quantal-armel.ghc_7.4.1-3_FAILEDTOBUILD.txt.gz17:34
bdrungtumbleweed: i want one command line parameter to set the vendor. DEBCHANGE_VENDOR could be dropped as compromise17:47
bdrungtumbleweed: do you have some changes in the pipe for dch using distro-info?17:48
bdrungtumbleweed: can you implement following: if no vendor is specified on the command line, try to determine the vendor based on the given distribution17:56
Laneygeser: well, armel has now broken both ghc and mono for q18:17
tumbleweedbdrung: you'll see some distro-info patches included in that branch18:26
tumbleweedLaney: \o/ :)18:26
bdrungtumbleweed: can you refresh your patches against master head?18:30
tumbleweedyeah must do that18:30
bdrungtumbleweed: or i can review the changes and let you commit them directly18:33
bdrungtumbleweed: you can commit part 2 of 2880f1a67 directly18:34
bdrungtumbleweed: and 304f97318:34
tumbleweedbdrung: I was intending to break them up into clearly defined and standalone patches. But in the end, it got a bit messy and there are later commits fixing mistakes in earlier ones. And it's all largely untested18:35
bdrungtumbleweed: i have some tests in the pipe18:36
tumbleweedI want to wave the substvar stuff by the other devscripts maintainers. It's a fairly invasive packaging change18:37
bdrungtumbleweed: i have some time _now_ and want to get the changes into devscripts. what workflow do you suggest?18:37
bdrungtumbleweed: the subvars stuff didn't convinced me yet18:38
tumbleweedwe could also just wait for archive-reorg :P18:38
tumbleweedright now, I need to get a chicken into the oven, so you have half an hour to do whatever you want :)18:38
tumbleweedfeel free to push any of that into master if you like the look of it18:39
bdrungtumbleweed: may i merge some of your changes under my name?18:39
tumbleweedsure, it's not like it's my original work. I was just extracting ubuntu changes18:39
bdrungk18:39
tumbleweed(well, much of it)18:39
bdrungtumbleweed: ping me after dinner and you will get a status update18:40
bdrungtumbleweed: pushed. afk for 2h18:53
tumbleweedbdrung: thanks19:20
highvoltagetumbleweed: where's that ubuntu conflicts page that shows packages with conflicing files again?20:20
MrChrisDruifGood evening all. How are dependencies determined for packages like epiphany-extensions?20:55
=== soren_ is now known as soren
=== Adri2000 is now known as Guest35099
tumbleweedhighvoltage: http://conflictchecker.ubuntu.com/possible-conflicts/ (according to qa.ubuntuwire.org)22:15
highvoltagetumbleweed: thanks (and sorry for the random bother)22:33
tumbleweednp. If I wasn't outside swatting off mosquitos I'd have replied sooner22:34
tumbleweedbdrung: pushed some distro-info changes, btw.22:34
tumbleweedbdrung: releasing u-d-t. Screw testing, that's what users are for22:35
tumbleweed(I joke, naturally)22:36
* ajmitch saves that quote22:37
tumbleweedthere is quite a bit of churn, I'm sure there are still issues. But I can't see them rgiht now.22:38
highvoltageheh, at least that boosts your mosquito body count :)22:46
bdrungtumbleweed: your changes look good. what do you think about http://paste.ubuntu.com/1012276/ ?22:47
bdrungtumbleweed: hope that your upload fixes more bugs than introducing new ones ;)22:49
tumbleweedbdrung: if that works, no objection22:54
bdrungtumbleweed: that works (compare that with testHelp() for example)22:57
bdrungtumbleweed: i played user regarding bug #99972722:57
ubottuLaunchpad bug 999727 in ubuntu-dev-tools (Ubuntu) "[backportpackage] -v and -m options don't work" [Undecided,Triaged] https://launchpad.net/bugs/99972722:57
bdrung:P22:57
bdrungtumbleweed: should we release distro-info 0.10?23:02
bdrungtumbleweed: what happens if python-distro-info throws an out-of-date exeption without distro-info being installed?23:02
tumbleweedmove that README to distro-info-data?23:04
bdrungtumbleweed: then it will be always present23:10
tumbleweedexactly23:10
bdrungcan you do that?23:10
tumbleweedbdrung: that readme assumes we'd use stable-updates (the modern volatile) but we haven't actually asked the release-team if they'd do that.23:12
bdrungtumbleweed: can you ask them?23:13
=== Guest35099 is now known as Adri2000

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