Quassel IRC 0.3.0.3 has been working great for more than 30 days here. Please consider for stabilization. Reproducible: Always Steps to Reproduce:
As the the new quassel releases depend on the newly introduced qt split ebuilds versions >4.4 we need to wait for these going stable until we can mark quassel stable. Patrick can you set the dependency field on the qt split ebuilds stabilistation request (bug #248038) or let it block this one. Unfortunately I have not the proper permissions to do so.
I suggest to stabilize quassel-0.4.0-r2. qt-4.4.2 is already stable an cmake-2.6.2-r1 is about to be stabled. See bug #259741.
I guess we'll go to 0.4.1 directly. It's a minor update to 0.4.0, which has been there since mid february. Arches, please do your magic :)
# emerge -1av =net-irc/quassel-0.4.1 These are the packages that would be merged, in order: Calculating dependencies... done! !!! All ebuilds that could satisfy ">=kde-base/kdelibs-4.1" have been masked. !!! One of the following masked packages is required to complete your request: - kde-base/kdelibs-4.2.1-r3 (masked by: ~x86 keyword) - kde-base/kdelibs-4.2.1-r2 (masked by: ~x86 keyword) - kde-base/kdelibs-4.2.1-r1 (masked by: ~x86 keyword) - kde-base/kdelibs-4.2.1 (masked by: ~x86 keyword)
(In reply to comment #4) > # emerge -1av =net-irc/quassel-0.4.1 > > These are the packages that would be merged, in order: > > Calculating dependencies... done! > > !!! All ebuilds that could satisfy ">=kde-base/kdelibs-4.1" have been masked. > !!! One of the following masked packages is required to complete your request: > - kde-base/kdelibs-4.2.1-r3 (masked by: ~x86 keyword) > - kde-base/kdelibs-4.2.1-r2 (masked by: ~x86 keyword) > - kde-base/kdelibs-4.2.1-r1 (masked by: ~x86 keyword) > - kde-base/kdelibs-4.2.1 (masked by: ~x86 keyword) > Sorry I totally forgot about the kde use flag. If we ever want this version stable, i think we have to mask this flag.
quassel-0.3.1-r4 could be stabilized, it does not yet have the kde USE-flag. However it was removed from the tree a few days ago.
Created attachment 187317 [details, diff] quassel-0.4.1.diff Another option would be bumping version 0.4.1 to -r1 and rip out the kde stuff from 0.4.1 so it can be stabilized. The changes in the attached diff should be enough.
Bumping to -r1 without or with masked kde USE flag would be ok, but only if there is some -r10 with kde support. -r1 could then be stabilized. Else users would have the kde support disappearing behind their backs.
Why not just package.use.mask the kde use flag for quassel versions expected to go stable?
(In reply to comment #9) > Why not just package.use.mask the kde use flag for quassel versions expected to > go stable? I think I have made this proposal in comment #4!? So there are two options if quassel should go stable before kde-4*. Either package.use.mask the kde flag or create a new ebuild without the optional kde support.
(In reply to comment #10) > I think I have made this proposal in comment #4!? Comment #5 of course.
(In reply to comment #9) > Why not just package.use.mask the kde use flag for quassel versions expected to > go stable? If the latest version of quassel has the kde flag use.masked, that will affect ~arch users too, so a revbump is probably needed anyway. It's just easier to not have to deal with the stuff in profiles/ all the time.
So whats the status on this?
Re-CC us if there is any movement on this.
Nothing happening...so come again when you are ready.
quassel-0.4.3 now has the kde use flag removed so it should be ready for stabilization.
amd64/x86 stable, all arches done.
