Processed: submitter 664707, submitter 462809, submitter 529539, submitter 820996, submitter 843347

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> submitter 664707 !
Bug #664707 [phlipple] phlipple: Segmentation fault on startup
Bug #653675 [phlipple] phlipple: Segmentation fault on startup
Changed Bug submitter to 'Ben Finney ' from 'Ben Finney 
'.
> submitter 462809 !
Bug #462809 [partman-auto] installation-report: successful installation of 
'lenny' to Powermac G5, but required manual partitioning
Bug #462691 [partman-auto] debian-installer: fails to partition hard drives on 
powermac g5
Changed Bug submitter to 'Ben Finney ' from 'Ben Finney 
'.
> submitter 529539 !
Bug #529539 [evolution-common] evolution-common: help files cause “namespace 
error : colon are forbidden from PI names”
Bug #521892 [evolution-common] evolution-common: help files cause “namespace 
error : colon are forbidden from PI names”
Bug #525105 [evolution-common] evolution-common: help files cause “namespace 
error : colon are forbidden from PI names”
Changed Bug submitter to 'Ben Finney ' from 'Ben Finney 
'.
> submitter 820996 !
Bug #820996 [spykeviewer] spykeviewer: Section should not be “python”
Bug #813558 [spykeviewer] spykeviewer: Section should be “science”
Changed Bug submitter to 'Ben Finney ' from 'Ben Finney 
'.
> submitter 843347 !
Bug #843347 [python-migrate-doc] python-migrate-doc: Section should be “doc”
Changed Bug submitter to 'Ben Finney ' from 'Ben Finney 
'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
462691: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=462691
462809: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=462809
521892: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=521892
525105: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=525105
529539: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=529539
653675: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=653675
664707: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=664707
813558: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813558
820996: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=820996
843347: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843347
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Re: Please unblock glibc/2.24-14

[Cyril Brulebois]

Hello,

Aurelien Jarno  (2017-08-19):
> glibc/2.24-14 has been blocked for long in unstable due to the linux
> package not migrating. Unfortunately it failed to migrate at the same
> time due to bug#871275, which has nothing to glibc besides the fact that
> "libc-bin" appears in the log.
> 
> In short, after waiting for more than 2 weeks, it missed the freeze only
> by a few hours. It would be nice to have it in testing asap, as the
> current version in testing is not buildable with binutils 2.19 which is
> now in testing. Besides that nothing to worry about for d-i.

glibc  | 2.24-14   | testing| source
glibc  | 2.24-14   | unstable   | source

Happened during the 1000Z run.


KiBi.


signature.asc
Description: Digital signature

Please unblock glibc/2.24-14

[Aurelien Jarno]

Hi,

glibc/2.24-14 has been blocked for long in unstable due to the linux
package not migrating. Unfortunately it failed to migrate at the same
time due to bug#871275, which has nothing to glibc besides the fact that
"libc-bin" appears in the log.

In short, after waiting for more than 2 weeks, it missed the freeze only
by a few hours. It would be nice to have it in testing asap, as the
current version in testing is not buildable with binutils 2.19 which is
now in testing. Besides that nothing to worry about for d-i.

Thanks,
Aurelien

-- 
Aurelien Jarno  GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://www.aurel32.net


signature.asc
Description: PGP signature

Bug#839595: Device-Tree naming and hardware variants

[Josua Mayer]

Hi there,

Now it is time to raise a different problem: Hardware Variants.
Right now we have the Clearfog Pro, and the Clearfog Base.
The future might bring also introduce other CPU variants different from
Armada-388 (but thats pure speculation).

The Device-Tree was actually renamed in mainline with
712032aa65ae19a613488f8ce956e575cc5e1486, to
armada-388-clearfog-pro.dts. That one sets the model field to "SolidRun
Clearfog Pro A1".

Then we have the "SolidRun Clearfog Base A1" in
armada-388-clearfog-base.dts.

How can these variants be mirrored in flash-kernel? And is there a way
to allow moving SD-Cards between device variants? That would be a
*really* useful feature!

Either way, what can we do about this?

br
Josua Mayer

Bug#839595: tested

[Josua Mayer]

Hi again everybody,

I finally got around to trying this out myself using a freshly
debootstrapped stretch, and 2017.07-rc3 u-boot and these are my findings
with the early posted db entry:

The device-tree gets copied as expected
boot.scr gets generated
root= argument is not added to cmdline: That is actually fine!

I still had some trouble with mounting the rootfs, because it turns out
I used /dev/root short-hand in my fstab.
This is a problem because flash-kernel picks that value up and stores it
as conf/conf.d/default_root.
Obviously passing root=/dev/root makes no sense to the kernel.
I might even go as far as suggesting to not populate default_root if it
is set to this magical value!
Anyway after putting a UUID=... line in my fstab its all good!

And now to question the Kernel-Flavors Line:
Does anybody know if the Armada 388 supports lpae? I did not manage
finding sufficient information.
However I can tell you that the current linux-image-4.9.0-3-armmp-lpae
does *not* boot!
That means the serial console stays quiet after "Starting kernel ..."

So I now have this database entry:
Machine: SolidRun Clearfog A1
Kernel-Flavors: armmp
Boot-Script-Path: /boot/boot.scr
DTB-Id: armada-388-clearfog.dtb
U-Boot-Script-Name: bootscr.uboot-generic
Required-Packages: u-boot-tools

br
Josua Mayer

Re: Bug#872598: udev-udeb: no input in graphical installer

[Felipe Sateler]

On Sat, Aug 19, 2017 at 9:38 AM, Cyril Brulebois  wrote:
> Control: tag -1 patch
>
> Hi,
>
> (Again, please keep debian-boot@ in copy.)
>
> Raphael Hertzog  (2017-08-19):
>> > I've only quickly glanced at the contents of both packages, and
>> > debdiff mentions no obvious issues (file lists are the same).
>>
>> I believe this is precisely the problem. The new udev-udeb should
>> include a new file:
>> diff --git a/debian/udev-udeb.install b/debian/udev-udeb.install
>> index 6a8e2108f..6758fef06 100644
>> --- a/debian/udev-udeb.install
>> +++ b/debian/udev-udeb.install
>> @@ -5,6 +5,7 @@ lib/udev/ata_id
>>  lib/udev/scsi_id
>>  lib/udev/cdrom_id
>>  lib/udev/rules.d/50-udev-default.rules
>> +lib/udev/rules.d/60-input-id.rules
>>  lib/udev/rules.d/60-cdrom_id.rules
>>  lib/udev/rules.d/60-persistent-input.rules
>>  lib/udev/rules.d/60-persistent-storage.rules
>>
>> I won't have the time to test this now but I believe it's the problem.
>
> That's absolutely correct. I've started by copying the file manually into
> the netboot-gtk mini.iso, and confirmed the fix. To be extra sure, I've
> rebuilt a systemd package with your change, and used the new udev udebs
> for a clean build, and that works as well.
>
> A timely fix would be appreciated, the breakage(s) in the graphical
> installer prevented us from releasing debian-installer over the past few
> weeks, and it would be great not to wait too long before we're able to do
> so, esp. with linux 4.12.6-1 having reached testing lately.
>
> Thinking about this, I'll check with debian-release@ and I might just
> freeze all udeb-producing packages right away. Winter has come.
>
>
>> It would be nice to have a fixed udev soon. Thank you Cyril for the
>> investigation!
>>
>> I wonder if it would be possible to have autopkgtest tests covering
>> udev-udeb...
>
> I'm still new to the whole autopkgtest thing, but from where I stand, the
> fact d-i is broken has been known for quite a while; the core issue is
> that nobody investigated this before I found some time. An easy way to be
> more proactive on the systemd side would be to make sure that new (and/or
> deleted) files in the udev and libudev1 binaries are detected by
> maintainers (esp. since udev.install uses wildcards for rules files, while
> udev-udeb.rules uses a static list), so that the update can be propagated
> to the udebs if relevant.

--fail-missing is broken on the udeb builds at the moment, so it is
not enabled. I'll try to fix this and enable it. This should help
catch these sort of issues in the future.

-- 

Saludos,
Felipe Sateler

Re: Bug#872598: udev-udeb: no input in graphical installer

[Michael Biebl]

Am 19.08.2017 um 14:38 schrieb Cyril Brulebois:

> A timely fix would be appreciated, the breakage(s) in the graphical
> installer prevented us from releasing debian-installer over the past few
> weeks, and it would be great not to wait too long before we're able to do
> so, esp. with linux 4.12.6-1 having reached testing lately.

I might have time for that mid next week.

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Re: Bug#872598: udev-udeb: no input in graphical installer

[Cyril Brulebois]

Control: tag -1 patch

Hi,

(Again, please keep debian-boot@ in copy.)

Raphael Hertzog  (2017-08-19):
> > I've only quickly glanced at the contents of both packages, and
> > debdiff mentions no obvious issues (file lists are the same).
> 
> I believe this is precisely the problem. The new udev-udeb should
> include a new file:
> diff --git a/debian/udev-udeb.install b/debian/udev-udeb.install
> index 6a8e2108f..6758fef06 100644
> --- a/debian/udev-udeb.install
> +++ b/debian/udev-udeb.install
> @@ -5,6 +5,7 @@ lib/udev/ata_id
>  lib/udev/scsi_id
>  lib/udev/cdrom_id
>  lib/udev/rules.d/50-udev-default.rules
> +lib/udev/rules.d/60-input-id.rules
>  lib/udev/rules.d/60-cdrom_id.rules
>  lib/udev/rules.d/60-persistent-input.rules
>  lib/udev/rules.d/60-persistent-storage.rules
> 
> I won't have the time to test this now but I believe it's the problem.

That's absolutely correct. I've started by copying the file manually into
the netboot-gtk mini.iso, and confirmed the fix. To be extra sure, I've
rebuilt a systemd package with your change, and used the new udev udebs
for a clean build, and that works as well.

A timely fix would be appreciated, the breakage(s) in the graphical
installer prevented us from releasing debian-installer over the past few
weeks, and it would be great not to wait too long before we're able to do
so, esp. with linux 4.12.6-1 having reached testing lately.

Thinking about this, I'll check with debian-release@ and I might just
freeze all udeb-producing packages right away. Winter has come.


> It would be nice to have a fixed udev soon. Thank you Cyril for the
> investigation!
> 
> I wonder if it would be possible to have autopkgtest tests covering
> udev-udeb...

I'm still new to the whole autopkgtest thing, but from where I stand, the
fact d-i is broken has been known for quite a while; the core issue is
that nobody investigated this before I found some time. An easy way to be
more proactive on the systemd side would be to make sure that new (and/or
deleted) files in the udev and libudev1 binaries are detected by
maintainers (esp. since udev.install uses wildcards for rules files, while
udev-udeb.rules uses a static list), so that the update can be propagated
to the udebs if relevant.

I'm fine with setting up a check through a cron job on d-i.debian.org so
as to avoid putting the burden on systemd maintainers. The feedback loop
might take a few hours/days after an upload with such a change, but that
would make it obvious that something “important” changed, and would speed
up understanding such regressions.


KiBi.


signature.asc
Description: Digital signature

Re: Bug#872598: udev-udeb: no input in graphical installer

[Michael Biebl]

Am 19.08.2017 um 10:14 schrieb Raphael Hertzog:

> I wonder if it would be possible to have autopkgtest tests covering
> udev-udeb...

We'd be happy to ship such an autopkgtest. Help in that regard would be
much appreciated.

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Re: Bug#872598: udev-udeb: no input in graphical installer

[Michael Biebl]

Am 19.08.2017 um 10:19 schrieb Michael Biebl:
> Am 19.08.2017 um 04:59 schrieb Cyril Brulebois:
>>
>> I haven't looked into the changelog and actual changes (yet), but I'd be
>> happy to get some input (no pun intended) from systemd maintainers.
>>
> 
> Maybe this is related:
> https://github.com/systemd/systemd/commit/43af16c99c800afdfc4b6913ea7596aaddd0395d
> 
> I.e., could you apply this upstream patch, make sure the udev rule is in
> the udeb and try again?

Urgh, I missed that this patch is already part of v234, sorry for the
confusion.
So all that's missing seems to be the installation in the udev-udeb.


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#861652: task-kde-desktop: Speed of the mouse pointer does not depend on the speed settings in the system settings of the kde.

[Igor]

I've been searching for more information about this bug, and I've found
a bug report at RedHat that probably is connected to this one:
https://bugzilla.redhat.com/show_bug.cgi?id=1227522 . This had led me to
another bug report, this time, in KDE:
https://bugs.kde.org/show_bug.cgi?id=350688 .

So it seems to be an upstream bug between KDE Plasma and LibInput. As
a workaround, one can use the "xinput" command to set the acceleration
directly from the command line:

  xinput set-prop  276 

276 is the ID of the property "libinput Accel Speed". For example, in my
case, to set the acceleration to the maximum (1.0), I've had to do this:

  xinput set-prop 12 276 1.0

Use this command to list the connected devices:

  xinput list

Use this command to know the current properties of a specific device:

  xinput list-props 

Another workaround is to just install "xserver-xorg-input-evdev" and
uninstall "xserver-xorg-input-libinput". In my opinion, for now, EvDev
suits my needs much better than LibInput.

Salutes.

Re: Bug#872598: udev-udeb: no input in graphical installer

[Michael Biebl]

Am 19.08.2017 um 04:59 schrieb Cyril Brulebois:
> 
> I haven't looked into the changelog and actual changes (yet), but I'd be
> happy to get some input (no pun intended) from systemd maintainers.
> 

Maybe this is related:
https://github.com/systemd/systemd/commit/43af16c99c800afdfc4b6913ea7596aaddd0395d

I.e., could you apply this upstream patch, make sure the udev rule is in
the udeb and try again?

If that doesn't help, we will need log files to debug this further.
A Xorg log from a working/non-working installer would be a start.

Regards,
Michael

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Processed: Re: flash-kernel: Patch for Raspberry Pi 2 support

[Debian Bug Tracking System]

Processing control commands:

> found -1 3.35
Bug #872601 [flash-kernel] flash-kernel: Patch for Raspberry Pi 2 support
Marked as found in versions flash-kernel/3.35.
> notfound -1 3.79
Bug #872601 [flash-kernel] flash-kernel: Patch for Raspberry Pi 2 support
Ignoring request to alter found versions of bug #872601 to the same values 
previously set
> close -1
Bug #872601 [flash-kernel] flash-kernel: Patch for Raspberry Pi 2 support
Marked Bug as done

-- 
872601: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872601
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#872601: flash-kernel: Patch for Raspberry Pi 2 support

[Petter Reinholdtsen]

Control: found -1 3.35
Control: notfound -1 3.79
Control: close -1

Forgot to add a version number to this report.

While trying to apply this patch to the latest version, I discovered
that there already is a RPi entry in version 3.79, and the reason this
did not work for me was that the wrong kernel (the one from the
collabora repo) was installed and not recognized.

I thus suspect this issue is a bit besides what can and should be fixed
in a Debian package, and flag it as not found in version 3.79.

-- 
Happy hacking
Petter Reinholdtsen

Bug#861652: task-kde-desktop: Speed of the mouse pointer does not depend on the speed settings in the system settings of the kde.

[Igor]

Hello:

I'm also experiencing this problem. I've checked the content of the file
~/.config/kcminputrc and the settings are effectively changed in it.
However, neither the mouse cursor speed nor its acceleration seem to
take any effect. I've also tried to change the number of lines scrolled
by the mouse wheel, but it hasn't worked either.

Thank you.

Bug#862139: [flash-kernel] Please, stop flashing multiple times

[Petter Reinholdtsen]

Control: found -1 3.35

As far as I can tell from the changelog of 3.35+deb8u3,
none of the changes done to the jessie branch relates to
this problem, so it seem appropriate to set the version
to the common anchestor of the all branches.

-- 
Happy hacking
Petter Reinholdtsen

Processed: Re: [flash-kernel] Please, stop flashing multiple times

[Debian Bug Tracking System]

Processing control commands:

> found -1 3.35
Bug #862139 [flash-kernel] [flash-kernel] Please, stop flashing multiple times
Marked as found in versions flash-kernel/3.35.

-- 
862139: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=862139
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems