Debian Bug report logs - #440430
kvm build-depends on gcc-3.4/g++-3.4 (needed for -no-kvm only)

Toggle useless messages

Message #5 received at maintonly@bugs.debian.org (full text, mbox, reply):

From: Matthias Klose <doko@cs.tu-berlin.de>

To: maintonly@bugs.debian.org

Subject: kvm build-depends on gcc-3.4/g++-3.4

Date: Sat, 1 Sep 2007 14:10:55 +0200 (MEST)

Package: kvm
Severity: important
Usertag: build-depends-gcc-3.4

The package build-depends on gcc-3.4 and/or g++-3.4, which we will remove
for the lenny release. Please build the package with the default compiler
currently found in unstable.

The severity of this report is likely to be raised before the release.

Message #10 received at 440430-maintonly@bugs.debian.org (full text, mbox, reply):

From: Baruch Even <baruch@debian.org>

To: Matthias Klose <doko@cs.tu-berlin.de>, 440430-maintonly@bugs.debian.org

Subject: Re: Bug#440430: kvm build-depends on gcc-3.4/g++-3.4

Date: Sat, 1 Sep 2007 21:25:13 +0300

* Matthias Klose <doko@cs.tu-berlin.de> [070901 15:15]:
> Package: kvm
> Severity: important
> Usertag: build-depends-gcc-3.4
> 
> The package build-depends on gcc-3.4 and/or g++-3.4, which we will remove
> for the lenny release. Please build the package with the default compiler
> currently found in unstable.
> 
> The severity of this report is likely to be raised before the release.

I'm not sure about the current status of kvm/qemu but at the time qemu
requires gcc 3.x to compile. Will there be another 3.x compiler or are
we moving completely to 4.x?

Baruch

Message #15 received at 440430-maintonly@bugs.debian.org (full text, mbox, reply):

From: Matthias Klose <doko@cs.tu-berlin.de>

To: Baruch Even <baruch@debian.org>

Cc: 440430-maintonly@bugs.debian.org

Subject: Re: Bug#440430: kvm build-depends on gcc-3.4/g++-3.4

Date: Sat, 1 Sep 2007 20:31:22 +0200

Baruch Even writes:
> * Matthias Klose <doko@cs.tu-berlin.de> [070901 15:15]:
> > Package: kvm
> > Severity: important
> > Usertag: build-depends-gcc-3.4
> > 
> > The package build-depends on gcc-3.4 and/or g++-3.4, which we will remove
> > for the lenny release. Please build the package with the default compiler
> > currently found in unstable.
> > 
> > The severity of this report is likely to be raised before the release.
> 
> I'm not sure about the current status of kvm/qemu but at the time qemu
> requires gcc 3.x to compile. Will there be another 3.x compiler or are
> we moving completely to 4.x?

4.x, you have the free choice of 4.1, 4,2 and 4.3 (snapshot). What is
the upstream status for support of newer compilers?

  Matthias

Message #20 received at 440430-maintonly@bugs.debian.org (full text, mbox, reply):

From: Baruch Even <baruch@debian.org>

To: Matthias Klose <doko@cs.tu-berlin.de>, 440430-maintonly@bugs.debian.org

Subject: Re: Bug#440430: kvm build-depends on gcc-3.4/g++-3.4

Date: Sat, 1 Sep 2007 21:51:17 +0300

* Matthias Klose <doko@cs.tu-berlin.de> [070901 21:34]:
> Baruch Even writes:
> > * Matthias Klose <doko@cs.tu-berlin.de> [070901 15:15]:
> > > Package: kvm
> > > Severity: important
> > > Usertag: build-depends-gcc-3.4
> > > 
> > > The package build-depends on gcc-3.4 and/or g++-3.4, which we will remove
> > > for the lenny release. Please build the package with the default compiler
> > > currently found in unstable.
> > > 
> > > The severity of this report is likely to be raised before the release.
> > 
> > I'm not sure about the current status of kvm/qemu but at the time qemu
> > requires gcc 3.x to compile. Will there be another 3.x compiler or are
> > we moving completely to 4.x?
> 
> 4.x, you have the free choice of 4.1, 4,2 and 4.3 (snapshot). What is
> the upstream status for support of newer compilers?

I remember vaguely that some patches floated around for 4.x support,
I'll look into it.

I guess that if qemu proper will solve the issue kvm will solve it as
well, it's mostly the same code.

Baruch

Message #25 received at 440430@bugs.debian.org (full text, mbox, reply):

From: Jan Lübbe <j.luebbe@atekon.de>

To: 440430@bugs.debian.org

Date: Tue, 27 Nov 2007 19:22:17 +0100

It is possible to compile kvm with gcc-4.x, this will cause the --no-kvm
option be unavailable. The kvm upstream will probably not fix this
problem, so we will have to wait for a gcc-4.x compatible qemu before
reenabling --no-kvm.

Even without --no-kvm the package fullfills its normal function so i'll
downgrade this bug.

-- 
Jan Lübbe <j.luebbe@atekon.de>

Message #32 received at 440430-close@bugs.debian.org (full text, mbox, reply):

From: Jan Lübbe <jluebbe@debian.org>

To: 440430-close@bugs.debian.org

Subject: Bug#440430: fixed in kvm 65+dfsg-2

Date: Fri, 11 Apr 2008 12:04:02 +0000

Source: kvm
Source-Version: 65+dfsg-2

We believe that the bug you reported is fixed in the latest version of
kvm, which is due to be installed in the Debian FTP archive:

kvm-data_65+dfsg-2_all.deb
  to pool/main/k/kvm/kvm-data_65+dfsg-2_all.deb
kvm-source_65+dfsg-2_all.deb
  to pool/main/k/kvm/kvm-source_65+dfsg-2_all.deb
kvm_65+dfsg-2.diff.gz
  to pool/main/k/kvm/kvm_65+dfsg-2.diff.gz
kvm_65+dfsg-2.dsc
  to pool/main/k/kvm/kvm_65+dfsg-2.dsc
kvm_65+dfsg-2_i386.deb
  to pool/main/k/kvm/kvm_65+dfsg-2_i386.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 440430@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Jan Lübbe <jluebbe@debian.org> (supplier of updated kvm package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.8
Date: Thu, 10 Apr 2008 22:52:26 +0200
Source: kvm
Binary: kvm kvm-data kvm-source
Architecture: source all i386
Version: 65+dfsg-2
Distribution: unstable
Urgency: low
Maintainer: Jan Lübbe <jluebbe@debian.org>
Changed-By: Jan Lübbe <jluebbe@debian.org>
Description: 
 kvm        - Full virtualization on x86 hardware
 kvm-data   - Data files for the KVM package
 kvm-source - Source for the KVM driver
Closes: 440430 469125 474209
Changes: 
 kvm (65+dfsg-2) unstable; urgency=low
 .
   * Install PXE boot ROMs only if they exists and Build-Depend on
     etherboot only on i386
     - This allows building on amd64 (closes: #469125)
   * Disable qemu CPU emulation and drop Build-Depend on gcc-3.4
     (closes: #440430)
   * Don't Recommend qemu (we ship qemu-img as kvm-img)
   * Move vde2 from Recommends to Suggests
   * Suggest samba for the -smb option (closes: #474209)
Checksums-Sha1: 
 695299c1c933dc5a8229b6c80d96320088664c8f 1300 kvm_65+dfsg-2.dsc
 ddcede18931cb465df8db78e3556b1ddc314bd0b 29649 kvm_65+dfsg-2.diff.gz
 b776c161041434f1f3f399e533ed8a41126050bd 190336 kvm-data_65+dfsg-2_all.deb
 dda16b1d236311318e6b8efff04ce28ef25e0371 153268 kvm-source_65+dfsg-2_all.deb
 01e294dbec8fbdccd67cc7eaf47499a3ca73df11 609962 kvm_65+dfsg-2_i386.deb
Checksums-Sha256: 
 dea643b98d973c15bcc9a711c63340142e4e8a03be85a752e6555f179ab08075 1300 kvm_65+dfsg-2.dsc
 955281708a997754b952fc9a17d095e707ba4c666c8568b45e986cadb2b896d8 29649 kvm_65+dfsg-2.diff.gz
 adefcf68344bfe2cf72e0b65f6c72963919d248f2e6b305604030369ebc7d5cf 190336 kvm-data_65+dfsg-2_all.deb
 2770eaef5f91be63068e280666a8432be3eda23029643b68073dfaf8742326a2 153268 kvm-source_65+dfsg-2_all.deb
 02f5caded1e0d9fa40fcd190dadcbb50e19d6928b50e42df3d1f7108fcb34605 609962 kvm_65+dfsg-2_i386.deb
Files: 
 34988cdb9e7dd8da48ba85c732430948 1300 misc optional kvm_65+dfsg-2.dsc
 6b9bc6bc3ecff7378b2d596b87ac441d 29649 misc optional kvm_65+dfsg-2.diff.gz
 6e2baa90e81a49587d25243074422615 190336 misc optional kvm-data_65+dfsg-2_all.deb
 190fd459a9248cb165a9b6720e34cb3c 153268 misc optional kvm-source_65+dfsg-2_all.deb
 236604309ad97a8633752488cc9a9ead 609962 misc optional kvm_65+dfsg-2_i386.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFH/n77ioOL5NhIDy4RAqmBAJ4uyoJcFkTtYv5VQjuTcGNa6SYJywCg/VEk
EAYayPFt0+HASPayshfrwBE=
=IkTZ
-----END PGP SIGNATURE-----

Send a report that this bug log contains spam.