[blfs-dev] .. r15999 - in trunk/BOOK: general/sysutils introduction/welcome
Fernando de Oliveira
famobr at yahoo.com.br
Wed May 20 04:50:40 PDT 2015
On 20-05-2015 07:58, Fernando de Oliveira wrote:
> On 19-05-2015 23:28, Bruce Dubbs wrote:
>> Fernando de Oliveira wrote:
>>>> Fernando, if you had used 'svn blame | less' you would probably have
>>>> spotted that I changed this in r15811.
>>> $ svn blame | less
>>> svn: E205001: Try 'svn help blame' for more information
>>> svn: E205001: Poucos argumentos fornecidos
>> svn blame ./general/sysutils/unzip.xml
>> works for me.
> OK, just learned how to do it. But could not find my older commit.
>>> I was banned from git, because asked there about an error in the tests,
>>> related to unzip. This was considered a spam. Now, I am in their filter.
>>> Fortunately, one developer sent me a private message with the fix that I
>>> included in the book.
>> Interesting. However I don't understand the relationship between git
>> and unzip. Is there a regression test that uses unzip? We don't mention
>>> If ou made the change and the git test does not fail, I don't mind, your
>>> commands are better, if everything is OK, and the unzip tests are not
>>> very relevant.
>>> IIRC, what mattered for me was the -DNO_LCHMOD.
>>>> Second, it means what we have identical instructions for i686 and
>>>> x86_64. I reagard that as a Good Thing.™
>>> Agree, again, if git tests are OK.
>> I agree too.
>>> Douglas, I will revert my modification tomorrow. My ventilator broke,
>>> and i'm under more than 35 Celsius.
> Will do it soon. Was searching the problem I referred to.
>> I might add that instead of just changing something after a recent
>> modification by another editor, asking on -dev generally clears things up.
> Problem was not with git, but with mercurial:
> $ rm -rf tmp && ./run-tests.py --debug --tmpdir tmp test-archive-symlinks.t
> + unzip archive.zip
> lchmod (file attributes) error: Function not implemented
> + echo SALT1391445401.18 35 0
> SALT1391445401.18 35 0
> + cd zip
> + echo SALT1391445401.18 36 0
> SALT1391445401.18 36 0
> + /tmp/mercurial-2.9/tests/readlink.py dangling
> dangling -> nothing
> + echo SALT1391445401.18 39 0
> SALT1391445401.18 39 0
> + cd ..
> + echo SALT1391445401.18 40 0
> SALT1391445401.18 40 0
> # Ran 1 tests, 0 skipped, 0 failed.
> Then, I received a private post (can forward privately, but here, will
> remove poster info, don't want to give him trouble):
> On 03-02-2014 20:12, [Hidden Sender] wrote:
>> On Mon, 2014-02-03 at 19:58 -0300, Fernando de Oliveira wrote:
>>> Em 03-02-2014 14:18, Fernando de Oliveira escreveu:
>>>> RE: [issue2667] failure in test-archive-symlinks.t
>>>> I would like to confirm that I have the same problem.
>>>> I noticed this problem with version 2.8.2 and it also occurs with
>>>> version 2.9.
>>>> Curiously, if I run the test with the --debug switch, it passes,
>>>> although the apparent source for the error is there "lchmod (file
>>>> attributes) error: Function not implemented":
>>>> lchmod (file attributes) error: Function not implemented
>> This is a known problem with some builds of unzip as shipped by some
>> distributions. Please complain to your distro and ask them to add
>> -DNO_LCHMOD to their build.. because Linux doesn't have lchmod.
> Then I fixed the book for i?86, because the sed was not working as was:
> : Fix UnZip-6.0 Instructions.
> --- a/trunk/BOOK/general/sysutils/unzip.xml
> +++ b/trunk/BOOK/general/sysutils/unzip.xml
> @@ -184,5 +184,5 @@
> <screen><userinput>case `uname -m` in
> - sed -i -e 's/DASM"/DASM -DNO_LCHMOD"/' unix/Makefile
> + sed -i -e 's/DASM_CRC"/DASM_CRC -DNO_LCHMOD"/' unix/Makefile
> make -f unix/Makefile linux
> The rest is my present problem:
> 15811 ken <para><parameter>make -f unix/Makefile
> : More GCC5 Tags Removed non-existent unzip test suite
> 15999 fernando <para>To test the results, issue: <command>make
> Going to send a private mail about gnupg, then revert my commit, and
> reply to this.
Hope the fix at revision 16003, which is also an apology to all, is enough.
Also, sorry, but will not be running test suites in new updates, until
this trauma I'm feeling now is gone.
More information about the blfs-dev