[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1120289: trixie-pu: magit/4.3.5-1+deb13u1



On Thursday, November 13, 2025 12:01:04 PM Mountain Standard Time Soren 
Stoutner wrote:

> > Soren, I put you into CC because you original added the advice of using
> 
> sbuild
> 
> > with $build_source=1 here:
> > https://wiki.debian.org/sbuild?action=diff&rev1=288&rev2=289
> 
> Thanks for making that change.  I had misunderstood what the option did.

I just needed to do a library transition, involving a binary upload to NEW.  
Without the $build_source entry in my .sbuildrc, it did not produce the 
necessary files.  When uploading the amd64.changes file, this is what was 
sent:

2025-11-17 18:22:22,746 - dput[80807]: uploader.invoke_dput - Uploading 
libsecp256k1 using ftp to ftp-master (host: ftp.upload.debian.org; directory: 
/pub/UploadQueue/)
2025-11-17 18:22:22,746 - dput[80807]: hook.run_hook - running allowed-
distribution: check whether a local profile permits uploads to the target 
distribution
2025-11-17 18:22:22,749 - dput[80807]: hook.run_hook - running protected-
distribution: warn before uploading to distributions where a special policy 
applies
2025-11-17 18:22:22,752 - dput[80807]: hook.run_hook - running checksum: 
verify checksums before uploading
2025-11-17 18:22:22,756 - dput[80807]: hook.run_hook - running suite-mismatch: 
check the target distribution for common errors
2025-11-17 18:22:22,758 - dput[80807]: hook.run_hook - running gpg: check 
GnuPG signatures before the upload
2025-11-17 18:22:23,268 - dput[80807]: uploader.invoke_dput - Uploading 
libsecp256k1-6-dbgsym_0.7.0-1_amd64.deb
2025-11-17 18:22:24,337 - dput[80807]: uploader.invoke_dput - Uploading 
libsecp256k1-6_0.7.0-1_amd64.deb
2025-11-17 18:22:25,385 - dput[80807]: uploader.invoke_dput - Uploading 
libsecp256k1-dev_0.7.0-1_amd64.deb
2025-11-17 18:22:26,806 - dput[80807]: uploader.invoke_dput - Uploading 
libsecp256k1_0.7.0-1_amd64.buildinfo
2025-11-17 18:22:27,317 - dput[80807]: uploader.invoke_dput - Uploading 
libsecp256k1_0.7.0-1_amd64.changes

Which was promptly rejected because it did not contain the source.

With the $build_source entry in my .sbuildrc, uploading the amd64.changes 
performed as expected:

2025-11-17 18:48:55,512 - dput[113547]: uploader.invoke_dput - Uploading 
libsecp256k1 using ftp to ftp-master (host: ftp.upload.debian.org; directory: 
/pub/UploadQueue/)
2025-11-17 18:48:55,513 - dput[113547]: hook.run_hook - running allowed-
distribution: check whether a local profile permits uploads to the target 
distribution
2025-11-17 18:48:55,515 - dput[113547]: hook.run_hook - running protected-
distribution: warn before uploading to distributions where a special policy 
applies
2025-11-17 18:48:55,518 - dput[113547]: hook.run_hook - running checksum: 
verify checksums before uploading
2025-11-17 18:48:55,523 - dput[113547]: hook.run_hook - running suite-
mismatch: check the target distribution for common errors
2025-11-17 18:48:55,525 - dput[113547]: hook.run_hook - running gpg: check 
GnuPG signatures before the upload
2025-11-17 18:48:56,101 - dput[113547]: uploader.invoke_dput - Uploading 
libsecp256k1_0.7.0-1.dsc
2025-11-17 18:48:56,631 - dput[113547]: uploader.invoke_dput - Uploading 
libsecp256k1_0.7.0.orig.tar.gz
2025-11-17 18:48:57,826 - dput[113547]: uploader.invoke_dput - Uploading 
libsecp256k1_0.7.0-1.debian.tar.xz
2025-11-17 18:48:58,365 - dput[113547]: uploader.invoke_dput - Uploading 
libsecp256k1-6-dbgsym_0.7.0-1_amd64.deb
2025-11-17 18:48:59,255 - dput[113547]: uploader.invoke_dput - Uploading 
libsecp256k1-6_0.7.0-1_amd64.deb
2025-11-17 18:49:00,338 - dput[113547]: uploader.invoke_dput - Uploading 
libsecp256k1-dev_0.7.0-1_amd64.deb
2025-11-17 18:49:01,432 - dput[113547]: uploader.invoke_dput - Uploading 
libsecp256k1_0.7.0-1_amd64.buildinfo
2025-11-17 18:49:01,953 - dput[113547]: uploader.invoke_dput - Uploading 
libsecp256k1_0.7.0-1_amd64.changes


Is this the expected behavior?  Is there something else that should be added 
to .sbuildrc instead so that binary uploads are complete?

-- 
Soren Stoutner
soren@debian.org

Attachment: signature.asc
Description: This is a digitally signed message part.


Reply to: