On Thu, 6 Nov 2014 22:49:38 +
Ciaran McCreesh wrote:
> Not if the new package has already been added you can't. Moving a
> package on top of an existing package is very very bad.
Also, the versions don't actually match so the content will probably
have changed. Oh well.
jer
On Thu, 6 Nov 2014 23:47:20 +0100
Jeroen Roovers wrote:
> On Thu, 06 Nov 2014 23:44:24 +0100
> Manuel Rüger wrote:
> > It could have been introduced to the tree as a pkgmove, but it
> > wasn't. The best solution for now is imho to lastrite it.
>
> You could still do the pkgmove right now, and no
On Thu, 06 Nov 2014 23:44:24 +0100
Manuel Rüger wrote:
> It could have been introduced to the tree as a pkgmove, but it wasn't.
> The best solution for now is imho to lastrite it.
You could still do the pkgmove right now, and not wait thirty days. :)
jer
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 06.11.2014 23:19, Jeroen Roovers wrote:
> On Thu, 06 Nov 2014 22:03:26 +0100 Manuel Rüger
> wrote:
>
>> # Manuel Rüger (6 Nov 2014) # Use
>> kde-base/oxygen-fonts instead # Masked for removal in 30 days
>> media-fonts/oxygen-fonts
>
> That on
On Thu, 06 Nov 2014 22:03:26 +0100
Manuel Rüger wrote:
> # Manuel Rüger (6 Nov 2014)
> # Use kde-base/oxygen-fonts instead
> # Masked for removal in 30 days
> media-fonts/oxygen-fonts
That one wasn't up for a pkgmove?
jer
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
# Manuel Rüger (6 Nov 2014)
# Use kde-base/oxygen-fonts instead
# Masked for removal in 30 days
media-fonts/oxygen-fonts
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0
iQJ8BAEBCgBmBQJUW+IeXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlm
