The following Fedora EPEL 7 Security updates need testing:
Age URL
9 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-ea01d505c9
pdns-4.1.14-1.el7
7 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-a37e7c643e
xawtv-3.107-1.el7
5
The following Fedora EPEL 8 Security updates need testing:
Age URL
8 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-1790461e43
chromium-85.0.4183.121-1.el8
1 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-0f2bfced63
prosody-0.11.7-1.el8
The following builds
https://bugzilla.redhat.com/show_bug.cgi?id=1859831
Fedora Update System changed:
What|Removed |Added
Status|ON_QA |CLOSED
Fixed In Version|
https://bugzilla.redhat.com/show_bug.cgi?id=1855962
Fedora Update System changed:
What|Removed |Added
Status|ON_QA |CLOSED
Fixed In Version|
https://bugzilla.redhat.com/show_bug.cgi?id=1882884
Fedora Update System changed:
What|Removed |Added
Status|ON_QA |CLOSED
Fixed In
ok, I will try it. Thanks! : )
在 2020年10月3日星期六，Neal Gompa 写道：
> On Sat, Oct 3, 2020 at 10:18 AM Vitaly Zaitsev via devel
> wrote:
> >
> > On 03.10.2020 15:47, Ruki Wang wrote:
> > > I try `%?set_build_flags` and it works fine.
> >
> > No, it will not. This command will just force RPM to ignore
Thank you very much!
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines:
During an attempted upgrade to F33 Beta I ran into:
Error: Transaction test error:
file /usr/lib/.build-id/0e/fd9f1f23d7cefd37989b7d1b401b4994fee742 conflicts
between attempted installs of openjfx-11.0.3-1.fc33.x86_64 and
openjfx8-8.0.202-24.b07.fc33.x86_64
file
Am 03.10.20 um 00:53 schrieb Fabio Valentini:
> - python3-certbot-dns-google is newer in 32 than in 33:
> 0:1.7.0-1.fc32 > 0:1.5.0-1.fc33
>
> This is caused by python-certbot-dns-google being FTBFS for fedora 33+.
> There was no FTBFS bug reported for it, but both releng builds have failed.
>
On Sat, Oct 03, 2020 at 11:29:43PM +0300, bbonev wrote:
> Already did that in git yesterday, I will wait a couple of days to see if
> something else is suggested and will update the bug.
>
> BTW. How it goes with review and sponsorship in Fedora community - do I
> need to do something more or I
Hi Matthew,
Already did that in git yesterday, I will wait a couple of days to see if
something else is suggested and will update the bug.
BTW. How it goes with review and sponsorship in Fedora community - do I need to
do something more or I have already done all that is needed
On Sat, Oct 3, 2020 at 4:09 AM Marius Schwarz wrote:
>
> Am 03.10.20 um 11:43 schrieb Tomasz Torcz:
>
> If you do not state the devicename, how does grub choose the correct
>
> drive? I don't want to overwrite the bootloader on the ssd.
>
> There is only one correct ESP partition in EFI system
On Fri, Oct 2, 2020 at 3:12 AM Petr Pisar wrote:
>
> On Thu, Oct 01, 2020 at 11:07:28AM -0700, Samuel Sieb wrote:
> > On 10/1/20 5:52 AM, Marius Schwarz wrote:
> > >
> > > >
> > > > Is it possible to boot from the stick and then perform a grub-install
> > > > with an old grub?
> > > >
> > >
> > >
https://bugzilla.redhat.com/show_bug.cgi?id=1884931
Bug ID: 1884931
Summary: perl-Pod-Checker-1.74 is available
Product: Fedora
Version: rawhide
Status: NEW
Component: perl-Pod-Checker
Keywords: FutureFeature, Triaged
On Mon, 28 Sep 2020 16:51:02 +0200, Jan Kratochvil wrote:
> To make DWZ better consumable it needs to have the partial units separately
> parseable. That way they can be shared at IR level and not just at DWARF level
> That means:
> * DW_TAG_partial_unit should have DW_AT_language.
> *
On Sat, Oct 03, 2020 at 01:28:22AM +0300, Boian Bonev wrote:
> Here I mean the project name, which is iotop-c. I see no problem in
> renaming the binary.
Yeah, I'd suggest just making it match -- `iotop-c`.
--
Matthew Miller
Fedora Project Leader
On Thu, Oct 01, 2020 at 11:12:28PM -0500, Carl George wrote:
> Here is my rough outline of the steps required to implement this proposal.
> I imagine things would happen roughly in this order, but some things could
> probably take place in parallel.
>
> 1. EPEL Steering Committee approves the
On Fri, 2 Oct 2020 at 11:53, Vít Ondruch wrote:
> Hi,
>
> I was in contact with Sebastian, who used to work for RH and maintained
> several Fedora packages. However, due to chances in his live, he decided to
> orphan his packages. Since he is not subscribed to fedora-devel ML, I'm
> forwarding
On Sat, Oct 3, 2020 at 11:09 AM Vitaly Zaitsev via devel
wrote:
>
> On 03.10.2020 16:54, Neal Gompa wrote:
> > Instead of "%set_build_flags" or "%?set_build_flags", do the following:
>
> Don't forget about the different package names in Fedora and openSUSE.
>
> Maintainers can use something like
On 03.10.2020 16:54, Neal Gompa wrote:
> Instead of "%set_build_flags" or "%?set_build_flags", do the following:
Don't forget about the different package names in Fedora and openSUSE.
Maintainers can use something like this to avoid this problem:
BuildRequires: cmake(Foo)
BuildRequires:
On Sat, Oct 3, 2020 at 10:18 AM Vitaly Zaitsev via devel
wrote:
>
> On 03.10.2020 15:47, Ruki Wang wrote:
> > I try `%?set_build_flags` and it works fine.
>
> No, it will not. This command will just force RPM to ignore errors. No
> actual build flags will be forwarded.
>
> You need to create
On 03.10.2020 15:47, Ruki Wang wrote:
> I try `%?set_build_flags` and it works fine.
No, it will not. This command will just force RPM to ignore errors. No
actual build flags will be forwarded.
You need to create separate SPEC files for Fedora and openSUSE.
--
Sincerely,
Vitaly Zaitsev
I try `%?set_build_flags` and it works fine.
Thanks!
Miro Hrončok 于2020年10月3日周六 下午2:45写道：
> On 03. 10. 20 5:04, Ruki Wang wrote:
> > Hi, every one.
> >
> > I am making rpm spec and doing tests on copr.
> >
> > But on opensuse-leap-15.1-*, %set_build_flags still causes some problems.
> >
> >
>
Got it, thanks!
Neal Gompa 于2020年10月3日周六 下午8:07写道：
> On Sat, Oct 3, 2020 at 2:45 AM Miro Hrončok wrote:
> >
> > On 03. 10. 20 5:04, Ruki Wang wrote:
> > > Hi, every one.
> > >
> > > I am making rpm spec and doing tests on copr.
> > >
> > > But on opensuse-leap-15.1-*, %set_build_flags still
>Problem 1: package copydeps-4.0-3.fc32.noarch requires python(abi) = 3.8, but
>none of the providers can be installed
> - python3-3.8.5-5.fc32.x86_64 does not belong to a distupgrade repository
> - problem with installed package copydeps-4.0-3.fc32.noarch
This is because copydeps has been
Hi again.
You can build packages depending on Sundials by using the side-tag
f34-build-side-31299:
Use 'fedpkg build --target=f34-build-side-31299' to use it.
Use 'koji wait-repo f34-build-side-31299' to wait for the build repo to
be generated.
On 25/09/20 21:04, Antonio T. sagitter wrote:
> Hi
On Sat, Oct 3, 2020 at 2:45 AM Miro Hrončok wrote:
>
> On 03. 10. 20 5:04, Ruki Wang wrote:
> > Hi, every one.
> >
> > I am making rpm spec and doing tests on copr.
> >
> > But on opensuse-leap-15.1-*, %set_build_flags still causes some problems.
> >
> >
> > + %set_build_flags
> >
No missing expected images.
Soft failed openQA tests: 1/16 (x86_64)
(Tests completed, but using a workaround for a known bug)
Old soft failures (same test soft failed in Fedora-IoT-33-20201002.0):
ID: 684227 Test: x86_64 IoT-dvd_ostree-iso iot_clevis
URL:
Am 03.10.20 um 11:43 schrieb Tomasz Torcz:
> If you do not state the devicename, how does grub choose the correct
>> drive? I don't want to overwrite the bootloader on the ssd.
> There is only one correct ESP partition in EFI system to install
> bootloader to. You can read the code finding it at
On Sat, Oct 03, 2020 at 11:17:44AM +0200, Marius Schwarz wrote:
> Am 02.10.20 um 11:12 schrieb Petr Pisar:
> > On Thu, Oct 01, 2020 at 11:07:28AM -0700, Samuel Sieb wrote:
> >> On 10/1/20 5:52 AM, Marius Schwarz wrote:
> Is it possible to boot from the stick and then perform a grub-install
>
Am 03.10.20 um 11:17 schrieb Marius Schwarz:
>
> FYI: Not working without manual corrections
>
> insmod lvm
> insmod xfs
> set root=(hd0,gpt3)
> configfile /grub2/grub.cfg
> linux /vmlinuz-5.8.10
> initrd /initramfs-5.8.10
> boot
>
> Q: Why is configfile read, but not used if anything
Missing expected images:
Xfce raw-xz armhfp
Compose FAILS proposed Rawhide gating check!
1 of 43 required tests failed
openQA tests matching unsatisfied gating requirements shown with **GATING**
below
Failed openQA tests: 13/181 (x86_64)
New failures (same test not failed in
Am 02.10.20 um 11:12 schrieb Petr Pisar:
> On Thu, Oct 01, 2020 at 11:07:28AM -0700, Samuel Sieb wrote:
>> On 10/1/20 5:52 AM, Marius Schwarz wrote:
Is it possible to boot from the stick and then perform a grub-install
with an old grub?
>>> This attempt failed too:
>>>
>>> #
On Sat, Oct 03, 2020 at 09:22:52AM +0200, Fabrice BAUZAC-STEHLY wrote:
> Hello,
>
> I wish to contribute, especially with packaging work.
>
> I'm a 40-year-old programmer, GNU/Linux user since I'm 15, with
> knowledge about sysadmin, networking, Linux, C, Python, Perl... And I
> like good
Missing expected images:
Xfce raw-xz armhfp
Failed openQA tests: 4/181 (x86_64)
New failures (same test not failed in Fedora-33-20200929.n.0):
ID: 683936 Test: x86_64 universal install_repository_http_graphical
URL: https://openqa.fedoraproject.org/tests/683936
ID: 683991 Test:
OLD: Fedora-33-20200929.n.0
NEW: Fedora-33-20201003.n.0
= SUMMARY =
Added images:4
Dropped images: 4
Added packages: 16
Dropped packages:0
Upgraded packages: 190
Downgraded packages: 1
Size of added packages: 25.28 MiB
Size of dropped packages:0 B
Size
Hello,
I wish to contribute, especially with packaging work.
I'm a 40-year-old programmer, GNU/Linux user since I'm 15, with
knowledge about sysadmin, networking, Linux, C, Python, Perl... And I
like good technical documentation. Recently I have started contributing
some packaging work for
Announcing the creation of a new nightly release validation test event
for Fedora 33 Branched 20201003.n.0. Please help run some tests for this
nightly compose if you have time. For more information on nightly
release validation testing, see:
https://fedoraproject.org/wiki
On 03. 10. 20 5:04, Ruki Wang wrote:
Hi, every one.
I am making rpm spec and doing tests on copr.
But on opensuse-leap-15.1-*, %set_build_flags still causes some problems.
+ %set_build_flags
/var/tmp/rpm-tmp.9RYL8i: line 32: fg: no job control
error: Bad exit status from
39 matches
Mail list logo
