hi, when I run `makepkg`, it generates a second package with the `-debug` "extension" (eg. `mypackage-w.x.y-z-x86_64.pkg.tar.zst` and `mypackage-debug-w.x.y-z-x86_64.pkg.tar.zst`). I couldn't find anything about this on the wiki : is this a new feature and/or is there a parameter to pass to `makepkg` to avoid building it ? regards, lacsaP.
On 3/7/24 12:34, lacsaP Patatetom wrote:
hi, Hi,
when I run `makepkg`, it generates a second package with the `-debug` "extension" (eg. `mypackage-w.x.y-z-x86_64.pkg.tar.zst` and `mypackage-debug-w.x.y-z-x86_64.pkg.tar.zst`).
I couldn't find anything about this on the wiki : is this a new feature and/or is there a parameter to pass to `makepkg` to avoid building it ?
Debug packages have been introduced in Arch in early 2022. See https://archlinux.org/news/debug-packages-and-debuginfod/
regards, lacsaP.
-- Regards, Robin Candau / Antiz
On Thu, Mar 7, 2024, at 4:38 AM, Robin Candau wrote:
On 3/7/24 12:34, lacsaP Patatetom wrote:
hi, Hi,
when I run `makepkg`, it generates a second package with the `-debug` "extension" (eg. `mypackage-w.x.y-z-x86_64.pkg.tar.zst` and `mypackage-debug-w.x.y-z-x86_64.pkg.tar.zst`).
I couldn't find anything about this on the wiki : is this a new feature and/or is there a parameter to pass to `makepkg` to avoid building it ?
Debug packages have been introduced in Arch in early 2022. See https://archlinux.org/news/debug-packages-and-debuginfod/
regards, lacsaP.
-- Regards, Robin Candau / Antiz
*Attachments:* • OpenPGP_0xFDC3040B92ACA748.asc • OpenPGP_signature.asc
Arch itself may have been generating debug packages since 2022, however it's only recently that makepkg started spitting out debug packages by default. The change was made all the way back in June of last year <https://gitlab.archlinux.org/archlinux/packaging/packages/pacman/-/commit/90bf367e61b4f77f8351d0412be3d0c4ddadb85a>, but was only included in a pacman release at the beginning of February <https://gitlab.archlinux.org/archlinux/packaging/packages/pacman/-/tags/6.0.2-9>, as part of a pkgrel bump. This came as a surprise to me as well, when I had -debug packages start showing up in my personal repository when they had not before, without any changes made on my end. Personally I would have expected some sort of announcement for this change, though there was none.
On 3/7/24 13:21, Ryan Petris wrote:
On Thu, Mar 7, 2024, at 4:38 AM, Robin Candau wrote:
On 3/7/24 12:34, lacsaP Patatetom wrote:
hi, Hi,
when I run `makepkg`, it generates a second package with the `-debug` "extension" (eg. `mypackage-w.x.y-z-x86_64.pkg.tar.zst` and `mypackage-debug-w.x.y-z-x86_64.pkg.tar.zst`).
I couldn't find anything about this on the wiki : is this a new feature and/or is there a parameter to pass to `makepkg` to avoid building it ?
Debug packages have been introduced in Arch in early 2022. See https://archlinux.org/news/debug-packages-and-debuginfod/ <https://archlinux.org/news/debug-packages-and-debuginfod/>
regards, lacsaP.
-- Regards, Robin Candau / Antiz
*Attachments:*
* OpenPGP_0xFDC3040B92ACA748.asc * OpenPGP_signature.asc
Arch itself may have been generating debug packages since 2022, however it's only recently that makepkg started spitting out debug packages by default. The change was made all the way back in June of last year <https://gitlab.archlinux.org/archlinux/packaging/packages/pacman/-/commit/90bf367e61b4f77f8351d0412be3d0c4ddadb85a>, but was only included in a pacman release at the beginning of February <https://gitlab.archlinux.org/archlinux/packaging/packages/pacman/-/tags/6.0.2-9>, as part of a pkgrel bump.
This came as a surprise to me as well, when I had -debug packages start showing up in my personal repository when they had not before, without any changes made on my end.
Personally I would have expected some sort of announcement for this change, though there was none. The news in 2022 said that enabling debug packages for all packages was an ongoing effort, suggesting that such a change would happen sooner or later. But fair enough, I get your point.
If anything, as Christian/gromit already said in a previous mail on that thread, you can disable the debug option in PKGBUILDs/makepkg.conf to avoid -debug packages from being created. -- Regards, Robin Candau / Antiz
Le jeu. 7 mars 2024 à 13:28, Robin Candau <antiz@archlinux.org> a écrit :
On 3/7/24 13:21, Ryan Petris wrote:
On Thu, Mar 7, 2024, at 4:38 AM, Robin Candau wrote:
On 3/7/24 12:34, lacsaP Patatetom wrote:
hi, Hi,
when I run `makepkg`, it generates a second package with the `-debug` "extension" (eg. `mypackage-w.x.y-z-x86_64.pkg.tar.zst` and `mypackage-debug-w.x.y-z-x86_64.pkg.tar.zst`).
I couldn't find anything about this on the wiki : is this a new feature and/or is there a parameter to pass to `makepkg` to avoid building it ?
Debug packages have been introduced in Arch in early 2022. See https://archlinux.org/news/debug-packages-and-debuginfod/ <https://archlinux.org/news/debug-packages-and-debuginfod/>
regards, lacsaP.
-- Regards, Robin Candau / Antiz
*Attachments:*
* OpenPGP_0xFDC3040B92ACA748.asc * OpenPGP_signature.asc
Arch itself may have been generating debug packages since 2022, however it's only recently that makepkg started spitting out debug packages by default. The change was made all the way back in June of last year < https://gitlab.archlinux.org/archlinux/packaging/packages/pacman/-/commit/90bf367e61b4f77f8351d0412be3d0c4ddadb85a>, but was only included in a pacman release at the beginning of February < https://gitlab.archlinux.org/archlinux/packaging/packages/pacman/-/tags/6.0.2-9>, as part of a pkgrel bump.
This came as a surprise to me as well, when I had -debug packages start showing up in my personal repository when they had not before, without any changes made on my end.
Personally I would have expected some sort of announcement for this change, though there was none. The news in 2022 said that enabling debug packages for all packages was an ongoing effort, suggesting that such a change would happen sooner or later. But fair enough, I get your point.
If anything, as Christian/gromit already said in a previous mail on that thread, you can disable the debug option in PKGBUILDs/makepkg.conf to avoid -debug packages from being created.
-- Regards, Robin Candau / Antiz
thank you for your answers. I did see the changes introduced last February in `/etc/makepkg.conf` but I had targeted those related to Rust since my package is "based" on cargo. have a nice day, regards, lacsaP.
If you had the configuration autoreplaced it would mean you never edited it - in which case you'd be building packages on a single thread... Surely not? Martin On Thu, Mar 7, 2024, 14:41 Ryan Petris <ryan@petris.net> wrote:
On Thu, Mar 7, 2024, at 4:38 AM, Robin Candau wrote:
On 3/7/24 12:34, lacsaP Patatetom wrote:
hi, Hi,
when I run `makepkg`, it generates a second package with the `-debug` "extension" (eg. `mypackage-w.x.y-z-x86_64.pkg.tar.zst` and `mypackage-debug-w.x.y-z-x86_64.pkg.tar.zst`).
I couldn't find anything about this on the wiki : is this a new feature and/or is there a parameter to pass to `makepkg` to avoid building it ?
Debug packages have been introduced in Arch in early 2022. See https://archlinux.org/news/debug-packages-and-debuginfod/
regards, lacsaP.
-- Regards, Robin Candau / Antiz
*Attachments:*
- OpenPGP_0xFDC3040B92ACA748.asc - OpenPGP_signature.asc
Arch itself may have been generating debug packages since 2022, however it's only recently that makepkg started spitting out debug packages by default. The change was made all the way back in June of last year <https://gitlab.archlinux.org/archlinux/packaging/packages/pacman/-/commit/90bf367e61b4f77f8351d0412be3d0c4ddadb85a>, but was only included in a pacman release at the beginning of February <https://gitlab.archlinux.org/archlinux/packaging/packages/pacman/-/tags/6.0.2-9>, as part of a pkgrel bump.
This came as a surprise to me as well, when I had -debug packages start showing up in my personal repository when they had not before, without any changes made on my end.
Personally I would have expected some sort of announcement for this change, though there was none.
On Thu, Mar 7, 2024, at 6:45 AM, Martin Rys wrote:
If you had the configuration autoreplaced it would mean you never edited it - in which case you'd be building packages on a single thread... Surely not?
Martin
On Thu, Mar 7, 2024, 14:41 Ryan Petris <ryan@petris.net> wrote:
__ On Thu, Mar 7, 2024, at 4:38 AM, Robin Candau wrote:
On 3/7/24 12:34, lacsaP Patatetom wrote:
hi, Hi,
when I run `makepkg`, it generates a second package with the `-debug` "extension" (eg. `mypackage-w.x.y-z-x86_64.pkg.tar.zst` and `mypackage-debug-w.x.y-z-x86_64.pkg.tar.zst`).
I couldn't find anything about this on the wiki : is this a new feature and/or is there a parameter to pass to `makepkg` to avoid building it ?
Debug packages have been introduced in Arch in early 2022. See https://archlinux.org/news/debug-packages-and-debuginfod/
regards, lacsaP.
-- Regards, Robin Candau / Antiz
*Attachments:* • OpenPGP_0xFDC3040B92ACA748.asc • OpenPGP_signature.asc
Arch itself may have been generating debug packages since 2022, however it's only recently that makepkg started spitting out debug packages by default. The change was made all the way back in June of last year <https://gitlab.archlinux.org/archlinux/packaging/packages/pacman/-/commit/90bf367e61b4f77f8351d0412be3d0c4ddadb85a>, but was only included in a pacman release at the beginning of February <https://gitlab.archlinux.org/archlinux/packaging/packages/pacman/-/tags/6.0.2-9>, as part of a pkgrel bump.
This came as a surprise to me as well, when I had -debug packages start showing up in my personal repository when they had not before, without any changes made on my end.
Personally I would have expected some sort of announcement for this change, though there was none.
Prior to needing to modify options, my changes to makepkg consisted of: echo 'MAKEFLAGS="-j$(nproc)"' >> /etc/makepkg.conf So yes, it's possible. On that note, I'm building my packages using standard github actions; I don't believe those are multi-threaded anyway.
Le jeu. 7 mars 2024 à 15:15, Ryan Petris <ryan@petris.net> a écrit :
On Thu, Mar 7, 2024, at 6:45 AM, Martin Rys wrote:
If you had the configuration autoreplaced it would mean you never edited it - in which case you'd be building packages on a single thread... Surely not?
Martin
On Thu, Mar 7, 2024, 14:41 Ryan Petris <ryan@petris.net> wrote:
On Thu, Mar 7, 2024, at 4:38 AM, Robin Candau wrote:
On 3/7/24 12:34, lacsaP Patatetom wrote:
hi, Hi,
when I run `makepkg`, it generates a second package with the `-debug` "extension" (eg. `mypackage-w.x.y-z-x86_64.pkg.tar.zst` and `mypackage-debug-w.x.y-z-x86_64.pkg.tar.zst`).
I couldn't find anything about this on the wiki : is this a new feature and/or is there a parameter to pass to `makepkg` to avoid building it ?
Debug packages have been introduced in Arch in early 2022. See https://archlinux.org/news/debug-packages-and-debuginfod/
regards, lacsaP.
-- Regards, Robin Candau / Antiz
*Attachments:*
- OpenPGP_0xFDC3040B92ACA748.asc - OpenPGP_signature.asc
Arch itself may have been generating debug packages since 2022, however it's only recently that makepkg started spitting out debug packages by default. The change was made all the way back in June of last year <https://gitlab.archlinux.org/archlinux/packaging/packages/pacman/-/commit/90bf367e61b4f77f8351d0412be3d0c4ddadb85a>, but was only included in a pacman release at the beginning of February <https://gitlab.archlinux.org/archlinux/packaging/packages/pacman/-/tags/6.0.2-9>, as part of a pkgrel bump.
This came as a surprise to me as well, when I had -debug packages start showing up in my personal repository when they had not before, without any changes made on my end.
Personally I would have expected some sort of announcement for this change, though there was none.
Prior to needing to modify options, my changes to makepkg consisted of:
echo 'MAKEFLAGS="-j$(nproc)"' >> /etc/makepkg.conf
So yes, it's possible.
On that note, I'm building my packages using standard github actions; I don't believe those are multi-threaded anyway.
idem for me. but I build packages very occasionally, so it's not a problem for me (I'll have a coffee in the meantime;-)).
hi,
when I run `makepkg`, it generates a second package with the `-debug` "extension" (eg. `mypackage-w.x.y-z-x86_64.pkg.tar.zst` and `mypackage-debug-w.x.y-z-x86_64.pkg.tar.zst`).
I couldn't find anything about this on the wiki : is this a new feature and/or is there a parameter to pass to `makepkg` to avoid building it ?
regards, lacsaP.
You are building a split package [0]. Thats a feature, not a bug. [0] https://man.archlinux.org/man/PKGBUILD.5#PACKAGE_SPLITTING
On 3/7/24 12:38, Georg wrote:
hi,
when I run `makepkg`, it generates a second package with the `-debug` "extension" (eg. `mypackage-w.x.y-z-x86_64.pkg.tar.zst` and `mypackage-debug-w.x.y-z-x86_64.pkg.tar.zst`).
I couldn't find anything about this on the wiki : is this a new feature and/or is there a parameter to pass to `makepkg` to avoid building it ?
regards, lacsaP.
You are building a split package [0]. Thats a feature, not a bug.
[0] https://man.archlinux.org/man/PKGBUILD.5#PACKAGE_SPLITTING
That's not a split package, it's a package built with debug symbols for analyses and debugging purposes. See https://wiki.archlinux.org/title/Debuginfod for more info. -- Regards, Robin Candau / Antiz
On 3/7/24 12:41, Robin Candau wrote:
On 3/7/24 12:38, Georg wrote:
hi,
when I run `makepkg`, it generates a second package with the `-debug` "extension" (eg. `mypackage-w.x.y-z-x86_64.pkg.tar.zst` and `mypackage-debug-w.x.y-z-x86_64.pkg.tar.zst`).
I couldn't find anything about this on the wiki : is this a new feature and/or is there a parameter to pass to `makepkg` to avoid building it ?
regards, lacsaP.
You are building a split package [0]. Thats a feature, not a bug.
[0] https://man.archlinux.org/man/PKGBUILD.5#PACKAGE_SPLITTING
That's not a split package, it's a package built with debug symbols for analyses and debugging purposes. See https://wiki.archlinux.org/title/Debuginfod for more info. Err, I meant https://wiki.archlinux.org/title/Debugging/Getting_traces
-- Regards, Robin Candau / Antiz
That's not a split package, it's a package built with debug symbols for analyses and debugging purposes. See https://wiki.archlinux.org/title/Debuginfod for more info.
I see, thanks. Sorry for the confusion.
On 24/03/07 12:34PM, lacsaP Patatetom wrote:
hi,
Hey,
when I run `makepkg`, it generates a second package with the `-debug` "extension" (eg. `mypackage-w.x.y-z-x86_64.pkg.tar.zst` and `mypackage-debug-w.x.y-z-x86_64.pkg.tar.zst`).
I couldn't find anything about this on the wiki : is this a new feature and/or is there a parameter to pass to `makepkg` to avoid building it ?
This was introduced with the following change in pacman[0], see the documentation for the 'debug' option in makepkg.conf(5): debug Add the user-specified debug flags as specified in DEBUG_CFLAGS and DEBUG_CXXFLAGS to their counterpart buildflags. Creates a separate package containing the debug symbols when used with ‘strip’. So if you want to disable this behaviour you'll have to disable that option in the config.
regards, lacsaP.
regards, gromit [0]: https://gitlab.archlinux.org/archlinux/packaging/packages/pacman/-/merge_req...
On 3/7/24 06:10, Christian Heusel wrote:
This was introduced with the following change in pacman[0], see the documentation for the 'debug' option in makepkg.conf(5):
debug Add the user-specified debug flags as specified in DEBUG_CFLAGS and DEBUG_CXXFLAGS to their counterpart buildflags. Creates a separate package containing the debug symbols when used with ‘strip’.
So if you want to disable this behaviour you'll have to disable that option in the config.
regards, lacsaP.
regards, gromit
[0]: https://gitlab.archlinux.org/archlinux/packaging/packages/pacman/-/merge_req...
New features are generally something that can be enabled if wanted, not something that is forced on an existing build system. For those building packages, they are quite familiar with how to generate a debug package if wanted -- I for one have no use for them and having my system suddenly start generating unwanted debug packages in an unwelcomed surprise. Granted, they are easy enough to disable, but the recent "surprise" changes seem to fly in the face of the Arch "KISS" philosophy. It would seem the far better approach would be to announce the new feature along with the notice to remove the '!' before debug in makepkg.conf rather than foisting the debug packages on everyone and having those that don't want them go re-add the '!' where it was before. Just my $.02, not a complaint, just an observation. -- David C. Rankin, J.D.,P.E.
On Sat, 9 Mar 2024 01:30:26 -0600 "David C. Rankin" <drankinatty@gmail.com> wrote:
New features are generally something that can be enabled if wanted, not something that is forced on an existing build system. For those building packages, they are quite familiar with how to generate a debug package if wanted -- I for one have no use for them and having my system suddenly start generating unwanted debug packages in an unwelcomed surprise.
Granted, they are easy enough to disable, but the recent "surprise" changes seem to fly in the face of the Arch "KISS" philosophy.
"forced on an existing build system" really? This is a simple config file and the defaults changed, nothing has been 'forced on' anyone. This is also in the backup array, so if the file has been modified at all, you would get a .pacnew. You're seriously claiming that changing config file defaults isn't KISS? Do you know what KISS even means for things like Arch?
On Thu, 2024-03-07 at 12:34 +0100, lacsaP Patatetom wrote:
hi,
when I run `makepkg`, it generates a second package with the `-debug` ...
Right, while makepkg defaults to '!debug' at some point /etc/makepkg.conf set the default to 'debug' instead. Its actually a nice feature if/when you want debug symbols. To stop your own builds making this by default just take the OPTIONS line from /etc/makepkg.conf and put it into your ~/.config/pacman/makepkg.conf and change 'debug' to '!debug'. -- Gene
participants (9)
-
Christian Heusel
-
David C. Rankin
-
Doug Newgard
-
Genes Lists
-
Georg
-
lacsaP Patatetom
-
Martin Rys
-
Robin Candau
-
Ryan Petris