Just curious about how we build new releases of tb now:Stevo wrote: ↑Wed Jun 06, 2018 1:26 pm OK, I'll ask Tim to move the Birb over to main, pull our mozilla-binaries, and announce it in in the package threads. For future maintainers, I think these steps will work for rebuilds of new releases from Debian:
Bump the epoch to 2: for our rebuild.
Copy the control file over from the last MX rebuild. Check the changelog to see if any new langpacks were added and add those to the control file. You don't need dummy transitional packages for new ones.
Optional: the -dbg files end up at hundreds of MB and are very seldom used. They can be disabled in the rules file by editing the override:toCode: Select all
override_dh_strip: if [ "$(RELEASE)" != "UNRELEASED" ]; then \
Tbird automatically builds using all available cores/threads. I just noticed that the Liquorix kernel does this as well.Code: Select all
override_dh_strip: if [ "$(RELEASE)" = "UNRELEASED" ]; then \
1-Do we still use the get-orig-source and if so do we need a new method for lightning?
2-Since it sounds like we're really building them now as opposed to just repackaging the binaries, they'll need to be built on their real arch's instead of using the -B ai386/-aamd64 trick, right?
3-what comes after the backslash in your debug removal script?
Code: Select all
override_dh_strip:
if [ "$(RELEASE)" != "UNRELEASED" ]; then \
4-anything (ie;icedove) else?
- mike