Re: Test upgrades from F37 to F38 - it will take you just a minute

[Nathanael D. Noblet]

On Wed, 2023-02-22 at 10:30 +0100, Miroslav Suchý wrote:
> dnf --releasever=38 --setopt=module_platform_id=platform:f38 \
>  --enablerepo=updates-testing \
>  $(rpm -q fedora-repos-modular >/dev/null && echo --
> enablerepo=updates-testing-modular) \
>  --assumeno distro-sync

I got 

Error: 
 Problem: package msv-xsdlib-1:2013.6.1-19.fc33.noarch requires
mvn(relaxngDatatype:relaxngDatatype), but none of the providers can be
installed
  - jaxb-relaxng-datatype-2.3.5-7.fc37.noarch does not belong to a
distupgrade repository
  - problem with installed package msv-xsdlib-1:2013.6.1-19.fc33.noarch
(try to add '--skip-broken' to skip uninstallable packages)


I don't know why those are installed (I don't recognize the packages
and they aren't dependencies of anything I know I need) and just
removed them and everything was good after that.


___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Donate 1 minute of your time to test upgrades from F36 to F37

[Nathanael D. Noblet]

On Mon, 2022-09-12 at 14:59 +0200, Miroslav Suchý wrote:
> Do you want to make Fedora 37 better? Please spend 1 minute of your
> time and try to run:
>  
>  # Run this only if you use default Fedora modules
>  # next time you run any DNF command default modules will be enabled
> again
>  sudo dnf module reset '*'
>  
> dnf --releasever=37 --setopt=module_platform_id=platform:f37 \
>  --enablerepo=updates-testing \
>  $(rpm -q fedora-repos-modular >/dev/null && echo --
> enablerepo=updates-testing-modular) \
>  --assumeno distro-sync
> 
Error: 
 Problem 1: package lucene-analysis-8.8.2-1.fc35.noarch requires
mvn(org.apache.lucene:lucene-core) = 8.8.2, but none of the providers
can be installed
  - package lucene-analysis-8.8.2-1.fc35.noarch requires
osgi(org.apache.lucene.core) = 8.8.2, but none of the providers can be
installed
  - lucene-8.8.2-1.fc35.noarch does not belong to a distupgrade
repository
  - problem with installed package lucene-analysis-8.8.2-1.fc35.noarch
 Problem 2: package nautilus-dropbox-1:2020.03.04-3.fc35.x86_64
requires libnautilus-extension.so.1()(64bit), but none of the providers
can be installed
  - nautilus-extensions-42.2-1.fc36.x86_64 does not belong to a
distupgrade repository
  - problem with installed package nautilus-dropbox-1:2020.03.04-
3.fc35.x86_64
 Problem 3: package perl-File-Inplace-0.20-31.fc36.noarch requires
perl(:MODULE_COMPAT_5.34.0), but none of the providers can be installed
  - perl-libs-4:5.34.1-486.fc36.x86_64 does not belong to a distupgrade
repository
  - problem with installed package perl-File-Inplace-0.20-
31.fc36.noarch
  - package perl-libs-4:5.34.1-487.module_f37+15117+20131e0e.x86_64 is
filtered out by modular filtering
 Problem 4: package mod_perl-2.0.12-5.fc37.x86_64 requires
libperl.so.5.36()(64bit), but none of the providers can be installed
  - cannot install both perl-libs-4:5.36.0-491.fc37.x86_64 and perl-
libs-4:5.34.1-486.fc36.x86_64
  - cannot install both perl-libs-4:5.36.0-492.fc37.x86_64 and perl-
libs-4:5.34.1-486.fc36.x86_64
  - problem with installed package mod_perl-2.0.12-1.fc36.x86_64
  - package perl-Lingua-EN-Fathom-1.22-11.fc36.noarch requires
perl(:MODULE_COMPAT_5.34.0), but none of the providers can be installed
  - mod_perl-2.0.12-1.fc36.x86_64 does not belong to a distupgrade
repository
  - problem with installed package perl-Lingua-EN-Fathom-1.22-
11.fc36.noarch
  - package perl-libs-4:5.34.1-487.module_f37+15117+20131e0e.x86_64 is
filtered out by modular filtering
  - package perl-libs-4:5.36.0-491.module_f37+14796+372df908.x86_64 is
filtered out by modular filtering
 Problem 5: package perl-BDB-1.92-18.fc37.x86_64 requires
libperl.so.5.36()(64bit), but none of the providers can be installed
  - cannot install both perl-libs-4:5.36.0-491.fc37.x86_64 and perl-
libs-4:5.34.1-486.fc36.x86_64
  - cannot install both perl-libs-4:5.36.0-492.fc37.x86_64 and perl-
libs-4:5.34.1-486.fc36.x86_64
  - problem with installed package perl-BDB-1.92-16.fc36.x86_64
  - package perl-Lingua-EN-Syllable-1:0.30-18.fc36.noarch requires
perl(:MODULE_COMPAT_5.34.0), but none of the providers can be installed
  - perl-BDB-1.92-16.fc36.x86_64 does not belong to a distupgrade
repository
  - problem with installed package perl-Lingua-EN-Syllable-1:0.30-
18.fc36.noarch
  - package perl-libs-4:5.34.1-487.module_f37+15117+20131e0e.x86_64 is
filtered out by modular filtering
  - package perl-libs-4:5.36.0-491.module_f37+14796+372df908.x86_64 is
filtered out by modular filtering
 Problem 6: package perl-BSD-Resource-1.291.100-20.fc37.x86_64 requires
libperl.so.5.36()(64bit), but none of the providers can be installed
  - cannot install both perl-libs-4:5.36.0-491.fc37.x86_64 and perl-
libs-4:5.34.1-486.fc36.x86_64
  - cannot install both perl-libs-4:5.36.0-492.fc37.x86_64 and perl-
libs-4:5.34.1-486.fc36.x86_64
  - problem with installed package perl-BSD-Resource-1.291.100-
18.fc36.x86_64
  - package publican-4.3.2-23.fc36.noarch requires
perl(:MODULE_COMPAT_5.34.0), but none of the providers can be installed
  - perl-BSD-Resource-1.291.100-18.fc36.x86_64 does not belong to a
distupgrade repository
  - problem with installed package publican-4.3.2-23.fc36.noarch
  - package perl-libs-4:5.34.1-487.module_f37+15117+20131e0e.x86_64 is
filtered out by modular filtering
  - package perl-libs-4:5.36.0-491.module_f37+14796+372df908.x86_64 is
filtered out by modular filtering
(try to add '--allowerasing' to command line to replace conflicting
packages or '--skip-broken' to skip uninstallable packages)

___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 

Re: Request for assistance: zfs-fuse

[Nathanael D. Noblet]

On Tue, 2022-08-09 at 18:17 +, Gwyn Ciesla via devel wrote:
> 
> 
> > gcc -o cmd/mount_zfs/mount_zfs.o -c "-O2 -flto=auto -ffat-lto-
> > objects
> > -fexceptions -g -grecord-gcc-switches -pipe -Wall
> > -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2
> > -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-
> > hardened-cc1
> > -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-
> > cc1
> > -m64 -mcpu=power8 -mtune=power8 -fasynchronous-unwind-tables
> > -fstack-clash-protection" -pipe -Wall -std=c99 -Wno-switch -Wno-
> > unused
> > -Wno-missing-braces -Wno-parentheses -Wno-uninitialized -Wcast-
> > align
> > -fno-strict-aliasing -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -
> > D_REENTRANT
> > -DTEXT_DOMAIN=\"zfs-fuse\" -ggdb -DDEBUG -fPIC -DLINUX_AIO
> > -I/usr/include/tirpc -Ilib/libuutil/include -Ilib/libnvpair/include
> > -Ilib/libumem/include -Ilib/libzfscommon/include -
> > Ilib/libzpool/include
> > -Ilib/libzfs/include -Ilib/libsolcompat/include -
> > Ilib/libavl/include
> > cmd/mount_zfs/mount_zfs.c
> > cc1: error: argument to '-O' should be a non-negative integer, 'g',
> > 's',
> > 'z' or 'fast'
> > 
> 
> Doesn't help:
> 
> + '[' -f /usr/lib/rpm/generate-rpm-note.sh ']'
> + /usr/lib/rpm/generate-rpm-note.sh zfs-fuse 0.7.2.2-22.fc38 x86_64
> + cd zfs-fuse-0.7.2.2
> + export CCFLAGS=-O2 -flto=auto -ffat-lto-objects -fexceptions -g -
> grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-
> D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS -
> specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-
> strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -
> mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -
> fcf-protection
> + CCFLAGS=-O2
> /var/tmp/rpm-tmp.u56vY5: line 42: export: `-flto=auto': not a valid
> identifier
> /var/tmp/rpm-tmp.u56vY5: line 42: export: `-ffat-lto-objects': not a
> valid identifier
> /var/tmp/rpm-tmp.u56vY5: line 42: export: `-fexceptions': not a valid
> identifier
> /var/tmp/rpm-tmp.u56vY5: line 42: export: `-g': not a valid
> identifier
> /var/tmp/rpm-tmp.u56vY5: line 42: export: `-grecord-gcc-switches':
> not a valid identifier
> /var/tmp/rpm-tmp.u56vY5: line 42: export: `-pipe': not a valid
> identifier
> /var/tmp/rpm-tmp.u56vY5: line 42: export: `-Wall': not a valid
> identifier
> /var/tmp/rpm-tmp.u56vY5: line 42: export: `-Werror=format-security':
> not a valid identifier
> /var/tmp/rpm-tmp.u56vY5: line 42: export: `-Wp,-D_FORTIFY_SOURCE=2':
> not a valid identifier
> /var/tmp/rpm-tmp.u56vY5: line 42: export: `-Wp,-
> D_GLIBCXX_ASSERTIONS': not a valid identifier
> /var/tmp/rpm-tmp.u56vY5: line 42: export: `-
> specs=/usr/lib/rpm/redhat/redhat-hardened-cc1': not a valid
> identifier
> /var/tmp/rpm-tmp.u56vY5: line 42: export: `-fstack-protector-strong':
> not a valid identifier
> /var/tmp/rpm-tmp.u56vY5: line 42: export: `-
> specs=/usr/lib/rpm/redhat/redhat-annobin-cc1': not a valid identifier
> /var/tmp/rpm-tmp.u56vY5: line 42: export: `-m64': not a valid
> identifier
> /var/tmp/rpm-tmp.u56vY5: line 42: export: `-mtune=generic': not a
> valid identifier
> /var/tmp/rpm-tmp.u56vY5: line 42: export: `-fasynchronous-unwind-
> tables': not a valid identifier
> /var/tmp/rpm-tmp.u56vY5: line 42: export: `-fstack-clash-protection':
> not a valid identifier
> /var/tmp/rpm-tmp.u56vY5: line 42: export: `-fcf-protection': not a
> valid identifier
> error: Bad exit status from /var/tmp/rpm-tmp.u56vY5 (%build)
> 


I'm no expert but you're hitting two different issues. Your first error
message was running the compilre gcc with options being quoted.

gcc -o cmd/mount_zfs/mount_zfs.o -c "-O2 -flto=auto "

The second is when the environment variable is being exported.

export CCFLAGS=-O2 -flto=auto ...

I think you want export CCFLAGS="-O2 -flto=auto" and the gcc line to
not quote the env var.

Maybe post the spec somewhere?

Sincerely,
-- 
Nathanael
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: FESCo wants to know what you use i686 packages for

[Nathanael D. Noblet]

One more update.

On Wed, 2022-04-06 at 16:24 +, Nathanael Noblet wrote:
> Hello,
> 
>    I didn't think I needed i386 personally. In fact due to this
> thread I removed many i386 packages left on my machine. Just today I
> plugged in an 'IronKey' device. Its an encrypted USB drive. When
> plugged in a read only like mount is mounted, like a CD. On it is a
> binary to unlock the device. It no longer works, I get an "unable to
> execute ./ironkey: No such file or directory" likely because I'm now
> missing the i386 libraries or other requirements.

Looks like I need 
glibc.i686 (and it installed glibc-gconv-extra.i686, libgcc.i686) for
this ironkey device.

Sincerely,
-- 
Nathanael
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

F36 - Errors/Warnings with `dnf update`

[Nathanael D. Noblet]

Hello,

  Just wondering if this is a bug and what to report against. I
upgraded from F35 to F36Beta last night. Today I ran `sudo dnf update`
and saw some odd output. Not sure if its a bug with dnf or selinux or
the packages being installed. Let me know if its a known issue or if I
need to file a bug and where.

Running transaction
  Preparing:  
1/1 
  Upgrading: crun-1.4.4-1.fc36.x86_64 
1/16 
error: lsetfilecon: (/usr/bin/crun;62451078,
system_u:object_r:container_runtime_exec_t:s0) Invalid argument
error: Plugin selinux: hook fsm_file_prepare failed

Error unpacking rpm package crun-1.4.4-1.fc36.x86_64
  Upgrading: containers-common-4:1-53.fc36.noarch 
2/16 
error: unpacking of archive failed on file /usr/bin/crun;62451078:
cpio: (error 0x2)
error: crun-1.4.4-1.fc36.x86_64: install failed
error: lsetfilecon: (/var/lib/containers/sigstore,
system_u:object_r:container_var_lib_t:s0) Invalid argument
error: Plugin selinux: hook fsm_file_prepare failed

Error unpacking rpm package containers-common-4:1-53.fc36.noarch
  Upgrading: conmon-2:2.1.0-2.fc36.x86_64 
3/16 
error: unpacking of archive failed on file
/var/lib/containers/sigstore: cpio: (error 0x2)
error: containers-common-4:1-53.fc36.noarch: install failed
error: lsetfilecon: (/usr/bin/conmon;62451078,
system_u:object_r:conmon_exec_t:s0) Invalid argument
error: Plugin selinux: hook fsm_file_prepare failed

Error unpacking rpm package conmon-2:2.1.0-2.fc36.x86_64
  Upgrading: podman-3:4.0.2-1.fc36.x86_64 
4/16 
error: unpacking of archive failed on file /usr/bin/conmon;62451078:
cpio: (error 0x2)
error: conmon-2:2.1.0-2.fc36.x86_64: install failed
error: lsetfilecon: (/usr/bin/podman;62451078,
system_u:object_r:container_runtime_exec_t:s0) Invalid argument
error: Plugin selinux: hook fsm_file_prepare failed

Error unpacking rpm package podman-3:4.0.2-1.fc36.x86_64
  Upgrading: runc-2:1.1.1-1.fc36.x86_64   
5/16 
error: unpacking of archive failed on file /usr/bin/podman;62451078:
cpio: (error 0x2)
error: podman-3:4.0.2-1.fc36.x86_64: install failed
error: lsetfilecon: (/usr/bin/runc;62451078,
system_u:object_r:container_runtime_exec_t:s0) Invalid argument
error: Plugin selinux: hook fsm_file_prepare failed

Error unpacking rpm package runc-2:1.1.1-1.fc36.x86_64
  Upgrading: swtpm-0.7.2-1.20220307git21c90c1.fc36.x86_64 
6/16 
error: unpacking of archive failed on file /usr/bin/runc;62451078:
cpio: (error 0x2)
error: runc-2:1.1.1-1.fc36.x86_64: install failed
error: lsetfilecon: (/usr/bin/swtpm;62451078,
system_u:object_r:swtpm_exec_t:s0) Invalid argument
error: Plugin selinux: hook fsm_file_prepare failed

Error unpacking rpm package swtpm-0.7.2-
1.20220307git21c90c1.fc36.x86_64
  Upgrading: snapd-2.54.4-1.fc36.x86_64   
7/16 
error: unpacking of archive failed on file /usr/bin/swtpm;62451078:
cpio: (error 0x2)
error: swtpm-0.7.2-1.20220307git21c90c1.fc36.x86_64: install failed
error: lsetfilecon: (/etc/sysconfig/snapd;62451078,
system_u:object_r:snappy_config_t:s0) Invalid argument
error: Plugin selinux: hook fsm_file_prepare failed

Error unpacking rpm package snapd-2.54.4-1.fc36.x86_64
  Running scriptlet: flatpak-1.12.7-1.fc36.x86_64 
8/16 
error: unpacking of archive failed on file
/etc/sysconfig/snapd;62451078: cpio: (error 0x2)
error: snapd-2.54.4-1.fc36.x86_64: install failed

  Upgrading: flatpak-1.12.7-1.fc36.x86_64 
8/16 
error: lsetfilecon: (/usr/libexec/flatpak-system-helper;62451078,
system_u:object_r:flatpak_helper_exec_t:s0) Invalid argument
error: Plugin selinux: hook fsm_file_prepare failed

Error unpacking rpm package flatpak-1.12.7-1.fc36.x86_64
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Orphaning some packages (w3c-markup-validator fallout)

[Nathanael D. Noblet]

Hello,

  I recently gave ownership of w3c-markup-validator to Sérgio Basto
which reminded me that there are a handful of perl packages that I
probably created/took a hand in as part of that. I haven't touched them
in as long as w3c-markup-validator so probably should also orphan them
as well. There are also some other packages like dspam that were great
at the time and I used to use them but they don't get much if any
development anymore and I don't run mail servers anymore.

The are as follows:

dspam
html401-dtds
perl-Config-General
perl-HTML-Encoding
perl-HTML-Tidy
perl-Mail-MBox-MessageParser
perl-Mail-MBox-MboxParser
perl-SGML-Parser-OpenSP
php-pecl-cairo
wkhtmltopdf

I will orphan them sometime next week if someone does want them. That
or retire but I don't know/remember what depends on them.


Sincerely,
-- 
Nathanael
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Orphaning some packages (w3c-markup-validator fallout)

[Nathanael D. Noblet]

Hello,

  I recently gave ownership of w3c-markup-validator to Sérgio Basto
which reminded me that there are a handful of perl packages that I
probably created/took a hand in as part of that. I haven't touched them
in as long as w3c-markup-validator so probably should also orphan them
as well. There are also some other packages like dspam that were great
at the time and I used to use them but they don't get much if any
development anymore and I don't run mail servers anymore.

The are as follows:

dspam
html401-dtds
perl-Config-General
perl-HTML-Encoding
perl-HTML-Tidy
perl-Mail-MBox-MessageParser
perl-Mail-MBox-MboxParser
perl-SGML-Parser-OpenSP
php-pecl-cairo
wkhtmltopdf

I will orphan them sometime next week if someone does want them. That
or retire but I don't know/remember what depends on them.


Sincerely,
-- 
Nathanael
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Intent to retire w3c-markup-validator, perl-HTML-Tidy, tidyp

[Nathanael D. Noblet]

Hello Sérgio,
> 
> 
> perl(HTML::Tidy) is optional for w3c-markup-validator [1] I'd like
> maintain w3c-markup-validator package in Fedora at least for sometime
> ,
> I was looking for a tool like this for some time 
> 
> 
> https://src.fedoraproject.org/rpms/w3c-markup-validator/blob/rawhide/f/w3c-markup-validator.spec#_33
> 


  I've passed ownership on to you. If I recall correctly I also had
taken a handful of perl packages that it depended on. I can't recall
the last time I touched them but I'll look at that list and see if
there are at least comaintainers on them. It has to be at least a
decade since I touched w3c-markup-validator as a user...

Sincerely,
-- 
Nathanael
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: F35 Potential Bugs - Where/What to file against

[Nathanael D. Noblet]

On Sat, 2021-10-16 at 15:40 +, Zbigniew Jędrzejewski-Szmek wrote:
> Try pressing ctrl-alt-f8 to switch to a text console. If the text
> login
> appears, then the issue was most likely in the graphics stack. If
> still
> blank, try pressing ctrl-alt-del. On a text console this should
> result
> in a reboot. If it reboots, you should be able to see logs with
> 'journalctl -b-1'. If it doesn't respond to ctrl-alt-del, then it's a
> kernel driver issue. Further debugging is possible, but let's check
> the
> easy things first.

Yeah, I tried ctrl-alt-{f2, f1} but nothing like f8 so will try that
next time. I did manually tell the system to suspend twice and then
closed the lid and it successfully resumed when I opened the lid the
next time. However I'll see if f8 or rebooting works.

> 
> >   #2 - In F34 Gnome control center -> battery I could choose the
> > laptops power profile (performance, balanced, powersave). This
> > seems to
> > be gone.
> > https://fedoraproject.org/wiki/Changes/Power_Profiles_Daemon
> > seems like its supposed to be supplying this, but systemd says the
> > service is masked. Looks like it is masked by TLP. TLP has the
> > benefit
> > of being able to configure that setting between when on AC and when
> > on
> > BAT which is nice but I'm wondering is it a bug that I can no
> > longer
> > change that setting in gnome control panel? Is this expected
> > behaviour?
> 
> One of the reasons to introduce power-profiles-daemon was the dbus
> API
> that gnome knows how to use. TLP and others do not provide the same
> API. power-profiles-daemon.service conflicts with tlp.service,
> probably
> because they'd both try to set the same settings. So if you want
> p-p-d.service, then make sure it is enabled and disable tlp.service.
> 

Right, that's kinda what I'm wondering though. I may have originally
installed tlp but don't recall. To be clearer about what I'm asking
about is, if p-p-d is the new default (and using this laptop with F34
had the options in control center). Why is p-p-d masked? Should it be?
how come the power options were available in gnome-control-center in
F34 when presumably both services existed there as well? Basically, it
was there in F34 and now its gone, but I'm told p-p-d is default in F35
so why did the option disappear and is it a bug?

-- 
Nathanael
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

F35 Potential Bugs - Where/What to file against

[Nathanael D. Noblet]

Hello,

  I recently updated from F34 to F35 on an MSI laptop. I've noticed two
'regressions' and I'm not sure where to file bugs.

  #1 - The first one is if I close the lid and the device suspends (I
assume as it used to do this fine), when I re-open the lid, the
keyboard lights up, fans start, but the screen never turns on and I
don't know if the device is running and the screen is blank or if its
just not waking up. Is this a kernel/systemd bug? What steps/info is
required to file a bug here?

  #2 - In F34 Gnome control center -> battery I could choose the
laptops power profile (performance, balanced, powersave). This seems to
be gone. https://fedoraproject.org/wiki/Changes/Power_Profiles_Daemon
seems like its supposed to be supplying this, but systemd says the
service is masked. Looks like it is masked by TLP. TLP has the benefit
of being able to configure that setting between when on AC and when on
BAT which is nice but I'm wondering is it a bug that I can no longer
change that setting in gnome control panel? Is this expected behaviour?

Otherwise the upgrade has gone well.

Sincerely,
-- 
Nathanael
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Donate 1 minute of your time to test upgrades from F34 to F35

[Nathanael D. Noblet]

On Tue, 2021-09-07 at 18:14 +0200, Miroslav Suchý wrote:
>  Do you want to make Fedora 35 better? Please spend 1 minute of your
> time and try to run:
>  
>  # Run this only if you use default Fedora modules
>  # next time you run any DNF command default modules will be enabled
> again
>  sudo dnf module reset '*'
>  
> sudo dnf --releasever=35 --setopt=module_platform_id=platform:f35 \
> --enablerepo=updates-testing --enablerepo=updates-testing-modular \
>  distro-sync
>  
> This command does not replace `dnf system-upgrade`, but it will reveal
> potential problems.
> You may also run `dnf upgrade` before running this command.
Error: 
 Problem: package ant-apache-log4j-1.10.9-2.fc34.noarch requires ant =
1.10.9-2.fc34, but none of the providers can be installed
  - ant-1.10.9-2.fc34.noarch does not belong to a distupgrade
repository
  - problem with installed package ant-apache-log4j-1.10.9-
2.fc34.noarch
(try to add '--skip-broken' to skip uninstallable packages)


I removed ant-apache-log4j - nothing else was removed at the same time.
Should I be reporting an issue?


>  
>  If you get this prompt:
>  
>  ...
>  Total download size: XXX M
>  Is this ok [y/N]:
>  
>  you can answer N and nothing happens, no need to test the actual
> upgrade.
>  
> But very likely you get some dependency problem now. In that case,
> please report it against the appropriate package.
> Or against fedora-obsolete-packages if that package should be removed
> in Fedora 35. Please check existing reports against
> fedora-obsolete-packages first:
>  https://red.ht/2kuBDPu
> 
> and also there is already bunch of "Fails to install"
> (F35FailsToInstall) reports:
> https://bugzilla.redhat.com/buglist.cgi?bug_id=1927313_id_type=anddependson=tvp_id=12125305#
>  
>  Thank you
>  Miroslav
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
> Do not reply to spam on the list, report it:
> https://pagure.io/fedora-infrastructure

___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Donate 1 minute of your time to test upgrades from F33 to F34

[Nathanael D. Noblet]

On Sat, 2021-02-20 at 10:49 +0100, Miroslav Suchý wrote:
> Do you want to make Fedora 34 better? Please spend 1 minute of your
> time and try to run:
> 
>    # Run this only if you use default Fedora modules
>    # next time you run any DNF command default modules will be enabled
> again
>    sudo dnf module reset '*'
> 
>    sudo dnf --releasever=34 --setopt=module_platform_id=platform:f34 \
>  --enablerepo=updates-testing --enablerepo=updates-testing-modular
> \
>  distro-sync

Looks like I still have the empathy package (I do actually still use it
) but learned today it was retired/orphaned/obsoleted awhile ago. Any
idea why its still on my system?

Fedora Modular 34 - x86_64 - Updates 45 kB/s |  13 kB
Fedora Modular 34 - x86_64 - Test Updates79 kB/s |  13 kB
Fedora 34 - x86_64 - Test Updates73 kB/s |  13 kB
Fedora 34 - x86_64 - Updates 78 kB/s |  13 kB
Errors during downloading metadata for repository 'noblet':
  - Status code: 404 for
https://yum.noblet.ca/fedora/34/x86_64/repodata/repomd.xml (IP:
144.217.182.3)
Error: Failed to download metadata for repo 'noblet': Cannot download
repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried
Ignoring repositories: noblet
Error: 
 Problem: package empathy-1:3.12.14-7.fc29.x86_64 requires
libfolks.so.25()(64bit), but none of the providers can be installed
  - folks-1:0.14.0-5.fc33.x86_64 does not belong to a distupgrade
repository
  - problem with installed package empathy-1:3.12.14-7.fc29.x86_64
(try to add '--skip-broken' to skip uninstallable packages)


___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Ars claims: Fedora 32 is sluggish

[Nathanael D. Noblet]

On Thu, 2021-02-04 at 13:25 -0500, Matthew Miller wrote:
> On Thu, Feb 04, 2021 at 10:33:37AM -0700, Nathanael D. Noblet wrote:
> > > I genuinely wonder if this is due to the launch animation. I know
> > > that
> > > subjectively for myself using the Impatience to triple the speed
> > > makes
> > > my desktop feel more snappy.
> > 
> > Sorry, what is 'the Impatience'? How does it improve the desktop
> > performance?
> 
> It is this extension: 
> https://github.com/timbertson/gnome-shell-impatience
> 
> It does not _actually_ improve performance. It gives you a slider
> which can
> be used to double or triple (or whatever) the speed of the
> animations, which
> has — to my easily-tricked brain — the effect of making the desktop
> _seem_
> more responsive. Try it and see if it works for you too!

Oh my goodness that's hilarious and all kinds of awesome. The name of
the extension is great.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: Ars claims: Fedora 32 is sluggish

[Nathanael D. Noblet]

On Wed, 2021-02-03 at 14:48 -0500, Matthew Miller wrote:
> I genuinely wonder if this is due to the launch animation. I know
> that
> subjectively for myself using the Impatience to triple the speed
> makes my
> desktop feel more snappy.

Sorry, what is 'the Impatience'? How does it improve the desktop
performance?

-- 
Nathanael

___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: Ars claims: Fedora 32 is sluggish

[Nathanael D. Noblet]

On Wed, 2021-02-03 at 10:53 -0600, Michael Catanzaro wrote:
> Hi,
> 
> Has anybody investigated Jim Salter's claims that Fedora 32 is slow
> to 
> launch applications? Recent article:
> 
> https://arstechnica.com/gadgets/2021/02/ubuntu-core-20-adds-secure-boot-with-hardware-backed-encryption/
> 
> "in my experience, Fedora 32 is noticeably, demonstrably more
> sluggish 
> to launch applications than Ubuntu is in general."
> 
> Original article:
> 
> https://arstechnica.com/gadgets/2020/05/linux-distro-review-fedora-workstation-32/
> 
> Would be good to know, for starters, whether this difference is real 
> and measurable.

I haven't used Ubuntu in a long time. However I do know that I remember
creating Ubuntu VM a few years ago and was blown away at how fast it
went from grub to a desktop login compared to Fedora. Other than that
Fedora seems fast enough to me. Just a single datapoint...
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: compat-openssl11 vs openssl1.1

[Nathanael D. Noblet]

On Tue, 2020-09-15 at 13:46 -0400, Neal Gompa wrote:
> On Tue, Sep 15, 2020 at 1:36 PM Nathanael D. Noblet 
> > My 2 cents would be consistency. If others disagree, perhaps
> > compat-
> > openssl10 should be renamed to compat-openssl1.0 and obsolete the
> > old
> > compat-openssl10? Its annoying to try to find the magic name
> > something
> > has based on something else... python-foo vs Foo-python etc.
> 
> The compat- prefix is no longer allowed. Instead we should be using
> versioned package names.
> 
> So if we're changing the old one, it'll become openssl1.0 to comply
> with current guidelines.

Yeah, either way I'd 100% say consistency is important. So to clean up
and be consistent I'd suggest the other one is renamed as well.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: compat-openssl11 vs openssl1.1

[Nathanael D. Noblet]

On Tue, 2020-09-15 at 19:26 +0200, Tomas Mraz wrote:
> I've submitted a new compat-openssl11 package for review but it was
> pointed out to me that according to the new format of the naming for
> compat packages it should be named openssl1.1. However there already
> is
> a compat-openssl10 package.
> 
> What is more important? Consistency between those two compat packages
> or strictly following the naming rules for the new package?
> 

My 2 cents would be consistency. If others disagree, perhaps compat-
openssl10 should be renamed to compat-openssl1.0 and obsolete the old
compat-openssl10? Its annoying to try to find the magic name something
has based on something else... python-foo vs Foo-python etc.

Sincerely,
-- 
Nathanael
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: SELinux question

[Nathanael D. Noblet]

On Wed, 2020-06-24 at 12:12 +0200, Iñaki Ucar wrote:
> Thanks, I got [1] and [2] more or less covered thanks to the output
> of
> the SELinux troubleshooter. The missing parts were how to get
> policies
> into a subpackage (and [3] explains this, thanks), and how to write a
> rule just for my script, not for the whole python3 stack, and I'm
> still missing that bit.

So I can't exactly point you to some documents but the link below may
help. The basic idea is you need to label your script and give it a
type and then allow that type to access the type/action its trying to
do. Like the httpd daemon has a type and there are then file types. and
a process running in the httpd_t domain can read files but not talk to
the network for example... Hope that helps.


https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/selinux_users_and_administrators_guide/chap-Security-Enhanced_Linux-SELinux_Contexts

> 
> > [1] https://fedoraproject.org/wiki/SELinux/audit2why
> > [2] https://fedoraproject.org/wiki/SELinux/audit2allow
> > [3] https://fedoraproject.org/wiki/SELinux/IndependentPolicy
> 
> -- 
> Iñaki Úcar
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct: 
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: 
> https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: A few questions about a package update / policy questions / GCC 9 error

[Nathanael D. Noblet]

On Thu, 2020-06-11 at 16:13 -0400, Simo Sorce wrote:
> I wish this was easier done than said :)

Yeah, this isn't *my* project, I just packaged it. 

Thank you to everyone who added suggestions to dealing with the C code.
I'll take a look and see what upstream thinks about it.

I am wondering if anyone has thoughts about changing the sysconfig
file.

Sincerely,
-- 
Nathanael
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

A few questions about a package update / policy questions / GCC 9 error

[Nathanael D. Noblet]

Hello,

  I maintain beanstalkd which is a message server of sorts. It recently
released a new version however some changes I'm not 100% sure about.

  When compiling I got the following GCC error.

usr/include/bits/string_fortified.h:106:10: error: '__builtin_strncpy'
specified bound 201 equals destination size [-Werror=stringop-
truncation]
  106 |   return __builtin___strncpy_chk (__dest, __src, __len, __bos
(__dest));
  |  ^~


Results via google says that strncpy needs to have the third argument
less than the 2nd, so I've got this patch, similar to others:

--- beanstalkd-1.12/tube.c.org  2020-06-10 09:37:35.129224346 -0600
+++ beanstalkd-1.12/tube.c  2020-06-10 09:37:42.761138035 -0600
@@ -12,7 +12,7 @@
 if (!t)
 return NULL;

-strncpy(t->name, name, MAX_TUBE_NAME_LEN);
+strncpy(t->name, name, MAX_TUBE_NAME_LEN-1);
 if (t->name[MAX_TUBE_NAME_LEN - 1] != '\0') {
 t->name[MAX_TUBE_NAME_LEN - 1] = '\0';
 twarnx("truncating tube name");

You'll notice it was already checking the len-1 for null. Can anyone
verify that my change won't cause some un-intended bug I don't
understand?

Finally, they also now support socket activation. Which means I was
looking at .service file which I had setup to use a sysconfig
environment file. When I looked at it, I realized that the default was
to listen to 0.0.0.0 which means someone could install and if not
really careful / pre config or what not have a service listening where
they maybe don't want to. I was thinking of changing this to 127.0.0.1
with a note about how it should be modified. However I figure if I do
that, anyone with this installed and unmodified who gets the update
will suddenly have their service stop listening to the outside world.
What should be done then? 

My thought is I leave it as 0.0.0.0 for all released versions (but what
about epel7) and then in rawhide change to 127.0.0.1. I just don't like
leaving the package like that for epel as well.

Any ideas/direction would be appreciated.

Sincerely,
-- 
Nathanael

___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: Firewalld/nftable/libvirt...

[Nathanael D. Noblet]

On Fri, 2020-05-08 at 22:08 +0200, Igor Raits wrote:
> 
> I would guess that some ip_forward or something like this is not set.
> I'd report this against firewalld component on 
> https://bugzilla.redhat.com.
> 

Thanks Igor,

  In attempting to file the bug I found that a bug has been filed
already. https://bugzilla.redhat.com/show_bug.cgi?id=1832723.

Much appreciated.
-- 
Nathanael
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Firewalld/nftable/libvirt...

[Nathanael D. Noblet]

Hello,

  I upgraded to F32 Beta, and then final when it came out. In the last
few days I've got an issue that I'm 99% sure I'm not the cause of but I
don't know what component to report it on.

  I've had this workstation for years and it has a number of VMs that I
manage with virt-manager/libvirt. eth0 is part of a bridge, "bridge0"
every VM uses that bridge as its network interface to get an IP on my
local network. It has worked like this for years, upgrading sometimes
messed up the bridge configuration. This upgrade there were no issues
until recently. 

  Now my VMs can't get an IP address via DHCP unless I temporarily stop
firewalld. I wondered if it was the change from iptables to nftables.
However I changed it to use iptables and that didn't fix it.

  So, seeing as I didn't change the firewall rules and I don't know why
this is no longer working I'm kinda thinking its a bug but not sure
where to report it? 

Thoughts?
-- 
Nathanael
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: Compilation Error on F32

[Nathanael D. Noblet]

On Mon, 2020-03-30 at 13:47 -0600, Nathanael D. Noblet wrote:
> Thank you for looking into this for me. Just to be clear, the proper
> place to fix this is in the php-cpp project because it is using
> std::runtime_exception without including . Is that
> correct?

Aaaand I just tried it and it works so thanks again!
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: Compilation Error on F32

[Nathanael D. Noblet]

On Mon, 2020-03-30 at 20:55 +0200, Jakub Jelinek wrote:
> So, from the offlist posted preprocessed source, seems the TU
> includes the
> following libstdc++ headers
> #include 
> #include 
> #include 
> #include 
> #include 
> #include 
> #include 
> and then uses std::runtime_exception.  That one is defined in
> 
> header though, and is not included.  Before
> https://gcc.gnu.org/legacy-ml/libstdc++/2019-06/msg00032.html
> change it has been included as implementation detail from headers
> included
> in ,  or  from the above list.
> So, you just need to make sure  is also included if you
> need
> classes from it.
> 

Thank you for looking into this for me. Just to be clear, the proper
place to fix this is in the php-cpp project because it is using
std::runtime_exception without including . Is that correct?

Sincerely,
-- 
Nathanael
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: Coronavirus: Fedora RTC solutions and YOU

[Nathanael D. Noblet]

On Mon, 2020-03-30 at 14:09 -0400, Neal Becker wrote:
> Sérgio Basto wrote:
> 
> Before jumping into jitsi, I think you should see what I got when I
> tried it 
> using the web app.
> 
> Why does it want access to my youtube??

I've used Jitsi without an account at all for over a year (at least the
one at meet.jit.si - so my guess is that is a configuration option?


___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: Coronavirus: Fedora RTC solutions and YOU

[Nathanael D. Noblet]

On Mon, 2020-03-30 at 18:09 +0200, Dario Lesca wrote:
> Il giorno sab, 28/03/2020 alle 15.13 +, Sérgio Basto ha scritto:
> > I will try packaging all Jitsi Meet suite [1] 

Me too, I've been watching that suite of tools and would love to be a
little involved as potentially a co-maintainer but definitely a
tester...
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Compilation Error on F32

[Nathanael D. Noblet]

Hello,

  I have a project that isn't part of Fedora yet - though really I
should add it at this point. Its php-cpp. It allows me to write c++
extensions for PHP. Its worked well for a couple years. I upgraded to
F32 beta and now when compiling anything that includes its headers
compilation fails and I'm not entirely sure why. 

g++ -MT pdf-image.o -MMD -MP -MF .d/pdf-image.Td -Wall -g -c -O2
-std=c++11 -fPIC `pkg-config poppler-cpp fontconfig openssl --
cflags`-DVERSION=\"0.11.16\"  -c -o pdf-image.o pdf-image.cpp
In file included from /usr/include/phpcpp.h:38,
 from pdf-image.cpp:8:
/usr/include/phpcpp/throwable.h:29:1: error: expected class-name before
‘{’ token

I've attached the header. Any gcc experts out there able to tell me
what's wrong with the header format that used to compile but no longer
does?

In case it is relevant PHPCPP_EXPORT has the following definition:
#define PHPCPP_EXPORT __attribute__ ((visibility ("default")))

Sincerely,
-- 
Nathanael
/**
 *  Throwable.h
 *
 *  Base class for exceptions and errors, where an error is a runtime
 *  problem with the program (like file-does-not-exist), and an error
 *  is a more fatal programming problem (like call-to-private-method).
 *
 *  @author Jasper van Eck 
 *  @author Emiel Bruijntjes 
 *  @copyright 2013 - 2019 Copernica BV
 */
#include 
#include 

/**
 *  Forward declarations
 */
struct _zend_object;

/**
 *  Set up namespace
 */
namespace Php {

/**
 *  Class definition
 */
class PHPCPP_EXPORT Throwable : public std::runtime_error
{
protected:
/**
 *  The exception code
 *  @var long int
 */
long int _code = -1;


protected:
/**
 *  Protected constructor - only derived classes can instantiate
 *  @param  message The exception message
 */
Throwable(const std::string ) : std::runtime_error(message) {}

/**
 *  Another protected constructor
 *  @param  object
 */
Throwable(struct _zend_object *object);

public:
/**
 *  Destructor
 */
virtual ~Throwable() = default;

/**
 *  Rethrow the exception / make sure that it ends up in PHP space
 */
virtual void rethrow() = 0;
 
/**
 *  Returns the exception code
 *  @return The exception code
 */
long int code() const _NOEXCEPT
{
// expose the code
return _code;
}
};

/**
 *  End of namespace
 */
}
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

F32 selinux denials

[Nathanael D. Noblet]

Hello,

  I upgraded to F32 yesterday and everything seems to have gone
smoothly except I'm getting many selinux denials (I'm in permissive so
functionality is ok at the moment). What should I report them against?
I've done a relabel to try to resolve them.

A sample of the most common:

SELinux is preventing /usr/lib/systemd/systemd-journald from read
access on the lnk_file /run/user/1000/systemd/units/invocation:dbus-:
1.2-org.fedoraproject.Setroubleshootd@1.service.

SELinux is preventing pcscd from using the sys_nice capability.

SELinux is preventing accounts-daemon from using the sys_nice
capability.

Sincerely,
-- 
Nathanael
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: Donate 1 minute of your time to test upgrades from F31 to F32

[Nathanael D. Noblet]

On Wed, 2020-03-04 at 16:24 +0100, Miroslav Suchý wrote:
> 
> But very likely you get some dependency problem now. In that case,
> please report it against the appropriate package. Or
> against fedora-obsolete-packages if that package should be removed in
> Fedora 32. Please check existing reports first:
> https://red.ht/2kuBDPu
> 
[gnat@iridium ~]$ sudo dnf --releasever=32 --
setopt=module_platform_id=platform:f32 --enablerepo=updates-testing 
--enablerepo=updates-testing-modular distro-sync
Last metadata expiration check: 0:01:26 ago on Wed 04 Mar 2020 09:13:44
AM MST.
Error: 
 Problem: package system-config-keyboard-1.4.0-18.fc31.noarch requires
python2-newt, but none of the providers can be installed
  - python2-newt-0.52.21-2.fc31.x86_64 does not belong to a distupgrade
repository
  - problem with installed package system-config-keyboard-1.4.0-
18.fc31.noarch


If I'm reading that correctly system-config-keyboard is requiring a
python2 package. Is system-config-keyboard supposed to be obsolete?
Seems like probably not but I'm not sure what to do here.

-- 
Nathanael
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Intent to Orphan/Retire dspam

[Nathanael D. Noblet]

Hello,

  Years ago I was managing mail servers and really liked dspam's
accuracy and resource consumption so added it to fedora and maintained
it. Sadly shortly after adding it upstream went through a number of
ownership changes and nothing has been added to it in years. I no
longer use it, upstream is essentially dead and it is now FTBS in F32.

  I'm planning on orphaning it unless someone wants it.

Sincerely,
-- 
Nathanael
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: Donate 1 minute of your time to test upgrades from F30 to F31

[Nathanael D. Noblet]

On Fri, 2019-09-13 at 06:23 +, Zbigniew Jędrzejewski-Szmek wrote:
> On Thu, Sep 12, 2019 at 02:47:20PM -0600, Nathanael D. Noblet wrote:
> > Is this an error with gegl03?
> 
> https://bugzilla.redhat.com/show_bug.cgi?id=1703828
> 

The update there seems to have fixed the issue and I now get to the y/n
prompt successfully.

Sincerely,
-- 
Nathanael

___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: Donate 1 minute of your time to test upgrades from F30 to F31

[Nathanael D. Noblet]

I've since run

sudo dnf module reset eclipse

Which results in the following error when trying a distro-sync.

 Problem: conflicting requests
  - nothing provides module(eclipse) needed by module
jmc:latest:3120190813124555:7188e41a-0.x86_64
Error: 
 Problem: package gegl03-0.3.30-5.fc30.x86_64 requires libIlmImf-
2_2.so.22()(64bit), but none of the providers can be installed
  - OpenEXR-libs-2.2.0-16.fc30.x86_64 does not belong to a distupgrade
repository
  - problem with installed package gegl03-0.3.30-5.fc30.x86_64
(try to add '--skip-broken' to skip uninstallable packages)

Is this an error with gegl03?

Sincerely,
-- 
Nathanael


___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: Donate 1 minute of your time to test upgrades from F30 to F31

[Nathanael D. Noblet]

Hello,

  I had a few problems. To clear some I had to run.

sudo dnf module reset libgit2

  This resulted in the rest of the errors.

Modular dependency problems:

 Problem 1: conflicting requests
  - nothing provides module(platform:f30) needed by module
eclipse:2019-06:3020190807134759:6ebe2c0f-0.x86_64
 Problem 2: module jmc:latest:3120190813124555:7188e41a-0.x86_64
requires module(eclipse), but none of the providers can be installed
  - conflicting requests
  - nothing provides module(platform:f30) needed by module
eclipse:2019-06:3020190807134759:6ebe2c0f-0.x86_64
Error: 
 Problem: package gegl03-0.3.30-5.fc30.x86_64 requires libIlmImf-
2_2.so.22()(64bit), but none of the providers can be installed
  - OpenEXR-libs-2.2.0-16.fc30.x86_64 does not belong to a distupgrade
repository
  - problem with installed package gegl03-0.3.30-5.fc30.x86_64
(try to add '--skip-broken' to skip uninstallable packages)


I used to use eclipse but no longer do so I'm unsure as to the actually
issue here. Nor do I know what is actually the problem with the
potential upgrade.

Sincerely,
-- 
Nathanael

___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: Compiling with AddressSanitizer

[Nathanael D. Noblet]

On Thu, 2019-07-18 at 10:25 +0200, Florian Weimer wrote:
> * Nathanael Noblet:
> 
> >I have been using a library for awhile now and have been
> > thinking
> >of submitting it to Fedora. Part of what I have been doing with
> > it
> >was compiling it using -fsanitize=address and leak etc. I’m
> > kinda
> >wondering about how that is handled with Fedora packages. Are we
> >able to / should we provide library package versions that are
> >compiled against these kinds of sanitizers?
> 
> Address Sanitizer does not provide ABI stability itself, and also
> removes ABI stability for glibc functions.  In general, you cannot
> use it for distribution builds.

Right, I think I didn't communicate it clearly. What I meant was having
like libfoo and libfoo-sanitized or something like that that conflict
with each other so you could install libfoo-sanitized for debug
purposes. It seems that the answer is likely no need to do it.

> 
> >Or if someone wants to do that they should recompile the RPM
> > with
> >those flags and use it locally?
> 
> Yes, rebuilding the RPM or the upstream sources is currently the only
> way.
> 
> Thanks,
> Florian

___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: F29 Self-Contained Change: GnuTLS enables TLS 1.3 by default

[Nathanael D. Noblet]

On Fri, 2018-10-05 at 17:14 +0200, mcatanz...@gnome.org wrote:
> On Fri, Oct 5, 2018 at 4:54 PM, Nathanael D. Noblet <
> nathan...@gnat.ca> wrote:
> > Ok, so should I be filing a bug and if so against which component?
> > I
> > wasn't sure if the google online accounts part of GNOME used GnuTLS
> > or
> > not.
> 
> It uses glib-networking, which does use GnuTLS. glib-networking
> already enables SNI (off the top of my head, in
> GTlsClientConnectionGnutls.c), so some further debugging is going to
> be required here to see if indeed it's true that the SNI extension is
> not being sent for some reason.

Ok, I can help with the debugging if needed. I just didn't know what
stack this was built on. Let me know if/what you'd like me to do.

-- 
Nathanael

___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: F29 Self-Contained Change: GnuTLS enables TLS 1.3 by default

[Nathanael D. Noblet]

On Thu, 2018-10-04 at 21:33 +0200, Michael Schwendt wrote:
> 
> Yes. If Google hands out certificates for other secure services in
> the
> same way as it does on its IMAP servers, any other TLS based client
> will
> need to be developed further.

Ok, so should I be filing a bug and if so against which component? I
wasn't sure if the google online accounts part of GNOME used GnuTLS or
not.

-- 
Nathanael


___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: F29 Self-Contained Change: GnuTLS enables TLS 1.3 by default

[Nathanael D. Noblet]

On Sat, 2018-09-22 at 22:32 +0200, Michael Schwendt wrote:
> On Wed, 18 Jul 2018 17:26:06 -0400, Ben Cotton wrote:
> 
> > This change enables TLS 1.3 (draft28) support on the gnutls crypto
> > library.
> > == Upgrade/compatibility impact ==
> > That change should have no impact on upgrade or compatibility. The
> > TLS
> > 1.3 protocol is designed in a way that does not cause
> > incompatibility
> > issues with existing (and even broken) implementations.
> > == User Experience ==
> > That change should not be noticeable by users except for
> > applications
> > which report the connected protocol.
> 
> Apparently, this change breaks Google Mail IMAP for Claws Mail.
> https://bugzilla.redhat.com/1629151

I get what I think is a similar error with the google 'Online accounts'

I get a certificate error. The message is:

"No SNI provided; please fix your client."

Would this be a related issue?

___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: poppler soname bump in rawhide

[Nathanael D. Noblet]

On Mon, 2018-08-20 at 11:17 -0600, Nathanael D. Noblet wrote:
> On Tue, 2018-08-14 at 02:31 +0200, Marek Kasik wrote:
> > Hi,
> > 
> > I'm going to rebase poppler in rawhide to poppler-0.67.0 now.
> 
> Just in case you weren't aware.. They release 0.68 yesterday with
> some
> security fixes. Not sure if the API changed or anything like that as
> their changelog is pretty terse.

Looks like it changed from libpoppler.so.79 from so.78...

___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/PT4TF4G6CDR5ETVCHGKVBLFLY2H5FKLG/

Re: poppler soname bump in rawhide

[Nathanael D. Noblet]

On Tue, 2018-08-14 at 02:31 +0200, Marek Kasik wrote:
> Hi,
> 
> I'm going to rebase poppler in rawhide to poppler-0.67.0 now.

Just in case you weren't aware.. They release 0.68 yesterday with some
security fixes. Not sure if the API changed or anything like that as
their changelog is pretty terse.



___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/E6IESTBQFUFUIEN5DVTXZAEQKQJHU7F5/

Re: Release criteria proposal: installing / removing software

[Nathanael D. Noblet]

On Mon, 2018-07-16 at 17:32 -0700, Adam Williamson wrote:
> 
> Basic:
> 
> "The installed system must be able appropriately to install, remove,
> and update software with the default console tool for the relevant
> software type (e.g. default console package manager). This includes
> downloading of packages to be installed/updated."
> 

Just a small typo/grammar correction I think. 

"The installed system must be able to appropriately install, remove,
and update.." 

just moved the 'to' infront of appropriately.. Apologies if that's a
dumb thing to nit-pick. Otherwise looks good to me.

-- 
Nathanael
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/LV3V7R5WKHJZYOGZ4BEIQIAJCXLL4SRW/

Re: [ACTION NEEDED] Missing BuildRequires: gcc/gcc-c++

[Nathanael D. Noblet]

On Mon, 2018-02-26 at 11:09 +0100, Igor Gnatenko wrote:
> On Mon, 2018-02-26 at 10:47 +0100, Vít Ondruch wrote:
> > Will you be doing such rebuild every weekend to track the progress?
> > ;)
> 
> My plan is to do this bi-weekly ;) So this weekend then.

Hello,

  So I made a fix for clamsmtp, and pushed it to master. However its in
your list with the error:

clamsmtp:/mnt/koji/work/tasks/4870/64870/build.log:checking for cc...
no

Here's the latest change (minus release bump and changelog) I had made
to the spec file:

diff --git a/clamsmtp.spec b/clamsmtp.spec
index 4ed326e..776b0d8 100644
-BuildRequires:  clamav-devel
-BuildRequires:  systemd-units
+BuildRequires:  clamav-devel gcc gcc-c++ systemd-units
+
 Requires(pre):  shadow-utils
 Requires(post): systemd-sysv


What did I do wrong/miss?

-- 
Nathanael

> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: [ACTION NEEDED] Missing BuildRequires: gcc/gcc-c++

[Nathanael D. Noblet]

On Wed, 2018-02-21 at 00:03 +0100, Nils Philippsen wrote:
> On Sun, 2018-02-18 at 18:09 +0100, Igor Gnatenko wrote:
> > List of packages and respective maintainers:
> > https://ignatenkobrain.fedorapeople.org/gcc-removal-pkgs.txt
> > nphilipp   babl dcraw gegl gimp gpsdrive gtick gtkimageview
> > hydrogen

beanstalkd and clamsmtp are done
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: F26 System Wide Change: Enable TRIM pass down to encrypted disks

[Nathanael D. Noblet]

On Fri, 2017-02-03 at 17:32 +0100, Tomasz Torcz wrote:
> > So I've got multiple systems with encrypted partitions on SSD
> > disks.
> > Are there ways of enabling this for pre-existing partitions?
> 
>   I believe putting “discard” at the the of each line in
> /etc/crypttab
> will do the trick.

Nice, Does this apply to encrypted swap partitions?

Also what are the risks of enabling this?

Thanks,
-- 
Nathanael
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: F26 System Wide Change: Enable TRIM pass down to encrypted disks

[Nathanael D. Noblet]

On Fri, 2017-02-03 at 09:40 -0500, Josh Boyer wrote:
> On Mon, Jan 16, 2017 at 10:32 AM, Jan Kurik 
> wrote:
> > = System Wide Change: Enable TRIM pass down to encrypted disks =
> > https://fedoraproject.org/wiki/Changes/EnableTrimOnDmCrypt
> > 
> > Change owner(s):
> > * Vratislav Podzimek 
> > * Ondrej Kozina 
> > 
> > 
> > Override kernel default for dm-crypt mappings of LUKS1 encrypted
> > volumes via flag put in /etc/crypttab file. This change should
> > affect
> > only newly created encrypted storage based on LUKS1 format during
> > installation.

So I've got multiple systems with encrypted partitions on SSD disks.
Are there ways of enabling this for pre-existing partitions?

___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: Docker/Libvirt networking issue / bug?

[Nathanael D. Noblet]

On Thu, 2016-10-06 at 14:02 -0500, Dan Williams wrote:
> 
> Try running 'iptables-save' before you start docker, and then running
> 'iptables-save' after.  Diff the results.  Did docker remove
> anything?

Hello,

  So this seems to be the source of the problem but I'm a little out of
my depth to all its doing.

So I've attached three files

[1] iptables.onBoot (which is iptables after a clean boot)
[2] iptables.afterDockerService (which is iptables after systemctl
start docker)
[3] iptables.diff ( the difference between the two files where I've
removed differences that don't matter like packet counts etc).

So this seems like docker doesn't play well with libvirtd? Should I be
filing a bug on docker? Or is this just a mis-configuration on my part?
I don't think I've changed either libvirtd/qemu or docker's default
configuration. Other than my VMs all attach to bridge0 instead of using
NAT.

I'll start looking up what the -m addrtype --dst-type LOCAL does and
all the docker related rules that are added but I'm really not sure
what's going on. Particularly since VMs that are running and network
connected when before I run a docker container continue to be. Only VMs
brought up after that aren't. Also at a minimum if I stop the docker
service I would expect these rules to go away which they don't. For
example after systemctl stop docker I still have docker0 bridge
interface up and 

[gnat@iridium ~]$ sudo iptables -L -n | grep DOCKER
DOCKER-ISOLATION  all  --  0.0.0.0/00.0.0.0/0   
DOCKER all  --  0.0.0.0/00.0.0.0/0   
Chain DOCKER (1 references)
Chain DOCKER-ISOLATION (1 references)

still shows the chains are in place...# Generated by iptables-save v1.6.0 on Fri Oct 14 14:49:48 2016
*nat
:PREROUTING ACCEPT [25:1604]
:INPUT ACCEPT [0:0]
:OUTPUT ACCEPT [126:9336]
:POSTROUTING ACCEPT [126:9336]
:DOCKER - [0:0]
:OUTPUT_direct - [0:0]
:POSTROUTING_ZONES - [0:0]
:POSTROUTING_ZONES_SOURCE - [0:0]
:POSTROUTING_direct - [0:0]
:POST_FedoraWorkstation - [0:0]
:POST_FedoraWorkstation_allow - [0:0]
:POST_FedoraWorkstation_deny - [0:0]
:POST_FedoraWorkstation_log - [0:0]
:POST_dmz - [0:0]
:POST_dmz_allow - [0:0]
:POST_dmz_deny - [0:0]
:POST_dmz_log - [0:0]
:POST_trusted - [0:0]
:POST_trusted_allow - [0:0]
:POST_trusted_deny - [0:0]
:POST_trusted_log - [0:0]
:PREROUTING_ZONES - [0:0]
:PREROUTING_ZONES_SOURCE - [0:0]
:PREROUTING_direct - [0:0]
:PRE_FedoraWorkstation - [0:0]
:PRE_FedoraWorkstation_allow - [0:0]
:PRE_FedoraWorkstation_deny - [0:0]
:PRE_FedoraWorkstation_log - [0:0]
:PRE_dmz - [0:0]
:PRE_dmz_allow - [0:0]
:PRE_dmz_deny - [0:0]
:PRE_dmz_log - [0:0]
:PRE_trusted - [0:0]
:PRE_trusted_allow - [0:0]
:PRE_trusted_deny - [0:0]
:PRE_trusted_log - [0:0]
-A PREROUTING -j PREROUTING_direct
-A PREROUTING -j PREROUTING_ZONES_SOURCE
-A PREROUTING -j PREROUTING_ZONES
-A PREROUTING -m addrtype --dst-type LOCAL -j DOCKER
-A OUTPUT -j OUTPUT_direct
-A OUTPUT ! -d 127.0.0.0/8 -m addrtype --dst-type LOCAL -j DOCKER
-A POSTROUTING -s 172.17.0.0/16 ! -o docker0 -j MASQUERADE
-A POSTROUTING -s 192.168.121.0/24 -d 224.0.0.0/24 -j RETURN
-A POSTROUTING -s 192.168.121.0/24 -d 255.255.255.255/32 -j RETURN
-A POSTROUTING -s 192.168.121.0/24 ! -d 192.168.121.0/24 -p tcp -j MASQUERADE 
--to-ports 1024-65535
-A POSTROUTING -s 192.168.121.0/24 ! -d 192.168.121.0/24 -p udp -j MASQUERADE 
--to-ports 1024-65535
-A POSTROUTING -s 192.168.121.0/24 ! -d 192.168.121.0/24 -j MASQUERADE
-A POSTROUTING -j POSTROUTING_direct
-A POSTROUTING -j POSTROUTING_ZONES_SOURCE
-A POSTROUTING -j POSTROUTING_ZONES
-A DOCKER -i docker0 -j RETURN
-A POSTROUTING_ZONES -o em1 -g POST_dmz
-A POSTROUTING_ZONES -o bridge0 -g POST_dmz
-A POSTROUTING_ZONES -o virbr0 -j POST_trusted
-A POSTROUTING_ZONES -o virbr0-nic -j POST_trusted
-A POSTROUTING_ZONES -g POST_FedoraWorkstation
-A POSTROUTING_ZONES_SOURCE -d 192.168.121.0/24 -g POST_dmz
-A POSTROUTING_ZONES_SOURCE -d 192.168.4.0/24 -g POST_dmz
-A POST_FedoraWorkstation -j POST_FedoraWorkstation_log
-A POST_FedoraWorkstation -j POST_FedoraWorkstation_deny
-A POST_FedoraWorkstation -j POST_FedoraWorkstation_allow
-A POST_dmz -j POST_dmz_log
-A POST_dmz -j POST_dmz_deny
-A POST_dmz -j POST_dmz_allow
-A POST_trusted -j POST_trusted_log
-A POST_trusted -j POST_trusted_deny
-A POST_trusted -j POST_trusted_allow
-A PREROUTING_ZONES -i em1 -g PRE_dmz
-A PREROUTING_ZONES -i bridge0 -g PRE_dmz
-A PREROUTING_ZONES -i virbr0 -j PRE_trusted
-A PREROUTING_ZONES -i virbr0-nic -j PRE_trusted
-A PREROUTING_ZONES -g PRE_FedoraWorkstation
-A PREROUTING_ZONES_SOURCE -s 192.168.121.0/24 -g PRE_dmz
-A PREROUTING_ZONES_SOURCE -s 192.168.4.0/24 -g PRE_dmz
-A PRE_FedoraWorkstation -j PRE_FedoraWorkstation_log
-A PRE_FedoraWorkstation -j PRE_FedoraWorkstation_deny
-A PRE_FedoraWorkstation -j PRE_FedoraWorkstation_allow
-A PRE_dmz -j PRE_dmz_log
-A PRE_dmz -j PRE_dmz_deny
-A PRE_dmz -j PRE_dmz_allow
-A PRE_trusted -j PRE_trusted_log
-A PRE_trusted -j PRE_trusted_deny
-A PRE_trusted -j PRE_trusted_allow

Re: Docker/Libvirt networking issue / bug?

[Nathanael D. Noblet]

On Thu, 2016-10-06 at 14:28 -0400, Neil Horman wrote:
> I rarely mess with docker, but I expect that the docker0 bridge has
> an ip
> address on it which may conflict with the one on libvirt
> bridge.  That is to
> say, if they are on the same subnet, and the route for the docker0
> bridge takes
> precidence, you will loose dhcp.  Check the docker bridge ip and
> remove it if
> you see one, I expect that will restore your functionality
> 

Unfortunately that isn't the issue as the docker bridge is 172... and
bridge0 is 192.168... so they don't conflict. Also docker0 doesn't seem
to have any devices (meaning it brctl show has no interfaces attached
to it). Finally shutting down docker and removing docker0 doesn't
restore connectivity, only a reboot does. Not even restarting NM fixes
the issue.

-- 
Nathanael
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Docker/Libvirt networking issue / bug?

[Nathanael D. Noblet]

Hello,

  I have an issue that likely needs a bug or something to fix but I'm
not sure which component is at fault. So I'm writing here in the hopes
that someone will know where to point me.

  I have a F24 Workstation where I've been using libvirt/qemu VMs for
development for awhile now. It works great. I have a bridge0 that
bridges all VMs and my main NIC so that the VMs are accessible on the
network. That works well too.

  Recently I started playing with docker. Both times after running a
few docker containers (with no defined networking / portmapping etc)
just a bash shell in the container. My VMs are no longer able to get IP
addresses from the router. They just time out. It has happened twice
this week and both times it happens sometime after I've done something
with docker. 

  I haven't done any custom configuration with docker so from what I
understood the docker daemon listens on a unix socket, however there is
a docker0 bridge that comes up (and doesn't go away when I stop the
docker service).

  Any VM that was up and running and connected to the network continues
to be. Any VM that I bring up after docker (if it is actually docker's
fault) can no longer get an IP. Stopping the docker service, bringing
down the docker0 bridge in no way fixes the issue. The only way I've
been able to fix it is to reboot the workstation. Once I do that then
the VMs are able to get IPs again.

  Where do I start looking/debugging this?

Thanks,
-- 
Nathanael
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: On packager motivation

[Nathanael D. Noblet]

On Wed, 2016-02-03 at 08:44 -0700, Jerry James wrote:
> I know a number of companies have experimented with "ownership-free"
> models of code development, but they are able to offer incentives
> that
> Fedora cannot offer, such as money and kudos offered in front of
> coworkers.  What motivates volunteer packagers to do what they do?
> I'd like to hear from a few packagers on this topic.

I can't speak to the rest of the issues you've experienced as I haven't
so far. I became a packager because software I was using on some of our
systems weren't in Fedora/EPEL. I was using them and building them and
figured, 
a) I've always wanted to contribute to FOSS but haven't really been
able to yet. 
b) These are packages that I already have to deal with, might as well
have them in the distro to make life easier and provide them for
others.

Since that first package I'm the point of contact for a mere 12
packages and co-maintainer of 3. Each of those because I was using
something and needed newer versions or what have you. Looking at the
list, there are a number of dependencies on a package I'm the
maintainer of but no longer actively use, however it doesn't change
much so why not keep at it.

--
devel mailing list
devel@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org

Re: Needless use of %defattr (in 4464 packages)

[Nathanael D. Noblet]

On Mon, 2016-01-25 at 16:34 -0600, Jason L Tibbitts III wrote:

> beanstalkd (jjh, gnat)

removed defattr.


-- 
Nathanael
--
devel mailing list
devel@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org

Unresponsive Maintainer Question

[Nathanael D. Noblet]

Hello,

  I'm interested in taking over beanstalkd (at least for EPEL) but will
take it for all of fedora as well if the maintainer is completely gone
as opposed to not interested in EPEL. The maintainer in question is
Jeremy Hinegardner, (jjh).

  A bug report requesting the el7 branch be created for beanstalkd on
Sep 2014 [1]. The maintainer didn't respond, however one of the
comments is from someone who said they contacted the maintainer Jeremy
Hinegardner, who said he was no longer active in the EPEL community. 

  The last build by Jeremy was Sep 2013. There is a new release of
beanstalk (1.10) released August 2014.

  I've sent a personal email only two days ago and requested commit
rights on the package. Both have been unanswered.

  I've only started looking at this the last few days however I feel
like its pretty obvious that at least for this package the maintainer
is un-interested. Should I still wait the three weeks or would it be
okay to request ownership through FESCO?


-- 
Nathanael
--
devel mailing list
devel@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org

Re: Unresponsive Maintainer Question

[Nathanael D. Noblet]

On Fri, 2015-12-11 at 11:04 -0700, Nathanael D. Noblet wrote:
> Hello,
> 
>   I'm interested in taking over beanstalkd (at least for EPEL) but
> will
> take it for all of fedora as well if the maintainer is completely
> gone
> as opposed to not interested in EPEL. The maintainer in question is
> Jeremy Hinegardner, (jjh).
> 
>   A bug report requesting the el7 branch be created for beanstalkd on
> Sep 2014 [1]. The maintainer didn't respond, however one of the
> comments is from someone who said they contacted the maintainer
> Jeremy Hinegardner, who said he was no longer active in the EPEL
> community. 

Sorry forgot the bug link.

[1] - https://bugzilla.redhat.com/show_bug.cgi?id=1139358
--
devel mailing list
devel@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org

Re: Announcing the release of Fedora 23 Beta!

[Nathanael D. Noblet]

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:
> 
> * FedUp has gotten a lot of positive press *just recently*, including
> this
>   interview with Jim Whitehurst
>   http://www.mylinuxrig.com/post/129154618674/the-linux-setup-jim-whi
> tehurst-presidentceo
> 
> * Although the mechanisms are different, the basic concepts,
>   especially from a user point of view, are very similar
> 
> * Documentation won't need (as much) updating
> 
> * fedup.sh is already done
> 
> * FedUp is an awesome name
> 
> * People get all stabby over changes. Let's save getting stabbed for
>   when we really need it.
> 
So I noticed a little while ago fedup on my system was replaced by dnf-
plugin-system-upgrade. Running fedup gets you the dnf 'this command is
no longer the one to use use dnf system-upgrade...' I used it and am
running F23 Beta now. It may be too late. One thing though is I
searched for fedup first, found the wiki and it has nothing about using
dnf on it anymore.

Otherwise it seemed to run fine.

It didn't however relabel the system during the upgrade which caused a
few selinux messages. Should it?

-- 
Nathanael
-- 
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: bodhi 2 now live

[Nathanael D. Noblet]

On Wed, 2015-08-19 at 21:45 -0600, Kevin Fenzi wrote:
 Greetings. 
 
 After a longer than expected outage window, I'm happy to report that
 bodhi2 is now live in production at
 
 https://admin.fedoraproject.org/updates
 or
 https://bodhi.fedoraproject.org/

I see in the thread that people seem to be having issues with this.
Just wanted to say that to me it looks nicer and seems to work great.
Nice work everyone who worked on it. I assume it will continue to get
better.


-- 
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: Validity of i686 as a release blocker

[Nathanael D. Noblet]

On Tue, 2015-08-04 at 11:12 -0400, Bill Nottingham wrote:
 Here's my perspective as an i686 Fedora user...
 
 I have a box (2009-ish) that's in use as a file/backup server. As 
 such, I don't
 spend a lot of time futzing with it - it doesn't run rawhide, it 
 rarely runs
 the prereleases until beta or later time.  If something breaks, I'll 
 look at
 it, send some feedback, update it as necessary, and back off to a 
 working
 version.  And historically, it *hasn't* broken.
 
 But, if it did break that hard... would I spend a month digging into 
 the
 kernel source and bisecting to try and find a fix? Or would I spend 
 the
 $100-120 to slap a new motherboard in it and install the x86_64 
 version?
 
 I'd like to say I'd do the former. But realisitically it's the 
 latter. And I
 wonder how much of the i686 Fedora-using community is in the same 
 boat.

So we have a product that is installed on about ~80 netbooks running
i386-PAE kernels. They are now running f21 I think. I considered
updating them but they are offline machines for nearly their entire
life. I had contemplated putting CentOS 7 but there is no i386 for
that. I would imagine that the hardware would be replaced by newer
netbooks that handle x64. If they can't be they'll run EOL'd versions
of fedora till death.  If I can update them eventually it wouldn't
matter to me if the i386 system saw less love but eventually came out.
Granted if fedora dropped i386 completely I'd find a distro to use that
supported it I guess if any. It wouldn't be the end of the world for
me.

-- 
Nathanael


-- 
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: f22 screensaver/lockout issue requiring reboot :/

[Nathanael D. Noblet]

On Wed, 2015-06-10 at 16:39 -0400, Paul Wouters wrote:
  gdm still does not start properly on boot, and when using
 startx once the screen locks, despite disabling screensaver, all I
 can do is reboot.
 

Can you access the machine via ssh?
-- 
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: GNOME 3 bug?

[Nathanael D. Noblet]

On Fri, 2015-05-08 at 09:42 -0600, Nathanael D. Noblet wrote:
 
   So is this a bug? Is there a way to 'reset' gnome settings to
 defaults? Or detect differences between defaults and a user's 
 settings
 that may have caused this? I ask because previously I had window 
 focus
 set to follow the mouse at one point so perhaps a series of non
 -standard settings is causing this.
 
   Finally is this something that I should file a bug on?

Deleting a host of .gnome directories and re-logging in seems to have
fixed the window focus issue at the expense of having lost some other
minor settings.

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

GNOME 3 bug?

[Nathanael D. Noblet]

Hello,

  I updated my F21 workstation to F22 beta. Everything has gone well
except for some bug in GNOME.

  Window focus is messed up. When I click on a window in the
background it gets focus, but doesn't come to the foreground. Only
clicking a window title brings it forward. A side effect of this
behaviour if I click and drag a window that wasn't already the 'top'
most window, it drags it behind all other windows. Makes it difficult
to manage window placement if you can't see it.

  A new user created doesn't have the same issues.

  So is this a bug? Is there a way to 'reset' gnome settings to
defaults? Or detect differences between defaults and a user's settings
that may have caused this? I ask because previously I had window focus
set to follow the mouse at one point so perhaps a series of non
-standard settings is causing this.

  Finally is this something that I should file a bug on?

-- 
Nathanael
-- 
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: Dependency chain issue...

[Nathanael D. Noblet]

On Tue, 2015-02-03 at 05:49 +0100, Kevin Kofler wrote:
 Nathanael d. Noblet wrote:
I have F21 Workstation installed. I installed liveusb-creator and the
  following was the dependency chain installed.
  
  http://www.fpaste.org/180713/34735142/
  
The real odd parts are all the multi-media being installed. This seems
  to stem from phonon being included in the chain. I don't really know why
  it is. Is this a bug?
 
 Problem #1 is that PyQt4 is not split into subpackages for the different Qt 
 modules being bound, so you end up with the Phonon and QtWebKit bindings 
 installed, which drag in the rest. So far we have chickened out of splitting 
 PyQt4, we'll need to look into this issue in the KDE SIG.
 
 Problem #2 is that you are getting phonon-backend-vlc instead of phonon-
 backend-gstreamer, which ends up dragging in a lot of dependencies. Try 
 using --exclude=phonon-backend-vlc to force yum to pick -gstreamer instead. 
 This is a result of phonon-backend-vlc being in RPM Fusion (and you having 
 that enabled). It gets preferred by yum for some reason (shorter name? fewer 
 direct dependencies? something else? I don't know which of the many criteria 
 is being used here). I have always said that having phonon-backend-vlc in 
 the repositories is a bad idea (because you end up with a different default 
 backend depending on the repositories you have selected, leading to a 
 support nightmare), but I wasn't listened to. (In fact, this even affects 
 builds of KDE packages in RPM Fusion, where phonon-backend-vlc also gets 
 dragged in, and thus the KDE packages cannot be rebuilt against a new FFmpeg 
 before VLC is. That sucks.)

Ah I see. Well thanks for the info. I was pretty surprised to see all
these multi-media related things being dragged in for what is
essentially a dd wrapper.


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

Dependency chain issue...

[Nathanael d. Noblet]

Hello,

  I have F21 Workstation installed. I installed liveusb-creator and the
following was the dependency chain installed.

http://www.fpaste.org/180713/34735142/

  The real odd parts are all the multi-media being installed. This seems
to stem from phonon being included in the chain. I don't really know why
it is. Is this a bug?

-- 
Nathanael

-- 
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: F22 Self Contained Change: Vagrant

[Nathanael D. Noblet]

On Thu, 2015-01-22 at 11:09 -0700, Nathanael D. Noblet wrote:
 On Thu, 2015-01-22 at 10:21 -0500, Jaroslav Reznik wrote:
  == Scope ==
  * Proposal Owners: Initial work has been done in for Vagrant on F20 
  in a Copr repository. 
 
 I'm really really interested in vagrant on fedora. I am however running
 F21. The copr is only for F20. Any chance one can be created for F21
 that I could use for testing? Recently I've had vagrant /
 vagrant-libvirt pretty much die on my so I'm using virt-manager to deal
 with the VMs in the mean time. I would very much like to use vagrant
 again.

Oh it looks like there is a F21 copr repo. I'll try that. Thanks.


-- 
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: F22 Self Contained Change: Vagrant

[Nathanael D. Noblet]

On Thu, 2015-01-22 at 10:21 -0500, Jaroslav Reznik wrote:
 == Scope ==
 * Proposal Owners: Initial work has been done in for Vagrant on F20 
 in a Copr repository. 

I'm really really interested in vagrant on fedora. I am however running
F21. The copr is only for F20. Any chance one can be created for F21
that I could use for testing? Recently I've had vagrant /
vagrant-libvirt pretty much die on my so I'm using virt-manager to deal
with the VMs in the mean time. I would very much like to use vagrant
again.

-- 
Nathanael

-- 
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: Power consumption with Fedora

[Nathanael D. Noblet]

On Tue, 2014-12-02 at 21:47 +0100, Jan Kratochvil wrote:
 On Tue, 02 Dec 2014 06:30:57 +0100, Nathanael d. Noblet wrote:
  I don't know much about it but I hate how bad my battery life is on my
  laptop...
 
 My 3 years old Lenovo X220 lasts for 12 hours (powertop reports so) on Fedora 
 20
 x86_64 with powertop --auto-tune.  According to powertop approx. 5.5W is
 display backlight and 1W is the rest of system.
 
 Just to give a reply that Fedora is not bad on all configs/hardware.

Well until yesterday I didn't know that Fedora didn't install /
configure any of these packages. I've installed tlp and powertop, I
didn't know powertop did anything other than monitor. I'll see what
powertop --auto-tune does. I don't even know if the tlp package has
enabled anything either. I wonder if having tlp installed and running
powertop --auto-tune will conflict / fight each other...

Time to try stuff out.

-- 
Nathanael



-- 
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: Power consumption with Fedora

[Nathanael D. Noblet]

On Tue, 2014-12-02 at 15:23 -0700, Kevin Fenzi wrote:
 On Tue, 02 Dec 2014 14:44:59 -0700
 Nathanael D. Noblet nathan...@gnat.ca wrote:
 
  On Tue, 2014-12-02 at 21:47 +0100, Jan Kratochvil wrote:
   On Tue, 02 Dec 2014 06:30:57 +0100, Nathanael d. Noblet wrote:
I don't know much about it but I hate how bad my battery life is
on my laptop...
   
   My 3 years old Lenovo X220 lasts for 12 hours (powertop reports so)
   on Fedora 20 x86_64 with powertop --auto-tune.  According to
   powertop approx. 5.5W is display backlight and 1W is the rest of
   system.
   
   Just to give a reply that Fedora is not bad on all configs/hardware.
  
  Well until yesterday I didn't know that Fedora didn't install /
  configure any of these packages. I've installed tlp and powertop, I
  didn't know powertop did anything other than monitor. I'll see what
  powertop --auto-tune does. I don't even know if the tlp package has
  enabled anything either. I wonder if having tlp installed and running
  powertop --auto-tune will conflict / fight each other...
  
  Time to try stuff out.
 
 You might also look at tuned... 
 
 (I think it was mentioned early in the thread). 
 
 tuned-adm profile powersave
 
 Also: 
 
 https://docs.fedoraproject.org/en-US/Fedora/20/html-single/Power_Management_Guide/index.html
 
 Of course it would be nice if this stuff just did the right thing and
 you didn't have to run any commands or read any guides. 

Oh my I've barely started readind the above and its great... I wish I
knew of this long ago. Thanks for the pointers and mention of tuned.

-- 
Nathanael

-- 
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: Power consumption with Fedora

[Nathanael d. Noblet]

On Mon, 2014-12-01 at 17:57 -0700, john.tiger wrote:
 Obviously priority is now on F21 bugs but looking beyond that
 
 I want to work with someone more knowledgeable on power consumption - it 
 stinks on Fedora 20.
 
 OSX on mac air gets 11-12 hrs  Fedora gets 4
 Chrome OS on Chromebook gets 9-10  Fedora gets about 6
 
 Tried powertop - see slight improvement.
 
 Guys at ARCH claim with powerdown scripts they get close to 11 on Mac 
 Air - that's good
 
 So we need to get the powerdown scripts to work well with Fedora.  I 
 have no idea how much conversion, if any is needed for Fedora - just 
 don't have the knowledge of processes, Fedora scripts, etc.  But willing 
 to help out, test, etc.  (I want 11 hrs on my Mac Air !).

I don't know much about it but I hate how bad my battery life is on my
laptop... I've been considering buying a mac because I thought it was
the size of battery etc (granted that could still be a factor). It truly
is miserable. I'd be willing to work to try to test / package stuff.

-- 
Nathanael


-- 
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: The Poodlebleed Bug

[Nathanael D. Noblet]

On Wed, 2014-10-15 at 17:00 +0100, Sérgio Basto wrote:
 this site 
 http://poodlebleed.com/ 
 
 says that my server with F19 is vulnerable 
 
 any news about this ? 

Disable SSL3? Who needs IE6 on XP?



-- 
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/F22: xorg-x11-drv: which for SiS?

[Nathanael D. Noblet]

On Tue, 2014-09-23 at 17:20 +0200, Marcin Juszkiewicz wrote:
 Last cpu for 775 socket was released in 2010 not 2008.
 
 But yes, it can be seen as old and slow.

So just to clarify. It should be possible to remove the part in
xorg.conf specifying the sis driver, while still manually setting the
display resolution. Would that not solve all the issues? Does it?

-- 
Nathanael

-- 
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: Improving the offline updates user experience

[Nathanael d. Noblet]

On Fri, 2014-09-12 at 16:47 +0100, Richard Hughes wrote:
 On 12 September 2014 16:16, Nathanael d. Noblet nathan...@gnat.ca wrote:
  Yeah, I almost never use the reboot  install method. 90% of the
  packages being installed/updated seem foolish to need a reboot to
  update.
 
 I've been called worse that foolish I guess...
 
  I typically do a yum update manually and then if I notice
  glibc/kernel/systemd or other big packages do a reboot.
 
 That's just not safe. Have you ever had firefox open and done a
 firefox update? Widgets start disappearing, redraws start having weird
 artifects and then after a little while it just crashes. Other
 applications like LibreOffice behave the same. Anyone that says things
 like the old version of the library stays in memory obviously hasn't
 actually done much real-world GUI programming in the last decade, or
 runs any kind of secure desktop system. The *only* way to do this
 securely and safely in the system we have now is in a clean pre-boot
 environment, which is sad and crap UX, but still nevertheless true.
 When we have application sandboxing and a stable OS platform to use,
 we can certainly do something more sane, but until then we're just
 hacking around the problem.

So I don't use Firefox anymore but I do know back in the day if we had
FF open when we updated it would do a double request for each page/form.
However when updating we just restarted FF and it would work fine after
that. I've never noticed any other issues than FF but like I said I
don't use it anymore.

Granted that doesn't matter obviously we don't want that kind of
behaviour. 

I am curious though. Everyone says the only way to do it securely and
safely is with nothing running. Why can't updates be applied with stuff
running prior to a reboot? 


-- 
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: PkgDB, pending ACL requests

[Nathanael d. Noblet]

On Thu, 2014-07-17 at 19:13 +0200, Dominik 'Rathann' Mierzejewski wrote:
 On Thursday, 17 July 2014 at 15:28, Pierre-Yves Chibon wrote: 
  From the version 1.16, the page listing all the pending ACLs now provides
  'Approve all' and 'Deny all' buttons.
  
  So feel free to visit: https://admin.fedoraproject.org/pkgdb/acl/pending/ 
  and
  take action.
 
 Wonderful! I wasn't even aware that people were waiting for my
 approvals. All done now.

Me neither! I've approved the ones waiting for me too.


-- 
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: Lockscreen / suspend / keyboard issue

[Nathanael d. Noblet]

On Sun, 2014-05-11 at 22:30 -0600, Nathanael d. Noblet wrote:
   After opening/closing the computer a few times sometimes I just hard
 reset the machine. Sometimes it comes to and lets me enter my password
 and unlocks. I'd like to debug and find the source of the problem. 
 
   If I login via ssh from another computer no process is consuming the
 CPU, there aren't obvious highly repetitive messages in the logs or that
 I can see would be related.
 
   This has been happening since I got the machine for all F20 kernels.
 Where do I look? What can I do to figure this out?

Hello,

  So I think what is happening is that the keyboard isn't activated. It
makes the most sense. I found some people talking about similar issues.
Most of the time it seems adding atkbd.reset to the kernel command line
seemed to fix it. Granted these were all Ubuntu machines. Adding the
atkbd.reset to grub did nothing for me. I'm not sure if we use atkbd or
if there is an equivalent command I can use on fedora to overcome this
very annoying issue. I did find a bug that may be similar enough so I
added myself and comments to it

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

I would love any pointers or things to do to figure out if the keyboard
not resuming or otherwise having issues this is indeed the case.

-- 
Nathanael

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

Lockscreen / suspend / keyboard issue

[Nathanael d. Noblet]

Hello,

  I'm writing here because I don't know what component to report a bug
against. 

  I have a Toshiba P50-A. When waking from suspend I have often but not
always have issues. 

  1) Sometimes the keyboard and mouse are non-responsive. Except for
what I presume are handled by APCI (screen brightness etc). So for
example I open the laptop, the screen brightens, I see the gnome lock
screen (the one prior to the actual unlock part where you enter your
password). Hitting any key results in nothing. The mouse does not
respond. I can't switch to another VT nada. Numlock/Capslock do not
light the LEDs for their respective functions. Close the lid and the
computer enters sleep state. 

  2) I get past the above however the password prompt is in a tight
submission loop. As if I was holding the enter key without ever
releasing it. Lots of failed logins. Again, I close the lid and the
computer enters sleep state.

  After opening/closing the computer a few times sometimes I just hard
reset the machine. Sometimes it comes to and lets me enter my password
and unlocks. I'd like to debug and find the source of the problem. 

  If I login via ssh from another computer no process is consuming the
CPU, there aren't obvious highly repetitive messages in the logs or that
I can see would be related.

  This has been happening since I got the machine for all F20 kernels.
Where do I look? What can I do to figure this out?

Thanks,
-- 
Nathanael



-- 
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: GnuTLS issue (Mandos Server/Client)

[Nathanael D. Noblet]

On Thu, 2014-04-03 at 16:05 +0200, Nikos Mavrogiannopoulos wrote:
 On Wed, 2014-04-02 at 10:50 -0600, Nathanael D. Noblet wrote:
  CentOS 6 = gnutls 2.8.5
  F20  = gnutls 3.1.20
  The server is a python app and sets the priority string as follows:
  priority=SECURE256:!CTYPE-X.509:+CTYPE-OPENPGP
  this is fed to some gnutls function somewhere in the stack.
 
 Does it really use TLS with openpgp certificates? If yes, I doubt you
 could make 2.8.5 interoperate with gnutls 3.1.20. GnuTLS was modified in
 3.1.x to adhere with RFC6091 which was incompatible the previous attempt
 to have openpgp keys to TLS.

Hello,

  Yes it uses TLS and opengpg certificates. So gnutls 3.1.20 can't use
both new and old methods I presume?



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

GnuTLS issue (Mandos Server/Client)

[Nathanael D. Noblet]

Hello,

  I'm working on getting a package (mandos) included in Fedora/EPEL.
Currently its heavily focused on debian based distros so I'm not ready
for a review. However I have it working in a few situations but have
some issues in others. I'm hoping someone here may be able to shed light
on what may be going on. So that I can finish adding the bits needed to
be fully functional and then included.

  So the whole thing works only if servers and clients are on the same
OS version. Different errors are thrown for different combinations.

Client OS  Server OSError
F20CentOS 6 TLS packet with unexpected length was received
CentOS 6   F20  The TLS connection was non-properly terminated
CentOS 6   CentOS 6 No error
F20F20  No error

CentOS gnutls versions
CentOS 6 = gnutls 2.8.5
F20  = gnutls 3.1.20

The server is a python app and sets the priority string as follows:
priority=SECURE256:!CTYPE-X.509:+CTYPE-OPENPGP
this is fed to some gnutls function somewhere in the stack.

I'm at a complete loss as to why it doesn't work. Pointers or docs or
anything else that can help me figure out why an app can talk to itself
as long as the same base OS is used would be GREATLY appreciated..

Thanks,
-- 
Nathanael

-- 
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: GnuTLS issue (Mandos Server/Client)

[Nathanael D. Noblet]

On Wed, 2014-04-02 at 10:15 -0700, Adam Williamson wrote:
 Well, have you tried the 'obvious' - building the newer gnutls on CentOS
 6 (or the older on Fedora 20) and building mandos against that, to see
 if the issue is in gnutls or somewhere else in the 'base system'? That'd
 narrow it down at least.

Hmm that does seem obvious in hindsight. However no I haven't tried
that. I figured I'd end up with a huge mess trying to recompile
something like that between distros with such huge time periods all the
related packages that depend on them. For example the python bindings
etc... I'll look into doing it 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

qemu / VNC / vino

[Nathanael D. Noblet]

Hello,

  So I've found a 'bug'. I have a group of developers who use
vagrant/libvirt to develop against. We use VNC since we are a
distributed team to connect to each other's desktops/workstations for
when we're at the 'huh this makes no sense'.

  If libvirt/qemu-system-x86_64 starts before vino-server (which is
common since we don't leave the vnc access on all the time). Then vino
only listens on ipv6 instead of ipv4 and ipv6. At that point no one can
connect to the workstation over vnc since we are all ipv4 connected.

  I'm not sure where the bug is and it isn't really a big bug as much as
I need to be able to tell either vino or qemu-system-x what ports to
use. 

  Thoughts? What should I look at/report?
-- 
Nathanael

-- 
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: qemu / VNC / vino

[Nathanael D. Noblet]

On Tue, 2014-03-25 at 18:24 +, Daniel P. Berrange wrote:

 In /etc/libvirt/qemu.conf you can set  remote_display_port_{min,max}
 to control the port range used

So that is awesome thank you. 

Given that by default virt-manager/libvirt/qemu listens to
127.0.0.0:PORT as opposed to 0.0.0.0:PORT. Should this be filed as a
bug? As in could the default port qemu started on be 6900 instead of
5900 so that this doesn't happen? I realize that 5900 is the standard
vnc port... I'm just wondering if there is a use case where changing
that config breaks anything?

-- 
Nathanael


-- 
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: qemu / VNC / vino

[Nathanael D. Noblet]

On Tue, 2014-03-25 at 17:51 -0400, Cole Robinson wrote:
 There was a bug about that in the past, but we rejected changing the default
 range. Libvirt and xen and qemu have all used the assumption of starting at
 port 5900 for too long, we didn't want to deal with any potential fallout for
 something that affects a small number of users, and that nowadays has a manual
 workaround.
 
 vino could always be extended to try a little harder/smarter to find a free
 port, which libvirt has done for years.

Yeah I see what you're saying. Just a couple points in favor of changing
qemu/libvirt...

#1) If someone is using a normal desktop and vino finds a collision it
has no way of informing the user. It could find a free port but telling
someone to connect to my host, I have no way of knowing what port it is
using without going into a terminal and looking for listening ports. The
libvirt/qemu would continue to work by default if the default was set to
something else. In qemu.conf and I presume the other backends
libvirt/virt-manager supported. 

#2) In the case where an admin/user wants to have access to the VM host
from a *remote* host. They have to change some configuration since
qemu-system-x86_64 is only listening on 127.0.0.1 not on any external
interface. At this point the admin is not likely configuring this on a
desktop and if they are can specify any port they'd like and should
realize that if they are using vino (or something similar), they have to
use different ports. (Which I would know too - I just didn't know why
qemu was listening on that port when I didn't have any gui up accessing
that host...).

#3) Based on bugs I've seen on gnome I can't see them changing it much.
(I just posted a bug to vinagre/ a vnc/rdp client) which doesn't notify
the user of a password prompt *or* to accept a certificate on SSL
connections. The devs basically said don't use vinagre, use the command
line program that is being used by vinagre. Kinda odd...

So I understand if nothing gets changed but it would be nice if it was
reconsidered. I may not understand all the implications but if the
default local port was configured to not collide. I dunno, I'd enjoy
it. :) Granted I'm enjoying it at the moment anyway. 

Thanks,
-- 
Nathanael

-- 
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: [perl-SGML-Parser-OpenSP/epel7] exclude ppc64 for now as perl-class-accessor is unavailable

[Nathanael D. Noblet]

On Tue, 2014-01-28 at 16:36 +, Paul Howarth wrote:
 On 28/01/14 16:32, Paul Howarth wrote:
  On 28/01/14 16:14, Nathanael Noblet wrote:
  commit 09acd6327d876e6d1126ebed87ae9e1e1ec84c27
  Author: Nathanael D. Noblet nathan...@noblet.ca
  Date:   Tue Jan 28 09:14:44 2014 -0700
 
   exclude ppc64 for now as perl-class-accessor is unavailable
 
perl-SGML-Parser-OpenSP.spec |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
 
  I'm in the process of fixing that:
 
  https://admin.fedoraproject.org/updates/FEDORA-EPEL-2014-0374/perl-Class-Accessor-0.31-0.6.1.el6
 
 And, having now noticed that you were referring to epel7, spot has 
 branched this yesterday but not yet built it, so it should be available 
 soon (in EPEL, for all architectures; only EL-6 has the arch-specific 
 issue).
 

Awesome - After I emailed spot I remembered that it was likely what you
just described... I eagerly await the fix for el6 and build on el7.

Thanks!

--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel

Re: Fedora.next in 2014 -- Big Picture and Themes

[Nathanael D. Noblet]

On Tue, 2014-01-28 at 19:04 +0100, drago01 wrote:
  Second, give people what they *do* care about: choices of language stacks
  above the base level, and a layer of separation so that there isn't a big
  impact when the base layer changes. To quote someone I talked to: No
  distribution does that well, so if you can, you'd really have something
  valuable to me.
 
 This is again hand wavy(sorry for overusing this term). I can
 already have multiple language stacks
 for instance python, java, ruby and php on fedora (or pretty much any
 other distribution) just fine today.
 
 And I don't expect it to break when the base layer (whatever that
 means ... kernel? glibc? systemd?) changes.
 So in that case I didn't even get the problem itself so I cannot
 comment much on the solution.

From my perspective it isn't about the language stacks, its about the
stacks within the languages. Fedora has a 18 month window. My servers
run for years. I don't have time to update the entire server every 18
months. It just isn't feasible. (I'm also not fully virtualized and
automated with ansible and friends yet). So given that I use CentOS
since I know it will remain stable. The downside is that php is never
updated on it. It has a really really old php 5.3, I want 5.4 but so
many things are compiled against the 5.3 so its a huge amount of work.

I'm SUPER intrigued by Fedora.next if it is trying to solve this issue.
I can have a base OS, but pick the PHP 5.4 stack or 5.5 stack and/or
upgrade *just* that part on a live server. I'd be super happy. I could
upgrade my php stack but leave the os running happily. Less work.
Eventually I'd expect bringing up a cloud instance with ansible
provisioning and all that would also allow that.

-- 
Nathanael

-- 
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: Discontinued Packing of NetBeans IDE

[Nathanael D. Noblet]

On 11/05/2013 09:46 AM, Rahul Sundaram wrote:

Someone from Sun used to be the maintainer and noone is doing it right
now.  No technical or licensing issues if anyone is interested in
packaging it afaik.


I've been loving using netbeans however I've been using the upstream 
package.. I looked into the original package but the spec file is so 
complicated and I have no idea how java programs are packagaed so shied 
away. If someone else thinks collectively we could bring it back up to a 
recent version. I'd be delighted to co-maintain it.



--
Nathanael d. Noblet
t 403.875.4613
--
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: Get FAS account authentication facility for my Web page

[Nathanael D. Noblet]

On 09/13/2013 10:35 AM, Kevin Fenzi wrote:

We want to make sure people don't enter their fas information into any
3rd party forms or websites. You should only enter your fas
login/password to a fedoraproject.org site.


Ah shoot! I'm going to have to write that nice Nigerian prince and see 
if we can still do the $100,000,000 transfer with only my personal 
information and without my FAS credentials. :D Fingers crossed!



--
Nathanael d. Noblet
t 403.875.4613
--
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: Rebuilding in dependency order

[Nathanael D. Noblet]

On 08/29/2013 07:42 AM, Marcela Mašláňová wrote:

You make it sound like Peter has a tool for rebuilding in dependency
order. I need such a thing. Can it be made to work for other things
than Perl?




It can take a list of packages and count dependencies, so it could be
used for different languages. He didn't release the latest version yet.

Archive of older releases http://ppisar.fedorapeople.org/Fedora-Rebuild/


So awhile back Seth sent me his buildorder.py scripts you can see it here.

http://skvidal.wordpress.com/2013/05/17/sorting-srpms-by-buildorder/

Its nice in that it also does grouping so that it tells you what can be 
built in parallel.



--
Nathanael d. Noblet
t 403.875.4613
--
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: Schedule for Wednesday's FESCo Meeting (2013-08-14)

[Nathanael D. Noblet]

On 08/15/2013 10:26 AM, Jóhann B. Guðmundsson wrote:

On 08/15/2013 10:16 AM, Marcela Mašláňová wrote:


I agree our updates should be supported option ;-) They are usually
working very well.



We really should try to stop using the word supported since it
misleading for everybody.

Best effort is what accurately describes what the community does so
surely there is a word in the English vocabulary that is a better match
to that then support and we can try to use...


tested?


--
Nathanael d. Noblet
t 403.875.4613
--
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: Fwd: Thursday is Spice Test Day!

[Nathanael D. Noblet]

On 05/30/2013 11:23 AM, Adam Williamson wrote:

On Thu, 2013-05-30 at 15:53 +0200, poma wrote:

On 30.05.2013 14:16, Martin Holec wrote:

Are you tired of using VNC?


Nope.
Do you have any issues with VNC?


It's slow, doesn't have as good guest integration as Spice, and misses
lots of spice's advanced features...



Can Spice be used to connect to an already running Gnome desktop for 
remote support purposes?


The docs I looked at talked about using Spice for virtualization and or 
setting up remote login, but nothing like VNC/Vino for connecting to 
someone else's desktop...


--
Nathanael d. Noblet
t 403.875.4613
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

looking for co-maintainer / new owner

[Nathanael D. Noblet]

Hello,

  The package barry is used to sync a blackberry device with a desktop. 
I took it over awhile ago when I owned a blackberry. I've since moved on 
to own various other devices and don't see myself returning to a 
blackberry anytime soon. As such I'm wondering if anyone wants to take 
ownership.


  There is a semi-active upstream. They have new releases and a few 
community members contributing. A very responsive main developer - any 
issues we've had he's helped resolve and accepts patches readily. Its a 
low maintenance package by most accounts. I'll continue to maintain it 
if no one steps up for a little. If no one takes it I'll likely drop it 
around F20 or so.


--
Nathanael d. Noblet
t 403.875.4613
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

Re: Smock successor?

[Nathanael D. Noblet]

On 04/04/2013 06:44 AM, Till Maas wrote:

Hi everyone,

I have been using smock.pl regularly and since it was not developed
recently. I wonder what everyone else is using, e.g. does something
better exist? If not, I am planning to give it a proper new home,
currently I am trying out gitorious:
https://gitorious.org/smock/smock/


Hello,

  I still use smock with some modifications (patched to build different 
distro/arches in threads). I think I also modified it to sign the 
packages it builds (asks for the key when I kick off a build)...



--
Nathanael d. Noblet
t 403.875.4613
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

Re: Smock successor?

[Nathanael D. Noblet]

On 04/04/2013 10:25 AM, Till Maas wrote:

Can you provide the patches? Adding support to sign packages is
something I want to look into as well.


I thought I provided them upstream awhile ago when I wrote them at this 
point I don't know what is original and what is not. Attached is my 
smock-threaded.pl script diffing it against whatever is latest would 
likely show you the changes made. You'll note that it has an autosign 
script it calls if it is asked to auto sign the rpms. Since this was all 
internal and used mainly for quick development builds I had a *terrible* 
script that used expect and all that for the password. It would be much 
better to just grab from the perl script itself the signing password 
than to do what I did. I also hardcoded the number of packages. Not my 
best work but included for completeness... :D





--
Nathanael d. Noblet
t 403.875.4613


smock-threaded.pl
Description: Perl program
#!/usr/bin/expect

set package_0 [ lindex $argv 0 ]
set package_1 [ lindex $argv 1 ]
set package_2 [ lindex $argv 2 ]
set package_3 [ lindex $argv 3 ]
set package_4 [ lindex $argv 4 ]
set package_5 [ lindex $argv 5 ]
set package_6 [ lindex $argv 6 ]
set package_7 [ lindex $argv 7 ]
set package_8 [ lindex $argv 8 ]

if {$argc == 0} {
  send_user NO arguments??? $argv
}
if {$argc == 1} {
send_user calling rpmsign --addsign $package_0\nargv: $argv
spawn rpmsign --addsign $package_0
expect Enter pass phrase: 
send PASSWORD_HERE\r
expect eof

}
if {$argc == 2} {
spawn rpmsign --addsign $package_0 $package_1
expect Enter pass phrase: 
send PASSWORD_HERE\r
expect eof

}
if {$argc == 3} {
spawn rpmsign --addsign $package_0 $package_1 $package_2
expect Enter pass phrase: 
send PASSWORD_HERE\r
expect eof

}
if {$argc == 4} {
spawn rpmsign --addsign $package_0 $package_1 $package_2 $package_3
expect Enter pass phrase: 
send PASSWORD_HERE\r
expect eof

}
if {$argc == 5} {
spawn rpmsign --addsign $package_0 $package_1 $package_2 $package_3 $package_4
expect Enter pass phrase: 
send PASSWORD_HERE\r
expect eof
}
if {$argc == 6} {
spawn rpmsign --addsign $package_0 $package_1 $package_2 $package_3 
$package_4 $package_5
expect Enter pass phrase: 
send PASSWORD_HERE\r
expect eof
}
if {$argc == 7} {
spawn rpmsign --addsign $package_0 $package_1 $package_2 $package_3 
$package_4 $package_5 $package_6
expect Enter pass phrase: 
send PASSWORD_HERE\r
expect eof
}
if {$argc == 8} {
spawn rpmsign --addsign $package_0 $package_1 $package_2 $package_3 
$package_4 $package_5 $package_6 $package_7
expect Enter pass phrase: 
send PASSWORD_HERE\r
expect eof
}
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

Re: Feedback wanted: Fedora Formulas

[Nathanael D. Noblet]

On 01/09/2013 12:26 PM, Seth Vidal wrote:




On Wed, 9 Jan 2013, Kevin Fenzi wrote:



One of the big questions to answer is distribution. I can see good
arguments on the one hand distributing formulas via RPM and on the
other having an official Git repository for them.


Yep. I am torn here too. rpms get us a lot, but are also inflexable in
other ways. :)



Let me make an argument against rpms here.

Ansible doesn't require anything on the local system to run a playbook.

That's one of its virtues.

For a user if we just use a git repo then the user doesn't have to
modify their system in order to use the tools to change their system.

There is a certain amount of elegance in that not to mention just not
being annoying.


It also allows a user to take a recipe, fork, modify, improve etc and 
test it without necessarily knowing anything about rpm... or being a 
packager in the packager group etc. Having a fedora account etc...



--
Nathanael d. Noblet
t 403.875.4613
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

Re: How do I find the maintainers of a package ?

[Nathanael D. Noblet]

On 10/23/2012 12:39 PM, Alain Williams wrote:

Hi,

when maintaining/configuring my systems I occasionally make changes that I think
would be generally useful. What is the easiest way of bringing an idea to the
attention of a package maintainer  if he likes the idea I would then collect
up  push what I have done, etc.

I have looked at the URL below, but it does not give what I want:

 
https://fedoraproject.org/wiki/Category:Package_Maintainers?rd=PackageMaintainers


The package that I am looking at today is dhcp. If you have more than one
interface and need different parameters on each interface the current setup does
not work - mine does and cleanly drops back to the current config.


You should be able to email packagename-ow...@fedoraproject.org and it 
will get to whoever owns the package. One caveat is make sure its the 
*package name* as the src.rpm would be named, not the sub-packages it 
may produce.



--
Nathanael d. Noblet
t 403.875.4613
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

Re: HEADUP for all PEAR packages

[Nathanael D. Noblet]

On 10/23/2012 08:40 AM, Remi Collet wrote:

For years... pear have its metadata database stored in /usr/share/pear

This will move soon to /var/lib/pear (to be FHS compliant).
(feature approved/merged by upstream)

With this last change, we'll have only libraries in /usr/share/pear
(which is part of the default php include_path)

WARNING : all pear packages will be FTBFS.

Very simple fix:

Define the default metadata directory location

%{!?pear_metadir: %global pear_metadir %{pear_phpdir}}


And instead of
# Clean up unnecessary files
rm -rf %{buildroot}%{pear_phpdir}/.??*

Use
rm -rf %{buildroot}%{pear_metadir}/.??*


This can be applied on all branches
(already used on some of my packages, see php-phpunit-PHPUnit p.e.)


I presume php-pecl packages are un-affected by this?


--
Nathanael d. Noblet
t 403.875.4613
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

Re: Taking over orphaned Func and Certmaster packages

[Nathanael D. Noblet]

On 10/11/2012 10:39 AM, Steve Salevan wrote:

Hey guys,
I'd like to put my name in to take over ownership of the orphaned Func
and Certmaster packages as per the orphaned package takeover procedure.
  I am the new project maintainer for these projects, and I'd like to
add a few tuneups here and there that we've found useful out here at
Tumblr.  My Fedora Project username is ssalevan and I've applied for
commit and bugzilla watching on each package branch; let me know if I
can provide any further information, and I very much appreciate the
consideration.



So I noticed you took ownership of func but not certmaster. Oversight?


--
Nathanael d. Noblet
t 403.875.4613
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

Re: Taking over orphaned Func and Certmaster packages

[Nathanael D. Noblet]

Hello,

  These packages have become semi important to us as well so I'd be 
willing and interested in being a co-maintainer.


On 10/11/2012 10:56 AM, Toshio Kuratomi wrote:

On Thu, Oct 11, 2012 at 12:46:35PM -0400, Seth Vidal wrote:




On Thu, 11 Oct 2012, Steve Salevan wrote:


Hey guys, I'd like to put my name in to take over ownership of the orphaned 
Func and Certmaster packages as per the orphaned package takeover procedure.  I 
am the new project maintainer for these
projects, and I'd like to add a few tuneups here and there that we've found 
useful out here at Tumblr.  My Fedora Project username is ssalevan and I've 
applied for commit and bugzilla watching on
each package branch; let me know if I can provide any further information, and 
I very much appreciate the consideration.




I just orphaned the packages and I'm vouching for Steve as the new
func maintainer. How should I go about having him take them over?


If you're willing to mentor him, it's probably easiest to do this:
http://fedoraproject.org/wiki/How_to_get_sponsored_into_the_packager_group#Become_a_co-maintainer






--
Nathanael d. Noblet
t 403.875.4613
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

Re: Why is not enabled TapButton of touchpad on Fedora by default?

[Nathanael D. Noblet]

I wonder if this couldn't be a RFE for anaconda. Maybe not possible, 
however couldn't we allow the upload of a kickstart 'snippet' or 
something where users installing Fedora could provide snippets to set 
the defaults at install time? Something where it doesn't really need a 
full blown kickstart, but somehow merges only the pieces that are 
inputted?? This way there are the defaults, but a community of 'user 
preference' snippets could exist etc...


Just a random thought.

--
Nathanael d. Noblet
t 403.875.4613
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

Re: Why is not enabled TapButton of touchpad on Fedora by default?

[Nathanael D. Noblet]

On 09/26/2012 12:23 PM, Adam Williamson wrote:

On Wed, 2012-09-26 at 12:15 -0600, Nathanael D. Noblet wrote:

I wonder if this couldn't be a RFE for anaconda. Maybe not possible,
however couldn't we allow the upload of a kickstart 'snippet' or
something where users installing Fedora could provide snippets to set
the defaults at install time? Something where it doesn't really need a
full blown kickstart, but somehow merges only the pieces that are
inputted?? This way there are the defaults, but a community of 'user
preference' snippets could exist etc...


kickstarts can already be partial and anaconda will prompt for anything
that's not covered. I've never tested a kickstart which *only* did %
post, which is more or less what this would be (AFAICS), though.

Yeah, something where it could accept a file upload, or typed right 
in... or one day loaded from a list of community snippets to include.


--
Nathanael d. Noblet
t 403.875.4613
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

Re: Network configuration future

[Nathanael D. Noblet]

On 09/07/2012 03:34 PM, Dan Williams wrote:


And here comes the bigger question what is keeping all you networking
guys from simply combine all that effort and coming up with one single
network application that everybody can use happily from embedded to
servers to desktop?



There's room to work towards consensus on functionality, but at the
moment I don't see a lot of momentum towards a Grand New Unified Plan,
partially because that's how free software works.  It would be great if
we had one, and I'm certainly willing to entertain changes to
NetworkManager that make it more capable for anyone's use-cases.  Nobody
thinks NM has reached perfection, least of all me.


As someone who recently needed some pretty niche functionality if you 
ask me. I was amazed at the amount of help and open-mindedness of Dan. 
He helped me learn where stuff was in the tree, and gave me pseudo code. 
Walked me through some parts and spoon fed me other pieces of code 
necessary to make what I needed happen with NM. It was then merged into 
NetworkManager. Of any project that could potentially do all the things 
that are necessary, I'd vote for NM. It'd be a shame that the other 
projects couldn't work together towards a common goal. I can't imagine 
how it wouldn't be possible to get NM to the point where it does do 
everything one needs it to do. Especially with the lead developers it has.


My 2cents.
--
Nathanael d. Noblet
t 403.875.4613
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

Re: building compose, selinux problems

[Nathanael D. Noblet]

On 08/15/2012 10:44 AM, Brian C. Lane wrote:

On Tue, Aug 14, 2012 at 08:49:15AM +0100, Ian Malone wrote:

Hi,

I'm trying to build a spin on F16 against F17 (specifically the
fedora-jam spin, ssh://git.fedorahosted.org/git/music-creation
spin-kickstarts/fedora-jam/fedora-live-jam-kde.ks, with the
mono-bristol package removed).


Have you fried building on F17? It generally isn't a good idea to expect
building from a different release to work. Sometimes it does, but really
you should be using F17 to build F17 spins.


I've seen instructions that you can use mock to do this kind of thing. 
https://fedoraproject.org/wiki/How_to_create_a_Fedora_install_ISO_for_testing


I've used it with good success.


--
Nathanael d. Noblet
t 403.875.4613
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

Re: Fedora-Review 0.2.0

[Nathanael D. Noblet]

Where would you like bug reports?

I tried it against one of my own review tickets. It found a number of 
issues however almost all of them except one was wrong.


For example it complained of no clean section with a rm -rf %{buildroot} 
which the specfile contained, same message except in the install section 
etc.


To try it out yourself try it against bug 841662

--
Nathanael d. Noblet
t 403.875.4613
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

Re: Fedora-Review 0.2.0

[Nathanael D. Noblet]

On 08/02/2012 12:02 AM, Mathieu Bridon wrote:

On Wed, 2012-08-01 at 23:52 -0600, Nathanael D. Noblet wrote:

Where would you like bug reports?

I tried it against one of my own review tickets. It found a number of
issues however almost all of them except one was wrong.

For example it complained of no clean section with a rm -rf %{buildroot}
which the specfile contained, same message except in the install section
etc.


Are you sure it wasn't complaining that the specfile actually contained
those lines?

The Fedora guidelines say those lines are not needed, and shouldn't be
there for new packages, unless the package maintainer wants to ensure
compatibility with EPEL 5.


Hmm I guess I mis-read it then.

[!]: MUST Buildroot is not present
[!]: MUST Package does not run rm -rf %{buildroot} (or $RPM_BUILD_ROOT) 
at the beginning of %install


When I read that, the ! tells me I failed that. So Package does not run 
rm -rf %{buildroot} at the beginning of %install. I think the double 
negative there is what threw me. I think putting the MUST part into the 
actual description would help. For example


[!] Package MUST NOT run rm -rf %{buildroot} ...

Clearly tells me that I failed that because I am running the rm command. 
Whereas a MUST preceding the line and the failure can be interpreted as 
I failed because the package does not run rm -rf ... Not sure if you see 
what I mean. Now that it is pointed out it does make more sense.


Thoughts? Is it just me that read that totally wrong?

--
Nathanael d. Noblet
t 403.875.4613
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

Re: Fedora-Review 0.2.0

[Nathanael D. Noblet]

On 08/02/2012 08:29 AM, Pierre-Yves Chibon wrote:

Maybe it would be better formulated as:
[!]: MUST: Buildroot MUST NOT be present (NOTE: this is not true for
EPEL5)
[!]: MUST: Package MUST NOT run rm -rf %{buildroot} (or $RPM_BUILD_ROOT)
at the beginning of %install

What do you think?


That would definitely be clearer to me.


--
Nathanael d. Noblet
t 403.875.4613
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

Package review...

[Nathanael D. Noblet]

Hello,

  No rush on this I *just* posted it and sadly I don't have a lot of 
time to swap reviews. I thought I would point out that I had posted a 
review for php-pecl-cairo if anyone is interested in having it in fedora 
so they could review it.


--
Nathanael d. Noblet
t 403.875.4613

--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

Re: Fedora-Review 0.2.0

[Nathanael D. Noblet]

Hello,

  I tried to use fedora-review and it seems to attempt building the 
package using Fedora 14?


from root.log

rootdir = /var/lib/mock/fedora-14-x86_64/root/

Is that intentional? A mis-configuration on my part?

On 07/11/2012 11:23 AM, Pierre-Yves Chibon wrote:

Dear all,

A new fedora-review is being brought to you. With this new version you
can find:
- Checks for Ruby packages (incomplete, but started)
- Checks for PHP packages (incomplete, but started)
- Better handling of the sources (handled now directly through rpm)
- Generate all review-related files in a subdirectory
- Add provides/requires to review template
- New report layout
- Support for different bugzilla
- Support for pre-built RPMs
- Possibility to exclude (-x) a test
- Possibility to run a single (-s) test
- A number of bugs fixed

And many more!

We would like to take this opportunity to thanks :
Alec Leamas (who has done the major part of this release)
Michael Scherer
Gregor Tätzner
Christof Damian
Ralph Bean
Bohuslav Kabrda
Toshio Kuratomi
who have joined our fearless team of developers and of course thanks to
all the people that brought us food^cbug reports and RFE.

Finally, for those of you that would like to see what's going on, feel
free to join the mailing-list:
https://fedorahosted.org/mailman/listinfo/fedorareview

And because they need karma, the announced updates:
https://admin.fedoraproject.org/updates/fedora-review-0.2.0-1.fc17
https://admin.fedoraproject.org/updates/fedora-review-0.2.0-1.fc16


Enjoy!

Stanislav  Pierre




--
Nathanael d. Noblet
t 403.875.4613


--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel