| acheronuk | and off it goes | 00:01 |
|---|---|---|
| Snowhog | acheronuk: Just did an apt-get update && apt-get dist-upgrade on my 16.04 VM. plasma-discover-updater was included in the 19 packages for upgrade. The description on that package doesn't state it's a dummy package at all. | 00:03 |
| -kubuntu-ci:#kubuntu-devel- Project merger_kdesdk-thumbnailers build #102: FAILURE in 3 min 28 sec: http://kci.pangea.pub/job/merger_kdesdk-thumbnailers/102/ | 00:04 | |
| -kubuntu-ci:#kubuntu-devel- Yippee, build fixed! | 00:04 | |
| -kubuntu-ci:#kubuntu-devel- Project merger_kcoreaddons build #776: FIXED in 3 min 30 sec: http://kci.pangea.pub/job/merger_kcoreaddons/776/ | 00:04 | |
| Snowhog | acheronuk: Never mind! Didn't read your comment correctly. :/ | 00:05 |
| acheronuk | Snowhog: muon-updater is the transitional dummy pkg | 00:05 |
| acheronuk | oh. ok | 00:05 |
| -kubuntu-ci:#kubuntu-devel- Project mgmt_merger build #696: STILL UNSTABLE in 7 min 25 sec: http://kci.pangea.pub/job/mgmt_merger/696/ | 00:08 | |
| -kubuntu-ci:#kubuntu-devel- Project mgmt_progenitor build #682: STILL UNSTABLE in 7 min 28 sec: http://kci.pangea.pub/job/mgmt_progenitor/682/ | 00:08 | |
| Snowhog | As to Muon Package Manager. IF on has Release upgrade set to Normal Releases, then when a new release is available, then Full Upgrade becomes 'active'; turns Green at here. Otherwise, it remains greyed out. So you don't get a pop-up notification, but you can do a distribution full upgrade. Now I don't ever do such from a GUI anyway. I do all of my package management from the CLI. | 00:13 |
| Snowhog | ^^IF one has | 00:13 |
| acheronuk | "Full upgrade" button in Muon here just simply upgrades all packages that can be in the current distribution. It does not do an actual distribution upgrade. | 00:19 |
| Snowhog | Hmm. As I haven't actually clicked on Full Upgrade (when I had Release upgrade set to Normal Releases), I can't confirm that, but I'll take you at your word. | 00:21 |
| acheronuk | just tried it to make sure | 00:22 |
| acheronuk | and now there are no normal updates for xenial left, it is greyed out again. | 00:22 |
| Snowhog | So then, it was the muon-updater package -- before it became a dummy to plasma-discover-updater -- did the deed when Release upgrade was set to Normal Releases. | 00:24 |
| -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kppp build #88: STILL UNSTABLE in 15 min: http://kci.pangea.pub/job/yakkety_unstable_kppp/88/ | 00:25 | |
| -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdesdk-kioslaves build #85: STILL UNSTABLE in 22 min: http://kci.pangea.pub/job/xenial_unstable_kdesdk-kioslaves/85/ | 00:32 | |
| -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdesdk-kioslaves build #46: STILL UNSTABLE in 23 min: http://kci.pangea.pub/job/yakkety_unstable_kdesdk-kioslaves/46/ | 00:32 | |
| -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kppp build #11: STILL UNSTABLE in 23 min: http://kci.pangea.pub/job/xenial_unstable_kppp/11/ | 00:32 | |
| Snowhog | acheronuk: Searching Muon Package Manager (which has issues displaying filtered searches -- still) finds that update-manager-kde; NOT installed in my 16.04 VM; provides "Support modules for Muon Notifier and Apper to check for new distro releases and download the dist-upgrade tool." | 00:39 |
| -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kopete build #88: STILL UNSTABLE in 31 min: http://kci.pangea.pub/job/xenial_unstable_kopete/88/ | 00:41 | |
| -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kde-runtime build #204: STILL FAILING in 30 min: http://kci.pangea.pub/job/xenial_unstable_kde-runtime/204/ | 00:41 | |
| valorie | https://vizzzion.org/blog/2016/10/plasmas-road-ahead/ - including a proposed release calendar | 00:49 |
| -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kcoreaddons build #267: STILL UNSTABLE in 22 min: http://kci.pangea.pub/job/xenial_unstable_kcoreaddons/267/ | 00:55 | |
| -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kde-runtime build #210: STILL FAILING in 45 min: http://kci.pangea.pub/job/yakkety_unstable_kde-runtime/210/ | 00:55 | |
| -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kopete build #65: STILL UNSTABLE in 46 min: http://kci.pangea.pub/job/yakkety_unstable_kopete/65/ | 00:55 | |
| -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdevelop-pg-qt build #22: STILL UNSTABLE in 23 min: http://kci.pangea.pub/job/yakkety_unstable_kdevelop-pg-qt/22/ | 00:56 | |
| -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kauth build #157: STILL UNSTABLE in 24 min: http://kci.pangea.pub/job/yakkety_unstable_kauth/157/ | 00:56 | |
| * tsimonq2 yawns | 00:59 | |
| ScottK | clivejo: if the button you click on to start the upgrade is part of plasma-discover then I disagree with the comment. | 01:01 |
| tsimonq2 | valorie: You upgrade to Zesty yet? XD | 01:02 |
| valorie | I'm thinking about it | 01:02 |
| valorie | it seems a bit crazy in retrospect to have run YY since day one on my production machine, but it did work out this release | 01:03 |
| -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kde-runtime build #205: STILL FAILING in 17 min: http://kci.pangea.pub/job/xenial_unstable_kde-runtime/205/ | 01:03 | |
| -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_okular build #21: STILL UNSTABLE in 31 min: http://kci.pangea.pub/job/xenial_unstable_okular/21/ | 01:04 | |
| -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_okular build #99: STILL UNSTABLE in 32 min: http://kci.pangea.pub/job/yakkety_unstable_okular/99/ | 01:04 | |
| mparillo | Nothing here: http://cdimage.ubuntu.com/kubuntu/daily-live/ Or do you sed /etc/apt/sources.list ? | 01:04 |
| mamarley | Wait, is Zesty even installable yet? | 01:04 |
| acheronuk | https://launchpad.net/ubuntu/+source/base-files/9.6ubuntu6 | 01:05 |
| valorie | and wow, as soon as I say that, yakuake crashes | 01:06 |
| valorie | weird | 01:06 |
| valorie | wasn't using it | 01:06 |
| tsimonq2 | valorie: I'm running it! :D | 01:06 |
| valorie | mparillo: that's how I did it for YY - sed | 01:06 |
| valorie | tsimonq2: bravo, young sir | 01:07 |
| tsimonq2 | valorie: And of course I'm back in the channel... | 01:07 |
| * tsimonq2 kicks clivejo :P | 01:07 | |
| mparillo | mamarley: So now I know how valorie got YY a day before I did. | 01:07 |
| * valorie is not feeling so wild and crazy today | 01:08 | |
| * mamarley will probably upgrade once 5.8 is staged. :p | 01:09 | |
| -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kcrash build #278: STILL UNSTABLE in 18 min: http://kci.pangea.pub/job/xenial_unstable_kcrash/278/ | 01:13 | |
| -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kauth build #285: STILL UNSTABLE in 18 min: http://kci.pangea.pub/job/xenial_unstable_kauth/285/ | 01:13 | |
| -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kcrash build #154: STILL UNSTABLE in 17 min: http://kci.pangea.pub/job/yakkety_unstable_kcrash/154/ | 01:13 | |
| valorie | mamarley: I would 100% do it then | 01:14 |
| valorie | today is colonoscopy prep day, so ..... | 01:14 |
| mamarley | Got to have my KDE Krack. :) | 01:15 |
| valorie | I'm looking forward to the future with a smile on my face, believe me | 01:15 |
| * tsimonq2 needs a Debian Developer | 01:17 | |
| tsimonq2 | Anyone know someone who would be willing to upload a new package to Sid for me? ;) | 01:17 |
| tsimonq2 | I will owe beer when I can legally buy it for them... | 01:18 |
| -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kde-runtime build #211: STILL FAILING in 19 min: http://kci.pangea.pub/job/yakkety_unstable_kde-runtime/211/ | 01:19 | |
| tsimonq2 | Mirv: When is your next planned Qt transition? | 01:23 |
| -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kwallet build #292: STILL UNSTABLE in 15 min: http://kci.pangea.pub/job/xenial_unstable_kwallet/292/ | 01:51 | |
| -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kwallet build #131: STILL UNSTABLE in 14 min: http://kci.pangea.pub/job/yakkety_unstable_kwallet/131/ | 01:58 | |
| Snowhog | acheronuk: Yup, installing update-manager-kde and setting Release upgrade to Normal Releases and logging out and rebooting, once I was logged in to the Deskop, a a pop-up notifier appeared telling me there was a new distribution to upgrade to. | 02:42 |
| -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_spectacle build #108: STILL UNSTABLE in 10 min: http://kci.pangea.pub/job/xenial_unstable_spectacle/108/ | 03:05 | |
| -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_spectacle build #87: STILL UNSTABLE in 10 min: http://kci.pangea.pub/job/yakkety_unstable_spectacle/87/ | 03:06 | |
| -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kstars build #259: STILL UNSTABLE in 23 min: http://kci.pangea.pub/job/xenial_unstable_kstars/259/ | 03:21 | |
| -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_umbrello build #94: STILL UNSTABLE in 23 min: http://kci.pangea.pub/job/xenial_unstable_umbrello/94/ | 03:21 | |
| -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_okteta build #116: STILL UNSTABLE in 26 min: http://kci.pangea.pub/job/xenial_unstable_okteta/116/ | 03:31 | |
| -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_umbrello build #79: STILL UNSTABLE in 20 min: http://kci.pangea.pub/job/yakkety_unstable_umbrello/79/ | 03:31 | |
| -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kstars build #127: STILL UNSTABLE in 27 min: http://kci.pangea.pub/job/yakkety_unstable_kstars/127/ | 03:38 | |
| -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_plasma-framework build #150: STILL FAILING in 16 min: http://kci.pangea.pub/job/yakkety_unstable_plasma-framework/150/ | 03:39 | |
| -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_libkcompactdisc build #50: STILL UNSTABLE in 13 min: http://kci.pangea.pub/job/xenial_unstable_libkcompactdisc/50/ | 03:45 | |
| -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_ktp-common-internals build #136: STILL UNSTABLE in 23 min: http://kci.pangea.pub/job/yakkety_unstable_ktp-common-internals/136/ | 03:45 | |
| -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_ktp-common-internals build #210: STILL UNSTABLE in 23 min: http://kci.pangea.pub/job/xenial_unstable_ktp-common-internals/210/ | 03:45 | |
| -kubuntu-ci:#kubuntu-devel- Yippee, build fixed! | 03:46 | |
| -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_plasma-framework build #285: FIXED in 23 min: http://kci.pangea.pub/job/xenial_unstable_plasma-framework/285/ | 03:46 | |
| -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_plasma-framework build #151: STILL FAILING in 14 min: http://kci.pangea.pub/job/yakkety_unstable_plasma-framework/151/ | 03:58 | |
| -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kirigami build #36: STILL UNSTABLE in 24 min: http://kci.pangea.pub/job/xenial_unstable_kirigami/36/ | 04:10 | |
| -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_ktp-auth-handler build #184: STILL UNSTABLE in 24 min: http://kci.pangea.pub/job/xenial_unstable_ktp-auth-handler/184/ | 04:10 | |
| -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_ktp-auth-handler build #137: STILL UNSTABLE in 24 min: http://kci.pangea.pub/job/yakkety_unstable_ktp-auth-handler/137/ | 04:10 | |
| -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_akonadi-contacts build #41: STILL UNSTABLE in 18 min: http://kci.pangea.pub/job/xenial_unstable_akonadi-contacts/41/ | 04:10 | |
| -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kirigami build #40: STILL UNSTABLE in 12 min: http://kci.pangea.pub/job/yakkety_unstable_kirigami/40/ | 04:11 | |
| -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_plasma-mediacenter build #187: STILL UNSTABLE in 24 min: http://kci.pangea.pub/job/xenial_unstable_plasma-mediacenter/187/ | 04:11 | |
| -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kwin build #5: STILL FAILING in 1 min 21 sec: http://kci.pangea.pub/job/xenial_unstable_kwin/5/ | 04:11 | |
| -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_plasma-mediacenter build #104: STILL UNSTABLE in 12 min: http://kci.pangea.pub/job/yakkety_unstable_plasma-mediacenter/104/ | 04:11 | |
| -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kwin build #6: STILL FAILING in 42 sec: http://kci.pangea.pub/job/xenial_unstable_kwin/6/ | 04:17 | |
| -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kwin build #5: STILL FAILING in 47 sec: http://kci.pangea.pub/job/yakkety_unstable_kwin/5/ | 04:17 | |
| -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_akonadi-calendar build #5: STILL UNSTABLE in 11 min: http://kci.pangea.pub/job/yakkety_unstable_akonadi-calendar/5/ | 04:22 | |
| -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_plasma-sdk build #229: STILL UNSTABLE in 11 min: http://kci.pangea.pub/job/xenial_unstable_plasma-sdk/229/ | 04:22 | |
| -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_plasma-sdk build #123: STILL UNSTABLE in 11 min: http://kci.pangea.pub/job/yakkety_unstable_plasma-sdk/123/ | 04:22 | |
| -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_plasma-integration build #5: STILL UNSTABLE in 12 min: http://kci.pangea.pub/job/xenial_unstable_plasma-integration/5/ | 04:22 | |
| -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kwin build #6: STILL FAILING in 46 sec: http://kci.pangea.pub/job/yakkety_unstable_kwin/6/ | 04:23 | |
| -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_plasma-integration build #5: STILL UNSTABLE in 10 min: http://kci.pangea.pub/job/yakkety_unstable_plasma-integration/5/ | 04:28 | |
| -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_discover build #5: STILL UNSTABLE in 11 min: http://kci.pangea.pub/job/yakkety_unstable_discover/5/ | 04:33 | |
| -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdepim-addons build #5: STILL FAILING in 42 sec: http://kci.pangea.pub/job/yakkety_unstable_kdepim-addons/5/ | 04:48 | |
| -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdepim-addons build #6: STILL FAILING in 1 min 9 sec: http://kci.pangea.pub/job/yakkety_unstable_kdepim-addons/6/ | 04:54 | |
| -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdepim-addons build #72: STILL FAILING in 37 sec: http://kci.pangea.pub/job/xenial_unstable_kdepim-addons/72/ | 05:03 | |
| -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdepim-addons build #73: STILL FAILING in 36 sec: http://kci.pangea.pub/job/xenial_unstable_kdepim-addons/73/ | 05:09 | |
| Mirv | tsimonq2: unfortunately only January-February for Qt 5.7.1. of course it's not released yet either, but I need to work on some snappy stuff and Qt 5.6.2 first, and I will be gone for several weeks before the end of year. | 06:42 |
| Mirv | and I lost several days in trying to find a solution for the arm64 problem that happens if using 4.4 kernel on builders. https://codereview.qt-project.org/#/c/169892 is supposedly the fix but it does not solve all errors. meanwhile, a workarounded kernel is now installed on builders but I'm a bit puzzled... I ended up piling 5+ patches from upstream and trying even the 5.7 | 06:44 |
| Mirv | 's arm64 JIT support, but none gave similarly error-free results than simple 5.6.1 with earlier kernel (or the kernel flag reverted) | 06:44 |
| acheronuk | :) http://i.imgur.com/ucIpoXH.png | 07:33 |
| sheytan | Hey, just upgraded and akonadi doesn't work. Know problem? | 07:37 |
| sheytan | http://imgur.com/a/OjFch | 07:42 |
| acheronuk | sheytan: try 'sudo mkdir /var/lib/mysql-files' | 08:01 |
| sheytan | acheronuk: works, thank you ;) But this should be fixed | 08:11 |
| jimarvan | good morning :) | 08:17 |
| -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » swy-01 build #1050: FAILURE in 3 min 47 sec: http://kci.pangea.pub/job/mgmt_docker/label=swy-01/1050/ | 09:48 | |
| yofel | o.O | 09:49 |
| -kubuntu-ci:#kubuntu-devel- Yippee, build fixed! | 09:53 | |
| -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » swy-01 build #1051: FIXED in 2 min 42 sec: http://kci.pangea.pub/job/mgmt_docker/label=swy-01/1051/ | 09:53 | |
| jimarvan | :D | 09:56 |
| jimarvan | hmm do we still have kubuntu hoodies? | 09:56 |
| jimarvan | I want to buy one! | 09:56 |
| santa_ | clivejo: what have you done in the discover git? | 10:11 |
| jimarvan | I hope he destroyed it | 10:14 |
| jimarvan | I really dislike discover... I want muon back :( | 10:14 |
| santa_ | jimarvan: not on the mood for that kind of jokes, and if you want it back, go maintain it | 10:17 |
| soee_ | o/ | 10:18 |
| santa_ | o/ | 10:18 |
| soee_ | discover with kirigami interface isn't that bad but it needs some love still to polish styles and few other things | 10:18 |
| jimarvan | :O | 10:23 |
| jimarvan | sorry santa_! | 10:23 |
| jimarvan | guys in launchpad if i change my username | 10:33 |
| jimarvan | I guess it will have an impact on what I will be doing with that account right? might risk been locked out, is that correct? | 10:34 |
| IrcsomeBot | <CliffordTheBigRedDoggie> Santa_ I have done anything with it just yet | 10:36 |
| IrcsomeBot | <CliffordTheBigRedDoggie> Havent | 10:36 |
| santa_ | well, apparently someone screwed and very bad the compatibility of our git repositories with debian | 10:39 |
| santa_ | now the master branches of a couple of plasma packages doesn't point where they are suposed to point | 10:39 |
| santa_ | and I suspect all the other plasma packages are affected | 10:40 |
| santa_ | aha | 10:41 |
| yofel | jimarvan: you can change your display name, but the ID can only be changed when there's no PPAs. That's how it was in the past at least | 10:41 |
| santa_ | tsimonq2: https://git.launchpad.net/~kubuntu-packagers/kubuntu-packaging/+git/kgamma5/commit/?id=ff4527edeedb711856b55c8d41d9e5baaa94f797 | 10:41 |
| santa_ | ↑ could you explain this please? | 10:42 |
| jimarvan | thanks yofel! | 10:43 |
| yofel | how does that screw with out debian compatibility at all? | 10:43 |
| yofel | we are not mirroring debian | 10:43 |
| yofel | *with our | 10:44 |
| santa_ | well the master branch must track debian's master branch, otherwise we can't merge properly | 10:44 |
| yofel | no it doesn't | 10:44 |
| santa_ | yes it does | 10:44 |
| yofel | you don't need to merge 'master', you can merge 'debian/master' just fine | 10:44 |
| yofel | that's what remotes are for | 10:44 |
| santa_ | so basically our master branches are now incompatible. great | 10:45 |
| IrcsomeBot | <CliffordTheBigRedDoggie> I asked Simon to look into a way of cleanly copying yakkety_archive into master. | 10:46 |
| yofel | uhm, I still don't quite get the problem, care to explain? | 10:46 |
| IrcsomeBot | <CliffordTheBigRedDoggie> I also asked him NOT to push it until we reviewed | 10:46 |
| yofel | I was suggesting using master for dev a couple days ago, clearly saying that I didn't think about all possible downsides | 10:47 |
| yofel | but I don't remember any part of our workflow that involves our master branch | 10:47 |
| yofel | at least I haven't used them at all since the move to LP | 10:47 |
| santa_ | <CliffordTheBigRedDoggie> I asked Simon to look into a way of cleanly copying yakkety_archive into master. | 10:48 |
| santa_ | why? | 10:48 |
| IrcsomeBot | <CliffordTheBigRedDoggie> Because I agree with Phil about using master to track dev | 10:49 |
| santa_ | "to track dev" | 10:49 |
| yofel | ok, so the problem was that someone wanted to stage some work for the dev release to be able to make backports for the released stuff | 10:49 |
| IrcsomeBot | <CliffordTheBigRedDoggie> To put our unreleased stuff | 10:50 |
| yofel | with ZZ not having been initialized, there was no place to do that | 10:50 |
| santa_ | yes it is | 10:50 |
| santa_ | kubuntu_yakkety_backports | 10:50 |
| yofel | and there's the fact that having the PPA code in _archive is seriously annoying when working on the archive | 10:50 |
| santa_ | that's what scarler was using in that situations | 10:50 |
| santa_ | * scarlett | 10:51 |
| yofel | yes, and the following forward-merges always messed things up | 10:51 |
| IrcsomeBot | <CliffordTheBigRedDoggie> The use of master makes more sense to me | 10:51 |
| santa_ | which breaks the compatiblity with debian | 10:51 |
| yofel | so I *suggested* using master for it's intended purpose | 10:51 |
| yofel | how?!? | 10:51 |
| yofel | nowhere in our wokflow should master have been used at all | 10:52 |
| IrcsomeBot | <CliffordTheBigRedDoggie> I don't understand how it breaks debian | 10:52 |
| santa_ | you can't pull the debian master branch properly | 10:52 |
| yofel | it always contained outdated debian code, that was just duplicated from debian | 10:52 |
| IrcsomeBot | <CliffordTheBigRedDoggie> Sure you can | 10:52 |
| santa_ | can you do this: git checkout master; git pull debian master ? | 10:52 |
| santa_ | properly? | 10:52 |
| yofel | uh... 'git remote add debian ...', 'git fetch debian', 'git merge debian/master' | 10:53 |
| yofel | that's what I usually do if I need to merge something from debian for other projects | 10:53 |
| yofel | I never set up a local remote tracking branch for the debian remote | 10:53 |
| santa_ | so you can't use the master branch properly. great | 10:53 |
| yofel | define "properly"? The proper use of 'master' in git is to track the main development of *your project* | 10:54 |
| santa_ | unless you are the downstream of *other project* | 10:55 |
| yofel | like I don't even get why you would go and merge debian master into ours, there should be nothing to merge as it should always be a fast-forward rebase | 10:55 |
| * soee_ https://goo.gl/5WhTkL | 10:56 | |
| yofel | yes, so...? that's what remotes are for? that's the same thing we have to do when taking something from neon or vice-versa? | 10:56 |
| santa_ | git checkout master; git pull debian master; git checkout kubuntu_zesty_archive; git merge master | 10:56 |
| yofel | leave the first thing away, make the 2nd git fetch debian, and the last git merge debian/master | 10:56 |
| yofel | done | 10:56 |
| yofel | git doesn't care where stuff is, as long as it knows how to track it | 10:57 |
| IrcsomeBot | <CliffordTheBigRedDoggie> I don't get why would need a copy of Debian master in our repo | 10:57 |
| IrcsomeBot | <tsimonq2> Doing that merge would *always* break anyways afair, we have different Vcs-* fields | 10:57 |
| santa_ | so you are breaking the current workflow and the compatibility with debian's branches | 10:57 |
| IrcsomeBot | <tsimonq2> We have no current Git workflow with Debian. | 10:58 |
| acheronuk | it's only there as debian master as a historical anomaly from switching repo's AFAIK | 10:58 |
| IrcsomeBot | <tsimonq2> Correct. | 10:58 |
| yofel | first thing I'll agree with to - to fix issues with the current one, 2nd not so much | 10:58 |
| acheronuk | never any intention to keep that in sync with debian master | 10:59 |
| santa_ | awesome | 11:00 |
| santa_ | well, whatever, I have other things to do. let me know whats the current workflow, no matter how much broken it is and I will adapt myself as usual | 11:01 |
| santa_ | oh and the by the way | 11:07 |
| jimarvan | :) | 11:08 |
| acheronuk | jimarvan: I changed my ID the other week :) | 11:08 |
| santa_ | in case you haven't noticed, doing git checkout b; git merge a doesn't mean the branch a and b have the same contents | 11:08 |
| santa_ | therefore | 11:09 |
| santa_ | <CliffordTheBigRedDoggie> I asked Simon to look into a way of cleanly copying yakkety_archive into master. | 11:09 |
| jimarvan | thanks acheronuk! ;) | 11:09 |
| santa_ | https://git.launchpad.net/~kubuntu-packagers/kubuntu-packaging/+git/kgamma5/commit/?id=ff4527edeedb711856b55c8d41d9e5baaa94f797 | 11:09 |
| santa_ | ↑ FAIL | 11:09 |
| santa_ | just sayin | 11:09 |
| tsimonq2 | yofel, clivejo, acheronuk: you guys think I messed up there? ^ | 11:10 |
| santa_ | if someone messed up was the entire team | 11:11 |
| santa_ | we had a workflow, if you want to change it, change it properly | 11:11 |
| acheronuk | tsimonq2: well, clivejo said specifically not to push to git. to just investigate | 11:12 |
| tsimonq2 | acheronuk: Yes, and that's my fault. | 11:13 |
| clivejo | I had my reasons for saying not to do it | 11:13 |
| acheronuk | tsimonq2: we need a clean copy of yakkety_archive as master if it is to be done at all. if that was not achieved, then it's a problem | 11:13 |
| tsimonq2 | clivejo, acheronuk: would you guys please be able to accomplish that while I'm at school? | 11:14 |
| clivejo | 1) I wanted to let you investigate and learn about git 2) I wanted you to come back with the results and see it it would even work proper (I knew a merge would break things) | 11:15 |
| yofel | it looks like you just did a merge, which would end up with the wrong result as some master branches aren't fully merged in kubuntu_ | 11:15 |
| acheronuk | tsimonq2: I was going to discuss and look at our branches with clivejo later anyway, so just another item to sort I suppose | 11:15 |
| tsimonq2 | Please do. :) | 11:15 |
| clivejo | 3) I wanted us all to get together in BBB and do it, so everyone had a chance to raise concerns | 11:15 |
| acheronuk | yofel: can we nuke what was done and start over? | 11:16 |
| tsimonq2 | clivejo: 1) I know about Git. :P | 11:16 |
| clivejo | 4) I wanted to do all the repos in in one clean pass | 11:16 |
| tsimonq2 | clivejo: 2) I proposed a planning metting... :/ | 11:16 |
| tsimonq2 | *meeting | 11:17 |
| yofel | lets not touch this until we know what we'll do | 11:17 |
| yofel | as fixing this might require a force-push - reverting the change would screw up future merges | 11:17 |
| acheronuk | 4) yes, doing them piecemeal in several parts is bound to end up a mess | 11:17 |
| santa_ | <yofel> lets not touch this until we know what we'll do | 11:18 |
| clivejo | the reason I asked you was because you had experience with pulling all the git repos from LP | 11:18 |
| santa_ | +1 | 11:18 |
| acheronuk | yofel: will you be available later at all to have a chat on BBB with us? | 11:18 |
| clivejo | and I have never done that | 11:18 |
| yofel | acheronuk: not until friday | 11:18 |
| clivejo | we would all learn from the experience and transfer skills | 11:18 |
| acheronuk | yofel: what about creating zesty_archive branches? that at least is not a trauma | 11:19 |
| tsimonq2 | ^ heh | 11:20 |
| yofel | that you can do ;) | 11:20 |
| acheronuk | tsimonq2: you = _we_ on that | 11:20 |
| clivejo | talk to each other, scratch heads, rubber duck stuff | 11:21 |
| clivejo | I have to go push more paper | 11:21 |
| tsimonq2 | acheronuk: dude I'm doing homework than going to school | 11:21 |
| clivejo | stupid EU rules | 11:22 |
| tsimonq2 | ping me throughout the day and I'll respond within an hour | 11:22 |
| tsimonq2 | s/than/then/ | 11:23 |
| santa_ | my suggestion here is: | 11:25 |
| santa_ | 1) don't touch master more until the meeting | 11:25 |
| santa_ | 2) keep using the old workflow (which doesn't need to push things to master) until the meeting | 11:26 |
| santa_ | and that's it | 11:26 |
| tsimonq2 | clivejo, acheronuk: thoughts? ^ | 11:33 |
| acheronuk | at the moment I'm thinking "mmmm donuts" | 11:35 |
| tsimonq2 | Ok, I'm off o/ | 11:37 |
| BluesKaj | Hiyas all | 12:45 |
| jimarvan | Hey BluesKaj!!! :D | 12:49 |
| BluesKaj | Hi jimarvan :-) | 12:50 |
| Mirv | tsimonq2: anyway, as soon as 5.7.1 is out, silo 1985 is there that could be filled for zesty. 5.7.0 is partially done in the ubuntu+1 branches, and of course many will come directly without modifications from debian. | 14:13 |
| Mirv | I'm just not certain on the schedule of 5.7.1 being out and me having time to work on it | 14:14 |
| soee_ | anyone tried CLP ? | 14:49 |
| soee_ | *CLS | 14:50 |
| CRogers | I get the feeling people on the mailing list patently dislike the chameleon logo. lol | 15:18 |
| CRogers | oops, wrong window. lol | 15:19 |
| IrcsomeBot | <tsimonq2> o/ | 17:24 |
| IrcsomeBot | <tsimonq2> Anybody around? | 17:25 |
| IrcsomeBot | <acheronuk> @tsimonq2, no | 17:25 |
| * mamarley isn't here either. | 17:26 | |
| IrcsomeBot | <tsimonq2> Lol | 17:27 |
| * genii washes out all the coffee mugs and mops the floors while the place is temporarily empty | 17:27 | |
| IrcsomeBot | <tsimonq2> So nobody is around? No progress? :P | 17:29 |
| IrcsomeBot | <acheronuk> @tsimonq2, My chilli is nearly done. that is progress :) | 17:30 |
| IrcsomeBot | <tsimonq2> :P | 17:30 |
| * yofel puts on his invisibility cloak and gets back to work | 17:31 | |
| IrcsomeBot | <tsimonq2> XD | 17:31 |
| IrcsomeBot | <tsimonq2> It seems the Zesty floodgates have partially opened | 17:33 |
| IrcsomeBot | <tsimonq2> So progress there too | 17:33 |
| acheronuk | lots of email on the zesty changes list anyway | 17:52 |
| IrcsomeBot | <tsimonq2> Well of course. | 17:53 |
| soee_ | Mesa 13.0 Release Candidate 1 Arrives With Intel OpenGL 4.5 Complete | 19:28 |
| soee_ | \o, | 19:29 |
| tsimonq2 | !ninjas | 22:11 |
| ubottu | yofel, clivejo, acheronuk, tsimonq2, santa_: we need your attention! | 22:11 |
| tsimonq2 | Hey, were we going to decide on something? | 22:11 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!
