[EPEL-devel] Re: Owncloud updates

> "SJS" == Stephen John Smoogen writes: SJS> My question is how slow is slow. They are looking to do monthly or SJS> faster updates of OwnCloud with non-skippable schema changes each SJS> update. Uh Do they at least store a schema version or something so that the

Re: No Rich boolean deps in Requires/Recommends for f24

> "PP" == Petr Pisar writes: PP> This changes meaning regarding to F25. Previous text banned rich PP> strong dependencies in F24 only. This current text extends the ban PP> to all Fedoras. PP> Is that intentional? It's currently correct according to FESCo's request as I

Re: Koschei eating Koji?

> "RS" == Richard Shaw writes: RS> I've noticed general sluggishness of the Koji web interface and a RS> large number of Koschei builds in process. Is this what's causing RS> the problem? It is not. There is an ongoing issue with the backend database server. - J< --

Re: introducing curl-minimal and libcurl-minimal RPM packages

> "KD" == Kamil Dudka writes: KD> Exactly. libcurl conflicts with libcurl-minimal, which means that KD> exactly one of them will be installed on any Fedora system at a KD> time. On a regular system (server, desktop, etc.) it will always be KD> libcurl. But... we don't

Re: introducing curl-minimal and libcurl-minimal RPM packages

> "JLT" == Jason L Tibbitts writes: JLT> Using a different soname and patching python-pycurl to use the JLT> maximal module if present and the minimal module otherwise would be JLT> another possibility, assuming it's even doable. Or, even easier, having

Re: No Rich boolean deps in Requires/Recommends for f24

> "KF" == Kevin Fenzi writes: KF> At today's FESCo meeting we decided to ask maintainers to not use KF> rich boolean Requires/Recommends for the time being until tooling KF> can catch up and allow us to push updates with them. Could someone look over the language in

Re: [Guidelines change] Changes to the packaging guidelines

> "RD" == Rex Dieter writes: RD> Perhaps fpc folks missed my recent related post: That change was actually made quite some time before I sent the announcement. Sometimes I get behind. - J< -- devel mailing list devel@lists.fedoraproject.org

[Guidelines change] Changes to the packaging guidelines

Here are the recent changes to the packaging guidelines. - The use of rich (or Boolean) dependencies is now OK for F23+. * https://fedoraproject.org/wiki/Packaging:Guidelines#Rich.2FBoolean_dependencies * https://fedorahosted.org/fpc/ticket/593 - The ban on the use of the

[Guidelines change] Changes to the packaging guidelines

Here are the recent changes to the packaging guidelines. - The section on the use of pregenerated code was amended to indicate the preference for having tools necessary to regenerate such code be free software and packaged in Fedora. * https://fedoraproject.org/wiki/Packaging:Guidelines *

Re: [Fedora-legal-list] Re: Policy change on emulators

> "TC" == Tom Callaway writes: TC> That's a very strange situation, but I don't think it would affect TC> inclusion of openmw in Fedora. I would think that it requiring S3TC would be more of a blocker. But then again, maybe it's possible for someone to cook up their

Re: Improvements of Fedora Sponsorship process

I wanted to elaborate on one of the ideas I threw out during that discussion. We (need to|should|strive really hard to) treat new packagers more like new volunteers for fedora infrastructure. Except that we should accept that packaging is really, really hard when you don't know where to start

Re: F25 System Wide Change: Automatic Provides for Python RPM Packages

> "JR" == Jaroslav Reznik writes: JR> * Proposal owners: Prepare a draft for the Fedora Packaging JR> Guidelines for Python Please open a ticket with FPC sooner rather than later, even if the draft isn't ready/started. - J< -- devel mailing list

Re: Fixing /.autorelabel

> "PL" == Petr Lautrbach writes: PL> (2) when a generator file was mislabeled it could not be run by PL> systemd as systemd can't read fedora-relabel unit file now Isn't it possible to detect that situation and simply force the relabel? - J< -- devel mailing list

Re: [Guidelines change] Changes to the packaging guidelines

> "TK" == Tomasz Kłoczko writes: TK> And now someone should add to git filtering off above, process all TK> spec files in git repos and commit necessary changes adding in TK> commit comment link to updated guidelines. Yes, I have some scripts brewing but I am not

Re: fedorahosted.org sunset is next week!

> "KF" == Kevin Fenzi writes: KF> http://www.scrye.com/~kevin/fedora/sourcecheck/ And also https://pagure.io/fedora-source-url-check - J< ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to

Re: Spec files maintained in external source control: *please* mention this in the spec file

> "AW" == Adam Williamson writes: AW> Hi folks! So I got bitten again today by the situation where the AW> primary contact for a given package considers the 'canonical' source AW> for the spec file to be some external SCM, and finds it a problem AW> when someone

Re: Spec files maintained in external source control: *please* mention this in the spec file

> "ZJ" == Zbigniew Jędrzejewski-Szmek writes: ZJ> Indeed. I changed the status. (I feels a bit presumptuous to tell ZJ> the FPC when exactly they have to discuss something, but if it's ZJ> that's what it takes, then OK.) trac unfortunately doesn't have any facility for

[Guidelines change] Changes to the packaging guidelines

Here are the recent changes to the packaging guidelines. - The systemd section of the scriptlet guidelines was updated to indicate situations where the %systemd_ordering macro may be used instead of %systemd_requires. * https://fedoraproject.org/wiki/Packaging:Scriptlets#Systemd *

Re: [Guidelines change] Changes to the packaging guidelines

Oops, one additional change was made which I left out of the previous announcement. A section was added to the Python guidelines describing the automatic generation of Provides: which was added in Fedora 25. Descriptions of three new macros were also added. *

Re: F26 Self Contained Change: Making sudo pip Safe (Again)

> "JK" == Jan Kurik writes: JK> We aim to move the working directory for sudo pip3 to a more JK> appropriate location: /usr/local/lib/pythonX.Y/site-packages, and JK> modify the Python 3 interpreter in Fedora to scan both above JK> mentioned locations when importing

Re: Bodhi broken now?

> "JH" == James Hogarth writes: JH> Well pkgdb is stating "Sorry! This service is currently JH> unavailable." so I expect something has gone boom in the JH> infrastructure especially since koji says "ActionNotAllowed: policy JH> violation (build_from_srpm)" That's

Re: My experiences with KillUserProcesses=yes on F24

> "NK" == Nico Kadel-Garcia writes: NK> To me, it looks like systemd is activating a universal policy which NK> you, and others, need more thoughtful and tunable handling for. NK> Attempting to tune it by outsmarting systemd's default behavior NK> looks expensive and

My experiences with KillUserProcesses=yes on F24

After reading (some of) the "discussion" about systemd-logind's KillUserProcesses setting, I decided that I'd like to try enabling it and see how it works and how I can make it useful in my environment. Sorry, it's long, but I though folks might want to know. Disclaimer: I quite like systemd and

Re: My experiences with KillUserProcesses=yes on F24

> "JLT" == Jason L Tibbitts writes: JLT>I've found that if the user's user manager dies (for any reason JLT>you might choose) and linger is enable for them, a new one won't JLT>be started at login. They have to disable linger, log out, and JLT>log back in.

Triaging RH Bugzilla and forwarding bugs upstream (Was: F24, small backward steps)

> "RC" == Ralf Corsepius writes: RC> IMO, it should be mandatory for Fedora maintainers to look into RH RC> Bugzilla, because that's the product they are "maintaining" and what RC> users are using. I disagree in general; when the bug volume exceeds a certain amount

Re: How to obsolete a subpackage?

I would suggest everyone interested follow the relevant FPC ticket. I've just added https://fedorahosted.org/fpc/ticket/645#comment:11 which probably isn't complete but at least gives us a start. - J< -- devel mailing list devel@lists.fedoraproject.org

Re: Triaging RH Bugzilla and forwarding bugs upstream

> "RC" == Ralf Corsepius writes: RC> - A package triggering too many BZs. RC> IMO, this should question the package's quality. A package with a million users is going to get more bugs than a package with ten regardless of the package quality. I have a feeling that a

Re: [Fedora-packaging] Re: Broken dependencies: vim-syntastic

> "PR" == Pavel Raiskup writes: PR> What's should packager do in such case? Recap: noarch package PR> depends on arch-dependant package, which is not available PR> everywhere. Then the package is not noarch. Make it archful, add ExcludeArch: appropriately. - J<

Re: [Fedora-packaging] Re: Broken dependencies: vim-syntastic

First off, the guidelines have: https://fedoraproject.org/wiki/Packaging:Guidelines#Noarch_with_unported_dependencies I've been assuming that you're talking about the BuildRequires: case. If you're just talking about the case where you can build it anywhere because you're just copying files

Re: [Fedora-packaging] Re: Broken dependencies: vim-syntastic

> "PR" == Pavel Raiskup writes: PR> Here comes the same argument as with ExclusiveArch .. I don't want PR> to, because this _is_ noarch package and _is_ expected to work on PR> all arches, at some point. It's not noarch, sorry. It doesn't work on all architectures,

Re: [Fedora-packaging] Re: Broken dependencies: vim-syntastic

> "PR" == Pavel Raiskup writes: PR> The design issue (probably hard to solve) is that there is no PR> automatic way to _not_ include such package into particular ARCH yum PR> repo; and we rather bother packagers. I'm not entirely sure how the compose tools would that a

[Guidelines change] Changes to the packaging guidelines

Here are the recent changes to the packaging guidelines. - The Filesystem Layout section of the guidelines was simplified and outdated information was removed. * https://fedoraproject.org/wiki/Packaging:Guidelines * https://fedoraproject.org/wiki/Packaging:Guidelines#Filesystem_Layout *

Re: Broken: Firefox 48 + Private Tab + Kerberos SSO

> "RM" == Robert Marcano writes: RM> I wonder if the default setting for RM> network.negotiate-auth.trusted-uris=https:// is or isn't a leak. My understanding (from talking to npmccallum and ab/abbra at flock) is that the security and disclosure issues with that

Schedule for Thursday's FPC Meeting (2016-09-22 17:00 UTC)

Note the time change! Also note that James is out this week so I'll be bumbling the way through the meeting process. Following is the list of topics that will be discussed in the FPC meeting Thursday at 2016-11-03 17:00 UTC in #fedora-meeting-1 on irc.freenode.net. (Local time info omitted at I

Removal of the default 16 job limit for makefile parallelism

The hardcoded upper limit of 16 jobs, passed to make via "-j" when you use either %make_build or make %{?_smp_mflags} in the %build section of your specfiles, is going away in rawhide. This may result in your jobs being run with additional parallelization in some situations. This change will

Re: [Fedora-packaging] Re: Packaging udev rules

> "SB" == Sérgio Basto writes: SB> Anyway we should add some instructions in guidelines about this SB> matter, even if we don't need add nothing in %post etc   That would be great, but someone who knows all of the details would need to actually provide a draft. Or at

Re: Recommended upgrade procedure for >1 release upgrades

> "AW" == Adam Williamson writes: AW> (Interestingly, there is actually a way to solve this AW> *retroactively*: the other week I was kicking around the idea of AW> setting up a third-party repo containing a single package named AW> fedora-obsoletes which just

Re: Recommended upgrade procedure for >1 release upgrades

> "AW" == Adam Williamson writes: AW> Meh, I disagree. It a reasonable point, but there were strong opinions against forced removal of packages in the manner you propose. This did go through FESCo as well. AW> Personally, though, I think any non-maintained

Re: program requires SELinux policy to write to ~/.cache directory

> "RC" == Ralf Corsepius writes: RC> People seem to have forgotten that homes are completely out of a RC> distro's control. They are not guaranteed to be on a local RC> filesystem or on an SELinux-enabled filesystem and are not RC> standardized by any standard

Re: pkgdb: Could not save the request for branch: master, has it already been requested?

> "SM" == Sandro Mani writes: SM> Hi I filed the request to unretire eigen2, but I accidentally SM> specified only the rhbz ticket number instead of the full URL so it SM> got denied with "Invalid review BZ". I now tried filing a new SM> unretirement request with the

Re: How attached are we to branch ACLs? -- Should we kill pkgdb?

> "PC" == Pierre-Yves Chibon writes: PC> So, does per-branch ACLs make sense to you? Have you had cases where PC> you thought it was good/bad? More importantly, have you had cases PC> where you would want to give someone access to just one branch and PC> really really do

Re: How attached are we to branch ACLs? -- Should we kill pkgdb?

I also wanted to add that a small bit of ACL flexibility is a very small cost if we gain what Pagure offers. Easy personal package forks. Pull requests for packages. I'd give up more than per-branch ACLs for that, certainly. - J< ___ devel mailing

[Guidelines change] Changes to the packaging guidelines

Here are the recent changes to the packaging guidelines. The guidelines on versioning packages were completely rewritten in order to make them (hopefully) more comprehensible. This rewrite was not intended to introduce functional changes, but during the draft process the following small

Re: [Guidelines change] Changes to the packaging guidelines

> "JW" == Jonathan Wakely writes: JW> Sure. I was checking whether I should make the change myself, not JW> complaining it hadn't been done. You are of course welcome to change any page that isn't in one of the protected hierarchies (Packaging:, Legal:). We

Re: Package with spec name != packagename.spec

> "SM" == Sandro Mani writes: SM> So just for curiosity, does the tooling allow an arbitrary name for SM> the specfile and does it just pick the first one it finds when SM> building the SRPM? There is no one "tooling". fedpkg/pyrpkg will try to find the spec named

Re: [Guidelines change] Changes to the packaging guidelines

> "JW" == Jonathan Wakely writes: JW> The template at JW> https://fedoraproject.org/wiki/How_to_create_an_RPM_package#SPEC_templates_and_examples JW> still shows %install cleaning the buildroot as the first step, JW> should that be corrected? There are probably any

Re: Default location for addons AppStream metadata has changed

> "AP" == Alexander Ploumistos writes: AP> As far as I can tell that change went mostly unnoticed, given that AP> most of our packages still install addon metadata in AP> %{_datadir}/appdata/. I visited the relevant wiki page[1] which AP> %still AP> lists the old

Re: [Fedora-packaging] Bundled Provides Libraries and Versioning

> "AM" == Adam Miller writes: [...] AM> RPMs currently in Fedora (a reported 244 in Rawhide currently) that AM> are defining a `Provides: bundled() = ` but excluding AM> the version completely[0][1]. This removes that ability to properly AM> perform source code

Re: [Fedora-packaging] Bundled Provides Libraries and Versioning

of a particular piece of software. - J< RB> ___ devel mailing list RB> -- devel@lists.fedoraproject.org To unsubscribe send an email to RB> devel-le...@lists.fedoraproject.org -- Jason L Tibbitts III - ti...@math.uh.edu - 713/743-3486 - 660PGH System

Re: Coming soon: Pagure service for dist-git

> "MM" == Matthew Miller writes: MM> This might be an awful idea, but what if we have a proven packager MM> run a script to drop a README.md into each dist-git repo, with some MM> default template content (possibly including the %description)? Well, it's useful as

Re: F27 Self Contained Change: Authselect: new tool to replace authconfig

> "JR" == Jaroslav Reznik writes: JR> At the same time, some obsolete features of authconfig JR> would not be supported by authselect. I have a couple of concerns about this. First, this seems to impact anaconda/kickstart since the "authconfig" line basically _is_ an

Re: Coming soon: Pagure service for dist-git

> "MM" == Matthew Miller writes: MM> Or as an interim, show the spec file? This is actually a great opportunity for providing information about how a package is maintained. So those with the "don't touch MY packages" attitude have a place to document this. But

Re: F27 System Wide Change: Graphical Applications as Flatpaks

> "OT" == Owen Taylor writes: OT> If Fedora packages just hardcoded FHS paths, then all the path OT> macros wouldn't be necessary to start with! Actually we've been making those really annoying macros more and more optional over time. The only one which is mandatory is

Re: F27 System Wide Change: Graphical Applications as Flatpaks

> "OT" == Owen Taylor writes: OT> The issue with this is that nobody has yet figured out how to handle OT> OSTree repositories within the Fedora mirror infrastructure. While OT> OSTree repositories can be mirrored efficiently, they can't be OT> mirrored efficiently by

Re: Approved packages that never get imported?

> "MS" == Michael Schwendt writes: MS> The ticket blocks FE-NEEDSPONSOR. No idea why you've approved the MS> review officially, setting the fedora-review+ flag without being MS> able to sponsor the new contributor. Because that is perfectly acceptable. It is not

Re: Kernel 4.12 rebase plans

> "JF" == Justin Forbes writes: JF> Fedora 26 will get the 4.12.3 stable kernel update sent to JF> updates-testing in the next couple of days. Shortly afterwards JF> Fedora 25 will get a 4.12 update as well. Fedora 24 will remain on JF> 4.11 until the end of life. FYI,

Re: Approved packages that never get imported?

> "MS" == Michael Schwendt writes: MS> setting fedora-review+ hides the ticket from the needsponsor tracker MS> queue. You've deleted that part when quoting me. Why? Because it's not relevant to the point I was making. - J<

Re: Mass rebuild failures only on ppc64le: glibc problem?

> "FW" == Florian Weimer writes: FW> I'm doing scratch builds, and I think they are kind of difficult to FW> see in Koji. Yeah, you can see them in the task list when they're active. I see the one you're running now. Still, if you are running into problems and need me

Re: Mass rebuild failures only on ppc64le: glibc problem?

> "FW" == Florian Weimer writes: FW> I think I have a workaround, but I'm blocked by this koji CLI bug: You can always ask someone else to do a build for you; just let me know if you need that done. I don't see any recent koji jobs submitted by you, nor any recent glibc

Re: icemon: icecream monitor - reviving a dead review

> "MC" == Michael Cullen writes: MC> - would it be better to create a new review ticket or take over the MC> existing one? Please create a new ticket and close the old one as a duplicate. That way the original submitter can remove their address from the CC

Mass rebuild failures only on ppc64le: glibc problem?

I noticed one of my packages failed to build because the test suite failed, but only on ppc64le. builddir/build/BUILD/cyrus-imapd-3.0.2/cunit/.libs/lt-unit: error while loading shared libraries: /builddir/build/BUILD/cyrus-imapd-3.0.2/imap/.libs/libcyrus_imap.so.0: expected localentry:0

Re: Mass rebuild failures only on ppc64le: glibc problem?

I'm also seeing builds failing early in %build. It appears that libcurl has a similar problem and so cmake won't run: /usr/bin/cmake: error while loading shared libraries: /lib64/libcurl.so.4: expected localentry:0 `pthread_mutex_destroy' RPM build errors: - J<

Re: Proposed Mass Bug Filing: Renaming "python-" binary packages to "python2-"

> "AW" == Adam Williamson writes: AW> Right, that's a good point. *Why* exactly do we want to go to all AW> the trouble involved in making a switchover from 'python-foo' AW> meaning 'the Python 2 module called foo' to meaning 'the Python 3 AW> module called foo'?

Re: Proposed Mass Bug Filing: Renaming "python-" binary packages to "python2-"

> "AW" == Adam Williamson writes: AW> That seems like, frankly, quite a weak justification for all the AW> trouble that's involved in migrating the 'meaning' of python-foo AW> like this (and, as Smooge pointed out, potentially doing it *again* AW> for Python 4, if

Re: Proposed Mass Bug Filing: Renaming "python-" binary packages to "python2-"

First off, I really want to say that we should resist the idea that Red Hat product decisions should hold back Fedora's progress. This python-*/python2-*/python3-* mess has been with us for far too long, and I applaud the Python SIG for putting in the effort to try and get this regularized.

Re: Finalizing Fedora's Switch to Python 3

> "MH" == Miro Hrončok writes: MH> I just had a discussion with Tomáš Orsava and Petr Viktorin on MH> #fedora-python. Rather than asking FESCo now to allow mass MH> fully-automated spec changing, we'll open bugs as planned, but we'll MH> attach patches generated by your

Re: tcp_wrappers deprecation

For the record, denyhosts currently relies upon the tcp_wrappers functionality in openssh to function. While it's possible to make it manipulate the firewall as well, the whole situation is kind of a mess. (Does it talk to firewalld? What if you're not running firewalld?) Sadly I know how

Re: Requesting for contact info for Nethack maintainer

> "RO" == Ron Olson writes: RO> Hi all- I've been trying to follow the guidelines for assuming RO> responsibility for a package per RO> https://fedoraproject.org/wiki/Policy_for_nonresponsive_package_maintainers RO> and am on step 4, asking if anyone knows how to

Re: Requesting for contact info for Nethack maintainer

> "RO" == Ron Olson writes: RO> I did request access but the page gave me a catch-22 of needing to RO> be in a particular group to continue; it was awhile ago at the end RO> of last year and I kind of dropped it, but since I've been playing RO> more Nethack on my

Re: Requesting for contact info for Nethack maintainer

> "RO" == Ron Olson writes: RO> Sorry, right, I'm trying to become a packager. Funny enough, I use RO> IRC every day; what room should I join (I'm assuming Freenode). #fedora-devel on freenode is the place. Feel free to ask any questions you might have there. I'll

Re: F27 System Wide Change: Parallel Installable Debuginfo

> "MW" == Mark Wielaard writes: MW> I believe this has always been a hidden directory name that is MW> expected to be called that way by various tools. I don't recall having seen it before, and I've been doing packaging work for a very long time. The confusion about

Re: Proposed Mass Bug Filing: Renaming "python-" binary packages to "python2-"

> "JLT" == Jason L Tibbitts writes: JLT> Before doing that, please post a list of packages and their JLT> maintainers to the devel list. Preferably you would post two JLT> lists: one in the form: JLT> package owner1 owner2 owner2 JLT> And another in the form JLT> owner

Re: Proposed Mass Bug Filing: Renaming "python-" binary packages to "python2-"

I'm actually revising the mass bug filing page at the moment. - J< ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: Proposed Mass Bug Filing: Renaming "python-" binary packages to "python2-"

> "IS" == Iryna Shcherbina writes: IS> The packages that violate the above-mentioned policies are being IS> tracked in portingdb [3] and we plan to start filling bugs soon. Before doing that, please post a list of packages and their maintainers to the devel list.

Re: F27 System Wide Change: Parallel Installable Debuginfo

I know the boat has sailed on this and no amount of complaining will help at this point, but I want to make sure this gets on the record wherever this feature is proposed. > "JK" == Jan Kurik writes: JK> * build-id file /usr/lib/debug/.build-id/xx/...yyy which is a

Re: Proposed Mass Bug Filing: Renaming "python-" binary packages to "python2-"

> "IS" == Iryna Shcherbina writes: IS> Thanks a lot, that is helpful. There is also a pkgdb2client [0] IS> package that I've been looking into for this. You could run that tool in a loop, parse the result and generate the report, I guess, but it's also rather trivial to

Re: F27 System Wide Change: Rsyslog log format change proposal

> "ZJ" == Zbigniew Jędrzejewski-Szmek writes: ZJ> I you post the code somewhere, I could have a look. It's in the upstream "journal" branch of the denyhosts source: https://github.com/denyhosts/denyhosts/tree/journal

Guidelines change] Changes to the packaging guidelines

Here are the recent changes to the packaging guidelines. - The guidelines for enabling services by default modified to indicate that FESCo approval is required for services which change the behavior of other services. * https://fedoraproject.org/wiki/Packaging:DefaultServices#Restrictions *

Re: F27 System Wide Change: Rsyslog log format change proposal

> "TT" == Tomasz Torcz writes: TT> fail2ban works with journal. BTW, sshguard (which is similar to TT> fail2ban) works woth journal, too. Denyhosts doesn't use the journal, though I have a branch which does. Sadly I never could figure out why iterating over a

Denyhosts journal reads (Was: F27 System Wide Change: Rsyslog log format change proposal)

[I trimmed the CC list and changed the subject.] > "ZJ" == Zbigniew Jędrzejewski-Szmek writes: ZJ> IIUC, the code does a sleep loop, and does not use polling. So it's ZJ> not particularly efficient, but it should work. You are probably right; I had forgotten how I'd

Re: Denyhosts journal reads

> "ZJ" == Zbigniew Jędrzejewski-Szmek writes: ZJ> BTW., a debugging hint: if you need to generate a scenario where ZJ> there data is flowing in and journal files get rotated, it's easier ZJ> to use systemd-journal-remote and either feed it data from an ZJ> existing

Re: [HEADS UP] %add_maven_depmap macro deprecated and moved to javapackages-local

> "MŠ" == Michael Šimáček writes: MŠ> With upcoming version of javapackages-tools there will be changes to MŠ> %add_maven_depmap macro: I believe this would need to be reflected in the packaging guidelines. At least %add_maven_depmap is mentioned twice, once as an

Re: [HEADS UP] %add_maven_depmap macro deprecated and moved to javapackages-local

Also, ugh, please don't crosspost to closed mailing lists. - J< ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: Migrating sub-package to a different package: How to resolve file conflicts

> "MM" == Matthew Miller writes: MM> All other things aside, this is pragmatically easier, because MM> creating a new package4 or package5 triggers a new package review. That's not actually the case, though: https://fedoraproject.org/wiki/Package_Review_Process

Re: Migrating sub-package to a different package: How to resolve file conflicts

> "MM" == Matthew Miller writes: MM> Thanks for the correction! Sure. It seems a lot of people miss this, though I tried to announce it loudly back when it changed (in August). I've been trying to cut down on the bureaucracy, and a package that needs to add a

Re: Retiring Packages with Broken Dependencies in branched (2017-06-12)

> "PR" == Pavel Raiskup writes: PR> But I would be OK with this solution - if this idea was baked into PR> guidelines first. Is it realistic to ratify new guidelines PR> paragraph for this issue before F26? The packaging committee can certainly get guideline changes

Re: tcp_wrappers deprecation

> "JJ" == Jakub Jelen writes: JJ> The denyhosts got last update also 10 years ago [2] and we already JJ> have quite much 2 alternatives that can do the same using firewalls, JJ> so it might be also a time to go for denyhosts. Or not, but clearly JJ> document that OpenSSH

Re: Package add request

> "HV" == Hedayat Vatankhah writes: HV> I'd say to stick with upstream naming, which is the Fedora HV> way. Changing the names to lower case is a must in Debian, they HV> simply don't allow upper case letters to be in package names. The HV> developer clearly prefers

Re: [Fedora-packaging] Re: Package naming question

> "JA" == Jun Aruga writes: JA> Perl: perl-foo Python: python-foo NodeJs (NPM): nodejs-foo Ruby: JA> rubygem-foo R: R-foo PHP: php-foo Golang: golang-foo Those are all for libraries in the given language. JA> The prefix pattern "rust-parallel" looks better. This is not

Re: request admin access for gnumeric

> "GT" == Globe Trotter writes: GT> Hello, I have commit privileges for EPEL 7 for gnumeric. I recently GT> got a request to upgrade gnumeric. I went through and created the GT> rpm as usual and have now realized that I do not have commit GT> privileges for Fedora 27.

Re: request admin access for gnumeric

> "GT" == Globe Trotter writes: GT> Yes, indeed: aarem is me. So, I thought that I did not have GT> privileges because when I git push, I get the following: I have limited admin privileges, but one of the things I can do is see the gitolite configuration and... it

Re: Fedora 27 is officially released!

> "V" == Vascom writes: V> Most impatient can rebuild it from rawhide srpm. It is basically never necessary to rebuild the rawhide kernels from source. Kernels are broadly compatible between Fedora releases, at least in one direction. In the vast majority of cases you

[Guidelines change] Changes to the packaging guidelines

Here are the recent changes to the packaging guidelines. - Following releng approval, the restrictions on the use of rich/Boolean dependencies have been lifted. * https://fedoraproject.org/wiki/Packaging:Guidelines#Rich.2FBoolean_dependencies *

Re: /bin/sh and lua; was: Re: common location of spec files in upstream sources

> "RPH" == R P Herrold writes: RPH> I was referring to: section 37 ("Scripting inside of spec files ") RPH> https://fedoraproject.org/wiki/Packaging:Guidelines#Scripting_inside_of_spec_files Well, OK. I mean, Lua is right there so I'm not sure why you say it would

Re: Taskotron test failures (dist.rpmlint)

> "AP" == Alexander Ploumistos writes: AP> /usr/bin/python: can't open file '/usr/lib/rpm/python-macro-helper': AP> [Errno 2] No such file or directory For the record, this happens because rpmlint does the equivalent of: rpm -E %python_sitearch by calling the

Re: Adding Obsoletes to generated -debuginfo packages ?

> "DPB" == Daniel P Berrangé writes: DPB> How can I get the auto-generated DPB> libvirt-daemon-driver-libxl-debuginfo RPM to have an "Obsoletes: DPB> libvirt-daemon-driver-xen-debuginfo < 4.3.0" statement ? It seems DPB> impossible, meaning users with debuginfo have a

Re: F29 System Wide Change: Move /usr/bin/python into a separate package

> "CD" == Christian Dersch writes: CD> For me this change is just an unnecessary additional change which CD> will probably annoy users. I'm struggling to see how anyone but packagers (whose packages already don't meet the requirements against not directly using

Git hook for messaging based on specfile content (Was: F29 System Wide Change: Move /usr/bin/python into a separate package)

> "PC" == Pierre-Yves Chibon writes: PC> We have a git hook in place for commit adding/removing exclusie-arch PC> and alike for the alternative arch folks. I guess we could tweak it PC> to inform the python-sig (for example) about commits adding/removing PC> this

Re: F29 System Wide Change: Move /usr/bin/python into a separate package

> "RB" == Randy Barlow writes: RB> I don't disagree, but I will point out that it is possible to find RB> out which packages are using /usr/bin/python by looking at their RB> most recent test results in resultsdb. Could you fill us in a bit? The only thing I

Re: F29 System Wide Change: Move /usr/bin/python into a separate package

> "RB" == Randy Barlow writes: RB> https://taskotron.fedoraproject.org/resultsdb/results?testcases=dist.python-versions.python_usage This one seems on-point. rpm 4.14.1-9.fc28 fails: https://taskotron.fedoraproject.org/resultsdb/results/21327930 Is it

<    1   2   3   4   5   6   7   >