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

2016-08-22 Thread 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

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

2016-08-22 Thread 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

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

2016-08-22 Thread 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

Re: [ITP] FUSE 2.8

2016-08-22 Thread Corinna Vinschen
On Aug 22 02:43, Mark Geisert wrote: > On Wed, 17 Aug 2016, Corinna Vinschen wrote: > > > > Mark, did you find out how to move the repo under the Cygwin org > > > > in the meantime? Is it the "Import repository" functionality by > > > > any chance? > > > > > > Hi Corinna, > > > Bill and I worked

Re: [ITP] FUSE 2.8

2016-08-22 Thread Mark Geisert
On Wed, 17 Aug 2016, Corinna Vinschen wrote: Mark, did you find out how to move the repo under the Cygwin org in the meantime? Is it the "Import repository" functionality by any chance? Hi Corinna, Bill and I worked it out on a different thread of this conversation. I currently have a public