>>  It looks like Wheeze will be without this package.
> Not necessarily. As far as I can read the release.debian.org hints, 2.0-3 has
> been hinted to migrate despite the freeze. So I think we can safely assume
> that a fixed 2.0-3 could pass the freeze.

I have asked release team about this package. But there is no reply yet.

> Now for the content of your proposed upload:
>   * Update to stable release 2.1.
>   * Deleted file debian/patches/fix-build-on-kfreebsd-and-hurd-i386:
>     accepted in upstream.
> The two above are too much for a freeze exception. They would be suitable for
> experimental.

There are only two changes in upstream between versions 2.0 and 2.1:
  * Accepted my patch fix-build-on-kfreebsd-and-hurd-i386.
  * Updated translations.

>   * Added file debian/patches/ignore-symlinks:
>     prevents of possible infinite loop because of circular symlinks.
>     (Closes: #678714)
> I'm far from convinced that your proposed patch properly addresses #678714:
> you address point 1 by "avoiding symlinks" (this means that a Gtk3 theme put
> under /usr/share/themes/* with a symlink would not be detected e.g.)

Hmm, I don't see symlinks in /usr/share/themes/ in my systems. Is it really
possible situation?

> and you
> haven't addressed the point 2; you should answer to the bugreport by
> explaining how you plan to address (or not) it.

Program don't scan user's home directory, but only ~/.themes/ subdirectory.
So I think the problem is related with symlinks. I'll ask him to check it.

> So if we want this to go to Wheezy, we need a proposed source package as
> minimal as possible from 2.0-3 which was hinted for Wheezy. New translations
> might be put in though.

Current package already has minimal possible changes in sources and updated

Best regards,

pkg-kde-extras mailing list

Reply via email to