pylint-django is marked for autoremoval from testing
pylint-django 2.0.13-4 is marked for autoremoval from testing on 2024-12-21 It (build-)depends on packages with these RC bugs: 1085136: python3-mongomock: It no longer seems to work with the current pymongo https://bugs.debian.org/1085136 For more information on the autoremoval process, including hints to prevent autoremoval can be found on the wiki: https://wiki.debian.org/Autoremoval 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#574669: marked as done (asterisk-prompt-es-co: adjust to asterisk "1.6.0" layout)
Your message dated Thu, 28 Nov 2024 08:34:15 + with message-id and subject line Bug#574669: fixed in asterisk-prompt-es-co 0.20070403-4 has caused the Debian Bug report #574669, regarding asterisk-prompt-es-co: adjust to asterisk "1.6.0" layout 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.) -- 574669: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=574669 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: asterisk-prompt-es-co Version: 0.20070403-1 Severity: wishlist Tags: patch I would like to allow packaging more than one format of the same prompts in a separate package. This means we can't have all different prompt packages conflict with each other. As a way to fix this, I decided to move all the prompts to /usr/share/asterisk/sounds/xx_YY_Something rather than a simple /usr/share/asterisk/sounds/xx , and make that 'xx' a symlink. See: http://svn.debian.org/viewsvn/pkg-voip?view=rev&revision=8224 http://svn.debian.org/viewsvn/pkg-voip?view=rev&revision=8219 Note that this patch removes the old Asterisk 1.2 compatibility symlinks. Do you still need them? Attached a patch to fix the packaging. I'll also note that: 1. The package has a number of lintian warnings. Seem rather simple to fix. 2. It seems like a good candidate to being maintained by the pkg-voip team. -- Tzafrir Cohen icq#16849755 jabber:tzafrir.co...@xorcom.com +972-50-7952406 mailto:tzafrir.co...@xorcom.com http://www.xorcom.com iax:gu...@local.xorcom.com/tzafrir diff -u asterisk-prompt-es-co-0.20070403/debian/changelog asterisk-prompt-es-co-0.20070403/debian/changelog --- asterisk-prompt-es-co-0.20070403/debian/changelog +++ asterisk-prompt-es-co-0.20070403/debian/changelog @@ -1,3 +1,12 @@ +asterisk-prompt-es-co (0.20070403-1.1) unstable; urgency=low + + * Non-maintainer upload. + * Moving files to /usr/share/asterisk/sounds/es_CO_f_Avatar + * sounds/es is now a symlink + * Removed old Asterisk 1.2 compatibility links. + + -- Tzafrir Cohen Sat, 20 Mar 2010 01:35:57 +0200 + asterisk-prompt-es-co (0.20070403-1) unstable; urgency=low * Removed debian/ from .orig.tar.gz diff -u asterisk-prompt-es-co-0.20070403/debian/asterisk-prompt-es-co.install asterisk-prompt-es-co-0.20070403/debian/asterisk-prompt-es-co.install --- asterisk-prompt-es-co-0.20070403/debian/asterisk-prompt-es-co.install +++ asterisk-prompt-es-co-0.20070403/debian/asterisk-prompt-es-co.install @@ -1,2 +1,2 @@ -*.gsm usr/share/asterisk/sounds/es -digits/*.gsm usr/share/asterisk/sounds/es/digits +*.gsm usr/share/asterisk/sounds/es_CO_f_Avatar +digits/*.gsm usr/share/asterisk/sounds/es_CO_f_Avatar/digits reverted: --- asterisk-prompt-es-co-0.20070403/debian/asterisk-prompt-es-co.links +++ asterisk-prompt-es-co-0.20070403.orig/debian/asterisk-prompt-es-co.links @@ -1 +0,0 @@ -usr/share/asterisk/sounds/es/digits usr/share/asterisk/sounds/digits/es only in patch2: unchanged: --- asterisk-prompt-es-co-0.20070403.orig/debian/postinst +++ asterisk-prompt-es-co-0.20070403/debian/postinst @@ -0,0 +1,45 @@ +#! /bin/sh + +set -e + +# summary of how this script can be called: +#* `configure' +#* `abort-upgrade' +#* `abort-remove' `in-favour' +# +#* `abort-deconfigure' `in-favour' +#`removing' +# + +SYMLINK=/usr/share/asterisk/sounds/es +TARGET=es_CO_f_Avatar + + +case "$1" in +configure) +if [ ! -d "$SYMLINK" ]; then + if [ -L "$SYMLINK" ]; then + # dandling symlink? symlink to a file? kill it + rm -f "$SYMLINK" + fi + ln -s "$TARGET" "$SYMLINK" + fi +;; + +abort-upgrade|abort-remove|abort-deconfigure) +;; + +*) +echo "postinst called with unknown argument \`$1'" >&2 +exit 1 +;; +esac + +# dh_installdeb will replace this with shell code automatically +# generated by other debhelper scripts. + +#DEBHELPER# + +exit 0 + + only in patch2: unchanged: --- asterisk-prompt-es-co-0.20070403.orig/debian/postrm +++ asterisk-prompt-es-co-0.20070403/debian/postrm @@ -0,0 +1,11 @@ +#! /bin/sh -e + +SYMLINK=/usr/share/asterisk/sounds/es +TARGET=es_CO_f_Avatar + +if [ ! -d "$SYMLINK" ] && [ -L "$SYMLINK" ]; then +# dandling symlink? symlink to a file? kill it +rm -f "$SYMLINK" +fi + +#DEBHELPER# --- End Message --- --- Begin Message --- Source: asterisk-prompt-es-co Source-Version: 0.20070403-4 Done: Petter Reinholdtsen We believe that the bug you reported is fixed in the latest version of asterisk-prompt-es-co, which is due to be installed in the Debian FTP archive. A su
Bug#1075576: marked as done (tinydyndns: ftbfs with GCC-14)
Your message dated Thu, 28 Nov 2024 09:06:09 + with message-id and subject line Bug#1075576: fixed in tinydyndns 0.4.2.debian1-4 has caused the Debian Bug report #1075576, regarding tinydyndns: ftbfs with GCC-14 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.) -- 1075576: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075576 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:tinydyndns Version: 0.4.2.debian1-3 Severity: important Tags: sid trixie User: debian-...@lists.debian.org Usertags: ftbfs-gcc-14 [This bug is targeted to the upcoming trixie release] Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-14/g++-14, but succeeds to build with gcc-13/g++-13. The severity of this report will be raised before the trixie release. The full build log can be found at: http://qa-logs.debian.net/2024/07/01/tinydyndns_0.4.2.debian1-3_unstable_gccexp.log The last lines of the build log are at the end of this report. To build with GCC 14, either set CC=gcc-14 CXX=g++-14 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-14/porting_to.html [...] |^~ ./compile response.c ./compile dd.c ./choose c trydrent direntry.h1 direntry.h2 > direntry.h response.c:52:45: warning: argument 2 of type ‘const char[2]’ with mismatched bound [-Warray-parameter=] 52 | int response_query(const char *q,const char qtype[2],const char qclass[2]) | ~~~^~~~ In file included from response.c:4: response.h:9:40: note: previously declared as ‘const char *’ 9 | extern int response_query(const char *,const char *,const char *); |^~~~ response.c:52:65: warning: argument 3 of type ‘const char[2]’ with mismatched bound [-Warray-parameter=] 52 | int response_query(const char *q,const char qtype[2],const char qclass[2]) | ~~~^ response.h:9:53: note: previously declared as ‘const char *’ 9 | extern int response_query(const char *,const char *,const char *); | ^~~~ response.c:73:46: warning: argument 2 of type ‘const char[2]’ with mismatched bound [-Warray-parameter=] 73 | int response_rstart(const char *d,const char type[2],uint32 ttl) | ~~~^~~ response.h:18:41: note: previously declared as ‘const char *’ 18 | extern int response_rstart(const char *,const char *,uint32); | ^~~~ response.c:112:29: warning: argument 1 of type ‘const char[2]’ with mismatched bound [-Warray-parameter=] 112 | void response_id(const char id[2]) | ~~~^ response.h:12:25: note: previously declared as ‘const char *’ 12 | extern void response_id(const char *); | ^~~~ dd.c:4:44: warning: argument 3 of type ‘char[4]’ with mismatched bound [-Warray-parameter=] 4 | int dd(const char *q,const char *base,char ip[4]) | ~^ In file included from dd.c:2: dd.h:4:41: note: previously declared as ‘char *’ 4 | extern int dd(const char *,const char *,char *); | ^~ ./choose c trysysel select.h1 select.h2 > select.h ./compile chkshsgr.c ( ( ./compile trylsock.c && \ ./load trylsock -lsocket -lnsl ) >/dev/null 2>&1 \ && echo -lsocket -lnsl || exit 0 ) > socket.lib ./compile walldns-conf.c chkshsgr.c: In function ‘main’: chkshsgr.c:10:19: error: passing argument 2 of ‘getgroups’ from incompatible pointer type [-Wincompatible-pointer-types] 10 | if (getgroups(1,x) == 0) if (setgroups(1,x) == -1) _exit(1); | ^ | | | short int * In file included from /usr/include
asterisk-prompt-es-co_0.20070403-4_source.changes ACCEPTED into unstable
Thank you for your contribution to Debian. Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 28 Nov 2024 08:54:50 +0100 Source: asterisk-prompt-es-co Architecture: source Version: 0.20070403-4 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Petter Reinholdtsen Closes: 574669 Changes: asterisk-prompt-es-co (0.20070403-4) unstable; urgency=medium . * QA upload. . * Added d/gbp.conf to describe branch layout. * Updated vcs in d/control to Salsa. * Updated d/gbp.conf to enforce the use of pristine-tar. * Use wrap-and-sort -at for debian control files. * Bump debhelper from deprecated 9 to 13. * Set debhelper-compat version in Build-Depends. * Adjusted installed file layout and dropped Asterisk 1.2 compatibility link (Closes: #574669). * Use versioned GPL in d/copyright. Checksums-Sha1: 8f875be5315616133b7721eaf348303b3311afc7 2000 asterisk-prompt-es-co_0.20070403-4.dsc ead846fe942d839c8f0f7e1db81ac1e476c3090b 2940 asterisk-prompt-es-co_0.20070403-4.debian.tar.xz 0cdd1b3d188d0aec83f8c3179a08fcd43904fdf5 6447 asterisk-prompt-es-co_0.20070403-4_source.buildinfo Checksums-Sha256: 90638248100bcb2e886feb5f0945329660b7ab7f4d90edbe70b8071c7d1d1241 2000 asterisk-prompt-es-co_0.20070403-4.dsc c882ad7e18bb9e0b964edb085b986df79ec639988f9373548384b36f336b805c 2940 asterisk-prompt-es-co_0.20070403-4.debian.tar.xz a294ab206d56d162070a78fcfb17b1c6b869639990bf83c60a17b7203f4f13c0 6447 asterisk-prompt-es-co_0.20070403-4_source.buildinfo Files: 4637d551e8996100620d0db87610d7be 2000 comm optional asterisk-prompt-es-co_0.20070403-4.dsc 4ce95027576a488fc33f759b6d0ed4af 2940 comm optional asterisk-prompt-es-co_0.20070403-4.debian.tar.xz f8e79baff759ee1e2d8ef634b559c0de 6447 comm optional asterisk-prompt-es-co_0.20070403-4_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEERqLf4owIeylOb9kkgSgKoIe6+w4FAmdIIiAACgkQgSgKoIe6 +w5Q6xAAo2ngMXxdmqhZZcCS0NOCSvMf9kZTIDFMkIQh0Dbo8KO1n9yK0EADmKKV etDeMm/2yUEQfA7Ob6c07AmLr6015NemMnD4fXZPZlbwoE4pzqewUiyo3/9DbH5+ vrXLSYaTubS5KdbKTxBrRwsJWbojhYbyTkAJ39+6mI2hWsLUeZgpM6RSN1Czf4Zx 9PCIG4/bL9ctz5TZ9LJ4fMeh0ytFdwLOMduPL9OBUN2c159zpXqFhrarW6Z8gwan 0OAP4SmAY5RFKWU9XckrB0QicMcTCfty3yBRun0Q+lNPwqUi1/ikScYCHz2JLtX0 4psuK1wT/yYjXODFcmYpSpzxbm1QtJaSop0UskT29KlIs21mywgPD5oOjtbTHLIv uQiMWXa+1DD8jwLfxryxmfQx5nmWGz1YfDINHLw3CeRiksSN+US4N07Mfeqkh90q q4C78xePhm1ysGPuhlwlAA/r4X51T7o98TNnYHceluyVfUmZDbtpcBzVOu9Q+Qp0 Gbe0cX3i3sAcXrB53gnEIkuzJHW7JeYvUJigQOz84MuE4oiP3wKrDOK9cq9MUZPH fR3gpy7E/WKRVaa1hhRHJZZBykpNxoJxPlOtI0B6hYM9jmFmthJHfkgHa45Y9b4H DL+QiV+SIfbLOKjy1lljzGJ2h1Af7pyOh8V/NASnId5lrUMm9sg= =k4l5 -END PGP SIGNATURE- pgpM6x0jqBpLj.pgp Description: PGP signature
tinydyndns_0.4.2.debian1-4_source.changes ACCEPTED into unstable
Thank you for your contribution to Debian. Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 28 Nov 2024 09:50:29 +0100 Source: tinydyndns Architecture: source Version: 0.4.2.debian1-4 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Andreas Beckmann Closes: 1075576 Changes: tinydyndns (0.4.2.debian1-4) unstable; urgency=medium . * QA upload. * Fix building with -Werror=incompatible-pointer-types. (Closes: #1075576) Checksums-Sha1: 654cceb1b159299298c28608ecbf6cfdd08f86d5 1926 tinydyndns_0.4.2.debian1-4.dsc a874d3ba2964eb756d5604697a2cf88927e01b29 5400 tinydyndns_0.4.2.debian1-4.debian.tar.xz ea0b67fd5a54429c1ed92193b84265de08bd1c72 5554 tinydyndns_0.4.2.debian1-4_source.buildinfo Checksums-Sha256: 984d287eda6054b4faeb3d6cbfbb6217aea0ca98d8548d10049fdc1f7681a0f1 1926 tinydyndns_0.4.2.debian1-4.dsc b46f030d57d1cbde88ab5831b98ff6050050e58d594fdc9073753cce641ae9c8 5400 tinydyndns_0.4.2.debian1-4.debian.tar.xz 0dc8100260516b662e4e7f27368cb84e9175df9b1a44ad476a8016860ad2f9ac 5554 tinydyndns_0.4.2.debian1-4_source.buildinfo Files: 66bff861f6b787cfbea0ddae0e4be164 1926 net optional tinydyndns_0.4.2.debian1-4.dsc c918a40d4de533977e53f77494fc72f2 5400 net optional tinydyndns_0.4.2.debian1-4.debian.tar.xz ad0c6f2b73f03e20195d419ac7fd6521 5554 net optional tinydyndns_0.4.2.debian1-4_source.buildinfo -BEGIN PGP SIGNATURE- iQJEBAEBCAAuFiEE6/MKMKjZxjvaRMaUX7M/k1np7QgFAmdIL40QHGFuYmVAZGVi aWFuLm9yZwAKCRBfsz+TWentCDNfD/45RmXpmGRF8x7fKNe/kxZHmtNyR6A2iaZM fbN26jWtFD6yAid9KzE2NYg5idWH2a7YAcHKzACT3F/qxXQVUYeUY55r/W2pQLgQ +ArvwwkF2QlOw1ED6dwmu8gHkaqJMfCQcOKoQziIy/lrhSl0B5I1ZPrBt9Sq+kPv 3BFvVJbMqEVU85QQC0hjEDFa1C/GVAM95ocVe8ZLuxnGS17M5mweKjSOsk0SncG1 YfDsUbM8MBJvKV6o2EqGmuam9CEaN4G01NF2y9wziI812sjfXbruKcn3+/uZ/+6p 8IecNhPltY84DoUA0WZqIvqHacl+DkKEizdtQZ5aU9sdmSeCpWRK+LZMjST4i3Hs HzTT7NkRF0xsa9NKz++3z82pNRyXlH78Hzqm1VfsqNk9i4mwvOHclwsPjyB1zjKw pjh2gLji5eRCkwHBGvv7CPr7rZIVNpm9UVqL1ZbbdMe/a5yanl7QeqGIUTUlGrc9 JKcxvkgCEP/8wVFvM4rANBg4FIqLP5f0kahSeG8CU5VWNYr1Sr7p0SwcJAGRbWOX 7aTRVVdJgjyQqKs5UfMJlHoWcxEoaP22Dz5GEJaaT4YSQQJRLAMhtfWPW2hc9sXY ca4usg9eb0XPc+7P/dam7kXHeJT83smf8LhrKciGmNFk+Eff6yXRuDOSque6O43X wL+/AURe+Q== =OxKa -END PGP SIGNATURE- pgpRMFv12PhJS.pgp Description: PGP signature
Processing of tinydyndns_0.4.2.debian1-4_source.changes
tinydyndns_0.4.2.debian1-4_source.changes uploaded successfully to localhost along with the files: tinydyndns_0.4.2.debian1-4.dsc tinydyndns_0.4.2.debian1-4.debian.tar.xz tinydyndns_0.4.2.debian1-4_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)
Bug#1088586: pagure: move from twitter-bootstrap{3,4} to bootstrap-html (v5)
Package: pagure Severity: normal Tags: upstream User: debian-...@lists.debian.org Usertags: bootstrap-v5-migration Dear maintainer(s), Your package (build-)depends on one of the binary packages of src:twitter-bootstrap3 (fonts-glyphicons-halflings, libjs-bootstrap) and/or src:twitter-bootstrap4 (libjs-bootstrap4). Unfortunately, bootstrap versions 3 and 4 have been EOL'ed by upstream and it is difficult to provide security support for them. Projects depending on the unmaintained bootstrap versions are encouraged to migrate to bootstrap v5 (src:bootstrap-html). Please note that bootstrap v5 is not just a drop-in replacement, and some work on the upstream side may be needed. Upstream provides these migration guides that may help: https://getbootstrap.com/docs/5.3/migration/ https://getbootstrap.com/docs/4.6/migration/ Please, consider migrating to bootstrap v5.
elfrc_0.7-5_source.changes ACCEPTED into unstable
Thank you for your contribution to Debian. Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 28 Nov 2024 02:53:21 -0300 Source: elfrc Architecture: source Version: 0.7-5 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Mauro Nadalin Changes: elfrc (0.7-5) unstable; urgency=medium . * QA upload. * debian/copyright: Update packaging copyright information. * debian/salsa-ci.yml: Add to provide CI tests for Salsa. * debian/tests/control: Create autopkgtest. Checksums-Sha1: d69bb348c0a19abb29ffcad2ade1255b139620d4 1754 elfrc_0.7-5.dsc d999f8ce877d00ae2c9150d51b38bcd65fdcb1fb 4396 elfrc_0.7-5.debian.tar.xz 5d00f1bff61864c2291959d56318d45534c2f444 7337 elfrc_0.7-5_source.buildinfo Checksums-Sha256: 9e95417fe54c236b4b321e506c8b8132bd9dcee729e919fc67a7938b174c22ee 1754 elfrc_0.7-5.dsc 15b0f8f6a7680e01fa9186eead67cc846642ca2e6908c030e0cb8790dd6f7d52 4396 elfrc_0.7-5.debian.tar.xz 99b1685a3fe6ee687f264c1df92b4006aff42ea5b3b76381b463855861fc0f8f 7337 elfrc_0.7-5_source.buildinfo Files: 1af9e798293a9e7f90bdd3a55d480e38 1754 utils optional elfrc_0.7-5.dsc bd2f5fbc33e1b46065739df685fc027d 4396 utils optional elfrc_0.7-5.debian.tar.xz facdc645c2dc003f908337f034685342 7337 utils optional elfrc_0.7-5_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEtSLzkVnaB9053AsR9LqqgNsoukwFAmdIZwYACgkQ9LqqgNso ukwoqw//XKrHBWt8SaDsPlu7lVlFhnMA1Lh3r0xYfeURSfEWOMc7arqUwa7w9a1W SdCIfiyIU4F/NxXXd/7Ut/ZWATT7nnPbRRH98hW+mDAiRcip5GiGZGmALLEPP214 JClQxKzOqn0ghmZV9I87If+MZsyJi5J5xlJZ68SS48Fva4cbTpPBaghQX5i1+SqM fgJ6ZWA6+dQUGFckPCnmv1GiiQrSfNjL/T59OZ2o8vmTIsjJXqpfSEtZSdKhfPtk zoa4e1FS/B0ulYf1iXezt0T2pwPIJJo8aDCUzzPCF2tl01WgOU1wgJoC2D1Btty8 9P4BP5ukRQyMO+UTE0LOH3KhyHC9ZURASCoeedIIKgFBc/yES4VusYrF3Vzg9xPc v7qOxy+uELczPTJVdlHH7iag9uLjPrUF2TboCEV3cB/Haa/4fnehtP9gSNOlxyg9 b/lGJlm+uQW0VycJDqFql+OuLLce/ByVDReC2oPtJPiHffmimVpAcXQKex+OH1ci mGM6jd1rBCCKn3PflPcrDEUr5zzz7TZEMdhNSJ3qfo5SSPb5WN3/l5vkShgcBS5e WiBUTyt5YUiABJ57KZ9U1fA3mDRSxevhFXf4xCfwnmF5T3JW2RnNHzKCfFBc2qm6 sm39K+axfxOU/WCtu9Ra0J9FrwOQiS303Up72+FzB3vuP439kb8= =PUNx -END PGP SIGNATURE- pgpVi3_xYrjsl.pgp Description: PGP signature
Processing of elfrc_0.7-5_source.changes
elfrc_0.7-5_source.changes uploaded successfully to localhost along with the files: elfrc_0.7-5.dsc elfrc_0.7-5.debian.tar.xz elfrc_0.7-5_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)
libica_4.3.1-1_s390x.changes ACCEPTED into experimental
Thank you for your contribution to Debian. Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 28 Nov 2024 08:28:43 +0100 Source: libica Binary: libica-dev libica-utils libica-utils-dbgsym libica4 libica4-dbgsym Architecture: source s390x Version: 4.3.1-1 Distribution: experimental Urgency: medium Maintainer: Debian QA Group Changed-By: Petter Reinholdtsen Description: libica-dev - hardware cryptography support for IBM System z hardware (dev pack libica-utils - hardware cryptography support for Linux on z Systems (utils) libica4- hardware cryptography support for IBM System z hardware Changes: libica (4.3.1-1) experimental; urgency=medium . * QA upload. . * New upstream version 4.3.1. * Bring package in sync with Ubuntu: - Transition from libica3 to libica4. - Adjusting d/copyright. Checksums-Sha1: 95e41833f9ffdd70b60eed3c6d6bf3c620a67cd9 1980 libica_4.3.1-1.dsc 123a91286c4bab978d5c99fe5ade3c1ffc2bc713 576561 libica_4.3.1.orig.tar.gz 95fd9c086c6edd025cd873bc4747413c215aad27 8224 libica_4.3.1-1.debian.tar.xz 20cca2d4c7728d1cb446aa1410f1d7268de25e3b 27400 libica-dev_4.3.1-1_s390x.deb 69aaf8053bd08ea932adc9955d9d8869f205390f 36956 libica-utils-dbgsym_4.3.1-1_s390x.deb 46030f4b39b01abac1d1e02b35bdab7cd349a9f6 25360 libica-utils_4.3.1-1_s390x.deb 45f51c817097f0e75aab78d6a14911a63cb590ff 390900 libica4-dbgsym_4.3.1-1_s390x.deb bc7962e15ec3f8466a9385ab8d5738c73547c813 93908 libica4_4.3.1-1_s390x.deb 20be9336af75d107c54a752277b2a7db7e002c46 6697 libica_4.3.1-1_s390x.buildinfo Checksums-Sha256: 9e695c8e24fe0d2b3788fb54fb23187455f5e88a706fe8665c6bfceef0b7b1b5 1980 libica_4.3.1-1.dsc 5693fa8858941b68252a94c1f03f098e773b43cd56c10d6d3f15f24fdc623562 576561 libica_4.3.1.orig.tar.gz 6eb675e18f4efda5314c26bf9e3c54dc3eee268673414e3743c28bc9e362f93b 8224 libica_4.3.1-1.debian.tar.xz 5ca8036cf0e7850a5ff92ef6615f5f7bae0f879d144cb874e24e779a9369dedd 27400 libica-dev_4.3.1-1_s390x.deb f0ffcdd5110a1998a970ac12086121ab122ac401ddda50af0fe5b5db6c39e040 36956 libica-utils-dbgsym_4.3.1-1_s390x.deb 77722846bce668f642cdb39175daad0ff61aab0d096f4bd42654a73eb8d7944f 25360 libica-utils_4.3.1-1_s390x.deb 6045cc1ab79e1931db5f4da232a90fde32e79c36074d1e25c1701c50f9768383 390900 libica4-dbgsym_4.3.1-1_s390x.deb dee8c39c8f04e8d70605d0c1ab171bae4dfccbcbfd3905dfc4202af49b80e0fa 93908 libica4_4.3.1-1_s390x.deb caba9a7305dc46ad0ffbfacd8289a5d839efa91ec4721cb1ac6a0096debdca72 6697 libica_4.3.1-1_s390x.buildinfo Files: e2fd0803598c48d212cfe0791ff77306 1980 libs optional libica_4.3.1-1.dsc 13bf25e32b1060537b5242547d299369 576561 libs optional libica_4.3.1.orig.tar.gz 05d6812cf46d857c1eef4758397a7508 8224 libs optional libica_4.3.1-1.debian.tar.xz cb43e5cdddb33ef8f5c09199cbeb560b 27400 libdevel optional libica-dev_4.3.1-1_s390x.deb e8ffd82fa24c004c1e095a2acd0ae522 36956 debug optional libica-utils-dbgsym_4.3.1-1_s390x.deb 7ab6c398f2d146b8d7a3974ad3f01530 25360 libs optional libica-utils_4.3.1-1_s390x.deb 1032b4d741c5da6f290d82ffd067fffc 390900 debug optional libica4-dbgsym_4.3.1-1_s390x.deb 6f92754a68b16e9712142d26ac7f799e 93908 libs optional libica4_4.3.1-1_s390x.deb aa43731a78cd6658a4204548fbc54e21 6697 libs optional libica_4.3.1-1_s390x.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEERqLf4owIeylOb9kkgSgKoIe6+w4FAmdIj5kACgkQgSgKoIe6 +w70fQ/+L+vpWiN32m5Op3LPWfMVVTAYn9hHs+Fa2aUFod/VfP8q7Tdi8GetjBcS 51dnXume2IMh4ZPMO/Lc0hqSv03rblidCp/H+iUdnqkO2Qvs1E0n/xbchV37uXcG eI8rEKXZ1EnejJPLocyrIJE0H8FnM2nw0XLKb7bMmh5buVPlqvyJ9lhildq/L2tw Wm8MFdtLN3P95GEi1huWO7ma/D+1cA3Wp26CYV8AiG21WK58BOaQWnUquruQ2Hg4 gO1NgZoZYAiDqriRKq1b1X0wSsEZCTHpqNKh6QT9CologWZeKTHO2eL+gSiRDDMW a8FtMlfPdI5GQA3PbebIbRiIRm4btYBhysl1twm4nfm2qhTTHuaDgANWcGMiGLmJ U8dd4tF61GGZWKf5umwpxiCULG6sdVg5rL4Upvp8HhjVH9M/GNnsqUKIKMiQSqHV el0vkYm6IzECcZjZRT4hRhTTnGgqIe/Z1DDxcEv+O1vh84UCxsHOpoEtX81/WSQi +AUGHDXsZJ0GuUU5u623dc4/RjC1szQS9DdVIDhHyV05XGTMcLT9INYrjHWHxI5h vsove4o6OgaQwSOjmmJm+Vkn6QXaauxPnYhvL4NuiR+THDiK/9WtLSLhr+2FQqdu XiSNSYtmulYj2CCbJBLhElmS91SXIdTAUbja2B//bne5yu7QDbE= =3Zow -END PGP SIGNATURE- pgp5IIgZnPjAr.pgp Description: PGP signature
Processing of libica_4.3.1-1_amd64.changes
libica_4.3.1-1_amd64.changes uploaded successfully to localhost along with the files: libica_4.3.1-1.dsc libica_4.3.1.orig.tar.gz libica_4.3.1-1.debian.tar.xz libica_4.3.1-1_amd64.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)
Processing of asterisk-prompt-es-co_0.20070403-4_source.changes
asterisk-prompt-es-co_0.20070403-4_source.changes uploaded successfully to localhost along with the files: asterisk-prompt-es-co_0.20070403-4.dsc asterisk-prompt-es-co_0.20070403-4.debian.tar.xz asterisk-prompt-es-co_0.20070403-4_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)
Processing of libica_4.3.1-1_s390x.changes
libica_4.3.1-1_s390x.changes uploaded successfully to localhost along with the files: libica_4.3.1-1.dsc libica_4.3.1.orig.tar.gz libica_4.3.1-1.debian.tar.xz libica-dev_4.3.1-1_s390x.deb libica-utils-dbgsym_4.3.1-1_s390x.deb libica-utils_4.3.1-1_s390x.deb libica4-dbgsym_4.3.1-1_s390x.deb libica4_4.3.1-1_s390x.deb libica_4.3.1-1_s390x.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)
libica_4.3.1-1_s390x.changes is NEW
binary:libica4 is NEW. binary:libica4 is NEW. Your package has been put into the NEW queue, which requires manual action from the ftpteam to process. The upload was otherwise valid (it had a good OpenPGP signature and file hashes are valid), so please be patient. Packages are routinely processed through to the archive, and do feel free to browse the NEW queue[1]. If there is an issue with the upload, you will receive an email from a member of the ftpteam. If you have any questions, you may reply to this email. [1]: https://ftp-master.debian.org/new.html or https://ftp-master.debian.org/backports-new.html for *-backports pgp7fMC1p2mPQ.pgp Description: PGP signature
Bug#878858: marked as done (please drop transitional packages libfilesystem-ruby, libfilesystem-ruby1.8 and libfilesystem-ruby1.9.1)
Your message dated Thu, 28 Nov 2024 18:27:00 + with message-id and subject line Bug#1087388: Removed package(s) from unstable has caused the Debian Bug report #878858, regarding please drop transitional packages libfilesystem-ruby, libfilesystem-ruby1.8 and libfilesystem-ruby1.9.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.) -- 878858: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878858 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libfilesystem-ruby,libfilesystem-ruby1.8,libfilesystem-ruby1.9.1 Version: 0.5-5.1 Severity: normal user: qa.debian@packages.debian.org usertags: transitional Please drop the transitional packages libfilesystem-ruby, libfilesystem-ruby1.8 and libfilesystem-ruby1.9.1 for buster, as they have been released with jessie and stretch already. Thanks for maintaining ruby-filesystem! -- cheers, Holger signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Version: 0.5-8+rm Dear submitter, as the package ruby-filesystem has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1087388 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Thorsten Alteholz (the ftpmaster behind the curtain)--- End Message ---
Bug#202593: marked as done (snacc: Various changes, mostly to be able to compile CSTA (ECMA-180, ECMA-218))
Your message dated Thu, 28 Nov 2024 18:19:57 +
with message-id
and subject line Bug#1085565: Removed package(s) from unstable
has caused the Debian Bug report #202593,
regarding snacc: Various changes, mostly to be able to compile CSTA (ECMA-180,
ECMA-218)
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.)
--
202593: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=202593
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: snacc
Version: 1.3bbn-2.0.cats.4
Severity: normal
Tags: patch
I thought it was time to post our local changes.
I don't claim everything is necessarily the best solution.
The most important thing was probably teaching snacc about the CSTA
macros (well, actually they're the ROSE macros). There were also various
small bugfixes I don't exactly remember much about - sorry. And I know
I've gone back and forth about how to handle ANY DEFINED BY. At least
the current way seems to work, though it may be over-complicated from
the history.
diff -ausrN y/snacc-1.3bbn/c-examples/any/example.c
snacc-1.3bbn/c-examples/any/example.c
--- y/snacc-1.3bbn/c-examples/any/example.c Wed Jul 23 15:33:44 2003
+++ snacc-1.3bbn/c-examples/any/example.c Wed May 21 15:45:18 2003
@@ -81,7 +81,7 @@
}
size = sbuf.st_size;
-origData = (char*)malloc (size);
+origData = (char*)calloc(1, size);
if (read (fd, origData, size) != size)
{
perror ("main: read");
@@ -135,7 +135,7 @@
* value (may be larger than decoded value if encoding
* with indef lengths - so add 512 slush bytes)
*/
-encData = (char*) malloc (size + 512);
+encData = (char*) calloc(1, size + 512);
SBufInit (&encBuf, encData, size + 512);
SBufResetInWriteRvsMode (&encBuf);
diff -ausrN y/snacc-1.3bbn/c-examples/simple/expbuf-ex.c
snacc-1.3bbn/c-examples/simple/expbuf-ex.c
--- y/snacc-1.3bbn/c-examples/simple/expbuf-ex.cWed Jul 23 15:33:44 2003
+++ snacc-1.3bbn/c-examples/simple/expbuf-ex.c Wed May 21 15:45:18 2003
@@ -79,7 +79,7 @@
}
size = sbuf.st_size;
-origData = (char*)malloc (size);
+origData = (char*)calloc(1, size);
if (read (fd, origData, size) != size)
{
perror ("main: read");
diff -ausrN y/snacc-1.3bbn/c-examples/simple/minbuf-ex.c
snacc-1.3bbn/c-examples/simple/minbuf-ex.c
--- y/snacc-1.3bbn/c-examples/simple/minbuf-ex.cWed Jul 23 15:33:44 2003
+++ snacc-1.3bbn/c-examples/simple/minbuf-ex.c Wed May 21 15:45:18 2003
@@ -80,7 +80,7 @@
}
size = sbuf.st_size;
-origData = (char*)malloc (size);
+origData = (char*)calloc(1, size);
if (read (fd, origData, size) != size)
{
perror ("main: read");
@@ -127,7 +127,7 @@
* with indef lengths - so add 512 slush bytes)
*/
encBufSize = size + 512;
-encData = (char*) malloc (encBufSize);
+encData = (char*) calloc(1, encBufSize);
/*
* set 'buffer' up for writing by setting ptr
diff -ausrN y/snacc-1.3bbn/c-examples/simple/sbuf-ex.c
snacc-1.3bbn/c-examples/simple/sbuf-ex.c
--- y/snacc-1.3bbn/c-examples/simple/sbuf-ex.c Wed Jul 23 15:33:44 2003
+++ snacc-1.3bbn/c-examples/simple/sbuf-ex.cWed May 21 15:45:18 2003
@@ -77,7 +77,7 @@
}
size = sbuf.st_size;
-origData = (char*)malloc (size);
+origData = (char*)calloc(1, size);
if (read (fd, origData, size) != size)
{
perror ("main: read");
@@ -127,7 +127,7 @@
* value (may be larger than decoded value if encoding
* with indef lengths - so add 512 slush bytes)
*/
-encData = (char*) malloc (size + 512);
+encData = (char*) calloc(1, size + 512);
SBufInit (&encBuf, encData, size + 512);
SBufResetInWriteRvsMode (&encBuf);
diff -ausrN y/snacc-1.3bbn/c-lib/inc/asn-any.h snacc-1.3bbn/c-lib/inc/asn-any.h
--- y/snacc-1.3bbn/c-lib/inc/asn-any.h Sat Jan 27 02:02:58 2001
+++ snacc-1.3bbn/c-lib/inc/asn-any.hWed May 21 15:45:18 2003
@@ -78,16 +78,16 @@
* used before encoding or decoding a type so the proper
* encode or decode routine is used.
*/
-void SetAnyTypeByInt PROTO ((AsnAny *v, AsnInt id));
-void SetAnyTypeByOid PROTO ((AsnAny *v, AsnOid *id));
+void SetAnyTypeByInt PROTO ((AsnAny *v, AsnInt id, char *kind));
+void SetAnyTypeByOid PROTO ((AsnAny *v, AsnOid *id, char *kind));
/*
* used to initialize the hash table (s)
*/
-void InstallAnyByInt PROTO ((int anyId, AsnInt intId, unsigned int size,
EncodeFcn encode, DecodeFcn decode, FreeFcn free, PrintFcn print));
+void InstallAnyByInt PROTO ((int anyId, AsnInt intId, char *kind, unsigned in
Bug#1075520: marked as done (snacc: ftbfs with GCC-14)
Your message dated Thu, 28 Nov 2024 18:19:57 + with message-id and subject line Bug#1085565: Removed package(s) from unstable has caused the Debian Bug report #1075520, regarding snacc: ftbfs with GCC-14 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.) -- 1075520: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075520 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:snacc Version: 1.3.1-10 Severity: important Tags: sid trixie User: debian-...@lists.debian.org Usertags: ftbfs-gcc-14 [This bug is targeted to the upcoming trixie release] Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-14/g++-14, but succeeds to build with gcc-13/g++-13. The severity of this report will be raised before the trixie release. The full build log can be found at: http://qa-logs.debian.net/2024/07/01/snacc_1.3.1-10_unstable_gccexp.log The last lines of the build log are at the end of this report. To build with GCC 14, either set CC=gcc-14 CXX=g++-14 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-14/porting_to.html [...] Making all in compiler make[4]: Entering directory '/<>/compiler' Making all in core make[5]: Entering directory '/<>/compiler/core' test -f parse-asn1.c || /bin/bash ../../ylwrap parse-asn1.y y.tab.c parse-asn1.c y.tab.h `echo parse-asn1.c | sed -e s/cc$/hh/ -e s/cpp$/hpp/ -e s/cxx$/hxx/ -e s/c++$/h++/ -e s/c$/h/` y.output parse-asn1.output -- bison -y -d /<>/compiler/core/parse-asn1.y: warning: 61 shift/reduce conflicts [-Wconflicts-sr] /<>/compiler/core/parse-asn1.y: warning: 2 reduce/reduce conflicts [-Wconflicts-rr] /<>/compiler/core/parse-asn1.y: note: rerun with option '-Wcounterexamples' to generate conflict counterexamples updating parse-asn1.h gcc -DHAVE_CONFIG_H -I. -I../.. -DCOMPILER -DUSE_NIBBLE_MEMORY=0 -DUSE_EXP_BUF -I../../c-lib/inc -I../../c-lib/boot -I../../compiler/back-ends -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -O0 -DFLEX_IN_USE -c -o parse-asn1.o parse-asn1.c gcc -DHAVE_CONFIG_H -I. -I../.. -DCOMPILER -DUSE_NIBBLE_MEMORY=0 -DUSE_EXP_BUF -I../../c-lib/inc -I../../c-lib/boot -I../../compiler/back-ends -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -O0 -DFLEX_IN_USE -c -o lex-asn1.o lex-asn1.c gcc -DHAVE_CONFIG_H -I. -I../.. -DCOMPILER -DUSE_NIBBLE_MEMORY=0 -DUSE_EXP_BUF -I../../c-lib/inc -I../../c-lib/boot -I../../compiler/back-ends -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -O0 -DFLEX_IN_USE -c -o define.o define.c gcc -DHAVE_CONFIG_H -I. -I../.. -DCOMPILER -DUSE_NIBBLE_MEMORY=0 -DUSE_EXP_BUF -I../../c-lib/inc -I../../c-lib/boot -I../../compiler/back-ends -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -O0 -DFLEX_IN_USE -c -o dependency.o dependency.c gcc -DHAVE_CONFIG_H -I. -I../.. -DCOMPILER -DUSE_NIBBLE_MEMORY=0 -DUSE_EXP_BUF -I../../c-lib/inc -I../../c-lib/boot -I../../compiler/back-ends -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -O0 -DFLEX_IN_USE -c -o do-macros.o do-macros.c gcc -DHAVE_CONFIG_H -I. -I../.. -DCOMPILER -DUSE_NIBBLE_MEMORY=0 -DUSE_EXP_BUF -I../../c-lib/inc -I../../c-lib/boot -I../../compiler/back-ends -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector
Bug#375470: marked as done (Decoding routines generated by snacc expect extra EOC octets in a tagged CHOICE)
Your message dated Thu, 28 Nov 2024 18:19:57 +
with message-id
and subject line Bug#1085565: Removed package(s) from unstable
has caused the Debian Bug report #375470,
regarding Decoding routines generated by snacc expect extra EOC octets in a
tagged CHOICE
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.)
--
375470: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=375470
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: snacc
Version: 1.3bbn-9
Severity: important
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.14-2-686
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Versions of packages snacc depends on:
ii libc6 2.3.6-15 GNU C Library: Shared libraries
ii libsnacc0c2 1.3bbn-9 ASN.1 to C or C++ or IDL compiler,
Versions of packages snacc recommends:
ii libsnacc-dev 1.3bbn-9 ASN.1 to C or C++ or IDL compiler,
pn snacc-doc (no description available)
I found this bug when using snacc to generate the decoding routines for
TAP 3.11 (Transfer Account Procedure Data Record Format, Specification
Version Number 3. GSM Association, Official Document TD.57, 26 May 2005)
and testing them with data files from an external source that are surely
of this particular format. The routines returned an unexpected error:
BDecEoc: ERROR - non zero byte in EOC or end of data reached
The same files could be handled without errors by dumpasn1.
It wasn't easy to find out from where these errors come. I inserted
printf() calls adjacent to the BDecEoc() calls in the generated decoding
routines, and this way I finally found that:
The decoding routines expect (and check the presence of) two consecutive
EOC octets where only one EOC octet is present in my test files (no,
I cannot provide you with them). After deleting the extra code the
files went through decoding without errors.
I haven't had the same kind of problem with earlier versions of TAP 3,
so I searched for an explanation from the changes made in TAP 3
specifications from TAP 3.10 to TAP 3.11, and found that the extra
EOC was expected in the decoding routine at a tagged CHOICE, which
was non-tagged in earlier TAP 3 specifications.
The following is a simplified excerpt of the TAP 3.11 specification:
TAP-0311 DEFINITIONS IMPLICIT TAGS ::=
BEGIN
BasicService ::= [APPLICATION 36] SEQUENCE
{
serviceCode BasicServiceCodeOPTIONAL,
transparencyIndicator INTEGER OPTIONAL
}
BasicServiceCode ::= [APPLICATION 426] CHOICE
{
teleServiceCode TeleServiceCode,
bearerServiceCode BearerServiceCode
}
BearerServiceCode ::= [APPLICATION 40] HexString --(SIZE(2))
TeleServiceCode ::= [APPLICATION 218] HexString --(SIZE(2))
HexString ::= OCTET STRING
END
Compile this by snacc. You can find the following sequence of code
in the generated function BDecBasicServiceContent():
BDecBasicServiceCodeContent (b, tagId2, elmtLen2, (v->serviceCode),
&totalElmtsLen1, env);
if (elmtLen1 == INDEFINITE_LEN)
BDecEoc(b, &totalElmtsLen1, env);
if (elmtLen1 == INDEFINITE_LEN)
BDecEoc (b, &totalElmtsLen1, env);
One of the if sentences with its BDecEoc() call is too much, it
shouldn't be there!
I haven't checked if the coding functions produce output that is
compatible with the decoding functions (with extra EOC) or if they
are OK.
--- End Message ---
--- Begin Message ---
Version: 1.3.1-10+rm
Dear submitter,
as the package snacc has just been removed from the Debian archive
unstable we hereby close the associated bug reports. We are sorry
that we couldn't deal with your issue properly.
For details on the removal, please see https://bugs.debian.org/1085565
The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.
Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.
This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.
Debian distribution maintenance software
pp.
Thorsten Alteholz (the ftpmaster behind the curtain)--- End Message ---
Bug#1085565: Removed package(s) from unstable
We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: libsnacc-dev | 1.3.1-10 | amd64, arm64, armel, armhf, i386, mips64el, ppc64el, riscv64, s390x libsnacc0t64 | 1.3.1-10 | amd64, arm64, armel, armhf, i386, mips64el, ppc64el, riscv64, s390x snacc | 1.3.1-10 | source, amd64, arm64, armel, armhf, i386, mips64el, ppc64el, riscv64, s390x snacc-doc | 1.3.1-10 | all --- Reason --- RoQA; orphaned; dead upstream; rc-buggy -- Note that the package(s) have simply been removed from the tag database and may (or may not) still be in the pool; this is not a bug. The package(s) will be physically removed automatically when no suite references them (and in the case of source, when no binary references it). Please also remember that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. Packages are usually not removed from testing by hand. Testing tracks unstable and will automatically remove packages which were removed from unstable when removing them from testing causes no dependency problems. The release team can force a removal from testing if it is really needed, please contact them if this should be the case. We try to close bugs which have been reported against this package automatically. But please check all old bugs, if they were closed correctly or should have been re-assigned to another package. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1085...@bugs.debian.org. The full log for this bug can be viewed at https://bugs.debian.org/1085565 This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Thorsten Alteholz (the ftpmaster behind the curtain)
Bug#1085565: Removed package(s) from unstable
Version: 1.3.1-10+rm Dear submitter, as the package snacc has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1085565 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Thorsten Alteholz (the ftpmaster behind the curtain)
Bug#1047991: marked as done (ruby-filesystem: Fails to build source after successful build)
Your message dated Thu, 28 Nov 2024 18:27:00 + with message-id and subject line Bug#1087388: Removed package(s) from unstable has caused the Debian Bug report #1047991, regarding ruby-filesystem: Fails to build source after successful build 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.) -- 1047991: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1047991 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ruby-filesystem Version: 0.5-7 Severity: minor Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-sab-20230813 ftbfs-source-after-build User: debian...@lists.debian.org Usertags: qa-doublebuild Hi, This package fails to build a source package after a successful build (dpkg-buildpackage ; dpkg-buildpackage -S). This is probably a clear violation of Debian Policy section 4.9 (clean target), but this is filed as severity:minor for now, because a discussion on debian-devel showed that we might want to revisit the requirement of a working 'clean' target. More information about this class of issues, included common problems and solutions, is available at https://wiki.debian.org/qa.debian.org/FTBFS/SourceAfterBuild Relevant part of the build log: > cd /<> && runuser -u user42 -- dpkg-buildpackage --sanitize-env > -us -uc -rfakeroot -S > --- > > dpkg-buildpackage: info: source package ruby-filesystem > dpkg-buildpackage: info: source version 0.5-7 > dpkg-buildpackage: info: source distribution unstable > dpkg-buildpackage: info: source changed by Marcos Talau > dpkg-source --before-build . > fakeroot debian/rules clean > dh clean --buildsystem=ruby --with ruby > dh: warning: Compatibility levels before 10 are deprecated (level 8 in use) >debian/rules override_dh_auto_clean > make[1]: Entering directory '/<>' > rm -f Makefile > rm -rf ext/ > make[1]: Leaving directory '/<>' >dh_clean -O--buildsystem=ruby > dh_clean: warning: Compatibility levels before 10 are deprecated (level 8 in > use) > dpkg-source -b . > dpkg-source: info: using source format '3.0 (quilt)' > dpkg-source: info: building ruby-filesystem using existing > ./ruby-filesystem_0.5.orig.tar.gz > dpkg-source: info: using patch list from debian/patches/series > dpkg-source: warning: ignoring deletion of file Makefile, use > --include-removal to override > dpkg-source: warning: newly created empty file '.sitearchdir.time' will not > be represented in diff > dpkg-source: error: cannot represent change to filesystem.o: binary file > contents changed > dpkg-source: error: add filesystem.o in debian/source/include-binaries if you > want to store the modified binary in the debian tarball > dpkg-source: error: cannot represent change to filesystem.so: binary file > contents changed > dpkg-source: error: add filesystem.so in debian/source/include-binaries if > you want to store the modified binary in the debian tarball > dpkg-source: warning: executable mode 0755 of 'filesystem.so' will not be > represented in diff > dpkg-source: error: unrepresentable changes to source > dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 29 > > E: Command 'cd /<> && runuser -u user42 -- dpkg-buildpackage > --sanitize-env -us -uc -rfakeroot -S' failed to run. The full build log is available from: http://qa-logs.debian.net/2023/08/13/ruby-filesystem_0.5-7_unstable.log If you reassign this bug to another package, please mark 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 --- Version: 0.5-8+rm Dear submitter, as the package ruby-filesystem has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1087388 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution
Bug#1087388: Removed package(s) from unstable
Version: 0.5-8+rm Dear submitter, as the package ruby-filesystem has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1087388 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Thorsten Alteholz (the ftpmaster behind the curtain)
Bug#1087388: Removed package(s) from unstable
We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: libfilesystem-ruby | 0.5-8 | all libfilesystem-ruby1.8 | 0.5-8 | all libfilesystem-ruby1.9 | 0.5-8 | all ruby-filesystem | 0.5-8 | source, amd64, armel, armhf, i386, mips64el, ppc64el, riscv64, s390x ruby-filesystem | 0.5-8+b1 | arm64 --- Reason --- RoQA; dead upstream; does not build with the ruby3.3 -- Note that the package(s) have simply been removed from the tag database and may (or may not) still be in the pool; this is not a bug. The package(s) will be physically removed automatically when no suite references them (and in the case of source, when no binary references it). Please also remember that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. Packages are usually not removed from testing by hand. Testing tracks unstable and will automatically remove packages which were removed from unstable when removing them from testing causes no dependency problems. The release team can force a removal from testing if it is really needed, please contact them if this should be the case. We try to close bugs which have been reported against this package automatically. But please check all old bugs, if they were closed correctly or should have been re-assigned to another package. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1087...@bugs.debian.org. The full log for this bug can be viewed at https://bugs.debian.org/1087388 This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Thorsten Alteholz (the ftpmaster behind the curtain)
