reopen 1020290
severity 1020290 critical
stop
> Please stop playing BTS ping-pong.
STOP CLOSING BUG REPORTS WITHOUT FIXING THE PROBLEM.
> Either way it looks like you misconfigured you apt sources as you said
> earlier:
NO. I DID NOT MISCONFIGURE MY SYSTEM.
IT DOESN'T MATTER HOW MANY TIMES YOU CLAIM IT HAS BEEN MISCONFIGURED, IT IS
NOT. READ THE BUG REPORT. PAY ATTENTION TO WHAT HAS BEEN STATED SEVERAL
TIMES NOW. AT THE VERY LEAST DO YOUR OWN TESTS TO CONFIRM OR DISPROVE IT,
NOT JUST DISMISS IT WITH UNSUPPORTED STATEMENTS OF OPINION.
> # apt-get -d -u install usrmerge
> Reading package lists... Done
> Building dependency tree... Done
> Reading state information... Done
> Package usrmerge is not available, but is referred to by another package.
> This may mean that the package is missing, has been obsoleted, or
> is only available from another source
>
> That is obviously not a bug in the package. So find out why usrmerge is
> not available and then install it. It will probably also be picked up
> then.
THE SAME PROBLEM OCCURRED ON FIVE DIFFERENT SYSTEMS.
THE COPY-PASTE ABOVE IS FROM A BOG STANDARD SID VM, TOTALLY UNFUCKED WITH.
And, as I noted in a previous msg, the usrmerge package IS available,
"apt-cache show" finds it without a problem, but apt wants to install
usr-is-merged.
> But usrmerge does exist, it is available, there is an installation
candidate:
>
># apt-cache show usrmerge
>Package: usrmerge
>Version: 30+nmu1
>Installed-Size: 39
>Maintainer: Marco d'Itri
>Architecture: all
>Provides: usr-is-merged
>Depends: perl:any, libfile-find-rule-perl
It's not my responsibility to figure out what broken interactions your broken
package has with usrmerge, usr-is-merged, and apt itself. IT'S YOUR PACKAGE,
YOUR RESPONSIBILTY.
craig
--
craig sanders
