The instructions for the workaround were a little off for a Wheezy install and
unfortunately still did not work.
I did:
cd /usr/lib/debootstrp/scripts
chmod +x sid
ln s sid wheezy
That got past the script error, however the package keys do not seem to be
consistent with the debootstrap
Package: freecol
Version: 0.10.5+dfsg-1
Severity: important
Dear Maintainer,
*** Please consider answering these questions, where appropriate ***
* What led up to the situation?
Some time ago freecol was workingon this computer.
Now, it does not.
It might be related to an
Package: libcortado-java
Version: 0.6.0-1
Severity: normal
Dear Maintainer,
*** Please consider answering these questions, where appropriate ***
* What led up to the situation?
I would like to understand why sound does not work in freecol.
Bug#717048
As freecol uses cortado, I was wondering
Package: cpp-4.4
Version: 4.4.5-8
Severity: normal
It looks like cpp does not handle by default symbols which contain diactrics
such as in the following example.
Nonetheless, from my undesrstanding, Linux is assumed to be UTF-8 by default.
#define six 6
char * saint = {six,six,six};
#define π
Package: diff
Version: 1:3.0-1
Severity: normal
When diff is used to compare two files which are identical line by line and a
unique difference which is wether BOM is present or not to indicates UTF-8
encoding, diff does not indicate the good difference. (Byte Order Mark is one
kind of space
Package: bash
Severity: normal
I assume this bug does not exist anymore in version 4.3 as a binary file
appears to only be detected when a nul octet is present within the 80 first
bytes.
According to global.c file:
/* Return non-zero if the characters from SAMPLE are not all valid
Package: bash
Version: 4.1-3
Severity: normal
UTF8 is the standard encoding worldwide nowadays.
Unicode gives two options for starting an UTF8 file: with or without BOM.
BOM character in UTF8 is the sequence of three bytes EF BB BF.
It is introduced by many text editors.
bash only admit script
Package: audacity
Followup-For: Bug #617599
Here is a patch that probably only work on amd 64 bits machines and compatibles
as
it assumes sizeof long equals sizeof double.
--- ./lib-src/libnyquist/nyquist/nyqsrc/fft.c.original 2011-03-10
21:44:23.0 +0100
+++
Package: audacity
Version: 1.3.12-6
Severity: normal
I have a nyquist script using snd-fft api which have a random beaviour on my
computer
where floats are 32 bits and long 64 bits.
Each time I execute the script, result is different, when it should be about
equal.
I 'd like to know if same
Package: audacity
Version: 1.3.12-6
Followup-For: Bug #617599
To reproduce the bug.
Use a 64 amd processor.
Install the nyquist script in ~/.audacity-files/plug-ins/fft.ny
From a console, launch audacity.
If you cannot load a sound with bass such as bachata,
use the audacity menu:
10 matches
Mail list logo
