Re: Updating package python-feedparser

[Johannes Lips]

Thanks a lot!
--
___
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

Updating package python-feedparser

[Johannes Lips]

Hi all,

I was wondering if it would be possible, perhaps by a provenpackager, to update 
the abovementioned package. There already is a bug report for quite some time 
here [1].
The upstream discussion about this bug is here [2] and I even provided a pull 
request to make the update even easier.
The reason for this is that the issue is causing some builds to fail with 
python 3.13, so this will probably fix more than one package.

Thanks a lot,
Johannes

[1] https://bugzilla.redhat.com/show_bug.cgi?id=2262610
[2] https://github.com/kurtmckee/feedparser/issues/330
--
___
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: Update python-musicbrainzngs by a proven packager and request for adding a co-maintainer to the package

[Johannes Lips]

I've now also filed a bug report 
https://bugzilla.redhat.com/show_bug.cgi?id=2030824 for amluto. Please see the 
output of the fedora-active-user script in the following comment of the 
original bug 
https://bugzilla.redhat.com/show_bug.cgi?id=1685216#c10
Would this be sufficient or do I need to send an additional mail to devel?

Thanks 
Johannes
___
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

Update python-musicbrainzngs by a proven packager and request for adding a co-maintainer to the package

[Johannes Lips]

Hi all,

the package python-musicbrainzngs [1] has a long-standing bug [2] and is not 
upgraded to the latest version, which creates all sorts of issues for dependent 
packages. Therefore, I would like to ask if a proven-package could initiate an 
update. There's already a pull-request at 
https://src.fedoraproject.org/rpms/python-musicbrainzngs/pull-request/1
If possible it would be great if the package could get some co-maintainers in 
order to prevent a situation like this from happening again.

Thanks in advance
hannes

[1] https://src.fedoraproject.org/rpms/python-musicbrainzngs
[2 ] https://bugzilla.redhat.com/show_bug.cgi?id=1685216
___
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: Update python3-pystray to latest availabe upstream version in f34 and f33

[Johannes Lips]

Sorry, to bother again, but I missed that you only created the update for f35, 
but for at least f34 this should be an update to push into stable.

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
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Packages in need of a new maintainer

[Johannes Lips]

> On Sun, May 2, 2021 at 8:28 AM Johannes Lips  wrote:
> 
> maintainer.
> My fas is imcinerney.
Thanks, just added you.
> 
> -Ian
___
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: Update python3-pystray to latest availabe upstream version in f34 and f33

[Johannes Lips]

Thanks for 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 on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Packages in need of a new maintainer

[Johannes Lips]

> On Sun, May 2, 2021 at 9:28 AM Johannes Lips  wrote:
> 
> Hello Johannes,
> 
> Feel free to assign elementary-icon-theme to me. I'm already the
> maintainer of all other elementary / Pantheon packages in Fedora.
> Thank you for your work with maintaining those packages!
Done, thanks. You should be admin of both icon themes now, if necessary you can 
also become the main admin.
> 
> Fabio
___
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: Packages in need of a new maintainer

[Johannes Lips]

> I could help with the elementary stuff, but I don't think I can take over
> fully.
> 
> If anyone can help me maintain that'd be great.
I could probably help you out, if you give me your fas account name, I'll grant 
you the co-maintainer privileges.
Johannes
> 
> On Sun, 2 May, 2021, 12:59 pm Johannes Lips,  wrote:
___
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

Update python3-pystray to latest availabe upstream version in f34 and f33

[Johannes Lips]

Hi all,

I would like to ask if someone, probably a proven packager, could look into 
fixing a bug a lot of Xfce and dnfdragora users are facing at the moment.
The problem is that the update notification does not disappear by itself, but 
needs to be clicked away. See upstream bug report and also all the relevant 
links to the original culprit in pystray [1].

The easiest fix is to update python3-pystray to the latest upstream version, 
which fixes the bug. All the relevant information is also present in the RHBZ 
[2], but so far nothing happened and it really is just a matter of minutes to 
fix this.

Thanks
johannes


[1] https://github.com/manatools/dnfdragora/issues/178
[2] https://bugzilla.redhat.com/show_bug.cgi?id=1903824
___
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

Packages in need of a new maintainer

[Johannes Lips]

Dear all,

after quite some years, I would like to hand over the following packages to new 
maintainers. I will not orphan them if no one picks them up, but it would be 
great if someone with an interest in these packages could take them over.

backintime - backintime backup tool
elementary-icon-theme - Icons from the Elementary Project
elementary-xfce-icon-theme - Icons for Xfce based on the elementary Project 
Icon Theme
texstudio - A feature-rich editor for LaTeX documents

I am still using these, but the burden of doing package maintenance besides my 
day job and personal stuff is too high.

Thanks in advance for any volunteers

johannes
___
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: Please update Darktable to latest stable on Fedora 33

[Johannes Lips]

In defense of the maintainers, these build dates are right around f33 branching 
on August 11th, so perhaps that is the reason, why they've missed f33.

johannes
___
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: Enable EarlyOOM on Fedora KDE - Fedora 33 Self-Contained Change proposal

[Johannes Lips]

> Matthew Miller wrote:
> 
> Well, as I understand it, the main reason he is sending those private 
> replies is that he was banned from the mailing list, or put on moderation or 
> something.
> 
> If this mailing list were actually a place where people are allowed to voice 
> their technical criticisms without censorship, we would not have this 
> situation to begin with.
I think one of the major problems was, which is also evident in the above 
"private" mail, that it never was only technical and most of the time also 
included personal insults. I think since he was banned/moderated the overall 
climate on this mailing list improved considerably.

Johannes
> 
> Judging from the forwarded mail, I disagree with Harald on this particular 
> issue, but that does not mean I think we should not listen to his points.
> 
> Kevin Kofler
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://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 is preventing systemctl from read access on the file SecureBoot-8be4df61-93ca-11d2-aa0d-00e098032b8c.

[Johannes Lips]

Hi Joseph,

I am also affected by that bug and I think this is the relevant bug report.
https://bugzilla.redhat.com/show_bug.cgi?id=1800935

Cheers
Johannes
___
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: Allow comments and discussion even though an update was pushed to stable

[Johannes Lips]

> "Johannes Lips"  
> 
> We already have a tool for reporting issues and problems, and it's not
> bodhi.  If there's a problem with an already pushed update, it needs to
> be in bugzilla - where it's actually discoverable - not in bodhi, where
> it will go nowhere.
I am not intending to use bodhi as a bug tracker, but I would like to be able 
to reference issues, which were introduced with an update and I don't really 
see a lot of negative effects of this.
I think it's a way to make issues in bugzilla more easily traceable, since if 
an update is closely related with a new bug it is easier to just look into 
bodhi first and see if the issue affected others as well. If by chance the 
first reporter of a bug is too late in bodhi this connection is simply lost.
I don't see it as bodhi replacing bugzilla, but rather as an additional entry 
point, when looking for known issues in close relation with a bug.

Johannes
> 
> From the other side, as a maintainer, it is important to have as few
> channels for reporting issues as possible.  Keeping everything in one
> place is important so nothing gets lost, and it all can be queried and
> triaged appropriately.
> 
> Please do not use bodhi as a bug reporting tool.
> 
> Thanks,
> --Robbie
___
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

Allow comments and discussion even though an update was pushed to stable

[Johannes Lips]

Hi all,

I was recently bit by a bug, which was caused by a mismatch between 
texlive-biblatex and biber. The technical side is not so important, only so 
much that they need each other in a pretty specific version, which is not 
reflected on the rpm level.
What I found weird is that you can't comment on an update, which is already 
pushed to stable. A lot of users are only hit by a bug, once it reaches stable 
and then you don't have any possibility to highlight a bug report or an issue 
with this update. I would like to have the possibility to add such an 
information to an update, which introduced the issue.
Also I would like to ask if it is possible for important updates, like the 
texlive one to increase the stable karma. It really depends which mirrors you 
are using and if you are unlucky the updates get pushed to stable, before it 
reaches updates-testing for you and then again there's nothing to add, once 
it's pushed.

Thanks 
johannes
___
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

Informal Review Request

[Johannes Lips]

Hi all,

since backintime released a new, major update we need to transition away from 
Qt4 to Qt5. I would like to ask for an informal review on the newly created 
spec file. 
https://bugzilla.redhat.com/show_bug.cgi?id=1703680
Additionally, I would like to ask if we should get rid of the -common 
subpackage. Originally this was needed, because backintime offered several GUI 
options, but nowadays only one (Qt) is left, so actually there is no advantage 
of a -common package, because there aren't any GUIs, which share anything. 
Also please check if the Provides, Obsoletes stuff works, I've tested it on 
fedora 29 and all seems to be working.

Thanks in advance
Johannes
___
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

Orphaned some packages

[Johannes Lips]

Hi all,

due to lack of interest and upstream development I've orphaned the package:

devilspie: https://src.fedoraproject.org/rpms/devilspie
keybinder: https://src.fedoraproject.org/rpms/keybinder

I had a hard time finding out if there was any upstream activity at all 
and I think there are newer upstream projects.


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

Re: Intent to retire or orphan keybinder - python2 version

[Johannes Lips]

> On 29.8.2018 20:05, Johannes Lips wrote:
> 
> Try contacting the maintainers fo the dependent packages directly?
Well, I just did it this morning, let's see if there's some feedback. Otherwise 
I'll just proceed with the retirement process of the package.

Cheers
Johannes
___
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

Intent to retire or orphan keybinder - python2 version

[Johannes Lips]

Hi all,

since keybinder won't build on any fedora version >=29 and all functionality 
should be provided by the newer python3 keybinder3 package.
I would like to ask if it's ok to retire it, but since there are some packages 
depending on it, I would rather orphan it and let someone else take care of it. 
Packages depending on it:
dnf repoquery --whatrequires python2-keybinder
Last metadata expiration check: 0:29:57 ago on Mi 29 Aug 2018 19:31:04 CEST.
guake-0:0.8.8-4.fc28.noarch
kupfer-0:208-15.fc28.noarch
streamtuner-0:2.1.9-9.fc28.noarch

dnf repoquery --whatrequires keybinder
Last metadata expiration check: 0:30:10 ago on Mi 29 Aug 2018 19:31:04 CEST.
keybinder-devel-0:0.3.1-9.fc28.i686
keybinder-devel-0:0.3.1-9.fc28.x86_64
lxpanel-0:0.9.3-7.D20180305gitb85c71a6.fc28.i686
lxpanel-0:0.9.3-7.D20180305gitb85c71a6.fc28.x86_64
python2-keybinder-0:0.3.1-9.fc28.x86_64

FTBFS Bug:
https://bugzilla.redhat.com/show_bug.cgi?id=1604486
Upstream opinion:
https://github.com/kupferlauncher/keybinder/issues/14
___
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: [Proposal] Mass change: remove executing gtk-update-icon-cache in %post/%postu/%postrans to update hicolor theme cache

[Johannes Lips]

Well, of course, but the issue is not the change itself or anything. It's just 
the implementation and the lack of information for the maintainer. 
The maintainer just sees a git commit without additional information other than 
the scriplets are obsolete, which is not a lot to be honest. I would have 
preferred a heads-up, especially since it's nothing urgent.

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

Re: [Proposal] Mass change: remove executing gtk-update-icon-cache in %post/%postu/%postrans to update hicolor theme cache

[Johannes Lips]

Would have been nice to get some more background information than just the git 
commit message. Then one needs to do research to find this thread and the 
related ticket. I don't have time to follow all the discussions/tickets on 
devel or anywhere else, but this is even more time consuming. Especially, since 
it was just updated on the very same day, so actively maintained and I don't 
really see the need for a provenpackager to step in. Why not follow a more 
regular workflow with bug reports or whatever.

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

Re: Mass package change (python2- binary package renaming)

[Johannes Lips]

I would like to add, that apparently the capitalization of subpackages also 
changed. This broke dependencies for me. I don't know if this was intended. 
Please see:
https://bugzilla.redhat.com/show_bug.cgi?id=1485703
If it was intended, I am happy to fix this, otherwise please check your script 
to prevent more mistakes.

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

Re: Looking for co-maintainers - texstudio

[Johannes Lips]

> Hi Johannes,
> 
> as I'm experienced with Qt related stuff (member of KDE SIG too) and 
> also use TeXStudio as my default TeX editor all day, I requested commit 
> access now :)
You're hired! ;-)
> 
> Greetings,
> Christian
> 
> 
> On 12/08/2016 05:36 PM, Johannes Lips wrote:
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Looking for co-maintainers - texstudio

[Johannes Lips]

Dear list,

I would like to invite packagers with Qt experience to become co-maintainer on 
the texstudio package. I am pretty occupied with my day job and won't have time 
to delve into all details of Qt linking, which are currently not working 
properly, when building the package for fedora >24.
I hope someone can help me out with this bug [1], since apparently the users do 
use the software... ;-)

Thanks in advance,
johannes

[1] https://bugzilla.redhat.com/show_bug.cgi?id=1386665
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: OpenMPI binary only created on 64bit not on 32bit

[Johannes Lips]

> Am Mon, 28 Nov 2016 21:02:01 -0700
> schrieb Orion Poplawski  
> Seems to be more comlicated,than just the build-error.
> Nevertheless, "autoreconf ..." or "autoconf" does not work.
> Just for the build-fix:
> the newest upstream should have fixed the library-path problem, but the
> configure-script does not find mpi.h now.
> Here comes the full "%configure-call" (with your sources, not newest
> HEAD) that works for me:
> %configure--disable-static \
>   --disable-avx \
> %ifarch %{ix86}
> --with-mpi-include=/usr/include/openmpi-i386 \
> %endif
> --with-mpi-lib=%{_libdir}/openmpi/lib
> 
I've already was able to build it now with the explicit inclusion of those two 
paths, although I used %_arch instead of the if-statement. [1]
I also tried to use 
CC=mpicc
CXX=mpic++
FC=mpifort
but it didn't work properly. I've now managed to get working builds although 
somehow the requirements are not picked up properly, since I run into depcheck 
issues. Not sure what again causes this. 
Failing depcheck: 
https://taskotron.fedoraproject.org/artifacts/all/9e1ffb92-b5fc-11e6-bf8c-525400120b80/task_output/gretl-2016d-1.fc25.i386.log
Successful builds: http://koji.fedoraproject.org/koji/buildinfo?buildID=820579

I will of course move and rename the binary file, according to the wiki.

Thanks 
Johannes
[1] http://pkgs.fedoraproject.org/cgit/rpms/gretl.git/tree/gretl.spec
> 
> 
> But after reading the two answers above, that might be incorrect or
> unneeded. But it looks like the configure-script will fail without the
> change regardles of the used compiler.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: OpenMPI binary only created on 64bit not on 32bit

[Johannes Lips]

> Am 28.11.2016 09:51, schrieb Johannes Lips:
> 
> The pregenerated configure-script looks for libmpi.so in "/usr/lib 
> /usr/lib/openmpi /usr/lib64/openmpi/lib", but on i686 it's in 
> "/usr/lib/openmpi/lib".
> Regenerating the configure-script might work.
> Something like "autoreconf --force --install" in %prep after %setup.
> I can not test it at the moment (just windows-machines around me at 
> work).
Thanks a lot. I will try to regenerate the configure script, once I am back 
home. I also reported it back to upstream, since I am not sure if that's fedora 
specific.

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

OpenMPI binary only created on 64bit not on 32bit

[Johannes Lips]

Hi all,

I've been trying to build gretl with mpi support and I followed the guidelines 
in the wiki [1]. It apparently works, since I was able to build it on 64bit, 
which worked every time, but the 32bit build always fails to find the openmpi 
libraries, as can be seen from the build.log from the build in [2].
I would like to know if someone could check the spec file, if it's correct and 
tell me what's the issue with openmpi and why it can't be found on 32bit. 
The spec file I've been using can be found on my github.[3]

Thanks,
johannes

[1] https://fedoraproject.org/wiki/Packaging:MPI
[2] http://koji.fedoraproject.org/koji/taskinfo?taskID=16646986
[3] https://github.com/hannes101/gretl/blob/master/gretl.spec
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: F26 System Wide Change: Retire Synaptics Driver

[Johannes Lips]

> On Fri, 21 Oct 2016 09:17:08 +1000
> Peter Hutterer  
> 
> Yeah, I have never seen that here. 
> 
> Can you perhaps provide the information Oliver is asking for in the bug?
I've just tried libinput again and it seems to be working without any problems. 
Don't know what then was the problem.
Sorry for the noise!

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

Re: F26 System Wide Change: Retire Synaptics Driver

[Johannes Lips]

> On Thu, 20 Oct 2016 10:08:29 +0200
> Johannes Lips <johannes.lips(a)gmail.com wrote:
> 
> 
> Can you expand on how/what didn't work here?
> 
> I've been using it here with Xfce just fine since support was added...
> no particular problems here. 
Hi Kevin,
I think I was affected by this bug, basically natural scrolling was different 
across the gtk toolkits.
https://bugzilla.xfce.org/show_bug.cgi?id=11193

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

Re: F26 System Wide Change: Retire Synaptics Driver

[Johannes Lips]

On 20.10.2016 08:39, Jan Kurik wrote:

= Proposed System Wide Change: Retire Synaptics Driver =
https://fedoraproject.org/wiki/Changes/RetireSynapticsDriver

Change owner(s):
* Peter Hutterer 


Retire the xorg-x11-drv-synaptics driver and remove it from user's install.


== Detailed Description ==
xorg-x11-drv-synaptics has been the main X.Org touchpad driver for
over a decade. Since Fedora 22, it has been superseded by
xorg-x11-drv-libinput which aims to provide a better touchpad
experience.

The only way to assign X.Org drivers is via the xorg.conf.d
configuration system which is based on config file sort order. e.g.
evdev sorts as 10-evdev.conf, synaptics as 70-synaptics.conf, etc.
Whichever sorts last is assigned as driver for a device. Fedora 22 and
later shipped with libinput's config file sorting higher than all
other drivers to overwrite any previous matches.

Some users prefer the synaptics driver over libinput. This requires
the users to install the driver and then place a custom config snippet
or, more commonly, symlink to the synaptics config snippets with a
name that has a higher sort order than xorg-x11-drv-libinput.

The aim of this change is to ensure that the synaptics driver can
simply be installed when required without any further user
configuration. When installed, it should be assigned as the preferred
driver over xorg-x11-drv-libinput.

For historical reasons, a vast majority of users have the synaptics
driver installed, especially those updating from older releases.

We want to a) remove the xorg-x11-drv-synaptics driver from a user's
machine but b) make it possible to install where required.


== Scope ==
* Proposal owners:
- xorg-x11-drv-synaptics must be removed from comps (complete as of F25)
- xorg-x11-drivers must not include xorg-x11-drv-synaptics (complete as of F25)
- the X server needs to support a fallback input driver. This ensures
that when an xorg.conf snippet assigns the synaptics driver but that
driver is missing, the user still has a working touchpad. Complete as
of xorg-x11-server-1.18.4-5
- xorg-x11-drv-synaptics will get a subpackage
xorg-x11-drv-synaptics-legacy containing the actual driver
- xorg-x11-drv-libinput will obsolete/provide the current
xorg-x11-drv-synaptics version

* Other developers:
- packages that currently require xorg-x11-drv-synaptics need to
revisit and either require the new subpackage or drop the requirement
- Affected packages: mate-desktop, cinnamon-desktop
Afaik Xfce is also affected. I tried to switch to libinput and it did 
not really work well, especially the combination of Gtk3 and Gtk2.


- Johannes


* Release engineering: Nothing required, the RE changes are complete as of F25

* Policies and guidelines: No update needed

* Trademark approval: N/A (not needed for this Change)

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

Re: Gone upstream of nodm, so orphaning?

[Johannes Lips]

Why not retire it directly and properly? Just an idea ;-)
--
devel mailing list
devel@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org

Re: Large number of packages to be orphaned on Feb 26

[Johannes Lips]

> rpms/backintime -- Simple backup tool inspired from the Flyback
I've taken backintime, as always co-maintainers are highly welcome, since it 
needs quite a bit of work to get it up to date.

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

Non-responsive package maintainer process - backintime

[Johannes Lips]

Dear all,

I would like to formally send a mail requesting some feedback from cicku 
regarding the maintenance of the backintime package. 
There is one open bug, which requests an update [1] and additionally a trac 
ticket [2] was also opened, not by me.
I can see, that with an upgrade to later versions we'll loose the 
differentiation between a KDE and Gnome GUI, but I don't see why that really is 
an issue.
Additionally two request to become co-maintainer are unanswered so far, so I 
hope that we'll get that sorted pretty quick. 
Possibly there are some Chinese New Year festivities, so perhaps we'll give him 
some more time, but I would love to get some feedback.

Johannes

[1] https://bugzilla.redhat.com/show_bug.cgi?id=1186184
[2] https://fedorahosted.org/fesco/ticket/1542
--
devel mailing list
devel@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org

Re: Non-responsive package maintainer process - backintime

[Johannes Lips]

> On Fri, Feb 12, 2016 at 5:04 AM, Johannes Lips <johannes.lips(a)gmail.com 
> wrote:
> 
> Did you actually email cicku directly?  I don't see him on CC.
> 
Well, apparently I didn't add him to this e-mail, but he should have received 
enough notifications from bugzilla already. Additionally from someone who 
maintains more than 200 packages in fedora, I kind of expect that he is 
reachable within a reasonable time-frame. Otherwise it might be too much 
hassle, if something needs to be fixed.

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

Re: Non-responsive package maintainer process - backintime

[Johannes Lips]

> On Fri, Feb 12, 2016 at 1:48 PM, Johannes Lips <johannes.lips(a)gmail.com 
> wrote:
> 
> You make a lot of assumptions in that statement.  People filter email
> quite a bit and relying on bugzilla mail alone is not sufficient.
> 
> I find it ironic that your original email said "I would like to
> formally send a mail requesting some feedback from cicku.." but you
> didn't bother to email him directly.  That doesn't strike me as very
> formal.  I'm under no illusions that he is likely to respond to direct
> contact either, but it should at least be attempted.
> 
Why do I need to defend myself for following, perhaps not perfectly, the normal 
procedure in these cases and additionally I offered my help maintaining that 
package. 
I and another packager requested co-maintainership and are willing to help out, 
so I really don't see why I need to defend myself for the willingness to give 
up my valuable spare time.
Johannes
> josh
--
devel mailing list
devel@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org

Re: Retire a package from Fedora i686 (not x86_64)

[Johannes Lips]

Please leave this thread alone. Since numerous days, nothing about the 
original subject has been added.


--
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: Unresponsive maintainer : kanarip

[Johannes Lips]

Sorry to say, but this is like the hundredth time this topic came up.
https://lists.fedoraproject.org/pipermail/devel/2014-July/200860.html
-- 
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: Mozilla enabled ads in Firefox and they're active in Fedora

[Johannes Lips]

On Sat, Nov 15, 2014 at 6:56 PM, Christopher ctubbsii-fed...@apache.org
wrote:

 On Sat, Nov 15, 2014 at 9:34 AM, Rejy M Cyriac rcyr...@redhat.com wrote:

 On 11/15/2014 07:43 PM, Reindl Harald wrote:
 
  Am 15.11.2014 um 15:06 schrieb Kevin Kofler:
  Lars Seipel wrote:
  What does the community think of it? Is it okay for our flagship
  applications to carry ads and report tracking data?
 
  No!
 
  IMHO, we should consider dropping Firefox from Fedora entirely, in
  favor of
  Epiphany for Workstation and Midori for the Spins (except the KDE Spin
  which
  already ships Konqueror as the browser)
 
  NO!
 
  * i don't see that crap at all
  * even if i could disable it (or maybe have it in about:config)
  * i want to use Firefox for thousand reasons
 
  it's *not* freedom to remove Firefox
  freedom would be make it not default but still offer it
 
 
 
 +1

 Disabling the ADs feature from firefox, if that is possible, would be
 the right move for Fedora.

 We also could lobby mozilla to re-consider this decision.


 I don't really understand the issue at all. We also don't have any
problems offering google or any other search engine with our default
configuration in firefox. But if a truly open-source foundation implements
something to generate some revenue, which will most probably help the
development of open source software, it suddenly becomes a big deal?



 +1


 --
 Regards,

 Rejy M Cyriac (rmc)
 --
 devel mailing list
 devel@lists.fedoraproject.org
 https://admin.fedoraproject.org/mailman/listinfo/devel
 Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct



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

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

Please unblock tilda package in koji

[Johannes Lips]

Hi all,

could someone from the Rel-Eng team please unblock the tilda package? I
already opened a ticket with the request and I am not sure how long I'll
have to wait until it gets unblocked. [1]

-johannes

[1] https://fedorahosted.org/rel-eng/ticket/6018
-- 
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: No more deltarpms by default

[Johannes Lips]

On Mon, Oct 6, 2014 at 10:41 AM, Rahul Sundaram methe...@gmail.com wrote:

 Hi

 One of the long standing features that were enabled by default in yum is
 support for delta rpms.  dnf developers have disabled this and I think this
 change deserves a broader discussion

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

 I don't know if this really will happen, but when I read this I had to
think about this discussion.
http://uk.reuters.com/article/2014/10/22/uk-hungary-internet-tax-idUKKCN0IB0RI20141022


So deltarpm might be a way of actually saving money ;-)

-johannes


 Rahul

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

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

Re: Attempting to contact two unresponsive maintainers - dajt and jpacner

[Johannes Lips]

On Wed, Sep 3, 2014 at 10:44 PM, Kevin Fenzi ke...@scrye.com wrote:

 Greetings, we've been told that the email addresses for two package
 maintainers are no longer valid.  I'm starting the unresponsive
 maintainer policy to find out if they are still interested in
 maintaining their packages (and if so, have them update their email
 addresses in FAS).  If they're not interested in maintaining or we
 can't locate them I'll have FESCo orphan the packages so that others
 can take them over.

Hi all,

wouldn't it make sense to integrate a check into the processes, when people
leave Redhat, that the packages in fedora are properly orphaned or get a
new owner?
I mean this should be pretty easy to implement in a company, or?

All the best,

Johannes


 If you have a way to contact any of these maintainers, please let them
 know that we'd appreciate knowing what to do with their packages.
 Thanks!

 Maintainers:

 * jpacner - former email address jpac...@redhat.com
   https://admin.fedoraproject.org/pkgdb/packager/jpacner
   Point of contact: 0
   Co-maintainer:5
   Watched:  0

 * dajt - former email address fenla...@redhat.com
   https://admin.fedoraproject.org/pkgdb/packager/dajt
   Point of contact: 6
   Co-maintainer:3
   Watched:  0

 If we don't hear anything in a week, we will be removing their acls and
 will need to find new point of contacts, etc.

 Thanks,

 kevin

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

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

Re: Attempting to contact two unresponsive maintainers - dajt and jpacner

[Johannes Lips]

On Thu, Sep 4, 2014 at 12:04 PM, Pierre-Yves Chibon pin...@pingoured.fr
wrote:

 On Thu, Sep 04, 2014 at 11:35:43AM +0200, Johannes Lips wrote:
 On Wed, Sep 3, 2014 at 10:44 PM, Kevin Fenzi ke...@scrye.com wrote:
 
   Greetings, we've been told that the email addresses for two package
   maintainers are no longer valid.A  I'm starting the unresponsive
   maintainer policy to find out if they are still interested in
   maintaining their packages (and if so, have them update their email
   addresses in FAS).A  If they're not interested in maintaining or we
   can't locate them I'll have FESCo orphan the packages so that others
   can take them over.
 
 Hi all,
 
 wouldn't it make sense to integrate a check into the processes, when
 people leave Redhat, that the packages in fedora are properly
 orphaned or
 get a new owner?
 I mean this should be pretty easy to implement in a company, or?

 To my understanding, this is the problem: when someone leaves Red Hat
 either
 they deal with their package on their own (for example by simply changing
 their
 email address in FAS and creating the corresponding bugzilla account) or
 they
 don't.
 If they don't we get an automated email saying that the person has left
 and thus
 that the email is no longer valid.
 The thing that we actually do not know if whether the person is still
 interesting in contributing to Fedora. Sometime that's the case and they
 just
 say so, fix FAS and bugzilla and it's all good. Sometime that's not the
 case and
 then we need to orphan their packages and let someone else take it over.

 So all we can do is, when we get an email saying someone left, ask if
 someone
 know what they want to do with regards to their Fedora packages.


 Maybe it would be good to ask Red Hat to include Fedora in their final
 interview
 or so, but since contributing to Fedora is for a lot of people a wish and
 not a
 job, it might be missed quite often.

Well yeah I thought about something along this line, because in the those
cases we do have the possibility to deal with it before the person actually
leaves and it would make the whole process a bit easier, because we could
then act proactively.

Johannes


 Again, that is my understanding of the situation.

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

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

Re: Compiling with system hunspell - texmaker

[Johannes Lips]

On Thu, Aug 7, 2014 at 4:22 AM, Mukundan Ragavan 
nonamed...@fedoraproject.org wrote:

 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA512


 Hi All,

 I am trying to update Texmaker from version 4.2 to 4.3 and I have run
 into a problem I am unable to solve. Here it is -

 The source tarball has a directory hunspell which is removed in %prep
 and system hunspell libraries are used instead. This works without any
 problems with version 4.2. However, in 4.3, I get

 WARNING: Failure to find: hunspell/affentry.cxx
 WARNING: Failure to find: hunspell/affixmgr.cxx
 WARNING: Failure to find: hunspell/csutil.cxx
 WARNING: Failure to find: hunspell/dictmgr.cxx
 WARNING: Failure to find: hunspell/hashmgr.cxx

 [ ... ] {complete list of files removed}

 The compilation happens and fails with the following error -

 make: *** No rule to make target 'hunspell/affentry.cxx', needed by
 '.obj/affentry.o'.  Stop.


 qmake is used to compile texmaker by doing

 %{_qt5_qmake} -unix texmaker.pro

 As for differences in the texmaker.pro file, there is only one
 difference -

 - --- texmaker-4.2/texmaker.pro 2014-04-24 09:15:57.0 -0500
 +++ texmaker-4.3/texmaker.pro   2014-07-28 23:02:06.0 -0500
 @@ -10,7 +10,7 @@
  }

  CONFIG += qt warn_off release
 - -TEXMAKERVERSION=4.2
 +TEXMAKERVERSION=4.3
  DEFINES += TEXMAKERVERSION=\\\$${TEXMAKERVERSION}\\\
  DEFINES += HAVE_SPLASH


 I have tried adding CONFIG += enable-hunspell, LIBS += -lhunspell,
 etc. No use. I am just unable to build with hunspell. :(

 BuildRequires: hunspell-devel is present.

 Could someone help me out here please?

Hi Mukundan,

since I have the same issue with texstudio, which started as a fork of
texmaker, please take a look at the patch
https://apps.fedoraproject.org/packages/texstudio/sources/
http://pkgs.fedoraproject.org/cgit/texstudio.git/tree/texstudio-use-system-hunspell-instead-of-bundled-one.patch

I hope this helps!

Johannes



 Thanks!
 Mukundan.
 - --
 GPG key-ID: 00E8658D
 
 -BEGIN PGP SIGNATURE-
 Version: GnuPG v2

 iQIcBAEBCgAGBQJT4uLjAAoJEIfjPv0A6GWNo/cQALzE2Bnw5ppwigfvRwDf/hDf
 7WUBK/nFEVJpCTVj7a0CSkEJq2wDZbJvrRy5WJWC2sEsXwJNyA6KWQlXa2UrzGwe
 NSmFDBzQUMf472AmLU5tMKc/SrrdRGt+/seA7nAsPu4crBc9gRG7nqa53GGpss9r
 Po8sxL2kznoFqcnXFQWEMNzgIWM7b+l+jF9nijKR6qL3U9vgwtA0QvgEBwWvIoLg
 5qM5PvdsiGVewulD7GnDE1K8BD7Stq39vCZr3UwkbBJbMLCDehEzfhN7T+u5JF97
 OyHwDNgLWvwqK+yZUpI18WXz09lTYIXb72Ml7NfPvOj35CLomthJ/5FIROz+PfbX
 wAhDhaIAyCX2kbty3tfcWchYxlZ5qRd1HXBkeFLHxm1bfin5dpp6rMoFv/M2I29r
 9lQtkNdlmPcYgoZC6STCVoDHp6IOMSVAD/4Pxq2A4Ps5Bqfz/bSZViuPX57IJEq8
 R20Pyxo9kMPHRFhfa/shjGxc5tYLnDsg2OxHuaXlL2v6UZgIHkIzRnee71KknrOG
 iBoQDVQ7wN/RPKXtlfcWIquj4SPkwx5HYEiR+X0fvygDu6mYc26zIJeYEJ33BG0q
 TJUng3HaavrTg2s+F7uKDL1a5vbL5y6AkkH7MOJOXZM3GvppfINaxGuhVEb34IIZ
 Sds8IL3bG4GVqP15zXFf
 =0LtK
 -END PGP SIGNATURE-
 --
 devel mailing list
 devel@lists.fedoraproject.org
 https://admin.fedoraproject.org/mailman/listinfo/devel
 Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
-- 
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: Contact info - Jeroen van Meeuwen (kanarip)

[Johannes Lips]

On Wed, Aug 6, 2014 at 10:53 AM, Jan Rusnacko jrusn...@fedoraproject.org
wrote:

 Hello,

 following the policy for nonresponsive maintainers, does anyone have a
 contact of Jeroen van Meeuwen (kanarip) ? All three mail addresses listed
 here http://fedoraproject.org/wiki/User:Kanarip bounce back, including
 FAS email kana...@kanarip.com.

 He is a co-maintainer of quite a number of packages (
 https://admin.fedoraproject.org/pkgdb/packager/kanarip/), which now have
 ~20 unfixed vulnerabilities combined in EPEL, some of them for over a year.

 Hello,

this must be the second or third time we have issues contacting him.
Wouldn't it now be time to finally go ahead and orphan all his packages?
I mean he had time to respond and tried quite a lot to get in touch with
him. [1]

Johannes

[1] https://lists.fedoraproject.org/pipermail/devel/2014-July/200860.html

Thank you!
 --
 Jan Rusnacko, Fedora Security Team
 --
 devel mailing list
 devel@lists.fedoraproject.org
 https://admin.fedoraproject.org/mailman/listinfo/devel
 Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
-- 
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: Unresponsive maintainer: kanarip

[Johannes Lips]

On Wed, Jul 16, 2014 at 7:54 PM, Pierre-Yves Chibon pin...@pingoured.fr
wrote:

 On Wed, Jul 16, 2014 at 10:08:13AM -0600, Orion Poplawski wrote:
  On 07/16/2014 03:10 AM, Pierre-Yves Chibon wrote:
  On Wed, Jul 16, 2014 at 11:00:16AM +0200, Vít Ondruch wrote:
  
  Well, I contacted kanarip off-list and he responded that somebody else
  should supposedly fix this for him.
  
  So as always, he is not completely unresponsive ...
  
  On the infra side we have not seen his emails bounce for few days
 already.
  
  
  Pierre
  
 
  I just got one yesterday:
 
  Reporting-MTA: dns; bastion01.phx2.fedoraproject.org
  X-Postfix-Queue-ID: D5C40215B8
  X-Postfix-Sender: rfc822; or...@fedoraproject.org
  Arrival-Date: Tue, 15 Jul 2014 23:03:25 + (UTC)
 
  Final-Recipient: rfc822; kana...@kanarip.com
  Original-Recipient: rfc822;cobbler-ow...@fedoraproject.org
  Action: failed
  Status: 5.4.4
  Diagnostic-Code: X-Postfix; Host or domain name not found. Name service
 error
  for name=kanarip.com type=A: Host found but no data record of
 requested
  type
 
 
  And indeed I can't find any A or MX records for kanarip.com.  I'm not
 sure
  how it's supposed to be someone else's responsibility to fix his email
  address in FAS.

 I assume the fix is to be applied not in FAS but at the DNS/domain level.

Well but you could change the FAS address to a working one, so that it
doesn't bounce, no?


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

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

Re: Unresponsive maintainer: kanarip

[Johannes Lips]

On Thu, Jul 17, 2014 at 11:21 AM, Pierre-Yves Chibon pin...@pingoured.fr
wrote:

 On Thu, Jul 17, 2014 at 11:02:57AM +0200, Johannes Lips wrote:
 On Wed, Jul 16, 2014 at 7:54 PM, Pierre-Yves Chibon 
 pin...@pingoured.fr
 wrote:
 
   On Wed, Jul 16, 2014 at 10:08:13AM -0600, Orion Poplawski wrote:
On 07/16/2014 03:10 AM, Pierre-Yves Chibon wrote:
On Wed, Jul 16, 2014 at 11:00:16AM +0200, VAt Ondruch wrote:

Well, I contacted kanarip off-list and he responded that
 somebody
   else
should supposedly fix this for him.

So as always, he is not completely unresponsive ...

On the infra side we have not seen his emails bounce for few days
   already.


Pierre

   
I just got one yesterday:
   
Reporting-MTA: dns; bastion01.phx2.fedoraproject.org
X-Postfix-Queue-ID: D5C40215B8
X-Postfix-Sender: rfc822; or...@fedoraproject.org
Arrival-Date: Tue, 15 Jul 2014 23:03:25 + (UTC)
   
Final-Recipient: rfc822; kana...@kanarip.com
Original-Recipient: rfc822;cobbler-ow...@fedoraproject.org
Action: failed
Status: 5.4.4
Diagnostic-Code: X-Postfix; Host or domain name not found. Name
   service error
A  A  for name=kanarip.com type=A: Host found but no data record
 of
   requested
A  A  type
   
   
And indeed I can't find any A or MX records for kanarip.com. A
 I'm not
   sure
how it's supposed to be someone else's responsibility to fix his
 email
address in FAS.
 
   I assume the fix is to be applied not in FAS but at the DNS/domain
   level.
 
 Well but you could change the FAS address to a working one, so that it
 doesn't bounce, no?

 Assuming we would agree to change someone's personal information, how
 would we
 know which email to change it to ?

Of course I meant, that he should change it himself. If he doesn't show any
interest in his packages, why not just simply orphan them?
Johannes



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

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

Re: dnf even allows to uninstall RPM and systemd without warnings

[Johannes Lips]

Chris Adams wrote:
 Once upon a time, Reindl Harald h.rei...@thelounge.net said:
 without that protection any what is that, i don't need it
 and try to remove it brings the danger to ruin the setup
 
 And the protection is already there - the list of dependent packages
 that will be removed, followed by a confirmation request that you really
 want to do that.
Well, yeah and everybody is reading the complete output of yum/dnf if
it's trying to remove hundreds of packages?
I really don't see why we should remove automatic safety measures if
they were available for some time and are in such cases really useful.

Johannes

 

-- 
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: dnf even allows to uninstall RPM and systemd without warnings

[Johannes Lips]

Chris Adams wrote:
 Once upon a time, Johannes Lips johannes.l...@gmail.com said:
 Well, yeah and everybody is reading the complete output of yum/dnf if
 it's trying to remove hundreds of packages?
 
 Well, yeah.  First, if you think you are removing a leaf or minor
 package and the package manager lists 100+ dependent packages, you
 should take notice and perhaps re-think what you are trying to do.
 Second, if you decide you want to continue, you should look over the
 list of packages to be removed.
Of course, but how fast can a small three letter work like yum or dnf
can be overlooked?
I don't really see any benefit of not implementing it, if it makes an
installation safer.
But this whole discussion is pointless, because the people, who do the
work will most likely decide the outcome!

 
 If people really want some magic protections in this case, rather than
 having special packages, it should probably be based on the number of
 affected dependent packages (and/or maybe a percentage of installed
 packages).
 

-- 
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: dnf even allows to uninstall RPM and systemd without warnings

[Johannes Lips]

Les Howell hlhow...@pacbell.net wrote on Mon 23 Jun 2014 20:04:56 CEST:
 On Mon, 2014-06-23 at 19:57 +0200, Johannes Lips wrote:
 Chris Adams wrote:
 Once upon a time, Johannes Lips johannes.l...@gmail.com said:
 Well, yeah and everybody is reading the complete output of yum/dnf if
 it's trying to remove hundreds of packages?

 Well, yeah.  First, if you think you are removing a leaf or minor
 package and the package manager lists 100+ dependent packages, you
 should take notice and perhaps re-think what you are trying to do.
 Second, if you decide you want to continue, you should look over the
 list of packages to be removed.
 Of course, but how fast can a small three letter work like yum or dnf
 can be overlooked?
 I don't really see any benefit of not implementing it, if it makes an
 installation safer.
 But this whole discussion is pointless, because the people, who do the
 work will most likely decide the outcome!


 If people really want some magic protections in this case, rather than
 having special packages, it should probably be based on the number of
 affected dependent packages (and/or maybe a percentage of installed
 packages).


 
 The good news is that for dnf you can become a developer and then work
 from the group to make it do what you want.  I am sure that your
 experience and knowledge will be a welcome addition to the team.
What's the point of personal insults? I just stated my opinion, no need
to get personal with ironic comments!

 
 

-- 
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: Current FTBFS packages (was Re: [ACTION REQUIRED] Retiring packages for Fedora 21)

[Johannes Lips]

Till Maas wrote:
 
 The following packages did not build for two releases (no new build
 since 2013-07-25) and will be retired when Fedora (F21) is branched,
 unless someone successfully builds them till then.  If you know for sure
 that the package should be retired, please do so now with a proper
 reason:
 https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life
 
 According to https://fedoraproject.org/wiki/Schedule branching will
 occur not earlier than 2015-07-08. The packages will be retired shortly
 before.
 
Package(co)maintainers   
 ===
[...]
 keybinderhannes, hannes   
fixed in rawhide and f20
[...]
 The script creating this output is run and developed by Fedora
 Release Engineering. Please report issues at its trac instance:
 https://fedorahosted.org/rel-eng/
 The sources of this script can be found at:
 https://git.fedorahosted.org/cgit/releng/tree/scripts/find_unblocked_orphans.py
 

-- 
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: Orphaning most of my packages

[Johannes Lips]

On Thu, Apr 24, 2014 at 2:49 PM, Jon Ciesla limburg...@gmail.com wrote:




 On Thu, Apr 24, 2014 at 7:46 AM, Stanislav Ochotnicky 
 sochotni...@redhat.com wrote:


 I am doing spring cleanup and getting rid of most of my packages. The
 full list is a bit too long (mizdebsk agreed to take over all of my Maven
 related packages as primary maintainer). Here's the remaining bits that
 need a new home:

  * plotutils
  * python-gudev
  * python-icalendar


 I'll take python-icalendar, I need it for timeline.

 Thanks,
 J


  * python-webdav-library
  * freemind

 freemind would need some considerable amount of work, because it's already
several versions behind upstream. It's sad to see, but it's hard to package
java stuff.
I think best would be to either update it or just retire it properly,
although a lot of my work might be lost.

Johannes



 --
 Stanislav Ochotnicky sochotni...@redhat.com
 Software Engineer - Developer Experience

 PGP: 7B087241
 Red Hat Inc.   http://cz.redhat.com

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




 --
 http://cecinestpasunefromage.wordpress.com/
 
 in your fear, seek only peace
 in your fear, seek only love

 -d. bowie

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

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

Re: Fedora.NEXT Products and the fate of Spins

[Johannes Lips]

On Thu, Jan 30, 2014 at 2:33 PM, Frank Murphy frankl...@gmail.com wrote:

 On Thu, 30 Jan 2014 14:15:56 +0100
 Tomasz Torcz to...@pipebreaker.pl wrote:

  Personally I always felt that this symbiotic relationship was a big
  part of
   what made Fedora interesting.
 
Yes, but please don't paint Red Hat bussiness goals as Fedora
  community goals. There is some intersection, but not equality.

 I would love to see alt Desktops stay,
 but at the end of the day.
 The old saying comes to mind:

 http://dictionary.cambridge.org/dictionary/british/he-who-pays-the-piper-calls-the-tune

 That's a fact of life in any business relationship.

Well, but it's not only about money and a lot of contributors use their
spare time to contribute, so I wouldn't stress this money thing too much.







 ___
 Regards,
 Frank
 www.frankly3d.com

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

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

Re: VOB

[Johannes Lips]

On Thu, Nov 28, 2013 at 12:36 AM, Richard Vickery 
richard.vicker...@gmail.com wrote:

 Being on the test kernel - or, more likely, using a more stable one from
 the list that is compiled - is probably the answer to the issue: how am I
 to watch a VOB file?

This has nothing to do with the kernel and especially not with the -devel
list. Please just use the search engine you prefer to find out how to play
VOB files


 Linux 3.11.9-300.fc20.x86_64 #1 SMP Wed Nov 20 22:23:25 UTC 2013 x86_64

 Thanks
 --
 Richard

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

-- 
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: Orphaning of freemind and all my remaining Java packages

[Johannes Lips]

On Sat, Aug 24, 2013 at 11:43 AM, Johannes Lips johannes.l...@gmail.comwrote:

 Hi all,

 I finally came to the conclusion, that I no longer want to invest time and
 effort in keeping all my Java packages in good shape. I don't have the time
 anymore to unbundle all the bundled libraries and keep a dozen downstream
 patches to make it work.
 freemind is close to a 1.0.0 release and I provided packages for that
 already in a small side repo [1].
 There are also some review requests for additional libraries [2],[3].

 So I will orphan the packages next week and will block them if no one
 applies for taking them over.

 - freemind
 - SimplyHTML
 - jansi
 - jansi-native
 - jarbundler
 - jibx
 - xpp3

Ok, so I am going to orphan the remaining packages:
- SimplyHTML
- freemind

Perhaps someone is willing to pick them up.

- Johannes


 I hope someone will take good care of them.

 Johannes



 [1] 
 http://repos.fedorapeople.org/**repos/hannes/freemind-1.0.0/http://repos.fedorapeople.org/repos/hannes/freemind-1.0.0/
 [2] 
 https://bugzilla.redhat.com/**show_bug.cgi?id=923960https://bugzilla.redhat.com/show_bug.cgi?id=923960
 [3] 
 https://bugzilla.redhat.com/**show_bug.cgi?id=923959https://bugzilla.redhat.com/show_bug.cgi?id=923959

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

Orphaning of freemind and all my remaining Java packages

[Johannes Lips]

Hi all,

I finally came to the conclusion, that I no longer want to invest time 
and effort in keeping all my Java packages in good shape. I don't have 
the time anymore to unbundle all the bundled libraries and keep a dozen 
downstream patches to make it work.
freemind is close to a 1.0.0 release and I provided packages for that 
already in a small side repo [1].

There are also some review requests for additional libraries [2],[3].

So I will orphan the packages next week and will block them if no one 
applies for taking them over.


- freemind
- SimplyHTML
- jansi
- jansi-native
- jarbundler
- jibx
- xpp3

I hope someone will take good care of them.

Johannes



[1] http://repos.fedorapeople.org/repos/hannes/freemind-1.0.0/
[2] https://bugzilla.redhat.com/show_bug.cgi?id=923960
[3] https://bugzilla.redhat.com/show_bug.cgi?id=923959
--
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: Changes to make MySQL vs. MariaDB less confusing

[Johannes Lips]

On Fri, Aug 23, 2013 at 9:40 AM, James Hogarth james.hoga...@gmail.comwrote:

 On 22 August 2013 08:27, Bjorn Munch bjorn.mu...@oracle.com wrote:


 Yes we are! Sorry for the long silence. The window for F19 closed so
 it became less urgent, then I had vacation, was sick, then others here
 were on vacation but we're all here now and I shall be uploading new
 packages with MySQL 5.6.13 very soon. They are already ready
 internally, but I need to do some final checks and a scratch build. I
 was indeed planning to do that today anyway.

 I will get back with more details later.


 It's this sort of behaviour that leads many of us to want to wash our
 hands of Oracle in the first place...

Sorry to say, but to me it rather sounds just plain human.



 As for the 'window for F19' well you've missed the window for F20 now as
 well ...

 However that is somewhat of a moot point given that (and the AOO issues
 are similar but let's stay focused on mysql/mariadb) things like spec
 files, package reviews and so on don't need a release to target anyway -
 they just need bugzilla tickets and builds in koji following the standard
 packaging guidelines that everyone - big company or little individuals -
 need to follow.

 Once things are building cleanly there and package review is passed (and
 any outstanding conflict questions are dealt with) then fine look at adding
 it as a feature for a future Fedora - but that is a long way off at this
 point still it seems.

 Frankly I'm still of the opinion the Oracle distribution of the MySQL
 based server should be dropped entirely... If Oracle want 'community-mysql'
 to exist for Fedora and want to maintain it themselves then they can set up
 their own repositories on their own infrastructure and these
 compatibilities issues with Fedora can be removed entirely as a result.

 As for an upgrade of community-mysql from 5.5 to 5.6 that should probably
 be discussed or be considered as a feature in case of knock on issues with
 respect to F18 users upgrading (didn't the obsolete for mariadb only cover
  5.5?) plus the loss of file level compatibility for someone to make a
 switch between community-mysql and mariadb at their choosing... plus
 there's a lot of non-backwards compatible changes that people need to be
 aware of from 5.5 to 5.6:

 http://dev.mysql.com/doc/refman/5.6/en/upgrading-from-previous-series.html





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

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

Re: mass rebuild update

[Johannes Lips]

On Mon, Aug 5, 2013 at 11:22 AM, Peter Robinson pbrobin...@gmail.comwrote:

  On Sun, 2013-08-04 at 21:35 -0500, Dennis Gilmore wrote:
  There is a large number of failures[1] that need to be
  addressed.
 
  I don't know if this is just a coincidence, but the links to log files
  in the filled FTBFS bug reports don't work.
 
  Here are two examples (from my FTBFS bugs):
  https://bugzilla.redhat.com/show_bug.cgi?id=992784
  https://bugzilla.redhat.com/show_bug.cgi?id=992018

 Why don't you just go to koji and have a look at it directly there.

Of course one could do that, but then if you put the links there, they
should work.

Johannes


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

-- 
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: Obsoleting ConsoleKit once and for all

[Johannes Lips]

On Tue, Jul 30, 2013 at 11:59 PM, Lennart Poettering
mzerq...@0pointer.dewrote:

 BOn Tue, 30.07.13 16:14, Dan Williams (d...@redhat.com) wrote:

  On Tue, 2013-07-30 at 23:03 +0200, Lars Seipel wrote:
   On Tue, Jul 30, 2013 at 04:28:55PM +0200, Christoph Wickert wrote:
thunar and pcmanfm are file managers and require ConsoleKit for
 handling
removable storage.
  
   Are you sure you aren't confusing this with something? HAL maybe?
 
  There's some interaction with ConsoleKit to ensure that the removable
 1;3406;0c storage is tied to a specific session so that the logged-in
 user can
  actually modify their USB drive.  Otherwise it's only accessible to
  'root'.
 
  So yes, something *else* (HAL, udisks, etc) actually handles the
  mounting, but there's some other components involved in permissions and
  mount location, and that's where ConsoleKit helps out.

 But that's stuff that is hidden beneath udev/udisks not sure why a file
 manager needs to know that...

There is some stuff regarding thunar on this blog post by one of the thunar
developers:
http://gezeiten.org/post/2011/01/Xfce-4.8-on-BSD-flavors

Johannes


 Lennart

 --
 Lennart Poettering - Red Hat, Inc.
 --
 devel mailing list
 devel@lists.fedoraproject.org
 https://admin.fedoraproject.org/mailman/listinfo/devel
 Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

-- 
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: More unhelpful update descriptions

[Johannes Lips]

On Wed, Jul 3, 2013 at 9:32 AM, drago01 drag...@gmail.com wrote:

 On Mon, Jul 1, 2013 at 11:54 PM, Dan Mashal dan.mas...@gmail.com wrote:
  On Mon, Jul 1, 2013 at 2:52 PM, Pierre-Yves Luyten p...@luyten.fr wrote:
  Not sure if it makes any sense but maybe could we have something like
  freeze tag changes until desc is better.
 
  I propose this because testers will not _really_ want to -1 karma, and
  as a maintainer it might be a bit hard, but with a good reminder like
  not pushed to stable until desc is better I would have made less
  mistakes
 
  yes not being reminded is not an excuse and such proposal would not save
  time, still I believe it could help more than hurt
 
 
  There is already a perfect example of this.
 
 
 https://admin.fedoraproject.org/updates/FEDORA-2013-11846/selinux-policy-3.12.1-57.fc19

 This is also a perfect example of useless does not fix bug x karma.
 If it is not *worse* then the previous package there is no reason to
 give it negative karma.

If it doesn't fix the bugs, the update should fix, it is appropriate to
give negative karma. Otherwise the bugs would be closed, when it becomes
stable, but won't be fixed.

Johannes

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

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

Re: More unhelpful update descriptions

[Johannes Lips]

On Wed, Jul 3, 2013 at 9:47 AM, Michael Scherer m...@zarb.org wrote:

 Le mercredi 03 juillet 2013 à 09:44 +0200, Johannes Lips a écrit :
 
 
 
  On Wed, Jul 3, 2013 at 9:32 AM, drago01 drag...@gmail.com wrote:
  On Mon, Jul 1, 2013 at 11:54 PM, Dan Mashal
  dan.mas...@gmail.com wrote:
   On Mon, Jul 1, 2013 at 2:52 PM, Pierre-Yves Luyten
  p...@luyten.fr wrote:
   Not sure if it makes any sense but maybe could we have
  something like
   freeze tag changes until desc is better.
  
   I propose this because testers will not _really_ want to -1
  karma, and
   as a maintainer it might be a bit hard, but with a good
  reminder like
   not pushed to stable until desc is better I would have
  made less
   mistakes
  
   yes not being reminded is not an excuse and such proposal
  would not save
   time, still I believe it could help more than hurt
  
  
   There is already a perfect example of this.
  
  
 
 https://admin.fedoraproject.org/updates/FEDORA-2013-11846/selinux-policy-3.12.1-57.fc19
 
 
  This is also a perfect example of useless does not fix bug x
  karma.
  If it is not *worse* then the previous package there is no
  reason to
  give it negative karma.
  If it doesn't fix the bugs, the update should fix, it is appropriate
  to give negative karma. Otherwise the bugs would be closed, when it
  becomes stable, but won't be fixed.

 That's not what the guidelines say :


 https://fedoraproject.org/wiki/QA:Update_feedback_guidelines#Update_does_not_fix_a_bug_it_claims_to

Could be, but if the still broken bugs are going to be closed, when the
update becomes stable, doesn't really help, or? Given that this is enabled
in the update.




 --
 Michael Scherer

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

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

Re: More unhelpful update descriptions

[Johannes Lips]

Richard W.M. Jones wrote:

Since this topic comes up every few months, and no one's pointed
out the obvious answer yet, I'll say it:

* Instead of making up more rules, make the tooling better so
we don't have to repeat update descriptions in multiple places. *
Wouldn't it make sense to perhaps apply different rules or policies for 
different types of packages? I mean we could focus on those applications 
a regular user sees, like all the Office, Internet and Multimedia apps.
And make the rules for libs and all that stuff, normally only devs are 
interested in, less strict.
So we always write update comments with the respective target audience, 
making them less technical for all the userspace applications and so on.
On the other hand, bodhi probably can't distinguish between those two 
types of packages, or?


Johanens


Rich.



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

Re: Intent to orphan elementary-icon-theme

[Johannes Lips]

Christopher Meng wrote:

I can take it because I love elementary's things.

Ok, it's orphaned now. Thanks and take good care of it :-)

-Johannes




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

Intent to orphan elementary-icon-theme

[Johannes Lips]

Hi all,

I am going to orphan the elementary-icon-theme, because it's of no use 
to me. They dropped all the symlinks to make it compatible with other 
desktops than Gnome3. So anyone interested is invited to take over.

Currently there is one open bug, where a user requests an update.

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

Thanks a lot

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

Orphaning link-grammar

[Johannes Lips]

Hi all,

I am going to orphan link-grammar in a short while, because I actually 
have absolutely no use for it and I don't recall, why I picked it up in 
the first place.

So please anyone interested in abiword might want to pick it up.

Thanks a lot!

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

Re: Orphaning link-grammar

[Johannes Lips]

Jon Ciesla wrote:




On Wed, May 15, 2013 at 1:45 PM, Johannes Lips johannes.l...@gmail.com
mailto:johannes.l...@gmail.com wrote:

Hi all,

I am going to orphan link-grammar in a short while, because I
actually have absolutely no use for it and I don't recall, why I
picked it up in the first place.
So please anyone interested in abiword might want to pick it up.

Thanks a lot!

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


I'll take it when you orphan it, unless someone else jumps it.

I orphaned it, just now!

Thanks a lot for taking over!

Johannes


-J

--
http://cecinestpasunefromage.wordpress.com/

in your fear, seek only peace
in your fear, seek only love

-d. bowie




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

Re: Orphaning link-grammar

[Johannes Lips]

Johannes Lips wrote:

Jon Ciesla wrote:




On Wed, May 15, 2013 at 1:45 PM, Johannes Lips johannes.l...@gmail.com
mailto:johannes.l...@gmail.com wrote:

Hi all,

I am going to orphan link-grammar in a short while, because I
actually have absolutely no use for it and I don't recall, why I
picked it up in the first place.
So please anyone interested in abiword might want to pick it up.

Thanks a lot!

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


I'll take it when you orphan it, unless someone else jumps it.

I orphaned it, just now!

Sorry forgot all the other branches!
Just orphaned it in them as well.


Thanks a lot for taking over!

Johannes


-J

--
http://cecinestpasunefromage.wordpress.com/

in your fear, seek only peace
in your fear, seek only love

-d. bowie






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

Re: Idea: {Gnome,KDE,Xfce,...} Minimal Desktop groups

[Johannes Lips]

On Mon, Apr 29, 2013 at 4:58 PM, Sandro Mani manisan...@gmail.com wrote:




 On Mon, Apr 29, 2013 at 4:55 PM, Rich Mattes richmat...@gmail.com wrote:


 On Mon, Apr 29, 2013 at 9:07 AM, Sandro Mani manisan...@gmail.comwrote:

 So, what about creating groups for the various desktop environments
 which pull in basesystem + xorg + mesa drivers + displaymanager + bare
 desktop shell?


 Do the groups already provided in comps.xml[1] not work for this task?

 Currently, one can use yum's groupinstall option to install the gnome,
 kde, xfce, lxde, mate, and cinnamon desktops and desktop environments.

 Rich


 Well, those groups are not exactly minimal.

I also really like the idea, because I just recently had this issue. I got
a bug report, that one of my packages was not working properly under Gnome,
but I didn't want to install the whole Gnome Desktop group, because this
would be a real overkill for just checking the functionality of a program
on a different desktop.
So yes, I definitely would love more minimal desktop groups without all the
apps, for which I most probably already have working alternatives.

Johannes


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

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

Re: Smock successor?

[Johannes Lips]

On Thu, Apr 4, 2013 at 2:44 PM, Till Maas opensou...@till.name 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/

I think there is mockchain, which should do the same thing, or?
https://skvidal.wordpress.com/2012/04/20/mockchain-use-cases-and-examples/


 References:
 http://www.redhat.com/archives/rhl-devel-list/2008-November/msg01229.html

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

Re: [ACTION REQUIRED] Retiring packages for Fedora 19 - March 4 update

[Johannes Lips]

On Thu, Mar 7, 2013 at 4:15 AM, Adam Williamson awill...@redhat.com wrote:

 On 06/03/13 04:39 AM, Dan Mashal wrote:

  Took libindicator too. Is this deprecated upstream?


 No, there are commits right up to late Feb in launchpad. But then I don't
 immediately see that you'd want it for MATE purposes (or really any other
 Fedora purposes); it's a Unity thing. I packaged and used to own it for my
 aborted plan to try and package Unity, and it's orphaned because I don't
 want it any more. I don't think it has any dependencies in Fedora, and I
 think it's pretty useless if you're not running Unity.

Then why not just retire it properly? I mean of course someone could step
up to package unity in fedora but then, how likely and realistic is that?
As a side note I was also wondering why so many important packages like
hicolor-icon-theme were orphaned and I can't recall any announcement on
-devel or -announce about that.
Johannes


 bamf is in a similar position, but at least _something_ - gnome-pie,
 whatever that is - requires it. So it might actually be more useful for
 someone to pick that up.
 --
 Adam Williamson
 Fedora QA Community Monkey
 IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora
 http://www.happyassassin.net

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

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

Re: Problems testing packages on koji

[Johannes Lips]

Eduardo Javier Echeverria Alvarado wrote:

Hi, everyone

I've a problem that has kept me worried about three weeks ago and i do
not know how to solve, when I try to test any package on koji (in any
instance, ppc, arm, s390, x86 ) that has a higher weight to a mega, it
refuses to even begin the task

example:
koji build --scratch rawhide openteacher-3.0-1.fc17.src.rpm
Uploading srpm: openteacher-3.0-1.fc17.src.rpm
[]  00% 00:00:00 0.00 B-
B/sec

i.e. not upload the package, with files that weighing less than a mega,
koji behaves normally

example:

Uploading srpm: python-django-select2-3.2.1-1.fc18.src.rpm
[] 100% 00:00:06  69.52 KiB  11.13
KiB/sec
Created task: 5042273
Task info: http://koji.fedoraproject.org/koji/taskinfo?taskID=5042273
Watching tasks (this may be safely interrupted)...

I asked in IRC # fedora-devel and I have said it may be due to problems
with file locking by my ISP, but I checked it, and I have found no
problem with it, someone has ocurred this problem, or know to fix it?

Thanks for advance.

Hi all,

what I observed is that the upload works but the progress bar is not 
showing the progress.
It just jumps to 100% when it's finished. Perhaps try waiting a bit or 
try to monitor the upload speed, there you could perhaps see some movements.


Hope this helps,

Johannes


--
Eduardo Echeverria
https://fedoraproject.org/wiki/User:Echevemaster
echevemas...@fedoraproject.org mailto:echevemas...@fedoraproject.org
Fedora RPM Package Maintainer
Fedora Ambassador




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

Retiring tilda in rawhide

[Johannes Lips]

Hi all,

I am going to retire tilda in fedora rawhide in the near future. Upstream
is mostly dead and I had to maintain a lot of patches. Since the new
Xfce4-terminal also gained a dropdown mode, I don't have any further value
in tilda and so I would like to retire it and would advise all the users to
switch to alternatives like guake and the like.

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

Re: Looking for a freemind maintainer

[Johannes Lips]

Ok, I found some time to package up a new dep for freemind 1.0.0.
src-rpm url: http://hannes.fedorapeople.org/jortho-0.5-1.fc18.src.rpm
spec url: http://hannes.fedorapeople.org/jortho.spec

If it looks ok, I will submit it as a review.

Thanks for any hints on things, which are wrong.

Johannes


On Tue, Jan 8, 2013 at 6:39 AM, Kalpa Welivitigoda callka...@gmail.comwrote:




 On Tue, Dec 4, 2012 at 9:31 PM, Johannes Lips johannes.l...@gmail.comwrote:




 On Mon, Nov 26, 2012 at 12:40 PM, Kalpa Welivitigoda callka...@gmail.com
  wrote:

 On Mon, Nov 26, 2012 at 3:55 PM, Caterpillar caterpilla...@gmail.com
 wrote:
  Il 23/11/2012 15:33, Johannes Lips ha scritto:
  Hi all,
 
  I am looking for a new freemind maintainer. I've stated the reason for
  this in this mail to java-devel:
 
 http://lists.fedoraproject.org/pipermail/java-devel/2012-November/004561.html
 
  Perhaps someone would like to take over...
 

 I am a frequent freemind user and I would like to take over.

  Johannes
 
 
  Hi, I often use freemind for my studies, but I have never mantained a
  package. What level of knowledge does the freemind manteinance require?

 Perhaps you may join as a co-maintainer.

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



 --
 Best Regards,

 Kalpa Welivitigoda
 http://about.me/callkalpa
 --
 devel mailing list
 devel@lists.fedoraproject.org
 https://admin.fedoraproject.org/mailman/listinfo/devel


 Hi,

 sorry for the delay, but I've not had that much time recently.
 The knowledge needed for maintaining the package is basically java
 packaging, the ant buildsystem and you need to be familiar with the fedora
 processes as well.
 I would suggest that you, Kalpa, are applying for co-maintainership and I
 will give you all the needed rights. Then you could take a look at how it
 is packaged and see if you could make the new 1.0.0 release available.
 Please bear in mind that this might need some additional reviews of
 packages since upstream added some deps.
 If all goes well, I will happily hand the package over to you completely!

 Best wishes,

 Johannes


 Due to lack of available free time I am not in a position to maintain the
 package. Hope Stanislav will take care of that.



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




 --
 Best Regards,

 Kalpa Welivitigoda
 Junior Treasurer | Electrical Engineering Society
 Undergraduate | Department of Electrical Engineering
 University of Moratuwa
 Sri Lanka
 http://about.me/callkalpa

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

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

Re: Looking for a freemind maintainer

[Johannes Lips]

On Mon, Nov 26, 2012 at 12:40 PM, Kalpa Welivitigoda callka...@gmail.comwrote:

 On Mon, Nov 26, 2012 at 3:55 PM, Caterpillar caterpilla...@gmail.com
 wrote:
  Il 23/11/2012 15:33, Johannes Lips ha scritto:
  Hi all,
 
  I am looking for a new freemind maintainer. I've stated the reason for
  this in this mail to java-devel:
 
 http://lists.fedoraproject.org/pipermail/java-devel/2012-November/004561.html
 
  Perhaps someone would like to take over...
 

 I am a frequent freemind user and I would like to take over.

  Johannes
 
 
  Hi, I often use freemind for my studies, but I have never mantained a
  package. What level of knowledge does the freemind manteinance require?

 Perhaps you may join as a co-maintainer.

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



 --
 Best Regards,

 Kalpa Welivitigoda
 http://about.me/callkalpa
 --
 devel mailing list
 devel@lists.fedoraproject.org
 https://admin.fedoraproject.org/mailman/listinfo/devel


Hi,

sorry for the delay, but I've not had that much time recently.
The knowledge needed for maintaining the package is basically java
packaging, the ant buildsystem and you need to be familiar with the fedora
processes as well.
I would suggest that you, Kalpa, are applying for co-maintainership and I
will give you all the needed rights. Then you could take a look at how it
is packaged and see if you could make the new 1.0.0 release available.
Please bear in mind that this might need some additional reviews of
packages since upstream added some deps.
If all goes well, I will happily hand the package over to you completely!

Best wishes,

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

Looking for a freemind maintainer

[Johannes Lips]

Hi all,

I am looking for a new freemind maintainer. I've stated the reason for this
in this mail to java-devel:
http://lists.fedoraproject.org/pipermail/java-devel/2012-November/004561.html

Perhaps someone would like to take over...

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

Re: Calling for the packager of fping

[Johannes Lips]

On Thu, Aug 23, 2012 at 1:36 PM, Christopher Meng cicku...@gmail.comwrote:

 Ok,I'll try


 https://apps.fedoraproject.org/packages/fping/
Seems to me that there is some action on the package. I don't know if I
miss something here.
Especially the Changelog is not so dead as you describe it.
https://apps.fedoraproject.org/packages/fping/changelog

Johannes


 --


 *Yours sincerely,*
 *Christopher Meng*

 Ambassador/Contributor of Fedora Project and many others.
 http://cicku.me

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

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

Re: [ACTION REQUIRED v3] Retiring packages for F-18

[Johannes Lips]

On Wed, Jul 25, 2012 at 1:44 PM, Peter Robinson pbrobin...@gmail.comwrote:

 On Tue, Jul 24, 2012 at 9:04 PM, Bill Nottingham nott...@redhat.com
 wrote:
  Tom Lane (t...@redhat.com) said:
  Bill Nottingham nott...@redhat.com writes:
   Before we branch for Fedora 18, as is custom, we will block currently
   orphaned packages and packages that have failed to build since Fedora
 16.
 
   The following packages are currently orphaned, or fail to build.
   [snip]
 
  That list seems seriously incomplete.  I'm aware of at least these
  others that have FTBFS in both F17 and F18 mass rebuilds, as evidenced
  by their release tags:
 
  It's done by basing off of the F16FTBFS bug, as that's the easiest source
  of info when we haven't done a mass rebuild.
 
  We could include everything with older dist tags. Looking at it, that
 would
  be 78 more packages.

 It would be nice to get rid of anything that's FTBFS in non supported
 Fedora (ie at least  fc16) and the last time I looked at that there's
 a good 150 odd packages that are fc15 or older packages. There's been
 two mass rebuilds since then and if the package maintainers haven't
 managed to fix them (or they've not been fixed by people like
 secondary arches that fix them because they're blocking their builds)
 the package maintainer is either AWOL or not doing their job of
 maintaining packages or even bothering to check failure emails so it's
 likely better off for Fedora that they're scrapped as well. I think in
 the F17 cycle I fixed over 100+ of these packages.

It would probably help to keep track of the problem if we could manage to
get back the FTBFS bugs.
I don't know if there is some work done on this but it would definitely
help with this issue.

Johannes


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

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

Re: [ACTION REQUIRED] Retiring packages for Fedora 18

[Johannes Lips]

Toshio Kuratomi wrote:
 Just a note that the following additional packages were orphaned yesterday
 as part of cleaning up packages owned by people without bugzilla accounts:
 
 devilspie
I've taken devilspie, but just that it's not removed from fedora since I
think it's often useful to Xfce users.
Co-Maintainers are welcome and I would also be totally happy if someone
steps up and want to take ownership again!

Johannes
 dogtail
 gtkmm-utils
 k12linux-quick-start-guide
 kcoloredit
 kgrab
 kiconedit
 koverartist
 ksig
 libzip
 polyester
 polyester3
 python-djblets
 python-flask
 python-werkzeug
 stalonetray
 tasks
 
 -Toshio
 
 
 


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

Re: vim with Gnome integration: session restore support and vim-subpackage structure

[Johannes Lips]

On Wed, Jul 4, 2012 at 4:02 PM, Nathanael D. Noblet nathan...@gnat.cawrote:

 On 07/04/2012 03:04 AM, Michael J Gruber wrote:

 Hi there,

 gvim as provided in the Fedora packages does not support session restore
 (i.e. reopening with the same buffers) because it does not integrate
 with the GNOME nor KDE desktop environments.

 Recompiling with gnome support helps: as a proof of concept, I've added
 a vim-gnome subpackage to the spec file, see

 http://mjg.fedorapeople.org/**rpmdev/vim.spechttp://mjg.fedorapeople.org/rpmdev/vim.spec

 which is based on the current F16 (updates) spec. It provides a
 gnome-vim binary which is gvim + gnome integration and works with KDE
 as well.

 It's only POC because I think we need to decide about the package
 structure (see also 
 https://bugzilla.redhat.com/**show_bug.cgi?id=311061https://bugzilla.redhat.com/show_bug.cgi?id=311061
 ).
 vim can be compiled resp. is currently in Fedora in these shapes:

 * with minimal features: subpackage vim-minimal
 /bin/ex
 /bin/rvi
 /bin/rview
 /bin/vi
 /bin/view
 (or /usr/bin/ ;) )

 * with enhanced features and without X library support: not in Fedora

 * with enhanced features and no GUI: subpackage vim-enhanced
 /usr/bin/ex
 /usr/bin/rvim
 /usr/bin/vim
 /usr/bin/vimdiff
 /usr/bin/vimtutor
 (these support vim in xterm and such specifically and depend on X
 libraries!)


 Thie vim-minimal and vim-enhanced will now class in F17 due to the lack of
 a separation between /usr and / so /bin/ex == /usr/bin/ex... Just something
 to think about for this package it seems.

On a related note, the description of the vim-minimal package also needs
some updates. Since it doesn't really reflect the changes which are caused
by the usr-move.

Johannes


 --
 Nathanael d. Noblet
 t 403.875.4613



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

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

Re: Space wasted by Non English Packages shipped by Default on Fedora 17.

[Johannes Lips]

On Mon, Jun 25, 2012 at 2:27 PM, Malcolm Turmel malcolm.tur...@gmail.comwrote:

 Its still taking up valuable space.

 All the non-english packages should be optional.

 When I try to remove one of the Package, it tells me its going to also
 Uninstall lots of other stuff.

 How would I go about now uninstalling all of them without breaking my
 system.


 On Mon, Jun 25, 2012 at 6:10 AM, Julian Leyh jul...@vgai.de wrote:

 2012/6/25 Malcolm Turmel malcolm.tur...@gmail.com:
  There seems to be support for lots of languages other than English,
 which I
  don't need, but it seems to be installed by default on Fedora 17. Why?

 Package Groups are shown as installed, as soon as all mandatory
 packages are installed (IIRC at least one package of the group has to
 be installed). Some groups have no mandatory packages at all. Most of
 the language support groups have font packages in their list that can
 already be installed on default system. That way they get displayed as
 installed. In reality it means partially installed.

 No need to worry.

 --
 If you don't remember something, it never happened...
 If you aren't remembered, you never existed...
 --
 devel mailing list
 devel@lists.fedoraproject.org
 https://admin.fedoraproject.org/mailman/listinfo/devel



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

They are probably shipped by default, since there are people around who
don't speak english and also use a different set of letters.
I think it's good to give them a good out-of-the-box fedora experience.
To say if it's safe to remove the packages one would need to know which
packages exactly are removed by the yum transaction.

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

Re: poppler soname bump in rawhide

[Johannes Lips]

Marek Kasik wrote:
 Hi,
 
 I plan to rebase poppler in rawhide to poppler-0.20.1 at the end of next
 week.
 There are several API changes (new functions + 1 move of a private
 function to public section) and 1 soname bump (libpoppler.so.25 to
 libpoppler.so.26).
 
 Regards
 
 Marek
 ___
 devel-announce mailing list
 devel-annou...@lists.fedoraproject.org
 https://admin.fedoraproject.org/mailman/listinfo/devel-announce
 
Are you doing the necessary rebuilds as well or should we, the
maintainers of the depending packages, do them?

Johannes



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

Re: Important kernel update should not break stuff

[Johannes Lips]

On Wed, Jun 13, 2012 at 1:00 PM, Roman Kennke rken...@redhat.com wrote:

  Today something happened, that happens over and over again with Fedora,
  and it makes me angry. I am running Fedora 17, and so far it worked well
  with the initial kernel 3.3.x (except that it would panic on shutdown...
  but that was not important to me, but still embarassing). Today I was
  notified of an important security update in the kernel. Curiously, it
  would update from 3.3 to 3.4 (a major version upgrade, which should not
  happen in such a core package anyway, IMO). Reboot into the new kernel,
  everything comes up --- until I want to actually want to read email,
  surf web, or anything that requires my network. I am on an Intel Wifi
  card, iwlwifi module. I *can* connect to the network, but everything is
  suuper  slow or times-out every now and then. Completely unusable.
  Reboot into the older kernel, things work well again. Now I am left with
  the choice of running a new kernel w/o network or an unsecure kernel.
  Thank you very much!
 
  This sort of thing I would expect in rawhide/development builds, but not
  in a supposed-to-be stable release. I can understand the underlying idea
  of being on the bleeding edge, but I don't want to actually be bleeding.
  At least the base system components should not undergo major version
  updates. Security fixes should be backported to the software version
  that is in the stable release (1 year release cycle shouldn't be too
  demanding for this), and only security fixes and absolutely important
  fixes should go into stable releases. (Not to mention that some fixes
  that I *would* consider important enough to go into stable never end up
  there.) If major version updates are really really necessary, they
  should undergo serious testing. I cannot believe that I am the only one
  on an Intel Wifi chip. The way it is now, Fedora feels like a constantly
  rolling development version that is almost unusable (because any update,
  even security, has a fairly high risk of breaking things) for day-to-day
  work.
 
  Bugzilla report:
  https://bugzilla.redhat.com/show_bug.cgi?id=831571

 Since I just received an email in private pointing out that emails like
 mine above might be discouraging and not helpful... let me apologize for
 this. My intention is not to bash other people's best efforts, but
 instead try to help out (otherwise I would not bother to diligently file
 bugreports and mention my concerns on this list). I am willing to help
 track down and fix the problem. However, I see a more general problem
 and maybe we can turn this into a discussion how to address (or answer)
 it.

 - Why do we allow new major versions of core components into a stable
 release? What sort of testing is performed before a major kernel update
 hits Fedora stable?
 - What is the policy with regards to risky changes (like unnecessary
 feature updates, ABI changes, etc) in stable?
 - How can problems like the one I described above be avoided? Is there
 anything I and others can help with?

 Roman


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

I think the reason for shipping the latest upstream kernel is based on the
fact that backporting would be too much work.
http://fedoraproject.org/wiki/KernelRebases
Gives a good overview and probably prevents us from repeating arguments in
the discussion.

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

Re: Update ImageMagick in Fedora 16

[Johannes Lips]

Tadej Janež wrote:
 Pavel,
 
 On Tue, 2012-05-29 at 20:21 +0400, Pavel Alexeev wrote:
 
 It is main reason why I request provenpackager rights. In fedora 17 it
 was so painful because I several times asks build dependencies and
 then ask help to push updates too.
 I think in that turn now I can do all that myself, so it should be
 smoother.

 As there around 6 security issues, I think update upstream release is
 easiest, and furthermore robust way handle it.
 
 I've seen you didn't listen to Tomáš's or Kalev's advice on not bumping
 the ImageMagick's soname in a stable release.
 
 Furthermore, you didn't give any warning to the maintainers of the
 dependent packages (except for the message on this list).
 In my opinion, being a provenpackager is no excuse for not doing that.
 Please, use the packagename-ow...@fedoraproject.org addresses to send
 out emails to the appropriate package maintainers.
 
 For techne (one of the dependent packages which I maintain) you bumped
 the release from 0.2.3-2 to 0.2.3-3, which breaks upgrades to F-17 and
 rawhide.
 Is there a way to revert the change and make a 0.2.3-2.fc16.1 build?
The best practice now is to do a bump release in all newer branches. So
just bump the Version in fedora 17 and rawhide to 0.2.3-3.
The changelog entry could look like:
- bump release
or something similar.

Hope this helps

Johannes
 
 Best regards,
 Tadej Janež
 
 

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

Re: Update ImageMagick in Fedora 16

[Johannes Lips]

Pete Walter wrote:
 Pavel Alexeev forum at hubbitus.com.ru writes:
 May be in next time? What disadvantages you are seen proceed with that 
 update? Do you try test it?
 
 No, I did not test this. And here's a few reasons why I think this 
 shouldn't be pushed:
 
  - You are forcing others to do work they otherwise wouldn't need to 
do.  Why do you want me to test ImageMagick functionality in 57
dependant packages?  Fix your security bugs and leave other 
packages alone.  F16 is supposed to be stable.
 
  - A major ImageMagick update that introduces new features and new code 
invalidates the QA that has gone into the packages that use 
ImageMagick.
 
  - Needless update churn.  We have the Stable Updates Policy for a 
reason.  Do you development on rawhide and let stable Fedora 
release be stable.
 
  - The soname bump breaks third party packages that use ImageMagick 
libraries.  An example is 'transcode' from rpmfusion.
 
 
 http://fedoraproject.org/wiki/Updates_Policy explicitly says that such
 ABI bumps are left to the discretion of FESCO and the packager.  Have 
 you already asked FESCO for their blessing?
 
 Note that you should open this dialog _BEFORE_ you build or push updates.
 
 
   Pete
 
Just to be fair there was a mail to this mailing list, where he
described his plans. [1]
Also I think he did the major part of the work and if it's fine for him,
I don't really see a problem. I mean of course it could be better and he
could also bump the releases of all the newer fedora versions, but I
think there is not so much work for the package maintainers left.
I don't want to argue in favor of the whole upgrade but I think the
criticism is a bit too harsh.

Johannes

[1] http://lists.fedoraproject.org/pipermail/devel/2012-May/167462.html

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

Re: Finding out about a pkg?

[Johannes Lips]

On 05/26/2012 10:23 AM, Frank Murphy wrote:

I'm trying to follow up on struts,
http://koji.fedoraproject.org/koji/buildinfo?buildID=239819
is the last mention I can see of it.

yum with *testing shows nothing.
How can I find if it's orphaned?


Hi,

you could checkout the pkgdb:
https://admin.fedoraproject.org/pkgdb/acls/name/struts
It seems to be deprecated.

Hope this helps,

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

Re: default media size [Was: Proposed F18 feature: MiniDebugInfo]

[Johannes Lips]

On Thu, May 10, 2012 at 4:00 PM, Adam Jackson a...@redhat.com wrote:

 On Thu, 2012-05-10 at 09:16 +0200, Kevin Kofler wrote:
  Adam Jackson wrote:
   Even if all of your objections are true, and who knows, they might be:
   we already do provide alternatives.  The Live media is not the only
   install media.
 
  The other alternatives are either already DVDs or netinstall CDs which
  require a fast Internet connection (which people who don't even have a
 DVD
  drive are unlikely to have).

 So the set of people we'd be inconveniencing is exactly the set of
 people with no bandwidth and the inability to boot from anything larger
 than a CD.

 Do we think that's a statistically significant number of people, or are
 we just arguing?

Would be interesting to get some input from lower-income countries.
Ambassadors from those countries could perhaps tell us about the hardware
which is most common.

Johannes


 - ajax

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

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

Re: Install Fedora Button for LiveCD

[Johannes Lips]

Perhaps he was just not aware of these objections. Although I could not
speak for him but it's at least a possible explanation for the proposal.

Johannes

On Fri, May 4, 2012 at 9:18 AM, Adam Williamson awill...@redhat.com wrote:

 On Fri, 2012-05-04 at 12:50 +0700, Michel Alexandre Salim wrote:
  On 04/27/2012 08:58 PM, Jared K. Smith wrote:
   On Fri, Apr 27, 2012 at 9:50 AM, Colin Walters walt...@verbum.org
 wrote:
   The whole thing is clearly a mess that needs some high level
   streamlining, from the entire process of download from web page (or
   receive CD from friend) to the on-disk install first boot.
  
   While I certainly wouldn't disagree with this statement, let's not let
   perfect get in the way of better here.
  
   What can we do in the *near* term to make it easier for people to find
   the Install to Hard Drive option from the LiveCD?
 
  How about installing the Dock extension on the liveuser account, and
  configuring it to *not* auto-hide? That way we get a solution that
  a) many users use anyway
  b) is aesthetically pleasing

 I don't see the point of making proposals like this which it's quite
 clear have absolutely no chance of happening. Desktop team has already
 stated clearly that they won't set up extensions as default
 configuration. Continuing to 'suggest' that they do is only likely to
 rile them up and start another of those long boring argumentative
 threads that have no purpose...
 --
 Adam Williamson
 Fedora QA Community Monkey
 IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora
 http://www.happyassassin.net

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

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

Re: tilda unmaintained? (was: Re: Examining -static package build timestamps in koji)

[Johannes Lips]

Well I would like to see tilda maintained in fedora. In this bugreport I
created the patch and asked a provenpackager to apply it, which never
actually happened.
I could of course apply for co-maintainership but I doubt that the
maintainer would answer in a timely manner, like on most of his bugreports.
Johannes

On Fri, May 4, 2012 at 6:32 PM, Michael Schwendt 
mschwe...@fedoraproject.org wrote:

 On Fri, 04 May 2012 18:30:58 +0200, PM (Petr) wrote:

   21 link with flex libs-- flex doesn't change often, though
 
  I believe that libfl.a hasn't really changed in Fedora at all.  It
  exports two symbols, totaling something like 10 lines of actual code.
  Absence of client rebuilds is just not a problem in this case.
 
   tilda-0.9.6-6.fc16.src  older than  flex-2.5.35-15.fc18.src.rpm
 231 days

 Yeah, I figured so much.

 Interestingly, tilda has failed to rebuild two times in a row according
 to koji status, and its bug status page doesn't look too pretty:

http://bugz.fedoraproject.org/tilda

 There's even somebody interested in co-maintaining it, but hasn't got
 a response in over a month: https://bugzilla.redhat.com/781875

 --
 Fedora release 17 (Beefy Miracle) - Linux 3.3.4-3.fc17.x86_64
 loadavg: 0.12 0.04 0.05
 --
 devel mailing list
 devel@lists.fedoraproject.org
 https://admin.fedoraproject.org/mailman/listinfo/devel
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

Re: Fedora release name in the future

[Johannes Lips]

http://lists.fedoraproject.org/pipermail/devel/2012-April/166087.html

On Fri, Apr 27, 2012 at 2:22 PM, Michael Schwendt mschwe...@gmail.comwrote:

 On Fri, 27 Apr 2012 15:10:45 +0200, AT (Antonio) wrote:

  The poll about Fedora release names keeping is terminated
  [1]
 https://admin.fedoraproject.org/voting/results/poll-rel-names?_csrf_token=ed7209dc06f5c8c58528ac55251f52c8ffacdc40
 .
 
  And now ?

 Well, I've missed the announcement of this poll.
 Where has it been announced?

 --
 Fedora release 17 (Beefy Miracle) - Linux 3.3.2-8.fc17.x86_64
 loadavg: 0.12 0.08 0.06
 --
 devel mailing list
 devel@lists.fedoraproject.org
 https://admin.fedoraproject.org/mailman/listinfo/devel

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

Re: F16: Broken ypbind

[Johannes Lips]

Is it this bug: https://bugzilla.redhat.com/show_bug.cgi?id=812501
If yes, there is already an update in updates-testing which you could try.
hth
Johannes
On 04/21/2012 08:10 AM, Terry Barnaby wrote:

Some update appears to have broken the operation of ypbind recently.
I have a F14 sever that serves /home and implements NIS services (ypserv)
and has been running fine for over a year.

The F16 clients use NetworkManager with wired Ethernet set to
automatic/system connection. Everything comes up fine except for ypbind
that fails. This
has worked fine until a week or so ago (fails on multiple clients).

The boot.log is enclosed, any ideas ?

Cheers


Terry




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

Re: Fedora 18 schedule and Python 3.3

[Johannes Lips]

Hi,
I found http://fedoraproject.org/wiki/Releases/Schedule and there seems 
to be a relatively easy way to determine the Fedora 18 Release date. 
Tuesday before October 31st. So most probably Tuesday, 30th October 
2012, if I am not mistaken.


HTH
Johannes
On 04/16/2012 10:11 PM, David Malcolm wrote:

Do we have a schedule for Fedora 18 yet?

I've started creating a feature page for getting Python 3.3 into Fedora:
   https://fedoraproject.org/wiki/Features/Python_3.3
but it's not clear to me yet how well the Python 3.3 upstream schedule
lines up with Fedora's schedule.  So for now I've simply used the Fedora
16 schedule, and offset the dates by a year (2011 -  2012).

Based on that, Python 3.3 will probably be a Fedora 18 feature - though
I don't think we can do any packaging work until 3.3 hits feature freeze
(stabilizing the .pyc format and the .so ABI).  Having said that there's
plenty of work to be done getting our patches into upstream before it
hits feature freeze!

Hope this sounds sane
Dave



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

Re: End user needs info: Freeplane on Fedora 17

[Johannes Lips]

As the maintainer of freemind, I also looked into packaging freeplane 
but I gave up since it adds a whole bunch of new deps. I didn't have the 
time and motivation to add all those, just for a program which basically 
does the same as freemind. I know that it does have some additional 
features and is a bit better maintained, but this didn't justify the 
additional workload for me.
This is also a result of the way Java projects ship their software which 
makes it hard to use it in a way, we need it in fedora.
I know that there were some issues of freemind with regard to exporting 
(which should be mostly fixed by now) and with the usage of Japanese 
Letters or Signs, but this is more an upstream thing and there is not 
much we could do about.
The only way freeplane is coming to fedora is that someone steps up and 
does the required packaging work. (Note that I am also not really a 
programmer and was also just an end user before I started working on 
fedora) ;-)


Johannes


On 04/12/2012 01:39 AM, nomnex wrote:

http://freeplane.sourceforge.net/wiki/index.php/Main_Page

Will there be a Freeplane package available on the F17 repository (  Is
there a Freeplane Fedora package maintainer)?

I am using Freemind 0.9 on F15. It is not without problems.

Thank you


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

Fedora Packages Search

[Johannes Lips]

Hi all,

I really like this website[1] and think it's really useful. I just 
wanted to know what the current state of it is. Especially could I use 
the current URL to promote some packages or is it likely that the URL 
could change in the near future.
Is there some place where I could find information about the things 
which are planned in the future.


Thanks a lot

Johannes




[1] https://community.dev.fedoraproject.org/packages/
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

Re: Fedora Packages Search

[Johannes Lips]

On 03/30/2012 03:58 PM, Kevin Fenzi wrote:

On Fri, 30 Mar 2012 08:06:11 +0100
Johannes Lipsjohannes.l...@googlemail.com  wrote:


Hi all,

I really like this website[1] and think it's really useful. I just
wanted to know what the current state of it is. Especially could I
use the current URL to promote some packages or is it likely that the
URL could change in the near future.
Is there some place where I could find information about the things
which are planned in the future.


The best place would be the infrastructure list, or #fedora-admin on
irc, but here works fine too. ;)

We are working on deploying this into production...

https://apps.fedoraproject.org/packages/ is the initial instance.
We still are working on deploying tagger and cleaning some things up
before we officially announce it and start supporting it in production.

packages and tagger are part of the 2.0 version of fedora-community.

See: https://fedorahosted.org/fedoracommunity for how to contact them
and add your ideas/patches/etc.

Hope that helps,

kevin




Yes this helps a lot and answered all my questions!
Thanks a lot Kevin!

Johannes

P.S.: Sorry for posting this to -devel, I just don't want to subscribe 
to all fedora-mls ;-)

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

Re: This karma stuff is a pain!

[Johannes Lips]

On 03/16/2012 10:06 PM, Kevin Kofler wrote:

David Tardon wrote:

How do we prevent inexperienced testers from giving undeserved karma and
thus causing an update to be automatically pushed to stable?

One has to fulfil certain requirements before one becomes a packager.
But anyone with FAS account can give karma to an update...


+1, the current policy is really flawed, we trust any idiot with a FAS
account more than our sponsored packagers (and even our carefully vetted
provenpackagers).

 Kevin Kofler

But this policy also prevents the misuse of power, which is also a good 
thing I think. And there needs to be more than one idiot to make any 
changes to the update which is not the case of packagers or even 
provenpackagers. Which I think is really helpful since in most cases 
those people are also only humans which could make mistakes.
I think this policy helps to prevent updates which break a lot of stuff 
when pushed to stable, it also provides a nice and quicker way of first 
contact to check if there are some issues with an update.


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

Re: Issues with yum

[Johannes Lips]

There is a filed bug regarding this behavior. But so far no explanation or
cause for this behavior.
https://bugzilla.redhat.com/show_bug.cgi?id=771043

Johannes
On Tue, Feb 28, 2012 at 9:04 AM, Gerd Hoffmann kra...@redhat.com wrote:

  Hi,

  2) yum is currently downloading repository information separately for
  each user.
  It can use the same downloaded repository information for all users.

  Wrong, information are cached in /var/lib/yum.

 When you run yum as user it doesn't use the cache though.  It creates
 its own cache somewhere in /var/tmp.  It ignores the cachedir option too.

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

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

Re: How to determine FAS from BZ email?

[Johannes Lips]

Isn't it easiest to just ask for the FAS name of the person who wants to
become a packager? I don't really see how this should be less efficient
than searching the mail address in the FAS database.


On Thu, Feb 23, 2012 at 3:23 PM, Jamie Nguyen ja...@tomoyolinux.co.ukwrote:

 Thomas Spura toms...@fedoraproject.org wrote:
  On Thu, Feb 23, 2012 at 3:24 PM, Jamie Nguyen ja...@tomoyolinux.co.uk
 wrote:
  Thomas Spura wrote:
  2012/2/23 Miroslav Suchý msu...@redhat.com:
  But I find incredibly hard to find relation between bugzilla email
 and FAS
  account.
  How do you do this check?
 
  Show all useres in the cla_signed group [3] and search for the mail
  address. When it's not there it may be overritten in [4].
  When it's not there either, the user has not signed cla yet and cannot
  be a packager, yet.
 
  You can't be a packager without signing the CLA, but you can sign the
  CLA without being a packager.
 
  Yes, no cla - no packager, like I wrote above.
  When someone has signed the cla, you then need to look if the user is
  already member of the packager group...

 Perhaps I misunderstand, but I think the real problem is that the
 email used for bugzilla doesn't have to be the same as the email
 specified when signing up for a FAS account. So if the bugzilla email
 isn't found in FAS, it doesn't necessarily mean that they don't yet
 have a FAS account. Similarly, it also doesn't necessarily mean that
 they haven't signed the CLA yet.

 I don't know how these queries are done, but I would have thought that
 if you can query whether any members of the CLA group have the email
 address in question, you might as well query the Packager group from
 the start.


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

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

Re: F-17 Branched report: 20120211 changes

[Johannes Lips]

Alright to answer my own question: It was already orphaned in the last
round before f16. So it's probably worth reviving!
But I think the associated workload with reviving a package could be
lowered, just to make it easier for contributors!

On Sun, Feb 12, 2012 at 9:27 AM, Johannes Lips johannes.l...@googlemail.com
 wrote:

 What's the reason pyorbit is orphaned and deprecated? It was not part of
 the recent mass orphaning and is a dep for many packages.
 I just would like to know if it's worth reviving it since one of my
 packages is indirectly depending on it and now refuses to build in rawhide.
 Thanks

 johannes

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

Re: F-17 Branched report: 20120211 changes

[Johannes Lips]

What's the reason pyorbit is orphaned and deprecated? It was not part of 
the recent mass orphaning and is a dep for many packages.
I just would like to know if it's worth reviving it since one of my 
packages is indirectly depending on it and now refuses to build in rawhide.

Thanks

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

Qt Package Build fails in rawhide and f17 and builds in f16

[Johannes Lips]

Hey,

I just seem to run into an error that a package builds just fine in f16
(unpackaged file is another thing) but it won't build on f17 and f18. Is
there an incompatibility of the source code with newer Qt versions or is it
just a temporary koji hickup?

f16 build:
http://koji.fedoraproject.org/koji/taskinfo?taskID=313
f17 build:
http://koji.fedoraproject.org/koji/taskinfo?taskID=315
f18 build:
http://koji.fedoraproject.org/koji/taskinfo?taskID=309

Thanks for any help,

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