I added a patch to cdrtools that allows burning CDs with AES encryption. This patch needs sys-fs/cryptsetup. Your arch isn't added yet, so there is a RDEPEND-issue with cdrtools and the crypt-USE-flag set. Please test sys-fs/cryptsetup and add your arch (~ would suffice).
How the heck did this get commited to the tree? Your commit managed to break deps on nine different archs. Repoman spits those errors out for a reason, in the future please get the archs involved before commiting, not afterwards.
Created attachment 52404 [details] compile output on ppc64 this won't compile on ppc64. $ emerge --info Portage 2.0.51-r15 (default-linux/ppc64/2005.0, gcc-3.4.3, glibc-2.3.4.20041102-r0, 2.6.9-gentoo-r9 ppc64) ================================================================= System uname: 2.6.9-gentoo-r9 ppc64 PPC970, altivec supported Gentoo Base System version 1.6.9 Python: dev-lang/python-2.3.3-r2 [2.3.3 (#1, Feb 7 2005, 19:24:34)] dev-lang/python: 2.3.3-r2 sys-devel/autoconf: 2.13, 2.59-r6 sys-devel/automake: 1.5, 1.8.5-r3, 1.6.3, 1.7.9-r1, 1.4_p6, 1.9.4 sys-devel/binutils: 2.15.90.0.3-r3 sys-devel/libtool: 1.5.10-r4 virtual/os-headers: 2.6.8.1-r2 ACCEPT_KEYWORDS="ppc64" AUTOCLEAN="yes" CFLAGS="-mcpu=G5 -O3 -pipe -fsigned-char -mabi=altivec" CHOST="powerpc64-unknown-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.3/env /usr/kde/3.3/share/config /usr/kde/3.3/shutdown /usr/kde/3.4/env /usr/kde/3.4/share/config /usr/kde/3.4/shutdown /usr/kde/3/share/config /usr/lib/X11/xkb /usr/share/config /usr/share/texmf/dvipdfm/config/ /usr/share/texmf/dvips/config/ /usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/ /usr/share/texmf/xdvi/ /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-mcpu=G5 -O3 -pipe -fsigned-char -mabi=altivec" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs autoconfig ccache cvs distlocks sandbox sfperms" GENTOO_MIRRORS="http://linux.rz.ruhr-uni-bochum.de/download/gentoo-mirror/ http://ftp-stud.fht-esslingen.de/pub/Mirrors/gentoo/" MAKEOPTS="-j3" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="X aalib alsa altivec apache2 bcmath berkdb bitmap-fonts bzip2 bzlib calendar cdb cdparanoia cdr cdrom chroot client crypt cups curl dba dedicated dga dict dio divx4linux dv dvd dvdr dvdread encode exif fam fame fbcon ffmpeg flac flatfile fortran fpx freetype ftp gcc-libffi gd gdbm gif gimp gimpprint glade gnuplot gnustep gpm graphviz gs gstreamer gtk gtk2 iconv icq ieee1394 image imagemagick imap imlib imlib2 ipv6 ipv6arpa jabber jack java javacomm javamail javascript jbig jpeg jpeg2k kerberos latex ldap libwww live mad maildir md5sum mhash mikmod mime mimencode mixer mjpeg mng motif mozsvg mp3 mpeg mpeg4 mpi music mysql native ncurses neXt nls nocardbus nowin nptl nptlonly objc oggvorbis openal opengl openssh pam pdf pdflib perl php physfs plotutils png pnp portaudio posix ppc64 procmail python qt quicktime quotas quotes radius readline rtc samba sasl sdk sdl serial server session silc slang smime sndfile sockets sounds spell ssl svg tcpd tetex tga theora tidy tiff tools transcode truetype truetype-fonts type1-fonts uml unicode uptimed usb v4l v4l2 vcd vhosts videos vidix vim wmf wxwindows xanim xchatdccserver xchattext xine xml2 xmms xosd xpm xprint xscreensaver xsl xv xvid xvmc zlib" Unset: ASFLAGS, CBUILD, CTARGET, LANG, LC_ALL, LDFLAGS, PORTDIR_OVERLAY $
in the future, if you're going to force arches to test crap, could not force us to test crappy ebuilds ? ive cleaned it up and added arm/hppa/ia64/s390 ... it still kind of sucks, but not nearly as much now
~sparc'ed
~alpha keyworded.
I recently changed the
I recently changed the crypt USE-flag in cdrtools-2.01-r3 into on-the-fly-crypt. As there are architectures where cryptsetup fails to build (ppc64 for sure), they can now easily mask that USE-flag and go further with a newer version of cdrtools. I would like to clean out app-cdr/cdrtools-2.01-r1. Could you please test on your arch and mask cdrtools-2.01-r3 stable?
Works on ppc64. -r3 stable now.
device-mapper, a dependency of cryptsetup is linux-specific. Thus, it's not going to work for ppc-macos. Masking "on-the-fly-crypt" for ppc-macos.
Added ~mips to sys-fs/device-mapper and sys-fs/cryptsetup.
alpha team can you guys please test and keyword as apropriate cdrtools so we can close this bug? Thanks
kloeri did this one long time ago, he just forgot to close this bug. Cheers, Ferdy