cairo-dock-team team mailing list archive

[Nobuhiro Iwamatsu <657564@xxxxxxxxxxxxxxxxxx>]

Hi,

Sorry, answer is too late...

2011/8/31 Matthieu Baerts <matttbe@xxxxxxxxx>:
> Hello and sorry for this late answer...
>
>> What do you mean that Debian is refusing to apply patches from
> upstream? What are these patches? Are there bugs about them in Debian's
> bug tracker, and why doesn't upstream just release a new tarball? Unless
> you really mean that upstream prefers a certain packaging layout which
> is not something that upstream needs to worry about.
>
> We (the developers of Cairo-Dock) don't like our Debian packages for a few reasons:
>  * About Cairo-Dock (core):
>  - Their patches are strange...They change the version number! Maybe there is a good reason but they do that without posting any message here or on our forum. This is a bit annoying because that's change the name of our soname, of our themes, of all .conf files and it's also a problem when we have to debug something or if we add some restriction about the version (about our plug-ins).

This was a change for package checks of Debian (lintian).

>  - They change our default theme. I can understand that they replace
firefox by iceweasel but now, if firefox is not available it will use
iceweasel. But I don't understand why they change the terminal
application... They can propose to us to change something, it's not a
problem but they force this modification....

We have not forced it on you about this.
This is a correction to have only in Debian.

>  - cairo-dock-core and cairo-dock-data have been merged, but why? Is
it not a recommendation to split this kind of packages like that?

Hmm? We have not provided cairo-dock-data package.
We will change it like that if you want to divide it as cairo-dock-data package.

> * About Cairo-Dock Plug-Ins:
>  - They have changed the name of the package (cairo-dock-plug-ins -> cairo-dock-plugins). Ok, it's the official name (set in the CMakeLists.txt file but not on Launchpad and BZR) but this package has been uploaded on Ubuntu before to be uploaded on Debian and this package has been proposed on Debian with the same name.

The up stream was cairo-dock-plugins. We only just use it.
If you need , I will change.

>  - The version has been changed too but it's a problem if there is a
modification in the API because the dock checks if we use the same
version (core and plug-ins)

I recommend that you change major and minor of soname if API is added,
and movement changes.
I cannot change these.

>  - They have split each plugin in one package per plugin but it's not
a good idea for a few things (see above) (e.g. it's harder to maintain
it: the name can change, one plugin can be required by another, our
themes can be modified, our new plug-ins are often missing, etc.)

Because there is a user doing various how to use in Debian, I do
packaging so that many users are easy to use it.
I explain this by a former email.

>  - A few files are missing (e.g. for our DBus plugin)

Please bug report.

>  - Our 'integration' plug-ins do not required of any dependences (we
do not have to use shlibs for them) because they are used only if a
library is available (e.g. our XFCE plug-in is activated only if thunar
and gvfs is available but you don't need to install thunar and all other
XFCE lib if you're using LXDE... a lot of useless dependences (more than
30Mo I think) are installed and it's a bit ridiculous (bug already
reported two years ago I think)

Sorry, where did you report this bug?
At least I was not able to find it in Debian.

>  - Our unstable plug-ins are compiled and installed, why? And our new plug-ins are not available...
>  (...)
> I've proposed a new version of these two packages on mentors.debian.net (see above) but these modifications have been rejected (not all of them, thank you for these modifications but it's not enough...). I've also proposed to maintain these packages but without any success (yes, I'm an Ubuntu user so I guess I'm not able to do that... even if I'm a former Debian user.? :) but it will be so easier...)
>

Few month ago, I meet you in the cairo-dock packaging team.
If there is the place that you want to change, please argue in a
mailing list with other members.


> Also I want to note that these plug-ins packages have been included
> first in Ubuntu (I don't know why but our previous maintainer wanted to
> do that...) and then in Debian but the Debian maintainers have change
> the name and all the content of the debian directory :-/
>
>
>> Please stop pushing to this duplicate source package and have the Debian named package provide the same named transitional packages so that upgraders will get the correctly named packages.
>
> Do I have to rename the source package? ('cairo-dock-plugins' instead of
> 'cairo-dock-plug-ins')
>

I will do this in debian too


Best regards,
  Nobuhiro

-- 
Nobuhiro Iwamatsu
   iwamatsu at {nigauri.org / debian.org}
   GPG ID: 40AD1FA6

-- 
You received this bug notification because you are a member of Cairo-
Dock Team, which is subscribed to cairo-dock-plugins in Ubuntu.
https://bugs.launchpad.net/bugs/657564

Title:
  Duplicated package with cairo-dock-plugins (coming from Debian)

Status in “cairo-dock-plug-ins” package in Ubuntu:
  Confirmed
Status in “cairo-dock-plugins” package in Ubuntu:
  Confirmed
Status in “cairo-dock-plug-ins” source package in Natty:
  Confirmed
Status in “cairo-dock-plugins” source package in Natty:
  Confirmed
Status in “cairo-dock-plug-ins” source package in Oneiric:
  Confirmed
Status in “cairo-dock-plugins” source package in Oneiric:
  Confirmed
Status in “cairo-dock-plugins” package in Debian:
  Confirmed

Bug description:
  Binary package hint: cairo-dock-plug-ins

  Hi,

  After syncing cairo-dock-plugin package from debian, we now have two
  time the same source in the archive. Please work with Debian to be
  able to merge the 2 packages, and have it only once.

  Thanks,
  Fabrice

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cairo-dock-plug-ins/+bug/657564/+subscriptions