Fwd: calm: cygwin package upload report from sourceware.org for Marco Atzeri

Fwd: calm: cygwin package upload report from sourceware.org for Marco Atzeri

[Marco Atzeri]

Jon,
it seems that the upload of guile2.0 am guile-2.2
need a manual intervention


-------- Weitergeleitete Nachricht --------
Betreff: calm: cygwin package upload report from sourceware.org for
Marco Atzeri
Datum: Tue, 07 Aug 2018 17:35:06 -0000

ERROR: package 'libguile2.0-devel' is at paths
x86/release/guile/libguile2.0-devel and
x86/release/guile2.0/libguile2.0-devel
ERROR: error while merging uploaded x86 packages for Marco Atzeri
SUMMARY: 2 ERROR(s), 10 INFO(s)

---
Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft.
https://www.avast.com/antivirus

Re: Fwd: calm: cygwin package upload report from sourceware.org for Marco Atzeri

[Marco Atzeri]

Am 07.08.2018 um 19:55 schrieb Marco Atzeri:
> Jon,
> it seems that the upload of guile2.0 am guile-2.2
> need a manual intervention
>
>
> -------- Weitergeleitete Nachricht --------
> Betreff: calm: cygwin package upload report from sourceware.org for
> Marco Atzeri
> Datum: Tue, 07 Aug 2018 17:35:06 -0000
>
> ERROR: package 'libguile2.0-devel' is at paths
> x86/release/guile/libguile2.0-devel and
> x86/release/guile2.0/libguile2.0-devel
> ERROR: error while merging uploaded x86 packages for Marco Atzeri
> SUMMARY: 2 ERROR(s), 10 INFO(s)

I was able to move around the needed directories by myself.

"calm" is not complaining anymore

Regards
Marco

---
Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft.
https://www.avast.com/antivirus

Re: Fwd: calm: cygwin package upload report from sourceware.org for Marco Atzeri

[Jon Turney]

On 08/08/2018 05:27, Marco Atzeri wrote:
> Am 07.08.2018 um 19:55 schrieb Marco Atzeri:
>> Jon,
>> it seems that the upload of guile2.0 am guile-2.2
>> need a manual intervention
>>
>>
>> -------- Weitergeleitete Nachricht --------
>> Betreff: calm: cygwin package upload report from sourceware.org for
>> Marco Atzeri
>> Datum: Tue, 07 Aug 2018 17:35:06 -0000
>>
>> ERROR: package 'libguile2.0-devel' is at paths
>> x86/release/guile/libguile2.0-devel and
>> x86/release/guile2.0/libguile2.0-devel
>> ERROR: error while merging uploaded x86 packages for Marco Atzeri
>> SUMMARY: 2 ERROR(s), 10 INFO(s)
> 
> I was able to move around the needed directories by myself.
> 
> "calm" is not complaining anymore

Ok, glad you got that sorted.  Sorry for the inconvenience.

You should be aware that the relarea contents are only re-read by calm 
at 00:10 UTC and every four hours thereafter.

(At the moment, it's only possible for cygwin-admin to request that scan 
happen sooner. It's on my backlog [1] to fix that.)

[1] https://cygwin.com/ml/cygwin-apps/2017-07/msg00013.html

Re: Fwd: calm: cygwin package upload report from sourceware.org for Marco Atzeri

[Jon Turney]

On 30/07/2016 14:15, Marco Atzeri wrote:
> On 30/07/2016 13:47, Jon Turney wrote:
>> But that's not usually appropriate for an old soversion of a shared
>> library (even though it has no users left in the distro, there may be
>> 3rd party packages or local builds which depend on the old soversion),
>> so it should be kept.
>
> tried also that.
>
> Leaving 6.9.0.0-4 libs as they are but calm also complains
> that the package "libMagickCore6" and "libMagickC++6_5" are incomplete.
> So I can not update ImageMagick at all.

Hmm... I don't see an attempt to do that.  Perhaps things were confused 
by some of the remove tokens remaining?

> All the files are in the stage area now, I just avoided to put
> the "!ready" tag.

Ok.  I adjusted things to keep the old soversion and set !ready and this 
seems to have moved the right things to the right places.

Note that there does seem to be a difference between these libraries, 
and between x86 and x86_64:

x86
libMagicCore6   6.9.1.3-3  empty, obsoleted by libMagickCore6_2
libMagicC++6_5  6.9.0.0-4

x86_64
libMagicCore6   6.9.0.0-4  empty, obsoleted by libMagickCore6_2
libMagicC++6_5  6.9.0.0-4

>> I'd appreciate your help in understanding if either of those cases
>> applies to these packages, or if something else is needed here...
>
> currently nothing on cygwin depends on
>
> libMagickC++6_5
> libMagickCore6
>
> They were obsoleted ~ 1 year ago
> https://sourceware.org/ml/cygwin-announce/2015-07/msg00003.html

I guess we need a better way to deal with these things.

Re: Fwd: calm: cygwin package upload report from sourceware.org for Marco Atzeri

[Marco Atzeri]

On 30/07/2016 13:47, Jon Turney wrote:
> On 30/07/2016 05:45, Marco Atzeri wrote:
>> I have some problem to remove the obsolete versions
>>
>> The usual trick before was to remove all
>>
>> x86/release/ImageMagick/-ImageMagick-6.9.0.0-4-src.tar.xz
>> x86/release/ImageMagick/libMagickC++6_5/-libMagickC++6_5-6.9.0.0-4.tar.xz
>> x86/release/ImageMagick/libMagickC++6_5/-setup.hint
>>
>> x86_64/release/ImageMagick/-ImageMagick-6.9.0.0-4-src.tar.xz
>> x86_64/release/ImageMagick/libMagickC++6_5/-libMagickC++6_5-6.9.0.0-4.tar.xz
>>
>>
>> x86_64/release/ImageMagick/libMagickC++6_5/-setup.hint
>> x86_64/release/ImageMagick/libMagickCore6/-libMagickCore6-6.9.0.0-4.tar.xz
>>
>> x86_64/release/ImageMagick/libMagickCore6/-setup.hint
>>
>> but calm seems to have problem with it.
>
> Hi,
>
> Sorry about the inconvenience.
>
> The problem that calm is complaining about here is that removing the
> last version of these packages will leave the package with no versions
> (since you want to remove the package entirely).
>
> While historically permitted by uspet, removing a package doesn't make
> much sense, currently.
>
> setup doesn't do anything about installed packages which have
> disappeared from setup.ini, so the files a removed package contains will
> linger indefinitely in any existing installs (which also creates the
> possibility of pathname collisions with future packages)
>
> Normally, where a package has been replaced or superseded by another
> package, it is updated with an empty, obsolete version, which depends on
> it's replacement, so existing installs are updated to that.
>
> But that's not usually appropriate for an old soversion of a shared
> library (even though it has no users left in the distro, there may be
> 3rd party packages or local builds which depend on the old soversion),
> so it should be kept.

tried also that.

Leaving 6.9.0.0-4 libs as they are but calm also complains
that the package "libMagickCore6" and "libMagickC++6_5" are incomplete.
So I can not update ImageMagick at all.

All the files are in the stage area now, I just avoided to put
the "!ready" tag.


> I'd appreciate your help in understanding if either of those cases
> applies to these packages, or if something else is needed here...

currently nothing on cygwin depends on

libMagickC++6_5
libMagickCore6

They were obsoleted ~ 1 year ago
https://sourceware.org/ml/cygwin-announce/2015-07/msg00003.html


Regards
Marco

Re: Fwd: calm: cygwin package upload report from sourceware.org for Marco Atzeri

[Jon Turney]

On 30/07/2016 05:45, Marco Atzeri wrote:
> I have some problem to remove the obsolete versions
>
> The usual trick before was to remove all
>
> x86/release/ImageMagick/-ImageMagick-6.9.0.0-4-src.tar.xz
> x86/release/ImageMagick/libMagickC++6_5/-libMagickC++6_5-6.9.0.0-4.tar.xz
> x86/release/ImageMagick/libMagickC++6_5/-setup.hint
>
> x86_64/release/ImageMagick/-ImageMagick-6.9.0.0-4-src.tar.xz
> x86_64/release/ImageMagick/libMagickC++6_5/-libMagickC++6_5-6.9.0.0-4.tar.xz
>
> x86_64/release/ImageMagick/libMagickC++6_5/-setup.hint
> x86_64/release/ImageMagick/libMagickCore6/-libMagickCore6-6.9.0.0-4.tar.xz
> x86_64/release/ImageMagick/libMagickCore6/-setup.hint
>
> but calm seems to have problem with it.

Hi,

Sorry about the inconvenience.

The problem that calm is complaining about here is that removing the 
last version of these packages will leave the package with no versions 
(since you want to remove the package entirely).

While historically permitted by uspet, removing a package doesn't make 
much sense, currently.

setup doesn't do anything about installed packages which have 
disappeared from setup.ini, so the files a removed package contains will 
linger indefinitely in any existing installs (which also creates the 
possibility of pathname collisions with future packages)

Normally, where a package has been replaced or superseded by another 
package, it is updated with an empty, obsolete version, which depends on 
it's replacement, so existing installs are updated to that.

But that's not usually appropriate for an old soversion of a shared 
library (even though it has no users left in the distro, there may be 
3rd party packages or local builds which depend on the old soversion), 
so it should be kept.

I'd appreciate your help in understanding if either of those cases 
applies to these packages, or if something else is needed here...

> -------- Forwarded Message --------
> Subject: calm: cygwin package upload report from sourceware.org for
> Marco Atzeri
> Date: Fri, 29 Jul 2016 20:42:02 -0700 (PDT)
> From: cygwin-no-reply@cygwin.com
> To: marco.atzeri@gmail.com
>
> INFO: package 'libMagickC++6_5' appears to be source-only as it has no
> install tarfiles, adding 'skip:' hint
> ERROR: package 'libMagickC++6_5' doesn't have any versions
> INFO: package 'libMagickCore6' appears to be source-only as it has no
> install tarfiles, adding 'skip:' hint
> ERROR: package 'libMagickCore6' doesn't have any versions
> ERROR: error while validating merged x86_64 packages for Marco Atzeri