Summary: | virtual/x11 should be removed | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Arfrever Frehtes Taifersar Arahesis (RETIRED) <arfrever> |
Component: | New packages | Assignee: | Gentoo X packagers <x11> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | armin76, jakub, ssuominen |
Priority: | High | Keywords: | PMASKED |
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | 116233, 139792, 153202, 153212, 153225, 154314, 158082 | ||
Bug Blocks: |
Description
Arfrever Frehtes Taifersar Arahesis (RETIRED)
2007-02-25 14:39:22 UTC
+1; and take the broken unported crap that noone cares about with it (Bug 116233, Bug 139792 Bug 153202). I agree. Shouldn't this just depend on 112675, which is already tracking the porting process? These can be removed once 169987 is resolved, =xfce-base/libxfce4util-4.2* =xfce-base/libxfcegui4-4.2* =xfce-base/libxfce4mcs-4.2* =xfce-base/xfce-mcs-manager-4.2* =xfce-base/xfce-mcs-plugins-4.2* =xfce-base/xfce4-panel-4.2* =xfce-base/xfwm4-4.2* =xfce-base/xfce-utils-4.2* =xfce-base/xfdesktop-4.2* =xfce-base/xfce4-session-4.2* =xfce-base/xfprint-4.2* =xfce-extra/xfwm4-themes-4.2* =xfce-extra/xfce4-appfinder-4.2* =xfce-extra/xfce4-icon-theme-4.2* =xfce-extra/xfce4-mixer-4.2* dev-libs/dbh (In reply to comment #3) > These can be removed once 169987 is resolved, > > =xfce-base/libxfce4util-4.2* > =xfce-base/libxfcegui4-4.2* > =xfce-base/libxfce4mcs-4.2* > =xfce-base/xfce-mcs-manager-4.2* > =xfce-base/xfce-mcs-plugins-4.2* > =xfce-base/xfce4-panel-4.2* > =xfce-base/xfwm4-4.2* > =xfce-base/xfce-utils-4.2* > =xfce-base/xfdesktop-4.2* > =xfce-base/xfce4-session-4.2* > =xfce-base/xfprint-4.2* > =xfce-extra/xfwm4-themes-4.2* > =xfce-extra/xfce4-appfinder-4.2* > =xfce-extra/xfce4-icon-theme-4.2* > =xfce-extra/xfce4-mixer-4.2* > dev-libs/dbh > Scratch that. We don't have anything in tree that blocks this bug anymore. Fixed bacula and masked this. Someone nuke fox-1.2.6-r2 (and restore -r3 if *really* needed - no, nothing depends on it AFAICT) and re-mask this thing. I need ia64 stable keywords for (at least) x11-libs/fox-1.2.18-r1, that's why it's still in the tree. Seems i missed the ia64 folks when doing the stabling, shame on me. (In reply to comment #7) > I need ia64 stable keywords for (at least) x11-libs/fox-1.2.18-r1, that's why > it's still in the tree. Well, it doesn't even compile, plus you've nuked 1.2.6-r3 (gcc-4 + modular X fixed) by mistake. Last i checked, -r3 wasn't even ~ia64, so i fail to see what bringing it back would help the situation over ia64 marking 1.2.18-r1 stable... (In reply to comment #9) As said above, it won't even compile. But oh well, it's "stable". ia64 doesn't have any other x11-libs/fox version stable, I dropped the stable keyword from -r2 locally, checked the whole tree, and guess what - no broken dependencies anywhere because of the dropped keyword. So, what's the magic reason why x11-libs/fox-1.2.18-r1 *must* be stable on ia64? I must be missing something obvious, I guess? The magic reason is policy. I'm not in for being slapped for dropping the last stable keyword for a package, that's all. If ia64 is not interested in fox, fine with me. Please let the team speak up and resolve the situation. Marked the following: x11-libs/fox-1.6.19 ~ia64 x11-libs/fox-1.4.34-r1 ia64 And its deps, of course. x11-libs/fox-wrapper-2 ia64 dev-util/reswrap ia64 fox-1.2.6 gone. Thanks Raul for the quick reaction. The list of packages in my system still having the virtual-x11 dependency: app-editors/emacs-21.4-r4 app-editors/gvim-7.0.174 app-editors/vim-7.0.174 app-office/lyx-1.5.0_beta1 app-text/ghostscript-esp-8.15.3 app-text/tetex-3.0_p1-r3 dev-dotnet/libgdiplus-1.2.2 dev-lang/squeak-3.9.7 dev-lang/tk-8.4.9 dev-perl/perl-tk-804.027 dev-python/pyopengl-2.0.0.44 dev-util/ddd-3.3.11 media-fonts/corefonts-1-r2 media-fonts/cronyx-fonts-2.3.1-r2 media-fonts/font-adobe-100dpi-1.0.0 media-fonts/font-adobe-75dpi-1.0.0 media-fonts/font-adobe-utopia-type1-1.0.1 media-fonts/font-bh-type1-1.0.0 media-fonts/font-cursor-misc-1.0.0 media-fonts/font-misc-misc-1.0.0 media-fonts/font-schumacher-misc-1.0.0 media-fonts/freefonts-0.10-r3 media-fonts/intlfonts-1.2.1 media-fonts/terminus-font-4.20 media-fonts/ttf-bitstream-vera-1.10-r3 media-gfx/xloadimage-4.1-r4 media-gfx/xv-3.10a-r12 media-libs/giflib-4.1.4 media-libs/gst-plugins-0.8.11 media-libs/libdc1394-1.2.1 media-libs/libsdl-1.2.11 media-libs/sdl-ttf-2.0.8 media-libs/t1lib-5.0.2 media-libs/urt-3.1b-r1 media-plugins/gst-plugins-x-0.10.4 media-plugins/gst-plugins-xvideo-0.8.11 media-plugins/gst-plugins-xvideo-0.10.4-r1 media-sound/playmidi-2.5-r1 net-misc/x11-ssh-askpass-1.2.4.1-r1 net-www/mplayerplug-in-3.35 sci-visualization/gnuplot-4.0-r1 sys-devel/gcc-4.1.1-r3 www-client/opera-9.20 x11-libs/Xaw3d-1.5-r1 x11-libs/gtk+-1.2.10-r12 x11-libs/gtk+-2.10.9 x11-libs/openmotif-2.2.3-r9 x11-libs/startup-notification-0.8 x11-libs/xforms-1.0.90-r1 x11-terms/xterm-222 (In reply to comment #14) > The list of packages in my system still having the virtual-x11 dependency It's illusion. You can safely unmerge virtual/x11 and emerge won't want to install it back. Please delete virtual/x11 since it's masked for many months. It is fixed. |