ot;Invalid Format" has just been introduced,
> which covers that.
Cool, that's probably work of Oliver Falk :).
>
> --
>
> Michal Schorm
> Software Engineer
> Core Services - Databases Team
> Red Hat
>
> --
>
> On Tue, Mar 5, 2019 at 5:41 AM Michal Novotn
On Mon, Mar 4, 2019 at 4:26 PM Michal Schorm wrote:
>
> Any idea how to use it?
>
> The: https://src.fedoraproject.org/settings#nav-basic-tab
> has an option to change the avatar.
> That will redirect me to: https://www.libravatar.org/account/login/
>
> I have an image uploaded in: https://www.lib
On Thu, Feb 21, 2019 at 2:46 PM Tom Hughes wrote:
>
> On 21/02/2019 13:41, Michal Novotny wrote:
>
> > I am not sure why http://libravatar.org to https://www.libravatar.org
> > redirect is bad. Can you, please, explain?
>
> The reason for saying it should redirect with
On Thu, Feb 21, 2019 at 12:51 PM Till Maas wrote:
>
> On Thu, Feb 21, 2019 at 09:40:16AM +0100, Michal Novotny wrote:
>
> > We, as a libravatar group, are very happy that Fedora Infra provided
> > us with the needed
> > hardware. We will keep the service running by our
On Wed, Feb 20, 2019 at 8:27 PM John Harris wrote:
>
> On Wednesday, February 20, 2019 5:49:13 AM EST Stephen John Smoogen wrote:
> > On Wed, 20 Feb 2019 at 00:07, John Harris wrote:
> >
> > >
> > >
> > > On Tuesday, February 19, 2019 11:46:16 PM
Hello!
maybe you know that around April 2018, there was an announcement that
libravatar service (a service for serving user avatars) is shutting
down:
https://blog.libravatar.org/posts/Libravatar.org_is_shutting_down_on_2018-09-01/
This raised a big wave of interest in the service and in keeping
Hello Petr,
> So, first, I'd like to thank you for taking the time to think
> about this. It's certainly interesting and tries to solve similar
> problems from a completely different angle.
>
> Your proposal focuses on distribution packages rather than on
> independent applications. I'd argue it
Hello Fedora devels!
TL;DR: let's use rpm DistTag (DistTag, not the %dist macro) to denote
stream names
As we all know, modularity was created to provide
parallel-availability, that is providing the same package in its
different major versions from the same rpm repository.
The first question to
On Tue, Nov 20, 2018 at 1:57 PM Michal Novotny wrote:
> On Tue, Nov 20, 2018 at 12:43 PM Tomas Tomecek
> wrote:
>
>> > * Matthew Miller:
>> >
>> >
>> > Make it cheap to maintain branches. I expect that one what to achieve
>> > this w
On Tue, Nov 20, 2018 at 12:43 PM Tomas Tomecek wrote:
> > * Matthew Miller:
> >
> >
> > Make it cheap to maintain branches. I expect that one what to achieve
> > this would be to build directly out of Git, with synthesized release
> > numbers and changelogs. This way, you can apply a lot of fix
only go to VARIANT and VARIANT_ID because it's not a release code name like e.g.
"Beefy Miracle" was for Fedora 17.
We are overusing codename VERSION substring for things that are not codenames
but they are variants and a version.
clime (Michal Novotny)
M.
>
> Pavel
>
>
I cannot take your review right now but i just want to say: Welcome!
Michal
On Thu, Aug 23, 2018 at 10:11 AM Manas Mangaonkar
wrote:
> Hello,
>
> My name is Manas,i am a Computer Engineering student at the University of
> Mumbai.
>
> i recently began packaging with my first package being this
>
Hello,
there have been security problem fixed in copr-frontend today. Basically by
forking, you could get to webhook secrets of an original project being
forked. Also the integration page where you can insert pagure api token was
actually available under certain URL if you knew how this URL should
Hello,
in addition to auto-rebuilding feature from Fedora DistGit (
src.fedoraproject.org), we have added possibility to flag commits and pull
requests after an auto-rebuild. This works not only with Fedora DistGit but
with any pagure instance (e.g. also
https://upstreamfirst.fedorainfracloud.org/
On Thu, Aug 16, 2018 at 11:09 PM Neal Gompa wrote:
> On Thu, Aug 16, 2018 at 5:04 PM Stephen Gallagher
> wrote:
> >
> >
> >
> > On Thu, Aug 16, 2018 at 8:30 AM Michal Novotny wrote:
> >>
> >> On Thu, Aug 16, 2018 at 10:49 AM Zbigniew
On Thu, Aug 16, 2018 at 3:47 PM Miro Hrončok wrote:
> > I was actually thinking about this some time ago. If there's a
> > responsive fedora-review maintainer who can respond to people's
> > questions and complains (because if we start running it for every
> > package build and show it in Bodhi,
On Thu, Aug 16, 2018 at 10:49 AM Zbigniew Jędrzejewski-Szmek <
zbys...@in.waw.pl> wrote:
> f-r currently fails to build (#1603956), it has a bunch of bugs open [1]
> and many issues and unhandled pull requests in the upstream repo [2, 3].
> The last upstream commit was 2 years ago.
>
> f-r has is
On Sat, Aug 11, 2018 at 10:33 AM Miroslav Suchý wrote:
> As part of migration of fedmsg from ZMQ to AMQP, I would like to revisit
> what is Copr sending to fedmsg.
>
> Right now we are sending:
>
> 'build.start': {
> 'what': "build start: user:{user} copr:{copr}" \
>
On Mon, Aug 13, 2018 at 12:52 AM Jeff Johnson wrote:
> Changing Fedora infrastructure to use AMQP brings up a different usage
> case.
>
> Build systems tend to eventually invoke rpmbuild to do the actual build.
>
> Would you like rpmbuild to, say, send time stamped progress messages
> directly th
On Thu, Aug 2, 2018 at 2:07 PM Neal Gompa wrote:
> On Tue, Jul 31, 2018 at 9:59 AM Kamil Paral wrote:
> >
> > Hello devel list,
> >
> > this is a request for comments for a recent proposal I filed at releng
> tracker:
> > https://pagure.io/releng/issue/7445
> >
> > In short, package managers on
On Tue, Jul 31, 2018 at 3:40 PM Michal Novotny wrote:
> On Tue, Jul 31, 2018 at 1:25 PM Jeff Johnson wrote:
>
>> This simply is not true.
>>
>> Whatever "rpm format" means, historically RPM itself has always gone to
>> some lengths not to expose E:
On Tue, Jul 31, 2018 at 1:25 PM Jeff Johnson wrote:
> This simply is not true.
>
> Whatever "rpm format" means, historically RPM itself has always gone to
> some lengths not to expose E: to users to simplify the endless fog of
> dependency hell clutter.
>
Yeah, something which is eluding my unde
Hello,
On Fri, Jul 27, 2018 at 4:56 AM Jens-Ulrik Petersen
wrote:
> On Fri, Jul 27, 2018 at 12:54 AM Jens-Ulrik Petersen
> wrote:
>
>> I should test some larger package sets to see how well rpmbuild-order
>> scales too...
>>
>
> BTW are there any tarballs of all the fedora spec files available
I would like to see dnf history not being messed up by direct installations
with `rpm -i`.
While `dnf history` is a great feature, it would be even greater if the
related functionality
was implemented directly in rpmdb and both rpm and dnf used that db.
Meaning that
any consistency checks would be
On Mon, Jul 23, 2018 at 8:08 PM Chris Murphy
wrote:
> On Thu, Jul 19, 2018 at 10:08 AM, Manas Mangaonkar
> wrote:
> > No offense but can you kindly rephrase whatever you said.Its kinda
> difficult
> > to decipher as your sentences seem to contradict.
>
>
> I need installation instructions to use
On Sun, Jul 22, 2018 at 8:03 PM Kevin Fenzi wrote:
> On 07/20/2018 11:15 PM, Miro Hrončok wrote:
> > On 20.7.2018 19:56, Kevin Fenzi wrote:
> >> On 07/20/2018 03:55 AM, Michal Novotny wrote:
> >>
> >>>
> >>> I actually already filed the respe
On Fri, Jul 20, 2018 at 10:45 AM Kamil Paral wrote:
> On Fri, Jul 20, 2018 at 9:37 AM, Miro Hrončok wrote:
>
>> On 20.7.2018 06:25, Michal Novotny wrote:
>>
>>> Hello,
>>>
>>> I am occasionally experiencing the following error in my day-to-day dn
Hello,
I am occasionally experiencing the following error in my day-to-day dnf use:
Failed to synchronize cache for repo 'fedora'
or
Failed to synchronize cache for repo 'updates'
I've had that happened even in local mock builds.
Do you also experience this error upon dnf operations l
Hello,
lots of times, I see name "copr", "Copr", or "COPR" used somewhere but it's
almost never used correctly for the given context. So I would like to make
it clear, what's the correct way to write it down to get the meaning right.
"Copr" or "COPR" = service providing space for community projec
I can test too.
On Mon, Apr 16, 2018 at 10:19 AM, mohammad luqman
wrote:
> send me the wireframes too.
>
> On 16 April 2018 at 11:59, Clement Verna wrote:
>
>> On 14 April 2018 at 00:08, Abhishek Sharma
>> wrote:
>> > Sent you the invite, Umar. Thanks!
>> >
>> > Will love to see more particip
Hello,
I would like to do rename of rpkg-client (
https://src.fedoraproject.org/rpms/rpkg-client) to rpkg-util and also I
would like to go the package again through a review process because the
spec might deserve some care:
https://bugzilla.redhat.com/show_bug.cgi?id=1563184
Can I possibly swap r
On Sun, Mar 25, 2018 at 7:29 PM, Christopher
wrote:
> On Sun, Mar 25, 2018 at 4:43 AM Michal Novotny wrote:
>
>> On Sun, Mar 25, 2018 at 12:03 AM, Neal Gompa wrote:
>>
>>> On Sat, Mar 24, 2018 at 6:57 PM, Ben Rosser
>>> wrote:
>>> >
>>>
On Sun, Mar 25, 2018 at 12:03 AM, Neal Gompa wrote:
> On Sat, Mar 24, 2018 at 6:57 PM, Ben Rosser wrote:
> >
> > Looking at the dist-git README further reinforces this impression. The
> > first sentence says: "DistGit (Distributed Git) is Git with additional
> > data storage". My initial reactio
On Sun, Mar 25, 2018 at 12:03 AM, Neal Gompa wrote:
> On Sat, Mar 24, 2018 at 6:57 PM, Ben Rosser wrote:
> >
> > Looking at the dist-git README further reinforces this impression. The
> > first sentence says: "DistGit (Distributed Git) is Git with additional
> > data storage". My initial reactio
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
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
especially MariaDB 10.3 and MySQL 8 which are still in
> developement.
I am glad it works. Let me know if you find anything that we can
improve on our side.
clime
>
>
> --
>
> Michal Schorm
> Associate Software Engineer
> Core Services - Databases Team
> Red Hat
>
On Tue, Mar 20, 2018 at 2:54 PM, Miro Hrončok wrote:
> On 20.3.2018 14:33, Michal Novotny wrote:
>>
>> Hello,
>>
>> On Tue, Mar 20, 2018 at 1:55 PM, Miro Hrončok wrote:
>>>
>>> On 27.2.2018 00:04, 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.fedoraproject.org/rpms/nodejs
with the updated spec file and sources for the
Hello Dridi,
On Mon, Mar 19, 2018 at 10:13 AM, Dridi Boukelmoune
wrote:
> Hello list,
>
> Since I work on a project that uses the Coverity Scan free plan for
> open source software it came to my attention today that free scans
> were put on hold and resumed recently because people were abusing it
Hello,
On Wed, Mar 14, 2018 at 1:56 PM, Chenxiong Qi wrote:
> Hi all,
>
> Recently, a fedpkg global option --module-name could confuse some
> packagers easily because word "module" is sort of ambiguous with the
> module introduced by Fedora Modularity. This option is used for
> specifying a repos
Hello,
On Fri, Feb 9, 2018 at 10:57 PM, Michal Novotny wrote:
> Hello,
>
> On Fri, Feb 9, 2018 at 3:22 PM, Panu Matilainen
> wrote:
>
>> On 02/09/2018 03:34 PM, Josh Boyer wrote:
>>
>>> On Thu, Feb 8, 2018 at 1:32 PM, Matthew Miller
>>> wrote:
>
Hello,
the fedora-28-ppc64le chroot was no working up until now due to lack of
compose. This was resolved however in issue.
https://pagure.io/releng/issue/7357
clime
___
devel-announce mailing list -- devel-annou...@lists.fedoraproject.org
To unsubscrib
Hello,
you can now very easily setup auto-rebuilds for your src.fp.o package:
1) make a SCM package in COPR with Clone URL pointing to the src.fp.o fork
(please, use the https:// cloning option)
2) make sure "Webhook Rebuild" checkbox is checked when you are creating
the package
3) Go to settings
On Thu, Feb 15, 2018 at 10:36 AM, Igor Gnatenko <
ignatenkobr...@fedoraproject.org> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> On Thu, 2018-02-15 at 10:17 +0100, Michal Novotny wrote:
> > I feel PRs are better for this sort of stuff. Mainly because peo
I feel PRs are better for this sort of stuff. Mainly because people are
informed why exactly this change is made,
they can read the guidelines and then merge the change when they are sure
they understand it. It helps spreading knowledge
and keeping community involved. Python team did it very well i
On Wed, Feb 14, 2018 at 11:16 AM, Pavel Raiskup wrote:
> On Wednesday, February 14, 2018 10:54:48 AM CET Michal Novotny wrote:
> > Hello Pavel,
> >
> > On Wed, Feb 14, 2018 at 10:18 AM, Pavel Raiskup
> wrote:
> >
> > > On Tuesday, February 13, 20
Hello Pavel,
On Wed, Feb 14, 2018 at 10:18 AM, Pavel Raiskup wrote:
> On Tuesday, February 13, 2018 10:15:42 PM CET Michal Novotny wrote:
> > On Tue, Feb 13, 2018 at 9:51 PM, Michal Novotny
> wrote:
> >
> > > Hello,
> > >
> > > On Tue, Feb 13, 201
On Tue, Feb 13, 2018 at 9:51 PM, Michal Novotny wrote:
> Hello,
>
> On Tue, Feb 13, 2018 at 12:54 PM, Michael Šimáček
> wrote:
>
>> On 2018-02-13 11:47, Pavel Raiskup wrote:
>>
>>> Sorry, I wanted to CC fedora devel before, forwarding.
>>>
>>
Hello,
On Tue, Feb 13, 2018 at 12:54 PM, Michael Šimáček
wrote:
> On 2018-02-13 11:47, Pavel Raiskup wrote:
>
>> Sorry, I wanted to CC fedora devel before, forwarding.
>>
>> Pavel
>>
>> On Tuesday, February 13, 2018 10:54:55 AM CET Pavel Raiskup wrote:
>>
>>> Because we are unable to find a cons
On Tue, Feb 13, 2018 at 5:32 PM, Jason L Tibbitts III
wrote:
> [For those who don't read epel-devel, this is a duplicate of a message
> also posted there.]
>
> The initial set of stub python2-* packages I created have now made their
> way to EPEL6 and EPEL7 stable, so packages can now depend on
>
I must agree with Kevin that taking every single commit message and putting
it into changelog without further tweaking
might just produce lots of redundant and not really desired lines in the
output. But I think something still can be done.
When you invoke `rpkg tag` (the same goes for `fedpkg tag`
Hello,
On Fri, Feb 9, 2018 at 3:22 PM, Panu Matilainen wrote:
> On 02/09/2018 03:34 PM, Josh Boyer wrote:
>
>> On Thu, Feb 8, 2018 at 1:32 PM, Matthew Miller
>> wrote:
>>
>>> On Thu, Feb 08, 2018 at 05:02:10PM +0100, Igor Gnatenko wrote:
>>>
It seems that a lot of people have %file, %check
Hello Richard,
On Sat, Feb 3, 2018 at 3:45 PM, Richard Shaw wrote:
> I would like to manage a COPR via SCM (in this case pagure)
>
> I'm assuming using rpkg would be a good way to do this? Or should I forget
> that and just use plain git+copr-cli?
>
> There is OK documentation for the independen
Planned Outage: COPR BACKEND upgrade - 2018-01-16 09:00 UTC
There will be an outage starting at 2018-01-16 09:00 UTC, which will last
approximately 0.5 hours.
To convert UTC to your local time, take a look at
http://fedoraproject.org/wiki/Infrastructure/UTCHowto or run: date -d
'2018-01-16 09:00
Hello,
I am looking for an alternative for Java logstash application (not in
Fedora) that can parse logs (e.g. httpd access.log) and collect stats about
number of occurrences for a given search pattern (basically it can e.g.
group by IP and give number of lines for each IP and then post it to some
Hello,
we have found out that http://copr.fedoraproject.org was used as default
API endpoint if no copr_url was specified for CoprClient initialization.
This is now fixed in the latest version of python-copr (python-copr-1.84)
and we recommend updating to that version. Also we have decided to revo
Hello,
lately, COPR pending job queues are holding jobs for pretty long time (even
hours). This is a buggy behaviour and we will be doing our best to fix this
issue in the following days.
Thank your for your patience
COPR team
___
devel-announce mailing
We have finished the SCM source type implementation. You can read more in
this blog post: https://clime.github.io/2017/10/24/COPR-SCM.html
Thank you for the feedback!
clime
On Wed, Sep 27, 2017 at 10:28 PM, Michal Novotny wrote:
> Hello,
>
> On Tue, Sep 5, 2017 at 5:50 PM, Petr Stodul
Hello,
On Tue, Sep 5, 2017 at 5:50 PM, Petr Stodulka wrote:
>
>
> On 4.9.2017 19:27, Michal Novotny wrote:
> > I might contact you for more information, but alright, if you feel the
> custom script is more convenient,
> > then I am all for it. But first, I would like to
On Fri, Sep 1, 2017 at 11:20 AM, Gerd Hoffmann wrote:
> Hi,
>
> > It's easier on implementation. That's the main reason. I generally
> > believe that
> > what's easier on implementation is better.
>
> It's maybe easier on the copr side, but not for the copr users ...
>
> If you can modify the u
n (with screenshots and
just complete feature request description) so that users can clearly see
the options and pick what
they like the best. We can work with Pavel on it.
If you agree, I would post the two proposals here before actual
implementation.
>
>
> On 4.9.2017 09:47, Pavel Ra
On Fri, Sep 1, 2017 at 1:41 PM, Gerd Hoffmann wrote:
> Hi,
>
> > Right, this is cool. The problem is that the upstream repo would need
> > to be configured to provide a public message that something has been
> > changed
> > in it (i.e. new release) so the question is how to do this part.
>
> Ah
Hey Marc,
On Fri, Sep 1, 2017 at 8:55 AM, Marc Dequènes (Duck)
wrote:
> Quack,
>
> On 09/01/2017 01:28 AM, Michal Novotny wrote:
>
> > But I think an off-line talk might be the best. Depends on you.
>
> I can understand you don't want this thread to end-up in f
Hello Gerd,
On Fri, Sep 1, 2017 at 11:20 AM, Gerd Hoffmann wrote:
> Hi,
>
> > It's easier on implementation. That's the main reason. I generally
> > believe that
> > what's easier on implementation is better.
>
> It's maybe easier on the copr side, but not for the copr users ...
>
> If you can
Hello Pavel,
On Thu, Aug 31, 2017 at 4:37 PM, Pavel Raiskup wrote:
> On Thursday, August 31, 2017 3:48:21 PM CEST Michal Novotny wrote:
> > a) you need an additional db field. you need to have more inputs in SCM
> tabs
> > when one has a meaning only if 'cus
On Thu, Aug 31, 2017 at 1:47 PM, Pavel Raiskup wrote:
> On Thursday, August 31, 2017 11:43:08 AM CEST Michal Novotny wrote:
> > On Thu, Aug 31, 2017 at 8:43 AM, Pavel Raiskup
> wrote:
> > > I'm curious why you insist on 'make srpm'; that sounds like yo
On Thu, Aug 31, 2017 at 8:43 AM, Pavel Raiskup wrote:
> On Wednesday, August 30, 2017 5:18:39 PM CEST Michal Novotny wrote:
> > We are considering the options here and so far the most convenient
> method (at
> > least from the implementation point of view) seems to be to
&g
Hello Martin,
On Wed, Aug 23, 2017 at 2:02 PM, Martin Sehnoutka
wrote:
> Hi,
>
> I'm using Copr for build on commit for dnssec-trigger project:
> https://github.com/InfrastructureServices/dnssec-trigger-fedora
> It's using tito.
>
> But I'm looking for a different way of doing this. Especially w
Hello Petr,
On Thu, Aug 24, 2017 at 1:35 PM, Petr Stodulka wrote:
>
>
> On 24.8.2017 08:04, Pavel Raiskup wrote:
> > On Wednesday, August 23, 2017 1:46:46 PM CEST Miroslav Suchý wrote:
> >> Do you use Copr for building packages for nightlies? For building
> packages
> >> before pull request is m
e project if the batch building would be
done separately from the main project repo and only be included if
successful. Ok, thanks for this input. I think we can do something about
this.
> kind regards,
> Rudolf Kastl
>
>
>
> 2017-08-22 17:15 GMT+02:00 Kamil Dudka :
>
>&g
Hello Langdon,
On Tue, Aug 22, 2017 at 11:42 PM, Langdon White
wrote:
>
>
> On Tue, Aug 22, 2017 at 2:40 PM Michal Novotny wrote:
>
>> I would like to publicly note that I had completely different idea about
>> this project first time I have encountered it at the last
I would like to publicly note that I had completely different idea about
this project first time I have encountered it at the last Flock.
My idea was that the project will target runtime rather than build-time and
will try to provide a set of packages that would be able to
e.g. spawn and run an ht
On Tue, Aug 22, 2017 at 4:40 PM, Kamil Dudka wrote:
> On Tuesday, August 22, 2017 1:51:44 PM CEST Michal Novotny wrote:
> > Hey Kamil,
> >
> > On Tue, Aug 22, 2017 at 12:07 PM, Kamil Dudka wrote:
> > > On Tuesday, August 22, 2017 9:04:24 AM CEST Matthias Runge w
Eventually, a new version should pop up here:
https://bodhi.fedoraproject.org/updates/?packages=mock
You can give it Karma when it appears so that it reaches Fedora repos a bit
faster.
On Tue, Aug 22, 2017 at 2:41 PM, Alexander Ploumistos <
alex.ploumis...@gmail.com> wrote:
> Thanks Michal. Is t
Hey Kevin,
On Tue, Aug 22, 2017 at 2:03 PM, Kevin Kofler
wrote:
> Michal Novotny wrote:
> > - Batch package rebuilding ("Rebuild all" button in Packages view) so
> > that you can rebuild all your packages in the new chroots.
>
> Unfortunately, this feature is
Hey Kamil,
On Tue, Aug 22, 2017 at 12:07 PM, Kamil Dudka wrote:
> On Tuesday, August 22, 2017 9:04:24 AM CEST Matthias Runge wrote:
> > - the ability to directly upload srpms; that is, one can store spec
> > files etc. on the local machine. I'm undecided, if integrating a
> > distgit on copr
Hello Mikolaj,
On Tue, Aug 22, 2017 at 11:29 AM, Mikolaj Izdebski
wrote:
> On 08/22/2017 11:17 AM, Michal Novotny wrote:
> >> - it would be great, if there is a possibility to trigger rebuilds on
> >> dependent packages, like rebuild required packages after ABI bump.
>
Hello Alexander,
you haven't missed anything. It is just that there hasn't been mock release
yet
with f27 configs added. It is in upstream already but not yet released. If
it is
not in Fedora until the end of the week, then we can probably temporarily
provide
our own substitute repo configs.
clim
Hello Matthias,
On Tue, Aug 22, 2017 at 9:04 AM, Matthias Runge
wrote:
> On Tue, Aug 22, 2017 at 05:17:56AM +0200, Michal Novotny wrote:
> > Hello,
> >
> > we will have soon a planning meeting that should determine a more
> long-term
> > strategy and bring us to
Hello,
we will have soon a planning meeting that should determine a more long-term
strategy and bring us to a team agreement on what COPR currently is and
what it should be in half a year or so.
I would like to kindly ask for some input here on the devel list to find
out what the actual expectati
On Mon, Aug 21, 2017 at 1:22 PM, Michal Novotny wrote:
> Hello,
>
> On Mon, Aug 21, 2017 at 11:09 AM, Pavel Raiskup
> wrote:
>
>> On Monday, August 21, 2017 10:42:00 AM CEST Michal Novotny wrote:
>> > Hello Kevin,
>> >
>> > sorry for t
Hello,
On Mon, Aug 21, 2017 at 11:09 AM, Pavel Raiskup wrote:
> On Monday, August 21, 2017 10:42:00 AM CEST Michal Novotny wrote:
> > Hello Kevin,
> >
> > sorry for the late response caused by me being on vacations.
> >
> > On Sat, Aug 12, 2017 at 2:35 AM, Kevi
Hello Kevin,
sorry for the late response caused by me being on vacations.
On Sat, Aug 12, 2017 at 2:35 AM, Kevin Kofler
wrote:
> Hi,
>
> Michal Novotny wrote:
> > - "Follow Fedora branching" project switch that (if enabled) makes COPR
> > fork your rawhide chroo
Hello,
I am sending these release notes also to fedora-devel list (and not just
copr-devel list as usually) because they contain information
about upcoming Fedora branching and what features COPR provides to move the
set of packages from your rawhide chroots into the newly branched ones.
We have
Hello,
while working on another thing, I noticed that when use_bootstrap_container
project option was introduced (Wed Jun 14 this year), it was introduced as
enabled for existing COPR projects at that time. That was not exactly
intended as this feature is experimental.
Enabling this option makes
I am no flatpack expert, but I think that really any container technology
in question should be just a porter of an rpm or set of rpms and there
should (could) be packaged ansible scripts that are able to setup and spawn
those containers e.g. in OpenShift or just on a host machine through ssh or
by
Hello,
I was able to successfully use 'fedpkg new-sources' (still from f25) right
now.
clime
On Fri, Jul 14, 2017 at 11:04 AM, Fabio Valentini
wrote:
> Right now, I can't build updates or new packages, because "fedpkg
> new-sources" is getting stuck (for more than 15 minutes) without error
> m
Can you, please, show the emails or just one of them?
On Tue, Jun 27, 2017 at 11:34 PM, Michael Schwendt
wrote:
> Whoever set up that service, seriously?
>
> Why would I receive 610 emails for activity in "epel7"? For packages with
> a longer git history, it will likely be thousands of emails.
>
Hello,
I have implemented a set of macros specific for module development. I would
be happy to review your package if you can review mine:
https://bugzilla.redhat.com/show_bug.cgi?id=1461769
clime
___
devel mailing list -- devel@lists.fedoraproject.org
Dear rawhide users,
if you have enabled a COPR repo in the last three months (since the
beginning of December last year till yesterday), then it points to
fedora-$releasever-$basearch. You can reenable it by using `dnf copr enable
` to get .repo file pointing to actual fedora-rawhide chroot in
the
On Tue, Feb 21, 2017 at 5:15 PM, Kevin Fenzi wrote:
> On Tue, 21 Feb 2017 11:00:15 +0100
> Michal Novotny wrote:
>
> > On Tue, Feb 21, 2017 at 10:28 AM, Vít Ondruch
> > wrote:
> >
> > > I honestly don't understand what is purpose of the f26 vs master.
se as well.
P.S. Adding devel to the recipient list so that more people can comment.
> Vít
>
> Dne 21.2.2017 v 10:05 Michal Novotny napsal(a):
>
> Hello folks,
>
> We have quite recently changed naming of rawhide chroot to fXY in COPR and
> I would like to know your opinion
On Fri, Feb 3, 2017 at 12:07 PM, Didier Fabert
wrote:
> Hi there,
>
> I'm unable to build netdata package for f26 on copr. The error, in file
> root.log.gz, was about pkgconfig:
> > Error: package pkgconf-pkg-config-1.2.1-1.fc26.x86_64 conflicts with
> pkgconfig < 1:0.29.1-2 provided by pkgconfig
On Mon, Nov 7, 2016 at 6:57 PM, Matthew Miller
wrote:
> On Mon, Nov 07, 2016 at 03:13:43PM +0100, Michal Novotny wrote:
> > I'd like to announce that we now support package auto-rebuilding on a new
> > commit(s) into a Pagure repository. Apart from having your package repo
Hey,
I'd like to announce that we now support package auto-rebuilding on a new
commit(s) into a Pagure repository. Apart from having your package repo
hosted in Pagure, you just need to enable firing of fedmsg notifications
for new commits by clicking a single checkbox in 'Hooks' section...well,
The description of Kevin is very precise. I am additionally thinking about
implementing
user option to rebuild all project packages for a new target when added. So
when f27 is added, user could click one button to launch rebuild of all his
packages
for this target.
Basically, this allows us to be
The truth is that the script for the review awards will need to be written
almost from a scratch and it seems to be a longer shot from where we are
now. As a lazy programmer, I need to cheer for the stats being sent to the
list :).
clime
On Wed, Jul 13, 2016 at 11:30 PM, Kevin Fenzi wrote:
> On
On Tue, Jul 12, 2016 at 5:01 AM, Parag Nemade wrote:
> Hi,
>
> On Mon, Jul 11, 2016 at 7:05 PM, Igor Gnatenko
> wrote:
> > On Mon, Jul 11, 2016 at 3:18 PM, Raphael Groner
> > wrote:
> >> Can that information be used to award badges? There's an old open issue
> to implement badges for doing pack
On Mon, Jul 11, 2016 at 3:18 PM, Raphael Groner
wrote:
> Can that information be used to award badges? There's an old open issue to
> implement badges for doing package reviews. Maybe get in contact with the
> badges team.
> https://fedorahosted.org/fedora-badges/ticket/101
This is a nice idea
1 - 100 of 104 matches
Mail list logo
