(Sorry for the duplicate -- I inadvertently failed to cc the bug report on my
private reply.)
On Sun, Apr 14, 2024, at 1:50 PM, Thorsten Glaser wrote:
> Jay Berkenbilt dixit:
>
> >As it happens, I am upstream.
>
> Oh, nice ☻ in that case, thanks for qpdf.
>
> >
n Sun, Apr 7, 2024, at 5:04 AM, Thorsten Glaser wrote:
> Jay Berkenbilt dixit:
>
> >Can you tell me where in the docs it says what you're describing?
> >Here's a direct quote from the current qpdf documentation:
> >
> >It is not generally practical to remove
Can you tell me where in the docs it says what you're describing?
Here's a direct quote from the current qpdf documentation:
It is not generally practical to remove objects from QDF files without
messing up object numbering, but if you remove all references to an
object, you can run qpdf on the fi
11.9.0-1
uploaded right away since I'd like it to sync to Ubuntu before the
24.04 feature freeze.
I'm sending this to the qpdf NMU debdiff bug and to the bug
referenced in that issue. Thanks.
--Jay Berkenbilt , qpdf maintainer
I'll reply to this instead of starting
over.
> On Tue, 2023-10-17 at 07:32 -0400, Jay Berkenbilt wrote:
> > The attached patch to qpdf 11.3.0 fixes a bug that could potentially
> > result in loss of data. I'd like permission from the release team to
> > . . .
> >
Package: qpdf
Version: 11.3.0-1
Severity: important
Tags: upstream
X-Debbugs-Cc: q...@debian.org
Note: I am the upstream author and debian maintainer for qpdf.
Upstream bug https://github.com/qpdf/qpdf/issues/1050 revealed a bug
in qpdf's lexical layer that would cause qpdf to discard the charact
would be hard
to detect.
Please let me know if I should proceed with an update to stable.
--Jay Berkenbilt (a.k.a. q...@debian.org)--- libqpdf/QPDFTokenizer.cc.orig 2023-10-17 07:19:31.829119946 -0400
+++ libqpdf/QPDFTokenizer.cc 2023-10-17 07:20:55.689510562 -0400
@@ -739,17 +739,22 @@
Package: pikepdf
Version: 5.0.0+dfsg-1
X-Debbugs-CC: q...@debian.org
Still getting errors here:
https://ci.debian.net/data/autopkgtest/testing/amd64/p/pikepdf/19355172/log.gz
apparently because of tomli not being found. Is this a pikepdf
packaging issue or something about how the test is being run
I have released qpdf 10.6.2, and a new pikepdf should be coming out imminently
as well. This gets us back in sync -- the new pikepdf tests pass against 10.6.2.
Package: pikepdf
Version: 4.2.0+dfsg-1
X-Debbugs-CC: q...@debian.org
The current version of pikepdf has some failed tests that are preventing qpdf
10.6.1 from transitioning. I just wanted to make you aware of this upstream bug
report: https://github.com/pikepdf/pikepdf/issues/303
Short version:
On Fri, Jan 21, 2022, at 5:13 PM, 積丹尼 Dan Jacobson wrote:
> Package: qpdf
> Version: 10.5.0-1
> Severity: wishlist
>
> Add a qpdf-doc package, so the documentation can be viewed offline,
> without needing to obtain an Internet connection, once one realizes the
> full documentation is missing.
Thi
packaged for debian is 1.17.3. I think pikepdf should be removed from
debian or upgraded. It's not really fair for such an old version of pikepdf to
be blocking the transition of qpdf anymore. Please let me know if there's
anything I can do to help the situation.
--Jay Berkenbilt
Here's an additional patch. This time I tested it against the actual debian
source package. Just drop this into debian/patches and append to
debian/patches/series, and you should be good to go. Thanks. As an added bonus,
I also verified that this is clean with what will soon be qpdf 10.2.
commit
Package: pikepdf
Version: 1.17.3+dfsg-3
X-Debbugs-CC: q...@debian.org
Please see
https://ci.debian.net/data/autopkgtest/testing/amd64/p/pikepdf/10125896/log.gz
If needed, I can try to prepare a patch, but I think my previous patch already
included the fix for this issue. Please let me know if y
On Tue, Jan 19, 2021, at 4:06 PM, Sean Whitton wrote:
> control: tag -1 + patch pending
>
> Hello,
>
> On Tue 19 Jan 2021 at 09:39AM -05, Jay Berkenbilt wrote:
>
> > Here's a patch that applies cleanly against upstream v1.17.3 after
> > which the resulting
tags 980426 +patch
thanks
Here's a patch that applies cleanly against upstream v1.17.3 after which the
resulting pikepdf builds and passes its test with qpdf 10.1. Please let me know
if this is sufficient. I put some comments at the top of the patch citing
original commits in case you want to d
(pardon the duplicate -- I accidentally did reply to sender instead of reply
all)
On Mon, Jan 18, 2021, at 7:55 PM, Sean Whitton wrote:
> Dear Jay,
>
> On Mon 18 Jan 2021 at 05:35PM -05, Jay Berkenbilt wrote:
>
> > Package: pikepdf
> > Version: 1.17.3+dfsg-2
> >
Package: pikepdf
Version: 1.17.3+dfsg-2
X-Debbugs-CC: q...@debian.org
This is a request to please upload the latest pikepdf to sid. Right now, qpdf
10.1.0 is not able to transition to testing because autopkgtest is failing
because of a regression in pikepdf. The problem is actually in pikepdf, a
The @ syntax doesn't work in the middle of an argument. You can put
--password=something
in a file and use @file in place of the whole argument, or you can use @- and
type
--password=something
I'll admit that it's a bit confusingly worded. I will clarify the documentation
about this and see i
Oops, I fixed this, but I made a cut and paste error and "Closed" the wrong bug
number in the changelog. I wlll clean it up tomorrow by removing the fixed
version from the wrong bug and adding it to the right one.
On Fri, Apr 10, 2020, at 1:39 PM, Debian Bug Tracking System wrote:
> Processing c
I've fixed it in my local repository, so the bug will close the next time I
upload. Thanks.
On Tue, Jul 30, 2019 at 7:27 AM Vincent Lefevre wrote:
> Package: qpdf
> Version: 8.4.2-1
> Severity: normal
>
> In the /usr/share/doc/qpdf/copyright file:
>
> It was downloaded from http://github.com/q
On Mon, May 27, 2019 at 4:14 PM Paul Gevers wrote:
> Control: tags -1 moreinfo
>
> On Sun, 19 May 2019 20:43:29 -0400 Jay Berkenbilt wrote:
> > The changes between qpdf 8.4.0 and 8.4.2 are bug fixes, but I am
> > asking for consideration because this update includes f
Definitely a bug. I have no idea why I did that. Probably a cut and paste
error when I first create the package years ago. I will fix and upload a
new version. Thanks for the report.
On Fri, Feb 8, 2019 at 7:39 AM Laurent Bigonville wrote:
> Source: qpdf
> Version: 8.4.0-1
> Severity: normal
>
>
plement your suggestion?
>
> [2008-06-11 18:35] Petter Reinholdtsen
> >
> > part text/plain 448
> > [Jay Berkenbilt]
> > > A quick perusal of the code suggests that it should be a pretty
> > > localized change.
> >
> > I w
This will be fixed with upstream release 8.2.0. Thanks for taking the time
to report this and for proiving a patch.
On Thu, Jun 28, 2018 at 8:15 PM Bjarni Ingi Gislason
wrote:
> Package: qpdf
> Version: 8.1.0-1
> Severity: minor
> Tags: patch
>
> Input file is qpdf.1
>
> Add a period in front of
Thanks for making me aware of this. I didn't know about pikepdf. That's
really exciting -- I've always wanted to be able to use qpdf from Python. I
will contact pikepdf's author.
On Thu, Jul 12, 2018 at 3:18 AM Sean Whitton
wrote:
> Package: wnpp
> Severity: wishlist
> Owner: Sean Whitton
>
> *
ng to apply them.
I will tag these bugs as fixed when I package 7.0.0 for debian, but they
will remain applicable to older versions.
--
Jay Berkenbilt
x27;t even
have any test cases for it. Anyway, it's fixed now in master and will be
in the next release. Sorry for taking sooo long to get to it.
--
Jay Berkenbilt
reopen 825246 https://github.com/qpdf/qpdf/issues/129
upstream 825246 https://github.com/qpdf/qpdf/issues
thanks
On 08/01/2017 10:43 AM, 積丹尼 Dan Jacobson wrote:
> B> I've never been able to reproduce this problem.
> What do you see when you type
> qpdf --empty out.pdf --pages *.pdf --
> ?
>
Oh, a
Upstream has accepted the fbpanel genmon pango patch. It'd be kinda nice
if the patch made it into the debian version so that debian and probably
Ubuntu 16.04 LTS would have it, but if not, the next upstream version
will have it.
--
Jay Berkenbilt
case letters in green.
I'm not sure whether upstream is actually going to release 7.0 or
whether it will include my patch. I just keep patching fbpanel and using
a patched version. I don't run a graphical desktop on that many systems,
so this is not a huge deal for me
--
Jay Berkenbilt
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
The latest version of qpdf includes an soname bump. The qpdf
transition is very small. The only other source package with a
dependency on libqpdf is cups-filters. qpdf 6.0.0 with libqpdf1
Package: qpdf
Version: 5.2.0-1
Severity: grave
Tags: upstream
Justification: causes non-serious data loss
qpdf 5.2.0 breaks ABI compatibility. I am releasing qpdf 6.0.0 and am
uploading a new version of 5.2.0 that reverts the ABI change.
n and little-endian
systems. I believe all three architectures you listed are little-endian.
You could check ppc and see if platform.h differs there. The patch was
done when ICU 4.8 was current. It's conceivable that it's no longer
required, or as you say, it's also possible that t
"László Böszörményi (GCS)" wrote:
> Hi Jay,
>
> On Thu, Aug 6, 2015 at 5:26 PM, Jay Berkenbilt wrote:
>> I hope that the new maintainer will see if the new upstream version of
>> vips includes a soname bump and, if so, will just upload that.
> As you know,
I hope that the new maintainer will see if the new upstream version of
vips includes a soname bump and, if so, will just upload that. That's
what I would do if I were still maintaining this.
--
Jay Berkenbilt
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
w
I uploaded a version that renames libqpdf13 to libqpdf13v5 since qpdf is
affected and has no dependencies that are effected. Its only reverse
dependency in the archive that is affected is cups-filters.
--
Jay Berkenbilt
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
rg/cgi-bin/bugreport.cgi?bug=764276 for
additional discussion.
--
Jay Berkenbilt
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Package: vips
Version: 7.42.1-1
Severity: normal
See https://github.com/lovell/sharp/pull/173#issuecomment-76177598
Github user lovell says: "I think libgsf-1-dev should be added as a
mandatory dependency of lipvips-dev given libgsf-1-114 is a mandatory
dependency of libvips38."
--
To UNSUBSCR
l go through. Thanks for taking care of it.
I can do a quick review if desired, but I would only be reviewing
mechanics, not correctness of the patches, as I haven't and won't have
time to look into the details of the problems or their solutions.
--
Jay Berkenbilt
--
To UNSUBSCRI
urity supported version, which is one of the
main challenges of maintaining icu.
--
Jay Berkenbilt
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
I am not going to be able to handle the ICU transition and am looking
for a new maintainer for ICU (an RFA is open). Whoever takes over ICU
will have to manage the transition to whatever version of ICU is current
at the time, and it will have to be handled after jessie is released.
--
To UNSUBSC
Package: wnpp
Severity: normal
I request an adopter for the psutils package since I no longer have
time to maintain it.
The package description is:
This collection of utilities is for manipulating PostScript
documents. Page selection and rearrangement are supported, including
arrangement int
Package: wnpp
Severity: normal
I request an adopter for the xerces-c package since I no longer have
time to maintain it.
The package description is:
Xerces-C++ is a validating XML parser written in a portable subset of
C++. This package contains the development files for Xerces. It also
cont
Package: wnpp
Severity: normal
I request an adopter for the tiff package since I no longer have time to
maintain it properly.
The package description is:
libtiff is a library providing support for the Tag Image File Format
(TIFF), a widely used format for storing image data. This package
cont
Package: wnpp
Severity: normal
I request an adopter for the icu package as I no longer have time to
maintain the package.
The package description is:
ICU is a C++ and C library that provides robust and full-featured
Unicode and locale support. This package contains programs used to
manipulate
7:22.0 -0400
+++ icu-52.1/debian/changelog 2015-01-21 21:47:39.0 -0500
@@ -1,3 +1,10 @@
+icu (52.1-7) unstable; urgency=high
+
+ * Patch to CVE-2014-6591, CVE-2014-6585 a font parsing bug.
+(Closes: #775884)
+
+ -- Jay Berkenbilt Wed, 21 Jan 2015 21:33:19 -0500
+
icu (52.1-6) unst
high
(though I believe urgency is ignored right now) and will request a
freeze exception justified by this fixing a security bug. Please advise
as to whether this should be fixed in stable. I'm not sure how urgent it
is given that a formal CVE has not yet been issued (right?) and that
this is clas
n bmp2tiff. CVE-2014-9330. (Closes: #773987)
+
+ -- Jay Berkenbilt Tue, 30 Dec 2014 11:32:04 -0500
+
tiff (4.0.3-11) unstable; urgency=medium
* Don't crash on JPEG => non-JPEG conversion (Closes: #741451)
diff -Nru tiff-4.0.3/debian/patches/CVE-2014-9330.patch tiff-4.0.3/debian/patches/
ff-4.0.3/debian/changelog 2014-06-29 17:32:44.0 -0400
+++ tiff-4.0.3/debian/changelog 2014-12-23 15:52:13.0 -0500
@@ -1,3 +1,10 @@
+tiff (4.0.3-11) unstable; urgency=medium
+
+ * Don't crash on JPEG => non-JPEG conversion (Closes: #741451)
+ * Thanks Tomasz Buchert
f
it. Your good efforts made my job trivial. Thanks!
I have also submitted an unblock request to the release team.
--
Jay Berkenbilt
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
efore I
was a DD, I participated in the maintenance of team-maintained package
and got sponsorship sometimes from the team and sometimes from outside
the team. It shouldn't really make a difference.
--
Jay Berkenbilt
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debi
/Content in the page dictionary,
enabling printing of files with blank pages as produced by some
software. (Closes: #769599)
-- Jay Berkenbilt Fri, 14 Nov 2014 21:07:25 -0500
--
unblock qpdf/5.1.2-2
-- System Information:
Debian Release: jessie/sid
APT prefers unstable
APT
Package: qpdf
Version: 5.1.2-1
Severity: important
qpdf, which is used in cups-filters for printing, throws an exception
when asked to provide the contents of a page that has no /Contents
entry in its page dictionary. The result of this is that users are not
able to print PDF files with blank page
Jay Berkenbilt wrote:
> Mathieu Malaterre wrote:
>
>> On Tue, Oct 28, 2014 at 7:13 PM, Tomasz Buchert
>> wrote:
>>> Hi,
>>> I've worked on that bug today's evening and I found
>>> a fairly simple fix.
>>
>> Thanks Toma
ve done is to create an upstream bug report with this. If it's
excepted, then I will mark this patch to include in my first post-Jessie
upload. There's a chance upstream will issue a new version before then
anyway, and we will want this fix to go in.
Here's the upstream bug report:
ht
g this in the amount of time I have, but if he
or you comes up with a good patch, I will certainly be happy to apply it
to the debian package.
--
Jay Berkenbilt
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
The ICU bug that contributed to this was fixed in the most recent upload.
--
Jay Berkenbilt
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
includes lots of code generators. Surely, in the general
case,some of the flags passed in at compile time will be needed and
others won't. Hopefully for the debian build I can come up with some way
of doing it cleanly.
--
Jay Berkenbilt
--
To UNSUBSCRIBE, email to debian-bugs-dist-re
d a chance to do
that yet.
--
Jay Berkenbilt
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
ther he could get confirmation that it would
be free to distribute. If the above looks okay from a copyright
standpoint, it could be a replacement.
--
Jay Berkenbilt
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
aining a non-distributable file.
I'll take care of this part after I have a replacement.
--
Jay Berkenbilt
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
ICU version 53 is out, and this is the latest version of ICU that will
be available before the freeze for Jesse, so this will be the only
remaining ICU transition the Jesse freeze.. (ICU
im. In any case, if this is no longer reproducible, I guess we
can close the bug.
--
Jay Berkenbilt
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
l fix it all up shortly
Yup, just replacing the build dependency with libtiff-dev was the
original suggestion and what almost everyone did with their packages. We
all have bad dreams sometimes. :-)
--
Jay Berkenbilt
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with
ant to keep a transitional package around, and
removing it has always been part of the plan. I'm sorry that this is
causing a hassle for you. I tried to organize this to minimize hassle
and to provide loads of time for developers to make the switch.
Let me know if I can be of any assista
the remaining 24 open
bugs and see if others are like that as well. Thanks.
--
Jay Berkenbilt
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
dependency from
libtiff4-dev to libtiff5-dev, but this is unlikely since libtiff5-dev
has only existed for a short time, and it is more likely that you can
just remove the version number.
--
Jay Berkenbilt
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of
dependency from
libtiff4-dev to libtiff5-dev, but this is unlikely since libtiff5-dev
has only existed for a short time, and it is more likely that you can
just remove the version number.
--
Jay Berkenbilt
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of
dependency from
libtiff4-dev to libtiff5-dev, but this is unlikely since libtiff5-dev
has only existed for a short time, and it is more likely that you can
just remove the version number.
--
Jay Berkenbilt
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of
dependency from
libtiff4-dev to libtiff5-dev, but this is unlikely since libtiff5-dev
has only existed for a short time, and it is more likely that you can
just remove the version number.
--
Jay Berkenbilt
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of
dependency from
libtiff4-dev to libtiff5-dev, but this is unlikely since libtiff5-dev
has only existed for a short time, and it is more likely that you can
just remove the version number.
--
Jay Berkenbilt
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of
dependency from
libtiff4-dev to libtiff5-dev, but this is unlikely since libtiff5-dev
has only existed for a short time, and it is more likely that you can
just remove the version number.
--
Jay Berkenbilt
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of
dependency from
libtiff4-dev to libtiff5-dev, but this is unlikely since libtiff5-dev
has only existed for a short time, and it is more likely that you can
just remove the version number.
--
Jay Berkenbilt
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of
dependency from
libtiff4-dev to libtiff5-dev, but this is unlikely since libtiff5-dev
has only existed for a short time, and it is more likely that you can
just remove the version number.
--
Jay Berkenbilt
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of
dependency from
libtiff4-dev to libtiff5-dev, but this is unlikely since libtiff5-dev
has only existed for a short time, and it is more likely that you can
just remove the version number.
--
Jay Berkenbilt
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of
dependency from
libtiff4-dev to libtiff5-dev, but this is unlikely since libtiff5-dev
has only existed for a short time, and it is more likely that you can
just remove the version number.
--
Jay Berkenbilt
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of
dependency from
libtiff4-dev to libtiff5-dev, but this is unlikely since libtiff5-dev
has only existed for a short time, and it is more likely that you can
just remove the version number.
--
Jay Berkenbilt
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of
dependency from
libtiff4-dev to libtiff5-dev, but this is unlikely since libtiff5-dev
has only existed for a short time, and it is more likely that you can
just remove the version number.
--
Jay Berkenbilt
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of
dependency from
libtiff4-dev to libtiff5-dev, but this is unlikely since libtiff5-dev
has only existed for a short time, and it is more likely that you can
just remove the version number.
--
Jay Berkenbilt
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of
dependency from
libtiff4-dev to libtiff5-dev, but this is unlikely since libtiff5-dev
has only existed for a short time, and it is more likely that you can
just remove the version number.
--
Jay Berkenbilt
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of
dependency from
libtiff4-dev to libtiff5-dev, but this is unlikely since libtiff5-dev
has only existed for a short time, and it is more likely that you can
just remove the version number.
--
Jay Berkenbilt
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of
dependency from
libtiff4-dev to libtiff5-dev, but this is unlikely since libtiff5-dev
has only existed for a short time, and it is more likely that you can
just remove the version number.
--
Jay Berkenbilt
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of
dependency from
libtiff4-dev to libtiff5-dev, but this is unlikely since libtiff5-dev
has only existed for a short time, and it is more likely that you can
just remove the version number.
--
Jay Berkenbilt
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of
dependency from
libtiff4-dev to libtiff5-dev, but this is unlikely since libtiff5-dev
has only existed for a short time, and it is more likely that you can
just remove the version number.
--
Jay Berkenbilt
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of
dependency from
libtiff4-dev to libtiff5-dev, but this is unlikely since libtiff5-dev
has only existed for a short time, and it is more likely that you can
just remove the version number.
--
Jay Berkenbilt
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of
dependency from
libtiff4-dev to libtiff5-dev, but this is unlikely since libtiff5-dev
has only existed for a short time, and it is more likely that you can
just remove the version number.
--
Jay Berkenbilt
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of
dependency from
libtiff4-dev to libtiff5-dev, but this is unlikely since libtiff5-dev
has only existed for a short time, and it is more likely that you can
just remove the version number.
--
Jay Berkenbilt
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of
dependency from
libtiff4-dev to libtiff5-dev, but this is unlikely since libtiff5-dev
has only existed for a short time, and it is more likely that you can
just remove the version number.
--
Jay Berkenbilt
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of
dependency from
libtiff4-dev to libtiff5-dev, but this is unlikely since libtiff5-dev
has only existed for a short time, and it is more likely that you can
just remove the version number.
--
Jay Berkenbilt
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of
dependency from
libtiff4-dev to libtiff5-dev, but this is unlikely since libtiff5-dev
has only existed for a short time, and it is more likely that you can
just remove the version number.
--
Jay Berkenbilt
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of
dependency from
libtiff4-dev to libtiff5-dev, but this is unlikely since libtiff5-dev
has only existed for a short time, and it is more likely that you can
just remove the version number.
--
Jay Berkenbilt
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of
dependency from
libtiff4-dev to libtiff5-dev, but this is unlikely since libtiff5-dev
has only existed for a short time, and it is more likely that you can
just remove the version number.
--
Jay Berkenbilt
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of
dependency from
libtiff4-dev to libtiff5-dev, but this is unlikely since libtiff5-dev
has only existed for a short time, and it is more likely that you can
just remove the version number.
--
Jay Berkenbilt
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of
dependency from
libtiff4-dev to libtiff5-dev, but this is unlikely since libtiff5-dev
has only existed for a short time, and it is more likely that you can
just remove the version number.
--
Jay Berkenbilt
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of
27;s security support was over, but I wasn't sure
who/what had responsibility for the long-term support for squeeze. I
remember the announcement about LTS but hadn't realized/remembered that
there was a separate upload path. I found the information about how to
do it. Thanks!
--
Jay Berkenb
Michael Gilbert wrote:
> On Sat, Jun 21, 2014 at 6:32 PM, Jay Berkenbilt wrote:
>> I've finally had a chance to deal with this. The patch applies cleanly
>> with offsets to the versions in squeeze, wheezy, and sid, so I've
>> prepared packages for all three d
applies cleanly
with offsets to the versions in squeeze, wheezy, and sid, so I've
prepared packages for all three distributions. I'm attaching the debdiff
files here. Please let me know if I should proceed to upload.
For sid, this will be fixed in 4.0.3-9. I realize there is no DSA.
--
Just for the record, I think the problem fixed here actually doesn't
have anything to do with gcc 4.9. ICU was probably FTBFS for all
versions. There was a time-based test that started failing between the
last time we built and when the gcc 4.9 build was attempted. I didn't
verify that the problem
The version of ICU I'm about to upload builds and tests fine for me
locally with the latest gcc-4.9 package from sid. Hopefully this solves
the problem. There was a failing test case, and I found a fix for it
from upstream.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
wi
1 - 100 of 678 matches
Mail list logo
