Debian Bug report logs - #235855
xfree86 suite pre-init scripts bug

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox):

From: Szymon Juraszczyk <szymon@juraszczyk.com>
To: submit@bugs.debian.org
Subject: xfree86 suite pre-init scripts bug
Date: Tue, 02 Mar 2004 21:33:14 +0100

Package: xfree86-common
Version: 4.3.0-3

 Most of the recent packages from xfree86 suite (version 4.3.0-3) have 
broken pre-init scripts. They crash badly if /bin/sh shell is linked to 
dash. Since dash is a POSIX compliant shell, that means, that these 
scripts do not strictly conform to a POSIX Bourne shell standard. After 
linking /bin/sh to /bin/bash, the packages installed successfully.
 As far as I can remember, there was no such problem in 4.3.0-2 version 
or earlier, so the bug must have been introduced in the latest version 
of the packages. Note that I've had /bin/sh linked to dash for some time 
and successfully installed 4.3.0-2 before.
 My suggestion is to either explicitely use /bin/bash as an interpreter 
for pre-init scripts (does the Debian policy allow it?) or make the 
scripts POSIX Bourne shell compliant.
 Below come the errors that occur during the installation. Sorry for 
some Polish messages - the ones of your most intrest are fortunately in 
English. It seems that there's a bracket missing or something.

 Preconfiguring packages ...
/tmp/xfree86-common.config.22201: 610: Syntax error: end of file 
unexpected (expecting ")")
nie udało się skonfigurować xfree86-common, kod wyjścia: 2
/tmp/xserver-common.config.22203: 765: Syntax error: end of file 
unexpected (expecting ")")
nie udało się skonfigurować xserver-common, kod wyjścia: 2
/tmp/xserver-xfree86.config.22205: 1703: Syntax error: end of file 
unexpected (expecting ")")
nie udało się skonfigurować xserver-xfree86, kod wyjścia: 2
(Odczytywanie bazy danych ... 58484 plików i katalogów obecnie 
zainstalowanych.)
Przygotowanie do zastąpienia xfree86-common 4.3.0-2 (wykorzystując 
.../xfree86-common_4.3.0-3_all.deb) ...
/var/lib/dpkg/tmp.ci/preinst: 631: Syntax error: end of file unexpected 
(expecting ")")
dpkg: błąd przetwarzania 
/var/cache/apt/archives/xfree86-common_4.3.0-3_all.deb (--unpack):
podproces pre-installation script zwrócił kod błędu 2
/var/lib/dpkg/tmp.ci/postrm: 618: Syntax error: end of file unexpected 
(expecting ")")
dpkg: błąd podczas czyszczenia środowiska:
podproces post-removal script zwrócił kod błędu 2
Przygotowanie do zastąpienia xlibs-data 4.3.0-2 (wykorzystując 
.../xlibs-data_4.3.0-3_all.deb) ...
/var/lib/dpkg/tmp.ci/preinst: 610: Syntax error: end of file unexpected 
(expecting ")")
dpkg: błąd przetwarzania 
/var/cache/apt/archives/xlibs-data_4.3.0-3_all.deb (--unpack):
podproces pre-installation script zwrócił kod błędu 2
/var/lib/dpkg/tmp.ci/postrm: 610: Syntax error: end of file unexpected 
(expecting ")")
dpkg: błąd podczas czyszczenia środowiska:
podproces post-removal script zwrócił kod błędu 2
Przygotowanie do zastąpienia libx11-6 4.3.0-2 (wykorzystując 
.../libx11-6_4.3.0-3_i386.deb) ...
/var/lib/dpkg/tmp.ci/preinst: 611: Syntax error: end of file unexpected 
(expecting ")")
dpkg: błąd przetwarzania 
/var/cache/apt/archives/libx11-6_4.3.0-3_i386.deb (--unpack):
podproces pre-installation script zwrócił kod błędu 2
/var/lib/dpkg/tmp.ci/postrm: 615: Syntax error: end of file unexpected 
(expecting ")")
dpkg: błąd podczas czyszczenia środowiska:
podproces post-removal script zwrócił kod błędu 2
Przygotowanie do zastąpienia libxt6 4.3.0-2 (wykorzystując 
.../libxt6_4.3.0-3_i386.deb) ...
/var/lib/dpkg/tmp.ci/preinst: 611: Syntax error: end of file unexpected 
(expecting ")")
dpkg: błąd przetwarzania /var/cache/apt/archives/libxt6_4.3.0-3_i386.deb 
(--unpack):
podproces pre-installation script zwrócił kod błędu 2
/var/lib/dpkg/tmp.ci/postrm: 615: Syntax error: end of file unexpected 
(expecting ")")
dpkg: błąd podczas czyszczenia środowiska:
podproces post-removal script zwrócił kod błędu 2
Przygotowanie do zastąpienia xbase-clients 4.3.0-2 (wykorzystując 
.../xbase-clients_4.3.0-3_i386.deb) ...
/var/lib/dpkg/tmp.ci/preinst: 639: Syntax error: end of file unexpected 
(expecting ")")
dpkg: błąd przetwarzania 
/var/cache/apt/archives/xbase-clients_4.3.0-3_i386.deb (--unpack):
podproces pre-installation script zwrócił kod błędu 2
/var/lib/dpkg/tmp.ci/postrm: 623: Syntax error: end of file unexpected 
(expecting ")")
dpkg: błąd podczas czyszczenia środowiska:
podproces post-removal script zwrócił kod błędu 2
Przygotowanie do zastąpienia xserver-common 4.3.0-2 (wykorzystując 
.../xserver-common_4.3.0-3_i386.deb) ...
/var/lib/dpkg/tmp.ci/config: 765: Syntax error: end of file unexpected 
(expecting ")")
dpkg: błąd przetwarzania 
/var/cache/apt/archives/xserver-common_4.3.0-3_i386.deb (--unpack):

-- 
With kind regards,
Szymon Juraszczyk
szymon@juraszczyk.com

Message #22 received at 235855-submitter@bugs.debian.org (full text, mbox):

From: Branden Robinson <branden@debian.org>
To: 235855-submitter@bugs.debian.org, control@bugs.debian.org
Subject: Re: Bug#235855: xfree86 suite pre-init scripts bug
Date: Thu, 4 Mar 2004 22:03:54 -0500

[Message part 1 (text/plain, inline)]

severity 235855 grave
reassign 235855 xfree86
close 235855
merge 235687 235855
thanks

[The following is a form letter.]

Hello,

You recently filed a duplicate bug report against a Debian package; that
is, the problem had already been reported.

While there is often nothing inherently wrong with doing so, the filing of
duplicate reports can cause Debian package maintainers to spend time
performing triage and maintenance operations on bug reports (e.g.,
instructing the Debian Bug Tracking System to merge the duplicates) that
could otherwise be spent resolving problems and doing other work on the
package.

One very good way to file bugs with the Debian Bug Tracking System is to
use the "reportbug" package and command of the same name.  A very nice
feature of reportbug is that, if the machine where you run it has network
access to the World Wide Web, it can query the Debian Bug Tracking System
and show you existing reports.  This reduces the chance that you'll file a
duplicate report, and offers you the option of adding follow-up information
to an existing bug report.  This is especially valuable if you have unique
information to add to an existing report, because this way information
relevant to the problem is gathered together in one place as opposed to
being scattered among multiple, duplicate bug reports where some facts may
be overlooked by the package maintainers.  The reportbug program also does
a lot of automatic information-gathering that helps package maintainers to
understand your system configuration, and also ensures that your message to
the Debian Bug Tracking System is well-formed so that it is processed
correctly by the automated tools that manage the reports.  (If you've ever
gotten a "bounce" message from the Debian Bug Tracking System that tells
you your message couldn't be processed, you might appreciate this latter
feature.)

Therefore, I strongly urge you to give "reportbug" a try as your primary
bug reporting tool for the Debian System.

One way to install reportbug is with "apt-get"; for
example:

  # apt-get install reportbug

The "reportbug" command has a few different modes that cater to different
levels of user expertise.  If this message has contained a lot of jargon
that is unfamiliar to you, you likely want to use reportbug's "novice"
mode; here's one way to do that.

  $ reportbug --mode=novice
  Please enter the name of the package in which you have found a problem,
  or type 'other' to report a more general problem.
  >

If you're more sophisticated, or if you are not using the released version
of Debian ("stable"), but instead Debian "testing" or "unstable", you
should use reportbug's standard mode.

  $ reportbug
  Please enter the name of the package in which you have found a problem,
  or type 'other' to report a more general problem.
  >

The reportbug command is extensively documented in its usage message and
manual page.  Commands to view these pieces of documentation are:

  $ reportbug --help | more
  $ man reportbug

(The output of the above commands has been omitted from this message.)

Thanks for using the Debian system!

-- 
G. Branden Robinson                |      What cause deserves following if
Debian GNU/Linux                   |      its adherents must bury their
branden@debian.org                 |      opposition with lies?
http://people.debian.org/~branden/ |      -- Noel O'Connor

[signature.asc (application/pgp-signature, inline)]

Send a report that this bug log contains spam.