Bug#862123: RFS: golang-github-nebulouslabs-fastrand/0.0~git20170420.0.5a1a312-1 [ITP]
hello, >"golang-github-nebulouslabs-fastrand" LGTM G.
Re: Bug#861754: libpll: FTBFS on non-x86: x86intrin.h: No such file or directory
Hi Aaron, On Mon, May 15, 2017 at 10:01:53AM -0400, Aaron M. Ucko wrote: > > Alas, non-x86 builds are still failing, with the immediate cause of > failure being either an uncompilable cpuid call Hmmm, I'm a bit clueless about this. > or (in the case of > powerpc[spe] and ppc64[el]) the use of x86-specific compiler flags for > certain files. Please limit all of the above to x86 architectures. I think I could realise this but I'm afraid after having done so the cpuid issue will remain also for these - so seeking for help here fist. Any hints? Kind regards Andreas. -- http://fam-tille.de
Bug#862711: marked as done (RFS: dirty.js/1.0.0-1.1 [NMU] [RC])
Your message dated Tue, 16 May 2017 08:57:27 + (UTC) with message-id <703176211.381066.1494925047...@mail.yahoo.com> and subject line Re: Bug#862711: RFS: dirty.js/1.0.0-1.1 [NMU] [RC] has caused the Debian Bug report #862711, regarding RFS: dirty.js/1.0.0-1.1 [NMU] [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.) -- 862711: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=862711 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 "dirty.js" * Package name: dirty.js Version : 1.0.0-1.1 Upstream Author : Felix Geisendörfer * URL : https://github.com/felixge/node-dirty * License : MIT License Section : web It builds those binary packages: node-dirty - tiny and fast key-value store for Node To access further information about this package, please visit the following URL: https://mentors.debian.net/package/dirty.js Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/d/dirty.js/dirty.js_1.0.0-1.1.dsc More information about hello can be obtained from https://www.example.com. Changes since the last upload: * Non-maintainer upload. * New upstream version 1.0.0 (Closes: #771790) * Fixing lintian issues Regards, Val Markovic --- End Message --- --- Begin Message --- hello, tweaked a lot of stuff (compat level, VCS fields, copyright link, versioning and something else) and sponsored. also pushed stuff on git G.--- End Message ---
Re: artifacts in upstream, re: pristine source
On 2017-05-16 12:52 +0800, Paul Wise wrote: > On Tue, May 16, 2017 at 12:42 PM, Brian Smith wrote: > > > Regarding the "pristine source" requirement (i.e. no build artifacts) in the > > source archive: should the upstream tarball be imported to the upstream > > branch "as is", and the tar command for orig.tar.gz should be configured to > > omit build artifacts? Or should artifacts either be removed from or not > > imported to the upstream branch? > > Contact upstream and ask them to remove them from their VCS and source > tarballs and put them into their binary tarballs/packages. If they > refuse, then add Files-Excluded to debian/watch Files-Excluded goes in debian/copyright, not debian/watch. (unless there is some new feature I'm not aware of). It would arguably make more sense in watch, but that's not how it works. See man mk-origtargz for details. Wookey -- Principal hats: Linaro, Debian, Wookware, ARM http://wookware.org/ signature.asc Description: Digital signature
Bug#862687: RFS: libtgvoip/0.4.1~git20170514.73bf810-1 [ITP] - VoIP library for Telegram clients
Control: tag -1 moreinfo Control: owner -1 ! On Mon, May 15, 2017 at 10:57:36PM +0300, Коля Гурьев wrote: > I am looking for a sponsor for my package "libtgvoip" o/ > dget -x > https://mentors.debian.net/debian/pool/main/libt/libtgvoip/libtgvoip_0.4.1~git20170514.73bf810-1.dsc Using git as you know I prefer it :) I fixed the HEAD on alioth to point to the debian branch (as otherwise cloning would checkout master causing warning: remote HEAD refers to nonexistent ref, unable to checkout. ), also could you please push some upstream tags and add an appropriate d/gbp.conf? Review: * d/control: + Vcs-Git is wrong + I appreciate when Vcs-Browser is the same as Vcs-Git, given they can be now (hint: use /git/ in both) * d/rules: + why are you calling dh_install manually at the end of dh_auto_install? it's called by dh anyway It also fails to build for me on i386 with an error that looks like SSE2 related (but I'll let you look at it). Otherwise it looks cool to me, but I'd like to have a correct Vcs-Git and a working i386 build at the first upload… -- 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#862687: RFS: libtgvoip/0.4.1~git20170514.73bf810-1 [ITP] - VoIP library for Telegram clients
Hi, >It also fails to build for me on i386 with an error that looks like SSE2 >related (but I'll let you look at it). does this mean having to restrict telegram to amd64 and eventually only i386? this would exclude a lot of architectures G.
Re: Bug#861754: libpll: FTBFS on non-x86: x86intrin.h: No such file or directory
Control: tags -1 patch
Hi,
On 16/05/17 09:50, Andreas Tille wrote:
> Hi Aaron,
>
> On Mon, May 15, 2017 at 10:01:53AM -0400, Aaron M. Ucko wrote:
>>
>> Alas, non-x86 builds are still failing, with the immediate cause of
>> failure being either an uncompilable cpuid call
>
> Hmmm, I'm a bit clueless about this.
>
>> or (in the case of
>> powerpc[spe] and ppc64[el]) the use of x86-specific compiler flags for
>> certain files. Please limit all of the above to x86 architectures.
>
> I think I could realise this but I'm afraid after having done so the
> cpuid issue will remain also for these - so seeking for help here fist.
Possibly the attached patch will work?
This:
- only tries to detect x86 features on x86
- detects altivec properly (although it's not used anywhere?)
- uses GCC's __builtin_cpu_supports which is nicer than cpuid
- compiles with --disable-* on all arches except x86
- enables arch specific code on x86 (there is proper runtime detection now)
- uses debhelper 10 to avoid manual autogen
- includes architecture.mk which is required before using DEB_HOST_*
james
diff -Nru libpll-0.3.0/debian/compat libpll-0.3.0/debian/compat
--- libpll-0.3.0/debian/compat 2017-05-15 08:19:35.0 +0100
+++ libpll-0.3.0/debian/compat 2017-05-16 11:45:26.0 +0100
@@ -1 +1 @@
-9
+10
diff -Nru libpll-0.3.0/debian/patches/hardware-detect.patch
libpll-0.3.0/debian/patches/hardware-detect.patch
--- libpll-0.3.0/debian/patches/hardware-detect.patch 1970-01-01
01:00:00.0 +0100
+++ libpll-0.3.0/debian/patches/hardware-detect.patch 2017-05-16
11:45:11.0 +0100
@@ -0,0 +1,61 @@
+--- a/src/hardware.c
b/src/hardware.c
+@@ -21,45 +21,23 @@
+
+ #include "pll.h"
+
+-#ifndef __PPC__
+-#define cpuid(f1, f2, a, b, c, d)\
+- __asm__ __volatile__ ("cpuid" \
+-: "=a" (a), "=b" (b), "=c" (c), "=d" (d) \
+-: "a" (f1), "c" (f2));
+-#endif
+-
+ static void cpu_features_detect()
+ {
+- unsigned int a,b,c,d;
+-
+ memset(pll_hardware,0,sizeof(pll_hardware_t));
+
+-#ifdef __PPC__
+- pll_hardware->altivec_present = 1;
+-#else
+-
+- cpuid(0,0,a,b,c,d);
+- unsigned int maxlevel = a & 0xff;
+-
+- if (maxlevel >= 1)
+- {
+-cpuid(1,0,a,b,c,d);
+-pll_hardware->mmx_present= (d >> 23) & 1;
+-pll_hardware->sse_present= (d >> 25) & 1;
+-pll_hardware->sse2_present = (d >> 26) & 1;
+-pll_hardware->sse3_present = (c >> 0) & 1;
+-pll_hardware->ssse3_present = (c >> 9) & 1;
+-pll_hardware->sse41_present = (c >> 19) & 1;
+-pll_hardware->sse42_present = (c >> 20) & 1;
+-pll_hardware->popcnt_present = (c >> 23) & 1;
+-pll_hardware->avx_present= (c >> 28) & 1;
+-
+-if (maxlevel >= 7)
+-{
+- cpuid(7,0,a,b,c,d);
+- pll_hardware->avx2_present = (b >> 5) & 1;
+-}
+- }
++#if defined(__PPC__)
++ pll_hardware->altivec_present = __builtin_cpu_supports("altivec");
++#elif defined(__x86_64__) || defined(__i386__)
++ pll_hardware->mmx_present = __builtin_cpu_supports("mmx");
++ pll_hardware->sse_present = __builtin_cpu_supports("sse");
++ pll_hardware->sse2_present= __builtin_cpu_supports("sse2");
++ pll_hardware->sse3_present= __builtin_cpu_supports("sse3");
++ pll_hardware->ssse3_present = __builtin_cpu_supports("ssse3");
++ pll_hardware->sse41_present = __builtin_cpu_supports("sse4.1");
++ pll_hardware->sse42_present = __builtin_cpu_supports("sse4.2");
++ pll_hardware->popcnt_present = __builtin_cpu_supports("popcnt");
++ pll_hardware->avx_present = __builtin_cpu_supports("avx");
++ pll_hardware->avx2_present= __builtin_cpu_supports("avx2");
+ #endif
+ }
+
diff -Nru libpll-0.3.0/debian/patches/series libpll-0.3.0/debian/patches/series
--- libpll-0.3.0/debian/patches/series 2017-05-15 08:19:35.0 +0100
+++ libpll-0.3.0/debian/patches/series 2017-05-16 11:45:20.0 +0100
@@ -1 +1,2 @@
have_x86intrin_h.patch
+hardware-detect.patch
diff -Nru libpll-0.3.0/debian/rules libpll-0.3.0/debian/rules
--- libpll-0.3.0/debian/rules 2017-05-15 08:19:35.0 +0100
+++ libpll-0.3.0/debian/rules 2017-05-16 11:45:26.0 +0100
@@ -2,19 +2,18 @@
# DH_VERBOSE := 1
+include /usr/share/dpkg/architecture.mk
+
export DEB_BUILD_MAINT_OPTIONS = hardening=+all
%:
dh $@
override_dh_auto_configure:
- ./autogen.sh
-ifeq ($(DEB_BUILD_ARCH),i386)
- ./autogen.sh --disable-avx --disable-sse
- dh_auto_configure -- --disable-avx --disable-sse
+ifneq ($(filter $(DEB_HOST_ARCH_CPU), amd64 i386),)
+ dh_auto_configure
else
- ./autogen.sh --disable-avx
- dh_auto_configure -- --disable-avx
+ dh_auto_configure -- --disable-sse --disable-avx --disable-avx2
endif
override_dh_install:
signature.asc
Description: OpenPGP digital signature
Bug#862749: RFS: python-mechanicalsoup/0.7.0-1
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for the following package: * Package name: python-mechanicalsoup Version : 0.7.0 Upstream Author : Mirth Hickford * URL : https://github.com/hickford/MechanicalSoup * License : Expat Section : python One can check out the package by visiting the following URL: https://anonscm.debian.org/git/python-modules/packages/python-mechanicalsoup.git Changes since last upload: * Swith from git-dpm to gbp - Drop git-dpm configuration - Add gbp configuration * Fix typo in watch regex * Fixup Vcs-Browser URI * New upstream version 0.7.0 * Bump minimum Py3 version to 3.3 * Exclude egg-info directory via extend-diff-ignore * Add DEP-8 tests, drop superfluous Testsuite field Best regards, Ghis
Bug#862711: closed by Gianfranco Costamagna (Re: Bug#862711: RFS: dirty.js/1.0.0-1.1 [NMU] [RC])
Thanks Gianfranco! :)
Bug#861805: RFS: golang-github-puerkitobio-goquery/1.1.0+git20170324.3.ed7d758-1 [ITP]
Thanks for reviewing and for the notice, Gianfranco! I have revised the license of that html file (plus another file on the same directory that seemed to be under a different license as well), and pushed to git, tagged, and uploaded a new version in mentors (1.1.0+git20170324.3.ed7d758-2). Best regards, and thanks again, On 15/05/2017, Gianfranco Costamagna wrote: > control: owner -1 ! > control: tags -1 moreinfo > > ./testdata/gowiki.html > > this seems to have a different license. > > G. > > > > Il Giovedì 4 Maggio 2017 11:09, Diego M. Rodriguez > ha scritto: > > > > > > > Package: sponsorship-requests > > Severity: wishlist > > > Dear mentors, > > > I am looking for a sponsor for my package > "golang-github-puerkitobio-goquery" > > > * Package name: golang-github-puerkitobio-goquery > >Version : 1.1.0+git20170324.3.ed7d758-1 > >Upstream Author : Martin Angers > > * URL : https://github.com/PuerkitoBio/goquery > > * License : BSD-3-clause > >Section : devel > > > It builds those binary packages: > > > golang-github-puerkitobio-goquery-dev - jQuery-style HTML manipulation > in Go > > > To access further information about this package, please visit the > following URL: > > > https://mentors.debian.net/package/golang-github-puerkitobio-goquery > > > > Alternatively, one can download the package with dget using this command: > > > dget -x > https://mentors.debian.net/debian/pool/main/g/golang-github-puerkitobio-goquery/golang-github-puerkitobio-goquery_1.1.0+git20170324.3.ed7d758-1.dsc > > > Or on the following repository: > > > https://anonscm.debian.org/cgit/pkg-go/packages/golang-github-puerkitobio-goquery.git > > > > Changes since the last upload: > > > * Initial release (Closes: #858359) > > > Regards, > >Diego M. Rodriguez >
Bug#862763: atomic/1.17.1-1 [ITP] -- Atomic Run Tool for installing/running/managing container images
Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package "atomic" * Package name: atomic Version : 1.7.1-1 Upstream Author : Atomic Project * URL : https://github.com/projectatomic/atomic * License : GPL-2+ Programming Lang: Python Section : admin Description : Atomic Run Tool for installing/running/managing container images It builds those binary packages: atomic: allows an image provider to specify how a container image expects to be run atomic-doc: various documentations and concepts behind atomic To access further information about this package, please visit the following URL: https://mentors.debian.net/package/atomic Alternatively, one can download the package with dget using this command: dget -x https//mentors.debian.net/debian/pool/main/a/atomic/atomic_1.7.1-1.dsc This project defines the entrypoint for Project Atomic hosts. On an Atomic Host, there are at least two distinct software delivery vehicles; Docker (often used in combination with the traditional RPM/yum/dnf), and rpm-ostree to provide atomic upgrades of the host system. The goal of Atomic is to provide a high level, coherent entrypoint to the system, and fill in gaps in Linux container implementations. For Docker, |atomic| can make it easier to interact with special kinds of containers, such as super-privileged debugging tools and the like. atomic host does not support Debian-based OS by now (limited to rpm-based OS). Yet it permit to easily install/uninstall docker container into the system. Regards, -- Philippe THIERRY
Bug#862797: RFS: atomic/1.17.1-1 [ITP] -- Atomic Run Tool for installing/running/managing container images
Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package "atomic" * Package name : atomic Version : 1.7.1-1 Upstream Author : Atomic Project * URL : https://github.com/projectatomic/atomic [1] * License : GPL-2+ Programming Lang: Python Section : admin Description : Atomic Run Tool for installing/running/managing container images It builds those binary packages: atomic: allows an image provider to specify how a container image expects to be run atomic-doc: various documentations and concepts behind atomic To access further information about this package, please visit the following URL: https://mentors.debian.net/package/atomic [2] Alternatively, one can download the package with dget using this command: dget -x https//mentors.debian.net/debian/pool/main/a/atomic/atomic_1.7.1-1.dsc This project defines the entrypoint for Project Atomic hosts. On an Atomic Host, there are at least two distinct software delivery vehicles; Docker (often used in combination with the traditional RPM/yum/dnf), and rpm-ostree to provide atomic upgrades of the host system. The goal of Atomic is to provide a high level, coherent entrypoint to the system, and fill in gaps in Linux container implementations. For Docker, atomic can make it easier to interact with special kinds of containers, such as super-privileged debugging tools and the like. atomic host does not support Debian-based OS by now (limited to rpm-based OS). Yet it permit to easily install/uninstall docker container into the system. If integrated, this package can be used by openscap-daemon (already in sid and one of the packages i maintain) to instanciate docker container hosting openscap service. Regards, -- Philippe THIERRY Links: -- [1] https://github.com/projectatomic/atomic [2] https://mentors.debian.net/package/atomic
