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

Bug#377023: marked as done (xdm: FTBFS on GNU/kFreeBSD)



Your message dated Tue, 06 Feb 2007 23:47:03 +0000
with message-id <E1HEa1f-0002Pd-10@ries.debian.org>
and subject line Bug#377023: fixed in xdm 1:1.1.4-1
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---
Package: xdm
Severity: important
Version: 1:1.0.5-1
Tags: patch


Hi,

the current version fails to build on GNU/kFreeBSD.
The same problem probably also affects hurd.

It needs small tweak for configure.ac/configure.
Please find patch bellow.


It would also be nice if you can ask upstream
to include this change.

Thanks in advance

                        Petr
only in patch2:
unchanged:
--- xdm-1.0.5.orig/configure.ac
+++ xdm-1.0.5/configure.ac
@@ -121,7 +121,7 @@


 case $host_os in
-    linux*)
+    linux*|*-gnu)
         OS_CFLAGS="-D_XOPEN_SOURCE"
        SU="su"
         ;;

diff -u xdm-1.0.5/configure xdm-1.0.5/configure
--- xdm-1.0.5/configure
+++ xdm-1.0.5/configure
@@ -23376,7 +23376,7 @@


 case $host_os in
-    linux*)
+    linux*|*-gnu)
         OS_CFLAGS="-D_XOPEN_SOURCE"
        SU="su"
         ;;


--- End Message ---
--- Begin Message ---
Source: xdm
Source-Version: 1:1.1.4-1

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

xdm_1.1.4-1.diff.gz
  to pool/main/x/xdm/xdm_1.1.4-1.diff.gz
xdm_1.1.4-1.dsc
  to pool/main/x/xdm/xdm_1.1.4-1.dsc
xdm_1.1.4-1_i386.deb
  to pool/main/x/xdm/xdm_1.1.4-1_i386.deb
xdm_1.1.4.orig.tar.gz
  to pool/main/x/xdm/xdm_1.1.4.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 377023@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Julien Cristau <jcristau@debian.org> (supplier of updated xdm 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.7
Date: Wed,  7 Feb 2007 00:08:12 +0100
Source: xdm
Binary: xdm
Architecture: source i386
Version: 1:1.1.4-1
Distribution: experimental
Urgency: low
Maintainer: Debian X Strike Force <debian-x@lists.debian.org>
Changed-By: Julien Cristau <jcristau@debian.org>
Description: 
 xdm        - X display manager
Closes: 335388 377023
Changes: 
 xdm (1:1.1.4-1) experimental; urgency=low
 .
   * New upstream release.
     + Refresh/update all patches.
     + Drop style and whitespace changes from xdm_fixes.diff, as they won't
       apply cleanly.
     + Patch to fix FTBFS on non-linux GNU systems applied upstream
       (closes: #377023).
   * Add LSB dependency information to xdm's init script, using patch from
     Petter Reinholdtsen <pere@hungry.com> (closes: #335388).
   * Install upstream ChangeLog.
   * Change my email address in debian/control.
Files: 
 0ee0567420ecaf1270d5db6a68ebaa7c 887 x11 optional xdm_1.1.4-1.dsc
 d03314f8f1e0c3430817db9c2a730111 510513 x11 optional xdm_1.1.4.orig.tar.gz
 a81bd7f1281e263ab7c1d5d06d4a924d 219683 x11 optional xdm_1.1.4-1.diff.gz
 a034e58fd38ffc84209bf46dfc6f6d88 185928 x11 optional xdm_1.1.4-1_i386.deb

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

iD8DBQFFyQ6rmEvTgKxfcAwRAmEGAJ9/AJ1u6508TrZmsGB7yIdzpSy72QCfdDNG
JgJZCsjsdK63Q7b3F16APYA=
=QtXi
-----END PGP SIGNATURE-----


--- End Message ---

Reply to: