msys2/msys2

also on Discord: https://discord.gg/jPQdRdDcT9

Ray Donnelly

@mingwandroid

But it installs really old packages so we need to fix that (both my company and conda-forge, the open source community effort who are our upstream).

umarcor

@umarcor

By looking at https://anaconda.org/search?q=m2-, essentially all the MSYS2 packages were "wrapped" 4 years ago?

So, you were not referring a manual procedure, but to something similar to MSYS2 autobuilder which would generate Conda m2- packages, isn't it?

Ray Donnelly

@mingwandroid

Something automatic yes. We call it binary-repackaged at my place but yes, wrapped works too.

We'd prefer from source builds of the PKGBUILDs inside the conda recipe to repackaging.

Christopher Degawa

@1480c1

I just realized something that might be something I have a problem against, in the start menu, msys2 shows up as MSYS2 MinGW {64,32}-bit referring to MinGW instead of mingw-w64

along with the MSYS2 MSYS one since technically msys also is from MinGW

Ray Donnelly

@mingwandroid

Yeah, we should fix that IMHO.

Christoph Reiter

@lazka

it refers to the msys2 subsystem

David Macek

@elieux

Then maybe it should be called the same as inside (and everywhere else).

Christoph Reiter

@lazka

yeah

Алексей

@Alexpux

@lazka @elieux I se that some updatea are go to repo but some not

what the reason for it?

Christoph Reiter

@lazka

@Alexpux some failed, others are waiting for those

@Alexpux I'll improve all this shortly

sadly busy at work atm

Алексей

@Alexpux

Christoph Reiter

@lazka

python3 autobuild.py fetch-assets --verbose --pretend _bla shows you why

I'll integrate this information into the website

summary: for a package to be downloadable all its dependencies and reverse dependencies in the queue need to be finished.

Алексей

@Alexpux

python3 autobuild.py fetch-assets --verbose --pretend _bla shows you why

I dont understand output of this command

Алексей

@Alexpux

@dscho there are problems with symlinks in current msys2 runtime

Johannes Schindelin

@dscho

@dscho there are problems with symlinks in current msys2 runtime

What exactly do you want to tell me?
What exactly do you want me to do about it?

Christoph Reiter

@lazka

@Alexpux that's ok. I'll improve things

Christoph Reiter

@lazka

@Alexpux the information is now in the "Status" column here: https://packages.msys2.org/queue

I'll work on the manual package upload next

David Macek

@elieux

What do you mean?

Christoph Reiter

@lazka

hm?

David Macek

@elieux

... by manual package upload.

Christoph Reiter

@lazka

@elieux oh. I was planning to have a "autobuild.py upload-assets" command so alexey can upload some packages CI can't handle.

David Macek

@elieux

Oh. Cool.

umarcor

@umarcor

the information is now in the "Status" column here: https://packages.msys2.org/queue

@lazka, thank you so much!

Christoph Reiter

@lazka

@Alexpux msys2/msys2-autobuild@4daf82d

h-c-mueller

@h-c-mueller

Can you please rebuild mingw-w64-*-python. Issue msys2/MINGW-packages#7681 is closed with msys2/MINGW-packages#7686, but git version 3.8.7-3 is not available as package.

Naveen M K

@naveen521kk

It doesn't need a rebuild. It is just waiting for people to sign and upload. I think @elieux is in-charge of signing and upliading things...

h-c-mueller

@h-c-mueller

@naveen521kk thanks for the clarification.

David Macek

@elieux

It's waiting for related packages.

 ('mingw-w64-python',
  'mingw64',
  {'desc': 'waiting on mingw-w64-python-oslo-serialization, '
           'mingw-w64-audaspace, mingw-w64-python-numexpr, '
           'mingw-w64-python-markdown, mingw-w64-python-lxml, '
           'mingw-w64-python-oslo-context, mingw-w64-python-mock, '
           'mingw-w64-python-oslo-concurrency, mingw-w64-python-oslo-db, '
           'mingw-w64-python-oslo-i18n, mingw-w64-python-mako, '
           'mingw-w64-python-cx_Freeze, mingw-w64-python-oslotest, '
           'mingw-w64-python-oslo-log, mingw-w64-python-numba'}),

@h-c-mueller

h-c-mueller

@h-c-mueller

@elieux thanks for the information.

David Macek

@elieux

Should be uploaded soon.

bladee drain gang

@bleedingfrmmyeyez_gitlab

peniss

so yall kno where i can cop sum fentanyl

feeling like peep rn ong

umarcor

@umarcor

Can someone help with customising a qmake *.pro file for supporting MSYS2?

Biswapriyo Nath

@Biswa96

@umarcor I am not familiar with Qt. But I was compiling OpenRGB project in msys2. Here https://gitlab.com/CalcProgrammer1/OpenRGB/-/blob/master/OpenRGB.pro. Typically you don't need anything special for msys2 in a project. If you require anything specific for msys2 look at the main cause of that requirement.

umarcor

@umarcor

@Biswa96, please see https://github.com/Serial-Studio/Serial-Studio/issues/6#issuecomment-770159176

The tool is already an MSYS2 package, but package is done "manually": https://github.com/msys2/MINGW-packages/blob/master/mingw-w64-serial-studio/PKGBUILD#L36-L37

The purpose is to use make install instead. However, it is being difficult for qmake and make to understand PREFIX and DESTDIR.

Precisely, pkgdir is not defined when qmake is executed in the build() step of the PKGBUILD recipe.

Where communities thrive

People

Repo info

Activity