#mer log for Monday, 2017-06-26

*** Nokius_ <Nokius_!~Nokius@p5DDB5A8D.dip0.t-ipconnect.de> has joined #mer00:05
*** Nokius <Nokius!~Nokius@p5DDB6574.dip0.t-ipconnect.de> has quit IRC (Ping timeout: 240 seconds)00:08
*** KaIRC <KaIRC!~robert@193-80-168-158.adsl.highway.telekom.at> has quit IRC (Remote host closed the connection)00:18
*** frinring <frinring!~frinring@x55b4a027.dyn.telefonica.de> has quit IRC (Ping timeout: 240 seconds)00:28
*** Administrator <Administrator!~quassel@124.202.185.26> has joined #mer01:38
*** Administrator is now known as Guest5552401:38
*** Guest55524 is now known as zhxt01:42
*** Son_Goku <Son_Goku!~King_InuY@fedora/ngompa> has quit IRC (Quit: My MacBook has gone to sleep. ZZZzzz…)05:23
*** mkosola1 <mkosola1!~mkosola@37-219-218-191.nat.bb.dnainternet.fi> has quit IRC (Quit: Leaving.)05:51
*** SfietKonstantin <SfietKonstantin!~sk@88.190.246.243> has joined #mer05:57
*** Nokius_ is now known as Nokius06:08
*** phlixi <phlixi!~phlixi@ppp-46-244-140-185.dynamic.mnet-online.de> has quit IRC ()06:14
*** phlixi <phlixi!~phlixi@ppp-46-244-140-185.dynamic.mnet-online.de> has joined #mer06:52
*** diego_r <diego_r!~diego@host57-224-static.7-79-b.business.telecomitalia.it> has joined #mer07:06
*** nerdboy <nerdboy!~sarnold@gentoo/developer/nerdboy> has quit IRC (Ping timeout: 240 seconds)07:07
*** SfietKonstantin <SfietKonstantin!~sk@88.190.246.243> has quit IRC (Ping timeout: 276 seconds)07:10
*** IZh <IZh!~IZh@sgr-a.ru> has quit IRC (Quit: leaving)07:13
*** IZh <IZh!~IZh@sgr-a.ru> has joined #mer07:16
*** Son_Goku <Son_Goku!~King_InuY@fedora/ngompa> has joined #mer07:17
*** aard_ <aard_!~bwachter@edna-edison.lart.info> has quit IRC (Quit: iamer)07:35
*** Aard <Aard!~bwachter@edna-edison.lart.info> has joined #mer07:35
*** xruxa <xruxa!~xruxa@cable-83.217.152.30.coditel.net> has joined #mer07:56
*** nerdboy <nerdboy!~sarnold@gatekeeper.gentoogeek.org> has joined #mer08:00
*** nerdboy <nerdboy!~sarnold@gatekeeper.gentoogeek.org> has quit IRC (Changing host)08:00
*** nerdboy <nerdboy!~sarnold@gentoo/developer/nerdboy> has joined #mer08:00
*** xruxa <xruxa!~xruxa@cable-83.217.152.30.coditel.net> has quit IRC (Ping timeout: 246 seconds)08:00
*** xruxa <xruxa!~xruxa@cable-83.217.152.30.coditel.net> has joined #mer08:00
*** xruxa <xruxa!~xruxa@cable-83.217.152.30.coditel.net> has quit IRC (Ping timeout: 240 seconds)08:05
*** xruxa <xruxa!~xruxa@cable-83.217.152.30.coditel.net> has joined #mer08:05
*** jpetrell <jpetrell!~jpetrell@2001:998:2a:dead:6022:ce32:c77d:8c16> has joined #mer08:06
*** xruxa <xruxa!~xruxa@cable-83.217.152.30.coditel.net> has quit IRC (Ping timeout: 240 seconds)08:09
*** xruxa <xruxa!~xruxa@cable-83.217.152.30.coditel.net> has joined #mer08:09
*** morphis <morphis!~morphis@pD9ED6566.dip0.t-ipconnect.de> has joined #mer08:12
*** cxl000 <cxl000!~cxl000@c27-253-11-51.brodm4.vic.optusnet.com.au> has joined #mer08:18
*** xruxa <xruxa!~xruxa@cable-83.217.152.30.coditel.net> has quit IRC (Read error: Connection timed out)08:25
pvuoreladcaliste: lbt, abranson_, on pydbus, i'm okayish for adding things to mer if there's enough demand, but then again the version is 0.6.0 without mention of api stability. looking at code it's tens of kilobytes of pure python so should be easy to include copies within applications too?08:39
*** notmart <notmart!~diau@kde/mart> has joined #mer08:40
*** KaIRC <KaIRC!~robert@193-80-168-158.adsl.highway.telekom.at> has joined #mer08:41
dcalistepvuorela: yes, I know the thing is labelled 0.6.0… Never trusted the numbering though, Inkscape is still below 1.0 but I use it regularly for instance. Anyway, I understand your point of high demand, and I don't know if indeed there's a high demand for DBus Python bindings.08:53
dcalisteThe code is pure Python and easy to include in the application, I agree also.08:54
*** Son_Goku <Son_Goku!~King_InuY@fedora/ngompa> has quit IRC (Read error: Connection reset by peer)08:54
dcaliste(Maybe except for the dependencies, I'm not sure they are allowed in Harbour and they are definitely more complex to include)08:55
*** Sir_Gallantmon <Sir_Gallantmon!King_InuYa@fedora/ngompa> has joined #mer08:56
dcalisteBesides, pydbus seems to be the *current* official way to have DBus calls from Python, according to the Freedesktop page you rightly pointed: https://www.freedesktop.org/wiki/Software/DBusBindings/08:57
LarstiQdcaliste: have you come across upstream writing about the deprecation?08:59
*** frinring <frinring!~frinring@x55b60079.dyn.telefonica.de> has joined #mer09:00
dcalisteI'm checking not to say anything stupid, but I think Gnome stack advocate to use pydbus instead of older python-dbus, because it is based on the new gdbus included in GLib itself.09:01
LarstiQseeing MartinK maintains pydbus in Fedora, that's enough for me to include it into Mer09:01
LarstiQprovided the dependencies work out09:02
dcalisteYes, the spec file originate from MartinK. I just adapted it to Mer requirements.09:02
* LarstiQ now got to reading those comments :)09:02
pvuoreladcaliste: comparison to inkspace isn't necessarily good since it's not a library providing an api.09:03
LarstiQpvuorela: I don't think that's a problem09:03
pvuorelaLarstiQ: what?09:04
dcalistepvuorela: yes, I agree. You're right. Besides, the library python-dbus (the actual) is based on, namely dbus-glib, is clearly obsolete and replaced by gdbus.09:04
LarstiQa sub 1.0 version number on pydbus09:04
pvuorelabut but, pydbus requires pygi and we could make that allowed in harbour.09:04
dcalistepvuorela: yes, the depency chain, that need to be allowed in harbour can be an issue and should be discussed.09:05
LarstiQ0.5 is from 2016-0409:05
pvuorelaLarstiQ: no mention of how stable the api can be considered.09:06
LarstiQpvuorela: you're right that it isn't as stable as the dead python-dbus09:06
pvuorelabut still, it's a small pure python lib we've managed without for years now so i'd propose going by allowing now only pygi and suggesting applications of including a copy of their own for pydbus.09:08
dcalistelarstiq: since Gnome3, they are asking to migrate from dbus-glib to gdbus, see https://wiki.gnome.org/DevGnomeOrg/Gnome3PortingGuide09:10
dcalistepvuorela: allowing pygi and explaining in a wiki how to include pydbus is necessary should be fine. I can help with the wiki if you agree.09:11
dcalistes/is necessary// sorry09:11
pvuoreladcaliste: sounds good. think it would be good to have more examples including external modules that are not directly provided by the os or allowed in harbour.09:14
dcalistepvuorela, LarstiQ: I understand the issue of maintainance for Mer, less packages, better support. When community members are not here anymore to maintain what they push inside, the burden of Mer maintainance increase. For DBus Python bindings, let's go as you suggested for the moment, 1. allow pygi in harbour, 2. write a wiki on howto include pydbus in apps. I will take the point 2., and answer the TJC question with a wiki post, feel free later on to c09:27
dcalisteopy this to sailfishos.org if adapted.09:27
tbrwell, it seems to be too much work in general for jolla to maintain mer, so I'm not exactly sure why they insist on asserting ownership of mer10:32
pvuorela?10:35
tbrfrom my impression it's not very well maintained and simple requests for trivial stability updates of packages stall until they are obsolete10:37
tbr(I actually submitted a *tested* PR so all it would have taken would be to review and approve merge)10:37
LarstiQtbr: where?10:38
pvuorelaif this is related to above conversation, it was also about what is allowed in harbour.10:38
tbrit was tangential10:38
tbrwe're on Mer, so harbour is a bit off topic here anyway10:38
pvuorelabut true that some PRs have been pending too long. been trying to get the list shorter lately.10:38
pvuorelanot the best channel, yea.10:39
*** spiiroin__ is now known as spiiroin10:42
tbrwhere I'm coming from is: I'd be happy to submit the occasional PR to improve stability/security, but if stuff gets ignored and once it's outdated, 2 months later, it gets closed as libcurl had security releases, well...10:42
tbrIf you say "we own this", then you should also own up and maintain it10:42
LarstiQtbr: from my point, I have too many places to watch, so it works best if alerted directly10:42
LarstiQ(not that it sounds like I was directly involved here)10:43
tbroh, and it looks like nobody bothered to actually update the vulnerable curl... >.>10:44
pvuorelawhat i checked current curl doesn't have vulnerabilities.10:45
pvuorelathere was a PR that introduced vulnerabilities so it was closed.10:45
tbrCVE-2017-950210:46
tbrmy PR didn't introduce vulnerabilities when I filed it. it updated to a newer version. You are bordering on insulting.10:46
pvuorelahttps://curl.haxx.se/docs/adv_20170614.html - "Not affected versions: libcurl < 7.53.0 and >= 7.54.1"10:47
tbryeah, also it's just cygwin and dos...10:48
tbrmy point stands though and to be honest after this conversation I feel even more unwelcome to contribute10:49
pvuorelano intention on insulting or anything. just from technical point of view if a release seems to introduce problems when current one doesn't have them, it's not necessarily a good update to make. new PRs of course welcome and i'll try to watch those more carefully.10:52
LarstiQthis one? https://git.merproject.org/mer-core/curl/merge_requests/1511:03
LarstiQpvuorela: the PR was filed 4 months ago, at that point there were no security issues11:04
LarstiQ(judging from what tbr said)11:04
pvuorelayes.11:04
LarstiQso the problem is not "oh this introduces issues, let's not merge it"11:04
LarstiQthe problem is "the PR lingered for 3 months and by then it was obsolete"11:05
LarstiQwhich comes back to filing PRs by itself doesn't show up on radar11:07
* LarstiQ doesn't know what is needed to be notified about PRs11:08
LarstiQOwner/Master/Developer status?11:08
LarstiQnotification settings for each project?11:09
LarstiQditching gitlab?11:10
tbrhttps://git.merproject.org/help/workflow/notifications should answer that11:10
tbrgitlab seems to be a decent system. I'm admin of an instance at work.11:11
LarstiQso by default, no one11:11
tbrI'd suggest to configure your maintainer scripts to set up notifications too11:12
LarstiQtbr: don't suppose you have a handy 'new PR -> irc notification' script11:12
LarstiQtbr: yeah, that makes sense11:12
tbrno. I have a setup involving mattermost as the chat system (with IRC bridge), but that involves per project setup11:13
tbrI guess it should be possible to configure projects to emit that and have merbot pick it up11:13
tbrIIRC it listens to a TCP or UDP port internally11:13
LarstiQyeah11:13
tbrif desired I can look into that as it would be good for me to know too11:14
LarstiQtbr: if you figure that out I can apply it11:14
tbrluckily gitlab is very extensible11:14
*** Sir_Gallantmon <Sir_Gallantmon!King_InuYa@fedora/ngompa> has quit IRC (Quit: My MacBook has gone to sleep. ZZZzzz…)11:14
tbr*nod*11:14
LarstiQI'm reasonably sure our volume of PRs is not too high, and then having notifications here would, for me, be the best solution11:16
tbryou could also create an account on gitlab that subscribes to all PRs and or issues and point that to e.g. a mailing list or an alias with a couple of people11:17
* LarstiQ hates email11:18
tbrhehe11:18
tbrone thing that I'm sort of missing is a global search/feed for the whole gitlab instance. It might be already possible, but it's not intuitive in that way11:19
tbrhttps://git.merproject.org/dashboard/merge_requests?scope=all&state=opened&utf8=%E2%9C%9311:20
LarstiQchange frequency ~ couple a day11:22
*** zhxt is now known as zhxt_afk11:36
*** simosx <simosx!~simosx@ubuntu/member/simosx> has joined #mer11:58
*** xruxa <xruxa!~xruxa@cable-83.217.152.30.coditel.net> has joined #mer12:00
*** pashik <pashik!~Pavel@host-207-138.dialup.telecet.ru> has quit IRC (Quit: WeeChat 1.4)12:15
*** pashik <pashik!~Pavel@host-207-138.dialup.telecet.ru> has joined #mer12:15
*** xruxa <xruxa!~xruxa@cable-83.217.152.30.coditel.net> has quit IRC (Read error: Connection timed out)12:16
*** xruxa <xruxa!~xruxa@cable-83.217.152.30.coditel.net> has joined #mer12:16
*** guhl <guhl!~guhl@gateway/tor-sasl/guhl> has joined #mer12:18
*** xruxa <xruxa!~xruxa@cable-83.217.152.30.coditel.net> has quit IRC (Ping timeout: 246 seconds)12:20
*** xruxa <xruxa!~xruxa@cable-83.217.152.30.coditel.net> has joined #mer12:21
*** Son_Goku <Son_Goku!~King_InuY@fedora/ngompa> has joined #mer12:25
*** xruxa <xruxa!~xruxa@cable-83.217.152.30.coditel.net> has quit IRC (Ping timeout: 246 seconds)12:25
*** xruxa <xruxa!~xruxa@cable-83.217.152.30.coditel.net> has joined #mer12:26
*** tbr <tbr!dm8tbr@mail.bfst.de> has quit IRC (Ping timeout: 258 seconds)12:28
*** xruxa <xruxa!~xruxa@cable-83.217.152.30.coditel.net> has quit IRC (Ping timeout: 240 seconds)12:30
*** xruxa <xruxa!~xruxa@cable-83.217.152.30.coditel.net> has joined #mer12:30
*** tbr <tbr!dm8tbr@mail.bfst.de> has joined #mer12:34
*** Son_Goku <Son_Goku!~King_InuY@fedora/ngompa> has quit IRC (Read error: No route to host)12:37
*** Sir_Gallantmon <Sir_Gallantmon!King_InuYa@fedora/ngompa> has joined #mer12:42
*** xruxa <xruxa!~xruxa@cable-83.217.152.30.coditel.net> has quit IRC (Quit: Leaving)12:42
*** zhxt_ <zhxt_!~zhxt@36.102.227.70> has joined #mer13:06
*** simosx <simosx!~simosx@ubuntu/member/simosx> has quit IRC (Quit: Yakkety Bye!)14:11
*** jpetrell <jpetrell!~jpetrell@2001:998:2a:dead:6022:ce32:c77d:8c16> has quit IRC (Ping timeout: 240 seconds)14:18
*** Sir_Gallantmon is now known as Son_Goku14:31
*** jpetrell <jpetrell!~jpetrell@2001:998:2a:dead:6022:ce32:c77d:8c16> has joined #mer14:37
*** jpetrell <jpetrell!~jpetrell@2001:998:2a:dead:6022:ce32:c77d:8c16> has quit IRC (Ping timeout: 276 seconds)14:52
*** pashik <pashik!~Pavel@host-207-138.dialup.telecet.ru> has quit IRC (Quit: WeeChat 1.4)15:13
*** zhxt_ <zhxt_!~zhxt@36.102.227.70> has quit IRC (Ping timeout: 255 seconds)15:20
*** pashik <pashik!~Pavel@host-207-138.dialup.telecet.ru> has joined #mer15:30
*** Son_Goku <Son_Goku!King_InuYa@fedora/ngompa> has quit IRC (Read error: Connection reset by peer)15:52
*** KaiRo_Mozilla <KaiRo_Mozilla!~robert@193-83-193-116.adsl.highway.telekom.at> has joined #mer15:52
*** Son_Goku <Son_Goku!~King_InuY@fedora/ngompa> has joined #mer15:53
*** KaIRC <KaIRC!~robert@193-80-168-158.adsl.highway.telekom.at> has quit IRC (Ping timeout: 240 seconds)15:55
*** Son_Goku <Son_Goku!~King_InuY@fedora/ngompa> has quit IRC (Read error: Connection reset by peer)16:21
*** leinir <leinir!~leinir@amarok/usability/leinir> has quit IRC (Quit: Konversation terminated!)16:23
*** leinir_ <leinir_!~leinir@amarok/usability/leinir> has joined #mer16:23
*** Sir_Gallantmon <Sir_Gallantmon!~King_InuY@fedora/ngompa> has joined #mer16:28
*** Sir_Gallantmon <Sir_Gallantmon!~King_InuY@fedora/ngompa> has quit IRC (Quit: My MacBook has gone to sleep. ZZZzzz…)16:47
*** notmart <notmart!~diau@kde/mart> has quit IRC (Quit: notmart terminated!)17:18
*** leviathan_ <leviathan_!~quassel@pcd317061.netvigator.com> has joined #mer17:20
*** gmoro_ <gmoro_!~gmoro@31.169.96.75> has quit IRC (Ping timeout: 255 seconds)18:26
*** merlin1991 <merlin1991!~merlin@Maemo/community/cssu/merlin1991> has quit IRC (Read error: Connection reset by peer)18:44
*** kelvan <kelvan!~quassel@mail.merlin1991.at> has quit IRC (Remote host closed the connection)18:44
*** merlin1991 <merlin1991!~merlin@Maemo/community/cssu/merlin1991> has joined #mer18:45
*** kelvan <kelvan!~quassel@mail.merlin1991.at> has joined #mer18:45
*** SfietKonstantin <SfietKonstantin!~sk@88.190.246.243> has joined #mer19:45
*** tigeli <tigeli!pasjohol@siirappi.com> has quit IRC (Ping timeout: 246 seconds)20:22
*** tigeli <tigeli!pasjohol@siirappi.com> has joined #mer20:30
*** SfietKonstantin <SfietKonstantin!~sk@88.190.246.243> has quit IRC (Ping timeout: 240 seconds)20:33
*** gmoro <gmoro!~gmoro@31.169.96.75> has joined #mer20:37
*** leviathan_ <leviathan_!~quassel@pcd317061.netvigator.com> has quit IRC (Remote host closed the connection)20:54
*** SfietKonstantin <SfietKonstantin!~sk@88.190.246.243> has joined #mer20:58
*** SfietKonstantin <SfietKonstantin!~sk@88.190.246.243> has quit IRC (Ping timeout: 246 seconds)21:03
*** phlixi <phlixi!~phlixi@ppp-46-244-140-185.dynamic.mnet-online.de> has quit IRC ()21:57
*** phlixi <phlixi!~phlixi@ppp-46-244-140-185.dynamic.mnet-online.de> has joined #mer21:57
*** Son_Goku <Son_Goku!~King_InuY@fedora/ngompa> has joined #mer22:00
*** morphis <morphis!~morphis@pD9ED6566.dip0.t-ipconnect.de> has quit IRC (Ping timeout: 240 seconds)22:26
*** alextai <alextai!~alextai@5.102.218.139> has quit IRC (Ping timeout: 240 seconds)22:49
*** alextai <alextai!~alextai@5.102.218.139> has joined #mer22:55
*** zhxt_afk <zhxt_afk!~quassel@124.202.185.26> has quit IRC (Read error: Connection reset by peer)23:00
*** cxl000 <cxl000!~cxl000@c27-253-11-51.brodm4.vic.optusnet.com.au> has quit IRC (Quit: Leaving)23:22
*** guhl <guhl!~guhl@gateway/tor-sasl/guhl> has quit IRC (Ping timeout: 248 seconds)23:26
*** salyavin1 <salyavin1!~salyavin@gokuraku.fcac.com> has quit IRC (Ping timeout: 246 seconds)23:44

Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!