From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin-apps@cygwin.com
Subject: Re: [ITA] po4a
Date: Sun, 15 Nov 2020 09:59:01 -0700 [thread overview]
Message-ID: <d25ecea9-08ab-3e3d-5020-371d19c1202b@SystematicSw.ab.ca> (raw)
In-Reply-To: <8bdeea6f000897964022bed5fd2562f1@xs4all.nl>
On 2020-11-15 09:28, Erwin Waterlander wrote:
> Achim Gratz schreef op 2020-11-04 18:20:
>> Erwin Waterlander writes:
>>> I fixed the BUILD_REQUIRES in the playground branch. po4 0.61 builds,
>>> but fails on test.
>>> I don't know how to fix the test.
>>
>> At least the failing permissions tests are a result of the test not
>> expecting ACL to be present. You should be able to copy the relevant
>> part of my cygport file for RCS, which has the same problem:
>>
>> https://cygwin.com/git-cygwin-packages/?p=git/cygwin-packages/rcs.git;a=blob;f=rcs.cygport
>>
>>
>> Whether you also need to drop the admin privileges you need to try out.
>>
>>> The current version 0.52 also fails on test.
>>
>> As it should.
>>
>>> I had not much time to look at the tests, or if it works for me (with
>>> failing test).
>>
>> WHen you push again to the playground branch you should now be able to
>> download an archive of the build directory. That should enable you to
>> look at the full test logs to see if there is anything that requires
>> more attention. For instance the rubydoc test fail looks like a missing
>> (test) dependency to me. You don't necessarily need to fix these up
>> when you can be sure the package otherwise works (which it looks like it
>> does).
>
>
> I don't see permission problems, or dependency problems.
> The sgml test fails, like it did in 0.52, and three new tests fail partly.
> As far as I can see the 0.61 package works. I have uploaded packages.
>
> I'm not able to push the new cygport file to the master branch.
>
> Writing objects: 100% (3/3), 452 bytes | 452.00 KiB/s, done.
> Total 3 (delta 1), reused 0 (delta 0), pack-reused 0
> remote: FATAL: W refs/heads/master git/cygwin-packages/po4a Erwin_Waterlander
> DENIED by fallthru
> remote: error: hook declined to update refs/heads/master
> To ssh://cygwin.com/git/cygwin-packages/po4a.git
> ! [remote rejected] master -> master (hook declined)
> error: failed to push some refs to 'ssh://cygwin.com/git/cygwin-packages/po4a.git'
If you haven't already done the adoption git dance - you have to clone
ssh://cygwin@cygwin.com/git/cygwin-packages/po4a.git somewhere, move the .git
dir under the dir with your ...cygport, change .git/config if required; then
tag, commit, push.
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in binary units and prefixes, physical quantities in SI.]
next prev parent reply other threads:[~2020-11-15 16:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-13 6:48 Erwin Waterlander
2020-10-13 16:34 ` Ken Brown
2020-11-04 11:44 ` Erwin Waterlander
2020-11-04 17:20 ` Achim Gratz
2020-11-15 16:28 ` Erwin Waterlander
2020-11-15 16:49 ` ASSI
2020-11-15 17:48 ` Jon Turney
2020-11-15 18:56 ` Erwin Waterlander
2020-11-15 16:59 ` Brian Inglis [this message]
2020-10-13 19:03 ` Achim Gratz
2020-11-15 17:11 ` Brian Inglis
2020-11-15 21:15 ` ASSI
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=d25ecea9-08ab-3e3d-5020-371d19c1202b@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--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).