Re: Disable PulseAudio flat volumes to prevent it from pushing volume level to max

[Samuel Sieb]

On 09/23/2015 12:25 PM, kendell clark wrote:

hi
I use thunderbird. I generally press control+shift+r to reply to all,
including the list. There is a reply to list option, but all it seems to
do is forward, so I'm not sure how. I'll investigate today since I've
got some time on my hands.


I use Thunderbird and a simple reply replies only to the list.  The 
reply-to field is set to go to the list, so unless you've changed some 
setting related to that, there shouldn't be a problem.

--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: Announcing the release of Fedora 23 Beta!

[Samuel Sieb]

On 09/23/2015 10:19 AM, Richard W.M. Jones wrote:

and it works fine.  You may hit a problem that the reboot command
doesn't work immediately after the update (sorry, don't have the BZ or
error message right now), but you can just do:

   sync
   reboot -f

For anyone else that runs into this, just do "systemctl daemon-reexec", 
then the reboot should work normally.

--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: Announcing the release of Fedora 23 Beta!

[Adam Williamson]

On Wed, 2015-09-23 at 22:55 -0400, Eric Griffith wrote:
> On Sep 23, 2015 10:37 PM, "Adam Williamson"  rg>
> wrote:
> > 
> > On Wed, 2015-09-23 at 15:42 -0400, Eric Griffith wrote:
> > > Also is "--distro-sync --best" advised or not? The wiki only
> > > listed
> > > the
> > > first part of that command, not those two additional flags.
> > 
> > Well, last time I touched it, it recommended *trying* --best. You
> > may
> > have been looking at the 'upgrading with yum' page, which has
> > different
> > instructions.
> > 
> 
> I was looking at the dnf system upgrade feature page, which still
> recommends masking packagekit-offline-updates

Yeah, change pages don't always get updated terribly quickly. Please
consider https://fedoraproject.org/wiki/DNF_system_upgrade the
'official' page (as official as the wiki gets) and yell if anything on
it is wrong.

> Hmmm not what I thought it'd do. Im still trying to figure out why
> system-upgrade left me with about a 1k post-upgrade updates to apply.

Probably down to exactly the issue I mentioned. If you have third party
repos enabled, particularly, there are several known chains that will
lead to dnf-system-upgrade leaving huge numbers of packages out of the
upgrade. See https://bugzilla.redhat.com/show_bug.cgi?id=1263677 .
-- 
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net


-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: F23 broke dependencies

[Peter Robinson]

On Wed, Sep 23, 2015 at 4:31 PM, Richard Shaw  wrote:
> On Wed, Sep 23, 2015 at 7:00 AM, Vít Ondruch  wrote:
>>
>> > [trustedqsl]
>> >   tqsllib-devel-2.4-9.fc23.1.i686 requires tqsllib(x86-32) =
>> > 0:2.4-9.fc23
>> >   tqsllib-devel-2.4-9.fc23.1.x86_64 requires tqsllib(x86-64) =
>> > 0:2.4-9.fc23
>
>
> This is due to the fact that upstream puts both the application and library
> in the same source archive but they have different versions AND that no one
> reads the comments in the spec file which tells you to bump the library rev.
> I was waiting for the rebuilds to stop before fixing, I guess it's time.

Why does the app care about the RPM revisions, surely that should be a
dep on the exact version of the library alone. That way random spec
bumps should have no impact on the app.

Peter
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: Announcing the release of Fedora 23 Beta!

[Eric Griffith]

On Sep 23, 2015 10:37 PM, "Adam Williamson" 
wrote:
>
> On Wed, 2015-09-23 at 15:42 -0400, Eric Griffith wrote:
> > Also is "--distro-sync --best" advised or not? The wiki only listed
> > the
> > first part of that command, not those two additional flags.
>
> Well, last time I touched it, it recommended *trying* --best. You may
> have been looking at the 'upgrading with yum' page, which has different
> instructions.
>

I was looking at the dnf system upgrade feature page, which still
recommends masking packagekit-offline-updates

> --best will bail with a useful message if there are any updates
> available that cannot be applied - say you have foo-1 installed, and
> foo-2 is available, but can't be installed due to some dependency
> problem, --best will bail and tell you why. Without --best the upgrade
> will just leave 'foo' at 'foo-1' and proceed, without really telling
> you.
> --

Hmmm not what I thought it'd do. Im still trying to figure out why
system-upgrade left me with about a 1k post-upgrade updates to apply.
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: F23 broke dependencies

[Richard Shaw]

Maybe the simplest solution is to create a "noautobump" macro so bumpspec
will ignore it but error out or provide some sort of feedback so someone
can do it manually.

Thanks,
Richard
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: Announcing the release of Fedora 23 Beta!

[Adam Williamson]

On Wed, 2015-09-23 at 15:42 -0400, Eric Griffith wrote:
> Also is "--distro-sync --best" advised or not? The wiki only listed
> the
> first part of that command, not those two additional flags.

Well, last time I touched it, it recommended *trying* --best. You may
have been looking at the 'upgrading with yum' page, which has different
instructions.

--best will bail with a useful message if there are any updates
available that cannot be applied - say you have foo-1 installed, and
foo-2 is available, but can't be installed due to some dependency
problem, --best will bail and tell you why. Without --best the upgrade
will just leave 'foo' at 'foo-1' and proceed, without really telling
you.
-- 
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net


-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: Fedora 23 cloud image (and, for that matter, minimal anything) bloat

[Zbigniew Jędrzejewski-Szmek]

On Wed, Sep 23, 2015 at 03:28:57PM -0400, Matthew Miller wrote:
> On Wed, Sep 23, 2015 at 07:07:09PM +, Zbigniew Jędrzejewski-Szmek wrote:
> > Not really. localed is simply linked to libxkbcommon.so, so it will
> > not run without. Anyway, libxkbcommon.rpm is 260kb, so some potential
> > (complicated) scheme to avoid a dependency simply does not seem worth
> > the trouble.
> 
> No; bring brings in xkeyboard-config, which is over 5mb, putting it in
> the top 20 biggest packages. 5mb-on-disk isn't _huge_ but overall we
> grew 220mb on disk over two releases, and a whole bunch of "eh, who
> cares?" adds up. If it *got* us anything in terms of functionality,
> okay, I can sell that to people, but for the base, this is just bloat.

Bummer. The reason for libxkbcommon dependency is to be able to make
sure that the new config is valid. Before that was added we had a set
of rules and heuristics implemented in localed and regular bug reports
when typos and other mistakes were not caught by localed but Xorg
would not accept the new config. This is more important than might
seem, 'cause people tend to get grumpy when a misconfigured keyboard
mapping prevents them from typing in their password. So this dependency
does bring useful functionality.

Maybe it would be possible to change libxkbcommon to be able to provide
verification of the mapping configuration without having the mappings
installed, i.e. remove the dependency on xkeyboard-config. Then the
dependnecy on xkeyboard-config would have to be added to xserver or
to other consumers. I don't know if this is even feasible.

Zbyszek
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Schedule for Thursday's FPC Meeting (2015-09-24 16:00 UTC)

[James Antill]

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

 Local time information (via. rktime):

2015-09-24 09:00 Thu US/Pacific PDT
2015-09-24 12:00 Thu US/Eastern EDT
2015-09-24 16:00 Thu UTC <-
2015-09-24 17:00 Thu Europe/London  BST
2015-09-24 18:00 Thu Europe/Paris  CEST
2015-09-24 18:00 Thu Europe/Berlin CEST
2015-09-24 21:30 Thu Asia/Calcutta  IST
--new day--
2015-09-25 00:00 Fri Asia/Singapore SGT
2015-09-25 00:00 Fri Asia/Hong_Kong HKT
2015-09-25 01:00 Fri Asia/Tokyo JST
2015-09-25 02:00 Fri Australia/Brisbane EST

 Links to all tickets below can be found at: 

https://fedorahosted.org/fpc/report/13

= Followups =

#topic #566 RPM file triggers
.fpc 566
https://fedorahosted.org/fpc/ticket/566


#topic #567 Packaging Python 3 applications and modules for EPEL 7+
.fpc 567
https://fedorahosted.org/fpc/ticket/567

= New business =

#topic #569 texlive bundles lua
.fpc 569
https://fedorahosted.org/fpc/ticket/569

#topic #570 Allocating a soft static uid and gid for sssd
.fpc 570
https://fedorahosted.org/fpc/ticket/570

#topic #571 sabre/dav bundle exception in Horde
.fpc 571
https://fedorahosted.org/fpc/ticket/571

#topic #572 Mass review exception for php-zendframework
.fpc 572
https://fedorahosted.org/fpc/ticket/572


= Open Floor = 

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

https://fedorahosted.org/fpc/report/13

 If you would like to add something to this agenda, you can reply to
this e-mail, file a new ticket at https://fedorahosted.org/fpc,
e-mail me directly, or bring it up at the end of the meeting, during
the open floor topic. Note that added topics may be deferred until
the following meeting. 
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: Announcing the release of Fedora 23 Beta!

[Eric Griffith]

Is anyone else noticing dnf being really slow? Like taking 5mins+ to do a
simple metadata search
On Sep 23, 2015 15:51, "Pádraig Brady"  wrote:

> On 23/09/15 18:19, Richard W.M. Jones wrote:
> > On Tue, Sep 22, 2015 at 12:13:39PM -0400, Eric Griffith wrote:
> >> Suggested way to upgrade from 22 to 23? Fresh install? Fedup? Change
> >> release ver  for dnf? Did the new dnf upgrade tool get packaged?
> >
> > I've done this on a number of machines (I would say at least 5):
> >
> >
> https://fedoraproject.org/wiki/Upgrading_Fedora_using_yum#Fedora_22_-.3E_Fedora_23
> >
> > and it works fine.  You may hit a problem that the reboot command
> > doesn't work immediately after the update (sorry, don't have the BZ or
> > error message right now),
>
> https://bugzilla.redhat.com/1229416
>
> > but you can just do:
> >
> >   sync
> >   reboot -f
> >
> > to work around that, and the reboot command works afterwards.
>
> Yes it's an selinux issue. So I did:
>
>   sync
>   setenforce 0
>   reboot
>
> cheers,
> Pádraig
> --
> devel mailing list
> devel@lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/devel
> Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: Announcing the release of Fedora 23 Beta!

[Pádraig Brady]

On 23/09/15 18:19, Richard W.M. Jones wrote:
> On Tue, Sep 22, 2015 at 12:13:39PM -0400, Eric Griffith wrote:
>> Suggested way to upgrade from 22 to 23? Fresh install? Fedup? Change
>> release ver  for dnf? Did the new dnf upgrade tool get packaged?
> 
> I've done this on a number of machines (I would say at least 5):
> 
>   
> https://fedoraproject.org/wiki/Upgrading_Fedora_using_yum#Fedora_22_-.3E_Fedora_23
> 
> and it works fine.  You may hit a problem that the reboot command
> doesn't work immediately after the update (sorry, don't have the BZ or
> error message right now),

https://bugzilla.redhat.com/1229416

> but you can just do:
> 
>   sync
>   reboot -f
> 
> to work around that, and the reboot command works afterwards.

Yes it's an selinux issue. So I did:

  sync
  setenforce 0
  reboot

cheers,
Pádraig
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: Announcing the release of Fedora 23 Beta!

[Eric Griffith]

On Sep 23, 2015 13:48, "Andreas Tunek"  wrote:
>
> 2015-09-23 0:16 GMT+02:00 Adam Williamson :
> > On Tue, 2015-09-22 at 13:33 -0400, Matthew Miller wrote:
> >> On Tue, Sep 22, 2015 at 06:21:00PM +0100, Pádraig Brady wrote:
> >> > I just used dnf distro-sync as per:
> >> > https://fedoraproject.org/wiki/Upgrading_Fedora_using_yum#Fedora_22
> >> > _-.3E_Fedora_23
> >> >
> >> > This went fine, and I'm now typing this on F23 beta.
> >> > What are the main advantages of system-upgrade?
> >> > Should the above wiki mention the system-uprade instructions?
> >>
> >> There's actually a "fedup" script as part of the package. I think we
> >> should update the dnf-plugin-system-upgrade to Provide: fedup, and
> >> keep
> >> the instructions the same. Rationale:
> >
> > Sorry, but I already re-did all the wiki pages last week. Of course we
> > can change them again, but...
> >
> > https://fedoraproject.org/wiki/Upgrading was revised to list dnf-
> > system-upgrade as the 'recommended method' for upgrades to F23, and I
> > wrote https://fedoraproject.org/wiki/DNF_system_upgrade documenting
> > how to use it.
> >
> > The page Padraig linked to was not about fedup at all, it's the page
> > for doing your upgrades just using bare yum/dnf (which is not
> > officially supported, but we do have that page for known caveats and
> > best practices if you really must do it).
> > --
> > Adam Williamson
> > Fedora QA Community Monkey
> > IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
> > http://www.happyassassin.net
> >
> >
> I tried doing
>
> dnf system-upgrade download --releasever=23 --distro-sync --best
> dnf system-upgrade reboot
>
> as root but it rebooted directly when the upgrade started. Where can I
> find the logs to se what went wrong?

Make sure you are fully up to date before doing the upgrade. There was a
packagekit bug that would cause a dnf upgrade to fail immediately.

Also is "--distro-sync --best" advised or not? The wiki only listed the
first part of that command, not those two additional flags.
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: [fedora-virt] Do we need the Fedora 'virt' mailing list?

[W. Michael Petullo]

>>> One week - do you want to close the list or should I?  Dan suggested a
>>> method to use here:
>>>
>>> https://lists.fedoraproject.org/pipermail/virt/2015-September/004295.html
>> 
>> The xen@ one should probably go too.
 
> There's a few xen devs on that mailing list, I figured I'd leave it up to
> them. And if they wanted to keep it going, hand off maintenance to them.
> Haven't asked yet though

I occasionally find the Xen list very useful, mainly because Michael
Young is so helpful. For this reason, the Xen list has in the past been
a good place to bring up issues that arise as Fedora and Xen are updated.

-- 
Mike

:wq
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: Fedora 23 cloud image (and, for that matter, minimal anything) bloat

[Matthew Miller]

On Wed, Sep 23, 2015 at 07:07:09PM +, Zbigniew Jędrzejewski-Szmek wrote:
> Not really. localed is simply linked to libxkbcommon.so, so it will
> not run without. Anyway, libxkbcommon.rpm is 260kb, so some potential
> (complicated) scheme to avoid a dependency simply does not seem worth
> the trouble.

No; bring brings in xkeyboard-config, which is over 5mb, putting it in
the top 20 biggest packages. 5mb-on-disk isn't _huge_ but overall we
grew 220mb on disk over two releases, and a whole bunch of "eh, who
cares?" adds up. If it *got* us anything in terms of functionality,
okay, I can sell that to people, but for the base, this is just bloat.

-- 
Matthew Miller

Fedora Project Leader
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: Disable PulseAudio flat volumes to prevent it from pushing volume level to max

[kendell clark]

hi
I use thunderbird. I generally press control+shift+r to reply to all,
including the list. There is a reply to list option, but all it seems to
do is forward, so I'm not sure how. I'll investigate today since I've
got some time on my hands.
Thanks
Kendell clark


On 09/23/2015 10:41 AM, Jonathan Wakely wrote:
> On 23/09/15 00:09 +0200, Reindl Harald wrote:
>>
>> Am 22.09.2015 um 23:58 schrieb kendell clark:
>>> but I'm certainly not going to insist on it. I also need to
>>> figure out how to just reply to the list, rather than to the person who
>>> sent the message as well as the list
>>
>> get a mail-client which supports basic things like mail headers
>> instead all this shitty webmail-crap would be a start
> 
> Gmail works fine for lists, including quoting and bottom-posting:
> https://gcc.gnu.org/ml/gcc-help/2015-06/msg00053.html
> 
> You just need to make a modicum of effort and click the little [...]
> button instead of just banging out an email at the top and quoting the
> entire message.
> 
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: Fedora 23 cloud image (and, for that matter, minimal anything) bloat

[Zbigniew Jędrzejewski-Szmek]

On Wed, Sep 23, 2015 at 02:46:52PM -0400, Matthew Miller wrote:
> On Wed, Sep 23, 2015 at 06:35:04PM +, Zbigniew Jędrzejewski-Szmek wrote:
> > > > >5423400 xkeyboard-config  # really looks like a systemd dep chain
> > > > >involving plymouth
> > > > plymouth luckily is no hard dependency for anything
> > > "Involving plymouth" might have been wrong. libxkbcommon.so.0 looks
> > > like a direct dependency, from /usr/lib/systemd/systemd-localed.
> > Yes, libxkbcommon is used to validate the configuration set
> > with 'localectl set-keymap' or 'localectl set-x11-keymap'
> > (or directly through dbus api).
> 
> This is not relevant in most cloud images and in very, very few
> containers. Can we make the dependency optional in some way?

Not really. localed is simply linked to libxkbcommon.so, so it will
not run without. Anyway, libxkbcommon.rpm is 260kb, so some potential
(complicated) scheme to avoid a dependency simply does not seem worth
the trouble.

Zbyszek
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Summary/Minutes from today's FESCo Meeting (2015-09-23)

[Dennis Gilmore]

===
#fedora-meeting: FESCO (2015-09-23)
===


Meeting started by dgilmore at 18:02:30 UTC. The full logs are available
at
http://meetbot.fedoraproject.org/fedora-meeting/2015-09-23/fesco.2015-09-23-18.02.log.html
.



Meeting summary
---
* init process  (dgilmore, 18:02:31)

* #1427 List of release blocking deliverables  (dgilmore, 18:06:46)
  * LINK: https://fedorahosted.org/fesco/ticket/1427   (dgilmore,
18:06:47)
  * AGREED: : we will use nirik's wiki page until we can egt something
in a better format that can be used to visualise and by tools to
verify a compose  (dgilmore, 18:21:48)

* #1452 F23 System Wide Change: Two Week Atomic  (dgilmore, 18:22:45)
  * LINK: https://fedorahosted.org/fesco/ticket/1452   (dgilmore,
18:22:46)
  * AGREED: mattdm's proposal is accepted (5,0,1)  (dgilmore, 18:30:53)

* #1480  F24 Schedule  (dgilmore, 18:31:24)
  * LINK: https://fedorahosted.org/fesco/ticket/1480   (dgilmore,
18:31:25)
  * we will revisit the schedule next week with the changes in place
(dgilmore, 18:38:35)

* #1481  Decision on distro-sync during upgrades with dnf-plugin-system-
  (dgilmore, 18:38:53)

* #1481  Decision on distro-sync during upgrades with
  dnf-plugin-system-upgrade  (dgilmore, 18:38:59)
  * LINK: https://fedorahosted.org/fesco/ticket/1481   (dgilmore,
18:39:03)
  * ticket had meeting keyword but is worded for furture meeting, FESCo
to invite stakeholders to the FESCo meeting next week to discuss
(dgilmore, 18:47:20)

* Next week's chair  (dgilmore, 18:47:45)
  * ACTION: nirik to run the next meeting  (dgilmore, 18:48:30)

* Open Floor  (dgilmore, 18:48:43)
  * AGREED: untag the broken dnf build  (dgilmore, 18:53:24)

Meeting ended at 18:57:12 UTC.




Action Items

* nirik to run the next meeting




Action Items, by person
---
* nirik
  * nirik to run the next meeting
* **UNASSIGNED**
  * (none)




People Present (lines said)
---
* dgilmore (102)
* nirik (38)
* number80 (38)
* jkurik (16)
* jwb (13)
* paragan (12)
* zodbot (11)
* ajax (7)
* thozza (7)
* kushal (3)
* adamw (2)
* roshi (2)
* Southern_Gentlem (2)
* sgallagh (0)
* rishi (0)
* hguemar (0)




Generated by `MeetBot`_ 0.1.4

.. _`MeetBot`: http://wiki.debian.org/MeetBot



signature.asc
Description: This is a digitally signed message part.
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: Fedora 23 cloud image (and, for that matter, minimal anything) bloat

[Matthew Miller]

On Wed, Sep 23, 2015 at 06:35:04PM +, Zbigniew Jędrzejewski-Szmek wrote:
> > > >5423400 xkeyboard-config  # really looks like a systemd dep chain
> > > >involving plymouth
> > > plymouth luckily is no hard dependency for anything
> > "Involving plymouth" might have been wrong. libxkbcommon.so.0 looks
> > like a direct dependency, from /usr/lib/systemd/systemd-localed.
> Yes, libxkbcommon is used to validate the configuration set
> with 'localectl set-keymap' or 'localectl set-x11-keymap'
> (or directly through dbus api).

This is not relevant in most cloud images and in very, very few
containers. Can we make the dependency optional in some way?

-- 
Matthew Miller

Fedora Project Leader
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: Announcing the release of Fedora 23 Beta!

[Zbigniew Jędrzejewski-Szmek]

On Wed, Sep 23, 2015 at 07:47:58PM +0200, Andreas Tunek wrote:
> 2015-09-23 0:16 GMT+02:00 Adam Williamson :
> > On Tue, 2015-09-22 at 13:33 -0400, Matthew Miller wrote:
> >> On Tue, Sep 22, 2015 at 06:21:00PM +0100, Pádraig Brady wrote:
> >> > I just used dnf distro-sync as per:
> >> > https://fedoraproject.org/wiki/Upgrading_Fedora_using_yum#Fedora_22
> >> > _-.3E_Fedora_23
> >> >
> >> > This went fine, and I'm now typing this on F23 beta.
> >> > What are the main advantages of system-upgrade?
> >> > Should the above wiki mention the system-uprade instructions?
> >>
> >> There's actually a "fedup" script as part of the package. I think we
> >> should update the dnf-plugin-system-upgrade to Provide: fedup, and
> >> keep
> >> the instructions the same. Rationale:
> >
> > Sorry, but I already re-did all the wiki pages last week. Of course we
> > can change them again, but...
> >
> > https://fedoraproject.org/wiki/Upgrading was revised to list dnf-
> > system-upgrade as the 'recommended method' for upgrades to F23, and I
> > wrote https://fedoraproject.org/wiki/DNF_system_upgrade documenting
> > how to use it.
> >
> > The page Padraig linked to was not about fedup at all, it's the page
> > for doing your upgrades just using bare yum/dnf (which is not
> > officially supported, but we do have that page for known caveats and
> > best practices if you really must do it).
> > --
> > Adam Williamson
> > Fedora QA Community Monkey
> > IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
> > http://www.happyassassin.net
> >
> >
> I tried doing
> 
> dnf system-upgrade download --releasever=23 --distro-sync --best
> dnf system-upgrade reboot
> 
> as root but it rebooted directly when the upgrade started. Where can I
> find the logs to se what went wrong?

journalctl -b-1 --system

(In general, there's nothing special about the dnf upgrade
environment, so normal journalctl commands should work.)

Zbyszek
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: Fedora 23 cloud image (and, for that matter, minimal anything) bloat

[Zbigniew Jędrzejewski-Szmek]

On Mon, Sep 21, 2015 at 11:35:54AM -0400, Matthew Miller wrote:
> On Mon, Sep 21, 2015 at 05:11:24PM +0200, Reindl Harald wrote:
> > >5423400 xkeyboard-config  # really looks like a systemd dep chain
> > >involving plymouth
> > plymouth luckily is no hard dependency for anything
> 
> "Involving plymouth" might have been wrong. libxkbcommon.so.0 looks
> like a direct dependency, from /usr/lib/systemd/systemd-localed.
Yes, libxkbcommon is used to validate the configuration set
with 'localectl set-keymap' or 'localectl set-x11-keymap'
(or directly through dbus api).

> I also don't know how plymouth crept in, though. 

Zbyszek
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: Announcing the release of Fedora 23 Beta!

[Andreas Tunek]

2015-09-23 0:16 GMT+02:00 Adam Williamson :
> On Tue, 2015-09-22 at 13:33 -0400, Matthew Miller wrote:
>> On Tue, Sep 22, 2015 at 06:21:00PM +0100, Pádraig Brady wrote:
>> > I just used dnf distro-sync as per:
>> > https://fedoraproject.org/wiki/Upgrading_Fedora_using_yum#Fedora_22
>> > _-.3E_Fedora_23
>> >
>> > This went fine, and I'm now typing this on F23 beta.
>> > What are the main advantages of system-upgrade?
>> > Should the above wiki mention the system-uprade instructions?
>>
>> There's actually a "fedup" script as part of the package. I think we
>> should update the dnf-plugin-system-upgrade to Provide: fedup, and
>> keep
>> the instructions the same. Rationale:
>
> Sorry, but I already re-did all the wiki pages last week. Of course we
> can change them again, but...
>
> https://fedoraproject.org/wiki/Upgrading was revised to list dnf-
> system-upgrade as the 'recommended method' for upgrades to F23, and I
> wrote https://fedoraproject.org/wiki/DNF_system_upgrade documenting
> how to use it.
>
> The page Padraig linked to was not about fedup at all, it's the page
> for doing your upgrades just using bare yum/dnf (which is not
> officially supported, but we do have that page for known caveats and
> best practices if you really must do it).
> --
> Adam Williamson
> Fedora QA Community Monkey
> IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
> http://www.happyassassin.net
>
>
I tried doing

dnf system-upgrade download --releasever=23 --distro-sync --best
dnf system-upgrade reboot

as root but it rebooted directly when the upgrade started. Where can I
find the logs to se what went wrong?
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Schedule for Wednesday's FESCo Meeting (2015-09-23)

[Dennis Gilmore]

Following is the list of topics that will be discussed in the FESCo
meeting Wednesday at 18:00UTC in #fedora-meeting on irc.freenode.net.

To convert UTC to your local time, take a look at
  http://fedoraproject.org/wiki/UTCHowto

or run:
  date -d '2015-09-23 18:00 UTC'


Links to all tickets below can be found at: 
https://fedorahosted.org/fesco/report/9

= Followups =

#topic #1427 List of release blocking deliverables
.fesco 1427
https://fedorahosted.org/fesco/ticket/1427

#topic #1452 F23 System Wide Change: Two Week Atomic
.fesco 1452
https://fedorahosted.org/fesco/ticket/1452

= New business =

#topic #1480  F24 Schedule
.fesco 1480
https://fedorahosted.org/fesco/ticket/1480

#topic #1481  Decision on distro-sync during upgrades with dnf-plugin-system-
upgrade
.fesco 1481
https://fedorahosted.org/fesco/ticket/1481

= Open Floor = 

For more complete details, please visit each individual ticket.  The
report of the agenda items can be found at
https://fedorahosted.org/fesco/report/9

If you would like to add something to this agenda, you can reply to
this e-mail, file a new ticket at https://fedorahosted.org/fesco,
e-mail me directly, or bring it up at the end of the meeting, during
the open floor topic. Note that added topics may be deferred until
the following meeting. 

signature.asc
Description: This is a digitally signed message part.
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: F23 broke dependencies

[Michael Schwendt]

On Wed, 23 Sep 2015 10:31:15 -0500, Richard Shaw wrote:

> On Wed, Sep 23, 2015 at 7:00 AM, Vít Ondruch  wrote:
> 
> > > [trustedqsl]
> > >   tqsllib-devel-2.4-9.fc23.1.i686 requires tqsllib(x86-32) =
> > 0:2.4-9.fc23
> > >   tqsllib-devel-2.4-9.fc23.1.x86_64 requires tqsllib(x86-64) =
> > 0:2.4-9.fc23
> >
> 
> This is due to the fact that upstream puts both the application and library
> in the same source archive but they have different versions AND that no one
> reads the comments in the spec file which tells you to bump the library
> rev. I was waiting for the rebuilds to stop before fixing, I guess it's
> time.

$ rpmdev-bumpspec -V trustedqsl.spec
trustedqsl.spec
-%{tqslrel}
+%{tqslrel}.1

trustedqsl.spec
-%{libtqslrel}
+%{libtqslrel}.1

trustedqsl.spec
-%{libtqslrel}
+%{libtqslrel}.1

That won't work, of course, if those macros are used elsewhere in the
spec file.

One work-around that would be compatible with rpmdev-bumpspec is to
move a common sub-release value into the %baserelease or %release variable:

  %global baserelease 0%{?dist}
  %global tqslrel 10.%{baserelease}
  %global libtqslrel 10.%{baserelease}

That is because the script assumes that either %baserelease or %release
is used throughout the entire spec file to set the package release values.
It won't touch the Release tags anymore then, but only the first %baserelease
or %release macro definition:

$ rpmdev-bumpspec -V trustedqsl.spec
trustedqsl.spec
-0%{?dist}
+1%{?dist}

$ rpmdev-bumpspec -V trustedqsl.spec
trustedqsl.spec
-1%{?dist}
+2%{?dist}

$ rpmdev-bumpspec -V trustedqsl.spec
trustedqsl.spec
-2%{?dist}
+3%{?dist}

There will be an extra number in your release value then, however. ;-)
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: [fedora-virt] Do we need the Fedora 'virt' mailing list?

[Cole Robinson]

On 09/23/2015 01:30 PM, Richard W.M. Jones wrote:
> On Wed, Sep 23, 2015 at 06:27:09PM +0100, Richard W.M. Jones wrote:
>> One week - do you want to close the list or should I?  Dan suggested a
>> method to use here:
>>
>> https://lists.fedoraproject.org/pipermail/virt/2015-September/004295.html
> 
> The xen@ one should probably go too.
> 
> Rich.
> 

There's a few xen devs on that mailing list, I figured I'd leave it up to
them. And if they wanted to keep it going, hand off maintenance to them.
Haven't asked yet though

- Cole
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: [fedora-virt] Do we need the Fedora 'virt' mailing list?

[Cole Robinson]

On 09/23/2015 01:27 PM, Richard W.M. Jones wrote:
> On Wed, Sep 16, 2015 at 10:08:57AM -0400, Cole Robinson wrote:
>> On 09/16/2015 08:20 AM, Daniel P. Berrange wrote:
>>> On Wed, Sep 16, 2015 at 12:45:28PM +0100, Richard W.M. Jones wrote:

 Crickets ... https://lists.fedoraproject.org/pipermail/virt/

 The virt list has long been in an odd place.  Fedora has best in class
 virt support, because so many virt developers use it.  It also follows
 upstream very closely, with upstream packages like libvirt and qemu
 going straight into Rawhide without any significant patching.

 So there isn't really much need for a Fedora+virt-specific list, since
 almost any question should go upstream to one of the following lists:

  - https://www.redhat.com/mailman/listinfo/virt-tools-list
  - https://libvirt.org/contact.html#email
  - http://wiki.qemu.org/MailingLists
  - https://libosinfo.org/communicate/
  - https://www.redhat.com/mailman/listinfo/libguestfs

 Or as a last resort if it really is a rare virt integration issue that
 only affects to Fedora, then:

  - https://admin.fedoraproject.org/mailman/listinfo/users
  - https://admin.fedoraproject.org/mailman/listinfo/devel

 Can we kill the virt list?
>>>
>>> At this point in time, I'd say yes.
>>>
>>
>> Yeah I've thought similar for a long while too. So I'm for it. I'll leave a
>> bit more time for discussion but if nothing changes I'll close the list next 
>> week.
> 
> One week - do you want to close the list or should I?  Dan suggested a
> method to use here:
> 

It's on my list but I might not get to it today, so go for it

> https://lists.fedoraproject.org/pipermail/virt/2015-September/004295.html
> 
> I was also interested in whether any web pages reference this list.  I
> think just these ones:
> 
> https://fedoraproject.org/wiki/Virtualization#News
> https://fedoraproject.org/wiki/Virtualization_Preview_Repository#Contact
> https://www.redhat.com/mailman/listinfo/fedora-virt
> https://fedoraproject.org/wiki/Virtualization/News
> 

I don't think it's in any man pages or anything, so that looks right to me

Thanks,
Cole
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: [fedora-virt] Do we need the Fedora 'virt' mailing list?

[Richard W.M. Jones]

On Wed, Sep 23, 2015 at 06:27:09PM +0100, Richard W.M. Jones wrote:
> One week - do you want to close the list or should I?  Dan suggested a
> method to use here:
> 
> https://lists.fedoraproject.org/pipermail/virt/2015-September/004295.html

The xen@ one should probably go too.

Rich.

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
libguestfs lets you edit virtual machines.  Supports shell scripting,
bindings from many languages.  http://libguestfs.org
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: [fedora-virt] Do we need the Fedora 'virt' mailing list?

[Richard W.M. Jones]

On Wed, Sep 16, 2015 at 10:08:57AM -0400, Cole Robinson wrote:
> On 09/16/2015 08:20 AM, Daniel P. Berrange wrote:
> > On Wed, Sep 16, 2015 at 12:45:28PM +0100, Richard W.M. Jones wrote:
> >>
> >> Crickets ... https://lists.fedoraproject.org/pipermail/virt/
> >>
> >> The virt list has long been in an odd place.  Fedora has best in class
> >> virt support, because so many virt developers use it.  It also follows
> >> upstream very closely, with upstream packages like libvirt and qemu
> >> going straight into Rawhide without any significant patching.
> >>
> >> So there isn't really much need for a Fedora+virt-specific list, since
> >> almost any question should go upstream to one of the following lists:
> >>
> >>  - https://www.redhat.com/mailman/listinfo/virt-tools-list
> >>  - https://libvirt.org/contact.html#email
> >>  - http://wiki.qemu.org/MailingLists
> >>  - https://libosinfo.org/communicate/
> >>  - https://www.redhat.com/mailman/listinfo/libguestfs
> >>
> >> Or as a last resort if it really is a rare virt integration issue that
> >> only affects to Fedora, then:
> >>
> >>  - https://admin.fedoraproject.org/mailman/listinfo/users
> >>  - https://admin.fedoraproject.org/mailman/listinfo/devel
> >>
> >> Can we kill the virt list?
> > 
> > At this point in time, I'd say yes.
> > 
> 
> Yeah I've thought similar for a long while too. So I'm for it. I'll leave a
> bit more time for discussion but if nothing changes I'll close the list next 
> week.

One week - do you want to close the list or should I?  Dan suggested a
method to use here:

https://lists.fedoraproject.org/pipermail/virt/2015-September/004295.html

I was also interested in whether any web pages reference this list.  I
think just these ones:

https://fedoraproject.org/wiki/Virtualization#News
https://fedoraproject.org/wiki/Virtualization_Preview_Repository#Contact
https://www.redhat.com/mailman/listinfo/fedora-virt
https://fedoraproject.org/wiki/Virtualization/News

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
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: Announcing the release of Fedora 23 Beta!

[Richard W.M. Jones]

On Tue, Sep 22, 2015 at 12:13:39PM -0400, Eric Griffith wrote:
> Suggested way to upgrade from 22 to 23? Fresh install? Fedup? Change
> release ver  for dnf? Did the new dnf upgrade tool get packaged?

I've done this on a number of machines (I would say at least 5):

  
https://fedoraproject.org/wiki/Upgrading_Fedora_using_yum#Fedora_22_-.3E_Fedora_23

and it works fine.  You may hit a problem that the reboot command
doesn't work immediately after the update (sorry, don't have the BZ or
error message right now), but you can just do:

  sync
  reboot -f

to work around that, and the reboot command works afterwards.

Rich.

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
virt-top is 'top' for virtual machines.  Tiny program with many
powerful monitoring features, net stats, disk stats, logging, etc.
http://people.redhat.com/~rjones/virt-top
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: F23 broke dependencies

[Kalev Lember]

On 09/23/2015 05:31 PM, Richard Shaw wrote:
> On Wed, Sep 23, 2015 at 7:00 AM, Vít Ondruch  > wrote:
> 
> > [trustedqsl]
> >   tqsllib-devel-2.4-9.fc23.1.i686 requires tqsllib(x86-32) =
> 0:2.4-9.fc23
> >   tqsllib-devel-2.4-9.fc23.1.x86_64 requires tqsllib(x86-64) =
> 0:2.4-9.fc23
> 
> 
> This is due to the fact that upstream puts both the application and
> library in the same source archive but they have different versions AND
> that no one reads the comments in the spec file which tells you to bump
> the library rev. I was waiting for the rebuilds to stop before fixing, I
> guess it's time.

Automated mass rebuilds tend to all use rpmdev-bumpspec and it has no
idea how to read comments in the spec file :) Spec files should be
written in a way so that they don't break when rpmdev-bumpspec touches them.

-- 
Hope this helps,
Kalev
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Fedora Rawhide 20150923 compose check report

[Fedora compose checker]

No missing expected images.

No images in this compose but not Rawhide 20150922

Images in Rawhide 20150922 but not this:

Xfce disk raw armhfp
Cloud docker x86_64

Failed openQA tests: 52 of 52

ID: 3342Test: i386 kde_live default_install
ID: 3341Test: x86_64 workstation_live default_install@uefi
ID: 3340Test: x86_64 workstation_live default_install
ID: 3339Test: x86_64 kde_live default_install
ID: 3338Test: i386 workstation_live default_install
ID: 3337Test: i386 generic_boot default_install
ID: 3336Test: x86_64 generic_boot default_install@uefi
ID: 3335Test: x86_64 generic_boot default_install
ID: 3334Test: i386 universal upgrade_desktop_32bit
ID: Test: i386 universal server_lvmthin
ID: 3332Test: i386 universal server_ext3
ID: 3331Test: i386 universal server_btrfs
ID: 3330Test: i386 universal server_software_raid
ID: 3329Test: i386 universal server_simple_encrypted
ID: 3328Test: i386 universal server_repository_http_graphical
ID: 3327Test: i386 universal server_scsi_updates_img
ID: 3326Test: i386 universal package_set_minimal
ID: 3325Test: x86_64 universal server_no_swap@uefi
ID: 3324Test: x86_64 universal server_lvmthin@uefi
ID: 3323Test: x86_64 universal server_ext3@uefi
ID: 3322Test: x86_64 universal server_btrfs@uefi
ID: 3321Test: x86_64 universal server_software_raid@uefi
ID: 3320Test: x86_64 universal server_multi_empty@uefi
ID: 3319Test: x86_64 universal server_simple_free_space@uefi
ID: 3318Test: x86_64 universal server_simple_encrypted@uefi
ID: 3317Test: x86_64 universal server_delete_partial@uefi
ID: 3316Test: x86_64 universal server_delete_pata@uefi
ID: 3315Test: x86_64 universal server_sata_multi@uefi
ID: 3314Test: x86_64 universal european_language_install
ID: 3313Test: x86_64 universal server_shrink_ntfs
ID: 3312Test: x86_64 universal server_shrink_ext4
ID: 3311Test: x86_64 universal server_updates_img_local
ID: 3310Test: x86_64 universal upgrade_desktop_64bit
ID: 3309Test: x86_64 universal upgrade_minimal_64bit
ID: 3308Test: x86_64 universal server_kickstart_hdd
ID: 3307Test: x86_64 universal server_no_swap
ID: 3306Test: x86_64 universal server_lvmthin
ID: 3305Test: x86_64 universal server_ext3
ID: 3304Test: x86_64 universal server_btrfs
ID: 3303Test: x86_64 universal server_software_raid
ID: 3302Test: x86_64 universal server_multi_empty
ID: 3301Test: x86_64 universal server_simple_free_space
ID: 3300Test: x86_64 universal server_simple_encrypted
ID: 3299Test: x86_64 universal server_delete_partial
ID: 3298Test: x86_64 universal server_repository_http_variation
ID: 3297Test: x86_64 universal server_repository_http_graphical
ID: 3296Test: x86_64 universal server_mirrorlist_graphical
ID: 3295Test: x86_64 universal server_delete_pata
ID: 3294Test: x86_64 universal server_kickstart_user_creation
ID: 3293Test: x86_64 universal server_scsi_updates_img
ID: 3292Test: x86_64 universal server_sata_multi
ID: 3291Test: x86_64 universal package_set_minimal
-- 
Mail generated by check-compose:
https://git.fedorahosted.org/cgit/fedora-qa.git/tree/check-compose
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: Disable PulseAudio flat volumes to prevent it from pushing volume level to max

[Jonathan Wakely]

On 23/09/15 00:09 +0200, Reindl Harald wrote:


Am 22.09.2015 um 23:58 schrieb kendell clark:

but I'm certainly not going to insist on it. I also need to
figure out how to just reply to the list, rather than to the person who
sent the message as well as the list


get a mail-client which supports basic things like mail headers 
instead all this shitty webmail-crap would be a start


Gmail works fine for lists, including quoting and bottom-posting:
https://gcc.gnu.org/ml/gcc-help/2015-06/msg00053.html

You just need to make a modicum of effort and click the little [...]
button instead of just banging out an email at the top and quoting the
entire message.

--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: Announcing the release of Fedora 23 Beta!

[Jonathan Wakely]

On 22/09/15 16:30 +0100, Richard Hughes wrote:

On 22 September 2015 at 16:16, Neal Gompa  wrote:

Looks like Fedora 23 is shaping up to be an exciting release!


It does, but not exciting enough to use HTML email. Can you switch
your email client to use text emails please.


And trim the quoted text instead of replying with the entire content
of whatever you're replying to.

--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: F23 broke dependencies

[Richard Shaw]

On Wed, Sep 23, 2015 at 7:00 AM, Vít Ondruch  wrote:

> > [trustedqsl]
> >   tqsllib-devel-2.4-9.fc23.1.i686 requires tqsllib(x86-32) =
> 0:2.4-9.fc23
> >   tqsllib-devel-2.4-9.fc23.1.x86_64 requires tqsllib(x86-64) =
> 0:2.4-9.fc23
>

This is due to the fact that upstream puts both the application and library
in the same source archive but they have different versions AND that no one
reads the comments in the spec file which tells you to bump the library
rev. I was waiting for the rebuilds to stop before fixing, I guess it's
time.

Thanks,
Richard
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: F23 broke dependencies

[Jonathan Wakely]

On 23/09/15 23:11 +0800, Christopher Meng wrote:

  licq-1.8.2-9.fc23.armv7hl requires libboost_regex.so.1.57.0


What‘s wrong with boost regex on f23 ARM?


Nothing, but it's version 1.58.0 and licq fails to build.

This is for rawhide, but IIRC it's the same problem in F23:
https://bugzilla.redhat.com/show_bug.cgi?id=1259779


--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: F23 broke dependencies

[Christopher Meng]

>   licq-1.8.2-9.fc23.armv7hl requires libboost_regex.so.1.57.0

What‘s wrong with boost regex on f23 ARM?

-- 

Yours sincerely,
Christopher Meng

http://awk.io
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Intent to retire: csisat

[Jerry James]

I intend to retire the csisat package in Rawhide and F-23 in 2 days.
If somebody wants to keep it, let me know and I will turn the package
over to you.

The csisat package was originally added to Fedora in pursuit of the
BLAST program, which is a suite of tools for analyzing C programs.
However, BLAST itself turned out to have license issues that were
never resolved.  It has since been replaced by other tools, which
don't use csisat, so I see no point in keeping this package in Fedora.
-- 
Jerry James
http://www.jamezone.org/
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Fedora 23 Branched 20150923 compose check report

[Fedora compose checker]

Missing expected images:

Cloud disk raw i386
Cloud disk raw x86_64
Cloud_atomic disk raw x86_64
Generic boot i386
Generic boot x86_64

No images in this compose but not 23 Branched 20150922

No images in 23 Branched 20150922 but not this.

Failed openQA tests: 5 of 5

ID: 3290Test: i386 kde_live default_install
ID: 3289Test: i386 workstation_live default_install
ID: 3288Test: x86_64 workstation_live default_install@uefi
ID: 3287Test: x86_64 workstation_live default_install
ID: 3286Test: x86_64 kde_live default_install
-- 
Mail generated by check-compose:
https://git.fedorahosted.org/cgit/fedora-qa.git/tree/check-compose
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

the python package [was: cloud image size blah blah blah] bloat

[Matthew Miller]

On Wed, Sep 23, 2015 at 04:18:52AM -0400, Robert Kuska wrote:
> > Cool. Let's put you on the future list for
> > https://fedorahosted.org/fedora-badges/ticket/378 :)
> I've tried to move idlelib and lib2to3 to -tools subpackage
> but unfortunately I had to revert this change as distutils
> uses lib2to3 module and idlelib is used by -tkinter meaning
> that -tkinter would have to depend on -tools subpackage but
> -tools already requires -tkinter so it would lead to cyclic dep.

Could they maybe be moved to a new subpackage? It seems unfortunate to
carry such heavy deps simply in case someone wants wants Tk inside a
container or other minimal use.

On a tangent, the tkinter subpackage, says:

  The Tkinter (Tk interface) program is an graphical user interface for
  the Python scripting language.

  You should install the tkinter package if you'd like to use a
  graphical user interface for Python programming.

... but this is wrong, right? It's a widget/GUI toolkit, not a GUI
itself, isn't it?

-- 
Matthew Miller

Fedora Project Leader
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: Announcing the release of Fedora 23 Beta!

[Matthew Miller]

On Wed, Sep 23, 2015 at 03:58:28AM +0200, Ralf Corsepius wrote:
> >There's actually a "fedup" script as part of the package. I think we
> >should update the dnf-plugin-system-upgrade to Provide: fedup, and keep
> >the instructions the same. Rationale:
> 
> IMO, this discussion is moot.

It's not moot -- it's a suggestion to...

> Because ppckaging-wise, the dnf-plugin-system-upgrade situation
> currently is broken [1]:
> dnf-plugin-system-upgrade Obsoletes: fedup, but lacks the
> corresponding Provides.

... add that Provides. :)


-- 
Matthew Miller

Fedora Project Leader
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

psabata retired perl-Data-Dump-Streamer in master

[notifications]

psabata retired perl-Data-Dump-Streamer in master
https://admin.fedoraproject.org/pkgdb/package/perl-Data-Dump-Streamer/
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-de...@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel

[Bug 1231297] perl-Carp-REPL-0.18-1.fc23 FTBFS with perl-5.22

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1231297
Bug 1231297 depends on bug 1231204, which changed state.

Bug 1231204 Summary: perl-Data-Dump-Streamer-2.38-4.fc23: FTBFS with Perl 5.22
https://bugzilla.redhat.com/show_bug.cgi?id=1231204

   What|Removed |Added

 Status|ASSIGNED|CLOSED
 Resolution|--- |CURRENTRELEASE



-- 
You are receiving this mail because:
You are on the CC list for the bug.
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-de...@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel

[Bug 1231285] perl-Devel-REPL-1.003026-1.fc23 FTBFS with perl-5.22

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1231285
Bug 1231285 depends on bug 1231204, which changed state.

Bug 1231204 Summary: perl-Data-Dump-Streamer-2.38-4.fc23: FTBFS with Perl 5.22
https://bugzilla.redhat.com/show_bug.cgi?id=1231204

   What|Removed |Added

 Status|ASSIGNED|CLOSED
 Resolution|--- |CURRENTRELEASE



-- 
You are receiving this mail because:
You are on the CC list for the bug.
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-de...@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel

Re: Heads up: glibmm/gtkmm now requires -std=c++11

[Kalev Lember]

On 09/23/2015 02:56 AM, Josh Stone wrote:
> On 09/22/2015 05:49 PM, Mamoru TASAKA wrote:
>> Rather, can't be pkgconfig file in gtkmm30 modified for now to add -std=c++11
>> to Cflags?
> 
> I'd guess that they really require *at least* c++11.
> 
> A project might instead choose gnu++11, c++14, gnu++14, etc.

Yes, agreed; I think that's a good reason why to not put it in the
pkgconfig file.

I am sure we'll sooner or later find a project that wants to support
another C++ dialect, such as C++14, and then if gtkmm30's pkgconfig file
overrides it, we'd a conflict between -std=c++11 and -std=c++14 and then
we'd have to back it out from the pkgconfig file and would be back to
square one :)

Good idea though, thanks!

-- 
Kalev
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

[Bug 1231204] perl-Data-Dump-Streamer-2.38-4.fc23: FTBFS with Perl 5.22

[bugzilla]

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

Petr Šabata  changed:

   What|Removed |Added

 Status|ASSIGNED|CLOSED
 Resolution|--- |CURRENTRELEASE
Last Closed||2015-09-23 09:49:13



--- Comment #4 from Petr Šabata  ---
Non-trivial to fix and upstream seems dead.
Retiring in F23+.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-de...@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel

[Bug 1231880] perl-Devel-BeginLift-0.001003-9.fc23 FTBFS with perl-5.22: unsatisfied depencency

[bugzilla]

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

Fedora Admin XMLRPC Client  changed:

   What|Removed |Added

   Assignee|psab...@redhat.com  |extras-orphan@fedoraproject
   ||.org



--- Comment #3 from Fedora Admin XMLRPC Client  
---
This package has changed ownership in the Fedora Package Database.  Reassigning
to the new owner of this component.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-de...@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel

Re: Trying to contact package maintainer for boinc-client

[Germano Massullo]

Lastest update [1] has been submitted by user [2] that is a provenpackager


**What is a provenpackager?**
Provenpackagers are members of the 'provenpackager' group. In addition
to the rights granted to members of 'packager', provenpackagers are able
to commit changes to packages they do not own or maintain.


[1] https://bodhi.fedoraproject.org/updates/FEDORA-2015-12667
[2] https://bodhi.fedoraproject.org/users/corsepiu
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: F23 broke dependencies

[Vít Ondruch]

Dne 23.9.2015 v 15:07 Kalev Lember napsal(a):
> On 09/23/2015 02:00 PM, Vít Ondruch wrote:
>> Will there be some effor to clean this up prior release?
> Yes, same plan as in previous releases: anything that still has broken
> deps by the time of final freeze is going to get retired. I opened
> https://fedorahosted.org/rel-eng/ticket/6260 to sort this out and looks
> like I'll be the one sending out warning mails.
>
> I'll send them out later tonight.
>

Ah, ok :)

Thanks


Vít
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: F23 broke dependencies

[Kalev Lember]

On 09/23/2015 02:00 PM, Vít Ondruch wrote:
> Will there be some effor to clean this up prior release?

Yes, same plan as in previous releases: anything that still has broken
deps by the time of final freeze is going to get retired. I opened
https://fedorahosted.org/rel-eng/ticket/6260 to sort this out and looks
like I'll be the one sending out warning mails.

I'll send them out later tonight.

-- 
Kalev
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: Packaging Icinga 2 requiring SELinux assistance

[Miroslav Grepl]

On 09/23/2015 01:57 PM, Alec Leamas wrote:
> On 23/09/15 13:16, Petr Lautrbach wrote:
>> On 09/22/2015 08:46 PM, Shawn Starr wrote:
> 
>> However in long terms it's better to incorporate a package policy  to
>> the system policy. You can either file a bug against selinux-policy or
>> try to contribute yourself using this [2] howto.
> 
> That howto is somewhat sketchy if you (as me) are new to this. However,
>  Miroslaw has made some promises to improve it [3]

Yeap. I will update "How to Contribute" section with more details and
examples as my next step.

Thx.


> 
> Cheers!
> 
> --alec
> 
> [3] https://github.com/fedora-selinux/selinux-policy/issues/38
> 
> 
> 
> 


-- 
Miroslav Grepl
Senior Software Engineer, SELinux Solutions
Red Hat, Inc.
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

perl-Crypt-Rijndael license corrected

[Petr Pisar]

Hello,

I corrected lincese declaration in perl-Crypt-Rijndael-1.13-1.fc24
from (LGPLv3) to (LGPLv3 and LGPLv2+ and (GPL+ or Artistic)).

-- Petr


-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

rawhide report: 20150923 changes

[Fedora Rawhide Report]

Compose started at Wed Sep 23 05:15:03 UTC 2015
Broken deps for i386
--
[IQmol]
IQmol-2.3.0-9.fc24.i686 requires libboost_serialization.so.1.58.0
IQmol-2.3.0-9.fc24.i686 requires libboost_iostreams.so.1.58.0
IQmol-2.3.0-9.fc24.i686 requires libOpenMeshCore.so.3.2
[Macaulay2]
Macaulay2-1.6-17.fc24.i686 requires libntl.so.14
[Singular]
Singular-3.1.6-16.fc24.i686 requires libntl.so.14
[apache-scout]
apache-scout-1.2.6-11.fc21.noarch requires mvn(org.apache.juddi:uddi-ws)
apache-scout-1.2.6-11.fc21.noarch requires 
mvn(org.apache.juddi:juddi-client)
[aqsis]
aqsis-1.8.2-20.fc24.i686 requires libboost_thread.so.1.58.0
aqsis-1.8.2-20.fc24.i686 requires libboost_system.so.1.58.0
aqsis-1.8.2-20.fc24.i686 requires libboost_regex.so.1.58.0
aqsis-1.8.2-20.fc24.i686 requires libboost_program_options.so.1.58.0
aqsis-1.8.2-20.fc24.i686 requires libboost_filesystem.so.1.58.0
aqsis-core-1.8.2-20.fc24.i686 requires libboost_wave.so.1.58.0
aqsis-core-1.8.2-20.fc24.i686 requires libboost_thread.so.1.58.0
aqsis-core-1.8.2-20.fc24.i686 requires libboost_system.so.1.58.0
aqsis-core-1.8.2-20.fc24.i686 requires libboost_regex.so.1.58.0
aqsis-core-1.8.2-20.fc24.i686 requires libboost_iostreams.so.1.58.0
aqsis-core-1.8.2-20.fc24.i686 requires libboost_filesystem.so.1.58.0
aqsis-libs-1.8.2-20.fc24.i686 requires libboost_thread.so.1.58.0
aqsis-libs-1.8.2-20.fc24.i686 requires libboost_system.so.1.58.0
aqsis-libs-1.8.2-20.fc24.i686 requires libboost_regex.so.1.58.0
aqsis-libs-1.8.2-20.fc24.i686 requires libboost_iostreams.so.1.58.0
aqsis-libs-1.8.2-20.fc24.i686 requires libboost_filesystem.so.1.58.0
[aws]
aws-tools-2015-2.fc23.i686 requires libaws_ssl.so
[bro]
bro-2.3.2-6.fc23.i686 requires libjemalloc.so.1
[bwm-ng]
bwm-ng-0.6-18.fc24.i686 requires libstatgrab.so.6
[cp2k]
cp2k-openmpi-2.7.0-0.2.20150911svn15878.fc24.i686 requires 
libmpi_usempif08.so.0(openmpi-i386)
cp2k-openmpi-2.7.0-0.2.20150911svn15878.fc24.i686 requires 
libmpi_usempi_ignore_tkr.so.0(openmpi-i386)
cp2k-openmpi-2.7.0-0.2.20150911svn15878.fc24.i686 requires 
libmpi_mpifh.so.2(openmpi-i386)
cp2k-openmpi-2.7.0-0.2.20150911svn15878.fc24.i686 requires 
libmpi.so.1(openmpi-i386)
[derelict]
derelict-3-32.20141022git7fc1714.fc23.i686 requires 
libphobos2-ldc-debug.so.66
derelict-3-32.20141022git7fc1714.fc23.i686 requires 
libdruntime-ldc-debug.so.66
derelict-AL-3-32.20141022git7fc1714.fc23.i686 requires 
libphobos2-ldc-debug.so.66
derelict-AL-3-32.20141022git7fc1714.fc23.i686 requires 
libdruntime-ldc-debug.so.66
derelict-ALURE-3-32.20141022git7fc1714.fc23.i686 requires 
libphobos2-ldc-debug.so.66
derelict-ALURE-3-32.20141022git7fc1714.fc23.i686 requires 
libdruntime-ldc-debug.so.66
derelict-ASSIMP3-3-32.20141022git7fc1714.fc23.i686 requires 
libphobos2-ldc-debug.so.66
derelict-ASSIMP3-3-32.20141022git7fc1714.fc23.i686 requires 
libdruntime-ldc-debug.so.66
derelict-FI-3-32.20141022git7fc1714.fc23.i686 requires 
libphobos2-ldc-debug.so.66
derelict-FI-3-32.20141022git7fc1714.fc23.i686 requires 
libdruntime-ldc-debug.so.66
derelict-FT-3-32.20141022git7fc1714.fc23.i686 requires 
libphobos2-ldc-debug.so.66
derelict-FT-3-32.20141022git7fc1714.fc23.i686 requires 
libdruntime-ldc-debug.so.66
derelict-GL3-3-32.20141022git7fc1714.fc23.i686 requires 
libphobos2-ldc-debug.so.66
derelict-GL3-3-32.20141022git7fc1714.fc23.i686 requires 
libdruntime-ldc-debug.so.66
derelict-GLFW3-3-32.20141022git7fc1714.fc23.i686 requires 
libphobos2-ldc-debug.so.66
derelict-GLFW3-3-32.20141022git7fc1714.fc23.i686 requires 
libdruntime-ldc-debug.so.66
derelict-IL-3-32.20141022git7fc1714.fc23.i686 requires 
libphobos2-ldc-debug.so.66
derelict-IL-3-32.20141022git7fc1714.fc23.i686 requires 
libdruntime-ldc-debug.so.66
derelict-LUA-3-32.20141022git7fc1714.fc23.i686 requires 
libphobos2-ldc-debug.so.66
derelict-LUA-3-32.20141022git7fc1714.fc23.i686 requires 
libdruntime-ldc-debug.so.66
derelict-ODE-3-32.20141022git7fc1714.fc23.i686 requires 
libphobos2-ldc-debug.so.66
derelict-ODE-3-32.20141022git7fc1714.fc23.i686 requires 
libdruntime-ldc-debug.so.66
derelict-Ogg-3-32.20141022git7fc1714.fc23.i686 requires 
libphobos2-ldc-debug.so.66
derelict-Ogg-3-32.20141022git7fc1714.fc23.i686 requires 
libdruntime-ldc-debug.so.66
derelict-PHYSFS-3-32.20141022git7fc1714.fc23.i686 requires 
libphobos2-ldc-debug.so.66
derelict-PHYSFS-3-32.20141022git7fc1714.fc23.i686 requires 
libdruntime-ldc-debug.so.66
derelict-PQ-3-32.20141022git7fc1714.fc23.i686 requires 
libphobos2-ldc-debug.so.66
derelict-PQ-3-32.20141022git7f

F23 broke dependencies

[Vít Ondruch]

Will there be some effor to clean this up prior release?


Vít



Dne 23.9.2015 v 13:18 Fedora Branched Report napsal(a):
> Compose started at Wed Sep 23 07:15:03 UTC 2015
> Broken deps for armhfp
> --
> [apache-scout]
>   apache-scout-1.2.6-11.fc21.noarch requires mvn(org.apache.juddi:uddi-ws)
>   apache-scout-1.2.6-11.fc21.noarch requires 
> mvn(org.apache.juddi:juddi-client)
> [aws]
>   aws-tools-2015-2.fc23.armv7hl requires libaws_ssl.so
> [calligra]
>   calligra-kexi-map-form-widget-2.9.7-1.fc23.armv7hl requires 
> libmarblewidget.so.21
>   calligra-reports-map-element-2.9.7-1.fc23.armv7hl requires 
> libmarblewidget.so.21
>   calligra-semanticitems-2.9.7-1.fc23.armv7hl requires 
> libmarblewidget.so.21
> [dpm-contrib-admintools]
>   dpm-contrib-admintools-0.2.1-6.fc23.armv7hl requires 
> MySQL-python(armv7hl-32)
> [hawaii-shell]
>   hawaii-shell-0.3.0-3.fc22.armv7hl requires 
> libqtaccountsservice-qt5.so.0.1.2
> [hbase]
>   hbase-0.98.3-4.fc22.noarch requires mvn(com.sun.jersey:jersey-server)
>   hbase-0.98.3-4.fc22.noarch requires mvn(com.sun.jersey:jersey-json)
>   hbase-0.98.3-4.fc22.noarch requires mvn(com.sun.jersey:jersey-core)
>   hbase-tests-0.98.3-4.fc22.noarch requires 
> mvn(com.sun.jersey:jersey-server)
>   hbase-tests-0.98.3-4.fc22.noarch requires 
> mvn(com.sun.jersey:jersey-json)
>   hbase-tests-0.98.3-4.fc22.noarch requires 
> mvn(com.sun.jersey:jersey-core)
> [licq]
>   licq-1.8.2-9.fc23.armv7hl requires libboost_regex.so.1.57.0
> [mariadb-galera]
>   1:mariadb-galera-server-10.0.17-5.fc23.armv7hl requires galera >= 
> 0:25.3.3
> [moon-buggy]
>   moon-buggy-1.0.51-14.fc23.armv7hl requires libesd.so.0
> [netbeans-platform]
>   1:netbeans-platform-harness-7.0.1-11.fc22.armv7hl requires cobertura >= 
> 0:1.9.3
> [nodejs-grunt-contrib-copy]
>   nodejs-grunt-contrib-copy-0.8.0-2.fc23.noarch requires 
> npm(file-sync-cmp) < 0:0.2
>   nodejs-grunt-contrib-copy-0.8.0-2.fc23.noarch requires 
> npm(file-sync-cmp) >= 0:0.1.0
>   nodejs-grunt-contrib-copy-0.8.0-2.fc23.noarch requires npm(chalk) >= 
> 0:0.5.1
> [nodejs-grunt-saucelabs]
>   nodejs-grunt-saucelabs-8.6.1-2.fc23.noarch requires npm(sauce-tunnel) 
> >= 0:2.2.3
>   nodejs-grunt-saucelabs-8.6.1-2.fc23.noarch requires npm(requestretry) < 
> 0:1.3
>   nodejs-grunt-saucelabs-8.6.1-2.fc23.noarch requires npm(requestretry) 
> >= 0:1.2.2
>   nodejs-grunt-saucelabs-8.6.1-2.fc23.noarch requires npm(lodash) >= 
> 0:3.7.0
>   nodejs-grunt-saucelabs-8.6.1-2.fc23.noarch requires npm(colors) >= 
> 0:1.0.0
> [nodejs-proxy-agent]
>   nodejs-proxy-agent-1.1.0-1.fc22.noarch requires npm(socks-proxy-agent) 
> < 0:1
> [oat]
>   oat-appraiser-1.6.0-16.fc22.armv7hl requires tomcat-servlet-3.0-api
>   oat-client-1.6.0-16.fc22.armv7hl requires tomcat-servlet-3.0-api
> [oozie]
>   oozie-4.0.1-5.fc22.noarch requires mvn(org.apache.pig:pig)
>   oozie-4.0.1-5.fc22.noarch requires mvn(org.apache.hive:hive-serde)
>   oozie-4.0.1-5.fc22.noarch requires mvn(org.apache.hive:hive-metastore)
>   oozie-4.0.1-5.fc22.noarch requires mvn(org.apache.hive:hive-exec)
>   oozie-4.0.1-5.fc22.noarch requires mvn(org.apache.hive:hive-common)
>   oozie-4.0.1-5.fc22.noarch requires mvn(org.apache.hive:hive-cli)
>   oozie-4.0.1-5.fc22.noarch requires 
> mvn(org.apache.hive.hcatalog:webhcat-java-client)
>   oozie-4.0.1-5.fc22.noarch requires 
> mvn(org.apache.hive.hcatalog:hcatalog-server-extensions)
>   oozie-4.0.1-5.fc22.noarch requires 
> mvn(org.apache.hive.hcatalog:hcatalog-pig-adapter)
>   oozie-4.0.1-5.fc22.noarch requires 
> mvn(org.apache.hive.hcatalog:hcatalog-core)
> [openstack-heat-gbp]
>   openstack-heat-gbp-2014.2-2.fc23.noarch requires openstack-heat-engine 
> < 0:2014.3
> [openstack-neutron-gbp]
>   openstack-neutron-gbp-2014.2-2.fc23.noarch requires openstack-neutron < 
> 0:2014.3
> [openstack-swift]
>   openstack-swift-2.3.0-2.fc23.noarch requires python-pyeclib
> [perl-B-Hooks-OP-Check-EntersubForCV]
>   perl-B-Hooks-OP-Check-EntersubForCV-0.09-10.fc22.armv7hl requires 
> perl(:MODULE_COMPAT_5.20.0)
>   perl-B-Hooks-OP-Check-EntersubForCV-0.09-10.fc22.armv7hl requires 
> libperl.so.5.20
> [perl-Data-Alias]
>   perl-Data-Alias-1.18-4.fc22.armv7hl requires perl(:MODULE_COMPAT_5.20.0)
>   perl-Data-Alias-1.18-4.fc22.armv7hl requires libperl.so.5.20
> [perl-Data-Dump-Streamer]
>   perl-Data-Dump-Streamer-2.38-3.fc22.armv7hl requires 
> perl(:MODULE_COMPAT_5.20.0)
>   perl-Data-Dump-Streamer-2.38-3.fc22.armv7hl requires libperl.so.5.20
> [perl-Devel-BeginLift]
>   perl-Devel-BeginLift-0.001003-9.fc22.armv7hl requires 
> perl(:MODULE_COMPAT_5.20.0)
>   perl-Devel-BeginLift-0.001003-9.fc22.armv7hl requires libperl.so.5.20
> [perl-Devel-FindRef]
>   perl-Devel-FindRef-1.44-3.fc22.armv7hl requires 
> perl(:MODULE_COMPA

Re: Packaging Icinga 2 requiring SELinux assistance

[Alec Leamas]

On 23/09/15 13:16, Petr Lautrbach wrote:

On 09/22/2015 08:46 PM, Shawn Starr wrote:



However in long terms it's better to incorporate a package policy  to
the system policy. You can either file a bug against selinux-policy or
try to contribute yourself using this [2] howto.


That howto is somewhat sketchy if you (as me) are new to this. However,
 Miroslaw has made some promises to improve it [3]

Cheers!

--alec

[3] https://github.com/fedora-selinux/selinux-policy/issues/38




--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

F-23 Branched report: 20150923 changes

[Fedora Branched Report]

Compose started at Wed Sep 23 07:15:03 UTC 2015
Broken deps for armhfp
--
[apache-scout]
apache-scout-1.2.6-11.fc21.noarch requires mvn(org.apache.juddi:uddi-ws)
apache-scout-1.2.6-11.fc21.noarch requires 
mvn(org.apache.juddi:juddi-client)
[aws]
aws-tools-2015-2.fc23.armv7hl requires libaws_ssl.so
[calligra]
calligra-kexi-map-form-widget-2.9.7-1.fc23.armv7hl requires 
libmarblewidget.so.21
calligra-reports-map-element-2.9.7-1.fc23.armv7hl requires 
libmarblewidget.so.21
calligra-semanticitems-2.9.7-1.fc23.armv7hl requires 
libmarblewidget.so.21
[dpm-contrib-admintools]
dpm-contrib-admintools-0.2.1-6.fc23.armv7hl requires 
MySQL-python(armv7hl-32)
[hawaii-shell]
hawaii-shell-0.3.0-3.fc22.armv7hl requires 
libqtaccountsservice-qt5.so.0.1.2
[hbase]
hbase-0.98.3-4.fc22.noarch requires mvn(com.sun.jersey:jersey-server)
hbase-0.98.3-4.fc22.noarch requires mvn(com.sun.jersey:jersey-json)
hbase-0.98.3-4.fc22.noarch requires mvn(com.sun.jersey:jersey-core)
hbase-tests-0.98.3-4.fc22.noarch requires 
mvn(com.sun.jersey:jersey-server)
hbase-tests-0.98.3-4.fc22.noarch requires 
mvn(com.sun.jersey:jersey-json)
hbase-tests-0.98.3-4.fc22.noarch requires 
mvn(com.sun.jersey:jersey-core)
[licq]
licq-1.8.2-9.fc23.armv7hl requires libboost_regex.so.1.57.0
[mariadb-galera]
1:mariadb-galera-server-10.0.17-5.fc23.armv7hl requires galera >= 
0:25.3.3
[moon-buggy]
moon-buggy-1.0.51-14.fc23.armv7hl requires libesd.so.0
[netbeans-platform]
1:netbeans-platform-harness-7.0.1-11.fc22.armv7hl requires cobertura >= 
0:1.9.3
[nodejs-grunt-contrib-copy]
nodejs-grunt-contrib-copy-0.8.0-2.fc23.noarch requires 
npm(file-sync-cmp) < 0:0.2
nodejs-grunt-contrib-copy-0.8.0-2.fc23.noarch requires 
npm(file-sync-cmp) >= 0:0.1.0
nodejs-grunt-contrib-copy-0.8.0-2.fc23.noarch requires npm(chalk) >= 
0:0.5.1
[nodejs-grunt-saucelabs]
nodejs-grunt-saucelabs-8.6.1-2.fc23.noarch requires npm(sauce-tunnel) 
>= 0:2.2.3
nodejs-grunt-saucelabs-8.6.1-2.fc23.noarch requires npm(requestretry) < 
0:1.3
nodejs-grunt-saucelabs-8.6.1-2.fc23.noarch requires npm(requestretry) 
>= 0:1.2.2
nodejs-grunt-saucelabs-8.6.1-2.fc23.noarch requires npm(lodash) >= 
0:3.7.0
nodejs-grunt-saucelabs-8.6.1-2.fc23.noarch requires npm(colors) >= 
0:1.0.0
[nodejs-proxy-agent]
nodejs-proxy-agent-1.1.0-1.fc22.noarch requires npm(socks-proxy-agent) 
< 0:1
[oat]
oat-appraiser-1.6.0-16.fc22.armv7hl requires tomcat-servlet-3.0-api
oat-client-1.6.0-16.fc22.armv7hl requires tomcat-servlet-3.0-api
[oozie]
oozie-4.0.1-5.fc22.noarch requires mvn(org.apache.pig:pig)
oozie-4.0.1-5.fc22.noarch requires mvn(org.apache.hive:hive-serde)
oozie-4.0.1-5.fc22.noarch requires mvn(org.apache.hive:hive-metastore)
oozie-4.0.1-5.fc22.noarch requires mvn(org.apache.hive:hive-exec)
oozie-4.0.1-5.fc22.noarch requires mvn(org.apache.hive:hive-common)
oozie-4.0.1-5.fc22.noarch requires mvn(org.apache.hive:hive-cli)
oozie-4.0.1-5.fc22.noarch requires 
mvn(org.apache.hive.hcatalog:webhcat-java-client)
oozie-4.0.1-5.fc22.noarch requires 
mvn(org.apache.hive.hcatalog:hcatalog-server-extensions)
oozie-4.0.1-5.fc22.noarch requires 
mvn(org.apache.hive.hcatalog:hcatalog-pig-adapter)
oozie-4.0.1-5.fc22.noarch requires 
mvn(org.apache.hive.hcatalog:hcatalog-core)
[openstack-heat-gbp]
openstack-heat-gbp-2014.2-2.fc23.noarch requires openstack-heat-engine 
< 0:2014.3
[openstack-neutron-gbp]
openstack-neutron-gbp-2014.2-2.fc23.noarch requires openstack-neutron < 
0:2014.3
[openstack-swift]
openstack-swift-2.3.0-2.fc23.noarch requires python-pyeclib
[perl-B-Hooks-OP-Check-EntersubForCV]
perl-B-Hooks-OP-Check-EntersubForCV-0.09-10.fc22.armv7hl requires 
perl(:MODULE_COMPAT_5.20.0)
perl-B-Hooks-OP-Check-EntersubForCV-0.09-10.fc22.armv7hl requires 
libperl.so.5.20
[perl-Data-Alias]
perl-Data-Alias-1.18-4.fc22.armv7hl requires perl(:MODULE_COMPAT_5.20.0)
perl-Data-Alias-1.18-4.fc22.armv7hl requires libperl.so.5.20
[perl-Data-Dump-Streamer]
perl-Data-Dump-Streamer-2.38-3.fc22.armv7hl requires 
perl(:MODULE_COMPAT_5.20.0)
perl-Data-Dump-Streamer-2.38-3.fc22.armv7hl requires libperl.so.5.20
[perl-Devel-BeginLift]
perl-Devel-BeginLift-0.001003-9.fc22.armv7hl requires 
perl(:MODULE_COMPAT_5.20.0)
perl-Devel-BeginLift-0.001003-9.fc22.armv7hl requires libperl.so.5.20
[perl-Devel-FindRef]
perl-Devel-FindRef-1.44-3.fc22.armv7hl requires 
perl(:MODULE_COMPAT_5.20.0)
perl-Devel-FindRef-1.44-3.fc22.armv7hl requires libperl.so.5.20
[perl-Method-Signatures]
perl-Method-Signatures-20141021-1.fc22.noarch requires 
perl(:MODULE_COMPAT_5.20.1)
[perl-POE-API-Peek]
1:perl-PO

Re: package naming question: IT++

[Antonio Trande]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On 09/23/2015 10:24 AM, Antonio Trande wrote:
> On 09/23/2015 10:03 AM, Marco Driusso wrote:
>> OK, many thanks for the replies. Go for plain 'itpp'.
> 
>> For anyone interested in reviewing the package, this is the 
>> bugzilla ticket, I need a sponsor! -> 
>> https://bugzilla.redhat.com/show_bug.cgi?id=1264686
> 
>> Cheers,
> 
>> Marco
> 
> Please, read carefully this guide-lines: 
> http://fedoraproject.org/wiki/How_to_get_sponsored_into_the_packager_gro
>
> 
up
> 
> 

Correction:

These guide-lines:
http://fedoraproject.org/wiki/How_to_get_sponsored_into_the_packager_group


- -- 
Antonio Trande

mailto: sagitter 'at' fedoraproject 'dot' org
http://fedoraos.wordpress.com/
https://fedoraproject.org/wiki/User:Sagitter
GPG Key: 0x565E653C
Check on https://keys.fedoraproject.org/
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQEcBAEBCAAGBQJWAmLiAAoJEF5tK7VWXmU8+6sIAJ5Y613NH4emmLOU8i4bapZb
PbS9guKYMlWQ5/dM0C0kkkl3BCMwB/2muPGPfeQ7BwRhTwCuSYSG41AwNnER3Ues
7KxyQ5AQYHbxaX49Xkyx7MzGSSYCYMRobkQATaHI0TtdTBgf/P2u4FFX5giN6ISG
NPqCzIfKIlBfyOO2lsf1q8NWAYZnwPRsuo6vul+i+nGDkVZ0pSDg9/ML3u3SnLLj
EJJ8ZYnSUg6oqc5fDCjbHt8oZwS3UNhqunlupFwFjaeqXE6AB1V78TbgbHngsvtp
jsIq6+Y5QVPlC41tHrfyxq6hCRlivTOM15+cU80tNBj5xDeTDHp2xqG+E4ogNwY=
=o0kT
-END PGP SIGNATURE-
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: package naming question: IT++

[Antonio Trande]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On 09/23/2015 10:03 AM, Marco Driusso wrote:
> OK, many thanks for the replies. Go for plain 'itpp'.
> 
> For anyone interested in reviewing the package, this is the
> bugzilla ticket, I need a sponsor! -> 
> https://bugzilla.redhat.com/show_bug.cgi?id=1264686
> 
> Cheers,
> 
> Marco

Please, read carefully this guide-lines:
http://fedoraproject.org/wiki/How_to_get_sponsored_into_the_packager_gro
up

- -- 
Antonio Trande

mailto: sagitter 'at' fedoraproject 'dot' org
http://fedoraos.wordpress.com/
https://fedoraproject.org/wiki/User:Sagitter
GPG Key: 0x565E653C
Check on https://keys.fedoraproject.org/
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQEcBAEBCAAGBQJWAmGqAAoJEF5tK7VWXmU8K14H/jyJ6EZbbrsfAGcCv/nK1Sgr
5Viva5iOI+Vt3XZpQu9IWM2WOZwUEMR4gKZeY6oJP2bTKRTuzmsNfNssP5D28LhM
tcgpiHzq9QrfIdbsv4gvl0JZ4btlNCSbPW/vkGuICqe5JLr3WRuoUlRNX4L6okh/
NWSrEG5l06m5HbgK7WwMnb5yt4sm21kzYZP6n1K0144VCDrgLNTo54V9B5HXLKwz
cBdzTOAHmEjUGtn91EfS62DsjKJ+DoFecjXkBRpWzYxksYSPn6o5534hxhr1xpyz
9G85YhWOq6Nw9Ndusv3h+O+YNwqsrZb3uv7Ct7BHx5n1kwSD37z9IGzoLrO344E=
=ijBO
-END PGP SIGNATURE-
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: Fedora 23 cloud image (and, for that matter, minimal anything) bloat

[Robert Kuska]

- Original Message -
> From: "Matthew Miller" 
> To: "Development discussions related to Fedora" 
> 
> Sent: Tuesday, September 22, 2015 3:49:19 PM
> Subject: Re: Fedora 23 cloud image (and, for that matter, minimal anything)   
> bloat
> 
> On Tue, Sep 22, 2015 at 05:07:58AM -0400, Matej Stuchlik wrote:
> > When it comes to python3, one way to shave off ~9MiB from
> > python3-libs, and possibly quite a bit more overall, would be to not
> > install both optimized and unoptimized bytecode, as we do now, but
> > just the unoptimized one (the performance hit should be very small).
> > 
> > I'll look into if that could be done.
> > 
> > We could also move few things from -libs to -devel, possibly.
> 
> Cool. Let's put you on the future list for
> https://fedorahosted.org/fedora-badges/ticket/378 :)

I've tried to move idlelib and lib2to3 to -tools subpackage
but unfortunately I had to revert this change as distutils
uses lib2to3 module and idlelib is used by -tkinter meaning
that -tkinter would have to depend on -tools subpackage but
-tools already requires -tkinter so it would lead to cyclic dep.

> 
> 
> 
> --
> Matthew Miller
> 
> Fedora Project Leader
> --
> devel mailing list
> devel@lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/devel
> Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct


--
Robert Kuska
{rkuska}
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: package naming question: IT++

[Marco Driusso]

OK, many thanks for the replies. Go for plain 'itpp'.

For anyone interested in reviewing the package, this is the bugzilla 
ticket, I need a sponsor! -> 
https://bugzilla.redhat.com/show_bug.cgi?id=1264686


Cheers,

Marco


On 22/09/15 13:33, Neal Gompa wrote:

On Tue, Sep 22, 2015 at 6:44 AM, Jonathan Wakely mailto:jwak...@redhat.com>>wrote:

On 22/09/15 10:40 +0200, Marco Driusso wrote:

So I think we have two options:
1) use 'itpp' as the name of the package, which corresponds to
the include dir name, but not to the lib file name (libitpp.so);
in this


All libraries start with "lib" but that doesn't mean the package that
provides a library should do.

Look at the output of rpm -qf /usr/lib64/lib* and you'll see most of
them are not called "libxxx" just because they install a file called
"libxxx.so".  e.g. gtk3 installs libgtk-3

The project is called IT++, it installs headers in  and
installs libitpp.so, so itpp seems the most natural name.



If this wasn't a library that's linked at compile time, I would suggest
also including a "Provides: libitpp" line in there too, but I think
that's not necessary, since packages that would depend on it would use
the library dependency "libitpp.so.8" instead, which there should be an
automatic Provides generated in the itpp package.

Basically, RPM does nice things for you, so you don't have to care (as
much) about this kind of stuff.


--
真実はいつも一つ！/ Always, there's only one truth!



--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: Trying to contact package maintainer for boinc-client

[Laurence]

On 22/09/15 18:39, Mattia Verga wrote:

Il 22/09/2015 16:12, Laurence ha scritto:

Thanks I have tried to contact him too but no response so far.

On 21.09.2015 12:23, Germano Massullo wrote:

The actual BOINC working mantainer is Mattia Verga




I'm no more a maintainer of boinc-client. And I didn't received any 
email from you... I assume you want someone to approve commit access, 
but I've resigned my commits and I can't.


You should try to ask some provenpackager.



The package administrators are Miloš Jakubíček and Marek Mahut. Neither 
are responsive.


https://admin.fedoraproject.org/pkgdb/package/boinc-client/
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct