Bug#1004666: Unable to set TEXMFAUXTREES in texlive
Package: texlive-latex-base
Version: 2020.20210202-3
I have a texmf tree that I plan to deploy in a *.deb package using a private
company-wide debian repository.
In postinst, I'm expecting to be able to add my tree to the TEXMFAUXTREES:
$ sudo tlmgr conf auxtrees add /usr/share/texlive/texmf-mycompany
Then I confirm it was added
$ tlmgr conf auxtrees
List of auxiliary texmf trees:
/usr/share/texlive/texmf-mycompany
I can also confirm this in the texmf.cnf:
$ cat /usr/share/texlive/texmf.cnf
TEXMFAUXTREES = /usr/share/texlive/texmf-mycompany,
However, it is not applied:
$ kpsewhich -var-value TEXMFAUXTREES
{}
Further inspection shows /usr/share/texlive/texmf.cnf is not read by texlive:
$ kpsewhich -all texmf.cnf
/etc/texmf/web2c/texmf.cnf
/usr/share/texmf/web2c/texmf.cnf
/usr/share/texlive/texmf-dist/web2c/texmf.cnf
$ kpsewhich -show-path texmf.cnf
/etc/texmf/web2c:/usr/local/share/texmf/web2c:/usr/share/texmf/web2c:/usr/share/texlive/texmf-dist/web2c://share/texmf/web2c
If support for /usr/share/texlive/texmf.cnf was removed to ensure tlmgr doesn't
conflict with apt, there should be an alternative provided so private package
maintainers can deploy trees.
These are the texmf directories currently supported:
TEXMFLOCAL /usr/local/share/texmf
TEXMFAUXTREES {}
TEXMFDIST /usr/share/texlive/texmf-dist
TEXMFHOME $HOME/texmf
Bug#968612:
tags 968612 + upstream thank you Bug forwarded upstream: https://github.com/systemd/systemd/issues/16781 signature.asc Description: This is a digitally signed message part
Bug#968612: New ConditionEnable feature inop
Package: systemd Version: 246.1-1 Severity: normal Systemd 246 introduces ConditionEnviornment=/AssertEnvironment [1] in the [Unit] configuration (see systemd.unit(5)). This feature does not appear to work. The first evidence of this is neither ConditionEnvironment or AssertEnvironment get parsed by `systemd-analyze` which other conditions are parsed (even when empty): $ systemd-analyze condition \ 'ConditionKernelVersion=' \ 'ConditionKernelVersion=' \ 'ConditionACPower=' \ 'ConditionArchitecture=' \ 'AssertPathExists=' \ 'AssertEnvironment=' Cannot parse "AssertEnvironment=". The second evidence is that targets can be reached when conditions are not met: $ systemctl --user cat i3-session-pre.target # /home/stew/.config/systemd/user/i3-session-pre.target [Unit] Description=i3 session BindsTo=graphical-session-pre.target ConditionEnvironment=THIS_ENV_DOESNT_EXIST=1 $ systemctl --user start i3-session-pre.target $ systemctl --user status i3-session-pre.target ● i3-session-pre.target - i3 session Loaded: loaded (/home/stew/.config/systemd/user/i3-session- pre.target; static) Active: active since Tue 2020-08-18 17:29:36 CEST; 6s ago Aug 18 17:29:36 stewbian systemd[1717]: Reached target i3 session. The same behaviour was observed for (1) non-existent environment variables (2) environment variables with incorrect data (3) matching environment variables. I can confirm that the pull request related to this [2] appears to be integrated. I confirmed that with `apt source systemd` and inspecting the sources. I suspect the problem lies upstream. [1]: https://raw.githubusercontent.com/systemd/systemd/master/NEWS [2]: https://github.com/systemd/systemd/pull/15817 signature.asc Description: This is a digitally signed message part
Bug#957091:
Solved upstream with: https://github.com/ckb-next/ckb-next/commit/a9f41cd8b8f5b04c0c66c6d94f96a9725943831ehttps://github.com/ckb-next/ckb-next/commit/a9f41cd8b8f5b04c0c66c6d94f96a9725943831e Will patch debian version
Bug#933784: Patch rev 2
I realized that d/patches/* wasn't enough. I also had to update d/control. Please see corrected patch attached. From dc7147723a6297410cf56a451ba8a20b177e396b Mon Sep 17 00:00:00 2001 From: Stewart Ferguson Date: Tue, 6 Aug 2019 19:01:57 +0200 Subject: [PATCH] Updating rouge dependency to 3.7.0 (Closes: #933784) --- debian/control | 4 ++-- debian/patches/rouge_3_7.patch | 26 ++ debian/patches/series | 1 + 3 files changed, 29 insertions(+), 2 deletions(-) create mode 100644 debian/patches/rouge_3_7.patch diff --git a/debian/control b/debian/control index 6174cf5..2ade209 100644 --- a/debian/control +++ b/debian/control @@ -32,7 +32,7 @@ Build-Depends: dbconfig-common, ruby-rmagick (>= 2.14.0~), ruby-roadie (>= 3.2.2~), ruby-roadie-rails (>= 1.3.0~), - ruby-rouge (>= 3.3.0~) + ruby-rouge (>= 3.7.0~) Build-Depends-Indep: po-debconf Standards-Version: 4.3.0 Vcs-Browser: https://salsa.debian.org/ruby-team/redmine @@ -71,7 +71,7 @@ Depends: dbconfig-common, ruby-rmagick (>= 2.14.0~), ruby-roadie (>= 3.2.2~), ruby-roadie-rails (>= 1.3.0~), - ruby-rouge (>= 3.3.0~), + ruby-rouge (>= 3.7.0~), libjs-jquery, libjs-jquery-ui, libjs-raphael, diff --git a/debian/patches/rouge_3_7.patch b/debian/patches/rouge_3_7.patch new file mode 100644 index 000..a6a6a5a --- /dev/null +++ b/debian/patches/rouge_3_7.patch @@ -0,0 +1,26 @@ +Description: Updating rouge dependency to 3.7.0 + Debian provides ruby-rouge 3.7.0 while redmine 4.0.4 requires ~>3.3.0. + Shortly after releasing 4.0.4 upstream updated rouge dependency to 3.7.0 + with no further changes to the sources. Therefore it is safe to do the same + in Debian's release of 4.0.4. + . + This change is already applied in redmine release 4.1.0. This patch should be + removed when importing that version or higher. +Author: Stewart Ferguson +Bug: http://www.redmine.org/issues/31556 +Forwarded: not-needed +Applied-Upstream: 4.1.0 +Last-Update: 2019-08-06 +--- +This patch header follows DEP-3: http://dep.debian.net/deps/dep3/ +--- a/Gemfile b/Gemfile +@@ -3,7 +3,7 @@ source 'https://rubygems.org' + gem "bundler", ">= 1.5.0" + + gem "rails", "~> 5.2.2" +-gem "rouge", "~> 3.3.0" ++gem "rouge", "~> 3.7.0" + gem "request_store", "~> 1.1" + gem "mini_mime", "~> 1.0.1" + gem "actionpack-xml_parser" diff --git a/debian/patches/series b/debian/patches/series index 8178d32..a740184 100644 --- a/debian/patches/series +++ b/debian/patches/series @@ -4,3 +4,4 @@ 0004-Add-multi-tenancy-support.patch 0005-Assume-default-instance.patch use_system_jquery_libs.patch +rouge_3_7.patch -- 2.23.0.rc1 signature.asc Description: This is a digitally signed message part
Bug#933784: Patch for bug
tags 933784 + patch thank you I've attached a simple patch to address this issue. Simply bumps the ruby-rouge revision. The change has already been made upstream[1], requiring only the dependency version bump and targeting release 4.1.0 (at which time this patch should be removed). I was able to install this package properly on my unstable installation after building with this patch. [1] http://www.redmine.org/issues/31556 Stewart Ferguson From 341b1f9b04199c20e64ed5c65fe30bba8af2ffaa Mon Sep 17 00:00:00 2001 From: Stewart Ferguson Date: Tue, 6 Aug 2019 19:01:57 +0200 Subject: [PATCH] Updating rouge dependency to 3.7.0 (Closes: #933784) --- debian/patches/rouge_3_7.patch | 26 ++ debian/patches/series | 1 + 2 files changed, 27 insertions(+) create mode 100644 debian/patches/rouge_3_7.patch diff --git a/debian/patches/rouge_3_7.patch b/debian/patches/rouge_3_7.patch new file mode 100644 index 000..a6a6a5a --- /dev/null +++ b/debian/patches/rouge_3_7.patch @@ -0,0 +1,26 @@ +Description: Updating rouge dependency to 3.7.0 + Debian provides ruby-rouge 3.7.0 while redmine 4.0.4 requires ~>3.3.0. + Shortly after releasing 4.0.4 upstream updated rouge dependency to 3.7.0 + with no further changes to the sources. Therefore it is safe to do the same + in Debian's release of 4.0.4. + . + This change is already applied in redmine release 4.1.0. This patch should be + removed when importing that version or higher. +Author: Stewart Ferguson +Bug: http://www.redmine.org/issues/31556 +Forwarded: not-needed +Applied-Upstream: 4.1.0 +Last-Update: 2019-08-06 +--- +This patch header follows DEP-3: http://dep.debian.net/deps/dep3/ +--- a/Gemfile b/Gemfile +@@ -3,7 +3,7 @@ source 'https://rubygems.org' + gem "bundler", ">= 1.5.0" + + gem "rails", "~> 5.2.2" +-gem "rouge", "~> 3.3.0" ++gem "rouge", "~> 3.7.0" + gem "request_store", "~> 1.1" + gem "mini_mime", "~> 1.0.1" + gem "actionpack-xml_parser" diff --git a/debian/patches/series b/debian/patches/series index 8178d32..a740184 100644 --- a/debian/patches/series +++ b/debian/patches/series @@ -4,3 +4,4 @@ 0004-Add-multi-tenancy-support.patch 0005-Assume-default-instance.patch use_system_jquery_libs.patch +rouge_3_7.patch -- 2.23.0.rc1 signature.asc Description: This is a digitally signed message part
Bug#925871: unblock: python-apptools/4.4.0-3
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package python-apptools
piuparts found some broken links in python-apptools-doc binary
documentation package in 4.4.0-2 [1]. Most links are solved by
adding a missing Depends (libjs-sphinxdoc). The last link was
solved by fixing a path of the source and destination of the link.
As the debdiff is so trivial, my sponsor suggested I apply for an
unblock. The fix (4.4.0-3) is already in unstable.
[1]
https://piuparts.debian.org/sid-broken-symlinks/fail/python-apptools-doc_4.4.0-2.log
* link broke shortly after uploading 4.4.0-3 to unstable
`debdiff python-apptools_4.4.0-2.dsc python-apptools_4.4.0-3.dsc` attached
unblock python-apptools/4.4.0-3
-- System Information:
Debian Release: buster/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.19.0-4-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8),
LANGUAGE=en_GB:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru python-apptools-4.4.0/debian/changelog python-apptools-4.4.0/debian/changelog
--- python-apptools-4.4.0/debian/changelog 2019-02-14 21:19:20.0 +0100
+++ python-apptools-4.4.0/debian/changelog 2019-03-05 21:26:46.0 +0100
@@ -1,3 +1,9 @@
+python-apptools (4.4.0-3) unstable; urgency=medium
+
+ * Fixing broken links in python-apptools-doc
+
+ -- Stewart Ferguson Tue, 05 Mar 2019 21:26:46 +0100
+
python-apptools (4.4.0-2) unstable; urgency=medium
* Adding Breaks and Replaces to new doc package (Closes: #922286)
diff -Nru python-apptools-4.4.0/debian/control python-apptools-4.4.0/debian/control
--- python-apptools-4.4.0/debian/control 2019-02-14 21:19:20.0 +0100
+++ python-apptools-4.4.0/debian/control 2019-03-05 21:17:51.0 +0100
@@ -55,7 +55,7 @@
Package: python-apptools-doc
Architecture: all
Section: doc
-Depends: ${misc:Depends}
+Depends: ${misc:Depends}, ${sphinxdoc:Depends}
Breaks: python-apptools (<< 4.4.0)
Replaces: python-apptools (<< 4.4.0)
Description: ETS Application Tools (doc)
diff -Nru python-apptools-4.4.0/debian/python-apptools-doc.links python-apptools-4.4.0/debian/python-apptools-doc.links
--- python-apptools-4.4.0/debian/python-apptools-doc.links 2019-02-02 17:31:53.0 +0100
+++ python-apptools-4.4.0/debian/python-apptools-doc.links 2019-03-05 21:09:18.0 +0100
@@ -1 +1 @@
-usr/share/doc/python-apptools-doc/README.rst usr/share/python-apptools-doc/html/_sources/README.rst.txt
+usr/share/doc/python-apptools/README.rst usr/share/doc/python-apptools/html/_sources/README.rst.txt
signature.asc
Description: This is a digitally signed message part
Bug#924417: lintian: Allow *.pth files in python dist-packages
Package: lintian Version: 2.9.1 Severity: normal Tags: patch Dear Maintainer, /usr/lib/python*/dist-packages/*.pth files currently trigger lintian error tag: unknown-file-in-python-module-directory *.pth should not be unknown. They are well-documented by the Python specification[1] and this location is exactly where they belong. Legitimate uses of this file exist in the archive. python- testing.mysqld[2] and python-input-pad[3] override this tag with the phrase "false positive". The vast majority (>150) of others including python- matplotlib and python-gobject-2 simply ignore this lintian error as they deploy pth files[4]. There few important cases of this lintian error being raised including: - debdry deploying 'control' - python-cf deploying 'delme.nc' - python-django-ranged-response deploying 'db.sqlite3' - python3-csvkit deploying 'stdin_out.csv' One could argue that the use of *.pth files should be discouraged. Installing a package which deploys a *.pth can change the global python environment. In this case a new tag (perhaps with lower severity) would be more appropriate which warns the packager to carefully check the file's contents and consider removing it. A more relevant tag describing the position is less likely to be ignored than a general error which says this Python-specification-compliant file is 'unknown'. A new tag would be more appropriate than changing this tag because there are legitimate and important instances of the existing tag as-is. Best Regards, Stewart Ferguson [1] https://docs.python.org/3/library/site.html [2] https://sources.debian.org/src/python-testing.mysqld/1.4.0-3/debian/python3-testing.mysqld.lintian-overrides/ [3] https://sources.debian.org/src/input-pad/1.0.3-3/debian/python-input-pad.lintian-overrides/ [4] https://lintian.debian.org/tags/unknown-file-in-python-module-directory.html -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-2-amd64 (SMP w/8 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages lintian depends on: ii binutils 2.31.1-15 ii bzip2 1.0.6-9 ii diffstat 1.62-1 ii dpkg 1.19.5 ii dpkg-dev 1.19.5 ii file 1:5.35-2 ii gettext0.19.8.1-9 ii gpg2.2.12-1 ii intltool-debian0.35.0+20060710.5 ii libapt-pkg-perl0.1.34+b1 ii libarchive-zip-perl1.64-1 ii libcapture-tiny-perl 0.48-1 ii libcgi-pm-perl 4.40-1 ii libclass-accessor-perl 0.51-1 ii libclone-perl 0.41-1+b1 pn libdigest-sha-perl ii libdpkg-perl 1.19.5 ii libemail-valid-perl1.202-1 ii libfile-basedir-perl 0.08-1 ii libio-async-perl 0.72-1 ii libipc-run-perl20180523.0-1 ii liblist-moreutils-perl 0.416-1+b4 ii libparse-debianchangelog-perl 1.2.0-13 ii libpath-tiny-perl 0.108-1 ii libtext-levenshtein-perl 0.13-1 ii libtimedate-perl 2.3000-2 ii libtry-tiny-perl 0.30-1 ii liburi-perl1.76-1 ii libxml-simple-perl 2.25-1 ii libyaml-libyaml-perl 0.76+repack-1 ii man-db 2.8.5-2 ii patchutils 0.3.4-2 ii perl 5.28.1-4 ii t1utils1.41-3 ii xz-utils 5.2.4-1 Versions of packages lintian recommends: ii libperlio-gzip-perl 0.19-1+b5 Versions of packages lintian suggests: pn binutils-multiarch ii libhtml-parser-perl3.72-3+b3 ii libtext-template-perl 1.54-1 -- no debconf information From d63a53132f8aa87895f38cddee932b93f7d4f218 Mon Sep 17 00:00:00 2001 From: Stewart Ferguson Date: Tue, 12 Mar 2019 19:51:20 +0100 Subject: [PATCH] Allowing *pth files in python dist-packages --- data/files/allowed-python-files | 1 + 1 file changed, 1 insertion(+) diff --git a/data/files/allowed-python-files b/data/files/allowed-python-files index e55d096c9..edaba07d9 100644 --- a/data/files/allowed-python-files +++ b/data/files/allowed-python-files @@ -4,3 +4,4 @@ \.egg-info$ \.so$ \.py[ic]?$ +\.pth$ -- 2.20.1 signature.asc Description: This is a digitally signed message part
Bug#921021: ITP: ckb-next -- driver for Corsair keyboards and mice
Package: wnpp Severity: wishlist Owner: Stewart Ferguson * Package name: ckb-next Version : 0.3.2 Upstream Author : Tasos Sahanidis * URL : https://github.com/ckb-next/ckb-next * License : GPL-2 Programming Lang: C++ Description : ckb-next is an open-source driver for Corsair keyboards and mice. It aims to bring the features of Corsair's proprietary CUE software to the Linux and Mac operating systems. I plan to be the long-term maintainer of the application as an individual contributer. I also have an interest in keeping this package in Debian so that my own keyboard remains pretty. signature.asc Description: This is a digitally signed message part
Bug#920293: FTBFS: python-apptools auto-generated files contaminate source package
Package: python-apptools
Version: 4.3.0-1
Severity: important
Tags: ftbfs
Owner: s...@ferg.aero
When building from the Salsa git repository, this package is ftbfs. This
is because during dh_clean, setup.py checks for .git, and if it exists, it
modifies apptools/_version.py. This leaves a modified file in the tree
which causes dpkg-source to fail.
I've set the severity as "important" instead of "serious" because this does
not affect users who build from the dsc.
Full log below:
dpkg-buildpackage -us -uc -ui
dpkg-buildpackage: info: source package python-apptools
dpkg-buildpackage: info: source version 4.3.0-2
dpkg-buildpackage: info: source distribution UNRELEASED
dpkg-buildpackage: info: source changed by Ondřej Nový
dpkg-source --before-build .
dpkg-buildpackage: info: host architecture amd64
fakeroot debian/rules clean
pyversions: missing X(S)-Python-Version in control file, fall back to
debian/pyversions
pyversions: missing debian/pyversions file, fall back to supported versions
test -x debian/rules
dh_clean
dh_clean: Compatibility levels before 9 are deprecated (level 7 in use)
cd . && python setup.py clean -a
running clean
'build/lib.linux-x86_64-2.7' does not exist -- can't clean it
'build/bdist.linux-x86_64' does not exist -- can't clean it
'build/scripts-2.7' does not exist -- can't clean it
rm -rf debian/python-module-stampdir
find "/home/stew/src/python-apptools_4.3" -name '*.py[co]' -delete
find "/home/stew/src/python-apptools_4.3" -name __pycache__ -type d -empty
-delete
find "/home/stew/src/python-apptools_4.3" -prune -name '*.egg-info' -exec
rm -rf '{}' ';'
dpkg-source -b .
dpkg-source: info: using source format '3.0 (quilt)'
dpkg-source: info: building python-apptools using existing
./python-apptools_4.3.0.orig.tar.gz
dpkg-source: info: local changes detected, the modified files are:
python-apptools_4.3/apptools/_version.py
dpkg-source: error: aborting due to unexpected upstream changes, see
/tmp/python-apptools_4.3.0-2.diff.lfR1uN
dpkg-source: info: you can integrate the local changes with dpkg-source
--commit
dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2
debuild: fatal error at line 1182:
dpkg-buildpackage -us -uc -ui failed
Bug#796930: Wrong bug number
user debian-rele...@lists.debian.org usertags 796930 - bsp-2019-01-venlo thank you Disregard last message. Wrong bug... removing tags
Bug#845538: Bug solved, waiting for next release.
user debian-rele...@lists.debian.org usertags 845538 + bsp-2019-01-venlo tags 845538 + pending thank you Dependency has been changed on the salsa repository. It should be included in the next upload. Since this isn't release critical, it isn't essential for us to release immediately.
Bug#796930:
user debian-rele...@lists.debian.org usertags 796930 + bsp-2019-01-venlo tags 796930 + pending thank you Dependency has been changed on the salsa repository. It should be included in the next upload. Since this isn't release critical, it isn't essential for us to release immediately.
Bug#918751: Investigation results
noowner 827832 thank you The interesting part of the reporter's logs suggest that the following test fails: shade.tests.unit.test_object.TestObjectUploads.test_object_segment_retry_failure The failure is caused by a thread failing to spawn due to resource limitations on the reporter's machine. The reporter is using a single-processor VM. I tried to emulate this by using `dpkg-buildpackage -j1` and again by using `taskset --cpu-list 0 dpkg-buildpackage`. I was unable to reproduce the problem. I also fixed another RC bug in this package and buildd was also able to build this package. Because buildd and other single-core builds are all successful, I would regard this bug as `important` instead of `serious`. I am offloading ownership as I focus on other RC bugs.
Bug#918751: python-shade: BSP tag
user debian-rele...@lists.debian.org usertags -1 + bsp-2019-01-nl-venlo thank you signature.asc Description: This is a digitally signed message part
Bug#918671: python-shade: BSP tag
user debian-rele...@lists.debian.org usertags -1 + bsp-2019-01-nl-venlo thank you signature.asc Description: This is a digitally signed message part
Bug#915789: ITP: python-flask-cors -- Flask extension for handling CORS
Package: wnpp Owner: Stewart Ferguson Severity: wishlist * Package name: python-flask-cors Version : 3.0.7 Upstream Author : Cory Dolphin * URL : http://flask-cors.corydolphin.com * License : MIT Programming Lang: Python Description : Flask extension for handling CORS A Flask extension for handling Cross Origin Resource Sharing (CORS), making cross-origin AJAX possible. This package has a simple philosophy, when you want to enable CORS, you wish to enable it for all use cases on a domain. This means no mucking around with different allowed headers, methods, etc. By default, submission of cookies across domains is disabled due to the security implications, please see the documentation for how to enable credential’ed requests, and please make sure you add some sort of CSRF protection before doing so! I've been using this package from pip but feel it needs a home through apt like the other flask libraries. I will maintain it within the python-modules (DPMT) team. I will be pinging my usual sponsors for help uploading, but will seek help within mentors if they are unavailable. Best Regards, Stew signature.asc Description: This is a digitally signed message part
Bug#912772: ITP: python-schedutils -- Linux scheduler python bindings
Package: wnpp
Severity: wishlist
Owner: Stewart Ferguson
* Package name: python-schedutils
Version : 0.6
Upstream Author : Jiri Kastner
* URL : https://rt.wiki.kernel.org/index.php/Tuna
* License : GPL
Programming Lang: Python
Description : Linux scheduler python bindings
Python interface for the Linux scheduler
sched_{get,set}{affinity,scheduler} functions and friends.
Dependency for tuna (see ITP bug 912762).
I plan to be the long-term maintainer of the application, and will do
so as a member of the DPMT group. Co-maintainers are unnecessary as
this package is quite old and does not update much. I've already
spoken with a DD to arrange sponsorship.
signature.asc
Description: This is a digitally signed message part
Bug#912771: ITP: python-linux-procfs -- Linux /proc abstraction classes in python
Package: wnpp Severity: wishlist Owner: Stewart Ferguson * Package name: python-linux-procfs Version : 0.6 Upstream Author : Jiri Kastner * URL : https://rt.wiki.kernel.org/index.php/Tuna * License : GPL Programming Lang: Python Description : Linux /proc abstraction classes in python Python abstractions to extract information from the Linux kernel /proc files. Dependency for tuna (see ITP bug 912762). I plan to be the long-term maintainer of the application, and will do so as a member of the DPMT group. Co-maintainers are unnecessary as this package is quite old and does not update much. I've already spoken with a DD to arrange sponsorship. signature.asc Description: This is a digitally signed message part
Bug#912762: ITP: tuna -- Thread and IRQ affinity setting GUI and cmd line tool
Package: wnpp Severity: wishlist Owner: Stewart Ferguson * Package name: tuna Version : 0.14 Upstream Author : Jiri Kastner * URL : https://rt.wiki.kernel.org/index.php/Tuna * License : GPL Programming Lang: Python Description : Thread and IRQ affinity setting GUI and cmd line tool Provides interface for changing scheduler and IRQ tunables, at whole CPU and at per thread/IRQ level. Allows isolating CPUs for use by a specific application and moving threads and interrupts to a CPU by just dragging and dropping them. Operations can be done on CPU sockets, understanding CPU topology. Used by embedded RT systems to minimize interrupts on multi-core systems and achieve deterministic operation. I plan to be the long-term maintainer of the application, and will do so as a member of the PAPT group. Co-maintainers are unnecessary as this package is quite old and does not update much. I've already spoken with a DD to arrange sponsorship. signature.asc Description: This is a digitally signed message part
