Hi, again. Wasn't sure how to do this but it seemed potentially appropriate to announce an already found temporary workaround as a top post. Installing "libxine2-misc-plugins" BY ITSELF subsequently also successfully installed libxine2 AND the remaining dependencies with no further aborts or uninstall attempts by "apt-get". Prior to doing so, I tested "libxine2", and it still was NOT installing at that moment.
Xine was tested for my usual limited uses, and all is fine. "dpkg -s" shows the version is now current, too. Even thinking of doing this "backdoor" approach was just something I stumbled on once in desperation. Sometimes it works, sometimes it doesn't. Just didn't occur to me to attempt the rest of the dependencies when my first backdoor'ed dependency install attempt failed. Again, this is my first bug report so likewise in please do let me know if I should have presented this response in a more appropriate bug report friendly way, including possibly NOT including as much of the original report as I did here.. Thank you again. Best wishes! Cindy Sue Causey Talking Rock, Georgia, USA On 9/29/15, Cindy Sue Causey <butterflyby...@gmail.com> wrote: > Package: libxine2 > Version: 1.2.6-1+b4 > Severity: grave > Justification: renders package unusable > > Dear Maintainer, > > Dear Maintainer, > > This is my very first bug report so please forgive any incidental missteps > in this report. I chose Severity #2 Grave because this bug fits the "renders > package uninstallable" criteria under that severity level. My thought > process is it inhibits the installation of packages that could potentially > contain your most recent security patches. > > So what happened was: Today I ran "apt-get update" followed by > "apt-show-versions -u" multiple times as is my daily routine. Results were > the same each time I manually tried to upgrade libxine2 (via "apt-get > install"). Its package install/upgrade was unsuccessful and generated the > following informative (snipped for brevity): > > libxine2 : Depends: libxine2-plugins (= 1.2.6-1); libxine2-misc-plugins (= > 1.2.6-1+b5) > E: Unable to correct problems, you have held broken packages. > > On a whim, I tried a backdoor approach via an install attempt of (randomly > chosen) libxine2-x. I immediately aborted that approach upon seeing the > following advisement: > > The following packages will be REMOVED: > libxine2 libxine2-misc-plugins libxine2-plugins xine-ui > > My approach for now will be to leave the previous libxine2 related packages > as were in anticipation that your Development Team will correct the > situation as soon as Humanly possible. > > Thank you so much for the work you do. Xine is one of my relatively few > installed Debian packages hand chosen for being Xfce4 AND user friendly. > > PS My presumption is you will not need further input as this particular type > of bug appears to be a regular, accepted occurrence in Unstable. If you do > require further feeback, please note that specifically so that I cognitively > grasp that my part of this process is not complete yet. :) > > Cindy Sue Causey > Talking Rock, Georgia, USA > > > > -- System Information: > Debian Release: stretch/sid > APT prefers unstable > APT policy: (500, 'unstable') > Architecture: amd64 (x86_64) > > Kernel: Linux 4.1.0-1-amd64 (SMP w/4 CPU cores) > Locale: LANG=, LC_CTYPE= (charmap=ANSI_X3.4-1968) > Shell: /bin/sh linked to /bin/dash > Init: systemd (via /run/systemd/system) > > Versions of packages libxine2 depends on: > ii libxine2-bin 1.2.6-1+b4 > ii libxine2-misc-plugins 1.2.6-1+b4 > ii libxine2-plugins 1.2.6-1 > > Versions of packages libxine2 recommends: > ii libxine2-doc [libxine-doc] 1.2.6-1 > ii libxine2-ffmpeg 1.2.6-1+b4 > > Versions of packages libxine2 suggests: > pn gxine <none> > ii xine-ui 0.99.9-1.2 > > -- no debconf information
