| Summary: | app-text/qpdfview-0.4.12 stabilization request | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Ben de Groot (RETIRED) <yngwin> |
| Component: | [OLD] Keywording and Stabilization | Assignee: | Qt Bug Alias <qt> |
| Status: | RESOLVED OBSOLETE | ||
| Severity: | enhancement | CC: | x86 |
| Priority: | Normal | Keywords: | STABLEREQ |
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Ben de Groot (RETIRED)
2014-12-25 11:19:54 UTC
Hello Ben, I know there will always be bugs (after all I produce most of them in this software) and stable does not equal bug-free, but I think 0.4.13 is a better candidate for stabilization as it fixes a crash and a memory leak within the DjVu backend which where actually introduced in 0.4.12 whereas there have only been paper-cut fixes for 0.4.14 so far. Best regards, Adam. (In reply to Adam Reichold from comment #1) > I think 0.4.13 is a better > candidate for stabilization as it fixes a crash and a memory leak within the > DjVu backend which where actually introduced in 0.4.12 If I may hazard an assumption, I think most people hardly use the djvu backend if at all. I think we can go ahead with the stabilization, but stable-mask the djvu useflag. I do plan to get 0.4.13 stable as soon as the regular 30 day period has passed. Stable-masking the flag sounds overkill to me and would just create more confusion for our users. arm stable This request cannot be completed because of the following repoman error(s): app-text/qpdfview/qpdfview-0.4.12.ebuild: DEPEND: amd64(default/linux/amd64/13.0) ['app-text/mupdf:0/1.4'] Since the amd64 team is unable to continue this task, I'm removing the amd64 arch team from the CC field. Feel free to cc the amd64 arch team again when you provide the complete list of the missing dependencies. Let's continue with version 0.4.13 in bug #540738 |