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

2024-02-10 Thread Pirate Praveen

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-faraday 2 is in unstable now.


Fixed in ruby-graphlient 0.7.0



Bug#1063658: drop snowlow-tracker orig tar

2024-02-10 Thread Pirate Praveen

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 and covered by yarn install in postinst.




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

2024-02-10 Thread Pirate Praveen

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 dependency 
in last upload and it has no other reverse dependencies.




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

2024-02-10 Thread Pirate Praveen

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/exAspArk/graphql-errors has a banner "This repository 
has been archived by the owner on Apr 8, 2020. It is now read-only."


This was originally packaged as build dependency for ruby-graphlient 
which no longer needs it.




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

2024-02-09 Thread Pirate Praveen
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/pull/1203




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

2024-02-09 Thread Pirate Praveen

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 stage 
so rake assets:precompile can still find it.


So it looks like gem2deb test is working as expected, but we still need 
to figure out a way out for symlinks. May be we should just link them in 
the build target itself as a solution. If that is the recommended 
solution, we can close this bug with a note in dh_ruby documentation.




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

2024-02-09 Thread Pirate Praveen

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, the test is passing 
even with a broken symbolic link.


Try building master branch which has this commit
https://salsa.debian.org/ruby-team/ruby-rails-assets-underscore/-/commit/194c526208b3be29870f745d9ac0bfbc9af6d66c

Without libjs-underscore in build depends, the test should fail, but it 
is passing.




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

2024-02-08 Thread Pirate Praveen

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 not yet run when this test is run.


Details here https://lists.debian.org/debian-ruby/2024/02/msg6.html

So I think we have a few options,

1. Run this only as an autopkgtest (like how it is currently done) which 
will have the links

2. Run this tests after dh_link is done
3. Manually run dh_link before this test

To reproduce this bug, you can build this branch 
https://salsa.debian.org/ruby-team/ruby-jquery-rails/-/tree/debian-tests-assets?ref_type=heads




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

2024-02-07 Thread Pirate Praveen

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(described_class::LOCATION).to 
eq('location') }


   expected: "location"
got: "Location"

   (compared using ==)
 # ./spec/integration/rack/v3/headers_spec.rb:5:in `block (2 
levels) in '


  2) Grape::Http::Headers is expected to eq "allow"
 Failure/Error: it { expect(described_class::ALLOW).to eq('allow') }

   expected: "allow"
got: "Allow"

   (compared using ==)
 # ./spec/integration/rack/v3/headers_spec.rb:4:in `block (2 
levels) in '


  3) Grape::Http::Headers is expected to eq "x-cascade"
 Failure/Error: it { expect(described_class::X_CASCADE).to 
eq('x-cascade') }


   expected: "x-cascade"
got: "X-Cascade"

   (compared using ==)
 # ./spec/integration/rack/v3/headers_spec.rb:7:in `block (2 
levels) in '


  4) Grape::Http::Headers is expected to eq "transfer-encoding"
 Failure/Error: it { expect(described_class::TRANSFER_ENCODING).to 
eq('transfer-encoding') }


   expected: "transfer-encoding"
got: "Transfer-Encoding"

   (compared using ==)
 # ./spec/integration/rack/v3/headers_spec.rb:6:in `block (2 
levels) in '


Finished in 7.29 seconds (files took 1.68 seconds to load)
2171 examples, 4 failures, 1 pending

Failed examples:

rspec ./spec/integration/rack/v3/headers_spec.rb:5 # 
Grape::Http::Headers is expected to eq "location"
rspec ./spec/integration/rack/v3/headers_spec.rb:4 # 
Grape::Http::Headers is expected to eq "allow"
rspec ./spec/integration/rack/v3/headers_spec.rb:7 # 
Grape::Http::Headers is expected to eq "x-cascade"
rspec ./spec/integration/rack/v3/headers_spec.rb:6 # 
Grape::Http::Headers is expected to eq "transfer-encoding"


Randomized with seed 42165



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

2024-02-05 Thread Pirate Praveen




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 locks to 2.0.27.


This is merged upstream, can you try if this patch fixes it?

https://gitlab.com/gitlab-org/gitlab/-/merge_requests/134851



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

2024-02-05 Thread Pirate Praveen




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. See if manually 
installing [1] graphql 2.0.27 fixes it.


[1] 
https://wiki.debian.org/gitlab/troubleshooting#manually_installing_ruby_dependencies




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

2024-01-17 Thread Pirate Praveen




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.


This is expected, megapixels doesn't support the L5 (yet?).


I was looking at a blog post for QR code readers and mega pixel was 
mentioned


https://forums.puri.sm/t/qr-code-scanning-via-megapixels/14408

Found another reference now https://blog.brixit.nl/megapixels-2-0/

but seems this never finished.



Bug#1060797: Swutch to caddy from nginx+certbot

2024-01-14 Thread Pirate Praveen

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

2024-01-12 Thread Pirate Praveen

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]

2023-12-30 Thread Pirate Praveen

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) - did find: 
[octokit-6.1.1]  (Gem::MissingSpecVersionError)


Please update the package to make way for ruby-octokit 6 reupload to 
unstable.


It is already fixed upstream, so a simple upstream update would be 
enough to fix this


https://github.com/jekyll/github-metadata/blob/a605d047566c5cb22a7f549d9fad590724d1ba98/jekyll-github-metadata.gemspec



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

2023-12-30 Thread Pirate Praveen

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/dependency.rb:317:in `to_specs': 
Could not find 'octokit' (~> 4.2) - did find: [octokit-6.1.1] 
(Gem::MissingSpecVersionError)


Please update the package to make way for ruby-octokit 6 reupload to 
unstable.


It is probably fine to just patch it and relax the requirements, as 
breaking changes in 5.0 and 6.0 are probably not affecting this package 
as explained in https://github.com/jekyll/jekyll-gist/issues/99




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

2023-12-22 Thread Pirate Praveen

Package: gitlab
Version: 16.4.4+ds1-1
severity: important

Currently gitlab shows a warning during installation

  ██ ██  █  ██  ███    ██ ██ ███    ██  ██ 
  ██ ██ ██   ██ ██   ██    ██ ██    ██ ██  
  ██  █  ██ ███ ██  ██ ██  ██ ██ ██ ██  ██ ██   ███ 
  ██ ███ ██ ██   ██ ██   ██ ██  ██ ██ ██ ██  ██ ██ ██    ██ 
   ███ ███  ██   ██ ██   ██ ██    ██ ██     ██  

**
  Your database has a single connection, and single connections were
  deprecated in GitLab 15.9 
https://docs.gitlab.com/ee/update/deprecations.html#single-dat

abase-connection-is-deprecated.

  Please add a :ci section to your database, following these instructions:

https://docs.gitlab.com/ee/install/installation.html#configure-gitlab-db-settings.
**

We should follow the instructions to update the configuration.



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

2023-12-22 Thread Pirate Praveen

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 an ack from its maintainer to remove it 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958692#42 so this is 
the only real blocker remaining to remove node-request.




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

2023-12-22 Thread Pirate Praveen

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 this library 
from version 4.0.2 in unstable).




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

2023-12-20 Thread Pirate Praveen

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 support for latest 
libgit2). This was originally packaged as a build dependency of gitaly 
which has removed its dependency from 16.4




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

2023-12-13 Thread Pirate Praveen

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-error.log
Arguments:
  /usr/bin/node /usr/bin/yarnpkg --help

PATH:
  /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin

Yarn version:
  1.22.19

Node version:
  18.13.0

Platform:
  linux x64

Trace:
  TypeError: commander.on is not a function
  at Object.run (/usr/share/nodejs/yarn/lib/cli/commands/help.js:75:13)
  at run (/usr/share/nodejs/yarn/lib/cli/index.js:494:30)
  at /usr/share/nodejs/yarn/lib/cli/index.js:732:24

npm manifest:
  No manifest

yarn manifest:
  No manifest

Lockfile:
  No lockfile


# yarnpkg --frozen-lockfile install
TypeError: _commander(...).default.optionFor is not a function
at /usr/share/nodejs/yarn/lib/cli/index.js:355:88
at Array.findIndex ()
at _callee$ (/usr/share/nodejs/yarn/lib/cli/index.js:352:38)
at tryCatch 
(/usr/share/nodejs/@babel/runtime/helpers/regeneratorRuntime.js:44:17)
at Generator. 
(/usr/share/nodejs/@babel/runtime/helpers/regeneratorRuntime.js:125:22)
at Generator.next 
(/usr/share/nodejs/@babel/runtime/helpers/regeneratorRuntime.js:69:21)
at asyncGeneratorStep 
(/usr/share/nodejs/@babel/runtime/helpers/asyncToGenerator.js:3:24)
at _next 
(/usr/share/nodejs/@babel/runtime/helpers/asyncToGenerator.js:22:9)

at /usr/share/nodejs/@babel/runtime/helpers/asyncToGenerator.js:27:7
at new Promise ()



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

2023-11-20 Thread Pirate Praveen

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 with Android Private DNS setting. So probably a bug with 
systemd-resolved.




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

2023-11-20 Thread Pirate Praveen
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 issues.


This dependency is needed if you are running systemd-resolved only, so 
this would be a problem only for people with systemd-resolved installed.



I tried with systemd-resolved installed without openvpn-systemd-resolved
install - no problems observed.


hmm, I got it to work with a plain openvpn connection only with this 
installed. I don't remember if I tested riseup-vpn without it.



But on mobian trixie, which has
systemd-resolved installed by default (through mobian-base), dns
resolution fails when riseup vpn is connected.


I do not have a device to try out mobian. I tried it on debian
trixie/testing with openvpn-system-resolved and I do not see any such
issue.


;; communications error to 127.0.0.53#53: timed out
;; communications error to 127.0.0.53#53: timed out
;; no servers could be reached


OTOH, this log has very superficial info and is not helpful into
debugging if there's even anything wrong with riseup-vpn.

The error comes only when riseup-vpn is running. When it is turned off 
the DNS works as expected.



This maybe a setup/configuration issue for your system. I did find a
similar issue on the systemd repository itself[1] and the fix was to add
in a "DNS=" entry in resolved.conf. Can you try this and report back?


I already have DNS= 103.87.68.194 (opennic.org dns resolver) set to and 
FallbackDNS=9.9.9.9


I also had DNSOverTLS=yes. After disabling this host command works.


Could you also check this on a different network connection?

[1]: https://github.com/systemd/systemd/issues/25397

Best,
Nilesh




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

2023-11-19 Thread Pirate Praveen

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 is connected.


error log attached



;; communications error to 127.0.0.53#53: timed out
;; communications error to 127.0.0.53#53: timed out
;; no servers could be reached



Bug#1055880: kaidan missing two dependencies

2023-11-13 Thread Pirate Praveen

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

2023-11-02 Thread Pirate Praveen




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 Jonas, Hubert,



Are you planning to update matrix-js-sdk? We'd like to remove
deprecated node-request from the archive and this package is a
blocker.


I don't currently have time to update matrix-js-sdk.  Feel free to
remove it from testing so that it doesn't block anything else.  I can
always upload a new version later.



This is already not in testing for 525 days. We can't remove a package 
from the archive if any package (build) depends on it.




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

2023-10-29 Thread Pirate Praveen

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 this 
conflict and to run


sudo ln -s /usr/bin/yarnpkg /usr/bin/yarn

if they want to use yarn command.

Automating this via a postinst may be a good idea too, but not sure if 
that is allowed by policy. May be we can ask for an exception since this 
is a special case. This way people who want to use yarn command has a 
way to do it easily.


Prompting users is a bad idea in general if we can have good defaults, 
but we don't have much options left here.


OpenPGP_signature.asc
Description: OpenPGP digital signature


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

2023-10-29 Thread Pirate Praveen



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 edit source package 
name.

 >
 > Maybe, we can work together to fix it.  Please understand I have 
no idea on

 > the nodejs package name conventions.

 May be looking for a package.json or package.yaml file in the source
 directory would be a better thing to detect a nodejs package.



Currently, I have 'src/debmake/analyze.py' containing:


 # Javascript nodejs
 elif os.path.isfile("package.json"):
 para["build_type"] = "nodejs"
 para["dh_with"].update({"nodejs"})
 para["build_depends"].update({"pkg-js-tools"})



Should I do:
# Javascript nodejs
elif os.path.isfile("package.json") or 
os.path.isfile("package.yaml"):

para["build_type"] = "nodejs"
para["dh_with"].update({"nodejs"})
para["build_depends"].update({"pkg-js-tools"})


As you noted in subsequent comment, we can skip package.yaml. Build 
depends can be dh-sequence-nodejs instead of pkg-js-tools (npm2deb did 
that switch).


If dh-sequence-nodejs is in Build Deps then we don't need to add --with 
nodejs to dh as well.


Regards,

Osamu




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

2023-10-27 Thread Pirate Praveen




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 name conventions.


May be looking for a package.json or package.yaml file in the source 
directory would be a better thing to detect a nodejs package.




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

2023-10-25 Thread Pirate Praveen

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-packages/ansible_collections/community/zabbix/roles/zabbix_server/tasks/Debian.yml': 
line 86, column 3, but may\nbe elsewhere in the file depending on the 
exact syntax problem.\n\nThe offending line appears to be:\n\n\n- name: 
\"Debian | Install gpg key\"\n  ^ here\n"}


I can see a newer commit adding support

https://github.com/ansible-collections/community.zabbix/commit/9856769381625c7994c33a07b7e27a277f8bea86#diff-c1a1a767b71f8dcff0bb354327aba87b4b1885711f107a2b8ecb58fce7992697

It is kind of a chicken and egg problem to include bookworm support in 
bookworm first release. But I think we can include a patch in a stable 
update.


I managed to fix this by installing with ansible-galaxy (2.1.0) but 
would be nice to fix the packaged version.




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

2023-10-14 Thread Pirate Praveen



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/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 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 [1]. So I'm using mobian bookworm 
but I miss
 > > the newer phosh (especially easy access to suspend button, 
which I use

 > > often for power saving).
 >
 > As discussed in the Mobian issue you mention, the auto-suspend 
problem
 > you're experiencing is only happening with recent versions of 
phosh,
 > which basically reset the idle counter when a critical 
notification

 happens.
 >
 > Providing a backported version of phosh wouldn't help there, and 
the
 > solution should be provided by upstream gnome-settings-daemon[1]. 
In the
 > meantime, you can work around this issue by executing, for 
example:

 >
 >gsettings set sm.puri.phosh.notifications 
wakeup-screen-triggers '[]'


 Thanks this fixes the auto suspend, though one motivation for 
getting newer
 phosh was its suspend inhibition when wifi tethering is active, 
which is

 also disabled with this setting. But I can live with that until


Suspend when wifi hotspot is active is *not* related to any
wakup-screen-triggers. The phosh in stable/bookworm simply doesn't 
take

an inhibitor when the hotspot is active (this was added in 0.26.0).



I am using phosh 0.32 which I rebuilt on bookworm. So this added that 
feature but the other bug of never suspending made it unusable.

Cheers,
 -- Guido

 gnome-settings-daemon is fixed. This means I have to remember to 
toggle
 suspend when charging each time I turn on or off wifi tethering. I 
was using
 a script earlier to launch tethering and inhibit suspend earlier, I 
will go

 back to it until this gets fixed.






 > Cheers,
 > Arnaud
 >
 > [1]
 >
 
<<https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/merge_requests/338>>

 >
 > >
 > > I have built the debs already and started using it from 
yesterday. I
 > > have shared the debs in my personal repo [2]. I'd like to 
upload and
 > > help maintain it in bookworm-backports if you are okay with the 
idea of

 > > providing official backports.
 > >
 > > Since pureos crimson is not yet useable, I think this would be 
useful

 > > for many who want a newer base OS.
 > >
 > > [1]
 
<<https://salsa.debian.org/Mobian-team/devices/librem5-support/-/issues/7>>

 > > [2] <<https://people.debian.org/~praveen/mobian/>>
 > >
 > > ___
 > > Debian-on-mobile-maintainers mailing list
 > > debian-on-mobile-maintain...@alioth-lists.debian.net 
<mailto:debian-on-mobile-maintain...@alioth-lists.debian.net>
 > > 
<<https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-on-mobile-maintainers>>

 >
 >
 >






 ___
 Debian-on-mobile-maintainers mailing list
 debian-on-mobile-maintain...@alioth-lists.debian.net 
<mailto:debian-on-mobile-maintain...@alioth-lists.debian.net>
 
<https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-on-mobile-maintainers>






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

2023-10-13 Thread Pirate Praveen
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 wrote:

> > 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 [1]. So I'm using mobian bookworm but I miss 
the newer
> > phosh (especially easy access to suspend button, which I use often 
for power

> > saving).
> >
> > I have built the debs already and started using it from yesterday. 
I have
> > shared the debs in my personal repo [2]. I'd like to upload and 
help
> > maintain it in bookworm-backports if you are okay with the idea of 
providing

> > official backports.
>
> I'm okay with the idea if you sign up to handle bug reports 
concerning

> the backported versions. If that makes sense to you and Mobian has no
> objections (as I think running it together with Mobian will be the 
main

> use case for most people) we should maintain the backported branch in
> the DebianOnMobile git too.
>
> Note that backporting phosh will imply backporting phoc at some point
> and might also break phosh-mobile-settings at some point (and that
> requires newer libadwaita already (which requires newer GTK). That
> shouldn't' prevent us from backporting just now, just wanted to lay 
out

> that it might get a bit more involved in the future.

I tried backporting phosh-mobile-settings now, as you mentioned it 
needs newer libadwaita, which in turn needs newer glib and gtk4. So I 
think gnome team won't like the official backports.


Arnaud,

Do you think it would be a good idea to have bookworm-backports suite 
in mobian repo and upload these there?


As for bugs, I think keeping up with new upstream versions would be a 
good strategy. If I go with byzantium experience, I'd think you will 
support newer versions on crimson, so having bookworm-backports should 
be easier to maintain.

> Cheers and thanks for having a look at this,
>  -- Guido
>
> >
> > Since pureos crimson is not yet useable, I think this would be 
useful for

> > many who want a newer base OS.
> >
> > [1] 
<https://salsa.debian.org/Mobian-team/devices/librem5-support/-/issues/7>

> > [2] <https://people.debian.org/~praveen/mobian/>
> >
> > ___
> > Debian-on-mobile-maintainers mailing list
> > debian-on-mobile-maintain...@alioth-lists.debian.net
> > 
<https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-on-mobile-maintainers>

> >
>
>





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

2023-10-13 Thread Pirate Praveen
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 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 [1]. So I'm using mobian bookworm but 
I miss
> > the newer phosh (especially easy access to suspend button, which I 
use

> > often for power saving).
>
> As discussed in the Mobian issue you mention, the auto-suspend 
problem

> you're experiencing is only happening with recent versions of phosh,
> which basically reset the idle counter when a critical notification 
happens.

>
> Providing a backported version of phosh wouldn't help there, and the
> solution should be provided by upstream gnome-settings-daemon[1]. In 
the

> meantime, you can work around this issue by executing, for example:
>
>gsettings set sm.puri.phosh.notifications wakeup-screen-triggers 
'[]'


Thanks this fixes the auto suspend, though one motivation for getting 
newer phosh was its suspend inhibition when wifi tethering is active, 
which is also disabled with this setting. But I can live with that 
until gnome-settings-daemon is fixed. This means I have to remember to 
toggle suspend when charging each time I turn on or off wifi tethering. 
I was using a script earlier to launch tethering and inhibit suspend 
earlier, I will go back to it until this gets fixed.


> Cheers,
> Arnaud
>
> [1]
> 
<https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/merge_requests/338>

>
> >
> > I have built the debs already and started using it from yesterday. 
I
> > have shared the debs in my personal repo [2]. I'd like to upload 
and
> > help maintain it in bookworm-backports if you are okay with the 
idea of

> > providing official backports.
> >
> > Since pureos crimson is not yet useable, I think this would be 
useful

> > for many who want a newer base OS.
> >
> > [1] 
<https://salsa.debian.org/Mobian-team/devices/librem5-support/-/issues/7>

> > [2] <https://people.debian.org/~praveen/mobian/>
> >
> > ___
> > Debian-on-mobile-maintainers mailing list
> > debian-on-mobile-maintain...@alioth-lists.debian.net
> > 
<https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-on-mobile-maintainers>

>
>
>





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

2023-10-10 Thread Pirate Praveen

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
pristine-tar: successfully generated 
../glib2.0_2.78.0.orig-unicode-data.tar.xz
fatal: ambiguous argument 
'5d3bcca0ea769dad9fd32d32274931e7bb443b0d^{tree}': unknown revision or 
path not in the working tree.

Use '--' to separate paths from revisions, like this:
'git  [...] -- [...]'
fatal: not a valid object name: 
5d3bcca0ea769dad9fd32d32274931e7bb443b0d^{tree}

tar: This does not look like a tar archive
tar: Exiting with failure status due to previous errors
pristine-tar: command failed: git archive --format=tar 
5d3bcca0ea769dad9fd32d32274931e7bb443b0d\^\{tree\} | (cd 
'/tmp/pristine-tar.GClS2GBRhr' && tar x)

pravi@ilvala2:~/forge/gnome-team/glib$ gbp export-orig --pristine-tar
gbp:info: Creating /home/pravi/forge/gnome-team/glib2.0_2.78.0.orig.tar.xz
gbp:info: Creating 
/home/pravi/forge/gnome-team/glib2.0_2.78.0.orig-unicode-data.tar.xz




Bug#1053747: Upload phosh to bookworm-backports ?

2023-10-10 Thread Pirate Praveen

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 [1]. So I'm using mobian bookworm but I miss 
the newer phosh (especially easy access to suspend button, which I use 
often for power saving).


I have built the debs already and started using it from yesterday. I 
have shared the debs in my personal repo [2]. I'd like to upload and 
help maintain it in bookworm-backports if you are okay with the idea of 
providing official backports.


Since pureos crimson is not yet useable, I think this would be useful 
for many who want a newer base OS.


[1] https://salsa.debian.org/Mobian-team/devices/librem5-support/-/issues/7
[2] https://people.debian.org/~praveen/mobian/



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

2023-09-22 Thread Pirate Praveen

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

2023-09-22 Thread Pirate Praveen
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 for 
plasma-mobile to depend on plasma-dialer and to force some user to 
install plasma-dialer even if not needed.


Thanks for the explanation, makes sense. I was not thinking about the 
tablet use case.


Your point will be addressed in the near future, as a metapackage is 
being worked on to bring something like plasma-mobile-phone (which will 
depend on plasma-dialer and many others) and plasma-mobile-tablet (which 
will not depend on plasma-dialer) to Debian. In the phone usecase, you 
will have to install plasma-mobile-phone to get a full plasma-mobile 
system for the phone usecase, including the dialer.


Thanks for this.



For the point of the plasma-dialer error, that's an error I've seen in 
two situations: inside a virtual machine (hence no modem available to 
route audio calls) or when something was crashing really bad. Just to be 
sure, have you installed plasma-dialer from the Debian repo with all its 
dependencies, right? 


yes installed via apt.
> Does this error still happen after reboot?

It seems to be fixed now and I can make calls with plasma dialer now, 
lso incoming calls are also handled via plasma dialer now.



Kind regards

Marco





OpenPGP_signature
Description: OpenPGP digital signature


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

2023-09-19 Thread Pirate Praveen

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 for incoming calls on 
lockscreen and also in unlocked state (we have to manually select calls 
window to answer)


gnome calls issue #599 (no paste option in geary under plasma mobile)

when manually installing plasma-dialer and starting, it fails with 
error The name org.kde.telephony.CallUtils was not provided by any 
.service files




Bug#1049343:

2023-08-14 Thread Pirate Praveen

  
  


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 does not have this issue and google-protobuf
version in /var/lib/gitlab/.gem/gems/ is 3.23.4 while I have
3.24.0
  

  
  
Regards,



A work around could be downgrading this gem manually. Can you try
  that?


See
https://wiki.debian.org/gitlab/troubleshooting#manually_installing_ruby_dependencies


Modify the gem install command to, gem install -v 3.23.4
  google-protobuf and
gem uninstall -v 3.24.0

  




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

2023-08-03 Thread Pirate Praveen

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/nheko
and run nheko from terminal

First noticed when I reinstalled, flatpack also fails same way so looks 
like an upstream issue.


Second time, nheko starts but initial sync never completes. Both chatty 
and gomuks works with same matrix id.


[2023-08-03 17:42:55.678] [ui] [info] Restoring window size 0x0
[2023-08-03 17:42:55.759] [ui] [info] WebRTC: initialised GStreamer 1.22.4
[2023-08-03 17:42:55.883] [ui] [info] jdenticon plugin not found.
[2023-08-03 17:42:57.976] [ui] [info] starting nheko 0.11.3
[2023-08-03 17:42:57.986] [ui] [info] Unity service available: false
Error: signal 11:
nheko(_Z17stacktraceHandleri+0x40)[0xd55ee940]
linux-vdso.so.1(__kernel_rt_sigreturn+0x0)[0xa06be7ac]
nheko(+0x973940)[0xd5433940]
nheko(+0x977090)[0xd5437090]
nheko(+0x9783bc)[0xd54383bc]
/lib/aarch64-linux-gnu/libgstreamer-1.0.so.0(+0x55270)[0x9da25270]
/lib/aarch64-linux-gnu/libglib-2.0.so.0(g_main_context_dispatch+0x148)[0x9d83a6c8]
/lib/aarch64-linux-gnu/libglib-2.0.so.0(+0x5aaa0)[0x9d83aaa0]
/lib/aarch64-linux-gnu/libglib-2.0.so.0(g_main_context_iteration+0x34)[0x9d83ab44]
/lib/aarch64-linux-gnu/libQt5Core.so.5(_ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE+0x54)[0x9deef6d8]
/lib/aarch64-linux-gnu/libQt5Core.so.5(_ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE+0x13c)[0x9de89d2c]
/lib/aarch64-linux-gnu/libQt5Core.so.5(_ZN16QCoreApplication4execEv+0x98)[0x9de933f8]
nheko(main+0xd14)[0xd526b684]
/lib/aarch64-linux-gnu/libc.so.6(+0x26dc0)[0x9d2a6dc0]
/lib/aarch64-linux-gnu/libc.so.6(__libc_start_main+0x98)[0x9d2a6e98]
nheko(_start+0x30)[0xd526c770]
Error: signal 6:
nheko(_Z17stacktraceHandleri+0x40)[0xd55ee940]
linux-vdso.so.1(__kernel_rt_sigreturn+0x0)[0xa06be7ac]
/lib/aarch64-linux-gnu/libc.so.6(+0x7fd30)[0x9d2ffd30]
/lib/aarch64-linux-gnu/libc.so.6(gsignal+0x1c)[0x9d2b9e2c]
nheko(_Z17stacktraceHandleri+0xd8)[0xd55ee9d8]
linux-vdso.so.1(__kernel_rt_sigreturn+0x0)[0xa06be7ac]
nheko(+0x973940)[0xd5433940]
nheko(+0x977090)[0xd5437090]
nheko(+0x9783bc)[0xd54383bc]
/lib/aarch64-linux-gnu/libgstreamer-1.0.so.0(+0x55270)[0x9da25270]
/lib/aarch64-linux-gnu/libglib-2.0.so.0(g_main_context_dispatch+0x148)[0x9d83a6c8]
/lib/aarch64-linux-gnu/libglib-2.0.so.0(+0x5aaa0)[0x9d83aaa0]
/lib/aarch64-linux-gnu/libglib-2.0.so.0(g_main_context_iteration+0x34)[0x9d83ab44]
/lib/aarch64-linux-gnu/libQt5Core.so.5(_ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE+0x54)[0x9deef6d8]
/lib/aarch64-linux-gnu/libQt5Core.so.5(_ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE+0x13c)[0x9de89d2c]
/lib/aarch64-linux-gnu/libQt5Core.so.5(_ZN16QCoreApplication4execEv+0x98)[0x9de933f8]
nheko(main+0xd14)[0xd526b684]
/lib/aarch64-linux-gnu/libc.so.6(+0x26dc0)[0x9d2a6dc0]
/lib/aarch64-linux-gnu/libc.so.6(__libc_start_main+0x98)[0x9d2a6e98]
nheko(_start+0x30)[0xd526c770]


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

2023-07-14 Thread Pirate Praveen
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

2023-07-14 Thread Pirate Praveen
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

2023-07-14 Thread Pirate Praveen

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 packaged as dependency of ruby-ms-rest-azure, which is in the 
same situation and has an rm bug filed for it (#1041065)




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

2023-07-14 Thread Pirate Praveen

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 unmaintained upstream. This was originally 
packaged as a dependency of ruby-gitlab-fog-azure-rm, but this 
dependency is removed in ruby-gitlab-fog-azure-rm 1.8.




Bug#1037994: retitle and add forwarded

2023-07-14 Thread Pirate Praveen

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 reassign. This dependency is removed in ruby-gitlab-fog-azure-rm 
1.8.




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

2023-07-13 Thread Pirate Praveen

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 is now succeeding on 
armel and mipsel.


https://buildd.debian.org/status/fetch.php?pkg=golang-github-go-enry-go-license-detector=armel=4.3.0%2Bgit20221007.a3a1cc6-3=1689278197=0

https://buildd.debian.org/status/fetch.php?pkg=golang-github-go-enry-go-license-detector=mipsel=4.3.0%2Bgit20221007.a3a1cc6-3=1689281650=0



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

2023-07-13 Thread Pirate Praveen




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 +0100 Sebastian Ramacher
  wrote:
  > Source: golang-github-go-enry-go-license-detector
  > Version: 4.3.0+git20221007.a3a1cc6-1
  > Severity: serious
  > Tags: ftbfs
  > Justification: fails to build from source (but built 
successfully in

 the past)
  >
  >
 
https://buildd.debian.org/status/fetch.php?pkg=golang-github-go-enry-go-license-detector=mipsel=4.3.0%2Bgit20221007.a3a1cc6-1%2Bb2=1675941345=0

  >

 This looks like a temporary error, last build was passing

 
https://buildd.debian.org/status/fetch.php?pkg=golang-github-hhatto-gorst=mipsel=0.0%7Egit20181029.ca9f730-2%2Bb6=1681037294=0


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.



Thanks for pointing out the mistake. I was looking at both failures and 
got confused.

--
Shengjing Zhu




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

2023-07-13 Thread Pirate Praveen
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 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.

>
> AFAIK, it uses the standard AUTOPKGTEST_TMP directory which is the
> standard across debian. I got the same impression on skimming through
> dh-golang code.
>
> As far as fix for your package is concerned, it is as simple as 
avoiding
> to remove entire data directory (which is just 28K in size). I'm 
able to get

> autopkgtests passing locally. Patch pasted
> inline.

Thanks. I guess I was over enthusiastic to suppress

I: golang-github-hhatto-gorst-dev: 
package-contains-documentation-outside-usr-share-doc 
[usr/share/gocode/src/github.com/hhatto/gorst/data/autopep8.readme.rst]


and did not notice the autopkgtest failure then.

I'm uploading the fix you suggested.



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

2023-07-13 Thread Pirate Praveen

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

2023-07-12 Thread Pirate Praveen

Control: fixed -1 0.23.1-3



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

2023-07-11 Thread Pirate Praveen



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) ...
   Could not find gem 'pg (~> 1.4.5, >= 1.4.5)' in cached gems or installed
   locally.

   The source contains the following gems matching 'pg':
 * pg-1.5.2
   dpkg: error processing package gitlab (--configure):
   installed gitlab package post-installation script subprocess returned
   error exit status 1

This looks like an error parsing some notation that version 1.4.5 or later
of some ruby gem is needed when version 1.5.2 is actually available.


It should have been '~> 1.4, >= 1.4.5', but this is already fixed in 
latest versions which has


gem 'pg', '~> 1.5', '>= 1.5.3'

We only support installing one version (latest) of gitlab at any time.


I suspect the version relationship was expressed in a way not supported by
the only available ruby-rubygems package, but possibly by some other not
available implementation not explicitly specified as a gitlab dependency
rule.  Of cause it could be some other ruby package responsible for the
expression in the error message or its parsing.

P.S.

A mostly blank bookworm VM would consist only of bookworm core packages,
SysV init, git packages and site specific configuration of stuff such as
networking.


You can try installing the latest version of gitlab which is 
16.0.7+ds1-3~fto12+2

P.P.S.

I am not Irish, its just the only English EU locale


OpenPGP_0x8F53E0193B294B75.asc
Description: OpenPGP public key


OpenPGP_signature
Description: OpenPGP digital signature


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

2023-07-11 Thread Pirate Praveen

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 by rc bug #1040054 and blocks testing migration of 
ruby-cfpropertylist. Its only reverse dependency is ruby-fog-vmfusion 
and can be removed as well (rm bug #1040831).


OpenPGP_0x8F53E0193B294B75.asc
Description: OpenPGP public key


OpenPGP_signature
Description: OpenPGP digital signature


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

2023-07-11 Thread Pirate Praveen

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 commit in 2017). This also blocks removal of 
ruby-fission which is in similar situation and has an rc bug.


OpenPGP_0x8F53E0193B294B75.asc
Description: OpenPGP public key


OpenPGP_signature
Description: OpenPGP digital signature


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

2023-07-10 Thread Pirate Praveen

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 #1033705 and leaf package. This was originally 
packaged for gitlab-shell but no longer needed.


OpenPGP_0x8F53E0193B294B75.asc
Description: OpenPGP public key


OpenPGP_signature
Description: OpenPGP digital signature


Bug#1034565: ftbfs tests fail on ppc64el and mips64el

2023-07-08 Thread Pirate Praveen
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(:initial_mmap_file_size))
>
> expected: 4096
>  got: 16384
>
> (compared using ==)
>   # ./spec/prometheus/client/helpers/mmaped_file_spec.rb:30:in
> `block (3 levels) in '

Fixed upstream in 0.20 and 0.23 is being uploaded to experimental. We 
can close this once we confirm the failures are fixed.




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

2023-07-08 Thread Pirate Praveen
On Thu, 29 Jun 2023 16:03:13 +0200 Paul Gevers  
wrote:


> 
┌──┐

>   19s │ Checking Rubygems dependency resolution on ruby3.1
>  │
>   19s
> 
└──┘

>   19s  19s GEM_PATH= ruby3.1 -e gem\ \"derailed_benchmarks\"
>   19s /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1413:in
> `rescue in block in activate_dependencies': Could not find
> 'memory_profiler' (~> 0) among 102 total gem(s) 
(Gem::MissingSpecError)

>   19s Checked in

This is fixed upstream but the new upstream version adds a new 
dependency dead_end gem. Also gitlab has moved this dependency from 
production to test group in Gemfile, so we can remove this once the 
dependency is dropped from gitlab.




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

2023-07-08 Thread Pirate Praveen
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 pkgProblemResolver with broken count: 1
> Investigating (0) autopkgtest-satdep:amd64 < 0 @iU K Nb Ib >
> Broken autopkgtest-satdep:amd64 Depends on ruby-gitaly-proto:amd64 <
> none @un H >
>Removing autopkgtest-satdep:amd64 because I can't find
> ruby-gitaly-proto:amd64

ruby-gitaly-proto used to be provided by ruby-gitaly binary package 
built from this source package. But ruby-gitaly binary package is now 
built from gitaly source package which does not provide 
ruby-gitaly-proto.


This was originally packaged as a dependency of gitlab-shell, which no 
longer need golang-gitaly-proto-dev build dependency.


So we can remove this package. I will file an rm request once the build 
dependency is removed from gitlab-shell in unstable.




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

2023-07-08 Thread Pirate Praveen

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 to me that the change in ruby-memory-profiler was intended 
and

> your package needs to update to the new situation.

ruby-benchmark-memory 0.2.0-1 was ready in experimental, but missed a 
reupload to unstable. I'm reuploading it to unstable now.




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

2023-07-06 Thread Pirate Praveen

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 and 
gitaly no longer needs it (so I'm not interested in maintaining it any 
longer). It is also blocking testing migration of ruby-rouge 
(#1040405). So I have filed an rm request #1040461 for it. If you are 
interested in maintaining it, you can close the rm bug and fix the rc 
bug.




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

2023-07-06 Thread Pirate Praveen
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

2023-07-06 Thread Pirate Praveen

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 armel and i386 will allow removal of 
ruby-gollum-lib (which will unblock testing migration of ruby-rouge and 
redmine).




OpenPGP_0x8F53E0193B294B75.asc
Description: OpenPGP public key


OpenPGP_signature
Description: OpenPGP digital signature


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

2023-07-06 Thread Pirate Praveen

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 
#1040405. It was originally packaged as a dependency of gitaly which no 
longer depend on it.


This will require removing of gitaly from armel and i386, which are 
lagging compared to other arches and has a dependency on ruby-gollum-lib.


OpenPGP_0x8F53E0193B294B75.asc
Description: OpenPGP public key


OpenPGP_signature
Description: OpenPGP digital signature


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

2023-06-21 Thread Pirate Praveen

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 for typhoeus ->
> https://github.com/dleavitt/faraday-typhoeus

faraday should be replaced with faraday-typhoeus in tests
https://github.com/typhoeus/typhoeus/issues/717



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

2023-06-21 Thread Pirate Praveen

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

2023-06-19 Thread Pirate Praveen

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

2023-06-19 Thread Pirate Praveen

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 3.20 and while trying to update
> it, the build fails with
>
>   13) Failure:
> TestRubyParserV32#test_unless_pre_not__18
> [/usr/lib/ruby/vendor_ruby/pt_testcase.rb:159]:
> failed on input: "unless not b then a end".
> --- expected
> +++ actual
> @@ -1 +1,4 @@
> -s(:if, s(:call, nil, :b), s(:call, nil, :a), nil)
> +s(:if,
> + s(:call, s(:call, nil, :b).line(1), :!).line(1),
> + nil,
> + s(:call, nil, :a).line(1)).line(1)

This is fixed by updating ruby-sexp-processor to 4.17.0



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

2023-06-18 Thread Pirate Praveen
Control: forwarded -1 
https://github.com/rabbit-shocker/rabbit/issues/151


On Thu, 15 Jun 2023 01:18:17 +0530 Pirate Praveen 
 wrote:

>
> Started
> E
> 
===

> Error: test_upload(TestSlideShare): Faraday::Error: :multipart is not
> registered on Faraday::Request

Requested upstream https://github.com/rabbit-shocker/rabbit/issues/151



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

2023-06-18 Thread Pirate Praveen

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) 
(Gem::ConflictError)


Upstream now support faraday 2.0 
https://github.com/puppetlabs/forge-ruby/commit/06102bc9478d9d19fbe12b505639fb253d29ba54




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

2023-06-18 Thread Pirate Praveen

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://github.com/travis-ci/gh/issues/46



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

2023-06-18 Thread Pirate Praveen
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-translate-v2 and google-cloud-translate-v3.




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

2023-06-18 Thread Pirate Praveen
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) 
among


There is an upstream pull request that adds support for faraday 2.0
https://github.com/Azure/azure-storage-ruby/issues/227



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

2023-06-18 Thread Pirate Praveen




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)


This seems to be caused by ruby-faraday-middleware.


Since ruby-faraday-middleware is deprecated, we should update to 
graphlient 0.7




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

2023-06-18 Thread Pirate Praveen
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

2023-06-18 Thread Pirate Praveen
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/-/issues/3



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

2023-06-18 Thread Pirate Praveen

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

2023-06-17 Thread Pirate Praveen
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)' in cached gems or installed
> locally.
>
> Full log attached. Please adapt redmine to rouge 4.1 so I can 
reupload

> it unstable soon.
>

I'm hoping to upload ruby-rouge 4.1 to unstable on July 1st. redmine is 
the last blocking package. If redmine is fixed before that, I can 
upload ruby-rouge earlier too.




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

2023-06-17 Thread Pirate Praveen

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

2023-06-15 Thread Pirate Praveen

Control: clone 1037992 -1



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

2023-06-15 Thread Pirate Praveen

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 ruby-faraday 2.7.1 to unstable soon.

sbuild (Debian sbuild) 0.85.2 (11 March 2023) on mahishi

+==+
| ruby-ms-rest 0.7.6-2 (amd64) Wed, 14 Jun 2023 20:35:44 + |
+==+

Package: ruby-ms-rest
Version: 0.7.6-2
Source Version: 0.7.6-2
Distribution: unstable
Machine Architecture: amd64
Host Architecture: amd64
Build Architecture: amd64
Build Type: binary

I: NOTICE: Log filtering will replace 'var/run/schroot/mount/unstable-amd64-sbuild-95d70ff4-2889-4a45-a8c6-dfb595c50a90' with '<>'
Copying /home/pravi/forge/ruby-team/ruby-faraday_2.7.1-1_all.deb to Sbuild::ChrootSchroot=HASH(0x5642e3a44858)->get('Location')...
I: NOTICE: Log filtering will replace 'build/ruby-ms-rest-Csx4Jl/resolver-tON6Pw' with '<>'

+--+
| Update chroot|
+--+

Get:1 file:/build/ruby-ms-rest-Csx4Jl/resolver-2F0pKG/apt_archive ./ InRelease
Ign:1 file:/build/ruby-ms-rest-Csx4Jl/resolver-2F0pKG/apt_archive ./ InRelease
Get:2 file:/build/ruby-ms-rest-Csx4Jl/resolver-2F0pKG/apt_archive ./ Release [606 B]
Get:2 file:/build/ruby-ms-rest-Csx4Jl/resolver-2F0pKG/apt_archive ./ Release [606 B]
Get:3 file:/build/ruby-ms-rest-Csx4Jl/resolver-2F0pKG/apt_archive ./ Release.gpg
Ign:3 file:/build/ruby-ms-rest-Csx4Jl/resolver-2F0pKG/apt_archive ./ Release.gpg
Get:4 file:/build/ruby-ms-rest-Csx4Jl/resolver-2F0pKG/apt_archive ./ Packages [1152 B]
Get:5 http://deb.debian.org/debian unstable InRelease [199 kB]
Get:6 http://deb.debian.org/debian experimental InRelease [101 kB]
Get:7 http://deb.debian.org/debian unstable/main Sources.diff/Index [63.6 kB]
Get:8 http://deb.debian.org/debian unstable/main amd64 Packages.diff/Index [63.6 kB]
Get:9 http://deb.debian.org/debian unstable/main Sources T-2023-06-14-1403.53-F-2023-06-13-1418.37.pdiff [149 kB]
Get:9 http://deb.debian.org/debian unstable/main Sources T-2023-06-14-1403.53-F-2023-06-13-1418.37.pdiff [149 kB]
Get:10 http://deb.debian.org/debian unstable/main amd64 Packages T-2023-06-14-1403.53-F-2023-06-13-1418.37.pdiff [188 kB]
Get:10 http://deb.debian.org/debian unstable/main amd64 Packages T-2023-06-14-1403.53-F-2023-06-13-1418.37.pdiff [188 kB]
Get:11 http://deb.debian.org/debian experimental/main amd64 Packages [902 kB]
Fetched 1667 kB in 8s (215 kB/s)
Reading package lists...
Reading package lists...
Building dependency tree...
Reading state information...
Calculating upgrade...
The following packages will be upgraded:
  cpp-12 g++-12 gcc-12 gcc-12-base libgcc-12-dev libmd0 libstdc++-12-dev
7 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 44.7 MB of archives.
After this operation, 1327 kB of additional disk space will be used.
Get:1 http://deb.debian.org/debian unstable/main amd64 libmd0 amd64 1.1.0-1 [35.5 kB]
Get:2 http://deb.debian.org/debian unstable/main amd64 g++-12 amd64 12.3.0-3 [10.8 MB]
Get:3 http://deb.debian.org/debian unstable/main amd64 libstdc++-12-dev amd64 12.3.0-3 [2045 kB]
Get:4 http://deb.debian.org/debian unstable/main amd64 gcc-12 amd64 12.3.0-3 [19.5 MB]
Get:5 http://deb.debian.org/debian unstable/main amd64 libgcc-12-dev amd64 12.3.0-3 [2434 kB]
Get:6 http://deb.debian.org/debian unstable/main amd64 cpp-12 amd64 12.3.0-3 [9857 kB]
Get:7 http://deb.debian.org/debian unstable/main amd64 gcc-12-base amd64 12.3.0-3 [39.5 kB]
debconf: delaying package configuration, since apt-utils is not installed
Fetched 44.7 MB in 0s (160 MB/s)
(Reading database ... 
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 13839 files and directories currently installed.)
Preparing to unpack .../libmd0_1.1.0-1_amd64.deb ...
Unpacking libmd0:amd64 (1.1.0-1) over (1.0.4-2) ...
Setting up libmd0:amd64 (1.1.0-1) ...
(Reading database ... 
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading 

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

2023-06-15 Thread Pirate Praveen
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/Asana/ruby-asana/pull/152


But it will need packaging two new gems

 spec.add_dependency "faraday-follow_redirects"
 spec.add_dependency "faraday-multipart"



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

2023-06-14 Thread Pirate Praveen

Package: rabbit
Version: 3.0.0-5
Severity: important

Full log attached

Started
E
===
Error: test_upload(TestSlideShare): Faraday::Error: :multipart is not 
registered on Faraday::Request
/usr/share/rubygems-integration/all/gems/faraday-2.7.1/lib/faraday/middleware_registry.rb:57:in 
`lookup_middleware'
/usr/share/rubygems-integration/all/gems/faraday-2.7.1/lib/faraday/rack_builder.rb:242:in 
`use_symbol'
/usr/share/rubygems-integration/all/gems/faraday-2.7.1/lib/faraday/rack_builder.rb:103:in 
`request'

/usr/lib/ruby/3.1.0/forwardable.rb:238:in `request'
/tmp/autopkgtest-lxc.sdllem2t/downtmp/build.zXz/src/lib/rabbit/slideshare.rb:50:in 
`block in initialize'
/usr/share/rubygems-integration/all/gems/faraday-2.7.1/lib/faraday/connection.rb:91:in 
`initialize'
/usr/share/rubygems-integration/all/gems/faraday-2.7.1/lib/faraday.rb:98:in 
`new'
/usr/share/rubygems-integration/all/gems/faraday-2.7.1/lib/faraday.rb:98:in 
`new'
/tmp/autopkgtest-lxc.sdllem2t/downtmp/build.zXz/src/lib/rabbit/slideshare.rb:49:in 
`initialize'
/tmp/autopkgtest-lxc.sdllem2t/downtmp/build.zXz/src/test/test-slideshare.rb:23:in 
`new'
/tmp/autopkgtest-lxc.sdllem2t/downtmp/build.zXz/src/test/test-slideshare.rb:23:in 
`setup'

===
..
Finished in 5.454974752 seconds.
---
123 tests, 173 assertions, 0 failures, 1 errors, 0 pendings, 0 
omissions, 0 notifications

99.187% passed


autopkgtest [00:57:54]: starting date and time: 2023-06-15 00:57:54+0530
autopkgtest [00:57:54]: version 5.28
autopkgtest [00:57:54]: host mahishi; command line: /usr/bin/autopkgtest --user debci --apt-upgrade --log-file=/tmp/ruby-faraday_2.7.1-1_amd64.QYj3zjw6Po/autopkgtest/rabbit.log /home/pravi/forge/ruby-team/ruby-faraday_2.7.1-1_all.deb rabbit -- lxc --sudo autopkgtest-unstable-amd64
autopkgtest [00:58:14]:  test bed setup
Get:1 http://deb.debian.org/debian unstable InRelease [199 kB]
Get:2 http://deb.debian.org/debian-debug unstable-debug InRelease [56.7 kB]
Get:3 http://deb.debian.org/debian unstable/contrib Sources.diff/Index [63.3 kB]
Get:4 http://deb.debian.org/debian unstable/non-free Sources.diff/Index [63.3 kB]
Get:5 http://deb.debian.org/debian unstable/main Sources.diff/Index [63.6 kB]
Get:6 http://deb.debian.org/debian unstable/non-free amd64 Packages.diff/Index [63.3 kB]
Get:7 http://deb.debian.org/debian unstable/contrib amd64 Packages.diff/Index [63.3 kB]
Get:8 http://deb.debian.org/debian unstable/main amd64 Packages.diff/Index [63.6 kB]
Get:9 http://incoming.debian.org/debian-buildd buildd-unstable InRelease [53.7 kB]
Get:10 http://deb.debian.org/debian unstable/contrib Sources T-2023-06-13-2009.09-F-2023-06-13-1418.37.pdiff [1,691 B]
Get:11 http://deb.debian.org/debian unstable/non-free Sources T-2023-06-13-2009.09-F-2023-06-13-2009.09.pdiff [715 B]
Get:12 http://deb.debian.org/debian unstable/main Sources T-2023-06-14-1403.53-F-2023-06-13-1418.37.pdiff [149 kB]
Get:13 http://deb.debian.org/debian unstable/non-free amd64 Packages T-2023-06-13-2009.09-F-2023-06-13-2009.09.pdiff [460 B]
Get:14 http://deb.debian.org/debian unstable/contrib amd64 Packages T-2023-06-14-0205.16-F-2023-06-13-2009.09.pdiff [563 B]
Get:10 http://deb.debian.org/debian unstable/contrib Sources T-2023-06-13-2009.09-F-2023-06-13-1418.37.pdiff [1,691 B]
Get:13 http://deb.debian.org/debian unstable/non-free amd64 Packages T-2023-06-13-2009.09-F-2023-06-13-2009.09.pdiff [460 B]
Get:12 http://deb.debian.org/debian unstable/main Sources T-2023-06-14-1403.53-F-2023-06-13-1418.37.pdiff [149 kB]
Get:11 http://deb.debian.org/debian unstable/non-free Sources T-2023-06-13-2009.09-F-2023-06-13-2009.09.pdiff [715 B]
Get:15 http://deb.debian.org/debian-debug unstable-debug/main Sources.diff/Index [63.6 kB]
Get:16 http://deb.debian.org/debian-debug unstable-debug/contrib Sources.diff/Index [63.3 kB]
Get:17 http://deb.debian.org/debian-debug unstable-debug/main amd64 Packages.diff/Index [63.6 kB]
Get:18 http://deb.debian.org/debian-debug unstable-debug/contrib amd64 Packages.diff/Index [63.3 kB]
Get:14 http://deb.debian.org/debian unstable/contrib amd64 Packages T-2023-06-14-0205.16-F-2023-06-13-2009.09.pdiff [563 B]
Get:19 http://deb.debian.org/debian unstable/main amd64 Packages T-2023-06-14-1403.53-F-2023-06-13-1418.37.pdiff [188 kB]
Get:20 http://deb.debian.org/debian-debug unstable-debug/main Sources T-2023-06-14-1403.53-F-2023-06-13-1418.37.pdiff [66.5 kB]
Get:19 http://deb.debian.org/debian unstable/main amd64 Packages T-2023-06-14-1403.53-F-2023-06-13-1418.37.pdiff [188 kB]
Get:21 http://deb.debian.org/debian-debug unstable-debug/contrib Sources T-2023-06-14-0205.16-F-2023-06-13-2009.09.pdiff [1,059 B]
Get:22 

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

2023-06-13 Thread Pirate Praveen

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,6 @@

indent with 2 spaces

-class=\"highlight\"> class=\"nx\">console.class=\"nx\">log(class=\"dl\">\"helloclass=\"dl\">\");
+class=\"highlight\"> class=\"nx\">console.class=\"nf\">log(class=\"dl\">\"helloclass=\"dl\">\");


"


13 runs, 13 assertions, 1 failures, 0 errors, 0 skips

full log attached

autopkgtest [13:11:22]: starting date and time: 2023-06-13 13:11:22+0530
autopkgtest [13:11:22]: version 5.28
autopkgtest [13:11:22]: host mahishi; command line: /usr/bin/autopkgtest --user debci --apt-upgrade --log-file=/tmp/ruby-rouge_4.1.0-1_amd64.UF50hEJjZw/autopkgtest/ruby-kramdown-parser-gfm.log /home/pravi/forge/ruby-team/build-area/ruby-rouge_4.1.0-1_all.deb ruby-kramdown-parser-gfm -- lxc --sudo autopkgtest-unstable-amd64
autopkgtest [13:11:39]:  test bed setup
Get:1 http://deb.debian.org/debian unstable InRelease [199 kB]
Get:2 http://deb.debian.org/debian-debug unstable-debug InRelease [56.7 kB]
Get:3 http://deb.debian.org/debian unstable/contrib Sources.diff/Index [63.3 kB]
Get:4 http://deb.debian.org/debian unstable/non-free Sources.diff/Index [63.3 kB]
Get:5 http://deb.debian.org/debian unstable/main Sources.diff/Index [63.6 kB]
Get:6 http://deb.debian.org/debian unstable/non-free amd64 Packages.diff/Index [63.3 kB]
Get:7 http://deb.debian.org/debian unstable/contrib amd64 Packages.diff/Index [63.3 kB]
Get:8 http://deb.debian.org/debian unstable/main amd64 Packages.diff/Index [63.6 kB]
Get:9 http://incoming.debian.org/debian-buildd buildd-unstable InRelease [53.7 kB]
Get:10 http://deb.debian.org/debian unstable/contrib Sources T-2023-06-13-0242.35-F-2023-06-12-1422.14.pdiff [1,388 B]
Get:11 http://deb.debian.org/debian unstable/non-free Sources T-2023-06-13-0242.35-F-2023-06-12-2020.02.pdiff [752 B]
Get:12 http://deb.debian.org/debian unstable/main Sources T-2023-06-13-0242.35-F-2023-06-12-1422.14.pdiff [124 kB]
Get:13 http://deb.debian.org/debian unstable/non-free amd64 Packages T-2023-06-13-0242.35-F-2023-06-13-0242.35.pdiff [326 B]
Get:14 http://deb.debian.org/debian unstable/contrib amd64 Packages T-2023-06-12-2020.02-F-2023-06-12-1422.14.pdiff [2,664 B]
Get:11 http://deb.debian.org/debian unstable/non-free Sources T-2023-06-13-0242.35-F-2023-06-12-2020.02.pdiff [752 B]
Get:10 http://deb.debian.org/debian unstable/contrib Sources T-2023-06-13-0242.35-F-2023-06-12-1422.14.pdiff [1,388 B]
Get:12 http://deb.debian.org/debian unstable/main Sources T-2023-06-13-0242.35-F-2023-06-12-1422.14.pdiff [124 kB]
Get:13 http://deb.debian.org/debian unstable/non-free amd64 Packages T-2023-06-13-0242.35-F-2023-06-13-0242.35.pdiff [326 B]
Get:15 http://deb.debian.org/debian-debug unstable-debug/main Sources.diff/Index [63.6 kB]
Get:14 http://deb.debian.org/debian unstable/contrib amd64 Packages T-2023-06-12-2020.02-F-2023-06-12-1422.14.pdiff [2,664 B]
Get:16 http://deb.debian.org/debian-debug unstable-debug/contrib Sources.diff/Index [63.3 kB]
Get:17 http://deb.debian.org/debian-debug unstable-debug/main amd64 Packages.diff/Index [63.6 kB]
Get:18 http://deb.debian.org/debian-debug unstable-debug/contrib amd64 Packages.diff/Index [63.3 kB]
Get:19 http://incoming.debian.org/debian-buildd buildd-unstable/non-free Sources [1,228 B]
Get:20 http://deb.debian.org/debian unstable/main amd64 Packages T-2023-06-13-0242.35-F-2023-06-12-1422.14.pdiff [158 kB]
Get:21 http://deb.debian.org/debian-debug unstable-debug/main Sources T-2023-06-13-0242.35-F-2023-06-12-1422.14.pdiff [73.0 kB]
Get:22 http://deb.debian.org/debian-debug unstable-debug/contrib Sources T-2023-06-13-0242.35-F-2023-06-12-2020.02.pdiff [968 B]
Get:23 http://deb.debian.org/debian-debug unstable-debug/main amd64 Packages T-2023-06-13-0242.35-F-2023-06-12-1422.14.pdiff [80.9 kB]
Get:20 http://deb.debian.org/debian unstable/main amd64 Packages T-2023-06-13-0242.35-F-2023-06-12-1422.14.pdiff [158 kB]
Get:21 http://deb.debian.org/debian-debug unstable-debug/main Sources T-2023-06-13-0242.35-F-2023-06-12-1422.14.pdiff [73.0 kB]
Get:22 http://deb.debian.org/debian-debug unstable-debug/contrib Sources T-2023-06-13-0242.35-F-2023-06-12-2020.02.pdiff [968 B]
Get:23 http://deb.debian.org/debian-debug unstable-debug/main amd64 Packages T-2023-06-13-0242.35-F-2023-06-12-1422.14.pdiff [80.9 kB]
Get:24 http://deb.debian.org/debian-debug unstable-debug/contrib amd64 Packages T-2023-06-13-0242.35-F-2023-06-12-2020.02.pdiff [6,695 B]
Get:25 http://incoming.debian.org/debian-buildd buildd-unstable/main Sources [277 kB]
Get:26 http://incoming.debian.org/debian-buildd buildd-unstable/contrib Sources [3,100 B]
Get:27 http://incoming.debian.org/debian-buildd buildd-unstable/main amd64 Packages [377 kB]
Get:28 http://incoming.debian.org/debian-buildd 

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

2023-06-13 Thread Pirate Praveen

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:01:15]: starting date and time: 2023-06-13 13:01:15+0530
autopkgtest [13:01:15]: version 5.28
autopkgtest [13:01:15]: host mahishi; command line: /usr/bin/autopkgtest --user debci --apt-upgrade --log-file=/tmp/ruby-rouge_4.1.0-1_amd64.UF50hEJjZw/autopkgtest/ruby-gollum-lib.log /home/pravi/forge/ruby-team/build-area/ruby-rouge_4.1.0-1_all.deb ruby-gollum-lib -- lxc --sudo autopkgtest-unstable-amd64
autopkgtest [13:01:54]:  test bed setup
Get:1 http://deb.debian.org/debian unstable InRelease [199 kB]
Get:2 http://incoming.debian.org/debian-buildd buildd-unstable InRelease [53.7 kB]
Get:3 http://deb.debian.org/debian-debug unstable-debug InRelease [56.7 kB]
Get:4 http://incoming.debian.org/debian-buildd buildd-unstable/contrib Sources [3,100 B]
Get:5 http://incoming.debian.org/debian-buildd buildd-unstable/non-free Sources [1,228 B]
Get:6 http://incoming.debian.org/debian-buildd buildd-unstable/main Sources [277 kB]
Get:7 http://incoming.debian.org/debian-buildd buildd-unstable/non-free amd64 Packages [1,040 B]
Get:8 http://incoming.debian.org/debian-buildd buildd-unstable/contrib amd64 Packages [7,448 B]
Get:9 http://incoming.debian.org/debian-buildd buildd-unstable/main amd64 Packages [377 kB]
Get:10 http://deb.debian.org/debian unstable/non-free Sources.diff/Index [63.3 kB]
Get:11 http://deb.debian.org/debian unstable/contrib Sources.diff/Index [63.3 kB]
Get:12 http://deb.debian.org/debian unstable/main Sources.diff/Index [63.6 kB]
Get:13 http://deb.debian.org/debian unstable/non-free amd64 Packages.diff/Index [63.3 kB]
Get:14 http://deb.debian.org/debian unstable/contrib amd64 Packages.diff/Index [63.3 kB]
Get:15 http://deb.debian.org/debian unstable/main amd64 Packages.diff/Index [63.6 kB]
Get:16 http://deb.debian.org/debian unstable/non-free Sources T-2023-06-13-0242.35-F-2023-06-12-2020.02.pdiff [752 B]
Get:17 http://deb.debian.org/debian unstable/contrib Sources T-2023-06-13-0242.35-F-2023-06-12-1422.14.pdiff [1,388 B]
Get:18 http://deb.debian.org/debian unstable/main Sources T-2023-06-13-0242.35-F-2023-06-12-1422.14.pdiff [124 kB]
Get:19 http://deb.debian.org/debian unstable/non-free amd64 Packages T-2023-06-13-0242.35-F-2023-06-13-0242.35.pdiff [326 B]
Get:20 http://deb.debian.org/debian unstable/contrib amd64 Packages T-2023-06-12-2020.02-F-2023-06-12-1422.14.pdiff [2,664 B]
Get:16 http://deb.debian.org/debian unstable/non-free Sources T-2023-06-13-0242.35-F-2023-06-12-2020.02.pdiff [752 B]
Get:20 http://deb.debian.org/debian unstable/contrib amd64 Packages T-2023-06-12-2020.02-F-2023-06-12-1422.14.pdiff [2,664 B]
Get:19 http://deb.debian.org/debian unstable/non-free amd64 Packages T-2023-06-13-0242.35-F-2023-06-13-0242.35.pdiff [326 B]
Get:18 http://deb.debian.org/debian unstable/main Sources T-2023-06-13-0242.35-F-2023-06-12-1422.14.pdiff [124 kB]
Get:17 http://deb.debian.org/debian unstable/contrib Sources T-2023-06-13-0242.35-F-2023-06-12-1422.14.pdiff [1,388 B]
Get:21 http://deb.debian.org/debian-debug unstable-debug/contrib Sources.diff/Index [63.3 kB]
Get:22 http://deb.debian.org/debian-debug unstable-debug/main Sources.diff/Index [63.6 kB]
Get:23 http://deb.debian.org/debian-debug unstable-debug/main amd64 Packages.diff/Index [63.6 kB]
Get:24 http://deb.debian.org/debian-debug unstable-debug/contrib amd64 Packages.diff/Index [63.3 kB]
Get:25 http://deb.debian.org/debian unstable/main amd64 Packages T-2023-06-13-0242.35-F-2023-06-12-1422.14.pdiff [158 kB]
Get:26 http://deb.debian.org/debian-debug unstable-debug/contrib Sources T-2023-06-13-0242.35-F-2023-06-12-2020.02.pdiff [968 B]
Get:27 http://deb.debian.org/debian-debug unstable-debug/main Sources T-2023-06-13-0242.35-F-2023-06-12-1422.14.pdiff [73.0 kB]
Get:28 http://deb.debian.org/debian-debug unstable-debug/main amd64 Packages T-2023-06-13-0242.35-F-2023-06-12-1422.14.pdiff [80.9 kB]
Get:25 http://deb.debian.org/debian unstable/main amd64 Packages T-2023-06-13-0242.35-F-2023-06-12-1422.14.pdiff [158 kB]
Get:26 http://deb.debian.org/debian-debug unstable-debug/contrib Sources T-2023-06-13-0242.35-F-2023-06-12-2020.02.pdiff [968 B]
Get:27 http://deb.debian.org/debian-debug unstable-debug/main Sources T-2023-06-13-0242.35-F-2023-06-12-1422.14.pdiff [73.0 kB]
Get:29 http://deb.debian.org/debian-debug unstable-debug/contrib amd64 Packages T-2023-06-13-0242.35-F-2023-06-12-2020.02.pdiff [6,695 B]
Get:29 http://deb.debian.org/debian-debug unstable-debug/contrib amd64 Packages T-2023-06-13-0242.35-F-2023-06-12-2020.02.pdiff [6,695 B]
Get:28 http://deb.debian.org/debian-debug unstable-debug/main amd64 Packages T-2023-06-13-0242.35-F-2023-06-12-1422.14.pdiff [80.9 kB]
Fetched 2,059 kB in 21s (98.3 kB/s)
Reading package lists...

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

2023-06-12 Thread Pirate Praveen

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-any.


golang.org/x/exp/maps
# golang.org/x/exp/maps
src/golang.org/x/exp/maps/maps.go:10:10: error: expected ‘(’
   10 | func Keys[M ~map[K]V, K comparable, V any](m M) []K {
  |  ^
src/golang.org/x/exp/maps/maps.go:10:13: error: invalid character 0x7e 
in input file

   10 | func Keys[M ~map[K]V, K comparable, V any](m M) []K {
  | ^
src/golang.org/x/exp/maps/maps.go:11:9: error: expected ‘]’
   11 | r := make([]K, 0, len(m))
  | ^
src/golang.org/x/exp/maps/maps.go:11:9: error: expected ‘;’ or newline 
after top level declaration

src/golang.org/x/exp/maps/maps.go:12:9: error: expected declaration
   12 | for k := range m {
  | ^
src/golang.org/x/exp/maps/maps.go:14:9: error: expected declaration
   14 | }
  | ^
src/golang.org/x/exp/maps/maps.go:15:9: error: expected declaration
   15 | return r
  | ^
src/golang.org/x/exp/maps/maps.go:16:1: error: expected declaration
   16 | }
  | ^
sbuild (Debian sbuild) 0.85.2 (11 March 2023) on mahishi

+===+
| golang-golang-x-exp 0.0~git20221028.83b7d23-2 (amd64) Mon, 12 Jun 2023 
12:47:20 + |
+===+

Package: golang-golang-x-exp
Version: 0.0~git20221028.83b7d23-2
Source Version: 0.0~git20221028.83b7d23-2
Distribution: unstable
Machine Architecture: amd64
Host Architecture: amd64
Build Architecture: amd64
Build Type: binary

I: NOTICE: Log filtering will replace 
'var/run/schroot/mount/unstable-amd64-sbuild-24a3fad7-52f9-45d5-ba4b-67774cece214'
 with '<>'
I: NOTICE: Log filtering will replace 
'build/golang-golang-x-exp-PqPMEI/resolver-ugb2fS' with '<>'

+--+
| Update chroot|
+--+

Hit:1 http://deb.debian.org/debian unstable InRelease
Reading package lists...
Reading package lists...
Building dependency tree...
Reading state information...
Calculating upgrade...
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

+--+
| Fetch source files   |
+--+


Local sources
-

/home/pravi/forge/go-team/golang-golang-x-exp_0.0~git20221028.83b7d23-2.dsc 
exists in /home/pravi/forge/go-team; copying to chroot
I: NOTICE: Log filtering will replace 
'build/golang-golang-x-exp-PqPMEI/golang-golang-x-exp-0.0~git20221028.83b7d23' 
with '<>'
I: NOTICE: Log filtering will replace 'build/golang-golang-x-exp-PqPMEI' with 
'<>'

+--+
| Install package build dependencies   |
+--+


Setup apt archive
-

Merged Build-Depends: debhelper-compat (= 13), dh-sequence-golang, gccgo-go (>= 
2:1.18~), gccgo-13, build-essential, fakeroot
Filtered Build-Depends: debhelper-compat (= 13), dh-sequence-golang, gccgo-go 
(>= 2:1.18~), gccgo-13, build-essential, fakeroot
dpkg-deb: building package 'sbuild-build-depends-main-dummy' in 
'/<>/apt_archive/sbuild-build-depends-main-dummy.deb'.
Ign:1 copy:/<>/apt_archive ./ InRelease
Get:2 copy:/<>/apt_archive ./ Release [609 B]
Ign:3 copy:/<>/apt_archive ./ Release.gpg
Get:4 copy:/<>/apt_archive ./ Sources [670 B]
Get:5 copy:/<>/apt_archive ./ Packages [702 B]
Fetched 1981 B in 0s (0 B/s)
Reading package lists...
Reading package lists...

Install main build dependencies (apt-based resolver)


Installing build dependencies
Reading package lists...
Building dependency tree...
Reading state information...
The following additional packages will be installed:
  autoconf automake autopoint autotools-dev bsdextrautils cpp-13 debhelper
  dh-autoreconf dh-golang dh-strip-nondeterminism dwz file gcc-13 gccgo-12
  gccgo-13 gccgo-go gettext gettext-base groff-base intltool-debian
  libarchive-zip-perl libdebhelper-perl libelf1
  libfile-stripnondeterminism-perl libgcc-13-dev libgo-12-dev libgo-13-dev
  libgo21 libgo22 libhwasan0 libicu72 libmagic-mgc libmagic1 libpipeline1
  libsub-override-perl libtool libuchardet0 libxml2 m4 man-db po-debconf
  sensible-utils
Suggested packages:
  autoconf-archive 

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

2023-06-11 Thread Pirate Praveen

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-gitlab-gitlab-org-labkit FTBFSes within unstable
> (with or without the updated golang-github-gin-gonic-gin package).
>

1.17.0-1 in experimental builds fine. I'm reuploading it to unstable.



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

2023-06-11 Thread Pirate Praveen

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 dependencies are working, this is now uploaded 
to unstable.




Bug#1036558: Update kaidan to new upstream release 0.9.1

2023-05-22 Thread Pirate Praveen

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 package.




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

2023-05-21 Thread Pirate Praveen

Control: reassign ruby3.1
Control: affects ruby-ruby-parser

On Thu, 4 May 2023 23:12:08 +0530 Praveen Arimbrathodiyil 
 wrote:

>
>
> On 04/05/23 11:05 pm, Praveen Arimbrathodiyil wrote:
> >
> >
> > On 04/05/23 10:44 pm, Pirate Praveen wrote:
> >> Running the tests like upstream would with ruby 3.1 installed via 
rvm,

> >> the same errors are reproduced.
> >>
> >> 
https://github.com/seattlerb/ruby_parser/issues/337#issuecomment-1535023385

> >>
> >
> > on bullseye with rvm installed ruby 3.0, all tests pass. Though on 
sid,

> > rvm install 3.0 fails.
>
> on bullseye too, with rvm installed ruby 3.1, the failures were
> reproduced. So we can confirm the failure is with ruby 3.1.

Since upstream confirmed the tests were passing with ruby 3.1.4 I was 
also able to get the tests passing with ruby 3.1.4 and the failure is 
only with ruby 3.1.2. Can we update ruby to 3.1.4?




Bug#1035529: ITP: ruby-semver-dialects -- utility function to process semantic versions expressed in different dialects

2023-05-04 Thread Pirate Praveen

Package: wnpp
severity: wishlist
Owner: Pirate Praveen 

Package https://rubygems.org/gems/semver_dialects



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

2023-05-04 Thread Pirate Praveen
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 3.20 and while trying to update
> it, the build fails with
>
>   13) Failure:
> TestRubyParserV32#test_unless_pre_not__18
> [/usr/lib/ruby/vendor_ruby/pt_testcase.rb:159]:
> failed on input: "unless not b then a end".
> --- expected
> +++ actual
> @@ -1 +1,4 @@
> -s(:if, s(:call, nil, :b), s(:call, nil, :a), nil)
> +s(:if,
> + s(:call, s(:call, nil, :b).line(1), :!).line(1),
> + nil,
> + s(:call, nil, :a).line(1)).line(1)
>
>
>   14) Failure:
> TestRubyParserV32#test_str_question_literal__18
> [/usr/lib/ruby/vendor_ruby/pt_testcase.rb:159]:
> failed on input: "?a".
> --- expected
> +++ actual
> @@ -1 +1 @@
> -s(:lit, 97)
> +s(:str, "a").line(1)
>
>
>   15) Failure:
> TestRubyParserV32#test_while_pre_not__18
> [/usr/lib/ruby/vendor_ruby/pt_testcase.rb:159]:
> failed on input: "while not true do\n  (1 + 1)\nend".
> --- expected
> +++ actual
> @@ -1 +1,4 @@
> -s(:until, s(:true), s(:call, s(:lit, 1), :+, s(:lit, 1)), true)
> +s(:while,
> + s(:call, s(:true).line(1), :!).line(1),
> + s(:call, s(:lit, 1).line(2), :+, s(:lit, 1).line(2)).line(2),
> + true).line(1)
>
>
>   16) Failure:
> TestRubyParserV32#test_unless_post_not__18
> [/usr/lib/ruby/vendor_ruby/pt_testcase.rb:159]:
> failed on input: "a unless not b".
> --- expected
> +++ actual
> @@ -1 +1,4 @@
> -s(:if, s(:call, nil, :b), s(:call, nil, :a), nil)
> +s(:if,
> + s(:call, s(:call, nil, :b).line(1), :!).line(1),
> + nil,
> + s(:call, nil, :a).line(1)).line(1)
>
>

Running the tests like upstream would with ruby 3.1 installed via rvm, 
the same errors are reproduced.


https://github.com/seattlerb/ruby_parser/issues/337#issuecomment-1535023385



Bug#1034996: libomemo0: missing Breaks+Replaces for libomemo-dev when upgrading from bullseye

2023-05-04 Thread Pirate Praveen
On Thu, 27 Apr 2023 14:59:11 +0200 Helmut Grohne  
wrote:

> Package: libomemo0
> Version: 0.8.1-1
> Severity: serious
> Justification: dpkg unpack error
>
> Attempting to unpack libomemo0/0.8.1-1 from Debian bookworm
> on a minimal Debian bullseye with libomemo-dev/0.7.0-1
> installed, causes an unpack error from dpkg due to
> /usr/lib/x86_64-linux-gnu/libomemo.so being contained in both 
packages.

>
> | (Reading database ... 12426 files and directories currently 
installed.)

> | Preparing to unpack ./libomemo0_0.8.1-1_amd64.deb ...
> | Unpacking libomemo0:amd64 (0.8.1-1) over (0.7.0-1) ...
> | dpkg: error processing archive ./libomemo0_0.8.1-1_amd64.deb 
(--unpack):
> |  trying to overwrite '/usr/lib/x86_64-linux-gnu/libomemo.so', 
which is also in package libomemo-dev:amd64 0.7.0-1

> | Processing triggers for libc-bin (2.31-13+deb11u5) ...
> | Errors were encountered while processing:
> |  ./libomemo0_0.8.1-1_amd64.deb
>
>
> Please ensure that libomemo0 has sufficient Breaks and Replaces 
declarations.

>
> Helmut
>
>

I could add the Breaks and Replaces, but looks like moving .so link out 
of -dev package is wrong as per lintian warning.


W: libomemo0: lacks-unversioned-link-to-shared-library example: 
usr/lib/x86_64-linux-gnu/libomemo.so 
[usr/lib/x86_64-linux-gnu/libomemo.so.0.8.1]
W: libomemo0: link-to-shared-library-in-wrong-package 
usr/lib/x86_64-linux-gnu/libomemo.so.0.8.1 
[usr/lib/x86_64-linux-gnu/libomemo.so]


This was moved to libomemo-dev in commit 
6ebca2f07eed072226503432b6149e671341f2c4 Should we move back 
libomemo.so to libomemo-dev ?




Bug#1033466: libabsl-dev: Please update ASAP

2023-04-28 Thread Pirate Praveen
On Sun, 26 Mar 2023 21:08:31 -0400 Benjamin Barenblat 
 wrote:

> Control: owner 1033466 !
>
> I’ll get 20230125.1 into experimental soon.
>
>
I have built a newer version, details here
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034908

Though it needs some more tweaks to be used in protobuf, it may already 
be enough for OR-Tools


See https://salsa.debian.org/debian/abseil/-/merge_requests/1



Bug#1035045: Please ship libgtest.so and libgmock.so for building libabsl-dev

2023-04-28 Thread Pirate Praveen

Package: libgmock-dev,libgtest-dev
Version: 1.12.1-0.2
Severity: important
Control: block 1034908 by -1

Newer libabsl-dev needs lbgtest.so and libgmock.so for building some 
shared libraries.


dpkg-shlibdeps: error: cannot find library libgtest.so.1.12.1 needed by
debian/libabsl20230125/usr/lib/x86_64-linux-gnu/libabsl_spinlock_test_common.so.20230125.0.0
(ELF format: 'elf64-x86-64' abi: '0201003e'; RPATH: '')
dpkg-shlibdeps: error: cannot find library libgmock.so.1.12.1 needed by
debian/libabsl20230125/usr/lib/x86_64-linux-gnu/libabsl_scoped_mock_log.so.20230125.0.0
(ELF format: 'elf64-x86-64' abi: '0201003e'; RPATH: '')

See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034908



Bug#1034908: Update libabsl-dev to new upstream version/snapshot for protobuf

2023-04-27 Thread Pirate Praveen

Control: tags -1 patch

On Thu, 27 Apr 2023 21:41:43 +0530 Pirate Praveen 
 wrote:

> After adding and adapting the patch from upstream,

attaching the patch if anyone wants to try

From 807763a7f57dcf0ba4af7c3b218013e8f525e811 Mon Sep 17 00:00:00 2001
From: Derek Mauro 
Date: Thu, 2 Mar 2023 17:32:02 -0800
Subject: [PATCH] CMake: Install TESTONLY libraries and their dependencies when
 they are built

https://github.com/abseil/abseil-cpp/issues/1407

PiperOrigin-RevId: 513684529
Change-Id: Ie0a164eea32becfef8f8e4a112aee158fd93dd7e
---
 CMake/AbseilHelpers.cmake | 92 +++
 1 file changed, 44 insertions(+), 48 deletions(-)

--- a/CMake/AbseilHelpers.cmake
+++ b/CMake/AbseilHelpers.cmake
@@ -153,52 +153,55 @@
 
   # Generate a pkg-config file for every library:
   if(ABSL_ENABLE_INSTALL)
-if(NOT ABSL_CC_LIB_TESTONLY)
-  if(absl_VERSION)
-set(PC_VERSION "${absl_VERSION}")
-  else()
-set(PC_VERSION "head")
-  endif()
-  if(NOT _build_type STREQUAL "dll")
-set(LNK_LIB "${LNK_LIB} -labsl_${_NAME}")
-  endif()
-  foreach(dep ${ABSL_CC_LIB_DEPS})
-if(${dep} MATCHES "^absl::(.*)")
-  # for DLL builds many libs are not created, but add
-  # the pkgconfigs nevertheless, pointing to the dll.
-  if(_build_type STREQUAL "dll")
-# hide this MATCHES in an if-clause so it doesn't overwrite
-# the CMAKE_MATCH_1 from (${dep} MATCHES "^absl::(.*)")
-if(NOT PC_DEPS MATCHES "abseil_dll")
-  # Join deps with commas.
-  if(PC_DEPS)
-set(PC_DEPS "${PC_DEPS},")
-  endif()
-  # don't duplicate dll-dep if it exists already
-  set(PC_DEPS "${PC_DEPS} abseil_dll = ${PC_VERSION}")
-  set(LNK_LIB "${LNK_LIB} -labseil_dll")
-endif()
-  else()
+if(absl_VERSION)
+  set(PC_VERSION "${absl_VERSION}")
+else()
+  set(PC_VERSION "head")
+endif()
+if(NOT _build_type STREQUAL "dll")
+  set(LNK_LIB "${LNK_LIB} -labsl_${_NAME}")
+endif()
+foreach(dep ${ABSL_CC_LIB_DEPS})
+  if(${dep} MATCHES "^absl::(.*)")
+# for DLL builds many libs are not created, but add
+# the pkgconfigs nevertheless, pointing to the dll.
+if(_build_type STREQUAL "dll")
+  # hide this MATCHES in an if-clause so it doesn't overwrite
+  # the CMAKE_MATCH_1 from (${dep} MATCHES "^absl::(.*)")
+  if(NOT PC_DEPS MATCHES "abseil_dll")
 # Join deps with commas.
 if(PC_DEPS)
   set(PC_DEPS "${PC_DEPS},")
 endif()
-set(PC_DEPS "${PC_DEPS} absl_${CMAKE_MATCH_1} = ${PC_VERSION}")
+# don't duplicate dll-dep if it exists already
+set(PC_DEPS "${PC_DEPS} abseil_dll = ${PC_VERSION}")
+set(LNK_LIB "${LNK_LIB} -labseil_dll")
   endif()
-endif()
-  endforeach()
-  foreach(cflag ${ABSL_CC_LIB_COPTS})
-if(${cflag} MATCHES "^(-Wno|/wd)")
-  # These flags are needed to suppress warnings that might fire in our headers.
-  set(PC_CFLAGS "${PC_CFLAGS} ${cflag}")
-elseif(${cflag} MATCHES "^(-W|/w[1234eo])")
-  # Don't impose our warnings on others.
 else()
   set(PC_CFLAGS "${PC_CFLAGS} ${cflag}")
+  # Join deps with commas.
+  if(PC_DEPS)
+set(PC_DEPS "${PC_DEPS},")
+  endif()
+  set(PC_DEPS "${PC_DEPS} absl_${CMAKE_MATCH_1} = ${PC_VERSION}")
 endif()
-  endforeach()
-  string(REPLACE ";" " " PC_LINKOPTS "${ABSL_CC_LIB_LINKOPTS}")
-  FILE(GENERATE OUTPUT "${CMAKE_BINARY_DIR}/lib/pkgconfig/absl_${_NAME}.pc" CONTENT "\
+  endif()
+endforeach()
+foreach(cflag ${ABSL_CC_LIB_COPTS})
+  if(${cflag} MATCHES "^(-Wno|/wd)")
+# These flags are needed to suppress warnings that might fire in our headers.
+set(PC_CFLAGS "${PC_CFLAGS} ${cflag}")
+  elseif(${cflag} MATCHES "^(-W|/w[1234eo])")
+# Don't impose our warnings on others.
+  elseif(${cflag} MATCHES "^-m")
+# Don't impose CPU instruction requirements on others, as
+# the code performs feature detection on runtime.
+  else()
+set(PC_CFLAGS "${PC_CFLAGS} ${cflag}")
+  endif()
+endforeach()
+string(REPLACE ";" " " PC_LINKOPTS "${ABSL_CC_LIB_LINKOPTS}")
+FILE(GENERATE OUTPUT "${CMAKE_BINARY_DIR}/lib/pkgconfig/absl_${_NAME}.pc" CONTENT "\
 prefix=${CMAKE_INSTALL_PRE

Bug#1034138: Backport message retraction support from upstream master

2023-04-27 Thread Pirate Praveen

Control: retitle -1 Update ejabberd to 23.04

On Mon, 10 Apr 2023 17:08:15 +0530 Pirate Praveen 
 wrote:

>
>
> On Mon, Apr 10 2023 at 04:50:05 PM +05:30:00 +05:30:00, Pirate 
Praveen

>  wrote:
> > I guess
> > 
https://salsa.debian.org/praveen/ejabberd/-/blob/master/debian/patches/src.includes.patch

> > will need to be updated, but I'm not familiar with erlang to figure
> > this out myself. Any help is welcome.
>
> Figured out this, I need to update erlang-p1-xmpp as well. After
> updating erlang-p1-xmpp, I could build ejabberd as well.

Support for message retractions is part of 23.04 release, so uploading 
a new version to experimental would be nice. Until freeze is lifted, 
this could be shipped via fasttrack.debian.net as well[1].


[1] https://salsa.debian.org/fasttrack-team/support/-/issues/49



Bug#1034908: Update libabsl-dev to new upstream version/snapshot for protobuf

2023-04-27 Thread Pirate Praveen
On Thu, 27 Apr 2023 20:14:46 +0530 Pirate Praveen 
 wrote:

> Looks like this is a bug in abseil itself
> https://github.com/abseil/abseil-cpp/issues/1407

After adding and adapting the patch from upstream, the build fails with 
below error. I can't find libgtest.so in any package.


apt-file list libgtest-dev gives
libgtest-dev: /usr/lib/x86_64-linux-gnu/libgtest.a

so we should either ship .so in libgtest-dev or adapt abseil to link 
against libgtest.a


dpkg-shlibdeps: error: cannot find library libgtest.so.1.12.1 needed by 
debian/libabsl20230125/usr/lib/x86_64-linux-gnu/libabsl_per_thread_sem_test_common.so.20230125.0.0 
(ELF format: 'elf64-x86-64' abi: '0201003e'; RPATH: '')
dpkg-shlibdeps: error: cannot find library libgtest.so.1.12.1 needed by 
debian/libabsl20230125/usr/lib/x86_64-linux-gnu/libabsl_spinlock_test_common.so.20230125.0.0 
(ELF format: 'elf64-x86-64' abi: '0201003e'; RPATH: '')
dpkg-shlibdeps: error: cannot find library libgmock.so.1.12.1 needed by 
debian/libabsl20230125/usr/lib/x86_64-linux-gnu/libabsl_scoped_mock_log.so.20230125.0.0 
(ELF format: 'elf64-x86-64' abi: '0201003e'; RPATH: '')
dpkg-shlibdeps: error: cannot find library libgtest.so.1.12.1 needed by 
debian/libabsl20230125/usr/lib/x86_64-linux-gnu/libabsl_scoped_mock_log.so.20230125.0.0 
(ELF format: 'elf64-x86-64' abi: '0201003e'; RPATH: '')
dpkg-shlibdeps: error: cannot find library libgtest.so.1.12.1 needed by 
debian/libabsl20230125/usr/lib/x86_64-linux-gnu/libabsl_exception_safety_testing.so.20230125.0.0 
(ELF format: 'elf64-x86-64' abi: '0201003e'; RPATH: '')
dpkg-shlibdeps: error: cannot find library libgtest.so.1.12.1 needed by 
debian/libabsl20230125/usr/lib/x86_64-linux-gnu/libabsl_log_internal_test_matchers.so.20230125.0.0 
(ELF format: 'elf64-x86-64' abi: '0201003e'; RPATH: '')
dpkg-shlibdeps: error: cannot find library libgtest.so.1.12.1 needed by 
debian/libabsl20230125/usr/lib/x86_64-linux-gnu/libabsl_log_internal_test_helpers.so.20230125.0.0 
(ELF format: 'elf64-x86-64' abi: '0201003e'; RPATH: '')

dpkg-shlibdeps: error: cannot continue due to the errors listed above
Note: libraries are not searched in other binary packages that do not 
have any shlibs or symbols file.




Bug#1034908: Update libabsl-dev to new upstream version/snapshot for newer protobuf

2023-04-27 Thread Pirate Praveen
On Thu, 27 Apr 2023 19:16:36 +0530 Pirate Praveen 
 wrote:

> though now the error changed to,
> CMake Error at cmake/tests.cmake:97 (target_link_libraries):
>   Target "tests" links to:
>
> absl::scoped_mock_log
>
>   but the target was not found. Possible reasons include:
>
> * There is a typo in the target name.
> * A find_package call is missing for an IMPORTED target.
> * An ALIAS target is missing.
>
> Call Stack (most recent call first):
>   CMakeLists.txt:401 (include)

Looks like this is a bug in abseil itself
https://github.com/abseil/abseil-cpp/issues/1407



Bug#1034668: Please update to new upstream release 3.22.3 in experimental

2023-04-27 Thread Pirate Praveen
With a newer libabsl-dev from 
https://people.debian.org/~praveen/new/pool/main/a/abseil/, the error 
changed to


CMake Error at cmake/tests.cmake:97 (target_link_libraries):
Target "tests" links to:

  absl::scoped_mock_log

but the target was not found. Possible reasons include:

  * There is a typo in the target name.
  * A find_package call is missing for an IMPORTED target.
  * An ALIAS target is missing.

Call Stack (most recent call first):
CMakeLists.txt:401 (include)



Bug#1034908: Update libabsl-dev to new upstream version/snapshot for newer protobuf

2023-04-27 Thread Pirate Praveen

Control: forwarded
-1 https://salsa.debian.org/debian/abseil/-/merge_requests/1


On Thu, 27 Apr 2023 16:55:49 +0530 Pirate Praveen 
 wrote:

> Package: libabsl-dev
> Version: 20220623.1-1
> Severity: wishlist
> Control: block 1034668 by -1
> Control: affects -1 protobuf
>
> Please update libabsl-dev so that we can build protobuf 3.22.3 in
> experimental.
>
> CMake Error at cmake/libprotobuf-lite.cmake:26 
(target_link_libraries):

>   Target "libprotobuf-lite" links to:
>
> absl::absl_check
>
>   but the target was not found. Possible reasons include:
>
> * There is a typo in the target name.
> * A find_package call is missing for an IMPORTED target.
> * An ALIAS target is missing.
>
> Call Stack (most recent call first):
>   CMakeLists.txt:354 (include)
>
> If you want to reprpoduce this, a wip version is available at
> https://people.debian.org/~praveen/new/pool/main/p/protobuf/

I have created a merge request with the new upstream version
https://salsa.debian.org/debian/abseil/-/merge_requests/1

though now the error changed to,
CMake Error at cmake/tests.cmake:97 (target_link_libraries):
 Target "tests" links to:

   absl::scoped_mock_log

 but the target was not found. Possible reasons include:

   * There is a typo in the target name.
   * A find_package call is missing for an IMPORTED target.
   * An ALIAS target is missing.

Call Stack (most recent call first):
 CMakeLists.txt:401 (include)



Bug#1034908: Update libabsl-dev to new upstream version/snapshot for newer protobuf

2023-04-27 Thread Pirate Praveen

Package: libabsl-dev
Version: 20220623.1-1
Severity: wishlist
Control: block 1034668 by -1
Control: affects -1 protobuf

Please update libabsl-dev so that we can build protobuf 3.22.3 in 
experimental.


CMake Error at cmake/libprotobuf-lite.cmake:26 (target_link_libraries):
 Target "libprotobuf-lite" links to:

   absl::absl_check

 but the target was not found. Possible reasons include:

   * There is a typo in the target name.
   * A find_package call is missing for an IMPORTED target.
   * An ALIAS target is missing.

Call Stack (most recent call first):
 CMakeLists.txt:354 (include)

If you want to reprpoduce this, a wip version is available at 
https://people.debian.org/~praveen/new/pool/main/p/protobuf/




  1   2   3   4   5   6   7   8   9   10   >