Re: Plasma desktop unusable in stretch

[Christian Hilberg]

Am Donnerstag 03 September 2015, 16:37:09 schrieb Andrey Rahmatullin:
> On Thu, Sep 03, 2015 at 12:43:37PM +0200, Christian Hilberg wrote:
> > "It's all automatic" is the bit I missed. I was under the impression
> > that this would be true for experimental->unstable only
> experimental->unstable is fully manual (even requiring a new upload).
Thanks for clarifying.


signature.asc
Description: This is a digitally signed message part.

Re: Plasma desktop unusable in stretch

[Christian Hilberg]

Hi Brad,

thanks for clarifying matters. A few more bits inline.

Am Donnerstag 03 September 2015, 14:19:53 schrieb Brad Rogers:
> On Thu, 03 Sep 2015 12:43:37 +0200
> Christian Hilberg  wrote:
> 
> Hello Christian,
> 
> >> You appear to expect somebody (well, several 
> >> somebodies) to stem the tide to avoid problems.  
> >"Expecting" is not what I meant to express, it is more like "being
> I wasn't sure, hence my writing "appear to..."  Having cleared up a
> misunderstanding about the unstable->testing migration, I can tell
> you're a lot less angry (I use the word cautiously; it may be too strong)
> about what's going on ATM.

No anger at all. Please excuse if my writings implied this.

What you call a misunderstanding about the package migration
between unstable and testing I think is better described by
the term "misconception on my side", something many may share
with me. So thanks again for taking time to explain.

> >Sure. Since there are the brave ones running unstable, I thought this
> >is where the biggest breakages were going to be caught and eliminated
> >before the packages entered testing.
> By and large, the biggest breakages _do_ occur in unstable.  The current
> situation is, in the time I've used testing (approx ten years),
> unprecedented.  I've seen the odd package or two migrate that couldn't
> be installed, but never on such a huge scale.

That's true. I'm a debian addict myself for more than 10 years
now, and haven't seen like this either. Although, I must admit,
I have not followed testing that much close.

> [...] 
> Much of the problem, AIUI, is caused by the change to GCC5 for
> Kf5/Plasma.  Just look at the number of packages held back from testing
> because of it;
> 
> Updating gcc-5 makes 408 depending packages uninstallable on amd64: 
>
> Note that that list refers to amd64 only.  It may differ on other
> architectures.  And that's just the _depending_ packages.  There's
> another 318 non-depending packages that are affected.

It might be helpful to have some mechanism handy which would allow
the release managers to easily hold off e.g. all of KDE from migrating
from unstable into testing while something like the GCC transition
is going on, and having testing just sit on the latest pre-GCCv5 version.
Once the transition is done, this "hold" flag would be removed and
the unstable packages (for KDE here) would start trickling into testing
again. But then, for something like this to work, the package dependencies
would need to already be correct... just thinking out loud, never mind. :-)

> https://release.debian.org/migration/testing.pl?package=gcc-5 has the
> full list.  It includes stuff like LibreOffice and all sort of Python
> stuff, not just KDE.

Thanks for the pointers.

> It's going to take a long time to sort it out, I'm sure.

I might bug you with some new bug reports in the meantime. :)

Kind regards,
Christian


signature.asc
Description: This is a digitally signed message part.

Re: Plasma desktop unusable in stretch

[Andrey Rahmatullin]

On Thu, Sep 03, 2015 at 06:30:13PM +0200, Matthias Bodenbinder wrote:
> Am 03.09.2015 um 18:12 schrieb Martin Steigerwald:
> >> Packages from Debian Unstable enter the next-stable testing distribution
> >> automatically, when a list of requirements is fulfilled: [...] The package
> >> does not introduce new release critical bugs.
> > 
> > So and now *who* reports these?
> > 
> > Then rethink from there.
> 
> Well, I would expect a minimum of testing from the package maintainers even 
> before a package is uploaded to unstable. I assume for the case at hand that 
> the package maintainers were pretty much aware about the broken KDE desktop. 
The maintainers are well aware that packages may behave badly during
large transitions and that shouldn't stop them from uploading, as it's the
only way forward.

-- 
WBR, wRAR


signature.asc
Description: Digital signature

Re: Plasma past G++ transition

[Jimmy Johnson]

On 09/03/2015 09:20 AM, Martin Steigerwald wrote:


Luc you could try install task-kde-desktop or install
kde-plasma-desktop, thats in testing.  In Sid, bits are still broken
like not being able to install Gimp and/or you can't do a dist-upgrade
but you can do an aptitude safe-upgrade and that is what I recommend for
both testing and unstable.


Yes you can. Well at least I could.

Calligra (including Krita) and Digikam are not there yet. Amarok, KMyMoney,
kde-full all there and working.


Be prepared that you may have to do the dist-upgrade in several steps, and
possibly partly from a tty, cause I had to.


Martin you do know that 'aptitude safe-upgrade' adds and removes 
packages as needed, don't you?



If you are not comfortable with this, wait and install some lxde or other
desktop for the time being. If you can.


Been using Debian for more than 20 yrs. I've seen many systems break and 
I fix them all, yes, I'm comfortable, thanks to Debian and my study of 
package management.

--
Jimmy Johnson

Debian - Wheezy - KDE 4.8.4 - AMD64 - EXT4 at sda1
Registered Linux User #380263

Re: Plasma desktop unusable in stretch

[Brad Rogers]

On Thu, 03 Sep 2015 16:54:32 +0200
Christian Hilberg  wrote:

Hello Christian,

>I might bug you with some new bug reports in the meantime. :)

Not me!   :-)

Like you, I'm a Debian user.  I don't represent Debian or KDE in any
way.  All opinions are my own etc, etc.

It just so happened that I could answer some of your queries.

-- 
 Regards  _
 / )   "The blindingly obvious is
/ _)radnever immediately apparent"
I'm not here for your entertainment
U & Ur Hand - P!nk


pgpO8CqiNYCgZ.pgp
Description: OpenPGP digital signature

Re: Plasma desktop unusable in stretch

[Brad Rogers]

On Thu, 03 Sep 2015 19:06:10 +0200
Diederik de Haas  wrote:

Hello Diederik,

>allotted time, the package transitions to testing. 

I was surprised to see that "allotted time" can be as little as two
days.  Which doesn't give unstable users a lot of time to discover any
real nasties.

For most packages, transition time is ten days, as I'm sure most people
know.

-- 
 Regards  _
 / )   "The blindingly obvious is
/ _)radnever immediately apparent"
Black man got a lot of problems, but he don't mind throwing a brick
White Riot - The Clash


pgprBT5HjCy1o.pgp
Description: OpenPGP digital signature

Re: Plasma desktop unusable in stretch

[Andrey Rahmatullin]

On Thu, Sep 03, 2015 at 03:03:35PM -0400, Gary Dale wrote:
> Sorry, but before releasing a major package to "testing", shouldn't it be
> tested against the "testing" environment? 
No, we don't do this.

-- 
WBR, wRAR


signature.asc
Description: Digital signature

Re: Plasma past G++ transition

[Martin Steigerwald]

Am Mittwoch, 2. September 2015, 05:37:13 schrieb Jimmy Johnson:
> On 09/02/2015 01:46 AM, Luc Castermans wrote:
> > this is very nice news!
> > 
> > However I tried to make fresh install from Testing last weekend, and
> > then get many dependency conflicts as
> > soon as I issue a "aptitide install kde-full".   In summary: I installed
> > a fresh Testing (base system), then do "aptitude install kde-full".
> > 
> > Should I add unstable to sources.list, then do "aptitude install -t sid
> > kde-full", or even from experimental?
> > 
> > Regards
> > 
> > Luc
> 
> Luc you could try install task-kde-desktop or install
> kde-plasma-desktop, thats in testing.  In Sid, bits are still broken
> like not being able to install Gimp and/or you can't do a dist-upgrade
> but you can do an aptitude safe-upgrade and that is what I recommend for
> both testing and unstable.

Yes you can. Well at least I could.

Calligra (including Krita) and Digikam are not there yet. Amarok, KMyMoney, 
kde-full all there and working.

Thanks,
-- 
Martin

Re: Plasma desktop unusable in stretch

[Christian Hilberg]

Am Donnerstag 03 September 2015, 18:12:04 schrieb Martin Steigerwald:
> Am Mittwoch, 2. September 2015, 22:46:12 schrieb Matthias Bodenbinder:
> > Am 02.09.2015 um 19:50 schrieb Gary Dale:
> > [...]
> > > the brave souls who run sid do what they, not I, signed up for.
> > I 100% support that statement. On the debian wiki
> > (https://wiki.debian.org/DebianTesting) it says:
> > 
> > Packages from Debian Unstable enter the next-stable testing distribution
> > automatically, when a list of requirements is fulfilled: [...] The package
> > does not introduce new release critical bugs.
> 
> So and now *who* reports these?

If the packages should be allowed into testing only if not
introducing new RC bugs, then the bugs must be reported
(i.e., opened) by the users of unstable, if they should
prevent the package from trickling into testing.

Then again, since the packages actually /went/ into testing,
this means that there were no new RC bugs opened by the
users of unstable -- maybe the packages were working there
and only in conjunction with the package situation in testing
the issues show.

That seems to be a pretty funny puzzle to solve.

> Then rethink from there.

Trying to. =)

Regards,
Christian

signature.asc
Description: This is a digitally signed message part.

Re: Plasma desktop unusable in stretch

[Matthias Bodenbinder]

Am 03.09.2015 um 18:12 schrieb Martin Steigerwald:
>> Packages from Debian Unstable enter the next-stable testing distribution
>> automatically, when a list of requirements is fulfilled: [...] The package
>> does not introduce new release critical bugs.
> 
> So and now *who* reports these?
> 
> Then rethink from there.

Well, I would expect a minimum of testing from the package maintainers even 
before a package is uploaded to unstable. I assume for the case at hand that 
the package maintainers were pretty much aware about the broken KDE desktop. 

Matthias

Re: Plasma desktop unusable in stretch

[Andrey Rahmatullin]

On Thu, Sep 03, 2015 at 06:16:53PM +0100, Brad Rogers wrote:
> >allotted time, the package transitions to testing. 
> I was surprised to see that "allotted time" can be as little as two
> days.  Which doesn't give unstable users a lot of time to discover any
> real nasties.
Urgencies higher than medium are used only in special cases.

> For most packages, transition time is ten days, as I'm sure most people
> know.
Five.
https://lists.debian.org/debian-devel-announce/2013/11/msg7.html


-- 
WBR, wRAR


signature.asc
Description: Digital signature

Re: Plasma desktop unusable in stretch

[Martin Steigerwald]

Am Mittwoch, 2. September 2015, 22:46:12 schrieb Matthias Bodenbinder:
> Am 02.09.2015 um 19:50 schrieb Gary Dale:
> > I know I've been using Debian for a long time. That's why I'm amazed that
> > something this bad is being put into testing. When KDE4 came along, it at
> > least was fairly stable and usable (if incomplete) before it was moved to
> > testing. If I wanted bleeding edge software that didn't necessarily work,
> > I would be running sid or pulling stuff from experimental.
> > 
> > As your quote says "Those criteria should ensure a good quality for
> > packages within testing." Putting out a broken desktop can in no way be
> > considered "good quality". I run testing because I want to test software,
> > not to get mad at the developers who volunteer their time to get the
> > packages ready for prime time. In this case the process seems to have
> > misfired by bringing us the Plasma desktop when it is nowhere near ready.
> > 
> > This is the third time in the last few weeks that I've been forced to use
> > Gnome because KDE couldn't do even basic desktop stuff. I suggest that
> > testing should revert to KDE4, if that is possible, and wait until KDE5
> > achieves some level of stability before inflicting it on us again. Let
> > the brave souls who run sid do what they, not I, signed up for.
> I 100% support that statement. On the debian wiki
> (https://wiki.debian.org/DebianTesting) it says:
> 
>   Packages from Debian Unstable enter the next-stable testing distribution
> automatically, when a list of requirements is fulfilled: [...] The package
> does not introduce new release critical bugs.

So and now *who* reports these?

Then rethink from there.

Thanks,
-- 
Martin

Re: Plasma desktop unusable in stretch

[Andrey Rahmatullin]

On Thu, Sep 03, 2015 at 12:03:04PM -0400, Gary Dale wrote:
> I've tended to view "testing" as a rolling release
That's the main misunderstanding.
We had several tries to design and/or create a rolling Debian distro but
there is nothing currently existing AFAIK.
And it takes a lot more effort than is currently spent on unstable and
testing (which is already a lot).

-- 
WBR, wRAR


signature.asc
Description: Digital signature

Re: Plasma past G++ transition

[Martin Steigerwald]

Am Mittwoch, 2. September 2015, 08:46:49 schrieb Luc Castermans:
> Op wo 2 sep. 2015 om 10:35 schreef Marco Valli :
> > In data mercoledì 2 settembre 2015 10:26:29, Martin Steigerwald ha 
scritto:
> > > Thanks to the Debian Qt/KDE team for this huge effort.
> > 
> > +1
> > 
> > --
> > Marco Valli
>
> this is very nice news!
> 
> However I tried to make fresh install from Testing last weekend, and then
> get many dependency conflicts as
> soon as I issue a "aptitide install kde-full".   In summary: I installed a
> fresh Testing (base system), then do "aptitude install kde-full".
> 
> Should I add unstable to sources.list, then do "aptitude install -t sid
> kde-full", or even from experimental?

I use Sid. I also have experimental, but I think Plasma 5 should be fully in 
Sid meanwhile.

Using Sid temporarily may help, as the G++ ABI transition seems to be 
completed there mostly. You can switch back to testing later.

Thanks,
-- 
Martin

Processing of libksysguard_5.4.0-1_amd64.changes

[Debian FTP Masters]

libksysguard_5.4.0-1_amd64.changes uploaded successfully to localhost
along with the files:
  libksysguard_5.4.0-1.dsc
  libksysguard_5.4.0.orig.tar.xz
  libksysguard_5.4.0-1.debian.tar.xz
  libkf5sysguard-bin_5.4.0-1_amd64.deb
  libkf5sysguard-data_5.4.0-1_all.deb
  libkf5sysguard-dbg_5.4.0-1_amd64.deb
  libkf5sysguard-dev_5.4.0-1_amd64.deb
  libkf5sysguard5-data_5.4.0-1_all.deb
  libkf5sysguard5_5.4.0-1_all.deb
  libksgrd7_5.4.0-1_amd64.deb
  libksignalplotter7_5.4.0-1_amd64.deb
  liblsofui7_5.4.0-1_amd64.deb
  libprocesscore7_5.4.0-1_amd64.deb
  libprocessui7_5.4.0-1_amd64.deb

Greetings,

Your Debian queue daemon (running on host franck.debian.org)

Re: Plasma desktop unusable in stretch

[Diederik de Haas]

On Thursday 03 September 2015 12:03:04 Gary Dale wrote:
> I also used to think of the "testing" package maintainers as the 
> guardians at the gate

There is no such thing. Package maintainers upload packages to unstable.
When there are no Release Critical bugs reported by *users* of unstable in the 
allotted time, the package transitions to testing. 


signature.asc
Description: This is a digitally signed message part.

Re: Plasma past G++ transition

[Martin Steigerwald]

Am Donnerstag, 3. September 2015, 23:29:07 schrieb Diederik de Haas:
> On Thursday 03 September 2015 11:22:19 Thomas Fjellstrom wrote:
> > > Using Sid temporarily may help, as the G++ ABI transition seems to be
> > > completed there mostly. You can switch back to testing later.
> > 
> > I'm not sure that's entirely accurate?
> 
> The whole libstdc++6 transition is only at 29% atm, but almost all kde
> packages are amongst that 29%.

Now if that doesn´t tell that the Debian Qt/KDE team has great package 
maintainers working on the package upgrades in their free time like crazy, I 
don´t know what is :)

Thanks,
-- 
Martin

Processing of khangman_15.08.0-1_source.changes

[Debian FTP Masters]

khangman_15.08.0-1_source.changes uploaded successfully to localhost
along with the files:
  khangman_15.08.0-1.dsc
  khangman_15.08.0.orig.tar.xz
  khangman_15.08.0-1.debian.tar.xz

Greetings,

Your Debian queue daemon (running on host franck.debian.org)

Re: Plasma desktop unusable in stretch

[Gary Dale]

On 03/09/15 03:42 PM, Andrey Rahmatullin wrote:

On Thu, Sep 03, 2015 at 03:03:35PM -0400, Gary Dale wrote:

Sorry, but before releasing a major package to "testing", shouldn't it be
tested against the "testing" environment?

No, we don't do this.


Obviously, but the question was "shouldn't you?"

Re: Plasma past G++ transition

[Martin Steigerwald]

Am Donnerstag, 3. September 2015, 10:05:59 schrieb Jimmy Johnson:
> On 09/03/2015 09:20 AM, Martin Steigerwald wrote:
> > Am Mittwoch, 2. September 2015, 05:37:13 schrieb Jimmy Johnson:
> >> On 09/02/2015 01:46 AM, Luc Castermans wrote:
> >>> this is very nice news!
> >>> 
> >>> However I tried to make fresh install from Testing last weekend, and
> >>> then get many dependency conflicts as
> >>> soon as I issue a "aptitide install kde-full".   In summary: I installed
> >>> a fresh Testing (base system), then do "aptitude install kde-full".
> >>> 
> >>> Should I add unstable to sources.list, then do "aptitude install -t sid
> >>> kde-full", or even from experimental?
> >> 
> >> Luc you could try install task-kde-desktop or install
> >> kde-plasma-desktop, thats in testing.  In Sid, bits are still broken
> >> like not being able to install Gimp and/or you can't do a dist-upgrade
> >> but you can do an aptitude safe-upgrade and that is what I recommend for
> >> both testing and unstable.
> > 
> > Yes you can. Well at least I could.
> > 
> > Calligra (including Krita) and Digikam are not there yet. Amarok,
> > KMyMoney,
> > kde-full all there and working.
> 
> Martin that is all relative to what packages you are holding.

I am holding back no packages anymore, I used "dist-upgrade" as I told. My 
system is completely on sid since yesterday, with apt-get only holding back 
some ffmpeg related packages probably due to multiarch synchronisity issues 
between i386 und amd64. My system is past G++ ABI transition:

martin@merkaba:~> apt-show-versions libstdc++6
libstdc++6:amd64/sid 5.2.1-15 uptodate
libstdc++6:i386/sid 5.2.1-15 uptodate

martin@merkaba:~> g++ --version
g++ (Debian 5.2.1-15) 5.2.1 20150808

libavresample-dev libavresample-ffmpeg2 libavutil-dev libavutil-ffmpeg54

And there calligra and digikam are currently not installable.

Thanks,
-- 
Martin

Re: Plasma past G++ transition

[Diederik de Haas]

On Thursday 03 September 2015 11:22:19 Thomas Fjellstrom wrote:
> > Using Sid temporarily may help, as the G++ ABI transition seems to be
> > completed there mostly. You can switch back to testing later.
> >
> I'm not sure that's entirely accurate?

The whole libstdc++6 transition is only at 29% atm, but almost all kde 
packages are amongst that 29%.


signature.asc
Description: This is a digitally signed message part.

Re: Plasma past G++ transition

[Martin Steigerwald]

Am Donnerstag, 3. September 2015, 10:24:06 schrieb Jimmy Johnson:
> On 09/03/2015 09:20 AM, Martin Steigerwald wrote:
> >>> Luc you could try install task-kde-desktop or install
> >>> kde-plasma-desktop, thats in testing.  In Sid, bits are still broken
> >>> like not being able to install Gimp and/or you can't do a dist-upgrade
> >>> but you can do an aptitude safe-upgrade and that is what I recommend for
> >>> both testing and unstable.
> >> 
> >> Yes you can. Well at least I could.
> >> 
> >> Calligra (including Krita) and Digikam are not there yet. Amarok,
> >> KMyMoney,
> >> kde-full all there and working.
> > 
> > Be prepared that you may have to do the dist-upgrade in several steps, and
> > possibly partly from a tty, cause I had to.
> 
> Martin you do know that 'aptitude safe-upgrade' adds and removes
> packages as needed, don't you?

These days I only use aptitude when apt-get does not give the result I am 
interested in.

> > If you are not comfortable with this, wait and install some lxde or other
> > desktop for the time being. If you can.
> 
> Been using Debian for more than 20 yrs. I've seen many systems break and
> I fix them all, yes, I'm comfortable, thanks to Debian and my study of
> package management.

Then go ahead and have fun :)

Thanks,
-- 
Martin

Re: Plasma desktop unusable in stretch

[Brad Rogers]

On Thu, 03 Sep 2015 10:12:52 +0200
Christian Hilberg  wrote:

Hello Christian,

>I guess it might have been wiser to let the transitions happen in
>unstable, since the massive breakage you mention was to be expected,
>and have the smaller issues and oversights ironed out in testing.
>This scheme worked out quite well in the past.

Testing acquires packages from unstable when certain criteria are met.
It's all automatic, except for when a freeze occurs.  That is to say,
nobody oversees it.  You appear to expect somebody (well, several
somebodies) to stem the tide to avoid problems.  Question is;  How do
they know what's going to cause problems?  Answer;  They don't/can't
until the problem(s) actually arise.  By then it's too late to avoid
them.

What you'd like to happen is never going to happen.  So it comes down to
three choices;

1) deal with it yourself
2) use stable
3) use another distro

With snapshot.debian.org 1 is easy to do, 2 may require an install and
3 _will_ require an install.

1 is probably the easiest.

-- 
 Regards  _
 / )   "The blindingly obvious is
/ _)radnever immediately apparent"
It's only the children of the --- wealthy tend to be good looking
Ugly - The Stranglers


pgpQmkyld7MtA.pgp
Description: OpenPGP digital signature

Re: Plasma desktop unusable in stretch

[Christian Hilberg]

Hi Brad,

Am Mittwoch 02 September 2015, 16:16:10 schrieb Brad Rogers:
> On Wed, 02 Sep 2015 10:21:47 -0400
> Gary Dale  wrote:
> 
> Hello Gary,
> 
> >Yesterday I rebooted my computer but when it came back up and I logged 
> >in, Plasma was no longer usable.
> 
> Come on Gary, you've been on this ML long enough to know that KDE is
> going through some *massive* changes ATM.  The path from KDE4 to
> KF5/Plasma is far from an easy one to tread.  Not least because of the
> change to GCC v5.  KF5/Plasma is very, /very/ different from KDE4.  It's
> not a huge surprise, to me at any rate, that some packages don't (yet)
> have their dependencies sorted out fully.
> 
> If one finds, when doing an update, it's necessary to remove large
> numbers of packages to get everything updated then one should pause and
> consider;  Do I really want to lose half of my software suite?  Usually
> the answer is "no".  In that case, see what can be updated without
> ripping the heart out of your system.
> 
> Testing sometimes has breakage.  Sometimes that breakage is big.  You
> just have to deal with it.  If you can't
> 
> there's always stable.

To me, that kind of breakage (due to the transitions KDE4->KF5 *and*
GCC4->GCC5 at the same time) is what we're used to see in unstable.
This is what unstable is for, imho.

By letting these transitions happen simultaneously in unstable as well
as testing, the ML became flooded with all-the-same-topic mails over
and over, because many people are using testing who do so because they
like to be more recent than stable while not daring enough to expedition
into unstable land.

I guess it might have been wiser to let the transitions happen in
unstable, since the massive breakage you mention was to be expected,
and have the smaller issues and oversights ironed out in testing.
This scheme worked out quite well in the past.

Kind regards,
Christian


signature.asc
Description: This is a digitally signed message part.

Re: Plasma desktop unusable in stretch

[anxiousmac]

On Thursday, 3 September 2015 09:20:02 UTC+1, Christian Hilberg  wrote:
> Hi Brad,
> 
> Am Mittwoch 02 September 2015, 16:16:10 schrieb Brad Rogers:
> > On Wed, 02 Sep 2015 10:21:47 -0400
> > Gary Dale  wrote:
> > 
> > Hello Gary,
> > 
> > >Yesterday I rebooted my computer but when it came back up and I logged 
> > >in, Plasma was no longer usable.
> > 
> > Come on Gary, you've been on this ML long enough to know that KDE is
> > going through some *massive* changes ATM.  The path from KDE4 to
> > KF5/Plasma is far from an easy one to tread.  Not least because of the
> > change to GCC v5.  KF5/Plasma is very, /very/ different from KDE4.  It's
> > not a huge surprise, to me at any rate, that some packages don't (yet)
> > have their dependencies sorted out fully.
> > 
> > If one finds, when doing an update, it's necessary to remove large
> > numbers of packages to get everything updated then one should pause and
> > consider;  Do I really want to lose half of my software suite?  Usually
> > the answer is "no".  In that case, see what can be updated without
> > ripping the heart out of your system.
> > 
> > Testing sometimes has breakage.  Sometimes that breakage is big.  You
> > just have to deal with it.  If you can't
> > 
> > there's always stable.
> 
> To me, that kind of breakage (due to the transitions KDE4->KF5 *and*
> GCC4->GCC5 at the same time) is what we're used to see in unstable.
> This is what unstable is for, imho.
> 
> By letting these transitions happen simultaneously in unstable as well
> as testing, the ML became flooded with all-the-same-topic mails over
> and over, because many people are using testing who do so because they
> like to be more recent than stable while not daring enough to expedition
> into unstable land.
> 
> I guess it might have been wiser to let the transitions happen in
> unstable, since the massive breakage you mention was to be expected,
> and have the smaller issues and oversights ironed out in testing.
> This scheme worked out quite well in the past.
> 
> Kind regards,
>   Christian

If we don't want breakage, we have to use stable. The primary purpose of 
testing is to develop the next release, not necessarily to produce a 
user-focused version of stable with newer packages. Last time I looked, 
warnings about this were liberally included in Debian documentation and wiki 
pages.

I have had my fair share of breakages using unstable, and trying to find my way 
out of them is usually quite educational. If I'm too busy at the time, I can 
always ssh my way to my data from another machine. Failing that, a live image.

anxiousmac

Subject=Re: Re: black icons after kde upgrade

[Nick Zarkadas]

I tried it but it didn't work.
Last week in the same machine I had installed fedora 22 (with desktop
effects on )
and I didn't had any problem with the desktop except the sddm screen  (it
was  black and white again.)

Re: Plasma desktop unusable in stretch

[Christian Hilberg]

Hi Brad,

Am Donnerstag 03 September 2015, 09:40:35 schrieb Brad Rogers:
> On Thu, 03 Sep 2015 10:12:52 +0200
> Christian Hilberg  wrote:
> 
> Hello Christian,
> 
> >I guess it might have been wiser to let the transitions happen in
> >unstable, since the massive breakage you mention was to be expected,
> >and have the smaller issues and oversights ironed out in testing.
> >This scheme worked out quite well in the past.
> 
> Testing acquires packages from unstable when certain criteria are met.
> It's all automatic, except for when a freeze occurs. That is to say,
> nobody oversees it.  

"It's all automatic" is the bit I missed. I was under the impression
that this would be true for experimental->unstable only and that the
packages in testing would then be marked as "ready for testing" manually,
once the breakage reports cease.

> You appear to expect somebody (well, several 
> somebodies) to stem the tide to avoid problems.

"Expecting" is not what I meant to express, it is more like "being
under the [wrong, I know by now] impression that somebody does",
given the actually relatively low frequency of breakages in testing.

> Question is;  How do they know what's going to cause problems?  Answer;  They 
> don't/can't
> until the problem(s) actually arise.  By then it's too late to avoid
> them.

Sure. Since there are the brave ones running unstable, I thought this
is where the biggest breakages were going to be caught and eliminated
before the packages entered testing.

> What you'd like to happen is never going to happen.  So it comes down to
> three choices;
> 
> 1) deal with it yourself
> 2) use stable
> 3) use another distro
> 
> With snapshot.debian.org 1 is easy to do, 2 may require an install and
> 3 _will_ require an install.
> 
> 1 is probably the easiest.

3) is not at all an option, sorry. ;-))

What I'm doing is using stable on my production machines and running
testing in a VM to follow up on what's going on and report issues as
I find them. It is not too much I can do there, but I try to add my
2 cent.

What had me puzzled a little was that I did not experience the KDE
packaged in testing being in the state it lately has been -- so that
is what may have misled my "expectations".

Kind regards,
Christian


signature.asc
Description: This is a digitally signed message part.

Bug#797886: muon-notifier: no update notifications from icon in KDE system tray

[Chrisitan Bachmaier]

Package: muon-notifier
Version: 4:5.3.2-3
Severity: normal

Dear Maintainer,

did a clean install of debian testing using kde. After apt-get update there is
no update notification in the system tray, although configured in kde system
settings notification dialog und updates are really available (installable via
apt-get upgrade).

apper, (deprecated and not available) update-notifier-kde, or similiar is not
installed. I installed apt-config-auto-update since it is recommended as
supplement of update-notifier-common.

$ dpkg -l | grep muon
ii  libmuon   4:5.3.2-3
amd64Runtime files for the Muon package management suite
ii  muon-common   4:5.3.2-3
all  Muon package manager suite (common data files)
ii  muon-discover 4:5.3.2-3
amd64Utility for browsing, installing, and removing applications
ii  muon-notifier 4:5.3.2-3
amd64update notifier for KDE
ii  muon-updater  4:5.3.2-3
amd64update manager for KDE

$ dpkg -l | grep aptdaemon
ii  aptdaemon 1.1.1-4
all  transaction based package management service
ii  aptdaemon-data1.1.1-4
all  data files for clients
ii  python3-aptdaemon 1.1.1-4
all  Python 3 modules for the server and client of aptdaemon
ii  python3-aptdaemon.gtk3widgets 1.1.1-4
all  Python 3 GTK+ 3 widgets to run an aptdaemon client

dpkg -l | grep update
ii  apt-config-auto-update2.0.0-1
all  Apt configuration for automatic cache updates
ii  libutempter0  1.1.6-1
amd64privileged helper for utmp/wtmp updates (runtime)
ii  muon-notifier 4:5.3.2-3
amd64update notifier for KDE
ii  muon-updater  4:5.3.2-3
amd64update manager for KDE
ii  update-inetd  4.43
all  inetd configuration file updater


Did I something wrong or missed I something?



Thanks,

Chris



-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.1.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages muon-notifier depends on:
ii  libc6 2.19-19
ii  libkf5configcore5 5.13.0-1
ii  libkf5i18n5   5.13.0-1
ii  libkf5kiowidgets5 5.12.0-1
ii  libkf5notifications5  5.12.0-1
ii  libqt5core5a  5.4.2+dfsg-5
ii  libqt5qml55.4.2-4
ii  libstdc++65.1.1-14
ii  muon-common   4:5.3.2-3
ii  muon-updater  4:5.3.2-3

muon-notifier recommends no packages.

muon-notifier suggests no packages.

-- no debconf information

Re: Plasma desktop unusable in stretch

[Andrey Rahmatullin]

On Thu, Sep 03, 2015 at 12:43:37PM +0200, Christian Hilberg wrote:
> "It's all automatic" is the bit I missed. I was under the impression
> that this would be true for experimental->unstable only
experimental->unstable is fully manual (even requiring a new upload).

-- 
WBR, wRAR


signature.asc
Description: Digital signature

Re: Plasma past G++ transition

[Thomas Fjellstrom]

On Thu 03 Sep 2015 11:29:07 PM Diederik de Haas wrote:
> On Thursday 03 September 2015 11:22:19 Thomas Fjellstrom wrote:
> > > Using Sid temporarily may help, as the G++ ABI transition seems to be
> > > completed there mostly. You can switch back to testing later.
> > 
> > I'm not sure that's entirely accurate?
> 
> The whole libstdc++6 transition is only at 29% atm, but almost all kde
> packages are amongst that 29%.

Hm, so i guess it'll be a few more weeks till it's all done? :(

I just have a lot of kde packages held back. Basically aptitude wants to 
remove most of kde still on my system. Aptitude upgrade can't even come up 
with a solution to do /anything/. It used to sit and try for a while with the 
progress counters, but now it just gives up right away.

-- 
Thomas Fjellstrom
tho...@fjellstrom.ca

qdbus commands in 64-bit jessie?

[D. R. Evans]

In wheezy, the following command worked correctly:



qdbus org.kde.yakuake /yakuake/sessions runCommandInTerminal $SESSION_ID "tmux"



Following my recent upgrade to jessie, the same command produces:



qdbus: could not exec '/usr/lib/i386-linux-gnu/qt4/bin/qdbus': No such file or
directory



The reference to i386 is a bit puzzling, since this is a 64-bit system.
Anyway, I discovered that all attempts to execute qdbus commands from the
command line produce the same error :-(

What do I need to do to get my qdbus commands working again?

  Doc

-- 
Web:  http://www.sff.net/people/N7DR





signature.asc
Description: OpenPGP digital signature

Re: Plasma desktop unusable in stretch

[Thomas Fjellstrom]

On Thu 03 Sep 2015 04:24:40 PM Gary Dale wrote:
> On 03/09/15 03:42 PM, Andrey Rahmatullin wrote:
> > On Thu, Sep 03, 2015 at 03:03:35PM -0400, Gary Dale wrote:
> >> Sorry, but before releasing a major package to "testing", shouldn't it be
> >> tested against the "testing" environment?
> > 
> > No, we don't do this.
> 
> Obviously, but the question was "shouldn't you?"

Yeah, I had thought the point of sid was to have a place to make sure things 
weren't completely broken, then things moved to testing to finish stabilizing.

-- 
Thomas Fjellstrom
tho...@fjellstrom.ca

Re: Plasma past G++ transition

[Thomas Fjellstrom]

On Fri 04 Sep 2015 02:09:39 AM Diederik de Haas wrote:
> On Thursday 03 September 2015 17:08:56 Thomas Fjellstrom wrote:
> > > The whole libstdc++6 transition is only at 29% atm, but almost all kde
> > > packages are amongst that 29%.
> > 
> > Hm, so i guess it'll be a few more weeks till it's all done? :(
> 
> Months is more likely ;-)

Lol. I more meant for a majority of the packages, especially the more commonly 
used ones, not every single package in main, contrib and non-free. :D 
Basically to where things aren't horribly broken when running aptitude/apt-
get.

> > I just have a lot of kde packages held back. Basically aptitude wants to
> > remove most of kde still on my system. Aptitude upgrade can't even come up
> > with a solution to do /anything/. It used to sit and try for a while with
> > the  progress counters, but now it just gives up right away.
> 
> Are you on sid or testing? From the aptitude output you posted earlier it
> looks like you're (partially) on sid.

Should be full sid. I don't even have stable or testing in my sources.

> If you are on sid, I suggest you try an 'aptitude full-upgrade -s' and let
> aptitude (optionally) run through many suggestions.

I've just tried that, but no luck after like 10. Still removing plasma and 
digikam.

> Another thing you could try is to try 'aptitude safe/full-upgrade 
> - s' and try whether you could upgrade things partially.
> But given the number of packages you seem to have installed you may have to
> wait (quite) a while before things get in enough shape for your system.

It seems like all the older virtual and meta packages are holding things back. 
I may go in and remove things like kde-full, and kde-workspace* (I think that 
was renamed plasma-workspace*?). But I really don't want to do without digikam 
which i read isn't updated yet.

Not sure what I'll do yet, i do virtually everything on this machine and I 
don't want to break anything essential (like kmail). I'll wait longer if I 
have to.

I setup a test install in virtual box that I'll try and upgrade to the latest 
kde and test out for a bit i think. See how it goes.

> I have fully upgraded (back) to sid yesterday and didn't loose too many
> packages, but I also don't have a lot of meta-packages which may have made
> things simpler in my case.

Fun story: a week or so ago, aptitude was regularly crashing trying to resolve 
conflicts. It would sit and spin for tens of minutes (possibly longer?) then 
crash. At least it isn't doing that anymore. heh.


-- 
Thomas Fjellstrom
tho...@fjellstrom.ca

Re: Plasma past G++ transition

[Thomas Fjellstrom]

On Fri 04 Sep 2015 03:43:44 AM Diederik de Haas wrote:
> On Thursday 03 September 2015 19:16:12 Thomas Fjellstrom wrote:
> > It seems like all the older virtual and meta packages are holding things
> > back.
> 
> That could very well be the case. There are a number of virtual/meta
> packages which have been 'retired' afaik
> 
> > I may go in and remove things like kde-full, and kde-workspace* (I
> > think that was renamed plasma-workspace*?).
> 
> I do think that kde-workspace has been 'retired'; it's not available on my
> system. Doing 'aptitude markauto kde-workspace' seems like a good idea.
> Wrt kde-full I read on IRC that work is underway to make that
> installable/upgradable, but since it includes the whole kitchen it naturally
> takes to most time to get ready.

Yeah, kde and its dependencies aren't exactly "small".

> > But I really don't want to do without digikam which i read isn't updated
> > yet.
> 
> Correct. Digikam is one of the applications which got removed on my upgrade
> (and some calligra packages I apparently had installed). Bluedevil was
> another one

I recall reading that bluedevil is now part of another package?

> > Not sure what I'll do yet, i do virtually everything on this machine and I
> > don't want to break anything essential (like kmail). I'll wait longer if I
> > have to.
> 
> Waiting a bit more is rarely a bad advice ;-)
> The transition tracker may help in deciding how long to wait:
> https://release.debian.org/transitions/

Heh. I just keep attempting dist/full-upgrade's and plain upgrades to see what 
goes through. Thanks for the link, I'll try and keep it open and check 
regularly.

I'd also like to avoid losing things like steam, and especially skype, and it 
seems the i386 stuff may be lagging behind.

-- 
Thomas Fjellstrom
tho...@fjellstrom.ca

Re: Plasma desktop unusable in stretch

[Brad Rogers]

On Thu, 03 Sep 2015 12:43:37 +0200
Christian Hilberg  wrote:

Hello Christian,

>> You appear to expect somebody (well, several 
>> somebodies) to stem the tide to avoid problems.  
>"Expecting" is not what I meant to express, it is more like "being

I wasn't sure, hence my writing "appear to..."  Having cleared up a
misunderstanding about the unstable->testing migration, I can tell
you're a lot less angry (I use the word cautiously; it may be too strong)
about what's going on ATM.

>Sure. Since there are the brave ones running unstable, I thought this
>is where the biggest breakages were going to be caught and eliminated
>before the packages entered testing.

By and large, the biggest breakages _do_ occur in unstable.  The current
situation is, in the time I've used testing (approx ten years),
unprecedented.  I've seen the odd package or two migrate that couldn't
be installed, but never on such a huge scale.

>> 1) deal with it yourself
>> 2) use stable
>> 3) use another distro
>3) is not at all an option, sorry. ;-))

No need to apologise, it's not necessary.  In all honesty, I didn't
expect it to be.

>What had me puzzled a little was that I did not experience the KDE
>packaged in testing being in the state it lately has been -- so that
>is what may have misled my "expectations".

Much of the problem, AIUI, is caused by the change to GCC5 for
Kf5/Plasma.  Just look at the number of packages held back from testing
because of it;

Updating gcc-5 makes 408 depending packages uninstallable on amd64: 

Note that that list refers to amd64 only.  It may differ on other
architectures.  And that's just the _depending_ packages.  There's
another 318 non-depending packages that are affected.

https://release.debian.org/migration/testing.pl?package=gcc-5 has the
full list.  It includes stuff like LibreOffice and all sort of Python
stuff, not just KDE.

It's going to take a long time to sort it out, I'm sure.

-- 
 Regards  _
 / )   "The blindingly obvious is
/ _)radnever immediately apparent"
An old custom to sell your daughter
Hong Kong Garden - Siouxsie & The Banshees


pgpbMsgaNmxYU.pgp
Description: OpenPGP digital signature

Re: Re: Plasma desktop unusable in stretch

[Hillel Lubman]

On Thu, 3 Sep 2015 21:21:52 +0500 Andrey Rahmatullin wrote: 
> That's the main misunderstanding.
> We had several tries to design and/or create a rolling Debian distro but
> there is nothing currently existing AFAIK.
> And it takes a lot more effort than is currently spent on unstable and
> testing (which is already a lot).

So what happened to these efforts to make always usable / always releasable 
testing? I remember such proposals, for example:
https://lwn.net/Articles/406301/
https://lwn.net/Articles/550032/

I always viewed testing as intended at desktop usage which ideally should suit 
causal non technical users too, but at the same time I know that such goals 
weren't yet reached and things can break seriously (so using snapshots to avoid 
major issues like recent Plasma 5 breakage is something every user of testing 
should learn). That's why I'm still hesitant to recommend testing for those who 
aren't ready to deal with such issues.

So are there still any plans to change that like above, or they were stalled 
because it requires too much resources to implement and maintain?

Regards,
Hillel Lubman.

Re: Plasma past G++ transition

[Diederik de Haas]

On Thursday 03 September 2015 19:16:12 Thomas Fjellstrom wrote:
> It seems like all the older virtual and meta packages are holding things
> back.  

That could very well be the case. There are a number of virtual/meta packages 
which have been 'retired' afaik

> I may go in and remove things like kde-full, and kde-workspace* (I
> think that was renamed plasma-workspace*?). 

I do think that kde-workspace has been 'retired'; it's not available on my 
system. Doing 'aptitude markauto kde-workspace' seems like a good idea.
Wrt kde-full I read on IRC that work is underway to make that 
installable/upgradable, but since it includes the whole kitchen it naturally 
takes to most time to get ready.

> But I really don't want to do without digikam which i read isn't updated
> yet.

Correct. Digikam is one of the applications which got removed on my upgrade 
(and some calligra packages I apparently had installed). Bluedevil was another 
one

> Not sure what I'll do yet, i do virtually everything on this machine and I 
> don't want to break anything essential (like kmail). I'll wait longer if I 
> have to.

Waiting a bit more is rarely a bad advice ;-)
The transition tracker may help in deciding how long to wait: 
https://release.debian.org/transitions/

signature.asc
Description: This is a digitally signed message part.