Bug#999434: bullseye-pu: package freeipmi/1.6.6-4+deb11u1

2021-11-10 Thread Mattia Rizzolo 
On Wed, Nov 10, 2021 at 11:55:03PM +0100, Fabio Fantoni wrote:
>   [x] attach debdiff against the package in (old)stable

Since this is a small likely uncontroversial change, I proceeded to
upload it already.

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
More about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature

Bug#999434: bullseye-pu: package freeipmi/1.6.6-4+deb11u1

2021-11-10 Thread Fabio Fantoni 

Package: release.debian.org
Severity: normal
Tags: bullseye
User: release.debian@packages.debian.org
Usertags: pu

[ Reason ]
There are wrong pkg-config file path in *-dev packages

[ Impact ]
As reported in #996325 for one of -dev package, that make build against
them fails or silently build without the freeipmi part

[ Tests ]
pkg-config files path are now correct:
http://debomatic-amd64.debian.net/distribution#bullseye/freeipmi/1.6.6-4+deb11u1/

[ Risks ]
No regression risk with this small fix FWIK

[ 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 ]
pkg-config files path in debian/*-dev.install

[ Other info ]
n/a

diff -Nru freeipmi-1.6.6/debian/changelog freeipmi-1.6.6/debian/changelog
--- freeipmi-1.6.6/debian/changelog 2021-07-28 16:41:51.0 +0200
+++ freeipmi-1.6.6/debian/changelog 2021-10-31 18:05:13.0 +0100
@@ -1,3 +1,9 @@
+freeipmi (1.6.6-4+deb11u1) bullseye; urgency=medium
+
+  * Fix .pc files path in -dev packages. Thanks to наб (Closes: #996325)
+
+ -- Fabio Fantoni   Sun, 31 Oct 2021 18:05:13 +0100
+
 freeipmi (1.6.6-4) unstable; urgency=medium
 
   [ Andreas Beckmann ]
diff -Nru freeipmi-1.6.6/debian/control freeipmi-1.6.6/debian/control
--- freeipmi-1.6.6/debian/control   2021-07-28 16:41:51.0 +0200
+++ freeipmi-1.6.6/debian/control   2021-10-31 18:05:13.0 +0100
@@ -15,7 +15,7 @@
 Rules-Requires-Root: binary-targets
 Homepage: https://www.gnu.org/software/freeipmi/
 Vcs-Browser: https://salsa.debian.org/debian/freeipmi
-Vcs-Git: https://salsa.debian.org/debian/freeipmi.git
+Vcs-Git: https://salsa.debian.org/debian/freeipmi.git -b bullseye
 
 Package: freeipmi
 Architecture: all
diff -Nru freeipmi-1.6.6/debian/gbp.conf freeipmi-1.6.6/debian/gbp.conf
--- freeipmi-1.6.6/debian/gbp.conf  2021-07-28 16:41:51.0 +0200
+++ freeipmi-1.6.6/debian/gbp.conf  2021-10-31 18:05:13.0 +0100
@@ -3,6 +3,7 @@
 upstream-tag = upstream/%(version)s
 debian-tag = debian/%(version)s
 pristine-tar = True
+debian-branch = bullseye
 
 # Options only affecting gbp buildpackage
 [buildpackage]
diff -Nru freeipmi-1.6.6/debian/.gitlab-ci.yml 
freeipmi-1.6.6/debian/.gitlab-ci.yml
--- freeipmi-1.6.6/debian/.gitlab-ci.yml2021-07-28 16:41:51.0 
+0200
+++ freeipmi-1.6.6/debian/.gitlab-ci.yml2021-10-31 18:05:13.0 
+0100
@@ -3,4 +3,4 @@
  - https://salsa.debian.org/salsa-ci-team/pipeline/raw/master/pipeline-jobs.yml
 
 variables:
- RELEASE: 'unstable'
+ RELEASE: 'bullseye'
diff -Nru freeipmi-1.6.6/debian/libfreeipmi-dev.install 
freeipmi-1.6.6/debian/libfreeipmi-dev.install
--- freeipmi-1.6.6/debian/libfreeipmi-dev.install   2021-07-28 
16:41:51.0 +0200
+++ freeipmi-1.6.6/debian/libfreeipmi-dev.install   2021-10-31 
18:05:13.0 +0100
@@ -1,5 +1,5 @@
 usr/include/freeipmi
 usr/lib/libfreeipmi.a
 usr/lib/libfreeipmi.so
-usr/lib/pkgconfig/libfreeipmi.pc 
usr/lib/${DEB_HOST_MULTIARCH}/pkgconfig/libfreeipmi.pc
+usr/lib/pkgconfig/libfreeipmi.pc usr/lib/${DEB_HOST_MULTIARCH}/pkgconfig
 usr/share/man/man3/libfreeipmi.3
diff -Nru freeipmi-1.6.6/debian/libipmiconsole-dev.install 
freeipmi-1.6.6/debian/libipmiconsole-dev.install
--- freeipmi-1.6.6/debian/libipmiconsole-dev.install2021-07-28 
16:41:51.0 +0200
+++ freeipmi-1.6.6/debian/libipmiconsole-dev.install2021-10-31 
18:05:13.0 +0100
@@ -1,5 +1,5 @@
 usr/include/ipmiconsole.h
 usr/lib/libipmiconsole.a
 usr/lib/libipmiconsole.so
-usr/lib/pkgconfig/libipmiconsole.pc 
usr/lib/${DEB_HOST_MULTIARCH}/pkgconfig/libipmiconsole.pc
+usr/lib/pkgconfig/libipmiconsole.pc usr/lib/${DEB_HOST_MULTIARCH}/pkgconfig
 usr/share/man/man3/libipmiconsole.3
diff -Nru freeipmi-1.6.6/debian/libipmidetect-dev.install 
freeipmi-1.6.6/debian/libipmidetect-dev.install
--- freeipmi-1.6.6/debian/libipmidetect-dev.install 2021-07-28 
16:41:51.0 +0200
+++ freeipmi-1.6.6/debian/libipmidetect-dev.install 2021-10-31 
18:05:13.0 +0100
@@ -1,5 +1,5 @@
 usr/include/ipmidetect.h
 usr/lib/libipmidetect.a
 usr/lib/libipmidetect.so
-usr/lib/pkgconfig/libipmidetect.pc 
usr/lib/${DEB_HOST_MULTIARCH}/pkgconfig/libipmidetect.pc
+usr/lib/pkgconfig/libipmidetect.pc usr/lib/${DEB_HOST_MULTIARCH}/pkgconfig
 usr/share/man/man3/libipmidetect.3
diff -Nru freeipmi-1.6.6/debian/libipmimonitoring-dev.install 
freeipmi-1.6.6/debian/libipmimonitoring-dev.install
--- freeipmi-1.6.6/debian/libipmimonitoring-dev.install 2021-07-28 
16:41:51.0 +0200
+++ freeipmi-1.6.6/debian/libipmimonitoring-dev.install 2021-10-31 
18:05:13.0 +0100
@@ -1,5 +1,5 @@
 usr/include/ipmi_monitoring*.h
 usr/lib/libipmimonitoring.a
 usr/lib/libipmimonitoring.so
-usr/lib/pkgconfig/libipmimonitoring.pc 
usr/lib/${DEB_HOST_MULTIARCH}/pkgconfig/libipmimonitoring.pc
+usr/lib/pkgconfig/libipmimonitoring.pc

Bug#940059: marked as done (buster-pu: package publicsuffix/20190925.1705-0+deb10u1)

2021-11-10 Thread Debian Bug Tracking System 
Your message dated Wed, 10 Nov 2021 16:33:51 -0500
with message-id <87mtmbpuf4@fifthhorseman.net>
and subject line Re: Bug#940059: buster-pu: package 
publicsuffix/20190904.1802-0+deb10u1
has caused the Debian Bug report #940059,
regarding buster-pu: package publicsuffix/20190925.1705-0+deb10u1
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.)


-- 
940059: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=940059
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
Tags: buster
User: release.debian@packages.debian.org
Usertags: pu
Control: affects -1 src:publicsuffix

Please consider an update to publicsuffix in debian buster.

This package reflects the state of the network, and keeping it current
is useful for all the packages that depend on it.

The debdiff from the previous version in buster is attached.

This proposed release is also available at the
"publicsuffix_debian/20190904.1802-0+deb10u1" tag on the "debian/buster" branch 
at
the git repo for publicsuffix packaging:

https://salsa.debian.org/debian/publicsuffix

Please followup on this ticket to confirm whether I should upload this
revision to buster.



../publicsuffix_20190415.1030-1_20190904.1802-0+deb10u1.debdiff.gz
Description: Binary data
--- End Message ---
--- Begin Message ---
Closing #940059 in favor of the more-recent #999430.--- End Message ---

Bug#941615: marked as done (buster-pu: package publicsuffix/20190925.1705-0+deb10u1)

2021-11-10 Thread Debian Bug Tracking System 
Your message dated Wed, 10 Nov 2021 16:33:51 -0500
with message-id <87mtmbpuf4@fifthhorseman.net>
and subject line Re: Bug#940059: buster-pu: package 
publicsuffix/20190904.1802-0+deb10u1
has caused the Debian Bug report #940059,
regarding buster-pu: package publicsuffix/20190925.1705-0+deb10u1
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.)


-- 
940059: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=940059
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
Tags: buster
User: release.debian@packages.debian.org
Usertags: pu
Control: affects -1 src:publicsuffix

Please consider an update to publicsuffix in debian buster.

This package reflects the state of the network, and keeping it current
is useful for all the packages that depend on it.

The debdiff from the previous version in buster is attached.

This proposed release is also available at the
"publicsuffix_debian/20190925.1705-0+deb10u1" tag on the "debian/buster" branch 
at
the git repo for publicsuffix packaging:

https://salsa.debian.org/debian/publicsuffix

Please followup on this ticket to confirm whether I should upload this
revision to buster.



../publicsuffix_20190904.1802-0+deb10u1_20190925.1705-0+deb10u1.debdiff.gz
Description: Binary data
--- End Message ---
--- Begin Message ---
Closing #940059 in favor of the more-recent #999430.--- End Message ---

Bug#999430: buster-pu: package publicsuffix/20211109.1735-0+deb10u1

2021-11-10 Thread Daniel Kahn Gillmor 
Package: release.debian.org
Severity: normal
Tags: buster
User: release.debian@packages.debian.org
Usertags: pu
X-Debbugs-Cc: d...@fifthhorseman.net
Control: affects -1 src:publicsuffix

Please consider an update to publicsuffix in debian buster.

This package reflects the state of the network, and keeping it current
is useful for all the packages that depend on it.

The debdiff from the previous version in buster is attached.

This proposed release is also available at the
"publicsuffix_debian/20211109.1735-0+deb10u1" tag on the "debian/buster" branch 
at
the git repo for publicsuffix packaging:

https://salsa.debian.org/debian/publicsuffix

Please followup on this ticket to confirm whether I should upload this
revision to buster.


publicsuffix_20190925.1705-0+deb10u1_20211109.1735-0+deb10u1.debdiff.gz
Description: application/gzip

Processed: buster-pu: package publicsuffix/20211109.1735-0+deb10u1

2021-11-10 Thread Debian Bug Tracking System 
Processing control commands:

> affects -1 src:publicsuffix
Bug #999430 [release.debian.org] buster-pu: package 
publicsuffix/20211109.1735-0+deb10u1
Added indication that 999430 affects src:publicsuffix

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

Processed: bullseye-pu: package publicsuffix/20211109.1735-0+deb11u1

2021-11-10 Thread Debian Bug Tracking System 
Processing control commands:

> affects -1 src:publicsuffix
Bug #999427 [release.debian.org] bullseye-pu: package 
publicsuffix/20211109.1735-0+deb11u1
Added indication that 999427 affects src:publicsuffix

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

Bug#999427: bullseye-pu: package publicsuffix/20211109.1735-0+deb11u1

2021-11-10 Thread Daniel Kahn Gillmor 
Package: release.debian.org
Severity: normal
Tags: bullseye
User: release.debian@packages.debian.org
Usertags: pu
X-Debbugs-Cc: d...@fifthhorseman.net
Control: affects -1 src:publicsuffix

Please consider an update to publicsuffix in debian bullseye.

This package reflects the state of the network, and keeping it current
is useful for all the packages that depend on it.

The debdiff from the previous version in bullseye is attached.

This proposed release is also available at the
"publicsuffix_debian/20211109.1735-0+deb11u1" tag on the "debian/bullseye" 
branch at
the git repo for publicsuffix packaging:

https://salsa.debian.org/debian/publicsuffix

Please followup on this ticket to confirm whether I should upload this
revision to bullseye.


publicsuffix_20210108.1309-1_20211109.1735-0+deb11u1.debdiff.gz
Description: application/gzip

Convocatoria final

2021-11-10 Thread FOESCO 
Buenos días



Desde FOESCO os informamos acerca de la presente y ÚLTIMA convocatoria de 
Cursos 100% Bonificables con cargo al Crédito de Formación 2021.


El plazo de inscripción se cerrará el próximo VIERNES 12, una vez pasada esta 
fecha no podrán tramitarse formaciones con cargo al Crédito de Formación 2021.



Precisáis que os mandemos el listado de Cursos disponibles para vuestros 
empleados o bien consultar el Crédito de Formación que tenéis asignado?



Quedamos a la espera de vuestra respuesta.



Saludos cordiales.



Alex Pons
Director FOESCO

Equipo FOESCO (Formación Estatal Continua).
Entidad Organizadora: B200592AA
Tel: 910 323 794
(Horario de 9h a 15h y de 17h a 20h de Lunes a Viernes)

FOESCO ofrece formación a empresas y trabajadores en activo a través de cursos 
bonificados por la Fundación Estatal para la Formación en el Empleo (antiguo 
FORCEM) que gestiona las acciones formativas de FORMACIÓN CONTINUA para 
trabajadores y se rige por la ley 30/2015 de 9 de Septiembre.

Antes de imprimir este e-mail piense bien si es necesario hacerlo. La 
información transmitida en este mensaje está dirigida solamente a las personas 
o entidades que figuran en el encabezamiento y contiene información 
confidencial, por lo que, si usted lo recibiera por error, por favor destrúyalo 
sin copiarlo, usarlo ni distribuirlo, comunicándolo inmediatamente al emisor 
del mensaje. De conformidad con lo dispuesto en el Reglamento Europeo del 
2016/679, del 27 de Abril de 2016, FOESCO le informa que los datos por usted 
suministrados serán tratados con las medidas de seguridad conformes a la 
normativa vigente que se requiere. Dichos datos serán empleados con fines de 
gestión. Para el ejercicio de sus derechos de transparencia, información, 
acceso, rectificación, supresión o derecho al olvido, limitación del 
tratamiento , portabilidad de datos y oposición de sus datos de carácter 
personal deberá dirigirse a la dirección del Responsable del tratamiento a C/ 
LAGUNA DEL MARQUESADO Nº10, 28021, MADRID, "PULSANDO AQUI" 
 y "ENVIAR".

Processed: tagging 999359, retitle 999359 to bullseye-pu: package libayatana-indicator/0.8.4-1+deb11u2

2021-11-10 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> tags 999359 - buster + bullseye
Bug #999359 [release.debian.org] buster-pu: package 
libayatana-indicator/0.8.4-1+deb11u2
Removed tag(s) buster.
Bug #999359 [release.debian.org] buster-pu: package 
libayatana-indicator/0.8.4-1+deb11u2
Added tag(s) bullseye.
> retitle 999359 bullseye-pu: package libayatana-indicator/0.8.4-1+deb11u2
Bug #999359 [release.debian.org] buster-pu: package 
libayatana-indicator/0.8.4-1+deb11u2
Changed Bug title to 'bullseye-pu: package 
libayatana-indicator/0.8.4-1+deb11u2' from 'buster-pu: package 
libayatana-indicator/0.8.4-1+deb11u2'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
999359: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999359
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#998344: buster-pu: package llvm-toolchain-11/1:11.0.1-2~deb10u1

2021-11-10 Thread Emilio Pozuelo Monfort 

On 10/11/2021 15:03, Roberto C. Sánchez wrote:

On Wed, Nov 10, 2021 at 09:00:50AM +0100, Emilio Pozuelo Monfort wrote:

On 09/11/2021 21:00, Roberto C. Sánchez wrote:

Hi Adam,

On Wed, Nov 03, 2021 at 02:20:35PM +, Adam D. Barratt wrote:

On Tue, 2021-11-02 at 13:28 -0400, Roberto C. Sanchez wrote:

In order to support the update of rustc in buster, which in turn is
needed to support the updates of firefox-esr and thunderbird, I am
proposing an update of llvm-toolchain-11 in buster.  The attached
diff represents the change from the current package in the buster-
backports repository.


That diff appears to be between the git branches, rather than the
generated packages. Would it be possible to have a source debdiff
between your base and the package you're planning to upload?


I rebased my changes on 11.0.1-2 from buster.  The debdiff attached to
this email represents the updated packge I am proposing for upload.


I think you mean from bullseye?


Yes, quite right.  I did in fact mean bullseye.  The target suite is
buster, but the source package I am basing the update on is from
bullseye.  I must have confused myself.


Note that I also updated the version of the proposed package to
11.0.1-2+deb10u1.


That should be 11.0.1-2~deb10u1, to be lower than the version in bullseye.


Again, it appears I successfully confounded myself :-/

I have updated the version to 11.0.1-2~deb10u1 and attached an updated
debdiff that reflects the corrected version.  Thanks for catching this,
Emilio.

As a side note, the version I have for the stretch upload is
11.0.1-2~deb9u1.


Thanks for the updated debdiff. Do you have an eta for the mips build? It'd be 
nice to have confirmation that that indeed builds fine.


btw minor nitpick, but the clang-tools install change isn't mentioned in the 
changelog. Would be nice to have that fixed before the actual upload, but no 
need to send another debdiff just for that.


Cheers,
Emilio

Bug#998344: buster-pu: package llvm-toolchain-11/1:11.0.1-2~deb10u1

2021-11-10 Thread Roberto C . Sánchez 
On Wed, Nov 10, 2021 at 09:00:50AM +0100, Emilio Pozuelo Monfort wrote:
> On 09/11/2021 21:00, Roberto C. Sánchez wrote:
> > Hi Adam,
> > 
> > On Wed, Nov 03, 2021 at 02:20:35PM +, Adam D. Barratt wrote:
> > > On Tue, 2021-11-02 at 13:28 -0400, Roberto C. Sanchez wrote:
> > > > In order to support the update of rustc in buster, which in turn is
> > > > needed to support the updates of firefox-esr and thunderbird, I am
> > > > proposing an update of llvm-toolchain-11 in buster.  The attached
> > > > diff represents the change from the current package in the buster-
> > > > backports repository.
> > > 
> > > That diff appears to be between the git branches, rather than the
> > > generated packages. Would it be possible to have a source debdiff
> > > between your base and the package you're planning to upload?
> > > 
> > I rebased my changes on 11.0.1-2 from buster.  The debdiff attached to
> > this email represents the updated packge I am proposing for upload.
> 
> I think you mean from bullseye?
> 
Yes, quite right.  I did in fact mean bullseye.  The target suite is
buster, but the source package I am basing the update on is from
bullseye.  I must have confused myself.

> > Note that I also updated the version of the proposed package to
> > 11.0.1-2+deb10u1.
> 
> That should be 11.0.1-2~deb10u1, to be lower than the version in bullseye.
> 
Again, it appears I successfully confounded myself :-/

I have updated the version to 11.0.1-2~deb10u1 and attached an updated
debdiff that reflects the corrected version.  Thanks for catching this,
Emilio.

As a side note, the version I have for the stretch upload is
11.0.1-2~deb9u1.

Regards,

-Roberto

-- 
Roberto C. Sánchez
diff -Nru llvm-toolchain-11-11.0.1/debian/changelog llvm-toolchain-11-11.0.1/debian/changelog
--- llvm-toolchain-11-11.0.1/debian/changelog	2021-01-06 14:16:26.0 -0500
+++ llvm-toolchain-11-11.0.1/debian/changelog	2021-10-30 13:14:49.0 -0400
@@ -1,3 +1,11 @@
+llvm-toolchain-11 (1:11.0.1-2~deb10u1) buster; urgency=medium
+
+  * Backport to buster.
+- Disable tests on (big endian) mips due to timeout (i.e., test runtime
+  exceeds 10h).
+
+ -- Roberto C. Sánchez   Sat, 30 Oct 2021 13:14:49 -0400
+
 llvm-toolchain-11 (1:11.0.1-2) unstable; urgency=medium
 
   * Fix the changelog
diff -Nru llvm-toolchain-11-11.0.1/debian/clang-tools-X.Y.install.in llvm-toolchain-11-11.0.1/debian/clang-tools-X.Y.install.in
--- llvm-toolchain-11-11.0.1/debian/clang-tools-X.Y.install.in	2020-11-01 04:19:28.0 -0500
+++ llvm-toolchain-11-11.0.1/debian/clang-tools-X.Y.install.in	2021-10-30 13:14:49.0 -0400
@@ -32,7 +32,7 @@
 usr/lib/llvm-@LLVM_VERSION@/bin/clang-move
 usr/lib/llvm-@LLVM_VERSION@/bin/clang-offload-wrapper
 
-[!armel !armhf !ppc64el !hurd-any !s390x !powerpc !ppc64 !mipsel !mips64el !sparc64 !riscv64] usr/lib/llvm-@LLVM_VERSION@/lib/clang/@LLVM_VERSION_FULL@/bin/hwasan_symbolize
+[!armel !armhf !ppc64el !hurd-any !s390x !powerpc !ppc64 !mips !mipsel !mips64el !sparc64 !riscv64] usr/lib/llvm-@LLVM_VERSION@/lib/clang/@LLVM_VERSION_FULL@/bin/hwasan_symbolize
 
 clang/tools/scan-build-@LLVM_VERSION@  usr/share/clang/
 clang/tools/scan-build-py-@LLVM_VERSION@  usr/share/clang/
diff -Nru llvm-toolchain-11-11.0.1/debian/rules llvm-toolchain-11-11.0.1/debian/rules
--- llvm-toolchain-11-11.0.1/debian/rules	2021-01-06 03:25:29.0 -0500
+++ llvm-toolchain-11-11.0.1/debian/rules	2021-10-30 13:14:49.0 -0400
@@ -196,7 +196,7 @@
 endif
 
 # llvm tests timeout, disable it on mipsel
-ifeq (mipsel,$(DEB_HOST_ARCH))
+ifneq (,$(filter $(DEB_HOST_ARCH), mips mipsel))
 	RUN_TEST=no
 endif

Bug#999359: buster-pu: package libayatana-indicator/0.8.4-1+deb11u2

2021-11-10 Thread Mike Gabriel 
Package: release.debian.org
Severity: normal
Tags: buster
User: release.debian@packages.debian.org
Usertags: pu

This buster-pu request is for two recent uploads of libayatana-indicator
(+deb11u1 and +deb11u2). The +deb11u1 upload has already been flagged for
acceptance if I interpreted some recent mail in my Debian INBOX correctly.

[ Reason ]
In +deb11u1, some icon scaling (when read from filepath) has been fixed.

Andrew Shadura reported weekly crashes in mate-indicator-applet and
nailed down the origin to a missing is_null check in
libayatana-indicator. This has been resolved in +deb11u2.

[ Impact ]
MATE indicator applet in MATE panel crashes and needs to be reload
frequently. Icon scaling can be wrong for some appindicator based panel
indicator icons.

[ Tests ]
Manual.

[ Risks ]
Virtually none.

[ 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 ]

Quoting myself from d/changelog:

-> +deb11u2:

+  * debian/patches:
++ Add 0002_src-indicator-ng.c-Make-sure-old-menu-item-name-is-n.patch.
+  Prevent regular crashes in indicator applets. (Closes: #992499).

-> +deb11u1: (already accepted)

+  [ Martin Wimpress ]
+  * debian/patches:
++ Add 0001_scale-icons-when-loading-from-filename.patch (LP: #1733301)
+
+  [ Mike Gabriel ]
+  * debian/patches:
++ Fix file path in 0001_scale-icons-when-loading-from-filename.patch.

When loading an icon from a filename, not a stock icon name, we need to
scale the pixbuf manually because gtk_image_set_pixel_size only works on
named icons from the theme that have multiple sizes available. The
downscaling has been added with the above patch.

[ Other info ]
diff -Nru libayatana-indicator-0.8.4/debian/changelog 
libayatana-indicator-0.8.4/debian/changelog
--- libayatana-indicator-0.8.4/debian/changelog 2021-02-03 16:20:46.0 
+0100
+++ libayatana-indicator-0.8.4/debian/changelog 2021-11-10 13:45:53.0 
+0100
@@ -1,3 +1,23 @@
+libayatana-indicator (0.8.4-1+deb11u2) bullseye; urgency=medium
+
+  * debian/patches:
++ Add 0002_src-indicator-ng.c-Make-sure-old-menu-item-name-is-n.patch.
+  Prevent regular crashes in indicator applets. (Closes: #992499).
+
+ -- Mike Gabriel   Wed, 10 Nov 2021 13:45:53 +0100
+
+libayatana-indicator (0.8.4-1+deb11u1) bullseye; urgency=medium
+
+  [ Martin Wimpress ]
+  * debian/patches:
++ Add 0001_scale-icons-when-loading-from-filename.patch (LP: #1733301)
+
+  [ Mike Gabriel ]
+  * debian/patches:
++ Fix file path in 0001_scale-icons-when-loading-from-filename.patch.
+
+ -- Mike Gabriel   Tue, 19 Oct 2021 10:26:27 +0200
+
 libayatana-indicator (0.8.4-1) unstable; urgency=medium
 
   * New upstream release.
diff -Nru 
libayatana-indicator-0.8.4/debian/patches/0001_scale-icons-when-loading-from-filename.patch
 
libayatana-indicator-0.8.4/debian/patches/0001_scale-icons-when-loading-from-filename.patch
--- 
libayatana-indicator-0.8.4/debian/patches/0001_scale-icons-when-loading-from-filename.patch
 1970-01-01 01:00:00.0 +0100
+++ 
libayatana-indicator-0.8.4/debian/patches/0001_scale-icons-when-loading-from-filename.patch
 2021-10-19 11:59:32.0 +0200
@@ -0,0 +1,27 @@
+diff --git a/src/indicator-image-helper.c b/src/indicator-image-helper.c
+index 2c0e244..4a22539 100644
+--- a/libayatana-indicator/indicator-image-helper.c
 b/libayatana-indicator/indicator-image-helper.c
+@@ -79,13 +79,15 @@ refresh_image (GtkImage * image)
+   }
+   g_object_unref (pixbuf);
+   } else if (icon_filename != NULL) {
+-  gtk_image_set_from_file(image, icon_filename);
+-
+-  gint height;
+-  gdk_pixbuf_get_file_info(icon_filename, NULL, &height);
+-
+-  if (height > ICON_SIZE) {
+-  gtk_image_set_pixel_size(image, ICON_SIZE);
++  GError* error = NULL;
++  GdkPixbuf* pixbuf = 
gdk_pixbuf_new_from_file_at_scale(icon_filename, ICON_SIZE, ICON_SIZE, TRUE, 
&error);
++  if (pixbuf != NULL) {
++  /* Put the pixbuf on the image */
++  gtk_image_set_from_pixbuf(image, pixbuf);
++  g_object_unref(G_OBJECT(pixbuf));
++  } else {
++  g_error_free(error);
++  gtk_image_set_from_icon_name(image, "image-missing", 
ICON_SIZE);
+   }
+   } else if (G_IS_LOADABLE_ICON(icon_names)) {
+   /* Build a pixbuf if needed */
diff -Nru 
libayatana-indicator-0.8.4/debian/patches/0002_src-indicator-ng.c-Make-sure-old-menu-item-name-is-n.patch
 
libayatana-indicator-0.8.4/debian/patches/0002_src-indicator-ng.c-Make-sure-old-menu-item-name-is-n.patch
--- 
libayatana-indicator-0.8.4/debian/patches/0002_src-indicator-ng.c-Make-sure-old-menu-item-name-is-n.patch
   1970-01-01 01:00:00.

Processed: Re: Bug#976811: transition: php8.0

2021-11-10 Thread Debian Bug Tracking System 
Processing control commands:

> forwarded -1 https://release.debian.org/transitions/html/php8.1.html
Bug #976811 [release.debian.org] transition: php8.0
Changed Bug forwarded-to-address to 
'https://release.debian.org/transitions/html/php8.1.html' from 
'https://release.debian.org/transitions/html/php8.0.html'.

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

Bug#976811: transition: php8.0

2021-11-10 Thread Sebastian Ramacher 
Control: forwarded -1 https://release.debian.org/transitions/html/php8.1.html

On 2021-09-05 19:26:39, Ondřej Surý wrote:
> Hi Sebastian,
> 
> the PHP 8.1 RC1 was released, so I think it would be better to skip php8.0
> and go directly with php8.1.  I do have the base package, but I haven’t tested
> any extensions yet, but I do plan to do so in upcoming weeks.
> 
> I’ll update this issue when I am ready.

The tracker for php8.1 is now at
https://release.debian.org/transitions/html/php8.1.html

Cheers

> 
> Ondrej
> --
> Ondřej Surý (He/Him)
> ond...@sury.org
> 
> > On 5. 9. 2021, at 19:14, Sebastian Ramacher  wrote:
> > 
> > Hi Ondřej
> > 
> > On 2020-12-08 09:28:38 +0100, Ondřej Surý wrote:
> >> Package: release.debian.org
> >> Severity: normal
> >> User: release.debian@packages.debian.org
> >> Usertags: transition
> >> 
> >> Hi,
> >> 
> >> I would like to transition the PHP to version 8.0; it's not such a huge 
> >> bump as
> >> it was with 5.6 -> 7.0 and most of the packages that were compatible with 
> >> PHP
> >> 7.4 are working just fine with PHP 8.0.
> >> 
> >> I do have most of the extensions ready for PHP 8.0 either via new upstream 
> >> version
> >> or with patches.
> > 
> > bullseye was released so I think we can revisit this transition. What's
> > the status here?
> > 
> > Cheers
> > 
> >> 
> >> Ondrej
> >> 
> >> Ben file:
> >> 
> >> title = "php8.0";
> >> is_affected = .depends ~ "phpapi-20190902" | .depends ~ "phpapi-20200930";
> >> is_good = .depends ~ "phpapi-20200930";
> >> is_bad = .depends ~ "phpapi-20190902";
> >> 
> >> 
> >> -- System Information:
> >> Debian Release: 10.7
> >>  APT prefers stable-updates
> >>  APT policy: (500, 'stable-updates'), (500, 'stable')
> >> Architecture: amd64 (x86_64)
> >> Foreign Architectures: i386
> >> 
> >> Kernel: Linux 4.19.0-12-amd64 (SMP w/8 CPU cores)
> >> Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
> >> Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8), 
> >> LANGUAGE=en_IE:en (charmap=UTF-8)
> >> Shell: /bin/sh linked to /bin/dash
> >> Init: systemd (via /run/systemd/system)
> >> 
> >> 
> > 
> > -- 
> > Sebastian Ramacher
> 

-- 
Sebastian Ramacher

Processed (with 1 error): Re: Bug#999342: shadow FTBFS: bd-uninstallable due to conflict on libsepol1-dev

2021-11-10 Thread Debian Bug Tracking System 
Processing control commands:

> forcemerge 998633 -1
Bug #998633 [src:shadow] shadow: Please switch libsemanage1-dev BD to 
libsemanage-dev
Bug #998633 [src:shadow] shadow: Please switch libsemanage1-dev BD to 
libsemanage-dev
Added tag(s) ftbfs and patch.
Bug #999342 [src:shadow] shadow FTBFS: bd-uninstallable due to conflict on 
libsepol1-dev
998067 was blocked by: 929484 998633 998634
998067 was not blocking any bugs.
Added blocking bug(s) of 998067: 999342
Added tag(s) pending, sid, and bookworm.
Merged 998633 999342
> tags = 998633 ftbfs bookworm pending sid
Unknown command or malformed arguments to command.


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

Bug#998344: buster-pu: package llvm-toolchain-11/1:11.0.1-2~deb10u1

2021-11-10 Thread Emilio Pozuelo Monfort 

On 09/11/2021 21:00, Roberto C. Sánchez wrote:

Hi Adam,

On Wed, Nov 03, 2021 at 02:20:35PM +, Adam D. Barratt wrote:

On Tue, 2021-11-02 at 13:28 -0400, Roberto C. Sanchez wrote:

In order to support the update of rustc in buster, which in turn is
needed to support the updates of firefox-esr and thunderbird, I am
proposing an update of llvm-toolchain-11 in buster.  The attached
diff represents the change from the current package in the buster-
backports repository.


That diff appears to be between the git branches, rather than the
generated packages. Would it be possible to have a source debdiff
between your base and the package you're planning to upload?


I rebased my changes on 11.0.1-2 from buster.  The debdiff attached to
this email represents the updated packge I am proposing for upload.


I think you mean from bullseye?


Note that I also updated the version of the proposed package to
11.0.1-2+deb10u1.


That should be 11.0.1-2~deb10u1, to be lower than the version in bullseye.

Cheers,
Emilio