Hi Bruno, > Was there specific difficulties with ubuntu16.04 (even if it's getting old > I'm sure there would be users of it)?
Basically - Qt4 orientation of the GUI. So, debian rules should be patched to use it. But if you think it is necessary for the users - let's try to do it. > - Where to host: yade-dem.org is available like before (it's on a brand new > hardware and it should stay for years), we need to give you access to it I > guess. Yes. Ideally there should be possible to run a docker. And also it would be good to have an access to the folder, which is symlinced to the the yade-dem.org/packages. > - Who/how to sign the packages: I don't see it very convenient if you have to > do anything manually, we are updating master many times a day at the moment. > Or maybe a few of us need to learn how to do it to. It is extremely easy. It runs similar to the documentation: packages should be pulled from gitlab, signing etc is done by this script [1] and aptly. Dockerfile for the image is here [2] [1] https://gitlab.com/yade-dev/trunk/blob/master/scripts/ppa_ci/aptly/update_repos_next.sh [2] https://gitlab.com/yade-dev/trunk/blob/master/scripts/ppa_ci/aptly/Dockerfile Regards Anton Am Mo., 15. Juli 2019 um 18:23 Uhr schrieb Bruno Chareyre <bruno.chare...@3sr-grenoble.fr>: > > Hi Anton, > > On Fri, 12 Jul 2019 at 19:03, Anton Gladky <gladky.an...@gmail.com> wrote: >> >> Comments, critic are >> very welcome. > > > This is great! Thank you very much. > Was there specific difficulties with ubuntu16.04 (even if it's getting old > I'm sure there would be users of it)? > If yes, then let it be. If it just needs to add a name in [1] then it's maybe > worth it. > [1] > https://gitlab.com/yade-dev/trunk/merge_requests/185/diffs#9e4f27c17b0dc74b4dff4de88036f97a4daf0f00_0_7 > >> >> > p.s. just curious about the amazonaws hosting, issues with gitlab.com? If >> > it helps local server yade-dem.org can be used to. Nothing against >> >> Now it is done on my laptop and I am just using the Amazon S3 for testing >> purposes. >> We can surely use it further, but I would also prefer to move to >> yade-dem.org. >> But we need to coordinate that. > > > Ok. There are two questions then: > - Where to host: yade-dem.org is available like before (it's on a brand new > hardware and it should stay for years), we need to give you access to it I > guess. > - Who/how to sign the packages: I don't see it very convenient if you have to > do anything manually, we are updating master many times a day at the moment. > Or maybe a few of us need to learn how to do it to. > > >> >> Theoretically, we could use the gitlab infrastructure to build the >> repository as well. >> But the problem is that it should be signed by the private yade-GPG key. >> And I would escape to upload this private key into the gitlab servers due >> to security concerns. Maybe I am missing something. > > > I know exactly what you mean. That's why currently yade-dem.org does wget the > documentation from gitlab (checking every 10 minutes or so) instead of gitlab > pushing actively. We did not like giving credentials to gitlab. > I don't think you missed anything, there is no escape on this aspect. > > Regards > > Bruno > > _______________________________________________ > Mailing list: https://launchpad.net/~yade-dev > Post to : yade-dev@lists.launchpad.net > Unsubscribe : https://launchpad.net/~yade-dev > More help : https://help.launchpad.net/ListHelp _______________________________________________ Mailing list: https://launchpad.net/~yade-dev Post to : yade-dev@lists.launchpad.net Unsubscribe : https://launchpad.net/~yade-dev More help : https://help.launchpad.net/ListHelp