Your message dated Fri, 13 Sep 2019 16:34:36 +0000
with message-id <[email protected]>
and subject line Bug#932849 fixed in ftp.debian.org
has caused the Debian Bug report #932849,
regarding ftp.debian.org: `dak process-policy new` loses .buildinfo files
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
932849: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932849
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: ftp.debian.org
Severity: normal

hi,

<h01ger> 
https://tracker.debian.org/news/1027072/accepted-liblogger-simple-perl-20-1-source-all-into-unstable-unstable/
 says this upload was made with a .buildinfo file, yet this .buildinfo file 
isnt available
<h01ger> this was on 2019-02-04
<h01ger> any idea why this could have happened?
<jrtc27> process_new loses them
<h01ger> really?
<jrtc27> the buildinfo copying happens here 
https://salsa.debian.org/ftp-team/dak/blob/master/dak/process_upload.py#L270
<jrtc27> which isn't on the NEW->policy->ACCEPT path
<h01ger> thanks. i would have accepted a 'yes' but this is "better" :/
<h01ger> i guess i will file a bug now
<jrtc27> tar tf /srv/ftp-master.debian.org/queue/done/2019/02.tar.xz  | grep 
liblogger-simple-perl
<jrtc27> 02/04/liblogger-simple-perl_2.0-1_amd64.changes
<jrtc27> 02/04/liblogger-simple-perl_2.0-1_amd64.buildinfo
<jrtc27> they're still retrievable, just not as friendly
<h01ger> lol/thank you!
       * h01ger lols at bremner mubling next to him
<h01ger> jrtc27: may i quote you in that bug to be filed?
<jrtc27> yeah please do
<jrtc27> meant to report one last time I ran into this...
<h01ger> thank you, again! :)
       * h01ger hopes that would be an easy patch
<jrtc27> probably, for someone who knows the detailed code structure for NEW
<jrtc27> that's one part of dak that I haven't really fully understood
<h01ger> isnt it just adding a 'cp $buildinfofile $path/$date/' somewhere?
<jrtc27> sure
<h01ger> (in python, of course)
<jrtc27> a call to the existing function
<jrtc27> the question is where exactly though
<jrtc27> :)


thanks for maintaining ftp.d.o!


-- 
cheers,
        Holger

-------------------------------------------------------------------------------
               holger@(debian|reproducible-builds|layer-acht).org
       PGP fingerprint: B8BF 5413 7B09 D35C F026 FE9D 091A B856 069A AA1C

Attachment: signature.asc
Description: PGP signature


--- End Message ---
--- Begin Message ---
Hello,

Bug #932849 in ftp.debian.org reported by you has been fixed in the Git 
repository.
You can see the commit message below and you can check the diff of the fix at:

https://salsa.debian.org/ftp-team/dak/commit/e29d4c4dca77aea5555aac7a5ea7f665efec688f

------------------------------------------------------------------------
Copy buildinfo files from NEW to BuildinfoArchive

Closes: #932849
------------------------------------------------------------------------

(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/932849

--- End Message ---

Reply via email to