Your message dated Tue, 25 Nov 2025 18:13:44 -0500 with message-id <caaajcmb-zkudbvezw9u4-t_dvenvxnowrmpcg3gri0vxfrx...@mail.gmail.com> and subject line Re: qa.debian.org: DDPO watch page shows error while uscan working locally has caused the Debian Bug report #1081249, regarding qa.debian.org: DDPO watch page shows error while uscan working locally 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.) -- 1081249: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1081249 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: qa.debian.org Severity: normal Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** The watch page for one of my package emacs-bazel-mode reports "error: failed to parse XML:"[1]. However, locally uscan works fine for me (tried both --report-status and --force-download). The tracker page of the package also shows the same error with "failed to parse XML: <dehs>"[2]. FYI the watch file can be found at [3]. Do let me know if more info is needed. Thanks in advance. [1] https://qa.debian.org/cgi-bin/watch?pkg=emacs-bazel-mode [2] https://tracker.debian.org/pkg/emacs-bazel-mode [3] https://salsa.debian.org/emacsen-team/emacs-bazel-mode/-/blob/master/debian/watch?ref_type=heads -- Xiyue Deng
--- End Message ---
--- Begin Message ---The Debian tools are properly reporting the upstream version for emacs-basel-mode, so I'm closing this bug now. Thank you, Jeremy Bícha
--- End Message ---
