On 2021-10-27 10:21 a.m., "Antonio T. sagitter"
wrote:
Use a side-tag
(https://docs.fedoraproject.org/en-US/package-maintainers/Package_Update_Guide/#multiple_packages),
please.
Done.
'''
Side tag 'f36-build-side-47153' (id 47153) created.
Use 'fedpkg build --target=f36-build-side-47153'
On Wed, 2021-10-27 at 13:40 -0400, Matthew Miller wrote:
> On Thu, Oct 21, 2021 at 04:37:18PM -0400, Ben Cotton wrote:
> > == User Experience ==
> > For some users this change may be a bit disruptive and it may
> > require
> > some learning curve for switching to alternative solutions.
>
> I've sp
Kia ora koutou,
I'm nedia, I live in NZ & I've been knocking about the matrix/irc for a few
days now. I'll be 28 on the 30th, I've been using Fedora for about a year,
Linux for about 3-4 (Ubuntu & Antergos), & have been doing software dev for
about 5-6 years.
I started my career w/ Java, then
Minutes:
https://meetbot.fedoraproject.org/fedora-meeting-1/2021-10-27/fedora_coreos_meeting.2021-10-27-16.27.html
Minutes (text):
https://meetbot.fedoraproject.org/fedora-meeting-1/2021-10-27/fedora_coreos_meeting.2021-10-27-16.27.txt
Log:
https://meetbot.fedoraproject.org/fedora-meeting-1/2021
Luca Boccassi wrote:
> If I am reading this correctly, when Fedora was first released in 2003,
> common hard drive capacity was around 80 GB:
>
https://upload.wikimedia.org/wikipedia/commons/a/a1/Hard_drive_capacity_over_time.png
> Today, 1 TB+ hard drives are common.
SSD capacity has been laggin
> Luca Boccassi wrote:
>
> The problem with your argument is that one "ridiculously negligible"
> overhead and then another and then yet another etc. ends up accumulating and
> we end up with minimum RAM and disk space requirements increased by a factor
> of 10 (!) since the day Fedora was foun
Lennart Poettering wrote:
> For one moment consider the life of the people who provide you with
> the software you run: coredumps become infinitely more useful if you
> can quickly derive which package they come from.
IMHO, core dumps should not even be enabled by default to begin with. They
are
Steve Grubb wrote:
> No good way. After composing the above email, I noticed it was lingering
> in the outbox. After some poking around, I found that one of the mail
> agents was no longer on dbus. I can only speculate it segfaulted.
That is quite likely. Akonadi agents just crash whenever they fe
Steve Grubb wrote:
> This brings up an interesting tangent (sorry), which I've asked on the KDE
> list with no answer.
Do not expect an answer from me on the k...@lists.fp.o list, as I have been
(IMHO unfairly) banned from all KDE SIG communication channels.
> When kontact segfaults, and it does
Luca Boccassi wrote:
> Whether you follow it or not, it has happened, it is happening and it will
> keep happening, because for others it is perfectly logical and highly
> desirable. So one can either stay here and complain all day long that
> containers are bad and they are all doing them wrong, a
On Wed, Oct 27, 2021 at 10:10:35PM +0200, Lennart Poettering wrote:
> On Mi, 27.10.21 20:34, Richard W.M. Jones (rjo...@redhat.com) wrote:
>
> > I have a habit of setting:
> >
> > export GLIBC_TUNABLES=glibc.malloc.check=1:glibc.malloc.perturb=99
> >
> > which causes glibc to do extra malloc int
On Wed, Oct 27, 2021 at 3:35 PM Richard W.M. Jones wrote:
>
> I have a habit of setting:
>
> export GLIBC_TUNABLES=glibc.malloc.check=1:glibc.malloc.perturb=99
>
> which causes glibc to do extra malloc integrity checks. In Rawhide at
> the moment I'm seeing memory corruption in calls like getpw
On Mi, 27.10.21 17:37, Fedora Development ML (devel@lists.fedoraproject.org)
wrote:
> On 25/10/2021 21:09, Ben Cotton wrote:
> > All binaries (executables and shared libraries) are annotated with an
> > ELF note that identifies the rpm for which this file was built. This
> > allows binaries to be
On Wed, Oct 27, 2021 at 4:07 PM Luca Boccassi wrote:
>
> > Dne 27. 10. 21 v 21:35 Luca Boccassi napsal(a):
> >
> > In repository in general (can be deb, zypper, local directory). Even the
> > offline systems
> > have some repository where they
> > get the packages from.
> >
> > Miroslav
>
> How d
On Mi, 27.10.21 20:34, Richard W.M. Jones (rjo...@redhat.com) wrote:
> I have a habit of setting:
>
> export GLIBC_TUNABLES=glibc.malloc.check=1:glibc.malloc.perturb=99
>
> which causes glibc to do extra malloc integrity checks. In Rawhide at
> the moment I'm seeing memory corruption in calls l
On Wed, Oct 27, 2021 at 08:34:11PM +0100, Richard W.M. Jones wrote:
> I have a habit of setting:
>
> export GLIBC_TUNABLES=glibc.malloc.check=1:glibc.malloc.perturb=99
>
> which causes glibc to do extra malloc integrity checks. In Rawhide at
> the moment I'm seeing memory corruption in calls l
> Dne 27. 10. 21 v 21:35 Luca Boccassi napsal(a):
>
> In repository in general (can be deb, zypper, local directory). Even the
> offline systems
> have some repository where they
> get the packages from.
>
> Miroslav
How do you know which one is it then? You have a core file from a container
On Wed, Oct 27, 2021 at 09:41:05PM +0200, Miroslav Suchý wrote:
> Dne 27. 10. 21 v 21:35 Luca Boccassi napsal(a):
> >>??? The build-id can be
> >>always retrieved from the dnf repository.
> >>
> >>Miroslav
> >Which dnf repository? What if it's not dnf but apt? Or zypper? What if it's
> >none? How
On Wed, Oct 27, 2021 at 12:44:27PM -0400, Frank Ch. Eigler wrote:
>
> sgrubb wrote:
>
> > This brings up an interesting tangent (sorry), which I've asked on the KDE
> > list with no answer. When kontact segfaults, and it does a lot, it starts
> > Dr.
> > Konqi and asks if you want to file a re
> Daniel P. Berrangé wrote:
>
> Well, my take is that it is really weird that the response to "I deleted the
> metadata from my container and now I cannot query the very metadata I
> deleted." (hardly a surprise!) is "Let us just duplicate the same metadata
> somewhere else, bloating the files
On Wed, Oct 27, 2021 at 09:13:04PM +0200, Kevin Kofler via devel wrote:
> Daniel P. Berrangé wrote:
> > AFAIK, that assumes the package NEVRs on disk haven't changed on disk
> > since the process was spawned.
>
> How common is it even that this happens? Especially nowadays where offline
> updates
On Wed, Oct 27, 2021 at 08:14:43PM +0200, Kevin Kofler via devel wrote:
> Zbigniew Jędrzejewski-Szmek wrote:
>
> > On Wed, Oct 27, 2021 at 02:00:36PM +0200, Kevin Kofler via devel wrote:
> >> offer" clause is in practice very hard to comply with. (Especially for
> >> GPLv2-only projects. The GPLv3
Miroslav Suchý writes:
> You do not need a crash for that
> /usr/libexec/drkonqi --dialog --keeprunning --pid $PID
> will try to debug running application. I tried that with PID of
> running vim.
Nice, thanks. In the "Developer Information" tab, one can watch gdb
"Downloading separate debug i
Dne 27. 10. 21 v 21:35 Luca Boccassi napsal(a):
??? The build-id can be
always retrieved from the dnf repository.
Miroslav
Which dnf repository? What if it's not dnf but apt? Or zypper? What if it's
none? How do you know?
In repository in general (can be deb, zypper, local directory). Even t
> On 27/10/2021 18:40, Daniel P. Berrangé wrote:
>
> As an upstream developer, I prefer only backtraces with debuginfo installed.
As an upstream developer, you get what users send you, which might or might not
be what you prefer. With this change, the bare minimum produced as a corefile
is usef
> Dne 25. 10. 21 v 21:09 Ben Cotton napsal(a):
>
> Why you hesitate to use network? When you allow network access then
> debuginfod already do
> that (more or less).
There can be many reasons, for example:
- privacy: it reveals what you are running to an external service
- security: airgapped o
I have a habit of setting:
export GLIBC_TUNABLES=glibc.malloc.check=1:glibc.malloc.perturb=99
which causes glibc to do extra malloc integrity checks. In Rawhide at
the moment I'm seeing memory corruption in calls like getpwnam and
gethostbyname. Unfortunately I don't have a simple reproducer
Dne 27. 10. 21 v 18:44 Frank Ch. Eigler napsal(a):
Do you have a recipe for
triggering this crash and the dr. konqi processing?
You do not need a crash for that
/usr/libexec/drkonqi--dialog \
--keeprunning--pid$PID
will try to debug running application. I tried that with PID of running vim
Daniel P. Berrangé wrote:
> AFAIK, that assumes the package NEVRs on disk haven't changed on disk
> since the process was spawned.
How common is it even that this happens? Especially nowadays where offline
updates are the default.
Kevin Kofler
Daniel P. Berrangé wrote:
> Container images are often not used and maintained in the same way as
> a traditional OS. If people want to pull in the latest RPM updates,
> they won't run 'dnf update' in the container, they'll simply build
> a new container image. Being able to query/manipulate the RP
In one week (2021-11-03), or slightly later, I will build
python-engineio 4.3.0 in Rawhide
(https://src.fedoraproject.org/rpms/python-engineio/pull-request/2).
This release technically contains a breaking change (“Reject websocket
messages larger than max_http_buffer_size”), although it should
Zbigniew Jędrzejewski-Szmek wrote:
> On Wed, Oct 27, 2021 at 02:00:36PM +0200, Kevin Kofler via devel wrote:
>> offer" clause is in practice very hard to comply with. (Especially for
>> GPLv2-only projects. The GPLv3 has made it slightly more practical,
>> admittedly.) In my experience, most proje
Hi -
> > If I read drkonqi sources correctly in that gdb is being used as the
> > backtracing backend. That suggests that its automatic debuginfod-based
> > downloading should be working on F35. Do you have a recipe for
> > triggering this crash and the dr. konqi processing?
> No good way [to r
On 27/10/2021 18:40, Daniel P. Berrangé wrote:
It is a benefit to Fedora & upstream maintainers who are on the receiving
end of bug reports from users.
As an upstream developer, I prefer only backtraces with debuginfo installed.
--
Sincerely,
Vitaly Zaitsev (vit...@easycoding.org)
__
On Thu, Oct 21, 2021 at 04:37:18PM -0400, Ben Cotton wrote:
> == User Experience ==
> For some users this change may be a bit disruptive and it may require
> some learning curve for switching to alternative solutions.
I've spoken with some of my sysadmin friends and universities, and they
suggest
On Wednesday, October 27, 2021 12:44:27 PM EDT Frank Ch. Eigler wrote:
> sgrubb wrote:
> > This brings up an interesting tangent (sorry), which I've asked on the
> > KDE
> > list with no answer. When kontact segfaults, and it does a lot, it starts
> > Dr. Konqi and asks if you want to file a report
Use a side-tag
(https://docs.fedoraproject.org/en-US/package-maintainers/Package_Update_Guide/#multiple_packages),
please.
On 10/27/21 01:42, Luya Tshimbalanga wrote:
Hello team,
I would like to let you know ImageMagick-6.9.12-26 recently landed
upstream.
Learning from the previous experie
Dne 25. 10. 21 v 21:09 Ben Cotton napsal(a):
But those
mechanisms will be different for different distributions and will
often require network access. With this change we aim to provide a
mechanism that is is very simple, provides a "human-readable" origin
information without further processing,
No missing expected images.
Failed openQA tests: 11/204 (x86_64), 7/141 (aarch64)
New failures (same test not failed in Fedora-35-20211025.n.0):
ID: 1042272 Test: x86_64 Server-dvd-iso server_role_deploy_database_server
URL: https://openqa.fedoraproject.org/tests/1042272
ID: 1042277 Test
Missing expected images:
Iot dvd x86_64
Iot dvd aarch64
Failed openQA tests: 1/16 (x86_64), 1/15 (aarch64)
Old failures (same test failed in Fedora-IoT-36-20211024.0):
ID: 1042693 Test: x86_64 IoT-dvd_ostree-iso iot_clevis
URL: https://openqa.fedoraproject.org/tests/1042693
ID: 1042713
sgrubb wrote:
> This brings up an interesting tangent (sorry), which I've asked on the KDE
> list with no answer. When kontact segfaults, and it does a lot, it starts Dr.
> Konqi and asks if you want to file a report. But because debuginfo rpms are
> not installed it fails and says not enough
On Wed, Oct 27, 2021 at 05:37:01PM +0200, Vitaly Zaitsev via devel wrote:
> On 25/10/2021 21:09, Ben Cotton wrote:
> > All binaries (executables and shared libraries) are annotated with an
> > ELF note that identifies the rpm for which this file was built. This
> > allows binaries to be identified
On Wed, Oct 27 2021 at 05:37:01 PM +0200, Vitaly Zaitsev via devel
wrote:
-1 for this change, because it will consume file system space and
99.99%
of users don't need this feature at all.
That doesn't seem fair:
The overhead is about 200 bytes for each ELF object.
We have about overall 3320
On Wed, 27 Oct 2021 15:02:30 +0200
Sandro Mani wrote:
> Hi Dan
>
> Sorry my bad - I had %{_libdir}/libalglib-%{version}.so in %files, so
> missed the bump when updating the package. I hardcoded the version in
> %files to prevent this from happening again.
no problem and thanks :-)
> Let me
On 25/10/2021 21:09, Ben Cotton wrote:
All binaries (executables and shared libraries) are annotated with an
ELF note that identifies the rpm for which this file was built. This
allows binaries to be identified when they are distributed without any
of the rpm metadata. `systemd-coredump` uses thi
On Wednesday, October 27, 2021 8:12:43 AM EDT Kevin Kofler via devel wrote:
> Daniel P. Berrangé wrote:
> > Furthermore as someone dealing with bug reports I don't have access
> > to the RPM database. That is on the end user's machine. Often all I
> > get is a core dump attached to a bug report, an
OLD: Fedora-35-20211025.n.0
NEW: Fedora-35-20211027.n.0
= SUMMARY =
Added images:0
Dropped images: 0
Added packages: 0
Dropped packages:0
Upgraded packages: 0
Downgraded packages: 0
Size of added packages: 0 B
Size of dropped packages:0 B
Size of upgraded
It turns out all that was needed was a reboot.
I did an update and since the kernel was not updated
I didn't do a reboot... that was the mistake...
I guess the flux capacitor got update and needed
a reboot!
Thanks for the help!!
steved.
On 10/27/21 8:16 AM, Chris Kelley wrote:
Hi Steve,
You
On Mi, 27.10.21 14:00, Fedora Development ML (devel@lists.fedoraproject.org)
wrote:
> Sorry, but I do not see what is "baseless" about the licensing issue (see
> also the further details I added above). And the idea is not to "force
> people to stop using" stuff, but to not spend time making it e
Missing expected images:
Xfce raw-xz armhfp
Compose FAILS proposed Rawhide gating check!
2 of 43 required tests failed
openQA tests matching unsatisfied gating requirements shown with **GATING**
below
Failed openQA tests: 8/206 (x86_64), 7/141 (aarch64)
New failures (same test not failed in Fe
Bear just needed a rebuild, which I took care of. It depends on grpc,
but was built before it in the side tag.
On 10/27/21 07:25, Miro Hrončok wrote:
On 26. 10. 21 13:53, Adrian Reber wrote:
All packages have been rebuild and the side tag has been merged. I was
not able to rebuild the followin
As foretold in the ancient prophecies, we will hold the F35 Go/No-Go
meeting[1] on Thursday 28 October at 1700 UTC in #fedora-meeting.
At this time, we will determine the status of the F35 Final for the 2
November target date #2 milestone[2]. For more information about the
Go/No-Go meeting, see t
On Wed, Oct 27, 2021 at 02:00:36PM +0200, Kevin Kofler via devel wrote:
> Zbigniew Jędrzejewski-Szmek wrote:
> > 5. This proposal is not about licensing, but if it is adopted, it'll only
> > make figuring out potential licensing violations easier (in some cases,
> > primarily when distributing with
Hi Dan
Sorry my bad - I had %{_libdir}/libalglib-%{version}.so in %files, so
missed the bump when updating the package. I hardcoded the version in
%files to prevent this from happening again.
Let me know if you need help with the rebuilds.
Sandro
On 27.10.21 14:59, Dan Horák wrote:
Hi,
se
Hi,
seems alglib got updated in rawhide, but it brought a soname bump,
because I have received a FTI bug for qmapshack. The affected packages
seems to be only:
gmsh
qmapshack
I will rebuild them both, unless someone will be faster :-)
Dan
On Wed, Oct 27, 2021 at 02:00:36PM +0200, Kevin Kofler via devel wrote:
> Zbigniew Jędrzejewski-Szmek wrote:
> > How so? It was rejected with the request to enhance the motivation section
> > and to answer some specific questions about upgrades. This has been done.
> > Why do you say an update to a
On Wed, Oct 27, 2021 at 02:12:43PM +0200, Kevin Kofler via devel wrote:
> Daniel P. Berrangé wrote:
> > Furthermore as someone dealing with bug reports I don't have access
> > to the RPM database. That is on the end user's machine. Often all I
> > get is a core dump attached to a bug report, and if
On Wed, Oct 27, 2021 at 12:47:03PM +0200, Florian Weimer wrote:
> * Zbigniew Jędrzejewski-Szmek:
>
> > On Wed, Oct 27, 2021 at 09:38:35AM +0200, Florian Weimer wrote:
> >> * Ben Cotton:
> >>
> >> > https://fedoraproject.org/wiki/Changes/Package_information_on_ELF_objects
> >> >
> >> > == Summary
Hi Steve,
You don't specify which version of Fedora each box is using, but if you
have one running F32 or earlier and one running F33+ then Petr is probably
correct. This is likely a result of SHA-1 being disabled in the DEFAULT
SWCP:
https://fedoraproject.org/wiki/Changes/StrongCryptoSettings2
h
Florian Weimer wrote:
> Can we enhance this to collect the package versions of all code that is
> linked statically?
That would make the bloat even larger.
Kevin Kofler
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send
Daniel P. Berrangé wrote:
> Furthermore as someone dealing with bug reports I don't have access
> to the RPM database. That is on the end user's machine. Often all I
> get is a core dump attached to a bug report, and if I'm lucky they
> manually typed a couple of RPM NEVRs into the bug description.
Zbigniew Jędrzejewski-Szmek wrote:
> How so? It was rejected with the request to enhance the motivation section
> and to answer some specific questions about upgrades. This has been done.
> Why do you say an update to a proposal that answers the issues that were
> raised should not be resubmitted?
OLD: Fedora-Rawhide-20211025.n.0
NEW: Fedora-Rawhide-20211027.n.0
= SUMMARY =
Added images:2
Dropped images: 0
Added packages: 4
Dropped packages:3
Upgraded packages: 241
Downgraded packages: 0
Size of added packages: 1.48 MiB
Size of dropped packages
On Wed, Oct 27, 2021 at 7:32 AM Luca Boccassi wrote:
>
> > * Zbigniew Jędrzejewski-Szmek:
> >
> >
> > The general case of any statically linked code. It could be libgcc,
> > startup files, the non-shared bits of glibc, static-only libraries, or
> > header-only C++ libraries.
> >
> > Thanks,
> > F
> * Zbigniew Jędrzejewski-Szmek:
>
>
> The general case of any statically linked code. It could be libgcc,
> startup files, the non-shared bits of glibc, static-only libraries, or
> header-only C++ libraries.
>
> Thanks,
> Florian
This would be indeed useful, but quite harder to do automagical
On 26. 10. 21 13:53, Adrian Reber wrote:
All packages have been rebuild and the side tag has been merged. I was
not able to rebuild the following packages:
* bear
https://bugzilla.redhat.com/show_bug.cgi?id=2017733
* community-mysql
https://bugzilla.redhat.com/show_bug.cgi?id=2017735
V Tue, Oct 26, 2021 at 01:31:31PM -0400, Steve Dickson napsal(a):
> A very strange problem... on one of my fedora
> build machine I'm getting the following error
> when I do a git pull
>
> $ git pull
> sign_and_send_pubkey: signing failed for RSA "/home/steved/.ssh/id_rsa" from
> agent: agent refu
* Zbigniew Jędrzejewski-Szmek:
> On Wed, Oct 27, 2021 at 09:38:35AM +0200, Florian Weimer wrote:
>> * Ben Cotton:
>>
>> > https://fedoraproject.org/wiki/Changes/Package_information_on_ELF_objects
>> >
>> > == Summary ==
>> > All binaries (executables and shared libraries) are annotated with an
>>
Hi, I remember a few years ago an imageMagick upgrade , we made one
compat-ImageMagick693 [1] and after a few days the packages was not
needed anymore .
I propose do the same , do one compat-ImageMagick6.9.12 and after
upgrade ImageMagick to 7 ...
[1]
https://bodhi.fedoraproject.org/updates/?
No missing expected images.
Soft failed openQA tests: 1/8 (aarch64), 1/8 (x86_64)
(Tests completed, but using a workaround for a known bug)
New soft failures (same test not soft failed in Fedora-Cloud-34-20211026.0):
ID: 1041886 Test: aarch64 Cloud_Base-qcow2-qcow2 cloud_autocloud@uefi
URL:
On Tue, Oct 26, 2021 22:52:40 -0400, Matthew Miller wrote:
> On Fri, Oct 22, 2021 at 03:56:42PM +0100, Ankur Sinha wrote:
> > If it's a general issue, it'll break kinit etc. for all package
> > maintainers as soon as they get the update. (Running `fedpkg
> > new-sources` was how I ran into the issu
On Mon, Oct 25, 2021 at 03:09:00PM -0400, Ben Cotton wrote:
> https://fedoraproject.org/wiki/Changes/Package_information_on_ELF_objects
>
> == Summary ==
> All binaries (executables and shared libraries) are annotated with an
> ELF note that identifies the rpm for which this file was built. This
>
On Wed, Oct 27, 2021 at 10:01:30AM +0200, Jakub Jelinek wrote:
> On Mon, Oct 25, 2021 at 03:09:00PM -0400, Ben Cotton wrote:
> > === New system: `.note.package` ===
> >
> > The new note is created and propagated similarly to
> > `.note.gnu.build-id`. The difference is that we inject the informatio
Hi Sundeep,
First of all I want to say thanks a lot for your contribution to sort
the languages in Anaconda. Especially for me as Anaconda developer this
is really handy feature.
I really like to see that you are thinking about the next improvement. I
love to see that, however, please wait w
On Mon, Oct 25, 2021 at 03:09:00PM -0400, Ben Cotton wrote:
> === New system: `.note.package` ===
>
> The new note is created and propagated similarly to
> `.note.gnu.build-id`. The difference is that we inject the information
> about package ''nevra'' from the build system.
Is the .note.package
Hello all,
Please ignore this reminder, as it's a leftover from the previous scheduling.
The Source-git SIG meetings were re-scheduled to happen every 4 weeks,
the next one is on the 10th of November.
Hunor
On Tue, Oct 26, 2021 at 4:32 PM wrote:
>
> Dear all,
>
> You are kindly invited to the
On Wed, Oct 27, 2021 at 09:38:35AM +0200, Florian Weimer wrote:
> * Ben Cotton:
>
> > https://fedoraproject.org/wiki/Changes/Package_information_on_ELF_objects
> >
> > == Summary ==
> > All binaries (executables and shared libraries) are annotated with an
> > ELF note that identifies the rpm for w
* Ben Cotton:
> https://fedoraproject.org/wiki/Changes/Package_information_on_ELF_objects
>
> == Summary ==
> All binaries (executables and shared libraries) are annotated with an
> ELF note that identifies the rpm for which this file was built. This
> allows binaries to be identified when they ar
No missing expected images.
Soft failed openQA tests: 1/8 (x86_64), 1/8 (aarch64)
(Tests completed, but using a workaround for a known bug)
Old soft failures (same test soft failed in Fedora-Cloud-33-20211026.0):
ID: 1041866 Test: x86_64 Cloud_Base-qcow2-qcow2 cloud_autocloud
URL: https://op
79 matches
Mail list logo
