Hi,
I've submitted a new font package for review [1], but I have 0
experience with fonts (I need it to unbundle it from [2]), and I found
the documentation about font packages a little bit outdated. It's a
pretty simple font (OFL, single family with a couple of styles), but
it would be great if so
Hi all,
FMN (https://apps.fedoraproject.org/notifications) is currently one of the
main blocking point for dropping fedmsg in favour of fedora-messaging.
FMN is quite important to the community and the composition of Fedora
because it gives emails and notifications on commits, composes, builds and
Am Di., 25. Feb. 2020 um 20:37 Uhr schrieb Matthew Miller
:
> > Whereas with 12h clocks, I think midnight is 12:00 PM, and noon is 12:00
> > AM? Which is still confusing me after having known about it for decades.
>
> It's the opposite, which furthers your point. :)
That does not seem to be very c
No missing expected images.
Passed openQA tests: 1/1 (x86_64)
--
Mail generated by check-compose:
https://pagure.io/fedora-qa/check-compose
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedorap
On 2/25/20 3:12 PM, Ankur Sinha wrote:
Basically, packages do not pass review merely because they use good
licenses.
Note that I just said that I thought it was the primary purpose, not the
only purpose.
___
devel mailing list -- devel@lists.fedorap
On Tue, 2020-02-25 at 16:11 +0100, Kevin Kofler wrote:
> Fabio Valentini wrote:
> > The recent update from cantor 19.08 to cantor 12.12 in both fedora 32
> > and rawhide bumped the SONAME of a shared library as mention in
> > $SUBJECT (maintainers in CC).
> >
> > At least LabPlot still needs to be
On 25/2/20 20:54, Richard W.M. Jones wrote:
> On Mon, Feb 24, 2020 at 10:07:15PM -0800, Luya Tshimbalanga wrote:
>> Hello team,
>>
>> It looks like spammers use closed bug report for their ads as seen
>> in this one:
>>
>> https://bugzilla.redhat.com/show_bug.cgi?id=1644013
>>
>> Can someone mainta
* Richard Shaw:
> While API/ABI breaking changes within a release is discouraged, it's
> still might be the right thing to do.
libffi within a Fedora release? That seems rather ... involved because
Python depends on it.
I don't think we'll need ABI changes for CET support, and we plan to
port C
No missing expected images.
Failed openQA tests: 25/160 (x86_64), 1/2 (arm)
New failures (same test not failed in Fedora-32-20200224.n.0):
ID: 527306 Test: x86_64 Server-dvd-iso server_remote_logging_server
URL: https://openqa.fedoraproject.org/tests/527306
ID: 527316 Test: x86_64 Serv
On Tue, 25 Feb 2020 at 12:55, Antonio Trande wrote:
>
> Hi all.
>
> Antimony (https://src.fedoraproject.org/rpms/antimony) is an orphan
> package since today.
Actually, it's orphaned *and retired*. This is not insurmountable for
anyone who wishes to take over, but one does not necessarily imply t
On Tue, Feb 25, 2020, at 2:53 PM, Matthew Miller wrote:
> On Mon, Feb 24, 2020 at 05:48:36PM +0100, Pierre-Yves Chibon wrote:
> > So these are the results of our current investigations, we are very much
> > eager
> > to get your feedback on them and even more eager if you have ideas on how to
> >
On Tue, Feb 25, 2020 at 12:22:10PM -0800, Michel Alexandre Salim wrote:
> > On February 25, 2020 3:38 AM Richard W.M. Jones wrote:
> >
> >
> > In the previous mass build LWT FTBFS because the tests failed on POWER
> > and s/390 (https://bugzilla.redhat.com/1792780). There is also a new
> > ver
> On February 25, 2020 3:38 AM Richard W.M. Jones wrote:
>
>
> In the previous mass build LWT FTBFS because the tests failed on POWER
> and s/390 (https://bugzilla.redhat.com/1792780). There is also a new
> version of LWT (https://bugzilla.redhat.com/1755859). The new version
> is noted as an
No missing expected images.
Compose PASSES proposed Rawhide gating check!
All required tests passed
Failed openQA tests: 18/160 (x86_64), 1/2 (arm)
New failures (same test not failed in Fedora-Rawhide-20200224.n.0):
ID: 527154 Test: x86_64 Server-dvd-iso modularity_tests
URL: https://openq
On Tue, Feb 25, 2020 14:41:34 -0500, Matthew Miller wrote:
> On Mon, Feb 24, 2020 at 10:35:08AM +, Ankur Sinha wrote:
> > > One thing that comes to my mind with this proposal is that we still need
> > > some way to vet licenses. Today, this is done via the package review
> > > process, and in m
Il 24/02/20 23:04, Ben Cotton ha scritto:
> In the weekly Fedora program update that I publish on
> communityblog.fedoraproject.org, I have started to include a count of the
> open package review requests. As of this moment, there are ~1300 open review
> requests. Some of these were opened in 2
On Mon, Feb 24, 2020 at 05:48:36PM +0100, Pierre-Yves Chibon wrote:
> So these are the results of our current investigations, we are very much eager
> to get your feedback on them and even more eager if you have ideas on how to
> approach/solve some of the challenges mentioned here.
This all sound
Thanks for the answer.
I make a comment in the bug.
El mar., 25 feb. 2020 a las 16:42, Scott Talbert ()
escribió:
> On Tue, 25 Feb 2020, Eduard Lucena wrote:
>
> > Hello team,
> >
> > I'm writing this here, because I don't know of any other place, so if
> there
> > is another place to report it,
Hello,
We're drafting a submission to CNS*2020[1] about NeuroFedora. Would
anyone know if there's a way to formally cite RPM?
Google Scholar gives me this document by Mark Ewing and Eric Troan[2]
from 1996. Should one keep citing this, or does someone know a newer
publication that we should use?
On Tue, 25 Feb 2020, Eduard Lucena wrote:
Hello team,
I'm writing this here, because I don't know of any other place, so if there
is another place to report it, I'll listen to go there.
I'm trying to install the package: python3-i3ipc
$ sudo dnf info python3-i3ipc
Last metadata expiration che
On Mon, Feb 24, 2020 at 10:35:08AM +, Ankur Sinha wrote:
> > One thing that comes to my mind with this proposal is that we still need
> > some way to vet licenses. Today, this is done via the package review
> > process, and in my mind is the primary purpose of package review. If we
> > started
On Sat, Feb 22, 2020 at 11:06:30AM +0100, Fabio Valentini wrote:
> I assume 00:00 UTC was confusing for people used to the AM/PM (12h) time
> format instead of the 24h format.
>
> For people used to 24h clocks, it's completely obvious that 00:00 is the
> beginning of the day, and 24:00 is the end
On Mon, Feb 24, 2020 at 05:04:26PM -0500, Ben Cotton wrote:
> The usual Bugzilla housekeeping (branching, EOL closure, etc) explicitly
> excludes review request bugs. Having a large number of open, ancient review
> requests isn't exactly harmful, but it's not very helpful either.
>
> Before I mak
Hello there
Here are the logs for today's meeting.
HTML Logs:
https://meetbot.fedoraproject.org/fedora-neuro/2020-02-25/neurofedora.2020-02-25-16.00.log.html
HTML Minutes:
https://meetbot.fedoraproject.org/fedora-neuro/2020-02-25/neurofedora.2020-02-25-16.00.html
Minutes in plain text are past
Announcing the creation of a new nightly release validation test event
for Fedora 32 Branched 20200225.n.0. Please help run some tests for this
nightly compose if you have time. For more information on nightly
release validation testing, see:
https://fedoraproject.org/wiki
Hello. I have updated the python27 package to use the bundled wheels of pip and
setuptools, so we can update setuptools in rawhide to a version that no longer
works with Python 2.
Unfortunately, that changes the license from "Python" to this beast:
Python and MIT and ASL 2.0 and BSD and ISC an
Hello team,
I'm writing this here, because I don't know of any other place, so if there
is another place to report it, I'll listen to go there.
I'm trying to install the package: python3-i3ipc
$ sudo dnf info python3-i3ipc
Last metadata expiration check: 0:02:42 ago on Tue 25 Feb 2020 02:18:22 P
On Tue, 25 Feb 2020 at 17:07, Michal Schorm wrote:
> Hello,
>
> Will anybody be able to explain to me the current state of the
> containers & containerization in Fedora, please?
>
Hi Michal,
As you mention in the points below the current state of building containers
in Fedora needs a lot of wor
Den tis 25 feb. 2020 kl 16:10 skrev Christophe de Dinechin <
dinec...@redhat.com>:
> Is there any documented procedure to safely downgrade from rawhide to
> the latest release?
>
> I tried
>
> # dnf update --releasever=32 fedora-release
> # dnf distro-sync --allowerasing --skip-broken
>
> Does som
Hi all.
Antimony (https://src.fedoraproject.org/rpms/antimony) is an orphan
package since today.
Feel free to take it.
--
---
Antonio Trande
Fedora Project
mailto 'sagitter at fedoraproject dot org'
GPG key: 0x7B30EE04E576AA84
GPG key server: https://keys.openpgp.org/
signature.asc
Descriptio
On Tue, Feb 25, 2020 at 9:57 AM Anthony Green wrote:
> Hello -- I'm the current Fedora maintainer for libffi, as well as the
> upstream author/maintainer. I'm looking for help with libffi
> packaging. Specifically, we need to roll out a new ABI-breaking
> release (required for ARM64 and Intel
On 25. 02. 20 15:27, Fabio Valentini wrote:
Side note: I've been meaning to propose dropping Epoch because of this
"we don't care about upgrade path anymore", but I've not gotten around
to do that yet
Unfortunately, that breaks rawhide users.
--
Miro Hrončok
--
Phone: +420777974800
IRC: mhronc
Add me as co-maintainer, please.
I'm using libffi as dependency for a couple of packages.
On 25/02/20 16:56, Anthony Green wrote:
> Hello -- I'm the current Fedora maintainer for libffi, as well as the
> upstream author/maintainer. I'm looking for help with libffi
> packaging. Specifically, we
On 25. 02. 20 9:50, Pierre-Yves Chibon wrote:
Upgrade path may be problematic if you update Fn to a version in less commit
than the update for Fn-1 (ie: you update F32 to 1.0 in 1 commit and update F31
to 1.0 in 2 commits, suddenly you have F32 with 1.0-1 and F31 with 1.0-2).
I don't consider t
Hi all,
Please see the latest AAA FAS replacement project update below:
AAA: FAS replacement project update 2/25/20
The month of February was a very busy month for the CPE AAA team and
community contributors working on this initiative. Great progress was made
in the development phase of the AAA
Hidden from sight of any mortal man, I've found 'Fedora Container SIG'
with as little information as possible [1], although they state, they have
notes from 2019 DevConf meetup [2], but locked [3].
Atleast I found first place of discussion! [4]
... if you can say that about bunch of threads with
Hello,
Will anybody be able to explain to me the current state of the
containers & containerization in Fedora, please?
I have some questions, but the more I searched for whom & where to
ask, the more confused I became.
--
1) There ́s an IRC on freenode, '#fedora-containers' channel.
The TOPIC s
Hello -- I'm the current Fedora maintainer for libffi, as well as the
upstream author/maintainer. I'm looking for help with libffi
packaging. Specifically, we need to roll out a new ABI-breaking
release (required for ARM64 and Intel CET support), and I don't have
the volunteer time available to
On Tue, Feb 25, 2020 at 04:09:32PM +0100, Christophe de Dinechin wrote:
> Is there any documented procedure to safely downgrade from rawhide to
> the latest release?
>
> I tried
>
> # dnf update --releasever=32 fedora-release
> # dnf distro-sync --allowerasing --skip-broken
>
> Does something li
Hello there
We will be starting in about 15-20 minutes. It would be great if
people could join the meeting. :D
On Mon, Feb 24, 2020 at 6:48 PM Aniket Pradhan
wrote:
>
> Hey there!
>
> You are invited to attend the next Open NeuroFedora team meeting this
> week on Tuesday at 1600UTC in #fedora-ne
On Tue, 25 Feb 2020 at 10:10, Christophe de Dinechin
wrote:
> Is there any documented procedure to safely downgrade from rawhide to
> the latest release?
>
> I tried
>
> # dnf update --releasever=32 fedora-release
> # dnf distro-sync --allowerasing --skip-broken
>
> Does something like that have
* Christophe de Dinechin:
> Is there any documented procedure to safely downgrade from rawhide to
> the latest release?
>
> I tried
>
> # dnf update --releasever=32 fedora-release
> # dnf distro-sync --allowerasing --skip-broken
>
> Does something like that have any chance of working? At first sig
Is there any documented procedure to safely downgrade from rawhide to
the latest release?
I tried
# dnf update --releasever=32 fedora-release
# dnf distro-sync --allowerasing --skip-broken
Does something like that have any chance of working? At first sight, it
seems to be somewhat successful.
-
Hi all,
Today's an important day on the Fedora 32 schedule[1], with several
significant cut-offs. First of all today is the Bodhi activation point
[2]. That means that from now on all Fedora 32 packages must be
submitted to updates-testing and pass the relevant requirements[3]
before they will be
Fabio Valentini wrote:
> The recent update from cantor 19.08 to cantor 12.12 in both fedora 32
> and rawhide bumped the SONAME of a shared library as mention in
> $SUBJECT (maintainers in CC).
>
> At least LabPlot still needs to be rebuilt on both f32 and rawhide
> (maintainers in CC).
Cantor is
On Tue, Feb 25, 2020 at 3:43 PM Ben Cotton wrote:
>
>
>
> On Mon, Feb 24, 2020, 17:32 Fabio Valentini wrote:
>>
>>
>> It sounds like you are both not aware that there's actually an
>> existing policy that covers stalled Review Requests:
>> https://fedoraproject.org/wiki/Policy_for_stalled_package
On Mon, Feb 24, 2020, 17:32 Fabio Valentini wrote:
>
> It sounds like you are both not aware that there's actually an
> existing policy that covers stalled Review Requests:
> https://fedoraproject.org/wiki/Policy_for_stalled_package_reviews
Ah ha! I thought I remembered seeing something before,
On Tue, Feb 25, 2020 at 3:12 PM Pierre-Yves Chibon wrote:
>
> On Tue, Feb 25, 2020 at 02:55:37PM +0100, Fabio Valentini wrote:
> > On Tue, Feb 25, 2020 at 2:47 PM Remi Collet
> > wrote:
> > >
> > > Le 24/02/2020 à 17:48, Pierre-Yves Chibon a écrit :
> > >
> > > > - You can easily opt-in by usi
On Tue, Feb 25, 2020 at 02:55:37PM +0100, Fabio Valentini wrote:
> On Tue, Feb 25, 2020 at 2:47 PM Remi Collet wrote:
> >
> > Le 24/02/2020 à 17:48, Pierre-Yves Chibon a écrit :
> >
> > > - You can easily opt-in by using the macros
> >
> > Please keep opt-in as a mandatory need for such a change
On Tue, Feb 25, 2020 at 12:59:39PM +0100, Vít Ondruch wrote:
>
> Dne 24. 02. 20 v 17:48 Pierre-Yves Chibon napsal(a):
> > Good Morning Everyone,
> >
> > This topic has already been discussed a few times over the past month, but
> > Adam
> > Saleh, Nils Philippsen and myself have had the opportuni
On Tue, Feb 25, 2020 at 2:47 PM Remi Collet wrote:
>
> Le 24/02/2020 à 17:48, Pierre-Yves Chibon a écrit :
>
> > - You can easily opt-in by using the macros
>
> Please keep opt-in as a mandatory need for such a change.
>
>
> To be clear, I will be (perhaps the only) one to not use it.
>
>
> For
On Sat, Feb 22, 2020 07:03:16 -0800, Erich Eickmeyer wrote:
>
>
> I have had a few people looking at my reviews. After I made corrections and
> posted that info, I have had zero responses on my bugs:
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1801352
> https://bugzilla.redhat.com/show_bug.
Hi,
After some test, is looks like the stream name of a module have to
match the branch name.
I think this constraint doesn't make sense.
We can want different content (.yaml file) for different
distributions (Fedora vs EPEL) or different Version
Reported as https://pagure.io/fedora-infrastruc
Le 24/02/2020 à 17:48, Pierre-Yves Chibon a écrit :
> - You can easily opt-in by using the macros
Please keep opt-in as a mandatory need for such a change.
To be clear, I will be (perhaps the only) one to not use it.
For now spec file are self-contained, which is nice.
I don't like the ide
I have given the project to mhjacks.
On Mon, 24 Feb 2020 at 18:19, Martin Jackson wrote:
>
> I will take them - mhjacks in FAS.
>
> Any other potential comaintainers would also be welcome but I am a fan of the
> stack and would hate to see it disappear from the Fedora ecosystem.
>
> Thanks!
>
>
Dne 25. 02. 20 v 9:55 Pierre-Yves Chibon napsal(a):
> On Mon, Feb 24, 2020 at 10:05:31PM +0100, Miroslav Suchý wrote:
>> Dne 24. 02. 20 v 18:13 Miro Hrončok napsal(a):
>>> Can we please have a "git is the only source of truth" version of this?
>>> I.e. "Compute the release field from the number
>
Dne 24. 02. 20 v 17:48 Pierre-Yves Chibon napsal(a):
> Good Morning Everyone,
>
> This topic has already been discussed a few times over the past month, but
> Adam
> Saleh, Nils Philippsen and myself have had the opportunity to invest some time
> on it with the hope of making the packager's life
On Tue, 25 Feb 2020 at 12:47, clime wrote:
>
> Hey pingou!
>
> On Tue, 25 Feb 2020 at 10:26, Pierre-Yves Chibon wrote:
> >
> > On Tue, Feb 25, 2020 at 12:18:24AM +0100, clime wrote:
> > > Hello!
> > >
> > > What is the point of including number of builds into release? I think
> > > the Miro's app
Hey pingou!
On Tue, 25 Feb 2020 at 10:26, Pierre-Yves Chibon wrote:
>
> On Tue, Feb 25, 2020 at 12:18:24AM +0100, clime wrote:
> > Hello!
> >
> > What is the point of including number of builds into release? I think
> > the Miro's approach solves it.
> > Or is there any other problem except sonam
In the previous mass build LWT FTBFS because the tests failed on POWER
and s/390 (https://bugzilla.redhat.com/1792780). There is also a new
version of LWT (https://bugzilla.redhat.com/1755859). The new version
is noted as an API break, although I don't know how that will affect
other packages.
On Mon, Feb 24, 2020 at 10:07:15PM -0800, Luya Tshimbalanga wrote:
> Hello team,
>
> It looks like spammers use closed bug report for their ads as seen
> in this one:
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1644013
>
> Can someone maintaining bugzilla investigate the issue?
There's a se
On Mon, Feb 24, 2020 at 01:53:37PM -0700, Jerry James wrote:
> On Mon, Feb 24, 2020 at 1:57 AM Richard W.M. Jones wrote:
> > * z3 - https://bugzilla.redhat.com/show_bug.cgi?id=1792740
>
> Actually, z3 should build. I checked in a workaround. The bug is
> still open to remind me to figure out an
No missing expected images.
Passed openQA tests: 1/1 (x86_64)
--
Mail generated by check-compose:
https://pagure.io/fedora-qa/check-compose
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedorap
On Mon, Feb 24, 2020 at 10:36:41AM -0800, Kevin Fenzi wrote:
> On Mon, Feb 24, 2020 at 10:27:44AM +0100, Fabio Valentini wrote:
> > On Mon, Feb 24, 2020 at 9:57 AM Richard W.M. Jones
> > wrote:
> > >
> > > OCaml 4.10.0 was released over the weekend.
> > >
> > > We currently have OCaml 4.10.0 beta
On Mon, Feb 24, 2020 at 10:12:41PM +, Dave Dykstra wrote:
> I made a ticket (bug #1806737) for the maintainer of the existing vault
> package in Fedora to see if he'd be willing to give it up so it can be
> used for Hashicorp vault (https://vaultproject.io) and he decided to
> mark it EOL so I
Le 2020-02-25 10:24, Pierre-Yves Chibon a écrit :
If you make the build system provide the ${dirty_appendix} and drop the
${pivot}
(because we want to generate the release, so there is no input
specified), you
get very close to what we described.
BTW, regardless of how things up, we have exi
On Tue, Feb 25, 2020 at 12:18:24AM +0100, clime wrote:
> Hello!
>
> What is the point of including number of builds into release? I think
> the Miro's approach solves it.
> Or is there any other problem except soname bumps?
It makes it easier to do rebuilds which means it makes it easier and simp
Il 24/02/20 23:12, Dave Dykstra ha scritto:
> I made a ticket (bug #1806737) for the maintainer of the existing vault
> package in Fedora to see if he'd be willing to give it up so it can be
> used for Hashicorp vault (https://vaultproject.io) and he decided to
> mark it EOL so I could claim it.
>
On Tue, Feb 25, 2020 at 09:06:35AM +0100, Petr Pisar wrote:
> On Mon, Feb 24, 2020 at 05:48:36PM +0100, Pierre-Yves Chibon wrote:
> > - commits containing "magic keyword" (#changelog_exclude,
> > #changelog_include?) will be ignored or included as the case may be
>
> Could we please use
On Mon, Feb 24, 2020 at 10:05:31PM +0100, Miroslav Suchý wrote:
> Dne 24. 02. 20 v 18:13 Miro Hrončok napsal(a):
> > Can we please have a "git is the only source of truth" version of this?
> > I.e. "Compute the release field from the number
> > of commits since the last version change" in the docu
On Mon, Feb 24, 2020 at 07:30:15PM +0100, Nicolas Mailhot via devel wrote:
> Le lundi 24 février 2020 à 18:13 +0100, Miro Hrončok a écrit :
> > On 24. 02. 20 17:48, Pierre-Yves Chibon wrote:
> > > However, for the release field, we are struggling a little bit
> > > more, two options
> > > are more
https://bugzilla.redhat.com/show_bug.cgi?id=1806724
--- Comment #3 from Fedora Update System ---
FEDORA-2020-465920564b has been submitted as an update to Fedora 30.
https://bodhi.fedoraproject.org/updates/FEDORA-2020-465920564b
--
You are receiving this mail because:
You are on the CC list f
I corrected a license tag for perl-HTTP-Message package from
"GPL+ or Artistic" to "(GPL+ or Artistic) and CC0". It should not affect other
packages because the CC0 license is only used for a documentation file.
-- Petr
signature.asc
Description: PGP signature
___
Jambo Benson,
Glad to be here.
Thanks!
On Tue, Feb 25, 2020 at 11:33 AM Benson Muite
wrote:
>
>
>
>
> On Tue, Feb 25, 2020, at 11:17 AM, Francis Gesora wrote:
>
> Hi All,
>
> I am Francis, based in Nairobi, Kenya.
>
> I am joining as a package maintainer to assist Ankur manage xmedcon and
> de
On Mon, Feb 24, 2020 at 06:13:21PM +0100, Miro Hrončok wrote:
> On 24. 02. 20 17:48, Pierre-Yves Chibon wrote:
> > However, for the release field, we are struggling a little bit more, two
> > options
> > are more appealing to us:
>
> Can we please have a "git is the only source of truth" version
On Tue, 25 Feb 2020 at 09:31, clime wrote:
>
> Hello Adam!
>
> On Tue, 25 Feb 2020 at 08:58, Adam Saleh wrote:
> >
> > Nice, I have been trying to fight through the 'git context already missing'
> > with pure lua rpm macros,
> > and so far was hitting walls left and right :-)
> >
> > Will look a
On Tue, Feb 25, 2020, at 11:17 AM, Francis Gesora wrote:
> Hi All,
>
> I am Francis, based in Nairobi, Kenya.
>
> I am joining as a package maintainer to assist Ankur manage xmedcon and deps
> as i get up to speed with package maintenance.
Hello/Hujambo Gesora,
Awesome to have you here.
Re
Hello Adam!
On Tue, 25 Feb 2020 at 08:58, Adam Saleh wrote:
>
> Nice, I have been trying to fight through the 'git context already missing'
> with pure lua rpm macros,
> and so far was hitting walls left and right :-)
>
> Will look at https://pagure.io/rpkg-util, might have more questions :-)
Y
No missing expected images.
Passed openQA tests: 1/1 (x86_64)
--
Mail generated by check-compose:
https://pagure.io/fedora-qa/check-compose
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedorap
Hi All,
I am Francis, based in Nairobi, Kenya.
I am joining as a package maintainer to assist Ankur manage xmedcon and
deps as i get up to speed with package maintenance.
Thanks!
--
Regards,
Gesora.
___
devel mailing list -- devel@lists.fedoraproject
On Mon, Feb 24, 2020 at 05:48:36PM +0100, Pierre-Yves Chibon wrote:
> - commits containing "magic keyword" (#changelog_exclude,
> #changelog_include?) will be ignored or included as the case may be
Could we please use the usual git commit keyword syntax? I.e. the e-mail
header format (Si
81 matches
Mail list logo
