Just FTR, there is attachment with logs. I have not noticed it on the
first look, but Leigh did :)
Vít
Dne 07. 01. 24 v 1:41 Alexander Ploumistos napsal(a):
Hello Patrick,
What was the command you issued? Were there any errors before the
excerpt you've posted? Does your user belong t
> Try adding 'BuildRequires: gcc-c++' to the specfile
>
> checking for x86_64-redhat-linux-gcc... gcc
> checking whether the C compiler works... no
> configure: error: in `/builddir/build/BUILD/hello-2.10':
> configure: error: C compiler cannot create execut
Try adding 'BuildRequires: gcc-c++' to the specfile
checking for x86_64-redhat-linux-gcc... gcc
checking whether the C compiler works... no
configure: error: in `/builddir/build/BUILD/hello-2.10':
configure: error: C compiler cannot create executables
See `config.log&#x
Hello Patrick,
What was the command you issued? Were there any errors before the
excerpt you've posted? Does your user belong to the 'mock' group?
Best regards,
A.
--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscrib
Hello,
I plan to unretire the GNU hello package.
(Apparently it was retired in 2012 just because the former
maintainer didn't want to add "Provides: bundled(gnulib)".)
Though it is fairly trivial it is a minimal system sanity package and
executable tool,
with gettext international
On Fri, Mar 23, 2018 at 7:24 AM, Michal Novotny wrote:
> On Tue, Mar 20, 2018 at 3:31 PM, Jan Kaluza wrote:
>> On Tue, Mar 20, 2018 at 10:06 AM, Michal Novotny wrote:
>>>
>>> The question here is why don't we actually implement the modularity
>>> the simple way.
>>>
>>> Let's suppose I would lik
On Tue, Mar 20, 2018 at 3:31 PM, Jan Kaluza wrote:
> On Tue, Mar 20, 2018 at 10:06 AM, Michal Novotny wrote:
>>
>> The question here is why don't we actually implement the modularity
>> the simple way.
>>
>> Let's suppose I would like to make nodejs-8 available in EPEL7.
>>
>> The most effortless
On Tue, Mar 20, 2018 at 3:18 PM, Kamil Paral wrote:
> On Mon, Mar 19, 2018 at 8:08 PM, Jan Kaluza wrote:
>
>> Your tool can use good old buildsys.build.state.change fedmsg with the
>> well known name/version/release fields like this:
>>
>> https://apps.stg.fedoraproject.org/datagrepper/raw?topic
On Tue, Mar 20, 2018 at 10:06 AM, Michal Novotny wrote:
> The question here is why don't we actually implement the modularity
> the simple way.
>
> Let's suppose I would like to make nodejs-8 available in EPEL7.
>
> The most effortless way would be to create subdirectory called 8 at
> src.fedorap
On Mon, Mar 19, 2018 at 8:08 PM, Jan Kaluza wrote:
> Your tool can use good old buildsys.build.state.change fedmsg with the
> well known name/version/release fields like this:
>
> https://apps.stg.fedoraproject.org/datagrepper/
> raw?topic=org.fedoraproject.stg.buildsys.build.state.change
>
Init
The question here is why don't we actually implement the modularity
the simple way.
Let's suppose I would like to make nodejs-8 available in EPEL7.
The most effortless way would be to create subdirectory called 8 at
src.fedoraproject.org/rpms/nodejs
with the updated spec file and sources for the
On Mon, Mar 19, 2018 at 4:43 PM, Adam Williamson wrote:
> On Mon, 2018-03-19 at 10:58 +0100, Stanislav Ochotnicky wrote:
> > On Mon 19 Mar 2018 09:38:58 AM GMT Fabio Valentini wrote:
> > > So you think having to send a request to a web service instead of just
> > > parsing a string locally with o
On Mon, 2018-03-19 at 17:18 +0100, Nils Philippsen wrote:
> On Mon, 2018-03-19 at 08:43 -0700, Adam Williamson wrote:
> > What if I just want to write a tool that parses fedmsgs about module
> > builds in Koji and does something that depends on module names,
> > streams
> > and versions? (e.g. some
On Mon, 2018-03-19 at 08:43 -0700, Adam Williamson wrote:
> What if I just want to write a tool that parses fedmsgs about module
> builds in Koji and does something that depends on module names,
> streams
> and versions? (e.g. some sort of changelog thing)
I haven't looked at actual fedmsgs lately
On Mon, 2018-03-19 at 10:58 +0100, Stanislav Ochotnicky wrote:
> On Mon 19 Mar 2018 09:38:58 AM GMT Fabio Valentini wrote:
> > So you think having to send a request to a web service instead of just
> > parsing a string locally with one line of code is a good trade-off for
> > allowing dashes?
>
>
On Mon, 2018-03-19 at 09:27 +0100, Petr Šabata wrote:
> This, AFAIK, only affects what you see in some parts of the
> build and update system (and on the bus).
That's a very important parenthesis, as we as a project do a lot of
work with fedmsg messages.
--
Adam Williamson
Fedora QA Community Mon
On Mon, Mar 19, 2018 at 10:10:23AM +0100, Jan Kaluza wrote:
>If something does not support modules and it should support modules and
>*needs* to work with Koji content-generator imported builds for some
>reason, it needs to updated to support modules and as part of this update,
>it
On Mon 19 Mar 2018 09:38:58 AM GMT Fabio Valentini wrote:
> So you think having to send a request to a web service instead of just
> parsing a string locally with one line of code is a good trade-off for
> allowing dashes?
This has been mentioned several times in this thread and I think there's
a
On Mon, Mar 19, 2018, 10:20 Petr Šabata wrote:
> On Mon, Mar 19, 2018 at 08:57:08AM +, Zbigniew Jędrzejewski-Szmek
> wrote:
> > On Mon, Mar 19, 2018 at 09:27:30AM +0100, Petr Šabata wrote:
> > > On Sun, Mar 18, 2018 at 07:09:23PM +, Zbigniew Jędrzejewski-Szmek
> wrote:
> > > > On Fri, Mar
On Mon, Mar 19, 2018 at 08:57:08AM +, Zbigniew Jędrzejewski-Szmek wrote:
> On Mon, Mar 19, 2018 at 09:27:30AM +0100, Petr Šabata wrote:
> > On Sun, Mar 18, 2018 at 07:09:23PM +, Zbigniew Jędrzejewski-Szmek wrote:
> > > On Fri, Mar 16, 2018 at 04:14:27PM -0400, Randy Barlow wrote:
> > > > On
On Sat, Mar 17, 2018 at 4:15 PM, Patrick マルタインアンドレアス Uiterwijk <
puiterw...@redhat.com> wrote:
> > Don't be afraid of koji. :)
>
> I couldn't agree more, Koji's a pretty nice project to work on.
> It might seems scary for newcomers because of all the ingrained knowledge
> and assumptions, but once
On Mon, Mar 19, 2018 at 09:27:30AM +0100, Petr Šabata wrote:
> On Sun, Mar 18, 2018 at 07:09:23PM +, Zbigniew Jędrzejewski-Szmek wrote:
> > On Fri, Mar 16, 2018 at 04:14:27PM -0400, Randy Barlow wrote:
> > > On 03/16/2018 04:04 PM, Dennis Gregorovic wrote:
> > > > modules are not RPMs. I would
(a repost from the infra list)
Please note that modules (and therefore module builds) may reference to
multiple RPM builds. Also, the module name doesn't need to match any RPM
name. Therefore getting package names from the module build name would not
be possible anyway.
As an exapmple, see the
On Sun, Mar 18, 2018 at 07:09:23PM +, Zbigniew Jędrzejewski-Szmek wrote:
> On Fri, Mar 16, 2018 at 04:14:27PM -0400, Randy Barlow wrote:
> > On 03/16/2018 04:04 PM, Dennis Gregorovic wrote:
> > > modules are not RPMs. I would not expect them to necessarily use the
> > > same format as RPMs. I
On Fri, Mar 16, 2018 at 04:14:27PM -0400, Randy Barlow wrote:
> On 03/16/2018 04:04 PM, Dennis Gregorovic wrote:
> > modules are not RPMs. I would not expect them to necessarily use the
> > same format as RPMs. If we take koji out of the equation, we have
> > module builds in N:S:V:C format and m
On Sat, 2018-03-17 at 15:15 +, Patrick マルタインアンドレアス Uiterwijk
wrote:
> > Don't be afraid of koji. :)
>
> I couldn't agree more, Koji's a pretty nice project to work on.
> It might seems scary for newcomers because of all the ingrained
> knowledge and assumptions, but once you get close the co
> Don't be afraid of koji. :)
I couldn't agree more, Koji's a pretty nice project to work on.
It might seems scary for newcomers because of all the ingrained knowledge and
assumptions, but once you get close the community is nice and friendly :).
>
> It is under active development. Of course,
El vie, 16-03-2018 a las 15:19 -0700, Adam Williamson escribió:
> On Fri, 2018-03-16 at 16:04 -0400, Dennis Gregorovic wrote:
> > modules are not RPMs. I would not expect them to necessarily use
> > the same
> > format as RPMs. If we take koji out of the equation,
>
> That's an extremely big and
Don't be afraid of koji. :)
It is under active development. Of course, resources are limited and not
everything can be taken on, but it's worth having the discussion. I have
filed https://pagure.io/koji/issue/851 as a strawman and will try to
solicit feedback on the idea.
Patrick, if https://pa
On Fri, 2018-03-16 at 16:14 -0400, Randy Barlow wrote:
>
> > If that means
> > tweaking the Koji UI we can look into that.
>
> For my concerns, it would be more helpful to tweak the Koji API than the
> UI, so that tools that interact with Koji (like Bodhi) don't have to
> know that Modules are di
On Fri, 2018-03-16 at 16:04 -0400, Dennis Gregorovic wrote:
> modules are not RPMs. I would not expect them to necessarily use the same
> format as RPMs. If we take koji out of the equation,
That's an extremely big and invalid 'if', though.
--
Adam Williamson
Fedora QA Community Monkey
IRC: ada
On Fri, Mar 16, 2018 at 4:04 PM, Dennis Gregorovic
wrote:
> The challenge here is that those module builds are squeezed into a N-V-R
> format when imported into Koji. The N-V-R format is used for all build
> types in Koji and it works well for its purpose, but it's also not
> realistic to expect
On 03/16/2018 04:04 PM, Dennis Gregorovic wrote:
> modules are not RPMs. I would not expect them to necessarily use the
> same format as RPMs. If we take koji out of the equation, we have
> module builds in N:S:V:C format and module RPMs in N-V-R.A format. They
> use different separators, but bo
modules are not RPMs. I would not expect them to necessarily use the same
format as RPMs. If we take koji out of the equation, we have module builds
in N:S:V:C format and module RPMs in N-V-R.A format. They use different
separators, but both can be parsed consistently.
The challenge here is tha
On 03/16/2018 05:18 AM, Pierre-Yves Chibon wrote:
> I wonder what we can do about this. Is it FESCo material?
> Can the folks working on modularity comment more on this?
I am considering filing it for FESCo to consider. I haven't seen a
compelling explanation for why modules are using a different
On Thu, Mar 15, 2018 at 05:47:41PM -0700, Adam Williamson wrote:
> So: there would be no problem with - in the *name* of the modules, so
> long as that's the first field, which apparently it is.
>
> The problem is if you allow the delimiter in *both* the first and last
> fields, or in *any other f
Randy Barlow wrote:
> It sounds like this breaks a great deal of tooling. Can we reconsider
> switching away from - separators in modules? Is allowing streams to have
> -'s in them important enough to break so many tools?
+1, I think allowing this ambiguity is a very bad idea.
Kevin Kofle
On Thu, 2018-03-15 at 19:57 -0400, langdon wrote:
> On 03/15/2018 04:31 PM, Simo Sorce wrote:
> > On Thu, 2018-03-15 at 14:06 -0400, Randy Barlow wrote:
> > > On 03/15/2018 12:28 PM, Chuck Anderson wrote:
> > > > : doesn't work very well in filenames due to it being a pathname
> > > > separator in
On 03/15/2018 04:31 PM, Simo Sorce wrote:
On Thu, 2018-03-15 at 14:06 -0400, Randy Barlow wrote:
On 03/15/2018 12:28 PM, Chuck Anderson wrote:
: doesn't work very well in filenames due to it being a pathname separator in
some filesystems among other things.
It sounds like this breaks a great
On Thu, 2018-03-15 at 14:06 -0400, Randy Barlow wrote:
> On 03/15/2018 12:28 PM, Chuck Anderson wrote:
> > : doesn't work very well in filenames due to it being a pathname separator
> > in some filesystems among other things.
>
> It sounds like this breaks a great deal of tooling. Can we reconsid
On 03/15/2018 12:28 PM, Chuck Anderson wrote:
> : doesn't work very well in filenames due to it being a pathname separator in
> some filesystems among other things.
It sounds like this breaks a great deal of tooling. Can we reconsider
switching away from - separators in modules? Is allowing strea
On Thu, Mar 15, 2018 at 04:19:46PM +, Daniel P. Berrangé wrote:
> On Thu, Mar 15, 2018 at 04:14:34PM +0100, Patrick Uiterwijk wrote:
> > For user consumption, they are Name:Stream:Version:Context, so you may
> > need to manually convert between one representation and the other if
> > you need t
On Thu, 2018-03-15 at 16:14 +0100, Patrick Uiterwijk wrote:
> One of the interesting things they wanted to also allow: dashes in streams.
> As a consequence, when you get an N-S-V.C as modules are represented
> in Koji builds, doing a .rsplit('-', 2) will not give you Name,
> Stream, Version.Contex
On Thu, Mar 15, 2018 at 04:14:34PM +0100, Patrick Uiterwijk wrote:
> Hi all,
>
> If you maintain any application in Fedora Infra (or outside) that
> tries to parse things out of RPM names, you might be interested in
> this.
>
> For those wondering where I've been spending most of my time the last
> On 15/03/18 15:30, Patrick Uiterwijk wrote:
>
> Well currently at any rate? What's the long term story?
>
> Only when some module rpms accidentally leaked into rawhide
> recently they definitely had the kind of rather unhelpful names
> that you described in your post and I got the impression at
On Thu, Mar 15, 2018 at 11:14 AM, Patrick Uiterwijk
wrote:
> Hi all,
>
> If you maintain any application in Fedora Infra (or outside) that
> tries to parse things out of RPM names, you might be interested in
> this.
>
> For those wondering where I've been spending most of my time the last
> few we
On 15/03/18 15:30, Patrick Uiterwijk wrote:
This does not affect traditional RPM/SRPM packages, right?
Correct, this only impacts modules.
Well currently at any rate? What's the long term story?
Only when some module rpms accidentally leaked into rawhide
recently they definitely had the ki
>
>
> This does not affect traditional RPM/SRPM packages, right?
Correct, this only impacts modules.
>
> Thanks,
> -Mat
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
___
On 03/15/2018 10:14 AM, Patrick Uiterwijk wrote:
Hi all,
If you maintain any application in Fedora Infra (or outside) that
tries to parse things out of RPM names, you might be interested in
this.
For those wondering where I've been spending most of my time the last
few weeks: I've been deep in
Hi all,
If you maintain any application in Fedora Infra (or outside) that
tries to parse things out of RPM names, you might be interested in
this.
For those wondering where I've been spending most of my time the last
few weeks: I've been deep in the internals of Bodhi fixing all kinds
of issues I
Hello to everyone, my name is Carlos i'm from Chile and I've fedora
collaborator in QA since F20. but now i want collaborate as maintainer
package. well I've create my first review request. it's a library for
shortening of URL page.
https://bugzilla.redhat.com/show_bug.cgi
On Mon, 30 Sep 2013 10:35:33 +0300, Oron Peled wrote:
>
> On Sunday 29 September 2013 21:22:24 Lars Kellogg-Stedman wrote:
> > I went ahead and generated a patch to the Makefile that uses the
> > package version for the library version.
>
> That's wrong, as library versions represent API/ABI cha
On Sun, 29 Sep 2013 12:38:25 -0400, Lars Kellogg-Stedman wrote:
> [...] what the upstream Makefile
> currently produces. I wasn't sure how invasive I should be in terms
> of patching the upstream build process.
The build output is "silent" using '@' command invocations in the Makefile.
Patching
On Sunday 29 September 2013 21:22:24 Lars Kellogg-Stedman wrote:
> I went ahead and generated a patch to the Makefile that uses the
> package version for the library version.
That's wrong, as library versions represent API/ABI changes and
the numbering has different *semantics* than package versi
On Sun, Sep 29, 2013 at 12:38:25PM -0400, Lars Kellogg-Stedman wrote:
> On Sun, Sep 29, 2013 at 06:14:30PM +0200, Michael Schwendt wrote:
> > A version-less library is less than ideal, however. How stable is the
> > API/ABI?
>
> Yeah, that's my feeling, too, but that's what the upstream Makefile
On Sun, Sep 29, 2013 at 06:14:30PM +0200, Michael Schwendt wrote:
> Doesn't look too bad ;) judging based on very brief look at the spec file,
> but it violates the Static Library Packaging Guidelines, and I wonder
> who "owns" %{_datadir}/re?
I've removed the static library and made the package a
On Sun, 29 Sep 2013 11:59:43 -0400, Lars Kellogg-Stedman wrote:
> Hello everyone,
>
> I've just submitted my first package review request to Fedora
> (https://bugzilla.redhat.com/show_bug.cgi?id=1013363), which is for
> "libre" (http://www.creytiv.com/re.ht
Hello everyone,
I've just submitted my first package review request to Fedora
(https://bugzilla.redhat.com/show_bug.cgi?id=1013363), which is for
"libre" (http://www.creytiv.com/re.html). This is a dependency for
"baresip" (http://www.creytiv.com/baresip.html), which
Hello,
I am looking for a sponsor.
I am Canadian, I know French, English, and many programming languages. I use
Fedora 17 on
my Lenovo Thinkpad x230 and I have started using Linux in 2003 on a Red Hat 9
installation.
Over the years, I have used: Slackware, Ubuntu, Gentoo, Fedora, CentOS, Mint
On Tue, May 22, 2012 at 02:38:40PM +0300, Назар Міштурак wrote:
> Hello, everyone, my name is Nazar. I have just made my first package review
> request(https://bugzilla.redhat.com/show_bug.cgi?id=823873). The package is
> The Powder Toy game which is very fun. So I want to see it in re
Hello, everyone, my name is Nazar. I have just made my first package review
request(https://bugzilla.redhat.com/show_bug.cgi?id=823873). The package is
The Powder Toy game which is very fun. So I want to see it in repo. It is not
my project, original code is from http://powdertoy.co.uk/
Nazar
Fedora Packagers,
I've been working through the Package Maintainers Join page and one of the
things to do is to send an introduction to the Fedora Devel list, so here it is.
Hi! It's been a while since I've done Open Source Distribution work but I've
gotten into a serious job since then and hav
On 04/02/2012 10:59 AM, Dmitriy Nikolaev wrote:
> Uups... I'm sorry. OK. I got it. THank you once again for your help
> and explanations.
>
> With best regards.
Happy to help. :)
--
Digimer
Papers and Projects: https://alteeve.com
--
devel mailing list
devel@lists.fedoraproject.org
https://adm
Uups... I'm sorry. OK. I got it. THank you once again for your help
and explanations.
With best regards.
On 2 April 2012 20:56, Digimer wrote:
> On 04/02/2012 10:45 AM, Dmitriy Nikolaev wrote:
>> Thank you for your fast answer.
>> That's interesting. But, could you, please, tell me also, if in t
On 04/02/2012 10:45 AM, Dmitriy Nikolaev wrote:
> Thank you for your fast answer.
> That's interesting. But, could you, please, tell me also, if in the
> future, not now, I would like to participate in kernel developing,
> then is it possible to join those guys?
Please reply to the mailing list. T
On 04/02/2012 10:34 AM, Dmitriy Nikolaev wrote:
> Hello , guys!
>
> I would like to participate in developing Fedora releases(coding,
> mostly in C/C++). Could you tell me, where I can find a source code
> and other relative things, for instance, headers and libraries
> descri
Hello , guys!
I would like to participate in developing Fedora releases(coding,
mostly in C/C++). Could you tell me, where I can find a source code
and other relative things, for instance, headers and libraries
descriptions?
Thank you beforehand for your answers.
With best regards.
--
devel
On Tue, 2011-11-29 at 12:32 +0545, Dipesh Acharya wrote:
> view again?
>
> Thank you :)
>
> Dipesh Acharya http://motorscript.com
> http://twitter.com/xtranophilist
>
Ah! No. Not required :)
--
Thanks,
Regards,
Ankur: "FranciscoD"
http://fedoraproject.org/wiki/User:Ankursinha
http://dodoin
t; > http://twitter.com/xtranophilist
> >
> > I don't think this makes sense - your extension is already included in
> > Fedora.
> > But you can apply for comaintainer
> > http://fedoraproject.org/wiki/Package_maintainer_policy#Co-Maintainership
> > . Or you can
>
> >
> > On Tue, Nov 29, 2011 at 6:38 AM, Ankur Sinha
> wrote:
> > > On Tue, 2011-11-29 at 01:58 +0545, Dipesh Acharya wrote:
> > > > Hello, this is Dipesh Acharya.
> > > >
> > > > I will be packaging and updating gnome-shell-extension-
r you can work on another application.
Greg
>
> On Tue, Nov 29, 2011 at 6:38 AM, Ankur Sinha wrote:
> > On Tue, 2011-11-29 at 01:58 +0545, Dipesh Acharya wrote:
> > > Hello, this is Dipesh Acharya.
> > >
> > > I will be packaging and updating gnom
:38 AM, Ankur Sinha wrote:
> On Tue, 2011-11-29 at 01:58 +0545, Dipesh Acharya wrote:
> >
> > Hello, this is Dipesh Acharya.
> >
> > I will be packaging and updating gnome-shell-extension-cpu-
> > temperature since I develop it.
> >
> > Thank you :)
>
On Tue, 2011-11-29 at 01:58 +0545, Dipesh Acharya wrote:
>
> Hello, this is Dipesh Acharya.
>
> I will be packaging and updating gnome-shell-extension-cpu-
> temperature since I develop it.
>
> Thank you :)
> Dipesh Acharya http://motorscript.com
> http://twitter
Hello, this is Dipesh Acharya.
I will be packaging and updating gnome-shell-extension-cpu-
temperature since I develop it.
Thank you :)
Dipesh Acharya
http://motorscript.com
http://twitter.com/xtranophilist
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org
74 matches
Mail list logo
