yade-dev team mailing list archive
-
yade-dev team
-
Mailing list archive
-
Message #14849
Re: Call for testing, updated yadedaily packages
-
To:
Anton Gladky <gladky.anton@xxxxxxxxx>
-
From:
Janek Kozicki <janek_listy@xxxxx>
-
Date:
Mon, 29 Jul 2019 00:22:57 +0200
-
Cc:
Yade developers <yade-dev@xxxxxxxxxxxxxxxxxxx>
-
Face:
iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAALVBMVEUBAQEtLS1KSkpRUVFXV1dYWFhjY2Nzc3N3d3eHh4eKioqdnZ24uLjLy8vc3NxVIagyAAAACXBIWXMAAAsTAAALEwEAmpwYAAAAB3RJTUUH2AIVEzgS1fgQtQAAAjRJREFUOMtt1DFv00AUAOAzFQNbjigSyoQaRaBMhKgLUyKXpVNNeUpk9vyDqFJhQ1kiBuaqAwJCqvPtSLY7RlTn5+5IdnYkkt/AOyfxXVLe5vf53Z1875kd34tOEax8djmj6GyjhB5bxz50GdsVZr9fqRjZwAtKOJw5Wqs2MMZ16ALHsaDncF7xAHix1oEFHAB8f+pRjcO4gfZDykcYzbiucRolOLUJ6kjA0xtVt+A6TySlM0RajIpK6DzwKZ/nOYbF/gclHMo1ZOHYY/+Ha+AWuM+3oMS4eeqYzZ8FiCltgUqI8cd2wwAVpJk+8LWYjBtnJdQpHQqJMd4Oxt4bU9ESiFGc5hkqaH74asAX4iabP5I5gZ+qjgGlJCqZa3h3lxhoeVcSE1qLQC4sqKOK9MGW9E3izFqqHokoztLFEgXg31sbZEKnWi2T74A4NxfVQqlkjKtcAWD+zcArFEES01dR0E/nnV0IgugmDd/2L84sOAouRBBHEc7gtc8teDkRlE0iNQPo2w3Xhh/D4TCIQ4LRLoTvgwjj6RRgavdurxYGMaIuGOyAW/PpNlCcU9/93AHenAWYjPoAwa+G3e3to/MgFNTAEKvKDjzuCzHTnY3qqdXtx24VijzQfZ0yewZ5cwRFQaa+mIYr1uI0I76+3W4xhlvoVRwOA0Fdl64HlJnxP6T8YpX/Lga4Wv4A3ErrU5oTfN7Mu/llXMl8RXEPji/lQkN3H7qXqgC2By47EXeU/7PJ/wPxRKMnuZwIeAAAAABJRU5ErkJggg==
-
In-reply-to:
<CALF6qJka0mXZc+c5eK0XQzX4Hyk1ewf084KY9TCyCozwAWfq_Q@mail.gmail.com>
Hi, I confirm that it works in my xenial chroot.
Anton Gladky said: (by the date of Sun, 28 Jul 2019 22:25:53 +0200)
> Hello all,
>
> packages for Ubuntu 16.04 Xenial are ready for testing.
> In addition to the original mail [1], this action needs to be
> done for this distribution:
>
> - Ubuntu 16.04 Xenial:
> sudo bash -c 'echo "deb http://yadedaily.s3.amazonaws.com/debian
> xenial main" >> /etc/apt/sources.list.d/yadedaily.list'
>
> Feedback is welcome.
>
> Next week there will be no updates of the yadedaily packages due to some
> technical reasons. Over the next week packages will be updated.
>
> [1] https://lists.launchpad.net/yade-dev/msg14823.html
>
> Best regards
>
> Anton
>
>
> Anton
>
>
> Am So., 28. Juli 2019 um 12:46 Uhr schrieb Janek Kozicki <janek_listy@xxxxx>:
> >
> > Looks like this conversation is now split between yade-dev and
> > https://gitlab.com/yade-dev/trunk/issues/58
> >
> > Reply to whichever you want, I monitor both channels :)
> >
> > Bruno can you make an Account for Anton on yade-dem.org ?
> >
> > I asked Anton to make .deb packages with debug symbols, but he cannot
> > upload them with his weak internet connection as they are quite large.
> >
> > After repo infrastructure is moved out of Anton's laptop we will be
> > able to provide packages with debug symbols, which will be very
> > useful: a normal user will be able to send us crash reports with
> > debug symbols.
> >
> > cheers
> > Janek
> >
> > Anton Gladky said: (by the date of Wed, 17 Jul 2019 20:17:18 +0200)
> >
> > > 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.chareyre@xxxxxxxxxxxxxxx>:
> > > >
> > > > Hi Anton,
> > > >
> > > > On Fri, 12 Jul 2019 at 19:03, Anton Gladky <gladky.anton@xxxxxxxxx> 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@xxxxxxxxxxxxxxxxxxx
> > > > Unsubscribe : https://launchpad.net/~yade-dev
> > > > More help : https://help.launchpad.net/ListHelp
> > >
> > > _______________________________________________
> > > Mailing list: https://launchpad.net/~yade-dev
> > > Post to : yade-dev@xxxxxxxxxxxxxxxxxxx
> > > Unsubscribe : https://launchpad.net/~yade-dev
> > > More help : https://help.launchpad.net/ListHelp
> >
> >
> > --
> > Janek Kozicki http://janek.kozicki.pl/ |
>
> _______________________________________________
> Mailing list: https://launchpad.net/~yade-dev
> Post to : yade-dev@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~yade-dev
> More help : https://help.launchpad.net/ListHelp
--
Janek Kozicki http://janek.kozicki.pl/ |
Follow ups
References
-
Call for testing, updated yadedaily packages
From: Anton Gladky, 2019-06-27
-
Re: Call for testing, updated yadedaily packages
From: Bruno Chareyre, 2019-06-28
-
Re: Call for testing, updated yadedaily packages
From: Anton Gladky, 2019-07-12
-
Re: Call for testing, updated yadedaily packages
From: Bruno Chareyre, 2019-07-15
-
Re: Call for testing, updated yadedaily packages
From: Anton Gladky, 2019-07-17
-
Re: Call for testing, updated yadedaily packages
From: Janek Kozicki, 2019-07-28
-
Re: Call for testing, updated yadedaily packages
From: Anton Gladky, 2019-07-28