Re: debian/watch file for the ledgersmb package
On Thu, Aug 2, 2018 at 1:58 PM Shengjing Zhu wrote: > Not about repack, current watch file will download tarball that github > generated, not the one upstream uploading to github release. Look at > https://github.com/ledgersmb/LedgerSMB/releases, please be careful > that there're two kinds of tarball. Don't look at > https://github.com/ledgersmb/LedgerSMB/tags, which doesn't have asc If that were entirely true then where does the, in this case, downloaded file ledgersmb-1.5.21.tar.gz.asc from? I'd always thought that resulted from the GitHub pgpsigurlmangle entry[1], which does point to the 'releases'. And if the final URL is pointed to the 'releases' also, it fails because it can't find the *.asc file as it's looking for the wrong file name and ends up not downloading anything. That's why it confused me; the form of watch I ended up using at least downloaded files but still failed due to the apparently bad downloaded archive. > And I think using upstream http release page is much simpler for you. I'm inclined to agree and will look at using that site instead. Thanks! Robert James Clay j...@rocasa.us [1] https://wiki.debian.org/debian/watch
Re: debian/watch file for the ledgersmb package
On Fri, Aug 3, 2018 at 1:25 AM Robert James Clay wrote: > Running, for instance, the command "uscan --force-download --verbose --rename > --destdir .." results in the error "BAD signature". And indeed, checking the > resulting files from that command finds that the archive does look to have > been repacked (it's smaller) and so the verify fails. Not about repack, current watch file will download tarball that github generated, not the one upstream uploading to github release. Look at https://github.com/ledgersmb/LedgerSMB/releases, please be careful that there're two kinds of tarball. Don't look at https://github.com/ledgersmb/LedgerSMB/tags, which doesn't have asc signatures. And I think using upstream http release page is much simpler for you. -- Best regards, Shengjing Zhu
Bug#905273: marked as done (RFS: im-config/0.37-1 [RC])
Your message dated Thu, 2 Aug 2018 19:54:50 +0200 with message-id <20180802175450.owfrigfdm2xi3...@angband.pl> and subject line Re: Bug#905273: RFS: im-config/0.37-1 [RC] has caused the Debian Bug report #905273, regarding RFS: im-config/0.37-1 [RC] to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 905273: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905273 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: sponsorship-requests Severity: important X-Debbugs-CC: os...@debian.org debian-input-met...@lists.debian.org Dear mentors and debian-input-method members, I am looking for a sponsor for team package "im-config" to fix a severe bug introduced in its last upload (shell grammar error causing login failure) * Package name: im-config Version : 0.37-1 Upstream Author : Osamu Aoki * URL : https://salsa.debian.org/input-method-team/im-config * License : GPL-2+ Section : x11 To access further information about this package, please visit the following URL: https://mentors.debian.net/package/im-config Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/i/im-config/im-config_0.37-1.dsc Git packaging repository: https://salsa.debian.org/input-method-team/im-config Changes since the last upload: im-config (0.37-1) unstable; urgency=high . * Team upload. * Fix shell grammar errors introduced in last upload. Closes: #905264, #905259, #905260. * Discard STDERR messages when launching fcitx. (Merged downstream harmless fix for LP: #1722427) * debian/control: Bump Standards-Version to 4.2.0 (no changes needed). -- Regards, Boyuan Yang --- End Message --- --- Begin Message --- On Thu, Aug 02, 2018 at 08:29:34PM +0800, Boyuan Yang wrote: > * Package name: im-config >Version : 0.37-1 > im-config (0.37-1) unstable; urgency=high > . >* Team upload. >* Fix shell grammar errors introduced in last upload. > Closes: #905264, #905259, #905260. >* Discard STDERR messages when launching fcitx. > (Merged downstream harmless fix for LP: #1722427) >* debian/control: Bump Standards-Version to 4.2.0 (no changes needed). ✓ -- // If you believe in so-called "intellectual property", please immediately // cease using counterfeit alphabets. Instead, contact the nearest temple // of Amon, whose priests will provide you with scribal services for all // your writing needs, for Reasonable And Non-Discriminatory prices.--- End Message ---
debian/watch file for the ledgersmb package
All, The upstream for the ledgersmb package [1] moved from Sourceforge to GitHub including for where new releases of the application are made available; so the debian/watch file in the package needed to be`updated for the new locations of the distribution archive and its detached`gpg file that is used for verification. Updating the watch file [2] so that uscan can see new releases was successful but the *.asc file associated with the new releases and used for the gpg verification does not seem to get referenced properly so the verification step fails. (Or the verify is happening after the repack for some reason but before renaming the archive? It's not clear...) Since the verify step is failing, the step for doing the repack of the archive does not happen. Manually downloading then verifying the archive can be done successfully although then repacking the upstream archive also has to done manually. The download, verify, and repacking was successful at the time when the watch file was pointing to the old SourceForge site. Running, for instance, the command "uscan --force-download --verbose --rename --destdir .." results in the error "BAD signature". And indeed, checking the resulting files from that command finds that the archive does look to have been repacked (it's smaller) and so the verify fails. The current upstream version in Debian is 1.5.21 but 1.6.3 has been released; I'll be working on upgrading the packaging for the new series. I'd appreciate if the current version of the debain/watch file be reviewed and advice given about how it could be updated to work properly. Besides the new releases being available at github (via their tags), they are also available at a separate upstream site [3]; I wonder if it would be better to try using that? Robert James Clay, j...@rocasa.us, rjc...@gmail.com [1] https://tracker.debian.org/pkg/ledgersmb [2] https://sources.debian.org/src/ledgersmb/1.5.21+ds-1/debian/watch/ [3] https://download.ledgersmb.org/f/Releases/
Bug#905273: RFS: im-config/0.37-1 [RC]
Package: sponsorship-requests Severity: important X-Debbugs-CC: os...@debian.org debian-input-met...@lists.debian.org Dear mentors and debian-input-method members, I am looking for a sponsor for team package "im-config" to fix a severe bug introduced in its last upload (shell grammar error causing login failure) * Package name: im-config Version : 0.37-1 Upstream Author : Osamu Aoki * URL : https://salsa.debian.org/input-method-team/im-config * License : GPL-2+ Section : x11 To access further information about this package, please visit the following URL: https://mentors.debian.net/package/im-config Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/i/im-config/im-config_0.37-1.dsc Git packaging repository: https://salsa.debian.org/input-method-team/im-config Changes since the last upload: im-config (0.37-1) unstable; urgency=high . * Team upload. * Fix shell grammar errors introduced in last upload. Closes: #905264, #905259, #905260. * Discard STDERR messages when launching fcitx. (Merged downstream harmless fix for LP: #1722427) * debian/control: Bump Standards-Version to 4.2.0 (no changes needed). -- Regards, Boyuan Yang
Re: PermissionError: [Errno 13] Permission denied: '/sbuild-nonexistent'
On Thursday, August 02 2018, PICCA Frederic-Emmanuel wrote: > Hello, > > I am preparing the new silx package and I get this error message during the > build > > WARNING: autodoc: failed to import module 'silx.opencl.codec.byte_offset'; > the following exception was raised: > Traceback (most recent call last): > File "/usr/lib/python3/dist-packages/sphinx/ext/autodoc/importer.py", line > 152, in import_module > __import__(modname) > File > "/<>/silx-0.8.0+dfsg/.pybuild/cpython3_3.6_silx/build/silx/opencl/codec/byte_offset.py", > line 58, in > from pyopencl.algorithm import GenericScanKernel > File "/usr/lib/python3/dist-packages/pyopencl/algorithm.py", line 37, in > > from pyopencl.scan import ScanTemplate > File "/usr/lib/python3/dist-packages/pyopencl/scan.py", line 1137, in > > key_builder=_NumpyTypesKeyBuilder()) > File "/usr/lib/python3/dist-packages/pytools/persistent_dict.py", line 566, > in __init__ > _PersistentDictBase.__init__(self, identifier, key_builder, container_dir) > File "/usr/lib/python3/dist-packages/pytools/persistent_dict.py", line 463, > in __init__ > self._make_container_dir() > File "/usr/lib/python3/dist-packages/pytools/persistent_dict.py", line 97, > in wrapper > return f(obj, *args, **kwargs) > File "/usr/lib/python3/dist-packages/pytools/persistent_dict.py", line 505, > in _make_container_dir > _make_dir_recursively(self.container_dir) > File "/usr/lib/python3/dist-packages/pytools/persistent_dict.py", line 72, > in _make_dir_recursively > os.makedirs(dir) > File "/usr/lib/python3.6/os.py", line 210, in makedirs > makedirs(head, mode, exist_ok) > File "/usr/lib/python3.6/os.py", line 210, in makedirs > makedirs(head, mode, exist_ok) > File "/usr/lib/python3.6/os.py", line 210, in makedirs > makedirs(head, mode, exist_ok) > File "/usr/lib/python3.6/os.py", line 220, in makedirs > mkdir(name, mode) > PermissionError: [Errno 13] Permission denied: '/sbuild-nonexistent' [ Disclaimer: I haven't analyzed why the package needs access to HOME. ] > so my question is. > > what is the right solutin in order to solve this ? > > export HOME=$CURDIR in the rules files (and voila) Yes, explicitly setting HOME is the default solution in this case. It can be a directory inside $(CURDIR) as well. > What I understant is that there is a persitent mechanism which is legitimate > in nomal use. > > So what is the purpose of HOME pointing no-where during the build process. HOME points to /sbuild-nonexistent because in general packages shouldn't mess with the user's home. But there are exceptions or special cases (specially during the testsuite run), so sometimes you need to override the variable by hand. Thanks, -- Sergio GPG key ID: 237A 54B1 0287 28BF 00EF 31F4 D0EB 7628 65FC 5E36 Please send encrypted e-mail if possible http://sergiodj.net/ signature.asc Description: PGP signature
PermissionError: [Errno 13] Permission denied: '/sbuild-nonexistent'
Hello, I am preparing the new silx package and I get this error message during the build WARNING: autodoc: failed to import module 'silx.opencl.codec.byte_offset'; the following exception was raised: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/sphinx/ext/autodoc/importer.py", line 152, in import_module __import__(modname) File "/<>/silx-0.8.0+dfsg/.pybuild/cpython3_3.6_silx/build/silx/opencl/codec/byte_offset.py", line 58, in from pyopencl.algorithm import GenericScanKernel File "/usr/lib/python3/dist-packages/pyopencl/algorithm.py", line 37, in from pyopencl.scan import ScanTemplate File "/usr/lib/python3/dist-packages/pyopencl/scan.py", line 1137, in key_builder=_NumpyTypesKeyBuilder()) File "/usr/lib/python3/dist-packages/pytools/persistent_dict.py", line 566, in __init__ _PersistentDictBase.__init__(self, identifier, key_builder, container_dir) File "/usr/lib/python3/dist-packages/pytools/persistent_dict.py", line 463, in __init__ self._make_container_dir() File "/usr/lib/python3/dist-packages/pytools/persistent_dict.py", line 97, in wrapper return f(obj, *args, **kwargs) File "/usr/lib/python3/dist-packages/pytools/persistent_dict.py", line 505, in _make_container_dir _make_dir_recursively(self.container_dir) File "/usr/lib/python3/dist-packages/pytools/persistent_dict.py", line 72, in _make_dir_recursively os.makedirs(dir) File "/usr/lib/python3.6/os.py", line 210, in makedirs makedirs(head, mode, exist_ok) File "/usr/lib/python3.6/os.py", line 210, in makedirs makedirs(head, mode, exist_ok) File "/usr/lib/python3.6/os.py", line 210, in makedirs makedirs(head, mode, exist_ok) File "/usr/lib/python3.6/os.py", line 220, in makedirs mkdir(name, mode) PermissionError: [Errno 13] Permission denied: '/sbuild-nonexistent' so my question is. what is the right solutin in order to solve this ? export HOME=$CURDIR in the rules files (and voila) or this is a bug in pytools ? What I understant is that there is a persitent mechanism which is legitimate in nomal use. So what is the purpose of HOME pointing no-where during the build process. thanks for your help. Frédéric
