problems with upgrade of kde
jjesse at gmail.com
Wed May 20 21:06:10 BST 2009
On Wed, May 20, 2009 at 12:57 PM, Harald Sitter <apachelogger at ubuntu.com>wrote:
> On Mittwoch, 20. Mai 2009 05:28:15 Richard JOHNSON wrote:
> > On Tue, May 19, 2009 at 11:01:22PM -0400, Clay Weber wrote:
> > > On Tuesday 19 May 2009 10:10:00 pm Jonathan Jesse wrote:
> > > > Please test the packages further before announcing the changes on the
> > > > website. I wonder how many other people are in the same boat as I
> > >
> > > Yes
> > >
> > > > i want the newest goodness of KDE and yes I want a working machine.
> > > > that too hard to ask for?
> > > >
> > > > Jonathan
> > >
> > > I don't mean to sound rude, but the repository is called 'kubuntu
> > > experimental' for a reason, and this is a beta of 4.3 as well. I am
> > > assuming once we get to 4.3 final, the packages will be in the 'kubuntu
> > > updates' ppa repo.
> > Right, and Jonathan understands this part, and I am sure it is the reason
> > why Network Manager is giving him issues, though the part about the
> > packages being broken has nothing to do with the PPA being experimental,
> > nor KDE 4.3 being a beta. We were just discussing this on IRC this
> > We, including me as I have been guilty in the past, need to make sure we
> > are doing some regression testing and that the packages work before
> > announcing them to the public. There were a lot of people on IRC
> > complaining about them today, and to me for some strange reason (30 or
> > people messaged me today alone).
> > Is everyone using the Pbuilder hooks that tests that once a package is
> > completed the build it installs/upgrades cleanly? I think using this and
> > doing some minor regression testing, you know making sure the packages
> > install cleanly and that the apps at least start, is a good thing to do.
> > This also prevents us from having about 5 unnecessary uploads for 4.3 in
> > Karmic, I think we are up to 0ubuntu5 now. We need to be a bit more
> > and not worry about Soyuz karma.
> Neversfelde was kind enough to provide us server capacity. Soon (i.e. as
> as I am able to master up the code for that) we will direct all Ninja
> Packaging through said server which should speed up the review process
> the whole coordinator dude position gets eliminated so that any core-dev
> review the changes and upload at will) as well as help us do automated QA.
> Because really, the fact that I spent at least one day for every release on
> basic regression testing (e.g. file clashes) is simply ridiculous.
> So in the future, file clashes should be detected by comparing the
> file lists. However, I'd like to note that with more resources we could do
> lot more (I am thinking real upgrade scenarios in chroots for example ;-)).
> kubuntu-devel mailing list
> kubuntu-devel at lists.ubuntu.com
> Modify settings or unsubscribe at:
Thanks for adressing how things are getting better and how better testing
will be following. Still getting notifications there are updates but still
having problems with packages being installed. Should I be starting over
somehow or still forcing these to install?
Errors were encountered while processing:
E: Sub-process /usr/bin/dpkg returned an error code (1)
Latest problems on installing things
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the kubuntu-devel