Package: mirrors
Severity: wishlist
User: mirr...@packages.debian.org
Usertags: mirror-submission
Submission-Type: new
Site: debian.mirror.net.in
Type: leaf
Archive-architecture: ALL amd64 arm64 armel armhf hurd-i386 i386 kfreebsd-amd64
kfreebsd-i386 mips mips64el mipsel powerpc ppc64el s390x
On Fri, Jan 28, 2022 at 09:42:43PM -0700, Neil Mayhew wrote:
> On 2022-01-28 08:29, Neil Mayhew wrote:
> > It looks like geocoding_data.cc is truncated and my working hypothesis
> > is that it's still in the process of being generated, which in turn is
> > due to race condition in the parallel
On 2022-01-28 08:29, Neil Mayhew wrote:
It looks like geocoding_data.cc is truncated and my working hypothesis
is that it's still in the process of being generated, which in turn is
due to race condition in the parallel build. This could explain why it
built successfully on some architectures
Hello, epubcheck maintainers.
This problem was described in epubcheck troubleshooting document.
https://github.com/w3c/epubcheck/wiki/Running#javalangstackoverflowerror
Just add 1024kb or more stack to fix this error.
> java -Xss1024k -jar epubcheck.jar moby-dick.epub
--
YOKOTA
On 29 January 2022 at 10:38, Paul Wise wrote:
| Control: fixed -1 4.0.3
|
| On Fri, 2022-01-28 at 20:07 -0600, Dirk Eddelbuettel wrote:
|
| > Per email by Graham from 14 Nov 2020 this has been resolved.
|
| Resolved upstream in 2020 but not in Debian until 2021.
Correct. Graham (as author)
Further for the records (for a future upgrade to newer ZK versions):
There will likely need to be a NEWS.Debian entry about the following:
https://issues.apache.org/jira/browse/ZOOKEEPER-3056
In short:
- apparently they've added a check that prevents ZK from starting, when
no snapshots were
On Fri, 2022-01-28 at 01:33 +0100, Pierre-Elliott Bécue wrote:
> I've made some changes I've decided to upload on salsa and on
> experimental.
>
> If you're able to test these changes on some clean environment, I'd
> be
> happy if you could do it as I like the time to redo a clean testing
>
Control: fixed -1 4.0.3
On Fri, 2022-01-28 at 20:07 -0600, Dirk Eddelbuettel wrote:
> Per email by Graham from 14 Nov 2020 this has been resolved.
Resolved upstream in 2020 but not in Debian until 2021.
> By now we have an even newer version 4.0.3.
Please use a versioned -done message next
On Sat, 29 Jan 2022 at 01:44, Adrian Bunk wrote:
>
> On Sat, Jan 29, 2022 at 01:32:44AM +, Luca Boccassi wrote:
> > Package: wnpp
> > Severity: wishlist
> > Owner: Luca Boccassi
> > X-Debbugs-Cc: debian-de...@lists.debian.org
> >
> > * Package name: tpm2-openssl
> > Version :
On Sat, Jan 29, 2022 at 01:32:44AM +, Luca Boccassi wrote:
> Package: wnpp
> Severity: wishlist
> Owner: Luca Boccassi
> X-Debbugs-Cc: debian-de...@lists.debian.org
>
> * Package name: tpm2-openssl
> Version : 1.0.1
> Upstream Author : Fraunhofer SIT, Intel, Wind River and
Package: wnpp
Severity: wishlist
Owner: Luca Boccassi
X-Debbugs-Cc: debian-de...@lists.debian.org
* Package name: tpm2-openssl
Version : 1.0.1
Upstream Author : Fraunhofer SIT, Intel, Wind River and others
* URL : https://github.com/tpm2-software/tpm2-tss-engine
*
Control: tags 965431 + patch
Control: tags 965431 + pending
Dear maintainer,
I've prepared an NMU for bfbtester (versioned as 2.0.1-7.2) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer or cancel it.
Regards,
Eriberto
diff -u bfbtester-2.0.1/debian/rules
Control: tags 1002213 + patch
Control: tags 1002213 + pending
Dear maintainer,
I've prepared an NMU for dmitry (versioned as 1.3a-1.2) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer or cancel the upload.
Regards,
Eriberto
diff -u
Hi Shengjing,
2022年1月28日(金) 23:38 Shengjing Zhu :
>
> On Fri, Jan 28, 2022 at 6:33 PM Nobuhiro Iwamatsu wrote:
> >
> > Hi Shengjing,
> >
> > 2022年1月28日(金) 18:39 Shengjing Zhu :
> > >
> > > It has been packaged,
> > > https://tracker.debian.org/pkg/golang-github-benbjohnson-clock
> >
> > Oh,
Source: libkcapi
Version: 1.3.1-2
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/fetch.php?pkg=libkcapi=all=1.3.1-2=1643387702=0
...
dh_missing -i
dh_missing: warning: usr/lib/x86_64-linux-gnu/libkcapi.la exists in debian/tmp
but is not installed to anywhere
dh_missing:
As of kernel 5.15.5 (bpo) I see that max_t() is still used. If this is
blocking any merge into the stable kernel patch, I can test it with
just PAGE_SIZE to confirm whether it is okay.
As it stands, I currently need to manually build the stable kernel in
order to have a functioning Blackbird
On Fri, Jan 28, 2022 at 08:32:25PM +, Peter wrote:
> -k--build-id
> is an answer to getting dbgsym packages,
> however I tried it out with c-evo and it is breaking reproducible build.
> Looks like the build ID is a random string, so the two builds differ.
Does it build reproducibily *without*
Here is the merge request:
https://salsa.debian.org/debian/spamassassin/-/merge_requests/7
I have tested on my Ubuntu 20.04 server running a manually patched
spamassassin 3.4.4-1ubuntu1.1
Thank you!
Simon
Hi Marco,
On Fri, Jan 21, 2022 at 10:53:12PM +0100, Marco d'Itri wrote:
> On Jan 20, Helmut Grohne wrote:
>
> > CONFFLAGS = --disable-werror --prefix=/usr \
> > - --disable-xcrypt-compat-files --enable-obsolete-api=glibc
> > + --disable-xcrypt-compat-files --enable-obsolete-api=glibc \
> > +
Package: spamassassin
Version: 3.4.4-1ubuntu1.1
The cron.daily refresh script works well for HTTP mirrors accessed
through a `http_proxy` (thanks to [*]) but fails when accessing HTTPS
mirrors. For those, the HTTPS equivalent variable would need to be
supported.
Thanks,
Simon
*:
Hi,
Do you plan to update the guvcview package please?
Regards,
Hi,
Is the Debian Multimedia Team planning to update this package please?
Regards,
-k--build-id
is an answer to getting dbgsym packages,
however I tried it out with c-evo and it is breaking reproducible build.
Looks like the build ID is a random string, so the two builds differ.
Maybe not a good idea for etc/fpc.cfg ?
Cheers,
Peter
I can confirm this.
Unstable (version 2.3.1-1):
zito@bobek:~$ ip a s dev wlp3s0
3: wlp3s0: mtu 1500 qdisc mq state UP group
default qlen 1000
link/ether 00:24:d7:f3:8d:e8 brd ff:ff:ff:ff:ff:ff
inet 192.168.1.120/24 brd 192.168.1.255 scope global dynamic noprefixroute
wlp3s0
On Fri, Jan 28, 2022 at 05:38:02PM +0100, Julien Cristau wrote:
> +xserver-xorg-video-intel (2:2.99.917+git20200714-1+deb11u1) bullseye;
> urgency=medium
I should have said, this is currently in pu-new.
Cheers,
Julien
Package: wnpp
X-Debbugs-Cc: debian-de...@lists.debian.org
Owner: Judit Foglszinger
X-Debbugs-Cc: ur...@debian.org
Severity: wishlist
* Package name: fonts-fantasma
Version : 1.0
Upstream Author : Froyo Tam
* URL : https://github.com/froyotam/Fantasma
* License
Source: ngraph-gtk
Version: 6.09.05-1
Tags: patch
User: debian-cr...@lists.debian.org
Usertags: ftcbfs
ngraph-gtk fails to cross build from source for multiple reasons. The
immediate failure is due to using AC_CHECK_FILE. That macro is meant to
check for files on the host system, but it is being
Package: spamass-milter
Version: 0.4.0-2
Severity: normal
X-Debbugs-Cc: none, Dave Love
I see this in syslog when mail is processed with postfix configured
according to README.Debian:
spamass-milter[673]: Could not retrieve sendmail macro "b"!. Please add it
to confMILTER_MACROS_ENVRCPT for
On Thu, Feb 18, 2016 at 08:18:33PM +0100, Stéphane Aulery wrote:
> Le 17/02/2016 22:13, walter harms a écrit :
> > >
> > > Jakub Wilk reported a possible integer overflow in make_message example :
> > >
> > > > The example in the printf(3) manpages looks like this (with boring parts
> > > >
On Wed, Jan 20, 2021 at 10:16:03AM +0100, Michael Kerrisk (man-pages) wrote:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866060
> seems to be related, and maybe the changes in the patch for that bug
> are sufficient to address the concerns in this bug? (That patch as
> just been taken
On Tue, Feb 16, 2016 at 10:35:15PM +0100, Stéphane Aulery wrote:
> [...]
> About this bug I had send this first patch to M. Kerrisk. He rejected it.
> Too long for a good review. See this thread on linux-...@vger.kernel.org
> [1].
>
> I started to break my patch and some passages were corrected
Argh! Nevermind, just figured it out.
It's actually documented in the original NEWS file, but it's
not very obvious to the user, why suddenly the modem disappears.
This is the solution:
ln -sft /etc/ModemManager/fcc-unlock.d
/usr/share/ModemManager/fcc-unlock.available.d/*
and it's also
Hi Roland,
Quoting Roland Clobus (2022-01-28 18:22:17)
> Sorry about the noise,
as far as I'm concerned, you made no noise but you made a very valuable
contribution instead. Thank you! :)
> Thanks for releasing a new version of fontconfig with the patch for the
> reproducible cache files
>
control: tags -1 patch
for py in $(py3versions -s); do
echo "= Running tests with $py =="
if ! $py3 -m unittest dulwich.tests.test_suite; then
rv=1
this should really be
for py3 in $(py3versions -s); do
echo "= Running tests with $py =="
if ! $py3
Hi Colin,
On Fri, 3 Dec 2021 11:17:26 + Colin Watson wrote:
GRUB 2.06 is a pretty big change over 2.04. I'd like to hold this in
unstable for a while longer to let things shake out before we allow it
to move to testing.
grub2 showed up in my out-of-sync tracking script output. Do you
Hi,
On 28-01-2022 08:44, Ondřej Surý wrote:
php-common 2:92 erroneously promoted to testing
No, not really. php-raphf just needs to migrate to testing as it is currently
not present in testing.
php-raphf was removed in December. So php-common was not blocked by it
to move to testing.
> > Should we release this as 0.1.13-2 ?
>
> Well, of course I'm biased towards reproducible builds... so my answer
> is yes! :)
True, let's do it. I'll have the upload close this bug so that this
gets visibly solved. :]
-mk
found 1004465 2.0.10-1
thanks
Dixi quod…
>Quite some files are missing:
[…]
>/usr/lib/klibc/include/alloca.h
[…]
>/usr/lib/klibc/include/arpa/inet.h
> /usr/lib/klibc/include/asm
> /usr/lib/klibc/include/asm-generic
>/usr/lib/klibc/include/assert.h
[…]
From this
Control: tags -1 + moreinfo
Hi,
I'm unable to reproduce using a porterbox
Sorry about the noise,
The long mail was sent only to control@... and therefore invisible.
With kind regards,
Roland Clobus
Forwarded Message
Subject: Improved patch
Date: Fri, 28 Jan 2022 18:08:28 +0100
From: Roland Clobus
To: cont...@bugs.debian.org
reopen 864082 =
Am 28.01.22 um 11:44 schrieb Simon McVittie:> On Fri, 28 Jan 2022 at
08:27:19 +0100, Philipp Huebner wrote:
>> On Debian Bullseye, flatpak crashes when trying to create a
>> bundle.
>
> Is this specific to being in an ecryptfs directory, or some other
> special filesystem configuration?
Not
Package: evolution-data-server
Version: 3.42.3-1
Severity: normal
Dear Maintainer,
I think that the trouble is described here:
https://lists.debian.org/debian-user/2022/01/msg01134.html
and a possible cause here:
https://lists.debian.org/debian-user/2022/01/msg01163.html
(Thanks to Didier!)
But
Hi,
>> Just to point out that you specified the 'Version' here as 2:3.2.7,
>> whilst the traceback you linked to:
>>
>> > https://buildd.debian.org/status/fetch.php?pkg=python-django=all=2%3A3.2.11-1=1641309500=0
>>
>> ... refers to a different version: 2:3.2.11.
[..]
> That was intentional:
>
Control: severity -1 important
Control: tag -1 upstream fixed-upstream patch
On Wednesday, 26 January 2022 21:12:35 CET Maximilian Engelhardt wrote:
> Control: found -1 2.37.90.20220123-2
> Control: affects -1 src:xen
User 'ChmEarl' on IRC noted the following commit
Le 28/01/2022 à 13:10, Adrian Bunk a écrit :
> Package: virt-top
> Version: 1.0.9-1.1
> Severity: serious
> X-Debbugs-Cc: Debian OCaml Maintainers
>
> $ virt-top
> the file '/usr/bin/virt-top' has not the right magic number: expected
> Caml1999X030, got Caml1999X028
/usr/bin/virt-top is a
On Fri, Jan 28, 2022 at 08:42:44AM -0800, Chris Lamb wrote:
> found 1004464 2:3.2.11-1
> thanks
>
> Hi Adrian,
>
> > Version: 2:3.2.7-1
>
> Just to point out that you specified the 'Version' here as 2:3.2.7,
> whilst the traceback you linked to:
>
> >
found 1004464 2:3.2.11-1
thanks
Hi Adrian,
> Version: 2:3.2.7-1
Just to point out that you specified the 'Version' here as 2:3.2.7,
whilst the traceback you linked to:
> https://buildd.debian.org/status/fetch.php?pkg=python-django=all=2%3A3.2.11-1=1641309500=0
... refers to a different
Hello Camm!
On 1/28/22 15:48, Camm Maguire wrote:
> Greetings, and once again, thanks for all you do for Debian! No rush on
> this item at all, needless to say.
>
> Problem persists. What package versions should I watch for to see that
> the fix has been installed?
If the current package
Package: release.debian.org
Severity: normal
Tags: bullseye
User: release.debian@packages.debian.org
Usertags: pu
X-Debbugs-Cc: jcris...@debian.org
[ Reason ]
Due to an issue with the way it sets compiler flags for sse2 routines,
the intel Xorg driver was compiled with sse2 enabled for more
On 2022-01-28 09:23, tony mancill wrote:
I'm considering setting parallel=1 for the next upload. Thoughts?
I think that's a good idea. I seems likely there's a bug in the
CMakeLists.txt that fails to express a dependency on the code generation
step, and this is a good workaround for now. If
On 2022-01-26, Miroslav Kratochvil wrote:
> Many thanks for reporting, I pushed this to github repo. I will update
> debhelper number when it's out of experimental.
>
> Should we release this as 0.1.13-2 ?
Well, of course I'm biased towards reproducible builds... so my answer
is yes! :)
But it
Am Donnerstag, dem 27.01.2022 um 18:55 -0500 schrieb Andres Salomon:
> you can also run "chromium --ozone-platform=wayland" to get native
> wayland.
Thanks for the tip, I never tried that. I do the chrome://flags way
because it's persistent and doesn't require running chromium from the
On Fri, Jan 28, 2022 at 08:29:36AM -0700, Neil Mayhew wrote:
> On 2022-01-28 07:59, tony mancill wrote:
> > it is surprising to see it fail with this:
> > > /<>/cpp/src/phonenumbers/geocoding/geocoding_data.cc:787278:13:
> > > error: ‘i18n::phonenumbers::{anonymous}::prefix_86_zh_descriptions’
>
Package: liblog4j1.2-java
Version: 1.2.17-10
Severity: grave
Tags: security upstream
Justification: user security hole
X-Debbugs-Cc: Debian Security Team
Hey.
A number of holes was found in the 1.2 branch of log4j.
The following is apparently critical (code injection):
On 2022-01-28 07:59, tony mancill wrote:
it is surprising to see it fail with this:
/<>/cpp/src/phonenumbers/geocoding/geocoding_data.cc:787278:13:
error: ‘i18n::phonenumbers::{anonymous}::prefix_86_zh_descriptions’ defined but not used
[-Werror=unused-variable]
787278 | const char*
Package: wnpp
X-Debbugs-Cc: debian-r...@lists.debian.org
Severity: wishlist
* Package name: mdbook
Version : 0.4.15
Upstream Author : https://rust-lang.github.io/mdBook/misc/contributors.html
* URL : https://github.com/rust-lang/mdBook
* License : Mozilla
I have the same problem here with Debian 11 (bullseye).
The only solution seems to be
apt-get purge uvcdynctrl
After that my webcam still works.
So this package can be seen as unusable, harmful and dispensable.
This should not be installed and all dependencies snatched.
Best regards
karsten
On Thu, Jan 27, 2022 at 10:55:15PM -0700, Neil Mayhew wrote:
> I saw the build errors. I think I've seen them before in local dev, and I
> think they're to do with parallel builds. The file with the compilation
> error is a generated file, and I think make is trying to compile it before
> it's
Greetings, and once again, thanks for all you do for Debian! No rush on
this item at all, needless to say.
Problem persists. What package versions should I watch for to see that
the fix has been installed?
Take care,
John Paul Adrian Glaubitz writes:
> On 12/30/21 22:05, John Paul Adrian
On Thu, 27 Jan 2022 18:36:10 -0300 Joao Paulo wrote:
Changes since the last upload:
pinpoint (1:0.1.8-6) unstable; urgency=medium
.
* New maintainer. (Closes:#1000155)
* debian/control:
- Bumped Standards-Version to 4.6.0.
- Updated debhelp-compat for version 13.
*
On Fri, Jan 28, 2022 at 6:33 PM Nobuhiro Iwamatsu wrote:
>
> Hi Shengjing,
>
> 2022年1月28日(金) 18:39 Shengjing Zhu :
> >
> > It has been packaged,
> > https://tracker.debian.org/pkg/golang-github-benbjohnson-clock
>
> Oh, thank you for pointing that out.
> I will close this bug.
>
> BTW, Are you
Hello Pierre-Elliott,
El 28/01/22 a las 00:28, Pierre-Elliott Bécue escribió:
> Hi Santiago,
>
> I'd like to resume on that bug: did you either find a solution for it or
> an explanation for this behaviour?
>
> Could you try to have a go with lxc4?
...
I didn't find any solution. And I got
I should mention that this was fixed in testing a long time ago. I am not
closing the bug myself in case it motivates a backport for stable, but I
am not affected anymore and fine with the bug being closed.
--
Marc Glisse
On 27/01/2022 16:41, Dylan Aïssi wrote:
Pipewire 0.3.43 is now in testing, this version includes f8cdc05720bf1.
Could you check if it works without having to modify the config file?
I had the same problem - not working USB Jabra conference speakers.
(My workaround was to stay with pipewire
On 28/01/22 12:23 PM, Bernhard Schmidt wrote:
> After that I have pushed Yangfl's patch to our git repo and Salsa CI
> looks happy, at least crossbuilding on arm64 appears to work. Since the
> patch introduces the use of pkg-config I'm not sure what upstream's take
> would be, so I have created a
Package: wnpp
Severity: wishlist
Subject: ITP: python-ci-info -- Python3 implementation of watson/ci-info
Package: wnpp
Owner: Andreas Tille
Severity: wishlist
* Package name: python-ci-info
Version : 0.2.0
Upstream Author : Mathias Goncalves
* URL :
Package: node-js-yaml
Version: 4.1.0+dfsg+~4.0.5-5
Severity: normal
Hi,
import * as Yaml from 'js-yaml';
fails because
"exports": {
".": {
"import": "./dist/js-yaml.mjs",
"require": "./index.js"
},
"./package.json": "./package.json"
},
and dist/js-yaml.mjs
is
Am Fri, Jan 28, 2022 at 12:56:56PM +0100 schrieb Bill Allombert:
> > What I'm actually imagine is that the time I need to write this kind of
> > mails I could perfectly use to convert 2-3 d/copyright files from old
> > format to DEP5. And now I'm wondering why I'm not doing so ...
>
> Do not
Hi Sam,
upstream apparently cannot reproduce the issue anymore[0]. Do you still
this see on your end?
Cheers,
--
Seb
[0] https://github.com/aptly-dev/aptly/issues/403#issuecomment-1024176943
Control: severity -1 serious
Still fails in 8.10-6:
https://buildd.debian.org/status/fetch.php?pkg=openconnect=amd64=8.10-6=1643371452=0
cu
Adrian
Source: emscripten
Version: 3.1.1~dfsg+~1.39.6-5
Severity: serious
Hello, some tests are trying to reach googleapis
test_global_inits (test_other.other) ... skipped 'relies on fastcomp
EXIT_RUNTIME=0 optimization not implemented/disabled'
ports:INFO: retrieving port: giflib from
Package: virt-top
Version: 1.0.9-1.1
Severity: serious
X-Debbugs-Cc: Debian OCaml Maintainers
$ virt-top
the file '/usr/bin/virt-top' has not the right magic number: expected
Caml1999X030, got Caml1999X028
$
Package: coreutils
Version: 8.32-4+b1
Severity: wishlist
X-Debbugs-Cc: sm...@smurf.noris.de
Moving files between btrfs subvolumes doesn't work because they're
different volumes.
However, it's possible to reflink the files to their new location, then
remove the original.
Rather than forcing the
On Fri, Jan 28, 2022 at 12:41:39PM +0100, Andreas Tille wrote:
)
> > > I personally would rather think that excluding files from the upstream
> > > source is a pretty good reason to make DEP5 mandatory *for these cases*.
> > > Besides a sensible way of documentation it saves maintainer time to
> >
Package: mdadm
Version: 4.2-1
Severity: minor
Dear Debian folks,
Doing `sudo apt update && sudo apt full-upgrade` on an outdated Debian
sid/unstable system, I wondered about the message below:
Unpacking mdadm (4.2-1) over (4.1-11) ...
dpkg: warning: unable to delete old directory
Hi Bill,
Am Fri, Jan 28, 2022 at 10:00:36AM +0100 schrieb Bill Allombert:
> On Fri, Jan 28, 2022 at 09:08:17AM +0100, Andreas Tille wrote:
> > > It should be possible to use it with the plain old copyright format too,
> > > otherwise we are kind of renegating on our promise that the machine
> > >
Hi,
> What's the status of this bug?
>
> There is a proposed patch attached to it, could you please apply it and
> upload?
Thanks for reminding me.
3.1.15-1 has been uploaded, which fixes build on other 32 bit platforms
upstream. It is still broken on 64 bit platforms.
After that I have
Dear Maintainer,
the previously reported p
roblem is quite probable due to fact that the setup instruction on groupmems
hadn't be performs.
This was done meanwhile.
But groupmem still does not work, see console logs
# system configuration
root@lune:/etc# grep tester2 group
[?2004l
Package: obs-studio
Version: 27.1.3+dfsg1-2
Followup-For: Bug #934510
X-Debbugs-Cc: lca...@bitergia.com
Dear Maintainer,
I'm not being able to use the X composite after upgrading to this version. This
is the error see in the console
error: Source ID 'xcomposite_input' not found
error: Failed to
Package: installation-reports
Severity: normal
Tags: d-i
X-Debbugs-Cc: atzli...@sina.com
Boot method: USB
Image version:
https://mirrors.bfsu.edu.cn/debian-cd/11.2.0/arm64/iso-dvd/debian-11.2.0-arm64-DVD-1.iso
Date: 2020-01-22
Machine: Phytium CPU FT-2000/4
Partitions:
udev devtmpfs
On Fri, 28 Jan 2022 at 08:27:19 +0100, Philipp Huebner wrote:
> On Debian Bullseye, flatpak crashes when trying to create a bundle.
Is this specific to being in an ecryptfs directory, or some other special
filesystem configuration?
> That issue has also already been reported here:
>
Package: mutrace
Version: 0.2.0-3.4+b2
Severity: normal
X-Debbugs-Cc: dankamong...@gmail.com
Dear Maintainer,
Trying to use mutrace with the -d option fails:
[schwarzgerat](1) $ mutrace -d ls
ls: symbol lookup error: /usr/lib/mutrace/libmutrace-backtrace-symbols.so:
undefined symbol:
Hi
On 2022-01-28 10:13:31, Christian Marillat wrote:
> Hi,
>
> libtorrent-rasterbar 2.0.5 is now in experimental.
>
> The moreinfo tag has been removed.
>
> libtorrent-rasterbar build for all release arches except mips64el and
> mipsel (Needs-Build).
>
> Should we wait for these arches to
Hi Shengjing,
2022年1月28日(金) 18:39 Shengjing Zhu :
>
> It has been packaged,
> https://tracker.debian.org/pkg/golang-github-benbjohnson-clock
Oh, thank you for pointing that out.
I will close this bug.
BTW, Are you planning to update this package?
Best regards,
Nobuhiro
--
Nobuhiro
Package: passwd
Version: 1:4.8.1-1
Severity: normal
Dear Maintainer,
* What led up to the situation?
Checks made for translation of man 8 groupmems
* What exactly did you do (or not do) that was effective (or
ineffective)?
Try to invoke groupmems as user and as
It has been packaged,
https://tracker.debian.org/pkg/golang-github-benbjohnson-clock
Hi,
libtorrent-rasterbar 2.0.5 is now in experimental.
The moreinfo tag has been removed.
libtorrent-rasterbar build for all release arches except mips64el and
mipsel (Needs-Build).
Should we wait for these arches to start the transition ?
Christian
Source: node-terser
Version: 4.8.0-1
Severity: wishlist
User: pkg-javascript-de...@alioth-lists.debian.net
Usertags: webpack5
Update node-terser to v5 which is required by terser-webpack-plugin
embededded in the webpack package.
The current version of node-terser breaks terser-webpack-plugin
Package: wnpp
Severity: wishlist
Owner: Nobuhiro Iwamatsu
* Package name: golang-github-benbjohnson-clock
Version : 1.3.0
Upstream Author : Ben Johnson
* URL : https://github.com/benbjohnson/clock
* License : Expat
Programming Lang: Go
Description: golang
On Fri, Jan 28, 2022 at 09:08:17AM +0100, Andreas Tille wrote:
> Hi,
>
> > It should be possible to use it with the plain old copyright format too,
> > otherwise we are kind of renegating on our promise that the machine
> > readable copyright format be optionnal.
>
> Did we ever promised this?
I believe:
cmake (3.16.3-1~bpo9+1) stretch-backports; urgency=medium
should have been:
cmake (3.16.3-1~bpo9+1) stretch-backports-sloppy; urgency=medium
since buster has cmake (3.13.4-1)
https://packages.debian.org/source/oldstable/cmake
Package: yamllint
Version: 1.26.3-1
Severity: normal
Hello,
$ cat l.yaml
---
mylist:
- |
blablub
};
$ yamllint l.yaml
Traceback (most recent call last):
File "/usr/bin/yamllint", line 33, in
For reference:
* https://buildd.debian.org/status/package.php?p=cmake=stretch-backports
Package: cmake
Version: 3.16.3-1~bpo9+1
Package cannot be installed on stretch + bpo:
```
% sudo apt-get install -t stretch-backports cmake libarchive13
Reading package lists... Done
Building dependency tree
Reading state information... Done
libarchive13 is already the newest version
Hi all,
The following Patch on top of a 4.19.208 is working in our test system
since Jan 5.
cheerio
Steve
Am 27.01.22 um 22:59 schrieb Florian Westphal:
> Salvatore Bonaccorso wrote:
>> Hi,
>>
>> On Thu, Jan 27, 2022 at 06:26:10PM +0100, Steffen Weinreich wrote:
>>> Hi all,
>>>
>>> The patch
Hello Chris,
Downstream didn't really do anything so far on this topic.
I also can only reproduce this issue on Kernel 5.15 and higher.
I don't know whether setting / as ReadOnly directly or using
ProtectSystem=strict along with PrivateDevices=true,
ProtectKernelTunables=true and
Hi,
Am Thu, Jan 27, 2022 at 11:25:31PM +0100 schrieb Bill Allombert:
> > > +
> > > +These types of files, or any others that Debian does not want to
> > > +include in our archive, must be stripped from the upstream
> > > tarball
> > > +prior to uploading. The
97 matches
Mail list logo
