Processing of zope.proxy_5.1-3_source.changes

2023-12-21 Thread Debian FTP Masters
zope.proxy_5.1-3_source.changes uploaded successfully to localhost
along with the files:
  zope.proxy_5.1-3.dsc
  zope.proxy_5.1-3.debian.tar.xz
  zope.proxy_5.1-3_source.buildinfo

Greetings,

Your Debian queue daemon (running on host usper.debian.org)



zope.proxy_5.1-3_source.changes ACCEPTED into unstable

2023-12-21 Thread Debian FTP Masters
Thank you for your contribution to Debian.



Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 21 Dec 2023 14:28:48 +0100
Source: zope.proxy
Architecture: source
Version: 5.1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Matthias Klose 
Changes:
 zope.proxy (5.1-3) unstable; urgency=medium
 .
   * QA upload.
   * Fix autopkg test, importing from the installed module.
Checksums-Sha1:
 bb3d84db6f75c842e207918706e5f211acd83b10 2086 zope.proxy_5.1-3.dsc
 2453e7bd59b84e2c2b466d7227ae3fd8342f9207 5204 zope.proxy_5.1-3.debian.tar.xz
 02eff8566b8b23b66acca27024f6f6258f81195b 7225 zope.proxy_5.1-3_source.buildinfo
Checksums-Sha256:
 9ea5ce6e2a8b94fe2e017bb9430dfd2c62f59ac6fe20ad0d8b60cc754d9c9590 2086 
zope.proxy_5.1-3.dsc
 d916f1e01c82b0f213ac20a99143e9153fbb45bcc468d65765d25d29a342a23e 5204 
zope.proxy_5.1-3.debian.tar.xz
 de217344689aea00f4d7a8c4b13631a75cba634685650832207f8a53fbfef82f 7225 
zope.proxy_5.1-3_source.buildinfo
Files:
 f32e5655a8b2db8bf73eef11fe45590d 2086 zope optional zope.proxy_5.1-3.dsc
 00c5e3a78d927c180a7610004809038b 5204 zope optional 
zope.proxy_5.1-3.debian.tar.xz
 2c88fe4bfd4ccd880d174f34e6794bd2 7225 zope optional 
zope.proxy_5.1-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCgAuFiEE1WVxuIqLuvFAv2PWvX6qYHePpvUFAmWEPgoQHGRva29AZGVi
aWFuLm9yZwAKCRC9fqpgd4+m9bA9D/oDUxi5ywek/RgovHcoAtCm/p0EZZgSBBdx
RUSZfsRb+pCVhJEsIDM+DJMWU5GwwT0QWxEUd+1vUc2aB69QULaFljyZxXrcDCD3
/bF+2/mI356ibT6swC00EC5UKMq3sWJulQYRio+Wr1iiKtJwbBp6H7c26eGHvAag
f7945M4C/OVoD955OLeleLtHdYaGMqw6aXdc4jE8YQrcyX9QuB81kMVNWpXZCYq7
TF+Rz3onP5Oc2wSxSFrH5HCkZynFrGQfx6CfKoWvMyQkxJJc8/J1KmugVoWI5p4e
jhklVziv/XhDwub3gfzYjq67wlB8Ho236KRfthoHbjaueapGN9OztuN0aK2Ea6bo
H7YFxBizWX8DCgmhL2tLLzXbbceNxTgqULmtk0yJmVeBJLGwvLFlwPBeWbKPUJAY
VpBizFx5K3ge8mXXuleqtNic6WLdW5P0mPjM1CRblFY+4d9B6kp7ouN2t+zledmY
Sp8AAxurJMbVgSb9FUe/DbneP5I5CM460jWcsjGC2u2Glo/Zgy00sXNeOKvVI0DI
nJ5TjZPsRCwLldDNT1h08eH6b3LKyavL+anr7RWWOqjqx99G16UevkH6S6X5+OoN
TQ//9YfwOC3fOsCNFV2Uhjk+gJtaJN8zB9AMq3V05DEu40PYeV8mBX9FTqI1PHr+
+jR6mTlFyA==
=kwRg
-END PGP SIGNATURE-



Bug#999937: tup: depends on obsolete pcre3 library

2023-12-21 Thread Yavor Doganov
On Tue, Aug 29, 2023 at 03:18:26PM +0200, Bastian Germann wrote:
> On Tue, 31 Jan 2023 21:36:46 +0800 Bo YU  wrote:
> > The upstream has tried to switch pcre2[0], but the backporting is
> > not easy, so maybe waiting a new release is good iead.
> 
> I have started a backport in git but there is at least one linker
> flag missing.

That's right; the attached patch makes the build succeed for me but I
have not tested further (sorry for the patch noise; it's because I had
to "quilt refresh").
>From 2b6f55b4d9f476646072d2be197b4fc1defcf7ac Mon Sep 17 00:00:00 2001
From: Yavor Doganov 
Date: Thu, 21 Dec 2023 19:20:23 +0200
Subject: [PATCH] pcre2.patch: Add missing linker flag; refresh

---
 debian/patches/pcre2.patch | 81 +-
 1 file changed, 37 insertions(+), 44 deletions(-)

diff --git a/debian/patches/pcre2.patch b/debian/patches/pcre2.patch
index 9d012bb..031b6a7 100644
--- a/debian/patches/pcre2.patch
+++ b/debian/patches/pcre2.patch
@@ -6,11 +6,9 @@ Subject: Update pcre 8.44 -> pcre2 10.42
 libpcre is no longer maintained, and was replaced by libpcre2. This
 requires some minor API changes.
 ---
-diff --git a/Tupfile b/Tupfile
-index 107c81cca..cc6ed1ce5 100644
 a/Tupfile
-+++ b/Tupfile
-@@ -30,7 +30,7 @@ srcs += src/sqlite3/*.o
+--- tup.orig/Tupfile
 tup/Tupfile
+@@ -30,7 +30,7 @@
  endif
  
  ifeq ($(use_system_pcre),y)
@@ -19,11 +17,9 @@ index 107c81cca..cc6ed1ce5 100644
  else
  srcs += src/pcre/*.o
  endif
-diff --git a/Tuprules.tup b/Tuprules.tup
-index 3cdab0ffc..a7fd6cb66 100644
 a/Tuprules.tup
-+++ b/Tuprules.tup
-@@ -99,7 +99,7 @@ else
+--- tup.orig/Tuprules.tup
 tup/Tuprules.tup
+@@ -89,7 +89,7 @@
  use_system_pcre = $(TUP_USE_SYSTEM_PCRE)
  endif
  ifeq ($(use_system_pcre),y)
@@ -32,11 +28,18 @@ index 3cdab0ffc..a7fd6cb66 100644
  else
  CFLAGS += -I$(TUP_CWD)/src/pcre
  CFLAGS += -DPCRE_STATIC
-diff --git a/build.sh b/build.sh
-index 7fecb8914..6ac7041e6 100755
 a/build.sh
-+++ b/build.sh
-@@ -80,6 +80,7 @@ mkdir luabuiltin
+--- tup.orig/build.sh
 tup/build.sh
+@@ -27,7 +27,7 @@
+ 	echo "Error: invalid TUP_SERVER \"$server\"" 1>&2
+ 	exit 1
+ fi
+-LDFLAGS="$LDFLAGS -lm"
++LDFLAGS="$LDFLAGS -lm -lpcre2-8"
+ : ${CC:=gcc}
+ case "$os" in
+ 	Linux)
+@@ -80,6 +80,7 @@
  ./lua ../src/luabuiltin/xxd.lua builtin.lua luabuiltin/luabuiltin.h
  
  CFLAGS="$CFLAGS -DTUP_SERVER=\"$server\""
@@ -44,11 +47,9 @@ index 7fecb8914..6ac7041e6 100755
  CFLAGS="$CFLAGS -DHAVE_CONFIG_H"
  
  for i in ../src/tup/*.c ../src/tup/tup/main.c ../src/tup/monitor/null.c ../src/tup/flock/fcntl.c ../src/inih/ini.c ../src/pcre/*.c $plat_files; do
-diff --git a/src/tup/entry.c b/src/tup/entry.c
-index 90e1b80c0..96842bc4b 100644
 a/src/tup/entry.c
-+++ b/src/tup/entry.c
-@@ -151,7 +151,7 @@ static int rm_entry(tupid_t tupid, int safe)
+--- tup.orig/src/tup/entry.c
 tup/src/tup/entry.c
+@@ -151,7 +151,7 @@
  		string_tree_rm(&tent->parent->entries, &tent->name);
  	}
  	if(tent->re) {
@@ -57,7 +58,7 @@ index 90e1b80c0..96842bc4b 100644
  	}
  	free_tent_tree(&tent->stickies);
  	free_tent_tree(&tent->group_stickies);
-@@ -504,11 +504,13 @@ static struct tup_entry *new_entry(tupid_t tupid, tupid_t dt,
+@@ -473,11 +473,13 @@
  	RB_INIT(&tent->entries);
  
  	if(tent->dt == exclusion_dt()) {
@@ -75,7 +76,7 @@ index 90e1b80c0..96842bc4b 100644
  			return NULL;
  		}
  	} else {
-@@ -795,14 +797,16 @@ int exclusion_match(FILE *f, struct tent_entries *exclusion_root, const char *s,
+@@ -767,14 +769,16 @@
  	*match = 0;
  	RB_FOREACH(tt, tent_entries, exclusion_root) {
  		int rc;
@@ -95,10 +96,8 @@ index 90e1b80c0..96842bc4b 100644
  			fprintf(f, "tup error: Regex failed to execute: %s\n", tt->tent->name.s);
  			return -1;
  		}
-diff --git a/src/tup/entry.h b/src/tup/entry.h
-index 332849842..1b37e077e 100644
 a/src/tup/entry.h
-+++ b/src/tup/entry.h
+--- tup.orig/src/tup/entry.h
 tup/src/tup/entry.h
 @@ -26,9 +26,9 @@
  #include "string_tree.h"
  #include "db_types.h"
@@ -110,7 +109,7 @@ index 332849842..1b37e077e 100644
  
  struct variant;
  struct estring;
-@@ -51,7 +51,7 @@ struct tup_entry {
+@@ -51,7 +51,7 @@
  	_Atomic int refcount;
  
  	/* For exclusions */
@@ -119,11 +118,9 @@ index 332849842..1b37e077e 100644
  
  	/* For command strings */
  	char *flags;
-diff --git a/src/tup/parser.c b/src/tup/parser.c
-index ce057737f..71ee32c79 100644
 a/src/tup/parser.c
-+++ b/src/tup/parser.c
-@@ -2288,6 +2288,7 @@ struct path_list *new_pl(struct tupfile *tf, const char *s, int len, struct bin_
+--- tup.orig/src/tup/parser.c
 tup/src/tup/parser.c
+@@ -2235,6 +2235,7 @@
  	pl->pel = NULL;
  	pl->bin = NULL;
  	pl->re = NULL;
@@ -131,7 +128,8 @@ index ce057737f..71ee32c79 100644
  	memcpy(pl->mem, s, len);
  	pl->mem[len] = 0;
  	pl->orderid = orderid;
-@@ -2316,13 +2317,16 @@ struct path_list *new_pl(struct tupfile *tf, const char *s, int len, struct bin_
+@@ -2262,14 +2263,17 @@
+ 		}
  	} else if(p[0] == '^') {
  		/* Exclusion */
 -		const char

Bug#1051502: Patch for d/watch

2023-12-21 Thread Vinay Keshava

--- a/debian/watch
+++ b/debian/watch
@@ -4,7 +4,8 @@
 # See uscan(1) for format

 # Compulsory line, this is a version 3 file
-version=3
-
-http://ftp.easysw.com/pub/epm/([\d\.]+)/epm-(.*)-source.tar.gz
-
+version=4
+opts="searchmode=plain,\
+filenamemangle=s%.*/v?@ANY_VERSION@%@PACKAGE@-$1.tar.xz%" \
+https://api.github.com/repos/jimjag/epm/releases?per_page=50 \
+https://api.github.com/repos/[^/]+/[^/]+/tarball/v?@ANY_VERSION@


epm upstream url has been changed hence the updated d/watch.

Here is the patch for d/watch, if anyone is interested to add the patch 
and update epm to v5



--
Best

Vinay Keshava



Bug#1030553: marked as done (tup FTBFS on hppa)

2023-12-21 Thread Debian Bug Tracking System
Your message dated Fri, 22 Dec 2023 00:38:13 +
with message-id 
and subject line Bug#1030553: fixed in tup 0.7.11-4
has caused the Debian Bug report #1030553,
regarding tup FTBFS on hppa
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.)


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

Package: tup
Tags: patch, ftbfs, hppa
Version: 0.7.11-3

The attached patch fixes the tup build on hppa.
In addition it would make sense that tup is compiled with the "future+lfs" flags
to support large files on large discs on 32-bit builds.
It currently builds with   -D_FILE_OFFSET_BITS=64 but large files is still 
missing.

Please apply to next upload.

Thanks!
Helgediff -up ./debian/rules.org ./debian/rules
--- ./debian/rules.org	2023-02-04 22:15:19.619396046 +
+++ ./debian/rules	2023-02-04 22:15:59.371776381 +
@@ -1,5 +1,5 @@
 #!/usr/bin/make -f
-export DEB_BUILD_MAINT_OPTIONS = hardening=+all qa=+canary
+export DEB_BUILD_MAINT_OPTIONS = hardening=+all qa=+canary future=+lfs
 DPKG_EXPORT_BUILDFLAGS = 1
 include /usr/share/dpkg/default.mk
 
diff -up ./src/tup/platform.c.org ./src/tup/platform.c
--- ./src/tup/platform.c.org	2023-02-04 22:10:17.296503537 +
+++ ./src/tup/platform.c	2023-02-04 22:11:02.672937681 +
@@ -60,6 +60,8 @@ const char *tup_arch = "arm";
 const char *tup_arch = "arm64";
 #elif __s390x__
 const char *tup_arch = "s390x";
+#elif __hppa__
+const char *tup_arch = "hppa";
 #elif (__riscv || __riscv__) && __riscv_xlen == 64
 const char *tup_arch = "riscv64";
 #elif (__riscv || __riscv__) && __riscv_xlen == 32
--- End Message ---
--- Begin Message ---
Source: tup
Source-Version: 0.7.11-4
Done: Bastian Germann 

We believe that the bug you reported is fixed in the latest version of
tup, 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 1030...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Bastian Germann  (supplier of updated tup 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: Fri, 22 Dec 2023 01:11:31 +0100
Source: tup
Architecture: source
Version: 0.7.11-4
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Bastian Germann 
Closes: 37 1030553
Changes:
 tup (0.7.11-4) unstable; urgency=medium
 .
   * QA upload.
   * Drop emacs integration which fails the build.
   * Build with pcre2. (Closes: #37)
 .
   [ Helge Deller ]
   * Fix ftbfs on hppa. (Closes: #1030553)
Checksums-Sha1:
 e8923d501e3e222dfda6359fd3e5d45c227303ea 1786 tup_0.7.11-4.dsc
 de54d1e053f9621560ec561a95fea54cc286667c 11680 tup_0.7.11-4.debian.tar.xz
 382e2db789a895b6855739ab732a437d074f5881 5992 tup_0.7.11-4_source.buildinfo
Checksums-Sha256:
 eb38a649fe1c08ac29018ba2b2840668c6981829ea4e184f34be1aab0a3da27b 1786 
tup_0.7.11-4.dsc
 275e1d3a8a4ce7deaa06ce568a54c5f0ffef1b076b047ca68ebb543e947c8e30 11680 
tup_0.7.11-4.debian.tar.xz
 2b9ee47f9b6588beb57784ed3aedd98970b03068d26cea983bf9eacc93373697 5992 
tup_0.7.11-4_source.buildinfo
Files:
 9bc22798ec379a97c88ed7a38a1c9b32 1786 devel optional tup_0.7.11-4.dsc
 1da71158e9a5a019939b2452f61eb2ff 11680 devel optional 
tup_0.7.11-4.debian.tar.xz
 def9865a85a826ab2d545b7714f0418c 5992 devel optional 
tup_0.7.11-4_source.buildinfo

-BEGIN PGP SIGNATURE-

iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmWE1+sQHGJhZ2VAZGVi
aWFuLm9yZwAKCRAfXHqLRVZDFPJcDACrcQkHfPs2PbRgkRg6z/atVMMYGT/0VpbP
ER1EEJD47+fmXZAWc+KP+2Bw1CMvVHvojsEWhcseLO1tt67JXhkuLi6MCLWNk8GB
DGTF5QR5Z9zmOA922Z/vWV//4OFckTu1BYaFqncz1ZhXzdUfc+kDVgoPe6T6U10y
XVe4Z9piDn2Sb0ciK0JFwW/FQqYTBFEkHGdg1+a+RUOPzTmNEDf7yMwk289dn1mv
0S/d1FO0DUFPvrWTJtkXZTIRHhPE0zHkY/ExU4RfGoDjLde89rLwMXwR7hsupLR8
rQ83nQyRvVnZGsIVKRxdco6L3mGYUPwGLcS3ToqAYi6HAahKfUyaLeil3ASG3tB0
4hQmDAQMGYpN8qVLF6DKMDyvIyQpujQ5qKglfJAwFWHAMymOvk0SX0i+jS/GZ3jp
AFinHqq784N52BoHBMyUOqt5oSBiSXiZZXoJ/l0s0Kzc9lRH6IXPQYcHnzCZO5dc
7tYo7IEkHDy1nJuuZoIk0t9uvFuj9rs=
=Fpr7
-END PGP SIGNATURE End Message ---


Bug#999937: marked as done (tup: depends on obsolete pcre3 library)

2023-12-21 Thread Debian Bug Tracking System
Your message dated Fri, 22 Dec 2023 00:38:13 +
with message-id 
and subject line Bug#37: fixed in tup 0.7.11-4
has caused the Debian Bug report #37,
regarding tup: depends on obsolete pcre3 library
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.)


-- 
37: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=37
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: tup
Severity: important
User: matthew-pcre...@debian.org
Usertags: obsolete-pcre3

Dear maintainer,

Your package still depends on the old, obsolete PCRE3[0] libraries
(i.e. libpcre3-dev). This has been end of life for a while now, and
upstream do not intend to fix any further bugs in it. Accordingly, I
would like to remove the pcre3 libraries from Debian, preferably in
time for the release of Bookworm.

The newer PCRE2 library was first released in 2015, and has been in
Debian since stretch. Upstream's documentation for PCRE2 is available
here: https://pcre.org/current/doc/html/

Many large projects that use PCRE have made the switch now (e.g. git,
php); it does involve some work, but we are now at the stage where
PCRE3 should not be used, particularly if it might ever be exposed to
untrusted input.

This mass bug filing was discussed on debian-devel@ in
https://lists.debian.org/debian-devel/2021/11/msg00176.html

Regards,

Matthew [0] Historical reasons mean that old PCRE is packaged as
pcre3 in Debian 
--- End Message ---
--- Begin Message ---
Source: tup
Source-Version: 0.7.11-4
Done: Bastian Germann 

We believe that the bug you reported is fixed in the latest version of
tup, 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 999...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Bastian Germann  (supplier of updated tup 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: Fri, 22 Dec 2023 01:11:31 +0100
Source: tup
Architecture: source
Version: 0.7.11-4
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Bastian Germann 
Closes: 37 1030553
Changes:
 tup (0.7.11-4) unstable; urgency=medium
 .
   * QA upload.
   * Drop emacs integration which fails the build.
   * Build with pcre2. (Closes: #37)
 .
   [ Helge Deller ]
   * Fix ftbfs on hppa. (Closes: #1030553)
Checksums-Sha1:
 e8923d501e3e222dfda6359fd3e5d45c227303ea 1786 tup_0.7.11-4.dsc
 de54d1e053f9621560ec561a95fea54cc286667c 11680 tup_0.7.11-4.debian.tar.xz
 382e2db789a895b6855739ab732a437d074f5881 5992 tup_0.7.11-4_source.buildinfo
Checksums-Sha256:
 eb38a649fe1c08ac29018ba2b2840668c6981829ea4e184f34be1aab0a3da27b 1786 
tup_0.7.11-4.dsc
 275e1d3a8a4ce7deaa06ce568a54c5f0ffef1b076b047ca68ebb543e947c8e30 11680 
tup_0.7.11-4.debian.tar.xz
 2b9ee47f9b6588beb57784ed3aedd98970b03068d26cea983bf9eacc93373697 5992 
tup_0.7.11-4_source.buildinfo
Files:
 9bc22798ec379a97c88ed7a38a1c9b32 1786 devel optional tup_0.7.11-4.dsc
 1da71158e9a5a019939b2452f61eb2ff 11680 devel optional 
tup_0.7.11-4.debian.tar.xz
 def9865a85a826ab2d545b7714f0418c 5992 devel optional 
tup_0.7.11-4_source.buildinfo

-BEGIN PGP SIGNATURE-

iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmWE1+sQHGJhZ2VAZGVi
aWFuLm9yZwAKCRAfXHqLRVZDFPJcDACrcQkHfPs2PbRgkRg6z/atVMMYGT/0VpbP
ER1EEJD47+fmXZAWc+KP+2Bw1CMvVHvojsEWhcseLO1tt67JXhkuLi6MCLWNk8GB
DGTF5QR5Z9zmOA922Z/vWV//4OFckTu1BYaFqncz1ZhXzdUfc+kDVgoPe6T6U10y
XVe4Z9piDn2Sb0ciK0JFwW/FQqYTBFEkHGdg1+a+RUOPzTmNEDf7yMwk289dn1mv
0S/d1FO0DUFPvrWTJtkXZTIRHhPE0zHkY/ExU4RfGoDjLde89rLwMXwR7hsupLR8
rQ83nQyRvVnZGsIVKRxdco6L3mGYUPwGLcS3ToqAYi6HAahKfUyaLeil3ASG3tB0
4hQmDAQMGYpN8qVLF6DKMDyvIyQpujQ5qKglfJAwFWHAMymOvk0SX0i+jS/GZ3jp
AFinHqq784N52BoHBMyUOqt5oSBiSXiZZXoJ/l0s0Kzc9lRH6IXPQYcHnzCZO5dc
7tYo7IEkHDy1nJuuZoIk0t9uvFuj9rs=
=Fpr7
-END PGP SIGNATURE End Message ---


Processing of tup_0.7.11-4_source.changes

2023-12-21 Thread Debian FTP Masters
tup_0.7.11-4_source.changes uploaded successfully to localhost
along with the files:
  tup_0.7.11-4.dsc
  tup_0.7.11-4.debian.tar.xz
  tup_0.7.11-4_source.buildinfo

Greetings,

Your Debian queue daemon (running on host usper.debian.org)



tup_0.7.11-4_source.changes ACCEPTED into unstable

2023-12-21 Thread Debian FTP Masters
Thank you for your contribution to Debian.



Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 22 Dec 2023 01:11:31 +0100
Source: tup
Architecture: source
Version: 0.7.11-4
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Bastian Germann 
Closes: 37 1030553
Changes:
 tup (0.7.11-4) unstable; urgency=medium
 .
   * QA upload.
   * Drop emacs integration which fails the build.
   * Build with pcre2. (Closes: #37)
 .
   [ Helge Deller ]
   * Fix ftbfs on hppa. (Closes: #1030553)
Checksums-Sha1:
 e8923d501e3e222dfda6359fd3e5d45c227303ea 1786 tup_0.7.11-4.dsc
 de54d1e053f9621560ec561a95fea54cc286667c 11680 tup_0.7.11-4.debian.tar.xz
 382e2db789a895b6855739ab732a437d074f5881 5992 tup_0.7.11-4_source.buildinfo
Checksums-Sha256:
 eb38a649fe1c08ac29018ba2b2840668c6981829ea4e184f34be1aab0a3da27b 1786 
tup_0.7.11-4.dsc
 275e1d3a8a4ce7deaa06ce568a54c5f0ffef1b076b047ca68ebb543e947c8e30 11680 
tup_0.7.11-4.debian.tar.xz
 2b9ee47f9b6588beb57784ed3aedd98970b03068d26cea983bf9eacc93373697 5992 
tup_0.7.11-4_source.buildinfo
Files:
 9bc22798ec379a97c88ed7a38a1c9b32 1786 devel optional tup_0.7.11-4.dsc
 1da71158e9a5a019939b2452f61eb2ff 11680 devel optional 
tup_0.7.11-4.debian.tar.xz
 def9865a85a826ab2d545b7714f0418c 5992 devel optional 
tup_0.7.11-4_source.buildinfo

-BEGIN PGP SIGNATURE-

iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmWE1+sQHGJhZ2VAZGVi
aWFuLm9yZwAKCRAfXHqLRVZDFPJcDACrcQkHfPs2PbRgkRg6z/atVMMYGT/0VpbP
ER1EEJD47+fmXZAWc+KP+2Bw1CMvVHvojsEWhcseLO1tt67JXhkuLi6MCLWNk8GB
DGTF5QR5Z9zmOA922Z/vWV//4OFckTu1BYaFqncz1ZhXzdUfc+kDVgoPe6T6U10y
XVe4Z9piDn2Sb0ciK0JFwW/FQqYTBFEkHGdg1+a+RUOPzTmNEDf7yMwk289dn1mv
0S/d1FO0DUFPvrWTJtkXZTIRHhPE0zHkY/ExU4RfGoDjLde89rLwMXwR7hsupLR8
rQ83nQyRvVnZGsIVKRxdco6L3mGYUPwGLcS3ToqAYi6HAahKfUyaLeil3ASG3tB0
4hQmDAQMGYpN8qVLF6DKMDyvIyQpujQ5qKglfJAwFWHAMymOvk0SX0i+jS/GZ3jp
AFinHqq784N52BoHBMyUOqt5oSBiSXiZZXoJ/l0s0Kzc9lRH6IXPQYcHnzCZO5dc
7tYo7IEkHDy1nJuuZoIk0t9uvFuj9rs=
=Fpr7
-END PGP SIGNATURE-



powerline-taskwarrior is marked for autoremoval from testing

2023-12-21 Thread Debian testing autoremoval watch
powerline-taskwarrior 0.7.2-2 is marked for autoremoval from testing on 
2024-01-25

It (build-)depends on packages with these RC bugs:
1058256: powerline: FTBFS: ModuleNotFoundError: No module named 'imp'
 https://bugs.debian.org/1058256



This mail is generated by:
https://salsa.debian.org/release-team/release-tools/-/blob/master/mailer/mail_autoremovals.pl

Autoremoval data is generated by:
https://salsa.debian.org/qa/udd/-/blob/master/udd/testing_autoremovals_gatherer.pl



glogic is marked for autoremoval from testing

2023-12-21 Thread Debian testing autoremoval watch
glogic 2.6-6 is marked for autoremoval from testing on 2024-01-11

It is affected by these RC bugs:
1058575: glogic: Fails to start due AttributeError
 https://bugs.debian.org/1058575



This mail is generated by:
https://salsa.debian.org/release-team/release-tools/-/blob/master/mailer/mail_autoremovals.pl

Autoremoval data is generated by:
https://salsa.debian.org/qa/udd/-/blob/master/udd/testing_autoremovals_gatherer.pl



Bug#612010: marked as done (gs: Integer overflow breaks huge procedures)

2023-12-21 Thread Debian Bug Tracking System
Your message dated Thu, 21 Dec 2023 23:05:00 -0600
with message-id <7584204.DvuYhMxLoT@riemann>
and subject line Re: gs: Integer overflow breaks huge procedures
has caused the Debian Bug report #612010,
regarding gs: Integer overflow breaks huge procedures
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.)


-- 
612010: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=612010
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gs
Version: 7.06-1.1
Severity: normal
Tags: upstream

There's a problem with how gs handles procedure definitions. This works
fine:

(echo "1 dict dup /MaxOpStack 10 put setuserparams {"; \
 yes 1 | head -6 ; echo "} quit") | gs -q -dNODISPLAY -

However, this causes a very obscure rangecheck error:

(echo "1 dict dup /MaxOpStack 10 put setuserparams {"; \
 yes 1 | head -7 ; echo "} quit") | gs -q -dNODISPLAY -

And in fact any procedure definition of similar size will fail in the
same way.

I delved into the problem, and it seems that it's a simple overflow
problem: in iscan.c:658 gs tries to build a large array of size > 65536,
but, as seen in iref.h:370, object sizes are stored in a 16 bit integer. 
The allocation succeeds, but its size is wrong. Hence, trouble.

The Right Thing would be to support longer arrays, but failing that, at
least the size should be checked before allocation and a more sensible
diagnostic produced. I don't understand gs's internal workings well
enough to produce a patch, though.

And no, the problem does not occur only in pathological cases. Combine
autotrace, which generates very complex PS figures from bitmaps, with
html2ps, which embeds all figures into procedures, and the mess is
ready. That's how I encountered it.

-- System Information:
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux la.iki.fi 2.4.18 #1 Mon Jul 22 17:03:02 EEST 2002 i586
Locale: LANG=C, LC_CTYPE=fi_FI.ISO-8859-1

Versions of packages gs depends on:
ii  gs-common 0.3.3  Common files for different Ghostsc
ii  libc6 2.3.1-11   GNU C Library: Shared libraries an
ii  libgimpprint1 4.2.5-2Gimp-Print printer drivers - core 
ii  libpaper1 1.1.12 Library for handling paper charact
ii  libpng12-01.2.5-10   PNG library - runtime
ii  xlibs 4.2.1-5X Window System client libraries
ii  zlib1g1:1.1.4-9  compression library - runtime

-- no debconf information


--- End Message ---
--- Begin Message ---
On Sun, 18 May 2003 20:25:13 +0300 Lauri Alanko  wrote:
> Package: gs
> Version: 7.06-1.1
> Severity: normal
> Tags: upstream

This was fixed upstream in 2012. 
I tested the reported repro and got no errors.

-Steve

> 
> There's a problem with how gs handles procedure definitions. This works
> fine:
> 
> (echo "1 dict dup /MaxOpStack 10 put setuserparams {"; \
>  yes 1 | head -6 ; echo "} quit") | gs -q -dNODISPLAY -
> 
> However, this causes a very obscure rangecheck error:
> 
> (echo "1 dict dup /MaxOpStack 10 put setuserparams {"; \
>  yes 1 | head -7 ; echo "} quit") | gs -q -dNODISPLAY -
> 
> And in fact any procedure definition of similar size will fail in the
> same way.
> 
> I delved into the problem, and it seems that it's a simple overflow
> problem: in iscan.c:658 gs tries to build a large array of size > 65536,
> but, as seen in iref.h:370, object sizes are stored in a 16 bit integer. 
> The allocation succeeds, but its size is wrong. Hence, trouble.
> 
> The Right Thing would be to support longer arrays, but failing that, at
> least the size should be checked before allocation and a more sensible
> diagnostic produced. I don't understand gs's internal workings well
> enough to produce a patch, though.
> 
> And no, the problem does not occur only in pathological cases. Combine
> autotrace, which generates very complex PS figures from bitmaps, with
> html2ps, which embeds all figures into procedures, and the mess is
> ready. That's how I encountered it.
> 
> -- System Information:
> Debian Release: testing/unstable
> Architecture: i386
> Kernel: Linux la.iki.fi 2.4.18 #1 Mon Jul 22 17:03:02 EEST 2002 i586
> Locale: LANG=C, LC_CTYPE=fi_FI.ISO-8859-1
> 
> Versions of packages gs depends on:
> ii  gs-common 0.3.3  Common files for different 
Ghostsc
> ii  libc6 2.3.1-11   GNU C Library: Shared libraries 
an
> ii  libgimpprint1 4.2.5-2Gimp-Print printer drivers - 
core 
> ii  libpaper1  

Bug#1036869: O: ghostscript -- interpreter for the PostScript language and for PDF

2023-12-21 Thread Steven Robbins
On Mon, 24 Oct 2022 15:17:20 +0200 Jonas Smedegaard  wrote:

> I have orphaned the ghostscript package, due to lack of time.

I'm willing to take on -- and hopefully, share -- the ghostscript maintenance.
If anyone wants to team up, let me know!

-Steve



signature.asc
Description: This is a digitally signed message part.