Bug 205242 - Please stabilise app-office/gnotime-2.3.0
|
Bug#:
205242
|
Product: Gentoo Linux
|
Version: unspecified
|
Platform: All
|
|
OS/Version: Linux
|
Status: RESOLVED
|
Severity: enhancement
|
Priority: P2
|
|
Resolution: FIXED
|
Assigned To: amd64@gentoo.org
|
Reported By: fauli@gentoo.org
|
|
Component: Ebuilds
|
|
|
URL:
|
|
Summary: Please stabilise app-office/gnotime-2.3.0
|
|
Keywords: STABLEREQ
|
|
Status Whiteboard:
|
|
Opened: 2008-01-10 20:09 0000
|
dev-libs/qof-0.7.2 also needed, thanks
on amd64:
well, app-office/gnotime-2.2.3 depends on =gnome-extra/gtkhtml-3.2*. the
problem is that both =gnome-extra/gtkhtml-3.2.4 and =gnome-extra/gtkhtml-3.2.5
are affected by bug 193458, so gnotime-2.2.3 cannot even be installed.
(In reply to comment #3)
> on amd64:
> well, app-office/gnotime-2.2.3 depends on =gnome-extra/gtkhtml-3.2*. the
> problem is that both =gnome-extra/gtkhtml-3.2.4 and =gnome-extra/gtkhtml-3.2.5
> are affected by bug 193458, so gnotime-2.2.3 cannot even be installed.
Please check again.
(In reply to comment #4)
> Please check again.
on amd64:
well, as bug 193458 has been fixed, i was able to take a look at
app-office/gnotime-2.2.3 USE="-debug"
using
dev-libs/qof-0.7.2
as far as i can say, gnotime-2.2.3 seems to work for fine (note that i didn't
do anything too fancy - i've never used that program before).
Portage 2.1.3.19 (default-linux/amd64/2007.0/desktop, gcc-4.1.2,
glibc-2.6.1-r0, 2.6.23-gentoo-r6 x86_64)
=================================================================
System uname: 2.6.23-gentoo-r6 x86_64 Intel(R) Core(TM)2 Duo CPU E6550 @
2.33GHz
Timestamp of tree: Thu, 31 Jan 2008 02:46:01 +0000
app-shells/bash: 3.2_p17-r1
dev-java/java-config: 1.3.7, 2.0.33-r1
dev-lang/python: 2.4.4-r6
dev-python/pycrypto: 2.0.1-r6
sys-apps/baselayout: 1.12.10-r5
sys-apps/sandbox: 1.2.18.1-r2
sys-devel/autoconf: 2.13, 2.61-r1
sys-devel/automake: 1.5, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2, 1.10
sys-devel/binutils: 2.18-r1
sys-devel/gcc-config: 1.4.0-r4
sys-devel/libtool: 1.5.24
virtual/os-headers: 2.6.23-r2
ACCEPT_KEYWORDS="amd64"
CBUILD="x86_64-pc-linux-gnu"
CFLAGS="-march=nocona -O2 -pipe"
CHOST="x86_64-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/kde/3.5/env /usr/kde/3.5/share/config
/usr/kde/3.5/shutdown /usr/share/X11/xkb /usr/share/config"
CONFIG_PROTECT_MASK="/etc/env.d /etc/env.d/java/ /etc/fonts/fonts.conf
/etc/gconf /etc/revdep-rebuild /etc/terminfo /etc/texmf/web2c
/etc/udev/rules.d"
CXXFLAGS="-march=nocona -O2 -pipe"
DISTDIR="/var/portage/distfiles"
FEATURES="distlocks metadata-transfer sandbox sfperms strict unmerge-orphans
userfetch"
GENTOO_MIRRORS="ftp://gd.tuwien.ac.at/opsys/linux/gentoo/
http://mirror.uni-c.dk/pub/gentoo/ http://trumpetti.atm.tut.fi/gentoo/ "
LANG="en_US.utf8"
LC_ALL="en_US.utf8"
LINGUAS="en de"
MAKEOPTS="-j3"
PKGDIR="/var/portage/packages"
PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress
--force --whole-file --delete --delete-after --stats --timeout=180
--exclude=/distfiles --exclude=/local --exclude=/packages
--filter=H_**/files/digest-*"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/var/portage/repos/gentoo"
PORTDIR_OVERLAY="/var/portage/repos/private"
SYNC="rsync://192.168.0.1/gentoo-portage"
USE="3dnow 3dnowext X a52 aac acpi alsa amd64 beagle berkdb bitmap-fonts bzip2
cairo caps cddb cdr cli cracklib crypt cups dbus djvu dri dvd dvdr dvdread eds
emboss encode evo exif fam ffmpeg firefox flac fortran gd gdbm gif gimp gnome
gphoto2 gpm gstreamer gtk hal hddtemp iconv icu ipod ipv6 isdnlog java jpeg
jpeg2k lcms ldap libnotify lm_sensors mad matroska midi mikmod mmap mmx mmxext
mono mp3 mpeg mudflap musicbrainz ncurses nls nptl nptlonly nvidia ogg opengl
openmp pam pcre pdf perl plotutils png pppd pulseaudio python qt3support
quicktime readline reflection ruby sdl session spell spl sse sse2 ssl ssse3 svg
tcpd tetex theora threads tiff truetype truetype-fonts type1-fonts unicode usb
vcd vim-syntax vorbis xattr xml xorg xv xvid zlib" ALSA_PCM_PLUGINS="adpcm alaw
asym copy dmix dshare dsnoop empty extplug file hooks iec958 ioplug ladspa
lfloat linear meter mulaw multi null plug rate route share shm softvol"
APACHE2_MODULES="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 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" CAMERAS="canon konica ptp2
kodak" ELIBC="glibc" INPUT_DEVICES="keyboard mouse evdev" KERNEL="linux"
LINGUAS="en de" USERLAND="GNU" VIDEO_CARDS="nvidia nv"
Unset: CPPFLAGS, CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LDFLAGS,
PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS
If you wait one more day, you can go and stable a newer qof for this...details
tomorrow. :)
If you wait three weeks lonker, gnotime 2.3.0 will go stable.
Christian:
I don't think that this is the right way if you want to get things done. After
all x86 could have waited a little longer too, as because of bug 193458,
gnotime could not be installed for most users for at least 20 days. Finally,
why does gnotime need qof-0.7.5 all of a sudden?
(In reply to comment #8)
> I don't think that this is the right way if you want to get things done. After
> all x86 could have waited a little longer too, as because of bug 193458,
> gnotime could not be installed for most users for at least 20 days. Finally,
> why does gnotime need qof-0.7.5 all of a sudden?
This had no malicious intent (and bug 193458 was not relevant for x86). Only
arch teams don't want to stable a package and see a newer version requested two
days later, so I warned amd64 beforehand and anybody can decide to wait a bit
longer.
It is qof's time now (that's the only reason), I filed a stable request and
linked it to this bug, so someone working on this one here sees the connection.
Three weeks is not too much for a bug lurking around for two months, and I
will file for gnotime-2.3.0 anyway.
(In reply to comment #9)
> This had no malicious intent (and bug 193458 was not relevant for x86).
Hmm, bug 193458 comment 13 ;-). As for the rest: The way you explain it now is
perfectly fine for me - I just had another impression from your prior comments.
I'm going to ask some of our amd64 guys if they want to go with 2.2.3 or the
next version and do some additional testing with qof-0.7.5 if appropriate.
And another round for a newer version