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

unexpected NMUs || buildd queue



Hello.

I've got two questions.

1) Did something change with sponsored uploads?
   Two of mine latest updated packages has been uploaded as NMU.
   I didn't have such problems sooner.
   This packages were uploaded by two independent sponsors, and one of them
   didn't answer me yet, and second has no idea why it was qualified as NMU.
   
   Could you tell me what is the correct way to make sponsored upload?
   Does rebuilding package and signed it with official DD's key is enough?
   Do I have to add my sponsor to Uploaders line?
   Developers' Reference describes only rebuilding with proper -k switch.
   Am I missing something?

2) Does buildd repects order of uploaded packages?
   I mean I uploaded (via sponsor of course cause I'm not DD yet) libphysfs
   package. Then I was waiting three days (iirc) and uploaded package which
   depends on it (paragui).
   I was very surprised when I noticed that paragui was built *before*
   libphysfs and of course it fails to build because of lack of dependencies.
   That however only happened on Alpha arch which had (has?) some problems
   last days.

   In addition firstly uploaded package hasn't been built yet.

   So my question is. Does buildd respect order of uploaded packages?
   Does it build it in the same order?
   
   Here are buildd logs from the mentioned packages:

   http://buildd.debian.org/build.php?pkg=libphysfs
   http://buildd.debian.org/build.php?pkg=libparagui1.0

I'll be very thankful of any comments regarding my doubts.
And please forgive me if these is obvious things, but I didn't find them in
any documentation. 

regards
fEnIo

-- 
      _      Bartosz Fenski | mailto:fenio@o2.pl | pgp:0x13fefc40 | IRC:fEnIo
    _|_|_     32-050 Skawina - Glowackiego 3/15 - w. malopolskie - Polska
    (0 0)          phone:+48602383548 | Slackware - the weakest link
ooO--(_)--Ooo  http://skawina.eu.org | JID:fenio@jabber.org | RLU:172001

Attachment: signature.asc
Description: Digital signature


Reply to: