CALM: error while merging uploaded packages for db (obsoleting db4.8)
Yaakov Selkowitz
yselkowitz@cygwin.com
Fri Aug 19 21:20:00 GMT 2016
On Fri, 2016-08-19 at 20:13 +0200, Dr. Volker Zell wrote:
> > Corinna Vinschen writes:
> Â Â Â Â > In the x86 area there's only a release/db4.8 dir, but no
> Â Â Â Â > release/db/db4.8 dir:
>
> Â Â Â Â > $ ls -d db*
>     > db4.8  dbus  dbus-glib
> Â Â Â Â > $ ls db4.8
>     > db4.8-4.8.30-1-src.tar.bz2  db4.8-doc  libdb4.8-
> devel  setup.hint  tcl-db4.8
> Â Â Â Â > db4.8-4.8.30-
> 1.tar.bz2      libdb4.8   md5.sum         sha512.sum
>
> Â Â Â Â > In your staging area there's only a db dir containing multiple
> db4.8
> Â Â Â Â > releated dirs in parallel:
>
> Â Â Â Â > $ ls
>     > db-6.2.23-1-src.tar.xz  db-doc     libdb-devel     setup.hint
>     > db-6.2.23-1.tar.xz      db4.8      libdb4.8-devel  tcl-db
>     > db-debuginfo            db4.8-doc  libdb6.2
>
> Â Â Â Â > This looks wrong anyway, even if you planned to obsolete 4.8.
>
> Â Â Â Â > Are you going to try further yourself (I just remove the entire
> content
>     > of your db staging dir) or do you need manual intervention?  If
> the
> Â Â Â Â > latter, what *exactly* is the desired result?
>
> Please remove everything...I know now what I did wrong and will try
> again as soon you give me the go...
>
I would ask you to hold off on 6.x. Â The licence change to AGPLv3+ is
incompatible with a number of packages which use libdb, and therefore
both Fedora and Debian have refrained from upgrading past the latest
5.3 revisions for legal reasons.
I understand this may put you in an uncomfortable position given your
employer, but it is unfortunately necessary.
--
Yaakov
More information about the Cygwin-apps
mailing list