[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: redmine depends on ruby-awesome-nested-set, which is not available

Hi Ondřej,

On Sun, Jul 20, 2014 at 11:13:07AM +0200, Ondřej Surý wrote:
> Hi Florian,
> On Fri, Jul 18, 2014, at 16:10, Florian Schlichting wrote:
> > Hi Ondrej,
> > 
> > redmine 2.5.1-2~bpo70+1 in wheezy-backports depends on
> > ruby-awesome-nested-set, which is unavailable in both wheezy and
> > wheezy-backports.
> sorry for the breakage due bad timing on my end.

Not only that; I think we are doing a lousy job in coordinating redmine
backports. See below.

> > Also, said redmine package depends on ruby-rack (>= 1.4.5~) while only
> > 1.4.1-2.1 is available in wheezy, and it also depends on
> > ruby-railties-3.2 (>= 3.2.16-1~) while the version in wheezy is 3.2.6-3.
> > 
> > Could you please fix this situation, preferably by uploading the
> > required packages to wheezy-backports, or if that's not possible as they
> > have just been removed from testing on your request along with all the
> > other ruby stuff and the backports ftp masters won't give a special
> > exception, remove the broken redmine package from wheezy-backports?
> We are in sort of deadlock here, since we don't want to have rails-3.2
> in testing (e.g. the RC bug there is just to prevent migration).
> Could we be granted an exception to upload fixed rails, ruby-rack and
> ruby-awesome-nested-set that fix security bugs in rails?

There is already a rails 3.2 stack in wheezy, and we don't need a
backported one.  We also don't a different ruby-rack than the one
already in wheezy.

When I backported redmine 2.4 to wheezy, I did all the adjustements to
the dependencies to make sure it would work with everything that is
already in wheezy. It's all in the git repository:


However, it seems that you uploaded redmine 2.5 to backports ignoring
all of packaging work and testing I have done with 2.4 to be able to use
the packages already available in wheezy; the changelog even lost the
entry for 2.4.2-1~bpo70+1.

Also, you did not push your changes to the git repository.

AFAICT the only missing piece is ruby-awesome-nested-set, which is a new
dependency introduced in the redmine 2.5 series which does not exist in
wheezy; this one does need to be backported, but that should be all.

> And if not, please remove redmine and rails from backports.

Let's get our shit together instead.

I use redmine from backports for work and I won't let it be removed.
Here is what I intend to do:

- import your redmine 2.5 backport into git, branch master-wheezy-backports
- reapply the packaging changes to make it work with rails and rack from
- make ruby-awesome-nested-set reach testing, and backport it.
- uploaded a fixed redmine to wheezy-backports

So the question to backports FTP masters is: even though redmine is not
present in testing right now because rails 3.2 won't be shipped in
jessie, would you be willing to allow uploading a redmine
2.5.1-2~bpo70+2 that fixes dependencies so that it uses rails and rack
packages from wheezy?

Antonio Terceiro <terceiro@debian.org>

Attachment: signature.asc
Description: Digital signature

Reply to: