* [gentoo-user] No ebuild for mysql-extras-20060316
@ 2006-04-11 4:58 Kristian Poul Herkild
2006-04-11 5:33 ` Rumen Yotov
2006-04-11 6:40 ` Ryan Tandy
0 siblings, 2 replies; 4+ messages in thread
From: Kristian Poul Herkild @ 2006-04-11 4:58 UTC (permalink / raw
To: gentoo-user
After this mornings emerge --sync, mysql-4.1.14-r1 is marked as stable.
But when doing emerge --update --deep --newuse world, I get following
error during compiling of mysql:
!!! No message digest entry found for file "mysql-extras-20060316.tar.bz2."
!!! Most likely a temporary problem. Try 'emerge sync' again later.
!!! If you are certain of the authenticity of the file then you may type
!!! the following to generate a new digest:
!!! ebuild /usr/portage/category/package/package-version.ebuild digest
But there is no such thing as mysql-extras. So I'm confused.
Kind Regards,
Kristian Poul Herkild
--
gentoo-user@gentoo.org mailing list
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [gentoo-user] No ebuild for mysql-extras-20060316
2006-04-11 4:58 [gentoo-user] No ebuild for mysql-extras-20060316 Kristian Poul Herkild
@ 2006-04-11 5:33 ` Rumen Yotov
2006-04-11 6:40 ` Ryan Tandy
1 sibling, 0 replies; 4+ messages in thread
From: Rumen Yotov @ 2006-04-11 5:33 UTC (permalink / raw
To: gentoo-user
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Kristian Poul Herkild wrote:
> After this mornings emerge --sync, mysql-4.1.14-r1 is marked as stable.
>
> But when doing emerge --update --deep --newuse world, I get following
> error during compiling of mysql:
>
> !!! No message digest entry found for file "mysql-extras-20060316.tar.bz2."
> !!! Most likely a temporary problem. Try 'emerge sync' again later.
> !!! If you are certain of the authenticity of the file then you may type
> !!! the following to generate a new digest:
> !!! ebuild /usr/portage/category/package/package-version.ebuild digest
>
> But there is no such thing as mysql-extras. So I'm confused.
>
> Kind Regards,
> Kristian Poul Herkild
Hi,
Same here, but with 5.0.19-r1, now checking and found some diffs between
what's in 4.1.14-r1 and 5.0.19-r1 digests and the file it want to
download, specially the dates differ - 20060316 vs 20060410.
Probably this is the main cause, will check mysql.eclass where the main
part of mysql ebuild is located (the eclass seems to be the culprit here ;)
Haven't checked Bugzilla, if nothing present there please file a Bug.
PS: or if in a hurry change manually (in overlay) or make a new digest.
HTH. Rumen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2-ecc0.1.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFEOz+fNbtuTtsWD3wRAoNFAJ9mksfyuG5rl/9Ds5at9vvjuqXeJgCdEJH+
gooLTUbvhC7iE9COAzwsJMk=
=Rpmo
-----END PGP SIGNATURE-----
--
gentoo-user@gentoo.org mailing list
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [gentoo-user] No ebuild for mysql-extras-20060316
2006-04-11 4:58 [gentoo-user] No ebuild for mysql-extras-20060316 Kristian Poul Herkild
2006-04-11 5:33 ` Rumen Yotov
@ 2006-04-11 6:40 ` Ryan Tandy
2006-04-11 10:25 ` Francesco Riosa
1 sibling, 1 reply; 4+ messages in thread
From: Ryan Tandy @ 2006-04-11 6:40 UTC (permalink / raw
To: gentoo-user
Kristian Poul Herkild wrote:
> After this mornings emerge --sync, mysql-4.1.14-r1 is marked as stable.
>
> But when doing emerge --update --deep --newuse world, I get following
> error during compiling of mysql:
>
> !!! No message digest entry found for file "mysql-extras-20060316.tar.bz2."
> !!! Most likely a temporary problem. Try 'emerge sync' again later.
> !!! If you are certain of the authenticity of the file then you may type
> !!! the following to generate a new digest:
> !!! ebuild /usr/portage/category/package/package-version.ebuild digest
>
> But there is no such thing as mysql-extras. So I'm confused.
>
> Kind Regards,
> Kristian Poul Herkild
>
mysql-extras isn't an ebuild, it's just another file required for the
mysql build. Someone evidently forgot to digest that tarball when
committing the newest bump - sync again in the morning, I'm sure it'll
be OK.
--
gentoo-user@gentoo.org mailing list
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [gentoo-user] No ebuild for mysql-extras-20060316
2006-04-11 6:40 ` Ryan Tandy
@ 2006-04-11 10:25 ` Francesco Riosa
0 siblings, 0 replies; 4+ messages in thread
From: Francesco Riosa @ 2006-04-11 10:25 UTC (permalink / raw
To: gentoo-user
Ryan Tandy wrote:
> Kristian Poul Herkild wrote:
>> After this mornings emerge --sync, mysql-4.1.14-r1 is marked as stable.
>>
>> But when doing emerge --update --deep --newuse world, I get following
>> error during compiling of mysql:
>>
>> !!! No message digest entry found for file
>> "mysql-extras-20060316.tar.bz2."
>> !!! Most likely a temporary problem. Try 'emerge sync' again later.
>> !!! If you are certain of the authenticity of the file then you may type
>> !!! the following to generate a new digest:
>> !!! ebuild /usr/portage/category/package/package-version.ebuild digest
>>
>> But there is no such thing as mysql-extras. So I'm confused.
>>
>> Kind Regards,
>> Kristian Poul Herkild
>>
> mysql-extras isn't an ebuild, it's just another file required for the
> mysql build. Someone evidently forgot to digest that tarball when
> committing the newest bump - sync again in the morning, I'm sure it'll
> be OK.
Not exactly what happened but the result don't change, it should be ok
right now.
more precisely at the moment mysql-extras contains all the patches
applyed to mysql package, it can however contain additional big (> 20
kb) files that does'nt fit well in the portage tree.
regards,
Francesco
--
gentoo-user@gentoo.org mailing list
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2006-04-11 10:29 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-04-11 4:58 [gentoo-user] No ebuild for mysql-extras-20060316 Kristian Poul Herkild
2006-04-11 5:33 ` Rumen Yotov
2006-04-11 6:40 ` Ryan Tandy
2006-04-11 10:25 ` Francesco Riosa
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox