SMEG (which is supposed to be called alacarte according to bug #111376) cannot find the cairo module when run. Originally it couldn't find the pygtk module but a re-emerge sorted that but now i get the cairo error. The exact error is as follows: Achilles george # smeg Traceback (most recent call last): File "/usr/bin/smeg", line 31, in ? from DialogHandler import DialogHandler File "/usr/lib/smeg/DialogHandler.py", line 30, in ? import gtk, gtk.glade File "/usr/lib64/python2.4/site-packages/gtk-2.0/gtk/__init__.py", line 38, in ? from _gtk import * ImportError: No module named cairo Emerge info: Portage 2.1_pre4-r1 (default-linux/amd64/2006.0, gcc-3.4.5, glibc-2.3.6-r3, 2.6.15-gentoo-r5 x86_64) ================================================================= System uname: 2.6.15-gentoo-r5 x86_64 AMD Athlon(tm) 64 Processor 3700+ Gentoo Base System version 1.12.0_pre16 ccache version 2.4 [enabled] 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-r1 sys-devel/binutils: 2.16.1-r1 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=k8 -O2 -pipe" CHOST="x86_64-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config /usr/lib/X11/xkb /usr/lib64/mozilla/defaults/pref /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-march=k8 -O2 -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig ccache distlocks sfperms strict" GENTOO_MIRRORS="ftp://mirrors.blueyonder.co.uk/mirrors/gentoo ftp://ftp.mirrorservice.org/sites/www.ibiblio.org/gentoo/" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" SYNC="rsync://rsync.uk.gentoo.org/gentoo-portage" USE="amd64 X alsa avi berkdb bitmap-fonts cdr crypt cups dvd eds emboss encode foomaticdb fortran gif gnome gpm gstreamer gtk gtk2 imlib ipv6 jpeg lzw lzw-tiff mp3 mpeg ncurses nls nptl nvidia offensive opengl pam pdflib perl png python quicktime readline sdl spell ssl tcpd tiff truetype-fonts type1-fonts usb userlocales vorbis xmms xpm xv xvid zlib elibc_glibc kernel_linux userland_GNU" Unset: ASFLAGS, CTARGET, EMERGE_DEFAULT_OPTS, LANG, LC_ALL, LDFLAGS, LINGUAS, PORTDIR_OVERLAY
Re-assign wrt Bug 23545, maintainer retired.
smeg has moved to alacarte (bug 111376) and should be available in portage tree when GNOME 2.16 will be released.
I mean, I think this bug should be closed and smeg should be dropped from the tree since it's old and bad for heart... :)
(In reply to comment #2) > smeg has moved to alacarte (bug 111376) and should be available in portage tree > when GNOME 2.16 will be released. > But it isn't yet...
x11-misc/alacarte in the tree, sending this corpse to treecleaners.
Pending Removal Oct 16th
well smeg still works here so why are you masking it now... alacart isnt available out of package.mask either and will not update without calling in 2.15 deps... so shouldnt you leave smeg unmasked then issue a block with alacarte if smeg is installed... or have it force and upgrade when gnome-2.16 is at least ~arch
(In reply to comment #7) > well smeg still works here so why are you masking it now... Because it's dead, missing a maintainer and alacarte replaces it. We don't need dead junk in the tree. ;)
But if there either isn't a replacement for it or the replacement isn't ready what is the point? When alacarte replaces it and it isn't masked then it should be removed. I see no security bugs about it.
Dead junk shouldn't be in the tree, no. However, dead stuff (where stuff != junk) is just that, dead. It's not moving. It's not imposing any threat of any kind. However, what you want is for us (for whom Smeg actually works like a charm), is to go on without a menu editor until Gnome 2.16 (with Alacarte) is unmasked. Why? Do you have an alternative while we wait? Until there is an alternative/replacement for Smeg (such as Alacarte) available, unmasked and in stable (at least on the architectures Smeg is/was), I wouldn't call Smeg junk. Junk can be thrown out, but this piece of alleged junk is so far non-replaceable.
actually, if you right click on the menu you will get the gnome-simple-menu-editor. It's simpler than smeg but smeg/old versions of alacarte actually doesn't work on every computer as you can see searching through bugzilla, whereas g-s-m-e works everywhere AFAIK
I agree with comments #7 and #9, why mask smeg now when alacarte is still masked as well? I can understand masking smeg once alacarte is unmasked, but why have both masked? Yes, smeg should be removed, but why not wait until it's replacement is available? As for comment #11, yes there is that, but it doesn't let you modify any of the actual menu entries, change icons, modify the description, etc...
I disagree with the removal too. You could mask it and comment to tell why the mask (ebuild needs a some love and a maintainer), but not remove until there is something decent and available to replace it. In the comments you could also tell how to unmask it (/etc/portage/package.unmask) with a warning: "it could be broken on your system, so don't report any bug" If you really want to remove it, then I (amongst many) will have to copy the ebuild to an overlay How about a few words in the next GWN ? asking for a maintainer ? to warn people about the masking/removal ?
well masking the package before removing it is part of the procedure, so you would have 30 days before it is really removed anyway. Just to be clear, smeg does not exist anymore, it is old name and old code of alacarte. Moreover smeg is broken as we can see in this bug report and so I think it is useless for people to keep going with something rusting and that they are complaining about. Even original author doesn't care anymore about those versions (the link in the ebuild leads to no post).
Removed.
