fmt -w 80 may do for a workaround
Depending on use case, using `fmt -w 80` instead of fold may do for a workaround.
Depending on use case, using `fmt -w 80` instead of fold may do for a workaround.
After pulling recent changes (up to e36ec69) today, I’ve hit what appears to be a regression of issue #359: I get a blank page and a ”Cannot redeclare geoip_country_code_by_name()” (in includes/geo/geoip.inc on line 1602) error in my log.
I can work around the issue by checking out d5a5522, which is the last commit prior to ”Update GeoIP” (96a159b).
I make no guarantees this doesn’t break something else, but for me it seems to work correctly if I make Feediron_Json::format() skip carriage returns:
$ git diff
diff --git a/Json.php b/Json.php
index c988962..fc7f554 100644
--- a/Json.php
+++ b/Json.php
@@ -8,6 +8,7 @@ class Feediron_Json{
$strLen = strlen($json);
$indentStr = ' ';
$newLine = "\n";
+ $cReturn = "\r";
$prevChar = '';
$outOfQuotes = true;
$currentline = 0;
@@ -30,6 +31,9 @@ class Feediron_Json{
$currentline++;
continue;
}
+ if($char == $cReturn){
+ continue;
+ }
if($char == ' ' && $outOfQuotes){
continue;
}
(Using PHP 5.6.30 here.)
@davesteele Yup, installs without a hitch now. Much appreciated!
Was there a regression or is gtk-update-icon-cache now a hard dependency? I’m getting this in Ubuntu 16.04 (when using the PPA).
The following packages have unmet dependencies:
gnome-gmail : Depends: gtk-update-icon-cache but it is not installable
$ zsync http://cdimage.ubuntu.com/ubuntu-server/daily/current/zesty-server-amd64.iso.zsync
#################### 100.0% 144.7 kBps DONE
No relevent local data found - I will be downloading the whole file. If that's not what you want, CTRL-C out. You should specify the local file is the old version of the file to download with -i (you might have to decompress it with gzip -d first). Or perhaps you just have no data that helps download the file
What I *think* it’s trying to say is something like: ”No relevant local data was found, and therefore the entire file will be downloaded. If that’s not what you want, use Ctrl-C to abort. If you do have local data, you should specify the location with -i. If the local data is compressed, decompress it first.”
Also, the ”verifying download…checksum matches OK” message (after downloading is finished) could do with capitalization and whitespace: ”Verifying download… Checksum matches OK.”
Redefining TimeoutIdle or TimeoutNoTransfer in a configuration file inside /etc/proftpd/conf.d/, after they’ve already been defined in /etc/proftpd/proftpd.conf, fails to change those values for the daemon — that is, after restarting the daemon, the values for those parameters remain as those set in /etc/proftpd/proftpd.conf.
At least TimeoutIdle or TimeoutNoTransfer are affected. TimeoutSession and TimeoutLogin, which (in stock 16.04) haven’t been defined in the master configuration file can be set effectively, but setting them first in the master file, then again to different values inside conf.d reveals them to be equally affected.
On the other hand, (at least) ServerName *can* be overridden in the custom configuration file, so the handling of different configuration knobs in this regard seems to be inconsistent.
Steps to reproduce:
1. Create a /etc/proftpd/conf.d/proftpd.conf with the following lines:
TimeoutIdle 10
TimeoutNoTransfer 10
2. Restart proftpd
3. Log into the server, wait 11 seconds
What I expect to happen:
To get kicked out of the server.
What happens instead:
I’m allowed to linger on the server, presumably for the 600 seconds defined for TimeoutNoTransfer in /etc/proftpd/proftpd.conf.
The Include directive, when given a directory as parameter (such as /etc/proftpd/conf.d/, as in the stock /etc/proftpd/proftpd.conf), causes all files in said directory to be read, not just ones ending in .conf. This causes problems if, for instance, I’m using vim to edit a file in the included directory while the proftpd service is being (re)started: vim stores a .swp file in the same directory, and proftpd may fail to start with ”fatal: unknown configuration directive” when it tries to parse the .swp file.
Those scripts are ran from the initrd, so it’s looking for plymouth and plymouthd in the initrd /bin and /sbin directories, and those are probably missing the said files just as the error message says.
/usr/share/initramfs-tools/hooks/plymouth is responsible for copying the plymouth executables onto the initrd, so to see why it fails to copy the files, I added `set -x` to it and then ran `update-initramfs -v -u`.
In my case (I’m running Kodibuntu, I recently upgraded the underlying system from 14.04 to 16.04) the issue was that the hook failed to find Kodibuntu theme files for Plymouth, because it was looking for them in /usr/share/plymouth/themes (which apparently is the standard place), whereas the files actually resided in /lib/plymouth/themes for some (legacy?) reason. The hook therefore determined that I have no working Plymouth theme and thus don’t need the executables.
After moving the theme files to /usr/share/plymouth/themes (and some manual labor updating references in the files themselves as well as Plymouth’s alternatives) the hook now correctly finds those files and then proceeds to copy the Plymouth executables onto the initrd.
Haven’t seen this once since upgrading to 16.04 back in April, so I’m pretty sure the issue has been fixed. Yay!