Bug#780170: Please, update compatibility.js symlink

2015-05-13 Thread Johannes Schauer
Hi David,

Quoting David Prévot (2015-05-13 18:13:26)
 It is now in testing. I’m in the process of updating pdf.js to 1.1.114
 now, it will drop the compatibility symlink pdf2htmlex is currently
 depending on. It will break pdf2htmlex ( 0.13.6+ds-2~), so:
 - pdf2htmlex will be uninstallable in Sid, thus the RC-severity bump
 - pdf2htmlex will still be installable in Stretch, and the break will
   prevent the new pdf.js version to migrate into testing (until
   pdf2htmlex 0.13.6+ds-2 or higher migrates, or gets removed because of
   the RC bug).
 
   I will make the change once pdf.js-common (= 1.0.1149) appears in 
   unstable.
 
 No pressure from me (I don’t mind if the new pdf.js doesn’t migrate into
 Stretch soon), but if you have any objection to the proposed plan, now
 is the time to say so (before I upload the new pdf.js ;).

thanks for your work!

I have just uploaded pdf2htmlex 0.13.6+ds-2 which uses
/usr/share/pdf.js/compatibility.js from pdf.js-common directly.

cheers, josch


signature.asc
Description: signature


Bug#780170: Please, update compatibility.js symlink

2015-05-13 Thread David Prévot
Control: severity -1 serious

Hi Johannes,

On Sat, May 02, 2015 at 06:14:28PM -0400, David Prévot wrote:
 On Sat, May 02, 2015 at 11:16:33PM +0200, Johannes Schauer wrote:
  Quoting Johannes Schauer (2015-03-18 21:13:51)
   Quoting David Prévot (2015-03-18 21:05:11)
Even better: you may use directly /usr/share/pdf.js/compatibility.js as
shipped in pdf.js-common (= 1.0.1149) instead of depending on 
libjs-pdf.
   
   I'll make the change as soon as Jessie is released :)
  
  I just uploaded the new pdf2htmlex upstream version to unstable but did not
  include the symlink change because pdf.js-common (= 1.0.1149) seems to 
  still
  be in experimental only.
 
 I’ve uploaded 1.1.1+dfsg-2 to Sid now.

It is now in testing. I’m in the process of updating pdf.js to 1.1.114
now, it will drop the compatibility symlink pdf2htmlex is currently
depending on. It will break pdf2htmlex ( 0.13.6+ds-2~), so:
- pdf2htmlex will be uninstallable in Sid, thus the RC-severity bump
- pdf2htmlex will still be installable in Stretch, and the break will
  prevent the new pdf.js version to migrate into testing (until
  pdf2htmlex 0.13.6+ds-2 or higher migrates, or gets removed because of
  the RC bug).

  I will make the change once pdf.js-common (= 1.0.1149) appears in unstable.

No pressure from me (I don’t mind if the new pdf.js doesn’t migrate into
Stretch soon), but if you have any objection to the proposed plan, now
is the time to say so (before I upload the new pdf.js ;).

Regards

David


signature.asc
Description: Digital signature


Bug#780170: Please, update compatibility.js symlink

2015-05-02 Thread David Prévot
Hi Johannes,

On Sat, May 02, 2015 at 11:16:33PM +0200, Johannes Schauer wrote:
 Quoting Johannes Schauer (2015-03-18 21:13:51)
  Quoting David Prévot (2015-03-18 21:05:11)
   Even better: you may use directly /usr/share/pdf.js/compatibility.js as
   shipped in pdf.js-common (= 1.0.1149) instead of depending on libjs-pdf.
  
  I'll make the change as soon as Jessie is released :)
 
 I just uploaded the new pdf2htmlex upstream version to unstable but did not
 include the symlink change because pdf.js-common (= 1.0.1149) seems to still
 be in experimental only.

I’ve uploaded 1.1.1+dfsg-2 to Sid now.

 I will make the change once pdf.js-common (= 1.0.1149) appears in unstable.

That should happen in a few minutes ;).

 What is the advantage/reason of depending on compatibility.js in pdf.js-common
 instead of the one in libjs-pdf?

pdf.js-common just ship the common files shared by libjs-pdf and
xul-ext-pdf.js (and soon, pdf2htmlex too). libjs-pdf only ships a
symlink to the actual file (well, two actually, but I’ll get rid of the
extra one once this bug is fixed ;).

Since libjs-pdf is about as big as pdf.js-common (and depend on it),
using pdf.js-common directly will save (your users) one package, almost
1MB to download, and almost 3MB on disk for each installation.

Symlinking to a symlink (that is already symlinking to a symlink) may
not be the most effective thing anyway.

Regards

David


signature.asc
Description: Digital signature


Bug#780170: Please, update compatibility.js symlink

2015-05-02 Thread Johannes Schauer
Hi,

Quoting Johannes Schauer (2015-03-18 21:13:51)
 Quoting David Prévot (2015-03-18 21:05:11)
  Even better: you may use directly /usr/share/pdf.js/compatibility.js as
  shipped in pdf.js-common (= 1.0.1149) instead of depending on libjs-pdf.
 
 thanks a lot for your bug report!
 
 I'll make the change as soon as Jessie is released :)

I just uploaded the new pdf2htmlex upstream version to unstable but did not
include the symlink change because pdf.js-common (= 1.0.1149) seems to still
be in experimental only.

I will make the change once pdf.js-common (= 1.0.1149) appears in unstable.

What is the advantage/reason of depending on compatibility.js in pdf.js-common
instead of the one in libjs-pdf?

cheers, josch


signature.asc
Description: signature


Bug#780170: Please, update compatibility.js symlink

2015-03-18 Thread Johannes Schauer
Hi David,

Quoting David Prévot (2015-03-18 21:05:11)
  I’d like to get rid of the compatibility symlinks introduced in pdf.js
  1.0.21+dfsg-1, and thus encourage you to change the
  /usr/share/pdf2htmlEX/compatibility.js symlink so it points to
  /usr/share/javascript/pdf/web/compatibility.js
 
 Even better: you may use directly /usr/share/pdf.js/compatibility.js as
 shipped in pdf.js-common (= 1.0.1149) instead of depending on
 libjs-pdf.

thanks a lot for your bug report!

I'll make the change as soon as Jessie is released :)

cheers, josch


signature.asc
Description: signature


Bug#780170: Please, update compatibility.js symlink

2015-03-18 Thread David Prévot
Control: affects -1 libjs-pdf

Hi Johannes,

On Mon, Mar 09, 2015 at 09:36:42PM -0400, David Prévot wrote:
 Package: pdf2htmlex

 I’d like to get rid of the compatibility symlinks introduced in pdf.js
 1.0.21+dfsg-1, and thus encourage you to change the
 /usr/share/pdf2htmlEX/compatibility.js symlink so it points to
 /usr/share/javascript/pdf/web/compatibility.js

Even better: you may use directly /usr/share/pdf.js/compatibility.js as
shipped in pdf.js-common (= 1.0.1149) instead of depending on
libjs-pdf.

 You may use a simple debian/links file containing the following line and
 drop the current override_dh_auto_install from debian/rules:

/usr/share/pdf.js/compatibility.js usr/share/pdf2htmlEX/compatibility.js

Regards

David


signature.asc
Description: Digital signature


Bug#780170: Please, update compatibility.js symlink

2015-03-09 Thread David Prévot
Package: pdf2htmlex
Version: 0.12+ds-1
Severity: wishlist

Hi Johannes,

I’d like to get rid of the compatibility symlinks introduced in pdf.js
1.0.21+dfsg-1, and thus encourage you to change the
/usr/share/pdf2htmlEX/compatibility.js symlink so it points to
/usr/share/javascript/pdf/web/compatibility.js instead of
/usr/share/javascript/pdf/compatibility.js as it currently does.

You may use a simple debian/links file containing the following line and
drop the current override_dh_auto_install from debian/rules:

usr/share/javascript/pdf/web/compatibility.js   
usr/share/pdf2htmlEX/compatibility.js

Thanks in advance

Regards

David


signature.asc
Description: Digital signature