CALM: error while merging uploaded packages for db (obsoleting db4.8)

CALM: error while merging uploaded packages for db (obsoleting db4.8)

[Dr. Volker Zell]

Hi

Can somebody who knows the current upload system better than me resolv
the following error mail (and situation) from calm:

ERROR: package 'db4.8' is at paths x86/release/db4.8 and x86/release/db/db4.8
ERROR: error while merging uploaded x86 packages for Dr. Volker Zell

I just uploaded the latest db packages and on x86 systems they should
obsolete the db4.8 packages, but somehow I messed up during upload.

Thanks
  Volker
  

Re: CALM: error while merging uploaded packages for db (obsoleting db4.8)

[Corinna Vinschen]

[-- Attachment #1: Type: text/plain, Size: 1467 bytes --]

On Aug 19 13:50, Dr. Volker Zell wrote:
> Hi
> 
> Can somebody who knows the current upload system better than me resolv
> the following error mail (and situation) from calm:
> 
> ERROR: package 'db4.8' is at paths x86/release/db4.8 and x86/release/db/db4.8
> ERROR: error while merging uploaded x86 packages for Dr. Volker Zell
> 
> I just uploaded the latest db packages and on x86 systems they should
> obsolete the db4.8 packages, but somehow I messed up during upload.

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?


Thanks,
Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

Re: CALM: error while merging uploaded packages for db (obsoleting db4.8)

[Dr. Volker Zell]

>>>>> Corinna Vinschen writes:

    > On Aug 19 13:50, Dr. Volker Zell wrote:
    >> Hi
    >> 
    >> Can somebody who knows the current upload system better than me resolv
    >> the following error mail (and situation) from calm:
    >> 
    >> ERROR: package 'db4.8' is at paths x86/release/db4.8 and x86/release/db/db4.8
    >> ERROR: error while merging uploaded x86 packages for Dr. Volker Zell
    >> 
    >> I just uploaded the latest db packages and on x86 systems they should
    >> obsolete the db4.8 packages, but somehow I messed up during upload.

    > 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...
    
    > Thanks,
    > Corinna

Thanks
  Volker
  

Re: CALM: error while merging uploaded packages for db (obsoleting db4.8)

[Yaakov Selkowitz]

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

Re: CALM: error while merging uploaded packages for db (obsoleting db4.8)

[Dr. Volker Zell]

On 19.08.2016 23:20, Yaakov Selkowitz wrote:
> 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.

OK to upgrade to latest 5.3.28 ?
http://download.oracle.com/otndocs/products/berkeleydb/html/changelog_5_3.html

Ciao
   Volker

Re: CALM: error while merging uploaded packages for db (obsoleting db4.8)

[Yaakov Selkowitz]

On Sat, 2016-08-20 at 11:13 +0200, Dr. Volker Zell wrote:
> On 19.08.2016 23:20, Yaakov Selkowitz wrote:
> > 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.
> 
> OK to upgrade to latest 5.3.28 ?
> http://download.oracle.com/otndocs/products/berkeleydb/html/changelog
> _5_3.html

Yes, please.  While you are at it, could you please add enable some
sqlite features in libdb_sql which are needed by libgda:

http://pkgs.fedoraproject.org/cgit/rpms/libdb.git/tree/libdb.spec#n223

--
Yaakov

Re: CALM: error while merging uploaded packages for db (obsoleting db4.8)

[Dr. Volker Zell]

On 21.08.2016 04:20, Yaakov Selkowitz wrote:
> On Sat, 2016-08-20 at 11:13 +0200, Dr. Volker Zell wrote:
>> On 19.08.2016 23:20, Yaakov Selkowitz wrote:
>>> 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.
>> OK to upgrade to latest 5.3.28 ?
>> http://download.oracle.com/otndocs/products/berkeleydb/html/changelog
>> _5_3.html
> Yes, please.  While you are at it, could you please add enable some
> sqlite features in libdb_sql which are needed by libgda:
>
> http://pkgs.fedoraproject.org/cgit/rpms/libdb.git/tree/libdb.spec#n223

Could you please delete the current contents of the db directories for 
both x86 and x86_64 architectures.
They still hold the 6.x versions and additionally there are db4.8 
related directories in x86 which are wrong.

I want to upload the latest 5.3 versions and obsoleting the db4.8 for x86.

Thanks
   Volker

Re: CALM: error while merging uploaded packages for db (obsoleting db4.8)

[Corinna Vinschen]

[-- Attachment #1: Type: text/plain, Size: 1290 bytes --]

On Aug 22 15:08, Dr. Volker Zell wrote:
> On 21.08.2016 04:20, Yaakov Selkowitz wrote:
> > On Sat, 2016-08-20 at 11:13 +0200, Dr. Volker Zell wrote:
> > > On 19.08.2016 23:20, Yaakov Selkowitz wrote:
> > > > 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.
> > > OK to upgrade to latest 5.3.28 ?
> > > http://download.oracle.com/otndocs/products/berkeleydb/html/changelog
> > > _5_3.html
> > Yes, please.  While you are at it, could you please add enable some
> > sqlite features in libdb_sql which are needed by libgda:
> > 
> > http://pkgs.fedoraproject.org/cgit/rpms/libdb.git/tree/libdb.spec#n223
> 
> Could you please delete the current contents of the db directories for both
> x86 and x86_64 architectures.

I cleared out the db dir.


HTH,
Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

Re: CALM: error while merging uploaded packages for db (obsoleting db4.8)

[Dr. Volker Zell]

>>>>> Corinna Vinschen writes:

    > On Aug 22 15:08, Dr. Volker Zell wrote:
    >> On 21.08.2016 04:20, Yaakov Selkowitz wrote:
    >> > On Sat, 2016-08-20 at 11:13 +0200, Dr. Volker Zell wrote:
    >> > > On 19.08.2016 23:20, Yaakov Selkowitz wrote:
    >> > > > 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.
    >> > > OK to upgrade to latest 5.3.28 ?
    >> > > http://download.oracle.com/otndocs/products/berkeleydb/html/changelog
    >> > > _5_3.html
    >> > Yes, please.  While you are at it, could you please add enable some
    >> > sqlite features in libdb_sql which are needed by libgda:
    >> > 
    >> > http://pkgs.fedoraproject.org/cgit/rpms/libdb.git/tree/libdb.spec#n223
    >> 
    >> Could you please delete the current contents of the db directories for both
    >> x86 and x86_64 architectures.

    > I cleared out the db dir.

Could somebody please check out what's wrong with my latest "db" upload
for x86_64 and x86 and the "db4.8" upload for x86 (should be obsoleted
by "db"). It somehow seems to be stuck in my staging area without
getting moved to the release area.

Thanks
  Volker
  

Re: CALM: error while merging uploaded packages for db (obsoleting db4.8)

[Achim Gratz]

Dr. Volker Zell writes:
> Could somebody please check out what's wrong with my latest "db" upload
> for x86_64 and x86 and the "db4.8" upload for x86 (should be obsoleted
> by "db"). It somehow seems to be stuck in my staging area without
> getting moved to the release area.

Did you place a !ready file?


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Wavetables for the Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#BlofeldUserWavetables

Re: CALM: error while merging uploaded packages for db (obsoleting db4.8)

[Dr. Volker Zell]

>>>>> Achim Gratz writes:

    > Dr. Volker Zell writes:
    >> Could somebody please check out what's wrong with my latest "db" upload
    >> for x86_64 and x86 and the "db4.8" upload for x86 (should be obsoleted
    >> by "db"). It somehow seems to be stuck in my staging area without
    >> getting moved to the release area.

    > Did you place a !ready file?

I thought it's not needed when doing a cygport upload. At least that's
the case with my other uploads so far.

Ciao
  Volker
  

Re: CALM: error while merging uploaded packages for db (obsoleting db4.8)

[Jon Turney]

On 23/08/2016 07:57, Dr. Volker Zell wrote:
>>>>>> Achim Gratz writes:
>
>     > Dr. Volker Zell writes:
>     >> Could somebody please check out what's wrong with my latest "db" upload
>     >> for x86_64 and x86 and the "db4.8" upload for x86 (should be obsoleted
>     >> by "db"). It somehow seems to be stuck in my staging area without
>     >> getting moved to the release area.
>
>     > Did you place a !ready file?
>
> I thought it's not needed when doing a cygport upload. At least that's
> the case with my other uploads so far.

cygport upload creates the !ready file for you.

I'm afraid calm isn't very intelligent and removes all the !ready files 
after an error has occurred, so you need to replace it to make it try to 
process the uploads again.

Anyhow, on to today's error:

> ERROR: package 'db4.8' version '4.8.30-2' source has no non-empty install tarfiles
> ERROR: error while validating merged x86 packages for Dr. Volker Zell

So, this error is caused by the fact that db4.8-4.8.30-2 source pacakge 
exists, and is non-empty, but the db4.8, db4.8-doc and libdb4.8-devel 
packages it creates are all empty obsoletion packages.

This is unusual, as in all existing cases, the superseding package (in 
this case 'db' is replacing 'db4.8') source would create the obsoletion 
packages.

I've moved db4.8-4.8.30-2-src.tar.xz aside and reset !ready to allow the 
upload to proceed.

(This is disallowed because we had a few cases where source for removed 
packages was being retained in the distro only because it was referenced 
by an obsoletion package.  This seems to be the case here with the 
db-4.8.30 source.)

I'll see if I can find a better way to handle these cases in the future.

Sorry for the inconvenience.