Bug#978440: RFS: paperwork/2.0.2-1 -- Personal document manager
El 14/2/21 a les 18:07, Jérémy Lal ha escrit: [...] > > > Hello, > > i'll go ahead. However there is a high chance it won't migrate to testing, > due to soft freeze policy as Thomas pointed out. Let's see. Release Team has sent and email explaining the sate of bullseye. There's a part that says: -- General === As always, talk to us, preferably via the bts, if you experience issues that we need to be aware of or where you need help. Please be aware it's now a very busy time for us, so bear with us. -- So, Thomas Perret, as maintainer, please follow that advice and put in contact with Release Team and explain the situation. Leopold -- -- Linux User 152692 GPG: 05F4A7A949A2D9AA Catalonia - A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail?
Bug#978440: RFS: paperwork/2.0.2-1 -- Personal document manager
Le dim. 14 févr. 2021 à 17:33, Leopold Palomo-Avellaneda a écrit : > Hi Mechtilde, > > > El 14/2/21 a les 14:41, Mechtilde Stehmann ha escrit: > > Hello Leopold, > > hello all, > > > > does it also build at buildd after a source only upload. > > ok > > > At the official build machines it is n't allowed to install a package > > which isn't called in debian/control beside the essential build packages. > > yes, you are right. > > > You have to call *all needed* packages for building in debian/control. > > Otherwise it can't be build at the official build machines. > > Yes, it's true. But, this is not the case. It call all the dependencies > to build the package. But it fails *before* you call pbuilder in a clean > env. > > > This should be ensured by pbuilder. You have to be able to build in a > > clean pbuilder chroot. > > I have a pbuilder installation to build packages. I'm using pbuilder, > and I built a lot of backports to myself. The server where I run > pbuilder is a Debian stable with several packages installed, nothing > important. Without sphinx-common, when I try to build paperwork, from > salsa I got: > > $ pdebuild > W: /root/.pbuilderrc does not exist > dpkg-checkbuilddeps: error: Unmet build dependencies: python3-sphinx > python3-sphinxcontrib.plantuml sphinx-doc > W: Unmet build-dependency in source > dpkg-source: info: using patch list from debian/patches/series > dpkg-source: info: applying > 0001-Search-for-data-files-in-system-folders.patch > dpkg-source: info: applying > 0002-Show-all-page-at-once-until-python3-getkey-gets-pack.patch > dpkg-source: info: applying > 0003-Disable-potentially-dangerous-plugins.patch > dh clean --with python3,sphinxdoc --buildsystem=pybuild > dh: error: unable to load addon sphinxdoc: Can't locate > Debian/Debhelper/Sequence/sphinxdoc.pm in @INC (you may need to install > the Debian::Debhelper::Sequence::sphinxdoc module) (@INC contains: > /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.28.1 > /usr/local/share/perl/5.28.1 /usr/lib/x86_64-linux-gnu/perl5/5.28 > /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.28 > /usr/share/perl/5.28 /usr/local/lib/site_perl > /usr/lib/x86_64-linux-gnu/perl-base) at (eval 15) line 1. > BEGIN failed--compilation aborted at (eval 15) line 1. > > make: *** [debian/rules:38: clean] Error 25 > > Before, pbuilder is call. However, if I install sphinx-common and run > again pbuilder paperwork is built. > > Another thing is if you really need to call: > > dh $@ --with python3,sphinxdoc --buildsystem=pybuild > > with sphinxdoc. > > In any case, salsa C-I is passed and doesn't fail, and AFAIK they use a > similar env as build machines. Please, DD, push this package. It would > be a pity that we don't have this version in Bullseye. > > Best regards, > > Leopold > > > > Kind regards > > > > Mechtilde > > > > Am 14.02.21 um 14:15 schrieb Leopold Palomo-Avellaneda: > >> Mechtilde, > >> > >> > >> El 14/2/21 a les 14:04, Mechtilde Stehmann ha escrit: > >> > >> [...] > >> > >>> dh clean --with python3,sphinxdoc --buildsystem=pybuild > >>> dh: error: unable to load addon sphinxdoc: Can't locate > >>> Debian/Debhelper/Sequence/sphinxdoc.pm in @INC (you may need to > install > >>> the Debian::Debhelper::Sequence::sphinxdoc module) (@INC contains: > >>> /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.32.1 > >>> /usr/local/share/perl/5.32.1 /usr/lib/x86_64-linux-gnu/perl5/5.32 > >>> /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl-base > >>> /usr/lib/x86_64-linux-gnu/perl/5.32 /usr/share/perl/5.32 > >>> /usr/local/lib/site_perl) at (eval 14) line 1. > >>> BEGIN failed--compilation aborted at (eval 14) line 1. > >> > >> [...] > >> > >> > >> IMHO the problem that you have here is that you have not installed in > >> the box where you run pbuilder or gbp the package sphinx-common. > >> > >> That package contains the file > >> sphinx-common: /usr/share/perl5/Debian/Debhelper/Sequence/sphinxdoc.pm > >> > >> that needs Debhelper to prepare the package to be built. > >> > >> I have backported paperwork without any problem. > >> > >> Best regards, > >> > >> Leopold > Hello, i'll go ahead. However there is a high chance it won't migrate to testing, due to soft freeze policy as Thomas pointed out. Let's see. Jérémy
Bug#978440: RFS: paperwork/2.0.2-1 -- Personal document manager
Hi Mechtilde, El 14/2/21 a les 14:41, Mechtilde Stehmann ha escrit: > Hello Leopold, > hello all, > > does it also build at buildd after a source only upload. ok > At the official build machines it is n't allowed to install a package > which isn't called in debian/control beside the essential build packages. yes, you are right. > You have to call *all needed* packages for building in debian/control. > Otherwise it can't be build at the official build machines. Yes, it's true. But, this is not the case. It call all the dependencies to build the package. But it fails *before* you call pbuilder in a clean env. > This should be ensured by pbuilder. You have to be able to build in a > clean pbuilder chroot. I have a pbuilder installation to build packages. I'm using pbuilder, and I built a lot of backports to myself. The server where I run pbuilder is a Debian stable with several packages installed, nothing important. Without sphinx-common, when I try to build paperwork, from salsa I got: $ pdebuild W: /root/.pbuilderrc does not exist dpkg-checkbuilddeps: error: Unmet build dependencies: python3-sphinx python3-sphinxcontrib.plantuml sphinx-doc W: Unmet build-dependency in source dpkg-source: info: using patch list from debian/patches/series dpkg-source: info: applying 0001-Search-for-data-files-in-system-folders.patch dpkg-source: info: applying 0002-Show-all-page-at-once-until-python3-getkey-gets-pack.patch dpkg-source: info: applying 0003-Disable-potentially-dangerous-plugins.patch dh clean --with python3,sphinxdoc --buildsystem=pybuild dh: error: unable to load addon sphinxdoc: Can't locate Debian/Debhelper/Sequence/sphinxdoc.pm in @INC (you may need to install the Debian::Debhelper::Sequence::sphinxdoc module) (@INC contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.28.1 /usr/local/share/perl/5.28.1 /usr/lib/x86_64-linux-gnu/perl5/5.28 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.28 /usr/share/perl/5.28 /usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base) at (eval 15) line 1. BEGIN failed--compilation aborted at (eval 15) line 1. make: *** [debian/rules:38: clean] Error 25 Before, pbuilder is call. However, if I install sphinx-common and run again pbuilder paperwork is built. Another thing is if you really need to call: dh $@ --with python3,sphinxdoc --buildsystem=pybuild with sphinxdoc. In any case, salsa C-I is passed and doesn't fail, and AFAIK they use a similar env as build machines. Please, DD, push this package. It would be a pity that we don't have this version in Bullseye. Best regards, Leopold > Kind regards > > Mechtilde > > Am 14.02.21 um 14:15 schrieb Leopold Palomo-Avellaneda: >> Mechtilde, >> >> >> El 14/2/21 a les 14:04, Mechtilde Stehmann ha escrit: >> >> [...] >> >>> dh clean --with python3,sphinxdoc --buildsystem=pybuild >>> dh: error: unable to load addon sphinxdoc: Can't locate >>> Debian/Debhelper/Sequence/sphinxdoc.pm in @INC (you may need to install >>> the Debian::Debhelper::Sequence::sphinxdoc module) (@INC contains: >>> /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.32.1 >>> /usr/local/share/perl/5.32.1 /usr/lib/x86_64-linux-gnu/perl5/5.32 >>> /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl-base >>> /usr/lib/x86_64-linux-gnu/perl/5.32 /usr/share/perl/5.32 >>> /usr/local/lib/site_perl) at (eval 14) line 1. >>> BEGIN failed--compilation aborted at (eval 14) line 1. >> >> [...] >> >> >> IMHO the problem that you have here is that you have not installed in >> the box where you run pbuilder or gbp the package sphinx-common. >> >> That package contains the file >> sphinx-common: /usr/share/perl5/Debian/Debhelper/Sequence/sphinxdoc.pm >> >> that needs Debhelper to prepare the package to be built. >> >> I have backported paperwork without any problem. >> >> Best regards, >> >> Leopold >> > -- -- Linux User 152692 GPG: 05F4A7A949A2D9AA Catalonia - A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail?
Bug#978440: RFS: paperwork/2.0.2-1 -- Personal document manager
Le dim. 14 févr. 2021 à 14:45, Mechtilde Stehmann a écrit : > Hello Leopold, > hello all, > > does it also build at buildd after a source only upload. > > At the official build machines it is n't allowed to install a package > which isn't called in debian/control beside the essential build packages. > > You have to call *all needed* packages for building in debian/control. > Otherwise it can't be build at the official build machines. > > This should be ensured by pbuilder. You have to be able to build in a > clean pbuilder chroot. > Hi, indeed, and we all agree on that. I'm using sbuild in a clean sid chroot, and i don't see the problem with sphinx at all. Could the problem be somewhere else ? Jérémy
Bug#978440: RFS: paperwork/2.0.2-1 -- Personal document manager
Hello Leopold, hello all, does it also build at buildd after a source only upload. At the official build machines it is n't allowed to install a package which isn't called in debian/control beside the essential build packages. You have to call *all needed* packages for building in debian/control. Otherwise it can't be build at the official build machines. This should be ensured by pbuilder. You have to be able to build in a clean pbuilder chroot. Kind regards Mechtilde Am 14.02.21 um 14:15 schrieb Leopold Palomo-Avellaneda: > Mechtilde, > > > El 14/2/21 a les 14:04, Mechtilde Stehmann ha escrit: > > [...] > >> dh clean --with python3,sphinxdoc --buildsystem=pybuild >> dh: error: unable to load addon sphinxdoc: Can't locate >> Debian/Debhelper/Sequence/sphinxdoc.pm in @INC (you may need to install >> the Debian::Debhelper::Sequence::sphinxdoc module) (@INC contains: >> /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.32.1 >> /usr/local/share/perl/5.32.1 /usr/lib/x86_64-linux-gnu/perl5/5.32 >> /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl-base >> /usr/lib/x86_64-linux-gnu/perl/5.32 /usr/share/perl/5.32 >> /usr/local/lib/site_perl) at (eval 14) line 1. >> BEGIN failed--compilation aborted at (eval 14) line 1. > > [...] > > > IMHO the problem that you have here is that you have not installed in > the box where you run pbuilder or gbp the package sphinx-common. > > That package contains the file > sphinx-common: /usr/share/perl5/Debian/Debhelper/Sequence/sphinxdoc.pm > > that needs Debhelper to prepare the package to be built. > > I have backported paperwork without any problem. > > Best regards, > > Leopold > -- Mechtilde Stehmann ## Debian Developer ## PGP encryption welcome ## F0E3 7F3D C87A 4998 2899 39E7 F287 7BBA 141A AD7F OpenPGP_signature Description: OpenPGP digital signature
Bug#978440: RFS: paperwork/2.0.2-1 -- Personal document manager
Mechtilde, El 14/2/21 a les 14:04, Mechtilde Stehmann ha escrit: [...] > dh clean --with python3,sphinxdoc --buildsystem=pybuild > dh: error: unable to load addon sphinxdoc: Can't locate > Debian/Debhelper/Sequence/sphinxdoc.pm in @INC (you may need to install > the Debian::Debhelper::Sequence::sphinxdoc module) (@INC contains: > /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.32.1 > /usr/local/share/perl/5.32.1 /usr/lib/x86_64-linux-gnu/perl5/5.32 > /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl-base > /usr/lib/x86_64-linux-gnu/perl/5.32 /usr/share/perl/5.32 > /usr/local/lib/site_perl) at (eval 14) line 1. > BEGIN failed--compilation aborted at (eval 14) line 1. [...] IMHO the problem that you have here is that you have not installed in the box where you run pbuilder or gbp the package sphinx-common. That package contains the file sphinx-common: /usr/share/perl5/Debian/Debhelper/Sequence/sphinxdoc.pm that needs Debhelper to prepare the package to be built. I have backported paperwork without any problem. Best regards, Leopold -- -- Linux User 152692 GPG: 05F4A7A949A2D9AA Catalonia - A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail?
Bug#978440: RFS: paperwork/2.0.2-1 -- Personal document manager
Hello Thomas, This is the diff i did: diff --git a/debian/rules b/debian/rules index 14222e7..a4cacc2 100755 --- a/debian/rules +++ b/debian/rules @@ -35,7 +35,7 @@ debian/paperwork-gtk.install: debian/paperwork-gtk.install.in %: - dh $@ --with python3,sphinxdoc --buildsystem=pybuild + dh $@ --with python3 --buildsystem=pybuild Without this patch I get the following message after applying the patches and before looking and downloading the dependencies. dh clean --with python3,sphinxdoc --buildsystem=pybuild dh: error: unable to load addon sphinxdoc: Can't locate Debian/Debhelper/Sequence/sphinxdoc.pm in @INC (you may need to install the Debian::Debhelper::Sequence::sphinxdoc module) (@INC contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.32.1 /usr/local/share/perl/5.32.1 /usr/lib/x86_64-linux-gnu/perl5/5.32 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl-base /usr/lib/x86_64-linux-gnu/perl/5.32 /usr/share/perl/5.32 /usr/local/lib/site_perl) at (eval 14) line 1. BEGIN failed--compilation aborted at (eval 14) line 1. make: *** [debian/rules:38: clean] Error 25 gbp:error: 'git-pbuilder' failed: it exited with 2 Kind regards Mechtilde Am 14.02.21 um 12:50 schrieb Thomas Perret: >> >> I build it in a pbuilder chroot. So all dependencies defined in >> debian/control are installed. >> > > Hi Mechtilde, > > It's weird, I'm also building it in a pbuilder chroot (using > git-buildpackage) and I also tried building with sbuild and everything > went well. > Can you provide the build errors you get? > > Best regards, > Thomas -- Mechtilde Stehmann ## Debian Developer ## PGP encryption welcome ## F0E3 7F3D C87A 4998 2899 39E7 F287 7BBA 141A AD7F OpenPGP_signature Description: OpenPGP digital signature
Bug#978440: RFS: paperwork/2.0.2-1 -- Personal document manager
I build it in a pbuilder chroot. So all dependencies defined in debian/control are installed. Hi Mechtilde, It's weird, I'm also building it in a pbuilder chroot (using git-buildpackage) and I also tried building with sbuild and everything went well. Can you provide the build errors you get? Best regards, Thomas
Bug#978440: RFS: paperwork/2.0.2-1 -- Personal document manager
Hi Jérémy, I improved the packages descriptions and added 'Suggests: paperwork-gtk' to openpaperwork-gtk and 'Suggests: paperwork-shell, paperwork-gtk' to paperwork-backend. Can you check this is enough and what you had in mind? Well bullseye is in soft freeze. Let's try to upload it asap to unstable, (along with fixing the packages long descriptions and Suggests: as described above). From what I read from the release team[1], the soft freeze doesn't allow NEW packages or to add new binaries to existing packages: > Dropping or adding binary packages to a source package, moving > binaries between source packages or renaming source or binary packages > is no longer allowed. Packages with these changes will not be allowed > to migrate to testing. These changes are also no longer appropriate in > unstable. Also i noticed autopkgtests are failing with lots of these (see below). This needs to be fixed. I can't reproduce the autopkgtest error you get. I'm running it using a schroot. The errors you get seems to be due to permission error to the $HOME directory of the user running tests. As paperwork needs read/write access to this folder (at least $HOME/.config or $XDG_CONFIG_HOME) by default, I'm not sure this should be considered an error on paperwork side. You can also check the autopkgtest job on salsa[2] which doesn't fail Regards, Thomas [1]: https://release.debian.org/bullseye/freeze_policy.html#soft [2]: https://salsa.debian.org/openpaperwork-team/paperwork/-/jobs/1442120
Bug#978440: RFS: paperwork/2.0.2-1 -- Personal document manager
Hello Thomas, I build it in a pbuilder chroot. So all dependencies defined in debian/control are installed. Regards Mechtilde Am 12.02.21 um 20:48 schrieb Thomas Perret: > Hi, > > Sorry I only checked (and answered) to your comment on mentors.d.n. I > just saw now you left the same message here. > > First, thanks for reviewing my package. > > The sphinxdoc debhelper extension[1] helps to install documentation > build with sphinx (python3-sphinx package). > Can you check you installed all build dependencies, especially > python3-sphinx which depends on sphinx-common which itself provides the > dh_sphinxdoc command? > > Well, I guess that now Bullseye soft freeze is gone, it's less urgent > matter. > > Best regards, > Thomas > > [1]: > https://manpages.debian.org/buster/sphinx-common/dh_sphinxdoc.1.en.html -- Mechtilde Stehmann ## Debian Developer ## PGP encryption welcome ## F0E3 7F3D C87A 4998 2899 39E7 F287 7BBA 141A AD7F OpenPGP_signature Description: OpenPGP digital signature
Bug#978440: RFS: paperwork/2.0.2-1 -- Personal document manager
Le sam. 13 févr. 2021 à 11:28, Thomas Perret a écrit : > Hi Jérémy, > > > > > However, i don't quite understand the usefulness of these packages: > > - openpaperwork-core > > - openpaperwork-core-doc > > - openpaperwork-gtk > > - openpaperwork-gtk-doc > > > > I've installed openpaperwork-gtk and it seems it doesn't depend on > > paperwork-gtk, > > but maybe i'm missing some documentation, and the long package > description > > of > > openpaperwork-gtk > > doesn't help either. > > In fact, paperwork-gtk depends on openpaperwork-gtk. > > I agree that openpaperwork-* packages descriptions are not really helpful
Bug#978440: RFS: paperwork/2.0.2-1 -- Personal document manager
Hi Jérémy, However, i don't quite understand the usefulness of these packages: - openpaperwork-core - openpaperwork-core-doc - openpaperwork-gtk - openpaperwork-gtk-doc I've installed openpaperwork-gtk and it seems it doesn't depend on paperwork-gtk, but maybe i'm missing some documentation, and the long package description of openpaperwork-gtk doesn't help either. In fact, paperwork-gtk depends on openpaperwork-gtk. I agree that openpaperwork-* packages descriptions are not really helpful. The basic idea is that openpaperwork-* is the core of the concept implementation of paperwork and paperwork-* are the user interface implementations. The upstream idea behind that is to allow different implementations of user interfaces (e.g.: web interface, mobile interface,…). With paperwork 2.* there is a full support for plugins. You can check which plugins are enabled with command lines: $ paperwork-cli plugins list $ paperwork-gtk plugins list You can check the documentation on openpaperwork-core-doc or online[1] which explains the core & plugins aspects. Manually i had to do dpkg -i paperwork-gtk_2.0.2-1_all.deb paperwork-backend_2.0.2-1_all.deb openpaperwork-core_2.0.2-1_all.deb to get it, and that somehow looks wrong. On the other hand, once installed, it seems to be working all right. I'll try to do actual scanning with it later. My guess is you will have some issues because paperwork-gtk needs plugins provided by openpaperwork-gtk (check the previous command). Maybe the split of package is something that could be discussed, especially the openpaperwork-gtk one which doesn't make a lot of sense in retrospective. Note that the best way to install paperwork in to select the l10n package that correspond to your language, e.g.: paperwork-gtk-l10n-* because it depends on all localized dependencies and provides the localization translations. I don't like that but I couldn't find a correct way to depends on current user's localization. i really think it would be a bonus to Bullseye to have paperwork 2. Maybe debian-release will allow it if we ensure the debian packaging is all right very quickly. I (obviously) agree with that ;-) Best regards, Thomas [1]: https://doc.openpaper.work/openpaperwork_core/latest/
Bug#978440: RFS: paperwork/2.0.2-1 -- Personal document manager
Hi Thomas, i've successfully built paperwork 2.0.2 in a clean sid chroot, using gbp buildpackage (and sbuild). The package is lintian clean. However, i don't quite understand the usefulness of these packages: - openpaperwork-core - openpaperwork-core-doc - openpaperwork-gtk - openpaperwork-gtk-doc I've installed openpaperwork-gtk and it seems it doesn't depend on paperwork-gtk, but maybe i'm missing some documentation, and the long package description of openpaperwork-gtk doesn't help either. Manually i had to do dpkg -i paperwork-gtk_2.0.2-1_all.deb paperwork-backend_2.0.2-1_all.deb openpaperwork-core_2.0.2-1_all.deb to get it, and that somehow looks wrong. On the other hand, once installed, it seems to be working all right. I'll try to do actual scanning with it later. Jérémy PS: i really think it would be a bonus to Bullseye to have paperwork 2. Maybe debian-release will allow it if we ensure the debian packaging is all right very quickly.
Bug#978440: RFS: paperwork/2.0.2-1 -- Personal document manager
Hi, Sorry I only checked (and answered) to your comment on mentors.d.n. I just saw now you left the same message here. First, thanks for reviewing my package. The sphinxdoc debhelper extension[1] helps to install documentation build with sphinx (python3-sphinx package). Can you check you installed all build dependencies, especially python3-sphinx which depends on sphinx-common which itself provides the dh_sphinxdoc command? Well, I guess that now Bullseye soft freeze is gone, it's less urgent matter. Best regards, Thomas [1]: https://manpages.debian.org/buster/sphinx-common/dh_sphinxdoc.1.en.html
Bug#978440: RFS: paperwork/2.0.2-1 -- Personal document manager
Hello, I can't build it as a clone from salsa with rules (2020-10-25). I don't understand what you want with "spinxdoc in line 38. If I use debian/rules without it. I can build it. You can find this comment also at mentors.debian.net Kind regards -- Mechtilde Stehmann ## Debian Developer ## PGP encryption welcome ## F0E3 7F3D C87A 4998 2899 39E7 F287 7BBA 141A AD7F OpenPGP_signature Description: OpenPGP digital signature
