Copied monotone-0.25.ebuild to monotone-0.26.ebuild and worked fine for amd64 GCC3.4.6 and GCC4.1.0. Compiles fine on my x86 machine, but for some reason segfaults on run. Portage 2.1_pre7-r5 (default-linux/amd64/2006.0, gcc-4.1.0, glibc-2.4-r1, 2.6.16-rc6 x86_64) ================================================================= System uname: 2.6.16-rc6 x86_64 AMD Athlon(tm) 64 Processor 3000+ Gentoo Base System version 1.12.0_pre17 dev-lang/python: 2.3.5-r2, 2.4.2-r1 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-r2 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="-O2 -march=k8" 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/lib64/mozilla/defaults/pref /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="-O2 -march=k8" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig distlocks metadata-transfer sandbox sfperms strict" GENTOO_MIRRORS="http://distfiles.gentoo.org http://distro.ibiblio.org/pub/linux/distributions/gentoo" LC_ALL="en_US.UTF-8" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="amd64 X aac accessibility ada alsa arts artswrappersuid avahi avahni avi bash-completion berkdb bitmap-fonts cdr clearcase cli crypt cups curl cvs dbus divx doc dri eds emboss encode esd evo exscalibar ext-debian ext-doc ext-dvi ext-koffice ext-kpresenter ext-kspread ext-kword ext-lyx ext-man ext-pdf ext-ppt ext-ps ext-rpm ext-rtf ext-tex ext-xls fam ffmpeg flac foomaticdb fortran gcj gdbm gif gnome gpm gstreamer gtk gtk2 haskell imlib ipod ipv6 isdnlog jack java javascript jpeg kde kqemu ldap libcaca lzw lzw-tiff mad mikmod modplug mono mozcalander mozdevelop mozsvg mp3 mpeg mplayer musepack musicbrainz nas ncurses netjack nls nptl nptlonly nvidia offensive ogg ole opengl oss pam pascal pcre pdf pdflib perforce perl php png pppd python qt quicktime readline reflection ruby sdl session sid sndfile spell spl sql ssl subversion svg tagwriting tcpd theora tiff truetype-fonts type1-fonts unicode usb v4l visualization vorbis wma xattr xcomposite xine xinerama xomposite xorg xosd xpm xprint xv xvid zeroconf zlib elibc_glibc input_devices_keyboard input_devices_mouse kernel_linux userland_GNU video_cards_vga video_cards_nvidia video_cards_nv" Unset: ASFLAGS, CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LANG, LDFLAGS, LINGUAS
Runs fine now on x86 after reemerging libstdc++-v3. Portage 2.1_pre9-r5 (default-linux/x86/2006.0, gcc-3.4.6, glibc-2.4-r1, 2.6.15 i686) ================================================================= System uname: 2.6.15 i686 Pentium III (Katmai) Gentoo Base System version 1.12.0_pre18 dev-lang/python: 2.3.5-r2, 2.4.3 dev-util/ccache: [Not Present] dev-util/confcache: [Not Present] 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-r2 sys-devel/libtool: 1.5.22 virtual/os-headers: 2.6.11-r5 ACCEPT_KEYWORDS="x86 ~x86" AUTOCLEAN="yes" CBUILD="i686-pc-linux-gnu" CFLAGS="-Os -march=pentium3 -pipe" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/eselect/compiler /etc/gconf /etc/revdep-rebuild /etc/terminfo /etc/env.d" CXXFLAGS="-Os -march=pentium3 -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig distlocks metadata-transfer sandbox sfperms strict" GENTOO_MIRRORS="http://distfiles.gentoo.org http://distro.ibiblio.org/pub/linux/distributions/gentoo" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="x86 alsa apache2 apm arts avi bash-completion berkdb bitmap-fonts cli crypt cups dri eds emboss encode esd foomaticdb fortran gd gdbm gif gpm gstreamer gtk gtk2 imap imlib ipv6 isdnlog jpeg kde ldap libg++ libwww mad maildir mikmod motif mp3 mpeg ncurses nls nptl nptlonly ogg opengl oss pam pcre pdflib perl png postgres pppd python qt quicktime readline reflection sasl session spell spl ssl tcpd truetype truetype-fonts type1-fonts udev unicode vorbis xml xmms xorg xv zlib elibc_glibc kernel_linux userland_GNU" Unset: ASFLAGS, CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LANG, LC_ALL, LDFLAGS, LINGUAS, MAKEOPTS
how was the migration? easy/hard? what instuctions would you recommend at the end of the ebuild?
The migration is relitively simple. All databases from pre 0.26 have to be upgraded (best to backup before doing it). mtn --db=(database) db migrate mtn --db=(database) db rosterify On the few databases i migrated i didnt run into any other problems, so I think that should be all needed for the warning. From the wiki though, the roster step has broken a few databases, so the backup is a good thing.
(In reply to comment #3) > The migration is relitively simple. > All databases from pre 0.26 have to be upgraded (best to backup before doing > it). > > mtn --db=(database) db migrate > mtn --db=(database) db rosterify Please note! The rosterify step should (in general) be run one once for each project (rather than for each database with a copy of the project. Normally, this is something that would be done by a "project coordinator" type person, typically on a copy of the db that lives on a central server, rather than by each end-user or developer. The exceptions to the "in general" comment above relate to private branches or revisions forking off the main repository, but not pushed back into it. People who have been following monotone development will be aware of this already, but just consider the above when wording any messages to be emitted by the ebuild. It's not a good idea to recommend to everyone to run "rosterify"
.26 fixes a gcc-4.1 issue here on ppc. It would be nice if .26 could be added to portage in the near future :-) Thanks
0.27 is now available (works nice with a bump in x86). It would also be nice if someone could provide the init scripts to easily start a monotone server.
Bumped to 0.27 fine on amd64 also.
*** Bug 138261 has been marked as a duplicate of this bug. ***
0.26 and 0.27 should be set SLOT=1 as they are incompatible with old-format databases. However, the binary has been renamed upstream from monotone to "mtn", so SLOTs are very easy to do :-D.
(In reply to comment #6) > 0.27 is now available (works nice with a bump in x86). > It would also be nice if someone could provide the init scripts to easily start > a monotone server. I'm still waiting for this nice person too :-) (In reply to comment #9) > 0.26 and 0.27 should be set SLOT=1 as they are incompatible with old-format > databases. Ok. I'm in final stages of preparation for 0.27. Is 0.26 needed? I'll do 0.27 as a SLOT=1. > However, the binary has been renamed upstream from monotone to > "mtn", so SLOTs are very easy to do :-D. How nice of them.
> > However, the binary has been renamed upstream from monotone to > > "mtn", so SLOTs are very easy to do :-D. > > How nice of them. > pitty the info files clash. Looking for a resolution here before commiting a SLOT. Hopefully the init files are easy.
0.28 is now released :P
0.28 bumped fine on amd64
Created attachment 93551 [details] monotone-0.28 + init scripts I've finally found the time to do the init scripts. I've used debian, red hat and netbsd monotone's init scripts as... "inspiration". Excuse me if there are some other-distro-isms, I'm no expert with init scripts yet ;) It's based on the bumped 0.28 version with SLOT dumped to 1 as discussed. I'm currently reinstalling monotone to see if all the scripts get installed in place (slow machine). Time to sleep!
Created attachment 93553 [details, diff] Patch to install the sample write-permissions The compilation finished before I touched my bed... I forgot to install the write-permissions sample file. This patch fixes it. I also forgot to add migration instructions from <=0.25, but I think someone else will explain it better than me.
Please can this bug be actioned ASAP. In addition, instead of giving detailed upgrade instructions during emerge, I'm sure that a reference to the detailed page http://www.venge.net/monotone/UPGRADE would be sufficient.
comment #16 - ref upgrade instructions noted thanks. comment #14 - thanks for init scripts. I was looking at doing a similar sort of "copying". Jordi - I'd feel more reassured if you've described that you've tested these. Ref slotting - if I don't have a patch to make the info files avoid clashing I'm not going to bother slotting it. Thanks to all other comments. I've just been very overloaded with other stuff to do. If anyone here has a good bug record and wants to maintain this and a few other packages email me with your details.
I confirm I've been using the init scripts since I posted them here. It's been running on my personal monotone server with no problems. I don't know how well does it work with other configs. I haven't tried 0.29 yet.
Add another looking for an update to the ebuild. (I know, do it myself and submit the patches)
Add another vote. I think the time to worry about migration and compatibility and side-by-side slot installs has passed, laudable though those ideals were. Anyone following or using monotone on gentoo has long since upgraded themselves from source -- or won't be upgrading if the ebuild is bumped anyway. Time to just push the button on this one.
Copied 0.25 to 0.29 without any editing. Emerged. It seems to work without problem. My architecture is x86. It would be nice to get it into portage, since 0.25 is portage's last ebuild. Cheers, Pavlix
Created attachment 95883 [details] tarball of ebuilds and other files (w/ init scripts) I decided to give the posted tarball a try and found it to work well. I wanted to used 0.29, so I copied over the ebuild to 0.29 and version bumped the boost requirement. It emerged both 0.28 and 0.29 just fine. So I figured I would wrap that up into a tarball and submit it. I have included ebuilds for both versions because it provides choice for those who do not want to use the latest boost version and because the changelog between monotone versions is not that severe. I have not included 0.26 or 0.27 ebuilds as they are pretty much obsoleted by this point. This tarball also includes the write-permissions patch that is also attached to this bug. tarball manifest: dev-util/monotone/ dev-util/monotone/files/ dev-util/monotone/files/hooks.lua dev-util/monotone/files/monotone.confd dev-util/monotone/files/monotone.initd dev-util/monotone/files/read-permissions dev-util/monotone/files/write-permissions dev-util/monotone/files/digest-monotone-0.29 dev-util/monotone/files/digest-monotone-0.28 dev-util/monotone/Manifest dev-util/monotone/monotone-0.29.ebuild dev-util/monotone/monotone-0.28.ebuild
abnomally aleart - montone-0.29 added. thanks to the many many many people who have endured my slowness and contributed to the concoction that is this ebuild and scripts
Erik, if you are still with us, could you review 0.99.1 and check if hooks.lua script is still required? It sources passphrase.lua script which is not available anymore... I'm going to drop hooks.lua with next version bump.
