Bug#1072856: bookworm-pu: package djangorestframework/3.14.0-2
Package: release.debian.org Severity: normal Tags: bookworm X-Debbugs-Cc: djangorestframew...@packages.debian.org Control: affects -1 + src:djangorestframework User: release.debian@packages.debian.org Usertags: pu [ Reason ] The user Simon Lyngshede spottet an issue with version 3.14.0-2 in bookworm which can result in a HTML error 500 in the priject that is using this version as the Debian package is missing the file bootstrap-tweaks.css in the static folder. https://bugs.debian.org/1068747 This is happen due a to agressive removing of existing CSS files while package build. [ Impact ] The potential impact is limited and no data loss will happen, but the Django application will simply not work and throw an error 500 if the CSS file can not be found. [ Tests ] Currently there are no upstream or autopkgtests which will detect such a missing file. Upstream will probably never create such a test because they ship the needed files within the source. [ Risks ] The risk of a potential data loss isn't existing, but the application that is using that package might loose all of it's functionality. [ 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 itself is rather simple, it's a one line fix in debian/rules. Please see below the output of debdiff. [ Other info ] Currently nothing I'm aware of that is needed to get mentioned here. -- Regards Carsten $ debdiff ../djangorestframework_3.14.0-2.dsc ../djangorestframework_3.14.0-2+deb12u1.dsc diff -Nru djangorestframework-3.14.0/debian/changelog djangorestframework-3.14.0/debian/changelog --- djangorestframework-3.14.0/debian/changelog 2023-01-31 12:59:37.0 +0100 +++ djangorestframework-3.14.0/debian/changelog 2024-06-09 08:20:01.0 +0200 @@ -1,3 +1,14 @@ +djangorestframework (3.14.0-2+deb12u1) bookworm; urgency=medium + + [ Carsten Schoenert ] + * [0e3d1fc] d/gbp.conf: Pick up some defaults, adjust to debian/bookworm + + [ Simon Lyngshede ] + * [7867bee] d/rules: Don't exclude bootstrap-tweaks.css file +(Closes: #1068747) + + -- Carsten Schoenert Sun, 09 Jun 2024 08:20:01 +0200 + djangorestframework (3.14.0-2) unstable; urgency=medium * Team upload diff -Nru djangorestframework-3.14.0/debian/gbp.conf djangorestframework-3.14.0/debian/gbp.conf --- djangorestframework-3.14.0/debian/gbp.conf 2023-01-31 12:59:37.0 +0100 +++ djangorestframework-3.14.0/debian/gbp.conf 2024-06-09 08:19:45.0 +0200 @@ -1,2 +1,11 @@ [DEFAULT] -debian-branch=debian/master +compression = gz +debian-branch = debian/bookworm +upstream-branch = upstream +pristine-tar = True + +[pq] +patch-numbers = False + +[dch] +id-length = 7 diff -Nru djangorestframework-3.14.0/debian/rules djangorestframework-3.14.0/debian/rules --- djangorestframework-3.14.0/debian/rules 2023-01-31 12:59:37.0 +0100 +++ djangorestframework-3.14.0/debian/rules 2024-06-09 08:19:45.0 +0200 @@ -21,7 +21,7 @@ # Don't embed what's already provided elsewhere $(RM) debian/python3-djangorestframework/usr/lib/python3/dist-packages/rest_framework/static/rest_framework/fonts/* $(RM) debian/python3-djangorestframework/usr/lib/python3/dist-packages/rest_framework/static/rest_framework/css/font-awesome*.css - $(RM) debian/python3-djangorestframework/usr/lib/python3/dist-packages/rest_framework/static/rest_framework/css/bootstrap*.css + $(RM) debian/python3-djangorestframework/usr/lib/python3/dist-packages/rest_framework/static/rest_framework/css/bootstrap*.min.css $(RM) debian/python3-djangorestframework/usr/lib/python3/dist-packages/rest_framework/static/rest_framework/css/prettify*.css $(RM) debian/python3-djangorestframework/usr/lib/python3/dist-packages/rest_framework/static/rest_framework/js/bootstrap*.js $(RM) debian/python3-djangorestframework/usr/lib/python3/dist-packages/rest_framework/static/rest_framework/js/jquery*.js
Bug#1036722: unblock: thunderbird/1:102.11.0-1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock X-Debbugs-Cc: thunderb...@packages.debian.org Control: affects -1 + src:thunderbird Please unblock package thunderbird [ Reason ] Upstream released a new ESR version of Thunderbird which included as usual some CVE fixes a few days ago. https://www.mozilla.org/en-US/security/advisories/mfsa2023-18/ [ Impact ] Users of bookworm would need to stay with the previous release 1:102.10.0-1 without the latest fixes. [ Tests ] The package build has a small set of tests which are successfully succeeded. I also use the new version on various devices without any problems. [ Risks ] The risk is nearly zero, the same version was build for Debian stable and oldstable are in the archive and are used without reported problems. [ Checklist ] [x] all changes are documented in the d/changelog [x] I reviewed all changes and I approve them [ ] attach debdiff against the package in testing [ Other info ] I don't have added a debdiff as this would be a rather hughe diff due the included changes from the underlying changes from firefox. The changes between 102.10.0 and 102.11.0 can be viewed on Salsa on https://salsa.debian.org/mozilla-team/thunderbird/-/commit/0626d725e05e7c6a4ef4fb204dddbbd0d1e116c9 unblock thunderbird/1:102.11.0-1
Bug#1035334: unblock: python-selenium/4.9.0+dfsg-1
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: python-selen...@packages.debian.org
Control: affects -1 + src:python-selenium
Please unblock package python-selenium
[ Reason ]
Upstream released another round of update to address some minor updates
and fixes of the 4.x series.
>From the CHANGES files:
* Remove "shadow_root" assertion in Python bindings for Firefox (#11821)
* Simplify driver binary and driver location selecting (#11864)
* Do not pass desired caps in Safari (#11854)
* Selenium Manager get Browser Version from Options classes
* Selenium Manager use binary from Browser Options
* Adding v112 and removing v109
[ Impact ]
Users of bookworm won't get the latest fixes and adjustments, might
result in non usable functionality.
[ Tests ]
The autopkgtest succeeded and so far no bug report nor private email
communication did need to happen.
Using the new version in some of my personal scripts did not show any
problems or regressions.
[ Risks ]
I'd say the risk of introducing problems is quite zero as basically the
difference to the previous version isn't big and straight forward from
reviewing the code changes.
OTOH python-selenium is marked as key package and requires a manual
unblock due this.
[ 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
[ Other info ]
A mostly better viewable diff of the upstream changes between 4.8.3 and
4.9.0 can seen on the Salsa upstream tree.
https://salsa.debian.org/sagiru-guest/python-selenium/-/commit/02f43bac627b47adb42fac57011e2e578797cdab
unblock python-selenium/4.9.0+dfsg-1
diff -Nru python-selenium-4.8.3+dfsg/CHANGES python-selenium-4.9.0+dfsg/CHANGES
--- python-selenium-4.8.3+dfsg/CHANGES 2023-03-24 19:05:50.0 +0100
+++ python-selenium-4.9.0+dfsg/CHANGES 2023-04-21 01:41:21.0 +0200
@@ -1,3 +1,11 @@
+Selenium 4.9.0
+* Remove "shadow_root" assertion in Python bindings for Firefox (#11821)
+* Simplify driver binary and driver location selecting (#11864)
+* Do not pass desired caps in Safari (#11854)
+* Selenium Manager get Browser Version from Options classes
+* Selenium Manager use binary from Browser Options
+* Adding v112 and removing v109
+
Selenium 4.8.3
* Add fine grained control for arguments provided to service subprocesses by
passing a `popen_kw` mapping for all services.
* `Options` classes now allow `timeout` to be set partially and no longer
raise an exception when all values are not provided. (#11623)
diff -Nru python-selenium-4.8.3+dfsg/debian/changelog
python-selenium-4.9.0+dfsg/debian/changelog
--- python-selenium-4.8.3+dfsg/debian/changelog 2023-03-29 12:14:56.0
+0200
+++ python-selenium-4.9.0+dfsg/debian/changelog 2023-04-22 13:02:57.0
+0200
@@ -1,3 +1,12 @@
+python-selenium (4.9.0+dfsg-1) unstable; urgency=medium
+
+ * [02f43ba] New upstream version 4.9.0+dfsg
+ * [e4e1dcd] Use a not so usual port for chromium test
+Use port 8088 instead of 8000, the port 8000 might be in use already by
+some other process.
+
+ -- Carsten Schoenert Sat, 22 Apr 2023 13:02:57
+0200
+
python-selenium (4.8.3+dfsg-1) unstable; urgency=medium
* [9118276] New upstream version 4.8.3+dfsg
diff -Nru python-selenium-4.8.3+dfsg/debian/tests/test-chromium
python-selenium-4.9.0+dfsg/debian/tests/test-chromium
--- python-selenium-4.8.3+dfsg/debian/tests/test-chromium 2023-03-29
12:14:56.0 +0200
+++ python-selenium-4.9.0+dfsg/debian/tests/test-chromium 2023-04-22
13:02:57.0 +0200
@@ -2,7 +2,7 @@
set -exu
-python3 -m http.server 8000 --bind 127.0.0.1 --directory="$(pwd)" &
+python3 -m http.server 8088 --bind 127.0.0.1 --directory="$(pwd)" &
pid=$!
trap "kill $pid" EXIT
@@ -23,23 +23,26 @@
driver = webdriver.Chrome(options = chrome_options)
-print("Getting data from http://127.0.0.1:8000;)
+print("Getting data from http://127.0.0.1:8088;)
-if driver.get("http://127.0.0.1:8000;) == None:
+if driver.get("http://127.0.0.1:8088;) == None:
print("Success.")
else:
print("Failed!")
+sys.exit(1)
print("Looking for a link named 'debian/'")
link = driver.find_element(By.LINK_TEXT, "debian/")
if link.click() == None:
print("Success.")
+print()
+print("\nTest seems to be successful!\nTest was using the following HTML
data to test the Chrome webdriver.\n")
+print("--- %< ---")
+print(driver.page_source)
+print("--- >% ---")
else:
print("Failed!")
+sys.exit(1)
-print("\nTest seems to be successful!\nTe
Bug#1034046: unblock: markdown-exec/1.4.0-1
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: markdown-e...@packages.debian.org
Control: affects -1 + src:markdown-exec
Please unblock package markdown-exec
[ Reason ]
The package got rather small upstream modifications since 1.3.0 I'd like
to see in the bookworm release. Another reason is the mark as a core
package which requires a manually unblock by the RT.
An diff about the differences between 1.3.0 and 1.4.0 can be viewed on
the project GitHub website.
https://github.com/pawamoy/markdown-exec/compare/1.3.0...1.4.0
[ Impact ]
The user can use a improved Session handling which was added to 1.4.0.
[ Tests ]
All the tests while package build and within the autopkgtest run
succeeded. Using the newer Debian package in local projects working just
fine.
[ Risks ]
The risks are quite low as only extra functionality was added and no
changes did happen to the existing code.
No issues got reported since the upload of 1.4.0-1 almost 3 weeks ago.
[ 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
diff -Nru markdown-exec-1.3.0/CHANGELOG.md markdown-exec-1.4.0/CHANGELOG.md
--- markdown-exec-1.3.0/CHANGELOG.md2023-02-18 13:54:04.0 +0100
+++ markdown-exec-1.4.0/CHANGELOG.md2023-03-15 21:43:25.0 +0100
@@ -5,6 +5,14 @@
and this project adheres to [Semantic
Versioning](http://semver.org/spec/v2.0.0.html).
+## [1.4.0](https://github.com/pawamoy/markdown-exec/releases/tag/1.4.0) -
2023-03-15
+
+[Compare with
1.3.0](https://github.com/pawamoy/markdown-exec/compare/1.3.0...1.4.0)
+
+### Features
+
+- Sessions: persist and reuse state for Python and Pycon code blocks
([a8fef5e](https://github.com/pawamoy/markdown-exec/commit/a8fef5e90b1d7165e16ff5afe4b84e8441503098)
by Timothée Mazzucotelli). [Issue
#16](https://github.com/pawamoy/markdown-exec/issues/16)
+
## [1.3.0](https://github.com/pawamoy/markdown-exec/releases/tag/1.3.0) -
2023-02-18
[Compare with 1.2.0](https://github.com/pawamoy/markdown-exec/compare/1.2.0...1.3.0)
diff -Nru markdown-exec-1.3.0/debian/changelog
markdown-exec-1.4.0/debian/changelog
--- markdown-exec-1.3.0/debian/changelog2023-02-27 12:21:30.0
+0100
+++ markdown-exec-1.4.0/debian/changelog2023-03-19 07:26:01.0
+0100
@@ -1,3 +1,9 @@
+markdown-exec (1.4.0-1) unstable; urgency=medium
+
+ * [2aede3c] New upstream version 1.4.0
+
+ -- Carsten Schoenert Sun, 19 Mar 2023 07:26:01
+0100
+
markdown-exec (1.3.0-1) unstable; urgency=medium
* [8a80096] New upstream version 1.3.0
diff -Nru markdown-exec-1.3.0/docs/usage/index.md
markdown-exec-1.4.0/docs/usage/index.md
--- markdown-exec-1.3.0/docs/usage/index.md 2023-02-18 13:54:04.0
+0100
+++ markdown-exec-1.4.0/docs/usage/index.md 2023-03-15 21:43:25.0
+0100
@@ -258,6 +258,27 @@
> WARNING - markdown_exec: Execution of python code block 'print world'
exited with errors
> ```
+## Sessions
+
+Markdown Exec makes it possible to persist state between executed code blocks.
+To persist state and reuse it in other code blocks, give a session name to
your blocks:
+
+md exec="1" source="material-block" title="Sessions"
+```python exec="1" session="greet"
+def greet(name):
+print(f"Hello {name}!")
+```
+
+Hello Mushu!
+
+```python exec="1" session="greet"
+greet("Ping")
+```
+
+
+WARNING: **Limitation**
+Sessions only work with Python and Pycon syntax for now.
+
## Literate Markdown
With this extension, it is also possible to write "literate programming" Markdown.
diff -Nru markdown-exec-1.3.0/README.md markdown-exec-1.4.0/README.md
--- markdown-exec-1.3.0/README.md 2023-02-18 13:54:04.0 +0100
+++ markdown-exec-1.4.0/README.md 2023-03-15 21:43:25.0 +0100
@@ -91,5 +91,14 @@
The `exec` option will be true for every possible value except `0`, `no`, `off` and `false` (case insensitive).
+Below you can see an example of running a bash script that is expected to
+return a non-zero exit code:
+
+md
+```bash exec="1" source="tabbed-left" returncode="2"
+grep extra_css README.md && exit 2
+```
+
+
See [usage](https://pawamoy.github.io/markdown-exec/usage/) for more details,
and the [gallery](https://pawamoy.github.io/markdown-exec/gallery/) for more
examples!
diff -Nru markdown-exec-1.3.0/src/markdown_exec/formatters/base.py
markdown-exec-1.4.0/src/markdown_exec/formatters/base.py
--- markdown-exec-1.3.0/src/markdown_exec/formatters/base.py2023-02-18
13:54:04.0 +0100
+++ markdown-exec-1.4.0/src/markdown_exec/formatters/base.py2023-03-15
21:43:25.0 +0100
@@ -50,6 +50,7 @@
id: str = "", # noqa: A002,VNE003
retu
Bug#1033789: unblock: verilator/5.006-3
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: verila...@packages.debian.org
Control: affects -1 + src:verilator
Please unblock package verilator
[ Reason ]
Dimitry Shachnev reported a RC issue (#1033667) against the verilator
package which is fixed by version 5.006-3.
[ Impact ]
Without that fix users are unable to install the verilator package in
bookworm.
[ Tests ]
The verialtor package has currently no autopkgtest so only manual
testing was happen.
[ Risks ]
There are no typical risks, verilator has no reverse dependencies by
or in other packages.
[ 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
As no modification did happen in the upstream related code parts I add
the debian/ related changes directly inline.
diff --git a/debian/changelog b/debian/changelog
index 4c4d83e7..48675e51 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,20 @@
+verilator (5.006-3) unstable; urgency=medium
+
+ * Team upload
+ [ Dmitry Shachnev ]
+ * [38e486b] Move ${sphinxdoc:Built-Using} to the correct field.
+(Closes: #1033667)
+
+ [ Carsten Schoenert ]
+ * [975c120] d/gbp.conf: Adjust to debian/bookworm
+ * [e05438c] Rebuild patch queue from patch-queue branch
+Added patches:
+Fix-build-on-hppa.patch
+Fix-date-on-the-front-page-of-verilator.pdf-3956-3957.patch
+(Closes: #1030913, #1031711)
+
+ -- Carsten Schoenert Thu, 30 Mar 2023 20:05:11
+0200
+
verilator (5.006-2) unstable; urgency=medium
* Team upload
diff --git a/debian/control b/debian/control
index d02cf292..add11de7 100644
--- a/debian/control
+++ b/debian/control
@@ -31,8 +31,9 @@ Depends:
${misc:Depends},
${perl:Depends},
${shlibs:Depends},
- ${sphinxdoc:Built-Using},
${sphinxdoc:Depends},
+Built-Using:
+ ${sphinxdoc:Built-Using},
Recommends:
libsystemc-dev,
Suggests:
diff --git a/debian/gbp.conf b/debian/gbp.conf
index f892216e..f59e67e2 100644
--- a/debian/gbp.conf
+++ b/debian/gbp.conf
@@ -3,7 +3,7 @@
pristine-tar = True
# generate gz compressed orig.tar file
compression = gz
-debian-branch = debian/sid
+debian-branch = debian/bookworm
upstream-branch = upstream
[pq]
diff --git a/debian/patches/Fix-build-on-hppa.patch
b/debian/patches/Fix-build-on-hppa.patch
new file mode 100644
index ..d0a82040
--- /dev/null
+++ b/debian/patches/Fix-build-on-hppa.patch
@@ -0,0 +1,24 @@
+From: Larry Doolittle
+Date: Fri, 10 Feb 2023 21:31:44 -0800
+Subject: Fix build on hppa
+
+As supplied by John David Anglin in Debian bug #1030913
+
+Forwarded: https://github.com/verilator/verilator/pull/3954
+---
+ include/verilatedos.h | 2 ++
+ 1 file changed, 2 insertions(+)
+
+diff --git a/include/verilatedos.h b/include/verilatedos.h
+index 0e30164..7efd61e 100644
+--- a/include/verilatedos.h
b/include/verilatedos.h
+@@ -519,6 +519,8 @@ using ssize_t = uint32_t; ///< signed size_t; returned
from read()
+ # define VL_CPU_RELAX() asm volatile("nop" ::: "memory");
+ #elif defined(__aarch64__) || defined(__arm__)
+ # define VL_CPU_RELAX() asm volatile("yield" ::: "memory")
++#elif defined(__hppa__) // HPPA does not currently have yield/pause
++# define VL_CPU_RELAX() asm volatile("nop" ::: "memory")
+ #elif defined(__loongarch__) // LoongArch does not currently have yield/pause
+ # define VL_CPU_RELAX() asm volatile("nop" ::: "memory")
+ #elif defined(__mips64el__) || defined(__mips__) || defined(__mips64__) ||
defined(__mips64)
diff --git
a/debian/patches/Fix-date-on-the-front-page-of-verilator.pdf-3956-3957.patch
b/debian/patches/Fix-date-on-the-front-page-of-verilator.pdf-3956-3957.patch
new file mode 100644
index ..d4d559a2
--- /dev/null
+++ b/debian/patches/Fix-date-on-the-front-page-of-verilator.pdf-3956-3957.patch
@@ -0,0 +1,69 @@
+From: Larry Doolittle
+Date: Sun, 12 Feb 2023 20:21:03 -0800
+Subject: Fix date on the front page of verilator.pdf (#3956) (#3957)
+
+Forwarded: https://github.com/verilator/verilator/issues/3956
+---
+ docs/guide/conf.py | 27 ---
+ 1 file changed, 12 insertions(+), 15 deletions(-)
+
+diff --git a/docs/guide/conf.py b/docs/guide/conf.py
+index 04759c6..9f69245 100644
+--- a/docs/guide/conf.py
b/docs/guide/conf.py
+@@ -10,7 +10,6 @@
+ # --
+ # -- Path setup
+
+-from datetime import datetime
+ import os
+ import re
+ import sys
+@@ -24,10 +23,17 @@ def get_vlt_version():
+ filename = "../../Makefile"
+ with open(filename, "r", encoding="utf8") as fh:
+ for line in fh:
+-match = re.search(r"PACKAGE_VERSION_NUMBER *= *([a-z0-9.]+)",
line)
++match = re.search(r"PACKAGE_VERSION *= *([a-z0-9.]+) +([-0-9]+)"
Bug#1033787: unblock: python-selenium/4.8.3+dfsg-1
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: python-selen...@packages.debian.org
Control: affects -1 + src:python-selenium
Please unblock package python-selenium
[ Reason ]
There was another micro update of python-selenium which includes these
modifications (according to the documented upstream changes). Not all of
these modification are located within the Python specific flavor of
Selenium. There were added a lot more of type safe checking basically
in this update and the -doc package got Sphinx related updates.
Selenium 4.8.3
* Add fine grained control for arguments provided to service
subprocesses by passing a `popen_kw` mapping for all services.
* `Options` classes now allow `timeout` to be set partially and no
longer raise an exception when all values are not provided. (#11623)
* No longer sending `SIGKILL` to subprocesses in instances where
`SIGTERM` was successful within 60 seconds.
* Add CDP files for v111 and remove v108
* Pass default to `pop` when parsing service popen_kw
* Using json output with Selenium Manager
* Sphinx config update to keep invoked methods and shorter aliases in
documentation (#11802)
[ Impact ]
User couldn't use the latest and greatest version of python-selenium in
Debian bookworm.
[ Tests ]
All upstream tests were successfull, a small checking of some local used
Selenium based snippets did also work as expected. Also the DebCI did
not shown any regressions.
[ Risks ]
There are no real risk to me, looking at the upstream changes I don't
see any potential pitfalls.
python-selenium is a key package and needs an manual unblock by the RT.
[ 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
[ Other info ]
There is also a differential view visable in the source repository on
GitHub.
https://github.com/SeleniumHQ/selenium/compare/selenium-4.8.2-python...selenium-4.8.3-python
But this is much bigger as the attached debdiff file as it also contains
parts of upstream code which we do filter out to fullfill the DFSG
requirements.
The Debian related modifications are only this rather small part.
$ git diff debian/4.8.2+dfsg-1 debian/
diff --git a/debian/changelog b/debian/changelog
index e10915a..ef494f9 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+python-selenium (4.8.3+dfsg-1) unstable; urgency=medium
+
+ * [9118276] New upstream version 4.8.3+dfsg
+ * [5bb3ae9] debian/: Move d/docs to d/python-selenium-doc.links
+
+ -- Carsten Schoenert Wed, 29 Mar 2023 12:14:56
+0200
+
python-selenium (4.8.2+dfsg-1) unstable; urgency=medium
* [8e56110] New upstream version 4.8.2+dfsg
diff --git a/debian/docs b/debian/docs
deleted file mode 100644
index a1320b1..000
--- a/debian/docs
+++ /dev/null
@@ -1 +0,0 @@
-README.rst
diff --git a/debian/python-selenium-doc.links b/debian/python-selenium-doc.links
new file mode 100644
index 000..567b3ed
--- /dev/null
+++ b/debian/python-selenium-doc.links
@@ -0,0 +1,4 @@
+# We can't just copy/install the original symlink from the source, it would
+# point to a non existing file after the packaging. So do the correct linking
+# here.
+usr/share/doc/python-selenium-doc/html/_sources/index.rst.txt
usr/share/doc/python-selenium-doc/README.rst
unblock python-selenium/4.8.3+dfsg-1
diff -Nru python-selenium-4.8.2+dfsg/CHANGES python-selenium-4.8.3+dfsg/CHANGES
--- python-selenium-4.8.2+dfsg/CHANGES 2023-02-18 00:17:10.0 +0100
+++ python-selenium-4.8.3+dfsg/CHANGES 2023-03-24 19:05:50.0 +0100
@@ -1,3 +1,12 @@
+Selenium 4.8.3
+* Add fine grained control for arguments provided to service subprocesses by
passing a `popen_kw` mapping for all services.
+* `Options` classes now allow `timeout` to be set partially and no longer
raise an exception when all values are not provided. (#11623)
+* No longer sending `SIGKILL` to subprocesses in instances where `SIGTERM` was
successful within 60 seconds.
+* Add CDP files for v111 and remove v108
+* Pass default to `pop` when parsing service popen_kw
+* Using json output with Selenium Manager
+* Sphinx config update to keep invoked methods and shorter aliases in
documentation (#11802)
+
Selenium 4.8.2
* Update tox.ini for a valid "isort" version (#11667)
* Undo a bug fix that caused a worse bug. (#11666)
diff -Nru python-selenium-4.8.2+dfsg/conftest.py
python-selenium-4.8.3+dfsg/conftest.py
--- python-selenium-4.8.2+dfsg/conftest.py 2023-02-18 00:17:10.0
+0100
+++ python-selenium-4.8.3+dfsg/conftest.py 2023-03-24 19:05:50.0
+0100
@@ -237,7 +237,9 @@
)
except Exception:
print("Starting the Selenium server")
-process = subprocess.Popen(["java", "-jar", _path, "standalone",
"--port", ""])
+process = subprocess.Pop
Bug#1033188: unblock: thunderbird/1:102.9.0-1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock X-Debbugs-Cc: thunderb...@packages.debian.org Control: affects -1 + src:thunderbird Please unblock package thunderbird [ Reason ] A new upstream release of the Thunderbird ESR series did happen that fixes a few CVE vulnerabilities. [ Impact ] Debian testing/bullseye would stick with version 102.8.0. [ Tests ] Even if the autopkgtests are marked superficial the main test did show that Thunbderbird is able to start and is picking up the global settings from /etc/thunderbird. Besides that I tested the new version a lot on alocal basis. [ Risks ] We are in the middle of the ESR releases and upstream change are now a lot less deep and agressive than on a start of a new ESR series. stable-security and also oldstable-security already are using 102.9.0 as actual version. [ 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 (only for the debian/folder) [ Other info ] The modifications for the source are quite big as usual but are going in parallel with firefox-esr due the same sorce code base. Please see further down for a diff of the chnages on the debian side. Basically only the Standards-Version was changed. unblock thunderbird/1:102.9.0-1 $ git diff debian/1%102.8.0-1 debian/ diff --git a/debian/changelog b/debian/changelog index b1c0dd97102..340fa97407c 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,18 @@ +thunderbird (1:102.9.0-1) unstable; urgency=medium + + * [ad8cc7c] New upstream version 102.9.0 +Fixed CVE issues in upstream version 102.9 (MFSA 2023-11): +CVE-2023-25751: Incorrect code generation during JIT compilation +CVE-2023-28164: URL being dragged from a removed cross-origin iframe +into the same tab triggered navigation +CVE-2023-28162: Invalid downcast in Worklets +CVE-2023-25752: Potential out-of-bounds when accessing throttled streams +CVE-2023-28176: Memory safety bugs fixed in Thunderbird 102.9 + * [b0a22c0] d/control: Increase Standards-Version to 4.6.2 +No further changes needed. + + -- Carsten Schoenert Wed, 15 Mar 2023 19:54:53 +0100 + thunderbird (1:102.8.0-1) unstable; urgency=medium * [b130936] New upstream version 102.8.0 diff --git a/debian/control b/debian/control index 13c0245e0c8..7f30678cab7 100644 --- a/debian/control +++ b/debian/control @@ -60,7 +60,7 @@ Vcs-Git: https://salsa.debian.org/mozilla-team/thunderbird.git -b debian/sid Vcs-Browser: https://salsa.debian.org/mozilla-team/thunderbird/commits/debian/sid/ Homepage: https://www.thunderbird.net/ X-Debian-Homepage: http://wiki.debian.org/Thunderbird -Standards-Version: 4.6.1 +Standards-Version: 4.6.2 Package: thunderbird Architecture: amd64 arm64 i386 mips64el ppc64el s390x ppc64
Bug#1031339: unblock: thunderbird/102.7.2-1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock X-Debbugs-Cc: thunderb...@packages.debian.org Control: affects -1 + src:thunderbird Please unblock package thunderbird [ Reason ] Due some planed traveling on my side I packaged the release candidate for Thunderbird 102.7.1-1 before the real final release on Mozilla did happen. I typically use the release candidate once it is available and normally this works without problems, but not this time for 102.7.1. Mozilla did encounter OAuth issues for user of O365 and did prepare a new release candidate which I was not able to pick up directly. This ended in an really delayed upload of the "fixed" Debian version 1:102.7.1+1-1 on 2023-02-07. And shortly after my upload Mozilla released one more new version 102.7.2 which is now sitting unstable and due the date 12th February migration time is extended to 10 days. The next ESR version of Thunderbird (102.8.0) will get released today but I wanted to see first the version 102.7.2-1 get migrated to tested so users of testing do not need to wait even longer for a fixed version of Thunderbird which is working again with O365 before I do a new upload of the next ESR version. [ Impact ] Users in testing need to wait for a fixed Debian version for CVE-2023-0430: Revocation status of S/Mime signature certificates was not checked (https://bugzilla.mozilla.org/show_bug.cgi?id=1810760) [ Tests ] I provided some testbuild for the real upstream version 102.7.1 before started to upload the final version for the archive. Affected user confirmed the fixed OAuth functionality. [ Risks ] There are no special risks as users confirmed the usability of the fixed version in Debian. [ Checklist ] [x] all changes are documented in the d/changelog [x] I reviewed all changes and I approve them [ ] attach debdiff against the package in testing [ Other info ] Currently nothing to add here. unblock thunderbird/102.7.2-1
Bug#1031279: bullseye-pu: package flask-security/4.0.0-1+deb11u1
Package: release.debian.org Severity: normal Tags: bullseye User: release.debian@packages.debian.org Usertags: pu X-Debbugs-Cc: flask-secur...@packages.debian.org Control: affects -1 + src:flask-security [ Reason ] The version of flask-security in bullseye is affected by CVE-2021-23385. https://security-tracker.debian.org/tracker/CVE-2021-23385 [ Impact ] Without that fix users of Flask based application which using get_post_logout_redirect and get_post_login_redirect functions might get an bypassed URL validation and redirect a user to an arbitrary URL. [ Tests ] Upstream has added a test to check the code for catching any bypass while adding the needed source code changes. https://github.com/Flask-Middleware/flask-security/commit/e39bb04615050448c1b8ba4caa7dacc0edd3e405#diff-56f87108fb8c4605e56b4702938ff2211dd019c94ac130bfbc8016e6a9143dd0 I did not check this fix manually but run several test run while working on updating flask-security in unstable at time. [ Risks ] The added debdiff is quite long as also a lot of documentation in configuration.rst is added. The relevant part of the source code changes to fix the CVE are rather small and not very complex. [ 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 ] Upstream extended the function validate_redirect_url() in a way if a configuration value of REDIRECT_VALIDATE_MODE is matching 'regex' the given URL will get validated. Upstream also added some more documentation in general to the documentation and also to functions that are used. And some test is added to the internal test suite. [ Other info ] This fix is backported from https://github.com/Flask-Middleware/flask-security/pull/489 and is included within the current version in unstable/testing. Note: The version in bullseye is originally based on the upstream source https://github.com/mattupstate/flask-security! But this git tree isn't actively maintained any more and the active development is happen now on https://github.com/Flask-Middleware/flask-security where the version in unstable/testing is based on. I was in conversation with the security team if this fix is worth to get an update through stable-security. As the issue is tagged as low-priority the suggestion was to fix the problem through a point update for bullseye. diff -Nru flask-security-4.0.0/debian/changelog flask-security-4.0.0/debian/changelog --- flask-security-4.0.0/debian/changelog 2021-02-01 14:42:21.0 + +++ flask-security-4.0.0/debian/changelog 2023-02-14 11:10:52.0 + @@ -1,3 +1,12 @@ +flask-security (4.0.0-1+deb11u1) bullseye; urgency=medium + + * Fix for CVE-2021-23385 +Cherry pick partially PR #489 from the upstream project +(https://github.com/Flask-Middleware/flask-security/pull/489) +to fix Open Redirect Vulnerability aka CVE-2021-23385. + + -- Carsten Schoenert Tue, 14 Feb 2023 11:10:52 + + flask-security (4.0.0-1) unstable; urgency=medium * Team upload. diff -Nru flask-security-4.0.0/debian/patches/0001-A-hopeful-fix-for-possible-open-redirect.patch flask-security-4.0.0/debian/patches/0001-A-hopeful-fix-for-possible-open-redirect.patch --- flask-security-4.0.0/debian/patches/0001-A-hopeful-fix-for-possible-open-redirect.patch 1970-01-01 01:00:00.0 +0100 +++ flask-security-4.0.0/debian/patches/0001-A-hopeful-fix-for-possible-open-redirect.patch 2023-02-14 11:02:05.0 + @@ -0,0 +1,298 @@ +From: jwag956 +Date: Sat, 29 May 2021 19:18:55 -0700 +Subject: A (hopeful) fix for possible open-redirect. + +While this is only an issue if the application sets the Werkzeug response variable: +autocorrect_location_header = False - it none the less poses a small security concern. + +pyupgrade and black changed again .. sigh... +pin read the docs sphinx versions. + +Closes: #486 + +Forwared: https://github.com/Flask-Middleware/flask-security/pull/489 +--- + docs/configuration.rst | 53 +++- + flask_security/core.py | 7 +- + flask_security/datastore.py | 2 +- + flask_security/decorators.py | 4 ++-- + flask_security/utils.py | 31 ++ + requirements/docs.txt| 6 ++--- + tests/test_misc.py | 17 ++ + tests/view_scaffold.py | 8 +++ + 8 files changed, 120 insertions(+), 8 deletions(-) + +diff --git a/docs/configuration.rst b/docs/configuration.rst +index 497bd1d..12144da 100644 +--- a/docs/configuration.rst b/docs/configuration.rst +@@ -216,7 +216,7 @@ These configuration keys are used globally across all features. + .. py:data:: SECURITY_REDIRECT_ALLOW_SUBDOMAINS + + If ``True`` then subdomains (and the root domain) of the top-level host set +-by Flask's ``SERVER_NAME`` configuration will be allowed as post
Bug#1001149: buster-pu: package gerbv/2.7.0-1
Package: release.debian.org
Severity: normal
Tags: buster
User: release.debian@packages.debian.org
Usertags: pu
gerbv is a utility for viewing Gerber RS-274X files, Excellon drill files,
and CSV files for pick-and-place files. Gerber files are used for
communicating printed circuit board (PCB) designs to PCB manufacturers.
[ Reason ]
The gerbv upstream project was getting in contact via the
pkg-electronic-devel mailing list to inform about a security issue for
gerbv that was found by the Cisco Talos team. That issue got the CVE
number CVE-2021-40391.
https://alioth-lists.debian.net/pipermail/pkg-electronics-devel/2021-November/008221.html
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-40391
This issue was fixed with the release of version 2.7.1, buster was
released with version 2.7.0, so this version is taking effect of the
CVE.
Debian testing and unstable are on version 2.8.1 for gerbv while writing.
[ Impact ]
Users of the unpatched gerbv version from the buster release might be
affected to get unwanted code exceution and loose of data.
[ Tests ]
Currently there are no automated or manuall test available to check the
fixing of this issue.
[ Risks ]
Nearlly to zero, the fix for this is quite non intrusive and really small
(basically it's just one line of code).
[ 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 whole change to get the CVE is fixed is adding one line of code
within the C-file drill.c, within the function drill_parse_T_code() a
'return -1' is need to solve the issue.
[ Other info ]
Anton Gladky within the LTS team did an upload of version 2.6.1-2+deb9u1
to fix this issue for Debian 9.
https://tracker.debian.org/news/1283553/accepted-gerbv-261-2deb9u1-source-into-oldoldstable/
The debdiff between the old version 2.7.0-1 in buster and prepared
version gerbv_2.7.0-1+deb10u1 is added here as it's not that big.
diff -Nru gerbv-2.7.0/debian/changelog gerbv-2.7.0/debian/changelog
--- gerbv-2.7.0/debian/changelog2019-02-18 17:57:45.0 +0100
+++ gerbv-2.7.0/debian/changelog2021-12-05 09:29:11.0 +0100
@@ -1,3 +1,14 @@
+gerbv (2.7.0-1+deb10u1) buster; urgency=medium
+
+ * Build for buster
+ * [c33610a] Rebuild patch queue from patch-queue branch
+Added patch:
+security/Fix-TALOS-2021-1402.patch
+Fixing CVE-2021-40391
+ * [09244b9] d/gbp.conf: Adjust to branch debian/buster
+
+ -- Carsten Schoenert Sun, 05 Dec 2021 09:29:11
+0100
+
gerbv (2.7.0-1) unstable; urgency=medium
* [ac52385] d/gbp.conf: adding helper for git-buildpackage
diff -Nru gerbv-2.7.0/debian/gbp.conf gerbv-2.7.0/debian/gbp.conf
--- gerbv-2.7.0/debian/gbp.conf 2019-02-18 17:55:34.0 +0100
+++ gerbv-2.7.0/debian/gbp.conf 2021-12-05 09:29:03.0 +0100
@@ -5,7 +5,7 @@
pristine-tar = True
# generate gz compressed orig.tar file
compression = gz
-debian-branch = debian/sid
+debian-branch = debian/buster
upstream-branch = upstream
[pq]
@@ -13,7 +13,7 @@
[dch]
id-length = 7
-debian-branch = debian/sid
+debian-branch = debian/buster
[import-orig]
# filter out unwanted files/dirs from upstream
diff -Nru gerbv-2.7.0/debian/patches/security/Fix-TALOS-2021-1402.patch
gerbv-2.7.0/debian/patches/security/Fix-TALOS-2021-1402.patch
--- gerbv-2.7.0/debian/patches/security/Fix-TALOS-2021-1402.patch
1970-01-01 01:00:00.0 +0100
+++ gerbv-2.7.0/debian/patches/security/Fix-TALOS-2021-1402.patch
2021-12-05 09:26:42.0 +0100
@@ -0,0 +1,27 @@
+From: eyal0 <109809+ey...@users.noreply.github.com>
+Date: Tue, 26 Oct 2021 21:39:25 -0600
+Subject: Fix TALOS-2021-1402
+
+See issue #30
+
+This commit fixes CVE-2021-40391. Background information can be found on
+this URL.
+https://talosintelligence.com/vulnerability_reports/TALOS-2021-1402
+
+Forwarded:
https://github.com/gerbv/gerbv/commit/9f83950b772b37b49ee188300e444546e6aab17e
+---
+ src/drill.c | 1 +
+ 1 file changed, 1 insertion(+)
+
+diff --git a/src/drill.c b/src/drill.c
+index bc90524..414872d 100644
+--- a/src/drill.c
b/src/drill.c
+@@ -1115,6 +1115,7 @@ drill_parse_T_code(gerb_file_t *fd, drill_state_t *state,
+ _("Out of bounds drill number %d "
+ "at line %ld in file \"%s\""),
+ tool_num, file_line, fd->filename);
++ return -1;
+ }
+
+ /* Set the current tool to the correct one */
diff -Nru gerbv-2.7.0/debian/patches/series gerbv-2.7.0/debian/patches/series
--- gerbv-2.7.0/debian/patches/series 2019-02-18 17:56:38.0 +0100
+++ gerbv-2.7.0/debian/patches/series 2021-12-05 09:26:42.0 +0100
@@ -5,3 +5,4 @@
debian-hacks/crossbuild-use-PKG_PROG_PKG_CONFIG-instead-of-AC_PATH_PRO.patch
fixes/man-page-fix-misspelled-excercise-exercise.patch
fixes/Fix-Werror-format-sec
Bug#1001148: bullseye-pu: package gerbv/2.7.0-2
Package: release.debian.org
Severity: normal
Tags: bullseye
User: release.debian@packages.debian.org
Usertags: pu
gerbv is a utility for viewing Gerber RS-274X files, Excellon drill files,
and CSV files for pick-and-place files. Gerber files are used for
communicating printed circuit board (PCB) designs to PCB manufacturers.
[ Reason ]
The gerbv upstream project was getting in contact via the
pkg-electronic-devel mailing list to inform about a security issue for
gerbv that was found by the Cisco Talos team. That issue got the CVE
number CVE-2021-40391.
https://alioth-lists.debian.net/pipermail/pkg-electronics-devel/2021-November/008221.html
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-40391
This issue was fixed with the release of version 2.7.1, bullseye was
released with version 2.7.0, so this version is taking effect of the
CVE.
Debian testing and unstable are on version 2.8.1 for gerbv while writing.
[ Impact ]
Users of the unpatched gerbv version from the bullseye release might be
affected to get unwanted code exceution and loose data.
[ Tests ]
Currently there are no automated or manuall test available to check the
fixing of this issue.
[ Risks ]
Nearlly to zero, the fix for this is quite non intrusive and relly small
(basically it's just one line of code).
[ 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 whole change to get the CVE is fixed is adding one line of code
within the C-file drill.c, within the function drill_parse_T_code() a
'return -1' is need to solve the issue.
[ Other info ]
Anton Gladky within the LTS team did an upload of version 2.6.1-2+deb9u1
to fix this issue for Debian 9.
https://tracker.debian.org/news/1283553/accepted-gerbv-261-2deb9u1-source-into-oldoldstable/
The debdiff between the old version 2.7.0-2 in bullseyse and prepared
version gerbv_2.7.0-2+deb11u1 is added here as it's not that big.
diff -Nru gerbv-2.7.0/debian/changelog gerbv-2.7.0/debian/changelog
--- gerbv-2.7.0/debian/changelog2020-06-07 10:01:13.0 +0200
+++ gerbv-2.7.0/debian/changelog2021-12-05 09:14:05.0 +0100
@@ -1,3 +1,14 @@
+gerbv (2.7.0-2+deb11u1) bullseye; urgency=medium
+
+ * Build for bullseye
+ * [e983451] Rebuild patch queue from patch-queue branch
+Added patch:
+security/Fix-TALOS-2021-1402.patch
+Fixing CVE-2021-40391
+ * [7d33020] d/gbp.conf: Adjust to branch debian/bullseye
+
+ -- Carsten Schoenert Sun, 05 Dec 2021 09:14:05
+0100
+
gerbv (2.7.0-2) unstable; urgency=medium
[ أحمد المحمودي (Ahmed El-Mahmoudy) ]
diff -Nru gerbv-2.7.0/debian/gbp.conf gerbv-2.7.0/debian/gbp.conf
--- gerbv-2.7.0/debian/gbp.conf 2019-02-18 17:55:34.0 +0100
+++ gerbv-2.7.0/debian/gbp.conf 2021-12-05 09:14:05.0 +0100
@@ -5,7 +5,7 @@
pristine-tar = True
# generate gz compressed orig.tar file
compression = gz
-debian-branch = debian/sid
+debian-branch = debian/bullseye
upstream-branch = upstream
[pq]
@@ -13,7 +13,7 @@
[dch]
id-length = 7
-debian-branch = debian/sid
+debian-branch = debian/bullseye
[import-orig]
# filter out unwanted files/dirs from upstream
diff -Nru gerbv-2.7.0/debian/patches/fixes/gcc10-extern.patch
gerbv-2.7.0/debian/patches/fixes/gcc10-extern.patch
--- gerbv-2.7.0/debian/patches/fixes/gcc10-extern.patch 2020-06-07
10:00:34.0 +0200
+++ gerbv-2.7.0/debian/patches/fixes/gcc10-extern.patch 2021-12-05
09:14:05.0 +0100
@@ -1,4 +1,5 @@
-From: أحمد المحمودي (Ahmed El-Mahmoudy)
+From: =?utf-8?b?Itij2K3ZhdivINin2YTZhdit2YXZiNiv2YogKEFobWVkIEVsLU1haG1v?=
+ =?utf-8?b?dWR5KSI=?=
Date: Mon, 25 May 2020 20:05:28 +0200
Subject: use extern for global vars.
diff -Nru gerbv-2.7.0/debian/patches/security/Fix-TALOS-2021-1402.patch
gerbv-2.7.0/debian/patches/security/Fix-TALOS-2021-1402.patch
--- gerbv-2.7.0/debian/patches/security/Fix-TALOS-2021-1402.patch
1970-01-01 01:00:00.0 +0100
+++ gerbv-2.7.0/debian/patches/security/Fix-TALOS-2021-1402.patch
2021-12-05 09:14:05.0 +0100
@@ -0,0 +1,27 @@
+From: eyal0 <109809+ey...@users.noreply.github.com>
+Date: Tue, 26 Oct 2021 21:39:25 -0600
+Subject: Fix TALOS-2021-1402
+
+See issue #30
+
+This commit fixes CVE-2021-40391. Background information can be found on
+this URL.
+https://talosintelligence.com/vulnerability_reports/TALOS-2021-1402
+
+Forwarded:
https://github.com/gerbv/gerbv/commit/9f83950b772b37b49ee188300e444546e6aab17e
+---
+ src/drill.c | 1 +
+ 1 file changed, 1 insertion(+)
+
+diff --git a/src/drill.c b/src/drill.c
+index bc90524..414872d 100644
+--- a/src/drill.c
b/src/drill.c
+@@ -1115,6 +1115,7 @@ drill_parse_T_code(gerb_file_t *fd, drill_state_t *state,
+ _("Out of bounds drill number %d "
+ "at line %ld in file \"%s\""),
+
Bug#991236: unblock: thunderbird/1:78.12.0-1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package thunderbird There was again a new ESR release of Thunderbird which fixes as usual some CVEs. [ Reason ] These CVEs got fixed by upstream release of 78.11.0 and 78.12.0. CVE-2021-29969: IMAP server responses sent by a MITM prior to STARTTLS could be processed CVE-2021-29970: Use-after-free in accessibility features of a document CVE-2021-30547: Out of bounds write in ANGLE CVE-2021-29976: Memory safety bugs fixed in Thunderbird 78.12 [ Impact ] Users of testing will get excluded from using the newer version with the fixed CVE related issues. [ Tests ] The local usage and installation tests didn't have shown any anomalies, the autopkgtests did run also successful. [ Risks ] The same risks are given as in the unblock request for 78.11.0-1, but contrary to 78.11.0-1 and the libnss3 library issue, which was worked around by -2 no other new issues come up until then. Thus I expect really no new bug reports due the new bumped version of Thunderbird. The upload of 78.12.0-1 to unstable did happen yesterday, even if the new Thunderbird version was released on Tuesday in the past week as I was offline for a few days due the various flood catastrophes near my home. You might want to decerase the transition time really only to a few days so we can act quick enough in case some issues will come up. [ Checklist ] [x] all changes are documented in the d/changelog [x] I reviewed all changes and I approve them [ ] attach debdiff against the package in testing [ Other info ] Again I'm not attaching a debdiff as even a smaller set of upstream modifications did happen it would be rather big and time consuming to read. unblock thunderbird/1:78.12.0-1
Re: Bug#989839: Thunderbird 1:78.11.0-1 in testing lacks full functionality
Hello Sebastian, Am 19.06.21 um 21:33 schrieb Sebastian Ramacher: ... >> To prevent quite a lot of work on all involved parties with not that >> much gain in the end I'd suggest to go back to my option B that was to >> (re)build Thunderbird with it's internal shipped NSS version. > > If that's fine with the security team -- thunderbird updates in stable > releases have been performed via DSAs so far -- it's fine with me. > Adding the security team to CC. thanks, I pushed 1:78.11.0-2 to unstable. This will fix the current issues for the users. -- Regards Carsten
Re: Bug#989839: Thunderbird 1:78.11.0-1 in testing lacks full functionality
Hello Kevin, hello Sebastian,
thanks for working on this issue in between times, I wasn't able to do
anything practically the last days.
Am 18.06.21 um 23:31 schrieb Kevin Locke:
> Hi Sebastian,
>
> On Fri, 2021-06-18 at 22:26 +0200, Sebastian Ramacher wrote:
>> Thanks for this detailed analysis. That actually means that the symbol
>> file for libnss3 2:3.67-1 is broken. It would need to bump the minimum
>> version requirement for all symbols that works with SSLChannelInfo. From
>> your description, at least the version for SSL_GetChannelInfo would need
>> to be bumped. If thunderbird would then be built against a libnss3
>> version with a fixed symbol files, it would pick up tight enought
>> dependencies.
>>
>> So ideally the bug against thunderbird would be reassigned to libnss3
>> 2:3.67-1 and its severits raised to serious. Once fixed, we can rebuild
>> thunderbird to pick up the correct depedencies.
>
> Good point. Fixing the libnss3 symbol file sounds like the right fix to
> me. As far as I can tell SSL_GetChannelInfo is the only symbol which
> takes SSLChannelInfo. I've opened https://bugs.debian.org/990058 with
> the proposed fix.
Fixing libnss3 is obviously the correct thing anyway. But this will take
its time to get it landed into bullseye.
>> But since that version of libnss3 is not in bullseye, the rebuild would
>> not be abile to migrate. Ideally libnss3 would be reverted to the
>> version in bullseye to avoid this issue. Otherwise I can schedule
>> binNMUs of thunderbird in tpu, but that means that we would need to do
>> that for any thunderbird upload that we want in bullseye until the
>> release. That is suboptimal - it's more work with less testing.
>
> That may be tricky. firefox 88.0.1-1 in unstable depends on
> libnss3 (>= 2:3.63~). If the maintainers are willing to upload an NSS
> version between 2:3.63 and 2:3.65, I believe that would solve the issue
> without breaking firefox. (2:3.63-1 is the only suitable version
> in debian/changelog.) I've opened https://bugs.debian.org/990059 to
> discuss.
To prevent quite a lot of work on all involved parties with not that
much gain in the end I'd suggest to go back to my option B that was to
(re)build Thunderbird with it's internal shipped NSS version.
Looking at "Help - Troubleshooting Information" I can see now that
Thunderbird is expecting NSS 3.51.1 (instead of 3.63) which gets
provided by exact this version (internally).
There will be only one more real ESR version 78.12.0 before the ESR
version will get bumped to 91.x. So in my eyes it's acceptable that we
start right now to use the internal shipped NSS version. We will need to
do this any way together with the new ESR version is getting prepared
for bullseye-security.
(To be honest, there will also be 78.{13-15}.0 before we probably be
ready for 91.3.0. In the past we've been very conservative with
uploading fresh and new ESR version to stable-security due limited
resources for testing before.)
I've done such a rebuild of 78.11.0 together with the internal NSS
library and so far I don't see any TLS/SSL related issue as before.
The packages and the debian folder can be found here
https://people.debian.org/~tijuca/thunderbird-bullseye/
I used a chroot of unstable to built the packages but all required
versions can get fulfilled in testing (libnss3 isn't a dependency now as
the internal version is used and dpkg-shlipdeps isn't adding any
dependency to this).
Thus we could simply use the usual way to update Thunderbird via
unstable in testing.
--
Regards
Carsten
Thunderbird 1:78.11.0-1 in testing lacks full functionality
Hi, a few days ago I requested the unblock of thunderbird 1:78.11.0-1 which was done quite quickly. Unfortunately rather also quickly I got some bug reports about Thunderbird isn't correctly working in testing/bullseye, but has before in version 1:78.10.0-1. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989839 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989839 I haven't found time yet to dig into the thing, but my expectation is already that the problem must have to do the the libnss3 library as no other parts have changed that deeply. Thunderbird 78.x has a version check for libnss3(-dev) while package build on nss >= 3.51.1. This can be fulfilled since a long time. We have in testing currently 2:3.61-1 and in unstable 2:3.67-1. While 1:78.11.0-1 was built against the previous version 3.66. The user Kevin Locke did some research on the differences between Thunderbird versions 1:78.10.0-1, 1:78.10.2-1 and 1:78.11.0-1 and found out that the previous version in testing was built against nss 3.63 and the current Thunderbird version was build against nss 3.66. He also confirms that these nasty issues in Thunderbird are gone if the libnss3 package from unstable is installed. I can confirm this too, I can see all suggested extensions again once I've installed libnss3 from unstable. For sure this all is somehow an upstream issue, somewhere between thunderbird and NSS3 and the build configuration. If I look at the the information from "Help - Troubleshooting Information" I can see Thunderbird is requesting libnss3 at least in version 3.63. but unstable has only 3.61 available, But how to proceed right now? I see two possible options. 1. Unblock nss 2:3.67-1 But I've no idea if Mike has his reasons for not requesting an unblock. But I also can't think of any. 2. Rebuild the thunderbird package and use the internal shipped nss source which is at 3.51.1. I expect this will get needed any way for bullseye once the next ESR circle is starting as and usually MZLA will use then the most recent available nss version within the shipped source. What for opinions the RT is seeing? -- Regrads Carsten
Bug#989789: RM: sogo-connector/68.0.1-2
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: rm Hi, please remove the sogo-connector package from testing and stable. The current version of sogo-connector isn't usable with any recent version of thunderbird in both releases. I was hoping upstream would release an updated new version compatible to the newer plugin API but until today this didn't happen. So it makes no sense to ship a version of sogo-connector that is not working with thunderbird. I requested the removal from unstable by filing #989788. Regards Carsten
Bug#989787: unblock: thunderbird/1:78.11.0-1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package thunderbird I hereby requesting the unblock of thunderbird. The current version in unstable is the usual update of the ESR version that happen about every 6 weeks whith fixes for some CVE issues since the release of the previous version 78.10.0. [ Reason ] These CVEs got fixed by upstream release of 78.10.2 and 78.11.0. CVE-2021-29957: Partial protection of inline OpenPGP message not indicated CVE-2021-29956: Thunderbird stored OpenPGP secret keys without master password protection CVE-2021-29967: Memory safety bugs fixed in Thunderbird 78.11 [ Impact ] Users of testing will get excluded from using the newer version with the fixed CVE related issues. [ Tests ] The local usage tests didn't hve shown any anomalies, the autopkgtests did run also successful. [ Risks ] No update is risk free, but this ESR circle is rather near it end. So it's quite unlikely that user experience breaking things will happen. The upload to unstable happen about 10 days ago and no new bug report was opened up since then. Users of stable and old-stable already did get the updated newer version. [ Checklist ] [x] all changes are documented in the d/changelog [x] I reviewed all changes and I approve them [ ] attach debdiff against the package in testing [ Other info ] I'm not attaching a debdiff as even a smaller set of upstream modifications did happen it would be rather big and time consuming to read. unblock thunderbird/1:78.11.0-1
Bug#987016: unblock: arduino/2:1.8.13+dfsg1-2
d content! + +1. Download the archived content of the reference. + + wget -P ~/Downloads https://downloads.arduino.cc/reference-1.6.6-3.zip + +2. Extract the content. + + unzip ~/Downloads/reference-1.6.6-3.zip -d /tmp/reference + +3. Move the extracted reference. + + # become root + mv -f /tmp/reference/* /usr/share/arduino/reference + # or if you are in the sudo group + sudo mv /tmp/reference/* /usr/share/arduino/reference + # remove used folder where content was extracted to (not fully needed) + rmdir /tmp/reference + +Please note that the content of the archive is missing some parts like used web +fonts and thus the website is looking not fully equal to the upstream version. +You will always find the current version of the reference online on + + https://www.arduino.cc/reference/en + diff -Nru arduino-1.8.13+dfsg1/debian/changelog arduino-1.8.13+dfsg1/debian/changelog --- arduino-1.8.13+dfsg1/debian/changelog 2021-01-26 19:13:48.0 +0100 +++ arduino-1.8.13+dfsg1/debian/changelog 2021-03-20 16:47:01.0 +0100 @@ -1,3 +1,23 @@ +arduino (2:1.8.13+dfsg1-2) unstable; urgency=medium + + * Team upload + * [e1dccaf] d/u/metadata: Adding DEP12 based metadata + * [5ca53c5] d/README.source: Rework information and suggestions + * [990e2d7] README.Debian: Adding notes regarding IDE language reference +We don't package the Arduino language reference currently, but having +(offline) access to it might be desirable by users. +Adding some steps how the reference could be made available within the +IDE. + * [81e8635] d/control: Adding entry for Rules-Requires-Root: no + * [3f07192] d/watch: re-add the pgpsigurlmangle option + * [e1f08c2] d/arduino.lintian-overrides: ignore duplicated pics +Ignore potential duplicated png files within the documentation, they are +very small. + * [5e9abef] d/arduino.links: Correct linking to bcprov.jar +(Closes: #985506) + + -- Carsten Schoenert Sat, 20 Mar 2021 16:47:01 +0100 + arduino (2:1.8.13+dfsg1-1) unstable; urgency=medium * Team upload @@ -262,7 +282,7 @@ * New upstream release - No wifishield firmware inluded in Debian: pre-compiled avr32 binaries - with no sane build system. For source code and binaries, see the + with no sane build system. For source code and binaries, see the wifishield repo on github * refreshed patches: - debian/patches/SimpleDateFormat_fix.diff deleted, applied upstream @@ -498,7 +518,7 @@ This allows arduino to start when using a sun-java jre. See Debian bug 382686. - -- Scott Howard Sat, 30 Oct 2010 11:26:53 -0400 + -- Scott Howard Sat, 30 Oct 2010 11:26:53 -0400 arduino (0021+dfsg-2) experimental; urgency=low diff -Nru arduino-1.8.13+dfsg1/debian/control arduino-1.8.13+dfsg1/debian/control --- arduino-1.8.13+dfsg1/debian/control 2021-01-26 19:11:43.0 +0100 +++ arduino-1.8.13+dfsg1/debian/control 2021-03-20 16:47:01.0 +0100 @@ -44,6 +44,7 @@ Homepage: https://www.arduino.cc Vcs-Browser: https://salsa.debian.org/electronics-team/arduino/arduino Vcs-Git: https://salsa.debian.org/electronics-team/arduino/arduino.git +Rules-Requires-Root: no Package: arduino Architecture: any-amd64 any-i386 arm64 armel armhf diff -Nru arduino-1.8.13+dfsg1/debian/README.source arduino-1.8.13+dfsg1/debian/README.source --- arduino-1.8.13+dfsg1/debian/README.source 2021-01-08 12:42:36.0 +0100 +++ arduino-1.8.13+dfsg1/debian/README.source 2021-03-20 16:37:20.0 +0100 @@ -1,72 +1,72 @@ +Organization of maintenance for src:arduino +--- -For my co-maintainers and my future self. +This package is maintained with git-buildpackage(1). +It uses pristine-tar(1) to store enough information in git to generate bit +identical tarballs when building the package without having downloaded an +upstream tarball first. + +When working with patches it is recommended to use "gbp pq import" to +import the patches, modify the source and then use "gbp pq export +--commit" to commit the modifications. + +The changelog is generated using "gbp dch" so if you submit any changes +don't bother to add changelog entries but rather provide a nice git commit +message that can then end up in the changelog. + +It is recommended to build the package with pbuilder using: + +gbp builpackage --git-pbuilder + +For information on how to set up a pbuilder environment see the +git-pbuilder(1) manpage. In short: + +DIST=sid git-pbuilder create +gbp clone https://salsa.debian.org/electronics-team/arduino/arduino.git +cd arduino +gbp buildpackage --git-pbuilder + + +Importing a new upstream version + + +To minimize workload and decrease possible mistakes the preferred way to +import a new version is doing this by git-buildpackage and let d/gbp.conf +control the whole import process. Importing a new version is d
Re: question regarding possible needed further action on package arduino
Hello Paul, Am 30.01.21 um 19:24 schrieb Paul Gevers: ... >> So here is my question, do I need to contact the FTP Team to clear this >> non solvable dependency (I remember I needed something similar in the >> past for Thunderbird) or can this issue get managed by the RT? Thanks! > > Please ask ftp-master to remove the old arduino-core package. As long as > that is in unstable, the package will not migrate as britney will keep > on believing that the arch:all hasn't been built. thanks for the quick answer and also for confirmation of my thinking. I'll contact the FTP team soon. -- Regards Carsten
question regarding possible needed further action on package arduino
Hi there, after a month of concentrate work together with Rock Storm on the arduino package , and some related build depending packages the Debian Electronics Team is happy we have now an updated Arduino IDE package in unstable. https://tracker.debian.org/pkg/arduino The current migration checking says that the build on architecture all is missing. The arduino package now doesn't have an 'all' architecture package any more as we needed to melt all together into architecture related. So here is my question, do I need to contact the FTP Team to clear this non solvable dependency (I remember I needed something similar in the past for Thunderbird) or can this issue get managed by the RT? Thanks! -- Regards Carsten
Re: Why does opencascade not migrate?
Hello Sebastian, seems your original email didn't reached me, but I've seen your answer in the list web ui. ... > That means that migrating those packages renders libdeal.ii-dev > uninstallable in testing. Consequently, the changes are not committed. > > The binNMU fixing libdeal.ii-dev's installability issues is currently > blocked by openmpi and other packages waiting for openmpi to migrate: > > deal.ii/amd64 (9.2.0-3 to 9.2.0-3) > Migration status for deal.ii/amd64 (9.2.0-3 to 9.2.0-3): BLOCKED: > Cannot migrate due to another item, which is blocked (please check which > dependencies are stuck) > Issues preventing migration: > Depends: deal.ii/amd64 petsc (not considered) > Invalidated by dependency > Depends: deal.ii/amd64 opencascade > Depends: deal.ii/amd64 openmpi > Depends: deal.ii/amd64 slepc > > (from https://release.debian.org/britney/update_excuses.html) > > Once the openmpi situation is resolved, opencascade should be able to > migrate. Thanks for analyzing and explanation. So this all should get solved by simply further waiting currently. -- Regards Carsten
Re: Re: Why does opencascade not migrate?
Why does opencascade not migrate?
Hi, I've asked on #debian-release already why the most recent version of opencascade in unstable isn't migrating to testing. Sebastian mentioned to have a look at https://release.debian.org/britney/update_output.txt But don't really understand the data that is visible here. As I like to see kicad migrating to testing, which is depending on opencascade, I'd like to ask if the situation can be reviewed by one of the RT members and give further advice how to process to solve the situation. PS: Please CC me, I'm not subscribed to any of the lists. -- Regards Carsten
Bug#978958: release.debian.org: package Thunderbird stucks on autopkgtest on ppc64el for ever
Package: release.debian.org Severity: normal Hi there, since ppc64el was added to the CI pipeline of autopkgtest the package Thunderbird did never pass a single test on the CI platform as it always staying in status "Test in progress" one a new version get uploaded. There is something looking fishy to me in principal on ppc64el. If the real reason can't be found why thunderbird isn't tested successful on ppc64el I suggest to ignore this testing on this architecture. Regards Carsten -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386, aarch64, arm64 Kernel: Linux 5.9.0-5-amd64 (SMP w/4 CPU threads) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Re: [Pkg-mozext-maintainers] Updating Mozilla plugins in stable
Hello Mehtilde, Am 25.10.20 um 13:39 schrieb Mechtilde Stehmann: >> On a related note, britney isn't attempting to migrate the 2.18 upload >> because: >> >> Not built on buildd: arch all binaries uploaded by o...@mechtilde.de, a new >> source-only upload is needed to allow migration > > Do you mean I have to upload it for sid again? looking at the upload Adam is referring I'd say yes. https://tracker.debian.org/news/1183242/accepted-tbsync-218-1-source-all-into-unstable/ You uploaded a binary build and not a source only build. Probably by accident. -- Regards Carsten
Bug#971989: unblock: thunderbird/1:78.3.2-1
Hello Michael, Am 20.10.20 um 15:49 schrieb Michael Biebl: > I guess the solution for that is to upload enigmail 2.2 as quickly as > possible to stable(-security). > It is not justification to break more stuff. that depends a bit on the point of view as I don't see anything is breaking here, but o.k.. :) In the past while working on the first betas for the upcoming new ESR version of Thunderbird I've tried to spread early any news regarding the next (and now live) TB ESR version 78.x by sending information about the ongoing process to pkg-mozext-maintainers. I requested early testing of TB and also that the maintainers of packaged Add-ons to take of "their" Add-ons. This mostly was not possible though as even the upstream maintainers did not provide updated versions of Add-ons. The situation for Enigmail was different, there were new versions. But until today we didn't get it managed that the Enigmail Add-on get updated within Debian without any feedback from the maintainers why no progress is possible. As nobody can be enforced to do anything in Debian, but also Thunderbird isn't a small and non relevant package in Debian, I moved ahead and uploaded finally Thunderbird to unstable to moving forward. It's always possible to install the Enigmail Add-on within the local profile. We did had a quite similar situation with the previous ESR version 68 in Debian. So I do not know why Enigmail can't get an update until today nor have I the time and knowledge to prepare a updated enigmail package via NMU. > Fwiw, I'm willing to NMU enigmail, if there is no progress on #970111. That's of course fine if you want to do that. And now already did. -- Regards Carsten Schoenert
Bug#971989: unblock: thunderbird/1:78.3.2-1
Hello Michael, Am 20.10.20 um 14:54 schrieb Michael Biebl: > Shouldn't we rather wait, until such an updated enigmail package is > available? I see, that the enigmail package has a bug report with > attached patches, maybe it's time to NMU (that said, I've explicitly > CCed Daniel, maybe he can chime in here) > > I don't think forcing TB 78 into testing is the answer, your users would > be quite unhappy. I personally think that we already break the user experience as we released TB for buster through stable-security and some days ago also for LTS users. So I see no need to wait any longer. Currently the upgrade path for buster users is at least broken for Thunderbird. I assume users of Debian testing are mostly more experienced than the addressed users for stable. Besides of that TB 1:78.x has a breaks on Enigmail << 2:2.2.0~ and the migration testing scripts currently doesn't care about that. It might be that the control version handling needs some more fine tuning, if so I'm happy to adjust that. -- Regards Carsten Schoeert
Bug#971989: unblock: thunderbird/1:78.3.2-1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package thunderbird The automatic migration testing for Thunderbird is containing some tests for the packages jsunit and enigmail which currently prevents the automatic migration of the thunderbird package to testing because the tests are failing. The enigmail package needs to be available in at least version 2.2 to give a useful user experience. Thunderbird has included a version requirement on enigmail that 2.2 is required. This requirement can't get fulfilled currently in Debian unstable or testing because the maintainers of the Enigmail package didn't prepared and upoaded until now a new version. There is s wishlist bug for updating enigmail to the most recent version since a few weeks. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970111 The jsunit package is now also outdated and must fail against the current Thunderbird versions. So far I've no feedback from the enigmail maintainers, they got involved within the communication with the security team while the upload of thunderbird for stable/security got prepared. The currently also reported uninstallability for the package webext-exteditor/2.0.4-1 is intended as this version isn't working with Thunderbird >= 78. So I'd like to suggest to remove (if this is possible) the auto migration testing of enigmail and jsunit against thunderbird. At least please allow the migration of the Thunderbird related packages into testing. I'm condidering removal requests for enigmail and jsunit in testing. Regards Carsten unblock thunderbird/1:78.3.2-1 -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386, aarch64, arm64 Kernel: Linux 5.8.0-2-amd64 (SMP w/4 CPU threads) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#958922: RM: xul-ext-quotecolors/0.3-6 in stable
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: rm Dear RT, the package xul-ext-quotecolors, an Thunderbird extension, isn't usable any longer since Thunderbird ESR has moved to 68.x due API changes within Thunderbird. It's dead from the upstream side and wont get updates in the future, please remove the package from the stable release. There is a RC bug about the non usable functionality in testing. https://bugs.debian.org/950512 I also requested the removal from unstable https://bugs.debian.org/958913 Thanks Carsten Schoenert -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.5.0-1-amd64 (SMP w/6 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#958923: RM: xul-ext-quotecolors/0.3-6 in old-stable
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: rm Dear RT, the package xul-ext-quotecolors, an Thunderbird extension, isn't usable any longer since Thunderbird ESR has moved to 68.x due API changes within Thunderbird. It's dead from the upstream side and wont get updates in the future, please remove the package from the old-stable release. There is a RC bug about the non usable functionality in testing. https://bugs.debian.org/950512 I also requested the removal from unstable https://bugs.debian.org/958913 Thanks Carsten Schoenert -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.5.0-1-amd64 (SMP w/6 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Re: [Pkg-rust-maintainers] rust ecosystem worries of a release team member
Hi, Am 03.02.20 um 13:08 schrieb Sylvestre Ledru: ... > I have been told that the transition of one of the build-dep is blocked by > packages blocked in NEW... > Not sure which one. this is more or less what I mean, we should get clearance about the root of problems. > We already started a discussion with the Debian release management team to > simplify the acceptation of > packages already existing in the archive but with a new binary coming. Sounds good! >> While Fosdem I've talked with Paul > Paul ? Paul Grevers aka elbrus ... > FYI, I've never been a QA manager at Mozilla. I was running the release > management team > (but doing something else now). > But yeah, I do see what you mean. Thanks. O.k. than my minds have fooled me, but never mind, glad you see what I'd like to mention. -- Regards Carsten Schoenert
Re: [Pkg-rust-maintainers] rust ecosystem worries of a release team member
Hi Sylvestre, Am 04.01.20 um 17:19 schrieb Sylvestre Ledru: > Honestly, (shame on me) I didn't pay much attention to the cbindgen > migration > or other migrations of rust binaries. > > Mostly because when I look at the transition dashboard, I don't > understand why they are blocked. For example: > fd find is blocked by > https://qa.debian.org/excuses.php?package=rust-ansi-term > Also because we are doing (too?) many changes. > > Anyway, sorry about that, I will try to make cbindgen migrated asap! is there any plan or list of issues ready that the rustc people are aware that need be done next work prepared or written somewhere so other Debian maintainers can see what's going on? While Fosdem I've talked with Paul about the currently not migrating Thunderbird package. And we talked of course about possibilities how to solve the unfortunate situation. Quite a lot of of Debian users have emailed me and asking why Thunderbird 68.x isn't available in testing but Firefox is. And it's sometimes difficult to explain the users the current situation, you as Mozilla QA manager for sure knows that the current ESR cycle is almost on 50% of the planned lifetime. Furthermore it's also quite difficult for AddOn maintainers in Debian to work on the extensions and prepare them than for p-u too due the outdated version of TB in testing. The stable RM are also not that happy with that circumstance. Maybe we need to create some more tools that helping to visualize a dependency chain and mark some package that need to worked on first. Such tools could be a thing for GSoC? So can we work out a list of packages that need to get prepared first to get the dependencies fixed? I've no deeper knowledge of the Rust ecosystem so my assumptions wouldn't help much I guess. -- Regards Carsten Schoenert
Bug#948205: buster-pu: package sogo-connector/60.0.2-1
Hi again, On Sat, Jan 25, 2020 at 07:34:20PM +, Adam D. Barratt wrote: > The delights of mozilla-related packages and stable. :-( Please go > ahead. thanks! Also in NEW due the new binary package. Regards Carsten
Bug#948203: buster-pu: package compactheader/2.1.6-1
Hello Adam, On Sat, Jan 25, 2020 at 07:36:03PM +, Adam D. Barratt wrote: > It's obviously not an ideal situation, but please go ahead. yes, hopefully Mozilla wont change their AddOn API again within the next ESR cycle of TB. Uploaded minutes ago, it's in NEW due the new binary package. Hopefully the FTP-Master can act in time. :) Regards Carsten
Bug#948203: buster-pu: package compactheader/2.1.6-1
Am 05.01.20 um 10:50 schrieb Carsten Schoenert: > Hello RT, > > I'd like to update the package compactheader in buster as the existing > version in buster isn't compatible with the new Thunderbird ESR series > 68.x any more. > > The current thunderbird package in stable-security has already a Breaks > on xul-ext-compachtheader << 3.0.0~ to force a removal of the old > incompatible version. > > Unfortunately the version of thunderbird in testing is stocking to > 60.9.1 due blocked migration from unstable. I've forgotten to add that this new package version also introduces a new binary package webext-compactheader and the existing package xul-ext-compactheader is moved over into a transitional package which is depending on webext-compactheader. The package for buster would be a rebuild of the current package in unstable. Currently there is no version of compactheader in testing due missing thunderbird package >= 68.0. -- Regards Carsten Schoenert
Bug#948205: buster-pu: package sogo-connector/60.0.2-1
Package: release.debian.org Severity: normal Tags: buster User: release.debian@packages.debian.org Usertags: pu Dear RT, I'd like to update the package sogo-connector in buster as the existing version in buster isn't compatible with the new Thunderbird ESR series 68.x any more. The current thunderbird package in stable-security has already a Breaks on xul-ext-sogo-connector << 68.0.0-1~ to force a removal of the old incompatible version. The version for buster would be a rebuild of the version 68.0.1-1 in testing which also introduces a new binary package webext-sogo-connector because the old xul-ext-sogo-connecter is now an transitional package which is depending on the webext-* package. The same technical transition was done e.g. for the dispmua package too. Regards Carsten -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.3.0-3-amd64 (SMP w/6 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#948203: buster-pu: package compactheader/2.1.6-1
Package: release.debian.org Severity: normal Tags: buster User: release.debian@packages.debian.org Usertags: pu Hello RT, I'd like to update the package compactheader in buster as the existing version in buster isn't compatible with the new Thunderbird ESR series 68.x any more. The current thunderbird package in stable-security has already a Breaks on xul-ext-compachtheader << 3.0.0~ to force a removal of the old incompatible version. Unfortunately the version of thunderbird in testing is stocking to 60.9.1 due blocked migration from unstable. -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.3.0-3-amd64 (SMP w/6 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#946081: RM: firetray/oldstable/stable/testing/unstable -- ROM; Orphaned and dead upstream, not needed any more
Package: ftp.debian.org Severity: normal firetray isn't developed and maintained upstream anymore and by the discuntinued legacy AddOn API in Thunderbird obsolete and useless now. It simply isn't working any more now Thunderbird 68.x is in the archive. Please remove this package completely from the archive. There is a bug report about the not working package in https://bugs.debian.org/946030 Regards Carsten
Bug#944443: kopano-webapp and/or kopanocore missing a versioned (test) dependency on the other?
Hello Paul, On 14.11.19 08:58, Paul Gevers wrote: ... > There's a third option: instead of requesting an unblock, I'll schedule > the test with both packages from unstable. Than all the other tooling > will do the right thing (assuming the test passes as expected). thank you very much! And indeed this is working too. ;) No both packages have already migrated. -- Mit freundlichen Grüßen Carsten Schönert
Bug#944443: kopano-webapp and/or kopanocore missing a versioned (test) dependency on the other?
Hello Paul, Am 13.11.19 um 19:35 schrieb Paul Gevers: > Hi Carsten, > > On 13-11-2019 07:20, Carsten Schoenert wrote: >> But I"m struggling *how* to add such an versioned test dependency. This >> version requirements are only needed for the autopkgtest(s) so because >> of this we haven't bumped regulary and wanted package dependency. > > Test version requirements go into debian/tests/control. Just add them to > the appropriate Depends field. unfortunately this is not possible this way as the test for kopano-webapp itself is structured as various depending segments (like in kopanocore too) there new packages get installed and we need a pre-configured mariadb-server instance to get the test working. https://salsa.debian.org/giraffe-team/kopano-webapp/blob/debian/sid/debian/tests/smoke So the test is first installing the database server and afterwards the kopano-webapp-apache2 package as we want to see all automatic pulled in dependencies are working. One of the dependencies here is kopano-contacts from src:kopanocore, and we pull also kopano-utils. The tool kopano-admin (provided by kopano-utils) is currently working internally differently in testing. As we install packages from kopanocore as an automatic dependency I see no way to control within the test the version we need as we can only relay on the version controlling within the packages itself. Sure, we could add a versioned dependency on kopanocore within kopano-webapp, but there is no real technical reason for this, it would only help that the autopkgtests do work. And as there is no real need for a version bump on kopanocore we didn't have done this yet. >> I'm happy to add such a needed version anywhere but I simply don't know >> how. Any example package I can look at something similar. I see currently only two possibilities to get kopanocore migrating to testing. One is to add a new higher version on the depending kopano-contacts in kopano-webapp-common (which then pulls kopano-libs), and the second option would be an unblock by the RT. This is still the right solution in my eyes. The first option would need of course a new upload of kopano-webapp. -- Regards Carsten Schoenert
Bug#944443: unblock: kopanocore/8.7.0-5 into testing
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package kopanocore in unstable We've needed to cherry-pick some upstream changes for src:kopanocore to fix some RC issues in unstable/testing that has changed the defaults for creation of new system users. Due this the test of kopano-webapp from testing against kopanocore from unstable is currently failing. The kopano-webapp package uses quite 90% of the same autopkgtest stuff as already in kopanocore is existing and used. While running the autopkgtest of kopano-webapp from testing against kopanocore in unstable this makeS the autopkgtest failing, due the changed default behavior in the kopanocore in unstable. There is no technical reason to add some Breaks stuff to kopanocore or kopano-webapp, there is no ABI or API change happen. The autopkgtest for kopano-webapp was adjusted with a new uploaded version (3.5.12-1) to keep track of the changed default kopanocore behavior and the test of this version in unstable is successful. So please unblock kopanocore so it can migrate to testing. We need afterwards to get the same issues for kopanocore fixed in stable. Thanks! Carsten unblock kopanocore/8.7.0-5 -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.2.0-3-amd64 (SMP w/6 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#930968: unblock: thunderbird/1:60.7.2-1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package thunderbird And one more security related update of the current Thunderbird ESR version 60.7 did happen. A few says ago Mozilla has released Thunderbird 60.7.2 which fixes two CVE vulnerabilities. As usual no major changes did happen to the packaging, I just imported the new source tarball and rebuild the package. Please look further down to see which CVE numbers are marked as fixed by this new TB version. diff -puNr -Naur thunderbird-60.7.1/debian/ thunderbird-60.7.2/debian/ --- thunderbird-60.7.1/debian/changelog 2019-06-14 07:25:35.0 +0200 +++ thunderbird-60.7.2/debian/changelog 2019-06-21 18:48:30.0 +0200 @@ -1,3 +1,12 @@ +thunderbird (1:60.7.2-1) unstable; urgency=medium + + * [d6c79ed] New upstream version 60.7.2 +Fixed CVE issues in upstream version 60.7.2 (MFSA 2019-20 +CVE-2019-11707: Type confusion in Array.pop +CVE-2019-11708: sandbox escape using Prompt:Open + + -- Carsten Schoenert Fri, 21 Jun 2019 18:48:43 +0200 + thunderbird (1:60.7.1-1) unstable; urgency=high * [f791dee] New upstream version 60.7.1 Hopefully tha last update before the planed release date of Buster. :) unblock thunderbird/1:60.7.2-1 -- System Information: Debian Release: 10.0 APT prefers testing APT policy: (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-5-amd64 (SMP w/6 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#930550: unblock: thunderbird/1:60.7.1-1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package thunderbird The release of an updated Thunderbird package by Mozilla was needed due found CVE issues. There are no changes did happen to the packaging thunderbird itself, it was only necessary to import the new sources and start a rebuild. The modification within the debian folder are really small and simple. $ diff -Naur thunderbird-60.7.0/debian/ thunderbird-60.7.1/debian/ diff -puNr -Naur thunderbird-60.7.0/debian/changelog thunderbird-60.7.1/debian/changelog --- thunderbird-60.7.0/debian/changelog 2019-06-15 10:00:28.591606482 +0200 +++ thunderbird-60.7.1/debian/changelog 2019-06-15 10:02:39.604085695 +0200 @@ -1,3 +1,14 @@ +thunderbird (1:60.7.1-1) unstable; urgency=high + + * [f791dee] New upstream version 60.7.1 +Fixed CVE issues in upstream version 60.7.1 (MFSA 2019-17) +CVE-2019-11703: Heap buffer overflow in icalparser.c +CVE-2019-11704: Heap buffer overflow in icalvalue.c +CVE-2019-11705: Stack buffer overflow in icalrecur.c +CVE-2019-11706: Type confusion in icalproperty.c + + -- Carsten Schoenert Fri, 14 Jun 2019 07:25:35 +0200 + thunderbird (1:60.7.0-1) unstable; urgency=medium * [f6dd130] New upstream version 60.7.0 So please consider to unblock the thunderbird package 1:60.7.1-1. unblock thunderbird/1:60.7.1-1 -- System Information: Debian Release: 10.0 APT prefers testing APT policy: (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386, aarch64, arm64 Kernel: Linux 4.19.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#929559: unblock: thunderbird/1:60.7.0-1
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package thunderbird
The package Thunderbird got the usual update to a new ESR version with
an update to 60.7.0.
This update fixes some known CVEs.
The changes to the packaging can be seen within the following diff output:
$ diff -Naur thunderbird-60.6.1/debian/ thunderbird-60.7.0/debian/
diff -puNr -Naur thunderbird-60.6.1/debian/changelog
thunderbird-60.7.0/debian/changelog
--- thunderbird-60.6.1/debian/changelog 2019-03-27 18:22:51.0 +0100
+++ thunderbird-60.7.0/debian/changelog 2019-05-23 17:03:27.0 +0200
@@ -1,3 +1,30 @@
+thunderbird (1:60.7.0-1) unstable; urgency=medium
+
+ * [f6dd130] New upstream version 60.7.0
+Fixed CVE issues in upstream version 60.7.0 (MFSA 2019-15)
+CVE-2019-9816: Type confusion with object groups and UnboxedObjects
+CVE-2019-9817: Stealing of cross-domain images using canvas
+CVE-2019-9819: Compartment mismatch with fetch API
+CVE-2019-9820: Use-after-free of ChromeEventHandler by DocShell
+CVE-2019-11691: Use-after-free in XMLHttpRequest
+CVE-2019-11692: Use-after-free removing listeners in the event listener
+manager
+CVE-2019-11693: Buffer overflow in WebGL bufferdata on Linux
+CVE-2019-7317: Use-after-free in png_image_free of libpng library
+CVE-2019-9797: Cross-origin theft of images with createImageBitmap
+CVE-2018-18511: Cross-origin theft of images with
+ImageBitmapRenderingContext
+CVE-2019-11698: Theft of user history data through drag and drop of
+hyperlinks to and from bookmarks
+CVE-2019-5798: Out-of-bounds read in Skia
+CVE-2019-9800: Memory safety bugs fixed in Firefox 67, Firefox ESR 60.7,
+ and Thunderbird 60.7
+ * [4106d54] rebuild patch queue from patch-queue branch
+added patch:
+fixes/rust-ignore-not-available-documentation.patch
+
+ -- Carsten Schoenert Thu, 23 May 2019 17:03:27
+0200
+
thunderbird (1:60.6.1-1) unstable; urgency=medium
[ intrigeri ]
diff -puNr -Naur
thunderbird-60.6.1/debian/patches/fixes/rust-ignore-not-available-documentation.patch
thunderbird-60.7.0/debian/patches/fixes/rust-ignore-not-available-documentation.patch
---
thunderbird-60.6.1/debian/patches/fixes/rust-ignore-not-available-documentation.patch
1970-01-01 01:00:00.0 +0100
+++
thunderbird-60.7.0/debian/patches/fixes/rust-ignore-not-available-documentation.patch
2019-05-23 17:02:09.0 +0200
@@ -0,0 +1,43 @@
+From: Carsten Schoenert
+Date: Wed, 22 May 2019 21:48:32 +0200
+Subject: rust: ignore not available documentation
+
+Picked up from a patch list for FF from Arch.
+---
+ servo/components/style/lib.rs| 2 --
+ servo/components/style_traits/lib.rs | 2 --
+ 2 files changed, 4 deletions(-)
+
+diff --git a/servo/components/style/lib.rs b/servo/components/style/lib.rs
+index 49acbe3..0d3871c 100644
+--- a/servo/components/style/lib.rs
b/servo/components/style/lib.rs
+@@ -23,7 +23,6 @@
+ //! [cssparser]: ../cssparser/index.html
+ //! [selectors]: ../selectors/index.html
+
+-#![deny(missing_docs)]
+
+ extern crate app_units;
+ extern crate arrayvec;
+@@ -148,7 +147,6 @@ pub mod values;
+ /// Generated from the properties.mako.rs template by build.rs
+ #[macro_use]
+ #[allow(unsafe_code)]
+-#[deny(missing_docs)]
+ pub mod properties {
+ include!(concat!(env!("OUT_DIR"), "/properties.rs"));
+ }
+diff --git a/servo/components/style_traits/lib.rs
b/servo/components/style_traits/lib.rs
+index 3b7304b..0f05333 100644
+--- a/servo/components/style_traits/lib.rs
b/servo/components/style_traits/lib.rs
+@@ -9,8 +9,6 @@
+ #![crate_name = "style_traits"]
+ #![crate_type = "rlib"]
+
+-#![deny(unsafe_code, missing_docs)]
+-
+ extern crate app_units;
+ #[macro_use] extern crate bitflags;
+ #[macro_use] extern crate cssparser;
diff -puNr -Naur thunderbird-60.6.1/debian/patches/series
thunderbird-60.7.0/debian/patches/series
--- thunderbird-60.6.1/debian/patches/series2019-03-26 21:53:39.0
+0100
+++ thunderbird-60.7.0/debian/patches/series2019-05-23 17:02:09.0
+0200
@@ -38,3 +38,4 @@ porting-armel/Bug-1463035-Remove-MOZ_SIG
porting-armel/Avoid-using-vmrs-vmsr-on-armel.patch
porting-powerpc/powerpc-Don-t-use-static-page-sizes-on-powerpc.patch
fixes/Bug-1526744-find-dupes.py-Calculate-md5-by-chunk.patch
+fixes/rust-ignore-not-available-documentation.patch
unblock thunderbird/1:60.7.0-1
-- System Information:
Debian Release: 10.0
APT prefers testing
APT policy: (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, aarch64, arm64
Kernel: Linux 4.19.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8),
LANGUAGE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Bug#927406: unblock: libcoap2/4.2.0-2
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package libcoap2
Upstream pointed me to an upstream issue after the release of version
4.2.0 a few weeks ago that might provoke a crash of a linked application
due a possible null pointer dereferenced access.
This is happen within the GnuTLS part of libcoap.
The fix was easy, use correct pointer arithmetic and logic in the code.
But the review of the attempt to fix this in the upstream project wasn't
done carefully, so a second patch was needed.
I applied both patches (and did not merge them together) to keep up the
fixing more in sync how it happen in the upstream project.
This is a debdiff between version 4.2.0-1 (testing) and 4.2.0-2
(unstable).
$ cat libcoap2_4.2.0-2.debdiff
diff -Nru libcoap2-4.2.0/debian/changelog libcoap2-4.2.0/debian/changelog
--- libcoap2-4.2.0/debian/changelog 2019-03-02 17:35:18.0 +0100
+++ libcoap2-4.2.0/debian/changelog 2019-04-13 08:00:48.0 +0200
@@ -1,3 +1,14 @@
+libcoap2 (4.2.0-2) unstable; urgency=medium
+
+ * [2f3b27d] rebuild patch queue from patch-queue branch
+added patches (cherry-picked from upstream):
+Client-crashes-in-gnutls-psk-setup.patc
+Fix-321-was-not-correctly-implemented.patch
+These patches fixing a possible crash in the GnuTLS bindings due a
+possible null pointer dereferenced access.
+
+ -- Carsten Schoenert Sat, 13 Apr 2019 08:00:48
+0200
+
libcoap2 (4.2.0-1) unstable; urgency=medium
* [b0fedea] New upstream version 4.2.0
diff -Nru
libcoap2-4.2.0/debian/patches/Client-crashes-in-gnutls-psk-setup.patch
libcoap2-4.2.0/debian/patches/Client-crashes-in-gnutls-psk-setup.patch
--- libcoap2-4.2.0/debian/patches/Client-crashes-in-gnutls-psk-setup.patch
1970-01-01 01:00:00.0 +0100
+++ libcoap2-4.2.0/debian/patches/Client-crashes-in-gnutls-psk-setup.patch
2019-04-13 07:57:35.0 +0200
@@ -0,0 +1,24 @@
+From: Jon Shallow
+Date: Sun, 31 Mar 2019 20:33:46 +0100
+Subject: Client crashes in gnutls psk setup
+
+src/coap_gnutls.c:
+
+Correct typo when null terminating username.
+---
+ src/coap_gnutls.c | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/src/coap_gnutls.c b/src/coap_gnutls.c
+index 026f378..08f3099 100644
+--- a/src/coap_gnutls.c
b/src/coap_gnutls.c
+@@ -404,7 +404,7 @@ psk_client_callback(gnutls_session_t g_session,
+ *username = gnutls_malloc(identity_len+1);
+ if (*username) {
+ memcpy(*username, identity, identity_len);
+-*username[identity_len] = '\0';
++username[identity_len] = '\0';
+ }
+
+ key->data = gnutls_malloc(psk_len);
diff -Nru
libcoap2-4.2.0/debian/patches/Fix-321-was-not-correctly-implemented.patch
libcoap2-4.2.0/debian/patches/Fix-321-was-not-correctly-implemented.patch
--- libcoap2-4.2.0/debian/patches/Fix-321-was-not-correctly-implemented.patch
1970-01-01 01:00:00.0 +0100
+++ libcoap2-4.2.0/debian/patches/Fix-321-was-not-correctly-implemented.patch
2019-04-13 07:57:35.0 +0200
@@ -0,0 +1,26 @@
+From: Jon Shallow
+Date: Sun, 7 Apr 2019 17:48:46 +0100
+Subject: Fix #321 was not correctly implemented
+
+While #321 prevented a core dump, that fix still caused memory corruption.
+
+src/coap_gnutls.c:
+
+Correct the code to correctly NULL terminate the created username.
+---
+ src/coap_gnutls.c | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/src/coap_gnutls.c b/src/coap_gnutls.c
+index 08f3099..cbfdffb 100644
+--- a/src/coap_gnutls.c
b/src/coap_gnutls.c
+@@ -404,7 +404,7 @@ psk_client_callback(gnutls_session_t g_session,
+ *username = gnutls_malloc(identity_len+1);
+ if (*username) {
+ memcpy(*username, identity, identity_len);
+-username[identity_len] = '\0';
++(*username)[identity_len] = '\0';
+ }
+
+ key->data = gnutls_malloc(psk_len);
diff -Nru libcoap2-4.2.0/debian/patches/series
libcoap2-4.2.0/debian/patches/series
--- libcoap2-4.2.0/debian/patches/series2019-03-02 17:33:17.0
+0100
+++ libcoap2-4.2.0/debian/patches/series2019-04-13 07:57:35.0
+0200
@@ -1,2 +1,4 @@
examples-Makefile.am-remove-DTLS_LIBS-variable.patch
examples-Makefile.am-create-DTLS-specific-binary-names.patch
+Client-crashes-in-gnutls-psk-setup.patch
+Fix-321-was-not-correctly-implemented.patch
unblock libcoap2/4.2.0-2
-- System Information:
Debian Release: buster/sid
APT prefers testing
APT policy: (500, 'testing'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, aarch64, arm64
Kernel: Linux 4.19.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8),
LANGUAGE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Bug#926283: unblock: thunderbird/1:60.6.1-1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package thunderbird The package Thunderbird got the usual update to a new ESR version with an update to 60.6.1. This update fixes some known CVEs. The changes to the packaging can be seen within the following diff output: diff -puNr thunderbird-60.5.1/debian/changelog thunderbird-60.6.1/debian/changelog --- thunderbird-60.5.1/debian/changelog 2019-02-14 20:01:03.0 +0100 +++ thunderbird-60.6.1/debian/changelog 2019-03-27 18:22:51.0 +0100 @@ -1,3 +1,32 @@ +thunderbird (1:60.6.1-1) unstable; urgency=medium + + [ intrigeri ] + * [2013645] d/rules: drop useless usage of dpkg-parsechangelog + + [ Carsten Schoenert ] + * [daf1252] New upstream version 60.6.1 +Fixed CVE issues in upstream version 60.6.0 (MFSA 2019-11) +CVE-2019-9790: Use-after-free when removing in-use DOM elements +CVE-2019-9791: Type inference is incorrect for constructors entered + through on-stack replacement with IonMonkey +CVE-2019-9792: IonMonkey leaks JS_OPTIMIZED_OUT magic value to script +CVE-2019-9793: Improper bounds checks when Spectre mitigations are disabled +CVE-2019-9794: Command line arguments not discarded during execution +CVE-2019-9795: Type-confusion in IonMonkey JIT compiler +CVE-2019-9796: Use-after-free with SMIL animation controller +CVE-2018-18506: Proxy Auto-Configuration file can define localhost access +to be proxied +CVE-2019-9788: Memory safety bugs fixed in Firefox 66, Firefox ESR 60.6, + and Thunderbird 60.6 +Fixed CVE issues in upstream version 60.6.1 (MFSA 2019-12) +CVE-2019-9810: IonMonkey MArraySlice has incorrect alias information +CVE-2019-9813: Ionmonkey type confusion with __proto__ mutations + * [f88a505] rebuild patch queue from patch-queue branch +added patch: +fixes/Bug-1526744-find-dupes.py-Calculate-md5-by-chunk.patch + + -- Carsten Schoenert Wed, 27 Mar 2019 18:22:51 +0100 + thunderbird (1:60.5.1-1) unstable; urgency=medium [ Alexander Nitsch ] diff -puNr thunderbird-60.5.1/debian/patches/debian-hacks/stop-configure-if-with-system-bz2-was-passed-but-no-.patch thunderbird-60.6.1/debian/patches/debian-hacks/stop-configure-if-with-system-bz2-was-passed-but-no-.patch --- thunderbird-60.5.1/debian/patches/debian-hacks/stop-configure-if-with-system-bz2-was-passed-but-no-.patch 2019-02-14 19:46:50.0 +0100 +++ thunderbird-60.6.1/debian/patches/debian-hacks/stop-configure-if-with-system-bz2-was-passed-but-no-.patch 2019-03-26 21:53:39.0 +0100 @@ -8,10 +8,10 @@ Subject: stop configure if '--with-syste 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/old-configure.in b/old-configure.in -index f78c54d..506c08e 100644 +index 8ac71d1..5769ef6 100644 --- a/old-configure.in +++ b/old-configure.in -@@ -1825,7 +1825,7 @@ if test -z "$BZ2_DIR" -o "$BZ2_DIR" = no; then +@@ -1826,7 +1826,7 @@ if test -z "$BZ2_DIR" -o "$BZ2_DIR" = no; then MOZ_SYSTEM_BZ2= else AC_CHECK_LIB(bz2, BZ2_bzread, [MOZ_SYSTEM_BZ2=1 MOZ_BZ2_LIBS="-lbz2"], diff -puNr thunderbird-60.5.1/debian/patches/fixes/Bug-1526744-find-dupes.py-Calculate-md5-by-chunk.patch thunderbird-60.6.1/debian/patches/fixes/Bug-1526744-find-dupes.py-Calculate-md5-by-chunk.patch --- thunderbird-60.5.1/debian/patches/fixes/Bug-1526744-find-dupes.py-Calculate-md5-by-chunk.patch 1970-01-01 01:00:00.0 +0100 +++ thunderbird-60.6.1/debian/patches/fixes/Bug-1526744-find-dupes.py-Calculate-md5-by-chunk.patch 2019-03-26 21:53:39.0 +0100 @@ -0,0 +1,49 @@ +From: Rob Lemley +Date: Thu, 21 Feb 2019 15:14:17 -0500 +Subject: Bug 1526744 - find-dupes.py: Calculate md5 by chunk. + +Read the file in chunks and use md5.update() rather than reading the entire +file into RAM and calculating the hash all at once. This prevents out of memory +errors on build systems with low RAM. +--- + toolkit/mozapps/installer/find-dupes.py | 18 ++ + 1 file changed, 14 insertions(+), 4 deletions(-) + +diff --git a/toolkit/mozapps/installer/find-dupes.py b/toolkit/mozapps/installer/find-dupes.py +index 3935b79..0ff7efc 100644 +--- a/toolkit/mozapps/installer/find-dupes.py b/toolkit/mozapps/installer/find-dupes.py +@@ -39,19 +39,29 @@ def is_l10n_file(path): + def normalize_path(p): + return normalize_osx_path(p) + ++def md5hash_size(fp, chunk_size=1024*10): ++md5 = hashlib.md5() ++size = 0 ++while True: ++data = fp.read(chunk_size) ++if not data: ++break ++md5.update(data) ++size += len(data) ++ ++return md5.digest(), size + + def find_dupes(source, allowed_dupes, bail=True): + allowed_dupes = set(allowed_dupes) + md5s = OrderedDict() + for p, f in UnpackFinder(source): +-content = f.open(
Bug#926008: unblock: kicad-templates/5.1.0-1
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package kicad-templates
The kicad-templates package provides additional data for prepared
electronics schematic and PCB data for the kicad application. The data
of the templates are simple text files and by this the package is
platform independent.
Even if the update of the kicad package (see #926004) isn't going to be
accepted kicad-templates should make it's way into Buster finally.
The update within the upstream version is small and really clear. But
also the Debian packaging got just one small update on the
Standards-Version and the updated copyright file.
diff -Nru kicad-templates-5.0.2/debian/changelog
kicad-templates-5.1.0/debian/changelog
--- kicad-templates-5.0.2/debian/changelog 2018-12-04 21:13:06.0
+0100
+++ kicad-templates-5.1.0/debian/changelog 2019-03-11 20:37:17.0
+0100
@@ -1,3 +1,12 @@
+kicad-templates (5.1.0-1) unstable; urgency=medium
+
+ * [db07e5c] New upstream version 5.1.0
+ * [98163f0] d/control: increase Standards-Version to 4.3.0
++ No further changes needed.
+ * [a21730b] d/copyright: update years on contributors
+
+ -- Carsten Schoenert Mon, 11 Mar 2019 20:37:17
+0100
+
kicad-templates (5.0.2-1) unstable; urgency=medium
* [7b1e635] New upstream version 5.0.2
diff -Nru kicad-templates-5.0.2/debian/control
kicad-templates-5.1.0/debian/control
--- kicad-templates-5.0.2/debian/control2018-08-31 22:12:24.0
+0200
+++ kicad-templates-5.1.0/debian/control2019-03-11 20:36:08.0
+0100
@@ -10,7 +10,7 @@
cmake,
Vcs-Git: https://salsa.debian.org/electronics-team/KiCad/kicad-templates.git
Vcs-Browser: https://salsa.debian.org/electronics-team/KiCad/kicad-templates
-Standards-Version: 4.2.1
+Standards-Version: 4.3.0
Homepage: https://github.com/KiCad/kicad-templates
Package: kicad-templates
diff -Nru kicad-templates-5.0.2/debian/copyright
kicad-templates-5.1.0/debian/copyright
--- kicad-templates-5.0.2/debian/copyright 2018-08-31 22:12:45.0
+0200
+++ kicad-templates-5.1.0/debian/copyright 2019-03-11 20:36:51.0
+0100
@@ -10,11 +10,11 @@
Material'."
Files: *
-Copyright: 2018 KiCad Community
+Copyright: 2019 KiCad Community
License: CC-BY-SA-4.0-with-exception
Files: debian/*
-Copyright: 2018, Carsten Schoenert
+Copyright: 2019, Carsten Schoenert
2017-2018, Jean-Samuel Reynaud
License: GPL-2+
diff -Nru kicad-templates-5.0.2/raspberrypi_hat/raspberrypi_hat.kicad_pcb
kicad-templates-5.1.0/raspberrypi_hat/raspberrypi_hat.kicad_pcb
--- kicad-templates-5.0.2/raspberrypi_hat/raspberrypi_hat.kicad_pcb
2018-11-15 18:38:06.0 +0100
+++ kicad-templates-5.1.0/raspberrypi_hat/raspberrypi_hat.kicad_pcb
2019-02-06 20:45:57.0 +0100
@@ -435,7 +435,7 @@
(net 10 "Net-(J9-Pad2)"))
(pad 8 smd rect (at 2.7 -1.905 180) (size 1.55 0.6) (layers F.Cu F.Paste
F.Mask)
(net 8 /P3V3))
-(model ${KISYS3DMOD}/Package_SOIC.3dshapes/SOIC-8_3.9x4.9mm_P1.27mm.wrl
+(model ${KISYS3DMOD}/Package_SO.3dshapes/SOIC-8_3.9x4.9mm_P1.27mm.wrl
(at (xyz 0 0 0))
(scale (xyz 1 1 1))
(rotate (xyz 0 0 0))
unblock kicad-templates/5.1.0-1
-- System Information:
Debian Release: buster/sid
APT prefers testing
APT policy: (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.19.0-4-amd64 (SMP w/6 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8),
LANGUAGE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Bug#926007: unblock: kicad-symbols/5.1.0-1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package kicad-symbols The kicad-symbols package provides additional data for schematic symbols for the kicad application. The schematic symbols data are simple text files and by this the package is platform independent. Even if the update of the kicad package (see #926004) isn't going to be accepted kicad-symbols should make it's way into Buster finally. A full debdiff is big due the updates to the upstream text files. Due it's size I've uploaded the full debdiff to p.d.o. https://people.debian.org/~tijuca/unblock/kicad-symbols-full.debdiff.tar.xz The modification of the debian folder between the version in testing and unstable is on contray really small. diff -puNr -puNr kicad-symbols-5.0.2/debian/changelog kicad-symbols-5.1.0/debian/changelog --- kicad-symbols-5.0.2/debian/changelog2018-12-04 21:07:58.0 +0100 +++ kicad-symbols-5.1.0/debian/changelog2019-03-11 20:26:47.0 +0100 @@ -1,3 +1,12 @@ +kicad-symbols (5.1.0-1) unstable; urgency=medium + + * [e0c482d] New upstream version 5.1.0 + * [ffcb043] d/control: increase Standards-Version to 4.3.0 ++ No further changes needed. + * [591c592] d/copyright: update years on contributors + + -- Carsten Schoenert Mon, 11 Mar 2019 20:26:47 +0100 + kicad-symbols (5.0.2-1) unstable; urgency=medium * [97acd5a] New upstream version 5.0.2 diff -puNr -puNr kicad-symbols-5.0.2/debian/control kicad-symbols-5.1.0/debian/control --- kicad-symbols-5.0.2/debian/control 2018-08-31 22:04:13.0 +0200 +++ kicad-symbols-5.1.0/debian/control 2019-03-11 20:26:41.0 +0100 @@ -10,7 +10,7 @@ Build-Depends: cmake, Vcs-Git: https://salsa.debian.org/electronics-team/KiCad/kicad-symbols.git Vcs-Browser: https://salsa.debian.org/electronics-team/KiCad/kicad-symbols -Standards-Version: 4.2.1 +Standards-Version: 4.3.0 Homepage: https://kicad.github.io/symbols Package: kicad-symbols diff -puNr -puNr kicad-symbols-5.0.2/debian/copyright kicad-symbols-5.1.0/debian/copyright --- kicad-symbols-5.0.2/debian/copyright2018-08-31 22:04:17.0 +0200 +++ kicad-symbols-5.1.0/debian/copyright2019-03-11 20:26:41.0 +0100 @@ -10,11 +10,11 @@ Comment: Like all KiCad libraries the li Material'." Files: * -Copyright: 2018 KiCad Community +Copyright: 2019 KiCad Community License: CC-BY-SA-4.0-with-exception Files: debian/* -Copyright: 2018, Carsten Schoenert +Copyright: 2019, Carsten Schoenert 2017-2018, Jean-Samuel Reynaud License: GPL-2+ unblock kicad-symbols/5.1.0-1 -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-4-amd64 (SMP w/6 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#926006: unblock: kicad-packages3d/5.1.0-1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package kicad-packages3d The kicad-packages3d package provides additional data of 3D-models for the kicad application. The 3D-models data are simple text files and by this the package is platform independent. Even if the update of the kicad package (see #926004) isn't going to be accepted kicad-packages3d should make it's way into Buster finally. A full debdiff is big due the updates to the upstream text files. Due it's size I've uploaded the full debdiff to p.d.o. https://people.debian.org/~tijuca/unblock/kicad-packages3d-full.debdiff.tar.xz A diff for the debian folder between the version in testing and unstable is about 95% changes to the debian/copyright file and the helper files of cme around this. The remaining about 5% is on updating the Standards-Versions and the new debian/changelog entry as no other modifications to the packaging was required. diff -puNr -puNr kicad-packages3d-5.0.2/debian/changelog kicad-packages3d-5.1.0/debian/changelog --- kicad-packages3d-5.0.2/debian/changelog 2018-12-06 16:47:58.0 +0100 +++ kicad-packages3d-5.1.0/debian/changelog 2019-03-15 20:15:27.0 +0100 @@ -1,3 +1,14 @@ +kicad-packages3d (5.1.0-1) unstable; urgency=medium + + * [674fff9] New upstream version 5.1.0 + * [387d52f] d/control: increase Standards-Version to 4.3.0 ++ No further changes needed. + * [90c3af4] copyright: add some additional information for cme script ++ Add some helping content into debian/fill.copyright.blanks.yml. + * [581a7ec] copyright: update information due release of 5.1.0 + + -- Carsten Schoenert Fri, 15 Mar 2019 20:15:27 +0100 + kicad-packages3d (5.0.2-1) unstable; urgency=medium * [aeb1d03] New upstream version 5.0.2 diff -puNr -puNr kicad-packages3d-5.0.2/debian/control kicad-packages3d-5.1.0/debian/control --- kicad-packages3d-5.0.2/debian/control 2018-08-31 21:43:47.0 +0200 +++ kicad-packages3d-5.1.0/debian/control 2019-03-15 00:26:53.0 +0100 @@ -10,7 +10,7 @@ Build-Depends: cmake, Vcs-Git: https://salsa.debian.org/electronics-team/KiCad/kicad-packages3d.git Vcs-Browser: https://salsa.debian.org/electronics-team/KiCad/kicad-packages3d -Standards-Version: 4.2.1 +Standards-Version: 4.3.0 Homepage: https://kicad.github.io/packages3d Package: kicad-packages3d diff -puNr -puNr kicad-packages3d-5.0.2/debian/copyright kicad-packages3d-5.1.0/debian/copyright --- kicad-packages3d-5.0.2/debian/copyright 2018-08-31 21:44:08.0 +0200 +++ kicad-packages3d-5.1.0/debian/copyright 2019-03-15 20:09:48.0 +0100 @@ -10,10 +10,17 @@ Comment: Like all KiCad libraries the li Material'." Files: * -Copyright: 2018, KiCad Community +Copyright: 2018, 2019, KiCad Community License: CC-BY-SA-4.0-with-exception [snip] [a lot of other modifications to d/copyright] The full diff for the debian folder I've uploaded again to p.d.o. https://people.debian.org/~tijuca/unblock/kicad-packages3d.debian-folder.debdiff unblock kicad-packages3d/5.1.0-1 -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-4-amd64 (SMP w/6 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#926005: unblock: kicad-footprints/5.1.0-1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package kicad-footprints The kicad-footprints package provides basic footprint data for the kicad application. The footprint data are simple text files and by this the package is platform independet. Even if the update of the kicad package (see #926004) isn't going to be accepted kicad-footprints should make it's way into Buster finally. A full debdiff is big due the updates to the upstream text files. Due it's size I've uploaded the full debdiff to p.d.o. https://people.debian.org/~tijuca/unblock/kicad-footprints-full.debdiff.tar.xz The modification of the debian folder between the version in testing and unstable is on contray really small. $ diff -puNr kicad-footprints-5.0.2/debian/ kicad-footprints-5.1.0/debian/ diff -puNr kicad-footprints-5.0.2/debian/changelog kicad-footprints-5.1.0/debian/changelog --- kicad-footprints-5.0.2/debian/changelog 2018-12-04 21:05:30.0 +0100 +++ kicad-footprints-5.1.0/debian/changelog 2019-03-11 19:58:05.0 +0100 @@ -1,3 +1,12 @@ +kicad-footprints (5.1.0-1) unstable; urgency=medium + + * [b602791] New upstream version 5.1.0 + * [22436a1] d/control: increase Standards-Version to 4.3.0 ++ No further changes needed. + * [d70afad] d/copyright: update years on contributors + + -- Carsten Schoenert Mon, 11 Mar 2019 19:58:05 +0100 + kicad-footprints (5.0.2-1) unstable; urgency=medium * [de61c7a] New upstream version 5.0.2 diff -puNr kicad-footprints-5.0.2/debian/control kicad-footprints-5.1.0/debian/control --- kicad-footprints-5.0.2/debian/control 2018-08-31 21:19:42.0 +0200 +++ kicad-footprints-5.1.0/debian/control 2019-03-11 19:55:15.0 +0100 @@ -10,7 +10,7 @@ Build-Depends: cmake, Vcs-Git: https://salsa.debian.org/electronics-team/KiCad/kicad-footprints.git Vcs-Browser: https://salsa.debian.org/electronics-team/KiCad/kicad-footprints -Standards-Version: 4.2.1 +Standards-Version: 4.3.0 Homepage: https://kicad.github.io/footprints Package: kicad-footprints diff -puNr kicad-footprints-5.0.2/debian/copyright kicad-footprints-5.1.0/debian/copyright --- kicad-footprints-5.0.2/debian/copyright 2018-08-31 21:20:48.0 +0200 +++ kicad-footprints-5.1.0/debian/copyright 2019-03-11 19:55:43.0 +0100 @@ -10,11 +10,11 @@ Comment: Like all KiCad libraries the li Material'." Files: * -Copyright: 2018 KiCad Community +Copyright: 2019 KiCad Community License: CC-BY-SA-4.0-with-exception Files: debian/* -Copyright: 2018, Carsten Schoenert +Copyright: 2019, Carsten Schoenert 2017-2018, Jean-Samuel Reynaud License: GPL-2+ unblock kicad-footprints/5.1.0-1 -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-4-amd64 (SMP w/6 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#926004: unblock: kicad/5.1.0+dfsg1-1
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package kicad
The KiCad binary packages based on upstream 5.0.2 (the current version
in testing from December 2018) are build with GTK2+ bindings which has
now some important downsides for the usability of KiCad. The upstream
developers are aware of this and have worked on pushing the KiCad
applications to work and use GTK3+ bindings. They released the new
version 5.1.0 about two weeks ago which addresses also a move over to
provide a Python3 library and dropping the old Python2 library instead.
Furthermore some additional possible UI stuff mainly provided by
external extension, that are based on wxWidgets and wxPython4, aren't
working with the version from testing due the GTK3+ binding in
the wxWidgets libaries.
And as usual a lot of small bug fixes did happen between the two
released versions.
The binary packages from src:kicad have no reverse dependencies nor
providing any public library (besides the Python3 library) so there are
no problems to be expected by the update at least I don't now any of
them.
In the past I've provided snapshots of the ongoing development including
release candidates of 5.1.0 in experimental and based on the feedback
from the KiCad forum and community no big issues nor packaging problem
got reported so I finally uploaded the 5.1.0 release to unstable. Also
here since the upload no new bug reports nor issues in forum got
reported, in contrary people start asking then KiCad 5.1.0 will be
available in testing and finally in the Buster release. :)
In all the reported issues against KiCad are really just a few,
currently we have 5 reports.
The resulting full debdiff between 5.0.2 from testing and 5.1.0 is
rather big due a natural lot of changes within the upstream source.
I uploaded a compressed version of the (full) debdiff to p.d.o.
https://people.debian.org/~tijuca/unblock/kicad-full.debdiff.tar.xz
The probably more interesting things are the differences within the debian
folder. I created a dedicated diff on this that is also available on
p.d.o as I'm not sure it the list will accept the plain file due size
limitations.
https://people.debian.org/~tijuca/unblock/kicad.debian-folder.debdiff
To summarize the Debian specific changes here:
* Adopt the build dependencies so the build is using wxWidgest GTK3+
based packages.
* Adjust a dedicated (binary) package dependency to use python-wxgtk3.0
which is linked against wxgtk3.0 with GTK3+ symbols, needed for the
internal KiCad scripting interface.
* Use Clang instead of GCC as compiler as the required GLM library >=
0.9.9.3 uses the C++ standard in it's "own" way which Clang is able to
work with, GCC7 is not.
* The Dutch documentation got dropped as not updated since at least on
release cycle.
* Upstream is providing a lot more of documentation in 5.1.0 which are
finally packaged in kicad-doc-{en,it,ru,zh}, no new binary packages.
* As usual a lot of updates to d/copyright due the changes happen to the
source.
* The build of the documentation of the final 5.1.0 needs a workaround as
the cmake system otherwise is puzzled and breaks a successful build.
(Since my package upload the root for this issue got identified and
will get fixed in future upstream updates.)
unblock kicad/5.1.0+dfsg1-1
-- System Information:
Debian Release: buster/sid
APT prefers testing
APT policy: (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.19.0-4-amd64 (SMP w/6 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8),
LANGUAGE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Bug#925990: unblock: libcoap2/4.2.0-1
uld be found! Install at least one of the package(s) that contains the development files for GnuTLS (>= $gnutls_version_required) or OpenSSL(>= $openssl_version_required) or disable the DTLS support using '--disable-dtls'." "$LINENO" 5 @@ -15031,7 +15031,7 @@ # report actual input values of CONFIG_FILES etc. instead of their # values after options handling. ac_log=" -This file was extended by libcoap $as_me 4.2.0rc4, which was +This file was extended by libcoap $as_me 4.2.0, which was generated by GNU Autoconf 2.69. Invocation command line was CONFIG_FILES= $CONFIG_FILES @@ -15098,7 +15098,7 @@ cat >>$CONFIG_STATUS <<_ACEOF || ac_write_fail=1 ac_cs_config="`$as_echo "$ac_configure_args" | sed 's/^ //; s/[\\""\`\$]/&/g'`" ac_cs_version="\\ -libcoap config.status 4.2.0rc4 +libcoap config.status 4.2.0 configured by $0, generated by GNU Autoconf 2.69, with options \\"\$ac_cs_config\\" diff -Nru libcoap2-4.2.0~rc4/configure.ac libcoap2-4.2.0/configure.ac --- libcoap2-4.2.0~rc4/configure.ac 2019-02-09 07:26:16.0 +0100 +++ libcoap2-4.2.0/configure.ac 2019-03-02 17:18:14.0 +0100 @@ -13,7 +13,7 @@ # define an appending release state if needed, for example for pre-releases # like 'alpha' or 'rc1', for a full release keep the value empty! -m4_define([libcoap_release_state], [rc4]) +m4_define([libcoap_release_state], []) # concatenate the full libcoap version string m4_define([libcoap_version], [m4_format([%s.%s.%s%s], libcoap_major_version, libcoap_minor_version, libcoap_micro_version, libcoap_release_state)]) @@ -428,7 +428,7 @@ # Note that tinyDTLS is used only when explicitly requested. # Giving out an error message if we haven't found at least one crypto library. -if test "x$have_gnutls" = "xno" -a "x$have_openssl" = "xno" -a "x$have_tinydtls" != "xno"; then +if test "x$have_gnutls" = "xno" -a "x$have_openssl" = "xno" -a "x$have_tinydtls" = "xno"; then AC_MSG_ERROR([==> Option '--enable-dtls' is set but one of the needed cryptography library GnuTLS nor OpenSSL nor tinyDTLS could be found! Install at least one of the package(s) that contains the development files for GnuTLS (>= $gnutls_version_required) or OpenSSL(>= $openssl_version_required) or disable the DTLS support using '--disable-dtls'.]) diff -Nru libcoap2-4.2.0~rc4/CONTRIBUTE libcoap2-4.2.0/CONTRIBUTE --- libcoap2-4.2.0~rc4/CONTRIBUTE 2018-08-05 03:41:02.0 +0200 +++ libcoap2-4.2.0/CONTRIBUTE 2019-03-02 17:18:14.0 +0100 @@ -120,7 +120,7 @@ the source file: --8< -/* -*- Mode: C; tab-width: 2; indent-tabs-mode: nil; c-basic-offset: 2 * -*- */ +/* -*- Mode: C; tab-width: 2; indent-tabs-mode: nil; c-basic-offset: 2 -*- */ --->8-- * Single lines within the source code should not be longer then 78 @@ -198,14 +198,13 @@ Also a good documentation on the usage of the libcoap and the example binaries is always improvable. So we appreciate any help on this. -* Man Pages +* Manual Pages The source is providing some example binaries which originally just should show how the libcoap can be used. Right now these binaries are fully usable and quite more than simple examples on a system. There are man pages for these binaries available, if you found there is a improvement needed please do so and write to the mailing list explained in section 2. -Maybe you can write up some good HowTo's on the usage for these binaries. A man -page for the library itself would be also a improvement. +Maybe you can write up some good HowTo's on the usage for these binaries. * HowTo's The libcoap library has now a lot of functions you can use. @@ -213,7 +212,7 @@ any external project. This means there is no HowTo or CheatSheet for a programming person available. You want to write up something? -* missed Functionality +* Missing functionality There are some features that are still missing inside the libcoap. For example some DTLS implementations and proxy functionality. diff -Nru libcoap2-4.2.0~rc4/debian/changelog libcoap2-4.2.0/debian/changelog --- libcoap2-4.2.0~rc4/debian/changelog 2019-02-09 07:43:56.0 +0100 +++ libcoap2-4.2.0/debian/changelog 2019-03-02 17:35:18.0 +0100 @@ -1,3 +1,13 @@ +libcoap2 (4.2.0-1) unstable; urgency=medium + + * [b0fedea] New upstream version 4.2.0 + * [da9142e] rebuild patch queue from patch-queue branch +removed patches (applied upstream): +spelling-fix-Addtional-Additional.patch +spelling-fix-funtion-function.patch + + -- Carsten Schoenert Sat, 02 Mar 2019 17:35:18 +0100 + libcoap2 (4.2.0~rc4-1) unstable; urgency=medium * [f43d44d] New upstream version 4.2.0~rc4 diff -Nru libcoap2-4.2.0~
Bug#925989: unblock: kopano-webapp/3.5.3+dfsg1-1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package kopano-webapp kopano-webapp is a web application for the kopano-server suite written in PHP with quite a lot of JS files. The update from 3.5.2 to 3.5.3 fixes as usual some small issues regarding the UI usability in various places. kopano-webapp is depening on a kopano-server and hos no reverse dependencies. It would be nice to have the recent upstream version of k-w within the buster release so please unlock kopano-webapp. The debdiff is quite long as there are many small changes within the source, mainly within the JS and the PO files. The packaging wasn't needed to change. unblock kopano-webapp/3.5.3+dfsg1-1 -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-4-amd64 (SMP w/6 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled kopano-webapp.debdiff.tar.xz Description: application/xz
Bug#925988: unblock: sogo-connector/60.0.2-1
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package sogo-connector
sogo-connector is a extension for Thunderbird which has no reverse
dependencies.
I'd like to see the sogo-connector package gets updated in
testing/buster. Upstream has fixed some minor issues regarding the
invitations dialog which could be always empty. The packaging itself got
no changes.
I've attached the debdiff output from the version currently in testing
against the version in unstable. Thanks for considering.
unblock sogo-connector/60.0.2-1
-- System Information:
Debian Release: buster/sid
APT prefers testing
APT policy: (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.19.0-4-amd64 (SMP w/6 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8),
LANGUAGE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru
sogo-connector-60.0.1/chrome/content/sogo-connector/calendar/calendar-invitations-list.xml
sogo-connector-60.0.2/chrome/content/sogo-connector/calendar/calendar-invitations-list.xml
---
sogo-connector-60.0.1/chrome/content/sogo-connector/calendar/calendar-invitations-list.xml
2019-02-20 14:31:59.0 +0100
+++
sogo-connector-60.0.2/chrome/content/sogo-connector/calendar/calendar-invitations-list.xml
2019-02-26 17:17:20.0 +0100
@@ -1,42 +1,7 @@
-
+
%dtd1;
@@ -54,10 +19,10 @@
@@ -80,11 +45,15 @@
null
null
+
+
+return {
+alldayEvent: "",
+recurrentEvent:
"",
+location: "",
+organizer: "",
+attendee: "",
+none: ""
+};
+
+
+
-
- var alldayEventText = "";
- var recurrentEventText =
"";
- var locationText = "";
- var organizerText = "";
- var attendeeText = "";
- var noneText = "";
-
-
+this.setAttribute("itemId", aItem.hashId);
+]]>
@@ -234,31 +207,32 @@
diff -Nru sogo-connector-60.0.1/debian/changelog
sogo-connector-60.0.2/debian/changelog
--- sogo-connector-60.0.1/debian/changelog 2019-02-21 19:27:47.0
+0100
+++ sogo-connector-60.0.2/debian/changelog 2019-03-07 19:40:57.0
+0100
@@ -1,3 +1,9 @@
+sogo-connector (60.0.2-1) unstable; urgency=medium
+
+ * [747546e] New upstream version 60.0.2
+
+ -- Carsten Schoenert Thu, 07 Mar 2019 19:40:57
+0100
+
sogo-connector (60.0.1-1) unstable; urgency=medium
* [37adbb6] New upstream version 60.0.1
diff -Nru sogo-connector-60.0.1/install.rdf sogo-connector-60.0.2/install.rdf
--- sogo-connector-60.0.1/install.rdf 2019-02-20 14:31:59.0 +0100
+++ sogo-connector-60.0.2/install.rdf 2019-02-26 17:17:20.0 +0100
@@ -5,7 +5,7 @@
Bug#918337: Re: stretch-pu: package xul-ext-sogo-connector/31.0.3-3
Hello Adam, Am 09.02.19 um 15:19 schrieb Adam D. Barratt: > [NB: this request appears never to have made it to debian-release] huh, I can remember I haven't get a feedback from the BTS but you are right, I can't find the forwarded mail to debian-release in January. Might related to the big diff I've attached. Thanks tor taking care nevertheless! > On Sat, 2019-01-05 at 10:49 +0100, Carsten Schoenert wrote: >> due the changed add-on interface in Thunderbird since version 60.x >> the current version 31.0.3-3 of the package xul-ext-sogo-connecter >> isn't usable any more in stretch. So I'd like to update the version >> of this package in stretch to version 60.0.0+gite2547a3-1 which is >> available in testing/unstable since months. >> >> The version for stretch would then be 60.0.0+gite2547a3-1~deb9u1. > > Please go ahead, bearing in mind that the window for getting fixes into > the 9.8 point release closes during this weekend. thanks for getting a go on on this package too! Like for compactheader, uploaded and got the also meanwhile the message from DAK the upload was accepted into stable-new. -- Regards Carsten Schoenert
Bug#918601: stretch-pu: package compactheader/2.1.0-3
Hello Adam, Am 09.02.19 um 15:22 schrieb Adam D. Barratt: > Please go ahead, bearing in mind that the window for the 9.8 point > release closes this weekend. thanks! Uploaded some minutes ago and already accepted. Excellent. -- Regards Carsten Schoenert
Bug#872998: transition: php7.2
Hi, On Thu, Feb 01, 2018 at 09:47:21AM +0100, Emilio Pozuelo Monfort wrote: > On 28/01/18 14:19, Ondřej Surý wrote: > > Yes, please, go ahead, and I will fix any eventual build failures as it > > goes. > > Done, see the failures on > https://release.debian.org/transitions/html/php7.2.html don't care much about kopanocore, it's no problem to build recent kopanocore versions against PHP7.2 and we just need to find some time to prepare a new upstrem version of kopanocore for unstable now it has left NEW. Should be done within this week. Regards Carsten
Re: transistion of thunderbird 1:52.5.0-1 into testing
Hello Adam, Am 19.12.2017 um 13:24 schrieb Adam D. Barratt: > On 2017-12-19 11:24, Carsten Schoenert wrote: >> Hi, >> >> some days ago jrtc27 helped me on the IRC to figure that a upload of >> debian-edu to unstable has prevented the transition of thunderbird >> packages to testing. The reason was probably that >> education-lang-zh-tw-desktop was depending on now non existing package >> iceowl-l10n-zh-tw in testing [1]. >> >> Now the fixed version of debian-edu has migrated to testing but >> thunderbird is still not migrating. > > Indeed. You also removed other packages which have reverse-dependencies. > At the very least, there are 6 binary packages in testing with a > dependency on "icedove" with no alternative dependency on thunderbird or > firefox. ohh, I just have done a look on the build-depends on other packages. Mea culpa, I'm gonna need to sort this out. Thanks! -- Regards Carsten Schoenert
transistion of thunderbird 1:52.5.0-1 into testing
Hi, some days ago jrtc27 helped me on the IRC to figure that a upload of debian-edu to unstable has prevented the transition of thunderbird packages to testing. The reason was probably that education-lang-zh-tw-desktop was depending on now non existing package iceowl-l10n-zh-tw in testing [1]. Now the fixed version of debian-edu has migrated to testing but thunderbird is still not migrating. https://release.debian.org/britney/excuses.yaml isn't showing any excuses (at least to me) why thunderbird isn't moving to testing. As all other releases have now already the latest Thunderbird version and 52.5.0 was also fixing some security issue as usual it would be good if testing would have the same version. Do I miss something why Thunderbird 52.5.0-1 isn't migrating? [1] https://bugs.debian.org/884193 -- Regards Carsten Schoenert
Bug#860404: unblock: kicad/4.0.6+dfsg1-1 (pre-approval)
Hello Niels, On Fri, Apr 21, 2017 at 11:20:00AM +, Niels Thykier wrote: > Ok. This, along with the fact that files are renamed and change meaning > (as noted in the README), worries me. My current gut feeling is to say > no to the upstream release for stretch. > > That said, I am happy to consider cherry-picks / targeted fixes for > issues (e.g. the d/rules changes or upstream bug fixes). o.k. then I can prepare the fixups for the existing release 4.0.5 of KiCad and create a new Debian version also for that. I already started to work on this, unfortunately some minor issue is coming out on that. The current source tarballs are named 4.0.5+dfsg1*. But there is one footprint library inside missing due a issue in the helper script that is downloading all the needed sources. The issue is a not correct call and usage of the GitHub API so not all footprint libraries are downloaded. In short, the tagged 4.0.5 footprint files of Connectors_Terminal_Blocks.pretty [1] are still missing in the current source files and I'd need to prepare a new source 4.0.5+dfsg2*. Otherwise the fix of the current situation is only a partial fix. I really recommend to add this missing library. So the current fix for the existing version 4.0.5+dfsg1-4 I'd like to do would be: 1. Adding the missing footprint library (resulting in 4.0.5+dfsg2). 2. Adding the symlinking of the renamed footprint folders. 3. Adding a README.Debian for explaining the symlinking. [1] https://github.com/KiCad/Connectors_Terminal_Blocks.pretty/tree/4.0.5 Regards Carsten
Bug#860404: unblock: kicad/4.0.6+dfsg1-1 (pre-approval)
Hello Niels,
On Sun, Apr 16, 2017 at 12:36:00PM +, Niels Thykier wrote:
> It is probably a lot easier for us to judge this given a source debdiff
> of the actual changes (or two, one for the symlinks and one for the
> upstream release). Could you perhaps provide such debdiff?
of course I can. The upstream changes are a bit to big adding them here and
they are not that useful I think. So I drop them here.
Upstream has added a new documentation for Indonesian, I added that as a new
package but disabled it for now, it's not that big and needs to go through NEW
later. Just added to not forget it later.
My current WIP specific to the debian/ folder looks like this:
t a/debian/changelog b/debian/changelog
index 76a10e38..5063ad23 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,11 +1,28 @@
+kicad (4.0.6+dfsg1-1~1.gbpa34244) UNRELEASED; urgency=medium
+
+ ** SNAPSHOT build @a342449ec6428e76587cc655786b8cf45501e14c **
+
+ * [2186d4d] debian/rules: make dh_fixperms arch-depended (again)
+ * [bc1607f] idf2vrml.1: fix syntax of the hyphen for option '-k'
+ * [6fce2c4] update footprint libraries for component tarball
+ * [e732ddb] New upstream version 4.0.6+dfsg1
+ * [aa82369] rebuild patch queue from patch-queue branch
+ * [5ef5ad6] debian/control: update B-D after upstream changes
+ * [668aca6] adding new -doc package with Indonesian i18n
+ * [b793a0f] kicad-common.README.Debian: adding Debian specific remarks
+ * [5f85335] debian/rules: set permissions for *.kicad_mod files
+ * [a342449] kicad-common: symlink renamed footprint libraries
+
+ -- Carsten Schoenert <c.schoen...@t-online.de> Sat, 15 Apr 2017 19:02:10
+0200
+
kicad (4.0.5+dfsg1-4) unstable; urgency=medium
[ Carsten Schoenert ]
* [375ce2f] Revert "debian/control: decrease Architectures for arch packages"
+ removing the arch specific decrease of the build architecture, it's
really not useful here (Thx Emilio & Aurelien)
- * [b2c400d] kicad-common.lintian-overrides: ingoring Lintian
-+ kicad-common is now arch dependend, silence lintian here that is saying
+ * [b2c400d] kicad-common.lintian-overrides: ignoring Lintian
++ kicad-common is now arch dependent, silence lintian here that is saying
kicad-common has only content that is indep but we relay on the python
package
diff --git a/debian/control b/debian/control
index 5d43e733..72f4f8cf 100644
--- a/debian/control
+++ b/debian/control
@@ -32,10 +32,11 @@ Build-Depends:
libboost-thread-dev,
libbz2-dev,
libcairo2-dev,
- libcurl4-gnutls-dev,
+ libcurl4-openssl-dev,
libglew-dev,
liblocale-gettext-perl,
libpython-stdlib,
+ libssl-dev,
libterm-readkey-perl,
libtext-wrapi18n-perl,
libunicode-linebreak-perl,
@@ -59,6 +60,7 @@ Build-Depends:
texlive-lang-german,
texlive-lang-italian,
texlive-lang-japanese,
+ texlive-lang-other,
texlive-lang-polish,
texlive-lang-spanish,
texlive-xetex,
@@ -206,6 +208,18 @@ Description: Kicad help files (French)
* Pcbnew - The printed circuit board software tool
* PlEditor - The layout editor for custom title block
+#Package: kicad-doc-id
+#Section: doc
+#Architecture: all
+#Multi-Arch: foreign
+#Depends:
+# ${misc:Depends},
+#Description: Kicad help files (Indonesian)
+# This package provides various documentation files for KiCad in Indonesian,
like
+# the EPUB and the PDF files and also the OnLine HTML documentation for:
+# .
+# * GSIK - Getting Started in KiCad
+
Package: kicad-doc-it
Section: doc
Architecture: all
diff --git a/debian/create_kicad_upstream_tarballs.sh
b/debian/create_kicad_upstream_tarballs.sh
index b72da2ef..2f4fbf31 100755
--- a/debian/create_kicad_upstream_tarballs.sh
+++ b/debian/create_kicad_upstream_tarballs.sh
@@ -356,61 +356,80 @@ echo
# collecting and preparing data for the KiCad libraries tarball #
#
-# The various component, footprint and 3D-model libraries are available one
+# The various component-, footprint- and 3D-model libraries are available on
# GitHub in various repositories. Uncomment the following two lines to get
-# a dynamically created list of repositories. Otherwise it's currently better
-# to use the static list as some repositories currently empty like:
+# a dynamically created list of repositories. We can keep the upstream provided
+# libararies even if there are some repositories currently empty like:
# Connectors_Amphenol.pretty
+# Enclosures.pretty
+# Housings_LCC.pretty
+# Housings_PGA.pretty
+# If we don't want to include empty repositories we need to also adjust the
+# default fp-lib-table in
libraries/kicad-library/template/fp-lib-table.for-pretty !
-#PRETTY_REPOS=$(curl https://api.github.com/orgs/KiCad/repos?per_page=2000 2>
/dev/null | sed -r 's:.+ "full_name".*"KiCad/(.+\.pretty)",:\1:p;d')
-#PRETTY_REPOS=$(echo $PRETTY_REPOS | tr " " "\n" | sort)
+#PRETTY_R
Bug#860404: unblock: kicad/4.0.6+dfsg1-1 (pre-approval)
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Dear Release Team, the current version of KiCad in testing is 4.0.5+dfsg1-4. KiCad is a Electronic Design Automation tool were people can create electronic schematics and also can create PCBs later from that. It was shown by report #859409 that the recent version in testing has some none working footprint settings. This makes it hard for not well experienced user to work around that. The reason for this misbehavior is due some restructured footprint libraries done by upstream in preparation for the release of 4.0.5. Upstream has mostly renamed some footprints and partially moved some parts of footprints into other libraries. Upstream has no rule like not renaming any footprints within one release cycle. We can "fix" this mostly by shipping the new footprints and do symlinking the old names to the new footprints. This is what I have done in #859409 and the reporter of #859409 has tested some new created modified packages. After the freeze in January upstream also has done a new fixup release, I prepared and melted this new release also into the packages provided in #859409. The feedback from the reporter and my local testing of this packages are positive and functional. So I'd like to ask if a upload of kicad package 4.0.6+dfsg1-1 to unstable is o.k. and if a unblock request after the 10 days is likely to be accepted? Otherwise we can provide the current version 4.0.6 later by backports, but I would really like to see a not broken version of KiCad in Stretch. There are no other packages that depends on any kicad*. Please note that I'm not the maintainer of KiCad, this is Georges Khaznadar. Georges gave me upload rights for kicad some months ago and I've done most of the packaging work of the last two upstream releases. Unfortunately Georges is busy and small on time in the past due his day job. I haven't seen this issue from the report while preparation of 4.0.5 for unstable as I wasn't aware of all the specific of the footprint handling at this time. Regards Carsten -- System Information: Debian Release: 9.0 APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: armhf Kernel: Linux 4.9.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
Bug#859975: unblock: icedove/1:45.8.0-3
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package icedove
Dear release team,
some small needed changes were done within the version 1:45.8.0-3 for
the icedove packages. The changes in detail are:
* A fixup within the starting wrapper script was added so users which
want to use symlinks for the existing old ~/.icedove profile folder
can use this together with the new created symlink ~/.thunderbird
pointing to ~/.icedove. Otherwise Thunderbird isn't starting.
* The starting wrapper has got a fix to detect the thunderbird-dbg
package correctly.
* A extra cherry picked patch from upstream was added to prevent
nullpointer segfaults.
* The apparmor profile was needed to be expanded so both existing profile
folders ~/.icedove and ~/.thunderbird are usable.
The following changes are visible by the debdiff append here.
diff -Nru icedove-45.8.0/debian/apparmor/usr.bin.thunderbird
icedove-45.8.0/debian/apparmor/usr.bin.thunderbird
--- icedove-45.8.0/debian/apparmor/usr.bin.thunderbird 2017-03-15
01:37:48.0 +0100
+++ icedove-45.8.0/debian/apparmor/usr.bin.thunderbird 2017-03-30
01:28:32.0 +0200
@@ -144,12 +144,12 @@
/**/ r,
# per-user thunderbird configuration
- owner @{HOME}/.thunderbird/ rw,
- owner @{HOME}/.thunderbird/** rw,
- owner @{HOME}/.thunderbird/**/storage.sdb k,
- owner @{HOME}/.thunderbird/**/*.{db,parentlock,sqlite}* k,
- owner @{HOME}/.thunderbird/plugins/** rm,
- owner @{HOME}/.thunderbird/**/plugins/** rm,
+ owner @{HOME}/.{icedove,thunderbird}/ rw,
+ owner @{HOME}/.{icedove,thunderbird}/** rw,
+ owner @{HOME}/.{icedove,thunderbird}/**/storage.sdb k,
+ owner @{HOME}/.{icedove,thunderbird}/**/*.{db,parentlock,sqlite}* k,
+ owner @{HOME}/.{icedove,thunderbird}/plugins/** rm,
+ owner @{HOME}/.{icedove,thunderbird}/**/plugins/** rm,
owner @{HOME}/.cache/thunderbird/ rw,
owner @{HOME}/.cache/thunderbird/** rw,
@@ -160,7 +160,7 @@
# Extensions
# /usr/share/.../extensions/... is already covered by '/usr/** r', above.
# Allow 'x' for downloaded extensions, but inherit policy for safety
- owner @{HOME}/.thunderbird/**/extensions/** mixrw,
+ owner @{HOME}/.{icedove,thunderbird}/**/extensions/** mixrw,
owner @{HOME}/.mozilla/extensions/**mixr,
/usr/share/xul-ext/**/*.sqlite rk,
/usr/lib/xul-ext/**/*.sqliterk,
@@ -237,10 +237,10 @@
/usr/lib/gnupg2/gpg2keys_hkp ix,
# silence noise from enigmail 1.9+
-deny owner @{HOME}/.thunderbird/*/.parentlock w,
-deny owner @{HOME}/.thunderbird/*/panacea.dat w,
-deny owner @{HOME}/.thunderbird/*/*.mab w,
-deny owner @{HOME}/.thunderbird/**/*.msf w,
+deny owner @{HOME}/.{icedove,thunderbird}/*/.parentlock w,
+deny owner @{HOME}/.{icedove,thunderbird}/*/panacea.dat w,
+deny owner @{HOME}/.{icedove,thunderbird}/*/*.mab w,
+deny owner @{HOME}/.{icedove,thunderbird}/**/*.msf w,
deny owner @{HOME}/.cache/thunderbird/**/_CACHE_* w,
/usr/share/xul-ext/enigmail/chrome/enigmail.jar r,
diff -Nru icedove-45.8.0/debian/changelog icedove-45.8.0/debian/changelog
--- icedove-45.8.0/debian/changelog 2017-03-15 01:37:48.0 +0100
+++ icedove-45.8.0/debian/changelog 2017-03-30 01:28:32.0 +0200
@@ -1,3 +1,17 @@
+icedove (1:45.8.0-3) unstable; urgency=medium
+
+ [ Carsten Schoenert ]
+ * [d923505] AppArmor: be more flexible on profile folders
+(Closes: #858735, #858737)
+ * [1e04099] tb-wrapper: use readlink also on ${ID_PROFILE_FOLDER}
+(Closes: #858771)
+ * [9f6b771] tb-wrapper: correct check for -dbg package (Closes: #858804)
+ * [8b5271a] rebuild patch queue from patch-queue branch
+added patches:
+- fixes/Bug-1273020-Add-missing-null-checks-in-ApplicationAccessi.patch
+
+ -- Christoph Goehre <ch...@sigxcpu.org> Wed, 29 Mar 2017 19:28:32 -0400
+
icedove (1:45.8.0-2) unstable; urgency=medium
[ Carsten Schoenert ]
diff -Nru
icedove-45.8.0/debian/patches/fixes/Bug-1273020-Add-missing-null-checks-in-ApplicationAccessi.patch
icedove-45.8.0/debian/patches/fixes/Bug-1273020-Add-missing-null-checks-in-ApplicationAccessi.patch
---
icedove-45.8.0/debian/patches/fixes/Bug-1273020-Add-missing-null-checks-in-ApplicationAccessi.patch
1970-01-01 01:00:00.0 +0100
+++
icedove-45.8.0/debian/patches/fixes/Bug-1273020-Add-missing-null-checks-in-ApplicationAccessi.patch
2017-03-30 01:28:32.0 +0200
@@ -0,0 +1,79 @@
+From: Carsten Schoenert <c.schoen...@t-online.de>
+Date: Tue, 28 Mar 2017 18:48:46 +0200
+Subject: Bug 1273020 - Add missing null checks in ApplicationAccessible.
+ r=surkov.
+
+Origin: https://hg.mozilla.org/mozilla-central/rev/8bfdf5dfcf6b
+Origin: https://hg.mozilla.org/mozilla-central/rev/798f02387d36
+Bug-Debian: https://bugs.debian.org/852149
+Bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1273020
+Applied-Upstream: Firefox 49.0
+---
+ .../access
Bug#851989: release.debian.org: de-branding Icedove, Thunderbird packages in Stretch?
Dear Release Team, On Fri, Mar 10, 2017 at 10:19:23PM +0100, Carsten Schoenert wrote: ... > BTW: The last emails from Julien in this bug report wasn't reaching me, > so it is not intended to don't answering question from the RT, I simply > hasn't seen any activity here. > > If no new big issues will arise we hopefully can write a unblock request > in about a few days ... it's seems you guys are working really quick and wanted to prevent me to write a extra unblock request for Thunderbird 1:45.8.0-2. :-) Thanks for already allowing the recent Thunderbird version to enter testing without extra action on our side! What should happen to this report? Should it be kept open? I guess this isn't really needed and the report could be closed. Regards Carsten
Bug#858063: unblock: libcoap/4.1.2-1
O" 5; }
-fi
-
-ac_ext=c
-ac_cpp='$CPP $CPPFLAGS'
-ac_compile='$CC -c $CFLAGS $CPPFLAGS conftest.$ac_ext >&5'
-ac_link='$CC -o conftest$ac_exeext $CFLAGS $CPPFLAGS $LDFLAGS conftest.$ac_ext
$LIBS >&5'
-ac_compiler_gnu=$ac_cv_c_compiler_gnu
-
-
-{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for ANSI C header files" >&5
-$as_echo_n "checking for ANSI C header files... " >&6; }
-if ${ac_cv_header_stdc+:} false; then :
- $as_echo_n "(cached) " >&6
-else
- cat confdefs.h - <<_ACEOF >conftest.$ac_ext
-/* end confdefs.h. */
-#include
-#include
-#include
-#include
-
-int
-main ()
-{
-
- ;
- return 0;
-}
-_ACEOF
-if ac_fn_c_try_compile "$LINENO"; then :
- ac_cv_header_stdc=yes
-else
- ac_cv_header_stdc=no
-fi
-rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext
-
-if test $ac_cv_header_stdc = yes; then
- # SunOS 4.x string.h does not declare mem*, contrary to ANSI.
- cat confdefs.h - <<_ACEOF >conftest.$ac_ext
-/* end confdefs.h. */
-#include
-
-_ACEOF
-if (eval "$ac_cpp conftest.$ac_ext") 2>&5 |
- $EGREP "memchr" >/dev/null 2>&1; then :
-
-else
- ac_cv_header_stdc=no
-fi
-rm -f conftest*
-
-fi
-
-if test $ac_cv_header_stdc = yes; then
- # ISC 2.0.2 stdlib.h does not declare free, contrary to ANSI.
- cat confdefs.h - <<_ACEOF >conftest.$ac_ext
-/* end confdefs.h. */
-#include
-
-_ACEOF
-if (eval "$ac_cpp conftest.$ac_ext") 2>&5 |
- $EGREP "free" >/dev/null 2>&1; then :
-
-else
- ac_cv_header_stdc=no
-fi
-rm -f conftest*
-
-fi
-
-if test $ac_cv_header_stdc = yes; then
- # /bin/cc in Irix-4.0.5 gets non-ANSI ctype macros unless using -ansi.
- if test "$cross_compiling" = yes; then :
- :
-else
- cat confdefs.h - <<_ACEOF >conftest.$ac_ext
-/* end confdefs.h. */
-#include
-#include
-#if ((' ' & 0x0FF) == 0x020)
-# define ISLOWER(c) ('a' <= (c) && (c) <= 'z')
-# define TOUPPER(c) (ISLOWER(c) ? 'A' + ((c) - 'a') : (c))
-#else
-# define ISLOWER(c) \
- (('a' <= (c) && (c) <= 'i') \
-|| ('j' <= (c) && (c) <= 'r') \
- || ('s' <= (c) && (c) <= 'z'))
-# define TOUPPER(c) (ISLOWER(c) ? ((c) | 0x40) : (c))
-#endif
-
-#define XOR(e, f) (((e) && !(f)) || (!(e) && (f)))
-int
-main ()
-{
- int i;
- for (i = 0; i < 256; i++)
-if (XOR (islower (i), ISLOWER (i))
- || toupper (i) != TOUPPER (i))
- return 2;
- return 0;
-}
-_ACEOF
-if ac_fn_c_try_run "$LINENO"; then :
-
-else
- ac_cv_header_stdc=no
-fi
-rm -f core *.core core.conftest.* gmon.out bb.out conftest$ac_exeext \
- conftest.$ac_objext conftest.beam conftest.$ac_ext
-fi
-
-fi
-fi
-{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_cv_header_stdc" >&5
-$as_echo "$ac_cv_header_stdc" >&6; }
-if test $ac_cv_header_stdc = yes; then
-
-$as_echo "#define STDC_HEADERS 1" >>confdefs.h
-
-fi
-
-# On IRIX 5.3, sys/types and inttypes.h are conflicting.
-for ac_header in sys/types.h sys/stat.h stdlib.h string.h memory.h strings.h \
- inttypes.h stdint.h unistd.h
-do :
- as_ac_Header=`$as_echo "ac_cv_header_$ac_header" | $as_tr_sh`
-ac_fn_c_check_header_compile "$LINENO" "$ac_header" "$as_ac_Header"
"$ac_includes_default
-"
-if eval test \"x\$"$as_ac_Header"\" = x"yes"; then :
- cat >>confdefs.h <<_ACEOF
-#define `$as_echo "HAVE_$ac_header" | $as_tr_cpp` 1
-_ACEOF
-
-fi
-
-done
-
-
for ac_header in dlfcn.h
do :
ac_fn_c_check_header_compile "$LINENO" "dlfcn.h" "ac_cv_header_dlfcn_h"
"$ac_includes_default
@@ -13498,6 +13723,12 @@
ADDITIONAL_CFLAGS="-D_GNU_SOURCE -DWITH_POSIX"
;;
+*kfreebsd*)
+{ $as_echo "$as_me:${as_lineno-$LINENO}: result: kFreeBSD" >&5
+$as_echo "kFreeBSD" >&6; }
+ADDITIONAL_CFLAGS="-D_GNU_SOURCE -DWITH_POSIX"
+;;
+
*)
{ $as_echo "$as_me:${as_lineno-$LINENO}: WARNING: ==> Currently
unsupported operating system '${host}' !" >&5
$as_echo "$as_me: WARNING: ==> Currently unsupported operating system
'${host}' !" >&2;}
@@ -13654,6 +13885,7 @@
as_fn_error $? "conditional \"am__fastdepCC\" was never defined.
Usually this means the macro was only invoked conditionally." "$LINENO" 5
fi
+
if test -z "${BUILD_DOCUMENTATION_TRUE}" && test -z
"${BUILD_DOCUMENTATION_FALSE}"; then
as_fn_error $? "conditional \"BUILD_DOCUMENTATION\" was never defined.
Usually this means the macro was only invoked conditionally." "$LINENO" 5
diff -Nru libcoap-4.1.2~rc+gi
Bug#858060: unblock: sogo-connector/31.0.3-3
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock/remove autoremoval for package sogo-connector
Hello release team,
the package sogo-connector is a extension for Icedove and with the
ongoing transition of Icedove back to Thunderbird also extension for the
Thunderbird package.
The build of the xul-ext-sogo-connector binary package is now depending
on thunderbird-dev in unstable as the needed files for building
sogo-connector are now placed in /usr/lib/thunderbird-devel/ due
icedove-dev is now a transitional package.
The version of sogo-connector in testing is currently 31.0.3-1, unstable
got 31.0.3-1.
Version 31.0.3-2 was expanding the description of the package, also the
MPL-1.1 license was moved into the copyright file.
The Vcs fields were adopted to the changed URL on anonscm.d.o and the
Build-Depends got expanded to "| thunderbird-dev". Unfortunately I
forgotten also to adjust the variables within the Makefile then, so the
package run into a FTBFS (#856457 [1]) which resulted in a fixed upload done
by 31.0.3-3.
Both versions -1 and -3 are technically the same, excpet the fixed
Build-Depends and the visible expanded description.
For Thunderbird we hope to also file a unblock request soon which depends on
some other small issues. So for the sogo-connector there are no strong needs to
go into testing right now.
But it would nothing break otherwise if -3 would be allowed to enter testing.
If you don't agree to unblock sogo-connector please remove the
autoremove marker then.
The srcdiff is rather big due the integration of the MPL-1.1 license
into the copyright file. The resulting changes without the license
adjustemnts are small.
[1] https://bugs.debian.org/856457
diff -Nru sogo-connector-31.0.3/debian/changelog
sogo-connector-31.0.3/debian/changelog
--- sogo-connector-31.0.3/debian/changelog 2016-07-02 20:13:12.0
+0200
+++ sogo-connector-31.0.3/debian/changelog 2017-03-04 09:51:45.0
+0100
@@ -1,3 +1,21 @@
+sogo-connector (31.0.3-3) unstable; urgency=medium
+
+ * [7f95a11] rebuild patch queue from patch-queue branch (Closes: #856457)
+ * [9328a7e] debian/control: reverse the resolving order for -dev package
+
+ -- Carsten Schoenert <c.schoen...@t-online.de> Sat, 04 Mar 2017 09:51:45
+0100
+
+sogo-connector (31.0.3-2) unstable; urgency=medium
+
+ * [85e9938] debian/control: wrap-and-sort all entries
+ * [82988f2] Build-Depends: append possible thunderbird-dev package
+ * [6ac973e] debhelper: bump to version 10
+ * [1f59a4a] debian/control: correcting, moving Vcs fields to https
+ * [c4ff179] debian/copyright: update same sections, adding MPL-1.1
+ * [ba1f4ce] debian/control: extend the description of sogo-connector
+
+ -- Carsten Schoenert <c.schoen...@t-online.de> Sun, 29 Jan 2017 14:40:27
+0100
+
sogo-connector (31.0.3-1) unstable; urgency=medium
* debian/control: increase B-D for mozilla-devscripts
diff -Nru sogo-connector-31.0.3/debian/compat
sogo-connector-31.0.3/debian/compat
--- sogo-connector-31.0.3/debian/compat 2016-07-02 20:13:12.0 +0200
+++ sogo-connector-31.0.3/debian/compat 2017-01-28 21:20:27.0 +0100
@@ -1 +1 @@
-8
+10
diff -Nru sogo-connector-31.0.3/debian/control
sogo-connector-31.0.3/debian/control
--- sogo-connector-31.0.3/debian/control2016-07-02 20:13:12.0
+0200
+++ sogo-connector-31.0.3/debian/control2017-03-04 09:51:27.0
+0100
@@ -2,28 +2,36 @@
Section: web
Priority: optional
Maintainer: Carsten Schoenert <c.schoen...@t-online.de>
-Uploaders: Christoph Goehre <ch...@sigxcpu.org>
+Uploaders:
+ Christoph Goehre <ch...@sigxcpu.org>,
Standards-Version: 3.9.8
-Build-Depends: debhelper (>= 9),
- icedove-dev (>= 24~),
- make (>=3.81~),
- mozilla-devscripts (>= 0.45.1~),
- python-ply
+Build-Depends:
+ debhelper (>= 10.2.2~),
+ thunderbird-dev | icedove-dev (>= 24~),
+ make (>=3.81~),
+ mozilla-devscripts (>= 0.45.1~),
+ python-ply,
Homepage: http://www.sogo.nu/
-Vcs-Git: git://anonscm.debian.org/pkg-mozext/sogo-connector.git
-Vcs-Browser:
http://anonscm.debian.org/gitweb/?p=pkg-mozext/sogo-connector.git;a=summary
+Vcs-Git: https://anonscm.debian.org/git/pkg-mozext/sogo-connector.git
+Vcs-Browser: https://anonscm.debian.org/git/pkg-mozext/sogo-connector.git
Package: xul-ext-sogo-connector
Architecture: all
-Depends: ${misc:Depends}, ${xpi:Depends},
+Depends:
iceowl-extension (>= 31~) | lightning,
-Recommends: ${xpi:Recommends}
-Breaks: ${xpi:Breaks}
-Provides: ${xpi:Provides}
-Enhances: ${xpi:Enhances}
-Description: transforms Icedove into a full DAV client for groupware servers
- The SOGo Connector makes Icedove to a full DAV client for any groupware
- server like SOGo, OpenGroupware, Citadel or Owncloud.
+ ${misc:Depends},
+ ${xpi:Depends},
+Recommends:
+ ${xpi:Recommends},
+Breaks:
+ ${xpi:Breaks},
+Provides:
+ ${xpi:Provid
Bug#851989: release.debian.org: de-branding Icedove, Thunderbird packages in Stretch?
Hello Emilio, On Fri, Mar 10, 2017 at 05:18:32PM +0100, Emilio Pozuelo Monfort wrote: > BTW why is the source package still named icedove instead of thunderbird? that's related to apt-listchanges. If we change the source name now apt-listchanges can't do his job for getting automatic information to the system administrators as apt-listchanges uses also the source package name to display NEWS entries. The name change for the source package is planned of course, but first we would need to get the change of the binary packages into testing (and stable-security and also wheezy-lts). > And thanks for the prompt fix. This was natural a needed thing to not break things longer than needed, and, Mozilla has released a new version. So the upload was not simply a re-upload with some fixes. We also got arm64 fixed by this. BTW: The last emails from Julien in this bug report wasn't reaching me, so it is not intended to don't answering question from the RT, I simply hasn't seen any activity here. If no new big issues will arise we hopefully can write a unblock request in about a few days ... Regards Carsten
Bug#851989: release.debian.org: de-branding Icedove, Thunderbird packages in Stretch?
On Fri, Jan 27, 2017 at 01:01:18AM +0100, Emilio Pozuelo Monfort wrote: ... > emilio@tatooine:~$ build-rdeps icedove-dev > WARNING: dose-extra >= 4.0 is not installed. Falling back to old unreliable > behaviour. > Reverse Build-depends in main: > -- > > calendar-exchange-provider > sogo-connector > > Found a total of 2 reverse build-depend(s) for icedove-dev. I'm the maintainer of the latter package, I will prepare a upload for this package on this weekend (it's planed for a longer time at all), sogo-connector is only using some *.idl files from icedove-dev, that are more or less just JS files. But to get of the need for the transitional packages for the build and the package later the package needs a rebuild. I filled bug #852875 for calendar-exchange-provider, it's quite the same as for the sogo-connector. No header or libraries are used, the B-D and the Depends field needs to be adjusted. Mozilla upstream released Thunderbird 45.7.0 two days ago. Are you o.k. if we plan the upload about this version into unstable? I mean, there are only two packages with that dependency on the -dev package and other packages wont break even for stretch. Regards Carsten
Bug#851989: release.debian.org: de-branding Icedove, Thunderbird packages in Stretch?
One more minor note, On Tue, Jan 24, 2017 at 08:07:02AM +0100, Carsten Schoenert wrote: ... > So maybe some extension may break now simply because the package > dependencies are now to strict. Such packages should be easy to find as > if the icedove package is referenced the thunderbird package needed to > be provided as well. Christoph could (and should) address such problems > in his announcement. this statement is not fully true from a backview. We need to ship the transitional icedove package for Stretch at all times so a dependency on 'icedove' will end in the reverse dependency on 'thunderbird' and the extension will work. For Stretch+1 we need to proof the xul-ext packages for depending on thunderbird then. Christoph will check which reverse depends on icedove-dev we have. Regards
Bug#851989: release.debian.org: de-branding Icedove, Thunderbird packages in Stretch?
Hello Julien, On Sun, Jan 22, 2017 at 05:32:01PM +0100, Julien Cristau wrote: > I guess it's better to do that now rather than after the release. What > are the effects of the rebranding on reverse dependencies, if any? thanks for your positive answer in principal about that! And yes, we think also the switch is done better now than some weeks after the relase. I'm running Thunderbird packages for about at least 1/2 year in all versions since 45.1.0. I haven't had any problems on that and haven't seen any non working reverse depended packages. But I can't test all xul-ext-* packages and other named plugins that can be found in the repository. As far as I've seen most of the maintainers of such packages have already done the extension the the package description with the adoption of the Provides/Enhances and the Depends field of their packages. So maybe some extension may break now simply because the package dependencies are now to strict. Such packages should be easy to find as if the icedove package is referenced the thunderbird package needed to be provided as well. Christoph could (and should) address such problems in his announcement. The typical extensions I'm using are working so far. Normaly I've installed enigmail, xul-ext-adblock-plus, xul-ext-compactheader, xul-ext-dispmua. I don't know a binary based reverse package that is using header and libs from icedove-dev or thunderbird-dev package. And I haven't done a look in detail into the the libraries in /usr/lib/icedove-devel/sdk/lib/ and /usr/lib/thunderbird-devel/sdk/lib/ Namely there are four libararies there: libldap60.so, libldif60.so, libprldap60.so, libxul.so So I can't say right now if there are some potentially pitfall inside. But that should be easy to check. Regards Carsten
Re: transition of packages into testing where Build-Depends can't be fulfilled for some architecture
Hello Emilo, Am 22.01.2017 um 23:36 schrieb Emilio Pozuelo Monfort: > Changing the architecture doesn't help and is not needed. You can revert that > in > your next upload. > > The issue is that the kicad-common package went from arch:all to arch:any, and > the arch:all package is still around. The arch:all package was available to > mips64el and s390x, and that confuses britney when switching to arch:any and > being unavailable on some architectures. > > The solution here is to file a removal bug for kicad-common_4.0.5+dfsg1-1 > against ftp.debian.org thanks for this helpful information! I wasn't aware of that reason why britney isn't showing the expected view. I will revert my last change about the architectures in a future upload. I think Adrian was much quicker than me about the removal request you suggested, thanks Adrian for filing the RM bug. https://bugs.debian.org/852262 -- Regards Carsten Schoenert
Bug#851989: release.debian.org: de-branding Icedove, Thunderbird packages in Stretch?
Package: release.debian.org Severity: normal Dear release team, as you know the Iceweasel package was moving back to use the offizial Mozilla Branding, that was reintroducing the Firefox packages. Sylvestre Ledru was requesting the same for Icedove, please see report #816679. For various reasons it tooks a painful long time to follow that request and do the needed preparation and basic testing of all. Unfortunately the new de-branded thunderbird packages couldn't be uploaded before 5th Dec 2016. In the near past we also was fighting with the binutils issue on the mips* platforms and focused on preparation for stable-security uploads. Anyway, Christoph was able to upload a first shoot of the new thunderbird packages into experimental on 31th Dec 2016. Some days ago Christoph has uploaded a new version with some fixups to experimental. We have planed to do a d-d-a this weekend about the relaunch of Thunderbird to get some more testers. We also would like to see the migrated Thunderbird packages going into the stretch release. But as we are now after the 5th Jan we need to figure out the possibility with the release team. So I like to ask what's the release team is thinking about Thunderbird for stretch. We believe it's still possible to do that. [1] https://bugs.debian.org/816679 -- System Information: Debian Release: 9.0 APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: armhf Kernel: Linux 4.8.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
transition of packages into testing where Build-Depends can't be fulfilled for some architecture
Hello, for some time I'm working on the package kicad [1] to help the current maintainer Georges Khaznadar. Georges told me he currently haven't the needed time to get kicad fully prepared for the Stretch release and thankfully he gave me upload rights. So I worked on the latest release of KiCad v4.0.5 and prepared the upload and changes for a Debian release. KiCad is using a lot of the Boost libraries, so the package libboost-context-dev is also needed. As I've now have seen boost changed [2] the supported platforms for this package in 1.58.0.2 and only the platforms any-i386 any-amd64 armel armhf arm64 mips mipsel powerpc ppc64el are now provided with a package of libboost-context-dev. Thus kicad isn't build able on mips64el and s390x [3]. And some other non RC platforms as well. So, now to my question, is this behavior preventing kicad to migrate into testing after the delay? Need I to change the Architecture field for the arch related packages of kicad then accordingly? As we are going on to the 26th January I would solve this issue before we would need to call for unblocking later. Or would kicad enter testing automatically and no further action is need for kicad? Thanks! [1] https://tracker.debian.org/pkg/kicad [2] http://metadata.ftp-master.debian.org/changelogs/main/b/boost-defaults/unstable_changelog https://sources.debian.net/src/boost-defaults/1.62.0.1/debian/control/#L200 [3] https://buildd.debian.org/status/package.php?p=kicad -- Regards Carsten Schoenert
Bug#796323: stretch-pu: package icedove/38.2.0-1~stretch
Hello Julien, On Tue, Aug 25, 2015 at 02:54:22PM +0200, Julien Cristau wrote: Control: tag -1 stretch Control: reopen -1 On Fri, Aug 21, 2015 at 12:24:07 +0200, Carsten Schoenert wrote: Package: release.debian.org Severity: normal Tags: strech User: release.debian@packages.debian.org Usertags: pu Hello there, due the GCC-5 transition we would like to upload the current Icedove ESR version (aka Thunderbird 38.2.0) to proposed updates for jessie. Do you mean stretch? yes, sorry for wrong spelled distro. The latest beta version 40.0~b1 is uploaded several days ago to experimental and the previous version 38.1.0-1 is currently in unstable. Due not go out of sync to current upstream versions we would like to place a recent version into stretch via proposed updated. That upload FTBFS on mips. (Also, please don't close release.d.o bugs via package changelogs.) I was asking Mike Homey if he can see something that would be probably wrong but he/we found nothing. We come to the conclusion that we should try another build on another buildd first before refractoring the patches again. We had similiar issue in the past on other architecture there a new build on another host went fine. Could please retrigger a build for mips on another host than mips-aql-01? Thanks and regards Carsten
Bug#796323: t-p-u of Icedove 38.2.0-1~stretch
Hello Niels, On Wed, Aug 26, 2015 at 08:18:01AM +0200, Niels Thykier wrote: Hi Carsten, Thanks for looking into this. We always use bugs to keep track of updates to tpu (and other pu-suites). In this case, you already filed #796323, which we will be using[1]. I see Julien has already replied to you there nothing an issue with building icedove on mips[2]. now I see, the reply of Julian hasn't reached me (until now). I was thinking about closing the bug in this case was not right ... but o.k. now I'm enlighted. ;) [...] As mentioned earlier, please follow up on #796323. I will do. Thanks, ~Niels [1] For future reference, please do not close the tpu bug in an upload. It is closed by the release team once the upload is accepted into testing rather than into testing-proposed-updates I tried to follow the instructions of the developers referens on 5.13.3, but exact this point is a little bit unclear I think. Maybe the reference should be a liitle bit more expanded here. Anyway, will look now into the build issue and thanks for explanations. Regards Carsten
t-p-u of Icedove 38.2.0-1~stretch
Hello, with #796323 a updated version of Icedove was uploaded to t-p-u. Depended on the GCC5 transition and it's migration progress some blocks coming along with this also to the current version of Icedove in unstable. So the version in testing is the outdated version 31.7.0-1, Wheezy and Jessie got 31.8.0-* in the between times. The 31.8.0 marks the end of the ESR series for version 31 so we don't wanted to package 31.8.0 for testing and worked on 38.0.1-1 in unstable so far. In the between time updated to 38.1.0-1. As made clear by Nils Thykier af DebConf we should not upload to unstable anymore if not really related to GCC5 transition he proposed me to upload newer ESR versions of Icedove to t-p-u. That's done last week by the bugnumber above. So sorry for maybe stupid asking, what needs to be done to get accept the upload of Icedove 38.2.0-1~stretch in testing? Did I need to append a debdiff? --- Regards Carsten Schoenert
Bug#796323: stretch-pu: package icedove/38.2.0-1~stretch
Package: release.debian.org Severity: normal Tags: strech User: release.debian@packages.debian.org Usertags: pu Hello there, due the GCC-5 transition we would like to upload the current Icedove ESR version (aka Thunderbird 38.2.0) to proposed updates for jessie. The latest beta version 40.0~b1 is uploaded several days ago to experimental and the previous version 38.1.0-1 is currently in unstable. Due not go out of sync to current upstream versions we would like to place a recent version into stretch via proposed updated. We are working also on providing versions for stable-security and oldstable-security, but that's not the focus here. -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: armhf Kernel: Linux 4.1.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
Bug#777472: unblock: icedove-l10n/31.4.0-1
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Please unblock package icedove-l10n
Christoph Goehre as package maintainer uploaded several days ago an updated
version of the l10n files for the icedove package.
By this upload a wrong Recommends on the package icedove-l10n-sr was fixed
and also a small update on the romanian language from the upstream source.
- From our point of view it would be good to keep the l10n package in sync
with the package version of icedove as the l10n packages have no reverse
depends except on icedove.
Here are the debdiff output for icedove-l10n-sr
$ debdiff icedove-l10n-sr_31.2.0-1_all.deb icedove-l10n-sr_31.4.0-1_all.deb
File lists identical (after any substitutions)
Control files: lines which differ (wdiff format)
-
Depends: icedove (= [-31.2.0),-] {+31.4.0),+} icedove ( 32)
Recommends: [-hunspell-se-] {+hunspell-sr+}
Version: [-1:31.2.0-1-] {+1:31.4.0-1+}
and for icedove-l10n-ro
$ debdiff icedove-l10n-ro_31.2.0-1_all.deb icedove-l10n-ro_31.4.0-1_all.deb
File lists identical (after any substitutions)
Control files: lines which differ (wdiff format)
-
Depends: icedove (= [-31.2.0),-] {+31.4.0),+} icedove ( 32)
Version: [-1:31.2.0-1-] {+1:31.4.0-1+}
unblock icedove-l10n/31.4.0-1
- -- System Information:
Debian Release: 8.0
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf
Kernel: Linux 3.10-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
iQIcBAEBCAAGBQJU14r1AAoJEIMBYBQlHR2wmK8P/3b39YDr6ffFa/aTwYUnzVlP
R00IpczeMOC1G6eJpjl65RuFJEHyPE1VHZottxmzQEjE8uFUE7022uzJW33H1eCy
FH+3pLz1N1xJvim+M62eLF2I813nuqep85em+0Ag6YMmWX5aZzGV69IX1maU3QS8
5JoFv5y+j0wAJD+vmIj6J6Ogt6O/eVWr5xyktbaaoPcOQpKtNXg8qqNXJMPGJGLa
Ynu9wgN2iY3+uHdPSHW9kmuB2XIN5j+7k5QOGfr9s9a624h9IEH/AqtnJqXPO70Y
acKZc1/1AJrUTfsrV9RvFsQRRlIQpGXCeHrdZGIZzafGPzRkJHF8hQJeXbrMKeMU
WV+OMOyrkVeXfcY9jiCRUtmZ8i2UEX0ehKsDE5KJ/kIsi0LsWzStytKhY8ClKX5y
YsK04tNJC7zoX8MCuNPKHb74ybEoDOJ9hNp4omZsq7M/Hs7e8rimQGU+cyc2hs/a
APC9RmvFKcs5XKSTjqnLUm50n7MfuHvNqqGmkQSydOz8LjdUuVugybtrqfF6ggcl
rNd1YkRCXxalc7xdThi4MOhzRjXtli+2hiY5c4owJ6NZov7CDzIciaj/4GmzMnzm
soiyuQ4eSKE16syWbcV3sx3cOv8BUwdxBdSWd013VpRcq8QEsP0NWLnsIOgH21ut
SoVZgpO4JxpDTiJBGHv4
=8Ud/
-END PGP SIGNATURE-
--
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive:
https://lists.debian.org/20150208161241.15925.26712.report...@jessie.cruise.homelinux.net
Bug#772455: unblock: sogo-connector/24.0.7-1
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package sogo-connector
The sogo-connector package is a plugin for Icedove/Thunderbird which is
depending
on the version of the iceowl-extension package. Upstream (Inversa
http://www.inverse.ca)
prepares packages only for the ESR versions of Thunderbird. Currently for the
31.x.x releases.
The sogo-connector has no other dependencies as the correct version on
iceowl-extension.
The upload of the current version in testing for the sogo-connector package was
depending on the released version by upstream. While packaging the version
that's
currently in the testing repository it was 24.0.7, shortly after this upload
upstream
was releasing a new version with explicitly increased version for minVersion
within
the install.rdf to version 31.x.x for the iceowl-extension (Lightning) to get
the
plugin also working with the releases of version 31 for Thunderbird.
The current version of sogo-connector in testing is working with Icedove and
iceowl-extension 31.2.0, but I suspect some incompatibilities in one of the
upcomming
versions of Icedove and iceowl-extension. Also Inversa was fixing a bug in
version
31.0.0 what makes the sogo-connector automatism working again to autofill
adresses
while typing.
http://sogo.nu/bugs/view.php?id=2870
Also a small fix for building the source by make with -j[ 1] was done.
http://sogo.nu/bugs/view.php?id=2922
To keep the sogo-connector in sync with the packages from the Icedove package I
would
like to suggest to let enter the current version into testing from sid.
The debdiff looks like this:
$ debdiff xul-ext-sogo-connector_24.0.7-1_all.deb
xul-ext-sogo-connector_31.0.0-1_all.deb
File lists identical (after any substitutions)
Control files: lines which differ (wdiff format)
Breaks: icedove ( [-24.0)-] {+31.0)+}
Depends: icedove (= [-24.0),-] {+31.0),+} iceowl-extension (= 31~)
Installed-Size: [-955-] {+956+}
Version: [-24.0.7-1-] {+31.0.0-1+}
The diff between the the upstream version 24.0.7 and 31.0.0 follows here:
$ git show upstream/31.0.0
tag upstream/31.0.0
Tagger: Carsten Schoenert c.schoen...@t-online.de
Date: Wed Oct 29 19:48:07 2014 +0100
Upstream version 31.0.0
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
iQIcBAABCAAGBQJUUTZnAAoJEIMBYBQlHR2w/JYP/0v41eUK3iiGNTh4VA4oxRP5
jnZcFtboosA5HTQq35KYzwQsOh86Aw2UsDCE02X7K8+BG4z8BsrKIH8wVjiSHrXI
f+j9827GL28sd4yLzNlJky8LfmRbrU2/xFv7QnYcUUeC1PdVPsvGUirKL2X8X4PV
Lv0LQLXcgcO4fuYKAGGa15V1o9raJ5Gi6lEuk9uU8n9jkStoAqLx90Rx4B2FHl7M
1eM1t7zRU4ElhKXVa7ToP8SMqkwFJpt4EDygVk7oBdas8Yey0QDqV1HpO+zh0HHk
necMJZYWudg8q0TeHDyvmnnGoxjB3B5CyreOrAn5Pd2mTCreDy8/ick1Jx9EUFVe
/2+Yu3j6WArdUvv+X0CuhATjAQBaJsZP0sQEQ8yMpUjZz1t4JpMrrhxO3fvF6gqD
EiZ0Ug/5nykfuwCaw8rCjGqonKcubfd1L1A/vZzrHSLi2Vsyf3JJhdzPp94S7epH
L/N9ufF7Mhw4JyF0vSuIDeZiWXzL8CGbi5byLuov88xbIukLND6+sGu4VgxWlUYY
B1rlG/eRHLALJuk0xNLPiLAF2K37jKzRHO8XOJhb/H2V9GCWg7JBCaHSPQ/ql60w
PKk6/Z6ILSoMYUNpa+1crtCsEm2oQoaJ3NjyIZGkEKIhmCM5QmrHFZlIExU9ICuB
YVqR5F704XCtbmJIHrFH
=PkSH
-END PGP SIGNATURE-
commit 61f550d13918c5ee501e861e3dc5701069c4494f
Author: Carsten Schoenert c.schoen...@t-online.de
Date: Wed Oct 29 19:48:06 2014 +0100
Imported Upstream version 31.0.0
diff --git a/RELEASE-NOTES b/RELEASE-NOTES
index 5c293e1..dc5918d 100644
--- a/RELEASE-NOTES
+++ b/RELEASE-NOTES
@@ -1,8 +1,10 @@
NEWS
-24.0.7 Fixed Hungarian translation
-
+31.0.0 Initial import for Thunderbird 31 and applied fix for bug #2870
+ Added patch from bug #2922
+ Fixed Hungarian translation (#2888)
+
24.0.6 We now correctly detect ACL changes on calendar components and
refresh the cache if necessary.
We also no longer require a Thunderbird restart when reloading
diff --git a/chrome/content/sogo-connector/addressbook/categories.js.orig
b/chrome/content/sogo-connector/addressbook/categories.js.orig
new file mode 100644
index 000..a7fa4db
--- /dev/null
+++ b/chrome/content/sogo-connector/addressbook/categories.js.orig
@@ -0,0 +1,92 @@
+let SCContactCategories = {
+getCategoriesAsString: function SCCC_getCategoriesAsString() {
+let cats = null;
+
+let prefService =
Components.classes[@mozilla.org/preferences-service;1]
+
.getService(Components.interfaces.nsIPrefBranch);
+try {
+cats =
prefService.getCharPref(sogo-connector.contacts.categories);
+}
+catch(e) {
+let strService =
Components.classes[@mozilla.org/intl/stringbundle;1]
+
.getService(Components.interfaces.nsIStringBundleService);
+let bundle =
strService.createBundle(chrome://sogo-connector/locale/preferences/categories.properties);
+cats = bundle.GetStringFromName(contacts.categories);
+}
+
+return cats;
+},
+
+setCategoriesAsString
Re: Bug#747532: Any plans getting fix for bug#747532 into next stable release?
Hello Jonas, Am 12.06.2014 14:49, schrieb Jonas Smedegaard: That is arguably of no use, however, if not then also fixed in stable. Any plans on doing that? same here too of course [1]. [1] http://anonscm.debian.org/gitweb/?p=pkg-mozilla/icedove.git;a=commit;h=dfbb25e2b7dcf10e318e64c717c08732db80bfd7 -- Regards Carsten signature.asc Description: OpenPGP digital signature
Re: Bug#747546: Any plans getting fix for bug#747546 into next stable release?
Hello Jonas, Am 12.06.2014 14:58, schrieb Jonas Smedegaard: That is arguably of no use, however, if not then also fixed in stable. Any plans on doing that? yes of course. It's already prepared [1] for the next version 24.6.0 of Icedove. The version 24.6.0 for the Thunderbird package was released an Tuesday this week, as far as I know Christoph will prepare the upload for stable-security this weekend. [1] http://anonscm.debian.org/gitweb/?p=pkg-mozilla/icedove.git;a=commit;h=ddd0d7e761e24b24873cf2ef6dda70692a5841d3 -- Regards Carsten signature.asc Description: OpenPGP digital signature
Transition of Icedove 24.2.0 to testing
Hello release team, as Mike asked a few days before for Iceweasel, would it be possible to force the transition of the current Icedove version 24.2.0 from unstable to testing before Christoph will prepare the package for stable-security? I'm currently able to build a version for Wheezy but it needs a little bit further tests before it can be uploaded by Christoph. -- Regards Carsten signature.asc Description: OpenPGP digital signature
Bug#725823: pu: package icedove/3.0.11-1+squeeze15
Hello, On Tue, Oct 08, 2013 at 09:30:26PM +0200, Carsten Schoenert wrote: Any chances to get this change into the next point release for Squeeze? the next point release will for Squeeze is comming in february as far as I can see. What about this bug to take place into the next point release? Regards Carsten -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20140108165003.ga20...@x201s.cruise.homelinux.net
Bug#725823: pu: package icedove/3.0.11-1+squeeze15
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: pu Dear release team, for the icedove version 3.0.x (and 3.1.x in squeeze-backport) released with squeeze are some similar bugs opened after the release of squeeze. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=626812 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=659301 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=659994 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=660736 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=691985 Those bugs are all depened on undefined symbols that all happend after the libc version 2.11.3-x. That relay on the order icedove is reading the symbols from the varous libraries and theese libraries again from other libraries. So in the end a fix is basicly simply, icedove has to be started with the presetted variables LD_LIBRARY_PATH and LD_PRELOAD to be shure the symbols are readed in the correct order and icedove will start and work correctly. The following patch will solve the described issues from the bug reports above. The patched file mozilla.in will become /usr/lib/icedove/icedove (/usr/lib/thunderbird/thunderbird in the original Thunderbird package) while package creating and is the executable start script for icedove. This script calls at the end /usr/lib/icedove/run-mozilla.sh that is shipped by Mozilla. diff --git a/mozilla/build/unix/mozilla.in b/mozilla/build/unix/mozilla.in index 4f54e23..336737c 100644 --- a/mozilla/build/unix/mozilla.in +++ b/mozilla/build/unix/mozilla.in @@ -134,6 +134,8 @@ if [ $debugging = 1 ] then echo $dist_bin/run-mozilla.sh $script_args $dist_bin/$MOZILLA_BIN $@ fi +export LD_LIBRARY_PATH=/usr/lib/icedove +export LD_PRELOAD=/usr/lib/icedove/libxpcom.so $dist_bin/run-mozilla.sh $script_args $dist_bin/$MOZILLA_BIN $@ exitcode=$? Any chances to get this change into the next point release for Squeeze? Regards Carsten -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20131008193026.6860.70903.report...@jessie.cruise.homelinux.net
