Bug#1102405: RFS: bluraybackup/2.0-1 -- Backup BDMV from the command line
On Mon, 28 Apr 2025 22:16:21 +0200 Matteo Bini <matteobin@tiepi.it> wrote:
> Hi Phil,
> thanks for your message.
>
> On 2025-04-10 14:27, Phil Wyett wrote:
> > Would you consider pulling from releases that are part of the upstream
> > git repo?
>
> Unfortunately, the git repo bluraybackup is hosted on is having crawl
> problems due to AI bots. I've changed the watch scan URL to plain FTP on
> another server, while the git administrators find a way to fix those
> issues. They are experimenting with a JavaScript CAPTCHA that may broke
> uscan. FTP is pretty easy to set up and secure for this kind of task.
> Moreover TLS wouldn't add any extra safety since all bluraybackup info
> is public and it wouldn't protect from release forgery.
>
> > It would be nice to have upstream bug reporting ability, possibly?
>
> Upstream is just me. Would an email address or maybe the Debian BTS
> package URL suffice?
>
The fields for 'debian/upstream/metadata' are at the below link.
https://dep-team.pages.debian.net/deps/dep12/
The 'Bug-Submit' field is for a URL only and an email cannot be used, in my
opinion restrictive. Looking at the document currently we rely on the 'Upstream-
Contact' field in 'debian/copyright'.
For the time being until your source host is better able to handle such
services, we are left to rely on the data you have placed in 'debian/copyright'
for upstream metadata for contact/bug reporting information.
> > The 'Standards-Version' has been update but is not reflected in
> > 'debian/changelog'. Would you consider updating the changelog?
>
> I've updated the changelog to better reflect all the changes occurred to
> the Debian package from version 1.0-1 to 2.0-1.
>
> Changes since the last upload:
>
> bluraybackup (2.0-1) unstable; urgency=low
> .
> * New upstream release.
> * debian/control:
> - Bump Standards-Version to 4.7.2.
> - Update Description to reflect change from C99 to ANSI C (C89).
> * debian/upstream/metadata:
> - Remove deprecated Name and Contact fields
Reply to: