Am 05.08.2017 um 17:51 schrieb Adam Williamson:
On Sat, 2017-08-05 at 16:15 +0900, Mamoru TASAKA wrote:
Adam Williamson wrote on 08/05/2017 05:00 AM:
On Wed, 2017-08-02 at 13:19 +0200, David Tardon wrote:
Hi,
I will build a new release of poppler this week, which includes soname
bump. I will take care of rebuilding the affected packages:
boomaga
calligra
cups-filters
evas-generic-loaders
gambas3
gdal
gdcm
inkscape
kf5-kfilemetadata
libreoffice
okular
pdf2djvu
poppler-sharp
texlive
texworks
Welp, the rebuild of texlive failed, which means gdal can't be built,
and I can't build openqa. And none of this seems to have been touched
since yesterday,
Umm? Did you really check?
https://koji.fedoraproject.org/koji/builds?order=-completion_time&userID=803
By 'this' I meant 'poppler and texlive' - I didn't check any others.
Perhaps next time, you could test rebuilds of at least major things
like texlive against the new poppler *before* you land the new poppler
into rawhide? Thanks.
And then, if test rebuild of such a big package like texlive against
new poppler fails, poppler maintainer has to wait until texlive is
to be ported into new poppler?
Yes. Yes, exactly that. We're building a distribution, we're not
running a Who Can Get A New Release Into The Repos The Fastest contest.
If something as important as texlive (which half the world depends on)
doesn't build against a new version of something, we don't want the new
version in our distribution yet.
The new version of poppler isn't compatible with pure C anymore; it
*REQUIRES* to have a C++ compile, that at least support basic
`-std=c++11` implementations like `nullptr`.
I fixed and rebuilt pdf2djvu as it was trivial.
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
