<br><br><div class="gmail_quote">On Wed, May 20, 2009 at 12:57 PM, Harald Sitter <span dir="ltr"><<a href="mailto:apachelogger@ubuntu.com">apachelogger@ubuntu.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> <div><div></div><div class="h5">On Mittwoch, 20. Mai 2009 05:28:15 Richard JOHNSON wrote:<br> > On Tue, May 19, 2009 at 11:01:22PM -0400, Clay Weber wrote:<br> > > On Tuesday 19 May 2009 10:10:00 pm Jonathan Jesse wrote:<br> > > > Please test the packages further before announcing the changes on the<br> > > > website. I wonder how many other people are in the same boat as I am?<br> > ><br> > > Yes<br> > ><br> > > > i want the newest goodness of KDE and yes I want a working machine. Is<br> > > > that too hard to ask for?<br> > > ><br> > > > Jonathan<br> > ><br> > > I don't mean to sound rude, but the repository is called 'kubuntu<br> > > experimental' for a reason, and this is a beta of 4.3 as well. I am<br> > > assuming once we get to 4.3 final, the packages will be in the 'kubuntu<br> > > updates' ppa repo.<br> ><br> > Right, and Jonathan understands this part, and I am sure it is the reason<br> > why Network Manager is giving him issues, though the part about the<br> > packages being broken has nothing to do with the PPA being experimental,<br> > nor KDE 4.3 being a beta. We were just discussing this on IRC this evening.<br> > We, including me as I have been guilty in the past, need to make sure we<br> > are doing some regression testing and that the packages work before<br> > announcing them to the public. There were a lot of people on IRC<br> > complaining about them today, and to me for some strange reason (30 or more<br> > people messaged me today alone).<br> ><br> > Is everyone using the Pbuilder hooks that tests that once a package is<br> > completed the build it installs/upgrades cleanly? I think using this and<br> > doing some minor regression testing, you know making sure the packages<br> > install cleanly and that the apps at least start, is a good thing to do.<br> > This also prevents us from having about 5 unnecessary uploads for 4.3 in<br> > Karmic, I think we are up to 0ubuntu5 now. We need to be a bit more patient<br> > and not worry about Soyuz karma.<br> <br> </div></div>Neversfelde was kind enough to provide us server capacity. Soon (i.e. as soon<br> as I am able to master up the code for that) we will direct all Ninja Release<br> Packaging through said server which should speed up the review process (since<br> the whole coordinator dude position gets eliminated so that any core-dev can<br> review the changes and upload at will) as well as help us do automated QA.<br> Because really, the fact that I spent at least one day for every release on<br> basic regression testing (e.g. file clashes) is simply ridiculous.<br> <br> So in the future, file clashes should be detected by comparing the packages'<br> file lists. However, I'd like to note that with more resources we could do a<br> lot more (I am thinking real upgrade scenarios in chroots for example ;-)).<br> <div><div></div><div class="h5"><br> <br> --<br> kubuntu-devel mailing list<br> <a href="mailto:kubuntu-devel@lists.ubuntu.com">kubuntu-devel@lists.ubuntu.com</a><br> Modify settings or unsubscribe at: <a href="https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel" target="_blank">https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel</a><br> </div></div></blockquote></div><br>Harald,<br><br>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?<br> <br>Errors were encountered while processing:<br> /var/cache/apt/archives/kdewallpapers_4%3a4.2.85-0ubuntu1~jaunty1~ppa1_all.deb<br>E: Sub-process /usr/bin/dpkg returned an error code (1)<br><br>Latest problems on installing things<br>