-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 12/22/2015 03:37 PM, Joachim Breitner wrote: > but why don’t you then build it regularly on amd64 to do the full > source upload, and then do a -b build on sparc64, and then upload > both changes?
Well, that's what I did. But you actually have to do is messing with the changes file as you need to replace the amd64 binary packages with the sparc64 binary packages in the changes file. > Or do a source-only upload of the sources, a -b build on sparc64, > and let the arch all autobuilder take care of the rest? Not really. This option is not very usable for unofficial modifications and such. For example, sometimes I need to hack something for unreleased just to get the package working initially, like a version of ghc which does not B-D on ghc. It isn't as simple as you would think. Otherwise I wouldn't ask to make it simpler :). Adrian - -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - [email protected] `. `' Freie Universitaet Berlin - [email protected] `- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJWeWEaAAoJEHQmOzf1tfkT0ZEP/0/ZG+ejGlB6CYFYTQ6sCWYt IYUMNsmpSpGpW9FLWatvrBx3re037O82xLn+y2u9mxRCS2Tk6vgYNLtTn+3icHzZ 0Zo57SyGCt2gfevtgAoXOeqnBFCQHWLJV5QOZha4xPcseT24lby/3SSPqJM1p5uA jQTdhEBL0Ox8feYLKZFWbPgftNgWRqBrsj9JvoTufi3hy6CNzPDKw/UVw9YEfeTn rCpHJL6zXjOxJJ6B7EDKhmN6hOV5PFXhvpB1P6BsEyVcLmabWe3WPwA3eYQVqu7T OCeF7PNX2h3tl8KXwVPEy5S5GX0e7TdEG7cBwKKrRIjQqmQHievBbing5XG3Sj7s jnY9ASNtiKePubX6lNCA5c20NVlosfYTxtvVO1cv/wYJE4u8ljXRW+IwYVs2WjVy qL0gAI9HObTaeCLSaRr3bqaZlP2xZVf39p43IIa+W2zLdSMSVenGkq3vgiQfVFse 05u8kdnHWCgeOPknyli04kaEOyjhOMMRAxPLDEiBDxQL5G+oXkMI6WMcJRecU8Xj HxaRTdLqCUo50FdtZGHc1nzW/yekpjJ0XHhCCsUEQsvNfqiO73kjJi3Q2ehOo0u0 6TRQyF+kKSq7mKmq54V2l9Z0xQM+6bStJlOxcjoOx8zKQyQZ0zX9D6YlDBqnPqG8 zWXeW4NGvJHn21FQof58 =4pry -----END PGP SIGNATURE-----
