[2019-11-29 09:49] Aurelien Jarno
> On 2019-11-28 22:04, Debian FTP Masters wrote:
> > sysvinit-core_2.96-2_amd64.deb: has 2 file(s) with a timestamp too far in
> > the past:
> > usr/share/doc/sysvinit-core/copyright (Thu Jan 1 00:00:01 1970)
> > usr/share/doc/sysvinit-c
>
control: tags -1 +confirmed
[2019-11-25 12:06] Jan Braun
> Dear Maintainer,
>
> The /lib/init/init-d-script errorneously returns failure when asked to
> stop a non-running service:
> [...]
>
> And indeed, one call to start-stop-daemon in /lib/init/init-d-script is
> missing the --oknodo flag.
[2019-11-10 02:31] Santiago Vila
> > I am losing context. We have at least following three files (oh, why all
> > this madness?):
> >
> > * /usr/lib/os-release
> > * /etc/os-release
> > * /etc/debian_version
> >
> > So, in case of conflicts, what should override what?
>
> Please note that
control: tags -1 +help
[2019-11-08 13:42] Santiago Vila
> Hi.
>
> I've asked the Release Managers about this here:
>
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944351
>
> If they say yes, I'll modify base-files accordingly (for Debian 10.2).
>
> If they say no, please be ready to fix
Control: tag -1 pending
Hello,
Bug #941273 in runit reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
control: severity -1 +normal
[2019-09-10 10:21] Jonathan Wiltshire
> >> The x.y there was a remnant from Debian sarge times.
> >
> > Up until squeeze I have seen it show x.y.z, then from wheezy to
> > stretch I see only x.y, but it does seem new behaviour in buster to
> > only show x.
> >
>
[2019-09-08 17:53] Jean-Marc LACROIX
> > Please:
> >
> > * Try installing something else, like `tor'. I expect you will get
> > similar error (`tor' depends on libsystemd0, sigh)
>
> ansible@pinebook:~$ sudo apt install tor
> [...]
Okay, tor installs fine with your apt-pinning. My
control: tags -1 +moreinfo
[2019-08-30 16:44] Jean-Marc LACROIX
> Package: sysvinit
> Version: 2.93-8
> Severity: grave
>
> Dear maintainers,
>
> It seems there is a dependency issue when installing sysvinit-core as
> indicated in following trace
> [...]
> Package: *systemd*
> Pin: release *
control: tags -1 +confirmed
[2019-07-17 07:41] Helmut Grohne
> part text/plain1094
> Control: reopen -1
> Control: affects -1 + src:dropbear
>
> On Tue, Jul 16, 2019 at 08:42:09PM +, Debian Bug Tracking System wrote:
> >* dh_installinit: Fix regression where
[2019-07-17 19:24] Felix Lechner
> Hi,
>
> Updating from version 12.1.1 in testing to 12.2.2 breaks the build
> process for test packages in Lintian. The unstable pipelines on
> jenkins and Gitlab are failing.
>
> The command 't/bin/build-test-packages' in Lintian runs for a while
> but then
; >
> > Helmut
> >
>
> Hi Dmitry,
>
> This report seems to be a regression related to your patch from #462389.
Definitely regression.
From a7288f30a003759b186389b93d336bef90491062 Mon Sep 17 00:00:00 2001
From: Dmitry Bogatov
Date: Mon, 15 Jul 2019 16:08:01 +
Subject: [PATCH]
control: severity -1 minor
[2019-05-29 13:31] lkcl
> Package: libgdbm6
> Version: 1.18.1-4
> Severity: serious
> Justification: 2
>
> Unpacking libgdbm-dev:amd64 (1.18.1-4) ...
> dpkg: error processing archive
> /var/cache/apt/archives/libgdbm-dev_1.18.1-4_amd64.deb (--unpack):
> trying to
Control: tag -1 pending
Hello,
Bug #927442 in runit reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Control: tag -1 pending
Hello,
Bug #927442 in runit reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
[2019-03-16 00:41] Lorenzo Puliti
> >Bogatov wrote:
> >Dear git maintainer, you could plug this bug by adding
> >`/var/lib/supervise/git-daemon' into `debian/git-daemon-run.dirs'.
>
> Dmitry, are you sure? runsv can create the 'git-daemon' directory if
> it's not there, and a dangling symlink
[2019-03-11 17:55] Helmut Grohne
> directfb has build failures. A cross build for armel fails:
>
> | mknod( C64X_DEVICE, 0666 | S_IFCHR, makedev( 400, 0 ) );
I encountered similar error on one of my packages recently (can't
remember which one). It was due upgrade to glibc-2.28 and
[2019-03-11 21:51] Axel Beckert
> > I believe it would be reasonable to add '--name $base' into `else'
> > clause. Opinions?
>
> Sounds sane, I just checked that with #924311 (miredo, uses
> start-stop-daemon directly, edited the init script) as well as #924312
> (stunnel4, by editing
control: tags -1 +moreinfo
[2019-02-06 20:20] Andreas Metzler
> Package: lsb-base
> Version: 10.2018112800
> Severity: serious
>
> Hello,
>
> there is a logic error in /lib/lsb/init-functions's killproc:
>
> base=${1##*/}
> if [ ! $pidfile ]; then
> name_param="--name $base
[2019-03-08 22:40] Niko Tyni
> On Fri, Mar 08, 2019 at 02:39:53PM +0000, Dmitry Bogatov wrote:
>
> > I believe this patch would somewhat solve issue. Dear submitter, can you
> > please apply this patch, build package and check, that `gdbm_load-nolfs'
> > binary from c
control: severity -1 important
[2019-03-07 17:21] Andras Korn
> The supplied "/etc/runit/1" calls "/lib/runit/run_sysv_scripts /etc/rcS.d"
> during boot.
>
> /lib/runit/run_sysv_scripts runs under "sh -eu", which has the effect that
> if any initscript exits unsuccesfully, all subsequent
dbbe906795dd977ed16cccaa7b0385ce8654c8a5 Mon Sep 17 00:00:00 2001
From: Dmitry Bogatov
Date: Thu, 7 Mar 2019 20:19:11 +
Subject: [PATCH] Provide version with LFS support disabled
---
debian/rules | 4
1 file changed, 4 insertions(+)
diff --git a/debian/rules b/debian/rules
index fce1572..03b6242 100755
[2019-03-05 17:44] Sergey Poznyakoff
> Hello,
>
> Investigation of the attached file has shown that it has been created
> by gdbm 1.8.3 compiled without large file support (sizeof(off_t) == 4).
> In contrast, gdbm 1.18.1 was compiled with large file support enabled,
> which naturally lead to
control: tags -1 +upstream +forwarded
Hello!
Can you please take a look at this Debian bug report [1]. It seems that
compatibility issues we discussed before and which were believed to
resolved in release 1.18.1 actually still present.
Reporter kindly provided receipe to reproduce issue and
`
[2019-02-28 18:01] Niko Tyni
> > > But ideally gdbm would restore compatibility and libmarc-charset-perl
> > > would
> > > not need any changes.
> >
> > I believe upstream release 1.8.1 introduced change, that
> > made it possible to read old /usr/lib/libmarc-charset-perl/Table. Am I
> >
[2019-02-27 21:20] Niko Tyni
> > - update perl to build-depend on libgdbm-dev (>= 1.18-2) and Break
> > older versions of libmarc-charset-perl (and any other perl packages
> > bundling GDBM or NDBM databases)
> >
> > - update libmarc-charset-perl (and any other perl packages bundling
> >
[2018-12-19 23:40] Dmitry Bogatov
>
> part text/plain 459
>
> control: tags -1 +moreinfo
>
> [2018-12-18 12:10] shirish शिरीष
> >
> > Dear all,
> >
> > At least here it updated without any issues -
> >
> > $ sudo
Since 1.18.0-1 (1.18.0-2 in unstable) debian packaging patch-out
integration with systemd, thus closing this bug.
Dear submitter, if you can somehow reproduce this bug with current
version of insserv, feel free to reopen this bug.
--
Note, that I send and fetch email in batch, once
[2019-01-23 12:41] Jonathan Nieder
> Dmitry Bogatov wrote:
> >> Jonathan Nieder wrote:
>
> >>> + * git-daemon-run: pre-create supervise directory so that postinst
> >>> +can start the service (thx Celejar and Dmitry Bogatov; closes:
> >>&g
[2019-01-23 12:41] Jonathan Nieder
> [...]
> > It is my fault. I dropped /var/lib/supervise directory in runit=2.1.2-4,
> > which was expected by git-daemon-run.
> >
> > Today runit packaging underwent quite a rework, and packages, providing
> > runscripts are encouraged to use dh_runit(1). It
[2019-01-21 19:54] Jonathan Nieder
> Dmitry Bogatov wrote:
> > [2019-01-16 14:49] Dmitry Bogatov
>
> >> So, should I propose you patch (in 7 days), that merges
> >> bin:git-daemon-run into bin:git-daemon, would you be able to review
> >> and apply/upload
[2019-01-21 20:03] Jonathan Nieder
> Jonathan Nieder wrote:
> > + * git-daemon-run: pre-create supervise directory so that postinst
> > +can start the service (thx Celejar and Dmitry Bogatov; closes:
> > +#919296).
> > [...]
>
> Unfortunately, this does
[2019-01-16 14:49] Dmitry Bogatov
> So, should I propose you patch (in 7 days), that merges
> bin:git-daemon-run into bin:git-daemon, would you be able to review
> and apply/upload it before hard freeze?
Probably, even better would be to merge `git-daemon-run' and
`git-daemon-sysvin
Hello?
Dear maintainer of ncurses, could you please upload a backport of
ncurses-term?
pgpLomqpgPKeE.pgp
Description: PGP signature
control: tags -1 +confirmed
[2019-01-14 19:56] Celejar
> ~# dpkg-reconfigure git-daemon-run
> Service git-daemon already added.
> warning: git-daemon: unable to open supervise/ok: file does not exist
>
> > If I'm lucky then that will get it working. I'll try to reproduce it
> > here and set
Package: gitlint
Version: 0.9.0-2
Severity: serious
Justification: FTBFS
Dear Maintainer,
gitlint fails to build from source -- it have 3 test cases failing. As I
discovered when trying to prepare NMU for #891538, these tests also fail
with gitlint-0.10, so I add upstream maintainer to thread.
control: tags -1 +moreinfo
[2018-12-18 12:10] shirish शिरीष
>
> Dear all,
>
> At least here it updated without any issues -
>
> $ sudo aptitude install insserv -y
> The following packages will be upgraded:
> insserv
> [...]
Thank you for help with bug triage, shirish.
Dear submitter, can
[2018-10-21 10:44] Andreas Beckmann
> Package: dvtm
> Version: 0.15-3~bpo9+1
> Severity: serious
> User: debian...@lists.debian.org
> Usertags: piuparts
> during a test with piuparts I noticed your package is not
> installable in stretch-backports:
> ncurses-term | 6.0+20161126-1+deb9u2 |
[2018-10-15 20:18] Niko Tyni
> > I am sorry to say it, but probably binNMU or sourceful upload would
> > be required for all packages, that bundle gdbm databases, generated
> > by (gdbm << 1.9)
>
> This sounds really sad. So even the gdbm we have in our current stable
> release is too old to
[2018-10-13 13:20] Niko Tyni
> The libgdbm6 transition broke autopkgtest checks of src:perl and
> libmarc-charset-perl.
>
> It looks like some GDBM databases which were working with the older
> gdbm are not readable any more with the new one.
After a bit more research I deduced, that
control: tag -1 +moreinfo
[2018-10-13 13:20] Niko Tyni
> For reference, the output with libgdbm5 1.14.1-6+b1 is
>
> % gdbm_dump debian/tests/data/jessie.gdbm
> # GDBM dump file created by GDBM version 1.14.1. 03/01/2018 on Sat Oct 13
> 13:15:59 201
> 8
> #:version=1.0
>
control: tag -1 confirmed
[2018-10-13 13:20] Niko Tyni
>
> part text/plain1170
> Package: libgdbm6
> Version: 1.18-2
> Severity: grave
> X-Debbugs-Cc: p...@packages.debian.org,
> libmarc-charset-p...@packages.debian.org
>
> The libgdbm6 transition broke autopkgtest
+++ courier-authlib-0.68.0/debian/changelog 2018-10-10 16:35:27.0
+
@@ -1,3 +1,11 @@
+courier-authlib (0.68.0-4.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Relax checks for C++ symbols (Closes: #897725)
+ * Update Vcs-* fields in debian/control
+
+ -- Dmitry Bogatov
control: close -1
[2016-09-07 22:56] Dmitry Bogatov <kact...@gnu.org>
> control: tags -1 +fixed-in-experimental
>
> > >From the attached log (scroll to the bottom...):
> >
> > Removing getty-run (2.1.2-6) ...
> > warning: getty-tty6: unable to
[2016-12-13 11:02] Sean Whitton <spwhit...@spwhitton.name>
> On Wed, Dec 07, 2016 at 09:34:13AM +0300, Dmitry Bogatov wrote:
> > I switched to emacs25 already (since this bug report). So far, no
> > changes.
> >
> > > - Could you fix #829299 based on th
> > > I don't see the related changes there, nor attribution (or NACK) for the
> > > patch...
> >
> > I read you patch email *after* I wrote almost same patch myself and
> > made RFS. Are there any attribution issues?
>
> Oh, no attribution issues whatsoever, more of a friendly thing. Always
> Did you forget to push this to:
>
> https://anonscm.debian.org/cgit/users/kaction-guest/dh-haskell.git
No. Now dh-haskell is under umbrella of DHG. Look here:
https://anonscm.debian.org/cgit/pkg-haskell/dh-haskell.git
> I don't see the related changes there, nor attribution (or
control: tags -1 +fixed-in-experimental
> >From the attached log (scroll to the bottom...):
>
> Removing getty-run (2.1.2-6) ...
> warning: getty-tty6: unable to open supervise/ok: file does not exist
> dpkg: error processing package getty-run (--remove):
>subprocess installed
> during a test with piuparts I noticed your package fails to remove.
>
> >From the attached log (scroll to the bottom...):
>
> Removing getty-run (2.1.2-6) ...
> warning: getty-tty6: unable to open supervise/ok: file does not exist
> dpkg: error processing package getty-run (--remove):
>
> My (dist-)upgrade attempt failed this morning with the same exact problem :
>
> -
> root@SAP5057241:~# apt-get dist-upgrade -u -f
> Lecture des listes de paquets... Fait
> Construction de l'arbre des dépendances
> Lecture des
control: tags -1 +moreinfo
Jan, could you please provide more information? I did not follow. As
I understand, there was some problem with mongrel2-run, but, as
mongrel2/1.11.0-1 it is no longer case (and I can confirm it, just
installed mongrel2-run without any problems), but this bug is still
> I'm not sure, but did you mean to report this bug against bcron package?
> I fail to understand why runit should have such problem
Well, it is my bad. runit-2.1.2_4 deserved a transition, but now we have at
least following
uninstallabe packages:
bcron-run
twoftpd-run
tinydns-run
Package: nis
Version: 3.17-34
Severity: serious
Justification: fails to build from source (but built successfully in the past)
Dear Maintainer,
Package no longer builds from source in up-to-date sid
environment. Build log attached.
-- System Information:
Debian Release: 8.5
APT prefers stable
* Gianfranco Costamagna costamagnagianfra...@yahoo.it [2015-08-08
07:35:10+]
Hi Dmitry,
I propose this solution:
remove all the Debian patches (actually the python3 patch seems correctly
handled by 2to3 at build time)
add a new patch to disable the only test actually requiring an
Just a few problems, seems that you didn't start from the last upload
you need to start with -3 release with the changes, because otherwise it
messes up things
(e.g.
[...]
Nice catch, thanks. Get fixed -4 release from my unstable.
--
Accept: text/plain, text/x-diff
Accept-Language:
* Gianfranco Costamagna costamagnagianfra...@yahoo.it [2015-08-08
11:22:51+]
Nice catch, thanks. Get fixed -4 release from my unstable.
Just a little nitpick, please add a Description for the patch, to make
lintian silent.
Added.
if this is ok for you, just ack and I'll upload :)
(no
Try this:
cd ~kaction-guest/repository/unstable
Seems mini-dinstall does not allow others view incoming/ queque. Sorry.
--
Accept: text/plain, text/x-diff
Accept-Language: eo,en,ru
X-Keep-In-CC: yes
pgpcOmF5G194e.pgp
Description: PGP signature
* Gianfranco Costamagna costamagnagianfra...@yahoo.it [2015-08-06
08:59:21+]
Okay. mentors gives me 500 error, probably it dislikes Tor. I will
investigate, but now to keep things fast you can
git clone git://anonscm.debian.org/users/kaction-guest/pygithub.git
and NMU it. Also, I
* Gianfranco Costamagna costamagnagianfra...@yahoo.it [2015-08-05
15:15:00+]
Control: forwarded -1 https://github.com/PyGithub/PyGithub/issues/331
Hi Dmitry, I guess the package is really not python3 ready, in my opinion
we should at least let the python2 version migrate to testing,
58 matches
Mail list logo
