First Last Prev Next    No search results available      Search page      Enter new bug
Bug#: 142457
Alias:
Product:
Component:
Status: RESOLVED
Resolution: FIXED
Assigned To: Gentoo's Team for Core System packages <base-system@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: Christoph Mockenhaupt <gentoo@mockies.de>
Add CC:
CC:
Remove selected CCs
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
baselayout-1.12.2.tar.bz2 corect baselayout file application/octet-stream squade 2006-08-02 02:46 0000 211.44 KB Details
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 142457 depends on: Show dependency tree
Bug 142457 blocks:
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)


Not eligible to see or edit group visibility for this bug.






View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug


Description:   Opened: 2006-08-01 12:15 0000
Emerged baselayout-1.12.2 earlier the day and just noticed, that I'm not able
to use the initscripts in /etc/init.d/ any longer. Just the next empty command
line, no error output.
Running /sbin/runscript by hand shows the problem: 

# runscript
bash: /sbin/runscript: cannot execute binary file

I'm glad, that I had not tried to reboot my system since the update. I was
using baselayout-1.12.1 before without problems.

While installing baselayout these error-messages occur:

strip: powerpc-unknown-linux-gnu-strip --strip-unneeded
   sbin/start-stop-daemon
powerpc-unknown-linux-gnu-strip: Unable to recognise the format of the input
file /var/tmp/portage/baselayout-1.12.2/image/sbin/start-stop-daemon
   sbin/consoletype
powerpc-unknown-linux-gnu-strip: Unable to recognise the format of the input
file /var/tmp/portage/baselayout-1.12.2/image/sbin/consoletype
   sbin/runscript
powerpc-unknown-linux-gnu-strip: Unable to recognise the format of the input
file /var/tmp/portage/baselayout-1.12.2/image/sbin/runscript

but it then merges and installs the package anyways.
If you are not watching the build you wouldn't notice that anything has gone
wrong.

emerge log mail does not contain any errormessages either.


emerge --info
Portage 2.1.1_pre4-r1 (default-linux/ppc/2004.3, gcc-4.1.1, glibc-2.4-r3,
2.6.16-gentoo-r3 ppc)
=================================================================
System uname: 2.6.16-gentoo-r3 ppc 750FX
Gentoo Base System version 1.12.2
app-admin/eselect-compiler: [Not Present]
dev-lang/python:     2.3.5-r2, 2.4.3-r1
dev-python/pycrypto: 2.0.1-r5
dev-util/ccache:     [Not Present]
dev-util/confcache:  [Not Present]
sys-apps/sandbox:    1.2.17
sys-devel/autoconf:  2.13, 2.60
sys-devel/automake:  1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2
sys-devel/binutils:  2.16.1-r3
sys-devel/gcc-config: 1.3.13-r2
sys-devel/libtool:   1.5.22
virtual/os-headers:  2.6.16
ACCEPT_KEYWORDS="ppc"
AUTOCLEAN="yes"
CBUILD="powerpc-unknown-linux-gnu"
CFLAGS="-O2 -pipe -mcpu=750 -fno-strict-aliasing"
CHOST="powerpc-unknown-linux-gnu"
CONFIG_PROTECT="/etc /usr/NX/etc /usr/NX/home /usr/kde/3.5/env
/usr/kde/3.5/share/config /usr/kde/3.5/shutdown /usr/lib/fax
/usr/lib/mozilla/defaults/pref /usr/share/X11/xkb /usr/share/config
/var/spool/fax/etc"
CONFIG_PROTECT_MASK="/etc/env.d /etc/env.d/java/ /etc/gconf
/etc/java-config/vms/ /etc/revdep-rebuild /etc/terminfo /etc/texmf/web2c"
CXXFLAGS="-O2 -fno-strict-aliasing -pipe"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoconfig distlocks fixpackages metadata-transfer sandbox sfperms
strict"
GENTOO_MIRRORS="ftp://ftp-stud.fht-esslingen.de/pub/Mirrors/gentoo/
http://ftp.belnet.be/mirror/rsync.gentoo.org/gentoo/
http://ftp.snt.utwente.nl/pub/os/linux/gentoo"
LANG="de_DE@euro"
LINGUAS="de en en_GB"
MAKEOPTS="-j2"
PKGDIR="/usr/portage/packages"
PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress
--force --whole-file --delete --delete-after --stats --timeout=180
--exclude='/distfiles' --exclude='/local' --exclude='/packages'"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY="/usr/local/portage /usr/portage/local/layman/sunrise"
SYNC="rsync://rsync.europe.gentoo.org/gentoo-portage"
USE="ppc X a52 aac acl alsa apache2 arts audiofile bash-completion berkdb
bitmap-fonts bzip2 calendar cdr cjk cli crypt cups dbus de dlloader dri dv dvd
dvdread emboss encode esd fam fbcon flac font-server foomaticdb fortran gcj gd
gif gphoto2 gpm graphviz gs gstreamer gtk gtk2 hal iconv imagemagick ipv6
isdnlog java jpeg jpeg2k kde kipi libwww mad matroska motif mp3 mpeg mplayer
musicbrainz mysql ncurses nls nptl nptlonly nsplugin ogg oggvorbis openexr
opengl oss pam pcntl pcre pda pdflib perl php png posix ppds pppd python qt qt3
qt4 quicktime rdesktop readline reflection samba scanner sdl session snmp speex
spell spl sql ssl tcpd tetex theora tiff truetype truetype-fonts type1-fonts
unicode usb vorbis wifi wmf xanim xattr xcomposite xine xml xml2 xmms xorg xosd
xv xvid zeroconf zlib elibc_glibc input_devices_keyboard input_devices_mouse
kernel_linux linguas_de linguas_en linguas_en_GB userland_GNU
video_cards_radeon video_cards_vesa video_cards_fbdev"
Unset:  CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LC_ALL, LDFLAGS,
PORTAGE_RSYNC_EXTRA_OPTS

------- Comment #1 From Christoph Mockenhaupt 2006-08-01 12:33:29 0000 -------
hmm...
even more critical: I cannot switch back to baselayout-2.12.1
It tries to download the same file again and again as if the file could not be
fully fetched

I also updated to portage-2.1.1_pre4-r1 today
Might be that there is more than one problem?

------- Comment #2 From Marcel Unbehaun 2006-08-01 13:16:43 0000 -------
I have excactly the same problem(s) on my pegasos2!
Fortunately I has a backup of my system & copied my old baselayout
over the new one manually...

------- Comment #3 From Christoph Mockenhaupt 2006-08-01 13:37:12 0000 -------
Finally, I was able to rebuild baselayout-1.12.1.
It seems that portage gets confused about the multible entries in SRC_URI
I copied baselayout-1.12.1.ebuild to my overlay and changed SRC_URI to

SRC_URI="mirror://gentoo/${P}.tar.bz2"
#       http://dev.gentoo.org/~uberlord/baselayout/${P}.tar.bz2
#       http://dev.gentoo.org/~azarah/baselayout/${P}.tar.bz2
#       http://dev.gentoo.org/~vapier/dist/${P}.tar.bz2"

But I still think this is strange, because the package merged without problems
earlier... I couldn't get it to work with the last version of portage either,
but then I don't know which version of portage I had, when I last compiled
baselayout.

------- Comment #4 From squade 2006-08-02 02:24:25 0000 -------
Hello. I think that this problem is caused by Makefile in
baselayout-1.12.2.tar.bz2. Command: "make all" result: "make: Nothing to be
done for `all'." In src directory ther are compiled binaries for x86-32 (ELF32)
and it probably will work only with x86 profile. My platform is AMD64.

------- Comment #5 From squade 2006-08-02 02:46:45 0000 -------
Created an attachment (id=93253) [edit]
corect baselayout file

------- Comment #6 From Roy Marples (RETIRED) 2006-08-02 02:47:26 0000 -------
OK, I've updated our build script to make clean before building the tarball so
this should not happen again. My appologies for this :/

baselayout-1.12.3 has the fix.

------- Comment #7 From Jakub Moc (RETIRED) 2006-08-03 13:45:14 0000 -------
*** Bug 142690 has been marked as a duplicate of this bug. ***

------- Comment #8 From SpanKY 2006-08-04 08:30:30 0000 -------
ive also updated the build script to check for .o files and not allow a tarball
to be created if they exist

First Last Prev Next    No search results available      Search page      Enter new bug