Next month there would be new delivery of the course.
This is great news! Thanks a lot!
@talkless In my containers I replaced all urls by http://old-releases.ubuntu.com/ubuntu
also the ports ones
vivid vivid-security vivid-backports vivid-updates (main / multiverse / restricted / universe) are all included there
But there's no
ubuntu-ports repository (directory) inside http://old-releases.ubuntu.com/
I did this:
lxc exec device-armhf -- /bin/bash
old-releasesin sources.list with
sed -i "s|archive|old-releases|" /etc/apt/sources.list
But after that, running apt update inside container, I get errors about
ports.ubuntu.com/ubuntu-ports/dists/vivid/... (404 Not Found), while
old-releases works fine for other repositories.
There are in fact no
vivid in this repo:
So what cane ports host be changed into? Is there archive as that
As far as I understand, the problem is to update the kits, not my system which is perfectly up to date
It seem so. I guess we need to update
lxd contaner used for building?
In our country, mobile carriers provide "Mobile Signature" service, that allows to use mobile phones for logging into bank accounts, government institutions (tax office for example), and digitally sign documents there, etc .
It has to do with some keys stored into SIM card which is provided by the carrier. User has to enter PIN code to confirm operation while logging into web application.
I guess some explicit implementation are needed to handle PIN prompts. Does anyone knows anything more tangible than I have written here?
My phone is E5 btw.
After this there was no zfs option available at all.
so had to use this
sudo apt install -t xenial-backports lxd lxd-client
xenial-backports helped to overcome that
Creating the bridge failed with: not implemented issue.
It would be nice to have this hint in Course.
Now, as I'm not a dev, I have to create a GH account to push back the changed code. From there I need some help... Can someone briefly tell me how to do it safely?
What do you mean by safely?
Generally, you create GitHub account, fork the project, checkout into your computer, do some changes, commit, push it back to GitHub (
git push origin master if you working on master branch) and then, inside GitHub interface, you click "New pull request" (or similar) to begin review process.
KeePit maintainer will review your changes and pull into official repository if all is alright (or all issues are fixed in the pull request by your updates).
Thanks to you guys I got my new phone! Yay.
Congrats! That was fast :) .
Yes I am but I'll be up-front with you I probably have less time to do that now than I did before.
It would still be fortunate to have active maintainer, even with limited time allocated.
New features or other big changes can be implemented by contributors.
Looks like your connection to UBports Forum was lost, please wait while we try to reconnect.