=== pepee- is now known as pepee
=== coreycb` is now known as coreycb
=== juliank is now known as Guest18923
=== juliank_ is now known as juliank
=== nelhage_ is now known as nelhage
ginggsnacc, Pharaoh_Atem: did you see https://packages.qa.debian.org/p/pcre3/news/20160227T165039Z.html ?06:47
=== Guest46749 is now known as Zic
Pharaoh_Atemginggs: hmm, maybe that'll fix the php segfaults10:53
Pharaoh_Atemginggs: that's one of the things Fedora patched to fix10:53
Pharaoh_Atembut can someone please tell me why pcre has a soversion of 3 in Debian/Ubuntu but nowhere else?10:54
ginggsPharaoh_Atem: and pcre2 is the new version10:55
Pharaoh_Atemin Fedora it makes sense, because pcre kept the soversion 110:55
Pharaoh_Atemso pcre2 is named correctly10:56
Pharaoh_Atemit's the same way in openSUSE, where they actually put the soversion in package names10:57
Pharaoh_Atemit's libpcre110:57
Pharaoh_Atemit's a really bizarre ABI change that seems to be exclusive to Debian/Ubuntu10:57
Pharaoh_Atemginggs: do you have any idea, as the pcre maintainer in Ubuntu?10:58
Pharaoh_Atemginggs: this is not a patch that makes me very happy... https://sources.debian.net/src/pcre3/2:8.38-2/debian/patches/soname.patch/11:00
ginggsi think i recall reading aomething about that11:00
ginggsupstream where bumping the SONAME unecessarily11:01
ginggsyou can look back through the changelog http://metadata.ftp-master.debian.org/changelogs/main/p/pcre3/unstable_changelog to see where pcre2 and pcre3 appeared11:02
Pharaoh_Atemoh geez11:03
Pharaoh_AtemI see how it happened11:03
Pharaoh_Atemthey patched and bumped the soversion when major versions were introduced11:04
Pharaoh_Atembut that's not irreversible now... unless they don't have a tool that rebuilds all the reverse depends, I guess?11:04
ginggsPharaoh_Atem: are you able to test if pcre3 2:8.38-2 fixes the php segfaults?11:12
Pharaoh_Atematm no, I have to rebuild everything :/11:13
Pharaoh_Atemwhich... takes hours11:13
=== Elimin8r is now known as Elimin8er
=== tlyu_ is now known as tlyu
=== yofel_ is now known as yofel
=== gusnan_ is now known as gusnan
=== ahasenac` is now known as ahasenack
=== Mirv__ is now known as Mirv
=== kees_ is now known as kees
=== Elimin8r is now known as Elimin8er
cjwatsonstefanct: groff> somewhat, depending on what you need17:10
=== Guest87218 is now known as kirkland
=== pepee- is now known as pepee
=== sarnold_ is now known as sarnold
stefanctcjwatson: sorted it out myself. i dont really understand why but adding \{ and \} to a branch containing a macro definition (.de) helped to avoid "warning: macro `.' not defined" at the end of that definition...22:32
stefanctand no, the line break within the .de is not the problem (alone)22:36
cjwatsonstefanct: that would make sense.  if you don't have the \{ there, then the .el only executes the next request, I'm not very surprised that that would have strange interactions with .de without \{ \}22:38
stefanctwell but executing the next request is exactly what it should do... just because that request has multiple lines i would not expect it to fail22:42
cjwatsonstefanct: I think technically the single line containing .de is the request, and then that request copies subsequent lines of input into a buffer22:55
cjwatsonstefanct: so if the .de isn't executed, then you have subsequent lines of input that will just be executed there and then22:56
cjwatsonstefanct: the .. (or whatever the macro closure is) is in fact a separate request after that telling troff to stop the macro definition22:57
cjwatsonstefanct: basically the parser is less smart than you were giving it credit for, but you have arrived at the correct answer :)22:57
stefanctyes, i think you are right22:58
stefanctin any case... lintian should now be happy so i am too :)22:59

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!