Your message dated Fri, 11 Aug 2017 12:44:51 -0700 with message-id <87o9rlx51o.fsf@iris.silentflame.com> and subject line Closing inactive Policy bugs has caused the Debian Bug report #490605, regarding debian-policy: please discourage the usage of echo -n, and echo in general to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@bugs.debian.org immediately.) -- 490605: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=490605 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: submit@bugs.debian.org
- Subject: debian-policy: please discourage the usage of echo -n, and echo in general
- From: Raphael Geissert <atomo64@gmail.com>
- Date: Sat, 12 Jul 2008 20:41:40 -0500
- Message-id: <200807122041.45259.atomo64@gmail.com>
Package: debian-policy Version: 3.0.8.1 Severity: wishlist As demonstrated by the following trivia[1], and also mentioned by SUSv3, the echo built-in varies from implementation to implementation and thus should be discouraged. 8<---trivia-starts-here--->8 $ ./echo-trivia.sh ++ bash + o='Foo:\n\tI do not like bar!!\n\nBar:\n\tI do not like you either' + set +x ++ dash + o='Foo: I do not like bar!! Bar: I do not like you either' + set +x ++ ksh + o='Foo:\n\tI do not like bar!!\n\nBar:\n\tI do not like you either' + set +x ++ zsh + o='Foo: I do not like bar!! Bar: I do not like you either' + set +x ++ posh + o='Foo: I do not like bar!! Bar: I do not like you either' + set +x ++ pdksh + o='Foo: I do not like bar!! Bar: I do not like you either' + set +x ++ mksh + o='Foo: I do not like bar!! Bar: I do not like you either' + set +x ++ busybox sh + o='Foo:\n\tI do not like bar!!\n\nBar:\n\tI do not like you either' + set +x ==Trivia results== Shells tested: 8 Shells expandind backslashes: 5 /bin/echo does NOT expand 8<---trivia-ends-here--->8 Additionally, the usage of echo -n should also be discouraged because it may not help stressing the idea of echo not being portable. Finally, completely OT but I don't believe it warrants yet another bug report, the following line should also mention the [ built-in and not just test: > test, if implemented as a shell built-in, must support -a and -o as binary > logical operators. [1] The script basically prints some text with 'echo' which containing backslashes and checks whether the backslashes were expanded or not. Kind regards, -- Atomo64 - Raphael Please avoid sending me Word, PowerPoint or Excel attachments. See http://www.gnu.org/philosophy/no-word-attachments.htmlAttachment: signature.asc
Description: This is a digitally signed message part.
--- End Message ---
--- Begin Message ---
- To: 617938-close@bugs.debian.org, 688363-close@bugs.debian.org, 821363-close@bugs.debian.org, 192571-close@bugs.debian.org, 215549-close@bugs.debian.org, 263448-close@bugs.debian.org, 276160-close@bugs.debian.org, 408500-close@bugs.debian.org, 562863-close@bugs.debian.org, 587377-close@bugs.debian.org, 592564-close@bugs.debian.org, 656569-close@bugs.debian.org, 663917-close@bugs.debian.org, 683570-close@bugs.debian.org, 684673-close@bugs.debian.org, 697134-close@bugs.debian.org, 704233-close@bugs.debian.org, 727754-close@bugs.debian.org, 737559-close@bugs.debian.org, 795783-close@bugs.debian.org, 832654-close@bugs.debian.org, 71621-close@bugs.debian.org, 120418-close@bugs.debian.org, 267142-close@bugs.debian.org, 291631-close@bugs.debian.org, 338219-close@bugs.debian.org, 375502-close@bugs.debian.org, 391240-close@bugs.debian.org, 397939-close@bugs.debian.org, 400112-close@bugs.debian.org, 412668-close@bugs.debian.org, 431109-close@bugs.debian.org, 457364-close@bugs.debian.org, 458824-close@bugs.debian.org, 462996-close@bugs.debian.org, 465140-close@bugs.debian.org, 466550-close@bugs.debian.org, 485559-close@bugs.debian.org, 491055-close@bugs.debian.org, 492144-close@bugs.debian.org, 521810-close@bugs.debian.org, 525843-close@bugs.debian.org, 528453-close@bugs.debian.org, 535577-close@bugs.debian.org, 541872-close@bugs.debian.org, 543417-close@bugs.debian.org, 549910-close@bugs.debian.org, 554194-close@bugs.debian.org, 570141-close@bugs.debian.org, 572571-close@bugs.debian.org, 580135-close@bugs.debian.org, 593177-close@bugs.debian.org, 610298-close@bugs.debian.org, 633994-close@bugs.debian.org, 660705-close@bugs.debian.org, 642914-close@bugs.debian.org, 663762-close@bugs.debian.org, 671503-close@bugs.debian.org, 681289-close@bugs.debian.org, 685992-close@bugs.debian.org, 690495-close@bugs.debian.org, 694384-close@bugs.debian.org, 775318-close@bugs.debian.org, 798714-close@bugs.debian.org, 524461-close@bugs.debian.org, 555981-close@bugs.debian.org, 682282-close@bugs.debian.org, 686143-close@bugs.debian.org, 515837-close@bugs.debian.org, 779506-close@bugs.debian.org, 628174-close@bugs.debian.org, 661417-close@bugs.debian.org, 681562-close@bugs.debian.org, 490605-close@bugs.debian.org, 647570-close@bugs.debian.org
- Subject: Closing inactive Policy bugs
- From: Sean Whitton <spwhitton@spwhitton.name>
- Date: Fri, 11 Aug 2017 12:44:51 -0700
- Message-id: <87o9rlx51o.fsf@iris.silentflame.com>
control: user debian-policy@packages.debian.org control: usertag -1 +obsolete control: tag -1 +wontfix Russ Allbery and I did a round of in-person bug triage at DebConf17 and we are closing this bug as inactive. The reasons for closing fall into the following categories, from most frequent to least frequent: - issue is appropriate for Policy, there is a consensus on how to fix the problem, but preparing the patch is very time-consuming and no-one has volunteered to do it, and we do not judge the issue to be important enough to keep an open bug around; - issue is appropriate for Policy but there does not yet exist a consensus on what should change, and no recent discussion. A fresh discussion might allow us to reach consensus, and the messages in the old bug are unlikely to help very much; or - issue is not appropriate for Policy. If you feel this bug is still relevant and want to restart the discussion, you can re-open the bug. However, please consider instead opening a new bug with a message that summarises and condenses the previous discussion, updates the report for the current state of Debian, and makes clear exactly what you think should change. A lot of these old bugs have long side tangents and numerous messages, and that old discussion is not necessarily helpful for figuring out what Debian Policy should say today. -- Sean WhittonAttachment: signature.asc
Description: PGP signature
--- End Message ---