From: Jonathan Brielmaier <jonathan.brielmaier@web.de>
To: Naga Malleswari <nagamalli@riseup.net>, 40356@debbugs.gnu.org
Subject: [bug#40356] Update meson package Description in build-tools.scm
Date: Wed, 1 Apr 2020 00:43:01 +0200 [thread overview]
Message-ID: <3b9eae2e-9f13-0eb6-9d52-fae632b6e39b@web.de> (raw)
In-Reply-To: <4168bbe0-8839-2901-4318-8a717946801c@riseup.net>
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
next prev parent reply other threads:[~2020-03-31 22:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-31 20:10 [bug#40356] Update meson package Description in build-tools.scm Naga Malleswari
2020-03-31 22:43 ` Jonathan Brielmaier [this message]
2020-04-01 5:54 ` Naga Malleswari
2020-11-21 9:50 ` bug#40356: " Christopher Baines
2020-05-15 8:31 ` [bug#40356] " Jonathan Brielmaier
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3b9eae2e-9f13-0eb6-9d52-fae632b6e39b@web.de \
--to=jonathan.brielmaier@web.de \
--cc=40356@debbugs.gnu.org \
--cc=nagamalli@riseup.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).