Processed: cl-pubmed: diff for NMU version 2.1.3-5.2

[Debian Bug Tracking System]

Processing control commands:

> tags 999331 + patch
Bug #999331 [src:cl-pubmed] cl-pubmed: missing required debian/rules targets 
build-arch and/or build-indep
Added tag(s) patch.
> tags 999331 + pending
Bug #999331 [src:cl-pubmed] cl-pubmed: missing required debian/rules targets 
build-arch and/or build-indep
Added tag(s) pending.

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

Bug#999331: cl-pubmed: diff for NMU version 2.1.3-5.2

[Marcos Talau]

Control: tags 999331 + patch
Control: tags 999331 + pending


Dear maintainer,

I've prepared an NMU for cl-pubmed (versioned as 2.1.3-5.2) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Regards.
diff -u cl-pubmed-2.1.3/debian/changelog cl-pubmed-2.1.3/debian/changelog
--- cl-pubmed-2.1.3/debian/changelog
+++ cl-pubmed-2.1.3/debian/changelog
@@ -1,3 +1,10 @@
+cl-pubmed (2.1.3-5.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/rules: Add build-{arch,indep} (Closes: #999331).
+
+ -- Marcos Talau   Tue, 01 Nov 2022 23:44:03 -0300
+
 cl-pubmed (2.1.3-5.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -u cl-pubmed-2.1.3/debian/rules cl-pubmed-2.1.3/debian/rules
--- cl-pubmed-2.1.3/debian/rules
+++ cl-pubmed-2.1.3/debian/rules
@@ -39,5 +39,7 @@
 
 binary: binary-indep
 
+build-arch: build
+build-indep: build
 
-.PHONY: build clean binary-indep binary-arch binary install
+.PHONY: build build-arch build-indep clean binary-indep binary-arch binary install

Processed: cl-umlisp-orf: diff for NMU version 3.3.2-3.1

[Debian Bug Tracking System]

Processing control commands:

> tags 999165 + patch
Bug #999165 [src:cl-umlisp-orf] cl-umlisp-orf: missing required debian/rules 
targets build-arch and/or build-indep
Added tag(s) patch.
> tags 999165 + pending
Bug #999165 [src:cl-umlisp-orf] cl-umlisp-orf: missing required debian/rules 
targets build-arch and/or build-indep
Added tag(s) pending.

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

Bug#999165: cl-umlisp-orf: diff for NMU version 3.3.2-3.1

[Marcos Talau]

Control: tags 999165 + patch
Control: tags 999165 + pending


Dear maintainer,

I've prepared an NMU for cl-umlisp-orf (versioned as 3.3.2-3.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Regards.
diff -Nru cl-umlisp-orf-3.3.2/debian/changelog cl-umlisp-orf-3.3.2/debian/changelog
--- cl-umlisp-orf-3.3.2/debian/changelog	2011-04-02 23:12:14.0 -0300
+++ cl-umlisp-orf-3.3.2/debian/changelog	2022-11-01 23:50:11.0 -0300
@@ -1,3 +1,10 @@
+cl-umlisp-orf (3.3.2-3.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/rules: Add build-{arch,indep} (Closes: #999165).
+
+ -- Marcos Talau   Tue, 01 Nov 2022 23:50:11 -0300
+
 cl-umlisp-orf (3.3.2-3) unstable; urgency=low
 
   * Fix package description (closes:620524)
diff -Nru cl-umlisp-orf-3.3.2/debian/rules cl-umlisp-orf-3.3.2/debian/rules
--- cl-umlisp-orf-3.3.2/debian/rules	2009-08-03 23:29:25.0 -0300
+++ cl-umlisp-orf-3.3.2/debian/rules	2022-11-01 23:50:11.0 -0300
@@ -39,5 +39,7 @@
 
 binary: binary-indep
 
+build-arch: build
+build-indep: build
 
-.PHONY: build clean binary-indep binary-arch binary install
+.PHONY: build build-arch build-indep clean binary-indep binary-arch binary install

Processed: cl-pipes: diff for NMU version 1.2.1-5.2

[Debian Bug Tracking System]

Processing control commands:

> tags 998994 + patch
Bug #998994 [src:cl-pipes] cl-pipes: missing required debian/rules targets 
build-arch and/or build-indep
Added tag(s) patch.
> tags 998994 + pending
Bug #998994 [src:cl-pipes] cl-pipes: missing required debian/rules targets 
build-arch and/or build-indep
Added tag(s) pending.

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

Bug#998994: cl-pipes: diff for NMU version 1.2.1-5.2

[Marcos Talau]

Control: tags 998994 + patch
Control: tags 998994 + pending


Dear maintainer,

I've prepared an NMU for cl-pipes (versioned as 1.2.1-5.2) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Regards.
diff -u cl-pipes-1.2.1/debian/changelog cl-pipes-1.2.1/debian/changelog
--- cl-pipes-1.2.1/debian/changelog
+++ cl-pipes-1.2.1/debian/changelog
@@ -1,3 +1,10 @@
+cl-pipes (1.2.1-5.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/rules: Add build-{arch,indep} (Closes: #998994).
+
+ -- Marcos Talau   Tue, 01 Nov 2022 23:42:31 -0300
+
 cl-pipes (1.2.1-5.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -u cl-pipes-1.2.1/debian/rules cl-pipes-1.2.1/debian/rules
--- cl-pipes-1.2.1/debian/rules
+++ cl-pipes-1.2.1/debian/rules
@@ -41,5 +41,7 @@
 
 binary: binary-indep
 
+build-arch: build
+build-indep: build
 
-.PHONY: build clean binary-indep binary-arch binary install
+.PHONY: build build-arch build-indep clean binary-indep binary-arch binary install

Processed: cl-xlunit: diff for NMU version 0.6.3-2.2

[Debian Bug Tracking System]

Processing control commands:

> tags 998971 + patch
Bug #998971 [src:cl-xlunit] cl-xlunit: missing required debian/rules targets 
build-arch and/or build-indep
Added tag(s) patch.
> tags 998971 + pending
Bug #998971 [src:cl-xlunit] cl-xlunit: missing required debian/rules targets 
build-arch and/or build-indep
Added tag(s) pending.

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

Bug#998971: cl-xlunit: diff for NMU version 0.6.3-2.2

[Marcos Talau]

Control: tags 998971 + patch
Control: tags 998971 + pending


Dear maintainer,

I've prepared an NMU for cl-xlunit (versioned as 0.6.3-2.2) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Regards.
diff -u cl-xlunit-0.6.3/debian/changelog cl-xlunit-0.6.3/debian/changelog
--- cl-xlunit-0.6.3/debian/changelog
+++ cl-xlunit-0.6.3/debian/changelog
@@ -1,3 +1,10 @@
+cl-xlunit (0.6.3-2.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/rules: Add build-{arch,indep} (Closes: #998971).
+
+ -- Marcos Talau   Tue, 01 Nov 2022 23:51:27 -0300
+
 cl-xlunit (0.6.3-2.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -u cl-xlunit-0.6.3/debian/rules cl-xlunit-0.6.3/debian/rules
--- cl-xlunit-0.6.3/debian/rules
+++ cl-xlunit-0.6.3/debian/rules
@@ -41,5 +41,7 @@
 
 binary: binary-indep
 
+build-arch: build
+build-indep: build
 
-.PHONY: build clean binary-indep binary-arch binary install
+.PHONY: build build-arch build-indep clean binary-indep binary-arch binary install

Processed: cl-xptest: diff for NMU version 1.2.4-3.2

[Debian Bug Tracking System]

Processing control commands:

> tags 998959 + patch
Bug #998959 [src:cl-xptest] cl-xptest: missing required debian/rules targets 
build-arch and/or build-indep
Added tag(s) patch.
> tags 998959 + pending
Bug #998959 [src:cl-xptest] cl-xptest: missing required debian/rules targets 
build-arch and/or build-indep
Added tag(s) pending.

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

Bug#998959: cl-xptest: diff for NMU version 1.2.4-3.2

[Marcos Talau]

Control: tags 998959 + patch
Control: tags 998959 + pending


Dear maintainer,

I've prepared an NMU for cl-xptest (versioned as 1.2.4-3.2) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Regards.
diff -u cl-xptest-1.2.4/debian/changelog cl-xptest-1.2.4/debian/changelog
--- cl-xptest-1.2.4/debian/changelog
+++ cl-xptest-1.2.4/debian/changelog
@@ -1,3 +1,10 @@
+cl-xptest (1.2.4-3.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/rules: Add build-{arch,indep} (Closes: #998959).
+
+ -- Marcos Talau   Tue, 01 Nov 2022 23:52:47 -0300
+
 cl-xptest (1.2.4-3.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -u cl-xptest-1.2.4/debian/rules cl-xptest-1.2.4/debian/rules
--- cl-xptest-1.2.4/debian/rules
+++ cl-xptest-1.2.4/debian/rules
@@ -40,5 +40,7 @@
 
 binary: binary-indep
 
+build-arch: build
+build-indep: build
 
-.PHONY: build clean binary-indep binary-arch binary install
+.PHONY: build build-arch build-indep clean binary-indep binary-arch binary install

Processed: cl-umlisp: diff for NMU version 1:2007ac.2-6.1

[Debian Bug Tracking System]

Processing control commands:

> tags 998935 + patch
Bug #998935 [src:cl-umlisp] cl-umlisp: missing required debian/rules targets 
build-arch and/or build-indep
Added tag(s) patch.
> tags 998935 + pending
Bug #998935 [src:cl-umlisp] cl-umlisp: missing required debian/rules targets 
build-arch and/or build-indep
Added tag(s) pending.

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

Bug#998935: cl-umlisp: diff for NMU version 1:2007ac.2-6.1

[Marcos Talau]

Control: tags 998935 + patch
Control: tags 998935 + pending


Dear maintainer,

I've prepared an NMU for cl-umlisp (versioned as 1:2007ac.2-6.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Regards.
diff -Nru cl-umlisp-2007ac.2/debian/changelog cl-umlisp-2007ac.2/debian/changelog
--- cl-umlisp-2007ac.2/debian/changelog	2011-04-03 01:10:11.0 -0300
+++ cl-umlisp-2007ac.2/debian/changelog	2022-11-01 23:48:37.0 -0300
@@ -1,3 +1,10 @@
+cl-umlisp (1:2007ac.2-6.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/rules: Add build-{arch,indep} (Closes: #998935).
+
+ -- Marcos Talau   Tue, 01 Nov 2022 23:48:37 -0300
+
 cl-umlisp (1:2007ac.2-6) unstable; urgency=low
 
   * debian/control: Fix typo in package description
diff -Nru cl-umlisp-2007ac.2/debian/rules cl-umlisp-2007ac.2/debian/rules
--- cl-umlisp-2007ac.2/debian/rules	2009-08-03 23:26:16.0 -0300
+++ cl-umlisp-2007ac.2/debian/rules	2022-11-01 23:48:37.0 -0300
@@ -40,5 +40,7 @@
 
 binary: binary-indep
 
+build-arch: build
+build-indep: build
 
-.PHONY: build clean binary-indep binary-arch binary install
+.PHONY: build build-arch build-indep clean binary-indep binary-arch binary install

Processed: cl-photo: diff for NMU version 0.14-4.2

[Debian Bug Tracking System]

Processing control commands:

> tags 999012 + patch
Bug #999012 [src:cl-photo] cl-photo: missing required debian/rules targets 
build-arch and/or build-indep
Added tag(s) patch.
> tags 999012 + pending
Bug #999012 [src:cl-photo] cl-photo: missing required debian/rules targets 
build-arch and/or build-indep
Added tag(s) pending.

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

Bug#999012: cl-photo: diff for NMU version 0.14-4.2

[Marcos Talau]

Control: tags 999012 + patch
Control: tags 999012 + pending


Dear maintainer,

I've prepared an NMU for cl-photo (versioned as 0.14-4.2) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Regards.
diff -u cl-photo-0.14/debian/changelog cl-photo-0.14/debian/changelog
--- cl-photo-0.14/debian/changelog
+++ cl-photo-0.14/debian/changelog
@@ -1,3 +1,10 @@
+cl-photo (0.14-4.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/rules: Add build-{arch,indep} (Closes: #999012).
+
+ -- Marcos Talau   Tue, 01 Nov 2022 23:41:10 -0300
+
 cl-photo (0.14-4.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -u cl-photo-0.14/debian/rules cl-photo-0.14/debian/rules
--- cl-photo-0.14/debian/rules
+++ cl-photo-0.14/debian/rules
@@ -40,5 +40,7 @@
 
 binary: binary-indep
 
+build-arch: build
+build-indep: build
 
-.PHONY: build clean binary-indep binary-arch binary install
+.PHONY: build build-arch build-indep clean binary-indep binary-arch binary install

Bug#999045: cl-lml: diff for NMU version 2.5.7-4.2

[Marcos Talau]

Control: tags 999045 + patch
Control: tags 999045 + pending


Dear maintainer,

I've prepared an NMU for cl-lml (versioned as 2.5.7-4.2) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Regards.
diff -u cl-lml-2.5.7/debian/changelog cl-lml-2.5.7/debian/changelog
--- cl-lml-2.5.7/debian/changelog
+++ cl-lml-2.5.7/debian/changelog
@@ -1,3 +1,10 @@
+cl-lml (2.5.7-4.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/rules: Add build-{arch,indep} (Closes: #999045).
+
+ -- Marcos Talau   Tue, 01 Nov 2022 23:14:05 -0300
+
 cl-lml (2.5.7-4.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -u cl-lml-2.5.7/debian/rules cl-lml-2.5.7/debian/rules
--- cl-lml-2.5.7/debian/rules
+++ cl-lml-2.5.7/debian/rules
@@ -41,5 +41,7 @@
 
 binary: binary-indep
 
+build-arch: build
+build-indep: build
 
-.PHONY: build clean binary-indep binary-arch binary install
+.PHONY: build build-arch build-indep clean binary-indep binary-arch binary install

Processed: cl-irc-logger: diff for NMU version 0.9.4-3.2

[Debian Bug Tracking System]

Processing control commands:

> tags 999079 + patch
Bug #999079 [src:cl-irc-logger] cl-irc-logger: missing required debian/rules 
targets build-arch and/or build-indep
Added tag(s) patch.
> tags 999079 + pending
Bug #999079 [src:cl-irc-logger] cl-irc-logger: missing required debian/rules 
targets build-arch and/or build-indep
Added tag(s) pending.

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

Bug#999079: cl-irc-logger: diff for NMU version 0.9.4-3.2

[Marcos Talau]

Control: tags 999079 + patch
Control: tags 999079 + pending


Dear maintainer,

I've prepared an NMU for cl-irc-logger (versioned as 0.9.4-3.2) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Regards.
diff -u cl-irc-logger-0.9.4/debian/changelog cl-irc-logger-0.9.4/debian/changelog
--- cl-irc-logger-0.9.4/debian/changelog
+++ cl-irc-logger-0.9.4/debian/changelog
@@ -1,3 +1,10 @@
+cl-irc-logger (0.9.4-3.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/rules: Add build-{arch,indep} (Closes: #999079).
+
+ -- Marcos Talau   Tue, 01 Nov 2022 23:06:40 -0300
+
 cl-irc-logger (0.9.4-3.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -u cl-irc-logger-0.9.4/debian/rules cl-irc-logger-0.9.4/debian/rules
--- cl-irc-logger-0.9.4/debian/rules
+++ cl-irc-logger-0.9.4/debian/rules
@@ -40,5 +40,7 @@
 
 binary: binary-indep
 
+build-arch: build
+build-indep: build
 
-.PHONY: build clean binary-indep binary-arch binary install
+.PHONY: build build-arch build-indep clean binary-indep binary-arch binary install

Processed: cl-lml: diff for NMU version 2.5.7-4.2

[Debian Bug Tracking System]

Processing control commands:

> tags 999045 + patch
Bug #999045 [src:cl-lml] cl-lml: missing required debian/rules targets 
build-arch and/or build-indep
Added tag(s) patch.
> tags 999045 + pending
Bug #999045 [src:cl-lml] cl-lml: missing required debian/rules targets 
build-arch and/or build-indep
Added tag(s) pending.

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

Processed: cl-lml2: diff for NMU version 1.6.6-4.2

[Debian Bug Tracking System]

Processing control commands:

> tags 998990 + patch
Bug #998990 [src:cl-lml2] cl-lml2: missing required debian/rules targets 
build-arch and/or build-indep
Added tag(s) patch.
> tags 998990 + pending
Bug #998990 [src:cl-lml2] cl-lml2: missing required debian/rules targets 
build-arch and/or build-indep
Added tag(s) pending.

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

Bug#998990: cl-lml2: diff for NMU version 1.6.6-4.2

[Marcos Talau]

Control: tags 998990 + patch
Control: tags 998990 + pending


Dear maintainer,

I've prepared an NMU for cl-lml2 (versioned as 1.6.6-4.2) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Regards.
diff -u cl-lml2-1.6.6/debian/changelog cl-lml2-1.6.6/debian/changelog
--- cl-lml2-1.6.6/debian/changelog
+++ cl-lml2-1.6.6/debian/changelog
@@ -1,3 +1,10 @@
+cl-lml2 (1.6.6-4.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/rules: Add build-{arch,indep} (Closes: #998990).
+
+ -- Marcos Talau   Tue, 01 Nov 2022 23:15:58 -0300
+
 cl-lml2 (1.6.6-4.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -u cl-lml2-1.6.6/debian/rules cl-lml2-1.6.6/debian/rules
--- cl-lml2-1.6.6/debian/rules
+++ cl-lml2-1.6.6/debian/rules
@@ -41,5 +41,7 @@
 
 binary: binary-indep
 
+build-arch: build
+build-indep: build
 
-.PHONY: build clean binary-arch binary-indep binary install
+.PHONY: build build-arch build-indep clean binary-arch binary-indep binary install

Processed: cl-pg: diff for NMU version 1:20061216-6.1

[Debian Bug Tracking System]

Processing control commands:

> tags 998973 + patch
Bug #998973 [src:cl-pg] cl-pg: missing required debian/rules targets build-arch 
and/or build-indep
Added tag(s) patch.
> tags 998973 + pending
Bug #998973 [src:cl-pg] cl-pg: missing required debian/rules targets build-arch 
and/or build-indep
Added tag(s) pending.

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

Processed: cl-modlisp: diff for NMU version 0.6-7.2

[Debian Bug Tracking System]

Processing control commands:

> tags 998947 + patch
Bug #998947 [src:cl-modlisp] cl-modlisp: missing required debian/rules targets 
build-arch and/or build-indep
Added tag(s) patch.
> tags 998947 + pending
Bug #998947 [src:cl-modlisp] cl-modlisp: missing required debian/rules targets 
build-arch and/or build-indep
Added tag(s) pending.

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

Bug#998973: cl-pg: diff for NMU version 1:20061216-6.1

[Marcos Talau]

Control: tags 998973 + patch
Control: tags 998973 + pending


Dear maintainer,

I've prepared an NMU for cl-pg (versioned as 1:20061216-6.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Regards.
diff -Nru cl-pg-20061216/debian/changelog cl-pg-20061216/debian/changelog
--- cl-pg-20061216/debian/changelog	2018-04-07 13:25:47.0 -0300
+++ cl-pg-20061216/debian/changelog	2022-11-01 23:32:08.0 -0300
@@ -1,3 +1,10 @@
+cl-pg (1:20061216-6.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/rules: Add build-{arch,indep} (Closes: #998973).
+
+ -- Marcos Talau   Tue, 01 Nov 2022 23:32:08 -0300
+
 cl-pg (1:20061216-6) unstable; urgency=medium
 
   * Team upload.
diff -Nru cl-pg-20061216/debian/rules cl-pg-20061216/debian/rules
--- cl-pg-20061216/debian/rules	2018-04-07 13:25:09.0 -0300
+++ cl-pg-20061216/debian/rules	2022-11-01 23:32:08.0 -0300
@@ -59,4 +59,8 @@
 	dh_builddeb
 
 binary: binary-indep binary-arch
-.PHONY: build clean binary-indep binary-arch binary install configure
+
+build-arch: build
+build-indep: build
+
+.PHONY: build build-arch build-indep clean binary-indep binary-arch binary install configure

Processed: cgilib: diff for NMU version 0.6-1.2

[Debian Bug Tracking System]

Processing control commands:

> tags 998933 + patch
Bug #998933 [src:cgilib] cgilib: missing required debian/rules targets 
build-arch and/or build-indep
Added tag(s) patch.
> tags 998933 + pending
Bug #998933 [src:cgilib] cgilib: missing required debian/rules targets 
build-arch and/or build-indep
Added tag(s) pending.

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

Bug#998947: cl-modlisp: diff for NMU version 0.6-7.2

[Marcos Talau]

Control: tags 998947 + patch
Control: tags 998947 + pending


Dear maintainer,

I've prepared an NMU for cl-modlisp (versioned as 0.6-7.2) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Regards.
diff -u cl-modlisp-0.6/debian/changelog cl-modlisp-0.6/debian/changelog
--- cl-modlisp-0.6/debian/changelog
+++ cl-modlisp-0.6/debian/changelog
@@ -1,3 +1,10 @@
+cl-modlisp (0.6-7.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/rules: Add build-{arch,indep} (Closes: #998947).
+
+ -- Marcos Talau   Tue, 01 Nov 2022 23:30:21 -0300
+
 cl-modlisp (0.6-7.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -u cl-modlisp-0.6/debian/rules cl-modlisp-0.6/debian/rules
--- cl-modlisp-0.6/debian/rules
+++ cl-modlisp-0.6/debian/rules
@@ -41,5 +41,7 @@
 
 binary: binary-indep binary-arch
 
+build-arch: build
+build-indep: build
 
-.PHONY: build clean binary-indep binary-arch binary install
+.PHONY: build build-arch build-indep clean binary-indep binary-arch binary install

Bug#998933: cgilib: diff for NMU version 0.6-1.2

[Marcos Talau]

Control: tags 998933 + patch
Control: tags 998933 + pending

Dear maintainer,

I've prepared an NMU for cgilib (versioned as 0.6-1.2) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Regards.
diff -u cgilib-0.6/debian/changelog cgilib-0.6/debian/changelog
--- cgilib-0.6/debian/changelog
+++ cgilib-0.6/debian/changelog
@@ -1,3 +1,10 @@
+cgilib (0.6-1.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/rules: Add build-{arch,indep} (Closes: #998933).
+
+ -- Marcos Talau   Tue, 01 Nov 2022 22:55:50 -0300
+
 cgilib (0.6-1.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -u cgilib-0.6/debian/rules cgilib-0.6/debian/rules
--- cgilib-0.6/debian/rules
+++ cgilib-0.6/debian/rules
@@ -119,3 +119,6 @@
 
-.PHONY: binary binary-arch binary-indep clean checkroot
+build-arch: build
+build-indep: build
+
+.PHONY: binary binary-arch binary-indep build build-arch build-indep clean checkroot
 

Bug#1021314: marked as done (hol88: license issues)

[Debian Bug Tracking System]

Your message dated Wed, 02 Nov 2022 01:49:48 +
with message-id 
and subject line Bug#1021314: fixed in hol88 2.02.19940316dfsg-1
has caused the Debian Bug report #1021314,
regarding hol88: license issues
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.)


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

Source: hol88
Severity: serious
Version: 2.02.19940316-35.1

hol88 has one certain license issue: It bundles an old copy of NOWEB, which has 
a non-free license.
Please repack so that NOWEB is not included.

Furthermore, the license of hol88 might be non-free as well. debian/copyright claims it is public domain, which might 
not necessarily be true. There is a license included in License/{READ-ME,License.tex}. Please check carefully if this 
can stay in main at all.
--- End Message ---
--- Begin Message ---
Source: hol88
Source-Version: 2.02.19940316dfsg-1
Done: Camm Maguire 

We believe that the bug you reported is fixed in the latest version of
hol88, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1021...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Camm Maguire  (supplier of updated hol88 package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 01 Nov 2022 21:20:09 -0400
Source: hol88
Architecture: source
Version: 2.02.19940316dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Camm Maguire 
Changed-By: Camm Maguire 
Closes: 1021314
Changes:
 hol88 (2.02.19940316dfsg-1) unstable; urgency=medium
 .
   * Repack without NOWEB
   * Bug fix: "license issues", thanks to Bastian Germann (Closes:
 #1021314).
   * Accept NMU
Checksums-Sha1:
 5941738297e72d2a1f058975e0ace9ad121859d2 2313 hol88_2.02.19940316dfsg-1.dsc
 bc74d2d9ec9af6fe04c6b6853b0a9850897c4b7f 10359437 
hol88_2.02.19940316dfsg.orig.tar.gz
 0987effc66118f3da350a7133cef904dca8e8059 131528 
hol88_2.02.19940316dfsg-1.debian.tar.xz
 9023ae52291ea7e9292373b3f8177acad7bdbdad 11174 
hol88_2.02.19940316dfsg-1_source.buildinfo
Checksums-Sha256:
 4771756e020c01b4d84c438a012e5ef92a8f628d8b75c1ce7548c05c1447a89c 2313 
hol88_2.02.19940316dfsg-1.dsc
 8e2a4f83cea20d0cf2416f7d55c951498f6c807b03ebc9381a02fa4c81c5da69 10359437 
hol88_2.02.19940316dfsg.orig.tar.gz
 155bf9f2557406187ef4677b0126c28fca0c5344d6f222663bc85bb02ac92900 131528 
hol88_2.02.19940316dfsg-1.debian.tar.xz
 9c34de22e88f02290fd4eb742a7dc943b737a51a7def0f2773a725371bb4131a 11174 
hol88_2.02.19940316dfsg-1_source.buildinfo
Files:
 69aaca01519769f322a0fa3dd8b46412 2313 math optional 
hol88_2.02.19940316dfsg-1.dsc
 d916adf41bc7c1f9eb2a7c07ff442b01 10359437 math optional 
hol88_2.02.19940316dfsg.orig.tar.gz
 249ddce05e42a0a2ce695126ffdd82fc 131528 math optional 
hol88_2.02.19940316dfsg-1.debian.tar.xz
 2c0a75b3f892d0aa2eb16f528a21a8a4 11174 math optional 
hol88_2.02.19940316dfsg-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEE/iFPNjaXdzJC6BbsuEXOUQ+bcU0FAmNhyAMACgkQuEXOUQ+b
cU2aiA/9Hw4FAllQX3uY9RqL1WqLp0Yq7jaBUlQeWaP4uk7AjHAl1RL0JO91NYjj
iVbE/aDdY6emGFntc9AQGfw9BtFbNZ/KdudFtfgt9c2Cjo28KPk+zeEMIoYEsYdO
mZ01Z99d7WQIBPFYEhKSKBca54vdz4ur9wBPybsqFqa6GUdMPMtKzsn5HbGm1FYD
58H8p64g82vm7XhUAEJlG1QASa0sYRl4eFtJ3SWBDBWi1vGKnolkGwLhct5hNkWC
XCnRxeprz4k71g/gIHCvW60R8HChCBLbdpmP5FV+m09SyrjSvh1l21/btU+qbvjT
tGmGSk50SzyPHTELh397/liNJe0DjblKylP2D/WrypPA2LKAq6EXGmHsJK9b1qWe
gH5nM5wAqyqeoXOIvmJCU8uJwfJlVY9WsV9At7QXrtwrL1aMPjgbgci6ROb8xg+r
U6IJxjHCdAPbNvuGLIB+GbWBAKkQCE0wadtdfL9fzMQJHaxxHLvUeir0tUN1q7xB
lpbgQ451iiVEBfIpcVlUgsGEKIEOuaWQVBKeMkPej9bK6im1ndrLQ/UYjS/IhVua
K6g8SIkja7j0q3ldIbNZyAUAL2Xht/GVz6Zg/N4K8DTgwpDSsRS5QzNnmJq5hjcY
k+5a5/ctTKqxkuDYBB7Vb3j0qarNfaEtRSuyy6TXLOkoT5Ac6CA=
=YJyi
-END PGP SIGNATURE End Message ---

Processed: found 1017711 in emacs/1:28.2+1-3, bug 1017711 is forwarded to https://debbugs.gnu.org/58956

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> found 1017711 emacs/1:28.2+1-3
Bug #1017711 [emacs-gtk] emacs-gtk: terminated with signal SIGABRT, 137 MB 
coredump
Ignoring request to alter found versions of bug #1017711 to the same values 
previously set
> forwarded 1017711 https://debbugs.gnu.org/58956
Bug #1017711 [emacs-gtk] emacs-gtk: terminated with signal SIGABRT, 137 MB 
coredump
Set Bug forwarded-to-address to 'https://debbugs.gnu.org/58956'.
> thanks
Stopping processing here.

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

Bug#1017711: emacs-gtk: terminated with signal SIGABRT, 137 MB coredump

[Sean Whitton]

Hello,

On Tue 01 Nov 2022 at 11:17PM +01, Vincent Lefevre wrote:

> On 2022-10-31 15:59:17 +0100, Vincent Lefevre wrote:
>> Hi,
>>
>> On 2022-10-30 06:31:27 -0700, Sean Whitton wrote:
>> > I've backported a couple of patches from upstream related to native
>> > compilation, now, so would you be able to test again with the latest
>> > upload?  Thanks.
>>
>> If you mean 1:28.2+1-3, I still got the same issue. But it seems
>> that after a reboot, the problem no longer occurs (after removing
>> the .emacs.d directory). Was a reboot needed?
>
> Unfortunately, it has just occurred again (with emacs run by
> Subversion to enter a commit message).
>
> Core was generated by `/usr/bin/emacs -no-comp-spawn --batch -l 
> /tmp/emacs-async-comp-url.el-FGov4z.el'.
> Program terminated with signal SIGABRT, Aborted.
> #0  __pthread_kill_implementation (threadid=, 
> signo=signo@entry=6, no_tid=no_tid@entry=0) at ./nptl/pthread_kill.c:44
> 44  ./nptl/pthread_kill.c: No such file or directory.
>
> I've attached the backtrace. Seems too many recursive calls to
> mark_object and mark_objects.
>
> Worse, not just a background emacs process, the UI also crashes
> (IIRC, this didn't happen before).

Thanks for following up.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Processed: Re: dropwatch build times out in the testsuite

[Debian Bug Tracking System]

Processing control commands:

> severity -1 normal
Bug #964540 [src:dropwatch] dropwatch build times out in the testsuite
Severity set to 'normal' from 'serious'

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

Bug#964540: dropwatch build times out in the testsuite

[Andreas Beckmann]

Control: severity -1 normal

On Wed, 8 Jul 2020 13:26:54 +0200 Matthias Klose  wrote:

Package: src:dropwatch
Version: 1.5.3-1



dropwatch build times out in the testsuite, no output available in the build 
log.


The 1.5.4-1 release built fine on the buildds for all release 
architectures. But there were testsuite timeouts on some ports 
architectures.



Andreas

Bug#1023019: marked as done (pyserial-asyncio FTBFS)

[Debian Bug Tracking System]

Your message dated Wed, 02 Nov 2022 01:04:19 +
with message-id 
and subject line Bug#1023019: fixed in pyserial-asyncio 0.6-4
has caused the Debian Bug report #1023019,
regarding pyserial-asyncio FTBFS
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.)


-- 
1023019: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023019
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pyserial-asyncio
Version: 0.6-2
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/logs.php?pkg=pyserial-asyncio=all

...
   dh_auto_test -i -O--buildsystem=pybuild
I: pybuild base:240: cd 
/<>/.pybuild/cpython3_3.10_serial_asyncio/build; python3.10 -m 
unittest discover -v 
test_asyncio (test.test_asyncio.Test_asyncio) ... 
/<>/.pybuild/cpython3_3.10_serial_asyncio/build/test/test_asyncio.py:36:
 DeprecationWarning: There is no current event loop
  self.loop = asyncio.get_event_loop()
ERROR

==
ERROR: test_asyncio (test.test_asyncio.Test_asyncio)
--
Traceback (most recent call last):
  File 
"/<>/.pybuild/cpython3_3.10_serial_asyncio/build/test/test_asyncio.py",
 line 89, in test_asyncio
self.loop.run_until_complete(coro)
  File "/usr/lib/python3.10/asyncio/base_events.py", line 649, in 
run_until_complete
return future.result()
  File "/usr/lib/python3.10/asyncio/base_events.py", line 1508, in create_server
raise OSError(err.errno, 'error while attempting '
OSError: [Errno 98] error while attempting to bind on address ('127.0.0.1', 
): address already in use

--
Ran 1 test in 0.002s

FAILED (errors=1)
E: pybuild pybuild:379: test: plugin distutils failed with: exit code=1: cd 
/<>/.pybuild/cpython3_3.10_serial_asyncio/build; python3.10 -m 
unittest discover -v 
dh_auto_test: error: pybuild --test -i python{version} -p 3.10 returned exit 
code 13
make: *** [debian/rules:8: binary-indep] Error 25


This fails on the IPV6-only buildds, and port  might also be used
on other buildds.
--- End Message ---
--- Begin Message ---
Source: pyserial-asyncio
Source-Version: 0.6-4
Done: Martin 

We believe that the bug you reported is fixed in the latest version of
pyserial-asyncio, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1023...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Martin  (supplier of updated pyserial-asyncio package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 02 Nov 2022 00:11:05 +
Source: pyserial-asyncio
Architecture: source
Version: 0.6-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Martin 
Closes: 1023019
Changes:
 pyserial-asyncio (0.6-4) unstable; urgency=medium
 .
   * Add patch: Use free port for test (Closes: #1023019)
Checksums-Sha1:
 0a4dfd23e0ff27929cfdc4c15f0a739a02c75dfa 2202 pyserial-asyncio_0.6-4.dsc
 34743c6ce3b65f6cbc38529a2dbc3fbad5d147d8 3260 
pyserial-asyncio_0.6-4.debian.tar.xz
 f4e5be552fa8239562f612c8b5f5a204b4044da4 8290 
pyserial-asyncio_0.6-4_amd64.buildinfo
Checksums-Sha256:
 2d1b240ef53ec3d1e33d2a97fefefe69e940710dac6713e0977323b87ebfd40c 2202 
pyserial-asyncio_0.6-4.dsc
 ea3a4e02e517b8735045bba3846ba1cc720d5636d059fa001744f63403d387cf 3260 
pyserial-asyncio_0.6-4.debian.tar.xz
 062b8b388bf29e5c2c15da8a480ff9335c30ba7ffaaec36ef534b7c50b349813 8290 
pyserial-asyncio_0.6-4_amd64.buildinfo
Files:
 a462dae52d74c9187b89edcaae8ceac0 2202 python optional 
pyserial-asyncio_0.6-4.dsc
 0bfc19cfc9401d5a338f7aba28e8a9ee 3260 python optional 
pyserial-asyncio_0.6-4.debian.tar.xz
 8d1e82aa791f9a0139a3b9f80c87bc10 8290 python optional 
pyserial-asyncio_0.6-4_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEftHeo0XZoKEY1KdA4+Chwoa5Y+oFAmNhvlEACgkQ4+Chwoa5
Y+pmsQ/9EUVooW7aimA9dhWzFE1MzNPJvY8TolWAfl89JqLMd98EiGfkEianJthK
uGHI1WFgX6k+rFyZWd1IZ6Iv/mQDsYcdQVLrBcgUsu3apF03eiXkeO8S58lst3zo
/XV26wYFhTC2loNXA6QK/UAVmMYT3+TUthnWBBxn1WjSK2p3je0Uyczjm/1yRXQR
1aUZs9nFFvEt5m2Ouf8UkTS7fL2HSqHLlIMeUlBsex4MNAtp0MHuGCMvvM8iNhLw

Processed: reassign 1023299 to ganeti-testsuite

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 1023299 ganeti-testsuite
Bug #1023299 [src:ganeti-testsuite] ganeti-testsuite: yaml.load in testsuite 
needs to specify loader
Warning: Unknown package 'src:ganeti-testsuite'
Bug reassigned from package 'src:ganeti-testsuite' to 'ganeti-testsuite'.
No longer marked as found in versions ganeti-testsuite/3.0.2-1.
Ignoring request to alter fixed versions of bug #1023299 to the same values 
previously set
> thanks
Stopping processing here.

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

Bug#1019784: marked as done (scorched3d: Please transition to wxwidgets3.2)

[Debian Bug Tracking System]

Your message dated Tue, 01 Nov 2022 23:23:08 +
with message-id 
and subject line Bug#1019784: fixed in scorched3d 44+dfsg-8
has caused the Debian Bug report #1019784,
regarding scorched3d: Please transition to wxwidgets3.2
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.)


-- 
1019784: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019784
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: scorched3d
Severity: normal
Control: block 1019416 by -1

Hi,

Please transition scorched3d from wxwidgets3.0 to wxwidgets3.2.

wxWidgets 3.2 (a new API/ABI stable release) has been released a few
months ago and is now packaged in unstable as wxwidgets3.2. Upstream
has stopped supporting wxWidgets 3.0, so the Debian wx team would
like to migrate all wx package users to wxwidgets3.2 for bullseye,
with the plan to remove wxwidgets3.0 before release.

For most packages, the transition should be as simple as changing
Build-Depends from libwxgtk3.0-gtk3-dev to libwxgtk3.2-dev. Some
packages may require small patches; I'm happy to help with those (and
I have some already from working on this transition in Fedora
already).

Thanks, Scott 
--- End Message ---
--- Begin Message ---
Source: scorched3d
Source-Version: 44+dfsg-8
Done: Scott Talbert 

We believe that the bug you reported is fixed in the latest version of
scorched3d, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1019...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Scott Talbert  (supplier of updated scorched3d package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 01 Nov 2022 18:10:34 -0400
Source: scorched3d
Architecture: source
Version: 44+dfsg-8
Distribution: unstable
Urgency: medium
Maintainer: Debian Games Team 
Changed-By: Scott Talbert 
Closes: 1019784
Changes:
 scorched3d (44+dfsg-8) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Debian Janitor ]
   * Remove overrides for lintian tags that are no longer supported:
 no-upstream-changelog, no-upstream-changelog
   * Set upstream metadata fields: Archive, Bug-Database, Name.
   * Fix day-of-week for changelog entry 37.2-1.
   * Update standards version to 4.6.1, no changes needed.
   * Avoid explicitly specifying -Wl,--as-needed linker flag.
 .
   [ Scott Talbert ]
   * Transition to wxWidgets 3.2 (Closes: #1019784)
Checksums-Sha1:
 949cbf2576859621657d548b557c88a7fa32fcc6 2359 scorched3d_44+dfsg-8.dsc
 a63e77926dff3112f6b751742249d4d4b218cfa0 124104 
scorched3d_44+dfsg-8.debian.tar.xz
 27dfc17a5c80ec3392425a010962bc867019d4e9 13997 
scorched3d_44+dfsg-8_amd64.buildinfo
Checksums-Sha256:
 719a9abfc00805881d6f9ccf8e374be769b661c685aef605e6f7c39e66974800 2359 
scorched3d_44+dfsg-8.dsc
 aa999031dbcac57e4c535a79114641da5a87e7e7f272be01ceb1cf6f647891d1 124104 
scorched3d_44+dfsg-8.debian.tar.xz
 d0511c24dc085e25a8e43515feda00cb7fefd9dae1b9bf554e1c2336d9301838 13997 
scorched3d_44+dfsg-8_amd64.buildinfo
Files:
 19110fd9919d0466d055d6d3af9dee15 2359 games optional scorched3d_44+dfsg-8.dsc
 51d79914c8345d8e6601ece631050b01 124104 games optional 
scorched3d_44+dfsg-8.debian.tar.xz
 bf16f7abcd0c9cf5d16ecb5dcc67a03c 13997 games optional 
scorched3d_44+dfsg-8_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJDBAEBCgAtFiEEbnQ09Yl9Q7F/zVe3U9W8ZLUjeKIFAmNhpGEPHHN3dEB0ZWNo
aWUubmV0AAoJEFPVvGS1I3iijiAP/jS64pOxB0ljQsASC3L9LTpwjGiRxG92Z6Bq
MOLRiCR4pMw1CUkLXnOLf27ZVzMQ8icmbQUUV9u29/qfCvYW8bh6+P4mmLdeEWfr
owdlV6u+0Hfowneivt8hMJbibqQWcFj7zNSQneniFSubAIQt9gYahCsOiYmFgI3/
NS1c1VsA+qDaQeeogiKTtH8jlJnkoLZSQxiU2dOVArR31k97XnFtHWQ4h1undruB
hzLJPVRmBWtLrZYRhDe5TlaWOZTJU4V4p5LouIDNCbRCp9AkIduuWaDVCvan3A40
tLqHZ8g2WuxF3xvdL3L5P0AMuJJm5u85EnJ3nVF4IyAA0zfdjuPaKGxL+6oRgOAz
O3+xODCgY21eDgOYf+43WoIrhvOdTagLuXlscVz+eq+QllRwvTHMwfO/SHteIlur
Iw9/yx8nrnHP4yX2ZVkVue66DXhkHix1ZANi9ZQsXPIUir96yFRd8B1WXUIuE8ka
0HurUD7b7DicHROs7FVdeYahNMhpCcjvcqe6HkMn22FCUfQV7g3IP6YKQMXa4FR9
qgIAkDVa5goiPbcJbKDvdzhKct40ZhnMD3KCCN314YRhr3/TnT9kh59HSo/PjEkH
9hf2Zn9MT/G+CUODGBeG/8WXswnpa3IYj03811paZsIqBN/I0YETCwLEgG/fo6/3
glXkGbeg
=Sgi/
-END PGP SIGNATURE End Message ---

Bug#1023303: jhead 1:3.06.0.1-3 deletes EXIF data

[Stefan Pietsch]

Package: jhead
Version: 1:3.06.0.1-3
Severity: grave


jhead version 1:3.06.0.1-3 deletes EXIF data when rotating images:

$ exiftool IMG_20221102_000230.jpg | wc -l

77



$ jhead -autorot IMG_20221102_000230.jpg



Nonfatal Error : 'IMG_20221102_000230.jpg' Command has invalid characters.



$ exiftool IMG_20221102_000230.jpg | wc -l

23





jhead 1:3.06.0.1-2 is not affected.

Bug#1023065: marked as done (xuxen-eu-spell: stop building hunspell-eu)

[Debian Bug Tracking System]

Your message dated Tue, 01 Nov 2022 23:05:44 +
with message-id 
and subject line Bug#1023065: fixed in xuxen-eu-spell 3.0.20070215-2
has caused the Debian Bug report #1023065,
regarding xuxen-eu-spell: stop building hunspell-eu
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.)


-- 
1023065: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023065
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: xuxen-eu-spell
Version: 3.0.20070215-1
Severity: serious

hunspell-eu is now built by src:hunspell-eu. Please stop building it
from xuxen-eu-spell.


Andreas
--- End Message ---
--- Begin Message ---
Source: xuxen-eu-spell
Source-Version: 3.0.20070215-2
Done: Agustin Martin Domingo 

We believe that the bug you reported is fixed in the latest version of
xuxen-eu-spell, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1023...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Agustin Martin Domingo  (supplier of updated 
xuxen-eu-spell package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 01 Nov 2022 23:08:57 +0100
Source: xuxen-eu-spell
Architecture: source
Version: 3.0.20070215-2
Distribution: unstable
Urgency: medium
Maintainer: Agustin Martin Domingo 
Changed-By: Agustin Martin Domingo 
Closes: 1023065
Changes:
 xuxen-eu-spell (3.0.20070215-2) unstable; urgency=medium
 .
   * Stop building hunspell-eu, hunspell-eu is now built by
 src:hunspell-eu.  Thanks Andreas Beckmann (Closes: #1023065).
   * Bump Standards-Version. No changes required.
   * debian/copyright: Update debian copyright years.
   * Add some overrides.
Checksums-Sha1:
 f8c05e8f2a9b51b326dec34f5de80dd72f5fb31b 1966 xuxen-eu-spell_3.0.20070215-2.dsc
 29a3b3a8f6efc8eeef65fbc331d88a7c4085fa00 6684 
xuxen-eu-spell_3.0.20070215-2.debian.tar.xz
 03b69d131fa114803d3057661e7fbc982739ddd2 6321 
xuxen-eu-spell_3.0.20070215-2_amd64.buildinfo
Checksums-Sha256:
 5c44efa011485abb3776f8e8dd965f4a2cc02d34a4257fb22905f73e2b671e8e 1966 
xuxen-eu-spell_3.0.20070215-2.dsc
 d5670d5319ed6f1de97b52d390fe66b40764e1de7e7a3f8deda058106903ff2b 6684 
xuxen-eu-spell_3.0.20070215-2.debian.tar.xz
 0823a9dbb08e60e697ac82c373b9681fdf1e8fbb02e28e20fe2f723e9c18404d 6321 
xuxen-eu-spell_3.0.20070215-2_amd64.buildinfo
Files:
 464d8d5835cbadb7fb795d7e4a3632a2 1966 text optional 
xuxen-eu-spell_3.0.20070215-2.dsc
 268978489d0df992633eb410d43d 6684 text optional 
xuxen-eu-spell_3.0.20070215-2.debian.tar.xz
 136bd6df54518c0cce2a358b8f1004b9 6321 text optional 
xuxen-eu-spell_3.0.20070215-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEEehey7p+gYd346SEFJrCLeiggvwFAmNhn9sACgkQFJrCLeig
gvwBEw//YNJVmPMghbcTiBBzLmxJ6Kd9ZFyHm6QtQOZxNutsmQ18gRJ/1acPCxfU
6Gvw4gvvR2bxmOkpzfqah0jshV8wxk0J5RkHd46stZCXg8uVy/XTcxonJbzrXoDO
5WKxCgu6/Q1nVuI/cTSMPbbpaTU2Q3kFa2it5xZR3HY8QdzqCdYFRFp3IYp7zAat
9MEzL0mAmhz3Q6aORJRB+GJ3NViuO8QmKI588DGiY4bsXlABKoPGi32+ptIhRWHn
R2G4iJdpGrIM0DgvjWjn40fb0V+f+l9d/B287nafgye9SsDjTdGBeBuzrOlrHr7E
BlbtFw5kY3HVWJI6RgROErCHoGGs0FPNFGpsBQBwMvD9yt96RetTdkTd+5K+K4As
+yUqNwxPqhW5qT0p6yRO34q7tP6boRph+zzAqfCc5UhncFDnnCKFDe4VbkvWQjmH
HRCyDCFuxy3jGz+x06r2JfkdYKB/KmaWfJusiVq5QV2K3vlooIl2q50HfFbo6MrB
HhIycRr5XLkhw9gpYMimuXiZ8sz898zJicFPm6cZIfFaF0WZ8SeL/O41aXgMZS5M
ORJ5ZF46UW3JEmXzXlsOW/ACenCtv9Y2TunykQy4o4SnnP9s3n1rtEyXO9zaR7oB
wTUT0ixtbBARtvhTphUgqaC8a2FopZzXnfXh4s8j7QLwR7eLdUc=
=oOpg
-END PGP SIGNATURE End Message ---

Processed: Bug#1019784 marked as pending in scorched3d

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1019784 [src:scorched3d] scorched3d: Please transition to wxwidgets3.2
Added tag(s) pending.

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

Bug#1019784: marked as pending in scorched3d

[Scott Talbert]

Control: tag -1 pending

Hello,

Bug #1019784 in scorched3d reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/games-team/scorched3d/-/commit/d997808b68bc1901ef182933177a53704d15cb01


Transition to wxWidgets 3.2 (Closes: #1019784)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1019784

Bug#967987: fuzz: diff for NMU version 0.6-19.1

[Marcos Talau]

Control: tags 967987 + pending

Dear maintainer,

I've prepared an NMU for fuzz (versioned as 0.6-19.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Regards.
diff -Nru fuzz-0.6/debian/changelog fuzz-0.6/debian/changelog
--- fuzz-0.6/debian/changelog	2020-09-28 09:32:35.0 -0300
+++ fuzz-0.6/debian/changelog	2022-11-01 19:09:03.0 -0300
@@ -1,3 +1,12 @@
+fuzz (0.6-19.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/patches/30-glibc-2.32.patch: Fix FTBFS against glibc 2.32 by using
+strerror() instead of sys_errlist. Thanks to Logan Rosen .
+(Closes: #967987).
+
+ -- Marcos Talau   Tue, 01 Nov 2022 19:09:03 -0300
+
 fuzz (0.6-19) unstable; urgency=medium
 
   * debian/control:
diff -Nru fuzz-0.6/debian/patches/30-glibc-2.32.patch fuzz-0.6/debian/patches/30-glibc-2.32.patch
--- fuzz-0.6/debian/patches/30-glibc-2.32.patch	1969-12-31 21:00:00.0 -0300
+++ fuzz-0.6/debian/patches/30-glibc-2.32.patch	2022-11-01 19:09:03.0 -0300
@@ -0,0 +1,19 @@
+Description: Fix FTBFS against glibc 2.32
+Author: Logan Rosen 
+Bug-Debian: https://bugs.debian.org/967987
+Forwarded: https://sourceforge.net/p/fuzz/bugs/6
+Last-Update: 2022-11-01
+
+Index: fuzz-0.6/fuzz.c
+===
+--- fuzz-0.6.orig/fuzz.c
 fuzz-0.6/fuzz.c
+@@ -814,7 +814,7 @@ void do_child(int *progpipe, char **argv
+ 
+   execv(progname,arguments);
+   write(cpy_stderr,"Exec failed.\n",strlen("Exec failed.\n"));
+-  write(cpy_stderr,sys_errlist[errno],strlen(sys_errlist[errno]));
++  write(cpy_stderr,strerror(errno),strlen(strerror(errno)));
+   exit(CANT_FORK_EXIT);
+ }
+ 
diff -Nru fuzz-0.6/debian/patches/series fuzz-0.6/debian/patches/series
--- fuzz-0.6/debian/patches/series	2016-10-19 04:16:45.0 -0200
+++ fuzz-0.6/debian/patches/series	2022-11-01 19:09:03.0 -0300
@@ -1,3 +1,4 @@
 10-fuzz.1-manpage-fixes.patch
 10-fuzz.1-manpage-fixes=11-newlines.patch
 20-fuzz.c--option-chroot.patch
+30-glibc-2.32.patch

Processed: fuzz: diff for NMU version 0.6-19.1

[Debian Bug Tracking System]

Processing control commands:

> tags 967987 + pending
Bug #967987 [fuzz] fuzz: Removal of sys_errlist
Added tag(s) pending.

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

Bug#1022289: [pkg-gnupg-maint] Bug#1022289: libassuan: FTBFS: configure: error: libgpg-error was not found

[Daniel Kahn Gillmor]

Hi Andreas--

Thanks for this.  I'm wrapping this up with a few other lintian fixes
and i should have a released version in unstable by later today or
tomorrow.

Thanks for helping out here!

--dkg

On Tue 2022-11-01 14:10:36 +0100, Andreas Metzler wrote:
> On 2022-10-23 Andreas Metzler  wrote:
> [...]
>> Caused by new gpg-error dropping gpg-error-config, this works for me:
>
>> --- libassuan-2.5.5/debian/rules2022-04-30 17:47:12.0 +0200
>> +++ patched/libassuan-2.5.5.patched/debian/rules2022-10-23 
>> 18:23:40.505849321 +0200
>> @@ -27,7 +27,6 @@
>> for cpu in i686 x86_64; do \
>>  mkdir -p build-$$cpu-w64-mingw32 && \
>>  cd build-$$cpu-w64-mingw32 && $(WIN_FLAGS) ../configure \
>> -   --with-libgpg-error-prefix=/usr/$$cpu-w64-mingw32 \
>
> Hello,
>
> Commited to GIT, please give me a heads up if you want me to make either
> a NMU or add myself to Uploaders and make a regular upload. (Although
> this is a serious bugreport I do not think it is yet so urgent to
> require a upload without maintainer feedback. - Might change, e.g if
> libassuan blocked a transition.)
>
> cu Andreas
> -- 
> `What a good friend you are to him, Dr. Maturin. His other friends are
> so grateful to you.'
> `I sew his ears on from time to time, sure'
> ___
> pkg-gnupg-maint mailing list
> pkg-gnupg-ma...@alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-gnupg-maint


signature.asc
Description: PGP signature

Bug#1017711: emacs-gtk: terminated with signal SIGABRT, 137 MB coredump

[Vincent Lefevre]

On 2022-10-31 15:59:17 +0100, Vincent Lefevre wrote:
> Hi,
> 
> On 2022-10-30 06:31:27 -0700, Sean Whitton wrote:
> > I've backported a couple of patches from upstream related to native
> > compilation, now, so would you be able to test again with the latest
> > upload?  Thanks.
> 
> If you mean 1:28.2+1-3, I still got the same issue. But it seems
> that after a reboot, the problem no longer occurs (after removing
> the .emacs.d directory). Was a reboot needed?

Unfortunately, it has just occurred again (with emacs run by
Subversion to enter a commit message).

Core was generated by `/usr/bin/emacs -no-comp-spawn --batch -l 
/tmp/emacs-async-comp-url.el-FGov4z.el'.
Program terminated with signal SIGABRT, Aborted.
#0  __pthread_kill_implementation (threadid=, 
signo=signo@entry=6, no_tid=no_tid@entry=0) at ./nptl/pthread_kill.c:44
44  ./nptl/pthread_kill.c: No such file or directory.

I've attached the backtrace. Seems too many recursive calls to
mark_object and mark_objects.

Worse, not just a background emacs process, the UI also crashes
(IIRC, this didn't happen before).

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Thread 1 (Thread 0x7f5b914cb380 (LWP 35005)):
#0  __pthread_kill_implementation (threadid=, 
signo=signo@entry=6, no_tid=no_tid@entry=0) at ./nptl/pthread_kill.c:44
tid = 
ret = 0
pd = 
old_mask = {__val = {0 }}
ret = 
#1  0x7f5b922895df in __pthread_kill_internal (signo=6, threadid=) at ./nptl/pthread_kill.c:78
#2  0x7f5b9223da02 in __GI_raise (sig=sig@entry=6) at 
../sysdeps/posix/raise.c:26
ret = 
#3  0x55fdfd114864 in terminate_due_to_signal (sig=sig@entry=6, 
backtrace_limit=backtrace_limit@entry=40) at ./debian/build-src/src/emacs.c:437
#4  0x55fdfd114d27 in emacs_abort () at ./debian/build-src/src/sysdep.c:2282
#5  0x55fdfd111e99 in check_message_stack () at 
./debian/build-src/src/xdisp.c:12157
#6  0x55fdfd20492a in shut_down_emacs (sig=0, stuff=0x0) at 
./debian/build-src/src/emacs.c:2789
tpgrp = 
#7  0x55fdfd114765 in Fkill_emacs (arg=arg@entry=0x6) at 
./debian/build-src/src/emacs.c:2692
exit_code = 
#8  0x55fdfd114827 in terminate_due_to_signal (sig=sig@entry=1, 
backtrace_limit=backtrace_limit@entry=40) at ./debian/build-src/src/emacs.c:417
#9  0x55fdfd114d00 in handle_fatal_signal (sig=sig@entry=1) at 
./debian/build-src/src/sysdep.c:1762
#10 0x55fdfd114d17 in deliver_process_signal (handler=0x55fdfd114cf5 
, sig=1) at ./debian/build-src/src/sysdep.c:1720
old_errno = 2
on_main_thread = true
#11 deliver_fatal_signal (sig=1) at ./debian/build-src/src/sysdep.c:1768
#12 0x7f5b9223daa0 in  () at 
/lib/x86_64-linux-gnu/libc.so.6
#13 0x55fdfd2641c3 in mark_object (arg=0x295d90329a68) at 
./debian/build-src/src/alloc.c:6628
obj = 0x295d90329a68
po = 
cdr_count = 0
#14 0x55fdfd26528e in mark_objects (n=3, obj=0x7f5b8e029930) at 
./debian/build-src/src/alloc.c:6607
i = 0
ptr = 0x7f5b8e029928
size = 3
#15 mark_vectorlike (header=0x7f5b8e029928) at 
./debian/build-src/src/alloc.c:6382
ptr = 0x7f5b8e029928
size = 3
#16 0x55fdfd26528e in mark_objects (n=3, obj=0x7f5b8e0298c0) at 
./debian/build-src/src/alloc.c:6607
i = 2
ptr = 0x7f5b8e0298b8
size = 3
#17 mark_vectorlike (header=0x7f5b8e0298b8) at 
./debian/build-src/src/alloc.c:6382
ptr = 0x7f5b8e0298b8
size = 3
#18 0x55fdfd26528e in mark_objects (n=711, obj=0x7f5b8e027fc8) at 
./debian/build-src/src/alloc.c:6607
i = 614
ptr = 0x7f5b8e027fc0
size = 711
#19 mark_vectorlike (header=0x7f5b8e027fc0) at 
./debian/build-src/src/alloc.c:6382
ptr = 0x7f5b8e027fc0
size = 711
#20 0x55fdfd26528e in mark_objects (n=7, obj=0x7f5b8da7eab8) at 
./debian/build-src/src/alloc.c:6607
i = 5
ptr = 0x7f5b8da7eab0
size = 7
#21 mark_vectorlike (header=0x7f5b8da7eab0) at 
./debian/build-src/src/alloc.c:6382
ptr = 0x7f5b8da7eab0
size = 7
#22 0x55fdfd2646ed in mark_object (arg=) at 
./debian/build-src/src/alloc.c:6787
subr = 0x7f5b8df6d260
ptr = 0x7f5b8df6d260
pvectype = 
obj = 0x7f5b8df6d265
po = 0x7f5b8df6d260
cdr_count = 0
#23 0x55fdfd2642d3 in mark_object (arg=) at 
./debian/build-src/src/alloc.c:6815
ptr = 0x7f5b8df6d230
obj = 
po = 0x7f5b8df6d230
cdr_count = 
#24 0x55fdfd26528e in mark_objects (n=5, obj=0x55fdff0253d8) at 
./debian/build-src/src/alloc.c:6607
i = 3
ptr = 0x55fdff0253d0
size = 5
#25 mark_vectorlike (header=0x55fdff0253d0) at 
./debian/build-src/src/alloc.c:6382
ptr = 0x55fdff0253d0
size = 5
#26 0x55fdfd2642d3 in mark_object (arg=) at 

Bug#1023298: linux: FTBFS on arm64 and armhf (ABI changes)

[Salvatore Bonaccorso]

Source: linux
Version: 6.0.6-2
Severity: serious
Justification: FTBFS
X-Debbugs-Cc: car...@debian.org

Documenting the build failures on arm64 and armhf due to ABI changes:

https://buildd.debian.org/status/fetch.php?pkg=linux=arm64=6.0.6-2=1667324068=0
https://buildd.debian.org/status/fetch.php?pkg=linux=armhf=6.0.6-2=1667316319=0

Regards,
Salvatore

Bug#1023299: ganeti-testsuite: yaml.load in testsuite needs to specify loader

[Scott Kitterman]

Source: ganeti-testsuite
Version: 3.0.2-1
Severity: serious
Tags: upstream ftbfs
Justification: fails to build from source
X-Debbugs-Cc: debian-pyt...@lists.debian.org

Previously yaml.load did not require a loader to be specified:

load(stream, Loader=None)

Now it does (starting in pyyaml 6.0):

load(stream, Loader)

Ganeti-testsuit uses yaml.load without specifying a loader, which now
causes a test failure in unstable.  Due to ganeti not being buildable
currently, it's not possible to fix this at the moment.

Note: Using FTBFS as a tag since that's the closest thing we have to a
test failure that would prevent migration.

Scott K

Bug#1019792: marked as done (springlobby: Please transition to wxwidgets3.2)

[Debian Bug Tracking System]

Your message dated Tue, 01 Nov 2022 21:09:15 +
with message-id 
and subject line Bug#1019792: fixed in springlobby 0.273-2
has caused the Debian Bug report #1019792,
regarding springlobby: Please transition to wxwidgets3.2
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.)


-- 
1019792: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019792
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: springlobby
Severity: normal
Control: block 1019416 by -1

Hi,

Please transition springlobby from wxwidgets3.0 to wxwidgets3.2.

wxWidgets 3.2 (a new API/ABI stable release) has been released a few
months ago and is now packaged in unstable as wxwidgets3.2. Upstream
has stopped supporting wxWidgets 3.0, so the Debian wx team would
like to migrate all wx package users to wxwidgets3.2 for bullseye,
with the plan to remove wxwidgets3.0 before release.

For most packages, the transition should be as simple as changing
Build-Depends from libwxgtk3.0-gtk3-dev to libwxgtk3.2-dev. Some
packages may require small patches; I'm happy to help with those (and
I have some already from working on this transition in Fedora
already).

Thanks, Scott 
--- End Message ---
--- Begin Message ---
Source: springlobby
Source-Version: 0.273-2
Done: Scott Talbert 

We believe that the bug you reported is fixed in the latest version of
springlobby, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1019...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Scott Talbert  (supplier of updated springlobby package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 01 Nov 2022 16:31:26 -0400
Source: springlobby
Architecture: source
Version: 0.273-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Games Team 
Changed-By: Scott Talbert 
Closes: 1019792
Changes:
 springlobby (0.273-2) unstable; urgency=medium
 .
   * Team upload.
   * Transition to wxWidgets 3.2 (Closes: #1019792)
Checksums-Sha1:
 0bb051b83fc663d16a5e700dde396c1aa3a19608 2178 springlobby_0.273-2.dsc
 7677be17b216c4b8b786fff1fa80782c46eb3318 16960 
springlobby_0.273-2.debian.tar.xz
 d24338c509de004c8becdfa408dd50a2e9d9bf1c 19534 
springlobby_0.273-2_amd64.buildinfo
Checksums-Sha256:
 83e40ee3a95c58e0fb58e45878e3b18e45307d32f52c679a3f187c0e24b7d528 2178 
springlobby_0.273-2.dsc
 b57cf869083ef6ae5d197114483b6705e87f7957a9b773414c778aa9a8a2f71e 16960 
springlobby_0.273-2.debian.tar.xz
 fc79188d66b957ea9b748a95ded6dc0c5b32e54d4f850ac8cfb9e0104a7b3dc7 19534 
springlobby_0.273-2_amd64.buildinfo
Files:
 f52e8a4a257071c0d78d65bfdbf65a85 2178 games optional springlobby_0.273-2.dsc
 9e57300ab35415e6320118cdf2953dfe 16960 games optional 
springlobby_0.273-2.debian.tar.xz
 ee288f41f3dabef5336d3d920acfbf8e 19534 games optional 
springlobby_0.273-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJDBAEBCgAtFiEEbnQ09Yl9Q7F/zVe3U9W8ZLUjeKIFAmNhhZcPHHN3dEB0ZWNo
aWUubmV0AAoJEFPVvGS1I3iibYwP/3OLGH6xQ8SrG8SDVQinpZKH4yImP1Wf/0mc
iO//HNuNenjS1JEX5V3aJnBWfMkb2bPl9tAukZuF76rOFn9X5o1lqix09HhqhSLu
MT320wHlNZ5Hity/VhvdWzXwxcli/iuHPf9Qf4vq8jpvRG8f19wcfLL6nrbrfXEC
cG+hMfaywLRT+EQ86mUnDkxxZsT9cEWl2tfH9QRZO/6nCK4iXnY9SlgeE4kIQbOn
GeSyayzdGm8BrrS5ERPI7pcUxi2vWKLQJZCNo41ndNZCZTd6OA6qgCH39wHrK1pM
+V0zA8OqvPGxIr9eNkSST5FKpHYpLUaioQaZ9/oON4bTNttFldVnvB5tDTcWQjPN
3kgwi0QmYSlrH8ecyRNhzWBdwU+1hXxmW8KtgiMmKZhihDb0gGOlo3/ESRZ5Zelv
IviEaOYAfTmK1LYFZaDA5HYJvgjP5yWL7AdrvrZvOMxMdAt0cSy6VXEsVZLaXdAt
uwcu6yt2rk/zEFhIp6tcehCCFtC/lECbAsz2lUzWn7VeQQVPrbQfzbncoy4k8IkO
DxQ/qdkdfBxhcOHMfWJqqLwXEBi+VXQVJ9by3OIefYPSpm4ukT0MJyRLXbx/apuh
SlpyEAkIwP/8VnrA3gC0a/p6JA0Y6CmaPHMZiuV6LkbrL3S6BdxkK6w08/VbrFEp
bInWc1u2
=kPgl
-END PGP SIGNATURE End Message ---

Processed: Bug#1019792 marked as pending in springlobby

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1019792 [src:springlobby] springlobby: Please transition to wxwidgets3.2
Added tag(s) pending.

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

Bug#1019792: marked as pending in springlobby

[Scott Talbert]

Control: tag -1 pending

Hello,

Bug #1019792 in springlobby reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/games-team/springlobby/-/commit/a0cad0c3f5090dcd96ffef2f09a13ea6c7ffd188


Transition to wxWidgets 3.2 (Closes: #1019792)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1019792

Processed: src:emacs: fails to migrate to testing for too long: unresolved RC issues

[Debian Bug Tracking System]

Processing control commands:

> close -1 1:28.2+1-3
Bug #1023297 [src:emacs] src:emacs: fails to migrate to testing for too long: 
unresolved RC issues
Marked as fixed in versions emacs/1:28.2+1-3.
Bug #1023297 [src:emacs] src:emacs: fails to migrate to testing for too long: 
unresolved RC issues
Marked Bug as done
> block -1 by 1017711 1020258
Bug #1023297 {Done: Paul Gevers } [src:emacs] src:emacs: 
fails to migrate to testing for too long: unresolved RC issues
1023297 was not blocked by any bugs.
1023297 was not blocking any bugs.
Added blocking bug(s) of 1023297: 1020258 and 1017711

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

Bug#1023297: src:emacs: fails to migrate to testing for too long: unresolved RC issues

[Paul Gevers]

Source: emacs
Version: 1:27.1+1-3.1
Severity: serious
Control: close -1 1:28.2+1-3
Tags: sid bookworm
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 1017711 1020258

Dear maintainer(s),

[I know you probably know I understand the delay, but to be transparent 
I'm filing this bug anyways. emacs is a key package so will not be 
autoremoved.]


The Release Team considers packages that are out-of-sync between testing 
and unstable for more than 60 days as having a Release Critical bug in 
testing [1]. Your package src:emacs has been trying to migrate for 74 
days [2]. Hence, I am filing this bug.


If a package is out of sync between unstable and testing for a longer 
period, this usually means that bugs in the package in testing cannot be 
fixed via unstable. Additionally, blocked packages can have impact on 
other packages, which makes preparing for the release more difficult. 
Finally, it often exposes issues with the package and/or
its (reverse-)dependencies. We expect maintainers to fix issues that 
hamper the migration of their package in a timely manner.


This bug will trigger auto-removal when appropriate. As with all new 
bugs, there will be at least 30 days before the package is auto-removed.


I have immediately closed this bug with the version in unstable, so if 
that version or a later version migrates, this bug will no longer affect 
testing. I have also tagged this bug to only affect sid and bookworm, so 
it doesn't affect (old-)stable.


If you believe your package is unable to migrate to testing due to 
issues beyond your control, don't hesitate to contact the Release Team.


Paul

[1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html
[2] https://qa.debian.org/excuses.php?package=emacs



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1013158: facet-analyser: vtk[6,7] removal

[Anton Gladky]

Hi Picca,

I have just successfully cloned the git-repo. I have only got a warning
"[attr]our-c-style   whitespace=tab-in-indent  format.clang-format=9 n"
but I thinking it is not critical.

Please try to checkout it again. Maybe it was salsa issue?

Regards

Anton


Am Di., 1. Nov. 2022 um 10:18 Uhr schrieb PICCA Frederic-Emmanuel <
frederic-emmanuel.pi...@synchrotron-soleil.fr>:

> Hello Anton, I try to checkout paraview in order to add the -dev
> dependencies
>
> but I have this message
>
> $ git clone https://salsa.debian.org/science-team/paraview
> Clonage dans 'paraview'...
> remote: Enumerating objects: 175624, done.
> remote: Counting objects: 100% (78929/78929), done.
> remote: Compressing objects: 100% (38687/38687), done.
> remote: Total 175624 (delta 47039), reused 65625 (delta 39190),
> pack-reused 96695
> Réception d'objets: 100% (175624/175624), 246.21 Mio | 12.11 Mio/s, fait.
> Résolution des deltas: 100% (109096/109096), fait.
> [attr]our-c-style  whitespace=tab-in-indent,-blank-at-eol
> format.clang-format non permis :
> ThirdParty/QtTesting/vtkqttesting/.gitattributes : 8
> [attr]our-c-style  whitespace=tab-in-indent,-blank-at-eol
> format.clang-format=9 non permis :
> ThirdParty/catalyst/vtkcatalyst/catalyst/.gitattributes : 4
> [attr]our-c-style  whitespace=tab-in-indent,-blank-at-eol
> format.clang-format=8 non permis : VTK/.gitattributes : 10
> [attr]our-c-style   whitespace=tab-in-indent  format.clang-format=9 non
> permis : VTK/ThirdParty/vtkm/vtkvtkm/vtk-m/.gitattributes : 2
> Mise à jour des fichiers: 100% (30828/30828), fait.
> [attr]our-c-style  whitespace=tab-in-indent,-blank-at-eol
> format.clang-format=8 non permis : VTK/.gitattributes : 10
> [attr]our-c-style   whitespace=tab-in-indent  format.clang-format=9 non
> permis : VTK/ThirdParty/vtkm/vtkvtkm/vtk-m/.gitattributes : 2
> Downloading VTK/ThirdParty/vtkm/vtkvtkm/vtk-m/data/README.md (643 B)
> Error downloading object: VTK/ThirdParty/vtkm/vtkvtkm/vtk-m/data/README.md
> (b30a14a): Smudge error: Error downloading
> VTK/ThirdParty/vtkm/vtkvtkm/vtk-m/data/README.md
> (b30a14a308f64c6fc2969e2b959d79dacdc5affda1d1c0e24f8e176304147146):
> [b30a14a308f64c6fc2969e2b959d79dacdc5affda1d1c0e24f8e176304147146] Object
> does not exist on the server or you don't have permissions to access it:
> [404] Object does not exist on the server or you don't have permissions to
> access it
>
> Errors logged to
> /home/experiences/instrumentation/picca/debian/science-team/paraview/.git/lfs/logs/20221101T101535.441130442.log
> Use `git lfs logs last` to view the log.
> error: le filtre externe 'git-lfs filter-process' a échoué
> fatal: VTK/ThirdParty/vtkm/vtkvtkm/vtk-m/data/README.md : le filtre smudge
> 'lfs' a échoué
> warning: Le clone a réussi, mais l'extraction a échoué.
> Vous pouvez inspecter ce qui a été extrait avec 'git status'
> et réessayer avec 'git restore --source=HEAD :/'
>

Bug#1023290: golang-raven-go: Include outdated copy of CA bundles

[Shengjing Zhu]

Source: golang-raven-go
Version: 0.2.0+ds1-2
Severity: serious
Tags: security
X-Debbugs-Cc: z...@debian.org, prav...@debian.org

Hi Pirate Praveen,

In 2018, you said we should not package golang-github-certifi-gocertifi[1],
as we should use the system CA bundles.

But why you include that in the vendor dir[2] in golang-raven-go?

[1] https://lists.debian.org/debian-go/2018/12/msg00065.html
[2] 
https://salsa.debian.org/go-team/packages/golang-raven-go/-/tree/debian/0.2.0+ds1-1/vendor/github.com/certifi/gocertifi

Bug#1022393: moment-timezone.js: FTBFS: make[1]: *** [debian/rules:12: data/meta/2022c.json] Error 1

[Antoine Beaupré]

On 2022-10-23 15:21:14, Lucas Nussbaum wrote:
>> make[1]: Entering directory '/<>'
>> # Fail the build if the tzdata package does not match TZVER.
>> grep -q '^# version 2022c$' /usr/share/zoneinfo/tzdata.zi
>> make[1]: *** [debian/rules:12: data/meta/2022c.json] Error 1

this looks like a failure due to the tzdata update... it looks like the
fix is just to update to latest upstream:

https://github.com/moment/moment-timezone/releases/tag/0.5.38

a.

-- 
Hard times are coming when we will be wanting the voices of writers
who can see alternatives to how we live now and can see through our
fear-stricken society and its obsessive technologies to other ways of
being, and even imagine some real grounds for hope. We will need
writers who can remember freedom. Poets, visionaries—the realists of a
larger reality. - Ursula Le Guin

Bug#1023284: libevent: FTBFS with glibc 2.36

[Samuel Thibault]

Source: libevent
Version: 2.0.21-stable-2+deb8u1
Severity: serious
Justification: FTBFS

Hello,

Since the upload of glibc 2.36 in unstable (2.36-3), libevent fails to
build from source:

dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols 
file: see diff output below
dpkg-gensymbols: warning: debian/libevent-core-2.1-7/DEBIAN/symbols doesn't 
match completely debian/libevent-core-2.1-7.symbols
--- debian/libevent-core-2.1-7.symbols 
(libevent-core-2.1-7_2.1.12-stable-5_amd64)
+++ dpkg-gensymbolse6mOZa   2022-11-01 18:35:41.660556092 +0100
@@ -394,7 +394,7 @@
  evutil_parse_sockaddr_port@Base 2.1.8-stable
  evutil_read_file_@Base 2.1.8-stable
  evutil_rtrim_lws_@Base 2.1.8-stable
- evutil_secure_rng_add_bytes@Base 2.1.8-stable
+#MISSING: 2.1.12-stable-5# evutil_secure_rng_add_bytes@Base 2.1.8-stable
  evutil_secure_rng_get_bytes@Base 2.1.8-stable
  evutil_secure_rng_global_setup_locks_@Base 2.1.8-stable
  evutil_secure_rng_init@Base 2.1.8-stable

That's probably due the addition of arc4random in glibc, which makes

#if !defined(EVENT__HAVE_ARC4RANDOM) || 
defined(EVENT__HAVE_ARC4RANDOM_ADDRANDOM)
void
evutil_secure_rng_add_bytes(const char *buf, size_t n)
{
arc4random_addrandom((unsigned char*)buf,
n>(size_t)INT_MAX ? INT_MAX : (int)n);
}
#endif

not define evutil_secure_rng_add_bytes any more.

Samuel

-- System Information:
Debian Release: bookworm/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 
'testing-debug'), (500, 'stable-security'), (500, 'stable-debug'), (500, 
'proposed-updates-debug'), (500, 'proposed-updates'), (500, 
'oldstable-proposed-updates'), (500, 'oldoldstable'), (500, 'buildd-unstable'), 
(500, 'unstable'), (500, 'stable'), (500, 'oldstable'), (1, 
'experimental-debug'), (1, 'buildd-experimental'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, arm64

Kernel: Linux 6.0.0 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

-- 
Samuel
---
Pour une évaluation indépendante, transparente et rigoureuse !
Je soutiens la Commission d'Évaluation de l'Inria.

Processed: tagging 1011977

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 1011977 + fixed-in-experimental
Bug #1011977 [src:htsjdk] FTBFS with OpenJDK 17: 5 failing tests
Added tag(s) fixed-in-experimental.
> thanks
Stopping processing here.

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

Bug#1022398: marked as done (bladerf: FTBFS: dh_install: error: missing files, aborting)

[Debian Bug Tracking System]

Your message dated Tue, 01 Nov 2022 17:19:34 +
with message-id 
and subject line Bug#1022398: fixed in bladerf 0.2021.10-4
has caused the Debian Bug report #1022398,
regarding bladerf: FTBFS: dh_install: error: missing files, aborting
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.)


-- 
1022398: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022398
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: bladerf
Version: 0.2021.10-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221023 ftbfs-bookworm

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
> make[3]: Entering directory '/<>/obj-x86_64-linux-gnu'
> make[3]: Nothing to be done for 'preinstall'.
> make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu'
> Install the project...
> /usr/bin/cmake -P cmake_install.cmake
> -- Install configuration: "RelWithDebInfo"
> -- Installing: 
> /<>/debian/tmp/usr/lib/x86_64-linux-gnu/pkgconfig/libbladeRF.pc
> -- Installing: 
> /<>/debian/tmp/usr/lib/x86_64-linux-gnu/libbladeRF.so.2
> -- Installing: 
> /<>/debian/tmp/usr/lib/x86_64-linux-gnu/libbladeRF.so
> -- Installing: /<>/debian/tmp/usr/share/doc/libbladerf-doc/html
> -- Installing: 
> /<>/debian/tmp/usr/share/doc/libbladerf-doc/html/dir_9be5de2ace8d8c3e15cf38969cc3d3a4.html
> -- Installing: 
> /<>/debian/tmp/usr/share/doc/libbladerf-doc/html/annotated.html
> -- Installing: 
> /<>/debian/tmp/usr/share/doc/libbladerf-doc/html/globals_eval.html
> -- Installing: 
> /<>/debian/tmp/usr/share/doc/libbladerf-doc/html/structbladerf__loopback__modes.html
> -- Installing: 
> /<>/debian/tmp/usr/share/doc/libbladerf-doc/html/blade_r_f2_8h.html
> -- Installing: 
> /<>/debian/tmp/usr/share/doc/libbladerf-doc/html/nav_g.png
> -- Installing: 
> /<>/debian/tmp/usr/share/doc/libbladerf-doc/html/dir_e5580c48c42f8c997ea83e33bdfb6840.html
> -- Installing: 
> /<>/debian/tmp/usr/share/doc/libbladerf-doc/html/group___f_n___b_l_a_d_e_r_f2___l_o_w___l_e_v_e_l___c_l_o_c_k___b_u_f_f_e_r.html
> -- Installing: 
> /<>/debian/tmp/usr/share/doc/libbladerf-doc/html/dynsections.js
> -- Installing: 
> /<>/debian/tmp/usr/share/doc/libbladerf-doc/html/group___f_n___b_l_a_d_e_r_f1___g_a_i_n.html
> -- Installing: 
> /<>/debian/tmp/usr/share/doc/libbladerf-doc/html/closed.png
> -- Installing: 
> /<>/debian/tmp/usr/share/doc/libbladerf-doc/html/structbladerf__rational__rate.html
> -- Installing: 
> /<>/debian/tmp/usr/share/doc/libbladerf-doc/html/todo.html
> -- Installing: 
> /<>/debian/tmp/usr/share/doc/libbladerf-doc/html/group___f_n___b_l_a_d_e_r_f1___s_a_m_p_l_i_n_g___m_u_x.html
> -- Installing: 
> /<>/debian/tmp/usr/share/doc/libbladerf-doc/html/dir_4f7e4242e27b8c8b476722507617a881.html
> -- Installing: 
> /<>/debian/tmp/usr/share/doc/libbladerf-doc/html/group___f_n___t_u_n_i_n_g___m_o_d_e.html
> -- Installing: 
> /<>/debian/tmp/usr/share/doc/libbladerf-doc/html/group___f_n___w_i_s_h_b_o_n_e___m_a_s_t_e_r.html
> -- Installing: 
> /<>/debian/tmp/usr/share/doc/libbladerf-doc/html/structbladerf__version.html
> -- Installing: 
> /<>/debian/tmp/usr/share/doc/libbladerf-doc/html/tabs.css
> -- Installing: 
> /<>/debian/tmp/usr/share/doc/libbladerf-doc/html/group___f_n___s_m_b___c_l_o_c_k.html
> -- Installing: 
> /<>/debian/tmp/usr/share/doc/libbladerf-doc/html/doxygen.css
> -- Installing: 
> /<>/debian/tmp/usr/share/doc/libbladerf-doc/html/blade_r_f1_8h_source.html
> -- Installing: 
> /<>/debian/tmp/usr/share/doc/libbladerf-doc/html/functions.html
> -- Installing: 
> /<>/debian/tmp/usr/share/doc/libbladerf-doc/html/sync_off.png
> -- Installing: 
> /<>/debian/tmp/usr/share/doc/libbladerf-doc/html/group___f_n___l_o_o_p_b_a_c_k.html
> -- Installing: 
> /<>/debian/tmp/usr/share/doc/libbladerf-doc/html/group___f_n___t_u_n_i_n_g.html
> -- Installing: 
> /<>/debian/tmp/usr/share/doc/libbladerf-doc/html/group___f_n___s_c_h_e_d_u_l_e_d___t_u_n_i_n_g.html
> -- Installing: 
> /<>/debian/tmp/usr/share/doc/libbladerf-doc/html/sync_rx_meta.html
> -- Installing: 
> /<>/debian/tmp/usr/share/doc/libbladerf-doc/html/group___f_n___b_l_a_d_e_r_f2___l_o_w___l_e_v_e_l___p_l_l.html
> -- Installing: 
> /<>/debian/tmp/usr/share/doc/libbladerf-doc/html/sync_tx_meta_bursts.html
> -- Installing: 
> /<>/debian/tmp/usr/share/doc/libbladerf-doc/html/group___f_n___c_h_a_n_n_e_l.html
> -- Installing: 
> /<>/debian/tmp/usr/share/doc/libbladerf-doc/html/pages.html
> -- Installing: 
> /<>/debian/tmp/usr/share/doc/libbladerf-doc/html/group___f_n___b_l_a_d_e_r_f2___l_o_w___l_e_v_e_l___p_m_i_c.html
> 

Processed: control

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> fixed 1022319 0.0~git20220518.5b14351-3
Bug #1022319 [src:gloo] gloo: FTBFS: ethtool.h:2088:17: error: flexible array 
member ‘ethtool_link_settings::link_mode_masks’ not at end of ‘struct 
gloo::getInterfaceSpeedGLinkSettings(int, ifreq*)::’
Marked as fixed in versions gloo/0.0~git20220518.5b14351-3.
> close 1022319
Bug #1022319 [src:gloo] gloo: FTBFS: ethtool.h:2088:17: error: flexible array 
member ‘ethtool_link_settings::link_mode_masks’ not at end of ‘struct 
gloo::getInterfaceSpeedGLinkSettings(int, ifreq*)::’
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#1022398: bladerf: FTBFS: dh_install: error: missing files, aborting

[Christoph Berg]

> > # Python3 bindings
> > python3 host/libraries/libbladeRF_bindings/python/setup.py install 
> > --root=debian/tmp/ --prefix=/usr
...
> > Copying bladerf.egg-info to 
> > debian/tmp/usr/local/lib/python3.10/dist-packages/bladerf-1.2.1-py3.10.egg-info
> > running install_scripts
> > Installing bladerf-tool script to debian/tmp/usr/local/bin

> >dh_install
> > dh_install: warning: Cannot find (any matches for) 
> > "usr/lib/python3*/site-packages/*" (tried in ., debian/tmp)

The problem here is that setup.py installs into tmp/usr/local despite
being told to use --prefix=/usr.

I have no idea why it's doing that and couldn't find a sane fix, so I
added a "mv usr/local usr" workaround to debian/rules.

Christoph

Processed: Bug#1022398 marked as pending in bladerf

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1022398 [src:bladerf] bladerf: FTBFS: dh_install: error: missing files, 
aborting
Added tag(s) pending.

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

Bug#1022398: marked as pending in bladerf

[Christoph Berg]

Control: tag -1 pending

Hello,

Bug #1022398 in bladerf reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/debian-hamradio-team/bladerf/-/commit/3b2c203682dede808731068ef37755c8514f853e


Fix installation of python bindings. (Closes: #1022398)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1022398

Bug#994892: marked as done (evdi-dkms: fails to build for kernel 5.14.0-1)

[Debian Bug Tracking System]

Your message dated Tue, 01 Nov 2022 16:49:22 +
with message-id 
and subject line Bug#994892: fixed in evdi 1.12.0+dfsg-0.1
has caused the Debian Bug report #994892,
regarding evdi-dkms: fails to build for kernel 5.14.0-1
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.)


-- 
994892: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994892
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: evdi-dkms
Version: 1.9.0+dfsg-1
Severity: important

Dear Maintainer,

I upgraded to linux-image 5.14.0-1-amd64, and evdi-dkms does not build 
anymore. 

sudo dpkg-reconfigure evdi-dkms 

--
Deleting module version: 1.9.0+dfsg
completely from the DKMS tree.
--
Done.
Loading new evdi-1.9.0+dfsg DKMS files...
Building for 5.14.0-1-amd64
Building initial module for 5.14.0-1-amd64
Error! Bad return status for module build on kernel: 5.14.0-1-amd64 (x86_64)
Consult /var/lib/dkms/evdi/1.9.0+dfsg/build/make.log for more information.

I attach the needed make.log file. Don't hesitate to ask for more info. 

Thanks a lot, 
-- 
Rémi

-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.14.0-1-amd64 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_USER, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_BE:fr
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages evdi-dkms depends on:
ii  dkms  2.8.4-4

Versions of packages evdi-dkms recommends:
ii  libevdi0  1.9.0+dfsg-1

evdi-dkms suggests no packages.

-- no debconf information
DKMS make.log for evdi-1.9.0+dfsg for kernel 5.14.0-1-amd64 (x86_64)
mer 22 sep 2021 20:19:06 CEST
make : on entre dans le répertoire « /usr/src/linux-headers-5.14.0-1-amd64 »
  CC [M]  /var/lib/dkms/evdi/1.9.0+dfsg/build/evdi_platform_drv.o
  CC [M]  /var/lib/dkms/evdi/1.9.0+dfsg/build/evdi_platform_dev.o
  CC [M]  /var/lib/dkms/evdi/1.9.0+dfsg/build/evdi_sysfs.o
  CC [M]  /var/lib/dkms/evdi/1.9.0+dfsg/build/evdi_modeset.o
  CC [M]  /var/lib/dkms/evdi/1.9.0+dfsg/build/evdi_connector.o
  CC [M]  /var/lib/dkms/evdi/1.9.0+dfsg/build/evdi_encoder.o
  CC [M]  /var/lib/dkms/evdi/1.9.0+dfsg/build/evdi_drm_drv.o
  CC [M]  /var/lib/dkms/evdi/1.9.0+dfsg/build/evdi_fb.o
  CC [M]  /var/lib/dkms/evdi/1.9.0+dfsg/build/evdi_gem.o
  CC [M]  /var/lib/dkms/evdi/1.9.0+dfsg/build/evdi_painter.o
/var/lib/dkms/evdi/1.9.0+dfsg/build/evdi_drm_drv.c:81:3: error: ‘struct 
drm_driver’ has no member named ‘preclose’; did you mean ‘postclose’?
   81 |  .preclose = evdi_driver_preclose,
  |   ^~~~
  |   postclose
/var/lib/dkms/evdi/1.9.0+dfsg/build/evdi_drm_drv.c:81:14: error: initialization 
of ‘void (*)(struct drm_device *)’ from incompatible pointer type ‘void 
(*)(struct drm_device *, struct drm_file *)’ 
[-Werror=incompatible-pointer-types]
   81 |  .preclose = evdi_driver_preclose,
  |  ^~~~
/var/lib/dkms/evdi/1.9.0+dfsg/build/evdi_drm_drv.c:81:14: note: (near 
initialization for ‘driver.release’)
/var/lib/dkms/evdi/1.9.0+dfsg/build/evdi_drm_drv.c:87:3: error: ‘struct 
drm_driver’ has no member named ‘gem_free_object_unlocked’
   87 |  .gem_free_object_unlocked = evdi_gem_free_object,
  |   ^~~~
/var/lib/dkms/evdi/1.9.0+dfsg/build/evdi_drm_drv.c:87:30: error: initialization 
of ‘void (*)(struct drm_device *)’ from incompatible pointer type ‘void 
(*)(struct drm_gem_object *)’ [-Werror=incompatible-pointer-types]
   87 |  .gem_free_object_unlocked = evdi_gem_free_object,
  |  ^~~~
/var/lib/dkms/evdi/1.9.0+dfsg/build/evdi_drm_drv.c:87:30: note: (near 
initialization for ‘driver.lastclose’)
/var/lib/dkms/evdi/1.9.0+dfsg/build/evdi_drm_drv.c:91:3: error: ‘struct 
drm_driver’ has no member named ‘gem_vm_ops’
   91 |  .gem_vm_ops = _gem_vm_ops,
  |   ^~
/var/lib/dkms/evdi/1.9.0+dfsg/build/evdi_drm_drv.c:91:16: error: initialization 
of ‘void (*)(struct drm_device *)’ from incompatible pointer type ‘const struct 
vm_operations_struct *’ [-Werror=incompatible-pointer-types]
   91 |  .gem_vm_ops = _gem_vm_ops,
  |^
/var/lib/dkms/evdi/1.9.0+dfsg/build/evdi_drm_drv.c:91:16: note: (near 
initialization for ‘driver.unload’)
/var/lib/dkms/evdi/1.9.0+dfsg/build/evdi_modeset.c:163:20: error: 
initialization of ‘void (*)(struct drm_crtc *, struct drm_atomic_state *)’ from 
incompatible 

Bug#1020028: marked as done (cimg: FTBFS: ImfHeader.h:22:10: fatal error: ImathVec.h: No such file or directory)

[Debian Bug Tracking System]

Your message dated Tue, 01 Nov 2022 16:49:13 +
with message-id 
and subject line Bug#1020028: fixed in cimg 3.1.6+dfsg-5
has caused the Debian Bug report #1020028,
regarding cimg: FTBFS: ImfHeader.h:22:10: fatal error: ImathVec.h: No such file 
or directory
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.)


-- 
1020028: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020028
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cimg
Version: 3.0.2+dfsg-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220917 ftbfs-bookworm

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
> g++ -o CImg_demo CImg_demo.cpp -I.. -Wall -Wextra -Wfatal-errors 
> -Werror=unknown-pragmas -Werror=unused-label -Wshadow -Ofast -Dcimg_use_vt100 
> -Dcimg_display=1   -Dcimg_use_xrandr  -Dcimg_use_tiff  -Dcimg_use_heif  
> -Dcimg_use_openexr -I/usr/include/OpenEXR -Dcimg_use_png  -Dcimg_use_jpeg  
> -Dcimg_use_zlib  -Dcimg_use_curl -Dcimg_use_opencv -I/usr/include/opencv4 
> -I/usr/include/opencv -I/usr/include/opencv4 -Dcimg_use_magick 
> -I/usr/include/GraphicsMagick -Dcimg_use_fftw3  -lm -lX11 -lpthread  -lXrandr 
> -ltiff -ltiffxx -lheif -lIlmImf -lHalf -lpng -lz -ljpeg -lz -lcurl 
> -lopencv_stitching -lopencv_alphamat -lopencv_aruco -lopencv_barcode 
> -lopencv_bgsegm -lopencv_bioinspired -lopencv_ccalib -lopencv_dnn_objdetect 
> -lopencv_dnn_superres -lopencv_dpm -lopencv_face -lopencv_freetype 
> -lopencv_fuzzy -lopencv_hdf -lopencv_hfs -lopencv_img_hash 
> -lopencv_intensity_transform -lopencv_line_descriptor -lopencv_mcc 
> -lopencv_quality -lopencv_rapid -lopencv_reg -lopencv_rgbd -lopencv_saliency 
> -lopencv_shape -lopencv_stereo -lopencv_structured_light 
> -lopencv_phase_unwrapping -lopencv_superres -lopencv_optflow 
> -lopencv_surface_matching -lopencv_tracking -lopencv_highgui 
> -lopencv_datasets -lopencv_text -lopencv_plot -lopencv_ml -lopencv_videostab 
> -lopencv_videoio -lopencv_viz -lopencv_wechat_qrcode -lopencv_ximgproc 
> -lopencv_video -lopencv_xobjdetect -lopencv_objdetect -lopencv_calib3d 
> -lopencv_imgcodecs -lopencv_features2d -lopencv_dnn -lopencv_flann 
> -lopencv_xphoto -lopencv_photo -lopencv_imgproc -lopencv_core 
> -lGraphicsMagick++ -lGraphicsMagick -lfftw3 -lfftw3_threads
> In file included from /usr/include/OpenEXR/ImfRgbaFile.h:23,
>  from ../CImg.h:584,
>  from CImg_demo.cpp:48:
> /usr/include/OpenEXR/ImfHeader.h:22:10: fatal error: ImathVec.h: No such file 
> or directory
>22 | #include "ImathVec.h"
>   |  ^~~~
> compilation terminated.
> make[3]: *** [Makefile:315: CImg_demo] Error 1


The full build log is available from:
http://qa-logs.debian.net/2022/09/17/cimg_3.0.2+dfsg-1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220917;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20220917=lu...@debian.org=1=1=1=1#results

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: cimg
Source-Version: 3.1.6+dfsg-5
Done: Nilesh Patra 

We believe that the bug you reported is fixed in the latest version of
cimg, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1020...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Nilesh Patra  (supplier of updated cimg package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 01 Nov 2022 21:55:38 +0530
Source: cimg
Architecture: source
Version: 3.1.6+dfsg-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Science 

Bug#1017058: marked as done (evdi-dkms: failt to compile drm/drm_irq.h is missing - kernel 5.18.0-3-amd64)

[Debian Bug Tracking System]

Your message dated Tue, 01 Nov 2022 16:49:22 +
with message-id 
and subject line Bug#1017058: fixed in evdi 1.12.0+dfsg-0.1
has caused the Debian Bug report #1017058,
regarding evdi-dkms: failt to compile drm/drm_irq.h is missing - kernel 
5.18.0-3-amd64
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.)


-- 
1017058: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017058
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: evdi-dkms
Version: 1.9.0+dfsg-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: t...@drillich.com

Dear Maintainer,
building the kernel-module on amd64 failed, cause there are no more
drm/drm_irq.h in the current kernel-source (and future Kernel, I've checked
19.1).

Is there a fix around?


-- System Information:
Debian Release: bookworm/sid
  APT prefers stable-security
  APT policy: (500, 'stable-security'), (500, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.18.0-3-amd64 (SMP w/32 CPU threads; PREEMPT)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), 
LANGUAGE=de:en_US:fa
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages evdi-dkms depends on:
ii  dkms  3.0.3-4

Versions of packages evdi-dkms recommends:
ii  libevdi0  1.9.0+dfsg-1

evdi-dkms suggests no packages.

-- no debconf information
DKMS make.log for evdi-1.9.0+dfsg for kernel 5.18.0-3-amd64 (x86_64)
Fr 12. Aug 14:38:14 CEST 2022
make: Verzeichnis „/usr/src/linux-headers-5.18.0-3-amd64“ wird betreten
  CC [M]  /var/lib/dkms/evdi/1.9.0+dfsg/build/evdi_platform_drv.o
  CC [M]  /var/lib/dkms/evdi/1.9.0+dfsg/build/evdi_platform_dev.o
  CC [M]  /var/lib/dkms/evdi/1.9.0+dfsg/build/evdi_sysfs.o
  CC [M]  /var/lib/dkms/evdi/1.9.0+dfsg/build/evdi_modeset.o
  CC [M]  /var/lib/dkms/evdi/1.9.0+dfsg/build/evdi_connector.o
  CC [M]  /var/lib/dkms/evdi/1.9.0+dfsg/build/evdi_encoder.o
  CC [M]  /var/lib/dkms/evdi/1.9.0+dfsg/build/evdi_drm_drv.o
  CC [M]  /var/lib/dkms/evdi/1.9.0+dfsg/build/evdi_fb.o
  CC [M]  /var/lib/dkms/evdi/1.9.0+dfsg/build/evdi_gem.o
  CC [M]  /var/lib/dkms/evdi/1.9.0+dfsg/build/evdi_painter.o
  CC [M]  /var/lib/dkms/evdi/1.9.0+dfsg/build/evdi_params.o
  CC [M]  /var/lib/dkms/evdi/1.9.0+dfsg/build/evdi_cursor.o
  CC [M]  /var/lib/dkms/evdi/1.9.0+dfsg/build/evdi_debug.o
  CC [M]  /var/lib/dkms/evdi/1.9.0+dfsg/build/evdi_i2c.o
  CC [M]  /var/lib/dkms/evdi/1.9.0+dfsg/build/evdi_ioc32.o
In file included from /var/lib/dkms/evdi/1.9.0+dfsg/build/evdi_drm_drv.c:23:
/var/lib/dkms/evdi/1.9.0+dfsg/build/evdi_drm_drv.h:23:10: fatal error: 
drm/drm_irq.h: Datei oder Verzeichnis nicht gefunden
   23 | #include 
  |  ^~~
compilation terminated.
make[1]: *** 
[/usr/src/linux-headers-5.18.0-3-common/scripts/Makefile.build:294: 
/var/lib/dkms/evdi/1.9.0+dfsg/build/evdi_drm_drv.o] Fehler 1
make[1]: *** Es wird auf noch nicht beendete Prozesse gewartet
In file included from /var/lib/dkms/evdi/1.9.0+dfsg/build/evdi_gem.c:16:
/var/lib/dkms/evdi/1.9.0+dfsg/build/evdi_drm_drv.h:23:10: fatal error: 
drm/drm_irq.h: Datei oder Verzeichnis nicht gefunden
   23 | #include 
  |  ^~~
compilation terminated.
make[1]: *** 
[/usr/src/linux-headers-5.18.0-3-common/scripts/Makefile.build:294: 
/var/lib/dkms/evdi/1.9.0+dfsg/build/evdi_gem.o] Fehler 1
In file included from /var/lib/dkms/evdi/1.9.0+dfsg/build/evdi_ioc32.c:32:
/var/lib/dkms/evdi/1.9.0+dfsg/build/evdi_drm_drv.h:23:10: fatal error: 
drm/drm_irq.h: Datei oder Verzeichnis nicht gefunden
   23 | #include 
  |  ^~~
compilation terminated.
make[1]: *** 
[/usr/src/linux-headers-5.18.0-3-common/scripts/Makefile.build:294: 
/var/lib/dkms/evdi/1.9.0+dfsg/build/evdi_ioc32.o] Fehler 1
In file included from 
/var/lib/dkms/evdi/1.9.0+dfsg/build/evdi_platform_dev.c:30:
/var/lib/dkms/evdi/1.9.0+dfsg/build/evdi_drm_drv.h:23:10: fatal error: 
drm/drm_irq.h: Datei oder Verzeichnis nicht gefunden
   23 | #include 
  |  ^~~
compilation terminated.
make[1]: *** 
[/usr/src/linux-headers-5.18.0-3-common/scripts/Makefile.build:294: 
/var/lib/dkms/evdi/1.9.0+dfsg/build/evdi_platform_dev.o] Fehler 1
In file included from /var/lib/dkms/evdi/1.9.0+dfsg/build/evdi_painter.c:19:
/var/lib/dkms/evdi/1.9.0+dfsg/build/evdi_drm_drv.h:23:10: fatal error: 
drm/drm_irq.h: Datei oder Verzeichnis nicht gefunden
   23 | #include 
  |  ^~~
compilation terminated.
make[1]: *** 

Bug#1016327: marked as done (apertium-oci-fra: FTBFS: make[2]: *** [Makefile:900: oci-fra.t1x.bin] Error 1)

[Debian Bug Tracking System]

Your message dated Tue, 01 Nov 2022 16:04:34 +
with message-id 
and subject line Bug#1016327: fixed in apertium-oci-fra 1.0.0-1
has caused the Debian Bug report #1016327,
regarding apertium-oci-fra: FTBFS: make[2]: *** [Makefile:900: oci-fra.t1x.bin] 
Error 1
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.)


-- 
1016327: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016327
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: apertium-oci-fra
Version: 0.3.0-4
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220728 ftbfs-bookworm

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
> make[2]: Entering directory '/<>'
> /bin/mkdir -p .deps
> touch .deps/.d
> cp /<>/apertium-oci-0.2.0/oci.prob oci-fra.prob
> cg-comp /<>/apertium-oci-0.2.0/apertium-oci.oci.rlx 
> oci-fra.rlx.bin
> cp /<>/apertium-fra-1.7.0/fra.autogen.bin oci-fra.autogen.bin
> cp /<>/apertium-fra-1.7.0/fra.autopgen.bin oci-fra.autopgen.bin
> apertium-validate-transfer apertium-oci-fra.oci-fra.t1x
> apertium-validate-interchunk apertium-oci-fra.oci-fra.t2ax
> apertium-validate-interchunk apertium-oci-fra.oci-fra.t2bx
> apertium-validate-interchunk apertium-oci-fra.oci-fra.t2cx
> apertium-validate-postchunk apertium-oci-fra.oci-fra.t3x
> apertium-validate-transfer apertium-oci-fra.oci-fra.t4x
> cp /<>/apertium-fra-1.7.0/fra.prob fra-oci.prob
> Sections: 1, Rules: 87, Sets: 110, Tags: 102
> cg-comp /<>/apertium-fra-1.7.0/apertium-fra.fra.rlx 
> fra-oci.rlx.bin
> apertium-metalrx apertium-oci-fra.fra-oci.metalrx 
> .deps/apertium-oci-fra.fra-oci.metalrx
> apertium-preprocess-transfer apertium-oci-fra.oci-fra.t2cx oci-fra.t2cx.bin
> apertium-preprocess-transfer apertium-oci-fra.oci-fra.t2bx oci-fra.t2bx.bin
> apertium-preprocess-transfer apertium-oci-fra.oci-fra.t3x oci-fra.t3x.bin
> apertium-preprocess-transfer apertium-oci-fra.oci-fra.t2ax oci-fra.t2ax.bin
> apertium-preprocess-transfer apertium-oci-fra.oci-fra.t4x oci-fra.t4x.bin
> apertium-metalrx apertium-oci-fra.fra-oci@gascon.metalrx 
> .deps/apertium-oci-fra.fra-oci@gascon.metalrx
> cp /<>/apertium-oci-0.2.0/oci.autogen.bin fra-oci.autogen.bin
> Sections: 1, Rules: 742, Sets: 459, Tags: 246
> apertium-preprocess-transfer apertium-oci-fra.oci-fra.t1x oci-fra.t1x.bin
> cp /<>/apertium-oci-0.2.0/o...@gascon.autogen.bin 
> fra-...@gascon.autogen.bin
> cp /<>/apertium-oci-0.2.0/oci.autopgen.bin fra-oci.autopgen.bin
> cp /<>/apertium-oci-0.2.0/o...@gascon.autopgen.bin 
> fra-...@gascon.autopgen.bin
> apertium-validate-transfer apertium-oci-fra.fra-oci.t1x
> apertium-validate-interchunk apertium-oci-fra.fra-oci.t2x
> apertium-validate-postchunk apertium-oci-fra.fra-oci.t3x
> apertium-validate-transfer apertium-oci-fra.fra-oci.t4x
> apertium-validate-modes modes.xml
> apertium-preprocess-transfer apertium-oci-fra.fra-oci.t3x fra-oci.t3x.bin
> apertium-preprocess-transfer apertium-oci-fra.fra-oci.t4x fra-oci.t4x.bin
> apertium-gen-modes modes.xml
> apertium-preprocess-transfer apertium-oci-fra.fra-oci.t2x fra-oci.t2x.bin
> Debug mode name oci-fra-interchunk generated multiple times, disregarding 
> result from oci-fra step 9
> Debug mode name oci-fra-interchunk generated multiple times, disregarding 
> result from oci-fra step 10
> Error at line xsltproc --stringparam alt oci alt.xsl 
> apertium-oci-fra.oci-fra.dix >.deps/fra-oci.dix
> Debug mode name oci_gascon-fra-interchunk generated multiple times, 
> disregarding result from oci_gascon-fra step 9
> Debug mode name oci_gascon-fra-interchunk generated multiple times, 
> disregarding result from oci_gascon-fra step 10
> 4327, column 66: Undefined attr-item lemg.
> make[2]: *** [Makefile:900: oci-fra.t1x.bin] Error 1


The full build log is available from:
http://qa-logs.debian.net/2022/07/28/apertium-oci-fra_0.3.0-4_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220728;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20220728=lu...@debian.org=1=1=1=1#results

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in 

Bug#1020845: marked as done (golang-github-newrelic-go-agent-v3-dev: missing Breaks+Replaces: golang-github-newrelic-go-agent-dev (<< 3.15.2-4))

[Debian Bug Tracking System]

Your message dated Tue, 1 Nov 2022 16:54:41 +0100
with message-id <6aeba067-d103-62f9-44cf-b9bd6508c...@debian.org>
and subject line Re: golang-github-newrelic-go-agent-v3-dev: missing 
Breaks+Replaces: golang-github-newrelic-go-agent-dev (<< 3.15.2-4)
has caused the Debian Bug report #1020845,
regarding golang-github-newrelic-go-agent-v3-dev: missing Breaks+Replaces: 
golang-github-newrelic-go-agent-dev (<< 3.15.2-4)
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.)


-- 
1020845: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020845
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: golang-github-newrelic-go-agent-v3-dev
Version: 3.15.2-4
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces

>From the attached log (scroll to the bottom...):

  Preparing to unpack 
.../golang-github-newrelic-go-agent-v3-dev_3.15.2-4_all.deb ...
  Unpacking golang-github-newrelic-go-agent-v3-dev (3.15.2-4) ...
  dpkg: error processing archive 
/var/cache/apt/archives/golang-github-newrelic-go-agent-v3-dev_3.15.2-4_all.deb 
(--unpack):
   trying to overwrite 
'/usr/share/gocode/src/github.com/newrelic/go-agent/v3/integrations/logcontext/logcontext.go',
 which is also in package golang-github-newrelic-go-agent-dev 3.15.2-3
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   
/var/cache/apt/archives/golang-github-newrelic-go-agent-v3-dev_3.15.2-4_all.deb


cheers,

Andreas


golang-github-newrelic-go-agent-dev=3.15.2-3_golang-github-newrelic-go-agent-v3-dev=3.15.2-4.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---

Version: 3.15.2-6

B+R were added in -6--- End Message ---

Bug#1020938: khard: missing Python dependency python3-pkg-resources

[Sebastian Crane]

Dear Adrian,

Thank you very much for digging deeper into this issue! If I understand
you correctly, this bug report can be closed now, since the next Debian
Stable release would rebuild the package anyway. Is this indeed the
case?

Best wishes,

Sebastian

Bug#1022486: marked as done (healpy: FTBFS: distutils.errors.DistutilsSetupError: each element of 'ext_modules' option must be an Extension instance or 2-tuple)

[Debian Bug Tracking System]

Your message dated Tue, 01 Nov 2022 15:05:22 +
with message-id 
and subject line Bug#1022486: fixed in healpy 1.16.1-1
has caused the Debian Bug report #1022486,
regarding healpy: FTBFS: distutils.errors.DistutilsSetupError: each element of 
'ext_modules' option must be an Extension instance or 2-tuple
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.)


-- 
1022486: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022486
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: healpy
Version: 1.15.0-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221023 ftbfs-bookworm

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
>  debian/rules binary
> dh binary --with python3 --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:240: python3.10 setup.py config 
> /usr/lib/python3/dist-packages/_distutils_hack/__init__.py:18: UserWarning: 
> Distutils was imported before Setuptools, but importing Setuptools also 
> replaces the `distutils` module in `sys.modules`. This may lead to 
> undesirable behaviors or errors. To avoid these issues, avoid using distutils 
> directly, ensure that setuptools is installed in the traditional way (e.g. 
> not an editable install), and/or make sure that setuptools is always imported 
> before distutils.
>   warnings.warn(
> /usr/lib/python3/dist-packages/_distutils_hack/__init__.py:33: UserWarning: 
> Setuptools is replacing distutils.
>   warnings.warn("Setuptools is replacing distutils.")
> /usr/lib/python3/dist-packages/setuptools/_distutils/extension.py:134: 
> UserWarning: Unknown Extension options: 'cython_directives'
>   warnings.warn(msg)
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:240: /usr/bin/python3 setup.py build 
> /usr/lib/python3/dist-packages/_distutils_hack/__init__.py:18: UserWarning: 
> Distutils was imported before Setuptools, but importing Setuptools also 
> replaces the `distutils` module in `sys.modules`. This may lead to 
> undesirable behaviors or errors. To avoid these issues, avoid using distutils 
> directly, ensure that setuptools is installed in the traditional way (e.g. 
> not an editable install), and/or make sure that setuptools is always imported 
> before distutils.
>   warnings.warn(
> /usr/lib/python3/dist-packages/_distutils_hack/__init__.py:33: UserWarning: 
> Setuptools is replacing distutils.
>   warnings.warn("Setuptools is replacing distutils.")
> /usr/lib/python3/dist-packages/setuptools/_distutils/extension.py:134: 
> UserWarning: Unknown Extension options: 'cython_directives'
>   warnings.warn(msg)
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.10_healpy/build/healpy
> copying healpy/__init__.py -> 
> /<>/.pybuild/cpython3_3.10_healpy/build/healpy
> copying healpy/pixelfunc.py -> 
> /<>/.pybuild/cpython3_3.10_healpy/build/healpy
> copying healpy/sphtfunc.py -> 
> /<>/.pybuild/cpython3_3.10_healpy/build/healpy
> copying healpy/visufunc.py -> 
> /<>/.pybuild/cpython3_3.10_healpy/build/healpy
> copying healpy/fitsfunc.py -> 
> /<>/.pybuild/cpython3_3.10_healpy/build/healpy
> copying healpy/projector.py -> 
> /<>/.pybuild/cpython3_3.10_healpy/build/healpy
> copying healpy/rotator.py -> 
> /<>/.pybuild/cpython3_3.10_healpy/build/healpy
> copying healpy/projaxes.py -> 
> /<>/.pybuild/cpython3_3.10_healpy/build/healpy
> copying healpy/version.py -> 
> /<>/.pybuild/cpython3_3.10_healpy/build/healpy
> copying healpy/cookbook.py -> 
> /<>/.pybuild/cpython3_3.10_healpy/build/healpy
> copying healpy/newvisufunc.py -> 
> /<>/.pybuild/cpython3_3.10_healpy/build/healpy
> copying healpy/zoomtool.py -> 
> /<>/.pybuild/cpython3_3.10_healpy/build/healpy
> creating /<>/.pybuild/cpython3_3.10_healpy/build/healpy/test
> copying healpy/test/__init__.py -> 
> /<>/.pybuild/cpython3_3.10_healpy/build/healpy/test
> copying healpy/test/test_spinfunc.py -> 
> /<>/.pybuild/cpython3_3.10_healpy/build/healpy/test
> copying healpy/test/test_visufunc.py -> 
> /<>/.pybuild/cpython3_3.10_healpy/build/healpy/test
> copying healpy/test/test_rotator.py -> 
> /<>/.pybuild/cpython3_3.10_healpy/build/healpy/test
> copying healpy/test/test_fitsfunc.py -> 
> /<>/.pybuild/cpython3_3.10_healpy/build/healpy/test
> copying healpy/test/test_pixelweights.py -> 
> /<>/.pybuild/cpython3_3.10_healpy/build/healpy/test
> copying healpy/test/test_pixelfunc.py -> 
> 

Bug#1013259: samba-libs: Possible policy violation (now with libndr.so.2 => libndr.so.3)

[Michael Tokarev]

Hmm. Other sssd packages are also affected by this.
Not only sssd-ad but sssd-ipa and sssd-ad-common.

Added the Breaks for these in Bullseye (and also in Ubuntu Jammy, which
has exactly the same problem).  Will be in the next upload.

/mjt

Bug#1022488: marked as done (azure-cosmos-python: FTBFS: TypeError: dist must be a Distribution instance)

[Debian Bug Tracking System]

Your message dated Tue, 01 Nov 2022 15:04:09 +
with message-id 
and subject line Bug#1022488: fixed in azure-cosmos-python 3.1.1-5
has caused the Debian Bug report #1022488,
regarding azure-cosmos-python: FTBFS: TypeError: dist must be a Distribution 
instance
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.)


-- 
1022488: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022488
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: azure-cosmos-python
Version: 3.1.1-4
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221023 ftbfs-bookworm

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
>  debian/rules clean
> dh clean --with python3 --buildsystem=pybuild
>dh_auto_clean -O--buildsystem=pybuild
> I: pybuild base:240: python3.10 setup.py clean 
> /<>/setup.py:3: DeprecationWarning: The distutils package is 
> deprecated and slated for removal in Python 3.12. Use setuptools or check PEP 
> 632 for potential alternatives
>   from distutils.core import setup
> /usr/lib/python3/dist-packages/_distutils_hack/__init__.py:18: UserWarning: 
> Distutils was imported before Setuptools, but importing Setuptools also 
> replaces the `distutils` module in `sys.modules`. This may lead to 
> undesirable behaviors or errors. To avoid these issues, avoid using distutils 
> directly, ensure that setuptools is installed in the traditional way (e.g. 
> not an editable install), and/or make sure that setuptools is always imported 
> before distutils.
>   warnings.warn(
> /usr/lib/python3/dist-packages/_distutils_hack/__init__.py:33: UserWarning: 
> Setuptools is replacing distutils.
>   warnings.warn("Setuptools is replacing distutils.")
> /usr/lib/python3.10/distutils/dist.py:274: UserWarning: Unknown distribution 
> option: 'install_requires'
>   warnings.warn(msg)
> running clean
> Traceback (most recent call last):
>   File "/<>/setup.py", line 6, in 
> setup(name='azure-cosmos',
>   File "/usr/lib/python3.10/distutils/core.py", line 148, in setup
> dist.run_commands()
>   File "/usr/lib/python3.10/distutils/dist.py", line 966, in run_commands
> self.run_command(cmd)
>   File "/usr/lib/python3.10/distutils/dist.py", line 983, in run_command
> cmd_obj = self.get_command_obj(command)
>   File "/usr/lib/python3.10/distutils/dist.py", line 858, in get_command_obj
> cmd_obj = self.command_obj[command] = klass(self)
>   File "/usr/lib/python3/dist-packages/setuptools/__init__.py", line 158, in 
> __init__
> super().__init__(dist)
>   File "/usr/lib/python3/dist-packages/setuptools/_distutils/cmd.py", line 
> 59, in __init__
> raise TypeError("dist must be a Distribution instance")
> TypeError: dist must be a Distribution instance
> E: pybuild pybuild:379: clean: plugin distutils failed with: exit code=1: 
> python3.10 setup.py clean 
> dh_auto_clean: error: pybuild --clean -i python{version} -p 3.10 returned 
> exit code 13
> make: *** [debian/rules:6: clean] Error 25


The full build log is available from:
http://qa-logs.debian.net/2022/10/23/azure-cosmos-python_3.1.1-4_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20221023;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20221023=lu...@debian.org=1=1=1=1#results

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: azure-cosmos-python
Source-Version: 3.1.1-5
Done: Thomas Goirand 

We believe that the bug you reported is fixed in the latest version of
azure-cosmos-python, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1022...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Thomas Goirand  (supplier of updated azure-cosmos-python 
package)

(This message was generated 

Bug#1022390: marked as done (python-enmerkar: FTBFS: tests failed)

[Debian Bug Tracking System]

Your message dated Tue, 01 Nov 2022 14:44:48 +
with message-id 
and subject line Bug#1022390: fixed in python-enmerkar 0.7.1-5
has caused the Debian Bug report #1022390,
regarding python-enmerkar: FTBFS: tests failed
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.)


-- 
1022390: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022390
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-enmerkar
Version: 0.7.1-4
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221023 ftbfs-bookworm

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> make[1]: pyversions: No such file or directory
> py3versions: no X-Python3-Version in control file, using supported versions
> pkgos-dh_auto_install --no-py2 --in-tmp
> + PKGOS_IN_TMP=no
> + echo WARNING: --no-py2 is deprecated and always on.
> WARNING: --no-py2 is deprecated and always on.
> + shift
> + PKGOS_IN_TMP=yes
> + shift
> + dpkg-parsechangelog -SSource
> + SRC_PKG_NAME=python-enmerkar
> + echo python-enmerkar
> + sed s/python-//
> + PY_MODULE_NAME=enmerkar
> + py3versions -vr
> + PYTHON3S=3.10
> + [ yes = yes ]
> + TARGET_DIR=tmp
> + pwd
> + python3.10 setup.py install --install-layout=deb --root 
> /<>/debian/tmp
> running install
> /usr/lib/python3/dist-packages/setuptools/command/install.py:34: 
> SetuptoolsDeprecationWarning: setup.py install is deprecated. Use build and 
> pip and other standards-based tools.
>   warnings.warn(
> running build
> running build_py
> creating build
> creating build/lib
> creating build/lib/enmerkar
> copying enmerkar/__init__.py -> build/lib/enmerkar
> copying enmerkar/middleware.py -> build/lib/enmerkar
> copying enmerkar/extract.py -> build/lib/enmerkar
> creating build/lib/enmerkar/management
> copying enmerkar/management/__init__.py -> build/lib/enmerkar/management
> creating build/lib/enmerkar/templatetags
> copying enmerkar/templatetags/__init__.py -> build/lib/enmerkar/templatetags
> copying enmerkar/templatetags/babel.py -> build/lib/enmerkar/templatetags
> creating build/lib/enmerkar/management/commands
> copying enmerkar/management/commands/__init__.py -> 
> build/lib/enmerkar/management/commands
> copying enmerkar/management/commands/babel.py -> 
> build/lib/enmerkar/management/commands
> running install_lib
> creating /<>/debian/tmp
> creating /<>/debian/tmp/usr
> creating /<>/debian/tmp/usr/lib
> creating /<>/debian/tmp/usr/lib/python3
> creating /<>/debian/tmp/usr/lib/python3/dist-packages
> creating /<>/debian/tmp/usr/lib/python3/dist-packages/enmerkar
> copying build/lib/enmerkar/__init__.py -> 
> /<>/debian/tmp/usr/lib/python3/dist-packages/enmerkar
> copying build/lib/enmerkar/middleware.py -> 
> /<>/debian/tmp/usr/lib/python3/dist-packages/enmerkar
> copying build/lib/enmerkar/extract.py -> 
> /<>/debian/tmp/usr/lib/python3/dist-packages/enmerkar
> creating 
> /<>/debian/tmp/usr/lib/python3/dist-packages/enmerkar/management
> creating 
> /<>/debian/tmp/usr/lib/python3/dist-packages/enmerkar/management/commands
> copying build/lib/enmerkar/management/commands/__init__.py -> 
> /<>/debian/tmp/usr/lib/python3/dist-packages/enmerkar/management/commands
> copying build/lib/enmerkar/management/commands/babel.py -> 
> /<>/debian/tmp/usr/lib/python3/dist-packages/enmerkar/management/commands
> copying build/lib/enmerkar/management/__init__.py -> 
> /<>/debian/tmp/usr/lib/python3/dist-packages/enmerkar/management
> creating 
> /<>/debian/tmp/usr/lib/python3/dist-packages/enmerkar/templatetags
> copying build/lib/enmerkar/templatetags/__init__.py -> 
> /<>/debian/tmp/usr/lib/python3/dist-packages/enmerkar/templatetags
> copying build/lib/enmerkar/templatetags/babel.py -> 
> /<>/debian/tmp/usr/lib/python3/dist-packages/enmerkar/templatetags
> byte-compiling 
> /<>/debian/tmp/usr/lib/python3/dist-packages/enmerkar/__init__.py
>  to __init__.cpython-310.pyc
> byte-compiling 
> /<>/debian/tmp/usr/lib/python3/dist-packages/enmerkar/middleware.py
>  to middleware.cpython-310.pyc
> byte-compiling 
> /<>/debian/tmp/usr/lib/python3/dist-packages/enmerkar/extract.py 
> to extract.cpython-310.pyc
> byte-compiling 
> /<>/debian/tmp/usr/lib/python3/dist-packages/enmerkar/management/commands/__init__.py
>  to __init__.cpython-310.pyc
> byte-compiling 
> /<>/debian/tmp/usr/lib/python3/dist-packages/enmerkar/management/commands/babel.py
>  to babel.cpython-310.pyc
> byte-compiling 
> 

Bug#1022291: marked as done (hydrapaper: FTBFS: ModuleNotFoundError: No module named 'gi')

[Debian Bug Tracking System]

Your message dated Tue, 01 Nov 2022 14:39:04 +
with message-id 
and subject line Bug#1022291: fixed in blueprint-compiler 0.4.0-4
has caused the Debian Bug report #1022291,
regarding hydrapaper: FTBFS: ModuleNotFoundError: No module named 'gi'
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.)


-- 
1022291: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022291
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: hydrapaper
Version: 3.3.1-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221023 ftbfs-bookworm

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
>  debian/rules binary
> dh binary --with python3
>dh_update_autotools_config
>dh_autoreconf
>dh_auto_configure
>   cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 meson .. 
> --wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc 
> --localstatedir=/var --libdir=lib/x86_64-linux-gnu
> The Meson build system
> Version: 0.63.3
> Source dir: /<>
> Build dir: /<>/obj-x86_64-linux-gnu
> Build type: native build
> Project name: hydrapaper
> Project version: 3.3.1
> Host machine cpu family: x86_64
> Host machine cpu: x86_64
> Message: Looking for dependencies
> Found pkg-config: /usr/bin/pkg-config (0.29.2)
> Run-time dependency glib-2.0 found: YES 2.74.0
> Run-time dependency gobject-introspection-1.0 found: YES 1.74.0
> Run-time dependency gtk4 found: YES 4.8.1
> Run-time dependency libadwaita-1 found: YES 1.2.0
> Program python3 found: YES (/usr/bin/python3)
> Run-time dependency dbus-1 found: YES 1.14.4
> Message: Daemon Enabled: True
> Configuring hydrapaperd using configuration
> Configuring org.gabmus.hydrapaper.desktop.i18n.in using configuration
> Program msgfmt found: YES (/usr/bin/msgfmt)
> Configuring org.gabmus.hydrapaper.service using configuration
> Configuring org.gabmus.hydrapaper.Daemon.service using configuration
> Configuring org.gabmus.hydrapaperd.service using configuration
> Configuring org.gabmus.hydrapaper.Daemon.desktop.i18n.in using configuration
> Configuring org.gabmus.hydrapaper.gschema.xml using configuration
> Program blueprint-compiler found: YES (/usr/bin/blueprint-compiler)
> Configuring aboutdialog.ui using configuration
> Found pkg-config: /usr/bin/pkg-config (0.29.2)
> Program glib-compile-resources found: YES (/usr/bin/glib-compile-resources)
> Program glib-compile-schemas found: YES (/usr/bin/glib-compile-schemas)
> Program appstreamcli found: NO
> Configuring hydrapaper using configuration
> Message: Update translations
> Program msginit found: YES (/usr/bin/msginit)
> Program msgmerge found: YES (/usr/bin/msgmerge)
> Program xgettext found: YES (/usr/bin/xgettext)
> Program pandoc found: YES (/usr/bin/pandoc)
> Message: Compiling man page from markdown to groff
> WARNING: You should add the boolean check kwarg to the run_command call.
>  It currently defaults to false,
>  but it will default to true in future releases of meson.
>  See also: https://github.com/mesonbuild/meson/issues/9300
> Message: Man page compilation succeeded, installing
> Build targets in project: 16
> 
> hydrapaper 3.3.1
> 
>   User defined options
> buildtype: plain
> libdir   : lib/x86_64-linux-gnu
> localstatedir: /var
> prefix   : /usr
> sysconfdir   : /etc
> wrap_mode: nodownload
> 
> Found ninja-1.11.1 at /usr/bin/ninja
>dh_auto_build
>   cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 ninja -j8 -v
> [1/12] /usr/bin/glib-compile-schemas --targetdir data ../data
> No schema files found: doing nothing.
> [2/12] /usr/bin/msgfmt ../po/es.po -o po/es/LC_MESSAGES/hydrapaper.mo
> [3/12] /usr/bin/msgfmt ../po/de.po -o po/de/LC_MESSAGES/hydrapaper.mo
> [4/12] /usr/bin/msgfmt ../po/it.po -o po/it/LC_MESSAGES/hydrapaper.mo
> [5/12] /usr/bin/msgfmt ../po/pt_BR.po -o po/pt_BR/LC_MESSAGES/hydrapaper.mo
> [6/12] /usr/bin/msgfmt ../po/sv.po -o po/sv/LC_MESSAGES/hydrapaper.mo
> [7/12] /usr/bin/msgfmt ../po/ru.po -o po/ru/LC_MESSAGES/hydrapaper.mo
> [8/12] /usr/bin/blueprint-compiler batch-compile data/. ../data 
> ../data/ui/headerbar.blp ../data/ui/monitors_flowbox_item.blp 
> ../data/ui/shortcutsWindow.blp ../data/ui/wallpaper_flowbox_item_popover.blp 
> ../data/ui/wallpapers_flowbox.blp ../data/ui/wp_mode_popover_menu.blp 
> ../data/ui/wallpapers_folders_view.blp ../data/ui/wallpaper_flowbox_item.blp
> FAILED: data 
> /usr/bin/blueprint-compiler batch-compile data/. ../data 
> ../data/ui/headerbar.blp 

Bug#1022286: marked as done (gnome-shell-extension-manager: FTBFS: ModuleNotFoundError: No module named 'gi')

[Debian Bug Tracking System]

Your message dated Tue, 01 Nov 2022 14:39:04 +
with message-id 
and subject line Bug#1022286: fixed in blueprint-compiler 0.4.0-4
has caused the Debian Bug report #1022286,
regarding gnome-shell-extension-manager: FTBFS: ModuleNotFoundError: No module 
named 'gi'
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.)


-- 
1022286: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022286
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gnome-shell-extension-manager
Version: 0.2.3-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221023 ftbfs-bookworm

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
>  debian/rules binary
> dh binary
>dh_update_autotools_config
>dh_autoreconf
>dh_auto_configure
>   cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 meson .. 
> --wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc 
> --localstatedir=/var --libdir=lib/x86_64-linux-gnu
> The Meson build system
> Version: 0.63.3
> Source dir: /<>
> Build dir: /<>/obj-x86_64-linux-gnu
> Build type: native build
> Project name: extension-manager
> Project version: 0.2.3
> C compiler for the host machine: cc (gcc 12.2.0 "cc (Debian 12.2.0-7) 12.2.0")
> C linker for the host machine: cc ld.bfd 2.39
> Host machine cpu family: x86_64
> Host machine cpu: x86_64
> Configuring exm-config.h using configuration
> Program msgfmt found: YES (/usr/bin/msgfmt)
> Program desktop-file-validate found: NO
> Program appstream-util found: YES (/usr/bin/appstream-util)
> Program glib-compile-schemas found: YES (/usr/bin/glib-compile-schemas)
> Found pkg-config: /usr/bin/pkg-config (0.29.2)
> Run-time dependency gtk4 found: YES 4.8.1
> Run-time dependency libadwaita-1 found: YES 1.2.0
> Run-time dependency json-glib-1.0 found: YES 1.6.6
> Run-time dependency libsoup-3.0 found: YES 3.2.1
> Program blueprint-compiler found: YES (/usr/bin/blueprint-compiler)
> Found pkg-config: /usr/bin/pkg-config (0.29.2)
> Program glib-compile-resources found: YES (/usr/bin/glib-compile-resources)
> Program msginit found: YES (/usr/bin/msginit)
> Program msgmerge found: YES (/usr/bin/msgmerge)
> Program xgettext found: YES (/usr/bin/xgettext)
> Build targets in project: 23
> NOTICE: Future-deprecated features used:
>  * 0.56.0: {'meson.build_root'}
> 
> extension-manager 0.2.3
> 
>   User defined options
> buildtype: plain
> libdir   : lib/x86_64-linux-gnu
> localstatedir: /var
> prefix   : /usr
> sysconfdir   : /etc
> wrap_mode: nodownload
> 
> Found ninja-1.11.1 at /usr/bin/ninja
>dh_auto_build
>   cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 ninja -j8 -v
> [1/40] /usr/bin/msgfmt ../po/cs.po -o po/cs/LC_MESSAGES/extension-manager.mo
> [2/40] /usr/bin/msgfmt ../po/ca.po -o po/ca/LC_MESSAGES/extension-manager.mo
> [3/40] /usr/bin/msgfmt ../po/de.po -o po/de/LC_MESSAGES/extension-manager.mo
> [4/40] /usr/bin/msgfmt ../po/es.po -o po/es/LC_MESSAGES/extension-manager.mo
> [5/40] /usr/bin/msgfmt ../po/fr.po -o po/fr/LC_MESSAGES/extension-manager.mo
> [6/40] /usr/bin/msgfmt ../po/hu.po -o po/hu/LC_MESSAGES/extension-manager.mo
> [7/40] /usr/bin/msgfmt ../po/ja.po -o po/ja/LC_MESSAGES/extension-manager.mo
> [8/40] /usr/bin/msgfmt ../po/it.po -o po/it/LC_MESSAGES/extension-manager.mo
> [9/40] /usr/bin/msgfmt ../po/nb.po -o po/nb/LC_MESSAGES/extension-manager.mo
> [10/40] /usr/bin/msgfmt ../po/nl.po -o po/nl/LC_MESSAGES/extension-manager.mo
> [11/40] /usr/bin/msgfmt ../po/pl.po -o po/pl/LC_MESSAGES/extension-manager.mo
> [12/40] /usr/bin/msgfmt ../po/tr.po -o po/tr/LC_MESSAGES/extension-manager.mo
> [13/40] /usr/bin/msgfmt ../po/pt_BR.po -o 
> po/pt_BR/LC_MESSAGES/extension-manager.mo
> [14/40] /usr/bin/msgfmt ../po/ru_RU.po -o 
> po/ru_RU/LC_MESSAGES/extension-manager.mo
> [15/40] /usr/bin/blueprint-compiler batch-compile src/. ../src 
> ../src/gtk/help-overlay.blp ../src/exm-window.blp 
> ../src/exm-installed-page.blp ../src/exm-browse-page.blp 
> ../src/exm-extension-row.blp ../src/exm-search-row.blp 
> ../src/exm-detail-view.blp ../src/exm-screenshot.blp
> FAILED: src 
> /usr/bin/blueprint-compiler batch-compile src/. ../src 
> ../src/gtk/help-overlay.blp ../src/exm-window.blp 
> ../src/exm-installed-page.blp ../src/exm-browse-page.blp 
> ../src/exm-extension-row.blp ../src/exm-search-row.blp 
> ../src/exm-detail-view.blp ../src/exm-screenshot.blp
> Traceback (most recent call last):
>   File "/usr/bin/blueprint-compiler", line 37, in 
> from 

Processed: Bug#1022488 marked as pending in azure-cosmos-python

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1022488 [src:azure-cosmos-python] azure-cosmos-python: FTBFS: TypeError: 
dist must be a Distribution instance
Added tag(s) pending.

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

Bug#1022488: marked as pending in azure-cosmos-python

[Thomas Goirand]

Control: tag -1 pending

Hello,

Bug #1022488 in azure-cosmos-python reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/python-team/packages/azure-cosmos-python/-/commit/1a0239ca90bfae708477c0348fe9091c41f90660


Add fix-wrong-char-in-setup.py.patch (Closes: #1022488).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1022488

Processed: bug 1022290 is forwarded to https://github.com/dimitri/pgcopydb/pull/137

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forwarded 1022290 https://github.com/dimitri/pgcopydb/pull/137
Bug #1022290 [src:pgcopydb] pgcopydb: FTBFS: ld: cannot find -lzstd: No such 
file or directory
Set Bug forwarded-to-address to 'https://github.com/dimitri/pgcopydb/pull/137'.
> thanks
Stopping processing here.

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

Bug#1023156: haskell-gi-gtk FTBFS on armel

[Scott Talbert]

On Sun, 30 Oct 2022, Adrian Bunk wrote:


haskell-gi-gtk has only once ever been built successfully on armel.
Unless someone has a better suggestion, my short-term Plan B would be
that I request the removal of haskell-gi-gtk and reverse dependencies
on armel.


I think that's probably a good plan.  I believe I may have reported this 
bug (or one similar to it) to ghc, but it didn't sound like it was 
something that was going to fixed quickly/easily.


Scott

Bug#1022280: marked as done (rust-rustyline: FTBFS: build-dependency not installable: librust-fd-lock-3+default-dev)

[Debian Bug Tracking System]

Your message dated Tue, 1 Nov 2022 13:53:20 +
with message-id 
and subject line re: rust-rustyline: FTBFS: build-dependency not installable: 
librust-fd-lock-3+default-dev
has caused the Debian Bug report #1022280,
regarding rust-rustyline: FTBFS: build-dependency not installable: 
librust-fd-lock-3+default-dev
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.)


-- 
1022280: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022280
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rust-rustyline
Version: 9.1.2-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221023 ftbfs-bookworm

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper (>= 12), dh-cargo (>= 25), cargo, rustc, 
> libstd-rust-dev, librust-bitflags-1+default-dev (>= 1.3-~~), 
> librust-cfg-if-1+default-dev, librust-dirs-next-2+default-dev, 
> librust-fd-lock-3+default-dev, librust-libc-0.2+default-dev, 
> librust-log-0.4+default-dev, librust-memchr-2+default-dev, 
> librust-nix-0+default-dev (>= 0.23-~~), librust-radix-trie-0.2+default-dev, 
> librust-scopeguard-1+default-dev (>= 1.1-~~), librust-smallvec-1+default-dev 
> (>= 1.6.1-~~), librust-unicode-segmentation-1+default-dev, 
> librust-unicode-width-0.1+default-dev, librust-utf8parse-0.2+default-dev, 
> librust-winapi-0.3+consoleapi-dev, librust-winapi-0.3+default-dev, 
> librust-winapi-0.3+handleapi-dev, librust-winapi-0.3+minwindef-dev, 
> librust-winapi-0.3+processenv-dev, librust-winapi-0.3+std-dev, 
> librust-winapi-0.3+winbase-dev, librust-winapi-0.3+wincon-dev, 
> librust-winapi-0.3+winuser-dev, build-essential, fakeroot
> Filtered Build-Depends: debhelper (>= 12), dh-cargo (>= 25), cargo, rustc, 
> libstd-rust-dev, librust-bitflags-1+default-dev (>= 1.3-~~), 
> librust-cfg-if-1+default-dev, librust-dirs-next-2+default-dev, 
> librust-fd-lock-3+default-dev, librust-libc-0.2+default-dev, 
> librust-log-0.4+default-dev, librust-memchr-2+default-dev, 
> librust-nix-0+default-dev (>= 0.23-~~), librust-radix-trie-0.2+default-dev, 
> librust-scopeguard-1+default-dev (>= 1.1-~~), librust-smallvec-1+default-dev 
> (>= 1.6.1-~~), librust-unicode-segmentation-1+default-dev, 
> librust-unicode-width-0.1+default-dev, librust-utf8parse-0.2+default-dev, 
> librust-winapi-0.3+consoleapi-dev, librust-winapi-0.3+default-dev, 
> librust-winapi-0.3+handleapi-dev, librust-winapi-0.3+minwindef-dev, 
> librust-winapi-0.3+processenv-dev, librust-winapi-0.3+std-dev, 
> librust-winapi-0.3+winbase-dev, librust-winapi-0.3+wincon-dev, 
> librust-winapi-0.3+winuser-dev, 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 [963 B]
> Ign:3 copy:/<>/apt_archive ./ Release.gpg
> Get:4 copy:/<>/apt_archive ./ Sources [618 B]
> Get:5 copy:/<>/apt_archive ./ Packages [688 B]
> Fetched 2269 B in 0s (200 kB/s)
> Reading package lists...
> Reading package lists...
> 
> Install main build dependencies (apt-based resolver)
> 
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  sbuild-build-depends-main-dummy : Depends: librust-fd-lock-3+default-dev but 
> it is not installable
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.


The full build log is available from:
http://qa-logs.debian.net/2022/10/23/rust-rustyline_9.1.2-1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20221023;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20221023=lu...@debian.org=1=1=1=1#results

A list of current 

Bug#1023265: marked as done (Test failures blocking migration of rust-libc and several deps to testing)

[Debian Bug Tracking System]

Your message dated Tue, 1 Nov 2022 13:40:54 +
with message-id 
and subject line Re: Bug#1023265: Test failures blocking migration of rust-libc 
and several deps to testing
has caused the Debian Bug report #1023265,
regarding Test failures blocking migration of rust-libc and several deps to 
testing
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.)


-- 
1023265: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023265
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: rust-libc
Version: 0.2.137-1
Severity: serious
X-Debbugs-CC: plugw...@debian.org, wolfg...@silbermayr.at, infini...@debian.org

Migration of several other packages is blocked due to the issues listed
over at:

https://tracker.debian.org/pkg/rust-libc

In particular, it has caused failures in rust-capston on s390x and
rust-netlink-sys in multiple platforms.

Thanks,

John
--- End Message ---
--- Begin Message ---

On 01/11/2022 12:11, John Goerzen wrote:

Package: rust-libc
Version: 0.2.137-1
Severity: serious
X-Debbugs-CC: plugw...@debian.org, wolfg...@silbermayr.at, infini...@debian.org

Migration of several other packages is blocked due to the issues listed
over at:

https://tracker.debian.org/pkg/rust-libc

In particular, it has caused failures in rust-capston on s390x and
rust-netlink-sys in multiple platforms.


These failures are not caused by the new version of rust-libc, but are
artifiacts of the way Debian's CI infrastructure satisfies dependencies
for autopktests.

Specifically, when performing unstable->testing migration tests, but not
when performing plain testing tests, Debians autopkgtest infrastructure
uses a fallback dependency solver. This means if the test dependencies
can't be satisfied using the generated pins, it will instead try using
packages only for unstable.

The result of this is that the tests in question are skipped in plain
testing tests, but run in unstable->testing migration tests. This leads
to psudedo-regressions.

I have made uploads for netlink-sys and capstone which make the
autopkgtests pass, where I have felt reasonablly able to I have fixed
the underlying issues, but in some cases I have reported the issues
upstream and skipped the tests (since they do not represent real
regressions compared to the current state in testing.

Once the netlink-sys and capstone uploads reach testing and the migration
tests are re-run then libc should migrate to testing.--- End Message ---

Bug#1022425: marked as done (picard: FTBFS: distutils.errors.DistutilsClassError: command class must subclass Command)

[Debian Bug Tracking System]

Your message dated Tue, 01 Nov 2022 13:34:36 +
with message-id 
and subject line Bug#1022425: fixed in picard 2.8.3-2
has caused the Debian Bug report #1022425,
regarding picard: FTBFS: distutils.errors.DistutilsClassError: command class 
 must subclass Command
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.)


-- 
1022425: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022425
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: picard
Version: 2.8.3-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221023 ftbfs-bookworm

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
>  debian/rules binary
> dh binary --with python3 --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:240: python3.10 setup.py config 
> /<>/setup.py:42: DeprecationWarning: The distutils package is 
> deprecated and slated for removal in Python 3.12. Use setuptools or check PEP 
> 632 for potential alternatives
>   from distutils import log
> /usr/lib/python3/dist-packages/_distutils_hack/__init__.py:18: UserWarning: 
> Distutils was imported before Setuptools, but importing Setuptools also 
> replaces the `distutils` module in `sys.modules`. This may lead to 
> undesirable behaviors or errors. To avoid these issues, avoid using distutils 
> directly, ensure that setuptools is installed in the traditional way (e.g. 
> not an editable install), and/or make sure that setuptools is always imported 
> before distutils.
>   warnings.warn(
> /usr/lib/python3/dist-packages/_distutils_hack/__init__.py:33: UserWarning: 
> Setuptools is replacing distutils.
>   warnings.warn("Setuptools is replacing distutils.")
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:240: /usr/bin/python3 setup.py build --disable-autoupdate
> /<>/setup.py:42: DeprecationWarning: The distutils package is 
> deprecated and slated for removal in Python 3.12. Use setuptools or check PEP 
> 632 for potential alternatives
>   from distutils import log
> /usr/lib/python3/dist-packages/_distutils_hack/__init__.py:18: UserWarning: 
> Distutils was imported before Setuptools, but importing Setuptools also 
> replaces the `distutils` module in `sys.modules`. This may lead to 
> undesirable behaviors or errors. To avoid these issues, avoid using distutils 
> directly, ensure that setuptools is installed in the traditional way (e.g. 
> not an editable install), and/or make sure that setuptools is always imported 
> before distutils.
>   warnings.warn(
> /usr/lib/python3/dist-packages/_distutils_hack/__init__.py:33: UserWarning: 
> Setuptools is replacing distutils.
>   warnings.warn("Setuptools is replacing distutils.")
> Traceback (most recent call last):
>   File "/<>/setup.py", line 845, in 
> setup(**args)
>   File "/usr/lib/python3/dist-packages/setuptools/__init__.py", line 87, in 
> setup
> return distutils.core.setup(**attrs)
>   File "/usr/lib/python3/dist-packages/setuptools/_distutils/core.py", line 
> 172, in setup
> ok = dist.parse_command_line()
>   File "/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py", line 
> 474, in parse_command_line
> args = self._parse_command_opts(parser, args)
>   File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 1107, in 
> _parse_command_opts
> nargs = _Distribution._parse_command_opts(self, parser, args)
>   File "/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py", line 
> 540, in _parse_command_opts
> raise DistutilsClassError(
> distutils.errors.DistutilsClassError: command class  '__main__.picard_build'> must subclass Command
> E: pybuild pybuild:379: build: plugin distutils failed with: exit code=1: 
> /usr/bin/python3 setup.py build --disable-autoupdate
> dh_auto_build: error: pybuild --build -i python{version} -p 3.10 returned 
> exit code 13
> make: *** [debian/rules:13: binary] Error 25


The full build log is available from:
http://qa-logs.debian.net/2022/10/23/picard_2.8.3-1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20221023;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20221023=lu...@debian.org=1=1=1=1#results

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to 

Bug#1016338: marked as done (apertium-fra-frp: FTBFS: make[2]: *** [Makefile:885: fra-frp.t1x.bin] Error 1)

[Debian Bug Tracking System]

Your message dated Tue, 01 Nov 2022 13:34:05 +
with message-id 
and subject line Bug#1016338: fixed in apertium-fra-frp 1.1.0-1
has caused the Debian Bug report #1016338,
regarding apertium-fra-frp: FTBFS: make[2]: *** [Makefile:885: fra-frp.t1x.bin] 
Error 1
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.)


-- 
1016338: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016338
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: apertium-fra-frp
Version: 1.0.0-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220728 ftbfs-bookworm

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
> make[2]: Entering directory '/<>'
> /bin/mkdir -p .deps
> apertium-validate-dictionary apertium-fra-frp.fra-frp.dix
> cp /<>/apertium-fra-1.10.0/fra.prob fra-frp.prob
> cg-comp /<>/apertium-fra-1.10.0/apertium-fra.fra.rlx 
> fra-frp.rlx.bin
> lsx-comp lr apertium-fra-frp.fra-frp.l1x fra-frp.autosep1.bin
> lsx-comp lr apertium-fra-frp.fra-frp.l2x fra-frp.autosep2.bin
> cp /<>/apertium-frp-1.0.0/frp.autogen.bin fra-frp.autogen.bin
> cp /<>/apertium-frp-1.0.0/frp.autopgen.bin fra-frp.autopgen.bin
> touch .deps/.d
> apertium-validate-transfer apertium-fra-frp.fra-frp.t1x
> apertium-validate-interchunk apertium-fra-frp.fra-frp.t2x
> apertium-validate-postchunk apertium-fra-frp.fra-frp.t3x
> cp /<>/apertium-frp-1.0.0/frp.automorf.bin .deps/frp.automorf.bin
> apertium-validate-dictionary apertium-fra-frp.fra-frp.dix
> apertium-preprocess-transfer apertium-fra-frp.fra-frp.t3x fra-frp.t3x.bin
> apertium-preprocess-transfer apertium-fra-frp.fra-frp.t2x fra-frp.t2x.bin
> cp /<>/apertium-frp-1.0.0/frp.prob frp-fra.prob
> main@standard 1187 1566
> apertium-preprocess-transfer apertium-fra-frp.fra-frp.t1x fra-frp.t1x.bin
> cg-comp /<>/apertium-frp-1.0.0/apertium-frp.frp.rlx 
> frp-fra.rlx.bin
> apertium-metalrx apertium-fra-frp.frp-fra.metalrx 
> .deps/apertium-fra-frp.frp-fra.lrx
> Sections: 1, Rules: 1329, Sets: 843, Tags: 581
> main@standard 2153 2626
> lsx-comp lr apertium-fra-frp.frp-fra.l1x frp-fra.autosep1.bin
> lsx-comp lr apertium-fra-frp.frp-fra.l2x frp-fra.autosep2.bin
> cp /<>/apertium-fra-1.10.0/fra.autogen.bin frp-fra.autogen.bin
> cp /<>/apertium-fra-1.10.0/fra.autopgen.bin frp-fra.autopgen.bin
> apertium-validate-transfer apertium-fra-frp.frp-fra.t1x
> main@standard 373 462
> apertium-validate-interchunk apertium-fra-frp.frp-fra.t2ax
> Error at line 4615, column 23: Undefined attr-item lemg.
> make[2]: *** [Makefile:885: fra-frp.t1x.bin] Error 1


The full build log is available from:
http://qa-logs.debian.net/2022/07/28/apertium-fra-frp_1.0.0-3_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220728;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20220728=lu...@debian.org=1=1=1=1#results

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: apertium-fra-frp
Source-Version: 1.1.0-1
Done: Tino Didriksen 

We believe that the bug you reported is fixed in the latest version of
apertium-fra-frp, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1016...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Tino Didriksen  (supplier of updated apertium-fra-frp 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 01 Nov 2022 09:38:15 +0100
Source: apertium-fra-frp
Architecture: source
Version: 1.1.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Team 

Changed-By: Tino Didriksen 
Closes: 1016338
Changes:
 apertium-fra-frp 

Bug#1023258: marked as done (uses com.sun.org.apache.xml.internal.serialize)

[Debian Bug Tracking System]

Your message dated Tue, 01 Nov 2022 13:22:16 +
with message-id 
and subject line Bug#1023258: fixed in pcalendar 3.4.1-5
has caused the Debian Bug report #1023258,
regarding uses com.sun.org.apache.xml.internal.serialize
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.)


-- 
1023258: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023258
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: pcalendar
Version: 3.4.1-4
Severity: grave
Tags: upstream

I understand that com.sun.org.apache.xml.internal.serialize was an 
internal JDK class which is not available anymore.

When saving, it crashes with this error and DESTROYS the original file:

Exception in thread "AWT-EventQueue-0" java.lang.IllegalAccessError: class 
net.sf.linuxorg.pcal.engine.Engine (in unnamed module @0x614635c2) cannot 
access class com.sun.org.apache.xml.internal.serialize.OutputFormat (in module 
java.xml) because module java.xml does not export 
com.sun.org.apache.xml.internal.serialize to unnamed module @0x614635c2
at net.sf.linuxorg.pcal.engine.Engine.saveToFile(Engine.java:909)
at 
net.sf.linuxorg.pcal.MainWindow.saveToFileHandler(MainWindow.java:1408)
at 
net.sf.linuxorg.pcal.MainWindow$ActionSave.saveActionCore(MainWindow.java:1547)
at 
net.sf.linuxorg.pcal.MainWindow$ActionSave.actionPerformed(MainWindow.java:1553)
at 
java.desktop/javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1972)
at 
java.desktop/javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.java:2313)
at 
java.desktop/javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:405)
at 
java.desktop/javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:262)
at 
java.desktop/javax.swing.plaf.basic.BasicButtonListener.mouseReleased(BasicButtonListener.java:279)
at 
java.desktop/java.awt.AWTEventMulticaster.mouseReleased(AWTEventMulticaster.java:297)
at 
java.desktop/java.awt.Component.processMouseEvent(Component.java:6626)
at 
java.desktop/javax.swing.JComponent.processMouseEvent(JComponent.java:3389)
at java.desktop/java.awt.Component.processEvent(Component.java:6391)
at java.desktop/java.awt.Container.processEvent(Container.java:2266)
at 
java.desktop/java.awt.Component.dispatchEventImpl(Component.java:5001)
at 
java.desktop/java.awt.Container.dispatchEventImpl(Container.java:2324)
at java.desktop/java.awt.Component.dispatchEvent(Component.java:4833)
at 
java.desktop/java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4948)
at 
java.desktop/java.awt.LightweightDispatcher.processMouseEvent(Container.java:4575)
at 
java.desktop/java.awt.LightweightDispatcher.dispatchEvent(Container.java:4516)
at 
java.desktop/java.awt.Container.dispatchEventImpl(Container.java:2310)
at java.desktop/java.awt.Window.dispatchEventImpl(Window.java:2780)
at java.desktop/java.awt.Component.dispatchEvent(Component.java:4833)
at 
java.desktop/java.awt.EventQueue.dispatchEventImpl(EventQueue.java:773)
at java.desktop/java.awt.EventQueue$4.run(EventQueue.java:722)
at java.desktop/java.awt.EventQueue$4.run(EventQueue.java:716)
at 
java.base/java.security.AccessController.doPrivileged(AccessController.java:399)
at 
java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:86)
at 
java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:97)
at java.desktop/java.awt.EventQueue$5.run(EventQueue.java:746)
at java.desktop/java.awt.EventQueue$5.run(EventQueue.java:744)
at 
java.base/java.security.AccessController.doPrivileged(AccessController.java:399)
at 
java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:86)
at java.desktop/java.awt.EventQueue.dispatchEvent(EventQueue.java:743)
at 
java.desktop/java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:203)
at 
java.desktop/java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:124)
at 
java.desktop/java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:113)
at 
java.desktop/java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:109)
at 
java.desktop/java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:101)
  

Bug#1023260: marked as done (sightviewer: Instruction non permise (core dumped))

[Debian Bug Tracking System]

Your message dated Tue, 01 Nov 2022 13:22:54 +
with message-id 
and subject line Bug#1023260: fixed in sight 21.1.1-3
has caused the Debian Bug report #1023260,
regarding sightviewer: Instruction non permise (core dumped)
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.)


-- 
1023260: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023260
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sightviewer
Version: 21.1.1-2
Severity: important

Dear Maintainer,

while trying to start this software, I got a

Instruction non permise (core dumped)

the backtrace (not that usefull but at least it shows that the probleme is in 
the libsight_core library

(gdb) bt
#0  0x77c8da6e in ?? () from /lib/x86_64-linux-gnu/libsight_core.so.21.1
#1  0x77fcdcee in call_init (env=0x7fffdba8, argv=0x7fffdb98, 
argc=1, l=) at ./elf/dl-init.c:70
#2  call_init (l=, argc=1, argv=0x7fffdb98, 
env=0x7fffdba8) at ./elf/dl-init.c:26
#3  0x77fcddd4 in _dl_init (main_map=0x77ffe2c0, argc=1, 
argv=0x7fffdb98, env=0x7fffdba8) at ./elf/dl-init.c:117
#4  0x77fe498a in _dl_start_user () from /lib64/ld-linux-x86-64.so.2
#5  0x0001 in ?? ()
#6  0x7fffdf9d in ?? ()
#7  0x in ?? ()


my CPU

$ lscpu
Architecture :  x86_64
  Mode(s) opératoire(s) des processeurs :   32-bit, 64-bit
  Tailles des adresses: 36 bits physical, 48 bits virtual
  Boutisme :Little Endian
Processeur(s) : 2
  Liste de processeur(s) en ligne : 0,1
Identifiant constructeur :  GenuineIntel
  Nom de modèle :   Intel(R) Core(TM)2 Duo CPU 
T9900  @ 3.06GHz
Famille de processeur : 6
Modèle :23
Thread(s) par cœur :1
Cœur(s) par socket :2
Socket(s) : 1
Révision :  10
multiplication des MHz du/des CPU(s) :  52%
Vitesse maximale du processeur en MHz : 3059,
Vitesse minimale du processeur en MHz : 1596,
BogoMIPS :  6103,21
Drapeaux :  fpu vme de pse tsc msr pae mce cx8 
apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ht tm p
be syscall nx lm constant_tsc 
arch_perfmon pebs bts rep_good nopl cpuid aperfmperf pni dtes64 monitor ds_cpl 
vmx s
mx est tm2 ssse3 cx16 xtpr pdcm 
sse4_1 xsave lahf_lm pti tpr_shadow vnmi flexpriority vpid dtherm
Fonctionnalités de virtualisation : 
  Virtualisation :  VT-x
Caches (somme de toutes) :  
  L1d : 64 KiB (2 instances)
  L1i : 64 KiB (2 instances)
  L2 :  6 MiB (1 instance)
NUMA :  
  Nœud(s) NUMA :1
  Nœud NUMA 0 de processeur(s) :0,1
Vulnérabilités :
  Itlb multihit :   KVM: Mitigation: VMX disabled
  L1tf :Mitigation; PTE Inversion; VMX EPT 
disabled
  Mds : Vulnerable: Clear CPU buffers 
attempted, no microcode; SMT disabled
  Meltdown :Mitigation; PTI
  Mmio stale data : Unknown: No mitigations
  Retbleed :Not affected
  Spec store bypass :   Vulnerable
  Spectre v1 :  Mitigation; usercopy/swapgs 
barriers and __user pointer sanitization
  Spectre v2 :  Mitigation; Retpolines, STIBP 
disabled, RSB filling, PBRSB-eIBRS Not affected
  Srbds :   Not affected
  Tsx async abort : Not affected


-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.0.0-2-amd64 (SMP w/2 CPU threads; PREEMPT)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages sightviewer depends on:
ii  libsight  21.1.1-2

sightviewer 

Bug#949570: marked as done (dropwatch should not use the private binutils shared libraries)

[Debian Bug Tracking System]

Your message dated Tue, 01 Nov 2022 13:20:19 +
with message-id 
and subject line Bug#949570: fixed in dropwatch 1.5.4-1
has caused the Debian Bug report #949570,
regarding dropwatch should not use the private binutils shared libraries
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.)


-- 
949570: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949570
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:dropwatch
Version: 1.5.1-2
Severity: serious
Tags: sid bullseye

dropwatch should not use the private binutils shared libraries.  If it cannot be
dropped, then please link those statically and document it with the Built-Using
tag in the binary package.
--- End Message ---
--- Begin Message ---
Source: dropwatch
Source-Version: 1.5.4-1
Done: Andreas Beckmann 

We believe that the bug you reported is fixed in the latest version of
dropwatch, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 949...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Andreas Beckmann  (supplier of updated dropwatch package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 01 Nov 2022 14:05:23 +0100
Source: dropwatch
Architecture: source
Version: 1.5.4-1
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Andreas Beckmann 
Closes: 949570 1023172
Changes:
 dropwatch (1.5.4-1) unstable; urgency=medium
 .
   * QA upload.
 .
   [ Dmitry Smirnov ]
   * New upstream release.
   * Standards-Version: 4.6.1.
 .
   [ Andreas Beckmann ]
   * Set Maintainer to Debian QA Group.  (See: #1009898)
   * Link against the static libbfd.a.  (Closes: #1023172, #949570)
   * Set Built-Using for statically linking libbfd.a.
   * Switch to debhelper-compat (= 13).
   * Refresh d/copyright.
Checksums-Sha1:
 d91baf14c7bca852c212669dc1b9d7e1261cc2c8 1956 dropwatch_1.5.4-1.dsc
 bf11c18d89838f8748b1ece8fe771b5bb8b26c10 24774 dropwatch_1.5.4.orig.tar.gz
 77d94bd5219a423aa06c00fb0db3c1fcc56804a1 3624 dropwatch_1.5.4-1.debian.tar.xz
 d6c54b0aa771b81fe607af023bc421b5c47f3dd8 6146 
dropwatch_1.5.4-1_source.buildinfo
Checksums-Sha256:
 3fac9d10acfe34709bbd5003102c85d3fe80891b23fd0469345f429e5c85c1af 1956 
dropwatch_1.5.4-1.dsc
 8c43d0c15d0cb9ce179fa1fb0610611723689a6f551b23c70a7ddc1cf068e8d2 24774 
dropwatch_1.5.4.orig.tar.gz
 4bcef1d5b6693131f969936ebac79e1ccd896376e14a0c469a8a0f046434af65 3624 
dropwatch_1.5.4-1.debian.tar.xz
 18978f6c1ead6a307308622f4eb7633e31d5fe30c2de0f2ca159c88d27b350d4 6146 
dropwatch_1.5.4-1_source.buildinfo
Files:
 46896358eb68fdfab1df4d6b47567b00 1956 net optional dropwatch_1.5.4-1.dsc
 94d03b47f424924cf24f21dad941a473 24774 net optional dropwatch_1.5.4.orig.tar.gz
 fa143a4a757698f8fe381f97b2f40ca9 3624 net optional 
dropwatch_1.5.4-1.debian.tar.xz
 c1039394a04d199618347763bbed85dc 6146 net optional 
dropwatch_1.5.4-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCAAuFiEE6/MKMKjZxjvaRMaUX7M/k1np7QgFAmNhGfcQHGFuYmVAZGVi
aWFuLm9yZwAKCRBfsz+TWentCHkwEACe9LPmhrRIhwCODYwRdCy5cGfcg0eGRlYL
AS0Wg4WytJIgWUX3UxWxFW0iYQTymMpK4iyko/IUuZHM9+DERbL2506/akiMm2Ss
dZdtmpjenoHqjVPEWJy0CUKVPSk7aVrqnGrgnfduZI3gvM4bA6+SwoREQeGGrx9z
Bo7FRt1ohq1lUJe/YGoQo/jBETKK+ipx9Pgr5GXY71a9AAlp6Cpdzq2aTehJNrK/
yo7uq1ztqk0qnC7LUMbZ7363sOLWk9L+1SHh1yS9YaCldgedUH4xxHhA04qnui6P
BKZj36C0YILawnAhzzFIabpEgnkl2Jt8RDhLN+/U/YtAF5AJ2TM6reckQr6wuvqc
0pZ3YOUQDByo1jQ8VUOpVi+FDkjr20UHGKIhqzHGyG4JXd8rOz3BlQI0vEf3R76t
atEQLqnY/FQywuLLDSYhU01DsOd+uiTgQuBqng1/BXEcZsBWIURemr1x7wszbSIE
w4nv6vsWQQ/w4MTTdLVSGhhA2oh/UdETzzZpjhSmwdwDH7X0cxPOWejIbCMyhxH4
CW7s/z/NGNp/ixJU+b/86Bpw5mRFH7tUezVVOLe/qHPLKxe7vne/A8kxVn5v2lxI
v20iVe/nyhuJ0EOHTm7WLuhnOfx1MAC7I2z3t/RrlFgrnsb6e32EXOnizK/NupYk
wxBtJwTXyw==
=r47c
-END PGP SIGNATURE End Message ---

Bug#964537: marked as done (dropwatch should not depend on the shared binutils libraries)

[Debian Bug Tracking System]

Your message dated Tue, 01 Nov 2022 13:20:19 +
with message-id 
and subject line Bug#949570: fixed in dropwatch 1.5.4-1
has caused the Debian Bug report #949570,
regarding dropwatch should not depend on the shared binutils libraries
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.)


-- 
949570: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949570
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:dropwatch
Version: 1.5.3-1
Severity: serious
Tags: sid bullseye

dropwatch should not depend on the shared binutils libraries. These are
non-public ABIs, and are changing frequently. If you have to use the dependency,
then please use the static libraries and mark the binary packages with the
"Built-Using" attribute.
--- End Message ---
--- Begin Message ---
Source: dropwatch
Source-Version: 1.5.4-1
Done: Andreas Beckmann 

We believe that the bug you reported is fixed in the latest version of
dropwatch, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 949...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Andreas Beckmann  (supplier of updated dropwatch package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 01 Nov 2022 14:05:23 +0100
Source: dropwatch
Architecture: source
Version: 1.5.4-1
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Andreas Beckmann 
Closes: 949570 1023172
Changes:
 dropwatch (1.5.4-1) unstable; urgency=medium
 .
   * QA upload.
 .
   [ Dmitry Smirnov ]
   * New upstream release.
   * Standards-Version: 4.6.1.
 .
   [ Andreas Beckmann ]
   * Set Maintainer to Debian QA Group.  (See: #1009898)
   * Link against the static libbfd.a.  (Closes: #1023172, #949570)
   * Set Built-Using for statically linking libbfd.a.
   * Switch to debhelper-compat (= 13).
   * Refresh d/copyright.
Checksums-Sha1:
 d91baf14c7bca852c212669dc1b9d7e1261cc2c8 1956 dropwatch_1.5.4-1.dsc
 bf11c18d89838f8748b1ece8fe771b5bb8b26c10 24774 dropwatch_1.5.4.orig.tar.gz
 77d94bd5219a423aa06c00fb0db3c1fcc56804a1 3624 dropwatch_1.5.4-1.debian.tar.xz
 d6c54b0aa771b81fe607af023bc421b5c47f3dd8 6146 
dropwatch_1.5.4-1_source.buildinfo
Checksums-Sha256:
 3fac9d10acfe34709bbd5003102c85d3fe80891b23fd0469345f429e5c85c1af 1956 
dropwatch_1.5.4-1.dsc
 8c43d0c15d0cb9ce179fa1fb0610611723689a6f551b23c70a7ddc1cf068e8d2 24774 
dropwatch_1.5.4.orig.tar.gz
 4bcef1d5b6693131f969936ebac79e1ccd896376e14a0c469a8a0f046434af65 3624 
dropwatch_1.5.4-1.debian.tar.xz
 18978f6c1ead6a307308622f4eb7633e31d5fe30c2de0f2ca159c88d27b350d4 6146 
dropwatch_1.5.4-1_source.buildinfo
Files:
 46896358eb68fdfab1df4d6b47567b00 1956 net optional dropwatch_1.5.4-1.dsc
 94d03b47f424924cf24f21dad941a473 24774 net optional dropwatch_1.5.4.orig.tar.gz
 fa143a4a757698f8fe381f97b2f40ca9 3624 net optional 
dropwatch_1.5.4-1.debian.tar.xz
 c1039394a04d199618347763bbed85dc 6146 net optional 
dropwatch_1.5.4-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCAAuFiEE6/MKMKjZxjvaRMaUX7M/k1np7QgFAmNhGfcQHGFuYmVAZGVi
aWFuLm9yZwAKCRBfsz+TWentCHkwEACe9LPmhrRIhwCODYwRdCy5cGfcg0eGRlYL
AS0Wg4WytJIgWUX3UxWxFW0iYQTymMpK4iyko/IUuZHM9+DERbL2506/akiMm2Ss
dZdtmpjenoHqjVPEWJy0CUKVPSk7aVrqnGrgnfduZI3gvM4bA6+SwoREQeGGrx9z
Bo7FRt1ohq1lUJe/YGoQo/jBETKK+ipx9Pgr5GXY71a9AAlp6Cpdzq2aTehJNrK/
yo7uq1ztqk0qnC7LUMbZ7363sOLWk9L+1SHh1yS9YaCldgedUH4xxHhA04qnui6P
BKZj36C0YILawnAhzzFIabpEgnkl2Jt8RDhLN+/U/YtAF5AJ2TM6reckQr6wuvqc
0pZ3YOUQDByo1jQ8VUOpVi+FDkjr20UHGKIhqzHGyG4JXd8rOz3BlQI0vEf3R76t
atEQLqnY/FQywuLLDSYhU01DsOd+uiTgQuBqng1/BXEcZsBWIURemr1x7wszbSIE
w4nv6vsWQQ/w4MTTdLVSGhhA2oh/UdETzzZpjhSmwdwDH7X0cxPOWejIbCMyhxH4
CW7s/z/NGNp/ixJU+b/86Bpw5mRFH7tUezVVOLe/qHPLKxe7vne/A8kxVn5v2lxI
v20iVe/nyhuJ0EOHTm7WLuhnOfx1MAC7I2z3t/RrlFgrnsb6e32EXOnizK/NupYk
wxBtJwTXyw==
=r47c
-END PGP SIGNATURE End Message ---

Bug#1023172: marked as done (dropwatch: not installable since dependency on outdated libbinutils)

[Debian Bug Tracking System]

Your message dated Tue, 01 Nov 2022 13:20:19 +
with message-id 
and subject line Bug#1023172: fixed in dropwatch 1.5.4-1
has caused the Debian Bug report #1023172,
regarding dropwatch: not installable since dependency on outdated libbinutils
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.)


-- 
1023172: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023172
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: dropwatch
Version: 1.5.3-1+b2
Severity: serious

Hi,

dropwatch is not installable in sid as it depends on libbinutils (< 2.35.1),
however the current version of that package in sid is 2.39-8.

-Ralf.
--- End Message ---
--- Begin Message ---
Source: dropwatch
Source-Version: 1.5.4-1
Done: Andreas Beckmann 

We believe that the bug you reported is fixed in the latest version of
dropwatch, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1023...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Andreas Beckmann  (supplier of updated dropwatch package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 01 Nov 2022 14:05:23 +0100
Source: dropwatch
Architecture: source
Version: 1.5.4-1
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Andreas Beckmann 
Closes: 949570 1023172
Changes:
 dropwatch (1.5.4-1) unstable; urgency=medium
 .
   * QA upload.
 .
   [ Dmitry Smirnov ]
   * New upstream release.
   * Standards-Version: 4.6.1.
 .
   [ Andreas Beckmann ]
   * Set Maintainer to Debian QA Group.  (See: #1009898)
   * Link against the static libbfd.a.  (Closes: #1023172, #949570)
   * Set Built-Using for statically linking libbfd.a.
   * Switch to debhelper-compat (= 13).
   * Refresh d/copyright.
Checksums-Sha1:
 d91baf14c7bca852c212669dc1b9d7e1261cc2c8 1956 dropwatch_1.5.4-1.dsc
 bf11c18d89838f8748b1ece8fe771b5bb8b26c10 24774 dropwatch_1.5.4.orig.tar.gz
 77d94bd5219a423aa06c00fb0db3c1fcc56804a1 3624 dropwatch_1.5.4-1.debian.tar.xz
 d6c54b0aa771b81fe607af023bc421b5c47f3dd8 6146 
dropwatch_1.5.4-1_source.buildinfo
Checksums-Sha256:
 3fac9d10acfe34709bbd5003102c85d3fe80891b23fd0469345f429e5c85c1af 1956 
dropwatch_1.5.4-1.dsc
 8c43d0c15d0cb9ce179fa1fb0610611723689a6f551b23c70a7ddc1cf068e8d2 24774 
dropwatch_1.5.4.orig.tar.gz
 4bcef1d5b6693131f969936ebac79e1ccd896376e14a0c469a8a0f046434af65 3624 
dropwatch_1.5.4-1.debian.tar.xz
 18978f6c1ead6a307308622f4eb7633e31d5fe30c2de0f2ca159c88d27b350d4 6146 
dropwatch_1.5.4-1_source.buildinfo
Files:
 46896358eb68fdfab1df4d6b47567b00 1956 net optional dropwatch_1.5.4-1.dsc
 94d03b47f424924cf24f21dad941a473 24774 net optional dropwatch_1.5.4.orig.tar.gz
 fa143a4a757698f8fe381f97b2f40ca9 3624 net optional 
dropwatch_1.5.4-1.debian.tar.xz
 c1039394a04d199618347763bbed85dc 6146 net optional 
dropwatch_1.5.4-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCAAuFiEE6/MKMKjZxjvaRMaUX7M/k1np7QgFAmNhGfcQHGFuYmVAZGVi
aWFuLm9yZwAKCRBfsz+TWentCHkwEACe9LPmhrRIhwCODYwRdCy5cGfcg0eGRlYL
AS0Wg4WytJIgWUX3UxWxFW0iYQTymMpK4iyko/IUuZHM9+DERbL2506/akiMm2Ss
dZdtmpjenoHqjVPEWJy0CUKVPSk7aVrqnGrgnfduZI3gvM4bA6+SwoREQeGGrx9z
Bo7FRt1ohq1lUJe/YGoQo/jBETKK+ipx9Pgr5GXY71a9AAlp6Cpdzq2aTehJNrK/
yo7uq1ztqk0qnC7LUMbZ7363sOLWk9L+1SHh1yS9YaCldgedUH4xxHhA04qnui6P
BKZj36C0YILawnAhzzFIabpEgnkl2Jt8RDhLN+/U/YtAF5AJ2TM6reckQr6wuvqc
0pZ3YOUQDByo1jQ8VUOpVi+FDkjr20UHGKIhqzHGyG4JXd8rOz3BlQI0vEf3R76t
atEQLqnY/FQywuLLDSYhU01DsOd+uiTgQuBqng1/BXEcZsBWIURemr1x7wszbSIE
w4nv6vsWQQ/w4MTTdLVSGhhA2oh/UdETzzZpjhSmwdwDH7X0cxPOWejIbCMyhxH4
CW7s/z/NGNp/ixJU+b/86Bpw5mRFH7tUezVVOLe/qHPLKxe7vne/A8kxVn5v2lxI
v20iVe/nyhuJ0EOHTm7WLuhnOfx1MAC7I2z3t/RrlFgrnsb6e32EXOnizK/NupYk
wxBtJwTXyw==
=r47c
-END PGP SIGNATURE End Message ---

Bug#1022289: libassuan: FTBFS: configure: error: libgpg-error was not found

[Andreas Metzler]

On 2022-10-23 Andreas Metzler  wrote:
[...]
> Caused by new gpg-error dropping gpg-error-config, this works for me:

> --- libassuan-2.5.5/debian/rules2022-04-30 17:47:12.0 +0200
> +++ patched/libassuan-2.5.5.patched/debian/rules2022-10-23 
> 18:23:40.505849321 +0200
> @@ -27,7 +27,6 @@
> for cpu in i686 x86_64; do \
>  mkdir -p build-$$cpu-w64-mingw32 && \
>  cd build-$$cpu-w64-mingw32 && $(WIN_FLAGS) ../configure \
> -   --with-libgpg-error-prefix=/usr/$$cpu-w64-mingw32 \

Hello,

Commited to GIT, please give me a heads up if you want me to make either
a NMU or add myself to Uploaders and make a regular upload. (Although
this is a serious bugreport I do not think it is yet so urgent to
require a upload without maintainer feedback. - Might change, e.g if
libassuan blocked a transition.)

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'


signature.asc
Description: PGP signature

Bug#1023248: marked as done (systemd fails to install: Failed to resolve group 'systemd-journal'.)

[Debian Bug Tracking System]

Your message dated Tue, 01 Nov 2022 13:11:39 +
with message-id 
and subject line Bug#1023248: fixed in systemd 252-2
has caused the Debian Bug report #1023248,
regarding systemd fails to install: Failed to resolve group 'systemd-journal'.
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.)


-- 
1023248: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023248
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: systemd
Version: 252-1
Severity: serious

systemd fails to install in unstable:

mmdebstrap --verbose --variant apt --include systemd unstable /dev/null

| Setting up systemd (252-1) ...
| Created symlink /etc/systemd/system/getty.target.wants/getty@tty1.service → 
/lib/systemd/system/getty@.service.
| Created symlink /etc/systemd/system/multi-user.target.wants/remote-fs.target 
→ /lib/systemd/system/remote-fs.target.
| Created symlink 
/etc/systemd/system/sysinit.target.wants/systemd-pstore.service → 
/lib/systemd/system/systemd-pstore.service.
| Initializing machine ID from random generator.
| /usr/lib/tmpfiles.d/systemd.conf:28: Failed to resolve group 
'systemd-journal'.
| /usr/lib/tmpfiles.d/systemd.conf:29: Failed to resolve group 
'systemd-journal'.
| /usr/lib/tmpfiles.d/systemd.conf:30: Failed to resolve group 
'systemd-journal'.
| dpkg: error processing package systemd (--configure):
|  installed systemd package post-installation script subprocess returned error 
exit status 65
| Processing triggers for libc-bin (2.35-4) ...
| Errors were encountered while processing:
|  systemd
| E: Sub-process env returned an error code (1)

Hope you can figure this out quickly. It happens to break rebootstrap
CI. If you happen to know a workaround that'd be appreciated as well.

Helmut
--- End Message ---
--- Begin Message ---
Source: systemd
Source-Version: 252-2
Done: Luca Boccassi 

We believe that the bug you reported is fixed in the latest version of
systemd, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1023...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Luca Boccassi  (supplier of updated systemd package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 01 Nov 2022 12:06:18 +
Source: systemd
Architecture: source
Version: 252-2
Distribution: unstable
Urgency: medium
Maintainer: Debian systemd Maintainers 

Changed-By: Luca Boccassi 
Closes: 1023248
Changes:
 systemd (252-2) unstable; urgency=medium
 .
   [ Jochen Sprickerhof ]
   * Let dh_installsysusers fix the /var/log/journal permissions.
 dh_installsysusers adds a systemd-sysusers in #DEBHELPER#. Otherwise
 it fails with: /usr/lib/tmpfiles.d/systemd.conf:28: Failed to resolve
 group 'systemd-journal'. Regression of fa0aade329. (Closes: #1023248)
   * Move restarting units after #DEBHELPER#. This makes sure that systemd-
 sysusers was executed as well as systemd-tmpfiles to setup proper
 permissions for /var/log/journal before systemd-journald is being
 restarted.
Checksums-Sha1:
 55df98d274319af8fb7c7cd0b9fdb1f99df75084 6315 systemd_252-2.dsc
 bee6eec4c8cc09f3e6a4aa25197d09d5f910441f 166684 systemd_252-2.debian.tar.xz
 76d068d7740eec8df4c6620cb0e59dd52a1b41f7 11295 systemd_252-2_source.buildinfo
Checksums-Sha256:
 bb9f528320efdd57424b8738614933d9e98524908047e3b48663a3fc55bddef4 6315 
systemd_252-2.dsc
 a35ecea1e0c79805ab2391fea1e2c31b0a340fa8d1fc2e831dd4818d0ae6f0fa 166684 
systemd_252-2.debian.tar.xz
 9fccf7c7789f5e169e1b8db5a6d2add37ba27a008050f0a10715fe6a8fd54c52 11295 
systemd_252-2_source.buildinfo
Files:
 c865e41ee811fd8c38ca4a5a1d5c07a0 6315 admin optional systemd_252-2.dsc
 363afce2870be6c9a4c22ab20aab6b61 166684 admin optional 
systemd_252-2.debian.tar.xz
 0f3a3ba08af1c34aeddaba109e0ab2f6 11295 admin optional 
systemd_252-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEErCSqx93EIPGOymuRKGv37813JB4FAmNhFvgRHGJsdWNhQGRl
Ymlhbi5vcmcACgkQKGv37813JB4aQQ/+JqYESnZK5V3D1GBWCxGRylSKgN9DaSwl
Jgfr4bid6SgJeckVTV3e++fHf8J26Hiqq5nHYH5TBqkX/9TJxGMFuYVkLNG/LMbM
hDpm/DcDgqnE/DEBMBSmi/U353UKWmI+GL3dBsejRiJw+stJ98rkCxrTd/uaNqY1
n85J+YC0mJkNvSgmm1HFL1oTjRQjXtL91S++5yF45tQmUU4g2xn6r1lOPYoImzjO

Processed: Bug#1023258 marked as pending in pcalendar

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1023258 [pcalendar] uses com.sun.org.apache.xml.internal.serialize
Added tag(s) pending.

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

Bug#1023258: marked as pending in pcalendar

[Étienne Mollier]

Control: tag -1 pending

Hello,

Bug #1023258 in pcalendar reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/med-team/pcalendar/-/commit/654e06a3b0fe5e13a689c6123904ba9d74f5c3be


fixes.patch: patch remaining com.sun.org.apache.xml.internal.serialize.

Closes: #1023258


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1023258

Bug#1023178: microprofile: Contains non-free source

[Bastian Germann]

Am 01.11.22 um 13:03 schrieb Andrea Pappacoda:
I'll fix it as soon as possible, possibly in the 4.0 release. I've already uploaded the latest release to mentors, but 
it doesn't contain this fix.


For the 4.0 release you would have to clarify the license situation.
At least, the Unlicense has to be contained in the debian/copyright file even 
if it does not apply to any file.

Bug#1013648: marked as done (apertium-nno-nob: FTBFS: configure: error: Package requirements (apertium-lex-tools >= 0.2.2) were not met)

[Debian Bug Tracking System]

Your message dated Tue, 01 Nov 2022 12:34:18 +
with message-id 
and subject line Bug#1013648: fixed in apertium-nno-nob 1.5.0-1
has caused the Debian Bug report #1013648,
regarding apertium-nno-nob: FTBFS: configure: error: Package requirements 
(apertium-lex-tools >= 0.2.2) were not met
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.)


-- 
1013648: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013648
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: apertium-nno-nob
Version: 1.3.0-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220624 ftbfs-bookworm

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
> checking pkg-config is at least version 0.9.0... yes
> checking for apertium >= 3.6.0... yes
> checking for lttoolbox >= 3.5.0... yes
> checking for cg3 >= 1.3.0... yes
> checking for apertium-lex-tools >= 0.2.2... no
> configure: error: Package requirements (apertium-lex-tools >= 0.2.2) were not 
> met
> 
> No package 'apertium-lex-tools' found
> 
> Consider adjusting the PKG_CONFIG_PATH environment variable if you
> installed software in a non-standard prefix.
> 
> Alternatively, you may set the environment variables APERTIUM_LEX_TOOLS_CFLAGS
> and APERTIUM_LEX_TOOLS_LIBS to avoid the need to call pkg-config.
> See the pkg-config man page for more details.
>   tail -v -n \+0 config.log


The full build log is available from:
http://qa-logs.debian.net/2022/06/24/apertium-nno-nob_1.3.0-2_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220624;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20220624=lu...@debian.org=1=1=1=1#results

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: apertium-nno-nob
Source-Version: 1.5.0-1
Done: Tino Didriksen 

We believe that the bug you reported is fixed in the latest version of
apertium-nno-nob, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1013...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Tino Didriksen  (supplier of updated apertium-nno-nob 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 26 Oct 2022 13:41:14 +0200
Source: apertium-nno-nob
Architecture: source
Version: 1.5.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Team 

Changed-By: Tino Didriksen 
Closes: 1013648
Changes:
 apertium-nno-nob (1.5.0-1) unstable; urgency=medium
 .
   * New upstream release (Closes: #1013648)
   * Bundles apertium-nno 1.3.0 and apertium-nob 1.3.0
Checksums-Sha1:
 30bf42f01fc22291df8fe07ae368efb8c83663fd 2209 apertium-nno-nob_1.5.0-1.dsc
 68b5f12e6ba90a88b2ce980d1f65646946b7847e 5763321 
apertium-nno-nob_1.5.0.orig.tar.bz2
 2b291655e40313b13effc37a60dc1acdd92921b7 2852 
apertium-nno-nob_1.5.0-1.debian.tar.xz
 e2a9df15adbc4418a98004fc8962879847c710b9 6932 
apertium-nno-nob_1.5.0-1_source.buildinfo
Checksums-Sha256:
 120ef13e7c1ef227d5caa95f8e6adbd02e4ad1d1c1ab5ed94cbe754ea0800728 2209 
apertium-nno-nob_1.5.0-1.dsc
 525da77a62794eb6e28cef39200262312cec83df5cb3e95e15095a6bcefa9d24 5763321 
apertium-nno-nob_1.5.0.orig.tar.bz2
 0510a11b284e8924e3c0585ea7bbe2a3c4042e2c9eca972ef04efab77bbbfb22 2852 
apertium-nno-nob_1.5.0-1.debian.tar.xz
 e51dc1e9955d657c65590349ac5c81f4d09ad350b37ac42f04507cf74ffe5751 6932 
apertium-nno-nob_1.5.0-1_source.buildinfo
Files:
 974e374e0f33b80d7dd029d2d2c50773 2209 science optional 
apertium-nno-nob_1.5.0-1.dsc
 47e158e977068848d90f974c5cf082e5 5763321 science optional 
apertium-nno-nob_1.5.0.orig.tar.bz2
 

Processed: bug 1023178 is forwarded to https://github.com/jonasmr/microprofile/issues/81

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forwarded 1023178 https://github.com/jonasmr/microprofile/issues/81
Bug #1023178 [src:microprofile] microprofile: Contains non-free source
Set Bug forwarded-to-address to 
'https://github.com/jonasmr/microprofile/issues/81'.
> thanks
Stopping processing here.

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

Bug#1023265: Test failures blocking migration of rust-libc and several deps to testing

[John Goerzen]

Package: rust-libc
Version: 0.2.137-1
Severity: serious
X-Debbugs-CC: plugw...@debian.org, wolfg...@silbermayr.at, infini...@debian.org

Migration of several other packages is blocked due to the issues listed
over at:

https://tracker.debian.org/pkg/rust-libc

In particular, it has caused failures in rust-capston on s390x and
rust-netlink-sys in multiple platforms.

Thanks,

John

Processed: Bug#1023260 marked as pending in fw4spl

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1023260 [sightviewer] sightviewer: Instruction non permise (core dumped)
Added tag(s) pending.

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

Bug#1023260: marked as pending in fw4spl

[Étienne Mollier]

Control: tag -1 pending

Hello,

Bug #1023260 in fw4spl reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/med-team/sight/-/commit/411f276bed57e8d50d3f78606cd5cbe51488b43b


d/rules: set SIGHT_ARCH to force CPU baseline.

The default provided by cmake files is to build with x86-64-v3 which
would include avx and avx2 support and leading to baseline violations
otherwise.

Closes: #1023260


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1023260

Bug#1023178: microprofile: Contains non-free source

[Andrea Pappacoda]

On Mon, 31 Oct 2022 11:02:55 +0100 Bastian Germann  
wrote:
> The files src/microprofile*.html contain JavaScript code from 
https://gist.github.com/mjackson/5311256
> which never got a license even though people have asked for it. So 
please exclude them.


Hi Bastian, thank you for the report. I'll fix it as soon as possible, 
possibly in the 4.0 release. I've already uploaded the latest release 
to mentors, but it doesn't contain this fix.


As a sidenote, the BTS doesn't send me emails, probably because of its 
broken DMARC/DKIM setup. In the future, please Cc me in emails you send 
to the BTS.


Thanks, as always!

Processed: Re: [Debian-med-packaging] Bug#1023260: sightviewer: Instruction non permise (core dumped)

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #1023260 [sightviewer] sightviewer: Instruction non permise (core dumped)
Severity set to 'serious' from 'important'

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

Bug#1023248: marked as pending in systemd

[Luca Boccassi]

Control: tag -1 pending

Hello,

Bug #1023248 in systemd reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/systemd-team/systemd/-/commit/b6e55a055e7fe21c76c71eb133de14811c4bb6c7


Let dh_installsysusers fix the /var/log/journal permissions

dh_installsysusers adds a systemd-sysusers in #DEBHELPER#. Otherwise
it fails with:

/usr/lib/tmpfiles.d/systemd.conf:28: Failed to resolve group 'systemd-journal'.

Regression of fa0aade329.
Closes: #1023248


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1023248

Processed: Bug#1023248 marked as pending in systemd

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1023248 [systemd] systemd fails to install: Failed to resolve group 
'systemd-journal'.
Added tag(s) pending.

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

Bug#1013259: samba-libs: Possible policy violation (now with libndr.so.2 => libndr.so.3)

[Michael Stone]

On Tue, Nov 01, 2022 at 10:59:11AM +0300, Michael Tokarev wrote:

And this revealed one more issue here, now with samba 4.17.  Where, the
same libndr.so again, has changed soname from libndr.so.2 to libndr.so.3!

And it looks like *this* is what you're talking about now, once 4.17 with
this new libndr.so.3 hits unstable.


Yes, sorry I wasn't as clear as I thought. :)

Bug#1022513: marked as done (bdebstrap: FTBFS: distutils.errors.DistutilsClassError: command class must subclass Command)

[Debian Bug Tracking System]

Your message dated Tue, 01 Nov 2022 11:19:46 +
with message-id 
and subject line Bug#1022513: fixed in bdebstrap 0.4.1-1
has caused the Debian Bug report #1022513,
regarding bdebstrap: FTBFS: distutils.errors.DistutilsClassError: command class 
 must subclass Command
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.)


-- 
1022513: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022513
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: bdebstrap
Version: 0.4.0-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221023 ftbfs-bookworm

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
>  debian/rules clean
> dh clean --buildsystem pybuild --with python3
>dh_auto_clean -O--buildsystem=pybuild
> I: pybuild base:240: python3.10 setup.py clean 
> /<>/setup.py:19: DeprecationWarning: The distutils package is 
> deprecated and slated for removal in Python 3.12. Use setuptools or check PEP 
> 632 for potential alternatives
>   import distutils.cmd
> /usr/lib/python3/dist-packages/_distutils_hack/__init__.py:18: UserWarning: 
> Distutils was imported before Setuptools, but importing Setuptools also 
> replaces the `distutils` module in `sys.modules`. This may lead to 
> undesirable behaviors or errors. To avoid these issues, avoid using distutils 
> directly, ensure that setuptools is installed in the traditional way (e.g. 
> not an editable install), and/or make sure that setuptools is always imported 
> before distutils.
>   warnings.warn(
> /usr/lib/python3/dist-packages/_distutils_hack/__init__.py:33: UserWarning: 
> Setuptools is replacing distutils.
>   warnings.warn("Setuptools is replacing distutils.")
> Traceback (most recent call last):
>   File "/<>/setup.py", line 74, in 
> setup(
>   File "/usr/lib/python3/dist-packages/setuptools/__init__.py", line 87, in 
> setup
> return distutils.core.setup(**attrs)
>   File "/usr/lib/python3/dist-packages/setuptools/_distutils/core.py", line 
> 172, in setup
> ok = dist.parse_command_line()
>   File "/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py", line 
> 474, in parse_command_line
> args = self._parse_command_opts(parser, args)
>   File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 1107, in 
> _parse_command_opts
> nargs = _Distribution._parse_command_opts(self, parser, args)
>   File "/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py", line 
> 540, in _parse_command_opts
> raise DistutilsClassError(
> distutils.errors.DistutilsClassError: command class  '__main__.CleanCommand'> must subclass Command
> E: pybuild pybuild:379: clean: plugin distutils failed with: exit code=1: 
> python3.10 setup.py clean 
> dh_auto_clean: error: pybuild --clean -i python{version} -p 3.10 returned 
> exit code 13
> make: *** [debian/rules:6: clean] Error 25


The full build log is available from:
http://qa-logs.debian.net/2022/10/23/bdebstrap_0.4.0-1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20221023;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20221023=lu...@debian.org=1=1=1=1#results

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: bdebstrap
Source-Version: 0.4.1-1
Done: Benjamin Drung 

We believe that the bug you reported is fixed in the latest version of
bdebstrap, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1022...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Benjamin Drung  (supplier of updated bdebstrap package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP