16.04.3 LTS bug in dwww (1.13.1)

Asked by William G Berry

I run ubuntu 16.04 LTS on a home server, which I also use to serve documentation via a modified apache2 config, using dwww. There is a bug in the version available in LTS (1.13.1), which has been fixed upstream. ("Last modified" instead of "Last-modified") Why is the broken version still available in the xenial repositories? Must I update from LTS in order to get the fixed version? 1.13.3 (the fixed version) is available in debian stable, so why not in ubuntu 16.04??

Until it is, what patch do I need to apply to correct the error? Which file needs modifying?

Revision history for this message
Manfred Hampl (m-hampl) said :
#1

There is already a bug report.
Click the "affects me" button on the bug to confirm it, and the developers should start working on it.

Revision history for this message
William G Berry (wortle) said :
#2

Thank you. I know the bug has been fixed in Debian, and the fixed
version is available in Ubuntu 17.10, so why can it not be backported to
16.04 LTS? I appear to have 2 choices:

1. Abandon LTS and upgrade to 17.10;

2. Manually edit the faulty file in my installation (which file?)

I run LTS because it is on a server, and I want it stable. The "S"
stands for "Support", which is surely a misnomer if a known bug is still
in the repos after a fix has been issued upstream? LTS is supposed to be
stable, but in this instance the "bleeding edge" works better than the
"stable"! That surely cannot be right?

On 20/12/17 21:32, Manfred Hampl wrote:
> Your question #662018 on dwww in Ubuntu changed:
> https://answers.launchpad.net/ubuntu/+source/dwww/+question/662018
>
> Status: Open => Answered
>
> Manfred Hampl proposed the following answer:
> There is already a bug report.
> Click the "affects me" button on the bug to confirm it, and the developers should start working on it.
>

Revision history for this message
William G Berry (wortle) said :
#3

I have found which file (dwww-convert) and made the edit myself. Now it
works.

I still think that the faulty 1.13.1 should be replaced in the repos for
LTS with 1.13.3.

Bug closed for me, but probably not yet for other users of LTS.

Revision history for this message
Manfred Hampl (m-hampl) said :
#4

The status of Bug #1702660 for dwww on Ubuntu is still only "new".
Why don't you click "affects me too" on the bug report?
Confirming the bug by a second person is a required step in bug handling.

Revision history for this message
rb.eng (rb-engch) said :
#5

Ran into this issue on 16.04.5 with dwww 1.13.1 (which is still in the repositories as of 2018_0828).

It's a frustrating bug given the simple fix. My solution was to

edit the file /usr/sbin/dwww-convert
     at line 330 which reads in part:
                        print "Last modified: " . gmtime($mtime) . "\n";
    corrected to read instead:
                       print "Last-modified: " . gmtime($mtime) . "\n";

note the missing hyphen between Last and modified. That little correction was the sauce.
Files in the "/usr/share/doc folders" now link to the correct pages.

Would have been great to come upon the answer here (in parts by William G. Berry) before my file dive search.

Please bump the update for 1.13.3

Revision history for this message
William G Berry (wortle) said :
#6

It is disappointing that the defective version 1.13.1 is STILL in the repos for 16.04 LTS. How difficult would it be to replace 1.13.1 with 1.13.3, the fixed version, in 16.04? 16.04 is clearly NOT supported, if a known bug, fixed upstream, is allowed to remain! Can someone please explain why nothing has been done? This post from rb.eng clearly shows that users are still experiencing problems with this bug. How many users, finding this bug and not knowing how to fix it, simply give up on Ubuntu?

This problem is STILL NOT SOLVED, and won't be until 1.13.1 is replaced in the 16.04 repos by 1.13.3. IS anyone maintaining dww in 16.04 LTS?

Can you help with this problem?

Provide an answer of your own, or ask William G Berry for more information if necessary.

To post a message you must log in.