Jonas,
The Rust bindings for Leptonica appear unhappy after the leptonlib
transition; perhaps they need to be regenerated? The specific
complaint seems to be "test bindgen_test_layout_max_align_t ... FAILED". I
am unfamiliar with Rust and unsure how to proceed.
https://ci.debian.net/packages/r/ru
I will take a look
leptonlib 1.83.1-4 uploaded to unstable. Also did NMU for dependency level
2 (tesseract, jbig2enc, k2pdfopt). Possibly I did the NMU too soon and the
autobuilders will get confused; will find out soon enough.
Hi Sebastian, may I proceed with transition?
control: tags 1081319 - moreinfo
libleptonica6 has been accepted into experimental, and I am ready to
proceed.
Control: tags - moreinfo
I have filed bugs with patches for the reverse dependencies that need
changes.
Bug numbers are 1081969 1081968 1081970
Currently waiting for leptonica6 to clear the NEW queue and enter
experimental.
The library name has changed from liblept to libleptonica. So I have now
changed the package name from liblept5 to libleptonica6. This is uploaded
to experimental as leptonlib_1.84.1-3. I am including the revised Ben file
below and attaching the patch for the most complex reverse dependency. All
re
Package: release.debian.org
Severity: normal
X-Debbugs-Cc: lepton...@packages.debian.org, j...@debian.org
Control: affects -1 + src:leptonlib
User: release.debian@packages.debian.org
Usertags: transition
Upstream has changed the name of the library.
BEFORE: liblept.so.5
AFTER: libleptonica.so
libwebp 1.2.1-7 has been successfully uploaded to unstable.
Anthony and Iustin, help is very strongly appreciated for the NMUs.
# remove the moreinfo tag
tags 1003548 - moreinfo
thanks
Sebastian, may we move forward with ibwebp?
To make it super clear, here is the updated formal request with updated Ben
file.
===
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
Hello Release Team,
We would like to transition libwebp to a new upstream version 1.2.1-6
The package has been corrected with version 1.2.1-6 which has
been uploaded to experimental.
Please let us know if we can proceed with the upload to unstable. Also
a binNMU rebuild of reverse dependencies would be required afterwards.
Attempted fix for Tesseract fix uploaded just now.
Beginning transition. Uploaded to unstable.
>Do the packages in
https://release.debian.org/transitions/html/auto-libwebp.html
>build fine against the new libwebpmux ?
There was a bug the libwep control file. I fixed that and uploaded
0.6.0-2 to experimental just now. Then I did some testing on AMD64 to
answer your question. Everything on th
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
This is a clean ABI bump. I've updated the symbols file appropriately.
New package has been uploaded to experimental.
Please be aware that the primary binary library package (libwebp6) i
Okay, clearly not webp. Sorry for the noise.
Makefile:1711: recipe for target 'lua/intf/cli.luac' failed
Bas> and vlc FTBFS on mips* before the libwebp NMUs.
Emilio> That needs to be looked at.
Do I understand correctly that the FTBFS is unrelated to webp?
webp 0.5.1 is now in unstable, will see if anything explodes
I have build-tested the reverse dependencies against the new libwebp
version.
>Have you build-tested the reverse dependencies against the new libwebp
version?
I've build tested a bunch of them successfully, and the rest are still
running.
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
This is a new upstream release and includes a soname bump on all three
shared libraries. I've only expressed the primary one in the Ben file;
please update as appropraite. Note that libwe
retitle 815919 nmu: tesseract_3.04.01-4 openalpr_2.2.3-1
gimagereader_3.1.2+git368fa8f-2 sikuli_1.0~x~rc3.tesseract3-dfsg1-12
thanks
There are some good reasons to do this sooner rather than later.
I've been advised on Debian Devel IRC mainly by juliank to stick
to libtesseract3 and not do libtesseract3a. See bug 815056.
Personally, I am in over my head but the IRC folks sound confident
that this is the right course of action.
P.S. Tersseract 3.04.01-4 has a breaks/replace against the ill fa
Subject: transition: tesseract-ocr
Package: release.debian.org
User: release.debian@packages.debian.org
Usertags: transition
Severity: normal
As described in bug #815056, there was a packaging mistake that led to
the brief existance of libtesseract4. This problem has been corrected
and we are
Upstream has looked at compatibility and decided to
not bump soname for this package. I'll give things a week
to settle down and then this bug is ready for closure.
Thank you, Julien. I'll talk to upstream and get a few more
details. They definitely bumped the soname for their
release, and probably for a good reason. The libwebp
upstream folks generally have their act together.
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
Tesseract upstream is releasing a new version that will
have an increased soname (libtesseact3 -> libtesseract4).
No exotic challenges expected.
-- System Information:
Debian Release: wh
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
Leptonica upstream is releasing a new version that will
have an increased soname (liblept3 -> liblept4). No exotic
challenges expected.
-- System Information:
Debian Release: wheezy/sid
Ping.
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
Upstream is releasing a new version of webp soon that has an expanded
API, and therefore will bump soname and package from libwebp4 to
libwebp5. Reverse dependency list appended; I think
> That diffstat is cerainly much larger than can be accepted at this stage
> in the release. Have you contacted the security team about these? It's
> possible to look at getting an update in after the release which fixes
> these specific issues.
I contacted the security team January 9th, no respon
Ping.
On Sun, Jan 16, 2011 at 6:19 PM, Jeff Breidenbach wrote:
>> diffstat: 61 files changed, 1502 insertions(+), 657 deletions(-)
>> Is all of that necessary to fix the security issues?
>
> No.
>
> However, I do not have the ability to isolate (and especially validate)
&
> diffstat: 61 files changed, 1502 insertions(+), 657 deletions(-)
> Is all of that necessary to fix the security issues?
No.
However, I do not have the ability to isolate (and especially validate)
just the security fixes. Additionally, it is conservative release that
should not break any existin
"Not touching package due to block request by freeze (contact debian-release
if update is needed)"
This mhonarc release fixes multiple security problems. Please propagate it
everywhere.
http://security-tracker.debian.org/tracker/source-package/mhonarc
-Jeff (the package maintainer)
Hi Sarge release team,
The java packing team just got blindsided by bug #300209, which
appears to have knocked tomcat4 out of Sarge. Heads up that you
may hear some begging for re-inclusion in the near future.
Jeff
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe".
37 matches
Mail list logo
