EPEL missing amavisd-new dependencies in epel6-arm

[Robert Moskowitz]

I am working on installing amavis-new on an arm system (Cubietruck with 
Redsleeve 6).  It has dependency issues.  I tried 'yum deplist 
amavis-new' and extracting from it I see:


  dependency: perl(Net::Server) = 0.87
   Unsatisfied dependency

  dependency: perl(Mail::SPF)
   Unsatisfied dependency

Can someone see about adding these (and any of their dependencies) to 
the epel6-arm repo?


thank you.


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

EPEL epel6 for arm

[Robert Moskowitz]

Well, it was just explained to me on the Redsleeve list, that the 
epel6-arm repo was done by a single maintainer who is no longer 
maintaining it.


Since at some point there will be work on the Centos7 for arm, and thus 
a need for epel7 for arm, I would really like to see the epel6 for arm 
brought current and a few things I need for like dovecot and amavisd be 
added.


thanks


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

Re: EPEL missing amavisd-new dependencies in epel6-arm

[Stephen John Smoogen]

On 8 October 2014 07:34, Robert Moskowitz r...@htt-consult.com wrote:

 I am working on installing amavis-new on an arm system (Cubietruck with
 Redsleeve 6).  It has dependency issues.  I tried 'yum deplist amavis-new'
 and extracting from it I see:

   dependency: perl(Net::Server) = 0.87
Unsatisfied dependency

   dependency: perl(Mail::SPF)
Unsatisfied dependency

 Can someone see about adding these (and any of their dependencies) to the
 epel6-arm repo?


Where are you getting an epel6 arm? There isn't one that we maintain



 thank you.


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




-- 
Stephen J Smoogen.
___
epel-devel mailing list
epel-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/epel-devel

Re: EPEL missing amavisd-new dependencies in epel6-arm

[Stephen John Smoogen]

On 8 October 2014 09:17, Robert Moskowitz r...@htt-consult.com wrote:


 On 10/08/2014 11:01 AM, Stephen John Smoogen wrote:



 On 8 October 2014 07:34, Robert Moskowitz r...@htt-consult.com wrote:

 I am working on installing amavis-new on an arm system (Cubietruck with
 Redsleeve 6).  It has dependency issues.  I tried 'yum deplist amavis-new'
 and extracting from it I see:

   dependency: perl(Net::Server) = 0.87
Unsatisfied dependency

   dependency: perl(Mail::SPF)
Unsatisfied dependency

 Can someone see about adding these (and any of their dependencies) to the
 epel6-arm repo?


  Where are you getting an epel6 arm? There isn't one that we maintain


 http://ftp.redsleeve.org/pub/el6/packages/epel/mirrors

 No, you are not maintaining it, as has been explained to me this morning
 by the Redsleeve leader, Gordon Bobic.  He said that it originally was put
 together by Michael Lang who has since moved on to other things.  So
 basically it seems it is orphaned.  It would be really nice if the epel
 community takes it on.  Get your feet wet so to speak before the
 Centos7-arm work.



We would need a RHEL-7 or CentOS-7 arm before we could even start building
stuff for EPEL-arm. It isn't a chicken or an egg problem, but a chicken and
then the egg problem.



-- 
Stephen J Smoogen.
___
epel-devel mailing list
epel-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/epel-devel

Re: EPEL missing amavisd-new dependencies in epel6-arm

[Robert Moskowitz]

On 10/08/2014 11:29 AM, Stephen John Smoogen wrote:



On 8 October 2014 09:17, Robert Moskowitz r...@htt-consult.com 
mailto:r...@htt-consult.com wrote:



On 10/08/2014 11:01 AM, Stephen John Smoogen wrote:



On 8 October 2014 07:34, Robert Moskowitz r...@htt-consult.com
mailto:r...@htt-consult.com wrote:

I am working on installing amavis-new on an arm system
(Cubietruck with Redsleeve 6).  It has dependency issues.  I
tried 'yum deplist amavis-new' and extracting from it I see:

  dependency: perl(Net::Server) = 0.87
   Unsatisfied dependency

  dependency: perl(Mail::SPF)
   Unsatisfied dependency

Can someone see about adding these (and any of their
dependencies) to the epel6-arm repo?


Where are you getting an epel6 arm? There isn't one that we maintain


http://ftp.redsleeve.org/pub/el6/packages/epel/mirrors

No, you are not maintaining it, as has been explained to me this
morning by the Redsleeve leader, Gordon Bobic. He said that it
originally was put together by Michael Lang who has since moved on
to other things.  So basically it seems it is orphaned.  It would
be really nice if the epel community takes it on.  Get your feet
wet so to speak before the Centos7-arm work.



We would need a RHEL-7 or CentOS-7 arm before we could even start 
building stuff for EPEL-arm. It isn't a chicken or an egg problem, but 
a chicken and then the egg problem.


This I understand.  First we need that Centos7 arm.  The Centos team 
made a call to start working on it a couple months ago, but there is no 
apparent activity on the centos-arm list.  I suspect higher priority 
migrations (like C7-i386).


But there is an equiv to Centos6-arm, and that is Redsleeve6.  There is 
that large community of Rasp-PI out there, but I see the Allwinner chip, 
particularly the Cubieboard as a more server device (has a sata 
interface and 1 - 2 G memory).


I was told that I might have to use cpan2rpm for these two, but that 
will be yet another new advanture.


And for Dovecot, I am missing:

perl-Email-Valid
perl-Log-Log4perl
perl-MIME-EncWords
imapsync

Going to have to figure out how to get those.

In the epel6 repo they all show as -noarch


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

Re: btrfs as default filesystem for F22?

[Thorsten Leemhuis]

Thorsten Leemhuis wrote on 08.10.2014 07:52:
 Josh Boyer wrote on 07.10.2014 21:15:
 On Tue, Oct 7, 2014 at 2:24 PM, Josef Bacik jo...@toxicpanda.com wrote:
 […]
 I think the point is somewhat valid though. To just keep repeating the
 mantra 'its not ready' is not going to make it any more ready. If suse
 can identify a stable subset of btrfs features and use it as their
 default file system with those restrictions, why can't we do the same ?
 The approach makes sense to me, at least...
 Because they still have the support staff for when users don't listen,
 Fedora doesn't.
 As an aside, I looked at their 3.16.2-1.1.gdcee397 kernel-source SRPM.
 I can't find any patches that limit btrfs usage.  I could totally be
 wrong, but if someone knows of a patch that limits the features please
 point me to it.
 
 Due to a coincidence I yesterday took a quick look myself and didn't
 spot anything. But in case you haven't looked further: I found one in
 the SLE-Kernels:
 
 http://kernel.opensuse.org/cgit/kernel-source/tree/patches.suse/btrfs--add-allow_unsupported-module-parameter.patch?h=SLE11-SP3
 http://kernel.opensuse.org/cgit/kernel-source/tree/patches.suse/btrfs--add-allow_unsupported-module-parameter.patch?h=SLE12

BTW  TWIMC, their solution to problems like this
http://aseigo.blogspot.de/2014/09/btrfs-rebalancing.html (ran into this
myself yesterday) seems to be a package called btrfsmaintenance that was
introduced a few days ago. Quoting
http://article.gmane.org/gmane.linux.suse.opensuse.devel/59787/

 From: David Sterba dsterba at suse.cz
 Subject: Introduce btrfsmaintenance package to Factory
 Newsgroups: gmane.linux.suse.opensuse.devel
 Date: 2014-10-06 15:40:37 GMT (1 day, 14 hours and 40 minutes ago)
 
 Hi,
 
 let me introduce a new package that supplements the btrfs filesystem and aims
 to automate a few maintenance tasks. This means the scrub, balance, trim or
 defragmentation. The package comes from SLE12 where btrfs is going to be the
 default filesystem as well.
 
 Each of the tasks can be turned on/off and configured independently. The
 default config values were selected to fit the default installation profile.
 
 * scrub - go through all medatada/data and verify the checksums, default 
 period
 is one month
 
 * balance - the balance command can do a lot of things, in general moves data
 around in big chunks, here we use it to reclaim back the space of the
 underused chunks so it can be allocated again according to current needs
 
 The point is to prevent some corner cases where it's not possible to eg.
 allocate new metadata chunks because the whole device space is reserved for 
 all
 the chunks, although the total space occupied is smaller and the allocation
 should succeed.
 
 * trim - run TRIM on the filesystem using the 'fstrim' utility, makes sense 
 for
 SSD devices.
 
 * defrag - run defrag on configured directories. This is for convenience and
 not necessary.
 
 There's a separate defragmentation task that happens automatically and
 defragments only the RPM database files in /var/lib/rpm. This is done via a
 zypper plugin and the defrag pass triggers at the end of the installation.
 
 This improves reading the RPM databases later, but the installation process
 fragments the files very quickly so it's not likely to bring a significant
 speedup here.
 
 Cron takes care of periodic execution of the scripts, but they can be run any
 time directly from /usr/share/btrfs/maintenance/, respecting the configured
 values in /etc/sysconfig/btrfsmaintenance.
 
 If the period is changed manually, the cron symlinks have to be refreshed, use
 systemctl restart btrfsmaintenance-refresh (or the
 rcbtrfsmaintenance-refresh shortcut). Changing the period via yast2 
 sysconfig
 editor triggers the refresh automatically.
 
 The project lives in obs://filesystems/btrfsmaintenance and I'm going to 
 submit
 it to Factory.
 
 I'd like to ask volunteers to give it some testing.  Feedback is welcome.
 
 Thanks,
 David

The package in the opensuse obs:
https://build.opensuse.org/package/show/filesystems/btrfsmaintenance

Seems to mostly consist of shell scripts.

CU
knurd
-- 
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: Possible PPC kernel bug on builders

[Dan Horák]

On Tue, 7 Oct 2014 16:27:52 -0600
Jerry James loganje...@gmail.com wrote:

 On Mon, Oct 6, 2014 at 2:36 PM, Jerry James loganje...@gmail.com
 wrote:
  I posted about this 5 days ago on ppc list [1], but have had no
  response.  I tried to get some attention on #fedora-ppc today, also
  with no success.  I am failing miserably to get the attention of any
  of the PPC folks, so I am trying email here to see if this will
  work.
 
 Still nothing.  Can anybody help me get the attention of somebody on
 the PPC team?

we know about it, don't have any answer yet :-(


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

syslinux-6.03

[Joachim Backes]

Anybody can tell when syslinux-6.03 will be available in F21?

(https://lists.fedoraproject.org/pipermail/test/2014-October/123202.html)

My reason for this request:
https://bugzilla.redhat.com/show_bug.cgi?id=1141496

Thanks.

Kind regards

-- 

Fedora release 21 (Twenty One)
Kernel-3.17.0-300.fc21.x86_64


Joachim Backes joachim.bac...@rhrk.uni-kl.de
https://www-user.rhrk.uni-kl.de/~backes
-- 
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: Orphan packages in rawhide

[Lukas Zapletal]

   launchy (maintained by: lzap)
   launchy-2.5-11.fc22.src requires boost-devel = 1.55.0-4.fc22

I don't understand why this package is included in the list. I still
maintain it, it builds fine. Can someone explain? I am short of
caffeine.

LZ

-- 
Later,
 Lukas #lzap Zapletal
-- 
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: Orphan packages in rawhide

[Martin Preisler]

- Original Message -
 From: Lukas Zapletal l...@redhat.com
 To: devel@lists.fedoraproject.org
 Sent: Wednesday, October 8, 2014 10:05:23 AM
 Subject: Re: Orphan packages in rawhide
 
  launchy (maintained by: lzap)
  launchy-2.5-11.fc22.src requires boost-devel = 1.55.0-4.fc22
 
 I don't understand why this package is included in the list. I still
 maintain it, it builds fine. Can someone explain? I am short of
 caffeine.

It depends on boost which in turn depends on mpich which was orphaned.

-- 
Martin Preisler
-- 
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: Orphan packages in rawhide

[Lukas Zapletal]

 It depends on boost which in turn depends on mpich which was orphaned.

Oh, I've forced out this option from my mind. Interesting.

Well, launchy is not much maintained software and not in wide use. I am
fine with orphaning it.

Thanks

-- 
Later,
 Lukas #lzap Zapletal
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

[PkgDB] jplesnik:perl-Feed-Find watchcommits set to Approved

[pkgdb]

user: jplesnik set for jplesnik acl: watchcommits of package: perl-Feed-Find 
from: Approved to: Approved on branch: el5

To make changes to this package see:
https://admin.fedoraproject.org/pkgdb/package/perl-Feed-Find
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-de...@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel

Re: Orphan packages in rawhide

[Martin Preisler]

- Original Message -
 From: Lukas Zapletal l...@redhat.com
 To: Development discussions related to Fedora 
 devel@lists.fedoraproject.org
 Sent: Wednesday, October 8, 2014 10:30:37 AM
 Subject: Re: Orphan packages in rawhide
 
  It depends on boost which in turn depends on mpich which was orphaned.
 
 Oh, I've forced out this option from my mind. Interesting.
 
 Well, launchy is not much maintained software and not in wide use. I am
 fine with orphaning it.

You don't have to orphan it. No action is required. The email is basically
telling you that one of your deps got orphaned, perhaps you might want to
adopt it yourself. At least that's how I understand it.

And since a lot of packages depend on boost there are a lot of packages
on that list :-)

-- 
Martin Preisler
-- 
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

[Mustafa Muhammad]

On Mon, Oct 6, 2014 at 9:55 PM, Jonathan Dieter jdie...@lesbg.com wrote:
 On 10/06/2014 08:57 PM, Reindl Harald wrote:

 Am 06.10.2014 um 19:45 schrieb Florian Festi:

 The way of getting around all this unnecessary computation is
 establishing trust via the deltarpm itself and giving up the idea of
 reconstructing the originally rpm as a prove of everything worked out
 just fine.

 To save even more time the delta would need to be applied directly on
 disk without creating an package at all. This would require a deeper
 integration with rpm and requires some tricky algorithms to make sure
 everything is ok in advance and won't blow up during the rpm
 transaction. So if anyone needs a hobby...


 oh no - don't tie all together for reasons which did not destory the
 world over years - it is a damned good design that the part dealing with
 rpm packages don't need to know anything aboutt delta rpms because the
 normal packages are created before that step

 don't break the unix-way of work the current behavior follows for no
 good reason and there is none - otherwise deltarpm would not have been
 default over years the way it works now


 Ok, granted, this sounds pretty scary.  But if we give rpm the ability to
 upgrade an installed package with a deltarpm, it wouldn't take away
 deltarpm's ability to generate a full rpm from a deltarpm.  And it does have
 the advantage of cutting right through the knot.  We already store checksums
 of the deltarpms in prestodelta.xml, as well as in the deltarpm itself.

 Probably the biggest weakness would be the chance that something would
 change on-disk between the check stage and actual install stage.  We'd have
 to evaluate whether it's worth making a temporary copy of the old data
 during the check stage and then applying the deltarpm to that.

 All of this would require a lot of buy-in from the rpm guys, though
 (Florian, you're one of them, right?).  If I recall correctly, when we first
 looked at deltarpms, one of the selling points was that rpm didn't have to
 change at all.

 Jonathan

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

Hi,
I live in a country where 1 Mbps (128 KB/s) is more than the average
(and considered GOOD), we really need deltarpm, it saves huge amounts
of data and time.
I think the problem is in compressing then decompressing the file, why
we don't take checksum of the tar file before compression? (of course
this must be done on the server too), this way we can use deltarpm
without much CPU, this should provide the best of the two worlds.

Mustafa Muhammad
-- 
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: Orphan packages in rawhide

[Emmanuel Seyman]

* Lukas Zapletal [08/10/2014 10:05] :

  launchy (maintained by: lzap)
  launchy-2.5-11.fc22.src requires boost-devel = 1.55.0-4.fc22
 
 I don't understand why this package is included in the list. I still
 maintain it, it builds fine. Can someone explain? I am short of
 caffeine.

It's in the list of packages that are going to be inpacted by the fact that
boost is about to be orphaned.

Emmanuel
-- 
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: Installer - how to get a shell ?

[David Timms]

On 08/10/14 10:41, Mike Ruckman wrote:
 The list of ttys you see along the bottom is from tmux [0]. From that screen
 if you were to hit `ctrl-b 2` it would switch to the pane labelled 'shell' at
 the bottom of the screen.
Uh-hah, thankyou.
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

F-21 Branched report: 20141008 changes

[Fedora Branched Report]

Compose started at Wed Oct  8 07:15:02 UTC 2014
Broken deps for armhfp
--
[PyQuante]
PyQuante-libint-1.6.4-11.fc21.1.armv7hl requires libint(armv7hl-32) = 
0:1.1.6-2.fc21
[audtty]
audtty-0.1.12-9.fc20.armv7hl requires libaudclient.so.2
[authhub]
authhub-0.1.2-3.fc19.armv7hl requires libjson.so.0
[avro]
avro-mapred-1.7.5-9.fc21.noarch requires hadoop-mapreduce
avro-mapred-1.7.5-9.fc21.noarch requires hadoop-client
[cduce]
cduce-0.5.5-9.fc21.armv7hl requires ocaml(Camlp4) = 
0:ebd368022fd2bc7b305a42902efa4c90
[cp2k]
cp2k-2.5.1-8.fc21.armv7hl requires libint(armv7hl-32) = 0:1.1.6-2.fc21
cp2k-mpich-2.5.1-8.fc21.armv7hl requires libint(armv7hl-32) = 
0:1.1.6-2.fc21
cp2k-openmpi-2.5.1-8.fc21.armv7hl requires libmpi_usempi.so.1
cp2k-openmpi-2.5.1-8.fc21.armv7hl requires libint(armv7hl-32) = 
0:1.1.6-2.fc21
[deltacloud-core]
deltacloud-core-rackspace-1.1.3-1.fc20.noarch requires 
rubygem(cloudservers)
deltacloud-core-rackspace-1.1.3-1.fc20.noarch requires 
rubygem(cloudfiles)
[django-recaptcha]
django-recaptcha-0.1-7.20091212svn6.fc21.noarch requires python-django14
[dragonegg]
dragonegg-3.4-0.3.rc0.fc21.armv7hl requires gcc = 0:4.8.2-14.fc21
[edelib]
edelib-2.1-5.fc21.armv7hl requires libedelib.so
edelib-devel-2.1-5.fc21.armv7hl requires libedelib.so
[elpa]
elpa-openmpi-2013.11-4.008.fc21.armv7hl requires libmpi_usempi.so.1
[eucalyptus]
eucalyptus-common-java-3.3.0-0.5.20130408git32052445.fc20.armv7hl 
requires hibernate3-jbosscache = 0:3.6.10-7
[fatrat]
1:fatrat-1.2.0-0.21.beta2.fc21.armv7hl requires 
libtorrent-rasterbar.so.7
[flush]
flush-0.9.12-10.fc21.armv7hl requires libtorrent-rasterbar.so.7
[freesteam]
freesteam-ascend-2.1-6.20140724svn753.fc21.armv7hl requires 
libascend.so.1
[gcc-python-plugin]
gcc-python2-debug-plugin-0.12-18.fc21.armv7hl requires gcc = 
0:4.8.2-14.fc21
gcc-python2-plugin-0.12-18.fc21.armv7hl requires gcc = 0:4.8.2-14.fc21
gcc-python3-debug-plugin-0.12-18.fc21.armv7hl requires 
libpython3.3dm.so.1.0
gcc-python3-debug-plugin-0.12-18.fc21.armv7hl requires gcc = 
0:4.8.2-14.fc21
gcc-python3-plugin-0.12-18.fc21.armv7hl requires libpython3.3m.so.1.0
gcc-python3-plugin-0.12-18.fc21.armv7hl requires gcc = 0:4.8.2-14.fc21
[gedit-valencia]
gedit-valencia-0.4.0-1.20131223git94442bf.fc21.armv7hl requires 
libvala-0.24.so.0
[gnome-python2-desktop]
gnome-python2-metacity-2.32.0-18.fc21.armv7hl requires 
libmetacity-private.so.0
[gofer]
ruby-gofer-0.77.1-2.fc21.noarch requires rubygem(qpid) = 0:0.16.0
[leiningen]
leiningen-1.7.1-7.fc20.noarch requires maven-ant-tasks
leiningen-1.7.1-7.fc20.noarch requires classworlds
[libghemical]
libghemical-2.99.1-24.fc20.armv7hl requires libf77blas.so.3
libghemical-2.99.1-24.fc20.armv7hl requires libatlas.so.3
[libmygpo-qt]
libmygpo-qt5-devel-1.0.8-1.fc21.armv7hl requires libmygpo-qt5{?_isa} = 
0:1.0.8-1.fc21
[libopensync-plugin-irmc]
1:libopensync-plugin-irmc-0.22-7.fc20.armv7hl requires libopenobex.so.1
[ltsp]
ltsp-client-5.4.5-8.fc21.armv7hl requires fuse-unionfs
ltsp-server-5.4.5-8.fc21.armv7hl requires cdialog
[meshmagick]
meshmagick-0.6.0-20.svn2898.fc21.armv7hl requires libOgreMain.so.1.8.1
meshmagick-libs-0.6.0-20.svn2898.fc21.armv7hl requires 
libOgreMain.so.1.8.1
[monodevelop-vala]
monodevelop-vala-2.8.8.1-6.fc21.armv7hl requires vala  0:0.25.0
[netdisco]
netdisco-1.1-7.fc21.noarch requires perl(SNMP::Info::Layer2::Bay)
[ocaml-pa-do]
ocaml-pa-do-0.8.16-3.fc21.armv7hl requires ocaml(Camlp4) = 
0:ebd368022fd2bc7b305a42902efa4c90
[openslides]
openslides-1.3.1-3.fc21.noarch requires python-django  0:1.5
[openstack-nova]
openstack-nova-compute-2014.1.2-1.fc21.noarch requires 
libvirt-daemon-xen
[openvas-client]
openvas-client-3.0.3-8.fc20.armv7hl requires libopenvas_omp.so.6
openvas-client-3.0.3-8.fc20.armv7hl requires libopenvas_nasl.so.6
openvas-client-3.0.3-8.fc20.armv7hl requires libopenvas_misc.so.6
openvas-client-3.0.3-8.fc20.armv7hl requires libopenvas_hg.so.6
openvas-client-3.0.3-8.fc20.armv7hl requires libopenvas_base.so.6
[perl-RT-Authen-ExternalAuth]
perl-RT-Authen-ExternalAuth-0.11-5.fc21.noarch requires rt3
[perl-RT-Extension-CommandByMail]
perl-RT-Extension-CommandByMail-0.07-10.fc21.noarch requires 
perl(RT::Interface::Email)
[pipelight-selinux]
pipelight-selinux-0.2.1-2.fc21.noarch requires pipelight-common
pipelight-selinux-0.2.1-2.fc21.noarch requires pipelight-common
pipelight-selinux-0.2.1-2.fc21.noarch requires pipelight
pipelight-selinux-0.2.1-2.fc21.noarch requires pipelight
[pootle]
pootle-2.1.6-8.fc21.noarch requires 

rawhide report: 20141008 changes

[Fedora Rawhide Report]

Compose started at Wed Oct  8 05:15:10 UTC 2014
Broken deps for i386
--
[Agda]
ghc-Agda-2.3.2.2-5.fc22.i686 requires libHSterminfo-0.3.2.5-ghc7.6.3.so
ghc-Agda-2.3.2.2-5.fc22.i686 requires libHShaskeline-0.7.0.3-ghc7.6.3.so
ghc-Agda-2.3.2.2-5.fc22.i686 requires 
ghc(haskeline-0.7.0.3-775b029f16a4b58f3cc6b4cb4f7e7ac5)
ghc-Agda-devel-2.3.2.2-5.fc22.i686 requires 
libHSterminfo-0.3.2.5-ghc7.6.3.so
ghc-Agda-devel-2.3.2.2-5.fc22.i686 requires 
libHShaskeline-0.7.0.3-ghc7.6.3.so
ghc-Agda-devel-2.3.2.2-5.fc22.i686 requires 
ghc-devel(haskeline-0.7.0.3-775b029f16a4b58f3cc6b4cb4f7e7ac5)
ghc-Agda-devel-2.3.2.2-5.fc22.i686 requires 
ghc(terminfo-0.3.2.5-61e0dc43a1465e327dacd9ab37bbe1a3)
ghc-Agda-devel-2.3.2.2-5.fc22.i686 requires 
ghc(haskeline-0.7.0.3-775b029f16a4b58f3cc6b4cb4f7e7ac5)
[PyQuante]
PyQuante-libint-1.6.4-11.fc22.1.i686 requires libint(x86-32) = 
0:1.1.6-2.fc21
[Sprog]
Sprog-0.14-27.fc20.noarch requires perl(:MODULE_COMPAT_5.18.0)
[audtty]
audtty-0.1.12-9.fc20.i686 requires libaudclient.so.2
[authhub]
authhub-0.1.2-3.fc19.i686 requires libjson.so.0
[aws]
aws-devel-3.1.0-6.fc21.i686 requires libgrypt-devel
[blender]
1:blender-2.71-3.fc22.i686 requires libOpenCOLLADAStreamWriter.so.0.1
1:blender-2.71-3.fc22.i686 requires 
libOpenCOLLADASaxFrameworkLoader.so.0.1
1:blender-2.71-3.fc22.i686 requires libOpenCOLLADAFramework.so.0.1
1:blender-2.71-3.fc22.i686 requires libOpenCOLLADABaseUtils.so.0.1
1:blender-2.71-3.fc22.i686 requires libMathMLSolver.so.0.1
1:blender-2.71-3.fc22.i686 requires libGeneratedSaxParser.so.0.1
1:blenderplayer-2.71-3.fc22.i686 requires 
libOpenCOLLADAStreamWriter.so.0.1
1:blenderplayer-2.71-3.fc22.i686 requires 
libOpenCOLLADASaxFrameworkLoader.so.0.1
1:blenderplayer-2.71-3.fc22.i686 requires libOpenCOLLADAFramework.so.0.1
1:blenderplayer-2.71-3.fc22.i686 requires libOpenCOLLADABaseUtils.so.0.1
1:blenderplayer-2.71-3.fc22.i686 requires libMathMLSolver.so.0.1
1:blenderplayer-2.71-3.fc22.i686 requires libGeneratedSaxParser.so.0.1
[cab]
cab-0.1.9-12.fc22.i686 requires cabal-dev
[darcs]
darcs-2.8.4-5.fc22.i686 requires libHSterminfo-0.3.2.5-ghc7.6.3.so
darcs-2.8.4-5.fc22.i686 requires libHShaskeline-0.7.0.3-ghc7.6.3.so
darcs-2.8.4-5.fc22.i686 requires 
ghc(terminfo-0.3.2.5-61e0dc43a1465e327dacd9ab37bbe1a3)
darcs-2.8.4-5.fc22.i686 requires 
ghc(haskeline-0.7.0.3-775b029f16a4b58f3cc6b4cb4f7e7ac5)
ghc-darcs-2.8.4-5.fc22.i686 requires libHSterminfo-0.3.2.5-ghc7.6.3.so
ghc-darcs-2.8.4-5.fc22.i686 requires libHShaskeline-0.7.0.3-ghc7.6.3.so
ghc-darcs-2.8.4-5.fc22.i686 requires 
ghc(terminfo-0.3.2.5-61e0dc43a1465e327dacd9ab37bbe1a3)
ghc-darcs-2.8.4-5.fc22.i686 requires 
ghc(haskeline-0.7.0.3-775b029f16a4b58f3cc6b4cb4f7e7ac5)
ghc-darcs-devel-2.8.4-5.fc22.i686 requires 
ghc-devel(terminfo-0.3.2.5-61e0dc43a1465e327dacd9ab37bbe1a3)
ghc-darcs-devel-2.8.4-5.fc22.i686 requires 
ghc-devel(haskeline-0.7.0.3-775b029f16a4b58f3cc6b4cb4f7e7ac5)
[debconf]
debconf-1.5.53-1.fc22.noarch requires perl(:MODULE_COMPAT_5.18.2)
[deltacloud-core]
deltacloud-core-rackspace-1.1.3-1.fc20.noarch requires 
rubygem(cloudservers)
deltacloud-core-rackspace-1.1.3-1.fc20.noarch requires 
rubygem(cloudfiles)
[django-recaptcha]
django-recaptcha-0.1-7.20091212svn6.fc21.noarch requires python-django14
[dnssec-check]
dnssec-check-1.14.0.1-4.fc20.i686 requires libval-threads.so.14
dnssec-check-1.14.0.1-4.fc20.i686 requires libsres.so.14
[dragonegg]
dragonegg-3.4-0.3.rc0.fc21.i686 requires gcc = 0:4.8.2-14.fc21
[edelib]
edelib-2.1-5.fc22.i686 requires libedelib.so
edelib-devel-2.1-5.fc22.i686 requires libedelib.so
[engrid]
engrid-1.4.0-4.gite6d55f5.fc22.i686 requires libnglib.so.5
[eucalyptus]
eucalyptus-common-java-3.3.0-0.5.20130408git32052445.fc20.i686 requires 
hibernate3-jbosscache = 0:3.6.10-7
[fatrat]
1:fatrat-1.2.0-0.21.beta2.fc22.i686 requires libtorrent-rasterbar.so.7
[flush]
flush-0.9.12-10.fc22.i686 requires libtorrent-rasterbar.so.7
[gedit-valencia]
gedit-valencia-0.4.0-1.20131223git94442bf.fc21.i686 requires 
libvala-0.24.so.0
[ghc-hjsmin]
ghc-hjsmin-0.1.4.7-3.fc22.i686 requires 
libHSoptparse-applicative-0.9.0-ghc7.6.3.so
[gnome-python2-desktop]
gnome-python2-metacity-2.32.0-18.fc21.i686 requires 
libmetacity-private.so.0
[gofer]
ruby-gofer-0.77.1-2.fc21.noarch requires rubygem(qpid) = 0:0.16.0
[gorm]
gorm-1.2.18-5.fc20.i686 requires libgnustep-gui.so.0.23
[hledger]
ghc-hledger-0.19.3-5.fc22.i686 requires 
libHSterminfo-0.3.2.5-ghc7.6.3.so
ghc-hledger-0.19.3-5.fc22.i686 requires 
libHShaskeline-0.7.0.3-ghc7.6.3.so

Re: Dash as default shell

[Miloslav Trmač]

- Original Message -
 On 6 October 2014 17:28, Miloslav Trmač m...@redhat.com wrote:
  - Original Message -
   usage/requirement as well.  Bringing the benefits of supporting dash to…
   the satisfaction of pedantically using the POSIX /bin/sh path as
   frequently as possible?
 
  Also known as portability, compatibility
 
  Upstreams can be interested in cross-distro portability and compatibility.
  I don’t see much benefit for Fedora and Fedora’s users.
 
 
 Fedora is never upstream? Ever?

The cases where Fedora is both a distribution and upstream happen, but in these 
cases the difference doesn’t matter.  It’s the other cases, where the roles are 
separate, that allow us to judge where the benefit, effort and policy should be 
allocated.

  and transparency.
 
  Perhaps for changing the #! line; adding yet another programming language
  to the OS would make it more complex and thus _reduce_ transparency.
 
 Not another programming language, one that is already being used.

If they have so different features and syntax that people writing scripts need 
to be aware of this, they are different languages.  Or to put it the other way, 
if they were the same languages then assumption that /bin/sh is bash couldn’t 
matter.

  Do we
  encourage people to turn compiler warnings off?
 
  No, but most compiler warnings are useful _for increasing quality
  noticeable to users of Fedora_.  A warning about use of a bash construct
  when we are using bash doesn’t help us help users.
 
 Getting dependencies right isn't helpful?

That’s what I said, and I think I said why.  If you think that changing 
dependencies, when it would change neither behavior nor on-disk contents is 
helpful, could you explain how?


 Lastly:
 http://en.wikipedia.org/wiki/Open_Build_Service
 Even the scripts that you might think are solely Fedora specific could
 be useful to other people.
Good for the scripts.  I suggest this should be handled it in the scripts’ 
upstreams and not Fedora’s packaging of them.
Mirek
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: btrfs as default filesystem for F22?

[Gene Czarcinski]

On 10/07/2014 11:04 AM, Gerald B. Cox wrote:


On Mon, Oct 6, 2014 at 12:37 PM, Gene Czarcinski 
gczarcin...@gmail.com mailto:gczarcin...@gmail.com wrote:


However, there are some things that could be done to make it
easier for those of us who want to make it easier to install
Fedora onto a btrfs filesystem.

My point was that unless and until there is more support for BTRFS
by members of the Fedora Project, btrfs cannot be made the
default.  That is, *IF* it makes sense to have it be the default.


That is a good point.  I've been using BTRFS Raid 6 across 6 1TB 
drives for over a year now with (knock on wood) no issues.  I did this 
because of the simplicity of setting up RAID under BTRFS and for me at 
least that is the biggest attraction.  Maybe I'm mistaken, but there 
almost seemed (and still is, IMO) an active discouragement for people 
to use this configuration.  You're not going to attract people to use 
and test something if you simultaneously tell them it is toxic.  Also, 
you can't jump from don't use it, it isn't safe to ok, let's make it 
the system default.


I also use raid (d=raid0, m=raid1) and it is nice to have a multidevice 
btrfs volume where you can add an additional device to the volume and 
also have btrfs shuffle the data to spread  it over all the devices.


Also, if there are bugs then they need to be discovered and fixed. They 
will not get discovered unless btrfs is used.  If the btrfs developers 
knew there are a bug, it would have been already fixed.


Gene

-- 
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: btrfs as default filesystem for F22?

[Josh Boyer]

On Wed, Oct 8, 2014 at 1:52 AM, Thorsten Leemhuis fed...@leemhuis.info wrote:
 Josh Boyer wrote on 07.10.2014 21:15:
 On Tue, Oct 7, 2014 at 2:24 PM, Josef Bacik jo...@toxicpanda.com wrote:
 [...]
 I think the point is somewhat valid though. To just keep repeating the
 mantra 'its not ready' is not going to make it any more ready. If suse
 can identify a stable subset of btrfs features and use it as their
 default file system with those restrictions, why can't we do the same ?
 The approach makes sense to me, at least...
 Because they still have the support staff for when users don't listen,
 Fedora doesn't.
 As an aside, I looked at their 3.16.2-1.1.gdcee397 kernel-source SRPM.
 I can't find any patches that limit btrfs usage.  I could totally be
 wrong, but if someone knows of a patch that limits the features please
 point me to it.

 Due to a coincidence I yesterday took a quick look myself and didn't
 spot anything. But in case you haven't looked further: I found one in
 the SLE-Kernels:

 http://kernel.opensuse.org/cgit/kernel-source/tree/patches.suse/btrfs--add-allow_unsupported-module-parameter.patch?h=SLE11-SP3
 http://kernel.opensuse.org/cgit/kernel-source/tree/patches.suse/btrfs--add-allow_unsupported-module-parameter.patch?h=SLE12

Yes, I found the same yesterday after doing some digging.  It's not in
OpenSuSE 13.2 though, so it seems they're just going with whatever
upstream provides there.

I'm not thrilled with adding that patch to Fedora at all.  It
accomplishes the goal, but it would break any existing user that is
using one of those btrfs features because the mount would fail.
Fedora would likely just have to taint and then ignore reports with
the taint set, which doesn't make for a great user experience either.
They get away with this in SLE12 because it's roughly the first time
btrfs is available in a supported fashion.  I suspect they hit the
same concerns in OpenSuSE that Fedora would though, which is why it
isn't there.

If someone was interested in the history of the patch in OpenSuSE and
wants to dig into it, that would be neat to read.

josh
-- 
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: btrfs as default filesystem for F22?

[Gene Czarcinski]

On 10/08/2014 02:28 AM, Thorsten Leemhuis wrote:

Thorsten Leemhuis wrote on 08.10.2014 07:52:

Josh Boyer wrote on 07.10.2014 21:15:

On Tue, Oct 7, 2014 at 2:24 PM, Josef Bacik jo...@toxicpanda.com wrote:
[…]

I think the point is somewhat valid though. To just keep repeating the
mantra 'its not ready' is not going to make it any more ready. If suse
can identify a stable subset of btrfs features and use it as their
default file system with those restrictions, why can't we do the same ?
The approach makes sense to me, at least...

Because they still have the support staff for when users don't listen,
Fedora doesn't.

As an aside, I looked at their 3.16.2-1.1.gdcee397 kernel-source SRPM.
I can't find any patches that limit btrfs usage.  I could totally be
wrong, but if someone knows of a patch that limits the features please
point me to it.

Due to a coincidence I yesterday took a quick look myself and didn't
spot anything. But in case you haven't looked further: I found one in
the SLE-Kernels:

http://kernel.opensuse.org/cgit/kernel-source/tree/patches.suse/btrfs--add-allow_unsupported-module-parameter.patch?h=SLE11-SP3
http://kernel.opensuse.org/cgit/kernel-source/tree/patches.suse/btrfs--add-allow_unsupported-module-parameter.patch?h=SLE12

BTW  TWIMC, their solution to problems like this
http://aseigo.blogspot.de/2014/09/btrfs-rebalancing.html (ran into this
myself yesterday) seems to be a package called btrfsmaintenance that was
introduced a few days ago. Quoting
http://article.gmane.org/gmane.linux.suse.opensuse.devel/59787/


From: David Sterba dsterba at suse.cz
Subject: Introduce btrfsmaintenance package to Factory
Newsgroups: gmane.linux.suse.opensuse.devel
Date: 2014-10-06 15:40:37 GMT (1 day, 14 hours and 40 minutes ago)

Hi,

let me introduce a new package that supplements the btrfs filesystem and aims
to automate a few maintenance tasks. This means the scrub, balance, trim or
defragmentation. The package comes from SLE12 where btrfs is going to be the
default filesystem as well.

Each of the tasks can be turned on/off and configured independently. The
default config values were selected to fit the default installation profile.

* scrub - go through all medatada/data and verify the checksums, default period
is one month

* balance - the balance command can do a lot of things, in general moves data
around in big chunks, here we use it to reclaim back the space of the
underused chunks so it can be allocated again according to current needs

The point is to prevent some corner cases where it's not possible to eg.
allocate new metadata chunks because the whole device space is reserved for all
the chunks, although the total space occupied is smaller and the allocation
should succeed.

* trim - run TRIM on the filesystem using the 'fstrim' utility, makes sense for
SSD devices.

* defrag - run defrag on configured directories. This is for convenience and
not necessary.

There's a separate defragmentation task that happens automatically and
defragments only the RPM database files in /var/lib/rpm. This is done via a
zypper plugin and the defrag pass triggers at the end of the installation.

This improves reading the RPM databases later, but the installation process
fragments the files very quickly so it's not likely to bring a significant
speedup here.

Cron takes care of periodic execution of the scripts, but they can be run any
time directly from /usr/share/btrfs/maintenance/, respecting the configured
values in /etc/sysconfig/btrfsmaintenance.

If the period is changed manually, the cron symlinks have to be refreshed, use
systemctl restart btrfsmaintenance-refresh (or the
rcbtrfsmaintenance-refresh shortcut). Changing the period via yast2 sysconfig
editor triggers the refresh automatically.

The project lives in obs://filesystems/btrfsmaintenance and I'm going to submit
it to Factory.

I'd like to ask volunteers to give it some testing.  Feedback is welcome.

Thanks,
David


The package in the opensuse obs:
https://build.opensuse.org/package/show/filesystems/btrfsmaintenance

Seems to mostly consist of shell scripts.

CU
knurd
The new btrfsmaintenance package looks like something that should be 
added to Fedora regardless of btrfs status ... again this is something 
that Fedora could do which would make things easy to use and promote 
knowledgeable use of BTRFS without making it default. It is the 
support/infrastruction packages that need more attention and the the 
btrfs-kernel or btrfs-progs themselves.


Gene
--
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: btrfs as default filesystem for F22?

[Thorsten Leemhuis]

On 08.10.2014 14:50, Josh Boyer wrote:
 On Wed, Oct 8, 2014 at 1:52 AM, Thorsten Leemhuis fed...@leemhuis.info 
 wrote:
 Josh Boyer wrote on 07.10.2014 21:15:
 On Tue, Oct 7, 2014 at 2:24 PM, Josef Bacik jo...@toxicpanda.com wrote:
 [...]
 http://kernel.opensuse.org/cgit/kernel-source/tree/patches.suse/btrfs--add-allow_unsupported-module-parameter.patch?h=SLE11-SP3
 http://kernel.opensuse.org/cgit/kernel-source/tree/patches.suse/btrfs--add-allow_unsupported-module-parameter.patch?h=SLE12
 [...] 
 I'm not thrilled with adding that patch to Fedora at all. 

Fully agreed.

 […] They get away with this in SLE12 because it's roughly the first time
 btrfs is available in a supported fashion. […]

Well, it's supported since SLE11SP2 already, which is more than two
years old, but the point in the end is the same, yes. But FWIW, it seems
that simply how they work afaics, as they do something similar to ext4, too:

http://kernel.opensuse.org/cgit/kernel-source/tree/patches.suse/ext4-unsupported-features.patch?h=SLE12

CU
knurd
-- 
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: Possible PPC kernel bug on builders

[Stephen John Smoogen]

On 8 October 2014 00:36, Dan Horák d...@danny.cz wrote:

 On Tue, 7 Oct 2014 16:27:52 -0600
 Jerry James loganje...@gmail.com wrote:

  On Mon, Oct 6, 2014 at 2:36 PM, Jerry James loganje...@gmail.com
  wrote:
   I posted about this 5 days ago on ppc list [1], but have had no
   response.  I tried to get some attention on #fedora-ppc today, also
   with no success.  I am failing miserably to get the attention of any
   of the PPC folks, so I am trying email here to see if this will
   work.
 
  Still nothing.  Can anybody help me get the attention of somebody on
  the PPC team?

 we know about it, don't have any answer yet :-(


Then at least say:

We are aware of this, but don't have a solution yet.

Leaving people hanging only makes it worse.



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




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

Schedule for Wednesday's FESCo Meeting (2014-10-08)

[Josh Boyer]

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

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

or run:
  date -d '2014-10-08 17:00 UTC'


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

= Followups =

#topic Fedora 22 scheduling strategy (and beyond)
.fesco 1349
https://fedorahosted.org/fesco/ticket/1349

#topic Consider renaming Change(s) freeze and Beta
deadline/accepted changes 100% complete points
.fesco 1351
https://fedorahosted.org/fesco/ticket/1351

= New business =

#topic FPC is not working
.fesco 1346
https://fedorahosted.org/fesco/ticket/1346

#topic Bash scripts should rely on bash explicitly
.fesco 1352
https://fedorahosted.org/fesco/ticket/1352

#topic deprecate fedora-release file
.fesco 1354
https://fedorahosted.org/fesco/ticket/1354

= Open Floor =

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

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

Re: Schedule for Wednesday's FESCo Meeting (2014-10-08)

[Matthew Miller]

On Wed, Oct 08, 2014 at 10:36:39AM -0400, Josh Boyer wrote:
 #topic Fedora 22 scheduling strategy (and beyond)
 .fesco 1349
 https://fedorahosted.org/fesco/ticket/1349

We spent a lot of time on this at the last meeting, and then I suggested we
continue in the ticket and then... that didn't happen. Could we move this to
the end of the agenda and continue on it if we have time after the other
stuff?


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

Re: Schedule for Wednesday's FESCo Meeting (2014-10-08)

[Josh Boyer]

On Wed, Oct 8, 2014 at 10:41 AM, Matthew Miller
mat...@fedoraproject.org wrote:
 On Wed, Oct 08, 2014 at 10:36:39AM -0400, Josh Boyer wrote:
 #topic Fedora 22 scheduling strategy (and beyond)
 .fesco 1349
 https://fedorahosted.org/fesco/ticket/1349

 We spent a lot of time on this at the last meeting, and then I suggested we
 continue in the ticket and then... that didn't happen. Could we move this to
 the end of the agenda and continue on it if we have time after the other
 stuff?

I was going to point that out in the meeting as well.  I'd rather
strike it entirely because we clearly haven't put more thought into it
so we aren't going to be productive in a live setting.

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

Re: Schedule for Wednesday's FESCo Meeting (2014-10-08)

[Matthew Miller]

On Wed, Oct 08, 2014 at 10:46:55AM -0400, Josh Boyer wrote:
 I was going to point that out in the meeting as well.  I'd rather
 strike it entirely because we clearly haven't put more thought into it
 so we aren't going to be productive in a live setting.

Agreed.

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

Re: Dash as default shell

[Gerald B. Cox]

My thought is this whole topic was started as a result of the recent Bash
vulnerability which has since been corrected.  Not bad for a product that
has been around for decades.  Nothing against Dash, but changing a default
isn't something that should be done each time the wind changes direction.
A bit of disk space savings or processing time IMO isn't a sufficient
reason either. That can change quite rapidly between products and their
updates.  When a default is chosen it sets up an expectation of familiarity
and stability within the user community.  It shouldn't be changed unless
there is an EXTREMELY compelling reason.  I've seen quite a few posts
lately regarding the changing of this default or that default.  I think
what gets lost in these conversations is what default status means.  People
are down in the weeds and can't see the forest for the trees.
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

[Test-Announce] Fedora 21 Beta Test Compose 2 (TC2) Available Now!

[Andre Robatino]

As per the Fedora 21 schedule [1], Fedora 21 Beta Test Compose 2 (TC2)
is now available for testing. Content information, including changes,
can be found at https://fedorahosted.org/rel-eng/ticket/6010#comment:2 .
Please see the following pages for download links (including delta ISOs)
and testing instructions. Normally dl.fedoraproject.org should provide
the fastest download, but download-ib01.fedoraproject.org is available
as a mirror (with an approximately 1 hour lag) in case of trouble. To
use it, just replace dl with download-ib01 in the download URL.

Installation:

https://fedoraproject.org/wiki/Test_Results:Current_Installation_Test

Base:

https://fedoraproject.org/wiki/Test_Results:Current_Base_Test

Workstation and Desktop:

https://fedoraproject.org/wiki/Test_Results:Current_Desktop_Test

Server:

https://fedoraproject.org/wiki/Test_Results:Current_Server_Test

Cloud:

https://fedoraproject.org/wiki/Test_Results:Current_Cloud_Test

Ideally, all Alpha and Beta priority test cases for each of these test
pages [2] should pass in order to meet the Beta Release Criteria [3].
Help is available on #fedora-qa on irc.freenode.net [4], or on the test
list [5].

Create Fedora 21 Beta test compose (TC) and release candidate (RC)
https://fedorahosted.org/rel-eng/ticket/6010

Current Blocker and Freeze Exception bugs:
http://qa.fedoraproject.org/blockerbugs/current

[1] http://fedorapeople.org/groups/schedule/f-21/f-21-quality-tasks.html
[2] https://fedoraproject.org/wiki/QA:Release_validation_test_plan
[3] https://fedoraproject.org/wiki/Fedora_21_Beta_Release_Criteria
[4] irc://irc.freenode.net/fedora-qa
[5] https://admin.fedoraproject.org/mailman/listinfo/test




signature.asc
Description: OpenPGP digital signature
___
test-announce mailing list
test-annou...@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/test-announce-- 
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: Idea: Ability to define dependencies between coprs (correctly)

[Tomas Hozza]

On 10/03/2014 08:24 AM, Bohuslav Kabrda wrote:
 - Original Message -
  Hi all,
 
  I have a proposal that would change how dependencies are defined in copr:
 
  Problem:
  Currently, copr allows to add a link to an arbitrary repo URL that is
  available for installing dependencies during building in copr. Using
  this dependent repo link we are able to build packages in coprA with
  dependencies in another coprB.
 
  However, when enabling only coprA and installing some packages from this
  copr, we can miss some packages from coprB, because those packages are
  not available since coprB is not enabled.
 
  Solution:
  We should be able to define dependency between coprs correctly. When
  creating coprA, we would add one or more depended coprs ('userB/coprB')
  instead of repo link. Then all packages from these coprs would be
  available during build, correct buildroots would be used (no need to
  specify variables $releasever and in addition, we would be able to
  provide correct (all) RPMs also when *installing* coprs.
 
  There are basically two ways how to implement this on the users' side:
  1) Simpler, preferred by Mirek, copr maintainer (CC'd):
  'copr' plugin in dnf would include -r option, which would basically
  installed all related coprs. That means when running `dnf copr enable -r
  userA/coprA`, user would end with two coprs enabled: userA/coprA and
  userB/coprB.
 
  2) More complicated, preferred by me :) :
  copr A repository from example above would not only include RPMs build
  as part of this copr, but would include also packages from copr B. That
  means that when running `dnf copr enable userA/coprA`, user would not
  need to install userB/coprB repository and would have all packages
  available.

 3) (And I think that I've already heard this idea from someone) I think it'd 
 be better to:
 - Put the copr repofiles into RPMs and put all these RPMs in a single repo.
 - These repofile RPMs can depend on each other.
 - dnf copr enable installs an RPM from this repo.
 - When a dependency between repos change, repofile RPMs will be updated. When 
 user runs dnf update, he will get the new repofile RPM build, which will 
 have dependencies changed properly - so dnf will install these, too.

  Both ways struggle with refreshing data:
  * in 1) we might need to refresh coprs enabled (on the users' side)
  * in 2) we would need to re-create repodata in depended coprA if coprB

 I think that 3) is ok from this POV. The problem here can be, that in 3), dnf 
 would on update technically enable other copr repos without explicit user 
 approval. I'm not sure whether this is a problem or not, though.
Well, dnf/yum should show you what will be installed/enabled as dependencies, 
so the user is kind of informed what extra repos will be installed and enabled.

  gets changed (on the server's side).
 
  Let's discuss this a bit, I'm eager to hear your opinions.
 
  Cheers,
  Honza

-- 
Tomas Hozza
Software Engineer - EMEA ENG Developer Experience

PGP: 1D9F3C2D
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

Summary/Minutes from today's FESCo Meeting (2014-10-08)

[Josh Boyer]

===
#fedora-meeting: FESCO (2014-10-08)
===


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



Meeting summary
---
* init process  (jwb, 17:00:12)

* Consider renaming Change(s) freeze and Beta  (jwb, 17:02:33)
  * LINK: https://fedorahosted.org/fesco/ticket/1351   (jwb, 17:02:41)
  * FESCo pats adamw on the back. Attaboy!  (sgallagh, 17:09:56)

* FPC is not working  (jwb, 17:11:43)
  * LINK: https://fedorahosted.org/fesco/ticket/1346   (jwb, 17:11:44)
  * AGREED: jreznik to open discussion on devel@ (+1: 7 0:0 -1:0)  (jwb,
17:33:55)
  * ACTION: jreznik to open discussion on devel@  (jwb, 17:34:05)

* Bash scripts should rely on bash explicitly  (jwb, 17:34:13)
  * LINK: https://fedorahosted.org/fesco/ticket/1352   (jwb, 17:34:14)
  * AGREED: Ask Rahul to work with upstreams to resolve this issue
rather than patching it downstream (+1: 7 0:0 -1:0)  (jwb, 17:42:26)
  * a list of packages with checkbashisms failures can be kept outside
of bugzilla to facilitate the upstream effort  (jwb, 17:42:59)
  * if fedora packages are the upstream, it's okay to file bugs
(mattdm, 17:44:05)

* deprecate fedora-release file  (jwb, 17:45:23)
  * LINK: https://fedorahosted.org/fesco/ticket/1354   (jwb, 17:45:24)
  * LINK: http://0pointer.de/blog/projects/os-release.html   (jwb,
17:51:18)

* Next week's chair  (jwb, 18:06:01)
  * ACTION: nirik to chair next week  (jwb, 18:08:37)

* Open Floor  (jwb, 18:08:47)

Meeting ended at 18:23:35 UTC.




Action Items

* jreznik to open discussion on devel@
* nirik to chair next week




Action Items, by person
---
* jreznik
  * jreznik to open discussion on devel@
* nirik
  * nirik to chair next week
* **UNASSIGNED**
  * (none)




People Present (lines said)
---
* jwb (150)
* nirik (83)
* mattdm (60)
* mitr (55)
* kalev (44)
* t8m (39)
* sgallagh (20)
* thozza (17)
* adamw (12)
* jreznik (12)
* zodbot (10)
* randomuser (2)
* mclasen (2)
* spot (1)
* mmaslano (0)
* dgilmore (0)




Generated by `MeetBot`_ 0.1.4

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

rpm 4.12 and weak dependencies

[Kevin Fenzi]

Greetings. 

This F21 change: 
http://fedoraproject.org//wiki/Changes/RPM-4.12

has brought us 'weak dependencies', namely: 

Recommends, Suggests, Supplements and Enhances

Rpm in f21 and rawhide sees these in spec files and builds fine with
them. createrepo in those branches also exports this into the metadata. 

yum however doesn't do anything with that information. 
dnf does (although it's not clear to me what exactly it does do, so
input from dnf maintainers would be great). 

There's 4 packages that are already using these weak deps, but our
default package manager (yum) doesn't understand them. People
installing via yum and installing via dnf will see different behavior. 

I filed a fesco ticket to ask that we ask maintainers to please not add
these until we have guidelines and our default package manager supports
this information:  https://fedorahosted.org/fesco/ticket/1353

FESCo asked me to post here and see what folks think.

Should we just ask folks not to use these for now (honor system). 

Should we add a check to redhat-rpm-macros to check packages and fail
the build if they use these tags (for now). 

Should we just not care that people will see different behavior and
leave it up to maintainers?

Or should we do something else?

Additionally, if we decide to not allow them for now, is anyone wanting
to work on a guidelines draft / document for when to use them? It would
depend on how dnf treats them I suspect. 

Thanks, 

kevin


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

Re: rpm 4.12 and weak dependencies

[Haïkel]

2014-10-08 20:31 GMT+02:00 Kevin Fenzi ke...@scrye.com:
 Greetings.

 This F21 change:
 http://fedoraproject.org//wiki/Changes/RPM-4.12

 has brought us 'weak dependencies', namely:

 Recommends, Suggests, Supplements and Enhances

 Rpm in f21 and rawhide sees these in spec files and builds fine with
 them. createrepo in those branches also exports this into the metadata.

 yum however doesn't do anything with that information.
 dnf does (although it's not clear to me what exactly it does do, so
 input from dnf maintainers would be great).

 There's 4 packages that are already using these weak deps, but our
 default package manager (yum) doesn't understand them. People
 installing via yum and installing via dnf will see different behavior.

 I filed a fesco ticket to ask that we ask maintainers to please not add
 these until we have guidelines and our default package manager supports
 this information:  https://fedorahosted.org/fesco/ticket/1353

 FESCo asked me to post here and see what folks think.

 Should we just ask folks not to use these for now (honor system).

 Should we add a check to redhat-rpm-macros to check packages and fail
 the build if they use these tags (for now).

 Should we just not care that people will see different behavior and
 leave it up to maintainers?

 Or should we do something else?


Since our default package manager does not understand them, it's
harmless to leave it up to the maintainers.
Most importantly, we need to update packaging guidelines to explain
what are the semantic differences between these different tags. But
that's a minor update.

Before dnf gets promoted as the default package manager, it would be
interesting to do some widespread testing.

1. document dnf behavior with weak dependencies and related
configuration options
2. let people experiment and provide feedbacks
3. based on feedbacks either propose guidelines or status quo if that's ok

Regards,
H.

 Additionally, if we decide to not allow them for now, is anyone wanting
 to work on a guidelines draft / document for when to use them? It would
 depend on how dnf treats them I suspect.

 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: Summary/Minutes from today's FESCo Meeting (2014-10-08)

[Rahul Sundaram]

Hi

On Wed, Oct 8, 2014 at 2:25 PM, Josh Boyer wrote:

 * Bash scripts should rely on bash explicitly  (jwb, 17:34:13)
   * LINK: https://fedorahosted.org/fesco/ticket/1352   (jwb, 17:34:14)
   * AGREED: Ask Rahul to work with upstreams to resolve this issue
 rather than patching it downstream (+1: 7 0:0 -1:0)  (jwb, 17:42:26)


Well, what I do with upstreams as an individual is not within FESCo's
purview and this message also appears to assume that downstream patches
would be needed.  If no coordination can be done within Fedora, that is
effectively a rejection of the proposal which is fine.  Just wanted to be
clear on that.

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

Re: Summary/Minutes from today's FESCo Meeting (2014-10-08)

[Matthew Miller]

On Wed, Oct 08, 2014 at 08:18:22PM -0400, Rahul Sundaram wrote:
 Well, what I do with upstreams as an individual is not within FESCo's
 purview and this message also appears to assume that downstream patches
 would be needed.  If no coordination can be done within Fedora, that is
 effectively a rejection of the proposal which is fine.  Just wanted to be
 clear on that.

See the transcript. I don't think there's any problem with coordinating it
in Fedora in some way, but we don't want that to be a way that puts a burden
on Fedora packagers unless they're interested. If you're interested in
having a Fedora page which tracks affected upstreams, that'd be fine.


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

Re: Summary/Minutes from today's FESCo Meeting (2014-10-08)

[Rahul Sundaram]

Hi

On Wed, Oct 8, 2014 at 10:12 PM, Matthew Miller  wrote:

 See the transcript. I don't think there's any problem with coordinating it
 in Fedora in some way, but we don't want that to be a way that puts a
 burden
 on Fedora packagers unless they're interested. If you're interested in
 having a Fedora page which tracks affected upstreams, that'd be fine


Wiki page is going to be a pain to maintain manually.  How about using
bugzilla to track the issues?  Using proven packager rights to fix the
issues?  I will also volunteer to send any patches upstream.

One of the issues I highlighted in the ticket which apparently wasn't
discussed is

https://fedoraproject.org/wiki/Packaging:ScriptletSnippets#Default_Shell

It is unclear to me whether FESCo considers this guideline something that
can be changed.   To reiterate,  the fundamental question that was placed
before FESCo is whether you consider a derivative or user wanting to change
/bin/sh to point to something else other than /bin/bash worth supporting or
not?

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

Re: Summary/Minutes from today's FESCo Meeting (2014-10-08)

[Matthew Miller]

On Wed, Oct 08, 2014 at 10:29:32PM -0400, Rahul Sundaram wrote:
 Wiki page is going to be a pain to maintain manually.  How about using
 bugzilla to track the issues?  Using proven packager rights to fix the
 issues?  I will also volunteer to send any patches upstream.

Well, specifically, we didn't want to use bugzilla. I'm not sure I'm
speaking for everyone, but I think that's because it's not really the best
place for minor upstream issues. (We agreed that bugzilla makes sense for
cases where the script in question is only carried in the package or a
Fedora-specific patch -- we _are_ the upstream.)

We also discussed being okay with a plan to use proven packager rights to
fix the issues, but I'd be concerned with accidentally introducing new bugs,
so I'd like that to be a team of people who really care about this and will
double-check each others' work. If there _are_ a team of such people, then I
don't think we'll get in the way.

 It is unclear to me whether FESCo considers this guideline something that
 can be changed.   To reiterate,  the fundamental question that was placed
 before FESCo is whether you consider a derivative or user wanting to change
 /bin/sh to point to something else other than /bin/bash worth supporting or
 not?

I think it's worth... not really getting in the way of, but it seems pretty
clear that we don't want an effort to do that to impose any additional cost
on packagers. There are plenty of other things to worry about.

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

Re: Summary/Minutes from today's FESCo Meeting (2014-10-08)

[Rahul Sundaram]

Hi

On Wed, Oct 8, 2014 at 10:36 PM, Matthew Miller wrote:


 Well, specifically, we didn't want to use bugzilla. I'm not sure I'm
 speaking for everyone, but I think that's because it's not really the best
 place for minor upstream issues.


Using a wiki to track bugs is obviously not ideal.  Any change can be
tracked in bugzilla.  We track upstream issues in Fedora bugzilla all the
time.  Maintainers can either fix it if they are interested or let a proven
packager do it for them.  Don't see how this is much of a burden.


 We also discussed being okay with a plan to use proven packager rights to
 fix the issues, but I'd be concerned with accidentally introducing new
 bugs,
 so I'd like that to be a team of people who really care about this and will
 double-check each others' work. If there _are_ a team of such people, then
 I
 don't think we'll get in the way.


Fair enough.  So I guess the question is, is anyone else interested?  If
so, please speak up and let me know here or offlist.  If OTOH, noone else
is, that by itself would suggest this isn't a idea worth pursuing and I
will drop it.  Thanks!


 I think it's worth... not really getting in the way of, but it seems pretty
 clear that we don't want an effort to do that to impose any additional cost
 on packagers. There are plenty of other things to worry about.


There always is.

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

Unresponsive maintainer -- Iain Arnell

[Ruediger Landmann]

Hi all --

Does anybody know how Iain's doing? I needed some of his packages 
updated a few weeks ago and had no response, so opened bugs to request 
responses.[0] In the meantime, other folks have stepped in to update 
these packages, so the immediate problem is solved (albeit after many 
weeks) but in case I need updates on these again in the future, I'd like 
to at least co-maintain them.


I haven't heard anything from Iain at all since I opened the initial 
bugs on 6 August.


Cheers
Rudi



[0] https://bugzilla.redhat.com/show_bug.cgi?id=1142584 
https://bugzilla.redhat.com/show_bug.cgi?id=1142586



--
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 -- Iain Arnell

[Ralf Corsepius]

On 10/09/2014 06:29 AM, Ruediger Landmann wrote:

Hi all --

Does anybody know how Iain's doing?
No. Last time, I've heard something from him, he mentioned to have 
switched jobs, to have moved and not to have much time for Fedora 
anymore and to welcome co-maintainers.



I needed some of his packages
updated a few weeks ago and had no response, so opened bugs to request
responses.[0] In the meantime, other folks have stepped in to update
these packages, so the immediate problem is solved (albeit after many
weeks)

That's because much of perl is maintained collaboratively ;)

Ralf

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

Non-responsive package maintainer (affix)

[Brandon Vincent]

All,

Over the past month, I have tried contacting Keiran Smith (affix) in
regards to nagios with no success [1].

Is anyone aware to his present status in regards to the Fedora Project
or possibly have an alternative method to reach him?

[1] https://bugzilla.redhat.com/show_bug.cgi?id=1145830

Thank you,

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

File bugzilla-4.4.6.tar.gz uploaded to lookaside cache by eseyman

[Emmanuel Seyman]

A file has been added to the lookaside cache for bugzilla:

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

[bugzilla] Update to 4.4.6

[Emmanuel Seyman]

commit 44aee18ab38465743144acae1161f1e08d66f08e
Author: Emmanuel Seyman emman...@seyman.fr
Date:   Wed Oct 8 08:07:08 2014 +0200

Update to 4.4.6

 .gitignore|1 +
 bugzilla.spec |5 -
 sources   |2 +-
 3 files changed, 6 insertions(+), 2 deletions(-)
---
diff --git a/.gitignore b/.gitignore
index 9f42168..1f2d404 100644
--- a/.gitignore
+++ b/.gitignore
@@ -20,3 +20,4 @@ bugzilla-3.6.1.tar.gz
 /bugzilla-4.2.9.tar.gz
 /bugzilla-4.4.4.tar.gz
 /bugzilla-4.4.5.tar.gz
+/bugzilla-4.4.6.tar.gz
diff --git a/bugzilla.spec b/bugzilla.spec
index 63119ef..1d0d3b8 100644
--- a/bugzilla.spec
+++ b/bugzilla.spec
@@ -4,7 +4,7 @@
 Summary: Bug tracking system
 URL: http://www.bugzilla.org/
 Name: bugzilla
-Version: 4.4.5
+Version: 4.4.6
 Group: Applications/Publishing
 Release: 1%{?dist}
 License: MPLv1.1
@@ -224,6 +224,9 @@ popd  /dev/null)
 %{bzinstallprefix}/bugzilla/contrib/Bugzilla.pm
 
 %changelog
+* Wed Oct 08 2014 Emmanuel Seyman emman...@seyman.fr - 4.4.6-1
+- Update to 4.4.6
+
 * Fri Jul 25 2014 Emmanuel Seyman emman...@seyman.fr - 4.4.5-1
 - Update to 4.4.5
 
diff --git a/sources b/sources
index 47f4042..b71ddb2 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-077c123ea9659ccbf76bb35ce951324b  bugzilla-4.4.5.tar.gz
+3e0553c67cbe33f8ae12dfe79a02ecdc  bugzilla-4.4.6.tar.gz
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel

[PkgDB] jplesnik:perl-Log-Log4perl watchcommits set to Approved

[pkgdb]

user: jplesnik set for jplesnik acl: watchcommits of package: perl-Log-Log4perl 
from: Approved to: Approved on branch: el6

To make changes to this package see:
https://admin.fedoraproject.org/pkgdb/package/perl-Log-Log4perl
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel

[bugzilla/f21] Update to 4.4.6

[Emmanuel Seyman]

commit edaa528eadeb31b82cf7c7c364a42e21eecd0798
Author: Emmanuel Seyman emman...@seyman.fr
Date:   Wed Oct 8 08:07:08 2014 +0200

Update to 4.4.6

 .gitignore|1 +
 bugzilla.spec |5 -
 sources   |2 +-
 3 files changed, 6 insertions(+), 2 deletions(-)
---
diff --git a/.gitignore b/.gitignore
index 9f42168..1f2d404 100644
--- a/.gitignore
+++ b/.gitignore
@@ -20,3 +20,4 @@ bugzilla-3.6.1.tar.gz
 /bugzilla-4.2.9.tar.gz
 /bugzilla-4.4.4.tar.gz
 /bugzilla-4.4.5.tar.gz
+/bugzilla-4.4.6.tar.gz
diff --git a/bugzilla.spec b/bugzilla.spec
index 2495563..f37e0ee 100644
--- a/bugzilla.spec
+++ b/bugzilla.spec
@@ -4,7 +4,7 @@
 Summary: Bug tracking system
 URL: http://www.bugzilla.org/
 Name: bugzilla
-Version: 4.4.5
+Version: 4.4.6
 Group: Applications/Publishing
 Release: 1%{?dist}
 License: MPLv1.1
@@ -224,6 +224,9 @@ popd  /dev/null)
 %{bzinstallprefix}/bugzilla/contrib/Bugzilla.pm
 
 %changelog
+* Wed Oct 08 2014 Emmanuel Seyman emman...@seyman.fr - 4.4.6-1
+- Update to 4.4.6
+
 * Fri Jul 25 2014 Emmanuel Seyman emman...@seyman.fr - 4.4.5-1
 - Update to 4.4.5 which fixes a security bug (CVE-2014-1546)
 
diff --git a/sources b/sources
index 47f4042..b71ddb2 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-077c123ea9659ccbf76bb35ce951324b  bugzilla-4.4.5.tar.gz
+3e0553c67cbe33f8ae12dfe79a02ecdc  bugzilla-4.4.6.tar.gz
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel

[PkgDB] jplesnik:perl-Log-Log4perl commit set to Approved

[pkgdb]

user: jplesnik set for jplesnik acl: commit of package: perl-Log-Log4perl from: 
Obsolete to: Approved on branch: el6

To make changes to this package see:
https://admin.fedoraproject.org/pkgdb/package/perl-Log-Log4perl
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel

[PkgDB] jplesnik:perl-Log-Log4perl set point of contact to: jplesnik

[pkgdb]

user: jplesnik changed point of contact of package: perl-Log-Log4perl from: 
orphan to: jplesnik on branch: el6

To make changes to this package see:
https://admin.fedoraproject.org/pkgdb/package/perl-Log-Log4perl
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel

[PkgDB] jplesnik:perl-Log-Log4perl watchbugzilla set to Approved

[pkgdb]

user: jplesnik set for jplesnik acl: watchbugzilla of package: 
perl-Log-Log4perl from: Approved to: Approved on branch: el6

To make changes to this package see:
https://admin.fedoraproject.org/pkgdb/package/perl-Log-Log4perl
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel

[PkgDB] jplesnik:perl-Log-Log4perl set point of contact to: jplesnik

[pkgdb]

user: jplesnik changed point of contact of package: perl-Log-Log4perl from: 
orphan to: jplesnik on branch: epel7

To make changes to this package see:
https://admin.fedoraproject.org/pkgdb/package/perl-Log-Log4perl
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel

[PkgDB] jplesnik:perl-Log-Log4perl approveacls set to Approved

[pkgdb]

user: jplesnik set for jplesnik acl: approveacls of package: perl-Log-Log4perl 
from: Approved to: Approved on branch: el6

To make changes to this package see:
https://admin.fedoraproject.org/pkgdb/package/perl-Log-Log4perl
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel

[PkgDB] jplesnik:perl-Log-Log4perl approveacls set to Approved

[pkgdb]

user: jplesnik set for jplesnik acl: approveacls of package: perl-Log-Log4perl 
from: Approved to: Approved on branch: epel7

To make changes to this package see:
https://admin.fedoraproject.org/pkgdb/package/perl-Log-Log4perl
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel

[PkgDB] jplesnik:perl-Log-Log4perl commit set to Approved

[pkgdb]

user: jplesnik set for jplesnik acl: commit of package: perl-Log-Log4perl from: 
Obsolete to: Approved on branch: epel7

To make changes to this package see:
https://admin.fedoraproject.org/pkgdb/package/perl-Log-Log4perl
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel

[PkgDB] jplesnik:perl-Log-Log4perl watchbugzilla set to Approved

[pkgdb]

user: jplesnik set for jplesnik acl: watchbugzilla of package: 
perl-Log-Log4perl from: Approved to: Approved on branch: epel7

To make changes to this package see:
https://admin.fedoraproject.org/pkgdb/package/perl-Log-Log4perl
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel

[PkgDB] jplesnik:perl-Marpa-XS watchbugzilla set to Approved

[pkgdb]

user: jplesnik set for jplesnik acl: watchbugzilla of package: perl-Marpa-XS 
from: Approved to: Approved on branch: el6

To make changes to this package see:
https://admin.fedoraproject.org/pkgdb/package/perl-Marpa-XS
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel

[PkgDB] jplesnik:perl-Marpa-XS commit set to Approved

[pkgdb]

user: jplesnik set for jplesnik acl: commit of package: perl-Marpa-XS from: 
Approved to: Approved on branch: el6

To make changes to this package see:
https://admin.fedoraproject.org/pkgdb/package/perl-Marpa-XS
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel

[PkgDB] jplesnik:perl-Marpa-XS set point of contact to: jplesnik

[pkgdb]

user: jplesnik changed point of contact of package: perl-Marpa-XS from: orphan 
to: jplesnik on branch: el6

To make changes to this package see:
https://admin.fedoraproject.org/pkgdb/package/perl-Marpa-XS
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel

[PkgDB] jplesnik:perl-Marpa-XS commit set to Approved

[pkgdb]

user: jplesnik set for jplesnik acl: commit of package: perl-Marpa-XS from: 
Approved to: Approved on branch: epel7

To make changes to this package see:
https://admin.fedoraproject.org/pkgdb/package/perl-Marpa-XS
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel

[PkgDB] jplesnik:perl-Marpa-XS approveacls set to Approved

[pkgdb]

user: jplesnik set for jplesnik acl: approveacls of package: perl-Marpa-XS 
from: Approved to: Approved on branch: el6

To make changes to this package see:
https://admin.fedoraproject.org/pkgdb/package/perl-Marpa-XS
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel

[PkgDB] jplesnik:perl-Marpa-XS approveacls set to Approved

[pkgdb]

user: jplesnik set for jplesnik acl: approveacls of package: perl-Marpa-XS 
from: Approved to: Approved on branch: epel7

To make changes to this package see:
https://admin.fedoraproject.org/pkgdb/package/perl-Marpa-XS
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel

[PkgDB] jplesnik:perl-Marpa-XS watchcommits set to Approved

[pkgdb]

user: jplesnik set for jplesnik acl: watchcommits of package: perl-Marpa-XS 
from: Approved to: Approved on branch: el6

To make changes to this package see:
https://admin.fedoraproject.org/pkgdb/package/perl-Marpa-XS
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel

[PkgDB] jplesnik:perl-Marpa-XS set point of contact to: jplesnik

[pkgdb]

user: jplesnik changed point of contact of package: perl-Marpa-XS from: orphan 
to: jplesnik on branch: epel7

To make changes to this package see:
https://admin.fedoraproject.org/pkgdb/package/perl-Marpa-XS
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel

[PkgDB] jplesnik:perl-Marpa-XS watchbugzilla set to Approved

[pkgdb]

user: jplesnik set for jplesnik acl: watchbugzilla of package: perl-Marpa-XS 
from: Approved to: Approved on branch: epel7

To make changes to this package see:
https://admin.fedoraproject.org/pkgdb/package/perl-Marpa-XS
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel

[PkgDB] jplesnik:perl-Marpa-XS watchcommits set to Approved

[pkgdb]

user: jplesnik set for jplesnik acl: watchcommits of package: perl-Marpa-XS 
from: Approved to: Approved on branch: epel7

To make changes to this package see:
https://admin.fedoraproject.org/pkgdb/package/perl-Marpa-XS
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel

[PkgDB] jplesnik:perl-RPM2 commit set to Approved

[pkgdb]

user: jplesnik set for jplesnik acl: commit of package: perl-RPM2 from: 
Approved to: Approved on branch: epel7

To make changes to this package see:
https://admin.fedoraproject.org/pkgdb/package/perl-RPM2
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel

[PkgDB] jplesnik:perl-RPM2 set point of contact to: jplesnik

[pkgdb]

user: jplesnik changed point of contact of package: perl-RPM2 from: orphan to: 
jplesnik on branch: el5

To make changes to this package see:
https://admin.fedoraproject.org/pkgdb/package/perl-RPM2
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel

[PkgDB] jplesnik:perl-RPM2 commit set to Approved

[pkgdb]

user: jplesnik set for jplesnik acl: commit of package: perl-RPM2 from: 
Approved to: Approved on branch: el5

To make changes to this package see:
https://admin.fedoraproject.org/pkgdb/package/perl-RPM2
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel

[PkgDB] jplesnik:perl-RPM2 commit set to Approved

[pkgdb]

user: jplesnik set for jplesnik acl: commit of package: perl-RPM2 from: 
Approved to: Approved on branch: el6

To make changes to this package see:
https://admin.fedoraproject.org/pkgdb/package/perl-RPM2
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel

[PkgDB] jplesnik:perl-RPM2 watchbugzilla set to Approved

[pkgdb]

user: jplesnik set for jplesnik acl: watchbugzilla of package: perl-RPM2 from: 
Approved to: Approved on branch: el5

To make changes to this package see:
https://admin.fedoraproject.org/pkgdb/package/perl-RPM2
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel

[PkgDB] jplesnik:perl-RPM2 approveacls set to Approved

[pkgdb]

user: jplesnik set for jplesnik acl: approveacls of package: perl-RPM2 from: 
Approved to: Approved on branch: epel7

To make changes to this package see:
https://admin.fedoraproject.org/pkgdb/package/perl-RPM2
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel

[PkgDB] jplesnik:perl-RPM2 watchcommits set to Approved

[pkgdb]

user: jplesnik set for jplesnik acl: watchcommits of package: perl-RPM2 from: 
Approved to: Approved on branch: epel7

To make changes to this package see:
https://admin.fedoraproject.org/pkgdb/package/perl-RPM2
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel

[PkgDB] jplesnik:perl-RPM2 watchbugzilla set to Approved

[pkgdb]

user: jplesnik set for jplesnik acl: watchbugzilla of package: perl-RPM2 from: 
Approved to: Approved on branch: epel7

To make changes to this package see:
https://admin.fedoraproject.org/pkgdb/package/perl-RPM2
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel

[PkgDB] jplesnik:perl-RPM2 set point of contact to: jplesnik

[pkgdb]

user: jplesnik changed point of contact of package: perl-RPM2 from: orphan to: 
jplesnik on branch: el6

To make changes to this package see:
https://admin.fedoraproject.org/pkgdb/package/perl-RPM2
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel

[PkgDB] jplesnik:perl-RPM2 watchcommits set to Approved

[pkgdb]

user: jplesnik set for jplesnik acl: watchcommits of package: perl-RPM2 from: 
Approved to: Approved on branch: el6

To make changes to this package see:
https://admin.fedoraproject.org/pkgdb/package/perl-RPM2
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel

[PkgDB] jplesnik:perl-RPM2 approveacls set to Approved

[pkgdb]

user: jplesnik set for jplesnik acl: approveacls of package: perl-RPM2 from: 
Approved to: Approved on branch: el6

To make changes to this package see:
https://admin.fedoraproject.org/pkgdb/package/perl-RPM2
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel

[PkgDB] jplesnik:perl-RPM2 watchcommits set to Approved

[pkgdb]

user: jplesnik set for jplesnik acl: watchcommits of package: perl-RPM2 from: 
Approved to: Approved on branch: el5

To make changes to this package see:
https://admin.fedoraproject.org/pkgdb/package/perl-RPM2
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel

[PkgDB] jplesnik:perl-Syntax-Highlight-Engine-Kate approveacls set to Approved

[pkgdb]

user: jplesnik set for jplesnik acl: approveacls of package: 
perl-Syntax-Highlight-Engine-Kate from: Approved to: Approved on branch: el5

To make changes to this package see:
https://admin.fedoraproject.org/pkgdb/package/perl-Syntax-Highlight-Engine-Kate
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel

[PkgDB] jplesnik:perl-Syntax-Highlight-Engine-Kate commit set to Approved

[pkgdb]

user: jplesnik set for jplesnik acl: commit of package: 
perl-Syntax-Highlight-Engine-Kate from: Approved to: Approved on branch: el5

To make changes to this package see:
https://admin.fedoraproject.org/pkgdb/package/perl-Syntax-Highlight-Engine-Kate
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel

[PkgDB] jplesnik:perl-Syntax-Highlight-Engine-Kate watchbugzilla set to Approved

[pkgdb]

user: jplesnik set for jplesnik acl: watchbugzilla of package: 
perl-Syntax-Highlight-Engine-Kate from: Approved to: Approved on branch: el5

To make changes to this package see:
https://admin.fedoraproject.org/pkgdb/package/perl-Syntax-Highlight-Engine-Kate
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel

[PkgDB] jplesnik:perl-Syntax-Highlight-Engine-Kate approveacls set to Approved

[pkgdb]

user: jplesnik set for jplesnik acl: approveacls of package: 
perl-Syntax-Highlight-Engine-Kate from: Approved to: Approved on branch: el6

To make changes to this package see:
https://admin.fedoraproject.org/pkgdb/package/perl-Syntax-Highlight-Engine-Kate
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel

[PkgDB] jplesnik:perl-Syntax-Highlight-Engine-Kate watchcommits set to Approved

[pkgdb]

user: jplesnik set for jplesnik acl: watchcommits of package: 
perl-Syntax-Highlight-Engine-Kate from: Approved to: Approved on branch: el6

To make changes to this package see:
https://admin.fedoraproject.org/pkgdb/package/perl-Syntax-Highlight-Engine-Kate
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel

[PkgDB] jplesnik:perl-Syntax-Highlight-Engine-Kate watchbugzilla set to Approved

[pkgdb]

user: jplesnik set for jplesnik acl: watchbugzilla of package: 
perl-Syntax-Highlight-Engine-Kate from: Approved to: Approved on branch: el6

To make changes to this package see:
https://admin.fedoraproject.org/pkgdb/package/perl-Syntax-Highlight-Engine-Kate
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel

[PkgDB] jplesnik:perl-Syntax-Highlight-Engine-Kate set point of contact to: jplesnik

[pkgdb]

user: jplesnik changed point of contact of package: 
perl-Syntax-Highlight-Engine-Kate from: orphan to: jplesnik on branch: el5

To make changes to this package see:
https://admin.fedoraproject.org/pkgdb/package/perl-Syntax-Highlight-Engine-Kate
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel

[PkgDB] jplesnik:perl-Syntax-Highlight-Engine-Kate commit set to Approved

[pkgdb]

user: jplesnik set for jplesnik acl: commit of package: 
perl-Syntax-Highlight-Engine-Kate from: Approved to: Approved on branch: el6

To make changes to this package see:
https://admin.fedoraproject.org/pkgdb/package/perl-Syntax-Highlight-Engine-Kate
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel

[PkgDB] jplesnik:perl-Syntax-Highlight-Engine-Kate set point of contact to: jplesnik

[pkgdb]

user: jplesnik changed point of contact of package: 
perl-Syntax-Highlight-Engine-Kate from: orphan to: jplesnik on branch: el6

To make changes to this package see:
https://admin.fedoraproject.org/pkgdb/package/perl-Syntax-Highlight-Engine-Kate
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel

[PkgDB] jplesnik:perl-Class-Can watchcommits set to Approved

[pkgdb]

user: jplesnik set for jplesnik acl: watchcommits of package: perl-Class-Can 
from: Approved to: Approved on branch: el6

To make changes to this package see:
https://admin.fedoraproject.org/pkgdb/package/perl-Class-Can
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel

[PkgDB] jplesnik:perl-Class-Can watchbugzilla set to Approved

[pkgdb]

user: jplesnik set for jplesnik acl: watchbugzilla of package: perl-Class-Can 
from: Approved to: Approved on branch: el5

To make changes to this package see:
https://admin.fedoraproject.org/pkgdb/package/perl-Class-Can
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel

[PkgDB] jplesnik:perl-Class-Can approveacls set to Approved

[pkgdb]

user: jplesnik set for jplesnik acl: approveacls of package: perl-Class-Can 
from: Approved to: Approved on branch: el6

To make changes to this package see:
https://admin.fedoraproject.org/pkgdb/package/perl-Class-Can
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel

[PkgDB] jplesnik:perl-Class-Can set point of contact to: jplesnik

[pkgdb]

user: jplesnik changed point of contact of package: perl-Class-Can from: orphan 
to: jplesnik on branch: el5

To make changes to this package see:
https://admin.fedoraproject.org/pkgdb/package/perl-Class-Can
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel

[PkgDB] jplesnik:perl-Class-Can set point of contact to: jplesnik

[pkgdb]

user: jplesnik changed point of contact of package: perl-Class-Can from: orphan 
to: jplesnik on branch: el6

To make changes to this package see:
https://admin.fedoraproject.org/pkgdb/package/perl-Class-Can
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel

[PkgDB] jplesnik:perl-Class-Can commit set to Approved

[pkgdb]

user: jplesnik set for jplesnik acl: commit of package: perl-Class-Can from: 
Obsolete to: Approved on branch: el6

To make changes to this package see:
https://admin.fedoraproject.org/pkgdb/package/perl-Class-Can
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel

[PkgDB] jplesnik:perl-Class-Can watchcommits set to Approved

[pkgdb]

user: jplesnik set for jplesnik acl: watchcommits of package: perl-Class-Can 
from: Approved to: Approved on branch: el5

To make changes to this package see:
https://admin.fedoraproject.org/pkgdb/package/perl-Class-Can
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel

[PkgDB] jplesnik:perl-Class-Can watchbugzilla set to Approved

[pkgdb]

user: jplesnik set for jplesnik acl: watchbugzilla of package: perl-Class-Can 
from: Approved to: Approved on branch: el6

To make changes to this package see:
https://admin.fedoraproject.org/pkgdb/package/perl-Class-Can
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel

[PkgDB] jplesnik:perl-Class-Exporter approveacls set to Approved

[pkgdb]

user: jplesnik set for jplesnik acl: approveacls of package: 
perl-Class-Exporter from: Approved to: Approved on branch: el5

To make changes to this package see:
https://admin.fedoraproject.org/pkgdb/package/perl-Class-Exporter
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel

[PkgDB] jplesnik:perl-Class-Exporter commit set to Approved

[pkgdb]

user: jplesnik set for jplesnik acl: commit of package: perl-Class-Exporter 
from: Obsolete to: Approved on branch: el6

To make changes to this package see:
https://admin.fedoraproject.org/pkgdb/package/perl-Class-Exporter
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel

[PkgDB] jplesnik:perl-Class-Exporter set point of contact to: jplesnik

[pkgdb]

user: jplesnik changed point of contact of package: perl-Class-Exporter from: 
orphan to: jplesnik on branch: el6

To make changes to this package see:
https://admin.fedoraproject.org/pkgdb/package/perl-Class-Exporter
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel

[PkgDB] jplesnik:perl-Class-Exporter set point of contact to: jplesnik

[pkgdb]

user: jplesnik changed point of contact of package: perl-Class-Exporter from: 
orphan to: jplesnik on branch: el5

To make changes to this package see:
https://admin.fedoraproject.org/pkgdb/package/perl-Class-Exporter
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel

[PkgDB] jplesnik:perl-Class-Exporter watchbugzilla set to Approved

[pkgdb]

user: jplesnik set for jplesnik acl: watchbugzilla of package: 
perl-Class-Exporter from: Approved to: Approved on branch: el6

To make changes to this package see:
https://admin.fedoraproject.org/pkgdb/package/perl-Class-Exporter
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel

[PkgDB] jplesnik:perl-Class-Exporter watchbugzilla set to Approved

[pkgdb]

user: jplesnik set for jplesnik acl: watchbugzilla of package: 
perl-Class-Exporter from: Approved to: Approved on branch: el5

To make changes to this package see:
https://admin.fedoraproject.org/pkgdb/package/perl-Class-Exporter
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel

[PkgDB] jplesnik:perl-Class-Exporter approveacls set to Approved

[pkgdb]

user: jplesnik set for jplesnik acl: approveacls of package: 
perl-Class-Exporter from: Approved to: Approved on branch: el6

To make changes to this package see:
https://admin.fedoraproject.org/pkgdb/package/perl-Class-Exporter
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel