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 > >

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

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,

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

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:

Re: Migration blocked by "Not built on buildd: arch ... binaries uploaded by ..."

On 2019-08-13 08:52, Bas Couwenberg wrote: > > You can request binNMUs for the affected packages, the release team > recently did this for all the packages in unstable. > >  https://release.debian.org/wanna-build.html Thanks a lot! I will look into it. Best, Andrius

Re: Migration blocked by "Not built on buildd: arch ... binaries uploaded by ..."

On 2019-08-13 07:43, mer...@debian.org wrote: After the buster release, all my new packages accepted by FTP Masters become blocked by "Not built on buildd: arch $arch binaries uploaded by $email" (i.e. [1]). How should I remove this blocker? I know that I can get around by doing source only