Bug#1077390: Rebooting the fort77 packaging

On Sat, Oct 12, 2024 at 12:41:23PM +0200, Roland Mas wrote: > fort77 is in the dependency chain of one of my packages, and it's currently > blocked from testing because of an FTBFS. I was having a look at it, and > found that the packaging was rather old-school :-) So I took the liberty of > reboo

Bug#1002056: Supporting alternative zlib implementations

On Wed, Sep 25, 2024 at 01:55:17AM +0200, Guillem Jover wrote: > The problem though is, that because the compressed stream is going to > change, that can make certain test suites fail if we perform this > switch, which I think would be the main fallout that we'd see from > this and would need manu

Bug#1002056: Supporting alternative zlib implementations

On Tue, Sep 24, 2024 at 05:45:49PM +0200, Guillem Jover wrote: > On Tue, 2024-09-24 at 15:58:10 +0200, Mark Brown wrote: > > Obviously it's far too late to do anything with the default for trixie, > > we might want to evaluate doing something after the release but for n

Bug#1002056: Supporting alternative zlib implementations

A recurrning question with the zlib package in Debian is interest in the various alternative zlib implementations that are out there. There was a long period where upstream zlib development seemed very stalled, during that period people who wanted improvements started forking their own projects.

Bug#1074796: gnome-shell: Silently applies pending package updates on shutdown

Package: gnome-shell Version: 43.9-0+deb12u2 Severity: serious [This bug is probably misfiled, I have no idea which GNOME component is responsible for the actual behaviour so this is a guess based on the fact that I interact with the UI to trigger it.] When I select "Power off" from the power men

Bug#1071276: Is 1:1.2.13.dfsg-1 affected by CVE-2023-45853, and if it is, will 1:1.3.dfsg-3.1 be backported to bookworm?

On Fri, May 17, 2024 at 10:56:53AM -0400, John Waffle wrote: > Hi Mark, > > How do I get in contact with them, should I just send a message to > secur...@debian.org? Yes. signature.asc Description: PGP signature

Bug#1071276: Is 1:1.2.13.dfsg-1 affected by CVE-2023-45853, and if it is, will 1:1.3.dfsg-3.1 be backported to bookworm?

On Fri, May 17, 2024 at 10:43:26AM -0400, John Waffle wrote: > - The zlib package page https://tracker.debian.org/pkg/zlib says that > CVE-2023-45853 > is ignored, what is the basis for ignoring this CVE? > - Is there a plan to backport

Bug#1035630: clc-intercal: Update packaging to dh and new upstream version (fixes reproducibility issues!)

le programs have been included in the package. Further > -reference material and more sample INTERCAL programs are avalible with > +reference material and more sample INTERCAL programs are available with > the C-INTERCAL compiler in the intercal package. > > -- Mark Brown , Fri, 5

Bug#1070854: clc-intercal FTBFS: dpkg-genbuildinfo: error: binary build with no binary artifacts found

On Fri, May 10, 2024 at 05:25:35PM +0300, Adrian Bunk wrote: > chmod +x `pwd`/debian/clc-intercal/usr/bin/* > dpkg-genbuildinfo --build=any > -O../clc-intercal_1.00-1_ppc64el-buildd.buildinfo > dpkg-genbuildinfo: error: binary build with no binary artifacts found; > .buildinfo is meaningless >

Bug#1060768: pdudaemon: Missing dependency on python3-aiohttp

Package: pdudaemon Version: 0.0.8.58.g597052b-1 Severity: serious Attempting to use pdudaemon without python3-aiohttp installed results in a traceback: # pdudaemon Traceback (most recent call last): File "/usr/sbin/pdudaemon", line 33, in sys.exit(load_entry_point('pdudaemon==0.1', 'consol

Bug#1059165: [Pkg-javascript-devel] Bug#1059165: src:zlib: fails to migrate to testing for too long: triggers autopkgtest issues

On Wed, Dec 20, 2023 at 10:14:44PM +0100, Jérémy Lal wrote: > BURP wrong zlib version check in the failing test - this could be NMUed > DOLFIN has a single test failure, that is odd and unrelated as well - this > could be NMUed For non-technical reasons I can't do these NMUs myself if they're wa

Bug#1059165: src:zlib: fails to migrate to testing for too long: triggers autopkgtest issues

clone 1059165 -1 reassign -1 nodejs retitle -1 autopkgtest failures on i386 found -1 18.19.0+dfsg-6 block 1059165 by -1 kthxbye On Wed, Dec 20, 2023 at 08:15:31PM +0100, Paul Gevers wrote: > The Release Team considers packages that are out-of-sync between testing and > unstable for more than 30 d

Bug#1055938: zlib1g: move libz.so.* to /usr

On Tue, Nov 14, 2023 at 03:33:00PM +0100, Helmut Grohne wrote: > > debootstrap is already broken by the /usr merge, which is something of > > an annoyance for anyone who uses pbuilder to actually build packages... > I suspect you are using a bulleye or bookworm system with pbuilder to > build for

Bug#1055938: zlib1g: move libz.so.* to /usr

On Tue, Nov 14, 2023 at 11:45:35AM +0100, Helmut Grohne wrote: > fortunately. We do not break the debian-installer (P10), because even > unmerged chroots have /usr/lib/ on their library search > paths. I locally verified that we do not break debootstrap (P8) and > since the affected filename is ar

Bug#1007510: tua: please consider upgrading to 3.0 source format

On Thu, Aug 17, 2023 at 04:34:56PM +0200, Bastian Germann wrote: > Am 17.08.23 um 14:25 schrieb Mark Brown: > > Would it not be more sensible to just require that the format always be > > specified? > The problem with that is that most of the implicitly 1.0 packages

Bug#1007510: tua: please consider upgrading to 3.0 source format

On Wed, Aug 16, 2023 at 04:51:44PM +0200, Bastian Germann wrote: > Am 16.08.23 um 16:40 schrieb Mark Brown: > > On Wed, Aug 16, 2023 at 04:33:40PM +0200, Bastian Germann wrote: > > > If you do not want to move to format 3.0, please at least specify 1.0 > > > format &g

Bug#1007510: tua: please consider upgrading to 3.0 source format

On Wed, Aug 16, 2023 at 04:33:40PM +0200, Bastian Germann wrote: > If you do not want to move to format 3.0, please at least specify 1.0 format > so that dpkg-source can move to default 3.0 format. If you're forcing people to specify the format why does the default matter? signature.asc Descrip

Bug#1036764: xemacs21: new upstream version available

On Thu, May 25, 2023 at 04:50:59PM +0200, Étienne Mollier wrote: > Newer releases look to have moved here[3], and there[4] for the > 21.5.y series; I reckon the layout is not ideal for watch files. The 21.5 series are beta releases still, the stable release is still 21.4. signature.asc Descript

Bug#1036648: zlib1g-dev: Missing manual pages for the functions

On Tue, May 23, 2023 at 09:57:42PM +0200, Alejandro Colomar wrote: > I'm going to use zlib in the near future in my job, so I can write some > manual pages for the functions I use. I'll keep upstream in the loop, > in case they want to pick the pages. I will probably only write pages > for the f

Bug#1036648: zlib1g-dev: Missing manual pages for the functions

severity 1036648 wishlist kthxbye On Tue, May 23, 2023 at 09:26:57PM +0200, Alejandro Colomar wrote: > This library lacks manual pages for the available functions, which seems > to be a violation of the Debian Policy. This is an *extremely* widespread violation of policy at this point... it'd be

Bug#1035485: network-manager-l2tp-gnome: No diagnostics

Package: network-manager-l2tp-gnome Version: 1.20.8-1 Severity: normal When attempting to enable a L2TP VPN connection via Network Manager if the connection fails then an error message is popped up briefly saying "Activation of network connection failed" but no diagnostics are made available indic

Bug#1024715: xemacs21: should use sed instead of perl in prerm scripts

On Wed, Nov 23, 2022 at 05:34:00PM +0100, Gioele Barabucci wrote: > index 73fd7e9..f1beb10 100644 > --- a/debian/prerm-base > +++ b/debian/prerm-base > @@ -9,7 +9,7 @@ fi > # installed. > ALREADY=0 > for i in mule nomule mule-canna-wnn gnome-mule gnome-nomule > gnome-mule-canna-wnn ; do > - ST

Bug#993612: [PATCH v2] of/address: Return an error when no valid dma-ranges are found

he issues there. Fixes: 7a8b64d17e35 ("of/address: use range parser for of_dma_get_range") Signed-off-by: Mark Brown Cc: Luca Di Stefano Cc: 993...@bugs.debian.org Cc: sta...@kernel.org --- Changes in v2: - Don't leak parsed resources. - Link to v1: https://lore.kernel.org/r/20230126

Bug#993612: [PATCH] of/address: Return an error when no valid dma-ranges are found

On Fri, Jan 27, 2023 at 12:37:35PM -0600, Rob Herring wrote: > Looks to me like we are leaking 'r' with this change. Oh, probably now that you mention it. Usually the OF code keeps track of more things than I expect... > Wouldn't this change work: > diff --git a/drivers/of/address.c b/drivers/

Bug#993612: [PATCH] of/address: Return an error when no valid dma-ranges are found

he issues there. Fixes: 7a8b64d17e35 ("of/address: use range parser for of_dma_get_range") Signed-off-by: Mark Brown Cc: Luca Di Stefano Cc: 993...@bugs.debian.org Cc: sta...@kernel.org --- drivers/of/address.c | 5 - 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/drive

Bug#1016803: [Pkg-utopia-maintainers] Bug#1016803: Bug#1016803: Generates unusable resolv.conf

On Thu, Aug 25, 2022 at 10:50:01PM +0200, Michael Biebl wrote: > Output of "nmcli" as well, please. wlp61s0: connected to sirena "Intel 8265 / 8275" wifi (iwlwifi), 48:F1:7F:C0:88:CF, hw, mtu 1500 ip4 default inet4 192.168.8.100/16 route4 192.168.0.0/16

Bug#1016803: Generates unusable resolv.conf

Package: network-manager Version: 1.30.6-1+deb11u1 Severity: important On one of my systems whenever network-manager connects to a WiFi network it generates an unusable resov.conf: # Generated by NetworkManager search example.org Other devices on the same network manage to acquir

Bug#1012674: zlib: contrib/testzlib included (lintian: source-ships-excluded-file)

On Wed, Jul 27, 2022 at 09:00:09PM +0200, vollan...@gmail.com wrote: > There is no licence on this code, it is juste free!! If that's the goal they should have a clear statement that they're in the public domain, without an explicit license grant of some kind the default is that things are copyri

Bug#1016088: binutils-multiarch-dev: libbfd and friends not available for multiarch development

Package: binutils-multiarch-dev Version: 2.35.2-2 Severity: normal Attempting to build a program linking against libbfd (such as perf) for a non-native architecture is not supported in a multiarch environment, binutils-multarch-dev does not provide the libraries and attempting to install the multi

Bug#1014763: dput-ng: dcut rm generates invalid commands

Package: dput-ng Version: 1.33 Severity: normal I have tried to delete some uploads using commands like dcut rm --searchdirs -f zlib_1.2.12.dfsg-0.1.dsc however I'm told that there are errors showing up in the logs on ftp-master saying Jul 11 17:18:33 /broonie-1657559146.command

Bug#1014762: dput-ng: Handling of .changes files for rm is unclear

Package: dput-ng Version: 1.33 Severity: normal The documentation for the rm option gives examples like dcut rm -f DELAYED/X-day/foobar.deb which indicate that dcut rm takes a list of files on the command line and will assemble a commands file for itself. For most files this seems to wo

Bug#1012674: NMU: zlib: contrib/testzlib included (lintian: source-ships-excluded-file)

On Mon, Jul 11, 2022 at 06:54:13PM +0200, Bastian Germann wrote: > Am 11.07.22 um 18:40 schrieb Mark Brown: > > On Mon, Jul 11, 2022 at 06:16:31PM +0200, Bastian Germann wrote: > > > I have uploaded zlib 1.2.12.dfsg-0.1 with the changes attached to > > > DELAYED/3.

Bug#1012674: NMU: zlib: contrib/testzlib included (lintian: source-ships-excluded-file)

On Mon, Jul 11, 2022 at 06:16:31PM +0200, Bastian Germann wrote: > I have uploaded zlib 1.2.12.dfsg-0.1 with the changes attached to DELAYED/3. Why? Please drop this. signature.asc Description: PGP signature

Bug#1014467: zlib1g: cannot install both of armhf and arm64 in multiarch setup

On Wed, Jul 06, 2022 at 05:03:36PM +0200, Jonas Schäfer wrote: > I installed Debian with an arm64 kernel but an armhf userland. I now > need some components as arm64, one of which depends on zlib1g. It is > impossible to install both zlib1g:armhf and zlib1g:arm64, which causes > the installation t

Bug#993612: bugs.debian.org: Socionext SynQuacer fails to mount rootfs after upgrade to Bullseye

On Tue, Mar 29, 2022 at 01:02:34AM +0100, Mark Brown wrote: > On Sun, Sep 05, 2021 at 05:01:18PM +0100, Steve McIntyre wrote: > I bisected this to > > commit 7a8b64d17e35810dc3176fe61208b45c15d25402 > > of/address: use range parser for of_dma_get_range > > on what a

Bug#993612: bugs.debian.org: Socionext SynQuacer fails to mount rootfs after upgrade to Bullseye

On Sun, Sep 05, 2021 at 05:01:18PM +0100, Steve McIntyre wrote: > On Sat, Sep 04, 2021 at 06:50:16PM +0100, Steve McIntyre wrote: > > > >I have a synquacer here still and I'll take a look. I noticed on > >bullseye release day that USB stuff didn't seem to work in the > >installer on the synquacer e

Bug#1008265: CVE-2018-25032: zlib memory corruption on deflate

On Fri, Mar 25, 2022 at 10:50:51PM +0100, Salvatore Bonaccorso wrote: > Here is a preliminary debdiff to address this. Thanks, that's roughly what I uploaded - it looks like your mail raced with my own update. signature.asc Description: PGP signature

Bug#919598: zlib: copyright file needs updating

On Thu, Jan 17, 2019 at 07:14:00PM +0100, Kai Pastor, DG0YT wrote: > a) the zlib 1:1.2.11.dfsg-1 copyright file claims to be based on sources > from zlib-1.0.4.tar.gz which is obviously wrong. That's just descriptive stuff about the creation of the package transferred over from the free form chan

Bug#999155: ping

On Mon, Jan 24, 2022 at 05:51:43PM +0100, Thorsten Alteholz wrote: > In order have some activity on this bug and to avoid autoremoval of > dependencies, this is a reminder of outstanding things to do ... Please don't send content free pings, they just add noise and make it likely that it's going

Bug#999155: RC bug in mm and zlib

On Wed, Jan 05, 2022 at 12:57:47PM +0100, Thorsten Alteholz wrote: > are you already working on an update of mm and zlib? Or do you need some > help? They're utterly trivial, I'll get round to them at some point when I do a batch run through all my packages. It'd be more effort to integrate some

Bug#1002056: ITP: zlib-ng -- optimized zlib compression library

On Tue, Dec 21, 2021 at 04:45:21AM +0100, Guillem Jover wrote: > instead of with its native API. But if that happens, I think it would > make sense to upload, as it's currently being embedded in several > upstream projects and even if dpkg would not switch to it, it would > still help with removin

Bug#992089: xemacs21-packages: contains a file with a non-free "disparaging to Sun" license

On Wed, Aug 11, 2021 at 02:38:48PM +0200, Pierre Gruet wrote: > Source: xemacs21-packages > Version: 2009.02.17.dfsg.2-4 > Severity: serious > Tags: stretch buster bullseye sid ... > The file > xemacs-packages/jde/java/src/jde/debugger/expr/LValue.java > incorporates a non-free license, stating

Bug#787860: closed by Simon McVittie (Re: Bug#787860: build seahorse compatible with gpg2)

On Mon, Apr 12, 2021 at 04:27:46PM +0100, Simon McVittie wrote: > On Mon, 12 Apr 2021 at 15:54:07 +0100, Mark Brown wrote: > > This bug appears to have drifted well away from the initial report > > (which was about GNOME forcing itself as the SSH agent even if one is > > al

Bug#787860: closed by Simon McVittie (Re: Bug#787860: build seahorse compatible with gpg2)

reopen 787860 kthxbye On Sun, Apr 11, 2021 at 04:03:19PM +, Debian Bug Tracking System wrote: > On Fri, 05 Jun 2015 at 16:45:28 -0400, Daniel Kahn Gillmor wrote: > > I've now filed a more extensive changeset at seahorse upstream, as noted > > above. > This seems to have been applied a long t

Bug#952257: xemacs21-packages: FTBFS: Malformed UTF-8 character (fatal) at /usr/share/texinfo/Texinfo/ParserNonXS.pm line 3364.

On Sun, Feb 23, 2020 at 02:22:15PM +0100, Lucas Nussbaum wrote: > Relevant part (hopefully): > > make[3]: Entering directory '/<>/xemacs-packages/edit-utils' Not sure how these are generated but there's over 1000 lines of log here, most of it irrelevant. This makes it hard to both find the actua

Bug#952434: dovecot-imapd: Problems opening mailboxes since upgrade to Debian 10

Package: dovecot-imapd Version: 1:2.3.4.1-5+deb10u1 Severity: important Since upgrading to Debian 10 several mailboxes have started failing to open/read, apparently due to some cache corruption or some format change between versions. The logs show errors like: read(FILENAME) failed: Cached messa

Bug#950626: dcut silently fails

reopen 950626 kthxbye On Thu, Feb 06, 2020 at 01:47:34PM +1100, Ben Finney wrote: > On 05-Feb-2020, Mark Brown wrote: > > If dcut is generating commands which produce no response from the > > server that seems like a really bad bug in dcut. > The server does not process comman

Bug#950626: dcut silently fails

On Tue, Feb 04, 2020 at 11:54:01PM +1100, Ben Finney wrote: > Control: tags -1 + moreinfo > > On 04-Feb-2020, Mark Brown wrote: > > I recently attempted to use dcut to cancel an upload which > > someone had done with commands like > > dcut ftp-master *zlib*

Bug#950626: dcut silently fails

Package: dput Version: 1.0.3 Severity: important I recently attempted to use dcut to cancel an upload which someone had done with commands like dcut ftp-master *zlib* This appeared to have succeded and produced no error message but did not in fact result in the upload being cancelled whi

Bug#949388: zlib: build lib64z for x32 and mipsn32 mipsn32el mipsr6 mipsr6el mipsn32r6 mipsn32r6el

On Tue, Jan 28, 2020 at 08:50:09PM +0800, YunQiang Su wrote: > On Tue, 21 Jan 2020 08:48:23 +0800 YunQiang Su wrote: > > This is some problem we met on mips/mipsel: > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=879636 > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849657 > I NMUed

Bug#945024: msmtp: Doesn't generate a Message-Id

Package: msmtp Version: 1.8.3-1 Severity: normal When injecting mail via /usr/sbin/sendmail if the client program does not generate a message ID then one won't be provided by msmtp resulting in messages going out without a message ID at all. This isn't an unusal thing for simple scripts or simila

Bug#931419: [Pkg-utopia-maintainers] Bug#931419: network-manager: Support for multiple wired networks is confusing

On Thu, Jul 04, 2019 at 05:09:08PM +0200, Michael Biebl wrote: > Am 04.07.19 um 16:14 schrieb Mark Brown: > > I actually see the same behaviour with the CLI and TUI as I do > > with the GNOME settings stuff - there's nothing obvious that > > suggests that the tw

Bug#931419: network-manager: Support for multiple wired networks is confusing

Package: network-manager Version: 1.14.6-2 Severity: normal On a system with multiple wired networks Network Manager displays them separately (eg, in the system settings app I see two network connections listed with separate settings buttons and on/off toggles) but in actual fact there is only a s

Bug#918113: linux-image-4.19.0-1-amd64: Fails to initalize DisplayPort displays with rx560

On Thu, Jan 03, 2019 at 01:49:49PM +, Mark Brown wrote: > Even with only one monitor connected the system is unable to do anything > useful with the display, it has trouble setting up a valid clock > configuration though there is no oops: > > Dec 29 17:57:14 debutante kernel

Bug#918113: linux-image-4.19.0-1-amd64: Fails to initalize DisplayPort displays with rx560

Package: src:linux Version: 4.19.13-1 Severity: important As covered in the kernel log below the amdgpu driver fails to initialize a multi-monitor DisplayPort chain connected to a and AMD RX560 (Polaris11), rendering the system unusable in desktop configurations. There is an oops earlier in the ke

Bug#915190: xemacs21-support: infinite loop in /etc/xemacs21/site-start.d

sg00093.html > > Date: Sat, 16 Jun 2018 11:04:27 -0500 > > From: Rob Browning > > Subject: [PATCH 3/4] Given new policy and emacsXY unversioning drop shared > > dirs > > To: debian-emac...@lists.debian.org > > Cc: Mark Brown > > > > --- > >

Bug#908022: xemacs is not in testing/buster repo any more

On Mon, Sep 10, 2018 at 06:00:05PM +0200, Agustin Martin wrote: > For the records, emacsen-common 3.0.3, already in sid, seems to fix this > dependency, > emacsen-common (3.0.3) unstable; urgency=medium > > * Don't conflict with xemacs21; it's now ready for 3.0. Ah, great - then it should propa

Bug#908022: xemacs is not in testing/buster repo any more

On Mon, Sep 10, 2018 at 12:08:15PM +0200, Chris Nospam wrote: > unfortunately the problem still exists, although you have closed the bug. Is > there any time esitmation, as xemacs is my favorite editor? Not really, it's dependent on Rob fixing the emacsen-common package to not conflict with xema

Bug#908022: xemacs21: xemacs is not in testing/buster repo any more

On Wed, Sep 05, 2018 at 09:53:38AM +0200, Christian Bachmaier wrote: > today 9/5/18 'apt-get dist-upgrade' automatically removed xemacs (xemacs21, > xemacs21-bin, ...) automatically from my buster/testing system. Yes, this is an expected result of a partially done transition - we need an update o

Bug#897573: You need to install the extra package

On Mon, May 07, 2018 at 03:01:23PM +0200, Bastien ROUCARIES wrote: > hi, > > It is a feature you need to depends on extra package It would have been rather more helpful if you were to mention which package this is. It would also have been helpful to have made some effort to communicate this chan

Bug#900358: O: nis -- clients and daemons for the Network Information Service (NIS)

Package: wnpp Severity: normal I intend to orphan the nis package. The package description is: This package provides tools for setting up and maintaining a NIS domain. NIS, originally known as Yellow Pages (YP), is mostly used to let several machines in a network share the same account informa

Bug#897551: usbview: FTBFS: convert-im6.q16: unable to open file `/tmp/magick-20115vbmutCN0nGsV': No such file or directory @ error/constitute.c/ReadImage/544.

clone 897551 -1 reassign -1 imagemagick retitle -1 imagemagic: Errors converting SVG to PNG causing build failures thanks On Wed, May 02, 2018 at 10:55:01PM +0200, Lucas Nussbaum wrote: > > make[2]: Entering directory '/<>' > > convert -geometry $(basename $(dirname $(dirname > > hicolor/64x64/a

Bug#883180: help with zlib package ?

> On 27 Apr 2018, at 14:03, Jérémy Lal wrote: > > Not directly related, but kind of a bug > please fix your email address broo...@debian.org: it isn't working. I seem to get a reasonable amount of mail there and the test mail I just sent to myself arrived fine... whatever problem you believe

Bug#883180: help with zlib package ?

On Fri, Apr 27, 2018 at 10:01:35AM +0200, Jérémy Lal wrote: > I'd like to help maintaining zlib package. > It really needs an update and a couple of fixes. Which fixes? I'm not aware of anything except the new version update... > Could you either do something about it, or accept help ? I've go

Bug#836021: yp-tools_3.3-5.1_source.changes ACCEPTED into unstable

On Wed, Mar 28, 2018 at 12:27:03PM +0100, James Cowgill wrote: > On 28/03/18 02:56, Mark Brown wrote: > > bugs are useful for keeping it out of releases. > I emailed the BTS with the diff on Thursday last week. The BTS says it > forwarded the email to you: > https://bugs.

Bug#853714: yp-tools_3.3-5.1_source.changes ACCEPTED into unstable

On Tue, Mar 27, 2018 at 08:51:30PM +, Debian FTP Masters wrote: >* Non-maintainer upload. >* debian/patches: > - Add patch to fix FTBFS with GCC 7. (Closes: #853714) > - Add patch to fix FTBFS on architectures with strict alignment >requirements. (Closes: #836021) Pl

Bug#890994: nis: ypbind started when the computer start without network

On Wed, Feb 21, 2018 at 01:04:33PM +0100, adrien moulin wrote: > On stretch when i start without network, the computer is very slow to > launch the graphical interface and when i try to login on tty console there > are important latency. > After research the origin of the problem, i found that /e

Bug#867555: gnome-shell: Tries to drive monitor at unsupported refresh rate

Package: gnome-shell Version: 3.26.1-3 Followup-For: Bug #867555 This bug appears to have become *much* worse on a recent upgrade. As well as having once again forgotten my monitor settings I'm now seeing almost any attempt to change settings away from the default resulting in at least one of my

Bug#867555: gnome-shell: Tries to drive monitor at unsupported refresh rate

On Fri, Jul 07, 2017 at 06:49:06PM +0100, Simon McVittie wrote: > On Fri, 07 Jul 2017 at 13:20:28 +0100, Mark Brown wrote: > > > * Move your ~/.config/monitors.xml out of the way (don't delete it; if > > > this works, it would be useful to see what's in it). Thi

Bug#867555: gnome-shell: Tries to drive monitor at unsupported refresh rate

On Fri, Jul 07, 2017 at 12:44:46PM +0100, Simon McVittie wrote: > My first question is, what graphics hardware and driver is this? It's this: 05:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 Series] using whatever Debian drives it

Bug#867555: gnome-shell: Tries to drive monitor at unsupported refresh rate

Package: gnome-shell Version: 3.22.3-3 Severity: important A recent upgrade on my system appears to have caused GNOME to drive one of my monitors at an unsupported refresh rate after login (gdm is fine). After login my primary display goes into power saving mode though GNOME appears to think it's

Bug#864418: lava-tool: Attempting to cancel invalid job produces Python traceback

Package: lava-tool Version: 0.21-1 Severity: normal Attempting to cancel a non-existant job produces a Python traceback: Traceback (most recent call last): File "/usr/bin/lava-tool", line 11, in load_entry_point('lava-tool==0.21', 'console_scripts', 'lava-tool')() File "/usr/lib/python2.

Bug#864417: lava-tool: Python exception splat attempting to list jobs

Package: lava-tool Version: 0.21-1 Severity: normal When attempting to list jobs on my server I get: $ lava-tool jobs-list http://broo...@lava.sirena.org.uk/RPC2 Traceback (most recent call last): File "/usr/bin/lava-tool", line 11, in load_entry_point('lava-tool==0.21', 'console_scripts',

Bug#862260: zlib: debian/copyright isn't in DEP5 format

severity 862260 wishlist tag 862260 - patch kthxbye On Wed, May 10, 2017 at 06:21:09PM +0700, Do Thanh Trung wrote: > +Files: * > +Copyright: 1995-2013 Jean-loup Gailly and Mark Adler > +License: Zlib > + This software is provided 'as-is', without any express or implied > + warranty. In no event

Bug#859661: chromium: Poor integration with gnome-shell after extension removal

Package: chromium Version: 57.0.2987.98-1 Severity: important With the removal of extension support there is a NEWS.Debian entry recommending that either a command line option or an environment variable is set to reenable them if users rely on them. Unfortunately there is no information provided

Bug#854376: gnupg-agent: Broken with systemd

Package: gnupg-agent Version: 2.1.18-4 Severity: important I've got: SSH_AUTH_SOCK=/run/user/1000/gnupg/S.gpg-agent (this is manually forced since gnome-keyring appears to be managing to force itself as the SSH agent, I've filed a separate bug about that). When I try to list keys I get: $

Bug#854318: gnome-keyring: Attempts to provide ssh-agent

On Mon, Feb 06, 2017 at 02:29:40AM +0100, Michael Biebl wrote: > Am 06.02.2017 um 00:43 schrieb Mark Brown: > > I have previously removed /etc/xdg/autostart/gnome-keyring-ssh.desktop > > (which is still removed) but it appears that this is now triggred by > > systemd someho

Bug#854318: gnome-keyring: Attempts to provide ssh-agent

Package: gnome-keyring Version: 3.20.0-3 Severity: important A recent upgrade to gnome-keyring appears to have resulted in it once again trying to provide a SSH agent. Since I use a gnupg smartcard to store my authentication keys for SSH (which is supported by GnuPG but not by gnome-keyring) this

Bug#849000: Upstream Updates and Packaging

On Wed, Feb 01, 2017 at 12:42:38PM +, Barak A. Pearlmutter wrote: > Okay. I'm including a diff from 2.0-3 to the debian/* subdir below. > I'm sending a tarball of an upstream snapshot (commit 6fe2f4f) under > separate cover without a BTS CC, because it seems silly to include it > as an attachm

Bug#849000: Upstream Updates and Packaging

On Wed, Dec 21, 2016 at 04:58:24PM +, Barak A. Pearlmutter wrote: > to support some modern devices etc. I have also done a revision pass > on the packaging scripts to enable a desktop file hooked into > policykit, harden the executable (which after all sees unsanitised > data from removable de

Bug#853781: git am ignores messages in Maildirs

Package: git Version: 1:2.11.0-2 Severity: important When running $ git am --signoff $MAILDIR git will frequently not even attempt to apply some of the patches in the Maildir. I can't see any obvious pattern in the messages being ignored, but it does seem to happen with excessive regularity m

Bug#787956: raising the severity, prevents usage of the multilib packages

On Sat, Jan 07, 2017 at 11:15:51AM +0100, Matthias Klose wrote: > multiarch is not yet ready; you can't build it on the buildds, you can't > depend > on foreign architectures on the buildds. If you want to spend some time > working > on this, it would be appreciated, but until then I think it's

Bug#787956: raising the severity, prevents usage of the multilib packages

On Fri, Jan 06, 2017 at 08:48:06AM +0100, Matthias Klose wrote: > On 05.12.2016 18:50, Mark Brown wrote: > > As we have been discussing it is still not clear to me if I should fix > > or remove the multilib packages since it is still not clear to me that > > there is a sensi

Bug#847270: closed by Mark Brown (Re: Bug#847270: zlib CVE-2016-9840 and CVE-2016-9841)

On Wed, Dec 07, 2016 at 07:21:02PM +0100, Salvatore Bonaccorso wrote: > > On Wed, Dec 07, 2016 at 12:31:43PM +0100, Salvatore Bonaccorso wrote: > > That's because you filed three different bug reports about CVEs all with > > just boilerplate and no directly readable content about them, mainly a >

Bug#845793: Bug#787956: raising the severity, prevents usage of the multilib packages

On Mon, Dec 05, 2016 at 06:24:46PM +0100, Matthias Klose wrote: > On 05.12.2016 18:14, Mark Brown wrote: > > I am suggesting that since nothing except for the multlib D runtime > > packages needs a multilib zlib and there seems to be a very limited use > > case for them it

Bug#787956: raising the severity, prevents usage of the multilib packages

On Mon, Dec 05, 2016 at 04:40:29PM +0100, Matthias Klose wrote: > On 05.12.2016 11:29, Mark Brown wrote: > > On Wed, Nov 30, 2016 at 03:31:59PM +0100, Matthias Klose wrote: > >> it's available in the GCC packages for a while now. > > Sure, but there's a bunch mo

Bug#787956: raising the severity, prevents usage of the multilib packages

On Wed, Nov 30, 2016 at 03:31:59PM +0100, Matthias Klose wrote: > On 30.11.2016 13:45, Mark Brown wrote: > > Well, there's a bunch of questions there - people seem generally > > negative on x32 and the use cases for multilib with tooling for early > > boot and so on

Bug#787956: raising the severity, prevents usage of the multilib packages

On Tue, Nov 29, 2016 at 02:00:48PM +0100, Matthias Klose wrote: > On 28.11.2016 19:42, Mark Brown wrote: > > On Sat, Nov 26, 2016 at 08:59:34PM +0100, Matthias Klose wrote: > > Which apparently changed at some point in the toolchain, probably quite > > some time ago, but fort

Bug#787956: raising the severity, prevents usage of the multilib packages

On Sun, Nov 27, 2016 at 06:39:22PM +0200, Sami Liedes wrote: > It seems to me that Mark is saying that this is not even supposed to > work with lib32z1-dev installed, but rather you should have > zlib1g-dev:i386 installed (and not doing so is user error). Right, that's now the expected way for us

Bug#787956: raising the severity, prevents usage of the multilib packages

On Sat, Nov 26, 2016 at 08:59:34PM +0100, Matthias Klose wrote: > On 26.11.2016 20:35, Mark Brown wrote: > > On Sat, Nov 26, 2016 at 07:52:26PM +0100, Matthias Klose wrote: > >> On 26.11.2016 19:42, Mark Brown wrote: > >>> On Sat, Nov 26, 2016 at 03:56:21PM +0100, Ma

Bug#787956: raising the severity, prevents usage of the multilib packages

On Sat, Nov 26, 2016 at 07:52:26PM +0100, Matthias Klose wrote: > On 26.11.2016 19:42, Mark Brown wrote: > > On Sat, Nov 26, 2016 at 03:56:21PM +0100, Matthias Klose wrote: > > Please allow at least a little time for a response, I've no real idea > > what you're e

Bug#812532: files with the same name installed in / and /usr

On Sun, Oct 23, 2016 at 02:06:29AM +0200, Marco d'Itri wrote: > On Oct 23, Mark Brown wrote: > > I'd have expected to at least have seen something going round saying > > that the transition was mostly complete and that there were only a few > > packages blocking

Bug#812532: files with the same name installed in / and /usr

On Sun, Oct 23, 2016 at 01:18:54AM +0200, Marco d'Itri wrote: > On Oct 23, Mark Brown wrote: > > Which was uploaded yesterday without warning which isn't exactly > > helpful, there's not even been a proposal from anyone working on this > > for how to fix i

Bug#812532: files with the same name installed in / and /usr

severity 812532 serious On Sun, Oct 23, 2016 at 12:36:18AM +0200, Marco d'Itri wrote: > Control: severity -1 grave Please don't play severity games, it's not at all helpful. > On Jan 24, Marco d'Itri wrote: > > which have the same name of file installed by the hostname package in > > /bin/,

Bug#837712: Processed: severity of 837712 is serious

On Fri, Oct 21, 2016 at 05:45:39PM +0200, Lucas Nussbaum wrote: > On 21/10/16 at 16:32 +0100, Mark Brown wrote: > > > Bug #837712 [src:xemacs21] xemacs21: FTBFS with bindnow and PIE enabled > > > Severity set to 'serious' from 'important' > &

Bug#837712: Processed: severity of 837712 is serious

On Fri, Oct 21, 2016 at 02:08:47PM +, Debian Bug Tracking System wrote: > Bug #837712 [src:xemacs21] xemacs21: FTBFS with bindnow and PIE enabled > Severity set to 'serious' from 'important' I've still not seen any usable reproduction instructions. signature.asc Description: PGP signature

Bug#837225: xemacs21: FTBFS: Can't locate var_file.pl in @INC

On Sat, Sep 10, 2016 at 09:30:31AM +0200, Lucas Nussbaum wrote: > During a rebuild of all packages in sid, your package failed to build on > amd64. FFS, why did this suddenly break and if it's due to the perl include transition why did it not get reported in the mass bug filing for this? signat

Bug#837712: xemacs21: FTBFS with bindnow and PIE enabled

On Tue, Sep 13, 2016 at 09:25:13PM +0200, Balint Reczey wrote: > For more information about the changes to sid's dpkg and GCC please > visit: > https://wiki.debian.org/Hardening/PIEByDefaultTransition You've not provided any instructions for reproducing this problem :( signature.asc Descriptio

Bug#835614: chromium: HiDPI handling no longer works

On Sat, Aug 27, 2016 at 06:06:38PM +0200, Mark Brown wrote: > Previous versions of Chromium rendered correctly on high DPI displays. > Since the most recent upgrade this support appears to have been removed > or at least become non-functional - everything in the display is > rend

Bug#835614: chromium: HiDPI handling no longer works

Package: chromium Version: 52.0.2743.116-2 Severity: important Previous versions of Chromium rendered correctly on high DPI displays. Since the most recent upgrade this support appears to have been removed or at least become non-functional - everything in the display is rendered without reference

  1   2   3   4   5   6   7   8   9   10   >