[11:57] <ahasenack> cpaelzer: I'm looking at the pcre3->pcre2 bug, apache2 specifically
[11:58] <ahasenack> cpaelzer: pcre2 has multiple libraries: 8bit, 16bit, 32bit, posix
[11:58] <ahasenack> cpaelzer: know anything about that/
[11:58] <ahasenack> ?
[14:18] <cpaelzer_> ahasenack: on experience on pcre
[16:45] <evit> Is Ubuntu vulnerable to https://www.cisecurity.org/advisory/multiple-vulnerabilities-in-php-could-allow-for-arbitrary-code-execution_2018-101/
[16:47] <RoyK> omg - another php bug
[16:47] <RoyK> evit: it's vulnerable, yes, but I don't know if the bug is fixed yet
[16:48] <evit> RoyK, You have something dripping off of you
[16:48] <evit> evit, sarcasm =P
[16:48] <evit> Ahh, I see
[16:48] <evit> RoyK, You are right PHP isn't my fav either
[16:50] <RoyK> evit: I asked on #debian if anyone knew there - a lot of ubuntu fixes comes to debian first
[16:53] <tomreyn> evit: find out their CVE IDs, then you can look them up on https://people.canonical.com/~ubuntu-security/cve/
[16:54] <RoyK> but where the fsck is the CVE?
[16:55] <evit> Where FSCK indeed
[16:55] <tomreyn> any responsible software developer would request one and list it on their bug tracker. e.g. https://bugs.php.net/bug.php?id=76778
[16:55] <tomreyn> "CVE-ID: 	None"
[16:56] <tomreyn> that is, if securit yimplication is assumed
[16:57] <tomreyn> https://bugs.php.net/bug.php?id=76582 got one.
[16:58] <tomreyn> i suspect the php folks dont consider memory leaks to have security impact.
[17:00] <sdeziel> Ubuntu syncs PHP from upstream
[17:03] <sdeziel> I'll open a bug for it
[17:08] <evit> sdeziel, Thanks =)
[17:18] <sdeziel> evit: LP: #1792987
[17:18] <adac> Hi there! How can I clear up the /var/cache/davfs2?
[17:19] <adac> It gets pretty huge and takes a lot of disk space
[17:23] <tomreyn> adac: this path doesn't seem to be managed by any (official) ubuntu package in any of the supported releases.
[17:25] <adac> tomreyn, actually I'm using autofs in combination with the davfs2 package
[17:26] <adac> and I'm on 16.04 LTS
[17:29] <tomreyn> adac: sorry, i dont know then. this software doesn't look like it's in a great state, though, judging by the bug tracker.
[17:29] <adac> tomreyn, ok I see. Yes I will probably simply replace that and mount the directry simply via fstab or so
[17:30] <adac> or mount it only when I do a backup
[17:30] <tomreyn> it seems to lack proper garbage collection, looses data when transfers are interrupted, transfers are slow.
[17:31] <sdeziel> evit: and the same for php5 LP: #1792991
[19:25] <DammitJim> how do I hold back dist-upgrades for a series of packages?
[19:26] <genii> !pinning
[19:26] <DammitJim> thanks genii
[19:26] <DammitJim> is it normal to have to do pinning?
[19:26] <genii> No
[19:26] <DammitJim> I'm having an issue where rabbitmq-server requires erlang
[19:26] <DammitJim> well, erlang's suggested upgrade through apt-get dist-upgrade is saying to go to version 21
[19:26] <DammitJim> well, the version of rabbitmq suggested is not compatible with erlang 21
[19:27] <DammitJim> and needs to stay with erlang 20
[19:27] <teward> DammitJim: do you have additional repositories enabled?
[19:27] <genii> Pinning is useful if for instance a normal particular package from regular repositories is doing something odd like pulling in a different dependency from an unexpected place like a PPA
[19:28] <teward> because erlang 20 is the only version in Ubuntu (and PPAs are... headaches)
[19:28] <DammitJim> oh yeah, thanks for pointing that out... I just noticed that there is a source for dl.bintray.com for erlang
[19:28] <DammitJim> oh man!
[19:29] <genii> If a dependency is stated like =(exactversion) it will usually use the specific one it really wants but some also have like >=(some minimum version)
[19:29] <DammitJim> genii, thank you for giving me the keyword... I just searched for pinning and that turned out a bunch of results on how to deal with this for rabbit and erlang users
[19:30] <DammitJim> but what a pain! I'm sure you guys are more used to this
[19:31] <JanC> PPAs are fine if they are maintained by people who know what they do  :)
[19:31] <JanC> like, not put random libraries in it that clash with existing libraries
[19:33] <DammitJim> ok, I think I'm about to break the internet
[19:33] <DammitJim> how about if I want to change the source where the packages come from
[19:36] <nacc> DammitJim: what do you mean?
[19:36] <nacc> DammitJim: you add repositories, and use pinning to change their priorities
[19:36] <DammitJim> it seems that rabbit is now suggesting to go from deb https://packages.erlang-solution.com/ubuntu xenial contrib to deb http://dl.bintray.com/rabbitmq/debian bionic erlang-20.x
[19:37] <DammitJim> this is so confusing! what a pain! why can't the developers just work with the version of rabbit and erlang that ubuntu provides from repos!!!
[19:37] <nacc> DammitJim: 'rabbit is no suggesting'?
[19:37] <nacc> *now...
[19:37] <DammitJim> yeah, the documentation has changed
[19:37] <nacc> DammitJim: 1) those are for two different releases
[19:37] <nacc> DammitJim: that's a question for the developers, not for us :)
[19:39] <DammitJim> I know nacc...  just complaining
[19:39] <DammitJim>  /join #complains
[20:52] <nacc> DammitJim: :)
[20:53] <linuxperia> Hi. I have php version "PHP 7.2.7-0ubuntu0.18.04.2" and phpinfo prints out this info here "Configuration File (php.ini) Path /etc/php/7.0/apache2 Loaded Configuration File /etc/php/7.0/apache2/php.ini" My Question is how i can change the settings in apache on my ubuntu server so it start uses the newest installed version 7.2 instead of this strange version here 7.0! I tryed this here but it did not work. "update-alternatives --set php
[20:53] <linuxperia> /usr/bin/php7.2" Thanks in advance for any helpfull tips to resolve this ubuntu apache problem.
[20:54] <nacc> linuxperia: what version of ubuntu are you on?
[20:54] <linuxperia> nacc: 18.04.2
[20:55] <nacc> linuxperia: given that doesn't exist yet, please clarify
[20:56] <linuxperia> well php has this version when i do php -v  "PHP 7.2.7-0ubuntu0.18.04.2"
[20:56] <linuxperia> so 18.04.02
[20:56] <jelly> linuxperia: try "lsb_release -r" instead
[20:57] <jelly> or lsb_release -a
[20:57] <nacc> linuxperia: that's a substring in a package version
[20:57] <nacc> linuxperia: not related, necessarily, to your ubuntu version
[20:59] <linuxperia> jelly: nacc: lsb_release -a No LSB modules are available. Distributor ID:	Ubuntu Description:	Ubuntu 18.04.1 LTS Release:	18.04 Codename:	bionic
[21:01] <linuxperia> i need apache to work with my newest installed php7.2 version instead of 7.0
[21:01] <nacc> linuxperia: `apt-cache policy libapache2-mod-php` in a pastebin
[21:01] <jelly> then figure out which php ABI apache uses, that php.ini path suggests mod_php
[21:02] <jelly> and then make sure versions of php-cli and mod_php match, because as you can see they can be completely separate
[21:03]  * jelly thought everyone switched to php-fpm 
[21:04] <linuxperia> nacc: http://paste.ubuntu.com/p/WFr73RwnmP/
[21:05] <nacc> linuxperia: ok, `apt-cache policy libapache2-mod-php7.0 libapache2-mod-php7.2` ?
[21:06] <linuxperia> nacc: http://paste.ubuntu.com/p/CBZWtXWwpS/
[21:07] <nacc> linuxperia: how did you upgrade from 16.04 to 18.04?
[21:08] <linuxperia> nacc: think it was dist-realease upgrade but it stoped after some time so i had to do then apt-get upgrade to finish it
[21:09] <nacc> linuxperia: ... right, that's what borked things then
[21:09] <nacc> (afaict)
[21:09] <nacc> linuxperia: is it possible that libapache2-mod-php7.0 is autoremovable? `sudo apt-get autoremove` ?
[21:09] <linuxperia> yes had some problems with the upgrade that is true
[21:09] <linuxperia> okey will try
[21:10] <linuxperia> yes i can autoremove it! should i ?
[21:10] <linuxperia> i guess is good will try it out thanks a lot for debugging the problem
[21:10] <linuxperia> lets see
[21:11] <nacc> linuxperia: yes, so your release upgrade didn't finish
[21:11] <nacc> linuxperia: you are still have packges from 16.04 intalled, such as that one
[21:11] <nacc> once you clean it up, i imagine things will fix themselves
[21:12] <linuxperia> yes the autoremove went without problems. this is the ouput: Module php7.0 disabled.
[21:12] <linuxperia> apache2_invoke prerm: Disable module php7.0
[21:12] <linuxperia>  apache still works. will test now phpinfo and see if apache works with the newest version.
[21:15] <linuxperia> nacc: Woowww Yuppiee you solved the Problem! Big Compliments to you Man! you helped me a lot after the upgrade strugle. Thank you very much! If you are from canonical then i will keep going my ubuntu server on the Google Cloud and support like the last years canonical the same way.
[21:18] <linuxperia> I am saved. All problems with the ubuntu server disapeared. Thanks a lot i feel very happy now :-)
[21:24] <nacc> linuxperia: glad to hear
[22:12] <linuxperia> nacc: i just remembered why the upgrade of my ubuntu server 16.04 got dirsupted. For some weired and bad reason the main database package mariadb 10.2 is not available for 18.04. Neither for Debain nor for ubuntu exist the stable release mariadb 10.2 for 18.04 however for 16.04 it existed and i did used it. Becouse tthe ubuntu database package is dis-functional my upgrade of the server crashed. Everyone that has ubuntu server running with
[22:12] <linuxperia> mysql/mariadb database 10.2 will endup with a crashed ubuntu server system. see here more info of mariadb package build failure. I could without any problem compile and install amriadb 10.2 from sources on ubuntu. Not sure why ubuntu and debian have such big problems getting mysql databse 10.2 packaged. https://launchpad.net/~mysql-ubuntu/+archive/ubuntu/mariadb-10.2/+packages
[22:18] <linuxperia> nacc: this is something the canonical people need look into it if they dont want lose customers because the most vital part of the ubuntu server aka the stable release of the database is broken and crashes any system when upgraded from 16.04 to 18.04 not only on ubuntu but also on debian. i already thinked to switch over to RedHat in the hope to avoid such a stupidity again. when i do build mariadb 10.2 from github on ubuntu however it gets
[22:18] <linuxperia> compiled and installed without any problems. so it is a packaging problem and not a source problem.
[22:45] <nacc> linuxperia: reading
[22:45] <nacc> linuxperia: mariadb-server 10.2 was never in ubuntu
[22:46] <nacc> linuxperia: afaict, 16.04, 18.04 all have 10.1
[22:46] <nacc> linuxperia: so, presumably, you were running some non-ubuntu mariadb on 16.04.
[22:46] <nacc> !info mariadb-server xenial
[22:46] <nacc> !info mariadb-server bionic
[22:47] <nacc> linuxperia: I don't work for Canonical.
[22:47] <nacc> linuxperia: and presumably you're not paying Canonical either, so I'm not sure why you think they are losing you as a customer?
[22:47] <nacc> linuxperia: if you are you should pursue your official support contract, if you want
[22:48] <nacc> linuxperia: you also chose to use a PPA (not a great thing) for something entitled "MariaDB 10.2 Testing" which implies it is not stable.
[22:48] <nacc> A PPA that hadn't received *any* updates in ... 2 years?
[22:50] <nacc> linuxperia: final point, mariadb-server in Ubuntu is in universe, which means it is community supported.
[23:01] <linuxperia> nacc: i use ubuntu server on the google cloud and by this pay canonical for the providing of the certified ubuntu server images => https://blog.ubuntu.com/2014/11/03/certified-ubuntu-images-available-on-google-cloud-platform i did not use any testing ppa i used the mariadb official ppa to get 10.2 running on ubuntu. Okey thanks a lot for the Information. I find it very strange that we have already the stable release of mariadb 10.3 but
[23:01] <linuxperia> debian and ubuntu are on 10.2 max. this is a little lame for ubuntu/debian as database is a vital part of a server. Okey thanks for the clarifications and help again. wish you a great time. Best regards.
[23:19] <RoyK> linuxperia: mariadb is available in all the recent versions from https://downloads.mariadb.org/ - distros like debian and ubuntu lag behind, which is normal, because they want to know that things work before they push a new version
[23:19] <RoyK> linuxperia: just grab the packages from https://downloads.mariadb.org/ and stop complaining
[23:21] <nacc> !latest | linuxperia
[23:21] <RoyK> see "!sns" in #debian as well ;)
[23:21] <nacc> linuxperia: also ... "mariadb official ppa"?
[23:22] <nacc> linuxperia: if by that you mean what RoyK is referring to, then that's your own issue to figure out. Not an Ubuntu problem.
[23:23]  * RoyK thinks linuxperia should run debian sid to experience the true joy of living on the bleeding edge for a while
[23:23] <nacc> heh
[23:30] <nacc> linuxperia: i think you really need to step back and think about what you are running, and what is reasonable expectations. Have a nice day.