GNU bug report logs - #78135
[PATCH tex-team] gnu: texstudio: Update to 4.8.7.

Previous Next

To reply to this bug, email your comments to 78135 AT debbugs.gnu.org.
There is no need to reopen the bug first.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Greg Hogan <code <at> greghogan.com>
To: guix-patches <at> gnu.org
Cc: Greg Hogan <code <at> greghogan.com>
Subject: [PATCH tex-team] gnu: texstudio: Update to 4.8.7.
Date: Tue, 29 Apr 2025 14:16:25 +0000

* gnu/packages/tex.scm (texstudio): Update to 4.8.7.

Change-Id: Ia8ebfca22da6a05225601560d7295f30d9dff18a
---
 gnu/packages/tex.scm | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/gnu/packages/tex.scm b/gnu/packages/tex.scm
index 04632e8408..e4b8943e57 100644
--- a/gnu/packages/tex.scm
+++ b/gnu/packages/tex.scm
@@ -71822,7 +71822,7 @@ (define-public texmaker
 (define-public texstudio
   (package
     (name "texstudio")
-    (version "4.8.2")
+    (version "4.8.7")
     (source (origin
               (method git-fetch)
               (uri (git-reference
@@ -71831,7 +71831,7 @@ (define-public texstudio
               (file-name (git-file-name name version))
               (sha256
                (base32
-                "1grkvwh174a2dx19w6wlkhq2adj6g2myy31f5hji7kxw4ks759xb"))))
+                "1z17j1wggs8fgjqk0mrqqwh7xcsmzckfhlpwc7aykr65ii4gqizz"))))
     (build-system qt-build-system)
     (arguments
      `(#:tests? #f))                    ;tests work only with debug build

base-commit: 32bc7695b50a2018f15618a86d7200fc8c3e2f58
-- 
2.49.0

Message #8 received at 78135 <at> debbugs.gnu.org (full text, mbox):

From: Nicolas Goaziou <mail <at> nicolasgoaziou.fr>
To: Greg Hogan <code <at> greghogan.com>
Cc: 78135 <at> debbugs.gnu.org, Andreas Enge <andreas <at> enge.fr>,
 Nicolas Goaziou <guix <at> nicolasgoaziou.fr>
Subject: Re: [bug#78135] [PATCH tex-team] gnu: texstudio: Update to 4.8.7.
Date: Tue, 29 Apr 2025 17:24:19 +0200

Hello,

Greg Hogan <code <at> greghogan.com> writes:

> * gnu/packages/tex.scm (texstudio): Update to 4.8.7.

Thank you.

Note that you already updated it to 4.8.6 on "tex-team" branch, which is
hopefully soon to be merged.

I suggest to wait for that to happen and then do the bump to 4.8.7
directly from master. WDYT?

Regards,
-- 
Nicolas Goaziou

Message #11 received at 78135 <at> debbugs.gnu.org (full text, mbox):

From: Greg Hogan <code <at> greghogan.com>
To: Nicolas Goaziou <mail <at> nicolasgoaziou.fr>
Cc: 78135 <at> debbugs.gnu.org, Andreas Enge <andreas <at> enge.fr>,
 Nicolas Goaziou <guix <at> nicolasgoaziou.fr>
Subject: Re: [bug#78135] [PATCH tex-team] gnu: texstudio: Update to 4.8.7.
Date: Tue, 29 Apr 2025 11:36:13 -0400

On Tue, Apr 29, 2025 at 11:24 AM Nicolas Goaziou <mail <at> nicolasgoaziou.fr> wrote:
>
> Hello,
>
> Greg Hogan <code <at> greghogan.com> writes:
>
> > * gnu/packages/tex.scm (texstudio): Update to 4.8.7.
>
> Thank you.
>
> Note that you already updated it to 4.8.6 on "tex-team" branch, which is
> hopefully soon to be merged.
>
> I suggest to wait for that to happen and then do the bump to 4.8.7
> directly from master. WDYT?
>
> Regards,
> --
> Nicolas Goaziou

Yes, I think there is some confusion over team branches and master.
From the documentation [0]: "Any changes that can be made on the
master branch, should be made on the master branch. If a commit can be
split to apply part of the changes on master, this is good to do."

texstudio has no dependent packages, so should be pushed directly to
master. My understanding is that it still needs to be either approved
or pushed by the owning team.

Or maybe it's not confusion, just that QA is generally unhelpful and
teams are using their branches as a replacement. And with no automated
or accurate method to compute the build cost simple patches get lumped
in with complex updates.

Message #14 received at 78135 <at> debbugs.gnu.org (full text, mbox):

From: Andreas Enge <andreas <at> enge.fr>
To: Greg Hogan <code <at> greghogan.com>
Cc: 78135 <at> debbugs.gnu.org, Nicolas Goaziou <guix <at> nicolasgoaziou.fr>,
 Nicolas Goaziou <mail <at> nicolasgoaziou.fr>
Subject: Re: [bug#78135] [PATCH tex-team] gnu: texstudio: Update to 4.8.7.
Date: Tue, 29 Apr 2025 18:54:49 +0200

Hello Greg,

Am Tue, Apr 29, 2025 at 11:36:13AM -0400 schrieb Greg Hogan:
> texstudio has no dependent packages, so should be pushed directly to
> master. My understanding is that it still needs to be either approved
> or pushed by the owning team.

I do not think this is necessary for non-disruptive changes after
verifying, for instance, that they pass QA.

Andreas

Message #17 received at 78135 <at> debbugs.gnu.org (full text, mbox):

From: Nicolas Goaziou <mail <at> nicolasgoaziou.fr>
To: Greg Hogan <code <at> greghogan.com>
Cc: 78135 <at> debbugs.gnu.org, Andreas Enge <andreas <at> enge.fr>,
 Nicolas Goaziou <guix <at> nicolasgoaziou.fr>
Subject: Re: [bug#78135] [PATCH tex-team] gnu: texstudio: Update to 4.8.7.
Date: Tue, 29 Apr 2025 19:12:38 +0200

Hello,

Greg Hogan <code <at> greghogan.com> writes:

> Yes, I think there is some confusion over team branches and master.
> From the documentation [0]: "Any changes that can be made on the
> master branch, should be made on the master branch. If a commit can be
> split to apply part of the changes on master, this is good to do."
>
> texstudio has no dependent packages, so should be pushed directly to
> master. My understanding is that it still needs to be either approved
> or pushed by the owning team.

You are right, it should have been pushed directly to master, not to
tex-team branch. But what is done is done!

> Or maybe it's not confusion, just that QA is generally unhelpful and
> teams are using their branches as a replacement. And with no automated
> or accurate method to compute the build cost simple patches get lumped
> in with complex updates.

It probably depends on the team. For example, there is no accurate
method to compute the build cost of a Rust package update, so the branch
indeed collects all the updates from all Rust packages, although it is
evolving. For other packages, guix refresh gives you a good idea of the
cost of an update.

Also some teams have a clear focus, e.g. updating Gnome. As for the tex
team, it exists because of the large numbers of builds implied by
changes to texlive packages. So it should mainly include
world-rebuilding changes.

Regards,
-- 
Nicolas Goaziou

Message #22 received at 78135-done <at> debbugs.gnu.org (full text, mbox):

From: Nicolas Goaziou <mail <at> nicolasgoaziou.fr>
To: 78135-done <at> debbugs.gnu.org
Cc: Andreas Enge <andreas <at> enge.fr>, Nicolas Goaziou <mail <at> nicolasgoaziou.fr>,
 Greg Hogan <code <at> greghogan.com>
Subject: Re: [PATCH tex-team] gnu: texstudio: Update to 4.8.7.
Date: Thu, 01 May 2025 01:33:26 +0200

Hello,

> Greg Hogan <code <at> greghogan.com> writes:
> 
> > Yes, I think there is some confusion over team branches and master.
> > From the documentation [0]: "Any changes that can be made on the
> > master branch, should be made on the master branch. If a commit can be
> > split to apply part of the changes on master, this is good to do."
> >
> > texstudio has no dependent packages, so should be pushed directly to
> > master. My understanding is that it still needs to be either approved
> > or pushed by the owning team.
> 
> You are right, it should have been pushed directly to master, not to
> tex-team branch. But what is done is done!

I had to rebase the "tex-team" branch, so I removed your previous patch
from there and pushed it directly to master.

Thank you,

Regards,
-- 
Nicolas Goaziou

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.