On Sun, 2018-11-04 at 18:24 -0800, Samuel Sieb wrote:
> On 11/4/18 7:18 AM, stan wrote:
> > On Sun, 04 Nov 2018 14:29:08 +
> > ja wrote:
> > > warning: %post(tex-fonts-hebrew-0.1-28.fc29.noarch) scriptlet failed,
> > > exit status 255 Error in POSTIN scriptlet in rpm package
> > > tex-fonts-he
On 11/4/18 7:18 AM, stan wrote:
On Sun, 04 Nov 2018 14:29:08 +
ja wrote:
warning: %post(tex-fonts-hebrew-0.1-28.fc29.noarch) scriptlet failed,
exit status 255 Error in POSTIN scriptlet in rpm package
tex-fonts-hebrew Installed: tex-fonts-hebrew-0.1-28.fc29.noarch
This is strange, since it
On Sun, 2018-11-04 at 09:48 -0500, Tom Horsley wrote:
> On Sun, 04 Nov 2018 13:34:29 +
> Patrick O'Callaghan wrote:
>
> > Unless you explicitly deleted the cache (e.g. with 'dnf clean') it
> > should not have been necessary to repeat the download.
>
> I noticed the same thing, I found the kee
On Sun, 04 Nov 2018 14:29:08 +
ja wrote:
> There is a bug in the tex-fonts-hebrew rpm as trying to install
> it on a working machine fails.
> root@paxos:~]$ dnf install tex-fonts-hebrew
> ...
> Installed: tex-fonts-hebrew-0.1-28.fc29.noarch
>
> Installing : tex-fonts-hebrew-0.1-28.fc
On Sun, 04 Nov 2018 13:34:29 +
Patrick O'Callaghan wrote:
> Unless you explicitly deleted the cache (e.g. with 'dnf clean') it
> should not have been necessary to repeat the download.
I noticed the same thing, I found the keepcache parameter
in the dnf.conf man page that says the default is F
On Sun, 2018-11-04 at 13:34 +, Patrick O'Callaghan wrote:
> On Sun, 2018-11-04 at 09:17 +, ja wrote:
> > 2. A fatal dnf error during installation of tex-fonts-hebrew rpm
> > required a complete start from scratch avoiding this particular rpm.
> > (Another 2.5GB download
On Sun, 2018-11-04 at 09:17 +, ja wrote:
> 2. A fatal dnf error during installation of tex-fonts-hebrew rpm
> required a complete start from scratch avoiding this particular rpm.
> (Another 2.5GB download)
Unless you explicitly deleted the cache (e.g. with 'dnf clean') it
I have made a clean installed of F29 onto a small SSD
and had a few problems which may be of interest.
1. It was necessary to separately dd and recreate the required
partitions using gdisk to get the installer to accept a custom layout.
The installer would not let me use the e
