[06:48] <patstoms> is there any way to upgrade kernel up to 4.15 on ubuntu 16?
[06:49] <patstoms> just tried 4.18 which depends on libssl1.1 (>= 1.1.0), but ubuntu 16 have libssl1.0
[07:00] <tomreyn> !info linux-image-generic-hwe-16.04 xenial
[07:00] <tomreyn> !hwe | patstoms
[07:01] <tomreyn> i'm assuming you're referring to "ubuntu 16.04 LTS" ("ubuntu 16" is ambiguous)
[07:12] <patstoms> tomreyn, so i should not upgrade kernel?
[07:14] <tomreyn> patstoms: If you run ubuntu 16.04 LTS and want to stay with it for now, but want kernel 4.15, then you should install the HWE kernel package.
[07:23] <patstoms> !info linux-image-generic-hwe-16.04 bionic
[07:23] <patstoms> !info linux-image-generic-hwe-18.04 bionic
[07:23] <patstoms> ok, i will just upgrade then, thanks for info
[07:26] <tomreyn> so 4.15 works fine on 16.04 LTS if you just install the linux-image-generic-hwe-16.04 package, but sure, upgrading all of ubuntu is always an option.
[14:52] <ahasenack> hi, I have a package that builds on all arches, but has a runtime dependency on another package, from another source, that is amd64 only
[14:53] <ahasenack> should it be restricted to amd64 as well?
[14:53] <ahasenack> "depends"?
[14:57] <teward> ahasenack: if it has a dependency that only exists on amd64 your package should probably only be an amd64 package
[14:57] <teward> to avoid dependency hell
[14:57] <ahasenack> it came from debian like this, I'll suggest that to them
[14:57] <teward> Ubuntu Delta Necessary maybe?
[14:57] <teward> ahasenack: it SOUNDS like if it's depping on an amd64-only package it needs to be amd64 only
[14:57] <ahasenack> it builds in other arches, but the binaries are not installable on !amd64 (well, one in particular), because of this depends
[14:58] <ahasenack> it's a -dev binary package that has the depends on -dev from the amd64-only one
[14:58] <ahasenack> ok, it could be a delta
[14:58] <ahasenack> as I think without this, it won't pass migration
[14:58] <teward> yeah i think that'd be a problem :p
[14:59] <teward> ahasenack: IMO you may need to add it as a delta until Debian fixes it, but that'd be a q I'd run by the release team just in case.
[19:05] <tomreyn> is bug 1828878 known? is this not the right way to install mysql server on a fresh ubuntu installation?
[19:06] <tomreyn> (this is 18.04.2, typo)
[19:08] <tomreyn> ^ OP, thanks for joining, JuJUBee
[19:14] <tomreyn> JuJUBee: i'm trying to reproduce this now. while installing default-mysql-server, i notice it will install a lot more dependencies than it did for you: https://i.imgur.com/30BJvbH.png
[19:15] <JuJUBee> tomreyn, any chance that is because I tried mysql-server first?
[19:15] <tomreyn> if you're looking for a workaround, then i suggest you apt purge all these packages on my screenshot
[19:15] <tomreyn> yes, probably, but it should still not have been an issue.
[19:16] <JuJUBee> easier for me to resinstall 18.04
[19:16] <tomreyn> ok
[19:16] <JuJUBee> This is a VM anyway.
[19:16] <tomreyn> fwiw, it installed fine for me
[19:16] <tomreyn> also a VM, also 18.04.2 amd64
[19:17] <JuJUBee> ok, I will give it another go...
[19:18] <tomreyn> JuJUBee: if keeping this VM is an option, please do for at least a couple days, in case seomeone will respond to your bug report
[19:18] <JuJUBee> tomreyn, sure, I created a new one.
[19:18] <tomreyn> thanks
[19:20] <JuJUBee> no, thank you
[19:20] <tomreyn> :-)
[19:22] <tomreyn> JuJUBee: maybe you could later post your /var/log/apt/term.log* from the 'broken' VM as well, this could help reproducing the issue.
[19:56] <JuJUBee> tomreyn, ok, so installed 18.04 and upgraded.  Then default-mysql-client & server, but server never asked for a root password.
[20:10] <JuJUBee> tomreyn, ran mysql_secure_installation and all seems good now.
[20:10] <JuJUBee> tomreyn, thanks again, time for me to go home...
[23:59] <tomreyn> JuJUBee: glad you worked it out. :)