On 09/01/15 20:50, Mathieu Malaterre wrote:
Control: severity -1 grave
See 774883#12 (Thanks Ben !)
The package has been non-functional for the last three releases. Do
not ship on jessie.
The apm_bios device workaround was only relevant for Xfree, its lack
does not affect functionality of pmud
Hi,
sorry about the bounce - I had been assured mail forwarding would be
set up when the mailserver handling that address was retired.
Shall I prepare a source-only upload to correct the address?
Cheers,
Michael
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a sub
> Package: mac-fdisk
> Version: 0.1-15
> Severity: serious
> Tags: patch d-i
>
> The udebs do not get a correct dependency on libc6-udeb, but instead
> depend on the regular libc6 package. We've ignored this for previous
> releases, but for Squeeze it's RC because of britney support for udebs.
Hi,
I'll have to let Christian answer for the licensing of
cts_amiga_info.tar.gz. The rest of the amiga icons are in the d-i
repo. If these have clear licensing (I'm pretty sure they do) then
we should probably move them there too.
As I recall they were created either by or for Christian to use
> Thanks for the patch. However, I propose that the definition should be
> in the Imakefile, where the other architecture specific definitions
> are as well. Unfortunately I don't have access to a 64-bit machine at
> the moment, could you test that the patch below actually works?
The patch actuall
Package: rasmol
Version: 2.7.2.1.1-4
Severity: serious
rasmol is unuseable on amd64 (and perhaps other 64bit architectures) due
to using the wrong data type for writes to the frame buffer. This simple
patch fixes it:
--- src/rasmol.h.org2006-11-10 09:35:34.0 +0100
+++ src/rasmol.h
Package: apache2.2-common
Version: 2.2.3-1
Severity: serious
Prevents proper unattended installation of apache2.2-common:
Setting up apache2.2-common (2.2.3-1) ...
touch: cannot touch `/var/log/apache2/error.log': No such file or directory
touch: cannot touch `/var/log/apache2/access.log': No suc
It very much is - removing qt3-dev-tools and qt3-qtconfig fixed it for me
while upgrading a testing installation.
Michael
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
> Package: pmud-utils
> Version: 0.10-9
> Severity: serious
> Justification: Breaks installation of new X11/XOrg R7.0
>
> Please install xmouse into /usr/bin, rather than /usr/X11R6/bin. The
> current X in unstable has removed the /usr/X11R6/bin directory:
Yep; noticed that on the m68k autobuilde
Package: libc6
Version: 2.3.5-6
Severity: serious
Architecture: powerpc
Subject says it: while upgrading from a rather dated testing install
(around Apr. 05) with libc6 2.2.5-11.8 to current testing, a number of
things went wrong.
Most notably, upon unpacking libc6 2.3.5-6, the libc6 postinstall
> On Fri, Mar 25, 2005 at 01:38:27AM +0100, Daniel Kobras wrote:
> > On Tue, Mar 22, 2005 at 08:36:01PM +, Paul Brossier wrote:
> > > there is probably a better mean to do so though, ie checking what
> > > type of conversion is needed according to libavcodec, but it does
> > > effectively fixes
Package: bison
Version: 1.875d-1
Severity: serious
Synopsis: installation of bison does not properly install the yacc
alternatives symlinks - see below.
> I think I ran into this a few months back. It had to do with
> alternatives -- very odd.
Odd indeed. I found a stale yacc alternatives file
> On Mon, Feb 14, 2005 at 05:41:26PM +0100, Michael Schmitz wrote:
> > I can confirm the XV problem is the same old problem that a patch had
> > been posted for in http://jira.schirmacher.de/jira-kino/browse/KINO-76.
> > I've added some #ifdef __BIG_ENDIAN__ around
> > I suspect kino declares BE audio data to be LE in the DV export (or indeed
> > any) pipe. No idea what's the cause of the XV and mpeg2enc endianness
> > problems though.
>
> The audio problems seem to be caused (at least) by big-endian length
> fields in an otherwise little-endian WAV file. I'm
Sorry for the late reply; I've been away from my Powerbook (or indeed,
the net) for the last weeks...
> On Fri, Jan 07, 2005 at 06:37:52PM +0100, Michael Schmitz wrote:
> > Severity: serious
>
> Can you please comment on why you think these bugs make kino unsuitable
> fo
15 matches
Mail list logo
