1. Forum
  2. Usenet
  3. LINUX.DEBIAN.BUGS.DIST

  • Bug#1101456: not false positive

    From VA@21:1/5 to All on Sun Apr 27 15:00:01 2025
    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.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Chris Hofstaedtler@21:1/5 to Fiona Ebner on Sun Apr 27 15:30:01 2025
    Control: found -1 javascript-common/12

    Hi VA,

    On Sun, Apr 27, 2025 at 02:50:17PM +0200, VA wrote:
    The given commands output `No conf matches javascript-common` and `1`.
    [..]

    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

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Chris Hofstaedtler@21:1/5 to All on Sun Apr 27 16:40:02 2025
    * VA <bugs@indigo.re> [250427 15:46]:
    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 :
    | > a2query -c javascript-common
    | > echo $?

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

    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

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Chris Hofstaedtler@21:1/5 to All on Sun Apr 27 17:40:01 2025
    Control: found -1 javascript-common/11+nmu1
    Control: tags -1 = confirmed
    Control: severity -1 serious

    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

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From VA@21:1/5 to All on Sun Apr 27 18:00:01 2025
    Le 27/04/2025 à 16:32, Chris Hofstaedtler a écrit :
    a) /etc/apache2/conf-available/javascript-common.conf does NOT exist?

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

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

    ```
    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
    ```

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

    ```
    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
    ```

       dpkg -L javascript-common

    ```
    /.
    /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
    ```

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From VA@21:1/5 to All on Sat May 3 16:50:02 2025
    Le 03/05/2025 à 16:22, Pirate Praveen a écrit :
    On Sun, 27 Apr 2025 17:29:03 +0200 Chris Hofstaedtler <zeha@debian.org> wrote:
    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.)
    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.

    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.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From VA@21:1/5 to All on Sat May 3 19:00:01 2025
    Le 03/05/2025 à 16:52, Pirate Praveen a écrit :
    Did you try apt reinstall javascript-common ?

    Yes I already did, but for reference:

    ```
    # 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

    ```

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)