Bug#995848: bullseye-pu: package brltty/6.3+dfsg-1+deb11u1
Package: release.debian.org Severity: normal Tags: bullseye User: release.debian@packages.debian.org Usertags: pu Hello, [ Reason ] Bug#994729 was noticed only recently: when installing Debian with sysvinit rather than systemd, Braille output wouldn't work in the X session. This was probably already happening in the Stretch & Buster releases. This is not a problem for systemd-based systems that already have a fix since october 2016. [ Impact ] Blind users that use sysvinit-based Debian systems cannot use Braille within X. [ Tests ] The original reporter of the bug tested the fix. [ Risks ] The code is trivial [ Checklist ] [X] *all* changes are documented in the d/changelog [X] I reviewed all changes and I approve them [X] attach debdiff against the package in (old)stable [X] the issue is verified as fixed in unstable [ Changes ] The change simply makes the brltty sysvinit script wait for local filesystems to be mounted before brltty can start, so that /var/lib/BrlAPI is mounted and thus the BrlAPI socket is settled in the right place, for polkit authentication to be working and thus the X screen reader able to use it to display Braille output. diff -Nru brltty-6.3+dfsg/debian/brltty.init brltty-6.3+dfsg/debian/brltty.init --- brltty-6.3+dfsg/debian/brltty.init 2021-01-28 17:18:34.0 +0100 +++ brltty-6.3+dfsg/debian/brltty.init 2021-09-20 23:37:07.0 +0200 @@ -1,7 +1,7 @@ #! /bin/sh ### BEGIN INIT INFO # Provides: brltty -# Required-Start:mountkernfs +# Required-Start:mountkernfs $local_fs # Required-Stop: # Should-Start: udev # Should-Stop: diff -Nru brltty-6.3+dfsg/debian/changelog brltty-6.3+dfsg/debian/changelog --- brltty-6.3+dfsg/debian/changelog2021-01-28 17:45:12.0 +0100 +++ brltty-6.3+dfsg/debian/changelog2021-09-20 23:37:34.0 +0200 @@ -1,3 +1,11 @@ +brltty (6.3+dfsg-1+deb11u1) bullseye; urgency=medium + + [ Gregory Nowak ] + * brltty.init: Make it wait for $local_fs, like the systemd service does. +(Closes: Bug#994729) + + -- Samuel Thibault Mon, 20 Sep 2021 23:37:34 +0200 + brltty (6.3+dfsg-1) unstable; urgency=medium * New upstream release. diff -Nru brltty-6.3+dfsg/debian/salsa-ci.yml brltty-6.3+dfsg/debian/salsa-ci.yml --- brltty-6.3+dfsg/debian/salsa-ci.yml 2021-01-28 17:18:34.0 +0100 +++ brltty-6.3+dfsg/debian/salsa-ci.yml 2021-09-20 23:37:34.0 +0200 @@ -7,4 +7,7 @@ # Disable reprotest until salsa-ci-team/pipeline#26 is resolved SALSA_CI_DISABLE_REPROTEST: 1 + SALSA_CI_DISABLE_VERSION_BUMP: 1 + RELEASE: bullseye + # vim: ts=2 sw=2 et sts=2 ft=yaml
Bug#995636: OpenSSL 3.0 - Apache 2.0 vs GPL 2 (Re: Bug#995636: transition: openssl)
Paul Wise writes: > On Wed, Oct 6, 2021 at 11:30 AM Luca Boccassi wrote: >> On Tue, 2021-10-05 at 21:04 +0200, Sebastian Andrzej Siewior wrote: >> > Additionally OpenSSL is considered system library, see >> > https://bugs.debian.org/951780 >> > https://bugs.debian.org/972181 >> >> Even if that interpretation holds, and it's not a universal >> interpretation (eg: lawyers from Canonical strongly disagree as far as >> I know), again that applies to first-party binaries only as far as I >> understand. It's not as clear-cut with libraries used by third parties. I believe Canonical also ships GPL-2-only programs linked (possibly indirectly) to OpenSSL as part of their Linux distribution these days. > As I understand it, it is meant only for binaries distributed by > parties other than the one distributing the system containing the > "system library". So third-party app distributors are fine to ignore > the incompatibility between a GPL app and a proprietary libc, but the > OS vendor can't include GPL apps linked to that proprietary libc > within their system. Debian uses many GPL-2-incompatible system libraries: for example GPL-3-or-later libraries such as libstdc++ or libgcc or gnutls[1]. Debian also ships many GPL-2-only programs using these. So if this was considered a problem, then the problem would be quite large. [1]: gnutls could be made LGPL-2.1-or-later by rewriting the GPL-3-or-later build scripts; note that GPL-2 states that "complete source code" includes "scripts used to control compilation and installation of the executable" > I believe OpenSSL 3's choice of the Apache 2 license only improves > compatibility, it doesn't reduce it. GPLv3 is supposedly compatible > with Apache 2, so GPLv3 and GPLv2+ programs are newly compatible with > OpenSSL 3. Most existing GPLv2-only programs that use OpenSSL will > have the exception anyway. This depends on what you mean by "use OpenSSL": if program use OpenSSL directly, maybe; if programs link to OpenSSL indirectly, for example via dependency chains such as my-program -> some-library -> some-library-implementing-some-network-protocol -> OpenSSL this becomes increasingly unlikely the longer the chain is. Also people seem to keep adding TLS support to more and more libraries, so such a dependency can just silently appear later. Python programs using OpenSSL also usually don't have such an exception. , Ansgar
Processed: your mail
Processing commands for cont...@bugs.debian.org: > tags 994416 - moreinfo Bug #994416 [release.debian.org] transition: console-bridge Removed tag(s) moreinfo. > End of message, stopping processing here. Please contact me if you need assistance. -- 994416: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994416 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#995636: OpenSSL 3.0 - Apache 2.0 vs GPL 2 (Re: Bug#995636: transition: openssl)
On Wed, Oct 6, 2021 at 11:30 AM Luca Boccassi wrote: > On Tue, 2021-10-05 at 21:04 +0200, Sebastian Andrzej Siewior wrote: > > Additionally OpenSSL is considered system library, see > > https://bugs.debian.org/951780 > > https://bugs.debian.org/972181 > > Even if that interpretation holds, and it's not a universal > interpretation (eg: lawyers from Canonical strongly disagree as far as > I know), again that applies to first-party binaries only as far as I > understand. It's not as clear-cut with libraries used by third parties. As I understand it, it is meant only for binaries distributed by parties other than the one distributing the system containing the "system library". So third-party app distributors are fine to ignore the incompatibility between a GPL app and a proprietary libc, but the OS vendor can't include GPL apps linked to that proprietary libc within their system. https://lists.debian.org/debian-devel/2020/10/msg00168.html > The core issue as always is uncertainty: any time there are doubts and > conflicting interpretations, we all lose, especially our users, and > especially those that are then forced to have awkward conversations > with their corporate lawyers. Which is why it's really unfortunate that > , in order to fix compatibility issues with the GPL, among all the > permissive licenses available out there, the OpenSSL project picked the > _one_ that has serious compatibility questions with the GPL :-( I believe OpenSSL 3's choice of the Apache 2 license only improves compatibility, it doesn't reduce it. GPLv3 is supposedly compatible with Apache 2, so GPLv3 and GPLv2+ programs are newly compatible with OpenSSL 3. Most existing GPLv2-only programs that use OpenSSL will have the exception anyway. -- bye, pabs https://wiki.debian.org/PaulWise
Bug#995823: bullseye-pu: package kodi/2:19.2+dfsg1-1~deb11u1 (pre-upload unblock bug)
Package: release.debian.org
Severity: normal
Tags: bullseye
User: release.debian@packages.debian.org
Usertags: pu
[ Reason ]
This is a second point release of Kodi 19 "Matrix".
It consists of 69 commits, closing 40 upstream bugs.
Most notable bugs fixed include 8 PVR issues, that led to Kodi crashes
under certain circumstances, and 4 fixes for Kodi's default skin, Estuary.
Another must-have bugfix for users controlling their Kodi set-ups remotely
is the proper handling of partial websocket messages.
Debian packaging changes requested by users include the patch adding metainfo
file to /usr/share/metainfo, needed by GNOME 40 integration.
Apart from that, translations of i10n were updated to fix users' complaints.
These changes produce a lot of changes in .po files, so I filtered the debdiff
as follows to get rid of noise not related to code:
filterdiff kodi_19.1+dfsg2-2_19.2+dfsg1-1.debdiff \
-x "*/addons/*.xml" \
-x "*/addons/*.po" \
-x "*/cmake/scripts/windows/*" \
-x "*/docs/*" \
-x "*/Changelog" \
-x "*/Makefile.in" \
-x "*/*.m4" \
-x "*/configure" \
-x "*/msvc/*" \
-x "*/media/*" \
-x "*/system/*" \
-x "*/tools/buildsteps/windows/*" \
-x "*/xbmc/cores/VideoPlayer/VideoRenderers/windows/*" \
-x "*/xbmc/windowing/win10/*" \
-x "*/xbmc/windowing/windows/*" \
1>kodi_19.1+dfsg2-2_19.2+dfsg1-1.filterdiff
[ Impact ]
Users receive fixes for problems reported upstream
[ Tests ]
Automated tests + manual testing by Kodi users
[ Risks ]
The struct release policy of upstream ensures no breaking
changes are allowed past BETA releases. Point releases
bring only bugfixes and security fixes, so risk is low.
Furthermore, I have become the official member of Team Kodi!
That should contribute in the mitigation of risks :)
[ Checklist ]
[x] *all* changes are documented in the d/changelog
[x] I reviewed all changes and I approve them
[x] attach debdiff against the package in (old)stable
[x] the issue is verified as fixed in unstable
[ Changes ]
Here is the outline of changes merged in 19.2:
https://github.com/xbmc/xbmc/pull/20224 ('Bump to 19.2. final'): 1 commit(s)
- "Bump to 19.2. final"
https://github.com/xbmc/xbmc/pull/20189 ('[CGUIDialogVolumeBar] Fix dialog not
updating values if smartredraw i…'): 1 commit(s)
- "[CGUIDialogVolumeBar] Fix dialog not updating values if smartredraw is
enabled"
https://github.com/xbmc/xbmc/pull/20185 ('[Backport] Sync game controllers for
language updates'): 1 commit(s)
- "Sync game controllers for language updates"
https://github.com/xbmc/xbmc/pull/20178 ('[Matrix] PVR: fix "Delete
permanently" of recordings from trash'): 1 commit(s)
- "PVR: fix "Delete permanently" of recordings from trash"
https://github.com/xbmc/xbmc/pull/20161 ('[Backport][linux] Use posix_memalign
to implement AlignedMalloc'): 1 commit(s)
- "[linux] Use posix_memalign to implement AlignedMalloc"
https://github.com/xbmc/xbmc/pull/20140 ('[Backport] Websocket: handle partial
messages'): 1 commit(s)
- "Websocket: handle partial messages"
https://github.com/xbmc/xbmc/pull/20119 ('[Matrix][PVR] Search missing channel
icons job must be executed by PVR manage…'): 1 commit(s)
- "[PVR] Search missing channel icons job must be executed by PVR manager
thread to avoid races in complex restart scenarios."
https://github.com/xbmc/xbmc/pull/20116 ('[Matrix][Estuary] PVR Guide window:
Truncated channel names should scroll whe…'): 1 commit(s)
- "[Estuary] PVR Guide window: Truncated channel names should scroll when
focused."
https://github.com/xbmc/xbmc/pull/20115 ('[Matrix][Estuary] PVR channel guide
dialog changes.'): 1 commit(s)
- "[Estuary] PVR channel guide dialog changes."
https://github.com/xbmc/xbmc/pull/20114 ('[Matrix][Estuary] Default PVR radio
channel icon should have transparent background'): 1 commit(s)
- "[Estuary] Default PVR radio channel icon should have transparent background."
https://github.com/xbmc/xbmc/pull/20092 ('[Matrix][PVR] Fix and simplify addon
connection state change handling.'): 1 commit(s)
- "[PVR] Fix and simplify addon connection state change handling."
https://github.com/xbmc/xbmc/pull/20060 ('[addons] sync
service.xbmc.versioncheck with repo'): 1 commit(s)
- "[addons] sync service.xbmc.versioncheck with repo"
https://github.com/xbmc/xbmc/pull/20053 ('[Music] Fix grouping discs by
subtitle if first disc has one'): 1 commit(s)
- "[MUSIC] Ensure grouping discs by title if subtitles present"
https://github.com/xbmc/xbmc/pull/20051 ('[bp][addons] Update default and SNES
controller addons'): 1 commit(s)
- "[addons] Update default and SNES controller addons"
https://github.com/xbmc/xbmc/pull/20047 ('[bp][addons] fix display logic for
official/3rd party modules'): 3 commit(s)
- "[addons] fix display logic for official/3rd party modules"
- "[cleanup] remove advanced settings 'showalldependencies' (obsolete)"
- "[addons] move sort out of for-loop that fills the vector to be sorted"
https://github.com/xbmc/xbmc/pull/20037 ('change explanation string for cddb'):
1
Bug#995823: bullseye-pu: package kodi/2:19.2+dfsg1-1~deb11u1 (pre-upload unblock bug)
Hi Adam! Sorry for confusion! I have prepared the release which will first go into unstable (and after several days, to testing). I also want this release in stable, because it is a bugfix point release fixing a lot of user reports. So I decided to file the pre-unblock bug for stable upload just like I did at freeze time. I want to be sure the Stable Release Managers accept it. The version in stable will be kodi/2:19.2+dfsg1-1~deb11u1 as Mattia suggested, but it will differ from kodi/2:19.2+dfsg1-1 targeting unstable only by an entry in d/changelog. Hope I was clear this time! :) Cheers! -- Vasyl Gello == Certified SolidWorks Expert Mob.:+380 (98) 465 66 77 E-Mail: vasek.ge...@gmail.com Skype: vasek.gello == 호랑이는 죽어서 가죽을 남기고 사람은 죽어서 이름을 남긴다
Processed: Re: Bug#995823: bullseye-pu: package kodi/2:19.2+dfsg1-1~deb11u1 (pre-upload unblock bug)
Processing control commands: > tags -1 + moreinfo Bug #995823 [release.debian.org] bullseye-pu: package kodi/2:19.2+dfsg1-1~deb11u1 (pre-upload unblock bug) Added tag(s) moreinfo. -- 995823: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995823 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#995823: bullseye-pu: package kodi/2:19.2+dfsg1-1~deb11u1 (pre-upload unblock bug)
Control: tags -1 + moreinfo On Wed, 2021-10-06 at 13:39 +, Vasyl Gello wrote: > Please unblock package kodi > That's not what you mean if the subject is accurate. But see below. > [ Reason ] > > This is a second point release of Kodi 19 "Matrix". > [...] > [ Checklist ] > [x] all changes are documented in the d/changelog > [x] I reviewed all changes and I approve them > [x] attach debdiff against the package in testing That's the checklist for an unblock request, i.e. for migrating a package from unstable to testing, not an update to stable, which is a p-u bug. Which are you actually requesting? The metadata is for one sort of request while the content is for another. If you're actually asking about an update to stable then the checklist is: [ Checklist ] [ ] *all* changes are documented in the d/changelog [ ] I reviewed all changes and I approve them [ ] attach debdiff against the package in stable [ ] the issue is verified as fixed in unstable This clearly isn't a changelog entry for a stable update: +kodi (2:19.2+dfsg1-1) unstable; urgency=medium + + * New upstream version 19.2+dfsg1 + * Restrict watchfile to current Debian stable codename + * Bump standard version + * Refresh patches + * Install package metainfo + + -- Vasyl Gello Wed, 06 Oct 2021 10:59:56 + + 2:19.2 also isn't even in unstable yet, which adds to my confusion. [...] > [ Other info ] > > unblock kodi/2:19.2+dfsg1-1~deb11u1 Unblock hints (and indeed, hints in general) are for testing. They have nothing to do with updates to (old)stable. If you're actually talking about an upload to unstable, then as we're outside of freeze and this upload wouldn't cause a transition so far as I can see, then you don't need to request the Release Team's permission to upload. Regards, Adam
Bug#995277: marked as done (unblock: golang-github-klauspost-compress/1.11.7-2)
Your message dated Wed, 6 Oct 2021 09:52:04 -0400 with message-id and subject line Package has migrated has caused the Debian Bug report #995277, regarding unblock: golang-github-klauspost-compress/1.11.7-2 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 995277: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995277 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package golang-github-klauspost-compress The problem is with autopkgtest, on armel and armhf, the test machines frequently run out of memory when executing the extensive test suite. I suggest the folling hints: force-badtest golang-github-klauspost-compress/*/armhf force-badtest golang-github-klauspost-compress/*/armel (not sure what's the difference between /*/ and /all/ is). Thanks for your help! --- End Message --- --- Begin Message --- now in testing. Thanks for your input! -- regards, Reinhard --- End Message ---
Bug#995823: bullseye-pu: package kodi/2:19.2+dfsg1-1~deb11u1 (pre-upload unblock bug)
Package: release.debian.org
Severity: normal
Tags: bullseye
User: release.debian@packages.debian.org
Usertags: pu
Please unblock package kodi
[ Reason ]
This is a second point release of Kodi 19 "Matrix".
It consists of 69 commits, closing 40 upstream bugs.
Most notable bugs fixed include 8 PVR issues, that led to Kodi crashes
under certain circumstances, and 4 fixes for Kodi's default skin, Estuary.
Another must-have bugfix for users controlling their Kodi set-ups remotely
is the proper handling of partial websocket messages.
Debian packaging changes requested by users include the patch adding metainfo
file to /usr/share/metainfo, needed by GNOME 40 integration.
Apart from that, translations of i10n were updated to fix users' complaints.
These changes produce a lot of changes in .po files, so I filtered the debdiff
as follows to get rid of noise not related to code:
filterdiff kodi_19.1+dfsg2-2_19.2+dfsg1-1.debdiff \
-x "*/addons/*.xml" \
-x "*/addons/*.po" \
-x "*/cmake/scripts/windows/*" \
-x "*/docs/*" \
-x "*/Changelog" \
-x "*/Makefile.in" \
-x "*/*.m4" \
-x "*/configure" \
-x "*/msvc/*" \
-x "*/media/*" \
-x "*/system/*" \
-x "*/tools/buildsteps/windows/*" \
-x "*/xbmc/cores/VideoPlayer/VideoRenderers/windows/*" \
-x "*/xbmc/windowing/win10/*" \
-x "*/xbmc/windowing/windows/*" \
1>kodi_19.1+dfsg2-2_19.2+dfsg1-1.filterdiff
[ Impact ]
Users receive fixes for problems reported upstream
[ Tests ]
Automated tests + manual testing by Kodi users
[ Risks ]
The struct release policy of upstream ensures no breaking
changes are allowed past BETA releases. Point releases
bring only bugfixes and security fixes, so risk is low.
Furthermore, I have become the official member of Team Kodi!
That should contribute in the mitigation of risks :)
[ Checklist ]
[x] all changes are documented in the d/changelog
[x] I reviewed all changes and I approve them
[x] attach debdiff against the package in testing
[ Changes ]
Here is the outline of changes merged in 19.2:
https://github.com/xbmc/xbmc/pull/20224 ('Bump to 19.2. final'): 1 commit(s)
- "Bump to 19.2. final"
https://github.com/xbmc/xbmc/pull/20189 ('[CGUIDialogVolumeBar] Fix dialog not
updating values if smartredraw i…'): 1 commit(s)
- "[CGUIDialogVolumeBar] Fix dialog not updating values if smartredraw is
enabled"
https://github.com/xbmc/xbmc/pull/20185 ('[Backport] Sync game controllers for
language updates'): 1 commit(s)
- "Sync game controllers for language updates"
https://github.com/xbmc/xbmc/pull/20178 ('[Matrix] PVR: fix "Delete
permanently" of recordings from trash'): 1 commit(s)
- "PVR: fix "Delete permanently" of recordings from trash"
https://github.com/xbmc/xbmc/pull/20161 ('[Backport][linux] Use posix_memalign
to implement AlignedMalloc'): 1 commit(s)
- "[linux] Use posix_memalign to implement AlignedMalloc"
https://github.com/xbmc/xbmc/pull/20140 ('[Backport] Websocket: handle partial
messages'): 1 commit(s)
- "Websocket: handle partial messages"
https://github.com/xbmc/xbmc/pull/20119 ('[Matrix][PVR] Search missing channel
icons job must be executed by PVR manage…'): 1 commit(s)
- "[PVR] Search missing channel icons job must be executed by PVR manager
thread to avoid races in complex restart scenarios."
https://github.com/xbmc/xbmc/pull/20116 ('[Matrix][Estuary] PVR Guide window:
Truncated channel names should scroll whe…'): 1 commit(s)
- "[Estuary] PVR Guide window: Truncated channel names should scroll when
focused."
https://github.com/xbmc/xbmc/pull/20115 ('[Matrix][Estuary] PVR channel guide
dialog changes.'): 1 commit(s)
- "[Estuary] PVR channel guide dialog changes."
https://github.com/xbmc/xbmc/pull/20114 ('[Matrix][Estuary] Default PVR radio
channel icon should have transparent background'): 1 commit(s)
- "[Estuary] Default PVR radio channel icon should have transparent background."
https://github.com/xbmc/xbmc/pull/20092 ('[Matrix][PVR] Fix and simplify addon
connection state change handling.'): 1 commit(s)
- "[PVR] Fix and simplify addon connection state change handling."
https://github.com/xbmc/xbmc/pull/20060 ('[addons] sync
service.xbmc.versioncheck with repo'): 1 commit(s)
- "[addons] sync service.xbmc.versioncheck with repo"
https://github.com/xbmc/xbmc/pull/20053 ('[Music] Fix grouping discs by
subtitle if first disc has one'): 1 commit(s)
- "[MUSIC] Ensure grouping discs by title if subtitles present"
https://github.com/xbmc/xbmc/pull/20051 ('[bp][addons] Update default and SNES
controller addons'): 1 commit(s)
- "[addons] Update default and SNES controller addons"
https://github.com/xbmc/xbmc/pull/20047 ('[bp][addons] fix display logic for
official/3rd party modules'): 3 commit(s)
- "[addons] fix display logic for official/3rd party modules"
- "[cleanup] remove advanced settings 'showalldependencies' (obsolete)"
- "[addons] move sort out of for-loop that fills
Bug#995636: OpenSSL 3.0 - Apache 2.0 vs GPL 2 (Re: Bug#995636: transition: openssl)
On Tue, 2021-10-05 at 21:04 +0200, Sebastian Andrzej Siewior wrote: > On 2021-10-05 20:03:49 [+0200], Michael Biebl wrote: > > Hi Kurt, hi Luca, hi everyone, > Hi Michael, > > > That said, I'm not a lawyer and reading license texts hurts my brain. > > So my goal is is mainly to raise awareness of this issue and seek input from > > the community. > > GPL code which linked against OpenSSL usually has a "gpl-exception > clause for OpenSSL". This should be still accepted since it refers > specifically to OpenSSL. Many projects do not have that. Also to be extremely pedantic it needs to be checked if it just references OpenSSL as a project, or specifically the OpenSSL license which is a specific and well defined document: https://spdx.org/licenses/OpenSSL.html AFAIK there's no "standard" clause, everyone uses their own wording, more or less. More importantly, as far as I understand and I was told recently these are not transitive - ie, it's fine for an executable, but if it concerns a library, it does not "transfer" to external programs linking to that library. > Additionally OpenSSL is considered system library, see > https://bugs.debian.org/951780 > https://bugs.debian.org/972181 Even if that interpretation holds, and it's not a universal interpretation (eg: lawyers from Canonical strongly disagree as far as I know), again that applies to first-party binaries only as far as I understand. It's not as clear-cut with libraries used by third parties. The core issue as always is uncertainty: any time there are doubts and conflicting interpretations, we all lose, especially our users, and especially those that are then forced to have awkward conversations with their corporate lawyers. Which is why it's really unfortunate that , in order to fix compatibility issues with the GPL, among all the permissive licenses available out there, the OpenSSL project picked the _one_ that has serious compatibility questions with the GPL :-( But of course this doesn't mean we shouldn't move to the new version, quite the contrary - I'll simply be careful about the projects I am involved in and what it means for them and their license clarity, and what I can do to make it better, if anything. -- Kind regards, Luca Boccassi signature.asc Description: This is a digitally signed message part
Bug#994086: transition: netcdf
On 2021-10-06 06:42:42, Sebastiaan Couwenberg wrote: > Testing still lacks a few rebuilt packages for this transition. > > labplot should migrated in two days. > > pymol will be rebuilt in unstable after it gets out the DELAYED > according to #995666, although I don't see it at > > ftp://ftp.upload.debian.org/pub/UploadQueue/DELAYED/ You can find the deferred queue at https://ftp-master.debian.org/deferred.html Cheers > > magics++ & metkit are blocked by eckit which is no longer built on 32bit > architectures, and is waiting for ftpmaster to act on #993624. > > Kind Regards, > > Bas > > -- > GPG Key ID: 4096R/6750F10AE88D4AF1 > Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1 -- Sebastian Ramacher
Bug#995806: nmu: js-of-ocaml_3.8.0-2
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: binnmu nmu js-of-ocaml_3.8.0-2 . ANY . unstable . -m "rebuild against menhir 20210929" libjs-of-ocaml-dev is no longer installable and needs to be rebuild against the version of menhir in unstable. This is also blocking the migration of menhir to testing. -Ralf.
