Your message dated Tue, 03 Aug 2010 15:32:53 +0000
with message-id <e1ogju5-0004bh...@franck.debian.org>
and subject line Bug#588930: fixed in chrony 1.24-2
has caused the Debian Bug report #588930,
regarding FTBFS [ia64,hppa]: "I don't know the values of the _IOC_* constants 
on your architecture"
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 ow...@bugs.debian.org
immediately.)


-- 
588930: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=588930
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: chrony
Version: 1.24-1
Severity: serious
User: debian-h...@lists.debian.org

chrony fails to build on hppa on ia64. Complete build logs are
available here:
  https://buildd.debian.org/build.cgi?pkg=chrony&dist=unstable

>From the most recent build attempt on hppa:
[...]
gcc -Wmissing-prototypes -Wall -g -O2 -DLINUX -DHAS_STDINT_H -DHAS_INTTYPES_H 
-DHAVE_IPV6 -DHAVE_SCHED_SETSCHEDULER -DHAVE_MLOCKALL  -DFEAT_RTC=1 -c 
rtc_linux.c
In file included from rtc_linux.c:61:
io_linux.h:40:2: error: #error "I don't know the values of the _IOC_* constants 
for your architecture"
rtc_linux.c: In function 'switch_interrupts':
rtc_linux.c:679: error: 'CHRONY_IOC_NONE' undeclared (first use in this 
function)
rtc_linux.c:679: error: (Each undeclared identifier is reported only once
rtc_linux.c:679: error: for each function it appears in.)
rtc_linux.c:679: error: 'CHRONY_IOC_NRBITS' undeclared (first use in this 
function)
rtc_linux.c:679: error: 'CHRONY_IOC_TYPEBITS' undeclared (first use in this 
function)
rtc_linux.c:679: error: 'CHRONY_IOC_SIZEBITS' undeclared (first use in this 
function)
rtc_linux.c: In function 'set_rtc':
rtc_linux.c:721: error: 'CHRONY_IOC_WRITE' undeclared (first use in this 
function)
rtc_linux.c:721: error: 'CHRONY_IOC_NRBITS' undeclared (first use in this 
function)
rtc_linux.c:721: error: 'CHRONY_IOC_TYPEBITS' undeclared (first use in this 
function)
rtc_linux.c:721: error: 'CHRONY_IOC_SIZEBITS' undeclared (first use in this 
function)
rtc_linux.c: In function 'read_from_device':
rtc_linux.c:916: error: 'CHRONY_IOC_READ' undeclared (first use in this 
function)
rtc_linux.c:916: error: 'CHRONY_IOC_NRBITS' undeclared (first use in this 
function)
rtc_linux.c:916: error: 'CHRONY_IOC_TYPEBITS' undeclared (first use in this 
function)
rtc_linux.c:916: error: 'CHRONY_IOC_SIZEBITS' undeclared (first use in this 
function)
rtc_linux.c: In function 'RTC_Linux_TimePreInit':
rtc_linux.c:1072: error: 'CHRONY_IOC_READ' undeclared (first use in this 
function)
rtc_linux.c:1072: error: 'CHRONY_IOC_NRBITS' undeclared (first use in this 
function)
rtc_linux.c:1072: error: 'CHRONY_IOC_TYPEBITS' undeclared (first use in this 
function)
rtc_linux.c:1072: error: 'CHRONY_IOC_SIZEBITS' undeclared (first use in this 
function)
make[1]: *** [rtc_linux.o] Error 1
make[1]: Leaving directory `/build/buildd-chrony_1.24-1-hppa-b0CbX3/chrony-1.24'
make: *** [build-stamp] Error 2



--- End Message ---
--- Begin Message ---
Source: chrony
Source-Version: 1.24-2

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

chrony_1.24-2.diff.gz
  to main/c/chrony/chrony_1.24-2.diff.gz
chrony_1.24-2.dsc
  to main/c/chrony/chrony_1.24-2.dsc
chrony_1.24-2_amd64.deb
  to main/c/chrony/chrony_1.24-2_amd64.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 588...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
John G. Hasler <jhas...@newsguy.com> (supplier of updated chrony 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 ftpmas...@debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Fri, 30 Jul 2010 20:32:55 -0500
Source: chrony
Binary: chrony
Architecture: source amd64
Version: 1.24-2
Distribution: unstable
Urgency: low
Maintainer: John G. Hasler <jhas...@newsguy.com>
Changed-By: John G. Hasler <jhas...@newsguy.com>
Description: 
 chrony     - Sets your computer's clock from time servers on the Net
Closes: 588930 590888
Changes: 
 chrony (1.24-2) unstable; urgency=low
 .
   * Fixed regression that caused default CHRONY_IOC_ lines to
     vanish from io_linux.h thereby breaking hppa and ia64.
 .
     Closes: #588930: FTBFS [ia64,hppa]: "I don't know the values of the
     _IOC_* constants on your architecture"
 .
   * $remote_fs was added in 1.24-1.  Depending on networking is neither
     necessary nor desireable.
 .
     Closes: #590888: Dependencies on init.d script insuficcient
 .
   * Still need to rewrite scripts.
Checksums-Sha1: 
 bcbbf61947ebc7242b99eb9b6d43286f8c3b7888 1628 chrony_1.24-2.dsc
 2c043468f013bd95b4a2910a97fc4ec1b828410a 133858 chrony_1.24-2.diff.gz
 0c304b37cdca8fa29b7855c98fd9e0f1377255c9 361082 chrony_1.24-2_amd64.deb
Checksums-Sha256: 
 81d6bab6330b9e87f7b61caf85c001a07a2b26d0e8616e831121cc9d26607830 1628 
chrony_1.24-2.dsc
 4ebc86e9953ae48ca114eff180f05bc3decc693ec85b0de227f23e18b355c040 133858 
chrony_1.24-2.diff.gz
 fb61f19cbbb40cd4e10b3853589b67bbd9175df84426d93af98a1fd29937073e 361082 
chrony_1.24-2_amd64.deb
Files: 
 d8ee8aa3f90b5ce5cc5bf82d3ddb7f8b 1628 admin extra chrony_1.24-2.dsc
 391461f4af34252f635680f16b9d0a56 133858 admin extra chrony_1.24-2.diff.gz
 3b798d9eacdf9937553660a6897377da 361082 admin extra chrony_1.24-2_amd64.deb

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

iQIcBAEBCAAGBQJMVGcmAAoJEHNAHjW0+9qlYX0P/3QQrirv31JP0Nu5jVV3nIeG
x/vB5f+a61gAjWczZMNtinOJ3y7PPYC2IE5eFxPdXGxmIxdf/8Qc+1w0lvdXxloQ
wxTxpb/QgP3Fsi5Tic5mmDR85JO5K8y8IXUZcNOhd3jcyvuGqvSDb2zy4AWorDxj
L3Ui6dqxd7MAfahijRoCtzyalK9N9zIUWfzLXUyvefDbwuT0A7e4q4Sg031ne5kC
s5EzXZoLVZtpT9/iRNifbl0HSyYQAUwF7wRjnSRdmxdsck8Vnryos6SKQ9LQFhwW
5auZBfSybjgXHwd9OINCfA/k+kbbem3gxoae2a50r8BlW6IPAKZ6j3wi9mXmHtFP
M4Vv45Ey2xU5vJt8OQbthy5YRiAW5hb3XIvy7f6w67Wn/hmkgFcsb9QvewImna+I
smGsiFge4CKoCQL/1RFG3cVyAjHLDmGTGkXRP6hqHilS/dYBmY08V1KwoZZpqyDS
ovlOpBt7Qr1HgLsnt5NUUXMxwnw3Fyb3bF4MocKb+v6M21J1W5G6suklsI7dqrLA
GtVicaYvLcgCwy+hxWDPqn025GSISZeueHfFY+FXBNsiaD4PtVSBswK0tLH5dZP4
ZdoOBfI2+i9k9lG2QVSDmsJokGW5HNOnpx9X/bqjcYzFxHKAdVtTrRafJsNIqXpY
lXMUSovrGeXeteN0YVTu
=IBja
-----END PGP SIGNATURE-----



--- End Message ---

Reply via email to