[Bug 1698704] New: perl-Cache-FastMmap-1.48 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1698704

Bug ID: 1698704
   Summary: perl-Cache-FastMmap-1.48 is available
   Product: Fedora
   Version: rawhide
Status: NEW
 Component: perl-Cache-FastMmap
  Keywords: FutureFeature, Triaged
  Assignee: jpazdzi...@redhat.com
  Reporter: upstream-release-monitor...@fedoraproject.org
QA Contact: extras...@fedoraproject.org
CC: iarn...@gmail.com, jpazdzi...@redhat.com,
perl-devel@lists.fedoraproject.org
  Target Milestone: ---
Classification: Fedora



Latest upstream release: 1.48
Current version/release in rawhide: 1.47-4.fc30
URL: http://search.cpan.org/dist/Cache-FastMmap/

Please consult the package updates policy before you issue an update to a
stable branch: https://fedoraproject.org/wiki/Updates_Policy

More information about the service that created this bug can be found at:
https://fedoraproject.org/wiki/Upstream_release_monitoring

Please keep in mind that with any upstream change, there may also be packaging
changes that need to be made. Specifically, please remember that it is your
responsibility to review the new version to ensure that the licensing is still
correct and that no non-free or legally problematic items have been added
upstream.

Based on the information from anitya: 
https://release-monitoring.org/project/6745/

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org

[389-devel] 389 DS nightly 2019-04-11 - 93% PASS

[vashirov]

https://fedorapeople.org/groups/389ds/ci/nightly/2019/04/11/report-389-ds-base-1.4.1.2-20190410git51eb5b2.fc29.x86_64.html
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/389-devel@lists.fedoraproject.org

Re: Basic graphics mode / 'nomodeset' testing request, round 2

[Richard Shaw]

On Wed, Apr 10, 2019 at 8:40 PM Adam Williamson 
wrote:

> On Wed, 2019-04-10 at 19:00 -0500, Richard Shaw wrote:
> > Tried on my Gigabyte AM4 X370 w/ AMD Ryzen 2600 and Nvidia GT1050
> >
> > I got to GDM just fine but there was some weird jerkiness when I moused
> > over the "Try Fedora / Install" buttons but not when moving the mouse
> > cursor over the desktop area. I coped dmesg and journalctl to a separate
> > machine if it's needed.
>
> I think you're the first person to say it worked, so actually yeah, I
> would like to see those logs :) Can you throw them up somewhere we can
> look at them? Thanks!
>

https://hobbes1069.fedorapeople.org/dmesg.log
https://hobbes1069.fedorapeople.org/journalctl.log

Thanks,
Richard
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: Basic graphics mode / 'nomodeset' testing request, round 2

[Adam Williamson]

On Wed, 2019-04-10 at 19:00 -0500, Richard Shaw wrote:
> Tried on my Gigabyte AM4 X370 w/ AMD Ryzen 2600 and Nvidia GT1050
> 
> I got to GDM just fine but there was some weird jerkiness when I moused
> over the "Try Fedora / Install" buttons but not when moving the mouse
> cursor over the desktop area. I coped dmesg and journalctl to a separate
> machine if it's needed.

I think you're the first person to say it worked, so actually yeah, I
would like to see those logs :) Can you throw them up somewhere we can
look at them? Thanks!
-- 
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: Basic graphics mode / 'nomodeset' testing request, round 2

[Richard Shaw]

Tried on my Gigabyte AM4 X370 w/ AMD Ryzen 2600 and Nvidia GT1050

I got to GDM just fine but there was some weird jerkiness when I moused
over the "Try Fedora / Install" buttons but not when moving the mouse
cursor over the desktop area. I coped dmesg and journalctl to a separate
machine if it's needed.

Thanks,
Richard
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: dlib update

[Luya Tshimbalanga]

On 2019-04-10 8:36 a.m., Stephen John Smoogen wrote:
>
>
>
>
> Please try it again, and if it doesn't work please do the following:
>
> curl -O https://puiterwijk.fedorapeople.org/fedpkg_new-sources.sh
>
> run the command with the upload and paste the output and also a
> `klist` as some of the problems have been people not having kerberos
> tickets and others with the command.
>
>
>
Here is the attached output including the "klist" command result.


Luya

sh fedpkg_new-sources.sh rpms/dlib dlib-19.17.tar.bz2 
Checking if dlib-19.17.tar.bz2 exists...
  % Total% Received % Xferd  Average Speed   TimeTime Time  Current
 Dload  Upload   Total   SpentLeft  Speed
  0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 0*   Trying 209.132.181.16...
* TCP_NODELAY set
* Connected to src.fedoraproject.org (209.132.181.16) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/pki/tls/certs/ca-bundle.crt
  CApath: none
} [5 bytes data]
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
} [512 bytes data]
* TLSv1.3 (IN), TLS handshake, Server hello (2):
{ [80 bytes data]
* TLSv1.2 (IN), TLS handshake, Certificate (11):
{ [2862 bytes data]
* TLSv1.2 (IN), TLS handshake, Server key exchange (12):
{ [556 bytes data]
* TLSv1.2 (IN), TLS handshake, Server finished (14):
{ [4 bytes data]
* TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
} [37 bytes data]
* TLSv1.2 (OUT), TLS change cipher, Change cipher spec (1):
} [1 bytes data]
* TLSv1.2 (OUT), TLS handshake, Finished (20):
} [16 bytes data]
* TLSv1.2 (IN), TLS handshake, Finished (20):
{ [16 bytes data]
* SSL connection using TLSv1.2 / ECDHE-RSA-AES128-GCM-SHA256
* ALPN, server accepted to use http/1.1
* Server certificate:
*  subject: C=US; ST=North Carolina; L=Raleigh; O=Red Hat Inc.; CN=*.fedoraproject.org
*  start date: Feb  1 00:00:00 2017 GMT
*  expire date: May  1 12:00:00 2020 GMT
*  subjectAltName: host "src.fedoraproject.org" matched cert's "*.fedoraproject.org"
*  issuer: C=US; O=DigiCert Inc; OU=www.digicert.com; CN=DigiCert SHA2 High Assurance Server CA
*  SSL certificate verify ok.
} [5 bytes data]
> POST /repo/pkgs/upload.cgi HTTP/1.1
> Host: src.fedoraproject.org
> User-Agent: curl/7.64.0
> Accept: */*
> Content-Length: 593
> Content-Type: multipart/form-data; boundary=0dd1cf000ccc23cd
> 
} [5 bytes data]
< HTTP/1.1 401 Unauthorized
< Date: Wed, 10 Apr 2019 23:48:36 GMT
< Server: Apache/2.4.39 (Fedora)
< Strict-Transport-Security: max-age=31536000; includeSubDomains; preload
< X-Frame-Options: SAMEORIGIN
< X-Xss-Protection: 1; mode=block
< X-Content-Type-Options: nosniff
< Referrer-Policy: same-origin
[24524] 1554940125.952528: ccselect module realm chose cache KCM:1000:39355 with client principal l...@fedoraproject.org for server principal HTTP/src.fedoraproject@fedoraproject.org
[24524] 1554940126.4280: Getting credentials l...@fedoraproject.org -> HTTP/src.fedoraproject@fedoraproject.org using ccache KCM:1000:39355
[24524] 1554940126.4281: Retrieving l...@fedoraproject.org -> HTTP/src.fedoraproject@fedoraproject.org from KCM:1000:39355 with result: 0/Success
[24524] 1554940126.4283: Creating authenticator for l...@fedoraproject.org -> HTTP/src.fedoraproject@fedoraproject.org, seqnum 774297883, subkey aes256-cts/ECA6, session key aes256-cts/7C54
< WWW-Authenticate: Negotiate
< Content-Length: 469
< Content-Type: text/html; charset=iso-8859-1
* HTTP error before end of send, stop sending
< 
 55  10620 0  100   593  0 55  0:00:10  0:00:10 --:--:--55
* Closing connection 0
* Issue another request to this URL: 'https://src.fedoraproject.org/repo/pkgs/upload.cgi'
* Hostname src.fedoraproject.org was found in DNS cache
*   Trying 209.132.181.16...
* TCP_NODELAY set
* Connected to src.fedoraproject.org (209.132.181.16) port 443 (#1)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/pki/tls/certs/ca-bundle.crt
  CApath: none
} [5 bytes data]
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
} [512 bytes data]
* TLSv1.3 (IN), TLS handshake, Server hello (2):
{ [80 bytes data]
* TLSv1.2 (IN), TLS handshake, Certificate (11):
{ [2862 bytes data]
* TLSv1.2 (IN), TLS handshake, Server key exchange (12):
{ [556 bytes data]
* TLSv1.2 (IN), TLS handshake, Server finished (14):
{ [4 bytes data]
* TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
} [37 bytes data]
* TLSv1.2 (OUT), TLS change cipher, Change cipher spec (1):
} [1 bytes data]
* TLSv1.2 (OUT), TLS handshake, Finished (20):
} [16 bytes data]
  0 00 00 0  0  0 --:--:--  0:00:10 --:--:-- 0* TLSv1.2 (IN), TLS handshake, Finished (20):
{ [16 bytes data]
* SSL connection using TLSv1.2 / ECDHE-RSA-AES128-GCM-SHA256
* ALPN, server accepted to use http/1.1
* Server certificate:
*  subject: C=US; ST=North Carolina; 

Schedule for Thursday's FPC Meeting (2019-04-11 16:00 UTC)

[James Antill]

Following is the list of topics that will be discussed in the FPC
meeting Thursday at 2019-04-11 16:00 UTC in #fedora-meeting-1 on 
irc.freenode.net.

 Local time information (via. uitime):


= Day: Thursday ==
2019-04-11 09:00 PDT  US/Pacific
2019-04-11 12:00 EDT  --> US/Eastern <--
2019-04-11 16:00 UTC  UTC   
2019-04-11 17:00 BST  Europe/London 
2019-04-11 18:00 CEST Europe/Berlin 
2019-04-11 18:00 CEST Europe/Paris  
2019-04-11 21:30 IST  Asia/Calcutta 
 New Day: Friday -
2019-04-12 00:00 HKT  Asia/Hong_Kong
2019-04-12 00:00 +08  Asia/Singapore
2019-04-12 01:00 JST  Asia/Tokyo
2019-04-12 02:00 AEST Australia/Brisbane


 Links to all tickets below can be found at: 

https://pagure.io/packaging-committee/issues?status=Open=meeting

= Followups =

#topic #845 Wiki deprecation status
.fpc 845
https://pagure.io/packaging-committee/issue/845

#topic #859 Scriptlet to replace a directory: try delete first? 
.fpc 859
https://pagure.io/packaging-committee/issue/859

= New business =

#topic #876 Mass Python 2 Package Removal - policies and exceptions  
.fpc 876
https://pagure.io/packaging-committee/issue/876

#topic #878 Package Naming Guildelines for lua packages  
.fpc 878
https://pagure.io/packaging-committee/issue/878

= Open Floor = 

 For more complete details, please visit each individual ticket.  The
report of the agenda items can be found at:

https://pagure.io/packaging-committee/issues?status=Open=meeting

 If you would like to add something to this agenda, you can:
  * Reply to this e-mail
  * File a new ticket at: https://pagure.io/packaging-committee
  * E-mail me directly
  * Bring it up at the end of the meeting, during the open floor topic. Note
that added topics may be deferred until the following meeting.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: Can we maybe reduce the set of packages we install by default a bit?

[Japheth Cleaver]

On 4/10/2019 4:10 AM, Brian (bex) Exelbierd wrote:

On Tue, Apr 9, 2019 at 8:40 PM Japheth Cleaver  wrote:

Is this really worth the effort? cronie in F30 is a 103K package, and a
decent chunk of that might be the ChangeLog. crontabs is all of 18K,
which is 95% the GPL and the RPM header. It seems like a very small
price to pay for something everyone is going to assume will be on any
*nix-compatible system of note.

I read, possibly misread, the original comment as being about the
number of "unneeded" things in the install, not necessarily the weight
of the specific packages.  What I think we are hearing from
containers, OSTree, etc. is that there is a group of people that wants
their systems more minimal with less unnecessary stuff.


*snip*


This seems to go back to who is the primary target audience for our
Workstation edition and what do they want/expect.  Then we can
document the changes and socialize them over a few releases so that
other users can get to where they want to be.  Basically "extra" isn't
what no one wants, its what our defined target doesn't want/expect.


Although this was originally posted about Workstation, I can virtually 
guarantee that a solution accepted for implementation would not be 
"Remove cron in %post," thus this really comes about as removing it as a 
default install pretty much everywhere. Of course, things like 
OSTree/atomic, containers, and micro-environments where every byte 
counts are likely to be bypassing typical installation mechanisms 
regardless to fine-tune what's delivered -- eg, removing documentation, 
etc in docker kickstart %post, or re-implementing parts of RPM to begin 
with.


Reducing the Minimal size is, in general, good, but it's possible to go 
too far, and I think that's the case with low-level, *nix wide tools 
like this. I'm reminded of the time someone thought tar needed to go 
too: https://bugzilla.redhat.com/show_bug.cgi?id=1409920


One might make the case for a removal from @core -- *maybe* -- but 
definitely not @base.




Lastly, taking a position on some of this, for example, removing cron,
is a form of opinionation that calls back to our roots of innovating
in the OS space.  We would be saying, we recognize this is the way we
did things X years ago, but there are new ways and processes and we
see value in those.  If we can't remove these things, then we are
being a good distribution by pointing out where solutions that claim
to fix something have fallen short so that those upstreams can make
decisions about what to do.


But what, exactly, has cron fallen short in? I'm reminded of that old 
testimonial tag line for the similarly named, but unrelated, utility 
cronolog: "cronolog kicks ass in every conceivable way in which a 
utility like cronolog can kick ass." ( 
http://web.archive.org/web/20090627031834/http://cronolog.org/ ) There 
are other launching mechanisms, sure... I've worked on one of them, but 
that doesn't mean there's anything wrong with cron, or /etc/cron.*/ 
directories.


More directly, I'm old enough to remember when we were assured that 
systemd's timers were not "to be in competition here" with cron, and and 
it was promised to "make sure that cron is advertised as a good solution 
for people who just want to queue a simple cronjob." With all the 
discussion of ease-of-use and discoverability, removing the "good 
solution" mechanism for users in favor of something requiring a package 
install doesn't seem to be a great example of that. 
https://lists.fedoraproject.org/pipermail/devel/2014-March/196293.html




The last thing I'd want to have to deal with is solving for a missing
/etc/cron.* because someone forgot to click a checkbox somewhere or
didn't call it out in kickstart.

Yes, but I also don't want to deal with a security fix in cron when I
didn't want it to begin with.  Adding software the user doesn't want
to have it as assumed for other users is always a trade-off.


True, but - as written elsewhere - that can be taken to a logical 
extreme, both via removal of simple, auditable utilities and shell 
scripts, and eventual giant replacements.


-jc
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: Basic graphics mode / 'nomodeset' testing request, round 2

[Lukas Ruzicka]

I have a no boot, too. Reported in the Bugzilla.
L.

On Wed, Apr 10, 2019 at 6:41 PM Geoffrey Marr  wrote:

> Have tried two machines so far, a MacBook
>
> 02:00.0 VGA compatible controller: Intel Corporation Mobile GM965/GL960
> Integrated Graphics Controller (primary) (rev 03)
>
> and a Dell Precision M4600 with:
>
> 01:00.0 VGA compatible controller: NVIDIA Corporation GF106GLM [Quadro
> 2000M] (rev a1)
>
> The MacBook has strange keybindings between the Command/Ctrl/Alt/Function
> keys and I can't for the life of me figure out how to register a
> "Ctrl-Alt-F3", so I can't say for sure if the error is in the log, but it's
> definitely not booting. The Dell however is showing the same error, the
> "(EE) Cannot run in framebuffer mode. Please specify busIDs for all
> framebuffer devices" and likewise not booting any further. I did a search
> through the logs for what Kamil is seeing in the second message, but none
> of those lines were found, only the original error. If I can get this
> MacBook into a terminal, I'll post what it says too.
>
> Geoff Marr
> IRC: coremodule
>
>
> On Wed, Apr 10, 2019 at 9:28 AM Kamil Paral  wrote:
>
>> On Wed, Apr 10, 2019 at 3:21 PM Kamil Paral  wrote:
>>
>>> Then I tried with Thinkpad T450s. I had to boot in UEFI with CSM on,
>>> because CSM off or even SecureBoot on make the image unbootable (I'll
>>> report a separate bug about that).
>>>
>>
>> https://bugzilla.redhat.com/show_bug.cgi?id=1698550
>>
>> ___
>> test mailing list -- t...@lists.fedoraproject.org
>> To unsubscribe send an email to test-le...@lists.fedoraproject.org
>> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
>> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>> List Archives:
>> https://lists.fedoraproject.org/archives/list/t...@lists.fedoraproject.org
>>
> ___
> test mailing list -- t...@lists.fedoraproject.org
> To unsubscribe send an email to test-le...@lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/t...@lists.fedoraproject.org
>


-- 

Lukáš Růžička

FEDORA QE, RHCE

Red Hat



Purkyňova 115

612 45 Brno - Královo Pole

lruzi...@redhat.com
TRIED AND PERSONALLY TESTED, ERGO TRUSTED. 
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: vanishing abrt logs

[jfilak]

> I think abrt should figure out if the crashing binary is part of





Would it be an option to create your own configuration for libreport?

It is much simpler and robust to deliver a config tailored for your


packages than trying to generalize the task and define a global policy




Example:




cat >/etc/libreport/events.d/my_system_service.conf < my_system_service.log

EOF




> Could we have a per-service switch that says 





Unfortunately, I am not sure we can say that a coredump file

never contains any security sensitive data. For example, it contains

a copy of /proc/[pid]/environ and if not cleared and  an admin has

a strange idea to export a crazy stuff, we are in trouble.







Jakub


-- Původní e-mail --
Od: Zbigniew Jędrzejewski-Szmek 
Komu: Development discussions related to Fedora 
Datum: 9. 4. 2019 9:04:48
Předmět: Re: vanishing abrt logs
"On Mon, Apr 08, 2019 at 02:21:47PM +0200, jfi...@fedoraproject.org wrote:
> I agree, but the file /proc/meminfo is not present, right?
> And yes, the abrt thing just reads the data from journal and
>
> stores them on filesystem to be able to upload them to Bugzilla.
>
>
>
>
>
> Regarding the missing logs, the journal log lines should
>
> be extracted by this thing:
>
> https://github.com/abrt/abrt/blob/master/src/plugins/ccpp_event.conf#L25
> (https://github.com/abrt/abrt/blob/master/src/plugins/ccpp_event.conf#L25)

>
> which is a little bit complex, so no wonder if it is broken

Thanks for the link. That code boils down to
"journalctl -q -b --since=-3m --system -n 99 _COMM="$base_executable" 
and for systemd services this is very underwhelming, because it doesn't 
use the information that the process is part of service, and all logs
from that service are relevant, e.g. when it launches a second
executable or switches uid.

I think abrt should figure out if the crashing binary is part of a
system service, and switch to a log collection mode that is more like
'journalctl -u' in this case. Also, don't limit the messages to just 3
minutes or 99 messages.

> (I am just not sure why the abrt test suite is not failing though).
>
> Regarding the core files, I was under the impression that
> the core files can be attached only if the reporter wants to attach it.
> IOW the core files were never attached automatically (due to security 
> issues).

Could we have a per-service switch that says "this service never has
private information, make the coredump file collection opt-out"?
For example, we get a number of reports for systemd-logind, and by
design it never has any private user data or keys. The user interface
could be simplified. Similarly for hwrngd, and probably many others.

> If you need some information that is relevant only to your packages,
> we can work together to create a new abrt configuration which will
> gather that information for your packages
> (for example, dnf ships its own abrt configuration).

Can you point me to it? rpm -ql $(rpm -qa|grep dnf)|grep abrt doesn't
yield anything.

Zbyszek
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.
fedoraproject.org
"

___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Node.js packages now provide v8-devel

[Stephen Gallagher]

I've just submitted nodejs-10.15.3-1 into Bodhi and buildroot
overrides for F29 and F30 (it was built for Rawhide last night).

This new build provides two new subpackages:
 * `nodejs-libs` provides libnode.so which is ABI-compatible with
libv8_libbase.so.6 and libv8_libplatform.so.6, for which it provides
compatibility symlinks.
* `v8-devel` provides the appropriate C headers to build against v8 as libnode.

Thank you very much to Elliot Sales de Andrade who did most of the
work to make this happen. This should now make it possible to build
and provide R-V8 for Fedora.

For right now, we're only providing v8-devel from the Node.js 10.x
release. Once Node.js 12.x is released at the end of the month, I will
probably package that up and make it the default for Fedora 31 (as
well as providing a modular version for F29 and F30).
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: F30 live images still contain dbus-daemon package, anaconda-core requires it ?

[Adam Williamson]

On Wed, 2019-04-10 at 11:03 -0600, Chris Murphy wrote:
> On Wed, Apr 10, 2019 at 3:07 AM Hans de Goede  wrote:
> > Hi All,
> > 
> > I just noticed that Fedora-Workstation-Live-x86_64-30-20190408.n.0.iso still
> > contains the dbus-daemon package even though we are using dbus-broker now.
> > 
> > I've tried to rpm -e it and it for some reason it is required by
> > anaconda-core which seems weird.
> > 
> > So should I file a bug against anaconda for this? I guess it is too late
> > to fix this for F30?
> 
> Anaconda. Freeze is next week.

It's not a bug. All is as intended.

https://bugzilla.redhat.com/show_bug.cgi?id=1658739#c9
-- 
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: F30 live images still contain dbus-daemon package, anaconda-core requires it ?

[Martin Kolman]

On Wed, 2019-04-10 at 11:07 +0200, Hans de Goede wrote:
> Hi All,
> 
> I just noticed that Fedora-Workstation-Live-x86_64-30-20190408.n.0.iso still
> contains the dbus-daemon package even though we are using dbus-broker now.
> 
> I've tried to rpm -e it and it for some reason it is required by
> anaconda-core which seems weird.
This is by design - we decided to continue using dbus-deamon for the time being 
as dbus-broker required too much extra work on our side for basically no extra 
benefits.

Adding Jirka Konecny who handled this on our side to CC.

> 
> So should I file a bug against anaconda for this? I guess it is too late
> to fix this for F30?
> 
> Regards,
> 
> Hans
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: F30 live images still contain dbus-daemon package, anaconda-core requires it ?

[Chris Murphy]

On Wed, Apr 10, 2019 at 3:07 AM Hans de Goede  wrote:
>
> Hi All,
>
> I just noticed that Fedora-Workstation-Live-x86_64-30-20190408.n.0.iso still
> contains the dbus-daemon package even though we are using dbus-broker now.
>
> I've tried to rpm -e it and it for some reason it is required by
> anaconda-core which seems weird.
>
> So should I file a bug against anaconda for this? I guess it is too late
> to fix this for F30?

Anaconda. Freeze is next week.

-- 
Chris Murphy
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: Basic graphics mode / 'nomodeset' testing request, round 2

[Geoffrey Marr]

Have tried two machines so far, a MacBook

02:00.0 VGA compatible controller: Intel Corporation Mobile GM965/GL960
Integrated Graphics Controller (primary) (rev 03)

and a Dell Precision M4600 with:

01:00.0 VGA compatible controller: NVIDIA Corporation GF106GLM [Quadro
2000M] (rev a1)

The MacBook has strange keybindings between the Command/Ctrl/Alt/Function
keys and I can't for the life of me figure out how to register a
"Ctrl-Alt-F3", so I can't say for sure if the error is in the log, but it's
definitely not booting. The Dell however is showing the same error, the
"(EE) Cannot run in framebuffer mode. Please specify busIDs for all
framebuffer devices" and likewise not booting any further. I did a search
through the logs for what Kamil is seeing in the second message, but none
of those lines were found, only the original error. If I can get this
MacBook into a terminal, I'll post what it says too.

Geoff Marr
IRC: coremodule


On Wed, Apr 10, 2019 at 9:28 AM Kamil Paral  wrote:

> On Wed, Apr 10, 2019 at 3:21 PM Kamil Paral  wrote:
>
>> Then I tried with Thinkpad T450s. I had to boot in UEFI with CSM on,
>> because CSM off or even SecureBoot on make the image unbootable (I'll
>> report a separate bug about that).
>>
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1698550
>
> ___
> test mailing list -- t...@lists.fedoraproject.org
> To unsubscribe send an email to test-le...@lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/t...@lists.fedoraproject.org
>
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: dlib update

[Stephen John Smoogen]

On Wed, 10 Apr 2019 at 11:29, Luya Tshimbalanga 
wrote:

> On 2019-04-10 5:06 a.m., Dridi Boukelmoune wrote:
> >> From looking at it quickly, it seems like you've updated the .spec for
> >> version 19.17 but have only uploaded sources for 19.16. > > If he's not
> the maintainer he probably doesn't have the privileges to do so. > > Dridi
> > ___ > devel mailing list --
> devel@lists.fedoraproject.org > To unsubscribe send an email to
> devel-le...@lists.fedoraproject.org > Fedora Code of Conduct:
> https://getfedora.org/code-of-conduct.html > List Guidelines:
> https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives:
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
> Right as I attempted to do so:
>
> fedpkg new-sources dlib-19.17.tar.bz2
> Uploading: dlib-19.17.tar.bz2
> 
> 100.0%
> Could not execute new_sources: Fail to upload files. Server returns status
> 408
>

Please try it again, and if it doesn't work please do the following:

curl -O https://puiterwijk.fedorapeople.org/fedpkg_new-sources.sh

run the command with the upload and paste the output and also a `klist` as
some of the problems have been people not having kerberos tickets and
others with the command.




>
> Luya
>
>
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
>


-- 
Stephen J Smoogen.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: dlib update

[Luya Tshimbalanga]

On 2019-04-10 5:06 a.m., Dridi Boukelmoune wrote:
>> From looking at it quickly, it seems like you've updated the .spec for >> 
>> version 19.17 but have only uploaded sources for 19.16. > > If he's
not the maintainer he probably doesn't have the privileges to do so. > >
Dridi > ___ > devel mailing
list -- devel@lists.fedoraproject.org > To unsubscribe send an email to
devel-le...@lists.fedoraproject.org > Fedora Code of Conduct:
https://getfedora.org/code-of-conduct.html > List Guidelines:
https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Right as I attempted to do so:

fedpkg new-sources dlib-19.17.tar.bz2
Uploading: dlib-19.17.tar.bz2

100.0%
Could not execute new_sources: Fail to upload files. Server returns
status 408


Luya


___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: Basic graphics mode / 'nomodeset' testing request, round 2

[Kamil Paral]

On Wed, Apr 10, 2019 at 3:21 PM Kamil Paral  wrote:

> Then I tried with Thinkpad T450s. I had to boot in UEFI with CSM on,
> because CSM off or even SecureBoot on make the image unbootable (I'll
> report a separate bug about that).
>

https://bugzilla.redhat.com/show_bug.cgi?id=1698550
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: Could not execute import_srpm

[Kevin Fenzi]

On 4/9/19 6:26 PM, Jerry James wrote:
> On Tue, Apr 9, 2019 at 2:30 PM Kevin Fenzi  wrote:
>> We have had at least 3 reports of this today...
>> (upload causing 408 error).
>>
>> Can any of you folks seeing this:
>>
>> Run this script:
>> https://paste.fedoraproject.org/paste/tWt5LBT13-~d22wBpo38uQ/raw
>>
>> and send me the output?
> 
> I just had a failure to upload new sources for eclib, and ran this
> script.  The output is attached.

It seems you don't have a valid kerberos ticket here?

Can you do a kinit and try again?

kevin





signature.asc
Description: OpenPGP digital signature
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

[Bug 1697635] perl-Sereal-Encoder-4.006 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1697635

Fedora Update System  changed:

   What|Removed |Added

 Status|MODIFIED|ON_QA



--- Comment #9 from Fedora Update System  ---
perl-Sereal-Encoder-4.006-1.fc30 has been pushed to the Fedora 30 testing
repository. If problems still persist, please make note of it in this bug
report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-2019-d5ce92c1b9

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org

[Bug 1697634] perl-Sereal-Decoder-4.006 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1697634



--- Comment #8 from Fedora Update System  ---
perl-Sereal-Decoder-4.006-1.fc30 has been pushed to the Fedora 30 testing
repository. If problems still persist, please make note of it in this bug
report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-2019-e03735d10d

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org

[Bug 1697630] perl-App-a2p-1.011 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1697630

Fedora Update System  changed:

   What|Removed |Added

 Status|MODIFIED|ON_QA



--- Comment #2 from Fedora Update System  ---
perl-App-a2p-1.011-1.fc30 has been pushed to the Fedora 30 testing repository.
If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-2019-d7bb240e1b

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org

Re: Can we maybe reduce the set of packages we install by default a bit?

[Brian (bex) Exelbierd]

On Wed, Apr 10, 2019 at 3:22 PM Michael Watters  wrote:
>
> You mean like systemd?  ;)

Given the origin of this thread, I tried not to go there.  However,
now that you've broached it, yes.  This :D.

systemd is a lot of things, but it also is the way forward we think
that our audience wants.  It has the adoption that shows that leaving
it out is bad, and in this specific cron example, not using its full
feature set is probably bad for our users and is poor of us as a
distro.

The more interesting set of cases is what our users want/need to be
successful.  For example, if we are targetting developers, should we
work on replacing some tools like `cat` with `bat` as it is code
aware.  This would be a HUGE undertaking, potentially, but could
potentially create an ease of use and experience that shows we
understand our market.

regards,

bex

>
> On 4/10/19 7:10 AM, Brian (bex) Exelbierd wrote:
> > Adding software the user doesn't want
> > to have it as assumed for other users is always a trade-off.
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org



-- 
Brian (bex) Exelbierd | bexel...@redhat.com | b...@pobox.com
Fedora Community Action & Impact Coordinator
@bexelbie | http://www.winglemeyer.org
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: Introduction for gaming packaging/maintaining

[Karsten Andreas Artz]

Hi Kamil,
personally I'd prefer containing the games on Flatpak to be more flexible and 
it can be provided for a hugh user base.
I hope the games I've suggested  now are mostly clones. Thus they might be 
included for Fedora.  The Dark Mod sounds an interesting game!  I've made a 
notice for your wish:) 

Cheers
 Andi



Am Mittwoch, 10. April 2019, 13:28:24 MESZ hat Kamil Paral 
 Folgendes geschrieben:  
 
 On Mon, Apr 8, 2019 at 7:34 PM Karsten Andreas Artz  
wrote:

Hi guys,
my name is Andi, 29 and I'm from Germany.  I'm using Fedora almost 2 years 
(Fedora 26). My programming skills are on Python, Java/Java Script, and C/C++. 
But acutally I prefer mostly Python hacking. I studied B.A. of Arts History, 
Archaeology and Cath.Theology. Besides this, I can speak a lot of languages: 
German, English, French, a bit Italian and Spanish. 

It would be glad starting contributing on Fedora as a maintainer. Therefore I 
hope to work on a small project soon.
I'm interested in games packaging, but I don't know where to start.


Hi Andi,
only opensource software can be part of Fedora, and there are not that many 
opensource games out there (which are not already packaged for Fedora), so it 
might be a bit difficult to find something suitable and interesting (but some 
of the OS clones might be a good idea). Additionally regarding games packaging, 
you can consider making flatpaks instead of RPMs and submitting them to Flathub 
[1]. Flathub can not only contain opensource games, but also freeware and 
free-to-play games (let's talk about Linux-native games at the moment, 
incorporating Wine into them would be another level of difficulty). For 
example, I'd personally love to see The Dark Mod [2] available at Flathub.
In Fedora you can also participate on packaging and maintaining game-related 
software, like emulators and launchers. Wine, Lutris and PLayOnLinux are the 
most visible ones, but then there are also lots of retro emulators, many of 
them not even in Fedora yet, I'd guess. So it depends on your experience and 
interests (both gaming and packaging). You could even participate in e.g. 
Lutris community in creating and maintaining scripts to allow easy installation 
of Windows and other platforms' games on Linux.
The Gaming SIG [3] might provide a better advice, this is just what I know.

[1] https://flathub.org
[2] http://www.thedarkmod.com[3] https://fedoraproject.org/wiki/SIGs/Games
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
  ___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: Basic graphics mode / 'nomodeset' testing request, round 2

[Kamil Paral]

On Tue, Apr 9, 2019 at 3:03 AM Adam Williamson 
wrote:

> Hi folks!
>
> A few weeks back we asked for testing of 'basic graphics mode' /
> nomodeset booting - the feedback from that was very helpful in
> establishing that we had a generic issue which dated back to Fedora 29,
> thanks a lot. We have now established more or less what that initial
> issue is, and work is ongoing to get it fixed entirely. However, it's
> already been fixed *partially*, and that revealed a subsequent bug.
>
> The initial bug is fixed for the case of UEFI native boots (it is not
> fixed for BIOS native boots yet). However, in testing, I and others
> found that several UEFI test systems still do not boot successfully to
> GDM, because they run into a *different* bug later:
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1693409
>
> This bug can be identified by the presence of the following string in
> the journal:
>
> "(EE) Cannot run in framebuffer mode. Please specify busIDsfor
> all framebuffer devices"
>
> (yes, with a bunch of spaces - but just the first part of the line is
> sufficient to identify the problem, I think).
>
> It would be great if folks with UEFI-capable systems could try booting
> a recent Fedora 30 Workstation live image on them, e.g. this one:
>
>
> https://kojipkgs.fedoraproject.org/compose/branched/Fedora-30-20190408.n.0/compose/Workstation/x86_64/iso/Fedora-Workstation-Live-x86_64-30-20190408.n.0.iso
>
> ensure you boot in UEFI mode. Please report back whether it works. If
> it doesn't work, please check the logs - you should be able to log into
> a console on tty3 (ctrl-alt-f3 to get there) as root with no password,
> then run 'journalctl -b' to see the logs - and report if that line is
> present or not. If it isn't, it'd be useful to know if some other error
> message is present.
>

Using the linked 20190408 image, I'm seeing this on my desktop PC with
Radeon 580 (booted with UEFI + basic graphics mode):

Apr 10 11:39:19 localhost gnome-shell[1730]: Failed to create backend: No
> GPUs found with udev
> Apr 10 11:39:19 localhost gnome-session[1631]: gnome-session-binary[1631]:
> WARNING: App 'org.gnome.Shell.desktop' exited with code 1
> Apr 10 11:39:19 localhost gnome-session-binary[1631]: WARNING: App
> 'org.gnome.Shell.desktop' exited with code 1
> Apr 10 11:39:19 localhost gnome-session-binary[1631]: Unrecoverable
> failure in required component org.gnome.Shell.desktop
>

The card is:

> 01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc.
> [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] [1002:67df]
> (rev e7)
>

So the error message is different, but the outcome is the same - a black
screen with a flashing cursor instead of GDM. Enabling integrated Intel
graphics in BIOS doesn't help (but I can't disable the AMD card in BIOS,
I'd have to pull it out physically, so both cards are visible to the
system).


Then I tried with Thinkpad T450s. I had to boot in UEFI with CSM on,
because CSM off or even SecureBoot on make the image unbootable (I'll
report a separate bug about that). With UEFI+CSM, I see exactly the same
error as before:

Apr 10 15:01:04 localhost gnome-shell[1773]: Failed to create backend: No
> GPUs found with udev
>

The card is:

> 00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics
> 5500 [8086:1616] (rev 09)
>


Finally I tried with Thinkpad T480s (here CSM=off and even SecureBoot=on
works fine). I see again the same error:

Apr 10 15:07:47 localhost gnome-shell[1806]: Failed to create backend: No
> GPUs found with udev
>

And I finally see even the error you mentioned (I have no idea why I
haven't seen it on other machines):

Apr 10 15:07:48 localhost /usr/libexec/gdm-x-session[1897]: (EE) Cannot run
> in framebuffer mode. Please specify busIDsfor all framebuffer
> devices
>

The card is:

> 00:02.0 VGA compatible controller [0300]: Intel Corporation UHD Graphics
> 620 [8086:5917] (rev 07)
>


So, for me, not a single machine where fallback graphics would work with
UEFI.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: Can we maybe reduce the set of packages we install by default a bit?

[Michael Watters]

You mean like systemd?  ;)

On 4/10/19 7:10 AM, Brian (bex) Exelbierd wrote:
> Adding software the user doesn't want
> to have it as assumed for other users is always a trade-off.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: Fork a 119MB pagure project to updating monitoring?

[Pierre-Yves Chibon]

On Wed, Apr 10, 2019 at 02:45:48PM +0200, Robert-André Mauchin wrote:
> On Wednesday, 10 April 2019 11:04:11 CEST Pierre-Yves Chibon wrote:
> > On Mon, Mar 25, 2019 at 02:55:23PM -0500, Richard Shaw wrote:
> > 
> > >Other than having it as a direct option in [1]src.fp.org I think being
> > >part of a special file in git would be next best.
> > 
> > 
> > In the recent releases pagure grew the possibility to have 3rd party
> > extensions
>  with their own URL endpoints and able to extend the current
> > database model to store extra information.
> > 
> > I've spent a little time using this feature to gain back support in pagure's
> > UI
>  to toggle the monitoring status.
> > 
> > Here is a small demo of how it looks like:
> > http://ambre.pingoured.fr/public/Screencast_pagure_distgit_anitya.webm
> > 
> > Basically, there would now be a button on the sidebar which would show the
> > current monitoring status and would allow project admins and pagure wide
> > admins
>  to update this setting.
> > 
> > Feedback most welcome :)
> > 
> > I'm going to clean up the code a little bit and open a PR on the
> > pagure-dist-git
>  project, reviews and suggestions welcome there as well.
> > 
> > 
> 
> Nice! But could it also come with an API endpoint to do this programatically?
> Like if I want to switch all my monitoring at once in a Python script.

That's how the button works, it calls on to the API endpoint, which is the one
of the tab you can see in the demo :)
The only thing is figuring out the discoverability of that this API endpoint
since it's not part of pagure itself.
For the moment it may end up being in the upstream doc only, I'll see if I can
find something better.


Pierre
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: Fork a 119MB pagure project to updating monitoring?

[Robert-André Mauchin]

On Wednesday, 10 April 2019 11:04:11 CEST Pierre-Yves Chibon wrote:
> On Mon, Mar 25, 2019 at 02:55:23PM -0500, Richard Shaw wrote:
> 
> >Other than having it as a direct option in [1]src.fp.org I think being
> >part of a special file in git would be next best.
> 
> 
> In the recent releases pagure grew the possibility to have 3rd party
> extensions
 with their own URL endpoints and able to extend the current
> database model to store extra information.
> 
> I've spent a little time using this feature to gain back support in pagure's
> UI
 to toggle the monitoring status.
> 
> Here is a small demo of how it looks like:
> http://ambre.pingoured.fr/public/Screencast_pagure_distgit_anitya.webm
> 
> Basically, there would now be a button on the sidebar which would show the
> current monitoring status and would allow project admins and pagure wide
> admins
 to update this setting.
> 
> Feedback most welcome :)
> 
> I'm going to clean up the code a little bit and open a PR on the
> pagure-dist-git
 project, reviews and suggestions welcome there as well.
> 
> 

Nice! But could it also come with an API endpoint to do this programatically?
Like if I want to switch all my monitoring at once in a Python script.

___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

How to fix dnf segmentation fault (zchunk metadata is re-enabled)

[Jonathan Dieter]

FESCo has given us the go-ahead to turn zchunk metadata on again[1] for
the F30 fedora repository after the librepo segmentation fault bug[2]
was fixed.  An updated librepo[3] was built a week ago and was pushed
to stable five days ago, so most beta users should have the new
version.

If you're using F30 and have librepo-1.9.6-1.fc30, please update to
librepo-1.9.6-2.fc30 as soon as possible!  If you don't, you will once
again get a segmentation fault when running dnf.

If you find yourself getting a segmentation fault when running dnf on a
system with librepo-1.9.6-1.fc30, you can temporarily work around it by
doing the following:

1. Edit /etc/dnf/dnf.conf and add the following line:

   zchunk=False

2. Run:
   dnf update librepo

   Verify that you got librepo-1.9.6-2.fc30 or later in the update

3. Remove the 'zchunk=False' line you added to /etc/dnf/dnf.conf

4. Run:
   dnf update

At this point, dnf should download the repository metadata without any
segmentation faults, and any further repository metadata downloads
should be significantly smaller.

Jonathan

 1. https://pagure.io/fesco/issue/2116
 2. 
https://lists.fedoraproject.org/archives/list/devel-annou...@lists.fedoraproject.org/thread/RHZ6V6MFVFAIJ6OEXZ5VL7BPPLHJE4GF/
 3. https://bodhi.fedoraproject.org/updates/FEDORA-2019-07c3e09858
___
devel-announce mailing list -- devel-annou...@lists.fedoraproject.org
To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel-annou...@lists.fedoraproject.org
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

How to fix dnf segmentation fault (zchunk metadata is re-enabled)

[Jonathan Dieter]

FESCo has given us the go-ahead to turn zchunk metadata on again[1] for
the F30 fedora repository after the librepo segmentation fault bug[2]
was fixed.  An updated librepo[3] was built a week ago and was pushed
to stable five days ago, so most beta users should have the new
version.

If you're using F30 and have librepo-1.9.6-1.fc30, please update to
librepo-1.9.6-2.fc30 as soon as possible!  If you don't, you will once
again get a segmentation fault when running dnf.

If you find yourself getting a segmentation fault when running dnf on a
system with librepo-1.9.6-1.fc30, you can temporarily work around it by
doing the following:

1. Edit /etc/dnf/dnf.conf and add the following line:

   zchunk=False

2. Run:
   dnf update librepo

   Verify that you got librepo-1.9.6-2.fc30 or later in the update

3. Remove the 'zchunk=False' line you added to /etc/dnf/dnf.conf

4. Run:
   dnf update

At this point, dnf should download the repository metadata without any
segmentation faults, and any further repository metadata downloads
should be significantly smaller.

Jonathan

 1. https://pagure.io/fesco/issue/2116
 2. 
https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/thread/RHZ6V6MFVFAIJ6OEXZ5VL7BPPLHJE4GF/
 3. https://bodhi.fedoraproject.org/updates/FEDORA-2019-07c3e09858
___
devel-announce mailing list -- devel-announce@lists.fedoraproject.org
To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org

Re: Anyone seeing udev failing to start in Rawhide?

[Richard W.M. Jones]

On Wed, Apr 10, 2019 at 02:17:43PM +0200, Lennart Poettering wrote:
> On Mi, 10.04.19 14:08, Vít Ondruch (vondr...@redhat.com) wrote:
> 
> > Just FTR, my Rawhide is working fine with
> > systemd-242~rc3-1.fc31.x86_64.
> 
> does adding a drop-in for the service unit with the following contents fix it?
> 
>  [Service]
>  RestrictSUIDSGID=no
>  ProtectHostname=no

To set expectations here, I don't think I'm going to have time to look
at this.  I've just finished rebuilding the machine and I don't want
to break it again because I need it for work.

Rich.

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
Fedora Windows cross-compiler. Compile Windows programs, test, and
build Windows installers. Over 100 libraries supported.
http://fedoraproject.org/wiki/MinGW
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: Anyone seeing udev failing to start in Rawhide?

[Lennart Poettering]

On Mi, 10.04.19 14:08, Vít Ondruch (vondr...@redhat.com) wrote:

> Just FTR, my Rawhide is working fine with
> systemd-242~rc3-1.fc31.x86_64.

does adding a drop-in for the service unit with the following contents fix it?

 [Service]
 RestrictSUIDSGID=no
 ProtectHostname=no

Lennart

--
Lennart Poettering, Berlin
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: dlib update

[Dridi Boukelmoune]

> From looking at it quickly, it seems like you've updated the .spec for
> version 19.17 but have only uploaded sources for 19.16.

If he's not the maintainer he probably doesn't have the privileges to do so.

Dridi
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: Anyone seeing udev failing to start in Rawhide?

[Vít Ondruch]

Just FTR, my Rawhide is working fine with systemd-242~rc3-1.fc31.x86_64.


Vít



Dne 10. 04. 19 v 10:50 Richard W.M. Jones napsal(a):
> Repeated errors on the console like this:
>
>  Starting udev Kernel Device Manager...
> [FAILED] Failed to start udev Kernel Device Manager.
> See 'systemctl status systemd-udevd.service' for details.
> [  OK  ] Stopped udev Kernel Device Manager.
>  Starting udev Kernel Device Manager...
> [FAILED] Failed to start udev Kernel Device Manager.
> See 'systemctl status systemd-udevd.service' for details.
>
> When I finally get to the emergency console the output from "systemctl
> status systemd-udevd.service" isn't actually any more helpful:
>
> ● systemd-udevd.service - udev Kernel Device Manager
>Loaded: loaded (/usr/lib/systemd/system/systemd-udevd.service; static; 
> vendor preset: disabled)
>Active: failed (Result: exit-code) since Wed 2019-04-10 09:43:21 BST; 3min 
> 41s ago
>  Docs: man:systemd-udevd.service(8)
>man:udev(7)
>   Process: 938 ExecStart=/usr/lib/systemd/systemd-udevd (code=exited, 
> status=226/NAMESPACE)
>  Main PID: 938 (code=exited, status=226/NAMESPACE)
>
> Apr 10 09:43:21 trick.home.annexia.org systemd[1]: Starting udev Kernel 
> Device Manager...
> Apr 10 09:43:21 trick.home.annexia.org systemd[1]: systemd-udevd.service: 
> Main process exited, code=exited, status=226/NAMESPACE
> Apr 10 09:43:21 trick.home.annexia.org systemd[1]: systemd-udevd.service: 
> Failed with result 'exit-code'.
> Apr 10 09:43:21 trick.home.annexia.org systemd[1]: Failed to start udev 
> Kernel Device Manager.
> Apr 10 09:43:21 trick.home.annexia.org systemd[1]: systemd-udevd.service: 
> Service has no hold-off time (RestartSec=0), scheduling restart.
> Apr 10 09:43:21 trick.home.annexia.org systemd[1]: systemd-udevd.service: 
> Scheduled restart job, restart counter is at 5.
> Apr 10 09:43:21 trick.home.annexia.org systemd[1]: Stopped udev Kernel Device 
> Manager.
> Apr 10 09:43:21 trick.home.annexia.org systemd[1]: systemd-udevd.service: 
> Start request repeated too quickly.
> Apr 10 09:43:21 trick.home.annexia.org systemd[1]: systemd-udevd.service: 
> Failed with result 'exit-code'.
> Apr 10 09:43:21 trick.home.annexia.org systemd[1]: Failed to start udev 
> Kernel Device Manager.
>
> The kernel is: 5.1.0-0.rc3.git3.1.fc31.x86_64
>
> It seems to be a udev problem because going back to kernel 5.0.0
> does not help ...
>
> Rich.
>
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: Can we maybe reduce the set of packages we install by default a bit?

[Martin Kolman]

On Tue, 2019-04-09 at 14:20 -0400, Neal Gompa wrote:
> On Tue, Apr 9, 2019 at 1:11 PM Adam Williamson
>  wrote:
> > On Tue, 2019-04-09 at 12:54 -0400, Stephen John Smoogen wrote:
> > > On Tue, 9 Apr 2019 at 12:07, Lennart Poettering 
> > > wrote:
> > > 
> > > > Heya,
> > > > 
> > > > today I installed the current Fedora 30 Workstation beta on my new
> > > > laptop. It was a bumpy ride, I must say (the partitioner (blivet?)
> > > > crashed five times or so on me, always kicking me out of anaconda
> > > > again, just because I wanted to undo something). But I don't really
> > > > want to discuss that. What I do want to discuss is this:
> > > > 
> > > > Can we maybe reduce the default set of packages a bit? In particular
> > > > the following ones I really don't think should be in our default
> > > > install:
> > > > 
> > > > 
> > > This is not the first time this has come up and I expect it won't be the
> > > last time.
> > > 
> > > I think the main reason they stick around is that the people who want them
> > > gone just show up right after a release, drop a bunch of requests, and 
> > > then
> > > go off to their own busy work. Then they come back a release later, don't
> > > see any change and either drop another email detailing things to be 
> > > dropped
> > > OR discouraged that no-one ever listens. The things that do get changed 
> > > and
> > > pulled out (or kept in) do so because people come in and work on scrubbing
> > > out the reasons and making sure the replacements are socialized in.
> > > 
> > > One of the things is that I am not sure any of these items
> > > 
> > > 
> > > 1. multipathd. On a workstation, uh?? I obviously have no multipath
> > > 
> > > 2. dmraid. Not quite as bad as multipathd as it is more likely to
> > > 
> > > I think these two are here because of the blivet you mentioned earlier.
> > > Advanced partitioning requires them to be there... and there do seem to be
> > > people who actually do expect both of those to work on their workstations
> > > when it was looked at to be removed in the past.
> > > 
> > > I do not know if the SIlverBlue does not have them on the other hand.
> > 
> > Basically, anything that's part of the install environment is going to
> > be present after a live install. That accounts for both of the above:
> > the installer supports multipath and dmraid storage devices, so the
> > relevant packages are part of the install environment, so they're part
> > of the lives, so they're installed by a live install.
> > 
> > This is kind of a limitation of the live deployment mechanism. In
> > theory a post-install stage could be added to strip things that were
> > only needed at install time, or that we can tell aren't actually needed
> > by the installed system, but this has never been done, though I recall
> > it being discussed at times.
> > 
> 
> I'd personally like to see some kind of post-install mechanism that
> could remove unneeded things
This is on the technical level doable as long as:
- RPM & DNF tooling on the image works
- you are only removing stuff
- the "recipe" what to remove needs to be maintained somewhere and kept current

>  or apply updates before rebooting into
> the new environment.
This on the other hand is a bit harder four a couple reasons:
- the current live installation does not need networking and this network is 
(IIRC) generally
  not setup, so you would need to make sure network is available at the time 
you attempt to do this
- unlike the live image that is always the same and passes quite some testing 
(both automated and manual)
  before it is declared fit for GA, update repos can change more or less at 
random, creating
  a miriad of combinations with the live image package set, some of them 
potentially wrong (file conflicts,
  broken deps, failing scriptlets)
- any errors due to updates might be harder to debug in the live environment 
than on installed system
- note that thisa is not the same as netins as you would be always taking a 
frozen package set and then aplying
  a bunch of ever changing updates on top of it VS installing a full system 
from latest packages on netinst
- while making the system up to date (and potentially more secure) this could 
make the live installation run
  quite a bit longer & taking ever longer the older the live image is
  (current live image just rsyncs the base filesystem content to the target, no 
need to run all the scriptlets and
   rpm machinery)


> That's something that Ubiquity, DrakX, Calamares,
> and YaST all do, and it's quite nice to have...
It's all possible in principle, but both remove & update is:
- extra code not useed on netinst that needs to be written, maintained & QAed
- will this be the same for all lives or different per spins vs workstation
- do the SIGs taking care of the Workstation live and other live spins actually 
want this ?

> 
> > > > 3. atd? Do we still need that? Do we have postinst scripts that need
> > > 
> > > 4. Similar crond. On my fresh install 

Re: Can we maybe reduce the set of packages we install by default a bit?

[Lennart Poettering]

On Mi, 10.04.19 08:16, Julen Landa Alustiza (ju...@zokormazo.info) wrote:

> I'm really interested on the livet crash, but I can't reproduce it with
> latest branched compose.
> Can you provide us with reproduction steps?

Urks, I don't remember. I think created an ESP part, two ext4
partitions, one encrypted swap and one encrypted btrfs or so, and then
changed my mind and flushed it all out with that button in the lower
right, and then it died on me. And then I did the same twice again it
it died again. But sorry, I didn't record the errors, it wasn't
particularly special though...

Lennart

--
Lennart Poettering, Berlin
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: Can we maybe reduce the set of packages we install by default a bit?

[Lennart Poettering]

On Di, 09.04.19 18:34, Chris Murphy (li...@colorremedies.com) wrote:

> > Ideally, the top 4 wouldn't be installed at all anymore (in case of
> > the first two at least on the systems which do not need them). But if
> > that's not in the cards, it would be great to at least not enable
> > these services anymore in the default boot so that they are only a
> > "systemctl enable" away for people who need them?
>
> At the least it seems reasonable they can be disabled on the installed
> system, and enabled for Live OS boot if the installer needs them.

I mean, it could be as easy that these services remain off, but the
installer does a "systemctl enable --now …" on them as soon as it
notices it needs them. That way the livesys and the host installed
version can be 100% identical, if that's what people want.

Lennart

--
Lennart Poettering, Berlin
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: Can we maybe reduce the set of packages we install by default a bit?

[Lennart Poettering]

On Mi, 10.04.19 12:49, Kamil Paral (kpa...@redhat.com) wrote:

> > Hmm, but the installed OS is not 100% the same as the livesys, or is
> > it? If not, it should be possible to add a "systemctl disable
> > dmraid.service --root=/path/to/os" somewhere, no?
>
> AFAIK, they are 100% same. There's a hack, check your
> /etc/rc.d/init.d/livesys
> /etc/rc.d/init.d/livesys-late
> They are executed every time during boot, but immediately quit if they
> detect they're not running on a Live image (using kernel command line). You
> can see them also here:
> https://pagure.io/fedora-kickstarts/blob/f30/f/fedora-live-base.ks#_73
> https://pagure.io/fedora-kickstarts/blob/f30/f/fedora-live-base.ks#_232
> They are ugly, I think, and many improvements could be made there. But some
> Live image adjustments are possible through them. But those are just
> runtime changes for Live environment, they don't affect the installed
> system. If anaconda had a post-install phase where it would make
> appropriate changes to the installed system (and also ideally removed
> itself and those livesys scripts), that would be great, yes.

Those scripts, can't we make them part of some RPM btw? I filed a bug
about that yesterday:

https://bugzilla.redhat.com/show_bug.cgi?id=1698119

These scripts are a bit annoying since they are the only SysV scripts
left really (not even LSB!), have no purposes on an installed system
and live outside of any RPM ownership and validation.

Lennart

--
Lennart Poettering, Berlin
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: Introduction for gaming packaging/maintaining

[Kamil Paral]

On Mon, Apr 8, 2019 at 7:34 PM Karsten Andreas Artz 
wrote:

> Hi guys,
>
> my name is Andi, 29 and I'm from Germany.  I'm using Fedora almost 2 years
> (Fedora 26). My programming skills are on Python, Java/Java Script, and
> C/C++. But acutally I prefer mostly Python hacking. I studied B.A. of Arts
> History, Archaeology and Cath.Theology. Besides this, I can speak a lot of
> languages: German, English, French, a bit Italian and Spanish.
>
> It would be glad starting contributing on Fedora as a maintainer.
> Therefore I hope to work on a small project soon.
> I'm interested in games packaging, but I don't know where to start.
>

Hi Andi,

only opensource software can be part of Fedora, and there are not that many
opensource games out there (which are not already packaged for Fedora), so
it might be a bit difficult to find something suitable and interesting (but
some of the OS clones might be a good idea). Additionally regarding games
packaging, you can consider making flatpaks instead of RPMs and submitting
them to Flathub [1]. Flathub can not only contain opensource games, but
also freeware and free-to-play games (let's talk about Linux-native games
at the moment, incorporating Wine into them would be another level of
difficulty). For example, I'd personally love to see The Dark Mod [2]
available at Flathub.

In Fedora you can also participate on packaging and maintaining
game-related software, like emulators and launchers. Wine, Lutris and
PLayOnLinux are the most visible ones, but then there are also lots of
retro emulators, many of them not even in Fedora yet, I'd guess. So it
depends on your experience and interests (both gaming and packaging). You
could even participate in e.g. Lutris community in creating and maintaining
scripts to allow easy installation of Windows and other platforms' games on
Linux.

The Gaming SIG [3] might provide a better advice, this is just what I know.

[1] https://flathub.org
[2] http://www.thedarkmod.com
[3] https://fedoraproject.org/wiki/SIGs/Games
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: Introduction for gaming packaging/maintaining

[Karsten Andreas Artz]

Yeah that would be great too. 


Sent from Yahoo Mail for iPhone


On Wednesday, April 10, 2019, 11:08 AM, Damian Ivanov  
wrote:

Yet, if they are free to be redestributed a flatpak on flathub would be great?
On Wed, 10 Apr 2019, 11:31 Dan Čermák,  wrote:

Hi Andi,

the games you listed are proprietary and can thus not be shipped with
Fedora.

What you could do, is to try to improve the out of the box experience
when trying to install and play these games. But that is quite an
undertaking as that will require diving into the guts of wine.

My recommendation would be: find something in Fedora that annoys you or
that you think it lacks and try to work on that.


Cheers,

Dan

Karsten Andreas Artz  writes:

> Hi Dan, 
> thx for welcoming me to the pack! 
> I’ve skimmed through the games. I have different games in favor: Raildroad 
> Tycoon, Pizza Tycoon and escape from Monkey Island. 
> What are the first steps to start? 
> Thx in forward
> Cheers 
> Andi 
>
>
> Sent from Yahoo Mail for iPhone
>
>
> On Tuesday, April 9, 2019, 10:48 AM, Dan Čermák 
>  wrote:
>
> Hi Andi,
>
> welcome to the pack!
>
> You can try to review some packages or submit your own package, whatever
> you feel like doing (if you submit a package, you'll need to get
> sponsored though and reviewing packages is a good way how to get
> sponsored).
>
> In case you want to package some games, there's a pretty long list of
> open source game clones: https://osgameclones.com/
> Most of these are afaik not in Fedora (yet) and some smaller ones could
> be a nice start (although you should watch out for licensing issues).
>
> In case you are looking for other ways to contribute, there's always
> this site: https://whatcanidoforfedora.org/
>
>
> Cheers,
>
> Dan
>
> Karsten Andreas Artz  writes:
>
>> Hi Benson,
>> thx for welcoming me on Fedora and thx for providing the links. 
>> I’ve read through them and skimmed them. 
>> Should I start reviewing packages or do you have another idea?
>> Regards
>> Andi 
>> Sent from Yahoo Mail for iPhone
>>
>>
>> On Monday, April 8, 2019, 9:35 PM, Benson Muite  
>> wrote:
>>
>>  
>> Hi Andi,
>>  Welcome to Fedora. Some general information is at:
>>  https://docs.fedoraproject.org/en-US/project/
>>  The get involved page still needs an update:
>>  https://docs.fedoraproject.org/en-US/project/join/
>>  but packaging guidelines are here:
>>  https://docs.fedoraproject.org/en-US/packaging-guidelines/
>>  
>> most people start by reviewing packages - though there are other ways to 
>> contribute other than packaging.
>>  
>>
>>  
>>  Regards,
>>  Benson 
>>
>>  
>>  On 4/8/19 7:32 PM, Karsten Andreas Artz wrote:
>>  
>>  
>>            Hi guys, 
>>  my name is Andi, 29 and I'm from Germany.  I'm using Fedora almost 2 years 
>>(Fedora 26). My programming skills are on Python, Java/Java Script, and  
>>C/C++. But acutally I prefer mostly Python hacking. I studied B.A. of Arts 
>>History, Archaeology and Cath.Theology. Besides this, I can speak a lot of 
>>languages: German, English, French, a  bit Italian and Spanish. 
>>  
>>  It would be glad starting contributing on Fedora as a maintainer. Therefore 
>>I hope to work on a small  project soon.
>>  I'm interested in games packaging, but I don't know where to start.
>>  
>>  
>>  Regards 
>>  Andi
>>          
>>  
>>    
>>  ___
>> devel mailing list -- devel@lists.fedoraproject.org
>> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
>> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
>> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>> List Archives: 
>> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
>>  ___
>> devel mailing list -- devel@lists.fedoraproject.org
>> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
>> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
>> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>> List Archives: 
>> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
>>
>>
>>
>> ___
>> devel mailing list -- devel@lists.fedoraproject.org
>> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
>> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
>> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>> List Archives: 
>> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: Introduction for gaming packaging/maintaining

[Karsten Andreas Artz]

Hi Dan,
I’ve checked again and I guess the clones should be the one which can be 
included on Fedora, can’t they? 
Let me list my favors: Pizza Buisness, FreeRails, Jagged Alliance 2 - 
Steaciatella. 
This should be not proprietary, shouldn’t they? 
Thx in forward!
Cheers 
Andi

Sent from Yahoo Mail for iPhone


On Wednesday, April 10, 2019, 10:30 AM, Dan Čermák 
 wrote:

Hi Andi,

the games you listed are proprietary and can thus not be shipped with
Fedora.

What you could do, is to try to improve the out of the box experience
when trying to install and play these games. But that is quite an
undertaking as that will require diving into the guts of wine.

My recommendation would be: find something in Fedora that annoys you or
that you think it lacks and try to work on that.


Cheers,

Dan

Karsten Andreas Artz  writes:

> Hi Dan, 
> thx for welcoming me to the pack! 
> I’ve skimmed through the games. I have different games in favor: Raildroad 
> Tycoon, Pizza Tycoon and escape from Monkey Island. 
> What are the first steps to start? 
> Thx in forward
> Cheers 
> Andi 
>
>
> Sent from Yahoo Mail for iPhone
>
>
> On Tuesday, April 9, 2019, 10:48 AM, Dan Čermák 
>  wrote:
>
> Hi Andi,
>
> welcome to the pack!
>
> You can try to review some packages or submit your own package, whatever
> you feel like doing (if you submit a package, you'll need to get
> sponsored though and reviewing packages is a good way how to get
> sponsored).
>
> In case you want to package some games, there's a pretty long list of
> open source game clones: https://osgameclones.com/
> Most of these are afaik not in Fedora (yet) and some smaller ones could
> be a nice start (although you should watch out for licensing issues).
>
> In case you are looking for other ways to contribute, there's always
> this site: https://whatcanidoforfedora.org/
>
>
> Cheers,
>
> Dan
>
> Karsten Andreas Artz  writes:
>
>> Hi Benson,
>> thx for welcoming me on Fedora and thx for providing the links. 
>> I’ve read through them and skimmed them. 
>> Should I start reviewing packages or do you have another idea?
>> Regards
>> Andi 
>> Sent from Yahoo Mail for iPhone
>>
>>
>> On Monday, April 8, 2019, 9:35 PM, Benson Muite  
>> wrote:
>>
>>  
>> Hi Andi,
>>  Welcome to Fedora. Some general information is at:
>>  https://docs.fedoraproject.org/en-US/project/
>>  The get involved page still needs an update:
>>  https://docs.fedoraproject.org/en-US/project/join/
>>  but packaging guidelines are here:
>>  https://docs.fedoraproject.org/en-US/packaging-guidelines/
>>  
>> most people start by reviewing packages - though there are other ways to 
>> contribute other than packaging.
>>  
>>
>>  
>>  Regards,
>>  Benson 
>>
>>  
>>  On 4/8/19 7:32 PM, Karsten Andreas Artz wrote:
>>  
>>  
>>            Hi guys, 
>>  my name is Andi, 29 and I'm from Germany.  I'm using Fedora almost 2 years 
>>(Fedora 26). My programming skills are on Python, Java/Java Script, and  
>>C/C++. But acutally I prefer mostly Python hacking. I studied B.A. of Arts 
>>History, Archaeology and Cath.Theology. Besides this, I can speak a lot of 
>>languages: German, English, French, a  bit Italian and Spanish. 
>>  
>>  It would be glad starting contributing on Fedora as a maintainer. Therefore 
>>I hope to work on a small  project soon.
>>  I'm interested in games packaging, but I don't know where to start.
>>  
>>  
>>  Regards 
>>  Andi
>>          
>>  
>>    
>>  ___
>> devel mailing list -- devel@lists.fedoraproject.org
>> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
>> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
>> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>> List Archives: 
>> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
>>  ___
>> devel mailing list -- devel@lists.fedoraproject.org
>> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
>> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
>> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>> List Archives: 
>> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
>>
>>
>>
>> ___
>> devel mailing list -- devel@lists.fedoraproject.org
>> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
>> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
>> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>> List Archives: 
>> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: 

Re: Can we maybe reduce the set of packages we install by default a bit?

[Brian (bex) Exelbierd]

On Tue, Apr 9, 2019 at 8:40 PM Japheth Cleaver  wrote:
> Is this really worth the effort? cronie in F30 is a 103K package, and a
> decent chunk of that might be the ChangeLog. crontabs is all of 18K,
> which is 95% the GPL and the RPM header. It seems like a very small
> price to pay for something everyone is going to assume will be on any
> *nix-compatible system of note.

I read, possibly misread, the original comment as being about the
number of "unneeded" things in the install, not necessarily the weight
of the specific packages.  What I think we are hearing from
containers, OSTree, etc. is that there is a group of people that wants
their systems more minimal with less unnecessary stuff.  Some of this
is about resource-sizing (RAM, Disk, etc.), some is about update and
security footprints, and some of it is about "psychic weight."  I
realize that we have to make these tradeoffs in some cases, for
example, aiui, gnome-keyring is not able to be removed and still have
a functional Gnome environment.  But this isn't universally the case.

This seems to go back to who is the primary target audience for our
Workstation edition and what do they want/expect.  Then we can
document the changes and socialize them over a few releases so that
other users can get to where they want to be.  Basically "extra" isn't
what no one wants, its what our defined target doesn't want/expect.  I
don't expect the tools I use to always be installed by default and I
don't think anyone else on the list does either.  It also speaks to
our spins/labs as ways to take our existing software and reformulate
the install to meet different users' needs.

Lastly, taking a position on some of this, for example, removing cron,
is a form of opinionation that calls back to our roots of innovating
in the OS space.  We would be saying, we recognize this is the way we
did things X years ago, but there are new ways and processes and we
see value in those.  If we can't remove these things, then we are
being a good distribution by pointing out where solutions that claim
to fix something have fallen short so that those upstreams can make
decisions about what to do.

> The last thing I'd want to have to deal with is solving for a missing
> /etc/cron.* because someone forgot to click a checkbox somewhere or
> didn't call it out in kickstart.

Yes, but I also don't want to deal with a security fix in cron when I
didn't want it to begin with.  Adding software the user doesn't want
to have it as assumed for other users is always a trade-off.

regards,

bex
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: Can we maybe reduce the set of packages we install by default a bit?

[Kamil Paral]

On Tue, Apr 9, 2019 at 8:21 PM Lennart Poettering 
wrote:

> Hmm, but the installed OS is not 100% the same as the livesys, or is
> it? If not, it should be possible to add a "systemctl disable
> dmraid.service --root=/path/to/os" somewhere, no?
>

AFAIK, they are 100% same. There's a hack, check your
/etc/rc.d/init.d/livesys
/etc/rc.d/init.d/livesys-late
They are executed every time during boot, but immediately quit if they
detect they're not running on a Live image (using kernel command line). You
can see them also here:
https://pagure.io/fedora-kickstarts/blob/f30/f/fedora-live-base.ks#_73
https://pagure.io/fedora-kickstarts/blob/f30/f/fedora-live-base.ks#_232
They are ugly, I think, and many improvements could be made there. But some
Live image adjustments are possible through them. But those are just
runtime changes for Live environment, they don't affect the installed
system. If anaconda had a post-install phase where it would make
appropriate changes to the installed system (and also ideally removed
itself and those livesys scripts), that would be great, yes.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: Could not execute import_srpm

[Antonio Trande]

Thank you, Todd.

Output attached and posted in
https://pagure.io/fedora-infrastructure/issue/7704

-- 
---
Antonio Trande
Fedora Project
mailto 'sagitter at fedoraproject dot org'
GPG key: 0x6e0331dd1699e4d7
GPG key server: https://keys.fedoraproject.org/


fedpkg_test.tar.xz
Description: application/xz


signature.asc
Description: OpenPGP digital signature
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: dlib update

[Fabio Valentini]

On Wed, Apr 10, 2019 at 4:08 AM Luya Tshimbalanga
 wrote:
>
> Hello team,
>
> dlib needs an update but the maintainer has not responded for month to
> verify and merge the change.
> Can a proven test push the merge and update that package matching
> upstream release.

From looking at it quickly, it seems like you've updated the .spec for
version 19.17 but have only uploaded sources for 19.16.

> See https://release-monitoring.org/project/18600/
>
> Reference:
>
> ---
>
> https://src.fedoraproject.org/rpms/dlib/pull-request/4
>
>
> Thanks,
>
> Luya
>
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: Updating/rebuilding of coin-or packages

[Antonio Trande]

On 10/04/19 05:50, Jerry James wrote:
> On Tue, Apr 9, 2019 at 4:21 AM Antonio Trande  wrote:
>> We can complete the coin-or-Bonmin, coin-or-Couenne, coin-or-Dip,
>> coin-or-OS reviews before, of course.
>>
>> Let me check them.
> 
> I had hoped to get a COPR set up tonight, but alas!  I ran out of
> time.

You may ask permissions for my Copr project:
https://copr.fedorainfracloud.org/coprs/sagitter/ForTesting/permissions/

> So I just uploaded a tarball here:
> 
> http://www.jamezone.org/coin-or.tar
> 
> I'll leave it there for a few days.  I haven't had time to review what
> you have done, either.  Sorry.  I'm going to be busy tomorrow, too, so
> I probably won't get to anything else until Thursday.
> 
> Regards,
> 

-- 
---
Antonio Trande
Fedora Project
mailto 'sagitter at fedoraproject dot org'
GPG key: 0x6e0331dd1699e4d7
GPG key server: https://keys.fedoraproject.org/



signature.asc
Description: OpenPGP digital signature
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: Can we maybe reduce the set of packages we install by default a bit?

[Kamil Paral]

On Wed, Apr 10, 2019 at 2:35 AM Chris Murphy 
wrote:

> > 1. multipathd.
>
> I'm pretty sure it gets dragged in by the installer


Nope, multipath seems to be present because libblockdev and udisks (and
perhaps some more), which is in turn required by GNOME:

$ rpm -q --whatrequires device-mapper-multipath
libblockdev-fs-2.21-2.fc30.x86_64
libblockdev-part-2.21-2.fc30.x86_64
libblockdev-mpath-2.21-2.fc30.x86_64
fcoe-utils-1.0.32-6.fc29.x86_64

$ rpm -q --whatrequires libblockdev-fs
udisks2-2.8.2-1.fc30.x86_64

$ rpm -q --whatrequires udisks2
gvfs-1.40.0-1.fc30.x86_64
gnome-disk-utility-3.32.0-1.fc30.x86_64

That was latest F30 Workstation Live.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: Anyone seeing udev failing to start in Rawhide?

[Richard W.M. Jones]

On Wed, Apr 10, 2019 at 09:53:26AM +0100, Richard W.M. Jones wrote:
> 
> Forgot to say that the version of systemd is:
> systemd-242~rc3-1.fc31.x86_64

systemd-242~rc4-1.fc31 is also broken.  Maybe critical packages like
these could be tested in a VM before we let ordinary users suffer
them?

Anyway I ended up completely destroying the system while trying to
recover so now have to reinstall from scratch.

Rich.

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
virt-top is 'top' for virtual machines.  Tiny program with many
powerful monitoring features, net stats, disk stats, logging, etc.
http://people.redhat.com/~rjones/virt-top
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: Could not execute import_srpm

[Martin Stransky]

I see that too, filed it as 
https://pagure.io/fedora-infrastructure/issue/7704

ma

On 4/8/19 12:08 PM, Antonio Trande wrote:

Hi all.

I can't upload source archive of new package 'smoldyn'

$ fedpkg import ../../smoldyn-2.58-1.fc29.src.rpm
Uploading: /home/sagitter/rpmbuild/SRPMS/fedora-scm/smoldyn/smoldyn-2.58.tgz

100.0%
Could not execute import_srpm: Fail to upload files. Server returns
status 408



___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: Introduction for gaming packaging/maintaining

[Damian Ivanov]

Yet, if they are free to be redestributed a flatpak on flathub would be
great?

On Wed, 10 Apr 2019, 11:31 Dan Čermák, 
wrote:

> Hi Andi,
>
> the games you listed are proprietary and can thus not be shipped with
> Fedora.
>
> What you could do, is to try to improve the out of the box experience
> when trying to install and play these games. But that is quite an
> undertaking as that will require diving into the guts of wine.
>
> My recommendation would be: find something in Fedora that annoys you or
> that you think it lacks and try to work on that.
>
>
> Cheers,
>
> Dan
>
> Karsten Andreas Artz  writes:
>
> > Hi Dan,
> > thx for welcoming me to the pack!
> > I’ve skimmed through the games. I have different games in favor:
> Raildroad Tycoon, Pizza Tycoon and escape from Monkey Island.
> > What are the first steps to start?
> > Thx in forward
> > Cheers
> > Andi
> >
> >
> > Sent from Yahoo Mail for iPhone
> >
> >
> > On Tuesday, April 9, 2019, 10:48 AM, Dan Čermák <
> dan.cer...@cgc-instruments.com> wrote:
> >
> > Hi Andi,
> >
> > welcome to the pack!
> >
> > You can try to review some packages or submit your own package, whatever
> > you feel like doing (if you submit a package, you'll need to get
> > sponsored though and reviewing packages is a good way how to get
> > sponsored).
> >
> > In case you want to package some games, there's a pretty long list of
> > open source game clones: https://osgameclones.com/
> > Most of these are afaik not in Fedora (yet) and some smaller ones could
> > be a nice start (although you should watch out for licensing issues).
> >
> > In case you are looking for other ways to contribute, there's always
> > this site: https://whatcanidoforfedora.org/
> >
> >
> > Cheers,
> >
> > Dan
> >
> > Karsten Andreas Artz  writes:
> >
> >> Hi Benson,
> >> thx for welcoming me on Fedora and thx for providing the links.
> >> I’ve read through them and skimmed them.
> >> Should I start reviewing packages or do you have another idea?
> >> Regards
> >> Andi
> >> Sent from Yahoo Mail for iPhone
> >>
> >>
> >> On Monday, April 8, 2019, 9:35 PM, Benson Muite <
> benson_mu...@emailplus.org> wrote:
> >>
> >>
> >> Hi Andi,
> >>  Welcome to Fedora. Some general information is at:
> >>  https://docs.fedoraproject.org/en-US/project/
> >>  The get involved page still needs an update:
> >>  https://docs.fedoraproject.org/en-US/project/join/
> >>  but packaging guidelines are here:
> >>  https://docs.fedoraproject.org/en-US/packaging-guidelines/
> >>
> >> most people start by reviewing packages - though there are other ways
> to contribute other than packaging.
> >>
> >>
> >>
> >>  Regards,
> >>  Benson
> >>
> >>
> >>  On 4/8/19 7:32 PM, Karsten Andreas Artz wrote:
> >>
> >>
> >>Hi guys,
> >>  my name is Andi, 29 and I'm from Germany.  I'm using Fedora almost 2
> years (Fedora 26). My programming skills are on Python, Java/Java Script,
> and  C/C++. But acutally I prefer mostly Python hacking. I studied B.A. of
> Arts History, Archaeology and Cath.Theology. Besides this, I can speak a
> lot of languages: German, English, French, a  bit Italian and Spanish.
> >>
> >>  It would be glad starting contributing on Fedora as a maintainer.
> Therefore I hope to work on a small  project soon.
> >>  I'm interested in games packaging, but I don't know where to start.
> >>
> >>
> >>  Regards
> >>  Andi
> >>
> >>
> >>
> >>  ___
> >> devel mailing list -- devel@lists.fedoraproject.org
> >> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> >> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> >> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> >> List Archives:
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
> >>  ___
> >> devel mailing list -- devel@lists.fedoraproject.org
> >> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> >> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> >> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> >> List Archives:
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
> >>
> >>
> >>
> >> ___
> >> devel mailing list -- devel@lists.fedoraproject.org
> >> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> >> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> >> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> >> List Archives:
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: 

Re: Anyone seeing udev failing to start in Rawhide?

[Damian Ivanov]

Yes, system is unable to boot anymore. With previous kernels and rescue
modes as well. I used the opportunity to install silver blue.
BR,
Damian

On Wed, 10 Apr 2019, 11:53 Richard W.M. Jones,  wrote:

>
> Forgot to say that the version of systemd is:
> systemd-242~rc3-1.fc31.x86_64
>
> Rich.
>
> --
> Richard Jones, Virtualization Group, Red Hat
> http://people.redhat.com/~rjones
> Read my programming and virtualization blog: http://rwmj.wordpress.com
> virt-df lists disk usage of guests without needing to install any
> software inside the virtual machine.  Supports Linux and Windows.
> http://people.redhat.com/~rjones/virt-df/
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
>
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

F30 live images still contain dbus-daemon package, anaconda-core requires it ?

[Hans de Goede]

Hi All,

I just noticed that Fedora-Workstation-Live-x86_64-30-20190408.n.0.iso still
contains the dbus-daemon package even though we are using dbus-broker now.

I've tried to rpm -e it and it for some reason it is required by
anaconda-core which seems weird.

So should I file a bug against anaconda for this? I guess it is too late
to fix this for F30?

Regards,

Hans
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: Fork a 119MB pagure project to updating monitoring?

[Pierre-Yves Chibon]

On Mon, Mar 25, 2019 at 02:55:23PM -0500, Richard Shaw wrote:
>Other than having it as a direct option in [1]src.fp.org I think being
>part of a special file in git would be next best.

In the recent releases pagure grew the possibility to have 3rd party extensions
with their own URL endpoints and able to extend the current database model to
store extra information.

I've spent a little time using this feature to gain back support in pagure's UI
to toggle the monitoring status.

Here is a small demo of how it looks like:
http://ambre.pingoured.fr/public/Screencast_pagure_distgit_anitya.webm

Basically, there would now be a button on the sidebar which would show the
current monitoring status and would allow project admins and pagure wide admins
to update this setting.

Feedback most welcome :)

I'm going to clean up the code a little bit and open a PR on the pagure-dist-git
project, reviews and suggestions welcome there as well.


Hoping this helps,

Pierre
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

[Bug 1698315] perl-Verilog-Perl-3.462 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1698315

Fedora Update System  changed:

   What|Removed |Added

 Status|ASSIGNED|MODIFIED



--- Comment #1 from Fedora Update System  ---
perl-Verilog-Perl-3.462-1.fc30 has been submitted as an update to Fedora 30.
https://bodhi.fedoraproject.org/updates/FEDORA-2019-94b4b94de8

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org

Re: Anyone seeing udev failing to start in Rawhide?

[Richard W.M. Jones]

Forgot to say that the version of systemd is:
systemd-242~rc3-1.fc31.x86_64

Rich.

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
virt-df lists disk usage of guests without needing to install any
software inside the virtual machine.  Supports Linux and Windows.
http://people.redhat.com/~rjones/virt-df/
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Anyone seeing udev failing to start in Rawhide?

[Richard W.M. Jones]

Repeated errors on the console like this:

 Starting udev Kernel Device Manager...
[FAILED] Failed to start udev Kernel Device Manager.
See 'systemctl status systemd-udevd.service' for details.
[  OK  ] Stopped udev Kernel Device Manager.
 Starting udev Kernel Device Manager...
[FAILED] Failed to start udev Kernel Device Manager.
See 'systemctl status systemd-udevd.service' for details.

When I finally get to the emergency console the output from "systemctl
status systemd-udevd.service" isn't actually any more helpful:

● systemd-udevd.service - udev Kernel Device Manager
   Loaded: loaded (/usr/lib/systemd/system/systemd-udevd.service; static; 
vendor preset: disabled)
   Active: failed (Result: exit-code) since Wed 2019-04-10 09:43:21 BST; 3min 
41s ago
 Docs: man:systemd-udevd.service(8)
   man:udev(7)
  Process: 938 ExecStart=/usr/lib/systemd/systemd-udevd (code=exited, 
status=226/NAMESPACE)
 Main PID: 938 (code=exited, status=226/NAMESPACE)

Apr 10 09:43:21 trick.home.annexia.org systemd[1]: Starting udev Kernel Device 
Manager...
Apr 10 09:43:21 trick.home.annexia.org systemd[1]: systemd-udevd.service: Main 
process exited, code=exited, status=226/NAMESPACE
Apr 10 09:43:21 trick.home.annexia.org systemd[1]: systemd-udevd.service: 
Failed with result 'exit-code'.
Apr 10 09:43:21 trick.home.annexia.org systemd[1]: Failed to start udev Kernel 
Device Manager.
Apr 10 09:43:21 trick.home.annexia.org systemd[1]: systemd-udevd.service: 
Service has no hold-off time (RestartSec=0), scheduling restart.
Apr 10 09:43:21 trick.home.annexia.org systemd[1]: systemd-udevd.service: 
Scheduled restart job, restart counter is at 5.
Apr 10 09:43:21 trick.home.annexia.org systemd[1]: Stopped udev Kernel Device 
Manager.
Apr 10 09:43:21 trick.home.annexia.org systemd[1]: systemd-udevd.service: Start 
request repeated too quickly.
Apr 10 09:43:21 trick.home.annexia.org systemd[1]: systemd-udevd.service: 
Failed with result 'exit-code'.
Apr 10 09:43:21 trick.home.annexia.org systemd[1]: Failed to start udev Kernel 
Device Manager.

The kernel is: 5.1.0-0.rc3.git3.1.fc31.x86_64

It seems to be a udev problem because going back to kernel 5.0.0
does not help ...

Rich.

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
virt-builder quickly builds VMs from scratch
http://libguestfs.org/virt-builder.1.html
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: Introduction for gaming packaging/maintaining

[Dan Čermák]

Hi Andi,

the games you listed are proprietary and can thus not be shipped with
Fedora.

What you could do, is to try to improve the out of the box experience
when trying to install and play these games. But that is quite an
undertaking as that will require diving into the guts of wine.

My recommendation would be: find something in Fedora that annoys you or
that you think it lacks and try to work on that.


Cheers,

Dan

Karsten Andreas Artz  writes:

> Hi Dan, 
> thx for welcoming me to the pack! 
> I’ve skimmed through the games. I have different games in favor: Raildroad 
> Tycoon, Pizza Tycoon and escape from Monkey Island. 
> What are the first steps to start? 
> Thx in forward
> Cheers 
> Andi 
>
>
> Sent from Yahoo Mail for iPhone
>
>
> On Tuesday, April 9, 2019, 10:48 AM, Dan Čermák 
>  wrote:
>
> Hi Andi,
>
> welcome to the pack!
>
> You can try to review some packages or submit your own package, whatever
> you feel like doing (if you submit a package, you'll need to get
> sponsored though and reviewing packages is a good way how to get
> sponsored).
>
> In case you want to package some games, there's a pretty long list of
> open source game clones: https://osgameclones.com/
> Most of these are afaik not in Fedora (yet) and some smaller ones could
> be a nice start (although you should watch out for licensing issues).
>
> In case you are looking for other ways to contribute, there's always
> this site: https://whatcanidoforfedora.org/
>
>
> Cheers,
>
> Dan
>
> Karsten Andreas Artz  writes:
>
>> Hi Benson,
>> thx for welcoming me on Fedora and thx for providing the links. 
>> I’ve read through them and skimmed them. 
>> Should I start reviewing packages or do you have another idea?
>> Regards
>> Andi 
>> Sent from Yahoo Mail for iPhone
>>
>>
>> On Monday, April 8, 2019, 9:35 PM, Benson Muite  
>> wrote:
>>
>>  
>> Hi Andi,
>>  Welcome to Fedora. Some general information is at:
>>  https://docs.fedoraproject.org/en-US/project/
>>  The get involved page still needs an update:
>>  https://docs.fedoraproject.org/en-US/project/join/
>>  but packaging guidelines are here:
>>  https://docs.fedoraproject.org/en-US/packaging-guidelines/
>>  
>> most people start by reviewing packages - though there are other ways to 
>> contribute other than packaging.
>>  
>>
>>  
>>  Regards,
>>  Benson 
>>
>>  
>>  On 4/8/19 7:32 PM, Karsten Andreas Artz wrote:
>>  
>>  
>>            Hi guys, 
>>  my name is Andi, 29 and I'm from Germany.  I'm using Fedora almost 2 years 
>>(Fedora 26). My programming skills are on Python, Java/Java Script, and  
>>C/C++. But acutally I prefer mostly Python hacking. I studied B.A. of Arts 
>>History, Archaeology and Cath.Theology. Besides this, I can speak a lot of 
>>languages: German, English, French, a  bit Italian and Spanish. 
>>  
>>  It would be glad starting contributing on Fedora as a maintainer. Therefore 
>>I hope to work on a small  project soon.
>>  I'm interested in games packaging, but I don't know where to start.
>>  
>>  
>>  Regards 
>>  Andi
>>          
>>  
>>    
>>  ___
>> devel mailing list -- devel@lists.fedoraproject.org
>> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
>> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
>> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>> List Archives: 
>> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
>>  ___
>> devel mailing list -- devel@lists.fedoraproject.org
>> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
>> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
>> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>> List Archives: 
>> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
>>
>>
>>
>> ___
>> devel mailing list -- devel@lists.fedoraproject.org
>> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
>> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
>> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>> List Archives: 
>> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


signature.asc
Description: PGP signature
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

[EPEL-devel] Fedora EPEL 6 updates-testing report

[updates]

The following Fedora EPEL 6 Security updates need testing:
 Age  URL
  40  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-06b243cced   
guacamole-server-1.0.0-1.el6
  19  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-62f9745b71   
drupal7-7.65-1.el6
  10  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-8d5207833a   
ntfs-3g-2017.3.23-11.el6
   1  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-73e99f4a82   
python34-3.4.10-1.el6


The following builds have been pushed to Fedora EPEL 6 updates-testing

bdii-5.2.25-2.el6
pspg-1.6.5-1.el6

Details about builds:



 bdii-5.2.25-2.el6 (FEDORA-EPEL-2019-a65e3cb820)
 The Berkeley Database Information Index (BDII)

Update Information:

bdii 5.2.25

ChangeLog:

* Tue Apr  9 2019 Mattias Ellert  - 5.2.25-2
- Define __python2 if undefined
* Tue Apr  9 2019 Mattias Ellert  - 5.2.25-1
- Version 5.2.25
- Upstream project moved to github
* Thu Jan 31 2019 Fedora Release Engineering  - 
5.2.23-12
- Rebuilt for https://fedoraproject.org/wiki/Fedora_30_Mass_Rebuild
* Tue Nov 13 2018 Mattias Ellert  - 5.2.23-11
- Don't use /usr/bin/python shebang
- Remove EPEL 5 conditionals
* Thu Jul 12 2018 Fedora Release Engineering  - 
5.2.23-10
- Rebuilt for https://fedoraproject.org/wiki/Fedora_29_Mass_Rebuild
* Wed Feb  7 2018 Iryna Shcherbina  - 5.2.23-9
- Update Python 2 dependency declarations to new packaging standards
  (See https://fedoraproject.org/wiki/FinalizingFedoraSwitchtoPython3)
* Wed Feb  7 2018 Fedora Release Engineering  - 
5.2.23-8
- Rebuilt for https://fedoraproject.org/wiki/Fedora_28_Mass_Rebuild
* Wed Jul 26 2017 Fedora Release Engineering  - 
5.2.23-7
- Rebuilt for https://fedoraproject.org/wiki/Fedora_27_Mass_Rebuild
* Fri Feb 10 2017 Fedora Release Engineering  - 
5.2.23-6
- Rebuilt for https://fedoraproject.org/wiki/Fedora_26_Mass_Rebuild
* Mon Aug 15 2016 Mattias Ellert  - 5.2.23-5
- Convert to systemd unit files (Fedora 25+)
* Wed Feb  3 2016 Fedora Release Engineering  - 
5.2.23-4
- Rebuilt for https://fedoraproject.org/wiki/Fedora_24_Mass_Rebuild
* Sun Jul 26 2015 Mattias Ellert  - 5.2.23-3
- Adapt to new policycoreutils packaging (Fedora 23+)
* Wed Jun 17 2015 Fedora Release Engineering  
- 5.2.23-2
- Rebuilt for https://fedoraproject.org/wiki/Fedora_23_Mass_Rebuild




 pspg-1.6.5-1.el6 (FEDORA-EPEL-2019-6db5064584)
 A unix pager optimized for psql

Update Information:

new upstream release, per release notes:
https://github.com/okbob/pspg/releases/tag/1.6.5

ChangeLog:

* Tue Apr  9 2019 Pavel Raiskup  - 1.6.5-1
- new upstream release, per release notes:
  https://github.com/okbob/pspg/releases/tag/1.6.5

References:

  [ 1 ] Bug #1697260 - pspg-1.6.5 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1697260


___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org

[Bug 1698172] perl-Sereal-4.007 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1698172

Petr Pisar  changed:

   What|Removed |Added

 Status|ASSIGNED|MODIFIED
   Fixed In Version||perl-Sereal-4.007-1.fc31



-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org

[Bug 1698174] perl-Sereal-Encoder-4.007 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1698174



--- Comment #3 from Fedora Update System  ---
perl-Sereal-Encoder-4.007-1.fc29 has been submitted as an update to Fedora 29.
https://bodhi.fedoraproject.org/updates/FEDORA-2019-6b8d5826ee

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org

[Bug 1697635] perl-Sereal-Encoder-4.006 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1697635

Fedora Update System  changed:

   What|Removed |Added

 Status|ON_QA   |MODIFIED



--- Comment #7 from Fedora Update System  ---
perl-Sereal-Encoder-4.007-1.fc29 has been submitted as an update to Fedora 29.
https://bodhi.fedoraproject.org/updates/FEDORA-2019-6b8d5826ee

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org

[Bug 1697635] perl-Sereal-Encoder-4.006 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1697635



--- Comment #8 from Fedora Update System  ---
perl-Sereal-Encoder-4.007-1.fc28 has been submitted as an update to Fedora 28.
https://bodhi.fedoraproject.org/updates/FEDORA-2019-8cd7dca507

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org

[Bug 1698174] perl-Sereal-Encoder-4.007 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1698174



--- Comment #2 from Fedora Update System  ---
perl-Sereal-Encoder-4.007-1.fc30 has been submitted as an update to Fedora 30.
https://bodhi.fedoraproject.org/updates/FEDORA-2019-6d62add2b9

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org

[Bug 1698174] perl-Sereal-Encoder-4.007 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1698174



--- Comment #4 from Fedora Update System  ---
perl-Sereal-Encoder-4.007-1.fc28 has been submitted as an update to Fedora 28.
https://bodhi.fedoraproject.org/updates/FEDORA-2019-8cd7dca507

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org

[Bug 1697634] perl-Sereal-Decoder-4.006 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1697634

Fedora Update System  changed:

   What|Removed |Added

 Status|MODIFIED|ON_QA



--- Comment #7 from Fedora Update System  ---
perl-Sereal-Decoder-4.006-1.fc29 has been pushed to the Fedora 29 testing
repository. If problems still persist, please make note of it in this bug
report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-2019-d5b3e2cb13

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org

[Bug 1697635] perl-Sereal-Encoder-4.006 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1697635



--- Comment #6 from Fedora Update System  ---
perl-Sereal-Encoder-4.006-1.fc29 has been pushed to the Fedora 29 testing
repository. If problems still persist, please make note of it in this bug
report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-2019-4965667f10

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org

[Bug 1698173] perl-Sereal-Decoder-4.007 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1698173



--- Comment #3 from Fedora Update System  ---
perl-Sereal-Decoder-4.007-1.fc29 has been submitted as an update to Fedora 29.
https://bodhi.fedoraproject.org/updates/FEDORA-2019-3201ee80ae

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org

[Bug 1697634] perl-Sereal-Decoder-4.006 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1697634

Fedora Update System  changed:

   What|Removed |Added

 Status|ON_QA   |MODIFIED



--- Comment #6 from Fedora Update System  ---
perl-Sereal-Decoder-4.007-1.fc28 has been submitted as an update to Fedora 28.
https://bodhi.fedoraproject.org/updates/FEDORA-2019-a203e0e74a

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org

[Bug 1698173] perl-Sereal-Decoder-4.007 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1698173



--- Comment #4 from Fedora Update System  ---
perl-Sereal-Decoder-4.007-1.fc28 has been submitted as an update to Fedora 28.
https://bodhi.fedoraproject.org/updates/FEDORA-2019-a203e0e74a

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org

[Bug 1698173] perl-Sereal-Decoder-4.007 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1698173



--- Comment #2 from Fedora Update System  ---
perl-Sereal-Decoder-4.007-1.fc30 has been submitted as an update to Fedora 30.
https://bodhi.fedoraproject.org/updates/FEDORA-2019-222d8a64ac

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org

Re: Can we maybe reduce the set of packages we install by default a bit?

[Nicolas Mailhot]

Le mardi 09 avril 2019 à 10:11 -0700, Adam Williamson a écrit :
> 
> To be specific here, 'at' is part of the @standard group. 'chrony' is
> pulled in several ways. It's part of @standard *if gnome-control-
> center 
> is being installed*, so effectively it'll be installed with
> Workstation
> but not other editions/spins. That sort of implies that there's some
> functionality in GNOME that depends on chrony; 

chrony, mdadm and dmraid are all necessary parts of a workstation
setup.

The first one because some virtualisation systems (windows 10 Hyper-V
for example) are braindamaged and will wake up VMs (including GNOME
VMs) with a system clock stuck at the time the VM was frozen. So you
better have a clock-skewing ntp client running in all your vms. chrony
is the best existing one right now IIRC (kuddo to chrony devs, they
passed their security audits with style)

The others because raid does exist on workstations, and the dmraid guys
never got around to finish replicating all the mdadm functionnalities
(pretty much like networkd stopped at integrating bonding, and never
bothered to do teaming, for example).

chrond, at, udev settle… that's all lack or good proeminent systemd
documentation, that causes third party projects to kludge, and gave up
on things they do not understand.

-- 
Nicolas Mailhot
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

[Bug 1698174] perl-Sereal-Encoder-4.007 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1698174

Petr Pisar  changed:

   What|Removed |Added

 Status|ASSIGNED|MODIFIED
   Fixed In Version||perl-Sereal-Encoder-4.007-1
   ||.fc31



--- Comment #1 from Petr Pisar  ---
A dummy release. Suitable for all Fedora.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org

[Bug 1698173] perl-Sereal-Decoder-4.007 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1698173

Petr Pisar  changed:

   What|Removed |Added

 Status|ASSIGNED|MODIFIED
   Fixed In Version||perl-Sereal-Decoder-4.007-1
   ||.fc31



--- Comment #1 from Petr Pisar  ---
An enhancement release suitable for all Fedoras.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org

[Bug 1698172] perl-Sereal-4.007 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1698172

Petr Pisar  changed:

   What|Removed |Added

 Depends On||1698173, 1698174



--- Comment #1 from Petr Pisar  ---
A bug-fix release that needs latest Sereal::Encoder and Sereal::Decoder. I will
push it into older Fedoras once they become stable.


Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=1698173
[Bug 1698173] perl-Sereal-Decoder-4.007 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1698174
[Bug 1698174] perl-Sereal-Encoder-4.007 is available
-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org

[Bug 1698173] perl-Sereal-Decoder-4.007 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1698173

Petr Pisar  changed:

   What|Removed |Added

 Blocks||1698172




Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=1698172
[Bug 1698172] perl-Sereal-4.007 is available
-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org

[Bug 1698174] perl-Sereal-Encoder-4.007 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1698174

Petr Pisar  changed:

   What|Removed |Added

 Blocks||1698172




Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=1698172
[Bug 1698172] perl-Sereal-4.007 is available
-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org

Re: Can we maybe reduce the set of packages we install by default a bit?

[Julen Landa Alustiza]

I'm really interested on the livet crash, but I can't reproduce it with
latest branched compose.
Can you provide us with reproduction steps?

Hau idatzi du Neal Gompa (ngomp...@gmail.com) erabiltzaileak (2019 api. 10,
az. (02:59)):

> On Tue, Apr 9, 2019 at 8:35 PM Chris Murphy 
> wrote:
> >
> > On Tue, Apr 9, 2019 at 10:07 AM Lennart Poettering 
> wrote:
> > >
> > > Heya,
> > >
> > > today I installed the current Fedora 30 Workstation beta on my new
> > > laptop. It was a bumpy ride, I must say (the partitioner (blivet?)
> > > crashed five times or so on me, always kicking me out of anaconda
> > > again, just because I wanted to undo something).
> >
> > I haven't seen a single one come across in QA
> >
> > > 1. multipathd.
> >
> > I'm pretty sure it gets dragged in by the installer, i.e. the
> > installation environment needs it because installing to multipath is
> > supported. And since it's on the Workstation LiveOS, it just gets
> > copied over along with the installer itself (LiveOS installs use
> > rsync). I wonder if it's reasonable to apply more exclude filtering
> > during rsync to avoid copying some things needed for Live OS
> > environment, but not on the final installed system. But that's sorta
> > up to Workstation WG I think.
> >
>
> Not having the rpmdb in sync with what content is on the system is
> probably not a good idea. I'd advocate for anaconda being able to run
> dnf to clean up stuff instead.
>
> >
> > > 2. dmraid.
> >
> > Same as above. I'm not sure whether, or when, dmraid stuff is going to
> > be dropped by anaconda. For a long time now dmraid is deprecated. The
> > two supported ways of doing software raid are managed by mdadm and
> > lvm, both of which actually use the md driver in the kernel.
> >
> > So I think this is a question for the anaconda team.
> >
> >
> > > 4. Similar crond. On my fresh install it's only used by "zfs-fuse",
> > >which I really wonder why it even is in the default install? And
> > >"mdadm" wants this too. (which would be great if it would just use
> > >timer units)
> >
> > I think zfs-fuse and glusterfs are dragged in by libvirt, which is
> > present because of GNOME Boxes. I don't know why any of those want
> > crond.
> >
>
> These could be converted to systemd units. There's no reason not to,
> really...
>
> > mdadm scrub and monitoring depends on crond, and then email
> > notifications if mismatch count != 0; it's archaic these days I guess,
> > but that's how it works.
> >
> >
> > > 5. libvirtd. Why is this running? Can't we make this socket
> > >activatable + exit-on-idel? While I am sure it's useful on
> > >workstations why run it all the time, given that only very few
> > >users probably actually need that, and if they do starting it on
> > >demand would be much more appropriate? On my freshly installed
> > >system it is running all the time even though there are no VMs or
> > >anything around.
> >
> > Agreed.
> >
> >
> > >
> > > Ideally, the top 4 wouldn't be installed at all anymore (in case of
> > > the first two at least on the systems which do not need them). But if
> > > that's not in the cards, it would be great to at least not enable
> > > these services anymore in the default boot so that they are only a
> > > "systemctl enable" away for people who need them?
> >
> > At the least it seems reasonable they can be disabled on the installed
> > system, and enabled for Live OS boot if the installer needs them.
> >
> > --
> > Chris Murphy
> > ___
> > devel mailing list -- devel@lists.fedoraproject.org
> > To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> > Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> > List Archives:
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
>
>
>
> --
> 真実はいつも一つ！/ Always, there's only one truth!
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
>


-- 
Julen Landa Alustiza 
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org