'prt-get diff --all' cuts off separators if long name of port #1

New Issue

FeodorPetrov · 2024-05-08T21:34:38+02:00

FeodorPetrov commented

2024-05-08 21:34:38 +02:00

When listing 'prt-get diff --all' it deletes whitespaces if there is a long name of a port.

For example:

# prt-get diff --all
Differences between installed packages and ports tree:
Port                Installed           Available in the ports tree

...
spirv-llvm-translator17.0.0-1            18.1.0-2            locked
...

When listing 'prt-get diff --all' it deletes whitespaces if there is a long name of a port. For example: ``` # prt-get diff --all Differences between installed packages and ports tree: Port Installed Available in the ports tree ... spirv-llvm-translator17.0.0-1 18.1.0-2 locked ... ```

farkuhar commented

2024-09-14 14:15:05 +02:00

I tried to reproduce the missing whitespace with my fork of prt-get, and here's what I saw:

# prt-get diff --all
Differences between installed packages and ports tree:

Port                Installed           Available in the ports tree

cmake               3.30.2-1            3.30.3-1
curl                8.9.1-1             8.10.0-1
libdevmapper        1.02.199-1          1.02.200-1
...
python3-backports_entry-points-selectable 1.2.0-1             1.3.0-2
...

It looks like my fork (master branch) is preserving the whitespace (although not the column alignment). I haven't bothered to dig deeper to find the specific commit where the behaviour changed. Any experts in the use of git-bisect are welcome to search, so we can merge a clean patch for this specific bug.

I tried to reproduce the missing whitespace with my fork of prt-get, and here's what I saw: ``` # prt-get diff --all Differences between installed packages and ports tree: Port Installed Available in the ports tree cmake 3.30.2-1 3.30.3-1 curl 8.9.1-1 8.10.0-1 libdevmapper 1.02.199-1 1.02.200-1 ... python3-backports_entry-points-selectable 1.2.0-1 1.3.0-2 ... ``` It looks like my fork (master branch) is preserving the whitespace (although not the column alignment). I haven't bothered to dig deeper to find the specific commit where the behaviour changed. Any experts in the use of `git-bisect` are welcome to search, so we can merge a clean patch for this specific bug.

Sign in to join this conversation.

2 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: tools/prt-get#1