Signed-off-by: Dylan Aïssi <dylan.aissi@collabora.com>

Signed-off-by: Dylan Aïssi <dylan.aissi@collabora.com>

Signed-off-by: Ryan Gonzalez <ryan.gonzalez@collabora.com>

Signed-off-by: Dylan Aïssi <dylan.aissi@collabora.com>

Signed-off-by: Dylan Aïssi <dylan.aissi@collabora.com>

Signed-off-by: Dylan Aïssi <dylan.aissi@collabora.com>

Signed-off-by: Walter Lozano <walter.lozano@collabora.com>

Signed-off-by: Walter Lozano <walter.lozano@collabora.com>

Signed-off-by: Arnaud Ferraris <arnaud.ferraris@collabora.com>

Signed-off-by: Arnaud Ferraris <arnaud.ferraris@collabora.com>

Our previous patch was flawed in that it didn't allow for multiple `-k`
arguments. Upstream came up with a better solution so we should switch
to that one.

Signed-off-by: Arnaud Ferraris <arnaud.ferraris@collabora.com>

Signed-off-by: Frédéric Danis <frederic.danis@collabora.com>

Backport upstream fixes as `tr` fails to replace characters in squeeze-repeats
mode

Signed-off-by: Frédéric Danis <frederic.danis@collabora.com>

In some cases, `cp` doesn't handle symlinks due to the lack of checks,
especially with symlinks pointing to directories. This has been fixed
upstream so we backport the corresponding patches in this commit.

Signed-off-by: Arnaud Ferraris <arnaud.ferraris@collabora.com>

Rather then leaking a boxed value to keep the upstream code working wrap
the unescape string into a cow. This causes a bunch of allocations
to happen if the upper/lower character classes are used but at least
there are no allocations leaked.

Signed-off-by: Sjoerd Simons <sjoerd@collabora.com>

The current implementation of `rust-coreutils` isn't complete yet, and
some of the executables need improvements in order to be able to build a
base Apertis system.

This commit adds the necessary patches to ensure we can use to package
to build Apertis images.

Signed-off-by: Arnaud Ferraris <arnaud.ferraris@collabora.com>

The `revert-twox-hash.dif` patch is no longer needed as a similar change
was merged upstream, which is included in this package as part of the
`sort` backport.

`bump-thread-local` is an empty file causing issues when using `gbp pq`,
and can be safely removed.

Signed-off-by: Arnaud Ferraris <arnaud.ferraris@collabora.com>

The new implementation of `sort` backported from upstream adds a
dependency on the `rayon` crate. This commit adds the corresponding
Debian package as a build-dependency.

Signed-off-by: Arnaud Ferraris <arnaud.ferraris@collabora.com>

The post-installation script of at least one packages makes use of the
`-k` option for `sort`, which isn't implemented in release 0.0.6 of
`rust-coreutils`.

As this has since been implemented upstream, this commit picks the
corresponding patches so we can benefit of those improvements.

Signed-off-by: Arnaud Ferraris <arnaud.ferraris@collabora.com>

`rust-coreutils` provides `hashsum` as an implementation for all `*sum`
executables (md5sum, sha1sum...). As most software expect individual
binaries for each of those, this commit adds symlinks pointing to
`hashsum` for all supported algorithms.

Signed-off-by: Arnaud Ferraris <arnaud.ferraris@collabora.com>

Some of the executables installed by `rust-coreutils` are already
provided by other packages:
- `more` is provided by `util-linux`
- `hostname` is provided by `hostname`
- `kill` and `uptime` are provided by `procps`

Removing those executables from this package solves conflicts.

Signed-off-by: Arnaud Ferraris <arnaud.ferraris@collabora.com>

As we want `rust-coreutils` to be a replacement to `coreutils-gplv2`, we
need to ensure this package gets picked up when boostrapping the system,
and that `coreutils-gplv2` won't be installed at the same time.

This is achieved by:
- adding Conflicts/Breaks/Replaces/Provides relationships identical to
  those of `coreutils-gplv2`
- adding another Conflicts relationship with `coreutils-gplv2`
- make the package priority `required` so it can be pulled by
  `debootstrap`

Signed-off-by: Arnaud Ferraris <arnaud.ferraris@collabora.com>

On Debian, `rust-coreutils` is meant to be installed alongside
`coreutils`, which would cause file conflicts if the manpages had the
same name, hence the need for the `rust-` prefix.

We intend to fully replace `coreutils` with `rust-coreutils` in Apertis,
so this prefix is not necessary nor relevant in our case.

Signed-off-by: Arnaud Ferraris <arnaud.ferraris@collabora.com>

Executables are installed to `/usr/lib/cargo/bin/coreutils` in the
Debian package as this is an experimental package, not meant to replace
`coreutils` yet, contrary to what we want for Apertis.

This commit changes the install path of all executables so they are
placed in `/bin` and `/usr/bin`, and can therefore be used system-wide.

Signed-off-by: Arnaud Ferraris <arnaud.ferraris@collabora.com>

rust-coreutils (0.0.6-1~exp1) experimental; urgency=medium
.
  * New upstream release
.
rust-coreutils (0.0.4-1~exp2) experimental; urgency=medium
.
  * Binaries have been moved in usr/lib/cargo/bin/coreutils
    The rational is that some other rust programs are installed
    in this directory (ex: /usr/lib/cargo/bin/fd). So, users might
    add /usr/lib/cargo/bin/ to their PATH and caused some unexpected
    errors if the Rust coreutils binaries aren't behaving like GNU's.
.
rust-coreutils (0.0.4-1~exp1) experimental; urgency=medium
.
  * New upstream release
  * Rebase of the patches
  * Set a minimal version for platform-info
  * Use PROFILE=release instead of a silly sed
.
rust-coreutils (0.0.3-1~exp2) experimental; urgency=medium
.
  * Set a minimal version for librust-hostname-dev
  * chroot, hashsum, hostname, kill, more, relpath and uptime were
    not installed
  * Add fail missing
.
rust-coreutils (0.0.3-1~exp1) experimental; urgency=medium
.
  * New upstream release
  * Add missing build dependency (librust-cpp-build-dev)
.
rust-coreutils (0.0.2-1~exp1) experimental; urgency=medium
.
  * Package coreutils 0.0.2 from crates.io using debcargo 2.4.4-alpha.0