Your message dated Thu, 23 Apr 2009 21:34:59 +0000
with message-id <[email protected]>
and subject line Bug#507325: fixed in v86d 0.1.9-1
has caused the Debian Bug report #507325,
regarding New version of v86d upstream available:  v86d-0.1.9
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
507325: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=507325
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: v86d
Version: 0.1.6-1+klibc-1.5.14-1~exp1+linux-2.6.27-rc5-tip-master+fac8f1e4
Severity: wishlist


I compile my own kernels, and rely on 'uvesafb' to allow me to use 60
Hz modes with my monitor that are not official VESA modes.

I haven't updated my kernels since September because of a kernel bug
that prevented any 2.6.2[67] kernel from working on 2 of my 3
machines.  After seeking help on LKML during August, fixes to the PCI
initialization routines in the kernel were developed, but were too
late in the process to be included in 2.6.27... but now the 2.6.28
kernel is nearing release, and 2.6.28-rc3 is the first kernel that
runs on all of my machines (without hanging during boot) since kernel
2.6.25.

I am currently building kernels for all of my machines, but I always
build 'klibc' and 'v86d' from source -- as per the recommendations of
the UVESA FB author at

    http://dev.gentoo.org/~spock/projects/uvesafb/

Just now, I noticed that 'apt-cache policy v86d' gives me this:

v86d:
  Installed: 0.1.6-1+klibc-1.5.14-1~exp1+linux-2.6.27-rc5-tip-master+fac8f1e4
  Candidate: 0.1.6-1+klibc-1.5.14-1~exp1+linux-2.6.27-rc5-tip-master+fac8f1e4
  Version table:
 *** 0.1.6-1+klibc-1.5.14-1~exp1+linux-2.6.27-rc5-tip-master+fac8f1e4 0
        100 /var/lib/dpkg/status
     0.1.5.2-1 0
        990 ftp://ftp.uwsg.indiana.edu unstable/main Packages

which indicates that the last version of 'v86d' available as a Debian
package is still 0.1.5.2!  The UVESA FB website lists the lastest
version as 0.1.9!!

I've never had a problem with any version of 'v86d' -- though I always
home brew mine and never use the precompiled Debian binaries -- so I
consider this a wishlist request.  As you can see from the 'apt-cache'
output above, the last time I built 'v86d' I hacked together DEBs by
using the 'debian' directory from the 0.1.5.2 sources with the "Spock"
upstream version of 0.1.6.  I am about to try the same hack again with
0.1.9, so we'll see how that goes.

Also, I requested before that the scripts used to produce the DEBs
should include the 'misc/initramfs' file in some shared directory in
the filesystem, so that later kernel compilations could continue to
use the currently-installed 'v86d' package via the CONFIG_INITRAMFS_
SOURCE kernel option.  The UVESA FB author seems to have standardized
a location for packages to install that file (see step 6 under
"uvesafb::installation instructions" at the website mentioned above):

    /usr/share/v86d/initramfs

It should be simple to copy this text file to the proper location in
'debian/v86d-<version>/usr/share/v86d' when the DEB is being created.


Thanks,
Dave W.


-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (350, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.27-rc5+fac8f1e4-080918.desktop.uvesafb (SMP w/2 CPU cores; 
PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

v86d depends on no packages.

Versions of packages v86d recommends:
ii  initramfs-tools               0.92l      tools for generating an initramfs

v86d suggests no packages.

-- no debconf information



--- End Message ---
--- Begin Message ---
Source: v86d
Source-Version: 0.1.9-1

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

v86d_0.1.9-1.diff.gz
  to pool/main/v/v86d/v86d_0.1.9-1.diff.gz
v86d_0.1.9-1.dsc
  to pool/main/v/v86d/v86d_0.1.9-1.dsc
v86d_0.1.9-1_i386.deb
  to pool/main/v/v86d/v86d_0.1.9-1_i386.deb
v86d_0.1.9.orig.tar.gz
  to pool/main/v/v86d/v86d_0.1.9.orig.tar.gz



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 [email protected],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Evgeni Golov <[email protected]> (supplier of updated v86d 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 [email protected])


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

Format: 1.8
Date: Thu, 23 Apr 2009 21:58:45 +0200
Source: v86d
Binary: v86d
Architecture: source i386
Version: 0.1.9-1
Distribution: unstable
Urgency: low
Maintainer: Evgeni Golov <[email protected]>
Changed-By: Evgeni Golov <[email protected]>
Description: 
 v86d       - daemon to run x86 code in an emulated environment
Closes: 507325
Changes: 
 v86d (0.1.9-1) unstable; urgency=low
 .
   * New upstream release. (Closes: #507325)
   * debian/rules:
     + Install misc/initramfs to /u/s/v86d (as requested by Dave Witbrodt).
     + Use dh_clean instead of rm -f in the clean target.
     + Use $(QUILT_STAMPFN) instead of patch, so configure isn't run twice.
     + Add $(CURDIR) to the direct install calls.
   * debian/patches:
     + Refresh 01_use-external-libx86.patch as upstream has changed the
       Makefile a bit.
     + Add 02_fix-parsing-of-OEM-descriptions.patch and
       03_map-BIOS-with-PROT_WRITE.patch from upstream git.
   * debian/README.Debian:
     + Note that uvesafb is in Debian's default kernels now.
     + Correctly document initrd usage.
     + uvesafb from recent kernels wants mode_option instead of mode.
   * debian/control:
     + Update my e-mail address.
     + Bump Standards-Version to 3.8.1.
Checksums-Sha1: 
 9f62a963c14d18b1fad2e31f3b3ba281f1f88040 1006 v86d_0.1.9-1.dsc
 8bc6531c4c4884cb0b1c2212c51ea54a9904985b 85881 v86d_0.1.9.orig.tar.gz
 29039f874c760ea71ea7a250ae25c7d75a3668dc 7501 v86d_0.1.9-1.diff.gz
 5ccd4bc66f3e9d30d0d896a6c983316c40734449 11628 v86d_0.1.9-1_i386.deb
Checksums-Sha256: 
 e2bf1ab3b768e9d13ae1d1a69b6f66465d17857d2c6a17cb0bf6a79e2f862214 1006 
v86d_0.1.9-1.dsc
 066ebcb5ac77a2dec52aabc08602f9a335e50e15bb0978bc284b55a9de4c9551 85881 
v86d_0.1.9.orig.tar.gz
 f08fd639f6736e5234eb66fa52ccb519eef351ecb0f446081910afe4b5f3efb7 7501 
v86d_0.1.9-1.diff.gz
 f4195afef94ad6889b0d5357f76d422cb1ea90cd5b1e073fc0f8f5ff959ea25d 11628 
v86d_0.1.9-1_i386.deb
Files: 
 43626bb308396d9009e2e88b1be66780 1006 utils optional v86d_0.1.9-1.dsc
 d546125ced42add5b16eb85e16591a4c 85881 utils optional v86d_0.1.9.orig.tar.gz
 52880acc8345a7b3e79792f910b1493a 7501 utils optional v86d_0.1.9-1.diff.gz
 bf95c65ce28d2f0827cd51c07f5e0ca2 11628 utils optional v86d_0.1.9-1_i386.deb

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

iEYEARECAAYFAknwy90ACgkQJKAUGKwVtQzVdACfTp0Ord02ScH0YEb8vnrMdt6I
DXIAnA/Jx5F20cK1H8TiT5kcvYeEmZx4
=nOFx
-----END PGP SIGNATURE-----



--- End Message ---

Reply via email to