2007/12/28, Christoph Wickert <christoph.wickert@xxxxxxxxxxxxxx>:
I fallen on an broken deps on kernel-xen-devel during the update of my F-8 release, why don't talk about too ?
Its not the first time we have this kind of trouble.
I Agree this should not happen but, ask first why there is a broken deps on some packages and why this happen.
It's not difficult, it's not my first update of gammu collection/dependence package, and it's not the first time a upadte depended release.
I think we should set up and automate or web_api to request repo tag for package we wanted to build against fresh released one
to build other into koji/mock from repo
For that, we could make a bodhi policy. Cause no rules say all package Must go to testing-update before move to stable one.
Why does only security update should go to stable ?
I'm not here to blame anyone too but this thread should up many time ago.
on differente pacakge that broken yum udpate in the past, not only this one.
Raleigh, we have a problem...
python-gammu, which is required by wammu, prevents users from updating
to the latest gammu release for several days now. It has already been
reported in Bugzilla, see
https://bugzilla.redhat.com/show_bug.cgi?id=426848 and - even more
interesting -
https://bugzilla.redhat.com/show_bug.cgi?id=425831
I fallen on an broken deps on kernel-xen-devel during the update of my F-8 release, why don't talk about too ?
Its not the first time we have this kind of trouble.
I Agree this should not happen but, ask first why there is a broken deps on some packages and why this happen.
This leads me to some questions:
1. Why is # 425831 still in status "New"? It has been reported on
Dec 16th and the maintainer already responded to it.
2. What's so difficult to coordinate 2 (3 with wammu) dependent
packages? All are owned by the same packager. IMO this should be
done in one single update in bodhi.
It's not difficult, it's not my first update of gammu collection/dependence package, and it's not the first time a upadte depended release.
3. Do we need better training for our maintainers or more
documentation in the wiki? The broken deps already appeared in
EPEL before they were in F8, so the maintainer should have known
that he's breaking something when he did the gammu update in
Fedora.
I think we should set up and automate or web_api to request repo tag for package we wanted to build against fresh released one
to build other into koji/mock from repo
4. When was the testing done? gammu-1.17.0-1.fc8 was built on Dec.
22 11:22:28 MST [1] and hit the updates repo on Dec. 23 22:50:08
[2]. This is less than 36 hours for testing.
For that, we could make a bodhi policy. Cause no rules say all package Must go to testing-update before move to stable one.
5. Why has gammu been pushed directly to updates and not to
updates-testing? According to the changelog it was not a
security update.
Why does only security update should go to stable ?
Note that I don't want to blame a single person here. I think this is
just an example that we really NEED to think about how to avoid such
situations in the future? I know there are people on vacation these
days, but there are enough people that offered help. Unfortunately they
are not allowed to by the ACLs.
I'm not here to blame anyone too but this thread should up many time ago.
on differente pacakge that broken yum udpate in the past, not only this one.
Any thoughts?
Christoph
[1] http://koji.fedoraproject.org/koji/buildinfo?buildID=28966
[2] https://admin.fedoraproject.org/updates/F8/FEDORA-2007-4743
--
Xavier.t Lamien
--
French Fedora Ambassador
Fedora/EPEL Contributor | http://fedoraproject.org/wiki/XavierLamien
GPG-Key ID: F3903DEB
Fingerprint: 0F2A 7A17 0F1B 82EE FCBF 1F51 76B7 A28D F390 3DEB
-- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
