Re: Nonresponsive maintainer: Björn Esser (besser82)

[Miro Hrončok]

On 01. 11. 18 7:48, Jan Pokorný wrote:

On 27/08/18 08:41 +0200, Matthias Runge wrote:

On Fri, Aug 17, 2018 at 03:48:12PM +0200, Bob Mauchin wrote:

On Fri, Aug 17, 2018, 12:53 Leigh Scott 
wrote:


Besser82 hasn't answered  any of my emails for months.



I saw him back in May for a couple of reviews, maybe he's in holidays.



I briefly contacted Björn, and he promised to get back here.


Any signs of his activity, yet?


There was a "wait for October" call from Björn.
Later I've seen no activity.


I'd be interested in (co)maintenance of one of his packages,
tried contacting him over email (less than a day ago), then
realized I could check this ML.


Claim the package in https://pagure.io/releng/issues

Link https://pagure.io/fesco/issue/1971

--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
___
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: Translating the banner text

[Mattia Verga]

Il 10/31/18 6:03 PM, mcatanz...@gnome.org ha scritto:
>
> Just want to add: the banners don't really look great, and it'd be nice
> to see them removed from the installer (or replaced). First there's the
> hot dog, which is fun but not very professional. Then the Rhythmbox one
> where "Music" gets cut off after "Mus" because the full width of the
> banner is not displayed
>
I had opened a bug for that a year ago
https://bugzilla.redhat.com/show_bug.cgi?id=1506955

but I've just realized it was filled in the wrong component.

Now I've reassigned it to the design team. You can also post this ticket 
on the design-team mailing list to make them aware of it.

Mattia

___
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: Enabling powerline theme system wide by default

[Michal Konecny]

+1

I'm installing powerline as first think on Fedora for tmux, vim and fish.

On 01/11/18 01:13, Luya Tshimbalanga wrote:

It will be nice to enable powerline theme by default system and user
wide. Simple reason is refresh the look of terminal while also providing
useful information especially for git branch. Since powerline does not
impact the performance, it will be great to set for Fedora 30.

Comments welcome.

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: Use immutable CRAN URLs

[Nicolas Mailhot]

Le mercredi 31 octobre 2018 à 21:31 +0100, Iñaki Ucar a écrit :
> On Wed, 31 Oct 2018 at 21:22, Iñaki Ucar 
> wrote:
> > while the R package name is TH.data, not TH-data. I see that the
> > SPEC
> > says "# Cannot use . in name", but this is clearly not true (maybe
> > it
> > was true long ago?).
> 
> Well... the guidelines for Python state: 'Note that when a module that
> has a dot in its name, the usual rule about changing "." to "-"
> applies.' But the guidelines for R say nothing about that, and as a
> result, most packages with a dot don't change it. Maybe R-TH-data is
> the only one that is compliant after all? :)

And the guidelines also say to lowercase by default…

So my packagename computing macros just do this nowadays (aside from
adding the correct prefix or suffix)

  r = string.gsub(r, "[%p%s]+", "-")
  r = string.gsub(r, "^-", "")
  r = string.gsub(r, "-$", "")
  r = string.lower(r)

-- 
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

Re: IBM buying RedHat

[Richard W.M. Jones]

On Sun, Oct 28, 2018 at 05:32:52PM -0400, Neal Gompa wrote:
> Red Hat has been a company I've admired since I got into Linux back in
> 2000. I genuinely worry that IBM will smother Red Hat and kill one of
> the largest producers of awesome FOSS with its bureaucratic
> proprietary-ness.

I wrote this yesterday on HN:

  > Will Red Hat's acquisition hurt fedora? 

  In a word, no. It would be crazy for IBM to put at risk Red Hat's
  proven and highly profitable development model, and that all starts
  with Fedora.

Of course no one knows, and maybe IBM will kill Fedora, but I think
they would have to be especially stupid to do that and (despite what
you read) they are not stupid.

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: Enabling powerline theme system wide by default

[Nicolas Mailhot]

Le mercredi 31 octobre 2018 à 17:13 -0700, Luya Tshimbalanga a écrit :
> It will be nice to enable powerline theme by default system and user
> wide. Simple reason is refresh the look of terminal while also
> providing
> useful information especially for git branch. Since powerline does not
> impact the performance, it will be great to set for Fedora 30

If someone wants to do this the font powerline uses should be fixed to
used correct unicode point values (and PUA when it include things not
standardised by unicode).

Otherwise powerline display is just broken on many terminals

Regards,

-- 
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

Re: Nonresponsive maintainer: Björn Esser (besser82)

[Jan Pokorný]

On 01/11/18 08:30 +0100, Miro Hrončok wrote:
> On 01. 11. 18 7:48, Jan Pokorný wrote:
>> I'd be interested in (co)maintenance of one of his packages,
>> tried contacting him over email (less than a day ago), then
>> realized I could check this ML.
> 
> Claim the package in https://pagure.io/releng/issues
> 
> Link https://pagure.io/fesco/issue/1971

Thanks for the pointers, applied: https://pagure.io/releng/issue/7901

-- 
Jan (Poki)


pgpInx6_0_2n9.pgp
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

Re: Enabling powerline theme system wide by default

[Brian (bex) Exelbierd]

On Thu, Nov 1, 2018 at 9:48 AM Michal Konecny  wrote:
>
> +1
>
> I'm installing powerline as first think on Fedora for tmux, vim and fish.
>
> On 01/11/18 01:13, Luya Tshimbalanga wrote:
>
> It will be nice to enable powerline theme by default system and user
> wide. Simple reason is refresh the look of terminal while also providing
> useful information especially for git branch. Since powerline does not
> impact the performance, it will be great to set for Fedora 30.

+1 - this is a great way for us to differentiate our desktop and
provide a useful out of box experience for developers.  I realize it
won't be 100% useful to everyone, but it moves us to an opinionated
system :).

regards,

bex

>
> Comments welcome.
>
> 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



-- 
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

FOSDEM 2019 - Distributions Devroom Call for Participation

[Brian (bex) Exelbierd]

Note: Funding is probably available for this event for Fedora related
talks and helpers.  Please coordinate with mitzie and/or Mindshare.

Please also distribute this to people and lists which you know would
find it interesting?

Thanks,

bex
---

The Distributions devroom will take place Sunday 3 February 2019 at
FOSDEM, in Brussels, Belgium at the Université Libre de Bruxelles.

As more and more workloads are being considered for containerization in
the future and are finally landing in virtualized environments today,
distributions remain a critical success factor and are more important
than ever. Containers, like virtual machines, are not magical and
rely on piles of software being assembled in a way that is repeatable,
reliable, and functional. This is at the very heart of the problem that
distributions have always solved.

Each distribution is responsible for building, testing, and releasing
software as well as managing the lifecycle of each application in the
collection. Additionally, distributions do very important work in ensuring
that various versions of upstream software work well together and can
co-exist. Distributions are also, often responsible, for "de-vendoring"
upstream software so that security fixes can be applied more quickly.

We welcome submissions targeted at contributors interested in issues
unique to distributions, especially in the following topics:

# Topics and Areas of Focus

## Focus Areas

- The ways that distribution technologies can be leveraged to allow
  for easier creation of a multi-verse of artifacts from single source
  trees. This includes the increasing move toward self-contained
  applications and providing multiple non-parallel installed versions
  of software.

- Efforts being made in shared environments around Build/Test/Release
  cycles.

- Topics related to the delivery problem as it impacts updates in
  terms of both size and rollback/reliability are expected to be featured.

## Additional Topic Ideas

- Distribution and Community collaborations, eg: how does code flow from
  developers to end users across communities, ensuring trust and code
  audibility

- Automating building software for redistribution to minimize human
  involvement, eg: bots that branch and build software, bots that
  participate as team members extending human involvement

- Cross-distribution collaboration on common issues, eg: content
  distribution, infrastructure, and documentation

- Growing distribution communities, eg: onboarding new users, helping
  new contributors learn community values and technology,  increasing
  contributor technical skills, recognizing and rewarding contribution

- Principals of Rolling Releases, Long Term Supported Releases (LTS),
  Feature gated releases, and calendar releases

- Distribution construction, installation, deployment, packaging and
  content management

- Balancing new code and active upstreams verus security updates, back
  porting and minimization of user breaking changes

- Delivering architecture independent software universally across
  architectures within the confines of distribution systems

- Effectively communicating the difference in experience across
  architectures for developers, packagers, and users

- Working with vendors and including them in the community

- The future of distributions, emerging trends and evolving user demands
  from the idea of a platform

Ideal submissions are actionable and opinionated. Submissions may
be in the form of 25 or 50 minute talks, panel sessions, round-table
discussions, or Birds of a Feather (BoF) sessions.

Dates
--
Submission Deadline: 02-Dec-2018 @ 2359 GMT
Acceptance Notification: 7-Dec-2018
Final Schedule Posted: 14-Dec-2018

How to submit
--
Visit https://penta.fosdem.org/submission/FOSDEM19

1.) If you do not have an account, create one here
2.) Click 'Create Event'
3.) Enter your presentation details
4.) Be sure to select the Distributions Devroom track!
5.) Submit

What to include
---
- The title of your submission
- A 1-paragraph Abstract
- A longer description including the benefit of your talk to your target
  audience, including a definition of your target audience.
- Approximate length / type of submission (talk, BoF, ...)
- Links to related websites/blogs/talk material (if any)

Administrative Notes

We will be live-streaming and recording the Distributions Devroom.
Presenting at FOSDEM implies permission to record your session and
distribute the recording afterwards. All videos will be made available
under the standard FOSDEM content license (CC-BY).

If you have any questions, feel free to contact the
devroom organizers: distributions-devr...@lists.fosdem.org
(https://lists.fosdem.org/listinfo/distributions-devroom)

Cheers!

Brian Exelbierd (twitter: @bexelbie) and Brian Stinson (twitter:
@bstinsonmhk) for and on behalf of The Distributions Devroom Program
Committee


-- 
Brian (bex) Exelbierd | bexel...@redhat.com | b...@pobox

Re: FOSDEM 2019 - Distributions Devroom Call for Participation

[Alexander Bokovoy]

On to, 01 marras 2018, Brian (bex) Exelbierd wrote:

Note: Funding is probably available for this event for Fedora related
talks and helpers.  Please coordinate with mitzie and/or Mindshare.

Please also distribute this to people and lists which you know would
find it interesting?

I am definitely interested. FreeIPA is one of solutions that put most
distributions to an extreme in terms of coordination of development,
testing, and delivery of affected packages, as well as defining a
coherent distribution policy around secure defaults on multiple fronts.

I'll submit the talk proposal.
--
/ Alexander Bokovoy
Sr. Principal Software Engineer
Security / Identity Management Engineering
Red Hat Limited, Finland
___
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: IBM buying RedHat

[Nico Kadel-Garcia]

On Tue, Oct 30, 2018 at 4:48 PM Matthew Miller  wrote:
>
> On Sun, Oct 28, 2018 at 07:44:12PM -0400, Neal Gompa wrote:
> > It'd be nice if someone from up top would deign to come and talk to us
> > directly...
>
> Communications are pretty carefully controlled for regulatory reasons, and
> the fact is even those at the top don't know everything yet. And speculation
> is basically right out. That said, I'm working on what I can do here. Are
> there specific things you'd like to ask?

When did the engineering staff know? Will IBM push Red Hat towards, or
away, from their current level of worldwide telecommuting? Whose
management will be in charge on a day to day basis? What will be the
relationship with Fedora? Will Red Hat engineers be as encouraged as
they are now to publish software and fixes to the Fedora releases?
Will the CentOS core development team stay employed by Red Hat? What
is the expected release date for RHEL 8, so I can stop building the
*very* large dependency chains between current Fedora components I
need to backport to RHEL 7 and CentOS 7? Will IBM and Red Hat rein in
the "let's replace another system function into systemd that has
nothing to do with logging or daemon management" ?
___
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

Spam/scam links in bugzilla

[Alexander Ploumistos]

Hello,

A few minutes ago I was notified about a post in a closed bug. It
turns out that the account that made the post has been sporadically
spamming various bugs:
https://bugzilla.redhat.com/page.cgi?id=user_activity.html&action=run&who=dragoelanie%40gmail.com&from=2018-01-01&to=2018-11-01&sort=when
The websites that are being linked to from these posts seem to be of
the support scam garden variety.
I did not know where to report this, hence this message.
Can someone nuke the posts or at least the hyperlinks?
Btw, bugzilla reports that there are multiple accounts with the same
name, so that might be worth looking into.

Regards,
Alex
___
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: Enabling powerline theme system wide by default

[Robert Marcano]

On 10/31/18 8:13 PM, Luya Tshimbalanga wrote:

It will be nice to enable powerline theme by default system and user
wide. Simple reason is refresh the look of terminal while also providing
useful information especially for git branch. Since powerline does not
impact the performance, it will be great to set for Fedora 30.


-1 and say this as a Powerline user. It requires a user level demon just 
to be fast enough rendering the prompt every time, that is more memory 
consumption for something some users will never use (users that don't 
use a terminal). There are lightweight alternatives like powerline-go 
(single process rendering) but still starting it for every rendering is 
not ultra fast either.


I really prefer some kind of subpackage like powerline-system-config 
that could add an something to /etc/profile.d that add a default 
configuration for all non system users instead of telling people to 
adapt their .bash_profile/.bashrc (or preferred shell) scripts




Comments welcome.

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: Spam/scam links in bugzilla

[Stephen John Smoogen]

I have forwarded this to the Bugzilla owner. Thank you for the research on this.
On Thu, 1 Nov 2018 at 08:20, Alexander Ploumistos
 wrote:
>
> Hello,
>
> A few minutes ago I was notified about a post in a closed bug. It
> turns out that the account that made the post has been sporadically
> spamming various bugs:
> https://bugzilla.redhat.com/page.cgi?id=user_activity.html&action=run&who=dragoelanie%40gmail.com&from=2018-01-01&to=2018-11-01&sort=when
> The websites that are being linked to from these posts seem to be of
> the support scam garden variety.
> I did not know where to report this, hence this message.
> Can someone nuke the posts or at least the hyperlinks?
> Btw, bugzilla reports that there are multiple accounts with the same
> name, so that might be worth looking into.
>
> Regards,
> Alex
> ___
> 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: Spam/scam links in bugzilla

[Caolán McNamara]

On Thu, 2018-11-01 at 12:23 +0100, Alexander Ploumistos wrote:
> Hello,
> 
> A few minutes ago I was notified about a post in a closed bug. It
> turns out that the account that made the post has been sporadically
> spamming various bugs:
> 
https://bugzilla.redhat.com/page.cgi?id=user_activity.html&action=run&who=dragoelanie%40gmail.com&from=2018-01-01&to=2018-11-01&sort=when
> The websites that are being linked to from these posts seem to be of
> the support scam garden variety.

hfjkd1...@gmail.com is another one in RH bugzilla, the same scammers
are doing the same to the libreoffice bugzilla too
___
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: Use immutable CRAN URLs

[Iñaki Ucar]

All this would be very useful. CRAN guidelines are pretty strict, and
they are enforced by R packaging and checking tools, and additionally
upon submission to CRAN, with many automatic checks. As a result, and
as you say, most SPEC sections in most packages can be fully
automated, and I think we should tend to that, with proper mechanisms
to treat special cases.

Let me add to your findings from my experience as both R and Fedora
package maintainer:

- Version: As you already found out, there are many version formats
allowed. The only special cases are those using a hyphen, such as
R-uuid, that needs to be substituted with a dot. Other formats may
contain two or three components, year and month... but they don't
require special treatment if there are no hyphens.

- Arch, Requires, BuildRequires, libdir/datadir: As Elliott pointed
out already, archful packages can be detected just by looking into the
DESCRIPTION file, by checking whether the NeedsCompilation flag
exists. If it does, the package must go to libdir and R-devel must be
added as BuildRequires. Furthermore, the LinkingTo field in the
DESCRIPTION file lists packages that must be added as BuildRequires,
such as R-Rcpp-devel. If NeedsCompilation does not exist, the package
must go to datadir, noarch needs to be specified and R-core must be
added as Requires. Further Requires usually are a little bit trickier
to automate and should be managed by us.

- Package devel: This could be automated also. LinkingTo other R
packages is possible if headers are listed under inst/include (in the
sources; the installation path is %{rlibdir}/%{packname}/include) in
those packages. So the R-%packname-devel package must be defined if
such directory exists. There are two flavors for this: packages that
NeedsCompilation, so they are archful, and packages that don't. The
latter are devel-only (see, e.g., R-BH).

- %prep, %build, %install, %check, %files: These can be automated too.
%build (void) and %install are always the same. %prep and %check may
require some tuning (patching, unbundling; defining some exports and
setting some flags in the "R CMD check" command). %files are pretty
standard: there is a basic set, and then other may or may not be
there, such as LICENSE/LICENCE, NEWS/NEWS.md, README/README.md,
Changelog, and CITATION; and directories such as libs and include.

I'm not familiar at all with RPM macros, but I can help with all these details.

On Thu, 1 Nov 2018 at 03:22, Jason L Tibbitts III  wrote:
>
> And with some tweaks to the macro file (current version at
> https://www.math.uh.edu/~tibbs/fedora/macros.test) and the R-uuid
> package is reduced to the following.  Not quite as simple, but it shows
> how you can still split out the individual sections when you need to add
> something, and also cope with a difficult version number.  (I switched
> the argument order around for %cran_source.)
>
> Sadly you still need %build if not using %r_simple_archful_package.  I
> could explain why but
>
> Name: R-uuid
> Version:  0.1.2
> Release:  6%{?dist}
> Summary:  Tools for generating and handling of UUIDs
>
> License:  MIT
> URL:  %cran_url
> Source0:  %cran_source 0.1-2
>
> BuildRequires:libuuid-devel
>
> %description
> Tools for generating and handling of UUIDs (Universally Unique
> Identifiers).
>
> %r_archful_package
>
> %prep
> %r_prep
>
> pushd %{packname}
> rm configure.ac configure src/Makevars.in src/[a-z]*.[ch]
> sed -i -e '/configure/d' -e '/Makevars/d' -e '/src\/[a-z].*.[ch]/d' MD5
> rm -r src/config.h.in src/win32
> sed -i -e '/config.h/d' MD5
> cat > src/Makevars << EOF
> PKG_CFLAGS = \$(shell pkg-config --cflags uuid)
> PKG_LIBS = \$(shell pkg-config --libs uuid)
> EOF
> popd
>
> %build
>
> %install
> %r_install
>
> %check
> %r_check
>
> %files -f %packname.files
>
> %changelog



-- 
Iñaki Ucar
___
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: Use immutable CRAN URLs

[Nicolas Mailhot]

Le jeudi 01 novembre 2018 à 13:36 +0100, Iñaki Ucar a écrit :

Hi,

> - Arch, Requires, BuildRequires, libdir/datadir: As Elliott pointed
> out already, archful packages can be detected just by looking into the
> DESCRIPTION file, by checking whether the NeedsCompilation flag
> exists. If it does, the package must go to libdir and R-devel must be
> added as BuildRequires. Furthermore, the LinkingTo field in the
> DESCRIPTION file lists packages that must be added as BuildRequires,

And that makes it yet another language that needs
https://github.com/rpm-software-management/rpm/issues/104
and the functional part of https://pagure.io/fesco/issue/2004
to be automated properly.

> %files are pretty
> standard: there is a basic set, and then other may or may not be
> there, such as LICENSE/LICENCE, NEWS/NEWS.md, README/README.md,
> Changelog, and CITATION; and directories such as libs and include.

Take a look at
https://copr.fedorainfracloud.org/coprs/nim/fontpackages-2/builds/

for an example on how to pass doc wildcards to generic automation
macros.

(currently polishing it and cross-pollinating with go macros)

Regards,

-- 
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

Re: Use immutable CRAN URLs

[Iñaki Ucar]

On Thu, 1 Nov 2018 at 05:05, Elliott Sales de Andrade
 wrote:
>
> Basically anything under %{rlibdir}%{packname} is needed and nothing appears 
> elsewhere. If we didn't need to mark doc and license files, we could have 
> just specified that top-level directory. The hard part about that is the 
> naming is pretty inconsistent. Because CRAN disallows providing the full 
> license text in LICENSE, upstreams that want to follow the terms of the 
> license will put it in a separate file and the name is never the same.

This is not correct. The naming is very consistent and it's clearly
specified in the "Writing R Extensions" manual (section 1.1 Package
structure). Most licenses (such as GPL) must not be bundled in the
sources. Some of them (such as MIT) require a file with the year and
the name of the copyright holders, and this file must be called
LICENSE or LICENCE.

If there are other copyright holders different from the authors, and
in general if the authoring information is too complex, files AUTHORS
and COPYRIGHTS may be present.

Anyway, the presence of these files must be specified in the
DESCRIPTION file (LICENSE/LICENCE -> License field; AUTHORS -> Author
field; COPYRIGHTS -> Copyright field), see, e.g., the XML and bookdown
packages.

-- 
Iñaki Ucar
___
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: Enabling powerline theme system wide by default

[Daniel J. R. May]

On Thu, 2018-11-01 at 08:26 -0400, Robert Marcano wrote:
> On 10/31/18 8:13 PM, Luya Tshimbalanga wrote:
> 
> I really prefer some kind of subpackage like powerline-system-config 
> that could add an something to /etc/profile.d that add a default 
> configuration for all non system users instead of telling people to 
> adapt their .bash_profile/.bashrc (or preferred shell) scripts

I agree. I prefer an "off by default, but easy to on" option. I did
write some rough and ready BASH script for my own machine configuration
needs ages ago, but I think it just automatically modified ~/.bashrc. I
could dig it out and stick it on GitLab if anyone is interested… 😉

Cheers, Dan



signature.asc
Description: This is a digitally signed message part
___
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: IBM buying RedHat

[Jonathan Wakely]

On 01/11/18 07:18 -0400, Nico Kadel-Garcia wrote:

On Tue, Oct 30, 2018 at 4:48 PM Matthew Miller  wrote:


On Sun, Oct 28, 2018 at 07:44:12PM -0400, Neal Gompa wrote:
> It'd be nice if someone from up top would deign to come and talk to us
> directly...

Communications are pretty carefully controlled for regulatory reasons, and
the fact is even those at the top don't know everything yet. And speculation
is basically right out. That said, I'm working on what I can do here. Are
there specific things you'd like to ask?


When did the engineering staff know?


At the same time as everybody else: when the press releases went
public on Sunday.

There's no way they could have given thousands of people advance
notice without leaks, which would have risked insider trading.
Regulations around this kind of thing are strict.

___
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: IBM buying RedHat

[Neal Gompa]

On Thu, Nov 1, 2018 at 8:14 AM Nico Kadel-Garcia  wrote:
>
> On Tue, Oct 30, 2018 at 4:48 PM Matthew Miller  
> wrote:
> >
> > On Sun, Oct 28, 2018 at 07:44:12PM -0400, Neal Gompa wrote:
> > > It'd be nice if someone from up top would deign to come and talk to us
> > > directly...
> >
> > Communications are pretty carefully controlled for regulatory reasons, and
> > the fact is even those at the top don't know everything yet. And speculation
> > is basically right out. That said, I'm working on what I can do here. Are
> > there specific things you'd like to ask?
>
> When did the engineering staff know?

I'm pretty sure it's obvious by this thread that everyone found out at
the same time...

> Will IBM push Red Hat towards, or
> away, from their current level of worldwide telecommuting? Whose
> management will be in charge on a day to day basis? What will be the
> relationship with Fedora? Will Red Hat engineers be as encouraged as
> they are now to publish software and fixes to the Fedora releases?
> Will the CentOS core development team stay employed by Red Hat?

These are questions I'm interested in answers on. However, I'm also
worried about how much the "cloud" was mentioned in the presser. It
makes me nervous about Red Hat's investment into other areas, which a
lot of the Linux ecosystem relies on, even outside of the Fedora
community. Desktop Linux, traditional server platforms, IoT, etc. look
like areas that might be disinvested in. :(

> What
> is the expected release date for RHEL 8, so I can stop building the
> *very* large dependency chains between current Fedora components I
> need to backport to RHEL 7 and CentOS 7?

Yeah, no. They're not going to answer this. I wouldn't even expect
them to. But a little sleuthing will give you some idea of when we'll
see the next RHEL release. :)

> Will IBM and Red Hat rein in
> the "let's replace another system function into systemd that has
> nothing to do with logging or daemon management" ?

Yeah, no. That's very pejorative. I wouldn't answer it even if I knew
the answer to it.

--
真実はいつも一つ！/ 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

Say thanks during Fedora Appreciation Week (Nov. 5-11)

[Justin W. Flory]

This year, the first-ever Fedora Appreciation Week will run from Monday,
November 5th to Sunday, November 11th. Fedora Appreciation Week is an
annual event organized by the Fedora Community Operations (CommOps)
team. It’s a week-long event to celebrate efforts of Fedora Project
contributors and to say “thank you” to each other.

This year, the Appreciation Week runs during the fifteenth anniversary
of the Fedora Project. The Fedora Project has changed in many ways since
2003, but not the importance of our contributor community. This is a
week to celebrate the friends, colleagues, and contributors who are part
of this fifteen-year open source saga. Learn more about the event here.

https://fedoramagazine.org/say-thanks-appreciation-week-2018/

-- 
Cheers,
Justin W. Flory
jflo...@gmail.com



signature.asc
Description: OpenPGP digital signature
___
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

Commit notifications for Fedora dist-git

[Florian Weimer]

On src.fedoraproject.org, I selected “Watch Issues, PRs, and Commits”
for various packages and assumed that I would receive notifications for
new commits.  But nothing arrives anymore, as far as I can tell.

Obviously, this is problematic if proven packages do uncoordinated
package changes.

What can we do here?  I can filter down scm-commits, but I don't know
how complete those notifications are.

Thanks,
Florian
___
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: Enabling powerline theme system wide by default

[Randy Barlow]

On Wed, 2018-10-31 at 17:13 -0700, Luya Tshimbalanga wrote:
> Since powerline does
> not
> impact the performance, it will be great to set for Fedora 30.

I experienced a performance problem with powerline on Fedora on a
Raspberry Pi I was setting up for a friend. It seemed to put
significant load on the CPU.


signature.asc
Description: This is a digitally signed message part
___
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: Enabling powerline theme system wide by default

[Randy Barlow]

On Thu, 2018-11-01 at 10:04 -0400, Randy Barlow wrote:
> I experienced a performance problem with powerline on Fedora on a
> Raspberry Pi I was setting up for a friend. It seemed to put
> significant load on the CPU.

My memory is a little hazy - I think it was specifically tmux-powerline 
and not the bash powerline. Not 100% sure and I don't have a pi to test
with myself.


signature.asc
Description: This is a digitally signed message part
___
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

CVE-2018-14665 : Xorg X Server Vulnerabilities

[Cătălin George Feștilă]

https://www.securepatterns.com/2018/10/cve-2018-14665-xorg-x-server.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: Enabling powerline theme system wide by default

[Stephen Gallagher]

On Thu, Nov 1, 2018 at 10:14 AM Randy Barlow
 wrote:
>
> On Thu, 2018-11-01 at 10:04 -0400, Randy Barlow wrote:
> > I experienced a performance problem with powerline on Fedora on a
> > Raspberry Pi I was setting up for a friend. It seemed to put
> > significant load on the CPU.
>
> My memory is a little hazy - I think it was specifically tmux-powerline
> and not the bash powerline. Not 100% sure and I don't have a pi to test
> with myself.

Well, it's worth noting that this *can* put a significant load on the
system when operating within a directory that has an enormous commit
history (such as the kernel). So if we were to go this route, I think
we'd want to first enhance powerline to avoid reading the entire git
history while displaying the status.
___
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: CVE-2018-14665 : Xorg X Server Vulnerabilities

[Cătălin George Feștilă]

Thank you!

On Thu, Nov 1, 2018 at 4:38 PM Reindl Harald  wrote:

>
>
> Am 01.11.18 um 15:33 schrieb Cătălin George Feștilă:
> > https://www.securepatterns.com/2018/10/cve-2018-14665-xorg-x-server.html
>
> https://fedoraproject.org/wiki/Features/RemoveSETUID
> Targeted release: Fedora 15
>
> ls -la /usr/bin/Xorg
> -rwxr-xr-x 1 root root 273 2018-04-23 20:16 /usr/bin/Xorg
>
___
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: Use immutable CRAN URLs

[Jason L Tibbitts III]

> "IU" == Iñaki Ucar  writes:

IU> - Version: As you already found out, there are many version formats
IU> allowed.

But it's easy to work from Version: in the normal case and simply allow
the CRAN version to be specified separately, as I showed in the R-uuid
sample.  If it's rather more common that updating the version in two
places is a burden, we can certainly look at other ways to do it.

IU> - Arch, Requires, BuildRequires, libdir/datadir: As Elliott pointed
IU> out already, archful packages can be detected just by looking into
IU> the DESCRIPTION file, by checking whether the NeedsCompilation flag
IU> exists.

As nim pointed out in a previous message, it's "not possible" to make
use of this information for many things as long as DESCRIPTION is within
the tarball, because unpacking does not happen until well after specfile
parsing (and thus macro expansion) has happened.  (Technically all
things are possible but there isn't too much you can do with a source
file before it's even been downloaded, and we certainly have to be able
to parse the spec before that point.)

There are of course some things you can do.  The %prep and %install
scriptlets, for example, are just shell code which can be inserted by
macros but which actually runs much later.  So you can use that
information to figure out how to build, and what files to install.  But
you can't look in there to add BuildArch: noarch or add build
dependencies because those have to be done much earlier.

So that's why I just provided separate macros for the archful and noarch
cases.

IU> - %prep, %build, %install, %check, %files: These can be automated
IU> too.

Well, look at the two examples I provided.  The %files list isn't
completely consistent (one package has COPYING and the other doesn't)
but the test macro file I provided conditionalizes this properly.

IU> I'm not familiar at all with RPM macros, but I can help with all
IU> these details.

So then perhaps have a look at those examples I provided and see how
they would actually work in real life on more than the two specs I
converted.  If I get time today I'll fill things in for the noarch
package case.

 - J<
___
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: CVE-2018-14665 : Xorg X Server Vulnerabilities

[Tom Hughes]

On 01/11/2018 14:33, Cătălin George Feștilă wrote:


https://www.securepatterns.com/2018/10/cve-2018-14665-xorg-x-server.html


Just sending a URL to the list is not very helpful - you need
to explain what you expect us to do with it, or what the question
is that would like answered.

That CVE is nearly a week old now so I'm sure the relevant people
are already aware of it, if only because the security team would
likely have opened a few dozen bugs about it by now if it was
relevant.

It's not relevant though, because it doesn't affect Fedora as
the X server is not setuid in Fedora and hasn't been for some
considerable time (since F22 at least).

Tom

--
Tom Hughes (t...@compton.nu)
http://compton.nu/
___
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: CVE-2018-14665 : Xorg X Server Vulnerabilities

[Chris Adams]

Once upon a time, Cătălin George Feștilă  said:
> Thank you!
> 
> On Thu, Nov 1, 2018 at 4:38 PM Reindl Harald  wrote:
> 
> >
> >
> > Am 01.11.18 um 15:33 schrieb Cătălin George Feștilă:
> > > https://www.securepatterns.com/2018/10/cve-2018-14665-xorg-x-server.html
> >
> > https://fedoraproject.org/wiki/Features/RemoveSETUID
> > Targeted release: Fedora 15
> >
> > ls -la /usr/bin/Xorg
> > -rwxr-xr-x 1 root root 273 2018-04-23 20:16 /usr/bin/Xorg

That means nothing... that's just a shell script that calls:

$ ls -l /usr/libexec/Xorg.wrap
-rwsr-xr-x. 1 root root 11376 Apr 12  2018 /usr/libexec/Xorg.wrap

which is where the problem lies.  I think SELinux should help (because
it should stop writes to lots of things), but I haven't seen a bug or
statement from Fedora about vulnerability.

-- 
Chris Adams 
___
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: IBM buying RedHat

[William Moreno]

>
>
> These are questions I'm interested in answers on. However, I'm also
> worried about how much the "cloud" was mentioned in the presser. It
> makes me nervous about Red Hat's investment into other areas, which a
> lot of the Linux ecosystem relies on, even outside of the Fedora
> community. Desktop Linux, traditional server platforms, IoT, etc. look
> like areas that might be disinvested in. :(
>
>
> Gnome, LibreOffice, PulseAudio, Pipeware  and a really long list
available here:

https://community.redhat.com/software/

I really like the RedHat way about open source (
https://www.redhat.com/es/open-source/red-hat-way) many of those projects
are lucrative, but many others are not so, Redhat have been profitable even
investing a lot in many open source projects, so **MAYBE** IBM will make
not many changes in the short or midle term, but if they want a higher
return over investment they can see a way to cut expenses by reducing
contributions to areas that they do not focus.

Fedora is the upstream of RHEL, I do not see IBM killing RHEL just because
is the heart of RedHat bussines model, a there are a lot of things IBM can
do on top of the RHEL base, and if you want to keep RHEL solid you need a
strong base in the Fedora Project, I am really curios about IBM position
about the Community around Fedora (**we** the people that do some stuff in
Fedora without any direct RH income), I do not see IBM killing the Fedora
Community just because they need to keep the development of the Linux
ecosystem to keep RHEL strong, maybe we can see a lot more bureaucracy, we
can maybe less budget for events, but I do thing that the Fedora Project
will continue and I hope it will kepp being a awesome community to be part
of it.

We have F29 out now and can be happy about it.
___
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: Use immutable CRAN URLs

[Iñaki Ucar]

On Thu, 1 Nov 2018 at 15:45, Jason L Tibbitts III  wrote:
>
> > "IU" == Iñaki Ucar  writes:
>
> IU> - Version: As you already found out, there are many version formats
> IU> allowed.
>
> But it's easy to work from Version: in the normal case and simply allow
> the CRAN version to be specified separately, as I showed in the R-uuid
> sample.  If it's rather more common that updating the version in two
> places is a burden, we can certainly look at other ways to do it.

Your example is fine. I was, again, just completing the picture to
show that your solution is enough to treat every case.

> IU> - Arch, Requires, BuildRequires, libdir/datadir: As Elliott pointed
> IU> out already, archful packages can be detected just by looking into
> IU> the DESCRIPTION file, by checking whether the NeedsCompilation flag
> IU> exists.
>
> As nim pointed out in a previous message, it's "not possible" to make
> use of this information for many things as long as DESCRIPTION is within
> the tarball, because unpacking does not happen until well after specfile
> parsing (and thus macro expansion) has happened.  (Technically all
> things are possible but there isn't too much you can do with a source
> file before it's even been downloaded, and we certainly have to be able
> to parse the spec before that point.)
>
> There are of course some things you can do.  The %prep and %install
> scriptlets, for example, are just shell code which can be inserted by
> macros but which actually runs much later.  So you can use that
> information to figure out how to build, and what files to install.  But
> you can't look in there to add BuildArch: noarch or add build
> dependencies because those have to be done much earlier.
>
> So that's why I just provided separate macros for the archful and noarch
> cases.

I see. Anyway, I suppose that it's healthy to preserve some manual
intervention in these sections.

> IU> - %prep, %build, %install, %check, %files: These can be automated
> IU> too.
>
> Well, look at the two examples I provided.  The %files list isn't
> completely consistent (one package has COPYING and the other doesn't)
> but the test macro file I provided conditionalizes this properly.

From "Writing R Extensions":

"Whereas you should feel free to include a license file in your source
distribution, please do not arrange to install yet another copy of the
GNU COPYING or COPYING.LIB files but refer to the copies on
https://www.R-project.org/Licenses/ and included in the R distribution
(in directory share/licenses)".

Therefore, that file shouldn't be there and should be removed
(actually, it's funny because uuid's maintainer is a member of R-Core,
and we usually get our submissions to CRAN rejected due to smaller
details ¯\_(ツ)_/¯).

> IU> I'm not familiar at all with RPM macros, but I can help with all
> IU> these details.
>
> So then perhaps have a look at those examples I provided and see how
> they would actually work in real life on more than the two specs I
> converted.  If I get time today I'll fill things in for the noarch
> package case.

You can count on that. I'll try to identify corner cases to see how
your macros behave in such packages and report back as time permits.

>
>  - J<

-- 
Iñaki Ucar
___
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: CVE-2018-14665 : Xorg X Server Vulnerabilities

[Tomasz Torcz]

On Thu, Nov 01, 2018 at 04:33:47PM +0200, Cătălin George Feștilă wrote:
> https://www.securepatterns.com/2018/10/cve-2018-14665-xorg-x-server.html

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

-- 
Tomasz Torcz   "Never underestimate the bandwidth of a station
xmpp: zdzich...@chrome.plwagon filled with backup tapes." -- Jim Gray
___
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: IBM buying RedHat

[Peter Robinson]

On Thu, Nov 1, 2018 at 2:26 PM Neal Gompa  wrote:
>
> On Thu, Nov 1, 2018 at 8:14 AM Nico Kadel-Garcia  wrote:
> >
> > On Tue, Oct 30, 2018 at 4:48 PM Matthew Miller  
> > wrote:
> > >
> > > On Sun, Oct 28, 2018 at 07:44:12PM -0400, Neal Gompa wrote:
> > > > It'd be nice if someone from up top would deign to come and talk to us
> > > > directly...
> > >
> > > Communications are pretty carefully controlled for regulatory reasons, and
> > > the fact is even those at the top don't know everything yet. And 
> > > speculation
> > > is basically right out. That said, I'm working on what I can do here. Are
> > > there specific things you'd like to ask?
> >
> > When did the engineering staff know?
>
> I'm pretty sure it's obvious by this thread that everyone found out at
> the same time...
>
> > Will IBM push Red Hat towards, or
> > away, from their current level of worldwide telecommuting? Whose
> > management will be in charge on a day to day basis? What will be the
> > relationship with Fedora? Will Red Hat engineers be as encouraged as
> > they are now to publish software and fixes to the Fedora releases?
> > Will the CentOS core development team stay employed by Red Hat?
>
> These are questions I'm interested in answers on. However, I'm also
> worried about how much the "cloud" was mentioned in the presser. It
> makes me nervous about Red Hat's investment into other areas, which a
> lot of the Linux ecosystem relies on, even outside of the Fedora
> community. Desktop Linux, traditional server platforms, IoT, etc. look
> like areas that might be disinvested in. :(

And none of those questions are anything to do with the Fedora project
what so ever, they are between Red Hat employees, Red Hat and IBM.
Whether a Red Hat employee works on Fedora from their house or an
office desk is irrelevant! While I know people are fascinated by
peaking over people's back fences or taking a sticky beak at someone
else's private life basically none of any of the above has any outcome
to do with Fedora, those questions that are have already been answered
on this thread as best as they currently can be.

> > What
> > is the expected release date for RHEL 8, so I can stop building the
> > *very* large dependency chains between current Fedora components I
> > need to backport to RHEL 7 and CentOS 7?
>
> Yeah, no. They're not going to answer this. I wouldn't even expect
> them to. But a little sleuthing will give you some idea of when we'll
> see the next RHEL release. :)

Completely irrelevant WRT anything to do with the IBM acquisition.

> > Will IBM and Red Hat rein in
> > the "let's replace another system function into systemd that has
> > nothing to do with logging or daemon management" ?

Completely irrelevant. Please keep the thread on topic. Nice try
trying to fuel sentiment but unrelated.
___
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

Nobody care about dmz-cursor-themes package

[Ivan Romanov]

Hello. 

Seems no care about dmz-cursor-themes package. Many time ago was opened
an issue https://bugzilla.redhat.com/show_bug.cgi?id=1397803. But no
any progress. There is an update. Need only to update package. How it
can be done? I have own version of this package which I use for myself
but I want to update package in Fedora.
___
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: Spam/scam links in bugzilla

[Cole Robinson]

On 11/01/2018 07:23 AM, Alexander Ploumistos wrote:
> Hello,
> 
> A few minutes ago I was notified about a post in a closed bug. It
> turns out that the account that made the post has been sporadically
> spamming various bugs:
> https://bugzilla.redhat.com/page.cgi?id=user_activity.html&action=run&who=dragoelanie%40gmail.com&from=2018-01-01&to=2018-11-01&sort=when
> The websites that are being linked to from these posts seem to be of
> the support scam garden variety.
> I did not know where to report this, hence this message.
> Can someone nuke the posts or at least the hyperlinks?
> Btw, bugzilla reports that there are multiple accounts with the same
> name, so that might be worth looking into.
> 

Apparently also bodhi too? Maybe unrelated, but this comment came in
earlier today:

https://bodhi.fedoraproject.org/updates/python-bugzilla-2.2.0-1.el7#comment-855877

- Cole
___
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: CVE-2018-14665 : Xorg X Server Vulnerabilities

[Cătălin George Feștilă]

Good to know.
I don't know all about of these problems (setuid  and protect with SELinux
- can de an good idea ).
I used F28, I think also is not fixed with F29.
$ ls -l /usr/libexec/Xorg.wrap
-rwsr-xr-x. 1 root root 11376 Apr 23  2018 /usr/libexec/Xorg.wrap


On Thu, Nov 1, 2018 at 5:44 PM Chris Adams  wrote:

> Once upon a time, Cătălin George Feștilă  said:
> > Thank you!
> >
> > On Thu, Nov 1, 2018 at 4:38 PM Reindl Harald 
> wrote:
> >
> > >
> > >
> > > Am 01.11.18 um 15:33 schrieb Cătălin George Feștilă:
> > > >
> https://www.securepatterns.com/2018/10/cve-2018-14665-xorg-x-server.html
> > >
> > > https://fedoraproject.org/wiki/Features/RemoveSETUID
> > > Targeted release: Fedora 15
> > >
> > > ls -la /usr/bin/Xorg
> > > -rwxr-xr-x 1 root root 273 2018-04-23 20:16 /usr/bin/Xorg
>
> That means nothing... that's just a shell script that calls:
>
> $ ls -l /usr/libexec/Xorg.wrap
> -rwsr-xr-x. 1 root root 11376 Apr 12  2018 /usr/libexec/Xorg.wrap
>
> which is where the problem lies.  I think SELinux should help (because
> it should stop writes to lots of things), but I haven't seen a bug or
> statement from Fedora about vulnerability.
>
> --
> Chris Adams 
> ___
> 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: CVE-2018-14665 : Xorg X Server Vulnerabilities

[Jiri Eischmann]

Chris Adams píše v Čt 01. 11. 2018 v 09:53 -0500:
> Once upon a time, Cătălin George Feștilă 
> said:
> > Thank you!
> > 
> > On Thu, Nov 1, 2018 at 4:38 PM Reindl Harald <
> > h.rei...@thelounge.net> wrote:
> > 
> > > 
> > > Am 01.11.18 um 15:33 schrieb Cătălin George Feștilă:
> > > > https://www.securepatterns.com/2018/10/cve-2018-14665-xorg-x-server.html
> > > 
> > > https://fedoraproject.org/wiki/Features/RemoveSETUID
> > > Targeted release: Fedora 15
> > > 
> > > ls -la /usr/bin/Xorg
> > > -rwxr-xr-x 1 root root 273 2018-04-23 20:16 /usr/bin/Xorg
> 
> That means nothing... that's just a shell script that calls:
> 
> $ ls -l /usr/libexec/Xorg.wrap
> -rwsr-xr-x. 1 root root 11376 Apr 12  2018 /usr/libexec/Xorg.wrap
> 
> which is where the problem lies.  I think SELinux should help
> (because
> it should stop writes to lots of things), but I haven't seen a bug or
> statement from Fedora about vulnerability.

I wonder if Fedora has even been affected. I was not able to reproduce
the exploit on Fedora 29 Workstation (with Xorg older than the one
fixing the issue).

Jiri

>  
> Chris Adams 
> ___
> 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: Nonresponsive maintainer: Björn Esser (besser82)

[Sérgio Basto]

On Thu, 2018-11-01 at 09:59 +0100, Jan Pokorný wrote:
> On 01/11/18 08:30 +0100, Miro Hrončok wrote:
> > On 01. 11. 18 7:48, Jan Pokorný wrote:
> > > I'd be interested in (co)maintenance of one of his packages,
> > > tried contacting him over email (less than a day ago), then
> > > realized I could check this ML.
> > 
> > Claim the package in https://pagure.io/releng/issues
> > 
> > Link https://pagure.io/fesco/issue/1971
> 
> Thanks for the pointers, applied: https://pagure.io/releng/issue/7901


besser82 commented 2 months ago

Please do not orphan my packages. I've been really busy during the last
two years, thus a lot of stuff went by me. I'm still alive and will be
more responsive after the end of September.


-- 
Sérgio M. B.
___
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: IBM buying RedHat

[Neal Gompa]

On Thu, Nov 1, 2018 at 12:12 PM Peter Robinson  wrote:
>
> On Thu, Nov 1, 2018 at 2:26 PM Neal Gompa  wrote:
> >
> > On Thu, Nov 1, 2018 at 8:14 AM Nico Kadel-Garcia  wrote:
> > >
> > > On Tue, Oct 30, 2018 at 4:48 PM Matthew Miller  
> > > wrote:
> > > >
> > > > On Sun, Oct 28, 2018 at 07:44:12PM -0400, Neal Gompa wrote:
> > > > > It'd be nice if someone from up top would deign to come and talk to us
> > > > > directly...
> > > >
> > > > Communications are pretty carefully controlled for regulatory reasons, 
> > > > and
> > > > the fact is even those at the top don't know everything yet. And 
> > > > speculation
> > > > is basically right out. That said, I'm working on what I can do here. 
> > > > Are
> > > > there specific things you'd like to ask?
> > >
> > > When did the engineering staff know?
> >
> > I'm pretty sure it's obvious by this thread that everyone found out at
> > the same time...
> >
> > > Will IBM push Red Hat towards, or
> > > away, from their current level of worldwide telecommuting? Whose
> > > management will be in charge on a day to day basis? What will be the
> > > relationship with Fedora? Will Red Hat engineers be as encouraged as
> > > they are now to publish software and fixes to the Fedora releases?
> > > Will the CentOS core development team stay employed by Red Hat?
> >
> > These are questions I'm interested in answers on. However, I'm also
> > worried about how much the "cloud" was mentioned in the presser. It
> > makes me nervous about Red Hat's investment into other areas, which a
> > lot of the Linux ecosystem relies on, even outside of the Fedora
> > community. Desktop Linux, traditional server platforms, IoT, etc. look
> > like areas that might be disinvested in. :(
>
> And none of those questions are anything to do with the Fedora project
> what so ever, they are between Red Hat employees, Red Hat and IBM.
> Whether a Red Hat employee works on Fedora from their house or an
> office desk is irrelevant! While I know people are fascinated by
> peaking over people's back fences or taking a sticky beak at someone
> else's private life basically none of any of the above has any outcome
> to do with Fedora, those questions that are have already been answered
> on this thread as best as they currently can be.
>

I'm surprised that you take that opinion, because the fact that people
are working on these things as part of their day job makes it so that
things often move forward. In many cases, people can't afford to work
on these kinds of things from the side without really sacrificing
something.

Heck, I know that I sacrifice quite a lot of "free" time to working on
stuff like this because I can't do it as part of my job. And because
of that, my commitments are much woozier and limited, because I can't
spend dedicated cycles on everything I work on.

The fact I get anything done is more the exception than the rule. :)


-- 
真実はいつも一つ！/ 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

Re: IBM buying RedHat

[mcatanzaro]

On Thu, Nov 1, 2018 at 8:32 AM, Neal Gompa  wrote:

These are questions I'm interested in answers on. However, I'm also
worried about how much the "cloud" was mentioned in the presser. It
makes me nervous about Red Hat's investment into other areas, which a
lot of the Linux ecosystem relies on, even outside of the Fedora
community. Desktop Linux, traditional server platforms, IoT, etc. look
like areas that might be disinvested in. :(


The press release's focus on cloud cloud cloud sure makes it sound like 
desktop team will be first in line for cuts. I think it's quite natural 
for Fedora Workstation users to be worried right now, given the lack of 
public statement regarding the future of Red Hat's desktop work. It 
goes without saying that Fedora will not have a very bright future if 
Red Hat's investment in desktop and Workstation were to cease or be 
significantly reduced.


Plus a lot of my friends work on desktop and they will be :( :( :( if 
their jobs go away.


Michael
___
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: CVE-2018-14665 : Xorg X Server Vulnerabilities

[Adam Jackson]

On Thu, 2018-11-01 at 16:33 +0200, Cătălin George Feștilă wrote:
> https://www.securepatterns.com/2018/10/cve-2018-14665-xorg-x-server.html

Forgive me, it's been a stressful week.

https://bodhi.fedoraproject.org/updates/FEDORA-2018-839720583a
https://bodhi.fedoraproject.org/updates/FEDORA-2018-4ab08fedd6

- ajax
___
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: Nobody care about dmz-cursor-themes package

[Robert-André Mauchin]

On jeudi 1 novembre 2018 16:47:03 CET Ivan Romanov wrote:
> Hello. 
> 
> Seems no care about dmz-cursor-themes package. Many time ago was opened
> an issue https://bugzilla.redhat.com/show_bug.cgi?id=1397803. But no
> any progress. There is an update. Need only to update package. How it
> can be done? I have own version of this package which I use for myself
> but I want to update package in Fedora.

Yeah the maintainer seems to be missing:

python2 fedora_active_user.py --user company
Last login in FAS:
   company 2016-11-08
Last action on koji:
   Fri, 16 Mar 2018 package list entry revoked: gstreamer-plugins-bad-free in 
trashcan by oscar
Last package update on bodhi:
   2015-04-28 01:43:12 on package cairo-1.14.2-1.fc21

You should find a packager who cares, like Link Dupont, and ask him to start 
the process for Non-responsive Maintainer 
https://docs.fedoraproject.org/en-US/fesco/Policy_for_nonresponsive_package_maintainers/
 His packages would be 
orphaned and Link could adopt dmz-cursor-themes.

Best regards,

Robert-André

___
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: Nobody care about dmz-cursor-themes package

[Matthew Miller]

On Thu, Nov 01, 2018 at 08:47:03PM +0500, Ivan Romanov wrote:
> Seems no care about dmz-cursor-themes package. Many time ago was opened
> an issue https://bugzilla.redhat.com/show_bug.cgi?id=1397803. But no
> any progress. There is an update. Need only to update package. How it
> can be done? I have own version of this package which I use for myself
> but I want to update package in Fedora.

Ideally, you can get ahold of the maintainer and be added as a
co-maintainer.

If that doesn't work, the process is here: 
https://fedoraproject.org/wiki/Policy_for_nonresponsive_package_maintainers



-- 
Matthew Miller

Fedora Project Leader
___
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: Spam/scam links in bugzilla

[Alasdair G Kergon]

On Thu, Nov 01, 2018 at 12:35:17PM +, Caolán McNamara wrote:
> hfjkd1...@gmail.com is another one in RH bugzilla, the same scammers
> are doing the same to the libreoffice bugzilla too

I've cleaned those up and closed the accounts concerned (together with
some other similar ones I found).  They are defeating our existing anti-spam
protection!

If anyone spots any more, please open a ticket by emailing bugzilla-requests
@redhat.com and one of us will clean it up.

Alasdair
___
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: CVE-2018-14665 : Xorg X Server Vulnerabilities

[Chris Adams]

Once upon a time, Jiri Eischmann  said:
> I wonder if Fedora has even been affected. I was not able to reproduce
> the exploit on Fedora 29 Workstation (with Xorg older than the one
> fixing the issue).

IIRC F29 Workstation uses Wayland, not X, right?
-- 
Chris Adams 
___
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: Spam/scam links in bugzilla

[Alexander Ploumistos]

On Thu, Nov 1, 2018 at 7:05 PM Alasdair G Kergon  wrote:
> If anyone spots any more, please open a ticket by emailing bugzilla-requests
> @redhat.com and one of us will clean it up.

Thanks Alasdair, that's good to know.
___
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: Use immutable CRAN URLs

[Jason L Tibbitts III]

> "IU" == Iñaki Ucar  writes:

IU> I see. Anyway, I suppose that it's healthy to preserve some manual
IU> intervention in these sections.

Well, it would be super great if we didn't have to do that and one day
RPM might give us some reasonable way to generate more of the specfile
based on the contents of the source files.  See 
https://github.com/rpm-software-management/rpm/issues/104
But even if we get that, you won't be able to use it on anything but
rawhide for some time.

IU> You can count on that. I'll try to identify corner cases to see how
IU> your macros behave in such packages and report back as time permits.

I'm certainly happy to develop them in tandem with your investigations.
I have no expectation that what I banged out yesterday is remotely
complete, but it at least shows that for at least a couple of packages
you can hide rather a lot of the details behind macros.

I think the next step is for me to stuff those macros in a temporary
pagure repo.  We can track what's missing with tickets and then
eventually get the macros packaged up so that they can be used in the
buildsystem.

 - J<
___
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: Enabling powerline theme system wide by default

[Jan Pokorný]

On 01/11/18 09:53 +0100, Nicolas Mailhot wrote:
> Le mercredi 31 octobre 2018 à 17:13 -0700, Luya Tshimbalanga a écrit :
>> It will be nice to enable powerline theme by default system and user
>> wide. Simple reason is refresh the look of terminal while also
>> providing
>> useful information especially for git branch. Since powerline does not
>> impact the performance, it will be great to set for Fedora 30
> 
> If someone wants to do this the font powerline uses should be fixed to
> used correct unicode point values (and PUA when it include things not
> standardised by unicode).
> 
> Otherwise powerline display is just broken on many terminals

+1 if this would naturally solve "unable to calculate font width
for 'PowerlineSymbols'" problem with rxvt-unicode.

-- 
Nazdar,
Jan (Poki)


pgpGUBFSxIf0T.pgp
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

Re: CVE-2018-14665 : Xorg X Server Vulnerabilities

[Adam Jackson]

On Thu, 2018-11-01 at 13:08 -0500, Chris Adams wrote:
> Once upon a time, Jiri Eischmann  said:
> > I wonder if Fedora has even been affected. I was not able to reproduce
> > the exploit on Fedora 29 Workstation (with Xorg older than the one
> > fixing the issue).
> 
> IIRC F29 Workstation uses Wayland, not X, right?

The thing driving the display [1] is a wayland server named gnome-
shell. Due to accident of implementation there is also an X server
named Xwayland running as well. This CVE affects the X server named
Xorg.

[1] - Assuming you select "GNOME" from the little gear menu in gdm, as
opposed to "GNOME on Xorg".

- ajax
___
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: CVE-2018-14665 : Xorg X Server Vulnerabilities

[Marek Marczykowski-Górecki]

On Thu, Nov 01, 2018 at 04:33:21PM -0400, Adam Jackson wrote:
> On Thu, 2018-11-01 at 13:08 -0500, Chris Adams wrote:
> > Once upon a time, Jiri Eischmann  said:
> > > I wonder if Fedora has even been affected. I was not able to reproduce
> > > the exploit on Fedora 29 Workstation (with Xorg older than the one
> > > fixing the issue).
> > 
> > IIRC F29 Workstation uses Wayland, not X, right?
> 
> The thing driving the display [1] is a wayland server named gnome-
> shell. Due to accident of implementation there is also an X server
> named Xwayland running as well. This CVE affects the X server named
> Xorg.

If I understand this CVE correctly, it doesn't matter what X server is
running (if any at all). Do matter what setuid-root Xorg binary is
installed (or not).

-- 
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?


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

Fedora updates-20181101.0 compose check report

[Fedora compose checker]

No missing expected images.

Failed openQA tests: 2/2 (x86_64)

Old failures (same test failed in updates-20181031.0):

ID: 304523  Test: x86_64 AtomicHost-dvd_ostree-iso install_default
URL: https://openqa.fedoraproject.org/tests/304523
ID: 304524  Test: x86_64 AtomicHost-dvd_ostree-iso install_default@uefi
URL: https://openqa.fedoraproject.org/tests/304524
-- 
Mail generated by check-compose:
https://pagure.io/fedora-qa/check-compose
___
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

Fedora testing-20181101.0 compose check report

[Fedora compose checker]

No missing expected images.

Failed openQA tests: 2/2 (x86_64)

ID: 304548  Test: x86_64 AtomicHost-dvd_ostree-iso install_default
URL: https://openqa.fedoraproject.org/tests/304548
ID: 304549  Test: x86_64 AtomicHost-dvd_ostree-iso install_default@uefi
URL: https://openqa.fedoraproject.org/tests/304549
-- 
Mail generated by check-compose:
https://pagure.io/fedora-qa/check-compose
___
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: CVE-2018-14665 : Xorg X Server Vulnerabilities

[Lukas Vrabec]

On 11/1/18 5:08 PM, Cătălin George Feștilă wrote:
> Good to know. 
> I don't know all about of these problems (setuid  and protect with
> SELinux - can de an good idea ).
> I used F28, I think also is not fixed with F29. 
> $ ls -l /usr/libexec/Xorg.wrap
> -rwsr-xr-x. 1 root root 11376 Apr 23  2018 /usr/libexec/Xorg.wrap  
> 

SELinux can block the exploit if the "unconfined" module is disabled.
I'm writing blog about it. When it will be ready, I add link also to
this thread.

Thanks,
Lukas.

> 
> On Thu, Nov 1, 2018 at 5:44 PM Chris Adams  > wrote:
> 
> Once upon a time, Cătălin George Feștilă  > said:
> > Thank you!
> >
> > On Thu, Nov 1, 2018 at 4:38 PM Reindl Harald
> mailto:h.rei...@thelounge.net>> wrote:
> >
> > >
> > >
> > > Am 01.11.18 um 15:33 schrieb Cătălin George Feștilă:
> > > >
> https://www.securepatterns.com/2018/10/cve-2018-14665-xorg-x-server.html
> > >
> > > https://fedoraproject.org/wiki/Features/RemoveSETUID
> > > Targeted release: Fedora 15
> > >
> > > ls -la /usr/bin/Xorg
> > > -rwxr-xr-x 1 root root 273 2018-04-23 20:16 /usr/bin/Xorg
> 
> That means nothing... that's just a shell script that calls:
> 
> $ ls -l /usr/libexec/Xorg.wrap
> -rwsr-xr-x. 1 root root 11376 Apr 12  2018 /usr/libexec/Xorg.wrap
> 
> which is where the problem lies.  I think SELinux should help (because
> it should stop writes to lots of things), but I haven't seen a bug or
> statement from Fedora about vulnerability.
> 
> -- 
> Chris Adams mailto:li...@cmadams.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
> 
> 
> ___
> 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
> 


-- 
Lukas Vrabec
Software Engineer, Security Technologies
Red Hat, Inc.
___
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: Use immutable CRAN URLs

[Jason L Tibbitts III]

Since I actually had an existing pagure repo for random RPM macro
experiments, I just dropped the R macro stuff there.

https://pagure.io/misc-rpm-macros
https://pagure.io/misc-rpm-macros/blob/master/f/macros.R-extra

I still have some ideas to implement but feel free to test what's there.
To use this, you just need to check out the repo and then add a symlink
to macros.R-extra in /usr/lib/rpm/macros.d.

 - J<
___
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: Intent to relicense fontpackages

[Kevin Kofler]

Nicolas Mailhot wrote:
> Just FYI, I intend to relicense fontpackages from LGPL3+ to GPL3+, to
> make sharing parts with go-macros easier.
> 
> Since fontpackages only contains templates and scripts and is not linked
> anywhere there is no practical difference.
> 
> If you see a problem with this change, or have contributed to
> fontpackages to the past and do not like this change, please say so now.

I don't think you even have to ask the people who contributed in this case, 
because you are converting from LGPLv3+ to GPLv3+, which the licenses are 
designed to allow.

Kevin Kofler
___
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

State building since Mon, 17 Sep 2018 16:12:27 UTC !???

[Sérgio Basto]

this koji build [1] is in state bunding since , 17 Sep 2018 16:12:27
UTC !???

[1]
https://koji.fedoraproject.org/koji/buildinfo?buildID=1145294

-- 
Sérgio M. B.
___
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

Need assistance to build LuxCoreRender

[Luya Tshimbalanga]

LuxRender is dead, long live LuxCoreRender. 

I attempt to build LuxCoreRender in rpm format. Unfortunately, issue
like unable to detect boost despite its presence forcing to use static
version. I include the spec file for preview and would some pointers.

Thanks in advance.


Luya

# [Fedora] Turn off the brp-python-bytecompile script
%global __os_install_post %(echo '%{__os_install_post}' | sed -e 's!/usr/lib[^[:space:]]*/brp-python-bytecompile[[:space:]].*$!!g')

%global		with_prerelease 1
%global		prerelease	beta1

Name:   LuxCoreRender
Version:2.1
%if %{with_prerelease}
Release:0.1.%{prerelease}%{?dist}
%else
Release:1%{?dist}
%endif

Summary:Lux Renderer, an unbiased rendering system

License:GPLv3+ and Apache 2.0s
URL:http://www.luxcorerender.org
%if %{with_prerelease}
Source0:https://github.com/%{name}/LuxCore/archive/luxcorerender_v%{version}%{prerelease}.tar.gz
Source1:https://github.com/%{name}/BlendLuxCore/archive/blendluxcore_v%{version}%{prerelease}.tar.gz
%else
Source0:https://github.com/%{name}/LuxCore/archive/luxcorerender_v%{version}.tar.gz
Source1:https://github.com/%{name}/BlendLuxCore/archive/blendluxcore_v%{version}.tar.gz
%endif
Source2:blendluxcore-default.cfg
Source4:	luxcorerender.appdata.xml
Source5:	luxcorerender-blender.metainfo.xml

#LuxCoreRender use intensively SSE3
#ExclusiveArch:	%%{ix86} x86_64 ia64
ExclusiveArch:	x86_64

BuildRequires:  bison
BuildRequires:	blender-rpm-macros
BuildRequires:	blosc-devel
BuildRequires:  boost-static
BuildRequires:	boost-python3-devel
BuildRequires:  cmake
BuildRequires:  desktop-file-utils
BuildRequires:  dos2unix
BuildRequires:  doxygen
BuildRequires:  embree-devel
BuildRequires:  fftw-devel
BuildRequires:  flex
BuildRequires:  fltk-devel
BuildRequires:  freeglut-devel
BuildRequires:  freeimage-devel
BuildRequires:	gcc-c++
BuildRequires:  glfw-devel
BuildRequires:  gtk3-devel
BuildRequires:  ilmbase-devel
BuildRequires:  libappstream-glib
BuildRequires:  libcdio-devel
BuildRequires:  libpng-devel
BuildRequires:  libjpeg-turbo-devel
BuildRequires:  libtiff-devel
#BuildRequires:  libXdamage-devel
#BuildRequires:  libXmu-devel
BuildRequires:  ocl-icd-devel
BuildRequires:  opencl-headers
BuildRequires:  OpenEXR-devel
BuildRequires:	OpenImageIO-devel
BuildRequires:  python3-devel
BuildRequires:	tbb-devel
BuildRequires:  wxGTK-devel
Requires:	boost
Requires:  	%{name}-core = %{version}-%{release}
Obsoletes:	LuxRender < 2.0

%description
LuxCoreRender is a rendering system for physically correct image synthesis.

%package lib
Summary:Libraries for %{name}

%description lib
The %{name}-lib package contains shared library for %{name}.

%packagecore
Summary:Core binaries for %{name}
Requires:   %{name}-lib%{?_isa} = %{version}-%{release}
Obsoletes:	LuxRender-core < 2.0

%descriptioncore
The %{name}-core package contains core binaries for using %{name}.

%packageblender
Summary:Blender export plugin to %{name}
Requires:   %{name}%{?_isa} = %{version}-%{release}
Requires:	blender(ABI)%{?blender_api: = %{blender_api}}
BuildArch:	noarch
Obsoletes:	LuxRender-blender < 2.0

%descriptionblender
The %{name}-blender package contains the plugin for Blender
to export into %{name}

%packagedevel
Summary:Development files for %{name}
Requires:   %{name}-lib%{?_isa} = %{version}-%{release}
Provides:   %{name}-devel-docs = %{version}-%{release}
Obsoletes:  %{name}-devel-docs < 0.7

%descriptiondevel
The %{name}-devel package contains libraries and header files for
developing applications that use %{name}.



%prep
%if %{with_prerelease}
%autosetup -n LuxCore-luxcorerender_v%{version}%{prerelease}
%else
%autosetup -n LuxCore-luxcorerender_v%{version}
%endif

#Building lux
%cmake \
	-DCMAKE_VERBOSE_MAKEFILE:BOOL=TRUE \
	-DCMAKE_CXX_FLAGS="$CXXFLAGS -DLUXRAYS_DISABLE_OPENCL=0"
%make_build 


%install
mkdir -p %{buildroot}%{bindir}/luxcorerender
install -Dpm 0755 LuxCore-%{name} %{buildroot}%{bindir}/luxcorerender

# Import add-ons and preset
mkdir -p %{buildroot}%{blender_addons}
mkdir -p %{buildroot}%{blender_preset}
cp -pr luxcorerender-luxblend-%{hash1}/src/luxcorerender \
  %{buildroot}%{blender_addons}/
cp -pr luxcorerender-luxblend-%{hash1}/src/presets/luxcorerender \
  %{buildroot}%{blender_preset}/

# Install default configuration
mkdir -p %{buildroot}%{blender_libdir}/scripts/bpydata/config
install -pm 0644 %{SOURCE3} \
  %{buildroot}%{blender_libdir}/scripts/bpydata/config/blendluxcore-default.cfg


# AppData
# BugReportURL: http://www.luxcorerender.net/mantis/view.php?id=1540
install -p -m 644 -D %{SOURCE4} %{buildroot}%{_datadir}/metainfo/luxcorerender.appdata.xml
install -p -m 644 -D %{SOURCE5} %{buildroot}%{_datadir}/metainfo/luxcorerender-blender.metainfo.xml

%check
appstream-util validate-relax --nonet %{buildroot}/%{_datadir}/metainfo/luxcorerender.appdata.xml
app

Re: CVE-2018-14665 : Xorg X Server Vulnerabilities

[Raphael Groner]

> On 11/1/18 5:08 PM, Cătălin George Feștilă wrote:
> 
> SELinux can block the exploit if the "unconfined" module is disabled.

Same thoughts here. No main process (by user) should be allowed to overwrite 
system configuration except the dedicated tools or an editor.

> I'm writing blog about it. When it will be ready, I add link also to
> this thread.

Thanks. Please let us know about your work.

Regards, Raphael
___
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: CVE-2018-14665 : Xorg X Server Vulnerabilities

[Raphael Groner]

> On 11/1/18 5:08 PM, Cătălin George Feștilă wrote:
> 
> SELinux can block the exploit if the "unconfined" module is disabled.

Same thoughts here. No main process (by user) should be allowed to overwrite 
system configuration except the dedicated tools or an editor.

> I'm writing blog about it. When it will be ready, I add link also to
> this thread.

Thanks. Please let us know about your work.

Regards, Raphael
___
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: CVE-2018-14665 : Xorg X Server Vulnerabilities

[Raphael Groner]

> On Thu, Nov 01, 2018 at 04:33:21PM -0400, Adam Jackson wrote:
> 
> If I understand this CVE correctly, it doesn't matter what X server is
> running (if any at all). Do matter what setuid-root Xorg binary is
> installed (or not).

+1
SELinux should block such kind of attacks.
___
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: Nobody care about dmz-cursor-themes package

[Raphael Groner]

Hi Ivan,
do you still care about psi-plus? I felt so free to update this package.
Maybe you can help with better support for OMEMO. Upstream told there's no 
other alternative than libsignal but it's not packaged and I don't have time 
for that. Sorry for my offtopic question to this thread.
Regards, Raphael
___
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: Nonresponsive maintainer: Björn Esser (besser82)

[Raphael Groner]

Björn is reachable via Facebook. At least, I've chatted with him some days ago.
___
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: Enabling powerline theme system wide by default

[Porfirio Andrés Páiz Carrasco]

El mié., 31 de oct. de 2018 a la(s) 19:06, Luya Tshimbalanga
(l...@fedoraproject.org) escribió:
>
> It will be nice to enable powerline theme by default system and user
> wide. Simple reason is refresh the look of terminal while also providing
> useful information especially for git branch. Since powerline does not
> impact the performance, it will be great to set for Fedora 30.

Is there going to be any way to disable this?

I'm a powerline user on Terminal, Tmux and vim, but I don't enable
this in all my boxes.

Please note that not all users use powerline and will not want to have
it enabled or pre-installed by default.

And those who do use it do not have problems installing it, it's a
matter of personal taste.

Polite as usual,
Porfirio.
___
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