Re: Please help me fix the build pipeline for apt-listchanges on Salsa, which is failing
On 9/2/24 03:19, Jonathan Kamens wrote: However, the pipeline is still failing, now in reprotest. For example <https://salsa.debian.org/debian/apt-listchanges/-/jobs/6215633#L1650>. Perhaps this is because I haven't yet finalized the changelog for the upcoming release so the trailer line is badly formatted. :shrug: nope. it's failing, because the .deb files are not identical. if you do not want to run reprotest locally and still have a closer look at the differences, you can download the build-artifacts (that is: the .deb files produced by the job at [1]) and inspect them with diffoscope, to see that the files in the tarballs have different timestamps (which obviously makes them non-reproducible. note: this is just general advice, i haven't looked at the *actual* package. gfmasdr IOhannes [1] <https://salsa.debian.org/debian/apt-listchanges/-/jobs/6215633/artifacts/download> OpenPGP_0xB65019C47F7A36F8.asc Description: OpenPGP public key OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1076954: marked as done (general: Kde Wayland flash screen stuck after recent system upgrade.)
Your message dated Thu, 25 Jul 2024 02:49:21 +0200 with message-id and subject line Re: Bug#1076954: general: Kde Wayland flash screen stuck after recent system upgrade. has caused the Debian Bug report #1076954, regarding general: Kde Wayland flash screen stuck after recent system upgrade. to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1076954: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1076954 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: general Severity: important X-Debbugs-Cc: nathanind...@gmail.com Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** Upgrading the system. * What led up to the situation? :Q * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** --- End Message --- --- Begin Message --- This issue is tracked in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1076729 OpenPGP_signature.asc Description: OpenPGP digital signature --- End Message ---
Re: Q: Ubuntu PPA induced version ordering mess.
On 7/3/24 00:28, Alec Leamas wrote: The upstream shall consider adopting 5 digit release version numbering [...] The upstream "shall" not do anything, they are open for discussions but certainly not for dictates. thou shalt not ask if thou wisheth for no answers. (please keep in mind that not all Debian contributors are native speakers so you probably should go easy on the subtle differences between the various subjunctive forms. so unless somebody uses "SHALL (as in RFC-2119)", I would assume that the "shall" is a mere suggestion). If you are able to sell this idea to upstream it would certainly work. I would not try it, it would generate a lot of friction to no use. And at afaict, all suggestions end with that same argument: upstream would resist. which makes the discussion a bit moot. anyhow here's my 2¢: according to you¹, upstream have simply botched their package versioning, which i would consider *a bug*. bugs cause pain. if upstream acknowledges that it *is* a bug, they might be interested in fixing it (even if the fix causes more intermediate pain). if they don't, I personally would go for a workaround like an epoch :-) and some other idea (not very well through through, it's still early in the morning and the caffeine level is low): depending on the ecosystem, you might get away with using an epoch only for the frontend application package. e.g. if there is a meta (binary) package "opencpn" that depends/recommends/... on various opencpn libraries, plugins and what not you could bump the epoch for this package only and have some clever Breaks against the too-high versions, which should eventually force the users to downgrade/re-install the child packages. gdfasmr IOhannes ¹ i looked up <https://launchpad.net/~opencpn/+archive/ubuntu/opencpn/+packages> and did not see any problematic package versions (i probably did not look long enough). so which (actual) package/version is this about? OpenPGP_0xB65019C47F7A36F8.asc Description: OpenPGP public key OpenPGP_signature.asc Description: OpenPGP digital signature
Processed: reassign 1074176 to www.debian.org, user www.debian....@release.debian.org, usertagging 1074176
Processing commands for cont...@bugs.debian.org: > # How is this a "general" bug? > reassign 1074176 www.debian.org Bug #1074176 [general] packages.debian.org: allow seeing files Bug reassigned from package 'general' to 'www.debian.org'. Ignoring request to alter found versions of bug #1074176 to the same values previously set Ignoring request to alter fixed versions of bug #1074176 to the same values previously set > user www.debian@release.debian.org Setting user to www.debian@release.debian.org (was a...@adam-barratt.org.uk). > usertags 1074176 + packages There were no usertags set. Usertags are now: packages. > thanks Stopping processing here. Please contact me if you need assistance. -- 1074176: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074176 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1072491: marked as done (Dead keys stopped working in unspecified environment)
Your message dated Fri, 07 Jun 2024 22:18:08 +0200 with message-id and subject line Re: Bug#1072491: Dead keys stopped working in unspecified environment has caused the Debian Bug report #1072491, regarding Dead keys stopped working in unspecified environment to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1072491: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072491 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libglib2.0-0t64 Version: 2.80.2-2 Severity: important Dear Maintainer, Exactly some bug as https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070745 appears once again. -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (600, 'unstable'), (500, 'unstable-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.8.12-amd64 (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libglib2.0-0t64 depends on: ii libc6 2.38-12 ii libffi8 3.4.6-1 ii libmount1 2.40.1-4 ii libpcre2-8-0 10.42-4+b1 ii libselinux1 3.5-2+b2 ii zlib1g1:1.3.dfsg+really1.3.1-1 Versions of packages libglib2.0-0t64 recommends: ii libglib2.0-data 2.80.2-2 ii shared-mime-info 2.4-5 ii xdg-user-dirs 0.18-1 Versions of packages libglib2.0-0t64 suggests: pn low-memory-monitor -- no debconf information This mail was virus scanned and spam checked before delivery. This mail is also DKIM signed. See header dkim-signature. --- End Message --- --- Begin Message --- Closing then. Am 7. Juni 2024 22:01:56 MESZ schrieb Michael Rasmussen : >Conclusion: My Cinnamon DE using my old user must have gone haywire >somehow so I have created a new user and therefore this bug can be >closed with solution 'works here, must be user error' ;-) -- Sent from /e/ OS on Fairphone3--- End Message ---
Processed: Re: Bug#1072491: Dead keys stopped working in unspecified environment
Processing control commands: > retitle -1 Dead keys stopped working in unspecified environment Bug #1072491 [libglib2.0-0t64] libglib2.0-0t64: Dead keys stopped working, again! Changed Bug title to 'Dead keys stopped working in unspecified environment' from 'libglib2.0-0t64: Dead keys stopped working, again!'. > reassign -1 general Bug #1072491 [libglib2.0-0t64] Dead keys stopped working in unspecified environment Bug reassigned from package 'libglib2.0-0t64' to 'general'. No longer marked as found in versions glib2.0/2.80.2-2. Ignoring request to alter fixed versions of bug #1072491 to the same values previously set -- 1072491: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072491 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1071126: Info received (Bug#1071126: ITP: battinfo -- cli tool & nim-lang library to query battery info for GNU/Linux)
Thank you for the additional information you have supplied regarding this Bug report. This is an automatically generated reply to let you know your message has been received. Your message is being forwarded to the package maintainers and other interested parties for their attention; they will reply in due course. Your message has been sent to the package maintainer(s): w...@debian.org Prasanna Venkadesh If you wish to submit further information on this problem, please send it to 1071...@bugs.debian.org. Please do not send mail to ow...@bugs.debian.org unless you wish to report a problem with the Bug-tracking system. -- 1071126: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071126 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1071126: Info received (Bug#1071126: ITP: battinfo -- cli tool & nim-lang library to query battery info for GNU/Linux)
Thank you for the additional information you have supplied regarding this Bug report. This is an automatically generated reply to let you know your message has been received. Your message is being forwarded to the package maintainers and other interested parties for their attention; they will reply in due course. Your message has been sent to the package maintainer(s): w...@debian.org Prasanna Venkadesh If you wish to submit further information on this problem, please send it to 1071...@bugs.debian.org. Please do not send mail to ow...@bugs.debian.org unless you wish to report a problem with the Bug-tracking system. -- 1071126: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071126 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1070829: ITP: wprs -- rootless remote desktop access for remote Wayland and x11 applications like xpra
Package: wnpp Subject: ITP: wprs -- rootless remote desktop access for remote Wayland and X11 applications like xpra X-Debbugs-Cc: debian-devel@lists.debian.org Owner: Yifei Zhan Severity: wishlist * Package name: wprs Version : 0.1.0 Upstream Contact: Nicolas Avrutin * URL : https://github.com/wayland-transpositor/wprs * License : Apache 2.0 Programming Lang: Rust Description : rootless remote desktop access for remote Wayland (and X11, via XWayland) applications like xpra wprs implements rootless remote desktop access for remote Wayland (and X11, via XWayland) applications with supports for session resumption (running applications will survive wprsc disconnection and later reconnection and wprsc restarts). Currently only the the Core and XDG shell protocols are implemented and hardware rendering/dmabuf support is not yet implemented. Generally, wprs will aim to support as many protocols as feasible, it's a question of time and prioritization.
Bug#1070800: ITP: evremap -- keyboard input remapper for Linux/Wayland systems
Subject: ITP: evremap -- keyboard input remapper for Linux/Wayland systems Package: wnpp X-Debbugs-Cc: debian-devel@lists.debian.org Owner: Yifei Zhan Severity: wishlist * Package name: evremap Version : 0.1.0 Upstream Author : Wez Furlong * URL : https://github.com/wez/evremap * License : MIT Programming Lang: Rust Description : keyboard input remapper for Linux/Wayland systems evremap works by grabbing exclusive access to an input device and maintaining a model of the keys that are pressed. It then applies your remapping configuration to produce the effective set of pressed keys and emits appropriate changes to a virtual output device. Because evremap targets the evdev layer of libinput, its remapping is effective system-wide: in Wayland, X11 and the linux console. (^ from project readme) It works well on my machines and supports more complex mapping (e.g. dual role key based on tapping/holding and M <-> N mapping (F3 -> Ctrl-K / Shift-K -> F5)) while maintaining a simple configure syntax.
Bug#1065810: Info received (New appointments for the Debian Technical Committee: csmall)
Thank you for the additional information you have supplied regarding this Bug report. This is an automatically generated reply to let you know your message has been received. Your message is being forwarded to the package maintainers and other interested parties for their attention; they will reply in due course. Your message has been sent to the package maintainer(s): Technical Committee If you wish to submit further information on this problem, please send it to 1065...@bugs.debian.org. Please do not send mail to ow...@bugs.debian.org unless you wish to report a problem with the Bug-tracking system. -- 1065810: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065810 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1068778: marked as done (geoclue and gpsd are running by default (they aren't needed and could be used for location tracking))
Your message dated Wed, 24 Apr 2024 16:32:20 +0200 (CEST) with message-id <1ffdb551-a9e9-7361-b524-31847de3c...@sourcepole.ch> and subject line Re: geoclue and gpsd are running by default (they aren't needed and could be used for location tracking) has caused the Debian Bug report #1068778, regarding geoclue and gpsd are running by default (they aren't needed and could be used for location tracking) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1068778: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068778 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: general I wondered why Debian comes with geoclue-2.0 and gpsd running by default (which could be used for location tracking). Please do not install them by default or if you really must, please do not make them autostart. At most it could be useful for a few users if it was installed but not enabled and not running by default (so just an option one could enable in the configs or which could be enabled by the user through a prompt). If it's running by default this also means that after upgrades it could be running again. This is a privacy issue, an undesired bloat service that requires to spend time to remove it, and a larger attack surface even if there was a proper and vulnerability-free permissions-management for GPS-location-access. --- End Message --- --- Begin Message --- Hi mYnDstrEAm, mYnDstrEAm wrote on Wed, 10 Apr 2024 22:54:04 +: Package: general I wondered why Debian comes with geoclue-2.0 and gpsd running by default (which could be used for location tracking). Please do not install them by default or if you really must, please do not make them autostart. At most it could be useful for a few users if it was installed but not enabled and not running by default (so just an option one could enable in the configs or which could be enabled by the user through a prompt). If it's running by default this also means that after upgrades it could be running again. This is a privacy issue, an undesired bloat service that requires to spend time to remove it, and a larger attack surface even if there was a proper and vulnerability-free permissions-management for GPS-location-access. I'm closing this bugreport for the following reasons: 1. You write: "geoclue-2.0 and gpsd running by default". On my system: $ ps faux|grep gpsd|grep -v grep $ -> that means that gpsd is not running by default and we do not have fix that. 2. You write: "geoclue-2.0 and gpsd running by default". On my system: $ ps faux|grep geoclue|grep -v grep me 3089 0.0 0.0 234036 3100 ?Sl Apr20 0:00 \_ /usr/libexec/geoclue-2.0/demos/agent $ apt-cache rdepends geoclue-2.0 --installed geoclue-2.0 Reverse Depends: redshift libqt5positioning5 -> please check on your system, who depends on geoclue-2.0 and if you think it is necessary, create a wishlist bug report on those packages that you have installed that depend on geoclue-2.0. I might note, that the geoclue-2.0 dependency is not hard for the packages I have installed, but a recommendation, so that I can still deinstall geoclue-2.0 if I think I do not want it: $ ( dpkg -s redshift ; dpkg -s libqt5positioning5 ) | grep geoclue-2.0 Recommends: geoclue-2.0 Recommends: geoclue-2.0 3. I assume that packages depending on geoclue-2.0 will possibly be able to get some info on where you are. In the case of redshift that'll probably be used to adjust your display brightness/color. That isn't privacy invasive as far as I can see. So again no problem -> no bug. In the same vein you could argue "packages should not use the network, because that can invade your privacy, since they *can* send some info about you and your device to somewhere". So yes, of course they can, but the question is *do they*? If they don't then there's no breach of privacy. 4. When you assigning bug reports against "general" then it's very likely your bug report will be ignored, because nobody maintains a "general" package and thus nobody feels very much responsible for bugreports against the "general" pseudo package. Thanks, *t--- End Message ---
Processed: reassigning bugreport to kernel
Processing commands for cont...@bugs.debian.org: > reassign 1069735 linux-image-6.6.15-amd64 Bug #1069735 [general] general: atlantic driver doesn't work on thinkpad Bug reassigned from package 'general' to 'linux-image-6.6.15-amd64'. Ignoring request to alter found versions of bug #1069735 to the same values previously set Ignoring request to alter fixed versions of bug #1069735 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 1069735: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069735 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1068823: (No Subject)
Processing control commands: > reassign -1 src:apt Bug #1068823 [general] Stepwise Debian upgrade to enable systems with little free storage space to upgrade without breaks due to "No space left on device" Bug reassigned from package 'general' to 'src:apt'. Ignoring request to alter found versions of bug #1068823 to the same values previously set Ignoring request to alter fixed versions of bug #1068823 to the same values previously set > severity -1 wishlist Bug #1068823 [src:apt] Stepwise Debian upgrade to enable systems with little free storage space to upgrade without breaks due to "No space left on device" Severity set to 'wishlist' from 'normal' -- 1068823: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068823 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: closing 1028557
Processing commands for cont...@bugs.debian.org: > close 1028557 Bug #1028557 [general] general: The Debian Social Contract (DSC) is meaningless Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1028557: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028557 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1064903: ITP: slm -- school library management
Package: wnpp Severity: wishlist Owner: Georges Khaznadar X-Debbugs-Cc: debian-devel@lists.debian.org * Package name: slm Version : 0.4 Upstream Contact: Georges Khaznadar * URL : https://salsa.debian.org/georgesk/slm0 * License : GPL-3+ Programming Lang: Python, Javascript Description : school library management SLM stands for "school library management". It provides a web service useful for teams who lend school books to students. Here are some features: . - defining constants for the school, like name, logo, manager's name - creating a catalogue of available books - managing the inventory of books, each one identified by a unique barcode - importing lists of students, with their optional curricula - lending quickly a few books to every student, with the help of a barcode reader - managing the book returns, with the help of a barcode reader - replying to some request, like "whom is this book?", list of students which still owe books, list of students who have no book lended, and so on. - every web page comes with a contextual help I am using SML in my school's cooperative association to lend school books to students, and already packaged extra dependencies which were not part of Debian previously: python3-pylabels, node-html5-qrcode, python3-trml2pdf. This package's source is maintained in Salsa: https://salsa.debian.org/debian/slm
Processed: closing 1061518
Processing commands for cont...@bugs.debian.org:
> close 1061518
Bug #1061518 {Done: Salvatore Bonaccorso } [general] (no
subject)
Bug 1061518 is already marked as done; not doing anything.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1061518: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061518
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: closing 1061512
Processing commands for cont...@bugs.debian.org: > close 1061512 Bug #1061512 [general] 4 Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1061512: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061512 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: closing 1061518
Processing commands for cont...@bugs.debian.org: > close 1061518 Bug #1061518 [general] (no subject) Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1061518: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061518 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Re: Limited security support for Go/Rust? Re ssh3
On 1/16/24 17:20, Simon Josefsson wrote: it seems that many people think that "Built-Using" can be used to express static linking (including yours truly, even though i *know* that it is meant for license compliance only). which makes me wonder: probably we should have an additional field that expresses such static linking (and therefore would trigger a rebuild when the dependency changes). or we could finally accept that many¹ people would just use "Built-Using" for this anyhow, and explicitly allow such use. Would that be better or worse than making *.buildinfo files more generally available and required? Buildinfo files appears to have some traction already, and it seems like they could help address the same problem. my understanding¹ of buildinfo files is, that they collect the exact information against which packages a given binary package was built. but that doesn't really help us with static linking (or license compliance as in Built-Using), as the binary might just use whatever parts of it's build-dependencies, and do e.g. dynamic linking or just run a given tool (e.g. 'ninja'). we can already track the required dependencies with Build-Depends, so we could also just rebuild all reverse dependencies. but afaiu, we want a more specific approach to be able to rebuild only those packages that would actually benefit from that (as opposed to a full archive rebuild because 'make' was uploaded for a policy version bump). gfmdasr IOhannes ¹ which is pretty dim on this topic; so do not hesitate to enlighten me OpenPGP_0xB65019C47F7A36F8.asc Description: OpenPGP public key OpenPGP_signature.asc Description: OpenPGP digital signature
Re: Limited security support for Go/Rust? Re ssh3
On 1/16/24 13:56, Jérémy Lal wrote: As Built-Using is for license compliance only, no? See https://www.debian.org/doc/debian-policy/ch-relationships.html#additional-source-packages-used-to-build-the-binary-built-using Indeed, thanks for the link. it seems that many people think that "Built-Using" can be used to express static linking (including yours truly, even though i *know* that it is meant for license compliance only). which makes me wonder: probably we should have an additional field that expresses such static linking (and therefore would trigger a rebuild when the dependency changes). or we could finally accept that many¹ people would just use "Built-Using" for this anyhow, and explicitly allow such use. dmas IOhannes ¹ i have the gut feeling i am not alone :-) but i don't have any numbers OpenPGP_0xB65019C47F7A36F8.asc Description: OpenPGP public key OpenPGP_signature.asc Description: OpenPGP digital signature
Message with no Package: tag cannot be processed! (ITP: golang-github-calmh-incontainer -- determine if we're running inside a container or not.)
Your message didn't have a Package: line at the very first line of the mail body (part of the pseudo-header), or didn't have a Package: line at all. Unfortunatly, this means that your message has been ignored completely. Without this information we are unable to categorise or otherwise deal with your problem report. Please _resubmit_ your report to sub...@bugs.debian.org and tell us which package the report is for. For help, check out https://www.debian.org/Bugs/Reporting. Your message was dated Tue, 2 Jan 2024 15:46:05 +0100 and had message-id and subject ITP: golang-github-calmh-incontainer -- determine if we're running inside a container or not.. The complete text of it is attached to this message. If you need any assistance or explanation please contact ow...@bugs.debian.org and include the the attached message. If you didn't send the attached message (spam was sent forging your from address), we apologize; please disregard this message. -- -1: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=-1 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- debian...@lists.debian.org Package: wnpp Severity: wishlist Owner: Félix Sipma * Package name: golang-github-calmh-incontainer Version : 0.0~git20221224.b3e71b1-1 Upstream Author : Jakob Borg * URL : https://github.com/calmh/incontainer * License : MIT Programming Lang: Go Description : determine if we're running inside a container or not. Loosely based on (https://github.com/pitkley/in-container) for Rust. Needed by recent versions of Syncthing. -- Félix signature.asc Description: PGP signature --- End Message ---
Message with no Package: tag cannot be processed! (ITP: golang-github-calmh-incontainer)
Your message didn't have a Package: line at the very first line of the mail body (part of the pseudo-header), or didn't have a Package: line at all. Unfortunatly, this means that your message has been ignored completely. Without this information we are unable to categorise or otherwise deal with your problem report. Please _resubmit_ your report to sub...@bugs.debian.org and tell us which package the report is for. For help, check out https://www.debian.org/Bugs/Reporting. Your message was dated Tue, 2 Jan 2024 15:21:44 +0100 and had message-id and subject ITP: golang-github-calmh-incontainer. The complete text of it is attached to this message. If you need any assistance or explanation please contact ow...@bugs.debian.org and include the the attached message. If you didn't send the attached message (spam was sent forging your from address), we apologize; please disregard this message. -- -1: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=-1 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- debian...@lists.debian.org Package: wnpp Severity: wishlist Owner: Félix Sipma * Package name: golang-github-calmh-incontainer Version : 0.0~git20221224.b3e71b1-1 Upstream Author : Jakob Borg * URL : https://github.com/calmh/incontainer * License : MIT Programming Lang: Go Description : determine if we're running inside a container or not. Loosely based on (https://github.com/pitkley/in-container) for Rust. Needed by recent versions of Syncthing. -- Félix signature.asc Description: PGP signature --- End Message ---
Bug#1058937: Info received (/usr-move: Do we support upgrades without apt?)
Thank you for the additional information you have supplied regarding this Bug report. This is an automatically generated reply to let you know your message has been received. Your message is being forwarded to the package maintainers and other interested parties for their attention; they will reply in due course. Your message has been sent to the package maintainer(s): Debian kernel team If you wish to submit further information on this problem, please send it to 1058...@bugs.debian.org. Please do not send mail to ow...@bugs.debian.org unless you wish to report a problem with the Bug-tracking system. -- 1058937: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058937 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: retitle 1056357 to general: on hppa, command line of any program invocation is limited to less than 3544 bytes
Processing commands for cont...@bugs.debian.org: > retitle 1056357 general: on hppa, command line of any program invocation is > limited to less than 3544 bytes Bug #1056357 [general] general: on hppa, command line of any program invocation is Changed Bug title to 'general: on hppa, command line of any program invocation is limited to less than 3544 bytes' from 'general: on hppa, command line of any program invocation is'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1056357: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056357 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1056357: general: on hppa, command line of any program invocation is limited to less than 3544 bytes
Processing control commands: > retitle -1 general: on hppa, command line of any program invocation is Bug #1056357 [general] general: Command line of any program invocation is limited to less than 3544 bytes Changed Bug title to 'general: on hppa, command line of any program invocation is' from 'general: Command line of any program invocation is limited to less than 3544 bytes'. -- 1056357: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056357 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Re: What would help the most?
Hi, I have the feeling, that this is some kind of semi-AI generated chat. I think we should stop it now. Imre, Nagy 2023. 10. 30. 2:29 keltezéssel, Lukasz Szybalski írta: On Sat, Oct 28, 2023 at 3:41 AM Paul Wise wrote: On Fri, 2023-10-27 at 14:00 -0500, Lukasz Szybalski wrote: > What is the minimum most value thing that would > help YOU accomplish your goals for Debian ? Check out this page if no-one gives anything more specific: https://www.debian.org/intro/help Paul, Marc, Andrey Thanks for replying. To narrow it down: *Vision of Debian:* Create a free operating system, freely available for everyone. *Goal:* Coding and Maintaining Packages <https://www.debian.org/intro/help> Testing and Bug Squashing <https://www.debian.org/intro/help> /In these 2 goals:/ What is the minimum most valuable thing that would help YOU accomplish your goals for Debian ? Thanks Lucas
Bug#1053664: marked as done (general: Plugging or unplugging USB device sometimes causes the system to lockup.)
Your message dated Wed, 18 Oct 2023 12:57:27 +0200 (CEST) with message-id <436febb7-775-290-45a4-7a98acfb...@sourcepole.ch> and subject line closing, not enough infos has caused the Debian Bug report #1053664, regarding general: Plugging or unplugging USB device sometimes causes the system to lockup. to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1053664: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053664 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: general Severity: important X-Debbugs-Cc: cmclr...@gmail.com Dear Maintainer, plugging in a FTDI device caused lockup ( keyboard,mouse unresponsive) . Also unplugging and replugging wireless lan caused same condition. --- End Message --- --- Begin Message --- Hello clinton, your bug reports doesn't contain enough informations to be actionable. Therefore I am closing it. Please contact one of the Debian support channels to sort your problem out and possibly add useful informations to the bug report. See https://www.debian.org/support for support options. Thanks, *t--- End Message ---
Bug#1051401: marked as done (general: PATH variable definition in debian 12)
Your message dated Tue, 19 Sep 2023 08:35:05 +0200 (CEST) with message-id <10e42929-f4db-dc2d-ea8-cb9a8cfaf...@sourcepole.ch> and subject line closing bug report has caused the Debian Bug report #1051401, regarding general: PATH variable definition in debian 12 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1051401: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051401 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: general Severity: normal X-Debbugs-Cc: robinhodges...@yahoo.co.uk Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** Had a problem when I installed debian 12 onto my PC. As root the reboot and shutdown commands wouldnt work. I have solved this on my PC by including the following into the root .bashrc file export PATH=$PATH:/usr/local/sbin:/usr/sbin:/sbin Thank you --- End Message --- --- Begin Message --- I am closing this bug report since there was no answer a simple follow up question [1] in nearly two weeks. *t [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051401#10--- End Message ---
Processed: Re: Bug#1051086: general: networking misconfigured and unusable after bookworm upgrade
Processing control commands: > reassign -1 network-manager Bug #1051086 [general] general: networking misconfigured and unusable after bookworm upgrade Bug reassigned from package 'general' to 'network-manager'. Ignoring request to alter found versions of bug #1051086 to the same values previously set Ignoring request to alter fixed versions of bug #1051086 to the same values previously set -- 1051086: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051086 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Re: How do you cause a re-run of autopkgtests?
On 7/21/23 12:57, G. Branden Robinson wrote: Hi folks, But I see no mechanism for interacting with autopkgtests to force them to re-run due to the remedy of a defect in the test harness itself. How is this to be done? you mean, apart from clicking on the ♻ retry icon? (you probably have to be authenticated in order to even see these icons) Should some automated mechanism for achieving this be added, and if so, where? https://ci.debian.net/api/doc mgfdsar IOhannes
Processed: reassign 1038627 to pipewire
Processing commands for cont...@bugs.debian.org: > reassign 1038627 pipewire Bug #1038627 [general] general: Various applications log PipeWire-related errors on a Bookworm system using PulseAudio. Bug reassigned from package 'general' to 'pipewire'. Ignoring request to alter found versions of bug #1038627 to the same values previously set Ignoring request to alter fixed versions of bug #1038627 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 1038627: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038627 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1037968: marked as done (unauthorised background updates)
Your message dated Wed, 14 Jun 2023 23:55:39 + with message-id and subject line Re: Bug#1037968: unauthorised background updates has caused the Debian Bug report #1037968, regarding unauthorised background updates to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1037968: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037968 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: general Severity: serious X-Debbugs-Cc: slimshad...@zohomail.eu without my approval the latest kernel update was applied and the most surprising thing is that no downloaded files are present in the cache folder. all happens in the background without my knowledge. only found out during reboot. same for all the other updates like firefox but they not that serious. again updates set to manual. --- End Message --- --- Begin Message --- On Thu, Jun 15, 2023 at 02:46:38AM +0530, slimshady wrote: > without my approval the latest kernel update was applied and the most > surprising thing is that no downloaded files are present in the cache folder. > all happens in the background without my knowledge. only found out during > reboot. same for all the other updates like firefox but they not that serious. > again updates set to manual. closing. -- cheers, Holger ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ holger@(debian|reproducible-builds|layer-acht).org ⢿⡄⠘⠷⠚⠋⠀ OpenPGP: B8BF54137B09D35CF026FE9D 091AB856069AAA1C ⠈⠳⣄ Why Did We Ban Smoking Indoors When We Could Have Just All Washed Our Hands More? (@TheVertlartnic) signature.asc Description: PGP signature --- End Message ---
Bug#1035883: marked as done (general: TMOUT and autologout are set to 3600, but logout occurs much earlier)
Your message dated Wed, 14 Jun 2023 17:48:02 +0530 (IST) with message-id <185761594.515418.1686745082...@office.mailbox.org> and subject line Re: Bug#1035883: Close out this report, please has caused the Debian Bug report #1035883, regarding general: TMOUT and autologout are set to 3600, but logout occurs much earlier to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1035883: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035883 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: general Severity: minor Dear Maintainer, This bug report is a rather minor issue, but it is an inconvenience for me. I realize that auto logout is a general security feature, but in my case, I have a secrure environment where only my wife and I have access to my computer. I strong prefer to NOT have my computer auto logout for 10 hours, allowing me to leave my computer in the evening and return to it in the morning without haveing to log on. I have the enrivonment variables TMOUT and autologout both set to 36000, or 10 hours, but these are not honored by the system. Thank you. Jim Anderson -- System Information: Distributor ID: Bunsenlabs Description:BunsenLabs GNU/Linux 10.5 (Lithium) Release:10.5 Codename: buster Architecture: x86_64 Kernel: Linux 4.19.0-23-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled --- End Message --- --- Begin Message --- On 06/14/2023 1:27 AM IST Jim Anderson wrote: > I have looked at my other debian computers and the TMOUT setting works > on them. I'm not sure why TMOUT does not work on my one computer, but it > is not worth the effort to try to debug this issue for one system. > Please consider this issue closed. Closing. Best, Nilesh--- End Message ---
Bug#1035110: Info received (Bug#1035110: ITP: drminfo -- Small utility to dump info about DRM devices)
Thank you for the additional information you have supplied regarding this Bug report. This is an automatically generated reply to let you know your message has been received. Your message is being forwarded to the package maintainers and other interested parties for their attention; they will reply in due course. Your message has been sent to the package maintainer(s): w...@debian.org Rodrigo Siqueira If you wish to submit further information on this problem, please send it to 1035...@bugs.debian.org. Please do not send mail to ow...@bugs.debian.org unless you wish to report a problem with the Bug-tracking system. -- 1035110: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035110 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: reassign bug to kernel
Processing commands for cont...@bugs.debian.org: > reassign 1033149 linux Bug #1033149 [general] general: debian 11 fails to hibernate when RAM usage above 7GB Bug reassigned from package 'general' to 'linux'. Ignoring request to alter found versions of bug #1033149 to the same values previously set Ignoring request to alter fixed versions of bug #1033149 to the same values previously set > End of message, stopping processing here. Please contact me if you need assistance. -- 1033149: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033149 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1030280: general: General non-recognized errors (im novice) after the installation: drivers, battery, booting errors...
Processing control commands: > reassign -1 installation-reports Bug #1030280 [general] general: General non-recognized errors (im novice) after the installation: drivers, battery, booting errors... Bug reassigned from package 'general' to 'installation-reports'. Ignoring request to alter found versions of bug #1030280 to the same values previously set Ignoring request to alter fixed versions of bug #1030280 to the same values previously set > tag -1 moreinfo Bug #1030280 [installation-reports] general: General non-recognized errors (im novice) after the installation: drivers, battery, booting errors... Added tag(s) moreinfo. -- 1030280: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030280 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1030189: Let regular users know need to put non-free-firmware in sources.list
Processing control commands: > reassign -1 release-notes Bug #1030189 [general] Let regular users know need to put non-free-firmware in sources.list Bug reassigned from package 'general' to 'release-notes'. Ignoring request to alter found versions of bug #1030189 to the same values previously set Ignoring request to alter fixed versions of bug #1030189 to the same values previously set -- 1030189: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030189 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Re: Bug#1026087: ITP: distribution-gpg-keys -- GPG keys by various Linux distributions
Hi! On Thu, Dec 15, 2022 at 03:12:21PM +0100, Guillem Jover wrote: > The project name talks about gpg keys, but those are really OpenPGP > keys (or even better, certificates). I've asked upstream to rename the > project to avoid this common confusion. So you might want to wait until > that's settled to avoid multiple trips over NEW. > > <https://github.com/xsuchy/distribution-gpg-keys/issues/76> Thank you very much! I liked this issue on github and waiting for upstream reply. > > (If this project is also intended to only cover RPM-based distributions, > as Adam brought up, you might want to further ask them to make that clear > from the project name, say rpm-distribution-openpgp-keys or similar. But > in any case regardless of the intended target use, it still seems like a > very generic name which can be easily confused for a package that would > be needed for Debian, or derivatives.) Mainly for mock we just need keys for rpm-based distributions/repositories. On the other way we have extrepo-offline-data package where are repository keys for 3rd party debian repositories. Also maybe it's better to have extern PGP keys on one place. What do you think about it? Best Regards, Juri Grabowski
Bug#1025739: Info received (Is an autogenerated configure shell script non-editable source)
Thank you for the additional information you have supplied regarding this Bug report. This is an automatically generated reply to let you know your message has been received. Your message is being forwarded to the package maintainers and other interested parties for their attention; they will reply in due course. Your message has been sent to the package maintainer(s): Debian Med Packaging Team If you wish to submit further information on this problem, please send it to 1025...@bugs.debian.org. Please do not send mail to ow...@bugs.debian.org unless you wish to report a problem with the Bug-tracking system. -- 1025739: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025739 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1024542: marked as done (general: Add Budgie-Desktop to the software selection menu list)
Your message dated Mon, 21 Nov 2022 09:14:13 +0100 with message-id and subject line Re: Bug#1024542: general: Add Budgie-Desktop to the software selection menu list has caused the Debian Bug report #1024542, regarding general: Add Budgie-Desktop to the software selection menu list to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1024542: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024542 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: general Severity: normal Dear Maintainers, I have filed a bug report, but I got a reply that it was posted at the wrong section. Therefore, this is a reminder for the previous report. best regards. Quated as following: Hi, Green (2022-11-21): > Under the Debian 11 (bullseye), Debian-installer does not give an > option for Budgie Desktop in the software selection list. > > Please add Budgie Desktop for convenience of users on the next release > of Debian 11 (bookwarm). Closing this bug report, as #1024531 has the right metadata: tasksel is responsible for the desktop environment selection. Cheers, -- Cyril Brulebois (k...@debian.org)<https://debamax.com/> D-I release manager -- Release team member -- Freelance Consultant --- End Message --- --- Begin Message --- On Mon, Nov 21, 2022 at 04:31:45PM +0900, Green wrote: > Package: general > Severity: normal > > Dear Maintainers, > > I have filed a bug report, but I got a reply that it was posted at the wrong > section. The bug (#1024529) has been closed because it was assigned to the wrong package, as Cyril mentioned: this is not a topic for the debian-installer but for the tasksel package and as there is already a bug from you on tasksel (#1024531), Cyril closed the misfiled one. > Therefore, this is a reminder for the previous report. As there is already a appropiate bug report, closing this one as duplicate. People will follow up on the original bug, no need to file multiple ones. -- Cheers, tobi--- End Message ---
Bug#1023778: Info received (Bug#1023778: TMPDIR behaviour in maintainer scripts [was: Re: Bug#1023778: mysql-server-8.0: fails to restart on upgrade with libpam-tmpdir])
Thank you for the additional information you have supplied regarding this Bug report. This is an automatically generated reply to let you know your message has been received. Your message is being forwarded to the package maintainers and other interested parties for their attention; they will reply in due course. Your message has been sent to the package maintainer(s): Debian MySQL Maintainers If you wish to submit further information on this problem, please send it to 1023...@bugs.debian.org. Please do not send mail to ow...@bugs.debian.org unless you wish to report a problem with the Bug-tracking system. -- 1023778: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023778 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1022994: Info received (Bug#1023778: TMPDIR behaviour in maintainer scripts [was: Re: Bug#1023778: mysql-server-8.0: fails to restart on upgrade with libpam-tmpdir])
Thank you for the additional information you have supplied regarding this Bug report. This is an automatically generated reply to let you know your message has been received. Your message is being forwarded to the package maintainers and other interested parties for their attention; they will reply in due course. Your message has been sent to the package maintainer(s): Debian MySQL Maintainers If you wish to submit further information on this problem, please send it to 1022...@bugs.debian.org. Please do not send mail to ow...@bugs.debian.org unless you wish to report a problem with the Bug-tracking system. -- 1022994: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022994 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#903158: Info received (Bug#903158: Multi-Arch: foreign and -dbgsym: too weak dependency)
Thank you for the additional information you have supplied regarding this Bug report. This is an automatically generated reply to let you know your message has been received. Your message is being forwarded to the package maintainers and other interested parties for their attention; they will reply in due course. Your message has been sent to the package maintainer(s): Debhelper Maintainers If you wish to submit further information on this problem, please send it to 903...@bugs.debian.org. Please do not send mail to ow...@bugs.debian.org unless you wish to report a problem with the Bug-tracking system. -- 903158: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903158 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1020295: ITP: dh-puredata -- debhelper addon for building Pd externals
Package: wnpp Severity: wishlist Owner: IOhannes m zmölnig (Debian/GNU) X-Debbugs-Cc: debian-devel@lists.debian.org * Package name: dh-puredata Version : 1 Upstream Author : IOhannes m zmölnig * URL : * https://salsa.debian.org/multimedia-team/pd/dh-puredata * License : GPL3+ Programming Lang: Perl Description : debhelper addon for building Pd externals This package provides the 'pd-lib-builder' Debhelper-sequence for streamlining the process of creating Debian packages of pd-lib-builder based externals for the Pure Data computer music language. I intend to maintain this under the multimedia-team umbrella, along with the other Pure Data related packages.
Bug#1018891: marked as done (general: Can't install fans on msi laptop due to missing ec_sys kernel. Command prompt modprobe ec_sys write_support=1, I get error: FATAL: Module ec_sys not found in dire
Your message dated Tue, 13 Sep 2022 21:33:03 +0200 with message-id and subject line Re: Bug#1018891: general: Can't install fans on msi laptop due to missing ec_sys kernel. Command prompt modprobe ec_sys write_support=1, I get error: FATAL: Module ec_sys not found in directory /lib/modules/5.10.0-17-amd64 has caused the Debian Bug report #1018891, regarding general: Can't install fans on msi laptop due to missing ec_sys kernel. Command prompt modprobe ec_sys write_support=1, I get error: FATAL: Module ec_sys not found in directory /lib/modules/5.10.0-17-amd64 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1018891: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1018891 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: general Severity: normal X-Debbugs-Cc: velmory...@gmail.com Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** --- End Message --- --- Begin Message --- On Thu, 2022-09-01 at 18:43 +0300, Psyho786 wrote: > Package: general > Severity: normal > X-Debbugs-Cc: velmory...@gmail.com > > Dear Maintainer, > > *** Reporter, please consider answering these questions, where appropriate *** > >* What led up to the situation? >* What exactly did you do (or not do) that was effective (or > ineffective)? >* What was the outcome of this action? >* What outcome did you expect instead? > > *** End of the template - remove these template lines *** > We intentionally do not enable this debug driver. Ben. -- Ben Hutchings Unix is many things to many people, but it's never been everything to anybody. signature.asc Description: This is a digitally signed message part --- End Message ---
Processed (with 2 errors): Re: [gsfonts] Fonts include copyrighted adobe fragment all rights reserved
Processing commands for cont...@bugs.debian.org:
> unblock 694320 by 694308
Bug #694320 {Done: Fabian Greffrath } [gsfonts] [gsfonts]
Fonts include copyrighted adobe fragment all right reserved
Bug #694321 {Done: Fabian Greffrath } [gsfonts] [gsfonts]
Fonts include copyrighted adobe fragment all right reserved
694320 was blocked by: 694308
694320 was not blocking any bugs.
Removed blocking bug(s) of 694320: 694308
694321 was blocked by: 694308
694321 was not blocking any bugs.
Removed blocking bug(s) of 694321: 694308
> The fonts files in fonts-urw-core35 are not built by fontforge anymore.
Unknown command or malformed arguments to command.
> - Fabian
Unknown command or malformed arguments to command.
>
End of message, stopping processing here.
Please contact me if you need assistance.
--
694320: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=694320
694321: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=694321
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1014029: marked as done (invisible malicious unicode in source code - detection and prevention)
Your message dated Thu, 30 Jun 2022 10:22:58 +0200 with message-id <20220630082257.dfe35x2cghs7a...@gpm.stappers.nl> and subject line Too broad has caused the Debian Bug report #1014029, regarding invisible malicious unicode in source code - detection and prevention to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1014029: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014029 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: general Severity: normal Quote https://trojansource.codes > Some Vulnerabilities are Invisible > Rather than inserting logical bugs, adversaries can attack the encoding of > source code files to inject vulnerabilities. > > These adversarial encodings produce no visual artifacts. > The trick is to use Unicode control characters to reorder tokens in source code at the encoding level. > These visually reordered tokens can be used to display logic that, while semantically correct, diverges from the logic presented by the logical ordering of source code tokens. > Compilers and interpreters adhere to the logical ordering of source code, not the visual order. > The attack is to use control characters embedded in comments and strings to > reorder source code characters in a way that changes its logic. > Adversaries can leverage this deception to commit vulnerabilities into code > that will not be seen by human reviewers. > This attack is particularly powerful within the context of software supply > chains. > If an adversary successfully commits targeted vulnerabilities into open > source code by deceiving human reviewers, downstream software will likely > inherit the vulnerability. > The defense - > Compilers, interpreters, and build pipelines supporting Unicode should throw errors or warnings for unterminated bidirectional control characters in comments or string literals, and for identifiers with mixed-script confusable characters. - > Language specifications should formally disallow unterminated bidirectional control characters in comments and string literals. - > Code editors and repository frontends should make bidirectional control characters and mixed-script confusable characters perceptible with visual symbols or warnings. additional ideas to protect from this: - **check if potential existing compromises:** scan all source code for existing unicode - **educate existing and future source code reviewers:** add a source code reviewer policy which existing and future reviewers need to acknowledge that they understand the issue. - **remove as much unicode from source code as possible**: by reducing the amount of unicode in source code, audits for malicious unicode with automated tools gets simpler. If possible, if unicode is considered essential, instead of writing `®` when required it should be encoded as `®`. - **local check by reviewer:** document tools that source code reviewers could/should use to scan future contributions for malicious unicode - **lintian check:** a lintian test that notifies when unicode is included in the source code. - **build scripts / CI scripts:** should check if there is unicode in any files except in opt-in expected files defines in a list. If there is any unexpected unicode in unexpected files, the build should error out. - **scan upstream projects source code**: check if these are compromised by malicious unicode. - **notify upstream projects**: these might not be aware of this issue and already compromised by malicious unicode. how to check example: grep_args="--exclude=changelog.upstream --exclude-dir=.git --binary-files=without-match --recursive --color=auto -P -n" LC_ALL=C grep $grep_args '[^\x00-\x7F]' LC_ALL=C grep $grep_args "[^[:ascii:]]" A few other tools might be desirable in case grep can ever be tricked to miss anything. --- End Message --- --- Begin Message --- Hi, This email will close this way too broad bugreport. Having this BR closed will prevent further drain of human energy. Those who think "but it important" do I recomment to take smaller steps in going forward. Regards Geert Stappers DD -- Silence is hard to parse signature.asc Description: PGP signature --- End Message ---
Re: Package uploads silently discarded: how to investigate?
On 6/27/22 03:08, Scott Kitterman wrote: On June 27, 2022 1:06:10 AM UTC, Russ Allbery wrote: Ben Finney writes: My guess is that this is something to do with an update to the signing GnuPG key expiry date. I can get into that in a different thread if needed. The trouble is, I can only guess, because there are no messages from anything in the Debian archive telling me what went wrong. My recollection is that if the signature on the upload is invalid, we intentionally delete the upload with no notice (because we have no confirmed knowledge of who to notify). It's possible that my information is dated, though That's correct. as i've wondered myself about this in the past (not for some time though, since i no longer update my keys just-in-time): would it be possible to list reasons for (silent) discards on a prominent page? (e.g. somewhere on https://ftp-master.d.o¹). i see that ftp://ftp.upload.debian.org/pub/UploadQueue/ contains a README that says: > Only known Debian developers can upload here. Uploads have to be > signed by PGP keys in the Debian keyring. Files not meeting this > criterion or files not mentioned in a .changes file will be removed > after some time. which hints at the current behaviour (but does not make it explicit). and to be honest: i think that some random file on an ftp-server is not very visible in the first place. chrome and firefox both have ditched ftp support, which reduces the options to just *browse* the ftp-directory to...what? filezilla (shudder) and ftp on the cmdline (my beard is now white enough to get homely feelings when i encounter such a thing; but really?)² gfmsar IOhannes ¹ i guess https://ftp-master.debian.org/#rejections would be a good starting place, although this currently only speaks about explicit *rejects* , and silently discards the notion of silent *discards*. ² is there some special reason to not make the UploadQueue available via https *also*? at least i haven't found a browseable link anywhere...
Processed: Re: Bug#1012227: general: CPU usage is 50% or higher with WebKitWebProcess
Processing control commands: > reassign -1 libwebkit2gtk-4.0-37 Bug #1012227 [general] general: CPU usage is 50% or higher with WebKitWebProcess Bug reassigned from package 'general' to 'libwebkit2gtk-4.0-37'. Ignoring request to alter found versions of bug #1012227 to the same values previously set Ignoring request to alter fixed versions of bug #1012227 to the same values previously set > retitle -1 webkitgtk: CPU usage is 50% or higher with WebKitWebProcess Bug #1012227 [libwebkit2gtk-4.0-37] general: CPU usage is 50% or higher with WebKitWebProcess Changed Bug title to 'webkitgtk: CPU usage is 50% or higher with WebKitWebProcess' from 'general: CPU usage is 50% or higher with WebKitWebProcess'. -- 1012227: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012227 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: reassign 1008652 to mirrors
Processing commands for cont...@bugs.debian.org: > reassign 1008652 mirrors Bug #1008652 [general] mirrors must support also HTTPS in order to be considered official Bug reassigned from package 'general' to 'mirrors'. Ignoring request to alter found versions of bug #1008652 to the same values previously set Ignoring request to alter fixed versions of bug #1008652 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 1008652: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008652 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: mirrors must support also HTTPS in order to be considered official
Processing control commands: > retitle -1 mirrors must support also HTTPS in order to be considered official Bug #1008652 [general] mirrors must support HTTPS in order to be considered official Changed Bug title to 'mirrors must support also HTTPS in order to be considered official' from 'mirrors must support HTTPS in order to be considered official'. -- 1008652: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008652 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1005339: marked as done (general: usbmouse+keyboard lag on closing the lid or issuing xrandr --output eDP-1 --off)
Your message dated Wed, 2 Mar 2022 10:01:53 +0100 (CET) with message-id and subject line reporter has solved the issue has caused the Debian Bug report #1005339, regarding general: usbmouse+keyboard lag on closing the lid or issuing xrandr --output eDP-1 --off to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1005339: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005339 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: general Severity: normal Dear Maintainer, * What led up to the situation? with an external monitor attached, closing the lid or issuing xrandr --output eDP-1 --off to disable the laptop screen. * What exactly did you do (or not do) that was effective (or ineffective)? close laptop lid or issue above xrandr command * What was the outcome of this action? the usbmouse and keyboard lag * What outcome did you expect instead? normal behaviour of usbmouse and keyboard Note: By issuing xrandr --auto usbmouse+keyboard return to normal, but the laptop screen is on, even if lid is closed Linux 5.10.0-11-amd64 #1 SMP Debian 5.10.92-1 (2022-01-18) x86_64 GNU/Linux Debian 11 bullseye -- Mario Natiello --- End Message --- --- Begin Message --- See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005339#10--- End Message ---
Bug#1005271: ITP: csound-plugins -- plugin collection for Csound
Package: wnpp Severity: wishlist Owner: IOhannes m zmölnig (Debian/GNU) X-Debbugs-Cc: debian-devel@lists.debian.org * Package name: csound-plugins Version : 1.0.2 Upstream Author : Csound Developers * URL : https://github.com/csound/plugins * License : LGPL Programming Lang: C, C++ Csound is a sound and music synthesis system. Drawing from over 450 signal processing modules, it can be used to model virtually any synthesizer or multi-effect processor. It can work either in real-time or as a compiler. . Csound is to sound synthesis as C is to programming. . This package contains additional plugins. Upstream has split their repository, so now add-ons for the main "Csound" package have a different repo and release cycle. To not lose those plugins in Debian, packaging the new repo is required as well. I intend to maintain this under the multimedia-team umbrella, along with the other csound related packages. gfmdasr IOhannes
Processed: reassing bug to correct package
Processing commands for cont...@bugs.debian.org: > reassign 1002573 util-linux Bug #1002573 [general] general: fstrim, 2 errors Bug reassigned from package 'general' to 'util-linux'. Ignoring request to alter found versions of bug #1002573 to the same values previously set Ignoring request to alter fixed versions of bug #1002573 to the same values previously set > End of message, stopping processing here. Please contact me if you need assistance. -- 1002573: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002573 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#999493: ITP: pika-backup -- simple backups based on borg
Package: wnpp Severity: wishlist Owner: Debian Borg Collective X-Debbugs-Cc: debian-devel@lists.debian.org * Package name: pika-backup Version : 0.3.5 Upstream Author : Sophie Herold * URL : https://apps.gnome.org/app/org.gnome.World.PikaBackup/ https://wiki.gnome.org/Apps/PikaBackup https://gitlab.gnome.org/World/pika-backup * License : GPL-3 Programming Lang: Rust Description : simple backups based on borg Doing backups the easy way. Plugin your USB drive and let the Pika do the rest for you. Features * Setup new backup repositories or uses existing ones * Create backups locally and remote * Save time and disk space because Pika Backup does not need to copy known data again * Encrypt your backups * List created archives and browse through their contents * Recover files or folders via your file browser Pika Backup is powered by the well-tested borg-backup software. Limitations Currently, scheduled backups are not supported. Excluding files from a backup via regular expressions and alike is not implemented yet. Pika Backup is designed to save your personal data and does not support complete system recovery.
Processed: Re: Bug#998689: general: Screen with wrong resolution at boot and marked as disconnected after suspend
Processing control commands: > reassign -1 src:linux 5.10.70-1 Bug #998689 [general] general: Screen with wrong resolution at boot and marked as disconnected after suspend Bug reassigned from package 'general' to 'src:linux'. Ignoring request to alter found versions of bug #998689 to the same values previously set Ignoring request to alter fixed versions of bug #998689 to the same values previously set Bug #998689 [src:linux] general: Screen with wrong resolution at boot and marked as disconnected after suspend Marked as found in versions linux/5.10.70-1. -- 998689: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998689 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Re: Lintian and Dpkg's :any multiarch acceptor
On 11/3/21 23:34, Felix Lechner wrote: 1. Did anyone find the latest Lintian versions (2.109.0 and up) confusing as to whether the :any should be included? The material you would have encountered includes both the context offered by Lintian (the extra information after the tag) and any relevant tag descriptions. being the one who initially triggered #995981 by blindly following advice of lintian (yes i know: *never* blindly follow lintian's advise), i think i can say that i indeed found the description of the "rules-require-build-prerequisite" tag highly confusing. in general i think tag descriptions should ony use "machine-parsable advice" if the machine-parsable is meant to be used as-is, and use human language in all other cases. that is: rather than using a string like "python3:any | python3-all:any | python3-dev:any | python3-all-dev:any | dh-sequence-python3" (which looks very much like code) use someting like "the package should probably build depend on one of python3-dev:any or dh-sequence-python3 or [...]". the point i'm trying to make is not about the correctness of the advice itself, but that an explanation that looks like a code-example is probably going to be understood as such. so if the text is not to be copy and pasted into code, it shouldn't look like tit could. fmdst IOhannes OpenPGP_signature Description: OpenPGP digital signature
Processed: Re: Bug#996000: general: System does not boot with second monitor attached
Processing control commands: > Severity -1 normal Bug #996000 [general] general: System does not boot with second monitor attached Severity set to 'normal' from 'important' -- 996000: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996000 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: closing 993488
Processing commands for cont...@bugs.debian.org: > reassign 993488 general Bug #993488 [security-tracker] security-tracker: Revoked group permission on a user continue to take effect on all existing processes and sessions Bug reassigned from package 'security-tracker' to 'general'. Ignoring request to alter found versions of bug #993488 to the same values previously set Ignoring request to alter fixed versions of bug #993488 to the same values previously set > tags 993488 + wontfix Bug #993488 [general] security-tracker: Revoked group permission on a user continue to take effect on all existing processes and sessions Added tag(s) wontfix. > close 993488 Bug #993488 [general] security-tracker: Revoked group permission on a user continue to take effect on all existing processes and sessions Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 993488: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993488 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#992692: general: Use https for {deb,security}.debian.org by default
Processing control commands:
> tags -1 + moreinfo
Bug #992692 [general] general: Use https for {deb,security}.debian.org by
default
Added tag(s) moreinfo.
--
992692: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=992692
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
[bts-link] source package general
# # bts-link upstream status pull for source package general # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # https://bts-link-team.pages.debian.net/bts-link/ # user debian-bts-l...@lists.debian.org # remote status report for #992503 (http://bugs.debian.org/992503) # Bug title: [RFC] [meta][WiP] URL specification with IPv6 zone identifiers # * https://github.com/whatwg/url/issues/392 # * remote status changed: (?) -> closed # * closed upstream tags 992503 + fixed-upstream usertags 992503 + status-closed thanks
Processed: [bts-link] source package general
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package general > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org Setting user to debian-bts-l...@lists.debian.org (was debian-bts-l...@lists.debian.org). > # remote status report for #992503 (http://bugs.debian.org/992503) > # Bug title: [RFC] [meta][WiP] URL specification with IPv6 zone identifiers > # * https://github.com/whatwg/url/issues/392 > # * remote status changed: (?) -> closed > # * closed upstream > tags 992503 + fixed-upstream Bug #992503 [general] [RFC] [meta][WiP] URL specification with IPv6 zone identifiers Added tag(s) fixed-upstream. > usertags 992503 + status-closed There were no usertags set. Usertags are now: status-closed. > thanks Stopping processing here. Please contact me if you need assistance. -- 992503: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=992503 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#992237: marked as done (general: dpkg broken, so no security updates available)
Your message dated Mon, 16 Aug 2021 10:49:44 +0200 with message-id <878s11wz87@hands.com> and subject line Re: Bug#992237: general: dpkg broken, so no security updates available has caused the Debian Bug report #992237, regarding general: dpkg broken, so no security updates available to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 992237: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=992237 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: general Severity: important Dear Maintainer, see below: Get:1 http://security.debian.org/debian-security bullseye-security InRelease [44.1 kB] Hit:2 http://deb.debian.org/debian bullseye InRelease Hit:3 http://deb.debian.org/debian bullseye-updates InRelease Hit:4 http://deb.debian.org/debian bullseye-backports InRelease Fetched 44.1 kB in 0s (93.7 kB/s) Reading package lists... Done Reading package lists... Done Building dependency tree... Done Reading state information... Done Calculating upgrade... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. root@wp:~# dpkg -S /bin dpkg-query: no path found matching pattern /bin root@wp:~# dpkg -l root@wp:~# After upgrading to stable, dpkg does not know anything about installed packages. This means that security patches will not be installed. --- End Message --- --- Begin Message --- Olaf Zaplinski writes: > Package: general > Severity: important > > Dear Maintainer, > > see below: > > > Get:1 http://security.debian.org/debian-security bullseye-security InRelease > [44.1 kB] > Hit:2 http://deb.debian.org/debian bullseye InRelease > Hit:3 http://deb.debian.org/debian bullseye-updates InRelease > Hit:4 http://deb.debian.org/debian bullseye-backports InRelease > Fetched 44.1 kB in 0s (93.7 kB/s) > Reading package lists... Done > Reading package lists... Done > Building dependency tree... Done > Reading state information... Done > Calculating upgrade... Done > 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. > root@wp:~# dpkg -S /bin > dpkg-query: no path found matching pattern /bin > root@wp:~# dpkg -l > root@wp:~# > > After upgrading to stable, dpkg does not know anything about installed > packages. This means that security patches will not be installed. > I'm afraid you're going to have to do rather more research about what you did there, because if I look at one of the many systems I've upgraded I see: =-=-=- root@sheikh:~# apt update Hit:1 http://debian.hands.com/debian bullseye InRelease Hit:2 http://security.debian.org bullseye-security InRelease Reading package lists... Done Building dependency tree... Done Reading state information... Done All packages are up to date. root@sheikh:~# dpkg -S /bin kbd, tar, psmisc, net-tools, login, bash, busybox, console-setup, systemd, systemd-container, util-linux, startpar, mount, cpio, coreutils, udev, debianutils, sysvinit-utils, procps, nano, iputils-ping, netcat-traditional, netcat-openbsd, bzip2, sed, dash, base-files, grep, fuse, hostname, gzip, iproute2, kmod: /bin root@sheikh:~# dpkg -l | wc -l 1149 root@sheikh:~# dpkg -l | head Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++--==--== ii acpi 1.7-1.1 amd64displays information on ACPI devices ii adduser 3.118 all add and remove users and groups ii adwaita-icon-theme 3.38.0-1 all default icon theme of GNOME ii alsa-topology-conf 1.2.4-1 all ALSA topology configuration files ii alsa-ucm-conf1.2.4-2 all ALSA Use Case Manager configuration files root@sheikh:~# =-=-=- That being the case there must be something specific about your setup that has caused your issue, rather than a general bug in Debia
Re: Gitlab support for Debian repositories (Was: Regarding the new "Debian User Repository")
Le lun. 5 juil. 2021 à 11:46, Holger Levsen a écrit : > > Hi Mathieu, Hi Holger, > On Mon, Jul 05, 2021 at 10:37:31AM +0200, Mathieu Parent (Debian) wrote: > > [2]: https://docs.gitlab.com/ee/user/packages/debian_repository/ > > thanks, this looks nice and simple! Thanks. > Do you have plans to support publishing builds only if they've produced > bit by bit identical results on several builders? IOW, do you plan to > support reproducible builds? :) There is no specific support for reproducible builds. Currently, buildinfo files can be uploaded and are kept, with the metadata stored in the DB. but nothing is done yet with those. But reproducibility can be tested in GItlab jobs, before the upload. Cheers, -- Mathieu Parent
Re: Gitlab support for Debian repositories (Was: Regarding the new "Debian User Repository")
Le sam. 3 juil. 2021 à 12:11, Simon McVittie a écrit : > > On Fri, 02 Jul 2021 at 20:04:45 +0200, Mathieu Parent wrote: > > On a related topic, I'm currently developing support for Debian > > repositories in Gitlab (and transitively Salsa). > > That's great news - being able to build packages in CI and make the results > easily installable seems like a big step forward, particularly for > fast-moving non-core packages. > > Given the other discussion in this thread, perhaps it should be labelled > "apt repositories" or ".deb repositories" or something else more > distro-neutral, to avoid implying Debian approval or official status, > while also making it obvious that if you want to build and publish > packages for Ubuntu or Linux Mint or some other Debian derivative, > this is also the right feature for those? I'm not sure. "Debian repository" is the official term for the format, as documented in the wiki [1]. And here, Debian is not in the product name. [1]; https://wiki.debian.org/DebianRepository/Format As the doc is now live [2],any ambiguous usage of the Debian term can be fixed, but I don't see any. [2]: https://docs.gitlab.com/ee/user/packages/debian_repository/ -- Mathieu Parent
Processed: Re: Bug#989370 closed by Chris Hofstaedtler (Re: Bug#989370: general: In bonding network configuration, hwaddress crashes networking service, fails to restart)
Processing control commands:
> reopen 989370
Bug #989370 {Done: Chris Hofstaedtler } [general] general: In
bonding network configuration, hwaddress crashes networking service, fails to
restart
Bug reopened
Ignoring request to alter fixed versions of bug #989370 to the same values
previously set
> reassign 989370 ifupdown
Bug #989370 [general] general: In bonding network configuration, hwaddress
crashes networking service, fails to restart
Bug reassigned from package 'general' to 'ifupdown'.
Ignoring request to alter found versions of bug #989370 to the same values
previously set
Ignoring request to alter fixed versions of bug #989370 to the same values
previously set
--
989370: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989370
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#989370: marked as done (general: In bonding network configuration, hwaddress crashes networking service, fails to restart)
Your message dated Thu, 3 Jun 2021 13:39:37 +0200 with message-id <20210603113937.6kc5bgn5vkzqx...@percival.namespace.at> and subject line Re: Bug#989370: general: In bonding network configuration, hwaddress crashes networking service, fails to restart has caused the Debian Bug report #989370, regarding general: In bonding network configuration, hwaddress crashes networking service, fails to restart to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 989370: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989370 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: general Severity: important Dear Maintainer, * What led up to the situation? Created a network configuration via /etc/network/interfacess file method for a single ethernet NIC, i.e. eth0, and WiFi adapter, i.e. wlan0. Both had customized MAC addresses via the 'hwaddress' option. This configuration worked as expected with no issues. * What exactly did you do (or not do) that was effective (or ineffective)? Changed the configuration to a bonding configuration adding bond0 interface, and changing the eth0 and wlan0 configuration to work as slaves under a simple active-backup bonding configuration. * What was the outcome of this action? On reboot or systemctl restart networking, the networking service fails, and network connectivity is broken, nonfunctional. ONLY AFTER REMOVING 'hwaddress' option under bond0 interface configuration, did networking start as expected. Did not expect the 'hwaddress' option to working on slave interfaces, but it should have worked on the bond, i.e. bond0 interface. Nowhere in the documentation, that I have found as yet, is the 'hwaddress' feature excluded from a bonding configuration. * What outcome did you expect instead? MAC address set per 'hwaddress' option of bond0 interface, at a minimum, set as expected, and networking being functional. Fail to understand why hwaddress option fails on bond0 interface when bond0 configuration is functional without said option being used. At a minimum, if eth0 interface as primary has a 'hwaddress' option set, the bond0 configuration should accept it. But a better implementation would be for the bond0 interface to accept use of the hwaddress option. Which apparently is not the case now. -- System Information: Distributor ID: Raspbian Description:Raspbian GNU/Linux 10 (buster) Release:10 Codename: buster Architecture: armv6l Kernel: Linux 5.10.17+ Kernel taint flags: TAINT_CRAP Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) --- End Message --- --- Begin Message --- > Distributor ID: Raspbian > Description: Raspbian GNU/Linux 10 (buster) > Architecture: armv6l > Kernel: Linux 5.10.17+ > Kernel taint flags: TAINT_CRAP Please do not file bugs that happen on derivatives against Debian, as we do not know about their changes. Instead, please use the derivative (Raspbian) bug tracker. If you can reproduce this on a current, supported Debian release, please file a bug against the correct Debian package (i.e. not "general"). Best, Chris--- End Message ---
Processed: reassign 987798 to src:linux
Processing commands for cont...@bugs.debian.org: > reassign 987798 src:linux Bug #987798 [general] general: TG3 fails without repair when applying high load to NIC Bug reassigned from package 'general' to 'src:linux'. Ignoring request to alter found versions of bug #987798 to the same values previously set Ignoring request to alter fixed versions of bug #987798 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 987798: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=987798 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: reassign 986292 to command-not-found
Processing commands for cont...@bugs.debian.org: > reassign 986292 command-not-found Bug #986292 [general] general: sqlite3 problem when a command is not available Bug reassigned from package 'general' to 'command-not-found'. Ignoring request to alter found versions of bug #986292 to the same values previously set Ignoring request to alter fixed versions of bug #986292 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 986292: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986292 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: closing 964115
Processing commands for cont...@bugs.debian.org: > close 964115 Bug #964115 [general] end user support request: video playback bullseye Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 964115: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964115 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: closing 842854
Processing commands for cont...@bugs.debian.org: > close 842854 Bug #842854 [general] general: Lenovo X220T rotate screen key works in Debian8/Gnome but not KDE Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 842854: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=842854 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#985833: General: when searching repos I get an error message
Processing control commands: > reassign -1 command-not-found Bug #985833 [general] General: when searching repos I get an error message Bug reassigned from package 'general' to 'command-not-found'. Ignoring request to alter found versions of bug #985833 to the same values previously set Ignoring request to alter fixed versions of bug #985833 to the same values previously set > tags -1 + wontfix Bug #985833 [command-not-found] General: when searching repos I get an error message Added tag(s) wontfix. -- 985833: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985833 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: end user support request: video playback bullseye
Processing commands for cont...@bugs.debian.org: > retitle 964115 end user support request: video playback bullseye Bug #964115 [general] Web browser video playback broken in bullseye Changed Bug title to 'end user support request: video playback bullseye' from 'Web browser video playback broken in bullseye'. > severity 964115 wishlist Bug #964115 [general] end user support request: video playback bullseye Severity set to 'wishlist' from 'important' > tags 964115 unreproducible moreinfo Bug #964115 [general] end user support request: video playback bullseye Added tag(s) unreproducible and moreinfo. > stop Stopping processing here. Please contact me if you need assistance. -- 964115: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964115 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#985272: ITP: golang-github-huandu-go-assert -- Magic assert macros for Go.
Package: wnpp
Severity: wishlist
Owner: deb...@thola.io
* Package name: golang-github-huandu-go-assert
Version : 1.1.5-1
Upstream Author : Huan Du
* URL : https://github.com/huandu/go-assert
* License : Expat
Programming Lang: Go
Description : Magic assert macros for Go.
Package assert - Magic assert macros for Go Go Go Doc
(https://pkg.go.dev/github.com/huandu/go-assert)
.
Package assert provides developer a way to assert expression and output
useful contextual information automatically when a case fails. With this
package, we can focus on writing test code without worrying about how
to print lots of verbose debug information for debug.
.
Here is a quick sample.
.
```go import "github.com/huandu/go-assert"
.
func TestSomething(t *testing.T) {
str := Foo(42) assert.Assert(t, str == "expected")
// This case fails with following message. // // Assertion failed:
// str == "expected" // Referenced variables are assigned
in following statements: // str := Foo(42)
.
} ``` Import Use go get to install this package.
.
shell go get github.com/huandu/go-assert
.
.
Current stable version is v1.*. Old versions tagged by v0.* are obsoleted.
UsageAssertion methods If we just want to use functions like Assert,
Equal or NotEqual, it's recommended to import this package as ..
.
```go import "github.com/huandu/go-assert"
.
func TestSomething(t *testing.T) {
a, b := 1, 2 assert.Assert(t, a > b)
// This case fails with message: // Assertion failed: // a > b
.
}
.
func TestAssertEquality(t *testing.T) {
assert.Equal(t, map[string]int{
"foo": 1, "bar": -2,
}, map[string]int{
"bar": -2, "foo": 1,
})
// This case fails with message: // Assertion failed: // The
value of following expression should equal. // [1] map[string]int{
// "foo": 1, // "bar": -2, // } // [2]
map[string]int{ // "bar": -2, // "foo": 1, //
} // Values: // [1] -> (map[string]int)map[bar:-2 foo:1] //
[2] -> (map[string]int)map[bar:-2 foo:1]
.
} ``` Advanced assertion wrapper: type A If we want more controls on
assertion, it's recommended to wrap t in an A.
.
There are lots of useful assert methods implemented in A. • Assert
(https://godoc.org/github.com/huandu/go-assert#A.Assert)/Eqaul
(https://godoc.org/github.com/huandu/go-assert#A.Equal)/NotEqual
(https://godoc.org/github.com/huandu/go-assert#A.NotEqual):
Basic assertion methods.• NilError
(https://godoc.org/github.com/huandu/go-assert#A.NilError)/NonNilError
(https://godoc.org/github.com/huandu/go-assert#A.NonNilError):
Test if a func/method returns expected error.• Use
(https://godoc.org/github.com/huandu/go-assert#A.Use): Track variables. If
any assert method fails, all variables tracked by A and related in assert
method will be printed out automatically in assertion message. Here is
a sample to demonstrate how to use A#Use to print related variables in
assertion message.
.
```go import "github.com/huandu/go-assert"
.
func TestSomething(t *testing.T) {
a := assert.New(t) v1 := 123 v2 := []string{"wrong", "right"} v3 :=
v2[0] v4 := "not related" a.Use(&v1, &v2, &v3, &v4)
a.Assert(v1 == 123 && v3 == "right")
.
// This case fails with following message. // // Assertion failed:
// v1 == 123 && v3 == "right" // Referenced variables are
assigned in following statements: // v1 := 123 // v3 :=
v2[0] // Related variables: // v1 -> (int)123 // v2 ->
([]string)[wrong right] // v3 -> (string)wrong
.
}
Bug#985268: ITP: golang-github-huandu-go-sqlbuilder -- A flexible and powerful SQL string builder library plus a zero-config ORM.
Package: wnpp
Severity: wishlist
Owner: deb...@thola.io
* Package name: golang-github-huandu-go-sqlbuilder
Version : 1.12.0-1
Upstream Author : Huan Du
* URL : https://github.com/huandu/go-sqlbuilder
* License : Expat
Programming Lang: Go
Description : A flexible and powerful SQL string builder library plus a
zero-config ORM.
SQL builder for Go Go (https://github.com/huandu/go-sqlbuilder/actions)
GoDoc (https://pkg.go.dev/github.com/huandu/go-sqlbuilder) Go Report
(https://goreportcard.com/report/github.com/huandu/go-sqlbuilder) Coverage
Status (https://coveralls.io/github/huandu/go-sqlbuilder?branch=master)
• Install (#install)• Usage (#usage) • Basic
usage (#basic-usage)• Pre-defined SQL builders
(#pre-defined-sql-builders)• Build SQL for MySQL, PostgreSQL or
SQLite (#build-sql-for-mysql--postgresql-or-sqlite)• Using Struct
as a light weight ORM (#using--struct--as-a-light-weight-orm)•
Nested SQL (#nested-sql)• Use sql.Named in a builder
(#use--sqlnamed--in-a-builder)• Argument modifiers
(#argument-modifiers)• Freestyle builder (#freestyle-builder)• Using
special syntax to build SQL (#using-special-syntax-to-build-sql)•
Interpolate args in the sql (#interpolate--args--in-the--sql-)• FAQ
(#faq) • What's the difference between this package and squirrel
(#what-s-the-difference-between-this-package-and--squirrel-)• License
(#license) Package sqlbuilder provides a set of flexible and powerful
SQL string builders. The only goal of this package is to build SQL
string with arguments which can be used in DB#Query or DB#Exec defined
in package database/sql. Install Use go get to install this package.
.
shell go get github.com/huandu/go-sqlbuilder
.
UsageBasic usage We can build a SQL really quick with this package.
.
```go sql := sqlbuilder.Select("id", "name").From("demo.user").
Where("status = 1").Limit(10). String()
.
fmt.Println(sql)
.
// Output: // SELECT id, name FROM demo.user WHERE status = 1 LIMIT 10 ```
.
In the most cases, we need to escape all input from user. In this case,
create a builder before starting.
.
```go sb := sqlbuilder.NewSelectBuilder()
.
sb.Select("id", "name", sb.As("COUNT(*)", "c")) sb.From("user")
sb.Where(sb.In("status", 1, 2, 5))
.
sql, args := sb.Build() fmt.Println(sql) fmt.Println(args)
.
// Output: // SELECT id, name, COUNT(*) AS c FROM user WHERE
status IN (?, ?, ?) // [1 2 5] ``` Pre-defined SQL builders
Following builders are implemented right now. API document
and examples are provided in the godoc document. • Struct
(https://pkg.go.dev/github.com/huandu/go-sqlbuilder#Struct):
Builder factory for a struct.• CreateTableBuilder
(https://pkg.go.dev/github.com/huandu/go-sqlbuilder#CreateTableBuilder):
Builder for CREATE TABLE.• SelectBuilder
(https://pkg.go.dev/github.com/huandu/go-sqlbuilder#SelectBuilder):
Builder for SELECT.• InsertBuilder
(https://pkg.go.dev/github.com/huandu/go-sqlbuilder#InsertBuilder):
Builder for INSERT.• UpdateBuilder
(https://pkg.go.dev/github.com/huandu/go-sqlbuilder#UpdateBuilder):
Builder for UPDATE.• DeleteBuilder
(https://pkg.go.dev/github.com/huandu/go-sqlbuilder#DeleteBuilder):
Builder for DELETE.• UnionBuilder
(https://pkg.go.dev/github.com/huandu/go-sqlbuilder#UnionBuilder):
Builder for UNION and UNION ALL.• Buildf
(https://pkg.go.dev/github.com/huandu/go-sqlbuilder#Buildf):
Freestyle builder using fmt.Sprintf-like syntax.• Build
(https://pkg.go.dev/github.com/huandu/go-sqlbuilder#Build): Advanced
freestyle builder using special syntax defined in Args#Compile
(https://pkg.go.dev/github.com/huandu/go-sqlbuilder#Args.Compile).•
BuildNamed
(https://pkg.go.dev/github.com/huandu/go-sqlbuilder#BuildNamed): Advanced
freestyle builder using ${key} to refer the value of a map by key.
There is a method SQL(sql string) implemented by all statement builders
like SelectBuilder. We can use this method to insert any arbitrary SQL
fragment when building a SQL. It's quite useful to build SQL containing
non-standard syntax supported by a OLTP or OLAP system.
.
``go // Build a SQL to create a HIVE table. sql :=
sqlbuilder.CreateTable("users").
SQL("PARTITION BY (year)"). SQL("AS"). SQL(
sqlbuilder.Select("columns[0] id", "columns[1] name", "columns[2]
year").
From("all-users.csv`"). Limit(100). String(),
). String()
.
fmt.Println(sql)
.
// Output: // CREATE TABLE users PARTITION BY (year) AS SELECT columns[0]
id, columns[1] name, columns[2] year FROM all-users.csv LIMIT 100 ```
.
To learn how to use builders, check out examples on GoDoc
(https://pkg.go.dev/github.com/huandu/go-sqlbuilder#pkg-examples).
Build SQL for MySQL, PostgreSQL or SQLite Parameter markers are different
in MySQL, PostgreSQL and SQLite. This package provides some methods to
set the type of markers (we call it "flavor") in all builders.
.
By default, all builders uses DefaultFlavor to build SQL. The defaul
Processed: closing 985100
Processing commands for cont...@bugs.debian.org: > close 985100 Bug #985100 [general] server suspended after installation Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 985100: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985100 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#983523: marked as done (general: some WWW sites no longer work neither in Firefox nor in Chrome)
Your message dated Tue, 09 Mar 2021 10:51:14 +0100 with message-id <87a6rcy7sd@mimuw.edu.pl> and subject line problem no longer reproducible has caused the Debian Bug report #983523, regarding general: some WWW sites no longer work neither in Firefox nor in Chrome to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 983523: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983523 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: general Severity: normal I was angry with my Internet provider because on their site since several weeks the chat was reported as not available. It appeared the chat works all the time in any Windows browser. Today I tried to order some goods by Internet, by I was unable to select the interesting items with a click neither in Firefox nor in Chrome. Again it appeared that it works in any Windows browser. Please reassign as appropriate. Best regards Janusz -- System Information: Debian Release: 10.8 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-14-amd64 (SMP w/12 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled -- , Janusz S. Bien emeryt (emeritus) https://sites.google.com/view/jsbien --- End Message --- --- Begin Message --- Just noticed that the problem vanished. No idea why. Regards Janusz -- , Janusz S. Bien emeryt (emeritus) https://sites.google.com/view/jsbien--- End Message ---
Processed: Re: Bug#982562: general: Storing upstream signatures next to upstream tarballs is problematic
Processing control commands: > block -1 by 876643 Bug #982562 [general] general: Storing upstream signatures next to upstream tarballs is problematic 982562 was not blocked by any bugs. 982562 was not blocking any bugs. Added blocking bug(s) of 982562: 876643 -- 982562: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982562 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: general: Storing upstream signatures next to upstream tarballs is problematic
Processing control commands: > affects -1 ftp.debian.org dpkg-dev Bug #982562 [general] general: Storing upstream signatures next to upstream tarballs is problematic Added indication that 982562 affects ftp.debian.org and dpkg-dev -- 982562: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982562 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#981565: ITP: golang-github-inexio-go-monitoringplugin -- Golang package for writing monitoring check plugins for nagios, icinga2, zabbix, etc.
Package: wnpp
Severity: wishlist
Owner: deb...@thola.io
* Package name: golang-github-inexio-go-monitoringplugin
Version : 0.0~git20201117.ec06ef4-1
Upstream Author : inexio
* URL : https://github.com/inexio/go-monitoringplugin
* License : BSD-2-clause
Programming Lang: Go
Description : Golang package for writing monitoring check plugins for
nagios, icinga2, zabbix, etc.
go-monitoringplugin Go Report Card
(https://goreportcard.com/report/github.com/inexio/go-monitoringplugin)
GitHub license
(https://github.com/inexio/go-monitoringplugin/blob/master/LICENSE)
Description Golang package for writing monitoring check plugins
for nagios (https://www.nagios.org/), icinga2 (https://icinga.com/),
zabbix (https://www.zabbix.com/), checkmk (https://checkmk.com/), etc.
The package complies with the Monitoring Plugins Development Guidelines
(https://www.monitoring-plugins.org/doc/guidelines.html). Example /
Usagepackage main
.
import (
monitoringplugin "github.com/inexio/go-monitoringplugin"
)
.
func main() {
//Creating response with a default ok message that will be
displayed when the checks exits with status ok response :=
monitoringplugin.NewResponse("everything checked!")
.
//Set output delimiter (default is \n) //response.SetOutputDelimiter("
/ ")
.
//updating check plugin status and adding message to the ouput
(status only changes if the new status is worse than the current one)
response.UpdateStatus(monitoringplugin.OK, "something is ok!") //check
status stays ok response.UpdateStatus(monitoringplugin.CRITICAL,
"something else is critical!") //check status updates to critical
response.UpdateStatus(monitoringplugin.WARNING, "something else is
warning!") //check status stays critical, but message will be added
to the output
.
.
//adding performance data err :=
response.AddPerformanceDataPoint(monitoringplugin.NewPerformanceDataPoint("response_time",
10, "s").SetWarn(10).SetCrit(20).SetMin(0)) if err != nil {
//error handling
} err =
response.AddPerformanceDataPoint(monitoringplugin.NewPerformanceDataPoint("memory_usage",
50, "%").SetWarn(80).SetCrit(90).SetMin(0).SetMax(100)) if err !=
nil {
//error handling
}
.
response.OutputAndExit() /* exits program with exit code 2 and
outputs: CRITICAL: something is ok! something else is critical!
something else is warning! | 'response_time'=10s;10;20;0;
'memory_usage'=50%;80;90;0;100 */
}
Re: Making Debian available - patch for webwml
On 1/29/21 1:44 PM, Holger Levsen wrote: Hi Holger, On Thu, Jan 28, 2021 at 10:53:54AM +0100, Holger Wansing wrote: FYI: a patch has been applied in the meantime, adding such hint to nearly all d.o pages, which have links to download images [eg] www.debian.org/distrib/ to make users aware of those images. very cool, thank you very much! I'm still a bit sad we call the non-free images "unofficial" instead of "non-free", but hey, todays presentation is much better than last months already! IOW: I think we should call our non-free images our official non-free images. But still, yay progress! anecdotally, i installed buster on my wife's 13 year old i686 laptop yesterday morning (trying to refurbish it as a home-schooling device). the hardware is obviously pretty old (no x86_64!), but at least that made me hope that the wifi card might work out of the box. being fully aware of this thread (and just to be on the safe side), i checked how easy it was to find a i386 netinstaller images with non-free firmware. i'm sad to say that even though there has been obvious progress on the homepage¹, i failed. to be fair, i did find i386 images including non-free, but apparently only "full installation" ISOs, that (i suspected) wouldn't fit on my already crammed USB-stick. (i've been installing Debian since 1998 or so, and I don't think I ever used anything but the netinstaller. i'd like to keep it that way) of course, once i started the installer, it turned out that non-free firmware was indeed needed for the iwlwifi. so i copied one of the two mentioned firmware files (the other one was missing, so i assumed that the two were just different versions) from my own laptop (running sid) into a firmware/ directory on the USB stick, and started a-new. this time i was not prompted to insert a disk with the missing firmware (so providing the missing firmware was obviously pretty easy), only to find that i still could not connect to my WPA2-protected WiFi. so i just grabbed an old network cable from my bag of stuff, connected my own laptop to the old one, setup internet sharing, and from then it went kind of smoothly (apart from losing connection every other time, so it took a couple of attempts until the base system had been downloaded; but that might be due to the cable, or the rusty eth connector). after a successful installation i enabled non-free, grabbed the firmware-iwlwifi package, and since then everything seems to work splendidly (module that fan, that is making weird noises). fdmsrsa IOhannes ¹ note: i think "the page" (https://get.d.o) changed again since yesterday, and i now have been able to locate i386-netinstall+non-free images (although only after searching the page for "firmware" and then go daringly 3 more appalling pages (that reminded me fondly of ftp-directories and FAQs of yore) OpenPGP_signature Description: OpenPGP digital signature
Bug#977975: marked as done (general: Root does not aknoledge root password)
Your message dated Wed, 23 Dec 2020 20:48:41 +0100 with message-id <8735zwi9ra@hands.com> and subject line Re: Bug#977975: general: Root does not aknoledge root password has caused the Debian Bug report #977975, regarding general: Root does not aknoledge root password to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 977975: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977975 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: general Severity: important Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? I made several netinstalls of Debian Buster 10.7, via Netinst-cd-images. Used eather Graphic or non-graphic, mostly expert install as I have used to make partitions myself. Added to first Debian base item only Mate desktop and System (tools) (the last item). About 3-4 times I chose in install also activate the "Root login", gave the same password to Root as to my ordinary account: as the only user I used 1-digit password, the same digit as ordinary Username login. My internet connection did not fail all the time (lan, 10/10 MBit/s). I used to make separate Boot, Root, Home partitions; Grub on MBR of GPT table, although my PC is EFI-capable (Fujitsu Esprimo d756; Intel 6(5)00; 256 ssd Hynix (all used ones before me for 3-4 years), no signs ever of harware deficiencies. (I am writing the Report on MX Linux install, not Debian.) * What exactly did you do (or not do) that was effective (or ineffective)? After install and reboot I tried to gain root rights: su. Then the Terminal told the password was not right one, and that this incidence would be reported. Also tried to login as Root. Again was always told that the password was not right (one digit!). Yet about in 1(2) install all about the logins were working excellently! Yet then I had missed some other minor things, and did new install, hoping that I eventually had caught the point of my own mistake... Installing Debian in case I did not determed Root-login, then, as if I remember right (I made less such installs), at one install root privileges worked faultlessly, at other not 100%. Also tried both 32-bit and 64-bit installer; always Mate desktop adding just minimal selection. * What was the outcome of this action? As I wanted to find out Linux distro allowing minimal graphic desktop install (less unused programs (bloatedness)), I tried Debian install really a lot of times, thinking that the cause has to be my unfamiliarity with Debian installer. At most times I did clean install, also reformatted the Home- partition. Yet I had to abandon each new install because I could not use the Terminal. (I am not sure, but probably the Synaptic accepted my password.) * What outcome did you expect instead? I expected my passwords working well. It is not so easy to get the su or sudo working in Debian as I had used in Linux Mint -- but this is another question, the question of convenience for newcomers. There was another thing also: the wording (explaining) of the activating of Root login was quite different in Graphic login and/or Graphic expert login and/or Non-graphic expert login. It was quite hard for me get an idea what really I had chosen. Nevertheless mostly I admire the detailness of Debian tutorial pages! Although, hard to catch sometimes for simple mortals as I... *** *** -- System Information: Debian Release: 10.6 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 4.19.0-12-686-pae (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: sysvinit (via /sbin/init) --- End Message --- --- Begin Message --- Hi Juhan, Juhan writes: ... > After install and reboot I tried to gain root rights: su. Then the Terminal > told the password was not right one, and that this incidence would be > reported. If it told you that the incident would be reported, then I believe you must have been using 'sudo' not 'su'. If you assigned a password to root, then the non-root user you created for yourself will not have been added to the 'sudo' group, so you will not be able to use 'sudo' to become root. However, if during the occasion when you say it worked you happened not to have given root a password, then you user would instead have been added to the 'sudo&#x
Bug#975570: ITP: capbattleship -- Sink your enemy! - A (pretty) pirate battleship board game.
Package: wnpp Severity: wishlist Owner: Fabien Givors X-Debbugs-Cc: debian-devel@lists.debian.org, f+deb...@chezlefab.net * Package name: capbattleship Version : 1.0~alpha2 Upstream Author : Fabien Givors and Damien Monteillard * URL : https://capbattleship.tuxfamily.org/ * License : MIT (code) + CC-BY-4.0 (music) + CC0-1.0 (artworks) Programming Lang: Python3 + Pygame Description : Sink your enemy! - A (pretty) pirate battleship board game. Capbattleship is a pirate themed modern implementation of the classic turn-based battleship board-game, featuring amazing graphics and cool music. I beleive this package should be included in Debian because: - it's more graphical and accessible to children - there is an imersive pirate theme - it has very little dependencies I would like to maintain this package inside the Debian Games Team. I am looking for a sponsor.
Processed: Re: Bug#963846: bugs.debian.org: usb-audio : Lexicon Omega only 2 analog inputs in Debian 10, while showing 4 analog inputs in Debian 9
Processing control commands: > reassign -1 jackd Bug #963846 [general] bugs.debian.org: usb-audio : Lexicon Omega only 2 analog inputs in Debian 10, while showing 4 analog inputs in Debian 9 Bug reassigned from package 'general' to 'jackd'. Ignoring request to alter found versions of bug #963846 to the same values previously set Ignoring request to alter fixed versions of bug #963846 to the same values previously set -- 963846: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963846 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#883133: marked as done (general: Add new package header Upstream-Version:)
Your message dated Sat, 05 Sep 2020 18:35:43 +0200 with message-id <1599323743.11983.17.ca...@jasp.net> and subject line Re: Bug#883133: general: Add new package header Upstream-Version: has caused the Debian Bug report #883133, regarding general: Add new package header Upstream-Version: to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 883133: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883133 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: general Severity: wishlist Dear Maintainers, I propose to add new package header Upstream-Version: to contain the version as of the upstream of the package. The header should be optional because not every package has a definite upstream version. I am writing software which should call a program in specific version range (or fail to call it if the program in this version range is not installed). It should work for Debian and other systems (so I can use only the upstream version, not Debian version as is, to be compatible with other systems). Adding this header would ease the task to extract the upstream version of a specific package. It is possible now, but the algorithm of extracting the version of upstream may be different for every package. This is no good. My software should work not only on Debian. So writing a special algorithm to extract Debian version numbers (instead of simply looking into Upstream-Version:) is not a good way to do this task. Somebody, please report a similar idea for Fedora, SUSE and others. (I don't have it installed and don't know the proper way to report to them.) -- System Information: Debian Release: buster/sid APT prefers stable-updates APT policy: (990, 'stable-updates'), (500, 'unstable'), (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.13.0-1-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) --- End Message --- --- Begin Message --- El dj 27 de 08 de 2020 a les 10:25 +0200, Javier Serrano Polo va escriure: > May I close this report? No objection; closing. Reopen if needed. smime.p7s Description: S/MIME cryptographic signature --- End Message ---
Bug#883134: marked as done (general: Add new package header Upstream-Version:)
Your message dated Sat, 05 Sep 2020 18:35:43 +0200 with message-id <1599323743.11983.17.ca...@jasp.net> and subject line Re: Bug#883133: general: Add new package header Upstream-Version: has caused the Debian Bug report #883133, regarding general: Add new package header Upstream-Version: to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 883133: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883133 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: general Severity: wishlist Dear Maintainers, I propose to add new package header Upstream-Version: to contain the version as of the upstream of the package. The header should be optional because not every package has a definite upstream version. I am writing software which should call a program in specific version range (or fail to call it if the program in this version range is not installed). It should work for Debian and other systems (so I can use only the upstream version, not Debian version as is, to be compatible with other systems). Adding this header would ease the task to extract the upstream version of a specific package. It is possible now, but the algorithm of extracting the version of upstream may be different for every package. This is no good. My software should work not only on Debian. So writing a special algorithm to extract Debian version numbers (instead of simply looking into Upstream-Version:) is not a good way to do this task. Somebody, please report a similar idea for Fedora, SUSE and others. (I don't have it installed and don't know the proper way to report to them.) -- System Information: Debian Release: buster/sid APT prefers stable-updates APT policy: (990, 'stable-updates'), (500, 'unstable'), (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.13.0-1-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) --- End Message --- --- Begin Message --- El dj 27 de 08 de 2020 a les 10:25 +0200, Javier Serrano Polo va escriure: > May I close this report? No objection; closing. Reopen if needed. smime.p7s Description: S/MIME cryptographic signature --- End Message ---
Processed: Re: Bug#966004: bugs.debian.org: .XCompose fails to make long substitutions
Processing control commands: > reassign -1 libx11-6 Bug #966004 [general] bugs.debian.org: .XCompose fails to make long substitutions Bug reassigned from package 'general' to 'libx11-6'. Ignoring request to alter found versions of bug #966004 to the same values previously set Ignoring request to alter fixed versions of bug #966004 to the same values previously set -- 966004: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966004 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#865771: marked as done (general: always stuck before reaching gui mode and can not reach text mode with ctrl + alt + f6 (debian 9 stable, asus rog552vx))
Your message dated Mon, 31 Aug 2020 02:13:22 +0200 with message-id <20200831001321.xibagugltsmqi...@percival.namespace.at> and subject line Re: Bug#865771: general: always stuck before reaching gui mode and can not reach text mode with ctrl + alt + f6 (debian 9 stable, asus rog552vx) has caused the Debian Bug report #865771, regarding general: always stuck before reaching gui mode and can not reach text mode with ctrl + alt + f6 (debian 9 stable, asus rog552vx) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 865771: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865771 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: general Severity: important Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** -- System Information: Debian Release: 9.0 Architecture: amd64 (x86_64) Foreign Architectures: i382, i386 Kernel: Linux 4.9.0-3-amd64 (SMP w/2 CPU cores) Locale: LANG=id_ID.UTF-8, LC_CTYPE=id_ID.UTF-8 (charmap=UTF-8), LANGUAGE=id_ID.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) --- End Message --- --- Begin Message --- Hi agung vega,, thanks for your interest in making Debian better and filing this report: > always stuck before reaching gui mode and >can not reach text mode with ctrl + alt + f6 (debian 9 stable, asus >rog552vx) However, at this time it looks more like a support request, and the bug tracker is not well-suited for helping users interactively. Please try getting help first from other venues listed at https://www.debian.org/support - especially IRC, the mailing lists or http://forums.debian.net/ . Once there is a clear bug identified, please file a new report against the package having the bug. Thank you for your understanding, Chris--- End Message ---
Bug#942406: marked as done (bugs.debian.org: Dual Monitors - Full Screen behaviour)
Your message dated Mon, 31 Aug 2020 02:12:06 +0200 with message-id <20200831001205.3h3t6sucr4ans...@percival.namespace.at> and subject line Re: Bug#942406: bugs.debian.org: Dual Monitors - Full Screen behaviour has caused the Debian Bug report #942406, regarding bugs.debian.org: Dual Monitors - Full Screen behaviour to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 942406: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942406 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: bugs.debian.org Severity: important Dual identical monitors on Raspberry PI, and Intel machine with dual identical graphics cards and same two monitors. full screen expands only to a single monitor. Desired behavior is to expand window to fill both monitors. -- System Information: Distributor ID: Raspbian Description:Raspbian GNU/Linux 10 (buster) Release:10 Codename: buster Architecture: armv7l Kernel: Linux 4.19.75-v7l+ (SMP w/4 CPU cores) Kernel taint flags: TAINT_CRAP Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) --- End Message --- --- Begin Message --- Hi Duncan Hare, * Duncan Hare : [..] > Distributor ID: Raspbian > Description: Raspbian GNU/Linux 10 (buster) You seem to have filed a bug about Raspbian in the Debian bug tracker - please try the Raspbian support channels instead. Thank you for your understanding, Chris--- End Message ---
Processed: reassign 943791 to src:linux ..., reassign 823124 to src:linux, reassign 901008 to src:linux
Processing commands for cont...@bugs.debian.org: > reassign 943791 src:linux Bug #943791 [general] general: laptop HP 15_bw0xx does not power-off properly Bug reassigned from package 'general' to 'src:linux'. Ignoring request to alter found versions of bug #943791 to the same values previously set Ignoring request to alter fixed versions of bug #943791 to the same values previously set > forwarded 823124 > https://github.com/linuxwacom/input-wacom/issues/110#issuecomment-557458801 Bug #823124 [general] general: Wacom stylus / touch screen no longer work after OS resumes from sleep mode. Set Bug forwarded-to-address to 'https://github.com/linuxwacom/input-wacom/issues/110#issuecomment-557458801'. > reassign 823124 src:linux Bug #823124 [general] general: Wacom stylus / touch screen no longer work after OS resumes from sleep mode. Bug reassigned from package 'general' to 'src:linux'. Ignoring request to alter found versions of bug #823124 to the same values previously set Ignoring request to alter fixed versions of bug #823124 to the same values previously set > reassign 901008 src:linux Bug #901008 [general] bugs.debian.org: Hibernation fails when RAM usage is high Bug reassigned from package 'general' to 'src:linux'. Ignoring request to alter found versions of bug #901008 to the same values previously set Ignoring request to alter fixed versions of bug #901008 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 823124: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823124 901008: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901008 943791: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943791 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#915964: marked as done (bugs.debian.org: Boot process with kernel 4.18.0.3 fails and goes to black screen.)
Your message dated Mon, 31 Aug 2020 01:55:09 +0200 with message-id <20200830235508.syobgdcnoir3n...@percival.namespace.at> and subject line Re: Bug#915964: bugs.debian.org: Boot process with kernel 4.18.0.3 fails and goes to black screen. has caused the Debian Bug report #915964, regarding bugs.debian.org: Boot process with kernel 4.18.0.3 fails and goes to black screen. to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 915964: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915964 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: bugs.debian.org Severity: normal Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? Standard terminal update of Debian Testing system that included the new kernel. * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.18.0-2-amd64 (SMP w/4 CPU cores) 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 /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled --- End Message --- --- Begin Message --- Hi alanscott221, thanks for your interest in making Debian better and filing this report: * alanscott221 : > Standard terminal update of Debian Testing system that included the new > kernel. However, at this time it looks more like a support request, and the bug tracker is not well-suited for helping users interactively. Please try getting help first from other venues listed at https://www.debian.org/support - especially IRC, the mailing lists or http://forums.debian.net/ . Once there is a clear bug identified, please file a new report against the package having the bug. Thank you for your understanding, Chris--- End Message ---
Processed: reassign 920318 to src:linux, retitle 920318 to Quanta VZ1: keyboard, touchpad broken since 4.9.0-8
Processing commands for cont...@bugs.debian.org: > reassign 920318 src:linux Bug #920318 [general] bugs.debian.org: Keyboard and Touchpad Not working after Kernel Upgrade Bug reassigned from package 'general' to 'src:linux'. Ignoring request to alter found versions of bug #920318 to the same values previously set Ignoring request to alter fixed versions of bug #920318 to the same values previously set > retitle 920318 Quanta VZ1: keyboard, touchpad broken since 4.9.0-8 Bug #920318 [src:linux] bugs.debian.org: Keyboard and Touchpad Not working after Kernel Upgrade Changed Bug title to 'Quanta VZ1: keyboard, touchpad broken since 4.9.0-8' from 'bugs.debian.org: Keyboard and Touchpad Not working after Kernel Upgrade'. > thanks Stopping processing here. Please contact me if you need assistance. -- 920318: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920318 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: reassign 936096 to src:linux, found 936096 in 5.2.9-2
Processing commands for cont...@bugs.debian.org: > reassign 936096 src:linux Bug #936096 [general] bugs.debian.org: Wlan switch on and off after update 4.19 to 5.2 (normal Testing update) Bug reassigned from package 'general' to 'src:linux'. Ignoring request to alter found versions of bug #936096 to the same values previously set Ignoring request to alter fixed versions of bug #936096 to the same values previously set > found 936096 5.2.9-2 Bug #936096 [src:linux] bugs.debian.org: Wlan switch on and off after update 4.19 to 5.2 (normal Testing update) Marked as found in versions linux/5.2.9-2. > thanks Stopping processing here. Please contact me if you need assistance. -- 936096: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936096 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#878259: marked as done (general: Image icons progressively becoming either absent or default placemat whatever settings)
Your message dated Mon, 31 Aug 2020 01:47:30 +0200 with message-id <20200830234729.ktvyqpkmtrtqf...@percival.namespace.at> and subject line Re: Bug#878259: general: Image icons progressively becoming either absent or default placemat whatever settings has caused the Debian Bug report #878259, regarding general: Image icons progressively becoming either absent or default placemat whatever settings to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 878259: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878259 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: general Severity: normal Dear Maintainer, Debian Sid/Buster loosing image icons for file browsers Nautilus, Nemo (becoming default placemat tree image) and Dolphin (totally blank). Changing the threshold value for displaying images in Nautilus had no effect. Only new or modified files effected for Nautilus, Nemo but all files for Dolphin. Effect noticed shortly after upgrade from Stretch to Buster 64bit. *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** -- System Information: Debian Release: 9.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-3-amd64 (SMP w/8 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) --- End Message --- --- Begin Message --- Hi Jon, thanks for your interest in making Debian better and filing this report: * Jon : > Debian Sid/Buster loosing image icons for file browsers Nautilus, Nemo > (becoming default placemat tree image) and Dolphin (totally blank). Changing > the threshold value for displaying images in Nautilus had no effect. Only new > or modified files effected for Nautilus, Nemo but all files for Dolphin. > Effect > noticed shortly after upgrade from Stretch to Buster 64bit. However, at this time it looks more like a support request, and the bug tracker is not well-suited for helping users interactively. Please try getting help first from other venues listed at https://www.debian.org/support - especially IRC, the mailing lists or http://forums.debian.net/ . Once there is a clear bug identified, please file a new report against the package having the bug. Thank you for your understanding, Chris--- End Message ---
Bug#964940: marked as done (bugs.debian.org: After an upgrade and crash, the boot process say ACPI error: AE_NOT_FOUND. I think that the problem was an upgrade not completed on the bios machine or
Your message dated Mon, 31 Aug 2020 01:48:50 +0200 with message-id <20200830234849.jezb7nkmm63uy...@percival.namespace.at> and subject line Re: Bug#964940: bugs.debian.org: After an upgrade and crash, the boot process say ACPI error: AE_NOT_FOUND. I think that the problem was an upgrade not completed on the bios machine or similar. has caused the Debian Bug report #964940, regarding bugs.debian.org: After an upgrade and crash, the boot process say ACPI error: AE_NOT_FOUND. I think that the problem was an upgrade not completed on the bios machine or similar. to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 964940: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964940 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: bugs.debian.org Severity: important Dear Maintainer, On the subject. Thank you. -- System Information: Debian Release: 10.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 4.19.0-9-686-pae (SMP w/2 CPU cores) Locale: LANG=es_VE.UTF-8, LC_CTYPE=es_VE.UTF-8 (charmap=UTF-8), LANGUAGE=es_VE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled --- End Message --- --- Begin Message --- Hi Juan Alberto Zarate Sanoja, thanks for your interest in making Debian better and filing this report: * Juan Alberto Zarate Sanoja : > After an upgrade and crash, the > boot process say ACPI error: AE_NOT_FOUND. I think that the problem was > an upgrade not completed on the bios machine or similar. > On the subject. Thank you. However, at this time it looks more like a support request, and the bug tracker is not well-suited for helping users interactively. Please try getting help first from other venues listed at https://www.debian.org/support - especially IRC, the mailing lists or http://forums.debian.net/ . Once there is a clear bug identified, please file a new report against the package having the bug. Thank you for your understanding, Chris--- End Message ---
Bug#872930: marked as done (general: reboots every time even when i shut it down)
Your message dated Mon, 31 Aug 2020 01:42:47 +0200 with message-id <20200830234246.y5kshnggn5in5...@percival.namespace.at> and subject line Re: Bug#872930: general: reboots every time even when i shut it down has caused the Debian Bug report #872930, regarding general: reboots every time even when i shut it down to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 872930: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872930 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: general Severity: normal Dear Maintainer, When I shut down my computer it reboots every time, but only when I use Linux (debian). However, I don't have this problem with Windows. I have both of the OSs on the same computer. And only when debian reboots after I tried to suspend it, and error message appears before. It says something like : "* time is in the future ( by less than a day probably due to *'s clock...)" This message doesn't appear after using Windows or turning off the computer by removing the battery. Thank you, -- System Information: Debian Release: 9.1 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) --- End Message --- --- Begin Message --- * Geert Stappers [200830 23:42]: > Who thinks that this bug should be closed. Doing this, then. Chris--- End Message ---
Processed: Re: Bug#942698: bugs.debian.org: Multiple Call Traces in dmesg
Processing control commands: > reassign -1 linux-image-4.19.0-6-amd64 Bug #942698 [general] bugs.debian.org: Multiple Call Traces in dmesg Bug reassigned from package 'general' to 'linux-image-4.19.0-6-amd64'. Warning: Unknown package 'linux-image-4.19.0-6-amd64' Warning: Unknown package 'linux-image-4.19.0-6-amd64' Ignoring request to alter found versions of bug #942698 to the same values previously set Warning: Unknown package 'linux-image-4.19.0-6-amd64' Warning: Unknown package 'linux-image-4.19.0-6-amd64' Ignoring request to alter fixed versions of bug #942698 to the same values previously set Warning: Unknown package 'linux-image-4.19.0-6-amd64' > retitle -1 i915 workqueue issue / i915_hotplug_work_func __flush_work.cold.53 Bug #942698 [linux-image-4.19.0-6-amd64] bugs.debian.org: Multiple Call Traces in dmesg Warning: Unknown package 'linux-image-4.19.0-6-amd64' Changed Bug title to 'i915 workqueue issue / i915_hotplug_work_func __flush_work.cold.53' from 'bugs.debian.org: Multiple Call Traces in dmesg'. Warning: Unknown package 'linux-image-4.19.0-6-amd64' -- 942698: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942698 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#920391: marked as done (bugs.debian.org: Boot fails without acpi=off on HP ENVY 13-ah0003na)
Your message dated Mon, 31 Aug 2020 00:42:42 +0200 with message-id <20200830224241.6t4t6fz2cysma...@percival.namespace.at> and subject line Re: Bug#920391: bugs.debian.org: Boot fails without acpi=off on HP ENVY 13-ah0003na has caused the Debian Bug report #920391, regarding bugs.debian.org: Boot fails without acpi=off on HP ENVY 13-ah0003na to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 920391: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920391 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: bugs.debian.org Severity: normal Dear Maintainer, I can only boot into Debian if I use the option acpi=off; this is from a fresh install. Using acpi=ht also fails to boot. -- System Information: Debian Release: 9.7 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-8-amd64 (SMP w/1 CPU core) 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) --- End Message --- --- Begin Message --- Hi Jake P, thank you for your interest in making Debian better and filing this report: * Jake P [200830 22:39]: > I can only boot into Debian if I use the option acpi=off; this is from a > fresh install. Using acpi=ht also fails to boot. >From other discussions on the Internet it appears the Envy 13 hardware/firmware generally doesn't support non-Windows OS, and a lot of hacks are required to make stuff work at all. I don't consider this a bug in Debian, even if Debian or various components can add workarounds to improve the situation. If motivated Envy 13 owners can help with this, please coordinate the work on the relevant upstream channels. For now, I'm closing this bug as there won't be much we can do on the Debian side. Thank you for your understanding, Chris--- End Message ---
Bug#951314: marked as done (bugs.debian.org: Laptop does not resume when undocked while suspended.)
Your message dated Mon, 31 Aug 2020 00:31:13 +0200 with message-id <20200830223111.vuzbm6yjgz5ub...@percival.namespace.at> and subject line Re: Bug#951314: bugs.debian.org: Laptop does not resume when undocked while suspended. has caused the Debian Bug report #951314, regarding bugs.debian.org: Laptop does not resume when undocked while suspended. to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 951314: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951314 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: bugs.debian.org Severity: normal Dear Maintainer, * What led up to the situation? Undocking my suspended Laptop and resumed it in the train. * What exactly did you do (or not do) that was effective (or ineffective)? Suspended the laptop the night before (via the sleep button). Opened the lid a day later after I unplugged it from the dock. * What was the outcome of this action? Screen was blank. Switching to other virtual consoles did not work. No reaction to alt+ctrl+del shortcut. Only reboot by pressing the power button for several seconds worked for me. * What outcome did you expect instead? Open the lid, see the lock screen, log in. -- System Information: Debian Release: 10.3 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-8-amd64 (SMP w/8 CPU cores) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled --- End Message --- --- Begin Message --- Hi Robin de Silva Jayasinghe, thanks for your interest in making Debian better and filing this report: * Robin de Silva Jayasinghe [200830 22:30]: >* What led up to the situation? > Undocking my suspended Laptop and resumed it in the train. >* What exactly did you do (or not do) that was effective (or > ineffective)? > Suspended the laptop the night before (via the sleep button). Opened the lid a > day later after I unplugged it from the dock. >* What was the outcome of this action? > Screen was blank. Switching to other virtual consoles did not work. No > reaction > to alt+ctrl+del shortcut. Only reboot by pressing the power button for several > seconds worked for me. [..] However, at this time it looks more like a support request, and the bug tracker is not well-suited for helping users interactively. Please try getting help first from other venues listed at https://www.debian.org/support - especially IRC, the mailing lists or http://forums.debian.net/ . Once there is a clear bug identified, please file a new report against the package having the bug. Thank you for your understanding, Chris--- End Message ---
