Instatlled daily build 23/11 pgadmin4-fedora-repo.noarch and tried
 sudo dnf install pgadmin4-web
...

Dependencies resolved.
====================================================================================================================================================================================
 Package                                          Architecture
                 Version
Repository                               Size
====================================================================================================================================================================================
Installing:
 pgadmin4-web                                     noarch
                 6.2-1.fc35
pgAdmin4                                8.7 k
Installing dependencies:
 pgadmin4-server                                  x86_64
                 6.2-1.fc35
pgAdmin4                                 85 M
 postgresql14-libs                                x86_64
                 14.1-1PGDG.f35
pgAdmin4                                277 k

Transaction Summary
====================================================================================================================================================================================
Install  3 Packages

Total download size: 85 M
Installed size: 199 M
Is this ok [y/N]: y
Downloading Packages:
(1/3): pgadmin4-web-6.2-1.fc35.noarch.rpm

       33 kB/s | 8.7 kB     00:00
(2/3): postgresql14-libs-14.1-1PGDG.f35.x86_64.rpm

      619 kB/s | 277 kB     00:00
(3/3): pgadmin4-server-6.2-1.fc35.x86_64.rpm

      6.0 MB/s |  85 MB     00:14
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Total

      6.0 MB/s |  85 MB     00:14
Running transaction check
Transaction check succeeded.
Running transaction test
The downloaded packages were saved in cache until the next successful
transaction.
You can remove cached packages by executing 'dnf clean packages'.
Error: Transaction test error:
  file /usr/lib/.build-id/fb/0ab37232a700c1fc92e0fd8e1a6193224b1749
from install of pgadmin4-server-6.2-1.fc35.x86_64 conflicts with file
from package python3-3.10.0-1.fc35.x86_64

On Mon, 15 Nov 2021 at 11:23, Dave Page <dave.p...@enterprisedb.com> wrote:
>
> Hi
>
> On Sat, Nov 13, 2021 at 3:48 PM toni incog <toni.in...@gmail.com> wrote:
>>
>> Lo and behold, I just upgraded a laptop to f35 with pgadmin4 still
>> installed and it was enough to install python9 to get a running
>> desktop version. So when upgrading don't rm pgadmin, disable the
>> pgadmin repo and afterwards install python9. Not sure if that will
>> work for the web version.
>
>
> That's good to know - thanks for the info.
>
>>
>>
>> On Tue, 9 Nov 2021 at 17:35, richard coleman
>> <rcoleman.ascen...@gmail.com> wrote:
>> >
>> > Dave,
>> >
>> > Good to know,
>> >
>> > thanks,
>> > rik.
>> >
>> >
>> > On Tue, Nov 9, 2021 at 8:43 AM Dave Page <dave.p...@enterprisedb.com> 
>> > wrote:
>> >>
>> >> Hi
>> >>
>> >> On Tue, Nov 9, 2021 at 12:41 PM richard coleman 
>> >> <rcoleman.ascen...@gmail.com> wrote:
>> >>>
>> >>> Dave,
>> >>>
>> >>> Have you ever considered using something like flatpak ( 
>> >>> https://flatpak.org/ ) for the Linux versions of pgAdmin?  It might; 
>> >>> make it easier to handle the many different distributions, and deal with 
>> >>> the different release schedules of the many dependencies that pgAdmin 
>> >>> relies upon.
>> >>
>> >>
>> >> Technologies like Flatpak make it significantly harder to maintain 
>> >> applications like pgAdmin, and for system administrators to ensure their 
>> >> systems are secure. This is primarily because they bundle third party 
>> >> libraries within the application package, which means that every time 
>> >> there is a security update to a library such as OpenSSL, we need to 
>> >> update the package we distribute, and the system administrator can't 
>> >> simply do a yum update or equivalent and be sure that their system is as 
>> >> secure as possible. It also means end users need to install a separate 
>> >> package management tool from the one that is native to their system.
>> >>
>> >> So, whilst (if we had the resources) I wouldn't object to supporting 
>> >> Flatpak and similar, I would certainly not want them to replace the 
>> >> standard native packages as the primary offering.
>> >>
>> >>>
>> >>>
>> >>> Just a thought.
>> >>>
>> >>> rik.
>> >>>
>> >>>
>> >>> On Tue, Nov 9, 2021 at 4:23 AM Dave Page <dave.p...@enterprisedb.com> 
>> >>> wrote:
>> >>>>
>> >>>>
>> >>>>
>> >>>> On Tue, Nov 9, 2021 at 8:11 AM toni incog <toni.in...@gmail.com> wrote:
>> >>>>>
>> >>>>> fwiw That didn't work out. Symlinks where pointing to 3.9 though I
>> >>>>> stopped at  Failed to exec Python script file
>> >>>>> '/usr/pgadmin4/web/pgAdmin4.wsgi'... ModuleNotFoundError: No module
>> >>>>> named 'flask'
>> >>>>
>> >>>>
>> >>>> :-(.
>> >>>>
>> >>>>>
>> >>>>> I guess I've to practice some patience.
>> >>>>
>> >>>>
>> >>>> Yeah, unfortunately. The issue is that one of the upstream libraries we 
>> >>>> use doesn't have a release that supports Python 3.10 yet. We have all 
>> >>>> the build system etc. setup and ready to go, but until they put out a 
>> >>>> new release we're kinda stuck.
>> >>>>
>> >>>>>
>> >>>>>
>> >>>>> On Mon, 8 Nov 2021 at 10:01, toni incog <toni.in...@gmail.com> wrote:
>> >>>>> >
>> >>>>> > Ok, then I give that a try, thx!
>> >>>>> >
>> >>>>> > On Mon, 8 Nov 2021 at 09:56, Dave Page <dave.p...@enterprisedb.com> 
>> >>>>> > wrote:
>> >>>>> > >
>> >>>>> > >
>> >>>>> > >
>> >>>>> > > On Mon, Nov 8, 2021 at 8:34 AM Aditya Toshniwal 
>> >>>>> > > <aditya.toshni...@enterprisedb.com> wrote:
>> >>>>> > >>
>> >>>>> > >>
>> >>>>> > >>
>> >>>>> > >> On Mon, Nov 8, 2021 at 1:28 PM toni incog <toni.in...@gmail.com> 
>> >>>>> > >> wrote:
>> >>>>> > >>>
>> >>>>> > >>> No easy way to fallback to python 3.9 in f35? 3.9 is installable 
>> >>>>> > >>> fwiw
>> >>>>> > >>
>> >>>>> > >> I'm not aware of any. @Dave do you have any ?
>> >>>>> > >
>> >>>>> > >
>> >>>>> > > The F34 packages might work if you have 3.9 installed (I *think* 
>> >>>>> > > the symlinks in our venv should still point to the correct 
>> >>>>> > > locations in that case). There may be other things that don't work 
>> >>>>> > > though.
>> >>>>> > >
>> >>>>> > >>>
>> >>>>> > >>>
>> >>>>> > >>> On Mon, 8 Nov 2021 at 06:17, Aditya Toshniwal
>> >>>>> > >>> <aditya.toshni...@enterprisedb.com> wrote:
>> >>>>> > >>> >
>> >>>>> > >>> > Hi Toni,
>> >>>>> > >>> >
>> >>>>> > >>> > All of the python packages used by pgAdmin are not yet 
>> >>>>> > >>> > available for 3.10. We're continuously testing pgAdmin on 
>> >>>>> > >>> > v3.10 to make it work.
>> >>>>> > >>> > Once pgAdmin works on v3.10, F35 builds can be made available.
>> >>>>> > >>> >
>> >>>>> > >>> > On Sat, Nov 6, 2021 at 6:35 PM toni incog 
>> >>>>> > >>> > <toni.in...@gmail.com> wrote:
>> >>>>> > >>> >>
>> >>>>> > >>> >> No yum repos for f35 yet. Using the 34 repos has troubles 
>> >>>>> > >>> >> with f35
>> >>>>> > >>> >> python3.10. Any fast solution for this? Is installing 
>> >>>>> > >>> >> python3.9 an
>> >>>>> > >>> >> option. I'm not familiar with this pyhton world but became 
>> >>>>> > >>> >> dependend
>> >>>>> > >>> >> on pgadmin4.
>> >>>>> > >>> >>
>> >>>>> > >>> >> thx
>> >>>>> > >>> >>
>> >>>>> > >>> >>
>> >>>>> > >>> >
>> >>>>> > >>> >
>> >>>>> > >>> > --
>> >>>>> > >>> > Thanks,
>> >>>>> > >>> > Aditya Toshniwal
>> >>>>> > >>> > pgAdmin Hacker | Software Architect | edbpostgres.com
>> >>>>> > >>> > "Don't Complain about Heat, Plant a TREE"
>> >>>>> > >>
>> >>>>> > >>
>> >>>>> > >>
>> >>>>> > >> --
>> >>>>> > >> Thanks,
>> >>>>> > >> Aditya Toshniwal
>> >>>>> > >> pgAdmin Hacker | Software Architect | edbpostgres.com
>> >>>>> > >> "Don't Complain about Heat, Plant a TREE"
>> >>>>> > >
>> >>>>> > >
>> >>>>> > >
>> >>>>> > > --
>> >>>>> > > Dave Page
>> >>>>> > > VP, Chief Architect, Database Infrastructure
>> >>>>> > > Blog: https://www.enterprisedb.com/dave-page
>> >>>>> > > Twitter: @pgsnake
>> >>>>> > >
>> >>>>> > > EDB: https://www.enterprisedb.com
>> >>>>
>> >>>>
>> >>>>
>> >>>> --
>> >>>> Dave Page
>> >>>> VP, Chief Architect, Database Infrastructure
>> >>>> Blog: https://www.enterprisedb.com/dave-page
>> >>>> Twitter: @pgsnake
>> >>>>
>> >>>> EDB: https://www.enterprisedb.com
>> >>
>> >>
>> >>
>> >> --
>> >> Dave Page
>> >> VP, Chief Architect, Database Infrastructure
>> >> Blog: https://www.enterprisedb.com/dave-page
>> >> Twitter: @pgsnake
>> >>
>> >> EDB: https://www.enterprisedb.com
>
>
>
> --
> Dave Page
> VP, Chief Architect, Database Infrastructure
> Blog: https://www.enterprisedb.com/dave-page
> Twitter: @pgsnake
>
> EDB: https://www.enterprisedb.com


Reply via email to