bug-global
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Regarding the release of v6.6.2


From: Shigio YAMAGUCHI
Subject: Re: Regarding the release of v6.6.2
Date: Tue, 15 May 2018 13:31:26 +0900

Hello,
> So, my question is: Was GNU GLOBAL 6.6.2 re-released? 

Yes, it was.
At first I have released GLOBAL-6.6.2 at 9 Feb 2018.

        http://lists.gnu.org/archive/html/info-global/2018-02/msg00000.html

But it included a big mistake. This is a mail that points out that.

        http://lists.gnu.org/archive/html/bug-global/2018-02/msg00000.html

Since it was just after release, I replaced the file without updating 
the release number. So, to be precise, there are two tarballs with the
same release number (6.6.2).
Would you please use the package on the GNU ftp site?

        https://ftp.gnu.org/pub/gnu/global/global-6.6.2.tar.gz

I am sorry for confusion.

Regards,
Shigio


2018-05-15 5:11 GMT+09:00 Patrick McCarty <address@hidden>:
Hello,

When GNU GLOBAL 6.6.2 was released back in February, the project I work
on (Clear Linux Project for Intel Architecture) soon updated to that
version.

However, when I try to rebuild the same version using the Clear Linux
tooling, the tooling refuses to build it by default because the upstream
tarball signature differs from the one cached locally. After further
investigation, I discovered that the tarball for 6.6.2 also differed
from the one cached in the project's local mirror.

So, my question is: Was GNU GLOBAL 6.6.2 re-released? More specifically,
were two release tarballs (and associated signatures) created for GNU
GLOBAL 6.6.2?

If so, can a new bug-fix version be released so that it's clear that the
source tree was modified since the original 6.6.2 release?


Regards,
-Patrick

_______________________________________________
Bug-global mailing list
address@hidden
https://lists.gnu.org/mailman/listinfo/bug-global



--
Shigio YAMAGUCHI <address@hidden>
PGP fingerprint: 
26F6 31B4 3D62 4A92 7E6F  1C33 969C 3BE3 89DD A6EB

reply via email to

[Prev in Thread] Current Thread [Next in Thread]