1 |
Duncan wrote: |
2 |
> What's up with kde-4.3.2? I see it's masked, but the mask was pre-4.3.2 |
3 |
> release I believe, presumably until 4.3.2 was released, it has been out |
4 |
> for several days now, and the masking comment isn't helpful at all as to |
5 |
> why it might /still/ be masked, even in the kde-testing overlay. |
6 |
> |
7 |
> Also, I see revision bumps for 4.3.1 when I'd expect to see 4.3.2 coming |
8 |
> out, and the lzma USE flag that was on testing kdelibs now seems to be |
9 |
> disappeared again as it downgrades back to gentoo-tree, etc. |
10 |
> |
11 |
> So I'm asking what's up. |
12 |
Thats quite simple, 4.3.2 stay masked until we stable 4.3.1, stablebugs are |
13 |
waiting on archies, we are hoping people will test for us. If we unmask 4.3.2 |
14 |
everyone will migrate to it so we would be stabling something not approved |
15 |
working. |
16 |
> |
17 |
> Meanwhile, what about kde-testing changelogs? When I see a -rX bump, I |
18 |
> like to see why it's happening. Similarly with USE flags coming and |
19 |
> going. kde-testing doesn't seem to include changelogs. OK, sort of, but |
20 |
> is there an easy replacement for it, besides manually browsing viewcvs or |
21 |
> whatever? It's git-based, right? I know and use git what-changed on my |
22 |
> live kernel git all the time. I suppose I could do that on the kde- |
23 |
> testing git repo as well. Is that the suggested solution or is there |
24 |
> better? I've been more or less flying blind and it's beginning to bother |
25 |
> me, so getting the problem addressed would make me a rather happier |
26 |
> camper. =:^) |
27 |
There will be no changelogs. Use git history. |
28 |
http://git.overlays.gentoo.org/gitweb/?p=proj/kde.git;a=summary |
29 |
or just cd /path/to/the/interesting/dir/ && git log ../dir/ |
30 |
> |
31 |
> And if I do find a bug, do I check for and post it @ bugs.gentoo, or |
32 |
> elsewhere? |
33 |
bugs.gentoo.org is official bugzilla for official projects. So yes you open bug in |
34 |
there. Just add prefix [kde-testing] to summary for easier identification in the |
35 |
list. |
36 |
> |
37 |
> Meanwhile, there's not a mailing list to follow what's going on more |
38 |
> closely, is there? I obviously already follow this one. I suppose it's |
39 |
> mostly IRC driven... and I'm not an IRC type of guy., |
40 |
We are IRC driven guys mostly. :D So this is best tracker for you. If you |
41 |
think this is too few informations, well bad luck, because we aint going to |
42 |
improve it probably. If you want more infos on MLs then join the irc and do |
43 |
the summaries. :P |
44 |
|
45 |
Cheers |
46 |
Tomas |