add Devuan the apt list

changed the description

Do you want to make the PR on gerrit? (It's better to have the good author name as the author, and better for review)

But yeah, if this works for devuan, we can change the make-ring.py.

added build label

I am in the process of familiarising myself with gerrit.

Then I will submit each change individually.

None of these changes are really any more than "getting it to build" with the provided tool. (make-ring.py)

The devuan addition to the apt list is almost decorative. ( there should be almost no difference in packages to upstream debian _unless systemd is directly_ involved and then its something "devuanites" are used to in any case :)

However the shift in devlib names is actually an issue as with the current apt-get instruction the script fails. (rightly so)

I am also on the steep part of the learning curve around the project structure generally. The reason I cloned in the first place was to track some errors :)

gerrit and I do not agree on almost anything.

I am missing something really obvious I guess.

( I followed the instructions on review.jami.net )

" git push origin HEAD:refs/for/master " Using the USERNAME as per my account on review.jami.net

Tried the https password

Tried the ssh type password and uloading a pubkey etc.

(which gives me forbidden / not allowed errors)

Is there another git I need to clone ??

Or some setting I need to make to my local .gits ?

Tried setting project username and email address to match ... (and other random desperate guesses measures)

** The changes are all in the previously attached file. **

also a diff -u patch is attached to THIS message

I was trying to stage them in. But its the best I could manage.

Apologies if I missed a big green button or a gerrit convention someplace.

e.g.


$ git push origin HEAD:refs/for/master
Username for 'https://git.jami.net': PeteGozz
Password for 'https://PeteGozz@git.jami.net': 
remote: You are not allowed to push code to this project.
fatal: unable to access 'https://git.jami.net/savoirfairelinux/ring-project.git/': The requested URL returned error: 403

FWIW I would be surprised if I WAS allowed to actually hit the live code :)

** ATTACHED: is a diff -u **

make-ring.py-devuan-libupnp.diff

See https://git.jami.net/savoirfairelinux/ring-project/wikis/tutorials/Working-with-gerrit

git.jami.net is our Gitlab server and is a mirror of gerrit. The remote should be "ssh://YOUR_USER@review.jami.net:29420/ring-project", So can you try "git remote set-url origin ssh://YOUR_USER@review.jami.net:29420/ring-project" and then push.

Note, if you use ssh, you need to add your ssh key in the profile on the gerrit profile page.

Also if you want to log into "review.jami.net", click on "Sign in", Gitlab => log into gitlab.

I hope it's more clear :)

Ah thank you ! I am following your notes and have (dutifully) read the Working-with-gerrit tutorial.

cough one issue was I was trying to load jami-project rather than ring-project.

[short version] is now I can ssh clone a fresh repository of ring-project and will continue on with the pushes later today. (all going well)

For General information I generated a specific "-t rsa" ssh key and used the following (over featured) ~/.ssh/config stanza :


Host JamiReview
Hostname review.jami.net
AddressFamily inet
Port 29420
User PeteGozz
IdentityFile ~/.ssh/jami-review-gerrit
# ControlPath ~/.ssh/ssh_control_sockets/%r@%h:%p
# ControlPersist 60
# ControlMaster auto
TCPKeepAlive yes
ServerAliveInterval 60
# StrictHostKeyChecking no
VisualHostKey yes

Which means I only have to get this clone string correct :)

git clone "ssh://JamiReview:29420/ring-project"

For a real result :) (though I didn't even need the port number ... )

...

Cloning into 'ring-project'
<snips>
remote: Counting objects: 6, done
remote: Finding sources: 100% (2306/2306)
remote: Total 2306 (delta 1359), reused 2306 (delta 1359)
Receiving objects: 100% (2306/2306), 517.63 KiB | 884.00 KiB/s, done.
Resolving deltas: 100% (1359/1359), done

.

...

Thank you @sblin for the clear assistance . [ edits to # optionalise Control Path settings in ssh/conf file. ]

I seem to be able to get all the way to push. AOK. However

Enumerating objects: 5, done.
Counting objects: 100% (5/5), done.
Delta compression using up to 2 threads
Compressing objects: 100% (2/2), done.
Writing objects: 100% (3/3), 450 bytes | 450.00 KiB/s, done.
Total 3 (delta 2), reused 1 (delta 1)
remote: Resolving deltas: 100% (2/2)
remote: error: branch refs/heads/master:
remote: To push into this reference you need 'Push' rights.
remote: User: PeteGozz
remote: Contact an administrator to fix the permissions
remote: Processing changes: refs: 1, done
To ssh://JamiReview:29420/ring-project
 ! [remote rejected] master -> master (prohibited by Gerrit: not permitted: update)
error: failed to push some refs to 'ssh://JamiReview:29420/ring-project'

Here is what local git says::

kant 61 [Mon Aug 26 01:16 PM] pete:~/sources/ring-project$ git config --local --list
core.repositoryformatversion=0
core.filemode=true
core.bare=false
core.logallrefupdates=true
remote.origin.url=ssh://JamiReview:29420/ring-project
remote.origin.fetch=+refs/heads/*:refs/remotes/origin/*
branch.master.remote=origin
branch.master.merge=refs/heads/master
user.name=PeteGozz
user.email=poota@internode.on.net
submodule.client-android.active=true
submodule.client-android.url=https://review.jami.net/ring-client-android
submodule.client-electron.active=true
submodule.client-electron.url=https://review.jami.net/ring-client-electron
submodule.client-gnome.active=true
submodule.client-gnome.url=https://review.jami.net/ring-client-gnome
submodule.client-ios.active=true
submodule.client-ios.url=https://review.jami.net/ring-client-ios
submodule.client-macosx.active=true
submodule.client-macosx.url=https://review.jami.net/ring-client-macosx
submodule.client-uwp.active=true
submodule.client-uwp.url=https://review.jami.net/ring-client-uwp
submodule.client-windows.active=true
submodule.client-windows.url=https://review.jami.net/ring-client-windows
submodule.daemon.active=true
submodule.daemon.url=https://review.jami.net/ring-daemon
submodule.lrc.active=true
submodule.lrc.url=https://review.jami.net/ring-lrc

Indeed, nobody can push directly to master, you need to follow the link I gave you (https://git.jami.net/savoirfairelinux/ring-project/wikis/tutorials/Working-with-gerrit#to-create-the-review)

git push origin HEAD:refs/for/master, this will create the patchset.

I wrote up a "howto". ... may be useful for others... ... It may also be totally misguided ...

Setting up git and ssh

(to work smoothly with Gerrit.)

first see:

'creating a gerrit review' https://git.jami.net/savoirfairelinux/ring-project/wikis/tutorials/Working-with-gerrit#to-create-the-review

Then perhaps this walk through may help.

ssh setup

Generate the key set

Generate a personal dedicated public / private key set.

...

$ `ssh-keygen -t rsa -f ~/.ssh/jami_gerrit_review_rsa`

...

reports::

Generating public/private rsa key pair.

Your identification has been saved in jami_gerrit_review_rsa.

Your public key has been saved in jami_gerrit_review_rsa.pub.

Tell gerrit your public key

Login to your gerrit account

https://git.ring.cx/users/sign_in
- Best use your Jami Gitlab OAuth access
- Standard TAB (unless you know otherwise)
This OAuth remote login process will send you to:

https://review.jami.net

Follow the ssh key instructions found from (your) user options settings.

https://review.jami.net/settings/

so for example::

...

' $ cat ~/.ssh/jami_gerrit_review_rsa.pub '

...

(paste that output into the [ New SSH key ] field, down the page)

https://review.jami.net/settings/#SSHKeys
Set up Your Local ssh

edit ~/.ssh/config

Contruct a Hostname stanza to suit this gerrit .

This will configure ssh connections using::

The public key generated above
YOUR_GERRIT_USERNAME
the correct port number
the correct URL

and (optionally) other settings to taste

So for example::

Host JamiReview
Hostname review.jami.net
AddressFamily inet
#AddressFamily inet6
Port 29420
User YOUR_GITLAB_USERNAME_GOES_HERE
IdentityFile ~/.ssh/jami_gerrit_review_rsa
TCPKeepAlive yes
ServerAliveInterval 60
#StrictHostKeyChecking no
#VisualHostKey yes

Test all of the above.

...

' $ ssh JamiReview '

...

Your Repository

This assumes you have moved any existing project clone out of the way.

Clone a (fresh) copy of the project.

' $ git clone ssh://JamiReview/PROJECT_NAME_GOES_HERE.git '

for example:: ...

' $ git clone ssh://JamiReview/ring_project.git '

...

Configure this clones local .git/config

** Before you edit or even locally commit any source code. **

Its easiest and (for me at least) less surprising if you set up your local repositories git just a little more.

...

' $ cd project_name '

...

First gather some scope, context, current state.

...

' $ git config --list '

...

and compare with the output of these.

...

' $ git config --local --list ' ' $ cat .git/config '

...

Set gits remote access origin
- The URL and by extension ssh details (which you built in the 'ssh setup'_ section above)

...

' $ git remote set-url origin ssh://JamiReview/PROJECT_NAME_GOES_HERE '

' $ git config --local --list '

...

Validate: (remote.origin.url=ssh://JamiReview/ring-project)

Push by Default in refs/for/master

You can configure git to automatically create a review when you push a change from here.

...

' $ git config remote.origin.push HEAD:refs/for/master '

' $ git config --local --list '

...

Validate: (remote.origin.push=HEAD:refs/for/master)

Generate commit Change-Ids

aka: commit-msg hook script

A shell script, to be installed to .git/hooks/commit-msg.

The script creates a unique Change_Id:hash for each commit made from your repository.

The first time you attempt a push to review, gerrit will notice a lack of Change-Id.

( and refuse to "publish" the push )
Gerrit will also present a secure copy (scp) string. Use that to download a copy of .git/hooks/commit-msg.

(you will probably need to tell scp which identity file to include.)
something like::

' -i ~/.ssh/jami_gerrit_review_rsa '

This string should work with the above ssh set up.::
```
...

' $ `scp  JamiReview:hooks/commit-msg  .git/hooks/` '

...
```

References

[creating a gerrit review] https://git.jami.net/savoirfairelinux/ring-project/wikis/tutorials/Working-with-gerrit#to-create-the-review

[uploading SSH PUBLIC key] https://review.jami.net/Documentation/user-upload.html#ssh

[Some Gritty Details] https://review.jami.net/Documentation/user-upload.html#_gritty_details

Tues 27th August 2019 Peter Gossner eof

setupgit.txt

Its in simple rst format .

I will update the wiki as soon as possible

Just for your info, this will take some time for the review, because I'll have to setup a Devuan VM and correctly test it before actually merging it :)

Bugger. Like I said not a huge issue. Just nice if the option is available.

If there is some lockin to systemd devuan will try to remove it themselves. Its what they do :) If they have an issue they will contact you (upstream) . ...

Devuan essentially tracks Debian stable testing and unstable really closely.

Beyond cleaning out as much of systemd as possible:: There is some (often intense) user level focus on the lighter desktops, and login GUI's (slim or lightdm ) eudev is used instead of udev. Dbus is supported. (so far :)

The system level daemon launch stuff is sysv init.d by default. However users use whatever init they like or need.

The approach is that if it works on Debian then Devuan makes it work as well.

Packages are imported (per instance) direct from debian and if there is no issue they go straight through. Otherwise apt dpkg's equivs system is used to replace them.

(( except for the systemd ... um ... dependency tree ))

Having rabbited on about all that ... just go with a default install :) It certainly wont hurt.

Actually its not only the equivs approach , there are dedicated packages built as well. So far as a (nominally typical[1]) devaun user, running either E16 or openbox as a desktop environment, I can run gnome-ring OK with only occasional issues::

dring instances not stopping on logout, and
some interface sizing issues... lag on updates ...

None of them scratchy enough (yet), for me to grok all that C++.

[1] There is no such thing I suspect.

@PeteGozz at least, I added your page to our docs with some quick modifications (we use markdown btw)

https://git.jami.net/savoirfairelinux/ring-project/wikis/technical/4.2.-Submit-your-first-patch

I mainly removed duplicated links + the .ssh part. I think the full commands should be given, if anyone wants to change the default commands by editing a local .config, they can do that, but I prefer to not mention it in a general doc.

But feel free to improve the page. For now, only devs can update the doc. Maybe I will move it to a dedicated repo to make contributions easy.

Nice work editing all that verbose guff down @sblin :)

Hopefully its a helpful walk through.

closed

add Devuan the apt list

Designs

Child items ...

Activity

Setting up git and ssh

ssh setup

Your Repository

References