Re: dbgsym metapackages?
On Mon, Aug 12, 2019 at 06:17:02AM +0800, Paul Wise wrote: > On Mon, Aug 12, 2019 at 3:18 AM Ross Vandegrift wrote: > > Make it easier for users/devs to get backtraces for EFL apps. Automatic > > dbgsym > > results in 49 dbgsym packages from src:efl. Getting all of the required > > ones > > for a given backtrace can be a chore. A metapackage occurred to me as a > > possible improvement in the absence of a tool addressing #843466. > > You can use find-dbgsym-packages (from debian-goodies) to get the list > of dbgsym packages needed for a given ELF file or core dump. Oh nice, this is a big improvement. Thanks for the pointer Paul! Ross
Re: Re: concern with pdebuild --pbuilder cowbuilder
On Tue, Aug 13, 2019 at 08:12:42PM +0200, Patrice Duroux wrote: > Ok, you mean before creating the X.debian.tar.xz? Yes, creating the source package from an unpacked dir means creating debian.tar and .dsc. -- WBR, wRAR signature.asc Description: PGP signature
Re: Re: concern with pdebuild --pbuilder cowbuilder
Ok, you mean before creating the X.debian.tar.xz? Because before running pdebuild, uscan was used to provide the X.orig.tar.xz and in the folder where I run pdebuild there is only the debian/* files (without any extra file). I was thinking that pdebuild is somehow a way to build packages from a "read-only" (source) folder, ie. nothing to touch or clean before going! Thanks!
Re: concern with pdebuild --pbuilder cowbuilder
On Tue, Aug 13, 2019 at 03:33:07PM +0200, Patrice Duroux wrote: > It seems that pdebuild somehow calls 'debian/rules' before going to the > pbuilder > environment and so it fails as some build-deps are required to run this > 'debian/rules' but not available in the call environment. Specifically, it calls clean. > Why such a step is not done inside the pbuilder environment if this is > required? Because pbuilder operates on source packages and when creating a source package tools run clean. > Then is there a way to avoid such a step in my case? See pbuilder debuild/pdebuild --use-pdebuild-internal. -- WBR, wRAR signature.asc Description: PGP signature
concern with pdebuild --pbuilder cowbuilder
Hi,
It seems that pdebuild somehow calls 'debian/rules' before going to the pbuilder
environment and so it fails as some build-deps are required to run this
'debian/rules' but not available in the call environment.
In my case it is 'debian/rules' that includes some .mk files that are provided
by the build-deps.
I just found the following lines in the pdebuild script that may be responsible
for this (not sure at all!):
$ grep -H -n -C 3 "rules" /usr/bin/pdebuild
/usr/bin/pdebuild-86-SOURCE_OPTIONS=$(get_source_options)
/usr/bin/pdebuild-87-eval dpkg-source ${SOURCE_OPTIONS} --before-build .
/usr/bin/pdebuild-88-if should_clean_source; then
/usr/bin/pdebuild:89:"${BUILDSOURCEROOTCMD}" debian/rules clean
/usr/bin/pdebuild-90-fi
/usr/bin/pdebuild-91-eval dpkg-source ${SOURCE_OPTIONS} -b .
/usr/bin/pdebuild-92-if ! [ "../${DSC}" -ef "${BUILDRESULT}/${DSC}" ]; then
Why such a step is not done inside the pbuilder environment if this is required?
Then is there a way to avoid such a step in my case?
Thanks,
Patrice
Debian Salsa and NMUs
Hello, I have a question about handling NMUs in Salsa. Are the rules for NMUs disabled there just because a package is in the Debian namespace? Thanks CU Jörg -- New: GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB 30EE 09F8 9F3C 8CA1 D25D GPG key (long) : 09F89F3C8CA1D25D GPG Key: 8CA1D25D CAcert Key S/N : 0E:D4:56 Old pgp Key: BE581B6E (revoked since 2014-12-31). Jörg Frings-Fürst D-54470 Lieser git: https://jff.email/cgit/ Threema: SYR8SJXB Wire: @joergfringsfuerst Skype:joergpenguin Ring: jff Telegram: @joergfringsfuerst My wish list: - Please send me a picture from the nature at your home. signature.asc Description: This is a digitally signed message part
