On Sunday, November 10, 2019, Kevin Kofler wrote:
> Frantisek Zatloukal wrote:
> > How is statically linked libpython hack? It's just a different way to do
> > it, isn't it?
>
> It means you are shipping 2 copies of the Python interpreter, one
> statically
> linked into the python3 binary and one
That's right because I have a signature not a checksum. On Nov 10, 2019 10:19, Vascom wrote:It is about signatures, not checksums.вс, 10 нояб. 2019 г., 9:47 Baxi :I followed fedora source file verification and there was nothing about SHA checksum verification. Also it is 2048
It is about signatures, not checksums.
вс, 10 нояб. 2019 г., 9:47 Baxi :
> I followed fedora source file verification and there was nothing about SHA
> checksum verification. Also it is 2048 bits long so I doubt it is SHA256
> checksum file.
>
>
> https://docs.fedoraproject.org/en-US/packaging-gu
I followed fedora source file verification and there was nothing about SHA checksum verification. Also it is 2048 bits long so I doubt it is SHA256 checksum file.https://docs.fedoraproject.org/en-US/packaging-guidelines/#_source_file_verificationOn Nov 10, 2019 10:05, Vascom wrote:May be you need
May be you need use sha256sum instead gpg?
вс, 10 нояб. 2019 г., 9:17 Baxi :
> Hi. I am trying to package a program. The upstream provided sha256sum.asc
> file. Verifying tarball with that signature says, Can't check signature: No
> public key. I found his public key in key directory by searching
Hi. I am trying to package a program. The upstream provided sha256sum.asc file. Verifying tarball with that signature says, Can't check signature: No public key. I found his public key in key directory by searching his email and added that key. Now gpg says Bad signature from that person. Also upst
Announcing the creation of a new nightly release validation test event
for Fedora 32 Rawhide 20191109.n.1. 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 Sat, 2019-11-09 at 16:30 +0100, Miro Hrončok wrote:
> On 09. 11. 19 8:39, Kevin Kofler wrote:> Miro Hrončok wrote:
> >> Anyway, I've closed NEW bugs with successful builds after the
> mass
> >> rebuild.
> >
> > Can you please post an updated list with that done?
IMHO, is a better bugzilla q
Frantisek Zatloukal wrote:
> How is statically linked libpython hack? It's just a different way to do
> it, isn't it?
It means you are shipping 2 copies of the Python interpreter, one statically
linked into the python3 binary and one as a shared library. This is much
less elegant than shipping a
Hello,
Here's a trivial review if anyone would like to swap for another easy
review:
https://bugzilla.redhat.com/show_bug.cgi?id=1770496
If you are a new packager or looking to be sponsored to the packager
team, please feel free to review this one unofficially for practice too.
--
Thanks,
Regar
On Sat, Nov 09, 2019 at 12:36:33PM +0100, Miro Hrončok wrote:
> On 06. 11. 19 22:02, Kevin Fenzi wrote:
> > On Wed, Nov 06, 2019 at 08:56:53PM +0100, Miro Hrončok wrote:
> > > On 06. 11. 19 20:41, Gwyn Ciesla via devel wrote:
> > > > I'll take openal-soft, pdfbox, freealut, python-httplib2, and dos
On Fri, Nov 08, 2019 14:06:18 -0800, Kevin Fenzi wrote:
> On Fri, Nov 08, 2019 at 01:14:14PM +, Ankur Sinha wrote:
> > On Fri, Nov 08, 2019 13:16:21 +0100, Miro Hrončok wrote:
> > > zathura-cb
> > > zathura-djvu
> > > zathura-pdf-mupdf
> > > zathura-pdf-poppler
> > > zathura-ps
> >
> > These a
* Ben Cotton:
> https://fedoraproject.org/wiki/Changes/PythonStaticSpeedup
>
> == Summary ==
> Python 3 traditionally in Fedora was built with a shared library
> libpython3.?.so and the final binary was dynamically linked against
> that shared library. This change is about creating the static libr
On 09. 11. 19 18:15, Dominik 'Rathann' Mierzejewski wrote:
On Saturday, 09 November 2019 at 16:30, Miro Hrončok wrote:
On 09. 11. 19 8:39, Kevin Kofler wrote:> Miro Hrončok wrote:
Anyway, I've closed NEW bugs with successful builds after the mass
rebuild.
Can you please post an updated list w
On Sat, Nov 9, 2019 at 8:31 AM Kevin Kofler wrote:
> Sorry, but I'm with Vít there. If Python is running into toolchain
> limitations, the goal should be to work on improving the toolchain, not to
> add a hack with side effects (bloat, compatibility issues) to the Python
> package, a hack with wh
On Thu, Nov 7, 2019 at 1:32 PM Miro Hrončok wrote:
>
> ...
> "[2 months for RCs instead of 1] allows for synchronizing the schedule of
> Python
> release management with Fedora. They've been historically very helpful in
> early
> finding regressions not only in core Python but also in third-part
On Thursday, 07 November 2019 at 13:31, Miro Hrončok wrote:
> Hello,
>
> I'd like to inform you that [PEP 602] "Annual Release Cycle for Python" has
> been approved and [PEP 596] "Python 3.9 Release Schedule" is pending
> approval:
>
> tl;dr New Python 3.X versions will be released annually, with
Hello!
On Saturday, 09 November 2019 at 18:07, Lyes Saadi wrote:
[...]
> So, as a last statement (or paragraph), thank you all, thank you for reading
> me, thank you for your hard work, thank you for dedicating your life to
> Linux, to help millions around the globe, for freeing the poor and the
>
On Saturday, 09 November 2019 at 16:30, Miro Hrončok wrote:
> On 09. 11. 19 8:39, Kevin Kofler wrote:> Miro Hrončok wrote:
> >> Anyway, I've closed NEW bugs with successful builds after the mass
> >> rebuild.
> >
> > Can you please post an updated list with that done?
> https://bugzilla.redhat.com/
Hi !
So, it's now 1 week that I have proposed to join the package maintainer
community ( https://bugzilla.redhat.com/show_bug.cgi?id=1770147 , it
would be really kind of you to review it ;), or give me a thought, not
especially sponsorship, just advice) and that I subscribed to the devel
mail
On 09. 11. 19 8:39, Kevin Kofler wrote:> Miro Hrončok wrote:
>> Anyway, I've closed NEW bugs with successful builds after the mass
>> rebuild.
>
> Can you please post an updated list with that done?
https://bugzilla.redhat.com/buglist.cgi?bug_id=1701227,1716412,1716488,1716525,1716546,1729908,1734
Le samedi 09 novembre 2019 à 12:46 +0100, Marius Schwarz a écrit :
> Am 09.11.19 um 10:12 schrieb Nicolas Mailhot via devel:
> > That’s why DoH is intrinsically centralized and rotten to the core.
> >
> > DoH supporters are perfectly happy with a world where there is no
> > standard for delegation
Am 09.11.19 um 10:12 schrieb Nicolas Mailhot via devel:
> That’s why DoH is intrinsically centralized and rotten to the core.
>
> DoH supporters are perfectly happy with a world where there is no
> standard for delegation. And if there is no standard, classical network
> effects will favor the bigg
On 06. 11. 19 22:02, Kevin Fenzi wrote:
On Wed, Nov 06, 2019 at 08:56:53PM +0100, Miro Hrončok wrote:
On 06. 11. 19 20:41, Gwyn Ciesla via devel wrote:
I'll take openal-soft, pdfbox, freealut, python-httplib2, and dosbox. FAS:limb
Thanks for the quick response.
BTW For example python-httplib
Le samedi 09 novembre 2019 à 12:04 +0100, Nicolas Mailhot a écrit :
> Le samedi 09 novembre 2019 à 11:09 +0100, Tomasz Torcz a écrit :
> > On Thu, Nov 07, 2019 at 06:18:46PM +0100, Nicolas Mailhot via devel
> > wrote:
> > Here's a network management lesson for you:
> > - run DoH resolver* not on
Le samedi 09 novembre 2019 à 11:09 +0100, Tomasz Torcz a écrit :
> On Thu, Nov 07, 2019 at 06:18:46PM +0100, Nicolas Mailhot via devel
> wrote:
> > > >
> Here's a network management lesson for you:
> - run DoH resolver* not on ::1, but on IP available on your LAN
> - put above IP in DHCP and RA
On 09. 11. 19 11:38, Peter Lemenkov wrote:
Hello All,
Sorry for the late answer but coupld you please keep these - I am
working on building them:
rpms/couchdb
rpms/erlang-clique
rpms/erlang-cluster_info
rpms/erlang-cuttlefish
rpms/erlang-erlando
rpms/erlang-erlydtl
rpms/erlang-riak_search
rpms/e
Hello All,
Sorry for the late answer but coupld you please keep these - I am
working on building them:
rpms/couchdb
rpms/erlang-clique
rpms/erlang-cluster_info
rpms/erlang-cuttlefish
rpms/erlang-erlando
rpms/erlang-erlydtl
rpms/erlang-riak_search
rpms/erlang-stdlib2
rpms/erlpmd
rpms/fop
rpms/ugene
Hello All,
Sorry for the late answer but coupld you please keep these - I am
working on building them:
rpms/couchdb
rpms/erlang-clique
rpms/erlang-cluster_info
rpms/erlang-cuttlefish
rpms/erlang-erlando
rpms/erlang-erlydtl
rpms/erlang-riak_search
rpms/erlang-stdlib2
rpms/erlpmd
rpms/fop
rpms/ugene
On Thu, Nov 07, 2019 at 06:18:46PM +0100, Nicolas Mailhot via devel wrote:
> > >
> > > DoH has zero integration and manageability. “It’s not centralized”
> > > (but
> > > you have to set manually DoH settings in all apps *or* rely on a
> > > centralized Google DoH whitelist) is an utter joke.
> >
Le samedi 09 novembre 2019 à 01:15 +0100, Sheogorath via devel a
écrit :
> And the owner should be able to delegate this decision to the
> network
> > manager.
> >
>
> Then let's talk on how we properly implement this delegation process
> instead of asking ourselves whenever we want DoH or DoT o
Il giorno gio, 07/11/2019 alle 10.27 +, Sérgio Basto ha scritto:
> I can help you here as I'm a Fedora packager maintainer .
>
> Have you Pull request and BugZilla reports with that information
Nico, have you filled the BugZilla Request suggested by Sérgio?
For rebuild last samba package w
32 matches
Mail list logo