Re: ipp-usb 0.9.27 announce

Hi Zdenek,

you don't need to ignore. goipp can peacefully coexist with ipp-usb.

Alex.

On 7/24/24 4:37 PM, Zdenek Dohnal wrote:
> Hi Alex,
> 
> can I somehow ignore vendor dir of goipp at the moment?
> 
> goipp project is already in Fedora for several years, and now it is 
> already cloned into the newest CentOS Stream, so making it disappear 
> would be more work than it gains.
> 
> Thank you in advance!
> 
> Zdenek
> 
> On 7/23/24 21:41, Alexander Pevzner wrote:
>> Hi everybody,
>>
>> I am pleased to announce the release of ipp-usb 0.9.27.
>>
>> A few hours before I've erroneously issued a  0.9.26 release. Please, 
>> ignore it and sorry for inconvenience.
>>
>> This new release brings some bug fixes and improvements.
>>
>> 1. Previously, after introduction of [uid auth], ipp-usb attempted to 
>> obtain localhost client UID even if it was not actually required. For 
>> example, in the default, permissive configuration. If client UID could 
>> not be obtained, it could cause connection attempt to be rejected.
>>
>> As result, ipp-usb didn't work in snap, because snap configuration 
>> effectively prohibits ability to obtain client UID (this problem was 
>> noticed and reported by Till).
>>
>> Now, ipp-usb obtains client UID only if it is really required by 
>> configuration.
>>
>> 2. Fixed [uid auth] behavior on systems with IPv6 disabled in the 
>> kernel configuration and only IPv4 is enabled.
>>
>> 3. Fixed allocation of TCP ports for devices. ipp-usb attempts to 
>> persist port allocation, so once allocated, port is "bound" to device, 
>> and if device disconnected and then connected again, it will receive 
>> the same port. Strictly speaking, it is not required neither for 
>> printing nor for scanning, but this level of reproducibility should be 
>> convenient for users.
>>
>> Due to mistake, at the moment of port allocation for newly connected 
>> device only allocations of currently connected devices were taken into 
>> consideration. So port allocated for some device could be reused by 
>> newly connected device, if old device was not connected when new 
>> device arrives.
>>
>> This is fixed in this release.
>>
>> 4. External dependency, github.com/OpenPrinting/goipp, now "vendored" 
>> which means that copy of its sources included into the ipp-usb source 
>> tree. This is a standard Go practice, and consistency of "vendored" 
>> libraries is strictly controlled by Go toolchain.
>>
>> As result, there is no need to package the 
>> github.com/OpenPrinting/goipp in order to build ipp-usb; The ipp-usb 
>> package currently has no external dependencies at the moment of 
>> building. It should simplify packaging process.
>>

-- 

	Wishes, Alexander Pevzner ([email protected])