Bug#834567: marked as done (RFS: gxmessage/3.4.3-1 [QA upload])
Your message dated Thu, 18 Aug 2016 22:26:24 + with message-id and subject line closing RFS: gxmessage/3.4.3-1 [QA upload] has caused the Debian Bug report #834567, regarding RFS: gxmessage/3.4.3-1 [QA upload] 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.) -- 834567: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=834567 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "gxmessage" * Package name: gxmessage * Version : 3.4.3-1 * Upstream Author : Tim Musson * URL : http://savannah.gnu.org/projects/gxmessage/ * License : GPL-3.0+ Section : gnome It builds those binary packages: gxmessage - xmessage clone based on GTK+ To access further information about this package, please visit the following URL: https://mentors.debian.net/package/gxmessage Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/g/gxmessage/gxmessage_3.4.3-1.dsc More information about gxmessage can be obtained from http://savannah.gnu.org/projects/gxmessage/ Changes since the last upload: * QA Upload. * New upstream release. (Closes: #786751) * debian/control + Change to libgtk-3-dev in B-D. * debian/patches + Add missing dep3 header to 01_549822.diff * debian/copyright + Update to DEP5 copyright format 1.0. Regards, Daniel Echeverry -- Daniel Echeverry http://wiki.debian.org/DanielEcheverry http://rinconinformatico.net Linux user: #477840 Debian user --- End Message --- --- Begin Message --- Package gxmessage version 3.4.3-1 is in unstable now. https://packages.qa.debian.org/gxmessage--- End Message ---
Bug#834768: RFS: codicefiscale/0.9-1
control: owner -1 !
control: tag -1 moreinfo
On Thu, Aug 18, 2016 at 10:24:31PM +0200, Elena ``of Valhalla'' Grandi wrote:
> On 2016-08-18 at 21:48:05 +0200, Elena ``of Valhalla'' wrote:
FYI: no need to explicitly CC d-mentors@, RFSes are somehow sent there
anyway.
> > To access further information about this package, please visit the
> > following URL:
> >
> > https://mentors.debian.net/package/codicefiscale
> >
> >
> > Alternatively, one can download the package with dget using this command:
> >
> > dget -x
> > https://mentors.debian.net/debian/pool/main/c/codicefiscale/codicefiscale_0.9-1.dsc
> >
> > Or directly from git at:
> >
> > https://anonscm.debian.org/git/python-modules/packages/codicefiscale.git
>
> sorry, I forgot about removing the codicefiscale.egg-info, the actual
> dsc is:
>
> dget -x
> https://mentors.debian.net/debian/pool/main/c/codicefiscale/codicefiscale_0.9+ds0-1.dsc
>
> (all other urls are ok, and their content have been updated, sorry)
This is DPMT, where the usage of git is mandated, so I expect the git
repository to match the generated .dsc (hence I'm ignoring mentors here)
A few small things I'd like to see:
* you email address in d/copyright
* Files-Excluded in d/copyright doesn't list all the files that are
removed (at least according to `git diff --stat
upstream/0.9..upstream/0.9+ds0`)
besides, wrapping that list might not be a bad idea
* Also would be nice to see Build-Depends wrap-and-sort'ed
* python3-codicefiscale uses ${python:Depends} instead of
${python3:Depends}
* why do you disable the tests? (a comment on d/rules might not be a
bad idea here either)
+ I see setup.py lists non-existant tests, if that's the issue maybe
you can get that tests= arg removed (or the actual tests included)
upstream?
* in d/watch, you dversionmangle '.ds0' away, but you're using '+ds0'
actually, so it's not actually mangling anything
* just quickly skimming over the README, I think it would make sense to
include in the binaries, as it provides quick documentation (I think)
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
more about me: https://mapreri.org : :' :
Launchpad user: https://launchpad.net/~mapreri `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia `-
signature.asc
Description: PGP signature
Bug#834768: RFS: codicefiscale/0.9-1
On 2016-08-18 at 21:48:05 +0200, Elena ``of Valhalla'' wrote: > To access further information about this package, please visit the following > URL: > > https://mentors.debian.net/package/codicefiscale > > > Alternatively, one can download the package with dget using this command: > > dget -x > https://mentors.debian.net/debian/pool/main/c/codicefiscale/codicefiscale_0.9-1.dsc > > Or directly from git at: > > https://anonscm.debian.org/git/python-modules/packages/codicefiscale.git sorry, I forgot about removing the codicefiscale.egg-info, the actual dsc is: dget -x https://mentors.debian.net/debian/pool/main/c/codicefiscale/codicefiscale_0.9+ds0-1.dsc (all other urls are ok, and their content have been updated, sorry) -- Elena ``of Valhalla'' signature.asc Description: PGP signature
Bug#834768: RFS: codicefiscale/0.9-1
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "codicefiscale" * Package name: codicefiscale Version : 0.9-1 Upstream Author : Emanuele Rocca * URL : https://github.com/ema/pycodicefiscale * License : LGPL-2.1+ Section : python It builds those binary packages: python-codicefiscale - Generate and validate Italian "codice fiscale" (Python 2.x) python3-codicefiscale - Generate and validate Italian "codice fiscale" (Python 3.x) To access further information about this package, please visit the following URL: https://mentors.debian.net/package/codicefiscale Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/c/codicefiscale/codicefiscale_0.9-1.dsc Or directly from git at: https://anonscm.debian.org/git/python-modules/packages/codicefiscale.git This is the first upload for this package (the it ITP bug is at https://bugs.debian.org/834710 ). Regards, -- Elena ``of Valhalla'' Grandi signature.asc Description: PGP signature
Bug#834759: RFS: mercurial-keyring/1.1.5-1
On 18 August 2016 at 19:11, Christoph Mathys wrote: > Package: sponsorship-requests > Severity: normal > > Dear mentors, > > I am looking for a sponsor for my package "mercurial-keyring" > > * Package name: mercurial-keyring > Version : 1.1.5-1 > Upstream Author : Marcin Kasperski > * URL : http://pypi.python.org/pypi/mercurial_keyring > * License : BSD-3-clause > Section : python > > It builds those binary packages: > > mercurial-keyring - Mercurial Keyring Extension > > To access further information about this package, please visit the following > URL: > > http://mentors.debian.net/package/mercurial-keyring > > Alternatively, one can download the package with dget using this command: > > dget -x > http://mentors.debian.net/debian/pool/main/m/mercurial-keyring/mercurial-keyring_1.1.5-1.dsc > > More information about mercurial-keyring can be obtained from > http://pypi.python.org/pypi/mercurial_keyring > > Changes since the last upload: > > * New upstream release. If nobody esle has, I will review and sponsor this. -- Cheers, Andrew
Bug#834759: RFS: mercurial-keyring/1.1.5-1
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "mercurial-keyring" * Package name: mercurial-keyring Version : 1.1.5-1 Upstream Author : Marcin Kasperski * URL : http://pypi.python.org/pypi/mercurial_keyring * License : BSD-3-clause Section : python It builds those binary packages: mercurial-keyring - Mercurial Keyring Extension To access further information about this package, please visit the following URL: http://mentors.debian.net/package/mercurial-keyring Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/m/mercurial-keyring/mercurial-keyring_1.1.5-1.dsc More information about mercurial-keyring can be obtained from http://pypi.python.org/pypi/mercurial_keyring Changes since the last upload: * New upstream release. Regards, Christoph Mathys
Re: Problems building latest phyml
Hi Andreas (et al.), Thanks for all this. I've made a few very dirty commit early on this summer and hoping to clean up all this sometime in Septembre. It might be a good idea to wait until to build a Debian package for PhyML... Regards, -Stephane- On 17/08/2016 16:33, Andreas Tille wrote: Hi, involving upstream into the discussion now. On Wed, Aug 17, 2016 at 02:48:35PM +0100, James Cowgill wrote: So lets come to the real build errors of [1]: I just fixed the first issue in a new patch (please git pull) but I do not understand this one: Stephane, I've created a simple fix for a missing declaration[2]. Remark: Back than when I was doing some C programming I was told to use register variables when tying to swap values. May be the compiler does this now on its own ... ... gcc -I. -I.. -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -O2 -msse -fomit-frame-pointer -funroll-loops -Wempty-body -Wuninitialized -I/usr/include/libhmsbeagle-1 -lhmsbeagle -ldl -c -o lk.o lk.c lk.c: In function 'Update_PMat_At_Given_Edge': lk.c:2449:31: error: invalid initializer int p_matrices[1] = b_fcus->Pij_rr_idx; ^~ lk.c:2450:31: error: invalid initializer double branch_lens[1] = len; You can't initialize an array with a scalar value (double[] != double). Also, using an array of fixed size 1 is a code smell (why use an array at all?) The quick fix here is probably to wrap the values in curly braces to form a correct array initializer. My patch [3] implements this hint given by James (thanks for the hint) but I agree with James that this code looks a bit suspicious - thus I would like to clarify whether this is really what should be done. Unfortunately this is not the last issue. I'm also running into a linker error which I do not have time to track down for the moment: libtool: link: gcc -Wall -O2 -msse -fomit-frame-pointer -funroll-loops -Wempty-body -Wuninitialized -I/usr/include/libhmsbeagle-1 -Wl,-z -Wl,relro -o phyml-beagle main.o utilities.o optimiz.o lk.o bionj.o models.o free.o help.o simu.o eigen.o pars.o alrt.o interface.o cl.o spr.o draw.o stats.o rates.o mcmc.o times.o tiporder.o mg.o m4.o io.o make.o nexus.o init.o xml.o mixt.o beagle_utils.o -ldl -lhmsbeagle -lm times.o: In function `TIMES_Lk_Birth_Death': times.c:(.text+0x47cd): undefined reference to `DATE_J_Sum_Product' times.o: In function `TIMES_Randomize_Tree_With_Time_Constraints': times.c:(.text+0x62c8): undefined reference to `DATE_Assign_Primary_Calibration' times.c:(.text+0x62d0): undefined reference to `DATE_Update_T_Prior_MinMax' times.c:(.text+0x63b7): undefined reference to `DATE_Check_Calibration_Constraints' times.c:(.text+0x63c5): undefined reference to `DATE_Check_Time_Constraints' collect2: error: ld returned 1 exit status Makefile:1738: recipe for target 'phyml-beagle' failed Kind regards Andreas. [2] https://anonscm.debian.org/cgit/debian-med/phyml.git/tree/debian/patches/fix_declaration_of_temp.patch [3] https://anonscm.debian.org/cgit/debian-med/phyml.git/tree/debian/patches/fix_wrong_initialisation_of_array.patch
Bug#834313: RFS: dh-text/1.0 ITP
On Thu, 2016-08-18 at 08:51 +0200, Ferenc Wágner wrote: > >There's a typo in the man page patch (standa instead of stanza). The typo got fixed after he uploaded the patch. > It's good to have this function in the core, but doesn't that exclude > backports? There were dpkg backports in the past, so not necessarily. > Just out of curiosity: could you please describe a use case for this? None were mentioned on IRC, a C:field for changelog fields was just a thought. -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
