Hi Felix,
> xorg-x11-drv-sis seems to have disappeared. Did that happen on purpose? It
> still exists as a selelection in Bugzilla. Xorg is looking for sis module but
> cannot find it. Gfxchip here is Z7/Z9 (XG20 core). Is it now supposed to be
> using some other (not installed) driver? Before tod
Compose started at Wed Sep 24 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
[askbot]
askbot-0.7.48-13.fc21.noarch requires python-d
On 23/09/14 14:23, Stephen Gallagher wrote:
> Django 1.4 and 1.5 have been retired from the Fedora collection in
> Fedora 21 in favor of the two supported branches, 1.6 and 1.7.
>
Thank you Stephen,
I'm guilty to have missed to send this heads-up mail.
> On 09/23/2014 07:34 AM, Fedora Branched
Broken deps for i386
--
[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)
[askbot]
askbot-0.7.48-13.fc21.noa
I wanted to get some input before initiating the retirement process.
PVM upstream seems to be dead, version 3.4.6 was release in 2009.
Also, the entire build is pretty much non-compliant to the packaging
guidelines. The entire source is copied to the buildroot and compiled in
place.
Does anyone
On Wed, Sep 24, 2014 at 10:12:14AM +, Fedora Branched Report wrote:
> [cduce]
> cduce-0.5.5-9.fc21.armv7hl requires ocaml(Camlp4) =
> 0:ebd368022fd2bc7b305a42902efa4c90
> [ocaml-bisect]
> ocaml-bisect-1.3-3.fc21.armv7hl requires ocaml(Camlp4) =
> 0:ebd368022fd2bc7b305a42902efa4c90
Hi All,
Recently we came across a issue i.e. bz [1] , where ldconfig returned
error as below on Fedora 20 machine (same issue is present in other
Fedora variants too).
/"yum remove glusterfs-libs" giving some Non-fatal POSTUN scriptlet failure.
/sbin/ldconfig: relative path `0' used to build
Hello,
the “-p /sbin/ldconfig” syntax triggers a special behavior in RPM if the
scriptlet is otherwise empty . In your case, the “%post libs” scriptlet also
actually, surprising as it may seem, includes the following lines:
> ##--
On 09/24/2014 07:42 PM, Miloslav Trmač wrote:
Hello,
the “-p /sbin/ldconfig” syntax triggers a special behavior in RPM /if
the scriptlet is otherwise empty/. In your case, the “%post libs”
scriptlet also actually, surprising as it may seem, includes the
following lines:
##-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
There has been some discussion in various forums lately about how we
will handle fedup upgrades from Fedora 20 to Fedora 21 products.
Several suggestions have been made that warrant discussion:
* Upgrades from Fedora 20 remain non-productized. They
- Original Message -
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> There has been some discussion in various forums lately about how we
> will handle fedup upgrades from Fedora 20 to Fedora 21 products.
>
> Several suggestions have been made that warrant discussion:
>
> * Upgrad
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/24/2014 12:22 PM, Jaroslav Reznik wrote:
> - Original Message - There has been some discussion in
> various forums lately about how we will handle fedup upgrades from
> Fedora 20 to Fedora 21 products.
>
> Several suggestions have been m
On Wed, Sep 24, 2014 at 12:16:06PM -0400, Stephen Gallagher wrote:
> I think either the first option (easy) or the last option (requiring
> fedup changes) will be preferable. In the selectable case, I think
> that fedup should operate as a non-productized upgrade unless
> otherwise specified at the
On Tue, 2014-09-23 at 21:35 -0400, Felix Miata wrote:
> Adam Jackson wrote on 2014-09-23 12:45 (GMT-0400):
> > That's the fbdev X driver, pointed at either vesafb or uvesafb kernel
> > driver. Which I suppose will get you a high-res console, but isn't
> > especially great for mode selection in X.
Am 24.09.2014 um 18:16 schrieb Stephen Gallagher:
> There has been some discussion in various forums lately about how we
> will handle fedup upgrades from Fedora 20 to Fedora 21 products.
>
> Several suggestions have been made that warrant discussion:
>
> * Upgrades from Fedora 20 remain non-pr
Following is the list of topics that will be discussed in the FESCo meeting
Wednesday (today!) 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-09-24 17:00 UTC'
We only have on
Am 24.09.2014 um 18:22 schrieb Jaroslav Reznik:
>> Maybe we can go with first option and say, upgrades to products are not
>> supported, please reinstall. It's new beginning and say non-productized
>> update support will be gone in F22 timeframe and only productized updates
>> will be allowed
don
- Original Message -
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 09/24/2014 12:22 PM, Jaroslav Reznik wrote:
> > - Original Message - There has been some discussion in
> > various forums lately about how we will handle fedup upgrades from
> > Fedora 20 to Fedora 21 pro
Hi
On Wed, Sep 24, 2014 at 12:35 PM, Jaroslav Reznik wrote:
> Ah, you're right. On the other hand I think all spins are somehow
> desktop related (at least now), so moving spins to use workstation
> as the base is probably desirable
>
No. It is not. Workstation is GNOME based. Most spins are f
- Original Message -
> Hi
>
> On Wed, Sep 24, 2014 at 12:35 PM, Jaroslav Reznik wrote:
>
>
> Ah, you're right. On the other hand I think all spins are somehow
> desktop related (at least now), so moving spins to use workstation
> as the base is probably desirable
>
> No. It is not. Work
On 09/24/2014 06:16 PM, Stephen Gallagher wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> There has been some discussion in various forums lately about how we
> will handle fedup upgrades from Fedora 20 to Fedora 21 products.
>
> Several suggestions have been made that warrant discus
On 09/24/2014 11:28 AM, Kalev Lember wrote:
Fourth option might be to make all installations that have gnome-shell
installed become Workstation, and leave others non-productized.
This is hardly a guarantee. I have several servers that get a default Fedora
install and I don't bother removing X
On Wed, 24 Sep 2014 12:39:35 +0200
Matthias Runge wrote:
> On 23/09/14 14:23, Stephen Gallagher wrote:
> > Django 1.4 and 1.5 have been retired from the Fedora collection in
> > Fedora 21 in favor of the two supported branches, 1.6 and 1.7.
> >
>
> Thank you Stephen,
>
> I'm guilty to have mis
===
#fedora-meeting: FESCO (2014-09-24)
===
Meeting started by mattdm at 17:00:50 UTC. The full logs are available
at
http://meetbot.fedoraproject.org/fedora-meeting/2014-09-24/fesco.2014-09-24-17.00.log.html
.
Meeting summary
---
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, 24 Sep 2014 18:29:11 +0200
Reindl Harald wrote:
>
> Am 24.09.2014 um 18:16 schrieb Stephen Gallagher:
> > There has been some discussion in various forums lately about how we
> > will handle fedup upgrades from Fedora 20 to Fedora 21 product
Summary of changes:
8201039... Perl 5.20 rebuild (*)
a2f2ffe... Update to 1.10 (*)
ba7ae7c... Update to 1.11 (*)
dcf7207... Perl 5.20 rebuild (*)
fa5e58c... Perl 5.20 re-rebuild of bootstrapped packages (*)
19c5e98... Update to 1.12 (*)
(*) This commit already existed in another branc
Am 24.09.2014 um 19:12 schrieb Dennis Gilmore:
> I have updated a few machines by running "yum --releasever=21 install
> fedora-release" then "yum distro-sync" and not had any issues. As I
> understand this thread it is soley about what to do in the case of
> using fedup only. in which case we nee
Following is the list of topics that will be discussed in the FPC
meeting Thursday at 2014-09-25 16:00 UTC in #fedora-meeting-1 on
irc.freenode.net.
Local time information (via. rktime):
2014-09-25 09:00 Thu US/Pacific PDT
2014-09-25 12:00 Thu US/Eastern EDT
2014-09-25 1
On Wed, Sep 24, 2014 at 6:22 PM, Jaroslav Reznik wrote:
> - Original Message -
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> There has been some discussion in various forums lately about how we
>> will handle fedup upgrades from Fedora 20 to Fedora 21 products.
>>
>> Several su
On 24 September 2014 10:16, Stephen Gallagher wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> There has been some discussion in various forums lately about how we
> will handle fedup upgrades from Fedora 20 to Fedora 21 products.
>
> Several suggestions have been made that warrant di
On 09/23/2014 02:37 AM, Matthias Runge wrote:
On 22/09/14 17:18, Haïkel wrote:
Proposals are supposed to provide travel costs from pre-determined
airports at the *targeted* period.
If I trust informations from the proposals, SLC would be too expensive
to cover travel expenses for EMEA folks.
Hi,
I noticed that mulitple packages own /etc/bash_completion.d/ even though
it is nowadays part of the filesystem package. From what I read from the
Guidelines, it is not clear to me whether it is prohibited or not.
Should it be fixed? Here is a current list for Fedora 19:
repoquery --whatprovid
Hi, folks!
I'm currently like two months behind on devel@ - apologies if I've
missed anything relevant.
A discussion in #anaconda this morning made it clear that folks have
trouble following our full release cycle, and particularly the various
kinds of 'freeze' that exist.
So, there is a page na
On Wed, 24 Sep 2014 12:41:17 -0700
Adam Williamson wrote:
...snip...
> AFAICS, the "Branch freeze" kicks in at the point we enable Bodhi on
> the Branched tree, which is usually a couple of weeks after forking
> it from Rawhide. For instance, on the F21 schedule -
> https://fedoraproject.org/wik
On Wed, 24 Sep 2014 21:36:15 +0200, Till Maas wrote:
> Hi,
>
> I noticed that mulitple packages own /etc/bash_completion.d/ even though
> it is nowadays part of the filesystem package. From what I read from the
> Guidelines, it is not clear to me whether it is prohibited or not.
https://fedorapr
On Wed, 2014-09-24 at 14:46 -0600, Kevin Fenzi wrote:
> On Wed, 24 Sep 2014 12:41:17 -0700
> Adam Williamson wrote:
>
> ...snip...
>
> > AFAICS, the "Branch freeze" kicks in at the point we enable Bodhi on
> > the Branched tree, which is usually a couple of weeks after forking
> > it from Rawhid
On Wed, 24 Sep 2014 12:27:04 -0400
Matthew Miller wrote:
> On Wed, Sep 24, 2014 at 12:16:06PM -0400, Stephen Gallagher wrote:
> > I think either the first option (easy) or the last option (requiring
> > fedup changes) will be preferable. In the selectable case, I think
> > that fedup should opera
On Wed, 24 Sep 2014 14:02:41 -0700
Adam Williamson wrote:
> On Wed, 2014-09-24 at 14:46 -0600, Kevin Fenzi wrote:
> > On Wed, 24 Sep 2014 12:41:17 -0700
> > Adam Williamson wrote:
> >
> > ...snip...
> >
> > > AFAICS, the "Branch freeze" kicks in at the point we enable Bodhi
> > > on the Branch
On Wed, 24 Sep 2014 17:14:40 -0400
Simo Sorce wrote:
> On Wed, 24 Sep 2014 12:27:04 -0400
> Matthew Miller wrote:
>
> > On Wed, Sep 24, 2014 at 12:16:06PM -0400, Stephen Gallagher wrote:
> > > I think either the first option (easy) or the last option
> > > (requiring fedup changes) will be pref
On Wed, Sep 24, 2014 at 3:41 PM, Adam Williamson wrote:
> Hi, folks!
>
> I'm currently like two months behind on devel@ - apologies if I've
> missed anything relevant.
>
> A discussion in #anaconda this morning made it clear that folks have
> trouble following our full release cycle, and particul
On Wed, 24 Sep 2014 17:22:29 -0400
Christopher wrote:
> That page only describes policy, it doesn't really connect policy to
> actions one could take, or offer any explanation about what is
> actually "frozen", and is very confusing. What can a package owner do
> in git? What shouldn't they do? W
On Wed, 2014-09-24 at 17:22 -0400, Christopher wrote:
> >
> That page only describes policy, it doesn't really connect policy to
> actions one could take, or offer any explanation about what is actually
> "frozen", and is very confusing. What can a package owner do in git? What
> shouldn't they do?
On Wed, 24 Sep 2014 20:09:51 +0530, Lalatendu Mohanty wrote:
> On 09/24/2014 07:42 PM, Miloslav Trmač wrote:
> > Hello,
> > the “-p /sbin/ldconfig” syntax triggers a special behavior in RPM /if
> > the scriptlet is otherwise empty/. In your case, the “%post libs”
> > scriptlet also actually, su
On 24/09/14 19:54, Máirín Duffy wrote:
>> E.g. in June, flights to Boston are US$ 850 vs US$ 1400 in August. Maybe
>> it's a good idea to move the conference out of main holiday season?
>
> Are you located in EMEA or APAC? Because Flock alternates between North
> America and EMEA I think partially
On 24/09/14 19:01, Kevin Fenzi wrote:
> ...snip...
>
> Fedora Infrastructure only runs it on RHEL6 currently.
>
> I don't know off hand if it runs on newer django, but can take a look.
>
> It would be nice to get it running on rhel7/epel7.
>
> kevin
>
>
Kevin, I totally agree.
askbot ups
45 matches
Mail list logo
