Hi, Brandon. The fix isn't released into the packaging stream yet, so yum doesn't know anything about it. See Fred's sentence: "Known issue, fixed in Git ‘master’. >>It will appear in the next regular release.<<"
If you're a site that builds Rivendell itself, rather than using the pre-packaged system, you would need to pull the latest Rivendell source updates from the github repository and do a mass build. Otherwise you'll need to wait until Fred & Co. release the next 3.x package. Mike On Fri, Oct 4, 2019 at 11:01 PM Brandon <bran...@subliminalradio.net> wrote: > Hi Robert, > > So last night, we ran yum update -y as root on the server and there were > no updates to apply... Removing the %i wildcard on the server also didn't > fix the issue (even though it worked on my virtualbox Rivendell test > server/client setup). > > We installed the client last night and ran yum update -y as root. The > dropboxes still fail to import with metadata wildcards. However, dropboxes > on the client successfully import to the server without the metadata > wildcards. > > Thanks for the help!! > > On Thu, Oct 3, 2019 at 10:56 AM Robert Jeffares <jeffares.rob...@gmail.com> > wrote: > >> Hi Brandon, >> >> do a # yum update -y [as root] and the metadata wildcards should then >> work. >> >> as will the logging bit. >> >> The dropbox code was broken but has been fixed. >> >> I run update a couple of times after install as a matter of course. >> >> regards >> >> Robert >> On 10/3/19 8:07 PM, Brandon wrote: >> >> Hello everyone! >> >> Not sure if I discovered a bug in v3.1.0... Or a glitch specific to our >> install at UCLA Radio in LA. >> >> Just did a fresh Server/Client Riv 3.1.0 install on CentOS 7 with the >> appliance script. Converted the DB from previous V2.10.3 install. >> Everything seemed to go without a hitch. >> >> The problem: Dropbox is ignoring files and not reporting any errors in >> the error log. When I run rdimport from the command line, it threw an error >> (which I don't recall at the moment -- but Googling made it sound like an >> Apache error) -- but this seems unlikely since we installed from the >> appliance script. >> >> After experimenting with different Dropbox configs all night, removing %i >> from the Dropbox Metadata Pattern field fixed the issue and Dropbox resumes >> importing files. Using %t_%a metadata pattern also fails to import >> anything. >> >> Is anyone else experiencing Dropbox import issues when specifying >> metadata patterns? >> >> We can live without it, but %i gives us the cleanest cut titles without >> "imported from..." in the titles, although doesn't fix cart titles. Worked >> as expected in 2.10.3. >> >> Thank you!! >> >> -- >> Brandon Anjeleno >> Subliminal Radio <http://subliminalradio.net/popup-player> >> (213) 839-7667 <//+1-213-839-7667> >> >> _______________________________________________ >> Rivendell-dev mailing >> listRivendell-dev@lists.rivendellaudio.orghttp://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev >> >> _______________________________________________ >> Rivendell-dev mailing list >> Rivendell-dev@lists.rivendellaudio.org >> http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev >> > > > -- > Brandon Anjeleno > Subliminal Radio <http://subliminalradio.net/popup-player> > (213) 839-7667 <//+1-213-839-7667> > _______________________________________________ > Rivendell-dev mailing list > Rivendell-dev@lists.rivendellaudio.org > http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev >
_______________________________________________ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
