Bug#1055999: marked as pending in python-asyncssh
Control: tag -1 pending Hello, Bug #1055999 in python-asyncssh 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: https://salsa.debian.org/python-team/packages/python-asyncssh/-/commit/6423198026dcf1bef675a3590be029dc3f9778d1 Patches for CVE-2023-46446 and CVE-2023-46445 * d/p/0003-Fix-rogue-session-attack-and-rogue-extension-negotia.patch: Added. - Fixes rogue session attack CVE-2023-46446 (closes: #1055999) and the rogue extension negotiation attack CVE-2023-46445 (closes: #1056000). (this message was generated automatically) -- Greetings https://bugs.debian.org/1055999
Bug#1055672: Depends on python3-typed-ast, which has been removed from testing and unstable due to #1051802
Package: prospector Version: 1.1.7-4 Severity: serious X-Debbugs-Cc: daniel.leid...@ext.secunet.com The package declares a dependency on python3-typed-ast. However, due to #1051802, this package is no longer available. It is my understanding that python3-typed-ast has been superseeded by the "ast" standard library in Python 3.8+. Thus, prospector is currently uninstallable. Regards, Daniel -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 6.5.0-3-amd64 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages prospector depends on: ii dodgy 0.1.9-5 ii libjs-sphinxdoc7.2.6-2 ii pylint 2.17.4-1 ii python33.11.4-5+b1 ii python3-astroid2.15.6-1 ii python3-mccabe 0.7.0-1 ii python3-mypy 1.6.1-1 ii python3-pep8-naming0.10.0-2 ii python3-pycodestyle2.10.0-1 ii python3-pydocstyle 6.3.0-1 ii python3-pyflakes 2.5.0-1 ii python3-pylint-celery 0.3-7 ii python3-pylint-django 2.0.13-3 ii python3-pylint-flask 0.5-5 ii python3-pylint-plugin-utils0.7-3 ii python3-pyroma 2.6b2-1 ii python3-requirements-detector 0.6-4 ii python3-setoptconf 0.3.0-2 ii python3-typed-ast 1.5.4-1+b1 ii python3-yaml 6.0.1-1 Versions of packages prospector recommends: ii vulture 2.7-1 prospector suggests no packages. -- no debconf information
Bug#1053558: Impossible to add VPN connection or change settings of existing profiles
Package: network-manager-openconnect-gnome Version: 1.2.10-1 Severity: serious -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hello, I have existing network-manager profiles for openconnect (anyconnect) and I try to create new ones. If I want to create a new profile, the dialog appears, but after adding the necessary informtion and hitting the "Apply" button, nothing has been saved. There is no new connection shown in the VPN settings page. I also tried to add a route to an existing connection profile. While it seems to save the setting for automatically/manually setting routes, the route itself is also not saved. Right now, I have to write the profiles by hand. I don't see any errors in the logs (except for "openconnect[...]: Failed to open /dev/vhost-net", which I think is irrelevant). There might be some relevance in these reports, though: https://gitlab.gnome.org/GNOME/NetworkManager-openconnect/-/issues/106 https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/2499 Regards, Daniel - -- System Information: Debian Release: trixie/sid APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'oldstable-updates'), (500, 'oldstable-security'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (500, 'oldstable') Architecture: amd64 (x86_64) Kernel: Linux 6.5.0-1-amd64 (SMP w/20 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages network-manager-openconnect-gnome depends on: ii libc62.37-12 ii libgcr-base-3-1 3.41.1-3 ii libgcr-ui-3-13.41.1-3 ii libglib2.0-0 2.78.0-2 ii libgtk-3-0 3.24.38-5 ii libgtk-4-1 4.12.2+ds-1 ii libnm0 1.44.0-1 ii libnma-gtk4-01.10.6-1 ii libnma0 1.10.6-1 ii libopenconnect5 9.12-1 ii libsecret-1-00.21.1-1 ii libsoup2.4-1 2.74.3-1 ii libwebkit2gtk-4.0-37 2.42.1-1 ii libxml2 2.9.14+dfsg-1.3 ii network-manager-openconnect 1.2.10-1 network-manager-openconnect-gnome recommends no packages. network-manager-openconnect-gnome suggests no packages. - -- no debconf information -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEvu1N7VVEpMA+KD3HS80FZ8KW0F0FAmUf0vUACgkQS80FZ8KW 0F28BhAAyfR7dmdgjUZJQwiy0lzYZ3adDS6qqaE1yKh/20U0JamyOCMIaOx4a/gq +EaRWLsQhqUEAgauTZovLrwMsqC3Xb7yKGNLwqYH8+kJqErmj2JjpjbRzJVgZLat zuWl9yey1GlWYTbhSmNTBv6Vm+YbebSfAq6jblJZJuMwkBWG6JMa1RqeP4eXoS8Q t/dcNIE0WW8rz78oJy+qYVGsRQBESiT+7/XRfPGjJIDbWqWysg3oeSMQmDlauiT3 09hQTF+m5vAMaKCE7Iu4SBlA717FmLS1iFB31BJ35gE7k4m+GF8D7uUQ1LQEaGHR cSnGQMkumXp9Usa1QICgMGPmSF2GoFIzvIVV9Z35le2nPHuGKCEpbshrCV/6eBWr j5wTc0aQ59w2ZQGYDtYc5RBfFLHoj/UVr7bwx1zspGNLTAZt3sYLBy9VfBMs27qf 6AQLEyLT3icgIwLIGT7tX+2ubusstgljTlnCWjDE+QDOzNm0kdO/I9sPfldsdPkh kQk+YvZdmule00DcP1jV2ljwOSuATkdZ6Ky+YmYAK+SajSaPmjNd29W2jWK7oNjM QBVh9O/WP0Gnaot39Nr2oSaDy+98mKYy8ZOrxPmXWKNqP3O2njjhMdJI/T/HlGNL hzHuj0GigyJ1FvI0kEmEYdnShkT4/MXLNcYZGdms0AST/2GiMKI= =EkRK -END PGP SIGNATURE-
Bug#1029588: bts: Changes in libio-socket-ssl-perl 2.078 make bts fail to send mail to mail-server via SSL/TLS - hostname verification failed
Hi, Am Mittwoch, dem 29.03.2023 um 18:42 +0200 schrieb Dominique Dumont: > > Turns out that Perl module Net::SMTP supports SSL since 2014 [1], but > bts still use Net::SMTPS which is an old wrapper around Net::SMTP. > > I've patched bts to use Net::SMTP instead of Net::STMPS and I can > connect to Daniel's server: I'm really sorry for not getting back earlier. I was just too busy. I'll test the updated package asap. Thank you so much for working on this. Regards, Daniel
Bug#1031441: Potential RM candidate ?
Am Mittwoch, dem 15.03.2023 um 21:19 +0530 schrieb Pirate Praveen: > On Mon, 13 Mar 2023 23:17:02 +0530 Mohd Bilal > wrote: > > Hello, > > > > The upstream[1] for ruby-github-api has been inactive for over 2 years > > now and this is affecting other packages like ruby-oauth2[2] and > > ruby-faraday[3] from migrating. > > > > $ reverse-depends -b ruby-github-api > > Reverse-Build-Depends > > * ruby-jeweler > > > > $ reverse-depends -b ruby-jeweler > > No reverse dependencies found > > > > So should we remove these 2 packages ? or as a workaround we could relax > > the versions in Gemfile to actually fix this bug since the Debian source > > doesn't ship the upstream test suite. > > I think we can remove these two packages. I agree. Without migrating github-api to oauth2, IMHO/AFAIR it is also dysfunctional right now. JFTR: The upstream author is still very much active on github, just not working on that gem, it seems. Regards, Daniel
Bug#1032221: cryptsetup: libgcc_s.so.1 must be installed for pthread_exit to work
Booting an older kernel/initrd and then downgrading libargon2-1 to the version in Testing and updating the initrd resolves the situation for now. Thanks to Kai and Guilhem. Regards, Daniel signature.asc Description: This is a digitally signed message part
Bug#1031548: FTBFS with ruby-jekyll-github-metadata 2.15.0
Am Sonntag, dem 26.02.2023 um 16:57 +0200 schrieb Adrian Bunk: > On Sun, Feb 26, 2023 at 03:47:49PM +0100, Daniel Leidert wrote: > > Am Samstag, dem 25.02.2023 um 16:15 +0200 schrieb Adrian Bunk: > > > > [..] > > > FYI: > > > > > > The package in bookworm builds with jekyll-github-metadata > > > 2.15.0: > > > https://tests.reproducible-builds.org/debian/rb-pkg/bookworm/amd64/ruby-jekyll-remote-theme.html > > > (the buildinfo link has the complete package list) > > > > That is due to this environments not running the failing test. The > > test-file checks if there is an internet connection and adds or > > removes > > tests depending on the outcome). The test in question is one that > > requires an internet connection. > > ... > > Accessing the internet during the build is an RC bug. It would be pretty stupid to generally disable tests for a *remote theme* plugin (or any other package) that by defition relies on the internet. This would disable the majority of tests here. We (as in "the Ruby team") instead handle the tests if there is no internet, and whenever possible, run them via autopkgtest (needs-internet restriction) at least. IMHO this is a valid approach and in this case spotted a regression. To my understanding, builds must not fail due to access attempts and the build itself must not rely on downloaded resources. However, this is the test stage, not the build stage. But if you feel that strongly about that, please show me the exact ruling. It won't change the fact though, that this package will fail autopkgtest anyway due to a regression. Daniel
Bug#1031548: FTBFS with ruby-jekyll-github-metadata 2.15.0
Am Samstag, dem 25.02.2023 um 16:15 +0200 schrieb Adrian Bunk: [..] > FYI: > > The package in bookworm builds with jekyll-github-metadata 2.15.0: > https://tests.reproducible-builds.org/debian/rb-pkg/bookworm/amd64/ruby-jekyll-remote-theme.html > (the buildinfo link has the complete package list) That is due to this environments not running the failing test. The test-file checks if there is an internet connection and adds or removes tests depending on the outcome). The test in question is one that requires an internet connection. The package currently doesn't build in a Bookworm nor a Sid chroot if the test in question is running. I can also reproduce the issue in a chrooot with a Ruby-only environment. It has already been forwarded to upstream, and I might simply revert the commit in jekyll-github- metadata 2.15.0 that is causing this regression, or disable this one test for now. Regards, Daniel signature.asc Description: This is a digitally signed message part
Bug#1031548: FTBFS with ruby-jekyll-github-metadata 2.15.0
Source: ruby-jekyll-remote-theme Version: 0.4.3-3 Severity: serious Forwarded: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 The package fails to build right now with jekyll-github-metadata 2.15.0. The culprit seems to be https://github.com/jekyll/github-metadata/commit/a771d0d7457a7bff42b129ce0bed70c74514a506 The issue has been forwarded to https://github.com/benbalter/jekyll-remote-theme/issues/98 Regards, Daniel - -- System Information: Debian Release: bookworm/sid APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'unstable'), (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-4-amd64 (SMP w/20 CPU threads; PREEMPT) Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEvu1N7VVEpMA+KD3HS80FZ8KW0F0FAmPwtkgACgkQS80FZ8KW 0F2IUg//R+DwQrb/S78zLPMtd3eL/6Xl7rF0lrubOnakzRhWj0zykVxzQq1iFgX0 6BrTARWOK2XDTZOTWB4+4FhPuhZd1SPiyC6XDg/PSBCZb+blyyhG/zY7X7p9faPm GbWSq6QIo470HEVwC4E5crDdIWEG4ApLocEX2A7+GbJeb0tbXGxI0A6HrkxnILJr 5aqds/+5D842QU0Tro+otAeMvM+jPffk6vY8tgRDzxGf8X8HU4oBYQeoPeoczrc9 fr4M6yrGKZ3gPleLHijktUsza8yUFaQKZwTalbesQfxfAdwKdLKS05Uv+wQPz3w8 79Z09ZLK4b1XqU4njQYPRWrr8WOFGqzkWaF0g2qGlwdZXQv3bcWhug6PGoP+A2/M ehYGjry1kldPzXBhRZKFAJsk90zcQbmmqlZ6uiwMa8gtoQhX5JEMebPJ+iFk+PSt U3aKQSXdsp2ey6jAwjkuOf+OWfTB+YVVvzwKs6hecdM7DkSye3Qh9Dw4GyYg7lh+ KxyKJf4NSdmkaOIBYdOBwtYdIId4krg+um5nJSfE9D8xOafvGbkvsialfz2WBOuv +3CQQbuVcYYOrY3NM9gRT5cvem+kals67n9gITsr87QXH10s3tbijTvpl2vf5fZk bid9XIIpQMIOfo1QryLqbRCj4r/Y083p9YSULQvjyN40OIxTaGc= =woiX -END PGP SIGNATURE-
Bug#1030966: marked as pending in ruby-jekyll-remote-theme
Control: tag -1 pending Hello, Bug #1030966 in ruby-jekyll-remote-theme 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: https://salsa.debian.org/ruby-team/ruby-jekyll-remote-theme/-/commit/bf744b6d951229f6ba0c1455454345cf59a6a01d Enable tests accessing the internet only if internet is available * d/ruby-tests.rake: Revert a debugging commit that enabled tests by default that access the internet (closes: #1030966). (this message was generated automatically) -- Greetings https://bugs.debian.org/1030966
Bug#1031441: Relax oauth2 dependency
I just rebuilt ruby-github-api by relaxing the dependency on oauth2. I pulled the test cases from github to check if anything happens. It built just fine. 6 tests failed, but none related to OAuth2 (seems some keywords/options mismatch). I think we could fix this by relaxing the dep on oauth2 for now. There is an upstream report asking for supporting oauth2 2.x at https://github.com/piotrmurach/github/issues/386. Regards, Daniel
Bug#1031325: e2fsprogs 1.47.0 introduces a breaking change into Bookworm, breaking grub and making installations of Ubuntu and Debian releases via debootstrap impossible
Am Donnerstag, dem 16.02.2023 um 20:10 +0200 schrieb Adrian Bunk: [..] > I am currently spending time trying to summarize the situation and open > questions, and I am a bit underwhelmed by the inaccuracies and lack of > technical detail in your emails. Well, I didn't have weeks to prepare. I had <24 hours and gave you already enough information so you did not have to start from scratch. I will summarize my points at the bottom. > The instructions you cite in [1] are for installing bullseye from > non-Debian systems. That is simply not true. Those are general instructions, they are not limited to non-Debian systems. Most server providers have exctly *one* rescue system from where I can do a clean installation with deboostrap (and that even usually is a Debian). I cannot choose to use one that hasn't an e2fsprogs that has this breaking change enabled. Say for example, grml, used by multiple providers I know as rescue system and based on Debian, picks up Bookworm with e2fsprogs with that change. Now users trying to install anything other than a Debian Bookworm using the deboostrap method will run into the situation that "grub-install" will fail, and it won't even indicate that they will have to tune the just created ext4 filesystem or even change /etc/mke2fs.conf. I spent a few hours until I tracked it down. And the situation right now is, that I can simply install any system with the deboostrap method. I'm not aware that there are any breakages or incompatibilities. > What bookworm ships does not matter much there, > these instructions will be wrong as soon as some *other* distribution > like Fedora changes the default. Fedora isn't used much as a rescue system, don't you think? Have you ever encountered that? I do custom server setups with deboostrap for almost two decades now. I haven't seen any distribution so far that changed the created filesystem to be incomatible with grub-install from the systems that might be installed. Most of the rescue systems were Debian based, JFTR. > I am wondering how exactly your often repeated "there is no grub > upstream release with support for it" would be relevant in practice. > Whether it's 2.06-8 or 2.07-1 in bookworm shouldn't make a difference. You completely miss the point here. It would lead to exactly the same situation if 2.07 would be the *first* to support it and could be shipped with Bookworm as long as e2fsprogs makes this breaking change now. But it makes a huge difference if 2.07 with a fix is released in around the same time as Bookworm and can spread until Trixie is prepared and the breaking change is postponed to Trixie. Ubuntu 24 would have picked up that fix by then. 22 and maybe even 20 would probably have picked it up either. Even bullseye could get a patch to deal with that. The breakage would have less impact than it has now, while nothing is prepared. And it is completely illusional to say that people should first create a Bullseye chroot to then do a deboostrap setup of a target system from that chroot, as Theodore suggested. Well, I'm more than underwhlemed by suggestions like this. > Sebastian has now created #1031364 for your original vmdb2 problem, > everyone discussing in #1030939 seems to have missed that tools in > bookworm creating images for < bookworm must handle such changes. > That's not different from debootstrap having code to handle > apt-transport-https being required in some older releases. I agree. So don't you think introducing this now is a really bad timing? I checked a search engine to find out what this feature even does. Turns out, there were less than 500 hits. It is a feature available since kernel 4.4 and not widely used nor default. So what is the gain here? I also tried to understand why our users would need to be able to change the UUID of the filesystem. In 20 years with Debian, I haven't encountered a situation where this has been necessary (I didn't even know that one could). My gut feeling is, that this feature is only useful to a handful of people. I haven't heard any explanation so far why this needs to be turned on by default just now. The whole discussion so far has been Theodore argueing why he doesn't care about his actions and why he doesn't have to. If this feature should be turned on, then I still think that doing this for Trixie is the better choice. The tools affected can be fixed to work around the issue. The other distributions can pick up the grub- install fix. And JFTR: The attitude I preceived since I got into the discussion with the simple sentence that fixing grub in Bookworm might not be enough, can be summarized as "I/we don't care". So, sorry, I care, even if my less excellent mails might be underwhelming for you. Daniel
Bug#1031325: e2fsprogs 1.47.0 introduces a breaking change into Bookworm, breaking grub and making installations of Ubuntu and Debian releases via debootstrap impossible
Am Donnerstag, dem 16.02.2023 um 18:37 +0200 schrieb Adrian Bunk: > On Wed, Feb 15, 2023 at 12:05:41AM +0100, Daniel Leidert wrote: > > ... > > Reasons: > > ... > > - - the change makes it impossible to create filesystems with this version > > of > > e2fsprogs and then run a grub-install from a target system that does not > > cope > > with that feature; basically breaking the debootstrap method of installing > > Debian or Ubuntu onto a server (violating #4 of the Debian social > > contract) > > ... > > Instead, turning on this feature should be postponed for the next release > > cycle > > where a proper transition can be done. > > ... > > Daniel, you are contradicting yourself when claiming that a change that > would allegedly violate the Debian social contract could be done in the > next release cycle. Actually, I'm not. I have never said that I reject the introduction of that change. But I reject it in the current situation, and I reject the way it is handled. And if you read the whole report and the discussion I was involved in, then maybe you can understand that I perceive it that both, Steve and Theodore, were very well with the idea of breaking with Bullseye and Ubuntu and other systems, where grub doesn't support that feature, right now and "just like that". And I think this is a violation of #4. I have also written in [1] how I think the transition should be handled (IMO), especially given the fact that grub has no upstream release with a fix yet. [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030939#108 Regards, Daniel
Bug#1031395: tzdata 2022g-3 removes /etc/timezone while other packages depend on it, breaking these packages
Package: tzdata Version: 2022g-3 Severity: critical -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi, in version 2022g-3, the /etc/timezone file has been removed and gets purged from user's computers. This makes unrelated software break that relies on this file. Examples are samizdat and ruby-et-orbi. But codesearch.d.o shows more code-snippets that rely on the existence of that file. There hasn't been any announcement, any transition, nor any mass-bug filing, leaving multiple packages broken at this stage. I reported that issue to the release team as #1031376 and have been asked to open a bug report against tzdata. Regards, Daniel - -- System Information: Debian Release: bookworm/sid APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'unstable'), (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-4-amd64 (SMP w/20 CPU threads; PREEMPT) Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages tzdata depends on: ii debconf [debconf-2.0] 1.5.82 tzdata recommends no packages. tzdata suggests no packages. - -- debconf information excluded -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEvu1N7VVEpMA+KD3HS80FZ8KW0F0FAmPuJ/gACgkQS80FZ8KW 0F2CPQ/+M+A8ok4famSAdTA6Tpjw+ydaYGO2E4+NoQy/diq8KKhFMiOOdduiQji4 6J8no1J7K00eEPgqBko3lQXDJByDuRKHWXD3NFmQJme/pL9Wf4yc7+Zx4QhaBI96 UuUV4M8khv89bA9Bb6TWGUD0OkEOgpze7HAZAQqc8gnaGA2yRkh3JC9DmHe9boQJ ywODuoFmlPIgyv+Jx8KlXgGdZWWoJpQtm8ol21WeYRtAWxPL+b/FbC1rTrSSEgka wmw+pa4VbKC8sQIyGQPbJJk0q3PTIqKu1ia59KGKSrCox4cfAvV3EccgyH1xYliI BRrlSEG1mau1O8jz4fq7oqMVs6W/KMRuj+pSI4n5DEFU9tEJ2G3trysusnS531tj L++pD/aWISx76rpVzizVQjw1J63pr9sK8sh9/s/jz4s3Ddwiij/HVMaA6t7X+2DU I3O8jgUq4N6taWw7NcBLDSyFRESqc0BcZYwfsvD7DD0UHSUeZmE5PnetHVWLwqeg O/ljWDNuIiB61DfVWJr5nfhKXOZYFWXJEOOwDQ5zxWviHlahEGsu3wOQLGW7OA9E bKUO2IpAOMHX0Oxx752t9eParFqs2yfAX338PGC73w7dCIB5bVowD9SHRCJi6FRX 8HhD5hgq8SsuJEej0eBS63QqN3uqxZKbZsoQgA5aS3eMffxEPRM= =i0wy -END PGP SIGNATURE-
Bug#1030846: Bug#1030939: e2fsprogs: generates filesystems that grub-install doesn't recognize
Am Dienstag, dem 14.02.2023 um 16:53 -0500 schrieb Theodore Ts'o: [snip] Your arrogant and ignorant attitude is frustrating, to say the least. You don't care about the mess you create, for a feature, that probably only a handful of people will ever need (I did a quick search and didn't find anything regarding this feature - so why turn it on by default then?). But yet you have to make it the default and break running toolchains and methods. Talking to you is pointless. You cost me hours of useless work yesterday and today because you ignore the rules we have set out as a project to not frustrate each other. I have reported this to the release team now. Daniel
Bug#1031325: e2fsprogs 1.47.0 introduces a breaking change into Bookworm, breaking grub and making installations of Ubuntu and Debian releases via debootstrap impossible
Package: release.debian.org Severity: serious -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 A week ago, Theodore Ts'o uploaded e2fsprogs 1.47.0 into Debian unstable. This version contains a unannounced change that basically breaks grub2 (and grub-install). This issue has been reported as #1030939 [1] and #1030846 [2]. To "fix" the issue, instead of turning the feature off, a patch to grub2 in Sid has been committed recently. Unfortunately, that only fixes grub in Sid. Grub in Bullseye or any current Ubuntu release *cannot* deal with a filesystem created by this version of e2fsprogs. This basically breaks the debootstrap method of installing a Debian or Ubuntu. If e2fsprogs 1.47.0 is allowed into Testing, we can no longer use the debootstrap method to install a Debian Bullseye (or older) or any Ubuntu release. It requires to manually change the filesystem features before it can be used again. It also makes e.g. vmdb2 in Sid unusable to create images of Bullseye or older Debian releases, or Ubuntu releases. The gain of enabling the metadata_csum_seed feature by default is not noteworthy. It is a feature that hardly anybody needs. I have not seen one use-case nor even relevant search hits. But the loss is heavy. User's can no longer simply follow [3] to install any Debian or Ubuntu system if the filesystem has been created with e2fsprogs 1.47.0. It also breaks software in the midst of the freeze. I hereby ask the release team to step in and either make sure that the metadata_csum_seed feature is not turned on by default in e2fsprogs in Bookworm or that version 1.47.0 is not shipped as part of Bookworm. Reasons: - - this breaks existing tools for no apparant reason - - introducing this breaking change is too late in the release cycle to deal with it properly - - the metadata_csum_seed feature is hardly useful or requested; it can be turned on if necessary; no need to make it the default in Bookworm - - there is no grub upstream release with support for it; only patched grub versions can cope with it - - the change makes it impossible to create filesystems with this version of e2fsprogs and then run a grub-install from a target system that does not cope with that feature; basically breaking the debootstrap method of installing Debian or Ubuntu onto a server (violating #4 of the Debian social contract) - - to cope with the former issues, users will have to know about that incompatibility and ways to deal with it; none of that is prepared; the package maintainer even refuses a NEWS entry - - it breaks vmdb2, only allowing to make images of Debian Bookworm and Sid (if grub is involved) - - pushing this metadata_csum_seed feature violates #4 of the Debian social contract Instead, turning on this feature should be postponed for the next release cycle where a proper transition can be done. [1] https://bugs.debian.org/1030939 [2] https://bugs.debian.org/1030846 [3] https://www.debian.org/releases/stable/amd64/apds03 Daniel Leidert -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEvu1N7VVEpMA+KD3HS80FZ8KW0F0FAmPsE8UACgkQS80FZ8KW 0F0Aug/+Kb6xrQcILq+VYpKk/161UXgQA47ccydz78uT3r1eRBVJIPReULZPdjvk W4PDDOYypScsx4+EahdOVViAMiOyzI0eroivZmDItxY1HR6LpKdeQFPLET6FdbfM pDHezFKXqsulYQWLu5M6yPCtMWGCmAtiH9NeppzUY7+dnBr2yzZGitH4pPSh7MmS 9jxRIKG0xGa3wF+a1yEgHE0nPvqD5a97GlwL5+MTg580k/e1VRpaQaYrTRr3CHyK EJbVOu70K+qXgP837x6B5eyYmihJWiNBMxm9JqF1TrwTKXwk26zpZ2+T1uKVgVKj Y5AlZX8Gypdxq0Q3uFPSlzBhetd2wvrUt9hKEb52fdzw3L4AsY2Ken98sAhqy7Xi PGVdihiUSAT5gslthm3qB3fGQQMIEXI3UdHqSx7ARgZJ6Gkf/zIjk5sKl/xiGe+t jJExPdCR7H8+tPNZhJEhx6BLtLs8tLm+zhOAr3rZVekEn3PJJAHOKPs1KPBWinYr FsVBsWBWzOgKNARu31u/o4s5BFV99M45gZqHLs3Mp5TvJqIxkbwS0FDoCa/TausP vojuW4kDPM7Jjw568W4O8csXBiI/qEcEPXZGPrgGVs3Yo1hV/KkJUOkQ9y/VvRps POx+RwF400ov8zOxGPqETkqDjl/2JQ47OOvogJMi6FDRQk+YE2w= =bKh7 -END PGP SIGNATURE-
Bug#1030846: Bug#1030939: e2fsprogs: generates filesystems that grub-install doesn't recognize
Am Dienstag, dem 14.02.2023 um 12:34 -0500 schrieb Theodore Ts'o: > [..] > In any case, a version of grub that will support the csum_seed feature > will be landing in Bookworm in just a few days. So at that point, > you'll be able to create VM images for Bookworm and Sid that will work > with the e2fsprogs in sid. The current plan of record is that it will > only be at that point that e2fsprogs will be allowed to migrate into > Bookworm. As soon as this version hits testing, you have successfully disabled the last working environment to use vmdb2 to create images of Ubuntu and Debian. As soon as this version hits Testing, one then can no longer build images for either any Ubuntu release nor Debian Bullseye or older. I can then only build images for Bookworm and Sid. Please think about that. You *seriously* break the debootstrap method of installing Debian or Ubuntu. vmdb2 ist just another tool that is broken by now, a tool that I use very often. I explained the impacts of what you are doing often enough now. By now the impact should be clear. And you are still not dealing with the aftermath of your intended action?! You haven't done a proper transition. You haven't given any affected toolchain the necessary time to adopt. You haven't documented how to disable that breaking change when creating filesystems for distributions where grub does not support this (there is not even a NEWS entry). You haven't even announced that breaking change. And yet you are going to break one of our two standard methods of installing Debian or Ubuntu. How is any of what you have been saying so far addressing any of these issues? > [..] > By the way, in the case of the csum_seed feature, it's pretty > straightforward to just run "tune2fs -O ^metadata_csum_seed > /tmp/boot.img". If the UUID has been changed since the file system > was created, you'll have to do this while the file system is > unmounted > and it will take a few seconds, but that's almost certainly not the > case with vmdb2. Well, how do you intend to distribute that information, so people who have to use the deboostrap method to install a Debian or Ubuntu release with a grub not supporting csum_seed (basically all existing releases, except for the upcoming Bookworm) know that? I do not understand why you are pushing 1.47.0 over 1.46.6, which you had uploaded just five days before the former. You haven't even presented a reason yet. Regards, Daniel
Bug#1030846: Bug#1030939: e2fsprogs: generates filesystems that grub-install doesn't recognize
Am Dienstag, dem 14.02.2023 um 14:58 + schrieb Steve McIntyre: > On Tue, Feb 14, 2023 at 12:50:18PM +0100, Daniel Leidert wrote: > > [..] > Breakages happen like this, This breakage is *unnecessary* and it breaks at the momnent *all* debootstrap installations except for doing a bookworm/sid installation themselves. That is just stupid. Get down from your high horse and ackknowledge the problems your behavior causes. > and this has happened before in similar > circumstances. No it has not. You are doing a breakage on purpose during a freeze period while the transition period is over. Do it with a proper transition during the next release cycle. > > [..] > > Whe whole handling is completely wrong here. First, grub should have > > been fixed upstream. And the change in e2fsprogs should have been done > > only after "fixed" grub versions had settled. If we do it the other way > > around, we have to patch grub in affected distributions as well. And > > for Debian that means at least to patch Bullseye and any other release > > we want to be able to install from Bookworm. I even a lot of companies > > using Buster still. > > And I know of folks still working on Stretch and Jessie. How far back > do you want to tie things?? How about staying on topic and explaining, why this transition is necessary and has to be done the wrong way around, instead of picking the fact that older systems still exist? You break almost *all* installation right now. You also broke an Ubuntu 20.04 or 22.04 LTS installation. Are they new enough? [..] > > > > I'm critizicing the way of handling that breaking change and the > > ignorance shown reagarding the impact, not that fact that there is a > > breaking change. And it breaks a lot! This doesn't affect just a few > > minor use cases. It affects the basic way of installing a clean Ubuntu > > or Debian (or derivative) on a remote server using the debootstrap > > method. > > People using these tools need to be aware of the potential issue. What > would happen if you ran debootstrap with a filesystem that the target > distro doesn't know how to mount at all, for example? That is different from introducing a breaking change for which no grub upstream release has a fix yet. So basically the only system able to handle a filesystem created with e2fsprogs 1.47.0 is Sid right now. Can you please ignore your ego and see the problems you are causing? You push a breaking change for no reason at all. What is the gain here compared to the issues you are causing? > > And again: We are in the middle of a freeze here. And e2fsprogs > > pushes > > a breaking change that is not even handled by any existing grub > > upstream release, and is also not properly handled within Debian?! > > Grub upstream is already known to be problematic in terms of release > cycles. That is not enough and it is not a solution for the problem. There is *no* grub version out there supporting this, except for the patched version is Sid. Is this the sign for a working transition? > We now know about this particular issue (thanks Ted!) and > we've fixed it in unstable (and soon testing). Which helps exactly nobody, as it still breaks all other Debian or Ubuntu installation. I cannot belive that you intentionally break one of the standard methods to install Debian or Ubuntu for no reason at all and without a proper transition. Version 1.47.0 of e2fsprogs contains nothing necessary for Bookworm. I'll bring this to the attention of the release team. I'm sick of your ignorance. Do a proper transition and don't start it during a freeze. Daniel
Bug#1030846: Bug#1030939: e2fsprogs: generates filesystems that grub-install doesn't recognize
Am Dienstag, dem 14.02.2023 um 10:45 + schrieb Steve McIntyre: > On Tue, Feb 14, 2023 at 11:34:13AM +0100, Daniel Leidert wrote: > > Am Montag, dem 13.02.2023 um 21:35 -0500 schrieb Theodore Ts'o: > > ... > > > > But a generalized requirement that we be able to use debootstrap and > > > vmdb2 to be able to bootstrap an arbitrarily old distribution doesn't > > > seem to be reasonable. > > > > You are completyl wrong. This breaks a standard way of installing any > > system supported by deboostrap with a grub without a fix to deal with > > this version of e2fsprogs. This isn't just about vmdb2. > > > > What you are saying is ignorant. > > > > If this isn't cared about, then this version of e2fsprogs shouldn't > > make it into Bookworm. We are in the middle of a freeze and this breaks > > toolchains and a standard way (see [1]) of installing Debian. > > Sorry Daniel, but I have to (mostly!) agree with Ted here. If you're > creating an image of an older release using newer tools then you'll > need to be aware that sometimes the newer tools will create things > that don't work there. If there's a bug here, I would strongly argue > that it's in vmdb2. deboostrap (for example) includes some > release-specific knowledge to cope with issues like this. debootstrap does nothing related to grub. So it is a bad example. Again I refer to [1]: If the host system contains the problematic e2fsprogs and the target system doesn't contain a grub with the fix [2], then this breaks installations. This breaks older systems *and* current systems. For example, I neither see the necessary grub patch in both Ubuntu 20.04 and 22.04 either. So they also cannot be installed using the deboostrap method and the toolchain in Sid (and Bookworm if e2fsprogs makes it there). [1] https://www.debian.org/releases/stable/amd64/apds03 [2] Even "our" grub only contains a patch and not an upstream version with support. So how can you even expect the target system to contain a fix and be able to handle the created filesystem?! Whe whole handling is completely wrong here. First, grub should have been fixed upstream. And the change in e2fsprogs should have been done only after "fixed" grub versions had settled. If we do it the other way around, we have to patch grub in affected distributions as well. And for Debian that means at least to patch Bullseye and any other release we want to be able to install from Bookworm. I even a lot of companies using Buster still. > If we don't allow for this kind of change, that wouldn't allow us to > *ever* make breaking changes in some packages, and that's just not > sustainable. I'm critizicing the way of handling that breaking change and the ignorance shown reagarding the impact, not that fact that there is a breaking change. And it breaks a lot! This doesn't affect just a few minor use cases. It affects the basic way of installing a clean Ubuntu or Debian (or derivative) on a remote server using the debootstrap method. And again: We are in the middle of a freeze here. And e2fsprogs pushes a breaking change that is not even handled by any existing grub upstream release, and is also not properly handled within Debian?! Daniel
Bug#1030846: Bug#1030939: e2fsprogs: generates filesystems that grub-install doesn't recognize
Am Montag, dem 13.02.2023 um 21:35 -0500 schrieb Theodore Ts'o: > On Tue, Feb 14, 2023 at 01:01:38AM +0100, Daniel Leidert wrote: > > Hi Steve, > > > > I believe that your fix to grub2 in Sid is not enough to handle > > #1030939/#1030846. > > > > This problem breaks e.g. vmdb2. I can no longer create a Bullseye > > system image with vmdb2 on Sid, because the grub-install step in the > > Bullseye chroot now fails, because the created filesystem (created with > > e2fsprogs on Sid) cannot be recognized by grub. > > I'm confused, why does using vmdb2 on *sid* involve running > grub-install on a *bulleye* chroot? My workstation is running Sid. I want to create an image for Bullseye (in this case using vmdb2, but I could do it manually as well). First, one creates the paritioning and the filesystems for the target system with the tools provided by the host system. This involves running the unfortunate version of e2fsprogs with the breaking change. Then, one installs the base system with deboostrap (also from the host system) into the created partitions/filesystem. Then one (bind-)mounts the virtual filesystems into the target systems, does a chroot into it, and then one finishes the installation inside the chroot, including running grub-install. This is standard and common behavior. I have never ever seen in my whole life someone to use grub2 from Sid to make a grub-install for a Bullseye target. I have not even seen anybody suggest that. Consider another example: Server providers use GRML or Bookworm with e2fsprogs 1.47.0 as their rescue system. Now people are no longer able to create a Bullseye system using the deboostrap method [1]. If the host system uses e2fsprogs 1.47.0 or above and the target system for [1] uses a grub without a fix, then this no longer works. [1] https://www.debian.org/releases/stable/amd64/apds03 > That seems to be extremely ill-advised. I'm sorry? I think you are completely missing the point. > If you are trying to install a bullseye system, why > can't you using vmdb2 on bullseye? Because I am using Sid and because I use features of vmdb2 which are not available in the version in Bullseye. And this feature breaks vmdb2 and similar tools. It also breaks a standard way of installing Debian systems. > And if you are trying to install a sid or bookworm system using vmdb2, > why can't you (or vmdb2) use a sid or bookworm chroot for doing the > grub-install? What are you talking about? You basically break the toolchains and then you suggest to do non-standard stuff to handle this or even avoid doing installations of affected systems?! > > I guess that the fix applied to grub2 in Sid would have to be applied > > to grub2 in Bullseye as well (and basically to any grub2 package in any > > Debian or Ubuntu or Raspbian release supported by debootstrap). > > I can understand why we need to keep things synchronized so that a > debian installer for Bookworm be able to generate a bootable system > using the version of grub and e2fsprogs in Bookworm. > > But a generalized requirement that we be able to use debootstrap and > vmdb2 to be able to bootstrap an arbitrarily old distribution doesn't > seem to be reasonable. You are completyl wrong. This breaks a standard way of installing any system supported by deboostrap with a grub without a fix to deal with this version of e2fsprogs. This isn't just about vmdb2. What you are saying is ignorant. If this isn't cared about, then this version of e2fsprogs shouldn't make it into Bookworm. We are in the middle of a freeze and this breaks toolchains and a standard way (see [1]) of installing Debian. Daniel
Bug#1030846: e2fsprogs: generates filesystems that grub-install doesn't recognize
Hi Steve, I believe that your fix to grub2 in Sid is not enough to handle #1030939/#1030846. This problem breaks e.g. vmdb2. I can no longer create a Bullseye system image with vmdb2 on Sid, because the grub-install step in the Bullseye chroot now fails, because the created filesystem (created with e2fsprogs on Sid) cannot be recognized by grub. I have to downgrade e2fsprogs to the version in Testing to get the build going again. It also means that a Bookworm system can never be used to format and debootstrap a Bullseye or Buster system that requires a grub installation. I guess that the fix applied to grub2 in Sid would have to be applied to grub2 in Bullseye as well (and basically to any grub2 package in any Debian or Ubuntu or Raspbian release supported by debootstrap). This situation is really messy. It breaks basically all my image builds with vmdb2. Regards, Daniel signature.asc Description: This is a digitally signed message part
Bug#1019681: marked as pending in samizdat
Control: tag -1 pending Hello, Bug #1019681 in samizdat 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: https://salsa.debian.org/ruby-team/samizdat/-/commit/fbf5ddcf6f78951a53353880e02463b13e08b519 Fix FTBFS * d/control (Build-Depends, Depend): Depend on ruby-whitewash with Psych fix. * debian/patches/0003-Fix-compatibility-with-Psych-4.patch. Add patch. - Use YAML.unsafe_load() because YAML.load() changed to YAML.safe_load() in Psych 4, leading to a FTBFS with errors like: Psych::DisallowedClass: Tried to load unspecified class XXX (closes: #1019681). * d/patches/series: Add new patch. (this message was generated automatically) -- Greetings https://bugs.debian.org/1019681
Bug#1005625: marked as pending in ruby-gettext-i18n-rails-js
Control: tag -1 pending Hello, Bug #1005625 in ruby-gettext-i18n-rails-js 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: https://salsa.debian.org/ruby-team/ruby-gettext-i18n-rails-js/-/commit/965b8125b594ce2b5af01e712051ccbb5c2787f2 Fix FTBFS * d/clean: Add file and drop override_dh_clean. * d/control (Build-Depends): Bum debhelper to version 13. * d/rules: Work around new rubygems limitation and copy assets for build stage and symlink them afterward (closes: #1005625). (this message was generated automatically) -- Greetings https://bugs.debian.org/1005625
Bug#1026479: marked as pending in ruby-faraday-middleware
Control: tag -1 pending Hello, Bug #1026479 in ruby-faraday-middleware 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: https://salsa.debian.org/ruby-team/ruby-faraday-middleware/-/commit/c67c1a2471b6796fd410a95d224abae7dea3114c Fix build * d/control (Build-Depends): Add ruby-safe-yaml (closes: #1026479). (this message was generated automatically) -- Greetings https://bugs.debian.org/1026479
Bug#1005631: marked as pending in ruby-handlebars-assets
Control: tag -1 pending Hello, Bug #1005631 in ruby-handlebars-assets 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: https://salsa.debian.org/ruby-team/ruby-handlebars-assets/-/commit/4a863d6cb4532d68be3d1548bbfbd58dec6e598c Fix tests with Ruby HAML 6 * debian/patches/0005-Fix-syntax-for-ruby-haml-6.patch: Add patch. - Fix syntax for Ruby HAML 6 (closes: #1005631). (this message was generated automatically) -- Greetings https://bugs.debian.org/1005631
Bug#1011445: marked as pending in ruby-license-finder
Control: tag -1 pending Hello, Bug #1011445 in ruby-license-finder 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: https://salsa.debian.org/ruby-team/ruby-license-finder/-/commit/c8a2a2c0bed2b9f683068eb4c635ddad8891ec96 Conflict with ruby-gitlab-license-finder * d/control: Declare a conflict with ruby-gitlab-license-finder (closes: #1011445). (this message was generated automatically) -- Greetings https://bugs.debian.org/1011445
Bug#1015224: Illegal instruction (SIGILL) on arm64
Package: librocksdb6.11
Version: 6.11.4-3
Followup-For: Bug #1015224
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Attached is a possible debdiff.
- -- System Information:
Debian Release: bookworm/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500,
'stable-security'), (500, 'stable-debug'), (500, 'unstable'), (500, 'testing'),
(500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 5.18.0-4-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages librocksdb6.11 depends on:
ii libbz2-1.01.0.8-5
ii libc6 2.34-4
ii libgcc-s1 12.1.0-8
pn libgflags2.2
ii liblz4-1 1.9.3-2
ii libsnappy1v5 1.1.9-2
ii libstdc++612.1.0-8
ii libzstd1 1.5.2+dfsg-1
ii zlib1g1:1.2.11.dfsg-4.1
librocksdb6.11 recommends no packages.
librocksdb6.11 suggests no packages.
-BEGIN PGP SIGNATURE-
iQIzBAEBCgAdFiEEvu1N7VVEpMA+KD3HS80FZ8KW0F0FAmMDoyQACgkQS80FZ8KW
0F007w//dKCqzbe+82TIHobnj18BEq0ilHiTwkh6vkP7pFEsJJE/fqrOzQfgaAV/
77jGf8sZDDn0tpetdAvIGXuQFRQqjNlahNLCepX40sxfUpLl04wlMhs5PnQw4hX3
+NK6k3KTWR2k+ViAGL6VeAzmVuqe5l7BcWluf6y3tQbTYNCIWy+qmcybshR/Azn3
j0e/xHoJA9PQ3r3+WFsElXw1Cm8mqHSKq5XMld4cMYlq6S9BZxNBlQ5Lzk7lPILA
Q44aTcKCAjAGUW9pRYZCvcRca9LGoIWckWTvmSvEyjodbqJwXgFAp4Z794o2UIp4
MYnYvVGEn/LmHhi0TrPTiFvyH3K3Zs+Du1ZDMZwE+Sdl7DDiPvvXRa5Qo4j/16jw
qMp3MDL4CQc82nNWKHqZ8uh1rGz8EMyAAlkj/DoM21ygrQ04ZhexyrT8bBWXjBcm
1I3bADg97GoxQLA5b8pycgKTKGqM1U/SxnMVzocacbOOaOdeskiCKTtg5PJJM4Zt
9qz90H6tyXbNn9NnofRgfiok70dItamDSKsYWavaAsp3wO4ikoydc3guKIzasTJp
l+BNqUPmnym7fI90r93LFvxlxhTTYnzoJ+98Rkp8WzMRXRUfIaxPF0ls8k6W7ZZP
CCFRNJdm8T5fECoXf0eURwpKyGxtqy2VON7J34FRaFdBieACUqk=
=U1bp
-END PGP SIGNATURE-
diff -Nru rocksdb-6.11.4/debian/changelog rocksdb-6.11.4/debian/changelog
--- rocksdb-6.11.4/debian/changelog 2020-12-10 17:13:16.0 +
+++ rocksdb-6.11.4/debian/changelog 2022-07-18 21:51:17.0 +
@@ -1,3 +1,10 @@
+rocksdb (6.11.4-3.1) bullseye; urgency=medium
+
+ * Non-maintainer upload.
+ * Fix illegal instruction (closes: #1015224).
+
+ -- Daniel Leidert Mon, 18 Jul 2022 21:51:17
+
+
rocksdb (6.11.4-3) unstable; urgency=medium
* Explicitly link shared library with dynamic linking library
diff -Nru rocksdb-6.11.4/debian/patches/fix_illegal_instruction.patch
rocksdb-6.11.4/debian/patches/fix_illegal_instruction.patch
--- rocksdb-6.11.4/debian/patches/fix_illegal_instruction.patch 1970-01-01
00:00:00.0 +
+++ rocksdb-6.11.4/debian/patches/fix_illegal_instruction.patch 2022-07-18
21:48:42.0 +
@@ -0,0 +1,225 @@
+From 29f7bbef995bdf83098963799c66af742e95373f Mon Sep 17 00:00:00 2001
+From: Yuqi Gu
+Date: Tue, 22 Sep 2020 10:39:54 -0700
+Subject: [PATCH] Fix RocksDB SIGILL error on Raspberry PI 4 (#7233)
+MIME-Version: 1.0
+Content-Type: text/plain; charset=UTF-8
+Content-Transfer-Encoding: 8bit
+
+Summary:
+Issue：https://github.com/facebook/rocksdb/issues/7042
+
+No PMULL runtime check will lead to SIGILL on a Raspberry pi 4.
+
+Leverage 'getauxval' to get Hardware-Cap to detect whether target
+platform does support PMULL or not in runtime.
+
+Consider the condition that the target platform does support crc32 but not
support PMULL.
+In this condition, the code should leverage the crc32 instruction
+rather than skip all hardware crc32 instruction.
+
+Pull Request resolved: https://github.com/facebook/rocksdb/pull/7233
+
+Reviewed By: jay-zhuang
+
+Differential Revision: D23790116
+
+fbshipit-source-id: a3ebd821fbd4a38dd2f59064adbb7c3013ee8140
+---
+ util/crc32c.cc | 6 +++
+ util/crc32c_arm64.cc | 111 ++-
+ util/crc32c_arm64.h | 1 +
+ 3 files changed, 74 insertions(+), 44 deletions(-)
+
+Index: rocksdb-6.11.4/util/crc32c.cc
+===
+--- rocksdb-6.11.4.orig/util/crc32c.cc
rocksdb-6.11.4/util/crc32c.cc
+@@ -41,6 +41,10 @@
+
+ #endif
+
++#if defined(__linux__) && defined(HAVE_ARM64_CRC)
++bool pmull_runtime_flag = false;
++#endif
++
+ namespace ROCKSDB_NAMESPACE {
+ namespace crc32c {
+
+@@ -494,6 +498,7 @@ std::string IsFastCrc32Supported() {
+ if (crc32c_runtime_check()) {
+ has_fast_crc = true;
+ arch = "Arm64";
++pmull_runtime_flag = crc32c_pmull_runtime_check();
+ } else {
+ has_fast_crc = false;
+ arch = "Arm64";
+@@ -1224,6 +1229,7 @@ static inline Function Choose_Extend() {
+ return isAltiVec() ? ExtendPPCImpl : ExtendImpl;
+ #elif defined(__linux__) && defined(HAVE_ARM64_CRC)
+ if(crc32c_runtime_check()) {
++pmull_runtime_flag = crc32c_pmull_runtime_check();
+ return ExtendARMImpl;
+ } else {
+ return Ext
Bug#1015224: Illegal instruction (SIGILL) on arm64
Package: librocksdb6.11 Version: 6.11.4-3 Severity: grave Tags: bullseye, patch -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 I got just hit by https://github.com/facebook/rocksdb/pull/7233 on my RPI 400 running Debian Bullseye. I rebuilt the librocksdb6.11 package with the patch from https://github.com/facebook/rocksdb/commit/29f7bbef995bdf83098963799c66af742e95373f and I can confirm that this patch fixes the SIGILL issue. Is there any chance to push that fix into Bullseye? Without it, librocksdb is not working for me on my Raspberry PI. Regards, Daniel - -- System Information: Debian Release: bookworm/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'stable-security'), (500, 'stable-debug'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.18.0-2-amd64 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages librocksdb6.11 depends on: ii libbz2-1.01.0.8-5 ii libc6 2.33-8 ii libgcc-s1 12.1.0-5 pn libgflags2.2 ii liblz4-1 1.9.3-2 ii libsnappy1v5 1.1.9-2 ii libstdc++612.1.0-5 ii libzstd1 1.5.2+dfsg-1 ii zlib1g1:1.2.11.dfsg-4 librocksdb6.11 recommends no packages. librocksdb6.11 suggests no packages. -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEIB9kcJqmmF4VguFXclr8JZgo7DMFAmLUhqkACgkQclr8JZgo 7DPsPRAAtqU9d0WaXdqYIfrjyMNnJkvcCzGTM211mRIq5tFk9PqiyRAWZqjhCwn3 7QNA4uYQbECXgd6Bgc+hP+GDoPlbwPYRe6VeNIzPc87LpAVh2BR2jG2D4tzCtG1/ hHqolpGbDsMmTyr1hSQwfZWwCZJ5uIsIk60Of3O1TD/PM2dFpSqwFb/dwKJ2B/v+ oqqaZDLOxeh87vqEmFmCxubstk9giNWtID9tMXfE8c5ot9naAViNBlHzRyj9L2PC xJ7dPSmS4qqWouZUSOM/PaIYjmK2oFB2OVJ/w1isao0SNkQIePRMg43R8x5TGKI+ x3pUvPyBe5lekq2yVD/wigOSFF2fLh+FhM/5+Noq+c6aEIRAU16pa0iMA5SF/w9C 5l0tapF/T0RYM8zaAfZe95hqCgq4OtUwHry1OEEL/r0ngEPnLkjUwHaOVPr0PGNh ZZhmBrpg23NR17m+4H4OksyGB3D8w8I5X2EiljKBiIXZzOVUO5ATGedZOM2nWXH7 EYCZqhbjVWCYuGZtNBuzlFaeK5bGA0UWTj+LG1LQcaAXIWLnWJQ7vKeXDiDeJ+m/ hposcBS9yR3ndCX0Wp418EvgQVYgnmCABbeH/o2PJ1JgvpFDLajUHeWOhSSU7iGu yAvryTvY/Hc/4uXRr7V0F+YKoBCbNOVKrnS/ypZbxBHSt/p9Yu4= =GH1z -END PGP SIGNATURE-
Bug#1008811: Won't start without python3-dbus (misses dependency)
Package: snapper-gui
Version: 0git.960a94834f-3.1
Severity: serious
snapper-gui doesn't start without python3-dbus:
$ snapper-gui
Traceback (most recent call last):
File "/usr/bin/snapper-gui", line 33, in
sys.exit(load_entry_point('snappergui==0.1', 'gui_scripts',
'snapper-gui')())
File "/usr/bin/snapper-gui", line 25, in importlib_load_entry_point
return next(matches).load()
File "/usr/lib/python3.9/importlib/metadata.py", line 77, in load
module = import_module(match.group('module'))
File "/usr/lib/python3.9/importlib/__init__.py", line 127, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
File "", line 1030, in _gcd_import
File "", line 1007, in _find_and_load
File "", line 972, in _find_and_load_unlocked
File "", line 228, in _call_with_frames_removed
File "", line 1030, in _gcd_import
File "", line 1007, in _find_and_load
File "", line 986, in _find_and_load_unlocked
File "", line 680, in _load_unlocked
File "", line 790, in exec_module
File "", line 228, in _call_with_frames_removed
File "/usr/lib/python3/dist-packages/snappergui/__init__.py", line 1, in
import dbus
ModuleNotFoundError: No module named 'dbus'
It seems this dependency is missing.
Regards, Daniel
-- System Information:
Debian Release: 11.3
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 5.10.0-13-amd64 (SMP w/12 CPU threads)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages snapper-gui depends on:
ii gir1.2-gtksource-3.0 3.24.11-2
ii python3 3.9.2-3
ii snapper 0.8.15-1
snapper-gui recommends no packages.
snapper-gui suggests no packages.
-- no debconf information
Bug#1007248: nodejs trying to overwrite /usr/share/systemtap/tapset/node.stp
reopen 1007248 thanks I just got hit by this bug as well: Entpacken von nodejs (16.13.2+really14.19.1~dfsg-5) über (12.22.9~dfsg-1) ... dpkg: Fehler beim Bearbeiten des Archivs /tmp/apt-dpkg-install-DvPfq0/442- nodejs_16.13.2+really14.19.1~dfsg-5_amd64.deb (--unpack): Versuch, »/usr/share/systemtap/tapset/node.stp« zu überschreiben, welches auch in Paket libnode72:amd64 12.22.9~dfsg-1 ist It seems this issue is not yet fixed or this is a regression. Regards, Daniel -- Regards, Daniel Leidert | https://www.wgdd.de/ GPG-Key RSA4096 / BEED4DED5544A4C03E283DC74BCD0567C296D05D GPG-Key ED25519 / BD3C132D8B3805D1808123AB7ACE00941E338C78 https://www.fiverr.com/dleidert https://www.patreon.com/join/dleidert signature.asc Description: This is a digitally signed message part
Bug#886617: Please package version 2.1
unblock 886617 by 936212 block 936212 by 886617 block 1003405 by 886617 retitle 886617 python-pmw: Please package version 2.1 and include Python 3 support thanks Hi, there is finally a bkchem version ported to python 3 and it has already been packaged. However, it requires the update pf pmw to version 2.1 (https://pypi.org/project/Pmw-py3/). This would close a lot of open bug reports, and maybe even allow the final removal of python2. Should we prepare an NMU? Regards, Daniel -- Regards, Daniel Leidert | https://www.wgdd.de/ GPG-Key RSA4096 / BEED4DED5544A4C03E283DC74BCD0567C296D05D GPG-Key ED25519 / BD3C132D8B3805D1808123AB7ACE00941E338C78 https://www.fiverr.com/dleidert https://www.patreon.com/join/dleidert signature.asc Description: This is a digitally signed message part
Bug#1003405: misses dependency on python3-pmw
Source: bkchem Version: 0.14.0~pre4+git20211228-1 Severity: grave -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 bkchem requires the pmw module. But it ships neither a dependency on python3-pmw, nor has python3-pmw been uploaded to the archive yet. There is a working module though: https://pypi.org/project/Pmw-py3/ Regards, Daniel - -- System Information: Debian Release: bookworm/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'stable-security'), (500, 'stable-debug'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.15.0-2-amd64 (SMP w/8 CPU threads) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEvu1N7VVEpMA+KD3HS80FZ8KW0F0FAmHbFIQACgkQS80FZ8KW 0F2tNA/9Fzmqc73T5VYN11Nt6Le+DG/+XH6JiH6q5oKNiw6NglO3ZI2h47NcfKVn c7R6LwINax/Dzb721IQJAeK6yQpnsMA+twAu0WCKbTsM7R1AgqP5qjE+8CBBwpby zCRo/RhA0nJZO+nbzdCVF/we2+X318oR3j9BA9zjavWCFBwyz6WTySPvRCjm4KPX vzhWJigbak32CF3D2eKFUUlLph/UcuIFLKMJtKrC3jWC/PpJX6hV/rUqRZzLjV3q Zz5jPqidtHovGoq/UGq3bKoxVkuj+dfnsbjT0pLUb2zDn7ct8sGWnBJqyPnU53Cb GD8mN1UWS2cLiiFzuySWns4O/z+bt44RJpakTd7vr1JZMKbzNP9WOE9AwsYMk3Aa 8YEzMwQ7736hINQnXBRdTHAUxR00SxOvzBLrXPeOVo7h99IZdZ7bmPD9A3bcXVoN Ub9hu47LiUIODjyeu5zbmhR1asVA3BMGbE3KYcasFwTlVapRjGscyau1XEUuDGN9 D5wGT+EdHvoB8eGZJ8mDA6TaHz+VlRjFBuyG772oboCiYIYsFmucwPIe6CdR8rfn 2cR/gtvhDvxTdMrC+7AuOMRgSvHwg5yxct6Eh2OS3fVPIoUdgTL3hPHkXp+PCTnG 7m1hq/ciZPMm/7uPFe7puqgImVz5zPB0kNHgNoM3rx57s0gtmIE= =qWAi -END PGP SIGNATURE-
Bug#996520: marked as pending in ruby-varia-model
Control: tag -1 pending Hello, Bug #996520 in ruby-varia-model 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: https://salsa.debian.org/ruby-team/ruby-varia-model/-/commit/f78938f6e176d18d7b5bdf9d4dbbcf349ebe13ed Add patch to deal with FTBFS with Ruby 3.0 * d/patches/0003-Ignore-test-on-Ruby-3.0.patch: Add patch (closes: #996520). - Ignore test relying on JSON.create_id=nil hack on Ruby 3.0. * d/patches/series: Add new patch. (this message was generated automatically) -- Greetings https://bugs.debian.org/996520
Bug#976493: marked as pending in ruby-psych
Control: tag -1 pending Hello, Bug #976493 in ruby-psych 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: https://salsa.debian.org/ruby-team/ruby-psych/-/commit/e71781cff79f3af8d1a673fc5cb015b5e26675ac Re-enable Java extension * d/control (Build-Depends): Re-add jruby and java dependencies. Add libbytelist-java and libjcodings-java. * d/javabuild: Add to build psych.jar with javahelper. * d/rules: Build Java extension without running jruby directly (closes: #976493, #959571). (this message was generated automatically) -- Greetings https://bugs.debian.org/976493
Bug#959571: marked as pending in ruby-psych
Control: tag -1 pending Hello, Bug #959571 in ruby-psych 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: https://salsa.debian.org/ruby-team/ruby-psych/-/commit/e71781cff79f3af8d1a673fc5cb015b5e26675ac Re-enable Java extension * d/control (Build-Depends): Re-add jruby and java dependencies. Add libbytelist-java and libjcodings-java. * d/javabuild: Add to build psych.jar with javahelper. * d/rules: Build Java extension without running jruby directly (closes: #976493, #959571). (this message was generated automatically) -- Greetings https://bugs.debian.org/959571
Bug#997657: NMU
Hi,
I've just uploaded an NMU to fix this issue. Please find attached the debdiff.
Please note that your Git repository is not in sync with the Debian archive. It
is missing version 3.0.0, this NMU applies to.
Regards, Daniel
--
Regards,
Daniel Leidert | https://www.wgdd.de/
GPG-Key RSA4096 / BEED4DED5544A4C03E283DC74BCD0567C296D05D
GPG-Key ED25519 / BD3C132D8B3805D1808123AB7ACE00941E338C78
https://www.fiverr.com/dleidert
https://www.patreon.com/join/dleidert
diff -Nru ruby-prawn-icon-3.0.0/debian/changelog ruby-prawn-icon-3.0.0/debian/changelog
--- ruby-prawn-icon-3.0.0/debian/changelog 2021-10-10 20:37:56.0 +0200
+++ ruby-prawn-icon-3.0.0/debian/changelog 2021-12-07 11:14:30.0 +0100
@@ -1,3 +1,12 @@
+ruby-prawn-icon (3.0.0-1.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Use gem installation layout, so the font files can be found in the
+expected path (closes: #997657).
+ * Enable tests and add ruby-pdf-inspector to build dependencies.
+
+ -- Daniel Leidert Tue, 07 Dec 2021 11:14:30 +0100
+
ruby-prawn-icon (3.0.0-1) unstable; urgency=medium
* New upstream version
diff -Nru ruby-prawn-icon-3.0.0/debian/control ruby-prawn-icon-3.0.0/debian/control
--- ruby-prawn-icon-3.0.0/debian/control 2021-10-10 20:37:56.0 +0200
+++ ruby-prawn-icon-3.0.0/debian/control 2021-12-07 11:14:30.0 +0100
@@ -6,6 +6,7 @@
Build-Depends: debhelper-compat (= 13),
gem2deb,
rake,
+ ruby-pdf-inspector,
ruby-prawn (<< 3.0.0),
ruby-prawn (>= 1.1.0),
ruby-rspec
@@ -20,8 +21,8 @@
Package: ruby-prawn-icon
Architecture: all
XB-Ruby-Versions: ${ruby:Versions}
-Depends: ${ruby:Depends},
- ${misc:Depends}
+Depends: ${misc:Depends},
+ ${ruby:Depends}
Description: Provides icon fonts for PrawnPDF
Prawn::Icon provides various icon fonts including
FontAwesome, PaymentFont and Foundation Icons
diff -Nru ruby-prawn-icon-3.0.0/debian/patches/0003-Remove-bundler-and-simplecov.patch ruby-prawn-icon-3.0.0/debian/patches/0003-Remove-bundler-and-simplecov.patch
--- ruby-prawn-icon-3.0.0/debian/patches/0003-Remove-bundler-and-simplecov.patch 1970-01-01 01:00:00.0 +0100
+++ ruby-prawn-icon-3.0.0/debian/patches/0003-Remove-bundler-and-simplecov.patch 2021-12-07 11:14:30.0 +0100
@@ -0,0 +1,31 @@
+Author: Daniel Leidert
+Date: 2021-12-07
+Subject: Remove bundler and simplecov usage
+
+Forwarded: not-needed
+
+--- a/spec/spec_helper.rb
b/spec/spec_helper.rb
+@@ -5,11 +5,11 @@
+ # This is free software. Please see the LICENSE and COPYING files for details.
+ #
+ #
+-require 'simplecov'
+-SimpleCov.start
++#require 'simplecov'
++#SimpleCov.start
+
+-require "bundler"
+-Bundler.setup
++#require "bundler"
++#Bundler.setup
+
+ require "prawn/icon"
+ require 'pdf/inspector'
+@@ -22,4 +22,4 @@
+ RSpec.configure do |config|
+ config.include PDFHelper
+ config.include ParserHelper
+-end
+\ No newline at end of file
++end
diff -Nru ruby-prawn-icon-3.0.0/debian/patches/series ruby-prawn-icon-3.0.0/debian/patches/series
--- ruby-prawn-icon-3.0.0/debian/patches/series 2021-10-10 20:37:56.0 +0200
+++ ruby-prawn-icon-3.0.0/debian/patches/series 2021-12-07 11:14:30.0 +0100
@@ -1,2 +1,3 @@
0001-Clear-executable-bit-on-data-fonts-pf.patch
-0002-Access-data-files-from-usr-share-ruby-prawn-icon.patch
+#0002-Access-data-files-from-usr-share-ruby-prawn-icon.patch
+0003-Remove-bundler-and-simplecov.patch
diff -Nru ruby-prawn-icon-3.0.0/debian/ruby-prawn-icon.install ruby-prawn-icon-3.0.0/debian/ruby-prawn-icon.install
--- ruby-prawn-icon-3.0.0/debian/ruby-prawn-icon.install 2021-10-10 20:37:56.0 +0200
+++ ruby-prawn-icon-3.0.0/debian/ruby-prawn-icon.install 1970-01-01 01:00:00.0 +0100
@@ -1 +0,0 @@
-data/fonts/[a-z]* /usr/share/ruby-prawn-icon/data/fonts/
diff -Nru ruby-prawn-icon-3.0.0/debian/ruby-tests.rake ruby-prawn-icon-3.0.0/debian/ruby-tests.rake
--- ruby-prawn-icon-3.0.0/debian/ruby-tests.rake 2021-10-10 20:37:56.0 +0200
+++ ruby-prawn-icon-3.0.0/debian/ruby-tests.rake 2021-12-07 11:14:30.0 +0100
@@ -1,4 +1,5 @@
-task default: %w[test]
+require 'gem2deb/rake/spectask'
-task :test do
+Gem2Deb::Rake::RSpecTask.new do |spec|
+ spec.pattern = './spec/**/*_spec.rb'
end
diff -Nru ruby-prawn-icon-3.0.0/debian/rules ruby-prawn-icon-3.0.0/debian/rules
--- ruby-prawn-icon-3.0.0/debian/rules 2021-10-10 20:37:56.0 +0200
+++ ruby-prawn-icon-3.0.0/debian/rules 2021-12-07 11:09:32.0 +0100
@@ -5,5 +5,7 @@
# Uncomment this to turn on verbose mode.
export DH_VERBOSE=1
+export DH_RUBY = --gem-install
+
%:
dh $@ --buildsystem=ruby --with ruby
signature.asc
Description: This is a digitally signed message part
Bug#997657: Problem is in ruby-prawn-icon
Hi, the problem is actually in ruby-prawn-icon in the files /usr/lib/ruby/vendor_ruby/prawn/icon/font_data.rb and /usr/lib/ruby/vendor_ruby/prawn/icon/configuration.rb. In the first the path to the fonts relies on Icon.configuration.font_directory which is defined in the second and leads to the non-existent directory /usr/lib/ruby/data/fonts, whereas the fonts are actually in /usr/share/ruby-prawn-icon/data/fonts/. The quick fix might be to change to the gem installation layout. Otherwise the font_directory default must be adjusted. Reassigning to ruby-prawn-icon. Regards, Daniel -- Regards, Daniel Leidert | https://www.wgdd.de/ GPG-Key RSA4096 / BEED4DED5544A4C03E283DC74BCD0567C296D05D GPG-Key ED25519 / BD3C132D8B3805D1808123AB7ACE00941E338C78 https://www.fiverr.com/dleidert https://www.patreon.com/join/dleidert signature.asc Description: This is a digitally signed message part
Bug#998509: marked as pending in ruby-rspec-puppet
Control: tag -1 pending Hello, Bug #998509 in ruby-rspec-puppet 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: https://salsa.debian.org/ruby-team/ruby-rspec-puppet/-/commit/81b88ac3fe3a6232dfdfcd6c7ac59703dd045580 Add patch to fix Ruby 3.0 compatbility * d/patches/Add-Ruby-3.0-support.patch: Add patch. - Fix keyword argument issue (closes: #998509). * d/patches/series: Add new patch. (this message was generated automatically) -- Greetings https://bugs.debian.org/998509
Bug#1001129: Ruby 3.0: puppet/util.rb:469:in `uri_encode': undefined method `escape' for URI:Module (NoMethodError)
Package: puppet Version: 5.5.22-2 Severity: serious -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 The version is not ruby 3.0 compatible: ruby3.0 -e "require 'puppet'" /usr/lib/ruby/vendor_ruby/puppet/util.rb:469:in `uri_encode': undefined method `escape' for URI:Module (NoMethodError) from /usr/lib/ruby/vendor_ruby/puppet/util.rb:337:in `path_to_uri' from /usr/lib/ruby/vendor_ruby/puppet/pops/model/ast.rb:4863:in `register_pcore_types' from /usr/lib/ruby/vendor_ruby/puppet/pops.rb:119:in `' from /usr/lib/ruby/vendor_ruby/puppet/pops.rb:1:in `' from :85:in `require' from :85:in `require' from /usr/lib/ruby/vendor_ruby/puppet/parser/compiler.rb:8:in `' from :85:in `require' from :85:in `require' from /usr/lib/ruby/vendor_ruby/puppet/parser.rb:6:in `' from :85:in `require' from :85:in `require' from /usr/lib/ruby/vendor_ruby/puppet.rb:302:in `' from :85:in `require' from :85:in `require' from -e:1:in `' I'm intending to do a quick NMU to fix this. Regards, Daniel - -- System Information: Debian Release: bookworm/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'stable-security'), (500, 'stable-debug'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.15.0-2-amd64 (SMP w/8 CPU threads) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages puppet depends on: ii adduser 3.118 ii facter 3.14.12-1.1 ii hiera3.2.0-2.1 ii init-system-helpers 1.60 ii lsb-base 11.1.0 ii ruby 1:2.7.6 ii ruby-augeas 1:0.5.0-3+b9 ii ruby-deep-merge 1.1.1-1 ii ruby-shadow 2.5.0+gh-1+b1 Versions of packages puppet recommends: ii debconf-utils 1.5.79 ii lsb-release11.1.0 pn ruby-selinux Versions of packages puppet suggests: pn ruby-hocon pn ruby-rrd - -- no debconf information -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEvu1N7VVEpMA+KD3HS80FZ8KW0F0FAmGsALEACgkQS80FZ8KW 0F1nHQ/6AyVaWCMDdPHi0AyhhQZiEISZP0GYNqdrnD/LYF9SdZ2PRlXxQrQfJ7RI F226bh4sRgzY/pcgfeUmiizaDfCyKxtGrvyjPqOvnoFACDRHDJm/rhjybdsTDCF7 MnHCNjIEic6qoPBqQmG20W15pshRzxbnSojTrZ+4QpHicn7shGYe2EmEJW2ZD6J3 Wsf/YB0Ny7AXKjZzWBqz3TFbBWObo47LC7XiutuirmjM7xe5f+QB5VtGiBk4448f XgWIPU9LwyAS9uUYWbXd+jxSVZ/92YoR83KyfGTd861Gj042EFXvu/zHRYru+FGj zM/H2PoQRudDUVlsVX4LXjKdaPJWxYjqhFOYeESRh86paZJFTzCp2VFdCMnCjAyo y42hH4SFjYsZhysNyDjEMwwSBKjQguKKqkRCjdJ1PeFYWc8CEQwlgAZLtLGSFdPA d22BplnTtZHT3AEweXUNWDvjfmDjAgObe85u/p5YQgAYldrj5f0C9BoWHpJ02P5I 6pi2KzWDgApuVk8OEbMrgoxsKnGxaXKEGRqoYxYZe8MWvDRJ8vlwTgXqZk3Us0LB taAXdHCdzvQ3NxYT6JgWkOeBwcfKY14sVzPfeKE7vzB/Ib/HxqdR4qyAdkWqt2V0 ujonrXF3NDPL5ZAi2QIkb/7v42p3B1nc2PeJJ2z/SoIbq1nfqh8= =CMGz -END PGP SIGNATURE-
Bug#1001022: ruby-pathutil: Not Ruby 3.0 compatible due to kwargs issues
Package: ruby-pathutil Version: 0.16.1-1.1 Severity: serious Tags: patch upstream bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.0 -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi, During tests to fix Jekyll 3 it was discovered, that some issues are caused by ruby-pathutil. There is a new version of this gem available, but this patch: https://github.com/envygeeks/pathutil/pull/5/files will be necessary as well to make it Ruby 3.0 compatible. Regards, Daniel - -- System Information: Debian Release: bookworm/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'stable-security'), (500, 'stable-debug'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.15.0-2-amd64 (SMP w/8 CPU threads) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages ruby-pathutil depends on: ii ruby 1:2.7.6 ii ruby-forwardable-extended 2.6.0-1.1 ruby-pathutil recommends no packages. ruby-pathutil suggests no packages. - -- no debconf information -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEvu1N7VVEpMA+KD3HS80FZ8KW0F0FAmGpH9AACgkQS80FZ8KW 0F0Quw//TSe8FYttG0mg/0uoc+k2t4gLqet8o/38C2mHwJI3aLDD8WiRvjfmnEaX 7Kvlyhtbz+d3Or1iSAcMU3IWXXeBdv/0M9KqQ9LvSJG7C91SrkUOkpPiLj5ungeK 1IgG+FERjHCvYWeesnMDePn68yqEG10ULeHqyS6qjjitTCvUELV0MV/vg1wOGL+8 6w1uz00/3smgpMivdvPp+AsVGwBGW/q3MzsZ2vjg0JTKLbpDtB7pivFk35vY8CzB GJK+qzoMIY87IrF/W1HvlMwh/08FP+CjqT6d/6qc11nQcCKBEUbrI5GQg1fZHnNR 13uCWXovjLA5DLf0o7kobpy8/TKao8wnJyRv69z7YsLrMjIEJJW9/+sw8K+86/en VNRiYP81i9weTd+KEadkyV7ZUtW8OfCF7zwO2Yqo4/og7ILIixA34anttwZHjCGp ocVPSmvBBfkeG2vi0qUDsaXwFMNjYMpgQ/jU5tU2zo9e4Tc9l0YD1YdrByLBtt8A kzJnHh7UoAVXZhzAv+vsuHw6wpuQdPEmVdK6Ff0tU2VSSAnwYeG9paGwM1uBt2va sbuLHkrC2YK25wsEdg63ZD+WuKJ0BKyFXfkOeCX3719J5Rtvh2s+iFHH3pNiFNxY 1/4ndoVPY2eTshJPdq0ZSGhyecPDtNVWCQbBRdwMnibHvi3mJQE= =Rkmc -END PGP SIGNATURE-
Bug#996380: marked as pending in ruby-safe-yaml
Control: tag -1 pending Hello, Bug #996380 in ruby-safe-yaml 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: https://salsa.debian.org/ruby-team/ruby-safe-yaml/-/commit/c41b54f5b21e3790adc8ed2973b848cdd56140ab Add patch to fix build with Ruby 3.0 * d/patches/fix_ruby_3_compatibility.patch: Add patch. - Allow to run the gem with Ruby 3.0 (closes: #996380). * d/patches/series: Adjust. (this message was generated automatically) -- Greetings https://bugs.debian.org/996380
Bug#995353: Info
We need to restart the autopkgtest runs as soon as the fixed version of ruby- rspec-memory hits Testing. Regards, Daniel -- Regards, Daniel Leidert | https://www.wgdd.de/ GPG-Key RSA4096 / BEED4DED5544A4C03E283DC74BCD0567C296D05D GPG-Key ED25519 / BD3C132D8B3805D1808123AB7ACE00941E338C78 https://www.fiverr.com/dleidert https://www.patreon.com/join/dleidert signature.asc Description: This is a digitally signed message part
Bug#998099: marked as pending in ruby-hitimes
Control: tag -1 pending Hello, Bug #998099 in ruby-hitimes 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: https://salsa.debian.org/ruby-team/ruby-hitimes/-/commit/1f4bed3a3d71d0cd73830469bab6ca8ff3148326 Refresh patch and fix build issue on s390x * d/patches/disable-timing-tests.patch: Adjust patch. - Refresh patch and disable missing timing tests susceptible to sceduling latency (closes: #998099). (this message was generated automatically) -- Greetings https://bugs.debian.org/998099
Bug#997357: marked as pending in ruby-fakefs
Control: tag -1 pending Hello, Bug #997357 in ruby-fakefs 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: https://salsa.debian.org/ruby-team/ruby-fakefs/-/commit/1539c970bc02ae3f837f117edb0cbc5c5ea5b7bf Make sure to run build as root * d/control (Rules-Requires-Root): Set to binary-targets (closes: #997357). (this message was generated automatically) -- Greetings https://bugs.debian.org/997357
Bug#998501: marked as pending in ruby-em-http-request
Control: tag -1 pending Hello, Bug #998501 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: https://salsa.debian.org/ruby-team/ruby-em-http-request/-/commit/aab3c600e9afceea28c6f53e3294bc469f83b781 Add missing build-dependency * d/control (Build-Depends): Add ruby-webrick (closes: #998501). (this message was generated automatically) -- Greetings https://bugs.debian.org/998501
Bug#995354: Requires to package ruby-thread-local
Fixing this issue requires to update the gem version to 0.56.x. However in this version a new dependency was added on thread-local: https://github.com/socketry/thread-local Regards, Daniel -- Regards, Daniel Leidert | https://www.wgdd.de/ GPG-Key RSA4096 / BEED4DED5544A4C03E283DC74BCD0567C296D05D GPG-Key ED25519 / BD3C132D8B3805D1808123AB7ACE00941E338C78 https://www.fiverr.com/dleidert https://www.patreon.com/join/dleidert signature.asc Description: This is a digitally signed message part
Bug#996117: marked as pending in ruby-active-model-serializers
Control: tag -1 pending Hello, Bug #996117 in ruby-active-model-serializers 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: https://salsa.debian.org/ruby-team/ruby-active-model-serializers/-/commit/9857a7687983c236dbc8c90bf5c22113e76842bf Add patch to fix tests with Rails 6.1 * d/patches/relax-rails-61-tests.patch: Add patch applied upstream. - Fix tests with Rails 6.1 (closes: #996117). * d/patches/series: Enable new patch. (this message was generated automatically) -- Greetings https://bugs.debian.org/996117
Bug#996451: GSL and ruby-gsl
Hi, I just had a look at ruby-gsl. The package builds and tests fine with the GSL version is was built with. However, the tests break when the version built against 2.7 is run with GSL 2.6 and vice-versa. Maybe this is also due to the ABI breakage (#993324). IMHO you could add a Breaks: ruby-gsl (<< 2.1.0.3+dfsg1-4~) to help the transition. or we wait and rebuild as soon as you upload your latest changes to unstable. Regards, Daniel -- Regards, Daniel Leidert | https://www.wgdd.de/ GPG-Key RSA4096 / BEED4DED5544A4C03E283DC74BCD0567C296D05D GPG-Key ED25519 / BD3C132D8B3805D1808123AB7ACE00941E338C78 https://www.fiverr.com/dleidert https://www.patreon.com/join/dleidert signature.asc Description: This is a digitally signed message part
Bug#996294: Change in webrick 1.7.0 is causing a problem with the tests in Ruby 2.7 (at least)
I did some debugging on the issue reported that the tests fail after adding
ruby-webrick 1.7.0 to b-d for Ruby 3.0.
The problem is in parse_header() (lib/httpclient/session.rb) in the line
828 line = socket.gets("\n")
With webrick 1.7.0 it stalls here. This is caused by this small change in
webrick:
https://github.com/ruby/webrick/commit/069e9b1908aad3a30a0dcf67b6d3bb13c3216d2c
If I revert this, the tests no longer timeout and succeed under Ruby 2.7.
Regards, Daniel
--
Regards,
Daniel Leidert | https://www.wgdd.de/
GPG-Key RSA4096 / BEED4DED5544A4C03E283DC74BCD0567C296D05D
GPG-Key ED25519 / BD3C132D8B3805D1808123AB7ACE00941E338C78
https://www.fiverr.com/dleidert
https://www.patreon.com/join/dleidert
signature.asc
Description: This is a digitally signed message part
Bug#996238: ruby-hamster FTBFS caused by ruby-rbtree and ruby-sorted-set
Source: ruby-sorted-set Version: 1.0.3-2 Severity: serious User: debian-r...@lists.debian.org Usertags: ruby3.0 Tags: help After doing some debugging on the ruby-hamster FTBFS, the problem seems to be ruby-btree and ruby-sorted-set breaking the tests. In a pure Ruby 2.7 environment, this is true: SortedSet.new([1,3,2]).eql?(SortedSet.new([1,2,3])) => true Installing ruby-rbtree, and the same matcher becomes false: SortedSet.new([1,3,2]).eql?(SortedSet.new([1,2,3])) => false Now adding ruby-sorted-set in the mix for the Ruby3.0 transition, which depends on ruby-rbtree, more tests fail. This is causing ruby-hamster's tests to fail. This bug report is to indicate that this blocks the ruby-hamster fix. Regards, Daniel -- Regards, Daniel Leidert | https://www.wgdd.de/ GPG-Key RSA4096 / BEED4DED5544A4C03E283DC74BCD0567C296D05D GPG-Key ED25519 / BD3C132D8B3805D1808123AB7ACE00941E338C78 https://www.fiverr.com/dleidert https://www.patreon.com/join/dleidert signature.asc Description: This is a digitally signed message part
Bug#996350: marked as pending in ruby-rabl
Control: tag -1 pending Hello, Bug #996350 in ruby-rabl 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: https://salsa.debian.org/ruby-team/ruby-rabl/-/commit/57032c0b6d8285b6f8f9d81ca7307444dc88df01 Fix the test issues * debian/ruby-test-files.yaml: Remove file. * debian/ruby-tests.rake: Add, and enable patches by loading Rakefile and running the test target. This fixes the test failures (closes: #996350). * d/patches/fix-rakefile.patch: Add patch. - Fix Rakefile to be able to run the tests. * d/patches/series: Enable new patch. (this message was generated automatically) -- Greetings https://bugs.debian.org/996350
Bug#996378: marked as pending in ruby-rspec-retry
Control: tag -1 pending Hello, Bug #996378 in ruby-rspec-retry 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: https://salsa.debian.org/ruby-team/ruby-rspec-retry/-/commit/91eba55133161295ec87ba1739456cc95ff84c7f Add patch to workaround class variables in tests with Ruby 3.0 * d/patches/0002-Workaround-class-variable-issues.patch: Add patch. - Work around the usage of class variables in tests (closes: #996378). * d/patches/series: Enable new patch. (this message was generated automatically) -- Greetings https://bugs.debian.org/996378
Bug#996527: marked as pending in sup-mail
Control: tag -1 pending Hello, Bug #996527 in sup-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: https://salsa.debian.org/ruby-team/sup-mail/-/commit/9a12bf6ed2976e5dacf68f1adc7d7eb0992472d3 Add patch for Ruby 3.0 compatibility * d/patches/0005-avoid-URI.encode-and-URI.decode.patch: Add patch. - Replace methods not available in Ruby 3.0 (closes: #996527). * d/patches/series: Enable new patch. (this message was generated automatically) -- Greetings https://bugs.debian.org/996527
Bug#1000679: marked as pending in ruby-rr
Control: tag -1 pending Hello, Bug #1000679 in ruby-rr 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: https://salsa.debian.org/ruby-team/ruby-rr/-/commit/12e9e609ee3e27d8b87b6432b3e72060a9cdbcea ruby-rr (3.0.8-1) UNRELEASED * New upstream release. - Fixes Minitest and ActiveSupport integration (closes: #1000679). (this message was generated automatically) -- Greetings https://bugs.debian.org/1000679
Bug#996528: marked as pending in test-kitchen
Control: tag -1 pending Hello, Bug #996528 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: https://salsa.debian.org/ruby-team/test-kitchen/-/commit/b078c418725c243a02c0e9ef9acbbcf810e91d9b Add patch to relax dependency on thor * d/patches/0019-Relax-dependency-on-thor.patch: Add patch. - Allow thor 1.x (closes: #996528) * d/patches/series: Add new patch. (this message was generated automatically) -- Greetings https://bugs.debian.org/996528
Bug#967018: marked as pending in test-kitchen
Control: tag -1 pending Hello, Bug #967018 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: https://salsa.debian.org/ruby-team/test-kitchen/-/commit/f95bcf341f8bb4e0edc481978c238146ff804ce7 Add patch to replace deprecated aruba requires * d/patches/0020-Fix-Aruba-depreaction.patch: Add patch. - Replace deprecated aruba requires (closes: #967018). * d/patches/series: Add new patch. (this message was generated automatically) -- Greetings https://bugs.debian.org/967018
Bug#996137: marked as pending in ruby-binding-of-caller
Control: tag -1 pending Hello, Bug #996137 in ruby-binding-of-caller 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: https://salsa.debian.org/ruby-team/ruby-binding-of-caller/-/commit/52666f29526bdafe719174b5aeb47e076ec4135e ruby-binding-of-caller (1.0.0-1) UNRELEASED * New upstream release (closes: #996137) (this message was generated automatically) -- Greetings https://bugs.debian.org/996137
Bug#996363: marked as pending in ruby-rbpdf
Control: tag -1 pending
Hello,
Bug #996363 in ruby-rbpdf 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:
https://salsa.debian.org/ruby-team/ruby-rbpdf/-/commit/637ee7bff7b2ec4aff2e5d76ff43a7e476947126
Update packaging files
* d/control: Add Rules-Requires-Root field.
(Build-Depends): Add ruby-webrick (closes: #996363).
(Standards-Version): Bump to 4.6.0.
(Depends): Remove interpreters and use ${ruby:Depends}.
* d/copyright: Add Upstream-Contact field.
(Copyright): Add team.
* d/rules: Install upstream changelog.
* d/watch: Update file.
* d/upstream/metadata: Add missing fields.
(this message was generated automatically)
--
Greetings
https://bugs.debian.org/996363
Bug#996350: Problem can be tracked down to ruby-rr
I was examining the problem. The problem seems to be ruby-rr 3.x. rabl actually requires rr 1.x, and with this version it works. I verified this by building against ruby-rr from Stable. But with ruby-rr 3.x in Testing/Unstable it fails. I don't have a fix for that. -- Regards, Daniel Leidert | https://www.wgdd.de/ GPG-Key RSA4096 / BEED4DED5544A4C03E283DC74BCD0567C296D05D GPG-Key ED25519 / BD3C132D8B3805D1808123AB7ACE00941E338C78 https://www.fiverr.com/dleidert https://www.patreon.com/join/dleidert signature.asc Description: This is a digitally signed message part
Bug#996295: marked as pending in ruby-i18n-inflector-rails
Control: tag -1 pending Hello, Bug #996295 in ruby-i18n-inflector-rails 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: https://salsa.debian.org/ruby-team/ruby-i18n-inflector-rails/-/commit/46f1206101506bef4a831da0f8f62a49111e0799 Add patch to fix FTBFS * d/patches/fix-for-ruby3-and-rails6.patch: Add patch. - Fix errors with Ruby 3.0 and Rails 6 (closes: #996295). * d/patches/series: Enable new patch. (this message was generated automatically) -- Greetings https://bugs.debian.org/996295
Bug#996155: marked as pending in origami-pdf
Control: tag -1 pending Hello, Bug #996155 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: https://salsa.debian.org/ruby-team/origami-pdf/-/commit/ee3bbfed5480084305724d42939638475c313f6f Fix Ruby 3.0 keyword arguments error * d/patches/0002-Fix-Ruby-2.7-keyword-arguments-warnings.patch: Add patch. - Fixes Ruby 3.0 keyword argument handling error (closes: #996155). * d/patches/series: Add new patch. (this message was generated automatically) -- Greetings https://bugs.debian.org/996155
Bug#951248: marked as pending in origami-pdf
Control: tag -1 pending Hello, Bug #951248 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: https://salsa.debian.org/ruby-team/origami-pdf/-/commit/73c56e34ed807c4537c0d1580731fecab1d7703a origami-pdf (2.0.4+dfsg-1) UNRELEASED * New upstream release. - Removes Bignum/Fixnum usage (closes: #951248). (this message was generated automatically) -- Greetings https://bugs.debian.org/951248
Bug#990443: [DRE-maint] Bug#990443: Issue seems to be ruby-gtk2
Am Donnerstag, dem 25.11.2021 um 22:15 +0100 schrieb Daniel Leidert: > I did some debugging with this issue and it actually seems to be caused by > ruby-gtk2. It is easy to reproduce. In irb: > > require 'gtk2' > include Gtk > require 'openssl' > > => crash (happens when openssl loads openssl.so): Correkt traceback: 14: from test.rb:3:in `' 13: from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require' 12: from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require' 11: from /usr/lib/ruby/2.7.0/openssl.rb:20:in `' 10: from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require' 9: from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require' 8: from /usr/lib/ruby/2.7.0/openssl/ssl.rb:15:in `' 7: from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require' 6: from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require' 5: from /usr/lib/ruby/2.7.0/ipaddr.rb:19:in `' 4: from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require' 3: from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require' 2: from /usr/lib/ruby/2.7.0/socket.rb:4:in `' 1: from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require' /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require': superclass mismatch for class Socket (TypeError) -- Regards, Daniel Leidert | https://www.wgdd.de/ GPG-Key RSA4096 / BEED4DED5544A4C03E283DC74BCD0567C296D05D GPG-Key ED25519 / BD3C132D8B3805D1808123AB7ACE00941E338C78 https://www.fiverr.com/dleidert https://www.patreon.com/join/dleidert signature.asc Description: This is a digitally signed message part
Bug#990443: Issue seems to be ruby-gtk2
I did some debugging with this issue and it actually seems to be caused by ruby-gtk2. It is easy to reproduce. In irb: require 'gtk2' include Gtk require 'openssl' => crash (happens when openssl loads openssl.so): Traceback (most recent call last): 28: from /usr/bin/pdfwalker:25:in `' 27: from /usr/bin/pdfwalker:25:in `load' 26: from /usr/share/rubygems-integration/all/gems/origami-2.0.4/bin/pdfwalker:4:in `' 25: from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require' 24: from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require' 23: from /usr/share/origami/gui/walker.rb:31:in `' 22: from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require' 21: from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require' 20: from /usr/share/rubygems-integration/all/gems/origami-2.0.4/lib/origami.rb:41:in `' 19: from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require' 18: from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require' 17: from /usr/share/rubygems-integration/all/gems/origami-2.0.4/lib/origami/pdf.rb:49:in `' 16: from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require' 15: from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require' 14: from /usr/share/rubygems-integration/all/gems/origami-2.0.4/lib/origami/encryption.rb:21:in `' 13: from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require' 12: from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require' 11: from /usr/lib/ruby/2.7.0/openssl.rb:20:in `' 10: from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require' 9: from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require' 8: from /usr/lib/ruby/2.7.0/openssl/ssl.rb:15:in `' 7: from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require' 6: from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require' 5: from /usr/lib/ruby/2.7.0/ipaddr.rb:19:in `' 4: from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require' 3: from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require' 2: from /usr/lib/ruby/2.7.0/socket.rb:4:in `' 1: from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require' /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require': superclass mismatch for class Socket (TypeError) That's not a bug in origami. I'll have a look at ruby-gtk2. However, I guess as soon as Gtk2 vanishes from Debian, pdfwalker will become dysfunctional. Regards, Daniel -- Regards, Daniel Leidert | https://www.wgdd.de/ GPG-Key RSA4096 / BEED4DED5544A4C03E283DC74BCD0567C296D05D GPG-Key ED25519 / BD3C132D8B3805D1808123AB7ACE00941E338C78 https://www.fiverr.com/dleidert https://www.patreon.com/join/dleidert signature.asc Description: This is a digitally signed message part
Bug#996352: marked as pending in ruby-rack-timeout
Control: tag -1 pending Hello, Bug #996352 in ruby-rack-timeout 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: https://salsa.debian.org/ruby-team/ruby-rack-timeout/-/commit/df14f02502c32de385e237a09cdbf1a1107bc93b Add patch to fix Ruby 3.0 compatbility * d/patches/Explicitly-convert-hash-to-kwargs-in-test_helper.patch: Add. - Fix for Ruby 3.0 keyword argument handling (closes: #996352). * d/patches/series: Add new patch. (this message was generated automatically) -- Greetings https://bugs.debian.org/996352
Bug#969157: marked as pending in ruby-diaspora-federation-rails
Control: tag -1 pending Hello, Bug #969157 in ruby-diaspora-federation-rails 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: https://salsa.debian.org/ruby-team/ruby-diaspora-federation-rails/-/commit/1f6da353e718c690b24133e094fea601193e1fbc ruby-diaspora-federation-rails (0.2.7-1) UNRELEASED * New upstream release. - Adds support for Ruby 3.0 and Rails < 7 (closes: #969157). (this message was generated automatically) -- Greetings https://bugs.debian.org/969157
Bug#969157: marked as pending in ruby-diaspora-federation-rails
Control: tag -1 pending Hello, Bug #969157 in ruby-diaspora-federation-rails 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: https://salsa.debian.org/ruby-team/ruby-diaspora-federation-rails/-/commit/e71e325c7082d5a144a31282386c04da4445ec49 Add patch to backport Rails 6 support * d/patches/relax-rails-dep.patch: Add patch. - Relax Rails dependency accordingly to upstream's master branch (closes: #969157). * d/patches/series: Add new patch. The change has not been shipped with version 0.2.7. Therefor we have to "backport" the patch. (this message was generated automatically) -- Greetings https://bugs.debian.org/969157
Bug#964607: Massive update necessary
This gem is out-of-date. Upstream is at 3.2.2, which requires packaging for google-cloud-translate-v2 and google-cloud-translate-v3 and updating google- cloud-core to >= 1.6. The tests require packageing google-style. Regards, Daniel -- Regards, Daniel Leidert | https://www.wgdd.de/ GPG-Key RSA4096 / BEED4DED5544A4C03E283DC74BCD0567C296D05D GPG-Key ED25519 / BD3C132D8B3805D1808123AB7ACE00941E338C78 https://www.fiverr.com/dleidert https://www.patreon.com/join/dleidert signature.asc Description: This is a digitally signed message part
Bug#996323: marked as pending in ruby-mono-logger
Control: tag -1 pending Hello, Bug #996323 in ruby-mono-logger 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: https://salsa.debian.org/ruby-team/ruby-mono-logger/-/commit/4bfe8ac410a0e8532e14e252c388d06a9260a152 ruby-mono-logger (1.1.1-1) UNRELEASED * Team upload. * New upstream release. - Fixes compatibility with Ruby 3.0 (closes: #996323). (this message was generated automatically) -- Greetings https://bugs.debian.org/996323
Bug#996345: marked as pending in ruby-packable
Control: tag -1 pending Hello, Bug #996345 in ruby-packable 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: https://salsa.debian.org/ruby-team/ruby-packable/-/commit/da340b430a052d3313303df76de70ee207505b4a Add patch to fix ArgumentError * d/patches/fix-ruby-3.0-argumenterror.patch: Add patch. - Fix for trying to create a Proc object without a block (closes: #996345). * d/patches/series: Add new patch. (this message was generated automatically) -- Greetings https://bugs.debian.org/996345
Bug#996300: marked as pending in ruby-jaeger-client
Control: tag -1 pending Hello, Bug #996300 in ruby-jaeger-client 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: https://salsa.debian.org/ruby-team/ruby-jaeger-client/-/commit/da76fc757eec6a74f0f51e44733ee2f0bf18700e ruby-jaeger-client (1.2.0-1) UNRELEASED * New upstream release. - Provides compatibility with Ruby 3.0 (closes: #996300). (this message was generated automatically) -- Greetings https://bugs.debian.org/996300
Bug#996351: marked as pending in ruby-rack-oauth2
Control: tag -1 pending Hello, Bug #996351 in ruby-rack-oauth2 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: https://salsa.debian.org/ruby-team/ruby-rack-oauth2/-/commit/ee3d412c2e843b9cf0882153a71ab1cff57389ac ruby-rack-oauth2 (1.19.0-1) UNRELEASED * New upstream release. - Removes usage of obsolete URI.encode method (closes: #996351). (this message was generated automatically) -- Greetings https://bugs.debian.org/996351
Bug#996309: marked as pending in ruby-kubeclient
Control: tag -1 pending Hello, Bug #996309 in ruby-kubeclient 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: https://salsa.debian.org/ruby-team/ruby-kubeclient/-/commit/d8da5d49ee86d4ad2a2b93fdffc2701d7ae8116f Update packaging files * d/control (Build-Depends): Bump ruby-recursive-open-struct to 1.1.3, which is Ruby 3.0 compatible (closes: #996309). * d/copyright (Copyright): Add team. * d/rules: Use gem installation layout and install upstream changelog. * d/watch: Update file. * d/upstream/metadata: Update Changelog URL. (this message was generated automatically) -- Greetings https://bugs.debian.org/996309
Bug#996364: marked as pending in ruby-recursive-open-struct
Control: tag -1 pending Hello, Bug #996364 in ruby-recursive-open-struct 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: https://salsa.debian.org/ruby-team/ruby-recursive-open-struct/-/commit/75483f8c9a820734b0bb9a5174f991c78f8e0a9e ruby-recursive-open-struct (1.1.3-1) UNRELEASED * New upstream release. - Adds Ruby 3.0 support (closes: #996364). (this message was generated automatically) -- Greetings https://bugs.debian.org/996364
Bug#996365: marked as pending in ruby-redis-activesupport
Control: tag -1 pending Hello, Bug #996365 in ruby-redis-activesupport 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: https://salsa.debian.org/ruby-team/ruby-redis-activesupport/-/commit/0186c6c1933b2689172b2f48d2c7f3aa1d580662 Add patch to fix tests with Rails 6 * d/patches/Disable-tests-which-will-fail-with-Rails-6.patch: Add patch. - Fix remaining test failures caused by this gem not being targetted at Rails 6 (closes: #996365). * d/patches/series: Enable new patch. (this message was generated automatically) -- Greetings https://bugs.debian.org/996365
Bug#996239: marked as pending in ruby-hashie
Control: tag -1 pending Hello, Bug #996239 in ruby-hashie 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: https://salsa.debian.org/ruby-team/ruby-hashie/-/commit/ecc355f37ea1712b938f578d4093fd9be39a60a5 Add patch to fix FTBFS * d/patches/0002-Suppress-keyword-arguments-warning-for-Ruby-2.7.0.patch: Add - Fix ArgumentError with Ruby 3 (closes: #996239). * d/patches/series: Enable new patch. (this message was generated automatically) -- Greetings https://bugs.debian.org/996239
Bug#996370: marked as pending in ruby-rgen
Control: tag -1 pending Hello, Bug #996370 in ruby-rgen 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: https://salsa.debian.org/ruby-team/ruby-rgen/-/commit/bacd0489d2c81cea85b7595a90026108258d4dc5 Fix tests * d/patches/Handle-Ruby-3-test-failures-fue-to-new-name-method.patch: Add. - In Ruby 3 some classes got name methods. This leads to an unexpected error message in some tests, so we ignore them (closes: #996370). * d/patches/series: Adjust file. (this message was generated automatically) -- Greetings https://bugs.debian.org/996370
Bug#996381: marked as pending in ruby-sanitize
Control: tag -1 pending Hello, Bug #996381 in ruby-sanitize 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: https://salsa.debian.org/ruby-team/ruby-sanitize/-/commit/56462205a3c0b8529533a88bc20e86c6c2450c78 ruby-sanitize (5.2.3-1) UNRELEASED * New upstream release. - Fixes issue when using keyword arguments (closes: #996381). (this message was generated automatically) -- Greetings https://bugs.debian.org/996381
Bug#1000488: marked as pending in ruby-nokogumbo
Control: tag -1 pending Hello, Bug #1000488 in ruby-nokogumbo 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: https://salsa.debian.org/ruby-team/ruby-nokogumbo/-/commit/614048c6710572a43789c2f048026c451cefa089 Add patch to make nokogumbo Ruby 3.0 compatible * d/patches/Fix-Ruby3-keywords-issue.patch: Add patch. - Fixes deprecated keyword parameters handling (closes: #1000488). * d/patches/series: Enable new patch. (this message was generated automatically) -- Greetings https://bugs.debian.org/1000488
Bug#996524: marked as pending in ruby-whitequark-parser
Control: tag -1 pending Hello, Bug #996524 in ruby-whitequark-parser 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: https://salsa.debian.org/ruby-team/ruby-whitequark-parser/-/commit/50a09bacea441200b52d5554c816f644eb4775ca ruby-whitequark-parser (3.0.2.0-1) unstable This version adds Ruby 3.0 support (closes: #996524). (this message was generated automatically) -- Greetings https://bugs.debian.org/996524
Bug#996526: marked as pending in rubygems
Control: tag -1 pending Hello, Bug #996526 in rubygems 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: https://salsa.debian.org/ruby-team/rubygems/-/commit/e848598f1d036f952d53ddb50d0610619f06de95 Update packaging files and fix FTBFS * d/bundler.docs: Add bundler/UPGRADING.md. * d/control (Standards-Version): Don't use the minor patch level. (Build-Depends): Add ruby-webrick (closes: #996526). * d/copyright: Add bundler copyright and license information. (Copyright): Update and add team. * d/watch: Update file. (this message was generated automatically) -- Greetings https://bugs.debian.org/996526
Bug#997364: marked as pending in ruby-sprite-factory
Control: tag -1 pending Hello, Bug #997364 in ruby-sprite-factory 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: https://salsa.debian.org/ruby-team/ruby-sprite-factory/-/commit/392beac8f4ca4b947fb8102b61017da27f0f4d6a Add patch to replace deprecated method * d/patches/replace-deprecated-method-opacity.patch: Add patch. - Replace deprecated method (closes: #997364). * d/patches/series: Enable new patch. (this message was generated automatically) -- Greetings https://bugs.debian.org/997364
Bug#996380: Explanation
It seems here is an explanation of the problem: https://github.com/paolobrasolin/jekyll-antex/issues/16 I cannot find any patches so far. Regards, Daniel -- Regards, Daniel Leidert | https://www.wgdd.de/ GPG-Key RSA4096 / BEED4DED5544A4C03E283DC74BCD0567C296D05D GPG-Key ED25519 / BD3C132D8B3805D1808123AB7ACE00941E338C78 https://www.fiverr.com/dleidert https://www.patreon.com/join/dleidert signature.asc Description: This is a digitally signed message part
Bug#996212: Fix require dalli 3.x
After having a look at the issue, the 2.x series is not compatible with Rails 6.1. We need to upload dalli 3.x instead. https://github.com/petergoldstein/dalli/issues/771 I checked and the 3.x series builds fine (except for one test which requires network access and must be disabled). Regards, Daniel -- Regards, Daniel Leidert | https://www.wgdd.de/ GPG-Key RSA4096 / BEED4DED5544A4C03E283DC74BCD0567C296D05D GPG-Key ED25519 / BD3C132D8B3805D1808123AB7ACE00941E338C78 https://www.fiverr.com/dleidert https://www.patreon.com/join/dleidert signature.asc Description: This is a digitally signed message part
Bug#996301: marked as pending in ruby-jbuilder
Control: tag -1 pending Hello, Bug #996301 in ruby-jbuilder 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: https://salsa.debian.org/ruby-team/ruby-jbuilder/-/commit/0d696ce1230a2fe2788f8bb5444cb52e20693fca Add patch to fix tests * d/patches/fix-the-test-that-depends-on-the-time-helper.patch: Add patch. - Fix test case with rails 6.1 and timezone-aware helper (closes: #996301). * d/patches/series: Enable new patch. (this message was generated automatically) -- Greetings https://bugs.debian.org/996301
Bug#996304: marked as pending in ruby-json-schema
Control: tag -1 pending Hello, Bug #996304 in ruby-json-schema 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: https://salsa.debian.org/ruby-team/ruby-json-schema/-/commit/7093323f30f36c2f376f33a3c417d27eaab13e1d Add patch to fix FTBFS with Ruby 3.0 * d/patches/ruby_30_support_uri_open.patch: Add patch. - Call URI.open instead of open (closes: #996304). * d/patches/series: Enable new patch. (this message was generated automatically) -- Greetings https://bugs.debian.org/996304
Bug#996229: marked as pending in ruby-flexmock
Control: tag -1 pending Hello, Bug #996229 in ruby-flexmock 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: https://salsa.debian.org/ruby-team/ruby-flexmock/-/commit/16b99bbb52294d3fc2e222984d439fd1215f9b6f Add patch by Fedora to fix build with Ruby 3.0 * d/patches/0003-Fix-compatibility-with-Ruby-3.0.patch: Add patch. - Fix build with Ruby 3.0 (closes: #996229). * d/patches/series: Enable new patch. (this message was generated automatically) -- Greetings https://bugs.debian.org/996229
Bug#996297: Ruby 3 freezes Ranges by default
The problem is caused by Ruby 3 freezing Ranges by default [1,2]. Thus the tests try to handle already frozen objects and some code is not working as well. I've forwarded the problem to upstream, but they have been inactive for some time. [1] https://bugs.ruby-lang.org/issues/15504 [2] https://github.com/ruby/ruby/pull/3583/files -- Regards, Daniel Leidert | https://www.wgdd.de/ GPG-Key RSA4096 / BEED4DED5544A4C03E283DC74BCD0567C296D05D GPG-Key ED25519 / BD3C132D8B3805D1808123AB7ACE00941E338C78 https://www.fiverr.com/dleidert https://www.patreon.com/join/dleidert signature.asc Description: This is a digitally signed message part
Bug#996140: marked as pending in ruby-bogus
Control: tag -1 pending
Hello,
Bug #996140 in ruby-bogus 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:
https://salsa.debian.org/ruby-team/ruby-bogus/-/commit/e984d931b5f765002d56ed50fa7b69fe9595416f
Update packaging files
* d/control: Add Rules-Requires-Root field.
(Standards-Version): Bump to 4.6.0.
(Depends): Remove interpreters and use ${ruby:Depends}.
* d/copyright: Add Upstream-Contact field.
(Copyright): Add team.
* d/ruby-tests.rake: Exclude 2.0/2.1 tests with Ruby 3.0 (closes: #996140).
* d/rules: Use gem installation layout.
* d/watch: Update file to use secure gemwatch URL.
* d/upstream/metadata: Add missing fields.
(this message was generated automatically)
--
Greetings
https://bugs.debian.org/996140
Bug#996382: marked as pending in ruby-seamless-database-pool
Control: tag -1 pending Hello, Bug #996382 in ruby-seamless-database-pool 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: https://salsa.debian.org/ruby-team/ruby-seamless-database-pool/-/commit/f820bc6a8d91a276b935de5b350dff6d9c061b15 Add patch to fix FTBFS * d/patches/0002-Fix-Ruby-3.0-kwargs-handling.patch: Add patch. - Fix handling of keyword arguments for Ruby 3.0 (closes: #996382). * d/patches/series: Enable new patch. (this message was generated automatically) -- Greetings https://bugs.debian.org/996382
Bug#996126: marked as pending in ruby-attr-encrypted
Control: tag -1 pending Hello, Bug #996126 in ruby-attr-encrypted 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: https://salsa.debian.org/ruby-team/ruby-attr-encrypted/-/commit/98da5fe243d0774be3f007c9217fc9e793e206ed Fix FTBFS by fixing Ruby 2.7/3.0 compatibility * d/patches/fix-ruby-3.0.patch: Add patch. - Fix support for Ruby 2.7 and its kwargs (closes: #996126). * d/patches/series: Enable new patch. (this message was generated automatically) -- Greetings https://bugs.debian.org/996126
Bug#996128: marked as pending in ruby-awesome-print
Control: tag -1 pending Hello, Bug #996128 in ruby-awesome-print 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: https://salsa.debian.org/ruby-team/ruby-awesome-print/-/commit/4b5ff87b83ad5c1fc0deb31f0c72edbc09f2a529 ruby-awesome-print (1.9.2-1) UNRELEASED * New upstream release. - Provides compatbility with Ruby 3.0 (closes: #996128). (this message was generated automatically) -- Greetings https://bugs.debian.org/996128
Bug#996119: marked as pending in ruby-activerecord-nulldb-adapter
Control: tag -1 pending
Hello,
Bug #996119 in ruby-activerecord-nulldb-adapter 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:
https://salsa.debian.org/ruby-team/ruby-activerecord-nulldb-adapter/-/commit/e15ee7c2458c63f5d4d7bcba737f94868ea7e1c0
Update packaging files
* d/control (Standards-Version): Bump to 4.6.0.
(Build-Depends): Bump to ruby-activerecord >= 2:6.1 (closes: #996119).
(Depends): Add ${ruby:Depends}.
* d/copyright: Add Upstream-Contact field.
(Copyright): Add team.
* d/rules: Use gem installation layout and install changelog.
* d/upstream/metadata: Add Archive and Changelog fields.
(this message was generated automatically)
--
Greetings
https://bugs.debian.org/996119
Bug#996303: marked as pending in ruby-json-jwt
Control: tag -1 pending
Hello,
Bug #996303 in ruby-json-jwt 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:
https://salsa.debian.org/ruby-team/ruby-json-jwt/-/commit/6ecae09c727dbb05924661c016b725a2c0567afb
Update packaging files
* d/control: Add Rules-Requires-Root field.
(Standards-Version): Bump to 4.6.0.
(Build-Depends): Require ruby-activesupport >= 6.1 (closes: #996303).
(Depends): Use ${ruby:Depends}.
* d/copyright: Add Upstream-Contact field.
(Copyright): Add team.
* d/rules: Use gem installation layout.
* d/watch: Update file.
* d/upstream/metadata: Add Archive field.
(this message was generated automatically)
--
Greetings
https://bugs.debian.org/996303
Bug#996117: Update after uploading Rails 6.1
Am Samstag, dem 20.11.2021 um 00:18 +0100 schrieb Daniel Leidert: > With Rails 6.1 the package now fails to build with Ruby 2.7 and a bunch of > errors like this: > > Failure: > ActionController::Serialization::ImplicitSerializerTest#test_render_array_using > _custom_root > [/<>/test/action_controller/serialization_test.rb:186]: > --- expected > +++ actual > @@ -1 +1 @@ > -"application/json" > +"application/json; charset=utf-8" > > > rails test /<>/test/action_controller/serialization_test.rb:181 > I think that this commit was supposed to fix this test issue: https://github.com/rails-api/active_model_serializers/commit/55a6b23cd84395029aa92605f8aae73f37f57c4a However, it doesn't work and this issue says that it has a different meaning: https://github.com/rails/rails/issues/40376 It is possible that this problem is unsolved at the moment. -- Regards, Daniel Leidert | https://www.wgdd.de/ GPG-Key RSA4096 / BEED4DED5544A4C03E283DC74BCD0567C296D05D GPG-Key ED25519 / BD3C132D8B3805D1808123AB7ACE00941E338C78 https://www.fiverr.com/dleidert https://www.patreon.com/join/dleidert signature.asc Description: This is a digitally signed message part
Bug#996117: Update after uploading Rails 6.1
With Rails 6.1 the package now fails to build with Ruby 2.7 and a bunch of errors like this: Failure: ActionController::Serialization::ImplicitSerializerTest#test_render_array_using_custom_root [/<>/test/action_controller/serialization_test.rb:186]: --- expected +++ actual @@ -1 +1 @@ -"application/json" +"application/json; charset=utf-8" rails test /<>/test/action_controller/serialization_test.rb:181 -- Regards, Daniel Leidert | https://www.wgdd.de/ GPG-Key RSA4096 / BEED4DED5544A4C03E283DC74BCD0567C296D05D GPG-Key ED25519 / BD3C132D8B3805D1808123AB7ACE00941E338C78 https://www.fiverr.com/dleidert https://www.patreon.com/join/dleidert signature.asc Description: This is a digitally signed message part
Bug#996228: marked as pending in ruby-ffaker
Control: tag -1 pending Hello, Bug #996228 in ruby-ffaker 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: https://salsa.debian.org/ruby-team/ruby-ffaker/-/commit/a341b7e36f4f9bcbe855064914a9adf3b7490408 Add patch to fix FTBFS * d/patches/0003-Test-with-github-action-ruby-3-468.patch: Add patch. - Fix Ruby 3 compatibility (closes: #996228). * d/patches/series: Enable new patch. (this message was generated automatically) -- Greetings https://bugs.debian.org/996228
Bug#996159: marked as pending in ruby-batch-loader
Control: tag -1 pending
Hello,
Bug #996159 in ruby-batch-loader 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:
https://salsa.debian.org/ruby-team/ruby-batch-loader/-/commit/df92d61337b44f2366b3c90e042fddcf47d6a86e
Update packaging files
* d/control (Build-Depends): Adjust ruby-graphql version (closes: #996159).
(Depends): Remove ruby-graphql and rely on ${ruby:Depends}.
* d/copyright (Copyright): Add team.
* d/rules: Use gem installation layout.
* d/watch: Update file.
* d/upstream/metadata: Update some URLs.
(this message was generated automatically)
--
Greetings
https://bugs.debian.org/996159
Bug#995358: marked as pending in ruby-graphql
Control: tag -1 pending Hello, Bug #995358 in ruby-graphql 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: https://salsa.debian.org/ruby-team/ruby-graphql/-/commit/68709ce9c8c544d7c9df4ff0206d7ca42cae54a4 Add patch to fix FTBFS in ruby-batch-loader * d/patches/Add-missing-require.patch: Add patch. - Fix NameError by adding missing require statement (closes: #995358). * d/patches/series: Enable new patch. (this message was generated automatically) -- Greetings https://bugs.debian.org/995358
Bug#996366: marked as pending in ruby-regexp-parser
Control: tag -1 pending Hello, Bug #996366 in ruby-regexp-parser 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: https://salsa.debian.org/ruby-team/ruby-regexp-parser/-/commit/82a4d330a36ec918ed68ce49c677fcb36f324169 Fix FTBFS and Riby 3 compatibility * d/patches/996366-fix-frozenerror.patch: Add patch. - Don't modify range for Ruby 2.7+ (closes: #996366). * d/patches/series: Enable new patch. (this message was generated automatically) -- Greetings https://bugs.debian.org/996366
