Backport bacula-client from jaunty to dapper

Bug #344850 reported by Ryan Parrish
4
Affects Status Importance Assigned to Milestone
Dapper Backports
Won't Fix
Undecided
Unassigned

Bug Description

I know jaunty is not released yet, so this request is a bit early.

I would like to see current versions of the bacula-client meta package backported to 6.06. By doing this myself and others can keep our stable and well running 6.06 servers as they are, and then have a single more recent version of Ubuntu act as the director and storage daemon. This way we can continue to take advantage of new features in bacula (migration jobs, BAT) and leave the bulk of our servers untouched.

I have been able to get the client packages to compile under prevu by hacking down the control and rules file so that it only builds the client packages, however I am no professional at writing makefiles and I am sure to have made some mistakes so I don't consider these to be widely distributable (however the built packages seem to work fine in my production environment).

Revision history for this message
Ryan Parrish (ryanparrish) wrote :
Revision history for this message
Ryan Parrish (ryanparrish) wrote :
Revision history for this message
Ryan Parrish (ryanparrish) wrote :

Whoops, uploaded the wrong rules file. Sorry.

Revision history for this message
Evan Broder (broder) wrote :

Closing the dapper-backports task due to Ubuntu 6.06 (Dapper Drake) no longer being supported.

This bug is being closed by a bot. If you feel the change was made in error, please feel free to re-open the bug. However, backports requests for Ubuntu 6.06 (Dapper Drake) are no longer being accepted.

Changed in dapper-backports:
status: New → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.