F26 Self Contained Change: Docker Overlay 2
= Proposed Self Contained Change: Docker Overlay 2 = https://fedoraproject.org/wiki/Changes/DockerOverlay2 Change owner(s): * Lokesh Mandvekar Change the default Docker Storage to be overlay2 . == Detailed Description == Upstream docker is moving to overlay2 by default for its storage. We plan on following suit. There are some performance advantages of overlay2 over devicemapper in memory sharing, which we would like to take advantage of. We now have SELinux support for Overlay file systems, so the security should be just as good. Note: Overlay is not a Posix Compliant file system, so there could be problems with your containers running on overlay, so we want to make sure it is fairly easy to switch back to devicemapper. Devicemapper out of the box, on Fedora Workstation, currently defaults to loopback devices for storage, which has a performance penalty, but this was the only way we were able to get docker to work right away. Switching to overlay2 will cause the storage to be shared with / and will eliminate this performance overhead. This is the way we will ship Fedora Workstation. On Fedora atomic host and Fedora server we have been storing devicemapper storage on a separate partition. We plan on doing the same thing with overlay2. This means separate device will be mounted on /var/lib/docker. This will make it easier for someone to switch back to devicemapper, if overlay2 has problems. Upgraded systems will not be effected. If you want to switch from one storage to another take a look at the `atomic storage` commands. We will write up release notes to cover this change. Along with a blog explaining the commands to switch back and forth. == Scope == * Proposal owners: Implementation of this Change * Other developers: N/A (not a System Wide Change) * Release engineering: N/A (not a System Wide Change) * List of deliverables: N/A (not a System Wide Change) * Policies and guidelines: N/A (not a System Wide Change) * Trademark approval: N/A (not needed for this Change) -- Jan Kuřík Platform & Fedora Program Manager Red Hat Czech s.r.o., Purkynova 99/71, 612 45 Brno, Czech Republic ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Re: Unretiring itpp
> Provided I get some guidance (or readings, account settings, ...), I
> ciuld maintain or co-maintain the package if necessary.
> Release:0%{?dist}
First release of a package usually starts with 1 not 0:
https://fedoraproject.org/wiki/Packaging:Versioning#Release_Tag
> %package devel
> Requires: %{name} = %{version}-%{release}
https://fedoraproject.org/wiki/Packaging:Guidelines#Requiring_Base_Package
> Requires: pkgconfig
If there are pkgconfig .pc files included in that package, there will
be automatic Provides/Requires for pkgconfig and the inter-dependencies
as specified within the .pc files.
> Requires: fftw-devel, atlas-devel, gcc-gfortran
You may want to make them arch-specific, too.
> %package doc
> Summary:Documentation for itpp
> Group: Development/Libraries
Wrong group tag for Documentation packages, and the Group tag is not
necessary for a long time:
https://fedoraproject.org/wiki/Packaging:Guidelines#Tags_and_Sections
Most likely, you also want to make this subpackage "BuildArch: noarch".
> Requires: %{name} = %{version}-%{release}
Doubtful. Keep documentation packages free of dependencies when the
included HTML documentation can be displayed and doesn't need the base
package.
> %install
> rm -rf $RPM_BUILD_ROOT
Clean up of buildroot is automatic for a long time:
https://fedoraproject.org/wiki/Packaging:Guidelines#Tags_and_Sections
> make install DESTDIR=$RPM_BUILD_ROOT LIBDIR=$RPM_BUILD_ROOT/usr/lib64
What does the LIBDIR definition achieve when you still need to move
the libs from /usr/lib later?
> mv $RPM_BUILD_ROOT/usr/lib $RPM_BUILD_ROOT/%{_libdir}
> %clean
> rm -rf $RPM_BUILD_ROOT/
https://fedoraproject.org/wiki/Packaging:Guidelines#Tags_and_Sections
> %files
> %defattr(-,root,root,-)
https://fedoraproject.org/wiki/Packaging:Guidelines#File_Permissions
> %dir %{_docdir}/%{name}
> %{_docdir}/%{name}/[A-Z]*
https://fedoraproject.org/wiki/Packaging:LicensingGuidelines#License_Text
> %{_bindir}/%{name}-config
Needs to be checked whether it refers to /usr/lib and /usr/lib64.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Re: bex represents pagure emails in hyperkitty
> for some reason in hyperkitty the emails from pagure show up as > coming from Brian Exelbierd (bex). Anyone know why that is? They now show up as coming from "Josh Berkus", that's weird indeed. The posting address is indeed "pag...@pagure.io". There are several places where the poster's fullname can be looked for, I'll check it out. Aurélien ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Re: Changing default "docker" storage to to Overlay2 in Fedora 26
On Wed, Jan 18, 2017 at 9:54 PM, Dusty Mabe wrote: > > > On 01/18/2017 03:50 PM, Igor Gnatenko wrote: >> On Wed, Jan 18, 2017 at 9:48 PM, Dusty Mabe wrote: >>> >>> >>> On 01/06/2017 03:29 PM, Daniel J Walsh wrote: https://fedoraproject.org/wiki/Changes/DockerOverlay2 >>> >>> Can we get this onto the "official looking" page for F26 changes [1]? >> Change initiator should add it to category ReadyForWrangler and this >> change will be discussed on next (or after next) FESCo meeting. > > I see this on that page already: Category:ChangeReadyForWrangler no, it's just text. real category is: [[Category:ChangePageIncomplete]] > > Does that work? > > Dusty > ___ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@lists.fedoraproject.org ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Re: Changing default "docker" storage to to Overlay2 in Fedora 26
On Wed, Jan 18, 2017 at 9:48 PM, Dusty Mabe wrote: > > > On 01/06/2017 03:29 PM, Daniel J Walsh wrote: >> https://fedoraproject.org/wiki/Changes/DockerOverlay2 > > Can we get this onto the "official looking" page for F26 changes [1]? Change initiator should add it to category ReadyForWrangler and this change will be discussed on next (or after next) FESCo meeting. > > Do we also need to document in here the different configurations for the > different variants? > > Atomic Host vs Server vs Workstation? > > Dusty > > [1] https://fedoraproject.org/wiki/Releases/26/ChangeSet > ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Re: Changing default "docker" storage to to Overlay2 in Fedora 26
On 01/06/2017 03:29 PM, Daniel J Walsh wrote: > https://fedoraproject.org/wiki/Changes/DockerOverlay2 Can we get this onto the "official looking" page for F26 changes [1]? Do we also need to document in here the different configurations for the different variants? Atomic Host vs Server vs Workstation? Dusty [1] https://fedoraproject.org/wiki/Releases/26/ChangeSet ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Re: Changing default "docker" storage to to Overlay2 in Fedora 26
On 01/18/2017 03:50 PM, Igor Gnatenko wrote: > On Wed, Jan 18, 2017 at 9:48 PM, Dusty Mabe wrote: >> >> >> On 01/06/2017 03:29 PM, Daniel J Walsh wrote: >>> https://fedoraproject.org/wiki/Changes/DockerOverlay2 >> >> Can we get this onto the "official looking" page for F26 changes [1]? > Change initiator should add it to category ReadyForWrangler and this > change will be discussed on next (or after next) FESCo meeting. I see this on that page already: Category:ChangeReadyForWrangler Does that work? Dusty ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Re: Is there something wrong with the Koji builders?
On Wed, 18 Jan 2017 07:22:49 -0500 (EST) Charalampos Stratakis wrote: > Python 3 started failing on i686, x86_64 and arm only. > > https://koji.fedoraproject.org/koji/taskinfo?taskID=17313924 > > The failures come from the test_socket.py [0], test_aead_aes_gcm [1] > and more specifically this line [2] with the message: OSError: [Errno > 22] Invalid argument > > This test is checking Python's interface for the kernel crypto API > (added in 3.6 [3]). > > [0] > https://hg.python.org/cpython/file/3.6/Lib/test/test_socket.py#l5473 > [1] > https://hg.python.org/cpython/file/3.6/Lib/test/test_socket.py#l5472 > [2] > https://hg.python.org/cpython/file/3.6/Lib/test/test_socket.py#l5497 > [3] http://bugs.python.org/issue27744 Thats nothing to do with the buildsystem. Or at least if it is, it's not any of the known issues I was working on. As far as I know now everything should be back to working/normal. There were 3 issues: 1. The buildvm's were updated and started crashing under load. They would spew oopses and finally reboot. This would result in builds on them getting restarted or dying in strange ways. This seems to be something particular to their hardware/setup that changed in later 4.8.x and early 4.9.x kernels. We are currently running 4.10rc4 on them and it's been stable (knock on wood). 2. Sometimes, very rarely dnf would fail downloading packages for the build root. We have worked around this by passing dnf via koji several mirrors where it can download from, so if it fails on one it should fall back to the next and so on. https://pagure.io/fedora-infrastructure/issue/5689 3. In some configurations (where there was more than I host to download from) koji would fail to download the src.rpm correctly and error out. We are working around this now by just pointing koji at one place for these downloads for now until we can get things fixed. https://pagure.io/fedora-infrastructure/issue/5694 Sorry for all the instability the last few days. If you see any further issues like the above, let me know. kevin pgpYyociMQWA4.pgp Description: OpenPGP digital signature ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Re: bex represents pagure emails in hyperkitty
On Wed, Jan 18, 2017, at 04:00 PM, Dennis Gilmore wrote: > El mar, 17-01-2017 a las 22:15 +0100, Brian Exelbierd escribió: > > On Tue, Jan 17, 2017, at 09:55 PM, Dusty Mabe wrote: > > > > > > The atomic working group has configured pagure to send > > > notifications to > > > the > > > cloud mailing list. These notifications come through as normal > > > emails > > > but for some reason in hyperkitty the emails from pagure show up as > > > coming from Brian Exelbierd (bex). Anyone know why that is? > > > > Because like Batman - I am everywhere baby > > > > My real theory is that when I set up the fedora-budget repo to send > > emails to budget-de...@lists.fp.o I must have somehow linked the > > email > > ID to my name when adding the address as an authorized email. I > > can't > > find any evidence of this in hyperkitty, however I also can't get my > > mailman settings page to even load. > > > > regards, > > > > bex > > > > > > > > You can see that he has the most posts on the summary page: > > > https://lists.fedoraproject.org/archives/list/cloud@lists.fedorapro > > > ject.org/ > > > > > > Here is an example of a single email that looks like it is coming > > > from > > > him: > > > https://lists.fedoraproject.org/archives/list/cloud@lists.fedorapro > > > ject.org/thread/EI6QCHLZSM3UDEPM6OWQPJCQ4R7DA5WC/ > > they all show as being from Ankur Sinha now > > I suspect it is hyperkitty being dumb and setting all emails from pagur > e...@pagure.io to the name of the person who last commented on an issue or > did a PR resulting in an email being sent to a list. This is motivating me to be a prolific commenter. :P regards, bex ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Re: Unretiring itpp
On 01/18/2017 07:01 PM, Jon Ciesla wrote: > > It will need to be re-reviewed, since it's been retired more than two weeks. Of course... Theo. signature.asc Description: OpenPGP digital signature ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Re: Unretiring itpp
On Wed, Jan 18, 2017 at 11:53 AM, Theodore Papadopoulo < theodore.papadopo...@inria.fr> wrote: > Hi, > > I'd like to unretire itpp(which was retired on 2011-07-25 due to > constant C++ build problems). It seems that those problems have been > solved and that as of (at least) itpp-4.3.1, it now correctly builds. > > Basically I recovered the last spec from fedpkgs and adapted it to cmake > (which is now supported by itpp). As far as I can tell, it builds with > almost no troubles. The only problem is that libraries got installed (as > usual with cmake) in /usr/lib and not in /usr/lib64, which I worked > around with a mv (not sure this is teh best solution, but it works). > > itpp is a veru general library for signal processing and is also used in > a brain computer interface suite called OpenVibe, which without itpp is > crippled on fedora (which is not the case on Unbutu or windows for > example). > > Provided I get some guidance (or readings, account settings, ...), I > ciuld maintain or co-maintain the package if necessary. > > Thank you very much, > > Theo Papadopoulo. > > ___ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > > It will need to be re-reviewed, since it's been retired more than two weeks. -- 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 To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Unretiring itpp
Hi,
I'd like to unretire itpp(which was retired on 2011-07-25 due to
constant C++ build problems). It seems that those problems have been
solved and that as of (at least) itpp-4.3.1, it now correctly builds.
Basically I recovered the last spec from fedpkgs and adapted it to cmake
(which is now supported by itpp). As far as I can tell, it builds with
almost no troubles. The only problem is that libraries got installed (as
usual with cmake) in /usr/lib and not in /usr/lib64, which I worked
around with a mv (not sure this is teh best solution, but it works).
itpp is a veru general library for signal processing and is also used in
a brain computer interface suite called OpenVibe, which without itpp is
crippled on fedora (which is not the case on Unbutu or windows for example).
Provided I get some guidance (or readings, account settings, ...), I
ciuld maintain or co-maintain the package if necessary.
Thank you very much,
Theo Papadopoulo.
Name: itpp
Version:4.3.1
Release:0%{?dist}
Summary:C++ library for math, signal/speech processing, and communications
Group: System Environment/Libraries
License:GPLv2+
URL:http://itpp.sourceforge.net/
Source0:http://downloads.sourceforge.net/itpp/itpp-%{version}.tar.bz2
BuildRoot: %{_tmppath}/%{name}-%{version}-%{release}-root-%(%{__id_u} -n)
# Filed into upstream bugtracker at:
# https://sourceforge.net/tracker/?func=detail&aid=2780001&group_id=37044&atid=418758
BuildRequires: gcc-gfortran, atlas-devel, fftw-devel
BuildRequires: tetex-latex
BuildRequires: doxygen, ghostscript
%description
IT++ is a C++ library of mathematical, signal processing, speech
processing, and communications classes and functions. The kernel of
the IT++ library is built upon templated vector and matrix classes
with many functions for their manipulation. Such a kernel makes IT++
similar to Octave. IT++ makes extensive use of existing open-source
libraries (but not only) for increased functionality, speed, and
accuracy.
%package devel
Summary:Development files for itpp
Group: Development/Libraries
Requires: %{name} = %{version}-%{release}
Requires: pkgconfig
Requires: fftw-devel, atlas-devel, gcc-gfortran
%description devel
This package contains the itpp header files, libs, and man pages.
%package doc
Summary:Documentation for itpp
Group: Development/Libraries
Requires: %{name} = %{version}-%{release}
%description doc
This package contains the documentation for itpp.
%prep
%setup -q
%build
%cmake -DBLA_VENDOR=ATLAS -DCMAKE_BUILD_TYPE=Release -DCMAKE_INSTALL_PREFIX=/usr
make %{?_smp_mflags}
%install
rm -rf $RPM_BUILD_ROOT
make install DESTDIR=$RPM_BUILD_ROOT LIBDIR=$RPM_BUILD_ROOT/usr/lib64
mv $RPM_BUILD_ROOT/usr/lib $RPM_BUILD_ROOT/%{_libdir}
mkdir -p $RPM_BUILD_ROOT/%{_docdir}/%{name}
cp -p COPYING AUTHORS ChangeLog NEWS README \
$RPM_BUILD_ROOT/%{_docdir}/%{name}
%clean
rm -rf $RPM_BUILD_ROOT/
%post -p /sbin/ldconfig
%postun -p /sbin/ldconfig
%files
%defattr(-,root,root,-)
%dir %{_docdir}/%{name}
%{_docdir}/%{name}/[A-Z]*
%{_libdir}/*.so.*
%{_datadir}/%{name}
%files devel
%defattr(-,root,root,-)
%{_includedir}/%{name}
%{_libdir}/*.so
%{_libdir}/pkgconfig/%{name}.pc
%{_bindir}/%{name}-config
%{_mandir}/man1/*
%files doc
%defattr(-,root,root,-)
%{_docdir}/%{name}/html
%changelog
* Wed Jan 18 2017 theodore.papadopo...@inria.fr = 4.3.1-0
- Switched to version 4.3.1
- Adapted to cmake build.
* Wed Jan 18 2017 BogusDateBot
- Eliminated rpmbuild "bogus date" warnings due to inconsistent weekday,
by assuming the date is correct and changing the weekday.
Tue Sep 13 2006 --> Tue Sep 12 2006 or Wed Sep 13 2006 or Tue Sep 19 2006 or
Sun Oct 28 2006 --> Sun Oct 22 2006 or Sat Oct 28 2006 or Sun Oct 29 2006 or
* Wed Feb 09 2011 Fedora Release Engineering - 4.0.6-3
- Rebuilt for https://fedoraproject.org/wiki/Fedora_15_Mass_Rebuild
* Fri Jul 24 2009 Fedora Release Engineering - 4.0.6-2
- Rebuilt for https://fedoraproject.org/wiki/Fedora_12_Mass_Rebuild
* Fri Apr 24 2009 Milos Jakubicek - 4.0.6-1
- Fix FTBFS:
- Update to 4.0.6 bugfix release
- Dropped itpp-gcc43.patch (merged upstream).
- Added itpp-gcc44.patch
* Wed Feb 25 2009 Fedora Release Engineering - 4.0.0-7
- Rebuilt for https://fedoraproject.org/wiki/Fedora_11_Mass_Rebuild
* Mon Dec 15 2008 Deji Akingunola - 4.0.0-6
- Rebuild for atlas-3.8.2
* Sun Sep 14 2008 Manuel "lonely wolf" Wolfshant - 4.0.0-5
- Fix building with gcc4.3
* Fri May 23 2008 Jon Stanley - 4.0.0-4
- Fix license tag
* Mon Feb 18 2008 Fedora Release Engineering - 4.0.0-3
- Autorebuild for GCC 4.3
* Sun Dec 9 2007 Ed Hill - 4.0.0-2
- fix hard-coded libdir error
* Sun Dec 9 2007 Ed Hill - 4.0.0-1
- new upstream 4.0.0
* Sat Aug 25 2007 Ed Hill - 3.10.12-1
- new upstream 3.10.12
* Tue Apr 17 2007 Ed Hill - 3.10.10-1
- new upstream 3.10.10
* Tue Apr 17 2007
Re: RFH: Annotating ELF binaries
Hi Carlos, > I've added 2 questions to the Toolchain/Watermark wiki but will post them > here for posterity: Thanks - I'll try answering them here first, and if my answers make sense then I will update the wiki. > (1) What happened to SHT_GNU_ATTRIBUTES and how does it relate to what > you are proposing? Good question, and unfortunately I do not know the answer. The problem is, I have been unable to locate any documentation that describes SHT_GNU_ATTRIBUTES and how it is supposed to be used. I think that the two schemes are quite similar, although this new proposal is intended to be able to cope with attributes that only apply to part of an executable and not necessarily the executable as a whole. (Also, IMHO, my proposal has better documentation...) > (2) What is being done to ensure the attributes are space and time > efficient for dynamic link comparison in the dynamic linker? > Speed of checking 10,000 DSOs (scalability) for ABI compatibility is > going to be a very important requirement. I believe that H.J's design for the dynamic link notes does take efficiency into consideration, but I will leave that for him to comment on further. One thing that I have already done for the static notes is to implement a new option for objcopy called "--merge-notes" which eliminates redundancies. Theoretically this option could be extended to work with the dynamic notes too, helping to make them as space efficient as possible. Another possibility is that the linker could be extended so that when it creates a dynamic executable it also inserts a "master" dynamic linker note, which contains all of the information that the dynamic linker will need, without it having to search through all of the shared libraries used by the application. (This does assume that the shared libraries examined at static link time are the same ones that are loaded/used at dynamic link time). > (b) Loadable notes and space/time efficiency vs. non-loadable notes and > static analysis tools. > > Run-time checking of properties is radically different from offline > checking of properties and we absolutely need two different designs to > meet these needs. However, if we could weld the two together in a compatible > way, that would be great. For example if the dynamic loader could map from > a 'run-time property' to a 'link-time property' to increase the verbosity > of the error in a failure scenario, then that might be beneficial. I think that this might not be easy to do in a way that both imposes a low code-increase cost on the dynamic linker and a keep-the-dynamic-link-notes-small space requirement. There is no harm in investigating though. > If we > could translate 'link-time notes' into 'a collection of run-time properties' > in > a semi-automatic fashion given strict rules about the notes application, > then that would also be awesome. Now this might well be feasible. I am thinking of another new option to objcopy here that examines the static notes and generates dynamic notes from them. This should be quite straightforward, provided that the static notes have captures the right information. Cheers Nick ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Review swap
Hey all, I've got two Python packages in need of review and I'd be happy to review your package requests in return: * https://bugzilla.redhat.com/show_bug.cgi?id=1410901 * https://bugzilla.redhat.com/show_bug.cgi?id=1412798 Thanks! -- Jeremy Cline XMPP: jer...@jcline.org IRC: jcline signature.asc Description: OpenPGP digital signature ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Re: nfs-utils-2.1.1 Changes Everything!
Hello, On 01/16/2017 03:11 PM, Steve Dickson wrote: > Hello, > > The latest nfs-utils release drastically changes how the NFS > servers are configured, for the good IMHO... > > All daemon configuration now goes through /etc/nfs.conf. > See nfs.conf(5) for details. > > The command line interfaces in the systemd services files > have been removed. Which means all your current configures > will break, because the variables in /etc/sysconfig/nfs are > no longer used. > > Again, I think is a move in the right direction and I know > you might find this surprising 8-) but I really don't want to > break all the current server configuration. So I'm trying t > o figure out how to do this with least amount of impact. > > Here is what I see as the options > > 1) Upgrade rawhide w/out a backward compatible patch > (since it is so early in the release cycle) > Upgrade f25 with an backwards compatible patch > > 2) Upgrade rawhide and f25 with the backward compatible > patch... but we have to ween ourselves of the command > line interface at some point... > > 3) Do nothing and push everything into f27, which is the least > favorite option. > > I'm leaning toward option 1... but I'm asking... so I'm listening. :-) After further review of the actual /etc/nfs.conf interface... It's a bit incomplete. There are flags you can set with the current interface but not with /etc/nfs.conf. These holes are fixable but I think the best thing to do is keep the current configuration in as the /etc/nfs.conf matures. Then figure out a migration path or not? Maybe it makes senses to keep both the upstream and Fedora way of configuring the NFS server? Anyways... Thanks for all the input It was appreciated! steved. > > Also, how do I documented something like this? > > tia, > > steved. > ___ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@lists.fedoraproject.org ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Re: bex represents pagure emails in hyperkitty
El mar, 17-01-2017 a las 22:15 +0100, Brian Exelbierd escribió: > On Tue, Jan 17, 2017, at 09:55 PM, Dusty Mabe wrote: > > > > The atomic working group has configured pagure to send > > notifications to > > the > > cloud mailing list. These notifications come through as normal > > emails > > but for some reason in hyperkitty the emails from pagure show up as > > coming from Brian Exelbierd (bex). Anyone know why that is? > > Because like Batman - I am everywhere baby > > My real theory is that when I set up the fedora-budget repo to send > emails to budget-de...@lists.fp.o I must have somehow linked the > email > ID to my name when adding the address as an authorized email. I > can't > find any evidence of this in hyperkitty, however I also can't get my > mailman settings page to even load. > > regards, > > bex > > > > > You can see that he has the most posts on the summary page: > > https://lists.fedoraproject.org/archives/list/cloud@lists.fedorapro > > ject.org/ > > > > Here is an example of a single email that looks like it is coming > > from > > him: > > https://lists.fedoraproject.org/archives/list/cloud@lists.fedorapro > > ject.org/thread/EI6QCHLZSM3UDEPM6OWQPJCQ4R7DA5WC/ they all show as being from Ankur Sinha now I suspect it is hyperkitty being dumb and setting all emails from pagur e...@pagure.io to the name of the person who last commented on an issue or did a PR resulting in an email being sent to a list. Dennis > > Dusty > > signature.asc Description: This is a digitally signed message part ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Re: Self-Introduction: Daniel Moerner
Hello Daniel and welcome! On 17/01/17 17:45, Daniel Moerner wrote: Hi everyone, My name is Daniel Moerner. I am interested in contributing to Fedora as a package maintainer. My GPG key fingerprint is BBD6 4965 3FB1 47F3 C7CD 0A30 CB3D 014E D7F1 B32A. I live in New Haven, CT, where I am a PhD student in philosophy at Yale University. My first Linux distribution was Fedora Core 1, and I've been using Linux full-time since 2007. In my earlier years I contributed to Debian development, focusing on tools for lightweight WMs (including pekwm, tint2) and interpreters for functional programming languages (including ypsilon, smlnj). I was a member of the debian-maintainers keyring from 2009-2010, before stepping down due to lack of time. I am a bit older now, and I have the time and interest to commit to contributing to Fedora, which I use on all of my machines. I have two main areas I want to contribute to in Fedora. First, I am still interested in functional programming, particularly in Standard ML. Fedora's support for SML is currently a bit poor, and I hope to work to improve it. Second, I am interested in games and game emulators, building on Fedora's recent change in their policy on emulators. I have already introduced myself to the Games SIG, and I don't want to repeat too much here.[1] I will just say that I find game emulators fascinating from both a technical and historical/archival perspective. I also love documentation, especially man pages. (Who doesn't?) I view writing manpages and submitting them upstream as part of my role as a packager. I feel the same way about QA work; I recently wrote and submitted a basic manpage upstream for a recent practice review I completed.[2] Recently, I've been spending more time in IRC under my handle, dmoerner. Here is a link for my first review request, the Game Boy and Game Boy Color emulator Gearboy, for which I need a sponsor: https://bugzilla.redhat.com/show_bug.cgi?id=1414087 I tried to include all the relevant information in the review request for any potential sponsor. I look forward to being involved in Fedora! Best, Daniel [1] https://lists.fedoraproject.org/archives/list/ga...@lists.fedoraproject.org/thread/LPEW5CCGK6JRGDCV3CTRXGGDTAD2EHO5/ [2] https://bugzilla.redhat.com/show_bug.cgi?id=1410651#c1 ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Re: Package question: zanata-platform
On 18/01/17 08:29, Ding Yi Chen wrote: On version 4.0.0, we merge all the sub projects like parent, api, common, client and server into zanata-platform. At this point, we have no plan to pack server as RPM yet, because there too many dependencies to solve (Maven and Java-scripts) Should I continue to call it zanata-client, or rename them as zanata-platform? Regards, I think it should be zanata-platform despite it doesn't include server yet, but given it's more than just the client I think it makes more sense. Cheers, Sylvia ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Re: Self-Introduction: Daniel Moerner
Hello and welcome! Charalampos Stratakis Associate Software Engineer Python Maintenance Team, Red Hat - Original Message - From: "Daniel Moerner" To: devel@lists.fedoraproject.org Sent: Tuesday, January 17, 2017 6:45:56 PM Subject: Self-Introduction: Daniel Moerner Hi everyone, My name is Daniel Moerner. I am interested in contributing to Fedora as a package maintainer. My GPG key fingerprint is BBD6 4965 3FB1 47F3 C7CD 0A30 CB3D 014E D7F1 B32A. I live in New Haven, CT, where I am a PhD student in philosophy at Yale University. My first Linux distribution was Fedora Core 1, and I've been using Linux full-time since 2007. In my earlier years I contributed to Debian development, focusing on tools for lightweight WMs (including pekwm, tint2) and interpreters for functional programming languages (including ypsilon, smlnj). I was a member of the debian-maintainers keyring from 2009-2010, before stepping down due to lack of time. I am a bit older now, and I have the time and interest to commit to contributing to Fedora, which I use on all of my machines. I have two main areas I want to contribute to in Fedora. First, I am still interested in functional programming, particularly in Standard ML. Fedora's support for SML is currently a bit poor, and I hope to work to improve it. Second, I am interested in games and game emulators, building on Fedora's recent change in their policy on emulators. I have already introduced myself to the Games SIG, and I don't want to repeat too much here.[1] I will just say that I find game emulators fascinating from both a technical and historical/archival perspective. I also love documentation, especially man pages. (Who doesn't?) I view writing manpages and submitting them upstream as part of my role as a packager. I feel the same way about QA work; I recently wrote and submitted a basic manpage upstream for a recent practice review I completed.[2] Recently, I've been spending more time in IRC under my handle, dmoerner. Here is a link for my first review request, the Game Boy and Game Boy Color emulator Gearboy, for which I need a sponsor: https://bugzilla.redhat.com/show_bug.cgi?id=1414087 I tried to include all the relevant information in the review request for any potential sponsor. I look forward to being involved in Fedora! Best, Daniel [1] https://lists.fedoraproject.org/archives/list/ga...@lists.fedoraproject.org/thread/LPEW5CCGK6JRGDCV3CTRXGGDTAD2EHO5/ [2] https://bugzilla.redhat.com/show_bug.cgi?id=1410651#c1 ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Re: Request for review swap
Till Hofmann wrote on 01/18/2017 09:30 PM: On 18.01.2017 13:09, Mamoru TASAKA wrote: Hello, all: I have one review request for a package for LXDE: https://bugzilla.redhat.com/show_bug.cgi?id=1409243 lxhotkey Review swap is appreciated. I'll take it. Can you please review librealsense: https://bugzilla.redhat.com/show_bug.cgi?id=1413646 Taken. Will review later. Thank you for taking my review request. Regards, Mamoru ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Re: Request for review swap
On 18.01.2017 13:09, Mamoru TASAKA wrote: > Hello, all: > > I have one review request for a package for LXDE: > https://bugzilla.redhat.com/show_bug.cgi?id=1409243 lxhotkey > > Review swap is appreciated. I'll take it. Can you please review librealsense: https://bugzilla.redhat.com/show_bug.cgi?id=1413646 Thank you! Till ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Re: Is there something wrong with the Koji builders?
Python 3 started failing on i686, x86_64 and arm only. https://koji.fedoraproject.org/koji/taskinfo?taskID=17313924 The failures come from the test_socket.py [0], test_aead_aes_gcm [1] and more specifically this line [2] with the message: OSError: [Errno 22] Invalid argument This test is checking Python's interface for the kernel crypto API (added in 3.6 [3]). [0] https://hg.python.org/cpython/file/3.6/Lib/test/test_socket.py#l5473 [1] https://hg.python.org/cpython/file/3.6/Lib/test/test_socket.py#l5472 [2] https://hg.python.org/cpython/file/3.6/Lib/test/test_socket.py#l5497 [3] http://bugs.python.org/issue27744 Charalampos Stratakis Associate Software Engineer Python Maintenance Team, Red Hat - Original Message - From: "Kevin Fenzi" To: devel@lists.fedoraproject.org Sent: Monday, January 16, 2017 5:16:40 PM Subject: Re: Is there something wrong with the Koji builders? On Mon, 16 Jan 2017 09:38:25 -0500 (EST) Jaroslav Skarvada wrote: > - Original Message - > > I've done two builds for rawhide this morning. > > > > On the first the armv7hl and ppc64le builds failed because the > > source tar file could not be unpacked. > > > > On the second the aarch64 build failed because the source tar file > > could not be unpacked. > > > > All the other arches built successfully. > > > > -- > > > > Kaleb > > ___ > > devel mailing list -- devel@lists.fedoraproject.org > > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > > > > I am encountering the same problem even on i686 (when trying to > scratch build graphviz [1, 2]), so there is probably something wrong > with the builders Yes, there's been ongoing issues since last week: * This issue (which seems new in the last few days) where srpm isn't unpacking correctly. https://pagure.io/fedora-infrastructure/issue/5694 * Sometimes downloads of packages for the mock chroot are failing. Even though there's nothing at all wrong with the squid cache (and In fact I added a second one this weekend). https://pagure.io/fedora-infrastructure/issue/5689 * buildvm's are unstable and sometimes reboot or have odd kernel blowups. (The 4.9.x kernel bug is https://bugzilla.redhat.com/show_bug.cgi?id=1413314 but it might not be a kernel bug at all, since 4.8.x kernels are doing the same now as well. I guess my monday is all mapped out for me. ;) will keep the above bugs posted and report back here when I figure anything out. ;( kevin ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Request for review swap
Hello, all: I have one review request for a package for LXDE: https://bugzilla.redhat.com/show_bug.cgi?id=1409243 lxhotkey Review swap is appreciated. Regards, Mamoru ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Re: Planned Outage: Taskotron - 2017-01-17 20:00 UTC
Outage is complete, everything is back up and running. Please let us know if you see anything not working correctly. Tim On Mon, 16 Jan 2017 13:22:20 -0700 Tim Flink wrote: > There will be an outage starting at 2017-01-17 20:00 UTC, which will > last approximately 12 hours. > > To convert UTC to your local time, take a look at > https://fedoraproject.org/wiki/UTCHowto > or run: > > date -d '2016-01-17 20:00 UTC' > > Reason for outage: > > We will be upgrading Taskotron to a new version which requires a > migration that will take 8-12 hours. This migration will be very > infrequent if it ever happens and we don't anticipate needing long > outages like this in the future > > All jobs which would have run during the outage will be queued for > execution after the outage has completed > > Affected Services: > > All services on taskotron.fedoraproject.org > > Ticket Information: https://pagure.io/fedora-infrastructure/issue/5697 > > Contact Information: infrastruct...@lists.fedoraproject.org > > Please join #fedora-admin in irc.freenode.net or add comments to the > ticket for this outage above. pgpl7eSMFhOP7.pgp Description: OpenPGP digital signature ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Package question: zanata-platform
On version 4.0.0, we merge all the sub projects like parent, api, common, client and server into zanata-platform. At this point, we have no plan to pack server as RPM yet, because there too many dependencies to solve (Maven and Java-scripts) Should I continue to call it zanata-client, or rename them as zanata-platform? Regards, -- Ding-Yi Chen Software Engineer Globalization Group DID: +61 7 3514 8239 Email: dc...@redhat.com Red Hat, Asia-Pacific Pty Ltd Level 1, 193 North Quay Brisbane 4000 Office: +61 7 3514 8100 Fax: +61 7 3514 8199 Website: www.redhat.com Red Hat, Inc. Facebook: Red Hat APAC | Red Hat Japan | Red Hat Korea | JBoss APAC Twitter: Red Hat APAC | Red Hat ANZ LinkedIn: Red Hat APAC | JBoss APAC ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
