Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #247456 > unrolled thread

Why does this take so much time?

Back to article view | Back to linux.debian.user

Contents

  Why does this take so much time? steve <dlist@bluewin.ch> - 2022-04-22 19:30 +0200
    Re: Why does this take so much time? "Andrew M.A. Cater" <amacater@einval.com> - 2022-04-22 19:50 +0200
      Re: Why does this take so much time? Charles Curley <charlescurley@charlescurley.com> - 2022-04-22 20:20 +0200
        Re: Why does this take so much time? "Andrew M.A. Cater" <amacater@einval.com> - 2022-04-22 20:50 +0200
          Re: Why does this take so much time? Charles Curley <charlescurley@charlescurley.com> - 2022-04-23 03:40 +0200
            Re: Why does this take so much time? Eric S Fraga <e.fraga@ucl.ac.uk> - 2022-04-23 18:10 +0200
              Re: Why does this take so much time? steve <dlist@bluewin.ch> - 2022-04-23 18:20 +0200
    Re: Why does this take so much time? Charles Curley <charlescurley@charlescurley.com> - 2022-04-22 20:20 +0200
      Re: Why does this take so much time? steve <dlist@bluewin.ch> - 2022-04-23 11:10 +0200
        Re: Why does this take so much time? Charles Curley <charlescurley@charlescurley.com> - 2022-04-23 16:20 +0200
          Re: Why does this take so much time? steve <dlist@bluewin.ch> - 2022-04-23 17:00 +0200

#247456 — Why does this take so much time?

Hi,


When I 'apt update', the following URL takes ages:

Atteint :2 https://updates.signal.org/desktop/apt xenial InRelease

Why? Do you see the same?

Best,

s

[toc] | [next] | [standalone]

#247457

On Fri, Apr 22, 2022 at 07:26:47PM +0200, steve wrote:
> 
> Hi,
> 
> 
> When I 'apt update', the following URL takes ages:
> 
> Atteint :2 https://updates.signal.org/desktop/apt xenial InRelease
> 
> Why? Do you see the same?
> 
> Best,
> 
> s
>

Hi steve,

Sorry: This is a third party .deb package which appears to be packaged
for an Ubuntu release 16.04  (Xenial Xerus) that is now out of standard
support from Canonical with effect from the release of Jammy Jellyfish 
yesterday.

I'm not sure we can help you on this list and I would suggest that you
ask signal.org.

Mixing .deb packages from multiple Debian/Debian-derived distributions is
normally a very bad idea - https://wiki.debian.org/DontBreakDebian

With every good wish, as ever,

Andy Cater

[toc] | [prev] | [next] | [standalone]

#247459

On Fri, 22 Apr 2022 17:48:06 +0000
"Andrew M.A. Cater" <amacater@einval.com> wrote:

> Mixing .deb packages from multiple Debian/Debian-derived
> distributions is normally a very bad idea -
> https://wiki.debian.org/DontBreakDebian

In general I agree with this. However, this is what the signal folks
tell Debian users to do. So if they answer Steve at all, that is likely
what they will tell him to do.

root@hawk:~# apt show signal-desktop
Package: signal-desktop
Version: 5.40.0
Priority: optional
Section: default
Maintainer: Signal Messenger, LLC <support@signal.org>
Installed-Size: 375 MB
Depends: libnotify4, libxtst6, libnss3, libasound2, libxss1
Recommends: libappindicator3-1
Homepage: https://github.com/signalapp/Signal-Desktop#readme
Vendor: Signal Messenger, LLC <support@signal.org>
License: AGPL-3.0-only
Download-Size: 116 MB
APT-Manual-Installed: yes
APT-Sources: https://updates.signal.org/desktop/apt xenial/main amd64 Packages
Description: Private messaging from your desktop

N: There are 43 additional records. Please use the '-a' switch to see them.
root@hawk:~# 



-- 
Does anybody read signatures any more?

https://charlescurley.com
https://charlescurley.com/blog/

[toc] | [prev] | [next] | [standalone]

#247460

On Fri, Apr 22, 2022 at 12:17:27PM -0600, Charles Curley wrote:
> On Fri, 22 Apr 2022 17:48:06 +0000
> "Andrew M.A. Cater" <amacater@einval.com> wrote:
> 
> > Mixing .deb packages from multiple Debian/Debian-derived
> > distributions is normally a very bad idea -
> > https://wiki.debian.org/DontBreakDebian
> 
> In general I agree with this. However, this is what the signal folks
> tell Debian users to do. So if they answer Steve at all, that is likely
> what they will tell him to do.
> 

Hi Charles,

Thanks for stepping in with concrete help - it's good that we had someone
else running Signal to help. I think the point I wanted to make is that
we _can't_ be expected to help out on all third party .debs, especially
when that .deb is compiled against an obsolescent version of Ubuntu.
Likewise "I'm running Linux Mint / TDE and I can't find support in their
channel - please help"

A large chunk of the mails here are sorting out:

"I don't know how to edit an /etc/apt/sources.list" or
"I added some app from some site and it all broke" or
"I mixed Ubuntu and Debian and now I don't know what I have"

Those are almost as popular as the favourite:

"I did something, then I did something else then X happened so I did Y
and now it's not working but I've no idea how I got here" 

which is a well known thread starter here.

With every good wish, as ever,

Andy Cater

[toc] | [prev] | [next] | [standalone]

#247462

On Fri, 22 Apr 2022 18:46:39 +0000
"Andrew M.A. Cater" <amacater@einval.com> wrote:

> Thanks for stepping in with concrete help - it's good that we had
> someone else running Signal to help.

I was in a position to help, so I did. I have not so far heard back
from Steve whether he has found a solution.

> I think the point I wanted to make is that we _can't_ be expected to
> help out on all third party .debs, especially when that .deb is
> compiled against an obsolescent version of Ubuntu. Likewise "I'm
> running Linux Mint / TDE and I can't find support in their channel -
> please help"

I agree, people should not expect help on 3rd party applications,
frankendebians, or other situations that run against the standard
advice around here. I think you did a good job of explaining this to
Steve.

Once in a while, someone asks for help in such a situation, and someone
else is in a position to give it. But that's the exception. So I have
no problem with someone asking. I do take exception to some twatwaffle
getting irate because no-one answered his badly framed and off-topic
query.

Besides, we're all volunteers here, something some people can't seem to
get wedged between their ears.

-- 
Does anybody read signatures any more?

https://charlescurley.com
https://charlescurley.com/blog/

[toc] | [prev] | [next] | [standalone]

#247469

On Friday, 22 Apr 2022 at 19:37, Charles Curley wrote:
> I was in a position to help, so I did. I have not so far heard back
> from Steve whether he has found a solution.

Just to add a data point, probably mostly for the benefit of the OP: I
use Signal and have the same source in my list for apt and have no
problems at all.  I've noticed no delay for that server.  Just tried
updating right now and the response was immediate.
-- 
Eric S Fraga with org 9.5.3 in Emacs 29.0.50 on Debian 11.3

[toc] | [prev] | [next] | [standalone]

#247470

Le 23-04-2022, à 17:01:22 +0100, Eric S Fraga a écrit :

>On Friday, 22 Apr 2022 at 19:37, Charles Curley wrote:
>> I was in a position to help, so I did. I have not so far heard back
>> from Steve whether he has found a solution.
>
>Just to add a data point, probably mostly for the benefit of the OP: I
>use Signal and have the same source in my list for apt and have no
>problems at all.  I've noticed no delay for that server.  Just tried
>updating right now and the response was immediate.

Thanks Eric for that. So it's on my side, which is good to know. And I
just noticed that it happens on my main machine and not on my laptop. 

[toc] | [prev] | [next] | [standalone]

#247458

On Fri, 22 Apr 2022 19:26:47 +0200
steve <dlist@bluewin.ch> wrote:

> When I 'apt update', the following URL takes ages:
> 
> Atteint :2 https://updates.signal.org/desktop/apt xenial InRelease
> 
> Why? Do you see the same?

As luck would have it, I just had an update for signal (5.40) waiting
for me. I saw no noticeable delay.

What is your sources.list for signal? I have:

root@hawk:~# cat /etc/apt/sources.list.d/signal-xenial.list 
deb [arch=amd64 signed-by=/usr/share/keyrings/signal-desktop-keyring.gpg] https://updates.signal.org/desktop/apt xenial main
root@hawk:~# 

-- 
Does anybody read signatures any more?

https://charlescurley.com
https://charlescurley.com/blog/

[toc] | [prev] | [next] | [standalone]

#247464

Hi,

Thanks to everyone for the help, and I know I'm a bit off topic here
with this Signal thing, sorry. It's the only Franken thing on my box.

But, I thought maybe someone was also using Signal on their Debian box
and could help. In fact this lag when updating in pretty new, but I
cannot say when it appeared in the first place (thought it might go away
by it's own).


Le 22-04-2022, à 12:11:14 -0600, Charles Curley a écrit :

>On Fri, 22 Apr 2022 19:26:47 +0200
>steve <dlist@bluewin.ch> wrote:
>
>> When I 'apt update', the following URL takes ages:
>>
>> Atteint :2 https://updates.signal.org/desktop/apt xenial InRelease
>>
>> Why? Do you see the same?
>
>As luck would have it, I just had an update for signal (5.40) waiting
>for me. I saw no noticeable delay.
>
>What is your sources.list for signal? I have:
>
>root@hawk:~# cat /etc/apt/sources.list.d/signal-xenial.list
>deb [arch=amd64 signed-by=/usr/share/keyrings/signal-desktop-keyring.gpg] https://updates.signal.org/desktop/apt xenial main

cat signal-xenial.list
deb [arch=amd64] https://updates.signal.org/desktop/apt xenial main

The keyring thing missing was I added it, but it didn't change anything,
update still lags. But upgrade goes quickly. 

Is there a debug mode for apt that could be helpful? I tried

apt -oDebug::pkgAcquire::Worker=1 update

but it doesn't show interesting info for my case.

Might need to fire up tcpdump to see the trafic.

[toc] | [prev] | [next] | [standalone]

#247467

On Sat, 23 Apr 2022 11:06:29 +0200
steve <dlist@bluewin.ch> wrote:

> cat signal-xenial.list
> deb [arch=amd64] https://updates.signal.org/desktop/apt xenial main
> 
> The keyring thing missing was I added it, but it didn't change
> anything, update still lags. But upgrade goes quickly. 

OK, just an idea.

Are you going through any proxy server, such as apt-cacher-ng?
apt-cacher-ng doesn't like https at all and that could be part of the
problem.

-- 
Does anybody read signatures any more?

https://charlescurley.com
https://charlescurley.com/blog/

[toc] | [prev] | [next] | [standalone]

#247468

Le 23-04-2022, à 07:13:32 -0600, Charles Curley a écrit :

>On Sat, 23 Apr 2022 11:06:29 +0200
>steve <dlist@bluewin.ch> wrote:
>
>> cat signal-xenial.list
>> deb [arch=amd64] https://updates.signal.org/desktop/apt xenial main
>>
>> The keyring thing missing was I added it, but it didn't change
>> anything, update still lags. But upgrade goes quickly.
>
>OK, just an idea.
>
>Are you going through any proxy server, such as apt-cacher-ng?
>apt-cacher-ng doesn't like https at all and that could be part of the
>problem.

Na, nothing like that.

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web