Are follow-up steps for Lomiri desktop required?

2024-05-22 Thread Roland Clobus

Hello installer team,

I've noticed that (currently as draft) preparations [1] are ongoing to 
add Lomiri as task-lomiri-desktop into task-desktop.


Is it intended to have Lomiri available in the installer and to have 
live images?


If so, it would need some coordination to have it all set up. (I'm 
thinking of d-i, regular builds, openQA, Jenkins, live-build, ...)


With kind regards,
Roland Clobs

[1] https://salsa.debian.org/installer-team/tasksel/-/merge_requests/30/


OpenPGP_signature.asc
Description: OpenPGP digital signature


Re: Re-planning for 12.6

2024-05-22 Thread Cyril Brulebois
Hi,

Jonathan Wiltshire  (2024-04-21):
> Too late now in any case. SRMs will regroup and decide whether we push
> for one in May or just wait for June anyway.

June is 10 days away. Do we have any kind of tentative schedule?


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


signature.asc
Description: PGP signature


Re: Are follow-up steps for Lomiri desktop required?

2024-05-22 Thread Mike Gabriel

Hi Roland,
(Cc:ing Guido who also works on Lomiri in Debian with correct now)

On  Mi 22 Mai 2024 16:50:02 CEST, Roland Clobus wrote:


Hello installer team,

I've noticed that (currently as draft) preparations [1] are ongoing  
to add Lomiri as task-lomiri-desktop into task-desktop.


Is it intended to have Lomiri available in the installer and to have  
live images?


If so, it would need some coordination to have it all set up. (I'm  
thinking of d-i, regular builds, openQA, Jenkins, live-build, ...)


With kind regards,
Roland Clobs

[1] https://salsa.debian.org/installer-team/tasksel/-/merge_requests/30/


The plan is indeed to propose Lomiri as possible selection for a  
desktop environment in D-I.


Unfortunately, I don't know what steps are required to get Lomiri in.  
Neither do I know who has a say in this, where it gets decided what  
gets included as installer option in D-I and what not.


The Lomiri Operating Environment packaging for Debian is currently  
seeing quite a boot because we have found a sponsor that finance the  
related work. The overall goal is to have Lomiri available in Debian,  
so we can pre-install a Debian based tablet OS for Debian Edu.


Thanks for picking this up starting the discussion!
Mike (aka sunweaver at d.o)
--

mike gabriel aka sunweaver (Debian Developer)
mobile: +49 (1520) 1976 148
landline: +49 (4351) 486 14 27

GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22  0782 9AF4 6B30 2577 1B31
mail: sunwea...@debian.org, http://sunweavers.net



pgpQ4qzUSvBtv.pgp
Description: Digitale PGP-Signatur


Re: Are follow-up steps for Lomiri desktop required?

2024-05-22 Thread Cyril Brulebois
Mike Gabriel  (2024-05-22):
> The plan is indeed to propose Lomiri as possible selection for a
> desktop environment in D-I.
> 
> Unfortunately, I don't know what steps are required to get Lomiri in.
> Neither do I know who has a say in this, where it gets decided what
> gets included as installer option in D-I and what not.

In d-i, pkgsel starts tasksel, so if that's available in tasksel…

> The Lomiri Operating Environment packaging for Debian is currently seeing
> quite a boot because we have found a sponsor that finance the related work.
  

Good one!


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


signature.asc
Description: PGP signature


Re: Are follow-up steps for Lomiri desktop required?

2024-05-22 Thread Mike Gabriel

On  Mi 22 Mai 2024 17:50:06 CEST, Cyril Brulebois wrote:


Mike Gabriel  (2024-05-22):



The Lomiri Operating Environment packaging for Debian is currently seeing
quite a boot because we have found a sponsor that finance the related work.

  

Good one!


/me grins, s/boot/boost/, of course.

Mike
--

mike gabriel aka sunweaver (Debian Developer)
mobile: +49 (1520) 1976 148
landline: +49 (4351) 486 14 27

GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22  0782 9AF4 6B30 2577 1B31
mail: sunwea...@debian.org, http://sunweavers.net



pgphh1spMpy5v.pgp
Description: Digitale PGP-Signatur


Bug#1071648: FTBFS with Linux 6.8+

2024-05-22 Thread Tianon Gravi
Source: busybox
Version: 1:1.36.1-7
Severity: serious
Tags: ftbfs upstream
X-Debbugs-Cc: tia...@debian.org

The recent upload of src:linux to 6.8+ (specifically 6.8.9-1,
ironicially uploaded around the same time as the last busybox upload)
causes src:busybox to FTBFS (logs from reproducible-builds):

| /build/reproducible-path/busybox-1.36.1/networking/tc.c: In function 
'cbq_print_opt':
| /build/reproducible-path/busybox-1.36.1/networking/tc.c:237:27: error: 
'TCA_CBQ_MAX' undeclared (first use in this function); did you mean 
'TCA_CBS_MAX'?
|   237 | struct rtattr *tb[TCA_CBQ_MAX+1];
|   |   ^~~
|   |   TCA_CBS_MAX
| /build/reproducible-path/busybox-1.36.1/networking/tc.c:237:27: note: each 
undeclared identifier is reported only once for each function it appears in
| /build/reproducible-path/busybox-1.36.1/networking/tc.c:250:16: error: 
'TCA_CBQ_RATE' undeclared (first use in this function); did you mean 
'TCA_TBF_RATE64'?
|   250 | if (tb[TCA_CBQ_RATE]) {
|   |^~~~
|   |TCA_TBF_RATE64
| /build/reproducible-path/busybox-1.36.1/networking/tc.c:256:16: error: 
'TCA_CBQ_LSSOPT' undeclared (first use in this function)
|   256 | if (tb[TCA_CBQ_LSSOPT]) {
|   |^~
| /build/reproducible-path/busybox-1.36.1/networking/tc.c:257:61: error: 
invalid application of 'sizeof' to incomplete type 'struct tc_cbq_lssopt'
|   257 | if (RTA_PAYLOAD(tb[TCA_CBQ_LSSOPT]) < sizeof(*lss))
|   | ^
| /build/reproducible-path/busybox-1.36.1/networking/tc.c:262:16: error: 
'TCA_CBQ_WRROPT' undeclared (first use in this function)
|   262 | if (tb[TCA_CBQ_WRROPT]) {
|   |^~
| /build/reproducible-path/busybox-1.36.1/networking/tc.c:263:61: error: 
invalid application of 'sizeof' to incomplete type 'struct tc_cbq_wrropt'
|   263 | if (RTA_PAYLOAD(tb[TCA_CBQ_WRROPT]) < sizeof(*wrr))
|   | ^
| /build/reproducible-path/busybox-1.36.1/networking/tc.c:268:16: error: 
'TCA_CBQ_FOPT' undeclared (first use in this function)
|   268 | if (tb[TCA_CBQ_FOPT]) {
|   |^~~~
| /build/reproducible-path/busybox-1.36.1/networking/tc.c:269:59: error: 
invalid application of 'sizeof' to incomplete type 'struct tc_cbq_fopt'
|   269 | if (RTA_PAYLOAD(tb[TCA_CBQ_FOPT]) < sizeof(*fopt))
|   |   ^

https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/busybox_1.36.1-7.rbuild.log.gz

This has been reported upstream[1][2] (back in January), but with no
upstream resolution yet.

[1]: https://bugs.busybox.net/show_bug.cgi?id=15931
[2]: https://bugs.busybox.net/show_bug.cgi?id=15934


-- System Information:
Debian Release: trixie/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash



Bug#1071648: FTBFS with Linux 6.8+

2024-05-22 Thread Tianon Gravi
On Wed, 22 May 2024 at 16:09, Tianon Gravi  wrote:
> The recent upload of src:linux to 6.8+ (specifically 6.8.9-1,
> ironicially uploaded around the same time as the last busybox upload)
> causes src:busybox to FTBFS (logs from reproducible-builds):
>
> ...
>
> https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/busybox_1.36.1-7.rbuild.log.gz

Full build log now attached (apologies for not including it in the
original submission).

♥,
- Tianon
  4096R / B42F 6819 007F 00F8 8E36  4FD4 036A 9C25 BF35 7DD4


busybox_1.36.1-7.rbuild.log.gz
Description: application/gzip


Bug#1071651: debootstrap --print-debs jumbled output

2024-05-22 Thread jidanni
Package: debootstrap
Version: 1.0.128+nmu2+deb12u1
Severity: minor

With --print-debs first there are packages on single lines. Then,
without even a newline, comes one long line of packages.
$ sudo debootstrap --print-debs sid /home/sid-chroot 
http://opensource.nchc.org.tw/debian/
...
tzdata
usr-is-merged
util-linux
zlib1g adduser apt-utils cpio cron cron-daemon-common...

P.S., on the bottom of the man page is a twenty-year old date...



Bug#1071652: Man page forgets to mention actual --second-stage usage

2024-05-22 Thread jidanni
Package: debootstrap
Version: 1.0.128+nmu2+deb12u1

Man page says:
   --second-stage
  Complete  the bootstrapping process.  Other arguments are 
generally not needed.

Well one cannot just run these two in sequence:
SYNOPSIS
   debootstrap [OPTION...]  SUITE TARGET [MIRROR [SCRIPT]]
   debootstrap [OPTION...]  --second-stage

On https://unix.stackexchange.com/a/355197/179494 we see the answer.
Therefore the man page must kindly also mention: "to run the second stage,
chroot to where you've unpacked the archive, and run
/debootstrap/debootstrap --second-stage
"



Bug#1071652: As a matter of fact

2024-05-22 Thread Dan Jacobson
As a matter of fact, the solution I posted doesn't work either.

Therefore, be sure on the man page, to mention the true sequence needed:

# debootstrap 
(missing step goes here)
# debootstrap --second-stage