[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Installed xosview 1.7.3-10 (i386 source)



-----BEGIN PGP SIGNED MESSAGE-----

Format: 1.7
Date: Sun,  3 Feb 2002 18:19:06 -0600
Source: xosview
Binary: xosview
Architecture: source i386
Version: 1.7.3-10
Distribution: unstable
Urgency: low
Maintainer: Zed Pobre <zed@debian.org>
Changed-By: Zed Pobre <zed@debian.org>
Description: 
 xosview    - X based system monitor
Closes: 117297 126469
Changes: 
 xosview (1.7.3-10) unstable; urgency=low
 .
   * Undocumented fixes from the 3.1 NMU reinstated:
     * s/friend XWin/friend class Xwin/ in xwin.h
     * ia64, hppa, arm, mips (and alpha, but that was already taken care
       of) cannot deal with ioperm, so exclude them in
       linux/serialmeter.cc.
     * use std::hex instead of hex in serialmeter.cc
   * The above changes mean that arm and mips can actually compile
     serialmeter.cc, so remove the ugly hack used in 1.7.3-9.
   * The ioperm changes should fix compilation on mips (closes: #117297),
     and the C++ changes should fix hppa (closes: #126469).
Files: 
 c2a38d31684fb1f5dc5a21a3937aea76 837 utils optional xosview_1.7.3-10.dsc
 bc40c2b45257bf64e60cafc0af2d5c9c 30551 utils optional xosview_1.7.3-10.diff.gz
 48b19b18cbf9d50ac46cac4028700e77 71900 utils optional xosview_1.7.3-10_i386.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6

iQEVAwUBPF3XSR0207zoJUw5AQGCKggAtv6A4keb5r3QEafnqrCcQnr3nuB7xQXW
17M4lf7QvJx9bDf48RMHYDQJ7JxZeotDjxdTtvr3M7MaAJfkf1tJn1uAfMZunmuE
R+51vv4JO+FIQtkNJzJUq64tBvM5EoBy4Mk2hw4xCNQ0NLe/HJNzaWHloBVDIsAq
A/atrS01D02Waxh1SzvyASbBvtrNIVVNKXht5pOblrlU1DehX56X+6czxWpn+64b
dVjo3wIHzsPLB3+ubZIx1chCxamkkYwAyh/SdBBH1fx6JTpcAkEE+ny+M+psXK31
Rxw3jfBL2V8/hj7PzSIlTky0fuYgnXWYQAasz1JpyOoBa/L6r7CMKw==
=hB5N
-----END PGP SIGNATURE-----


Installed:
xosview_1.7.3-10.diff.gz
  to pool/main/x/xosview/xosview_1.7.3-10.diff.gz
xosview_1.7.3-10.dsc
  to pool/main/x/xosview/xosview_1.7.3-10.dsc
xosview_1.7.3-10_i386.deb
  to pool/main/x/xosview/xosview_1.7.3-10_i386.deb



Reply to: