| dcaliste | chriadam, jpetrell: I'm currently checking and ironing remaining bugs when signing an outgoing email with an S/MIME key. Some time ago, I mentioned that dirmngr package is required (it's part of GnuPG also, but at the versin we have, it was not included yet). Who should I ping to have it included in Mer ? | 08:45 |
|---|---|---|
| chriadam | dcaliste: hi | 08:45 |
| dcaliste | I've created RPM packaging for it in gitlab.merproject.org/dcaliste/dirmngr | 08:46 |
| chriadam | lbt: is probably the right person | 08:46 |
| dcaliste | Hello chriadam, I hope you're fine. | 08:46 |
| chriadam | dcaliste: not too bad. sorry I wasn't at the meeting on Tuesday, I had to leave the office early | 08:46 |
| chriadam | dcaliste: I hope you're well also? | 08:46 |
| lbt | chriadam: I can do the actual setup but in general packages need to be approved by a maintainer | 08:47 |
| lbt | chriadam: so if this goes into your section of the Maintainers file then I need a nod from you :) | 08:48 |
| chriadam | lbt: at least gnupg2 is part of Base Packages, which you're the master for :-P I'm a developer for that one. | 08:48 |
| chriadam | not sure if dirmgr should go to the same package group or not, I assume so? | 08:49 |
| lbt | the general question for me is who's going to a) care about and b) be impacted by .... upstream releases and CVEs | 08:49 |
| chriadam | I can't put up my hand to be maintainer in that sense, my plate is already too full as it is :-/ | 08:50 |
| lbt | if b) is multiple areas then it goes into the base section | 08:51 |
| chriadam | as to what effect would a CVE in dirmgr have - dcaliste this doesn't affect e.g. root CA or similar, it only affects signatures on emails, right? | 08:51 |
| dcaliste | Thank you lbt and chriadam, dirmngr is now part of GnuPG package itself, but since we're stucked at version 2.0.4 because of licensing, dirmngr was at that time a separated tar.gz. | 08:51 |
| lbt | chriadam: that's my point - I would tend to put it in the same group as email stuff for that reason | 08:51 |
| dcaliste | I think dirmngr is only used by gpgsm (which is GnuPG implementation of S/MIME protocol). | 08:51 |
| chriadam | lbt: that makes sense. I wonder if we should move gnupg2 to email section also | 08:52 |
| lbt | I suspect so | 08:52 |
| lbt | question b) .... | 08:52 |
| lbt | who else is impacted by it ... if no-one then yes | 08:52 |
| dcaliste | about moving gnupg to email section, I'm not sure, depends if some other parts will use gpg to sign packaging or repo for instance. | 08:53 |
| dcaliste | Like what abranson is discussing at the moment in ssu. | 08:53 |
| chriadam | ah, good point... urgh. abranson do you know if rpm / ssu using signed stuff is using gnupg for signatures? | 08:53 |
| lbt | *nod* ... so I'm kinda using this as an example of the thinking behind where it goes in Maintainers | 08:54 |
| chriadam | makes sense | 08:54 |
| lbt | Once that is answered then I have no issue in putting it into base | 08:54 |
| lbt | I mean mer-core | 08:54 |
| abranson | hmm no I don't sorry. i guess openssl though? | 08:54 |
| dcaliste | About maintenance of dirmngr, the real issue IMHO is that dirmngr as a separate package from gnupg is not supported anymore, it even have no repo anymore. I only found an old tar.gz on the gnupg ftp server. | 08:55 |
| chriadam | lbt: so, dirmngr is only used for the s/mime plugin of gnupg, which is strictly email related. but gnupg itself may be used for other purposes. do we want to keep them together for maintenance reasons? or separate for impact reasons? | 08:56 |
| dcaliste | If gnupg is used only for email at the moment, that's a good opportunity when adding dirmngr to email to move gnupg to email also. Otherwise, it's fine to have them separated. | 08:57 |
| dcaliste | Clearly, dirmngr will be used in the forseeable future only for S/MIME email signatures. | 08:57 |
| chriadam | if abranson isn't aware of any other usages of gnupg2 in sfos currently, I'd vote for it to be moved to email also | 08:58 |
| lbt | chriadam: good question - but I'd go with dirmngr in email for now; especially since it'll vanish 'soon' (if I understand correctly) | 08:58 |
| dcaliste | Well, soon means when GPLv3 will be allowed, which may not be that soon… | 08:58 |
| lbt | volume_key-libs and then gpgme -> libzypp | 08:59 |
| chriadam | volume_key-libs? eh? | 09:01 |
| lbt | block crypto | 09:01 |
| dcaliste | I was thinking music volume too, not logical volume ;) | 09:01 |
| lbt | just rpm --test -e on the device :) | 09:01 |
| chriadam | ah! LVM | 09:01 |
| chriadam | sorry it's late my brain isn't working | 09:01 |
| lbt | np :) | 09:02 |
| chriadam | rainemak do we use that for luks etc? | 09:02 |
| lbt | so I expected gpg to be used a bit more widely tbh | 09:02 |
| chriadam | ok, so no moving gnupg2 to email. | 09:02 |
| chriadam | but dirmngr belongs there | 09:02 |
| lbt | and I think it makes sense for gpg to stay in base and dirmngr to go to email | 09:02 |
| chriadam | +1 from me | 09:03 |
| lbt | and it'll be clear there's a BR | 09:03 |
| lbt | so I need an MR for Maintainers file to add it to a group please | 09:03 |
| * lbt looks at dcaliste :) | 09:03 | |
| chriadam | ssh://git@git.merproject.org:2222/mer-core/Maintainers.git | 09:03 |
| dcaliste | Sorry, was discussing with my boss, so I'm adding dirmngr to the email category ? | 09:09 |
| chriadam | no problem, and yes :-) | 09:10 |
| chriadam | should probably add yourself as a developer to email and to secrets/crypto category also | 09:10 |
| dcaliste | I can't find any email category by itself… QMF is in contact and communication middleware and nemo-qml-plugin-email is in QML middleware (which sound reasonable). | 09:11 |
| chriadam | oops | 09:12 |
| dcaliste | secret and crypto neither since it's in Github, not in mer. | 09:13 |
| chriadam | ah | 09:13 |
| chriadam | of course | 09:13 |
| dcaliste | I'm looking where I can put it safely though… | 09:13 |
| chriadam | although, that's curious | 09:13 |
| * chriadam has to head off, late night shopping tonight and need to buy a present for my nephew | 09:15 | |
| chriadam | gnight! | 09:15 |
| dcaliste | lbt, chriadam: well I would be willing to create an email package-group, like there is one for calendar and move there messagingframework and dirmngr. | 09:15 |
| dcaliste | chriadam, sure good night. | 09:15 |
| chriadam | if there's antyhing you need me to do, email me the instructions and I'll do it tomorrow asap | 09:15 |
| lbt | I think comms middleware sounds reasonable. chriadam is master there too | 09:17 |
| dcaliste | lbt: yes you're right, and messagingframework is depending on libaccounts and other things there. So I'm adding dirmngr there also. | 09:18 |
| tortoisedoc_ | hello | 11:18 |
| tortoisedoc_ | if in obs I have repositories configured but no build targets | 11:18 |
| tortoisedoc_ | what does it mean? | 11:18 |
| tortoisedoc_ | ha | 11:19 |
| tortoisedoc_ | it means the default repo which is added to the created package automatically doesnt exist :P | 11:20 |
| tortoisedoc_ | readding a repo fixes that | 11:20 |
| tortoisedoc_ | hmm | 11:33 |
| tortoisedoc_ | lbt : how comes i get this https://build.merproject.org/project/show/home:tortoisedoc:branches:mer-core:devel | 11:33 |
| tortoisedoc_ | when I try to branch a mer-devel pkg? | 11:33 |
| lbt | because https://build.merproject.org/project/show/mer-core:devel | 11:34 |
| lbt | and because mer-core is deprecated | 11:34 |
| lbt | use mer:core | 11:34 |
| lbt | I have tried to clean up in the past but it's a laborious manual task | 11:36 |
| lbt | and I've not done it for a while | 11:36 |
| r0kk3rz | yeah theres a lot of stuff that needs nuking | 12:02 |
| mal | quite many obsolete projects there | 12:04 |
| *** ersatzmaus is now known as fledermaus | 13:29 | |
| *** rinigus[m] is now known as rinigus | 19:48 | |
| attah | Somewhat stupid questions... how do i connect the cover actions to my mediaplayer, and where do i keep the object if i want playback across several pages? | 20:09 |
| attah | I saw someone putting a shitload of loose signal definitions in the ApplicationWindow, but i forget where | 20:10 |
| kimmoli | just put them in there. qtcreator just fails to autocomplete them | 20:12 |
| kimmoli | in applicationwindow | 20:12 |
| attah | well, i'm still at the where part | 20:16 |
| attah | sailfish docs says nada about signals in the cover example | 20:18 |
| mal | attah: here is an example https://github.com/joonne/harbour-nayttamo/blob/master/qml/main.qml | 20:20 |
| attah | thanks | 20:21 |
| kimmoli | https://github.com/kimmoli/chargemon/tree/master/qml sample of somewhat dynamic coveractions | 20:23 |
| attah | mal: thanks again... too easy! | 20:26 |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!