public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Patrick Lauer <gentoo@toso-digitals.de>
To: gentoo-dev@gentoo.org
Subject: [gentoo-dev] xine-lib
Date: Fri, 17 Oct 2003 19:20:40 +0200	[thread overview]
Message-ID: <1066411240.4207.15.camel@localhost> (raw)

[-- Attachment #1: Type: text/plain, Size: 990 bytes --]

Hi,

while doing an emerge -U world the compilation of xine-lib stopped:
 
* Please uninstall older xine libraries.
* The compilation cannot procede.


This can also be found as Bug 19409. (WONTFIX)
So an emerge -U world will NOT complete. Also, xine-lib-0.9.13-r3 
is installed as dependency of pornview, the next emerge -U or 
installation of xine-ui will try to install xine-lib-1-beta12 
(which will not complete). 

So:
* pornview does not work (xine-lib problems)
* Xine-ui can not be installed without emerge -C
* emerge -U functionality is broken when xine-lib is installed.

1) How did this slip through QA?
2) What is the official policy on breaking emerge -U ? I thought that's a big no-no?
3) Why is a bug that I'd consider a BLOCKER only WONTFIX ?

I hope nobody feels flamed, but this behaviour has existed for some time, and it's 
not what a normal user would want to work around. I unmerged xine-lib a few times 
because that's the easiest workaround !?


Patrick Lauer





[-- Attachment #2: Type: text/html, Size: 1307 bytes --]

             reply	other threads:[~2003-10-17 17:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-17 17:20 Patrick Lauer [this message]
2003-10-17 19:05 ` [gentoo-dev] xine-lib Andrew Gaffney
2003-10-17 19:19   ` C. Brewer
2003-10-18  2:29     ` Andrew Gaffney
2003-10-18 11:02       ` Horror Vacui
2003-10-18 11:33       ` Peter Ruskin
2003-10-17 19:29 ` Paul de Vrieze
2003-10-17 20:37   ` AW: " Martin Holzer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1066411240.4207.15.camel@localhost \
    --to=gentoo@toso-digitals.de \
    --cc=gentoo-dev@gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox