Description of problem:
zipnote crashes when editing .zip files.
Version-Release number of selected component (if applicable):
zipenote 3.0 (July 5th 2008)
Steps to Reproduce:
1. Use `zipnote -w` to edit files within a zip archive
zipnote crashes with segfault
archive was edited
Other literature on the issue, including a patch to fix this bug:
Hi, yes, this problem is here longer time (I know about it month ago) however when I test it, new version of zipnote doesn't remove this problem and crashes too. I will look at it soon, however it seems that this bug is here few years so I don't think that's really so urgent.
A release that fixes this bug has already happened, if you read the two links I attached, version 3.1b (which is in Beta) has the fix.
I just downloaded, built, and tested 3.1c, and it worked fine in my test case, which I've attached. Considering this release is 4.5 years old, I'd imagine it's pretty stable. Don't know what the deal is with zipnotes release cycles. Additionally the 3.1 version provides support for zip files > 2GB, which is a nice feature.
To test this run the following, replacing zipnote with the executable you want to test:
printf "@ hello.txt\n@=goodbye.txt\n" | zipnote -w hello.zip
Created attachment 977853 [details]
Test zip file
For you is probably stable, but for upstream not. I will add this as soon as it will be marked as stable by upstream - with zip and unzip too. If you want use it, you can install it on your machine yourself. In other way I will create patch when I finish more important things. If you create patch, I can check it and then add it to fedora earlier.
Do you have any contact with the Info-ZIP devs? They don't want bugs opened to prompt them to make a release, but I'd like to contact the devs directly if possible, but I'm unsure of how to do that. There was even supposed to be a 31d beta release in November. Maybe if they knew that we're blocking on them having a non-beta release they might be more inclined to move forward with releasing one.
New beta was planned few months ago, however there are some bigger bugs (I don't know which are bigger for them now) and they didn't push new beta version on public. You can contact them only through their forum  after registration (and confirmation from their side if I remember well this process) with PM or topic.
There you can find info about plans and bugs. However they response sometimes with big delay - I wait for some responses even few months (if they response at all).
I think that the fastest way for new beta is creating of patches for bugs which are reported on forum and are not resolved yet. Unfortunately, it's not too much clear. If you create patch for some bug, you can look here too  for tests. If there is not test for your bug, you can write here some tests too. It saves time for testing of new patches. And this tests are used by upstream too. Test for this bug has number 41, however It's not written yet due to some unpredictable behaviour in some situations.
Oh, I see it now. I apologize for my blind eyes. I see the link to forum now. Yes, that's clear fix. I will send patched zipnote for tests. Thanks for patience.
zip-3.0-10.fc20 has been submitted as an update for Fedora 20.
zip-3.0-13.fc21 has been submitted as an update for Fedora 21.
* should fix your issue,
* was pushed to the Fedora 21 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing zip-3.0-13.fc21'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
Done. Thanks for working on this pstodulk.
zip-3.0-13.fc21 has been pushed to the Fedora 21 stable repository. If problems still persist, please make note of it in this bug report.
zip-3.0-10.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.