Good Morning,
I don't see any intervention of the motu-council here.
You are talking about two different upstream projects,
falcon the language
and
falcon the whatever python script.
As it is in the real world, one comes up with a good name, and another
one comes up with the same name.
What
Fellow MOTU,
In recent weeks, I've noticed a fair number of REVU candidates
being uploaded to the repositories, without the NEW notification being
forwarded to this list. Unless there was agreement to stop doing that
of which I am unaware, I'd like to ask that uploaders resume
forwarding the
Hi,
On Mo, 2008-01-14 at 11:01 +0100, Giancarlo Niccolai wrote:
Stephan Hermann wrote:
Good Morning,
I don't see any intervention of the motu-council here.
You are talking about two different upstream projects,
snip
And I think this is your problem right now. Not a technical or
The next MOTU Meeting will be held in #ubuntu-meeting on Freenode
2008-1-18 12:00 UTC.
If you'd like to raise anything for discussion, please add an entry to
https://wiki.ubuntu.com/MOTU/Meetings
Attendance is open to all, for discussion of any items that impact the
MOTU Community.
--
Emmet
Stephan Hermann wrote:
Well, when you respect the ubuntu users or your users in general (ubuntu
is not that special) then you would solve the problem by yourself. e.G.
you rename all your binaries and libs from falcon to falconpl (this is
just an example of a simple solution ! ) and then you
Scott Kitterman wrote:
My suggestion is to call your package falconpl as you've said you would and
then conflict against falcon. After that, we can let the market decide. If
one of these packages gets popular enough to cause the other difficulty with
the conflicts, then the less popular
On Jan 14 January 2008 11:31 AM, Giancarlo Niccolai wrote:
Up to date, several MOTUs have checked and reported there is no
current namespace clash. I am also willing to call my package
falconpl, which is also the name of the site:
On Jan 14, 2008 1:42 PM, Scott Kitterman wrote:
My suggestion
On Mon, Jan 14, 2008 at 11:52:43AM +0100, Stephan Hermann wrote:
That's why I always tell upstream authors to never package their own
software, because they are not objective.
I think this is silly. The more familiar the maintainer is with upstream
the better, IMO. They need to realise that
Morten Kjeldgaard wrote:
Scott Kitterman wrote:
My suggestion is to call your package falconpl as you've said you would and
then conflict against falcon. After that, we can let the market decide. If
one of these packages gets popular enough to cause the other difficulty with
the
On Mo, 2008-01-14 at 14:39 +0100, Soren Hansen wrote:
IMO, the programming language should allowed to be /usr/bin/falcon.
Changing the name of the interpreter will mean that any program that is
supposed to be interpreted by falcon will need to be patched. OTOH,
renaming the binary in Dennis'
NEW: livemix_0.49~rc2.orig.tar.gz
NEW: livemix_0.49~rc2-0ubuntu1.diff.gz
NEW: livemix_0.49~rc2-0ubuntu1.dsc
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Sat, 22 Dec 2007 13:41:31 +0100
Source: livemix
Binary: livemix
Architecture: source
Version: 0.49~rc2-0ubuntu1
On Mo, 2008-01-14 at 14:39 +0100, Soren Hansen wrote:
On Mon, Jan 14, 2008 at 10:15:41PM +0900, Emmet Hikory wrote:
I don't have a strong opinion about which is the right falcon, but
such a Conflicts: would be wrong. Section 10.1 of the Debian Policy
Manual (1) clearly states, in part:
On Mon, Jan 14, 2008 at 05:17:49PM +0100, Stephan Hermann wrote:
IMO, the programming language should allowed to be /usr/bin/falcon.
Changing the name of the interpreter will mean that any program that
is supposed to be interpreted by falcon will need to be patched.
OTOH, renaming the
On Mon, Jan 14, 2008 at 05:12:15PM +0100, Stephan Hermann wrote:
That's why I always tell upstream authors to never package their own
software, because they are not objective.
I think this is silly. The more familiar the maintainer is with
upstream the better, IMO. They need to realise that
Hi motu,
is there a known problem with xslideshow on a plain 7.10 64Bit installation. I
am always getting SigServ Errors ...
would be patient for any hint on this,
Chris
--
Ubuntu-motu mailing list
Ubuntu-motu@lists.ubuntu.com
Modify settings or unsubscribe at:
Hello,
Have a look at https://launchpad.net/ubuntu/+source/xslideshow/+bugs
If you don't find a report about your problem, create one.
Gauvain
Christian aka Baumi wrote:
Hi motu,
is there a known problem with xslideshow on a plain 7.10 64Bit installation.
I am always getting SigServ
16 matches
Mail list logo
