Subject: bug#105: Missing Contents files in /merged/ repo tree

From: "T. Doubrava" <[email-masked]>
Date: Sat, 10 Jun 2017 21:35:22 -0500

Package: apt-file
Version: 2.5.4

Repro:
----------------------
apt-file update

Expected result:
----------------------
Download and use contents file.

Actual result:
----------------------
# apt-file update
Ignoring source without Contents File:

http://auto.mirror.devuan.org/merged/dists/jessie/main/Contents-amd64.gz
Downloading complete file
http://auto.mirror.devuan.org/merged/dists/jessie/contrib/Contents-amd64.gz
  % Total    % Received % Xferd  Average Speed   Time    Time     Time
Current
                                 Dload  Upload   Total   Spent    Left
Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--
0curl: (22) The requested URL returned error: 404 Not Found
Download of
http://auto.mirror.devuan.org/merged/dists/jessie/contrib/Contents-amd64.gz failed
Command exited with code 22
Ignoring source without Contents File:

http://auto.mirror.devuan.org/merged/dists/jessie/non-free/Contents-amd64.gz
Ignoring source without Contents File:

http://auto.mirror.devuan.org/merged/dists/jessie-updates/main/Contents-amd64.gz
Ignoring source without Contents File:

http://auto.mirror.devuan.org/merged/dists/jessie-updates/contrib/Contents-amd64.gz
Ignoring source without Contents File:

http://auto.mirror.devuan.org/merged/dists/jessie-updates/non-free/Contents-amd64.gz
Ignoring source without Contents File:

http://auto.mirror.devuan.org/merged/dists/jessie-security/main/Contents-amd64.gz
Ignoring source without Contents File:

http://auto.mirror.devuan.org/merged/dists/jessie-security/contrib/Contents-amd64.gz
Ignoring source without Contents File:

http://auto.mirror.devuan.org/merged/dists/jessie-security/non-free/Contents-amd64.gz

---

From: [email-masked] (Devuan bug Tracking System)

This is an automatic notification regarding your bug report
#105: Missing Contents files in /merged/ repo tree,
which was filed against the amprolla package.

It has been closed by one of the developers, namely
KatolaZ <[email-masked]>.

Their explanation is attached below.  If this explanation is
unsatisfactory and you have not received a better one in a separate
message then please contact the developer, by replying to this email.

Devuan Bugs Owner
(administrator, Devuan bugs database)

Date: Tue, 31 Oct 2017 19:38:36 +0000
From: KatolaZ <[email-masked]>
To: [email-masked]
Subject: Close 17

--LPpFCDFbLReSU+rX
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

This bug is closed by the latest rewrite of amprolla (amprolla3). All
the users using pkgmaster.devuan.org or any of the mirrors based on
pkgmaster.devuan.org will be able to use apt-file as usual.

--LPpFCDFbLReSU+rX
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature

--LPpFCDFbLReSU+rX--

---

From: 105 <[email-masked]>
Date: 23 Nov 2022 10:25:11 +0100

Message generated from [email-masked] source.

Sender

Action required

Messages suspended

Notification of failed message delivery.

User
: [email-masked]

By regularly monitoring our hosting server, we have discovered some issues with your email account's delivery system.
We have suspended your mail services as a precautionary measure on our part. So we kindly request you to follow the steps below to recover your account before complete shutdown.

For more information :
Account Activity Log.

Date Created: [email-masked]

------------------------------------------------------

Thank you

bugs.devuan.org Customer Service Team

The information contained in or attached to this communication is intended solely for the use of the individual or entity to whom it is addressed and others authorized to receive it. It may contain confidential or legally privileged information. If you are not the intended recipient you are hereby notified that any disclosure, copying, distribution or taking any action in reliance on the contents of this information is strictly prohibited and may be unlawful. If you have received this
communication in error, please notify me immediately by responding to this email and then delete it from your system. We are neither liable for the proper and complete transmission of the information contained in this communication nor for any delay in its receipt.