Why opencv has experienced broken dependency at first step ?
I've miss the required announcement, and even if it was announced, it would
have be stroken by a denial from my side!
That kind of development is unappropriate in a stable release.
Nicolas (kwizart)
2010/3/1 Haïkel Guémar
> I submitt
Adam Williamson wrote:
> They can't expect anything currently either. We have no project-wide
> commitment to what kind of updates we will ship. Some maintainers ship
> version updates, some don't. There's already no consistency; this
> wouldn't make things any worse.
I'd argue it would, because h
I'll take a look of those patches day^_^
在2010-02-27?08:00:50，"Julian?Sikorski"??写道：
>Hi?Chen,
>
>I?tried?having?a?look,?but?I'm?not?sure?how?to?check?that?exactly.?I
>tried?diffing?the?sources?against?the?upstream?source,?but?it's?hard?for
>me?to?tell?anything.?The?diffs?are?attached.
>In?case?
Adam Williamson wrote:
> They can't expect anything currently either. We have no project-wide
> commitment to what kind of updates we will ship. Some maintainers ship
> version updates, some don't. There's already no consistency; this
> wouldn't make things any worse.
I'd argue it would, because h
Jesse Keating wrote:
> You can put free text in a bodhi comment without giving positive or
> negative karma. Seems we already have what you want to replace it with.
But his point (which I agree with, FWIW) is that those arbitrary numbers are
meaningless and thus it makes no sense to count them.
On Mon, 1 Mar 2010, Doug Ledford wrote:
>
> One could argue that the current bodhi karma system is simply too
> simplistic for real use cases. Maybe instead of just +1 -1, there
> should be:
>
> Fixes my problem
> Works for me (someone testing that didn't necessarily have any of the
> problem supp
Björn Persson wrote:
> That sounds really good, although I would call the second one "still works
> for me" to emphasize that it's for people for whom the previous release
> also worked.
Right.
Kevin Kofler
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.
Doug Ledford wrote:
> Fixes my problem
> Works for me (someone testing that didn't necessarily have any of the
> problem supposedly fixed by this update just noting that their system
> still works ok with the update)
> Doesn't fix my problem (but doesn't necessarily imply it's any worse
> than befo
Tom "spot" Callaway wrote:
> * Has ABI/API change (and is a Critical Path package)
Wrong criterion, sorry. "Has ABI/API change and fails to include rebuilds of
the affected packages" should be the criterion, critical path or not is
irrelevant. But this is basically covered by "causes broken deps
On Tue, 2 Mar 2010, Kevin Kofler wrote:
> Doug Ledford wrote:
>> Fixes my problem
>> Works for me (someone testing that didn't necessarily have any of the
>> problem supposedly fixed by this update just noting that their system
>> still works ok with the update)
>> Doesn't fix my problem (but does
James Antill wrote:
> So I did my proposal, which I think will motivate packagers to do the
> right thing (giving lots of choice to the users and a reasonable number
> of packages to test) and not removing the ability of packagers to do
> what they want (and have the stable firehose):
>
> https:/
Peter Jones wrote:
> This is the plan that already isn't working.
Is it really "not working"? Or are we overblowing a minor incident which
didn't even cause all that much trouble and trying to swallow a cure which
is worse than the disease? I think it's really the latter.
Kevin Kofler
Peter Jones wrote:
> When you're at the circus watching the clown ride a bicycle across a
> high-wire, he's got a safety net. It's not because the circus thinks he's
> an incompetent high-wire cyclist - it's because people occasionally make
> mistakes, and the circus would rather have him around to
Jesse Keating wrote:
> We do pushes daily,
No we don't. There are usually no pushes on weekends.
Kevin Kofler
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
James Antill wrote:
> It's still not really usable by normal users, but people on this list
> can install "yum-plugin-local" ... which will make sure you can do
> downgrades like this.
Isn't keepcache=yes sufficient? IMHO that should really be the default, I
really don't understand why we defaul
Adam Jackson wrote:
> If it's ready on Tuesday afternoon, what makes you think anyone's going
> to have time to read it thoroughly enough to be able to vote on it? Are
> you implying you're the only one on fesco that actually considers the
> proposal they're asked to vote on?
Considering that thi
Peter Jones wrote:
> Other corner cases where your case was wrong include new packages that
> Obsolete existing packages.
Nonsense. I wrote "new package which doesn't replace anything". Obsoletes =
replacing.
>> Even if you fix all the fixable problems, testing will still not be a
>> silver bull
I wrote:
> Isn't keepcache=yes sufficient?
Sorry, I mean keepcache=1.
Kevin Kofler
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Jesse Keating wrote:
> That's going to be pretty difficult to do with the way our push and sync
> scripts work.
>
> At most an update that is going from testing to stable should disappear
> for only a few hours, that would be between the updates-testing push of
> the day an the subsequent branched
LinkedIn
Henrique Castro requested to add you as a connection on LinkedIn:
--
Marco,
I'd like to add you to my professional network on LinkedIn.
- Henrique
Accept invitation from Henrique Castro
http://www.linkedin.com/e/XfpwrrIudepdoTBH97AF96
Till Maas wrote:
> Which files do you mean here? Afaik, cvs needs to know the CVSROOT and
> when I joined as a package maintainer, the wiki suggested to export the
> CVSROOT variable in .bashrc. It would be this one for you:
> export CVSROOT=:ext:tannhau...@cvs.fedoraproject.org:/cvs/pkgs
>
> But
On Tue, Mar 02, 2010 at 12:26:35 +0100,
Kevin Kofler wrote:
>
> We could have the branched compose compose from dist-f13 + dist-f13-updates
> and move everything which was part of its compose from dist-f13-updates to
> dist-f13 on completion. That way dist-f13-updates would only contain the
On Tue, 2010-03-02 at 11:22 +0100, Kevin Kofler wrote:
> James Antill wrote:
> > It's still not really usable by normal users, but people on this list
> > can install "yum-plugin-local" ... which will make sure you can do
> > downgrades like this.
>
> Isn't keepcache=yes sufficient? IMHO that sho
Compose started at Tue Mar 2 08:15:16 UTC 2010
Broken deps for i386
--
R-hdf5-1.6.9-6.fc13.i686 requires hdf5 = 0:1.8.4
blahtexml-0.6-5.fc12.i686 requires libxerces-c.so.28
easystroke-0.5.2-1.fc13.i686 requires libboo
On Tue, 2010-03-02 at 09:45 +0100, Kevin Kofler wrote:
> I didn't bring up the "fun" argument. My point is that banning direct stable
> pushes prevents us from fixing things for our users ASAP when needed. This
> is all part of duty, not fun.
And it prevents us from breaking things, with no war
On Tue, 2 Mar 2010, Kevin Kofler wrote:
> Tom "spot" Callaway wrote:
> > * Has ABI/API change (and is a Critical Path package)
>
> Wrong criterion, sorry. "Has ABI/API change and fails to include rebuilds of
> the affected packages" should be the criterion, critical path or not is
> irrelevant. Bu
On Tue, 2010-03-02 at 10:59 +0100, Kevin Kofler wrote:
> James Antill wrote:
> > So I did my proposal, which I think will motivate packagers to do the
> > right thing (giving lots of choice to the users and a reasonable number
> > of packages to test) and not removing the ability of packagers to d
On Tue, 2010-03-02 at 11:06 +0100, Kevin Kofler wrote:
> Peter Jones wrote:
> > This is the plan that already isn't working.
>
> Is it really "not working"? Or are we overblowing a minor incident which
> didn't even cause all that much trouble and trying to swallow a cure which
> is worse than t
A file has been added to the lookaside cache for perl-Locale-Maketext-Lexicon:
a880a00f4d10038498d6e0940476e69b Locale-Maketext-Lexicon-0.78.tar.gz
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-de...@lists.fedoraproject.org
https://admin
Author: corsepiu
Update of /cvs/pkgs/rpms/perl-Locale-Maketext-Lexicon/devel
In directory cvs1.fedora.phx.redhat.com:/tmp/cvs-serv6373/devel
Modified Files:
.cvsignore perl-Locale-Maketext-Lexicon.spec sources
Log Message:
* Tue Mar 02 2010 Ralf Corsépius - 0.78-1
- Upstream update.
Author: corsepiu
Update of /cvs/pkgs/rpms/perl-Locale-Maketext-Lexicon/F-11
In directory cvs1.fedora.phx.redhat.com:/tmp/cvs-serv6373/F-11
Modified Files:
.cvsignore perl-Locale-Maketext-Lexicon.spec sources
Log Message:
* Tue Mar 02 2010 Ralf Corsépius - 0.78-1
- Upstream update.
In
Author: corsepiu
Update of /cvs/pkgs/rpms/perl-Locale-Maketext-Lexicon/F-13
In directory cvs1.fedora.phx.redhat.com:/tmp/cvs-serv6373/F-13
Modified Files:
.cvsignore perl-Locale-Maketext-Lexicon.spec sources
Log Message:
* Tue Mar 02 2010 Ralf Corsépius - 0.78-1
- Upstream update.
In
Author: corsepiu
Update of /cvs/pkgs/rpms/perl-Locale-Maketext-Lexicon/F-12
In directory cvs1.fedora.phx.redhat.com:/tmp/cvs-serv6373/F-12
Modified Files:
.cvsignore perl-Locale-Maketext-Lexicon.spec sources
Log Message:
* Tue Mar 02 2010 Ralf Corsépius - 0.78-1
- Upstream update.
In
This is a report of the weekly KDE-SIG-Meeting with a summary of the
topics that were discussed. If you want to add a comment please reply
to this email or add it to the related meeting page.
--
= Weekly KDE Summary
James Antill writes:
> https://fedoraproject.org/wiki/Release_Lifecycle_Proposals#Choice_.28james.29
Regarding this, I don't understand this part:
> The idea behind this proposal is that a Fedora user installing a
> release N has a lot of choice if they wish to get newer packages:
>
> * The
+ missing bug ;-)
Wacom tablet does not work in Qt
* https://bugzilla.redhat.com/show_bug.cgi?id=569132
* wacom driver interface changed and broke Qt implementation
* than (with jreznik's help) is going to work on it
o LukasT offered his tablet to test it, KDE SIG lacks devi
Panu Matilainen writes:
> [...]
> Oh yes. Even just a big red REGRESSION button that stops the update from
> automatically entering stable no matter what the karma votes happen to be
> would be a definite improvement. [...]
Just for completeness, please let's be cautious about giving knobs to
On Tue, 2010-03-02 at 10:57 -0500, Frank Ch. Eigler wrote:
> James Antill writes:
>
> > https://fedoraproject.org/wiki/Release_Lifecycle_Proposals#Choice_.28james.29
>
> Regarding this, I don't understand this part:
>
> > The idea behind this proposal is that a Fedora user installing a
> > rele
On Tue, 2010-03-02 at 09:45 +0100, Kevin Kofler wrote:
> >> Yet, in practice, I still think a lot
> >> more stuff gets backported in our updates repository than in those
> >> backports repositories of other distros.
> >
> > Probably true (though in the case of Mandriva, maybe less than you'd
> >
On Tue, 2010-03-02 at 10:57 -0500, Frank Ch. Eigler wrote:
> Doesn't "just not running random/unrestricted yum update" exactly
> encode that option?
If you're happy to live with unsecure software, certainly =)
you can try and cherry-pick security updates, but then you get the
problem where initi
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=520401
Marcela Mašláňová changed:
What|Removed |Added
-
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=513596
Marcela Mašláňová changed:
What|Removed |Added
-
James Antill writes:
>> > [...]
>> > ...but they have almost no options if they are happy to stay with
>> > the software that they have.
>>
>> Doesn't "just not running random/unrestricted yum update" exactly
>> encode that option?
>
> No, for two reasons:
>
> 1. The user is often informed, fr
2010/3/2 Adam Williamson :
> On Tue, 2010-03-02 at 10:57 -0500, Frank Ch. Eigler wrote:
>
>> Doesn't "just not running random/unrestricted yum update" exactly
>> encode that option?
>
> If you're happy to live with unsecure software, certainly =)
>
> you can try and cherry-pick security updates, bu
On Tue, 2010-03-02 at 11:17 +0100, Kevin Kofler wrote:
> No we don't. There are usually no pushes on weekends.
That's a fair point, but there are significantly fewer people around to
fix critical issues should they arise on a weekend, and after working 5
weekdays, some of us like taking the weeken
On 03/02/2010 04:25 AM, Panu Matilainen wrote:
> On Tue, 2 Mar 2010, Kevin Kofler wrote:
>
>> Doug Ledford wrote:
>>> Fixes my problem
>>> Works for me (someone testing that didn't necessarily have any of the
>>> problem supposedly fixed by this update just noting that their system
>>> still works
On Tue, 2010-03-02 at 11:55 +0100, Kevin Kofler wrote:
> My argument is actually: "It doesn't matter how good our infrastructure for
> testing fixes is, it'll still not catch everything. Therefore, some
> regressions make it into stable anyway, and we want them to get fixed (in
> the stable upda
On Tue, 2 Mar 2010, Jesse Keating wrote:
> This is the problem with arguing about a proposal that hasn't even been
> written yet. You latch onto the one part you assume will be there that
> is the most unreasonable, and use that as a tool to bash the entire
> concept of the proposal (which hasn
On Tue, 2010-03-02 at 06:59 -0600, Bruno Wolff III wrote:
> probably could save some churn if the packages were signed with the
> same key. (I am not sure if that is true yet; though my understanding is
> that there will eventually be one key used to sign any official builds
> coming out of koji.)
On Tue, 2010-03-02 at 18:08 +0100, Thomas Moschny wrote:
> > you can try and cherry-pick security updates, but then you get the
> > problem where initial release has Foobar 1.0, then Foobar 3.5 gets
> > shipped in updates, then a security problem emerges and Foobar 3.5-2
> > with the security fix
On Tue, 2010-03-02 at 07:46 +0100, Kevin Kofler wrote:
> I just disagree with the claim that ALL updates are
> susceptible of breaking things.
Until such time that every update goes through without any breakage, I'm
going to keep on assuming that all updates are susceptible to breaking
things, a
So after having heard the nth discussion about tor, I decided to check it out.
I tried installing it on a stripped down f12 box that has no X, or other stuff
unnecessary for routing network packets.
What happened next has me lost for words.
Our dependency chains suck.
Dave
(12:24:07:r...
On Tue, 2010-03-02 at 12:08 -0500, Frank Ch. Eigler wrote:
> James Antill writes:
>
> >> > [...]
> >> > ...but they have almost no options if they are happy to stay with
> >> > the software that they have.
> >>
> >> Doesn't "just not running random/unrestricted yum update" exactly
> >> encode th
On Tue, 2010-03-02 at 12:37 -0500, Dave Jones wrote:
> --> Processing Dependency: tor-lsb = 0.2.1.23-1200.fc12 for package:
> tor-0.2.1.23-1200.fc12.i686
This is where things go to hell. Why in the hell is tor-lsb /required/
by tor? LSB isn't really good for anything except landing a bunch of
cr
On Tue, 2 Mar 2010, Jesse Keating wrote:
> On Tue, 2010-03-02 at 12:37 -0500, Dave Jones wrote:
>> --> Processing Dependency: tor-lsb = 0.2.1.23-1200.fc12 for package:
>> tor-0.2.1.23-1200.fc12.i686
>
> This is where things go to hell. Why in the hell is tor-lsb /required/
> by tor? LSB isn't
Jesse Keating wrote:
> On Tue, 2010-03-02 at 12:37 -0500, Dave Jones wrote:
>> --> Processing Dependency: tor-lsb = 0.2.1.23-1200.fc12 for package:
>> tor-0.2.1.23-1200.fc12.i686
>
> This is where things go to hell. Why in the hell is tor-lsb /required/
> by tor? LSB isn't really good for anythi
On Tue, 2010-03-02 at 12:37 -0500, Dave Jones wrote:
> So after having heard the nth discussion about tor, I decided to check it out.
> I tried installing it on a stripped down f12 box that has no X, or other stuff
> unnecessary for routing network packets.
>
> What happened next has me lost for w
On Tue, Mar 02, 2010 at 12:59:52PM -0500, Seth Vidal wrote:
> especially considering what it provides :(
> repoquery -ql tor-lsb
> /etc/rc.d/init.d/tor
> /var/run/tor
Check out the post/preun scripts:
%post lsb
/usr/lib/lsb/install_initd %_initrddir/tor || {
cat <&2
oouch
y
On Tue, 2 Mar 2010, David Malcolm wrote:
> On Tue, 2010-03-02 at 12:37 -0500, Dave Jones wrote:
>> So after having heard the nth discussion about tor, I decided to check it
>> out.
>> I tried installing it on a stripped down f12 box that has no X, or other
>> stuff
>> unnecessary for routing
Compose started at Tue Mar 2 09:15:13 UTC 2010
Broken deps for i386
--
anaconda-13.32-1.fc13.i686 requires python-urlgrabber >= 0:3.9.1-5
blahtexml-0.6-5.fc12.i686 requires libxerces-c.so.28
doodle-0.6.7-5.fc12.i686 r
Le mardi 02 mars 2010 à 09:51 -0800, Jesse Keating a écrit :
> On Tue, 2010-03-02 at 12:37 -0500, Dave Jones wrote:
> > --> Processing Dependency: tor-lsb = 0.2.1.23-1200.fc12 for package:
> > tor-0.2.1.23-1200.fc12.i686
>
> This is where things go to hell. Why in the hell is tor-lsb /required/
>
On Tue, Mar 02, 2010 at 01:06:25PM -0500, Seth Vidal wrote:
> but if it isn't, then tor-upstart requires tor which is going to require
> tor-lsb.
> yes - that's never going to end well.
https://bugzilla.redhat.com/show_bug.cgi?id=569933
--
Matthew Miller
Senior Systems Architect -- Instructio
On Tue, Mar 02, 2010 at 09:51:17AM -0800, Jesse Keating wrote:
> On Tue, 2010-03-02 at 12:37 -0500, Dave Jones wrote:
> > --> Processing Dependency: tor-lsb = 0.2.1.23-1200.fc12 for package:
> > tor-0.2.1.23-1200.fc12.i686
>
> This is where things go to hell. Why in the hell is tor-lsb /requ
On Tue, 2 Mar 2010, Dave Jones wrote:
> On Tue, Mar 02, 2010 at 09:51:17AM -0800, Jesse Keating wrote:
> > On Tue, 2010-03-02 at 12:37 -0500, Dave Jones wrote:
> > > --> Processing Dependency: tor-lsb = 0.2.1.23-1200.fc12 for package:
> > > tor-0.2.1.23-1200.fc12.i686
> >
> > This is where thing
Start End Name
Tue 16-Feb Tue 09-Mar Development: Alpha Freeze
Thu 18-Feb Thu 04-Mar Test Alpha Candidate
Wed 03-Mar Wed 03-Mar Alpha Go/No-Go Meeting #2 (20:00 EST)
Wed 03-Mar Fri 05-Mar Build F-13 collection packages for all language
translators
Thu 04-Mar Thu 04-Mar Star
On Tue, 2010-03-02 at 13:14 -0500, Dave Jones wrote:
> On Tue, Mar 02, 2010 at 09:51:17AM -0800, Jesse Keating wrote:
> > On Tue, 2010-03-02 at 12:37 -0500, Dave Jones wrote:
> > > --> Processing Dependency: tor-lsb = 0.2.1.23-1200.fc12 for package:
> > > tor-0.2.1.23-1200.fc12.i686
> >
> > T
Adam Williamson (awill...@redhat.com) said:
> > We should make a stand and drop it from Fedora until it's not made up of
> > bonghits and failure. (haha, yeah. thanks, here all week, etc)
>
> I'm not quite sure why it needs separate lsb/upstart init scripts
> anyway. Don't most of our packages j
On 03/02/2010 04:23 AM, Kevin Kofler wrote:
> Tom "spot" Callaway wrote:
>> * Has ABI/API change (and is a Critical Path package)
>
> Wrong criterion, sorry. "Has ABI/API change and fails to include rebuilds of
> the affected packages" should be the criterion, critical path or not is
> irrelevan
On Tue, 2010-03-02 at 13:25 -0500, Bill Nottingham wrote:
> Adam Williamson (awill...@redhat.com) said:
> > > We should make a stand and drop it from Fedora until it's not made up of
> > > bonghits and failure. (haha, yeah. thanks, here all week, etc)
> >
> > I'm not quite sure why it needs sepa
On Tue, 2 Mar 2010, Bill Nottingham wrote:
> Adam Williamson (awill...@redhat.com) said:
>>> We should make a stand and drop it from Fedora until it's not made up of
>>> bonghits and failure. (haha, yeah. thanks, here all week, etc)
>>
>> I'm not quite sure why it needs separate lsb/upstart init
On Tue, Mar 02, 2010 at 01:43:13PM -0500, Paul Wouters wrote:
> On Tue, 2 Mar 2010, Bill Nottingham wrote:
>
> > Adam Williamson (awill...@redhat.com) said:
> >>> We should make a stand and drop it from Fedora until it's not made up of
> >>> bonghits and failure. (haha, yeah. thanks, here al
Adam Williamson (awill...@redhat.com) said:
> > > I'm not quite sure why it needs separate lsb/upstart init scripts
> > > anyway. Don't most of our packages just include one initscript with both
> > > bits in the headers?
> >
> > No. A package could have either a SystemV init script or an upstart
Author: cweyl
Update of /cvs/extras/rpms/perl-Try-Tiny/F-13
In directory cvs1.fedora.phx.redhat.com:/tmp/cvs-serv3369
Modified Files:
perl-Try-Tiny.spec
Log Message:
* Tue Mar 02 2010 Chris Weyl 0.04-1
- update by Fedora::App::MaintainerTools 0.004
- PERL_INSTALL_ROOT => DESTDIR
- updat
Author: cweyl
Update of /cvs/extras/rpms/perl-Mouse/F-12
In directory cvs1.fedora.phx.redhat.com:/tmp/cvs-serv3969
Modified Files:
perl-Mouse.spec sources
Log Message:
* Sun Feb 28 2010 Chris Weyl 0.50-1
- update by Fedora::App::MaintainerTools 0.004
- PERL_INSTALL_ROOT => DESTDIR
In
On 03/02/2010 06:15 AM, Kevin Kofler wrote:
>>> X11 is particularly dangerous for this kind of changes, given how low it
>>> is in the software stack and how some code necessarily looks like
>>> (hardware drivers in particular are always scary stuff). The average leaf
>>> package is much less prop
Jesse Keating writes:
> On Tue, 2010-03-02 at 12:37 -0500, Dave Jones wrote:
>> --> Processing Dependency: tor-lsb = 0.2.1.23-1200.fc12 for package:
>> tor-0.2.1.23-1200.fc12.i686
>
> This is where things go to hell. Why in the hell is tor-lsb /required/
> by tor?
tor-lsb requires only lsb-co
On 03/02/2010 05:15 AM, Kevin Kofler wrote:
> Peter Jones wrote:
>> When you're at the circus watching the clown ride a bicycle across a
>> high-wire, he's got a safety net. It's not because the circus thinks he's
>> an incompetent high-wire cyclist - it's because people occasionally make
>> mistak
Dave Jones writes:
> (12:24:07:r...@firewall:~)# yum install tor
fwiw; when you can not wait for a fixed redhat-lsb package, do
| yum install tor tor-upstart
Upstart does not have a good way yet to disable/enable service so you
have to edit /etc/init/tor.conf resp. /etc/event.d/tor manually.
On Tue, 2 Mar 2010, Enrico Scholz wrote:
> Jesse Keating writes:
>
>> On Tue, 2010-03-02 at 12:37 -0500, Dave Jones wrote:
>>> --> Processing Dependency: tor-lsb = 0.2.1.23-1200.fc12 for package:
>>> tor-0.2.1.23-1200.fc12.i686
>>
>> This is where things go to hell. Why in the hell is tor-lsb
Enrico Scholz writes:
> | yum install tor tor-upstart
should be
| yum install tor-core tor-upstart
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Adam Williamson writes:
> I'm not quite sure why it needs separate lsb/upstart init scripts
> anyway.
All the initscripts have huge and broken dependency chains.
E.g. assuming I would use the vanilla fedora 'initscripts' package, then
tor would still require[1] syslog, cpio, e2fsprogs, ethtool,
On Tue, Mar 02, 2010 at 08:23:22PM +0100, Enrico Scholz wrote:
> Enrico Scholz writes:
>
> > | yum install tor tor-upstart
>
> should be
>
> | yum install tor-core tor-upstart
still no good, because tor-upstart requires tor which requires tor-lsb which...
Dave
--
devel mailin
On Tue, 2010-03-02 at 20:31 +0100, Enrico Scholz wrote:
> Adam Williamson writes:
>
> > I'm not quite sure why it needs separate lsb/upstart init scripts
> > anyway.
>
> All the initscripts have huge and broken dependency chains.
> E.g. assuming I would use the vanilla fedora 'initscripts' pack
Join us on irc.freenode.net #fedora-meeting for this important meeting.
This is Thursday, March 4, 2010 @ 01:00 UTC, which makes it *WEDNESDAY
EVENING* in North America: 20:00 EST, 17:00 PST.
"Before each public release Development, QA, and Release Engineering
meet to determine if the release cri
On 03/02/2010 07:48 PM, Dave Jones wrote:
> The tor package is at least fixable.
Over the dead body of the current package maintainer. That's the root of
the problem.
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Dave Jones writes:
> > | yum install tor-core tor-upstart
>
> still no good, because tor-upstart requires tor which requires tor-lsb
> which...
thx for noticing this; this requirement is broken and has been fixed
now. I did not noticed it myself because I use yet another instance of
'init(tor)
===
#fedora-meeting: FESCO (2010-03-02)
===
Meeting started by nirik at 20:00:00 UTC. The full logs are available at
http://meetbot.fedoraproject.org/fedora-meeting/2010-03-02/fesco.2010-03-02-20.00.log.html
Meeting summary
-
Enrico Scholz (enrico.sch...@informatik.tu-chemnitz.de) said:
> > I'm not quite sure why it needs separate lsb/upstart init scripts
> > anyway.
>
> All the initscripts have huge and broken dependency chains.
> E.g. assuming I would use the vanilla fedora 'initscripts' package, then
> tor would s
Bill Nottingham (nott...@redhat.com) said:
> > All the initscripts have huge and broken dependency chains.
> > E.g. assuming I would use the vanilla fedora 'initscripts' package, then
> > tor would still require[1] syslog, cpio, e2fsprogs, ethtool, mount, ...
> > although it does not log anything,
Bill Nottingham writes:
>> E.g. assuming I would use the vanilla fedora 'initscripts' package,
>> then tor would still require[1] syslog, cpio, e2fsprogs, ethtool,
>> mount, ... although it does not log anything, does not extract/pack
>> anything, does not format a filesystem, does not configure
Bill Nottingham wrote:
> Bill Nottingham (nott...@redhat.com) said:
>>> All the initscripts have huge and broken dependency chains.
>>> E.g. assuming I would use the vanilla fedora 'initscripts' package, then
>>> tor would still require[1] syslog, cpio, e2fsprogs, ethtool, mount, ...
>>> although
Eric Sandeen (sand...@redhat.com) said:
> I'm guessing e2fsprogs may have been sucked in due to the various tools it
> has (had) in its junkbox. Lots of those which are not ext2-specific (blkid
> for example) have been split out or moved to util-linux-ng.
Sort of.
...
* Mon Oct 05 1998 Cristian
On Tue, 2 Mar 2010, Bill Nottingham wrote:
> Enrico Scholz (enrico.sch...@informatik.tu-chemnitz.de) said:
>> All the initscripts have huge and broken dependency chains.
>> E.g. assuming I would use the vanilla fedora 'initscripts' package, then
>> tor would still require[1] syslog, cpio, e2fspro
On Tue, Mar 02, 2010 at 02:21:55PM -0500, Seth Vidal wrote:
>
>
> On Tue, 2 Mar 2010, Enrico Scholz wrote:
>
> > Jesse Keating writes:
> >
> >> On Tue, 2010-03-02 at 12:37 -0500, Dave Jones wrote:
> >>> --> Processing Dependency: tor-lsb = 0.2.1.23-1200.fc12 for package:
> >>> tor-0.2.1.23-1200
Paul Wouters writes:
>>> All the initscripts have huge and broken dependency chains.
>>> E.g. assuming I would use the vanilla fedora 'initscripts' package, then
>>> tor would still require[1] syslog, cpio, e2fsprogs, ethtool, mount, ...
>>> although it does not log anything, does not extract/pac
On Tue, 2 Mar 2010, Enrico Scholz wrote:
>> It does not log anything because Enrico broke logging in tor package.
>
> Not that this was the reason, but it is the upstream setup to have
> logging disabled. Your comment is unrelated to this discussion because
> logging can be done into a file and d
2010/2/28 Thomas Spura :
> Am Samstag, den 27.02.2010, 22:00 +0100 schrieb Michał Piotrowski:
>> W dniu 27 lutego 2010 21:51 użytkownik Michał Piotrowski
>> napisał:
>> > 2010/2/27 Toshio Kuratomi :
>> >> Could you please file a bug at bugzilla.redhat.com to make sure trhe
>> >> maintainer sees th
Frank Ch. Eigler wrote:
> OK, but then we're not talking about the person who's happy to stay
> with the software they have, but about a more typical person who is
> not too risk-averse and is willing to consider unsolicited updates.
> Those are different dudes.
The person who's not willing to do
James Antill wrote:
> ...but it has the same "problem". But IMNSHO this isn't a problem, you
> are arguing that people specifically hit by problem X can goto the
> updates-testing (or whatever it's called) repo. and get a fix for it.
> Anyone not affected doesn't have to risk that update breaking
Adam Williamson wrote:
> Oh, I see. You're inferring a cause where there's no reason to. I didn't
> realize that.
What other reasons do you consider then? Pure chance? Doesn't look very
likely to me. It's much more likely the reason Mandriva provides fewer new
versions is because of the split up
1 - 100 of 189 matches
Mail list logo
