All recent updates to sys-fs/aufs3 with kernel-patch enables fail because kernel patching fail. * Messages for package sys-fs/aufs3-3_p20140127: * It seems you are using gentoo-sources with aufs3 * Please use sys-kernel/aufs-sources * This will save you the nasty reemerge of sys-fs/aufs3 on every kernel upgrade * Patching your kernel... * Failed Patch: aufs3-standalone-base-mmap-combined.patch ! * ( /var/tmp/portage/sys-fs/aufs3-3_p20140127/temp/aufs3-standalone/aufs3-standalone-base-mmap-combined.patch ) * * Include in your bugreport the contents of: * * /var/tmp/portage/sys-fs/aufs3-3_p20140127/temp/aufs3-standalone-base-mmap-combined.patch.out * ERROR: sys-fs/aufs3-3_p20140127::gentoo failed (setup phase): * Failed Patch: aufs3-standalone-base-mmap-combined.patch! Reproducible: Always Steps to Reproduce: 1. System has gentoo-sources and aufs3-3_p20140114 (with ~amd64) with kernel-patch USE flag 2. run emerge -uqDN world to update to latest version Actual Results: update fails Expected Results: update succeeds Content of /var/tmp/portage/sys-fs/aufs3-3_p20140127/temp/aufs3-standalone-base-mmap-combined.patch.out: ***** aufs3-standalone-base-mmap-combined.patch ***** PWD: /usr/src/linux ===================================================== PATCH COMMAND: patch -p0 -g0 -E --no-backup-if-mismatch < '/var/tmp/portage/sys-fs/aufs3-3_p20140127/temp/aufs3-standalone/aufs3-standalone-base-mmap-combined.patch' ===================================================== can't find file to patch at input line 4 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |unchanged: |--- b/fs/file_table.c |+++ b/fs/file_table.c -------------------------- No file to patch. Skipping patch. 2 out of 2 hunks ignored can't find file to patch at input line 26 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |unchanged: |--- b/fs/inode.c |+++ b/fs/inode.c -------------------------- No file to patch. Skipping patch. 3 out of 3 hunks ignored can't find file to patch at input line 54 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |unchanged: |--- b/fs/splice.c |+++ b/fs/splice.c -------------------------- No file to patch. Skipping patch. 3 out of 3 hunks ignored can't find file to patch at input line 94 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |unchanged: |--- a/include/linux/fs.h |+++ b/include/linux/fs.h -------------------------- No file to patch. Skipping patch. 1 out of 1 hunk ignored can't find file to patch at input line 105 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |unchanged: |--- a/include/linux/splice.h |+++ b/include/linux/splice.h -------------------------- No file to patch. Skipping patch. 1 out of 1 hunk ignored can't find file to patch at input line 119 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |unchanged: |--- a/fs/namespace.c |+++ b/fs/namespace.c -------------------------- No file to patch. Skipping patch. 3 out of 3 hunks ignored can't find file to patch at input line 146 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |unchanged: |--- a/fs/notify/group.c |+++ b/fs/notify/group.c -------------------------- No file to patch. Skipping patch. 4 out of 4 hunks ignored can't find file to patch at input line 181 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |unchanged: |--- a/fs/notify/mark.c |+++ b/fs/notify/mark.c -------------------------- No file to patch. Skipping patch. 4 out of 4 hunks ignored can't find file to patch at input line 216 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |unchanged: |--- a/fs/open.c |+++ b/fs/open.c -------------------------- No file to patch. Skipping patch. 1 out of 1 hunk ignored can't find file to patch at input line 227 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |unchanged: |--- a/security/commoncap.c |+++ b/security/commoncap.c -------------------------- No file to patch. Skipping patch. 1 out of 1 hunk ignored can't find file to patch at input line 242 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |unchanged: |--- a/security/device_cgroup.c |+++ b/security/device_cgroup.c -------------------------- No file to patch. Skipping patch. 2 out of 2 hunks ignored can't find file to patch at input line 261 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |unchanged: |--- a/security/security.c |+++ b/security/security.c -------------------------- No file to patch. Skipping patch. 10 out of 10 hunks ignored can't find file to patch at input line 345 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |only in patch2: |unchanged: |--- a/fs/buffer.c |+++ b/fs/buffer.c -------------------------- No file to patch. Skipping patch. 1 out of 1 hunk ignored can't find file to patch at input line 358 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |only in patch2: |unchanged: |--- a/fs/proc/nommu.c |+++ b/fs/proc/nommu.c -------------------------- No file to patch. Skipping patch. 1 out of 1 hunk ignored can't find file to patch at input line 373 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |only in patch2: |unchanged: |--- a/fs/proc/task_mmu.c |+++ b/fs/proc/task_mmu.c -------------------------- No file to patch. Skipping patch. 2 out of 2 hunks ignored can't find file to patch at input line 396 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |only in patch2: |unchanged: |--- a/fs/proc/task_nommu.c |+++ b/fs/proc/task_nommu.c -------------------------- No file to patch. Skipping patch. 1 out of 1 hunk ignored can't find file to patch at input line 411 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |only in patch2: |unchanged: |--- a/include/linux/mm.h |+++ b/include/linux/mm.h -------------------------- No file to patch. Skipping patch. 2 out of 2 hunks ignored can't find file to patch at input line 513 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |only in patch2: |unchanged: |--- a/include/linux/mm_types.h |+++ b/include/linux/mm_types.h -------------------------- No file to patch. Skipping patch. 2 out of 2 hunks ignored can't find file to patch at input line 533 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |only in patch2: |unchanged: |--- a/kernel/fork.c |+++ b/kernel/fork.c -------------------------- No file to patch. Skipping patch. 1 out of 1 hunk ignored can't find file to patch at input line 546 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |only in patch2: |unchanged: |--- a/mm/filemap.c |+++ b/mm/filemap.c -------------------------- No file to patch. Skipping patch. 1 out of 1 hunk ignored can't find file to patch at input line 559 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |only in patch2: |unchanged: |--- a/mm/fremap.c |+++ b/mm/fremap.c -------------------------- No file to patch. Skipping patch. 1 out of 1 hunk ignored can't find file to patch at input line 573 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |only in patch2: |unchanged: |--- a/mm/madvise.c |+++ b/mm/madvise.c -------------------------- No file to patch. Skipping patch. 1 out of 1 hunk ignored can't find file to patch at input line 592 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |only in patch2: |unchanged: |--- a/mm/memory.c |+++ b/mm/memory.c -------------------------- No file to patch. Skipping patch. 2 out of 2 hunks ignored can't find file to patch at input line 614 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |only in patch2: |unchanged: |--- a/mm/mmap.c |+++ b/mm/mmap.c -------------------------- No file to patch. Skipping patch. 6 out of 6 hunks ignored can't find file to patch at input line 673 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |only in patch2: |unchanged: |--- a/mm/msync.c |+++ b/mm/msync.c -------------------------- No file to patch. Skipping patch. 1 out of 1 hunk ignored can't find file to patch at input line 690 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |only in patch2: |unchanged: |--- a/mm/nommu.c |+++ b/mm/nommu.c -------------------------- No file to patch. Skipping patch. 4 out of 4 hunks ignored patch program exited with status 1 ===================================================== PATCH COMMAND: patch -p1 -g0 -E --no-backup-if-mismatch < '/var/tmp/portage/sys-fs/aufs3-3_p20140127/temp/aufs3-standalone/aufs3-standalone-base-mmap-combined.patch' ===================================================== patching file fs/file_table.c patching file fs/inode.c patching file fs/splice.c patching file include/linux/fs.h patching file include/linux/splice.h patching file fs/namespace.c patching file fs/notify/group.c patching file fs/notify/mark.c patching file fs/open.c patching file security/commoncap.c patching file security/device_cgroup.c patching file security/security.c patching file fs/buffer.c patching file fs/proc/nommu.c patching file fs/proc/task_mmu.c patching file fs/proc/task_nommu.c patching file include/linux/mm.h patching file include/linux/mm_types.h patching file kernel/fork.c patching file mm/filemap.c patching file mm/fremap.c Hunk #1 FAILED at 206.
Created attachment 369108 [details] Patching output
Please post your `emerge --info' output in a comment.
$ emerge --info Portage 2.2.7 (default/linux/amd64/13.0/desktop/gnome/systemd, gcc-4.7.3, glibc-2.17, 3.10.25-gentoo x86_64) ================================================================= System uname: Linux-3.10.25-gentoo-x86_64-Intel-R-_Core-TM-_i5-3320M_CPU_@_2.60GHz-with-gentoo-2.2 KiB Mem: 7869556 total, 4188976 free KiB Swap: 4194300 total, 4194300 free Timestamp of tree: Thu, 30 Jan 2014 08:00:01 +0000 ld GNU ld (GNU Binutils) 2.23.2 app-shells/bash: 4.2_p45 dev-java/java-config: 2.1.12-r1 dev-lang/python: 2.7.5-r3, 3.3.3 dev-util/cmake: 2.8.11.2 dev-util/pkgconfig: 0.28 sys-apps/baselayout: 2.2 sys-apps/openrc: 0.12.4 sys-apps/sandbox: 2.6-r1 sys-devel/autoconf: 2.13, 2.69 sys-devel/automake: 1.11.6, 1.13.4 sys-devel/binutils: 2.23.2 sys-devel/gcc: 4.7.3-r1 sys-devel/gcc-config: 1.7.3 sys-devel/libtool: 2.4.2 sys-devel/make: 3.82-r4 sys-kernel/linux-headers: 3.9 (virtual/os-headers) sys-libs/glibc: 2.17 Repositories: gentoo ACCEPT_KEYWORDS="amd64" ACCEPT_LICENSE="* -@EULA" CBUILD="x86_64-pc-linux-gnu" CFLAGS="-march=native -O2 -pipe" CHOST="x86_64-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/share/config /usr/share/gnupg/qualified.txt" CONFIG_PROTECT_MASK="/etc/ca-certificates.conf /etc/dconf /etc/env.d /etc/fonts/fonts.conf /etc/gconf /etc/gentoo-release /etc/revdep-rebuild /etc/sandbox.d /etc/terminfo" CXXFLAGS="-march=native -O2 -pipe" DISTDIR="/usr/portage/distfiles" FCFLAGS="-O2 -pipe" FEATURES="assume-digests binpkg-logs config-protect-if-modified distlocks ebuild-locks fixlafiles merge-sync news parallel-fetch preserve-libs protect-owned sandbox sfperms strict unknown-features-warn unmerge-logs unmerge-orphans userfetch userpriv usersandbox usersync" FFLAGS="-O2 -pipe" GENTOO_MIRRORS="ftp://ftp.free.fr/mirrors/ftp.gentoo.org/ http://mirror.ovh.net/gentoo-distfiles/ ftp://mirrors.linuxant.fr/distfiles.gentoo.org/" LANG="en_US.utf8" LDFLAGS="-Wl,-O1 -Wl,--as-needed" MAKEOPTS="-j4" PKGDIR="/usr/portage/packages" PORTAGE_CONFIGROOT="/" PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --omit-dir-times --compress --force --whole-file --delete --stats --human-readable --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="X a52 aac acl acpi alsa amd64 berkdb bindist bluetooth branding bzip2 cairo cdda cdr cli colord cracklib crypt cups cxx dbus dri dts dvd dvdr eds emboss encode evo exif fam firefox flac fortran gdbm gif gnome gnome-keyring gnome-online-accounts gpm gstreamer gtk iconv introspection ipv6 jpeg lcms ldap libnotify libsecret mad mmx mng modules mp3 mp4 mpeg multilib nautilus ncurses nls nptl ogg opengl openmp pam pango pcre pdf png policykit ppds pulseaudio qt3support qt4 readline sdl session socialweb spell sse sse2 ssl startup-notification svg systemd tcpd tiff truetype udev udisks unicode upower usb vorbis wxwidgets x264 xcb xml xv xvid zlib" ABI_X86="64" ALSA_CARDS="ali5451 als4000 atiixp atiixp-modem bt87x ca0106 cmipci emu10k1x ens1370 ens1371 es1938 es1968 fm801 hda-intel intel8x0 intel8x0m maestro3 trident usb-audio via82xx via82xx-modem ymfpci" APACHE2_MODULES="authn_core authz_core socache_shmcb unixd actions alias auth_basic authn_alias authn_anon authn_dbm authn_default authn_file authz_dbm authz_default authz_groupfile authz_host authz_owner authz_user autoindex cache cgi cgid dav dav_fs dav_lock deflate dir disk_cache env expires ext_filter file_cache filter headers include info log_config logio mem_cache mime mime_magic negotiation rewrite setenvif speling status unique_id userdir usertrack vhost_alias" CALLIGRA_FEATURES="kexi words flow plan sheets stage tables krita karbon braindump author" CAMERAS="ptp2" COLLECTD_PLUGINS="df interface irq load memory rrdtool swap syslog" ELIBC="glibc" GPSD_PROTOCOLS="ashtech aivdm earthmate evermore fv18 garmin garmintxt gpsclock itrax mtk3301 nmea ntrip navcom oceanserver oldstyle oncore rtcm104v2 rtcm104v3 sirf superstar2 timing tsip tripmate tnt ublox ubx" INPUT_DEVICES="evdev synaptics" KERNEL="linux" LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text" LIBREOFFICE_EXTENSIONS="presenter-console presenter-minimizer" OFFICE_IMPLEMENTATION="libreoffice" PHP_TARGETS="php5-5" PYTHON_SINGLE_TARGET="python2_7" PYTHON_TARGETS="python2_7 python3_3" RUBY_TARGETS="ruby19 ruby18" USERLAND="GNU" VIDEO_CARDS="intel i915" XTABLES_ADDONS="quota2 psd pknock lscan length2 ipv4options ipset ipp2p iface geoip fuzzy condition tee tarpit sysrq steal rawnat logmark ipmark dhcpmac delude chaos account" Unset: CPPFLAGS, CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LC_ALL, PORTAGE_BUNZIP2_COMMAND, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS, USE_PYTHON
Which kernel?
I am using the up-to-date gentoo-sources: pelvoux sylvain # eselect kernel list Available kernel symlink targets: [1] linux-3.10.25-gentoo *
(In reply to Sylvain Chevalier from comment #5) > I am using the up-to-date gentoo-sources: if you use gentoo-sources you can simply switch to aufs-sources and is should work. > > pelvoux sylvain # eselect kernel list > Available kernel symlink targets: > [1] linux-3.10.25-gentoo * Upstream has a bug report for this version and latest aufs3. You should be careful.
Hi, Same here with gentoo-sources-3.10.25 bug occurs since version 3_p20140119 version 3_p20140114 installs ok For patch oputput see attachment: https://bugs.gentoo.org/attachment.cgi?id=369108 Regards Massimo. Outputs: emerge -auDtvN world These are the packages that would be merged, in reverse order: Calculating dependencies... done! [ebuild U ~] sys-fs/aufs3-3_p20140127 [3_p20140114] USE="fuse inotify kernel-patch ramfs -debug -doc -hfs -nfs -pax_kernel" 0 kB Total: 1 package (1 upgrade), Size of downloads: 0 kB >>> Verifying ebuild manifests >>> Emerging (1 of 1) sys-fs/aufs3-3_p20140127 >>> Jobs: 0 of 1 complete, 1 running Load avg: 1.64, 1.19, 1.30openpty failed: 'out of pty devices' >>> Failed to emerge sys-fs/aufs3-3_p20140127, Log file: >>> '/var/tmp/portage/sys-fs/aufs3-3_p20140127/temp/build.log' >>> Jobs: 0 of 1 complete, 1 failed Load avg: 2.07, 1.30, 1.34 * Package: sys-fs/aufs3-3_p20140127 * Repository: gentoo * Maintainer: jlec@gentoo.org * USE: elibc_glibc fuse inotify kernel-patch kernel_linux ramfs userland_GNU x86 * FEATURES: preserve-libs sandbox userpriv usersandbox * Determining the location of the kernel source code * Found kernel source directory: * /usr/src/linux * Found kernel object directory: * /lib/modules/3.10.25-gentoo/build * Found sources for kernel version: * 3.10.25-gentoo * Checking for suitable kernel configuration options... [ ok ] * It seems you are using gentoo-sources with aufs3 * Please use sys-kernel/aufs-sources * This will save you the nasty reemerge of sys-fs/aufs3 on every kernel upgrade >>> Unpacking aufs3-standalone-3_p20140127.tar.xz to /var/tmp/portage/sys-fs/aufs3-3_p20140127/temp * Patching your kernel... * Applying aufs3-standalone-base-mmap-combined.patch ... * Failed Patch: aufs3-standalone-base-mmap-combined.patch ! * ( /var/tmp/portage/sys-fs/aufs3-3_p20140127/temp/aufs3-standalone/aufs3-standalone-base-mmap-combined.patch ) * * Include in your bugreport the contents of: * * /var/tmp/portage/sys-fs/aufs3-3_p20140127/temp/aufs3-standalone-base-mmap-combined.patch.out * ERROR: sys-fs/aufs3-3_p20140127::gentoo failed (setup phase): * Failed Patch: aufs3-standalone-base-mmap-combined.patch! * * Call stack: * ebuild.sh, line 93: Called pkg_setup * aufs3-3_p20140127.ebuild, line 88: Called epatch '/var/tmp/portage/sys-fs/aufs3-3_p20140127/temp/aufs3-standalone/aufs3-standalone-base-mmap-combined.patch' * eutils.eclass, line 638: Called die * The specific snippet of code: * die "Failed Patch: ${patchname}!" * * If you need support, post the output of `emerge --info '=sys-fs/aufs3-3_p20140127::gentoo'`, * the complete build log and the output of `emerge -pqv '=sys-fs/aufs3-3_p20140127::gentoo'`. * The complete build log is located at '/var/tmp/portage/sys-fs/aufs3-3_p20140127/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/sys-fs/aufs3-3_p20140127/temp/die.env'. * Working directory: '/usr/src/linux' * S: '/var/tmp/portage/sys-fs/aufs3-3_p20140127/work/aufs3-standalone' * Messages for package sys-fs/aufs3-3_p20140127: * It seems you are using gentoo-sources with aufs3 * Please use sys-kernel/aufs-sources * This will save you the nasty reemerge of sys-fs/aufs3 on every kernel upgrade * Patching your kernel... * Failed Patch: aufs3-standalone-base-mmap-combined.patch ! * ( /var/tmp/portage/sys-fs/aufs3-3_p20140127/temp/aufs3-standalone/aufs3-standalone-base-mmap-combined.patch ) * * Include in your bugreport the contents of: * * /var/tmp/portage/sys-fs/aufs3-3_p20140127/temp/aufs3-standalone-base-mmap-combined.patch.out * ERROR: sys-fs/aufs3-3_p20140127::gentoo failed (setup phase): * Failed Patch: aufs3-standalone-base-mmap-combined.patch! * * Call stack: * ebuild.sh, line 93: Called pkg_setup * aufs3-3_p20140127.ebuild, line 88: Called epatch '/var/tmp/portage/sys-fs/aufs3-3_p20140127/temp/aufs3-standalone/aufs3-standalone-base-mmap-combined.patch' * eutils.eclass, line 638: Called die * The specific snippet of code: * die "Failed Patch: ${patchname}!" * * If you need support, post the output of `emerge --info '=sys-fs/aufs3-3_p20140127::gentoo'`, * the complete build log and the output of `emerge -pqv '=sys-fs/aufs3-3_p20140127::gentoo'`. * The complete build log is located at '/var/tmp/portage/sys-fs/aufs3-3_p20140127/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/sys-fs/aufs3-3_p20140127/temp/die.env'. * Working directory: '/usr/src/linux' * S: '/var/tmp/portage/sys-fs/aufs3-3_p20140127/work/aufs3-standalone' * * The following package has failed to build or install: * * (sys-fs/aufs3-3_p20140127::gentoo, ebuild scheduled for merge), Log file: * '/var/tmp/portage/sys-fs/aufs3-3_p20140127/temp/build.log' * emerge --info: Portage 2.2.7 (default/linux/x86/13.0, gcc-4.7.3, glibc-2.17, 3.10.25-gentoo i686) ================================================================= System uname: Linux-3.10.25-gentoo-i686-Intel-R-_Core-TM-_i5_CPU_M_520_@_2.40GHz-with-gentoo-2.2 KiB Mem: 8164964 total, 1745992 free KiB Swap: 8389628 total, 8389628 free Timestamp of tree: Tue, 04 Feb 2014 10:30:01 +0000 ld ld di GNU (GNU Binutils) 2.23.2 app-shells/bash: 4.2_p45 dev-lang/python: 2.7.5-r3, 3.3.3 dev-util/cmake: 2.8.11.2 dev-util/pkgconfig: 0.28 sys-apps/baselayout: 2.2 sys-apps/openrc: 0.12.4 sys-apps/sandbox: 2.6-r1 sys-devel/autoconf: 2.13, 2.69 sys-devel/automake: 1.11.6, 1.13.4 sys-devel/binutils: 2.23.2 sys-devel/gcc: 4.7.3-r1 sys-devel/gcc-config: 1.7.3 sys-devel/libtool: 2.4.2 sys-devel/make: 3.82-r4 sys-kernel/linux-headers: 3.9 (virtual/os-headers) sys-libs/glibc: 2.17 Repositories: gentoo ACCEPT_KEYWORDS="x86" ACCEPT_LICENSE="*" CBUILD="i686-pc-linux-gnu" CFLAGS="-march=k8-sse3 -O2 -fomit-frame-pointer -pipe" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/share/gnupg/qualified.txt" CONFIG_PROTECT_MASK="/etc/ca-certificates.conf /etc/env.d /etc/fonts/fonts.conf /etc/gconf /etc/gentoo-release /etc/revdep-rebuild /etc/sandbox.d /etc/splash /etc/terminfo" CXXFLAGS="-march=k8-sse3 -O2 -fomit-frame-pointer -pipe" DISTDIR="/usr/portage/distfiles" EMERGE_DEFAULT_OPTS="--autounmask=n" FCFLAGS="-O2 -march=i686 -pipe" FEATURES="assume-digests binpkg-logs config-protect-if-modified distlocks ebuild-locks fixlafiles merge-sync news parallel-fetch preserve-libs protect-owned sandbox sfperms strict unknown-features-warn unmerge-logs unmerge-orphans userfetch userpriv usersandbox usersync" FFLAGS="-O2 -march=i686 -pipe" GENTOO_MIRRORS="http://distfiles.gentoo.org" LANG="it_IT.utf8" LDFLAGS="-Wl,-O1 -Wl,--as-needed" MAKEOPTS="-j6" PKGDIR="/usr/portage/packages" PORTAGE_CONFIGROOT="/" PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --omit-dir-times --compress --force --whole-file --delete --stats --human-readable --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="" USE="3dnow 3dnowext X a52 aac aacplus aalib acl acpi alsa amr atmo audio audioqueue avcodec avformat avx berkdb bidi bluray bzip2 cdda cddb cdio cli consolekit cpudetection cracklib crypt custom-cflags cxx dbus dc1394 dga dirac direct2d directfb directx dri dshow dts dvb dvbpsi dvd dxva2 egl encode extras faac fbcon fbosd ffmpeg flac fluidsynth fontconfig fortran fuse g3dvl gcrypt gdbm ggi gif gme gmp gnutls growl gsm httpd hwdb iconv ieee1394 inotify ios-vout ipv6 jack joystick jpeg jpeg2k kate kernel-patch libass libcaca libkms libnotify libproxy libsamplerate libtar libtiger libv4l linsys lirc live lua macosx macosx-audio macosx-dialog-provider macosx-eyetv macosx-qtkit macosx-quartztext macosx-vout mad matroska media-library midi mikmod minizip mmx mmxext mod modplug modules mp3 mpeg mtp musepack nas ncurses network nls nptl ogg omxil openal opengl openmp openssl oss pam pcre pic playtools png policykit portaudio postproc projectm pulseaudio pvr python qt4 ramfs readline realtime rtmp rtsp run-as-root samba schroedinger sdl sdl-image session shine shout sid skins smpeg speex sqlite sse sse2 sse3 ssl ssse3 svg switcher swscale system-wide taglib tcpd theora threads tiff timidity truetype tslib twolame udev udex unicode upnp v4l vaapi vcdx vdpau video vlm vorbis vpx wav waveout win32codecs wingdi wma-fixed x264 x86 xcb xinerama xml xorg xosd xv xvid zlib zvbi" ABI_X86="32" ALSA_CARDS="ali5451 als4000 atiixp atiixp-modem bt87x ca0106 cmipci emu10k1 emu10k1x ens1370 ens1371 es1938 es1968 fm801 hda-intel intel8x0 intel8x0m maestro3 trident usb-audio via82xx via82xx-modem ymfpci" APACHE2_MODULES="authn_core authz_core socache_shmcb unixd actions alias auth_basic authn_alias authn_anon authn_dbm authn_default authn_file authz_dbm authz_default authz_groupfile authz_host authz_owner authz_user autoindex cache cgi cgid dav dav_fs dav_lock deflate dir disk_cache env expires ext_filter file_cache filter headers include info log_config logio mem_cache mime mime_magic negotiation rewrite setenvif speling status unique_id userdir usertrack vhost_alias" CALLIGRA_FEATURES="kexi words flow plan sheets stage tables krita karbon braindump author" CAMERAS="ptp2" COLLECTD_PLUGINS="df interface irq load memory rrdtool swap syslog" ELIBC="glibc" GPSD_PROTOCOLS="ashtech aivdm earthmate evermore fv18 garmin garmintxt gpsclock itrax mtk3301 nmea ntrip navcom oceanserver oldstyle oncore rtcm104v2 rtcm104v3 sirf superstar2 timing tsip tripmate tnt ublox ubx" INPUT_DEVICES="keyboard mouse evdev" KERNEL="linux" LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text" LIBREOFFICE_EXTENSIONS="presenter-console presenter-minimizer" LINGUAS="it en" NETBEANS_MODULES="*" OFFICE_IMPLEMENTATION="libreoffice" PHP_TARGETS="php5-5" PYTHON_SINGLE_TARGET="python2_7" PYTHON_TARGETS="python2_7 python3_3" RUBY_TARGETS="ruby19 ruby18" USERLAND="GNU" VIDEO_CARDS="intel vesa nouveau radeon i915 i965 r100 r200 r300 r600" XTABLES_ADDONS="quota2 psd pknock lscan length2 ipv4options ipset ipp2p iface geoip fuzzy condition tee tarpit sysrq steal rawnat logmark ipmark dhcpmac delude chaos account" Unset: CPPFLAGS, CTARGET, INSTALL_MASK, LC_ALL, PORTAGE_BUNZIP2_COMMAND, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS, SYNC, USE_PYTHON
So I will close this for two reason, 1. I don't support aufs3 + gentoo-sources anymore, please use aufs-sources, 2. we have a working version.
:(
(In reply to Dhalsim from comment #9) > :( Why don't you use aufs-sources?
Hi, Becouse this is a part of hi critical italian certified slot machine system. Changing the kernel sources even if they only include addition of aufs3 and paratically will be identical to the gentoo-source patched version, will trigger a lot of new maintence and tests for stability and security by our engineers and italian monopoly engineers because the certification protocol is mandatory for this kind of upgrade. We have also to change the way the scripts automaticaly update and mantain all the boot process (kernel name change for example and so on). The only aufs3 update will require minor tests by us and monopoly engineers. By the way this brunch of aufs3 software is going to be very critical for us, we will study some alternatives. PS: why you maintain a full set of new kernel ebuilds only for aufs3 and instead you will not mantain only aufs3 ebuilds ? Why instead you do not include a dependency ebuild for aufs3 called for example aufs3-patches that can be merged before kernel compilation in order to patch kernel and avoid double kernel compilation ? Regards Massimo.
(In reply to Dhalsim from comment #11) > Hi, > > Becouse this is a part of hi critical italian certified slot machine system. > Changing the kernel sources even if they only include addition of aufs3 and > paratically will be identical to the gentoo-source patched version, will > trigger a lot of new maintence and tests for stability and security by our > engineers and italian monopoly engineers because the certification protocol > is mandatory for this kind of upgrade. We have also to change the way the > scripts automaticaly update and mantain all the boot process (kernel name > change for example and so on). The only aufs3 update will require minor > tests by us and monopoly engineers. > Great to hear that application of Gentoo. I would really recommend to use aufs3-sources instead of the combination of aufs3 + gentoo-sources. They will follow the genpatches and are as identically stable and secure. On the long run you will reduce maintenance effort. > > PS: why you maintain a full set of new kernel ebuilds only for aufs3 and > instead you will not mantain only aufs3 ebuilds ? > the standalone aufs3 package bypasses all portage security features by manipulating files on live file system. By this it is also uncontrollable for me what is present on the live system and will often make the patching fail. so instead of supporting out-of-portage patching of the using the stand-alone patching I recommend to use the prepatched aufs-sources. They represent the same result as the combination of aufs3 + gentoo-sources. > Why instead you do not include a dependency ebuild for aufs3 called for > example aufs3-patches that can be merged before kernel compilation in order > to patch kernel and avoid double kernel compilation ? What would avoid the double patching?
+*aufs3-3_p20140127-r1 (04 Feb 2014) + + 04 Feb 2014; Justin Lecher <jlec@gentoo.org> +aufs3-3_p20140127-r1.ebuild: + Fix patching of latest stable gentoo-sources , #499756 +
(In reply to Justin Lecher from comment #13) > +*aufs3-3_p20140127-r1 (04 Feb 2014) > + > + 04 Feb 2014; Justin Lecher <jlec@gentoo.org> +aufs3-3_p20140127-r1.ebuild: > + Fix patching of latest stable gentoo-sources , #499756 > + Thanks, I confirm that "x86" and "amd_64" now both works with gentoo-sources-3.10.25. Special thanks to Justin Lecher for your assistance, and thanks all other that makes this masterpieace of distribution a reality. Regards Massimo.
> What would avoid the double patching? This secondary ebuilds could install before aufs3 main ebuilds, theis only work is to patch the kernel not to compile the module. Doing so you could emerge gentoo-sources than aufs3_patch new ebuild, configure and compile the kernel and finally emerge aufs3 main ebuild for aufs3 module compilation. Thus avoiding the current double kernel compilation (emerge gentoo-soruces configure and compile, emerge aufs3 recompile the kernel and then reemerge aufs3 module). Is thath correct ?
gentoo-sources-3.10-32 affected by this bug! Regards Massimo.
Created attachment 371870 [details, diff] Patching output with kernel gentoo-sources-3.10.32 Same issue now with kernel 3.10.32. Patch output was attached, emerge output below: # emerge -q1 aufs3 * IMPORTANT: 7 news items need reading for repository 'gentoo'. * Use eselect news to read news items. >>> Verifying ebuild manifests >>> Emerging (1 of 1) sys-fs/aufs3-3_p20140224 >>> Failed to emerge sys-fs/aufs3-3_p20140224, Log file: >>> '/var/tmp/portage/sys-fs/aufs3-3_p20140224/temp/build.log' * Package: sys-fs/aufs3-3_p20140224 * Repository: gentoo * Maintainer: jlec@gentoo.org * USE: amd64 elibc_glibc kernel-patch kernel_linux userland_GNU * FEATURES: preserve-libs sandbox userpriv usersandbox * Determining the location of the kernel source code * Found kernel source directory: * /usr/src/linux * Found sources for kernel version: * 3.10.32-gentoo * Checking for suitable kernel configuration options... [ ok ] * It seems you are using gentoo-sources with aufs3 * Please use sys-kernel/aufs-sources * This will save you the nasty reemerge of sys-fs/aufs3 on every kernel upgrade * Patching your kernel... * Applying aufs3-standalone-base-mmap-combined.patch ... * Failed Patch: aufs3-standalone-base-mmap-combined.patch ! * ( /var/tmp/portage/sys-fs/aufs3-3_p20140224/temp/aufs3-standalone/aufs3-standalone-base-mmap-combined.patch ) * * Include in your bugreport the contents of: * * /var/tmp/portage/sys-fs/aufs3-3_p20140224/temp/aufs3-standalone-base-mmap-combined.patch.out * ERROR: sys-fs/aufs3-3_p20140224::gentoo failed (setup phase): * Failed Patch: aufs3-standalone-base-mmap-combined.patch! * * Call stack: * ebuild.sh, line 93: Called pkg_setup * aufs3-3_p20140224.ebuild, line 90: Called epatch '/var/tmp/portage/sys-fs/aufs3-3_p20140224/temp/aufs3-standalone/aufs3-standalone-base-mmap-combined.patch' * eutils.eclass, line 638: Called die * The specific snippet of code: * die "Failed Patch: ${patchname}!" * * If you need support, post the output of `emerge --info '=sys-fs/aufs3-3_p20140224::gentoo'`, * the complete build log and the output of `emerge -pqv '=sys-fs/aufs3-3_p20140224::gentoo'`. * The complete build log is located at '/var/tmp/portage/sys-fs/aufs3-3_p20140224/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/sys-fs/aufs3-3_p20140224/temp/die.env'. * Working directory: '/usr/src/linux' * S: '/var/tmp/portage/sys-fs/aufs3-3_p20140224/work/aufs3-standalone' * Messages for package sys-fs/aufs3-3_p20140224: * It seems you are using gentoo-sources with aufs3 * Please use sys-kernel/aufs-sources * This will save you the nasty reemerge of sys-fs/aufs3 on every kernel upgrade * Patching your kernel... * Failed Patch: aufs3-standalone-base-mmap-combined.patch ! * ( /var/tmp/portage/sys-fs/aufs3-3_p20140224/temp/aufs3-standalone/aufs3-standalone-base-mmap-combined.patch ) * * Include in your bugreport the contents of: * * /var/tmp/portage/sys-fs/aufs3-3_p20140224/temp/aufs3-standalone-base-mmap-combined.patch.out * ERROR: sys-fs/aufs3-3_p20140224::gentoo failed (setup phase): * Failed Patch: aufs3-standalone-base-mmap-combined.patch! * * Call stack: * ebuild.sh, line 93: Called pkg_setup * aufs3-3_p20140224.ebuild, line 90: Called epatch '/var/tmp/portage/sys-fs/aufs3-3_p20140224/temp/aufs3-standalone/aufs3-standalone-base-mmap-combined.patch' * eutils.eclass, line 638: Called die * The specific snippet of code: * die "Failed Patch: ${patchname}!" * * If you need support, post the output of `emerge --info '=sys-fs/aufs3-3_p20140224::gentoo'`, * the complete build log and the output of `emerge -pqv '=sys-fs/aufs3-3_p20140224::gentoo'`. * The complete build log is located at '/var/tmp/portage/sys-fs/aufs3-3_p20140224/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/sys-fs/aufs3-3_p20140224/temp/die.env'. * Working directory: '/usr/src/linux' * S: '/var/tmp/portage/sys-fs/aufs3-3_p20140224/work/aufs3-standalone'
Reopened with kernel update gentoo-sources-3.10.32
Same ussie gentoo-sources-3.10.32 and newly released aufs3-3_p20140303. Regards
(In reply to Dhalsim from comment #19) > Same ussie gentoo-sources-3.10.32 and newly released aufs3-3_p20140303. No support for gentoo-sources + aufs3. Please use aufs-sources.
+ 06 Mar 2014; Justin Lecher <jlec@gentoo.org> aufs3-3_p20140303.ebuild: + Fix patch source, #499756 +
Thanks a lot for fixing it. If I can make a suggestion, it would be more clear to remove the kernel-patch use flag of sys-fs/aufs3 if it is not maintainable. As a user, given the choice, I'd always take the patch version rather than switching kernel.
(In reply to Sylvain Chevalier from comment #22) > If I can make a suggestion, it would be more clear to remove the > kernel-patch use flag of sys-fs/aufs3 if it is not maintainable. It would be the same problem when doing it by hand. But I will think about it. > As a user, > given the choice, I'd always take the patch version rather than switching > kernel. Why?
(In reply to Justin Lecher from comment #23) > (In reply to Sylvain Chevalier from comment #22) > > If I can make a suggestion, it would be more clear to remove the > > kernel-patch use flag of sys-fs/aufs3 if it is not maintainable. > > It would be the same problem when doing it by hand. But I will think about > it. > > > As a user, > > given the choice, I'd always take the patch version rather than switching > > kernel. > > Why? Hi Justin, those are some of the reasons why we prefer patches against aufs3 sources and why you would prefer it too: - the aufs3-sources ebuilds doesn't show exactly the aufs3 patch version is applied thus means when a new version of auf3 ebuild is out in not clear which version on your aufs3-sources patch is applied, and is not clear for everyone if the new module will work fine with an older patched kernel - in a very high critial environmpent is ot so easy to switch kernel without testing all the functionalities on itit (think of high availability web servers or the slot system I have explained in the post above) even if you have to do once in the product life. - whenever we use patched gentoo-sources or aufs3-sources we should rebuild the whole kernel/modules on every aufs3 ebuild release for robustness. This not give us the chance to save time for compiling and rebooting (so there is no real benefit on your one or another) but and also give us the effort to check if we need to redownload the aufs3-sources ebuilds files (about 150mb) - mantaining the aufs3-sources ebuild needs more effort for you becouse the needs to patch/check/build/test/sign/release a complete set of kernel sources each ebuilds files size is 150mb. I think you test the aufs3 ebuilds with other kernel ebuild sources such as hardened-sources. Now think about you could save time avoiding aufs3-sources whole ebuild set - the idea to work with another kernel-source branch is giving us disquiet, anxiety and all other negative emotions we feel when we change sometingh that worked for years in favour of something completly new. Then, when you work in a team and you are the team leader in a high competitive environment, there is always someone envy of your position that will speculate on your decisions even if the future problems of the project is not a direct consequence of them in order to smash you out. Think about it even if I have no experience I will be very happy to have the canche to help you mantaining the aufs3 ebuild fully functional with the gentoo-sources branch. Regards Massimo.
(In reply to Dhalsim from comment #24) > - the aufs3-sources ebuilds doesn't show exactly the aufs3 patch version is > applied thus means when a new version of auf3 ebuild is out in not clear > which version on your aufs3-sources patch is applied, and is not clear for > everyone if the new module will work fine with an older patched kernel We can change that. In principle I always apply the latest possible aufs3, because this is how upstream develops aufs. > - in a very high critial environmpent is ot so easy to switch kernel without > testing all the functionalities on itit (think of high availability web > servers or the slot system I have explained in the post above) even if you > have to do once in the product life. gentoo-sources + aufs3[kernel-patch] are exactly aufs-sources. So no need to retest. > > - whenever we use patched gentoo-sources or aufs3-sources we should rebuild > the whole kernel/modules on every aufs3 ebuild release for robustness. This > not give us the chance to save time for compiling and rebooting (so there is > no real benefit on your one or another) but and also give us the effort to > check if we need to redownload the aufs3-sources ebuilds files (about 150mb) The size difference between gentoo-sources and aufs-sources are 149kb for the linux-3.13. So no gain for you here to not switch. And you need to rebuilt the whole kernel in both cases. > > - mantaining the aufs3-sources ebuild needs more effort for you becouse the > needs to patch/check/build/test/sign/release a complete set of kernel > sources each ebuilds files size is 150mb. I think you test the aufs3 ebuilds > with other kernel ebuild sources such as hardened-sources. Now think about > you could save time avoiding aufs3-sources whole ebuild set Seriously, maintaining the crap with sys-fs/aufs3 is what makes the most problems. I only have reports for 1% or less of the aufs-sources releases, but with a much higher percentage for aufs3. > Think about it even if I have no experience I will be very happy to have the > canche to help you mantaining the aufs3 ebuild fully functional with the > gentoo-sources branch. Sure, help is always welcome. Just send patches whenever something goes wrong.
