On 12 April 2016 at 21:39, Michael Hudson-Doyle
wrote:
> We could do it without 1) and the consequent re-uploading of every go
> library by using dpkg-query --search a lot, which would be slow I
> guess, but maybe could be done as a fallback?
I still asking dpkg about file/directory package owner
* Michael Hudson-Doyle:
> There is another approach to the static linking issue, which is to
> start using dynamic linking instead. It's implemented upstream for
> most architectures now (only mips64 le/be and ppc64 be missing I
> think). I'm going to be working on starting to use dynamic linking
Bit of a late reply, been busy.
On 5 April 2016 at 19:27, Florian Weimer wrote:
> Hi,
>
> we need to discuss how we can support applications written in Go for
> stretch.
>
> The most radical approach would be not to ship any Go applications in
> stretch, only the basic Go language implementations
binary:golang-github-masterzen-xmlpath-dev is NEW.
source:golang-github-masterzen-xmlpath is NEW.
Your package has been put into the NEW queue, which requires manual action
from the ftpteam to process. The upload was otherwise valid (it had a good
OpenPGP signature and file hashes are valid), so p
golang-github-masterzen-xmlpath_0.0~git20140218.13f4951-1_amd64.changes
uploaded successfully to localhost
along with the files:
golang-github-masterzen-xmlpath_0.0~git20140218.13f4951-1.dsc
golang-github-masterzen-xmlpath_0.0~git20140218.13f4951.orig.tar.xz
golang-github-masterzen-xmlpath_0
