Hi Steve, > Sure. I'm guessing I just renamed the file a while back, and that's > what caused the conflict.
Thanks — I’ve dropped all the permissions on the old name, which resolves the conflict. Cheers, Neil >> I’m one of the PAUSE admins. I’m working through tidying up permissions >> conflicts that have been caused by the fact that PAUSE now consider package >> names case insensitively (due to case-insensitive filesystems, as on Windows >> and MacOS X). PAUSE doesn’t let these situations occur now, but we have some >> historical cases. I’m sorting these out so that we don’t need code in the >> toolchain for dealing with permissions conflicts. >> >> You have first-come permissions on both >> PDF::API2::Resource::XObject::Image::TIFF::File and >> PDF::API2::Resource::XObject::Image::Tiff::File; the former is what’s >> released now. AREIBENS has co-maint on both. >> >> Are you ok for me to drop the permissions on the no-longer-used >> PDF::API2::Resource::XObject::Image::Tiff::File?
