On Sat, Feb 29, 2020 at 8:42 PM Adam Williamson
wrote:
>
> Hey folks!
>
> So, I caught an interesting story on LWN today:
>
> https://lwn.net/Articles/813254/
>
> it appears the FSF is planning to run a forge and contribute to
> whatever project they use, and Pagure is currently their leading
> co
On Sat, 29 Feb 2020 at 22:42, Nicolas Mailhot via devel
wrote:
>
> Le samedi 29 février 2020 à 20:57 +0100, clime a écrit :
> > On Sat, 29 Feb 2020 at 16:24, Nicolas Mailhot via devel
> > wrote:
> > > Le samedi 29 février 2020 à 15:12 +0100, clime a écrit :
> > > > On Sat, 29 Feb 2020 at 14:47, N
Hey folks!
So, I caught an interesting story on LWN today:
https://lwn.net/Articles/813254/
it appears the FSF is planning to run a forge and contribute to
whatever project they use, and Pagure is currently their leading
contender:
https://libreplanet.org/wiki/Fsf_2019_forge_evaluation
"Pagure
On Sat, 29 Feb 2020 at 21:50, Nicolas Mailhot via devel
wrote:
>
> Le samedi 29 février 2020 à 20:30 +0100, clime a écrit :
> >
> > What about fedpkg local and fedpkg verrel then?
>
> Putting %{dynrel} reconciliation in the rpmbuild -bs stage using
> detached file state means that fedpkg local (or
Le samedi 29 février 2020 à 20:57 +0100, clime a écrit :
> On Sat, 29 Feb 2020 at 16:24, Nicolas Mailhot via devel
> wrote:
> > Le samedi 29 février 2020 à 15:12 +0100, clime a écrit :
> > > On Sat, 29 Feb 2020 at 14:47, Nicolas Mailhot via devel
> > > wrote:
> > > > Le samedi 29 février 2020 à 1
Le samedi 29 février 2020 à 20:30 +0100, clime a écrit :
>
> What about fedpkg local and fedpkg verrel then?
Putting %{dynrel} reconciliation in the rpmbuild -bs stage using
detached file state means that fedpkg local (or checking out git state
and building in mock or copr or OBS or via plain rp
On Sat, 29 Feb 2020 at 16:24, Nicolas Mailhot via devel
wrote:
>
> Le samedi 29 février 2020 à 15:12 +0100, clime a écrit :
> > On Sat, 29 Feb 2020 at 14:47, Nicolas Mailhot via devel
> > wrote:
> > > Le samedi 29 février 2020 à 14:28 +0100, clime a écrit :
> > > > Does ENVR without %{dist} means
On Sat, 29 Feb 2020 at 16:12, Nicolas Mailhot via devel
wrote:
>
> Le samedi 29 février 2020 à 13:49 +0100, clime a écrit :
> > On Sat, 29 Feb 2020 at 10:15, Nicolas Mailhot via devel
> > wrote:
> > > Hi,
> > >
> > > Anyway, here is what I would personnaly consider a robust,
> > > inclusive,
> >
Hi all.
I have two new packages ready for the review:
https://bugzilla.redhat.com/show_bug.cgi?id=1808573
https://bugzilla.redhat.com/show_bug.cgi?id=1808571
I'm available to review other packages in return.
--
---
Antonio Trande
Fedora Project
mailto 'sagitter at fedoraproject dot org'
GPG ke
On 2/27/20 12:08 AM, Dan Čermák wrote:
For the changelog: yes please, generate it from the commit log! They are
more or less the same for all my packages and I'm getting tired of copy
pasting the same text into %changelog and git commit.
Do you know about fedpkg commit --clog ?
--
Orion Popla
Le samedi 29 février 2020 à 16:11 +0100, Nicolas Mailhot a écrit :
>
> Build-time state changes need to be commited back, of course
> (otherwise the produced srpm needs to be re-imported manually)
Probably, only on *successful* production build however. We don’t need
to record failed or scratch b
Le samedi 29 février 2020 à 15:12 +0100, clime a écrit :
> On Sat, 29 Feb 2020 at 14:47, Nicolas Mailhot via devel
> wrote:
> > Le samedi 29 février 2020 à 14:28 +0100, clime a écrit :
> > > Does ENVR without %{dist} means something with respect to the
> > > content
> > > from
> > > which the pack
Le samedi 29 février 2020 à 13:49 +0100, clime a écrit :
> On Sat, 29 Feb 2020 at 10:15, Nicolas Mailhot via devel
> wrote:
> > Hi,
> >
> > Anyway, here is what I would personnaly consider a robust,
> > inclusive,
> > and future-proof design:
>
> I will need to ask some questions to really under
OLD: Fedora-32-20200228.n.0
NEW: Fedora-32-20200229.n.0
= SUMMARY =
Added images:0
Dropped images: 0
Added packages: 1
Dropped packages:0
Upgraded packages: 0
Downgraded packages: 0
Size of added packages: 1.09 MiB
Size of dropped packages:0 B
Size of
No missing expected images.
Failed openQA tests: 21/171 (x86_64), 1/2 (arm)
New failures (same test not failed in Fedora-32-20200228.n.0):
ID: 529891 Test: x86_64 Workstation-live-iso install_default_upload
URL: https://openqa.fedoraproject.org/tests/529891
ID: 529940 Test: x86_64 univ
On Sat, 29 Feb 2020 at 14:47, Nicolas Mailhot via devel
wrote:
>
> Le samedi 29 février 2020 à 14:28 +0100, clime a écrit :
> >
> > Does ENVR without %{dist} means something with respect to the content
> > from
> > which the package was built or with respect to features that it
> > offers for the
Le samedi 29 février 2020 à 14:28 +0100, clime a écrit :
>
> Does ENVR without %{dist} means something with respect to the content
> from
> which the package was built or with respect to features that it
> offers for the given distribution version?
You need to evaluate evr with a neutral dist val
On Thu, 27 Feb 2020 at 18:07, Zbigniew Jędrzejewski-Szmek
wrote:
>
> On Tue, Feb 25, 2020 at 05:42:11PM +0100, Miro Hrončok wrote:
> > 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
On Sat, 29 Feb 2020 at 10:15, Nicolas Mailhot via devel
wrote:
>
> Hi,
>
> Anyway, here is what I would personnaly consider a robust, inclusive,
> and future-proof design:
I will need to ask some questions to really understand it.
>
> — a %{use_dynstate} rpm variable enables dynamic changelog/re
On 28. 02. 20 23:49, Miro Hrončok wrote:
A follow-up observation, btw: can we exclude things from
pyproject_buildrequires ? (whether that's done at the level of the
dynamic build generation process itself, or within the pyproject
macro/tool I don't care - but I couldn't find any docs indicating i
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,
Anyway, here is what I would personnaly consider a robust, inclusive,
and future-proof design:
— a %{use_dynstate} rpm variable enables dynamic changelog/release
behaviour
— probably initialy set to false distro-wide, to let volunteers test
the thing by setting it to true iin their specs,
22 matches
Mail list logo
