On 2016-04-15 10:50, Klaus Ethgen wrote:
Hi David,
Am Fr den 15. Apr 2016 um 9:54 schrieb David Kalnischkies:
[...]
This dash-mksh package is from a third-party repository (tg's mirbsd)
and is tagged as essential ???
Partly true. That package is from the mirbsd repository that I mainly
need
Hi David,
Am Fr den 15. Apr 2016 um 9:54 schrieb David Kalnischkies:
> Control: retitle -1 apt: deal better with non-co-installable essentials
I don't think that this is the case. See below.
> Control: severity -1 minor
As descripted below, I still think that this assumption is wrong.
> On Th
Control: retitle -1 apt: deal better with non-co-installable essentials
Control: severity -1 minor
On Thu, Apr 14, 2016 at 11:06:58AM +0100, Klaus Ethgen wrote:
> Investigating (0) dash-mksh [ amd64 ] < none -> 7 > ( shells )
> Broken dash-mksh:amd64 Kollidiert mit on dash [ amd64 ] < 0.5.8-2.2 >
Hi David,
Am Do den 14. Apr 2016 um 10:00 schrieb David Kalnischkies:
> On Wed, Apr 13, 2016 at 09:45:08AM +0100, Klaus Ethgen wrote:
> > Now cvs comes with "Suggests: mksh (>= 40~), rcs" what makes mksh always
> > installed if I issue a "apt-get dist-upgrade". I had to file the
> > preferences be
Hi
On Wed, Apr 13, 2016 at 09:45:08AM +0100, Klaus Ethgen wrote:
> Now cvs comes with "Suggests: mksh (>= 40~), rcs" what makes mksh always
> installed if I issue a "apt-get dist-upgrade". I had to file the
> preferences below to mitigate that problem.
I have cvs installed on this machine, but mk
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Package: apt
Version: 1.2.10
Severity: normal
I found a strange problem that I only see with cvs -> mksh now.
I never installed mksh on my systems willfully. But I have cvs installed
on all such systems.
Now cvs comes with "Suggests: mksh (>= 40~)
6 matches
Mail list logo
