Sync yaws 1.87-1 (universe) from Debian testing (main)

Bug #540583 reported by Charlie_Smotherman
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
yaws (Ubuntu)
Fix Released
Wishlist
Unassigned

Bug Description

Please sync yaws 1.87-1 (universe) from Debian testing (main)
According to http://people.ubuntuwire.org/~lucas/ubuntu-nbs/32/yaws_1.84-2_llucid32.buildlog
yaws FTBFS. This sync will correct the FTBFS
Changelog entries since current lucid version 1.84-2:

yaws (1.87-1) unstable; urgency=low

  * New upstream release.
  * Moved Yaws binaries to /usr/lib/yaws directory to follow upstream closer
    and to make sure that private Yaws modules don't clash with any other
    application. The drawback is that now one has to add -pa /usr/lib/yaws/ebin
    to the command line if he wants to use Yaws in embedded mode.
  * Split out yaws-doc package which contains documentation in PDF and
    examples.
  * Added README.Debian in which clarified how to change epam permissions in
    case when it has to be suid or sgid binary.
  * Don't create /var/run/yaws in Yaws init script because this directory is
    no longer used. Also, change working dir to /var/cache/yaws before starting
    the daemon because Erlang issues warnings about inaccessible modules if
    the current dir isn't readable by yaws user.
  * Fixed a few spelling errors in manpages.

 -- Sergei Golovan <email address hidden> Fri, 15 Jan 2010 23:41:06 +0300

yaws (1.86-2) unstable; urgency=low

  * Renamed \ifpdf macro to \ifpdfoutput in yaws.tex documentation file because
    it clashes with ifpdf package which is sourced by geometry package in
    TeXLive 2009 (closes: #560759).
  * Added texlive-font-utils to build dependencies because epstopdf script has
    been moved to it from texlive-extra-utils in TeXLive 2009.

 -- Sergei Golovan <email address hidden> Sat, 12 Dec 2009 19:19:32 +0300

yaws (1.86-1) unstable; urgency=low

  * New upstream release.

 -- Sergei Golovan <email address hidden> Fri, 11 Dec 2009 19:37:09 +0300

yaws (1.85-1) unstable; urgency=low

  * New upstream release.

 -- Sergei Golovan <email address hidden> Fri, 30 Oct 2009 22:36:02 +0300

Revision history for this message
Charlie_Smotherman (cjsmo) wrote :
Changed in yaws (Ubuntu):
importance: Undecided → Wishlist
status: New → Confirmed
Revision history for this message
Iulian Udrea (iulian) wrote :

Please see https://wiki.ubuntu.com/FreezeExceptionProcess and provide all the missing information.

Changed in yaws (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Charlie_Smotherman (cjsmo) wrote :
Revision history for this message
Charlie_Smotherman (cjsmo) wrote :

Unable to create a diff of upstreams Changelog, as there are no changes between 1.84 and 1.87.
Attached install_log

WOW, so your telling me the release team would rather keep a package that currently FTBFS, rather than sync one over from debian that does build? Could you please explain the regression potential here? I really don't see how the package could regress any more than it already has considering it's current FTBFS state.

Changed in yaws (Ubuntu):
status: Incomplete → New
Revision history for this message
StefanPotyra (sistpoty) wrote :

What testing have you done?

Oh, and just for your question about regressions:
>> rmadison -s lucid yaws
      yaws | 1.84-2 | lucid/universe | source, amd64, i386

so we do have binaries available.

StefanPotyra (sistpoty)
Changed in yaws (Ubuntu):
status: New → Incomplete
Revision history for this message
Steve Langasek (vorlon) wrote :

unsubscribing ubuntu-archive, please resubscribe once FFe is granted.

Revision history for this message
Michael Bienia (geser) wrote :

yaws 1.88-1 got autosynced to maverick.

Changed in yaws (Ubuntu):
status: Incomplete → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.