Dear experimented Ada library packagers…
Ludovic's gtkada packaging passes the -V option to dh_makeshlibs(1). I
guess this is motivated, but I hardly imagine in which scenario. Worst, the
manpage describes a potential problem with excessive use of this option.
If -V is needed, we should mention
Hello.
Ludovic has uploaded libxmlada4.1-dev (depending on gnat-4.6). The previous
version was libxmlada3.2-dev (depending on gnat-4.4). It seems that he has
forgotten to make the package conflict/replace the previous version.
However, I suggest that we relax the policy (in the Coexistence not
On Thu, Sep 08, 2011 at 08:54:21AM +0200, Ludovic Brenta wrote:
I propose the following small change to the Debian Policy for Ada:
--- debian-ada-policy.texi
+++ debian-ada-policy.texi
@@ -1119,7 +1118,14 @@ @subsection Avoiding the indirect FTBFS
it is necessary that the package
Hello.
It seems that this migration to 4.6 is the occasion to update our packages
to multiarch, as described in
http://wiki.debian.org/Multiarch/Implementation
Let me attempt to summarize the needed changes, maybe to prepare a policy
modification.
Supporting multi-arch is specific to
On Mon, Sep 26, 2011 at 07:37:17AM -0400, Stephen Leake wrote:
Proposed rule:
If a binary package build-depends on gnat (ie, it is an Ada
package), and the package name changes only by incrementing a number
(ie it is an aliversion change [ref debian ada policy]), then it is
On Tue, Sep 27, 2011 at 11:41:04AM -0400, Stephen Leake wrote:
Any maintainer can make his package Build-Depend on gnat, or imitate
a shared library to fake whatever automatic test I can imagine.
I think you are implying that Bad Things Can Happen if this rule is
accepted; can you be
Dear Ada packagers...
Gnat uses trampolines to handle exceptions, this sometimes triggers a
lintian warning about executable stack. So an Ada library package may
need a lintian override file like the following.
/usr/share/lintian/overrides/$(package)
--
# GNAT uses trampolines for Ada
Hello.
I got the following message from lintian for a library devel package.
N: Processing binary package libgmpada3-dev (version 0.0.20110925-2, arch
amd64) ...
W: libgmpada3-dev: virtual-package-depends-without-real-package-depends
depends: ada-compiler
N:
N:The package declares a
On Thu, Nov 24, 2011 at 11:40:10PM +0100, Ludovic Brenta wrote:
I think
Depends: gnat-x.y | ada-compiler
would be even better. Note that lintian says: depends on a virtual
package without listing a real package as an alternative first.
Alternatives are separated by | in Depends and
On Thu, Nov 17, 2011 at 03:07:03PM +, Ludovic Brenta wrote:
Nicolas, would you have time to write at least a one-page description of
ALDH for the novice packager, as an appendix in the Debian Policy for
Ada? That would make it possible for more packagers to consider using
it the next time
Hello.
The debian-ada-policy says that the libfoo package should provide the
/usr/share/ada/adainclude/foo.gpr GNAT project file, mentioning the
right path to Library_Dir and Library_ALI_Dir. These path depend on
the current architecture (/usr/lib/DEB_HOST_MULTIARCH and
Hello.
As far as I know, the current practice for a package providing a
library depending on another library is to mention the linker options
in the *build* project, say for example
for Library_Options use (-Wl,--as-needed, -lgmp, -lmpfr);
but not to mention them in the *installed* project. I
Hello.
If foo is a symlink targeting foo, GNAT's implementation of
Ada.Directories.Full_Name (foo) returns .
System.OS_Lib.Normalize_Pathname body ends with:
-- Too many iterations: give up
-- This can happen when there is a circularity in the symbolic links: A
-- is a symbolic link for B,
Interesting.
I tryed to summarize the thread in
f6903e3b1cc3b2c189c8613389b50df6764c9c32.
--
To UNSUBSCRIBE, email to debian-ada-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120308174404.GA16013@pegase
Hello.
(This should only concern library packagers.)
I am interested in writing a native package providing a program in the
Debian helper style, named dh_ada_library.
To respect Debian helper tradition,
* it could be run directly or inserted in the dh sequence
by adding --with ada-library to
I would suggest a name less generic than directories.gpr. An end-user
may, for very similar reasons, have a project named directories.gpr in
the current directory, and this would cause obscure errors. Something
like system_library_directories.gpr?
Now that you've implemented dh-ada-library, it
On Tue, Jun 26, 2012 at 01:08:13PM +0200, Xavier Grave wrote:
One concern I have is that I'm using po_gnatdist tool to build
distributed application, I'll have to sort out if it rely on gnatmake or
gprbuild (command line shows gnat compile and gnat make)
On Fri, Sep 21, 2012 at 11:45:32AM +0200, Xavier Grave wrote:
As far as I remember the Breaks/Replace libpolyorb2 by libpolyorb3
isn't an option ?
Imagine
exe2 is linked to libpolyorb2
exe3 is linked to libpolyorb3
Breaks/Replace would unexpectedly make those executables not
coinstallable. I
[in addition to Ludovic's links]
If you are completely new to Ada, you may be interested in
http://en.wikibooks.org/wiki/Ada_Programming
http://www.adahome.com/FAQ/learning.html#tutorials
If you are completely new to Debian, you may be interested in
On Mon, Jul 15, 2013 at 07:19:23PM +0200, Florian Weimer wrote:
Did you mean to write GFDL instead of GPL somewhere?
You are right, of course. Thanks.
- a verbatim copy of GPL-1 at the end of the manual
Here, read GFDL instead of GPL-1.
--
To UNSUBSCRIBE, email to
On Mon, Jul 15, 2013 at 09:13:26PM +0200, Florian Weimer wrote:
- a verbatim copy of GPL-1 at the end of the manual
Here, read GFDL instead of GPL-1.
And what are the invariant sections and cover texts?
If there are none, non-free isn't necessary.
Here is an extract from the *current*
https://lists.debian.org/debian-ada/2013/04/msg1.html
Any news about this?
--
To UNSUBSCRIBE, email to debian-ada-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/2013083513.GA12195@pegase
Libgtkada source products two packages. Among them:
libgtkadagl$(GTK_GL_ALI_VERSION)-dev
libgtkada$(GTK_ALI_VERSIOn)-dev
Currently, the former Depends: the latter (= common Debian binary version).
Maybe the version restriction is not needed. Any binary package with
the right GTK_ALI_VERSION
Unless I miss something in the current policy for Ada packages,
http://people.debian.org/~lbrenta/debian-ada-policy.html
the scenario coexistence allowed for library foo is the same than
the scenario coexistence not allowed for library foo4, except that:
- the dev package is named libfoo4-dev,
With the gnat-4.8 transition, we may consider changing the policy for
-dev packages to avoid architecture-dependent contents in /usr/share/.
You may want to (re-)read Björn's idea about projects [π], the
discussion about arch-dependent sources ([√2] and same thread next
month [i]), or the wiki
On Sun, Nov 10, 2013 at 01:10:37PM +0100, Ludovic Brenta wrote:
Nicolas Boulenguez writes:
the scenario coexistence allowed for library foo is the same than
the scenario coexistence not allowed for library foo4, except that:
- the dev package is named libfoo4-dev, not libfoo4-V-dev
On 2013-11-28, Nicolas Boulenguez wrote:
I am interested in sponsoring the GHDL package, but will not have time
for this before two weeks.
On Wed, Jan 15, 2014 at 09:14:46PM +0100, Joris van Rantwijk wrote:
Are you still interested in sponsoring the GHDL package for Debian?
Sorry
On Mon, Feb 10, 2014 at 05:42:30PM +0100, Svante Signell wrote:
Hi, where can I download it? It might be worth the effort to make it
compile on Debian GNU/Hurd too.
I believe this should be enough.
# mtn clone mtn://www.ada-france.org?org.debian.gnat-4-6
Download may be quite long.
Some of the
Hello.
Congratulations, head of the gnat-4.9 branch builds on amd64!
Here is a survey covering most of the bugs reported against gnat-4.y.
Most of them persist in 4.9: 244936, 244970, 246183, 246187, 247013,
247017, 247018, 247019, 247569, 247570, 247571, 248166, 248168,
248678, 248680, 248681,
On Fri, Feb 21, 2014 at 03:25:26PM +0100, Xavier Grave wrote:
Although I have this in my gnatmake command line: -Wl,-z,relro I
still have this lintian warning and get back at [3] with
hardening-no-relro
[3] https://lists.debian.org/debian-ada/2012/05/msg00016.html
# /usr/bin/hardening-check
Hello. I would like some advices about...
Xmlada produces 5 libraries: xmlada_$module for $module in dom,
input_sources, unicode, sax and schema. This makes sense, because SAX
users may not want to [load in memory|statically embed] the DOM part,
or may want to use the unicode module only.
Former
Hello. Because of the migration from gtk2 to gtk3, we have to select
a gtkada version for next release.
The adacore download site provides
- gtkada 3.4.2.
- gps 5.2.1 relying on gtkada 2.24.3.
On their respective VCS
- gnat-gps not-yet-6.1.0 relies on gtkada 2.24.5 or later.
- gtkada
@@ -5,7 +5,7 @@ Author: Nicolas Boulenguez nicolas@debi
--- a/src/misc.c
+++ b/src/misc.c
-@@ -407,7 +407,7 @@
+@@ -235,7 +235,7 @@
GLogLevelFlags log_level,
const gchar*format)
{
@@ -14,38 +14,3 @@ Author: Nicolas Boulenguez nicolas@debi
}
void
-@@ -4161,14 +4161,14
Follow-up for https://lists.debian.org/debian-ada/2014/03/msg00017.html.
I wrote:
If libbar depends on libfoo, -lfoo must be given both when linking
libbar and later when linking an executable with libbar.
and was proven wrong by Björn. In normal circumstances, if (dynamic)
libbar is linked
On Wed, Apr 30, 2014 at 01:42:42PM +0100, Ludovic Brenta wrote:
xavier grave wrote:
In the Holy Debian Ada Policy [1] it is stated that
Rule: The project file SHALL have
/usr/share/ada/adainclude/LIBRARY.
a Library_Kind attribute equal to ‘dynamic’.
I'm wondering if the Library_Kind
On Sun, Aug 17, 2014 at 03:09:42PM +0200, Eugen Wintersberger wrote:
I have a problem with gprbuild on Jessie. When using gprbuild with
gnat-4.9 installed I get the following warning message
warning: no compiler specified for language Ada, ignoring all its sources
Is this a bug in the
On Sun, Aug 17, 2014 at 09:05:51PM +0200, Eugen Wintersberger wrote:
According to
http://en.wikibooks.org/wiki/Ada_Programming/Installing
gnat-4.6 should provide full support for Ada 2012.
As far as I remember, -gnat12 support was not complete in 4.6.
However, things like
for e in vector
Hello.
May I suggest you to read this document carefully next time you
prepare a non-maintainer upload?
https://www.debian.org/doc/manuals/developers-reference/pkgs.html#nmu-guidelines
Your NMU for apq fixes a FTBFS by removing an explicit GNAT version
from the build dependencies.
On Tue, Sep 23, 2014 at 03:27:41PM -0500, Stephen Leake wrote:
I'm preparing the next release of the Emacs ada-mode ELPA package, and
I'm wondering whether to include the Ada Reference Manual (ARM) in info
format.
The ARM is available as a Debian package, so including it in the ELPA
package
Hello.
We are packaging some of the software available at
http://libre.adacore.com/download/configurations
for the Debian distribution, and would like some clarification about a
license issue. The issue has been detected for ASIS, but probably
affects other packages as well.
The second
For the record, li...@adacore.com does not exist anymore.
I have filled the contact form in the web page.
--
To UNSUBSCRIBE, email to debian-ada-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive:
On Mon, Oct 06, 2014 at 06:05:41PM +0200, Ludovic Brenta wrote:
The packages are not migrating to testing despite the 10-day delay
being long expired. I believe this is due to the renaming of binary
packages. Has apq gone through the NEW queue?
Both passed the NEW queue, then failed to build
On Mon, Oct 06, 2014 at 06:35:08PM +0200, Ludovic Brenta wrote:
That's sad but apparently unavoidable. What is the link between
postgresql and OpenSSL? Is there no way to use postgresql (libpq)
without OpenSSL?
A pessimistic summary is available at
http://lwn.net/Articles/428111/
I ignore if
Dear collective wisdom,
the following source (originating in opentoken-6.0a-1) is
- rejected by gcc-4.9,
- accepted by GNAT-GPL-2014 and GNAT-Pro-7.3.1.
Is it valid Ada 2012?
package P is
A : access constant Integer;
procedure P (I : aliased in Integer);
end P;
package body P is
Hello.
I have added the following suggestion in debian-ada-policy. Feel free
to comment or disapprove before anything is published.
Recommendation: If an Ada source is patched, preprocessed, generated or
otherwise modified during the build process, its modification time
should be enforced to
Package: gnat-5
Version: 5.2.1-22
Severity: wishlist
Hello.
The symbolic link
/usr/bin/gnatgcc -> gcc-x.y
installed by package gnat-x.y used to help mixing Ada and C code,
/usr/bin/gnatgcc version being compatible with gnat, and sometimes
different from /usr/bin/gcc version.
In gnat-5, the
Hello.
One day in the near future, all -dbg packages should be generated
automatically after upload [2]. The Ada policy may then forget
everything about -dbg packages.
For now, we distribute an unstripped static archive with each Ada
library. A new lintian tag [1] seems to show that we should
Hello.
Policy mandates that packaged library projects live in
/usr/share/ada/adainclude.
Ludovic has stated many times that this choice was quite arbitrary,
and could be modified if necessary.
Now, gprbuild and gprinstall hardcode /usr/share/gpr. I am patching
them to also accept our path for a
> OK if /usr/share/gpr is not also used by another Debian package.
There would already have been a conflict. Gprbuild has been installing
its implicit project /usr/share/gpr/_default.gpr there for a while.
> And for one release cycle we'll want to make a symlink from the old
> path to the new
Hello.
The gnat (= 5), libxmlada, gprbuild and dh-ada-library source packages
now build with gnat-5.
If they are uploaded to unstable, they will make most other packages
FTBFS during the migration again, and any fix targeting testing will
have to go through testing-proposed-updates.
It may be
Hello.
My explanation was wrong, there is a new victim (libaws).
However, if recompiling libraries and packages without changing ALI
versions in Build-Dependencies removes the error, then a library
somewhere is probably breaking the Ada policy by silently changing the
contents of its Ada
Hello.
I would welcome help or advices about a tricky problem with gnat-gps,
the (hopefully) last key step in the gnat-6 migration.
The current packaging in the monotone server builds GPS-6.1.1 (aka
GPL-2015, not GPL-2016). You will need to manually download and repack
the sources from the
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu
Hello.
Every package containing an Ada library embeds checksums of its
recursive dependencies, in files suffixed with .ali. Everytime
something attempts to build against the library, gcc
Hello.
Most Ada packages are released once a year, around the summer. Our
roadmap is to do only one transition in unstable, involving gnat-6 and
version 2016 of these packages.
In order to prepare that incrementally, we have started working on
version 2015 in experimental. The already updated
Hello.
I suggest the attached update to the policy, now that debhelper
handles packages containing debug symbols.
https://lists.debian.org/debian-devel/2015/12/msg00262.html
--- debian-ada-policy.texi 624fca334250dca52abf31fd163833c439630a81
+++ debian-ada-policy.texi
Hello.
The experimental distribution seems a right place for gnat
migrations. For example, #818416 has been fixed in unstable/testing,
preventing the removal of templates-parser reverse dependencies.
The gcc-6 source package stil builds libgnatvsn and libgnatprj, so few
changes seem necessary
Hello.
The new resolver on experimental buildds fails to install gnat-6 (even
from unstable), so I have started the migration in unstable.
Sooner or later, libgnatprj will be produced by gprbuild instead of
GCC. In order to avoid circular dependencies, XMLAda and GPRBuild now
build without
Hello.
Now that gnat Depends: gnat-6, and to the extent of my knowledge, all
Ada packages
- either have migrated to gnat-6
- or should only require a recompilation request:
spark
- or fail to build because they Build-Depend: gnat, gnat-4.9:
adabrowse
adacgi
adasockets
ahven
anet
> Nicolas Boulenguez wrote:
> >Now that gnat Depends: gnat-6, and to the extent of my knowledge, all Ada
> >packages
> >- either have migrated to gnat-6
> >- or should only require a recompilation request:
> >- or fail to build because they Build-Depend: gnat
On Thu, Aug 04, 2016 at 10:03:00PM +0200, Jacob Sparre Andersen wrote:
> I've installed "asis-programs" in my "sid" chroot. It appears that the
> "gnatmetric" tool has been removed from the package, except for a few
> architectures:
>
>
Source: gcc-6
Package: gnat-6
Version: 6.3.0-4
Followup-For: Bug #839209
Hello.
gcc Depends: gcc-6, and they provide the following /usr/bin symlinks.
gcc: gcc-> gcc-6
gcc: ARCH-gcc-> gcc-6
gcc-6 : gcc-6 -> ARCH-gcc-6
For gnat-6 (the gnat package has a
Hello.
As far as I understand the situation, disabling the whole patch at
https://anonscm.debian.org/viewvc/gcccvs/branches/sid/gcc-7/debian/patches/ada-default-project-path.diff?view=markup
was the right choice for gnat-7.
It may probably be dropped, as gprbuild is already patched to search
Hello.
When building gnat-gps, I see the ugly message below.
The two first lines should be unrelated. The dependency solver always
selects the unstable version, then installs the version from
experimental because it is required (by gprbuild).
I have tried to re-link with and without -PIE, with
Matthias Klose:
> I was reading https://tracker.debian.org/news/794344,
>Replace libgnatprj/vsn, dropped by GCC with libgpr from gprbuild.
> why? libgnatprj/vsn, dropped by GCC is not true. Or are there plans not to use
> libgnatprj/vsn anymore?
Hello.
Ludovic has created Debian-specific
Hello.
In testing and unstable, most Ada packages FTBFS because some changes
libgnat6-dev invalidate their .ali files. Fixing this requires a
source upload and a passage through the NEW queue for every library.
[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866355
In experimental, the
Hello.
The gnat package now depends on gnat-7, meaning that gnat-7 is the
default Ada compiler in the unstable distribution.
Each source package building an Ada library requires a source+binary
upload with new ALI and SO versions (source-only uploads are not
allowed in the NEW queue).
Each
Hello.
Next default C compiler on Debian will be gcc-8.
Most Ada packages already build with trivial changes [1].
Every library will need to rename its -dev and so package.
Such renamings take time because they imply a manual review in the NEW queue.
Please consider updating your packages and
Dani:
> I'm curious about which Security Libraries are allowed in Ada libraries
> from now in Debian.
> eg.: ssl , tls etc :-)
Hello.
In Debian, the only Ada library using ssl or tls is libaws.
The distributed binary is linked with gnutls, but a command-line Make
assignment should be
Hello.
The switch to gnat-8 should happen in a few weeks, breaking almost all
Ada packages. Ideally, the migration should then be finished in the
experimental distribution, so that the unstable distribution only
requires a new upload of each Ada package.
These packages are ready.
gnat
> I've made several improvements on Aflex and Ayacc and I've also
> created a Debian package for Aflex.
> https://github.com/Ada-France/ayacc
> https://github.com/Ada-France/aflex
> Are you interested in having Debian packages for these two tools?
If you feel that these tools should be easy to
Hello.
All Ada packages seem ready for the migration to GCC-8, and the
release team has given their consent [1].
Most packages only require a trivial source upload to unstable with a
changelog entry stating:
* Rebuild in unstable for gnat-8 transition.
while a few exceptions only require a
> libgnatvsn ftbfs in 9.2.1-10
Sorry for the mess.
After a successful build, it seems that I have incorrectly played the
autoreconf/quilt refresh/scp/git commit music.
A build currently tests the following fix.
--- a/debian/patches/ada-libgnatvsn.diff
+++ b/debian/patches/ada-libgnatvsn.diff
@@
Hello.
> Can Get_Fallback_list be re-enable in
> /usr/share/ada/adainclude/gpr/gpr-knowledge.adb in Debian ?
> 'testing' or 'unstable' repo has this already enabled ?
It is available in version 2019. This version of the gprbuild package
currently exists only in 'experimental' because of the
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
Hello.
The gcc-$BV source package builds an Ada compiler named gnat-$BV,
and the companion libraries (libgnat-$BV, libgnatvsn$BV).
In unstable, gnat-8 and gnat-9 coexist.
The default
Hello.
You are receiving this message because you maintain a package
depending on the gnat Ada compiler in Debian.
The transition from gnat-8 to gnat-9 is almost completed.
Most packages require a source upload to the unstable distribution.
No accurate synchronization is necessary, but all
Hello.
The freeze for bullseye will start in december.
https://lists.debian.org/debian-devel-announce/2020/03/msg2.html
The default toolchain will be gcc-10.
gnat-10 is available, but not yet the default.
All Ada libraries must be updated for Gcc-10 and uploaded to
experimental. Because of
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
Hello.
The gcc-$V source package builds the Ada compiler (gnat-$V) and
companion libraries (libgnat-$V and libgnat_util-$V).
The default Ada compiler is selected by the gnat package.
In
Hello.
The transition to gnat-10 is now completed.
By the way, here is a message by the release team member who has
managed this transition.
As far as I can tell,
gnat (>= 10), gnat (<< 11),
could very well replace
gnat, gnat-10,
in the Ada Policy for libraries if this is more practical for
> It seems the libgnatprj7-dev package is missing the 'gpr.gpr' compatibility
> project.
Hello.
Thanks for spotting and reporting this issue.
>From your description, I infer that you are using
libgnatprj7-dev/2019-3 from the 'testing' or 'unstable' distribution.
I have added the project and a
> gnat ls -Pxmlada_sax.gpr
> Can't find ALI file for /usr/share/ada/adainclude/xmlada_sax/sax-symbols.adb
With gnat-9/9.3.0-18 and libxmlada-sax9-dev/9.3.0-18 from
testing/unstable, the command answers 'unknown switch
"-Pxmlada_sax.gpr"'. This is expected for recent installations, as
Adacore has
Source: dh-ada-library
Followup-For: Bug #992241
Hello.
(For context, see https://bugs.debian.org/992241. This bug should be
reassigned to either gprbuild or gnat, depending on the following
discussion)
If gnat(=10), gcc(=11) and g++(=11) are installed, then
/usr/bin/gnatgcc -> gcc-10
Hello.
Inspired by this thread, I have started https://wiki.debian.org/Ada to
collect information that does not fit into the Debian Policy for Ada.
I hope reading it will answer your concern.
Feel free to improve it.
> we will fix it by specifying the CFLAGS value in our upstream Makefile
> I think I found an error in the gprbuild package on Debian bullseye.
> The utility gprlib is installed in /usr/lib/gprbuild/gprlib.
Hello.
Sorry for the delay.
I have forwarded your report at https://bugs.debian.org/998628.
Hello.
The transition to gnat-11 is on its way in experimental.
Mostly because of me, it has started quite late.
As usual, once all Ada packages build in experimental, we will request
the approval from FTPmasters, then reupload them to unstable.
There are unresolved issues, so I expect this to
Hello.
Some news about the transition to gcc-11.
Most Ada packages are currently removed from testing because of
#995578 (libxmlada build-depends on unicode-data (< 14~) but
testing/unstable has 14.0.0-1). The fix is trivial but would require
a libxmlada transition, so it will be part of the
TLDR: Does anyone need the unversioned
* HOST-gnatmake executable,
* -lgnat shared library or
* gnatgcc executable?
Hello.
It seems possible to make the gnat-VERSION packages coinstallable.
The gnat-13 transition may be a good opportunity to debug this in
experimental.
A roadmap follows.
Hello.
During the gnat-10 transition, the release team suggested a change in
order to help the automatic migration from unstable to testing of all
Ada packages at once.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975589#24
Currently, the policy requires that
Package: lib...-dev
Hello.
Anyone interested in Ada should read Jean-Pierre Rosen’s summary about
ASIS in the Download section of
https://www.adalog.fr/en/adacontrol.html.
A possible workaround is to generate ASIS trees with the last gcc
supporting them (10), but compile with the current default gcc
(currently 11).
libgnatcoll-db is fixed in experimental.
For the record:
> That looks workable. Thanks for the tip. I assume that the package in
> unstable will at some point be linked to a new version of Libgnat or
> some other library, and thus become uninstallable in Bookworm, so I
> should do the above
Hello.
The experimental step of the gcc-12 transition is almost completed.
The last package (gtkada) is in the NEW queue, but the queue
processing time is neglectable nowadays, and the pending changes are
mostly trivial.
Ada packages need to be reuploaded to/rebuilt in/removed from unstable
> I have an Ada program that uses a database on Debian. Do I understand
> correctly that Gnatcoll-DB will be removed entirely from Debian
> Bookworm because of what looks like miscompilation on a single arch?
> So I'll have to build Gnatcoll-DB myself to be able to upgrade from
> Bullseye to
> > I am about to upload new ghdl packages once I get the remaining issues
Good!
> > fixed. I switched it to gcc/gnat-11 as that is the current default for
> > Ada.
> > There are more changes coming, so there will be a bunch of uploads as
> > they get implemented. At what point would you say it
Hello.
The transition of Ada packages to gcc-12 must be completed on
2023-01-12 [1].
-- Status of packages
AdaCore doesn’t support ASIS (or gnat-util) anymore. No one has
packaged a replacement. The asis libaws adabrowse adacontrol packages
will be removed from Debian.
gnat-studio/gnat-gps
Hello.
> Is it possible to integrate [the Alire Ada package manager] in the
> Debian distribution?
It does not make sense to *integrate* a tool intending to overlap with
distribution-specific integration tools like dpkg or rpm.
CPAN or TeXLive are useful, but source or binary packages from
Hello.
Intrusive changes are on their way.
Are there any objection?
The usr/bin/gnatgcc symbolic link has caused lots of maintenance
issues, for arguable benefit, and even confusion in rare occasions.
It will eventually be removed.
For now, it will be replaced with a script displaying the
> check_ali_update.sh is triggered with gcc-12 12.3.0-2.
Hello.
This is a false alert.
Commit 8fd9efdd6cc7fd537aa3ac1d4c57178ca0d3e6b7 in the GCC packaging
should prevent it.
Here are some details, in case further investigation is required.
Between gnat-12_12.2.0-14_amd64.deb and
Hello.
> check_ali_update.sh is triggered with gcc-12 12.3.0-2.
Probably, the only fix requires to rename of Ada -dev packages:
~20 trivial NMUs + NEW + stable-proposed-updates
> There were no changes to gcc/ada and libada.
The change may be caused by generated code interfacing with C.
>
Alejandro R. Mosteo
> Something that has been in the back of my mind also since the beginnings of
> the project is that I hope it should be relatively straightforward to
> generate Debian packages from Alire's metadata for someone familiar with
> Debian's Ada policy. If not, I would be interested
Hello.
GCC-13 is now the default Ada compiler for the unreleased ("testing")
Debian 13 ("trixie") distribution.
This list describes some changes specific to Debian.
* The GNU C library enables 64 bits durations on 32 bits architectures
like arm{el,hf}, preventing an overflow in 2038. The
Package: release.debian.org
X-Debbugs-Cc: debian-ada@lists.debian.org
Hello.
In addition to the information in https://bugs.debian.org/1065309,
here is the usual summary preparing a gnat transition.
--
This bug requests a green light for a transition of Ada packages from
gnat-12 to gnat-13 in
100 matches
Mail list logo
