Package: adequate
Version: 0.15.4
Severity: normal
X-Debbugs-Cc: t...@mirbsd.de
performous-composer: incompatible-licenses /usr/games/performous-composer
GPLv2+ + OpenSSL (libssl.so.1.1)
This is now permitted in Debian, as OpenSSL is now a System Library
(like in the BSDs).
-- System Informatio
Package: adequate
Version: 0.15.3
Severity: normal
X-Debbugs-Cc: t...@mirbsd.de
Adequate reports obsolete-conffile if a package no longer ships a
conffile, but there are two cases to distinguish:
• the package’s buggy and didn’t clean up
• dpkg didn’t remove the conffile because it was locally ch
Jakub Wilk dixit:
> * Thorsten Glaser , 2019-10-08, 13:57:
>> setting effective gid to 32767: Invalid argument at /usr/bin/adequate line
>> 1070.
>
> That's probably #941985.
Indeed. Good catch!
Thanks,
//mirabilos
--
(gnutls can also be used, but if you are compi
Package: adequate
Version: 0.15.2
Severity: normal
I get tons of messages like…
adequate: ldd -r /usr/bin/virt-xml: setting effective gid to 32767: Invalid
argument at /usr/bin/adequate line 1070.
… when I upgrade now.
-- System Information:
Debian Release: bullseye/sid
APT prefers unreleas
Package: schroot
Version: 1.6.10-5
Severity: normal
tglase@tglase:~ $ schroot -prc vncsess dpkg -l mksh
E: Only one action may be specified
I: Run “schroot --help” to list usage example and all available options
Apparently, there’s a workaround…
tglase@tglase:~ $ schroot -prc vncsess -- dpkg -l
tags 58743 = confirmed upstream wontfix
thanks
I’ve looked at this in great detail now again.
The structure of file,v at the time of merge is as follows:
RCS file: /home/tg/cvsrepo/cvsbug/Attic/file,v
Working file: file
head: 1.2
branch:
locks: strict
access list:
symbolic names:
branch
tags 774716 + pending upstream
thanks
bugzilla-dae...@gentoo.org dixit:
>https://bugs.gentoo.org/show_bug.cgi?id=537522
>could you resync the pax code w/the latest openbsd ?
For the record over here: resync in progress, but we’ll see
a security fix backport-only release first (which the regula
reassign 807185 usrmerge
thanks
Julian Andres Klode dixit:
>Installing mksh on a system with usrmerge installed, that is,
>/ merged into /usr fails:
Huh. Why would anyone do that.
>update-alternatives: using /bin/mksh to provide /bin/ksh (ksh) in auto mode
>update-alternatives: error: unable to
Nicholas Bamber dixit:
> Also I would have thought the fc functionality is an intrinsically interactive
> piece of functionality. What sort of script would depend on the fc default
> being 'ed'? And if a script did somehow interact with fc surely it would
ed is an interactive editor ;) but, to an
Hi,
this is now implemented in CVS HEAD. Please test.
bye,
//mirabilos
--
“The final straw, to be honest, was probably my amazement at the volume of
petty, peevish whingeing certain of your peers are prone to dish out on
d-devel, telling each other how to talk more like a pretty princess, as tho
Kenneth Pronovici dixit:
>I filed the bug so nothing would get lost while the package is
>orphaned, which seems like a reasonable thing to do. The next
That may seem reasonable…
>maintainer might very well have a different policy for Debian bugs
>than you did. I would if it were my package.
…
Kenneth Pronovici dixit:
>I'm not trying to be snarky here, but I'm a little lost. This package
>is orphaned. If you're no longer the package maintainer, why should
>it even matter to you whether upstream issues are tracked as Debian
>bugs?
Because
① I’m upstream,
② I’m maintaining this packa
Kenneth Pronovici dixit:
>I'll file a Debian bug to document the improvements I asked for, just
Please DO NOT file Debian bugs for upstream issues in mksh,
only for packaging issues.
This has been at the top of README.Debian for ages.
Debian bugs requesting functionality changes are likely to
g
Vincent Lefevre dixit:
>I think that it should enable this option in posix and sh modes.
No, because POSIX specifies some amount of locales tracking,
using the host’s wide char functions, locales, etc. which
is diametrally against what mksh promises (to behave consistently
across platforms).
The
Alexander Cherepanov dixit:
> 1. paxtar will extract files with .. components in names.
> 2. While extracting an archive, it will extract symlinks and then follow them
> if they are referenced in further entries.
Please check if any of these are required by POSIX and, if not,
report this bug to
Source: blackbox
Version: 0.70.1-14
[…]
dh_makeshlibs -a
dpkg-gensymbols: warning: some symbols or patterns disappeared in the symbols
file: see diff output below
dpkg-gensymbols: warning: debian/libbt0/DEBIAN/symbols doesn't match completely
debian/libbt0.symbols
--- debian/libbt0.symbols (l
Package: pdksh
Severity: serious
Tags: pending
As discussed in IRC today, pdksh symlinked to lksh should not
transition to testing without a NEWS file detailing the transition
and that users shall switch to mksh as login shell since lksh
is not intended for interactive use.
Will tackle this ASAP
Jonathan Nieder dixit:
>Maybe rgselk is on i386. I'm guessing it also works there, though.
Hrm, then he wouldn’t have written about 64 bit? Anyway:
r($n=0;$n<2097160;$n++){
<
> print FH $x;} close(FH);'
ll x
tglas
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA384
Hi,
I’m the new maintainer of CVS in Debian. The package has been
totally replaced by a new one, which differs quite a lot from
the old package. For example, no repositories are managed au-
tomatically any more, PAM is gone, Kerberos is there (but n
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA384
Hi,
I’m the new maintainer of CVS in Debian. The package has been
totally replaced by a new one, which differs quite a lot from
the old package. For example, no repositories are managed au-
tomatically any more, PAM is gone, Kerberos is there (but n
Dixi quod…
>>As for db4.7, there’s the other build error, but as it’s been
>>orphaned I’m going to search for it, hopefully fix it and do a
>>QA upload.
>
>Mh apparently other arches suffer from the same (avr32 gcj
>uninstallable, mips and sparc64 fail the same way as m68k).
I think it’s #594816,
Definitively. Note that -10 did the same, and I didn’t think
to check if other architectures were affected by this bug.
I’m looking into it.
bye,
//mirabilos
--
“Having a smoking section in a restaurant is like having
a peeing section in a swimming pool.”
https://buildd.debian.org/fetch.cgi?&pkg=db4.7&ver=4.7.25-10&arch=sparc&stamp=1289791596&file=log
https://buildd.debian.org/fetch.cgi?&pkg=db4.7&ver=4.7.25-11&arch=sparc&stamp=1294793616&file=log
But look at the debdiff between -10 and -11 as there’s nothing
which can explain this in there… althou
23 matches
Mail list logo
