public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Jon Turney <jon.turney@dronecode.org.uk>
To: "cygwin-apps@cygwin.com" <cygwin-apps@cygwin.com>
Subject: Re: python-odf
Date: Wed, 22 Dec 2021 14:42:02 +0000	[thread overview]
Message-ID: <b8e8b732-07d0-655f-481f-192f4cd1b024@dronecode.org.uk> (raw)
In-Reply-To: <9dd47636-b8d5-9c42-3c1c-94a3d43fef7d@gmail.com>

On 22/12/2021 13:17, Marco Atzeri wrote:
> On 20.12.2021 23:14, Marco Atzeri wrote:
>> Hi Jon,
>> while updating python-odf for the 3.9 round I noticed that for 1.4.1-1
>> I wrongly set a arch package instead of noarch as was for 0.9.5-1.
>>
>> To solve the issue I copied the content of
>>
>> /sourceware/ftp/anonftp/pub/cygwin/x86_64/release/python-odf
>> on
>> /sourceware/ftp/anonftp/pub/cygwin/noarch/release/python-odf
>>
>>
>> and removed the
>>
>> /sourceware/ftp/anonftp/pub/cygwin/x86_64/release/python-odf
>> /sourceware/ftp/anonftp/pub/cygwin/x86/release/python-odf
>>
>> I assume the modification should propagate at the next full rebuild 
>> (that I can not trigger)
>>
>> I plan tomorrow to deploy almost all python packages
>>
> it seems to have worked
Yes, this is fine.

It's perhaps slightly non-ideal because it changes the published hash 
for the x86 python-odf 0.9.5-1 package, but I don't think this actually 
causes any problems.

(setup doesn't know the package has changed, so doesn't reinstall it, 
but that's not a problem as the contents are the same. There's perhaps 
some room for a setup feature where it records the hash of installed 
packages so it can notice this situation.)

(There used to be issues where setup would notice the a package in the 
package download cache with a mismatched hash and stop, but I think that 
is no longer the case and setup now evicts such packages from the 
package download cache.  But I don't think that applies in this case 
because a different download path will cause this package to be located 
in a different place in the package download cache)

      reply	other threads:[~2021-12-22 14:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-20 22:14 python-odf Marco Atzeri
2021-12-22 13:17 ` python-odf Marco Atzeri
2021-12-22 14:42   ` Jon Turney [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=b8e8b732-07d0-655f-481f-192f4cd1b024@dronecode.org.uk \
    --to=jon.turney@dronecode.org.uk \
    --cc=cygwin-apps@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).