0000334: Bad sfv parsing - pzs-ng feature requests

Project Zipscript Next Generation
(bug tracker)

View Issue Details [ Jump to Notes ]

[ Issue History ] [ Print ]

ID

Project

Category

View Status

Date Submitted

Last Update

0000334

pzs-ng v1.0

zipscript

public

2005-02-24 22:08

2005-02-25 20:26

Reporter

SoD-

Assigned To

psxc

Priority

normal

Severity

minor

Reproducibility

always

Status

resolved

Resolution

fixed

Platform

OS

OS Version

Product Version

BETA5

Target Version

Fixed in Version

BETA5

Summary

0000334: Bad sfv parsing

Description

If the first sfv-file entry in the sfv is overly long (>256 chars or so) the sfv is accepted but no -missing file is created (this is ok since we don't want that long file names). Problem is that any proper sfv entries following is ignored. Therefore pzs-ng shouldn't accept the sfv in the first place. I've included a bad sfv.

Additional Information

CHANGELOG doesnt say if this is beta5 but i think so, it's r1382.

Tags

No tags attached.

buggy.sfv [^] (300 bytes) 2005-02-24 22:08

Relationships

Notes
(0000576) psxc (developer) 2005-02-25 20:26	This should be fixed in r1456. There is still some problems with paths >NAME_MAX-11 re: incomplete-indicator, but it's not fatal, and it is very improbable someone uses that long dirnames. Anyhoo, i'll look into it, and will try to fix it in a later revision.

Issue History
Date Modified	Username	Field	Change
2005-02-24 22:08	SoD-	New Issue
2005-02-24 22:08	SoD-	File Added: buggy.sfv
2005-02-25 20:23	psxc	Status	new => assigned
2005-02-25 20:23	psxc	Assigned To	=> psxc
2005-02-25 20:26	psxc	Status	assigned => resolved
2005-02-25 20:26	psxc	Fixed in Version	=> BETA5
2005-02-25 20:26	psxc	Resolution	open => fixed
2005-02-25 20:26	psxc	Note Added: 0000576

Copyright © 2000 - 2010 MantisBT Group