On Sat, 18 Feb 2012 11:11:38 +0100, RC (Ralf) wrote:
> On 02/15/2012 06:00 PM, Michael Schwendt wrote:
> > On Wed, 15 Feb 2012 13:10:00 +0100, RC (Ralf) wrote:
> >
> >> [...] Playing down the issues and to wipe them under the carpet
> >> doesn't help anybody.
> >
> > Who's "playing down the issues
On 02/15/2012 06:00 PM, Michael Schwendt wrote:
On Wed, 15 Feb 2012 13:10:00 +0100, RC (Ralf) wrote:
[...] Playing down the issues and to wipe them under the carpet
doesn't help anybody.
Who's "playing down the issues"? Don't make up such things
Well, as I read your response, you have been a
On Thu, 16 Feb 2012 01:38:37 +
Marko Vojinovic wrote:
> On Wednesday 15 February 2012 18:16:40 Kevin Fenzi wrote:
> > On Wed, 15 Feb 2012 19:45:11 -0500
> >
> > Tom Horsley wrote:
> > > Huh? None of that junk is in updates today, that's why people
> > > find it broken all the time. The test
On Thu, 16 Feb 2012 12:05:29 +, MV (Marko) wrote:
> On Thursday 16 February 2012 12:17:14 Michael Schwendt wrote:
> > On Thu, 16 Feb 2012 01:22:05 +, MV (Marko) wrote:
> > > Even better, the virtual machine can do a "yum update --skip-broken",
> > > and then pick up yum's report on what wa
On Thursday 16 February 2012 12:17:14 Michael Schwendt wrote:
> On Thu, 16 Feb 2012 01:22:05 +, MV (Marko) wrote:
> > Even better, the virtual machine can do a "yum update --skip-broken",
> > and then pick up yum's report on what was updated and what was skipped.
>
> --skip-broken is not safe
On Wed, 15 Feb 2012 20:38:35 -0500, TH (Tom) wrote:
> I'm talking a simple practical system to catch
> most errors, not the ultimate perfect system
> which will never actually be finished :-).
It doesn't need to be perfect, but delaying security updates because
something else breaks deps isn't a
On Wed, 15 Feb 2012 19:45:11 -0500, TH (Tom) wrote:
> On Wed, 15 Feb 2012 23:40:22 +0100
> Michael Schwendt wrote:
>
> > Of course, a temporary staging repo would be needed. Filling it isn't
> > trivial, however, and requires lots of iterations and a bullet-proof
> > "--skip-broken" finder
>
> H
On Thu, 16 Feb 2012 01:22:05 +, MV (Marko) wrote:
> Even better, the virtual machine can do a "yum update --skip-broken", and
> then
> pick up yum's report on what was updated and what was skipped.
--skip-broken is not safe yet, is it? At least on x86_64, broken deps
have caused the depsolv
On Wednesday 15 February 2012 18:16:40 Kevin Fenzi wrote:
> On Wed, 15 Feb 2012 19:45:11 -0500
>
> Tom Horsley wrote:
> > Huh? None of that junk is in updates today, that's why people
> > find it broken all the time. The test system using the staging
> > repo can either run "yum update" with no e
On Wed, 15 Feb 2012 18:28:42 -0700
Kevin Fenzi wrote:
> The DVD is a small subset of all available packages. ;)
I know that, but the reason (presumably) packages are
included on the DVD is because they are felt to be
frequently used as opposed to the ones only on the
network repos.
I'm talking
On Wed, 15 Feb 2012 20:23:35 -0500
Tom Horsley wrote:
> On Wed, 15 Feb 2012 18:16:40 -0700
> Kevin Fenzi wrote:
>
> > Whats on the test system? Everything? It can't have all packages
> > installed due to some conflicting (deliberately, or due to bugs).
>
> Install from the DVD, select custom p
On Wed, 15 Feb 2012 18:16:40 -0700
Kevin Fenzi wrote:
> Whats on the test system? Everything? It can't have all packages
> installed due to some conflicting (deliberately, or due to bugs).
Install from the DVD, select custom packages, right click
every package group and say "select all optional
On Wednesday 15 February 2012 19:45:11 Tom Horsley wrote:
> Yes, that means nothing goes in updates if even one thing
> is broken in the staging repo. But that is NOT a problem.
> Virtually everyone trying to run "yum update" with the current
> process is getting errors and giving up till things wo
On Wed, 15 Feb 2012 19:45:11 -0500
Tom Horsley wrote:
> Huh? None of that junk is in updates today, that's why people
> find it broken all the time. The test system using the staging
> repo can either run "yum update" with no errors, or it can't.
> If it gets no errors, the staging repo becomes t
On Wed, 2012-02-15 at 19:45 -0500, Tom Horsley wrote:
> Virtually everyone trying to run "yum update" with the current
> process is getting errors and giving up till things work
> anyway.
No doubt some people are getting this, but virtually everyone? I don't
usually have any problems of this sort
On Wed, 15 Feb 2012 23:40:22 +0100
Michael Schwendt wrote:
> Of course, a temporary staging repo would be needed. Filling it isn't
> trivial, however, and requires lots of iterations and a bullet-proof
> "--skip-broken" finder
Huh? None of that junk is in updates today, that's why people
find it
On Wed, 15 Feb 2012 13:02:22 -0500, TH (Tom) wrote:
> > Secondly, you can only catch the broken dep prior to moving _individual
> > packages_ from updates-testing to updates. Moving alsa-lib plus alsa-utils
> > at once would have been fine.
>
> So don't move them to updates, move them to pushed-b
On Wed, 15 Feb 2012 18:00:30 +0100
Michael Schwendt wrote:
> Secondly, you can only catch the broken dep prior to moving _individual
> packages_ from updates-testing to updates. Moving alsa-lib plus alsa-utils
> at once would have been fine.
So don't move them to updates, move them to pushed-but-
On Wed, 15 Feb 2012 13:10:00 +0100, RC (Ralf) wrote:
> [...] Playing down the issues and to wipe them under the carpet
> doesn't help anybody.
Who's "playing down the issues"? Don't make up such things.
These issues are a topic not just on this mailing-list, but in (all?)
Fedora related communit
On Wed, 15 Feb 2012 06:23:53 -0500, TH (Tom) wrote:
> On Wed, 15 Feb 2012 12:12:43 +0100
> Michael Schwendt wrote:
>
> > It's really a scenario where the Fedora Updates System needs to prevent a
> > packager from pushing something. That has not been implemented yet,
> > however. And more will nee
On 15-02-12 13:10, Ralf Corsepius wrote:
I am not blaming the alsa-utils/libs packager(s), I am blaming those
people who are supposed to assure the distros' releases and updates are
consistent.
Isn't that the packagers/maintainers responsibility? They create and
push the updates that have an
On 02/15/2012 12:12 PM, Michael Schwendt wrote:
On Wed, 15 Feb 2012 10:29:19 +0100, RC (Ralf) wrote:
Wasn't this kind of bugs supposed to be caught by AutoQA?
It caught it,
https://admin.fedoraproject.org/updates/FEDORA-2012-1132/alsa-utils-1.0.25-7.fc16
but obviously only after the aut
On Wed, 15 Feb 2012 12:12:43 +0100
Michael Schwendt wrote:
> It's really a scenario where the Fedora Updates System needs to prevent a
> packager from pushing something. That has not been implemented yet,
> however. And more will need to be implemented to get it right.
Yes, but it is the insane q
On Wed, 15 Feb 2012 10:29:19 +0100, RC (Ralf) wrote:
> >> Wasn't this kind of bugs supposed to be caught by AutoQA?
> > It caught it,
> >
> >
> > https://admin.fedoraproject.org/updates/FEDORA-2012-1132/alsa-utils-1.0.25-7.fc16
> >
> > but obviously only after the automatic request to push it
On 02/15/2012 09:46 AM, Michael Schwendt wrote:
On Wed, 15 Feb 2012 04:53:54 +0100, RC (Ralf) wrote:
On 02/14/2012 10:28 PM, Michael Schwendt wrote:
On Tue, 14 Feb 2012 22:21:05 +0100, HD (Heinz) wrote:
Hi,
seems like alsa-lib update is broken, does anybody see the same with F16?
*sigh*
h
On Wed, 15 Feb 2012 04:53:54 +0100, RC (Ralf) wrote:
> On 02/14/2012 10:28 PM, Michael Schwendt wrote:
> > On Tue, 14 Feb 2012 22:21:05 +0100, HD (Heinz) wrote:
> >
> >> Hi,
> >>
> >> seems like alsa-lib update is broken, does anybody see the same with F16?
> >
> > *sigh*
> >
> > https://admin.fed
On 2/14/2012 7:53 PM, Ralf Corsepius wrote:
On 02/14/2012 10:28 PM, Michael Schwendt wrote:
On Tue, 14 Feb 2012 22:21:05 +0100, HD (Heinz) wrote:
Hi,
seems like alsa-lib update is broken, does anybody see the same with
F16?
*sigh*
https://admin.fedoraproject.org/updates/FEDORA-2012-1025/a
On 02/14/2012 10:28 PM, Michael Schwendt wrote:
On Tue, 14 Feb 2012 22:21:05 +0100, HD (Heinz) wrote:
Hi,
seems like alsa-lib update is broken, does anybody see the same with F16?
*sigh*
https://admin.fedoraproject.org/updates/FEDORA-2012-1025/alsa-lib-1.0.25-1.fc16
Guess there isn't any
If you use update-testing repo you can update alsa stuff
Inviato da Samsung Mobile
Original message
Subject: Re: Alsa-utils update broken
From: Digimer
To: Community support for Fedora users
CC:
On 02/14/2012 04:21 PM, Heinz Diehl wrote:
> Hi,
>
> seems like
On Tue, 14 Feb 2012 22:21:05 +0100, HD (Heinz) wrote:
> Hi,
>
> seems like alsa-lib update is broken, does anybody see the same with F16?
*sigh*
https://admin.fedoraproject.org/updates/FEDORA-2012-1025/alsa-lib-1.0.25-1.fc16
> Guess there isn't any alsa-lib package >= 1.0.25 in F16 updates.
T
On 02/14/2012 04:21 PM, Heinz Diehl wrote:
> Hi,
>
> seems like alsa-lib update is broken, does anybody see the same with F16?
> Guess there isn't any alsa-lib package >= 1.0.25 in F16 updates.
>
> [root@wildsau ~]# yum update
> Loaded plugins: langpacks, presto, refresh-packagekit
> Setting up U
31 matches
Mail list logo
