Package: gimp
Version: 2.10.2-1
Severity: grave
Justification: renders package unusable
Hi.
Since some time the GIMP is completely broken.
In most cases it does not even start (e.g. when invoking
it from another program) or when:
$ gimp
or
$ gimp 0.jpg
(with 0.jpg not existing)
it simply hangs
On Tue, 2018-07-10 at 17:20 -0400, Jeremy Bicha wrote:
> I don't know. It works fine here. Could you try to be more specific
> about *when* things stopped working?
I'm afraid I have no idea... I noticed it a week ago, which doesn't
mean though, that it wasn't introduced earlier.
Wasn't there rece
Package: nautilus
Version: 3.30.0-4
Severity: grave
Justification: renders package unusable
Hi.
Since a week or so (IIRC, when the new glib version entered unstable):
$ nautilus
(nautilus:32154): Tracker-ERROR **: 20:06:22.721: Unable to find default domain
ontology rule /usr/share/tracker/dom
Package: xul-ext-useragentswitcher
Version: 0.7.3-3
Followup-For: Bug #881904
Hi.
I've just contacted the upstream author. He in fact plans to make a
WebExtensions
version sooner or later:
On Thu, 2017-11-16 at 17:02 -0800, Chris Pederick wrote:
> I was focused on updating Web Developer up to t
Package: clamav-freshclam
Version: 0.99.3~beta1+dfsg-3
Severity: grave
Justification: renders package unusable
Hi.
With the lastest version the package fails to upgrade:
Setting up clamav-freshclam (0.99.3~beta1+dfsg-3) ...
To check for updates more often than hourly, please run freshclam as a da
Package: libxtables12
Version: 1.6.0+snapshot20161117-2
Severity: grave
Justification: renders package unusable
Hi.
Unpacking libxtables12:amd64 (1.6.0+snapshot20161117-2) ...
dpkg: error processing archive
/tmp/apt-dpkg-install-DBLJsg/0-libxtables12_1.6.0+snapshot20161117-2_amd64.deb
(--unpac
Source: linux
Version: 4.19.20-1
Severity: critical
Tags: upstream patch
Justification: causes serious data loss
Hi.
Apparently there was a longer existing data corruption bug in btrfs[0],
AFAIU it happened when compression was used together with holes in data
and there was *no* recognition by ch
Here's the "proper" patch:
https://www.mail-archive.com/linux-btrfs@vger.kernel.org/msg85515.html
Package: epiphany-browser
Version: 3.31.91-2
Severity: grave
Justification: renders package unusable
Hi.
When starting epiphany it crashes:
$ epiphany
(epiphany:1935): GLib-GIO-ERROR **: 19:35:05.423: Settings schema
'org.gnome.Epiphany.web' does not contain a key named
'hardware-acceleratio
Hey.
Well, while I guess it's functionality will be missed, you're right
that it probably makes no sense to keep it, now that Mozilla broke all
XUL add-ons.
Cheers,
Chris.
On Wed, 2015-08-12 at 20:02 +0200, Sylvestre Ledru wrote:
> libgit, libmarble & libdivecomputer
What a pity :-(
> I have been maintaining subsurface for a while. It was easy in the
> past,
> it is much harder now...
Well your work is highly appreciated... hope you're able to keep it up
=)
Chee
Hey.
How saddening to see such a nice program for divers being basically
destroyed by a stupid and arrogant upstream (and while some may
consider this impolite, I guess it's simply the truth).
Especially the assumption to know it better than the rest of the whole
opensource world and decades of p
On Tue, 2015-08-25 at 17:55 -0700, Dirk Hohndel wrote:
> Being called stupid and arrogant is usually not a great conversation
> opener, but hey, I've been called worse.
Well I should have probably immediately apologised along the way, just
for the sake of politeness...
But the believe to know it m
On Wed, 2015-08-26 at 13:40 +0300, Lubomir I. Ivanov wrote:
> your approach for convincing is offensive and unwise.
Well if upstreams are effectively hostile against core paradigms of the
FLOSS community, it must expect that people won't be happy with it.
> as a peace of software it now no longer
On Wed, 2015-08-26 at 09:05 -0700, Dirk Hohndel wrote:
> Some of us have expressed our dismay with the way distributions work
> these days.
Well to be honest such dismay comes usually always from the same
fraction within open source... which is typically exactly that fraction
which tries to put mor
Hey Guilhem.
> There might be a better way to detect an initramfs-tools environment
I once faced the same question when writing a (cryptsetup) keyscript,
i.e. how to definitely find out whether one's "within" the initramfs.
With crypsetup it may seem easy - check for e.g. /scripts/local-
top/cr
Hey Guilhem.
Is it possible that your fix doesn't work on not-yet-usr-merged
systems?
I get here:
$ env --unset=LD_PRELOAD ldd /sbin/cryptsetup | sed -nr
'/.*=>\s*(\S+)\/libargon2\.so\..*/ {s//\1/p;q}'
/usr/lib/x86_64-linux-gnu
but:
$ dpkg -L libgcc-s1
/lib/x86_64-linux-gnu
/lib/x86_64-linux-
Control: reopen -1
On Wed, 2023-03-08 at 08:16 +0100, Milan Broz wrote:
> Just upstream is no longer responding here...
Seems upstream is dead... I also have some minor PRs open against
argon2, but no response. Tried to get directly in contact with some of
them, but the same.
@Guilhem, I'm reope
On Wed, 2023-03-08 at 14:04 +0100, Guilhem Moulin wrote:
> No please don't, #-1 is RC so that would block transitioning into
> Bookworm which only supports merged-usr… Will fix that later during
> the
> freeze, but ATM the priority is to get -2 into Bookworm ASAP, not
> further delay the transitio
Hey.
Thanks for the fix.
Am I right that this *generally* does not longer enable apache2-
doc.conf per default (i.e. also on fresh installs)?
Causes that would also make it fix #977014.
Cheers,
Chris.
On Mon, 2023-04-03 at 10:38 +0400, Yadd wrote:
> > Causes that would also make it fix #977014.
> Sure, thanks for the link
You've marked it as fixed but haven't closed it.
Was that on purpose or should I close it?
> I saw in this issue that you were a little frustrated by the lack of
> respons
Package: libheif1
Version: 1.16.2-1+b1
Severity: grave
Justification: renders package unusable
Hey.
With libheif1, heif-gdk-pixbuf and heif-thumbnailer installed, I was able
to display *.heic images from my smartphone in eog, geeqie and gimp.
But after upgrading to 1.16.2-1+b1 dies works no long
Weird... I did another upgrade/downgrade cycle and it now works (with
the downgraded version) for eog too.
And I'm pretty sure I checked the first time, whether eog was perhaps
still running and using the old (that is the new version) of the lib.
On Sun, 2023-07-16 at 16:25 +0200, Fabian Greffrath wrote:
> Do you have the heif-gdk-pixbuf package installed?
Yes:
On Sun, 2023-07-16 at 14:25 +0200, Christoph Anton Mitterer wrote:
> With libheif1, heif-gdk-pixbuf and heif-thumbnailer installed, I was
Cheers,
Chris.
Hey Joachim.
On Mon, 2023-07-17 at 08:49 +0200, Joachim Bauch wrote:
> do you have any of the "libheif-plugin-*" packages installed with
> 1.16.2?
Quoting myself :-)
On Sun, 2023-07-16 at 14:25 +0200, Christoph Anton Mitterer wrote:
> But after upgrading to 1.16.2-1+b1 dies
Package: kismet-plugins
Version: 2016.07.R1-1+b1
Severity: grave
Justification: renders package unusable
Hey.
libssl1.1 has been removed from unstable and thus kismet-plugins is no
longer installable.
Cheers,
Chris.
Package: vim
Version: 2:9.0.1000-2
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
Hey.
The following probably still worked with 2:9.0.1000-1, but definitely works
again
when going back to the version in testing (2:9.0.0813-1+b1).
Wh
Control: tags -1 - ftbfs
Control: severity -1 important
Still not used to reportbug's new numbering...
Hey Pierre.
On Tue, 2022-12-06 at 23:08 +0100, Pierre Gruet wrote:
> Thanks for the bug report (and the follow-up precisions you sent)!
>
> Yet I fail to reproduce it on testing. I installed zookeeper and
> zookeeperd on testing, then ran
>
> $ /usr/share/zookeeper/bin/zkCli.sh
> specifying not
Hey.
AFAICS, all python script have been adapted to Python3 upstream (or
dropped)... so I guess this could be solved by upgrading to the current
version.
Cheers,
Chris.
On Tue, 2021-05-04 at 16:51 +0200, Guido Günther wrote:
> Since upstream is pretty inactive i wonder if we should just drop it,
> it
> won't be in bullseye either and popcon is fairly low:
Hmm I always found it to be pretty nice... an are there any specific
bugs/features that would be needed to wo
Source: zookeeper
Version: 3.4.13-6
Severity: grave
Tags: security
Justification: user security hole
X-Debbugs-Cc: Debian Security Team
Hi.
The release notes for https://zookeeper.apache.org/doc/r3.6.3/releasenotes.html
list various security issues:
CVE-2020-25649
CVE-2021-21295
CVE-2021-28165
Hey.
Just wondered:
1) Since this is a binary blob who, by it's nature, is made for
surveillance, it's IMO more a rather serious security issue than just a
DFSG-policy problem.
No one really knows what exactly Google ships there.
So maybe people should be told about this more actively in a DSA
On Fri, 2021-01-01 at 12:10 +0100, Michel Le Bihan wrote:
>
>
> That's actually intended. It would be easier to set the build flag
> that
> disables it, but some users are still interested in using it. The way
> it's done currently still allows them to use it.
Yeah, but the point is, AFAIU, for
Package: gimp-gmic
Version: 2.9.4-1
Severity: grave
Justification: renders package unusable
Hi.
Since one of the more recent upgrades, gimp doesn't start up anymore, when
gimp-gmic is present (purging it solves the issue), but instead hangs
forever at th slapsh screen.
Cheers,
Chris.
$ gimp
Hey.
Seems gprename has been ported to GTK3... would be awesome if this
could find it's way back into Debian :-)
https://sourceforge.net/p/gprename/bugs/18/
Cheers,
Chris.
On Sat, 2017-07-15 at 22:21 +, Debian Bug Tracking System wrote:
> * Disable remote updates to fix CVE-2017-7480 and prevent bugs like
> it in the future (closes: #765895, #866677)
It's good to see this finally done... but really sad to see, that it
required an actually exploit to be fou
Source: zookeeper
Severity: grave
Tags: security
Justification: user security hole
Hi.
It seems there is a grave permission issue in the zookeeper package,
namely that /var/lib/zookeeper is created world-readable.
Since ZK creates its files word-readable as well, any user on the system
can extra
On Fri, 2017-01-27 at 10:34 +0100, lopiuh wrote:
> * What outcome did you expect instead?
> [...]
> #LoginGraceTime 2m
> PermitRootLogin prohibit-password
> #StrictModes yes
> #MaxAuthTries 6
> #MaxSessions 10
> [...]
No, the outcome shouldn't be that, it should be left just at default
(which
Package: firefox-esr
Version: 45.7.0esr-2
Severity: grave
Justification: renders package unusable
Hi.
Since the upgrade from -1 to -2 firefox esr crashes few seconds or minutes
after starting it,
with a Mozilla Crash Handler dialog.
Downgrading to 45.7.0esr-1 fixes the issue.
Cheers,
Chris.
-
On Sun, 2017-02-05 at 18:15 +0100, Pascal Legrand wrote:
> What is the way to downgrade 45.7.0esr-1 ?
You can for example enable testing in your sources.list, then update
and then just select/install the older version in aptitude.
Cheers,
Chris.
smime.p7s
Description: S/MIME cryptographic signatu
Package: xul-ext-status4evar
Version: 2016.10.11.01-1
Severity: grave
Justification: renders package unusable
Hi.
In FF54, the plugin does not really seem to work anymore.
The status bar is shown, but no content in it.
An update seems to be available, solving this:
http://forums.mozillazine.org
Package: xul-ext-noscript
Version: 5.1.2-1
Severity: grave
Tags: security
Justification: renders package unusable
Hi.
Since the upgrade to 5.1.2-1 the plugin, while still appearing in the
add-ons list (and marked enabled there), no longer seems to work.
It's "icons/menus/etc" disappeared and can
Package: src:linux
Version: 4.13.10-1
Severity: critical
Justification: breaks unrelated software
Hi.
Apparently AppArmor was enabled per default in the last version.
While I'm usually in favour of anything that improves security
(leaving aside the question here whether SELinux wouldn't be the
Package: base-files
Version: 10.2
Severity: critical
Justification: breaks unrelated software
Hi.
While the bug is likely in debian-security-support, as soon as upgrading to 10.2
(downgrading to 10.1 fixes the problem) a debian-security-support hook will
fail at basically every installed/upgrade
Yeah it's definitely that strange hardcoded part in:
/usr/bin/check-support-status:
> DEB_LOWEST_VER_ID=7
> # Version ID for next Debian stable
> DEB_NEXT_VER_ID=9
> …
> if [ "$DEBIAN_VERSION" -lt "$DEB_LOWEST_VER_ID" ] || [ "$DEBIAN_VERSION" -gt
> "$DEB_NEXT_VER_ID" ] ; then
> eval_gettext "
On Sat, 2019-04-20 at 09:22 +0200, Santiago Vila wrote:
> I'm adding "affect base-files" so that people see this bug in the BTS
> page for base-files and nobody thinks the problem is in base-files,
> but just for that.
Well at least with this it does *not* show up in apt-listbugs and
prevent peopl
Package: plowshare
Version: 2.1.7-2
Severity: grave
Tags: security
Justification: user security hole
Hi.
The removal of plowshare-modules, which was IMO quite !smart, forces
users to use plowmod which is IMO, like basically every code-downloader
inherently insecure.
1) There seems to be no veri
Control: reopen -1
As if I wouldn't have written it before... o.O
Now all that was done is changing the value from 9 to 10 and it will
break again in xx months when the next-stable arrives an no one will
remember by then that this must be adapted...
Can't you just set a Conflicts/Breaks against
Package: liblog4j1.2-java
Version: 1.2.17-10
Severity: grave
Tags: security upstream
Justification: user security hole
X-Debbugs-Cc: Debian Security Team
Hey.
A number of holes was found in the 1.2 branch of log4j.
The following is apparently critical (code injection):
https://www.cvedetails.co
Further for the records (for a future upgrade to newer ZK versions):
There will likely need to be a NEWS.Debian entry about the following:
https://issues.apache.org/jira/browse/ZOOKEEPER-3056
In short:
- apparently they've added a check that prevents ZK from starting, when
no snapshots were fou
Hey.
Is that going to be fixed in stable, too?
Cheers,
Chris.
Hey.
On Sun, 2021-06-27 at 14:46 +0200, Salvatore Bonaccorso wrote:
> To me this looks like CVEs in other products, but which zookeeper
> uses
> as dependency? Is this correct?
Indeed, but I couldn't find that the zookeeper package depends on these
while it does contain:
zookeeper-3.4.13/src$ fin
On Thu, 2021-07-15 at 21:18 -0700, tony mancill wrote:
> The Debian package disables building against Netty via this patch:
> https://salsa.debian.org/java-team/zookeeper/-/blob/master/debian/patches/13-disable-netty-connection-factory.patch
Ah I see.
> This is certainly a valid point. There i
Package: kdenlive-data
Version: 21.04.3-1
Severity: grave
Justification: renders package unusable
Hey.
There is some conflict:
Preparing to unpack .../kdenlive-data_21.04.3-1_all.deb ...
Unpacking kdenlive-data (21.04.3-1) over (20.12.3-1) ...
dpkg: error processing archive
/var/cache/apt/arch
Source: pulseaudio
Version: 15.0+dfsg1-2
Severity: grave
Justification: renders package unusable
Hi
Since upgrading to 15.0+dfsg1-2, the pulseaudio daemon runs constantly at
around ~20% CPU
on my system (even when no sound is played).
If sound is played it's constantly crackling.
Downgrading
Package: libigdgmm12
Version: 22.1.1+ds1-1
Severity: critical
Justification: breaks unrelated software
Hey.
This version breaks e.g. video playback with mpv (also vlc):
$ mpv test.mp4
(+) Video --vid=1 (h264 720x300 23.976fps)
(+) Audio --aid=1 (aac 2ch 44100Hz)
Segmentation fault
With:
Mar
On Sun, 2022-03-20 at 07:07 +0100, Paul Menzel wrote:
> Firefox with VA-API enabled crashes too,
> but not when it’s disabled.
> Do you have VA-API enabled for mpv?
I do have:
hwdec=auto
in mpv.conf, which I think would use vaapi here.
However, I have nothing specifically set for VLC.
Thanks,
Package: cryptsetup
Version: 2:2.4.2-1
Severity: critical
Tags: security upstream
Justification: root security hole
Hey.
You've probably seen it already... Milan found CVE-2021-4122, and
the package should be upgraded to 2.4.3 ASAP.
Thanks in advance,
Chris.
Not sure if this is related, but since a while I've noted even bigger
than the usual performance problems of firefox...
Crackling sound is something I've heard for a month now... but since
about FF93 came out CPU utilisation seems to be much higher.
I just load simple webpages and may CPU goes up
On Thu, 2021-11-11 at 23:06 +1100, 小太 wrote:
> So either the change needs to be backported to v94
It seems Mike has already been active in that bug (and even found it
himself a ~month ago ^^) and indicated he'll backport it (AFAIU).
Which I hope really happens... I know there is no official secu
On Sat, 2021-11-20 at 15:30 -0800, Josh Triplett wrote:
> I'm still experiencing this bug regularly, with complete browser UI
> freezes that require killing and restarting Firefox.
Hm perhaps something else? At least I haven't suffered from that
particular issue since 94.0-2.
Cheers,
Chris.
I just had one occasion of the "freezing" problem... but it was the
first time since we got 94.0-2.
Also it didn't occur short after start, but quite some time after
browsing the very same websites.
But the symptoms were as described in message #15 (i.e. that loading
wheel).
So there may be sti
Package: libphonenumber8
Version: 8.12.46-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
Hi.
8.12.46-1 causes evolution to fail:
$ evolution
evolution: symbol lookup error: /usr/lib/x86_64-linux-gnu/libphonenumber.so.8:
undefined s
On Sat, 2022-04-02 at 08:14 -0700, tony mancill wrote:
> Thank you for the bug report Chris, for setting the severity so
> as to block the migration, and noting the affected packages.
Actually, the latter two were done by some other helpers :-)
Thanks,
Chris.
Package: ca-certificates
Version: 20211004
Severity: grave
Justification: renders package unusable
Hey.
It seems that when not selecting any of the new certs on upgrade, the package
install fails:
Setting up ca-certificates (20211004) ...
Updating certificates in /etc/ssl/certs...
chmod: cannot
Package: firefox
Version: 93.0-1+b1
Severity: grave
Justification: renders package unusable
Hey.
Since about yesterday (possibly since the rebuilt package came in)
firefox freezes shortly after being started.
There is no high CPU activity then, it just takes no input anymore
(no keyboard, no mous
Sometimes it seems that firefox doesn't freeze "immediatly" but some
sites continue to work (and e.g. the address bar still allows input).
But new sites (especially with JS stuff) don't load correctly or just
freeze.
Eventually whole firefox freezes and one cannot event select the
address bar anym
Oh and as a warning for everyone who wants to try out.
Stupid *zilla seems to no prevent downgrade of the profiles... so once
upgraded you cannot downgrade without throwing away your old profile
with all data in it. Wonderful...
FF94 is still broken.
> I was also experiencing this problem and was monitoring this bug
> report for potential solutions, but the problem seems to have
> recently disappeared.
I cannot confirm this.
I've just upgraded to 94.0-1 (with everything else on my system
upgraded to the current state of unstable, well everyt
Package: linux-base
Version: 4.6
Severity: grave
Justification: renders package unusable
Hi.
Since last April, the package can't be upgraded as it conflicts with
the current version of kernel-common.
Would be nice if this could be resolved.
Probably it's this change:
* Take over kernel-img.c
Hey.
Just to put some emphasise on this, the fix has now been merged late to
5.3 as urgent.
Also note Filipe's post[0] that the issue can more or less hit anyone.
Cheers,
Chris.
[0]
https://lore.kernel.org/linux-btrfs/9731b0e7-81f3-4ee5-6f89-b4fd8d981...@petaramesh.org/T/#m7b3863ef7ec5f62a2f7
Hey.
Is there anything one can help to speed this up?
A patch is available for two weeks now, while Debian users of testing
and unstable are left with the danger of catastrophic btrfs corruption
without even any warning to them (so that they could at least downgrade
to <5.2).
Cheers,
Chris.
Control: forwarded -1
https://lore.kernel.org/lkml/d05aba2742ae42783788c954e2a380e7fcb10830.ca...@scientia.net/
Hey.
I've forwarded this to lkml.
My most recent post in that thread[0] contains an pretty elaborate test
series comparing kernel 5.2 vs. 5.4 (each with intel_pstate=disable and
witho
Hey.
According to https://gitlab.freedesktop.org/drm/intel/issues/953 the
bug was introduced by:
drm/i915/gen8+: Add RC6 CTX corruption WA
(d4360736a7c0a6326e3bbdf7d41181f6ed03d9a6)
which, AFAIU, is actually a security fix.
There seem to be some patches, but not sure when they'll be "final" (i
Package: unhide
Version: 20130526-3
Severity: grave
Justification: renders package unusable
Since 1-3 weeks unhide segfaults every time:
Nov 30 01:39:48 heisenberg kernel: unhide[208429]: segfault at 7ffd06cfec58 ip
55c15aa077d3 sp 7ffd06cfec60 error 6 in unhide-linux[55c15aa07000+6000
Hey Ben, Salvatore.
Thanks for cherry-picking the bug for unstable.
AFAIU stretch and jessie[-backports] should be affected as well.
Shouldn't it go there, too?
At least at the upstream mailing list it was said[0] the the bug was
introduced around October 2008, which should be roughly kernel 2.6
Package: o-saft
Version: 17.09.17-1
Severity: grave
Justification: renders package unusable
Hey.
The following happens on a fresh install:
$ o-saft
Can't locate osaft.pm in @INC (you may need to install the osaft module) (@INC
contains: ./ ./lib /usr/bin /bin /etc/perl
/usr/local/lib/x86_64-l
Source: openmpi
Version: 3.1.3-6
Severity: critical
Justification: causes serious data loss
Hi.
On upgrading from 3.1.3-5 I get these:
Unpacking libopenmpi3:amd64 (3.1.3-6) over (3.1.3-5) ...
rm: cannot remove '/usr/lib/x86_64-linux-gnu/fortran/gfortran-8#': No such file
or directory
rm: cannot
Package: iptables
Version: 1.8.1-1
Severity: critical
Tags: security
Hi.
Seems the massive changes in the recent version breaks loading of
firewall rules by tools like netfilter-persistent...
# journalctl | grep netfilter
Oct 25 15:36:55 klenze systemd[1]: Starting netfilter persistent
configu
Source: linux
Version: 4.18.20-2
Severity: critical
Tags: upstream patch
Justification: causes serious data loss
Hi.
There's a bug in the blk-mq schedulers which may cause serious data
curruption...
See https://bugzilla.kernel.org/show_bug.cgi?id=201685
Seems like a patch was made recently,...
For those reading along, Jens Axboe gave a summary on how to
check whether one's affected or not:
Quoting from: https://bugzilla.kernel.org/show_bug.cgi?id=201685#c294
> scsi_mod.use_blk_mq=0 will do the trick, as will just ensuring that you have
> a scheduler for your device. Eg for sda, check:
>
Source: linux
Version: 5.2.9-2
Severity: critical
Tags: upstream patch
Justification: causes serious data loss
Hi.
There were some reports over the last weeks from users on linux-btrfs which
suffered from catastrophic btrfs corruption.
The bug which is apparently a regression introduced in 5.2 h
Source: linux
Version: 5.19.6-1
Severity: critical
Justification: breaks the whole system
Hi.
6.0.3 introduced a commit that causes (permanent) CPU soft lockups
for some people with btrfs filesystems, effectively breaking the
system, e.g. when booting.
See e.g.
https://lore.kernel.org/linux-btr
Control: retitle -1 6.0.5 fixes critical btrfs bug in 6.0.3, affecting space
cache v1 filesystems
Control: notfound -1 5.19.6-1
Control: found -1 6.0.3-1
No idea why reportbug picked 5.19.6, which I have not even installed
anymore... o.O
Hey Salvatore.
On Fri, 2022-10-28 at 06:49 +0200, Salvatore Bonaccorso wrote:
> I did decide to still do so, so we can have the CVE fix migrate
> finally to testing (which took some time as well given there was the
> perl transition ongoing).
Fine for me... I think it would be nice if there was a
On Sat, 2022-10-29 at 09:23 +0200, Salvatore Bonaccorso wrote:
>
> No unfortunately we cannot do that. The reason is similar to what
> lead
> to
> https://salsa.debian.org/kernel-team/linux/-/commit/248736d493fcfd0e05cd23f97befe40f5c125c71
> or caused bugs like #916927.
Forgive me my ignorance, b
Package: firefox
Version: 100.0.2-1
Severity: serious
Tags: security ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: Debian Security Team
Hi.
Would be good to see 101 packaged ASAP, as it fixes numerous issues,
including some which are apparent
On Sat, 2022-06-04 at 14:42 +0200, Vincent Bernat wrote:
> Unfortunately, Firefox is not buildable due to depending on a version
> of
> Cargo not available in unstable.
Shouldn't that be reopened then?
I wouldn't be surprised if quite a number of people use the non ESR FF,
probably also DDs/DMs.
Could someone then possibly rebuild this with Julian’s patch, ASAP?
Over a week with a likely remote code exploit hole in the browser of
any Debian (non-ESR) FF user, seems not so ideal,
Thanks,
Chris.
On Fri, 2022-06-10 at 05:09 +0900, Mike Hommey wrote:
> There's a 101.0.1 on the way.
I assume you mean "being built for Debian"?
Anyway... thanks for taking care. :-)
Cheers,
Chris.
Hey Holger.
It also seems as if neither that director or its files nor the created
user is ever cleaned up on purge, but left behind as cruft forever.
Or did I oversee something in the posrm?
Thanks,
Chris.
On Tue, 2022-08-23 at 16:23 +, Holger Levsen wrote:
> users must not be cleaned up (=removed) on package removal
Well perhaps not a must as per policy, but I think for debian-security-
support it would still make sense to clean up the user, or do you
expect anyone to create files under that us
Package: libgtkhex-4-1
Version: 43~alpha-1
Severity: grave
Justification: renders package unusable
Hey.
When trying to upgrade:
Unpacking libgtkhex-4-1:amd64 (43~alpha-1) ...
dpkg: error processing archive
/var/cache/apt/archives/libgtkhex-4-1_43~alpha-1_amd64.deb (--unpack):
trying to overwri
Package: qtqr
Version: 2.1~bzr46-2
Severity: grave
Justification: renders package unusable
Hey.
On a fresh install of the package:
$ qtqr
Traceback (most recent call last):
File "/usr/bin/qtqr", line 15, in
from qrtools import QR
ModuleNotFoundError: No module named 'qrtools'
Thanks,
Ch
Package: libphonenumber8
Version: 8.12.57+ds-1+b2
Severity: serious
Hey.
After the upgrade, evolution crashes when started:
$ evolution
evolution: symbol lookup error:
/usr/lib/x86_64-linux-gnu/libebook-contacts-1.2.so.4: undefined symbol:
_ZN4i18n12phonenumbers11PhoneNumberC1EPN6google8protob
Hey Tony.
On Tue, 2022-11-22 at 20:40 -0800, tony mancill wrote:
> Thank you for the bug report. libphonenumber 8.12.57+ds-1 has been
> in
> testing for longer than a month at this point [1]. Has it been
> broken
> all of this time? If not, I suspect this is related the protobuf
> transition [2
On Tue, 2022-11-22 at 21:11 -0800, tony mancill wrote:
> Yes, totally. I didn't mean to imply that the bug shouldn't be here.
Sure... just wanted to point out, that I don't consider it your fault
or so :-)
> > I had evolution running, while I've upgraded. And didn't restart it
> > afterwards (
Hey.
I've just installed this again on some node, and for some reason apt-
listbugs still shows it as open:
# aptitude
Performing actions...
Retrieving bug reports... Done
Parsing Found/Fixed information... Done
grave bugs of liblog4j1.2-java (→ 1.2.17-10+deb11u1)
b1 - #1004482 - liblog4j1.2-jav
1 - 100 of 519 matches
Mail list logo
