Thanks for fixing it!
I tried on irc, but I'm not an irc guy and couldn't make it past "cannot send
to nick/channel" ...
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora
On Saturday, November 14, 2020 2:36:43 PM CET Michael J Gruber wrote:
> Same today:
>
> ssh: connect to host 3.237.199.13 port 22: Connection timed out
>
> https://download.copr.fedorainfracloud.org/results/mjg/scribus/fedora-32-x86_64/01768969-scribus156/builder-live.log.gz
>
> Copr infra
Same today:
ssh: connect to host 3.237.199.13 port 22: Connection timed out
https://download.copr.fedorainfracloud.org/results/mjg/scribus/fedora-32-x86_64/01768969-scribus156/builder-live.log.gz
Copr infra networked borked?
___
devel mailing list --
Builds seem to be failing right in the middle due to "broken ssh connections"
again and again now. Maybe builders switching over one by one and taking build
down?
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to
On Friday, November 13, 2020 6:44:14 PM CET Iñaki Ucar wrote:
> On Fri, 13 Nov 2020 at 18:13, Pavel Raiskup wrote:
> > > - Can a build depend on more than one build ID?
> >
> > You should rather think about "batches" in this case, and each batch can
> > only depend on one batch.
> >
> > Corner
On Fri, 13 Nov 2020 at 18:13, Pavel Raiskup wrote:
>
> Thanks for questions!
>
> On Friday, November 13, 2020 5:50:46 PM CET Iñaki Ucar wrote:
> > On Fri, 13 Nov 2020 at 17:26, Pavel Raiskup wrote:
> > >
> > > Hello!
> > >
> > > On Nov 13 2020, a new Copr release landed production. The list of
Thanks for questions!
On Friday, November 13, 2020 5:50:46 PM CET Iñaki Ucar wrote:
> On Fri, 13 Nov 2020 at 17:26, Pavel Raiskup wrote:
> >
> > Hello!
> >
> > On Nov 13 2020, a new Copr release landed production. The list of user
> > visible
> > changes is in the release notes document:
> >
>
On Fri, 13 Nov 2020 at 17:50, Iñaki Ucar wrote:
>
> On Fri, 13 Nov 2020 at 17:26, Pavel Raiskup wrote:
> >
> > Hello!
> >
> > On Nov 13 2020, a new Copr release landed production. The list of user
> > visible
> > changes is in the release notes document:
> >
> >
On Fri, 13 Nov 2020 at 17:26, Pavel Raiskup wrote:
>
> Hello!
>
> On Nov 13 2020, a new Copr release landed production. The list of user
> visible
> changes is in the release notes document:
>
> https://docs.pagure.org/copr.copr/release-notes/2020-11-13.html
Many thanks for the build batches
Hello!
On Nov 13 2020, a new Copr release landed production. The list of user visible
changes is in the release notes document:
https://docs.pagure.org/copr.copr/release-notes/2020-11-13.html
Happy building!
Copr Team
___
devel mailing list --
Unfortunately, Copr still deletes data without warning:
https://bugzilla.redhat.com/show_bug.cgi?id=1868367
Kevin Kofler
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
On Wed, 12 Aug 2020 at 12:32, Pavel Raiskup wrote:
>
> On Wednesday, August 12, 2020 11:19:00 AM CEST Iñaki Ucar wrote:
> > On Wed, 12 Aug 2020 at 10:29, Pavel Raiskup wrote:
> > > - Copr newly provides a build-time macro %buildtag. Its format is
> > > `.copr` and is useable for
On Wednesday, August 12, 2020 11:19:00 AM CEST Iñaki Ucar wrote:
> On Wed, 12 Aug 2020 at 10:29, Pavel Raiskup wrote:
> >
> > Hello.
> >
> > On Aug 12 2020, a new Copr release landed production. Here is the list
> > of visible changes:
> >
> > - Project karma implemented; Logged-in users can
On 12. 08. 20 11:19, Iñaki Ucar wrote:
- Copr newly provides a build-time macro %buildtag. Its format is
`.copr` and is useable for auto-incrementing the package's NVR
in subsequent builds. It may be used in spec file like:
Release: 1%{?dist}%{?buildtag}
It could be useful
On 12. 08. 20 11:20, Pavel Raiskup wrote:
- Copr newly provides a build-time macro %buildtag. Its format is
`.copr` and is useable for auto-incrementing the package's NVR
in subsequent builds. It may be used in spec file like:
Release: 1%{?dist}%{?buildtag}
It could be
On Wednesday, August 12, 2020 10:51:56 AM CEST Miro Hrončok wrote:
> On 12. 08. 20 10:29, Pavel Raiskup wrote:
> > - Project karma implemented; Logged-in users can give
> >thumbs-up/thumbs-down to the existing copr projects. [snip]
> >This is just
>
> Assuming the arrows up and down near
On Wed, 12 Aug 2020 at 10:29, Pavel Raiskup wrote:
>
> Hello.
>
> On Aug 12 2020, a new Copr release landed production. Here is the list
> of visible changes:
>
> - Project karma implemented; Logged-in users can give
> thumbs-up/thumbs-down to the existing copr projects. This is just
>
On 12. 08. 20 10:29, Pavel Raiskup wrote:
Hello.
On Aug 12 2020, a new Copr release landed production. Here is the list
of visible changes:
- Project karma implemented; Logged-in users can give
thumbs-up/thumbs-down to the existing copr projects. This is just
another way to give
Hello.
On Aug 12 2020, a new Copr release landed production. Here is the list
of visible changes:
- Project karma implemented; Logged-in users can give
thumbs-up/thumbs-down to the existing copr projects. This is just
another way to give feedback about a particular Copr project quality.
> - Copr project "runtime" dependencies were implemented. Newly you can
> specify set of repositories your project depends on. Such repositories
> will be installed together with the copr project repo file (e.g., by
> 'dnf copr enable YOU/YOUR_PROEJCT'). Those repositories can be other
>
On Tuesday, June 16, 2020 8:48:32 PM CEST Ian McInerney wrote:
> ...snip...
> >
> > - There's now more fair build scheduler. Previously, no matter whether the
> > "background" attribute was set or not for the build - once builder was
> > allocated for a concrete copr user - copr never
...snip...
>
> - There's now more fair build scheduler. Previously, no matter whether the
> "background" attribute was set or not for the build - once builder was
> allocated for a concrete copr user - copr never terminated the builder
> as long as the user kept filling the build queue with
On Wednesday, June 10, 2020 10:31:32 PM CEST Iñaki Ucar wrote:
> > - Copr-cli supports batch build delete feature:
> >
> > $ copr-cli delete build_id [build_id ...]
>
> Hooray! Just delete or delete-build?
Yes, typo, I meant "delete-build" command.
Pavel
On Wed, 10 Jun 2020 at 21:42, Pavel Raiskup wrote:
>
> - Copr project "runtime" dependencies were implemented.
Great!
> - Copr-cli supports batch build delete feature:
>
> $ copr-cli delete build_id [build_id ...]
Hooray! Just delete or delete-build?
--
Iñaki Úcar
Hello!
On Jun 10, 2020, a new Copr release landed production. Related client tooling
updates are here:
https://bodhi.fedoraproject.org/updates/FEDORA-2020-390cce74d6
https://bodhi.fedoraproject.org/updates/FEDORA-2020-f90873700f
Hello Kevin,
thank you for your feedback.
> This is still inherently flawed and unsafe because you have absolutely no
> way of guaranteeing that the notification mail actually reached the
> maintainer, only that it has been sent. E-mail is not a certified delivery
> mechanism.
True, that's why
Pavel Raiskup wrote:
> - The EOL chroot policy scripts responsible for notifying users about
> upcoming removals were fixed, users should now always be notified - and
> if for some reason they are not, the EOL chroot will not be removed.
This is still inherently flawed and unsafe because you
On Thursday, February 6, 2020 8:42:56 AM MST Pavel Raiskup wrote:
> Hello,
>
> recently (on Feb 06, 2020) a new Copr release landed production. Here is
> the list of visible changes:
>
> - Users now can build packages against explicitly enabled modules. Go to
> `Project -> Settings -> Build
Hello,
recently (on Feb 06, 2020) a new Copr release landed production. Here is
the list of visible changes:
- Users now can build packages against explicitly enabled modules. Go to
`Project -> Settings -> Build Options -> [Edit] button (near _enabled_
chroot) -> Enable module: textarea`.
On Fri, Oct 4, 2019 at 3:37 PM Pavel Raiskup wrote:
> Hello,
>
> today (on Oct 4, 2019), new Copr release landed production.
>
> This was mostly a bugfix release, with some optimization/reliability
> patches interesting for copr administrators. But there were few exciting
> changes for the
Hello,
today (on Oct 4, 2019), new Copr release landed production.
This was mostly a bugfix release, with some optimization/reliability
patches interesting for copr administrators. But there were few exciting
changes for the end-users:
Multilib projects
-
If you go to the
Hello,
recently (on Feb 19) a major Copr update took place. It was announced,
but release notes weren't attached. Because a list of all changes
would be long and boring,
I rather decided to present you some highlights of the release.
- Allow per-package chroot-blacklisting by wildcard patterns
32 matches
Mail list logo
