Re: #60973 zope names itself Zope in the control
On Fri, Mar 24, 2000 at 01:39:01PM +0100, Georg Bauer wrote:
> Hi!
>
> On Fri, Mar 24, 2000 at 12:42:18PM +0100, Gregor Hoffleit wrote:
> > Is it possible that you have an old version of siteaccess-zope on
> > your system ? siteaccess-zope <= 0.2.0-1 had an dependency on "Zope"
> > and that made apt angry...
>
> I looked into /var/lib/dpkg/status, and there was a Package: Zope line
> in there. And all files in /var/lib/dpkg/info where called Zope.*.
>
> I had to patch it to "zope" to get it going again. This might be because
> of older packages damaging someway back in the past something, I don't
> know dpkg that much. But someone most definitely installed a Package
> Zope instead of zope.
>
> bye, Georg
But there was never any zope package made by me which used "Zope", and
AFAIK all NMU's made also were correct (why should they change the control
file).
There was this case of siteaccess-zope using a wrong name, though, and
maybe that made dpkg/apt corrupt the status file and therefore the files???
Anyway, I'll reassign this bug to dpkg.
To the dpkg maintainer: Is it possible that dpkg (resp. apt) would install
the files in /var/lib/dpkg/info under a wrong name, because it was
confused about the capitalization of the name ?
The story was this: Once upon a time, siteaccess-zope had a dependency
on "Zope", while the package's real name was "zope". At that time, I
received reports about problems with apt that made me think apt was not
coherently handling this case of different capitalization.
Gregor
Reply to: