Le jeudi, 16 juillet 2020, 18.20:10 h CEST Alexander Pevzner a écrit :
> Hi Didier,
>
> > No you didn't. I just had this mail in my outbox (but not sent) for a
> > week; it just went out now as I logged back on my laptop.
> >
> > It's just some time-warping :-)
>
> I have a similar problem on OBS, and as a dirty workaround I simply
> unpack on a build machine an archive that contains go cache of all
> downloaded dependencies. Not very convenient, but it works.
>
> If problem still exist, after a week of labtop being not used :-), I can
> put release tag on goipp. As go dependencies are versioned, I will have
> to update and re-release the ipp-usb too.
>
> Note, the goipp library is not expected to be updated very often.
Apparently it's common in the Go world to rely on unreleased/untagged Github
repositories. The tooling took the 0.0~git20200517.da79ff1 version
automatically, and this entered Debian (sid). It just sounds cleaner (to me),
to actually tag/release it as 0.1, especially if it's not going to be moving a
lot.
--
OdyXAttachment:
signature.asc
Description: This is a digitally signed message part.