Re: making Ctrl-Alt-Bksp work

[Peter Hutterer]

On Wed, May 07, 2014 at 02:38:59PM -0400, Felix Miata wrote:
> On 2014-05-07 19:03 (GMT+0100) Sérgio Basto composed:
> 
> >yes Ctrl-Alt-Bksp works and restart X , as Reindl Harald notice, I also have
> 
> >Option "XkbOptions" "terminate:ctrl_alt_bksp,
> 
> >cat /etc/X11/xorg.conf.d/00-keyboard.conf
> 
> > Option  "XkbModel"  "pc105"
> > Option  "XkbLayout" "pt"
> > Option  "XkbOptions""terminate:ctrl_alt_bksp,"
> 
> >my video card is :
> >[52.601] (II) intel(0): [DRI2]   DRI driver: i965
> 
> >"DontZoom" don't works , you are right
> 
> Your (locale pt) and Reindl's (locale de) answers beg two questions:
> 
> 1-why do 00-keyboard.conf for pt and de contain
> terminate:ctrl_alt_bksp, but for locale us it is absent?
> 
> 2-what creates 00-keyboard.conf in the first place, since it doesn't
> get automatically recreated even by rebooting if deleted?

systemd-localed. This file is written when you change the locale, either
during install or later with localectl. It doesn't automatically get
restored when you delete it.

http://fedoraproject.org/wiki/Input_device_configuration
lists the magic command as:
   localectl set-x11-keymap "us" "" "" "terminate:ctrl_alt_bksp"

which communicates the new keymap to systemd-localed, which then writes out
the file.

but having just tested this on F20, just running "localectl set-keymap us"
also writes out the right configuration, including the terminate option. The
above is needed for custom x11 keymaps, but shouldn't be needed for normal
setup.

> re 2: Maybe your two installations have 00-keyboard.conf carried
> over from before xorg-x11-drv-keyboard was superceded by
> xorg-x11-drv-evdev, which on (re)installation does not create it if
> it does not exist?

neither the keyboard nor the evdev driver have anything to do with it. the
retirement of the keyboard driver should have no effect on anything newer
than, say, Fedora 12.

Zapping in the server works as a two-stage process. A key combination is
interpreted by a XKB as a Terminate_Server action. The server then
interprets that and terminates. With DontZap you only control the
second part, i.e. whether the server terminates when the action is triggered.
If you don't have the XKB setting, you can't trigger it in the first place.
And DontZap is only useful if you want to _prohibit_ zapping completely. It
just makes Terminate_Server do nothing.

For your use-case, forget about DontZap, it has no effect. I'm the
maintainer for these parts of the server, so regardless of how many
configurations you find that tell you to enable it, please trust my word
here. You need to get the terminate XKB option into your keymap, that's all
that matters.

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

Schedule for Thursday's FPC Meeting (2014-05-08 16:00 UTC)

[James Antill]

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

 Local time information (via. rktime):

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

 Links to all tickets below can be found at: 

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

= Followups =

(approval and retirement sections already passed, /opt exception passed)
#topic #339 software collections in Fedora
.fpc 339
https://fedorahosted.org/fpc/ticket/339

#topic #382 Go Packaging Guidelines Draft
.fpc 382
https://fedorahosted.org/fpc/ticket/382

#topic #400 Exception for bundled library FoX in exciting
.fpc 400
https://fedorahosted.org/fpc/ticket/400

(remaining votes needed)
#topic #411 proposal: migrate license files to %license instead of %
doc
.fpc 411
https://fedorahosted.org/fpc/ticket/411

(remaining votes needed)
#topic #413 Bundling exception request for nodejs-shelljs
.fpc 413
https://fedorahosted.org/fpc/ticket/413


#topic #414 Please consider requiring AppData for all desktop
applications
.fpc 414
https://fedorahosted.org/fpc/ticket/414

= New business =

#topic #417 sha2 library bundling in clementine
.fpc 417
https://fedorahosted.org/fpc/ticket/417

#topic #418 Bundling exception for reaver-wps
.fpc 418
https://fedorahosted.org/fpc/ticket/418

#topic #419 ruby193 in SCL
.fpc 419
https://fedorahosted.org/fpc/ticket/419

#topic #421 Update environment modules guidelines
.fpc 421
https://fedorahosted.org/fpc/ticket/421

#topic #422 move an existing package to a different upstream fork
.fpc 422
https://fedorahosted.org/fpc/ticket/422

#topic #423 Bundling exception request (copylib) for TommyDS library
used in SnapRAID
.fpc 423
https://fedorahosted.org/fpc/ticket/423

#topic #424 Bundling exception request for nodejs-weak-map
.fpc 424
https://fedorahosted.org/fpc/ticket/424

#topic #425 systemd or systemd-units should not be required if a spec
file does a %systemd_post command
.fpc 425
https://fedorahosted.org/fpc/ticket/425

#topic #426 Need policy and macros for binfmt.d file handling
.fpc 426
https://fedorahosted.org/fpc/ticket/426

#topic #427 Bundling exception requests for new julia package
.fpc 427
https://fedorahosted.org/fpc/ticket/427

= 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/12


 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: making Ctrl-Alt-Bksp work

[Fidel Leon]

On Wednesday 07 May 2014 16:01:53 Felix Miata wrote:
> On 2014-05-07 20:49 (GMT+0200) Fidel Leon composed:
> >> re 2: Maybe your two installations have 00-keyboard.conf carried over
> >> from
> >> before xorg-x11-drv-keyboard was superceded by xorg-x11-drv-evdev, which
> >> on
> >> (re)installation does not create it if it does not exist?
> > 
> > My case was a clean install.
> 
> Every install had to be a clean install by going far enough back in time.

Yes, of course, my point was saying "I haven't upgraded from past releases", no 
old files which could carry such setup.

Anyway:

# ll -dt /boot/grub2/grub.cfg /boot/lost+found/ 
/boot/initramfs-3.14.2-200.fc20.i686+PAE.img 
/etc/X11/xorg.conf.d/00-keyboard.conf 
-rw---. 1 root root 4799 May  4 00:05 /boot/grub2/grub.cfg
-rw---. 1 root root 19034041 May  4 00:04 
/boot/initramfs-3.14.2-200.fc20.i686+PAE.img
-rw-r--r--. 1 root root  324 May  4 00:02 
/etc/X11/xorg.conf.d/00-keyboard.conf
drwx--. 2 root root12288 May  3 20:38 /boot/lost+found/

That was four days ago - exactly when I (re)installed F20. I did a network 
installation, so most installed packages were already in the most current 
versions. Hence, in some moment after package installation but before the 
dracut and grub installation steps, was my keyboard file created (.conf file 
which follows what anaconda wrote in the kickstart files).

That's consistent with what I see on another system I manage, which used a Xfce 
live CD to be installed.
-- 
Fidel Leon
fidell...@mykolab.com
GSM: +34 639 000 390
GPG: AD74FB97
"Developers have the attention spans of slightly moronic woodland creatures."
-- 
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: BerkeleyDB 6 symbol versioning and associated problems

[Chris Adams]

Once upon a time, Adam Jackson  said:
> I don't know if I have a good suggestion here, none of the alternatives
> sound appealing.

Is there a compelling reason to upgrade to BDB-6 (other than 6 > 5)?
The license change really seems to be a PITA, since it is incompatible
with the licenses of software already using BDB-5.
-- 
Chris Adams 
-- 
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: making Ctrl-Alt-Bksp work

[Felix Miata]

On 2014-05-07 20:49 (GMT+0200) Fidel Leon composed:


re 2: Maybe your two installations have 00-keyboard.conf carried over from
before xorg-x11-drv-keyboard was superceded by xorg-x11-drv-evdev, which on
(re)installation does not create it if it does not exist?



My case was a clean install.


Every install had to be a clean install by going far enough back in time. The 
question remains when you did a clean install, as retirement of the keyboard driver 
was recent, and may have occurred after your clean installation.

--
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/
--
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: BerkeleyDB 6 symbol versioning and associated problems

[Adam Jackson]

On Wed, 2014-05-07 at 15:19 +0200, Jan Staněk wrote:
> One of the planned parts of the F21 System Wide Change: BerkeleyDB 6 [1]
> is the introduction of downstream symbol versioning of both versions of
> the libraries (libdb with v6 and libdb5 with v5). This part is planned
> in order to not introduce bugs similar to [2]. However, if we introduce
> downstream versioning (as upstream is generally unresponsive), then we
> face the problem similar to [3].
> 
> In short, if we introduce the downstream versioning, we will ship
> library with ABI incompatible with upstream ABI. If we won't,
> applications with modules/plugins (ie. Apache with mod_perl) that each
> use different version of the library may break due to double symbols
> (one from the v5 and other from v6, and ld would not know which symbol
> is which).
> 
> I'd like to ask for suggestions on how to resolve this problem.

It's unfortunate that BerkeleyDB doesn't use a system like pkg-config,
where the name of the library being linked is disconnected from the
module being requested; if it were, we could build a libfeddb-6.so with
symbol versioning and a libdb-6.so without, link our OS with the former
by simply switching what the pkgconfig file points to, and maintain a
semblance of binary compatibility with the outside world.

It's also unfortunate that symbol versioning falls over like this.  The
relevant section from Uli's writeup reads:

---
[... I]f the object with the references uses symbol versions but the
object with the definitions has none.  In this case a matching symbol is
accepted unless the object's name matches the one in the Elfxx_Verneed
entry.  In the latter case this is a fatal error.  In fact, this should
never have happened in the first place since it would mean the list of
required symbols was not correct and the steps required in the last
section therefore haven't detected a too old version of an object file.
---

This sort of breaks the upgrade path from unversioned to versioned
symbols within a library, if I understand it correctly; adding versions
effectively requires bumping the object's soname, since otherwise
linking against libfoo.so.1 just after versions were added would prevent
that binary from running against an unversioned-but-otherwise-identical
libfoo.so.1.  (Unless the library still exports unversioned names for
every symbol, I suppose.)

Which is doubly unfortunate, since it means ld can't just decide to
enable --default-symver at some point, as every binary linked afterwards
will be incompatible with prior runtimes.

I don't know if I have a good suggestion here, none of the alternatives
sound appealing.

- ajax

-- 
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: making Ctrl-Alt-Bksp work

[Reindl Harald]

Am 07.05.2014 20:38, schrieb Felix Miata:
> On 2014-05-07 19:03 (GMT+0100) Sérgio Basto composed:
> 
>> yes Ctrl-Alt-Bksp works and restart X , as Reindl Harald notice, I also have
> 
>> Option "XkbOptions" "terminate:ctrl_alt_bksp,
> 
>> cat /etc/X11/xorg.conf.d/00-keyboard.conf
> 
>>  Option  "XkbModel"  "pc105"
>>  Option  "XkbLayout" "pt"
>>  Option  "XkbOptions""terminate:ctrl_alt_bksp,"
> 
>> my video card is :
>> [52.601] (II) intel(0): [DRI2]   DRI driver: i965
> 
>> "DontZoom" don't works , you are right
> 
> Your (locale pt) and Reindl's (locale de) answers beg two questions:
> 
> 1-why do 00-keyboard.conf for pt and de contain terminate:ctrl_alt_bksp, but 
> for locale us it is absent?

because nobody did write it there?

> 2-what creates 00-keyboard.conf in the first place, since it doesn't get 
> automatically 
> recreated even by rebooting if deleted?

not what - who - a smart admin in my case which just used google years ago:
https://bbs.archlinux.org/viewtopic.php?pid=602885




signature.asc
Description: OpenPGP digital 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: BerkeleyDB 6 symbol versioning and associated problems

[Miloslav Trmač]

Hello,
2014-05-07 15:19 GMT+02:00 Jan Staněk :

> In short, if we introduce the downstream versioning, we will ship
> library with ABI incompatible with upstream ABI. If we won't,
> applications with modules/plugins (ie. Apache with mod_perl) that each
> use different version of the library may break due to double symbols
> (one from the v5 and other from v6, and ld would not know which symbol
> is which).
>
> I'd like to ask for suggestions on how to resolve this problem.
>
 

> As I stated above, I welcome any suggestions. I would also like to hear
> from someone responsible for the distro architecture which of the
> aforementioned issues is more painful for us, so we know which path to
> take if no complete solution is found.
>

In my personal opinion, keeping Fedora working at all is more important
than cross-distribution compatibility (which is desirable but not as
critical *to Fedora)*, so the former would be preferable.

Separately, please note today's FESCo request in
https://fedorahosted.org/fesco/ticket/1291#comment:4 .
Mirek
-- 
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: making Ctrl-Alt-Bksp work

[Fidel Leon]

Just adding my two cents as I don't use the us locale.

On Wednesday 07 May 2014 14:38:59 Felix Miata wrote:
> On 2014-05-07 19:03 (GMT+0100) Sérgio Basto composed:
> > yes Ctrl-Alt-Bksp works and restart X , as Reindl Harald notice, I also
> > have
> > 
> 1-why do 00-keyboard.conf for pt and de contain terminate:ctrl_alt_bksp, but
> for locale us it is absent?

The es locale doesn't have a terminate subsection...:

# Read and parsed by systemd-localed. It's probably wise not to edit this file
# manually too freely.
Section "InputClass"
Identifier "system-keyboard"
MatchIsKeyboard "on"
Option "XkbLayout" "es,si,rs"
Option "XkbVariant" ",,"
Option "XkbOptions" "grp:lalt_lshift_toggle"
EndSection

> 2-what creates 00-keyboard.conf in the first place, since it doesn't get
> automatically recreated even by rebooting if deleted?

I installed my Fedora from a network install image, and the three locales I 
have were the languages I itold anaconda I wanted support for. Hence, at least 
for me, it was the system installation which created it.

> re 2: Maybe your two installations have 00-keyboard.conf carried over from
> before xorg-x11-drv-keyboard was superceded by xorg-x11-drv-evdev, which on
> (re)installation does not create it if it does not exist?

My case was a clean install.

-- 
Fidel Leon
fidell...@mykolab.com
GSM: +34 639 000 390
GPG: AD74FB97
"Developers have the attention spans of slightly moronic woodland creatures."
-- 
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 (2014-05-07)

[Miloslav Trmač]

===
#fedora-meeting: FESCO (2014-05-07)
===


Meeting started by mitr at 17:00:19 UTC. The full logs are available at
http://meetbot.fedoraproject.org/fedora-meeting/2014-05-07/fesco.2014-05-07-17.00.log.html
.



Meeting summary
---
* init process  (mitr, 17:00:25)

* #1221 Product working group activity reports  (mitr, 17:03:49)
  * see activity reports starting at
https://fedorahosted.org/fesco/ticket/1221#comment:51  (mitr,
17:04:28)

* #1291 F21 System Wide Change: BerkeleyDB 6 -
  https://fedoraproject.org/wiki/Changes/BerkeleyDB_6  (mitr, 17:06:03)
  * AGREED: Please contact upstream now about symbol versioning, and
report back by next week; if upstream doesn't agree, have a proposed
approach (+7)  (mitr, 17:18:39)

* #1297 F21 System Wide Change: Workstation: Enable Software Collections
  -

https://fedoraproject.org/wiki/Changes/Workstation_Enable_Software_Collections
  (mitr, 17:19:04)
  * LINK: https://fedorahosted.org/fesco/ticket/1297#comment:3 has some
specific questions  (mitr, 17:21:29)
  * AGREED: merge workstation SCL change into
https://fedoraproject.org/wiki/Changes/SCL, and add a note about
workstation there (+6)  (mitr, 17:34:15)

* #1303 Add exception for enabling nss-pam-ldapd's nslcd to start by
  default in obsoleting-install cases  (mitr, 17:34:38)
  * AGREED: Exception for enabling nss-pam-ldapd's nslcd approved (+7)
(mitr, 17:36:58)

* #1304 replacing reSIProcate in Fedora 20  (mitr, 17:37:04)
  * AGREED: reSIProcate update policy exception approved (+7)  (mitr,
17:40:03)
  * Please let the packages stay in updates-testing for an extended
period, and consider turning off autokarma  (mitr, 17:40:26)

* #1305 F21 System Wide Change: Application Installer Continued -
  https://fedoraproject.org/wiki/Changes/AppInstallerContinued  (mitr,
  17:40:34)
  * AGREED: Application Installer Continued was approved (+6)  (mitr,
17:49:39)

* #1306 F21 System Wide Change: Wayland -
  https://fedoraproject.org/wiki/Changes/Wayland  (mitr, 17:50:20)
  * AGREED: Wayland change approved (+7)  (mitr, 17:53:52)

* #1307 F22 System Wide Change: Default Local DNS Resolver -
  https://fedoraproject.org/wiki/Changes/Default_Local_DNS_Resolver
  (mitr, 17:52:58)
  * AGREED: FESCo doesn't have significant objections to the idea as
such, or its use on physical machines and VMs (+7)  (mitr, 18:00:39)
  * AGREED: Deferring appproval fo the change for a plan that explicitly
describes what, if anything, will be done for containers, Docker in
particular (+7)  (mitr, 18:00:51)

* #1302 Fedora Core OS Product  (mitr, 18:01:03)
  * Will close the ticket based on JĂłhann's request  (mitr, 18:04:20)

* Next week's chair  (mitr, 18:04:27)
  * sgallagh will chair next week's meeting  (mitr, 18:05:17)

* Open Floor  (mitr, 18:05:24)

* #1250 F21 Self Contained Changes  (mitr, 18:06:03)
  * AGREED: Self-Contained Changes: Remote Journal Logging, Cache
Logical Volumes, MariaDB 10.0, Shogun approved (+6)  (mitr,
18:11:26)
  * Docker Cloud skipped per mattdm's request  (mitr, 18:10:45)

* Open Floor  (mitr, 18:10:58)

Meeting ended at 18:15:37 UTC.




Action Items






Action Items, by person
---
* **UNASSIGNED**
  * (none)




People Present (lines said)
---
* mitr (99)
* dgilmore (32)
* abadger1999 (28)
* mattdm (24)
* t8m (23)
* pjones (18)
* jwb (18)
* notting (16)
* mclasen (14)
* zodbot (13)
* sgallagh (11)
* Viking-Ice (8)
* jzb (4)
* jsmith (2)
* nirik (0)
* mmaslano (0)




Generated by `MeetBot`_ 0.1.4

.. _`MeetBot`: http://wiki.debian.org/MeetBot
-- 
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: DISTRIBUTION tag seems wrong

[Steve Grubb]

On Wed, 7 May 2014 11:53:30 -0500
Dennis Gilmore  wrote:
> > Not sure if this is bz worthy or just something to mention on a mail
> > list. I was doing some experimenting on creating SWID tags out of
> > the rpm database and noticed some inconsistencies. For example:
> > 
> > # rpm -q --queryformat '%{DISTRIBUTION}\n' bash
> > Fedora Project
> > # rpm -q --queryformat '%{DISTRIBUTION}\n' xbmc
> > Fedora 20
> > 
> > Seems that rpmfusion has it right and the main Fedora build system
> > is misconfigured.
>
> rpmfusion has it wrong, they should be using rpmfusion.  koji sets the
> distribution tag for everything that is built in the buildsys to be
> the same. for fedora that is "Fedora Project" as that is who is
> building and distributing the rpms

OK, maybe I am approaching this from the wrong direction. What I need
to identify in the rpm database is the following:

1) product title - this would be the rpm package name
2) product version - again version from rpm
3) software creator - was thinking this was URL
4) software licensor - was thinking this was VENDOR
5) component_of - was thinking that this was DISTRIBUTION

It doesn't seem right to have 4 & 5 say Fedora Project. In a sense its
true. But I was wanting the component_of to say Fedora 20 or 19 so that
the tag contents better identify an OS component to match reality. If
we have the same version of a package on F19 & F20, the way it is now,
all identification will be the same but the file hashes will be
different because of timestamps, compiler options, different
definitions of macros & inline functions, etc. Hope this clarifies
things a bit.

Thanks,
-Steve
-- 
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: making Ctrl-Alt-Bksp work

[Felix Miata]

On 2014-05-07 19:03 (GMT+0100) Sérgio Basto composed:


yes Ctrl-Alt-Bksp works and restart X , as Reindl Harald notice, I also have



Option "XkbOptions" "terminate:ctrl_alt_bksp,



cat /etc/X11/xorg.conf.d/00-keyboard.conf



 Option  "XkbModel"  "pc105"
 Option  "XkbLayout" "pt"
 Option  "XkbOptions""terminate:ctrl_alt_bksp,"



my video card is :
[52.601] (II) intel(0): [DRI2]   DRI driver: i965



"DontZoom" don't works , you are right


Your (locale pt) and Reindl's (locale de) answers beg two questions:

1-why do 00-keyboard.conf for pt and de contain terminate:ctrl_alt_bksp, but for 
locale us it is absent?


2-what creates 00-keyboard.conf in the first place, since it doesn't get 
automatically recreated even by rebooting if deleted?


re 2: Maybe your two installations have 00-keyboard.conf carried over from before 
xorg-x11-drv-keyboard was superceded by xorg-x11-drv-evdev, which on (re)installation 
does not create it if it does not exist?

--
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/
--
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: making Ctrl-Alt-Bksp work

[Sérgio Basto]

On Qua, 2014-05-07 at 19:45 +0200, Reindl Harald wrote: 
> 
> Am 07.05.2014 19:41, schrieb Felix Miata:
> > On 2014-05-07 18:22 (GMT+0100) Sérgio Basto composed:
> > 
> >> answering to the subject
> > 
> >> my /etc/X11/xorg.conf is:
> > 
> >> Section "ServerLayout"
> >>  Identifier "single head configuration"
> >>  Option  "DontZap" "false"
> >>  Option  "DontZoom" "false"
> >> EndSection
> > 
> > In what way does that answer anything? Unless you are using a UMS video 
> > driver, I doubt DontZoom has any effect on
> > anything. Does Ctrl-Alt-Bksp do anything on your system? If so, what locale 
> > do you use, and which video driver?

yes Ctrl-Alt-Bksp works and restart X , as Reindl Harald notice, I also
have  

Option "XkbOptions" "terminate:ctrl_alt_bksp,

cat /etc/X11/xorg.conf.d/00-keyboard.conf 

Section "InputClass"
Identifier  "system-setup-keyboard"
MatchIsKeyboard "on"
Option  "XkbModel"  "pc105"
Option  "XkbLayout" "pt"
Option  "XkbOptions""terminate:ctrl_alt_bksp,"
EndSection

my video card is :
[52.601] (II) intel(0): [DRI2]   DRI driver: i965


"DontZoom" don't works , you are right 


> that bring sme back to the login-creen on any pyhsical machine
> with Ctrl-Alt-Bksp over years
> 
> [root@srv-rhsoft:/etc/X11/xorg.conf.d]$ cat 00-keyboard.conf
> Section "InputClass"
>  Identifier  "system-setup-keyboard"
>  MatchIsKeyboard "on"
>  Option "XkbModel"   "pc105"
>  Option "XkbLayout"  "de"
>  Option "XkbVariant" "nodeadkeys"
>  Option "XkbOptions" "terminate:ctrl_alt_bksp,"
> EndSection
> 

-- 
Sérgio M. B.

-- 
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: making Ctrl-Alt-Bksp work

[Reindl Harald]

Am 07.05.2014 19:41, schrieb Felix Miata:
> On 2014-05-07 18:22 (GMT+0100) Sérgio Basto composed:
> 
>> answering to the subject
> 
>> my /etc/X11/xorg.conf is:
> 
>> Section "ServerLayout"
>>  Identifier "single head configuration"
>>  Option  "DontZap" "false"
>>  Option  "DontZoom" "false"
>> EndSection
> 
> In what way does that answer anything? Unless you are using a UMS video 
> driver, I doubt DontZoom has any effect on
> anything. Does Ctrl-Alt-Bksp do anything on your system? If so, what locale 
> do you use, and which video driver?

that bring sme back to the login-creen on any pyhsical machine
with Ctrl-Alt-Bksp over years

[root@srv-rhsoft:/etc/X11/xorg.conf.d]$ cat 00-keyboard.conf
Section "InputClass"
 Identifier  "system-setup-keyboard"
 MatchIsKeyboard "on"
 Option "XkbModel"   "pc105"
 Option "XkbLayout"  "de"
 Option "XkbVariant" "nodeadkeys"
 Option "XkbOptions" "terminate:ctrl_alt_bksp,"
EndSection



signature.asc
Description: OpenPGP digital 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: making Ctrl-Alt-Bksp work

[Felix Miata]

On 2014-05-07 18:22 (GMT+0100) Sérgio Basto composed:


answering to the subject



my /etc/X11/xorg.conf is:



Section "ServerLayout"
 Identifier "single head configuration"
 Option  "DontZap" "false"
 Option  "DontZoom" "false"
EndSection


In what way does that answer anything? Unless you are using a UMS video driver, I 
doubt DontZoom has any effect on anything. Does Ctrl-Alt-Bksp do anything on your 
system? If so, what locale do you use, and which video driver?

--
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/
--
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: making Ctrl-Alt-Bksp work (was: first and only X needs to be on tty7)

[Sérgio Basto]

answering to the subject 

my /etc/X11/xorg.conf is: 

Section "ServerLayout"
Identifier "single head configuration"
Option  "DontZap" "false"
Option  "DontZoom" "false"
EndSection


On Qua, 2014-05-07 at 21:09 +1000, Peter Hutterer wrote: 
> On Tue, May 06, 2014 at 06:15:12AM -0400, Felix Miata wrote:
> > On 2014-05-06 00:13 (GMT-0700) Samuel Sieb composed:
> > 
> > >Felix Miata wrote:
> > 
> > >>For years, probably since the time of that document, I've had
> > 
> > >> Option"DontZap""off"
> > >> Option"ZapWarning""off"
> > 
> > >>somewhere in /etc/X11/xorg.con*. It used to work. Now it fails, but only
> > >>in Fedora (at least as far back as F14, worked as recent at least as
> > >>F8), so far that I've noticed.
> > 
> > >I use the following that works on F20:
> > ># cat /etc/X11/xorg.conf.d/99-zap.conf
> > >Section "ServerFlags"
> > >  Option "DontZap" "false"
> > >EndSection
> > 
> > >Section "InputClass"
> > >  Identifier  "Keyboard Defaults"
> > >  MatchIsKeyboard "yes"
> > >  Option  "XkbOptions" "terminate:ctrl_alt_bksp"
> > >EndSection
> 
> fwiw (only answering one email) this is what systemd-localed should drop
> into /etc/X11/xorg.conf.d/00-keyboard.conf, with configuration based on
> whatever language settings you picked. so you shouldn't need this section.
> 
> > Thank you!
> > 
> > Turns out DontZap works with either false or off, but the difference
> 
> the option parser in X is entertaining. "no", "off", "false", and "0" all
> work to disable, and so does prefixing the option with "No". So Option
> "NoDontZap" "off" is valid, just don't expect anyone to understand a
> triple-negation :) you can also sprinkle random whitespaces or underscores
> in there, in case you have too many of them.
> 
> Cheers,
>Peter
> 
> > between SUSE and Fedora is the addtional need for XkbOptions in
> > Fedora, and here's why:
> > 
> > /usr/share/X11/xkb/rules/
> > --- evdev   2014-01-29 22:45:32.0 -0500
> > +++ evdev-suse  2014-04-09 15:51:53.0 -0400
> > @@ -857,9 +857,9 @@
> >*yu  unicodeyz   =   
> > +srp(latinunicodeyz):4
> > 
> >  ! model=   symbols
> > -  $evdevkbds=   +inet(evdev)+inet(%m)
> > -  applealu_jis  =   +inet(evdev)+macintosh_vndr/jp(alujiskeys)
> > -  * =   +inet(evdev)
> > +  $evdevkbds=   +inet(evdev)+inet(%m)+terminate(ctrl_alt_bksp)
> > +  applealu_jis  =   
> > +inet(evdev)+macintosh_vndr/jp(alujiskeys)+terminate(ctrl_alt_bksp)
> > +  * =   +inet(evdev)+terminate(ctrl_alt_bksp)
> > 
> >  ! modellayout  =   symbols
> > 
> > Using the SUSE evdev file in place of Fedora's my original xorg.con*
> > that used to work also in Fedora works in it again without need for
> > the XkbOptions addition.
> > -- 
> > "The wise are known for their understanding, and pleasant
> > words are persuasive." Proverbs 16:21 (New Living Translation)
> > 
> >  Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
> > 
> > Felix Miata  ***  http://fm.no-ip.com/
> > -- 
> > devel mailing list
> > devel@lists.fedoraproject.org
> > https://admin.fedoraproject.org/mailman/listinfo/devel
> > Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
> > 

-- 
Sérgio M. B.

-- 
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: making Ctrl-Alt-Bksp work

[Felix Miata]

On 2014-05-07 21:09 (GMT+1000) Peter Hutterer composed:


>Section "InputClass"
>  Identifier  "Keyboard Defaults"
>  MatchIsKeyboard "yes"
>  Option  "XkbOptions" "terminate:ctrl_alt_bksp"
>EndSection



fwiw (only answering one email) this is what systemd-localed should drop
into /etc/X11/xorg.conf.d/00-keyboard.conf, with configuration based on
whatever language settings you picked. so you shouldn't need this section.


An F21 boot to multiuser, delete of 00-keyboard.conf, and then startx leaves 
/etc/X11/xorg.conf.d/ void of 00-keyboard.conf, so apparently systemd-localed 
currently drops nothing at all there.



Turns out DontZap works with either false or off, but the difference



the option parser in X is entertaining. "no", "off", "false", and "0" all
work to disable, and so does prefixing the option with "No". So Option
"NoDontZap" "off" is valid, just don't expect anyone to understand a
triple-negation :) you can also sprinkle random whitespaces or underscores
in there, in case you have too many of them.

--
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/
--
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: DISTRIBUTION tag seems wrong

[Dennis Gilmore]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Wed, 7 May 2014 10:54:38 -0400
Steve Grubb  wrote:

> Hello,
> 
> Not sure if this is bz worthy or just something to mention on a mail
> list. I was doing some experimenting on creating SWID tags out of the
> rpm database and noticed some inconsistencies. For example:
> 
> # rpm -q --queryformat '%{DISTRIBUTION}\n' bash
> Fedora Project
> # rpm -q --queryformat '%{DISTRIBUTION}\n' xbmc
> Fedora 20
> 
> Seems that rpmfusion has it right and the main Fedora build system is
> misconfigured.
rpmfusion has it wrong, they should be using rpmfusion.  koji sets the
distribution tag for everything that is built in the buildsys to be the
same. for fedora that is "Fedora Project" as that is who is building
and distributing the rpms

> Also...
> 
> # rpm -q --queryformat '%{PACKAGER}\n' bash
> Fedora Project
> # rpm -q --queryformat '%{PACKAGER}\n' xbmc
> 
> 
> Which is correct way to do it?
neither is wrong. 

> # rpm -q --queryformat '%{DISTTAG}\n' bash
> (none)
> # rpm -q --queryformat '%{DISTTAG}\n' xbmc
> (none)
> 
> You would think this would spit out f20. But it doesn't.

disttag is a macro defined at build time and is not something embedded
into the binary rpms.  I wouldn't expect it to be visible in the built
rpms.

Dennis
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.22 (GNU/Linux)

iQIcBAEBAgAGBQJTamUPAAoJEH7ltONmPFDRsecQAJhrvjnz8iXht0wEzmFkgWFZ
8rsa/ifBYVPq5N3FADJLPm0EnxEq6Q2twcKXJyqKG/exXVFxkj/ND5sqSYCJSSW1
+TRZ1ascNoCbfCrUdJOb7ZSsx1ZEAF+E1iv9ItdadGaz123alaM8wh8d/1C5ULxh
w8gUuCS7CwXvlxwjUjn+thqbYQzhv++OOjTgyW5n2FCqowtdEnQ0htybL3xmnUFm
HoNcFzOZVC3W+1viM6faLFIIwjo3BL5mwXjcx0jP5bpZ27V8N1fGlhqDEy5Tvzdu
j6IHNqY2vJPLw28bR3rh/J2hTT28ygWbuTUY4PKK1MfAFPsuRSVaT1LZ5xsyOLhI
hNrC+K9PtuWOQUfZNblVfzJhqbmVeaypzWRfq1sbtXzL9csTBt0ayebSurvdlf/A
BKFucmvGXndr12kfvyZaLe+OKDqWqCZuS71pJDV0axT9tdYeainu9+AmJ3JzZiHE
oZBsE/D+OuKawV8lip2nf02dpPpOEUlfpUd+dZR+A8zQbM3Tiencb/Uapz65Sog3
+7URUYLWxUV67Gwl4oqN+9qpbi4EZF8CktnpP15Ix/81nFL90BO7KctePY2Hc9wZ
6LKyWh5eKpiG1PsaKwFYDP41vDNb9HnTCeJlGjeJsvHb9MCsao3tIiCRyt/TyTlE
s0R83DDYgsaJoBMpJmuq
=89H5
-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

Heads up: nss-3.16.1 & nspr-4.10.5 released and now on Rawhide

[Elio Maldonado]

For more details please see the upstream release notes at 
https://developer.mozilla.org/en-US/docs/Mozilla/Projects/NSS/NSS_3.16.1_release_notes

-Elio
-- 
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: heads up: plist/usbmux/imobiledevice soname bumps

[Richard Shaw]

Ok, I have built F20 versions of the 3 libraries from your rawhide builds
and rebuilt the rest of the dependency chain with the current F20 versions
and was able to get good build and installed them. Since I did it remotely
I'll have to wait until I get home from work to test it out.

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: F21 Self Contained Change: Remote Journal Logging

[Marc Deop i Argemí]

On Tuesday 22 April 2014 06:34:48 Lennart Poettering wrote:
> On Wed, 16.04.14 12:46, Bill Nottingham (nott...@splat.cc) wrote:
> > Zbigniew Jędrzejewski-Szmek (zbys...@in.waw.pl) said:
> > > On Mon, Apr 14, 2014 at 04:20:16PM -0400, Bill Nottingham wrote:
> > > > Jaroslav Reznik (jrez...@redhat.com) said:
> > > > > = Proposed Self Contained Change: Remote Journal Logging =
> > > > > https://fedoraproject.org/wiki/Changes/Remote_Journal_Logging
> > > > > 
> > > > > Change owner(s): Zbigniew Jędrzejewski-Szmek 
> > > > > 
> > > > > Systemd journal can be configured to forward events to a remote
> > > > > server.
> > > > > Entries are forwarded including full metadata, and are stored in
> > > > > normal
> > > > > journal files, identically to locally generated logs.
> > > > 
> > > > What's the future of gatewayd if this becomes more widely used?
> > > 
> > > gatewayd works in pull mode. Here I'm proposing a push model, where the
> > > "client" (i.e. machine generating the logs) pushes logs to the server
> > > at the time of its own chosing. gatewayd is probably better for some use
> > > cases, this for others.
> > 
> > I understand the pull vs push distinction ... I'm just not clear why pull
> > would ever be a model you'd want to use. (vs something like a local
> > cockpit
> > agent.)
> 
> Pull is the only model that scales, since the centralized log infrastructure
> can schedule when it pulls from where and thus do this according to
> available resources. THe push model is prone to logging bursts
> overwhelming log servers if you scale your network up.

"Push" mechanism seems to scale pretty well when we talk about web sites. 
Specially taking into account that  you mentioned that systemd is going to use 
https protocol, you can take advantage of many existing solutions to 
scale/load balance your systems. (although that doesn't mean I agree on the 
election of the protocol)

> 
> I am pretty sure that a pull model should be the default for everything
> we do, and push only be done where realtimish behaviour is desired to do
> live debugging or suchlike.
> 

For me it should be precisely the other way around(in syslogging context)

> I am pretty sure the push model concept is one of the major weaknesses
> of the BSD syslog protocol.
> 

Again I disagree: for me is a strong point :-)

-- 
Marc Deop 
System Administrator

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: DISTRIBUTION tag seems wrong

[Bruno Wolff III]

On Wed, May 07, 2014 at 11:21:06 -0400,
 Steve Grubb  wrote:


If that's true, what tag should output Fedora 20? Something should. We
also have the VENDOR tag and that is Fedora Project. I think that is
the right place for Fedora Project.


For at least some things (e.g. yum) the release number is the version of 
system-release.

--
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: DISTRIBUTION tag seems wrong

[Steve Grubb]

On Wed, 7 May 2014 19:02:57 +0400
Igor Gnatenko  wrote:
> > Not sure if this is bz worthy or just something to mention on a mail
> > list. I was doing some experimenting on creating SWID tags out of
> > the rpm database and noticed some inconsistencies. For example:
> >
> > # rpm -q --queryformat '%{DISTRIBUTION}\n' bash
> > Fedora Project
> > # rpm -q --queryformat '%{DISTRIBUTION}\n' xbmc
> > Fedora 20
> >
> > Seems that rpmfusion has it right and the main Fedora build system
> > is misconfigured.
>
> I think first right. How about EPEL?

If that's true, what tag should output Fedora 20? Something should. We
also have the VENDOR tag and that is Fedora Project. I think that is
the right place for Fedora Project.

-Steve

> > Also...
> >
> > # rpm -q --queryformat '%{PACKAGER}\n' bash
> > Fedora Project
> > # rpm -q --queryformat '%{PACKAGER}\n' xbmc
> > 
> >
> > Which is correct way to do it?
>
> First. We choosed first method for Copr (but with changes)
> >
> > # rpm -q --queryformat '%{DISTTAG}\n' bash
> > (none)
> > # rpm -q --queryformat '%{DISTTAG}\n' xbmc
> > (none)
> >
> > You would think this would spit out f20. But it doesn't.
>
> Here I think the same.
-- 
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: DISTRIBUTION tag seems wrong

[Igor Gnatenko]

On May 7, 2014 6:54 PM, "Steve Grubb"  wrote:
>
> Hello,
Hi,
>
> Not sure if this is bz worthy or just something to mention on a mail
> list. I was doing some experimenting on creating SWID tags out of the
> rpm database and noticed some inconsistencies. For example:
>
> # rpm -q --queryformat '%{DISTRIBUTION}\n' bash
> Fedora Project
> # rpm -q --queryformat '%{DISTRIBUTION}\n' xbmc
> Fedora 20
>
> Seems that rpmfusion has it right and the main Fedora build system is
> misconfigured.
I think first right. How about EPEL?
>
> Also...
>
> # rpm -q --queryformat '%{PACKAGER}\n' bash
> Fedora Project
> # rpm -q --queryformat '%{PACKAGER}\n' xbmc
> 
>
> Which is correct way to do it?
First. We choosed first method for Copr (but with changes)
>
> # rpm -q --queryformat '%{DISTTAG}\n' bash
> (none)
> # rpm -q --queryformat '%{DISTTAG}\n' xbmc
> (none)
>
> You would think this would spit out f20. But it doesn't.
Here I think the same.
>
> -Steve
--
-Igor Gnatenko
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

DISTRIBUTION tag seems wrong

[Steve Grubb]

Hello,

Not sure if this is bz worthy or just something to mention on a mail
list. I was doing some experimenting on creating SWID tags out of the
rpm database and noticed some inconsistencies. For example:

# rpm -q --queryformat '%{DISTRIBUTION}\n' bash
Fedora Project
# rpm -q --queryformat '%{DISTRIBUTION}\n' xbmc
Fedora 20

Seems that rpmfusion has it right and the main Fedora build system is
misconfigured.

Also...

# rpm -q --queryformat '%{PACKAGER}\n' bash
Fedora Project
# rpm -q --queryformat '%{PACKAGER}\n' xbmc


Which is correct way to do it?

# rpm -q --queryformat '%{DISTTAG}\n' bash
(none)
# rpm -q --queryformat '%{DISTTAG}\n' xbmc
(none)

You would think this would spit out f20. But it doesn't.

-Steve
-- 
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-java] Mass-bug filing for removed OpenJDK 9 internal APIs

[Florian Weimer]

On 05/06/2014 02:15 PM, Mikolaj Izdebski wrote:

On 05/06/2014 02:00 PM, Florian Weimer wrote:

I plan to file bugs against packages which contain hard (i.e. not
reflection-based) references to internal OpenJDK classes and methods
which have been removed from OpenJDK 9.  The total number of affected
packages is around 40.  The bug reports will mention the recommended
replacements in the public API.

This does not affect features like the support for pointer arithmetic
and arbitrary memory access, at least not until they are removed upstream.

Comments?


IMO go ahead, but please add them to some tracking bug.


The top-level trackers are:

https://bugzilla.redhat.com/show_bug.cgi?id=1095326 (OpenJDK 8)
https://bugzilla.redhat.com/show_bug.cgi?id=1094780 (OpenJDK 9)

--
Florian Weimer / Red Hat Product Security Team
--
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 1094488] [abrt] logwatch: do_clean_objs(): perl killed by SIGSEGV

[bugzilla]

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



--- Comment #12 from Petr Pisar  ---
The code crashes because of jumping into invalid address when destroying
allocated data structures on perl interpreter exit. This is itself very weird
and it can be a symptom of bug in the perl, a memory corruption, or a compiler
bug.

Because the the code flow of the logwatch tool depends on the file system
content, it's almost impossible to reproduce this crash and thus to debug this
problem. E.g., the "/usr/sbin/logwatch --output mail" command proceeds cleanly
for me.

I'm sorry, but without more details, especially debugging on your side like
narrowing what's the trigger, it's impossible to fix this issue.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug 
https://bugzilla.redhat.com/token.cgi?t=ycC2QIkwiu&a=cc_unsubscribe
--
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: BerkeleyDB 6 symbol versioning and associated problems

[Joe Orton]

On Wed, May 07, 2014 at 03:19:42PM +0200, Jan Staněk wrote:
> One of the planned parts of the F21 System Wide Change: BerkeleyDB 6 [1]
> is the introduction of downstream symbol versioning of both versions of
> the libraries (libdb with v6 and libdb5 with v5). This part is planned
> in order to not introduce bugs similar to [2]. However, if we introduce
> downstream versioning (as upstream is generally unresponsive), then we
> face the problem similar to [3].

If we keep libdb5 (forever?) then the [3] problem is less of an issue, 
IMO.  Given that portably linking against libdb has historically been a 
major headache I'd be surprised if there are any binary third-party apps 
which even try doing this, to be honest.

I don't claim to understand the licensing matrix here, though, is there 
any background reading on that?  Can we even switch *anything* which is 
potentially linked into httpd to using BDB 6?  If not then basically 
nothing in $libdir can link against BDB 6.

Regards, Joe

-- 
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-Params-Validate] Upstream update.

[corsepiu]

commit e3f366e155cbbb7dde82b63801162a2245c0c52a
Author: Ralf Corsépius 
Date:   Wed May 7 15:34:21 2014 +0200

Upstream update.

 .gitignore|2 +-
 perl-Params-Validate.spec |8 ++--
 sources   |2 +-
 3 files changed, 8 insertions(+), 4 deletions(-)
---
diff --git a/.gitignore b/.gitignore
index 82511d6..06966e8 100644
--- a/.gitignore
+++ b/.gitignore
@@ -1 +1 @@
-/Params-Validate-1.08.tar.gz
+/Params-Validate-1.09.tar.gz
diff --git a/perl-Params-Validate.spec b/perl-Params-Validate.spec
index 337a967..0ce3d80 100644
--- a/perl-Params-Validate.spec
+++ b/perl-Params-Validate.spec
@@ -15,8 +15,8 @@
 
 Summary:   Params-Validate Perl module
 Name:  perl-Params-Validate
-Version:   1.08
-Release:   8%{?dist}
+Version:   1.09
+Release:   1%{?dist}
 License:   Artistic 2.0
 Group: Development/Libraries
 URL:   http://search.cpan.org/dist/Params-Validate/
@@ -42,6 +42,7 @@ BuildRequires:  perl(File::Temp)
 BuildRequires:  perl(lib)
 BuildRequires:  perl(Test::Fatal)
 BuildRequires:  perl(Test::More) >= 0.88
+BuildRequires:  perl(Test::Requires)
 BuildRequires:  perl(Test::Taint) >= 0.02
 BuildRequires:  perl(Tie::Array)
 BuildRequires:  perl(Tie::Hash)
@@ -97,6 +98,9 @@ find $RPM_BUILD_ROOT -type d -depth -exec rmdir {} 
2>/dev/null ';'
 %{_mandir}/man3/*
 
 %changelog
+* Wed May 07 2014 Ralf Corsépius  - 1.09-1
+- Upstream update.
+
 * Wed May 07 2014 Ralf Corsépius  - 1.08-8
 - Use aspell-en instead of hunspell.
 
diff --git a/sources b/sources
index 063375d..0aad84d 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-5edfb0ffd92cbb0e2646ddf23d4516e9  Params-Validate-1.08.tar.gz
+959dfc6798e877d70a8a10c513d46967  Params-Validate-1.09.tar.gz
--
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

File Params-Validate-1.09.tar.gz uploaded to lookaside cache by corsepiu

[corsepiu]

A file has been added to the lookaside cache for perl-Params-Validate:

959dfc6798e877d70a8a10c513d46967  Params-Validate-1.09.tar.gz
--
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: BerkeleyDB 6 symbol versioning and associated problems

[Florian Weimer]

On 05/07/2014 03:19 PM, Jan Staněk wrote:

One of the planned parts of the F21 System Wide Change: BerkeleyDB 6 [1]
is the introduction of downstream symbol versioning of both versions of
the libraries (libdb with v6 and libdb5 with v5). This part is planned
in order to not introduce bugs similar to [2]. However, if we introduce
downstream versioning (as upstream is generally unresponsive), then we
face the problem similar to [3].


If upstream is unresponsive, why even upgrade to a new version with 
licensing-related challenges?


Anyway, have you investigated if you can use the upstream symbol 
mangling mechanism?




--
Florian Weimer / Red Hat Product Security Team
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

BerkeleyDB 6 symbol versioning and associated problems

[Jan Staněk]

One of the planned parts of the F21 System Wide Change: BerkeleyDB 6 [1]
is the introduction of downstream symbol versioning of both versions of
the libraries (libdb with v6 and libdb5 with v5). This part is planned
in order to not introduce bugs similar to [2]. However, if we introduce
downstream versioning (as upstream is generally unresponsive), then we
face the problem similar to [3].

In short, if we introduce the downstream versioning, we will ship
library with ABI incompatible with upstream ABI. If we won't,
applications with modules/plugins (ie. Apache with mod_perl) that each
use different version of the library may break due to double symbols
(one from the v5 and other from v6, and ld would not know which symbol
is which).

I'd like to ask for suggestions on how to resolve this problem.

The ideal solution would be to convince upstream to version their
symbols (and I will contact them about it), but from my experience with
them this is very unlikely. Or we could try to keep an eye on
troublesome applications and force them and all their modules/plugins to
be built with the same version of libdb, but I have no idea if this is
even possible.

As I stated above, I welcome any suggestions. I would also like to hear
from someone responsible for the distro architecture which of the
aforementioned issues is more painful for us, so we know which path to
take if no complete solution is found.

Best regards and thanks for replies,
Jan

[1] https://fedoraproject.org/wiki/Changes/BerkeleyDB_6
[2] https://bugzilla.redhat.com/show_bug.cgi?id=768846
[3] https://bugzilla.redhat.com/show_bug.cgi?id=1045013
-- 
Jan Stanek - Red Hat Associate Developer Engineer - Databases Team
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

package doesn't build due to possible regression in gcc 4.9.0

[Martin Gieseking]

Hi,

I'm currently trying to rebuild the zorba package due to a broken 
dependency in rawhide. Unfortunately, the newly built binary segfaults 
when it's compiled with gcc 4.9.0. The same package builds correctly for 
f20 (using gcc 4.8.2). It seems that this is a regression in the 
optimizer of gcc 4.9.0 since the issue only appears when building with 
-O1, -O2, or -O3. An "unoptimized build" (-O0) succeeds.


Unfortunately, it's pretty hard to debug an optimized binary in order to 
isolate the origin of the segfault. It would be great if somebody could 
help to track down the issue.


Here is the corresponding BZ bug:
https://bugzilla.redhat.com/show_bug.cgi?id=1095292

Martin
--
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: making Ctrl-Alt-Bksp work (was: first and only X needs to be on tty7)

[Peter Hutterer]

On Tue, May 06, 2014 at 06:15:12AM -0400, Felix Miata wrote:
> On 2014-05-06 00:13 (GMT-0700) Samuel Sieb composed:
> 
> >Felix Miata wrote:
> 
> >>For years, probably since the time of that document, I've had
> 
> >> Option"DontZap""off"
> >> Option"ZapWarning""off"
> 
> >>somewhere in /etc/X11/xorg.con*. It used to work. Now it fails, but only
> >>in Fedora (at least as far back as F14, worked as recent at least as
> >>F8), so far that I've noticed.
> 
> >I use the following that works on F20:
> ># cat /etc/X11/xorg.conf.d/99-zap.conf
> >Section "ServerFlags"
> >  Option "DontZap" "false"
> >EndSection
> 
> >Section "InputClass"
> >  Identifier  "Keyboard Defaults"
> >  MatchIsKeyboard "yes"
> >  Option  "XkbOptions" "terminate:ctrl_alt_bksp"
> >EndSection

fwiw (only answering one email) this is what systemd-localed should drop
into /etc/X11/xorg.conf.d/00-keyboard.conf, with configuration based on
whatever language settings you picked. so you shouldn't need this section.

> Thank you!
> 
> Turns out DontZap works with either false or off, but the difference

the option parser in X is entertaining. "no", "off", "false", and "0" all
work to disable, and so does prefixing the option with "No". So Option
"NoDontZap" "off" is valid, just don't expect anyone to understand a
triple-negation :) you can also sprinkle random whitespaces or underscores
in there, in case you have too many of them.

Cheers,
   Peter

> between SUSE and Fedora is the addtional need for XkbOptions in
> Fedora, and here's why:
> 
> /usr/share/X11/xkb/rules/
> --- evdev 2014-01-29 22:45:32.0 -0500
> +++ evdev-suse2014-04-09 15:51:53.0 -0400
> @@ -857,9 +857,9 @@
>*  yu  unicodeyz   =   +srp(latinunicodeyz):4
> 
>  ! model  =   symbols
> -  $evdevkbds=   +inet(evdev)+inet(%m)
> -  applealu_jis  =   +inet(evdev)+macintosh_vndr/jp(alujiskeys)
> -  * =   +inet(evdev)
> +  $evdevkbds=   +inet(evdev)+inet(%m)+terminate(ctrl_alt_bksp)
> +  applealu_jis  =   
> +inet(evdev)+macintosh_vndr/jp(alujiskeys)+terminate(ctrl_alt_bksp)
> +  * =   +inet(evdev)+terminate(ctrl_alt_bksp)
> 
>  ! model  layout  =   symbols
> 
> Using the SUSE evdev file in place of Fedora's my original xorg.con*
> that used to work also in Fedora works in it again without need for
> the XkbOptions addition.
> -- 
> "The wise are known for their understanding, and pleasant
> words are persuasive." Proverbs 16:21 (New Living Translation)
> 
>  Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
> 
> Felix Miata  ***  http://fm.no-ip.com/
> -- 
> 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: first and only X needs to be on tty7

[Peter Hutterer]

On Tue, May 06, 2014 at 12:21:05AM -0400, Felix Miata wrote:
> On 2014-05-06 11:04 (GMT+1000) Peter Hutterer composed:
> 
> >On Mon, May 05, 2014 at 11:45:31AM -0400, Felix Miata wrote:
> 
> >>I might not even care about the location of X sessions if only it
> >>wasn't so complicated to kill a broken one. Why doesn't Ctrl-Alt-BS
> >>not work any more?
> 
> >http://who-t.blogspot.com.au/2009/04/zapping-server.html
> 
> Are you by providing that link in any way suggesting that there's
> been a keymap change that needs a user adjustment (for KDE users
> anyway if not others)? It provides no help where to look to make it
> happen globally in a post-sysvinit world.

there is no "globally" and it has nothing to do with being post-sysvinit.
you can add it to the default options on startup with an InputClass section
(which we do, check /etc/X11/xorg.conf.d/00-keyboard.conf) so it'll work out
of the box until something overwrites the user's keymap. That something
could be gdm or your desktop environment, ymmv.

if you want it set for your user in GNOME, install gnome-tweak-tool, it's in
Typing, iirc. Other desktops have other ways to configure it, but I don't
know those off-heart.
 
> For years, probably since the time of that document, I've had
> 
>   Option  "DontZap"   "off"
>   Option  "ZapWarning""off"
> 
> somewhere in /etc/X11/xorg.con*. It used to work. Now it fails, but

DontZap disallows zapping completely, regardless of your xkb settings. But
you're setting it to what is the default, so it has no effect. ZapWarning
is not an option in Fedora, it's an old SuSE patch that never got merged
upstream. Your config has no effect since X server 1.6 or possibly longer.

> only in Fedora (at least as far back as F14, worked as recent at
> least as F8), so far that I've noticed.

F11 had this change, judging by the package names I linked to in that blog
post.
 
> They still get the job done in Cauldron's 1.15.99.902, Factory's
> 1.15.99.902.2 and Linux Mint LMDE (aka Debian Jessie/Sid) 1.14.3.

yeah, and Fedora stays close to upstream, so we don't have those patches.

Cheers,
   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: Don't use at_console in DBus policy files

[Stef Walter]

On 06.05.2014 15:36, Richard W.M. Jones wrote:
> On Fedora 20, I'm seeing this list:
> 
> /etc/dbus-1/system.d/bluetooth.conf: bluez-0:5.12-1.fc20.x86_64
> /etc/dbus-1/system.d/com.redhat.NewPrinterNotification.conf: 
> system-config-printer-libs-0:1.4.3-2.fc20.noarch
> /etc/dbus-1/system.d/com.redhat.PrinterDriversInstaller.conf: 
> system-config-printer-libs-0:1.4.3-2.fc20.noarch
> /etc/dbus-1/system.d/com.redhat.tuned.conf: tuned-0:2.3.0-2.fc20.noarch
> tuned-0:2.3.0-3.fc20.noarch
> /etc/dbus-1/system.d/connman.conf: connman-0:1.21-1.fc20.x86_64
> /etc/dbus-1/system.d/dbus-abrt.conf: abrt-dbus-0:2.2.1-1.fc20.x86_64
> /etc/dbus-1/system.d/FirewallD.conf: firewalld-0:0.3.9.3-1.fc20.noarch
> /etc/dbus-1/system.d/nm-ifcfg-rh.conf: 
> NetworkManager-1:0.9.9.0-38.git20131003.fc20.x86_64
> /etc/dbus-1/system.d/nm-user-settings.conf: sugar-0:0.100.2-1.fc20.noarch
> /etc/dbus-1/system.d/ofono.conf: ofono-0:1.14-1.fc20.x86_64
> /etc/dbus-1/system.d/org.fedoraproject.Setroubleshootd.conf: 
> setroubleshoot-server-0:3.2.17-1.fc20.x86_64
> /etc/dbus-1/system.d/org.fedoraproject.SetroubleshootFixit.conf: 
> setroubleshoot-server-0:3.2.17-1.fc20.x86_64
> /etc/dbus-1/system.d/org.freedesktop.NetworkManager.conf: 
> NetworkManager-1:0.9.9.0-38.git20131003.fc20.x86_64
> /etc/dbus-1/system.d/org.selinux.conf: 
> policycoreutils-python-0:2.2.5-3.fc20.x86_64
> /etc/dbus-1/system.d/wicd.conf: wicd-common-0:1.7.2.4-7.fc20.noarch
> /etc/dbus-1/system.d/yum-updatesd.conf: yum-updatesd-1:0.9-15.fc20.noarch

Thanks! And thanks for the repoquery info.

I've filed a bunch more bugs tracked here:

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

Cheers,

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