-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Sun, 19 May 2024 02:44:17 -0700
Source: debian-el
Built-For-Profiles: noudeb
Architecture: source
Version: 37.12
Distribution: unstable
Urgency: medium
Maintainer: Debian Emacsen team
Changed-By: Xiyue Deng
Closes: 1032662
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Tue, 28 May 2024 16:11:38 +0900
Source: debian-reference
Architecture: source
Version: 2.123
Distribution: unstable
Urgency: medium
Maintainer: Osamu Aoki
Changed-By: Osamu Aoki
Changes:
debian-reference (2.123) unstable
Hi,
On Fri, May 24, 2024 at 10:28 PM Otto Kekäläinen wrote:
>
> Hi!
>
> So just to clarify, are you saying that a copy of
> https://security.debian.org/debian-security/dists/buster/ will never
> be archived at https://archive.debian.org/debian-security/dists/ like
> previo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Mon, 27 May 2024 10:33:42 +0200
Source: puppet-module-debian-archvsync
Architecture: source
Version: 1.0.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian OpenStack
Changed-By: Thomas Goirand
Changes:
puppet-module
Hi!
So just to clarify, are you saying that a copy of
https://security.debian.org/debian-security/dists/buster/ will never
be archived at https://archive.debian.org/debian-security/dists/ like
previous releases have been so far?
This is not about getting *new security updates*, but purely
Quoting Bill Allombert (2024-05-24 10:54:32)
> Le Fri, May 24, 2024 at 09:30:44AM +0200, Bastian Venthur a écrit :
> > Hi,
> >
> > I'm having troubles finding the relevant parts in the developers reference.
> > I've uploaded a version to experimental and later found out that this
> > version
Le Fri, May 24, 2024 at 09:30:44AM +0200, Bastian Venthur a écrit :
> Hi,
>
> I'm having troubles finding the relevant parts in the developers reference.
> I've uploaded a version to experimental and later found out that this
> version fixes several bugs.
>
> Can I rewrite existing changelog
Quoting Andrey Rakhmatullin (2024-05-24 09:37:45)
> On Fri, May 24, 2024 at 09:30:44AM +0200, Bastian Venthur wrote:
> > I'm having troubles finding the relevant parts in the developers reference.
> > I've uploaded a version to experimental and later found out that this
> > version fixes several
On Fri, May 24, 2024 at 09:30:44AM +0200, Bastian Venthur wrote:
> I'm having troubles finding the relevant parts in the developers reference.
> I've uploaded a version to experimental and later found out that this
> version fixes several bugs.
>
> Can I rewrite existing changelog entries for
the relevant "closes" line to the
previsions version?
Cheers,
Bastian
--
Dr. Bastian Venthur https://venthur.de
Debian Developer venthur at debian org
remote pointing at the maintainer's
history. So it sort of does this. We could make it do more.
Huh. Than my workflow hides this. All I'm often seeing is just the tar
content represented in a commit, the latest Debian packing in another
and the merge of these two (if I recall and describe what I
; I find doing a code review in a web page far more frustrating than in
> email.
There are external paid integrations for gitlab which provide the
feature to send emails with full diffs for projects, so there should be
a way to add this feature to the Debian gitlab. I would guess by using
the API.
You ca
Hi!
On Sun, 19 May 2024 at 20:48, Don Armstrong wrote:
>
> On Sun, 19 May 2024, Bill Allombert wrote:
> > Also debbugs is a special case:
> > The debbugs Debian package (as opposed to the debbugs software) have never
> > been
> > really maintained. I am actu
ecause I have, I do use it in my day job, and I
don't really like it that much.
Even so, I think it is enough better that Debian should move in that
direction.
But Otto, I would encourage you to have more compassion for people who
work with the world differently than you.
In this thread, and in
On Tue, 21 May 2024 at 14:13, Andrey Rakhmatullin wrote:
>
> On Tue, May 21, 2024 at 08:45:50PM +0900, Simon Richter wrote:
> > Hi,
> >
> > On 5/21/24 15:54, Andrey Rakhmatullin wrote:
> >
> > > > The Debian archive itself is
On Mon, May 20, 2024 at 04:11:02AM +0900, Simon Richter wrote:
> The Debian archive itself is a VCS, so git-maintained packaging is also a
> duplication, and keeping the official VCS and git synchronized is causing
> additional work for developers, which is why people are opposed
On Tue, May 21, 2024 at 08:45:50PM +0900, Simon Richter wrote:
> Hi,
>
> On 5/21/24 15:54, Andrey Rakhmatullin wrote:
>
> > > The Debian archive itself is a VCS, so git-maintained packaging is also a
> > > duplication, and keeping the official VCS and git synchroniz
Hi,
On 5/21/24 15:54, Andrey Rakhmatullin wrote:
The Debian archive itself is a VCS, so git-maintained packaging is also a
duplication, and keeping the official VCS and git synchronized is causing
additional work for developers, which is why people are opposed to having it
mandated
Hello,
On Sun 19 May 2024 at 10:05am +02, Paul Gevers wrote:
>
> PS: I've always wondered if the dgit server shouldn't track history, even if
> uploads don't happen via it. A dgit clone could (should?) already provide
> available history, even if no upload happened via it yet.
Well, 'dgit
Hello,
On Sun 19 May 2024 at 12:32pm -07, Otto Kekäläinen wrote:
> You could go to
> https://salsa.debian.org/debbugs-team/debbugs/-/merge_requests/19 and
> conduct a code review?
>
> You might discover that GitLab is useful and is not duplicating
> Debbugs or anyth
On Mon, May 20, 2024 at 04:11:02AM +0900, Simon Richter wrote:
> > My concern about Gitlab is not its *additions* to existing services, but
> > its *duplications* of core services already in Debian.
>
> I agree, that's the key problem.
>
> The Debian archive itself is
On Sun, May 19, 2024 at 08:38:58PM -0700, Don Armstrong wrote:
> On Sun, 19 May 2024, Bill Allombert wrote:
> > Also debbugs is a special case:
> > The debbugs Debian package (as opposed to the debbugs software) have never
> > been
> > really maintained. I am actuall
"Theodore Ts'o" writes:
> On Sun, May 12, 2024 at 04:27:06PM +0200, Simon Josefsson wrote:
>> Going into detail, you use 'gzip -9n' but I use git-archive defaults
>> which is the same as -n aka --no-name. I agree adding -9 aka --best is
>> an improvement. Gnulib's maint.mk also add
> > Ideally debbugs should be made non-native so that some else could
> > maintain the Debian package.
>
> I'm happy to review patches that get the 2.6 branch of debbugs in shape
> where it can be released into Debian again if someone wants to take that
> effort. I've
security) for versions with extended support.
https://archive.debian.org/debian/dists/
https://security.debian.org/debian-security/dists/
This point you mentioned is relevant. I will be following the finally of
this conversation.
Look, I hope I helped in some way and I realize that many users don't
On Sat, 23 Mar 2024 at 01:32, Ansgar wrote:
>
> Hi,
>
> Debian 10 "buster" has moved to archive.debian.org in order to free
> space on the main mirror network. We plan to start removing files for
> non-LTS architectures in about two weeks; the existing Rel
On Sun, 19 May 2024, Bill Allombert wrote:
> Also debbugs is a special case:
> The debbugs Debian package (as opposed to the debbugs software) have never
> been
> really maintained. I am actually one of the very few users of this package
> and I tried several times to get the ma
Hi,
On 5/20/24 04:32, Otto Kekäläinen wrote:
I agree that duplication is bad - but I disagree that use of version
control duplicates the use of the Debian archive for source code
storage, or that use of GitLab for code reviews would duplicate
Debbugs.
Outside of DM uploads, I'm not sure
Thanks for reply Jonas,
> > You could go to
> > https://salsa.debian.org/debbugs-team/debbugs/-/merge_requests/19 and
> > conduct a code review?
> >
> > You might discover that GitLab is useful and is not duplicating
> > Debbugs or anything else in Debian
Quoting Otto Kekäläinen (2024-05-19 21:32:36)
> > > My concern about Gitlab is not its *additions* to existing services, but
> > > its *duplications* of core services already in Debian.
> >
> > I agree, that's the key problem.
>
> I agree that duplicat
> > My concern about Gitlab is not its *additions* to existing services, but
> > its *duplications* of core services already in Debian.
>
> I agree, that's the key problem.
I agree that duplication is bad - but I disagree that use of version
control duplicates the use of
Hi,
On 5/19/24 16:11, Jonas Smedegaard wrote:
My concern about Gitlab is not its *additions* to existing services, but
its *duplications* of core services already in Debian.
I agree, that's the key problem.
The Debian archive itself is a VCS, so git-maintained packaging is also
On Sat, May 18, 2024 at 08:25:10PM -0700, Otto Kekäläinen wrote:
> Hi Bill and Wookey!
>
> In a recent long thread on debian-devel you had somewhat negative
> sentiments towards the usefulness of Salsa.
I am not sure this characterize my position. I have no opposition to
Salsa
Quoting Mathias Behrle (2024-05-19 11:08:58)
> * Jonas Smedegaard: " Re: Salsa - best thing in Debian in recent years? (Re:
> finally end single-person maintainership)" (Sun, 19 May 2024 10:47:38
> +0200):
>
>
> > i.e. you are being
> > asocial if you don'
* Jonas Smedegaard: " Re: Salsa - best thing in Debian in recent years? (Re:
finally end single-person maintainership)" (Sun, 19 May 2024 10:47:38 +0200):
> i.e. you are being
> asocial if you don't, and can expect your behavior being discussed as a
> public-wide issue f
t; consequences. Than I think this discussion is going to be moot. I don't
> think there's much forcing possible and I think most already agree that
> stuff *should* be in VCS, so this isn't going to change for those in
> favor. And does it really add enough value if those that ar
Two mistakes spotted
On 19-05-2024 10:05 a.m., Paul Gevers wrote:
I think there's a large majority (maybe
even consensus) that believe you *should* have the packaging in VCS
I meant "at least should", as in "should or must".
I think what pere did [3]
[3]
so this isn't going to change for those in
favor. And does it really add enough value if those that are forced are
just going to do "gbp import-dsc" for each upload to the archive on a
./debian only repository? Because that (or better) we could already
automate (see also my PS).
I'm again
Quoting Otto Kekäläinen (2024-05-19 05:25:10)
> In a recent long thread on debian-devel you had somewhat negative
> sentiments towards the usefulness of Salsa. I do see you doing good
> technical work for Debian and recently a MR from Bill too, so I was
> thinking that maybe you will
Hi Bill and Wookey!
In a recent long thread on debian-devel you had somewhat negative
sentiments towards the usefulness of Salsa. I do see you doing good
technical work for Debian and recently a MR from Bill too, so I was
thinking that maybe you will change your mind when you read more
in-depth
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Sat, 18 May 2024 22:50:49 +0200
Source: debian-science
Architecture: source
Version: 1.14.6
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Team
Changed-By: Andreas Tille
Changes:
debian-science (1.14.6
+debian-live
Hello Aditya,
On 11/05/2024 10:21, Aditya Garg wrote:
I wanted to create a custom ISO of Debian, with the following customisations:
1. I want to add a custom kernel that supports my Hardware.
2. I want to add my own Apt repo which hosts various software packages to
support my
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Sat, 18 May 2024 06:07:53 +
Source: rust-assorted-debian-utils
Architecture: source
Version: 0.7.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Rust Maintainers
Changed-By: Peter Michael Green
Changes:
rust
t; It cannot be redistributed legally.
You can still use the netinstall image. Its smaller, easier to
distribute and you or a user can add new things. You don't need to
distribute large parts of Debian just to replace the kernel and add a
repo.
But at the end the installers are all similar, it shouldn't make
ux
kernel and to the Debian Linux kernel packages and to Debian itself.
--
bye,
pabs
https://wiki.debian.org/PaulWise
signature.asc
Description: This is a digitally signed message part
rin Rodrigues
> wrote:
>
> Hi,
>
> I'm removing debian-project from the recipients.
>
> Quoting Aditya Garg (2024-05-11 10:21:55)
>> I wanted to create a custom ISO of Debian, with the following customisations:
>>
>> 1. I want to add a custom kernel that
Hi,
I'm removing debian-project from the recipients.
Quoting Aditya Garg (2024-05-11 10:21:55)
> I wanted to create a custom ISO of Debian, with the following customisations:
>
> 1. I want to add a custom kernel that supports my Hardware.
> 2. I want to add my own Apt repo which h
Well it's indeed not as easy as I thought as far as Debian ISOs are concerned.
I'll try to be more precise. I am a maintainer for Ubuntu on Linux on T2 Macs
project: https://t2linux.org/.
We work to modify ISOs of commonly used distros by adding a custom kernel with
drivers for T2 Macs
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Wed, 15 May 2024 09:56:16 +0200
Source: debian-security-support
Architecture: source
Version: 1:13+2024.05.15
Distribution: unstable
Urgency: medium
Maintainer: Debian Security Team ,
Changed-By: Holger Levsen
Closes: 1063756
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Tue, 14 May 2024 18:07:54 +0200
Source: debian-security-support
Architecture: source
Version: 1:13+2024.05.14
Distribution: unstable
Urgency: medium
Maintainer: Debian Security Team ,
Changed-By: Holger Levsen
Changes:
debian
her autoconf
or the aclocal macros changing in incompatible ways between versions.
So my practice is to check into git the configure script as generated
by autoconf on Debian testing, which is my development system; and if
it fails on anything else, or when a new version of autoconf or
automake, etc.
Ansgar writes:
> In ecosystems like NPM, Cargo, Golang, Python and so on pinning to
> specific versions is also "explicitly intended to be used"; they just
> sometimes don't include convenience copies directly as they have tooling
> to download these (which is not all
e.
>
> No, there's an explicit exception for cases like gnulib. Policy 4.13:
>
> Some software packages include in their distribution convenience
> copies of code from other software packages, generally so that users
> compiling from source don’t have to downloa
is a bit differently from how we treat
> other C shared libraries, where we claim that *all* libraries must be
> dynamically linked, and that include source code by reference is against
> Debian Policy, precisely because of the toil needed to update all of the
> binary packages sh
ame --best --rsyncable > -o inetutils-$(git describe)-src.tar.gz
>> To reach our goals in the beginning of this post, this upstream tarball
>> has to be filtered to remove all pre-generated artifacts and vendored
>> code. Use some mechanism, like the debian/copyright File
post, this upstream tarball
> has to be filtered to remove all pre-generated artifacts and vendored
> code. Use some mechanism, like the debian/copyright Files-Excluded
> mechanism to remove them. If you used a git-archive upstream tarball,
> chances are higher that you won't have
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Thu, 09 May 2024 00:18:46 +0200
Source: rshim-user-space
Architecture: source
Version: 2.0.20+debian-3
Distribution: unstable
Urgency: medium
Maintainer: da...@debian.org
Changed-By: Taihsiang Ho (tai271828)
Closes: 1064920
On 2024-05-11 07:09, Simon Josefsson via Gnulib discussion list wrote:
I would assume that (some stripped down
version of) git is a requirement to do any useful work on any platform
these days, so maybe it isn't a problem
Yes, my impression also is that Git has migrated into the realm of
gt; * 'cargo fetch' for Rust source code packages [2],
>
> except that gnulib-tool is simpler: it fetches from a single source location
> only.
>
> How does Debian handle these kinds of source-code dependencies?
I don't know the details but I believe those commands are turned into
lo
except that gnulib-tool is simpler: it fetches from a single source location
only.
How does Debian handle these kinds of source-code dependencies?
Bruno
[1]
https://nodejs.org/en/learn/getting-started/an-introduction-to-the-npm-package-manager
[2] https://doc.rust-lang.org/cargo/commands/cargo-fetch.html
Am Samstag, 11. Mai 2024, 10:21:55 CEST schrieb Aditya Garg:
> Hello
>
> I wanted to create a custom ISO of Debian, with the following
> customisations:
>
> 1. I want to add a custom kernel that supports my Hardware.
> 2. I want to add my own Apt repo which hosts vari
All, (going out to both debian-devel and bug-gnulib, please be
respectful of each community's different perspectives and trim Cc
when focus shifts to any Debian or gnulib specific topics)
(please pardon the accidental duplicate post to bug-gnulib...)
The content of upstream
On 5/11/24 16:21, Aditya Garg wrote:
Hello
I wanted to create a custom ISO of Debian, with the following customisations:
1. I want to add a custom kernel that supports my Hardware.
2. I want to add my own Apt repo which hosts various software packages to
support my hardware.
I am not able
* Aditya Garg [240511 05:15]:
> Hello
>
> I wanted to create a custom ISO of Debian, with the following customisations:
>
> 1. I want to add a custom kernel that supports my Hardware.
> 2. I want to add my own Apt repo which hosts various software packages to
> support m
Hello
I wanted to create a custom ISO of Debian, with the following customisations:
1. I want to add a custom kernel that supports my Hardware.
2. I want to add my own Apt repo which hosts various software packages to
support my hardware.
I am not able to get any good documentation
Hello
I wanted to create a custom ISO of Debian, with the following customisations:
1. I want to add a custom kernel that supports my Hardware.
2. I want to add my own Apt repo which hosts various software packages to
support my hardware.
I am not able to get any good documentation
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sat, 11 May 2024 07:05:42 +0200
Source: nmon
Architecture: source
Version: 16q+debian-1
Distribution: unstable
Urgency: medium
Maintainer: Salvatore Bonaccorso
Changed-By: Salvatore Bonaccorso
Changes:
nmon (16q+debian-1
Hi Charles,
* Charles Plessy [2024-05-08 07:27]:
I want to leverage our cluster to automate as much of the rebuilds
as I
can, but could not find the right tool. I tried to run sbuild in a
Singularity image and this failed. However, I do not need the whole
power of engines like sbuild, as
Le Wed, May 08, 2024 at 08:02:41AM -0700, Otto Kekäläinen a écrit :
>
> I read the docs on how Singularity is able to pull Docker images of Debian
> Sid and build on top of them, and run and exec just like Docker/Podman.
> Unfortunately it has its own Containerfile form
t; Podman? Our cluster runs only singularity 3.5.2
> (https://docs.sylabs.io/guides/3.5/user-guide/). Debian has version
> 4.1.2 in the singularity-container package.
>
> The conversion of a Docker container to the Singularity format is
> simple, and Singularity already mounts most of th
rts running Podman in user mode (=no root permissions needed),
Hi Otto,
it looks really great!
Do you think you can make it work with Singularity/Apptainer instead of
Podman? Our cluster runs only singularity 3.5.2
(https://docs.sylabs.io/guides/3.5/user-guide/). Debian has version
4.1.2
engines like sbuild, as none of the packages involved require
> root priviledges to build.
>
> Do you have a suggestion for a tool can run in user mode in a container
> image having access to local storage on the host, and that given a
> Debian source control file will download
Hello everybody,
I just re-suscribed :)
At work I have access to a nice cluster with plenty of nodes rich of 128
cores and 512 Gb RAM. The nodes do not run Debian but Singularity is
available for virtualisation
(https://en.wikipedia.org/wiki/Singularity_(software)).
And in Debian I am part
Package: wnpp
Severity: wishlist
Owner: Emmanuel Arias , Santiago Ruano Rincón
X-Debbugs-Cc: debian-devel@lists.debian.org, t...@security.debian.org,
debian-ker...@lists.debian.org, debian-...@lists.debian.org, eam...@debian.org
* Package name: linux-livepatching
Version
), the Debian Technical Committee
has recommended the appointment to the committee of:
* Craig Small
I agree with their recommendation, and hereby appoint Craig as member of
the Technical Committee, effective immediately.
For reference, the nominations and votes are recorded at:
https
-tracking system.
--
1065810: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065810
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
On Fri, Apr 19, 2024 at 07:59:19AM +0100, Sean Whitton wrote:
> Hello Go and Rust packagers,
>
> On Thu 18 Apr 2024 at 11:29pm +03, Maytham Alsudany wrote:
>
> > With the increasing amount of programs in Debian that Build-Depend and
> > statically link with Golang
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sat, 20 Apr 2024 19:26:49 +0200
Source: rshim-user-space
Architecture: source
Version: 2.0.20+debian-2
Distribution: unstable
Urgency: medium
Maintainer: da...@debian.org
Changed-By: Taihsiang Ho (tai271828)
Closes: 1064920
On 22/4/24 21:29, Steve Langasek wrote:
On Mon, Apr 22, 2024 at 05:11:39PM +0200, José Luis González González wrote:
I sent 5 minutes ago an email to "Plaza de Castilla *courts*" setting
^^^
BS. It just doesn't work like this. A regular citizen can't communicate
solved.
>
> "Kinda or not"
>
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developer https://www.debian.org/
slanga...@ubuntu.com
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Mon, 22 Apr 2024 08:59:25 +0700
Source: ncrack
Architecture: source
Version: 0.7+debian-6
Distribution: unstable
Urgency: medium
Maintainer: Debian Security Tools
Changed-By: Arnaud Rebillout
Closes: 1065799
Changes:
ncrack (0.7
Greetings,
This message is an automated, unofficial publication of vote results.
Official results shall follow, sent in by the vote taker, namely
Debian Project Secretary
This email is just a convenience for the impatient.
I remain, gentle folks,
Your humble servant
ating system. This has happened before, thrice recently.
> > >
> > > Additionally the files on /usr/share/doc/dash are wrong.
> > >
> > > The main issues of mutt that I know so far is the documentation is
> > > useless for what I needed, which is using the pro
You've written a lot of text here in a few mails, replying to yourself
several times. This is not a positive pattern.
On Fri, Apr 19, 2024 at 11:58:18AM +0200, José Luis González González wrote:
>> There are similar issues with boa and dhttpd, and it seems Apache is going
>> that way.
>
>nvi
ating system. This has happened before, thrice recently.
> > >
> > > Additionally the files on /usr/share/doc/dash are wrong.
> > >
> > > The main issues of mutt that I know so far is the documentation is
> > > useless for what I needed, which is using the pro
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sun, 24 Mar 2024 09:03:13 +
Source: debian-keyring
Architecture: source
Version: 2024.03.24
Distribution: unstable
Urgency: medium
Maintainer: Debian Keyring Maintainers
Changed-By: Jonathan McDowell
Changes:
debian-keyring
far is the documentation is
> > useless for what I needed, which is using the program, and the package,
> > that was installed, is missing from my computer, besides the maintainer
> > being subversive as well.
> >
> > If this is not solved I will cease to stop using De
r
> being subversive as well.
>
> If this is not solved I will cease to stop using Debian and Debian will
> die.
>
> "Kinda or not"
The problems that I had in 2020 were life or death security problems
that prevented me to use my computer at all for almost one year. I
Hello Go and Rust packagers,
On Thu 18 Apr 2024 at 11:29pm +03, Maytham Alsudany wrote:
> With the increasing amount of programs in Debian that Build-Depend and
> statically link with Golang and Rust libraries, it's important that
> the Debian Policy clearly sets out the req
Package: debian-policy
Version: 4.7.0.0
Severity: normal
X-Debbugs-Cc: debian-devel@lists.debian.org
Dear Policymakers,
With the increasing amount of programs in Debian that Build-Depend and
statically link with Golang and Rust libraries, it's important that the
Debian Policy clearly sets out
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Wed, 17 Apr 2024 14:53:41 +0700
Source: dsniff
Architecture: source
Version: 2.4b1+debian-33
Distribution: unstable
Urgency: medium
Maintainer: Debian Security Tools
Changed-By: Arnaud Rebillout
Closes: 1066431
Changes:
dsniff
On Thu, Apr 11, 2024 at 04:46:03PM +, mYnDstrEAm wrote:
> With the two commands above one can already split it up into two steps but
> especially the second command still requires a lot of disk space.
I am going to assume that your "a lot of disk space" stems from the
*.deb files that are
gt;
quick and dirty and not tested:
while apt -s upgrade | grep '^Inst' | head -1 | awk '{print $2}' |
xargs apt install; do apt clean; done
Use head -10 or whatever fits for more/less packages.
--
Bernd ZeimetzDebian GNU/Linux Developer
http://bzed.de
Please do it yourself by following the instructions here:
https://lists.debian.org/debian-devel/
Maycon Antônio wrote on 08/04/2024 at 17:44:20+0200:
> Please cancel my name from this list, thank you.
>
> On Sun, 7 Apr 2024 at 12:32, Sean Whitton wrote:
>>
>> Hello e
Package: general
A distro upgrade of Debian needs a lot of disk space on the root partition.
That partition often doesn't have a large size. That could for example be
because it's on a mobile device, on a SSD drive, has lots of installed
software, or because the user simply followed the advice
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Thu, 11 Apr 2024 08:08:27 +0900
Source: debian-reference
Architecture: source
Version: 2.122
Distribution: unstable
Urgency: medium
Maintainer: Osamu Aoki
Changed-By: Osamu Aoki
Changes:
debian-reference (2.122) unstable
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Thu, 11 Apr 2024 01:31:20 +0200
Source: debian-edu-artwork
Architecture: source
Version: 2.12.4-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Edu Developers
Changed-By: Holger Levsen
Closes: 1040296
Changes:
debian
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Wed, 10 Apr 2024 20:08:55 +
Source: xerces-c
Architecture: source
Version: 3.2.4+debian-1.3
Distribution: unstable
Urgency: medium
Maintainer: William Blough
Changed-By: Bastian Germann
Closes: 1067309
Changes:
xerces-c
Please cancel my name from this list, thank you.
On Sun, 7 Apr 2024 at 12:32, Sean Whitton wrote:
>
> Hello everyone,
>
> I just pushed version 4.7.0.0 of the Debian Policy Manual and related
> documents to sid. Below you will find the significant normative changes
> f
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sun, 07 Apr 2024 22:44:35 +0200
Source: rust-assorted-debian-utils
Architecture: source
Version: 0.7.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Rust Maintainers
Changed-By: Sebastian Ramacher
Changes:
rust
1 - 100 of 32668 matches
Mail list logo
