Actually, a specific example would be useful and constructive information.
Your comment is neither.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mawk in Ubuntu.
https://bugs.launchpad.net/bugs/1074404
Title:
Segfault with mawk
To
Because mawk is not POSIX compliant, cannot be updated safely without
great risk of breaking things.
** Changed in: mawk (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mawk in Ubuntu.
https:
** Changed in: mawk (Debian)
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mawk in Ubuntu.
https://bugs.launchpad.net/bugs/1074404
Title:
Segfault with mawk
To manage notifications about this bug go t
ApportVersion: 2.19.1-0ubuntu3
Architecture: amd64
CasperVersion: 1.365
CurrentDesktop: Unity
Dependencies:
gcc-5-base 5.2.1-22ubuntu2
libc6 2.21-0ubuntu4
libgcc1 1:5.2.1-22ubuntu2
DistroRelease: Ubuntu 15.10
LiveMediaBuild: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
Package: mawk 1
mawk in Ubuntu and Debian is 18 years, see LP bug #1332114
I think this bug should be marked as duplicate of bug #1332114
Many bugs of Mawk are fixed in a new upstream versions 1.3.4-2010-2015,
but the Debian maintainer does not want to update for an obscure reason.
We need to push here: h