First Last Prev Next    No search results available      Search page      Enter new bug
Bug#: 29874
Alias:
Product:
Component:
Status: RESOLVED
Resolution: FIXED
Assigned To: Robin Johnson <robbat2@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: brian tarricone <bjt23@ece.cornell.edu>
Add CC:
CC:
Remove selected CCs
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 29874 depends on: Show dependency tree
Bug 29874 blocks:
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)


Not eligible to see or edit group visibility for this bug.






View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug

Description:   Opened: 2003-09-29 00:24 0000 
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't a version bump - it's a
totally different app.  the 1.1 ebuild merged a program called 'par' that
created and could verify/repair using PAR v1 files.  the 2.0.3 ebuild merges a
program called 'par2cmdline' 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'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.

------- Comment #1 From SpanKY 2003-09-29 00:42:38 0000 ------- 

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't a version bump - it's
a totally different app.  the 1.1 ebuild merged a program called 'par' that
created and could verify/repair using PAR v1 files.  the 2.0.3 ebuild merges
a program called 'par2cmdline' 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'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.

------- Comment #2 From Robin Johnson 2003-11-14 18:10:52 0000 ------- 
fixed in CVS.
First Last Prev Next    No search results available      Search page      Enter new bug