guous and its name is
poorly chosen. But I realise it's way too late to change "~/.local" to
anything now.
And this leads to why I'd like to see a much broader discussion on the
topic about ~/.local/bin, also bringing it outside of Fedora's core.
Lets rather move forward w
ware popping up an alert saying: "What you're about
to do now is most likely crazy, silly and stupid. Are you sure you really
want to do this? You might regret bitterly if you proceed!"
Just like what Firefox has done with the "about:config" warning.
kind regards,
D
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 27/07/11 17:40, Roman Rakus wrote:
> Hi all,
> from the discussion here, I'm tempted to revert the change. Any objections?
+1 ... at least the there is some common consensus, also across distributions.
kind regards,
David Sommerseth
stands this, and understands what will happen when their
binaries are attempted started on a different arch via NFS mounts. They
most likely also know what they're doing when creating ~/bin or similar
directories and updating their .*shrc. Average user John Doe, doesn't
really need know th
s with such needless verbose logging
Did you take a look at /var/log/dnf.rpm.log?
--
kind regards,
David Sommerseth
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
On 10/09/15 17:46, Reindl Harald wrote:
>
> Am 10.09.2015 um 17:38 schrieb David Sommerseth:
>> On 10/09/15 15:31, Reindl Harald wrote:
>>> what in the world is that garbage instead a clear and simple log as
>>> /var/log/yum.log just listing installed
re users out there ... Or if someone has
already done that - no need to reinvent the wheel!
--
kind regards,
David Sommerseth
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
aper over the cracks. I've seen that again and again and
> it just stops being maintainable after a few years.
+1 ... If the kernel isn't perfect, lets make the kernel perfect instead.
Just my 2 cents.
--
kind regards,
David Sommerseth
--
devel mailing list
devel@lis
On 28/05/15 17:45, Josh Boyer wrote:
> On Thu, May 28, 2015 at 11:26 AM, David Sommerseth wrote:
>>
>> Hi,
>>
>> I've started poking into packaging the mhvtl project for Fedora and
>> EPEL. This package also contains a kernel module, which normally wor
On 28/05/15 23:03, David Smith wrote:
> On 05/28/2015 10:26 AM, David Sommerseth wrote:
>
> ... stuff deleted ...
>
>> Any thoughts or comments to this approach? Anyone got a better idea?
>
> Your process looks reasonable.
Thanks!
>> Yes, I do know it
On 29/05/15 14:54, Josh Boyer wrote:
> On Fri, May 29, 2015 at 8:40 AM, David Sommerseth wrote:
>> On 28/05/15 17:45, Josh Boyer wrote:
>>> On Thu, May 28, 2015 at 11:26 AM, David Sommerseth
>>> wrote:
>>>>
>>>> Hi,
>>>>
>>&
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 29/05/15 17:04, Simon Farnsworth wrote:
> On Friday 29 May 2015 15:24:24 David Sommerseth wrote:
>>
>> On 28/05/15 23:03, David Smith wrote:
>
>>> But really the best solution here is to get the mhvtl kernel
>>
kind regards,
David Sommerseth
___
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:
opy generation and prepare bigger entropy pools than
what's default in the kernel space.
But as mentioned, be careful with havege. It might not be as random
as you'd expect.
kind regards,
David Sommerseth
-BEGIN PGP SIGNAT
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 30/03/12 21:01, Przemek Klosowski wrote:
> On 03/30/2012 01:02 PM, David Sommerseth wrote:
>>
>> That sounds reasonable. Unless I mix /dev/random and
>> /dev/urandom, the latter blocks until it has filled up the
>> e
esn't make any setups less complicated. Managing security
properly is a complicated task.
I would further like to hear *how* you mean tcpwrappers "make things
worse". You just state it, you don't provide any arguments supporting it.
And comparing code and condoms is just as clever as comparing age and
wisdom.
--
kind regards,
David Sommerseth
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
O load and energy consumption is crucial - and especially if you
have plenty of RAM. But (spinning) disk space is still fairly cheap,
and /tmp on a real disk behaves in a predictable manner - even with
misbehaving programs. And RAM is far more expensive per GB than
spinning disks.
I'
stream began to be a
bit too big. There are still a few things which needs to be ironed out.
But once the mbed TLS/OpenSSL issue and a few other more minor issues
gets resolved, I'd say we're pretty much in a reasonable shape.
If you have questions, issues or comments ... feel fr
On 26/04/17 17:08, Lee Howard wrote:
> On 04/25/2017 01:39 PM, David Sommerseth wrote:
>> This is actually just a very late heads-up about challenges with OpenVPN
>> in Fedora 26.
>>
>> Fedora is moving towards OpenSSL v1.1, which is in my opinion a sane and
>>
On 27/04/17 01:20, Dominik 'Rathann' Mierzejewski wrote:
> On Wednesday, 26 April 2017 at 21:18, David Sommerseth wrote:
>> On 26/04/17 17:08, Lee Howard wrote:
>>> On 04/25/2017 01:39 PM, David Sommerseth wrote:
>>>> This is actually just a very late heads-
On 27/04/17 23:15, Pete Travis wrote:
>
>
> On Apr 27, 2017 3:13 PM, "David Sommerseth" <mailto:d...@eurephia.org>> wrote:
>
> On 27/04/17 01:20, Dominik 'Rathann' Mierzejewski wrote:
> > Thanks a lot for the write-up, David. Can you m
.spec files, *whatever* which uses
your approach so we can see and get experience on how to resolve it.
If you're not coming up with anything concrete by now, you'll just be
ignored and mail threads of such types just gets silently ignored by the
mailing list recipients.
--
kind regards,
D
nsider doing something
similar in Fedora. Without that we have no idea how to adopt this to a
full scale on all packages and how much work it will be.
The bottom line is: Show us a proof-of-concept which can be deployed
and tested directly in Fedora. And the POC *MUST* work in a Fedora
environment
> On 2 May 2017 at 11:14, David Sommerseth wrote:
>> Show us a dist-git repos we can clone and run 'fedpkg mockbuild' and see
>> how this works for _Fedora_.
>>
>> How things are done in various other distributions doesn't mean it can
>> be r
p with testing these
releases.
--
kind regards,
David Sommerseth
signature.asc
Description: OpenPGP digital signature
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
On 12/05/17 13:59, Jonathan Wakely wrote:
> On 11/05/17 16:59 +0200, David Sommerseth wrote:
>>
>> Hi,
>>
>> Just making a little noise here, as the upstream OpenVPN community have
>> released v2.4.2 which fixes to critical authenticated remote Do
On 12/05/17 13:59, Jonathan Wakely wrote:
> On 11/05/17 16:59 +0200, David Sommerseth wrote:
>>
>> Hi,
>>
>> Just making a little noise here, as the upstream OpenVPN community have
>> released v2.4.2 which fixes to critical authenticated remote Do
o seems to be handled quite well regardless if you are online or not.
From my perspective, SSSD solves more issues than what nscd is capable
of, at least to how I've learnt to know nscd. And my experience with
computers enrolled into a FreeIPA managed network have overall just been
a wonderful and
eason enough to treat it as
> system-wide.
One such program which strikes my mind instantly is logwatch ... how
will that cope this change?That said, this change does make a lot of
sense; as long as log parses won't choke and die. And those tools
should be fixed in these cases, don
x27;t test AES-128-GCM).
So I would recommend to re-test your own setup with the latest v2.4.3 on
the server side; which is what we ship in F25 and newer.
--
kind regards,
David Sommerseth
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
a 19, which I
doubt is such a good alternative in the long run. But I need to
consider that if BlueZ isn't downgraded somehow.
As a side note, it also needs to be discussed how such a key feature of
the bluetooth stack could go unnoticed through QA, and how to avoid this
from
On 23/01/14 19:58, Frank Murphy wrote:
> On Thu, 23 Jan 2014 19:53:19 +0100
> David Sommerseth wrote:
>
>>
>> Hi all,
>>
>> This might be a viewed as a fire torch, but there is, IMO, a major
>> regression in BlueZ 5 which is shipped in Fedora 20. It does
On 23/01/14 21:19, Dan Williams wrote:
> On Thu, 2014-01-23 at 14:17 -0600, Dan Williams wrote:
>> On Thu, 2014-01-23 at 20:04 +0100, David Sommerseth wrote:
>>> On 23/01/14 19:58, Frank Murphy wrote:
>>>> On Thu, 23 Jan 2014 19:53:19 +0100
[...snip...]
>>> M
On 23/01/14 23:59, Dan Williams wrote:
> On Thu, 2014-01-23 at 16:58 -0500, Brian J. Murrell wrote:
>> On Thu, 2014-01-23 at 20:04 +0100, David Sommerseth wrote:
>>>
>>> Nope, several packages depends on the bluez-5.13-1 package.
>>
>> Indeed. However I coul
On 23/01/14 23:16, Chris Murphy wrote:
> On Jan 23, 2014, at 2:56 PM, "Brian J. Murrell" wrote:
>> On Thu, 2014-01-23 at 19:53 +0100, David Sommerseth wrote:
>>
>>> As a side note, it also needs to be discussed how such a key feature of
>>> the bluetoo
dsfree profile working.
Anyhow, I'm past this discussion and have started to figure out how to
recompile the needed packages. So anything which can simplify this job
is appreciated.
--
kind regards,
David Sommerseth
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedora
On 24/01/14 18:30, Dan Williams wrote:
> On Fri, 2014-01-24 at 12:21 +0100, David Sommerseth wrote:
>> On 23/01/14 21:19, Dan Williams wrote:
>>> On Thu, 2014-01-23 at 14:17 -0600, Dan Williams wrote:
>>>> On Thu, 2014-01-23 at 20:04 +0100, David Sommerseth wrote:
her hand can have a purpose, when used between DNS servers.
For more details about DoH challenges ... please have a look at this talk:
<https://www.youtube.com/watch?v=8SJorQ9Ufm8>
--
kind regards,
David Sommerseth
___
devel mailing list --
On 06/11/2019 18:56, Michael Catanzaro wrote:
> On Wed, Nov 6, 2019 at 4:54 pm, David Sommerseth wrote:
>> Yes, TLSv1.3 with encrypted SNI will help to some degree, but still there IP
>> addresses you connect to will still provide meta data which can be used to
>> pr
to do a move, it is possible to do such a
change in 4 years.
Time has run up. It is time to move on and accept the fate of Python 2
packages not being ready. Those caring so much for unported Python 2 packages
now got a brilliant chance to help moving them forward to Python 3 too.
On 14/08/2019 15:01, Kevin Kofler wrote:
> David Sommerseth wrote:
>> Like it or not, Python 2 is going to die:
>> <https://www.python.org/dev/peps/pep-0373/>
>>
>> Python 2 will not be maintained by upstream after January 1, 2020. Python
>> 2 will go EOL du
der that this is the static library is built by default, it is a
tiny library which is really fast to build and the built binaries are less
than a few megabytes all together.
As I can see it, there is little benefit of removing lz4-static. But I might
overlook something.
On 14/08/2019 23:08, Jason L Tibbitts III wrote:
>>>>>> "DS" == David Sommerseth writes:
>
> DS> As I can see it, there is little benefit of removing lz4-static.
>
> Isn't that entirely the decision of those maintaining the package? It's
&g
ect.org/wiki/How_to_remove_a_package_at_end_of_life
[...snip...]
> dsommers: python-which
This surprises me quite a lot. I have never been a package maintainer for
this package.
--
kind regards,
David Sommerseth
___
devel mailin
ple confuse the terms all the time and was wondering what to
> do about it without changing them.)
Looking at the URL above, seeing "Maintained by orphan" ... that certainly
does not help clear up any confusion ;-)
--
kind regards,
David Sommerseth
el@lists.sourceforge.net/msg19394.html>
[1] <https://copr.fedorainfracloud.org/coprs/dsommers/openvpn3/>
--
kind regards,
David Sommerseth
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists
e binaries we provide.
* D-Bus details
<https://github.com/OpenVPN/openvpn3-linux/tree/master/docs/dbus>
* man pages:
<https://github.com/OpenVPN/openvpn3-linux/tree/master/docs/man/>
Feel free to reach out if you have some questions or good ideas.
--
kind regards,
David Sommerseth
OpenV
On 01/02/2019 00:01, Tom Hughes wrote:
> On 31/01/2019 22:44, David Sommerseth wrote:
>
>> This new client shares the same code base the OpenVPN Connect (proprietary)
>> clients uses as well as the OpenVPN for Android when switching to use the
>> OpenVPN 3 backend. The
shouldn't be too daunting, as you can get a long way by using all the
various D-Bus interfaces being exposed by the OpenVPN 3 Linux services.
Please get in touch if you want to get involved and I can ensure you get
started in the right direction instantly.
--
kind regards,
David Sommer
tem-wide), it felt like an odd process ("Is
this the right template? In a wiki? Have I filled out all the proper fields
correctly? How is this proposal picked up and distributed properly?" are some
of the thousands questions which popped up
details, but I believe this is what /etc/firefox/pref is for.
There is also /usr/lib64/firefox/defaults/preferences, but this is owned by
the firefox package and can be overwritten.
At least a few places to look further.
--
kind regards,
David Somme
H/IBM employees?
Even though this is not an official source of any kind, I think the analysis
done here pretty well covers these questions for now:
<https://www.zdnet.com/article/red-hat-an-independent-barony-in-the-kingdom-of-ibm/>
--
kind regar
he future
cloud solutions?
I do believe Fedora, as a whole, plays a fundamental role in the bigger
ecosystem for RHEL and towards the hybrid cloud everyone works towards.
Fedora plays a role providing a good experience and platform, all from the
developers and the sys-admins perspective to the end u
Fedora Copr repository available too, which contains all
the needed pieces:
<https://copr.fedorainfracloud.org/coprs/dsommers/openvpn-beta/>
--
kind regards,
David Sommerseth
signature.asc
Description: OpenPGP digital signature
___
devel mailing l
y.openvpn.net/openvpn/wiki/SupportedVersions>
--
kind regards,
David Sommerseth
signature.asc
Description: OpenPGP digital signature
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedorapr
.
If you have any questions or comments, feel free to reach out!
--
kind regards,
David Sommerseth
OpenVPN Inc
signature.asc
Description: OpenPGP digital signature
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubs
ji run the build, you can also use 'fedpkg build
--scratch' and provide an SRPM (generated by 'fedpkg srpm'). This shouldn't
need to be git pushed either to work.
Just my 2 cents.
--
kind regards,
David Sommerseth
signature.asc
Description: OpenPGP digital signature
On 09/02/18 23:46, Kevin Kofler wrote:
> David Sommerseth wrote:
>> Doesn't 'fedpkg mockbuild' resolve those test builds? To my knowledge,
>> this is fairly close to what koji does under the hood. Then you'll have
>> everything tested locally, git tree ca
On 10/02/18 12:54, Kevin Kofler wrote:
> David Sommerseth wrote:
>> I doubt Koji was primarily built for "does this work?"-builds. It exists
>> to build proper packages targeting Fedora repositories.
>
> But that is the point, to build a proper package:
>
>
t still use any of htese for legacy environments?
Perhaps a silly and ignorant question but is it still possible to send
builds to EPEL 5 repositories? I thought that option got closed long ago,
together with RHEL 5 reaching EOL.
--
kind regards,
David Sommerseth
signature.asc
Descr
ely bad
and useless". And since we have the attention of the rpmlint maintainer,
perhaps there would be a better chance to figure out how to report those
issues in a better way - or remove what isn't truly an issue.
--
kind regards,
David Sommerseth
signature.asc
Description: OpenP
d. I
am very much thankful for all automation being done.
--
kind regards,
David Sommerseth
signature.asc
Description: OpenPGP digital signature
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
On 16/02/18 19:48, Tom Hughes wrote:
> On 16/02/18 18:26, David Sommerseth wrote:
>
>> But my "worst" example was probably the openvpn package I'm now in charge for
>> (and I am a core upstream developer for that project as well). But it didn't
>> take
gt;
> I think the old maintainer did a blog post about this some time ago,
> can't seem to find it with a quick search, but I think it was on the
> planet.
Here's some traces ...
<https://twitter.com/hogarthj/status/961300659931926528>
Not sure what
ld issue.
Any advice would be appreciated.
--
kind regards,
David Sommerseth
signature.asc
Description: OpenPGP digital signature
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.
el>
[2] <https://community.openvpn.net/openvpn/newticket>
(Need a Trac account to file tickets)
--
kind regards,
David Sommerseth
OpenVPN Inc
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.
ot gone as far as Fedora 33.
Common to all of these alternatives, the VPN server must push DNS options or
the client configuration file must include the appropriate --dhcp-options.
[0]
<https://www.mail-archive.com/openvpn-devel@lists.sourceforge.net/msg20607.html>
--
kind regards,
On 18/07/17 22:55, Farkas Levente wrote:
> On 07/18/2017 10:03 PM, David Sommerseth wrote:
>> On 18/07/17 17:50, Farkas Levente wrote:
>>> On 07/18/2017 03:55 PM, Jaroslav Reznik wrote:
>>>> This will result in the following:
>>>> * OpenVPN 2.4 based cli
On 20/07/17 09:46, Farkas Levente wrote:
> On 07/20/2017 02:09 AM, David Sommerseth wrote:
>> On 18/07/17 22:55, Farkas Levente wrote:
>>> On 07/18/2017 10:03 PM, David Sommerseth wrote:
>>>> On 18/07/17 17:50, Farkas Levente wrote:
>>>>> On 07/18/2017
On 20/07/17 13:55, Alexander Ploumistos wrote:
> On Thu, Jul 20, 2017 at 2:21 PM, David Sommerseth wrote:
>> I rather prefer to have this change in Fedora _now_ in a _planned_
>> release where this can be tested out before the final F27 is released.
>
> I modified the unit
a unified .spec file is
really not worth the efforts in the long run IMO.
Once the RPM build tools and packaging guidelines is unified across all
RPM based distributions you will find it reasonable to unify the .spec
files.
--
kind regards,
David Sommerseth
___
s,
rather that the pace gets improved and it will come back again in
stronger and more solid during a future RHEL 8 release.
--
kind regards,
David Sommerseth
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
only gnupg2. That said, I don't know how broken my build is (all
I know is that it works well enough for my printer, including network
scan). But for all I know, it might be it is the GUI tools which
depends on the gnupg stuff.
--
kind regards,
David Sommerseth
ing with root
privileges for tunnel setup. All the session management and user
front-ends will run completely unprivileged.
But if these scenarios are reasonable arguments for having a fixed
uid/gid, I do not currently know. The OpenVPN source code itself
is not tied to any specific uid/
On 02/10/17 19:33, Colin Walters wrote:
> On Mon, Oct 2, 2017, at 10:56 AM, David Sommerseth wrote:
>
>>"diag" : "Invocation of useradd without specifying a
>> UID; this may be OK, because /usr/share/doc/setup/uidgid defines no UID for
>> o
eject doing verification during install if the key is revoked.
> My personal worry is that old keys may get compromised over time, so it
> is a very good practice to regularly "disable" old keys.
+1
--
kind regards,
David Sommerseth
signature.asc
Description: OpenPGP digital signature
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
ly, what is the best approach to resolve this?
--
kind regards,
David Sommerseth
signature.asc
Description: OpenPGP digital signature
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fed
On 27/01/2022 15:35, Neal Gompa wrote:
On Thu, Jan 27, 2022 at 9:33 AM David Sommerseth wrote:
Hi,
I've hit a challenge I've not been able to figure out properly. I'm
putting together a Fedora Copr repo which should cover most the various
distros supported via Copr- Cent
Stream?
To be clear, to me there is a difference between EPEL builds (targetting
the traditional CentOS/RHEL distros)
and CentOS Stream. But again, I
might have misunderstood these concepts.
--
kind regards,
David Sommerseth
signature.asc
Description: OpenPGP digital signature
overseeing the
DCO development.
[0]
<https://community.openvpn.net/openvpn/wiki/GettingHelp#Developersupport>
--
kind regards,
David Sommerseth
OpenVPN Inc
signature.asc
Description: OpenPGP digital signature
___
devel mailing list -- devel@li
On 03/02/2022 05:52, Demi Marie Obenour wrote:
On 2/2/22 13:34, David Sommerseth wrote:
Hi,
An OpenVPN colleague of me, Antonio Quartulli (on Cc), has been working
on a kernel acceleration module for OpenVPN for quite some time. We
call this OpenVPN Data Channel Offload (DCO). This moves
com/OpenVPN/openvpn/blob/dco/README.dco.md#limitations-by-design>
--
kind regards,
David Sommerseth
signature.asc
Description: OpenPGP digital signature
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to de
On 04/02/2022 15:55, Fabio Valentini wrote:
On Fri, Feb 4, 2022 at 11:04 AM David Sommerseth wrote:
OpenVPN 2.6 and the openvpn-dco Copr builds should also work even if
kmod-ovpn-dco is not available. And we will provide and support the
kmod-ovpn-dco via the openvpn3 Copr repository until we
On 04/02/2022 15:53, Vitaly Zaitsev via devel wrote:
On 04/02/2022 11:03, David Sommerseth wrote:
We plan to release OpenVPN 2.6 later this year, which will be DCO
capable. This will be available in the existing Fedora repositories, as
well as Fedora Copr for releases (like EPEL 7 and 8) where
[bouncing this msg, as Antonio is not subscribed to this devel list]
Hi,
On 04/02/2022 15:35, David Sommerseth wrote:
On 04/02/2022 15:09, Neal Becker wrote:
Does this modified openvpn support all the same features/options as the
stable release version?
Almost. I recommend to have a look
me. A more heterogeneous environment might bring in bigger challenges.
--
kind regards,
David Sommerseth
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https
c++?
c) Which other traps may I be facing using a devtoolset for EPEL-7 builds?
--
kin
d regards,
David Sommerseth
signature.asc
Description: OpenPGP digital signature
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send
Beasley
Thanks a lot! I adopted a few tricks from there, and seems to build
great. Will run more testing on the binaries, but hopefully nothing
unexpected will be found.
--
kind regards,
David Sommerseth
signature.asc
Description: OpenPGP digital signature
red a business model for a subscription
service.
--
kind regards,
David Sommerseth
signature.asc
Description: OpenPGP digital signature
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
ook something like
-
Fedora
Recovery options
|`- Fedora (older kernel, 4.13.0-103)
|`- Fedora (older kernel, 4.14.5-300)
|`- Fedora (older kernel, 4.15.3-304)
\-- System recover mode (expert)
-
forward porting fixes for issues are always more convenient than
backwards porting them. Especially when writing new code and
features for a project.
--
kind regards,
David Sommerseth
___
devel mailing list -- devel@lists.fedoraproject.org
ot doesn't get wiped on errors and
that you don't have to dig deep into the /var/lib/mock directories to
find the source location
For me, this is where fedpkg local excels over mock build
--
kind regards,
David Sommerseth
___
devel mailing
e.com/openvpn-devel@lists.sourceforge.net/msg20607.html>
[2] <https://github.com/jonathanio/update-systemd-resolved>
--
kind regards,
David Sommerseth
OpenVPN Inc
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-l
e we're getting ready with a stable release, I want to submit the
Copr packaging to mainline Fedora.
But do read the quick-start part in [0], as OpenVPN 3 Linux is designed
very differently from OpenVPN 2.x ... and it tries to have a user
interface which is more end-user friendly than
On 25/02/2021 16:02, Dan Williams wrote:
On Thu, 2021-02-25 at 11:57 +0100, David Sommerseth wrote:
[...snip...]
* NetworkManger and OpenVPN
Outside of that, OpenVPN via NetworkManager will be a different beast
to
tackle which we have not yet dug into from the OpenVPN project side.
From
OpenVPN 2.5
release for distros shipping OpenVPN 2.4 in the main repos:
<https://copr.fedorainfracloud.org/coprs/dsommers/openvpn-release/build/2143551/>
--
kind regards,
David Sommerseth
OpenVPN Inc
___
devel mailing list -- devel@lists.fedoraproje
9646-openvpn3/>
--
kind regards,
David Sommerseth
OpenVPN Inc
___
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
On 14/07/2021 11:55, Miro Hrončok wrote:
On 14. 07. 21 11:49, David Sommerseth wrote:
Hi,
So I'm running some builds for the openvpn3-linux project on Fedora Rawhide
... And we have this little line in configure.ac:
AM_PATH_PYTHON([3.5],, [:])
When ./configure runs, it re
On 08/01/2025 11:04, Miro Hrončok wrote:
On 08. 01. 25 10:27, Daniel P. Berrangé wrote:
On Wed, Jan 08, 2025 at 09:01:33AM -, Hong Xu wrote:
This email follows week 0.step 3 in the nonresponsive
maintainer page:
https://docs.fedoraproject.org/en-US/fesco/Policy_for_nonresponsive_package_ma
in EPEL, as it makes the
scripting so much simpler and easier than what GnuPG/gpg could ever do.
But it was just real a smack in the face to starting to receive lots of
empty mails over the weekend once again after having hit the same issue
just week
1 - 100 of 102 matches
Mail list logo
