Your message dated Thu, 16 Jan 2025 15:21:16 +0200
with message-id <Z4kHzHEujYX9s0AA@localhost>
and subject line Re: Bug#1093008: Please disable the check for upstream updates
has caused the Debian Bug report #1093008,
regarding Please disable the check for upstream updates
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.)
--
1093008: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1093008
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: glab
Version: 1.49.0-1+b1
Severity: normal
X-Debbugs-Cc: [email protected]
glab has a check for upstream updates, which takes a while to run, and
which isn't helpful for the Debian-packaged version. Please consider
disabling it.
-- System Information:
Debian Release: trixie/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: arm64
Kernel: Linux 6.12.8-amd64 (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages glab depends on:
ii libc6 2.40-5
glab recommends no packages.
glab suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
On Thu, Jan 16, 2025 at 02:04:53PM +0100, Nicolas Schier wrote:
> On Thu, Jan 16, 2025 at 10:18:13AM +0200, Josh Triplett wrote:
> > Nicolas Schier wrote:
> > > in glab v1.49 we have a patch that sets the default value for glab
> > > update checks to false. So, if glab creates an initial configuration
> > > file, update checks are disabled by default. The idea is, that those
> > > who want these update checks (e.g. myself as I want to know whether our
> > > glab version is still up-to-date), can simply enable it by updating the
> > > config file.
> > >
> > > Do you have strong argument for completely disabling the update checks
> > > by removing the possibility to enable them manually?
> >
> > No, having them disabled by default is quite sufficient. However, I'm
> > using 1.49 and they don't seem to be disabled by default. I had to
> > change the configuration setting myself.
>
> oh? Could you please try it once again:
>
> mv .config/glab-cli/config.yml .config/glab-cli/config.yml.orig
>
> glab version
> # glab should only output its installed version 1.49.0, no infos
> # about the newer upstream version
>
> mv .config/glab-cli/config.yml.orig .config/glab-cli/config.yml
>
> On my systems it works as expected (w/o upstream update check).
I just realized that you were saying your patch works by *changing the
configuration file written out by default*. It does indeed work exactly
as you said, and I now know why it had seemed like it hadn't worked as
expected.
Before installing the Debian-packaged glab, I tried the upstream binary
once, and it must have written out a config file.
(Pet peeve: This is one of many reasons why tools shouldn't write out
configuration files that contain every option, only the ones the user
has changed.)
Closing this, and thank you for the debugging assistance.
--- End Message ---
