The following is the list of topics that will be discussed in the
FESCo meeting Friday at 16:00UTC in #fedora-meeting on
irc.freenode.net.
To convert UTC to your local time, take a look at
http://fedoraproject.org/wiki/UTCHowto
or run:
date -d '2017-11-17 16:00 UTC'
Links to all issues belo
The following is the list of topics that will be discussed in the
FESCo meeting Friday at 16:00UTC in #fedora-meeting on
irc.freenode.net.
To convert UTC to your local time, take a look at
http://fedoraproject.org/wiki/UTCHowto
or run:
date -d '2017-11-10 16:00 UTC'
Links to all issues belo
With Bodhi 3, we don't use python-fedmsg-atomic-composer anymore:
https://src.fedoraproject.org/rpms/python-fedmsg-atomic-composer
I probably should have just retired it, but I figured I'd orphan it in
case someone out there still wants it to exist for some reason. I also
forgot that it is not po
On 10/19/2017 04:52 PM, Cole Robinson wrote:
> Maybe just switch the stable
> branches back to FAS_USERNAME which avoids the GDM issue
Thanks for the thougtful reply Cole! I've filed an issue to follow your
suggestion here:
https://bugzilla.redhat.com/show_bug.cgi?id=1509094
signature.asc
Desc
Greetings!
I would like to unretire python-diff-cover. It seems to have been
retired due to being orphaned without being adopted.
https://bugzilla.redhat.com/show_bug.cgi?id=1508020
signature.asc
Description: OpenPGP digital signature
___
devel maili
Greetings!
I would like to unretire python-jinja2_pluralize. It seems to have been
retired due to being orphaned without being adopted.
https://bugzilla.redhat.com/show_bug.cgi?id=1508016
signature.asc
Description: OpenPGP digital signature
___
devel
On 10/29/2017 07:56 AM, Matthew Miller wrote:
> On Sat, Oct 28, 2017 at 11:06:08PM -0400, Randy Barlow wrote:
>>> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/UDXVXLT7JXCY6N7NRACN4GBS3KA6D4M6/
>> It's also documented here:
>> h
On 10/27/2017 12:56 PM, Alexander Ploumistos wrote:
> On Fri, Oct 27, 2017 at 7:12 PM, Christopher
> wrote:
>> I see a new option in Bodhi called "Push to Batched".
>> After clicking, it now gives the familiar "Push to Stable" option.
>>
>> How does this work, what is meant by "Batched", how does
On 10/22/2017 09:04 AM, Dennis Gilmore wrote:
> updates does not have composes it has mashes, the behaviour is expected
> to be different, the problem boils down to the fact that if a package
> is made multilib indirectly, i.e. it is only pulled in because some
> external package that is multilib r
Greetings fellow Fedorans,
We're about to release Bodhi 3.0.0[0] upstream, which has a backwards
incompatible CLI change[1] that I am considering backporting to the
stable Fedoras, but I wanted feedback first before I do that.
The Bodhi 2 CLI will use the USERNAME environment variable when
authen
On 10/17/2017 05:53 PM, Randy Barlow wrote:
> I do believe the CLI would allow you to push this one to stable as a
> work around as suggested by Adam.
To make it easy for you, the bodhi-2 CLI command to do this is:
$ bodhi updates request FEDORA-2017-a62dd57720 stable
If you are on Fed
On 10/17/2017 09:44 AM, Michael Cronenworth wrote:
> On 10/06/2017 01:47 PM, Randy Barlow wrote:
>> but either way you can push it to batched,
>> and you can push it to stable too.
>
> Except when it was auto-pushed to batched.
>
> https://bodhi.fedoraproject.org/upd
On 10/15/2017 12:34 PM, Neal Gompa wrote:
> I would suggest that you submit librealsense1 as a separate package,
> instead. The applications that use the older versions should probably
> be linked to the older one, but things should progressively migrate to
> the newer one.
This sounds like a reas
I filed an issue to request this change:
https://github.com/fedora-infra/bodhi/issues/1895
signature.asc
Description: OpenPGP digital signature
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.f
On 10/14/2017 12:45 PM, Peter Robinson wrote:
>> Since branched releases have the updates-testing repository enabled by
>> default, won't the effect you desire happen anyway?
> No, because the updates-testing repo is enabled by default for
> installs, it's not enabled for the composes so things lik
On 10/12/2017 03:06 AM, Peter Robinson wrote:
> It seems batched updates is turned on for F-27 [1], surely it makes
> sense for updates to go straight out in the development cycle, this
> affects things getting into the nightly composes for testing in live
> images and other such things.
>
> I fee
On 10/06/2017 06:18 AM, Kamil Paral wrote:
> So if the update doesn't use karma autopush, and the maintainer clicks
> "Push to stable", will this go to batched queue or directly stable? And
> if directly stable, is there a way to put it into the batched queue for
> such updates?
Hello Kamil!
A no
FESCo failed to achieve quorum today, as several members were traveling
(enjoy!). Here's this week's logs:
Logs:
https://meetbot.fedoraproject.org/fedora-meeting/2017-10-06/fesco.2017-10-06-16.00.txt
Log:
https://meetbot.fedoraproject.org/fedora-meeting/2017-10-06/fesco.2017-10-06-16.00.log.html
Greetings fellow Fedora friends!
bodhi-2.11.0[0] has been deployed to production, and this release
introduces a new state for updates where the request can be "batched".
The purpose of this state is to give updates a place to sit once they've
reached the stable requirements until the next weekly b
The following is the list of topics that will be discussed in the
FESCo meeting Friday at 16:00UTC in #fedora-meeting on
irc.freenode.net.
To convert UTC to your local time, take a look at
http://fedoraproject.org/wiki/UTCHowto
or run:
date -d '2017-10-06 16:00 UTC'
Links to all issues belo
On 09/29/2017 03:54 AM, Hedayat Vatankhah wrote:
> I've recently added 2 new packages, but when I tried to add them to
> F27/F26 updates, it doesn't recognize them in the "Packages" box and
> says: "Unable to find any packages that match the current query". BTW, I
> can create the desired update, t
Greetings!
During Friday's FESCo meeting[0] we were asked to approve a change to
the release schedule to accommodate translation string freeze deadlines
that somehow got left out of the new "no-alphas" schedule.
Several participants pointed out that Fedora has not enforced the
"string freeze" in
Here are links to the summary and minutes from today's FESCo meeting:
https://meetbot-raw.fedoraproject.org/fedora-meeting/2017-09-08/fesco.2017-09-08-16.00.txt
https://meetbot.fedoraproject.org/fedora-meeting/2017-09-08/fesco.2017-09-08-16.00.log.html
signature.asc
Description: OpenPGP digita
On 09/08/2017 10:51 AM, Tom Hughes wrote:
> Surely (c) would make a mockery of change system. What would not make a
> mockery of the change system would be to invoke the contingency plan.
>
> Except there doesn't seem to be one:
>
> https://fedoraproject.org/wiki/Changes/Modular_Server#Contingenc
On 09/08/2017 02:40 AM, Nikos Mavrogiannopoulos wrote:
>> The currently implementation of the Bodhi CLI subclasses
>> fedora.client.OpenIdBaseClient, which does not support kerberos:
>>
>> https://github.com/fedora-infra/bodhi/blob/2.10.1/bodhi/client/bindin
>> gs.py#L105
>
> Is there a bug opened
On 09/07/2017 09:14 AM, Nikos Mavrogiannopoulos wrote:
> It works with the browser indeed. Would it work with command line tools
> like bodhi as well?
The currently implementation of the Bodhi CLI subclasses
fedora.client.OpenIdBaseClient, which does not support kerberos:
https://github.com/fedor
On 09/06/2017 08:25 AM, Nikos Mavrogiannopoulos wrote:
> * To submit a changed package: bodhi: raw passwords
> * To subscribe to a mailing list: lists.fedoraproject.org: openid?
A minor correction here: Bodhi also uses OpenID.
signature.asc
Description: OpenPGP digital signature
_
Following is the list of topics that will be discussed in the
FESCo meeting Friday at 16:00UTC in #fedora-meeting on
irc.freenode.net.
To convert UTC to your local time, take a look at
http://fedoraproject.org/wiki/UTCHowto
or run:
date -d '2017-09-08 16:00 UTC'
Links to all issues below ca
On 08/13/2017 11:02 AM, Zbigniew Jędrzejewski-Szmek wrote:
> On Sun, Aug 13, 2017 at 04:45:57AM -, Andrew Toskin wrote:
>> If you're talking specifically about the Bodhi web UI, then I think I'm
>> having the same problem: After I logged in, I clicked on Create > New
>> Update, tried to searc
On 08/10/2017 06:46 PM, Ravindra Kumar wrote:
> I forgot to mention that Bodhi web interface did not offer any
> suggestions when I typed 'open-vm-tools' package name. This was bit
> surprising and I could not use Bodhi web interface as a workaround.
This is a known issue and is planned to be fixe
On 08/03/2017 05:41 AM, Kamil Paral wrote:
> Randy, can you please describe how it's going to change in terms of koji
> tags? How the (new) koji tags are going to be named, when packages enter
> them, when they leave them (including the -pending tags). Or is there a
> diagram somewhere? I'd like to
On Tue, 2017-08-01 at 16:47 -0400, Matthew Miller wrote:
> What about the opposite? Should we require classification for bugfix
> and security updates?
I'd say it wouldn't hurt to require it. It always makes data nice if
the parser of the data can know that a field is guaranteed to exist so
they d
On Tue, 2017-08-01 at 16:11 -0400, Matthew Miller wrote:
> Yeah, exactly. Do you want a new RFE issue for this?
Sure, it makes sense to me. Though I will say that there probably isn't
much tangible harm done leaving it as it is, even though it doesn't
make sense.
signature.asc
Description: This i
On Tue, 2017-08-01 at 15:31 -0400, Matthew Miller wrote:
> I think this is why we don't just automatically make security fixes
> all
> high priority but instead have a separate field. Many security
> updates
> fix problems which only happen in unlikely configurations, or have
> extremely minor cons
On Tue, 2017-08-01 at 15:31 -0400, Matthew Miller wrote:
> (Hmmm. And should enhancement
> and new packages _get_ a severity option? Maybe that should be locked
> to "unspecified"?)
Hahaha, "This newpackage update is urgently severe! Have some severe
new features!"
signature.asc
Description: This
On Tue, 2017-08-01 at 11:02 -0500, Dennis Gilmore wrote:
> I would really like to see us have a single unified
> view on update management at a distro level and not having different
> tools implementing their own behaviours.
I agree with Dennis here - not all users of Fedora use the Gnome
Software
On Tue, 2017-08-01 at 08:26 +0100, Michael Catanzaro wrote:
> Also, if I mark a security update as low priority, that means it
> really is low priority. There's no need for many security updates to
> skip batched. Many are e.g. minor DoS vulnerabilities that are
> unlikely to be exploited ever, let
On Mon, 2017-07-31 at 22:13 -0400, Ben Rosser wrote:
> 1. Are you saying that this feature will be *activated* once it's
> merged, or just that it will be available should Fedora decide to
> turn
> it on as a policy decision? I'm assuming it's the latter, as I don't
> think I've seen a change propo
On Mon, 2017-07-31 at 21:00 -0400, Matthew Miller wrote:
> This is awesome, Randy! Thanks!
Caleigh did the hard work ☺
signature.asc
Description: This is a digitally signed message part
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscr
To necromance this old thread, I wanted to give a heads up that we're about to
get a cool feature in Bodhi in response to this thread:
https://github.com/fedora-infra/bodhi/pull/1678
With that pull request, there will be a new request state called "batched".
When non-priority[0] updates reach t
On Sat, 2017-07-29 at 17:25 +0200, Jos de Kloe wrote:
> FAILED: BuildError: package metar not in list for tag f27-pending
>
> does anyone know what is wrong, and how to solve it?
Hi Jos!
I believe this can happen for a short while after a package is added
(or in your case, adopted). Adding a pac
On Fri, 2017-07-28 at 14:11 -0400, Colin Walters wrote:
> First, I don't see a need for even mild pejoratives; instead of
> "normal" you could say
> for example "other editions".
My apologies - I was just struggling with terminology. No offense
intended.
signature.asc
Description: This is a digit
On Fri, 2017-07-28 at 12:41 -0400, Colin Walters wrote:
> I'm opposed to switching the meaning of `/usr/bin/python` for AH
> anytime soon. It's just going to break stuff, and to me the gain is
> quite
> low.
One of Fedora's stated goals is to remain close to the upstream.
Upstream Python is going
On Fri, 2017-07-21 at 07:31 +0100, Peter Robinson wrote:
> > Keep in mind that Ansible is also something small-scale admins
> don't use. It
> > only makes sense at all if you have at least 2 servers, and it is
> only
> > really worthwhile if you have several, mostly identical servers. If
> you have
On Thu, 2017-07-13 at 00:36 +0200, Kevin Kofler wrote:
> Koji will take care of the signing for Flatpaks
> built in Koji as it does for RPMs built in Koji.
Sigul[0] is actually the system that signs the packages. They are
placed into a Koji tag when they need to be signed, and when Sigul is
done
On Mon, 2017-07-10 at 11:40 -0500, Adam Miller wrote:
> The main motivation for bundling as of late is golang[0], it's
> extremely common out in the community for software to pull in
> "Vendored" libraries even if they are exact copies of remote
> upstreams
> (this is common with tools like godep[1
The upstream for erlang-p1_pam has changed their license from GPLv2 to
ASL 2.0 in version 1.0.1[0]. I almost missed it since that's a .z
release! I plan to make that update only on Rawhide[1] (to version
1.0.3).
[0] https://github.com/processone/epam/blob/master/CHANGELOG.md
[1] https://bugzilla.
On Fri, 2017-07-07 at 11:55 -0500, Adam Miller wrote:
> My question to the Fedora Contributor Community is, how should we
> handle this?
I am guilty of doing this a few times in a couple of my packages. My
reasons when I did it were that I didn't know the version, and didn't
know an easy way to de
On Thu, 2017-06-08 at 22:17 +0200, Adam Samalik wrote:
> You add the package and other people start to use it. That's great
> until you need to change the version, but can't, because other people
> started to use it as a dependency and it would break their stuff.
I recently heard that it will be i
On Sun, 2017-06-04 at 08:50 +0200, Pierre-Yves Chibon wrote:
> Do you think we could change this to check:
> - has the user rights on that particular package?
> - is the user a member of the packager group?
I believe it does both of these currently.
signature.asc
Description: This is a digitally
On Sat, 2017-06-03 at 09:32 +0200, Pierre-Yves Chibon wrote:
> Bodhi I believe also check this, maybe Randy could confirm this.
I think I just answered this in another e-mail. Let me know if you need
more info.
signature.asc
Description: This is a digitally signed message part
___
On Fri, 2017-06-02 at 21:42 +0200, Pierre-Yves Chibon wrote:
> What do you think?
Bodhi also currently cares about users being in the packager group to
decide whether they can create buildroot overrides (I think, not
actually 100% sure). It uses pkgdb to decide whether a user has access
to create
On Fri, 2017-05-26 at 13:04 -0400, Charalampos Stratakis wrote:
> Seeing this also on my F25 machine.
Hmmm, I'm not sure why, but I don't see this on my F24 machine with the
bodhi client (which has the same version of bodhi and python-fedora
though obviously a different release since it's F24):
$
On Fri, 2017-05-26 at 08:33 +0200, Zdenek Dohnal wrote:
> I asked about this message on IRC #fedora-admin channel and they told
> me
> this message should disappear after future updates (no specific
> version
> wasn't told).
I wrote a bit about this here:
https://bugzilla.redhat.com/show_bug.cgi?
On Fri, 2017-05-19 at 11:48 -0400, Matthew Miller wrote:
> Yeah, I just tested and this works:
>
> $ sudo dnf upgrade --advisory FEDORA-2017-f590422f5b
Fantastic! I'm bummed that I now need a new idea, but I'm glad this
exists because I will use it ☺
The Koji thing could be cool, but it is getti
On Fri, 2017-05-19 at 15:34 +0100, Sérgio Basto wrote:
> https://bugzilla.redhat.com/show_bug.cgi?id=1234930#c18
>
> claims that dnf equivalent of “yum update --security” is available in
> dnf 2.something
>
> also
> https://unix.stackexchange.com/questions/221983/dnf-equivalent-of-yum
> -update
Hello!
I had an idea for a summer internship project, but I wanted to ask my
fellow Fedora devs if something like this already exists so it doesn't
get created as a duplicate project.
The idea is to create a dnf plugin that would allow you to do this:
$ sudo dnf upgrade FEDORA-2017-30604deb62
T
There is a common issue that people have been hitting with the Bodhi
CLI. If you've been seeing lots of HTML printed to your terminal and a
traceback that mentions HTTP 403 codes, the following updates will
help:
Rawhide: https://koji.fedoraproject.org/koji/buildinfo?buildID=887188
F26: https:
On Fri, 2017-05-05 at 17:35 -0500, po...@pouar.net wrote:
> Though according to the Fedora Wiki, they say to "inform upstream".
> Should I do this first before creating a review request for the
> package or wait until the package is approved?
You can do it in either order - it's more about introdu
The following updates address the bodhi client issue:
Rawhide: https://koji.fedoraproject.org/koji/buildinfo?buildID=887188
F26: https://bodhi.fedoraproject.org/updates/FEDORA-2017-26b2a7f9ba
F25: https://bodhi.fedoraproject.org/updates/FEDORA-2017-d069d3faf9
F24: https://bodhi.fedorap
On Fri, 2017-05-05 at 19:41 +0100, Michael Young wrote:
> See https://bugzilla.redhat.com/show_bug.cgi?id=1445294 and in
> particular
> the patches linked to in Comments 6 and 7.
Indeed, I'm working right now at getting a bodhi-2.6.2 update released.
Also, Patrick has made a python-fedora-0.9 rel
On Fri, 2017-05-05 at 09:46 +0200, Vít Ondruch wrote:
> I love this well explained license changes: "Ah, removing file
> extension, that is good opportunity to change the license as well" :)
> https://github.com/devopsgroup-io/vagrant-hostmanager/commit/e97bc6fd
> 169bed754755d8f3f68786610ef48281
vagrant-hostmanager has changed its license from MIT to MPLv2.0 with
version 1.8.6:
https://github.com/devopsgroup-io/vagrant-hostmanager/compare/v1.8.5...v1.8.6
Due to this, I only plan to release 1.8.6 on Rawhide[0].
[0] https://bugzilla.redhat.com/show_bug.cgi?id=1447820
signature.asc
Descr
On Wed, 2017-05-03 at 19:51 -0500, Richard Shaw wrote:
> I have two packages which I got notifications that they were
> "ejected" from the push…
> Bodhi is giving me the option to push it to testing again but the
> koji tag is already showing f26-updates-testing...
This was due to a Bodhi mash ru
On Mon, 2017-03-27 at 12:26 +, Petr Pisar wrote:
> Or are these test failures expected to be delivered through FMN only?
This is currently how they are handled. I have my FMN settings
configured to send these to me over IRC and that works well for me.
However, I don't believe that is the defau
On Fri, 2017-03-24 at 15:37 -0400, Matthew Miller wrote:
> Oh good — this was going to be my comment… having different main
> contacts and package admins might be.
Oh good — this was going to be my comment ☺
I do like and use the ability to have bug reports for different
branches go to different
On Fri, 2017-03-24 at 13:38 +, Petr Pisar wrote:
> third-party == from different host (bodhi.fedoraproject.org. !=
> taskotron.fedoraproject.org.).
The JavaScript that loads the taskotron results from resultsdb is in
Bodhi, not taskotron:
https://github.com/fedora-infra/bodhi/blob/2.4.0/bodhi
Hello!
I would like to unretire nodejs-grunt-contrib-copy[0], and have filed a
package re-review:
https://bugzilla.redhat.com/show_bug.cgi?id=1432995
[0] https://bugzilla.redhat.com/show_bug.cgi?id=1432995
signature.asc
Description: This is a digitally signed message part
_
On Tue, 2017-03-14 at 22:55 +0100, Michael Schwendt wrote:
> The review is highly misleading, and the latest spec file does not
> include any headers in the package:
>
> %files
> %license COPYING
> %doc EXTENDING.html FAQ NEWS README
> %{_bindir}/arduino-ctags
> %{_mandir}/man1/arduino-c
Hello!
During a package review[0], I suggested that a CLI application's header
files need to go into a -devel subpackage (they are currently not being
packaged, except for the -debuginfo subpackage.) The reviewer
disagrees, but fedora-review uses the word must. I went to the
packaging guidelines[1
On Tue, 2017-02-28 at 23:39 +, Richard W.M. Jones wrote:
> I get this doing 'fedpkg update':
>
> fedora.client.bodhi.BodhiClientException: Unable to create update.
> Authentication required
>
> It's unclear what authentication is required, but I have a valid ssh
> key and live Kerberos ke
Hello Fedora devs!
Today I deployed Bodhi 2.4.0 to production. It's got a few new features
and some bug fixes. You can read the release notes here:
https://github.com/fedora-infra/bodhi/blob/2.4.0/docs/release_notes.rst#240
If you find issues with Bodhi, please let us know!
https://github.com/f
On Fri, 2017-02-17 at 05:08 +, Zbigniew Jędrzejewski-Szmek wrote:
> Filing bugs for transitive FTBFS during a mass rebuild isn't
> particularly helpful as it is done now.
I think it is helpful, because even if it is not the fault of the
package that failed to build, the package does still need
On Thu, 2017-02-16 at 09:36 -0500, Steve Grubb wrote:
> Yesterday I built a security update for the suricata package, 3.2.1-
> 1:
>
> https://koji.fedoraproject.org/koji/packageinfo?packageID=10021
>
> Any time I try to create the bodhi new release, it finds an older
> build, 3.2-1.
> Typing the
Thanks for all the input! I went with the popular option of calling it
qrcode-generator and inviting comaintainers to add subpackages in the
future if they desire:
https://bugzilla.redhat.com/show_bug.cgi?id=1422344
signature.asc
Description: This is a digitally signed message part
__
Hello!
In working on packaging Ampache, I found a dependency that has a
bundled version of this file:
https://github.com/kazuhikoarase/qrcode-generator/blob/master/js/qrcode.js
I started working on doing the right thing and packaging that file
separately, but it seems that the repository also ha
On Sun, 2017-02-12 at 18:27 +0530, Parag Nemade wrote:
> I've got one nodejs module package in need of review. I will be happy
> to review your package requests in return.
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1408105
I've taken it. I've got quite a few open review requests, so take you
On Mon, 2017-01-16 at 10:30 -0500, Matthew Miller wrote:
> > BTW, perhaps another way is to use bundled versions for these, to
> not
> > expose them as something "stable and maintained".
>
> Yeah, I was going to make this suggestion too. Seems like a
> reasonable
> use of bundling — having them se
Hello Fedora devs!
I recently started working on getting Ampache packaged for Fedora, and
it turns out it is no small feat. There are two problems:
0) 5 of the packages have been abandoned upstream, and have been
replaced with different packages that are now recommended. Ampache is
aware of this
On Thu, 2017-01-05 at 17:02 +, Jonathan Wakely wrote:
> Which definitely changes how software is built.
Containers also change the way software must be written in some cases,
since they expect there to be one main process and don't expect that
main process to interact with other "main" process
Hello fellow devs!
I recently unorphaned python-ipdb and in working to get it updated to
it's latest release I noted that upstream's license has shifted from
GPLv2+ to BSD with their 0.9 release (Rawhide currently has 0.8.3). I'm
working on updating Rawhide to 0.10.1, but I will leave F24/25 on
0.
On Wed, 2016-12-21 at 20:16 +0100, Mattia Verga wrote:
> Second question: I've uploaded new sources by using the new kinit
> method, but I see that the sources are actually double uploaded
> (upload
> reaches 100% and then restart again a second time). Is that normal?
I also noticed this change,
On Wed, 2016-12-21 at 12:08 -0500, Matthew Miller wrote:
> I see that the fc-cache data is arch-specific, but is it really
> host-specific? What if we just pre-generated it at *build* time and
> put
> it into /usr/share or /usr/lib? I guess that'd end up making font
> files
> archful, but that's no
On Wed, 2016-12-21 at 09:42 +0100, Ralf Corsepius wrote:
> > The fontconfig cache files are placed onto /var/cache/fontconfig
> > now.
> > this seems incompatible with the ostree model. so this is a
> > proposal
> > to move it to /usr/lib/fontconfig/cache.
>
> This proposal likely is incompatible
Hello!
I maintain ejabberd and I've got an issue filed about ejabberd's
policykit policy being desktop-centric[0]. I've done some reading about
how I could alter the policy to make it so that it doesn't expect the
user to be at a seat, but I can't help but think that sudo is a great
way to handle
On Mon, 2016-12-12 at 14:33 -0700, Kevin Fenzi wrote:
> First, I'll note you don't need to get a new ticket every day, you
> can
> just renew with 'kinit -R'. I am not sure what env kinit needs, but
> you
> may even be able to do this from a cron job. That will work for 1
> week.
You can even use
On Sun, 2016-12-11 at 18:34 -0600, Dennis Gilmore wrote:
> Additionally, via GSSAPI many browsers allow you to seamlessly login
> to any of our ipsilon using applications simply by clicking on the
> login
> button ( bodhi, fedorahosted trac, elections, fedocal, mailman3, etc)
This is fantastic,
On Sat, 2016-11-26 at 06:26 +0100, Ralf Corsepius wrote:
> I have been trying to push a package chain consisting of 2 new
> packages,
> which are required to update a 3 package, to Fedora:
>
> The first package hit "the freeze". It took ~3 weeks to make it to
> fc25
> stable. The second package
Hello Friends!
Igor and I were having a discussion on a package review ticket[0] about
how to handle a bundled library that seems to have no upstream that
either of us can find, and for which we don't know its version!
According to the packaging guidelines, it is OK to bundle the library
in certa
Hello fellow Fedora developers!
I wanted to inform you all that our change proposal for adding non-RPM
artifacts to Bodhi[0] is not going to be done in time for Fedora 26 as
was previously planned. There are simply too many things on my plate
for Fedora 26, and so it's been decided that we'll have
On Fri, 2016-10-28 at 10:15 -0400, Mike Miller wrote:
> My GitHub username
> is milleruntime.
Welcome Mike! Your username made me chuckle…
signature.asc
Description: This is a digitally signed message part
___
devel mailing list -- devel@lists.fedorapro
There are some good thoughts in this thread. A few people have
suggested that getting the update process to go faster would really
help with these problems, and I agree.
Patrick Uiterwijk has recently made quite a few contributions to Bodhi
that a) make it more reliable, and b) allow it to gate on
Thanks to a lot of help from fale and puiterwijk, I've now built bodhi-
2.2.0-1.fc26 in Rawhide and it should be pushed out soon. This update
is not backwards compatible, so it will only go out to Fedora Rawhide
and EPEL 7 (with special permission). If you would like to use the
bodhi 2 client on Fe
I've filed an issue to track this problem:
https://bugzilla.redhat.com/show_bug.cgi?id=1372461
Thanks again!
signature.asc
Description: This is a digitally signed message part
--
devel mailing list
devel@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/devel@lists.fedoraprojec
On Thu, 2016-09-01 at 20:45 +0200, Fabio Alessandro Locati wrote:
> The F24 copr seems to be broken. I've enabled it, updated all
> packages
> and running 'bodhi', it seems to be broken:
>
> pkg_resources.DistributionNotFound: The 'bodhi==2.1.8' distribution
> was
> not found and is required by t
I forgot to mention, I'm also maintaining a Copr for Bodhi 2 for Fedora
23 and 24:
https://copr.fedorainfracloud.org/coprs/bowlofeggs/bodhi/
Copr doesn't seem to have Fedora 25 buildroots yet, but I'll try to
remember to add Fedora 25 as well once it does.
signature.asc
Description: This is a di
Hello again Fedora friends!
I just built bodhi-2.1.8-1.fc26 for Rawhide, and wanted to give you a
heads up as it is a backwards incompatible change. Rawhide previously
had bodhi-0.9.12.2-5.fc25.noarch so this is a pretty major update.
The bodhi client is probably what most of you are used to inte
Hello my fellow Fedora friends!
It's 01:00 in my local time and perhaps I should be resting instead of
trying to figure out chicken-and-egg problems at such a time, but my
tired mind is on the fence about the solution to one of my tickets and
I would love the input of others:
https://bugzilla.red
erlang-p1_zlib-1.0.1 has changed the license from GPLv2 to ASL 2.0. I'm
making the change in the spec file as needed, but thought I'd mention
here just in case there's something more I should do.
--
Randy Barlow
xmpp: bowlofe...@electronsweatshop.com
irc: bowlofeggs on Freenode
s/ejabberd rbarlow DENIED
by fallthru
remote: error: hook declined to update refs/heads/rbarlow-16.01
Is there a way for me to remove this branch, or is it going to be there
permanently?
--
Randy Barlow
xmpp: bowlofe...@electronsweatshop.com
irc: bowlofeggs on Freenode
signature.asc
D
301 - 400 of 419 matches
Mail list logo
