Re: Debian Apache version

2024-03-07 Thread Paul Wise
On Wed, 2024-03-06 at 11:22 -0500, Ali Ramzan wrote:

> We are currently using Debian Apache version 2.4.57-2, which has some
> vulnerabilities (Apache 2.4.x < 2.4.58 Multiple Vulnerabilities CVE-
> 2023-31122 CVE-2023-43622 CVE-2023-45802). I am trying to find out
> when the new version of Apache (2.4.58-1) will be released. 

Please contact the Debian Apache Team for info about this:

https://wiki.debian.org/Teams/Apache
https://lists.debian.org/debian-apache/

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


signature.asc
Description: This is a digitally signed message part


Re: Some Gnome timeout imply proof of life requirement on server side to maintain or restore Xfce Session.

2024-03-07 Thread Paul Wise
On Wed, 2024-03-06 at 09:59 +0100, benoit Rolland wrote:

> When using Xfce remotely,
> 
> a kind of Gnome timeout occurs after a few minutes.

Please contact our support channels for help using Debian:

https://www.debian.org/support

They will be able to help you figure out this issue and
direct you to the right place to be able to fix the problem.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


signature.asc
Description: This is a digitally signed message part


Bug#1032623: marked as done (vcswatch: should not raise error on repos > 1GiB in size)

2024-03-07 Thread Guillem Jover
Hi!

On Wed, 2024-03-06 at 14:15:03 +, Debian Bug Tracking System wrote:
> 
> vcswatch: Use --filter blob:none
> 
> Required blobs (changelog, control, upstream metadata) are fetched by
> git on demand. Thanks to Gábor Németh for the suggestion!
> 
> Closes: #1032623
> 

It looks like this broke for remotes that do not support filtering
(yet?). The attached completely untested patch might make this work
again. Affecting at least git.hadrons.org and git.dpkg.org, but there
might be others too.

Thanks,
Guillem
From d78a41fad53de64eb50f72692bf057c82d41fc85 Mon Sep 17 00:00:00 2001
From: Guillem Jover 
Date: Thu, 7 Mar 2024 13:30:41 +0100
Subject: [PATCH] vcswatch: Ignore warning when the server does not know about
 filtering

The command succeeded, but emitted a warning. Instead of failing the
fetching, ignore the warning.
---
 data/vcswatch/vcswatch | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/data/vcswatch/vcswatch b/data/vcswatch/vcswatch
index be72cc35..611d5372 100755
--- a/data/vcswatch/vcswatch
+++ b/data/vcswatch/vcswatch
@@ -243,6 +243,8 @@ sub process_package ($) {
 	# try a full clone instead
 	runcmd ('git', 'clone', '--quiet', '--bare', '--mirror', '--template', '', $url, $pkgdir);
 	$dbh->do("UPDATE vcs SET dumb_http = true WHERE package = ?", undef, $pkg->{package});
+} elsif ($err =~ /warning: filtering not recognized by server, ignoring/) {
+	# ignore the warning
 } else {
 	error ($err);
 }
-- 
2.43.0



Bug#1032623: marked as done (vcswatch: should not raise error on repos > 1GiB in size)

2024-03-07 Thread Christoph Berg
> It looks like this broke for remotes that do not support filtering
> (yet?). The attached completely untested patch might make this work
> again. Affecting at least git.hadrons.org and git.dpkg.org, but there
> might be others too.

Thanks for spotting that, the patch seems to work.

Re-running the scan on the dpkg repo still takes around 3 minutes -
not sure what the client or the server are doing during that time, it
doesn't re-fetch the repo.

On acl and attr the scan is done in 2 or 3s.

Christoph



Bug#1032623: marked as done (vcswatch: should not raise error on repos > 1GiB in size)

2024-03-07 Thread Guillem Jover
Hi!

On Thu, 2024-03-07 at 14:34:39 +0100, Christoph Berg wrote:
> > It looks like this broke for remotes that do not support filtering
> > (yet?). The attached completely untested patch might make this work
> > again. Affecting at least git.hadrons.org and git.dpkg.org, but there
> > might be others too.
> 
> Thanks for spotting that, the patch seems to work.

Great! :)

> Re-running the scan on the dpkg repo still takes around 3 minutes -
> not sure what the client or the server are doing during that time, it
> doesn't re-fetch the repo.

I've now done a «git gc --aggressive» on the repo on the server,
hoping that might help with that.

> On acl and attr the scan is done in 2 or 3s.

These only contain the debian/ directory, so I'd expect them to be
fast no matter what.

Thanks,
Guillem



Re: Debian Apache version

2024-03-07 Thread Ali Ramzan
Thanks you let me try this

On Thu, Mar 7, 2024 at 4:41 AM Paul Wise  wrote:

> On Wed, 2024-03-06 at 11:22 -0500, Ali Ramzan wrote:
>
> > We are currently using Debian Apache version 2.4.57-2, which has some
> > vulnerabilities (Apache 2.4.x < 2.4.58 Multiple Vulnerabilities CVE-
> > 2023-31122 CVE-2023-43622 CVE-2023-45802). I am trying to find out
> > when the new version of Apache (2.4.58-1) will be released.
>
> Please contact the Debian Apache Team for info about this:
>
> https://wiki.debian.org/Teams/Apache
> https://lists.debian.org/debian-apache/
>
> --
> bye,
> pabs
>
> https://wiki.debian.org/PaulWise
>


Bug#884341: marked as done (debsources: Unnecessary vertical scroll bar interferes src view scrolling)

2024-03-07 Thread Debian Bug Tracking System
Your message dated Thu, 07 Mar 2024 20:02:31 -0500
with message-id <8c000f6d9c28f696638b229a9a35280ed9734a4e.ca...@debian.org>
and subject line Re: Bug#884341: debsources: Unnecessary vertical scroll bar 
interferes src view scrolling
has caused the Debian Bug report #884341,
regarding debsources: Unnecessary vertical scroll bar interferes src view 
scrolling
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.)


-- 
884341: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884341
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: qa.debian.org
Severity: minor

For any random page that shows the content of source code, there is an
unnecessary vertical scroll bar between the line number and the content of
source code. When the user put focus (e.g., by clicking the content of src),
the whole page will not be able to scroll up or down anymore till the user
moves the focus out the the webpage itself.

I believe we could eliminate the vertical scroll bar completely and solves this
problem.

I'm using Debian unstable with Firefox 57. I tested Chromium and the page on
Chromium seems don't get affected by the problem.



-- System Information:
Debian Release: buster/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.14.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=zh_CN.UTF-8, LC_CTYPE=zh_CN.UTF-8 (charmap=UTF-8), LANGUAGE= 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Hi,

Sorry for the (very) late reply. It seems that the result is caused by a 
combination
of fonts, locale and browser (Firefox here). As it is no a universal bug, 
getting a
targeted fix is not useful here. As a result I am closing this bug report here.

Thanks,
Boyuan Yang

On Sun, 11 Feb 2018 21:29:39 +0100 Matthieu Caneill  
wrote:
> Hi,
> 
> On Mon, Dec 18, 2017 at 11:05:28AM +0800, Boyuan Yang wrote:
> > See also the attached image (the same).
> > 
> > The scrollbar will disappear if I set "overflow-y: hidden" to the pre tag 
> > highlighted in the screenshot.
> 
> Thanks for the screenshot. I failed to reproduce it or understand
> where the scrollbar comes from. I also notice an horizontal scrollbar
> below the code that is not supposed to be there.
> 
> Since the element or its parents don't have any height set, there
> shouldn't be a scrollbar.
> 
> While I don't mind applying this CSS hack, I'd prefer to fix this
> properly. Are you using any extension that might change how the
> elements are displayed, or any parameter I'm not aware of that could
> have an impact?
> 
> Thanks in advance,
> --
> Matthieu



signature.asc
Description: This is a digitally signed message part
--- End Message ---