Sune Vuorela dixit:
>In theory. I don't know if there are any statistics on 'popular'
>3rdparty repositories and their keys. But assuming they're doing key
Hm. My own private repo should be ok (3072R), but my Launchpad PPAs
incidentally are not okay (1024D).
Since this comes from Canonical,
reopen 1063905
severity 1063905 wishlist
retitle 1063905 mksh: add /usr/bin/mksh{,-static} to /etc/shells
tags 1063905 + pending
found 1063905 59c-23
# well /usr/bin/mksh, /usr/bin/mksh-static is not, see below
notfound 1063905 59c-22
thanks
Russ Allbery dixit:
>After some research with git
Russ Allbery dixit:
>Thorsten Glaser writes:
>
>> Right… and why does pkexec check against /etc/shells?
>
>pkexec checks against /etc/shells because this is the traditional way to
>determine whether the user is in a restricted shell, and pkexec is
>essentially a
Russ Allbery dixit:
>It does check whether $SHELL is found in /etc/shells. So your question
>about what is setting the $SHELL variable is a good one, although I think
>I would still argue that it's not the most effective way to solve the
>issue.
Right… and why does pkexec check against
Dixi quod…
>Russ Allbery dixit:
>
>>> What sets $SHELL for the reporter’s case? Fix that instead. login(1)
>>> sets it to the path from passwd(5), which hopefully is from shells(5).
>>
>>My guess is that pkexec is calling realpath to canonicalize the path
>>before checking for it in /etc/shells,
Russ Allbery dixit:
>> What sets $SHELL for the reporter’s case? Fix that instead. login(1)
>> sets it to the path from passwd(5), which hopefully is from shells(5).
>
>My guess is that pkexec is calling realpath to canonicalize the path
>before checking for it in /etc/shells, although I have
Russ Allbery dixit:
>3. Something else that I don't yet understand happened that caused pkexec
> to detect the shell as /usr/bin/mksh instead of /bin/mksh. I'm not
What sets $SHELL for the reporter’s case? Fix that instead.
login(1) sets it to the path from passwd(5), which hopefully
is from
Matthias Klose dixit:
> you can work around it
Unfortunately not. (The musl packagers might be able to.)
>, this is not an RC issue. Please stop playing
> bug ping pong.
If GCC stops supporting an option it used to support,
and where the GCC documentation say it’s supported,
it in my opinion
Helmut Grohne dixit:
>> > rng-tools-debian
>>
>> Also false positive:
>>
>> Replaces: intel-rng-tools, rng-tools
>> Breaks: rng-tools (>= 5migratf), rng-tools (<< 5migrate)
>> Conflicts: intel-rng-tools
>
>This is *not* a false positive, but a real issue. It replaces any
>rng-tools, but
Simon McVittie dixit:
>opt-in to (2.) is available via -D_FILE_OFFSET_BITS=64 for the subset
>of libraries that can support it without breaking ABI, and similarly
Right, but e.g. refuses to work under it.
>That wasn't actually the reason for my concern. As far as I'm aware, the
>glibc dynamic
Helmut Grohne dixit:
> openjdk-8 (U)
Should be convered by the Depends lines in the respective
binary packages, e.g:
Depends: openjdk-8-jre (>= ${source:Version}),
openjdk-8-jdk (>= ${binary:Version}),
${misc:Depends}
Replaces: openjdk-8-jdk (<< 8u20~b26-1~)
> rng-tools-debian
Also
The Wanderer dixit:
>> snes emulator. last upstream release 2007
>>> zsnes deb otherosfs optional arch=any-i386
>
>FWIW: though I haven't touched it in quite some while, I recall from all
FWIW, I occasionally use zsnes and it works well.
But yes, hand-written assembly was part of that IIRC.
Simon McVittie dixit:
>On Wed, 05 Jul 2023 at 17:22:14 +0100, Wookey wrote:
[…]
>> i.e we could keep the existing i386 for the gamers and have i386t64
>> (or whatever we call it) for ongoing use of i386 as a real OS.
>
>On Fri, 09 Jun 2023 at 16:39:38 +, Thorsten Glaser w
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA384
Helmut Grohne dixit:
>I'm inclined to call this consensus now and therefore ask those that do
>not agree with it to reply here - even if your reply is only stating
I disagree.
I would like to see a long-term commitment against electronic waste
Ansgar dixit:
>the stretch, stretch-debug and stretch-proposed-updates suites have now
>also been imported on archive.debian.org. People still interested in
>these should update their sources.list.
Might be useful to note that stretch-updates should be dropped from
sources.list but has been
kilobyte wrote:
>At this point, I'd just enable os-prober unconditionally, and think of a
Erm, *no*?!
os-prober corrupts data when called (in virtualisation/emulation
guests, at the very least).
Steve wrote:
>I'm also pondering tweaking things in d-i to re-enable os-prober if
>the system
Steve McIntyre dixit:
>Please go and *read* and *respond* in debian-vote. The discussion is
>there, not here.
I wrote where the Reply-To pointed to. Perhaps if that had been
correct…
>You've utterly missed Phil's point about people not seeing or hearing
>boot options.
I didn’t. I pointed out
kilobyte dixit:
>Funny thing: there's not a single release architecture that's both
>bad-endian and supports X (they do build X related packages because the
>dependency graph is quite dense, but there are no users). So this
Meh. Remote X, X forwarding over SSH, VNC and RDP servers exist.
So do
Thorsten Glaser dixit:
>PS: Please do Cc me on replies.
Phil Morrell dixit:
>> Is there support for something like A but not enabled by default?
>> That is, you have to actively select a nōn-default option
>
>I don't believe so, because that doesn't solve the problem at
Didier 'OdyX' Raboud dixit:
>If these tests are run at build-time, errors halt the build and that provides
That may not be enough, though; there are cases where the build
architecture determines artefact endianness (e.g. with PCF bitmap
fonts), and that may even be enough (X servers can load
Debian Project Secretary - Kurt Roeckx dixit:
>it are available at: https://www.debian.org/vote/2022/vote_003
Hrm.
Is there support for something like A but not enabled by default?
That is, you have to actively select a nōn-default option in the
boot menu so that the installer loads the
Adam Borowski dixit:
>> These bugs are subtile miscompilations. In mksh, only one test
>> by accident fails due to the GCC LTO bug. It’s definitely *not*
>
>What was the last version of gcc that you have tested?
8, 9 and then-snapshot, i.e. 10 prereleases. So, pretty recent.
>> (As for
Matthias Klose dixit:
>The goal is to enable this optimization by default in an upcoming
>Debian release in dpkg-buildflags for 64bit architectures. The goal
>is to get this package to build with link time optimizations, or to
>explicitly disable link time optimizations for this package build.
Daniel Pocock dixit:
[ nōnsense ]
For all those who also got this eMail despite not being directly
subscribed to d-devel, apparently, “Software Freedom Institute SA”
is Pocock (didn’t someone ask for Init7 to do something about him?)
and blocking 195.8.117.0/24 and 2001:67c:1388::/48 in your
>"apt-get upgrade” doesn’t upgrade the linux-headers to the latest
>fixed version
You need “apt-get upgrade --with-new-pkgs” at the very least to keep
a stable system up-to-date. I use “apt-get --purge dist-upgrade” myself
while keeping an eye on what packages apt wants to remove with that.
Lucas Nussbaum dixit:
>column on https://udd.debian.org/cgi-bin/format10.cgi )
I’m apparently affected at least for cvs, but that package has
another very interesting use case for format 1.0:
Its .diff.gz file can *directly* be used as patch file in no less
than *two* other packaging systems
Paul Gevers dixit:
>
> * **Unblock request** deadline: > 2021-08-03 12:00 UTC <
>
> - You must submit your unblock request *before* then
> - Your changes must be ready to
Andreas Metzler dixit:
>1. Make merged-/usr-via-aliased-dirs the only supported layout and make
>this information available to apt. (Like we did for multi-arch-support.)
>2. After that individual packages can safely move files from / to /usr,
>pre-depending on merged-usr-support.
This will still
Johannes Drexl dixit:
>embrace getting rid of /sbin and /bin. FHS 3.0 explicitely states that
>/usr is allowed to be not only on a separate partition, but even on a
>network device shared by other machines:
This hasn’t been true on Debian for a while (partially due to the
systemd/usrmerge
Marc Haber dixit:
>think we can afford an additional time sink at the moment. Please, get
While that’s true…
>Can we please delay this discussion until after the release? I don't
… we can’t afford to: the TC discussion becomes valid as soon as
bullseye is released, which is in two weeks, and
Guillem Jover dixit:
>I've been meaning to send a note about this for some time now, but
>as I feel it keeps getting ignored, it always seems a bit pointless.
Yeah, I saw this popping up multiple times in that bugreport ☹
>But in any case, given that merged-usr-via-aliased-dirs is not really
Sean Whitton dixit:
>* #978636 move to merged-usr-only?
>
> We were asked to decide whether or not Debian 'bookworm' should
> continue to support systems which are not using the merged-usr
> filesystem layout. We decided that support should not continue beyond
> Debian 'bullseye'.
What?
Hi Paul,
> FTBFS) but it avoids busywork for maintainers that are not involved in
> bootstrapping java. Machine time is cheap, volunteer time is not.
this is not for bootstrapping. This is to prevent building of language
bindings for e.g. Java on platforms where there is simply no Java.
This is
Hello Sean,
>> Does this mean merging copyright headers that differ only,
>> for example, in the copyright years for a given author, is
>> no longer permitted? If so, please consider this a protest
>> from me as that would go against usual and accepted practice.
>
>No, that's still intended to be
Sean Whitton dixit:
>The copyright information for files in a package must be copied
>verbatim into ``/usr/share/doc/PACKAGE/copyright`` when
Does this mean merging copyright headers that differ only,
for example, in the copyright years for a given author, is
no longer permitted? If so,
On Wed, 24 Jun 2020, Emmanuel Bourg wrote:
> Version : 2.0.0~RC1
Given how long some packages stay in milestone status (some for
six years!) I’d prefer for there to be an actual 2.0.0 release
first before this can enter Debian.
bye,
//mirabilos
--
tarent solutions GmbH
Rochusstraße
On Sat, 23 May 2020, Sudip Mukherjee wrote:
> I have now made a list with package name, the jar files that it
> provides and the list of class that the jar provides.
This must be scripted/scriptable though… the list for stable is
pretty much fixed, but the one for unstable (which is the relevant
On Wed, 6 May 2020, Andreas Tille wrote:
> > Or perhaps we need a webpage or wiki page generated by parsing the
> > Contents file and listing the matching Debian package for each class
> > or, at least, Java package (unless split across multiple packages)…
>
> I remember times when such a web
On Wed, 6 May 2020, Andrej Shadura wrote:
> I wonder could we improve the package description and maybe add some
YES please, me either. Why even Geronimo, why not Jakarta’s, which
is the most latest?
> Provides or something to make it clear? I saw changes to packages adding
Or perhaps we need
Package: wnpp
Severity: wishlist
Owner: Thorsten Glaser
* Package name: jamulus
Version : 3.5.1
Upstream Author : Volker Fischer
* URL : http://llcon.sourceforge.net/
* License : GPLv2+
Programming Lang: C++/Qt
Description : real-time collaborative
Arnd Bergmann wrote:
>is clearly needed anyway. Once there is a working armhf version with
>full time64 user space, there can be a separate discussion about what
>to do with the i386 port (phase out i386 before y2038, migrate all of
>i386 to time64 quickly, have two separate i386 ports, or
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA384
Format: 1.8
Date: Mon, 27 Jan 2020 16:45:42 +0100
Source: ksh
Architecture: source
Version: 2020.0.0-5
Distribution: unstable
Urgency: high
Maintainer: Anuradha Weeraman
Changed-By: Thorsten Glaser
Changes:
ksh (2020.0.0-5) unstable; urgency=high
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA384
Format: 1.8
Date: Thu, 23 Jan 2020 00:41:50 +0100
Source: mksh
Architecture: source
Version: 57-5
Distribution: unstable
Urgency: medium
Maintainer: Thorsten Glaser
Changed-By: Thorsten Glaser
Changes:
mksh (57-5) unstable; urgency=medium
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA384
Format: 1.8
Date: Sat, 11 Jan 2020 02:40:04 +0100
Source: xrdp
Architecture: source
Version: 0.9.12-1
Distribution: unstable
Urgency: low
Maintainer: Debian Remote Maintainers
Changed-By: Thorsten Glaser
Closes: 883358 925890
Changes:
xrdp
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA384
Format: 1.8
Date: Sat, 11 Jan 2020 01:14:23 +0100
Source: xorgxrdp
Architecture: source
Version: 1:0.2.12-1
Distribution: unstable
Urgency: low
Maintainer: Debian Remote Maintainers
Changed-By: Thorsten Glaser
Changes:
xorgxrdp (1:0.2.12-1
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA384
Format: 1.8
Date: Wed, 18 Dec 2019 20:11:25 +0100
Source: etckeeper
Architecture: source
Version: 1.18.12-1.1
Distribution: unstable
Urgency: medium
Maintainer: Antoine Beaupré
Changed-By: Thorsten Glaser
Closes: 946055
Changes:
etckeeper
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA384
Format: 1.8
Date: Sun, 01 Dec 2019 21:36:03 +0100
Source: php-htmlpurifier
Architecture: source
Version: 4.11.0-1
Distribution: unstable
Urgency: low
Maintainer: Teckids Debian Task Force
Changed-By: Thorsten Glaser
Changes:
php-htmlpurifier
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA384
Format: 1.8
Date: Sun, 01 Dec 2019 20:42:12 +0100
Source: php-robmorgan-phinx
Architecture: source
Version: 0.9.2-3
Distribution: unstable
Urgency: medium
Maintainer: Teckids Debian Task Force
Changed-By: Thorsten Glaser
Changes:
php-robmorgan
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA384
Format: 1.8
Date: Wed, 20 Nov 2019 00:58:01 +0100
Source: ratchetphp
Architecture: source
Version: 0.4.1-3
Distribution: unstable
Urgency: medium
Maintainer: Teckids Debian Task Force
Changed-By: Thorsten Glaser
Closes: 939193
Changes:
ratchetphp
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA384
Format: 1.8
Date: Wed, 20 Nov 2019 00:22:43 +0100
Source: php-illuminate-database
Architecture: source
Version: 5.8.35-1
Distribution: unstable
Urgency: medium
Maintainer: Teckids Debian Task Force
Changed-By: Thorsten Glaser
Changes:
php
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA384
Format: 1.8
Date: Wed, 20 Nov 2019 00:22:43 +0100
Source: php-illuminate-container
Architecture: source
Version: 5.8.35-1
Distribution: unstable
Urgency: medium
Maintainer: Teckids Debian Task Force
Changed-By: Thorsten Glaser
Changes:
php
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA384
Format: 1.8
Date: Wed, 20 Nov 2019 00:22:43 +0100
Source: php-illuminate-support
Architecture: source
Version: 5.8.35-1
Distribution: unstable
Urgency: medium
Maintainer: Teckids Debian Task Force
Changed-By: Thorsten Glaser
Changes:
php
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA384
Format: 1.8
Date: Wed, 20 Nov 2019 00:48:29 +0100
Source: php-robmorgan-phinx
Architecture: source
Version: 0.9.2-2
Distribution: unstable
Urgency: medium
Maintainer: Teckids Debian Task Force
Changed-By: Thorsten Glaser
Closes: 939191
Changes
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA384
Format: 1.8
Date: Wed, 20 Nov 2019 00:39:56 +0100
Source: php-nesbot-carbon
Architecture: source
Version: 1.27.0-2
Distribution: unstable
Urgency: medium
Maintainer: Teckids Debian Task Force
Changed-By: Thorsten Glaser
Closes: 939193
Changes
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA384
Format: 1.8
Date: Wed, 20 Nov 2019 00:22:43 +0100
Source: php-illuminate-contracts
Architecture: source
Version: 5.8.35-1
Distribution: unstable
Urgency: medium
Maintainer: Teckids Debian Task Force
Changed-By: Thorsten Glaser
Changes:
php
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA384
Format: 1.8
Date: Wed, 20 Nov 2019 02:03:04 +0100
Source: movim
Architecture: source
Version: 0.14.1-6
Distribution: unstable
Urgency: medium
Maintainer: Debian XMPP Maintainers
Changed-By: Thorsten Glaser
Closes: 939190
Changes:
movim (0.14.1-6
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA384
Format: 1.8
Date: Wed, 13 Nov 2019 22:31:24 +0100
Source: campania
Architecture: source
Version: 2.009-2
Distribution: unstable
Urgency: low
Maintainer: Thorsten Glaser
Changed-By: Thorsten Glaser
Changes:
campania (2.009-2) unstable; urgency=low
gregor herrmann dixit:
>On Tue, 12 Nov 2019 15:08:56 -0700, Sean Whitton wrote:
>> optimising for writing these files, I don't think we should be expecting
>> people to come up with a package-specific reason if they find themselves
Thanks.
>> I'd like to suggest this recommendation could be of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA384
Format: 1.8
Date: Tue, 29 Oct 2019 23:28:45 +0100
Source: campania
Binary: fonts-campania
Architecture: source all
Version: 2.009-1
Distribution: unstable
Urgency: low
Maintainer: Thorsten Glaser
Changed-By: Thorsten Glaser
Description:
fonts
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA384
Format: 1.8
Date: Mon, 11 Nov 2019 18:26:12 +0100
Source: musescore-general-soundfont-small
Architecture: source
Version: 0.1.8-1
Distribution: unstable
Urgency: medium
Maintainer: Thorsten Glaser
Changed-By: Thorsten Glaser
Changes:
musescore
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA384
Format: 1.8
Date: Mon, 11 Nov 2019 18:30:51 +0100
Source: musescore-general-soundfont
Architecture: source
Version: 0.1.8-1
Distribution: unstable
Urgency: medium
Maintainer: Thorsten Glaser
Changed-By: Thorsten Glaser
Changes:
musescore-general
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA384
Format: 1.8
Date: Mon, 11 Nov 2019 00:00:19 +0100
Source: musescore
Architecture: source
Version: 3.2.3+dfsg1-4exp1
Distribution: experimental
Urgency: medium
Maintainer: Thorsten Glaser
Changed-By: Thorsten Glaser
Changes:
musescore (3.2.3+dfsg1
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA384
Format: 1.8
Date: Sun, 10 Nov 2019 22:54:07 +0100
Source: musescore
Architecture: source
Version: 3.2.3+dfsg1-4
Distribution: unstable
Urgency: medium
Maintainer: Thorsten Glaser
Changed-By: Thorsten Glaser
Changes:
musescore (3.2.3+dfsg1-4
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA384
Format: 1.8
Date: Sun, 10 Nov 2019 21:44:57 +0100
Source: dietlibc
Architecture: source
Version: 0.34~cvs20160606-12
Distribution: unstable
Urgency: low
Maintainer: Christian Seiler
Changed-By: Thorsten Glaser
Closes: 944489
Changes:
dietlibc
gregor herrmann dixit:
>Lately we as a project, guided by the DPL, have been in
>recommendation mode anyway: "Use dh(1) unless you have a reason not
>to", "Use git(1) and salsa unless …".
>
>I think "Write d/copyright in Copyright-Format 1.0 unless you have a
>specific reason not to do this for a
Andreas Tille dixit:
>explicit wish to not use DEP5. I wonder what other reasons might exist
>to explicitly stick to the non-machine readable format.
I prefer human-readable format. I also often deal in software which
has more… flexibility than the DEP 5 format allows, or where it is
plain
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA384
Format: 1.8
Date: Wed, 30 Oct 2019 15:37:20 +0100
Source: musescore
Architecture: source
Version: 3.2.3+dfsg1-3exp1
Distribution: experimental
Urgency: medium
Maintainer: Thorsten Glaser
Changed-By: Thorsten Glaser
Changes:
musescore (3.2.3+dfsg1
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA384
Format: 1.8
Date: Wed, 30 Oct 2019 15:36:22 +0100
Source: musescore
Architecture: source
Version: 3.2.3+dfsg1-3
Distribution: unstable
Urgency: high
Maintainer: Thorsten Glaser
Changed-By: Thorsten Glaser
Changes:
musescore (3.2.3+dfsg1-3
Sam Hartman dixit:
>depend on non-free software. Github is a common example of a web
>service that uses non-free software.
So is Salsa. It does not use the packaged version of GitLab,
which is in a sorry state anyway, and not suitable for a stable
release, but the proprietary “open core”
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA384
Format: 1.8
Date: Thu, 24 Oct 2019 21:47:00 +0200
Source: dietlibc
Architecture: source
Version: 0.34~cvs20160606-11
Distribution: unstable
Urgency: low
Maintainer: Christian Seiler
Changed-By: Thorsten Glaser
Closes: 925359 943429
Changes
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA384
Format: 1.8
Date: Thu, 24 Oct 2019 02:14:02 +0200
Source: mksh
Architecture: source
Version: 57-4
Distribution: unstable
Urgency: low
Maintainer: Thorsten Glaser
Changed-By: Thorsten Glaser
Changes:
mksh (57-4) unstable; urgency=low
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA384
Format: 1.8
Date: Wed, 23 Oct 2019 21:56:33 +0200
Source: mksh
Architecture: source
Version: 57-3
Distribution: unstable
Urgency: low
Maintainer: Thorsten Glaser
Changed-By: Thorsten Glaser
Changes:
mksh (57-3) unstable; urgency=low
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA384
Format: 1.8
Date: Wed, 16 Oct 2019 00:21:54 +0200
Source: antimicro
Architecture: source
Version: 2.23-2
Distribution: unstable
Urgency: high
Maintainer: Thorsten Glaser
Changed-By: Thorsten Glaser
Changes:
antimicro (2.23-2) unstable; urgency
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA384
Format: 1.8
Date: Wed, 03 Jul 2019 18:55:23 +0200
Source: antimicro
Binary: antimicro antimicro-dbgsym
Architecture: source amd64
Version: 2.23-1
Distribution: unstable
Urgency: medium
Maintainer: Thorsten Glaser
Changed-By: Thorsten Glaser
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA384
Format: 1.8
Date: Wed, 09 Oct 2019 19:22:38 +0200
Source: polkit-qt-1
Architecture: source
Version: 0.112.0-7.1
Distribution: unstable
Urgency: high
Maintainer: Debian Qt/KDE Maintainers
Changed-By: Thorsten Glaser
Closes: 925344
Changes:
polkit
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA384
Format: 1.8
Date: Wed, 02 Oct 2019 02:18:53 +0200
Source: sysvinit
Architecture: source
Version: 2.96~beta-3
Distribution: unstable
Urgency: medium
Maintainer: Debian sysvinit maintainers
Changed-By: Thorsten Glaser
Closes: 941378
Changes
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA384
Format: 1.8
Date: Mon, 30 Sep 2019 01:18:56 +0200
Source: musescore
Architecture: source
Version: 3.2.3+dfsg1-2
Distribution: unstable
Urgency: low
Maintainer: Thorsten Glaser
Changed-By: Thorsten Glaser
Changes:
musescore (3.2.3+dfsg1-2
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA384
Format: 1.8
Date: Mon, 30 Sep 2019 02:32:24 +0200
Source: musescore
Architecture: source
Version: 3.2.3+dfsg1-2exp1
Distribution: experimental
Urgency: low
Maintainer: Thorsten Glaser
Changed-By: Thorsten Glaser
Changes:
musescore (3.2.3+dfsg1
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA384
Format: 1.8
Date: Thu, 26 Sep 2019 00:52:17 +0200
Source: mksh
Architecture: source
Version: 57-2
Distribution: unstable
Urgency: medium
Maintainer: Thorsten Glaser
Changed-By: Thorsten Glaser
Changes:
mksh (57-2) unstable; urgency=medium
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA384
Format: 1.8
Date: Mon, 09 Sep 2019 17:39:10 +0200
Source: hwinfo
Architecture: source
Version: 21.67-1.1
Distribution: unstable
Urgency: low
Maintainer: Sebastien Badia
Changed-By: Thorsten Glaser
Closes: 935109
Changes:
hwinfo (21.67-1.1
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA384
Format: 1.8
Date: Fri, 13 Sep 2019 14:11:11 +0200
Source: pax
Architecture: source
Version: 1:20190825-1
Distribution: unstable
Urgency: low
Maintainer: Thorsten Glaser
Changed-By: Thorsten Glaser
Changes:
pax (1:20190825-1) unstable; urgency=low
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA384
Format: 1.8
Date: Fri, 16 Aug 2019 18:05:08 +0200
Source: rng-tools-debian
Architecture: source
Version: 2.1
Distribution: unstable
Urgency: low
Maintainer: Thorsten Glaser
Changed-By: Thorsten Glaser
Changes:
rng-tools-debian (2.1) unstable
Dominik George dixit:
>>than you think, either bind-mount tons of filesystem from the host,
>>and this is only safe-ish if both run sysvinit
>Why should that not work on systemd?
I wrote safe-ish and deliberately didn’t focus on this
as it’s not relevant for the point I was trying to make.
Hi Simon,
I ran into the same problem… in a chroot. Due to some bug,
systemd-sysv just did not want to install under cowbuilder
for some time.
I discovered that using the second alternative for *conf
worked: put this into /etc/apt/preferences:
Package: dconf-gsettings-backend
Pin: version *
>At a glance, there are also unique LVM IDs in /boot/grub/grub.cfg,
>though whether those would need to be changed when cloning I don't know.
Normally, you mount the root filesystem, chroot into it (more complex
than you think, either bind-mount tons of filesystem from the host,
and this is only
> Change popularity-contest by transmissing the hostid after it has been
> hashed with the content of /etc/machine-id.
Heh, there is no /etc/machine-id on my Debian system.
I have an …/etc/machine-id in buster and stretch chroots I created
and xenial, bionic and disco pbuilder base.cow
>JFTR: aptitude (and all other libapt-based frontends) can make use of
>that feature via the config option APT::Sources::With, the commandline
>flag is just syntactic sugar.
Doesn’t match my use case of repository injection for anything
that might call apt later.
I could, perhaps, add stuff to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA384
Format: 1.8
Date: Fri, 02 Aug 2019 23:07:47 +0200
Source: fluidr3mono-gm-soundfont
Architecture: source
Version: 2.315-6
Distribution: unstable
Urgency: medium
Maintainer: Thorsten Glaser
Changed-By: Thorsten Glaser
Changes:
fluidr3mono-gm
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA384
Format: 1.8
Date: Fri, 02 Aug 2019 22:29:06 +0200
Source: musescore-general-soundfont-small
Architecture: source
Version: 0.1.6-2
Distribution: unstable
Urgency: high
Maintainer: Thorsten Glaser
Changed-By: Thorsten Glaser
Changes:
musescore
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA384
Format: 1.8
Date: Fri, 02 Aug 2019 22:22:19 +0200
Source: musescore-general-soundfont
Architecture: source
Version: 0.1.7-2
Distribution: unstable
Urgency: high
Maintainer: Thorsten Glaser
Changed-By: Thorsten Glaser
Changes:
musescore-general
I wrote:
>in GCC 6 IIRC and *still* pertinent in GCC 8 and I believe 9,
Still present in (sid/amd64):
• gcc-8 (= 8.3.0-19)
• gcc-9 (= 9.1.0-10)
• gcc-snapshot (= 1:20190719-1)
>>I'm currently compiling e2fsprogs with LTO for Debian --- and I'm
>>seriously considering ditching that change. The
>We just had SuSE embracing LTO
Not entirely.
With my DD hat doffed and wearing the mksh upstream developer hat,
I’ve been asking the package maintainers of mksh in all distributions
to remove the LTO flags, and will remove the built-in support for
using LTO in the next release.
Why?
mksh’s
I actually have a use case: injecting packages from
/var/cache/pbuilder/base.cow-somedist/repo/ into APT
from an optional cowbuilder hook script that I can
enable (chmod +x) when needed.
The hook script has the interesting constraint that
it adds a repository to APT with*out* running apt-get
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA384
Format: 1.8
Date: Sun, 28 Jul 2019 20:52:27 +0200
Source: performous
Architecture: source
Version: 1.1+git20190701.9928c27-2
Distribution: experimental
Urgency: low
Maintainer: Debian Games Team
Changed-By: Thorsten Glaser
Changes:
performous
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA384
Format: 1.8
Date: Fri, 19 Jul 2019 15:47:46 +0200
Source: performous
Architecture: source
Version: 1.1+git20190701.9928c27-1
Distribution: experimental
Urgency: low
Maintainer: Debian Games Team
Changed-By: Thorsten Glaser
Changes:
performous
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA384
Format: 1.8
Date: Wed, 10 Jul 2019 18:57:24 +0200
Source: musescore
Binary: musescore3 musescore3-common musescore3-dbgsym
Architecture: source all i386
Version: 3.2.3+dfsg1-1exp1
Distribution: experimental
Urgency: low
Maintainer: Thorsten Glaser
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA384
Format: 1.8
Date: Wed, 10 Jul 2019 03:22:28 +0200
Source: musescore
Architecture: source
Version: 3.2.3+dfsg1-1
Distribution: unstable
Urgency: low
Maintainer: Thorsten Glaser
Changed-By: Thorsten Glaser
Changes:
musescore (3.2.3+dfsg1-1
Urgency: medium
Maintainer: Thorsten Glaser
Changed-By: Thorsten Glaser
Description:
musescore-snapshot - cross-platform multi-lingual music composition and
notation (deve
musescore-snapshot-common - MuseScore devel (music composition and notation)
shared files
Changes:
musescore-snapshot (3.2
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA384
Format: 1.8
Date: Thu, 04 Jul 2019 23:55:01 +0200
Source: musescore
Binary: musescore3 musescore3-common musescore3-dbgsym
Architecture: source all amd64
Version: 3.2.2+dfsg1-1
Distribution: experimental
Urgency: medium
Maintainer: Thorsten Glaser
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA384
Format: 1.8
Date: Mon, 24 Jun 2019 18:07:46 +0200
Source: musescore
Architecture: source
Version: 2.3.2+dfsg2-7
Distribution: unstable
Urgency: high
Maintainer: Debian Multimedia Maintainers
Changed-By: Thorsten Glaser
Closes: 931021
Changes
1 - 100 of 1102 matches
Mail list logo
