GNU bug report logs - #40356
Update meson package Description in build-tools.scm

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 40356 in the body.
You can then email your comments to 40356 AT debbugs.gnu.org in the normal way.

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

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

From: Naga Malleswari <nagamalli <at> riseup.net>
To: guix-patches <at> gnu.org
Cc: Danny Milosavljevic <dannym <at> scratchpost.org>,
 Gábor Boskovits <boskovits <at> gmail.com>
Subject: Update meson package Description in build-tools.scm
Date: Wed, 1 Apr 2020 01:40:13 +0530

[Message part 1 (text/plain, inline)]

Hi

I tried to update polari package description in gnome. It resulted unmet
dependency that meson should be greater than .51 where existing package
description was lower. So i have updated the package description in
build-tools.scm and sending the patch. Once this is done i will try
updating polari.


I guess i am following the correct method.

-- 
Regards
NagaMalli

[0001-gnu-Update-meson-to-0.54.0.patch (text/x-patch, attachment)]

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

From: Jonathan Brielmaier <jonathan.brielmaier <at> web.de>
To: Naga Malleswari <nagamalli <at> riseup.net>, 40356 <at> debbugs.gnu.org
Subject: Re: [bug#40356] Update meson package Description in build-tools.scm
Date: Wed, 1 Apr 2020 00:43:01 +0200

On 31.03.20 22:10, Naga Malleswari wrote:
> Hi
>
> I tried to update polari package description in gnome. It resulted unmet
> dependency that meson should be greater than .51 where existing package
> description was lower. So i have updated the package description in
> build-tools.scm and sending the patch. Once this is done i will try
> updating polari.
>
>
> I guess i am following the correct method.

Hello Naga,

yes, you are following the correct method for submitting patches.
Although we already have meson at version 0.53.2, just not in the master
branch yet.

It is only in the core-updates branch:
https://git.savannah.gnu.org/cgit/guix.git/commit/?h=core-updates&id=275f874958ddbbb68ddce93be2cb65bec7ac1bd4

This is due to the fact that many (some thousand) packages depend on
meson. So if we update meson, we have to rebuild all those packages.
This should not happen on the master branch. For more information see
point 8 at
http://guix.gnu.org/manual/en/html_node/Submitting-Patches.html#Submitting-Patches

Good night
Jonathan

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

From: Naga Malleswari <nagamalli <at> riseup.net>
To: Jonathan Brielmaier <jonathan.brielmaier <at> web.de>, 40356 <at> debbugs.gnu.org
Cc: Danny Milosavljevic <dannym <at> scratchpost.org>,
 Gábor Boskovits <boskovits <at> gmail.com>
Subject: Re: [bug#40356] Update meson package Description in build-tools.scm
Date: Wed, 1 Apr 2020 11:24:09 +0530

Hi

On 01/04/20 4:13 am, Jonathan Brielmaier wrote:
> On 31.03.20 22:10, Naga Malleswari wrote:
>> Hi
>>
>>
>> I guess i am following the correct method.
> Hello Naga,
>
> yes, you are following the correct method for submitting patches.
> Although we already have meson at version 0.53.2, just not in the master
> branch yet.
>
> It is only in the core-updates branch:
> https://git.savannah.gnu.org/cgit/guix.git/commit/?h=core-updates&id=275f874958ddbbb68ddce93be2cb65bec7ac1bd4
Thank you.

I understood the process.  I realize that i have done the same changes
like the patch you have given as well.

This means i can go ahead with similar process to update any packages on
the basis of the manual you shared below.

I suppose i cannot update Polari in gnome.scm as well until the
core-updates branch merges with master.


>
> This is due to the fact that many (some thousand) packages depend on
> meson. So if we update meson, we have to rebuild all those packages.
> This should not happen on the master branch. For more information see
> point 8 at
> http://guix.gnu.org/manual/en/html_node/Submitting-Patches.html#Submitting-Patches

I now understood why this happened. Ealier when i went through this
manual i couldnt get the essence of it.


Do I have to close this issue as it is no longer relavent.

>
> Good night
> Jonathan
>
>
-- 
Regards
NagaMalli

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

From: Jonathan Brielmaier <jonathan.brielmaier <at> web.de>
To: 40356 <at> debbugs.gnu.org
Subject: Update meson package Description in build-tools.scm
Date: Fri, 15 May 2020 10:31:41 +0200

You can close the issue by sending a mail to 40356-done <at> debbugs.gnu.org

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

From: Christopher Baines <mail <at> cbaines.net>
To: 40356-done <at> debbugs.gnu.org
Subject: Re: [bug#40356] Update meson package Description in build-tools.scm
Date: Sat, 21 Nov 2020 09:50:04 +0000

[Message part 1 (text/plain, inline)]

Naga Malleswari <nagamalli <at> riseup.net> writes:

> Do I have to close this issue as it is no longer relavent.

Closing, as it sounds like this isn't relevant any longer.

[signature.asc (application/pgp-signature, inline)]

Previous Next

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