Processed: libapache2-request-perl: description should include the names of the libraries

2023-06-12 Thread Debian Bug Tracking System
Processing control commands:

> tags -1 pending
Bug #850955 [libapache2-request-perl] libapache2-request-perl: description 
should include the names of the libraries
Added tag(s) pending.

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



Bug#850955: libapache2-request-perl: description should include the names of the libraries

2023-06-12 Thread Sebastiaan Couwenberg

Control: tags -1 pending

This is fixed in git:


https://salsa.debian.org/debian/libapreq2/-/commit/b450debda66bcf40de4c1053da642a8bd972a973

Kind Regards,

Bas

--
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1



Bug#490862: marked as done (HttpOnly support for APR::Request::Cookie)

2023-06-12 Thread Debian Bug Tracking System
Your message dated Tue, 13 Jun 2023 07:41:53 +0200
with message-id <49c6d6dc-38e7-3eeb-3027-a3ec8dfda...@xs4all.nl>
and subject line Re: HttpOnly support for APR::Request::Cookie
has caused the Debian Bug report #490862,
regarding HttpOnly support for APR::Request::Cookie
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.)


-- 
490862: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=490862
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libapache2-request-perl
Version: 2.08-4
Severity: wishlist

As best I can tell libapreq2 has no direct way to add the
HttpOnly flag to the cookies it sets.  Although browser support for this
feature is not universal, it is a useful measure to limit the impact of
cross-site scripting attacks in supported browsers.
http://msdn.microsoft.com/en-us/library/ms533046.aspx provides
some info on the syntax and support.

Thanks,
Robert Stone
diff -Naur libapreq2-2.08.old/glue/perl/lib/Apache2/Cookie.pm libapreq2-2.08/glue/perl/lib/Apache2/Cookie.pm
--- libapreq2-2.08.old/glue/perl/lib/Apache2/Cookie.pm	2006-08-08 21:26:45.0 -0700
+++ libapreq2-2.08/glue/perl/lib/Apache2/Cookie.pm	2008-07-14 12:06:05.0 -0700
@@ -436,6 +436,20 @@
 
 
 
+=head2 httponly
+
+$cookie->httponly()
+$cookie->httponly($set)
+
+Get or set the HttpOnly flag for the cookie:
+
+$cookie->httponly(1);
+$is_HttpOnly = $cookie->httponly;
+$cookie->httponly(0);
+
+
+
+
 =head2 comment
 
 $cookie->comment()
diff -Naur libapreq2-2.08.old/glue/perl/xsbuilder/APR/Request/Cookie/Cookie.pod libapreq2-2.08/glue/perl/xsbuilder/APR/Request/Cookie/Cookie.pod
--- libapreq2-2.08.old/glue/perl/xsbuilder/APR/Request/Cookie/Cookie.pod	2006-08-08 21:26:45.0 -0700
+++ libapreq2-2.08/glue/perl/xsbuilder/APR/Request/Cookie/Cookie.pod	2008-07-14 12:08:26.0 -0700
@@ -117,6 +117,8 @@
 
 =item -secure
 
+=item -httponly
+
 =item -version
 
 =item -path
@@ -235,6 +237,28 @@
 
 
 
+=head2 httponly
+
+$cookie->httponly()
+$cookie->httponly($set)
+
+
+Get/set the cookie's HttpOnly flag.
+
+=for example begin
+
+$cookie->httponly(1);
+ok $cookie->httponly == 1;
+
+=for example end
+
+=for example_testing
+$cookie->httponly(0);
+is $cookie->httponly, 0, "HttpOnly";
+
+
+
+
 =head2 version
 
 $cookie->version()
diff -Naur libapreq2-2.08.old/glue/perl/xsbuilder/APR/Request/Cookie/Cookie.xs libapreq2-2.08/glue/perl/xsbuilder/APR/Request/Cookie/Cookie.xs
--- libapreq2-2.08.old/glue/perl/xsbuilder/APR/Request/Cookie/Cookie.xs	2006-08-08 21:26:45.0 -0700
+++ libapreq2-2.08/glue/perl/xsbuilder/APR/Request/Cookie/Cookie.xs	2008-07-14 12:09:34.0 -0700
@@ -74,6 +74,23 @@
 RETVAL
 
 UV
+httponly(obj, val=NULL)
+APR::Request::Cookie obj
+SV *val
+
+  CODE:
+RETVAL = apreq_cookie_is_httponly(obj);
+if (items == 2) {
+if (SvTRUE(val))
+apreq_cookie_httponly_on(obj);
+else
+apreq_cookie_httponly_off(obj);
+}
+
+  OUTPUT:
+RETVAL
+
+UV
 version(obj, val=0)
 APR::Request::Cookie obj
 UV val
diff -Naur libapreq2-2.08.old/include/apreq_cookie.h libapreq2-2.08/include/apreq_cookie.h
--- libapreq2-2.08.old/include/apreq_cookie.h	2006-08-08 21:26:44.0 -0700
+++ libapreq2-2.08/include/apreq_cookie.h	2008-07-14 11:44:17.0 -0700
@@ -106,6 +106,27 @@
 APREQ_FLAGS_OFF(c->flags, APREQ_COOKIE_SECURE);
 }
 
+/** @return 1 if the HttpOnly flag is set, 0 otherwise. */
+static APR_INLINE
+unsigned apreq_cookie_is_httponly(const apreq_cookie_t *c) {
+return APREQ_FLAGS_GET(c->flags, APREQ_COOKIE_HTTPONLY);
+}
+
+/** Sets the cookie's HttpOnly flag, meaning it is not
+ *  accessible through client-side script in supported
+ *  browsers.
+ */
+static APR_INLINE
+void apreq_cookie_httponly_on(apreq_cookie_t *c) {
+APREQ_FLAGS_ON(c->flags, APREQ_COOKIE_HTTPONLY);
+}
+
+/** Turns off the cookie's HttpOnly flag. */
+static APR_INLINE
+void apreq_cookie_httponly_off(apreq_cookie_t *c) {
+APREQ_FLAGS_OFF(c->flags, APREQ_COOKIE_HTTPONLY);
+}
+
 
 /** @return 1 if the taint flag is set, 0 otherwise. */
 static APR_INLINE
diff -Naur libapreq2-2.08.old/include/apreq.h libapreq2-2.08/include/apreq.h
--- libapreq2-2.08.old/include/apreq.h	2006-08-08 21:26:44.0 -0700
+++ libapreq2-2.08/include/apreq.h	2008-07-14 11:35:52.0 -0700
@@ -179,6 +179,19 @@
  */
 #define APREQ_COOKIE_SECURE_MASK1
 
+/**
+ * Cookie's HttpOnly Bit 
+ * @see 

Processed: tagging 389679

2023-06-12 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> tags 389679 + upstream
Bug #389679 [libapache2-mod-apreq2] libapache2-mod-apreq2: Segmentation Fault 
under mod_perl2
Added tag(s) upstream.
> thanks
Stopping processing here.

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



Processed: tagging 303304

2023-06-12 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> tags 303304 + upstream
Bug #303304 [libapache2-request-perl] libapache2-request-perl: Dies complaining 
uploads cannot be disabled(parser not found)
Added tag(s) upstream.
> thanks
Stopping processing here.

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



Processed: tagging 377019

2023-06-12 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> tags 377019 + upstream
Bug #377019 [libapache2-request-perl] libapache2-request-perl: dies with 
uninformative error message
Added tag(s) upstream.
> thanks
Stopping processing here.

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



Bug#560014: marked as done (Installing libapache2-mod-apreq2 should enable the apreq module)

2023-06-12 Thread Debian Bug Tracking System
Your message dated Tue, 13 Jun 2023 07:29:05 +0200
with message-id 
and subject line Re: Installing libapache2-mod-apreq2 should enable the apreq 
module
has caused the Debian Bug report #560014,
regarding Installing libapache2-mod-apreq2 should enable the apreq module
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.)


-- 
560014: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=560014
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libapache2-mod-apreq2
Version: 2.08-5+b1

Installing this package causes the Apache2 module apreq to be
installed in /etc/apache2/mods-available, as it should, but does not
enable the installed module, with the result that it can't be used.
This is exacerbated by the uninformative error message that is
generated when attempting to use the module: the Apache2 error log
will contain something like:

/usr/sbin/apache2: symbol lookup error:
/usr/lib/perl5/auto/APR/Request/Apache2/Apache2.so: undefined symbol:
apreq_handle_apache2

This can be fixed by adding a post-installation script that enables
the module.  For example:

#!/bin/sh -e

case "$1" in
configure|upgrade)
a2enmod apreq
invoke-rc.d apache2 restart
;;

abort-upgrade|abort-remove|abort-deconfigure)
;;

*)
echo "postinst called with unknown argument '$1'" >&2
exit 1
;;
esac

#DEBHELPER#

exit 0


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

Version: 2.13-2

On Tue, 8 Dec 2009 10:04:31 + Mike Taylor wrote:

This can be fixed by adding a post-installation script that enables
the module.


This is done by dh_apache2 since 2.13-2.

Kind Regards,

Bas

--
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1--- End Message ---


Processed: tagging 407780

2023-06-12 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> tags 407780 + upstream
Bug #407780 [libapreq2] libapreq2: apreq_body doesn't work as expected when 
body like "a=1&==3" is passed
Added tag(s) upstream.
> thanks
Stopping processing here.

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



xchain is marked for autoremoval from testing

2023-06-12 Thread Debian testing autoremoval watch
xchain 1.0.1-10 is marked for autoremoval from testing on 2023-06-26

It is affected by these RC bugs:
1033514: xchain: autopkgtest fails: xvfb-run: command not found
 https://bugs.debian.org/1033514



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



granite-7_7.2.0-1_source.changes ACCEPTED into unstable

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



Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 12 Jun 2023 17:07:32 -0400
Source: granite-7
Architecture: source
Version: 7.2.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Boyuan Yang 
Changes:
 granite-7 (7.2.0-1) unstable; urgency=medium
 .
   * QA upload.
   * Upload to unstable.
Checksums-Sha1:
 c1c56eb76604b5ba2048dd4f844db92c4f9f53da 2238 granite-7_7.2.0-1.dsc
 6cc002d6089b0909d771ae927106d1864ceb4b1e 385952 granite-7_7.2.0.orig.tar.gz
 f90f3283f2024a3984c95e802fb8bafa9316aa0b 7300 granite-7_7.2.0-1.debian.tar.xz
 05dc7ad633a624044746761a935db408a7037b33 15781 
granite-7_7.2.0-1_amd64.buildinfo
Checksums-Sha256:
 0da24cf7f8b5c01f4021c29c892da849423628bb4c5c4cb10ff0483c3ff1804c 2238 
granite-7_7.2.0-1.dsc
 474b1ce3275e4065f48cc11b8bedaa6d976af0fb9b73c795300659d06ef3beef 385952 
granite-7_7.2.0.orig.tar.gz
 08ee8fc58c9561dba5e001d7856c2a802920b20f8e8d8a0e865b587bf26f06c5 7300 
granite-7_7.2.0-1.debian.tar.xz
 755061fb570d1b7f4858a22919fe374b967de356f817d7e0eb403fc5df8f7d67 15781 
granite-7_7.2.0-1_amd64.buildinfo
Files:
 9596331a798ef5f74638acba313f370f 2238 libs optional granite-7_7.2.0-1.dsc
 e5be721fe173dd1f6345bfbaf9f664b2 385952 libs optional 
granite-7_7.2.0.orig.tar.gz
 8f228a0bc2dfb7df4deaa1f3682b30a4 7300 libs optional 
granite-7_7.2.0-1.debian.tar.xz
 ba16fd2254f9ea43bd36c6a791955b5a 15781 libs optional 
granite-7_7.2.0-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEfncpR22H1vEdkazLwpPntGGCWs4FAmSHib8ACgkQwpPntGGC
Ws6uBw/6Ap6zqitVPoXWfgf56yZGf/a4HDayNbmppEREdLyu9EdXmTysqX0ppu73
aFR3BDZ73YjDBd6M48YgG6ua/Aqvgz0FjPZveDDpwnzvMSGy3I5sobH720zACZcW
2tdL99OA8lBu+A67wkN5i3kUbu/TDTnOUN1E3bMwhNNpjUYvgrz8k0qIQMpiiFiP
utDDMqKpEJLt0KdqJKnCc0ElUCE2bvUTGEaJovcmR2QbN+EVVRLZoZmvT3WShLU6
bhhjqK7oSMbYz+yxjIJeel+BhgZ0ecJpw+i17/M3Y8NQEtbl61OFmFEsJzDWLWBp
Xlxo2x5y5PuET6sDnMAR8sFB/xT751+TJkD+VITjHINqdMh6qX9S/PgVdkPFMVQo
7pVcid3lj5noK1c2IvmHQFqHAzhhrb3peNTJT837sm9xlogj55l3IpLH0fWTWHOT
vaHNJTnKq9omw6z1pIKbSMhbabu9NmZyD1KkcyX74f46FdvMa9orQGOJLjKlatSE
PcMBqUzHdCpT9J+NKwoorMaf/ZhS1UUMa4GZ57T+/xqPYJxto4zigYLq/N55TIYl
RQ0RNRuv5GnAmDO8fAmShtz2DfeNxb72fNqoknnAo/VSgwcrcsXAzgN0NoXQA/MV
xjg/LhYuGi+ES9RzHHtGaDZGEPZs+jph2n/ov20LyK1XpEwuue4=
=4l+s
-END PGP SIGNATURE-



Processing of granite-7_7.2.0-1_source.changes

2023-06-12 Thread Debian FTP Masters
granite-7_7.2.0-1_source.changes uploaded successfully to localhost
along with the files:
  granite-7_7.2.0-1.dsc
  granite-7_7.2.0.orig.tar.gz
  granite-7_7.2.0-1.debian.tar.xz
  granite-7_7.2.0-1_amd64.buildinfo

Greetings,

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



ifhp_3.5.20-19_source.changes ACCEPTED into unstable

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



Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 12 Jun 2023 23:53:08 +0530
Source: ifhp
Architecture: source
Version: 3.5.20-19
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Nilesh Patra 
Changes:
 ifhp (3.5.20-19) unstable; urgency=medium
 .
   * QA Upload.
   * Add options to configure to support cross-building
   * Ignore blhc failure due to -D_FORTIFY_SOURCE=2 in salsa-ci
   * Add comment in d/rules to justify configure option change
Checksums-Sha1:
 4c70ef4f5a3703b1cc7d656135eebeb9f762334c 1232 ifhp_3.5.20-19.dsc
 fc838065314351391a0cb4522b5485dbb2e765ce 92420 ifhp_3.5.20-19.debian.tar.xz
 2013151d88927790c0c9b5fc494854f33340b843 6755 ifhp_3.5.20-19_amd64.buildinfo
Checksums-Sha256:
 8c494e6ce8ca77e9bbde81519c2533cfb1c930a58e97a5be8c364e07e1d45774 1232 
ifhp_3.5.20-19.dsc
 f202fc6d8f5c4ea94cb318ceb164965737fc59edbc157688ed8c41d46c32c14e 92420 
ifhp_3.5.20-19.debian.tar.xz
 dcdb4de3bfd4c786e577f8a564ccfab6a04b99d8a6fa4af0d1f8a53087e7de74 6755 
ifhp_3.5.20-19_amd64.buildinfo
Files:
 fb3dded8654746d4c6982e8685f28bf9 1232 net optional ifhp_3.5.20-19.dsc
 c7f4ef66cd3de2387f1eff06eba110ab 92420 net optional 
ifhp_3.5.20-19.debian.tar.xz
 d4523c6503809098ddc5d6f809c78595 6755 net optional 
ifhp_3.5.20-19_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iHUEARYIAB0WIQSglbZu4JAkvuai8HIqJ5BL1yQ+2gUCZIdjqQAKCRAqJ5BL1yQ+
2j8KAQCmqo/iyXirA+mZc6X1ruxD8AmWN5maWmZArrjiscZFHQD/XqAbRF51kJXY
bBrlhWUzwNkNPaA7c3IspClAHyAl5gw=
=gq22
-END PGP SIGNATURE-



Processing of ifhp_3.5.20-19_source.changes

2023-06-12 Thread Debian FTP Masters
ifhp_3.5.20-19_source.changes uploaded successfully to localhost
along with the files:
  ifhp_3.5.20-19.dsc
  ifhp_3.5.20-19.debian.tar.xz
  ifhp_3.5.20-19_amd64.buildinfo

Greetings,

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



Bug#1037374: giggle: build-depends on transitional package libgdk-pixbuf2.0-dev

2023-06-12 Thread Simon McVittie
Source: giggle
Version: 0.7-5
Severity: important
Tags: trixie sid
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: split-gdk-pixbuf

This package Build-Depends on libgdk-pixbuf2.0-dev.

In Debian 11, libgdk-pixbuf2.0-dev was split into two packages:

- libgdk-pixbuf-2.0-dev contains the supported gdk-pixbuf-2.0 library

- libgdk-pixbuf-xlib-2.0-dev contains the deprecated, unmaintained
  Xlib integration layer, gdk-pixbuf-xlib-2.0

If this package only requires functionality from gdk-pixbuf-2.0.pc
and , please update the build-dependency to
libgdk-pixbuf-2.0-dev.

If it also requires the Xlib integration gdk-pixbuf-xlib-2.0.pc and
 (unlikely), then you can also build-depend on
libgdk-pixbuf-xlib-2.0-dev until the package can be updated to remove
that requirement.

libgdk-pixbuf-2.0-dev was present in both Debian 11 and Debian 12, so
it is not necessary to have a "| libgdk-pixbuf2.0-dev" alternative
dependency, even for packages that are expected to be backported.

We should remove the libgdk-pixbuf2.0-dev transitional package during
the Debian 13 'trixie' cycle, so this bug is likely to become RC later.

Thanks,
smcv