On Fri, 31 Jul 2020 12:48:44 +0200, Tomasz Torcz wrote:
> What about bringing old, possibly unmaintained library into Fedora?
> It may contain unfixed security bugs. Not that I know of any, but it's
> a possibility.
1) First it would need to pass the review process. Submitter _and_
reviewer
On Fri, Jul 31, 2020 at 12:01:53PM +0200, Michael Schwendt wrote:
> libqmatrixclient vs libquotient
>
> Absolutely no conflict whatsoever. Different SONAME, different file/folder
> names, different package names, different project name. Even if they came
> from the same project, the old compat-
libqmatrixclient vs libquotient
Absolutely no conflict whatsoever. Different SONAME, different file/folder
names, different package names, different project name. Even if they came
from the same project, the old compat- naming scheme would not have applied.
Vitaly Zaitsev via devel wrote:
> Previously it wasn't allowed to push different versions of the same
> project into repositories. That's why Fedora Modularity was invented.
That is what the Modularity developers wanted you to believe. The fact is,
parallel-installable compatibility libraries
On Thursday, 30 July 2020 at 17:11, Vitaly Zaitsev via devel wrote:
> On 30.07.2020 10:03, Kevin Kofler wrote:
> > Independently of what the current packaging guidelines say about this
> > (apparently, "compat-" is not even a thing anymore there, see Rathann's
> > reply), it simply does not make
On 30.07.2020 10:03, Kevin Kofler wrote:
> Independently of what the current packaging guidelines say about this
> (apparently, "compat-" is not even a thing anymore there, see Rathann's
> reply), it simply does not make sense to use any sort of prefixing or
> suffixing to the package name when
Vitaly Zaitsev via devel wrote:
> Libqmatrixclient is a very old version of libquotient. Compatibility
> packages should have compat- prefix.
Independently of what the current packaging guidelines say about this
(apparently, "compat-" is not even a thing anymore there, see Rathann's
reply), it
On Wednesday, 29 July 2020 at 20:06, Vitaly Zaitsev via devel wrote:
> On 29.07.2020 19:33, Brendan Early wrote:
> > Can you please explain what you mean by conflicts? They are in
> > completely different directories.
>
> Libqmatrixclient is a very old version of libquotient. Compatibility
>
> > Can you please explain what you mean by conflicts? They are in
> > completely different directories.
> Libqmatrixclient is a very old version of libquotient. Compatibility
> packages should have compat- prefix.
- That is not a conflict. I do not understand what is conflicting.
- Untagging is
On 29.07.2020 19:33, Brendan Early wrote:
> Can you please explain what you mean by conflicts? They are in
> completely different directories.
Libqmatrixclient is a very old version of libquotient. Compatibility
packages should have compat- prefix.
> I am unaware of any policy that does not
Vitaly,
Can you please explain what you mean by conflicts? They are in
completely different directories.
I am unaware of any policy that does not allow this, quaternion (by the
author of the library) has no release that can be built with libquotient
yet. Untagging libQMatrixClient will break
On 29.07.2020 19:14, Kevin Fenzi wrote:
> What exactly are the conflicts? Can you Obsolete/Provides whatever in
> libquotient?
libqmatrixclient is a very old version of libquotient (before the
upstream decided to rename it). Both of them provides the same files
(except of library versions).
If
On Wed, Jul 29, 2020 at 06:41:57PM +0200, Vitaly Zaitsev via devel wrote:
> Hello all.
>
> Duplicate package of libquotient - libqmatrixclient - was reviewed,
> accepted and pushed to stable repositories.
>
> Not it cause conflicts.
I guess you meant "Now" there?
>
> libqmatrixclient must be
Hello all.
Duplicate package of libquotient - libqmatrixclient - was reviewed,
accepted and pushed to stable repositories.
Not it cause conflicts.
libqmatrixclient must be untagged and removed from all Fedora releases.
--
Sincerely,
Vitaly Zaitsev (vit...@easycoding.org)
14 matches
Mail list logo
