For some reason, javascript-common fails to upgrade, and it also fails
to be reinstalled, which prevents from upgrading dependents.

```
# dpkg --configure --pending
Setting up javascript-common (12) ...
dpkg: error processing package javascript-common (--configure):
  installed javascript-common package post-installation script
subprocess returned error exit status 1
dpkg: dependency problems prevent configuration of dokuwiki:
  dokuwiki depends on javascript-common; however:
   Package javascript-common is not configured yet.

dpkg: error processing package dokuwiki (--configure):
  dependency problems - leaving unconfigured
Errors were encountered while processing:
  javascript-common
  dokuwiki
```

I tried to follow what's inside #718318 but I have no javascript-common
file in /etc/apache2. I don't have lighthttpd, so I removed
/etc/lighttpd (which contained files from javascript-common, see
#912002) and tried to install again:

```
# dpkg -i javascript-common_12_all.deb
(Reading database ... 482559 files and directories currently installed.)
Preparing to unpack javascript-common_12_all.deb ...
Unpacking javascript-common (12) over (12) ...
Setting up javascript-common (12) ...
javascript-alias was disabled in lighttpd.
Hint: Use "lighttpd-enable-mod javascript-alias" to re-enable.
dpkg: error processing package javascript-common (--install):
  installed javascript-common package post-installation script
subprocess returned error exit status 1
Errors were encountered while processing:
  javascript-common
```

As you can see, there's no error message indicating why it fails.

Hi,

AFAICT, the postinst script most likely fails in the automatically added
snippet:

Looking at the apache2-maintscript-helper, could you please run the
following commands and share the output?

Please also check your system logs/journal from the time around you
attempted the upgrade, there might be more messages there.

I wasn't able to reproduce the issue. For me, the javascript-common
installs and re-installs without issue. Thus, I wonder if this should be
considered release-critical or lowered in priority.

Best Regards,
Fiona

Control: close -1
Control: notfound -1 javascript-common/12
Looks to be a false positive.

reopen 1101456
thanks

That's definitely not a false positive. It still fails to upgrade and
thus now no package depending on it (like dokuwiki) can be installed on
my system since javascript-common fails.

The given commands output `No conf matches javascript-common` and `1`.

Also now:

```
# LANG=C dpkg --configure --pending
Setting up javascript-common (12) ...
ln: failed to create symbolic link
'/etc/lighttpd/conf-enabled/90-javascript-alias.conf': File exists
dpkg: error processing package javascript-common (--configure):
  installed javascript-common package post-installation script
subprocess returned error exit status 1
dpkg: dependency problems prevent configuration of dokuwiki:
  dokuwiki depends on javascript-common; however:
   Package javascript-common is not configured yet.

dpkg: error processing package dokuwiki (--configure):
  dependency problems - leaving unconfigured
Errors were encountered while processing:
  javascript-common
  dokuwiki
```

I removed `/etc/lighttpd/conf-enabled/90-javascript-alias.conf` and
rerun the configure:

```
# LANG=C dpkg --configure --pending
Setting up javascript-common (12) ...
dpkg: error processing package javascript-common (--configure):
  installed javascript-common package post-installation script
subprocess returned error exit status 1
dpkg: dependency problems prevent configuration of dokuwiki:
  dokuwiki depends on javascript-common; however:
   Package javascript-common is not configured yet.

dpkg: error processing package dokuwiki (--configure):
  dependency problems - leaving unconfigured
Errors were encountered while processing:
  javascript-common
  dokuwiki
```

Then on next configure, same error as before, file exists.

Hi VA,
[..]

please provide the additional info requested by Fiona:

On Fri, 11 Apr, 2025, Fiona Ebner wrote:
[..]
| AFAICT, the postinst script most likely fails in the automatically added
| snippet:
|
| > # Automatically added by dh_apache2/UNDECLARED
| > if true; then
| > 	if [ -e /usr/share/apache2/apache2-maintscript-helper ] ; then
| > 		. /usr/share/apache2/apache2-maintscript-helper
| > 		for conf in javascript-common  ; do
| > 			apache2_invoke enconf $conf  || exit 1
| > 		done
| > 	fi
| > fi
| > # End automatically added section
|
| Looking at the apache2-maintscript-helper, could you please run the
| following commands and share the output?
|
| > a2query -c javascript-common
| > echo $?
|
| Please also check your system logs/journal from the time around you
| attempted the upgrade, there might be more messages there.
|
| I wasn't able to reproduce the issue. For me, the javascript-common
| installs and re-installs without issue. Thus, I wonder if this should be
| considered release-critical or lowered in priority.


Best,
Chris

Hi Chris,

(Thanks for putting me in CC so I'm notified as I wasn't aware someone
had closed the issue)

Le 27/04/2025 à 15:22, Chris Hofstaedtler a écrit :

I gave it above, but I'll repeat it, a2query prints `No conf matches
javascript-common` and the echo prints `1`.

With plain `journalctl -e` without filter, there weren't any relevant
logs, only usual stuff.

* VA <bugs@indigo.re> [250427 15:46]:

Ah, I didn't understand that.

Could you check a few things please:

a) /etc/apache2/conf-available/javascript-common.conf does NOT
exist?

b) Does the following print anything?
    dpkg -C javascript-common

c) What do the following print?
    dpkg -l javascript-common
    dpkg -L javascript-common


Chris

Here's a scripted reproducer:

     mmdebstrap --variant=apt --chrooted-customize-hook='cd / && apt download javascript-common && dpkg -i ./javascript-common_*.deb && rm /etc/apache2/conf-available/javascript-common.conf && apt install -y apache2 && dpkg -i ./javascript-common_*.deb' stable /dev/null

I'll note this already happens with the version in stable.

Raising severity to serious, as per my understanding of the policy,
removing a conffile is a supported action, and maintainer scripts
must not fail in this case.

A workaround should be:
     dpkg -i --reinstall ./javascript-common_*.deb
(Which should restore the missing conffiles.)

Chris

Le 27/04/2025 à 16:32, Chris Hofstaedtler a écrit :

indeed. I don't remember ever touching this file.

```
The following packages are only half configured, probably due to problems
configuring them the first time.  The configuration should be retried using
dpkg --configure <package> or the configure menu option in dselect:
  javascript-common    Base support for JavaScript library packages
```

```
Desired=Unknown/Install/Remove/Purge/Hold
|
Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name              Version      Architecture Description
+++-=================-============-============-============================================
iF  javascript-common 12           all          Base support for
JavaScript library packages
```

```
/.
/etc
/etc/apache2
/etc/apache2/conf-available
/etc/apache2/conf-available/javascript-common.conf
/etc/lighttpd
/etc/lighttpd/conf-available
/etc/lighttpd/conf-available/90-javascript-alias.conf
/usr
/usr/share
/usr/share/doc
/usr/share/doc/javascript-common
/usr/share/doc/javascript-common/README.Debian
/usr/share/doc/javascript-common/changelog.gz
/usr/share/doc/javascript-common/copyright
/usr/share/javascript
/usr/share/lintian
/usr/share/lintian/overrides
/usr/share/lintian/overrides/javascript-common
```

That file is the core part of the package. I wonder what it is supposed
to do if that is missing?

/etc/apache2/conf-available/javascript-common.conf

Without this file, the package becomes useless (if using apache2). Does
it really make sense to ignore this missing conf file in maintscripts?

This looks to me like a user error.

Dear maintainer,

I've prepared an NMU for javascript-common (versioned as 12+nmu1). The diff
is attached to this message.

Chris

Le 03/05/2025 à 16:22, Pirate Praveen a écrit :

If that file is really mandatory, maybe installing the package should
create/recreate it then? If not, what package is supposed to create the
file?
In the current state, the package can't even be reinstalled because the
file is not created by the package but the script depends on it. Can't
see the logic here.

We believe that the bug you reported is fixed in the latest version of
javascript-common, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1101456@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Chris Hofstaedtler <zeha@debian.org> (supplier of updated javascript-common package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)
Format: 1.8
Date: Sat, 03 May 2025 14:12:36 +0200
Source: javascript-common
Architecture: source
Version: 12+nmu1
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers <pkg-javascript-devel@lists.alioth.debian.org>
Changed-By: Chris Hofstaedtler <zeha@debian.org>
Closes: 1101456
Changes:
 javascript-common (12+nmu1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Make dh_apache2 failures in postinst/preinst non-fatal.
     (Closes: #1101456)
   * Correct postinst to use cat instead of echo with multiline
     mesage.
Checksums-Sha1:
 e869072afb7c40233248e9e6f76d13919bca89d6 1699 javascript-common_12+nmu1.dsc
 610ae36a4c93c7f8fb7f59607859c8e7bc8ca7d1 5960 javascript-common_12+nmu1.tar.xz
 9f60a31dd91d51a2b5d26df8eef29a461fcccca4 6381 javascript-common_12+nmu1_arm64.buildinfo
Checksums-Sha256:
 cf84d81b7aedbef879ee8173418236326c7b29f8a8cf012aa73db82e8f01234d 1699 javascript-common_12+nmu1.dsc
 8bbe48c3555d1141169fd7d56f6ff568318a8f29ee7deca5c75f16691cf9fff9 5960 javascript-common_12+nmu1.tar.xz
 b12a8b26c46b9c616bc9fee79fdbff5d516441cdc77569b05b24216e3fc0165b 6381 javascript-common_12+nmu1_arm64.buildinfo
Files:
 603f948367b70b4f992470acd7dfd0f0 1699 web optional javascript-common_12+nmu1.dsc
 44a3d5b00336711f248297f6e137a395 5960 web optional javascript-common_12+nmu1.tar.xz
 2fae6dc260e059aca338f666a2a32254 6381 web optional javascript-common_12+nmu1_arm64.buildinfo
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEfRrP+tnggGycTNOSXBPW25MFLgMFAmgWKA4ACgkQXBPW25MF
LgOehRAAoQBxNC8iw/WaqzSgiLVg/TujXM6uFtdYuka+BrdN6J/+FCVOz5EXFzjR
XzmABfDRstuvr632Ibw/lEtSHsgThkgIpHq2ZJEmkZ8qd8Zd5+Wmuu26fWMA9cdt
xTnAv1CysnMpjT8A3kqizR1LcDsYdOWLEJ+uQWP/8x8XpguBWW2nWtVKMUZmG5xB
dAfGNrUD1KIZJ7fAQI0oFudzrtGWIXbe3mMQBa0VWH+UZGxw0YtTBRfPcUEAEpEW
DwHNqtxpW6MkQENlltBabEM0Ee1XjOpZwUyRoJYfSs36BeTxV2Lff3PyT8A8X+xe
wD5/7wEVOtQTmxZoNLawvcqQ8z+xTo/fzokU8CWdmHlFU3zQNqyz9mB9uCjvCNRZ
oJIOHeglMmL4hNQkHlJGIkn1odqV/Ff/Xi6KhFRQNbyEAI3Ezz1T1H6ITeWx8m3t
7n/Y4DPdCS8h+LmgbFhJX6r9jOMiXPv0lHsr0EbPFYjbIsQteGXtIZ+gnaqURRdd
KrUjffzyZwbVmPItKWIfKSZi/exSXUetjkaIGpV9pB6IGwsHk79MBCd5mcHvKq++
CF8Czm1qODMbPieWx8wVeg4DW+UiVmCYgXa3/JwXCtlIVsK8eXMy5GUcCU/qmH6g
moyxrUekhprnr6h+6i4LT6SklwftiPeDTXStzPx0I/pdzwhe0lI=
=mKk9
-----END PGP SIGNATURE-----

It looks like that file was manually removed. Then the logical action
would be just reinstall it so that file is restored.

Did you try apt reinstall javascript-common ?

Le 03/05/2025 à 16:52, Pirate Praveen a écrit :

```
# aptitude reinstall javascript-common
The following packages will be REINSTALLED:
   javascript-common
0 packages upgraded, 0 newly installed, 1 reinstalled, 0 to remove and
277 not upgraded.
Need to get 0 B of archives. After unpacking 0 B will be used.
E: Internal Error, No file name for javascript-common:amd64

```