Only one of the fixes seems to apply to us and shouldn't have
affected composes.
I was also able to simplify the spec file after Phillip modified
the way he tagged releases.
Upstream used a different naming scheme for the release to solve
someone else's problem. That required us to tweak how we used
forgemeta to use the matching archive naming. The fix for that
triggered adding the tag to the release which I didn't want for
rpms based off of an actual release. So a second tweak was done
to fix that.
Phillip is about to release version 4.6 and I'd like to get some
testing in rawhide before that to make deploying any needed fix
easier.
I already ran a test that exercises the features that we use in
composes and didn't see any problems, so I'm not expecting any
problems.
Changes should slow down now and a tagged release might be a week
away. So this version might get pushed down to f34 and f35 even
though the release hasn't been tagged yet.
There is now better documentation in the man page and help for
the deprecated lzma support when it is built with that enabled.
There is still a bit more stuff expected before the 4.5.1 release.
I don't expect updates to be pushed back to released versions of
Fedora until that release occurs or something unexpected happens.
The point of getting these updates into rawhide is to make it less
likely that a regression gets into the 4.5.1 release.
Phillip is going to issue a new point release soon. Adding man pages is
the main thing to still be done. There are a few changes since our last
bug fix update. I want to get a little wider testing of the changes
before Phillip tags the new release. I'd rather not find something
just after the releae like what happened with 4.5.
I'm not going to push this to released versions of Fedora. Once the
new point release is out, I expect to eventually push that to released
versions of Fedora.
These are pretty minor and I wasn't planning on building anywhere but
rawhide for the time being. I think there is a good chance of additional
minor updates within a month or two. In particular, it would make sense
to tag a minor release. But I'd like to get a little wider testing of
the changes so far, because we found some issues right after the last
tagged release, because we didn't do enough testing.
Another write outside destination directory issue was fixed
post 4.5. While 4.5.1 should be out soon, I wanted to get
this out since the release date isn't known yet.
From a comment on the bug:
This is a regression caused by rewriting the duplicate checking code
to be more aggressive when looking for duplicates when using tail-end
packing. In particular a file doesn't now have to be the same size
to be considered a (partial) duplicate.
his is a bare bones update to test the release. There were a lot of
changes and 2 new sym lynced names. The programs help has info
about this. But the man pages are missing a lot and still need to
be updated. Potentially command line changes could break composes,
though I am not expecting that.
