<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Nasty bug in UnZip 6.00d (&amp;quot;BETA&amp;quot;) - BAD_DIRSIZE, BAD_DIRTYPE, ... in Operating System - OpenVMS</title>
    <link>https://community.hpe.com/t5/operating-system-openvms/nasty-bug-in-unzip-6-00d-quot-beta-quot-bad-dirsize-bad-dirtype/m-p/5100185#M25488</link>
    <description>The source kit for UnZip 6.00d (pre-release,&lt;BR /&gt;"BETA"):&lt;BR /&gt;&lt;BR /&gt;&lt;A href="ftp://ftp.info-zip.org/pub/infozip/beta/unzip60d.zip" target="_blank"&gt;ftp://ftp.info-zip.org/pub/infozip/beta/unzip60d.zip&lt;/A&gt;&lt;BR /&gt;&lt;A href="http://downloads.sourceforge.net/infozip/unzip60d.zip" target="_blank"&gt;http://downloads.sourceforge.net/infozip/unzip60d.zip&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;contains a nasty bug.  The bug was fixed last&lt;BR /&gt;year, but apparently the fix got lost, and I&lt;BR /&gt;didn't notice it soon enough.  When unpacking a&lt;BR /&gt;"-V" archive on a VMS system, UnZip may produce&lt;BR /&gt;corrupt directories.  ANALYZE /DISK_STRUCTURE&lt;BR /&gt;will emit complaints like BAD_DIRSIZE,&lt;BR /&gt;BAD_DIRTYPE, and so on, and something like&lt;BR /&gt;ANALYZE /DISK_STRUCTURE /REPAIR will be needed&lt;BR /&gt;to straighten things out again.&lt;BR /&gt;&lt;BR /&gt;This problem is likely to occur when more files&lt;BR /&gt;existed in a directory than were included in&lt;BR /&gt;the archive when Zip ("-V") created the&lt;BR /&gt;archive.  Then, when UnZip expands the archive,&lt;BR /&gt;it may erroneously restore some directory&lt;BR /&gt;attributes other than date-time (for example,&lt;BR /&gt;size!), and the result is a corrupt directory.&lt;BR /&gt;&lt;BR /&gt;   A new (probably better/safer) [.vms]vms.c&lt;BR /&gt;file should be available here:&lt;BR /&gt;&lt;BR /&gt;&lt;A href="ftp://antinode.org/info-zip/unzip60d/vms/vms.c" target="_blank"&gt;ftp://antinode.org/info-zip/unzip60d/vms/vms.c&lt;/A&gt;&lt;BR /&gt;&lt;A href="http://antinode.org/ftp/info-zip/unzip60d/vms/vms.c" target="_blank"&gt;http://antinode.org/ftp/info-zip/unzip60d/vms/vms.c&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;I'm sorry for the trouble.  With any luck (and&lt;BR /&gt;a bit more carefullness), it'll be right in&lt;BR /&gt;6.00e and up.</description>
    <pubDate>Thu, 27 Mar 2008 17:58:40 GMT</pubDate>
    <dc:creator>Steven Schweda</dc:creator>
    <dc:date>2008-03-27T17:58:40Z</dc:date>
    <item>
      <title>Nasty bug in UnZip 6.00d ("BETA") - BAD_DIRSIZE, BAD_DIRTYPE, ...</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/nasty-bug-in-unzip-6-00d-quot-beta-quot-bad-dirsize-bad-dirtype/m-p/5100185#M25488</link>
      <description>The source kit for UnZip 6.00d (pre-release,&lt;BR /&gt;"BETA"):&lt;BR /&gt;&lt;BR /&gt;&lt;A href="ftp://ftp.info-zip.org/pub/infozip/beta/unzip60d.zip" target="_blank"&gt;ftp://ftp.info-zip.org/pub/infozip/beta/unzip60d.zip&lt;/A&gt;&lt;BR /&gt;&lt;A href="http://downloads.sourceforge.net/infozip/unzip60d.zip" target="_blank"&gt;http://downloads.sourceforge.net/infozip/unzip60d.zip&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;contains a nasty bug.  The bug was fixed last&lt;BR /&gt;year, but apparently the fix got lost, and I&lt;BR /&gt;didn't notice it soon enough.  When unpacking a&lt;BR /&gt;"-V" archive on a VMS system, UnZip may produce&lt;BR /&gt;corrupt directories.  ANALYZE /DISK_STRUCTURE&lt;BR /&gt;will emit complaints like BAD_DIRSIZE,&lt;BR /&gt;BAD_DIRTYPE, and so on, and something like&lt;BR /&gt;ANALYZE /DISK_STRUCTURE /REPAIR will be needed&lt;BR /&gt;to straighten things out again.&lt;BR /&gt;&lt;BR /&gt;This problem is likely to occur when more files&lt;BR /&gt;existed in a directory than were included in&lt;BR /&gt;the archive when Zip ("-V") created the&lt;BR /&gt;archive.  Then, when UnZip expands the archive,&lt;BR /&gt;it may erroneously restore some directory&lt;BR /&gt;attributes other than date-time (for example,&lt;BR /&gt;size!), and the result is a corrupt directory.&lt;BR /&gt;&lt;BR /&gt;   A new (probably better/safer) [.vms]vms.c&lt;BR /&gt;file should be available here:&lt;BR /&gt;&lt;BR /&gt;&lt;A href="ftp://antinode.org/info-zip/unzip60d/vms/vms.c" target="_blank"&gt;ftp://antinode.org/info-zip/unzip60d/vms/vms.c&lt;/A&gt;&lt;BR /&gt;&lt;A href="http://antinode.org/ftp/info-zip/unzip60d/vms/vms.c" target="_blank"&gt;http://antinode.org/ftp/info-zip/unzip60d/vms/vms.c&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;I'm sorry for the trouble.  With any luck (and&lt;BR /&gt;a bit more carefullness), it'll be right in&lt;BR /&gt;6.00e and up.</description>
      <pubDate>Thu, 27 Mar 2008 17:58:40 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/nasty-bug-in-unzip-6-00d-quot-beta-quot-bad-dirsize-bad-dirtype/m-p/5100185#M25488</guid>
      <dc:creator>Steven Schweda</dc:creator>
      <dc:date>2008-03-27T17:58:40Z</dc:date>
    </item>
    <item>
      <title>Re: Nasty bug in UnZip 6.00d ("BETA") - BAD_DIRSIZE, BAD_DIRTYPE, ...</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/nasty-bug-in-unzip-6-00d-quot-beta-quot-bad-dirsize-bad-dirtype/m-p/5100186#M25489</link>
      <description>Only an announcement.</description>
      <pubDate>Thu, 27 Mar 2008 17:59:53 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/nasty-bug-in-unzip-6-00d-quot-beta-quot-bad-dirsize-bad-dirtype/m-p/5100186#M25489</guid>
      <dc:creator>Steven Schweda</dc:creator>
      <dc:date>2008-03-27T17:59:53Z</dc:date>
    </item>
  </channel>
</rss>

