Minor issues with collab-maint
Hi,
I'm having some minor issues with collab-maint today and didn't found
where to report it properly. There's a "collab-maint-devel"[1] list,
but there isn't any activity in there since June/2009. Please point
me to the correct mailing list if this isn't the proper one.
* The HTTP certificate for "anonscm.debian.org" expired on Friday,
April 1, 2016 at 8:59:59 PM (no mention to timezone). This yields
browser warnings saying that the certificate can't be trusted.
* Whenever I "git push" to the repository
"python-path-and-address.git" (which wasn't created by me), the
following error appears (although the code can be pushed perfectly
fine):
remote: Migrating settings from hooks.* to multimailhook.*
remote: Traceback (most recent call last):
remote: File "/usr/local/bin/git-commit-notice", line 16, in
remote: config.set('announceshortlog', 'true')
remote: File "/srv/git.debian.org/bin/git_multimail.py", line 405, in set
remote: env=self.env,
remote: File "/srv/git.debian.org/bin/git_multimail.py", line 272,
in read_git_output
remote: input=input, keepends=keepends, **kw
remote: File "/srv/git.debian.org/bin/git_multimail.py", line 287,
in read_output
remote: raise CommandError(cmd, retcode)
remote: git_multimail.CommandError: Command "git -c
i18n.logoutputencoding=UTF-8 config multimailhook.announceshortlog
true" failed with retcode 255
remote: error: unable to update info/refs+
This looks like a permission issue, but I'm not sure how to fix. Some
files and folders are owned by the group "Debian" (including the
"info/" folder), others are owned by the group "scm_collab-maint"
(like the "objects/" folder, which pushes are written to).
Regards,
Tiago.
[1]: http://lists.alioth.debian.org/pipermail/collab-maint-devel/
--
Tiago "Myhro" Ilieve
Blog: https://blog.myhro.info/
GitHub: https://github.com/myhro
LinkedIn: https://br.linkedin.com/in/myhro
Montes Claros - MG, Brasil
Bug#819773: RFS: python-path-and-address/1.0.0-1 [ITP]
Hi, I've updated the package to the version "1.1.0" which the upstream kindly released after integrating my patch fixing some issues with tests under Python 3. It was uploaded to mentors.d.n[1] as well. Regards, Tiago. [1]: http://mentors.debian.net/package/python-path-and-address -- Tiago "Myhro" Ilieve Blog: https://blog.myhro.info/ GitHub: https://github.com/myhro LinkedIn: https://br.linkedin.com/in/myhro Montes Claros - MG, Brasil
Re: Minor issues with collab-maint
On Sat, 02 Apr 2016, Tiago Ilieve wrote: > Hi, > > I'm having some minor issues with collab-maint today and didn't found > where to report it properly. There's a "collab-maint-devel"[1] list, > but there isn't any activity in there since June/2009. Please point > me to the correct mailing list if this isn't the proper one. > > * The HTTP certificate for "anonscm.debian.org" expired on Friday, > April 1, 2016 at 8:59:59 PM (no mention to timezone). This yields > browser warnings saying that the certificate can't be trusted. That was a misconfiguration of mine. It is fixed by now. Alex
Handling of symbols file on Debian build
Hello, I have some questions about the handling of symbols files at Debian. The quotes based on the package bitz-server[1]. My symbols file are[2]: [quote] libicap.so.1 libicap1 #MINVER# (c++)"icap::RequestHeader::read_header(std::__cxx11::basic_string, std::allocator > const&)@Base" 1.0.0 (c++)"icap::RequestHeader::RequestHeader(std::__cxx11::basic_string, std::allocator > const&)@Base" 1.0.0 (c++)"icap::RequestHeader::RequestHeader(std::__cxx11::basic_string, std::allocator > const&)@Base" 1.0.0 [/quote] The result after building the amd64 binaries are[3]: [quote] libicap.so.1 libicap1 #MINVER# _ZN4icap13RequestHeader11read_headerERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base 1.0.0 _ZN4icap13RequestHeaderC1ERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base 1.0.0 _ZN4icap13RequestHeaderC2ERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base 1.0.0 [/quote] The building at armel[4] fails with: [quote] --- debian/libicap1.symbols (libicap1_1.0.0-1_armel) +++ dpkg-gensymbols782sDG 2016-02-12 21:11:15.078848642 + @@ -1,4 +1,6 @@ libicap.so.1 libicap1 #MINVER# + _ZSt13__adjust_heapIN9__gnu_cxx17__normal_iteratorIPSt4pairINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEiESt6vectorIS9_SaIS9_iS9_NS0_5__ops15_Iter_comp_iterIN4icap6Header27encapsulated_header_comparevT_T0_SM_T1_T2_@Base 1.0.0-1 + _ZSt16__introsort_loopIN9__gnu_cxx17__normal_iteratorIPSt4pairINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEiESt6vectorIS9_SaIS9_iNS0_5__ops15_Iter_comp_iterIN4icap6Header27encapsulated_header_comparevT_SL_T0_T1_@Base 1.0.0-1 (c++)"__gnu_cxx::__normal_iterator, std::allocator > > std::__find_if<__gnu_cxx::__normal_iterator, std::allocator > >, __gnu_cxx::__ops::_Iter_pred > > >(__gnu_cxx::__normal_iterator, std::allocator > >, __gnu_cxx::__normal_iterator, std::allocator > >, __gnu_cxx::__ops::_Iter_pred > >, std::random_access_iterator_tag)@Base" 1.0.0 (c++)"icap::Header::Header()@Base" 1.0.0 (c++)"icap::Header::attach(std::__cxx11::basic_string, std::allocator >, std::__cxx11::basic_string, std::allocator >)@Base" 1.0.0 @@ -64,18 +66,18 @@ [/quote] The result looks like that all builds use an other symbols file as base, because already the second line differs from the original. Why? And from where comes the used symbols file? This circumstance also prevents the simple use of patch. Is there a plan to change it? And what is the best way to maintain it? Nice Weekend.. CU Jörg [1] https://tracker.debian.org/pkg/bitz-server [2] http://httpredir.debian.org/debian/pool/main/b/bitz-server/bitz-server_1.0.0-1.dsc [3] http://ftp.de.debian.org/debian/pool/main/b/bitz-server/libicap1_1.0.0-1_amd64.deb [4] https://buildd.debian.org/status/fetch.php?pkg=bitz-server&arch=armel&ver=1.0.0-1&stamp=1455311478 -- New: GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB 30EE 09F8 9F3C 8CA1 D25D GPG key (long) : 09F89F3C8CA1D25D GPG Key: 8CA1D25D CAcert Key S/N : 0E:D4:56 Old pgp Key: BE581B6E (revoked since 2014-12-31). Jörg Frings-Fürst D-54538 Bausendorf Threema: SYR8SJXB IRC: j_...@freenode.net j_...@oftc.net My wish list: - Please send me a picture from the nature at your home. signature.asc Description: This is a digitally signed message part
Re: Handling of symbols file on Debian build
Hi, On Sat, 2016-04-02 at 10:41 +0200, Jörg Frings-Fürst wrote: > I have some questions about the handling of symbols files at Debian. > > The quotes based on the package bitz-server[1]. > > My symbols file are[2]: > > [quote] > libicap.so.1 libicap1 #MINVER# > (c++)"icap::RequestHeader::read_header(std::__cxx11::basic_string, > std::allocator > const&)@Base" 1.0.0 > (c++)"icap::RequestHeader::RequestHeader(std::__cxx11::basic_string, > std::allocator > const&)@Base" 1.0.0 > (c++)"icap::RequestHeader::RequestHeader(std::__cxx11::basic_string, > std::allocator > const&)@Base" 1.0.0 > [/quote] [...] > The building at armel[4] fails with: > > [quote] > --- debian/libicap1.symbols (libicap1_1.0.0-1_armel) > +++ dpkg-gensymbols782sDG 2016-02-12 21:11:15.078848642 + > @@ -1,4 +1,6 @@ > libicap.so.1 libicap1 #MINVER# > + > _ZSt13__adjust_heapIN9__gnu_cxx17__normal_iteratorIPSt4pairINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEiESt6vectorIS9_SaIS9_iS9_NS0_5__ops15_Iter_comp_iterIN4icap6Header27encapsulated_header_comparevT_T0_SM_T1_T2_@Base > 1.0.0-1 > + > _ZSt16__introsort_loopIN9__gnu_cxx17__normal_iteratorIPSt4pairINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEiESt6vectorIS9_SaIS9_iNS0_5__ops15_Iter_comp_iterIN4icap6Header27encapsulated_header_comparevT_SL_T0_T1_@Base > 1.0.0-1 > (c++)"__gnu_cxx::__normal_iterator, std::allocator > > > std::__find_if<__gnu_cxx::__normal_iterator, std::allocator > >, > __gnu_cxx::__ops::_Iter_pred > > >(__gnu_cxx::__normal_iterator, > std::allocator > >, __gnu_cxx::__normal_iterator, std::allocator > >, > __gnu_cxx::__ops::_Iter_pred > >, std::random_access_iterator_tag)@Base" 1.0.0 > (c++)"icap::Header::Header()@Base" 1.0.0 > (c++)"icap::Header::attach(std::__cxx11::basic_string, std::allocator >, > std::__cxx11::basic_string, std::allocator >)@Base" 1.0.0 > @@ -64,18 +66,18 @@ > [/quote] Welcome to the world of C++ template instantiations! C++ has a rule called the One Deinition Rule (ODR). The rule states that there is exactly one definition of every used function (including templates) in an executable. When compiling a normal program, this is solved by compiling the template once for every translation unit it's used, and then the linker contains special support for merging all the definitions into one. When shared objects are used, for every library and executable which uses a function, the linker emits a weak global symbol for it. The dynamic linker then merges all the symbols together so that only one is used. What you're seeing here are these weak template instantiation symbols used to implement the ODR. In theory, any consumers of your library should work whether these symbols are defined or not (since consumers should have an implementation too), so they are not part of the ABI. Since these symbols are usually from the std:: namespace, I generally ignore all of them using a regex which covers most cases (this will obviously fail if your library actually does emit std:: symbols). Something like this handles it: https://sources.debian.net/src/libsfml/2.3.2%2Bdfsg-1/debian/libsfml-system2.3v5.symbols/ James signature.asc Description: This is a digitally signed message part
Bug#819804: RFS: opengm/2.3.6+20160131-2
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "opengm" * Package name: opengm Version : 2.3.6+20160131-2 Upstream Author : The OpenGM developers * URL : http://hci.iwr.uni-heidelberg.de/opengm2/ * License : Expat Section : science It builds those binary packages: libopengm-bin - command line tools for OpenGM libopengm-dev - C++ template library for discrete factor graph models libopengm-doc - documentation and examples for OpenGM python-opengm - Python interface to OpenGM python-opengm-doc - documentation for the Python interface to OpenGM To access further information about this package, please visit the following URL: http://mentors.debian.net/package/opengm Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/o/opengm/opengm_2.3.6+20160131-2.dsc Or checkout the packaging repository at: https://anonscm.debian.org/git/debian-science/packages/opengm.git Successful build logs on debomatic: [amd64] http://debomatic-amd64.debian.net/distribution#unstable/opengm/2.3.6+20160131-2/buildlog [i386] http://debomatic-i386.debian.net/distribution#unstable/opengm/2.3.6+20160131-2/buildlog Changes since the last upload: * Remove build dependency on vigra, not required. * d/rules: simplify dh_auto_test override. * d/rules: improve comments. * Add upstream patch fixing FBTFS errors on kfreebsd and hurd. * Install Python examples to the python-opengm-doc package. * d/u/metadata: fix formatting error. * d/gbp.conf: change packaging branch to debian/master (DEP-14). Regards, Ghislain Vaillant
Bug#819821: RFS: aggressive-indent-mode/1.5.1-1 -- Emacs minor mode that reindents code after every change
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for an update to aggressive-indent-mode. * Package name: aggressive-indent-mode Version : 1.5.1-1 Upstream Author : Artur Malabarba * URL : https://github.com/Malabarba/aggressive-indent-mode * License : GPL-2+ Section : lisp Changes since the last upload: * New upstream version. Download with dget: dget -x http://mentors.debian.net/debian/pool/main/a/aggressive-indent-mode/aggressive-indent-mode_1.5.1-1.dsc Or build it with gbp: gbp clone --pristine-tar https://anonscm.debian.org/git/pkg-emacsen/pkg/aggressive-indent-mode.git cd aggressive-indent-mode gbp buildpackage Thanks. -- Sean Whitton signature.asc Description: PGP signature
Re: Minor issues with collab-maint
Hi Alex, On 2 April 2016 at 05:32, Alexander Wirt wrote: > That was a misconfiguration of mine. It is fixed by now. Thank you for taking a look at it so quickly. Now it is using a short-lived Let's Encrypt certificate. :-) Regards, Tiago. -- Tiago "Myhro" Ilieve Blog: https://blog.myhro.info/ GitHub: https://github.com/myhro LinkedIn: https://br.linkedin.com/in/myhro Montes Claros - MG, Brasil
Bug#819289: marked as done (RFS: pythonpy/0.4.10-1 [ITP])
Your message dated Sat, 2 Apr 2016 18:54:14 -0300 with message-id and subject line Re: Bug#819289: RFS: pythonpy/0.4.10-1 [ITP] has caused the Debian Bug report #819289, regarding RFS: pythonpy/0.4.10-1 [ITP] 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.) -- 819289: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=819289 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package "pythonpy" * Package name: pythonpy Version : 0.4.10-1 Upstream Author : Russell Stewart * URL : https://github.com/Russell91/pythonpy * License : MIT Section : utils It builds those binary packages: pythonpy - 'python -c', with tab completion and shorthand To access further information about this package, please visit the following URL: http://mentors.debian.net/package/pythonpy Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/p/pythonpy/pythonpy_0.4.10-1.dsc I would like to thank Ben Finney and Gianfranco Costamagna who helped me with the initial packaging work. :-) Regards, Tiago. -- Tiago "Myhro" Ilieve Blog: https://blog.myhro.info/ GitHub: https://github.com/myhro LinkedIn: https://br.linkedin.com/in/myhro Montes Claros - MG, Brasil --- End Message --- --- Begin Message --- Hi, I'm closing this RFS bug as the package has reached unstable[1], thanks to the sponsorship of Dmitry Shachnev. :-) Regards, Tiago. [1]: https://lists.debian.org/debian-devel-changes/2016/04/msg00163.html -- Tiago "Myhro" Ilieve Blog: https://blog.myhro.info/ GitHub: https://github.com/myhro LinkedIn: https://br.linkedin.com/in/myhro Montes Claros - MG, Brasil--- End Message ---
Bug#819834: RFS: webfs/1.21+ds1-11
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor of my package "webfs": Package name: webfs Version : 1.21+ds1-11 Upstream Author : Gerd Knorr URL : http://linux.bytesex.org/misc/webfs.html License : GPL-2 Section : httpd It builds a single binary package: webfs - lightweight HTTP server for static content Further information about this package is available at http://mentors.debian.net/package/webfs As an alternate method, the package may be downloaded directly: dget -x http://mentors.debian.net/debian/pool/main/w/webfs/webfs_1.21+ds1-11.dsc Changes since last upload are as follows: * Step Standards-Version to 3.9.7, no changes. * Advance debhelper compatibility to 9. + debian/control, debian/compat: Updated. + debian/rules: Reduce rule set to use dh together with targets "override_dh_auto_build" and "override_dh_install". Include target "override_dh_auto_build" as no-op. * Suggested document root is already "/var/www/html". + debian/webfsd.conf: Updated. * Improve debconf questions. + debian/templates: Updated. Closes: #727803 * Update debconf translations: + Brazilian Portuguese (Adriano Rafael Gomes). Closes: #762473 + Danish (Joe Hansen). Closes: #765847 + French (Christian Perrier). Closes: #760259 + German (Holger Wansing). Closes: #761481 + Italian (Beatrice Torracca). Closes: #762344 + Japanese (Noritada Kobayashi): New file. + Portuguese (Pedro Ribeiro). Closes: #762495 + Russian (Yuri Kozlov). Closes: #760811 + Swedish (Per Andersson, Martin Bagge). Closes: #760194, #761976 Best regards, Mats Erik Andersson
Bug#819850: RFS: passwordsafe/0.98.1+dfsg-2
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "passwordsafe" * Package name: passwordsafe Version : 0.98.1+dfsg-2 Upstream Author : Rony Shapiro * URL : https://github.com/pwsafe/pwsafe * License : Artistic 2.0 Section : utils It builds those binary packages: passwordsafe - Simple & Secure Password Management passwordsafe-common - architecture independent files for Password Safe To access further information about this package, please visit the following URL: http://mentors.debian.net/package/passwordsafe Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/p/passwordsafe/passwordsafe_0.98.1+dfsg-2.dsc More information about passwordsafe can be obtained from http://www.pwsafe.org Changes since the last upload: Fixed logic error that caused the automated test suite to fail under certain conditions on 32-bit systems Regards, Bill Blough
Bug#817281: closed by Dmitry Smirnov (Re: [pkg-go] Bug#817281: RFS: golang-gopkg-hlandau-easyconfig.v1/1.0.13 [ITP] -- Go package with easy bindings for configurable)
Hi Dmitry, On Fri, Apr 01, 2016 at 09:36:04PM +, Debian Bug Tracking System wrote: > #817281: RFS: golang-gopkg-hlandau-easyconfig.v1/1.0.13 [ITP] -- Go package > with easy bindings for configurable Could you push the release tag to the git repository? https://qa.debian.org/cgi-bin/vcswatch?package=golang-gopkg-hlandau-easyconfig.v1 Regards, Peter
Bug#817281: closed by Dmitry Smirnov (Re: [pkg-go] Bug#817281: RFS: golang-gopkg-hlandau-easyconfig.v1/1.0.13 [ITP] -- Go package with easy bindings for configurable)
On Saturday, 2 April 2016 11:37:47 PM AEST Peter Colberg wrote: > Could you push the release tag to the git repository? Did I forget to push? It should be OK now. -- Best wishes, Dmitry Smirnov. --- The great enemy of the truth is very often not the lie -- deliberate, contrived and dishonest, but the myth, persistent, persuasive, and unrealistic. Belief in myths allows the comfort of opinion without the discomfort of thought. -- John F Kennedy signature.asc Description: This is a digitally signed message part.
Bug#816266: marked as done (RFS: python-qtawesome/0.3.0-1 [ITP])
Your message dated Sun, 03 Apr 2016 04:29:16 + with message-id and subject line closing RFS: python-qtawesome/0.3.0-1 [ITP] has caused the Debian Bug report #816266, regarding RFS: python-qtawesome/0.3.0-1 [ITP] 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.) -- 816266: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=816266 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package "python-qtawesome" * Package name: python-qtawesome Version : 0.3.0-1 Upstream Author : The Spyder Development Team * URL : https://github.com/spyder-ide/qtawesome * License : Expat Section : python It builds those binary packages: python-qtawesome - iconic fonts in PyQt and PySide applications (Python 2) python-qtawesome-common - common files for QtAwesome python-qtawesome-doc - documentation and examples for QtAwesome python3-qtawesome - iconic fonts in PyQt and PySide applications (Python 3) To access further information about this package, please visit the following URL: http://mentors.debian.net/package/python-qtawesome Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/p/python-qtawesome/python-qtawesome_0.3.0-1.dsc Changes since the last upload: * Initial release. (Closes: #814718) Additional information: * The -common package contains 2 fonts, one of which is not available for Debian (elusive-iconfont, SIL OFL 1.1). The other one (fontawesome) is symlinked from its corresponding package. * The package can be tested by installing one of the Python binary packages, the -doc package and running the example.py script under the following location: /usr/share/python-qtawesome-doc/examples. Regards, Ghislain Vaillant --- End Message --- --- Begin Message --- Package python-qtawesome has been removed from mentors.--- End Message ---
