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

Bug#900640: marked as done (garmin-forerunner-tools: Lots of URLs/addresses are incorrect)

Your message dated Sun, 19 Sep 2021 23:49:41 +0200
with message-id <2662790.cEtkglPLf8@bagend>
and subject line Re: garmin-forerunner-tools: Lots of URLs/addresses are incorrect
has caused the Debian Bug report #900640,
regarding garmin-forerunner-tools: Lots of URLs/addresses are incorrect
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 owner@bugs.debian.org
immediately.)


-- 
900640: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900640
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: garmin-forerunner-tools
Version: 0.10repacked-10+b1
Severity: normal

As the maintainer address is no longer functional (see #899519), I'm
sending it (also) directly to the listed maintainers.
Hopefully that's not (too) inappropriate.

I recently bought a Garmin Forerunner 645 Music and found this package,
but noticed several issues on its package tracker page,
https://tracker.debian.org/pkg/garmin-forerunner-tools.

- As listed above and in #899519, the maintainer address no longer
  works.
- The upstream web homepage is listed as
  http://garmintools.googlecode.com/ but that gives a 404. There is one
  that works (https://code.google.com/archive/p/garmintools/) but that's
  purely an archived version, so not very useful either.
  Through some detours I found that https://github.com/jorgesca/garmintools
  is now listed as the new upstream. But other then an import of that same 
  code, there isn't much/any difference. It does contain the original 
  issues though, which does seem useful.
  Searching on GitHub (https://github.com/search?q=garmintools) I found
  several others and looking through various of them, it looks like
  https://github.com/phako/garmintools is the one with various new
  commits added to them, most recently on 2018-02-23.
  OTOH it also contains a commit removing HURD ifdefs.
  I could of course create yet another repo and cherrypick various
  commits from various repos, but that'll create https://xkcd.com/927/.
- The VCS Browse URL points to
  https://git.debian.org/?p=pkg-running/garmin-forerunner-tools.git;a=summary
  but when opening that page you get a message that alioth is
  discontinued. I tried searching on https://salsa.debian.org/ but
  couldn't find garmin-forerunner-tools or pkg-running.
- I did find https://alioth-archive.debian.org/git/pkg-running/ which
  contains an archived copy of pkg-running and its sub-repos, including
  the repo for this package.

Looking through 
https://qa.debian.org/developer.php?email=pkg-running-devel%40lists.alioth.debian.org
it looks like the other pkg-running packages are in a similar, not so 
great, state but I hope there's still interest in improving things :).

Cheers,
  Diederik


-- System Information:
Debian Release: buster/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'), (101, 'experimental'), (1, 'experimental-debug')
Architecture: amd64 (x86_64)

Kernel: Linux 4.16.0-2-amd64 (SMP w/16 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages garmin-forerunner-tools depends on:
ii  libc6             2.27-3
ii  libusb-1.0-0      2:1.0.22-2
ii  libusb-1.0-0-dev  2:1.0.22-2

garmin-forerunner-tools recommends no packages.

garmin-forerunner-tools suggests no packages.

-- no debconf information

--- End Message ---
--- Begin Message --- 
Version: 0.10repacked-12

AFAICT all URLs have been fixed now. Thanks!

Attachment: signature.asc
Description: This is a digitally signed message part.


--- End Message ---
Reply to: