On Thu, Sep 15, 2022 at 7:11 AM Lukas Javorsky wrote:
>
> We've decided to remove them in Fedora 42, but it's impossible to remember to
> do it for 2 years.
> There is no way to file a Bugzilla to Fedora 42 yet.
I can create a '42' version in Bugzilla and disable it after the bug
is created. I d
On Fri, Sep 16, 2022 at 09:48:28AM +0200, Lukas Javorsky wrote:
> > put a comment in the specfile :-)
> That's quite easy to miss.
It's also no problem if the Obsoletes/Provides remain in place. Even
indefinitely. A comment in the spec file is the correct mechanism for
this, as it's something that
>
> put a comment in the specfile :-)
>
That's quite easy to miss.
On Thu, Sep 15, 2022 at 1:38 PM Dan Horák wrote:
> On Thu, 15 Sep 2022 13:10:41 +0200
> Lukas Javorsky wrote:
>
> > Hi,
> >
> > I just got a question about how should I track the removal of "Provides
> and
> > Obsoletes" from t
On Thu, 15 Sep 2022 13:10:41 +0200
Lukas Javorsky wrote:
> Hi,
>
> I just got a question about how should I track the removal of "Provides and
> Obsoletes" from the new minizip-ng package.
>
> We've decided to remove them in Fedora 42, but it's impossible to remember
> to do it for 2 years.
> T
Hi,
I just got a question about how should I track the removal of "Provides and
Obsoletes" from the new minizip-ng package.
We've decided to remove them in Fedora 42, but it's impossible to remember
to do it for 2 years.
There is no way to file a Bugzilla to Fedora 42 yet.
Is there some place wh
On Thu, Jul 28, 2022 at 11:19 AM Lukas Javorsky wrote:
>
> Also, the idea is to file Bugs for all packages that BuildRequire/Require the
> minizip package and let them know about this change and if they should change
> theirs requirements.
Just an idea: You could even make the switch from miniz
I've just created a Fedora Change devoted for this:
https://fedoraproject.org/wiki/Changes/MinizipRenaming
Feel free to add some comments there.
On Thu, Jul 28, 2022 at 6:33 PM Ben Cotton wrote:
> On Thu, Jul 28, 2022 at 4:32 AM Lukas Javorsky
> wrote:
> >
> > The first step I want to do is to
On Thu, Jul 28, 2022 at 4:32 AM Lukas Javorsky wrote:
>
> The first step I want to do is to create a Fedora Change, which contains this
> whole process and is well communicated within the community.
>
> This email serves as a heads-up and also opens a possibility for any tips
> that you can give
I've checked the packaging that should be affected by this change on Fedora
Rawhide:
repoquery --whatrequires "*libminizip.so.3*" | pkgname | uniq
R-libSBML
collada-dom
dolphin-emu
dolphin-emu-tool
java-libsbml
keepassxc
libnuml
librasterlite2
libsbml
libspatialite
libxlsxwriter
minizip-devel
perl-
Also, the idea is to file Bugs for all packages that BuildRequire/Require
the minizip package and let them know about this change and if they should
change theirs requirements.
On Thu, Jul 28, 2022 at 10:57 AM Marcus Müller wrote:
> ah, true, different sonames solves this :)
>
> On 28.07.22 10:5
ah, true, different sonames solves this :)
On 28.07.22 10:52, Daniel P. Berrangé wrote:
On Thu, Jul 28, 2022 at 10:44:14AM +0200, Marcus Müller wrote:
The latter change seems unwise. Packages which now depend on minizip (to be
minizip-ng) will continue to do depend on whatever Provides(minizip)
On Thu, Jul 28, 2022 at 10:44:14AM +0200, Marcus Müller wrote:
> The latter change seems unwise. Packages which now depend on minizip (to be
> minizip-ng) will continue to do depend on whatever Provides(minizip); if you
> rename the zlib subpackage to minizip, they will depend on the wrong thing.
The latter change seems unwise. Packages which now depend on minizip (to be minizip-ng)
will continue to do depend on whatever Provides(minizip); if you rename the zlib
subpackage to minizip, they will depend on the wrong thing.
Cheers,
Marcus
On 28.07.22 10:31, Lukas Javorsky wrote:
Hi fello
Hi fellow contributors,
Upstream has reported a request for minizip naming change from "minizip" to
"minizip-ng" (minizip-ng is the official name of the upstream package right
now).
As Fedora should match the upstream naming, I believe this change is
necessary.
Another naming change is required
14 matches
Mail list logo
