ICU 3.6 is in debian unstable now. Hopefully openoffice.org built
against it will follow soon. Then we can see if this bug is still
present in 3.6.
--
Incorrect Bengali rendering of ra+japhala
https://launchpad.net/bugs/35085
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Is anything happening with this? Applying the patch to the icu in
debian doesn't impact the rendering of test-case.odt. Debian bug 357137
has been open for some time, and I probably can't resolve it until this
problem is resolved. Alternatively, if someone would like to post a
proper patch to
The automatically generated links above do not point to the debian bug.
They point to a bug in this system with the same number should any such
bug eventually exist...
--
Incorrect Bengali rendering of ra+japhala
https://launchpad.net/bugs/35085
--
ubuntu-bugs mailing list
I just tried installing Etch using debian-installer b3, and I have good
X11 performance there too. Next time I have time, I'll try to figure
out the differences.
--
regression: poor X11 performance on Dell Latitude D810
https://launchpad.net/bugs/56100
--
ubuntu-bugs mailing list
This is probably my last update to this bug report as I am now running
etch instead of dapper on my laptop and have 100% of desired
functionality working. I prefer to be running debian but had been
running Ubuntu since it installed and worked more easily in the past,
but with this regression and
ICU 3.6 d02 (beta) is in debian experimental. I am going to see if I
can determine whether this bug is there in 3.6. Whoever is interested
in this may want to take advantage of this beta period of ICU to see if
they can get a patch upstream.
--
Incorrect Bengali rendering of ra+japhala
For what it's worth, after ICU 3.6 went into debian, openoffice reverted
to its internal ICU because of other apparent incompatibilities. I'm
not running Ubuntu right now, so I don't know whether Ubuntu has
followed. In any case, it's quite likely that this problem is no longer
reproducible in
I really appreciate this analysis. I will be uploading 7.15.5-2
momentarily with this patch (except, of course, the maintainer fields).
Also, I've used python*.* instead of python?.? in the install file, not
that I expect to see python 2.10 or 10.0, but it should be fine
anyway...
--
Please
Um, I'm not sure what it means for this bug to be assigned to me. I
have uploaded 7.15.5-2 into debian, but I wasn't planning on taking any
specific action on this bug. Hopefully, whoever does this sort of thing
in Ubuntu should be able to merge 7.15.5-2 from debian now without
having any custom
Last comment: hidden here is actually a bug in whichever viewers were
not showing incorrect colors since the problem was in the PDF file, not
the viewers.
--
xpdf viewer renders wrong colors for jpeg encoded images
https://bugs.launchpad.net/bugs/194295
You received this bug notification because
If you want an easy way to look into a PDF file, I recommend my qpdf
software, though in this case, you could look at the image dictionary in
the PDF file in a text editor. Solving this one required some
familiarity with the PDF spec.
--
xpdf viewer renders wrong colors for jpeg encoded images
Hello. I'm just looking over the tiff bugs in ubuntu. I'm the debian
tiff maintainer. Sorry you guys spent so much time on this. I was
already familiar with this problem. The problem is that tiff2pdf was
setting the /ColorTransform field to 0 in /DecodeParams when it should
not have been.
Public bug reported:
Binary package hint: xserver-xorg
For starters, let me state that I am aware that this is really an ATI
driver or fglrx driver problem, and not really an xserver-xorg problem.
Also, I have read several bugs already that discuss lockups and other
issues with the Radeon
I've done dpkg -P --force-depends xserver-xorg, rm /etc/X11/xorg.conf*,
apt-get install xserver-xorg to get a completely default xorg.conf. I
am attaching this here. This performance is only very slightly worse
than what I get if I install the proprietary ATI drivers from ATI's web
site using
I am confirming that this X11 performance problem is not present when I
boot off of breezy live. I snarfed the xorg.conf from the breezy live
configuration and tried using it. I also tried using vga=771 which was
necessary in breezy but not in badger. Neither of these things
completely solved
This is not a libtiff bug, and the fact that the tiff file is multipage
is not relevant. The problem is with the tiff file headers and with the
applications' interpretations of those headers. I believe eog and
evince are both misinterpreting the orientation header.
To rule out the multipage
In case it gets buried in the above comment, here is a workaround for
your problem:
* The above includes a workaround: run tiffcp your-image.tif new-
image.tif. The resulting image, at least in the case of the above
attachment, displays properly in all the above mentioned applications.
Also, I
Actually, I think the testing transition should happen in about 9 days
depending on its relationship to the openexr long double transition. In
case it makes any difference, the nip2 package has been updated for the
menu transition - it puts its menu files in Applications/Graphics
instead of
of the tiff packages for debian,
by the way. I don't generally follow bug reports on Ubuntu, but I check
in from time to time just to see if there's anything I need to be
concerned about.
--Jay Berkenbilt q...@debian.org
--
Libtiff-3.8.2 is distributed as libtiff4
https://bugs.launchpad.net/bugs
Okay, I confirm that the bug is still present with icu 3.6 in debian
sid.
--
Incorrect Bengali rendering of ra+japhala
https://launchpad.net/bugs/35085
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
The problem was resolved in comments here, and this now applies to a
very old version both qpdf and Ubuntu.
** Changed in: qpdf (Ubuntu)
Status: New = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Debian psutils 1.17-30 (just uploaded) now incorporates this patch.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/396025
Title:
psnup ignores -p option
To manage notifications about this bug go
Public bug reported:
I'm not sure whether I need to do this or not, but I just wanted to let
you know that I have incorporated all the Ubuntu changes into the debian
tiff package, so 3.9.5-2 should be essentially identical to
3.9.5-1ubuntu1. I was thinking it was time to figure out the multiarch
oneiros mar...@oneiros.de wrote:
2010/3/30 Jay Berkenbilt e...@ql.org:
standards version to 3.8.4. Let me know if you'd like me to make the
2.1.3 packages available somewhere. There may be a 2.1.4 soon anyway
based on your padding issue.
Jay,
I'm new to building debian packages from
Public bug reported:
As debian maintainer for the xerces-c package, I'd like to suggest a
Freeze Exception for this package. The version presently in lucid is
3.1.0~rc1-1. This is a release candidate that I put into debian at the
specific request of upstream. Given that the final 3.1.0 version
This isn't a bug. xerces-c 3.x doesn't supply libderces-depdom at all.
That is the deprecated DOM library, and it was dropped in 3.x. For
details, see http://xerces.apache.org/xerces-c/migrate-
archive-3.html#Migrateto300
--
Missing libxerces-depmod.so symbolic link
The first problem is a gcc 4.4 issue. I'm not sure what the second
problem is. I have already uploaded 2.1.3 to debian unstable, but it
won't show up until the current ftp-master hardware problems are
resolved. No changes were required from the 2.1.2 packaging. I updated
standards version to
For anyone who's watching, qpdf-3.0~rc1-1 is now in debian experimental.
Running the test suite is now enabled in the build. Based on the exp
buildd logs, it build and passed its test suite on all debian platforms.
My plan is to allow a couple of weeks for feedback on the release
candidate from a
(For the build dependency, of course, I mean libqpdf-dev 3.0~)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1024435
Title:
[MIR] qpdf
To manage notifications about this bug go to:
Okay, I'll upload 3.0 final sooner. Is experimental okay, or do I need
to upload to unstable in debian? Debian is in freeze right now. I'll
aim for August 2 or 3 to upload 3.0 final.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
qpdf 3.0.0-1 is in debian experimental now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1024435
Title:
[MIR] qpdf
To manage notifications about this bug go to:
As the debian maintainer of tiff, I would like to see tiff and tiff3
synced. Among other things, this will allow vips and nip2 with bigtiff
support to go in. Rather than blocking this on main inclusion of JBIG,
I'd suggest modifying it for Ubuntu to omit the jbig dependency. Simply
removing
For anyone watching, qpdf_4.0.1-2 in debian has had a fix for this
problem since February 25. The patch should be easy to backport to the
version in 12.10.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This patch is relative to 4.0.1. I suspect that it will apply cleanly
to 3.whatever-you-have with at most offsets. The change is very
localized. If you run into any problems, you can post here. I'm
subscribed to this bug.
** Patch added: patch to fix this problem
I see the same problem on my system, and this patch fixes it for me.
I'm the debian maintainer of the tiff packages, so I will include this
patch and also submit the bug to upstream. The fix will be in Ubuntu
next time the tiff packages are synchronized.
--
You received this bug notification
Upstream bug report: http://bugzilla.maptools.org/show_bug.cgi?id=2401
It's not a very good bug report, but I think the problem is simple
enough that whoever knows that code should be able to judge that it is
correct.
** Bug watch added: bugzilla.maptools.org/ #2401
For what it's worth, I'll mention also that upstream is also a debian
developer since 2005 and is the debian maintainer of the package. qpdf
is known to be used in at least three commercial products and was used
by a former employer (who enthusiastically supported its open source
development) to
I'm the author of qpdf. You are certainly correct to be concerned about
the security exposure of qpdf, and I'd be the last one to say that it is
100% of any potential for security problems. However I believe that it
is in relatively good shape from a security perspective, and I'll
briefly
See also bug 1257487, the nip2 sync request.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1257485
Title:
request sync of nip2 and vips from Debian
To manage notifications about this bug go to:
Public bug reported:
Note: I am the debian maintainer for vips.
The version of vips in Ubuntu is very old. Debian is now up to date
again. (Had gotten behind because of wheezy release and libmatio
transition.) I believe the Ubuntu changes should be trivial to port
forward and should hopefully
Public bug reported:
Note: I am the debian maintainer of nip2.
Please resync nip2 from debian unstable. The version I just uploaded to
unstable, 7.36.4-3, is the right one to take. This version changes the
goffice dependency from 0.8 to 0.10, which is one of your changes.
Debian still has an
On 12/06/2013 04:11 PM, Jackson Doak wrote:
Please upload a version with the fixed build-depends (now debian is
doing to tiff5 transition) and we can sync, that is a lot easier than
merging for a week or two
I just uploaded vips 7.36.3-3 with the new tiff dependencies. Hopefully
this should
Maybe uns can work with libxerces-c-dev instead? Almost all of the
things that used libxerces-c2-dev worked fine with libxerces-c-dev
because there were very few API changes.
I filed the removal request with Debian, but I have no idea when it will
be done.
--
You received this bug notification
Public bug reported:
(I am the debian maintainer of ICU)
Ubuntu trusty still has ICU 4.8, which is pretty old and has lots of
bugs that have been fixed in the current release, 52.1. Debian has
completed its transition to ICU 52.1. I don't plan on uploading any new
upstream versions of ICU
Public bug reported:
(I am the debian maintainer of tiff)
I just uploaded 4.0.3-7 with a dependency on dh-autoreconf. Hopefully
this will allow you to eliminate the delta on this package and go back
to matching the version in debian.
** Affects: tiff (Ubuntu)
Importance: Undecided
The qpdfview program is not related to qpdf. They just have an
unfortunate similarity in their names.
There was a bug in qpdf that could cause loss of form data in some
cases, but this bug was fixed in qpdf 5.0.0. I don't remember whether
4.2.0 had the fix in it, but I don't think it did.
icu-tools ( ${binary:Version} isn't really appropriate for the debian
package and gives a lintian error since icu-tools is not packaged by the
icu source package. I don't think debian ever had icu-tools. I think I
added libicu-devtools to serve the same function as icu-tools. How
about if I
Okay, 52.1-3 is uploaded to sid. You should see it momentarily.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1263706
Title:
request sync: icu 52.1 from debian
To manage notifications about this
Public bug reported:
(I am the debian maintainer for tiff and tiff3)
A transition is nearing completion in debian for tiff, and once it is
done, I will be requesting removal of the tiff3 package. However, I
don't expect this to happen before the sync freeze for trusty. I don't
know if you have
Public bug reported:
(I am the debian maintainer for xerces-c and xerces-c2)
There are only three packages left in debian that have build
dependencies on xerces-c2, and after my NMU goes through in a few days,
there will only be two packages left. Of these, one is not in debian's
testing
Fixed in 4.2.0-2. 4.2.0-1 was not binary compatible. 4.2.0-2 is binary
compatible with 4.1.0. The offending fix that had been in 4.2.0 will be
in 5.0.0 instead.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
On 08/08/2012 07:29 PM, Jamie Strandboge wrote:
MIR review:
* Does not ship a symbols file or use an empty argument to dh_makeshlibs -V.
This should be considered, but is not a blocker.
Consider it considered. I'm not aware of shipping a symbols file, so
it's something for me to learn
Public bug reported:
Please sync qpdf 3.0.1-1 (universe) from Debian experimental (main)
Changelog entries since current quantal version 3.0.0-2:
qpdf (3.0.1-1) experimental; urgency=low
* New upstream release
-- Jay Berkenbilt q...@debian.org Sat, 11 Aug 2012 13:58:29 -0400
** Affects
The change from 3.0.0-2 is a small bug fix that enables proper parsing
of certain PDF files that have scalars not followed by whitespace at the
ends of object streams. It also corrects an omission from the 3.0.0
release notes. The bug fixed in this release has been present in all
versions of
xerces-c2 is now gone from debian's unstable and testing distributions.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1271718
Title:
xerces-c2 will soon disappear from debian
To manage
Debian is in freeze, but I could upload to experimental and ubuntu could
sync from there if that works.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1397413
Title:
QPDF: Exception: operation for
The only solution is to rebuild those drivers against current libtiff-
dev. There's nothing that can provide libtiff4 because libtiff5 is not
binary compatible with it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I guess getPageContents should just return an empty vector in that case
and the documentation should specify that an empty vector might be
returned. This is already the case if /Contents is literally an empty
array. Thanks for the triage.
--
You received this bug notification because you are a
This is sufficient to fix the problem, I believe. I will pushing a
commit with this change to github shortly after I finish ChangeLog
updates, etc. I also created a test cases that calls qpdf --show-pages
on a file that has a page with no content. I haven't tested in the
context of printing, but I
I have just uploaded 5.1.2-2 to debian unstable. You should be able to
sync with that version to get a fix.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1392048
Title:
File not printed Exception:
I haven't tried it myself, but qpdf has few dependencies, and the ones
it has are pretty stable, and qpdf itself is binary compatible between
5.1.1 and 5.1.2. My guess is that you if grabbed the libqpdf13 package
from Vivid and tried installing it in trusty, it would most likely work
fine.
--
The problem is that the root object of the pages tree does not have a
/Type key in its dictionary. The PDF spec says that /Type is required
and must be /Pages for the root.
qpdf could and should handle this particular type of damage or could at
least give a better error message for it, but that's
Before I commit this for real, I need to create a test case, but this
seems to be a correct fix.
** Patch added: page.diff
https://bugs.launchpad.net/ubuntu/+source/qpdf/+bug/1397413/+attachment/4272366/+files/page.diff
--
You received this bug notification because you are a member of
Sorry for the long delay. I have uploaded 5.1.2-3 to experimental.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1397413
Title:
QPDF: Exception: operation for Name object attempted on object of
Having qpdf able to treat strings as names would be a pretty small
enhancement and would probably improve its ability to handle a whole
category of broken files. I'll try to work this in for the next update.
Thanks for providing this detailed summary of the problem. Very helpful.
--
You received
https://github.com/qpdf/qpdf/issues/45
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1397413
Title:
QPDF: Exception: operation for Name object attempted on object of
wrong type
To manage
Does your problem happen with 5.1.2-3?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1397413
Title:
QPDF: Exception: operation for Name object attempted on object of
wrong type
To manage
Public bug reported:
When I run
$ flickr_upload --tag qtest x0.jpg
I get the error:
Uploading x0.jpg...Can't locate object method "sign_args" via package
"Flickr::Upload" at /usr/share/perl5/Flickr/Upload.pm line 234.
The following super-obvious patch resolves the issue. I'm not sure
how/why
I verified that this problem does not occur with the version of the
package from xenial. If I download that manually and install it,
everything works fine with the other versions from wily. So this problem
only affects the wily version and has already been corrected upstream
and in xenial.
--
If I'm reading this correctly, it looks like there's no short-term
change to qpdf required. Is that correct? I'm thinking doing this type
of flatting in qpdf is probably out of scope, but in any case, I
wouldn't have time to work on it any time soon. I haven't studied
interactive forms enough to
Public bug reported:
**NOTE** The additional information attached to this bug report is for
my laptop and does not apply to this bug report. Using ubuntu-bug, I'm
not sure how to control this. Using the debian bug tool, I would have
just edited the file
If you attempt to launch an ec2
I know it works on c4 and m4 instance types. Those are the only other
ones I've tried. To test this kernel on r3, I'd probably have to launch
an instance on m4, upgrade the kernel from above, create a new AMI, and
try running that on r3. I'm in major crunch right now, so I can't stop
what I'm
Yes, I am able to boot an r3.large instance using this kernel, and I see
the correct number of CPUs. My procedure, in case anyone else wants to
reproduce it, was to boot up from the latest test AMI (ami-c1cb23ac),
sudo dpkg -i ./linux-headers-4.4.0-21* linux-image-* as downloaded from
your link,
I will test it and post results here.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1582776
Title:
HVM/SSD Xenial AWS AMI doesn't launch on r3.large
To manage notifications about this bug go to:
I'll have to study it. Sorry, I have been quite starved for time to work
on qpdf. I would like to fix this, but I can't commit to a timeframe.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1564249
The latest version of qpdf in github is able to process the attached
file now. When 7.0.0 is released later this summer, it should be able to
handle this file and many with similar errors. Thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Public bug reported:
If possible, please sync qpdf 7.1.0-1 from debian unstable for Ubuntu
8.04. This is binary compatible with 7.0.0, which is currently in
Ubuntu. I thought this happened automatically, so forgive me if this
report is superfluous. qpdf 7.1.0 has been in debian unstable for a
qpdf 8.0.2 is released, on github and sourceforge, and uploaded to
debian unstable. It should be visible momentarily.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1753621
Title:
FeatureFreeze
Acknowledged. I will try to get 8.0.2 out today and will update this
ticket when uploaded.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1753621
Title:
FeatureFreeze exception
To manage
As far as I know, 8.0.0 contains everything Sahil and Pranjal need. I
have finalized 8.0.2 and am building the releases now. It takes over an
hour because of that other OS that some people run. I should have 8.0.2
in debian within a few hours.
--
You received this bug notification because you
Public bug reported:
I am requesting an exception to the FeatureFreeze for Ubuntu 18.04 LTS.
I would like qpdf 8.0.1 to be synced from debian.
I am the upstream author of qpdf and the debian maintainer. I released
8.0.0 with the explicit goal of beating the 18.04 feature freeze. It was
released
I think this bug can be closed now, right?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1564249
Title:
Cannot print a PDF with AcroForms using fit-to-page
To manage notifications about this bug
Public bug reported:
10.3.1 includes a very small but important fix to a bug that would cause
qpdf 10.3.0 to reject certain valid files when splitting pages. I also
added a check for exceptions that will make future bugs of this type (if
any) just generate warnings instead of blocking the whole
Makes sense. Hopefully ubuntu is looking either at only the supported
architectures or only the ones that it uses itself. In the former case,
looks like everything's built but mips64el which appears to be building
now, so hopefully it's not much longer. If I'm lucky, 10.2.0 and 10.3.0
won't make
Thanks. I don't know if there's a way for me to know when your utility
can find it. I wait until I get the email from debian that the package
has been accepted before posting this, but apparently that's not quite
enough. Eventually debian will release, Ubuntu will release, and
automatic syncs will
This is a bug-fix release. It contains only two changes: correction of a
very old bug (from 2.3.0 released in 2011) involving references to
replaced objects and a more significant series of fixes to the form
field enhancements in 10.2.0, which turned out to be incorrect and were
creating PDF files
I just uploaded it. I can ask again in a couple of days. I'll put a
reminder for tomorrow to check status.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1916658
Title:
please sync qpdf 10.2.0-1
Great, thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1916658
Title:
please sync qpdf 10.2.0-1 from debian experimental
To manage notifications about this bug go to:
Public bug reported:
Since debian is in freeze, I uploaded qpdf-10.2.0-1 to experimental. I
know unstable syncs automatically to Ubuntu, but I'm not sure I have to
request a sync from experimental or if this is the way to do it. In any
case, it would be great if we can pull qpdf-10.2.0-1 from
Public bug reported:
Sorry to do this again so soon, but I released qpdf 10.3.0 and uploaded
to debian experimental. I have gotten the email from debian indicating
that the package has been accepted, and it is visible on qa.debian.org,
so hopefully it's "there" for purposes of doing the sync. If
Public bug reported:
I'm noticing that qpdf-10.6.1 is not syncing from Debian even though, as
far as I can see, automatic sync freeze has not yet happened. There are
some major changes in 10.6 that I would really like to get into Ubuntu
because they include transitional code to help users migrate
There will definitely be a 10.6.2 in the next day or two.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960924
Title:
qpdf 10.6.1 not syncing?
To manage notifications about this bug go to:
Public bug reported:
qpdf 10.6.3 is in debian unstable with no blockers other than age. It is
a bug-fix only release. The two code-facing changes are fix to allow
correct handling of PDF 2.0 native UTF-8 strings and a fix to appearance
stream generation when "0 Tf" appears in "/DA".
** Affects:
All regressions have been resolved now, and it seems to me like it's
going to automatically migrate, but I'm not sure whether we missed the
window to do so without a freeze exception. As far as I can see, the
freeze date was February 19. I think the pikepdf upload that resolved
the (false)
It helps. Thanks. I just released 10.6.2, and pikepdf 5.0 is also being
released hopefully today to get the two back in sync. Hopefully no
further manual action will be required.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thanks for the clarification. What is the last date for uploading 10.6.3
before final freeze? There is one small bug fix on main for appearance
stream generation that I might want to release, but I'll wait and see if
anything else shows up.
--
You received this bug notification because you are a
Public bug reported:
If needed, I can provide more exact steps to reproduce this, but
hopefully this will be sufficient. Note that follow identical steps with
Ubuntu 20.04 results in a working configuration.
Launch an ec2 instance using the latest version of the Ubuntu AMI as
returned by this
97 matches
Mail list logo
