Dear maintainers:
This bug report refers to a couple of distinct issues:
1. Evaluating arbitrary Lisp code when a file is opened.
2. Evaluating arbitrary LaTeX code in various circumstances.
While the second issue is important to consider, I'd like to
focus on the first part. This is a grave
On 12/13/17, Benjamin Moody <benjamin.mo...@gmail.com> wrote:
> Same problem here. 3.16.43-2+deb8u5 works, 3.16.51-2 is broken.
>
> Supermicro H8QM3
>
> Quad-Core AMD Opteron(tm) Processor 8347 HE (fam: 10, model: 02,
> stepping: 03)
>
> Two 3ware 9650SE RAID cards
Package: src:linux
Followup-For: Bug #884183
Same problem here. 3.16.43-2+deb8u5 works, 3.16.51-2 is broken.
Supermicro H8QM3
Quad-Core AMD Opteron(tm) Processor 8347 HE (fam: 10, model: 02,
stepping: 03)
Two 3ware 9650SE RAID cards
I can get the system to boot by doing the following:
*
Unless there is an automated way to identify all the cases of
integer/pointer confusion, I don't expect there'll ever be a way to
make libxview work on LP64 systems. I am less familiar with
olwm/olvwm, but this report is not encouraging.
It seems to me that the most sensible thing to do would be
This is a duplicate of bug #731998.
Here are patches to fix these issues.
First, the use of regexp.h as noted by the submitter.
Second, the use of 'union wait' which is apparently also unsupported
by the glibc in stretch.
Third, the manpage preprocessing error. This is not actually a build
failure (which is presumably a bug in
Package: backintime-common
Version: 1.0.36-1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
The current version of backintime seems to require the 'python-dbus'
package:
# /usr/bin/backintime --backup-job
Traceback (most recent call last):
File
7 matches
Mail list logo
