util-linux lacks fdisk
The fdisk programs are missing from util-linux-2.12-7.
The attached patch gets them to build and they apparently work. Is
there some reason why this was not done already, or was it just
overlooked?
--
Oliver Elphick olly@lfix.co.uk
Isle of Wight http://www.lfix.co.uk/oliver
GPG: 1024D/A54310EA 92C8 39E7 280E 3631 3F0E 1EC0 5664 7A2F A543 10EA
========================================
"Jesus said unto her, I am the resurrection, and the
life. He that believeth in me, though he were dead,
yet shall he live." John 11:25
diff -cr util-linux-2.12.orig/debian/control util-linux-2.12/debian/control
*** util-linux-2.12.orig/debian/control Mon May 17 09:33:13 2004
--- util-linux-2.12/debian/control Mon May 17 09:08:07 2004
***************
*** 54,60 ****
Included are: logger, renice, replay, script, wall
Package: fdisk-udeb
! Architecture: alpha arm hppa i386 ia64 mips mipsel powerpc hurd-i386 sparc
Priority: extra
Section: debian-installer
Depends: ${cfdisk-udeb:Depends}
--- 54,60 ----
Included are: logger, renice, replay, script, wall
Package: fdisk-udeb
! Architecture: alpha amd64 arm hppa i386 ia64 mips mipsel powerpc hurd-i386 sparc
Priority: extra
Section: debian-installer
Depends: ${cfdisk-udeb:Depends}
diff -cr util-linux-2.12.orig/debian/rules util-linux-2.12/debian/rules
*** util-linux-2.12.orig/debian/rules Mon May 17 09:33:13 2004
--- util-linux-2.12/debian/rules Mon May 17 09:06:19 2004
***************
*** 15,21 ****
export arch = $(DEB_HOST_ARCH)
version := $(shell sed -e '1{;s|^util-linux (\(.*\))\ .*|\1|;q;}' debian/changelog)
! fdisk_arch = $(findstring $(arch),alpha i386 powerpc arm mips mipsel hppa ia64 hurd-i386)
sparc = $(findstring $(arch),sparc)
nohwclock = $(findstring $(arch),s390)
--- 15,21 ----
export arch = $(DEB_HOST_ARCH)
version := $(shell sed -e '1{;s|^util-linux (\(.*\))\ .*|\1|;q;}' debian/changelog)
! fdisk_arch = $(findstring $(arch),alpha i386 powerpc arm mips mipsel hppa ia64 hurd-i386 amd64)
sparc = $(findstring $(arch),sparc)
nohwclock = $(findstring $(arch),s390)
Reply to: