[Pkg-julia-devel] Review utf8proc 2.0.1-1 before upload

Peter Colberg peter at colberg.org
Sun Jul 17 22:42:31 UTC 2016


On Sun, Jul 17, 2016 at 10:00:21AM +0200, Graham Inggs wrote:
> The tests seem to fail with unicode-data 8.0-3.  The minimum version
> of the build-dependency on unicode-data might need a bump, unless it
> can be modified to build with either.

I tightened the build-dependency, which is needed anyway to fully test
Unicode 9.0 support on all architectures. It worked previously using
older versions, but that also meant that the tests were incomplete.

Does Debian testing migration consider Build-Depends? I found only one
discussion [1] from 8 years ago which says it is not considered.

I am planning to propose to the unicode-data maintainer to package
each version separately, e.g., unicode-data-9.0, with a versioned
Provides: unicode-data (= ${binary:Version}). Separate packages could
be kept as long as needed to avoid breakage of dependent libraries, in
particular shortly before a freeze. I found one other package with a
strict build-dependency [2].

> In debian/control, I would use the cgit path for Vcs-Browser, i.e.:
> Vcs-Browser: https://anonscm.debian.org/cgit/pkg-julia/utf8proc.git
> I don't know whether that makes a difference.

IIRC, after a discussion on debian-devel, alioth was reconfigured to
allow cloning and browsing both under /git/ and /cgit/. I use /git/ in
both Vcs-* fields after a sponsor did so [3] on one of my packages.

I wrote to admin at alioth.d.o with a proposal to redirect /cgit/ →
/git/ to make the latter canonical, but so far did not hear back.

> Did upstream only add two symbols? [1]  Then why did they to bump the SONAME?

I included a link [4] in commit cd5ed8f that explains the ABI bump:
two fields in utf8proc_property_struct changed from int32 to uint16.

> IIRC, the new libutf8proc2 package means the upload will go through
> binNEW and your upload might be rejected.
> I suggest you try anyway and I'll upload if necessary.

Does “pass through the NEW queue” [5] include binNEW packages?

If so, I guess it is better if you sponsor right away.

Peter

[1] https://lists.debian.org/debian-release/2008/05/msg00096.html
[2] https://sources.debian.net/src/gucharmap/1:9.0.0-1/debian/control/?hl=28#L28
[3] https://anonscm.debian.org/git/letsencrypt/acmetool.git/commit/?id=011533683b306ccdce2445f93cbf0b5e0cf23ff5
[4] https://github.com/JuliaLang/utf8proc/pull/62
[5] https://wiki.debian.org/DebianMaintainer/Tutorial#Uploading_packages



More information about the Pkg-julia-devel mailing list