Bug#869088: unattended-upgrades FTBFS: FAIL: test_untrusted_check_without_conffile_check

Source: unattended-upgrades Version: 0.93.1+nmu2 Severity: serious https://buildd.debian.org/status/fetch.php?pkg=unattended-upgrades=all=0.93.1%2Bnmu2=1500545189=0 ... == FAIL: test_untrusted_check_without_conffile_check

Bug#869086: dsniff sometimes FTBFS due to missing Makefile dependency

Source: dsniff Version: 2.4b1+debian-26 Severity: serious Tags: patch dsniff sometimes FTBFS in parallel builds: https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/dsniff.html ... rpcgen -h mount.x -o mount.h ... ./decode_mountd.c: In function 'decode_mountd':

Bug#869084: linux-image-4.12.0-trunk-amd64: rtl8723be fails to work with old firmware

Package: src:linux Version: 4.12.2-1~exp1 Severity: important As of commit f70e4df2b384d21e36a7c30a591639592692e0ec, the rtl8723be driver uses a new firmware file rtlwifi/rtl8723befw_36.bin which is not packaged for Debian yet. There is fallback code to load the old firmware file

Bug#869083: snmp: getting the short interface name instead of long ifDescr

Package: snmpd Version: 5.7.2.1+dfsg-1 I'm using MRTG to do some simple monitoring (including network devices) of my Debian-based servers. The interfaces are identified by name (e.g. eth0, eth1,...), and MRTG maps these names to the proper OIDs by looking them up in IF-MIB::ifDescr:          

Bug#868695: [systemd] Have not had any LC_CTYPE on previous versions

Am 20.07.2017 um 09:14 schrieb David Baron: > Package: systemd > Version: 233-10 > > --- Please enter the report below this line. --- > I have not seen this env variable in ages. > Do I need to install something involving the getty systemd service to get it? > > Since I have lived without it so

Bug#868961: [tryton-debian] Bug#868961: cached-property: FTBFS: dh_auto_test: pybuild --test -i python{version} -p 2.7 returned exit code 13

* Lucas Nussbaum: " [tryton-debian] Bug#868961: cached-property: FTBFS: dh_auto_test: pybuild --test -i python{version} -p 2.7 returned exit code 13" (Wed, 19 Jul 2017 22:22:03 +0200): > Source: cached-property > Version: 1.3.0-2 > Severity: serious > Tags: buster sid > User:

Bug#869081: RFP: nvml -- Non-Volatile Memory Library

Package: wnpp Severity: wishlist * Package name: nvml Version : 1.3 Upstream Author : Krzysztof Czurylo * URL : https://github.com/pmem/nvml * License : BSD Programming Lang: C, C++ Description : Non-Volatile Memory Library

Bug#785497: less: occasional incorrect coloring

Control: found -1 481-2.1 with libc6 2.24-12 and libtinfo5 6.0+20170715-2 (up-to-date Debian/unstable), in case this matters. On 2017-07-18 12:09:03 +0200, Vincent Lefevre wrote: > This bug was still occurring in Debian/unstable in the last few > months, but it seems that I can no longer

Bug#868685: debmirror: not able to mirror sid

Here’s a few more APT error messages from whatever debmirror creates: E: Failed to fetch http://mirror.lan.tarent.de/debian/dists/sid/contrib/binary-amd64/PackagesIndex 404 Not Found [IP: 172.26.0.180 80]: rename failed, No such file or directory

Bug#869079: Kernel NULL Pointer Deference During cudaMalloc()

Control: tags -1 wontfix On Thu, 2017-07-20 at 11:39 +0100, Alex Richman wrote: > Package: nvidia-driver > > I've only hit this bug once so far, and have been running the same > code  > for weeks now so it's pretty rare.  Not certain but I believe this > was  > during a large cudaMalloc(). >

Bug#869080: virtualenv: impossible to install self-made package in virtualenv distributed with debian

Package: virtualenv Severity: normal Dear Maintainer, When trying to install a self-made package called "fledit" in a virtual evironment the following kept happening: Running setup.py develop for fledit Complete output from command /usr/bin/python3 -c "import setuptools,

Bug#862051: Allow nodejs to provide /usr/bin/node (draft resolution)

Tollef Fog Heen writes ("Bug#862051: Allow nodejs to provide /usr/bin/node (draft resolution)"): > 1. The CTTE decision from 2012-07-12 in bug #614907 is repealed. > > This means Debian's normal policies and practices take over and the > nodejs package is free to provide /usr/bin/node. The

Bug#865577: cloud-init: diff for NMU version 0.7.9-2.1

Control: tags 865577 + pending Dear maintainer, I've prepared an NMU for cloud-init (versioned as 0.7.9-2.1) and uploaded it to DELAYED/10. Please feel free to tell me if I should delay it longer or cancel it. cu Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out

Bug#869079: Kernel NULL Pointer Deference During cudaMalloc()

Package: nvidia-driver I've only hit this bug once so far, and have been running the same code for weeks now so it's pretty rare. Not certain but I believe this was during a large cudaMalloc(). Don't have the hardware to replicate it on another non-Debian system ATM, so unfortunately can't

Bug#869011: Pending fixes for bugs in the maven-install-plugin package

tag 869011 + pending thanks Some bugs in the maven-install-plugin package are closed in revision 1e5306ff8ec484cc08eb8f3a384826158f34afa7 in branch 'master' by Emmanuel Bourg The full diff can be seen at https://anonscm.debian.org/cgit/pkg-java/maven-install-plugin.git/commit/?id=1e5306f Commit

Bug#869078: texlive-base: fancyhdr extramarks fails

Package: texlive-base Version: 2017.20170629-1 Severity: important Dear TexLive Maintainers, Package fancyhdr 3.9 includes an extramarks style which fails to work with a XeTeX document with a book documentclass. Other classes work fine. Found this error while packaging XeTeX asn1c documentation

Bug#869077: RM: lazarus-*1.6 lazarus-ide-qt4 lcl-qt4 [all] -- ROM; obsolete arch:all packages

Package: ftp.debian.org Severity: normal X-Debbugs-CC: pkg-pascal-de...@lists.alioth.debian.org Please decruft the arch:all packages lazarus-1.6 lazarus-doc-1.6 lazarus-ide-qt4 lazarus-src-1.6 and lcl-qt4. They appear to be blocking lazarus' migration [1], despite lazarus never building on

Bug#869076: RM: fp-docs-3.0.0 fpc-3.0.0 fpc-source-3.0 [all] -- ROM; obsolete arch:all packages

Package: ftp.debian.org Severity: normal X-Debbugs-CC: pkg-pascal-de...@lists.alioth.debian.org Hi FTP Team Please decruft the arch:all packages fp-docs-3.0.0 fpc-3.0.0 andfpc-source-3.0. They appear to be blocking fpc's migration [1], despite fpc never building on mips64el, ppc64el and

Bug#868664: notmuch-addrlookup: diff for NMU version 8-0.1

Hi Thank for your bug report and for all the work you did. I should have answered before... I prepared yesterday the new version here: https://anonscm.debian.org/cgit/collab-maint/notmuch-addrlookup.git (I asked Raphaël Hertzog to review and upload it but he has no time right now) If you have

Bug#868126: webkit2gtk: Please add build support for m68k

Control: tags -1 pending On Thu, Jul 13, 2017 at 08:32:24AM +0200, John Paul Adrian Glaubitz wrote: > Another update. Fixes a typo and adds another missing assertion fix. > > With the patch, the package builds fine for me. Thanks, applied. It will be included in the next release. Berto

Bug#869069: [Pkg-libvirt-maintainers] Bug#869069: VMs with hugepages can't start after upgrade to stretch

Hi, On Thu, Jul 20, 2017 at 10:32:49AM +0200, Pavel Matěja wrote: > Package: libvirt-daemon > Version: 3.0.0-4 > > After upgrade from jessie to stretch I was unable to start VMs which are > using hugepages. > The error message is: > qemu-system-x86_64: can't open backing store

Bug#767235: torsocks: FTBFS on hurd-i386

[intrigeri 2014] > Hi David, > > could you please have a look at this Debian bug report: > > https://bugs.debian.org/767235 > > Thanks in advance! > > [Dropping the "patch" tag, as it seems unclear that the patch actually > does the right thing.] As far as I can tell, the tsocks_syscall()

Bug#869075: postfix: postdrop hangs until reboot: warning: mail_queue_enter: create file maildrop/...: Permission denied

Package: postfix Version: 3.2.2-1 Severity: important When I tried to send a mail with mutt (via the usual "/usr/sbin/sendmail -oem -oi" command), it was hanging, and ps showed that it was due to postdrop, which was hanging. There was no such problem when I sent a mail 20 minutes before.

Bug#869074: mame FTBFS on i386: virtual memory exhausted

Source: mame Version: 0.187+dfsg.1-1 Severity: serious https://buildd.debian.org/status/fetch.php?pkg=mame=i386=0.187%2Bdfsg.1-1=1500458517=0 ... Archiving libatari.a... rm -f ../../../../../scripts/mame_mame/libatari.a ar -rcs ../../../../../scripts/mame_mame/libatari.a

Bug#853285: closed by Clint Adams <cl...@debian.org> (Bug#853285: fixed in ghc 8.0.2-3)

Control: reopen -1 Since the patch was reverted in the GHC package, let's reopen this bug report. I have a very fast Kaby Lake machine now available, so I will be able to do plenty of test builds to improve the patch. I will attach an updated patch to this bug report as soon I have it. Cheers,

Bug#868843: xorg-server: please make the BUILD_{DATE,TIME} reproducible

Control: tag -1 upstream moreinfo On 07/19/2017 09:10 AM, Chris Lamb wrote: > Source: xorg-server > Version: 2:1.19.3-2 > Severity: wishlist > Tags: patch > User: reproducible-bui...@lists.alioth.debian.org > Usertags: timestamps > X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org > > Hi,

Bug#869073: flash-kernel: Please add an option to not use an initrd image or detect if one is available

Package: flash-kernel Version: 3.79 Severity: minor Tags: newcomer Please add a switch to disable the use of an initrd-image. I'm compiling my kernel with make dep-pkg and I'm not using an initrd-image. flash-kernel fails with error 2 and I found out that no initrd was found. Please fix this.

Bug#869072: reportbug: The --timeout option doesn't work

Package: reportbug Version: 7.1.7 Severity: normal The --timeout option doesn't work. For instance, a strace on reportbug --timeout=5 reportbug shows: [...] 12405 10:58:53 connect(5, {sa_family=AF_INET6, sin6_port=htons(80), inet_pton(AF_INET6, "2001:41c8:1000:21::21:4", _addr),

Bug#868919: physamp: FTBFS: AlignmentOptimizer.cpp:39:32: fatal error: Bpp/Seq/Alphabet.all: No such file or directory

Hi Julien, On Thu, Jul 20, 2017 at 10:49:10AM +0200, Julien Yann Dutheil wrote: > Yes, should be. But I noticed some other problems... I have made a version > 1.0.2 addressing them. Then I synchronized the upstream branch accordingly, > and then merged the master branch and the upstream branch,

Bug#869071: RFS: globjects/1.1.0-2

Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for the following package: * Package name: globjects   Version : 1.1.0-2   Upstream Author : CG Internals * URL : http://globjects.org/ * License : Expat   Section :

Bug#854273: Proper resolution on both screens

I uploaded a fix on https://github.com/pdfpc/pdfpc/pull/254 . Could you try it?

Bug#868919: physamp: FTBFS: AlignmentOptimizer.cpp:39:32: fatal error: Bpp/Seq/Alphabet.all: No such file or directory

Dear Andreas, Yes, should be. But I noticed some other problems... I have made a version 1.0.2 addressing them. Then I synchronized the upstream branch accordingly, and then merged the master branch and the upstream branch, is that the correct way to do? Version 1.0.2-1 should then normally build

Bug#869070: apt-listbugs does not honor Acquire::http::TimeOut

On 2017-07-20 10:43:22 +0200, Vincent Lefevre wrote: > apt-listbugs does not honor Acquire::http::TimeOut, while its man page > says: > > CONFIGURATION FILE > apt-listbugs understands APT configuration file (see apt.conf(5) for > more details). [...] [...] I see that not all configuration

Bug#865897: unattended-upgrades: diff for NMU version 0.93.1+nmu2

Control: tags 865897 + patch Control: tags 865897 + pending Dear maintainer, I've prepared an NMU for unattended-upgrades (versioned as 0.93.1+nmu2) and uploaded it to DELAYED/0. Please feel free to tell me if I should delay it longer. Regards. -- Debian Developer - deb.li/jak | jak-linux.org

Bug#862051: Allow nodejs to provide /usr/bin/node (draft resolution)

Le mercredi, 19 juillet 2017, 21.35:33 h CEST Tollef Fog Heen a écrit : > === DRAFT Resolution v2 === > > The Technical Committee recognises that circumstances change in ways > that make previous resolutions no longer appropriate. In 2012, it was > resolved that the nodejs package should not

Bug#866389: transition: perl 5.26

On Thu, 20 Jul 2017 10:43:30 +1000, Paul Wise wrote: > On Thu, Jul 20, 2017 at 5:04 AM, gregor herrmann wrote: > > #867213: syslog-ng-incubator: one rdep (syslog-ng). No reaction on > > the bug report, unrelated build failure; I guess syslog-ng* > > can be removed from testing

Bug#869070: apt-listbugs does not honor Acquire::http::TimeOut

Package: apt-listbugs Version: 0.1.23 Severity: important apt-listbugs does not honor Acquire::http::TimeOut, while its man page says: CONFIGURATION FILE apt-listbugs understands APT configuration file (see apt.conf(5) for more details). [...] This means that in case of partial network

Bug#866055: linux-image-4.9.0-3-amd64: Broadwell laptop hangs during light usage since upgrading to stretch

I've been running 5+ days on 4.9.0-3-rt-amd64 now. Not going to cry victory yet though, the previous run with 4.9.0-3-amd64 (4.9.30-2+deb9u2) lasted 8 days before going belly up. signature.asc Description: Digital signature

Bug#790198: banshee: depends on libwebkitgtk-1.0-0 which is deprecated

Control: fixed -1 2.9.0-1 On Wed, Jul 19, 2017 at 08:39:56PM -0400, Jeremy Bicha wrote: > Control: reopen -1 > Control: found -1 2.6.2-6.1 > > It is inappropriate to close this bug until this bug is actually fixed > in unstable. >... When the BTS does version tracking it does not matter whether

Bug#869069: VMs with hugepages can't start after upgrade to stretch

Package: libvirt-daemon Version: 3.0.0-4 After upgrade from jessie to stretch I was unable to start VMs which are using hugepages. The error message is: qemu-system-x86_64: can't open backing store /dev/hugepages/libvirt/qemu for guest RAM: Permission denied In jessie were permissions of the

Bug#869005: Pending fixes for bugs in the plexus-utils2 package

tag 869005 + pending thanks Some bugs in the plexus-utils2 package are closed in revision 37fe47a754bc2a16c8bb05ba4a1d64c321283537 in branch 'master' by Emmanuel Bourg The full diff can be seen at https://anonscm.debian.org/cgit/pkg-java/plexus-utils2.git/commit/?id=37fe47a Commit message:

Bug#868652: ros-vcstools FTBFS: CalledProcessError: Command 'git commit -m initial' returned non-zero exit status 128

reopen 868652 found 0.1.39-4 thanks (Just following up from IRC) This appears to be still affecting 0.1.39-4. Regards, -- ,''`. : :' : Chris Lamb, Debian Project Leader `. `'` la...@debian.org / chris-lamb.co.uk `-

Bug#869066: ruby-diaspora-federation-rails: FTBFS: ERROR: Test "ruby2.3" failed.

Source: ruby-diaspora-federation-rails Version: 0.1.4-2 Severity: serious Tags: buster sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20170720 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part

Bug#869064: ruby-factory-girl-rails: FTBFS: ERROR: Test "ruby2.3" failed: Invalid gemspec in [factory_girl_rails.gemspec]: No such file or directory - git

Source: ruby-factory-girl-rails Version: 4.7.0-1 Severity: serious Tags: buster sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20170720 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully

Bug#869062: ruby-turbolinks: FTBFS: ERROR: Test "ruby2.3" failed.

Source: ruby-turbolinks Version: 2.5.3-3 Severity: serious Tags: buster sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20170720 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /

Bug#869067: ruby-devise-lastseenable: FTBFS: ERROR: Test "ruby2.3" failed.

Source: ruby-devise-lastseenable Version: 0.0.6-1 Severity: serious Tags: buster sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20170720 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully

Bug#869068: ruby-omniauth-cas3: FTBFS: ERROR: Test "ruby2.3" failed.

Source: ruby-omniauth-cas3 Version: 1.1.3-1 Severity: serious Tags: buster sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20170720 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully

Bug#869065: ruby-roadie-rails: FTBFS: build-dependency not installable: ruby-roadie (>= 3.1)

Source: ruby-roadie-rails Version: 1.1.0-1 Severity: serious Tags: buster sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20170720 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully

Bug#869056: ruby-rails-admin: FTBFS: ERROR: Test "ruby2.3" failed.

Source: ruby-rails-admin Version: 0.8.1+dfsg-3 Severity: serious Tags: buster sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20170720 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully

Bug#869055: ruby-roadie: FTBFS: unsatisfiable build-dependency: ruby-nokogiri (< 1.7.0) but 1.8.0-1 is to be installed

Source: ruby-roadie Version: 3.1.1-1 Severity: serious Tags: buster sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20170720 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully

Bug#869058: ruby-sprockets-rails: FTBFS: ERROR: Test "ruby2.3" failed.

Source: ruby-sprockets-rails Version: 2.3.2-1 Severity: serious Tags: buster sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20170720 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully

Bug#869063: ruby-truncato: FTBFS: ERROR: Test "ruby2.3" failed.

Source: ruby-truncato Version: 0.7.8-1 Severity: serious Tags: buster sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20170720 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /usr/

Bug#869061: ruby-cucumber-rails: FTBFS: ERROR: Test "ruby2.3" failed.

Source: ruby-cucumber-rails Version: 1.4.3-1 Severity: serious Tags: buster sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20170720 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully

Bug#869059: ruby-redis-actionpack: FTBFS: ERROR: Test "ruby2.3" failed.

Source: ruby-redis-actionpack Version: 4.0.0-2 Severity: serious Tags: buster sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20170720 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully

Bug#869060: ruby-web-console: FTBFS: ERROR: Test "ruby2.3" failed.

Source: ruby-web-console Version: 2.2.1-2 Severity: serious Tags: buster sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20170720 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /

Bug#869054: ruby-dalli: FTBFS: ERROR: Test "ruby2.3" failed.

Source: ruby-dalli Version: 2.7.4-1 Severity: serious Tags: buster sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20170720 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /usr/

Bug#869057: ruby-doorkeeper: FTBFS: ERROR: Test "ruby2.3" failed: Invalid gemspec in [doorkeeper.gemspec]: No such file or directory - git

Source: ruby-doorkeeper Version: 4.2.0-3 Severity: serious Tags: buster sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20170720 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully

Bug#869048: ruby-actionpack-xml-parser: FTBFS: ERROR: Test "ruby2.3" failed.

Source: ruby-actionpack-xml-parser Version: 1.0.2-2 Severity: serious Tags: buster sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20170720 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully

Bug#869052: ruby-devise: FTBFS: ERROR: Test "ruby2.3" failed.

Source: ruby-devise Version: 4.2.0-1 Severity: serious Tags: buster sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20170720 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /usr/

Bug#869051: open-build-service: FTBFS: /usr/lib/ruby/vendor_ruby/bundler/resolver.rb:396:in `block in verify_gemfile_dependencies_are_found!': Could not find gem 'nokogiri (~> 1.6.7)' in any of the ge

Source: open-build-service Version: 2.7.1-10 Severity: serious Tags: buster sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20170720 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully

Bug#869053: ruby-health-check: FTBFS: ERROR: Test "ruby2.3" failed: Invalid gemspec in [health_check.gemspec]: No such file or directory - git

Source: ruby-health-check Version: 2.6.0-1 Severity: serious Tags: buster sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20170720 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully

Bug#869036: ruby-rails-i18n: FTBFS: ERROR: Test "ruby2.3" failed.

Source: ruby-rails-i18n Version: 4.0.8-1 Severity: serious Tags: buster sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20170720 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /

Bug#869042: ruby-js-routes: FTBFS: ERROR: Test "ruby2.3" failed: Invalid gemspec in [js-routes.gemspec]: No such file or directory - git

Source: ruby-js-routes Version: 1.3.3-1 Severity: serious Tags: buster sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20170720 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > Inva

Bug#869035: ruby-simple-form: FTBFS: ERROR: Test "ruby2.3" failed.

Source: ruby-simple-form Version: 3.2.0-1 Severity: serious Tags: buster sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20170720 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /

Bug#869046: ruby-activerecord-session-store: FTBFS: ERROR: Test "ruby2.3" failed.

Source: ruby-activerecord-session-store Version: 1.0.0-2 Severity: serious Tags: buster sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20170720 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part

Bug#869034: ruby-combustion: FTBFS: ERROR: Test "ruby2.3" failed.

Source: ruby-combustion Version: 0.5.4-1 Severity: serious Tags: buster sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20170720 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /

Bug#869044: ruby-sass-rails: FTBFS: ERROR: Test "ruby2.3" failed.

Source: ruby-sass-rails Version: 5.0.6-1 Severity: serious Tags: buster sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20170720 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /

Bug#869041: ruby-rails-dom-testing: FTBFS: ERROR: Test "ruby2.3" failed.

Source: ruby-rails-dom-testing Version: 1.0.6-1 Severity: serious Tags: buster sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20170720 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully

Bug#869049: ruby-doorkeeper-openid-connect: FTBFS: ERROR: Test "ruby2.3" failed: Invalid gemspec in [doorkeeper-openid_connect.gemspec]: No such file or directory - git

Source: ruby-doorkeeper-openid-connect Version: 1.1.2-1 Severity: serious Tags: buster sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20170720 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part

Bug#869039: ruby-kaminari: FTBFS: ERROR: Test "ruby2.3" failed.

Source: ruby-kaminari Version: 0.17.0-3 Severity: serious Tags: buster sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20170720 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /

Bug#869047: ruby-premailer-rails: FTBFS: ERROR: Test "ruby2.3" failed.

Source: ruby-premailer-rails Version: 1.9.2-2 Severity: serious Tags: buster sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20170720 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully

Bug#869050: ruby-jquery-rails: FTBFS: ERROR: Test "ruby2.3" failed: Invalid gemspec in [jquery-rails.gemspec]: No such file or directory - git

Source: ruby-jquery-rails Version: 4.2.1-2 Severity: serious Tags: buster sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20170720 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully

Bug#869033: ruby-actionpack-action-caching: FTBFS: ERROR: Test "ruby2.3" failed.

Source: ruby-actionpack-action-caching Version: 1.1.1-4 Severity: serious Tags: buster sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20170720 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part

Bug#869045: ruby-devise-two-factor: FTBFS: ERROR: Test "ruby2.3" failed: Invalid gemspec in [devise-two-factor.gemspec]: No such file or directory - git

Source: ruby-devise-two-factor Version: 3.0.0-2 Severity: serious Tags: buster sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20170720 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully

Bug#869043: vagrant-libvirt: FTBFS: ERROR: Test "ruby2.3" failed: Invalid gemspec in [vagrant-libvirt.gemspec]: No such file or directory - git

Source: vagrant-libvirt Version: 0.0.37-1 Severity: serious Tags: buster sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20170720 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully

Bug#869037: ruby-haml-rails: FTBFS: ERROR: Test "ruby2.3" failed.

Source: ruby-haml-rails Version: 0.9.0-4 Severity: serious Tags: buster sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20170720 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /

Bug#869038: ruby-rspec-rails: FTBFS: ERROR: Test "ruby2.3" failed.

Source: ruby-rspec-rails Version: 3.5.2-1 Severity: serious Tags: buster sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20170720 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /

Bug#869040: ruby-versionist: FTBFS: ERROR: Test "ruby2.3" failed.

Source: ruby-versionist Version: 1.5.0-1 Severity: serious Tags: buster sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20170720 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /

Bug#869032: ruby-api-pagination: FTBFS: ERROR: Test "ruby2.3" failed.

Source: ruby-api-pagination Version: 4.2.0-1 Severity: serious Tags: buster sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20170720 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully

Bug#869031: redmine: FTBFS: build-dependency not installable: ruby-roadie-rails

Source: redmine Version: 3.3.1-4 Severity: serious Tags: buster sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20170720 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully

Bug#868990: [Pkg-pascal-devel] Bug#868990: lazarus: FTBFS: Architecture mips(el) is not available for elf format

Control: forwarded -1 https://bugs.freepascal.org/view.php?id=31989 Control: tags -1 + upstream Hi Aaron On 20 July 2017 at 03:11, Aaron M. Ucko wrote: > Builds of lazarus for mips and mipsel failed with errors of the form > > Error: Architecture mips(el) is not available for

Bug#796562: lintian: Please identify lack of sanitation compiler/linker flags

Le 20 juillet 2017 08:02:41 GMT+02:00, intrigeri a écrit : >Control: retitle -1 Please identify lack of UBSAN compiler/linker flags > >Jakub Wilk: >> Relevant thread on oss-security: >> http://www.openwall.com/lists/oss-security/2016/02/17/9 > >Right, I was aware of this

Bug#868695: [systemd] Have not had any LC_CTYPE on previous versions

Package: systemd Version: 233-10 --- Please enter the report below this line. --- I have not seen this env variable in ages. Do I need to install something involving the getty systemd service to get it? Since I have lived without it so far, question is if not using ssh xorg login, to I indeed

Bug#820519: sitecopy: fails to accept SSL certificates issued by a CA (Let's Encrypt)

On 19 juil. 2017 21:59, Francesco Poli wrote: > On Wed, 19 Jul 2017 19:50:15 +0200 Christian Marillat wrote: > >> On 19 juil. 2017 19:33, Francesco Poli wrote: >> >> [...] >> >> > Is there any way to get more information? >> >> Could you

Bug#868768: marked as done (RFS: iperf3/3.2-1)

reopen 868768 thanks

Bug#803924: [Pkg-samba-maint] Bug#803924: -HUP needs to be sent more broadly

2017-07-20 2:07 GMT+02:00 Andrew Bartlett : > Thinking about this some more, in the multi-process architecture of the > AD DC, the -HUP will need to go to every samba process - just making > the master process reload won't do anything for the children, as far as > I'm aware. >

Bug#869029: Discussion in Simutrans forum

Some possible causes of this bug are discussed in this Simutrans forum post: http://forum.simutrans.com/index.php?topic=17182.0 Julius signature.asc Description: OpenPGP digital signature

Bug#796562: lintian: Please identify lack of sanitation compiler/linker flags

intrigeri: > Hi Chris, > > Chris Lamb: >>> lintian: Please identify lack of sanitation compiler/linker flags > >> Is this not covered by the following tags? > >> hardening-no-bindnow >> hardening-no-fortify-functions >> hardening-no-pie >> hardening-no-relro > > Nope: this bug report

Bug#866400: ifupdown: networking.service fails to start allow-hotplug interfaces at boot

On Thu, Jul 20, 2017 at 12:33:49AM +0200, Sven-Haegar Koch wrote: > > I tried that and the only result of that was that network interfaces > > added to the VM after booting were not renamed, the ones at boot time > > still were. The only thing that prevented everything from being renamed > > was

Bug#868878: [Pkg-libvirt-maintainers] Bug#868878: virt-manager: Please consider dropping dependency on gconf2

Guido Günther: > Negligence on my part, sorry. Fixed in git since early March. Amazing, thanks :) > I wonder if we can make it any simpler to check current git besides > gbp clone vcsgit:virt-manager I honestly don't know why I did `apt-get source' while I would usually debcheckout the

Bug#796562: lintian: Please identify lack of sanitation compiler/linker flags

Control: retitle -1 Please identify lack of UBSAN compiler/linker flags Jakub Wilk: > Relevant thread on oss-security: > http://www.openwall.com/lists/oss-security/2016/02/17/9 Right, I was aware of this additional info but failed to update this bug report accordingly. Sorry! tl;dr: "only the

Bug#869030: elixir: Please package v1.4

Package: elixir Version: 1.3.3-2 Severity: wishlist The upstream version of rabbitmq-server depends on elixir 1.4. -- System Information: Debian Release: 9.0 APT prefers stable APT policy: (700, 'stable'), (600, 'unstable'), (550, 'experimental'), (500, 'testing') Architecture: amd64

<    1   2   3