Re: New package: ITP or RFP ?

[Andrius Merkys]

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

Re: New package: ITP or RFP ?

[Nicholas D Steeves]

Ramūnas Keliuotis  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


signature.asc
Description: PGP signature

Re: New package: ITP or RFP ?

[Dominik George]

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

Re: New package: ITP or RFP ?

[Andrey Rakhmatullin]

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.

Re: New package: ITP or RFP ?

[Ramūnas Keliuotis]

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  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  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.

Re: New package: ITP or RFP ?

[Danial Behzadi]

Nice,

You can take a look here now:


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

Hello,

Ok, thank you. Just submitted an ITP request:


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 > 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.

Re: New package: ITP or RFP ?

[Arun Kumar Pariyar]

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  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





OpenPGP_0x4B542AF704F74516.asc
Description: OpenPGP public key


OpenPGP_signature
Description: OpenPGP digital signature

Re: New package: ITP or RFP ?

[Ramūnas Keliuotis]

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  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.

Re: New package: ITP or RFP ?

[Preuße , Hilmar]

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



OpenPGP_0x0C871C4C653C1F59.asc
Description: OpenPGP public key


OpenPGP_signature
Description: OpenPGP digital signature

New package: ITP or RFP ?

[Ramūnas Keliuotis]

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.