From: Mark Haywood <mark.haywood@oracle.com>
To: Leon Romanovsky <leon@kernel.org>
Cc: Jason Gunthorpe <jgg@ziepe.ca>, linux-rdma@vger.kernel.org
Subject: Re: buildlib/pandoc-prebuilt
Date: Fri, 6 Jan 2023 13:38:59 -0500 [thread overview]
Message-ID: <0757d1ae-334b-38ed-883d-f95b72dd04db@oracle.com> (raw)
In-Reply-To: <Y7Zl8k7F1gDNKE9q@unreal>
On 1/5/23 12:53 AM, Leon Romanovsky wrote:
> On Wed, Jan 04, 2023 at 02:18:42PM -0500, Mark Haywood wrote:
>>
>> On 1/4/23 1:42 PM, Leon Romanovsky wrote:
>>> On Wed, Jan 04, 2023 at 01:29:24PM -0400, Jason Gunthorpe wrote:
>>>> On Wed, Jan 04, 2023 at 11:05:53AM -0500, Mark Haywood wrote:
>>>>> On 1/3/23 7:18 PM, Jason Gunthorpe wrote:
>>>>>> On Tue, Jan 03, 2023 at 06:04:21PM -0500, Mark Haywood wrote:
>>>>>>> I just extracted https://github.com/linux-rdma/rdma-core/releases/download/v44.0/rdma-core-44.0.tar.gz
>>>>>>> and noticed that buildlib/pandoc-prebuilt does not exist in v44.0. Is that
>>>>>>> intentional?
>>>>>> ?
>>>>>>
>>>>>> It looks OK:
>>>>>>
>>>>>> $ wget https://github.com/linux-rdma/rdma-core/releases/download/v44.0/rdma-core-44.0.tar.gz
>>>>>> $ tar -tzf rdma-core-44.0.tar.gz | grep -i /pandoc-prebuilt/
>>>>>> rdma-core-44.0/buildlib/pandoc-prebuilt/
>>>>>> rdma-core-44.0/buildlib/pandoc-prebuilt/caaca7667f40fff2095c23c0f40c925f1ff3edea
>>>>>> rdma-core-44.0/buildlib/pandoc-prebuilt/e2cfc53feeefa2927ad8741ae5964165b27d6aee
>>>>>> rdma-core-44.0/buildlib/pandoc-prebuilt/971674ea9c99ebc02210ea2412f59a09a2432784
>>>>>> rdma-core-44.0/buildlib/pandoc-prebuilt/241312b7f23c00b7c2e6311643a22e00e6eedaac
>>>>>> [..]
>>>>> I can't explain it. The one I pulled yesterday doesn't have them:
>>>>>
>>>>> $ tar -tzf rdma-core-44.0.tar.gz.orig | grep -i /pandoc-prebuilt
>>>>> rdma-core-44.0/buildlib/pandoc-prebuilt.py
>>>>>
>>>>> The one today does:
>>>>>
>>>>> $ tar -tzf rdma-core-44.0.tar.gz | grep -i /pandoc-prebuilt | less
>>>>> rdma-core-44.0/buildlib/pandoc-prebuilt.py
>>>>> rdma-core-44.0/buildlib/pandoc-prebuilt/
>>>>> rdma-core-44.0/buildlib/pandoc-prebuilt/caaca7667f40fff2095c23c0f40c925f1ff3edea
>>>>> rdma-core-44.0/buildlib/pandoc-prebuilt/e2cfc53feeefa2927ad8741ae5964165b27d6aee
>>>>> [..]
>>>>>
>>>>> I am sure it was user error on may part, though I don't see how. Regardless,
>>>>> it's fine now, thanks.
>>>> There is a second link:
>>>>
>>>> https://github.com/linux-rdma/rdma-core/archive/refs/tags/v44.0.tar.gz
>>>>
>>>> That does not include the pandoc, perhaps you downloaded it by
>>>> mistake?
>>>>
>>>> I don't think the releae tar file changed at least, it is generated by
>>>> a script
>>> Right, I didn't change and/or force push anything after initial release.
>>
>> No problem. As I said, I'm sure it was user error on may part. I think Jason
>> is probably right and I just downloaded from the v44.0.tar.gz link.
>>
>> I just noticed that clicking on the v44.0 tar.gz link from
>> https://github.com/linux-rdma/rdma-core/tags downloads rdma-core-44.0.tar.gz
>> on my system and it looks like it is different than https://github.com/linux-rdma/rdma-core/releases/download/v44.0/rdma-core-44.0.tar.gz.
> I tried it now and got same file which includes pandoc.
Note that I am talking about the links provided under
https://github.com/linux-rdma/rdma-core/tags page, not the
https://github.com/linux-rdma/rdma-core/releases/tag/v44.0 page.
When I click on the v44.0 tar.gz link, it downloads a file,
rdma-core-44.0.tar.gz. If I just copy the link, it has a value of
https://github.com/linux-rdma/rdma-core/archive/refs/tags/v44.0.tar.gz.
I am not sure why the file downloaded when I click on the link is named
rdma-core-44.0.tar.gz. But I can wget
https://github.com/linux-rdma/rdma-core/archive/refs/tags/v44.0.tar.gz
and the v44.0.tar.gz and rdma-core-44.0.tar.gz files are identical and
do not include the prebuilt pandocs.
That said, this is probably moot since I should be downloading
https://github.com/linux-rdma/rdma-core/releases/download/v44.0/rdma-core-44.0.tar.gz
and extracting it to get access to the prebuilt pandocs.
Thanks.
Mark
>
> Thanks
prev parent reply other threads:[~2023-01-06 18:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-03 23:04 buildlib/pandoc-prebuilt Mark Haywood
2023-01-04 0:18 ` buildlib/pandoc-prebuilt Jason Gunthorpe
2023-01-04 16:05 ` buildlib/pandoc-prebuilt Mark Haywood
2023-01-04 17:29 ` buildlib/pandoc-prebuilt Jason Gunthorpe
2023-01-04 18:42 ` buildlib/pandoc-prebuilt Leon Romanovsky
2023-01-04 19:18 ` buildlib/pandoc-prebuilt Mark Haywood
2023-01-05 5:53 ` buildlib/pandoc-prebuilt Leon Romanovsky
2023-01-06 18:38 ` Mark Haywood [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=0757d1ae-334b-38ed-883d-f95b72dd04db@oracle.com \
--to=mark.haywood@oracle.com \
--cc=jgg@ziepe.ca \
--cc=leon@kernel.org \
--cc=linux-rdma@vger.kernel.org \
/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