Bug 2094897 - please bump tree to 2.0.2
Summary: please bump tree to 2.0.2
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: tree-pkg
Version: 36
Hardware: x86_64
OS: Linux
unspecified
low
Target Milestone: ---
Assignee: Kamil Dudka
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-06-08 14:53 UTC by Boris Petersen
Modified: 2022-06-15 01:30 UTC (History)
1 user (show)

Fixed In Version: tree-pkg-2.0.2-1.fc37 tree-pkg-2.0.2-1.fc36
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-06-15 01:30:20 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Boris Petersen 2022-06-08 14:53:22 UTC
Description of problem:
tree 2.0.1 has a known bug which leads to no output at all. it is fixed in 2.0.2. excerpt from the changelog of 2.0.2:

  - Okay, apparently the stddata addition is causing havoc (who knew how many
    scripts just haphazardly hand programs random file descriptors, that's
    surely not a problem.)  Going forward the stddata option will only work
    if the environment variable STDDATA_FD is present or set to the descriptor
    to produce the JSON output on.


Version-Release number of selected component (if applicable):
tree-2.0.1-2.fc36.x86_64

How reproducible:
always


Steps to Reproduce:
1. run "tree"
2.
3.

Actual results:
nothing

Expected results:
see a tree view of the current directory

Additional info:

Comment 1 Boris Petersen 2022-06-08 15:20:21 UTC
a bit more context. it's reproducible in at least bash and zsh:

$ ls -la
total 40
drwxr-xr-x.   2 boris.petersen boris.petersen  4096 Jun  8 17:16 .
drwx------. 148 boris.petersen boris.petersen 32768 Jun  8 17:16 ..
-rw-r--r--.   1 boris.petersen boris.petersen     0 Jun  8 17:16 test

$ tree

$ echo $?
141

$ strace -e trace=write -s 2048 tree
write(3, "[{\"type\":\"directory\",\"name\":\".\",\"contents\":[{\"type\":\"file\",\"name\":\"test\"}]},{\"type\":\"report\",\"directories\":0,\"files\":1}]\n", 121) = -1 EPIPE (Broken pipe)
--- SIGPIPE {si_signo=SIGPIPE, si_code=SI_USER, si_pid=85748, si_uid=1000} ---
+++ killed by SIGPIPE +++

$ tree 3>&1
[{"type":"directory","name":".","contents":[{"type":"file","name":"test"}]},{"type":"report","directories":0,"files":1}]

Comment 2 Kamil Dudka 2022-06-09 06:40:05 UTC
Thank you for letting me know!  I did not know there was a new upstream release.

Comment 4 Fedora Update System 2022-06-09 07:12:38 UTC
FEDORA-2022-b6ccb28c57 has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-b6ccb28c57

Comment 5 Fedora Update System 2022-06-09 14:37:39 UTC
FEDORA-2022-b6ccb28c57 has been pushed to the Fedora 36 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-b6ccb28c57`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-b6ccb28c57

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 6 Boris Petersen 2022-06-10 07:21:55 UTC
I don't have a fedora account but I can confirm the update fixed my issue. Thanks :)

Comment 7 Kamil Dudka 2022-06-10 08:13:45 UTC
Thank you for testing the update!

Comment 8 Fedora Update System 2022-06-15 01:30:20 UTC
FEDORA-2022-b6ccb28c57 has been pushed to the Fedora 36 stable repository.
If problem still persists, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.