Re: Feature Freeze and bug fix releases

[Stephan Hermann]

Good Morning,

Emilio Pozuelo Monfort wrote:
> Stephan Hermann wrote:
>> Hi,
>>
>> Emilio Pozuelo Monfort wrote:
>>> Stephan Hermann wrote:
 That's how I see it, too. If a new upstream fixes serious bugs, we
 should bring it in...(not forgetting the paperwork and an ack from
 motu-release)
>>> I think you misread his proposal. There's no need for an ACK from 
>>> motu-release
>>> if the new release is bug-fix only. That's why UpstreamVersionFreeze was 
>>> changed
>>> to FeatureFreeze, to allow bug-fix-only releases without needed the 
>>> paperwork.
>> No :)
>>  MOTU => new release fixes bug => upload
>>  NON-MOTU => new release fixes bug => needs paperwork => needs ack => 
>> upload
> 
> That would be an ack from a MOTU (an ack as in a "looks ok, let's upload"), 
> and
> not from motu-release as you said initially. But of course non-MOTUs need ACKs
> from MOTUs, but that's to do everything, as they can't do anything by 
> themselves :)

Yeah, but after sleeping over it, I think it's too easy, and I think
many people will spam us with new versions because they fix simple bugs,
but introducing new features.
I would like to see (and in the case I need to do something like this)
at least a bug report with the rational and some background why we did
it. Actually it's a 3 minute report, which wouldn't be a bad thing.


> What I wanted to say is that we shouldn't require paperwork for something 
> which
> was changed to avoid it (UVF -> FF) in case of bug-fixes-only releases.

Well, wine releases are bug-fixing-only releases with lots of features ;)

\sh

-- 
Ubuntu-motu mailing list
Ubuntu-motu@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu

Re: Feature Freeze and bug fix releases

[Emilio Pozuelo Monfort]

Stephan Hermann wrote:
> Hi,
> 
> Emilio Pozuelo Monfort wrote:
>> Stephan Hermann wrote:
>>> That's how I see it, too. If a new upstream fixes serious bugs, we
>>> should bring it in...(not forgetting the paperwork and an ack from
>>> motu-release)
>> I think you misread his proposal. There's no need for an ACK from 
>> motu-release
>> if the new release is bug-fix only. That's why UpstreamVersionFreeze was 
>> changed
>> to FeatureFreeze, to allow bug-fix-only releases without needed the 
>> paperwork.
> 
> No :)
>   MOTU => new release fixes bug => upload
>   NON-MOTU => new release fixes bug => needs paperwork => needs ack => 
> upload

That would be an ack from a MOTU (an ack as in a "looks ok, let's upload"), and
not from motu-release as you said initially. But of course non-MOTUs need ACKs
from MOTUs, but that's to do everything, as they can't do anything by 
themselves :)

Anyway I don't think non-MOTUs *need* (as in enforced by policy) to do
paperwork. Of course if they want to go through the SponsorsQueue they will do
it, but that's a different thing than Feature Freeze.

What I wanted to say is that we shouldn't require paperwork for something which
was changed to avoid it (UVF -> FF) in case of bug-fixes-only releases.

Cheers,
Emilio

> 
> 
> oh, s/upload/sync/
> 
> Regards,
> 
> \sh
> 




signature.asc
Description: OpenPGP digital signature
-- 
Ubuntu-motu mailing list
Ubuntu-motu@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu

Re: Feature Freeze and bug fix releases

[Stephan Hermann]

Hi,

Emilio Pozuelo Monfort wrote:
> Stephan Hermann wrote:
>> That's how I see it, too. If a new upstream fixes serious bugs, we
>> should bring it in...(not forgetting the paperwork and an ack from
>> motu-release)
> 
> I think you misread his proposal. There's no need for an ACK from motu-release
> if the new release is bug-fix only. That's why UpstreamVersionFreeze was 
> changed
> to FeatureFreeze, to allow bug-fix-only releases without needed the paperwork.

No :)
MOTU => new release fixes bug => upload
NON-MOTU => new release fixes bug => needs paperwork => needs ack => 
upload


oh, s/upload/sync/

Regards,

\sh

-- 
Ubuntu-motu mailing list
Ubuntu-motu@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu

Re: Feature Freeze and bug fix releases

[Luke Yelavich]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Fri, Feb 15, 2008 at 04:05:18AM EST, Scott Kitterman wrote:
> We no longer have upstream version freeze, we have feature freeze, so I 
> wonder 
> about upstream releases that just have bug fixes.  IIRC when the new freeze 
> structure was created there was some discussion about this.
> 
> Speaking for myself (not as part of motu-release, because we haven't 
> discussed 
> it), I think we generally want bug fix releases for a while.  Here is my 
> proposal:
> 
> Up through Alpha 6, if a MOTU believes upload of a new upstream release that 
> just has bug fixes in it is warranted, they may upload it.  File a bug in LP 
> with the upstream change log entries in it and mark it fix released when the 
> upload is done to document that it was bug fix only.  If you have doubts 
> about if something qualifies, check with a member of motu-release (or 
> subscribe motu-release to the bug) and if one person from motu-release agrees 
> it's a bug fix update, you're good for upload.
> 
> Comments?

I agree we need to have a discussion as a team, but this sounds sane to me.
- -- 
Luke Yelavich
GPG key: 0xD06320CE 
 (http://www.themuso.com/themuso-gpg-key.txt)
Email & MSN: [EMAIL PROTECTED]
Jabber: [EMAIL PROTECTED]
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFHtL5yjVefwtBjIM4RAr9wAJ45TKCqgG10ar08sibcx7WmmjSoDgCgkQv8
tpbgM00PuMkMilHxg2bSD6I=
=A4xV
-END PGP SIGNATURE-

-- 
Ubuntu-motu mailing list
Ubuntu-motu@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu

Re: Feature Freeze and bug fix releases

[Emilio Pozuelo Monfort]

Michael Bienia wrote:
> On 2008-02-14 22:11:29 +0100, Emilio Pozuelo Monfort wrote:
>> Another option I'm thinking which would be in the middle of having to do some
>> paperwork when it shouldn't be necessary and not thinking about it or not
>> checking it is to listen all the changes from upstream NEWS or ChangeLog (if 
>> the
>> list is reasonable) in debian/changelog. We already do that in the 
>> DesktopTeam
>> even if we don't have Freezes. Would that make sense?
> 
> That could only work when MOTUs package the bugfix release ahead of
> Debian. Perhaps also in merges. What do you propose in cases where the
> bugfix release is already in Debian unstable and only need syncing?
> 
> Michael
> 

In that case you need to report a bug in Launchpad anyway per the SyncRequest
policy, so an archive admin makes the sync. So simply put the changes in the
sync request.

Emilio



signature.asc
Description: OpenPGP digital signature
-- 
Ubuntu-motu mailing list
Ubuntu-motu@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu

Re: Feature Freeze and bug fix releases

[Michael Bienia]

On 2008-02-14 22:11:29 +0100, Emilio Pozuelo Monfort wrote:
> Another option I'm thinking which would be in the middle of having to do some
> paperwork when it shouldn't be necessary and not thinking about it or not
> checking it is to listen all the changes from upstream NEWS or ChangeLog (if 
> the
> list is reasonable) in debian/changelog. We already do that in the DesktopTeam
> even if we don't have Freezes. Would that make sense?

That could only work when MOTUs package the bugfix release ahead of
Debian. Perhaps also in merges. What do you propose in cases where the
bugfix release is already in Debian unstable and only need syncing?

Michael

-- 
Ubuntu-motu mailing list
Ubuntu-motu@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu

Re: Feature Freeze and bug fix releases

[Emilio Pozuelo Monfort]

Scott Kitterman wrote:
> On Thursday 14 February 2008 15:43, Michael Bienia wrote:
>> On 2008-02-14 12:05:18 -0500, Scott Kitterman wrote:
>>> Up through Alpha 6, if a MOTU believes upload of a new upstream release
>>> that just has bug fixes in it is warranted, they may upload it.  File a
>>> bug in LP with the upstream change log entries in it and mark it fix
>>> released when the upload is done to document that it was bug fix only.
>> What's the purpose of those bug filings? If it's for catching wrong
>> bugfix releases, then that's only works if someone regularly checks
>> those bugs and has time to raise a veto.
>>
>> Michael
> 
> My idea of the purpose is to ensure people take the time to think through 
> what 
> they are doing.  If you have to write it down in a bug (even if just 
> copy/paste) and put your name on it, you're more likely to have thought it 
> through.
> 
> Scott K
> 

Another option I'm thinking which would be in the middle of having to do some
paperwork when it shouldn't be necessary and not thinking about it or not
checking it is to listen all the changes from upstream NEWS or ChangeLog (if the
list is reasonable) in debian/changelog. We already do that in the DesktopTeam
even if we don't have Freezes. Would that make sense?

Emilio



signature.asc
Description: OpenPGP digital signature
-- 
Ubuntu-motu mailing list
Ubuntu-motu@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu

Re: Feature Freeze and bug fix releases

[Emilio Pozuelo Monfort]

Stephan Hermann wrote:
> That's how I see it, too. If a new upstream fixes serious bugs, we
> should bring it in...(not forgetting the paperwork and an ack from
> motu-release)

I think you misread his proposal. There's no need for an ACK from motu-release
if the new release is bug-fix only. That's why UpstreamVersionFreeze was changed
to FeatureFreeze, to allow bug-fix-only releases without needed the paperwork.

Cheers,
 Emilio



signature.asc
Description: OpenPGP digital signature
-- 
Ubuntu-motu mailing list
Ubuntu-motu@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu

Re: Feature Freeze and bug fix releases

[Scott Kitterman]

On Thursday 14 February 2008 15:43, Michael Bienia wrote:
> On 2008-02-14 12:05:18 -0500, Scott Kitterman wrote:
> > Up through Alpha 6, if a MOTU believes upload of a new upstream release
> > that just has bug fixes in it is warranted, they may upload it.  File a
> > bug in LP with the upstream change log entries in it and mark it fix
> > released when the upload is done to document that it was bug fix only.
>
> What's the purpose of those bug filings? If it's for catching wrong
> bugfix releases, then that's only works if someone regularly checks
> those bugs and has time to raise a veto.
>
> Michael

My idea of the purpose is to ensure people take the time to think through what 
they are doing.  If you have to write it down in a bug (even if just 
copy/paste) and put your name on it, you're more likely to have thought it 
through.

Scott K

-- 
Ubuntu-motu mailing list
Ubuntu-motu@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu

Re: Feature Freeze and bug fix releases

[Michael Bienia]

On 2008-02-14 12:05:18 -0500, Scott Kitterman wrote:
> Up through Alpha 6, if a MOTU believes upload of a new upstream release that 
> just has bug fixes in it is warranted, they may upload it.  File a bug in LP 
> with the upstream change log entries in it and mark it fix released when the 
> upload is done to document that it was bug fix only.

What's the purpose of those bug filings? If it's for catching wrong
bugfix releases, then that's only works if someone regularly checks
those bugs and has time to raise a veto.

Michael

-- 
Ubuntu-motu mailing list
Ubuntu-motu@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu

Re: Feature Freeze and bug fix releases

[Stefan Potyra]

Hi,

Am Donnerstag, 14. Februar 2008 18:05 schrieb Scott Kitterman:
> We no longer have upstream version freeze, we have feature freeze, so I
> wonder about upstream releases that just have bug fixes.  IIRC when the new
> freeze structure was created there was some discussion about this.
>
> Speaking for myself (not as part of motu-release, because we haven't
> discussed it), I think we generally want bug fix releases for a while. 
> Here is my proposal:
>
> Up through Alpha 6, if a MOTU believes upload of a new upstream release
> that just has bug fixes in it is warranted, they may upload it.  File a bug
> in LP with the upstream change log entries in it and mark it fix released
> when the upload is done to document that it was bug fix only.  If you have
> doubts about if something qualifies, check with a member of motu-release
> (or subscribe motu-release to the bug) and if one person from motu-release
> agrees it's a bug fix update, you're good for upload.
>
> Comments?

Excellent proposal! I'm all for it.

Cheers,
 Stefan.


pgpcqAv6PHSWl.pgp
Description: PGP signature
-- 
Ubuntu-motu mailing list
Ubuntu-motu@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu

REVU: New: ubuntume-themes 1.1 (source)

[Scott Kitterman]

Subject: New: ubuntume-themes 1.1 (source)
Date: Thursday 14 February 2008 12:40
From: Ubuntu Installer <[EMAIL PROTECTED]>
To: Scott Kitterman <[EMAIL PROTECTED]>

NEW: ubuntume-themes_1.1.tar.gz
NEW: ubuntume-themes_1.1.dsc

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Mon, 31 Oct 2007 21:35:50 +0200
Source: ubuntume-themes
Binary: ubuntume-themes
Architecture: source
Version: 1.1
Distribution: hardy
Urgency: low
Maintainer: Ubuntu Muslim Edition Team <[EMAIL PROTECTED]>
Changed-By: أحمد المحمودي (Ahmed El-Mahmoudy)
 <[EMAIL PROTECTED]> Description:
 ubuntume-themes - Ubuntu Muslim Edition themes
Launchpad-Bugs-Fixed: 185141
Changes:
 ubuntume-themes (1.1) hardy; urgency=low
 .
   * Initial release (LP: #185141).
Files:
 e6a76c68286e00dde8b6a19a1df078e2 641 x11 optional ubuntume-themes_1.1.dsc
 73fe9b7bbb111b068136b603688802b7 988124 x11 optional
 ubuntume-themes_1.1.tar.gz Original-Maintainer: أحمد المحمودي (Ahmed
 El-Mahmoudy) <[EMAIL PROTECTED]>

Your package contains new components which requires manual editing of
the override file.  It is ok otherwise, so please be patient.  New
packages are usually added to the overrides about once a week.

You may have gotten the distroseries wrong.  If so, you may get warnings
above if files already exist in other distroseries.

--
You are receiving this email because you are the uploader, maintainer or
signer of the above package.

---

-- 
Ubuntu-motu mailing list
Ubuntu-motu@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu

REVU: New: qdevelop 0.25.2-0ubuntu1 (source)

[Scott Kitterman]

Subject: New: qdevelop 0.25.2-0ubuntu1 (source)
Date: Thursday 14 February 2008 12:25
From: Ubuntu Installer <[EMAIL PROTECTED]>
To: Scott Kitterman <[EMAIL PROTECTED]>

NEW: qdevelop_0.25.2.orig.tar.gz
NEW: qdevelop_0.25.2-0ubuntu1.diff.gz
NEW: qdevelop_0.25.2-0ubuntu1.dsc

Format: 1.7
Date: Sun, 10 Feb 2008 14:00:24 +0100
Source: qdevelop
Binary: qdevelop
Architecture: source
Version: 0.25.2-0ubuntu1
Distribution: hardy
Urgency: low
Maintainer: Ubuntu MOTU Developers 
Changed-By: Guillaume Martres <[EMAIL PROTECTED]>
Description:
 qdevelop   - A development environment entirely dedicated to Qt4
Launchpad-Bugs-Fixed: 120739
Changes:
 qdevelop (0.25.2-0ubuntu1) hardy; urgency=low
 .
   * Initial release based on Daniel Rocher package (LP: #120739)
Files:
 c01f79fe45376ab31a70870cc2370902 676 devel optional
 qdevelop_0.25.2-0ubuntu1.dsc 48c6d7d32d1b75bd789dc19decbbcbf1 977529 devel
 optional qdevelop_0.25.2.orig.tar.gz 7c5073123abe18e643129c008efee7b0 7329
 devel optional qdevelop_0.25.2-0ubuntu1.diff.gz Original-Maintainer:
 Guillaume Martres <[EMAIL PROTECTED]>

Your package contains new components which requires manual editing of
the override file.  It is ok otherwise, so please be patient.  New
packages are usually added to the overrides about once a week.

You may have gotten the distroseries wrong.  If so, you may get warnings
above if files already exist in other distroseries.

--
You are receiving this email because you are the uploader, maintainer or
signer of the above package.

---

-- 
Ubuntu-motu mailing list
Ubuntu-motu@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu

Re: Feature Freeze and bug fix releases

[Emmet Hikory]

Scott Kitterman proposed:
>  Up through Alpha 6, if a MOTU believes upload of a new upstream release that
>  just has bug fixes in it is warranted, they may upload it.  File a bug in LP
>  with the upstream change log entries in it and mark it fix released when the
>  upload is done to document that it was bug fix only.  If you have doubts
>  about if something qualifies, check with a member of motu-release (or
>  subscribe motu-release to the bug) and if one person from motu-release agrees
>  it's a bug fix update, you're good for upload.

I'd like to see discussion of the motu-release freeze policy
internal to MOTU release and presented for review at the MOTU Meeting
this Friday, just to ensure that the entire team is comfortable with a
plan, rather than it being presented in advance (especially given that
the team as a slightly different role than has been granted for past
releases).

Aside from that, it sounds very sane, and certainly reduces the
overhead involved in tracking upstream (including Debian) bugfixes and
trying to get them all included in hardy.

-- 
Emmet HIKORY

-- 
Ubuntu-motu mailing list
Ubuntu-motu@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu

[REVU] New: php-xdebug 2.0.2-0ubuntu1 (source)]

[Stephan Hermann]

Subject: New: php-xdebug 2.0.2-0ubuntu1 (source)
Date: Thu, 14 Feb 2008 17:15:11 -
From: Ubuntu Installer <[EMAIL PROTECTED]>
Reply-To: Ubuntu Installer <[EMAIL PROTECTED]>
To: Stephan Hermann <[EMAIL PROTECTED]>

NEW: php-xdebug_2.0.2.orig.tar.gz
NEW: php-xdebug_2.0.2-0ubuntu1.diff.gz
NEW: php-xdebug_2.0.2-0ubuntu1.dsc

Format: 1.7
Date: Thu, 29 Nov 2007 16:23:42 -0500
Source: php-xdebug
Binary: php5-xdebug
Architecture: source
Version: 2.0.2-0ubuntu1
Distribution: hardy
Urgency: low
Maintainer: Ubuntu MOTU Developers 
Changed-By: Mark A. Hershberger <[EMAIL PROTECTED]>
Description:
 php5-xdebug - xdebug module for PHP 5
Launchpad-Bugs-Fixed: 189928
Changes:
 php-xdebug (2.0.2-0ubuntu1) hardy; urgency=low
 .
   * Initial Release (LP: #189928).
Files:
 307ece2acf3f608a7535bd214839c4b4 765 web optional
php-xdebug_2.0.2-0ubuntu1.dsc
 b994465f9941db4e7ffa4f8b81fa5c3d 279621 web optional
php-xdebug_2.0.2.orig.tar.gz
 a4559a24ff6df0ea2711dca7b266b1a5 4978 web optional
php-xdebug_2.0.2-0ubuntu1.diff.gz
Original-Maintainer: Mark A. Hershberger <[EMAIL PROTECTED]>



Your package contains new components which requires manual editing of
the override file.  It is ok otherwise, so please be patient.  New
packages are usually added to the overrides about once a week.

You may have gotten the distroseries wrong.  If so, you may get warnings
above if files already exist in other distroseries.

-- 
You are receiving this email because you are the uploader, maintainer or
signer of the above package.


-- 
Ubuntu-motu mailing list
Ubuntu-motu@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu

Re: Feature Freeze and bug fix releases

[Stephan Hermann]

Hi Scott,

Scott Kitterman wrote:
> We no longer have upstream version freeze, we have feature freeze, so I 
> wonder 
> about upstream releases that just have bug fixes.  IIRC when the new freeze 
> structure was created there was some discussion about this.
> 
> Speaking for myself (not as part of motu-release, because we haven't 
> discussed 
> it), I think we generally want bug fix releases for a while.  Here is my 
> proposal:
> 
> Up through Alpha 6, if a MOTU believes upload of a new upstream release that 
> just has bug fixes in it is warranted, they may upload it.  File a bug in LP 
> with the upstream change log entries in it and mark it fix released when the 
> upload is done to document that it was bug fix only.  If you have doubts 
> about if something qualifies, check with a member of motu-release (or 
> subscribe motu-release to the bug) and if one person from motu-release agrees 
> it's a bug fix update, you're good for upload.
> 
> Comments?

That's how I see it, too. If a new upstream fixes serious bugs, we
should bring it in...(not forgetting the paperwork and an ack from
motu-release)

Regards,

\sh

-- 
Ubuntu-motu mailing list
Ubuntu-motu@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu

Feature Freeze and bug fix releases

[Scott Kitterman]

We no longer have upstream version freeze, we have feature freeze, so I wonder 
about upstream releases that just have bug fixes.  IIRC when the new freeze 
structure was created there was some discussion about this.

Speaking for myself (not as part of motu-release, because we haven't discussed 
it), I think we generally want bug fix releases for a while.  Here is my 
proposal:

Up through Alpha 6, if a MOTU believes upload of a new upstream release that 
just has bug fixes in it is warranted, they may upload it.  File a bug in LP 
with the upstream change log entries in it and mark it fix released when the 
upload is done to document that it was bug fix only.  If you have doubts 
about if something qualifies, check with a member of motu-release (or 
subscribe motu-release to the bug) and if one person from motu-release agrees 
it's a bug fix update, you're good for upload.

Comments?


Scott K

-- 
Ubuntu-motu mailing list
Ubuntu-motu@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu

reminder: MOTU meeting

[Stefan Potyra]

Hi,

quick reminder: the MOTU meeting takes place at 4.00 UTC on Feb 15th in 
#ubuntu-meeting. 

If you're interested in ubuntu universe development, please join us at the 
meeting.

P.S.: Now would be a good time, to add your points to the agenda at 
.

Cheers,
  Stefan.


pgpFq1Vxw9iP8.pgp
Description: PGP signature
-- 
Ubuntu-motu mailing list
Ubuntu-motu@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu

avant window navigator

[Night Train]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

ho installato questa nuova versione di Avant Window Navigator, che da
poco è presente nei repo di ubuntu quindi senza dover aggiungere repo di
terzi, ma mancano totalmente le applets.
credo manchi il corrispondente pacchetto, che nelle altre versioni si
chiamava awn-core-applets.
per la cronaca, ho installato, su ubuntu 7.10 a 64 bit, i seguenti
pacchetti e non ho ricevuto errori di dipendenze o altro:
avant-window-navigator 0.2.1-0ubuntu1~gutsy1;
awn-manager 0.2.1-0ubuntu1~gutsy1;
libawn0 0.2.1-0ubuntu1~gutsy1;
libawn-dev 0.2.1-0ubuntu1~gutsy1; (che non era richiesto)
python-awn 0.2.1-0ubuntu1~gutsy1.

in /usr/lib/awn/applets c'è solo Launcher/Taskmanager

qualche idea?
grazie


Night Train
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHtE6Gyx3Ux97owlARAmItAJ981JYS+U2swhbcYRHzY8JzzaDvfQCdHs1D
XxIXwvEUPJUFZERZCujCcaI=
=SW/O
-END PGP SIGNATURE-

-- 
Ubuntu-motu mailing list
Ubuntu-motu@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu

Re: some help with debian merge

[Luis de Bethencourt]

On Thu, Feb 14, 2008 at 2:01 PM, Luis de Bethencourt <[EMAIL PROTECTED]> wrote:
> Can somebody please help me with the blender merge?
>  https://bugs.edge.launchpad.net/ubuntu/+source/blender/+bug/191130
>
>  I have compiling errors when doing pbuilder build, in some
>  src/blender/python stuff. I would really like this merge to make it
>  before freeze.
>

The pbuilder log, thanks for the help!

Luis

>  Luis de Bethencourt
>
>  --
>  Luis de Bethencourt Guimerá
>  luisbg
>  <[EMAIL PROTECTED]>
>  GPG: B0ED1326
>



-- 
Luis de Bethencourt Guimerá
luisbg
<[EMAIL PROTECTED]>
GPG: B0ED1326


pbuilder_log
Description: Binary data
-- 
Ubuntu-motu mailing list
Ubuntu-motu@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu

some help with debian merge

[Luis de Bethencourt]

Can somebody please help me with the blender merge?
https://bugs.edge.launchpad.net/ubuntu/+source/blender/+bug/191130

I have compiling errors when doing pbuilder build, in some
src/blender/python stuff. I would really like this merge to make it
before freeze.

Luis de Bethencourt

-- 
Luis de Bethencourt Guimerá
luisbg
<[EMAIL PROTECTED]>
GPG: B0ED1326

-- 
Ubuntu-motu mailing list
Ubuntu-motu@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu

REVU: New: phatch 0.1-0ubuntu1 (source)

[Scott Kitterman]

Subject: New: phatch 0.1-0ubuntu1 (source)
Date: Wednesday 13 February 2008 22:36
From: Ubuntu Installer <[EMAIL PROTECTED]>
To: Scott Kitterman <[EMAIL PROTECTED]>, Emilio Pozuelo Monfort 
<[EMAIL PROTECTED]>

NEW: phatch_0.1.orig.tar.gz
NEW: phatch_0.1-0ubuntu1.diff.gz
NEW: phatch_0.1-0ubuntu1.dsc

Format: 1.7
Date: Wed, 13 Feb 2008 23:48:47 +0100
Source: phatch
Binary: phatch
Architecture: source
Version: 0.1-0ubuntu1
Distribution: hardy
Urgency: low
Maintainer: Ubuntu MOTU Developers 
Changed-By: Emilio Pozuelo Monfort <[EMAIL PROTECTED]>
Description:
 phatch - Simple to use cross-platform GUI Photo Batch Processor
Launchpad-Bugs-Fixed: 145193
Changes:
 phatch (0.1-0ubuntu1) hardy; urgency=low
 .
   * Initial release (LP: #145193)
Files:
 0616a34da32c641d800aa923d3c88ac3 893 graphics optional
 phatch_0.1-0ubuntu1.dsc eaf7c80a72cee5b206fb3b86cdaaf5da 2097934 graphics
 optional phatch_0.1.orig.tar.gz 640092d07cf513f6021dbc954622816f 4389
 graphics optional phatch_0.1-0ubuntu1.diff.gz Original-Maintainer: Python
 Applications Packaging Team <[EMAIL PROTECTED]>

Your package contains new components which requires manual editing of
the override file.  It is ok otherwise, so please be patient.  New
packages are usually added to the overrides about once a week.

You may have gotten the distroseries wrong.  If so, you may get warnings
above if files already exist in other distroseries.

--
You are receiving this email because you are the uploader, maintainer or
signer of the above package.

-- 
Ubuntu-motu mailing list
Ubuntu-motu@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu