Hello dear developers,
to fix a critical bug on scsitools package (0.8-1), I'm willing to
upload a new revision of my package to stable but it was rejected by
dinstall merely because I targeted it only to stable but no newer
release is available in testing/unstable.
Although I'm working on a new release of scsitools for unstable to fix
more bugs, I'd rather want to upload a simple fix to address the
critical bug first. This is why I tried to upload to stable, with no
success.
So is there a chance to get it accepted if I target it both to stable
and unstable at once ? Is autobuilder so nice to build all
architectures under a stable chroot then ?
Or do I need to upload to unstable first (0.8-2 for instance) then try
again an upload targeted only to stable (named 0.8-1sarge for example) ?
Here is the message sent back to me by dinstall:
Mapping stable to proposed-updates.
Rejected: scsitools_0.8-1sarge_i386.deb: old version (0.8-1) in unstable <= new
version (0.8-1sarge) targeted at proposed-updates.
Rejected: scsitools_0.8-1sarge_i386.deb: old version (0.8-1) in testing <= new
version (0.8-1sarge) targeted at proposed-updates.
Rejected: scsitools_0.8-1sarge.dsc: old version (0.8-1) in unstable <= new
version (0.8-1sarge) targeted at proposed-updates.
Rejected: scsitools_0.8-1sarge.dsc: old version (0.8-1) in testing <= new
version (0.8-1sarge) targeted at proposed-updates.
Regards.
E.D.
PS: please cc: me as I'm not reading debian-devel every days.
--
Eric Delaunay | Il vaut mieux pomper même s'il ne se passe
[EMAIL PROTECTED] | rien que risquer qu'il se passe quelque chose
| de pire en ne pompant pas. Devise Shadok.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
