Processed: forwarded upstream
Processing commands for cont...@bugs.debian.org: > forwarded 861515 https://github.com/gruntjs/grunt-contrib-copy/issues/291 Bug #861515 [src:node-grunt-contrib-copy] src:node-grunt-contrib-copy: FTBFS on armhf i386: test failure: ✖ copy - timestamp_equal Set Bug forwarded-to-address to 'https://github.com/gruntjs/grunt-contrib-copy/issues/291'. > End of message, stopping processing here. Please contact me if you need assistance. -- 861515: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861515 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#859635: marked as done (php-horde-crypt: CVE-2017-7413 CVE-2017-7414)
Your message dated Wed, 03 May 2017 05:48:26 +
with message-id
and subject line Bug#859635: fixed in php-horde-crypt 2.7.5-2
has caused the Debian Bug report #859635,
regarding php-horde-crypt: CVE-2017-7413 CVE-2017-7414
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.)
--
859635: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859635
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: php-horde-crypt
Version: 2.7.5-1
Severity: grave
Tags: security upstream
Justification: user security hole
Hi,
the following vulnerabilities were published for php-horde-crypt.
CVE-2017-7413[0]:
| In Horde_Crypt before 2.7.6, as used in Horde Groupware Webmail Edition
| through 5.2.17, OS Command Injection can occur if the attacker is an
| authenticated Horde Webmail user, has PGP features enabled in their
| preferences, and attempts to encrypt an email addressed to a
| maliciously crafted email address.
CVE-2017-7414[1]:
| In Horde_Crypt before 2.7.6, as used in Horde Groupware Webmail Edition
| 5.x through 5.2.17, OS Command Injection can occur if the user has PGP
| features enabled in the user's preferences, and has enabled the "Should
| PGP signed messages be automatically verified when viewed?" preference.
| To exploit this vulnerability, an attacker can send a PGP signed email
| (that is maliciously crafted) to the Horde user, who then must either
| view or preview it.
If you fix the vulnerabilities please also make sure to include the
CVE (Common Vulnerabilities & Exposures) ids in your changelog entry.
For further information see:
[0] https://security-tracker.debian.org/tracker/CVE-2017-7413
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-7413
[1] https://security-tracker.debian.org/tracker/CVE-2017-7414
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-7414
Please adjust the affected versions in the BTS as needed.
Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: php-horde-crypt
Source-Version: 2.7.5-2
We believe that the bug you reported is fixed in the latest version of
php-horde-crypt, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 859...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Mathieu Parent (supplier of updated php-horde-crypt
package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Wed, 03 May 2017 07:15:32 +0200
Source: php-horde-crypt
Binary: php-horde-crypt
Architecture: source all
Version: 2.7.5-2
Distribution: unstable
Urgency: medium
Maintainer: Horde Maintainers
Changed-By: Mathieu Parent
Description:
php-horde-crypt - ${phppear:summary}
Closes: 859635
Changes:
php-horde-crypt (2.7.5-2) unstable; urgency=medium
.
* Escape user provided recipients and charset data. Fixes CVE-2017-7413 and
CVE-2017-7414 (Closes: #859635)
Checksums-Sha1:
6440ba3bbe64b6c7fe3a27a036535c6732d8525a 2113 php-horde-crypt_2.7.5-2.dsc
c997ede496d161dd5ea7723620f204dca6b0d6a7 3516
php-horde-crypt_2.7.5-2.debian.tar.xz
08dc3d3d3380cc23c25633eaf54ca27c243320e7 111882 php-horde-crypt_2.7.5-2_all.deb
215cc74074f098742812c0cc22374fd19b808b47 6225
php-horde-crypt_2.7.5-2_amd64.buildinfo
Checksums-Sha256:
8f98db7d046de2ed8b0f4372e074d6d1de9fd1e64ddf940021f787816bf01c85 2113
php-horde-crypt_2.7.5-2.dsc
7d8f0be8e7aa45d5f6fe2a0a1bf47c525a1593098cfa893db4bb4e53ae6e41f0 3516
php-horde-crypt_2.7.5-2.debian.tar.xz
85f4eedea48712e8c878454a3d1fbcbd9869c22887ca4c8bdf7f516ad8b3938b 111882
php-horde-crypt_2.7.5-2_all.deb
389d9c679971c780ed9b0c1bc382c5d222eeb2231e193851605e4fdfcce8e4bc 6225
php-horde-crypt_2.7.5-2_amd64.buildinfo
Files:
39dc9ebd1654a6f8e7f57743dc4e03f1 2113 php extra php-horde-crypt_2.7.5-2.dsc
693d7743709c91d5f0a0ca693d467f8d 3516 php extra
php-horde-crypt_2.7.5-2.debian.tar.xz
6ce6614c053bee5891b51b9e51a38c14 111882 php extra
php-horde-crypt_2.7.5-2_all.deb
01d61d04a68b34c9555029f3d8167b42 6225 php extra
php-horde-crypt_2.7.5-2_amd64.buildinfo
-BEGIN PGP SIGNATURE-
iQJHBAEBCAAxFiEEqIGbPTP9weQZ135HrgOYBGZoH6UFAlkJanUTHHNhdGhpZXVA
ZGViaWFuLm9yZwAKCRCuA5gEZmgfpc31D/94r9BScMKPvOdb8wuMRzH5y17IQHBR
n/qicGLLtaMBPcsat98CSVDv+
Bug#861575: tilix: Does not start on Stretch (symbol lookup error: undefined symbol)
On Sun, Apr 30, 2017 at 06:43:18PM -0400, Mathieu Basille wrote: > Following the name change from terminix to tilix, I updated > my Stretch system (which uses apt pining to install Sid > packages whenever possible) to use the new developments of > tilix. > > Install of v1.5.4-1 works without any problem, but I'm unable > to run tilix: > > tilix: symbol lookup error: tilix: undefined symbol: > > _D7gobject7ObjectG7ObjectG11addOnNotifyMFDFC7gobject9ParamSpec9ParamSpecC7gobject7ObjectG7ObjectGZvAyaE4gtkc12gobjecttypes13GConnectFlagsZm ... > > Versions of packages tilix depends on: > ii dconf-gsettings-backend [gsettings-backend] 0.26.0-2+b1 > ii libc62.24-10 > ii libgtkd-3-0 3.3.1-2 > ii libphobos2-ldc71 1:1.1.1-1 > ii libvted-3-0 3.3.1-2 > ii libx11-6 2:1.6.4-3 > ii tilix-common 1.5.4-1 tilix seems to require libgtkd-3-0 >= 3.5.1-1 and should have its Depends increased.
Bug#861711: buildd.debian.org: Architecture: all B-D confusion
Package: buildd.debian.org Severity: serious Justification: makes some packages fail to build from source Per https://buildd.debian.org/status/package.php?p=gsequencer&suite=sid , gsequencer shows up as BD-Uninstallable for Architecture: all with the explanation gsequencer build-depends on missing: - liboss4-salsa-dev:amd64 gsequencer specifies an appropriate architecture restriction here: Build-Depends: debhelper (>= 10), autotools-dev, dh-autoreconf, pkg-config, libcunit1-dev, libgtk2.0-dev, libcairo2-dev, xvfb, xauth, libx11-dev, libinstpatch-dev, libsndfile1-dev, libsamplerate-dev, libxml2-dev, ladspa-sdk, dssi-dev, lv2-dev, libgmp-dev, libasound2-dev [linux-any], liboss4-salsa-dev [!linux-any], oss4-dev [kfreebsd-any], libjack-dev, uuid-dev, docbook-xsl, docbook-xml, gtk-doc-tools, xsltproc Its maintainers could probably stand to split out B-D-Arch and B-D-Indep settings, but my understanding is that the Architecture: all build should have been able to proceed regardless; it certainly did in the past. Could you please take a look? Thanks! -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu
Bug#852261: proposed fix upstream
There is a proposed fix from upstream: https://github.com/boothj5/profanity/commit/3e18aab9f38fad3cd971ec09684f7e03f299cc87 This commit worked for me on armhf, but it should fix it also for all the other architecture. -- Diego Roversi
Processed: Re: Bug#861497: gcc-6-cross: FTBFS in stretch
Processing control commands: > severity -1 minor Bug #861497 [src:gcc-6-cross] gcc-6-cross: FTBFS in stretch Severity set to 'minor' from 'serious' > tags -1 + moreinfo Bug #861497 [src:gcc-6-cross] gcc-6-cross: FTBFS in stretch Added tag(s) moreinfo. -- 861497: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861497 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#861497: gcc-6-cross: FTBFS in stretch
Control: severity -1 minor Control: tags -1 + moreinfo On 29.04.2017 19:53, Santiago Vila wrote: > Package: src:gcc-6-cross > Version: 21 > Severity: serious > > Dear maintainer: > > I tried to build this package in stretch with "dpkg-buildpackage -A" > but it failed: fine, but you should make sure that this occurs in a distro environment as well. [unchecked tail of build log omitted] > This is just how the build ends, not necessarily the relevant part. sure, this is not the relevant part. > I've put the full build log here: > > https://people.debian.org/~sanvila/build-logs/gcc-6-cross/ for future reports, please could you keep a list of packages to check manually for the errors? I tried to rebuild the package, and I couldn't even reproduce this one. > I've also triggered a rebuild (for testing/amd64) in the reproducible builds > autobuilders and it also fails: > > https://tests.reproducible-builds.org/debian/rb-pkg/testing/amd64/gcc-6-cross.html completely unrelated. please check your scripts for automated bug reports, or check that the reason for the build failure really is the same. Thanks, Matthias PS: gcc-6-cross_22 was successfully built on the buildds.
Bug#861605: Treating similar bugs similarly
severity 534058 important severity 861605 important reopen 861605 thanks
Processed: Treating similar bugs similarly
Processing commands for cont...@bugs.debian.org:
> severity 534058 important
Bug #534058 [pixbros] pixbros: FTBFS on amd64: build-depends not available
Severity set to 'important' from 'normal'
> severity 861605 important
Bug #861605 {Done: Julien Cristau } [src:pixfrogger]
pixfrogger: FTBFS on amd64
Severity set to 'important' from 'serious'
> reopen 861605
Bug #861605 {Done: Julien Cristau } [src:pixfrogger]
pixfrogger: FTBFS on amd64
Bug reopened
Ignoring request to alter fixed versions of bug #861605 to the same values
previously set
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
534058: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=534058
861605: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861605
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#860805: marked as done (beignet-opencl-icd: OpenCL fails with: drm_intel_gem_bo_context_exec() failed: Device or resource busy)
Your message dated Tue, 02 May 2017 23:18:32 + with message-id and subject line Bug#860805: fixed in beignet 1.3.0-3 has caused the Debian Bug report #860805, regarding beignet-opencl-icd: OpenCL fails with: drm_intel_gem_bo_context_exec() failed: Device or resource busy 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.) -- 860805: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860805 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: beignet-opencl-icd Version: 1.3.0-2+b1 Severity: normal Dear Maintainer, running any opencl-using program (such as clinfo or osmocom_fft -F) does not work but produces: drm_intel_gem_bo_context_exec() failed: Device or resource busy Beignet: "Exec event 0x55bc572926b0 error, type is 4592, error staus is -5" This is on a Lenovo Thinkpad T440s with an Intel HD Graphics 4400. Rebuilding beignet-opencl-icd with the following upstream-patch fixes the problem and leads to working OpenCL: https://cgit.freedesktop.org/beignet/commit/?id=8b04f0be372da8eabdc93d6ae1b81a3c83cba284 Cheers, Michael -- Package-specific info: Graphics hardware: Providers: number : 1 Provider 0: id: 0x49 cap: 0xb, Source Output, Sink Output, Sink Offload crtcs: 4 outputs: 6 associated providers: 0 name:Intel server glx vendor string: SGI client glx vendor string: Mesa Project and SGI Extended renderer info (GLX_MESA_query_renderer): OpenGL vendor string: Intel Open Source Technology Center OpenGL renderer string: Mesa DRI Intel(R) Haswell Mobile 00:02.0 VGA compatible controller [0300]: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) 04:00.0 VGA compatible controller [0300]: NVIDIA Corporation GK208M [GeForce GT 730M] [10de:1290] (rev a1) Processor: Architecture: x86_64 CPU op-mode(s):32-bit, 64-bit Byte Order:Little Endian CPU(s):4 On-line CPU(s) list: 0-3 Thread(s) per core:2 Core(s) per socket:2 Socket(s): 1 NUMA node(s): 1 Vendor ID: GenuineIntel CPU family:6 Model: 69 Model name:Intel(R) Core(TM) i5-4300U CPU @ 1.90GHz Stepping: 1 CPU MHz: 2606.964 CPU max MHz: 2900. CPU min MHz: 800. BogoMIPS: 4988.37 Virtualization:VT-x L1d cache: 32K L1i cache: 32K L2 cache: 256K L3 cache: 3072K NUMA node0 CPU(s): 0-3 Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm epb tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid xsaveopt dtherm ida arat pln pts OpenCL library: rc amd-libopencl1:amd641:15.9-4~deb8u1 un libopencl-1.1-1 un libopencl-1.2-1 un libopencl-2.0-1 un libopencl-2.1-1 un libopencl1 rc nvidia-libopencl1:amd64 340.96-1 un nvidia-libopencl1-dev un nvidia-libopencl1-ia32 ii ocl-icd-libopencl1:amd642.2.11-1 ii ocl-icd-libopencl1:i386 2.2.11-1 ii amd-opencl-icd:amd641:15.9-4~deb8u2 un amd-opencl-icd-ia32 un amd-opencl-icd-virtual ii beignet-opencl-icd:amd641.3.0-2+b1 rc mesa-opencl-icd 10.3.2-1+deb8u1 un nvidia-opencl-icd un opencl-icd ==> /etc/OpenCL/vendors/amdocl64.icd <== libamdocl64.so ==> /etc/OpenCL/vendors/intel-beignet-x86_64-linux-gnu.icd <== /usr/lib/x86_64-linux-gnu/beignet//libcl.so ==> /etc/OpenCL/vendors/mesa.icd <== libMesaOpenCL.so ==> /etc/OpenCL/vendors/nvidia.icd <== libnvidia-opencl.so.1 -- System Information: Debian Release: 9.0 APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=C, LC_CTYPE=de_DE@euro (charmap=ISO-8859-15) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages beignet-opencl-icd depends on: ii libc6 2.24-9 ii libdrm-intel1 2.4.74-1 ii libdrm22.4.74-1 ii libgcc11:6.3.0-12 ii libstdc++6 6.3.0-12 ii libtinfo5 6.0+20161126-1 ii libx11-6 2:1.6.4-3 ii libxext6
Bug#860805: Could we set bug #860805 against beignet-opencl-icd to stretch-is-blocker?
On 2017-05-03 00:31, Rebecca N. Palmer wrote: > Someone please upload beignet (as currently in Alioth); I'll file an > unblock request. Upload is on its way. You can probably wait a few days with the unblock request, the release-team will probably pick up the upload fixing an RC bug on their own. Andreas
Bug#860805: [Pkg-opencl-devel] Bug#860805: Bug#860805: Could we set bug #860805 against beignet-opencl-icd to stretch-is-blocker?
Control: tags -1 pending The above looks like success - thanks. Someone please upload beignet (as currently in Alioth); I'll file an unblock request.
Processed: Re: [Pkg-opencl-devel] Bug#860805: Bug#860805: Could we set bug #860805 against beignet-opencl-icd to stretch-is-blocker?
Processing control commands: > tags -1 pending Bug #860805 [beignet-opencl-icd] beignet-opencl-icd: OpenCL fails with: drm_intel_gem_bo_context_exec() failed: Device or resource busy Added tag(s) pending. -- 860805: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860805 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#861431: restic: Rebuild needed for CVE-2017-3204; #859655
> It's built happily on ppc64el for the archive, so please either close this > bug or leave the fixed version in place (by all means keep it open if you > want to explore possible resource exhaustion on other machines). I haven't had a chance to re-test this build. If it's building fine for the archive, that's good enough for me. I might do some rebuild testing down the road, but I think it makes more sense to close now and re-open only if issues are found.
Bug#860703: marked as done (golang-github-jacobsa-fuse: FTBFS on i386: dh_auto_build: go install -v -p 1 github.com/jacobsa/fuse github.com/jacobsa/fuse/fsutil github.com/jacobsa/fuse/fuseops github.c
Your message dated Tue, 02 May 2017 21:49:04 + with message-id and subject line Bug#860703: fixed in golang-github-jacobsa-fuse 0.0~git20150806.0.9a7512a-2 has caused the Debian Bug report #860703, regarding golang-github-jacobsa-fuse: FTBFS on i386: dh_auto_build: go install -v -p 1 github.com/jacobsa/fuse github.com/jacobsa/fuse/fsutil github.com/jacobsa/fuse/fuseops github.com/jacobsa/fuse/fusetesting github.com/jacobsa/fuse/fuseutil github.com/jacobsa/fuse/internal/buffer github.com/jacobsa/fuse/internal/freelist github.com/jacobsa/fuse/internal/fusekernel returned exit code 2 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.) -- 860703: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860703 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: golang-github-jacobsa-fuse Version: 0.0~git20150806.0.9a7512a-1 Severity: serious Tags: stretch sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20170418-i386 qa-ftbfs Justification: FTBFS in stretch on i386 Hi, During a rebuild of all packages in stretch (in a stretch chroot, not a sid chroot), your package failed to build on i386. Relevant part (hopefully): > debian/rules build > dh build --buildsystem=golang --with=golang >dh_testdir -O--buildsystem=golang >dh_update_autotools_config -O--buildsystem=golang >dh_auto_configure -O--buildsystem=golang >dh_auto_build -O--buildsystem=golang > go install -v -p 1 github.com/jacobsa/fuse > github.com/jacobsa/fuse/fsutil github.com/jacobsa/fuse/fuseops > github.com/jacobsa/fuse/fusetesting github.com/jacobsa/fuse/fuseutil > github.com/jacobsa/fuse/internal/buffer > github.com/jacobsa/fuse/internal/freelist > github.com/jacobsa/fuse/internal/fusekernel > github.com/jacobsa/fuse/internal/fusekernel > github.com/jacobsa/fuse/fuseops > github.com/jacobsa/fuse/internal/buffer > # github.com/jacobsa/fuse/internal/buffer > src/github.com/jacobsa/fuse/internal/buffer/runtime.go:22: missing function > body for "memclr" > src/github.com/jacobsa/fuse/internal/buffer/runtime.go:27: missing function > body for "memmove" > github.com/jacobsa/fuse/internal/freelist > golang.org/x/net/context > github.com/jacobsa/fuse/fsutil > github.com/jacobsa/oglematchers > github.com/jacobsa/oglemock > github.com/jacobsa/ogletest/srcutil > github.com/jacobsa/reqtrace > github.com/jacobsa/ogletest > github.com/jacobsa/syncutil > github.com/jacobsa/fuse/fusetesting > # github.com/jacobsa/fuse/fusetesting > src/github.com/jacobsa/fuse/fusetesting/stat_linux.go:33: cannot use > sys.(*syscall.Stat_t).Nlink (type uint32) as type uint64 in assignment > dh_auto_build: go install -v -p 1 github.com/jacobsa/fuse > github.com/jacobsa/fuse/fsutil github.com/jacobsa/fuse/fuseops > github.com/jacobsa/fuse/fusetesting github.com/jacobsa/fuse/fuseutil > github.com/jacobsa/fuse/internal/buffer > github.com/jacobsa/fuse/internal/freelist > github.com/jacobsa/fuse/internal/fusekernel returned exit code 2 > debian/rules:7: recipe for target 'build' failed > make: *** [build] Error 2 The full build log is available from: http://aws-logs.debian.net/2017/04/18/golang-github-jacobsa-fuse_0.0~git20150806.0.9a7512a-1_testing-i386.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. --- End Message --- --- Begin Message --- Source: golang-github-jacobsa-fuse Source-Version: 0.0~git20150806.0.9a7512a-2 We believe that the bug you reported is fixed in the latest version of golang-github-jacobsa-fuse, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 860...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Roger Shimizu (supplier of updated golang-github-jacobsa-fuse package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 03 May 2017 00:28:03 +0900 Source: golang-github-jacobsa-fuse Binary: golang-github-ja
Bug#861467: marked as done (dput-ng: FTBFS (failing tests))
Your message dated Tue, 02 May 2017 21:34:11 +
with message-id
and subject line Bug#861467: fixed in dput-ng 1.12
has caused the Debian Bug report #861467,
regarding dput-ng: FTBFS (failing tests)
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.)
--
861467: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861467
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:dput-ng
Version: 1.11
Severity: serious
Dear maintainer:
I tried to build this package in stretch with "dpkg-buildpackage -A"
but it failed:
[...]
debian/rules build-indep
dh build-indep --with bash-completion,python2,sphinxdoc
dh_testdir -i
dh_update_autotools_config -i
dh_autoreconf -i
dh_auto_configure -i
debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
dh_auto_build
python setup.py build --force
running build
running build_py
creating build
creating build/lib.linux-x86_64-2.7
[... snipped ...]
dput.py7 0 100%
dput/changes.py 129 5557% 78, 84, 87, 91, 96,
139, 158, 164, 176-178, 184-188, 194, 217, 225, 232-236, 245-281, 302-309, 315,
327
dput/command.py 13711020% 47-49, 53, 57, 61, 65,
69, 73, 77-91, 96-125, 129-167, 171-176, 180-256
dput/commands.py 0 0 100%
dput/commands/contrib.py 0 0 100%
dput/config.py18 572% 49, 57, 66, 73, 80
dput/configs.py0 0 100%
dput/configs/dputcf.py71 2170% 28, 50, 58-68, 82-83,
108-112, 117-118, 123-124, 127-128, 141
dput/configs/dputng.py50 492% 40, 105-106, 117
dput/core.py 57 2163% 88, 95-103, 118-123,
126-131
dput/exceptions.py21 0 100%
dput/hook.py 32 681% 41, 56-58, 62-64
dput/hooks.py 0 0 100%
dput/hooks/checksum.py 9 278% 54-55
dput/hooks/deb.py 36 1072% 67-68, 74, 78-84, 91,
94, 98
dput/hooks/distribution.py65 4925% 66-106, 122-149,
169-181
dput/hooks/distro_info_checks.py 37 1170% 27-30, 62, 72, 74-79,
85, 90
dput/interface.py 35 1654% 65, 74-77, 85-87,
94-96, 102-104, 113, 120
dput/interfaces.py 0 0 100%
dput/interfaces/cli.py65 4925% 47-50, 62-78, 85-104,
110-113, 119-121, 127-136
dput/logger.py 7 0 100%
dput/overrides.py 9 544% 35-41, 50-51
dput/profile.py 148 3278% 128, 152-156, 187-188,
199-212, 221-227, 232-236, 283
dput/uploader.py 152 7749% 51-62, 65, 68, 71-88,
97, 107, 121, 128, 135, 153-177, 197, 207, 227, 239, 278, 287, 291, 294, 297,
300, 314-358
dput/uploaders.py 0 0 100%
dput/util.py 185 4775% 67-70, 75-77, 95-97,
124-130, 134, 141, 161-163, 172-173, 185-186, 192-193, 199, 254-255, 260-263,
297-310, 317-322, 333, 343
TOTAL 127052059%
--
Ran 6 tests in 5.281s
FAILED (errors=2)
{'foo': [['bar']]}
{'foo': [None]}
{'+foo': [['bar']]}
{'foo': [None, ['1']]}
{'foo': {'bar': {'baz': [['paultag.is.a.god']]}}}
{'foo': {'bar': [['1'], ['2'], ['3']]}, 'foo2': [['4']]}
{'foo': {'bar': [['True=True'], ['foo=False', 'obj2']]}, 'foo2': [['bar']]}
debian/rules:19: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1
make[1]: Leaving directory '/<>'
debian/rules:8: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2
The failure happens every time in all my autobuilders, and it also happens here:
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/dput-ng.html
Thanks.
--- End Message ---
--- Begin Message ---
Source: dput-ng
Source-Version: 1.12
We believe that the bug you reported is fixed in the latest version of
dput-ng, which is due to be installed in the Debian FTP archive.
A summ
Bug#861486: [Pkg-julia-devel] Bug#861486: Bug#861486: Bug#861486: julia: FTBFS on mips64el (segmentation fault)
On 2 May 2017 at 18:58, Peter Colberg wrote:
> Could you comment all lines and then successively uncomment to see
> which line triggers the segfault?
I commented out practically your entire program and it still randomly segfaults.
> You could also try querying a symbol in libm other than pow and see
> whether that changes anything.
No difference with 'exp' or 'SuiteSparse_config'. I also tried
replacing -lopenlibm with -lm.
I am able to reproduce the problem with the files below. Julia's
build-dependencies are still required, but not Julia's source.
Contents of shlibdeps.c:
int main(void)
{
return 0;
}
Contents of Makefile:
SHLIBDEPS+=-larpack
SHLIBDEPS+=-lopenblas
SHLIBDEPS+=-ldSFMT
SHLIBDEPS+=-lfftw3_threads
SHLIBDEPS+=-lfftw3f_threads
SHLIBDEPS+=-lgmp
SHLIBDEPS+=-lopenlibm
SHLIBDEPS+=-lmpfr
SHLIBDEPS+=-lopenspecfun
SHLIBDEPS+=-lpcre2-8
SHLIBDEPS+=-lcholmod
SHLIBDEPS+=-lspqr
SHLIBDEPS+=-lsuitesparseconfig
SHLIBDEPS+=-lumfpack
shlibdeps: shlibdeps.c
gcc -o shlibdeps shlibdeps.c -ldl $(SHLIBDEPS)
test: shlibdeps
for n in $(shell seq 1 30); do ./shlibdeps; done
$ make test
for n in 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23
24 25 26 27 28 29 30; do ./shlibdeps; done
Segmentation fault
Segmentation fault
Segmentation fault
Segmentation fault
Bug#860463: nodm: Missing handling of plymouth
On Tue, 02 May 2017 at 08:00:44 +0100, Simon McVittie wrote: > On Tue, 02 May 2017 at 01:38:15 +0200, Axel Beckert wrote: > > JFTR: This needs an "|| true" if your init script uses "set -e", > > otherwise starting or restarting the DM besides a fresh system bootup > > might fail. > > Oh, good point. I should change that for nodm. I've done a 0-day NMU of nodm with the attached diff to fix this mistake in my earlier NMU; I hope the nodm maintainers don't mind. Thanks to Axel Beckert for pointing this out. S diffstat for nodm-0.13 nodm-0.13 changelog |8 nodm.init |2 +- 2 files changed, 9 insertions(+), 1 deletion(-) diff -Nru nodm-0.13/debian/changelog nodm-0.13/debian/changelog --- nodm-0.13/debian/changelog 2017-04-27 18:37:16.0 +0100 +++ nodm-0.13/debian/changelog 2017-05-02 21:57:24.0 +0100 @@ -1,3 +1,11 @@ +nodm (0.13-1.2) unstable; urgency=medium + + * Non-maintainer upload + * nodm.init: Do not fail to start if plymouth has already been +stopped + + -- Simon McVittie Tue, 02 May 2017 21:57:24 +0100 + nodm (0.13-1.1) unstable; urgency=medium * d/p/nodm.service-Ask-Plymouth-to-stop-before-starting-no.patch: diff -Nru nodm-0.13/debian/nodm.init nodm-0.13/debian/nodm.init --- nodm-0.13/debian/nodm.init 2017-04-27 18:37:16.0 +0100 +++ nodm-0.13/debian/nodm.init 2017-05-02 21:57:24.0 +0100 @@ -52,7 +52,7 @@ case "$1" in start) if [ -x /bin/plymouth ]; then - /bin/plymouth quit + /bin/plymouth quit || true fi [ "$VERBOSE" != no ] && log_daemon_msg "Starting $DESC" "$NAME" if [ "$NODM_ENABLED" = "no" ] || [ "$NODM_ENABLED" = "false" ]
Bug#861682: marked as done (libpoco-dev: missing Depends on libssl-dev)
Your message dated Tue, 02 May 2017 21:07:03 + with message-id and subject line Bug#861682: fixed in poco 1.7.6+dfsg1-5 has caused the Debian Bug report #861682, regarding libpoco-dev: missing Depends on libssl-dev 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.) -- 861682: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861682 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libpoco-dev Version: 1.7.6+dfsg1-4 Severity: serious Dear Maintainer, In file included from /usr/include/Poco/Crypto/X509Certificate.h:24:0, from /usr/include/Poco/Net/Context.h:25, from /usr/include/Poco/Net/SecureServerSocket.h:25, from wsd/Admin.cpp:23: /usr/include/Poco/Crypto/OpenSSLInitializer.h:26:28: fatal error: openssl/crypto.h: No such file or directory #include ^ compilation terminated. If Poco/Net/SecureServerSocket.h needs libssl-dev (via said Poco/Crypto/OpenSSLInitializer.h), it should depend on it. Regards, RenePackage: libpoco-dev Version: 1.7.6+dfsg1-4 Severity: serious Dear Maintainer, In file included from /usr/include/Poco/Crypto/X509Certificate.h:24:0, from /usr/include/Poco/Net/Context.h:25, from /usr/include/Poco/Net/SecureServerSocket.h:25, from wsd/Admin.cpp:23: /usr/include/Poco/Crypto/OpenSSLInitializer.h:26:28: fatal error: openssl/crypto.h: No such file or directory #include ^ compilation terminated. If Poco/Net/SecureServerSocket.h needs libssl-dev (via said Poco/Crypto/OpenSSLInitializer.h), it should depend on it. Regards, Rene --- End Message --- --- Begin Message --- Source: poco Source-Version: 1.7.6+dfsg1-5 We believe that the bug you reported is fixed in the latest version of poco, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 861...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jochen Sprickerhof (supplier of updated poco package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 02 May 2017 22:00:07 +0200 Source: poco Binary: libpoco-dev libpococrypto46 libpocodata46 libpocomongodb46 libpocodatamysql46 libpocodataodbc46 libpocodatasqlite46 libpocofoundation46 libpoconet46 libpoconetssl46 libpocoutil46 libpocoxml46 libpocozip46 Architecture: source Version: 1.7.6+dfsg1-5 Distribution: unstable Urgency: medium Maintainer: Krzysztof Burghardt Changed-By: Jochen Sprickerhof Description: libpoco-dev - C++ Portable Components (POCO) Development files libpococrypto46 - C++ Portable Components (POCO) Crypto library libpocodata46 - C++ Portable Components (POCO) Data library libpocodatamysql46 - C++ Portable Components (POCO) Data MySQL library libpocodataodbc46 - C++ Portable Components (POCO) ODBC library libpocodatasqlite46 - C++ Portable Components (POCO) Data SQLite library libpocofoundation46 - C++ Portable Components (POCO) Foundation library libpocomongodb46 - C++ Portable Components (POCO) Data MySQL library libpoconet46 - C++ Portable Components (POCO) Network library libpoconetssl46 - C++ Portable Components (POCO) Network library with SSL libpocoutil46 - C++ Portable Components (POCO) Util library libpocoxml46 - C++ Portable Components (POCO) XML library libpocozip46 - C++ Portable Components (POCO) Zip library Closes: 861682 Changes: poco (1.7.6+dfsg1-5) unstable; urgency=medium . * Add missing dependencies (Closes: #861682) Checksums-Sha1: 05da4dcf26af7befa955bf676e900b85a4f22855 2874 poco_1.7.6+dfsg1-5.dsc 4a8bcdb03b1406ae4ac04c8f672f1f47886860b7 14096 poco_1.7.6+dfsg1-5.debian.tar.xz 011c7133a2ccb79b8b562dbf0ef2346dd0990072 6517 poco_1.7.6+dfsg1-5_source.buildinfo Checksums-Sha256: 8555a6971bd20fc338ee5ad6d106891ecbbc7c1e5f73b9b9d600934cbd69ed91 2874 poco_1.7.6+dfsg1-5.dsc 8c3144b1f52552726f510d56a424ab6f46bee6cfb003b9966bf5d319a8d0f7e2 14096 poco_1.7.6+dfsg1-5.debian.tar.xz aa2acdeadf254a6a635b663b30fd4d11b116c4cc938911eb2039d32988c657e2 6517 poco_1.7.6+dfsg1-5_source.buildinfo Files: 317d187581ac2b19958802c8d18faae2 2874 libs optional poco_1.7.6+dfsg1-5.dsc
Bug#861690: marked as done (gerris: FTBFS - uses dh-exec without Build-Depends on it)
Your message dated Tue, 02 May 2017 21:05:12 + with message-id and subject line Bug#861690: fixed in gerris 20131206+dfsg-16 has caused the Debian Bug report #861690, regarding gerris: FTBFS - uses dh-exec without Build-Depends on it 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.) -- 861690: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861690 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gerris Version: 20131206+dfsg-15 Severity: serious Hi, The just uploaded version of gerris FTBFS as it uses dh-exec without Build-Depends on dh-exec. Thanks, ~Niels --- End Message --- --- Begin Message --- Source: gerris Source-Version: 20131206+dfsg-16 We believe that the bug you reported is fixed in the latest version of gerris, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 861...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Anton Gladky (supplier of updated gerris package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 02 May 2017 21:43:03 +0200 Source: gerris Binary: gerris libgfs-1.3-2 libgfs-dev Architecture: source Version: 20131206+dfsg-16 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Anton Gladky Description: gerris - Fluid Flow Solver libgfs-1.3-2 - Fluid Flow Solver -- shared libraries libgfs-dev - Fluid Flow Solver -- development libraries and headers Closes: 861690 Changes: gerris (20131206+dfsg-16) unstable; urgency=medium . * [719a48f] Add dh-exec as a build-depends. (Closes: #861690) Checksums-Sha1: 8d813d7715fce0fab1120189b5f40832bcba1ae3 2428 gerris_20131206+dfsg-16.dsc 5b401228b758afc35be9b62995937d5c8b46cd98 16732 gerris_20131206+dfsg-16.debian.tar.xz 8db95bd1b41a72f8150c236d7e9312f377bad8a7 8627 gerris_20131206+dfsg-16_source.buildinfo Checksums-Sha256: da0681fb900702a297a26d0f55220289b2788df0dc5d918fe744d07bd5dfa8c2 2428 gerris_20131206+dfsg-16.dsc 7c05bacfd21928be26ad399101880e8518166f3af799d31cc090d8df71df2036 16732 gerris_20131206+dfsg-16.debian.tar.xz c768bd5917e65c7362630426f722cc26fbdbf1a08072bd2d778e260eb5a57027 8627 gerris_20131206+dfsg-16_source.buildinfo Files: 2ea6291325c33b99d7084f678ef10124 2428 science optional gerris_20131206+dfsg-16.dsc 5130263166785fa05d76f63d284e633e 16732 science optional gerris_20131206+dfsg-16.debian.tar.xz 4b7a67f5dcdd45f04c89b4fe187baef5 8627 science optional gerris_20131206+dfsg-16_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEu71F6oGKuG/2fnKF0+Fzg8+n/wYFAlkI4oQACgkQ0+Fzg8+n /wY5Aw/9FYIu4KI2/Yb+T0HdYioJSZ06/cCw3U0wwVEGn4j9rhPTvum6I8DRFTnH NbDGKsTcpXj7J634SFMmfbtgJsWFDYpy3DspI7YdrXoZdYJOzjoLLuSHbHlh9KuG 7/5gJUmAm7NLtUjYImnDlVl7UDDKi7HXvc483eHFbj3k0OJnW2iKv7rXIrHYsm2v LPhgbRTgYCKBIXSlOQXEURIJAAmf+X2UtK7n+UTrs+zW6/WARXoY4uDGujM3iMud MdO4DfwVhyfZ25mWMbdjk3VC08yV1/FACu+RIml0Vh3aww8JY0hsDQgEbHmSh+FY zYWf9d7miBZ3k5Xn+0vVeHnRD18+uKZY3EOn06sUYNCxUyYkELu0pgZs/RzKCvbi owDDYqRsvdk+p28X6JlB165p2kGSF7tN3GCIVAFnZIBEHHteQORjt9anG0xV54O5 7KMbs1mw34xHw5wCe5DsgH8E+H/4z2wR/akU+4OIMbxRoT50iGwJzmQSeXOUoCdW RoiIofRu3998UTE40dK/I8rvaIkrLny5lwq8hQDOlqEHruhkccjMo9+8RhRIxZqc peysYs/Zwclw+NS9ZM5WixlT9QVBJQ/Ei0oo4al2pWrxvvendFClujj4cWwuiRhi zPZ8gGnq71TMdiCRIaT2x1c6A2p1QOrKTAyZXGgDZwEuGehgIgg= =VJR9 -END PGP SIGNATURE End Message ---
Bug#861431: restic: Rebuild needed for CVE-2017-3204; #859655
Control: found -1 0.3.3-1+b1 Control: fixed -1 0.3.3-1+b2 Hi, On Sun, Apr 30, 2017 at 12:51:03PM +0200, Félix Sipma wrote: > ppc64el rebuilding seems to give the same error as yours, though. > > Do you think we can close this bug, or associate it with ppc64el only? > > It may be an issue with insufficient ressources but I'm not sure, and I'm a > bit > out of idea on how to fix this... It's built happily on ppc64el for the archive, so please either close this bug or leave the fixed version in place (by all means keep it open if you want to explore possible resource exhaustion on other machines). Thanks, -- Jonathan Wiltshire j...@debian.org Debian Developer http://people.debian.org/~jmw 4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC 74C3 5394 479D D352 4C51
Processed: Re: Bug#861431: restic: Rebuild needed for CVE-2017-3204; #859655
Processing control commands: > found -1 0.3.3-1+b1 Bug #861431 [restic] restic: Rebuild needed for CVE-2017-3204; #859655 Marked as found in versions restic/0.3.3-1. > fixed -1 0.3.3-1+b2 Bug #861431 [restic] restic: Rebuild needed for CVE-2017-3204; #859655 Marked as fixed in versions restic/0.3.3-1. -- 861431: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861431 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#860805: [Pkg-opencl-devel] Bug#860805: Could we set bug #860805 against beignet-opencl-icd to stretch-is-blocker?
Hi, On Tue, May 02, 2017 at 07:40:43AM +0100, Rebecca N. Palmer wrote: > Has anyone tried the clFFT test I requested above? I've now done a test on my system (Thinkpad T440s, i5-4300U): 1. Without the patch (stderr): drm_intel_gem_bo_context_exec() failed: Device or resource busy Beignet: "Exec event 0x55e6d5920fd0 error, type is 4592, error staus is -5" (err: 0)after clGetPlatformIDs (err: 0) Platform found: Intel Gen OCL Driver (err: 0)after clGetDeviceIDs (err: 0)Device found on the above platform: Intel(R) HD Graphics Haswell Ultrabook GT2 Mobile (err: 0) after clCreateContext (err: 0)after clCreateCommandQueue (err: 0)after clfftInitSetupData (err: 0)after clfftSetup Performing fft on an one dimensional array of size N = 8192 (err: 0)after clCreateBuffer (err: 0)after clfftCreateDefaultPlan (err: 0)after clfftSetPlanPrecision (err: 0)after clfftSetLayout (err: 0)after clfftSetResultLocation (err: 0)after clfftBakePlan (err: 0)after clEnqueueWriteBuffer drm_intel_gem_bo_context_exec() failed: Device or resource busy Beignet: "Exec event 0x55e6d61cf540 error, type is 4592, error staus is -5" clEnqueueNDRangeKernel failed second... -14 params: 1 1024 128 0 ERROR executing the kernel -5 (err: -14)after clfftEnqueueTransform (err: -14)after clfftEnqueueTransform = CL_EXEC_STATUS_ERROR_FOR_EVENTS_IN_WAIT_LIST (err: 0)after clFinish (err: 0)after clEnqueueReadBuffer Time took 1: 0.000406 ERROR: found same numbers !!! ... FFT was not executed !!! 2. With the patch (stderr): (err: 0)after clGetPlatformIDs (err: 0) Platform found: Intel Gen OCL Driver (err: 0)after clGetDeviceIDs (err: 0)Device found on the above platform: Intel(R) HD Graphics Haswell Ultrabook GT2 Mobile (err: 0) after clCreateContext (err: 0)after clCreateCommandQueue (err: 0)after clfftInitSetupData (err: 0)after clfftSetup Performing fft on an one dimensional array of size N = 8192 (err: 0)after clCreateBuffer (err: 0)after clfftCreateDefaultPlan (err: 0)after clfftSetPlanPrecision (err: 0)after clfftSetLayout (err: 0)after clfftSetResultLocation (err: 0)after clfftBakePlan (err: 0)after clEnqueueWriteBuffer (err: 0)after clfftEnqueueTransform (err: 0)after clFinish (err: 0)after clEnqueueReadBuffer Time took 1: 0.000887 stdout contains values which could be the in- and output of an FFT in the 2. case. Cheers, Michael
Bug#859262: Re: freezes Orca screen reader
Control: tags -1 pending Control: owner -1 Hi all, On 02-05-17 21:48, Joanmarie Diggs wrote: > On 05/02/2017 03:26 PM, Paul Gevers wrote: > >> @Joanmarie, did you get any feedback on the Orca list? > > Nope. I take that to mean all is well. If this bug doesn't receive negative feedback about my package, I'll try to upload the fix to unstable tomorrow. Paul signature.asc Description: OpenPGP digital signature
Processed (with 1 error): Re: Bug#859262: Re: freezes Orca screen reader
Processing control commands: > tags -1 pending Bug #859262 [gnome-orca] gnome-orca: Gets stuck if target app is busy Added tag(s) pending. > owner -1 Unknown command or malformed arguments to command. -- 859262: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859262 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#861696: certbot: Python package not found.
Package: certbot
Severity: grave
Justification: renders package unusable
Dear Maintainer,
* What led up to the situation?
test -x /usr/bin/certbot -a \! -d /run/systemd/system && perl -e 'sleep
int(rand(3600))' && certbot -q renew
* What exactly did you do (or not do) that was effective (or
ineffective)?
Installed certbot. I think it's missing a TTY handler. The Jessie version works.
-- System Information:
Debian Release: 9.0
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.9.0-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
Traceback (most recent call last):
File "/usr/bin/certbot", line 11, in
load_entry_point('certbot==0.10.2', 'console_scripts', 'certbot')()
File
"/usr/local/lib/python2.7/dist-packages/distribute-0.6.28-py2.7.egg/pkg_resources.py",
line 337, in load_entry_point
return get_distribution(dist).load_entry_point(group, name)
File
"/usr/local/lib/python2.7/dist-packages/distribute-0.6.28-py2.7.egg/pkg_resources.py",
line 2311, in load_entry_point
return ep.load()
File
"/usr/local/lib/python2.7/dist-packages/distribute-0.6.28-py2.7.egg/pkg_resources.py",
line 2017, in load
entry = __import__(self.module_name, globals(),globals(), ['__name__'])
File "/usr/lib/python2.7/dist-packages/certbot/main.py", line 11, in
import zope.component
File "/usr/lib/python2.7/dist-packages/zope/component/__init__.py", line 19,
in
from zope.interface import named
ImportError: cannot import name named
Bug#857296: marked as done (hol88-library is an empty package on arm64, hppa, and m68k)
Your message dated Tue, 02 May 2017 14:50:27 + with message-id <87vapj8g98@valiant.maguirefamily.org> and subject line Re: hol-library empty on arm64 has caused the Debian Bug report #857296, regarding hol88-library is an empty package on arm64, hppa, and m68k 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.) -- 857296: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857296 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: hol88-library Version: 2.02.19940316-32 Severity: grave Justification: unintentionally empty package on a release architecture User: helm...@debian.org Usertags: rebootstrap Something weired seems to have happend to hol88-library. On some architectures (arm64, hppa, m68k), the package is simply empty. Upon closer inspection it turns out that the upstream build system simply hides build failures. https://sources.debian.net/src/hol88/2.02.19940316-32/Makefile/#L291 | (date; $(MAKE) hol; date; $(MAKE) library; date) Thus technically, hol88 fails to build from source, it violates policy by not detecting such failure and it is dysfunctional by shipping empty packages. Helmut --- End Message --- --- Begin Message --- Greetings! This was due to a transient failure in the build architecture on the affected platforms. Package builds fine now in a fresh up to date chroot. BinNMU uploaded. As an oblique aside, it does appear on cursory examination that 'fakeroot' has issues on arm64. -- Camm Maguirec...@maguirefamily.org == "The earth is but one country, and mankind its citizens." -- Baha'u'llah--- End Message ---
Bug#859262: Re: freezes Orca screen reader
On 05/02/2017 03:26 PM, Paul Gevers wrote: > @Joanmarie, did you get any feedback on the Orca list? Nope. I take that to mean all is well. --joanie
Processed: severity of 861693 is grave
Processing commands for cont...@bugs.debian.org: > severity 861693 grave Bug #861693 [src:swftools] swftools: CVE-2017-8400 CVE-2017-8401 Severity set to 'grave' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 861693: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861693 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#861683: Package: installation-reports GNOME is not Working
On Mon, 1 May 2017 00:28:59 -0500 Gerardo Flores wrote: > Package:installation-reports > Boot method: (Virtual box) > > Image version: > RC3 > Date: Abril 29 20717 > Machine: Virtual BOX DELL Presicion and Lenovo X230 > Processor: Xeon / icore 7 > Memory: En la virtual 2G / Virtual 2GB > Partitions: Basicos en una sola partición LVM > > Output of lspci -knn (o lspci -nn): «lspci -nn»)> > > Base System Installation Checklist: si dicha fase funcionó, «E» si presentó algún fallo y déjela en blanco si > no intentó o no usó esta opción.> > [O] = OK, [E] = Error (descríbalo a continuación), [ ] = didn't try it > > Initial boot: [E] <¿Funcionó el arranque inicial?> > Detect network card:[O] <¿Se configuró el hardware de red?> > Configure network: [O] <¿Se configuró la red?> > Detect CD: [O] <¿Se detectó la unidad de CD?> > Load installer modules: [O] <¿Se cargaron los módulos del instalador?> > Detect hard drives: [O] <¿Se detectaron los discos duros?> > Partition hard drives: [O] <¿Se particionó el disco duro?> > Install base system:[O] <¿Se instaló el sistema base?> > Clock/timezone setup: [O] <¿Se configuró bien la zona horaria?> > User/password setup:[O] <¿Se configuró correctamente el usuario?> > Install tasks: [O] <¿Se instalaron bien las tareas?> > Install boot loader:[O] <¿Se instaló el gestor de arranque?> > Overall install:[E] <¿Reinició correctamente?> > > Comments/Problems: > > Hi, I am writing because you have tried to install Debian 9 for a month, on > two different computers with virtual box. And I can not put Gnome. In the > installation on a computer I get a red screen. So I just put the base system > without graphical environment and then try to install the gnome, the next > reboot will not boot. On any of the other desktops no problem is installed. > Then > I continued testing on different computers and different configurations > and continued with the problem I was not allowed to install gnome on > reboot after the computer does not boot. And in any desktop without problem > and also with only text I have problem only happens with gnome. > Sorry for my english, in fact I'm using google translator. I hope it helps > them to have a shiny Debian, as always. And while happy with my Jessie it > works phenomenally :) Most likely a duplicate of https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861683 seeing that you installed this system using Virtualbox -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#860805: [Pkg-opencl-devel] Bug#860805: beignet-opencl-icd: OpenCL fails with: drm_intel_gem_bo_context_exec() failed: Device or resource busy
Hi Rebecca, On Tue, May 02, 2017 at 07:04:20PM +0100, Rebecca N. Palmer wrote: > > Could > >you please give a direct link what program to run once I have rebuild? > > https://bugs.freedesktop.org/show_bug.cgi?id=100639#c15 > where patch_clfft_haswell.patch is > https://bugs.freedesktop.org/attachment.cgi?id=131090 > (Posting the actual binary would be a security hole, since I don't have a > GPG key yet...) I downloaded https://bugs.freedesktop.org/attachment.cgi?id=131090 and tried to add it as quilt patch at the end of sequence but it does not apply. Would you mind creating an extra branch in Git applying what should be applied and I just build this? BTW, it would be really great if you would get your key signed soon. ;-) Kind regards Andreas. -- http://fam-tille.de
Processed: Fix severity Re: [j...@debian.org: Re: Bug#861589: unblock: gnumed-client/1.6.11+dfsg-3]
Processing commands for cont...@bugs.debian.org:
> severity 861570 grave
Bug #861570 {Done: Andreas Tille } [gnumed-client] Recommends
python-hl7, but does not start without it
Severity set to 'grave' from 'important'
> severity 861589 normal
Bug #861589 {Done: Jonathan Wiltshire } [release.debian.org]
unblock: gnumed-client/1.6.11+dfsg-3
Severity set to 'normal' from 'grave'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
861570: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861570
861589: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861589
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#861690: gerris: FTBFS - uses dh-exec without Build-Depends on it
Source: gerris Version: 20131206+dfsg-15 Severity: serious Hi, The just uploaded version of gerris FTBFS as it uses dh-exec without Build-Depends on dh-exec. Thanks, ~Niels
Processed: [j...@debian.org: Re: Bug#861589: unblock: gnumed-client/1.6.11+dfsg-3]
Processing commands for cont...@bugs.debian.org:
> severity 861589 grave
Bug #861589 {Done: Jonathan Wiltshire } [release.debian.org]
unblock: gnumed-client/1.6.11+dfsg-3
Severity set to 'grave' from 'normal'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
861589: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861589
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#859262: Re: freezes Orca screen reader
Hi all, On 30-04-17 21:09, Joanmarie Diggs wrote: > From your output I see you clicked on the Apply button in Synaptic, a > bunch of events from DEAD accessible objects resulted, that Orca kept > processing events, presented the window you Alt+Tabbed into, etc. > > Having said that, if memory serves me, even before the changes I made, > Orca kept processing events, and probably would have presented the > window you Alt+Tabbed into. In other words, I don't know if, from the > user's perspective, anything has changed. But it appears that I've done > all I can do in Orca (i.e. handling the exceptions it's getting from > AT-SPI2 as a result of querying Synaptic for information via AT-SPI2). Just for the record, and I have no idea if it is relevant, but Synaptic also makes the main Synaptic window and/or its menu items inaccessible for the sighted people after pressing buttons. This is meant as feedback that Synaptic is busy. Maybe this behavior has something to do with the bug at hand (the one in AT-SPI2 I mean). And I would still appreciate feedback on my package. @Joanmarie, did you get any feedback on the Orca list? Paul signature.asc Description: OpenPGP digital signature
Processed: reassign 851120 to src:xorg, forcibly merging 861683 851120
Processing commands for cont...@bugs.debian.org: > reassign 851120 src:xorg Bug #851120 [xserver-xorg-video-all] gdm3 does not start on fresh stretch install in vbox Bug reassigned from package 'xserver-xorg-video-all' to 'src:xorg'. Ignoring request to alter found versions of bug #851120 to the same values previously set Ignoring request to alter fixed versions of bug #851120 to the same values previously set > forcemerge 861683 851120 Bug #861683 [src:xorg] Install xserver-xorg-legacy by default for stretch Bug #851120 [src:xorg] gdm3 does not start on fresh stretch install in vbox Severity set to 'serious' from 'normal' Marked as found in versions xorg/1:7.7+18. Merged 851120 861683 > thanks Stopping processing here. Please contact me if you need assistance. -- 851120: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851120 861683: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861683 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#860805: [Pkg-opencl-devel] Bug#860805: beignet-opencl-icd: OpenCL fails with: drm_intel_gem_bo_context_exec() failed: Device or resource busy
On 02/05/17 07:57, Andreas Tille wrote: I can confirm that beignet-dev_1.3.0-2 produces a lot of errors which vanished when using said status from Git. Good so far. - the clFFT test from https://bugs.freedesktop.org/show_bug.cgi?id=100639 This needs a small change to work in sid (its reporter was using jessie-backports): -DCMAKE_C_FLAGS:STRING="-O3 -DCL_USE_DEPRECATED_OPENCL_1_2_APIS=1" as linking to an __inline symbol (clfftInitSetupData) without optimization fails in recent gcc. In other words: I would need to rebuild beignet-dev_1.3.0-2 with the said change in d/rules as well as rebuild 7d60bf92c6706f174305393172841e2078ecd508 and compare again? No, that change is for the test program (which won't build in sid without it), not beignet itself. Could you please give a direct link what program to run once I have rebuild? https://bugs.freedesktop.org/show_bug.cgi?id=100639#c15 where patch_clfft_haswell.patch is https://bugs.freedesktop.org/attachment.cgi?id=131090 (Posting the actual binary would be a security hole, since I don't have a GPG key yet...)
Bug#861676: ruby-prof: broken symlink: /usr/share/doc/ruby-prof/fonts/Lato-RegularItalic.ttf -> ../../../fonts/truetype/lato/Lato-RegularItalic.ttf
Control: severity -1 normal Hi, On Tue, May 02, 2017 at 05:23:34PM +0200, Andreas Beckmann wrote: > Package: ruby-prof > Version: 0.16.2+dfsg-2 > Severity: serious > User: debian...@lists.debian.org > Usertags: piuparts > > Hi, > > during a test with piuparts I noticed your package ships (or creates) > a broken symlink. > > >From the attached log (scroll to the bottom...): > > 0m20.4s ERROR: FAIL: Broken symlinks: > /usr/share/doc/ruby-prof/fonts/Lato-RegularItalic.ttf -> > ../../../fonts/truetype/lato/Lato-RegularItalic.ttf > > ^^ > > The fonts-lato package ships > > /usr/share/fonts/truetype/lato/Lato-Italic.ttf >^^^ > instead. Can you clarify exactly why you think a dangling symlink should warrant severity serious? signature.asc Description: PGP signature
Processed: Re: Bug#861676: ruby-prof: broken symlink: /usr/share/doc/ruby-prof/fonts/Lato-RegularItalic.ttf -> ../../../fonts/truetype/lato/Lato-RegularItalic.ttf
Processing control commands: > severity -1 normal Bug #861676 [ruby-prof] ruby-prof: broken symlink: /usr/share/doc/ruby-prof/fonts/Lato-RegularItalic.ttf -> ../../../fonts/truetype/lato/Lato-RegularItalic.ttf Severity set to 'normal' from 'serious' -- 861676: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861676 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#861684: r-cran-randomfields: FTBFS against r-base 3.4.0-1
Package: r-cran-randomfields Version: 3.1.36-1 Severity: serious Justification: fails to build from source (but built successfully in the past) Dear Maintainer, This package FTBFS against r-base 3.4.0-1 which was uploaded to unstable recently. [..] make[1]: Leaving directory '/<>/src' make[1]: Entering directory '/<>/src' make[1]: Leaving directory '/<>/src' installing to /<>/debian/r-cran-randomfields/usr/lib/R/site-library/RandomFields/libs ** R ** data ** inst ** preparing package for lazy loading Error: package or namespace load failed for 'RandomFieldsUtils' in dyn.load(file, DLLpath = DLLpath, ...): allocation failure in R_setPrimitiveArgTypes Error : package 'RandomFieldsUtils' could not be loaded ERROR: lazy loading failed for package 'RandomFields' * removing '/<>/debian/r-cran-randomfields/usr/lib/R/site-library/RandomFields' dh_auto_install: R CMD INSTALL -l /<>/debian/r-cran-randomfields/usr/lib/R/site-library --clean . --built-timestamp='Sun, 08 Jan 2017 17:05:46 +0100' returned exit code 1 debian/rules:4: recipe for target 'binary' failed make: *** [binary] Error 25 dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2 Build finished at 2017-05-02T17:28:29Z Ximin -- System Information: Debian Release: 9.0 APT prefers testing APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 'testing-debug'), (300, 'unstable'), (200, 'experimental'), (1, 'experimental-debug') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
Bug#861683: Install xserver-xorg-legacy by default for stretch
Source: xorg Version: 1:7.7+18 Severity: serious With virtualbox-dkms gone for stretch, trying to install GNOME inside Virtualbox will lead to gdm failing to start, as it tries to run Xorg as unprivileged user. This requires a KMS compatible driver though. Same is true for users of startx. They need the suid wrapper provided by xserver-xorg-legacy in such a case. Not having the Xorg.wrap suid wrapper is a worthwile goal, but I guess we are not quite there yet, as there are still to many popular cases where it's needed. I would thus like to see xserver-xorg-legacy added as a Recommends to one of the xorg packages. This means it would be installed on upgrades and new installations but users with a KMS compatible driver can uninstall it. -- System Information: Debian Release: 9.0 APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (200, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages xserver-xorg depends on: ii x11-xkb-utils7.7+3+b1 ii xkb-data 2.19-1 ii xserver-xorg-core2:1.19.3-1 ii xserver-xorg-input-all 1:7.7+18 ii xserver-xorg-input-evdev [xorg-driver-input] 1:2.10.5-1 ii xserver-xorg-input-libinput [xorg-driver-input] 0.23.0-2 ii xserver-xorg-input-wacom [xorg-driver-input] 0.34.0-1 ii xserver-xorg-video-all 1:7.7+18 ii xserver-xorg-video-amdgpu [xorg-driver-video]1.2.0-1+b1 ii xserver-xorg-video-ati [xorg-driver-video] 1:7.8.0-1+b1 ii xserver-xorg-video-fbdev [xorg-driver-video] 1:0.4.4-1+b5 ii xserver-xorg-video-nouveau [xorg-driver-video] 1:1.0.13-3 ii xserver-xorg-video-radeon [xorg-driver-video]1:7.8.0-1+b1 ii xserver-xorg-video-vesa [xorg-driver-video] 1:2.3.4-1+b2 ii xserver-xorg-video-vmware [xorg-driver-video]1:13.2.1-1+b1 Versions of packages xserver-xorg recommends: ii libgl1-mesa-dri 13.0.6-1+b2 -- no debconf information
Bug#861677: marked as done (libgfs-dev: broken symlink on i386: /usr/lib/x86_64-linux-gnu/libgfs[23]D-1.3.so -> libgfs[23]D-1.3.so.2.0.0)
Your message dated Tue, 02 May 2017 17:33:26 + with message-id and subject line Bug#861677: fixed in gerris 20131206+dfsg-15 has caused the Debian Bug report #861677, regarding libgfs-dev: broken symlink on i386: /usr/lib/x86_64-linux-gnu/libgfs[23]D-1.3.so -> libgfs[23]D-1.3.so.2.0.0 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.) -- 861677: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861677 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libgfs-dev Version: 20131206+dfsg-14 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package ships (or creates) a broken symlink. >From the attached log (scroll to the bottom...): 1m26.4s ERROR: FAIL: Broken symlinks: /usr/lib/x86_64-linux-gnu/libgfs3D-1.3.so -> libgfs3D-1.3.so.2.0.0 /usr/lib/x86_64-linux-gnu/libgfs2D-1.3.so -> libgfs2D-1.3.so.2.0.0 ^^ Since this happens on i386 ... these symlinks seem to be manually created, while they should rather come from the build system. cheers, Andreas gfsview_20121130+dfsg-4.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: gerris Source-Version: 20131206+dfsg-15 We believe that the bug you reported is fixed in the latest version of gerris, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 861...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Anton Gladky (supplier of updated gerris package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 02 May 2017 19:06:33 +0200 Source: gerris Binary: gerris libgfs-1.3-2 libgfs-dev Architecture: source Version: 20131206+dfsg-15 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Anton Gladky Description: gerris - Fluid Flow Solver libgfs-1.3-2 - Fluid Flow Solver -- shared libraries libgfs-dev - Fluid Flow Solver -- development libraries and headers Closes: 861677 Changes: gerris (20131206+dfsg-15) unstable; urgency=medium . * [d9065f4] Respect arch-path for symbolic links. (Closes: #861677) Checksums-Sha1: 29544056c80a8f0f1219e931b36f00bdfbc9b99f 2419 gerris_20131206+dfsg-15.dsc d481191bceffc701a304319e211acd582ac171b4 16692 gerris_20131206+dfsg-15.debian.tar.xz b2c42c604023d041ac7516f99704dca629e355f2 8605 gerris_20131206+dfsg-15_source.buildinfo Checksums-Sha256: 91a5a7f9d885c760d7b1248d91207d6ec2028dbd439c01bb484e3345d6fe727c 2419 gerris_20131206+dfsg-15.dsc 81c3cc703427368c5aed2f307b498bab37f5e0eccacf9bbfba8c746ed338eaf6 16692 gerris_20131206+dfsg-15.debian.tar.xz c2fa0a64757b98338e05aefaca6d913a71207c9ec8ad39dbc02cbf5f6fce8f6c 8605 gerris_20131206+dfsg-15_source.buildinfo Files: a9ca7ba7768343b2210a50f0cd1f839c 2419 science optional gerris_20131206+dfsg-15.dsc d766dc1fe01b96451c43c565709dbaef 16692 science optional gerris_20131206+dfsg-15.debian.tar.xz 7940d0e525daf52deee77637cd30551b 8605 science optional gerris_20131206+dfsg-15_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEu71F6oGKuG/2fnKF0+Fzg8+n/wYFAlkIvswACgkQ0+Fzg8+n /wZV4hAAl2rTQZheXOulj0eufO5H9Nl8rn9lla1NRTyv9uFhnL0ScQofUikG92Wf wy4EDqH4Tql30Z9In80vkbekZKCy6jJ6KUEXJJ0HrcchjEyTSRod15KusH/Z3VUN lDnd4r85HlnviJ8xNDSKvKR+USE9crKSHVRX0ULa4HEAlNhgEIl8TEjKVucfTHq2 9LAHawOX29XPJMJbynUAdXdATcv6K7okUHTFZkTZlkq43Co4or0S16WoRfjhLGT+ IsX42Ow8U9ZCSFfaQyHeNaPvbrjfu7Pm4asXKTRWcsl/EU40EKHZSScD14WLBEat e2rBNJHmgkj+OUeo57w4MflIzkFx+fYqT+Zhr0wDewYui3hLquykSgKNiqGk1Gc+ +h7JS4KhaQkVnFRqWUgx3K7gvi34UdgHsJzeQDQjMVqLY3PL1oMw8enwWtC2y48H deM29CCZMKOYeQ8QihTf9ZTTwG0b1loyxCirRhIK97RIOgLWFLiy4P/H3+B7bF8o 0H7MXxw1Thku4WUbhuWxqrOVI+keBidHynS1UL4V/21f7h71viJHaHcubCKdV4yY Ko6QtuR2AdwCYs+vvOKu/wa0AyNH+uKF1LQBPnO1T9U08MGAqse+H4JoYnN4VASw mwfpDT5Tc591FmHYkdHQGSFuHyZQYkYk+BUkbfnCM9XuKqmYlpA= =soBw -END PGP SIGNATURE End Message ---
Bug#861682: libpoco-dev: missing Depends on libssl-dev
Package: libpoco-dev Version: 1.7.6+dfsg1-4 Severity: serious Dear Maintainer, In file included from /usr/include/Poco/Crypto/X509Certificate.h:24:0, from /usr/include/Poco/Net/Context.h:25, from /usr/include/Poco/Net/SecureServerSocket.h:25, from wsd/Admin.cpp:23: /usr/include/Poco/Crypto/OpenSSLInitializer.h:26:28: fatal error: openssl/crypto.h: No such file or directory #include ^ compilation terminated. If Poco/Net/SecureServerSocket.h needs libssl-dev (via said Poco/Crypto/OpenSSLInitializer.h), it should depend on it. Regards, RenePackage: libpoco-dev Version: 1.7.6+dfsg1-4 Severity: serious Dear Maintainer, In file included from /usr/include/Poco/Crypto/X509Certificate.h:24:0, from /usr/include/Poco/Net/Context.h:25, from /usr/include/Poco/Net/SecureServerSocket.h:25, from wsd/Admin.cpp:23: /usr/include/Poco/Crypto/OpenSSLInitializer.h:26:28: fatal error: openssl/crypto.h: No such file or directory #include ^ compilation terminated. If Poco/Net/SecureServerSocket.h needs libssl-dev (via said Poco/Crypto/OpenSSLInitializer.h), it should depend on it. Regards, Rene
Bug#861486: [Pkg-julia-devel] Bug#861486: Bug#861486: julia: FTBFS on mips64el (segmentation fault)
Hi Graham, On Mon, May 01, 2017 at 01:53:43PM +0200, Graham Inggs wrote: > Simply running, e.g. 'debian/shlibdeps pow', 10 or so times in a row > is enough to get it to segfault. > Unfortunately, it doesn't seem to happen when run in gdb. > I don't know why this program [1], which is used to generate > julia.links, would be failing randomly in this way (it seems to occur > after the final 'printf') and only on this architecture. > > [1] > https://anonscm.debian.org/cgit/pkg-julia/julia.git/tree/debian/shlibdeps.c Since I don’t have access to mips64el at the moment: Could you comment all lines and then successively uncomment to see which line triggers the segfault? You could also try querying a symbol in libm other than pow and see whether that changes anything. Regards, Peter
Bug#861645: gsequencer FTBFS on mips/mipsel: FAIL: ags_xorg_application_context_test
Hi I have experienced on some other architectures with ags_xorg_application_context_test the same problems. It was not evident to me if the problem was related to Gtk+-2.0 or xvfb-run since the stack-trace ended as doing gtk_widget_show(window); However other architectures just pass the test. Now, I'm going to set up a VM to get a meaningful stack-trace. Bests, Joël On Tue, May 2, 2017 at 10:05 AM, Adrian Bunk wrote: > Source: gsequencer > Version: 0.8.0-1 > Severity: serious > > https://buildd.debian.org/status/package.php?p=gsequencer&suite=sid > > ... > make check-TESTS > make[3]: Entering directory '/«PKGBUILDDIR»' > make[4]: Entering directory '/«PKGBUILDDIR»' > PASS: ags_thread_test > PASS: ags_audio_application_context_test > PASS: ags_turtle_test > PASS: ags_devout_test > PASS: ags_channel_test > PASS: ags_audio_test > PASS: ags_audio_signal_test > PASS: ags_recall_test > PASS: ags_port_test > PASS: ags_recycling_test > PASS: ags_pattern_test > PASS: ags_notation_test > PASS: ags_automation_test > PASS: ags_midi_buffer_util_test > PASS: ags_midi_builder_test > ./test-driver: line 107: 7386 Segmentation fault "$@" > $log_file 2>&1 > FAIL: ags_xorg_application_context_test > >gsequencer 0.8.0: ./test-suite.log > > > # TOTAL: 16 > # PASS: 15 > # SKIP: 0 > # XFAIL: 0 > # FAIL: 1 > # XPASS: 0 > # ERROR: 0 > > .. contents:: :depth: 2 > > FAIL: ags_xorg_application_context_test > === > > > > CUnit - A unit testing framework for C - Version 2.1-3 > http://cunit.sourceforge.net/ > > ** Message: loading preferences from data[0x55df8774] > ** Message: autosave-thread > ** Message: false > ** Message: simple-file > ** Message: true > ** Message: disable-feature > ** Message: experimental > ** Message: segmentation > ** Message: 4/4 > ** Message: model > ** Message: super-threaded > ** Message: super-threaded-scope > ** Message: channel > ** Message: lock-global > ** Message: ags-thread > ** Message: lock-parent > ** Message: ags-recycling-thread > ** Message: backend > ** Message: alsa > ** Message: device > ** Message: hw:0,0 > ** Message: samplerate > ** Message: 44100 > ** Message: buffer-size > ** Message: 1024 > ** Message: pcm-channels > ** Message: 2 > ** Message: dsp-channels > ** Message: 2 > ** Message: format > ** Message: 16 > ** Message: backend > ** Message: alsa > ** Message: device > ** Message: hw:0,0 > ** Message: samplerate > ** Message: 44100 > ** Message: buffer-size > ** Message: 1024 > ** Message: pcm-channels > ** Message: 2 > ** Message: dsp-channels > ** Message: 2 > ** Message: format > ** Message: 16 > ** Message: auto-sense > ** Message: true > > Suite: AgsXorgApplicationContextTest > Test: test of AgsXorgApplicationContext doing dispose ...** Message: Can't > get the next card number: Success > ** Message: Can't get the next card number: Success > FAIL ags_xorg_application_context_test (exit status: 139) > > > Testsuite summary for gsequencer 0.8.0 > > # TOTAL: 16 > # PASS: 15 > # SKIP: 0 > # XFAIL: 0 > # FAIL: 1 > # XPASS: 0 > # ERROR: 0 > > See ./test-suite.log > Please report to jkraehemann-gu...@users.alioth.debian.org > > Makefile:9817: recipe for target 'test-suite.log' failed > make[4]: *** [test-suite.log] Error 1 > ___ > pkg-multimedia-maintainers mailing list > pkg-multimedia-maintain...@lists.alioth.debian.org > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#861678: libi8x FTBFS on 32bit: FAIL: valid/test-corpus
Source: libi8x Version: 0.0.3-1 Severity: serious https://buildd.debian.org/status/package.php?p=libi8x&suite=sid ... make check-TESTS PASS: exec/ops/test-deref PASS: exec/test-factorial PASS: exec/test-smoke FAIL: valid/test-corpus libi8x 0.0.3: tests/test-suite.log # TOTAL: 4 # PASS: 3 # SKIP: 0 # XFAIL: 0 # FAIL: 1 # XPASS: 0 # ERROR: 0 .. contents:: :depth: 2 FAIL: valid/test-corpus === corpus/i8c/0.0.4/32el/test_deref/test_deref/0015-0001[0x9]: Unhandled note corpus/i8c/0.0.4/32el/test_deref/test_deref/0011-0001[0x9]: Unhandled note corpus/i8c/0.0.4/32be/test_deref/test_deref/0015-0001[0x9]: Unhandled note corpus/i8c/0.0.4/32be/test_deref/test_deref/0011-0001[0x9]: Unhandled note valid/test-corpus.c:137: ftw_failcount == 0 FAIL valid/test-corpus (exit status: 1) Testsuite summary for libi8x 0.0.3 # TOTAL: 4 # PASS: 3 # SKIP: 0 # XFAIL: 0 # FAIL: 1 # XPASS: 0 # ERROR: 0 See tests/test-suite.log Please report to infin...@sourceware.org Makefile:832: recipe for target 'test-suite.log' failed make[5]: *** [test-suite.log] Error 1
Bug#861486: julia: FTBFS on mips64el (segmentation fault)
A quick way to reproduce this on a porterbox, without having to build the entire julia package: Install julia's build-dependencies Change root to sid_mips64el-dchroot $ apt source julia $ cd julia-0.4.7/ $ debian/rules override_dh_link-arch If it manages to generate the links without a segfault, remove the output before trying again: $ rm debian/julia.links
Bug#861677: libgfs-dev: broken symlink on i386: /usr/lib/x86_64-linux-gnu/libgfs[23]D-1.3.so -> libgfs[23]D-1.3.so.2.0.0
Package: libgfs-dev Version: 20131206+dfsg-14 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package ships (or creates) a broken symlink. >From the attached log (scroll to the bottom...): 1m26.4s ERROR: FAIL: Broken symlinks: /usr/lib/x86_64-linux-gnu/libgfs3D-1.3.so -> libgfs3D-1.3.so.2.0.0 /usr/lib/x86_64-linux-gnu/libgfs2D-1.3.so -> libgfs2D-1.3.so.2.0.0 ^^ Since this happens on i386 ... these symlinks seem to be manually created, while they should rather come from the build system. cheers, Andreas gfsview_20121130+dfsg-4.log.gz Description: application/gzip
Processed: Merge duplicates
Processing commands for cont...@bugs.debian.org:
> unarchive 661958
Bug #661958 {Done: "Adam D. Barratt" }
[release.debian.org] transition: apache2 2.4
Unarchived Bug 661958
> forcemerge 669785 816310
Bug #669785 {Done: Debian FTP Masters }
[websvn] websvn: transition towards Apache 2.4
Bug #816310 [websvn] WebSVN wants do write to non existing folder
"/etc/apache2/conf.d"
661958 was blocked by: 669755 669834 666854 669775 666817 669735 666832 669825
669856 670973 711160 669777 669814 707062 669743 669791 707066 669840 666848
666850 666806 666857 666811 669782 669884 666838 666825 666855 669812 669747
666863 666829 669844 666799 669769 669738 666815 669821 707060 669828 669749
669792 669842 669762 669785 666807 666862 666859 710512 669823 666860 669745
669819 666796 669837 710688 669733 666822 669757 669830 669854 666858 666820
666847 669959 707065 666835 669804 707063 669801 669741 666833 666801 669767
669798 669750 669761 666831 669788 669779 669808 669759 666830 669832 669827
666837 666856 666814 669787 669737 669773 666849 666818 666852 669826 669774
666810 669806 669855 669768 666809 666797 669796 669815 669742 666846 666805
669885 669752 669734 707061 666802 669754 669820 669776 669813 669845 669746
669739 669833 666826 669846 669781 666804 666840 669783 666853 669817 669764
666794 710870 669770 666844 669822 669851 669841 666800 669843 669748 669790
666834 711175 666813 709462 669736 669824 710475 669794 669763 669800 718475
666808 669780 669857 669292 666842 666851 669802 669839 669805 669729 707064
669811 669818 669740 669803 666836 669756 666864 669829 666821 718649 669772
669766 669809 669751 666839 669789 669799 669786 669797 714537 669831 669836
669784
661958 was not blocking any bugs.
Added blocking bug(s) of 661958: 816310
Marked Bug as done
There is no source info for the package 'websvn' at version '2.3.3-1.3+rm' with
architecture ''
Unable to make a source version for version '2.3.3-1.3+rm'
Marked as fixed in versions 2.3.3-1.3+rm.
Marked as found in versions websvn/2.3.3-1.2.
Bug #669785 {Done: Debian FTP Masters }
[websvn] websvn: transition towards Apache 2.4
Marked as found in versions websvn/2.3.3-1.2+deb8u1.
Merged 669785 816310
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
661958: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=661958
669785: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=669785
816310: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=816310
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#860703: golang-github-jacobsa-fuse: FTBFS on i386: dh_auto_build
On Tue, 2 May 2017 16:34:02 +0900 Roger Shimizu wrote: > but the following errors still exist. I don't have clue yet. > > > src/github.com/jacobsa/fuse/internal/buffer/runtime.go:22: missing function > > body for "memclr" > > src/github.com/jacobsa/fuse/internal/buffer/runtime.go:27: missing function > > body for "memmove" Finally find a way to fix it. So pushed my commits to master (w/o releasing commit), and mentors branch (w/ releasing commit). Package is uploaded to mentors for RFS. Please kindly help to sponsor the upload. Thank you! Cheers, -- Roger Shimizu, GMT +9 Tokyo PGP/GPG: 4096R/6C6ACD6417B3ACB1 pgpOgrrfeTSNt.pgp Description: PGP signature
Processed (with 1 error): Merge duplicates
Processing commands for cont...@bugs.debian.org:
> forcemerge 669785 816310
Bug #669785 {Done: Debian FTP Masters }
[websvn] websvn: transition towards Apache 2.4
Bug #816310 [websvn] WebSVN wants do write to non existing folder
"/etc/apache2/conf.d"
Severity set to 'grave' from 'important'
Failed to forcibly merge 669785: Not altering archived bugs; see unarchive.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
669785: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=669785
816310: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=816310
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: Pending fixes for bugs in the golang-github-jacobsa-fuse package
Processing commands for cont...@bugs.debian.org: > tag 860703 + pending Bug #860703 [src:golang-github-jacobsa-fuse] golang-github-jacobsa-fuse: FTBFS on i386: dh_auto_build: go install -v -p 1 github.com/jacobsa/fuse github.com/jacobsa/fuse/fsutil github.com/jacobsa/fuse/fuseops github.com/jacobsa/fuse/fusetesting github.com/jacobsa/fuse/fuseutil github.com/jacobsa/fuse/internal/buffer github.com/jacobsa/fuse/internal/freelist github.com/jacobsa/fuse/internal/fusekernel returned exit code 2 Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 860703: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860703 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#860703: Pending fixes for bugs in the golang-github-jacobsa-fuse package
tag 860703 + pending thanks Some bugs in the golang-github-jacobsa-fuse package are closed in revision 09331450f4b0b3a5acb6b1b86d1c71faa036ab10 in branch 'master' by Roger Shimizu The full diff can be seen at https://anonscm.debian.org/cgit/pkg-go/packages/golang-github-jacobsa-fuse.git/commit/?id=0933145 Commit message: debian/patches: Add patch to fix FTBFS on i386 platform Closes: #860703
Bug#861676: ruby-prof: broken symlink: /usr/share/doc/ruby-prof/fonts/Lato-RegularItalic.ttf -> ../../../fonts/truetype/lato/Lato-RegularItalic.ttf
Package: ruby-prof Version: 0.16.2+dfsg-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package ships (or creates) a broken symlink. >From the attached log (scroll to the bottom...): 0m20.4s ERROR: FAIL: Broken symlinks: /usr/share/doc/ruby-prof/fonts/Lato-RegularItalic.ttf -> ../../../fonts/truetype/lato/Lato-RegularItalic.ttf ^^ The fonts-lato package ships /usr/share/fonts/truetype/lato/Lato-Italic.ttf ^^^ instead. cheers, Andreas ruby-prof_0.16.2+dfsg-2.log.gz Description: application/gzip
Processed: Not relevant for jessie
Processing commands for cont...@bugs.debian.org:
> tags 852044 stretch sid
Bug #852044 {Done: Daniel Silverstone }
[src:lua-curl] lua-curl: FTBFS: No rule to make target
'/usr/include/curl/curl.h', needed by 'curlopt.h'
Added tag(s) sid and stretch.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
852044: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852044
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: tagging 860646
Processing commands for cont...@bugs.debian.org: > tags 860646 + pending Bug #860646 [src:golang-github-jacobsa-ogletest] golang-github-jacobsa-ogletest: FTBFS on i386: dh_auto_test: go test -v -p 1 github.com/jacobsa/ogletest github.com/jacobsa/ogletest/srcutil github.com/jacobsa/ogletest/test_cases github.com/jacobsa/ogletest/test_cases/mock_image returned exit code 1 Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 860646: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860646 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 861474
Processing commands for cont...@bugs.debian.org: > tags 861474 + pending Bug #861474 [slim] slim: Session restarts in a loop rendering the whole system useless Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 861474: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861474 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: user debian...@lists.debian.org, usertagging 827122, reassign 827122 to liboasis3-dev ...
Processing commands for cont...@bugs.debian.org: > user debian...@lists.debian.org Setting user to debian...@lists.debian.org (was a...@debian.org). > usertags 827122 piuparts There were no usertags set. Usertags are now: piuparts. > reassign 827122 liboasis3-dev 3.mct+dfsg.121022-7 Bug #827122 [liboasis3-0d] liboasis3-0d: libpsmile.so is a broken symbolic link to libpsmile.MPI1.so.0d Bug reassigned from package 'liboasis3-0d' to 'liboasis3-dev'. No longer marked as found in versions oasis3/3.mct+dfsg.121022-7. Ignoring request to alter fixed versions of bug #827122 to the same values previously set Bug #827122 [liboasis3-dev] liboasis3-0d: libpsmile.so is a broken symbolic link to libpsmile.MPI1.so.0d Marked as found in versions oasis3/3.mct+dfsg.121022-7. > severity 827122 serious Bug #827122 [liboasis3-dev] liboasis3-0d: libpsmile.so is a broken symbolic link to libpsmile.MPI1.so.0d Severity set to 'serious' from 'important' > # Rationale: packages silently get linked against the static library as a > fallback > thanks Stopping processing here. Please contact me if you need assistance. -- 827122: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=827122 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: found 856966 in libtextutils-ocaml-dev/112.17.00-4, found 852125 in 0.13-1.1, found 776173 in 1.3.6-5 ...
Processing commands for cont...@bugs.debian.org: > found 856966 libtextutils-ocaml-dev/112.17.00-4 Bug #856966 [src:janest-core] Uninstallable on sid Bug #843312 [src:janest-core] FTBFS: libsexplib-camlp4-dev is no longer available Bug #852890 [src:janest-core] ocaml-textutils: FTBFS: build-dependency not installable: libcore-ocaml-dev (>= 113.00.00-4~) The source libtextutils-ocaml-dev and version 112.17.00-4 do not appear to match any binary packages Marked as found in versions libtextutils-ocaml-dev/112.17.00-4. Marked as found in versions libtextutils-ocaml-dev/112.17.00-4. Marked as found in versions libtextutils-ocaml-dev/112.17.00-4. > found 852125 0.13-1.1 Bug #852125 [nodm] nodm: purging leaves leaves dangling /etc/systemd/system/display-manager.service symlink Marked as found in versions nodm/0.13-1.1. > found 776173 1.3.6-5 Bug #776173 [slim] slim: unowned files after purge (policy 6.8, 10.8): /etc/systemd/system/display-manager.service -> /lib/systemd/system/slim.service Marked as found in versions slim/1.3.6-5. > found 857653 1:4.0-5 Bug #857653 [liblld-4.0] liblld-4.0: missing liblld-4.0.so.1 Marked as found in versions llvm-toolchain-4.0/1:4.0-5. > affects 857653 + liblld-5.0 Bug #857653 [liblld-4.0] liblld-4.0: missing liblld-4.0.so.1 Added indication that 857653 affects liblld-5.0 > found 857653 llvm-toolchain-snapshot/1:5.0~svn301421-1 Bug #857653 [liblld-4.0] liblld-4.0: missing liblld-4.0.so.1 Marked as found in versions llvm-toolchain-snapshot/1:5.0~svn301421-1. > affects 857680 + llvm-4.0-examples Bug #857680 [llvm-3.8-examples] llvm-3.8-examples: broken symlinks: /usr/share/doc/llvm-3.8-examples/Makefile.* -> ../../../lib/llvm-3.8/build/Makefile.* Added indication that 857680 affects llvm-4.0-examples > found 857680 llvm-4.0-examples/1:4.0-5 Bug #857680 [llvm-3.8-examples] llvm-3.8-examples: broken symlinks: /usr/share/doc/llvm-3.8-examples/Makefile.* -> ../../../lib/llvm-3.8/build/Makefile.* The source llvm-4.0-examples and version 1:4.0-5 do not appear to match any binary packages Marked as found in versions llvm-4.0-examples/1:4.0-5. > thanks Stopping processing here. Please contact me if you need assistance. -- 776173: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=776173 843312: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843312 852125: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852125 852890: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852890 856966: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=856966 857653: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857653 857680: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857680 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: your mail
Processing commands for cont...@bugs.debian.org: > forwarded 860618 https://github.com/seccomp/libseccomp-golang/issues/24 Bug #860618 [src:golang-github-seccomp-libseccomp-golang] golang-github-seccomp-libseccomp-golang: FTBFS on i386: dh_auto_test: go test -v -p 1 github.com/seccomp/libseccomp-golang returned exit code 1 Set Bug forwarded-to-address to 'https://github.com/seccomp/libseccomp-golang/issues/24'. > End of message, stopping processing here. Please contact me if you need assistance. -- 860618: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860618 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: BROKEN: 0.4.11 lacks support for get_info and URLs with a prefix path
Processing commands for cont...@bugs.debian.org: > retitle 861656 0.4.11 lacks support for get_info and URLs with a prefix path Bug #861656 [src:python-jenkins] BROKEN: 0.4.11 lacks support for get_info and URLs with a prefix path Changed Bug title to '0.4.11 lacks support for get_info and URLs with a prefix path' from 'BROKEN: 0.4.11 lacks support for get_info and URLs with a prefix path'. > thanks Stopping processing here. Please contact me if you need assistance. -- 861656: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861656 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#861474: slim: Session restarts in a loop renedering whole system useless.
Control: tags -1 patch Hi all, On Sun, 30 Apr 2017 12:38:33 +0200 Lukas wrote: > Hi > > Got the same problem on stretch. > > Changing the systemd service type to simple solves the problem for me: > > echo "Type=simple" >> /lib/systemd/system/slim.service > systemctl daemon-reload > > So, i guess the dbus name can't be acquired... > > BR > > Lukas So, to recap, this is due to the fix for #860465, which is part of 1.3.6-5. It appears that in order to fix plymouth handling, the service file was modified to include a number of things slim currently does *not* support: - BusName=org.freedesktop.DisplayManager which was added to the unit file silently converts the unit to Type=dbus and instructs systemd to expect slim to bind the org.freedesktop.DisplayManager endpoint on the system bus before it marks the service as running. However, grepping the source indicates that slim is completely unaware of dbus. Thus this directive causes systemd to endlessly restart slim every TimeoutStartSec seconds. - Moreover, slim seems to not be able to stop plymouth by itself, contrary to what is stated in the service file. This is also reflected by the manual handling of plymouth in the upstart and initscript files. The attached debdiff resolves the restart loop, while ensuring that slim plays nice with plymouth. If nobody responds, I intend to NMU the package tomorrow. Regards, Apollon diff -Nru slim-1.3.6/debian/changelog slim-1.3.6/debian/changelog --- slim-1.3.6/debian/changelog 2017-04-23 19:14:21.0 +0300 +++ slim-1.3.6/debian/changelog 2017-05-02 16:48:36.0 +0300 @@ -1,3 +1,11 @@ +slim (1.3.6-5.1) unstable; urgency=medium + + * Non-maintainer upload. + * slim.service: drop BusName and Conflicts/OnFailure=plymouth-quit.service +(Closes: #861474) + + -- Apollon Oikonomopoulos Tue, 02 May 2017 16:48:36 +0300 + slim (1.3.6-5) unstable; urgency=medium * Fix bugged Debian-Lines theme. (Closes: #776693) diff -Nru slim-1.3.6/debian/patches/fix-missing-plymouth-handling.patch slim-1.3.6/debian/patches/fix-missing-plymouth-handling.patch --- slim-1.3.6/debian/patches/fix-missing-plymouth-handling.patch 2017-04-23 18:38:28.0 +0300 +++ slim-1.3.6/debian/patches/fix-missing-plymouth-handling.patch 2017-05-02 16:46:20.0 +0300 @@ -5,20 +5,11 @@ --- a/slim.service +++ b/slim.service -@@ -2,7 +2,16 @@ +@@ -1,6 +1,6 @@ + [Unit] Description=SLiM Simple Login Manager - After=systemd-user-sessions.service +-After=systemd-user-sessions.service ++After=systemd-user-sessions.service plymouth-quit.service -+# replaces plymouth-quit since slim quits plymouth on its own -+Conflicts=plymouth-quit.service -+After=plymouth-quit.service -+ -+# slim takes responsibility for stopping plymouth, so if it fails -+# for any reason, make sure plymouth still stops -+OnFailure=plymouth-quit.service -+ [Service] ExecStartPre=/bin/sh -c '[ "$(cat /etc/X11/default-display-manager 2>/dev/null)" = "/usr/bin/slim" ]' - ExecStart=/usr/bin/slim -nodaemon - Restart=always -+BusName=org.freedesktop.DisplayManager
Processed: Re: slim: Session restarts in a loop renedering whole system useless.
Processing control commands: > tags -1 patch Bug #861474 [slim] slim: Session restarts in a loop rendering the whole system useless Added tag(s) patch. -- 861474: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861474 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#861474: slim: Session restarts in a loop renedering whole system useless.
Same problem here on debian testing with 1.3.6-5. My current workaround: - Open a root shell (via ctrl+alt+f1) - Stop slim via: /etc/init.d/slim stop (it is stopped via systemctl) - Start slim by simply entering slim I would guess it has something to do with the systemd startup scripts. Cheers Ruwen signature.asc Description: OpenPGP digital signature
Bug#861656: BROKEN: 0.4.11 lacks support for get_info and URLs with a prefix path
On 05/02/2017 01:18 PM, Antoine Musso wrote: > Source: python-jenkins > Version: 0.4.11-1 > Severity: important > > python-jenkins 0.4.11 is partly broken. There is at least two severe > breakages: > > * does not support a server URLs using a prefix such as: > http://example.org/ci > * creating a node raises a 400 bad request > > I would advise to drop 0.4.11 from testing and use 0.4.12 instead. Hi, How come this issue is only reported now? The package was uploaded in this version more than a year ago. The main reason why I maintain python-jenkins, is for Jenkins Jobs Builder. I believe it's not affected by this, is it? What do you mean by "creating a node"? Last, do you believe the release team will accept using 0.4.12 instead? I do not want to upload to later on figure out the release team refuses the upload. I'm asking for pre-approval. If it's not granted, I'll keep the old version in testing. Cheers, Thomas Goirand (zigo)
Processed: severity of 861656 is grave
Processing commands for cont...@bugs.debian.org: > severity 861656 grave Bug #861656 [src:python-jenkins] BROKEN: 0.4.11 lacks support for get_info and URLs with a prefix path Ignoring request to change severity of Bug 861656 to the same value. > thanks Stopping processing here. Please contact me if you need assistance. -- 861656: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861656 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity of 861656 is grave
Processing commands for cont...@bugs.debian.org: > severity 861656 grave Bug #861656 [src:python-jenkins] BROKEN: 0.4.11 lacks support for get_info and URLs with a prefix path Severity set to 'grave' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 861656: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861656 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#770369: Bug#737491: eterm: Occurs on upgrade to Jessie from Wheezy
Hi, Thanks for your help! I think this bug is the same than bug #770369. I tried to file this as a followup to the existing bug but must have messed up with my usage of `reportbug`; sorry! This bug is close in stretch (testing). As it is expected the release stretch occurs soon, the easiest way is: 1. To wait for the release of stretch to get this problem fixed when you upgrade from Wheezy to Stretch. 2. Downgrade the Eterm package to the version in Jessie so you can use it until the upgrade to Stretch. Do you mean wheezy? Do you have a command to hand that can do that for me or is it best to fetch the .deb out of the appropriate package pool? I am trying to maintain Eterm package, but my process of learning to do it properly is getting a little long so I have not prepared a new Eterm package. I have checked the fix proposed and my local Eterm package is working in Jessie-amd64 (thanks to Charles Gorand and Arnaud Ceyroll for the fix). Andy, if you want I can send you my local package to your e-mail, so you can use it. For Santiago Vila (or other developers) I have modified the source package in Jessie by performing the fix suggested by Arnaud and Charles to the command.c file, just recompiled in my Jessie system and the new Eterm package is working again. Maybe I can try to build my own local package? Are you able to send me the patch for the Jessie package? Maybe it is worth to propose an update for Jessie so the package will be usable again for all the users. I will have some spare time after the middle of June, so I would be able to apply the fix in the correct way (I have just edited the source to test it, I have to read deeper the maint-guide to do it in the right way). After the release of Stretch I will try to fix the UTF8 problem in Eterm to finally maintain this package. Thanks for your help and for giving the time. Regards, @ndy -- andy...@ashurst.eu.org http://www.ashurst.eu.org/ 0x7EBA75FF
Processed: Re: Bug#861108: live-build: stretch image produced with default configuration does not boot
Processing control commands: > severity -1 normal Bug #861108 [live-build] live-build: stretch image produced with default configuration does not boot Severity set to 'normal' from 'grave' > reassign -1 src:live-manual Bug #861108 [live-build] live-build: stretch image produced with default configuration does not boot Bug reassigned from package 'live-build' to 'src:live-manual'. No longer marked as found in versions live-build/1:20170213. Ignoring request to alter fixed versions of bug #861108 to the same values previously set > retitle -1 live-manual: minimum RAM requirements not documented Bug #861108 [src:live-manual] live-build: stretch image produced with default configuration does not boot Changed Bug title to 'live-manual: minimum RAM requirements not documented' from 'live-build: stretch image produced with default configuration does not boot'. -- 861108: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861108 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#861108: live-build: stretch image produced with default configuration does not boot
Control: severity -1 normal Control: reassign -1 src:live-manual Control: retitle -1 live-manual: minimum RAM requirements not documented On Tue, May 02, 2017 at 10:54:02AM +0200, Lukas Schwaighofer wrote: > Hi, > > I think the problem reported by Antonio is because the default RAM size > of kvm is too little. > > > Antonio: Can you retry with `-m 256M` or even `-m 512M` to have more > than the default of 128M RAM? Yes, 256+ works. I guess we just need to have that documented, then, at least in the QEMU section. Now that I think about it it all makes sense, but since the actual error message is not very insightful, people really need to know this beforehand (i.e. if you don't have enough RAM, you will hit such and such error message) signature.asc Description: PGP signature
Processed: bug 860646 is forwarded to https://github.com/jacobsa/ogletest/pull/30
Processing commands for cont...@bugs.debian.org: > forwarded 860646 https://github.com/jacobsa/ogletest/pull/30 Bug #860646 [src:golang-github-jacobsa-ogletest] golang-github-jacobsa-ogletest: FTBFS on i386: dh_auto_test: go test -v -p 1 github.com/jacobsa/ogletest github.com/jacobsa/ogletest/srcutil github.com/jacobsa/ogletest/test_cases github.com/jacobsa/ogletest/test_cases/mock_image returned exit code 1 Set Bug forwarded-to-address to 'https://github.com/jacobsa/ogletest/pull/30'. > thanks Stopping processing here. Please contact me if you need assistance. -- 860646: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860646 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#857995: respawn loop due to insufficient permissions
Am 02.05.2017 um 13:43 schrieb Michael Biebl: > After further investigation, this particular information is incorrect, > it seems. It's not the main gdm3 process which dies. So the respawning > is not done by systemd, but by the main gdm process: Which seems to be a result of the session scope of Debian-gdm not being stopped when the gdm service is stopped, so if you run systemctl stop gdm.service, the session scope is still running, along with all its processes: > │ └─user-109.slice > │ ├─user@109.service > │ │ ├─at-spi-dbus-bus.service > │ │ │ ├─5156 /usr/lib/at-spi2-core/at-spi-bus-launcher > │ │ │ ├─5161 /usr/bin/dbus-daemon > --config-file=/usr/share/defaults/at-spi2/accessibility.conf --nofork > --print-address 3 > │ │ │ └─5163 /usr/lib/at-spi2-core/at-spi2-registryd --use-gnome-session > │ │ ├─dbus.service > │ │ │ ├─5133 /usr/bin/dbus-daemon --session --address=systemd: --nofork > --nopidfile --systemd-activation > │ │ │ └─5174 /usr/lib/x86_64-linux-gnu/gconf/gconfd-2 > │ │ ├─xdg-permission-store.service > │ │ │ └─5180 /usr/lib/flatpak/xdg-permission-store > │ │ └─init.scope > │ │ ├─5126 /lib/systemd/systemd --user > │ │ └─5127 (sd-pam) > │ └─session-c4.scope > │ ├─5122 gdm-session-worker [pam/gdm-launch-environment] > │ ├─5131 /usr/lib/gdm3/gdm-wayland-session gnome-session --autostart > /usr/share/gdm/greeter/autostart > │ ├─5135 /usr/lib/gnome-session/gnome-session-binary --autostart > /usr/share/gdm/greeter/autostart > │ ├─5143 /usr/bin/gnome-shell > │ ├─5149 /usr/bin/Xwayland :1024 -rootless -noreset -listen 4 -listen 5 > -displayfd 6 > │ ├─5169 /usr/bin/pulseaudio --start --log-target=syslog > │ ├─5172 /usr/lib/x86_64-linux-gnu/pulse/gconf-helper > │ └─5189 /usr/lib/gnome-settings-daemon/gnome-settings-daemon As a workaround, I added ExecStopPost=/bin/loginctl kill-user Debian-gdm to gdm.service. This seems enough to make systemctl restart gdm.service work -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#857995: respawn loop due to insufficient permissions
Am 17.03.2017 um 01:06 schrieb Michael Biebl: > Am 17.03.2017 um 00:56 schrieb Michael Biebl: >> To reproduce the problem: >> >> reboot, login, logout, switch to console, login as root, systemctl >> restart gdm3. >> >> The result ist a constantly respawned gdm3.service which fails to start >> properly due to insufficient permissions. > > The constant respawns are done by systemd due to > > Restart=always > RestartSec=1s > > in gdm.service After further investigation, this particular information is incorrect, it seems. It's not the main gdm3 process which dies. So the respawning is not done by systemd, but by the main gdm process: Running journalctl -b -1 -u gdm, I get > Mai 02 13:29:52 pluto systemd[1]: Starting GNOME Display Manager... > Mai 02 13:29:52 pluto systemd[1]: Started GNOME Display Manager. > Mai 02 13:29:52 pluto gdm-launch-environment][755]: > pam_unix(gdm-launch-environment:session): session opened for user Debian-gdm > by (uid=0) > Mai 02 13:30:00 pluto gdm-password][1509]: pam_unix(gdm-password:session): > session opened for user michael by (uid=0) > Mai 02 13:30:48 pluto systemd[1]: Stopping GNOME Display Manager... > Mai 02 13:30:48 pluto gdm3[740]: GLib: g_hash_table_find: assertion 'version > == hash_table->version' failed > Mai 02 13:30:48 pluto systemd[1]: Stopped GNOME Display Manager. > Mai 02 13:30:48 pluto systemd[1]: Starting GNOME Display Manager... > Mai 02 13:30:48 pluto systemd[1]: Started GNOME Display Manager. > Mai 02 13:30:48 pluto gdm-launch-environment][2286]: > pam_unix(gdm-launch-environment:session): session opened for user Debian-gdm > by (uid=0) > Mai 02 13:30:48 pluto gdm3[2282]: GdmDisplay: display lasted 0.187789 seconds > Mai 02 13:30:48 pluto gdm3[2282]: Child process -2290 was already dead. > Mai 02 13:30:48 pluto gdm3[2282]: Child process 2286 was already dead. > Mai 02 13:30:48 pluto gdm3[2282]: Unable to kill session worker process > Mai 02 13:30:48 pluto gdm-launch-environment][2306]: > pam_unix(gdm-launch-environment:session): session opened for user Debian-gdm > by (uid=0) > Mai 02 13:30:48 pluto gdm3[2282]: Child process -2309 was already dead. > Mai 02 13:30:48 pluto gdm3[2282]: Child process 2306 was already dead. > Mai 02 13:30:48 pluto gdm3[2282]: Unable to kill session worker process > Mai 02 13:30:48 pluto gdm-launch-environment][2314]: > pam_unix(gdm-launch-environment:session): session opened for user Debian-gdm > by (uid=0) > Mai 02 13:30:48 pluto gdm3[2282]: GdmDisplay: display lasted 0.128089 seconds > Mai 02 13:30:48 pluto gdm3[2282]: Child process -2317 was already dead. > Mai 02 13:30:48 pluto gdm3[2282]: Child process 2314 was already dead. > Mai 02 13:30:48 pluto gdm3[2282]: Unable to kill session worker process [and so on, until forcefully rebooting the system] > Mai 02 13:30:50 pluto systemd[1]: Stopping GNOME Display Manager... > Mai 02 13:30:51 pluto gdm3[2282]: GdmLocalDisplayFactory: Failed to issue > method call: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message > recipient disconnected from message bus without replying > Mai 02 13:30:51 pluto gdm3[2282]: Child process -2518 was already dead. > Mai 02 13:30:51 pluto gdm3[2282]: Child process 2515 was already dead. > Mai 02 13:30:51 pluto systemd[1]: Stopped GNOME Display Manager. > This means, we can't workaround this issue by dropping Restart=always from gdm.service -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#770369: Bug#737491: eterm: Occurs on upgrade to Jessie from Wheezy
(I am writing to bugs #737491 and #770369 as the fix is the same) Dear Andy, I think this bug is the same than bug #770369. This bug is close in stretch (testing). As it is expected the release stretch occurs soon, the easiest way is: 1. To wait for the release of stretch to get this problem fixed when you upgrade from Wheezy to Stretch. 2. Downgrade the Eterm package to the version in Jessie so you can use it until the upgrade to Stretch. I am trying to maintain Eterm package, but my process of learning to do it properly is getting a little long so I have not prepared a new Eterm package. I have checked the fix proposed and my local Eterm package is working in Jessie-amd64 (thanks to Charles Gorand and Arnaud Ceyroll for the fix). Andy, if you want I can send you my local package to your e-mail, so you can use it. For Santiago Vila (or other developers) I have modified the source package in Jessie by performing the fix suggested by Arnaud and Charles to the command.c file, just recompiled in my Jessie system and the new Eterm package is working again. Maybe it is worth to propose an update for Jessie so the package will be usable again for all the users. I will have some spare time after the middle of June, so I would be able to apply the fix in the correct way (I have just edited the source to test it, I have to read deeper the maint-guide to do it in the right way). After the release of Stretch I will try to fix the UTF8 problem in Eterm to finally maintain this package. Sincerely, Jose
Bug#860646: Patch available
Control: tags -1 patch upstream
The attached debdiff makes the package build cleanly on i386 (also
tested on amd64). It extends upstream's existing code for sanitizing the
test output to replace all instances of `runtime.call\d+' with
`runtime.callXX', so that the test output will not vary between
architectures.
If nobody objects, I intend to NMU the package tomorrow and forward the
fix upstream.
Regards,
Apollon
diff -Nru golang-github-jacobsa-ogletest-0.0~git20150610/debian/changelog golang-github-jacobsa-ogletest-0.0~git20150610/debian/changelog
--- golang-github-jacobsa-ogletest-0.0~git20150610/debian/changelog 2017-01-11 19:42:43.0 +0200
+++ golang-github-jacobsa-ogletest-0.0~git20150610/debian/changelog 2017-05-02 14:14:37.0 +0300
@@ -1,3 +1,11 @@
+golang-github-jacobsa-ogletest (0.0~git20150610-6.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Handle architecture-dependent output in panicking test. Fixes FTBFS on
+i386 (Closes: #860646).
+
+ -- Apollon Oikonomopoulos Tue, 02 May 2017 14:14:37 +0300
+
golang-github-jacobsa-ogletest (0.0~git20150610-6) unstable; urgency=medium
* Team upload.
diff -Nru golang-github-jacobsa-ogletest-0.0~git20150610/debian/files golang-github-jacobsa-ogletest-0.0~git20150610/debian/files
--- golang-github-jacobsa-ogletest-0.0~git20150610/debian/files 2017-01-11 19:40:53.0 +0200
+++ golang-github-jacobsa-ogletest-0.0~git20150610/debian/files 1970-01-01 02:00:00.0 +0200
@@ -1 +0,0 @@
-golang-github-jacobsa-ogletest_0.0~git20150610-6_source.buildinfo devel extra
diff -Nru golang-github-jacobsa-ogletest-0.0~git20150610/debian/patches/mangle-runtime.callXX.patch golang-github-jacobsa-ogletest-0.0~git20150610/debian/patches/mangle-runtime.callXX.patch
--- golang-github-jacobsa-ogletest-0.0~git20150610/debian/patches/mangle-runtime.callXX.patch 1970-01-01 02:00:00.0 +0200
+++ golang-github-jacobsa-ogletest-0.0~git20150610/debian/patches/mangle-runtime.callXX.patch 2017-05-02 14:14:37.0 +0300
@@ -0,0 +1,49 @@
+Author: Apollon Oikonomopoulos
+Description: Mangle arch-dependent runtime.callXX tokens in test output
+ Strip architecture-dependent strings from the test output, as these break the
+ panicking test (at least) on i386.
+Bug-Debian: 860646
+Forwarded: no
+Last-Update: 2017-05-02
+--- a/integration_test.go
b/integration_test.go
+@@ -142,6 +142,10 @@
+ timingRe4 := regexp.MustCompile(`SlowTest \([0-9.]+ms\)`)
+ o = timingRe4.ReplaceAll(o, []byte("SlowTest (1234ms)"))
+
++ // Replace arch-dependent runtime.call32 etc. with runtime.callXX
++ callRe := regexp.MustCompile(`runtime.call\d+`)
++ o = callRe.ReplaceAll(o, []byte("runtime.callXX"))
++
+ return o
+ }
+
+--- a/test_cases/golden.panicking_test
b/test_cases/golden.panicking_test
+@@ -6,7 +6,7 @@
+
+ github.com/jacobsa/ogletest/somepkg_test.(*PanickingTest).ExplicitPanic
+ some_file.txt:0
+-runtime.call32
++runtime.callXX
+ some_file.txt:0
+ reflect.Value.call
+ some_file.txt:0
+@@ -24,7 +24,7 @@
+ some_file.txt:0
+ github.com/jacobsa/ogletest/somepkg_test.(*PanickingTest).ExplicitPanicInHelperFunction
+ some_file.txt:0
+-runtime.call32
++runtime.callXX
+ some_file.txt:0
+ reflect.Value.call
+ some_file.txt:0
+@@ -40,7 +40,7 @@
+
+ github.com/jacobsa/ogletest/somepkg_test.(*PanickingTest).NilPointerDerefence
+ some_file.txt:0
+-runtime.call32
++runtime.callXX
+ some_file.txt:0
+ reflect.Value.call
+ some_file.txt:0
diff -Nru golang-github-jacobsa-ogletest-0.0~git20150610/debian/patches/series golang-github-jacobsa-ogletest-0.0~git20150610/debian/patches/series
--- golang-github-jacobsa-ogletest-0.0~git20150610/debian/patches/series 2017-01-11 19:29:43.0 +0200
+++ golang-github-jacobsa-ogletest-0.0~git20150610/debian/patches/series 2017-05-02 14:14:37.0 +0300
@@ -1,2 +1,3 @@
803320.patch
dump-golden-files.patch
+mangle-runtime.callXX.patch
Processed: Patch available
Processing control commands: > tags -1 patch upstream Bug #860646 [src:golang-github-jacobsa-ogletest] golang-github-jacobsa-ogletest: FTBFS on i386: dh_auto_test: go test -v -p 1 github.com/jacobsa/ogletest github.com/jacobsa/ogletest/srcutil github.com/jacobsa/ogletest/test_cases github.com/jacobsa/ogletest/test_cases/mock_image returned exit code 1 Added tag(s) patch and upstream. -- 860646: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860646 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#861484: [Pkg-julia-devel] Bug#861484: julia: FTBFS on arm64
Hi Julien On 29/04/2017 17:13, Julien Cristau wrote: julia's build looks unreliable on arm64, it sometimes (often?) segfaults: https://buildd.debian.org/status/fetch.php?pkg=julia&arch=arm64&ver=0.4.7-6%2Bb3&stamp=1493471432&raw=0 https://buildd.debian.org/status/fetch.php?pkg=julia&arch=arm64&ver=0.4.7-6%2Bb1&stamp=1493124448&raw=0 https://buildd.debian.org/status/fetch.php?pkg=julia&arch=arm64&ver=0.4.7-5&stamp=1485154552&raw=0 Please investigate and fix. I've been unable to reproduce this failure on asachi.debian.org. It built without failure ten times yesterday, and again once today. There is definitely something wrong though, according to the julia arm64 build logs [1], the build has failed in the same way since January every time it was attempted on arm-arm-04. The most recent success a week ago was on arm-arm-03 and against llvm-3.8/1:3.8.1-22 which should have included the versioned symbols. Regards Graham [1] https://buildd.debian.org/status/logs.php?pkg=julia&arch=arm64
Bug#860646: Failure analysis
Hi, The build failure is due to panicking_test producing different output on i386 than what is expected by the golden file. The difference is that all occurrences of `runtime.call32' in the golden file are replaced by `runtime.call16' in the actual output. --- stretch/build/golang-github-jacobsa-ogletest-0.0~git20150610/obj-i686-linux-gnu/src/github.com/jacobsa/ogletest/test_cases/golden.panicking_test 2017-05-02 13:37:31.490452706 +0300 +++ golang-github-jacobsa-ogletest-0.0~git20150610/test_cases/golden.panicking_test 2017-05-02 13:18:21.0 +0300 @@ -6,7 +6,7 @@ github.com/jacobsa/ogletest/somepkg_test.(*PanickingTest).ExplicitPanic some_file.txt:0 -runtime.call16 +runtime.call32 some_file.txt:0 reflect.Value.call some_file.txt:0 @@ -24,7 +24,7 @@ some_file.txt:0 github.com/jacobsa/ogletest/somepkg_test.(*PanickingTest).ExplicitPanicInHelperFunction some_file.txt:0 -runtime.call16 +runtime.call32 some_file.txt:0 reflect.Value.call some_file.txt:0 @@ -40,7 +40,7 @@ github.com/jacobsa/ogletest/somepkg_test.(*PanickingTest).NilPointerDerefence some_file.txt:0 -runtime.call16 +runtime.call32 some_file.txt:0 reflect.Value.call some_file.txt:0 This is consistent with go's implementations of `reflectcall' for i386[1] and amd64[2] respectively. [1] https://golang.org/src/runtime/asm_386.s#L450 [2] https://golang.org/src/runtime/asm_amd64.s#L446 All in all, everything works as expected. Since part of the test output is architecture-dependent, upstream's test suite should take that into account. For the time being we could either disable this test completely on non-amd64 architectures, or patch integration_test.go to mangle all `runtime.call[0-9]+' tokens before comparing output and expected streams. Regards, Apollon
Bug#861204: marked as done (deb-systemd-invoke: fails to handle units with escaped characters)
Your message dated Tue, 02 May 2017 10:49:15 +
with message-id
and subject line Bug#861204: fixed in init-system-helpers 1.48
has caused the Debian Bug report #861204,
regarding deb-systemd-invoke: fails to handle units with escaped characters
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.)
--
861204: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861204
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: init-system-helpers
Version: 1.47
Severity: serious
Tags: patch
Hi,
to fix #856429 I need to handle a unit with an escaped character
correctly in the maintainer scripts generated by dh_systemd*.
Unfortunately deb-systemd-invoke does not quote the unit name
properly in a systemctl call, so it fails to handle the unit.
A patch is attached, with it deb-systemd-invoke works as expected.
I did not test my changes to t/001-deb-systemd-helper.t as I don't
have the necessary perl module installed and didn't want to mess
with CPAN. But I'd assume its correct.
Thanks for fixing,
Bernd
--
Bernd ZeimetzDebian GNU/Linux Developer
http://bzed.dehttp://www.debian.org
GPG Fingerprint: ECA1 E3F2 8E11 2432 D485 DD95 EB36 171A 6FF9 435F
From f506723313b8b85e062b61ccda5e31d7adc3a176 Mon Sep 17 00:00:00 2001
From: Bernd Zeimetz
Date: Tue, 25 Apr 2017 21:40:00 +0200
Subject: [PATCH] Handle units with escaped characters correctly.
Also see
https://www.freedesktop.org/software/systemd/man/systemd-escape.html
---
script/deb-systemd-invoke | 2 +-
t/001-deb-systemd-helper.t | 10 +-
2 files changed, 6 insertions(+), 6 deletions(-)
diff --git a/script/deb-systemd-invoke b/script/deb-systemd-invoke
index 4255d06..a4b3fbc 100755
--- a/script/deb-systemd-invoke
+++ b/script/deb-systemd-invoke
@@ -85,7 +85,7 @@ if ($action eq "start" || $action eq "restart") {
my $global_exit_code = 0;
for my $unit (@units) {
my $unit_installed = 0;
-my $enabled_output = `/bin/systemctl is-enabled -- $unit`;
+my $enabled_output = `/bin/systemctl is-enabled -- '$unit'`;
# matching enabled and enabled-runtime as an installed non static unit
if ($enabled_output =~ /enabled/) {
$unit_installed = 1;
diff --git a/t/001-deb-systemd-helper.t b/t/001-deb-systemd-helper.t
index 64332e3..2d5da28 100644
--- a/t/001-deb-systemd-helper.t
+++ b/t/001-deb-systemd-helper.t
@@ -54,7 +54,7 @@ unless ($ENV{'TEST_ON_REAL_SYSTEM'}) {
# ┃ Verify “is-enabled” is not true for a random, non-existing unit file. ┃
# ┗━━━┛
-my ($fh, $random_unit) = tempfile('unitX',
+my ($fh, $random_unit) = tempfile('unit\x2dX',
SUFFIX => '.service',
TMPDIR => 1,
UNLINK => 1);
@@ -303,13 +303,13 @@ ExecStart=/bin/sleep 1
[Install]
WantedBy=multi-user.target
-Alias=footest.service
+Alias=foo\x2dtest.service
EOT
close($fh);
isnt_enabled($random_unit);
-isnt_enabled('footest.service');
-my $alias_path = "/etc/systemd/system/footest.service";
+isnt_enabled('foo\x2dtest.service');
+my $alias_path = "/etc/systemd/system/foo\x2dtest.service";
ok(! -l $alias_path, 'alias link does not exist yet');
$retval = system("DPKG_MAINTSCRIPT_PACKAGE=test $dsh enable $random_unit");
is($retval, 0, "enable command succeeded");
@@ -376,7 +376,7 @@ EOT
close($fh);
isnt_enabled($random_unit);
-isnt_enabled('footest.service');
+isnt_enabled('foo\x2dtest.service');
# note that in this case $alias_path and $mask_path are identical
$retval = system("DPKG_MAINTSCRIPT_PACKAGE=test $dsh enable $random_unit");
is($retval, 0, "enable command succeeded");
--
2.11.0
--- End Message ---
--- Begin Message ---
Source: init-system-helpers
Source-Version: 1.48
We believe that the bug you reported is fixed in the latest version of
init-system-helpers, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 861...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Bernd Zeimetz (supplier of updated init-system-helpers
package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
For
Bug#861515: reproducibile here
I have set up an i386 debci lxc testbed with: debci_arch=i386 debci setup then confirmed that the lxc container has indeed been created: lxc-ls --fancy NAME STATE AUTOSTART GROUPS IPV4 IPV6 adt-sid-amd64 STOPPED 0 - -- adt-sid-i386 STOPPED 0 - -- and run the test suite from the source package in the archive with: adt-run --user debci --output-dir /tmp/output-dir node-grunt-contrib-copy --- lxc --sudo adt-sid-i386 it fails with: ✖ copy - timestamp_equal AssertionError: 1457124645257 == 1457124645000 at Object.equal (/usr/lib/nodejs/nodeunit/lib/types.js:83:39) at Object.exports.copy.timestamp_equal (/tmp/autopkgtest-virt-lxc.shared.wv8ud5o5/downtmp/build.iwX/node-grunt-contrib-copy-1.0.0/test/copy_test.js:92:10) at Object. (/usr/lib/nodejs/nodeunit/lib/core.js:236:16) at Object. (/usr/lib/nodejs/nodeunit/lib/core.js:236:16) at /usr/lib/nodejs/nodeunit/lib/core.js:236:16 at Object.exports.runTest (/usr/lib/nodejs/nodeunit/lib/core.js:70:9) at /usr/lib/nodejs/nodeunit/lib/core.js:118:25 at /usr/lib/nodejs/nodeunit/deps/async.js:513:13 at iterate (/usr/lib/nodejs/nodeunit/deps/async.js:123:13) at /usr/lib/nodejs/nodeunit/deps/async.js:134:25 at /usr/lib/nodejs/nodeunit/deps/async.js:515:17 at Immediate._onImmediate (/usr/lib/nodejs/nodeunit/lib/types.js:146:17) at processImmediate [as _immediateCallback] (timers.js:396:17) AssertionError: 1457124645257 == 1457124645000 at Object.equal (/usr/lib/nodejs/nodeunit/lib/types.js:83:39) at Object.exports.copy.timestamp_equal (/tmp/autopkgtest-virt-lxc.shared.wv8ud5o5/downtmp/build.iwX/node-grunt-contrib-copy-1.0.0/test/copy_test.js:93:10) at Object. (/usr/lib/nodejs/nodeunit/lib/core.js:236:16) at Object. (/usr/lib/nodejs/nodeunit/lib/core.js:236:16) at /usr/lib/nodejs/nodeunit/lib/core.js:236:16 at Object.exports.runTest (/usr/lib/nodejs/nodeunit/lib/core.js:70:9) at /usr/lib/nodejs/nodeunit/lib/core.js:118:25 at /usr/lib/nodejs/nodeunit/deps/async.js:513:13 at iterate (/usr/lib/nodejs/nodeunit/deps/async.js:123:13) at /usr/lib/nodejs/nodeunit/deps/async.js:134:25 at /usr/lib/nodejs/nodeunit/deps/async.js:515:17 at Immediate._onImmediate (/usr/lib/nodejs/nodeunit/lib/types.js:146:17) at processImmediate [as _immediateCallback] (timers.js:396:17) ✔ copy - timestamp_changed FAILURES: 2/17 assertions failed (234ms) AFAICT this seems related to this upstream PR: https://github.com/gruntjs/grunt-contrib-copy/pull/268, that claims to have fixed a similar problem I'll try to bring this to the attention of upstream over there.
Bug#857855: redis FTBFS on arm64: Executing test client: NOREPLICAS Not enough good slaves to write..
severity 857855 important thanks > It built on arm64 on the second attempt. So you can probably downgrade > this bug, or close it altogether if nobody can reproduce the build > failure. Lets downgrade it for now... Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Processed: Re: redis FTBFS on arm64: Executing test client: NOREPLICAS Not enough good slaves to write..
Processing commands for cont...@bugs.debian.org: > severity 857855 important Bug #857855 [src:redis] redis FTBFS on arm64: Executing test client: NOREPLICAS Not enough good slaves to write.. Severity set to 'important' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 857855: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857855 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#857855: redis FTBFS on arm64: Executing test client: NOREPLICAS Not enough good slaves to write..
It built on arm64 on the second attempt. So you can probably downgrade this bug, or close it altogether if nobody can reproduce the build failure.
Bug#845786: gammaray FTBFS on arm64, armel, mips* and s390x: QFatal in quickinspectortest
It worked on arm64 on the third attempt. The second failure was different from the first failure. So perhaps worth trying several times on other architectures.
Bug#861108: live-build: stretch image produced with default configuration does not boot
Hi, I think the problem reported by Antonio is because the default RAM size of kvm is too little. Antonio: Can you retry with `-m 256M` or even `-m 512M` to have more than the default of 128M RAM? Yves: I cannot reproduce the problems reported by you. In particular, microcode packages should not be installed by default (as they are in non-free). If you have installed any of the microcode packages, the initrd follows a special format (see [1]): The initrd consists of an uncompressed cpio archive only holding the microcode updates followed by a compressed cpio archive with the remainder of the initrd. This is a little bit tricky to uncompress, so when unpacking it it may seem like the initrd is broken. You can try the following to unpack the whole initrd into your current working directory: (cpio -id --no-absolute-filenames; zcat | cpio -id --no-absolute-filenames) < /path/to/initrd.img Regards Lukas [1] https://www.kernel.org/doc/Documentation/x86/early-microcode.txt pgp3jRQBsGCJW.pgp Description: OpenPGP digital signature
Bug#860608: [pkg-golang-devel] Bug#860608: Bug#860608: golang: FTBFS: Go version is "go1.6.1", ignoring -next /<>/api/next.txt
On 2 May 2017 at 19:23, Michael Stapelberg wrote: > Sorry for the late reply, I’ve been swamped. > > On Fri, Apr 21, 2017 at 10:28 AM, Niels Thykier wrote: > >> Michael Stapelberg: >> > On Fri, Apr 21, 2017 at 9:45 AM, Niels Thykier >> wrote: >> > >> >> [...] >> >>> >> >> >> >> They seem to be arch:all packages. We cannot binNMU arch:all packages, >> >> only architecture dependent ones. :-/ >> >> >> > >> > Okay. How do you suggest we rectify this issue instead, then? >> > >> >> A (possibly "no change") sourceful upload to force a rebuild of the >> arch:all package. >> > > A sourceful upload for which source package? src:golang has been removed > from unstable and testing since 2016-10. > Well, for this bug report specifically, the packages that have a built-using on golang 2:1.6.1-2, i.e. these: mwhudson@aeglos:~/tmp$ chdist grep-dctrl-packages sid -FBuilt-Using 'golang (= 2:1.6.1-2)' -sPackage Package: golang-github-armon-go-metrics-dev Package: golang-github-gosexy-gettext-dev Package: golang-github-hashicorp-go-msgpack-dev Package: golang-github-stretchr-objx-dev Package: golang-github-kr-pty-dev Package: golang-github-armon-go-metrics-dev Package: golang-github-gosexy-gettext-dev Package: golang-github-hashicorp-go-msgpack-dev Package: golang-github-stretchr-objx-dev Package: golang-github-kr-pty-dev As you can see these are all -dev packages, so the Built-Using is bogus and should simply be dropped from the package. There are quite a few more packages that reference obsolete golang packages in their Built-Using... Cheers, mwh > To avoid further delays, is this something you could NMU for us? If so, > I’d much appreciate that. Thanks! > > -- > Best regards, > Michael > > ___ > pkg-golang-devel mailing list > pkg-golang-de...@lists.alioth.debian.org > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-golang-devel >
Processed: Re: gpsshogi FTBFS on i386: error: '__builtin_ia32_psubd128' was not declared in this scope
Processing control commands:
> reassign -1 src:libosl 0.8.0-1.3
Bug #861273 [src:gpsshogi] gpsshogi FTBFS on i386: error:
'__builtin_ia32_psubd128' was not declared in this scope
Bug reassigned from package 'src:gpsshogi' to 'src:libosl'.
No longer marked as found in versions gpsshogi/0.7.0-1.1.
Ignoring request to alter fixed versions of bug #861273 to the same values
previously set
Bug #861273 [src:libosl] gpsshogi FTBFS on i386: error:
'__builtin_ia32_psubd128' was not declared in this scope
Marked as found in versions libosl/0.8.0-1.3.
> close -1 0.8.0-1.4
Bug #861273 [src:libosl] gpsshogi FTBFS on i386: error:
'__builtin_ia32_psubd128' was not declared in this scope
Marked as fixed in versions libosl/0.8.0-1.4.
Bug #861273 [src:libosl] gpsshogi FTBFS on i386: error:
'__builtin_ia32_psubd128' was not declared in this scope
Marked Bug as done
> affects -1 + gpsshogi
Bug #861273 {Done: Andreas Beckmann } [src:libosl] gpsshogi
FTBFS on i386: error: '__builtin_ia32_psubd128' was not declared in this scope
Added indication that 861273 affects gpsshogi
--
861273: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861273
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#861273: gpsshogi FTBFS on i386: error: '__builtin_ia32_psubd128' was not declared in this scope
Control: reassign -1 src:libosl 0.8.0-1.3 Control: close -1 0.8.0-1.4 Control: affects -1 + gpsshogi On Wed, 26 Apr 2017 22:44:19 +0300 Adrian Bunk wrote: > /usr/include/osl/bits/quadInt.h: In member function 'osl::container::QuadInt& > osl::container::QuadInt::operator-=(const osl::container::QuadInt&)': > /usr/include/osl/bits/quadInt.h:104:43: error: '__builtin_ia32_psubd128' was > not declared in this scope Finally solved in libosl. Andreas
Bug#825355: marked as done (firefox-esr: FTBFS on arm64: Error while running startup cache precompilation)
Your message dated Tue, 02 May 2017 08:08:45 +
with message-id
and subject line Bug#825355: fixed in firefox-esr 45.8.0esr-1~deb8u1
has caused the Debian Bug report #825355,
regarding firefox-esr: FTBFS on arm64: Error while running startup cache
precompilation
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.)
--
825355: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825355
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: firefox-esr
Version: 45.1.1esr-1
Severity: serious
Hi,
firefox-esr failed to build on arm64:
Executing /«PKGBUILDDIR»/build-browser/dist/bin/xpcshell -g
/«PKGBUILDDIR»/build-browser/dist/bin/ -a
/«PKGBUILDDIR»/build-browser/dist/bin/ -f
/«PKGBUILDDIR»/toolkit/mozapps/installer/precompile_cache.js -e
precompile_startupcache("resource://gre/");
resource://gre/components/ActivityMessageConfigurator.js
resource://gre/modules/commonjs/sdk/ui/sidebar/contract.js
[...]
resource://gre/modules/workers/require.js
ERROR!! RequestSyncService - Failed to retrieve data from the database.
Executing /«PKGBUILDDIR»/build-browser/dist/bin/xpcshell -g
/«PKGBUILDDIR»/build-browser/dist/bin/ -a
/«PKGBUILDDIR»/build-browser/dist/bin/browser -f
/«PKGBUILDDIR»/toolkit/mozapps/installer/precompile_cache.js -e
precompile_startupcache("resource://app/");
resource://app/components/ChromeProfileMigrator.js
resource://app/components/ExperimentsService.js
[...]
resource://app/modules/Chat.jsm
resource://app/modules/ContentClick.jsm
Traceback (most recent call last):
File "/«PKGBUILDDIR»/toolkit/mozapps/installer/packager.py", line 406, in
main()
File "/«PKGBUILDDIR»/toolkit/mozapps/installer/packager.py", line 400, in main
args.source, gre_path, base)
File "/«PKGBUILDDIR»/toolkit/mozapps/installer/packager.py", line 161, in
precompile_cache
errors.fatal('Error while running startup cache precompilation')
File "/«PKGBUILDDIR»/python/mozbuild/mozpack/errors.py", line 103, in fatal
self._handle(self.FATAL, msg)
File "/«PKGBUILDDIR»/python/mozbuild/mozpack/errors.py", line 98, in _handle
raise ErrorMessage(msg)
mozpack.errors.ErrorMessage: Error: Error while running startup cache
precompilation
/«PKGBUILDDIR»/toolkit/mozapps/installer/packager.mk:41: recipe for target
'stage-package' failed
Logs at
https://buildd.debian.org/status/logs.php?pkg=firefox-esr&ver=45.1.1esr-1%2Bb1&arch=arm64
Cheers,
Emilio
--- End Message ---
--- Begin Message ---
Source: firefox-esr
Source-Version: 45.8.0esr-1~deb8u1
We believe that the bug you reported is fixed in the latest version of
firefox-esr, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 825...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Mike Hommey (supplier of updated firefox-esr package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Sat, 11 Feb 2017 07:34:43 +0900
Source: firefox-esr
Binary: firefox-esr iceweasel firefox-esr-dbg iceweasel-dbg firefox-esr-dev
iceweasel-dev firefox-esr-l10n-all iceweasel-l10n-all firefox-esr-l10n-ach
iceweasel-l10n-ach firefox-esr-l10n-af iceweasel-l10n-af firefox-esr-l10n-an
iceweasel-l10n-an firefox-esr-l10n-ar iceweasel-l10n-ar firefox-esr-l10n-as
iceweasel-l10n-as firefox-esr-l10n-ast iceweasel-l10n-ast firefox-esr-l10n-az
iceweasel-l10n-az firefox-esr-l10n-be iceweasel-l10n-be firefox-esr-l10n-bg
iceweasel-l10n-bg firefox-esr-l10n-bn-bd iceweasel-l10n-bn-bd
firefox-esr-l10n-bn-in iceweasel-l10n-bn-in firefox-esr-l10n-br
iceweasel-l10n-br firefox-esr-l10n-bs iceweasel-l10n-bs firefox-esr-l10n-ca
iceweasel-l10n-ca firefox-esr-l10n-cs iceweasel-l10n-cs firefox-esr-l10n-cy
iceweasel-l10n-cy firefox-esr-l10n-da iceweasel-l10n-da firefox-esr-l10n-de
iceweasel-l10n-de firefox-esr-l10n-dsb iceweasel-l10n-dsb firefox-esr-l10n-el
iceweasel-l10n-el firefox-esr-l10n-en-gb iceweasel-l10n-en-gb
firefox-esr-l10n-en-za
iceweasel-l10n-en-za firefox-esr-l10n-eo iceweasel-l10n-eo
firefox-esr-l10n-es-ar iceweasel-l10n-es-ar firefox-esr-l10n-es-cl
iceweasel-l10n-es-cl firefox-esr-l10n-es-es iceweasel-l10n-es-es
firefox-esr-l10n-es-mx iceweasel-l10n-es-mx firefox-esr-l10n-et
ice
Bug#861645: gsequencer FTBFS on mips/mipsel: FAIL: ags_xorg_application_context_test
Source: gsequencer Version: 0.8.0-1 Severity: serious https://buildd.debian.org/status/package.php?p=gsequencer&suite=sid ... make check-TESTS make[3]: Entering directory '/«PKGBUILDDIR»' make[4]: Entering directory '/«PKGBUILDDIR»' PASS: ags_thread_test PASS: ags_audio_application_context_test PASS: ags_turtle_test PASS: ags_devout_test PASS: ags_channel_test PASS: ags_audio_test PASS: ags_audio_signal_test PASS: ags_recall_test PASS: ags_port_test PASS: ags_recycling_test PASS: ags_pattern_test PASS: ags_notation_test PASS: ags_automation_test PASS: ags_midi_buffer_util_test PASS: ags_midi_builder_test ./test-driver: line 107: 7386 Segmentation fault "$@" > $log_file 2>&1 FAIL: ags_xorg_application_context_test gsequencer 0.8.0: ./test-suite.log # TOTAL: 16 # PASS: 15 # SKIP: 0 # XFAIL: 0 # FAIL: 1 # XPASS: 0 # ERROR: 0 .. contents:: :depth: 2 FAIL: ags_xorg_application_context_test === CUnit - A unit testing framework for C - Version 2.1-3 http://cunit.sourceforge.net/ ** Message: loading preferences from data[0x55df8774] ** Message: autosave-thread ** Message: false ** Message: simple-file ** Message: true ** Message: disable-feature ** Message: experimental ** Message: segmentation ** Message: 4/4 ** Message: model ** Message: super-threaded ** Message: super-threaded-scope ** Message: channel ** Message: lock-global ** Message: ags-thread ** Message: lock-parent ** Message: ags-recycling-thread ** Message: backend ** Message: alsa ** Message: device ** Message: hw:0,0 ** Message: samplerate ** Message: 44100 ** Message: buffer-size ** Message: 1024 ** Message: pcm-channels ** Message: 2 ** Message: dsp-channels ** Message: 2 ** Message: format ** Message: 16 ** Message: backend ** Message: alsa ** Message: device ** Message: hw:0,0 ** Message: samplerate ** Message: 44100 ** Message: buffer-size ** Message: 1024 ** Message: pcm-channels ** Message: 2 ** Message: dsp-channels ** Message: 2 ** Message: format ** Message: 16 ** Message: auto-sense ** Message: true Suite: AgsXorgApplicationContextTest Test: test of AgsXorgApplicationContext doing dispose ...** Message: Can't get the next card number: Success ** Message: Can't get the next card number: Success FAIL ags_xorg_application_context_test (exit status: 139) Testsuite summary for gsequencer 0.8.0 # TOTAL: 16 # PASS: 15 # SKIP: 0 # XFAIL: 0 # FAIL: 1 # XPASS: 0 # ERROR: 0 See ./test-suite.log Please report to jkraehemann-gu...@users.alioth.debian.org Makefile:9817: recipe for target 'test-suite.log' failed make[4]: *** [test-suite.log] Error 1
Bug#861644: gpsshogi: FTBFS on i386: kifuViewer.cc:368:6: error: prototype for 'void KifuViewer::AnalysisOnlineDialog::showPVInt(...) does not match any in class
Package: gpsshogi Version: 0.7.0-1.1 Severity: serious Justification: fails to build from source (but built successfully in the past) Hi, after fixing libosl in several iterations, gpsshogi starts to build on i386 without SSE related problems. But now it fails here: g++ -c -pipe -DOSL_SMP -fno-strict-aliasing -O2 -Wall -W -D_REENTRANT -fPIC -DOSL_SMP -DQT_NO_DEBUG -DQT_WIDGETS_LIB -DQT_GUI_LIB -DQT_XML_LIB -DQT_NETWORK_LIB -DQT_CORE_LIB -I. -I. -I../../../osl/full -I../../../osl/std -I../../../osl/core -I../../include -isystem /usr/include/i386-linux-gnu/qt5 -isystem /usr/include/i386-linux-gnu/qt5/QtWidgets -isystem /usr/include/i386-linux-gnu/qt5/QtGui -isystem /usr/include/i386-linux-gnu/qt5/QtXml -isystem /usr/include/i386-linux-gnu/qt5/QtNetwork -isystem /usr/include/i386-linux-gnu/qt5/QtCore -I. -I. -I/usr/lib/i386-linux-gnu/qt5/mkspecs/linux-g++ -o kifuViewer.o kifuViewer.cc kifuViewer.cc:368:6: error: prototype for 'void KifuViewer::AnalysisOnlineDialog::showPVInt(long unsigned int, int, size_t, double, int, const std::vector&)' does not match any in class 'KifuViewer::AnalysisOnlineDialog' void KifuViewer::AnalysisOnlineDialog::showPVInt(unsigned long key, ^~ In file included from kifuViewer.cc:1:0: kifuViewer.h:143:8: error: candidate is: void KifuViewer::AnalysisOnlineDialog::showPVInt(long unsigned int, int, long unsigned int, double, int, const std::vector&) void showPVInt(unsigned long key, ^ Makefile:720: recipe for target 'kifuViewer.o' failed make[1]: *** [kifuViewer.o] Error 1 make[1]: Leaving directory '/build/gpsshogi-0.7.0/sample/viewer' debian/rules:38: recipe for target 'build/gpsshogi' failed make: *** [build/gpsshogi] Error 2 Andreas
Processed: your mail
Processing commands for cont...@bugs.debian.org: > forwarded 860684 https://github.com/streadway/amqp/issues/261 Bug #860684 [src:golang-github-streadway-amqp] golang-github-streadway-amqp: FTBFS on i386: dh_auto_test: go test -v -p 1 github.com/streadway/amqp returned exit code 1 Set Bug forwarded-to-address to 'https://github.com/streadway/amqp/issues/261'. > forwarded 860633 https://github.com/go-asn1-ber/asn1-ber/issues/5 Bug #860633 [src:golang-gopkg-asn1-ber.v1] golang-gopkg-asn1-ber.v1: FTBFS on i386: dh_auto_test: go test -v -p 1 gopkg.in/asn1-ber.v1 returned exit code 2 Set Bug forwarded-to-address to 'https://github.com/go-asn1-ber/asn1-ber/issues/5'. > End of message, stopping processing here. Please contact me if you need assistance. -- 860633: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860633 860684: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860684 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#860703: golang-github-jacobsa-fuse: FTBFS on i386: dh_auto_build
> src/github.com/jacobsa/fuse/fusetesting/stat_linux.go:33: cannot use
> sys.(*syscall.Stat_t).Nlink (type uint32) as type uint64 in assignment
issue above can be resolved by the patch enclosed.
but the following errors still exist. I don't have clue yet.
> src/github.com/jacobsa/fuse/internal/buffer/runtime.go:22: missing function
> body for "memclr"
> src/github.com/jacobsa/fuse/internal/buffer/runtime.go:27: missing function
> body for "memmove"
Cheers,
--
Roger Shimizu, GMT +9 Tokyo
PGP/GPG: 4096R/6C6ACD6417B3ACB1
From: Roger Shimizu
Date: Tue, 2 May 2017 09:56:18 +0900
Subject: 1st step
---
fusetesting/stat_linux.go | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fusetesting/stat_linux.go b/fusetesting/stat_linux.go
index eec3568..ccf1f7e 100644
--- a/fusetesting/stat_linux.go
+++ b/fusetesting/stat_linux.go
@@ -30,7 +30,7 @@ func extractBirthtime(sys interface{}) (birthtime time.Time, ok bool) {
}
func extractNlink(sys interface{}) (nlink uint64, ok bool) {
- nlink = sys.(*syscall.Stat_t).Nlink
+ nlink = (uint64)(sys.(*syscall.Stat_t).Nlink)
ok = true
return
}
Bug#860608: [pkg-golang-devel] Bug#860608: golang: FTBFS: Go version is "go1.6.1", ignoring -next /<>/api/next.txt
Sorry for the late reply, I’ve been swamped. On Fri, Apr 21, 2017 at 10:28 AM, Niels Thykier wrote: > Michael Stapelberg: > > On Fri, Apr 21, 2017 at 9:45 AM, Niels Thykier > wrote: > > > >> [...] > >>> > >> > >> They seem to be arch:all packages. We cannot binNMU arch:all packages, > >> only architecture dependent ones. :-/ > >> > > > > Okay. How do you suggest we rectify this issue instead, then? > > > > A (possibly "no change") sourceful upload to force a rebuild of the > arch:all package. > A sourceful upload for which source package? src:golang has been removed from unstable and testing since 2016-10. To avoid further delays, is this something you could NMU for us? If so, I’d much appreciate that. Thanks! -- Best regards, Michael
Bug#857360: marked as done (gitlab: Fails to install in Stretch)
Your message dated Tue, 2 May 2017 12:40:55 +0530 with message-id <0ef5b071-35fe-e66b-bd77-50c7be33d...@debian.org> and subject line Re: gitlab_8.13.11+dfsg-4 no longer available, unable to install has caused the Debian Bug report #857360, regarding gitlab: Fails to install in Stretch 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.) -- 857360: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857360 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: gitlab-shell Version: 3.6.6-4 Severity: grave Justification: renders package unusable -- System Information: Debian Release: 9.0 APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-1-amd64 (SMP w/16 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages gitlab-shell depends on: ii ruby 1:2.3.3 gitlab-shell recommends no packages. gitlab-shell suggests no packages. -- no debconf information Description: gitlab-shell fails to install on Stretch: while executing the installer script, it fails to find a file (config.yml.example). Downloading the file from uptream and manually copying to the right location does not work either, not sure why, since it is there after the failed re-attempt. Here's the output from apt-get: cp: cannot stat '/usr/share/doc/gitlab-shell/config.yml.example': No such file or directory dpkg: error processing package gitlab (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: Steps to reproduce: apt-get install gitlab gitlab-shell If any additional information is required to reproduce (e.g. installed packages), feel free to ask me about this. This bug happened in a basically fresh install of Stretch. --- End Message --- --- Begin Message --- On Sun, 23 Apr 2017 21:29:07 -0300 Joel Maxuel wrote: > Got it working. Based on the unicorn logs, I turned off listening for port > 1443 (depend on only socket listen) for it to work. A kludge, but it is > something quick and dirty I can investigate later. Closing this, as fixed version entered stretch. signature.asc Description: OpenPGP digital signature --- End Message ---
Bug#861388: marked as done (roundcube: CVE-2017-8114: security issue in virtualmin and sasl drivers)
Your message dated Tue, 02 May 2017 07:03:52 + with message-id and subject line Bug#861388: fixed in roundcube 1.2.3+dfsg.1-4 has caused the Debian Bug report #861388, regarding roundcube: CVE-2017-8114: security issue in virtualmin and sasl drivers 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.) -- 861388: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861388 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: roundcube Version: 1.2.3+dfsg.1-3 Severity: grave Tags: upstream security Hi, the following vulnerability was published for roundcube. CVE-2017-8114[0]: security issue in virtualmin and sasl drivers The security tracker contains the commit references for 1.2.x, 1.1.x and 1.0.x. If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2017-8114 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-8114 Regards, Salvatore --- End Message --- --- Begin Message --- Source: roundcube Source-Version: 1.2.3+dfsg.1-4 We believe that the bug you reported is fixed in the latest version of roundcube, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 861...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Guilhem Moulin (supplier of updated roundcube package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 01 May 2017 23:37:14 +0200 Source: roundcube Binary: roundcube-core roundcube roundcube-mysql roundcube-pgsql roundcube-sqlite3 roundcube-plugins Architecture: source all Version: 1.2.3+dfsg.1-4 Distribution: unstable Urgency: high Maintainer: Debian Roundcube Maintainers Changed-By: Guilhem Moulin Description: roundcube - skinnable AJAX based webmail solution for IMAP servers - metapack roundcube-core - skinnable AJAX based webmail solution for IMAP servers roundcube-mysql - metapackage providing MySQL dependencies for RoundCube roundcube-pgsql - metapackage providing PostgreSQL dependencies for RoundCube roundcube-plugins - skinnable AJAX based webmail solution for IMAP servers - plugins roundcube-sqlite3 - metapackage providing SQLite dependencies for RoundCube Closes: 861388 Changes: roundcube (1.2.3+dfsg.1-4) unstable; urgency=high . * Backport fix for CVE-2017-8114: Roundcube Webmail allows arbitrary password resets by authenticated users. This affects versions before 1.0.11, 1.1.x before 1.1.9, and 1.2.x before 1.2.5. The problem is caused by an improperly restricted exec call in the virtualmin and sasl drivers of the password plugin. (Closes: #861388). Checksums-Sha1: f8b9104bd9b595c1664f0a2b22be7d9f6c54928b 2470 roundcube_1.2.3+dfsg.1-4.dsc 38ad3916e5540e78fd6e8152cb16a2e29d0ab73c 4442288 roundcube_1.2.3+dfsg.1-4.debian.tar.xz cd797aa74c556f713ddc3d8f484d797347122be2 2112032 roundcube-core_1.2.3+dfsg.1-4_all.deb eef06728f4bdc44e5fe3fbddd480a1a094ae334b 70792 roundcube-mysql_1.2.3+dfsg.1-4_all.deb f1c6f05cd818213cbf4acd88301d7830b0a4cfd2 70762 roundcube-pgsql_1.2.3+dfsg.1-4_all.deb d33c91b60014e4cf2fd2dd92b8d93b58d56c35e2 661566 roundcube-plugins_1.2.3+dfsg.1-4_all.deb e5a6270708485e91872e816ac95e7cf28fc1a2c1 70742 roundcube-sqlite3_1.2.3+dfsg.1-4_all.deb ecbb7a98c41d1fab3dbefc399a61fa1e92374cb0 1376 roundcube_1.2.3+dfsg.1-4_all.deb f02ac4289fc687d5c5fec13f04952482fe291ea3 9011 roundcube_1.2.3+dfsg.1-4_amd64.buildinfo Checksums-Sha256: bc98b29226e77b6dc5f70eb4826e8539536cb341604f90ba81aa8deef53b6a83 2470 roundcube_1.2.3+dfsg.1-4.dsc 6e640a46f38dedd6e36015e66522a6756258878a04a047b39758a84ba97f1f57 4442288 roundcube_1.2.3+dfsg.1-4.debian.tar.xz 28b5b8e4eab62b8e3c867712966761328a13087b072cdb356259be44e00a96fa 2112032 roundcube-core_1.2.3+dfsg.1-4_all.deb 85542ab7d75edfa00777608143d3c34d14084cc3097bd58167aade05766bda7b 70792 roundcube-mysql_1.2.3+dfsg.1-4_all.deb edae5116e73a82e90bab72b23f587008516bd2d3d6b349682d840b09ae4e405f 70762 roundcube-pgsql_1.2.3+dfsg.1-4_all.deb cfbfbe5fae682b737a6dbcd409eaa80b8cf149c125d7076878fc5207846a3c00 661566 roundcube-pl
Bug#860463: Bug#782456: Bug#860463: nodm: Missing handling of plymouth (#782456)
On Tue, 02 May 2017 at 01:38:15 +0200, Axel Beckert wrote: > JFTR: This needs an "|| true" if your init script uses "set -e", > otherwise starting or restarting the DM besides a fresh system bootup > might fail. Oh, good point. I should change that for nodm. > > Should this say "/bin/plymouth quit --wait"? > > Hrm. I've just uploaded wdm without "--wait" (c.f. #860464, Cc'ed). > Please file a new bug report against wdm if I should change that. What's done elsewhere (e.g. in Fedora, which I think is where Plymouth originated) is using plymouth quit without --wait. I'm not entirely sure why that's sufficient to be useful, but it seems it is. S
Bug#861388: [Pkg-roundcube-maintainers] Bug#861388: roundcube: CVE-2017-8114: security issue in virtualmin and sasl drivers
❦ 1 mai 2017 23:57 +0200, Guilhem Moulin : >> the following vulnerability was published for roundcube. >> >> CVE-2017-8114[0]: >> security issue in virtualmin and sasl drivers > > Thanks, pushed. Sandro, Vincent, would you mind tagging & uploading? Done. Thanks! -- 10.0 times 0.1 is hardly ever 1.0. - The Elements of Programming Style (Kernighan & Plauger) signature.asc Description: PGP signature
Bug#860805: beignet-opencl-icd: OpenCL fails with: drm_intel_gem_bo_context_exec() failed: Device or resource busy
Hi Rebecca, On Sat, Apr 29, 2017 at 12:43:19PM +0100, Rebecca N. Palmer wrote: > The above patch is now in Alioth, but please do *not* upload it yet. I have tested beignet-dev_1.3.0-2 and compared it to what you get when building commit 7d60bf92c6706f174305393172841e2078ecd508. > > $ grep '^model name' /proc/cpuinfo | head -n1 > >model name : Intel(R) Core(TM) i5-4200U CPU @ 1.60GHz > >... 4200U is [Haswell] so I guess I can do the testing, right? > > If your integrated GPU is enabled (it might not be if you also have a > discrete GPU - xrandr --listproviders), yes. Please try, with both current > beignet-opencl-icd and the above fix: > > - the test suite (/usr/lib/x86_64-linux-gnu/beignet/utest_run from > beignet-dev): many failures before this fix, should be none after. I can confirm that beignet-dev_1.3.0-2 produces a lot of errors which vanished when using said status from Git. So the patch works perfectly on my machine. > - the clFFT test from https://bugs.freedesktop.org/show_bug.cgi?id=100639 > This needs a small change to work in sid (its reporter was using > jessie-backports): > -DCMAKE_C_FLAGS:STRING="-O3 -DCL_USE_DEPRECATED_OPENCL_1_2_APIS=1" > as linking to an __inline symbol (clfftInitSetupData) without optimization > fails in recent gcc. In other words: I would need to rebuild beignet-dev_1.3.0-2 with the said change in d/rules as well as rebuild 7d60bf92c6706f174305393172841e2078ecd508 and compare again? Could you please give a direct link what program to run once I have rebuild? Thanks a lot for your work on this Andreas. -- http://fam-tille.de
