Bug#991177: libdebian-installer: reproducible builds: Embeds build path in libdebian-installer-extra.so.*

2021-10-17 Thread Cyril Brulebois
Vagrant Cascadian  (2021-10-16):
> On 2021-07-16, Cyril Brulebois wrote:
> > I know we haven't always been stellar when it comes to merging repro
> > build work, sorry about that. Any chance you could chase^Wremind us
> > about such issues once Bullseye (r0, and maybe r1) is out the door?
> 
> The long-awaited requested reminder... is here! :)

Thanks, the patch no longer applies cleanly (some fuzz, can be applied
trivially anyway, no need to resubmit), and I do wonder whether Samuel's
commit[1] doesn't make the issue go away on its own: CFLAGS is now
inherited from the environment, and I'm seeing the flag you're proposing
to add in various Makefile (and related) files after a build.

 1. 
https://salsa.debian.org/installer-team/libdebian-installer/-/commit/4b679de89592dccb6446637498e619738ee1

Any chance you could check whether current master is fine, please?


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature


Bug#991177: libdebian-installer: reproducible builds: Embeds build path in libdebian-installer-extra.so.*

2021-10-17 Thread Vagrant Cascadian
On 2021-10-17, Cyril Brulebois wrote:
> Vagrant Cascadian  (2021-10-16):
>> On 2021-07-16, Cyril Brulebois wrote:
>> > I know we haven't always been stellar when it comes to merging repro
>> > build work, sorry about that. Any chance you could chase^Wremind us
>> > about such issues once Bullseye (r0, and maybe r1) is out the door?
>> 
>> The long-awaited requested reminder... is here! :)
>
> Thanks, the patch no longer applies cleanly (some fuzz, can be applied
> trivially anyway, no need to resubmit), and I do wonder whether Samuel's
> commit[1] doesn't make the issue go away on its own: CFLAGS is now
> inherited from the environment, and I'm seeing the flag you're proposing
> to add in various Makefile (and related) files after a build.
>
>  1. 
> https://salsa.debian.org/installer-team/libdebian-installer/-/commit/4b679de89592dccb6446637498e619738ee1
>
> Any chance you could check whether current master is fine, please?

Yes, that fixes the issue, great!

Just need to add the appropriate Closes line in debian/changelog and be
done with it, then. :)


live well,
  vagrant


signature.asc
Description: PGP signature


Bug#732696: Updated os-prober script for Haiku OS

2021-10-17 Thread Alexander G. M. Smith

Package: os-prober
Version: 1.79
Tags: patch

There's an updated version of the /usr/lib/os-probes/mounted/83haiku 
file now available for the os-prober package.  Hope it can be added to 
the latest Debian distribution!


I've gone through the previous work everyone here has done on making an 
83haiku script and fixed it up to detect the current versions of Haiku 
as well as all the older ones.  Added some internal documentation too.  
It's now got an official home on the Haiku source git repository:


https://git.haiku-os.org/haiku/tree/3rdparty/os_probe/83haiku

There's also a related README.md in the same directory, which I'll 
reproduce here:


# os-probe for the Haiku Computer Operating System

This is the Linux "os-probes" file to detect Haiku OS and to 
automatically add

it to the GRUB boot menu.  Mostly relevant for x86 BIOS based computers.

Copy the 83haiku file to your Linux system in the os-probes subdirectory,
usually (in Fedora at least) it will be 
/usr/libexec/os-probes/mounted/83haiku

You can find older 83haiku versions in the repository history, though the
latest should be able to detect older (pre-package manager) Haiku too.

Then regenerate the GRUB boot configuration file.  This will happen
automatically the next time your kernel is updated.  To do it manually,
for old school MBR BIOS boot computers, the command is
`grub2-mkconfig --output /boot/grub2/grub.cfg`
If it doesn't find the Haiku partitions, try manually mounting them in Linux
and rerun the grub command.

Computers using the newer UEFI boot system have a EFI/HAIKU/BOOTX64.EFI file
that you manually install to your EFI partition, and booting is done
differently, so you don't need this 83Haiku file for them.  See
[UEFI Booting Haiku](https://www.haiku-os.org/guides/uefi_booting/) instead.

The original seems to have come from Debian and was written by François 
Revol.

It's in the
[Debian os-prober 
package](https://packages.debian.org/search?keywords=os-prober).

There's also a big discussion about updating it in
[Debian Bug Report 
#732696](https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=732696).
Latest version is now at 
https://git.haiku-os.org/haiku/tree/3rdparty/os_probe


_AGMS20210927_