According to [1], these are the packages which need to be preserved to
keep js-jquery around:
nodejs-grunt-legacy-util
nodejs-load-grunt-tasks
nodejs-raw-body
Vít
[1] https://churchyard.fedorapeople.org/orphans-2019-12-02.txt
Dne 03. 12. 19 v 2:24 Sérgio Basto napsal(a):
> I will take nod
On Monday, December 2, 2019 12:39:52 PM MST Chris Murphy wrote:
> On Mon, Dec 2, 2019 at 9:48 AM Przemek Klosowski via devel
> wrote:
>
> >
> >
> > On 11/27/19 2:59 AM, Zbigniew Jędrzejewski-Szmek wrote:
> >
> >
> >
> > On Tue, Nov 26, 2019 at 09:39:59AM -0700, Chris Murphy wrote:
> >
> >
> >
> >
On Monday, December 2, 2019 12:46:30 PM MST Chris Murphy wrote:
> It's almost 2020, and I shouldn't have to pick and choose between
> remote access and securing user data at rest by default.
You don't have to. Data at rest would mean that your system is powered off, or
suspended to disk. You can
On Monday, December 2, 2019 11:16:43 AM MST Zbigniew Jędrzejewski-Szmek wrote:
> How often do you ssh *into* your laptop?
Every time I'm on another system without access to my NFS server, or I need my
GnuPG key when not using my laptop.
--
John M. Harris, Jr.
Splentity
On Tue, Dec 3, 2019 at 12:03 AM Mike Nguyen wrote:
> With Fedora 29 reaching End Of Life, this will be the final Fedora Atomic
> Host release (based on the Fedora 29 stream). Fedora Atomic Host will no
> longer receive any updates. More details can be found at
> https://www.projectatomic.io/blo
On Mon, 2019-12-02 at 19:49 +, Richard W.M. Jones wrote:
> On Mon, Dec 02, 2019 at 07:15:27PM +0100, Miro Hrončok wrote:
> > ocaml-bin-protorphan 2 weeks
> > ago
> > ocaml-bisect orphan 2 weeks
> > ag
Dear all,
You are kindly invited to the meeting:
Modularity Team (weekly) on 2019-12-03 from 15:00:00 to 16:00:00 UTC
At fedora-meetin...@irc.freenode.net
The meeting will be about:
Meeting of the Modularity Team.
More information available at: [Modularity Team
Docs](https://docs.pagure.o
I will take nodejs-dateformat .
Do you have a list of what more packages we have to keep?
On Mon, 2019-12-02 at 15:52 +0100, Raphael Groner wrote:
> Thanks a lot.
>
> Am 02.12.19 um 15:20 schrieb Tom Hughes:
> …
> > As I explained the other day js-jquery was dependent on a
> > nodejs module (a n
On Mon, 2019-12-02 at 19:15 +0100, Miro Hrončok wrote:
> The following packages are orphaned and will be retired when they
> are orphaned for six weeks, unless someone adopts them. If you know
> for sure
> that the package should be retired, please do so now with a proper
> reason:
> https://fedora
Xavier Bachelot writes:
> As offered in the bug, I can help with maintaining
> perl-Crypt-OpenSSL-X509. My FAS username is xavierb.
> I'll reassign the EL8 branch bug to me and take care of it. I'll also
> take care of updating to the recently released 1.813 in master.
1.813 is complete on maste
On Mon, Dec 2, 2019 at 12:39 PM Chris Murphy wrote:
> 4. If based on any fscrypt implementation, exclude ~/.ssh/ from encryption
Actually this is essentially the same problem. Yes, I've ssh'd into
the real home, but everything is still encrypted, so I'd have to
unlock my home dir manually to gai
On 03. 12. 19 0:26, Elliott Sales de Andrade wrote:
On Mon, 2 Dec 2019 at 08:22, Pierre-Yves Chibon wrote:
Good Morning Everyone™,
we have recently spent some time refactoring, improving and fixing the script
that syncs the default assignee and CC list from dist-git to Bugzilla.
Since the sc
On Mon, 2 Dec 2019 at 08:22, Pierre-Yves Chibon wrote:
>
> Good Morning Everyone™,
>
> we have recently spent some time refactoring, improving and fixing the script
> that syncs the default assignee and CC list from dist-git to Bugzilla.
>
> Since the script was broken for some time, we felt that
On Mon, Dec 2, 2019, 22:44 Kevin Kofler wrote:
> Igor Gnatenko wrote:
> > * Should any other packager (not that maintainer) be able to request
> > new branches on that repo?
> > * Should provenpackager be able to do the same request?
>
> Since I do not give a darn about what happens to my package
This is your reminder that voting for FESCo (and other elected bodies) is
open through 23:59 UTC on Thursday, 5 December. See below for more
information.
On Thu, Nov 21, 2019 at 5:41 AM Ben Cotton wrote:
> If you missed the Community Blog post[1], voting is now open for the
> Fedora 31 election
Igor Gnatenko wrote:
> * Should any other packager (not that maintainer) be able to request
> new branches on that repo?
> * Should provenpackager be able to do the same request?
Since I do not give a darn about what happens to my packages on EPEL, I am
fine with anybody requesting EPEL branches
On 02/12/2019 14:37, Daniel P. Berrangé wrote:
> IIUC, effectively "new branches" means "EPEL branches" since normal
> Fedora branches are all created automatically.
>
> So to rephrase this
>
> * Should someone who is not the maintainer be able to declare
> that the maintainer must acc
Petr Pisar wrote:
> On 2019-12-02, John M. Harris Jr wrote:
>> On Monday, December 2, 2019 12:17:20 AM MST Igor Gnatenko wrote:
>>> Sure, we just have to accept this until perl is made
>>> parallel-installable. Which may or may not happen, but if I have
>>> choice between "only one version of per
I have taken sassc but will welcome anyone else willing to help co-maintain
this train wreck.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://do
On Mon, Dec 02, 2019 at 06:16:43PM +, Zbigniew Jędrzejewski-Szmek wrote:
...snip...
> Nevertheless, I'm pretty sure that a workaround for this will be made
> anyway. I think the latest version of the patchset allows exporting
> the authorized_keys content in the non-encrypted metadata for the u
On Mon, Dec 02, 2019 at 07:15:27PM +0100, Miro Hrončok wrote:
> ocaml-bin-protorphan 2 weeks ago
> ocaml-bisect orphan 2 weeks ago
> ocaml-bitstring orphan 2 week
On Mon, Dec 2, 2019 at 10:45 AM John M. Harris Jr wrote:
>
> On Monday, December 2, 2019 9:48:05 AM MST Przemek Klosowski via devel wrote:
> > On 11/27/19 2:59 AM, Zbigniew Jędrzejewski-Szmek wrote:
> > > On Tue, Nov 26, 2019 at 09:39:59AM -0700, Chris Murphy wrote:
> > >> Mabee systemd-homed
On Mon, Dec 2, 2019 at 9:48 AM Przemek Klosowski via devel
wrote:
>
> On 11/27/19 2:59 AM, Zbigniew Jędrzejewski-Szmek wrote:
>
> On Tue, Nov 26, 2019 at 09:39:59AM -0700, Chris Murphy wrote:
>
> Mabee systemd-homed is in
> a position to solve this by having early enough authentication
> capab
On 02/12/2019 19:15, Wes Hardaker wrote:
Xavier Bachelot writes:
I've tried to get in touch with Wes Hardaker about
perl-Crypt-OpenSSL-X509 for 2 months. The bug was left untouched, even
after setting need-info flag. I've also tried to reach to him by
direct mail.
Hi, and sorry both.
I've b
On Mon, 2019-12-02 at 18:16 +, Zbigniew Jędrzejewski-Szmek wrote:
> On Mon, Dec 02, 2019 at 10:44:46AM -0700, John M. Harris Jr wrote:
> > On Monday, December 2, 2019 9:48:05 AM MST Przemek Klosowski via devel
> > wrote:
> > > On 11/27/19 2:59 AM, Zbigniew Jędrzejewski-Szmek wrote:
> > > > On
Le lundi 02 décembre 2019 à 18:16 +, Zbigniew Jędrzejewski-Szmek a
écrit :
>
> How often do you ssh *into* your laptop?
I use the same tech desktop and home server side. If it does not work
on my home server, I don’t want to see it on my desktops. I have other
things to do in life than coping
On Mon, Dec 02, 2019 at 10:44:46AM -0700, John M. Harris Jr wrote:
> On Monday, December 2, 2019 9:48:05 AM MST Przemek Klosowski via devel wrote:
> > On 11/27/19 2:59 AM, Zbigniew Jędrzejewski-Szmek wrote:
> > > On Tue, Nov 26, 2019 at 09:39:59AM -0700, Chris Murphy wrote:
> > >> Mabee systemd
The following packages are orphaned and will be retired when they
are orphaned for six weeks, unless someone adopts them. If you know for sure
that the package should be retired, please do so now with a proper reason:
https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life
Note: If
Xavier Bachelot writes:
> I've tried to get in touch with Wes Hardaker about
> perl-Crypt-OpenSSL-X509 for 2 months. The bug was left untouched, even
> after setting need-info flag. I've also tried to reach to him by
> direct mail.
Hi, and sorry both.
I've been swamped lately and haven't had ti
On Monday, December 2, 2019 9:48:05 AM MST Przemek Klosowski via devel wrote:
> On 11/27/19 2:59 AM, Zbigniew Jędrzejewski-Szmek wrote:
> > On Tue, Nov 26, 2019 at 09:39:59AM -0700, Chris Murphy wrote:
> >> Mabee systemd-homed is in
> >> a position to solve this by having early enough authentic
On 12/1/19 10:37 PM, Kevin Kofler wrote:
I definitely want some mechanism which will tell to user that "THIS
PACKAGE IS NOT FULLY SUPPORTED."
And I think telling that to the user is absolutely unfair and against the
spirit of Fedora.
The dilemma is, how to allow the useful stuff to remain, whil
On 11/27/19 2:59 AM, Zbigniew Jędrzejewski-Szmek wrote:
On Tue, Nov 26, 2019 at 09:39:59AM -0700, Chris Murphy wrote:
Mabee systemd-homed is in
a position to solve this by having early enough authentication
capability by rescue.target time that any admin user can login?
Actually, it may. Th
=
#fedora-meeting-1: FESCO (2019-12-02)
=
Meeting started by jforbes at 15:00:40 UTC. The full logs are available
at
https://meetbot.fedoraproject.org/fedora-meeting-1/2019-12-02/fesco.2019-12-02-15.00.log.html
.
Meeting s
Is there a special procedure for undeading a package if the two
packages happen to use the same name but are otherwise unrelated?
virt-v2v was a Perl program that existed up to Fedora 21. It's long
dead (since 2013) and there's a new program with the same name written
from scratch which I want t
Thanks a lot.
Am 02.12.19 um 15:20 schrieb Tom Hughes:
…
As I explained the other day js-jquery was dependent on a
nodejs module (a normal one, not modularised) which was
failing to build and which I have now fixed.
…
___
devel mailing list -- devel@l
On 02/12/2019 14:04, Raphael Groner wrote:
> I don't think modularity is to blame here.
Nah. The dependent nodejs stack broke away due to move into modularity
worlds.
No, it didn't.
I'm no fan of modularity but there is no need to blame it
for things it is not responsible for.
As I explaine
Hello everyone,
You are invited to the next Open/Public NeuroFedora team meeting at
1600UTC on Tuesday, 3rd December in #fedora-neuro on irc.freenode.net.
You can see the time in your local time zone by running this command in
a terminal:
$ date --date='TZ="UTC" 1600 next Tue'
or using the link
> I don't think modularity is to blame here.
Nah. The dependent nodejs stack broke away due to move into modularity
worlds.
> 3) since the bundling policy is relaxed, everybody just bundles with
zero motivation to maintain package for somebody else.
Ack. The unbundling of js-jsquery has been a
On Mon, 2 Dec 2019 at 12:56, Igor Gnatenko
wrote:
> Hello,
>
> 3 months ago, Miro opened releng ticket[0] raising question whether
> non-maintainers (of some specific packages) being able to request
> branches.
>
> However, it never went anywhere outside of that ticket.
>
> I'd like to ask people
On Mon, 2 Dec 2019 12:07:22 +0100
Xavier Bachelot wrote:
> Hi,
>
> I've tried to get in touch with Ian Arnell about perl-Crypt-Rijndael
> for almost 2 months. The bug was left untouched, even after setting
> need-info flag. I've also tried to reach to him by direct mail.
>
> Anyone knows how t
On Mon, Dec 02, 2019 at 01:26:00PM +, Zbigniew Jędrzejewski-Szmek wrote:
> On Fri, Nov 29, 2019 at 06:17:36PM +0100, Pierre-Yves Chibon wrote:
> > Good Morning Everyone™,
> >
> > we have recently spent some time refactoring, improving and fixing the
> > script
> > that syncs the default assig
On Mon, Dec 02, 2019 at 02:31:39PM +0100, Miro Hrončok wrote:
> On 29. 11. 19 18:17, Pierre-Yves Chibon wrote:
> > Good Morning Everyone™,
>
> Morning o/
>
> > we have recently spent some time refactoring, improving and fixing the
> > script
> > that syncs the default assignee and CC list from d
On Mon, Dec 02, 2019 at 01:55:55PM +0100, Igor Gnatenko wrote:
> Hello,
>
> 3 months ago, Miro opened releng ticket[0] raising question whether
> non-maintainers (of some specific packages) being able to request
> branches.
>
> However, it never went anywhere outside of that ticket.
>
> I'd like
On 29. 11. 19 18:17, Pierre-Yves Chibon wrote:
Good Morning Everyone™,
Morning o/
we have recently spent some time refactoring, improving and fixing the script
that syncs the default assignee and CC list from dist-git to Bugzilla.
Will this actualy reassign the existing bugzillas or just se
I know the name but it's been a long time I don't see him around. I don't
think he's working with Fedora anymore.
On Mon, 2 Dec 2019 at 12:08, Xavier Bachelot wrote:
> Hi,
>
> I've tried to get in touch with Ian Arnell about perl-Crypt-Rijndael for
> almost 2 months. The bug was left untouch
On Fri, Nov 29, 2019 at 06:17:36PM +0100, Pierre-Yves Chibon wrote:
> Good Morning Everyone™,
>
> we have recently spent some time refactoring, improving and fixing the script
> that syncs the default assignee and CC list from dist-git to Bugzilla.
>
> Since the script was broken for some time, w
Good Morning Everyone™,
we have recently spent some time refactoring, improving and fixing the script
that syncs the default assignee and CC list from dist-git to Bugzilla.
Since the script was broken for some time, we felt that it needs some validation
before we run it live (which will still req
Igor Gnatenko wrote:
> Yes, however maintainer of nodejs does not want to rename binaries and
> patch sources to be parallel-installable.
And that is exactly the problem.
> And today, we would block adding such "compat" package into the
> repositories.
Which is exactly how it should be.
> I agr
On 02. 12. 19 13:55, Igor Gnatenko wrote:
Hello,
3 months ago, Miro opened releng ticket[0] raising question whether
non-maintainers (of some specific packages) being able to request
branches.
However, it never went anywhere outside of that ticket.
I'd like to ask people on this mailing list a
No, sorry, I don't even know him.
On Mon, 2 Dec 2019 at 12:02, Xavier Bachelot wrote:
> Hi,
>
> I've tried to get in touch with Matias Kreder about perl-Crypt-Rijndael
> for almost 2 months. The bug was left untouched, even after setting
> need-info flag. I've also tried to reach to him by di
On Mon, Dec 2, 2019 at 7:16 AM Vít Ondruch wrote:
>
> I'm not sure I understand this change.
>
> Does it mean that currently, the "apt-rpm" is tool which installs RPMs
> from Fedora repositories, while the Debians "apt" will install the DEB
> packages coming from Debian?
>
> Does it means that pre
Hello,
3 months ago, Miro opened releng ticket[0] raising question whether
non-maintainers (of some specific packages) being able to request
branches.
However, it never went anywhere outside of that ticket.
I'd like to ask people on this mailing list a few questions. Let's say
we have some theor
Dne 28. 11. 19 v 19:43 Raphael Groner napsal(a):
> Hi,
>
> in case of my packages, jpype and pyvirtualize, I'd say to skip
> generation of documentation while js-jquery is b0rken.
>
> What's the issue about js-jquery? I tend to blame modularity due to
> nodejs-*.
I don't think modularity is to b
Following is the list of topics that will be discussed in the
FESCo meeting Monday at 15:00UTC in #fedora-meeting-1 on
irc.freenode.net.
To convert UTC to your local time, take a look at
http://fedoraproject.org/wiki/UTCHowto
or run:
date -d '2019-12-02 15:00 UTC'
Links to all issues to be
On 2019-12-02, John M. Harris Jr wrote:
> On Monday, December 2, 2019 12:17:20 AM MST Igor Gnatenko wrote:
>> Sure, we just have to accept this until perl is made
>> parallel-installable. Which may or may not happen, but if I have
>> choice between "only one version of perl and no bugzilla" or "tw
I'm not sure I understand this change.
Does it mean that currently, the "apt-rpm" is tool which installs RPMs
from Fedora repositories, while the Debians "apt" will install the DEB
packages coming from Debian?
Does it means that previously, there was only one glibc package
installed no matter wha
Thanks for help Fabio.
On Mon, Dec 2, 2019 at 12:10 PM Fabio Valentini
wrote:
> On Mon, Dec 2, 2019, 11:45 Tomas Korbar wrote:
>
>> Hi,
>> I would like to ask you a question. If upstream of your package does
>> major rewrite of it, then what is the proper process to rebase such
>> package? I'm
On Monday, December 2, 2019 12:17:20 AM MST Igor Gnatenko wrote:
> Sure, we just have to accept this until perl is made
> parallel-installable. Which may or may not happen, but if I have
> choice between "only one version of perl and no bugzilla" or "two
> conflicting versions of perl and bugzilla
OLD: Fedora-Rawhide-20191201.n.0
NEW: Fedora-Rawhide-20191202.n.0
= SUMMARY =
Added images:0
Dropped images: 3
Added packages: 1
Dropped packages:5
Upgraded packages: 16
Downgraded packages: 0
Size of added packages: 360.38 KiB
Size of dropped packages
On Mon, Dec 2, 2019, 11:45 Tomas Korbar wrote:
> Hi,
> I would like to ask you a question. If upstream of your package does major
> rewrite of it, then what is the proper process to rebase such package? I'm
> maintainer of cheat [0] which has been rewritten in go. I suppose i need a
> new package
Hi,
I've tried to get in touch with Ian Arnell about perl-Crypt-Rijndael for
almost 2 months. The bug was left untouched, even after setting
need-info flag. I've also tried to reach to him by direct mail.
Anyone knows how to contact him ?
Here's the non-responsive maintainer bug :
https://bu
Hi,
I've tried to get in touch with Matias Kreder about perl-Crypt-Rijndael
for almost 2 months. The bug was left untouched, even after setting
need-info flag. I've also tried to reach to him by direct mail.
Anyone knows how to contact him ?
Here's the non-responsive maintainer bug :
https:/
No missing expected images.
Compose FAILS proposed Rawhide gating check!
5 of 43 required tests failed, 1 result missing
openQA tests matching unsatisfied gating requirements shown with **GATING**
below
Failed openQA tests: 15/161 (x86_64), 1/2 (arm)
New failures (same test not failed in Fedora
Hi,
I've tried to get in touch with Wes Hardaker about
perl-Crypt-OpenSSL-X509 for 2 months. The bug was left untouched, even
after setting need-info flag. I've also tried to reach to him by direct
mail.
Anyone knows how to contact him ?
Here's the non-responsive maintainer bug :
https://bu
Hi,
I would like to ask you a question. If upstream of your package does major
rewrite of it, then what is the proper process to rebase such package? I'm
maintainer of cheat [0] which has been rewritten in go. I suppose i need a
new package review but then if the new spec passes review am i suppose
On Mon, Dec 02, 2019 at 11:12:31AM +0100, Sandro Bonazzola wrote:
>Hi,
>just tried to issue a new release for one of the packages I maintain and
>Bodhi is failing to get the list of the candidate builds.
>browser console shows (sorry, it's in italian):
>Errore mapping di origine
Le 2019-12-02 10:49, Igor Gnatenko a écrit :
On Mon, Dec 2, 2019 at 8:58 AM Nicolas Mailhot via devel
wrote:
Le 2019-12-02 07:47, Igor Gnatenko a écrit :
> Hi Neal,
>
> On Sat, Nov 30, 2019 at 11:58 PM Neal Gompa wrote:
>> I think we need to recognize that we've done some poor optimization
>
Le 2019-12-02 10:45, Igor Gnatenko a écrit :
On Mon, Dec 2, 2019 at 8:48 AM Nicolas Mailhot via devel
wrote:
Le 2019-12-02 08:17, Igor Gnatenko a écrit :
Building communities takes time and energy and has no immediate
benefit.
But, long-term, it's the most efficient way to do things (the “
On Mon, 2 Dec 2019 11:12:31 +0100
Sandro Bonazzola wrote:
> Hi,
> just tried to issue a new release for one of the packages I maintain
> and Bodhi is failing to get the list of the candidate builds.
>
> browser console shows (sorry, it's in italian):
> Errore mapping di origine: request failed w
Hi,
just tried to issue a new release for one of the packages I maintain and
Bodhi is failing to get the list of the candidate builds.
browser console shows (sorry, it's in italian):
Errore mapping di origine: request failed with status 404 URL risorsa:
https://bodhi.fedoraproject.org/static/v5.0.
On Mon, Dec 2, 2019 at 9:13 AM Nicolas Mailhot via devel
wrote:
>
> Le 2019-12-02 08:38, Igor Gnatenko a écrit :
> > On Mon, Dec 2, 2019 at 8:28 AM Nicolas Mailhot via devel
>
> >> Having all build elements in the package repos themselves is the CORE
> >> feature that makes the “share” community d
On Mon, Dec 2, 2019 at 8:58 AM Nicolas Mailhot via devel
wrote:
>
> Le 2019-12-02 07:47, Igor Gnatenko a écrit :
> > Hi Neal,
> >
> > On Sat, Nov 30, 2019 at 11:58 PM Neal Gompa wrote:
>
> >> I think we need to recognize that we've done some poor optimization
> >> for the majority of packager wor
On Mon, Dec 2, 2019 at 8:48 AM Nicolas Mailhot via devel
wrote:
>
> Le 2019-12-02 08:17, Igor Gnatenko a écrit :
>
> > I simply can't. If somebody gets a package into repo just because he
> > wants to build foo, it is probably not very reasonable to ask them to
> > "properly" maintain it.
>
> It 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
On Mon, Dec 2, 2019, 04:43 Kevin Kofler wrote:
> Igor Gnatenko wrote:
> > 1. Do we want to package multiple streams only for "leaf" software or
> > any kind of it?
> > I believe that we need both, and we do support both. However, it might
> > not look as nice as it could:
> > * Need to create mul
Le 2019-12-02 08:38, Igor Gnatenko a écrit :
On Mon, Dec 2, 2019 at 8:28 AM Nicolas Mailhot via devel
Having all build elements in the package repos themselves is the CORE
feature that makes the “share” community dimension of Fedora work.
Anyone
can take the packages and do whatever he wants w
76 matches
Mail list logo
