Add Hurl to official Debian repository

[fabricereix]

No description provided.

[lepapareil]

21/12/15 > Mail sent to [email protected]

[stappersg]

On Wed, Dec 15, 2021 at 06:42:41AM -0800, lepapareil wrote: 21/12/15 > Mail sent to ***@***.***`

Please elaborate

[jcamiel]

Hi @stappersg

It's just a note to ourself to keep an update on trying to add Hurl to official Debian repo.

We've 0 experience in this domain and struggle a bit to know where to start.
We've send a first mail to [email protected], as described in https://wiki.debian.org/DebianMentorsFaq#:~:text=File%20an%20ITP%20(intent%20to%20package)%20bug%20using%20reportbug to make a official request to propose Hurl.
Do you think you can help us ? Or share any experience/tips to guide us ?
Thanks,

Jc

[stappersg]

On Wed, Dec 15, 2021 at 10:17:28AM -0800, jcamiel wrote: We've send a first mail to < submit AT bugs.debian.org >

OK, that is the correct email address for reporting an "bug". Meanwhile should there be bug report number. What is it?

Do you think you can help us ?

I doing so by asking good questions.

Or share any experience/tips to guide us ?

Work in progress, currently low priority ...

[lepapareil]

Hi @stappersg, here is the bug report number https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001779.

[lepapareil]

Hi @stappersg, we probably need some help here...

Like @jcamiel said it's our first experience attempting to create a Debian package, so i wonder if we have forgotten something to move it forward since our bug report seems to be on hold for almost 3 months ?

Thks for your help :)

[stappersg]

On Thu, Mar 24, 2022 at 12:23:16AM -0700, lepapareil wrote: ... our bug seems to be on hold for almost 3 months ?

No, nothing is on hold. An request for packaging is a request for packaging.

Thks for your help :)

Expressing expectations is fine, insisting on ones own expectation doesn't help. FWIW, I only partly argee with "somebody else should do it", thing I will do is sponsoring uploads to Debian. On expressing expectations: I love to see messages like At $URL is hurl dependency foo packaged. What is, beside review time, needed to get it uploaded to Debian? Groeten Geert Stappers -- Silence is hard to parse

[lepapareil]

thks @stappersg

[jcamiel]

Doing small progress here. We can start by looking at packaging hurl-core. With cargo-debstatus, we can look which crate is available on Debian Unstable:

$ cargo debstatus --package hurl_core
 🔴 hurl_core v6.1.0-SNAPSHOT (/Users/jc/Documents/Dev/hurl/packages/hurl_core)
 ⌛ ├── colored v3.0.0 (outdated, 2.1.0 in debian)
 🔴 ├── libxml v0.3.3
    │   └── libc v0.2.169 (in debian)
    │   [build-dependencies]
    │   └── pkg-config v0.3.31 (in debian)
    └── regex v1.11.1 (in debian)

List of Rust packets available on Debian unstable (sid): https://packages.debian.org/sid/rust/.

Check that a foo crate is available : https://packages.debian.org/sid/rust/librust-foo-dev

=> We can see that the crate libxml is not in Debian Unstable. A really good first step would be to packetize libxml crate, this is a mandatory step for hurl_core to be available as a Debian packet.

We can do the same with libxml:

$ cargo debstatus
 🔴 libxml v0.3.3 (/Users/jc/Documents/Dev/rust-libxml)
    └── libc v0.2.169 (in debian)
    [build-dependencies]
    └── pkg-config v0.3.31 (in debian)
    [dev-dependencies]
    ├── criterion v0.5.1 (in debian)
    └── rayon v1.10.0 (in debian)

Every dependency crate of libxml crate is available on Debian unstable. We can try to make a first packet for it.

Regarding hurl

This is the list of crate that are not available in Debin Unstable:

cargo debstatus --package hurl
 🔴 hurl v6.1.0-SNAPSHOT (/Users/jc/Documents/Dev/hurl/packages/hurl)
 🔴 ├── hurl_core v6.1.0-SNAPSHOT (/Users/jc/Documents/Dev/hurl/packages/hurl_core)
 ⌛ │   ├── colored v3.0.0 (outdated, 2.1.0 in debian)
 🔴 │   ├── libxml v0.3.3
    │   │   └── libc v0.2.169 (in debian)
    │   │   [build-dependencies]
    │   │   └── pkg-config v0.3.31 (in debian)
    │   └── regex v1.11.1 (in debian)
    ├── base64 v0.22.1 (in debian)
 ⌛ ├── brotli v7.0.0 (outdated, 6.0.0 in debian)
    │   ├── alloc-no-stdlib v2.0.4 (in debian)
    │   ├── alloc-stdlib v0.2.2 (in debian)
    │   └── brotli-decompressor v4.0.2 (4.0.1 in debian)
    ├── chrono v0.4.39 (in debian)
    ├── clap v4.5.29 (4.5.23 in debian)
    ├── curl-sys v0.4.79+curl-8.12.0 (0.4.67 in debian)
    ├── curl v0.4.47 (0.4.44 in debian)
    ├── encoding v0.2.33 (in debian)
    ├── glob v0.3.2 (in debian)
    ├── hex v0.4.3 (in debian)
    ├── lazy_static v1.5.0 (in debian)
 ⌛ ├── libflate v2.1.0 (outdated, 0.1.25 in debian)
    │   ├── adler32 v1.2.0 (in debian)
    │   ├── core2 v0.4.0 (in debian)
    │   ├── crc32fast v1.4.2 (in debian)
    │   ├── dary_heap v0.3.7 (0.3.6 in debian)
 ⌛ │   └── libflate_lz77 v2.1.0 (outdated, 1.1.0 in debian)
    │       ├── core2 v0.4.0 (in debian)
    │       ├── hashbrown v0.14.5 (in debian)
    │       └── rle-decode-fast v1.0.3 (in debian)
 🔴 ├── libxml v0.3.3
    │   └── libc v0.2.169 (in debian)
    │   [build-dependencies]
    │   └── pkg-config v0.3.31 (in debian)
    ├── md5 v0.7.0 (in debian)
    ├── percent-encoding v2.3.1 (in debian)
    ├── regex v1.11.1 (in debian)
    ├── serde v1.0.217 (in debian)
    ├── serde_json v1.0.138 (1.0.134 in debian)
    ├── sha2 v0.10.8 (in debian)
    ├── similar v2.7.0 (2.6.0 in debian)
    ├── terminal_size v0.4.1 (in debian)
 ⌛ ├── termion v4.0.3 (outdated, 1.5.6 in debian)
    │   ├── libc v0.2.169 (in debian)
    │   └── numtoa v0.2.4 (in debian)
    ├── url v2.5.4 (2.5.2 in debian)
    ├── uuid v1.13.1 (1.10.0 in debian)
    └── xml-rs v0.8.25 (0.8.19 in debian)
    [build-dependencies]
    └── cc v1.2.13 (1.1.14 in debian)

Not regarding the version number, only hurl_core and libxml are not in Debian Unstable.