| 1 |
Graham Murray posted on Fri, 18 Nov 2011 18:57:43 +0000 as excerpted: |
| 2 |
|
| 3 |
> It seems that almost every time a new KDE version is keyworded ~arch in |
| 4 |
> the KDE overlay[1] that none (or at most 1 or 2) of the tarballs can be |
| 5 |
> fetched. The tarballs must exist otherwise the maintainers would not be |
| 6 |
> able to generate the manifests. |
| 7 |
> |
| 8 |
> [1] Today it is version 4.7.80 |
| 9 |
|
| 10 |
If you look at the kde upstream schedules... |
| 11 |
|
| 12 |
bookmarkable general link: http://techbase.kde.org/Schedules |
| 13 |
|
| 14 |
4.8: http://techbase.kde.org/Schedules/KDE4/4.8_Release_Schedule |
| 15 |
|
| 16 |
... You'll see this: |
| 17 |
|
| 18 |
>>>>> |
| 19 |
|
| 20 |
Thursday, November 17, 2011: KDE SC 4.8 Beta 1 Tagging |
| 21 |
|
| 22 |
Trunk is frozen for beta release tagging. Only urgent fixes, such as |
| 23 |
those fixing compilation errors, should be committed. The usual beta |
| 24 |
rules apply as soon as the Beta tarballs have been generated. |
| 25 |
|
| 26 |
Wednesday, November 23, 2011: KDE SC 4.8 Beta 1 Release |
| 27 |
|
| 28 |
The beta becomes available for general consumption. |
| 29 |
|
| 30 |
<<<<< |
| 31 |
|
| 32 |
If you read a bit more of the schedule, as well as check the gentoo/kde |
| 33 |
overlay's gitlog (change into the overlay dir and run git whatchanged), |
| 34 |
what you'll find is this: |
| 35 |
|
| 36 |
About a week before a kde version is announced to the public and tarballs |
| 37 |
made available for public download, it's tagged and preliminary tarballs |
| 38 |
made available to the distros for testing and creating their own builds. |
| 39 |
In this way, on the day of the announcement, they can already link to |
| 40 |
packages available from cooperating distros, who have been able to build |
| 41 |
them based on the preview copies they were able to get before the public |
| 42 |
announcement and release. |
| 43 |
|
| 44 |
However, it's worth noting that these preview tarballs aren't always |
| 45 |
exactly the same as the ones finally made available on public release |
| 46 |
day. Often there's a show-stopper bug or two discovered after the pre- |
| 47 |
release, that's fixed for the public announcement and release. It seems |
| 48 |
that nearly ever time, at least one of the tarballs is updated in the |
| 49 |
interim. Again, if you check the overlay commit logs, you'll see the |
| 50 |
entries where they update the manifests accordingly. That's also why if |
| 51 |
you try building the first day after public release, often packages based |
| 52 |
on one tarball or another fail the manifest check -- upstream changed the |
| 53 |
tarballs after the pre-release, and the gentoo/kde overlay hasn't caught |
| 54 |
up yet. |
| 55 |
|
| 56 |
What all that means in practice is that 4.8-beta1 (aka 4.7.80) hasn't yet |
| 57 |
been publicly released. It's only available to the distro kde |
| 58 |
maintainers. Wait until the 23rd or so (sometimes it's a day late, so |
| 59 |
try the 24th, or even the 25th), then try updating. |
| 60 |
|
| 61 |
Meanwhile, the gentoo/kde folks have been TRYING to keep those pre- |
| 62 |
releases hard-masked until public release, and they've had a chance to |
| 63 |
verify that their manifests still match those of the public release. |
| 64 |
However, that's a work in progress, and sometimes they forget, or they |
| 65 |
mask most of it but miss a package or two, which then try to pull in the |
| 66 |
rest of the update when they try to upgrade, causing problems because |
| 67 |
most of that version is still hard-masked. |
| 68 |
|
| 69 |
What you can usually do as a workaround, is take the closest |
| 70 |
package.(un)mask and/or package.keywords file from the kde overlay's |
| 71 |
Documentation dir and drop it in your /etc/portage/package.mask/ dir (or |
| 72 |
copy the list into the file, if you're still using a file instead of a |
| 73 |
dir). |
| 74 |
|
| 75 |
That usually fixes it, unless your other package.unmask entries are too |
| 76 |
broad, for example >=kde-base/kdelibs-4.7 or <=kde-base/kdelibs-4.8 |
| 77 |
instead of <=kde-base/kdelibs-4.7.50, if you were previously trying to |
| 78 |
early-unmask new 4.7 series versions, since 4.7.80 is really 4.8-beta1, |
| 79 |
and unmasks override masks. |
| 80 |
|
| 81 |
Also, as I said, sometimes a package slips thru the cracks and isn't |
| 82 |
listed on the (un)mask/keywords list, in which case you'll have to add |
| 83 |
it, to reestablish order. |
| 84 |
|
| 85 |
Just don't forget to delete that mask-file after the public release, |
| 86 |
assuming of course that you want to update to it as soon as you can. =:^) |
| 87 |
|
| 88 |
|
| 89 |
-- |
| 90 |
Duncan - List replies preferred. No HTML msgs. |
| 91 |
"Every nonfree program has a lord, a master -- |
| 92 |
and if you use the program, he is your master." Richard Stallman |
Archives