Your message dated Sat, 14 Mar 2026 17:23:19 +0000
with message-id
<e2e26553a905ced1a38d9838c9e12b9d7444c265.ca...@adam-barratt.org.uk>
and subject line Re: Bug#806853: byhand-win32-loader script TARGET directory
wrong for uploads to sid
has caused the Debian Bug report #806853,
regarding byhand-win32-loader script TARGET directory wrong for uploads to sid
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.)
--
806853: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=806853
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: ftp.debian.org
Severity: important
Dear FTP Masters,
I recently uploaded win32-loader 0.7.11 to unstable with a _source.changes,
resulting in an automated arch:all build.
For a reason not relevant to this bugreport, the final _all.changes as uploaded
by the buildd had 'sid' as suite, and the two "byhand" files
(win32-loader.{exe,txt}) landed in debian/tools/win32-loader/sid/ instead of
…/unstable/.
> # NOTE: it may be better to pass this to the script as a parameter!
> SUITE="$(grep "^Distribution:" "$CHANGES" | awk '{print $2}')"
> case $SUITE in
> "")
> echo "Error: unable to determine suite from Changes file"
> exit 1
> ;;
> unstable|sid)
> : # nothing to do
A simple fix would be to `TARGET="unstable"` here.
> ;;
> *)
> SUITE="${SUITE}-proposed-updates"
> ;;
> esac
I'm likely to upload 0.7.12 soon to fix a premature VCS-Browser change, I'll
therefore wait for this fix, as a test-case.
Cheers,
OdyX
--- End Message ---
--- Begin Message ---
On Thu, 2015-12-03 at 20:42 +0100, Didier 'OdyX' Raboud wrote:
> Le mercredi, 2 décembre 2015, 08.56:42 Didier 'OdyX' Raboud a écrit :
> > I recently uploaded win32-loader 0.7.11 to unstable with a
> > _source.changes, resulting in an automated arch:all build.
> >
> > For a reason not relevant to this bugreport, the final _all.changes
> > as
> > uploaded by the buildd had 'sid' as suite, and the two "byhand"
> > files
> > (win32-loader.{exe,txt}) landed in debian/tools/win32-loader/sid/
> > instead of …/unstable/.
> >
> > I'm likely to upload 0.7.12 soon to fix a premature VCS-Browser
> > change, I'll therefore wait for this fix, as a test-case.
>
> The fix was apparently committed to dak, and the 0.7.12 upload
> apparently landed in …/unstable correctly, thanks!
>
> The …/sid/ directory still needs to be closed though.
The "sid" directory there seems to be long gone.
Regards,
Adam
--- End Message ---
