Bug#950883: ITP: ruby-thwait -- watches for termination of multiple threads
Package: wnpp Owner: "Balasankar \"Balu\" C" Severity: wishlist Usertags: ruby2.7-transition * Package name: ruby-thwait Version : 0.1.0 Upstream Author : Keiju ISHITSUKA * URL : https://github.com/ruby/thwait * License : BSD-2-Clause Programming Lang: Ruby Description : watches for termination of multiple threads Provides thwait, which was split off from Ruby core in Ruby 2.7. Required for making ruby-innertube support Ruby 2.7
Bug#950869: Subject: ITP: ruby-e2mmap -- define custom exceptions with specific messages
Package: wnpp Severity: wishlist Owner: "Balasankar \"Balu\" C" * Package name: ruby-e2mmap Version : 0.0.1 Upstream Author : Keiju ISHITSUKA * URL : https://github.com/ruby/e2mmap * License : BSD-2-Clause Programming Lang: Ruby Description : define custom exceptions with specific messages Was split off from Ruby core in Ruby 2.7 - https://www.ruby-lang.org/en/news/2019/12/25/ruby-2-7-0-released/ This gem is required to package `thwait` gem, which in turn is required to add Ruby 2.7 support to existing ruby-innertube package. signature.asc Description: OpenPGP digital signature
Bug#950849: ITP: ruby-sync -- two-phase lock with a counter
Package: wnpp Owner: "Balasankar \"Balu\" C" Severity: wishlist * Package name: ruby-sync Version : 0.5.0 Upstream Author : Keiju ISHITSUKA * URL : https://github.com/ruby/sync/ * License : BSD-2-Clause Programming Lang: Ruby Description : two-phase lock with a counter This package provides they sync gem, which is essentially a module that provides a two-phase lock with a counter. This was part of Ruby core, but was split out in Ruby 2.7 - https://www.ruby-lang.org/en/news/2019/12/25/ruby-2-7-0-released/ This is needed to add Ruby 2.7 support to ruby-tins. signature.asc Description: OpenPGP digital signature
Bug#943259: [PATCH 0/1] Re: vim-autopep8: Python2 removal in sid/bullseye
Hi Nicholas On 30/11/19 10:17 AM, Nicholas D Steeves wrote: > Hi Balasankar, > > I'm not sure if you noticed this bug earlier this year, but it's RC > now, so I took the liberty to fix it, because the autopep8 fix it > blocks affects one of my packages. 'hope that's ok with you, since > the package used to be collab-maint and hasn't been updated in many > years. If you don't want me to NMU it, please let me know at your > earliest convenience :-) > I am so sorry for not noticing the bug, and apparently your mail. Seems my subscription setting for this package was incorrect and the mail got labeled/moved to the wrong directory. I have uploaded a new revision fixing all the Python 2 dependencies. Regards Balu signature.asc Description: OpenPGP digital signature
Bug#943086: (no subject)
Update: The upstream is releasing a new patch version to support Python 3 in the build process. Will update the package and close this bug once that is out.
Bug#931896: grub-efi-amd64: symbol `grub_file_filters` not found
Hi, I was also hit by this bug after upgrading yesterday (it has been few weeks since I updated the machine). Just like others, I also had to downgrade the following packages to 2.02 to get it working. 1. grub-common 2. grub2-common 3. grub-efi-amd64-bin 4. grub-efi-amd64 5. grub-pc-bin > This means that your GRUB installation is misconfigured: in > particular, it means that the GRUB core image that your firmware is > configured to boot from is not the one that grub-install is writing to > on upgrade, which means that the core image and the loadable modules > in /boot/grub/ are incompatible and you get this failure mode. AFAIK, my installation of Debian was pretty straightforward and I haven't tinkered with grub after installation at all. If anything caused GRUB misconfiguration, it is probably Debian Installer. > This is not a bug in the new version of GRUB; any upgrade at all that > changed the interface between the core image and modules (which is not > a stable interface) would have exposed this. Rather, it's a bug in > the way your system was installed or possibly in the way it has been > maintained since then Provided that multiple people are facing the same problem, maybe a bit more investigation would be helpful to know more about why this suddenly popped up, what is common with all these users' configuration, and whether it is a legit issue, etc.? Regards Balu
Bug#918639: hyphen-te: please provide symlinks for generic language hyphenation dictionaries
Hi, > In this case, i am asking for the same kind of symlink arrangement for > the following hyphenation dictionaries in the parenthesized binary > packages: > > te → te_IN (hyphen-te) Sorry for delayed response. I am fine with doing this, but I have a question for you. This package (hyphen-te) comes from the source package hyphen-indic, which builds the following binary packages * hyphen-as * hyphen-bn * hyphen-gu * hyphen-hi * hyphen-kn * hyphen-ml * hyphen-mr * hyphen-or * hyphen-pa * hyphen-ta * hyphen-te Do you wish this change to happen only for hyphen-te, or all those binary packages? Regards Balu
Bug#869919: [DRE-maint] Bug#869919: remove ruby-berkshelf-api-client?
Hi, On Thu, 27 Jul 2017 20:55:15 +0300 Hleb Valoshka <375...@gmail.com> wrote: > On 7/27/17, Pirate Praveen wrote: > > > Upstream readme has this "This gem has been fully deprecated, and its > > API has been moved inside the berkshelf gem itself." > > > > I bumped into this package when trying to update ruby-faraday as its > > gemspec declares a tight dependency on faraday ~> 0.9.1 > > > > Can we remove this package from debian? > > Yes we can but a bit later when I prepare an updated berkshelf, I'm > working on its dependencies now. > > Any update on this? Was the berkshelf update done? Can we remove this package? Regards Balu signature.asc Description: OpenPGP digital signature
