/srv/irclogs.ubuntu.com/2014/07/29/#ubuntu-devel.txt

cjwatsonpitti: http://d-jenkins.ubuntu-ci:8080/view/Utopic/view/AutoPkgTest/job/utopic-adt-kde-runtime/ARCH=i386,label=adt/45/console - we could really use "apt-get update || { sleep 15; apt-get update; }" or something in the adt setup02:20
hallynxnox: hey, late in your tz, so probably not, but...  are you around?02:32
=== _salem is now known as salem_
pitticjwatson: curious, adt-run is already using that in most places (we talked about it a few months ago); apparently I forgot one place, I'll have a look04:00
pittiGood morning04:00
pittislangasek: hey Steve!04:24
pittislangasek: do you think it's ok to upload the sysvinit to -proposed and keep it there with a block-proposed bug? that way we can already run all the testing against it04:24
pittislangasek: it's a relatively harmless effective change, after all04:25
=== timrc is now known as timrc-afk
pitticjwatson: oh -- that log already *does* retry, and the second apt-get update succeeds; the BADSIG is bug 134587704:34
ubottubug 1345877 in ubuntu-archive-publishing "Invalid GPG signature http://ddebs.ubuntu.com/dists/trusty/Release.gpg" [Undecided,Confirmed] https://launchpad.net/bugs/134587704:34
slangasekpitti: I'd rather not deliberately put stuff into -proposed that we don't expect to get out immediately04:34
slangasekpitti: but I guess it's your call04:34
pittislangasek: ah, I postponed it as the other day you said that there are some things you didn't like in the new versino, and you wanted to review04:35
pittislangasek: also, I don't want to land it in traincon-004:35
pitticjwatson: ah no, the badsig is from the main archive, not from ddebs; so I guess this is a case where apt-get update failed twice in a row :/04:35
slangasekpitti: correct, I want to review the merge before it goes in, on account of some vexing upstream changes04:35
pittislangasek: ok, then I won't upload it for now04:36
slangasek(and it's easier for me to review it than to give an accounting of all the things that have recently been wrong with sysvinit maintenance in Debian)04:36
=== salem_ is now known as _salem
=== doko_ is now known as doko
dokopitti, jibel: could you restart the plv8 and pgagent autopkg tests? seem to be qemu issues06:08
pittidoko: no, pgagent is an actual bug; I just uploaded the transition to 9.4 to Debian, will auto-sync06:08
dokogwenview did fail before tpp06:08
dokoahh, ok06:08
pittidoko: plv8 as well, there's something wrong with the transition (it tries to pull in 9.3)06:08
dokowell, blocking gcc-4.9 ...06:08
pittidoko: it's on my list for today, too06:08
=== evfool__ is now known as evfool
dokoRiddell, can you or #kubuntu have a look at the gwenview autopkg test failure?06:54
dholbachgood morning06:54
dokodobey, ubuntu-sso-client ping, could you have a look at the autopkg test failure?07:01
pittidoko: ah, the fixed plv8 is still stuck in Debian binNEW07:16
pittidoko: I'll do an Ubuntu upload to unblock07:16
=== tvoss is now known as tvoss|test
=== tvoss|test is now known as tvoss
cjwatsonpitti: oh, right, ugh.  ok08:20
cjwatsondoko: I already applied a force-badtest hint to gwenview; no idea why it's still showing there08:22
cjwatsonoh, p-m can only take one hint for any given package08:22
cjwatsondoko: once everything else is fixed, tell me and I'll force-skiptest gcc-4.908:22
=== vrruiz_ is now known as rvr
pittidoko: plv8 is good now; I just removed the NBS, it should promote in the next cycle; (and unblock gcc)08:45
dokopitti, cjwatson: that leaves gcc-4.9 with pgagent (which will be synced from debian soonish), and gwenview08:51
pittias the gwenview regression was introduced with 4:4.13.90-0ubuntu1 in -proposed, we could also just remove that package from -proposed08:52
cjwatsonpitti: no08:53
cjwatsonpitti: we've seen failures with earlier versions too; also please don't do anything to interfere with the megatransition08:53
cjwatsonpitti: ScottK has already forwarded it upstream, and we think the failures are ignorable for now08:53
cjwatsonhence my hint08:53
pittiack08:54
pittiwrt. history, http://d-jenkins.ubuntu-ci:8080/job/utopic-adt-gwenview/20/ was an infrastructure problem, otherwise http://d-jenkins.ubuntu-ci:8080/job/utopic-adt-gwenview/? looks fairly stable (pass/fail)08:54
cjwatsonoh, maybe the alleged failures with earlier versions are just adt-britney being confused08:54
pittibut override WFM, it's clearly not a gcc regressino in this case08:55
cjwatsonnotice how update_excuses says "autopkgtest for gwenview 4:4.13.2-0ubuntu2: Regression" in places08:55
pittiindeed; looks like it says the release version number there instead of the proposed version?08:56
cjwatsonI guess the cause is wrong in the various control files, but argh that stuff hurts my brain08:57
cjwatsondoko,pitti: ok, so I've hinted "force-skiptest gcc-4.9/4.9.1-3ubuntu2"08:57
pittinot a biggie right now either way08:57
pitticjwatson: thanks08:57
pittiif it's any urgent, you can also skip the pgagent test; I suppose it'll still be a few hours until it gets imported and synced08:58
cjwatson"force-skiptest" skips all tests hung off a given upload08:58
cjwatson"force-badtest" skips just tests for a given failing package08:58
pittiah08:58
cjwatsonSo in this case I meant to say "everything done, ignorable, or being fixed"08:59
cjwatsonAnd none of it caused by gcc in any event, as far as I understand it09:00
mlankhorstcjwatson: fglrx won't be available for some time when I release xorg-server 1.16, in that case could fglrx be temporarily dropped or something?09:11
seb128shouldn't we hold on 1.16 until all drivers are ready instead?09:11
cjwatsonmlankhorst: that seems questionable given that it's widely-used09:13
cjwatsonmlankhorst: but seems that needs wider discussion rather than just asking me, a non-fglrx user :)09:14
mlankhorstthere's radeon still available as alternative09:14
seb128-1 for letting users down this way09:14
seb128we decided some cycle ago to not do that anymore no?09:15
mlankhorstbut we won't receive upgrades for radeon until very near final release :/09:15
mlankhorstand flipping the whole xorg-server near release sounds like a  bad idea, while some of the other changes are definitely needed09:23
seb128needed for what?09:24
seb128well, you should talk to other teams, maybe email ubuntu-devel@ with the plan and why we need the update even if we don't have all drivers09:24
mlankhorstI have mailed a CFT to ubuntu-devel@09:24
cjwatsonRiddell: Can we slow down the KDE uploads for a bit?  I think libav might just have landed if not for the gwenview upload just now09:30
cjwatsonargh, which is dep-wait09:31
cjwatsonon something not uploaded yet!09:31
cjwatsontempted to remove that and copy the old one back09:31
xnoxwell, anything that would make britney transition things or give us a sensible list of things to fix is good.09:34
cjwatsonxnox: I've got a sensible list and it says "gwenview"09:36
cjwatsonlibav migrating!10:11
rbasak\o/10:11
cjwatsonpublisher on manual to ensure that all the copies go in one batch10:11
cjwatsonpublisher on auto10:20
mlankhorstcjwatson: what about a solution where we upload xorg-server and all the packages to -proposed near feature freeze, and keep it there until the next fglrx release, hopefully in a week or 2 later?10:39
cjwatsonI guess that's one option but be careful of things that might end up blocked on that10:40
cjwatsonhonestly I'd rather not be the decision-maker here - I'm going to have a lot to do with phone RTM10:40
mlankhorstwell not requiring a FFe for xorg-server would be ok with me too10:42
pittimlankhorst: so perhaps testing from a PPA would be better for now? (FWIW, I have no idea how important the fglrx driver is these days -- back then, radon worked just fine for me, but it's been years since I had something non-intel)10:51
pittiradeon even10:51
mlankhorstpitti: we have a ppa, but that doesn't get NEARLY as much testing as the archive does..10:52
mlankhorstI'll be lucky to get 10 people testing..10:52
pittixorg-edgers how how that was called?10:52
pittimlankhorst: OOI, in which regards is fglrx better than radeon these days?10:53
mlankhorstno idea, I tend to use radeon more. presumably fglrx has some features radeon lacks10:53
pittiI mean, if it doesn't work on some hardware, that's a good reason to not break utopic; if it's just marginally slower or eating a bit more power, temporarily dropping it seems just fine to me10:56
pitti(assuming that it automatically falls back to radeon)10:57
pitticomparing the vendor/product ID lists might help there?10:57
mlankhorstnot really, mostly newer HW works minus radeon bugs11:12
mlankhorstit's just that the latest might not, no idea tbh11:12
=== pete-woods is now known as pete-woods|lunch
=== MacSlow is now known as MacSlow|lunch
=== Trewas666 is now known as trewas
rbasakLooking at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752796, it looks like a Perl 5.20 transition is due to hit sid on 12 August.11:25
ubottuDebian bug 752796 in nginx "nginx: hardcodes /usr/lib/perl5" [Serious,Open]11:25
rbasakThat's before our feature freeze. Are we going to take that?11:26
rbasakI'm wondering whether to cherry-pick the fix for nginx that is in VCS but not uploaded to unstable yet.11:26
=== ycheng is now known as ycheng-afk
mdeslaur@pilot in11:27
=== udevbot changed the topic of #ubuntu-devel to: Archive: open | Devel of Ubuntu (not support or app devel) | build failures -> http://qa.ubuntuwire.com/ftbfs/ | #ubuntu for support and discussion of lucid -> trusty | #ubuntu-app-devel for app development on Ubuntu http://wiki.ubuntu.com/UbuntuDevelopment | See #ubuntu-bugs for http://bit.ly/lv8soi | Patch Pilots: mdeslaur
=== tvoss is now known as tvoss|lunch
mlankhorstpitti: oh and without xorg-server radeon will actually work worse, because it will lack the glamor updates11:34
mvo_jibel: can you confirm in the lap or on your test vm (when you have a moment) that #1347964 is no longer appearing?11:56
jibelmvo_, without any specific repo?11:58
rbasakpitti: the 'current specification' link from http://dep.debian.net/deps/dep8/ is broken.12:01
mvo_jibel: yeah, it should be fixed in the main repo already12:03
mvo_jibel: fingers crossed :)12:03
=== pete-woods|lunch is now known as pete-woods
=== pipe_dream is now known as lisca
jibelmvo_, upgrade in progress ...12:05
mvo_jibel: you rock12:09
=== MacSlow|lunch is now known as MacSlow
juliankslangasek: Is the patch debian/patches/gcc46-compatibility for gnu-efi still needed (what's the reason for building with gcc 4.6 these days?) or can this be synced from unstable to the new upstream release now?12:20
juliankIf it can be dropped, a "syncpackage -s juliank gnu-efi" would be nice12:22
pittirbasak: yeah, I fixed it in svn a few weeks ago and asked for updating it, but that didn't happen yet :/12:23
rbasakNo worries12:23
=== _salem is now known as salem_
dokojamespage, maven fun in proposed ... libcommons-logging-java and tomcat8 ...12:54
jamespagedoko, joy joy12:54
dokocan you have a look? http://people.canonical.com/~ubuntu-archive/component-mismatches-proposed.svg12:54
dokoobjenesis?12:55
jamespagedoko, not right now - dealing with some other things today12:55
jamespagedoko, as we doing tomcat8 for main this cycle?12:55
jamespageare we rather12:56
dokojamespage, you tell me ...12:56
* jamespage thinks12:56
dokozul better should subscribe ubuntu-mir when filing MIR's ...13:01
xnoxdoko: should i make 3.5 default for llvm-default on ppc64el only? or should I instead fix powerpc build failure and work out if/when/can we switch to 3.5 by default?13:02
* xnox looks at release schedule.13:02
dokoxnox, I'd say make it the default on all architectures after checking that mesa is fine with it13:04
xnoxdoko: ack. this also means fixing powerpc build then.13:05
dokodholbach, you sponsored python-wsme, hangs now in component mismatches ... please file the 30 MIR which are required, or drop the build deps ...13:07
dholbachNoskcaj, ^13:11
dholbachdoko, I followed up on the sponsoring bug - thanks - I thought I had checked all the build-deps and verified they were in main13:12
dholbachI must have missed something13:12
dobeydoko: re: ubuntu-sso-client, do you have a link? i didn't get any e-mail about it failing13:14
dokodobey, http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html13:15
dokotvoss|lunch, can you take care about https://bugs.launchpad.net/ubuntu/+source/libjsoncpp/+bug/1349834 ?13:16
ubottuUbuntu bug 1349834 in libjsoncpp (Ubuntu) "[MIR] flask-script and libjsoncpp (b-d's for net-cpp)" [Undecided,Incomplete]13:16
dholbachdoko, I reopened the bug as well13:16
dobeysigh, why is squid not starting13:18
apacheloggermardy: heya, any chance of getting a new signon upload for utopic? we are currently porting kde-accounts and it appears as though the cmake config installed by the current package has a bit of a divergent name from what is in git (namely SignOnQtConfig.cmake vs. SignOnQt5Config.cmake)13:24
jibelmvo_, upgrade from 12.04.4 desktop + Trusty HWE stack -> Trusty is successful on amd6413:35
* jibel hugs mvo_13:36
* mvo_ hugs jibel13:43
mvo_thanks for confirming13:44
=== tvoss|lunch is now known as tvoss
tvossdoko, on my list13:46
cjwatsonrbasak: perl 5.20> I'm considering it if the rest of -proposed is quiet enough at that point13:48
rbasakcjwatson: OK, thanks. I didn't cherry-pick it for now, but the patch (for nginx) is there for us to grab if we need it.13:50
argesjamespage: hello. I see ceph/nova are in teh trusty review queue. Is it alright if I review these and potentially accept into proposed? I don't want to mess up any plans you already have13:55
dholbachshadeslayer, ready for the hangout in ~1h?13:56
shadeslayeryep13:56
* shadeslayer is excited and nervous13:56
* dholbach hugs shadeslayer14:13
dholbachall will be fine :)14:13
shadeslayer:D14:14
dokocomponent-mismatches-proposed is frustrating ...14:16
bzoltanmitya57:  ping14:23
bzoltanmitya57:  I would need a friendly licensed maintainer who could review and approve an MR from us against the QtCreator packaging branch: https://code.launchpad.net/~kubuntu-packagers/kubuntu-packaging/qtcreator. The patch is rather simple -> https://code.launchpad.net/~zeller-benjamin/kubuntu-packaging/qtcreator-ubuntudevice-qmlprojects/+merge/228665 It enables ubuntu devices to be Run targets for QML apps.14:28
hallynpitti: do i understand right that cgmanger will start so long as there is a sysv init job but no systemd job;  and if i create a cgmanager.service disabled by default, then it won't start?14:35
* hallyn tries14:38
dokoapw, infinity, ogasawara: I assume we need a MIR for  linux-exynos5 ?14:44
pittihallyn: yes, but the init.d and unit names need to be identical14:45
hallyncan do - thanks14:47
jamespagearges, +1 please go ahead14:47
argesjamespage: ok cool. thanks14:48
infinitydoko: No.14:48
infinitydoko: It shouldn't be in main.14:48
infinitydoko: component-mismatches is lying to you.14:48
argestinoco: jamespage : one concern of the nova upload are if bugs 1219658, 1267191 are fixed in the utopic version of nova (its not entirely clear)14:50
ubottubug 1267191 in nova (Ubuntu) " openstack-nova-compute service fails with - libvirtError: internal error: CPU feature `avx' specified more than once" [Undecided,New] https://launchpad.net/bugs/126719114:50
ubottubug 1219658 in nova (Ubuntu) "Wrong image size using rbd backend for libvirt" [Undecided,In progress] https://launchpad.net/bugs/121965814:50
jamespagearges, lemme check14:50
tinocoarges: checking14:51
hallynpitti: sorr, one more q - is there a .target representing "virtual filesystems (i.e. proc and sys) are mounted" ?14:54
hallynlocal-fs is probably too much / too late;  oh, but maybe fine for cgmanager under systemd, as it's not needed for init there, duh14:55
* xnox loves C++11 static_assert14:57
xnox__linux is not defined, ftw! =)14:57
pittihallyn: that's already defined by basic.target, unless you specify DefaultDependencies=no all units can rely on those15:02
tinocoarges: rbd issue is applied15:04
tinocochecking other15:05
tinocoarges: other fix (cpu feature) is included but in a different source file (test_libvirt* changed to test_config)15:07
tinocoarges: i would say both are already applied to utopic nova-2014.2~215:09
hallynpitti: I want it to start as early as possible15:10
pittihallyn: so not depending on anything will do that15:10
pittihallyn: see man systemd.special: "Usually this should pull-in all mount points, swap devices, sockets, timers, and path units and other basic15:10
hallynpitti: sys and proc will still be mounted?15:11
pitti           initialization necessary for general purpose daemons."15:11
pittihallyn: I suppose you want all those15:11
hallynthe systemd manpages are hard to find :)  not found on my sid or trusty systems;  /me goes to manapges.ubuntu.com15:11
pittierr?15:11
hallynstill not15:11
pitti"man systemd.special"15:12
pittioh, on utopic15:12
hallynNo manual entry for systemd.special15:12
pittiyes, we didn't have systemd on trusty15:12
hallynyeah my utopic system is dead15:12
hallynbut also not found on unstable15:12
hallynoh no, there it is15:12
hallyndidn't find dh_systemd_enable though15:13
pittithat's the dh-systemd build dep15:13
hallynok cool, so now i just need to figure out how to do some scripting before the service starts15:14
pittihallyn: you can do stuff in ExecStartPre=15:15
pitti(man systemd.service for daemons, man systemd.unit for fields which apply to all units)15:15
hallynpitti: thx15:15
argestinoco: ok15:17
=== timrc-afk is now known as timrc
dokoNoskcaj, dholbach: MIR's for jquery needed (or better get rid off this b-d)15:17
dholbachdoko, that's for python-wsme?15:17
dokodholbach, no, that's a separate sync you sponsored15:18
dokohttp://people.canonical.com/~ubuntu-archive/component-mismatches-proposed.svg15:18
dholbachdoko, sorry, which package was that?15:18
dokojquery15:18
dholbachhuh?15:19
dholbachI can't see it here: https://launchpad.net/ubuntu/+source/jquery15:19
dokodholbach, https://launchpad.net/ubuntu/+source/jquery/1.7.2+dfsg-3ubuntu115:20
dholbachah, I was just surprised, because you said "sync" - let me take a second look15:21
dokosorry, merge15:21
hallynpitti: is there a way for a ExecStartPre to tell systemd to simply skip this service (contingnet on output of the command)?  like exit 2 or something?  I don't see it in the manpage15:23
argestinoco: where is the testcase for bug 1219658 ?15:23
ubottubug 1219658 in nova (Ubuntu) "Wrong image size using rbd backend for libvirt" [Undecided,In progress] https://launchpad.net/bugs/121965815:23
tinocoarges: i changed description for "to be provided". i'll create my own tests. bugs were cloned from fedora. i put them together for a ppa (large install) and relied on real tests (fixed both bugs).15:25
xnoxdoko: https://bugs.launchpad.net/ubuntu/+source/gcc-4.9/+bug/134990715:25
ubottuUbuntu bug 1349907 in gcc-4.9 (Ubuntu) "gcc, powerpc with C++11 standard does not define __linux" [Undecided,New]15:25
xnoxdoko: looks like that's the root cause for llvm-3.5/powerpc build failure, and affects debian and ubuntu. And also looks like complete obscure.15:26
argestinoco: can you describe the test case in that SRU section ? it doesn't have to be a script, but some explainination of what steps are required to see the issue15:26
tinocoarges: will do. gimme some minutes, i'll get back to you on this15:27
dokoxnox, please use __linux__15:27
xnoxdoko: sure, but __linux and linux is defined on all other arches, and with a default standard on powerpc.15:28
dokoxnox, and?15:29
xnoxdoko: any preference for __linux__ vs __linux preference? I personally see __linux used for the first time.15:29
doko<doko> xnox, please use __linux__15:30
xnoxdoko: and? -> well it causes FTBFS on powerpc of other packages, and it's not clear to me weather gcc-4.9 with C11 standard enabled is backwards incompatible here on powerpc only, or wether all code is wrong.15:30
xnoxdoko: why is __linux defined at other standards, and on other arches including C11 standard level?15:31
xnoxright, I found https://gcc.gnu.org/bugzilla/show_bug.cgi?id=2831415:32
ubottugcc.gnu.org bug 28314 in target "cpp: x86/powerpc inconsistency for the __linux macro" [Normal,New]15:32
xnoxwhich is good enough reference for me.15:32
xnoxdoko: which looks like reported by you =)15:33
mitya57bzoltan1: approved15:33
xnoxthanks a lot!15:34
dokoxnox, yes, and I won't change it on the package level15:34
xnoxdoko: excellent.15:34
=== charles_ is now known as charles
dokoxnox, what is problem fixing llvm?15:39
xnoxdoko: no problem, wrote a patch, test building and will submit upstream.15:42
xnox(and upload into ubuntu)15:42
mdeslaur@pilot out15:44
=== udevbot changed the topic of #ubuntu-devel to: Archive: open | Devel of Ubuntu (not support or app devel) | build failures -> http://qa.ubuntuwire.com/ftbfs/ | #ubuntu for support and discussion of lucid -> trusty | #ubuntu-app-devel for app development on Ubuntu http://wiki.ubuntu.com/UbuntuDevelopment | See #ubuntu-bugs for http://bit.ly/lv8soi | Patch Pilots:
tinocoarges: changed 1267191 [testcase]. could you please tell bugs 1319710 and 1303536 they are a duplicate of 1267191 ? I keep getting timeouts to mark them duplicate.15:51
ubottubug 1319710 in OpenStack Compute (nova) "Live-migration failed with OpenStack Icehouse and Ubuntu 12.04 " [Undecided,New] https://launchpad.net/bugs/131971015:51
ubottubug 1303536 in OpenStack Compute (nova) "Live migration fails. XML error: CPU feature `wdt' specified more than once" [Medium,Fix released] https://launchpad.net/bugs/130353615:51
argestinoco: technically they aren't targeted to ubuntu/nova, so we don't really need to mark them duplicates15:52
tinocoarges: ah ok, perfect15:53
tinocochecking the rbd testcase (it will be the same as the previous bug since it is a fix to a regression patch)15:53
argestinoco: ok can you update that too please15:54
tinocook15:54
tinocoarges: done.15:57
dholbachdoko, followed up on the merge proposal - thanks15:57
tinocoarges: i think both are ok now, let me know if you need anything else on this. tks!15:57
argestinoco: ok one more thing... did you change the urgency= field in the changelog?16:00
tinocochecking16:00
argesor rather why did you do it16:00
tinocourgency=high16:01
tinocothere were some outages because of these... P1 bug was created to provide fix16:01
argeswhy was it changed from urgency=medium?16:01
tinocoi had to provide this fix in few hours to avoid outage16:01
argestinoco: i don't think that translates to updating the changelog urgency field16:04
rbasakIs it just me, or has dch's default changed recently or something?16:07
rbasakI've seen much more variance in the urgency field recently16:07
xnoxdefault is medium these days.16:08
xnoxused to be low.16:08
xnoxmakes zilch of a difference. (like +/- a couple of build score points, in build queuing in ubuntu)16:08
argestinoco: anyway yea shouldn't make any difference editing that field. no need to modify it now16:09
tinocoarges: ok, tks chris16:09
xnoxtinoco: yeah, but that field is not the semantic meaning you are guessing it has =)16:10
* xnox ponders why i like yoda speak16:10
tinocoxnox: yep. totally agree now. tks guys16:10
argestinoco: np thanks for the fix, its been accepted16:11
mptev, any progress on the database migration?16:12
tinocoarges: great, updating here. tks!16:13
=== psivaa is now known as psivaa-bbl
evmpt: the priority had to be dropped as IS just had to pick up a big project. We're working to make sure we don't put the existing data at risk as this gets put on hold.16:26
rbasakcaribou or arges: please could you take a look at https://bugs.launchpad.net/ubuntu/+source/backuppc/+bug/1349031? Is this a botched merge?16:52
ubottuUbuntu bug 1349031 in backuppc (Ubuntu) "ping6 is not configurable over web ui" [Wishlist,New]16:52
argesrbasak: i know caribou is away on holiday. and i'm trying to remember this one...16:54
argesrbasak: looking at the diff i don't see 'ping6' or 'ipv6' or anything of that sort16:56
rbasakarges: http://paste.ubuntu.com/7896530/ is what I see16:57
rbasakThat's debdiff backuppc_3.3.0-1.dsc backuppc_3.3.0-1ubuntu1.dsc|pastebinit16:57
argesok i was looking at http://launchpadlibrarian.net/162543633/backuppc_3.2.1-4ubuntu2_3.3.0-1ubuntu1.diff.gz16:58
rbasakYeah that diff is against the previous Ubuntu package.16:58
argesyup yup. ok16:58
argesso that merge added functionality; why do you think it was botched?16:59
shadeslayerev: https://errors.ubuntu.com/?user=kubuntu-bugs&period=month still doesn't work16:59
argesadded the ping6 functionality16:59
evshadeslayer: bdmurray just arranged for a deployment containing that change17:00
evshould be up soon17:00
shadeslayerthx :)17:00
rbasakarges: it's not mentioned on the changelog17:00
rbasakarges: it looks to me (superficially, anyway) that Debian or upstream changed something about it, and what Ubuntu had before got carried forward, instead of taking upstream changes.17:00
argesrbasak: yup which is why the diff from the previous ubuntu version doesn't show that change. its a specific ubuntu patch somewhere17:01
rbasakarges: right, but were upstream changes in this area considered for this merge? The missing changelog entry suggests not.17:02
rbasakarges: are we sure that this cannot just be dropped?17:02
rbasakarges: because I see no mention of an addition of anything to do with ping6 in the previous changelog.17:02
rbasakarges: say for example that there was a bug, and upstream fixed it. If we carry forward what we had before, then we'll exclude that.17:03
rbasakarges: that seems to be the simplest explanation to me (at a cursory glance). Either that or a delta was introduced and I haven't found it documented anywhere.17:04
bdmurrayev: i think it has landed but the cronjob may not have run yet17:04
argesrbasak: so I'm not sure with this. I would look at the full changelog to see if this is documented anyway (in the Ubuntu version or Debian version). And if not try dropped it and test to see if we have the same functionality and it fixes that bug17:04
bdmurrayev, shadeslayer: it runs once a day so should work tomorrow17:06
shadeslayerbdmurray: thx17:07
=== Ursinha-afk is now known as Ursinha
=== Ursinha is now known as Ursinha-afk
=== Ursinha-afk is now known as Ursinha
=== roadmr is now known as roadmr_afk
sarnoldTrevinho: smells like a duplicate of something else recently: 134995318:05
sarnoldTrevinho: and another instance of the password going into a previously active client: 134996118:06
dokozul, commented on python-keystonemiddleware. there are a lot more missing MIR's18:41
=== Ursinha-afk is now known as Ursinha
zuldoko:  thanks18:42
=== psivaa-bbl is now known as psivaa
=== roadmr_afk is now known as roadmr
=== Logan__ is now known as Logan_
=== juliank0 is now known as juliank
=== salem_ is now known as _salem
=== _salem is now known as salem_
=== salem_ is now known as _salem
NoskcajScottK, Could you help me with python-wsme's component missmatches?21:59
NoskcajA few releases ago the debian maintainer added build-depends on a few things in universe, which got dropped without a changelog entry when you merged it. I have since had the package synced, and now i can't get the package to build from source because of some tarball strangeness22:02
=== Guest83948 is now known as Adri2000

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