Processed: Re: Bug#1068695: bookworm-pu: package json-smart/2.2-2+deb12u1

2024-05-10 Thread Debian Bug Tracking System
Processing control commands:

> tag -1 confirmed
Bug #1068695 [release.debian.org] bookworm-pu: package json-smart/2.2-2+deb12u1
Added tag(s) confirmed.

-- 
1068695: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068695
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#1068695: bookworm-pu: package json-smart/2.2-2+deb12u1

2024-05-10 Thread Jonathan Wiltshire
Control: tag -1 confirmed


Please go ahead.

Thanks,

-- 
Jonathan Wiltshire  j...@debian.org
Debian Developer http://people.debian.org/~jmw

4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC  74C3 5394 479D D352 4C51
ed25519/0x196418AAEB74C8A1: CA619D65A72A7BADFC96D280196418AAEB74C8A1



Re: Please add a testing suite for riscv64 architecture

2024-05-10 Thread Ansgar šŸ™€



On Fri, 2024-05-10 at 16:56 +, Graham Inggs wrote:
> On Fri, 10 May 2024 at 15:23, Ansgar šŸ™€  wrote:
> > I'm happy to do that, but someone from the release team should ack the
> > request. testing and related suites are their playground after all :-)
> 
> Please go ahead!

Here we go:

+---
| $ for s in ${testing_suites[@]}; do dak admin s-a add ${s} riscv64; done
| Added suite-architecture entry for buildd-testing-backports, riscv64
| Added suite-architecture entry for buildd-testing-proposed-updates, riscv64
| Added suite-architecture entry for testing-backports-debug, riscv64
| Added suite-architecture entry for testing-debug, riscv64
| Added suite-architecture entry for testing-proposed-updates-debug, riscv64
| Added suite-architecture entry for testing, riscv64
| Added suite-architecture entry for testing-backports, riscv64
| Added suite-architecture entry for testing-proposed-updates, riscv64
| Added suite-architecture entry for testing-updates, riscv64
+---

Ansgar



Re: Please add a testing suite for riscv64 architecture

2024-05-10 Thread Graham Inggs
Hi Ansgar

On Fri, 10 May 2024 at 15:23, Ansgar šŸ™€  wrote:
> I'm happy to do that, but someone from the release team should ack the
> request. testing and related suites are their playground after all :-)

Please go ahead!

Regards
Graham



Bug#1070856: bookworm-pu: package riseup-vpn/0.21.11+ds1-5+deb12u1

2024-05-10 Thread Nilesh Patra
Package: release.debian.org
Severity: normal
Tags: bookworm
X-Debbugs-Cc: riseup-...@packages.debian.org, nil...@debian.org
Control: affects -1 + src:riseup-vpn
User: release.debian@packages.debian.org
Usertags: pu

[ Reason ]
The bug got introduced due to a change in the external services that riseup-vpn
interacts with (riseup's servers) and failing to identify their letsencrypt 
certs.

Full details at Bug#1070270

[ Impact ]
The package is rendered unusable and the user will not be able to use riseup-vpn
and connect to the vpn.

[ Tests ]
Tried this on a fresh stable VM with multiple different angles.
This has also been tried on a stable user's machine and the problem is verified
to have been fixed.

[ Risks ]
This is a leaf package and the changes are fairly minimal. Very low risk to 
stable.

[ Checklist ]
  [x] *all* changes are documented in the d/changelog
  [x] I reviewed all changes and I approve them
  [x] attach debdiff against the package in (old)stable
  [x] the issue is verified as fixed in unstable

[ Changes ]
 Add patch to fixup client verification problems with
 riseup-vpn which renders the package useless otherwise.
 At the moment, the current code is unable to identify the
 letsencrypt certs. Used a systempool for the same and create
 a newcertpool as a fallback. Also added a Depends in d/control
 for ca-certificates for the same reason.

[ Other info ]
Since this is a leaf package and the breakage is due to external services, this 
may be a
candidate for stable-updates suite as per 
https://www.debian.org/doc/manuals/developers-reference/pkgs.html#special-case-the-stable-updates-suite

> Examples of circumstances in which the upload may qualify for such treatment 
> are:
> ...
> Uploads to stable-updates should target their suite name in the changelog as 
> usual, e.g. bookworm.

Since I was confident that this should be accepted, I did a (source-only) 
dput/upload.
diff -Nru riseup-vpn-0.21.11+ds1/debian/changelog 
riseup-vpn-0.21.11+ds1/debian/changelog
--- riseup-vpn-0.21.11+ds1/debian/changelog 2023-03-09 09:51:22.0 
+0530
+++ riseup-vpn-0.21.11+ds1/debian/changelog 2024-05-10 20:13:39.0 
+0530
@@ -1,3 +1,15 @@
+riseup-vpn (0.21.11+ds1-5+deb12u1) bookworm; urgency=medium
+
+  * Add patch to fixup client verification problems with
+riseup-vpn which renders the package useless otherwise.
+At the moment, the current code is unable to identify the
+letsencrypt certs. Used a systempool for the same and create
+a newcertpool as a fallback. Also added a Depends in d/control
+for ca-certificates for the same reason.
+(Closes: #1070270)
+
+ -- Nilesh Patra   Fri, 10 May 2024 20:13:39 +0530
+
 riseup-vpn (0.21.11+ds1-5) unstable; urgency=medium
 
   * Add procps, iproute2 and iptables to Depends (Closes: #1031905)
diff -Nru riseup-vpn-0.21.11+ds1/debian/control 
riseup-vpn-0.21.11+ds1/debian/control
--- riseup-vpn-0.21.11+ds1/debian/control   2023-03-09 09:51:22.0 
+0530
+++ riseup-vpn-0.21.11+ds1/debian/control   2024-05-10 20:13:39.0 
+0530
@@ -52,6 +52,7 @@
 Architecture: any
 Depends: ${shlibs:Depends},
  ${misc:Depends},
+ ca-certificates,
  iproute2,
  iptables,
  pkexec,
diff -Nru riseup-vpn-0.21.11+ds1/debian/patches/add-system-certs.patch 
riseup-vpn-0.21.11+ds1/debian/patches/add-system-certs.patch
--- riseup-vpn-0.21.11+ds1/debian/patches/add-system-certs.patch
1970-01-01 05:30:00.0 +0530
+++ riseup-vpn-0.21.11+ds1/debian/patches/add-system-certs.patch
2024-05-10 20:13:39.0 +0530
@@ -0,0 +1,27 @@
+From 14cf64b10a97c29688f252a7d9d3481c8484aa1d Mon Sep 17 00:00:00 2001
+From: max b 
+Date: Wed, 8 Mar 2023 12:41:45 -0800
+Subject: [PATCH] Add system certs to bonafide
+
+lilypad/float is now using letsencrypt certs for vpnweb so instead of
+instantiating an empty cert pool, we can just use the system pool and
+then add the manually configured cert for backwards compatibility.
+---
+ pkg/vpn/bonafide/bonafide.go | 6 +-
+ 1 file changed, 5 insertions(+), 1 deletion(-)
+
+--- a/pkg/vpn/bonafide/bonafide.go
 b/pkg/vpn/bonafide/bonafide.go
+@@ -94,7 +94,11 @@
+ 
+ // New Bonafide: Initializes a Bonafide object. By default, no Credentials 
are passed.
+ func New() *Bonafide {
+-  certs := x509.NewCertPool()
++  certs, err := x509.SystemCertPool()
++  if err != nil {
++  log.Println("Error loading SystemCertPool, falling back to 
empty pool")
++  certs = x509.NewCertPool()
++  }
+   certs.AppendCertsFromPEM(config.CaCert)
+   client := &http.Client{
+   Transport: &http.Transport{
diff -Nru riseup-vpn-0.21.11+ds1/debian/patches/series 
riseup-vpn-0.21.11+ds1/debian/patches/series
--- riseup-vpn-0.21.11+ds1/debian/patches/series2023-02-26 
02:39:10.0 +0530
+++ riseup-vpn-0.21.11+ds1/debian/patches/series2024-05-10 
20:13:39.

Processed: bookworm-pu: package riseup-vpn/0.21.11+ds1-5+deb12u1

2024-05-10 Thread Debian Bug Tracking System
Processing control commands:

> affects -1 + src:riseup-vpn
Bug #1070856 [release.debian.org] bookworm-pu: package 
riseup-vpn/0.21.11+ds1-5+deb12u1
Added indication that 1070856 affects src:riseup-vpn

-- 
1070856: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070856
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Re: Please add a testing suite for riscv64 architecture

2024-05-10 Thread Ansgar šŸ™€
Hi

On Fri, 2024-05-10 at 14:19 +0200, Aurelien Jarno wrote:
> The riscv64 port reached a point where it should be possible to add a
> testing suite. Most of packages from unstable have now been rebuilt on
> official buildds [1], and the release team confirmed that britney2 is
> ready for that.
> 
> Therefore could you please add a testing suite for riscv64 architecture?

I'm happy to do that, but someone from the release team should ack the
request. testing and related suites are their playground after all :-)

Ansgar



Processed: transition: gdal

2024-05-10 Thread Debian Bug Tracking System
Processing control commands:

> affects -1 + src:gdal
Bug #1070852 [release.debian.org] transition: gdal
Added indication that 1070852 affects src:gdal
> forwarded -1 https://release.debian.org/transitions/html/auto-gdal.html
Bug #1070852 [release.debian.org] transition: gdal
Set Bug forwarded-to-address to 
'https://release.debian.org/transitions/html/auto-gdal.html'.

-- 
1070852: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070852
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#1070852: transition: gdal

2024-05-10 Thread Bas Couwenberg
Package: release.debian.org
Severity: normal
X-Debbugs-Cc: g...@packages.debian.org
Control: affects -1 + src:gdal
User: release.debian@packages.debian.org
Usertags: transition
Control: forwarded -1 https://release.debian.org/transitions/html/auto-gdal.html

For the Debian GIS team I'd like to transition to GDAL 3.8.0.

All reverse dependencies except python-django and facet-analyser rebuilt 
successfully with GDAL 3.9.0 from experimental as summarized below.


python-django (3:4.2.11-1) FTBFS due to unrelated test failures. (#1042637)

facet-analyser (0.0~git20221121142040.6be10b8+ds1-3) FTBFS due to uninstallable 
build dependencies. (#1040334)


Bugreports can be found using the gdal-3.9 usertag:

 
https://bugs.debian.org/cgi-bin/pkgreport.cgi?users=debian-...@lists.debian.org&tag=gdal-3.9


Transition: gdal

 libgdal34t64 (3.8.5+dfsg-1) -> libgdal35 (3.9.0~beta1+dfsg-1~exp1)

The status of the most recent rebuilds is as follows.

 cloudcompare(2.11.3-7.1)  OK
 fiona   (1.9.6-1) OK
 gmt (6.5.0+dfsg-3)OK
 grass   (8.3.2-1) OK
 libcitygml  (2.5.2-1) OK
 libgeo-gdal-ffi-perl(0.11-2)  OK
 libosmium   (2.20.0-1)OK
 mapcache(1.14.0-4)OK
 mapnik  (3.1.0+ds-7)  OK
 mapproxy(2.0.2+dfsg-1)OK
 mapserver   (8.0.1-4) OK
 merkaartor  (0.19.0+ds-5) OK
 mysql-workbench (8.0.32+dfsg-2)   OK
 ncl (6.6.2.dfsg.1-7)  OK
 octave-mapping  (1.4.2-3) OK
 openorienteering-mapper (0.9.5-3.1)   OK
 openscenegraph  (3.6.5+dfsg1-8)   OK
 paraview(5.11.2+dfsg-6)   OK
 pgsql-ogr-fdw   (1.1.4-3) OK
 pktools (2.6.7.6+ds-6)OK
 postgis (3.4.2+dfsg-1)OK
 python-django   (3:4.2.11-1)  FTBFS (#1042637)
 qmapshack   (1.17.1-1)OK
 r-cran-sf   (1.0-15+dfsg-1)   OK
 r-cran-terra(1.7-65-1)OK
 rasterio(1.3.10-2)OK
 saga(9.4.0+dfsg-1)OK
 vtk9(9.1.0+really9.1.0+dfsg2-7.1) OK

 facet-analyser  (0.0~git20221121142040.6be10b8+ds1-3) FTBFS (#1040334)
 libgdal-grass   (1:1.0.2-7)   OK
 opencv  (4.6.0+dfsg-13.1) OK
 osmcoastline(2.4.0-2) OK
 qgis(3.34.6+dfsg-1)   OK
 sumo(1.18.0+dfsg-3)   OK


Kind Regards,

Bas



Please add a testing suite for riscv64 architecture

2024-05-10 Thread Aurelien Jarno
Dear FTP Masters,

The riscv64 port reached a point where it should be possible to add a
testing suite. Most of packages from unstable have now been rebuilt on
official buildds [1], and the release team confirmed that britney2 is
ready for that.

Therefore could you please add a testing suite for riscv64 architecture?

Thanks
Aurelien


[1] https://lists.debian.org/debian-riscv/2024/05/msg0.html

-- 
Aurelien Jarno  GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://aurel32.net


signature.asc
Description: PGP signature


Bug#1069891: bookworm-pu: package ansible/7.7.0+dfsg-3+deb12u1

2024-05-10 Thread Lee Garrett
I have just pushed some meta-data updates, and also a change that fixes 
CVE-2023-4237 in this package. See the commit logs here:


https://salsa.debian.org/python-team/packages/ansible/-/commits/debian/bookworm-proposed/



Processed: Re: Bug#1067842: transition: octave-9

2024-05-10 Thread Debian Bug Tracking System
Processing control commands:

> tags -1 + confirmed
Bug #1067842 [release.debian.org] transition: octave-9
Added tag(s) confirmed.

-- 
1067842: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067842
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#1067842: transition: octave-9

2024-05-10 Thread Graham Inggs
Control: tags -1 + confirmed

Hi SĆ©bastien

On Thu, 9 May 2024 at 08:09, Sebastian Ramacher  wrote:
> plplot is involved in the gnat and octave transitions. So let's do this
> one after gnat is done.

gnat 13 has migrated, please go ahead.

Regards
Graham



Bug#1065309: marked as done (transition: gnat (12 -> 13 + time_t64))

2024-05-10 Thread Debian Bug Tracking System
Your message dated Fri, 10 May 2024 09:54:01 +
with message-id 

and subject line Re: Bug#1065309: transition: gnat (12 -> 13 + time_t64)
has caused the Debian Bug report #1065309,
regarding transition: gnat (12 -> 13 + time_t64)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1065309: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065309
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---Ā BeginĀ MessageĀ ---

Package: release.debian.org
X-Debbugs-CC: Nicolas Boulenguez 

when preparing GCC packages for time_t64, I noticed that we'll have an 
ABI change for libgnat as well.  Instead of doing a gnat 12 -> 12+t64 
transition, let's do a gnat 12 -> 13+t64 transition instead.  According 
to Nicolas, packages are already prepared in experimental.


Waiting with the transition until all t64 stuff is finished doesn't work 
well, packages which need binNMUs will ftbfs.
---Ā End MessageĀ ---
---Ā BeginĀ MessageĀ ---
Hi Rafael and Nicolas

On Wed, 8 May 2024 at 19:58, Rafael LaboissiĆØre  wrote:
> I will soon upload version 5.15.0+dfsg2-11, with the fix proposed by
> Nicolas in Bug#1070746.

Thanks for the quick turnaround!

gnat 13 has migrated.

Regards
Graham---Ā End MessageĀ ---


Processed: Re: Bug#1060019: transition: poppler 24.02

2024-05-10 Thread Debian Bug Tracking System
Processing control commands:

> tags -1 confirmed
Bug #1060019 [release.debian.org] transition: poppler 24.02
Added tag(s) confirmed.

-- 
1060019: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060019
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#1060019: transition: poppler 24.02

2024-05-10 Thread Emilio Pozuelo Monfort

Control: tags -1 confirmed

On 05/05/2024 23:33, Jeremy BĆ­cha wrote:

Control: retitle -1 transition: poppler 24.02
Control: affects -1 src:poppler

Since originally requesting this transition, I have updated the
version to 24.02. I believe all reverse dependencies can be binNMU'd
for this.


Go ahead.

Emilio



NEW changes in oldstable-new

2024-05-10 Thread Debian FTP Masters
Processing changes file: 
shim-helpers-amd64-signed_1+15.8+1~deb11u1_amd64-buildd.changes
  ACCEPT
Processing changes file: 
shim-helpers-arm64-signed_1+15.8+1~deb11u1_arm64-buildd.changes
  ACCEPT
Processing changes file: 
shim-helpers-i386-signed_1+15.8+1~deb11u1_i386-buildd.changes
  ACCEPT



NEW changes in stable-new

2024-05-10 Thread Debian FTP Masters
Processing changes file: 
shim-helpers-amd64-signed_1+15.8+1~deb12u1_amd64-buildd.changes
  ACCEPT
Processing changes file: 
shim-helpers-arm64-signed_1+15.8+1~deb12u1_arm64-buildd.changes
  ACCEPT
Processing changes file: 
shim-helpers-i386-signed_1+15.8+1~deb12u1_i386-buildd.changes
  ACCEPT