On Thu, Apr 17, 2014 at 10:39 AM, Reindl Harald <h.reindl@xxxxxxxxxxxxx> wrote: > > > Am 17.04.2014 09:50, schrieb David Tardon: >> On Thu, Apr 17, 2014 at 12:48:47AM +0200, Reindl Harald wrote: >>> why do whe have that always with libreoffice? >> >> I will send a note to the editors of Oxford English Dictionary that >> "always" has been redefined to mean "in less than 10 % of cases". If I >> count correctly, we have issued 26 updates for F-20 that made it into >> stable (plus a few others that were obsoleted by a later one). One of >> these had a problem. Now there is a second one. > > the main question is why > >>> the broken build hangs around for 30 hours in the repo >> >> Good. Since you are so concerned about it, what have you done to make me >> aware of the problem? > > https://admin.fedoraproject.org/updates/FEDORA-2014-5062/libreoffice-4.2.3.3-4.fc20?_csrf_token=18bde034162ac31ef2045718cb3349921b85b388 > > hreindl - 2014-04-16 09:02:37 > independent of how often i do rm -rf /var/cache/yum* i still have the broken previous build in updates-testing > starting with yesterday evening Processing Dependency: libtllo.so()(64bit) for package: > 1:libreoffice-writer-4.2.3.3-3.fc20.x86_64 > >> Hint: I consider the mails from various Fedora tools as nonessential > > which seemes to be a problem if you don't verify your builds No the problem here is that our tools are broken and have been for a long time. Dep check is something that can and should be automated. This is being worked on though to finally have something that works. -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
