libmicrohttpd_1.0.0-2.1_armhf.changes ACCEPTED into unstable
Thank you for your contribution to Debian. Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 01 Mar 2024 12:21:57 + Source: libmicrohttpd Binary: libmicrohttpd-dev libmicrohttpd12t64 libmicrohttpd12t64-dbgsym Architecture: armhf Version: 1.0.0-2.1 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Steve Langasek Description: libmicrohttpd-dev - library embedding HTTP server functionality (development) libmicrohttpd12t64 - library embedding HTTP server functionality Closes: 1063129 Changes: libmicrohttpd (1.0.0-2.1) unstable; urgency=medium . * Non-maintainer upload. * Rename libraries for 64-bit time_t transition. Closes: #1063129 Checksums-Sha1: 013289ff158eebe57c0748fd6481390c5ca72cf8 337452 libmicrohttpd-dev_1.0.0-2.1_armhf.deb 6aceecf27eeec232583f411402a5e717b9dd92d9 310776 libmicrohttpd12t64-dbgsym_1.0.0-2.1_armhf.deb 3cef0dacbec8643611072518f9d6cc9e269c5b60 149600 libmicrohttpd12t64_1.0.0-2.1_armhf.deb b167381949fcb7137015164b05289f7ec185 8069 libmicrohttpd_1.0.0-2.1_armhf.buildinfo Checksums-Sha256: 098802aeef183f340cce3a28e51bc35407eaceee11a4b7205a449d61f604c1bb 337452 libmicrohttpd-dev_1.0.0-2.1_armhf.deb 0c56b2f8f1dc09400de5867df922877aa930138d8b80ea2e55574f5c96c4ec84 310776 libmicrohttpd12t64-dbgsym_1.0.0-2.1_armhf.deb 3524e471af902bb0136c1ce7a8adeedb402f18ca14f9555a8bf0fa7283ed192d 149600 libmicrohttpd12t64_1.0.0-2.1_armhf.deb 0b0d253e17805bf6b6f3e9015eb1868737318c7cc34cd102671595649b61b9b1 8069 libmicrohttpd_1.0.0-2.1_armhf.buildinfo Files: 6b44fb8fa83423898fe4cb2d571c74a0 337452 libdevel optional libmicrohttpd-dev_1.0.0-2.1_armhf.deb 71787851a6e7acd69499b87ca26b5549 310776 debug optional libmicrohttpd12t64-dbgsym_1.0.0-2.1_armhf.deb f9dd496364b0f032371263d27c6e91bb 149600 libs optional libmicrohttpd12t64_1.0.0-2.1_armhf.deb 23a8fef0b746fcad91e7d533b065df10 8069 libs optional libmicrohttpd_1.0.0-2.1_armhf.buildinfo -BEGIN PGP SIGNATURE- iQJGBAEBCgAwFiEErEg/aN5yj0PyIC/KVo0w8yGyEz0FAmXxLuASHHZvcmxvbkBk ZWJpYW4ub3JnAAoJEFaNMPMhshM93Q8P/1xgZ+Gokq6MsLjSZJsJocINf/X0noH1 MnHwMivNDAZSWaoYdI0uN9HXY51bgxN/ULIQOyYzdAspq1AvI38NOrv5lxe4mLmY RXkxFEjpYW4+RhHrgmAJV6PF2LFkeAo3aoPx2/klpYjvxRKQud6bxadqXjOA1zum BpVOXTfAcr5drz6hqdDL8CYCEGpJs5A4f44D7pxHRxKwm2cB47Bq0sTMb0YdWeHH l1IvHQr0TDHzp1lr+dzpq6eoZioYX/q3rn9HljO6Dn3OZrM4KFU52kekOG3Gtko1 v7vry3NzE5xRNFP9oFdThbey1Bl9wESpj1Vce3jIeATNmPuk9MECiJpOZlhX1NeT tkC7aGnF6cU/0RcTOD6BAXxjVEZsGSvAnG5anOs2MVcTox+NfQFdz4vWMlxhi+nM klur7mMbtDNbqWXWdCEiWgCWtVUEMGSZN1eOfpc5zLje1xmoPTg0XfzlWLL44rnQ 4b1SyMYbKCXyMNkrCO7bulLuccQuSbDdqRQmlPeh/iqbqVvuwI4K3PIteFcSsN9u 4t3FbUwxR5Ev9Ktjrm7YtjR4UD90JFiPMUInhtT/xXPK/dgwyEOZSLmMrHq8uHmz IjK+31kJgIu9nxGylZzasGBo8VNSxvrd2oyFIROMun/0ejiGPldvNSUiFr0KsgqN vlm7iVz3XAJR =w1AL -END PGP SIGNATURE- pgpzJeoGYTSxc.pgp Description: PGP signature
Processing of libmicrohttpd_1.0.0-2.1_armhf.changes
libmicrohttpd_1.0.0-2.1_armhf.changes uploaded successfully to localhost along with the files: libmicrohttpd-dev_1.0.0-2.1_armhf.deb libmicrohttpd12t64-dbgsym_1.0.0-2.1_armhf.deb libmicrohttpd12t64_1.0.0-2.1_armhf.deb libmicrohttpd_1.0.0-2.1_armhf.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)
libmicrohttpd_1.0.0-2.1_armel.changes ACCEPTED into unstable
Thank you for your contribution to Debian. Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 01 Mar 2024 12:21:57 + Source: libmicrohttpd Binary: libmicrohttpd-dev libmicrohttpd12t64 libmicrohttpd12t64-dbgsym Architecture: armel Version: 1.0.0-2.1 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Steve Langasek Description: libmicrohttpd-dev - library embedding HTTP server functionality (development) libmicrohttpd12t64 - library embedding HTTP server functionality Closes: 1063129 Changes: libmicrohttpd (1.0.0-2.1) unstable; urgency=medium . * Non-maintainer upload. * Rename libraries for 64-bit time_t transition. Closes: #1063129 Checksums-Sha1: 5d66d332b5eef040093241948ee5f95d8685834f 337536 libmicrohttpd-dev_1.0.0-2.1_armel.deb 335b4feb8eb0e5b9a0c738a72be3f4a3f49a4e28 305512 libmicrohttpd12t64-dbgsym_1.0.0-2.1_armel.deb fc452c266c4e042c8e2fb41a52a628157246e047 149564 libmicrohttpd12t64_1.0.0-2.1_armel.deb 92b86ed4cddc174bc851a213dc8e16ee833543e6 7764 libmicrohttpd_1.0.0-2.1_armel.buildinfo Checksums-Sha256: 94d0f87cb9b1c9813368cc45ffb52865d83475a34770d865e0dd2d0ccb128024 337536 libmicrohttpd-dev_1.0.0-2.1_armel.deb d65c48a1565ddd5ae5188e6a32546c7d9c02c2f3c00837f030f53fb3cee13dda 305512 libmicrohttpd12t64-dbgsym_1.0.0-2.1_armel.deb 9bfa8e39dbff3fc643e90068565e637f583ebb424ee9e7e6c97f15bd0eb5d87a 149564 libmicrohttpd12t64_1.0.0-2.1_armel.deb 0764d68d9861b68aa476bdb2da93c89293beac86318f8cda63daae545ee8a34f 7764 libmicrohttpd_1.0.0-2.1_armel.buildinfo Files: 5423ea9f33b7c5533aecb1cd16b9a33a 337536 libdevel optional libmicrohttpd-dev_1.0.0-2.1_armel.deb cc83f12adca6d951e1e2b5eeb8870f0a 305512 debug optional libmicrohttpd12t64-dbgsym_1.0.0-2.1_armel.deb 8cb2aa37a4757fe0f04dd69e4dbcf07c 149564 libs optional libmicrohttpd12t64_1.0.0-2.1_armel.deb 4c321545e894d2c8366285b6ba265234 7764 libs optional libmicrohttpd_1.0.0-2.1_armel.buildinfo -BEGIN PGP SIGNATURE- iQJGBAEBCgAwFiEErEg/aN5yj0PyIC/KVo0w8yGyEz0FAmXxHr8SHHZvcmxvbkBk ZWJpYW4ub3JnAAoJEFaNMPMhshM9AZ8QAKIC9mRj9ImhPELzCMlfo0rJdbhzI06q WzrZb+jRFJ0BiA1PdNdmPaoGWZBpGy+ISEBke3JVRdoBWiiDDsPmjWS1CTMnKFpy ugWeVgVqmX9GODTKNRuQQPrTKukZCpFGhpJ0RHvjWQCdVWcYd2UYO422DQH+ZyHe ePVlcScfTL+oyR1l4E/+kMtNQYA2i+IdnnlIjhXI/4+mCMbZScPeg1aIa7kg4gZV C/+PmwM9SyxyXN4f+vUb25dXsAVhMEiCD2l/iJysOc/NSaoQhb5EHFq4C0NTg1Fm gJuG4uZ2jUjlhZWxQ6MicnFd6+MGfSpl86YlD1DsK9h4mZy8TsFUr2OOZGCoqeIN srBthxhpCjGiLS1bGNASzUR3PyqPvUnbl6s61hcziclOL0jvN91iJ4VCkwJ91t6H lstKKKHvVDmjfJ4FXdc5avP73vxjpAt/TZhRlmaiL9XZrOBj3o2nCaywOzfGidWI R8yXosG24W6z56gUsH8hj9j4+MKsAi7m1eB8wt0gzknvMQZ3ezdyGgQkCt//tP85 bfCzPWYS8sBZEf29DJqMdYMuRyaF7zv6mKCe/zdNGPxqIX9gzPgvau7j6GigjfMl zXPdT01LN+wSHFmkeCpeePC4GAasqepRUqHydD5KyAhiLykRF3+kwRVT7hKrxaWG 9npiyeVbqo2c =0EzP -END PGP SIGNATURE- pgpXL1OcGAkkL.pgp Description: PGP signature
Processing of libmicrohttpd_1.0.0-2.1_armel.changes
libmicrohttpd_1.0.0-2.1_armel.changes uploaded successfully to localhost along with the files: libmicrohttpd-dev_1.0.0-2.1_armel.deb libmicrohttpd12t64-dbgsym_1.0.0-2.1_armel.deb libmicrohttpd12t64_1.0.0-2.1_armel.deb libmicrohttpd_1.0.0-2.1_armel.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)
Processed:
Processing control commands: > severity -1 wishlist Bug #1021473 [src:nitpic] nitpic: reproducible-builds: buildid differs in /usr/bin/nitpic Severity set to 'wishlist' from 'normal' -- 1021473: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021473 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed:
Processing control commands: > severity -1 wishlist Bug #1021472 [src:xzoom] xzoom: reproducible-builds: build path embedded in /usr/bin/xzoom Severity set to 'wishlist' from 'normal' -- 1021472: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021472 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed:
Processing control commands: > severity -1 wishlist Bug #1021470 [src:xsok] xsok: reproducible-builds: build path embedded in /usr/games/xsok Severity set to 'wishlist' from 'normal' -- 1021470: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021470 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed:
Processing control commands: > severity -1 wishlist Bug #1021461 [src:icon] icon: reproducible-builds: buildid differences in /usr/bin/icon* Severity set to 'wishlist' from 'normal' -- 1021461: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021461 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed:
Processing control commands: > severity -1 wishlist Bug #1021466 [src:pacman] pacman: reproducible-builds: build path embedded in /usr/games/pacman Severity set to 'wishlist' from 'normal' -- 1021466: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021466 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed:
Processing control commands: > severity -1 wishlist Bug #1021458 [src:o3dgc] o3dgc: reproducible-builds: build path embedded in libo3dgc_common_lib.a Severity set to 'wishlist' from 'normal' -- 1021458: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021458 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed:
Processing control commands: > severity -1 wishlist Bug #1021464 [src:stfl] stfl: reproducible-builds: build path embedded in binaries Severity set to 'wishlist' from 'normal' -- 1021464: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021464 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed:
Processing control commands: > severity -1 wishlist Bug #1021457 [src:olpc-powerd] olpc-powerd: reproducible-builds: build path embedded in debugging symbols Severity set to 'wishlist' from 'normal' -- 1021457: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021457 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed:
Processing control commands: > severity -1 wishlist Bug #1021456 [src:bwbasic] bwbasic: reproducible-builds: build path embedded in /usr/bin/bwbasic Severity set to 'wishlist' from 'normal' -- 1021456: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021456 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed:
Processing control commands: > severity -1 wishlist Bug #1021452 [src:libdv] libdv: reproducible-builds: build path embedded in libdv.so.4.0.3 Severity set to 'wishlist' from 'normal' -- 1021452: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021452 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed:
Processing control commands: > severity -1 wishlist Bug #1020876 [src:yaskkserv] yaskkserv: reproducible-builds: buildid differences in various binaries Severity set to 'wishlist' from 'normal' -- 1020876: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020876 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed:
Processing control commands: > severity -1 wishlist Bug #1020808 [src:powerdebug] powerdebug: reproducible-builds: Embedded build paths in /usr/sbin/powerdebug Severity set to 'wishlist' from 'normal' -- 1020808: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020808 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed:
Processing control commands: > severity -1 wishlist Bug #1020806 [src:perl-byacc] perl-byacc: reproducible-builds: differing buildid in in /usr/bin/pbyacc Severity set to 'wishlist' from 'normal' -- 1020806: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020806 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1020806:
Control: severity -1 wishlist Dear Maintainer, Because Debian builds packages from a fixed build path, neither the 'reprotest' utility in Salsa-CI, nor the Reproducible Builds team's package test infrastructure for Debian[1] currently check for equivalent binary package output from differing source package build paths. This means that your package will pass current reproducibility tests; however we believe that source code and/or build steps still embed the build path into the binary package output, making it more difficult than necessary for independent consumers to check the integrity of those packages by rebuilding them themselves. As a result, this bugreport will remain open and be re-assigned the 'wishlist' severity[2]. For more information about build paths and how they can affect reproducibility, please refer to: https://reproducible-builds.org/docs/build-path/ Thanks, James [1] - https://tests.reproducible-builds.org/debian/reproducible.html [2] - https://www.debian.org/Bugs/Developer#severities
Processed:
Processing control commands: > severity -1 wishlist Bug #1024283 [src:ipsvd] ipsvd: reproducible-builds: buildid differences in various binaries Severity set to 'wishlist' from 'normal' -- 1024283: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024283 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed:
Processing control commands: > severity -1 wishlist Bug #1024279 [src:tolua++] tolua++: reproducible-builds: build path embedded in tolua++5.1 Severity set to 'wishlist' from 'normal' -- 1024279: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024279 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed:
Processing control commands: > severity -1 wishlist Bug #1023960 [src:libcgicc] libcgicc: reproducible-builds: build path embedded in /usr/bin/cgicc-config Severity set to 'wishlist' from 'normal' -- 1023960: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023960 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed:
Processing control commands: > severity -1 wishlist Bug #1021509 [src:xxkb] xxkb: reproducible-builds: build path embedded in /usr/bin/xxkb Severity set to 'wishlist' from 'normal' -- 1021509: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021509 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed:
Processing control commands: > severity -1 wishlist Bug #1021498 [src:tcm] tcm: reproducible-builds: build path embedded in /usr/bin/tcm Severity set to 'wishlist' from 'normal' -- 1021498: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021498 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1021498:
Control: severity -1 wishlist Dear Maintainer, Because Debian builds packages from a fixed build path, neither the 'reprotest' utility in Salsa-CI, nor the Reproducible Builds team's package test infrastructure for Debian[1] currently check for equivalent binary package output from differing source package build paths. This means that your package will pass current reproducibility tests; however we believe that source code and/or build steps still embed the build path into the binary package output, making it more difficult than necessary for independent consumers to check the integrity of binary packages by recompiling them themselves. As a result, this bugreport will remain open and be re-assigned the 'wishlist' severity[2]. For more information about build paths and how they can affect reproducibility, please refer to: https://reproducible-builds.org/docs/build-path/ Thanks, James [1] - https://tests.reproducible-builds.org/debian/reproducible.html [2] - https://www.debian.org/Bugs/Developer#severities
Processed:
Processing control commands: > severity -1 wishlist Bug #1033032 [src:buddy] buddy: reproducible-builds: Embedded build path and usrmerge paths in example Makefile Severity set to 'wishlist' from 'normal' -- 1033032: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033032 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1033032:
Control: severity -1 wishlist Dear Maintainer, Because Debian builds packages from a fixed build path, neither the 'reprotest' utility in Salsa-CI, nor the Reproducible Builds team's package test infrastructure for Debian[1] currently check for equivalent binary package output from differing source package build paths. This means that your package will pass current reproducibility tests; however we believe that source code and/or build steps still embed the build path into the binary package output, making it more difficult than necessary for independent consumers to check the integrity of binary packages by recompiling them themselves. As a result, this bugreport will remain open and be re-assigned the 'wishlist' severity[2]. For more information about build paths and how they can affect reproducibility, please refer to: https://reproducible-builds.org/docs/build-path/ Thanks, James [1] - https://tests.reproducible-builds.org/debian/reproducible.html [2] - https://www.debian.org/Bugs/Developer#severities
Re: Question regarding time_t transition
Le 12/03/2024 à 19:11, Rene Engelhard a écrit : Are we supposed to report bugs against packages ending up with "t64" and missing the "Provides: " for affected architectures like armhf ? That Provides: is there for archs where the transition *doesn't* make a difference. In Debian: Anything except armel/armhf. (ignoring ports where the 32bit archs are in the same boat as armel/armhf ttbomk) So the packages not having a Provides: on armel/ armhf are correct. Or are they intentional and we should wait for the package to be tested/ready/whatever ? Intentional, yes. Thank you very much for explaining this. It wasn't clear from the various documents that I found. So the only thing to do is to wait for the dependencies to be available to build my package on armhf ? Regards, -- Raphaël Halimi
Re: Question regarding time_t transition
Hi, Am 12.03.24 um 15:17 schrieb Raphaël Halimi: Are we supposed to report bugs against packages ending up with "t64" and missing the "Provides: " for affected architectures like armhf ? That Provides: is there for archs where the transition *doesn't* make a difference. In Debian: Anything except armel/armhf. (ignoring ports where the 32bit archs are in the same boat as armel/armhf ttbomk) So the packages not having a Provides: on armel/armhf are correct. Or are they intentional and we should wait for the package to be tested/ready/whatever ? Intentional, yes. Regards, Rene
Bug#1065767: libopendbx: FTBFS on arm{el,hf}: mssql_basic.c:324:21: error: implicit declaration of function ‘dbpoll’ [-Werror=implicit-function-declaration]
On Sat, Mar 09, 2024 at 09:26:38PM +0100, Sebastian Ramacher wrote:
> mssql_basic.c: In function ‘mssql_odbx_result’:
> mssql_basic.c:324:21: error: implicit declaration of function ‘dbpoll’
> [-Werror=implicit-function-declaration]
> 324 | if( dbpoll( dbproc, ms, , ) == FAIL )
> { return -ODBX_ERR_BACKEND; }
> | ^~
dbpoll() is unimplemented:
https://github.com/FreeTDS/freetds/blob/4a6356010ef1e841bcdf3d26f8bbacbf2262d525/src/dblib/dblib.c#L7211
Thus its prototype is only available under #ifdef DBLIB_UNIMPLEMENTED,
whatever semantics does that have (I couldn't find docs for that).
--
WBR, wRAR
signature.asc
Description: PGP signature
Question regarding time_t transition
Dear fellow developers, I was about to file two bug reports (one against libdb5.3 and one against perl-base) but instead of wasting everybody's time, I'd like to ask first, since I couldn't find the information anywhere. Are we supposed to report bugs against packages ending up with "t64" and missing the "Provides: " for affected architectures like armhf ? Or are they intentional and we should wait for the package to be tested/ready/whatever ? Thanks in advance. Regards, -- Raphaël Halimi
