[00:12] DarinMiller: if you look at the status page kconfigwidgets is green [00:12] https://launchpad.net/~kubuntu-ppa/+archive/ubuntu/staging-frameworks/+packages?field.name_filter=kconfigwidgets&field.status_filter=published&field.series_filter=xenial [00:13] yet on LP there is a green cog meaning the package is pending publication [00:14] until the publisher actually runs, the packages that needs it to build have to wait [00:15] it only took 7mins to build, but can take the publisher 20-30mins to actually make the debs available [00:15] no actually it took 3mins 46.9 seconds [00:16] and finished 7 mins ago [00:17] OK, I follow. [00:17] it can be rather frustrating [00:19] wow, lots green already on the xenial frameworks status.... and the red 5.21 stuff is gone. [00:21] DarinMiller: have you still got a Xenial install? [00:21] clivejo: Who initiated the xenial build process? [00:21] yes [00:21] I my current box is XX. [00:21] I did [00:22] we packaged it for YY and have been testing it [00:22] Yes. my YY boxes are running great (no packaging related issues that I have discovered). [00:23] theres a bug with networkmanager Im a bit worried about [00:24] Do you need me to test something? [00:24] I can test or build whatever (but if I need to build, I will require instruction...) [00:25] DarinMiller: Im not sure, it seems to be using the proposed version of nm [00:25] Get:82 http://ftpmaster.internal/ubuntu xenial-proposed/main amd64 libnm0 amd64 1.2.0-0ubuntu0.16.04.2 [353 kB] [00:25] Yes, the proposed version took out my nm. I had to use ovidiuflorin solution to recover it. [00:26] I dont know how to handle it, need yofel's help [00:26] Xenial is an LTS so that needs to be fixed first [00:27] I don't understand your Get:82 line. Look like a hyperlink with spaces in it. [00:28] oh its from the buildlog [00:28] on the status page [00:28] http://qa.kubuntu.co.uk/ppa-status/frameworks/build_status_5.22.0_xenial.html [00:29] next to networkmanager-qt there are two links to logfile [00:29] one is the i386 and the other is amd64 [00:29] thats a link to the buildlog [00:30] so we can see what packages got installed on the clean environment [00:30] that much I understand, it's when I click on those links, I get lost in a hurry. :) [00:31] takes a while to understand how its fits together [00:31] wow kconfigwidgets is taking ages to publish [00:31] clivejo: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.6-yakkety/ is out now, if you want to get off the -rc version. :) [00:31] it finished 23 mins ago [00:32] mamarley: will it go to the archive? [00:32] clivejo: At some point it will become an official release. I don't know the timeline though. [00:33] Im happy enough on this rc [00:33] yofel the http://qa.kubuntu.co.uk/ page has some links that we no longer need I think. Can we make some cleanup there? [00:34] * clivejo sees kconfigwidgets is now published so pokes the other builds [00:34] Get some sleep :) [00:35] LOL yeah, I forgot about the time! [00:35] 1:35am! [00:36] 2:36 :) [00:36] Wow clivejo! [00:36] your in the future! [00:37] :) [00:37] right, Im off to bed, night all [00:38] nn [00:38] night! [04:21] ahoneybun: sgclark valorie: I spoke to Andrew at Digital Ocean, he said to email opensource@digitalocean.com with a request for cloud instances and he can probably help you out [04:25] oh very nice, mhall119! I'll write to the kub-devel ML and get an estimate of what we need/want [04:25] now, before I forget [04:32] done [06:03] +1 [06:15] hi ho [06:57] I guess I lost spectacle somewhere along the way [06:57] when I tried to install, [06:57] The following packages have unmet dependencies: [06:58] kde-spectacle : Depends: libkf5screen6 (>= 5.1.1) but it is not going to be installed [06:58] E: Unable to correct problems, you have held broken packages. [06:58] known problem, or should I file a bug? [06:59] or would it be fixed if I re-enabled staging-plasma and upgraded again? I'm on Plasma 5.6.3 still [07:03] spectacle was uninstallable here as well yesterday. that was on yakkety with the staging ppa all updated to 5.6.4 [07:03] hmmm [07:03] yes, should have mentioned that this was YY [07:03] so updating won't help [07:04] did you report it, acheron88? [07:04] i think clivejo mentioned that probem [07:04] nope. [07:04] or file a bug? [07:04] ok [07:04] figured something just needs a rebuild [07:05] I see that it is failing to build [07:05] and the ppa is for plasma, which works [07:05] right, and it ain't plasma [07:05] I forgot [07:06] ironically ksnapshot installed fine [07:07] sure, it's old [07:07] no changes [07:08] sgclark: mentioned it [07:08] [00:43] uh kde-spectacle want libkscreen [07:10] libkf5screen7 : Breaks: libkf5screen6 but 4:5.5.5-0ubuntu1 is to be installed [07:11] yes, I searched up [07:11] thanks for reminding me [07:11] I've a lot on my mind lately [07:14] morning :) [07:19] hiho renee77 [07:22] Hey [07:23] to upgrade xenial kde to staging, I need only staging-plasma, or staging-plasma, frameworks, apps aded to sources.d? [07:23] vip: only staging-plasma [07:23] soee: thanks [07:23] it contains both Plasma and Frameworks [07:24] I was looking at testing on wiki, is it of value to write to mailing list what is missing? like konq not installed on core system or only bug now? [07:26] i think might be worth both, first file a bug than link it on ml [07:26] ok :) [07:27] I'm curious why Konq should be installed on the core system? [07:28] There was one bug, during install when chosing keyboard layout. Install crashed, couldnt attache linked devices. [07:29] Lol it says so in the checklist valorie I assumed (not a got strategy) it had to do with being major application of kde. (webbrowsing, encryption etc). [07:30] soee: got another question, is your login wait time bug gone? [07:30] vip: i think yes [07:30] I see, renee77 [07:30] soee: lucky you [07:31] that's a judgement call, since Konq is no longer being developed [07:31] nor is Rekonq [07:32] oh i thought renee77 was talkign about drkonqi :) [07:35] I have to learn to bookmark had to work unexpected lost that wiki page [07:38] oh my, we couldn't do without Dr. K [07:38] renee77: check your browser history [07:43] it was from testing Kubuntu current browser history gone Had to work unexpectedly last night. [07:43] srry feeling realy stupid now [07:47] ah it is in the testing introduction for kubuntu [07:49] https://wiki.kubuntu.org/Testing/Kubuntu/Introduction [07:53] renee77: we all forget things [07:53] thanks :) [07:54] wow, that page could probably do with some refreshing [07:54] gosh [07:54] Lol that was the intention of asking if it was still used :) [07:55] well, it's still sound, yes [07:55] but we should copy it into the wiki we're actually using now, and put in more up-to-date tests [07:56] I was looking for a routine to assist and register [07:56] it def. should work though [07:56] ok thank you :) [07:56] renee77: the best way to do, is just what you are doing [07:56] follow your interest, and when you think you can help with something, do it [07:56] ask questions if you need to along the way [07:57] ok I will [07:57] you will find what YOU can do,, that nobody else does so well [07:57] I think most of us started where you are, with just a willing heart [07:59] :) Thanks you, these words are very encouraging [08:00] I know I did, and I still don't do much more than edit stuff, write emails, and help users [08:00] but they let me keep hanging around anyway, LOL [08:01] :D [08:02] * valorie needs to get some sleep [08:02] have a good day, y'all [08:02] sleep well :) [08:47] heya! [08:47] need a ppa to test 5.6 [09:33] * clivejo pokes LP [09:34] hard and in the eyes === oever is now known as vandenoever [09:46] someone on #kubuntu has probs with plasma-discover [09:46] I don't use it, so no idea [09:47] * acheron88 wonders in LP will poke back, or just fall over... [09:47] probably just be stubborn and go extra slow [09:49] regarding discover I dont know [09:59] * mamarley kicks LP. [10:00] finally!! [10:00] kparts is published [10:00] clivejo: Sorry, I just woke up. I can't commit acts of digital violence in my sleep. :p [10:00] * clivejo pokes it again [10:02] * clivejo sings [10:09] me father was a fairy, me mudder a banshee [10:21] ohayō gozaimasu [10:22] huh? [10:26] well learn new words :-) [10:26] https://www.youtube.com/watch?v=a8CQDP13px4 [11:18] http://www.alexl.netsons.org/blogposts/some-new-breeze-app-icons-in-frameworks-5-22/ [11:31] Howdy all [11:37] hi [11:40] well, my Yakkety install is borked again , no plasmashell or any shells are vailable according to the notifications when trying to startx after sddm fails [11:40] available [11:42] ~.>~ [11:47] so far YY has been nthe worst testing OS kubuntu has put out [11:51] to be fair, kubuntu hasn't really 'put out' anything for yaketty yet. [11:56] BluesKaj: And absolutely none of those problems are Kubuntu's fault. Also, you really shouldn't be running the development release this early unless you expect many problems and are confident that you can fix them. [11:56] +1 [11:56] first alpha might be a good starting point [11:57] I toyed with going with yakkety, but have not so far apart from a VM, and so far am glad [11:59] Yeah, I have a VM too. At the moment I don't plan to upgrade any of my real systems until after both GCC 6 and Qt 5.6 have been uploaded and any fallout has been resolved. [12:00] might try on an old intel only laptop on a seperate partition, which it dowsn't matter if I break, but that's as far as I'll go for now. [12:01] mamarley: it's my testing OS, not my regular use OS , I was asked as a tester to report breakage which I'm doing [12:02] xenial, despite some faults, has been pretty stable [12:03] fair enough. think it was the way you phrased your comment.... [12:05] I suppose it was a bit harsh, but true nevertheless [12:05] * clivejo bites tongue [12:06] plasma 5.6.4 , but i do think the kernel module problem with nvidia is also at work here [12:07] sddm is fragile at best [12:08] will lightdm start? [12:08] if that won't either, then something is up with the driver/X [12:08] taking 30mins or more to publish on LP [12:10] the released kernel in Yakkety is broken [12:10] it wont compiled the modules needed to install drivers [12:10] with is nothing to do with Kubuntu or 5.6.4 [12:10] this [12:11] I thought BluesKaj had the fixed 4.6RC7 kernel installed and the patched nvidia? [12:11] maybe not? [12:11] I'm begining to wonder if the switch to systemd hasn't created more problems than it solves ...so far I've had to be nuetral on that debate because I don't know enough about it, but circumstantial evidence sems to point at it [12:13] acheron88: I was going to try the 4.6 rc7 kernel , but adding to the instability at this point in the process isn't a good idea [12:14] BluesKaj: the problem is the kernel [12:14] clivejo: yeah the 4.4.0-22 [12:15] the modules wont build on 4.4.0-21 either [12:16] my nvidia mudules would only build on 4.6rc7 with the patches in mamarley's PPA [12:17] isn't the 4.6 officially released ? [12:17] Ive not seen it in the archive yet [12:17] the 4.6RC7 kernel is pretty solid, and as clivejo says you are not going do get driver modules to build without [12:18] 4.5 final was only yesterday [12:18] *4.6 [12:19] its very unfair blaming us(kubuntu) for something we have absolutely no control over [12:20] I fell into the same hole and got stuck in it for a few days [12:20] not sure if the patch to enable module module builds on yakkety toolchain is in the vanilla kernel.org 4.6 though [12:20] apw has it applied to the 4.6 in the kernel team ppa [12:21] https://linux.slashdot.org/story/16/05/16/0357226/linux-kernel-46-officially-released [12:21] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.6-yakkety/ === alvesadrian is now known as adrian [12:21] has 0002-disable-pie-when-gcc-has-it-enabled-by-default.patch so can't be in the kernel.org source yet then [12:22] soee_: you about? [12:23] clivejo: yup [12:23] do you have a XX to do a test install of Frameworks 5.22? [12:24] yes [12:24] trashable? [12:24] ie non-production? [12:25] i know how to fix things if i broke them :) [12:25] Im just waiting on LP to publish krunner [12:26] https://launchpad.net/~kubuntu-ppa/+archive/ubuntu/staging-frameworks/+packages?field.name_filter=krunner&field.status_filter=published&field.series_filter=xenial [12:26] clivejo: just to clarify , not using the nvidia driver on YY , just the default open source nouveau. I did install plasma 5.6.4 however [12:27] and the staging ppa is commented in the sources.list [12:27] soee_: when that green cog, turns to a green tick can you add the staging-frameworks PPA and do an install test for me please? [12:27] clivejo: yes [12:27] BluesKaj: with that kernel bug, no kernel modules will compile [12:28] I lost my virtualbox module [12:28] * clivejo goes off to find food [12:29] clivejo: thing is that YY was working quite well with nouveau , no flickering or obvious graphics problems [12:29] nouveau 'should' be fine [12:29] yeah , it was [12:29] still is on XX too [12:31] but installing 5.6.4 killed sddm? [12:31] or any graphical startup? [12:32] acheron88: seems so, plus plasmashell , no had to drop to vy/tty to try a login [12:33] no graphical startup [12:33] odd [12:34] well going to try to login again [12:34] bbl [12:34] soee_: krunner published, can you run the test? [12:35] BluesKaj: what error in /var/log/sddm.log if any? [12:35] clivejo: sure [12:35] clivejo: it will remove dbg files: libkf5solid5-dbg libkf5sonnet5-dbg libkf5threadweaver5-dbg plasma-framework-dbg [12:36] is it replacing them with version 6? [12:36] oh they debugging symbols [12:36] probably thinks you dont need them [12:37] clivejo: no [12:37] I think they safe to remove [12:37] and they are not used anymore to collect data when sending reports ? [12:39] soee_: https://launchpad.net/~kubuntu-ppa/+archive/ubuntu/staging-frameworks/+build/9750273 [12:39] looks like they been renamed [12:40] libkf5solid5-dbgsym [12:40] clivejo: xenial box currently on 5.5.5 http://paste.ubuntu.com/16458661/ [12:41] clivejo: so we do not replace them when upgrading frameworks ? [12:41] liek replace plasma-framework-dbg with plasma-framework-dbgsym ? [12:42] its a new debian idea I think [12:42] http://anonscm.debian.org/cgit/pkg-kde/frameworks/solid.git/tree/debian/rules [12:42] yofel: ^ [12:42] not sure how it works [12:42] the debugging packages are being generated automatically [12:43] https://wiki.debian.org/AutomaticDebugPackages [12:44] clivejo: my question is: if people have some xxx-dbg packages installed than they will be removed and users have to install new one again? So there is no way to migrate them to new one automatially? [12:45] soee_: that I dont know [12:45] soee_: apport should reload the debsym pkg (I assume). No need to installed them in advance + their future updates until something crashes [12:46] most users wont have the debugging packages installed [12:46] unless needed to report a bug [12:46] clivejo: so im starting upgrade [12:46] /me see's how much activity has been taking place in devel recently.. and his mind boggles... [12:46] * clivejo crosses fingers [12:46] WoW!! So much I simply do not know [12:48] do-all git merge kubuntu_yakkety_archive [12:49] debsym pkg default in debian since 2016: https://lists.debian.org/debian-devel/2015/12/msg00262.html [12:50] download speed is ~ 120 kB/s :/ [12:53] * clivejo pulls soee_'s button [12:53] pushes [12:54] clivejo: why plasma-framework has 'a' in version ? [12:56] clivejo: 1 error [12:56] dpkg: error processing archive /var/cache/apt/archives/qml-module-org-kde-activities_5.22.0-0ubuntu1~ubuntu16.04~ppa1_amd64.deb (--unpack): [12:56] trying to overwrite '/usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/activities/qmldir', which is also in package qml-module-org-kde-extensionplugin:amd64 5.21.0-0ubuntu1~ubuntu16.04~ppa2 [12:56] http://paste.ubuntu.com/16459040/ [12:56] yup, this one [12:57] Repeating the aptitude upgrade installs the package successfully though. [12:57] oO [12:58] It looks like that file moved from one package in 5.21 to another in 5.22, so installing 5.22 of the first package removes the file which then allows for the clean installation of the file from the other package the second time around. [12:58] Ah, looks like -dgb and -dgbsym.ddeb content is the same, but: -dgbsysm are build on the distro build server (-> always there), are in a different archive ( -> smaller apt update download volume especially for for soee, less load on mirrors) [12:59] mamarley: so what is the proper way to have it working on first attempt ? [12:59] * mamarley isn't sure, sorry. [13:00] allee: so those dub packages are generated on ubuntu servers [13:00] ? [13:00] *dbg [13:01] qml-module-org-kde-activities : Depends: libkf5activities5 (= 5.21.0-0ubuntu1~ubuntu16.04~ppa2) but 5.22.0-0ubuntu1~ubuntu16.04~ppa1 is installed [13:02] soee_: Yeah, that's just a side-effect of the file duplicate error. If you upgrade again, it should go away. [13:02] i had to use -f install [13:02] soee_: that how I understand the info for debian and ubuntu on the web. So no need to update debian/rules for dbg support + extra debug pkg repository [13:03] let m reboot, brb [13:06] and i'm back [13:08] soee: dbgsym.ddeb are automaticly build. -dbg need debian/rules support. With dbgsym on by default -dbg are no longer needed [13:08] ^^ AFAIU up to now ;-) [13:16] Can anyone come up with a fix for that file conflict? [13:25] ok , got a desktop on YY , had to remove the powerdevil dependency in order to get the kubuntu-desktop back [13:27] but the plasmashell is back to 5.5.5 [13:30] clivejo: Besides the file conflict, FW5.22 seems to work fine on Xenial. :) I don't know how to fix the conflict though, sorry. [13:33] clivejo: Perhaps add some sort of dependency trickery to make the package that contains the file in 5.22 conflict with the package that contains the file in 5.21 to ensure the old package will get upgraded before the new one? [13:34] I'm not sure what the "right" way to do these things is. [13:45] Riddell: ping [13:45] hi soee [13:46] Riddell: can you help us with one thing ? [13:46] dunno, what is it? [13:46] this one http://paste.ubuntu.com/16459040/ [13:46] what is the proper way to fix such problems when packaging ? [13:48] qml-module-org-kde-extensionplugin is a transitional dummy package, it shouldn't have any files in it [13:48] clivejo: ^ [13:49] so work out why it has files in it and stop that [14:19] anyone tried: http://www.etcher.io ? [14:22] soee: Looks promising. I used to use unetbootin becayse I used to be terrified of dd, but unetbootin has not worked for me for maybe none months and since then, I have not destroyed my data yet. [14:23] :) [14:52] soee: can you ppa-purge frameworks 5.22 on Xenial? [14:55] * clivejo taps mic [14:55] is this thing on? [14:55] * mamarley drops the mic. [14:55] clivejo: sure [15:02] * clivejo wanders off to mow some grass [15:03] soee: https://launchpad.net/~kubuntu-ppa/+archive/ubuntu/staging-frameworks/+packages?field.name_filter=kactivities-kf5&field.status_filter=published&field.series_filter=xenial [15:03] if kactivities-kf5 ever publishes and gets a tick, will you try installing it again [15:22] yofel: o/ [15:23] yofel: would you mind responding to https://lists.ubuntu.com/archives/ubuntu-motu/2016-May/007860.html please? I know the process is working as designed, but various users seem to be panicking. [15:23] yofel: see what I did with the bug description in bug 1539634 for example. [15:23] bug 1539634 in network-manager (Ubuntu Trusty) "network-manager crashes when using libnl-3-200-3.21.1-1ubuntu1" [High,Fix released] https://launchpad.net/bugs/1539634 [15:23] It's probably users who have proposed enabled but shouldn't. [15:24] yofel: also, if the package in proposed is known bad now, you can ask someone in the SRU team to delete it if that will help (eg. if not all users with proposed enabled have updated to it, then that might stop those users being hit) [15:25] yofel: I hope that helps. I haven't done anything myself to avoid stepping on your toes, but if you'd like me to do something, just let me know. [15:29] clivejo: [15:29] dpkg: error processing archive /var/cache/apt/archives/qml-module-org-kde-activities_5.22.0-0ubuntu1~ubuntu16.04~ppa2_amd64.deb (--unpack): [15:29] trying to overwrite "/usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/activities/libkactivitiesextensionplugin.so", which is also in package qml-module-org-kde-extensionplugin:amd64 5.21.0-0ubuntu1~ubuntu16.04~ppa2 [15:31] clivejo: so similar issue ? [15:32] ok this breakis harde rto fix [15:34] clivejo: i have reverted to FW 5.21 will test again when this problem is fixed :) [16:38] * clivejo throws stuff around [16:41] :D [16:43] soee: can you purge and try again? [16:43] Ill need help if this time doesnt fix it [16:44] oh, need to wait til it publishes [16:44] i purged before [16:45] If I go crazy then will you still call me superman [16:47] * clivejo sings [17:09] * BluesKaj wonders if he dares go back and give plasma 5.6.4 another try ;P [17:10] Soee can you try again please? [17:10] already doing it :) [17:12] Mind reader! [17:12] dpkg: error processing archive /var/cache/apt/archives/qml-module-org-kde-activities_5.22.0-0ubuntu1~ubuntu16.04~ppa2_amd64.deb (--unpack): [17:12] trying to overwrite '/usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/activities/libkactivitiesextensionplugin.so', which is also in package qml-module-org-kde-extensionplugin:amd64 5.21.0-0ubuntu1~ubuntu16.04~ppa2 [17:12] Ffs [17:12] mm [17:13] that extensionplugin should not be in that package [17:13] Please help!! [17:14] afraid I am leaving for a bit, will when I get back [17:14] Ah no prob [17:34] @Cliff if we finish FW 5.22 and than build Plasma 5.6.4 against it, will they be ready to move to backports ppa? [17:39] clivejo: qml-module-org-kde-extensionplugin -ppa3 doesn't contain any files it shouldn't. The problem is that -ppa2 and before did contain the libkactivitiesextensionplugin.so file, so when qml-module-org-kde-activities (which now contains that file) gets upgraded before qml-module-org-kde-extensionplugin, the file conflict occurs. [17:59] mamarley: so I need to add a breaks/replace for qml-module-org-kde-extensionplugin? [18:00] clivejo: Now that I look again, soee was actually installing the -ppa2 version. [18:00] I am purging one of my systems so that I can repeat the test with -ppa3. [18:01] I tried old one? [18:01] the file has moved from qml-module-org-kde-extensionplugin to qml-module-org-kde-extensionplugin [18:01] It was after package has been published [18:01] The error message you posted indicates -ppa2 for your packages, so yes. [18:01] Let me try again [18:02] so qml-module-org-kde-extensionplugin should be an empty transitional dummy package now, depending on qml-module-org-kde-activities [18:02] * clivejo sniffs [18:03] and I think I stepped in dog poo [18:03] It is already an empty package in the -ppa3 version. [18:05] clivejo: now all was fine :) [18:06] clivejo: Yeah, looks that way here too. An upgrade from the FW5.21 in staging-plasma to FW5.22 in staging-frameworks has 0 errors. [18:06] Time for plasma. :) [18:06] http://paste.ubuntu.com/16466095/ [18:07] *shakes fist at soee* [18:07] Scarin the bejayus outta me [18:08] * soee blames LP for beeing lazy [18:09] clivejo: You do an awesome job, thanks! :) [18:10] would someone mind testing an install of frameworks 5.22 from the staging ppa on dev aka Yak [18:10] I pushed the same update for it as well [18:11] clivejo: Sorry, the laptop on which my VM runs fell off the network earlier and I can't get to it anymore. :( [18:12] soee: regarding your 5.22.0a question, KDE spun those tarballs [18:13] I had introduced the original source to LP, therefore if you change the source code you have to change the version number [18:13] soee: you should sub to the release ML [18:16] soee: Im guessing you already found http://qa.kubuntu.co.uk/ppa-status/plasma/build_status_5.6.4_xenial.html [18:16] clivejo: But I will be more than willing to test Yakkety again once I get home and reset my laptop. [18:16] mamarley: not a problem [18:17] it *should* be resolved there [18:17] just wanted to confirm [18:18] anyone tried the daily yakkety iso? [18:20] Stupid green gear. [18:20] Not in last 3 days - before couldn't install in VB [18:48] mm when can we get KDE Telepathy working again? [18:48] its been broken since 15.10 at least [18:51] * mamarley kicks LP. [18:52] ovidiuflorin said we are just missing packages [18:52] Ooh, it worked! As soon as I kicked it, some packages started compiling! [18:53] I thought it was broken until the components are ported to kf5? [18:53] I said what? [18:53] I think it should work [18:53] mamarley: keep kicking it! [18:53] * mamarley kicks LP. [18:53] * mamarley kicks LP. [18:57] * ahoneybun upgrades [18:58] ahoneybun: upgrade to what? [18:58]