close 1069348 0.16.0-2
thanks
Control: tag -1 pending
Hello,
Bug #1068537 in ruby-ethon 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:
Control: tag -1 pending
Hello,
Bug #1066854 in ruby-magic 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:
Control: tag -1 pending
Hello,
Bug #1068589 in gem2deb 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:
On Tue, Mar 12, 2024 at 09:13:09PM +0100, Sebastian Andrzej Siewior wrote:
> tried with 1.50+nmu2 which is in deferred for the next 11h. So tomorrow
> it should be all good.
Please make sure to commit the patch to the pristine-tar git repository
as well.
signature.asc
Description: PGP signature
Control: tag -1 pending
Hello,
Bug #1065091 in gtg 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:
Package: gtg
Version: 0.6-6
Severity: grave
Justification: renders package unusable
Dear Maintainer,
$ gtg
2024-02-29 14:44:05,373 - ERROR - application:do_activate:153 - Exception
during activation
Traceback (most recent call last):
File
Control: tag -1 pending
Hello,
Bug #1058111 in cmdtest 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:
On Thu, Dec 21, 2023 at 10:41:57AM +0100, Helmut Grohne wrote:
> ## Upgrading using dpkg directly?
>
> We already have quite a number of packages that use Conflicts to prevent
> file loss in upgrades in a very similar way to #1058937 (Ben's
> libnfsidmap1 bug) even in released versions of Debian.
Control: forcemerge 1054256 -1
Control affects 1054256 + src:rails
On Fri, Oct 27, 2023 at 09:27:35PM +0200, Lucas Nussbaum wrote:
> Source: rails
> Version: 2:6.1.7.3+dfsg-2
> Severity: serious
> Justification: FTBFS
> Tags: trixie sid ftbfs
> User: lu...@debian.org
> Usertags: ftbfs-20231027
Package: ruby-blade
Version: 0.7.1-4
Severity: serious
Justification: uninstallable
After the last upload, ruby-blade ended up with a dependency on
ruby-thin, which does not exist.
8<8<8<-
$ LANG=C sudo apt install
Package: ohcount
Version: 4.0.0-3
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: debian-...@lists.debian.org
Dear Maintainer,
ohcount segfaults (and sometimes aborts with a Bus error) on arm64,
almost 90% of the time. I tried this on an up to date arm64 Debian
testing
On Fri, Aug 25, 2023 at 08:52:49PM +0200, François Mazen wrote:
> Dear Antonio,
>
> thanks for the crash report! I can reproduce it easily with unstable
> distribution and the call stack points to pango_font_description_to_string
> method.
>
> The issues seems to have been already reported
Package: gtg
Version: 0.6-4
Severity: grave
Justification: renders package unusable
Dear Maintainer,
gtg crashes on startup very often.
~$ gtg
2023-08-24 14:38:12,928 - WARNING - adaptive_button:do_forall:279 - Got error
in for but it should've stay valid:
On Thu, Jun 15, 2023 at 10:48:57PM +0200, Christian Kastner wrote:
>
> Package: debci
> Version: 3.6
> Severity: serious
> Tags: security
> X-Debbugs-Cc: Debian Security Team
>
> Hi,
>
> When using authentication in AMQP connections, the username and password
> supplied in the --url option to
Control: severity -1 normal
On Fri, 05 May 2023 15:17:37 + =?utf-8?q?Jens_Mei=C3=9Fner?=
wrote:
> Package: dnsmasq
> Version: 2.89-1
> Severity: grave
> Justification: renders package unusable
> X-Debbugs-Cc: heptal...@gmx.de
>
> Hello,
>
> dnsmasq on bookworm fails to start after
Control: tag -1 pending
Hello,
Bug #1017218 in ruby-parallel 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:
Control: tag -1 pending
Hello,
Bug #1031238 in debci 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:
Control: severity -1 normal
Failing on some inputs is not a justification for a `serious` severity.
Thus, I am downgrading this bug to normal.
signature.asc
Description: PGP signature
close 1025125
thanks
Control: tag -1 pending
Hello,
Bug #1004068 in origami-pdf 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:
Control: tag -1 pending
Hello,
Bug #1028871 in djangorestframework 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:
On Wed, Jan 18, 2023 at 06:27:59PM +0200, Adrian Bunk wrote:
> Control: tags 1026499 + patch
> Control: tags 1026499 + pending
>
> Dear maintainer,
>
> I've prepared an NMU for rows (versioned as 0.4.1-5.1) and uploaded
> it to DELAYED/14. Please feel free to tell me if I should cancel it.
I'm
Control: tag -1 pending
Hello,
Bug #1028890 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:
; Date: Sat, 24 Dec 2022 14:40:11 +
> From: Debian FTP Masters
> To: 1026779-cl...@bugs.debian.org
> Subject: Bug#1026779: fixed in binutils 2.39.50.20221224-1
> Reply-To: Matthias Klose
> Message-Id:
>
> Date: Tue, 20 Dec 2022 21:04:46 -0300
> From: Antonio T
Control: reassign -1 src:ruby-specinfra
Control: forcemerge #1027347 -1
Control: affects #1027347 src:itamae
On Fri, Dec 30, 2022 at 05:20:58PM +0100, Lucas Nussbaum wrote:
> Source: itamae
> Version: 1.14.1-1
> Severity: serious
> Justification: FTBFS
> Tags: bookworm sid ftbfs
> User:
Control: tag -1 pending
Hello,
Bug #1027449 in ruby-dbm 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:
Control: tag -1 + pending
On Fri, Dec 30, 2022 at 08:08:50PM -0300, Antonio Terceiro wrote:
> Control: reassign -1 dhelp
> Control: severity -1 serious
> Control: retitle: dhelp: depends on module removed from the Ruby stdlib (dbm)
>
> On Fri, Dec 30, 2022 at 06:09:03PM +0100, Dre
Source: ruby-rubocop-performance
Version: 1.7.1-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-r...@lists.debian.org
Usertags: ruby-rspec-3.12
Hi,
I'm about to upload ruby-rspec 3.12. During a test rebuild with that version,
ruby-rubocop-performance failed to
Source: ruby-mysql2
Version: 0.5.3-4
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-r...@lists.debian.org
Usertags: ruby-rspec-3.12
Hi,
I'm about to upload ruby-rspec 3.12. During a test rebuild with that version,
ruby-mysql2 failed to build. I retried it with the
Source: ruby-localhost
Version: 1.1.9-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-r...@lists.debian.org
Usertags: ruby-rspec-3.12
Hi,
I'm about to upload ruby-rspec 3.12. During a test rebuild with that version,
ruby-localhost failed to build. I retried it with
Control: reassign -1 ruby-rspec-expectations
Control: retitle -1 ruby-rspec-expectations: raise_error() matcher does not
work with ruby3.1
Control: forwarded -1 https://github.com/rspec/rspec-expectations/issues/1338
Control: affects -1 src:ruby-hashie
On Sat, Nov 19, 2022 at 03:29:31PM +0200,
Control: tag -1 pending
Hello,
Bug #1026897 in ruby-tilt 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:
Control: tag -1 pending
Hello,
Bug #1026178 in ruby-tzinfo 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:
Source: ruby-tilt
Version: 2.0.11-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
Hi,
After updating ruby-haml to 6.1.1, ruby-tilt fails to build with a test
failure.
Relevant part (hopefully):
> /usr/bin/ruby3.1 /usr/bin/gem2deb-test-runner
>
>
Source: ruby-html2haml
Version: 2.2.0-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1413:in `rescue in block
Source: ruby-haml-rails
Version: 2.0.1-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
Hi,
After updating ruby-haml to 6.1.1, ruby-haml-rails has unsatisfiable
build dependencies.
Relevant part (hopefully):
>
Source: ruby-haml-contrib
Version: 1.0.0.1-2.1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
Hi,
After updaring ruby-haml to 6.6.1, ruby-haml-contrib fails to build with
a test failure.
Relevant part (hopefully):
>
Source: asciidoctor
Version: 2.0.17-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
Hi,
I'm working on updating ruby-haml to the new upstream versinon 6.1.1,
and when trying asciidoctor against that the tests fail.
Relevant part (hopefully):
> /usr/bin/ruby3.1
Source: binutils
Version: 2.39.50.20221208-5
Severity: serious
Dear Maintainer,
Up to src:binutils 2.39-8, binutils-${DEB_HOST_MULTIARCH} and
libbinutils:${DEB_HOST_ARCH} were coinstallable. Upgrading a system
where both are installed (e.g. binutils-aarch64-linux-gnu and
libbinutils:arm64) fails
Package: jekyll
Version: 3.9.0+dfsg-5
Severity: serious
Tags: upstream
Dear Maintainer,
Working to get ruby3.1 as the default Ruby version it was noticed that
ruby-safe-yaml is incompatible with ruby3.1 and thus deprecated. Most
upstreams have dropped their dependencies on it; I checked and
On Fri, Dec 16, 2022 at 06:31:41PM +0100, Guillem Jover wrote:
> Package: vagrant
> Version: 2.2.19+dfsg-2
> Severity: serious
>
> Hi!
>
> Since virtualbox 7.0.4 got uploaded, vagrant is no longer installable
> in Debian sid. I assume this will require packaging a new upstream
> release to
Package: ruby-asciidoctor-pdf
Version: 1.6.2-1
Severity: serious
Tags: upstream
User: debian-r...@lists.debian.org
Usertags: ruby3.1
Dear Maintainer,
Working to get ruby3.1 as the default Ruby version it was noticed that
ruby-safe-yaml is incompatible with ruby3.1 and thus deprecated. Most
Control: tag -1 pending
Hello,
Bug #1019635 in ruby-mail 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:
Control: tag -1 pending
Hello,
Bug #1025261 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:
close 1024175 4.1.0-1
close 1024174 1.0.1-1
thanks
These bugs have been closed in the last uploads of ruby-omniauth-gitlab and
ruby-omniauth-dingtalk-oauth2, respectively, but I missed the bugs already
reported.
Control: tag -1 pending
Hello,
Bug #1006022 in puma 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:
On Wed, Oct 19, 2022 at 09:57:34PM +0200, Moritz Muehlenhoff wrote:
> On Tue, Oct 18, 2022 at 06:09:42PM -0300, Antonio Terceiro wrote:
> > Hi,
> >
> > On Thu, Oct 13, 2022 at 09:13:18PM +0200, Moritz Mühlenhoff wrote:
> > > Source: lava
> > > X-Debbugs-CC:
On Tue, Oct 18, 2022 at 06:09:45PM -0300, Antonio Terceiro wrote:
> Hi,
>
> On Thu, Oct 13, 2022 at 09:13:18PM +0200, Moritz Mühlenhoff wrote:
> > Source: lava
> > X-Debbugs-CC: t...@security.debian.org
> > Severity: grave
> > Tags: security
> >
>
# with the argument from the search
+q |= getattr(self, key)(self.terms["search"])
+
# now add "class specials" - from an iterable hash
# datetime uses (start_time__lte=timezone.now()-timedelta(days=3)
-data = data.filter(self._t
close 979887 2022.01.3-3
thanks
This has actually been fixed before 2022.01. Closing.
close 1020776
thanks
Hi,
On Fri, Oct 07, 2022 at 01:50:56AM +0300, Adrian Bunk wrote:
> On Mon, Sep 12, 2022 at 08:24:43PM -0300, Antonio Terceiro wrote:
> > Source: ruby-ahoy-email
> > Version: 1.1.1-2
> > Severity: serious
> > Justification: FTBFS
> > Tags: bookworm sid ftbfs
>
Control: tag -1 + unreproducible
Control: severity -1 important
Hi,
On Wed, Sep 21, 2022 at 07:20:31PM +0200, Sebastian Ramacher wrote:
> Source: ruby-prof
> Version: 1.4.3-1
> Severity: serious
> Tags: ftbfs
> Justification: fails to build from source (but built successfully in the past)
>
Source: unicorn-engine
Version: 2.0.0-3
Severity: serious
Tags: ftbfs
Justification: fails to build from source
Dear Maintainer,
unicorn-engine fails to build on s390x, with several test failures. It
seems to pass on all other release architectures.
Source: ruby-fog-core
Version: 2.1.0-3.1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-r...@lists.debian.org
Usertags: ruby3.1
Hi,
We are about to start the ruby3.1 transition in unstable. While trying to
rebuild ruby-fog-core with ruby3.1 enabled, the build
Source: ruby-enumerize
Version: 2.4.0-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-r...@lists.debian.org
Usertags: ruby3.1
Hi,
We are about to start the ruby3.1 transition in unstable. While trying to
rebuild ruby-enumerize with ruby3.1 enabled, the build
Source: ruby-did-you-mean
Version: 1.2.1-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-r...@lists.debian.org
Usertags: ruby3.1
Hi,
We are about to start the ruby3.1 transition in unstable. While trying to
rebuild ruby-did-you-mean with ruby3.1 enabled, the build
Source: ruby-factory-bot
Version: 6.2.0-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-r...@lists.debian.org
Usertags: ruby3.1
Hi,
We are about to start the ruby3.1 transition in unstable. While trying to
rebuild ruby-factory-bot with ruby3.1 enabled, the build
Source: ruby-excon
Version: 0.88.0-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-r...@lists.debian.org
Usertags: ruby3.1
Hi,
We are about to start the ruby3.1 transition in unstable. While trying to
rebuild ruby-excon with ruby3.1 enabled, the build failed.
Source: ruby-dalli
Version: 3.0.6-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-r...@lists.debian.org
Usertags: ruby3.1
Hi,
We are about to start the ruby3.1 transition in unstable. While trying to
rebuild ruby-dalli with ruby3.1 enabled, the build failed.
Source: ruby-delayed-job
Version: 4.1.9-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-r...@lists.debian.org
Usertags: ruby3.1
Hi,
We are about to start the ruby3.1 transition in unstable. While trying to
rebuild ruby-delayed-job with ruby3.1 enabled, the build
Source: ruby-delayed-job-active-record
Version: 4.1.6-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-r...@lists.debian.org
Usertags: ruby3.1
Hi,
We are about to start the ruby3.1 transition in unstable. While trying to
rebuild ruby-delayed-job-active-record with
Source: ruby-crack
Version: 0.4.4-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-r...@lists.debian.org
Usertags: ruby3.1
Hi,
We are about to start the ruby3.1 transition in unstable. While trying to
rebuild ruby-crack with ruby3.1 enabled, the build failed.
Source: ruby-capybara
Version: 3.36.0+ds-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-r...@lists.debian.org
Usertags: ruby3.1
Hi,
We are about to start the ruby3.1 transition in unstable. While trying to
rebuild ruby-capybara with ruby3.1 enabled, the build
Source: ruby-celluloid
Version: 0.17.3-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-r...@lists.debian.org
Usertags: ruby3.1
Hi,
We are about to start the ruby3.1 transition in unstable. While trying to
rebuild ruby-celluloid with ruby3.1 enabled, the build
Source: ruby-asset-sync
Version: 2.11.0-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-r...@lists.debian.org
Usertags: ruby3.1
Hi,
We are about to start the ruby3.1 transition in unstable. While trying to
rebuild ruby-asset-sync with ruby3.1 enabled, the build
Source: ruby-ahoy-email
Version: 1.1.1-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-r...@lists.debian.org
Usertags: ruby3.1
Hi,
We are about to start the ruby3.1 transition in unstable. While trying to
rebuild ruby-ahoy-email with ruby3.1 enabled, the build
Source: ruby-activerecord-import
Version: 1.2.0-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-r...@lists.debian.org
Usertags: ruby3.1
Hi,
We are about to start the ruby3.1 transition in unstable. While trying to
rebuild ruby-activerecord-import with ruby3.1
Source: redmine
Version: 5.0.0-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-r...@lists.debian.org
Usertags: ruby3.1
Hi,
We are about to start the ruby3.1 transition in unstable. While trying to
rebuild redmine with ruby3.1 enabled, the build failed.
Relevant
Source: rubocop
Version: 0.89.1+dfsg-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-r...@lists.debian.org
Usertags: ruby3.1
Hi,
We are about to start the ruby3.1 transition in unstable. While trying to
rebuild rubocop with ruby3.1 enabled, the build failed.
Source: roodi
Version: 5.0.0-4
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-r...@lists.debian.org
Usertags: ruby3.1
Hi,
We are about to start the ruby3.1 transition in unstable. While trying to
rebuild roodi with ruby3.1 enabled, the build failed.
Relevant part
Source: feed2imap
Version: 1.3.1-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-r...@lists.debian.org
Usertags: ruby3.1
Hi,
We are about to start the ruby3.1 transition in unstable. While trying to
rebuild feed2imap with ruby3.1 enabled, the build failed.
Source: bsfilter
Version: 1:1.0.19-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-r...@lists.debian.org
Usertags: ruby3.1
Hi,
We are about to start the ruby3.1 transition in unstable. While trying to
rebuild bsfilter with ruby3.1 enabled, the build failed.
Source: asciidoctor
Version: 2.0.16-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-r...@lists.debian.org
Usertags: ruby3.1
Hi,
We are about to start the ruby3.1 transition in unstable. While trying to
rebuild asciidoctor with ruby3.1 enabled, the build failed.
severity 1015305 serious
severity 1015309 serious
severity 1015310 serious
severity 1015322 serious
severity 1015327 serious
severity 1015328 serious
severity 1015329 serious
severity 1015334 serious
thanks
Hi,
We are about to start the ruby3.1 transition. I will coordinate this
with the release
Control: tag -1 pending
Hello,
Bug #1005442 in ruby-em-http-request 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:
Control: tag -1 pending
Hello,
Bug #1006026 in ruby-axiom-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:
Control: retitle -1 ruby-axiom-types: FTBFS randomly: ArgumentError: Cannot
proxy frozen objects, rspec-mocks relies on proxies for method stubbing and
expectations.
I tried this locally and couldn't reproduce twice in row, first on my
main system, then with sbuild. I then tried 10 times in a
Package: autopkgtest
Version: 5.23
Severity: grave
Justification: renders package unusable
This was first noticed by a salsa-ci user:
https://salsa.debian.org/salsa-ci-team/pipeline/-/issues/270#note_328972
I then tested locally, and reproduced the same issue with the snapshot I
was running
/5dbe7a8f795d2427379cb76c6fd64de69f963cfb
debian/rules: ensure rbconfig.rb is reproducible regardless of usr-merge
Closes: #1006471
Signed-off-by: Vagrant Cascadian
Signed-off-by: Antonio Terceiro
Control: tag -1 + pending
On Wed, Jul 27, 2022 at 02:52:47PM +0100, Simon McVittie wrote:
> Is the Ruby build intentionally putting EGREP into rbconfig.rb for use by
> some other component, or is it just populating that file with everything
> that Autoconf happens to have discovered, on the off
Control: clone -1 -2
Control: reassign -2 src:ruby3.1
Control: retitle -2 ruby3.1: reproducible builds: embeds path to various
binaries
Hi,
On Sun, Jul 17, 2022 at 12:04:45PM +0100, Simon McVittie wrote:
> Control: severity -1 serious
>
> On Fri, 25 Feb 2022 at 15:26:51 -0800, Vagrant
Source: xapian-bindings
Version: 1.4.20-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-r...@lists.debian.org
Usertags: ruby3.1
Hi,
We are about to start the ruby3.1 transition in unstable. While trying
to rebuild xapian-bindings with ruby3.1 enabled, the build
Source: ruby-mysql2
Version: 0.5.3-3.1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-r...@lists.debian.org
Usertags: ruby3.1
Hi,
We are about to start the ruby3.1 transition in unstable. While trying to
rebuild ruby-mysql2 with ruby3.1 enabled, the build failed.
On Tue, Jul 05, 2022 at 06:44:15PM +0200, Timo Röhling wrote:
> On Mon, 23 May 2022 01:58:56 +0200 Andreas Beckmann wrote:
> > Package: faker,ruby-faker
> > Severity: serious
> > Tags: sid bookworm
> > User: trei...@debian.org
> > Usertags: edos-file-overwrite
> > Control: found -1 0.9.3-0.1
> >
Control: tag -1 pending
Hello,
Bug #1005472 in typeshed 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:
Control: severity -1 important
Hi,
On Mon, Aug 23, 2021 at 03:00:16PM +0300, Adrian Bunk wrote:
> Source: passenger
> Severity: serious
>
> passenger-5.0.30/src/cxx_supportlib/vendor-copy:
> adhoc_lve.h libcurl libuv nghttp2 utf8 utf8.h
>
>
Source: ruby-bootsnap
Version: 1.9.3-1
Severity: serious
Tags: upstream ftbfs
Justification: fails to build from source
Forwarded: https://github.com/Shopify/bootsnap/issues/415
The ruby-bootsnap test suite hangs forever on ppc64el. This has been
reported upstream at the link above, and happens
tag 1010061 pending
thanks
Date: Sat Apr 23 10:08:16 2022 -0300
Author: Antonio Terceiro
Commit ID: 6733ab9603773281016812c34604aa3358fbdc34
Commit URL:
https://git.sigxcpu.org/cgit/git-buildpackage//commit/?id=6733ab9603773281016812c34604aa3358fbdc34
Patch URL:
https://git.sigxcpu.org/cgit
: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8),
LANGUAGE=pt_BR:pt:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
From d77682bf92b2c486ef1a35e5af13411129583fb1 Mon Sep 17 00:00:00 2001
From: Antonio Terceiro
Date: Sat, 23 Apr 2022 09
On Tue, Apr 12, 2022 at 02:33:50PM -0300, Antonio Terceiro wrote:
> Package: podman
> Version: 4.0.1+ds1-3
> Severity: serious
> Justification: fails to install
>
> I wanted to try podman 4.0 from experimental, but I can't install it:
> This is on a testing machine, with unst
Control: tag -1 pending
Hello,
Bug #1009374 in libpod 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:
Package: podman
Version: 4.0.1+ds1-3
Severity: serious
Justification: fails to install
I wanted to try podman 4.0 from experimental, but I can't install it:
This is on a testing machine, with unstable and experimental available,
but with testing at a higher priority:
On Fri, 11 Mar 2022 19:17:43 +0100 Paul Gevers wrote:
> severity 994456 serious
> tags 994456 ftbfs
> thanks
>
> Now also causing FTBFS during the ruby2.7 removal transition.
Testing this locally, the tests fail randomly aproximately 10% of the
times like this:
Control: tag -1 pending
Hello,
Bug #1006352 in bsfilter 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:
On Thu, Feb 24, 2022 at 10:51:16AM +0900, YABUKI Yukiharu wrote:
> Package: bsfilter
> Version: 1:1.0.19-2.1
> Severity: grave
> Justification: renders package unusable
>
> Dear Maintainer,
>
> Due to ruby transition, ruby could not load sdbm module.
>
> I use bsfilter which classifies spam
lt;8<-
commit 051a42d95d25087e32f225e0ed4c264ccd4d4923
Author: Antonio Terceiro
Date: Sun Feb 27 09:20:04 2022 -0300
Update diaspora to 0.7.16.0 for compatibility with ruby3.0+
diff --git a/debian/changelog b/debian/changelog
index 06a7254..f652f44 100644
--- a
On Sun, Feb 20, 2022 at 03:26:42PM -0300, Antonio Terceiro wrote:
> Control: tag -1 + patch
>
> On Sat, 19 Feb 2022 14:19:46 +0100 Paul Gevers wrote:
> > Source: uwsgi
> > Version: 2.0.20-2
> > Severity: serious
> > Tags: ftbfs
> > Justification:
-lang-1.12.2.dfsg/debian/changelog 2021-10-24 04:18:35.0 -0300
+++ elixir-lang-1.12.2.dfsg/debian/changelog 2022-02-24 08:47:39.0 -0300
@@ -1,3 +1,10 @@
+elixir-lang (1.12.2.dfsg-2.2) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Mark autopkgtest as flaky (see #997801)
+
+
1 - 100 of 750 matches
Mail list logo
