tags 956083 + patch,pending
thanks
Hello Tina!
I have prepared a _very_ simple patch for this issue that lacks
elegance, but I think solves the problem: As it is invoked before the
data rotation, it will notify via stderr and exit before destroying
past data:
diff --git a/autopostgresqlbackup
I can confirm this is the case, and that this bug has lingered without
a reply for two years and a half already :-(
The log flooding happens only when virt-manager is open (because it
keeps polling several files for displaying the guests' status). The
messages also appear when querying for
Gunnar Wolf dijo [Wed, Feb 17, 2021 at 12:45:05PM -0600]:
> ===BEGIN
>
> The Technical Committee recommends that Christoph Berg be
> appointed by the Debian Project Leader to the Technical Committee.
>
> A: Recommend to appoint Christoph Berg
> B: Further Discussion
>
Package: tech-ctte
Severity: normal
Given that Philip Hands' term in the Technical Committee finished in
December, I want first of all to thank him on behalf ot the rest of
the Committee members for his good work during the term, and call for
votes to accept a new TC member.
So, voting will
tags 982354 + confirmed,pending
thanks
> Documentation build dies when 'lmodern.sty' is missing. Installing
> package 'lmodern' fixes that.
>
> (P.S: sorry for not using reportbug: after going once through the
> whole questionnaire it ate the file. I didn't feel like doing all
> this again)
Package: wnpp
Severity: normal
Mp3roaster is a very easy to use and well thought out program to
record compressed audio files in audio CD format. I maintained it for
some time, but it didn't require any maintenance for a long
time... Then it fell out of my radar :-(
Nowadays, I don't own a CD
Gunnar Wolf dijo [Sun, Jan 31, 2021 at 03:32:02PM -0600]:
> My vote is:
>
> Y > F > N
...And to be clear: We at the TC are *not* doing detailed design
work. But I want to state (and not as part of the vote, but just as
yet another DD) that the only way I feel makes sense to cont
Sean Whitton dijo [Mon, Jan 25, 2021 at 11:45:55AM -0700]:
> ===BEGIN
> The Technical Committee resolves that Debian 'bookworm' should support
> only the merged-usr root filesystem layout, dropping support for the
> non-merged-usr layout.
>
> Until after the release of 'bullseye', any
tags 979977 + confirmed
thanks
Ummh, interesting...
Latest kernel and initrd are found by the following simplistic,
lexicographic logic:
latest_kernel=$(ls -1 /boot/vmlinuz-* | grep -v '\.dpkg-bak$' | sort -V -r
| head -1)
if [ -z "$latest_kernel" ]; then
echo "raspi-firmware: no
Sandro Tosi dijo [Tue, Jan 26, 2021 at 08:47:22PM -0500]:
> the ability to talk privately with the committee is something CTTE has
> allowed for a long time; it's a two-sided coin: it can prevent heated
> exchanges, but it can also leave a sour taste in the petitioner's
> mouth.
>
> While i would
Wouter Verhelst dijo [Tue, Jan 26, 2021 at 01:17:38PM +0200]:
> On Tue, Jan 26, 2021 at 12:28:45AM +0100, Marco d'Itri wrote:
> > Also, as is has been discussed, if the /usr/doc/ transition was
> > representative then this would probably take many years.
>
> You keep using that as an argument. I
Christian Kastner dijo [Tue, Jan 19, 2021 at 09:55:19AM +0100]:
> > We are considering NMU of vmdb 0.22. The Salsa repo. is at
> > https://salsa.debian.org/ckk/vmdb2
>
> Given that a new upstream version usually does not fit the profile of an
> NMU: just to be clear, the vmdb2 Maintainer
Matthew Vernon dijo [Mon, Jan 11, 2021 at 09:07:03PM +]:
> > If you intend the scope of this bug to involve overruling maintainers'
> > decisions in packages other than NM, what other packages/bugs did you
> > have in mind? Is it just udisks2/#923387, or are there more?
>
> I understand (but
tags 969287 + moreinfo,help
thanks
Hello,
I am sorry for not answering to this bug report sooner; I cannot test
to reproduce what you say (I have only one MicroHDMI cable), and even
if I could, I really don't think I can do much to help. Your bug
report has a lot of interesting insight, but I
tags 962038 + wontfix
thanks
Hello Bastian,
Thinking about this bug, I have decided to tag it "wontfix".
Of course, it does not mean it should not be fixed by alternate means
-- But I don't want to require following different sources for this
package. My aim with raspi-firmware is to allow a
tags 971884 + unreproducible
thanks
Hello,
Going over our list of pending bugs, I found this report pending
action. Please confirm whether you consider this bug to be present
(and explain it further, as I requested in my November 19 reply!), or
confirm this bug can be closed now.
Thanks!
Hello world,
As you have guessed by now, I have been unable to follow on this bug
report. As the Debian vmdb2 maintainer, I am ashamed of not even
answering... :-( Anyway, I'm happy to see that Lars, upstream author,
is part of the discussion, and there are other DDs involved.
As I said in
Please explain further as to what you mean; what do you mean by using
dpkg-reconfigure to configure something?
I can confirm to you that, when I change any values in
/etc/default/raspi*, 'dpkg-reconfigure raspi-firmware' enacts the
changes (that is, regenerates the relevant /boot/firmware/
Hello world,
When we had our last tech-ctte meeting, 2020.10.21¹, I volunteered to
write up a summary of our positions regarding this bug. Then... Well,
life happened, and I have not had the time to sit down and write until
today -- A couple of hours before our next meeting. Several other
Hello Lars,
I am writing to you regarding the bug report I am Cc:ing here. Please
help me correctly answer to this! The submitter says, in the initial
mail:
> I am trying to let autopkgtest-build-qemu work on arm64.
> See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973038
> for relevant
tags 973467 - patch
tags 973467 + confirmed upstream
severity 973467 important
thanks
Hello Ryutaroh,
As you said here, the workaround is not a fix, as it would make vmdb2
produce images unable to boot on amd64 - So I'm removing the "patch"
tag. I am also adding the tags "confirmed" and
tags 971882 + pending,confirmed
thanks
I have committed the fix for this bug (commit fec0d03). As I mentioned
on the other bug you reported (thanks!), I will upload this (and, if I
get the time for testing, will do an update to the newer upstream
release) after the package hits Backports.
tags 971748 + confirmed,pending
thanks
Hello,
I am sorry for the ~3 weeks that have passed since you reported this
bug. I do intend on fixing it in my next upload, and I do intend that
upload to happen soon; I have been quite busy, but am working on the
package now.
Before uploading a new
Sudip Mukherjee dijo [Fri, Oct 23, 2020 at 06:25:26PM +0100]:
> Package: wnpp
> Severity: wishlist
> Owner: Sudip Mukherjee
>
> * Package name: rfc6555
> Version :
> Upstream Author : Seth Michael Larson
> * URL : https://github.com/sethmlarson/rfc6555
> (...)
> The
Hayley Hughes dijo [Thu, Oct 22, 2020 at 09:31:30PM +1100]:
> * Package name : toolbox
> (...)
> Toolbox is a tool that offers a familiar package based environment for
> developing and debugging software that runs fully unprivileged using Podman.
>
> The toolbox environment is based on an OCI
Michael Biebl dijo [Wed, Oct 07, 2020 at 09:53:06PM +0200]:
> Forwarding this to the CTTE, just in case they have some input on this
> proposed plan.
> (...)
> A small update here:
> v246 provides a build switch -Dstandalone-binaries=true:
> (...)
> Atm, those supported binaries are
Hi,
Just a heads-up: git-hub v2.x.x has been ported to Python3, around one
month ago. Please update the package!
https://github.com/sociomantic-tsunami/git-hub/blob/v2.x.x/relnotes/python3-migration.md
Thanks,
signature.asc
Description: PGP signature
David Prévot dijo [Wed, Sep 23, 2020 at 10:49:33AM -0400]:
> > And we would have everything in place to notify people whose key is
> > to expire soon.
>
> Wonderful, thank you for working into making (part of) our lives easier!
:-]
I will add this, but not to this script (thinking during
Let me think out loud to this bug report...
Jonas Smedegaard dijo [Wed, Sep 23, 2020 at 08:43:03AM +0200]:
> I would certainly appreciate Debian running this kind of service.
>
> From a recipient PoV I would find it most sensible to receive such
> notification from the keyring maintainers, but
Philip Rinn dijo [Thu, Sep 10, 2020 at 12:09:29PM +0200]:
> Hi Gunnar,
>
> thanks for testing - but your message leaves me a little confused. You claim,
> the
> bug is fixed but you say
>
> > we have used only regular linux-image-armmp kernels (and have no
> > reason to suppose -lpae is
fixed 820622 4.19.132-1
thanks
Hello,
I have not seen this message appear in my RPi2, using stock Debian
kernels starting at 4.19 (even a bit before that, I think). I do not
use the LPAE kernel, as I understand it does not make much sense in
the RPi2 (sold only with 1GB RAM, and not expandable),
fixed 941597 5.7.17-1
thanks
I have some RPi3B+ using the arm64 Linuxkernel at version 5.7
(currently in testing), and they both shutdown and reboot reliably. I
believe this bug can now be closed.
signature.asc
Description: PGP signature
fixed 878332 4.19.132-1
fixed 878332 5.7.17-1
thanks
Hello,
This bug is no longer present in kernels shipped in Debian stable /
testing / unstable. Do note, though, that the Raspberry Pi 2 is sold
with 1GB RAM only and cannot be upgraded, and thus has no use for
LPAE, we have used only regular
tags 958606 + patch
thanks
The patch for this, given bitlbee already depends on debhelper, is
straightforward; I am inlining it here:
--- a/debian/control
+++ b/debian/control
@@ -4,7 +4,7 @@ Priority: optional
Maintainer: Wilmer van der Gaast
Uploaders: Jelmer Vernooij
Standards-Version:
tags 958606 + ftbfs pending
tags 942954 + ftbfs pending
thanks
I will be NMUing in some minutes bitlbee to the 3-day delayed queue
due to the two mentioned bugs, as they cause the package to FTBFS (and
are quite trivial to fix).
The patch for 942954 was sent several months ago by Matthias Klose;
he php-fpm
maintainers to work constructively to find a suitable way to describe
the needed dependencies so that php-fpm can be installed in a
containerized system without a full init system.
For fullness of references, the bug report tracking the conflict
between the systemctl and php-fpm packages i
Hello world,
Dmitry Smirnov Tue, 14 Jul 2020 18:04:45 +1000:
> Not yet, unfortunately. Sorry for inconvenience. I'm going to seek
> CTTE advise on #959174...
I am joining the conversation as an individual (so I'm not wearing any
tech-ctte hat yet), prompted by this. Do note that this has _not
tags 4964915 + confirmed
notfound 4964915 1.20190215-1+deb10u4
severity 4964915 critical
thanks
I am bumping up this bug to critical, as it «makes unrelated software
on the system (or the whole system) break» - Rendering a computer
unbootable is a critical bug in my book!
This bug does not
[ Adding a Cc: to #964915 ]
Lucas Nussbaum dijo [Fri, Jul 31, 2020 at 02:15:29PM +0200]:
> Hi,
>
> Can you confirm that it's not
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964915
Yes, that's precisely the culprit.
Even more - Both basti and me didn't find it any further because (I
Package: wnpp
Severity: normal
I intend to orphan the mp3roaster package. This package has not had
any activity since 2012, and eight years later... I don't even own a
device capable of writing music CDs.
The package works quite fine, although it's about to get kicked out of
testing unless
;
> The chair of the Debian Technical Committee will be:
>
> A : Philip Hands
> B : Margarita Manterola
> C : David Bremner
> D : Niko Tyni
> E : Gunnar Wolf
> F : Simon McVittie
> G : Sean Whitton
> H : Elana Hashman
>
> ===END===
My vote is:
B > A = C = D = E = F > G = H
signature.asc
Description: PGP signature
tags 961377 + pending
thanks
I have uploaded the fix and mailed the Stable Release Managers, this
should be fixed soon.
Thanks!
Package: release.debian.org
Severity: normal
Tags: buster
User: release.debian@packages.debian.org
Usertags: pu
Back in March, I uploaded to Buster version 1.20190215-1+deb10u3 of
raspi3-firmware, stating it fixed "unbootableness" on several
systems. I assumed it was all done, and went on
Thorsten Glaser dijo [Fri, Jul 03, 2020 at 04:28:37PM +]:
> Gunnar Wolf, Sun, 24 May 2020 16:03:04 -0500:
>
> >I will try to build+test+upload this in the next couple of days.
>
> $ rmadison -u qa raspi3-firmware
> raspi3-firmware | 1.20161123-2 | stretch/non-
Pirate Praveen dijo [Fri, Jun 19, 2020 at 12:47:51PM +0530]:
> The general case was discussed earlier and a recommendation was given at
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934948#54
>
> I'd like a confirmation from you if katex was following your
> recommendations or not. I think
tags 962808 + confirmed,upstream
thanks
Hi,
I have asked upstream about this issue, and he mentions it's a know
issue in his tracker:
https://gitlab.com/larswirzenius/vmdb2/-/issues/13
Sadly, he does not know why this breaks, and says is lacking time to
look into it right away (and so I
Florian La Roche dijo [Sun, Jun 14, 2020 at 02:26:17PM +0200]:
> creating one big LVM partition without encryption and then using grub to
> boot up does not seem to have a valid configuration.
>
> With vmdb2 0.14.1 I couldn't find any way to reference the device grub
> is getting installed on. It
Florian La Roche dijo [Sun, Jun 14, 2020 at 02:29:50PM +0200]:
> it would be good to add configuration possibiities to toggle a partition
> bootable within the config file. I am right now changing the image after
> creating it with vmdb2, code within vmdb2 would keep the whole setup in
> one
close 962396
thanks
Bálint Réczey dijo [Sun, Jun 07, 2020 at 02:56:17PM +0200]:
> Please update the keyring. Thank you.
> The last update took place ~2 months ago and a new one would be due, I
> think. I'm looking forward to being able to upload to the archive
> again. :-)
Updates take place on
tags 961377 + confirmed,pending
thanks
Thorsten Glaser dijo [Sat, May 23, 2020 at 08:55:01PM +0200]:
> Package: raspi3-firmware
> Version: 1.20190215-1+deb10u3
> Severity: critical
> Tags: patch buster
> Justification: breaks the whole system
>
> /etc/kernel/postinst.d/z50-raspi3-firmware in
David Bremner dijo [Wed, May 20, 2020 at 05:03:16PM -0300]:
> ===BEGIN
> The Technical Committee recommends that Sean Whitton be
> appointed by the Debian Project Leader to the Technical Committee.
>
> S: Recommend to Appoint Sean Whitton
> F: Further Discussion
> ===END
I am happy to vote:
David Bremner dijo [Wed, May 20, 2020 at 05:10:26PM -0300]:
> ===BEGIN
> The Technical Committee recommends that Elana Hashman be
> appointed by the Debian Project Leader to the Technical Committee.
>
> S: Recommend to Appoint Elana Hashman
> F: Further Discussion
> ===END
I am happy to vote:
Package: installation-reports
Version: 2.71
Severity: minor
The Buster installer could not find my wireless card (RTL 8821CE).
I performed the install using a spare external wireless interface; after
booting to the installed system, I found an unofficial module supporting
this hardware at:
Hi,
Just adding some info to this bug, for whoever stumbles upon it - I
just got a new HP laptop (HP Pavillion X360, 14", specific model
14-cd0004la) with this same wifi chip. I was able to install and use
the (very not official, run at your own risk!) drivers available at
Hello,
As far as I understand, the CPU in the RPi4 is a *completely*
different beast from the ones in the rest of the family. It seems it
will not require a binary firmware loader anymore!
Right now, it is not *yet* bootable using the stock Linux kernel, but
there are people working on its
Package: release.debian.org
Severity: normal
Tags: buster
User: release.debian@packages.debian.org
Usertags: pu
Several first-generation Raspberry Pi models have been unbootable, as
we managed to mess up with the names of the firmware. The patch I am
suggesting as version 1.20190215-1+deb10u3
Package: telegram-purple
Version: 1.4.1-1+b1
Severity: important
After several months of using telegram-purple (thanks for it!) via
bitlbee, I started receiving the following message in thelog, with
frequencies that go from every ten seconds to every ten minutes:
10:33:27 @root | purple -
Svante Signell dijo [Wed, Jan 29, 2020 at 08:15:36PM +0100]:
> > It's not like having two competing implementations causes much
> > harm here.we technically _can_ allow any /bin/systemd-* to be
> > provided by another implementation, that we should (actually, I think
> > we should clearly _not_).
I just want to subscribe with a very big +1 to what OdyX has said here:
Didier 'OdyX' Raboud dijo [Wed, Jan 29, 2020 at 04:31:09PM +0100]:
> (...)
> > So I am in the opinion that "as long as it's properly hooked in the
> > packaging system and boot sequence" simply doesn't work in this case, as
>
Thomas Goirand dijo [Wed, Jan 29, 2020 at 04:07:21PM +0100]:
> This reasoning can make sense, if we agree that we should use something
> else than /bin/systemd-sysusers and standardize on something else like
> /bin/sysusers. Then we modify the Debian policy that /bin/sysusers is
> *the* way to do
tags 928485 + patch,pending
thanks
I have submitted a patch upstream fixing this issue. Merge request
available at:
https://gitlab.com/larswirzenius/vmdb2/merge_requests/4
FWIW, the changes are basically trivial, so I'm inlining them here as
well:
diff --git a/vmdb/app.py b/vmdb/app.py
Lars Wirzenius dijo [Thu, Nov 28, 2019 at 11:27:54AM +0200]:
> Thanks, I've applied the changes and pushed them to git.liw.fi and
> gitlab.
Thanks for your prompt attention, Lars!
I am about to board a plane, but will try to work on this bug later
today. Lars, do you want to tag a release? Or
tags 922709 + confirmed,pending
thanks
I can confirm this issue has been fixed in Lars' repository, and will
be uploaded when a new version is released.
Package: ftp.debian.org
Severity: normal
Pcredz uses python-libpcap, which is pending autoremoval and is not
available for python3 (a migration to python3-pypcap requires adapting
the code beyond what I'm willing to do).
Besides, I have only done an upload of this tool, back in 2014, and
it's
Santiago Vila dijo [Thu, Jul 25, 2019 at 01:22:42PM +0200]:
> > Or are you asking the TC for advice, or are you asking us to use a
> > different one of the TC's powers?
>
> Advice first.
OK, good this is made explicit. Thanks.
> > There are many aspects of a build environment that might be
Package: nm.debian.org
Severity: minor
I was recently talking with jmw, and told him I was surprised to get
an NM assigned as I had set myself as inactive, although I didn't
lower my number of available slots. He asked me to file a bug, because
from the FD view, he does not even see the "active"
Don Armstrong dijo [Tue, Jul 23, 2019 at 06:06:59PM -0700]:
> I think this discussion is great and good to have; thanks for starting it!
I completely concur.
> As a point of order, the TC isn't responsible for deciding whether bugs
> are RC or not. That responsibility belongs with the Release
Sean Whitton dijo [Fri, Jun 21, 2019 at 02:36:05PM +0100]:
> My reading of the conclusion to #904558 is that the recommendation to
> form a working group is a recommendation that can be directed only to
> the developer body as a whole, not to the Policy process. That's
> because actually
Hello Sean,
> In #904558 I asked the T.C. for advice about how to move #802501
> forward. Their ultimate response was to recommend that a working group
> of developers come up with some method, other than exiting nonzero, for
> a maintscript to indicate that it failed to restart services. Let
Package: drupal7
Version: 7.52-2+deb9u8
Severity: grave
Tags: security upstream
Justification: user security hole
Drupal security advisory SA-CORE-2019-007 was issued today:
https://www.drupal.org/SA-CORE-2019-007
It refers to the following advisory in a bundled third-party library:
Package: drupal7
Version: 7.52-2+deb9u7
Severity: normal
Tags: security patch upstream
FWIW, report copied over from the Drupal advisory,
https://www.drupal.org/SA-CORE-2019-006
The jQuery project released version 3.4.0, and as part of that,
disclosed a security vulnerability that affects all
Didier 'OdyX' Raboud dijo [Mon, Feb 25, 2019 at 02:58:09PM +0100]:
> === Resolution ===
>
> The Technical Committee resolves to decline to override the debootstrap
> maintainers.
>
> Furthermore, using its §6.1.5 "Offering advice" power, the Technical
> Committee considers that the desirable
tags 922660 + upstream pending
thanks
Antonio Terceiro dijo [Mon, Feb 18, 2019 at 10:40:45PM -0300]:
> Package: vmdb2
> Version: 0.13.2+git20190215-1
> Severity: normal
> Tags: patch
>
> The minimal example provided in the documentation doesn't really work.
> The attached changes it to something that does (still, you can't login
> to
Antonio Terceiro dijo [Mon, Feb 18, 2019 at 10:44:39PM -0300]:
> The vmdb2 usage changed brutally, and broke the specification file
> produced by autopkgtest-build-qemu. I don't think this can't really be
> fixed in vmdb2 at this point, not only because this makes the
> specification format a lot
Didier 'OdyX' Raboud dijo [Sat, Feb 02, 2019 at 03:38:01PM +0100]:
> Le samedi, 2 février 2019, 14.48:22 h CET Ian Jackson a écrit :
> > Ping ?
>
> Thank for the ping.
>
> Gunnar and myself have started working on a draft, the latest version of
> which
> is available at
>
>
tags 917991 + pending
thanks
Removed in our working tree, will soon push to the live keyring.
Apollon Oikonomopoulos dijo [Wed, Dec 05, 2018 at 07:56:20PM +0200]:
> > We have found ganeti to embed the system path for ip — which is /bin
> > on non-/usrmerged systems, and /usr/bin on /usrmerged systems.
>
> Thanks for the report! Unfortunately ganeti embeds a lot of other paths,
> detected
Source: gnome-applets
Version: 3.30-0-1
Severity: important
User: m...@linux.it
Usertags: usrmerge
Hello,
You might be aware on the current discussion regarding
/usrmerged-systems breaking package builds for non-/usrmerged systems,
tracked in #914897 and with a long thread in debian-devel
Package: vigor
Version: 0.016-26
Severity: important
Hello,
You might be aware on the current discussion regarding
/usrmerged-systems breaking package builds for non-/usrmerged systems,
tracked in #914897 and with a long thread in debian-devel starting at
Source: ganeti
Version: 2.15
Severity: important
Hello,
You might be aware on the current discussion regarding
/usrmerged-systems breaking package builds for non-/usrmerged systems,
tracked in #914897 and with a long thread in debian-devel starting at
20181120211617.gxnuwxpx2hy44...@angband.pl
Ansgar Burchardt dijo [Wed, Dec 05, 2018 at 08:17:56AM +0100]:
> The Reproducible Builds project was so kind to help and now runs one
> build in a non-merged-/usr and a second build in a merged-/usr
> environment. Packages that hardcode the path to utilities, but would
> pick up the wrong one in
Svante Signell dijo [Wed, Dec 05, 2018 at 02:03:19PM +0100]:
> > If we keep merged-/usr as default then we can /recommend/ people to
> > install usrmerge to switch to merged-/usr; reducing the difference
> > between newly-installed and existing setups is a good idea IMHO. I
> > think I filed a
Adam Borowski dijo [Mon, Dec 03, 2018 at 12:36:29AM +0100]:
> (...)
> So, let's enumerate possible outcomes:
>
> 1. no usrmerge
> 1a. no moves at all (no effort needed!)
> 1b. moves via some dh_usrmove tool, until /bin is empty
> 2. supporting both merged-usr and unmerged-usr
> 3. mandatory
Tollef Fog Heen dijo [Mon, Nov 05, 2018 at 07:44:21PM +0100]:
> END OF RESOLUTION
>
> A: Approve resolution, disallowing the use of dpkg's vendor series
> F: Further Discussion
I vote:
A > F
Thanks,
signature.asc
Description: PGP signature
tags 911791 + pending
thanks
This bug has been fixed in Salsa, and will be included in the next
Stable update.
William Blough dijo [Wed, Oct 24, 2018 at 03:56:56PM -0400]:
> In stable, drupal7 defines a constant (DATE_RFC7231) that conflicts with
> the same constant already defined by php7. This happens intermittently
> depending on what code is being loaded/executed in php (the drupal
> constant is
Anonymous dijo [Sat, Sep 29, 2018 at 05:06:58PM +0200]:
> Dear Chair
Dear Anonymous,
Although it is of course completely fine for you to contact us
anonymously, in cases such as this one, having a "name" will help your
case. Do you actually use this? Have you worked with the issue? Is it
Oh, great.
I messed up when cleaning for this patch, and ended up uploading a
really-b0rken one (i.e. nasty syntax error)
Here goes the fix for the fix for the fix... :-þ
Description: Make listadmin properly follow redirects to HTTPS-using mailmans
Author: Gunnar Wolf
Bug: https
am thus only calling
resolve_redirects when $pattern is undef or empty.
Description: Make listadmin properly follow redirects to HTTPS-using mailmans
Author: Gunnar Wolf
Bug: https://bugs.debian.org/873287
Forwarded: No
Last-Update: 2018-09-20
Index: listadmin-2.42/listadmin.pl
merge 909255 909236
thanks
Both bugs report the same issue.
Stuart Prescott dijo [Wed, Sep 19, 2018 at 12:18:24PM +1000]:
> (...)
> That was perhaps also written before we started to realise that maintainer
> scripts are actually best avoided as they tend to be complicated, fragile,
> difficult to do right and make upgrades harder for the package
tags 740891 + pending
thanks
The package has been uploaded to DELAYED (5 days).
tags 873287 + pending
thanks
The package has been uploaded to DELAYED (5 days).
tags 740891 + patch
thanks
I am proposing the following patch for this package:
Index: listadmin-2.42/listadmin.pl
===
--- listadmin-2.42.orig/listadmin.pl
+++ listadmin-2.42/listadmin.pl
@@ -29,6 +29,7 @@ use strict;
use English;
I am attaching a second patch. Both of the suggestions mentioned here
work for me™.
This one generates a bit more requests early on, but the POSTs go to
the right place from the beginning.
My only quip here is that, if the URL built in the mailman_url
function (line 643--665) does not exist, the
tags 873287 + patch
thanks
Hi,
The simple patch below fixes the issue. Now, I am not too fond of this
patch because it could introduce some strange behavior - POST has
reasons _not_ to be redirected. I would not like actions happening
at a 301 redirect! Of course, the very existence of a 301
tags 903543 + pending
kthxbye
Fixed in the working tree, will be part of the next firmware upload
(which should be soonish, as a new version was recently made
available)
Package: mount
Version: 2.32-0.1
Severity: normal
If I request losetup to detach from a loop device and it cannot be
detached, I would expect it to notify me accordingly. However:
# losetup --list
NAMESIZELIMIT OFFSET AUTOCLEAR RO BACK-FILE
I have applied the patch mentioned above¹ to the aegisub packaging,
and fixed *this portion of* the FTBFS. Unfortunately, aegisub still
fails to build - From my build log:
g++ -MMD -MP -Wdate-time -D_FORTIFY_SOURCE=2
-I/home/gwolf/vcs/build-area/aegisub-3.2.2+dfsg/src/ -I..
101 - 200 of 1232 matches
Mail list logo
