Dear all,
TeX Live Multiarch ...
On Mon, 28 Sep 2015, Johannes Schauer wrote:
> > may I safely assume that I can upload the current status to
> > unstable sooner or later?
>
> yes, please do!
Done that just now:
tex-common 6.04
texlive-bin 2015.20150524.37493-7
Hi Norbert,
Quoting Norbert Preining (2015-09-28 09:51:28)
> may I safely assume that I can upload the current status to
> unstable sooner or later?
yes, please do!
Thanks again for all your work, testing and patience with us :)
cheers, josch
signature.asc
Description: signature
Dear all,
may I safely assume that I can upload the current status to
unstable sooner or later?
Norbert
PREINING, Norbert http://www.preining.info
JAIST, Japan T
On Fri, 25 Sep 2015, Norbert Preining wrote:
> texlive-lang and texlive-extra are being built now and I will upload
> them during the day.
Upload is running, should be there in 15min (according to unison)
Norbert
PREINING,
Hi,
Quoting Norbert Preining (2015-09-25 10:13:29)
> > mftrace complains: texlive-fonts-recommended : Depends: texlive-base (>=
> > 2015) but it is not going to be installed
> > That has:
> > Depends: texlive-base (>= 2015), tex-common (>= 6)
> > Breaks: texlive-base (<< 2015)
> > Not obvious to
Hi Wookey, hi all,
thanks for testing, that is very much appreciated.
> Quite a few packages don't install their tex-related build-deps yet:
> (xnee, r-base, jags, sdformat, m-tx, systemtap, music, frobby, transfig,
> noweb) due to texlive-extra not being M-A yet
texlive-lang and texlive-extra
+++ Norbert Preining [2015-09-23 23:17 +0900]:
> > - crosscompile a source package that build depends on texlive-binaries
> > (but I
> >hear Helmut already did that successfully)
>
> I will leave that to one of you, as I hav eno idea how to cross-compile
> something.
OK, I tested installati
+++ Norbert Preining [2015-09-23 23:17 +0900]:
> Hi Johannes, dear all
>
> thanks for your explanations, that helped a lot.
>
> I have now made the following test:
>
> > - install a package in a foreign architecture that depends on
> > texlive-binaries
>
> Namely, install xdvik-ja:i386 on a a
Hi Johannes, dear all
thanks for your explanations, that helped a lot.
I have now made the following test:
> - install a package in a foreign architecture that depends on
> texlive-binaries
Namely, install xdvik-ja:i386 on a amd64 system with the test packages
being available.
Installation w
Hi,
Quoting Norbert Preining (2015-09-22 14:57:44)
> I have now built tex-common and src:texlive-bin according to the
> discussed changes:
>
> > tex-common, texlive-lang, telxive-doc, texlive-base
> > M-A: foreign
> > texlive-binaries: M-A: foreign
> > lib*, lib*-dev: M-A:
debian-cr...@lists.debian.org
Subject: Re: Bug#792281: texlive-latex-base: not Multi-Arch: foreign
X-Spam-Status: No, score=-5.7 required=4.0 tests=HEADER_FROM_DIFFERENT_DOMAINS,
LDO_WHITELIST,RCVD_IN_DNSWL_LOW autolearn=unavailable autolearn_force=no
version=3.4.0
List-Id:
Dear al
Dear all,
I have now built tex-common and src:texlive-bin according to the
discussed changes:
> tex-common, texlive-lang, telxive-doc, texlive-base
> M-A: foreign
> texlive-binaries: M-A: foreign
> lib*, lib*-dev: M-A: same
> luatex: M-A: foreign (dummy transitional
Hi Thorsten,
thanks for the advice. Since 200 I never needed -Wno-error, and I think it
should not be necessary, so I am going through the code and fix all the
occurrences and will submit my fixes to upstream.
But for my testing of the M-A changes I'll use -Wno-error for the time being.
Thanks
Norbert Preining dixit:
>I am now trying to build the package - without success - debhelper9
>or gcc5 (don't know what) changed several warnings to errors
You *really* should use -Wno-error when compiling for Debian
(as opposed to compiling for your own testing) because that’s
a given – newer ver
Minna-sama
Thanks everyone - I have now made all the changes and pushed the
changes to the git repo.
Current status:
tex-common, texlive-lang, telxive-doc, texlive-base
M-A: foreign
texlive-binaries: M-A: foreign
lib*, lib*-dev: M-A: same
luatex: M-A: foreign (dummy
Norbert Preining dixit:
>Is there a place to install *arch* dependent header files?
Put it into /usr/include/$multiarch/kpathsea/ then.
The M-A capable compilers have an implicit -I/usr/include/$multiarch
so #include will find it.
Thanks for the visible amount of work you’re investing into this
+++ Johannes Schauer [2015-09-20 09:46 +0200]:
> Quoting Norbert Preining (2015-09-20 08:55:27)
> > > yes, there is /usr/include//
>
> as pointed out earlier, the -dev packages should be M-A:same and not foreign.
> For that, all files shared across architectures must be exactly the same and
> all
Hi,
Quoting Norbert Preining (2015-09-20 08:55:27)
> > yes, there is /usr/include//
>
> great, thanks. Should that part (in fact only c-auto.h) go into the lib
> package (libkpathsea6) and thus keep the -dev package M-A: foreign, or can I
> put that header file into the -dev package and do M-A:
Hi
(just short from the Jazz festival ...)
> yes, there is /usr/include//
great, thanks. Should that part (in fact only c-auto.h) go into the lib package
(libkpathsea6) and thus keep the -dev package M-A: foreign, or can I put that
header file into the -dev package and do M-A: same? Or are th
Hi Norbert,
Quoting Norbert Preining (2015-09-20 04:20:34)
> On Sun, 20 Sep 2015, Norbert Preining wrote:
> > /* The size of `long', as computed by sizeof. */
> > -#define SIZEOF_LONG 8
> > +#define SIZEOF_LONG 4
>
> Concerning this:
> Is there a place to install *arch* dependent header files?
Hi all,
On Sun, 20 Sep 2015, Norbert Preining wrote:
> /* The size of `long', as computed by sizeof. */
> -#define SIZEOF_LONG 8
> +#define SIZEOF_LONG 4
Concerning this:
Is there a place to install *arch* dependent header files?
To explain the situation: The normal texlive installation puts
th
Hi all,
thanks for the great suggestions and guidelines!!
On Fri, 18 Sep 2015, Johannes Schauer wrote:
> - libkpathsea-dev, libptexenc-dev, libsynctex-dev, libtexlua52-dev,
>libtexluajit-dev carry the development headers and *.a files and a symlink
>to the shared library. *-dev packages
Hi Norbert,
Quoting Norbert Preining (2015-09-18 09:28:24)
> > > then again, the real problem is not mixing i386 and am64, but
> > > big-endian and little-endian systems.
> >
> > Being endianess-aware can be a good reason for not marking something
> > M-A:foreign.
>
> I did check back with the t
+++ Norbert Preining [2015-09-18 16:28 +0900]:
> Hi Helmut, hi all,
>
> > > then again, the real problem is not mixing i386 and am64, but
> > > big-endian and little-endian systems.
> >
> > Being endianess-aware can be a good reason for not marking something
> > M-A:foreign.
>
> I did check back
Hi Helmut, hi all,
> > then again, the real problem is not mixing i386 and am64, but
> > big-endian and little-endian systems.
>
> Being endianess-aware can be a good reason for not marking something
> M-A:foreign.
I did check back with the tex-k development list, as well as doing
my own experim
Hi Norbert,
On Fri, Sep 18, 2015 at 12:02:58AM +0900, Norbert Preining wrote:
> I think the prime problem is with tex-common, although you didn't
> spot it. tex-common declares an interest on some files called
> format files. TeX (and friends like metafont) create dump files,
> memory images, whic
Hi Helmut,
thanks for your detailed answer, that is very helpful. I slowly
might get a feeling about what is necessary.
You broadly overestimate my understanding here:
> You are already understanding M-A stuff quite well as can be seen from
> the quality of your questions.
since I not even unde
Hi Norbert,
On Thu, Sep 17, 2015 at 03:23:26PM +0900, Norbert Preining wrote:
> sorry, I just found time to come back to this topic. Thanks for
> your explanations, but I need to confirm a few things first:
Thank you for taking the time to try and understand multiarch instead of
blindly applying
I forgot to add
On Thu, 17 Sep 2015, Norbert Preining wrote:
> What about the libraries build by src:texlive-bin? Would the need
> to be moved, or is there some dh magic that is doing this?
texlive-bin builds a different set of packages depending on the
architecture. and also the set of binaries
Hi Helmut,
sorry, I just found time to come back to this topic. Thanks for
your explanations, but I need to confirm a few things first:
> A package can expose architecture via three mechanisms:
> * Content
> * Maintainer scripts
> * Dependencies
>
> For arch:all packages (such as tex-common,
On Mon, Jul 13, 2015 at 04:28:05PM +0200, Thorsten Glaser wrote:
> Please add M-A: foreign to the relevant texlive-* packages.
> Do check with the M-A wizards (such as Helmut Grohne) for
> their correctness, though…
A package can expose architecture via three mechanisms:
* Content
* Maintainer s
Hi Thorsten!
On Mon, 13 Jul 2015, Thorsten Glaser wrote:
> Please add M-A: foreign to the relevant texlive-* packages.
> Do check with the M-A wizards (such as Helmut Grohne) for
> their correctness, though…
Good question ... the files under /usr/share/texlive are not
the problem, but there are m
Package: texlive-latex-base
Version: 2015.20150703-1
Severity: normal
Hi, this is a packaging issue ;-)
I would like to make mediawiki-math-texvc Multi-Arch: foreign,
but that means it still depends on texlive-latex-base and
texlive-latex-extra on the foreign arch (e.g. i386) as they
lack a Multi
33 matches
Mail list logo
