October 2018 - devel - Fedora Mailing-Lists

by Miroslav Suchý

I just stumbled upon https://unix.stackexchange.com/questions/400634/does-anyone-bother-to-rem... with the nice link to: https://blog.laimbock.com/2014/05/02/how-to-remove-an-imported-gpg-key-fr... And I wonder: is it a good idea to keep old gpg keys in RPM db? Or should we automate the removal of old keys? Mirek

1 week, 4 days

15
29
0 / 0

git push permission denied

by Neal Becker

I just had to setup a new machine, and new ssh keys. I visited https://admin.fedoraproject.org/accounts/user/edit/xxxx I chose my new id_rsa.pub to upload. But I get: git push --verbose Pushing to ssh://nbecker@pkgs.fedoraproject.org/mercurial Permission denied (publickey). fatal: The remote end hung up unexpectedly Hints?

3 months

4
5
2 / 0

Headsup: dbus 1.12.10-1.fc29 is missing systemd dbus.service file, breaking almost everything

by Hans de Goede

Hi All, Just a quick headsup for users following Fedora 29, the dbus 1.12.10-1.fc29 build is missing the systemd dbus.service file, breaking almost everything. Instead it contains a dbus-daemon.service file, but the dbus.socket file expects a matching dbus.service, not dbus-daemon.service. So either hold of on applying updates until this is fixed or exclude dbus. Regards, Hans

9 months, 2 weeks

17
28
1 / 0

Adding Obsoletes to generated -debuginfo packages ?

by Daniel P. Berrangé

In libvirt we recently deleted a driver for the legacy Xen toolstack. This was shipped in a libvirt-daemon-driver-xen RPM. I am able to add an "Obsoletes: libvirt-daemon-driver-xen < 4.3.0" line to the libvirt-daemon-driver-libxl RPM, which gives clean upgrade path for users. If they have the libvirt-daemon-driver-xen-debuginfo RPM installed though that still breaks the upgrade. How can I get the auto-generated libvirt-daemon-driver-libxl-debuginfo RPM to have an "Obsoletes: libvirt-daemon-driver-xen-debuginfo < 4.3.0" statement ? It seems impossible, meaning users with debuginfo have a broken upgrade path. An unfortunate consequence of switching to seprate -debuginfo per sub-RPM. Regards, Daniel -- |: https://berrange.com -o- https://www.flickr.com/photos/dberrange :| |: https://libvirt.org -o- https://fstop138.berrange.com :| |: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|

11 months, 2 weeks

7
12
0 / 0

Orphaning pykka

by Jonathan Dieter

I've just orphaned pykka (https://admin.fedoraproject.org/pkgdb/package /rpms/pykka/) as I'm no longer using it. Jonathan

1 year, 4 months

3
4
0 / 0

Use immutable CRAN URLs

by Iñaki Ucar

Hi, Currently, most of the R packages included in Fedora use the following lines in the SPEC: URL: https://cran.r-project.org/web/packages/%{packname}/ Source0: https://cran.r-project.org/src/contrib/%{packname}_%{version}.tar.gz This URL format is not recommended by CRAN, but more importantly, the Source0 format does not work anymore, as [1] noted, when a new version is released. However, there is an immutable format available, as [2] pointed out. So my proposal is to use always the following lines instead: URL: https://cran.r-project.org/package=%{packname} Source0: %{url}&version=%{version} which are both shorter and immutable, and I propose to add this to the R packaging guidelines too. If we agree on this, is there any easy way to request a system-wide change like that to all existing packages? Regards, -- Iñaki Ucar [1] https://stat.ethz.ch/pipermail/r-devel/2018-October/076988.html [2] https://stat.ethz.ch/pipermail/r-devel/2018-October/076989.html

1 year, 6 months

5
28
0 / 0

startx unsets DBUS_SESSION_BUS_ADDRESS, which breaks user D-Bus session

by Alexey Rochev

Hello, I would like to draw some attention to this bug: https://bugzilla.redhat.com/show_bug.cgi?id=1622259. Description: startx unsets DBUS_SESSION_BUS_ADDRESS, which result in launching another D-Bus session which breaks communicating with user systemd services (and any D-Bus services started before launching X) from X session via D-Bus, since they use two different D-Bus daemons. I would really like this bug to be fixed. Thanks, Alexey Rochev

1 year, 9 months

4
8
0 / 0

Nonresponsive maintainer: salimma

by Miro Hrončok

https://bugzilla.redhat.com/show_bug.cgi?id=1589077 Does anyone know how to contact the maintainer? -- Miro Hrončok -- Phone: +420777974800 IRC: mhroncok

1 year, 11 months

4
4
0 / 0

Attention Gmail users, please turn off HTML mail

by Dominik 'Rathann' Mierzejewski

Dear developers, sorry for a slightly off-topic post, but I've noticed that a significant number of posters is sending HTML e-mail to this list (not to mention top-replying), which generates unnecessary network traffic. Some people pay for every bit downloaded, so they're paying for the same information twice, because the e-mails are sent with multipart/alternative format, which contains BOTH text/plain and text/html. One thing I noticed those senders have in common is that they use Gmail. So, a plea to Gmail users: please stop sending HTML e-mail to Fedora mailing lists. Regards, Dominik (who still reads e-mail in text mode in a terminal) -- Fedora https://getfedora.org | RPMFusion http://rpmfusion.org There should be a science of discontent. People need hard times and oppression to develop psychic muscles. -- from "Collected Sayings of Muad'Dib" by the Princess Irulan

2 years, 1 month

14
15
0 / 0

Blocking criteria proposal for F30+: Printing

by Stephen Gallagher

There was a bug[1] filed recently that indicated that printing was broken on certain printers. As a result of that discussion, it became apparent that there was no criteria for printing to work at all, which seems like an oversight. I discussed this briefly with Matthias Clasen this morning and he agreed that this should be treated as blocking for Workstation. I'd like to propose that we add the following criteria to Beta for Fedora 30+: * Printing must work on at least one printer available to Fedora QA. "Work" is defined as the output from the device matching a preview shown on the GNOME print preview display. (Note that differences in color reproduction are not considered "non-working".) and this to Final for Fedora 30+: * Printing must work on at least one printer using each of the following drivers: (I don't know which ones to specify here, but we ought to try to figure out a cross-section that covers a large swath of our expected user base). [1] https://bugzilla.redhat.com/show_bug.cgi?id=1628255

2 years, 1 month

9
22
0 / 0

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

devel October 2018