* Dan Langille [2014-05-09 19:32:52 -0400]: > > Who did the Debian packages in previous versions.
The Debian Bacula Team; see http://packages.qa.debian.org/b/bacula.html for information. > That said, many projects have a build tool, such a poudriere, which allows > for easy creation of packages. Doesn’t Debian? "Easy" doesn't mean correct. Bacula major version upgrades typically involve changes to the database schema, which Debian users expect the packaging to automate for them. I'd rather see this done correctly than quickly. If I were in a hurry to upgrade my installation of Bacula (on Debian stable) to the latest version, I'd probably start from the existing package, transfer the debian/ subdirectory to the new release, then work out what needs to be changed to make it (a) build, (b) pass regression tests. This is almost certainly a more productive approach than repackaging from scratch. At the moment, however, I've got more urgent things to do. ------------------------------------------------------------------------------ Is your legacy SCM system holding you back? Join Perforce May 7 to find out: • 3 signs your SCM is hindering your productivity • Requirements for releasing software faster • Expert tips and advice for migrating your SCM now http://p.sf.net/sfu/perforce _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
