Sync alltray 0.70-1 (universe) from Debian testing (main)

[Allisson Azevedo]

Please sync alltray 0.70-1 (universe) from Debian testing (main)

Explanation of the Ubuntu delta and why it can be dropped:
- New upstream version.
- None of the Ubuntu patches apply on this version, according to the debian testing changelog.

Changelog entries since current lucid version 0.69-1ubuntu4:

alltray (0.70-1) unstable; urgency=low

  * QA upload.
  * Orphan the package as Carlos C Soto has no time to maintain it properly.
  * New upstream release.
  * Switch to 3.0 (quilt).
  * Move Homepage into its own control field.
  * Rename XS-Vcs-Svn in Vcs-Svn.
  * Drop linda overrides.
  * Switch to dh 7 tiny rules file and compat mode 7.
  * Add ${misc:Depends} to Depends.
  * Add watch file.
  * Update to Standards-Version 3.8.3.
  * None of the Ubuntu patches apply on this version, I did not look further
    to try to integrate them.

 -- Raphaël Hertzog <email address hidden> Mon, 25 Jan 2010 21:08:33 +0100

[Michael B. Trausch (mtrausch)]

Hi,

I was just wondering what the status of the new AllTray package that
Ignace was preparing for Debian was. Someone just reported Launchpad
bug 528675 (which is cc'd on this email) which is a sync request to
bring a new AllTray from Debian to Ubuntu, but the one in Debian appears
to not have been updated yet.

Does anyone know what the status on this is? Thanks!

 --- Mike

--
Michael B. Trausch ☎ [phone]

[Chow Loong Jin (hyperair)]

Patches not applying is a poor excuse to not integrate / drop them. Each patch has a description in its header explaining what it is for, and some even have bugs associated with them, i.e. they fix bugs. Please refresh these patches and manually merge their changes in for the hunks that do not apply.

After that, the next step would be to get these packages integrated into the alltray package in Debian, either by contacting the Maintainer directly, or by reporting bugs against the package in Debian and attaching said refreshed patches to them. In this case it would probably be sufficient to just drop an e-mail to Raphaël once you have refreshed them, considering he has already given the Ubuntu patches a glance.

I will be unsubscribing ubuntu-universe-sponsors for now. Please re-subscribe us when the merge is ready for review and uploading.

[Michael B. Trausch (mtrausch)]

On 02/26/2010 06:42 PM, Chow Loong Jin wrote:
> Patches not applying is a poor excuse to not integrate / drop them. Each
> patch has a description in its header explaining what it is for, and
> some even have bugs associated with them, i.e. they fix bugs. Please
> refresh these patches and manually merge their changes in for the hunks
> that do not apply.
>
> After that, the next step would be to get these packages integrated into
> the alltray package in Debian, either by contacting the Maintainer
> directly, or by reporting bugs against the package in Debian and
> attaching said refreshed patches to them. In this case it would probably
> be sufficient to just drop an e-mail to Raphaël once you have refreshed
> them, considering he has already given the Ubuntu patches a glance.
>
> I will be unsubscribing ubuntu-universe-sponsors for now. Please re-
> subscribe us when the merge is ready for review and uploading.

For the record, someone has prepared a newer version of AllTray (though
it would appear to have not made it into Debian yet) where the patches
(at least all of them that I and Ignace, the person who is attempting to
adopt the AllTray package in Debian, are aware of) have been
incorporated into the upstream AllTray distribution. A new release of
AllTray on this branch has been issued, and that should be used.

If there are any patches which remain to be applied upstream, I would
like to be made aware of them so that they can be incorporated.

 Thanks,
 Mike Trausch

--
Michael B. Trausch ☎ [phone]

[Chow Loong Jin (hyperair)]

On Saturday 27,February,2010 08:39 AM, Michael B. Trausch wrote:
> On 02/26/2010 06:42 PM, Chow Loong Jin wrote:
>> [...]
>
> For the record, someone has prepared a newer version of AllTray (though
> it would appear to have not made it into Debian yet) where the patches
> (at least all of them that I and Ignace, the person who is attempting to
> adopt the AllTray package in Debian, are aware of) have been
> incorporated into the upstream AllTray distribution. A new release of
> AllTray on this branch has been issued, and that should be used.

A newer version? You mean one of the 0.7.[1-4]dev versions? Those appear to be
alpha releases of a complete rewrite, and hence not fit for uploading to Ubuntu
just yet.

>
> If there are any patches which remain to be applied upstream, I would
> like to be made aware of them so that they can be incorporated.

The patches are in the debian/patches folder of the extracted 0.69-1ubuntu4
source package. I have attached these patches for reference. Their extensions
are dpatch, but they can be applied using `patch -p1 -i <patchname>` like any
other -p1 patch. As mentioned before, the patch headers contain bug links and
descriptions as to what they do. It is quite possible to get these patches to
apply to 0.70, but I'm not sure it would be as simple for one of the releases
post-rewrite.

--
Kind regards,
Chow Loong Jin (GPG: 0x8F02A411)
Ubuntu Developer

[Michael B. Trausch (mtrausch)]

On 02/27/2010 12:32 AM, Chow Loong Jin wrote:
> On Saturday 27,February,2010 08:39 AM, Michael B. Trausch wrote:
>> On 02/26/2010 06:42 PM, Chow Loong Jin wrote:
>>> [...]
>>
>> For the record, someone has prepared a newer version of AllTray (though
>> it would appear to have not made it into Debian yet) where the patches
>> (at least all of them that I and Ignace, the person who is attempting to
>> adopt the AllTray package in Debian, are aware of) have been
>> incorporated into the upstream AllTray distribution. A new release of
>> AllTray on this branch has been issued, and that should be used.
>
> A newer version? You mean one of the 0.7.[1-4]dev versions? Those appear to be
> alpha releases of a complete rewrite, and hence not fit for uploading to Ubuntu
> just yet.

No, a new release from the old-maintenance branch, which (to my
knowledge) has incorporated the fixes from Ubuntu (AFAIK, there were no
Debian-specific fixes). My apologies if I was unclear in specifying
that the release I was talking about came from the same branch as that
which is already in Debian.

The dev releases are not quite alpha, but they are not releases that I
would recommend be in Debian or Ubuntu unless they were packaged under a
different name that was obviously known to be unstable. I'm not ready
for that until the last feature is implemented, and even then, there
will be a period of testing before I call it 0.8.0 and release it and
welcome distributors to package it.

You may want to check the branches on LP:

  https://edge.launchpad.net/alltray

Which include the old-maintenance branch and its recent release, 0.71a,
which is a bug fix release of 0.70.

>> If there are any patches which remain to be applied upstream, I would
>> like to be made aware of them so that they can be incorporated.
>
> The patches are in the debian/patches folder of the extracted 0.69-1ubuntu4
> source package. I have attached these patches for reference. Their extensions
> are dpatch, but they can be applied using `patch -p1 -i<patchname>` like any
> other -p1 patch. As mentioned before, the patch headers contain bug links and
> descriptions as to what they do. It is quite possible to get these patches to
> apply to 0.70, but I'm not sure it would be as simple for one of the releases
> post-rewrite.

As far as I am aware, 0.71a (again, not 0.7.{1,2,3,4}-dev, which is
indeed a re-write; 0.71a is a continuation of the 0.70 line)
incorporates all the fixes that were present in ubuntu. This is why I
am confused at the sync request here, it doesn't make sense. Debian bug
566880 is, as I understand it, going to be resolved with an upload of
AllTray 0.71a, which should _then_ be brought to Ubuntu (though if it
comes to Ubuntu directly, that would also be fine---0.71a is a stable
release with bug fixes from 0.70).

In short (and this is just my 2¢ as the author of new AllTray and
maintainer of the old AllTray source code), I don't think 0.70-1 should
be imported from Debian. 0.71a should be available in Debian soon, and
I suspect that will result in a package 0.71a-1, which would be suitable
for inclusion in Ubuntu (as the 0.69 patches that I recall being in
ub...

[Chow Loong Jin (hyperair)]

On Saturday 27,February,2010 03:57 PM, Michael B. Trausch wrote:
> [...]
>
> No, a new release from the old-maintenance branch, which (to my
> knowledge) has incorporated the fixes from Ubuntu (AFAIK, there were no
> Debian-specific fixes). My apologies if I was unclear in specifying
> that the release I was talking about came from the same branch as that
> which is already in Debian.
>
> The dev releases are not quite alpha, but they are not releases that I
> would recommend be in Debian or Ubuntu unless they were packaged under a
> different name that was obviously known to be unstable. I'm not ready
> for that until the last feature is implemented, and even then, there
> will be a period of testing before I call it 0.8.0 and release it and
> welcome distributors to package it.

It could probably enter Debian Experimental, but not Debian Unstable, Testing or
Ubuntu, but this is to be handled by the new alltray package maintainer in Debian.

> You may want to check the branches on LP:
>
> https://edge.launchpad.net/alltray
>
> Which include the old-maintenance branch and its recent release, 0.71a,
> which is a bug fix release of 0.70.

I am sorry, but I was looking at https://edge.launchpad.net/alltray/+download
and could not find it, so I assumed that 0.70 was the latest prior to the
rewrite. Is that tarball an automatically generated tarball of a tag or
something? I think you should make it available at the aforementioned downloads
page as it is confusing and not discoverable to have your tarballs all over the
place.

>
> [...]
>
> As far as I am aware, 0.71a (again, not 0.7.{1,2,3,4}-dev, which is
> indeed a re-write; 0.71a is a continuation of the 0.70 line)
> incorporates all the fixes that were present in ubuntu. This is why I
> am confused at the sync request here, it doesn't make sense. Debian bug
> 566880 is, as I understand it, going to be resolved with an upload of
> AllTray 0.71a, which should _then_ be brought to Ubuntu (though if it
> comes to Ubuntu directly, that would also be fine---0.71a is a stable
> release with bug fixes from 0.70).

As I have just mentioned, there was quite a bit of confusion as to what
constitutes a new release from the old-maintenance branch, considering the
tarballs aren't available from your main downloads page.

> In short (and this is just my 2¢ as the author of new AllTray and
> maintainer of the old AllTray source code), I don't think 0.70-1 should
> be imported from Debian. 0.71a should be available in Debian soon, and
> I suspect that will result in a package 0.71a-1, which would be suitable
> for inclusion in Ubuntu (as the 0.69 patches that I recall being in
> ubuntu had to be adopted and backported from the old-maintenance bzr
> tree in the first place, like the GTK tooltip/balloon fix).

Yes, that's right. 0.71a should be synced from Debian once it gets ready,
assuming all our Ubuntu-specific patches so far can be dropped (if they have all
been applied upstream, for example) then.

I will mark this sync request as invalid then. Please make a new one when the
time comes (or poke me either via IRC or email and I will look into it).

  affects ubuntu/alltray
  status invalid

--
...

[Michael B. Trausch (mtrausch)]

On 02/27/2010 03:13 AM, Chow Loong Jin wrote:
> I am sorry, but I was looking
> athttps://edge.launchpad.net/alltray/+download and could not find it,
> so I assumed that 0.70 was the latest prior to the rewrite. Is that
> tarball an automatically generated tarball of a tag or something? I
> think you should make it available at the aforementioned downloads
> page as it is confusing and not discoverable to have your tarballs
> all over the place.

If you look at the front page for a project, you can see its releases.
If you click on a release number, you will be taken to its page, where
you can download it.

Unfortunately, I have no control over Launchpad, and the behavior you
have described here is due to a bug in Launchpad itself. This was
reported as Launchpad bug 490945, but the Launchpad people feel it is a
low-priority bug. Of course, I disagree.

 --- Mike

--
Michael B. Trausch ☎ [phone]