nger
work anymore, which tells me it's definitely been a long time since anyone
even looked at them.
https://bugzilla.redhat.com/show_bug.cgi?id=879839
https://bugzilla.redhat.com/show_bug.cgi?id=997190
https://bugzilla.redhat.com/show_bug.cgi?id=986550
https://bugzilla.redhat.com/show_bug.cgi?id=1005518
Ben Rosser
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
On Fri, Jul 10, 2015 at 6:44 PM, Michael Schwendt
wrote:
> On Fri, 10 Jul 2015 15:25:05 -0400, Ben Rosser wrote:
>
> > Speaking as someone who relatively recently went through the process
> though
> > (and whose package(s) sat in the review tracker for two years):
> m
will push updates for F23 also.
Ben Rosser
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
On Tue, Sep 8, 2015 at 6:32 PM, Rex Dieter wrote:
> Ben Rosser wrote:
>
> > Hi everyone,
> >
> > I am not certain if any packages other than my python-pdfminer are
> > currently using my packages of the Adobe CMap resources (
> > https://github.com/a
top
environments, but it's sort of the extreme edge case of what I'm talking
about).
Now, like I said, we don't have the manpower to support multiple versions
of KDE or GNOME ourselves, so I'm not seriously suggesting we do that, or
that we should go against our prin
n packages for a node application [1] and its
dependencies, and it's increasingly difficult due to old dependencies, even
when they're not FTBFS or FTI or orphaned. I don't have the bandwidth to
take over all of these, but I'd be willing to join some kind of collective
effort to impr
On Tue, Jun 16, 2020 at 5:38 PM Jared K. Smith wrote:
>
> On Tue, Jun 16, 2020 at 3:41 PM Ben Rosser wrote:
>>
>> So... this is a lot of node.js packages, and I haven't really seen any
>> discussion of this on the lists. And at least some of these are possibly
On Wed, Jun 17, 2020 at 12:50 PM Fabio Valentini wrote:
>
> On Wed, Jun 17, 2020 at 6:30 PM Ben Rosser wrote:
> >
> > On Tue, Jun 16, 2020 at 5:38 PM Jared K. Smith
> > wrote:
> > >
> > > On Tue, Jun 16, 2020 at 3:41 PM Ben Rosser wrote:
> > &
top their retirement?
I've gone ahead and taken mocha (running tests will be useful
regardless of whether or not we start bundling NPM modules). I haven't
yet figured out what I need to take to keep it + my other node
packages alive for now, but I'll work through that this eveni
On Mon, Jun 22, 2020 at 11:34 AM Sérgio Basto wrote:
>
> On Mon, 2020-06-22 at 11:29 -0400, Ben Rosser wrote:
> > On Thu, Jun 18, 2020 at 3:09 PM Stephen Gallagher <
> > sgall...@redhat.com> wrote:
> > > The Node.js SIG is very loosely organized. If you are a pack
nly wanted to take
what I actually needed for mocha and discord-irc. I think this is the
complete list; if I'm wrong, I guess I'll find out.)
Can I do this via releng ticket or do I need to actually go to each
page on Pagure and click the button?
Ben Rosser
Ben Rosser
___
guess I'll find out.)
> >
> > Can I do this via releng ticket or do I need to actually go to each
> > page on Pagure and click the button?
>
> I've done it in bulk. Thanks for talking them.
Thanks Miro, much appreciated!
Just to add: I've also taken uglify-js
On Tue, Jun 23, 2020 at 5:24 PM Stephen Gallagher wrote:
>
> On Mon, Jun 22, 2020 at 11:53 AM Ben Rosser wrote:
> >
> > On Mon, Jun 22, 2020 at 11:34 AM Sérgio Basto wrote:
> > >
> > > On Mon, 2020-06-22 at 11:29 -0400, Ben Rosser wrote:
> > > > O
On Tue, Jun 23, 2020 at 6:38 PM Miro Hrončok wrote:
>
> On 23. 06. 20 21:11, Ben Rosser wrote:
> > Thanks Miro, much appreciated!
>
> You are welocme.
>
> However, I am afraid I have some bad news. The recent report in
> https://churchyard.fedorapeople.org/orphans.tx
On Tue, Jun 23, 2020 at 7:23 PM Miro Hrončok wrote:
>
> On 24. 06. 20 1:10, Miro Hrončok wrote:
> > On 24. 06. 20 1:07, Ben Rosser wrote:
> >> Some of my nodejs packages are an artifact of a failed attempt to
> >> package quassel-webserver [1], which I eventually
lt was *actively harmful* to vi's chances
> in my case. :P
Same here, to be honest. Being dropped into vi when I ran some command
(I think it was visudo?) was honestly pretty traumatizing as a new
Linux user a ~decade ago, and to this day one of the first things I do
on
> usage a bit nicer. 'vi' and 'emacs -nw' don't ask.
The -t/--tempfile switch for nano (and pico) does exactly this:
https://linux.die.net/man/1/nano
Ben Rosser
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe sen
On Fri, Jun 26, 2020 at 12:46 PM Zbigniew Jędrzejewski-Szmek
wrote:
>
> On Fri, Jun 26, 2020 at 12:38:40PM -0400, Ben Rosser wrote:
> > On Fri, Jun 26, 2020 at 12:32 PM Zbigniew Jędrzejewski-Szmek
> > wrote:
> > >
> > > On Thu, Jun 25, 2020 at 01:18:59PM -0400
Hello all,
I've been sitting silently in this mailing list for the past few weeks, but
just this afternoon submitted my first package review request for pdfminer,
a Python library for extracting plaintext, HTML, and images from a pdf
file: https://bugzilla.redhat.com/show_bug.cgi?id=823679
I lear
Hey all,
I'm still looking for someone to review my first package, PDFMiner:
https://bugzilla.redhat.com/show_bug.cgi?id=823679
As I am looking for a sponser, I'm afraid I can't formally review any of
your packages in return, but I'd be glad to do some unofficial reviews and
help fix any problems
On Mon, May 28, 2012 at 9:00 PM, Adrian Alves wrote:
> We can trade reviews I can review ur package and u can review mines
>
> On Mon, May 28, 2012 at 12:18 AM, Ben Rosser wrote:
>
>> Hey all,
>>
>> I'm still looking for someone to review m
In Fedora 17, when you install grub2 and generate a fresh config file, that
config is produced by grub2-mkconfig. However, when you install a kernel
update, the kernel's entry is added to the grub2 boot menu by grubby.
This produces messy grub boot menus. The entries added by grubby read
something
On Sun, Jun 17, 2012 at 10:15 PM, Josh Boyer wrote:
> I'm not willing to change the kernel spec file for this.
>
> The kernel calls 'new-kernel-pkg', which today is provided by grubby.
> Despite the similar name, grubby actually works with more than just
> grub and grub2. It also supports bootlo
On Tue, Jun 19, 2012 at 8:55 PM, Garrett Holmstrom wrote:
> Like I mentioned two days ago, the only thing that matters for EC2
> images is that the kernel post-install scripts continue to be capable
> of updating grub configuration files, which means that wholesale
> replacement of grubby with gr
On Wed, Jun 20, 2012 at 9:21 AM, Peter Jones wrote:
> I think what's actually needed is a small patch to grubby to make it keep
> track of the bounding block the current default is in and add the new
> bounding block there, so that we don't accidentally change the cosmetic
> properties of the gru
On Wed, Jun 20, 2012 at 12:42 PM, Adam Williamson wrote:
> As I understood it, the latest version of the proposal involves having
> grubby simply call grub2-mkconfig when it is dealing with grub2. So the
> rest of the 'stack' doesn't change at all.
>
Well, my proposal is basically this:
If the b
Hello all,
I'm still looking for someone to review my Python package (
https://bugzilla.redhat.com/show_bug.cgi?id=823679 ), and then hopefully
sponsor me as a packager- if anyone would be interested in doing either
that would be greatly appreciated, and I'd try to review one of your
packages in t
> --
> devel mailing list
> devel@lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/devel
> Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
>
Amen. I've been wanting to chime in here, but this is exactly how I feel o
, but chatzilla appears to still under
active development here: https://hg.mozilla.org/chatzilla/shortlog.
However, the package appears to be five releases behind now (0.9.92 was
released last August according to Wikipedia), and I don't know what
chatzilla upstream is planning to do as a
So I've had a review ticket open on bugzilla for a while now for this
package:
https://bugzilla.redhat.com/show_bug.cgi?id=823679
The software, pdfminer, bundles Adobe cmap data to process Chinese,
Japanese, and Korean languages in a pdf file. However, the question is:
does this violate the genera
On Fri, Sep 14, 2012 at 9:46 AM, Nicolas Mailhot <
nicolas.mail...@laposte.net> wrote:
>
> Adobe CMAP is used by lots of font, ps and pdf related apps and IIRC
> packaging it is currently on the wishlist.
>
> You should unbundle it and create a separate package.
>
> I don't think CMAP has security
Here's a preliminary cmap rpm review request:
https://bugzilla.redhat.com/show_bug.cgi?id=859246
So far, the only package I've worked on making this compatible with is my
own, pdfminer: https://bugzilla.redhat.com/show_bug.cgi?id=823679. So it
will almost certainly require modifications to work ni
On Wed, Oct 10, 2012 at 9:45 AM, Seth Vidal wrote:
>
> I cannot agree enough. Just b/c we've blundered down a bad route doesn't
> mean you cannot turn back.
>
> Instead of chiseling our way back, let's just revert and go.
>
> Not every decision a distribution makes is a good one, lets not get caug
On Wed, Oct 31, 2012 at 1:33 PM, Reindl Harald wrote:
>
> this is WRONG behavior
>
> any upstream-script the next years will use #!/bin/perl and
> it would be idiotic to write patches for every application
> only becasue fdora decided to make UsrMove
>
> UsrMove is a distribution-feature
> and so
on to philosophical questions like what a "logout" really means
> or should mean, before the change landed.
>
> Rich
>
> [1] https://fedoraproject.org/wiki/Changes/Policy
> --
>
I agree; just because the change happened upstream in systemd doesn't mean
that this shouldn't be evaluated in Fedora itself before being turned on by
default.
This absolutely seems like the kind of thing that should be a system-wide
change proposal (for F25, I guess).
Ben Rosser
--
devel mailing list
devel@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org
Even if I accept for the moment that letting a user keep processes running
on a system when they log out should be considered "privileged", this is a
privilege that has more or less always been granted to users by default.
Why do we suddenly need to change the default?
Sure, providing fun
ailing list
> devel@lists.fedoraproject.org
> https://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org
>
I've taken crawl, any chance you could review elog (
https://bugzilla.redhat.com/show_bug.cgi?id=1302504) in return?
Ben Rosser
--
devel mailing list
devel@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org
Flatpak?
The latter makes sense to me, the former seems potentially controversial.
Ben Rosser
--
devel mailing list
devel@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org
On Tue, Jun 14, 2016 at 4:02 PM, Michael Catanzaro
wrote:
> On Tue, 2016-06-14 at 15:40 -0400, Ben Rosser wrote:
> > This is a slight tangent, but by "remove Fedora packages", do you
> > mean
> > actually remove them from the distribution entirely or simply not
&g
ut if someone is willing to maintain a traditional package of a piece of
software that also has a flatpak available, I really think we should let
them do so. We're not, as so far as I know, in the habit of telling the
maintainers of leaf Python packages "please retire your package and let
On Thu, Jun 16, 2016 at 1:30 PM, Matthew Miller
wrote:
> On Thu, Jun 16, 2016 at 01:12:07PM -0400, Ben Rosser wrote:
> > ship pip, npm, etc? Where I become uncomfortable, and the reason I chimed
> > in on this thread initially, is with the idea that these new
> container
On Fri, Jun 17, 2016 at 9:58 AM, Matthew Miller
wrote:
> On Thu, Jun 16, 2016 at 02:24:26PM -0400, Ben Rosser wrote:
> > > I think that once the full sandboxing / portal system is in place,
> > > there _will_ be a tangible reason to prefer Flatpak.
> > Well, assumi
edora, too.
Thanks in advance,
Ben Rosser
--
devel mailing list
devel@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org
y whitelisted if
the package providing it installed.
Just an idea that I probably haven't fully thought through yet... it may
have even been something mentioned on the last thread. This just seems like
it might be a better approach than trying to patch an arbitrary number of
programs, though?
On Sat, Jul 9, 2016 at 7:27 PM, Nico Kadel-Garcia wrote:
> On Sat, Jul 9, 2016 at 5:09 PM, Ben Rosser wrote:
> > On Sat, Jul 9, 2016 at 4:56 PM, Chris Murphy
> > wrote:
> >>
> >> I think this needs to be rethought. The options right now are, modify
&
say, Python or NodeJS packages, but it might
help if we want to automatically catalog the queue.
Ben Rosser
--
devel mailing list
devel@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org
looked at the Mageia how-to-become-a-packager process briefly a while ago
(my laptop dual-boots Fedora and Mageia, although I am primarily a Fedora
person), and I did notice how it seemed more hands on than ours. A
dedicated place for new contributors to go and meet potential spon
Is anyone interested in a review swap? I think this is a relatively simple
package, so I'd be willing to take something small in exchange.
spasm-ng: A z80 assembler with extra features for TI calculators
https://bugzilla.redhat.com/show_bug.cgi?id=1325378
Ben Rosser
--
devel mailing list
t sources. Sets _builddir to current working directory.
Skips handling of -n and untar in the %setup and the deletion of the
buildSubdir."
This might be helpful, if the current working directory is the root of the
git repository. I think it's a relatively new option-- I seem to r
), and new packages
have theoretically just been tested by both the maintainer (when packaging
them) and the reviewer (when reviewing them), so there is likely less need
for further testing than there would be for other updates. And also, it
should be significantly less likely for a new package to bre
nd - Frontend for the ResultsDB
> * https://bugzilla.redhat.com/show_bug.cgi?id=1346245
>
> Thanks,
>
> Tim
>
Taken resultsdb_frontend, any chance you could look at hddfancontrol? (
https://bugzilla.redhat.com/show_bug.cgi?id=1373666).
Thanks,
Ben Rosser
___
On Thu, Dec 13, 2012 at 10:06 AM, Fernando Nasser wrote:
> What is the difficult on adding a file to yum.repo.d ?
>
> It is designed for that. Each initial page for an aditional repo would
> have instructions on how to activate it and provide a repo file to copy
> from.
The difficulty is that,
On Tue, Feb 5, 2013 at 4:21 PM, Luya Tshimbalanga wrote:
> On 05/02/13 12:09 AM, Ralf Corsepius wrote:
>
>>
>> In the Gnome2 days you had choices between functionally similar DEs.
>>
>> Times have changed ... Gnome has been forked multiply (Gnome3, MATE,
>> Cinammon), xfce/enlightenment are back.
a.redhat.com/show_bug.cgi?id=1411962
https://bugzilla.redhat.com/show_bug.cgi?id=1411961
Ben Rosser
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Many of the packages I maintain are essentially one-offs that I'm not
convinced will ever belong in a specific module-- where would things
like this end up?
Ben Rosser
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
ow_bug.cgi?id=1426962
nodejs-simple-markdown - Javascript markdown parsing, made simple:
https://bugzilla.redhat.com/show_bug.cgi?id=1463821
nodejs-irc-colors - Color and formatting for irc made easy:
https://bugzilla.redhat.com/show_bug.cgi?id=1463797
On Mon, Jul 3, 2017 at 7:01 PM, Sandro Mani wrote:
> Hi Ben
>
> I'm happy to take the first two in exchange for
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1461368
> https://bugzilla.redhat.com/show_bug.cgi?id=1465676
>
> which are simple C/C++ MinGW packages. Deal?
>
> Thanks
> Sandro
Taken
latpaks over RPMs, that doesn't particularly
bother me. So I have no issue with this particular change. But I felt
like I should chime in here because this change thread has turned (as
any discussion on flatpak seems to) into a general discussion o
swap for either of these.
Ben Rosser
[1] https://github.com/mrjoes/sockjs-tornado
[2] http://www.archiveteam.org/index.php?title=Main_Page
[3] https://pypi.python.org/pypi/seesaw
--
devel mailing list
devel@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org
current developers" writeup somewhere? (by which I mean
"Fedora developers" in general).
Ben Rosser
[1] https://fedoraproject.org/wiki/Modularity
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
* nodejs-int64-buffer: https://bugzilla.redhat.com/show_bug.cgi?id=1397620
* nodejs-qtdatastream: https://bugzilla.redhat.com/show_bug.cgi?id=1397621
(depends on nodejs-int64-buffer)
Ben Rosser
___
devel mailing list -- devel@lists.fedoraproject.org
To
i build fired in response to (among a few other
things) a glibc upgrade, I wonder if this is a glibc bug on aarch64?
Ben Rosser
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
ike it or not, users, myself included, install nonfree software
like Steam on systems and generally expect it to continue working from
release to release.
Ben Rosser
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
estingly, it seems that "appstream-util validate-relax
--nonet" doesn't seem to care. It happily validates tilp2's appstream
information [2], which is why I never noticed this at the time. I
would think that "referenced desktop file doesn't exist on system"
shoul
uthor and
still compatible with the new license, as quassel-irssi is the only
Fedora package depending on quasselc at this time.
Ben Rosser
[1] https://fedoraproject.org/wiki/Licensing:Main?rd=Licensing#License_Changes
[2]
https://github.com/phhusson/QuasselC/c
eriod of time... and
nothing I've read in any of these threads so far has helped reassure
me that's not the case.
Not saying you're wrong that it would be nice to have the ability to
poll a broader selection of packagers. But I'm not sure using
n than it is
the first thing most new contributors will interact with, so perhaps
it is in our interest to make it as pleasant as possible.
Ben Rosser
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lis
On Wed, Oct 2, 2019 at 8:17 PM Ben Rosser wrote:
>
> On Wed, Oct 2, 2019 at 1:59 PM Pierre-Yves Chibon wrote:
> > There are regularly people complaining on this very list about how hard
> > packaging has become. So here is a thread trying to see if you can come up
> &
w request if
>> we can get this unretired before the deadline.
>
>
> It looks like this has been un-retired, so I'll go ahead and try to push an
> updated build to rawhide just as soon as the Koji outage is over.
Oops, I missed that you had requested a re-review.
Thanks! L
Pagure showed that information too. If nothing else, it
would save me a click or two when trying to check if a package is up
to date.
> Trying to improve the package review process is something that has been in my
> radar for a while now but n
ideline compliant)
6. rpmbuild -bs && mock ../SRPMS/foo*.src.rpm until it builds (and is
guideline compliant)
7. Upload somewhere when it is ready for review
I agree that this might not be the ideal workflow to teach new
packagers, but I don't think it is terrible.
It's certainly true that the loudest and most unhappy voices tend to
dominate discussions, but so far I haven't seen many people speak up
who are enthusiastic about modularity who aren't also involved in it
in some way.
Granted, that could well change over time as improvements
ora. We should decide what is and isn't acceptable to
modularize, what the rules are and aren't for creating and upgrading
streams, and so on. And if we can't figure out a way to square the
goals for modularity with the necessary guidelines to not cause major
problems in the distri
maintainer first:
https://fedoraproject.org/wiki/EPEL/GuidelinesAndPolicies#Getting_a_Fedora_package_in_EPEL
https://fedoraproject.org/wiki/Getting_a_Fedora_package_in_EPEL
Ben Rosser
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscrib
pkgdb before implementing new features like stream
expansion.
But in any case, I'm really glad that we do now finally have anitya
integration and easy de-orphaning back in pkgdb. Thanks to everyone
who made this happen!
Ben Rosser
___
On Tue, Dec 3, 2019 at 3:18 AM Tom Hughes wrote:
>
> Ben Rosser was working on sorting out grunt. In fact I believe he
> took the first of those at least.
>
> Tom
>
> On 03/12/2019 07:45, Vít Ondruch wrote:
> > According to [1], these are the packages which need to
of
that RPM?
(I realize that in this particular case, Igor is on FESCo, and so had
the policy been followed more carefully, he would have been aware
anyway).
Ben Rosser
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email
e required. Still, the policy requires an
announcement on this list, so here it is. :)
Cheers,
Ben Rosser
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Condu
mizdebsk, orphan 3 weeks ago
...
> reflections orphan 4 weeks ago
I have one Java package that requires both of these... although I'm
sure if I take them I'll wind up needing to take more of the Java
stack too.
I guess I'll t
Gs/Education
> [2] https://fedoraproject.org/wiki/SIGs/University
Hi Timothée,
I think this is a great initiative! Maybe it's a bit early to ask, but
I'm curious what sort of projects you see a SIG focusing on?
(If grad students would be welcome here too, I might be interested. :) )
C
Hi all,
Is anyone interested in a review swap for a Python(-ish) package?
cocotb: https://bugzilla.redhat.com/show_bug.cgi?id=1747574
Happy to review anything in exchange.
Cheers,
Ben Rosser
___
devel mailing list -- devel@lists.fedoraproject.org
To
the
use case of the "ordinary packager", not the "expert packager". And I
think that's packages with limited divergence from upstream (only a
few patches) that only one, _maybe_ two, people regularly touch.
Ben Rosser
___
devel mai
a bad idea
and won't improve things. We need to keep the simple/everyday use
cases in mind here.
I like that I can build a Fedora package with just a specfile--
essentially, a bit of metadata about how to build and install a
package-- and don't need to
On Thu, Sep 26, 2019 at 5:29 PM Pierre-Yves Chibon wrote:
>
> On Thu, Sep 26, 2019 at 04:46:32PM +0200, Ben Rosser wrote:
> > On Thu, Sep 26, 2019 at 4:29 PM Pierre-Yves Chibon
> > wrote:
> > > There is a clear initial rejection of a PR-only contribution model. I
>
tired just under eight weeks ago for being FTBFS-- on
2019-08-08. Hopefully it still is within the deadline for not
requiring rereview (that's eight weeks on Thursday)!
I'll submit a releng ticket, and am notifying devel as requested by the policy.
S
re.io/releng/issue/9236
Thanks in advance,
Ben Rosser
___
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.org/en-US/project/code-of-co
On Thu, Feb 13, 2020 at 12:01 PM Jerry James wrote:
>
> I'm trying to get an f32 branch for a newly created package. Branch
> creation has failed twice now with the error in $SUBJECT:
>
> https://pagure.io/releng/fedora-scm-requests/issue/22127
>
> Can I get a human to look at that ticket instead
thread from September, for
instance:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/FZZVKXUOW3TNUNX2JV2JGPUWFFGS3V3C/#426PWWHO6FVWBQSC6PP2D5HIKBONY6UE
Ben Rosser
___
devel mailing list -- devel@lists.fedoraproject.org
To
there was an opposition to the
idea, there just wasn't enough time or person-power to do it:
https://pagure.io/pagure/issue/2549
Ben Rosser
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedo
I am complaining on the devel list and not
actually doing anything to help, so I guess I'm part of the problem
too).
Ben Rosser
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedo
On Tue, Dec 11, 2018 at 4:07 PM Till Maas wrote:
>
> Hi Ben,
>
> On Tue, Dec 11, 2018 at 11:42:51AM +0100, Ben Rosser wrote:
>
> > I don't know. I feel like we could do a lot to improve the experience
> > of packaging by investing time into fixing these sorts of m
7;t think it
is going to happen on its own without some sort of organization to
make it happen, and to try and organize/focus the work. I don't know
if that organization requires an Objective to make happen, but I think
it would be nice to enshrine this as one of our medium-term goals.
Cheers,
interested in helping out, please feel free to add your own thoughts
as well.
Sincerely,
Ben Rosser
[1]
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/FYNU7W6KQQWA65JWVPUFDHKUP3RX6EKR/
[2] https://fedoraproject.org/wiki/Objectives/Packager_Experience
__
stream releases
which built just fine with Python 3.7-- upstream still seems to be
active.
I've submitted a new review here (and also built the package in copr):
https://bugzilla.redhat.com/show_bug.cgi?id=1665303
Happy to exchange a review swap.
nd
like a good idea? (Maybe #fedora-packaging, if it is not in use? Or
maybe #fedora-packaging-qol or something instead.)
Cheers,
Ben Rosser
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fe
could then be deleted from copr once the package gets
approved (or removed if the review is closed WONTFIX, or something).
Ben Rosser
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
the change, but it's not clear to me that
there is one beyond a desire to get away from using the name "yum".
Ben Rosser
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.o
ut I think the difficulty is that you can't rely on ffmpeg
being provided by RPM Fusion, because users could have a
non-RPM-Fusion repository on their system that provides ffmpeg, so if
could be dangerous to make assumptions about what the "ffmpeg" package
actually is?
Cheers
a group* should prepare and submit an objective proposal
describing what they want to work on.
Ben Rosser
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: http
esults to the packager, I bet
we would catch a lot of the licensing/bundling problems.
Anyway, I really like this idea. Maybe we should still require
quasi-manual reviews for new contributors as part of the sponsorship
process, though?
Ben Rosser
___
deve
1 - 100 of 138 matches
Mail list logo
