Bug#1078686: riseup-vpn: missing dependency - qrc:/main.qml: module "org.kde.breeze" is not installed

2024, ഒക്ടോ 21 10:57:51 PM Nilesh Patra : > Hi Praveen, Marco, > >> following rule nr.0 of bug reporting, i.e. always search for an already >> existing bug report with an error message similar to what you have before >> opening a new report, you could have found #1073959. We had already found >

Bug#1085033: Wishlist: include script to generate open VPN configuration file

Package: riseup-vpn Severity: wishlist Version: 0.24.8+ds2-1 Including this script https://github.com/BarbossHack/RiseupVPN-OpenVPN in riseup-vpn will be useful in situations like, 1. riseup-vpn qt client does not work (did not work on two of my mobile devices Librem 5/Trixie and FLX1/Trixie )

Bug#1078686: riseup-vpn: missing dependency - qrc:/main.qml: module "org.kde.breeze" is not installed

On Wed, Aug 28 2024 at 18:54:11 +00:00:00, Nilesh Patra wrote: Since as per last conversation, there's nothing diagnosable at riseup-vpn's end, and the issue looks to stem somewhere from qt/kde deps on mobian trixie, there's not much that can be done here. I think we should wait till we f

Bug#1078686: riseup-vpn: missing dependency - qrc:/main.qml: module "org.kde.breeze" is not installed

On 19/8/24 11:58 AM, Pirate Praveen wrote: But riseup-vpn is still showing the progress bar for a long time. Finally after a long wait it showed the connect button and pressing on it took a long long time before it was connected. On the same connection from laptop it connect very fast

Bug#1078686: riseup-vpn: missing dependency - qrc:/main.qml: module "org.kde.breeze" is not installed

On 19/8/24 11:23 AM, Pirate Praveen wrote: On 19/8/24 2:41 AM, Nilesh Patra wrote: to avoid waiting for MOTD end point to respond. Is OpenVPN working fine? I will test with a plain openvpn connection. I had to install openvpn-systemd-resolved (at least openvpn showed correct error

Bug#1078686: riseup-vpn: missing dependency - qrc:/main.qml: module "org.kde.breeze" is not installed

On 19/8/24 2:41 AM, Nilesh Patra wrote: What error do you get with phosh? Both gives same error (what I shared earlier). I was just suggesting behavior could be different if the theme is different. You could give a try with the riseup-vpn package backported on bookworm. It uses QT6 but i

Bug#1078686: riseup-vpn: missing dependency - qrc:/main.qml: module "org.kde.breeze" is not installed

On 19/8/24 1:40 AM, Nilesh Patra wrote: I don't think riseup-vpn does anything differently for phosh/plasma. IIRC you reported a bug once that it was not working on phosh and it was fixed later. The default theme could be different on both. It works fine on my laptop as well. It also worked

Bug#1078686: riseup-vpn: missing dependency - qrc:/main.qml: module "org.kde.breeze" is not installed

On 19/8/24 12:32 AM, Nilesh Patra wrote: I am very _very_ sure that it does not come from riseup-vpn. org.kde.breeze is not even present anywhere in the source code. [nilesh:/tmp/riseup-vpn]$ grep -irn breeze | wc -l 0 This was also tested rigorously by at least 3 people before it was uploaded

Bug#1078686: riseup-vpn: missing dependency - qrc:/main.qml: module "org.kde.breeze" is not installed

Package: riseup-vpn Version: 0.24.5+ds1-2+b2 Severity: grave Justification: fails to start One a freshly installed mobian trixie installer on Librem 5 (arm64) riseup-vpn does not start and gives the following error qrc:/main.qml: module "org.kde.breeze" is not installed Installing qml-module-

Bug#1069616: rc-buggy, not needed anymore

Package: ftp.debian.org Severity: normal X-Debbugs-Cc: ruby-...@packages.debian.org Control: affects -1 + src:ruby-eye User: ftp.debian@packages.debian.org Control: block -1 by 1069615 rc buggy #1031479 and originally packaged as dependency of diaspora which is now requested to be removed.

Bug#1069615: RM: diaspora -- ROM; unmaintained, rc-buggy

Package: ftp.debian.org Severity: normal X-Debbugs-Cc: diasp...@packages.debian.org Control: affects -1 + src:diaspora User: ftp.debian@packages.debian.org Usertags: remove I was hoping to come back to updating diaspora, but I don't think I will be able to find time. It is affected by rc bug

Bug#1068230: automatic suspend regression with gnome-settings-daemon 46

Package: gnome-settings-daemon,phosh severity: serious Recently automatic suspend stopped working. I think this was after gnome settings daemon 46 was available. Some background Not sure if phosh needs some adjustments w

Bug#1068049: update firefox-esr-mobile-config to latest upstream version

Package: firefox-esr-mobile-config Version: 4.2.0-1 This release includes fixes for extensions like browserpass

Bug#1025084: ruby-graphlient fails to rebuild after updating ruby-faraday to upstream

Control: fixed -1 0.7.0-1 On Wed, 7 Feb 2024 14:03:34 +0530 Praveen Arimbrathodiyil wrote: Control: severity -1 serious On Sun, 18 Jun 2023 13:14:21 +0530 Pirate Praveen wrote: > > Since ruby-faraday-middleware is deprecated, we should update to > graphlient 0.7 ruby-farada

Bug#1063658: drop snowlow-tracker orig tar

Package: gitlab Version: 16.6.6-3 Severity: wishlist snowplow-tracker orig.tar can be removed now, this was included because snowplow-tracker was in vendor in a generated form so providing the corresponding source was required to satisfy dfsg. Now snowplow-tracker is available from npmjs.com a

Bug#1063655: RM: ruby-graphql-errors -- ROM; unmaintained upstream, incompatible with ruby-graphql 2.x

Package: ftp.debian.org Severity: normal User: ftp.debian@packages.debian.org Usertags: remove X-Debbugs-Cc: ruby-graphql-err...@packages.debian.org Control: affects -1 + src:ruby-graphql-errors Control: block 1063654 by -1 Reported as RC bug 1063654. ruby-graphlient dropped the build depende

Bug#1063654: ruby-graphql-errors - upstream dead and incompatible with ruby-graphql 2.x

Package: ruby-graphql-errors Version: 0.4.0-2 Severity: serious source package has 1 unsatisfiable build dependency Build dependencies in unstable cannot be satisfied on amd64 because: unsatisfied dependency on ruby-graphql (< 2) Last commint was 4 years ago and https://github.com/exAsp

Bug#1052730: ruby-delayed-job: FTBFS: ERROR: Test "ruby3.1" failed: ArgumentError:

Control: forwarded -1 https://github.com/collectiveidea/delayed_job/pull/1203 On Tue, 26 Sep 2023 14:40:49 +0200 Lucas Nussbaum wrote: Relevant part (hopefully): > ArgumentError: >Invalid Timezone: US/Eastern Forwarded fix upstream https://github.com/collectiveidea/delayed_job

Bug#1063478: gem2deb rails assets smoke test should handle links or skip the test during build

Control: severity -1 important On 9/2/24 6:48 PM, Pirate Praveen wrote: Without libjs-underscore in build depends, the test should fail, but it is passing. ruby-rails-assets-underscore source package includes underscore.js and it is replaced by symlink to libjs-underscore only in dh_install

Bug#1063478: gem2deb rails assets smoke test should handle links or skip the test during build

Control: severity -1 serious On Fri, 9 Feb 2024 00:30:03 +0530 Pirate Praveen wrote: For majority of packages that wraps javascript assets, the actual assets are shipped in a libjs-* package and ruby-* package only include a symbolic link. Testing further with ruby-rails-assets-underscore

Bug#1063478: gem2deb rails assets smoke test should handle links or skip the test during build

Package: gem2deb Version: 2.2.1 Sevrity: important For majority of packages that wraps javascript assets, the actual assets are shipped in a libjs-* package and ruby-* package only include a symbolic link. At present, this means, the test will always fail in such cases since dh_link step is

Bug#1063389: Find out which dependency causes these failures with ruby-grape 2.0

Package: ruby-grape severity: wishlist I'm going to patch this to match the extected outcome, but we should figure out which dependency is causing a mismatch and ideally sync with upstream. Failures: 1) Grape::Http::Headers is expected to eq "location" Failure/Error: it { expect(descr

Bug#1063198: gitlab: GraphQL returns 500 when moving issues on issue board

On 05/02/24 11:06 pm, Jakob Haufe wrote: On Mon, 5 Feb 2024 22:39:41 +0530 Pirate Praveen wrote: One thing I can think of is newer graphql gem. See if manually installing [1] graphql 2.0.27 fixes it. Yes, you are right. Downgrading graphql to 2.0.27 fixes it. Sad fact: Even 16.8 still

Bug#1063198: gitlab: GraphQL returns 500 when moving issues on issue board

On 05/02/24 10:10 pm, Jakob Haufe wrote: - GraphQL::RequiredImplementationMissingError (GitlabSchema.resolve_type(type, obj, ctx) must be implemented to use Union types, Interface types, or `loads:` (tried to resolve: Types::BoardType)): One thing I can think of is newer graphql gem.

Bug#1060658: [Debian-on-mobile-maintainers] Bug#1060658: megapixels don't start could not find any config file

On 16/01/24 10:01 pm, Arnaud Ferraris wrote: Hi, Le 12/01/2024 à 10:37, Pirate Praveen a écrit : Package: megapixels Version: 1.7.0-1 Severity: grave Running megapixels from commandline on mobian trixie fails with this error /usr/share/megapixels/config/purism,librem5r4.ini not found

Bug#1060797: Swutch to caddy from nginx+certbot

Package: diaspora-common version: 0.7.18.2+debian1 severity: wishlist caddy has built in support for https certificate management so less code for us to manage. caddy configuration file is simpler and has good defaults for security.

Bug#1060658: megapixels don't start could not find any config file

Package: megapixels Version: 1.7.0-1 Severity: grave Running megapixels from commandline on mobian trixie fails with this error /usr/share/megapixels/config/purism,librem5r4.ini not found.

Bug#1059710: [ruby-octokit 6 transition] Could not find 'o,ctokit' (~> 4.0, != 4.4.0) - did find: [octokit-6.1.1]

Package: ruby-jekyll-github-metadata Version: 2.15.0-1 Severity: important User: debian-r...@lists.debian.org Usertags: octokit6 Control: tags -1 fixed-upstream ruby-jekyll-gist autopkgtest and rebuild fails with ruby-octokit 6 from experimental Could not find 'octokit' (~> 4.0, != 4.4.0) - d

Bug#1059707: [ruby-octokit 6 transition] Could not find 'octokit' (~> 4.2) - did find: [octokit-6.1.1]

Package: ruby-jekyll-gist Version: 1.5.0-2 Severity: important User: debian-r...@lists.debian.org Usertags: octokit6 Control: forwarded -1 https://github.com/jekyll/jekyll-gist/issues/99 ruby-jekyll-gist autopkgtest fails with ruby-octokit 6 from experimental /usr/lib/ruby/vendor_ruby/rubygems/

Bug#1059338: Update database config for 15.9 -> 16.0 upgrade (current config is deprecated)

Package: gitlab Version: 16.4.4+ds1-1 severity: important Currently gitlab shows a warning during installation ██ ██  █  ██  ███  ██ ██ ███  ██  ██  ██ ██ ██   ██ ██   ██   ██ ██   ██ ██   ██  █  ██ ███ ██  ██ ██  ██ ██ 

Bug#958682: node-jsonld: Remove dependency to node-request

On Sun, 29 Oct 2023 21:37:08 +0100 Jonas Smedegaard wrote: Yes, I still want to work on node-jsonld - I will make time to look at this soon... yarnpkg 4.0.2 was recently uploaded to unstable, so this and node-matrix-js-sdk are the only remaining reverse dependencies for node-request. We have

Bug#1059337: RM: node-request-capture-har -- ROM; wrapper around deprecated node-request

Package: ftp.debian.org Severity: normal User: ftp.debian@packages.debian.org Usertags: remove X-Debbugs-Cc: node-request-capture-...@packages.debian.org Control: affects -1 + src:node-request-capture-har Control: block 1002901 by -1 Affected by rc bug #1002901 (yarnpkg no longer depend on th

Bug#1059097: RM: golang-github-libgit2-git2go-v34-dev -- ROM; unmaintained upstream and no longer needed

Package: ftp.debian.org Severity: normal User: ftp.debian@packages.debian.org Usertags: remove X-Debbugs-Cc: golang-github-libgit2-git...@packages.debian.org Control: affects -1 + src:golang-github-libgit2-git2go Control: block 1053799 by -1 This is affected by rc bug #1053799 (no upstream su

Bug#1058596: yarnpkg broken on bookworm - yarnpkg --help fails with TypeError: commander.on is not a function

Package: yarnpkg Version: 1.22.19+~cs24.27.18-2 severity: grave justification: breaks any options passed to yarnpkg yarnpkg install also fails with similar errors due to incompatible node-commander We should backport the patches in unstable to bookworm as well. # cat /usr/share/nodejs/yarn-er

Bug#1056298: riseup-vpn dns configuration don't work with systemd-resolved

On 20/11/23 5:33 PM, Nilesh Patra wrote: I need something that I could reproduce to be able to further check. looks like none of the servers at https://servers.opennic.org/ that advertise DoT support works though https://servers.opennic.org/edit.php?srv=ns5.id.dns.opennic.glue was working w

Bug#1056298: riseup-vpn dns configuration don't work with systemd-resolved

Control: retitle -1 DNSOverTLS=yes in systemd-resolved conf breaks riseup-vpn dns On 20/11/23 3:29 PM, Nilesh Patra wrote: I do not have this installed however riseup-vpn works for me without any issues. Others who have tested this package on bookworm in the past also did not have any such issu

Bug#1056298: riseup-vpn dns configuration don't work with systemd-resolved

package: riseup-vpn severity: grave version: 0.21.11+ds1-5+b4 It misses a dependency on openvpn-systemd-resolved and on boomworm it was working after installing it. But on mobian trixie, which has systemd-resolved installed by default (through mobian-base), dns resolution fails when riseup vpn

Bug#1055880: kaidan missing two dependencies

Package: kaidan version: 0.9.1-1 severity: grave justification: fails to start Though fix is easy, missing dependencies are qml-module-org-kde-kquickimageeditor and qml-module-org-kde-kirigami-addons-labs-mobileform After installing these manually, kaidan starts as expected.

Bug#958692: node-matrix-js-sdk: Remove dependency to node-request

On 2/11/23 10:27 PM, Hubert Chathi wrote: On Sun, 29 Oct 2023 22:43:55 +0530, Praveen Arimbrathodiyil said: On Fri, 24 Apr 2020 13:52:39 +0200 y...@debian.org wrote: Upstream has deprecated node-request: https://github.com/request/request/issues/3142 It can be replaced by node-got Hi J

Bug#940511: [Pkg-javascript-devel] Bug#940511: Our mutual interest in /usr/bin/yarn

On Mon, 21 Nov 2022 09:39:31 +0100 "Yadd" wrote: I don't think that "Provides: yarn" is a good thing here since "/usr/bin/yarn" isn't provided by yarnpkg. "Provides: node-yarn" seems enough here and without any consequences. As a compromise, can we have a debconf prompt to notify users about

Bug#969177: debmake: cannot create deb for nodejs modeule

On Sat, Oct 28 2023 at 15:34:43 +09:00:00, Osamu Aoki wrote: Hi, On Fri, 2023-10-27 at 20:59 +0530, Pirate Praveen wrote: On 27/10/23 8:12 PM, Osamu Aoki wrote: > Hi, ... > Can you elaborate what do you mean by > > Though after this it'd take some effort to ed

Bug#969177: debmake: cannot create deb for nodejs modeule

On 27/10/23 8:12 PM, Osamu Aoki wrote: Hi, Thanks for the patch. I committed to salsa. Can you elaborate what do you mean by Though after this it'd take some effort to edit source package name. Maybe, we can work together to fix it. Please understand I have no idea on the nodejs package

Bug#1054544: community.zabbix plugin misses bookworm support and fails with error dict object' has no attribute 'bookworm'

package: anisble severity: important version: 7.3.0+dfsg-1 : FAILED! => {"msg": "The task includes an option with an undefined variable. The error was: 'dict object' has no attribute 'bookworm'. 'dict object' has no attribute 'bookworm'\n\nThe error appears to be in '/usr/lib/python3/dist-pack

Bug#1053747: [Debian-on-mobile-maintainers] Bug#1053747: Bug#1053747: Upload phosh to bookworm-backports ?

On Sat, Oct 14 2023 at 18:26:58 +02:00:00, Guido Günther wrote: Hi, On Fri, Oct 13, 2023 at 09:13:39PM +0530, Pirate Praveen via Debian-on-mobile-maintainers wrote: On Tue, 10 Oct 2023 23:56:54 +0200 Arnaud Ferraris mailto:aferra...@debian.org>> wrote: > Hi, > > Le 10/

Bug#1053747: [Debian-on-mobile-maintainers] Bug#1053747: Upload phosh to bookworm-backports ?

On Wed, 11 Oct 2023 11:07:57 +0200 Guido =?iso-8859-1?Q?G=FCnther?= wrote: > Hi Praveen, > I'm always in favour of providing newer phosh to users but see below for details: > > On Tue, Oct 10, 2023 at 02:33:52PM +0530, Pirate Praveen via Debian-on-mobile-maintainers wr

Bug#1053747: [Debian-on-mobile-maintainers] Bug#1053747: Upload phosh to bookworm-backports ?

On Tue, 10 Oct 2023 23:56:54 +0200 Arnaud Ferraris wrote: > Hi, > > Le 10/10/2023 à 11:03, Pirate Praveen via Debian-on-mobile-maintainers a > écrit : > > Package: phosh > > Version: 0.32.0-1 > > Severity: wishlist > > > > I think it'd be a g

Bug#1053755: origtargz should fallback to gbp export-orig if pristine-tar checkout fails

Package: devscripts Version: 2.23.4 Severity: important An example where this currently fails is g...@salsa.debian.org:gnome-team/glib.git I have noticed this with multiple repositories, usually when there is more than one orig.tar files pravi@ilvala2:~/forge/gnome-team/glib$ origtargz pris

Bug#1053747: Upload phosh to bookworm-backports ?

Package: phosh Version: 0.32.0-1 Severity: wishlist I think it'd be a good idea to provide new versions of phosh (with phoc, wlroots, feedbackd) via bookworm-backports. I was earlier daily driving mobian trixie on my Librem 5 but since its automatic suspend broke I could not continue using it

Bug#1052469: default resolution is too high, fonts too small

package: plasma-mobile version: 5.27.6-1 severity: important With recent apt dist-upgrade the default resolution of plasma mobile is too high and applications open in desktop mode. This was working earlier, I wonder if mobian has some patches to set correct resolution.

Bug#1052216: plasma-mobile should depend on plasma-dialer

On Thu, 21 Sep 2023 19:32:46 +0200 Marco Mattiolo wrote: Hi, thank you for reporting. For the point of plasma-mobile not depending on plasma-dialer, I'm sorry that's a "wontfix": there are usecases (e.g. tablet) where plasma-mobile can be used without plasma-dialer, then it makes no sense fo

Bug#1052216: plasma-mobile should depend on plasma-dialer

package: plasma-mobile version: 5.27.6-1 severity: important I have just installed plasma-mobile on debian trixie (mobian) on librem 5 but it did not install plasma-dialer, I think this should be in depends as otherwise we have to use gnome calls which does not integrate well with plasma mobile

Bug#1049343:

On 15/08/23 1:08 am, Nicolas Godet wrote: Hi,  Same bug during Debian upgrade from 11 to 12 today. Could be linked to google protobuf 3.24.0. Another user on IRC d

Bug#1042967: nheko crashes on first launch in arm64 (librem 5)

Package: nheko Version: 0.11.3-2+b1 severity: grave justification: makes the app unusable I initially noticed this on mobian bookworm (then I switched to chatty). Now I can reliable reproduce it on trixie as well. Crash log attached. To reproduce rm -rf .local/share/nheko .config/nheko .cache

Bug#1025090: ruby-gh fails to rebuild on updating ruby-faraday

On Sun, 18 Jun 2023 15:28:38 +0530 Pirate Praveen wrote: > Reported upstream https://github.com/travis-ci/gh/issues/46 I'm planning to upload ruby-faraday 2.0 to unstable around 1st August.

Bug#1025078: ruby-puppet-forge breaks after updating ruby-faraday to new upstream

On Sun, 18 Jun 2023 15:51:36 +0530 Pirate Praveen wrote: > Upstream now support faraday 2.0 > https://github.com/puppetlabs/forge-ruby/commit/06102bc9478d9d19fbe12b505639fb253d29ba54 I'm planning to upload ruby-faraday 2.0 to unstable around 1st August.

Bug#1041067: RM: ruby-ms-rest -- ROM; unmaintained upstream, rc buggy

Package: ftp.debian.org Severity: normal User: ftp.debian@packages.debian.org Usertags: remove X-Debbugs-Cc: ruby-ms-r...@packages.debian.org Control: affects -1 + src:ruby-ms-rest Control: block -1 by 1041065 It is unmaintained upstream and incompatible with ruby-faraday 2.0. This was packa

Bug#1041065: RM: ruby-ms-rest-azure -- ROM; unmaintained upstream, rc buggy

Package: ftp.debian.org Severity: normal User: ftp.debian@packages.debian.org Usertags: remove X-Debbugs-Cc: ruby-ms-rest-az...@packages.debian.org Control: affects -1 + src:ruby-ms-rest-azure ruby-ms-rest-azure is affected by rc bug #1037994 (incompatible with ruby-faraday 2.0) and is unmai

Bug#1037994: retitle and add forwarded

Control: reassign -1 ruby-ms-rest-azure On Sun, 18 Jun 2023 12:31:50 +0530 Pirate Praveen wrote: > Control: forwarded -1 > https://gitlab.com/gitlab-org/ruby/gems/gitlab-fog-azure-rm/-/issues/3 > Control: retitle -1 ruby-ms-rest-azure ftbfs with ruby-faraday 2.0 Also reass

Bug#1030932: golang-github-go-enry-go-license-detector: FTBFS on mipsel: test failures

Control: fixed -1 4.3.0+git20221007.a3a1cc6-3 On Thu, 13 Jul 2023 23:49:56 +0800 Shengjing Zhu wrote: > You look at the wrong log, it's golang-github-hhatto-gorst, not > golang-github-go-enry-go-license-detector. > It FTBFS on buildd currently. After increasing the timeout to 150m, the build

Bug#1030932: golang-github-go-enry-go-license-detector: FTBFS on mipsel: test failures

On Thu, Jul 13 2023 at 11:49:56 PM +08:00:00 +08:00:00, Shengjing Zhu wrote: Control: reopen -1 Thanks, I noticed the failure on buildd and was going to reopen it and found you did it aready. Hi, On Thu, Jul 13, 2023 at 6:09 PM Pirate Praveen wrote: On Thu, 9 Feb 2023 14:40:48

Bug#1030955: golang-github-hhatto-gorst: autopkgtest failure

On Thu, 13 Jul 2023 21:24:53 +0530 Nilesh Patra wrote: > Control: tags -1 patch > > On Thu, Jul 13, 2023 at 03:10:40PM +0530, Pirate Praveen wrote: > > On Fri, 10 Feb 2023 00:07:51 +0200 Adrian Bunk wrote: > > > The Ubuntu diff contains a patch that looks like

Bug#1030955: golang-github-hhatto-gorst: autopkgtest failure

On Fri, 10 Feb 2023 00:07:51 +0200 Adrian Bunk wrote: > The Ubuntu diff contains a patch that looks like a workaround (untested). This patch says data directory is reserved for golang autopkgtest in Ubuntu. Is this the same on debian too? If yes, that looks like a bad idea to me.

Bug#1034565: fixed in 0.23

Control: fixed -1 0.23.1-3

Bug#1040819: gitlab postinst fails with gem version number parsing error

On 11/07/23 10:34 am, Jakob Bohm wrote: Package: gitlab Version: 15.10.8+ds1-1~fto12+1 Severity: normal Dear Maintainer, When trying to install gitlab (fasttrack) in a mostly blank bookworm VM, postinst fails with the following messages: Setting up gitlab (15.10.8+ds1-1~fto12+1) ... Co

Bug#1040834: RM: ruby-fission -- ROM; rc buggy, abandoned upstream

Package: ftp.debian.org Severity: normal User: ftp.debian@packages.debian.org Usertags: remove X-Debbugs-Cc: ruby-fiss...@packages.debian.org Control: affects -1 + src:ruby-fission Control: block 1040054 by -1 Control: block -1 by 1040831 Control: affects ruby-cfpropertylist This is affected

Bug#1040831: RM: ruby-fog-vmfusion -- ROM; abandoned upstream, leaf package

Package: ftp.debian.org Severity: normal User: ftp.debian@packages.debian.org Usertags: remove X-Debbugs-Cc: ruby-fog-vmfus...@packages.debian.org Control: affects -1 + src:ruby-fog-vmfusion This was originally packaged for gitlab, but no longer required. It is abandoned upstream (last commi

Bug#1040772: RM: golang-gitaly-proto -- ROM; rc-buggy, no longer needed for gitlab-shell

Package: ftp.debian.org Severity: normal User: ftp.debian@packages.debian.org Usertags: remove X-Debbugs-Cc: golang-gitaly-pr...@packages.debian.org Control: affects -1 + src:golang-gitaly-proto Control: affects -1 + src:golang-gitaly-proto Control: block 1033705 by -1 Affected by rc bug #103

Bug#1034565: ftbfs tests fail on ppc64el and mips64el

On Tue, 18 Apr 2023 17:08:34 +0530 Pirate Praveen wrote: > Failures: > >1) Prometheus::Client::Helper::MmapedFile file does not exist creates > a file with minimum initial size > Failure/Error: expect(File.size(subject.filepath)).to > eq(subject.send(:init

Bug#1039916: ruby-derailed-benchmarks: autopkgtest needs update for new version of ruby-memory-profiler: Could not find 'memory_profiler' (~> 0)

On Thu, 29 Jun 2023 16:03:13 +0200 Paul Gevers wrote: > ┌──┐ > 19s │ Checking Rubygems dependency resolution on ruby3.1 > │ > 19s > └──

Bug#1033705: golang-gitaly-proto: autopkgtest regression: test dependency ruby-gitaly-proto doesn't exist

On Thu, 30 Mar 2023 19:19:44 +0200 Paul Gevers wrote: > autopkgtest [15:18:15]: test command1: preparing testbed > Reading package lists... > Building dependency tree... > Reading state information... > Correcting dependencies...Starting pkgProblemResolver with broken count: 1 > Starting 2 pkg

Bug#1039915: ruby-benchmark-memory: autopkgtest needs update for new version of ruby-memory-profiler: Could not find 'memory_profiler' (~> 0.9)

Control: fixed -1 0.2.0-1 On Thu, 29 Jun 2023 16:01:57 +0200 Paul Gevers wrote: > Currently this regression is blocking the migration of > ruby-memory-profiler to testing [1]. Of course, ruby-memory-profiler > shouldn't just break your autopkgtest (or even worse, your package), but > it seems

Bug#961595: ruby-gollum-lib: please package new upstream release 5.x

Control: block 1040461 by -1 On Tue, 26 May 2020 14:55:28 +0200 Jonas Smedegaard wrote: > gollum-lib 5.x has been out for a few months, with several exciting new > features. > > Please consider upgrading to that new release. ruby-gollum-lib was originally packaged as a dependency of gitaly an

Bug#1040405: ruby-gollum-lib: incompatible with newer ruby-rouge

On Wed, 5 Jul 2023 16:44:31 +0200 Gianfranco Costamagna wrote: > Can you please have a look? We no longer need ruby-gollum-lib for gitaly, so requested removal of ruby-gollum-lib in #1040461.

Bug#1040466: RM: gitaly [armel i386] -- NVIU; older version and blocking removal of ruby-gollum-lib

Package: ftp.debian.org Severity: normal User: ftp.debian@packages.debian.org Usertags: remove X-Debbugs-Cc: git...@packages.debian.org Control: affects -1 + src:gitaly Control: block 1040461 by -1 ruby-gollum-lib is no longer a dependency of gitaly in newer versions. Removing gitaly from ar

Bug#1040461: RM: ruby-gollum-lib -- ROM; incompatible with newer ruby-rouge

Package: ftp.debian.org Severity: normal User: ftp.debian@packages.debian.org Usertags: remove X-Debbugs-Cc: ruby-gollum-...@packages.debian.org Control: affects -1 + src:ruby-gollum-lib Control: block 1040405 by -1 Please remove ruby-gollum-lib from the archive. It is affected by rc bug #10

Bug#1025075: faraday-typhoeus adapter to support faraday 2.0

Control: forwarded -1 https://github.com/typhoeus/typhoeus/issues/717 On Sat, 10 Dec 2022 00:33:23 +0530 Vinay wrote: > Since this is an upstream issue we need to wait until typhoeus updates > to faraday 2.0 > > https://github.com/typhoeus/typhoeus/issues/686 > > faraday-typhoeus 2 adapter fo

Bug#1038773: ITP: ruby-faraday-net-http-persistent -- Faraday adapter for NetHttpPersistent

Package: wnpp Severity: wishlist Owner: Pirate Praveen Control: block 1025095 by -1 ruby-azure-storage-common needs this for ruby-faraday 2.0 support.

Bug#1038632: ITP: ruby-faraday-follow-redirects -- Faraday 2.x compatible extraction of FaradayMiddleware::FollowRedirects

Package: wnpp Severity: wishlist Owner: Pirate Praveen Control: block 1025097 by -1 ruby-asana new update needs this gem along with ruby-faraday 2.0

Bug#1035307: Update ruby-ruby-parser to 3.20.x

Control: clone -1 -2 Control: retitle -2 update ruby-sexp-processor to 4.17 Control: reassign -2 ruby-sexp-processor On Sun, 30 Apr 2023 20:35:00 +0530 Praveen Arimbrathodiyil wrote: > Package: ruby-ruby-parser > Version: 3.19.2-1 > Severity: important > > Gitlab 15.11.0 needs ruby-ruby-parser

Bug#1037963: rabbit ftbfs/autopkgtest failure with ruby-faraday 2.7 in experimental

Control: forwarded -1 https://github.com/rabbit-shocker/rabbit/issues/151 On Thu, 15 Jun 2023 01:18:17 +0530 Pirate Praveen wrote: > > Started >

Bug#1025078: ruby-puppet-forge breaks after updating ruby-faraday to new upstream

Control: tags -1 patch On Tue, 29 Nov 2022 22:30:43 +0530 Vinay wrote: > ruby3.0 -e gem\ \"puppet_forge\" > /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:2248:in > `raise_if_conflicts': Unable to activate faraday_middleware-1.0.0, > because faraday-2.7.1 conflicts with faraday (~> 1.0)

Bug#1025090: ruby-gh fails to rebuild on updating ruby-faraday

Control: forwarded -1 https://github.com/travis-ci/gh/issues/46 On Tue, 29 Nov 2022 23:56:38 +0530 Vinay wrote: > /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1413:in `rescue in > block in activate_dependencies': Could not find 'faraday' (~> 1.0) among Reported upstream https://githu

Bug#1025085: ruby-google-cloud-translate breaks after updating ruby-faraday

On Tue, 29 Nov 2022 23:38:44 +0530 Vinay wrote: > The following packages have unmet dependencies: > sbuild-build-depends-main-dummy : Depends: ruby-googleauth (< 0.10.0) > but 0.13.0-3 is to be installed This is a leaf package and we can remove it. Seems to be replaced by google-cloud-tran

Bug#1025095: ruby-azure-storage-common fails to rebuild after new upstream of ruby-faraday

Control: forwarded -1 https://github.com/Azure/azure-storage-ruby/issues/227 Control: tags -1 patch On Wed, 30 Nov 2022 00:12:19 +0530 Vinay wrote: > /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1413:in `rescue in > block in activate_dependencies': Could not find 'faraday' (~> 1.0) am

Bug#1025084: ruby-graphlient fails to rebuild after updating ruby-faraday to upstream

On Sun, Jun 18 2023 at 01:09:36 PM +05:30:00 +05:30:00, Pirate Praveen wrote: On Tue, 29 Nov 2022 23:33:01 +0530 Vinay wrote: > `raise_if_conflicts': Unable to activate faraday_middleware-1.0.0, > because faraday-2.7.1 conflicts with faraday (~> 1.0) (Gem::ConflictError)

Bug#1025084: ruby-graphlient fails to rebuild after updating ruby-faraday to upstream

On Tue, 29 Nov 2022 23:33:01 +0530 Vinay wrote: > `raise_if_conflicts': Unable to activate faraday_middleware-1.0.0, > because faraday-2.7.1 conflicts with faraday (~> 1.0) (Gem::ConflictError) This seems to be caused by ruby-faraday-middleware.

Bug#1037994: retitle and add forwarded

Control: forwarded -1 https://gitlab.com/gitlab-org/ruby/gems/gitlab-fog-azure-rm/-/issues/3 Control: retitle -1 ruby-ms-rest-azure ftbfs with ruby-faraday 2.0 this is unmaintained so should be removed (along with ruby-ms-rest). See https://gitlab.com/gitlab-org/ruby/gems/gitlab-fog-azure-rm/-/i

Bug#1038428: ITP: ruby-faraday-multipart -- Perform multipart-post requests using Faraday

Package: wnpp Severity: wishlist Owner: Pirate Praveen Control: block 1025097 by -1 ruby-asana new update needs this gem along with ruby-faraday 2.0

Bug#1037465: redmine autopkgtest fails with ruby-rouge 4.1 in experimental

On Tue, 13 Jun 2023 13:03:19 +0530 Pirate Praveen wrote: > Package: redmine > Version: 5.0.4-5 > Severity: important > > Redmine is not compatible with ruby-rouge 4.1 in experimental. > autopkgtest fails with > > Could not find gem 'rouge (~> 3.28)'

Bug#1038380: ITP: ruby-faraday-retry -- Catches exceptions and retries each request a limited number of times

Package: wnpp Severity: wishlist Owner: Pirate Praveen Control: block 1025098 by -1 ruby-acme-client new update needs this gem along with ruby-faraday 2.0 OpenPGP_0x8F53E0193B294B75.asc Description: OpenPGP public key OpenPGP_signature Description: OpenPGP digital signature

Bug#1037992: ruby-ms-rest-azure fails similarly

Control: clone 1037992 -1

Bug#1037992: ruby-ms-rest ftbfs with ruby-faraday 2.x in experimental

Package: ruby-ms-rest Version: Severity: important The following packages have unmet dependencies: sbuild-build-depends-main-dummy : Depends: ruby-faraday (< 2.0.0) but 2.7.1-1 is to be installed E: Unable to correct problems, you have held broken packages. apt-get failed. I'd like to upload

Bug#1025097: ruby-asana fails to rebuild after new upstream of ruby-faraday

On Wed, 30 Nov 2022 00:16:43 +0530 Vinay wrote: > /usr/lib/ruby/vendor_ruby/rubygems/dependency.rb:313:in `to_specs': > Could not find 'faraday' (>= 0.8, < 2.0) - did find: [faraday-2.7.1] > (Gem::MissingSpecVersionError) There is an upstream PR that adds faraday 2.0 support https://github.com

Bug#1037963: rabbit ftbfs/autopkgtest failure with ruby-faraday 2.7 in experimental

Package: rabbit Version: 3.0.0-5 Severity: important Full log attached Started E === Error: test_upload(TestSlideShare): Faraday::Error: :multipart is n

Bug#1037469: ruby-kramdown-parser-gfm ftbfs with ruby-rouge 4.1 in experimental

Package: ruby-kramdown-parser-gfm Version: 1.1.0-2 Severity: important I'd like to upload ruby-rouge 4.1 to unstable soon. 1) Failure: TestFiles#test_gfm_codeblock_fenced_to_html [/tmp/autopkgtest-lxc.r0kgad0i/downtmp/build.yfB/src/test/test_files.rb:32]: --- expected +++ actual @@ -16,6 +16,

Bug#1037467: ruby-gollum-lib not compatible with ruby-rouge 4.1

Package: ruby-gollum-lib Version: 4.2.7.10~gitlab.2+dfsg-1 Severity: important /usr/lib/ruby/vendor_ruby/rubygems/dependency.rb:313:in `to_specs': Could not find 'rouge' (~> 3.1) - did find: [rouge-4.1.0] full log attached. I'd like to reupload ruby-rouge 4.1 to unstable soon. autopkgtest [13

Bug#1037409: golang-golang-x-exp ftbfs with gccgo-go (both gccgo-12 and gccgo-13)

Package: src:golang-golang-x-exp Version: 0.0~git20221028.83b7d23-2 Severity: serious Building with golang-any changed to gccgo-go to force gccgo on amd64, build fails with error. Full build log attached. Either this should be fixed or dependency should be updated to golang-go instead of golang

Bug#1021583: golang-gitlab-gitlab-org-labkit: FTBFS (test failure): gitlab.com/gitlab-org/labkit/metrics/http_round_tripper

Control: fixed -1 1.17.0-1 On Tue, 11 Oct 2022 13:24:32 +0200 Cyril Brulebois wrote: > Source: golang-gitlab-gitlab-org-labkit > Version: 1.16.0-1 > Severity: serious > Justification: FTBFS > > Hi, > > While preparing an update for the golang-github-gin-gonic-gin package, > I noticed golang-

Bug#1037319: nomad ftbfs with newer golang-github-hashicorp-yamux-dev in experimental

Control: severity -1 serious On Sun, 11 Jun 2023 15:33:56 +0530 Pirate Praveen wrote: > I'd like to upload this version to unstable soon. Though this package > seems to not in a good shape otherwise, not in testing and last upload > in 2021-07-10. > Since all other reverse

Bug#1036558: Update kaidan to new upstream release 0.9.1

Package: kaidan Version: 0.8.0-2 Severity: wishlist Kaidan 0.9.1 is now available with end to end encryption support. Please update the version in the archive (it could be uploaded to experimental till bookworm is out). Currently I use the flatpak version, but would love to use the native pack

  1   2   3   4   5   6   7   8   9   10   >