Maintaining Jami #4

Maintaining Jami #4

[Jan]

Hello,
Sorry for the delay with Jami, but I lost access to my repository and
must make a new one. I'm also waiting for the developer responsible
for updating pjproject in Jami to update pjproject - he's on holidays
till the end of Feb. Waiting for core-updates to be merged too, in order
to check if the outdated glibc is a problem with one crash.
When will be the 1.1.0 version of Guix released?
The good news is pjproject 2.10 is out fixing many crashes.

Anyone knows how to upload git repository with Guix to Gitlab?


Jan Wielkiewicz

Re: Maintaining Jami #4

[Pierre Neidhardt]

[-- Attachment #1: Type: text/plain, Size: 217 bytes --]

Jan <tona_kosmicznego_smiecia@interia.pl> writes:

> Anyone knows how to upload git repository with Guix to Gitlab?

What do you mean?  Can you provide an example?

-- 
Pierre Neidhardt
https://ambrevar.xyz/

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

Re: Maintaining Jami #4

[Jan Wielkiewicz]

On Mon, 17 Feb 2020 17:46:39 +0100
Pierre Neidhardt <mail@ambrevar.xyz> wrote:

> What do you mean?  Can you provide an example?
> 
For example on notabug there was an option to make a mirror of existing
repository, so I just pasted there:
"https://git.savannah.gnu.org/git/guix.git" 
and it made a mirror I could work with.
On gitlab I didn't see such an option, so I just initialized a fresh
git repository and I would like to replace this repository with my
clone of Guix with Jami changes.


Jan Wielkiewicz

Re: Maintaining Jami #4

[Pierre Neidhardt]

[-- Attachment #1: Type: text/plain, Size: 456 bytes --]

What you need to do is the following:

- Create an empty repo on GitLab.
- In your local checkout of Guix, add your GitLab repository as a Git
  remote.
- Push to your GitLab repository.
- Create a wip-jami branch and commit your changes there.
- Whenever you want to update "master", simply "git fetch --all" then
  rebase your wip-jami onto origin/master.

Let me know if you want more details.

-- 
Pierre Neidhardt
https://ambrevar.xyz/

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

Re: Maintaining Jami #4

[Jan]

On Mon, 17 Feb 2020 18:42:05 +0100
Pierre Neidhardt <mail@ambrevar.xyz> wrote:

> What you need to do is the following:
> 
> - Create an empty repo on GitLab.
> - In your local checkout of Guix, add your GitLab repository as a Git
>   remote.
> - Push to your GitLab repository.
> - Create a wip-jami branch and commit your changes there.
> - Whenever you want to update "master", simply "git fetch --all" then
>   rebase your wip-jami onto origin/master.
> 
> Let me know if you want more details.
> 

Nope, that'll do, did something similar already. Thanks!


Jan Wielkiewicz

Re: Maintaining Jami #4

[Jan Wielkiewicz]

Dnia 2020-02-17, o godz. 18:42:05
Pierre Neidhardt <mail@ambrevar.xyz> napisał(a):

> What you need to do is the following:
> 
> - Create an empty repo on GitLab.
> - In your local checkout of Guix, add your GitLab repository as a Git
>   remote.
> - Push to your GitLab repository.
> - Create a wip-jami branch and commit your changes there.
> - Whenever you want to update "master", simply "git fetch --all" then
>   rebase your wip-jami onto origin/master.
> 
> Let me know if you want more details.
> 

I guess that's it, here's my most up-to-date work:
https://gitlab.com/kromka_chleba/jami-package-and-other-things-for-guix/

Now I must set up a channel and check how it behaves.


Jan Wielkiewicz

Re: Maintaining Jami #4

[Pierre Neidhardt]

[-- Attachment #1: Type: text/plain, Size: 234 bytes --]

Note that if you want to set up a channel that composes with current
Guix, you should not track upstream then, your channel should have only
the packages that you want to distribute.

-- 
Pierre Neidhardt
https://ambrevar.xyz/

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]