On Friday, June 16, 2017 12:23:58 AM CEST Jason L Tibbitts III wrote:
> > "PR" == Pavel Raiskup writes:
>
> PR> But I would be OK with this solution - if this idea was baked into
> PR> guidelines first. Is it realistic to ratify new guidelines
> PR> paragraph for this issue before F26?
>
>
On 2017-06-13, Petr Pisar wrote:
> On 2017-06-13, Pavel Raiskup wrote:
>>> vim-syntastic praiskup 38
>>> weeks ago
>>
>> Please don't remove this set of vim-syntastic* packages, there's
>> nothing to do about this. Once we have fixed release engineering
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hello everybody,
on behalf of Rust SIG[0] I'm happy to announce that recently we
migrated our package builds to COPR repository[1] and would like to ask
you which tool(s) you would like to see there (obviously, those should
be written in Rust).
So
> On 16. Jun 2017, at 12:49, Igor Gnatenko
> wrote:
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Hello everybody,
>
> on behalf of Rust SIG[0] I'm happy to announce that recently we
> migrated our package builds to COPR repository[1] and would like to ask
> you which tool(s) you
On 06/15/2017 08:13 PM, Dominik 'Rathann' Mierzejewski wrote:
> On Thursday, 15 June 2017 at 20:05, Stephen Gallagher wrote:
>> On 06/15/2017 02:02 PM, Tom Hughes wrote:
>>> On 15/06/17 18:27, Stephen Gallagher wrote:
>>>
I think you may misunderstand what "Recommends" means. At install-time,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Fri, 2017-06-16 at 02:13 +0200, Dominik 'Rathann' Mierzejewski
wrote:
> On Thursday, 15 June 2017 at 20:05, Stephen Gallagher wrote:
> > On 06/15/2017 02:02 PM, Tom Hughes wrote:
> > > On 15/06/17 18:27, Stephen Gallagher wrote:
> > >
> > > > I t
Hi guys, I hope you don't mind me posting this to devel.
So I built nodejs module today (Friday) [1], went over to taskotron interface
to see if tests were executed [2]. Unfortunately, the tests [3] we have present
in the module dist-git were not triggered. Why?
It would be awesome if I could exe
Quoting Igor Gnatenko (2017-06-16 12:49:21)
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Hello everybody,
>
> on behalf of Rust SIG[0] I'm happy to announce that recently we
> migrated our package builds to COPR repository[1] and would like to ask
> you which tool(s) you would like to
2017-06-13 13:54 GMT+02:00 Roman Pavelka :
> > It does not inspire confidence that the person(s) proposing this Change
> understand the potential fallout.
> ...
> > what packages in Fedora parse the rsyslog output and make sure that they
> are capable of handling the change.
>
> Everyone is free
> I think it’s the responsibility of the proponents of the change to come up
> with a plan; the Change process was pretty much instituted exactly so that
> there actually *is* *some* plan for seeing through breaking changes.
Agreed, the proponents of the change must identify areas (packages)
which
I would like to see some details on how this is going to be
implemented.
It all seem very vague and handwavy
El jue, 08-06-2017 a las 15:55 +0200, Jan Kurik escribió:
> = Proposed Self Contained Change: Decouple system java setting from
> java command setting =
> https://fedoraproject.org/wiki/Ch
On 16/06/17 12:49, Igor Gnatenko wrote:
> Hello everybody,
>
> on behalf of Rust SIG[0] I'm happy to announce that recently we
> migrated our package builds to COPR repository[1] and would like to ask
> you which tool(s) you would like to see there (obviously, those should
> be written in Rust).
>
On Mon, Jun 12, 2017 at 6:38 PM, wrote:
> asterisk jsmith, gtjoseph, itamarjp,83 weeks ago
>lbazan, russellb
>
>
I'm actively working on fixing up Asterisk -- it took a while to get
systemd support back into dahdi-tools and get it unorphan
On 06/16/2017 11:31 AM, K. Cong wrote:
> What about rustup? I feel it's quite important for anyone working in Rust.
I think rustup is great for managing rustc versions, and I do use it
myself, but I don't think it's a good fit for system packaging. It
wants to be interposed in your PATH with shim
Missing expected images:
Workstation live i386
Kde live x86_64
Workstation live x86_64
Kde live i386
Failed openQA tests: 5/102 (x86_64), 1/22 (i386), 1/2 (arm)
ID: 109096 Test: x86_64 Server-dvd-iso server_realmd_join_kickstart
URL: https://openqa.fedoraproject.org/tests/109096
ID: 109116
I took a shot at packaging the game and it went rather smoothly. The only issue
I have is that the level packs don't really have a licence; the only copyright
info is a line at the end of the readme, stating: "This package [...] may be
distributed freely, as long as its contents are left intact
On Thu, Jun 15, 2017 at 5:23 PM, Adam Miller
wrote:
> 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 r
On Fri, Jun 16, 2017 at 03:35:46PM +0200, Igor Gnatenko wrote:
> > > > What does "Recommends" do on upgrade?
> > > >
> > > > In other words if Recommends was used and a new perl version had
> > > > new modules in
> > > > the core package would an upgrade of perl pull them in as you
> > > > would e
Am 16.06.2017 um 22:52 schrieb Artur Iwicki:
I took a shot at packaging the game and it went rather smoothly. The only issue I have is
that the level packs don't really have a licence; the only copyright info is a line at
the end of the readme, stating: "This package [...] may be distributed fr
19 matches
Mail list logo
