> @Norbert: nevertheless I'd follow Karl's advice to build dvisvgm
Fully agreed. The integration of dvisvgm into the TL sources is always a
bit hacky.
Best
Norbert
--
PREINING Norbert http://www.preining.info
Accelia Inc. + IFMGA ProGuide + TU Wien + JAIST + TeX
On 16.08.19 20:11, Hector Oron wrote:
Hi Hector,
> JFYI, a give back (package rebuild from failed state) has been triggered
> per IRC request:
>
> Day changed to 16 Aug 2019
> 12:08 < gnu_srs1> (11:51:02 PM) srs: Can somebody gb texlive-bin
> 2019.20190605.51237-2 on
>
Hello,
JFYI, a give back (package rebuild from failed state) has been triggered per
IRC request:
Day changed to 16 Aug 2019
12:08 < gnu_srs1> (11:51:02 PM) srs: Can somebody gb texlive-bin
2019.20190605.51237-2 on
hurd-i386. It built fine locally.
signature.asc
Control: block 926701 by 932968
Control: tags 926701 + pending
Am 30.07.2019 um 08:20 teilte Norbert Preining mit:
> On Tue, 30 Jul 2019, Hilmar Preuße wrote:
>> rejected) you have to tag commit
>
> Thanks for the warning, but I have already tagged, but not pushed ;-)
>
Bug manipulation.
H.
On Tue, 30 Jul 2019, Hilmar Preuße wrote:
> rejected) you have to tag commit
Thanks for the warning, but I have already tagged, but not pushed ;-)
Norbert
--
PREINING Norbert http://www.preining.info
Accelia Inc. + IFMGA ProGuide + TU Wien + JAIST + TeX Live +
Am 26.07.2019 um 15:07 teilte Norbert Preining mit:
Hi Norbert,
> Uploaded.
>
> I wait with tagging until it is accepted.
>
I just noticed that the debian/watch file I created was broken. I've
corrected it and pushed it to github. So (unless our package get's
rejected) you have to tag commit
Am 26.07.2019 um 07:24 teilte Norbert Preining mit:
On Thu, 25 Jul 2019, Hilmar Preuße wrote:
Hi,
dvisvgm build (and links) fine on Hurd. We have a failure in the test
suite. I'll care about that later on.
Ok, please check that
I opened a bug @upstream [1] and got a patch for it. I'll
On Fri, 26 Jul 2019, Hilmar Preuße wrote:
> For the issue on Hurd I got a patch; I'll test it ASAP. The chroot on
That could be the non-source upload in case of acceptance.
Norbert
--
PREINING Norbert http://www.preining.info
Accelia Inc. + IFMGA ProGuide + TU Wien
Am 26.07.2019 um 15:07 teilte Norbert Preining mit:
Hi,
Uploaded.
I wait with tagging until it is accepted.
Great thanks!
For the issue on Hurd I got a patch; I'll test it ASAP. The chroot on
exodar was fixed, so I can use an official Debian porters box. Hope this
is more fun, than my
Uploaded.
I wait with tagging until it is accepted.
On Fri, 26 Jul 2019, Hilmar Preuße wrote:
>
> Am 26.07.2019 um 14:41 teilte Norbert Preining mit:
>
> > How do you interpret this?
> >
> See below.
>
> > On Fri, 26 Jul 2019, Hilmar Preuße wrote:
> > > From now on, we will no longer allow
Am 26.07.2019 um 14:41 teilte Norbert Preining mit:
How do you interpret this?
See below.
On Fri, 26 Jul 2019, Hilmar Preuße wrote:
From now on, we will no longer allow binaries uploaded by maintainers to
migrate to testing. This means that you will need to do source-only
uploads if you
On Fri, 26 Jul 2019, Hilmar Preuße wrote:
> Yes. It has to got through the new queue. Once this is done we can care
Just to check, going to NEW do we need to do source only or
source/binary uploads? Do you remember?
Norbert
--
PREINING Norbert
Am 26.07.2019 um 14:28 teilte Norbert Preining mit:
On Fri, 26 Jul 2019, Hilmar Preuße wrote:
Hi,
Yes. It has to got through the new queue. Once this is done we can care
Just to check, going to NEW do we need to do source only or
source/binary uploads? Do you remember?
No binary
Am 26.07.2019 um 14:29 teilte Norbert Preining mit:
Hi,
Yes. It has to got through the new queue. Once this is done we can
care about tl-binaries.
Actually since you put in only a suggest, we could do that immediately.
I am not sure whether we shouldn't do a Depends on dvisvgm instead...
I
Hi
How do you interpret this?
On Fri, 26 Jul 2019, Hilmar Preuße wrote:
> From now on, we will no longer allow binaries uploaded by maintainers to
> migrate to testing. This means that you will need to do source-only
> uploads if you want them to reach bullseye.
...
> Q: I needed to do a
> Yes. It has to got through the new queue. Once this is done we can care
> about tl-binaries.
Actually since you put in only a suggest, we could do that immediately.
I am not sure whether we shouldn't do a Depends on dvisvgm instead...
Norbert
--
PREINING Norbert
Am 26.07.2019 um 13:48 teilte Norbert Preining mit:
Hi,
Done for dvisvgm. texlive-binaries has been adapted too, dvisvgm is not
built any more, manual page is not installed.
Ok, so should I upload dvisvgm?
Yes. It has to got through the new queue. Once this is done we can care
about
Hallo Hilmar,
> Done for dvisvgm. texlive-binaries has been adapted too, dvisvgm is not
> built any more, manual page is not installed.
Ok, so should I upload dvisvgm?
> ??? What kind of support files? The manual page is not installed by
> tl-bin any more. The dvisvgm package just contains
On 26.07.19 07:55, Norbert Preining wrote:
Hi Norbert,
> We still need to do the replace stuff ... I might be able to look into
> it tomorrow, but today my time is running out.
>
> We need for sure replaces: texlive-binaries <= the current version in
> sid. Then we disable it for the next
Hi Hilmar,
On Fri, 26 Jul 2019, Hilmar Preuße wrote:
> > Should we rewrite the history? Or leave it like it is?
> >
> Leave it.
Ok.
> I can't promise that I'll have a result soon. As Hurd is not a release
> arch I don't see that as a show stopper. We could fix that in -1+x (with
> x >= 1).
On 26.07.19 07:24, Norbert Preining wrote:
Hi Norbert,
> On Thu, 25 Jul 2019, Hilmar Preuße wrote:
>>> hille@debian-amd64-sid
>>>
>> Solved...hopefully. Sorry, missed that.
>
> Should we rewrite the history? Or leave it like it is?
>
Leave it.
>> We're lintian clean. Do you have to chance
Hi Hilmar,
On Thu, 25 Jul 2019, Hilmar Preuße wrote:
> > hille@debian-amd64-sid
> >
> Solved...hopefully. Sorry, missed that.
Should we rewrite the history? Or leave it like it is?
> Statical "linking" the md5 calculation code solved the problem.
Thanks
> Have to re-learn that... ;-( Do
Am 25.07.2019 um 23:53 teilte Hilmar Preuße mit:
Am 25.07.2019 um 20:53 teilte Norbert Preining mit:
Hi,
- I did not push the orig.tar.gz to pristine-tar branch yet, it is on
[1], please push the code.
Ok, please do so at some point.
Have to re-learn that... ;-( Do I have to create
Am 25.07.2019 um 20:53 teilte Norbert Preining mit:
Hi,
a few things:
- your email is not configured for git, git lists
hille@debian-amd64-sid
as email.
Solved...hopefully. Sorry, missed that.
E: dvisvgm: possible-gpl-code-linked-with-openssl
That is still open.
Statical
Hi Hilmar,
a few things:
- your email is not configured for git, git lists
hille@debian-amd64-sid
as email.
> W: dvisvgm source: useless-autoreconf-build-depends autotools-dev
fixed
> W: dvisvgm source: dep5-copyright-license-name-not-unique gpl-3+
> (paragraph at line 11)
> W:
Am 25.07.2019 um 14:24 teilte Norbert Preining mit:
Hi Norbert,
No need to be lintian clean. It should be lintian clean when we tag a
release, not before. Please don't hesitate to commit half-backed not
ready stuff, that is normal!!
Looking forward to your work.
OK, I pushed everything to
Hi Hilmar,
On Thu, 25 Jul 2019, Hilmar Preuße wrote:
> I've created a repo on github now. The package should be at least
> lintian clean before first commit.
No need to be lintian clean. It should be lintian clean when we tag a
release, not before. Please don't hesitate to commit half-backed not
On 25.07.19 11:00, Norbert Preining wrote:
> On Thu, 25 Jul 2019, Hilmar Preuße wrote:
Hi,
>> I did some basic steps in packaging dvisvgm separately. Of course I'll
>
> Great, did you push your work to github so that I can take a look at it?
> I will also take a look into the replace/depends
Hi Hilmar,
On Thu, 25 Jul 2019, Hilmar Preuße wrote:
> I did some basic steps in packaging dvisvgm separately. Of course I'll
Great, did you push your work to github so that I can take a look at it?
I will also take a look into the replace/depends calls necessary for the
upgrade.
Thanks a lot
29 matches
Mail list logo
