Bug#951717: broccoli-ruby: suppor for multiple Ruby versions is broken

Source: broccoli-ruby Version: 1.62-1 Severity: serious Justification: broken, deprecated upstream, blocks Ruby transition User pkg-ruby-extras-maintain...@lists.alioth.debian.org Usertags: ruby2.7-transition After rebuilding broccoli-ruby with ruby2.7 support added, the shared libraries are not

Bug#951587: ruby-batch-loader: FTBFS against ruby2.7: cannot load such file -- irb/ruby-token

Source: ruby-batch-loader Version: 1.4.1+dfsg.1-1 Severity: serious Tags: ftbfs Justification: fails to build from source User pkg-ruby-extras-maintain...@lists.alioth.debian.org Usertags: ruby2.7-transition LoadError: cannot load such file -- irb/ruby-token # /<>/spec/spec_helper.rb:12:in `' #

Bug#950963: FTBFS: Could not find gem 'sqlite3 (~> 1.3.8)' in any of the gem sources listed in your Gemfile

Source: ruby-joiner Version: 0.4.2-1 Severity: serious Tags: ftbfs Justification: fails to build from source ruby-sqlite3 was recently updated in unstable, and now ruby-joiner fails to build with: Could not find gem 'sqlite3 (~> 1.3.8)' in any of the gem sources listed in your Gemfile. Note

Bug#950962: FTBFS: "JSON blows up on circular references" test fails

Source: ruby-sentry-raven Version: 2.9.0-1 Severity: serious Tags: ftbfs bullseye sid Justification: fails to build from source Failures: 1) JSON blows up on circular references Failure/Error: expect { JSON.dump(data) }.to raise_error(SystemStackError) expected SystemStackError,

Bug#950955: puppet-lint: FTBFS on unstable: undefined method `branch_coverage?' for SimpleCov:Module (NoMethodError)

Source: puppet-lint Version: 2.3.6-1 Severity: serious Tags: ftbfs Justification: fails to build from source After running the actual tests, something happens that makes the build crash. 8<8<8<- Finished in 1.34 seconds (files took

Bug#950227: marked as pending in ruby-mime-types

Control: tag -1 pending Hello, Bug #950227 in ruby-mime-types reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at:

Bug#950228: marked as pending in ruby-kaminari

Control: tag -1 pending Hello, Bug #950228 in ruby-kaminari reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at:

Bug#949824: schleuder: tests fail with ruby-sqlite 1.4.2-1

Source: schleuder Severity: serious Justification: FTBFS Hi, I'm about upload ruby-sqlite3 1.4.2-1, and schleuder now fails its tests on the dependency resolution step. ┌──┐ │ Checking Rubygems dependency resolution on

Bug#948187: marked as pending in ruby

Control: tag -1 pending Hello, Bug #948187 in ruby reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at:

Bug#948371: marked as pending in ruby

Control: tag -1 pending Hello, Bug #948371 in ruby reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at:

Bug#948455: marked as pending in ruby-byebug

Control: tag -1 pending Hello, Bug #948455 in ruby-byebug reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at:

Bug#937900: [pkg-lxc-devel] Bug#937900: python-lxc: Python2 removal in sid/bullseye

On Thu, Dec 19, 2019 at 07:58:15PM +, Evgeni Golov wrote: > Hi Moritz, > > yeah, that sounds reasonable. > > PEB, terceiro, any objections? nope, just go ahead signature.asc Description: PGP signature

Bug#946289: ufw: fails to start with iptables 1.8.4

Package: ufw Version: 0.36-1 Severity: grave Justification: renders package unusable This started since the latest upgrade of iptables (1.8.4). Reverting to 1.8.3 (testing) makes it work again. This is the contents of the journal for ufw.service: -- Logs begin at Thu 2019-12-05 14:15:18 -03,

Bug#945480: [PATCH 1/1] Remove remaining usage of python2

--- check | 2 +- setup.py | 2 +- yarns/900-implements.yarn | 10 +- 3 files changed, 7 insertions(+), 7 deletions(-) diff --git a/check b/check index 2d3d52c..290797e 100755 --- a/check +++ b/check @@ -4,7 +4,7 @@ set -eu python3 -m

Bug#945480: [PATCH 0/1] Drop remaining usage of python2

anymore. Antonio Terceiro (1): Remove remaining usage of python2 check | 2 +- setup.py | 2 +- yarns/900-implements.yarn | 10 +- 3 files changed, 7 insertions(+), 7 deletions(-) -- 2.24.0

Bug#945480: vmdb2: FTBFS on unstable: pylint failure

Source: vmdb2 Version: 0.13.2+git20190215-1 Severity: serious Tags: ftbfs Justification: fails to build from source The build currently fails with: Traceback (most recent call last): File "/usr/bin/pylint3", line 11, in load_entry_point('pylint==2.2.2', 'console_scripts', 'pylint')()

Bug#945415: gitano: FTBFS on unstable

Source: gitano Version: 1.2-1 Severity: serious Tags: ftbfs Justification: fails to build from source Hello, gitano currently fails to build from source under sbuild. the relevant part of the log is as follows: 8<8<8<- Running

Bug#942688: elixir-lang: tests fail randomly during build

Source: elixir-lang Version: 1.9.1.dfsg-1.1 Severity: serious Tags: ftbfs Justification: fails to build from source Hi, The latest upload failed to build on a few architectures: https://buildd.debian.org/status/package.php?p=elixir-lang=sid I tried building it locally and it worked. I then

Bug#933919: closing 933919

close 933919 thanks As per the discussion above, this bug is a false positive. I will also mark #934269 as RC.

Bug#939672: tmate: does not work at all; fails saying '[lost server]'

Package: tmate Version: 2.2.1-1+b2 Severity: grave Justification: renders package unusable Tags: bullseye sid When I try to start tmate, it just aborts and says '[lost server]'. After that the terminal is broken, and I have to reset it. I tried it on a Debian 10 VM and it just works, so this is

Bug#901552: marked as pending in ruby-bunny

Control: tag -1 pending Hello, Bug #901552 in ruby-bunny reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at:

Bug#933143: FTBFS, not Django 2.2 ready

On Fri, Jul 26, 2019 at 11:24:50PM +0200, Thomas Goirand wrote: > Package: python-django-mptt > Version: 0.8.7-1 > Severity: serious > Tags: patch > > Hi, > > Please find attached patch to do the Python 2 removal. > After this patch, your package continues to FTBFS. Please > get a fix for it.

Bug#927122: marked as pending in ruby

Control: tag -1 pending Hello, Bug #927122 in ruby reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at:

Bug#903448: [DRE-maint] Bug#903448: ruby-websocket-parser, ruby-websocket: error when trying to install together

Control: reassign -1 ruby-websocket-parser Control: retitle -1 ruby-websocket-parser: hijacks namespace from ruby-websocket Control: found -1 1.0.0-1 On Tue, Jul 10, 2018 at 10:13:32AM +0200, Andreas Beckmann wrote: > Package: ruby-websocket-parser,ruby-websocket > Severity: serious > User:

Bug#919999: Bug #919999 in ruby marked as pending

Control: tag -1 pending Hello, Bug #91 in ruby reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at:

Bug#912740: Bug #912740 in ruby marked as pending

Control: tag -1 pending Hello, Bug #912740 in ruby reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at:

Bug#921667: lxc, lava-dev: lxc fails to install along lava-dev --install-recommends

t; >Control: retitle -1 lxc,apparmor: lxc fails to install in a chroot with > >apparmor installed > > > >On 2019-02-10 20:06, Antonio Terceiro wrote: > >> I can reproduce this on a clean chroot (but not on a clean VM) > > > >I can also reproduce this in piuparts by

Bug#921667: [pkg-lxc-devel] Bug#921667: lxc, lava-dev: lxc fails to install along lava-dev --install-recommends

On Sun, Feb 10, 2019 at 12:13:43AM +0100, Pierre-Elliott Bécue wrote: > Le samedi 09 février 2019 à 22:19:13+0100, Andreas Beckmann a écrit : > > On 2019-02-09 21:51, Pierre-Elliott Bécue wrote: > > > I'm not sure that there is something we can do regarding lxc. Am I > > > wrong? > > > > You

Bug#909205: Bug #909205 in chef marked as pending

Control: tag -1 pending Hello, Bug #909205 in chef reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at:

Bug#921179: FTBFS: several test failures

Source: coquelicot Version: 0.9.6-1.1 Severity: serious Tags: ftbfs Justification: fails to build from source coquelicot currently fails to build in both unstable and buster, with several test failures. Log attached. -- System Information: Debian Release: buster/sid APT prefers unstable-debug

Bug#919818: Bug #919818 in test-kitchen marked as pending

Control: tag -1 pending Hello, Bug #919818 in test-kitchen reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at:

Bug#919962: Errors caused by not installing Recommend packages

Control: severity -1 normal Control: retitle -1 goaccess: absence of optional packages looks like an error, but it's not On Sun, Jan 20, 2019 at 03:57:22PM +0800, 積丹尼 Dan Jacobson wrote: > X-Debbugs-Cc: goacc...@prosoftcorp.com > Package: goaccess > Version: 1:1.2-4 > > Versions of packages

Bug#907718: python-dateutil breaks python-vobject autopkgtest

On Wed, Jan 09, 2019 at 05:55:47PM +0200, Adrian Bunk wrote: > On Thu, Dec 13, 2018 at 11:21:35PM +0100, Jonas Smedegaard wrote: > > Control: tags -1 help > > > > Quoting Guido Günther (2018-12-13 19:21:45) > > > On Thu, Dec 13, 2018 at 05:53:03PM +0100, Jonas Smedegaard wrote: > > > > @Guido,

Bug#919174: Bug #919174 in ruby-sinatra marked as pending

Control: tag -1 pending Hello, Bug #919174 in ruby-sinatra reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at:

Bug#918026: ruby-sinatra-contrib: uninstallable; depends on versions not present in the archive

On Wed, Jan 16, 2019 at 10:50:03AM +0900, Hideki Yamane wrote: > On Fri, 4 Jan 2019 10:22:08 -0300 > Antonio Terceiro wrote: > > Are you working on updating sinatra? I started working on a new sinatra > > upstream release to unbreak debci after a new rack was uploaded, a

Bug#918179: debci: configure error: undefined method `migrate'

Control: reassign -1 debci 1.14 Control: severity -1 serious Control: tag -1 + pending On Sun, Jan 06, 2019 at 08:12:58PM +0100, Paul Gevers wrote: > reassign 918179 src:rails 2:5.2.0+dfsg-2 > severity 918179 serious > > Hi Scott, > > On 04-01-2019 02:31, Scott Talbert wrote: > > I just updated

Bug#918026: ruby-sinatra-contrib: uninstallable; depends on versions not present in the archive

On Fri, Jan 04, 2019 at 10:22:08AM -0300, Antonio Terceiro wrote: > On Wed, Jan 02, 2019 at 10:58:15AM -0300, Antonio Terceiro wrote: > > Package: ruby-sinatra-contrib > > Version: 2.0.5-1 > > Severity: serious > > Justification: unsatisfiable dependencies > >

Bug#918026: ruby-sinatra-contrib: uninstallable; depends on versions not present in the archive

On Wed, Jan 02, 2019 at 10:58:15AM -0300, Antonio Terceiro wrote: > Package: ruby-sinatra-contrib > Version: 2.0.5-1 > Severity: serious > Justification: unsatisfiable dependencies > > # apt install ruby-sinatra-contrib > Reading package lists... Done > Building depende

Bug#918026: ruby-sinatra-contrib: uninstallable; depends on versions not present in the archive

Package: ruby-sinatra-contrib Version: 2.0.5-1 Severity: serious Justification: unsatisfiable dependencies # apt install ruby-sinatra-contrib Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have

Bug#911717: Bug #911717 in ruby marked as pending

Control: tag -1 pending Hello, Bug #911717 in ruby reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below, and you can check the diff of the fix at:

Bug#907790: Bug #907790 in ruby marked as pending

Control: tag -1 pending Hello, Bug #907790 in ruby reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below, and you can check the diff of the fix at:

Bug#900161: ruby-openssl: FTBFS against openssl 1.1.1

On Thu, Oct 04, 2018 at 12:10:53PM +0100, peter green wrote: > i tried to modify the testsuite to use stronger keys (patch > attatched), however after doing so the testsuite now hangs (relavent > output pasted at end of message). Not sure what is going wrong here (I > am neither a ruby expert or

Bug#900161: Bug #900161 in ruby-openssl marked as pending

Control: tag -1 pending Hello, Bug #900161 in ruby-openssl reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below, and you can check the diff of the fix at:

Bug#907118: error:141a318a:ssl routines:tls_process_ske_dhe:dh key too small

tc.net"; port = 6697; }; }; network { name = "freenode"; ssl = true; server { host = "irc.freenode.net"; port = 6697; }; }; network { name = "gimpnet"; ssl = true; server { host = "irc.gimp.org"; port = 6697; }; }; user { name = &qu

Bug#896660: Bug #896660 in vagrant marked as pending

Control: tag -1 pending Hello, Bug #896660 in vagrant reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below, and you can check the diff of the fix at:

Bug#896660: Bug #896660 in vagrant marked as pending

Control: tag -1 pending Hello, Bug #896660 in vagrant reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below, and you can check the diff of the fix at:

Bug#909205: FTBFS: 3 test failures

Source: chef Version: 13.8.7-2 Severity: serious Justification: fails to build from source This is the bottom of the build log: Finished in 1 minute 57.8 seconds (files took 6.76 seconds to load) 11422 examples, 3 failures, 24 pending Failed examples: rspec

Bug#905586: lxc: diff for NMU version 1:2.0.9-6.1

On Fri, Aug 31, 2018 at 02:42:15PM +0200, Salvatore Bonaccorso wrote: > Hi Antonio, > > On Fri, Aug 31, 2018 at 08:14:57AM -0300, Antonio Terceiro wrote: > > On Thu, Aug 30, 2018 at 10:06:15PM +0200, Salvatore Bonaccorso wrote: > > > Control: tags 905586 + pending

Bug#905586: lxc: diff for NMU version 1:2.0.9-6.1

On Thu, Aug 30, 2018 at 10:06:15PM +0200, Salvatore Bonaccorso wrote: > Control: tags 905586 + pending > > > Dear maintainer, > > I've prepared an NMU for lxc (versioned as 1:2.0.9-6.1) and > uploaded it to DELAYED/5. Thanks! > Please feel free to tell me if I should delay it longer. on the

Bug#907118: error:141a318a:ssl routines:tls_process_ske_dhe:dh key too small

Control: severity -1 important Hi, I would like to reinforce the request for a stable update: - according to the openssl maintainer, this is a security issue and should be fixed in stable - without such fix, bip on stable will soon be unusable to any client using a recent enough openssl

Bug#903063: Bug #903063 in coquelicot marked as pending

Control: tag -1 pending Hello, Bug #903063 in coquelicot reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below, and you can check the diff of the fix at:

Bug#903341: Bug #903341 in ruby-rubymail marked as pending

Control: tag -1 pending Hello, Bug #903341 in ruby-rubymail reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below, and you can check the diff of the fix at:

Bug#905439: su from util-linux breaks autopkgtest

Control: tag -1 + moreinfo unreproducible On Sat, Aug 04, 2018 at 03:11:17PM +, Lumin wrote: > Package: autopkgtest > Version: 5.4.2 > Severity: serious > > the "su" command from util-linux breaks autopkgtest. The previous > working one comes from shadow. > > python-h5py-dbg is already the

Bug#904921: wand: Wrong dependencies on libmagickcore-6.q16-6 instead of libmagickwand-6.q16-6

Hi On Mon, Jul 30, 2018 at 10:27:57AM -0300, Antonio Terceiro wrote: > FWIW, I intend to upload the patch below. wand is used as a test case in > the test suite of autopkgtest, and this bug causes it to fail. I noticed you are working in the git repository, so I will *not* be making

Bug#904921: wand: Wrong dependencies on libmagickcore-6.q16-6 instead of libmagickwand-6.q16-6

Hi, On Sun, Jul 29, 2018 at 10:57:44AM -0300, Antonio Terceiro wrote: > Source: wand > Version: Wrong dependencies on libmagickcore-6.q16-6 instead of > libmagickwand-6.q16-6 > Severity: serious > Justification: missing dependencies > > I think there is a typo in

Bug#904870: Bug #904870 in autopkgtest marked as pending

he existing behavior. Closes: #904870 Signed-off-by: Antonio Terceiro Signed-off-by: Chris Hofstaedtler (this message was generated automatically) -- Greetings https://bugs.debian.org/904870

Bug#904921: wand: Wrong dependencies on libmagickcore-6.q16-6 instead of libmagickwand-6.q16-6

Source: wand Version: Wrong dependencies on libmagickcore-6.q16-6 instead of libmagickwand-6.q16-6 Severity: serious Justification: missing dependencies I think there is a typo in Depends: which causes this: $ python3 -c 'from wand.image import Image' Traceback (most recent call last): File

Bug#899124: fonts-font-awesome: completely breaks web applications, with no notice

On Sat, May 26, 2018 at 02:29:56AM +0200, Pierre-Elliott Bécue wrote: > Le mardi 22 mai 2018 à 21:16:14+0530, Vasudev Kamath a écrit : > > Hi Antonio, > > > > Antonio Terceiro <terce...@debian.org> writes: > > > > > Control: forwarded -1 > >

Bug#899324: ruby-font-awesome-rails: broken with fonts-font-awesome 5

Package: ruby-font-awesome-rails Version: 4.7.0.2-1 Severity: grave Justification: renders package unusable Recently fonts-font-awesome 5 has been uploaded to ustable. There are some significant changes upstream, including but not limited to font files being renamed. fonts-font-awesome 5.0.10-4

Bug#899124: fonts-font-awesome: completely breaks web applications, with no notice

Control: forwarded -1 https://salsa.debian.org/fonts-team/fonts-font-awesome/merge_requests/1 On Sun, May 20, 2018 at 06:15:08PM -0300, Antonio Terceiro wrote: > Control: reopen -1 > > On Sun, May 20, 2018 at 10:32:38PM +0530, Vasudev Kamath wrote: > > Antonio Terceiro <t

Bug#899124: fonts-font-awesome: completely breaks web applications, with no notice

Control: reopen -1 On Sun, May 20, 2018 at 10:32:38PM +0530, Vasudev Kamath wrote: > Antonio Terceiro <terce...@debian.org> writes: > > 2) revert the changes in fonts-font-awesome in unstable, upload the > > new release to experimental, and give people a few months to

Bug#899124: fonts-font-awesome: completely breaks web applications, with no notice

Package: fonts-font-awesome Version: 5.0.10-1 Severity: grave Font-Awesome version completely changed everything, and any web applications that use it are now broken unless they go through some manual intervention. https://fontawesome.com/how-to-use/upgrading-from-4 As a maintainer of multiple

Bug#897653: tar 1.30 breaks pristine-tar

Control: tag -1 + patch On Mon, May 14, 2018 at 11:07:50AM -0700, Bdale Garbee wrote: > Paul Eggert <egg...@cs.ucla.edu> writes: > > > On 05/14/2018 07:56 AM, Antonio Terceiro wrote: > >> I still need to study the > code a bit further to try to come up with a >

Bug#898501: Broken symlinks

On Mon, May 14, 2018 at 03:10:34PM +0200, Paul Gevers wrote: > On Sun, 13 May 2018 14:14:05 -0300 Antonio Terceiro > <terce...@debian.org> wrote: > > not only that. there are 60+ packages that directly build-depend on > > fonts-font-awesome, and these changes probably

Bug#897653: tar 1.30 breaks pristine-tar

data (see below for one example). This is not a problem for newly imported tarballs, but it is a problem for tarballs that were imported with tar < 1.30. On Thu, May 03, 2018 at 05:14:54PM -0300, Antonio Terceiro wrote: > Package: tar > Version: 1.30+dfsg-1 > Severity: grave >

Bug#869191: pristine-tar: pristine-xz failed to reproduce build of ../util-linux_2.30.1.orig.tar.xz

Control: severity -1 important On Sun, May 13, 2018 at 03:00:44PM +0200, Alf Gaida wrote: > Control: severity -1 grave > > can confirm that the patch work fine. sure, thanks for testing. I have applied the patch to the git repository, and it will be available in the next upload. However this

Bug#898501: Broken symlinks

On Sat, 12 May 2018 12:39:50 -0700 Sean Whitton wrote: > Package: fonts-font-awesome > Version: 5.0.10-1 > Severity: grave > Control: affects -1 cider > > Dear maintainer, > > The latest upload introduces some new broken symlinks: > > fonts-font-awesome:

Bug#898524: FTBFS: unsatisfiable dependencies

Source: stylish-haskell Version: 0.8.1.0-1 Severity: serious Justification: fails to build from source Tags: sid buster Install stylish-haskell build dependencies (apt-based resolver) --- Installing build dependencies Reading package

Bug#897653: tar 1.30 breaks pristine-tar

Package: tar Version: 1.30+dfsg-1 Severity: grave Justification: causes non-serious data loss Hi, After tar 1.30 arrived in unstabled, pristine-tar can no longer reproduce tarballs that it previously could. For example I just hit this with bundler: $ debcheckout -a bundler declared git

Bug#894749: #894749 - libgoogle-perftools4: missing libprofiler.so.0 on ppc64el (was "ruby-grpc: FTBFS on ppc64el: cannot open shared object file: No such file or directory")

Control: reassign -1 libgoogle-perftools4 2.6.90-0.1 Control: retitle -1 libgoogle-perftools4: missing libprofiler.so.0 on ppc64el Control: affects -1 + ruby-grpc On Tue, 03 Apr 2018 22:50:29 +0200 Emilio Pozuelo Monfort wrote: > Source: ruby-grpc > Version: 1.3.2+debian-4 >

Bug#894305: package build-depends on legacy ruby2.3-dev

On Thu, 29 Mar 2018 01:11:20 +0800 Matthias Klose wrote: > Package: src:ruby-debugger-ruby-core-source > Version: 1.3.8+ds-1 > Severity: serious > Tags: sid buster patch > > the package build-depends on legacy ruby2.3-dev which is going to be removed. > Is > there are reason

Bug#892484: ruby-pgplot: missing ruby2.5 build

Source: ruby-pgplot Version: 0.1.9-3 Severity: serious Justification: ruby2.5 will be the default ruby in buster Tags: buster sid Since ruby-pgplot depends on a package from non-free, it won't be rebuilt on the buildds. So ruby-pgplot needs to be manually rebuilt and uploaded by someone who cares

Bug#892074: uwsgi: FTBFS with ruby2.5 as default

Source: uwsgi Version: 2.0.15-10.2 Severity: serious Justification: fails to build from source I am about to upload ruby-defaults to unstable, switching the default Ruby to ruby2.5. With that in place, uwsgi fails to build from source like this: [...] CFLAGS="-g -O2 -fdebug-prefix-map=/<>=.

Bug#892072: weechat: build against ruby2.5

Source: weechat Version: 1.9.1-1 Severity: serious Justification: will FTBFS soon Tags: patch Hi, I am about to upload ruby-defaults to unstable, switching the default Ruby to ruby2.5, and ruby2.3 support will be removed right after that. Please consider applying the attached patch, obtained

Bug#889873: vagrant: unable to download images (moved from atlas.hashicorp.com to app.vagrantup.com)

Control: tag -1 + pending Control: block -1 by 891484 On Sat, Feb 10, 2018 at 01:39:33PM -0500, James McCoy wrote: > On Thu, Feb 08, 2018 at 09:02:03AM +0100, Lucas Nussbaum wrote: > > It seems that Hashicorp decided to migrate from e.g. > > https://atlas.hashicorp.com/alpine/alpine64 > > to > >

Bug#890046: ruby-json: disabling jruby support

Control: retitle -1 jruby support broken on several architectures Control: severity -1 normal Hi, ruby-json currently FTBFS, and is blocking the Ruby transition, as reported in bug #890046 (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890046) All failures are related to the jruby support,

Bug#891449: jruby: system() does not work on arm64

Package: jruby Version: 9.1.13.0-1 Severity: grave Justification: renders package unusable When debugging #890046 on ruby-json, I realized that I cannot execute any program with system() under jruby on arm64: 8<8<8<-

Bug#890046: no build artifacts included in ruby-json, built for jruby

On Sat, 10 Feb 2018 15:04:25 +0100 Matthias Klose wrote: > there are no build artifacts included in ruby-json, built for jruby. Except > for > an additional README. yes, there are: $ dpkg -L ruby-json | grep jar /usr/lib/ruby/vendor_ruby/json/ext/generator.jar

Bug#889663: FTBFS: Unable to load the SpatiaLite library extension

Source: djangorestframework-gis Version: 0.12-1 Severity: serious Justification: fails to build from source dh_auto_test -- --system=custom --test-args="{interpreter} ./runtests.py" I: pybuild base:184: python2.7 ./runtests.py Creating test database for alias 'default'... Traceback (most recent

Bug#889026: ruby-shadow: FTBFS with ruby2.5: too many arguments to function 'rb_struct_ptr' / subscripted value is neither array nor pointer nor vector

Source: ruby-shadow Severity: serious Justification: Fails to build from source User: debian-r...@lists.debian.org Usertags: ruby2.5 I am filing this at severity serious as I am about to enable building for ruby2.5 in unstable.

Bug#889025: ruby-odbc: FTBFS with ruby2.5: invalid operands to binary / (have 'char *' and 'char *')

Source: ruby-odbc Severity: serious Justification: Fails to build from source User: debian-r...@lists.debian.org Usertags: ruby2.5 I am filing this at severity serious as I am about to enable building for ruby2.5 in unstable.

Bug#889023: ruby-gsl: FTBFS with ruby2.5: 'rb_cFixnum' undeclared

Source: ruby-gsl Severity: serious Justification: Fails to build from source User: debian-r...@lists.debian.org Usertags: ruby2.5 I am filing this at severity serious as I am about to enable building for ruby2.5 in unstable. [...] gcc -I. -I/usr/include/x86_64-linux-gnu/ruby-2.5.0

Bug#889021: ruby-ffi-yajl: FTBFS with ruby2.5: 'rb_cFixnum' undeclared

Source: ruby-ffi-yajl Severity: serious Justification: Fails to build from source User: debian-r...@lists.debian.org Usertags: ruby2.5 I am filing this at severity serious as I am about to enable building for ruby2.5 in unstable.

Bug#865588: [Python-modules-team] Bug#865588: Bug#865588: djangorestframework FTBFS with Django 1.11: ERROR collecting tests/test_fields.py

On Wed, Jan 10, 2018 at 05:38:02PM +1100, Brian May wrote: > Thijs Kinkhorst writes: > > > We're half a year on, so has this now changed? (I tried to check out the > > git repo and build it, but that had several problems so I might be missing > > one or two pieces to quickly

Bug#882404: ruby2.3: sometimes FTBFS on mips* - Net::TestSMTP#test_tls_connect timeout

Control: reopen -1 On Wed, Nov 22, 2017 at 10:54:21AM +, James Cowgill wrote: > Source: ruby2.3 > Version: 2.3.5-1 > Severity: serious > Tags: sid buster patch > > Hi, > > Currently ruby2.3 FTBFS on mips* with the error: > > 1) Error: > > Net::TestSMTP#test_tls_connect: > >

Bug#884772: projectile: FTBFS with new version of mkdocs

Source: projectile Severity: serious Justification: fails to build from source dpkg-source: info: using source format '3.0 (quilt)' dpkg-source: info: building projectile using existing ./projectile_0.14.0.orig.tar.xz dpkg-source: info: building projectile in projectile_0.14.0-1.debian.tar.xz

Bug#879231: security update: ruby2.3

On Sat, Nov 04, 2017 at 10:08:36PM +0100, Salvatore Bonaccorso wrote: > Hi Antonio > > Sorry for the late reply > > On Mon, Oct 23, 2017 at 11:49:28AM -0200, Antonio Terceiro wrote: > > Hi security team, > > > > I have prepared a security update for ruby2.3. >

Bug#879231: security update: ruby2.3

On Sat, Nov 04, 2017 at 10:45:06PM +, Adam D. Barratt wrote: > On Sat, 2017-11-04 at 22:08 +0100, Salvatore Bonaccorso wrote: > > Hi Antonio > > > > Sorry for the late reply > > > > On Mon, Oct 23, 2017 at 11:49:28AM -0200, Antonio Terceiro wrote: > >

Bug#880502: [pkg-lxc-devel] Bug#880502: lxc: cannot start container with kernel 4.13.10

Control: severity -1 important On Thu, Nov 02, 2017 at 11:04:10AM -0200, Antonio Terceiro wrote: > On Wed, Nov 01, 2017 at 03:38:23PM +0100, Evgeni Golov wrote: > > Ohai, > > > > On Wed, Nov 01, 2017 at 12:00:12PM -0200, Antonio Terceiro wrote: > > > > l

Bug#880502: [pkg-lxc-devel] Bug#880502: lxc: cannot start container with kernel 4.13.10

On Wed, Nov 01, 2017 at 03:38:23PM +0100, Evgeni Golov wrote: > Ohai, > > On Wed, Nov 01, 2017 at 12:00:12PM -0200, Antonio Terceiro wrote: > > > lxc-start 20171101123914.655 ERRORlxc_apparmor - > > > lsm/apparmor.c:apparmor_process_label_set:220 - If you

Bug#880502: lxc: cannot start container with kernel 4.13.10

Control: retitle -1 lxc: cannot start container with kernel 4.13.10 On Wed, Nov 01, 2017 at 11:32:31AM -0200, Antonio Terceiro wrote: > Package: lxc > Version: 1:2.0.9-3 > Severity: serious > > I'm filing this in lxc initially as I don't know exactly where the issue > is yet

Bug#880502: lxc: cannot start container (kernel related?)

Package: lxc Version: 1:2.0.9-3 Severity: serious I'm filing this in lxc initially as I don't know exactly where the issue is yet. We will probably want to reassign it. Something other than lxc itself changed recently in unstable which makes lxc not able to start a Debian container: # lxc-start

Bug#879231: security update: ruby2.3

) +Original patch by Eric Wong + + -- Antonio Terceiro <terce...@debian.org> Sun, 22 Oct 2017 12:45:48 -0200 + ruby2.3 (2.3.3-1+deb9u1) stretch-security; urgency=high * Fix arbitrary heap exposure problem in the JSON library (Closes: #873906) diff --git a/ext/openssl/ossl_asn1.c b/ext/o

Bug#878912: docker.io: docker run fails saying that containerd-shim not installed

Package: docker.io Version: 1.13.1~ds2-3 Severity: grave Justification: renders package unusable On a completely up to date sid system: $ docker run -it --rm debian:sid docker: Error response from daemon: containerd-shim not installed on system. I tried to be a smart ass and symlink

Bug#873906: ruby2.3 security update

ability in the query command. Discovered by Yusuke + Endoh, fix by Samuel Giddins. + [CVE-2017-0900] +- Fix a vulnerability in the gem installer that allowed a malicious gem to + overwrite arbitrary files. Discovered by Yusuke Endoh, fix by Samuel + Giddins. + [CVE-2017-09

Bug#869031: marked as pending

f1bca5ef65382a6bd370a501e88a08256076ca7f Author: Antonio Terceiro <terce...@debian.org> Date: Fri Aug 11 11:53:01 2017 -0400 New upstream release + dh-make-ruby -w diff --git a/debian/changelog b/debian/changelog index 31da8d6..a3c6286 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,14 @@

Bug#869615: mitmproxy: uninstallable in unstable (Depends: python-hyperframe (< 5) but 5.1.0-1 is to be installed)

Package: mitmproxy Version: 0.18.2-6 Severity: serious Justification: Policy 3.5 $ sudo apt install mitmproxy Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible

Bug#867651: marked as pending

73e454e2b46650b736b5bd4fea5d3759650d1c2c Author: Antonio Terceiro <terce...@debian.org> Date: Sun Jul 16 14:25:53 2017 -0300 New upstream release diff --git a/debian/changelog b/debian/changelog index 5c0c122..40e2366 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,10 @@ +ruby-rubymail (1

Bug#865667: ruby-prof FTBFS: ERROR: Test "ruby2.3" failed.

Control: tag -1 + unreproducible Control: severity -1 important On Fri, Jun 23, 2017 at 06:36:37PM +0300, Adrian Bunk wrote: > Source: ruby-prof > Version: 0.16.2+dfsg-2 > Severity: serious > Tags: buster sid > > Some recent change in unstable makes ruby-prof FTBFS: > >

Bug#864377: docker.io: Failure to install (cannot start daemon)

On Wed, 07 Jun 2017 14:19:16 -0400 Robbie Harwood wrote: > Package: docker.io > Version: 1.13.1~ds1-2 > Severity: grave > Justification: renders package unusable > > Dear Maintainer, > > During a system upgrade, I got the following: > > Setting up docker.io

<    1   2   3   4   5   6   7   8   >