[Gimp-print-devel] 5.2.13

I've posted the 5.2.13 tarball; Steve, you can do the OS X build
whenever it's convenient.

Solomon Peachy

2017-07-17 14:09:03 UTC

Post by Robert Krawitz
I've posted the 5.2.13 tarball; Steve, you can do the OS X build
whenever it's convenient.

The NEWS and README still list '5.2.13-pre1'

(As an aside, I also just committed a bugfix for the Mitsu CP9500D
printer. Assuming you respin the tarballs, it would be really nifty
if that could get in too..)

- Solomon

--
Solomon Peachy pizza at shaftnet dot org
Delray Beach, FL ^^ (email/xmpp) ^^
Quidquid latine dictum sit, altum videtur.

Robert Krawitz

2017-07-17 14:15:13 UTC

Post by Robert Krawitz
I've posted the 5.2.13 tarball; Steve, you can do the OS X build
whenever it's convenient.

The NEWS and README still list '5.2.13-pre1'

In the tarball?

It looks like I neglected to push it.

I'm going rebuild the tarball.

Post by Solomon Peachy
(As an aside, I also just committed a bugfix for the Mitsu CP9500D
printer. Assuming you respin the tarballs, it would be really nifty
if that could get in too..)

Solomon Peachy

2017-07-17 14:25:56 UTC

Post by Solomon Peachy
The NEWS and README still list '5.2.13-pre1'

In the tarball?
It looks like I neglected to push it.

No, in the repo -- it looks like you pushed the tag, which referenced a
commit that fixed up the README/NEWS file. So the tarball is probably
okay. (Can't check right now..)

- Solomon

--
Solomon Peachy pizza at shaftnet dot org
Delray Beach, FL ^^ (email/xmpp) ^^
Quidquid latine dictum sit, altum videtur.

Robert Krawitz

2017-07-17 14:31:07 UTC

Post by Solomon Peachy
The NEWS and README still list '5.2.13-pre1'

In the tarball?
It looks like I neglected to push it.

No, in the repo -- it looks like you pushed the tag, which referenced a
commit that fixed up the README/NEWS file. So the tarball is probably
okay. (Can't check right now..)

Sigh. I'm re-pushing right now.

That's probably going to leave the tag all messed up.

Solomon Peachy

2017-07-17 14:35:52 UTC

Post by Robert Krawitz
Sigh. I'm re-pushing right now.
That's probably going to leave the tag all messed up.

The tag itself is fine; it's just not on the 'master' branch thanks to
my poorly-timed commit. :/

- Solomon

--
Solomon Peachy pizza at shaftnet dot org
Delray Beach, FL ^^ (email/xmpp) ^^
Quidquid latine dictum sit, altum videtur.

Robert Krawitz

2017-07-17 14:45:11 UTC

Post by Robert Krawitz
Sigh. I'm re-pushing right now.
That's probably going to leave the tag all messed up.

The tag itself is fine; it's just not on the 'master' branch thanks to
my poorly-timed commit. :/

I deleted the remote tag (bad me!) and re-created it.

Robert Krawitz

2017-07-17 14:52:47 UTC

Post by Robert Krawitz
Sigh. I'm re-pushing right now.
That's probably going to leave the tag all messed up.

The tag itself is fine; it's just not on the 'master' branch thanks to
my poorly-timed commit. :/

I deleted the remote tag (bad me!) and re-created it.

Not quite...

Robert Krawitz

2017-07-17 14:56:25 UTC

Post by Robert Krawitz
Sigh. I'm re-pushing right now.
That's probably going to leave the tag all messed up.

The tag itself is fine; it's just not on the 'master' branch thanks to
my poorly-timed commit. :/

I deleted the remote tag (bad me!) and re-created it.

OK, now I think I've cleaned it up.

If you've pulled since last night, you need to:

% git reset --hard d3784bd141c31a32c004bea97cb9fca993203e73
% git tag -d gutenprint-5_2_13
% git pull

Robert Krawitz

2017-07-17 14:32:47 UTC

Post by Solomon Peachy
The NEWS and README still list '5.2.13-pre1'

In the tarball?
It looks like I neglected to push it.

No, in the repo -- it looks like you pushed the tag, which referenced a
commit that fixed up the README/NEWS file. So the tarball is probably
okay. (Can't check right now..)

Try it now -- I pushed what I think is everything.

(I hate that you have to push tags and changes separately, or am I
missing something?)

Robert Krawitz

2017-07-17 14:35:46 UTC

Post by Solomon Peachy
The NEWS and README still list '5.2.13-pre1'

In the tarball?
It looks like I neglected to push it.

No, in the repo -- it looks like you pushed the tag, which referenced a
commit that fixed up the README/NEWS file. So the tarball is probably
okay. (Can't check right now..)

Try it now -- I pushed what I think is everything.
(I hate that you have to push tags and changes separately, or am I
missing something?)

I did rebuild the tarball, BTW.

Greg Troxel

2017-07-23 12:25:53 UTC

Post by Robert Krawitz
I've posted the 5.2.13 tarball; Steve, you can do the OS X build
whenever it's convenient.

I just updated pkgsrc to 5.2.13. It builds ok (modulo a few not
important warnings) on NetBSD 7 amd64, and the test suite passes.

Sorry if I misread/misremembered your intent, but I gather the source
counted as a release and you're waiting for binary builds to be
available to announce, to avoid the flood of questions that would
otherwise result.

Robert Krawitz

2017-07-23 14:16:44 UTC

--=-=-Content-Type: text/plain

Post by Robert Krawitz
I've posted the 5.2.13 tarball; Steve, you can do the OS X build
whenever it's convenient.

I just updated pkgsrc to 5.2.13. It builds ok (modulo a few not
important warnings) on NetBSD 7 amd64, and the test suite passes.
Sorry if I misread/misremembered your intent, but I gather the source
counted as a release and you're waiting for binary builds to be
available to announce, to avoid the flood of questions that would
otherwise result.

No, please pull it. I haven't announced the release yet because there
is concern about some large format Epson printers.

Greg Troxel

2017-07-23 14:20:51 UTC