Bug#928921: reprotest: kernel too old SIGSEGV

On 2019-05-13, Dmitry Bogatov wrote: > Hello. I am working on setting up CI for my packages, and one of them > fail "reprotest" phase with error: "FATAL: kernel too old"[1][2]. This is probably due to the kernel variation using "setarch", which will cause uname to report a 2.6 kernel, which is

Bug#928924: user-mode-linux: xterm functionality broken due to wrong path to port-helper

Package: user-mode-linux Version: 4.19-1um-1 Severity: important File: /usr/bin/linux.uml linux.uml in a GNOME terminal gives these errors in new tabs: There was an error creating the child process for this terminal Failed to execute child process “port-helper” (No such file or directory) The

Bug#928923: linux-image-4.19.0-4-cloud-amd64: reports different NIC name than linux-image-amd64 on virtio-net

Package: src:linux Version: 4.19.28-2 Severity: normal Environment: Proxmox VE host, 5.4-1 KVM guest, Debian 10 testing virtio_net NIC With linux-image-4.19.0-4-cloud-amd64: # udevadm test-builtin net_id /sys/class/net/en* Load module index Parsed configuration file

Bug#914034: Bug#911938: libhttp-daemon-ssl-perl FTBFS: tests fail: Connection refused

On Mon, May 13, 2019 at 01:02:45AM +0200, Guilhem Moulin wrote: > Thanks for your analysis, Steffen. Dropping the Debian-specific patch > is definitely the way to go for libwww/LWP. However I still believe > IO::Socket::SSL should provide a way to clear SSL_MODE_AUTO_RETRY in > order to fix

Bug#928810: patch: Make debian-watch-uses-insecure-uri more generic

[2019-05-11 16:08] Jelmer Vernooij > On Sat, May 11, 2019 at 02:49:11PM +, Dmitry Bogatov wrote: > > From 2789fed85a6088c85f8f37ba96984eb7f3d8e8ef Mon Sep 17 00:00:00 2001 > > From: Dmitry Bogatov > > Date: Fri, 10 May 2019 23:32:01 + > > Subject: [PATCH] Make

Bug#928811: patch: New fixer: patch-file-present-but-not-mentioned-in-series.sh

[2019-05-11 15:56] Jelmer Vernooij > Thanks! Makes sense. > > Any chance you could add a test case for this under > tests/patch-file-present-but-not-mentioned-in-series/? Sure. From 6e795731f4ae266954acf9de70ace6f0ea4e944c Mon Sep 17 00:00:00 2001 From: Dmitry Bogatov Date: Sat, 11 May 2019

Bug#928918: hurd: taking over /etc/hurd/runsystem.sysv

Package: hurd Severity: normal Affects: initscripts Blocks: 922962 Dear Maintainer, bin:initscripts ships /etc/hurd/runsystem.sysv file on hurd architecture, thus making bin:initscript arch:any, which is quite unfortunate, given that both "/etc/hurd/runsystem.sysv" and rest of bin:initscript

Bug#928394: RFS: freetype-py/2.1.0.post1-1 [ITP]

[2019-05-09 22:35] Bastian Germann > I have changed that and also made the smoke test run. Fine. Uploaded. I also suggest you to use Gitlab CI. See here: https://salsa.debian.org/salsa-ci-team/pipeline/ -- Note, that I send and fetch email in batch, once every 24 hours.

Bug#928920: patch: Introduce logging functions that check ${VERBOSE}

Package: lsb-base Severity: wishlist Tags: patch From 58dd6e6add24a4e5531a84ff2404f2f5ed71e114 Mon Sep 17 00:00:00 2001 From: Dmitry Bogatov Date: Sat, 11 May 2019 21:20:48 + Subject: [PATCH] Introduce logging functions that check ${VERBOSE} Use of logging functions in initscripts are

Bug#928921: reprotest: kernel too old SIGSEGV

Package: reprotest Version: 0.7.8 Severity: normal Hello. I am working on setting up CI for my packages, and one of them fail "reprotest" phase with error: "FATAL: kernel too old"[1][2]. I grepped upstream sources for "kernel too old" message and found nothing. Regular build is successful. Any

Bug#928922: devscripts: make debrepro use debuild

Package: devscripts Version: 2.19.4 Severity: wishlist Dear Maintainer, please consider using "debuild" instead of "dpkg-buildpackage" in "debrepro" script to avoid spurious failures in unsual environments (effectful environment variables, unexpected binaries in PATH, ...) Alternatively (not

Bug#928919: patch: Do not hide errors from initscripts

Package: initscripts Severity: wishlist Tags: patch From 987ac0ec780a063052346ff8adb33a072694ae11 Mon Sep 17 00:00:00 2001 From: Dmitry Bogatov Date: Sat, 11 May 2019 20:19:11 + Subject: [PATCH] Do not hide errors from initscripts --- debian/src/initscripts/etc/init.d/bootlogs

Bug#921600: closed by "Arnaud Rebillout" ()

On Fri, 10 May 2019 22:12:46 + "brian m. carlson" wrote: > On Fri, May 10, 2019 at 02:12:04AM +, Debian Bug Tracking System wrote: > > > > This bug was fixed upstream already, see: > > - https://github.com/docker/libnetwork/pull/2343 > > -

Bug#928500: mentors.debian.net

Hi, FYI: https://mentors.debian.net/package/gsequencer cheers, Joël

Bug#928917: contents

-- Deleting module version: 4.19+20190211 completely from the DKMS tree. -- Done. Loading new aufs-4.19+20190211 DKMS files... Building for 4.19.0-4-amd64 Building initial module for 4.19.0-4-amd64 Done. aufs.ko: Running module version

Bug#928917: aufs-dkms: debian 10 don't install aufs-dkms

Package: aufs-dkms Version: 4.19+20190211-1 Severity: important Dear Maintainer, Subject: aufs-dkms: debian 10 don't install aufs-dkms package Package: aufs-dkms Version: 4.19+20190211-1 Severity: important Dear Maintainer, I want to install docker-ce in debian10. docker-ce relies on

Bug#928879: sample log

To: Mike Hommey Cc: related maintainers On 5/13/19 8:38 AM, Mike Hommey wrote: On Sun, May 12, 2019 at 08:52:20PM +0900, hoxp18 wrote: Dear maintainers, I forgot to add the sample log. Apology. kernel: [ sec] audit: type=1400 audit(X.YYY:ZZZ): apparmor="DENIED" operation="mknod"

Bug#928916: "System error during SSL_connect(): Success"

Package: fetchmail Version: 6.3.26-3 Severity: wishlist >From time to time I invoke fetchmail, and it fails with fetchmail: System error during SSL_connect(): Success fetchmail: SSL connection failed. which is a rather confusing error message. My libssl is 1.1.0j-1~deb9u1.

Bug#928915: Full log unavailable with -e or -x

Hmm, it seems there's been a change in behavior? Before I upgraded, I could access the full log with -xe, but it seems that now -e implies -n1000? So I guess this isn't explicitly an issue, but it was a surprise after I upgraded. Sincerely, Chiraag -- ಚಿರಾಗ್ ನಟರಾಜ್ Graduate Student at Brown

Bug#928915: systemd: Full log unavailable with -e or -x

Package: systemd Version: 242-1 Severity: normal Dear Maintainer, Different invocations of journalctl seem to display different amounts of the log. $ sudo journalctl -xe -- Logs begin at Sun 2019-05-12 20:37:51 EDT, end at Sun 2019-05-12 21:16:32 EDT. -- ಮೇ 12 20:44:29 chiraag env[8395]:

Bug#928914: Fix for #898892 breaks normal usage

Never mind, I'm an idiot. The name of the unit was boinc-client.service. Sincerely, Chiraag signature.asc Description: PGP signature

Bug#928914: systemd: Fix for #898892 breaks normal usage

Package: systemd Version: 242-1 Severity: normal Dear Maintainer, It seems the fix for #898892 renders bare unit names unusable. Example: $ sudo journalctl --unit boinc -- No entries -- $ sudo journalctl --unit boinc* ಮೇ 12 20:39:36 chiraag systemd[1]: Started Berkeley Open Infrastructure

Bug#928894: [pkg-gnupg-maint] Bug#928894: custom keyring is not honoured

Hi Daniel, On Sun, May 12, 2019 at 06:52:17PM -0400, Daniel Kahn Gillmor wrote: > I'm not sure that this demonstrates what you're describing. > > Here is a run with gpg 2.2.15-1 that demonstrates the key being fetched > into the extra keyring: > > 0 dkg@alice:/tmp/cdtemp.AhkyjS$ export

Bug#928879: sample log

On Sun, May 12, 2019 at 08:52:20PM +0900, hoxp18 wrote: > Dear maintainers, > > I forgot to add the sample log. Apology. > > kernel: [ sec] audit: type=1400 audit(X.YYY:ZZZ): > apparmor="DENIED" operation="mknod" > profile="/usr/share/firefox-esr/firefox-esr" >

Bug#927462: Bug #927462: megadown: Does not download anything

Hi, Did you see this bug on the megadown package ? I saw that your maintainer email (vivia.nikolai...@puri.sm) is not the one you used when creating bugs before (n.vi...@gmail.com), so I am mailing both just in case. On Sat, 20 Apr 2019 09:12:53 +0300 jim_p wrote: > Package: megadown >

Bug#928913: unblock: elpy/1.28.0-2

Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package elpy I'm filing this unblock request before uploading to unstable. This proposed upload closes several documentation-related bugs, and disables DH_VERBOSE. In

Bug#928901: shutdown-qapps FTCBFS: missing Build-Depens: qt5-qmake:native

Thank you Helmut! I will take a look this evening (Tokyo time).  There were some updates to the source that I wanted to do anyway. Best regards, Christian On 2019年5月13日 3:47:53 JST, Helmut Grohne wrote: >Source: shutdown-qapps >Version: 1.7.3-1 >Tags: patch >User: helm...@debian.org

Bug#925546: How to reproduce?

Hi, On Wed, 17 Apr 2019 15:27:19 +0300 Joonas Kylmälä wrote: > Hi, > > Hilko Bengen: > > I can get rid of the issues by backporting a number of commits from > > github.com/nsf/gocode and will submnit an updated package for > > stretch-proposed-updates. > > Thanks for investigating. > > > Are you

Bug#914034: Bug#911938: libhttp-daemon-ssl-perl FTBFS: tests fail: Connection refused

Thanks for your analysis, Steffen. Dropping the Debian-specific patch is definitely the way to go for libwww/LWP. However I still believe IO::Socket::SSL should provide a way to clear SSL_MODE_AUTO_RETRY in order to fix applications relying on the former OpenSSL defaults, as suggested in the

Bug#928912: shorewall: Shorewall does not automatically start after (re-)boot

Package: shorewall Version: 5.0.15.6-1 Severity: important Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? Clean install of the package, copied known good relevant interfaces, rules, zones, etc files

Bug#928894: [pkg-gnupg-maint] Bug#928894: custom keyring is not honoured

Control: tags 928894 + moreinfo Hi Toni-- On Sun 2019-05-12 19:46:45 +0100, Toni wrote: > --recv-keys does not seem to honour the keyring options, so the received > key ends up in the wrong keyring: > > $ touch ~/mnt/tools/gitea-keys.gpg > $ gpg --no-default-keyring --keyring

Bug#928892: RFS: heimdall-flash/1.4.2-1

Ah, I see. That must have been when I pasted the example text, I noticed some weard  formating in my mail client, I should have been more careful. Anyway, thank you for the help. Regards. May 13, 2019, 12:11 AM by bernha...@mailbox.org: > Hello Francois, > it looks like your email did not

Bug#928868: unblock: ruby-globalid/0.4.2+REALLY.0.3.6-1

Hey, On Mon 13 May, 2019, 12:42 AM Paul Gevers, wrote: > Hi Utkarsh, > > On 12-05-2019 11:44, Utkarsh Gupta wrote: > > Hence, requesting you to: > > unblock ruby-globalid/0.4.2+REALLY.0.3.6-1 > > It would have been easier if you would have left the old patches in > place, but anyways. Thanks

Bug#928892: RFS: heimdall-flash/1.4.2-1

Hello Francois, it looks like your email did not contain any newlines. Therefore it seems like the whole email was interpreted as the "package". You can see what I mean in this page [1] near "Bug reassigned from package". Kind regards, Bernhard [1]

Bug#928892: RFS: heimdall-flash/1.4.2-1

I'm not sure I understand what the problem is, but please do what you think necessary. Did I make a mistake ? It is my first RFS so that is very probable, but I don't see it. Thanks for your help. Regards,  François Etcheverry May 12, 2019, 11:48 PM by bernha...@mailbox.org: > Control:

Bug#928911: grub-efi-amd64: destroys EFI partition despite being told not to

Package: grub-efi-amd64 Version: 2.02+dfsg1-18 Severity: important Hi! Just did a d-i bare-metal test run; installing to another disk, with the obvious requirement of not damaging the primary system. Thus, I explicitly marked all relevant partitions (EFI, sys, and swap) as "do not use". Yet the

Bug#926180: scilab: FTBFS on all - New trouble - upstream bugfix release while in freeze

Hi, Le 12/05/2019 à 22:10, Julien Puydt a écrit : > Hi, > > On 12/05/2019 11:46, Alexis Murzeau wrote: > >> I saw that there is a bugfix release 6.0.2 with many fixes [0]. > > I had started to package 6.0.2 on salsa already in february. I was wondering, will such bug-fix upstream release be

Bug#928892: RFS: heimdall-flash/1.4.2-1

Control: reassign 928892 sponsorship-requests Hello Francois, it looks like somthing ate all newlines in your email. I hope it is ok if I reassign to sponsorship-requests. Kind regards, Bernhard

Bug#928805: texlive-lang-czechslovak: fails to install: fmtutil failed

> Committed to git, tag pending. Thanks! Norbert -- PREINING Norbert http://www.preining.info Accelia Inc. +JAIST +TeX Live +Debian Developer GPG: 0x860CDC13 fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Bug#928666: Want dgit FAQ

Sean Whitton writes ("Re: Bug#928666: Want dgit FAQ"): > I would like to just get this published on the Debian wiki as soon as > possible; let me know if you really want to avoid that, Ian. Great! Please go ahead. That's great. (I haven't reviewed these, but it's a wiki...) Ian.

Bug#928910: feature request: support odroid-hc1

Package: flash-kernel Version: 3.98 Would it be possible to support odroid-hc1 single board computers with flash-kernel? Here is how I configure the board manually: https://wiki.debian.org/InstallingDebianOn/OdroidHC1 flash-kernel wouldn't need to deal with samsung firmware blobs, as those get

Bug#928805: texlive-lang-czechslovak: fails to install: fmtutil failed

tags 928805 + pending stop On 11.05.19 15:55, Andreas Beckmann wrote: Hi, > during a test with piuparts I noticed your package failed to install. As > per definition of the release team this makes the package too buggy for > a release, thus the severity. > Committed to git, tag pending. H. --

Bug#928909: bleachbit: new upstream 2.2

Package: bleachbit Version: 2.2 Severity: normal Please consider to upgrade to the current upstream version (2.2). Regards Jonatan

Bug#927852: Info received (Bug#927852: Acknowledgement (xwayland: GNOME Shell crashes after connecting ThinkPad Thunderbolt 3 Dock Gen 2 via Thunderbolt to a Lenovo T470))

Am Freitag, den 10.05.2019, 12:13 +0200 schrieb Michel Dänzer: > On 2019-05-07 7:13 a.m., - wrote: > > This morning GNOME Shell crashed again, see attached logs. > > Connecting/disconecting the Thunderbolt Gen2 Dock was working fine > > for > > 1-2 weeks, now it crashed again. > > > > Hope the

Bug#928908: unblock: libdebian-installer/0.119

Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock libdebian-installer/0.119 fixing RC bug #55 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=55 Changes: libdebian-installer (0.119) unstable; urgency=medium

Bug#928905: kguiaddons FTCBFS: missing Build-Depends: qttools5-dev

Source: kguiaddons Version: 5.54.0-1 Tags: patch User: helm...@debian.org Usertags: rebootstrap kguiaddons fails to cross build from source, because it misses a dependency on qttools5-dev. See #915122 for details. Please consider applying the attached patch. Helmut diff --minimal -Nru

Bug#901592: Bug#928428: unblock: [pre-approval] wicd/1.7.4+tb2-7

Hi Niels, Niels Thykier wrote: > Axel Beckert: > > Package: release.debian.org > > Severity: normal > > User: release.debian@packages.debian.org > > Usertags: unblock > > > > In the light of dhcpcd5 automremoval (#928056, #928104, #928105), I'd > > like to upload a wicd package which relies

Bug#928907: karchive FTCBFS: missing Build-Depends: qttools5-dev

Source: karchive Version: 5.54.0-1 Tags: patch User: helm...@debian.org Usertags: rebootstrap karchive fails to cross build from source, because it misses a build dependency on qttools5-dev. See #915122 for context. Please consider applying the attached patch. Helmut diff --minimal -Nru

Bug#928906: pd-chaos FTCBFS: strips with the wrong strip

Source: pd-chaos Version: 0.2-3 Tags: patch User: helm...@debian.org Usertags: rebootstrap pd-chaos fails to cross build from source, because it uses the wrong strip during make install. Beyond breaking cross compilation, this also breaks DEB_BUILD_OPTIONS=nostrip as well as generation of -dbgsym

Bug#926180: scilab: FTBFS on all - New trouble

Hi, On 12/05/2019 11:46, Alexis Murzeau wrote: > I saw that there is a bugfix release 6.0.2 with many fixes [0]. I had started to package 6.0.2 on salsa already in february. I removed the patch about Linenum as that was supposed to have been reworked and fixed, and it now fails with : ocamlopt

Bug#907733: curlpp package still orphaned?

JB: > Hi, > > I would be interested in taking over this package but I'm confused ; it > seemed to have attracted other interested people as well, but the package is > still being listed as looking for a maintainer. > > So, I just wanted to know if someone (Jaime?) had taken over or if this >

Bug#858245: gmusicbrowser: Search-as-you-type causes crash

The fix works, Thank you!

Bug#928904: onionshare: new upstream 2.1

Package: onionshare Version: 2.1 Severity: High Please consider to upgrade to the current upstream version (2.1). Regards Jonatan

Bug#928903: ITP: piperka-client -- Mobile oriented web comics reader client

Package: wnpp Severity: wishlist Owner: Kari Pahula * Package name: piperka-client Version : 0.2.1 Upstream Author : Kari Pahula * URL : https://gitlab.com/piperka/client * License : GPLv2 or later Programming Lang: C++ Description : Mobile oriented

Bug#740504: Please Confirm This Information if you are Dead or Alive.

*Confirm This Information.* *It is totally against the ethics and civil service code of conduct in accordance with oath of secrecy for me to do this but I wish to do this on personal capacity believing you will not betray me but will surely come back to reward me for my sincerity, honesty and for

Bug#928717: in normal builds local urresponsive flas are parsed to build process

Control: tags -1 moreinfo Hello, I don't know asterisk at all but maybe I can help with triaging this bug. On Thu, 9 May 2019 12:10:08 -0400 PICCORO McKAY Lenz wrote: > Cited from upstream For a native x86_64 build, you need to REMOVE {{-fPIE}} > from the CFLAGS and {{-fPIE -pie}} from

Bug#928808: tracker.debian.org: automatic filing bugs

Hi, On Sat, 11 May 2019, Dmitry Bogatov wrote: > would it be possible to automatically file bugs with issues, already > detected by tracker? Right now, there's no email notification and I certainly agree that there should be some email notification about new upstream releases. Wouldn't that be

Bug#928367: libpapi5: SOVERSION is too wide for the runtime check in PAPI_library_init()

Control: tag -1 pending patch fixed-upstream On 2019-05-12 20:15, Andreas Tille wrote: > in the thread on the upstream mailing list[1] you proposed a patch that > was confirmed working by upstream. Do you think this patch should be > submitted to Debian BTS and the bug tagged patch? It's

Bug#928046: ~ Re: Bug#928046: dosbox: input issues under Wayland (some keys not behaving)

Hi all On Sat, May 11, 2019 at 11:36:00AM +, Niels Thykier wrote: Have you tried Stephen's suggestion of setting "usescancodes" and see if that fixes the issue? I hadn't, until now, but I can now confirm that this does resolve the issue. Thanks, -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Jonathan Dowland

Bug#928868: unblock: ruby-globalid/0.4.2+REALLY.0.3.6-1

Hi Utkarsh, On 12-05-2019 11:44, Utkarsh Gupta wrote: > Hence, requesting you to: > unblock ruby-globalid/0.4.2+REALLY.0.3.6-1 It would have been easier if you would have left the old patches in place, but anyways. Thanks for following up and reverting the new upstream version in unstable.

Bug#928897: pipemeter FTCBFS: strips with the build architecture strip

Source: pipemeter Version: 1.1.3-1 Tags: patch upstream User: helm...@debian.org Usertags: rebootstrap pipemeter fails to cross build from source, because it strips with the build architecture strip. Beyond breaking cross compilation, stripping at make install time also breaks

Bug#928902: spectrwm FTCBFS: uses build architecture build tools

Source: spectrwm Version: 3.2.0-1 Tags: patch User: helm...@debian.org Usertags: rebootstrap spectrwm fails to cross build from source, because it does not pass cross tools to make. The easiest way of fixing that - using dh_auto_build - is insufficient here. The relevant Makefile also hard codes

Bug#928900: efte FTCBFS: runs cmake for the build architecture

Source: efte Version: 1.1-2 Tags: patch User: helm...@debian.org Usertags: rebootstrap efte fails to cross build from source, because the cmake invocation lacks cross flags. The easiest way of fixing that is using dh_auto_configure. The attached patch implements that, but doesn't make efte cross

Bug#928898: t2n FTCBFS: multiple reasons

Source: t2n Version: 0.6-6 Tags: patch User: helm...@debian.org Usertags: rebootstrap t2n fails to cross build from source, because it does not pass cross tools to make. The easiest way to fix that - using dh_auto_build - is not sufficient here, because the Makefile hard codes gcc in one place

Bug#928901: shutdown-qapps FTCBFS: missing Build-Depens: qt5-qmake:native

Source: shutdown-qapps Version: 1.7.3-1 Tags: patch User: helm...@debian.org Usertags: rebootstrap shutdown-qapps fails to cross build from source, because it fails running lrelease. For using lrelease you must add qt5-qmake:native to Build-Depends. Please consider applying the attached patch.

Bug#928899: giftrans FTCBFS: uses the wrong compiler

Source: giftrans Version: 1.12.2-19 Tags: patch User: helm...@debian.org Usertags: rebootstrap giftrans fails to cross build from source, because debian/rules uses the build architecture compiler as a make default. The easiest way of fixing that - seeding $(CC) from dpkg's buildtools.mk - makes

Bug#928895: kmerresistance FTCBFS: uses the build architecture compiler

Source: kmerresistance Version: 2.0+git20180205.26467e9-1 Tags: patch User: helm...@debian.org Usertags: rebootstrap kmerresistance fails to cross build from source, because debian/rules hard codes plain "gcc". The easiest way of discovering the correct compiler is using dpkg's buildtools.mk.

Bug#928896: yabar FTCBFS: uses the wrong pkg-config

Source: yabar Version: 0.4.0-1 Tags: patch upstream User: helm...@debian.org Usertags: rebootstrap yabar fails to cross build from source, because the upstream Makefile hard codes the build architecture pkg-config. Making it substitutable is sufficient to fix this, but the cross build fails due

Bug#928894: custom keyring is not honoured

Package: gpg Version: 2.2.12-1 Severity: normal Hi, --recv-keys does not seem to honour the keyring options, so the received key ends up in the wrong keyring: $ touch ~/mnt/tools/gitea-keys.gpg $ gpg --no-default-keyring --keyring ~/mnt/tools/gitea-keys.gpg --recv-keys

Bug#928809: lintian: suggest adding gitlab-ci file

Mattia Rizzolo wrote: > > please add suggestion that if Vcs-Git points to salsa.debian.org, > > CI should be used. > > Please, don't. I'm somewhat inclined to agree with Mattia here but perhaps not as strongly - I'm a huge fan of CI systems to catch things. I'm not very happy with

Bug#928805: texlive-lang-czechslovak: fails to install: fmtutil failed

On 11.05.19 18:41, Norbert Preining wrote: Hi Norbert, > That needs some serious rework ... I tend to depend on texlive-lang-all > .. > Here is the list of not found files and the packages I had to install: hyph-en-gb texlive-lang-english hyph-it texlive-lang-italian hyph-de-1996

Bug#928367: libpapi5: SOVERSION is too wide for the runtime check in PAPI_library_init()

Hi Andreas, in the thread on the upstream mailing list[1] you proposed a patch that was confirmed working by upstream. Do you think this patch should be submitted to Debian BTS and the bug tagged patch? Kind regards Andreas. [1]

Bug#928891: linux-image-amd64: Kernel crash when using any disk that uses reiserfs

On Sun, 2019-05-12 at 18:34 +0200, Thanatermesis wrote: > Package: linux-image-amd64 > Version: 4.19+104 > Severity: important > > Dear Maintainer, > > When using any partition which uses reiserfs, the kernel crashes > > This happens very easily by just using the reiser (v3) filesystem, some >

Bug#928893: gnome-disk-utility: disk content permamently lost when changing LUKS password

Package: gnome-disk-utility Version: 3.30.2-3 Severity: important Dear Maintainer, * What led up to the situation? Install system using normal full disk encryption LUKS+Ext4. After install open gnome-disk-utility and change encryption password. It gives some error dialog and now you are

Bug#928892: RFS: heimdall-flash/1.4.2-1

Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "heimdall-flash" * Package name: heimdall-flash Version : 1.4.2-1 Upstream Author : Benjamin Dobell (@glassechidna ) * URL :

Bug#928861: flash-kernel: Please add an entry for FriendlyArm NanoPi NEO 2

On 2019-05-12, Karsten Merker wrote: > On Sun, May 12, 2019 at 10:40:39AM +0200, Domenico Andreoli wrote: >> +Machine: FriendlyARM NanoPi NEO 2 >> +Kernel-Flavors: arm64 >> +Boot-Script-Path: /boot/boot.scr >> +DTB-Id: allwinner/sun50i-h5-nanopi-neo2.dtb >> +U-Boot-Script-Name:

Bug#928887: hello: version skew: 2.10-1+deb9u1 (stretch-security) > 2.10-1 (buster)

On Sun, May 12, 2019 at 04:30:01PM +0200, Andreas Beckmann wrote: > Please do a dummy 2.10-2 upload to fix this ... I am in fact considering a not-so-dummy upload with minor changes, because after all this is a package to be copied and pasted, but I'll have to ask for permission to

Bug#928889: debhelper: dh_autoreconf says "sh: 1: build-aux/git-version-gen: not found"

Control: tags -1 moreinfo Santiago Vila: > Package: debhelper > Version: 12.1.1 > > Hello Niels. > Hi, > I tried using compat version 12 in package "hello" and this is what happened: > For reference/FYI, I suspect this will happen already at compat 10 or later (I noted that hello in sid

Bug#928891: linux-image-amd64: Kernel crash when using any disk that uses reiserfs

Package: linux-image-amd64 Version: 4.19+104 Severity: important -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Dear Maintainer, When using any partition which uses reiserfs, the kernel crashes This happens very easily by just using the reiser (v3) filesystem, some of my external hard disks

Bug#928505: fixed in ruby-pygments.rb 1.2.0-4

On Mon, 06 May 2019 11:48:47 + HIGUCHI Daisuke (VDR dai) wrote: > Source: ruby-pygments.rb > Source-Version: 1.2.0-4 > > We believe that the bug you reported is fixed in the latest version of > ruby-pygments.rb, which is due to be installed in the Debian FTP archive. > Hi dai, We will

Bug#915333: git-annex: Illegal Instruction on armel (Fujitsu Q700 like QNAP TS-21x/TS-22x)

On Sun, May 12, 2019 at 03:16:10PM +0300, Ilias Tsitsimpis wrote: > On Mon, Mar 11, 2019 at 12:05PM, Adrian Bunk wrote: > > On Thu, Jan 31, 2019 at 08:12:17PM +0100, Bernhard Übelacker wrote: > > > See attached file with several debugging attempts. > > > > Looking at the code, the bug seems to be

Bug#928666: Want dgit FAQ

Hello, I felt a desire to write some entries. I would like to just get this published on the Debian wiki as soon as possible; let me know if you really want to avoid that, Ian. ~ ~ ~ ~ ~ Q: Why should I bother to learn how to use dgit? A: If you incorporate `dgit push-source` into your

Bug#928889: debhelper: dh_autoreconf says "sh: 1: build-aux/git-version-gen: not found"

Package: debhelper Version: 12.1.1 Hello Niels. I tried using compat version 12 in package "hello" and this is what happened: sh: 1: build-aux/git-version-gen: not found sh: 1: build-aux/git-version-gen: not found sh: 1: build-aux/git-version-gen: not found sh: 1: build-aux/git-version-gen: not

Bug#927942: gucharmap: FTBFS with unicode-data >= 12

(note: I'm just someone taking a look to see what is blocking the unicode-data "transition", i'm not a maintainer of this package or a member of the release team). unicode-data 12.0.0 is now in unstable/testing (Buster). gucharmap FTBFS with this; It seems upstream have updated gucharmap

Bug#928888: On debian 9, /etc/init.d/hostapd shows [ ok ], when actually hostapd failed to start

Package: hostapd Version: 2.4-1+deb9u3 https://salsa.debian.org/debian/wpa/blob/debian/2%252.4-1+deb9u2/debian/hostapd.init log_daemon_msg "Starting $DESC" "$NAME" start-stop-daemon --start --oknodo --quiet --exec "$DAEMON_SBIN" \ --pidfile "$PIDFILE" --

Bug#927471: curl: Regression that fails to exhaust socket data

Hi! On Tue, 2019-05-07 at 14:57:53 +0200, Guillem Jover wrote: > Thanks! I tried yesterday and today to get a deterministic reproducer > with the version from unstable, but I'm not sure what's the trigger, > perhaps the torrent peers or the chunk arrival order or something. In > any case I was

Bug#928887: hello: version skew: 2.10-1+deb9u1 (stretch-security) > 2.10-1 (buster)

On Sun, May 12, 2019 at 04:30:01PM +0200, Andreas Beckmann wrote: > Package: hello > Version: 2.10-1 > Severity: serious > Tags: sid buster > User: debian...@lists.debian.org > Usertags: piuparts > > Hi, > > during a test with piuparts I noticed your package violates version > ordering: > >

Bug#928657: ITP: golang-github-naegelejd-go-acl -- Golang POSIX 1e ACL bindings

Hey, I've done everything with dh-make-golang already. Only the latest `gbp push` returns error by insufficient permissions. пт, 10 мая 2019 г. в 14:19, Shengjing Zhu : > Hi > > On Fri, May 10, 2019 at 4:06 PM Felixoid wrote: > > > > + submit, debian-devel, debian-go > > sub...@bugs.debian.org

Bug#928887: hello: version skew: 2.10-1+deb9u1 (stretch-security) > 2.10-1 (buster)

Package: hello Version: 2.10-1 Severity: serious Tags: sid buster User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package violates version ordering: hello | 2.10-1| stretch | source hello | 2.10-1| buster

Bug#926681: unblock: acme-tiny/1:4.0.4-1

Hello Niels, Sorry for the delay on this. > No worries, I know you've been doing lots of work during the freeze, and I noticed that you also proactively unblocked some of my packages, thanks for that. > Please go ahead with the upload and remove the moreinfo tag once it is > in unstable and

Bug#928886: iwgetid: document exit codes in man page

Package: wireless-tools Version: 30~pre9-12+b1 Severity: minor Dear Maintainer, please document the Exit Codes of iwgetid. For example, if the wireless network is not connected then iwgetid returns the exit code 255: # sudo iwgetid -r # echo $? 255 Are there more? Thank you for maintainting

Bug#921694: mdk4 (0~git20181205-2) is not suitable for Buster

Control: severity -1 serious Thank you for your work Santiago, I appreciate all of the bug reports I've received from you so far. I'm taking the opportunity of this bugreport to bump the severity and block mdk4 from entering Buster, as the current version in Testing is a git snapshot not

Bug#928885: FTBFS with librsync 2

Package: src:rdiff-backup Version: 1.2.8-7 Severity: normal Tags: upstream We plan upgrading librsync to 2.0.2 after the buster release, see #776246. This version is not API-compatible with 0.9.7 but it seems the only package that breaks is rdiff-backup: x86_64-linux-gnu-gcc -pthread -DNDEBUG -g

Bug#928884: avr-evtd FTCBFS: uses the build architecture compiler

Source: avr-evtd Version: 1.7.7-2 Tags: patch User: helm...@debian.org Usertags: rebootstrap avr-evtd fails to cross build from source, because debian/rules uses the build architecture compiler as a make default. Letting dpkg's buildtools.mk initialize $(CC) fixes that. Please consider applying

Bug#928014: binNMU: rebuild wine-development against unicode-data 12.1.0~pre1-2

control: retitle -1 binNMU: please rebuild wine-development against unicode-data 12.1.0~pre1-2 control: reassign -1 release.debian.org Hi, On 11.05.19 20:25, Paul Gevers wrote: > Hi Jens, > > On 09-05-2019 22:54, Jens Reyer wrote: > > [...] > >> The files built with unicode-data are in

Bug#928386: syslinux: possible regression bug 'Undef symbol FAIL: memset'

On Sun, May 12, 2019 at 01:10:47PM +0200, Lukas Schwaighofer wrote: > I've confirmed the issue is fixed in backports version > 3:6.04~git20190206.bf6db5b4+dfsg1-1~bpo9+2. Looks like the "Closes:" > mechanism is not available for backports, so closing manually thank you for both, Lukas! > (also

Bug#928822: raqm: clean after build deletes docs/html/* which is not regenerated

On 2019-05-12 04:38, أحمد المحمودي wrote: > I checked the diff between upstream sources 0.5.0 (the one in testing) & > 0.6.0, and I don't see any significant difference in Makefiles or docs/ > to cause this. It might something in experimental's toolchain ? This is probably reproducible in sid

Bug#915333: git-annex: Illegal Instruction on armel (Fujitsu Q700 like QNAP TS-21x/TS-22x)

On Mon, Mar 11, 2019 at 12:05PM, Adrian Bunk wrote: > On Thu, Jan 31, 2019 at 08:12:17PM +0100, Bernhard Übelacker wrote: > > See attached file with several debugging attempts. > > Looking at the code, the bug seems to be in >

Bug#928883: libzorpll-dev: add Breaks

Package: libzorpll-dev Version: 7.0.1.0~alpha1-1 Severity: serious Tags: patch User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'stretch' in some scenarios, and the old version from stretch is kept installed. This is

Bug#928809: lintian: suggest adding gitlab-ci file

Hi, On Sat, May 11, 2019 at 02:49:02PM +, Dmitry Bogatov wrote: > please add suggestion that if Vcs-Git points to salsa.debian.org, > CI should be used. Please, don't. For most of my packages, I don't want to bother with setting up a CI, neither I see any use for it, and I don't think

  1   2   >