Hello,

We just opensourced our NordVPN Linux application
and want to make it available from the public Debian repository.
As we are planning to do packaging and support by
ourselves, it is still not clear how to properly go
through the Debian packaging process and we would like
to get help and initial guidance.

So, question: which request to submit ITP or RFP ?


Best regards,
Ramunas Keliuotis

--
The content of this email, including all attachments, is confidential. If
you are not the intended recipient of this e-mail, please notify us
immediately and delete this email. Any disclosure, copying, distribution or
any other use of its content is strictly prohibited.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Hello,

Ok, thank you. Just submitted an ITP request: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038718

Now I expect we should wait for attention from debian
developer/maintainer volunteers and get
information on how to start the packaging process. Or please let me
know how to proceed to the next step.


Best regards,
Ramunas Keliuotis

On Tue, Jun 20, 2023 at 2:53 PM Preuße, Hilmar <[email protected]> wrote:

On 20.06.2023 13:34, Ramūnas Keliuotis wrote:

Hi,

We just opensourced our NordVPN Linux application
and want to make it available from the public Debian repository.
As we are planning to do packaging and support by
ourselves, it is still not clear how to properly go
through the Debian packaging process and we would like
to get help and initial guidance.

So, question: which request to submit ITP or RFP ?

ITP: Intend to package (open that if you want to maintain the package yourself).
RFP: Request for package (if you need the package, but don't want to
maintain yourself).

H.
--
sigfault

--
The content of this email, including all attachments, is confidential. If
you are not the intended recipient of this e-mail, please notify us immediately and delete this email. Any disclosure, copying, distribution or any other use of its content is strictly prohibited.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Nice,

You can take a look here now:
<https://mentors.debian.net/intro-maintainers>

در سه‌شنبه, ژوئن 20 2023 at ۱۵:۴۹:۴۲ +03:00:00,
Ramūnas Keliuotis <[email protected]> نوشته بود:

Hello,

Ok, thank you. Just submitted an ITP request: <https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038718>

Now I expect we should wait for attention from debian
developer/maintainer volunteers and get
information on how to start the packaging process. Or please let me
know how to proceed to the next step.

Best regards,
Ramunas Keliuotis

On Tue, Jun 20, 2023 at 2:53 PM Preuße, Hilmar <[email protected] <mailto:[email protected]>> wrote:

On 20.06.2023 13:34, Ramūnas Keliuotis wrote:

Hi,

We just opensourced our NordVPN Linux application
and want to make it available from the public Debian repository.
As we are planning to do packaging and support by
ourselves, it is still not clear how to properly go
through the Debian packaging process and we would like
to get help and initial guidance.

So, question: which request to submit ITP or RFP ?

ITP: Intend to package (open that if you want to maintain the
package
yourself).
RFP: Request for package (if you need the package, but don't want to
maintain yourself).

H.
--
sigfault

--
The content of this email, including all attachments, is
confidential. If
you are not the intended recipient of this e-mail, please notify us immediately and delete this email. Any disclosure, copying,
distribution or
any other use of its content is strictly prohibited.

<div id="geary-body" dir="auto"><div>Nice,</div><div><br>You can take a look here now:<br><a href="https://mentors.debian.net/intro-maintainers">https://mentors.debian.net/intro-maintainers</a></div></div><div id="geary-quote" dir="auto"><br>در سه‌�
�نبه, ژوئن 20 2023 at ۱۵:۴۹:۴۲ +03:00:00, Ramūnas Keliuotis &lt;[email protected]&gt; نوشته بود:<br><blockquote type="cite"><div class="plaintext" style="white-space: break-spaces;">Hello,

Ok, thank you. Just submitted an ITP request:
<a href="https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038718">https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038718</a>

Now I expect we should wait for attention from debian
developer/maintainer volunteers and get
information on how to start the packaging process. Or please let me
know how to proceed to the next step.


Best regards,
Ramunas Keliuotis

On Tue, Jun 20, 2023 at 2:53 PM Preuße, Hilmar &lt;<a href="mailto:[email protected]">[email protected]</a>&gt; wrote:
<blockquote>
On 20.06.2023 13:34, Ramūnas Keliuotis wrote:

Hi,

&gt; We just opensourced our NordVPN Linux application
&gt; and want to make it available from the public Debian repository.
&gt; As we are planning to do packaging and support by
&gt; ourselves, it is still not clear how to properly go
&gt; through the Debian packaging process and we would like
&gt; to get help and initial guidance.
&gt;
&gt; So, question: which request to submit ITP or RFP ?
&gt;
ITP: Intend to package (open that if you want to maintain the package
yourself).
RFP: Request for package (if you need the package, but don't want to
maintain yourself).

H.
--
sigfault

</blockquote>
<div>--
</div>The content of this email, including all attachments, is confidential. If
you are not the intended recipient of this e-mail, please notify us immediately and delete this email. Any disclosure, copying, distribution or any other use of its content is strictly prohibited.

</div></blockquote></div>

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Hi,

Thank you for the information, I was looking through Debian guides for a while. Will review your given links as well.

Now I need answers to questions:
1. Is it ok for source code to be in Github? or do I need a Salsa account?
2. Do I need to create a source package? *.dsc
3. How to implement build /scripts?
Now we are using bash scripts and preconfigured docker containers.
But dh scripts should be used, so, how to start using them?
I have installed Debian SID. I know that all dependencies must be there.

4. Also, we are using our own open source rust libraries https://github.com/NordSecurity/libtelio https://github.com/NordSecurity/libdrop
Maybe there is there a Debin Rust packaging team as well?

5. Also, we are using OpenVPN - building from C code,
but this package is long ago open source, so, assume it should be
easy to package.


Would be good to get reference to sample package - observe its build configuration.


Thank you. Regards.
Ramunas Keliuotis



On Tue, Jun 20, 2023 at 4:27 PM Arun Kumar Pariyar <[email protected]> wrote:

Hello Ramunas Keliuotis,

Here are some manuals and guides that you can use to prepare your
package. [1] [2]

As I see the source code primarily consists of Golang code, Debian Go Packaging team [3] would be something you might be interested on.

Once you finish preparing your package, you'll require a sponsor (DD)
who is interested to upload your package to the Debian archive.

Hope that helps!

[1] https://www.debian.org/doc/manuals/maint-guide/
[2] https://www.debian.org/doc/devel-manuals
[3] https://go-team.pages.debian.net/packaging.html

Regards,
~ Arun Kumar Pariyar

On 20/06/2023 18:34, Ramūnas Keliuotis wrote:

Hello,

Ok, thank you. Just submitted an ITP request: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038718

Now I expect we should wait for attention from debian
developer/maintainer volunteers and get
information on how to start the packaging process. Or please let me
know how to proceed to the next step.

Best regards,
Ramunas Keliuotis

On Tue, Jun 20, 2023 at 2:53 PM Preuße, Hilmar <[email protected]> wrote:

On 20.06.2023 13:34, Ramūnas Keliuotis wrote:

Hi,

We just opensourced our NordVPN Linux application
and want to make it available from the public Debian repository.
As we are planning to do packaging and support by
ourselves, it is still not clear how to properly go
through the Debian packaging process and we would like
to get help and initial guidance.

So, question: which request to submit ITP or RFP ?

ITP: Intend to package (open that if you want to maintain the package
yourself).
RFP: Request for package (if you need the package, but don't want to
maintain yourself).

H.
--
sigfault

--
The content of this email, including all attachments, is confidential. If
you are not the intended recipient of this e-mail, please notify us immediately and delete this email. Any disclosure, copying, distribution or any other use of its content is strictly prohibited.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Tue, Jun 20, 2023 at 05:15:05PM +0300, Ramūnas Keliuotis wrote:

1. Is it ok for source code to be in Github? or do I need a Salsa account?

It is OK for the source code to not have a VCS at all. It's also OK for
the packaging to not have a VCS at all, and these are two separate
questions, and packaging is usually stored in a separate VCS, usually on
salsa, because usually the maintainer is not the same as the upstream.

2. Do I need to create a source package? *.dsc

Yes.

3. How to implement build /scripts?

Ideally your software should have them before you start working on the packaging, because ideally your software should be buildable by anyone who downloads its source. The packaging just does the same in a more
controlled environment.

Now we are using bash scripts and preconfigured docker containers.
But dh scripts should be used, so, how to start using them?

dh should just call the upstream build system. If you are not using any
popular build system that dh can call you will need to write the necessary commands in debian/rules manually. It's also quite likely that those "bash scripts" are not suitable for this, in which case you will need to fix
them and/or switch to a proper build system.

5. Also, we are using OpenVPN - building from C code,
but this package is long ago open source, so, assume it should be
easy to package.

openvpn is of course already packaged.

Would be good to get reference to sample package - observe its build configuration.

You can look at any source package in Debian unless you need more specific examples.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

------1QM3YOULYHK857PFSEHF2EW36LVLQN
Content-Type: text/plain;
charset=utf-8
Content-Transfer-Encoding: quoted-printable

Hi,

Is it ok for source code to be in Github?

No. In my opinion (and I am aware that sadly, the majority of the project probably does not share this opinion), that is a direct violation of Debian's Code of Conduct, and its Social Contract as well.

GitHub has discriminatory terms of use that contradict Debian's values. They exclude parts of our community as contributors, e.g. persons under 16 years and persons who are unlucky enough to live in Russia, Syria, and other US-embargoed countries.

Please do not use GitHub or comparably hostile platforms for Debian.

Thanks,
Nik
------1QM3YOULYHK857PFSEHF2EW36LVLQN
Content-Type: text/html;
charset=utf-8
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE html><html><body><div dir="auto">Hi,<br><br>&gt; Is it ok for source code to be in Github?<br><br>No. In my opinion (and I am aware that sadly, the majority of the project probably does not share this opinion), that is a direct violation of
Debian's Code of Conduct, and its Social Contract as well.<br><br>GitHub has discriminatory terms of use that contradict Debian's values. They exclude parts of our community as contributors, e.g. persons under 16 years and persons who are unlucky enough
to live in Russia, Syria, and other US-embargoed countries.<br><br>Please do not use GitHub or comparably hostile platforms for Debian.<br><br>Thanks,<br>Nik</div></body></html>
------1QM3YOULYHK857PFSEHF2EW36LVLQN--

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Ramūnas Keliuotis <[email protected]> writes:

Hi,

Thank you for the information, I was looking through Debian guides for a while.
Will review your given links as well.

Now I need answers to questions:
1. Is it ok for source code to be in Github? or do I need a Salsa
account?

If you're asking if everything can be maintained on one branch, the
answer is that it will be easier to maintain a correct Debian package if
you dedicate a branch to it. Also, when configuring a branch it's
trivially easy to dedicate a different remote for the debian packaging
branch. More on this later.

The three most common workflows (in no particular order) are: 1. Use
'gbp import-orig --uscan' to download a tarball of the most recent
upstream release, and merge that to the Debian packaging branch.
2. Merge git tags to the Debian packaging branch. 3. The "packaging
branch only" approach, which only has the "debian" subdir.

2. Do I need to create a source package? *.dsc

dpkg-buildpackage, debuild, sbuild, etc. will create this for you.

https://wiki.debian.org/Packaging/SourcePackage#The_definition_of_a_source_package

3. How to implement build /scripts?
Now we are using bash scripts and preconfigured docker containers.
But dh scripts should be used, so, how to start using them?
I have installed Debian SID. I know that all dependencies must be there.

https://www.debian.org/doc/manuals/developers-reference/tools.html#dh-make

Your package will not have internet access when it is built, so all dependencies must be in debian/control.

4. Also, we are using our own open source rust libraries https://github.com/NordSecurity/libtelio https://github.com/NordSecurity/libdrop
Maybe there is there a Debin Rust packaging team as well?

Yes, if these are not in Debian then they will need to be packaged
first.

Would be good to get reference to sample package - observe its build configuration.

I would follow the Developers Reference, use dh_make, and then compare
the results with another package. Add "deb-src" lines to
/etc/apt/sources.list enables easy access to source with a simple
"debcheckout" or "apt source openvpn".

https://wiki.debian.org/Mentors

Have fun!
Nicholas

--=-=-Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQJEBAEBCgAuFiEE4qYmHjkArtfNxmcIWogwR199EGEFAmSSI4EQHHN0ZW5AZGVi aWFuLm9yZwAKCRBaiDBHX30QYXnbEACcPDR4D6yCzeJxUB4QBapwZTu7LXvdlToL O4/C5Y8LPtUvJDRhYz5tAFgA8hMdgdp1BucTSaxgV0ZqiSbUEFwRS7RZ8mWXD7Q6 s5IY++Xo9kubFGiRWbKhTYobItFBspTlHp3TL6js4hZ8pW34JL1Uia8Ed68xkFsY 07q669YKU3mh1xawslBo2majqEE+itDbJxTeDooD8i7iWN/cXgh9RSO7tlif44q2 zeOw2YiccxaJRYLtB34K8963rxY1KcYnCBeC1RCBVRRJyBZJT5xnTbVvTaBOcOXK xvrIHFkWQLywN91GEYRH3fDrYhe1SRR7gg3EJgaqAkV5cBfrjdrStHr4dCI2O93p dnKQAkJZWtbiFyjqk7OIyvo8Rfg/m5E00l8tz8iet4XeBPNZMbZTRKmBgcJMLHGn 5O6QpJ3tcqY2TKWdO1xd4LBsEqx4Q0xvGWBM7EHssP/4G/nod8ZmwEVlw0EywzkO fjyHspsthCJ4mRRr9ssoPN5eJD6rmSwc/VzYBPg2OjvzSdbhMlmZCOZA0pbEGD32 4SAcqSSfkOhqstcg1dK6rTz6nw5h45bJoPs8TyVxLVzillqH5WQ1/8sNLqvIwhaP j7HmMoBowHDvYKpEavY919un6pY4/3WAg+/YZweu59mMqvmJkJSX0akbPWXbtXvO XjHsdxi+TA==SR1d
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Copy: [email protected] (Dominik George)

This is a multi-part message in MIME format.

--nextPart2168238.WJy5SEWcXM
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="UTF-8"

I think there might be some conflation of ideas here.

1. Upstream source code for various packages is located all over the internet. If you are
asking if it is OK for your upstream to be on Github the answer is yes.

2. Most Debian packages maintain the /packaging/ source code on Salsa. This makes
sense because it makes it easy for other Debian Developers to assist you. Although it it not
required, I would highly recommend you place the packaging code on Salsa.

This is how I have handled my own software. I am the upstream developer of Privacy
Browser. My program source code is on a Git instance I run on my own hardware and is
accessible through a gitweb instance at:

https://gitweb.stoutner.com/?p=PrivacyBrowserPC.git;a=summary[1]

However, all of my packaging code is in a Salsa repository:

https://salsa.debian.org/sorenstoutner/privacybrowser[2]

Along these lines, I would highly recommend you use git-buildpackage to handle the
creation and updating of the Git packaging branches/tags.

https://packages.debian.org/sid/git-buildpackage[3]

You will see this referenced in some of the documentation that has already been suggested
to you, although much of the documentation was written before git-buildpackage was in
common use, so it tends to reference older methods of doing things.

Trying to figure out Debian packaging can feel a bit like drinking from a firehose. Don’t feel
overwhelmed. It tends to take about three months to wrap your mind around it. And
people on this mailing list are generally happy to help you out.

On Tuesday, June 20, 2023 11:18:34 AM MST Dominik George wrote:

Hi,

Is it ok for source code to be in Github?

No. In my opinion (and I am aware that sadly, the majority of the project probably does not share this opinion), that is a direct violation of
Debian's Code of Conduct, and its Social Contract as well.

GitHub has discriminatory terms of use that contradict Debian's values. They exclude parts of our community as contributors, e.g. persons under 16 years and persons who are unlucky enough to live in Russia, Syria, and other US-embargoed countries.

Please do not use GitHub or comparably hostile platforms for Debian.

Thanks,
Nik

--
Soren Stoutner
[email protected]

--------
[1] https://gitweb.stoutner.com/?p=PrivacyBrowserPC.git;a=summary
[2] https://salsa.debian.org/sorenstoutner/privacybrowser
[3] https://packages.debian.org/sid/git-buildpackage --nextPart2168238.WJy5SEWcXM
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html; charset="UTF-8"

<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body><p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">I think there might be some conflation of ideas here.</p>
<br /><p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">1.&nbsp; Upstream source code for various packages is located all over the internet.&nbsp; If you are asking if it is OK for your upstream to be on Github the answer is yes.</p>
<br /><p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">2.&nbsp; Most Debian packages maintain the <em>packaging</em>&nbsp;source code on Salsa.&nbsp; This makes sense

Hi,

On 2023-06-20 17:15, Ramūnas Keliuotis wrote:

4. Also, we are using our own open source rust libraries https://github.com/NordSecurity/libtelio https://github.com/NordSecurity/libdrop
Maybe there is there a Debin Rust packaging team as well?

Yes, there is Debian Rust packaging team [1]. According to the linked
wiki page, Rust crate packaging is largely automated. If NordVPN depends
on libdrop and libtelio, I would suggest starting from packaging them.

[1] https://wiki.debian.org/Teams/RustPackaging

Best wishes,
Andrius

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)