Bug#905928: RFS: phoronix-test-suite/8.0.1-2 [ITP]
Package: sponsorship-requests
Severity: wishlist
Dear mentors,
I am looking for a sponsor for my package "phoronix-test-suite"
* Package name: phoronix-test-suite
Version : 8.0.1-2
Upstream Author : Phoronix
* URL : https://phoronix-test-suite.com
* License : GPL-3+
Section : utils
It builds those binary packages:
phoronix-test-suite - Benchmarking and system testing framework
To access further information about this package, please visit the following
URL:
https://mentors.debian.net/package/phoronix-test-suite
Alternatively, one can download the package with dget using this command:
dget -x
https://mentors.debian.net/debian/pool/main/p/phoronix-test-suite/phoronix-test-suite_8.0.1-2.dsc
More information about hello can be obtained from
https://phoronix-test-suite.com.
Due to it downloading tests from OpenBenchmark.org, I think this belongs
in contrib.
This is a new package, and would therefore need to pass the NEW queue. I
plan on using this package to benchmark an assortment of systems, and
prefer installing with a Debian package to running a shell script any
day.
This package was removed between wheezy and jessie, and much time has
passed since then, so I completely repackaged it for the latest version.
A new version will be released soon ("Milestone 1" of 8.2.0 was released
21 days ago), so I will need an update upload sponsored then as well
(and far into the future, at least until I'm a DM; I plan on ensuring
this package doesn't get removed again).
Apologies for already bumping this to -2, I had forgotten to change the
release from UNRELEASED to unstable in the changelog, so I released -2
to fix that.
Regards,
--
Zebulon McCorkle
zebmccor...@asymptote.club | https://keybase.io/zebMcCorkle
803A 0F47 82AD DDEA 46BE 055F F8F9 DB8C 1A54 6398
|
|
__/
__ Asymptote Club
/(bad ASCII graph by yours truly)
|
|
signature.asc
Description: PGP signature
Re: Bug#905384: libmuscle does not build any more - probably some issue of newer automake
On Sat, Aug 11, 2018 at 08:15:20AM +0200, Andreas Tille wrote: > Hi, > > libmuscle[1] was bilding fine in several uploads but when I now > try to rebuild to fix #904690 I get: > > ... > dh_auto_build --no-parallel > make -j1 > make[2]: Entering directory '/build/libmuscle-3.7+4565' > Making all in libMUSCLE > make[3]: Entering directory '/build/libmuscle-3.7+4565/libMUSCLE' > g++ -DPACKAGE_NAME=\"\" -DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\" > -DPACKAGE_STRING=\"\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE_URL=\"\" > -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT > _H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 > -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 > -DLT_OBJDIR=\".libs/\" -DSTDC_HEADERS= > 1 -DTIME_WITH_SYS_TIME=1 -I. -I.. -Wdate-time -D_FORTIFY_SOURCE=2 -O2 > -funroll-loops -fomit-frame-pointer -ftree-vectorize -DNDEBUG=1 -fopenmp -g > -O2 -fdebug-prefix-map=/build/libmuscle- > 3.7+4565=. -fstack-protector-strong -Wformat -Werror=format-security -c -o > main.o main.cpp > make[3]: *** No rule to make target '../libMUSCLE/libMUSCLE.la', needed by > 'muscle'. Stop. > make[3]: Leaving directory '/build/libmuscle-3.7+4565/libMUSCLE' > ... > > > I suspect an issue in libMUSCLE/Makefile.am. Any hint how to fix this? Fix is attached. The triggering change for the FTBFS was automake 1.16, but this was an old bug. The --no-parallel in debian/rules was a workaround for the same bug and can now be dropped. > Kind regards > > Andreas. cu Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed Description: Correct the libMUSCLE.la dependency This allows automake to generate proper dependencies. Author: Adrian Bunk --- libmuscle-3.7+4565.orig/libMUSCLE/Makefile.am +++ libmuscle-3.7+4565/libMUSCLE/Makefile.am @@ -36,6 +36,6 @@ bin_PROGRAMS = muscle muscle_SOURCES = main.cpp -muscle_LDADD = $(top_builddir)/libMUSCLE/libMUSCLE.la +muscle_LDADD = libMUSCLE.la
Bug#905906: RFS: hinawa-utils/0.0.99-1 [ITP]
Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package "hinawa-utils" * Package name: hinawa-utils Version : 0.0.99-1 Upstream Author : Takashi Sakamoto * URL : https://github.com/takaswie/hinawa-utils * License : GPL-3+ Section : python It builds those binary packages: python3-hinawa-utils - Python 3 module to handle Audio and Music units on IEEE1394 To access further information about this package, please visit the following URL: https://mentors.debian.net/package/hinawa-utils Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/h/hinawa-utils/hinawa-utils_0.0.99-1.dsc More information about groonga-normalizer-mysql can be obtained from https://github.com/takaswie/hinawa-utils Changes since the last upload: [ Takashi Sakamoto ] * Preliminary Release. [ Kentaro Hayashi ] * Closes: #905840 * debian/control - Bump standard version to 4.2.0. No other changes are required. - Add Vcs-* fields - Add Uploaders field Regards, pgpwPXHLIuIIV.pgp Description: PGP signature
Bug#905884: closed by Adam Borowski (Re: Bug#905884: RFS: chafa/0.9.0+git20180731.5ddfe4c-1 [ITP])
On Sat, Aug 11, 2018 at 11:00:03AM +, Debian Bug Tracking System wrote: > On Sat, Aug 11, 2018 at 06:26:46AM +, Lumin wrote: > > > > * Package name: chafa > >Version : 0.9.0+git20180731.5ddfe4c-1 > > * URL : https://hpjansson.org/chafa/ > > * License : LGPL-3 > > > It builds those binary packages: > > > > chafa - Image-to-text converter supporting a wide range of symbols, etc. > > libchafa-dev - development files for image-to-text converter chafa > > libchafa0 - library for image-to-text converter chafa > > > chafa (0.9.0+git20180731.5ddfe4c-1) unstable; urgency=low > > > > * Initial release. (Closes: #905882) > > Awesome! Chafa was on my TODO list, I just lacked the tuits to package it. > And I really prefer work to be done by people who are not me. :) > > It's drastically better than catimg for Unicode images, and than caca for > plain ASCII. I came across Chafa several hours ago as a catimg user, and I was surprised by this brilliant tool. Chafa provides much better functionality compared to CACA and catimg, and supports many image formats. > In NEW. Thanks!
Bug#905884: marked as done (RFS: chafa/0.9.0+git20180731.5ddfe4c-1 [ITP])
Your message dated Sat, 11 Aug 2018 12:57:45 +0200 with message-id <20180811105745.6xpl43h4us6lb...@angband.pl> and subject line Re: Bug#905884: RFS: chafa/0.9.0+git20180731.5ddfe4c-1 [ITP] has caused the Debian Bug report #905884, regarding RFS: chafa/0.9.0+git20180731.5ddfe4c-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.) -- 905884: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905884 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 "chafa" * Package name: chafa Version : 0.9.0+git20180731.5ddfe4c-1 Upstream Author : Hans Petter Jansson * URL : https://hpjansson.org/chafa/ * License : LGPL-3 Section : graphics It builds those binary packages: chafa - Image-to-text converter supporting a wide range of symbols, etc. libchafa-dev - development files for image-to-text converter chafa libchafa0 - library for image-to-text converter chafa To access further information about this package, please visit the following URL: https://mentors.debian.net/package/chafa Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/c/chafa/chafa_0.9.0+git20180731.5ddfe4c-1.dsc More information about hello can be obtained from http://debomatic-amd64.debian.net/distribution#unstable/chafa/0.9.0+git20180731.5ddfe4c-1/buildlog chafa (0.9.0+git20180731.5ddfe4c-1) unstable; urgency=low * Initial release. (Closes: #905882) --- End Message --- --- Begin Message --- On Sat, Aug 11, 2018 at 06:26:46AM +, Lumin wrote: > > * Package name: chafa >Version : 0.9.0+git20180731.5ddfe4c-1 > * URL : https://hpjansson.org/chafa/ > * License : LGPL-3 > It builds those binary packages: > > chafa - Image-to-text converter supporting a wide range of symbols, etc. > libchafa-dev - development files for image-to-text converter chafa > libchafa0 - library for image-to-text converter chafa > chafa (0.9.0+git20180731.5ddfe4c-1) unstable; urgency=low > > * Initial release. (Closes: #905882) Awesome! Chafa was on my TODO list, I just lacked the tuits to package it. And I really prefer work to be done by people who are not me. :) It's drastically better than catimg for Unicode images, and than caca for plain ASCII. In NEW. 喵! -- ⢀⣴⠾⠻⢶⣦⠀ So a Hungarian gypsy mountainman, lumberjack by day job, ⣾⠁⢰⠒⠀⣿⡁ brigand by, uhm, hobby, invented a dish: goulash on potato ⢿⡄⠘⠷⠚⠋⠀ pancakes. Then the Polish couldn't decide which of his ⠈⠳⣄ adjectives to use for the dish's name.--- End Message ---
Re: RFS: pcapy/0.11.3-1 [ITA]
Hello Sergio! Thanks for your comments! I fix the problems that you say me. Please check it 1) On d/copyright, the license specified for the project is wrong. > According to the LICENSE file, the project is released under a slightly > modified version of the Apache license. This is something really > important to get right, otherwise the ftp-masters will certainly reject > the package. You listed the license as being "GPL-2", but the text is > clearly not GPL-2. > > Ohh!!! Sorry I saw the old d/copyright file to do this. 2) Still on d/copyright: as said above, the GPL-2 license is wrong. > However, I think it's also important to mention that the license text is > formatted in a strange/wrong manner. You have text like this: > > [...] > Redistribution and use in source and binary forms, with or without >modification, are permitted provided that the following conditions >are met: > >1. Redistributions of source code must retain the above > [...] > > The correct format for d/copyright is to indent the text using 1 space, > and to use . (dot) for blank lines. Like this: > > [...] > Redistribution and use in source and binary forms, with or without > modification, are permitted provided that the following conditions > are met: > . > 1. Redistributions of source code must retain the above > [...] > Ready! > > 3) The package uses a *really* old version of debhelper (version 5!). > We're at version 11 already, so you should update both d/compat and > d/control (i.e., depend on debhelp >= 11) to reflect that. > Ready! > > 4) You haven't addressed my comment about building a Python 3 package. > IMO you should really do that; lintian will warn you if you don't. > Yes, I forgot do that! Sorry! > > 5) You haven't answered my question about why the package has "Suggests: > doc-base". It seems to be a relic from this very old debhelper; I think > you can safely remove it. > Yes, I remove it. Since I do not have much knowledge about doc-base and why it is there, I left it. But now is removed. Thanks for your help! Regards! -- Arias Emmanuel https://www.linkedin.com/in/emmanuel-arias-437a6a8a http://eamanu.com
Bug#905884: RFS: chafa/0.9.0+git20180731.5ddfe4c-1 [ITP]
Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package "chafa" * Package name: chafa Version : 0.9.0+git20180731.5ddfe4c-1 Upstream Author : Hans Petter Jansson * URL : https://hpjansson.org/chafa/ * License : LGPL-3 Section : graphics It builds those binary packages: chafa - Image-to-text converter supporting a wide range of symbols, etc. libchafa-dev - development files for image-to-text converter chafa libchafa0 - library for image-to-text converter chafa To access further information about this package, please visit the following URL: https://mentors.debian.net/package/chafa Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/c/chafa/chafa_0.9.0+git20180731.5ddfe4c-1.dsc More information about hello can be obtained from http://debomatic-amd64.debian.net/distribution#unstable/chafa/0.9.0+git20180731.5ddfe4c-1/buildlog chafa (0.9.0+git20180731.5ddfe4c-1) unstable; urgency=low * Initial release. (Closes: #905882)
libmuscle does not build any more - probably some issue of newer automake
Hi, libmuscle[1] was bilding fine in several uploads but when I now try to rebuild to fix #904690 I get: ... dh_auto_build --no-parallel make -j1 make[2]: Entering directory '/build/libmuscle-3.7+4565' Making all in libMUSCLE make[3]: Entering directory '/build/libmuscle-3.7+4565/libMUSCLE' g++ -DPACKAGE_NAME=\"\" -DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\" -DPACKAGE_STRING=\"\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE_URL=\"\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT _H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DLT_OBJDIR=\".libs/\" -DSTDC_HEADERS= 1 -DTIME_WITH_SYS_TIME=1 -I. -I.. -Wdate-time -D_FORTIFY_SOURCE=2 -O2 -funroll-loops -fomit-frame-pointer -ftree-vectorize -DNDEBUG=1 -fopenmp -g -O2 -fdebug-prefix-map=/build/libmuscle- 3.7+4565=. -fstack-protector-strong -Wformat -Werror=format-security -c -o main.o main.cpp make[3]: *** No rule to make target '../libMUSCLE/libMUSCLE.la', needed by 'muscle'. Stop. make[3]: Leaving directory '/build/libmuscle-3.7+4565/libMUSCLE' ... I suspect an issue in libMUSCLE/Makefile.am. Any hint how to fix this? Kind regards Andreas. [1] https://salsa.debian.org/med-team/libmuscle -- http://fam-tille.de
Bug#905750: RFS: elpy/1.23.0-1
[Not prematurely sending mail this time] Nicholas, Alas I wrote before, whilst I appreciate the sentiment, please spend any limited time you have for Debian work writing such things in suitable venue(s) and not in an adjunct sponsorship bug. Otherwise I fear the effort expended in such a voluminous and detailed response will be in vain. > > * Please fix "wrong-section-according-to-package-name" on your next > >upload (or otherwise fix Lintian). > > This is currently an Informational level message. When it was a > Warning I declared Section: lisp, even though I do not believe that > this is accurate. Please strive to be Lintian clean not fuss about "warning" about "informational" which are not subject to strict scrutinity and classification by the Lintian maintainers as you seem to infer. > Re: fixing Lintian, this will require a discussion and a more clear > definition of Section: lisp. Most Emacs modes should probably be in > Section: editors, because they are interactive extensions to an > editor. Magit is definitely in the right section eg: vcs. Emacs > packages that enable IDE modes should be in Section: devel. > > Section: lisp should be reserved for libraries like dash-el. This is a topic for elsewhere. > > * gzip -9 might need to be gzip -9n for a reproducible build > >(unchecked) but I'm surprised it's not compressed by another tool > >too (unchecked). > > Thank you for pointing this out. I've reverted @commit:9095c18 > because README.rst is only 2.8k and dh_compress already does the > right thing automatically; that is to say, README.rst is not > "larger than 4k in size" and should not be compressed. ?? I was talking about -n, not -9. Nothing to do with 4k limits but rather reproducibly. > > On the topic of reproducibility, generating an info page made Elpy > unreproducible! > https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/elpy.html > > This will take time to look into. Possibilities are: > 1) sphinx-build is at fault > 2) makeinfo is at fault > 3) something is missing how I'm using 1 and/or 2. > - if this is the case then it's also a case of incomplete >documentation Likely #2 or something similar. https://bugs.debian.org/826158? But again, this is really the wrong venue for these 4/5 topics as it will quickly get lost.. Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Bug#905750: RFS: elpy/1.23.0-1
Nicholas, > > For your wishlist/TODO: > > > > * Please fix "wrong-section-according-to-package-name" on your next > >upload (or otherwise fix Lintian). > > This is currently an Informational level message. When it was a > Warning I declared Section: lisp, even though I do not believe that > this is accurate. > > Re: fixing Lintian, this will require a discussion and a more clear > definition of Section: lisp. Most Emacs modes should probably be in > Section: editors, because they are interactive extensions to an > editor. Magit is definitely in the right section eg: vcs. Emacs > packages that enable IDE modes should be in Section: devel. > > Section: lisp should be reserved for libraries like dash-el. > > > * You should probably avoid building the documentation too if the > >nodocs build profile is enabled. > > I've added it to my TODO and will start learning about how to do > this. > > > * gzip -9 might need to be gzip -9n for a reproducible build > >(unchecked) but I'm surprised it's not compressed by another tool > >too (unchecked). > > Thank you for pointing this out. I've reverted @commit:9095c18 > because README.rst is only 2.8k and dh_compress already does the > right thing automatically; that is to say, README.rst is not > "larger than 4k in size" and should not be compressed. That's not what I was talking about, ie. "reproducibility". > On the topic of reproducibility, generating an info page made Elpy > unreproducible! > https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/elpy.html > > This will take time to look into. Possibilities are: > 1) sphinx-build is at fault > 2) makeinfo is at fault > 3) something is missing how I'm using 1 and/or 2. > - if this is the case then it's also a case of incomplete >documentation > Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Re: RFS: pcapy/0.11.3-1 [ITA]
On Friday, August 10 2018, eamanu wrote: > Hello Sergio, Hi Emmanuel, > I am really sorry for the delay. No need to apologize :-). > I finish the update of pcapy package. I push the commit, but is on > UNRELEASED status. > > Please, check if whole the things are ok, and then I will make change to > unstable status on d/changelog Well, I still see a few problems. Sorry about that. Here's the list of things I spotted: 1) On d/copyright, the license specified for the project is wrong. According to the LICENSE file, the project is released under a slightly modified version of the Apache license. This is something really important to get right, otherwise the ftp-masters will certainly reject the package. You listed the license as being "GPL-2", but the text is clearly not GPL-2. 2) Still on d/copyright: as said above, the GPL-2 license is wrong. However, I think it's also important to mention that the license text is formatted in a strange/wrong manner. You have text like this: [...] Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the above [...] The correct format for d/copyright is to indent the text using 1 space, and to use . (dot) for blank lines. Like this: [...] Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: . 1. Redistributions of source code must retain the above [...] 3) The package uses a *really* old version of debhelper (version 5!). We're at version 11 already, so you should update both d/compat and d/control (i.e., depend on debhelp >= 11) to reflect that. 4) You haven't addressed my comment about building a Python 3 package. IMO you should really do that; lintian will warn you if you don't. 5) You haven't answered my question about why the package has "Suggests: doc-base". It seems to be a relic from this very old debhelper; I think you can safely remove it. 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
