[dpkg] 28/30: Dpkg::Vendor::Debian: Mark loong64 as having pie builtin

Author: yalingfang AuthorDate: Fri Oct 13 02:49:28 2023 +0200 Dpkg::Vendor::Debian: Mark loong64 as having pie builtin Closes: #1053778 Signed-off-by: Guillem Jover --- scripts/Dpkg/Vendor/Debian.pm | 1 + 1 file changed, 1 insertion(+) diff --git a/scripts/Dpkg/Vendor/Debian.pm b

[dpkg] 06/30: scripts: Remove unused GCJ and GCJFLAGS support

Author: Guillem Jover AuthorDate: Thu Aug 31 20:00:46 2023 +0200 scripts: Remove unused GCJ and GCJFLAGS support The gcj project is dead since 2018. --- doc/README.feature-removal-schedule | 6 ++ man/dpkg-buildflags.pod | 22 +- scripts/Dpkg

[dpkg] 20/30: test: Generate the .deb from scratch instead of adapting them

Author: Guillem Jover AuthorDate: Tue Sep 26 04:31:27 2023 +0200 test: Generate the .deb from scratch instead of adapting them The behavior for «ar rc» is not portable, and depending on the system implementation, it either replaces the file, or appends it at the end, or other

[dpkg] 23/30: dpkg-deb: Refactor legacy compress_params

Author: Guillem Jover AuthorDate: Thu Oct 12 06:07:43 2023 +0200 dpkg-deb: Refactor legacy compress_params This is the compression parameters for legacy modes, which we will use in other instances. Instead of repeating them, use a single variable that we can use to initialize from

[dpkg] 22/30: dpkg-deb: Reject --no-uniform-compression with format 0.939000

Author: Guillem Jover AuthorDate: Thu Oct 12 06:06:49 2023 +0200 dpkg-deb: Reject --no-uniform-compression with format 0.939000 This format has never supported non-uniform compression. Report it instead of letting the user think the operation succeeded. --- src/deb/main.c | 4 1

[dpkg] 19/30: test: Do not use -T for ln calls

Author: Guillem Jover AuthorDate: Tue Sep 26 04:30:40 2023 +0200 test: Do not use -T for ln calls This option is not portable, and makes the ln command fail when it's not a GNU implementation. --- src/at/realpath.at | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff

[dpkg] 01/30: test: Update cppcheck suppressions for 2.12.0

Author: Guillem Jover AuthorDate: Tue Oct 17 09:41:28 2023 +0200 test: Update cppcheck suppressions for 2.12.0 Warned-by: cppcheck --- t/cppcheck/cppcheck.supp | 11 +++ 1 file changed, 11 insertions(+) diff --git a/t/cppcheck/cppcheck.supp b/t/cppcheck/cppcheck.supp index

[dpkg] 02/30: test: Add installtest target and make test use the build tree programs

Author: Guillem Jover AuthorDate: Tue Oct 17 10:14:25 2023 +0200 test: Add installtest target and make test use the build tree programs The usual convention is for a test or check target to use the programs from the build tree, and an installtest or installcheck target to test

[dpkg] branch main updated (7486fb37d -> e6eb9f0b8)

This is an automated email from the git hooks/post-receive script. guillem pushed a change to branch main in repository dpkg. from 7486fb37d po: Update German man pages translation new 2e0ca957c test: Update cppcheck suppressions for 2.12.0 new 9c5108b5d test: Add installtest

Bug#1053705: dpkg-dev: please use a different word than Maintainer from dpkg-parsechangelog

On Mon, 2023-10-09 at 07:59:05 -0300, David Bremner wrote: > Package: dpkg-dev > Version: 1.22.0 > Severity: minor > The use of Maintainer in the output of dpkg-parsechangelog is > confusing, because it suggests that dpkg-parsechangelog is reporting > the Maintainer field from debian/control. I

Bug#1053778: dpkg: add loong64 to mask builtin feature list

Hi! [ In the future make sure to send mails to the Debian bug tracker as plain not-flowed text, otherwise that messes up with the pseudo-header formatting. Thanks! ] On Wed, 2023-10-11 at 09:31:01 +0800, yalingfang wrote: > Package: dpkg Version: 1.22.0 Severity: normal Tags: patch User: >

Bug#699208: marked as done (s-s-d: on kFreeBSD fails to stop mpd on upgrade)

Control: reopen -1 Control: retitle -1 s-s-d: On kFreeBSD fails to find deleted exec filename On Sat, 2023-10-07 at 14:16:08 +, Debian Bug Tracking System wrote: > kFreeBSD has been removed from Debian ports: > https://lists.debian.org/debian-bsd/2023/07/msg3.html This report is still a

Bug#1053481: libdpkg-perl: dpkg-source fails to generate (complete) Testsuite-Triggers if test deps have :native qualifier

Hi! On Wed, 2023-10-04 at 20:17:58 -0400, James McCoy wrote: > Package: libdpkg-perl > Version: 1.18.8 > Severity: normal > Control: affects -1 src:zsh src:poppler src:libjodycode src:doxygen > src:jemalloc src:jdupes src:libsdl2 src:iproute2 > Any test stanza in a debian/tests/control file

Re: format 0.939000 for breaking the 9.3GB barrier

Hi! On Sat, 2023-09-16 at 16:07:37 +0200, Adam Borowski wrote: > And we're closer and closer to get there: the last time we spoke, max > package size was 1.7GB, it's 5.5GB today. In fact, judging by > Installed-Size alone, some other packages would already breach this limit, > had they shipped

[dpkg] branch 1.20.x updated (1fd89b43d -> 908b77782)

This is an automated email from the git hooks/post-receive script. guillem pushed a change to branch 1.20.x in repository dpkg. from 1fd89b43d Release 1.20.12 add c3ad3e431 Bump version to 1.20.13 add bf7d547e8 libdpkg: Refactor pkg_format_print() out from pkg_format_show()

[dpkg] annotated tag 1.20.13 created (now e1afaaef4)

This is an automated email from the git hooks/post-receive script. guillem pushed a change to annotated tag 1.20.13 in repository dpkg. at e1afaaef4 (tag) tagging 908b777829113957c31ee1e91aa73e1faae66db9 (commit) replaces 1.20.12 by Guillem Jover on Wed Sep 13 23:40:38 2023

Bug#910377: System-critical package management

[ CCing #910377 for some context. ] Hi! On Thu, 2023-09-07 at 11:59:47 +0900, Simon Richter wrote: > > The lack of any system of recognition for packages that are critical to > > system operation impedes the reliability of Debian-based systems. For > > example, a reboot during a background

Re: System-critical package management

[ CCing #910377 for some context. ] Hi! On Thu, 2023-09-07 at 11:59:47 +0900, Simon Richter wrote: > > The lack of any system of recognition for packages that are critical to > > system operation impedes the reliability of Debian-based systems. For > > example, a reboot during a background

Bug#1051902: bullseye-pu: package dpkg/1.20.13

Package: release.debian.org Severity: normal Tags: bullseye User: release.debian@packages.debian.org Usertags: pu X-Debbugs-Cc: d...@packages.debian.org Control: affects -1 + src:dpkg Hi! [ Reason ] This update backports the loong64 arch support as requested in #1051763 because some of the

Bug#1051763: dpkg: Please backport support for loong64 to oldstable and stable

On Wed, 2023-09-13 at 09:20:46 +0200, John Paul Adrian Glaubitz wrote: > On Tue, 2023-09-12 at 22:34 +0200, Guillem Jover wrote: > > I guess I could backport it to dpkg 1.20.x for oldstable, but if the > > infra servers are going to be upgraded soon (at least out of oldstabl

Bug#1051763: dpkg: Please backport support for loong64 to oldstable and stable

Tags: fixed -1 1.21.21 On Tue, 2023-09-12 at 12:05:47 +0200, John Paul Adrian Glaubitz wrote: > Source: dpkg > Version: 1.21.22 > Severity: normal > User: debian-de...@lists.debian.org > Usertags: loong64 > X-Debbugs-Cc: zhangjial...@loongson.cn,zhangdan...@loongson.cn > In order to be able to

Re: Architecture variants for Debian / Ubuntu

Hi! On Fri, 2023-09-01 at 08:43:55 +1200, Michael Hudson-Doyle wrote: > Recently the topic of exploiting newer instructions without dropping > support for older machines has come up several times inside Ubuntu > engineering. I understand this topic has come up several times in the past > for

Bug#1051209: dpkg-dev: dpkg-source --commit should use configured default editor instead of forcing nano

Hi! On Mon, 2023-09-04 at 15:43:02 +0200, Axel Kittenberger wrote: > Package: dpkg-dev > Version: 1.22.0 > Severity: normal >* What led up to the situation? > > using: dpkg-source --commit > >* What exactly did you do (or not do) that was effective (or > ineffective)? > >

Bug#1051085: dpkg: dpkg-db-backup.timer stopped after upgrades

Hi! On Sat, 2023-09-02 at 16:43:57 +0200, Sven Joachim wrote: > Package: dpkg > Version: 1.22.0 > Severity: normal > Upgrading dpkg stops the dpkg-db-backup.timer, which seems rather > undesirable, as it the timer remains inactive until the next reboot or > until it is started manually: […] Ah!

Re: [RFC] Removing support for GCJ and GCJFLAGS from dpkg?

ed the attached patch which will be included in my next git push targeting dpkg 1.22.1. Regards, Guillem From 444a0d7b0546cde45c752f12125810cfeb5bf667 Mon Sep 17 00:00:00 2001 From: Guillem Jover Date: Thu, 31 Aug 2023 20:00:46 +0200 Subject: [PATCH] scripts: Remove unused GCJ and GCJFLAGS sup

[RFC] Removing support for GCJ and GCJFLAGS from dpkg?

Hi! While going through the supported compilers and build flags recently, I noticed that dpkg-buildflags and the various dpkg Makefile fragment files still have support for gcj, but that compiler seems to have stopped being maintained some time ago. According to Wikipedia

Bug#1021292: Enabling branch protection on amd64 and arm64

Hi! On Sun, 2023-08-27 at 12:51:53 +0200, Guillem Jover wrote: > On Tue, 2023-06-27 at 16:09:40 +0100, Wookey wrote: > > OK. We're all agreed on that then. Guillem can stick it in the next > > dpkg upload. So this happened, and Johannes reported that this seems to be breaking

[dpkg] 02/02: doc: Fix typos in code comments

-> main) Author: Guillem Jover AuthorDate: Wed Aug 30 22:02:23 2023 +0200 doc: Fix typos in code comments Warned-by: codespell --- scripts/t/Dpkg_Shlibs.t | 2 +- tests/t-disappear-depended/Makefile | 2 +- tests/t-disappear-diverted/Makefile

[dpkg] branch main updated (a2bc83ce4 -> 0fce517cd)

This is an automated email from the git hooks/post-receive script. guillem pushed a change to branch main in repository dpkg. from a2bc83ce4 po: Update German man pages translation new adf5254f1 po: Fix format string typo in German scripts translation new 0fce517cd doc: Fix typos

[dpkg] 01/02: po: Fix format string typo in German scripts translation

Author: Guillem Jover AuthorDate: Wed Aug 30 22:04:33 2023 +0200 po: Fix format string typo in German scripts translation Fixes: commit a024068d596f511ef59658bc1a3d2f2e14c98e25 Changelog: silent --- scripts/po/de.po | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[dpkg] branch main updated: man: Fix typo in stackclash feature name in dpkg-buildflags(1)

by this push: new 50bbd63cb man: Fix typo in stackclash feature name in dpkg-buildflags(1) 50bbd63cb is described below commit 50bbd63cbae8950a5744c6bfa4543a62404a0d70 (HEAD -> main) Author: Guillem Jover AuthorDate: Wed Aug 30 16:31:48 2023 +0200 man: Fix typo in stackclash feat

[dpkg] 02/03: Release 1.22.0

: 1.22.0) Author: Guillem Jover AuthorDate: Wed Aug 30 05:46:48 2023 +0200 Release 1.22.0 --- debian/changelog | 330 ++- 1 file changed, 327 insertions(+), 3 deletions(-) diff --git a/debian/changelog b/debian/changelog index 85a01f679

[dpkg] annotated tag 1.22.0 created (now 6a7d818da)

This is an automated email from the git hooks/post-receive script. guillem pushed a change to annotated tag 1.22.0 in repository dpkg. at 6a7d818da (tag) tagging 744487c98a622b9b38c22c6ca330315af4a30a11 (commit) replaces 1.21.20 by Guillem Jover on Wed Aug 30 05:46:48 2023

[dpkg] branch main updated (22d28f45e -> c9dcec596)

This is an automated email from the git hooks/post-receive script. guillem pushed a change to branch main in repository dpkg. from 22d28f45e Mark dpkg-build-api level 1 as stable new 462176757 po: Regenerate .pot files and merge .po files with them new 744487c98 Release 1.22.0

[dpkg] 03/03: Bump version to 1.22.1

-> main) Author: Guillem Jover AuthorDate: Wed Aug 30 06:07:47 2023 +0200 Bump version to 1.22.1 --- debian/changelog | 6 ++ 1 file changed, 6 insertions(+) diff --git a/debian/changelog b/debian/changelog index 7648041b0..1e6b61c90 100644 --- a/debian/changelog +++ b/debian/change

Re: Next upload 2023-08-27 (dpkg 1.22.0)

Hi! On Wed, 2023-08-23 at 13:51:27 +0200, Guillem Jover wrote: > I'm planning on uploading around this next weekend. I'll be flushing > pending branches and commits over the week, including the build API > support, and several of the changes to build flag changes that > seemingly g

[dpkg] 01/34: po: Update Romanian dselect translation

Author: Remus-Gabriel Chelu AuthorDate: Sat Jul 22 14:12:49 2023 +0200 po: Update Romanian dselect translation Closes: #1040869 Signed-off-by: Guillem Jover --- dselect/po/ro.po | 666 ++- 1 file changed, 260 insertions(+), 406

[dpkg] 34/34: Mark dpkg-build-api level 1 as stable

-> main) Author: Guillem Jover AuthorDate: Wed Aug 30 01:54:22 2023 +0200 Mark dpkg-build-api level 1 as stable While there are not many items in affected by the new API level, this is a good start as any. --- debian/control| 1 + man/dpkg-bu

[dpkg] 32/34: scripts/mk: On dpkg-build-api >= 1 default to dpkg_vendor_derives_from_v1

Author: Guillem Jover AuthorDate: Tue Sep 13 23:41:55 2022 +0200 scripts/mk: On dpkg-build-api >= 1 default to dpkg_vendor_derives_from_v1 --- man/dpkg-build-api.pod | 7 +++ scripts/mk/Makefile.am | 5 + scripts/mk/vendor.mk | 12 ++-- 3 files changed, 22 insertions(+)

[dpkg] 31/34: scripts/mk: Add new buildapi.mk support

Author: Guillem Jover AuthorDate: Tue Sep 13 23:41:55 2022 +0200 scripts/mk: Add new buildapi.mk support This makes it possible to switch default behavior for build API levels > 0. --- man/dpkg-buildapi.pod| 12 scripts/Makefile

[dpkg] 33/34: scripts/mk: On dpkg-build-api >= 1 include buildtools.mk in default.mk

Author: Guillem Jover AuthorDate: Tue Sep 13 23:41:55 2022 +0200 scripts/mk: On dpkg-build-api >= 1 include buildtools.mk in default.mk --- man/dpkg-build-api.pod | 4 scripts/mk/default.mk | 3 +++ 2 files changed, 7 insertions(+) diff --git a/man/dpkg-build-api.pod b/man/dpkg-bu

[dpkg] 30/34: dpkg-buildpackage: On dpkg-build-api >= 1 avoid build target heuristics

Author: Guillem Jover AuthorDate: Sat Dec 25 01:30:45 2021 +0100 dpkg-buildpackage: On dpkg-build-api >= 1 avoid build target heuristics --- man/dpkg-build-api.pod | 6 ++ scripts/dpkg-buildpackage.pl | 3 +++ 2 files changed, 9 insertions(+) diff --git a/man/dpkg-build-api.pod b/

[dpkg] 28/34: dpkg-shlibdeps: On dpkg-build-api >= 1 require -l instead of LD_LIBRARY_PATH

Author: Guillem Jover AuthorDate: Sat Dec 25 01:23:04 2021 +0100 dpkg-shlibdeps: On dpkg-build-api >= 1 require -l instead of LD_LIBRARY_PATH --- man/dpkg-build-api.pod | 5 + scripts/Dpkg/Shlibs.pm | 13 ++--- scripts/dpkg-gensymbols.pl | 5 - scripts/dpkg-shlibdeps

[dpkg] 26/34: dpkg-buildapi: New tool to fetch the dpkg-build-api level

Author: Guillem Jover AuthorDate: Fri Dec 2 19:30:13 2022 +0100 dpkg-buildapi: New tool to fetch the dpkg-build-api level --- debian/README.bug-usertags | 2 ++ debian/dpkg-dev.install| 1 + debian/dpkg-dev.manpages | 1 + man/Makefile.am| 2 ++ man/dpkg-buildapi.pod

[dpkg] 27/34: man: Open up dpkg-build-api level 1

Author: Guillem Jover AuthorDate: Sat Dec 25 01:23:04 2021 +0100 man: Open up dpkg-build-api level 1 --- man/dpkg-build-api.pod | 9 + 1 file changed, 9 insertions(+) diff --git a/man/dpkg-build-api.pod b/man/dpkg-build-api.pod index d2a56d8a9..de49dfa0e 100644 --- a/man/dpkg-build

[dpkg] 22/34: Dpkg::Vendor::Debian: Add support for new hardening branch feature

Author: Guillem Jover AuthorDate: Sat Jun 4 06:53:39 2022 +0200 Dpkg::Vendor::Debian: Add support for new hardening branch feature Closes: #1021292 --- man/dpkg-buildflags.pod | 9 + scripts/Dpkg/Vendor/Debian.pm | 19 +++ scripts/t/Dpkg_BuildFlags.t | 1

[dpkg] 24/34: Dpkg::Source::Quilt: Switch get_patch_file() to be based off get_patch_dir()

Author: Guillem Jover AuthorDate: Wed Aug 30 02:34:38 2023 +0200 Dpkg::Source::Quilt: Switch get_patch_file() to be based off get_patch_dir() Do not use get_patch_file() with no argument as a means to get the patch directory, instead reverse the implementation around and use

[dpkg] 21/34: Dpkg::Vendor::Debian: Handle abi feature flags as builtin

Author: Guillem Jover AuthorDate: Sun Jul 9 19:01:04 2023 +0200 Dpkg::Vendor::Debian: Handle abi feature flags as builtin These feature flags are builtin depending on the libc ABI of the port, and it's more correct to handle them like we handle PIE for example. --- scripts/Dpkg/Vendor

[dpkg] 23/34: Dpkg::Vendor::Debian: Add support for new stackclash hardening feature

Author: Guillem Jover AuthorDate: Mon Aug 28 12:38:19 2023 +0200 Dpkg::Vendor::Debian: Add support for new stackclash hardening feature Closes: #918914 --- man/dpkg-buildflags.pod | 8 scripts/Dpkg/Vendor/Debian.pm | 11 +++ scripts/t/Dpkg_BuildFlags.t | 1 + 3

[dpkg] 19/34: Dpkg::Vendor::Debian: Move lfs from future to abi area and create an alias

Author: Guillem Jover AuthorDate: Mon Jun 5 01:51:48 2023 +0200 Dpkg::Vendor::Debian: Move lfs from future to abi area and create an alias For the same reason we have moved the time64 feature from the future to the abi feature area to make the name more clear and pass the test

[dpkg] 11/34: dpkg-split: Use varbuf instead of ad-hoc allocation in read_info

Author: Guillem Jover AuthorDate: Wed Jul 12 05:33:41 2023 +0200 dpkg-split: Use varbuf instead of ad-hoc allocation in read_info Changelog: internal --- src/split/info.c | 21 ++--- 1 file changed, 10 insertions(+), 11 deletions(-) diff --git a/src/split/info.c b/src

[dpkg] 20/34: Dpkg::Vendor::Debian: Move builtin default setup before init_build_features()

Author: Guillem Jover AuthorDate: Sun Jul 9 17:58:45 2023 +0200 Dpkg::Vendor::Debian: Move builtin default setup before init_build_features() These are the defaults for the system, and we should provide those to the init_build_features(), which can then override them as they wish

[dpkg] 14/34: test: Move test_data_file() to test.h

Author: Guillem Jover AuthorDate: Sat Aug 26 14:01:37 2023 +0200 test: Move test_data_file() to test.h This function is generally useful for tests so that they can use data files. --- lib/dpkg/t/t-meminfo.c | 13 - lib/dpkg/test.h| 13 + 2 files changed

[dpkg] 05/34: libdpkg: Fix coding style for varbuf module

Author: Guillem Jover AuthorDate: Thu Jul 6 23:39:08 2023 +0200 libdpkg: Fix coding style for varbuf module --- lib/dpkg/varbuf.c | 191 -- 1 file changed, 99 insertions(+), 92 deletions(-) diff --git a/lib/dpkg/varbuf.c b/lib/dpkg/varbuf.c

[dpkg] 03/34: debian: Do not start the dpkg-db-backup timer during installation

Author: Guillem Jover AuthorDate: Wed Aug 30 00:43:08 2023 +0200 debian: Do not start the dpkg-db-backup timer during installation The code injected by debhelper does not ignore timers during installation, so we tell it to not start it, as that is the wrong time to perform

[dpkg] 15/34: libdpkg: Generalize command_in_path() from find_command()

Author: Guillem Jover AuthorDate: Thu Aug 24 12:11:14 2023 +0200 libdpkg: Generalize command_in_path() from find_command() This is useful for external users too. --- lib/dpkg/Makefile.am | 6 ++ lib/dpkg/command.c | 45

[dpkg] 18/34: Dpkg::Vendor::Debian: Move time64 buildflags feature from future to abi

Author: Guillem Jover AuthorDate: Wed May 24 22:09:49 2023 +0200 Dpkg::Vendor::Debian: Move time64 buildflags feature from future to abi Add this new feature area that describes the feature in a more correct and clear way, as flags that affect the userland ABI. And removes

[dpkg] 16/34: man: Document version when new programs where introduced

Author: Guillem Jover AuthorDate: Mon Aug 28 23:39:03 2023 +0200 man: Document version when new programs where introduced We should document not only when specific options or behavior was introduced but also when these new tools got introduced. --- man/dpkg-buildflags.pod | 2

[dpkg] 17/34: man: Fix typo in future lfs feature introduction version

Author: Guillem Jover AuthorDate: Mon Aug 28 04:45:14 2023 +0200 man: Fix typo in future lfs feature introduction version The version was mistyped. --- man/dpkg-buildflags.pod | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/man/dpkg-buildflags.pod b/man/dpkg

[dpkg] 06/34: libdpkg: Reorder varbuf functions

Author: Guillem Jover AuthorDate: Thu Jul 6 23:39:52 2023 +0200 libdpkg: Reorder varbuf functions Place the implementations in the order matching their usual life cycle. --- lib/dpkg/varbuf.c | 194 +++--- 1 file changed, 97 insertions

[dpkg] branch main updated (eb0e14f11 -> 22d28f45e)

This is an automated email from the git hooks/post-receive script. guillem pushed a change to branch main in repository dpkg. from eb0e14f11 po: Update German man pages translation new 773251dc1 po: Update Romanian dselect translation new e1ccdfccf debian: Set Persistent=true for

[dpkg] 12/34: Use varbuf_add_varbuf() instead of varbuf_add_buf()/_str()

Author: Guillem Jover AuthorDate: Thu Jun 22 02:30:15 2023 +0200 Use varbuf_add_varbuf() instead of varbuf_add_buf()/_str() Changelog: internal --- src/main/configure.c | 2 +- src/main/packages.c | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/src/main/configure.c

[dpkg] 09/34: libdpkg: Add varbuf setter functions

Author: Guillem Jover AuthorDate: Thu Jun 22 02:42:10 2023 +0200 libdpkg: Add varbuf setter functions Add _buf(), _varbuf(), _str() and _strn() setter functions to help initialize varbufs. --- lib/dpkg/libdpkg.map | 2 ++ lib/dpkg/t/t-varbuf.c | 35

[dpkg] 08/34: libdpkg: Add varbuf_add_strn()

Author: Guillem Jover AuthorDate: Wed Sep 30 13:55:24 2009 +0200 libdpkg: Add varbuf_add_strn() --- lib/dpkg/t/t-varbuf.c | 29 - lib/dpkg/varbuf.h | 1 + 2 files changed, 29 insertions(+), 1 deletion(-) diff --git a/lib/dpkg/t/t-varbuf.c b/lib/dpkg/t/t-varbuf.c

[dpkg] 13/34: Use varbuf_set_*() instead of ad-hoc initialization

Author: Guillem Jover AuthorDate: Wed Jul 12 05:14:54 2023 +0200 Use varbuf_set_*() instead of ad-hoc initialization Instead of using an explicit varbuf_reset() followed by varbuf_add_*() and possible varbuf_end_str(), just use a single varbuf_set_*() to initialize the varbuf

[dpkg] 07/34: libdpkg: Add varbuf_add_varbuf() function

Author: Guillem Jover AuthorDate: Thu Jun 22 02:27:14 2023 +0200 libdpkg: Add varbuf_add_varbuf() function --- lib/dpkg/libdpkg.map | 1 + lib/dpkg/t/t-varbuf.c | 28 +++- lib/dpkg/varbuf.c | 8 lib/dpkg/varbuf.h | 1 + 4 files changed, 37 insertions

[dpkg] 10/34: libdpkg: Switch ustar filename construction to use varbuf_add_strn()

Author: Guillem Jover AuthorDate: Wed Jul 12 04:25:48 2023 +0200 libdpkg: Switch ustar filename construction to use varbuf_add_strn() Use varbuf instead of formatting via str_fmt(), which should be more performant. --- lib/dpkg/tarfn.c | 10 -- 1 file changed, 8 insertions

[dpkg] 02/34: debian: Set Persistent=true for dpkg-db-backup systemd timer

t time. The timer is meant to trigger daily even if the computer is not running at midnight. By setting Persistent=true we make the timer trigger immediately if the specified time has passed. Closes: #1041730 Signed-off-by: Guillem Jover --- debian/dpkg.dpkg-db-backup.time

Bug#918914: Enabling -fstack-clash-protection for trixie

Hi! On Sun, 2023-08-06 at 23:25:23 +0200, Moritz Mühlenhoff wrote: > Following the procedure to modify default dpkg-buildflags I propose to > enable -fstack-clash-protection on amd64. The bug for dpkg tracking this > is #918914. > > | -fstack-clash-protection > | Generate code to prevent stack

Bug#1021292: Enabling branch protection on amd64 and arm64

Hi! On Tue, 2023-06-27 at 16:09:40 +0100, Wookey wrote: > On 2023-06-27 16:58 +0200, Moritz Mühlenhoff wrote: > > Am Wed, Jun 21, 2023 at 05:41:36PM +0200 schrieb Emanuele Rocca: > > > On 2022-10-26 08:20, Moritz Mühlenhoff wrote: > > > > I think this should rather be applied early after the

Next upload 2023-08-27 (dpkg 1.22.0)

Hi! I'm planning on uploading around this next weekend. I'll be flushing pending branches and commits over the week, including the build API support, and several of the changes to build flag changes that seemingly got consensus. I'll send individual mails stating this clearly in case anyone wants

Bug#1043298: Package dependenciens mishmash

Control: tag -1 moreinfo unreproducible Hi! On Tue, 2023-08-08 at 18:28:57 +, Mcgiwer wrote: > Package: dpkg > Version: 1.21.22 (amd64) > There seem to be problem with the packages dependencies. If there is a problem with package dependencies, then that should probably be assigned to the

Bug#1042931: dpkg-dev: dpkg-buildpackage -P option does not work

Hi! On Thu, 2023-08-03 at 03:29:54 +0200, Thorsten Glaser wrote: > Package: dpkg-dev > Version: 1.21.22 > Severity: normal > X-Debbugs-Cc: t...@mirbsd.de > > I tried to use build profiles for the first time today, and after > running into trouble with pbuilder I tried to run it manually and >

Re: RFC: New dpkg-build-api levels

Hi! On Wed, 2023-05-17 at 01:31:57 +0200, Guillem Jover wrote: > On Sun, 2023-05-14 at 10:25:19 +0200, Niels Thykier wrote: > > All in all, I hope you will go ahead with this proposal. >· > I'll leave some more time for comments, but otherwise I think I'll start > merging

Bug#1041730: dpkg: Systemd dpkg-db-backup.timer unit should be "Persistent=true"

Hi! On Sat, 2023-07-22 at 19:36:46 +0300, Teemu Likonen wrote: > Package: dpkg > Version: 1.21.22 > Severity: minor > Tags: patch > X-Debbugs-Cc: tliko...@iki.fi > Dpkg installs systemd timer unit dpkg-db-backup.timer which is supposed > to run daily: > > #

Bug#1041210: dpkg: vendor information should be read from /usr, not from /etc/dpkg/origins/

Control: reassign -1 dpkg-dev Control: retitle -1 dpkg-vendor: Support reading vendor info from /usr Control: severity -1 wishlist Control: block -1 by 695781 On Sat, 2023-07-15 at 19:42:25 +0200, Gioele Barabucci wrote: > Package: dpkg > Version: 1.21.22 > Usertags: conffiles-reduction >

Re: [RFC PATCH] libdpkg: Sort files within the package.

Hi! On Mon, 2023-07-03 at 21:37:08 +0200, Sebastian Andrzej Siewior wrote: > This started in 2021 and I have no idea what to do with it so here it > is. Let me get back to how it started: > I was looking into the why does it take some time after apt downloaded > the packages before dpkg starts

Re: Prevent dpkg-buildflags from overwriting any (or at least some) flags during compilation

Hi! On Sat, 2023-07-22 at 13:12:28 +0200, Guillem Jover wrote: > [ This feels more like a packaging question than one for dpkg development, > please redirect further replies to debian-mentors(?) now on Cc. :) ] [ Sorry noticed the typo in the mentors list address just when I was s

Re: Prevent dpkg-buildflags from overwriting any (or at least some) flags during compilation

Hi! [ This feels more like a packaging question than one for dpkg development, please redirect further replies to debian-mentors(?) now on Cc. :) ] On Wed, 2023-07-12 at 15:21:26 +0200, Jędrzej Dudkiewicz wrote: > I have few projects that I pack for our internal use. I use `debuild` > to

Re: Add openssl for hashing, as an option

Hi! On Thu, 2023-07-20 at 16:58:32 +0200, Adam Majer wrote: > This seems to be related to > https://lists.debian.org/debian-dpkg/2023/06/msg00059.html > which I've found after I've created this patch already. The motivation > is not to use openssl instead of libmd, but to have the option to use

Bug#951200: base-files: unable to upgrade, conffile error

Control: tags -1 moreinfo unreproducible Hi! On Wed, 2020-02-12 at 11:31:35 +, Luca Koroll wrote: > Package: base-files > Version: 9.9+deb9u11 > Severity: important > after rebooting my system and trying to update my packages an error with > the base-files package occured which brought me

Bug#606825: mingw triplets/ostable

Hi! Just noticed this change to the GNU config project which I wanted to add a reference here: https://git.savannah.gnu.org/cgit/config.git/commit/?id=91f6a7f616b161c25ba2001861a40e662e18c4ad Thanks, Guillem

Re: DEP 17: Improve support for directory aliasing in dpkg

Hi! On Wed, 2023-06-21 at 23:24:53 +0900, Simon Richter wrote: > On 6/21/23 20:33, Guillem Jover wrote: > > I don't think we disagree (?), I probably didn't express myself clearly. > > The fact that no package ships those symlinks *is* and *has* been a > > problem, and what

Bug#1037136: dpkg-buildflags: 64-bit time_t by default

Hi! On Wed, 2023-07-05 at 14:24:02 -0700, Steve Langasek wrote: > On Fri, Jun 09, 2023 at 03:56:28AM +0200, Guillem Jover wrote: > > On Mon, 2023-06-05 at 21:18:10 -0700, Steve Langasek wrote: > > > Package: dpkg-dev > > > Version: 1.21.22 > > &g

[dpkg] 01/05: dpkg-deb: Fix short lived memory leak after fork()

Author: Guillem Jover AuthorDate: Sun Jul 9 01:23:55 2023 +0200 dpkg-deb: Fix short lived memory leak after fork() This memory leak is short lived as we immediately exit from this child, but ASAN is complaining about it. Warned-by: gcc ASAN --- src/deb/extract.c | 1 + 1 file

[dpkg] 04/05: test: Disable ASAN link order check also for functional tests

Author: Guillem Jover AuthorDate: Sat Jul 8 23:47:01 2023 +0200 test: Disable ASAN link order check also for functional tests When we use eatmydata which sets LD_PRELOAD, that can confuse the ASAN link order check, making program abort and failing the entire test suite

[dpkg] 05/05: build: Do not enable the sanitizer for the functional test suite

-> main) Author: Guillem Jover AuthorDate: Sun Jul 9 02:44:39 2023 +0200 build: Do not enable the sanitizer for the functional test suite The way the code is currently structured, it is not freeing memory on code paths leading to an ohshit() or ohshite(). But those mi

[dpkg] 03/05: build: Fix sanitizer compiler options selected

Author: Guillem Jover AuthorDate: Sun Jul 9 00:15:48 2023 +0200 build: Fix sanitizer compiler options selected We should not pass -fsanitize=leak as that is already part of -fsanitize=address. To get better stack traces we should pass -fno-omit-frame-pointer. Fixes: commit

[dpkg] 02/05: build: Fix typo in DPKG_COMPILER_SANITIZER m4 macro comment

Author: Guillem Jover AuthorDate: Sat Jul 8 21:20:25 2023 +0200 build: Fix typo in DPKG_COMPILER_SANITIZER m4 macro comment Fixes: commit 59268c3f1098114c0dc27b2129882faa96897a1a Warned-by: codespell Changelog: silent --- m4/dpkg-compiler.m4 | 2 +- 1 file changed, 1 insertion

[dpkg] 05/10: build: Add support for compiler analyzer flags

Author: Guillem Jover AuthorDate: Sun Jun 4 23:54:54 2023 +0200 build: Add support for compiler analyzer flags This is intended for development use, and not to be enabled unconditionally, as it can generate large amounts of false positives, that require sentient triage intervention

[dpkg] 07/10: build: Warn on alloca() usage

Author: Guillem Jover AuthorDate: Tue Jun 13 22:43:25 2023 +0200 build: Warn on alloca() usage Using alloca() is generally unsafe as there's no error recovery on stack exhaustion, due to the function having no proper way to report such conditions. --- m4/dpkg-compiler.m4 | 1 + 1

[dpkg] 04/10: build: Add support for compiler sanitizer flags

Author: Guillem Jover AuthorDate: Sun Jun 4 23:53:26 2023 +0200 build: Add support for compiler sanitizer flags Add a new configure option to detect and enable these compiler flags and use them when running the unit and functional tests from the CI. --- .gitlab-ci.yml

[dpkg] 06/10: build: Add new gcc-13 warnings

Author: Guillem Jover AuthorDate: Mon Jun 5 22:47:25 2023 +0200 build: Add new gcc-13 warnings --- m4/dpkg-compiler.m4 | 2 ++ 1 file changed, 2 insertions(+) diff --git a/m4/dpkg-compiler.m4 b/m4/dpkg-compiler.m4 index 69a8b872a..1626407cc 100644 --- a/m4/dpkg-compiler.m4 +++ b/m4/dpkg

[dpkg] 02/10: test: Fix varbuf memory leak in t-pkg-format test

Author: Guillem Jover AuthorDate: Sat Jul 8 19:10:51 2023 +0200 test: Fix varbuf memory leak in t-pkg-format test Warned-by: gcc ASAN --- lib/dpkg/t/t-pkg-format.c | 1 + 1 file changed, 1 insertion(+) diff --git a/lib/dpkg/t/t-pkg-format.c b/lib/dpkg/t/t-pkg-format.c index a6d33feb6

[dpkg] 03/10: build: Namespace COMPILER_*FLAGS with DPKG_

Author: Guillem Jover AuthorDate: Mon Jun 5 18:01:35 2023 +0200 build: Namespace COMPILER_*FLAGS with DPKG_ Make it clear these are flags for dpkg itself. --- m4/dpkg-compiler.m4 | 10 ++ 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/m4/dpkg-compiler.m4 b/m4/dpkg

[dpkg] 08/10: build: Remove distcleancheck_listfiles override for CPAN dist-cpan target

Author: Guillem Jover AuthorDate: Tue Jun 27 01:22:59 2023 +0200 build: Remove distcleancheck_listfiles override for CPAN dist-cpan target The dist-cpan target was a dependency for the dist-hook target, the problem was that the dist-cpan target generates an artifact on the build

[dpkg] 02/09: doc: Fix typo

Author: Guillem Jover AuthorDate: Sun Jun 25 00:47:25 2023 +0200 doc: Fix typo Warned-by: codespell --- ChangeLog.old | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ChangeLog.old b/ChangeLog.old index 73542c585..660c473fb 100644 --- a/ChangeLog.old +++ b/ChangeLog.old

[dpkg] 06/09: test: Update cppcheck suppressions for 2.11

Author: Guillem Jover AuthorDate: Sun Jun 25 23:28:50 2023 +0200 test: Update cppcheck suppressions for 2.11 Warned-by: cppcheck --- t/cppcheck/cppcheck.supp | 3 +++ 1 file changed, 3 insertions(+) diff --git a/t/cppcheck/cppcheck.supp b/t/cppcheck/cppcheck.supp index 4ed6c2191

[dpkg] 01/09: test: Add new stop words for codespell 2.2.5

Author: Guillem Jover AuthorDate: Sun Jun 25 00:47:02 2023 +0200 test: Add new stop words for codespell 2.2.5 Warned-by: codespell --- t/codespell/stopwords | 1 + 1 file changed, 1 insertion(+) diff --git a/t/codespell/stopwords b/t/codespell/stopwords index 2360eae9e..0284472da 100644

[dpkg] 09/09: dselect: Add constVariableReference as a cppcheck suppression

-> main) Author: Guillem Jover AuthorDate: Sun Jun 25 23:31:06 2023 +0200 dselect: Add constVariableReference as a cppcheck suppression In cppcheck version 2.11 the constVariable has been split into multiple checks, so we need to also suppress the new name for the alre

<    1   2   3   4   5   6   7   8   9   10   >