Re: Bug#864597: upgrade-reports: jessie -> stretch: gnome fails to upgrade: cycle found while processing triggers

[Cyril Brulebois]

Bill Allombert  (2017-06-15):
> It would be really nice if we could remove the circular dependency 
> between openjdk-8 and ca-certificate before the release, otherwise
> the stretch to buster upgrade will be a nightmare.
> It always much easier to add circular dependency than to remove them.

Bill, we're trying to fix/work around a jessie to stretch upgrade path
issue for the default desktop setup. And we're days away from the
tentative date for the release. Needless to say, trying to fix this
upgrade path is somewhat more important than what happens for stretch to
buster, for which years still have to pass. Plenty of time to figure out
what to do.

Of course it would be better if ca-certificates-java wouldn't have been
“fixed” on 2017-05-31 when openjdk-7 was removed on 2016-04-22. But
that's the situation we have to deal with right now.


KiBi.


signature.asc
Description: Digital signature

Re: Bug#864597: upgrade-reports: jessie -> stretch: gnome fails to upgrade: cycle found while processing triggers

[Cyril Brulebois]

Emmanuel Bourg  (2017-06-15):
> If you upload a NMU could you please push the changes to the Git
> repository?

I'll look into this when I've slept a bit. Reminders/prods welcome.


KiBi.


signature.asc
Description: Digital signature

Re: Bug#864597: upgrade-reports: jessie -> stretch: gnome fails to upgrade: cycle found while processing triggers

[Emmanuel Bourg]

Le 15/06/2017 à 18:09, Cyril Brulebois a écrit :

> If all succeed, I intend to NMU ca-certificates-java with the attached
> changes. I could have reintroduced the old package, but I chose to retain
> the svn to git changes, and to drop the version for the openjdk-7 case,
> since even jessie had a higher version. Attached debdiffs against current
> version, and previous one.

Is this the only solution? That's a bit odd to retain the openjdk-7
dependency on ca-certificates-java and potentially stick with it
forever. Maybe we should simply remove the JRE dependency on
ca-certificates-java and move the keystore generation to openjdk-8. That
would also solve the circular dependency (#864657).

If you upload a NMU could you please push the changes to the Git repository?

Emmanuel Bourg

Re: Please dak copy-installer 20170615

[Jonathan Wiltshire]

Hi,

On 2017-06-15 15:00, Cyril Brulebois wrote:

Release team, please hint it into testing:

  unblock debian-installer/20170615
  urgent debian-installer/20170615


With pleasure.


--
Jonathan Wiltshire  j...@debian.org
Debian Developer http://people.debian.org/~jmw

4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC  74C3 5394 479D D352 4C51

 SaaS == Saunas as a Service
 broonie, more like Sauna as additional Storage

Re: Please dak copy-installer 20170615

[Ansgar Burchardt]

Cyril Brulebois writes:
> FTPmasters, please sync the installer from sid to testing:
>
>   dak copy-installer 20170615

Done.

> Also, there was no recent clean-up in the sid directory; I think we
> could remove everything from 2015. Maybe also everything from 2016,
> but I'm tempted to give debian-boot@ people a chance to react in case
> images from 2016 should stay a bit longer. Of course this can wait
> post-release, no urgency from my point of view.

Not done yet, but we should probably also do the clean-up for stretch.

Ansgar

Re: Bug#864597: upgrade-reports: jessie -> stretch: gnome fails to upgrade: cycle found while processing triggers

[Bill Allombert]

On Thu, Jun 15, 2017 at 03:16:17PM +0200, Cyril Brulebois wrote:
> Julien Cristau  (2017-06-15):
> > It sounds like openjdk-8 added two Breaks recently, one or both of
> > which are causing trouble, and none of which fix anything as bad as
> > this.  So I think we should remove the Breaks on tzdata-java from
> > openjdk-8-jdk-headless, and remove the Breaks on ca-certificates-java
> > from openjdk-8-jre-headless.  Would that fix the current issue?
> > 
> > From what I can see #863820 is at most a normal-severity issue.  Not
> > upgrading some packages is way way better than a failed upgrade.
> 
> I'm currently building an updated openjdk-8 with the attached changes
> to see what the upgrade-desktop test cases would look like.
> 
> Note: I've chosen to remove the “Breaks: ${jrehl:Breaks}” line from
> debian/control* so that I'm only touching these files, since d/rules
> seems to only set it to tzdata-java anyway, depending on the target
> dist.
> 
> I'll report the results afterwards, but as mentioned on IRC, even if
> that looks good in the end, fewer than 2 days to become confident it
> won't regress in other cases is really short. :(

It would be really nice if we could remove the circular dependency 
between openjdk-8 and ca-certificate before the release, otherwise
the stretch to buster upgrade will be a nightmare.
It always much easier to add circular dependency than to remove them.

Cheers,
Bill.

Bug#864802: unblock: squashfs-tools/1:4.3-4

[Niels Thykier]

Control: tags -1 moreinfo

László Böszörményi (GCS):
> Package: release.debian.org
> User: release.debian@packages.debian.org
> Usertags: unblock
> 
> Hi Release Team,
> 
> There are two data corruption bug in squashfs-tools that fixed in the
> last upload for Sid.

Hi,

Thanks for fixing it and notifying us.

> I let it age seven days even if the fixes quite
> straightforward.
> 

This was a very unfortunate choice.  We are way past the deadline for
fixes to stretch.  If you had come to us Thursday or Friday last week
(i.e. around the time of the upload),  granting an exception would have
been a lot easier for us (like aggressive aging).

 * Done is done. I am mentioning it for the next release.  Please be
   mindful of deadlines.

For the fixes themselves, they look like something we would very much
like to have in stretch.  Please consider submitting them for the stable
upload after the release.

Thanks,
~Niels

Processed: Re: Bug#864802: unblock: squashfs-tools/1:4.3-4

[Debian Bug Tracking System]

Processing control commands:

> tags -1 moreinfo
Bug #864802 [release.debian.org] unblock: squashfs-tools/1:4.3-4
Added tag(s) moreinfo.

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

debian stretch being released without fixing wpagui and wpasupplicant ?

[shirish शिरीष]

Dear all,

I had shared the below at debian-publicity in response to the stretch
announcement in which I was given this answer -

https://lists.debian.org/debian-publicity/2017/06/msg00012.html

Now as I'm not a DD (nor hopeful of becoming a non-uploading DD at
least for sometime) hence debian-devel list is closed to me and the
only way to get my plea heard is the debian-release team. So without
further ado, here it is -

I have a query, how is stretch being released without multiple bugs
fixed for wpagui and wpasupplicant, I had a look at the stretch
announcement notes as well as the serious and grave bugs filed against
wpagui and wpasupplicant i.e.

b1 - #849122 - With 2.6-2 i dont have the wifi adapter in the
(network-manager) list available
b2 - #849077 - wpasupplicant: [Regression] Updating wpasupplicant
makes not possible to connect to encrypted WiFi
 b3 - #849875 - broadcom-sta-dkms: Wifi association took too long,
failing activation

While some of the bugs is related to broadcom only chipsets, other bug
could be hit by anyone. So unless there are packages which can take
place of wpagui and wpasupplicant and these packages can be removed
then please inform users.

Or at the very least warn them through stretch announcement as to what
they should do otherwise users having broadcom chips would be in for a
very nasty surprise when upgrading.

Maybe some of the experts could weigh in and make a proper message
about the above bugs situation.

Till later.
-- 
  Regards,
  Shirish Agarwal  शिरीष अग्रवाल
  My quotes in this email licensed under CC 3.0
http://creativecommons.org/licenses/by-nc/3.0/
http://flossexperiences.wordpress.com
EB80 462B 08E1 A0DE A73A  2C2F 9F3D C7A4 E1C4 D2D8



-- 
  Regards,
  Shirish Agarwal  शिरीष अग्रवाल
  My quotes in this email licensed under CC 3.0
http://creativecommons.org/licenses/by-nc/3.0/
http://flossexperiences.wordpress.com
EB80 462B 08E1 A0DE A73A  2C2F 9F3D C7A4 E1C4 D2D8

Re: Bug#864597: upgrade-reports: jessie -> stretch: gnome fails to upgrade: cycle found while processing triggers

[Cyril Brulebois]

Cyril Brulebois  (2017-06-15):
> I was just saying this on IRC:
> 
> “should I try to reinstate ca-certificates-java's old dependencies and
> compare? from my initial bug report, that's the change in the archive
> that led to the regression.”
> 
> and mentioned earlier that given the old dependencies have an OR anyway,
> we shouldn't be introducing an uninstallable package. This would have
> the nice effect of being a solution that can be implemented in hours
> instead of days (given openjdk-8's build time). This doesn't mean we
> should jump the gun anyway…
> 
> I'll report back.

This is looking good so far: gnome upgrade path fixed, kde and xfce are
still looking good, and tests with other desktop tasks are still running.

If all succeed, I intend to NMU ca-certificates-java with the attached
changes. I could have reintroduced the old package, but I chose to retain
the svn to git changes, and to drop the version for the openjdk-7 case,
since even jessie had a higher version. Attached debdiffs against current
version, and previous one.


KiBi.
diff -Nru ca-certificates-java-20170531/debian/changelog ca-certificates-java-20170531+nmu1/debian/changelog
--- ca-certificates-java-20170531/debian/changelog	2017-05-31 15:02:23.0 +0200
+++ ca-certificates-java-20170531+nmu1/debian/changelog	2017-06-15 17:33:00.0 +0200
@@ -1,3 +1,13 @@
+ca-certificates-java (20170531+nmu1) unstable; urgency=high
+
+  * Non-maintainer upload.
+  * Revert to depending on openjdk-7 instead of openjdk-8, since this triggers
+a failure to dist-upgrade, due to the triggers loop (See: #864597). The
+openjdk-7 package was dropped from stretch, but the java7-runtime-headless
+alternative dependency is satisfied by openjdk-8.
+
+ -- Cyril Brulebois   Thu, 15 Jun 2017 17:33:00 +0200
+
 ca-certificates-java (20170531) unstable; urgency=medium
 
   * Team upload.
diff -Nru ca-certificates-java-20170531/debian/rules ca-certificates-java-20170531+nmu1/debian/rules
--- ca-certificates-java-20170531/debian/rules	2017-05-31 15:00:28.0 +0200
+++ ca-certificates-java-20170531+nmu1/debian/rules	2017-06-15 17:31:24.0 +0200
@@ -6,11 +6,11 @@
 
 ifeq ($(shell dpkg-vendor --derives-from Ubuntu && echo yes),yes)
 	SUBSTVARS = -Vnss:Depends="libnss3 (>= 3.12.9+ckbi-1.82-0ubuntu3~)" \
--Vjre:Depends="openjdk-8-jre-headless"
+-Vjre:Depends="openjdk-7-jre-headless"
 	nss_lib = libnss3
 else
 	SUBSTVARS = -Vnss:Depends="libnss3 (>= 3.12.10-2~)" \
--Vjre:Depends="openjdk-8-jre-headless"
+-Vjre:Depends="openjdk-7-jre-headless"
 	nss_lib = libnss3
 endif
 
diff -Nru ca-certificates-java-20161107/debian/changelog ca-certificates-java-20170531+nmu1/debian/changelog
--- ca-certificates-java-20161107/debian/changelog	2016-11-07 13:45:23.0 +0100
+++ ca-certificates-java-20170531+nmu1/debian/changelog	2017-06-15 17:33:00.0 +0200
@@ -1,3 +1,21 @@
+ca-certificates-java (20170531+nmu1) unstable; urgency=high
+
+  * Non-maintainer upload.
+  * Revert to depending on openjdk-7 instead of openjdk-8, since this triggers
+a failure to dist-upgrade, due to the triggers loop (See: #864597). The
+openjdk-7 package was dropped from stretch, but the java7-runtime-headless
+alternative dependency is satisfied by openjdk-8.
+
+ -- Cyril Brulebois   Thu, 15 Jun 2017 17:33:00 +0200
+
+ca-certificates-java (20170531) unstable; urgency=medium
+
+  * Team upload.
+  * Depend on openjdk-8 instead of openjdk-7 (Closes: #863803)
+  * Moved the package to Git
+
+ -- Emmanuel Bourg   Wed, 31 May 2017 15:02:23 +0200
+
 ca-certificates-java (20161107) unstable; urgency=medium
 
   * Team upload.
diff -Nru ca-certificates-java-20161107/debian/control ca-certificates-java-20170531+nmu1/debian/control
--- ca-certificates-java-20161107/debian/control	2016-11-07 13:41:49.0 +0100
+++ ca-certificates-java-20170531+nmu1/debian/control	2017-05-31 15:00:11.0 +0200
@@ -8,8 +8,8 @@
James Page 
 Build-Depends: debhelper (>= 9), default-jdk, javahelper, junit4
 Standards-Version: 3.9.8
-Vcs-Svn: svn://anonscm.debian.org/pkg-java/trunk/ca-certificates-java
-Vcs-Browser: https://anonscm.debian.org/viewvc/pkg-java/trunk/ca-certificates-java/
+Vcs-Git: https://anonscm.debian.org/git/pkg-java/ca-certificates-java.git
+Vcs-Browser: https://anonscm.debian.org/cgit/pkg-java/ca-certificates-java.git
 
 Package: ca-certificates-java
 Architecture: all
diff -Nru ca-certificates-java-20161107/debian/rules ca-certificates-java-20170531+nmu1/debian/rules
--- ca-certificates-java-20161107/debian/rules	2016-03-21 14:05:28.0 +0100
+++ ca-certificates-java-20170531+nmu1/debian/rules	2017-06-15 17:31:24.0 +0200
@@ -6,7 +6,7 @@
 
 ifeq ($(shell dpkg-vendor --derives-from Ubuntu && echo yes),yes)
 	SUBSTVARS = -Vnss:Depends="libnss3 (>= 3.12.9+ckbi-1.82-0ubuntu3~)" \
-

Re: Bug#864597: upgrade-reports: jessie -> stretch: gnome fails to upgrade: cycle found while processing triggers

[Cyril Brulebois]

Andreas Beckmann  (2017-06-15):
> On 2017-06-15 15:16, Cyril Brulebois wrote:
> > Julien Cristau  (2017-06-15):
> >> It sounds like openjdk-8 added two Breaks recently, one or both of
> >> which are causing trouble, and none of which fix anything as bad as
> >> this.  So I think we should remove the Breaks on tzdata-java from
> >> openjdk-8-jdk-headless, and remove the Breaks on ca-certificates-java
> >> from openjdk-8-jre-headless.  Would that fix the current issue?

FWIW, there are absolutely no differences when removing those two breaks,
even with resolver debugging enabled.

> What I had tested was reverting the recent ca-certificates-java change,
> i.e. switching the dependency on
>   openjdk-8-jre-headless | java7-runtime-headless
> back to
>   openjdk-7-jre-headless | java7-runtime-headless
> (or similar)
> That change was made later than the one in openjdk-8 and it proved to be
> sufficient in my piuparts test to fix^Wnot activate that trigger cycle.

I was just saying this on IRC:

“should I try to reinstate ca-certificates-java's old dependencies and
compare? from my initial bug report, that's the change in the archive
that led to the regression.”

and mentioned earlier that given the old dependencies have an OR anyway,
we shouldn't be introducing an uninstallable package. This would have
the nice effect of being a solution that can be implemented in hours
instead of days (given openjdk-8's build time). This doesn't mean we
should jump the gun anyway…

I'll report back.


KiBi.


signature.asc
Description: Digital signature

Re: Bug#864597: upgrade-reports: jessie -> stretch: gnome fails to upgrade: cycle found while processing triggers

[Andreas Beckmann]

On 2017-06-15 10:02, Michael Biebl wrote:
> Am 12.06.2017 um 20:33 schrieb Andreas Beckmann:
>> Switching desktop-file-utils or/and shared-mime-info to -noawait
>> triggers does not solve the problem.
> 
> So afaics there is nothing that can be done from the Debian GNOME team
> side, right?

You could add a Breaks: tzdata-java to some library deep in the gnome
stack (so that it gets a high score from apt) ... that could serve as a
workaround as well.


Andreas

Re: Bug#864597: upgrade-reports: jessie -> stretch: gnome fails to upgrade: cycle found while processing triggers

[Andreas Beckmann]

On 2017-06-15 15:16, Cyril Brulebois wrote:
> Julien Cristau  (2017-06-15):
>> It sounds like openjdk-8 added two Breaks recently, one or both of
>> which are causing trouble, and none of which fix anything as bad as
>> this.  So I think we should remove the Breaks on tzdata-java from
>> openjdk-8-jdk-headless, and remove the Breaks on ca-certificates-java
>> from openjdk-8-jre-headless.  Would that fix the current issue?

What I had tested was reverting the recent ca-certificates-java change,
i.e. switching the dependency on
  openjdk-8-jre-headless | java7-runtime-headless
back to
  openjdk-7-jre-headless | java7-runtime-headless
(or similar)
That change was made later than the one in openjdk-8 and it proved to be
sufficient in my piuparts test to fix^Wnot activate that trigger cycle.


Andreas

Please dak copy-installer 20170615

[Cyril Brulebois]

Hi,

FTPmasters, please sync the installer from sid to testing:

  dak copy-installer 20170615


Release team, please hint it into testing:

  unblock debian-installer/20170615
  urgent debian-installer/20170615


Also, there was no recent clean-up in the sid directory; I think we
could remove everything from 2015. Maybe also everything from 2016,
but I'm tempted to give debian-boot@ people a chance to react in case
images from 2016 should stay a bit longer. Of course this can wait
post-release, no urgency from my point of view.

For reference, full contents:

  20150422
  20150718
  20150813
  20150828
  20150911
  20151023
  20160101
  20160106
  20160516+b1
  20160516
  20160630
  20161027
  20161031
  20170112
  20170127
  20170407
  20170525
  20170608


KiBi.


signature.asc
Description: Digital signature

Re: Bug#864597: upgrade-reports: jessie -> stretch: gnome fails to upgrade: cycle found while processing triggers

[Cyril Brulebois]

Julien Cristau  (2017-06-15):
> It sounds like openjdk-8 added two Breaks recently, one or both of
> which are causing trouble, and none of which fix anything as bad as
> this.  So I think we should remove the Breaks on tzdata-java from
> openjdk-8-jdk-headless, and remove the Breaks on ca-certificates-java
> from openjdk-8-jre-headless.  Would that fix the current issue?
> 
> From what I can see #863820 is at most a normal-severity issue.  Not
> upgrading some packages is way way better than a failed upgrade.

I'm currently building an updated openjdk-8 with the attached changes
to see what the upgrade-desktop test cases would look like.

Note: I've chosen to remove the “Breaks: ${jrehl:Breaks}” line from
debian/control* so that I'm only touching these files, since d/rules
seems to only set it to tzdata-java anyway, depending on the target
dist.

I'll report the results afterwards, but as mentioned on IRC, even if
that looks good in the end, fewer than 2 days to become confident it
won't regress in other cases is really short. :(


KiBi.
diff -Nru openjdk-8-8u131-b11/debian/changelog openjdk-8-8u131-b11/debian/changelog
--- openjdk-8-8u131-b11/debian/changelog	2017-05-16 21:38:22.0 +
+++ openjdk-8-8u131-b11/debian/changelog	2017-06-15 12:57:13.0 +
@@ -1,3 +1,13 @@
+openjdk-8 (8u131-b11-2.1) unstable; urgency=high
+
+  * Non-maintainer upload.
+  * Remove recently-added Breaks which trigger dist-upgrade failures from
+jessie to stretch for some desktop tasks. Closes: #864597.
+- openjdk-8-jdk-headless → ${jrehl:Breaks}
+- openjdk-8-jre-headless → tzdata-java
+
+ -- Cyril Brulebois   Thu, 15 Jun 2017 12:57:13 +
+
 openjdk-8 (8u131-b11-2) unstable; urgency=medium
 
   * Tighten dependency on libatk-wrapper-java-jni. Closes: #862508.
diff -Nru openjdk-8-8u131-b11/debian/control openjdk-8-8u131-b11/debian/control
--- openjdk-8-8u131-b11/debian/control	2017-05-16 21:36:52.0 +
+++ openjdk-8-8u131-b11/debian/control	2017-06-15 12:57:13.0 +
@@ -30,7 +30,6 @@
   java5-sdk-headless, java6-sdk-headless,
   java7-sdk-headless, java8-sdk-headless,
 Replaces: openjdk-8-jdk (<< 8u72-b15-4),
-Breaks: ${jrehl:Breaks}
 Description: OpenJDK Development Kit (JDK) (headless)
  OpenJDK is a development environment for building applications,
  applets, and components using the Java programming language.
@@ -56,7 +55,6 @@
   java7-runtime-headless, java8-runtime-headless,
   ${defaultvm:Provides}, ${jvm:Provides}
 Breaks: oracle-java8-installer (<< 8u77+8u77arm-1),
-  ca-certificates-java (<< 20160321~)
 Description: OpenJDK Java runtime, using ${vm:Name} (headless)
  Minimal Java runtime - needed for executing non GUI Java programs,
  using ${vm:Name}.
diff -Nru openjdk-8-8u131-b11/debian/control.in openjdk-8-8u131-b11/debian/control.in
--- openjdk-8-8u131-b11/debian/control.in	2017-04-08 19:44:58.0 +
+++ openjdk-8-8u131-b11/debian/control.in	2017-06-15 12:57:13.0 +
@@ -30,7 +30,6 @@
   java5-sdk-headless, java6-sdk-headless,
   java7-sdk-headless, java8-sdk-headless,
 Replaces: @basename@-jdk (<< 8u72-b15-4),
-Breaks: ${jrehl:Breaks}
 Description: OpenJDK Development Kit (JDK) (headless)
  OpenJDK is a development environment for building applications,
  applets, and components using the Java programming language.
@@ -56,7 +55,6 @@
   java7-runtime-headless, java8-runtime-headless,
   ${defaultvm:Provides}, ${jvm:Provides}
 Breaks: oracle-java8-installer (<< 8u77+8u77arm-1),
-  ca-certificates-java (<< 20160321~)
 Description: OpenJDK Java runtime, using ${vm:Name} (headless)
  Minimal Java runtime - needed for executing non GUI Java programs,
  using ${vm:Name}.


signature.asc
Description: Digital signature

Re: Bug#864597: upgrade-reports: jessie -> stretch: gnome fails to upgrade: cycle found while processing triggers

[Julien Cristau]

On 06/15/2017 10:02 AM, Michael Biebl wrote:
> Hi
> 
> Am 12.06.2017 um 20:33 schrieb Andreas Beckmann:
>> Switching desktop-file-utils or/and shared-mime-info to -noawait
>> triggers does not solve the problem.
> 
> So afaics there is nothing that can be done from the Debian GNOME team
> side, right?
> 
>> I can confirm that the ca-certificates-java change triggered the bug
>> (i.e. backing it out makes the problem go away, but this is not a solution).
>>
>> I can also confirm that the changes I suggested in #863820 (adding
>> adding Breaks: tzdata-java to gcc-6-base) would fix this upgrade path.
>> It shakes the upgrade order quite well for this case ...
>> (I can post the log if someone is interested.)
>> According to piuparts, the upgrade paths of about 860 packages in
>> jessie2stretch-rcmd would be affected by this change (because
>> tzdata-java gets installed in jessie). These can be retested quickly.
> 
> I see that #863820 is still open and apparently also affects other
> upgrade paths. Shouldn't this be bumped to RC?
> What are we going to do about this? A failure to dist-upgrade our
> default desktop environment is pretty bad.
> Is there some known workaround which we could document in the release
> notes at least?
> From what I can see, wouldn't it be better to drop the the Breaks:
> tzdata-java from openjdk-8-jdk-headless again?
> 
It sounds like openjdk-8 added two Breaks recently, one or both of which
are causing trouble, and none of which fix anything as bad as this.  So
I think we should remove the Breaks on tzdata-java from
openjdk-8-jdk-headless, and remove the Breaks on ca-certificates-java
from openjdk-8-jre-headless.  Would that fix the current issue?

>From what I can see #863820 is at most a normal-severity issue.  Not
upgrading some packages is way way better than a failed upgrade.

Cheers,
Julien

Re: d-i-netboot-images package outdated (was Re: Debian Installer Stretch RC 5 release)

[Cyril Brulebois]

Andrew M.A. Cater  (2017-06-14):
> Seeing the post on PXE for UEFI on planet.debian.org and noting that
> you're planning another d-i release.

Please mention a direct URL, planet has a volatile content… Maybe you're
referring to this?
  http://sven.stormbind.net/blog/posts/deb_uefi_pxe_install_hpe_dl120/

> Is there any chance of putting in the symlink in d-i that will link 
> bootnetx64.efi in the same way as pxelinux as below
> 
> Also in netboot.tar.gz similarly
> 
> bootnetx64.efi -> debian-installer/amd64/bootnetx64.efi
> 
> This is exactly the way that pexlinux.0 and pxelinux.cfg are already
> linked and would be a trivial change that would allow UEFI booting
> more readily.

It seems that's a more detailed version of what you mentioned on May
27th following a release announcement. That really should be turned into
a bug report against src:debian-installer; I'm assuming you could try to
test a patch, which would likely modify build/config/x86.cfg there.

As for stretch r0, this is obviously too late, but we'll get a chance to
backport fixes from buster for point releases.


KiBi.


signature.asc
Description: Digital signature

Re: Bug#864457: Bug#864536: missing kernel modules in D-I sd-card images

[Cyril Brulebois]

Hi,

Karsten Merker  (2017-06-14):
> I have just completed a testinstall of the new "daily" build
> (hd-media offline install, debian-testing-armhf-xfce-CD-1.iso
> dated 2017-06-12, serial console, from a USB-Stick to an SD-card)
> on a Banana Pi, i.e. on a system with an AXP20x powermanagement
> controller, and everything has worked flawlessly.
> 
> I have also checked that a USB-keyboard (and the HDMI console)
> work in d-i.

This is wonderful, thanks! I had planned to upload in any cases, but
having confirmation runtime is OK as well is very nice. Just uploaded
debian-installer_20170615_source.changes accordingly.


KiBi.


signature.asc
Description: Digital signature

Re: Bug#864597: upgrade-reports: jessie -> stretch: gnome fails to upgrade: cycle found while processing triggers

[Michael Biebl]

Hi

Am 12.06.2017 um 20:33 schrieb Andreas Beckmann:
> Switching desktop-file-utils or/and shared-mime-info to -noawait
> triggers does not solve the problem.

So afaics there is nothing that can be done from the Debian GNOME team
side, right?

> I can confirm that the ca-certificates-java change triggered the bug
> (i.e. backing it out makes the problem go away, but this is not a solution).
> 
> I can also confirm that the changes I suggested in #863820 (adding
> adding Breaks: tzdata-java to gcc-6-base) would fix this upgrade path.
> It shakes the upgrade order quite well for this case ...
> (I can post the log if someone is interested.)
> According to piuparts, the upgrade paths of about 860 packages in
> jessie2stretch-rcmd would be affected by this change (because
> tzdata-java gets installed in jessie). These can be retested quickly.

I see that #863820 is still open and apparently also affects other
upgrade paths. Shouldn't this be bumped to RC?
What are we going to do about this? A failure to dist-upgrade our
default desktop environment is pretty bad.
Is there some known workaround which we could document in the release
notes at least?
From what I can see, wouldn't it be better to drop the the Breaks:
tzdata-java from openjdk-8-jdk-headless again?



-- 
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