Created attachment 374136 [details] build.log src_configure fails, displays errors like this: CMake Error at core/cmake/QutIMMacros.cmake:65 (QT4_CREATE_MOC_COMMAND): QT4_CREATE_MOC_COMMAND Macro invoked with incorrect arguments for macro named: QT4_CREATE_MOC_COMMAND Call Stack (most recent call first): core/cmake/QutIMMacros.cmake:316 (QUTIM_WRAP_CPP) plugins/blogimprover/CMakeLists.txt:1 (qutim_add_plugin) Portage 2.2.8-r1 (hardened/linux/amd64, gcc-4.7.3, glibc-2.17, 3.13.5-hardened-r1 x86_64) ================================================================= System Settings ================================================================= KiB Mem: 65825868 total, 906228 free KiB Swap: 0 total, 0 free Timestamp of tree: Wed, 02 Apr 2014 22:45:01 +0000 ld GNU ld (GNU Binutils) 2.23.2 app-shells/bash: 4.2_p45 dev-lang/python: 2.7.5-r3 dev-util/cmake: 2.8.12.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/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 nikoli ACCEPT_KEYWORDS="amd64" ACCEPT_LICENSE="* -@EULA" CBUILD="x86_64-pc-linux-gnu" CFLAGS="-march=corei7-avx -O2 -pipe" CHOST="x86_64-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/share/config /usr/share/gnupg/qualified.txt /usr/share/themes/oxygen-gtk/gtk-2.0 /usr/share/themes/oxygen-gtk/gtk-3.0 /var/bind" 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/terminfo" CXXFLAGS="-march=corei7-avx -O2 -pipe" FCFLAGS="-O2 -pipe" FEATURES="assume-digests binpkg-logs cgroup collision-protect config-protect-if-modified distlocks ebuild-locks fixlafiles ipc-sandbox merge-sync network-sandbox news parallel-fetch preserve-libs protect-owned sandbox sfperms strict test unknown-features-warn unmerge-logs unmerge-orphans userfetch userpriv usersandbox usersync xattr" FFLAGS="-O2 -pipe" LANG="en_US.UTF-8" LDFLAGS="-Wl,--hash-style=gnu -Wl,-O1 -Wl,--as-needed" MAKEOPTS="-j9" 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" PORTDIR_OVERLAY="/var/lib/layman/nikoli" USE="X a52 aac acl acpi aes-ni alsa amd64 amr audiofile avx bash-completion bzip2 cairo caps cdda cddb cdio cdparanoia cdr celt cli consolekit cracklib crypt css cups cxx dbus djvu dri dts dv dvd dvdr encode exif fat ffmpeg flac fluidsynth fontconfig fortran gd geoip gif gimp gmp gphoto2 gpm graphviz gsm gstreamer gtk handbook hardened iconv icu id3tag idn ilbc imagemagick imap imlib ios ipod ipv6 jbig jpeg jpeg2k justify kde kipi lame laptop lcms libass libnotify libproxy libsamplerate lm_sensors lzma lzo mac mad matroska mikmod mmx mmxext modplug modules mp3 mp4 mpeg mtp multilib musepack musicbrainz ncurses networkmanager nls nptl nptlonly ntfs ogg openal openexr opengl openmp opus pam pango pax_kernel pcre pdf phonon plasma pm-utils png policykit postscript qt3support qt4 quicktime rar raw readline reiserfs replaygain rtmp sasl scanner semantic-desktop session sid smp sndfile socks5 speex spell sqlite sse sse2 sse3 sse4_1 ssl ssse3 startup-notification svg symlink sysfs taglib theora threads thumbnail tiff truetype tta udev udisks unicode upnp upower usb v4l v4l2 vcd vdpau vorbis vpx wavpack webkit webp wma wmf x264 xattr xcb xcomposite xface xinerama xml xmp xpm xscreensaver xtpax xv xvid xz zip 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="*" 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" GRUB_PLATFORMS="efi-64" INPUT_DEVICES="evdev" KERNEL="linux" LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text" LIBREOFFICE_EXTENSIONS="presenter-minimizer" LINGUAS="ru ru_RU en" NGINX_MODULES_HTTP="access auth_basic autoindex fastcgi gzip rewrite" OFFICE_IMPLEMENTATION="libreoffice" PHP_TARGETS="php5-5" PYTHON_SINGLE_TARGET="python2_7" PYTHON_TARGETS="python2_7" QEMU_SOFTMMU_TARGETS="i386 x86_64" QEMU_USER_TARGETS="i386 x86_64" RUBY_TARGETS="ruby20" USERLAND="GNU" VIDEO_CARDS="radeon r600 modesetting vesa" 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, LC_ALL, PORTAGE_BUNZIP2_COMMAND, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS, SYNC, USE_PYTHON ================================================================= Package Settings ================================================================= net-im/qutim-0.3.1 was built with the following: USE="crypt dbus histman hunspell irc jabber kde mrim oscar otr phonon ssl test vkontakte webkit xscreensaver -aspell -awn (-ayatana) -debug -doc -kinetic -multimedia -purple -qml -sdl -telepathy" ABI_X86="64" LINGUAS="ru -ar -be -bg -cs -de -en_GB -sk -uk -zh_CN"
Caused by >=cmake-2.8.12 I guess.
(In reply to Davide Pesavento from comment #1) > Caused by >=cmake-2.8.12 I guess. There was a similar bug (+upstream fix) in net-libs/telepathy-qt-0.9.3-r1 and maybe qutim needs bump.
(In reply to Davide Pesavento from comment #1) > Caused by >=cmake-2.8.12 I guess. Interesting. So it seems I was both right and wrong in bug 505580.
*** Bug 510592 has been marked as a duplicate of this bug. ***
*** Bug 515844 has been marked as a duplicate of this bug. ***
The last version of cmake <2.8.12 was removed on July 13th, therefore it has been impossible to build qutim on gentoo for more than 3 months. There's a new upstream version (and a pending version bump bug open), but: (a) it's not clear if the new version fixes the incompatibility with current cmake (b) it's a big package, with a nontrivial set of dependencies, in some cases the new version depends on unreleased versions of other software, so in order to bump it we'd have to create VCS snapshots of other packages (c) version 0.4 is being developed upstream, and they switched from cmake to qbs, which probably means rewriting most of the ebuild (d) b+c above imply that qutim is a high maintenance package, however no members of the qt team seem interested in it (e) we are understaffed Therefore a version bump is unlikely to happen in the foreseeable future. In fact, I think we should mask qutim for removal.
(In reply to Davide Pesavento from comment #6) > Therefore a version bump is unlikely to happen in the foreseeable future. In > fact, I think we should mask qutim for removal. ++
https://github.com/qutIM/gentoo-portage-overlay/commit/d4791a7b49a7b34c4e6e3b7dd68c8aca2c302e67
(In reply to Nikoli from comment #8) > https://github.com/qutIM/gentoo-portage-overlay/commit/ > d4791a7b49a7b34c4e6e3b7dd68c8aca2c302e67 Just by reading, those ebuilds have numerous serious issues.
(In reply to Nikoli from comment #8) > https://github.com/qutIM/gentoo-portage-overlay/commit/ > d4791a7b49a7b34c4e6e3b7dd68c8aca2c302e67 ...so what?
(In reply to Davide Pesavento from comment #6) > The last version of cmake <2.8.12 was removed on July 13th, therefore it has > been impossible to build qutim on gentoo for more than 3 months. > > There's a new upstream version (and a pending version bump bug open), but: > > (a) it's not clear if the new version fixes the incompatibility with current > cmake There is a 0.3.3. release out a week ago which is stated to fix the issue. > (b) it's a big package, with a nontrivial set of dependencies, in some cases > the new version depends on unreleased versions of other software, so in > order to bump it we'd have to create VCS snapshots of other packages It seems the cmake dependency check is maintained well upstream, so it shouldn't be so hard to track them... > (c) version 0.4 is being developed upstream, and they switched from cmake to > qbs, which probably means rewriting most of the ebuild. By the way, is there some eclass-level workarounds about qbs by now? It's already been two bugfix release and over a year are gone since 0.4 branch is started to be developed... I don't suppose that 0.4 can be released any minute now... > (d) b+c above imply that qutim is a high maintenance package, however no > members of the qt team seem interested in it > (e) we are understaffed > Gimme a couple of hours ;)... Actually, a bit more, but only because I really should take a nap... =)
Created attachment 388384 [details, diff] A propoused patch to fix qutim-0.3.1 build
Created attachment 388386 [details, diff] The second patch, fixes build with the USE=kde
I've tested that net-im/qutim-0.3.1 builds well either with all use enabled as well as with all disabled. I haven't performed any usability tests because I'm already using the newer version and don't want to mess with downgrading...
(In reply to Fat-Zer from comment #11) > (In reply to Davide Pesavento from comment #6) > > The last version of cmake <2.8.12 was removed on July 13th, therefore it has > > been impossible to build qutim on gentoo for more than 3 months. > > > > There's a new upstream version (and a pending version bump bug open), but: > > > > (a) it's not clear if the new version fixes the incompatibility with current > > cmake > There is a 0.3.3. release out a week ago which is stated to fix the issue. > It's evident that nobody is interested in bumping this package though, as a previous bump request (bug 501808) is still pending...since February. > > (b) it's a big package, with a nontrivial set of dependencies, in some cases > > the new version depends on unreleased versions of other software, so in > > order to bump it we'd have to create VCS snapshots of other packages > It seems the cmake dependency check is maintained well upstream, so it > shouldn't be so hard to track them... > Packaging snapshots of unreleased software, especially libraries, is always very time consuming. > > (c) version 0.4 is being developed upstream, and they switched from cmake to > > qbs, which probably means rewriting most of the ebuild. > By the way, is there some eclass-level workarounds about qbs by now? > It's already been two bugfix release and over a year are gone since 0.4 > branch is started to be developed... I don't suppose that 0.4 can be > released any minute now... > I don't understand what you're saying. Please rephrase. > > (d) b+c above imply that qutim is a high maintenance package, however no > > members of the qt team seem interested in it > > (e) we are understaffed > > > Gimme a couple of hours ;)... Actually, a bit more, but only because I > really should take a nap... =) Are you willing to *maintain* this package? Just throwing some random patches isn't gonna help, this package needs a _dedicated_ maintainer.
> > By the way, is there some eclass-level workarounds about qbs by now? > > It's already been two bugfix release and over a year are gone since 0.4 > > branch is started to be developed... I don't suppose that 0.4 can be > > released any minute now... > > > > I don't understand what you're saying. Please rephrase. I've tried to say that I think the version 0.4 won't be released in the nearest future... > Are you willing to *maintain* this package? Just throwing some random > patches isn't gonna help, this package needs a _dedicated_ maintainer. I'd love to say "sure, why not", but I'll wait a bit and ask some questions instead... I'm a bit confused, what «dedicated» maintainer should/must/supposed to do? is there any guide? Just bumping newer version and react on bugs? nothing more extraordinary? And what is the workflow? Am I supposed to parse bugzilla myself or there is some sort of automation? How to pass my work? Through bugzilla? or there is a more direct way? Something like github's pull requests would be great...
(In reply to Fat-Zer from comment #16) > > Are you willing to *maintain* this package? Just throwing some random > > patches isn't gonna help, this package needs a _dedicated_ maintainer. > I'd love to say "sure, why not", but I'll wait a bit and ask some questions > instead... I'm a bit confused, what «dedicated» maintainer > should/must/supposed to do? is there any guide? > Just bumping newer version and react on bugs? nothing more extraordinary? > And what is the workflow? Am I supposed to parse bugzilla myself or there is > some sort of automation? How to pass my work? Through bugzilla? or there is > a more direct way? Something like github's pull requests would be great... http://wiki.gentoo.org/wiki/Project:Proxy_Maintainers
sounds not too hard... I think I can handle it...
Created attachment 388504 [details] net-im/qutim/metadata.xml
Created attachment 388506 [details, diff] qutim-0.3.1 ebuild patch
(In reply to cyberbat from comment #17) > > http://wiki.gentoo.org/wiki/Project:Proxy_Maintainers So, am I supposed to trigger devs somehow? e.g. changing the keywords or whatever? And am I expected to do something special to get the proxy-maintainer status now?
Did you contact proxy-maint@gentoo.org ?
(In reply to Davide Pesavento from comment #22) > Did you contact proxy-maint@gentoo.org ? not yeat...
it's usually relatively easy to do proxy-commit part, I can help here, but hope you guys can help to review all the patches and ebuilds, thanks. I'll commit in a few days if no objection of above patches.
(In reply to Yixun Lan from comment #24) > it's usually relatively easy to do proxy-commit part, I can help here, > but hope you guys can help to review all the patches and ebuilds, thanks. Awesome, thanks. Please remember to update metadata (you can drop qt@) and reassign open bugs too. As for the reviews, I think you can expect some help from us on qt-related patches or questions, but not much more than that (otherwise we'd be maintaining this package ourselves :P) > I'll commit in a few days if no objection of above patches. No objections from me, but I have two small suggestions: 1. add a reference to the bug# for patches in the ebuild 2. the names of the patches contain "newer" and "newest"... be more specific... what version(s) are you talking about?
Created attachment 388652 [details, diff] A propoused patch to fix qutim-0.3.1 build
Created attachment 388654 [details, diff] qutim-0.3.1 ebuild patch > > I'll commit in a few days if no objection of above patches. > > No objections from me, but I have two small suggestions: > > 1. add a reference to the bug# for patches in the ebuild done > 2. the names of the patches contain "newer" and "newest"... be more > specific... what version(s) are you talking about? Changed the name of the first patch. The second one is cherry-pick'ed&format-patch'ed from upstream git so I suppose it would be more straightforward to keep the name common with the commit message...
+*qutim-0.3.1-r1 (06 Nov 2014) + + 06 Nov 2014; Sergey Popov <pinkbyte@gentoo.org> -qutim-0.3.1.ebuild, + +qutim-0.3.1-r1.ebuild, +files/qutim-0.3.1-cmake-2.8.12-kde-build.patch, + +files/qutim-0.3.1-cmake-2.8.12-qt-build.patch, metadata.xml: + Revision bump: EAPI 5, fix bug #506614, patches by Alexander Golubev <fatzer2 + AT gmail.com>, who will maintain this package through proxy maintainers. Drop + old revision, drop qt herd from metadata
