[gentoo-catalyst] Problem with NMAP

[gentoo-catalyst] Problem with NMAP

[Kosta Todorovic]

[-- Attachment #1: Type: text/plain, Size: 303 bytes --]

I've tried to add NMAP to the livecd using catalyst but when I try and
run it it gives the following error:
nmap: error while loading shared libraries: libstdc++.so.5: cannot
open shared object file: No such file or directory


I have attached my spec files and fsscript.sh for more information.

[-- Attachment #2: livecd-stage1_hackbox-0.1.spec --]
[-- Type: application/octet-stream, Size: 1877 bytes --]

subarch: x86
version_stamp: 20050422 
target: livecd-stage1
rel_type: default
profile: default-linux/x86/2005.0
snapshot: 20050419
source_subpath: default/stage3-x86-2005.0
livecd/use:
        minimal
        ncurses
        readline
        ssl
	-X
	-gtk
	-gtk2
	-gnome
	-cups
	-mysql
	-svga
	ipv6
	socks5
	livecd
	fbcon
	-opengl
#	ethereal
		
livecd/packages:
        baselayout
        livecd-tools
        module-init-tools
        dhcpcd
        udev
        gentoo-sources
        kudzu-knoppix
        hotplug
        coldplug
        fxload
#       tsocks
        irssi
        gpm
        syslog-ng
        parted
        links
        raidtools
        nfs-utils
        jfsutils
        usbutils
        pciutils
        xfsprogs
        e2fsprogs
        reiserfsprogs
#       cryptsetup
        pwgen
        popt
        dialog
        rp-pppoe
        screen
        mirrorselect
        penggy
        iputils
        hwdata-knoppix
        hwsetup
        device-mapper
        lvm2
        evms
        vim
        pptpclient
        mdadm
        ethtool
        wireless-tools
        ntfsprogs
        dosfstools
        prism54-firmware
        wpa_supplicant
        genkernel
        tcpdump
        nmap
        libpcap
        sniffit
        telnet-bsd
        ftp
        hping
        dsniff
        bind-tools
        ethereal
        iproute2
        iptables
        shorewall
        iptraf
        dhcp
	bing
	bwmon
	dnstracer
	hydra
	johntheripper
	iftop
	macchanger
	netcat
	samba
	aircrack
#	kismet
	wepattack
	webmin	
	nessus	
	authforce
	angst
	amap
	vtun
	nast	
	hunt
	nbaudit
	nbtscan
	nikto
	ssldump
	chaosreader
	steghide
	examiner
	foremost
	sleuthkit
	rats
	flawfinder
	pscan
	slocate
	syslog-ng
	mutt
	pine
	bash-completion
	chkrootkit
	fping
	fprobe
	httping
	mping
	scanssh
	snort
	clamav
	airtraf
	wavemon
	rkhunter
#	aimsniff 

[-- Attachment #3: livecd-stage2_hackbox-0.1.spec --]
[-- Type: application/octet-stream, Size: 6392 bytes --]

subarch: x86
version_stamp: 20050422
target: livecd-stage2
rel_type: default
profile: default-linux/x86/2005.0
snapshot: 20050419
#source_subpath: default/livecd-stage1-x86-2005.0
source_subpath: default/livecd-stage1-x86-20050422

livecd/cdfstype: squashfs
livecd/archscript: /usr/lib/catalyst/livecd/runscript/x86-archscript.sh
livecd/runscript: /usr/lib/catalyst/livecd/runscript/default-runscript.sh
livecd/cdtar: /usr/lib/catalyst/livecd/cdtar/isolinux-2.13-memtest86+-cdtar.tar.bz2
# This fsscript removes serial and is not necessary in catalyst > 1.1.7
livecd/fsscript: /root/fsscript.sh
#livecd/iso: /home/beejay/2005.0/move/x86-installcd-2005.0-rc10.iso
livecd/iso: /etc/catalyst/test/hackbox-0.1-x86-20050422.iso
livecd/splash_type: gensplash
livecd/splash_theme: livecd-2005.0
livecd/gk_mainargs: --lvm2 --dmraid  
livecd/type: gentoo-release-minimal
livecd/modblacklist:
	8139cp


livecd/motd: /usr/lib/catalyst/livecd/files/hackbox-0.1.motd

#livecd/overlay: /root/livecd/overlay-minimal
#livecd/overlay: /home/beejay/2005.0/overlay-minimal/
livecd/overlay: /root/my_overlay/

livecd/devmanager: udev

# Commented by Chris Gianelloni
livecd/rcadd:
#	syslog-ng:default
	gpm:default
	nessusd:default
	webmin:default
	sshd:default	

boot/kernel: gentoo
boot/kernel/gentoo/sources: gentoo-sources

boot/kernel/gentoo/config: /usr/share/livecd-kconfigs-2005.0/x86/2.6.11-smp.config

boot/kernel/gentoo/use: pcmcia usb -X

boot/kernel/gentoo/postconf:
	splashutils
	splash-themes-livecd

boot/kernel/gentoo/packages:
	pcmcia-cs
	speedtouch
	slmodem
	globespan-adsl
	hostap-driver
	hostap-utils
	acpid
	cryptsetup

livecd/unmerge:
	autoconf
	automake
	bin86
	binutils
	libtool
	m4
	bison
	ld.so
	make
	patch
	linux-headers
	man-pages
	sash
	flex
	texinfo
	ccache
	distcc
	addpatches
	man
	groff
	lib-compat
	miscfiles
	rsync
	bc
	genkernel
	gcc-config
	gnu-config
	gcc
	grub
	help2man

livecd/empty:
	/var/tmp
	/var/cache
	/var/db
	/var/empty
	/var/lock
	/var/log
	/var/run
	/var/spool
	/var/state
	/tmp
	/usr/portage
	/usr/share/man
	/usr/share/info
	/usr/share/unimaps
	/usr/include
	/usr/share/zoneinfo
	/usr/share/dict
	/usr/share/doc
	/usr/share/ss
	/usr/share/state
	/usr/share/texinfo
	/usr/lib/python2.2
	/usr/lib/portage
	/usr/share/gettext
	/usr/share/i18n
	/usr/share/rfc
	/usr/X11R6/man
	/usr/X11R6/include
	/usr/X11R6/lib/X11/config
	/usr/X11R6/lib/X11/etc
	/usr/X11R6/lib/X11/doc
	/usr/src
	/usr/share/doc
	/usr/share/man
	/root/.ccache
# Added by wolf31o2
	/etc/cron.daily
	/etc/cron.hourly
	/etc/cron.monthly
	/etc/cron.weekly
	/etc/logrotate.d
	/etc/rsync
	/usr/X11R6
	/usr/include
	/usr/lib/awk
	/usr/lib/ccache
	/usr/lib/gcc-config
	/usr/lib/nfs
	/usr/local
	/usr/diet/include
	/usr/diet/man
	/usr/share/consolefonts/partialfonts
	/usr/share/consoletrans
	/usr/share/emacs
	/usr/share/gcc-data
	/usr/share/genkernel
	/etc/bootsplash/gentoo
	/etc/bootsplash/gentoo-highquality
	/etc/splash/gentoo
	/etc/splash/emergence
	/usr/share/gnuconfig
	/usr/share/lcms
	/usr/share/locale/af
	/usr/share/locale/be
	/usr/share/locale/bg
	/usr/share/locale/bs
	/usr/share/locale/ca
	/usr/share/locale/cs
	/usr/share/locale/da
	/usr/share/locale/de
	/usr/share/locale/el
	/usr/share/locale/en
	/usr/share/locale/en_GB
	/usr/share/locale/eo
	/usr/share/locale/es
	/usr/share/locale/et
	/usr/share/locale/et_EE
	/usr/share/locale/eu
	/usr/share/locale/eu_ES
	/usr/share/locale/fi
	/usr/share/locale/fr
	/usr/share/locale/ga
	/usr/share/locale/gl
	/usr/share/locale/gr
	/usr/share/locale/he
	/usr/share/locale/hr
	/usr/share/locale/hu
	/usr/share/locale/id
	/usr/share/locale/is
	/usr/share/locale/it
	/usr/share/locale/ja
	/usr/share/locale/ja_JP.EUC
	/usr/share/locale/ko
	/usr/share/locale/lug
	/usr/share/locale/ms
	/usr/share/locale/nb
	/usr/share/locale/nl
	/usr/share/locale/nn
	/usr/share/locale/no
	/usr/share/locale/pl
	/usr/share/locale/pt
	/usr/share/locale/pt_BR
	/usr/share/locale/ro
	/usr/share/locale/ru
	/usr/share/locale/sk
	/usr/share/locale/sl
	/usr/share/locale/sr
	/usr/share/locale/sv
	/usr/share/locale/tr
	/usr/share/locale/uk
	/usr/share/locale/vi
	/usr/share/locale/wa
	/usr/share/locale/zh_CN
	/usr/share/locale/zh_TW
	#/usr/share/misc/file
	#/usr/share/vim/vim63/doc
	#/usr/share/vim/vim63/syntax
	/etc/skel

livecd/rm:
	/lib/*.a
	/usr/lib/*.a
	/usr/lib/gcc-lib/*/*/libgcj*
	/usr/X11R6/lib/*.a
	/etc/dispatch-conf.conf
	/etc/etc-update.conf
	/etc/*-
	/etc/issue*
	/etc/make.conf
	/etc/man.conf
	/etc/*.old
	/root/.viminfo
	/usr/sbin/bootsplash*
	/usr/sbin/fb*
	/usr/sbin/fsck.cramfs
	/usr/sbin/fsck.minix
	/usr/sbin/mkfs.minix
	/usr/sbin/mkfs.bfs
	/usr/sbin/mkfs.cramfs
	/lib/security/pam_access.so
	/lib/security/pam_chroot.so
	/lib/security/pam_debug.so
	/lib/security/pam_ftp.so
	/lib/security/pam_issue.so
	/lib/security/pam_mail.so
	/lib/security/pam_motd.so
	/lib/security/pam_mkhomedir.so
	/lib/security/pam_postgresok.so
	/lib/security/pam_rhosts_auth.so
	/lib/security/pam_userdb.so
	/usr/share/consolefonts/1*
	/usr/share/consolefonts/7*
	/usr/share/consolefonts/8*
	/usr/share/consolefonts/9*
	/usr/share/consolefonts/A*
	/usr/share/consolefonts/C*
	/usr/share/consolefonts/E*
	/usr/share/consolefonts/G*
	/usr/share/consolefonts/L*
	/usr/share/consolefonts/M*
	/usr/share/consolefonts/R*
	/usr/share/consolefonts/a*
	/usr/share/consolefonts/c*
	/usr/share/consolefonts/dr*
	/usr/share/consolefonts/g*
	/usr/share/consolefonts/i*
	/usr/share/consolefonts/k*
	/usr/share/consolefonts/l*
	/usr/share/consolefonts/r*
	/usr/share/consolefonts/s*
	/usr/share/consolefonts/t*
	/usr/share/consolefonts/v*
	/etc/bootsplash/livecd-2005.0/images/bootsplash-12*
	/etc/bootsplash/livecd-2005.0/images/bootsplash-16*
	/etc/bootsplash/livecd-2005.0/images/bootsplash-8*
	/etc/bootsplash/livecd-2005.0/images/silent-12*
	/etc/bootsplash/livecd-2005.0/images/silent-16*
	/etc/bootsplash/livecd-2005.0/images/silent-8*
	/etc/splash/livecd-2005.0/16*
	/etc/splash/livecd-2005.0/12*
	/etc/splash/livecd-2005.0/6*
	/etc/splash/livecd-2005.0/8*
	/etc/splash/livecd-2005.0/images/silent-16*
	/etc/splash/livecd-2005.0/images/silent-12*
	/etc/splash/livecd-2005.0/images/silent-6*
	/etc/splash/livecd-2005.0/images/silent-8*
	/etc/splash/livecd-2005.0/images/verbose-16*
	/etc/splash/livecd-2005.0/images/verbose-12*
	/etc/splash/livecd-2005.0/images/verbose-6*
	/etc/splash/livecd-2005.0/images/verbose-8*
	/etc/make.conf.example
	/etc/make.globals
	/etc/resolv.conf

[-- Attachment #4: fsscript.sh --]
[-- Type: application/x-sh, Size: 807 bytes --]

Re: [gentoo-catalyst] Problem with NMAP

[Chris Gianelloni]

[-- Attachment #1: Type: text/plain, Size: 849 bytes --]

On Fri, 2005-04-22 at 10:47 +0000, Kosta Todorovic wrote:
> I've tried to add NMAP to the livecd using catalyst but when I try and
> run it it gives the following error:
> nmap: error while loading shared libraries: libstdc++.so.5: cannot
> open shared object file: No such file or directory

Either do not unmerge gcc, or unmask libstdc++-v3 and emerge it during
livecd-stage1.

Normally, we don't need to see your spec files.  You save traffic on the
mailing list by not attaching them until they're requested.  I know that
this is different than in bug reports, where we want as much information
as possible, but mailing lists reach many more users and we still have a
large number of users (and devs) on dial-up.

Thanks!

-- 
Chris Gianelloni
Release Engineering - Strategic Lead/QA Manager
Games - Developer
Gentoo Linux

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-catalyst] Problem with NMAP

[Kosta Todorovic]

Pardon the attachments!

How would i unmask libstdc++-v3? Im not quite sure what you mean? ~x86?



On 4/22/05, Chris Gianelloni <wolf31o2@gentoo.org> wrote:
> On Fri, 2005-04-22 at 10:47 +0000, Kosta Todorovic wrote:
> > I've tried to add NMAP to the livecd using catalyst but when I try and
> > run it it gives the following error:
> > nmap: error while loading shared libraries: libstdc++.so.5: cannot
> > open shared object file: No such file or directory
> 
> Either do not unmerge gcc, or unmask libstdc++-v3 and emerge it during
> livecd-stage1.
> 
> Normally, we don't need to see your spec files.  You save traffic on the
> mailing list by not attaching them until they're requested.  I know that
> this is different than in bug reports, where we want as much information
> as possible, but mailing lists reach many more users and we still have a
> large number of users (and devs) on dial-up.
> 
> Thanks!
> 
> --
> Chris Gianelloni
> Release Engineering - Strategic Lead/QA Manager
> Games - Developer
> Gentoo Linux
> 
> 
>

-- 
gentoo-catalyst@gentoo.org mailing list

Re: [gentoo-catalyst] Problem with NMAP

[Chris Gianelloni]

[-- Attachment #1: Type: text/plain, Size: 1433 bytes --]

On Fri, 2005-04-22 at 11:45 +0000, Kosta Todorovic wrote:
> Pardon the attachments!
> 
> How would i unmask libstdc++-v3? Im not quite sure what you mean? ~x86?

http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=3&chap=3

My suggestion is to unmask the package in your portage tree, then
re-snapshot.  You could also create an overlay with the package
unmasked, then re-snapshot with the overlay, if you're not comfortable
editing your live portage tree.

> On 4/22/05, Chris Gianelloni <wolf31o2@gentoo.org> wrote:
> > On Fri, 2005-04-22 at 10:47 +0000, Kosta Todorovic wrote:
> > > I've tried to add NMAP to the livecd using catalyst but when I try and
> > > run it it gives the following error:
> > > nmap: error while loading shared libraries: libstdc++.so.5: cannot
> > > open shared object file: No such file or directory
> > 
> > Either do not unmerge gcc, or unmask libstdc++-v3 and emerge it during
> > livecd-stage1.
> > 
> > Normally, we don't need to see your spec files.  You save traffic on the
> > mailing list by not attaching them until they're requested.  I know that
> > this is different than in bug reports, where we want as much information
> > as possible, but mailing lists reach many more users and we still have a
> > large number of users (and devs) on dial-up.

-- 
Chris Gianelloni
Release Engineering - Strategic Lead/QA Manager
Games - Developer
Gentoo Linux

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-catalyst] Problem with NMAP

[Kosta Todorovic]

I've actually been using a snapshot or portage from one of the gentoo
mirrors. Is it possible to do it with that?

On 4/22/05, Chris Gianelloni <wolf31o2@gentoo.org> wrote:
> On Fri, 2005-04-22 at 11:45 +0000, Kosta Todorovic wrote:
> > Pardon the attachments!
> >
> > How would i unmask libstdc++-v3? Im not quite sure what you mean? ~x86?
> 
> http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=3&chap=3
> 
> My suggestion is to unmask the package in your portage tree, then
> re-snapshot.  You could also create an overlay with the package
> unmasked, then re-snapshot with the overlay, if you're not comfortable
> editing your live portage tree.
> 
> > On 4/22/05, Chris Gianelloni <wolf31o2@gentoo.org> wrote:
> > > On Fri, 2005-04-22 at 10:47 +0000, Kosta Todorovic wrote:
> > > > I've tried to add NMAP to the livecd using catalyst but when I try and
> > > > run it it gives the following error:
> > > > nmap: error while loading shared libraries: libstdc++.so.5: cannot
> > > > open shared object file: No such file or directory
> > >
> > > Either do not unmerge gcc, or unmask libstdc++-v3 and emerge it during
> > > livecd-stage1.
> > >
> > > Normally, we don't need to see your spec files.  You save traffic on the
> > > mailing list by not attaching them until they're requested.  I know that
> > > this is different than in bug reports, where we want as much information
> > > as possible, but mailing lists reach many more users and we still have a
> > > large number of users (and devs) on dial-up.
> 
> --
> Chris Gianelloni
> Release Engineering - Strategic Lead/QA Manager
> Games - Developer
> Gentoo Linux
> 
> 
>

-- 
gentoo-catalyst@gentoo.org mailing list

Re: [gentoo-catalyst] Problem with NMAP

[Chris Gianelloni]

[-- Attachment #1: Type: text/plain, Size: 934 bytes --]

On Fri, 2005-04-22 at 17:06 +0400, Kosta Todorovic wrote:
> I've actually been using a snapshot or portage from one of the gentoo
> mirrors. Is it possible to do it with that?

Yes.  You just need to follow the second suggestion below.

> 
> On 4/22/05, Chris Gianelloni <wolf31o2@gentoo.org> wrote:
> > On Fri, 2005-04-22 at 11:45 +0000, Kosta Todorovic wrote:
> > > Pardon the attachments!
> > >
> > > How would i unmask libstdc++-v3? Im not quite sure what you mean? ~x86?
> > 
> > http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=3&chap=3
> > 
> > My suggestion is to unmask the package in your portage tree, then
> > re-snapshot.  You could also create an overlay with the package
> > unmasked, then re-snapshot with the overlay, if you're not comfortable
> > editing your live portage tree.

-- 
Chris Gianelloni
Release Engineering - Strategic Lead/QA Manager
Games - Developer
Gentoo Linux

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-catalyst] Problem with NMAP

[Kosta Todorovic]

Could you please explain the last step you descriped? I'm a little lost.

> > >You could also create an overlay with the package
> > > unmasked, then re-snapshot with the overlay, if you're not comfortable
> > > editing your live portage tree.

-- 
gentoo-catalyst@gentoo.org mailing list

Re: [gentoo-catalyst] Problem with NMAP

[Chris Gianelloni]

[-- Attachment #1: Type: text/plain, Size: 984 bytes --]

On Fri, 2005-04-22 at 18:20 +0400, Kosta Todorovic wrote:
> Could you please explain the last step you descriped? I'm a little lost.
> 
> > > >You could also create an overlay with the package
> > > > unmasked, then re-snapshot with the overlay, if you're not comfortable
> > > > editing your live portage tree.

mkdir -p /tmp/overlay/sys-libs
cp -r /usr/portage/sys-libs/libstdc++-v3 /tmp/overlay/sys-libs

Edit the libstdc++-v3 ebuild to remove the package from a masked state.
I am going to assume that you're on x86, so change KEYWORDS from ~x86 to
x86.

catalyst -s 20050422 -C portdir_overlay=/tmp/overlay

You will now have a new portage snapshot created
in /var/tmp/catalyst/snapshots called portage-20050422.tar.bz2 that will
contain your current portage tree + this overlay.

Change your spec files to use snapshot: 20050422

Restart catalyst.

-- 
Chris Gianelloni
Release Engineering - Strategic Lead/QA Manager
Games - Developer
Gentoo Linux

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-catalyst] Problem with NMAP

[Kosta Todorovic]

so:
1. make new snapshot with overlay
2. build stage 1
3. build stage 2
correct?

Will the snapshot be made from my live portage tree?



On 4/22/05, Chris Gianelloni <wolf31o2@gentoo.org> wrote:
> On Fri, 2005-04-22 at 18:20 +0400, Kosta Todorovic wrote:
> > Could you please explain the last step you descriped? I'm a little lost.
> >
> > > > >You could also create an overlay with the package
> > > > > unmasked, then re-snapshot with the overlay, if you're not comfortable
> > > > > editing your live portage tree.
> 
> mkdir -p /tmp/overlay/sys-libs
> cp -r /usr/portage/sys-libs/libstdc++-v3 /tmp/overlay/sys-libs
> 
> Edit the libstdc++-v3 ebuild to remove the package from a masked state.
> I am going to assume that you're on x86, so change KEYWORDS from ~x86 to
> x86.
> 
> catalyst -s 20050422 -C portdir_overlay=/tmp/overlay
> 
> You will now have a new portage snapshot created
> in /var/tmp/catalyst/snapshots called portage-20050422.tar.bz2 that will
> contain your current portage tree + this overlay.
> 
> Change your spec files to use snapshot: 20050422
> 
> Restart catalyst.
> 
> --
> Chris Gianelloni
> Release Engineering - Strategic Lead/QA Manager
> Games - Developer
> Gentoo Linux
> 
> 
>

-- 
gentoo-catalyst@gentoo.org mailing list

Re: [gentoo-catalyst] Problem with NMAP

[Chris Gianelloni]

[-- Attachment #1: Type: text/plain, Size: 652 bytes --]

On Fri, 2005-04-22 at 18:50 +0400, Kosta Todorovic wrote:
> so:
> 1. make new snapshot with overlay
> 2. build stage 1
> 3. build stage 2

If by stage 1 and stage 2 you mean livecd-stage1 and livecd-stage2, then
yes.  It might also be much easier if you specified these, rather than
calling them stage1 and stage2, as there are already stage1 and stage2
targets and it can get a bit confusing.

> correct?
> 
> Will the snapshot be made from my live portage tree?

Yes.  It will be made from your $PORTDIR, wherever that may be.

-- 
Chris Gianelloni
Release Engineering - Strategic Lead/QA Manager
Games - Developer
Gentoo Linux

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-catalyst] Problem with NMAP

[Kosta Todorovic]

> Yes.  It will be made from your $PORTDIR, wherever that may be.

What are the advantages of using the live portage tree rather than a
downloaded snapshot?
Is it possible to use a downloaded snapshot and put an overlay to make
a new snapshot?
Is there any point of doing this?

-- 
gentoo-catalyst@gentoo.org mailing list

Re: [gentoo-catalyst] Problem with NMAP

[derek tracy]

Please correct me if I am wrong, but to solve your problem I would
just create a package.keywords file to unmask libstdc++-v3 in your
portage_conf directory.  Read the examples that get emerged with
catalyst if you need further help I can walk you through it but all
documentation is included with catalyst.

I beleive that the perk to rolling your own portage snapshot is that
you can include your portage_overlay that you have setup on the
computer that you are building the livecd from.

e.g.
I have sys-kernel/love-sources on my host computer's portage overlay
directory and when I roll my own portage snapshot it includes that
along with the normal portage snapshot.

On 4/22/05, Kosta Todorovic <kostodo@gmail.com> wrote:
> > Yes.  It will be made from your $PORTDIR, wherever that may be.
> 
> What are the advantages of using the live portage tree rather than a
> downloaded snapshot?
> Is it possible to use a downloaded snapshot and put an overlay to make
> a new snapshot?
> Is there any point of doing this?
> 
> --
> gentoo-catalyst@gentoo.org mailing list
> 
>

-- 
gentoo-catalyst@gentoo.org mailing list

Re: [gentoo-catalyst] Problem with NMAP

[Kosta Todorovic]

I believe Chris was giving me a solution that meant not modifying my
live portage tree at all. But I guess its not a big deal if i unmask
it in package.keywords. Could even do it temporarily.

On 4/22/05, derek tracy <tracyde@gmail.com> wrote:
> Please correct me if I am wrong, but to solve your problem I would
> just create a package.keywords file to unmask libstdc++-v3 in your
> portage_conf directory.  Read the examples that get emerged with
> catalyst if you need further help I can walk you through it but all
> documentation is included with catalyst.
> 
> I beleive that the perk to rolling your own portage snapshot is that
> you can include your portage_overlay that you have setup on the
> computer that you are building the livecd from.
> 
> e.g.
> I have sys-kernel/love-sources on my host computer's portage overlay
> directory and when I roll my own portage snapshot it includes that
> along with the normal portage snapshot.
> 
> On 4/22/05, Kosta Todorovic <kostodo@gmail.com> wrote:
> > > Yes.  It will be made from your $PORTDIR, wherever that may be.
> >
> > What are the advantages of using the live portage tree rather than a
> > downloaded snapshot?
> > Is it possible to use a downloaded snapshot and put an overlay to make
> > a new snapshot?
> > Is there any point of doing this?
> >
> > --
> > gentoo-catalyst@gentoo.org mailing list
> >
> >
> 
> --
> gentoo-catalyst@gentoo.org mailing list
> 
>

-- 
gentoo-catalyst@gentoo.org mailing list

Re: [gentoo-catalyst] Problem with NMAP

[Chris Gianelloni]

[-- Attachment #1: Type: text/plain, Size: 509 bytes --]

On Fri, 2005-04-22 at 19:03 +0400, Kosta Todorovic wrote:
> > Yes.  It will be made from your $PORTDIR, wherever that may be.
> 
> What are the advantages of using the live portage tree rather than a
> downloaded snapshot?

You know what's in it.

> Is it possible to use a downloaded snapshot and put an overlay to make
> a new snapshot?

No.

> Is there any point of doing this?

No.

-- 
Chris Gianelloni
Release Engineering - Strategic Lead/QA Manager
Games - Developer
Gentoo Linux

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-catalyst] Problem with NMAP

[Chris Gianelloni]

[-- Attachment #1: Type: text/plain, Size: 1241 bytes --]

On Fri, 2005-04-22 at 11:15 -0400, derek tracy wrote:
> Please correct me if I am wrong, but to solve your problem I would
> just create a package.keywords file to unmask libstdc++-v3 in your
> portage_conf directory.  Read the examples that get emerged with
> catalyst if you need further help I can walk you through it but all
> documentation is included with catalyst.

Yeah, your could use portage_conf instead.  It is a directory of files
that follows the same exact syntax/usage as /etc/portage does for a
Gentoo system.

I never use it, because we don't use that option in building official
release media, but it would work just as well.

> I beleive that the perk to rolling your own portage snapshot is that
> you can include your portage_overlay that you have setup on the
> computer that you are building the livecd from.

Correct.

> I have sys-kernel/love-sources on my host computer's portage overlay
> directory and when I roll my own portage snapshot it includes that
> along with the normal portage snapshot.

Eww... love-sources?  I hope you wash your hands after touching that
thing... ;]

-- 
Chris Gianelloni
Release Engineering - Strategic Lead/QA Manager
Games - Developer
Gentoo Linux

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-catalyst] Problem with NMAP

[Chris Gianelloni]

[-- Attachment #1: Type: text/plain, Size: 1334 bytes --]

On Fri, 2005-04-22 at 19:18 +0400, Kosta Todorovic wrote:
> I believe Chris was giving me a solution that meant not modifying my
> live portage tree at all. But I guess its not a big deal if i unmask
> it in package.keywords. Could even do it temporarily.

portage_conf doesn't have to point to *your* /etc/portage, just a
directory with the same layout.  It could point to /tmp/portage or
anywhere else that you wished.

> On 4/22/05, derek tracy <tracyde@gmail.com> wrote:
> > Please correct me if I am wrong, but to solve your problem I would
> > just create a package.keywords file to unmask libstdc++-v3 in your
> > portage_conf directory.  Read the examples that get emerged with
> > catalyst if you need further help I can walk you through it but all
> > documentation is included with catalyst.
> > 
> > I beleive that the perk to rolling your own portage snapshot is that
> > you can include your portage_overlay that you have setup on the
> > computer that you are building the livecd from.
> > 
> > e.g.
> > I have sys-kernel/love-sources on my host computer's portage overlay
> > directory and when I roll my own portage snapshot it includes that
> > along with the normal portage snapshot.

-- 
Chris Gianelloni
Release Engineering - Strategic Lead/QA Manager
Games - Developer
Gentoo Linux

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-catalyst] Problem with NMAP

[Kosta Todorovic]

I've added a portage overlay with a unmasked libstdc++ ebuild and
added libstdc++ to livecd-stage1.spec but when i build livecd-stage1 i
get the following error:

!!! Digest verification Failed:
!!!    /usr/portage/sys-libs/libstdc++-v3/libstdc++-v3-3.3.3-r1.ebuild
!!! Reason: Filesize does not match recorded size







On 4/22/05, Chris Gianelloni <wolf31o2@gentoo.org> wrote:
> On Fri, 2005-04-22 at 19:18 +0400, Kosta Todorovic wrote:
> > I believe Chris was giving me a solution that meant not modifying my
> > live portage tree at all. But I guess its not a big deal if i unmask
> > it in package.keywords. Could even do it temporarily.
> 
> portage_conf doesn't have to point to *your* /etc/portage, just a
> directory with the same layout.  It could point to /tmp/portage or
> anywhere else that you wished.
> 
> > On 4/22/05, derek tracy <tracyde@gmail.com> wrote:
> > > Please correct me if I am wrong, but to solve your problem I would
> > > just create a package.keywords file to unmask libstdc++-v3 in your
> > > portage_conf directory.  Read the examples that get emerged with
> > > catalyst if you need further help I can walk you through it but all
> > > documentation is included with catalyst.
> > >
> > > I beleive that the perk to rolling your own portage snapshot is that
> > > you can include your portage_overlay that you have setup on the
> > > computer that you are building the livecd from.
> > >
> > > e.g.
> > > I have sys-kernel/love-sources on my host computer's portage overlay
> > > directory and when I roll my own portage snapshot it includes that
> > > along with the normal portage snapshot.
> 
> --
> Chris Gianelloni
> Release Engineering - Strategic Lead/QA Manager
> Games - Developer
> Gentoo Linux
> 
> 
>

-- 
gentoo-catalyst@gentoo.org mailing list

Re: [gentoo-catalyst] Problem with NMAP

[Robert Paskowitz]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

You need to 'ebuild libstdc++-v3-3.3.3-r1.ebuild digest' to create a new
Manifest file. This will have to be done before any catalyst stuff, in
the directory with the ebuild, and the base directory should be in your
make.conf's PORTDIR_OVERLAY.

Or, you could export FEATURES="-strict" in your catalyst envs to lower
the amount of verification performed, but I recommend the first method.

Robert

Kosta Todorovic wrote:
> I've added a portage overlay with a unmasked libstdc++ ebuild and
> added libstdc++ to livecd-stage1.spec but when i build livecd-stage1 i
> get the following error:
> 
> !!! Digest verification Failed:
> !!!    /usr/portage/sys-libs/libstdc++-v3/libstdc++-v3-3.3.3-r1.ebuild
> !!! Reason: Filesize does not match recorded size
> 
> 
> 
> 
> 
> 
> 
> On 4/22/05, Chris Gianelloni <wolf31o2@gentoo.org> wrote:
> 
>>On Fri, 2005-04-22 at 19:18 +0400, Kosta Todorovic wrote:
>>
>>>I believe Chris was giving me a solution that meant not modifying my
>>>live portage tree at all. But I guess its not a big deal if i unmask
>>>it in package.keywords. Could even do it temporarily.
>>
>>portage_conf doesn't have to point to *your* /etc/portage, just a
>>directory with the same layout.  It could point to /tmp/portage or
>>anywhere else that you wished.
>>
>>
>>>On 4/22/05, derek tracy <tracyde@gmail.com> wrote:
>>>
>>>>Please correct me if I am wrong, but to solve your problem I would
>>>>just create a package.keywords file to unmask libstdc++-v3 in your
>>>>portage_conf directory.  Read the examples that get emerged with
>>>>catalyst if you need further help I can walk you through it but all
>>>>documentation is included with catalyst.
>>>>
>>>>I beleive that the perk to rolling your own portage snapshot is that
>>>>you can include your portage_overlay that you have setup on the
>>>>computer that you are building the livecd from.
>>>>
>>>>e.g.
>>>>I have sys-kernel/love-sources on my host computer's portage overlay
>>>>directory and when I roll my own portage snapshot it includes that
>>>>along with the normal portage snapshot.
>>
>>--
>>Chris Gianelloni
>>Release Engineering - Strategic Lead/QA Manager
>>Games - Developer
>>Gentoo Linux
>>
>>
>>
> 
> 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (Darwin)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFCbJdzZwjIiODIZ4oRAulHAJ42NxgPSHBrGxnnE5LfqWWViTLVuwCeJkM6
JZ9sGiqhjB3vhCUI+IwGrMU=
=E/sS
-----END PGP SIGNATURE-----
-- 
gentoo-catalyst@gentoo.org mailing list

Re: [gentoo-catalyst] Problem with NMAP

[Kosta Todorovic]

so make.conf needs to have:
PORTAGE_OVERLAY=/tmp/overlay

where /tmp/overlay is my portage overlay. correct?



On 4/25/05, Robert Paskowitz <r2d2@gentoo.org> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> You need to 'ebuild libstdc++-v3-3.3.3-r1.ebuild digest' to create a new
> Manifest file. This will have to be done before any catalyst stuff, in
> the directory with the ebuild, and the base directory should be in your
> make.conf's PORTDIR_OVERLAY.
> 
> Or, you could export FEATURES="-strict" in your catalyst envs to lower
> the amount of verification performed, but I recommend the first method.
> 
> Robert
> 
> Kosta Todorovic wrote:
> > I've added a portage overlay with a unmasked libstdc++ ebuild and
> > added libstdc++ to livecd-stage1.spec but when i build livecd-stage1 i
> > get the following error:
> >
> > !!! Digest verification Failed:
> > !!!    /usr/portage/sys-libs/libstdc++-v3/libstdc++-v3-3.3.3-r1.ebuild
> > !!! Reason: Filesize does not match recorded size
> >
> >
> >
> >
> >
> >
> >
> > On 4/22/05, Chris Gianelloni <wolf31o2@gentoo.org> wrote:
> >
> >>On Fri, 2005-04-22 at 19:18 +0400, Kosta Todorovic wrote:
> >>
> >>>I believe Chris was giving me a solution that meant not modifying my
> >>>live portage tree at all. But I guess its not a big deal if i unmask
> >>>it in package.keywords. Could even do it temporarily.
> >>
> >>portage_conf doesn't have to point to *your* /etc/portage, just a
> >>directory with the same layout.  It could point to /tmp/portage or
> >>anywhere else that you wished.
> >>
> >>
> >>>On 4/22/05, derek tracy <tracyde@gmail.com> wrote:
> >>>
> >>>>Please correct me if I am wrong, but to solve your problem I would
> >>>>just create a package.keywords file to unmask libstdc++-v3 in your
> >>>>portage_conf directory.  Read the examples that get emerged with
> >>>>catalyst if you need further help I can walk you through it but all
> >>>>documentation is included with catalyst.
> >>>>
> >>>>I beleive that the perk to rolling your own portage snapshot is that
> >>>>you can include your portage_overlay that you have setup on the
> >>>>computer that you are building the livecd from.
> >>>>
> >>>>e.g.
> >>>>I have sys-kernel/love-sources on my host computer's portage overlay
> >>>>directory and when I roll my own portage snapshot it includes that
> >>>>along with the normal portage snapshot.
> >>
> >>--
> >>Chris Gianelloni
> >>Release Engineering - Strategic Lead/QA Manager
> >>Games - Developer
> >>Gentoo Linux
> >>
> >>
> >>
> >
> >
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.4 (Darwin)
> Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
> 
> iD8DBQFCbJdzZwjIiODIZ4oRAulHAJ42NxgPSHBrGxnnE5LfqWWViTLVuwCeJkM6
> JZ9sGiqhjB3vhCUI+IwGrMU=
> =E/sS
> -----END PGP SIGNATURE-----
> --
> gentoo-catalyst@gentoo.org mailing list
> 
>

-- 
gentoo-catalyst@gentoo.org mailing list

Re: [gentoo-catalyst] Problem with NMAP

[Ryan Lynch]

Yea, this has to do with a big change in portage.  IMHO, the need to put out an announcement when they make such a big change.  When you make a change like this, you know there are going to be a bunch of ebuilds that have incorrect/incomplete manifests that have gone unnoticed, and are going to be giving everybody problems.  But instead of making an official announcement about the change, they keep the information almost hidden from most people, and have caused myself and others considerable frustration.  I'm just annoyed thats all, because I'm using catalyst and other meathods to build some install media, and I ran into a bunch of these bad manifest errors before I was told about the change in portage.  Just my two cents.

On Mon, 25 Apr 2005 03:08:35 -0400
Robert Paskowitz <r2d2@gentoo.org> wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> You need to 'ebuild libstdc++-v3-3.3.3-r1.ebuild digest' to create a new
> Manifest file. This will have to be done before any catalyst stuff, in
> the directory with the ebuild, and the base directory should be in your
> make.conf's PORTDIR_OVERLAY.
> 
> Or, you could export FEATURES="-strict" in your catalyst envs to lower
> the amount of verification performed, but I recommend the first method.
> 
> Robert
-- 
gentoo-catalyst@gentoo.org mailing list