Bug 131073 – Autoregeneration of Manifest/digest files on merge

• Status: RESOLVED FIXED
• Product: Portage Development

[Description Diego Elio Pettenò (RETIRED) 2006-04-24 01:42:54 UTC]

portage 2.1_pre9-r{3,4} seems to regenerate Manifest/digest when doing fetch directly or while emerging something (also update).
This is bad because when working with PORTDIR set to a CVS tree you get the manifests changed there and waiting for a collision on the next "cvs up".

Portage 2.1_pre9-r4 (default-linux/amd64/2006.0, gcc-4.0.2, glibc-2.4-r2, 2.6.16-gentoo-r2 x86_64)
=================================================================
System uname: 2.6.16-gentoo-r2 x86_64 AMD Athlon(tm) 64 Processor 3500+
Gentoo Base System version 1.12.0_pre18
distcc 2.18.3 x86_64-pc-linux-gnu (protocols 1 and 2) (default port 3632) [disabled]
ccache version 2.4 [disabled]
dev-lang/python:     2.4.3
sys-apps/sandbox:    1.2.17
sys-devel/autoconf:  2.13, 2.59-r7
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, 2.16.92
sys-devel/libtool:   1.5.22
virtual/os-headers:  2.6.11-r3
ACCEPT_KEYWORDS="amd64 ~amd64"
AUTOCLEAN="yes"
CBUILD="x86_64-pc-linux-gnu"
CFLAGS="-march=athlon64 -Os -ftracer -pipe -ftree-vectorize -Wformat=2 -Wno-error -Wno-pointer-sign -g -ggdb -Wstrict-aliasing=2"
CHOST="x86_64-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.5/env /usr/kde/3.5/share/config /usr/kde/3.5/shutdown /usr/kde/3/share/config /usr/lib/X11/xkb /usr/share/X11/xkb /usr/share/config /var/qmail/control"
CONFIG_PROTECT_MASK="/etc/eselect/compiler /etc/gconf /etc/revdep-rebuild /etc/terminfo /etc/texmf/web2c /etc/env.d"
CXXFLAGS="-march=athlon64 -Os -ftracer -pipe -ftree-vectorize -Wno-error -Wformat=2 -g -ggdb -Wstrict-aliasing=2"
DISTDIR="/var/portage/distfiles"
EMERGE_DEFAULT_OPTS="--alphabetical"
FEATURES="autoaddcvs autoconfig buildpkg collision-protect confcache cvs digest distlocks metadata-transfer multilib-strict noauto noinfo parallel-fetch sandbox sfperms sign splitdebug userpriv usersandbox"
GENTOO_MIRRORS="http://www.die.unipd.it/pub/Linux/distributions/gentoo-sources/         http://ftp.unina.it/pub/linux/distributions/gentoo/      http://gentoo.osuosl.org/"
LANG="en_US.UTF-8"
LC_ALL=""
LDFLAGS="-Wl,-O1 -Wl,--as-needed -Wl,-hashvals"
LINGUAS="en it"
MAKEOPTS="-j1 -s"
PKGDIR="/var/portage/pkg-enterprise"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/var/portage/cvs/gentoo-x86"
PORTDIR_OVERLAY="/var/portage/crossoverlay /var/portage/cvs/gentoo-alt/overlay /var/portage/cvs/flame-overlay /var/portage/cvs/flame-portage /var/portage/cvs/vmware"
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
USE="3dnowex S3TC a52 aac acl acpi4linux alsa amd64 apm audiofile avi bash-completion bzip2 bzlib cdda cddb cdio cdr cjk crypt css cups dlloader dnd dpms dts dvd dvdr dvdread eds emboss fam fame ffmpeg flac foomaticdb gif gnutls gpgme gphoto2 gtk2 howl idn ieee1394 imlib imlib2 ipv6 ithreads joystick jpeg kde latex lm_sensors lx700 lzw lzw-tiff mad maildir matroska mmap mng mozsvg mp3 mpeg mpeg4 mpm-threadpool native no_wxgtk1 noantlr nobcel nobeanutils nobsh nocommonslogging nocommonsnet nodrm nojdepend nojsch nojython nolog4j nomotif nooro noregexp norhino noxalan noxerces nptl nptlonly nvidia ogg oggvorbis openntpd pam pdf pdflib pic png ppds qemu-fast qt rtc snmp speex spell ssl stencil-buffer subversion svg svgz symlink sysfs syslog tetex theora threads tiff truetype truetype-fonts type1 type1-fonts udev unicode usb userlocales utf8 v4l v4l2 vhosts vorbis wxwindows x11vnc xinerama xpm xv xvid zlib zvbi elibc_glibc kernel_linux linguas_en linguas_it sane_backends_snapscan userland_GNU video_cards_none video_cards_nvidia"
Unset:  ASFLAGS, CTARGET, INSTALL_MASK

[Comment 1 Zac Medico 2006-04-24 02:13:30 UTC]

It seems that FEATURES=digest is behaving differently now with the Manifest2 code.

[Comment 2 Marius Mauch (RETIRED) 2006-04-24 05:04:52 UTC]

Could be, IMO that crap should be dropped.

[Comment 3 Donnie Berkholz (RETIRED) 2006-04-24 13:36:13 UTC]

This also results in tracebacks when running emerge --fetch as a user, because it tries to create a Manifest in /usr/portage.

[Comment 4 Zac Medico 2006-04-24 14:14:59 UTC]

(In reply to comment #2)
> IMO that crap should be dropped.

Does anybody have a good argument to keep FEATURES=digest around?  Shouldn't digest/manifest creation should be restricted to tools such as ebuild and repoman?

[Comment 5 Donnie Berkholz (RETIRED) 2006-04-24 16:36:43 UTC]

I find it convenient for development to add/move an ebuild around, then run emerge -f foo.

[Comment 6 Zac Medico 2006-04-28 17:54:37 UTC]

(In reply to comment #3)
> This also results in tracebacks when running emerge --fetch as a user, because
> it tries to create a Manifest in /usr/portage.

I've fixed it to give a simple Permission Denied error in svn r3263.

(In reply to comment #0)
> portage 2.1_pre9-r{3,4} seems to regenerate Manifest/digest when doing fetch
> directly or while emerging something (also update).

As it should when FEATURES=digest is enabled.  Don't use it unless you want regeneration of both Manifests and digests (like in comment #5).

[Comment 7 Zac Medico 2006-04-29 08:28:38 UTC]

Released in 2.1_pre10.