Fonts are fine and could be changed from qtconfig. I'm running approximately for 2 months and didn't face with a stability problem.
6 Haz 2017 ÖS 8:01 tarihinde "Nick Andre" <[email protected]> yazdı: > Do the fonts look fine? We had stability problems with the older repos. > > Perhaps we can diff the source? > > --Nick > On Tue, Jun 6, 2017 at 00:28 Emir Yapıcı <[email protected]> wrote: > >> Hello Nick! >> >> I've installed QT3 via adding ubuntu archive repos for precise instead of >> building from source. No problem with the fonts. You may try: >> >> echo "deb http://archive.ubuntu.com/ubuntu precise main universe >> multiverse" | sudo tee /etc/apt/sources.list.d/precise.list >> sudo apt-get update >> >> after installation: >> sudo rm /etc/apt/sources.list.d/precise.list >> sudo apt-get update >> >> >> >> *Emir YAPICI* >> >> >> On Tue, Jun 6, 2017 at 2:28 AM, Nick Andre <[email protected]> wrote: >> >>> I'm piloting our auxiliary studio on 2.16.0 with 16.04 now and >>> everything seems fine. >>> >>> Have we done any digging into the font issue? I would assume this is a >>> Qt issue. It looks pretty shabby, though it's usable. >>> >>> --Nick >>> >>> On Wed, Jul 20, 2016 at 04:35 Wayne Merricks < >>> [email protected]> wrote: >>> >>>> Hi Fred/all, >>>> >>>> Apologies for the delay, the current stable branch appears to be usable >>>> with Ubuntu 16.04 provided you manually tweak MySQL. There is still >>>> oddness with QT fonts but that is most likely an Ubuntu and not a >>>> Rivendell problem. >>>> >>>> Since I last tried, DB upgrades from 2.10.3 seem to work fine (I have >>>> about 10,000 carts and its a system that has been running since 2012 in >>>> one form or another). We don't use 16.04 Riv in production here so >>>> anyone thinking of using it be wary of potential for oddness but the >>>> normal stuff all seems fine. >>>> >>>> One thing I have found, adding a host to the DB produces a truncated >>>> error: >>>> >>>> invalid SQL or failed DB connection[Data truncated for column >>>> 'INPUT_TYPE' at row 1 QMYSQL3: Unable to execute query]: >>>> >>>> insert into RDLIBRARY set >>>> INPUT_CARD=0,INPUT_PORT=0,INPUT_TYPE=0 ... STATION="ukriv005" >>>> >>>> The record is added anyway so it is not a big issue but it boils down to >>>> INPUT_TYPE being an ENUM (A, D). This might just be stable branch churn >>>> I'm not sure. >>>> >>>> Please note, we don't use rdcatch, rdfeed or VTs here so I'm not really >>>> sure if any of that is broken (it seems OK but I've not clicked every >>>> option to try them out). >>>> >>>> If you are planning a release soon, I'd say these changes are a good >>>> place to start with Ubuntu, there is nothing obviously wrong that I can >>>> find which is an improvement from barely working. >>>> >>>> Regards, >>>> >>>> Wayne >>>> _______________________________________________ >>>> Rivendell-dev mailing list >>>> [email protected] >>>> http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev >>>> >>> >>> _______________________________________________ >>> Rivendell-dev mailing list >>> [email protected] >>> http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev >>> >>> >>
_______________________________________________ Rivendell-dev mailing list [email protected] http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
