Rawhide (rh) lets you search for files on the command line using expressions and user-defined functions in a mini-language inspired by C. It’s like find(1), but more fun to use. Search criteria can be very readable and self-explanatory and/or very concise and typeable, and you can create your own lexicon of search terms. The output can include lots of detail, like ls(1).

Rawhide (rh) searches the filesystem, starting at each given path, for files that make the given search criteria expression true. If no search paths are given, the current working directory is searched.
The search criteria expression can come from the command line (with the -e option), from a file (with the -f option), or from standard input (stdin) (with -f-). If there is no explicit -e option expression, rh looks for an implicit expression among any remaining command line arguments. If no expression is specified, the default search criteria is the expression 1, which matches all filesystem entries.
An rh expression is a C-like expression that can call user-defined functions.
These expressions can contain all of C’s conditional, logical, relational, equality, arithmetic, and bit operators.

gstreamer1.0-pipewire
libkpipewire5
libkpipewiredmabuf5
libkpipewirerecord5
libpipewire-0.3-0
libpipewire-0.3-common
libpipewire-0.3-modules
libpipewire-0.3-modules-x11
pipewire
pipewire-alsa
pipewire-audio
pipewire-bin
pipewire-jack
pipewire-pulse
pipewire-v4l2
qml-module-org-kde-pipewire
vlc-plugin-pipewire

[E][19002.128612] mod.protocol-native | [module-protocol-:  716 init_socket_name()] server 0x6216eb1f3870: name pipewire-0 is not an absolute path and no runtime dir found. Set one of PIPEWIRE_RUNTIME_DIR, XDG_RUNTIME_DIR or USERPROFILE in the environment
[E][19002.128803] pw.conf      | [          conf.c:  573 load_module()] 0x6216eb1cb650: could not load mandatory module "libpipewire-module-protocol-native": No such file or directory
[E][19002.128990] default      | [      pipewire.c:  105 main()] failed to create context: No such file or directory

aclocal: warning: couldn't open directory 'm4': No such file or directory
/usr/bin/libtoolize: 1: /bin/sed: not found
/usr/bin/libtoolize: 1: /bin/sed: not found
/usr/bin/libtoolize: 1: /bin/grep: not found
/usr/bin/libtoolize: 1: /bin/sed: not found
/usr/bin/libtoolize: 1: /bin/sed: not found
: putting auxiliary files in '.'.
: copying file './ltmain.sh'
/usr/bin/libtoolize: 1: /bin/sed: not found

Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
2 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n]
Setting up cpio (2.15+dfsg-1) ...
update-alternatives: error: alternative path /bin/mt-gnu doesn't exist
dpkg: error processing package cpio (--configure):
 installed cpio package post-installation script subprocess returned error exit status 2
Setting up nano (7.2-2) ...
update-alternatives: error: alternative path /bin/nano doesn't exist
dpkg: error processing package nano (--configure):
 installed nano package post-installation script subprocess returned error exit status 2
Errors were encountered while processing:
 cpio
 nano
E: Sub-process /usr/bin/dpkg returned an error code (1)

git-replay - EXPERIMENTAL: Replay commits on a new base, works with bare repos too


SYNOPSIS
--------
(EXPERIMENTAL!) 'git replay' ([--contained] --onto <newbase> | --advance <branch>) <revision-range>...

DESCRIPTION
-----------

Takes ranges of commits and replays them onto a new location. Leaves
the working tree and the index untouched, and updates no references.
The output of this command is meant to be used as input to
`git update-ref --stdin`, which would update the relevant branches
(see the OUTPUT section below).

THIS COMMAND IS EXPERIMENTAL. THE BEHAVIOR MAY CHANGE.

OPTIONS
-------

--onto <newbase>
    Starting point at which to create the new commits.  May be any
    valid commit, and not just an existing branch name.

When `--onto` is specified, the update-ref command(s) in the output will
update the branch(es) in the revision range to point at the new
commits, similar to the way how `git rebase --update-refs` updates
multiple branches in the affected range.

--advance <branch>
    Starting point at which to create the new commits; must be a
    branch name.

When `--advance` is specified, the update-ref command(s) in the output
will update the branch passed as an argument to `--advance` to point at
the new commits (in other words, this mimics a cherry-pick operation).

<revision-range>
    Range of commits to replay. More than one <revision-range> can
    be passed, but in `--advance <branch>` mode, they should have
    a single tip, so that it's clear where <branch> should point
    to. See "Specifying Ranges" in git-rev-parse and the
    "Commit Limiting" options below.

OUTPUT
------

When there are no conflicts, the output of this command is usable as
input to `git update-ref --stdin`.  It is of the form:

    update refs/heads/branch1 ${NEW_branch1_HASH} ${OLD_branch1_HASH}
    update refs/heads/branch2 ${NEW_branch2_HASH} ${OLD_branch2_HASH}
    update refs/heads/branch3 ${NEW_branch3_HASH} ${OLD_branch3_HASH}

where the number of refs updated depends on the arguments passed and
the shape of the history being replayed.  When using `--advance`, the
number of refs updated is always one, but for `--onto`, it can be one
or more (rebasing multiple branches simultaneously is supported).

echo "Hello!"

Package: bfs
Version: 3.0.4-1
Priority: optional
Section: utils
Maintainer: Chris Lamb <lamby@debian.org>
Installed-Size: 321 kB
Depends: libacl1 (>= 2.2.23), libc6 (>= 2.34), libcap2 (>= 1:2.10), libonig5 (>= 6.8.1)