Hey Fabio,
On 11/06/2021 15.38, Fabio Valentini wrote:
On Fri, Jun 11, 2021 at 6:28 AM Fabio M. Di Nitto wrote:
Hey everyone,
I have been reading the current guideline here:
https://docs.fedoraproject.org/en-US/packaging-guidelines/Rust/
and for the most it´s pretty clear when packaging
On 11/06/2021 12.23, Richard W.M. Jones wrote:
On Fri, Jun 11, 2021 at 06:27:19AM +0200, Fabio M. Di Nitto wrote:
Hey everyone,
I have been reading the current guideline here:
https://docs.fedoraproject.org/en-US/packaging-guidelines/Rust/
and for the most it´s pretty clear when packaging
On 11/06/2021 07.57, Robert-André Mauchin wrote:
On 6/11/21 6:27 AM, Fabio M. Di Nitto wrote:
Hey everyone,
I have been reading the current guideline here:
https://docs.fedoraproject.org/en-US/packaging-guidelines/Rust/
and for the most it´s pretty clear when packaging a standalone crate
Hey everyone,
I have been reading the current guideline here:
https://docs.fedoraproject.org/en-US/packaging-guidelines/Rust/
and for the most it´s pretty clear when packaging a standalone crate /
rust generated binaries (given this is my very first step into
understanding rust).
I am
On 02/11/2020 12.27, Miro Hrončok wrote:
On 11/2/20 12:13 PM, Fabio M. Di Nitto wrote:
On 02/11/2020 12.03, 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
On 02/11/2020 12.03, 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:
Hi all,
with one of the latest updates of corosync, we had to break some
API/ABI. All packages have been rebuilt and they are waiting for updates
to be available.
I also re-built sheepdog
(http://koji.fedoraproject.org/koji/buildinfo?buildID=310076)
but i don´t have super powers to push the
On 4/4/2012 12:23 PM, Michael Schwendt wrote:
On Wed, 04 Apr 2012 09:23:16 +0200, FMDN (Fabio) wrote:
Hi all,
with one of the latest updates of corosync, we had to break some
API/ABI. All packages have been rebuilt and they are waiting for updates
to be available.
I also re-built
On 4/4/2012 1:36 PM, Daniel P. Berrange wrote:
On Wed, Apr 04, 2012 at 12:23:17PM +0200, Michael Schwendt wrote:
On Wed, 04 Apr 2012 09:23:16 +0200, FMDN (Fabio) wrote:
Hi all,
with one of the latest updates of corosync, we had to break some
API/ABI. All packages have been rebuilt and they
On 4/4/2012 2:24 PM, Daniel P. Berrange wrote:
On Wed, Apr 04, 2012 at 02:09:07PM +0200, Fabio M. Di Nitto wrote:
On 4/4/2012 1:36 PM, Daniel P. Berrange wrote:
On Wed, Apr 04, 2012 at 12:23:17PM +0200, Michael Schwendt wrote:
On Wed, 04 Apr 2012 09:23:16 +0200, FMDN (Fabio) wrote:
Hi all
On 4/4/2012 2:24 PM, Daniel P. Berrange wrote:
On Wed, Apr 04, 2012 at 02:09:07PM +0200, Fabio M. Di Nitto wrote:
On 4/4/2012 1:36 PM, Daniel P. Berrange wrote:
On Wed, Apr 04, 2012 at 12:23:17PM +0200, Michael Schwendt wrote:
On Wed, 04 Apr 2012 09:23:16 +0200, FMDN (Fabio) wrote:
Hi all
On 4/4/2012 6:17 PM, Michael Schwendt wrote:
On Wed, 04 Apr 2012 13:32:39 +0200, FMDN (Fabio) wrote:
Sheepdog update can be done in a separate update. If provenpackager can
make a ticket that would suffice. I don´t/didn´t test sheepdog.
On 3/18/2011 6:39 PM, Michel Alexandre Salim wrote:
Greetings,
LLVM 2.9 is scheduled to be released on April 3rd, and is currently in
the first of hopefully two testing periods (http://llvm.org/)
I'm not sure if we should be pushing this for F-15 -- the first test
release was not ready
On 12/03/2010 05:20 PM, James Antill wrote:
On Fri, 2010-12-03 at 10:24 +0100, Fabio M. Di Nitto wrote:
Hi all,
I am seeking some help here to solve a possible $subject. I have been
trying to find a simple alternate solution, but I just can´t see it or
it´s not obvious to me
Hi all,
I am seeking some help here to solve a possible $subject. I have been
trying to find a simple alternate solution, but I just can´t see it or
it´s not obvious to me.
This is the situation:
srpm foo 1.0 ships 2 rpm´s bar and baz. bar has a daemon inside.
due to upstream split:
srpm foo
15 matches
Mail list logo
