Here is a proposition of testsuite introduction with
https://gitlab.com/OldManProgrammer/unix-tree/-/merge_requests/19/diffs
** Patch added: "Debdiff"
https://bugs.launchpad.net/ubuntu/+source/tree/+bug/2056099/+attachment/5760629/+files/add_tree_testsuite.debdiff
--
You received this bug
** Also affects: chrony (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2032805
Title:
Could not open socket /var/run/timemaster/chrony.SOCK0
To
Github issue related to this MIR: https://github.com/canonical/ubuntu-
mir/issues/52
** Bug watch added: github.com/canonical/ubuntu-mir/issues #52
https://github.com/canonical/ubuntu-mir/issues/52
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
[MIR] tree
[Availability]
The package tree is already in Ubuntu universe.
Tree is a general purpose utility that is built and works on all Ubuntu
architectures.
Link to package https://launchpad.net/ubuntu/+source/tree
[Rationale]
The package tree is generally useful for a
Thank you Sudip.
I cannot reproduce on tree package version 2.1.1-2 under Noble.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1516441
Title:
*** buffer overflow detected ***: tree terminated
To
** Description changed:
Hello,
I was trying to run lintian on some deb packages an run onto some errors
messages from groff.
Steps to reproduce:
1. Setup a LXD container with mantic or Noble:
lxc launch ubuntu-daily:noble #or lxc launch ubuntu:mantic
- 2. Install
** Description changed:
Hello,
I was trying to run lintian on some deb packages an run onto some errors
messages from groff.
Steps to reproduce:
1. Setup a LXD container with mantic or Noble:
lxc launch ubuntu-daily:noble #or lxc launch ubuntu:mantic
2. Install
Hello bananenkasper,
There was some updates of tree since you reported this issue. Moreover,
some fix were about buffer overflow (specifically in v1.7.0 and v2.1.1).
Nowadays 2.1.1 is on noble so please, try to reproduce you issue with an
up to date version.
I couldn't reproduce you issue on my
