Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • 21:52
    Irvise opened #585
  • 21:35
    Irvise opened #584
  • 21:05
    mosteo opened #583
  • 19:22
    mosteo opened #582
  • 19:13
    mosteo commented #189
  • 19:13

    mosteo on stable-0.4

    GTKAda 21.0.0 (#189) * GTKAda … (compare)

  • 19:13
    mosteo closed #189
  • 15:24
    Fabien-Chouteau synchronize #189
  • 14:59
    Fabien-Chouteau synchronize #189
  • 14:57
    Fabien-Chouteau synchronize #189
  • 14:01

    mosteo on stable-0.4

    GNATcoll db change GitHub relea… (compare)

  • 14:01
    mosteo closed #195
  • 14:01

    mosteo on stable-0.4

    GNATcoll bindings change GitHub… (compare)

  • 14:01
    mosteo closed #194
  • 13:06
    Fabien-Chouteau commented #194
  • 13:02
    mosteo commented #194
  • 12:50

    mosteo on stable-0.4

    gnatcoll change GitHub release … (compare)

  • 12:50
    mosteo closed #193
  • 12:49

    mosteo on stable-0.4

    libgpr change GitHub release UR… (compare)

  • 12:49
    mosteo closed #192
Maxim Reznik
@reznikmm
Perhaps I copied it from https://github.com/alire-project/alire-index/blob/9b1c1cc5840a6ceeeec1a253f316da934c7c40e3/index/sd/sdlada/sdlada-2.3.1.toml#L36 
[gpr-set-externals]
SDL_MODE = "release"
Fabien Chouteau
@Fabien-Chouteau
Maybe. It is different for sdlada because the SDL_MODE is not comon to many different gpr.
Maxim Reznik
@reznikmm
the same issue with utilada-2.1.0.toml
[gpr-set-externals]
BUILD = "distrib"
UTIL_LIBRARY_TYPE = "static"
and gnatcoll
Maxim Reznik
@reznikmm
I'm also not quite understand a new publishing instruction. It says alire.toml should be in the project repository and that alire.toml should contain commit id. But I don't know commit id until I commit alire.toml.
Fabien Chouteau
@Fabien-Chouteau
In your repo you can keep alire.toml but without any release origin info, e.g.:https://github.com/Fabien-Chouteau/samd51-hal/blob/master/alire.toml
Once you are ready to release, make sure that the version in alire.toml is correct, if not change it an check in the change.
Then do alr publish.
Alejandro R Mosteo
@mosteo
@reznikmm those might be necessary if the gpr does not provide a default, in which case we're back to your first question on how to override it. I have not checked though.
Maxim Reznik
@reznikmm
btw we have 100 crates according to https://alire.ada.dev/crates.html
Alejandro R Mosteo
@mosteo
not bad! you have like 20% of responsibility :laughing:
repo.msys2.org seems to be down
Maxim Reznik
@reznikmm
Trying to publish with alr publish
Fabien Chouteau
@Fabien-Chouteau
Looks like the build failed
What does alr buildtells you?
Maxim Reznik
@reznikmm
Missing dependencies. Thank you Fabuen for explanation. I didn't know I can run alr build there :)
Maxim Reznik
@reznikmm
Now it works! Almost:
Publishing assistant: step 5 of 5: Generate index manifest
✓ Your index manifest file has been generated at /tmp/axmpp/alire/releases/axmpp-1.0.0.toml
✓ Please upload this file to https://github.com/alire-project/alire-index/upload/devel-0.4/index/ax/axmpp to create a pull request against the community index.

On the site:

Uploads are disabled.
File uploads require push access to this repository.

Fabien Chouteau
@Fabien-Chouteau
Nooooooo :(
Thank you for the report Maxim, we thought anyone could open a pull request like that...
Alejandro R Mosteo
@mosteo
may be it's a matter of configuring permissions? let me check
"Anyone with read permissions to a repository can create a pull request, but you must have write permissions to create a branch."
Maxim Reznik
@reznikmm
What i did: I replaced alire-project with reznikmm in the URL and it created a branch in my fork. Then I made a PR.
Alejandro R Mosteo
@mosteo
we'll have to rethink this one. the simplest change rn may be to use the user github login to provide the upload to their fork, as you did
the only problem is that the base branch has to already exist in the fork, or it redirects to an error
also, it defaults to use the fork as the base for the PR...
timlag1305
@timlag1305
I wanted to try using Alire on a pet project of mine. I ran into issues compilation errors when building gnatcoll dependency that I withed to my project. I noticed that it's stuck on the 2019 version. I'm not sure if that's causing the issue. For what it's worth, I am running on linux with gcc 10.2.0 (with gnat) and gnatcoll-core 2020 installed system-wide. Is there a fix for this? I can provide compilation errors that I'm seeing. Also if it's easier, could I just depend on my system-wide installation of gnatcoll for testing purposes? I saw alr with --path but I think it only works when --path points to a crate, not a generic install of a library using gprinstall.
Maxim Reznik
@reznikmm
@timlag1305 What error do you have?
Fabien Chouteau
@Fabien-Chouteau
@timlag1305 Alire will use the latest available version in the index first. So the 2019 in the index is used.
Note that we will add a more recent version gnatcoll in Alire very soon as we prepare for the BETA release of Alire.
timlag1305
@timlag1305
@reznikmm this is the error I see.
gnatcoll-traces.adb:1084:35: implicit conversion of anonymous access formal not allowed
gnatcoll-traces.adb:1182:58: implicit conversion of anonymous access formal not allowed
gnatcoll-traces.adb:1246:60: implicit conversion of anonymous access formal not allowed
gnatcoll-traces.adb:1310:38: implicit conversion of anonymous access formal not allowed
gnatcoll-traces.adb:1544:24: implicit conversion of anonymous access formal not allowed
gnatcoll-traces.adb:1084:35: implicit conversion of anonymous access formal not allowed
gnatcoll-traces.adb:1182:58: implicit conversion of anonymous access formal not allowed
gnatcoll-traces.adb:1246:60: implicit conversion of anonymous access formal not allowed
gnatcoll-traces.adb:1310:38: implicit conversion of anonymous access formal not allowed
gnatcoll-traces.adb:1544:24: implicit conversion of anonymous access formal not allowed
gnatcoll-projects.adb:7949:13: ambiguous expression (cannot resolve "Starts_With")
gnatcoll-projects.adb:7949:13: possible interpretation at gpr-util.ads:394
gnatcoll-projects.adb:7949:13: possible interpretation at gnatcoll-utils.ads:122
gnatcoll-projects.adb:7952:16: ambiguous expression (cannot resolve "Starts_With")
gnatcoll-projects.adb:7952:16: possible interpretation at gpr-util.ads:394
gnatcoll-projects.adb:7952:16: possible interpretation at gnatcoll-utils.ads:122
gnatcoll-projects.adb:7955:16: ambiguous expression (cannot resolve "Starts_With")
gnatcoll-projects.adb:7955:16: possible interpretation at gpr-util.ads:394
gnatcoll-projects.adb:7955:16: possible interpretation at gnatcoll-utils.ads:122
gnatcoll-projects.adb:8812:34: "Source_File" is not a visible entity of "Sinput"
gnatcoll-projects.adb:9010:51: "Source_File" is not a visible entity of "Sinput"
gnatcoll-projects.adb:9011:26: "Source_File" is not a visible entity of "Sinput"
gnatcoll-projects.adb:9013:17: "Source_File" is not a visible entity of "Sinput"
gnatcoll-projects.adb:7949:13: ambiguous expression (cannot resolve "Starts_With")
gnatcoll-projects.adb:7949:13: possible interpretation at gpr-util.ads:394
gnatcoll-projects.adb:7949:13: possible interpretation at gnatcoll-utils.ads:122
gnatcoll-projects.adb:7952:16: ambiguous expression (cannot resolve "Starts_With")
gnatcoll-projects.adb:7952:16: possible interpretation at gpr-util.ads:394
gnatcoll-projects.adb:7952:16: possible interpretation at gnatcoll-utils.ads:122
gnatcoll-projects.adb:7955:16: ambiguous expression (cannot resolve "Starts_With")
gnatcoll-projects.adb:7955:16: possible interpretation at gpr-util.ads:394
gnatcoll-projects.adb:7955:16: possible interpretation at gnatcoll-utils.ads:122
gnatcoll-projects.adb:8812:34: "Source_File" is not a visible entity of "Sinput"
gnatcoll-projects.adb:9010:51: "Source_File" is not a visible entity of "Sinput"
gnatcoll-projects.adb:9011:26: "Source_File" is not a visible entity of "Sinput"
gnatcoll-projects.adb:9013:17: "Source_File" is not a visible entity of "Sinput"
gnatcoll-projects.adb:7949:13: ambiguous expression (cannot resolve "Starts_With")
gnatcoll-projects.adb:7949:13: possible interpretation at gpr-util.ads:394
gnatcoll-projects.adb:7949:13: possible interpretation at gnatcoll-utils.ads:122
gnatcoll-projects.adb:7952:16: ambiguous expression (cannot resolve "Starts_With")
gnatcoll-projects.adb:7952:16: possible interpretation at gpr-util.ads:394
gnatcoll-projects.adb:7952:16: possible interpretation at gnatcoll-utils.ads:122
gnatcoll-projects.adb:7955:16: ambiguous expression (cannot resolve "Starts_With")
gnatcoll-projects.adb:7955:16: possible interpretation at gpr-util.ads:394
gnatcoll-projects.adb:7955:16: possible interpretation at gnatcoll-utils.ads:122
gnatcoll-projects.adb:8812:34: "Source_File" is not a visible entity of "Sinput"
gnatcoll-projects.adb:9010:51: "Source_File" is not a visible entity of "Sinput"
gnatcoll-projects.adb:9011:26: "Source_File" is not a visible entity of "Sinput"
gnatcoll-projects.adb:9013:17: "Source_File" is not a visible entity of "Sinput"
gnatcoll-projects.adb:7949:13: ambiguous expression (cannot resolve "Starts_With")
gnatcoll-projects.adb:7949:13: possible interpretation at gpr-util.ads:394
gnatcoll-projects.adb:7949:13: possible interpretation at gnatcoll-utils.ads:122
gnatcoll-projects.adb:7952:16: ambiguous expression (cannot resolve "Starts_With")
gnatcoll-projects.adb:7952:16: possible interpretation at gpr-util.ads:394
gnatcoll-projects.adb:7952:16: possible interpretation at gnatcoll-utils.ads:122
gnatcoll-projects.adb:7955:16: ambiguous expression (cannot resolve "Starts_With")
gnatcoll-projects.adb:7955:16: possible interpretation at gpr-util.ads:394
gnatcoll-projects.adb:7955:16: possible interpretation at gnatcoll-utils.ads:122
gnatcoll-projects.adb:8812:34: "Source_File" is not a visible entity of "Sinput"
gnatcoll-projects.adb:9010:51: "Source_File" is not a visible entity of "Sinput"
gnatcoll-projects.adb:9011:26: "Source_File" is not a visible entity of "Sinput"
gnatcoll-projects.adb:9013:17: "Source_File" is not a visible entity of "Sinput"
gnatcoll-projects.adb:7949:13: ambiguous expression (cannot resolve "Starts_With")
gnatcoll-projects.adb:7949:13: possible interpretation at gpr-util.ads:394
gnatcoll-projects.adb:7949:13: possible interpretation at gnatcoll-utils.ads:122
gnatcoll-projects.adb:7952:16: ambiguous expression (cannot resolve "Starts_With")
gnatcoll-projects.adb:7952:16: possible interpretation at gpr-util.ads:394
gnatcoll-projects.adb:7952:16: possible interpretation at gnatcoll-utils.ads:122
gnatcoll-projects.adb:7955:16: ambiguous expression (cannot resolve "Starts_With")
gnatcoll-projects.adb:7955:16: possible interpretation at gpr-util.ads:394
gnatcoll-projects.adb:7955:16: possible interpretation at gnatcoll-utils.ads:122
gnatcoll-projects.adb:8812:34: "Source_File" is not a visible entity of "Sinput"
gnatcoll-projects.adb:9010:51: "Source_File" is not a visible entity of "Sinput"
gnatcoll-projects.adb:9011:26: "Source_File" is not a visible entity of "Sinput"
gnatcoll-projects.adb:9013:17: "Source_File" is not a visible entity of "Sinput"

   compilation of gnatcoll-traces.adb failed
   compilation of gnatcoll-scripts-projects.adb failed
   compilation of gnatcoll-scripts-impl.adb failed
   compilation of gnatcoll-projects-normalize.adb failed
   compilation of gnatcoll-projects.adb failed
   compilation of gnatcoll-projects-aux.adb failed
Thanks for the clarification @Fabien-Chouteau
Alejandro R Mosteo
@mosteo
@timlag1305, as a temporary workaround, you can remove the gnatcoll dependency from your crate and your compiler will use the system-wide one.
or, you could check with alr search gnatcoll --external-detect the exact version of the system gnatcoll, and force that version. Assuming you're on Ubuntu or Debian, where the system gnatcoll should be detected.
Alejandro R Mosteo
@mosteo
add --full to that last incantation, sorry
Fabien Chouteau
@Fabien-Chouteau
alire.ada.dev is now listing crates from the latest stable alr release (using the setup-alire@latest-stable github action).
timlag1305
@timlag1305
Thanks @mosteo
Vinzent "Jellix" Saranen
@Jellix
I figured, I'll try the alr publish, after fixing some obvious issues with my understanding how it all works, I am now getting
info: Publishing assistant: step 5 of 6: User review
stderr: SYSTEM.ASSERTIONS.ASSERT_FAILURE
stderr: failed precondition from alire-publish.adb:456
stderr: raised SYSTEM.ASSERTIONS.ASSERT_FAILURE : failed precondition from alire-publish.adb:456
[/opt/GNAT/2020/bin/alr]
System.Assertions.Raise_Assert_Failure at s-assert.adb:46
Alire.Publish.Show_And_Confirm at alire-publish.adb:456
Alire.Publish.Start_At at alire-publish.adb:722
Alire.Publish.Remote_Origin at alire-publish.adb:880
Alr.Commands.Publish.Execute at alr-commands-publish.adb:76
Alr.Commands.Execute_By_Name at alr-commands.adb:743
Alr.Commands.Execute at alr-commands.adb:713
Alr.Main at alr-main.adb:28
Main at b__alr-main.adb:1851
[/lib/x86_64-linux-gnu/libc.so.6]
0x7f589a3980b1
[/opt/GNAT/2020/bin/alr]
0x43057c _start at ???
0xfffffffffffffffe
Any ideas what's missing? Looking at the source code where the assertion fails, a call to Is_Regular_File fails.
Vinzent "Jellix" Saranen
@Jellix
Ok, I know what was wrong. The alire.toml was missing. I created it locally, but didn't push it to the remote which I intended to publish.

Now I'm getting

error: Could not complete the publishing assistant:
error: GitHub API rate limit exceeded, please wait for a while before retrying.

Alejandro R Mosteo
@mosteo
Hi Vinzent. For unauthenticated users, the github API has a limit of 60 requests per hour. Sounds about right? I guess you could hit it if you did a lot of trials
Vinzent "Jellix" Saranen
@Jellix
I guess I did, :) meanwhile I'm out of cool down, everything's peachy.
Alejandro R Mosteo
@mosteo
In regard to the previous error, you should have been notified that your remote repo was behind your local one... I guess I'll have more questions for you once I try to reproduce it.
Unless your alire.toml was not added to git...
Vinzent "Jellix" Saranen
@Jellix
It wasn't added. I just copied it from the original alire-index and adjusted it manually (hence the rate limit). So yes, as mentioned in the issue, a hopefully rare occurence.
Alejandro R Mosteo
@mosteo
Rare but one that I thought we were checking. Oh well, that's what betas are for