I'm not sure about dupload, but at least dput has a configuration file which defines the upload targets.
Maybe just copy the configuration from elgar? Was the buildd actually able to successfully sign the changes file? The buildd also didn't upload the log file for python_3.4. I guess that's related to the dupload problem, isn't it? PS: Sorry for the bad posting style. Currently on mobile in the Biergarten. Adrian > On Apr 19, 2014, at 3:46 PM, Ingo Jürgensmann <[email protected]> wrote: > >> Am 19.04.2014 um 15:18 schrieb Ingo Jürgensmann <[email protected]>: >> >> The new buildd pacman just built its first package. Unfortunately there >> seems to be a problem with uploading it: > > Some more information: > > buildd@pacman:~$ dupload -d -k --to dports > python3.4_3.4.0+20140417-1_m68k.changes > dupload fatal error: Nothing known about host dports > at /usr/bin/dupload line 148 > > Apparently it doesn't know about dupload_archive_name => "dports". For > whatever reason this is. > > -- > Ciao... // http://blog.windfluechter.net > Ingo \X/ XMPP: [email protected] > > > gpg pubkey: http://www.juergensmann.de/ij_public_key.asc > > > -- > To UNSUBSCRIBE, email to [email protected] > with a subject of "unsubscribe". Trouble? Contact [email protected] > Archive: > https://lists.debian.org/[email protected] -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: https://lists.debian.org/[email protected]
