19:02:08 <wilcal> #startmeeting
19:02:08 <Inigo_Montoya> Meeting started Thu Oct 24 19:02:08 2019 UTC.  The chair is wilcal. Information about MeetBot at http://wiki.debian.org/MeetBot.
19:02:08 <Inigo_Montoya> Useful Commands: #action #agreed #help #info #idea #link #topic.
19:02:13 <wilcal> hello all
19:02:29 <wilcal> #topic Who's new?
19:02:35 <wilcal> anyone new here today
19:03:18 <wilcal> nothing moving on to the really only issue today
19:03:32 <wilcal> #topic Updating from M6 -> M7
19:03:46 <wilcal> Lots of discussion on the boards over this
19:04:09 <wilcal> For the record here
19:04:13 <wilcal> https://wiki.mageia.org/en/Mageia_7_Errata#Upgrade_issues
19:04:14 <wilcal> https://wiki.mageia.org/en/Mageia_7_Release_Notes#Upgrading_from_Mageia_6
19:04:16 <wilcal> https://bugs.mageia.org/show_bug.cgi?id=25476
19:04:18 <[mbot> [ 25476 – Upgrading from Mageia 6: adding media before selecting packages fails, conflict about /usr/lib64/rpm-plugins/syslog.so ]
19:04:38 <wilcal> that kinda sums it up with no real solution
19:05:05 <wilcal> QA has gone on the record that there is no real clear upgrade path
19:07:17 <wilcal> Anyone have any comments on the M6 -> M7 upgrade issues
19:07:35 <hviaene> In my case the really annoying is that the system boots after the seg fault
19:07:55 <hviaene> But no X works.
19:08:21 <wilcal> Lots of different results. Some successful some not at all
19:08:48 <wilcal> No X or boots to a blank screen and hangs are also common problems
19:09:12 <hviaene> I' ll try a DVD-upgrade, I want to get to a workable situation.
19:09:49 <wilcal> netinstall I see is successful
19:09:54 <DavidWHodgins> Sorry I'm late
19:09:57 <wilcal> Hello David
19:10:01 <wilcal> Great to see you here
19:10:07 <wilcal> No problem
19:10:13 <MageiaTJ> Hi, Dave!
19:10:30 <wilcal> we are discussing the only issure really and that is the M6 -> M7 upgrade
19:10:44 <DavidWHodgins> Forgot to ensure updated urpmi etc had actually been moved on local mirror before starting upgrades yesterday.
19:10:54 <wilcal> https://wiki.mageia.org/en/Mageia_7_Errata#Upgrade_issues
19:10:56 <wilcal> https://wiki.mageia.org/en/Mageia_7_Release_Notes#Upgrading_from_Mageia_6
19:10:57 <wilcal> https://bugs.mageia.org/show_bug.cgi?id=25476
19:10:59 <[mbot> [ 25476 – Upgrading from Mageia 6: adding media before selecting packages fails, conflict about /usr/lib64/rpm-plugins/syslog.so ]
19:11:22 <wilcal> Lots of discussion on the Boards over this
19:11:36 <DavidWHodgins> mgaapplet upgrade segfaulted on this computer. Was able to finish upgrade using urpmi only after enabling testing repo. That should be ok today.
19:11:39 <hviaene> Do you mean it's worth nother try now?
19:11:39 <wilcal> is it worth to continue to find a solution
19:12:18 <DavidWHodgins> The solution is already done, I just forgot to wait for the mirror to sync before starting the upgrade
19:12:22 <hviaene> another
19:12:46 <wilcal> Honoring David's presense here
19:12:48 <wilcal> #chair DavidWHodgins
19:12:48 <Inigo_Montoya> Current chairs: DavidWHodgins wilcal
19:13:10 <DavidWHodgins> On my main system, I had already giving up and started it's recovery procedure before I figured out what the problem was.
19:13:59 <MageiaTJ> Dave, that makes it sound like we are close to a breakthough.
19:14:00 <DavidWHodgins> On that system, after recovery, the recovered system wouldn't boot due to the bug when the kernel is too far into a large partition. Will fix that later today, and then try it again.
19:14:24 <DavidWHodgins> That system is on a much faster machine, but with every possible destop installed still takes a long time to upgrade
19:15:03 <DavidWHodgins> rpm -qa|wc -l shows 5416 packages on that system
19:16:00 <DavidWHodgins> I'd like to wait until I finish upgrading that system before recommending whether or not to turn on upgrades using mgaapplet for regular users
19:16:33 <DavidWHodgins> Opinions on opening up upgrades using mgaapplet?
19:17:26 <hviaene> I' ll personally will never do such thing
19:17:55 <MageiaTJ> Fine with me - if we can get them to work most of the time. I wouldn't do it, but others prefer it.
19:18:02 <wilcal> As I have stated in the past, and still today, my favorite first step in an upgrade is to use killdisk.com first
19:18:12 <DavidWHodgins> My main system, the one with over 5000 packages, started as a Mageia 3 install, and has been upgraded using mgapplet each release since then.
19:18:46 <wilcal> Does your main system use an nvidia video board?
19:19:02 <DavidWHodgins> No, ati radeon
19:19:33 <DavidWHodgins> a Radeon hd 5450 video card
19:20:19 <wilcal> I have only one nvidia based system here and when I replace that all will only be Intel graphics. No more nvidia
19:21:11 <wilcal> I am not a gamer
19:22:02 <DavidWHodgins> Just checked. Mageia 7 rpm update is still in updates testing. Guess it needs to be assigned to qa first, and then validated/pushed before trying another upgrade attempt
19:22:18 <MageiaTJ> I'm thinking of replacing my old geforce 210 with an ati/amd card. The nvidia340 driver's days are numbered.
19:23:25 <DavidWHodgins> Probably a good idea. While linux in general is great at continuing to support old hardware, the video drivers that are distributed as nonfree do not get updated for new kernels.
19:23:59 <hviaene> My desktop is on vidia340 , it served me weel, i'dd hate to let it go
19:24:22 <DavidWHodgins> :-)
19:24:25 <wilcal> So for now it looks this drags on until at least next weeks QA meeting and maybe longer
19:25:06 <wilcal> Lets move on
19:25:07 <wilcal> #topic Testing Updates & Backports
19:25:08 <DavidWHodgins> Hopefully not that long. As before, I upgraded this system ok after enabling updates testing to pick up the new rpm packages
19:25:59 <wilcal> So a pretty big update came through today.
19:26:21 <wilcal> The Vbox update went though so now I can work on the kernel
19:26:38 <hviaene> YEEESSSSS, some stuff that was hanging in
19:26:56 <MageiaTJ> There are some x11 video drivers on the list, too.
19:27:10 <wilcal> I find it very hard to work on updates_testing when there is a kernel, Vbox and testing on an nvidia platform
19:27:51 <wilcal> I started testing Vbox last Friday and blew up my test system by selecting just one wrong rpm
19:27:55 <wilcal> unrecoverable
19:28:01 <DavidWHodgins> Install all of those updates and test them together
19:28:52 <DavidWHodgins> When testing updates in vb, I always enable a snapshot before installing the update. revert and delete the snapshot, then install the update again after it's pushed
19:29:07 <MageiaTJ> I'm finding the qarepo tool to be invaluable for testing updates. I use it on almost all of them.
19:29:28 <DavidWHodgins> Or was it the vb update itself that failed?
19:29:30 <hviaene> I gave up on it
19:29:38 <DavidWHodgins> on the host, that is.
19:29:40 <hviaene> qarepo
19:30:04 <wilcal> the vbox upgrade video driver on nvidia is what usually bricks my test system
19:30:05 <DavidWHodgins> I use qarepo too.
19:30:41 <hviaene> I find it too time consuming
19:30:43 <wilcal> there are three x11 driver tests in updates testing. I assume those are hardware specific
19:30:51 <DavidWHodgins> Yes
19:31:17 <wilcal> A vbox update test takes me the better part of a day if the system does not blow up
19:31:42 <wilcal> If it blows up I push away from the computer rebuild it and try again the next day
19:31:56 <wilcal> never on the same day
19:32:21 <wilcal> again it's the Vbox/nvidia clashes that are the problem
19:32:32 <MageiaTJ> hviane: Qarepo is less time-consuming for me now that I have a MUCH faster ISP.
19:33:31 <wilcal> so 25604/5/6 are all hardware specific?
19:33:59 <DavidWHodgins> Yes. They each handle various video cards
19:34:28 <DavidWHodgins> If you don't have a card that uses that driver, all you can do is test that the update installs cleanly
19:34:39 <wilcal> So I guess you have to look to see if it is installed on your system to see if you can test the driver
19:35:09 <wilcal> Anything else in testing upgrades and updates?
19:35:12 <hviaene> Is there yet a solution for laptops with 2  graphic sets?
19:35:38 <DavidWHodgins> My video card uses the radeon driver, not the ati driver
19:35:39 <wilcal> Sounds like something for M8
19:35:58 <hviaene> Too bad
19:36:13 <DavidWHodgins> hviaene: My understanding is that it is supposed to work now, but that's something I cannot test.
19:36:39 <hviaene> I can, and nada, zero nothing
19:37:37 <wilcal> My laptop is supposed to support it's own display and an external RGB display at the same time but that's never worked
19:37:52 <wilcal> It's also kinda get'n old
19:37:58 <DavidWHodgins> Normally for kernel updates, we just ensure all related packages are installed together, test for at least a day, and then validate. In the case of critical security updates, we just test that boot to a working desktop works
19:39:06 <wilcal> I'll work that kernel update in the next days. Should be through it by the end of the weekend. Takes me also as long as Vbox testing as I make sure all of that works after the kernel update
19:39:36 <DavidWHodgins> I have a fairly new star labs laptop, and have tested it using hdmi connection to a 48" tv. works great for watching netflix. :-)
19:39:43 <wilcal> And you have to make sure Vbox clients work too
19:40:25 <wilcal> So bth the laptop and TV work at the same time maybe even with different resolutions?
19:40:35 <DavidWHodgins> Yes
19:40:40 <wilcal> Kool
19:40:55 <hviaene> I haven' t got time to watch  netflix if ever I should waant!!!
19:40:56 <DavidWHodgins> DIdn't have to configure anything. It just worked on first try.
19:41:17 <wilcal> 1920x1080 for both displays?
19:41:34 <DavidWHodgins> Actually, yes. They are the same resolution.
19:42:08 <wilcal> Ok anything else up updates testing
19:42:21 <hviaene> Not here
19:42:25 <wilcal> Lets move on to
19:42:28 <wilcal> #topic Anything else?
19:42:32 <wilcal> Anything else
19:42:49 <DavidWHodgins> Not here
19:42:50 <wilcal> Not from me
19:42:58 <wilcal> Thanks all for being here
19:43:00 <hviaene> Not here either
19:43:06 <wilcal> Oh time change
19:43:39 <wilcal> Nov 3 in the USA
19:43:47 <hviaene> G'night all, yess one hour longer sleep!!
19:43:56 <wilcal> so we have another meeting here at the same time
19:44:04 <wilcal> we'll bring it up next week
19:44:10 <DavidWHodgins> I'll dig up my msg to the qa list from last year. Think I finally got it right that time.
19:44:17 <wilcal> Countdown time
19:44:22 <wilcal> T-5
19:44:25 <wilcal> T-4
19:44:30 <DavidWHodgins> Thanks everyone
19:44:38 <wilcal> T-3
19:44:45 <wilcal> T-2
19:44:49 <wilcal> T-1
19:44:52 <wilcal> #endmeeting