Public bug reported:
vte (1:0.20.0-0ubuntu1) jaunty; urgency=low
* New upstream release
- Support using a real bold font instead of pseudo-bolding
- Respond to fontconfig configuration changes
- Bugs fixed in this release:
- Bug 54926 – Should try bold version of font before
pseudo-bolding
- Bug 570208 – vte fails to build outside source tree
- Bug 548272 – Fix output of CSI 13,14, 18-21 (LP: #208837)
- Bug 565688 – [gnome-pty-helper] using openpty in a bad way
- Bug 566795 – VTE fails to build in trunk
- Bug 524170 – Support initc terminfo capability and
change-cursor-color
- Bug 566730 – vte_terminal_set_color_cursor() calls invalidate_all but
it doesn't have to
- Bug 565679 – alloca is discouraged
- Bug 565675 – typo in configure.in cause ncurses checking fail
- Bug 565663 – compile failure because use static function in another .h
file
- Bug 575398 – configure warns about term.h under OpenSolaris
- Bug 574616 – "real" transparency not working from python bindings
- Bug 574025 – Crash in _vte_terminal_insert_char
* debian/patches/92_pangocairo_full_bold_fonts.patch:
- Dropped, merged upstream
* debian/patches/90_autoreconf.patch:
- Refreshed for the new release
* debian/patches/94_hardcode_gtkdoc_rebase.patch:
- Temp workaround to prevent FTBFS
** Affects: vte (Ubuntu)
Importance: Undecided
Status: Confirmed
--
Please sponsor vte 0.20.0 (main) into Jaunty
https://bugs.launchpad.net/bugs/344049
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to vte in ubuntu.
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
