Please reopen.
Advice is no replacement for a Depends in the package control file.
As shipped the package is still broken and at the reported severity -
breaking most of the system
A.
On 18/04/2019 14:48, Debian Bug Tracking System wrote:
This is an automatic notification regarding your
That is not an advice.
If nscd is a required dependency, NIS should bring it in.
Presently it is not.
Still broken
A.
On 18/04/2019 14:43, Elimar Riesebieter wrote:
* Elimar Riesebieter [2019-04-03 11:06 +0200]:
* Anton Ivanov [2019-04-03 09:43 +0100]:
Package: nis
Version:
Package: irqbalance
Version: 1.5.0-3
Severity: normal
15:05 < Diziet> Starting SMP IRQ Balancer: irqbalancestart-stop-daemon: unable
to start /usr/sbin/irqbalance (Exec format error)
15:06 < Diziet> What fun, if you install linux-image-amd64 on an i386 host it
Package: devscripts
Version: 2.19.4
Severity: normal
User: de...@kali.org
Usertags: origin-kali
We imported many repositories (through a manifest file) on gitlab.com and
they were all lacking descriptions. When I ran my update_safe command to
rename all the descriptions I got lots of unitialized
On 18/04/2019, Martin Guy wrote:
> The v0.9.1 branch "make install"s for me, however, and that is from
> October 2016.
Ah. It seemed to work when I tested it, but stopped doing so when I
removed the stable Debian package. Now it gives a blank screen because
uzbl-event-manager fails to start.
Package: devscripts
Version: 2.19.4
Severity: normal
User: de...@kali.org
Usertags: origin-kali
I'm running this command:
$ salsa --conf-file salsa-auth.conf --conf-file +./salsa-packages.conf
update_safe --all --yes --no-fail --verbose
salsa-auth.conf has my token and the API URL, and
Control: fixed -1 2:4.8.1+dfsg-1
Le jeu. 11 avr. 2019 à 22:06, Alexander Toresson
a écrit :
>
> Package: samba-common
> Version: 2:4.2.14+dfsg-0+deb8u12
>
> Hi,
>
> Suddenly my smb shares stopped working. I found out that an unattended
> upgrade of samba-common hade replaced (!) smb.conf, for
Package: usbutils
Version: 1:007-4+b1
Severity: important
File: /usr/bin/lsusb
Dear Maintainer,
I stumbled into `/usr/share/hwdata/usb.ids`, looking to see why some of my USB
devices where not recognized,
even though being not particulary recent. I was really surprised to that the
hardware
On Thu, 11 Apr 2019 18:35:04 +0200 Nicolas Schier wrote:
> On https://github.com/uzbl/uzbl there is a tag 'v0.9.1' available, but
> probably the 'master' or 'next' branch could also make sense...
The master branch doesn't build on current Debian stable - "git bisect
run make" thinks that the
* Elimar Riesebieter [2019-04-03 11:06 +0200]:
> * Anton Ivanov [2019-04-03 09:43 +0100]:
>
> > Package: nis
> > Version: 3.17.1-3+b1
> > Severity: critical
> > Justification: breaks unrelated software
> >
> > Dear Maintainer,
> >
> > Startup scripts are completely broken. Something in the
Package: wnpp
Severity: wishlist
Owner: Steffen Moeller
* Package name: tophat-recondition
* URL : https://github.com/cbrueffer/tophat-recondition
* License : custom
Programming Lang: Python
Description : post-processor for TopHat unmapped reads
The package is to
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "urlwatch"
* Package name: urlwatch
Version : 2.17-1
Upstream Author : Thomas Perl
* URL : https://thp.io/2008/urlwatch/
* License : BSD-3-clause
Package: wnpp
Severity: wishlist
Owner: Mo Zhou
* Package name: blingfire
Version : git-HEAD
Upstream Author : Microsoft
* URL : https://github.com/Microsoft/BlingFire
* License : MIT
Programming Lang: C++, Python, Perl, Batch, etc
Description :
On Thu, 18 Apr 2019, László Böszörményi wrote:
#2 0x7334640f in __assert_fail_base
(fmt=0x734a8ee0 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n",
assertion=0x76657940 "semaphore_info != (SemaphoreInfo *) NULL",
file=0x766578c8 "magick/semaphore.c", line=606,
function=) at
Michael Biebl wrote:
> On Mon, 8 Apr 2019 01:10:28 +0200 Michael Biebl wrote:
>> Control: tags -1 moreinfo
>>
>> Am 07.04.19 um 18:51 schrieb Andy Ruddock:
>>> Package: systemd
>>> Severity: critical
>>>
>>> I'm running Windows 10 (Home edition - up to date) on the desktop, with
>>> Virtualbox
Hi,
Le 18/04/2019 à 21:33, David Prévot a écrit :
> Le 14/04/2019 à 04:27, Ondřej Surý a écrit :
>> I am actually not sure this is related to PHP update
FWIW, upstream already provided a [workaround], and the root issue is
discussed in [#77896].
workaround:
to 18. huhtik. 2019 klo 11.27 Daniel Högele - adelphi
(hoeg...@adelphi.de) kirjoitti:
>
> >Maybe if you have apache compiled with the version X of the library,
> and then you upgrade Apache but not keeping in sync the libraries if
> might break down.
>
> Never compiled anything. Just simple "apt
Hi,
On Fri, 5 Apr 2019 23:26:55 +0200 =?UTF-8?Q?Bernhard_=c3=9cbelacker?=
wrote:
> Dear Maintainer,
> just tried to help triaging this issue.
Me too.
>
> Seems this is "expected" behaviour with LC_ALL not
> set to "C". In the end it leads to this upstream bug:
>
>
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package node-superagent
Hi all,
node-superagent is vulnerable to CVE-2017-16129 (tag high). Unfortunatly
no corresponding BTS has been filled, and I didn't see this before.
Hi,
Le 14/04/2019 à 04:27, Ondřej Surý a écrit :
> I am actually not sure this is related to PHP update, see the error:
>
> + rm -rf ./vendor
> + patch -Rp1
> patching file
> src/Symfony/Component/Form/Tests/Console/Descriptor/AbstractDescriptorTest.php
> + exit 1
No, the error comes from way
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package dovecot
Dovecot 1:2.3.4.1-4, already in unstable, fixes a crash related to
processing of invalid external input. The issue is known as
CVE-2019-10691[1], and was
Package: segemehl
Version: 0.3.4-1
Severity: serious
Hi,
This package uses htslib, which is no longer supported on any-i386. #914991
removed the binaries on any-i386, but until any-i386 is removed from
Architecture:, wanna-build will re-build the package, thereby reinstating the
binaries on
Package: tabix
Version: 1.9-10
Severity: serious
Hi,
This package uses htslib, which is no longer supported on any-i386. #914991
removed the binaries on any-i386, but until any-i386 is removed from
Architecture:, wanna-build will re-build the package, thereby reinstating the
binaries on any-i386.
Package: qtltools
Version: 1.1+dfsg-3
Severity: serious
Hi,
This package uses htslib, which is no longer supported on any-i386. #914991
removed the binaries on any-i386, but until any-i386 is removed from
Architecture:, wanna-build will re-build the package, thereby reinstating the
binaries on
Package: augustus
Version: 3.3.2+dfsg-2
Severity: serious
Hi,
This package uses htslib, which is no longer supported on any-i386. #914991
removed the binaries on any-i386, but until any-i386 is removed from
Architecture:, wanna-build will re-build the package, thereby reinstating the
binaries on
Package: samtools
Version: 1.9-4
Severity: serious
Hi,
This package uses htslib, which is no longer supported on any-i386. #914991
removed the binaries on any-i386, but until any-i386 is removed from
Architecture:, wanna-build will re-build the package, thereby reinstating the
binaries on
Package: delly
Version: 0.8.1-2
Severity: serious
Hi,
This package uses htslib, which is no longer supported on any-i386. #914991
removed the binaries on any-i386, but until any-i386 is removed from
Architecture:, wanna-build will re-build the package, thereby reinstating the
binaries on
Package: libhts2
Version: 1.9-10
Severity: serious
Hi,
This package uses htslib, which is no longer supported on any-i386. #914991
removed the binaries on any-i386, but until any-i386 is removed from
Architecture:, wanna-build will re-build the package, thereby reinstating the
binaries on
Package: nanopolish
Version: 0.11.0-2
Severity: serious
Hi,
This package uses htslib, which is no longer supported on any-i386. #914991
removed the binaries on any-i386, but until any-i386 is removed from
Architecture:, wanna-build will re-build the package, thereby reinstating the
binaries on
Package: libhts-dev
Version: 1.9-10
Severity: serious
Hi,
This package uses htslib, which is no longer supported on any-i386. #914991
removed the binaries on any-i386, but until any-i386 is removed from
Architecture:, wanna-build will re-build the package, thereby reinstating the
binaries on
> I’ve also found another wrong copyright year, while reviewing the
I found some more. For ease of review, the complete diff follows,
and I’ll upload (the -6) when I get the ACK. The diff, while still
trivial, is now a bit longer because it adds the CC-BY 3.0 legal
code, the need for which was
On 4/18/19 12:24 PM, Dmitry Bogatov wrote:
> Looks fine. Are you sure you want to upload into unstable now, during
> freeze? It may cause inconvenience should need to fix RC bug in
> previous version arise.
Hi Dmitry,
No problem, this can wait.
--
Olivier
Le 18/04/2019 à 13:53, Raphaël Hertzog a écrit :
> Package: devscripts
> Version: 2.19.4
> Severity: normal
> User: de...@kali.org
> Usertags: origin-kali
>
> $ salsa --group freexian-team list_groups
> Id : 3695
> Name : Extended LTS
> Full path: freexian-team/extended-lts
> Parent id:
Package: devscripts
Version: 2.19.4
Severity: normal
User: de...@kali.org
Usertags: origin-kali
$ salsa --group freexian-team list_groups
Id : 3695
Name : Extended LTS
Full path: freexian-team/extended-lts
Parent id: 2925
$ salsa --group freexian-team/extended-lts group
salsa error Bad
On 18 April 2019 at 13:27, Paul Gevers wrote:
| That check is for a version of r-cran-permute not yet in Debian, for
A bug in r-cran-permute.
In Google-speak, 'CRAN lives at HEAD'. The top of its release repo (ie the
CRAN mirrors) is what we would call a release and guaranteed to work across
Control: tags -1 confirmed d-i
Colin Watson:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: unblock
>
> Please unblock openssh 1:7.9p1-10; as discussed recently on
> debian-devel, this reverts an upstream change in 7.8 that causes
>
Thank you for your detailed advice, David.
On Thu, Apr 18, 2019 06:18 PM, David Rabel wote:
> James suggests there, that we could use dh-vim-addon for packaging and
> drop our maintainer scripts. That would be a nice cleanup of the package.
That sounds good. If there is a dedicated debhelper
Hi Dirk,
On Thu, 18 Apr 2019 05:38:34 -0500 Dirk Eddelbuettel wrote:
> I have argues before that these need to be reassigned as these packages
> generally build at CRAN -- and test in a wider (OS-wise speaking) setting
> than we have. See eg
>
Package: debconf
Version: 1.5.71
Severity: wishlist
File: /usr/sbin/dpkg-reconfigure
User does
# dpkg-reconfigure some_package
and starts answering some questions,
and some more,
and some more...
Therefore, somewhere on the screen, please add a running tally of which
question we are on, (e.g.,
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package salt
This version fixes the test_xen_virtual test case (bug #922352) and
exposes tornado4 as tornado for zmq.eventloop.ioloop (bug #924763). Our
salt
package: voctomix-outcasts
severity: important
x-debbugs-cc: 927...@bugs.debian.org, c...@nextdayvideo.com
Hi Carl,
On Thu, Apr 18, 2019 at 10:45:00AM +, Niels Thykier wrote:
> > voctomix-outcasts (0.8.0-1) unstable; urgency=medium
> Unblocked.
this is quite yay! (=it will make it into
retitle 926827 ruby-vcr: FTBFS randomly (failing tests)
severity 926827 important
tags 926827 + patch
thanks
Hi. This is really random, so I'm downgrading.
I've put a bunch of build logs here from my autobuilders:
https://people.debian.org/~sanvila/build-logs/ruby-vcr/
The failing test seems
>> I've always assumed that:
>>
>> - the rcX.d links are only meant to be changed by running "insserv"
>> (directly or via update-rc.d)
>>
>> - the dependencies of "/etc/init.d/foo" should be changed via
>> "/etc/insserv/overrides/foo"
>
> That sounds overly procrustean if applied rigorously,
Dmitry Bogatov writes ("Bug#711853: insserv: Design bug: rcN.d unstable and
not, maintainable"):
> [2019-04-17 18:02] Alessandro Vesely
> > I just meant respecting the existing order, either if possible or if a fix
> > is
> > not at all obvious. Suppose A requires B and B requires A, a
On 18 April 2019 at 09:28, Paul Gevers wrote:
| Source: r-base
| Severity: important
| User: debian...@lists.debian.org
| Usertags: breaks
| Control: affects -1 r-cran-permute
| Control: affects -1 r-cran-phangorn
| Control: affects -1 r-cran-popepi
| Control: affects -1 r-cran-recipes
|
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package voctomix-outcasts, it's a fringe package only
used by some conference video setups, which requested fixes for these
bugs:
voctomix-outcasts (0.8.0-1) unstable;
--27303_ĵaÅ_Apr_18_10_24_27_UTC_2019
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Here is prelimitary patch, that implement the check. It seems to affect
t/tags/checks/init.d/init.d-lsb-depends-nonrel/ check, and, maybe,
something else -- I did not
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package developers-reference:
$ debdiff developers-reference_3.4.23.dsc
developers-reference_3.4.24.dsc|diffstat
debian/changelog |9 ++
po4a/po/de.po
[2019-04-17 18:02] Alessandro Vesely
> On Wed 17/Apr/2019 00:44:26 +0200 Dmitry Bogatov wrote:
> > Right now insserv implements little more than topological sort. You can
> > modify relations between scripts by editing LSB headers. What do you
> > mean 'adjusting links without subverting
[2019-04-17 12:33] Olivier Girondel
> Package: sponsorship-requests
> Severity: normal
>
> Dear mentors,
>
> I am looking for a sponsor for my package "lebiniou":
>
> * Package name: lebiniou
>Version : 3.31-1
>Upstream Author : Olivier Girondel
> * URL :
Hello Yue Lan,
On 4/16/19 5:57 AM, Yue Lan wrote:
>
> I'm interested in taking over this package. I've been doing my daily
> work with Debian and Ubuntu for over a year but haven't made a
> contribution to the community yet, and now I want to make some changes
> to my work.
That's great!
>
Control: reassign -1 ftp.debian.org
Hi Elana,
On 17-04-2019 19:22, Elana Hashman wrote:
> This package was initially uploaded because leiningen-clojure was pinned
> to Clojure 1.8 while the clojure package was updated to 1.9 and onward.
> clojure/1.10 is currently in testing and
Hello Marcus Lundblad,
I don't know if it is related - I own a Baytrail
device that contains also these axp devices.
Back in late 2017 I got some help from Hans de Goede,
who worked that time in that area.
There my battery information was also missing with
the stock debian kernel.
He suggested to
Control: tags -1 moreinfo confirmed
Alberto Molina Coballes:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: unblock
>
> Please unblock package ebtables
>
> A serious bug was opened on ebtables and arptables regarding an issue
> with
Control: tags -1 moreinfo confirmed
Alberto Molina Coballes:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: unblock
>
> Please unblock package arptables
>
> A serious bug was opened on ebtables and arptables regarding an issue
> with
Hello Christian,
>> Hello, as said, please switch to nlohmann-json3, it seems supported
>> according to my build on DOM:
>
>Nothing important here. Severity set to normal.
the reason for setting the severity to important, is that this is the last
package depending on the oldnlohmann-json
On Wed, Apr 17, 2019 at 08:32:29PM +0200, Thorsten Alteholz wrote:
>
>
> On Sun, 14 Apr 2019, Jongmin Kim wrote:
> > https://salsa.debian.org/go-team/packages/golang-github-jesseduffield-gocui
>
> this shows:
> gbp:info: Cloning from
>
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please consider unblocking package calamares-settings-debian
Recently, I put out a call for testing for debian-live, and my #1
feedback from random users and Debian Developers alike was
Source: ganeti
Version: 2.15.2-7+deb9u3
Severity: important
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: flaky
Control: found -1 2.16.0-5
Dear maintainers,
Your package has an autopkgtest, great. However, it fails
once in a while in unstable, testing and
Source: kgb-bot
Version: 1.54-1
Severity: important
User: de...@kali.org
Usertags: origin-kali
We wanted to use kgb-bot with repositories hosted on gitlab.com but
the "webhook" support in KGB needs a whitelist of the IP that generates
the request. Unfortunately with a large infastructure such as
Hi Daniel, Doko
On 18-04-2019 06:36, Debian Bug Tracking System wrote:
> #920455: bash 5.0 "wait" builtin waits on "process substitution" subprocesses
>
> It has been closed by Matthias Klose .
I confirm that with this version of bash the autopkgtest timeout of
monkeysphere on the ci.d.n
Package: libdvbv5-0
Version: 1.16.3-2
Severity: important
Dear Maintainer,
upgrading the package to version 1.16.3-2, kaffeine breaks because no
longer finds the dvb adapter:
$ kaffeine
18-04-19 08:53:55.669 [Info] kaffeine.dvb: Using built-in dvb device manager
18-04-19 08:53:55.973
Package: plantuml
Version: 1:1.2018.13+ds-1
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
plantuml package declares a dependency on default-jre but is usable from
command-line so seems to only really need default-jre-headless.
If some features really need default-jre then
Package: ruby-i18n
Version: 1.5.3-1
The ruby-i18n 1.5.3-1 version currently shipped in Debian Buster ships
the gemspec as 0.7.0:
/usr/share/rubygems-integration/all/specifications/i18n-0.7.0.gemspec
I don't understand how or why there's a version mismatch there, but
it's actually useful as other
Package: command-not-found
Version: 18.04.5-1
Severity: minor
Dear Maintainer,
-- System Information:
Distributor ID: PureOS
Description:PureOS GNU/Linux 8
Release:8
Codename: green
Architecture: x86_64
Kernel: Linux 4.19.0-4-amd64 (SMP w/4 CPU cores)
Kernel taint flags:
On Thu, Apr 18, 2019 at 10:23:19AM +0200, Giovanni Mascellani wrote:
> Il 17/04/19 23:20, Santiago Vila ha scritto:
> > I'm really sorry. My apologies.
>
> Don't worry, it is perfectly reasonable. I did not realize it myself. I
> do not use overlayfs, so I'd say the problem is in eatmydata, which
Hi,
wow, how nasty! :-)
Il 17/04/19 23:20, Santiago Vila ha scritto:
> I'm really sorry. My apologies.
Don't worry, it is perfectly reasonable. I did not realize it myself. I
do not use overlayfs, so I'd say the problem is in eatmydata, which is
apparently not as transparent as it should. Do
>Maybe if you have apache compiled with the version X of the library,
and then you upgrade Apache but not keeping in sync the libraries if
might break down.
Never compiled anything. Just simple "apt install" from debian repositories.
>With the information provided I cannot reproduce the issue
On Thu, Apr 18, 2019 at 09:28:55AM +0200, Paul Gevers wrote:
> Source: r-base
> Severity: important
> User: debian...@lists.debian.org
> Usertags: breaks
> Control: affects -1 r-cran-permute
> Control: affects -1 r-cran-phangorn
> Control: affects -1 r-cran-popepi
> Control: affects -1
Package: uzbl
Version: 0.0.0~git.20120514-1.2
Severity: normal
Dear Maintainer,
the current Debian version of uzbl is quite old. Can you please update
uzbl to a more current version?
On https://github.com/uzbl/uzbl there is a tag 'v0.9.1' available, but
probably the 'master' or 'next' branch
Package: gnupg
Version: 2.2.12-1
Severity: normal
Hello,
TLDR; please tell the user how to migrate from jessie to buster.
after upgrading from jessie to buster, `gpg --search-keys` stopped
working with:
$ gpg --search-keys 1397BC53640DB551
gpg: WARNUNG: Tor is not running
gpg:
Am 18.04.19 um 01:43 schrieb Jul':
> Sorry for the lack of details.
>
> 1) how udev assigns this name?
>
> Since I have no custom udev rule, AFAIK, udev assigns it with the standards
> rules (in "/lib/udev/rules.d/60-persistent-alsa.rules" since it is a sound
> device).
>
This rules file
Hi Jonathan,
Jonathan Carter:
> KMS seems to work just fine, I see the full-resolution plymouth splash,
> it's only when Xorg starts when the screen goes blank (I can switch to
> VTs though).
Well, it may work well enough for Plymouth but both the kernel and
X.Org try to use modesetting and
Source: r-base
Severity: important
User: debian...@lists.debian.org
Usertags: breaks
Control: affects -1 r-cran-permute
Control: affects -1 r-cran-phangorn
Control: affects -1 r-cran-popepi
Control: affects -1 r-cran-recipes
Control: affects -1 r-cran-sp
Control: affects -1 r-cran-spam
Control:
Package: pmount
Version: 0.9.99-alpha-1
Severity: important
Repro:
suspend all HDDs (including the magnetic ones I have here)
hdparm -y /dev/sd*
Enter "pmount"
Result:
magnetic disks are spining up because something wants to read from them.
I can catch the troublemaker, usually it's:
root
reopen 924829
kthxbye
Since BTS cannot clone merged bugs, and thus very intelligently we
cannot carry over the discussion, let us reopen this bug again ..
(so many years and still not fixed lovely BTS ...)
Norbert
--
PREINING Norbert http://www.preining.info
clone 924829 -1
close 924829 2018.20190227-1
thanks
> reopen 924829
This is a different bug then the one reported here. Closing this bug
again, and cloning it for another.
Uploading after bug number is assigned.
Norbert
--
PREINING Norbert
On Wednesday, 17 April 2019 19:03:26 CEST Boyuan Yang wrote:
> I found that this will happen when I set the default font to be Noto Sans
> CJK SC with arbitary font weight. By resetting the font to default, the
> email viewer would recover back to normal however the composer is always
> missing
> @Norbert: can we risk it to upload that new tabu.sty to unstable?
Yes.
Preparing an upload now.
Norbert
--
PREINING Norbert http://www.preining.info
Accelia Inc. +JAIST +TeX Live +Debian Developer
GPG: 0x860CDC13 fp: F7D8 A928 26E3 16A1
Hello Brian,
Am 18.04.19 um 06:25 schrieb Brian Holaday:
> Is there a way we can get an update into backports from 5.0.2 to 5.1.1
> in Stretch?
currently not.
The rule for backports is simple, the same version needs to be available
in testing. This can't be fulfilled now as testing is completely
101 - 180 of 180 matches
Mail list logo
