<div dir="ltr"><div>Thanks for the report.</div><div><br></div><div>as is common now for smaller packages I didn't upload a .tds.zip file to ctan, just a source zip containing</div><div><span style="font-family:monospace"><br></span></div><div><span style="font-family:monospace">Archive: dpctex/tabulary/tabulary-ctan.zip<br> Length Date Time Name<br>--------- ---------- ----- ----<br> 169 06-06-2024 13:48 tabulary/README.txt<br> 13946 06-06-2024 13:48 tabulary/tabulary-v010.sty<br> 31535 06-06-2024 13:48 tabulary/tabulary.dtx<br> 156 06-06-2024 13:48 tabulary/tabulary.ins<br> 327251 06-06-2024 13:48 tabulary/tabulary.pdf</span></div><div><br></div><div>so the texlive integration will need to copy the -v010.sty snapshot of the package to the latex/tabulary directory but run the .ins script to generate tabulary.sty</div><div><br></div><div>Karl, if there is something I could have put in the ctan upload form to help flag this, let me know and I'll try harder next time.</div><div><br></div><div>
<div>David<br></div>
</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sun, 9 Jun 2024 at 09:13, Akira Yokosawa <<a href="mailto:akiyks@gmail.com">akiyks@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">[+To: Karl]<br>
<br>
On Wed, 5 Jun 2024 16:19:22 +0200, Frank Mittelbach wrote:<br>
> Am 05.06.24 um 04:32 schrieb Akira Yokosawa:<br>
> <br>
>> I'm not sure but such a backward-incompatible update might need an<br>
>> option for rollback to an earlier version, like array does.<br>
>><br>
>> Then, if I encounter a similar breakage in another package,<br>
>> I will be able to say:<br>
>><br>
>> \RequirePackage{array}[=v2.5]<br>
>> \RequirePackage{tabulary}[=v0.10]<br>
>> \usepackage{foo} % not compatible with array >=2.6<br>
>><br>
>> as a workaround and to wait for the update of foo.<br>
> <br>
> I think that a rollback (via date) matching the rollback that happens with array, is useful and probably needed --- basically stick the current version in as a dated version.<br>
> <br>
> Otherwise a document freezing the version to a certain date yyy/mm/dd will stop working because the kernel and array roll back but tabulary stays put<br>
> <br>
> frank<br>
<br>
David,<br>
<br>
I see you have uploaded v0.11 to CTAN, as announced at:<br>
<br>
<a href="https://ctan.org/ctan-ann/id/mailman.9332.1717769599.3764.ctan-ann@ctan.org" rel="noreferrer" target="_blank">https://ctan.org/ctan-ann/id/mailman.9332.1717769599.3764.ctan-ann@ctan.org</a><br>
<br>
, and download from <a href="https://mirrors.ctan.org/macros/latex/contrib/tabulary.zip" rel="noreferrer" target="_blank">https://mirrors.ctan.org/macros/latex/contrib/tabulary.zip</a><br>
contains tabulary v0.11. It behaves exactly as Frank mentioned above.<br>
Thank you, both!<br>
<br>
However, after "tlmgr update --all", I get the following by running<br>
grep -A 1 "ProvidesPackage" `kpsewhich tabulary.sty<br>
<br>
\ProvidesPackage{tabulary}<br>
[2014/06/11 v0.10 tabulary package (DPC)]<br>
<br>
"kpsewhich tabulary.sty" says:<br>
<br>
/usr/local/texlive/2024/texmf-dist/tex/latex/tabulary/tabulary.sty<br>
<br>
"tlmgr info --data localrev,cat-version tabulary" says:<br>
<br>
71455,0.11<br>
<br>
I guess r71455 has tabulary v0.10 rather than v0.11.<br>
<br>
Karl, can you please have a look at it?<br>
<br>
Best Regards,<br>
Akira<br>
<br>
</blockquote></div>