earner and a contributor for a while now.
>
> Coming to open-source contributions, I have contributed to the Debian
> community
> for Debian packaging for ruby gems mostly, as well as, have a keen interest in
> python language, did some doc fixes(newbie). I like to write mostly technic
community for Debian packaging for ruby gems mostly, as well as, have a
keen interest in python language, did some doc fixes(newbie). I like to
write mostly technical, you can find my blogs at
https://samyak-jn.github.io/.
It would be great if someone can mentor me with it, I would love to
contribute
On 2019-07-29, Ankur Sinha wrote:
> In the meantime, this was filed:
> https://bugzilla.redhat.com/show_bug.cgi?id=3D1732531
>
> "On Fedora Rawhide, the nest module does not have the default profile(s)
> set. Therefore, DNF will not install the module using `dnf module
> install librealsense`. It
Hi Petr,
Thanks very much for the detailed reply. The process is a lot clearer to
me now.
On Mon, Jul 22, 2019 11:24:49 -, Petr Pisar wrote:
> On 2019-07-20, Ankur Sinha wrote:
>
>
> > 3. And finally: version 2.18.0 is already available in the repos (the
> > platform?). So, did I mess up b
On 2019-07-20, Ankur Sinha wrote:
> 1. Why did that create 4 module build jobs for each stream?
>
> (ins)[asinha@ankur-pc nest(2.18.0=3D)]$ fedpkg module-build
> Submitting the module build...
> The builds 5109, 5110, 5111 and 5112 were submitted to the MBS
> Build URLs:
> https://mbs.fedoraproje
Hello,
I finally got around to modules. I wanted to provide users with two
versions of NEST: 2.16.0 and 2.18.0. So, I:
- requested branches for 2.18.0 and 2.16.0 in dist/git:
https://src.fedoraproject.org/rpms/nest/branches?branchname=master
- requested a new module and two branches (streams?)
On 10/25/2016 01:48 AM, Adam Williamson wrote:
> On Sat, 2016-10-22 at 22:08 -0600, William Moreno wrote:
>> By default koji will not let build a package of there is a previus buid
>> with the same NVR in the same branch, you can build many times the same NVR
>> in diferent branches, (fedpkg switc
On Sat, 2016-10-22 at 22:08 -0600, William Moreno wrote:
> > 3. What does the "e" stand for in n-v-r-e ?
>
> The E comer for the epoch rmp tag, this overrides the release and version
> tags
Note, this is conventionally given as NEVR (not NVRE), because that's
the logical order: the epoch is more
On Sat, 2016-10-22 at 22:08 -0600, William Moreno wrote:
> By default koji will not let build a package of there is a previus buid
> with the same NVR in the same branch, you can build many times the same NVR
> in diferent branches, (fedpkg switch-branch)
Well, no, because it won't be the same re
ge for outages within the Fedora infrastructure?
> >>
> >> Try fedpkg local to trigger a local build, source files must be
> uploaded by fedpkg new-sources path/to/tarball.tgz
> >>
> >> The source0 file it is not espected to.be in the package repo, patches
>
er a local build, source files must be
uploaded by fedpkg new-sources path/to/tarball.tgz
>>
>> The source0 file it is not espected to.be in the package repo, patches
and others soureces can be in the repo
>
>
> These sources are definitely in the repo, and the build works fine
in the repo
>
These sources are definitely in the repo, and the build works fine locally.
The error is from a missing patch (not Source0), and this patch is not new
and has not changed since the last successful build. Everything works
locally with both mockbuild and local. I'm pr
El 22/10/2016 9:51 p. m., "Christopher"
escribió:
>
> I should probably know the answers to these by now, but...
>
> 1. If I trigger more than one build for the same NVR in Koji, which one
will get tagged, and when? Which one will Bodhi use when I create an update?
By default koji will not let bu
I should probably know the answers to these by now, but...
1. If I trigger more than one build for the same NVR in Koji, which one
will get tagged, and when? Which one will Bodhi use when I create an update?
2. Should I preserve the entire changelog in the SPEC? Or should I roll it
over when I up
Thanks
On Tue, Aug 18, 2015 at 2:15 PM Orion Poplawski wrote:
> On 08/18/2015 11:12 AM, Nicolas Pio wrote:
> > Hello everyone,
> >
> > I wanted contribute with Fedora and wanted a help yours.
> > Where do I begin?
> >
> >
>
> LMGTFY -
> https://www.google.com/search?q=fedora+contribute&ie=utf-8
On 08/18/2015 11:12 AM, Nicolas Pio wrote:
> Hello everyone,
>
> I wanted contribute with Fedora and wanted a help yours.
> Where do I begin?
>
>
LMGTFY - https://www.google.com/search?q=fedora+contribute&ie=utf-8&oe=utf-8
--
Orion Poplawski
Technical Manager 303-415-9701
Hello everyone,
I wanted contribute with Fedora and wanted a help yours.
Where do I begin?
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
17 matches
Mail list logo