-
Notifications
You must be signed in to change notification settings - Fork 59
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upload new version to Debian #28
Comments
I'm going to look to push an update to Debian. For now I just want to point out that you seem to have rebased the repository, which means that I now need to start with a fresh httpdirfs repository on my end. Please, in the future, avoid at all costs rebasing commits that have been pushed to the master branch, and instead use development/feature branches. |
Yes, sorry, I did run the rebase command - I wasn't entirely sure what I was doing. I will bear that in mind in the future. |
Ok, I added a new feature to cache the directory structure, hence the version number bump. Once you finish making all the changes, let's bump the version number again. Once again, I am sorry for rebasing the repository - I definitely won't do it again! |
@fangfufu If I may make a suggestion: there's no need to create a new release every time you push a bugfix or feature. Instead, just push whatever you need to master. Once you're satisfied, let it settle for a while. Give users the chance to report bugs. Then when the code is stabilised and the last few commits are bug fixes, its a good time for a release. To be honest I don't feel it's very prudent to push code that has been just written and barely tested into Debian. This carries the risk of causing problems for users, which we want to avoid at all costs. |
@jcharaoui , I agree. I don't have much software development experience, so I am still learning the convention and etiquette. So I guess it might be a good idea to come back in two weeks and think about pushing the code to Debian. I think it is a good idea to let the code settle down a bit. I am currently testing the code by running it on my server. I am trying to cache a fairly large http directory. However, I have to say that the code in the repository is way better than the version in Debian. In particular, release 1.0.3 fixes failure when encountering directory with long listing, and release [1.1.0] fixes a memory leak during LinkTable creation - I couldn't cherry pick bug fix part of the code, so I decided to release the new feature alongside with the bug fix. |
@jcharaoui , Hey Debian Buster has been released. Shall we start working on this again? |
@jcharaoui , hey is there anything I could do to help? :-) |
@fangfufu Could you update the changelog and tag 1.1.7 ? |
I updated the change log and Makefile. I haven't created a tag for 1.1.7 yet, because you have made some changes, feel free to tag 1.1.7 once you finish making all the changes. :-) |
I tagged 1.1.7 but unfortunately it doesn't build with Debian unstable:
This probably has to do with API changes in libcurl4-openssl-dev ... |
The problem is not actually due to |
#28 (comment) In Debian's GCC 9, the linker is senstive to the ordering of the libraries and object files.
Phew, it took me a while to figure out what was going on. Ok, I fixed it now. The fix is in 97ecbff. I changed the location of It is basically this error: For more details, have a look at: |
@jcharaoui , I added some pragmas to suppress |
@fangfufu I suggest to remove the functions. I'll create a backport package that includes the required functions (via |
@jcharaoui I prefer to leave them in, unless there is a technical reason that they should be out. I don't see why we should break backward compatibility. Additionally this software might get used by non-Debian users. |
The new version had been uploaded to Debian. :-) |
This new version contains a significant new feature - permanent cache system, and various bug fixes and enhancement. I think we should package this and upload it to Debian.
I know the man page needs to be updated.
Is there anything I could do?
The text was updated successfully, but these errors were encountered: