Bug#871502: zotero-standalone-build: The newer Zotero is standalone only ; a reorganization is neded.
Le vendredi 05 octobre 2018 à 12:55 +0200, Félix Sipma a écrit : > On 2018-10-02 05:50+, Trout, Diane E. wrote: > > I was at least going to try and commit the work I did and stick on > > salsa, but I've been busy the past couple of days. I'll try to get it > > done in by the weekend. > > > > There's some javascript packages that are needed, that aren't packaged. > > > > What I had so far can only build outside of a chroot when npm can > > download packages. > > > > Would anyone be willing to help package some javascript dependencies? > > > > If my d/control file is right Debian is missing these: > > > > # node-babel-plugin-transform-es2015-modules-commonjs, > > # node-browserify, > > # node-chai, > > # node-chai-as-promised, > > # node-co-mocha, > > # node-eslint-plugin-react, > > # node-mocha, > > # node-node-sass, > > I'm not sure about the others, but at least for node-browserify, it seems like > a pretty big one. To be honest with myself, I don't think I'll have the time > to > learn how to package javascript packages and do some of the actual work before > the freeze. > > Is the possibility of bundling those dependencies still available? Yes, even though this is not the preferred Debian way, it is possible to do this. > I just tried the flatpak solution proposed, and I have to admit it just worked > great... Same for me. -- ⢀⣴⠾⠻⢶⣦⠀ Sébastien Villemot ⣾⠁⢠⠒⠀⣿⡁ Debian Developer ⢿⡄⠘⠷⠚⠋⠀ http://sebastien.villemot.name ⠈⠳⣄ http://www.debian.org signature.asc Description: This is a digitally signed message part
Bug#871502: zotero-standalone-build: The newer Zotero is standalone only ; a reorganization is neded.
On 2018-10-02 05:50+, Trout, Diane E. wrote: > I was at least going to try and commit the work I did and stick on > salsa, but I've been busy the past couple of days. I'll try to get it > done in by the weekend. > > There's some javascript packages that are needed, that aren't packaged. > > What I had so far can only build outside of a chroot when npm can > download packages. > > Would anyone be willing to help package some javascript dependencies? > > If my d/control file is right Debian is missing these: > > # node-babel-plugin-transform-es2015-modules-commonjs, > # node-browserify, > # node-chai, > # node-chai-as-promised, > # node-co-mocha, > # node-eslint-plugin-react, > # node-mocha, > # node-node-sass, I'm not sure about the others, but at least for node-browserify, it seems like a pretty big one. To be honest with myself, I don't think I'll have the time to learn how to package javascript packages and do some of the actual work before the freeze. Is the possibility of bundling those dependencies still available? I just tried the flatpak solution proposed, and I have to admit it just worked great... signature.asc Description: PGP signature
Bug#871502: zotero-standalone-build: The newer Zotero is standalone only ; a reorganization is neded.
On Sat, 2018-09-29 at 13:01 +0200, Félix Sipma wrote: > Package: src:zotero-standalone-build > Followup-For: Bug #871502 > > So, zotero is starting to be severely broken... Maybe we should > remove it > completely from Debian? > > Diane, you are the last one who tried to update zotero, do you still > have > interest in doing so? I was at least going to try and commit the work I did and stick on salsa, but I've been busy the past couple of days. I'll try to get it done in by the weekend. There's some javascript packages that are needed, that aren't packaged. What I had so far can only build outside of a chroot when npm can download packages. Would anyone be willing to help package some javascript dependencies? If my d/control file is right Debian is missing these: # node-babel-plugin-transform-es2015-modules-commonjs, # node-browserify, # node-chai, # node-chai-as-promised, # node-co-mocha, # node-eslint-plugin-react, # node-mocha, # node-node-sass, signature.asc Description: This is a digitally signed message part
Bug#871502: zotero-standalone-build: The newer Zotero is standalone only ; a reorganization is neded.
Package: src:zotero-standalone-build Followup-For: Bug #871502 So, zotero is starting to be severely broken... Maybe we should remove it completely from Debian? Diane, you are the last one who tried to update zotero, do you still have interest in doing so? Thanks! -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'stable'), (100, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.18.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled signature.asc Description: PGP signature
Bug#871502: zotero-standalone-build: The newer Zotero is standalone only ; a reorganization is neded.
On 2018-01-16 16:47+0100, Sébastien Villemot wrote: > On Tue, Jan 16, 2018 at 04:32:02PM +0100, Félix Sipma wrote: >> On 2018-01-16 12:46+0100, Sébastien Villemot wrote: > >>> Indeed you’re right. The zotero-web-library.js stuff is included in the >>> official Zotero client distribution. So lots of work ahead, I'm not sure >>> I'm up >>> to the task. I think I am going to orphan the package. >> >> I have to admit it did not motivate me either to see such a big work to do... >> Maybe an acceptable possibility would be to put the js libs in the package >> and >> move it in contrib? > > I'm not sure to understand your reasoning. > > Do you mean that the libraries would be downloaded at build time? This has > been > discussed on debian-devel@ recently, and it is clearly not acceptable, even > for > contrib. > > Or do you mean we would bundle the JS libs in the zotero package? If all the > source is there, it can go into "main". Still it's borderline, because library > bundling is bad practice, but maybe it could be acceptable as a temporary > solution. I was thinking of the bundling solution. I think this was also discussed on debian-devel, and the conclusion was that the package had to go in contrib (because which would provide something which is different from the source: concatenated/minified/etc. js). >> More and more js libs get packaged, so when the ones with a lot of >> dependencies >> would have entered Debian, we can try to package the last ones. What do you >> think about this? > > That may be an option, though we have no control of whether this will happen > anytime soon. I know it's far from perfect, but I see no other reasonable solution :(. I don't know exactly how we would prepare the tarball with the bundle of the JS libs. signature.asc Description: PGP signature
Bug#871502: zotero-standalone-build: The newer Zotero is standalone only ; a reorganization is neded.
On Tue, Jan 16, 2018 at 04:32:02PM +0100, Félix Sipma wrote: > On 2018-01-16 12:46+0100, Sébastien Villemot wrote: > > Indeed you’re right. The zotero-web-library.js stuff is included in the > > official Zotero client distribution. So lots of work ahead, I'm not sure > > I'm up > > to the task. I think I am going to orphan the package. > > I have to admit it did not motivate me either to see such a big work to do... > Maybe an acceptable possibility would be to put the js libs in the package and > move it in contrib? I'm not sure to understand your reasoning. Do you mean that the libraries would be downloaded at build time? This has been discussed on debian-devel@ recently, and it is clearly not acceptable, even for contrib. Or do you mean we would bundle the JS libs in the zotero package? If all the source is there, it can go into "main". Still it's borderline, because library bundling is bad practice, but maybe it could be acceptable as a temporary solution. > More and more js libs get packaged, so when the ones with a lot of > dependencies > would have entered Debian, we can try to package the last ones. What do you > think about this? That may be an option, though we have no control of whether this will happen anytime soon. -- ⢀⣴⠾⠻⢶⣦⠀ Sébastien Villemot ⣾⠁⢠⠒⠀⣿⡁ Debian Developer ⢿⡄⠘⠷⠚⠋⠀ http://sebastien.villemot.name ⠈⠳⣄ http://www.debian.org signature.asc Description: PGP signature
Bug#871502: zotero-standalone-build: The newer Zotero is standalone only ; a reorganization is neded.
On 2018-01-16 12:46+0100, Sébastien Villemot wrote: > Control: tags -1 + help > > On Mon, Jan 08, 2018 at 06:48:52PM +0100, Félix Sipma wrote: >> On 2017-11-28 15:58+0100, Sébastien Villemot wrote: >>> Are you sure that this package (node-zotero-web-library), which drags a lot >>> of >>> dependencies not yet in Debian, is really needed for packaging the new >>> release >>> of the Zotero client? Looking at its README.md, this package seems to be >>> related to zotero.org's server side. >> >> Sorry for the long delay... nodejs 8 has just reached sid, so this is not a >> blocker anymore. Concerning node-zotero-web-library (and other >> dependencies), I >> just looked at zotero's package.json. > > Indeed you’re right. The zotero-web-library.js stuff is included in the > official Zotero client distribution. So lots of work ahead, I'm not sure I'm > up > to the task. I think I am going to orphan the package. I have to admit it did not motivate me either to see such a big work to do... Maybe an acceptable possibility would be to put the js libs in the package and move it in contrib? More and more js libs get packaged, so when the ones with a lot of dependencies would have entered Debian, we can try to package the last ones. What do you think about this? signature.asc Description: PGP signature
Bug#871502: zotero-standalone-build: The newer Zotero is standalone only ; a reorganization is neded.
Control: tags -1 + help On Mon, Jan 08, 2018 at 06:48:52PM +0100, Félix Sipma wrote: > On 2017-11-28 15:58+0100, Sébastien Villemot wrote: > > Are you sure that this package (node-zotero-web-library), which drags a lot > > of > > dependencies not yet in Debian, is really needed for packaging the new > > release > > of the Zotero client? Looking at its README.md, this package seems to be > > related to zotero.org's server side. > > Sorry for the long delay... nodejs 8 has just reached sid, so this is not a > blocker anymore. Concerning node-zotero-web-library (and other dependencies), > I > just looked at zotero's package.json. Indeed you’re right. The zotero-web-library.js stuff is included in the official Zotero client distribution. So lots of work ahead, I'm not sure I'm up to the task. I think I am going to orphan the package. -- ⢀⣴⠾⠻⢶⣦⠀ Sébastien Villemot ⣾⠁⢠⠒⠀⣿⡁ Debian Developer ⢿⡄⠘⠷⠚⠋⠀ http://sebastien.villemot.name ⠈⠳⣄ http://www.debian.org signature.asc Description: PGP signature
Bug#871502: Re : Bug#871502: zotero-standalone-build: The newer Zotero is standalone only ; a reorganization is neded.
On 2017-11-28 15:58+0100, Sébastien Villemot wrote: > Are you sure that this package (node-zotero-web-library), which drags a lot of > dependencies not yet in Debian, is really needed for packaging the new release > of the Zotero client? Looking at its README.md, this package seems to be > related to zotero.org's server side. Sorry for the long delay... nodejs 8 has just reached sid, so this is not a blocker anymore. Concerning node-zotero-web-library (and other dependencies), I just looked at zotero's package.json. signature.asc Description: PGP signature
Bug#871502: Re : Bug#871502: zotero-standalone-build: The newer Zotero is standalone only ; a reorganization is neded.
On Fri, Nov 10, 2017 at 12:45:52PM +0100, Félix Sipma wrote: > On 2017-11-07 12:52+0100, Sébastien Villemot wrote: > > On Tue, Nov 07, 2017 at 12:38:36PM +0100, Félix Sipma wrote: > > > >> Do you want to help me packaging some node-* libs (I guess there will be > >> enough > >> for several people :-))? Again, I'm sure we'll be able to package the > >> firefox > >> extension again once the mozext team will have dealt with webextensions. > > > > Well, I have basically zero knowledge of NodeJS, and am not very interested > > in > > contributing to the Debian Javascript Maintainers team. > > > > I am nevertheless ready to help, at least by sponsoring. And maybe also by > > crafting a few packages if there is a clear recipe somewhere (but ideally I > > would prefer not to be listed in the Uploaders). > > > > Do you have a dependency tree of libraries that are not in Debian? > > > > Note that many nodejs libraries are currently waiting in the NEW queue, and > > some others may be in the pipeline (basically for getting the new gitlab in > > Debian), so do not forget to check the NEW queue summary [1] and the WNPP > > database [2]. > > > > [1] https://ftp-master.debian.org/new.html > > [2] https://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=wnpp;dist=unstable > node-zotero-web-library -> TODO https://github.com/zotero/web-library.git Are you sure that this package (node-zotero-web-library), which drags a lot of dependencies not yet in Debian, is really needed for packaging the new release of the Zotero client? Looking at its README.md, this package seems to be related to zotero.org's server side. -- ⢀⣴⠾⠻⢶⣦⠀ Sébastien Villemot ⣾⠁⢠⠒⠀⣿⡁ Debian Developer ⢿⡄⠘⠷⠚⠋⠀ http://sebastien.villemot.name ⠈⠳⣄ http://www.debian.org signature.asc Description: PGP signature
Bug#871502: Re : Bug#871502: zotero-standalone-build: The newer Zotero is standalone only ; a reorganization is neded.
On 2017-11-07 12:52+0100, Sébastien Villemot wrote: > On Tue, Nov 07, 2017 at 12:38:36PM +0100, Félix Sipma wrote: > >> Do you want to help me packaging some node-* libs (I guess there will be >> enough >> for several people :-))? Again, I'm sure we'll be able to package the firefox >> extension again once the mozext team will have dealt with webextensions. > > Well, I have basically zero knowledge of NodeJS, and am not very interested in > contributing to the Debian Javascript Maintainers team. > > I am nevertheless ready to help, at least by sponsoring. And maybe also by > crafting a few packages if there is a clear recipe somewhere (but ideally I > would prefer not to be listed in the Uploaders). > > Do you have a dependency tree of libraries that are not in Debian? > > Note that many nodejs libraries are currently waiting in the NEW queue, and > some others may be in the pipeline (basically for getting the new gitlab in > Debian), so do not forget to check the NEW queue summary [1] and the WNPP > database [2]. > > [1] https://ftp-master.debian.org/new.html > [2] https://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=wnpp;dist=unstable Here is the list of packages which need to be packaged for zotero (some are noted several times, I excluded the packaged already in the archive): node-react -> RFP 805376 https://wiki.debian.org/Javascript/Nodejs/Tasks/react node-react-dom -> TODO node-zotero-web-library -> TODO https://github.com/zotero/web-library.git dev: node-babelify -> RFP 862751 node-browserify -> node-browserify-lite? https://wiki.debian.org/Javascript/Nodejs/Tasks/Browserify node-chai -> TODO node-enzyme -> TODO node-fetch-mock -> TODO node-gulp -> OK gulp node-gulp-babili -> TODO node-gulp-connect -> TODO node-gulp-if -> TODO node-gulp-minify-css -> TODO node-gulp-rename -> TODO node-gulp-sass -> TODO node-react-test-renderer -> TODO node-redux-mock-store -> TODO node-sinon -> "^3.2.1" node-vinyl-buffer -> TODO node-vinyl-source-stream -> TODO node-watchify -> TODO dep: node-babel-regenerator-runtime -> TODO node-classnames -> TODO node-floatthead -> TODO node-history -> TODO node-jquery -> "^2.2.4" node-lodash.omit -> OK node-lodash-packages node-prop-types -> TODO node-react -> RFP 805376 node-react-dom -> TODO node-react-keydown -> TODO node-react-redux -> TODO node-react-router -> TODO node-react-select -> TODO node-react-tinymce -> TODO node-redux -> TODO node-redux-async-queue -> TODO node-redux-promise -> TODO node-redux-router -> TODO node-redux-thunk -> TODO node-tinymce -> TODO node-w3c-xmlhttprequest -> TODO node-zotero-api-client -> TODO https://www.npmjs.com/package/zotero-api-client https://github.com/tnajdek/zotero-api-client/issues/3 node-isomorphic-fetch -> TODO node-zotero-api-client-cache -> TODO node-zotero-api-client -> TODO dev node-babel-plugin-transform-es2015-modules-commonjs -> TODO node-browserify -> node-browserify-lite? node-chai -> TODO node-chai-as-promised -> TODO node-co-mocha -> TODO node-eslint-plugin-react -> TODO node-sass -> TODO Concerning packaging of nodejs modules, I'm new in this task, too. https://wiki.debian.org/Javascript/Nodejs points to https://wiki.debian.org/Javascript/Nodejs/Npm2Deb signature.asc Description: PGP signature
Bug#871502: Re : Bug#871502: zotero-standalone-build: The newer Zotero is standalone only ; a reorganization is neded.
On Tue, Nov 07, 2017 at 12:38:36PM +0100, Félix Sipma wrote: > Do you want to help me packaging some node-* libs (I guess there will be > enough > for several people :-))? Again, I'm sure we'll be able to package the firefox > extension again once the mozext team will have dealt with webextensions. Well, I have basically zero knowledge of NodeJS, and am not very interested in contributing to the Debian Javascript Maintainers team. I am nevertheless ready to help, at least by sponsoring. And maybe also by crafting a few packages if there is a clear recipe somewhere (but ideally I would prefer not to be listed in the Uploaders). Do you have a dependency tree of libraries that are not in Debian? Note that many nodejs libraries are currently waiting in the NEW queue, and some others may be in the pipeline (basically for getting the new gitlab in Debian), so do not forget to check the NEW queue summary [1] and the WNPP database [2]. [1] https://ftp-master.debian.org/new.html [2] https://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=wnpp;dist=unstable -- ⢀⣴⠾⠻⢶⣦⠀ Sébastien Villemot ⣾⠁⢠⠒⠀⣿⡁ Debian Developer ⢿⡄⠘⠷⠚⠋⠀ http://sebastien.villemot.name ⠈⠳⣄ http://www.debian.org signature.asc Description: PGP signature
Bug#871502: Re : Bug#871502: zotero-standalone-build: The newer Zotero is standalone only ; a reorganization is neded.
On 2017-11-07 12:29+0100, Sébastien Villemot wrote: > On Tue, Nov 07, 2017 at 12:28:25PM +0100, Félix Sipma wrote: >> On 2017-11-07 12:25+0100, Sébastien Villemot wrote: >>> On Tue, Nov 07, 2017 at 12:22:36PM +0100, Félix Sipma wrote: >>> I never used get-orig-source, you just run ./debian/rules get-orig-source? Or is this integrated with something else? >>> >>> Indeed you have to run it manually. It is documented in the Debian Policy, >>> but >>> in practice it is less popular than using uscan. In the present case >>> however, >>> uscan is not very well suited. >> >> OK, thanks. Where do you find the ZB_COMMIT and ZSB_COMMIT corresponding to a >> given release (which I guess corresponds to Z_COMMIT)? > > This is a good question. Upstream does not seem to provide this information. > So > in practice I take the most recent commit at the time of packaging. Ouch! Updating this package is getting harder and harder :-). I've asked upstream if they publish this information somewhere. Do you want to help me packaging some node-* libs (I guess there will be enough for several people :-))? Again, I'm sure we'll be able to package the firefox extension again once the mozext team will have dealt with webextensions. signature.asc Description: PGP signature
Bug#871502: Re : Bug#871502: zotero-standalone-build: The newer Zotero is standalone only ; a reorganization is neded.
On Tue, Nov 07, 2017 at 12:28:25PM +0100, Félix Sipma wrote: > On 2017-11-07 12:25+0100, Sébastien Villemot wrote: > > On Tue, Nov 07, 2017 at 12:22:36PM +0100, Félix Sipma wrote: > > > >> I never used get-orig-source, you just run ./debian/rules get-orig-source? > >> Or > >> is this integrated with something else? > > > > Indeed you have to run it manually. It is documented in the Debian Policy, > > but > > in practice it is less popular than using uscan. In the present case > > however, > > uscan is not very well suited. > > OK, thanks. Where do you find the ZB_COMMIT and ZSB_COMMIT corresponding to a > given release (which I guess corresponds to Z_COMMIT)? This is a good question. Upstream does not seem to provide this information. So in practice I take the most recent commit at the time of packaging. -- ⢀⣴⠾⠻⢶⣦⠀ Sébastien Villemot ⣾⠁⢠⠒⠀⣿⡁ Debian Developer ⢿⡄⠘⠷⠚⠋⠀ http://sebastien.villemot.name ⠈⠳⣄ http://www.debian.org signature.asc Description: PGP signature
Bug#871502: Re : Bug#871502: zotero-standalone-build: The newer Zotero is standalone only ; a reorganization is neded.
On 2017-11-07 12:25+0100, Sébastien Villemot wrote: > On Tue, Nov 07, 2017 at 12:22:36PM +0100, Félix Sipma wrote: > >> I never used get-orig-source, you just run ./debian/rules get-orig-source? Or >> is this integrated with something else? > > Indeed you have to run it manually. It is documented in the Debian Policy, but > in practice it is less popular than using uscan. In the present case however, > uscan is not very well suited. OK, thanks. Where do you find the ZB_COMMIT and ZSB_COMMIT corresponding to a given release (which I guess corresponds to Z_COMMIT)? signature.asc Description: PGP signature
Bug#871502: Re : Bug#871502: zotero-standalone-build: The newer Zotero is standalone only ; a reorganization is neded.
On Tue, Nov 07, 2017 at 12:22:36PM +0100, Félix Sipma wrote: > I never used get-orig-source, you just run ./debian/rules get-orig-source? Or > is this integrated with something else? Indeed you have to run it manually. It is documented in the Debian Policy, but in practice it is less popular than using uscan. In the present case however, uscan is not very well suited. -- ⢀⣴⠾⠻⢶⣦⠀ Sébastien Villemot ⣾⠁⢠⠒⠀⣿⡁ Debian Developer ⢿⡄⠘⠷⠚⠋⠀ http://sebastien.villemot.name ⠈⠳⣄ http://www.debian.org signature.asc Description: PGP signature
Bug#871502: Re : Bug#871502: zotero-standalone-build: The newer Zotero is standalone only ; a reorganization is neded.
On 2017-11-07 12:17+0100, Sébastien Villemot wrote: > On Tue, Nov 07, 2017 at 11:38:04AM +0100, Félix Sipma wrote: > >> I misunderstood the 5.0 refactoring, zotero still has to be built from three >> repos, only the client part (https://github.com/zotero/zotero) was refactored >> to use npm/node (and so, needs js libs to get packaged). So, I guess the >> packaging repo should stay as it is for now, and be refactored if upstream >> decides to merge everything in a single repo. >> >> Could you please share your workflow for updating the package? > > 1. look at the end of debian/rules, in the get-orig-source rule: it has the > machinery for creating a new tarball, by pinning commits in the 3 repos. > You'll probably have to update the rule, I tried to give it a try with > commits from 5.0 and it failed. I never used get-orig-source, you just run ./debian/rules get-orig-source? Or is this integrated with something else? > 2. then update debian/copyright > > 3. and deal with all the minified javascript snippets (see > debian/source/lintian-overrides and debian/missing-sources/*) > > 2. and 3. are very painful, so of course you can do them only at the end of > the > packaging process if you prefer. Thanks! signature.asc Description: PGP signature
Bug#871502: Re : Bug#871502: zotero-standalone-build: The newer Zotero is standalone only ; a reorganization is neded.
On Tue, Nov 07, 2017 at 11:38:04AM +0100, Félix Sipma wrote: > I misunderstood the 5.0 refactoring, zotero still has to be built from three > repos, only the client part (https://github.com/zotero/zotero) was refactored > to use npm/node (and so, needs js libs to get packaged). So, I guess the > packaging repo should stay as it is for now, and be refactored if upstream > decides to merge everything in a single repo. > > Could you please share your workflow for updating the package? 1. look at the end of debian/rules, in the get-orig-source rule: it has the machinery for creating a new tarball, by pinning commits in the 3 repos. You'll probably have to update the rule, I tried to give it a try with commits from 5.0 and it failed. 2. then update debian/copyright 3. and deal with all the minified javascript snippets (see debian/source/lintian-overrides and debian/missing-sources/*) 2. and 3. are very painful, so of course you can do them only at the end of the packaging process if you prefer. -- ⢀⣴⠾⠻⢶⣦⠀ Sébastien Villemot ⣾⠁⢠⠒⠀⣿⡁ Debian Developer ⢿⡄⠘⠷⠚⠋⠀ http://sebastien.villemot.name ⠈⠳⣄ http://www.debian.org signature.asc Description: PGP signature
Bug#871502: Re : Bug#871502: zotero-standalone-build: The newer Zotero is standalone only ; a reorganization is neded.
On 2017-11-06 12:11+0100, Sébastien Villemot wrote: > On Mon, Nov 06, 2017 at 11:52:43AM +0100, Félix Sipma wrote: >> On 2017-11-06 11:17+0100, Sébastien Villemot wrote: > >>> Why experimental and not unstable? Is the new version of the plugin >>> incompatible with Zotero 4? If yes, then that should be reflected in >>> dependencies (but then it's probably too early to upload it). >> >> It is not compatible with Zotero 4, as the Zotero part of the libreoffice >> extension is now plugged in zotero-standalone. The package just installs the >> libreoffice part. I've updated the control file to reflect this. OK, so we'll >> wait until having a zotero-standalone 5 package ready. I think having the new >> firefox extension ready should not be a blocker, though (in the case we don't >> have the tools ready to package it in time). > > Ok. > >> Concerning the zotero-standalone package, I guess it would be easier to also >> start from the beginning for the new package, as it was completely reworked. >> You still have no objection in me doing so? > > Please go ahead. Don't hesitate to revamp the packaging, what matters is to > get > something functional and easy to maintain. > > Thanks, I misunderstood the 5.0 refactoring, zotero still has to be built from three repos, only the client part (https://github.com/zotero/zotero) was refactored to use npm/node (and so, needs js libs to get packaged). So, I guess the packaging repo should stay as it is for now, and be refactored if upstream decides to merge everything in a single repo. Could you please share your workflow for updating the package? signature.asc Description: PGP signature
Bug#871502: Re : Bug#871502: zotero-standalone-build: The newer Zotero is standalone only ; a reorganization is neded.
On Mon, Nov 06, 2017 at 11:52:43AM +0100, Félix Sipma wrote: > On 2017-11-06 11:17+0100, Sébastien Villemot wrote: > > Why experimental and not unstable? Is the new version of the plugin > > incompatible with Zotero 4? If yes, then that should be reflected in > > dependencies (but then it's probably too early to upload it). > > It is not compatible with Zotero 4, as the Zotero part of the libreoffice > extension is now plugged in zotero-standalone. The package just installs the > libreoffice part. I've updated the control file to reflect this. OK, so we'll > wait until having a zotero-standalone 5 package ready. I think having the new > firefox extension ready should not be a blocker, though (in the case we don't > have the tools ready to package it in time). Ok. > Concerning the zotero-standalone package, I guess it would be easier to also > start from the beginning for the new package, as it was completely reworked. > You still have no objection in me doing so? Please go ahead. Don't hesitate to revamp the packaging, what matters is to get something functional and easy to maintain. Thanks, -- ⢀⣴⠾⠻⢶⣦⠀ Sébastien Villemot ⣾⠁⢠⠒⠀⣿⡁ Debian Developer ⢿⡄⠘⠷⠚⠋⠀ http://sebastien.villemot.name ⠈⠳⣄ http://www.debian.org signature.asc Description: PGP signature
Bug#871502: Re : Bug#871502: zotero-standalone-build: The newer Zotero is standalone only ; a reorganization is neded.
On 2017-11-06 11:17+0100, Sébastien Villemot wrote: > On Mon, Nov 06, 2017 at 11:07:40AM +0100, Félix Sipma wrote: > >> OK, I've setup a package for libreoffice-zotero-integration. Can you please >> check https://git.gueux.org/libreoffice-zotero-integration.git ? > > Great, that was fast! > > It looks good. > > I'm just wondering whether we could relicense the debian/ work under AGPL-3+, > because it always make more sense to have the debian packaging under the same > license as upstream (e.g. when sending patch). I am ok for relicensing, but I > guess we need to ask Michèle Cane. This is not a high priority item though. > >> I'm waiting for debian-science to join the team before uploading the repo to >> alioth (if I can, I'm not sure if repo creation is still allowed with the >> alioth migration). Then, maybe you could also sponsor the upload to >> experimental? > > Why experimental and not unstable? Is the new version of the plugin > incompatible with Zotero 4? If yes, then that should be reflected in > dependencies (but then it's probably too early to upload it). It is not compatible with Zotero 4, as the Zotero part of the libreoffice extension is now plugged in zotero-standalone. The package just installs the libreoffice part. I've updated the control file to reflect this. OK, so we'll wait until having a zotero-standalone 5 package ready. I think having the new firefox extension ready should not be a blocker, though (in the case we don't have the tools ready to package it in time). Concerning the zotero-standalone package, I guess it would be easier to also start from the beginning for the new package, as it was completely reworked. You still have no objection in me doing so? I'll try to see what javascript libs need to be packaged. signature.asc Description: PGP signature
Bug#871502: Re : Bug#871502: zotero-standalone-build: The newer Zotero is standalone only ; a reorganization is neded.
On Mon, Nov 06, 2017 at 11:07:40AM +0100, Félix Sipma wrote: > OK, I've setup a package for libreoffice-zotero-integration. Can you please > check https://git.gueux.org/libreoffice-zotero-integration.git ? Great, that was fast! It looks good. I'm just wondering whether we could relicense the debian/ work under AGPL-3+, because it always make more sense to have the debian packaging under the same license as upstream (e.g. when sending patch). I am ok for relicensing, but I guess we need to ask Michèle Cane. This is not a high priority item though. > I'm waiting for debian-science to join the team before uploading the repo to > alioth (if I can, I'm not sure if repo creation is still allowed with the > alioth migration). Then, maybe you could also sponsor the upload to > experimental? Why experimental and not unstable? Is the new version of the plugin incompatible with Zotero 4? If yes, then that should be reflected in dependencies (but then it's probably too early to upload it). -- ⢀⣴⠾⠻⢶⣦⠀ Sébastien Villemot ⣾⠁⢠⠒⠀⣿⡁ Debian Developer ⢿⡄⠘⠷⠚⠋⠀ http://sebastien.villemot.name ⠈⠳⣄ http://www.debian.org signature.asc Description: PGP signature
Bug#871502: Re : Bug#871502: zotero-standalone-build: The newer Zotero is standalone only ; a reorganization is neded.
On 2017-11-06 10:44+0100, Sébastien Villemot wrote: > On Mon, Nov 06, 2017 at 07:50:00AM +0100, Félix Sipma wrote: >> On 2017-11-05 19:12+0100, Sébastien Villemot wrote: As you may have already seen, this is a rather complex package. >> >> Yes :-). Upstream seems to have completely modified the distribution, and now >> provides one repo for each of zotero-standalone, zotero-connectors, >> zotero-libreoffice-integration, which may help to go back to something more >> sustainable. They also seem to have switched to javascript-only for >> zotero-standalone, but they use a recent version of nodejs, so we need to >> wait >> for #880936... > > Too bad :( > >> I'd like to move to something manageable, with git-buildpackage. > > Note that the existing setup already uses git-buildpackage. It's the orig > tarball which is custom. > >> A first step would be to add a new source package for >> zotero-libreoffice-integration, and to upload this one to experimental. This >> one may build with the bits taken from the current zotero-standalone-build >> source package. >> >> Do you have objections if I start from the beginning for this package? I'll >> import the changelog and the other needed bits from zotero-standalone-build >> but >> we'll lose the git history. > > That's fine with me. > >> I've asked the Debian Science administrators to join. > > Ok, let me know if your request is not processed in time. > > You may also want to look at > http://debian-science.alioth.debian.org/debian-science-policy.html > (it is outdated in a few places, e.g. priority extra is deprecated, and > Vcs-Browser shoud use /cgit/, not /git/) > > Thanks, OK, I've setup a package for libreoffice-zotero-integration. Can you please check https://git.gueux.org/libreoffice-zotero-integration.git ? I'm waiting for debian-science to join the team before uploading the repo to alioth (if I can, I'm not sure if repo creation is still allowed with the alioth migration). Then, maybe you could also sponsor the upload to experimental? signature.asc Description: PGP signature
Bug#871502: Re : Bug#871502: zotero-standalone-build: The newer Zotero is standalone only ; a reorganization is neded.
On Mon, Nov 06, 2017 at 07:50:00AM +0100, Félix Sipma wrote: > On 2017-11-05 19:12+0100, Sébastien Villemot wrote: > >> As you may have already seen, this is a rather complex package. > > Yes :-). Upstream seems to have completely modified the distribution, and now > provides one repo for each of zotero-standalone, zotero-connectors, > zotero-libreoffice-integration, which may help to go back to something more > sustainable. They also seem to have switched to javascript-only for > zotero-standalone, but they use a recent version of nodejs, so we need to wait > for #880936... Too bad :( > I'd like to move to something manageable, with git-buildpackage. Note that the existing setup already uses git-buildpackage. It's the orig tarball which is custom. > A first step would be to add a new source package for > zotero-libreoffice-integration, and to upload this one to experimental. This > one may build with the bits taken from the current zotero-standalone-build > source package. > > Do you have objections if I start from the beginning for this package? I'll > import the changelog and the other needed bits from zotero-standalone-build > but > we'll lose the git history. That's fine with me. > I've asked the Debian Science administrators to join. Ok, let me know if your request is not processed in time. You may also want to look at http://debian-science.alioth.debian.org/debian-science-policy.html (it is outdated in a few places, e.g. priority extra is deprecated, and Vcs-Browser shoud use /cgit/, not /git/) Thanks, -- ⢀⣴⠾⠻⢶⣦⠀ Sébastien Villemot ⣾⠁⢠⠒⠀⣿⡁ Debian Developer ⢿⡄⠘⠷⠚⠋⠀ http://sebastien.villemot.name ⠈⠳⣄ http://www.debian.org signature.asc Description: PGP signature
Bug#871502: Re : Bug#871502: zotero-standalone-build: The newer Zotero is standalone only ; a reorganization is neded.
On 2017-11-05 19:12+0100, Sébastien Villemot wrote: >> As you may have already seen, this is a rather complex package. Yes :-). Upstream seems to have completely modified the distribution, and now provides one repo for each of zotero-standalone, zotero-connectors, zotero-libreoffice-integration, which may help to go back to something more sustainable. They also seem to have switched to javascript-only for zotero-standalone, but they use a recent version of nodejs, so we need to wait for #880936... I'd like to move to something manageable, with git-buildpackage. A first step would be to add a new source package for zotero-libreoffice-integration, and to upload this one to experimental. This one may build with the bits taken from the current zotero-standalone-build source package. Do you have objections if I start from the beginning for this package? I'll import the changelog and the other needed bits from zotero-standalone-build but we'll lose the git history. I've asked the Debian Science administrators to join. >> The first step is to update the machinery under the get-orig-source target of >> debian/rules, in order to get a new orig tarball. >> >> And the most painful part is to deal with all the minified javascript that is >> spread across the various translators, and which are problematic from a DFSG >> perspective. See debian/source/lintian-overrides and the files under >> debian/missing-sources/*. This is a grunt work that has to be updated with >> every new release; I did not check if there is much to update for the 5.0 >> release. > > I forgot to mention the debian/copyright file, which is also a tad painful to > update. Hopefully, the new zotero will be easier to deal with... We'll see how it goes ;-). signature.asc Description: PGP signature
Bug#871502: Re : Bug#871502: zotero-standalone-build: The newer Zotero is standalone only ; a reorganization is neded.
On Sun, Nov 05, 2017 at 07:10:36PM +0100, Sébastien Villemot wrote:
> On Sun, Nov 05, 2017 at 06:59:38PM +0100, Félix Sipma wrote:
> > On 2017-11-05 18:50+0100, Sébastien Villemot wrote:
> > > On Sun, Nov 05, 2017 at 06:28:42PM +0100, Emmanuel Charpentier wrote:
> > >> Le dimanche 05 novembre 2017 à 18:11 +0100, Sébastien Villemot a
> > >> écrit :
> > >>> On Sun, Nov 05, 2017 at 03:15:59PM +0100, Félix Sipma wrote:
> > >>> So, unless I am missing something, it’s not yet possible to provide
> > >>> Zotero 5
> > >>> with the new Firefox connector. And shipping only the standalone app
> > >>> is rather
> > >>> useless in my opinion.
> > >>
> > >> Nope. For two reasons :
> > >>
> > >> - Zotero standalone can be used with Chrom{e|ium} and the
> > >> corresponding connector.
> > >>
> > >> - At least as an interim measure, Debian users could use Zotero-
> > >> built connectors along with Debian-packaged Chromium and Firefox.
> > >
> > > Since I am using zotero with Firefox, I must say that my motivation to
> > > package
> > > it without the Firefox connector is rather low (and I am not interested in
> > > packaging node-web-ext).
> > >
> > > Basically if any of you wants to become (co-)maintainer of the package
> > > and do
> > > the work, you are more than welcome! I may even open an official RFH/RFA,
> > > I’ll see.
> >
> > OK, I can try to update the package, and may be interested in
> > (co-)maintaining
> > it.
>
> Thanks Félix, this is a good news.
>
> As you may have already seen, this is a rather complex package.
>
> The first step is to update the machinery under the get-orig-source target of
> debian/rules, in order to get a new orig tarball.
>
> And the most painful part is to deal with all the minified javascript that is
> spread across the various translators, and which are problematic from a DFSG
> perspective. See debian/source/lintian-overrides and the files under
> debian/missing-sources/*. This is a grunt work that has to be updated with
> every new release; I did not check if there is much to update for the 5.0
> release.
I forgot to mention the debian/copyright file, which is also a tad painful to
update.
--
⢀⣴⠾⠻⢶⣦⠀ Sébastien Villemot
⣾⠁⢠⠒⠀⣿⡁ Debian Developer
⢿⡄⠘⠷⠚⠋⠀ http://sebastien.villemot.name
⠈⠳⣄ http://www.debian.org
signature.asc
Description: PGP signature
Bug#871502: Re : Bug#871502: zotero-standalone-build: The newer Zotero is standalone only ; a reorganization is neded.
On Sun, Nov 05, 2017 at 06:59:38PM +0100, Félix Sipma wrote:
> On 2017-11-05 18:50+0100, Sébastien Villemot wrote:
> > On Sun, Nov 05, 2017 at 06:28:42PM +0100, Emmanuel Charpentier wrote:
> >> Le dimanche 05 novembre 2017 à 18:11 +0100, Sébastien Villemot a
> >> écrit :
> >>> On Sun, Nov 05, 2017 at 03:15:59PM +0100, Félix Sipma wrote:
> >>> So, unless I am missing something, it’s not yet possible to provide
> >>> Zotero 5
> >>> with the new Firefox connector. And shipping only the standalone app
> >>> is rather
> >>> useless in my opinion.
> >>
> >> Nope. For two reasons :
> >>
> >> - Zotero standalone can be used with Chrom{e|ium} and the
> >> corresponding connector.
> >>
> >> - At least as an interim measure, Debian users could use Zotero-
> >> built connectors along with Debian-packaged Chromium and Firefox.
> >
> > Since I am using zotero with Firefox, I must say that my motivation to
> > package
> > it without the Firefox connector is rather low (and I am not interested in
> > packaging node-web-ext).
> >
> > Basically if any of you wants to become (co-)maintainer of the package and
> > do
> > the work, you are more than welcome! I may even open an official RFH/RFA,
> > I’ll see.
>
> OK, I can try to update the package, and may be interested in (co-)maintaining
> it.
Thanks Félix, this is a good news.
As you may have already seen, this is a rather complex package.
The first step is to update the machinery under the get-orig-source target of
debian/rules, in order to get a new orig tarball.
And the most painful part is to deal with all the minified javascript that is
spread across the various translators, and which are problematic from a DFSG
perspective. See debian/source/lintian-overrides and the files under
debian/missing-sources/*. This is a grunt work that has to be updated with
every new release; I did not check if there is much to update for the 5.0
release.
I hope you are still motivated to do the work after having looked at this :)
Ideally I would also like to move the package under the Debian Science Team
umbrella, because team maintenance is always better. But this can be postponed
if it complicates things for you (e.g. if you're not already in the Debian
Science team on Alioth).
Please feel free to update the repository (possibly on a new branch if you are
not confident enough). I will be happy to sponsor your work once it is ready
(I understand that you are a DM and not yet a DD).
Best,
--
⢀⣴⠾⠻⢶⣦⠀ Sébastien Villemot
⣾⠁⢠⠒⠀⣿⡁ Debian Developer
⢿⡄⠘⠷⠚⠋⠀ http://sebastien.villemot.name
⠈⠳⣄ http://www.debian.org
signature.asc
Description: PGP signature
Bug#871502: Re : Bug#871502: zotero-standalone-build: The newer Zotero is standalone only ; a reorganization is neded.
On 2017-11-05 18:50+0100, Sébastien Villemot wrote:
> On Sun, Nov 05, 2017 at 06:28:42PM +0100, Emmanuel Charpentier wrote:
>> Le dimanche 05 novembre 2017 à 18:11 +0100, Sébastien Villemot a
>> écrit :
>>> On Sun, Nov 05, 2017 at 03:15:59PM +0100, Félix Sipma wrote:
>>> So, unless I am missing something, it’s not yet possible to provide
>>> Zotero 5
>>> with the new Firefox connector. And shipping only the standalone app
>>> is rather
>>> useless in my opinion.
>>
>> Nope. For two reasons :
>>
>> - Zotero standalone can be used with Chrom{e|ium} and the
>> corresponding connector.
>>
>> - At least as an interim measure, Debian users could use Zotero-
>> built connectors along with Debian-packaged Chromium and Firefox.
>
> Since I am using zotero with Firefox, I must say that my motivation to package
> it without the Firefox connector is rather low (and I am not interested in
> packaging node-web-ext).
>
> Basically if any of you wants to become (co-)maintainer of the package and do
> the work, you are more than welcome! I may even open an official RFH/RFA,
> I’ll see.
OK, I can try to update the package, and may be interested in (co-)maintaining
it.
signature.asc
Description: PGP signature
Bug#871502: Re : Bug#871502: zotero-standalone-build: The newer Zotero is standalone only ; a reorganization is neded.
On Sun, Nov 05, 2017 at 06:28:42PM +0100, Emmanuel Charpentier wrote:
> Le dimanche 05 novembre 2017 à 18:11 +0100, Sébastien Villemot a
> écrit :
> > On Sun, Nov 05, 2017 at 03:15:59PM +0100, Félix Sipma wrote:
> > So, unless I am missing something, it’s not yet possible to provide
> > Zotero 5
> > with the new Firefox connector. And shipping only the standalone app
> > is rather
> > useless in my opinion.
>
> Nope. For two reasons :
>
> - Zotero standalone can be used with Chrom{e|ium} and the
> corresponding connector.
>
> - At least as an interim measure, Debian users could use Zotero-
> built connectors along with Debian-packaged Chromium and Firefox.
Since I am using zotero with Firefox, I must say that my motivation to package
it without the Firefox connector is rather low (and I am not interested in
packaging node-web-ext).
Basically if any of you wants to become (co-)maintainer of the package and do
the work, you are more than welcome! I may even open an official RFH/RFA, I’ll
see.
--
⢀⣴⠾⠻⢶⣦⠀ Sébastien Villemot
⣾⠁⢠⠒⠀⣿⡁ Debian Developer
⢿⡄⠘⠷⠚⠋⠀ http://sebastien.villemot.name
⠈⠳⣄ http://www.debian.org
signature.asc
Description: PGP signature
Bug#871502: zotero-standalone-build: The newer Zotero is standalone only ; a reorganization is neded.
On 2017-11-05 18:11+0100, Sébastien Villemot wrote: > Unfortunately the framework for packaging WebExtensions for Firefox is not yet > packaged in Debian (see [1]). > > So, unless I am missing something, it’s not yet possible to provide Zotero 5 > with the new Firefox connector. And shipping only the standalone app is rather > useless in my opinion. > > Any thoughts? > > [1] https://bugs.debian.org/877977 Even if it's just uploaded to experimental, it would be great to have zotero 5 standalone ready (firefox 57 is almost there), even if the new connector is ignored for now. This one will be easier to package later and it will probably not be the hardest part (provided that webextensions tools get packaged, which I guess will be, as there are a lot of other extensions which would otherwise be removed from sid). In the meantime, we would be able to test the standalone app with the connector installed from the zotero website. signature.asc Description: PGP signature
Bug#871502: Re : Bug#871502: zotero-standalone-build: The newer Zotero is standalone only ; a reorganization is neded.
Le dimanche 05 novembre 2017 à 18:11 +0100, Sébastien Villemot a
écrit :
> Control: block -1 by 877977
>
> On Sun, Nov 05, 2017 at 03:15:59PM +0100, Félix Sipma wrote:
> > Package: src:zotero-standalone-build
> > Followup-For: Bug #871502
> >
> > Is there any progress with this? 4.x syncing is said to be
> > supported until
> > "early 2018". Thanks for your work on this important piece of
> > software!
>
> Unfortunately the framework for packaging WebExtensions for Firefox
> is not yet
> packaged in Debian (see [1]).
Therefore, https://bugs.debian.org/877977 becomes an emergency...
> So, unless I am missing something, it’s not yet possible to provide
> Zotero 5
> with the new Firefox connector. And shipping only the standalone app
> is rather
> useless in my opinion.
Nope. For two reasons :
- Zotero standalone can be used with Chrom{e|ium} and the
corresponding connector.
- At least as an interim measure, Debian users could use Zotero-
built connectors along with Debian-packaged Chromium and Firefox.
HTH,
--
Emmanuel Charpentier
> Any thoughts?
>
> [1] https://bugs.debian.org/877977
>
Bug#871502: zotero-standalone-build: The newer Zotero is standalone only ; a reorganization is neded.
Control: block -1 by 877977 On Sun, Nov 05, 2017 at 03:15:59PM +0100, Félix Sipma wrote: > Package: src:zotero-standalone-build > Followup-For: Bug #871502 > > Is there any progress with this? 4.x syncing is said to be supported until > "early 2018". Thanks for your work on this important piece of software! Unfortunately the framework for packaging WebExtensions for Firefox is not yet packaged in Debian (see [1]). So, unless I am missing something, it’s not yet possible to provide Zotero 5 with the new Firefox connector. And shipping only the standalone app is rather useless in my opinion. Any thoughts? [1] https://bugs.debian.org/877977 -- ⢀⣴⠾⠻⢶⣦⠀ Sébastien Villemot ⣾⠁⢠⠒⠀⣿⡁ Debian Developer ⢿⡄⠘⠷⠚⠋⠀ http://sebastien.villemot.name ⠈⠳⣄ http://www.debian.org signature.asc Description: PGP signature
Bug#871502: zotero-standalone-build: The newer Zotero is standalone only ; a reorganization is neded.
Package: src:zotero-standalone-build Followup-For: Bug #871502 Is there any progress with this? 4.x syncing is said to be supported until "early 2018". Thanks for your work on this important piece of software! -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'stable'), (100, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.13.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) signature.asc Description: PGP signature
Bug#871502: zotero-standalone-build: The newer Zotero is standalone only ; a reorganization is neded.
Dear Emmanuel, Thanks for your report. On Tue, Aug 08, 2017 at 05:20:38PM +0200, Emmanuel Charpentier wrote: > Source: zotero-standalone-build > Severity: wishlist > Tags: upstream > After about 1 year of gestation, Zotero 5.0 is out. > * It is standalone only. > * The Firefox interface is now implemented in a "Connector" (as it was always > the > casefor Chrom(e|ium). > * The internal format seems to have changed. > * The interoperability with Zotero 4.x is maintained for a while, but > * The possibility of synchronizing 4.x with the Zotero site (an important > feature > for collaboration) will be terminated in a few months. This has been on my TODO list for some time. Hopefully I will be able to package the new version in the coming weeks, but I’m pretty busy. I must also say that the fact that 4.x clients will soon no longer be able to synchronize is rather demotivating for me. This means that the Zotero package currently in Debian “stretch” stable will become almost unusable, while I put a lot of effort in it. Of course once 5.x is packaged in unstable (and testing) a backport can be provided, but this is not the same in terms of ease and stability as having a package in a stable release. Note that any kind of help is very much welcome for packaging 5.x (and for later maintenance). Cheers, -- ⢀⣴⠾⠻⢶⣦⠀ Sébastien Villemot ⣾⠁⢠⠒⠀⣿⡁ Debian Developer ⢿⡄⠘⠷⠚⠋⠀ http://sebastien.villemot.name ⠈⠳⣄ http://www.debian.org signature.asc Description: PGP signature
Bug#871502: zotero-standalone-build: The newer Zotero is standalone only ; a reorganization is neded.
Source: zotero-standalone-build Severity: wishlist Tags: upstream Dear Maintainer, After about 1 year of gestation, Zotero 5.0 is out. * It is standalone only. * The Firefox interface is now implemented in a "Connector" (as it was always the casefor Chrom(e|ium). * The internal format seems to have changed. * The interoperability with Zotero 4.x is maintained for a while, but * The possibility of synchronizing 4.x with the Zotero site (an important feature for collaboration) will be terminated in a few months. Therefore, an update to Debian's various Zotero package(s) is needed. * The situation is simple for Zotero Standalone : a "simple" packaging analogous to the current "zotero-standalone" package should be enough. A test of upgrading a hand-installed 4.0 version to a hand-installed 5.0 version showed that the upgrade seems robust. * For users of the (original) Firefox plugin version (a. k. a. "xul-ext-zotero" in Debian), it's more complicated. At first sight, a transitional "xul-ext-zotero" package should : - depend on "zotero-standalone" ; - replace the current Zotero Firefox extension with the Connector, *without* intervention on the users' database(s) ; - (possibly) add a trigger starting Zotero standalone either at Firefox's startup (I'm not really sanguine about this possibility, but it would emulate Zotero's permanent availability in Firefox) or at Connector's activation. * libreoffice-zotero-integration : I dunno... I have trouble seeing the point of this package, since the Libreoffice Zotero plugin comes standard with Zoter (standalone) for Linux. The installation of Zotero Standalone should trigger the installation of the plugin if libreoffice-writer happens to be installed ; similarly, the installation of libreoffice-writer should trigger the plugin installation if zotero is installed. The impending suspension of synchronization for Zotero 4.0 makes this (not inconsiderable) work a bit of an emergency... HTH, -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (650, 'testing'), (60, 'unstable'), (50, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.11.0-1-amd64 (SMP w/8 CPU cores) Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8), LANGUAGE=fr_FR.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
