Re: update F34 - f35 postgresql module issue

2021-10-26 Thread Bruno Wolff III 

On Sat, Oct 23, 2021 at 23:40:25 +0200,
 Peter Boy  wrote:


Fedora 35 comes obviously without Postgres module 9.6. Unfortunately, the 
release change set doesn’t mention that. We need a clear indication and warning 
of this.


That might be because 9.6 gets its last update in about two weeks. This 
means that it will be unsupported for most of the lifetime of F35.

___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: update F34 - f35 postgresql module issue

2021-10-26 Thread Petr Pisar 
V Mon, Oct 25, 2021 at 12:23:29PM +0200, Peter Boy napsal(a):
> 
> > Am 24.10.2021 um 04:55 schrieb Samuel Sieb :
> > 
> > I've never used the modules, but with rpms, you get the postgresql-upgrade
> > package installed as well in order to upgrade the database.  Is this not
> > available with modules?
> 
> I’m not sure either. According to module list it only provides server and
> client.

No. Those are profiles. Those are just shortcuts for "please install packages
for a posgresql server" or "for a client". The complete list of packages can
be seen with "dnf module info postgresql:10" which lists postgresql-upgrade
RPM package. So once you do "dnf module switch-to postgresql:10", you can
install postgresql-upgrade with "dnf install postgresql-upgrade" if it has not
yet been installed.

> But that’s not a problem for me. We used modules to avoid upgrading.
> And we have an old service which requires version 9.6. So upgrade is not
> really an option.
> 
Well, Fedora won't support version 9.6 indefinitely.

> The postgresql project provides a version 9.6 rpm for Fedora 34. Don’t know
> if they will do it for Fedora 35 as well (I hope so).
> 
I also have no idea. File a request in Bugzilla. That's the way of
communicating with distribution maintainers.

> My main issue is that f35 removes the postgresql module version 9.6 without
> notice in the release notes or warning during upgrade.
> 
> And now dnf always complains
> "Problem: conflicting requests
>   - nothing provides module(platform:f34) needed by module 
> postgresql:9.6:3420210210170810:058368ca.x86_64“
>
That's the warning you were missing. Is that after a successfull "dnf
upgrade"? Or is it an error which prevents DNF from completing the upgrade?

> although this postgresql version is no longer present on the system.
> 
> Do you know, how I get rid of that? 
> 
There is no way. Either do not upgrade, or switch to a newer postgresql stream
(dnf switch-to postgresql:10), or persuade maintainers in Bugzilla to add 9.6.
into Fedora 35.

-- Petr


signature.asc
Description: PGP signature
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: update F34 - f35 postgresql module issue

2021-10-25 Thread Petr Pisar 
V Sat, Oct 23, 2021 at 11:40:25PM +0200, Peter Boy napsal(a):
> I just tested the dnf upgrade procedure on one of our standby backup systems
> which happens to have the F34 postgresql module version 9.6 installed. 
> 
> The module was overwritten with version 13 without warning.

I guess DNF reported "disabling postgresql:9.6 stream" among all packages to
upgrade and you had to approve the DNF transaction explicitly. If it is not
that case, then report a bug against DNF. I think DNF shuld not silently
uninstall a module stream.

However, if PostgreSQL maintainers did not provide postgresql:9.6 stream for
Fedora 35, then DNF has no much options except of aborting the upgrade. Modules
are always built for a specific Fedora release and are not portable to another
release.

> Given the data incompatibility, this is a very unattractive practice. As far
> as I remember, one could rely on the fact that with an upgrade the
> respective module was updated in the installed version. 
> 
I don't understand what you remember. In Fedora, there is currently no
mechanism for transitioning between module streams. E.g. from postgresql:9.6 to
postgresql:13.

The mechanism
 was planned
for Fedora 35, but it was postponed to Fedora 36. When the machanism is
implemented, then DNF will advertise that postgresql:9.6 ends its life on
2021-12-01 and the users are advised to migrate to postgresql:10. Maybe DNF
will offer switching from the old stream to the new stream during an upgrade
transaction. However, the mechanism won't provide any software-specific
migration tools, like convertingdatabase files from one format to another one.

Nowdays the end-of-life date can be obtained at

web page.

> Fedora 35 comes obviously without Postgres module 9.6.

Yes, I confirm it. It only delivers PostgresSQL 10 to 14.

> Unfortunately, the release change set doesn’t mention that. We need a clear
> indication and warning of this. 
>
If you believe that removal of a postgresql stream from a new Fedora release
is an important change and suitable for Fedora release notes, that file a bug
against that module stream
.
I cannot see any change like that on Fedora 35's list of changes
.

Also the maintainers could build postgresql:9.6 for F35 and support it there
until 2021-12-01. Maybe they only forgot to build it there.

-- Petr


signature.asc
Description: PGP signature
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: update F34 - f35 postgresql module issue

2021-10-25 Thread Peter Boy 


> Am 24.10.2021 um 04:55 schrieb Samuel Sieb :
> 
> On 10/23/21 14:40, Peter Boy wrote:
>> I just tested the dnf upgrade procedure on one of our standby backup systems 
>> which happens to have the F34 postgresql module version 9.6 installed.
>> The module was overwritten with version 13 without warning. Given the data 
>> incompatibility, this is a very unattractive practice. As far as I remember, 
>> one could rely on the fact that with an upgrade the respective module was 
>> updated in the installed version.
>> Fedora 35 comes obviously without Postgres module 9.6. Unfortunately, the 
>> release change set doesn’t mention that. We need a clear indication and 
>> warning of this.
> 
> I've never used the modules, but with rpms, you get the postgresql-upgrade 
> package installed as well in order to upgrade the database.  Is this not 
> available with modules?


I’m not sure either. According to module list it only provides server and 
client. But that’s not a problem for me. We used modules to avoid upgrading. 
And we have an old service which requires version 9.6. So upgrade is not really 
an option.

The postgresql project provides a version 9.6 rpm for Fedora 34. Don’t know if 
they will do it for Fedora 35 as well (I hope so).

My main issue is that f35 removes the postgresql module version 9.6 without 
notice in the release notes or warning during upgrade.

And now dnf always complains
"Problem: conflicting requests
  - nothing provides module(platform:f34) needed by module 
postgresql:9.6:3420210210170810:058368ca.x86_64“

although this postgresql version is no longer present on the system.

Do you know, how I get rid of that? 




Thanks
Peter

___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: update F34 - f35 postgresql module issue

2021-10-23 Thread Samuel Sieb 

On 10/23/21 14:40, Peter Boy wrote:

I just tested the dnf upgrade procedure on one of our standby backup systems 
which happens to have the F34 postgresql module version 9.6 installed.

The module was overwritten with version 13 without warning. Given the data 
incompatibility, this is a very unattractive practice. As far as I remember, 
one could rely on the fact that with an upgrade the respective module was 
updated in the installed version.

Fedora 35 comes obviously without Postgres module 9.6. Unfortunately, the 
release change set doesn’t mention that. We need a clear indication and warning 
of this.


I've never used the modules, but with rpms, you get the 
postgresql-upgrade package installed as well in order to upgrade the 
database.  Is this not available with modules?

___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure