Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#34113 - [calibre] missing makedependence qt4-private-headers

Attached to Project: Community Packages
Opened by Vorbote (vorbote) - Saturday, 02 March 2013, 17:18 GMT
Last edited by Andrea Scarpino (BaSh) - Saturday, 02 March 2013, 22:20 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Andrea Scarpino (BaSh)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

As fallout of the transition from qt to qt4, the package qt-private-headers dissapeared from the archive. There are a few packages that require those headers as makedepends. I am aware of Calibre; I am trying to compile the newest version and unfortunately it is impossible with the present state of the repositories.
This task depends upon

Closed by  Andrea Scarpino (BaSh)
Saturday, 02 March 2013, 22:20 GMT
Reason for closing:  Fixed
Additional comments about closing:  qt4-private-headers 4.8.4-1
Comment by John (graysky) - Saturday, 02 March 2013, 17:36 GMT
% sudo abs
% find /var/abs -name PKGBUILD -exec grep 'qt-private-headers' {} \; -print
makedepends=('python2-pycountry' 'qt-private-headers')
./community/calibre/PKGBUILD
Comment by John (graysky) - Saturday, 02 March 2013, 19:37 GMT
My point? Should be obvious: that is the only package that contains that text. Re-read your initial bug report.
Comment by Vorbote (vorbote) - Saturday, 02 March 2013, 19:42 GMT
And did you actually read the first sentence in my answer? Meh! I have no time to waste with a pedant.
Comment by Vorbote (vorbote) - Saturday, 02 March 2013, 19:44 GMT
I'm deleting my comments in this thread. If some developer fixes this, he has my thanks in advance.
Comment by John (graysky) - Saturday, 02 March 2013, 21:04 GMT
Chill out. I clarified a statement made by you: 'there are a few packages that require those headers...' when in actuality there is only one. This defines the scope of the bug, nothing more.

Loading...