<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<!DOCTYPE bugzilla SYSTEM "http://bugs.gentoo.org/bugzilla.dtd">

<bugzilla version="2.22.7"
          urlbase="http://bugs.gentoo.org/"
          maintainer="bugzilla@gentoo.org"
>

    <bug>
          <bug_id>29874</bug_id>
          
          <creation_ts>2003-09-29 00:24 0000</creation_ts>
          <short_desc>app-arch/par different app between 1.1 and 2.0.3</short_desc>
          <delta_ts>2003-11-14 18:10:52 0000</delta_ts>
          <reporter_accessible>1</reporter_accessible>
          <cclist_accessible>1</cclist_accessible>
          <classification_id>1</classification_id>
          <classification>Unclassified</classification>
          <product>Gentoo Linux</product>
          <component>Ebuilds</component>
          <version>unspecified</version>
          <rep_platform>All</rep_platform>
          <op_sys>Linux</op_sys>
          <bug_status>RESOLVED</bug_status>
          <resolution>FIXED</resolution>
          
          
          
          <priority>P2</priority>
          <bug_severity>normal</bug_severity>
          <target_milestone>---</target_milestone>
          
          
          
          <everconfirmed>1</everconfirmed>
          <reporter>bjt23@ece.cornell.edu</reporter>
          <assigned_to>robbat2@gentoo.org</assigned_to>
          <cc>vapier@gentoo.org</cc>

      

      
          <long_desc isprivate="0">
            <who>bjt23@ece.cornell.edu</who>
            <bug_when>2003-09-29 00:24:38 0000</bug_when>
            <thetext>i just did a sync and and world update, and app-arch/par was updated from version 1.1 to version 2.0.3.  problem is, this isn&apos;t a version bump - it&apos;s a totally different app.  the 1.1 ebuild merged a program called &apos;par&apos; that created and could verify/repair using PAR v1 files.  the 2.0.3 ebuild merges a program called &apos;par2cmdline&apos; that does the same thing, only it handles PAR v2 files.  it claims to have the ability to verify/repair using PAR v1 files, but it cannot (as far as i am able to determine) create PAR v1 files.  PARv2 hasn&apos;t really caught on yet all that well, and a lot of people (myself included) still use PARv1 when posting binaries to usenet.  with this version bump i am unable to do so without removing the new useless symlinks in /usr/bin (par, parcreate, parrecover, parverify), and downloading and manually compiling and installing the old par package.</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>vapier@gentoo.org</who>
            <bug_when>2003-09-29 00:42:38 0000</bug_when>
            <thetext>

i just did a sync and and world update, and app-arch/par was updated from
version 1.1 to version 2.0.3.  problem is, this isn&apos;t a version bump - it&apos;s
a totally different app.  the 1.1 ebuild merged a program called &apos;par&apos; that
created and could verify/repair using PAR v1 files.  the 2.0.3 ebuild merges
a program called &apos;par2cmdline&apos; that does the same thing, only it handles
PAR v2 files.  it claims to have the ability to verify/repair using PAR v1
files, but it cannot (as far as i am able to determine) create PAR v1 files.
 PARv2 hasn&apos;t really caught on yet all that well, and a lot of people (myself
included) still use PARv1 when posting binaries to usenet.  with this version
bump i am unable to do so without removing the new useless symlinks in /usr/bin
(par, parcreate, parrecover, parverify), and downloading and manually compiling
and installing the old par package.

</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>robbat2@gentoo.org</who>
            <bug_when>2003-11-14 18:10:52 0000</bug_when>
            <thetext>fixed in CVS.</thetext>
          </long_desc>
      
    </bug>

</bugzilla>