Bug#1102537: r-cran-gstat: autopkgtest failure on s390x

Forky, I am downgrading this bug to remove it from my radar and (possibly) prevent autoremoval. Have a nice day, Charles -- Charles Plessy - - ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ - - charles.ple...@oist.jp Okinawa Institute of Science and Technology Graduate University Senior staff scientist

Bug#1102511: marked as pending in r-cran-cards

Control: tag -1 pending Hello, Bug #1102511 in r-cran-cards reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/r-pkg-team/r-cran-cards/-/commit/16077b248ae66edbb83

Bug#1064135: Please unblock r-cran-bigmemory 4.6.4-2

autopkgtest failures, with a possible cascade effect of more removal / failure / removal cycles. Have a nice day, Charles -- Charles Plessy - - ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ - - charles.ple...@oist.jp Okinawa Institute of Science and Technology Graduate University Senior staff scientist ~~

Bug#1064922: src:r-cran-gbm: fails to migrate to testing for too long: autopkgtest regression

stream is asking users to migrate. I would not be surprised if it is removed from CRAN in the next few years. Have a nice day, Charles -- Charles Plessy - - ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ - - charles.ple...@oist.jp Okinawa Institute of Science and Technology Graduate University Senior staff

Bug#1064135: Help needed to pass -fsigned-char to r-cran-bigmemory

On 5/12/25 10:55, Dirk Eddelbuettel wrote: On 12 May 2025 at 09:43, Charles Plessy wrote: | - A src/Makevars file containing +CXXFLAGS = -fsigned-char a) maybe use += instead of = ? b) maybe use PKG_CXXFLAGS instead as CXXFLAGS get overridden ? b) should work but it's late-ish on a s

Bug#1064135: Help needed to pass -fsigned-char to r-cran-bigmemory

you know how to pass compiler flags to R CMD INSTALL in the context of dh $@ --buildsystem R ? Have a nice day, Charles -- Charles Plessy - - ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ - - charles.ple...@oist.jp Okinawa Institute of Science and Technology Graduate University Senior staff scien

Bug#1064135: bigmemory: fails to migrate to testing for too long: autopkgtest fails on arm*, ppc64el and s390x

On Wed, 7 May 2025 18:11:57 +0900 Charles Plessy wrote: > Hi all, > > I am trying to pass -fsigned-char to the compiler when building the > package but failed to do it by adding a src/Makevars file. (see patch > below). What is the standard approach? > --- /dev/null >

Bug#1064135: bigmemory: fails to migrate to testing for too long: autopkgtest fails on arm*, ppc64el and s390x

l run on MacOS. In Debian, r-cran-bigmemory fails on arm64 and a lot of other architectures. In my understanding, char is signed on macos-arm64 and linux amd64 (x86_64) and unsigned on linux arm64. This patch passes -fsigned-char to the compiler. Author: Charles Plessy Bug-Debian:

Bug#1100292: Debian packaged Fastcluster fails its test (Was: r-cran-fastcluster: FTBFS: FAIL: test_vector (tests.fastcluster_test.test_vector))

than two weeks we will have remove fastcluster from the next Debian release, and all the packages that depend on it, if we have reasons to worry that the package is not fit for the release. How bad are is test failure? Is that something that can be ignored? Have a nice day, Charles -- Charles

Bug#1064135: bigmemory: fails to migrate to testing for too long: autopkgtest fails on arm*, ppc64el and s390x

er architectures. In my understanding, `char` is signed on `macos-arm64` and linux `amd64` (`x86_64`) and unsigned on linux `arm64`. Would it solve the problem if _bigmemory_ would pass `-fsigned-char` to the compilers? Cheers, Charles -- Charles Plessy - - ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ - - charles.ple...@o

Bug#1102447: marked as pending in r-cran-rtf

Control: tag -1 pending Hello, Bug #1102447 in r-cran-rtf reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/r-pkg-team/r-cran-rtf/-/commit/79b169f0b6d738793bc1a2f

Bug#1104495: [R-pkg-team] Bug#1104495: r-cran-httr2: flaky tests on riscv64

Control: severity -1 normal Hi Chris, we are struggling hard with bigger issues, and risc64 is not supported upstream. Also the whole architecture as a popcon score of 29. Please allow us to ignore the issue in this release. Thanks, Charles Le Thu, May 01, 2025 at 10:42:03AM +0200, Chris

Bug#1104193: pv-grub-menu: Should pv-grub-menu be removed from unstable?

Thanks Andreas, on my side I agree with the removal. Have a nice Sunday, Charles Le Sun, Apr 27, 2025 at 08:09:05AM +0200, Andreas Tille a écrit : > Source: pv-grub-menu > Version: 1.3+nmu1 > Severity: serious > Justification: grab attention of maintainer > X-Debbugs-Cc:

Bug#1099927: [R-pkg-team] Bug#1099927: r-cran-testthat does not actually break other packages

ease let me know if there is a better way. Cheers, Charles -- Charles Plessy Nagahama, Yomitan, Okinawa, Japan Debian Med packaging team http://www.debian.org/devel/debian-med Tooting from home https://framapiaf.org/@charles_plessy - You do no

Bug#1102590: [R-pkg-team] Bug#1102590: r-cran-fansi fails to migrate to testing

an-fansi stays at version 1.0.5-1 in Trixie. But won't it prevent 4.5.0-2 from migrating? Have a nice day, Charles -- Charles Plessy http://charles.plessy.org Nagahama, Yomitan, Okinawa, Japan

Bug#1103201: RM: r-cran-genabel, r-cran-genabel.data -- RoM; RC-buggy, abandonned upstream

remove r-cran-genabel.data. Thanks! Charles Le Wed, Apr 16, 2025 at 04:29:17PM +0900, Charles Plessy a écrit : > Thanks a lot but maybe we just should remove r-cran-genabel altogether? > > https://cran.r-project.org/web/packages/GenABEL/index.html > > Have a nice day, > >

Bug#1102590: r-cran-fansi fixed, not yet uploaded.

I am far from my key. Given the flood of autoremoval messages today, please feel free to upload the package before I am back home! Have a nice week-end, Charles -- Charles Plessy Nagahama, Yomitan, Okinawa, Japan Debian Med packaging team http://www.debian.org

Bug#1103227: marked as pending in r-bioc-grohmm

Control: tag -1 pending Hello, Bug #1103227 in r-bioc-grohmm reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/r-pkg-team/r-bioc-grohmm/-/commit/4054e62028b49ba19

Bug#1103227: [R-pkg-team] Bug#1103227: [reply ] r-bioc-grohmm: FTBFS: DecayAlgorithm.c:94:15: error: expected identifier or '(' before 'false'

ts it belongs to BioC 3.21 and intentionally adds a virtual dependency that prevents the package from co-existing with BioC 3.20 packages. It's easy to workaround with a patch, but in that case patching the current version in Debian is as easy and more conservative. Cheers, Charles -- Charles Ples

Bug#1103199: [R-pkg-team] Bug#1103199: Bug#1103199: [PATCH] Fix for FTBFS with R 4.5.0

Le Wed, Apr 16, 2025 at 05:21:59PM +0900, Charles Plessy a écrit : > > Instead of carrying a patch, I would like to propose to upgrade to the new > upstream version that will be released very soon. Hi again, I tested an upgrade locally, but it gets convoluted with the Bioconductor t

Bug#1103199: [R-pkg-team] Bug#1103199: [PATCH] Fix for FTBFS with R 4.5.0

. https://www.bioconductor.org/developers/release-schedule/ Have a nice day, Charles

Bug#1103201: [R-pkg-team] Bug#1103201: [PATCH] Fix for FTBFS with R 4.5.0

Thanks a lot but maybe we just should remove r-cran-genabel altogether? https://cran.r-project.org/web/packages/GenABEL/index.html Have a nice day, Charles Le Wed, Apr 16, 2025 at 03:12:45PM +0800, liwenjun a écrit : > Package: src:r-cran-genabel > Version: 1.8-0-7 > Severity: serio

Bug#1100292: r-cran-fastcluster: FTBFS: FAIL: test_vector (tests.fastcluster_test.test_vector)

rtise. If somebody else can have a look that would be great. The alternative is to release without the package and its reverse dependencies, unless we know that there is no risk to inflict erroneous computations on our users. Have a nice day, Ch

Bug#1102548: [R-pkg-team] Bug#1102548: r-cran-dendextend: autopkgtest failure

that. Have a nice day, Charles -- Charles Plessy Nagahama, Yomitan, Okinawa, Japan Debian Med packaging team http://www.debian.org/devel/debian-med Tooting from work, https://fediscience.org/@charles_plessy Tooting from home, https

Bug#1071104: marked as pending in r-cran-performance

Control: tag -1 pending Hello, Bug #1071104 in r-cran-performance reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/r-pkg-team/r-cran-performance/-/commit/8b44e48

Bug#1071104: [R-pkg-team] Bug#1071104: r-cran-performance: diff for NMU version 0.13.0-2.1

uploads pushed on Salsa, I have just updated the package with your changes by myself. There is a high probability that I just discard all changes of NMUs by accident by running `routine-update` for new upstream version updates. Maybe we should implement a safety net for that… Have a nice day, Charles

Bug#1101729: 1101729

oves the need for sed. Have a nice day, Charles -- Charles Plessy - - ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ - - charles.ple...@oist.jp Okinawa Institute of Science and Technology Graduate University Senior staff scientist ~~ Luscombe Unit ~~ https://groups.oist.jp/grsu Toots from work - ~~ ~~~

Bug#1102447: r-cran-rtf: autopkgtest failure

ew test ♻, i386: Regression or new test ♻, ppc64el: Regression > or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new > test ♻ Hi Adrian, I can not see the jobs on https://ci.debian.net/packages/r/r-cran-rtf/, it all says "No reference" everywhere. Is there a bug in the platform? Cheers, Charles

Bug#1101251: marked as pending in r-bioconductor-lpsymphony

Control: tag -1 pending Hello, Bug #1101251 in r-bioconductor-lpsymphony reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/r-pkg-team/r-bioc-lpsymphony/-/commit/4

Bug#1101711: marked as pending in r-bioc-ihw

Control: tag -1 pending Hello, Bug #1101711 in r-bioc-ihw reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/r-pkg-team/r-bioc-ihw/-/commit/e61e8f103843b99ff2bd867

Bug#1101591: [R-pkg-team] Bug#1101591: r-cran-waveslim: FTBFS: build-dependency not installable: r-cran-multitaper

Thanks Lucas, I have to apologise for this one, I forgot to upload r-cran-multitaper to NEW two weeks ago… Bonne journée ! Charles Le Sat, Mar 29, 2025 at 09:20:09PM +0100, Lucas Nussbaum a écrit : Source: r-cran-waveslim Version: 1.8.5-1 Severity: serious Justification: FTBFS Tags: trixie

Bug#1095685: Weekly Build now working again.

This problem appears to be fixed in Debian GNU/Linux testing "Trixie" - Official Snapshot amd64 NETINST with firmware 20250217-04:57 Thank you. -- Does anybody read signatures any more? https://charlescurley.com https://charlescurley.com/blog/

Bug#1092364: [Debian-med-packaging] Bug#1092364: cluster3: needs rebuild for Python 3.13 as default

e day, Charles -- Charles Plessy Nagahama, Yomitan, Okinawa, Japan Debian Med packaging team http://www.debian.org/devel/debian-med Tooting from home https://framapiaf.org/@charles_plessy - You do not have my permission to use this email to train an AI -

Bug#1072630: r-cran-dplyr needs some love

that disables the test suite. Have a nice week-end, Charles Le Sun, Nov 24, 2024 at 08:44:04AM +0900, Charles Plessy a écrit : > Hi Dirk and everybody, > > yes it is in the radar. I will disable the tests before the removal if I > or others can not fix the failure: > &g

Bug#1072630: Help needed on providing the en_US locale in autopkgtests

vide the needed locale to debci, please let me know. Have a nice day, Charles -- Charles Plessy Nagahama, Yomitan, Okinawa, Japan Debian R packaging team https://wiki.debian.org/Teams/r-pkg-team Tooting from home https://framapiaf.org/@charles_pless

Bug#1081117: (r-cran-)survey not migrating to testing autoremovals

4 at 04:14:48PM +0900, Charles Plessy a écrit : > > quick message to say that r-cran-survey now passes all the CI tests > after I converted it to an architecture-dependent package.

Bug#1077454: [Debian-med-packaging] Bug#1077454: bioperl-run: t/SABlastPlus.t failure

ink that it is probably fine to release without it and to consider removing package go if we do not get complains. Have a nice day, Charles -- Charles Plessy Nagahama, Yomitan, Okinawa, Japan Debian Med packaging team http://www.debian.org/devel/debian-med

Bug#1077463: Forwarded upstream Bug#1077463: r-cran-backports: autopkgtest regression: Testing test_dotlibPaths.R

Control: forwarded 1077463 https://github.com/r-lib/backports/issues/83 Hi all, I forwarded the issue upstream. I hope they fix it themselves and we can close this bug with a routine upload. Have a nice day, Charles Le Mon, Jul 29, 2024 at 07:56:49AM +0200, Paul Gevers a écrit : > Source

Bug#1076615: [R-pkg-team] Bug#1076615: r-cran-metamix: autopkgtest regression with rmpi 0.7-2-2 (armel, armhf, i386)

of other packages. Cheers, Charles Le Fri, Jul 19, 2024 at 01:18:54PM -0500, Dirk Eddelbuettel a écrit : > > Source: r-cran-metamix > Version: 0.3-2 > Severity: serious > > Dear Maintainers, > > Your package r-cran-metamix is showing an autopkg regression with the up

Bug#1074529: [R-pkg-team] Bug#1074529: r-cran-dimred: autopkgtest regression with r-base 4.4.1 (i386)

hecks/check_results_dimRed.html Hello everybody, among the tested release architectures, only i386 is failing. I can update r-cran-dimred so that it excludes i386. But would that mean I have to do that for its reverse-dependencies too ? Have a nice day, Charles -- Charles Plessy

Bug#1073106: marked as pending in swarm-cluster

Control: tag -1 pending Hello, Bug #1073106 in swarm-cluster reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/med-team/swarm-cluster/-/commit/790cc43073aa1d80e2b

Bug#1073105: marked as pending in ssake

Control: tag -1 pending Hello, Bug #1073105 in ssake reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/med-team/ssake/-/commit/e182ba7de0f9b15d434fec946810055d09a

Bug#1073104: marked as pending in srst2

Control: tag -1 pending Hello, Bug #1073104 in srst2 reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/med-team/srst2/-/commit/5f8b6e6042855ddba33a608e8541be06330

Bug#1073103: marked as pending in scythe

Control: tag -1 pending Hello, Bug #1073103 in scythe reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/med-team/scythe/-/commit/953eea5245cbf129820dc601f3c0669fe

Bug#1073098: marked as pending in libvcflib

Control: tag -1 pending Hello, Bug #1073098 in libvcflib reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/med-team/libvcflib/-/commit/becbc3630213bcc3e3137abdd79

Bug#1073095: marked as pending in hilive

Control: tag -1 pending Hello, Bug #1073095 in hilive reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/med-team/hilive/-/commit/904fb9ec71de3d067f31607f6d7998a4f

Bug#1073090: marked as pending in alter-sequence-alignment

Control: tag -1 pending Hello, Bug #1073090 in alter-sequence-alignment reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/med-team/alter-sequence-alignment/-/comm

Bug#1073089: marked as pending in adapterremoval

Control: tag -1 pending Hello, Bug #1073089 in adapterremoval reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/med-team/adapterremoval/-/commit/7fa0487843be8a1e3

Bug#1072979: [Debian-med-packaging] Bug#1072979: beast-mcmc - build-dependencies unsatisfiable on i386.

h-specific removals were handled automatically. That would save everybody a lot of work! Cheers, Charles -- Charles Plessy Nagahama, Yomitan, Okinawa, Japan Debian Med packaging team http://www.debian.org/devel/debian-med Tooting from work,

Bug#999646: How can I help move this forward?

; good now (and maybe close the bug if it works for you now) that would be > great! > > Thanks, > Michael > > On Thu, May 23, 2024, at 14:45, Charles Suprin wrote: > > Hello, > > > > This seems to have a fix and a patch and How does one get it > > incorporated into bookworm? > > > > Thanks. >

Bug#999646: How can I help move this forward?

Hello, This seems to have a fix and a patch and How does one get it incorporated into bookworm? Thanks.

Bug#1061344: User input needed: Stop supporting 32 bit architectures with emboss (Was: emboss-lib: identified for time_t transition but no ABI in shlibs)

, Charles

Bug#1061880: s-tui: Selecting Graphs raises a ValueError exception

Package: s-tui Version: 1.1.4-1 Severity: grave Justification: renders package unusable X-Debbugs-Cc: genpfa...@threadpitch.net Dear Maintainer, Selecting the 'Graphs' option in s-tui causes a ValueError exception: Traceback (most recent call last): File "/usr/bin/s-tui", line

Bug#1057032: wims: An updated package of wims closing all bugs exists.

to make SSO CAS working * wims-modules: don't fail on postrm if /var/lib/wims is a mount point * wims-modules: add dependency to libjs-mootools, jsxgraph, yui-compressor and asciidoc-common #988894 * backport to bookworm -- Jean Charles Delépine Wed, 22 Nov 2023 08:37:09 +0100 S

Bug#1041556: [R-pkg-team] Bug#1041556: What is the architecture name in R what we call armel/armhf

ystem("dpkg-architecture -qDEB_BUILD_ARCH", intern=TRUE) %in% c("i386", "i686", "armel", "armhf") Have a nice day, -- Charles

Bug#1042776: [R-pkg-team] Bug#1042776: Bug#1042776: r-bioc-deseq: still depends on obsolete r-api-bioc-3.16

Le Tue, Aug 01, 2023 at 09:29:59AM +0900, Charles Plessy a écrit : > > the DESeq Bioconductor package was removed from the 3.17 release > upstream. I think that we can remove it from unstable and testing too. > > I will fill a removal later today. Actually it was removed from Bi

Bug#1042776: marked as pending in r-bioc-deseq

/bad370412269ea6b7543b3f76d238f1765e3affd r-bioc-deseq (1.39.0-12) unstable; urgency=medium * Team upload. * Update patch to rebuild for BioC API 3.17 (Closes: #1042776) -- Charles Plessy Tue, 01 Aug 2023 11:41:09 +0900

Bug#1042776: [R-pkg-team] Bug#1042776: r-bioc-deseq: still depends on obsolete r-api-bioc-3.16

7 release upstream. I think that we can remove it from unstable and testing too. I will fill a removal later today. Have a nice day, Charles -- Charles Plessy Nagahama, Yomitan, Okinawa, Japan Debian Med packaging team http://www.debian.org/devel/debian-med Too

Bug#1000209: Bug #1000209

this moment in time. Making this update just before does the trick. The patch is in attachment. Regards, Charles-Antoine Couret diff --git a/debian/timidity-daemon.postinst b/debian/timidity-daemon.postinst index a3610f9..573bc09 100644 --- a/debian/timidity-daemon.postinst +++ b/

Bug#1000209: Bug #1000209

Hi, I'm working with Gabriel on this as part of a BSP. Problems experienced earlier were caused by us trying to build the package in bullseye. We tried again from bookworm and were able to build the package again. We've been able to install the package using the attached patch that doesn't hack ar

Bug#1022307: [Debian-med-packaging] Bug#1022307: status on t_coffee causing biopython ftbfs

lar version may build fine, and let biophython pass its tests, we do not know if t_coffee produces sound results on these architectures. Unless we know or hear from an ARM user, I would recommend to play safe and only distribute it on amd64 for this release. Have a nic

Bug#1023230: [Debian-med-packaging] Bug#1023230: t-coffee breaks libbio-tools-run-alignment-tcoffee-perl autopkgtest: test times out after 2:47 hours

ink that t-coffee never worked on ARM. It built, but never worked. The simplest would be to distribute it only on amd64. See https://bugs.debian.org/631249 Have a nice day, Charles -- Charles Plessy Nagahama, Yomitan, Okinawa, Japan Debian Med packaging team http

Bug#1011048: firmware-nonfree: Fails to build without linux-support but linux-support isn't listed in Build-Depends

Package: firmware-nonfree Version: 20210818 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: genpfa...@gmail.com Dear Maintainer, While trying to backport firmware-nonfree/unstable in a bullseye amd64 schroot: user@host:~/

Bug#996569: getmail6 naming issues

s to be done from > upstream so that it is consistent in all other distros and pypi. Please > discuss that with Roland, the getmail6 upstream maintainer. As I have said, he obstinately refuses any name change, claiming equal rights to the name I have built up for 23 years. I'm

Bug#996569: getmail6 naming issues

f people who submitted patches *which currently do nothing except kill support for Python < 2.7*. > 2) The previous Debian maintainers have also requested Charles to do > the python3 development in open so that the effort is not duplicated. I do not currently use a public forge for getmail

Bug#996569: OT: Roland Puntaier / "getmail6" drama

Sudip Mukherjee wrote: > > Marking this bug as serious and the binary packages should be removed > in the next 30 days. Thank you. Charles -- ------ Charles Cazabon Software, consulting, and services

Bug#983471: rspamd should depend libjs-jquery

y.min.js is in libjs-jquery package, rspamd should depend on it. Sincerly, Jean Charles Delépine -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (901, 'testing'), (500, 'stable'), (90, 'unstable') Architecture: amd64 (x86_64)

Bug#981420: libglib2.0-0: gnome-keyring unable to unlock login keyring

ffected or this "security hardening" could break other GNOME/MATE parts? dbus-x11 is a strict dependency of mate-session-manager/gnome-session-bin, while dbus-user-session is not even suggested... -- Best Regards, Charles Malaheenee

Bug#981420: libglib2.0-0: gnome-keyring unable to unlock login keyring

rt981420dbus, no bug) Jan 31 18:39:09 big-pc gnome-keyring-daemon[905]: The Secret Service was already initialized Jan 31 18:39:09 big-pc gnome-keyring-daemon[905]: The SSH agent was already initialized Jan 31 18:39:09 big-pc gnome-keyring-daemon[905]: The PKCS#11 component was already initialized Hope this helps. -- Best Regards, Charles Malaheenee

Bug#955567: kalgebra: Output is always blank

d then restarting kalgebra (without logging out) with no change. I see nothing interesting in .xsession-errors or kalgebra's output Charles

Bug#978131: qemu-system-x86: Segfault when starting a VM

5 19 bb 3b 00 48 8d 3d Initially I thought it is because of the kernel, because last week it worked (that's why the kernel is 5.9.0-4-amd64). I can do more test if needed. Best regards, Charles -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (990, &#

Bug#969261: cyrus-common: bumping to debhelper 13 needs usind dh_installtmpfiles

d" mechanism is currently only used by systemd. Without this file cyrus can't start on a fresh install and can't reboot on an old one. Sincerly, Jean Charles Delépine -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (901, 'testing

Bug#955567: kalgebra: Output is always blank

Package: kalgebra Version: 4:17.08.3-2 Severity: grave Justification: renders package unusable Dear Maintainer, KAlgebra shows nothing in its output screen. This only applies to the algebraic displays, the graphs and dictionary tabs seem to work fine. Reproduce: Enter any equation into the input

Bug#946850: [Debian-med-packaging] Bug#946850: last-align ftbfs on non-x86 architectures

email feedback; at the moment I have not. Have a nice day ! --- Charles

Bug#946850: LAST build fails on non-amd64 platforms.

find portability bugs such as this one). What would you prefer ? Have a nice day, Charles -- Charles Plessy Akano, Uruma, Okinawa, Japan Debian Med packaging team http://www.debian.org/devel/debian-med Tooting from work, https://mastodon.techn

Bug#931529: Acknowledgement (gnome: Session locking does not possible)

Hi, The problem was solved after delete ~/.config/ directory. Best regards, Charles Le 07/07/2019 à 10:39, Debian Bug Tracking System a écrit : > Thank you for filing a new Bug report with Debian. > > You can follow progress on this Bug here: 931529: > https://bugs.debian

Bug#931529: gnome : session freezed when I've tried to lock it

Hi, Today when I've tried to lock my session, my system has totaly freeze. I've needed to halt system from power button. Best regards, Charles signature.asc Description: OpenPGP digital signature

Bug#931529: gnome : session lost after hibernation

Hi, When battery level is very low, my laptop goes into hibernation. When I resuming after hibernation, my session is lost. I enter my password and I'm on a new session, my opened applications are closed. Best regards, Charles signature.asc Description: OpenPGP digital signature

Bug#931585: gnome: Executed applications dock lost

bottom of the screen. Best regards, Charles -- System Information: Debian Release: 10.0   APT prefers stable   APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Loca

Bug#931529: gnome: Session locking does not possible

session, I can't recover my locked session. Best regards, Charles -- System Information: Debian Release: 10.0   APT prefers stable   APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores) Kernel taint flags: T

Bug#890117: Bug #890117 in bedtools marked as pending

. -- Charles Plessy Thu, 14 Feb 2019 22:11:21 +0900 (this message was generated automatically) -- Greetings https://bugs.debian.org/890117

Bug#890117: Bug #890117 in bedtools marked as pending

Control: tag -1 pending Hello, Bug #890117 in bedtools reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/med-team/bedtools/commit/25d45b7a051249d4c482fb5095a9bf45

Bug#890117: bedtools FTBFS on big endian: Tools failing: bamtobed bamtofastq coverage genomecov groupby intersect jaccard map merge multicov negativecontrol

t sure we have evidence that bedtools ever worked properly on big-endian machines. Altogether, this calls for removing bedtools from big endian architectures on Debian at the moment, until Upstream or somebody else steps up to do the porting work. I will fill a request for removal. Have a nice day,

Bug#916279: qemu-system-common

3 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /tmp/apt-dpkg-install-3L8qhF/00-qemu-system-common_1%3a3.1+dfsg-1_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) As temporary solution - rollback to 2.12. -- Best Regard

Bug#883922: Charles,your recent order85219

Amazon: You have no order from me. Is this a scam? Ship nothing. Charge me for nothing. I have not clicked on any links you sent me. Stop this. Donot send me ways to fix - YOU FIX! On Sat, Dec 9, 2017 at 11:00 AM, AmazonOffer wrote: > we would like to Thankyou > > >

Bug#879886: [Debian-med-packaging] Bug#879886: libhts2: libhts2 needs to handle ABI changes

(to be re-added) symbols file. Have a nice day, Charles -- Charles Plessy Debian Med packaging team, http://www.debian.org/devel/debian-med Tsurumi, Kanagawa, Japan

Bug#867588: buildbot: application fails at runtime requiring sqlalchemy-migrate==0.7.2

So far, I have not observed any failures after removing the offending lines ("sqlalchemy >= 0.6, <= 0.7.10" and "sqlalchemy-migrate==0.7.2") from /usr/lib/python2.7/dist-packages/buildbot-0.8.12.egg-info/requires.txt Tested with buildbot 0.8.12-3.2 on stretch, with python-sqlalchemy 1.0.15+ds1-1 a

Bug#861333: r-base: R packages uploaded to Debian before 14 April 2017 that use .C or .Fortran fail to find objects

what has been done until now. Not supporting partial upgrades puts the maintainers of the r-cran and r-bioc packages between the hammer and the anvil. This said, I think that we have made constant progresses over the years, so I do not feel shy saying "not yet" to the Release team again

Bug#859255: binNMU needed for more R packages.

nomicalignments_1.10.0-1 . ANY . -m "Rebuild for R 3.3.3." Note to debian-science: there are also R CRAN packages that fail with R 3.3.3, (r-cran-lubridate, r-cran-spam), but I am not yet sure if a binNMU is enough. Have a nice day, Charles -- Charles Plessy Debian Med packaging team

Bug#858183: binNMU needed for r-bioc- packages broken by R 3.3.3.

ctors_0.12.1-2 . ANY . -m "Rebuild for R 3.3.3." nmu r-bioc-iranges_2.8.1-1-m . ANY . "Rebuild for R 3.3.3." nmu r-bioc-genomicranges_1.26.2-1 . ANY -m "Rebuild for R 3.3.3." Otherwise I can prepare a more extensive list of packages to rebuild. Cheers, -- Charles Plessy Debian Med packaging team, http://www.debian.org/devel/debian-med Tsurumi, Kanagawa, Japan

Bug#857466: marked as done (r-base: CVE-2016-8714: R: Buffer overflow in the LoadEncoding functionality)

sie-backports by updating it to 3.3.3 as well. Have a nice day, -- Charles

Bug#851819: Fail on installation

Hi, I also encountered the same error: ``` Setting up flashplugin-nonfree (1:3.7) ... ERROR: wget failed to download http://people.debian.org/~bartm/flashplugin-nonfree/D5C0FC14/fp.24.0.0.194.sha512.amd64.pgp.asc More information might be available at: http://wiki.debian.org/FlashPlayer ```

Bug#845505: sra-sdk 2.7.0-1 is broken libncbi-vdb2 2.8.0+dfsg-1

day, -- Charles

Bug#831833: [Debian-med-packaging] Bug#831833: Tagged as fixed-upstream - do you intend to upload?

> On Wed, Nov 02, 2016 at 09:03:45PM +0900, Charles Plessy wrote: > > > > I was hoping that Upstream would make a new release with the fix :( > > > > So one would need to check if the following commit would be enough as a > > patch... > > > &

Bug#831833: Tagged as fixed-upstream - do you intend to upload?

check if the following commit would be enough as a patch... https://github.com/arq5x/bedtools2/commit/be2633d4951328264611e4cabc65e12fa8fef1cd I am not sure if I can do it in the short term... Everybody is welcome to be faster than me :) Cheers, -- Charles

Bug#838748: Bug#695327: Patch pending for cloud-init bugs 838748, 780637 and 695327

n the > v0.7.8/master branch on alioth. > > Should I NMU this? Hi Nicolas, may thanks for your help, cloud-init is in collab-maint, so you can also add yourself to Uploaders or mark your upload "team upload" instead of NMUing. Have a nice week-end, -- Charles

Bug#831833: Processed: Re: [Debian-med-packaging] bedtools is marked for autoremoval from testing

Control: tag -1 +sid Le Wed, Jul 27, 2016 at 05:03:05AM +, Debian Bug Tracking System a écrit : > Processing control commands: > > > notfound -1 2.25.0-1 > Bug #831833 [src:bedtools] bedtools groupby broken; will break users > pipelines. > Ignoring request to alter found versions of bug #831

Bug#831833: [Debian-med-packaging] bedtools is marked for autoremoval from testing

break users pipelines. This bug only affects the new upstream release. -- Charles Plessy Debian Med packaging team, http://www.debian.org/devel/debian-med Tsurumi, Kanagawa, Japan

Bug#831833: [Debian-med-packaging] Bug#831833: Command `groupby` broken; will break users pipelines.

for this command are not run by `make test`. (probably by accident) This reminds me that `make test` fails on Debian because of issues with seeded random numbers. It would be a great help if somebody would have time to solve that problem (which may be hard). Cheers, -- Charles

Bug#831833: Command `groupby` broken; will break users pipelines.

, -- Charles

  1   2   3   4   5   >