[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]
Re: libmtp soname change breakage (was: Re: Summary - Broken dependencies in Fedora Extras - 2007-02-07)
- From: Ralf Corsepius <rc040203 freenet de>
- To: Discussion related to Fedora Extras <fedora-extras-list redhat com>
- Cc:
- Subject: Re: libmtp soname change breakage (was: Re: Summary - Broken dependencies in Fedora Extras - 2007-02-07)
- Date: Thu, 08 Feb 2007 09:33:22 +0100
On Thu, 2007-02-08 at 09:23 +0100, Linus Walleij wrote:
> On Wed, 7 Feb 2007, Ville Skyttä wrote:
> > Apologies if I missed the announcement, but based on the above list of
> > breakage I'm not alone even within Fedora maintainers, let alone elsewhere.
>
> The packages were intended to be pushed out alongside each other, I built
> libmtp and I instructed gauret (Amarok maintainer) to rebuild and built
> gnomad2 immediately afterwards, however the build of libmtp was pushed
> before our builds were done.
>
> The actual question here is how do we coordinate package builds with
> pushing of builds in a good way?
Communication - Direct email, bugzilla.
If necessary introduce compat-packages.
> What we want to do is group three
> packages (libmtp, gnomad2, amarok) and not push any one of them until all
> three are built. This would totally solve this kind of nasty problems.
co-maintain them, give other maintainers privileges to rebuild the
packages when all agree upon such step?
Having a build-system which requires maintainers to "give explicit
clearance before a package is being pushed to the public"?
Ralf
[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]