[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]
Re: epel 4 and python-twisted-* packages
- From: Paul Howarth <paul city-fan org>
- To: epel-devel-list redhat com
- Subject: Re: epel 4 and python-twisted-* packages
- Date: Sun, 5 Jun 2011 12:39:46 +0100
On Sun, 05 Jun 2011 12:57:26 +0200
Stefan Schulze Frielinghaus <stefan seekline net> wrote:
> On So, 2011-06-05 at 11:28 +0100, Paul Howarth wrote:
> > On Sun, 05 Jun 2011 11:25:59 +0200
> > Stefan Schulze Frielinghaus <stefan seekline net> wrote:
> >
> > > Hi all,
> > >
> > > what happened to the python twisted framework in EPEL 4? For
> > > quite a while I receive broken dependency mails for the package
> > > pyicq-t but only for the EL4 branch, where I'm even not a
> > > maintainer of. Since I'm not using EL4 I'm not really up to date,
> > > but if I remember right the framework was available at least a
> > > year ago. Was it silently removed? If so, what should happen to
> > > packages which depend on it?
> >
> > There isn't even a git branch for python-twisted-core for el4 so
> > I'd be surprised if it ever existed there.
>
> Your right but then I don't know why I received broken dependency
> mails for the last couple of weeks/months but not, lets say, a year
> ago. The package pyicq-t for EL4 has not changed since 2009 but I
> receive the broken dependency mails only since a couple of
> weeks/months and not since 2009.
That's probably because broken dependency mails were only generated
intermittently up until the last few months.
> This is something which confuses me:
> If python-twisted-* never existed for EL4, then pyicq-t should have
> never made it into EL4 because of the dependency.
True, but there's no process enforcing this other than the maintainers
checking that their packages are installable; I don't think there's an
AutoQA process for EPEL as yet.
Paul.
[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]