Hi,
the following commits have been made to Salsa:
--
libisoburn:
commit 69ecfb2e52295798b52532bd8b1a5c693705fafe
Author: Thomas Schmitt
Date: Sat Sep 17 17:42:52 2022 +0200
Added "Multi-Arch: foreign" to the package
Hi,
I wrote:
> > My cheat sheet says that i shall add new sections with "UNRELEASED"
> > instead of "unstable"
Dominique Dumont wrote:
> Actually, you did set it to unstable in commit
> 06434fcf33b824059a20f5c788cd399cf2fd4ee8,
It is obvious that one should not let me do changes on Salsa.
But i
On Saturday, 17 September 2022 09:35:35 CEST Thomas Schmitt wrote:
> Seems plausible if xorriso gets it.
>
> Dominique: Do you agree ?
Yes.
> My cheat sheet says that i shall add new sections with "UNRELEASED" instead
> of "unstable" and that you change this word when uploading.
> So i wonder
Hello,
Thomas Schmitt, le sam. 17 sept. 2022 09:35:35 +0200, a ecrit:
> I am a bit confused by the presence of a section
> "libisoburn (1.5.4-3) unstable" in
>
> https://salsa.debian.org/optical-media-team/libisoburn/-/raw/HEAD/debian/changelog
> while libisoburn is at 1.5.4-2 in
>
Hi,
Samuel Thibault wrote:
> I was more thinking about architecture (i386, amd64, arm, etc.)
> difference, not OS difference :)
As long as it is Linux, libburn indeed behaves the same, modulo configuration
options. Similarly with libisofs, where the presence of development headers
or
Thomas Schmitt, le ven. 16 sept. 2022 17:55:33 +0200, a ecrit:
> Samuel Thibault wrote:
> > Since AIUI the xorriso package provides only a tool whose behavior is
> > exactly the same on all architectures,
>
> It depends on libburn which behaves different on Hurd compared to Linux.
I was more
Hi,
such Debian specifics are more a matter of my sponsor's opinion than
of my own. Cc-ing Dominique Dumont, therefore.
Samuel Thibault wrote:
> Since AIUI the xorriso package provides only a tool whose behavior is
> exactly the same on all architectures,
It depends on libburn which behaves
Package: xorriso
Version: 1.5.4-2
Severity: normal
Hello,
Since AIUI the xorriso package provides only a tool whose behavior is
exactly the same on all architectures, could you make it
Multi-Arch: foreign
so that the Debian Installer can use it as foreign dependency for
cross-builds?
Samuel
8 matches
Mail list logo
