Package: apt-move
Version: 4.2.27-6
Severity: important
Tags: patch
X-Debbugs-Cc: leeejobsacco...@mail.co.uk
Dear Maintainer,
* What led up to the situation?
I ran apt-move packages and found that when I then ran apt-update it reported
the
following warning:
mirrors/debian bookworm
Your message dated Tue, 16 Apr 2024 21:02:22 +0200
with message-id
and subject line Re: apt-move rebuilt with the wrong ABI on 32-bit architectures
has caused the Debian Bug report #1065069,
regarding apt-move rebuilt with the wrong ABI on 32-bit architectures
to be marked as done.
This means
apt-move 4.2.27-6 is marked for autoremoval from testing on 2024-03-29
It is affected by these RC bugs:
1065069: apt-move: apt-move rebuilt with the wrong ABI on 32-bit architectures
https://bugs.debian.org/1065069
This mail is generated by:
https://salsa.debian.org/release-team/release-tools
apt-move 4.2.27-6 is marked for autoremoval from testing on 2024-03-29
It is affected by these RC bugs:
1065069: apt-move: apt-move rebuilt with the wrong ABI on 32-bit architectures
https://bugs.debian.org/1065069
This mail is generated by:
https://salsa.debian.org/release-team/release-tools
r'
Bug reassigned from package 'gtk-theme-qogir' to 'wnpp'.
Ignoring request to alter found versions of bug #1065090 to the same values
previously set
Ignoring request to alter fixed versions of bug #1065090 to the same values
previously set
> notfound 1065069 apt-move/4.
Source: apt-move
Version: 4.2.27-6+b1
Severity: serious
X-Debbugs-Cc: debian-rele...@lists.debian.org
apt-move has been binNMUed for the time64_t transition. However due to
the lack of extra-depends and the impossibility to recreate chroots on
the buildd, it has been built with pre time64_t
apt-move 4.2.27-6 is marked for autoremoval from testing on 2022-06-30
It (build-)depends on packages with these RC bugs:
1011146: nvidia-graphics-drivers-tesla-470: CVE-2022-28181, CVE-2022-28183,
CVE-2022-28184, CVE-2022-28185, CVE-2022-28191, CVE-2022-28192
https://bugs.debian.org/1011146
s manual (that's its German title) which
utilises apt-move. The shell script /usr/bin/apt-move produces a Release file
that apt-get on a Linux VM describes as "having no hashes" (probably because in
its sources.list we use [trusted=yes] – the packages come from our safe
server!). A
apt-move 4.2.27-6 is marked for autoremoval from testing on 2020-03-23
It is affected by these RC bugs:
930663: apt-move: Port to apt 1.9
Your message dated Sun, 08 Mar 2020 13:49:05 +
with message-id
and subject line Bug#930663: fixed in apt-move 4.2.27-6
has caused the Debian Bug report #930663,
regarding apt-move: Port to apt 1.9
to be marked as done.
This means that you claim that the problem has been dealt with.
If this
Processing commands for cont...@bugs.debian.org:
> limit source apt-move
Limiting to bugs with field 'source' containing at least one of 'apt-move'
Limit currently set to 'source':'apt-move'
> tags 930663 + pending
Bug #930663 [apt-move] apt-move:
apt-move 4.2.27-5 is marked for autoremoval from testing on 2020-03-22
It is affected by these RC bugs:
930663: apt-move: Port to apt 1.9
Processing commands for cont...@bugs.debian.org:
> reassign 700368 apt-move
Bug #700368 [debootstrap] debootstrap does not work with local file mirror
(apt-move)
Bug reassigned from package 'debootstrap' to 'apt-move'.
No longer marked as found in versions debootstrap/1.0.
Package: apt-move
Version: 4.2.27-5
Severity: normal
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu eoan ubuntu-patch
In Ubuntu, the attached patch was applied to achieve the following:
* Port to apt 1.9
Thanks for considering the patch.
-- System Information
Package: apt-move
Version: 4.2.27-5
Severity: normal
Tags: patch pending
Dear maintainer,
I've prepared an NMU for apt-move (versioned as 4.2.27-5.1) and
the patch fixes a small issue found with apt-move. It is reported
on many lists, and some folks have done hacks around this.
Regards.
Package: apt-move
Version: 4.2.27-5
Severity: normal
Tags: patch pending
[Replace XX with correct value]
Dear maintainer,
I've prepared an NMU for apt-move (versioned as 4.2.27-5.1) and
the attached small fix fixes a long reported issue with running
apt-move.
Regards.
diff -Nru apt
more likely with increasing 'capacity' of
the server hardware.
Devuan 1.0 Jessie.
Dual Core E8400 @ 3.00GHz
awk -> mawk
apt-move 4.2.27-3
--
M
> There's no way around this unless apt-get starts supporting cross-arch
> downloads.
Well it does, if your system is multiarch.
I just tried to apt-move my amd64 and i386 packages, and lo and behold,
it only moves amd64 ones. Actually, the code looks as if it only expects
one arch
angs every time. This is not good since I have 'apt-move update' as
part of my daily cron jobs and hanging kills the execution of the other
parts.
I can reduce the severity of the bug by restricting the process to one cpu
using taskset. The process fails but completes.
Apt-move is act
Package: apt-move
Version: 4.2.27-3
Severity: important
I created a patch for apt-move to add sha256 support for
- the Release file
- the Packages files
- the Sources files
On a wheezy system I installed apt-move_4.2.27-3_i386.deb and just
after the installation of the deb file the patch can
Package: apt-move
Version: 4.2.27-1
Severity: important
I created a patch for apt-move to add sha256 support for
- the Packages files
- the Sources files
This patch also includes to former patches for version 4.2.27-1 so
it also adds sha256 support for
- The Release file
On a squeeze system
I can reproduce this bug with apt-move 4.2.27-2, here in line 1232.
--
To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/50cb247c.8010...@gmx.com
Your message dated Fri, 09 Nov 2012 11:32:25 +
with message-id
and subject line Bug#692342: fixed in apt-move 4.2.27-3
has caused the Debian Bug report #692342,
regarding apt-move uses obsolete implicit split functionality
to be marked as done.
This means that you claim that the problem has
retitle 639770 apt-move: fails to open fifo-file and hangs
tags 639770 + unreproducible
retitle 398297 apt-move: wrong version selected if containing tilde '~'
merge 398297 539524
retitle 692342 apt-move uses obsolete implicit split functionality
tags 692342 + pending, patch
thanks
Seem
Processing commands for cont...@bugs.debian.org:
> retitle 639770 apt-move: fails to open fifo-file and hangs
Bug #639770 [apt-move] apt-move doesn't work anymore
Changed Bug title to 'apt-move: fails to open fifo-file and hangs' from
'apt-move doesn't
control: tag -1 confirmed
Confirming that "apt-move get && apt-move move" behaves like this.
Building and installing 4.2.27-1 on wheezy doesn't help. Testing on
squeeze, it does work.
Best wishes,
Mike
--
To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debia
Processing control commands:
> tag -1 confirmed
Bug #692342 [apt-move] apt-move move command deletes all files without moving
them
Added tag(s) confirmed.
--
692342: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=692342
Debian Bug Tracking System
Contact ow...@bugs.debian.org with probl
Package: apt-move
Version: 4.2.27-2+b1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
I have for a long period of time (many years, i have been using linux since
kernel 0.96d, 20 years ago) been using apt-move to maintain my own repository
as I have
poor internet
Package: apt-move
Version: 4.2.27-2+b1
Followup-For: Bug #398297
Dear Maintainer,
Debian Wheezy have too.
-- System Information:
Debian Release: wheezy/sid
APT prefers testing-proposed-updates
APT policy: (500, 'testing-proposed-updates'), (500, 'testing'), (1,
'ex
The bug is also in apt-move 4.2.27-2 (from Ubuntu 12.04 repo). The
solution by Robert works like a charm. Thanks Robert!
smime.p7s
Description: S/MIME Cryptographic Signature
Hi,
Please use this patch instaed. I added my self as a copyright holder
because I added a bit of code.
sincerely yours
Mario
diff -Naur orig/usr/bin/apt-move new/usr/bin/apt-move
--- orig/usr/bin/apt-move 2012-03-31 20:32:03.0 +0200
+++ new/usr/bin/apt-move 2012-03-31 22:47
Hi,
I created a patch to solve the issue and attached it to that email.
After the patch is applied the apt-move supports MD5, SHA1 and SHA256
sums.
This patch includes the changed of my old patch attached to the bug so
only this patch needs to be applied.
I think this is a huge step forward
Hi:
Do we still need MD5 sums in the Packages file? If not I'd
suggest simply changing all existing references to md5 with
sha256 and it should just work.
Cheers,
--
Email: Herbert Xu
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
--
Package: apt-move
Version: 4.2.27-1+b8
Severity: important
Hi
I managed to add SHA256 Lines to the Release file. I have created a
patch for apt-move to fix the issue. I have attached this patch to
this bug report via email.
But I don't know yet how to add these SHA256 lines into the Pac
Your message dated Sun, 21 Nov 2004 18:17:04 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#242272: fixed in apt-move 4.2.23
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it
35 matches
Mail list logo
