** Changed in: midori (Debian)
Status: Won't Fix = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/674365
Title:
Midori useragent does not specify full operating system
To manage
Generally, this type of fix should be made upstream. In the case of
Epiphany, we already had a diff with Debian, with Midori we don't and I
don't think this is worth introducing one. In addition, for Epiphany,
the change existed and was accidentally dropped. It does not seem like
Midori ever
Browser useragents really should be generated on first run or at install
time using $ cat /etc/issue
Altering a package just to fix a useragent is the wrong way to go about
it entirely, but it's the way everyone has been doing it for a long,
long time.
If it would please everyone, I would gladly
Thank you for the update. Bug records should be around as long as
Launchpad is, which we hope is a very long time. :) Marking Won't Fix
for the time being. If Debian ends up including this in the future, I'm
happy to fix it for Ubuntu as well. Please report any other issues you
may find.
**
** Changed in: midori (Debian)
Status: Unknown = Won't Fix
--
Midori useragent does not specify full operating system
https://bugs.launchpad.net/bugs/674365
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
** Bug watch added: Debian Bug tracker #510860
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=510860
** Also affects: midori (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=510860
Importance: Unknown
Status: Unknown
--
Midori useragent does not specify full
Thank you for reporting this to Ubuntu. I linked a Debian report with a
similar request. I don't believe we should carry a diff from Debian just for
this, but if you can answer the Debian maintainer's request, then Debian might
be willing to include it as well. The request is:
If you can
Epiphany identified as Debian until a few months ago, and I filed a bug
against that, which Canonical fixed.
As long as somebody within Canonical has been made aware of the bug,
which given the long list of notified persons I think is probable,
nothing else needs to be done by either you nor me.
