On 05. 10. 19 1:37, Dennis Gilmore wrote:
On Fri, Oct 4, 2019 at 6:30 AM Richard W.M. Jones wrote:
This has happened to me twice this morning, the second time here:
https://koji.fedoraproject.org/koji/taskinfo?taskID=38048038
Rich.
koji uses very simple logic in parsing mock return codes
h
On 25. 09. 19 22:01, Elliott Sales de Andrade wrote:
On Wed, 25 Sep 2019 at 11:02, Miroslav Suchý wrote:
Dne 25. 09. 19 v 4:59 Elliott Sales de Andrade napsal(a):
https://koji.fedoraproject.org/koji/buildinfo?buildID=1389518
I looked at this one and:
https://koji.fedoraproject.org/koji/tas
On Fri, 2019-10-04 at 15:46 -0400, Matthew Miller wrote:
> On Fri, Oct 04, 2019 at 05:58:19PM +0100, Aoife Moloney wrote:
> >Fedocal: If no maintainer is found by October 18th, it will be
> >decommissioned.
>
> This is pretty huge, since we use this to keep IRC meeting channels
> coordina
On Fri, 2019-10-04 at 21:11 -0400, Chris wrote:
> HI,
>
> I'm just following the process identified here:
> https://docs.fedoraproject.org/en-US/fesco/Policy_for_nonresponsive_package_maintainers/
>
> 1) I filled this issue back in June/2019:
> https://bugzilla.redhat.com/show_bug.cgi?id=172085
HI,
I'm just following the process identified here:
https://docs.fedoraproject.org/en-US/fesco/Policy_for_nonresponsive_package_maintainers/
1) I filled this issue back in June/2019:
https://bugzilla.redhat.com/show_bug.cgi?id=1720857
2) I created a non responsive maintainer a couple of weeks ago
Miro Hrončok wrote:
> Wouldn't it be easier if the "default stream" would just behave like a
> regular package?
+1
> I can think of two solutions of that:
>
> 1. (drastic for modular maintainers)
>
> We keep miantaining the default versions of things as ursine packages. We
> only modularize alt
Randy Barlow wrote:
> It's not an either-or. If you resolve the conflict, you can have fast-
> forwarding *and* not pass irrelevant/confusing changelogs on to the end
> user.
>
> I personally avoid if statements in spec files and just resolve
> conflicts.
No. Resolving conflicts implies that you
Vít Ondruch wrote:
> It depends how you maintain your packages. My guess is (and I am sorry
> if I am mistaken) that you don't follow the
>
> https://fedoraproject.org/wiki/Updates_Policy#Philosophy
>
> If you followed this policy, then you would touch the stable branches
> just rarely and theref
Miro Hrončok wrote:
> It goes like this:
>
> - master and f31 are at the same commit "aa"
> - I push a change only possible in rawhide, commit "bb" to master
> (it includes release bump and changelog entry)
> - a commit relevant for both, "cc" is pushed to master
> (it in
Stephen John Smoogen wrote:
> What do you mean by breaking breaking because you use that term like a
> sledge hammer for anything from a 'pixel off' bug to 'too old software
> is in repos', 'too young software is in repos' , 'software is not in
> repos' to 'can't boot'. After a while, I assumed the
On Fri, Oct 4, 2019 at 6:30 AM Richard W.M. Jones wrote:
>
>
> This has happened to me twice this morning, the second time here:
>
> https://koji.fedoraproject.org/koji/taskinfo?taskID=38048038
>
> Rich.
koji uses very simple logic in parsing mock return codes
https://pagure.io/koji/blob/master/f/
Action summary
Accepted blockers
-
1. mutter — can't turn zoom off once enabled — NEW
ACTION: upstream to fix issue
2. distribution — Cannot upgrade to Fedora 31: package
exa-0.9.0-2.module_f31+5365+04413d87.x86_64 requires
libgit2.so.28()(64bit), but none of
On Fri, Oct 04, 2019 at 05:58:19PM +0100, Aoife Moloney wrote:
>Fedocal: If no maintainer is found by October 18th, it will be
>decommissioned.
This is pretty huge, since we use this to keep IRC meeting channels
coordinated. We used to use this to track people's vacations and
away-from-pr
# F31 Blocker Review meeting
# Date: 2019-09-30
# Time: 16:00 UTC
# Location: #fedora-blocker-review on irc.freenode.net
Hi folks! We have 5 proposed Final blockers and 2 proposed Final freeze
exception to review, so let's have a Fedora 31 blocker review meeting
on Monday!
If you have time today,
Hi folks! I'm proposing we cancel the QA meeting for Monday. I don't
think there's anything urgent right now. There will be a blocker review
meeting.
If you're aware of anything important we have to discuss this week,
please do reply to this mail and we can go ahead and run the meeting.
Thanks!
-
On 04. 10. 19 16:57, Stephen Gallagher wrote:
Right now, there are two conflicting requirements in Fedora Modularity
that we need to resolve.
1. Once a user has selected a stream, updates should follow that
stream and not introduce incompatiblities. Selected streams should not
be changed without
On Fri, Oct 04, 2019 at 06:57:55PM +0200, Vít Ondruch wrote:
> >> The package review becomes then a basic PR. We could leverage the tools we
> >> are
> >> working on for regular PRs.
> >> If the PR is approved, you get access granted to it.
> >> If the PR is denied, both repo are deleted.
> > This
On 10/3/19 12:19 PM, Matthew Miller wrote:
On Thu, Oct 03, 2019 at 11:13:32AM -0500, Michael Cronenworth wrote:
Remote changelog URLs might become inaccessible over time, making tracking down
behavior changes & tricky bugs problematic.
Yes, there are systems that do not have Internet access.
Ex
On Fri, Oct 04, 2019 at 08:52:45AM -0400, Neal Gompa wrote:
> I would personally make the same request as well for anything I've got
> a changelog entry for.
This is reasonable and I think anything which moves changelog entries out of
spec files (and ideally also RPM metadata) must preserve this.
Robbie Harwood wrote:
>I have experienced this as a maintainer as well. The issue for drive-by
>contributors is not so much pull requests as the account system itself.
>For example, I had a contributor from OpenSUSE email me patches to my
>pagure-hosted project (gssproxy) rather than opening a pul
Stephen Gallagher wrote:
>* The state `dep_enabled` would be set whenever a stream becomes
>enabled because some other module stream depended on it. This state
>must be entered only if the previous state was `default` or
>`available`. (We don't want `enabled` or `disabled` streams being able
>to tr
Hi Everyone,
Welcome to the CPE team weekly project update mail!
Background: The Community Platform Engineering group is the Red Hat team
combining IT and release engineering from Fedora and CentOS. Our goal is to
keep core servers and services running and maintained, build releases, and
other s
Dne 04. 10. 19 v 18:10 Fabio Valentini napsal(a):
> On Fri, Oct 4, 2019 at 5:54 PM Pierre-Yves Chibon wrote:
>> On Wed, Oct 02, 2019 at 08:17:37PM +0200, Ben Rosser wrote:
>>
>> Thanks for your words, I appreciate the support on the idea.
>>
>>> 1. Creating new packages has become (more of) a pai
Pierre-Yves Chibon writes:
> On Wed, Oct 02, 2019 at 03:17:33PM -0400, Robbie Harwood wrote:
>
>> With about six more emails about it, sure. And another piece of
>> infrastructure that has to be up and bug-free.
>>
>> Even the gating and bodhi emails today are rather a lot: I don't want to
>> b
On Friday, October 4, 2019 10:46:17 AM CEST Nicolas Chauvet wrote:
> Le jeu. 3 oct. 2019 à 21:40, Pavel Raiskup a écrit :
> >
> > On Friday, September 27, 2019 6:29:54 PM CEST Sérgio Basto wrote:
> > > On Fri, 2019-09-27 at 12:06 -0400, Neal Gompa wrote:
> > > > On Fri, Sep 27, 2019 at 12:03 PM Sé
On Fri, 4 Oct 2019 at 12:25, Pavel Raiskup wrote:
>
> On Friday, October 4, 2019 10:57:05 AM CEST Fabio Valentini wrote:
> > On Fri, Oct 4, 2019 at 10:47 AM Nicolas Chauvet wrote:
> > >
> > > Le jeu. 3 oct. 2019 à 21:40, Pavel Raiskup a écrit :
> > > >
> > > > On Friday, September 27, 2019 6:29:
On Friday, October 4, 2019 10:57:05 AM CEST Fabio Valentini wrote:
> On Fri, Oct 4, 2019 at 10:47 AM Nicolas Chauvet wrote:
> >
> > Le jeu. 3 oct. 2019 à 21:40, Pavel Raiskup a écrit :
> > >
> > > On Friday, September 27, 2019 6:29:54 PM CEST Sérgio Basto wrote:
> > > > On Fri, 2019-09-27 at 12:0
On Fri, Oct 4, 2019 at 5:54 PM Pierre-Yves Chibon wrote:
>
> On Wed, Oct 02, 2019 at 08:17:37PM +0200, Ben Rosser wrote:
>
> Thanks for your words, I appreciate the support on the idea.
>
> > 1. Creating new packages has become (more of) a pain since the
> > retirement of pkgdb2. I know I keep com
On Thu, Oct 03, 2019 at 08:07:33AM +, Zbigniew Jędrzejewski-Szmek wrote:
> Yep. Not every package is the same. For stuff like simple
> python/nodejs/rust/ruby/perl/… packages, I know that the only thing
> I do is mechanically bump the version and rebuild. I don't take a careful
> look at the ch
On Wed, Oct 02, 2019 at 08:17:37PM +0200, Ben Rosser wrote:
Thanks for your words, I appreciate the support on the idea.
> 1. Creating new packages has become (more of) a pain since the
> retirement of pkgdb2. I know I keep complaining about needing to
> manually fetch Pagure API keys, but it is
On Wed, Oct 02, 2019 at 03:17:33PM -0400, Robbie Harwood wrote:
> With about six more emails about it, sure. And another piece of
> infrastructure that has to be up and bug-free.
>
> Even the gating and bodhi emails today are rather a lot: I don't want to
> be notified if everything worked correc
Hi Everyone,
We have tried for a number of weeks now to find a new maintainer for
Fedocal.
Unfortunately this has not been successful and the CPE team will
decommission Fedocal at close of business EST on Friday, October 15th.
If a maintainer steps up between now and then we will of course work
Hi everybody,
To provide a bit of context: Syncthing ships unit files for both
system services and user services, where the system service can be
instantiated with the $USER the service should run as. The user
service obviously doesn't need this argument, but will only run when
the user is logged
On Fri, Oct 4, 2019 at 11:03 AM Robbie Harwood wrote:
>
> Björn Persson writes:
>
> > Panu Matilainen wrote:
> >> On 10/2/19 8:33 PM, Matthew Miller wrote:
> >>> On Wed, Oct 02, 2019 at 05:31:56PM +0100, Richard W.M. Jones wrote:
> >>>
> > ○ Every changes to dist-git is done via pull-requests
https://bugzilla.redhat.com/show_bug.cgi?id=1758586
--- Comment #1 from Xavier Bachelot ---
No matching package to install: 'perl(FreezeThaw)'
--
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list --
Björn Persson writes:
> Panu Matilainen wrote:
>> On 10/2/19 8:33 PM, Matthew Miller wrote:
>>> On Wed, Oct 02, 2019 at 05:31:56PM +0100, Richard W.M. Jones wrote:
>>>
> ○ Every changes to dist-git is done via pull-requests
Erm, no thank you. Pull requests are a terrible workflow
Right now, there are two conflicting requirements in Fedora Modularity
that we need to resolve.
1. Once a user has selected a stream, updates should follow that
stream and not introduce incompatiblities. Selected streams should not
be changed without direct action from the user.
2. So far as possi
On Fri, Oct 4, 2019 at 3:37 PM Pavel Raiskup wrote:
> Hello,
>
> today (on Oct 4, 2019), new Copr release landed production.
>
> This was mostly a bugfix release, with some optimization/reliability
> patches interesting for copr administrators. But there were few exciting
> changes for the end-u
I did, in fact, mean that, but a. mistyped b. failed to include it in the chain
build. I'll remedy that. Sorry. :)
--
Gwyn Ciesla
she/her/hers
in your fear, seek only peace
in your fear, seek only love
-d. bowie
Sent with ProtonMail Secure Ema
Hello,
today (on Oct 4, 2019), new Copr release landed production.
This was mostly a bugfix release, with some optimization/reliability
patches interesting for copr administrators. But there were few exciting
changes for the end-users:
Multilib projects
-
If you go to the proje
On Fri, 2019-10-04 at 13:23 +, Gwyn Ciesla via devel wrote:
> Hi! I'll be updating FreeGLUT to 3.2.1 today. Since this includes a
> soname bump, I'll do so with a chained rebuild for:
>
> mesa
I think you mean mesa-demos for the source package here. mesa proper
doesn't link to glut.
- ajax
_
Hi! I'll be updating FreeGLUT to 3.2.1 today. Since this includes a soname
bump, I'll do so with a chained rebuild for:
plib
libcaca
libfreenect
libwebp
mesa
OpenColorIO
asymptote
FlightGear
FlightGear-Atlas
gauche
gl-117
glglobe
gtengine
Io-language
jasper
ocaml-lablgl
OpenMesh
openni
perl-OpenGL
No missing expected images.
Failed openQA tests: 5/153 (x86_64), 1/2 (arm)
New failures (same test not failed in Fedora-31-20191003.n.1):
ID: 463075 Test: x86_64 KDE-live-iso apps_startstop
URL: https://openqa.fedoraproject.org/tests/463075
ID: 463082 Test: x86_64 Silverblue-dvd_ostree
On Fri, Oct 4, 2019 at 4:39 AM Daniel P. Berrangé wrote:
>
> On Thu, Oct 03, 2019 at 01:12:10PM -0500, Jason L Tibbitts III wrote:
> > > "MM" == Matthew Miller writes:
> >
> > MM> Whether or not it's documented policy (and I can't remember or find
> > MM> anything either), many packages have
Rex Dieter wrote:
> Appears to be a bodhi one
make that bodhi *bug*
-- Rex
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.o
Richard Shaw wrote:
> I messed up and build PySide2 5.13.x before I relealized that I should
> have built the latest 5.12.x as the MAJOR.MINOR has to match the version
> of Qt and we have not updated to 5.13 yet.
>
> So I bumped the Epoch in the spec file and built 5.12.5 but when I
> submitted u
OLD: Fedora-31-20191003.n.1
NEW: Fedora-31-20191004.n.0
= SUMMARY =
Added images:0
Dropped images: 0
Added packages: 0
Dropped packages:0
Upgraded packages: 0
Downgraded packages: 0
Size of added packages: 0 B
Size of dropped packages:0 B
Size of upgraded
Panu Matilainen wrote:
> On 10/2/19 8:33 PM, Matthew Miller wrote:
> > On Wed, Oct 02, 2019 at 05:31:56PM +0100, Richard W.M. Jones wrote:
> >>> ○ Every changes to dist-git is done via pull-requests
> >> Erm, no thank you. Pull requests are a terrible workflow.
> >
> > It's definitely the w
Hello fellow Python packagers. This is an announcement about a new set of RPM
macros you can use to build PEP 517/518 enabled packages, that is Python
packages that have the pyproject.toml file.
https://www.python.org/dev/peps/pep-0517/
https://www.python.org/dev/peps/pep-0518/
https://sn
This has happened to me twice this morning, the second time here:
https://koji.fedoraproject.org/koji/taskinfo?taskID=38048038
Rich.
--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
Fedora Wi
Hi all,
My name is Matěj and I would like to contribute to the Fedora
community by packaging some interesting and potentially useful
software. I have submitted my first review request for procdump
recently [1].
Currently, I'm a Master's student of IT security, with a focus on
usable security and
is this the right place for this sort of note?
some sort of Wayland or Gnome behavior.
I saw it the first time today, so I suspect the update yesterday. This is
an ASUS laptop with an external display and usb mouse, i.e. being used as a
regular machine.
To reproduce a person must boot with the
On Fri, Oct 4, 2019 at 11:43 AM Zbigniew Jędrzejewski-Szmek
wrote:
>
> Hi,
>
> git push — requires an ssh key (cached)
> fedpkg build — requires a kerberos ticket (cached)
> fedpkg override – asks for a password every damn time
>
> What's so special about buildroot overrides? Can we make
> them be
Hi,
git push — requires an ssh key (cached)
fedpkg build — requires a kerberos ticket (cached)
fedpkg override – asks for a password every damn time
What's so special about buildroot overrides? Can we make
them behave more like the other stuff?
Zbyszek
___
On Fri, Oct 4, 2019 at 10:47 AM Nicolas Chauvet wrote:
>
> Le jeu. 3 oct. 2019 à 21:40, Pavel Raiskup a écrit :
> >
> > On Friday, September 27, 2019 6:29:54 PM CEST Sérgio Basto wrote:
> > > On Fri, 2019-09-27 at 12:06 -0400, Neal Gompa wrote:
> > > > On Fri, Sep 27, 2019 at 12:03 PM Sérgio Bast
Le jeu. 3 oct. 2019 à 21:40, Pavel Raiskup a écrit :
>
> On Friday, September 27, 2019 6:29:54 PM CEST Sérgio Basto wrote:
> > On Fri, 2019-09-27 at 12:06 -0400, Neal Gompa wrote:
> > > On Fri, Sep 27, 2019 at 12:03 PM Sérgio Basto
> > > wrote:
> > > > Hi,
> > > > epel 8 brings a new file called
On Thu, Oct 03, 2019 at 01:12:10PM -0500, Jason L Tibbitts III wrote:
> > "MM" == Matthew Miller writes:
>
> MM> Whether or not it's documented policy (and I can't remember or find
> MM> anything either), many packages have the practice of trimming very
> MM> old entries.
>
> You can't alway
57 matches
Mail list logo
