On Thu, 13 Sep 2012, Moritz Muehlenhoff wrote:
On Fri, Aug 31, 2012 at 06:34:38PM +0200, Julien Cristau wrote:
Can't answer without a diff.
Mediawiki maintainers, what's the status?
Oh, sorry. Other stuff made me forget this for too long.
The diff between the two tarballs is over 10 MiB,
On Thu, 30 Aug 2012, Thorsten Glaser wrote:
I’m hereby seeking pre-upload approval for new uploads (not new
upstream versions) of src:mediawiki-extensions (the most critical
one), src:fusionforge (very important, as otherwise the mediawiki
binary package must declare a Breaks on fusionforge
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package mksh
The upload 40.9.20120630-3 was specifically made to target wheezy;
the changes have been tested for a while now, and the diff, split
by the kind of change done,
(which they were).
--- mediawiki-1.19.2-0/debian/changelog 2012-06-18 17:17:26.0 +0200
+++ mediawiki-1.19.2-1/debian/changelog 2012-09-20 13:45:26.0 +0200
@@ -1,3 +1,26 @@
+mediawiki (1:1.19.2-1) unstable; urgency=low
+
+ [ Thorsten Glaser ]
+ * New upstream: security fixes for CVE
content-less ul element in Collection extension
+ * Fix invalid XHTML in InputBox extension
+
+ -- Thorsten Glaser t...@mirbsd.de Thu, 20 Sep 2012 13:40:12 +0200
+
mediawiki-extensions (2.7) unstable; urgency=low
* Target MediaWiki 1.19
--- mediawiki-extensions-2.7/debian/control 2012-06-29 17
fixed 687641 2.7
fixed 686190 2.7
thanks
Adam D. Barratt dixit:
Please don't do that. Everyone's unblock request is important to them,
and many of them also fix RC bugs. unblock bugs are normal at most,
unless the release team choose to make them otherwise.
Okay, sorry.
If the bug is fixed in
Adam D. Barratt dixit:
Updating mediawiki-extensions-base introduces new bugs: #686190
Asking for an unblock that reintroduces an RC bug in to wheezy is a
little unusual, to say the least.
It actually fixes that one.
release team ever suggesting that they would be accepted and I thought
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu
nmu mksh_40.9.20120630-3 . armhf . -m Rebuild against fixed klibc
maximilian attems dixit:
On Sun, 30 Sep 2012, Thorsten Glaser wrote:
[…]
and without busybox, and rebuilding mksh
using sudo mwdisext FCKeditor.php if installed
+ from Debian packaging.
+
+ -- Thorsten Glaser t...@mirbsd.de Tue, 02 Oct 2012 14:09:42 +0200
--- mediawiki-extensions-2.8/debian/changelog 2012-09-20 13:45:26.0
+0200
+++ mediawiki-extensions-2.9/debian/changelog 2012-10-02 14:09
retitle 689153 unblock: mksh/40.9.20120630-4
thanks
Hi,
sorry for the trouble, but please wait for the -4 upload,
as recent changes in gcc will let mksh ftbfs, and doko
said he'll want to propose these versions for wheezy; I've
made the same hotfix in Ubuntu already.
bye,
//mirabilos
--
Michael Biebl dixit:
A better approach imho would be to simply remove sysklogd from the
archive.
Please no!
//mirabilos (still ill)
--
Natureshadow Dann mach ich git annex copy --to shore und fertig ist das
Natureshadow das ist ja viel cooler als ownCloud ...
mirabilos sag ich doch
On Wed, 14 Nov 2012, Niels Thykier wrote:
* The package had at least one RC bug without activity for the past
14 days.
Jonathan Wiltshire j...@debian.org
mediawiki-math (U)
Mediawiki Maintenance Team pkg-mediawiki-de...@lists.alioth.debian.org
mediawiki-math
Hey Jonathan,
Hi,
I’d like to do a ping for mksh unblocking and the release notes
entry, just so they don’t accidentally forgotten.
In case someone already has these on their radar, please sorry
for the noise.
bye,
//mirabilos
--
FWIW, I'm quite impressed with mksh interactively. I thought it was much
Hi,
I would like to put the following patch, which took me 3¼ hours to
find, into mksh in wheezy. It reverts a flag which I mistakenly
converted to bool back to int, as it’s used as a counter. The effect
is that, when you have non-ASCII characters on the command line and
then insert something in
-2012-3386
+ * Small improvements to package description and d/rules comments
+
+ -- Thorsten Glaser t...@mirbsd.de Wed, 18 Jul 2012 17:37:12 +
+
jupp (3.1.20-1) unstable; urgency=medium
* New upstream release “nik”
diff -Nru jupp-3.1.20/debian/control jupp-3.1.21/debian/control
--- jupp
Julien Cristau dixit:
On Wed, Jul 18, 2012 at 18:47:23 +, Thorsten Glaser wrote:
bw.c second hunk: yes, this is really an assignment (hence the
double parenthesēs), it’s the missing initialisation.
You know you could make that two lines and then it would actually be
readable and you
Hi,
sorry to disturb, but I'll be uploading a bugfix of mksh (korn shell)
soon, and would like to include a feature I forgot earlier but would be
useful to have in wheezy so scripts can depend on it. This goes under
guideline #6, as I believe more escaping is Always Good, especially in
shell
] Fix CONSERVATIVE_FDS use-before-definition bug
+- [tg] Correct a regression when tab-completing (LP#1025843) and fix
+ bugs in the same code wrt. completion display and other expansions
+ * Document use of CONSERVATIVE_FDS in lksh manpage
+
+ -- Thorsten Glaser t...@mirbsd.de Fri, 20
Enrico Tassi dixit:
With that version liblua5.2-dev installs in /usr/lib/$triplet/ include
What’s wrong with /usr/include/$triplet/ as other packages do?
bye,
//mirabilos
--
Using Lynx is like wearing a really good pair of shades: cuts out
the glare and harmful UV (ultra-vanity), and you
Adam D. Barratt dixit:
Any remaining automatic exceptions will therefore be retired after the
final britney run on July 30th - i.e. one month after freeze.
That’s a drastic thing to do with this short a notice,
especially considering nobody has bothered to fix the
nodejs thing yet, and at least
+ bugs in the same code wrt. completion display and other expansions
+ * Document use of CONSERVATIVE_FDS in lksh manpage
+
+ -- Thorsten Glaser t...@mirbsd.de Fri, 20 Jul 2012 23:32:37 +
+
mksh (40.9.20120630-1) unstable; urgency=low
* The “GC2TDN7” upload
--- mksh-40.9.20120630-1
Julien Cristau dixit:
And nodejs wasn't going to get into wheezy anyway, that boat sailed when
it wasn't fixed 6 months ago.
Ah thanks for saying so, now. May we at least fix json-js?
bye,
//mirabilos
--
Natureshadow Dann mach ich git annex copy --to shore und fertig ist das
Natureshadow das
Adam D. Barratt dixit:
document, also linked from dda). Fixing nodejs will require a new
source upload, which would immediately render the automatic exception
invalid in any case.
The one for nodejs, yes, but not the one for packages blocked by its
migration.
bye,
//mirabilos
--
Natureshadow
On Fri, 31 Aug 2012, Moritz Muehlenhoff wrote:
Please see here for more info:
http://www.gossamer-threads.com/lists/wiki/mediawiki/295767
Thanks.
The Release Notes say that 1.19.2 is a security-fix release,
and does not list any unrelated changes. Question is, (to the
more seasoned MW
On Thu, 30 Aug 2012, Thorsten Glaser wrote:
I’m hereby seeking pre-upload approval for new uploads (not new
[…]
• fusionforge_5.2~rc1wheezy1.debdiff
The diff attached will also need to be added to this upload
for security reasons. I found out today that deleted users
can still log in via SSH
On Mon, 3 Sep 2012, Thorsten Glaser wrote:
The diff attached will also need to be added to this upload
for security reasons.
And this one, too. The forge has public information, such as
a user’s homepage – https://alioth.debian.org/users/tg – and
the https://alioth.debian.org/top/toplist.php
On Wed, 5 Sep 2012, Raphael Geissert wrote:
Thorsten, anyone else: can somebody confirm whether this and the other issue
affect the version in squeeze?
No idea, I’ve never touched FF 5.0 (we skipped straight
to 5.1), but it’s not unlikely. Maybe one of the other
devs can say anything about
Lasse Collin dixit:
default memory usage limit for compression (but not decompression), but
I don't know what that should be (40 %, 80 %, 95 % of RAM? max(80 % of
RAM, RAM - 256 MiB)?). Some default limit may be needed in the future
RAM is irrelevant, datasize ulimit (soft, maybe hard if you
(unauthenticated local privilege escalation)
+using upstream-provided diff
+
+ -- Thorsten Glaser t...@mirbsd.de Thu, 17 Apr 2008 21:55:05 +
+
mksh (28.0-2) unstable; urgency=low
* Fix unaligned memory access on IA-64 (same fix was applied
diff -Nru /tmp/kByzvWMkp5/mksh-28.0/misc.c /tmp
Gerrit Pape dixit:
Hi, I support this. On top of it I would like to drop the debconf
question from the dash package, and install a /bin/sh symlink
unconditionally. If bash should optionally be installed as /bin/sh, a
similar config mechanism could be added to the bash package, and/or a
better
Petter Reinholdtsen dixit:
I do not see the advantage of increasing the complexity by making it
easier to change /bin/sh to anything but dash and bash.
First of, this is already possible, so that wouldn't be a change, just
keeping currently existing behaviour.
Second, Debian policy states that
Petter Reinholdtsen dixit:
Please consider keeping current policy and implementing the
alternatives system like the window manager stuff in the Debconf
tutorial.
I believe the reason /bin/sh replacment isn't done using alternatives
it to reduce the possibility of leaving the system completely
Otavio Salvador dixit:
suggest you to produce a set of patches to implment it and proposed it
to debian-devel and then as release goal (on another thread).
Hm, who is “you” in this case? For me, as mksh maintainer, it's “just”
important that all shells that CAN be used as /bin/sh have the exact
Brian Morris dixit:
I noticed the other day that a new dependency (MPC) from upstream for gcc4.5
http://gcc.gnu.org/gcc-4.5/changes.html
is failing to build on 68k,
see m68k at the bottom of this page, says not since gcc 4.3.
While I can probably take care of compiling gcc-4.5 and its
Matthias Klose dixit:
At this point, pretty well after the GCC 4.6.0 release, I would like to avoid
switching more architectures to 4.5, but rather get rid of GCC 4.5 to reduce
maintenance efforts on the debian-gcc side, even before the multiarch changes
Porters side, too. I’m okay with
Bernhard R. Link dixit:
The effect you see is usually not from a unclean chroot, but from a
non-minimal chroot.
Non-minimal is unclean.
It essentially means that the cvs package misses
either code to mitigate this or misses a Build-Conflicts.
Possibly… the package from squeeze and older is
Adam D. Barratt dixit:
Ping?
buildd.d.o doesn’t have stable-security build logs, but the
package showed up in the meantime. It does not contain the
dir file, so I’m considering the issue solved (for now).
bye,
//mirabilos
--
“Having a smoking section in a restaurant is like having
Adam D. Barratt dixit:
Erm, no. The mail you've replied to is about an issue in texlive, which
has nothing to do with either stable-security or info/dir.gz files.
Oops. Sorry. It went directly beneath the cvs one in my INBOX,
and so I was confused.
bye,
//mirabilos
--
“Having a smoking
Andrew Pollock dixit:
I just noticed that the version of xz-utils in wheezy is
5.1.1alpha+20110809-3
OK, you’ve just proven me wrong that nobody’d notice that.
So it sounds like this version is probably better suited in experimental,
and not unstable and testing. 5.0.3 is what wheezy should
Jonathan Wiltshire dixit:
With this in mind please bear with us for bringing this work and the
associated
testing closer to the freeze than would otherwise be desirable, and we are
happy to provide status information on request.
The same goes for FusionForge, which contains a plugin
Package: mksh
Version: 33.1-2
Severity: minor
Tags: goal-dash, moreinfo
Owner: debian-release@lists.debian.org
Hello!
I just saw the following:
# Switch /bin/sh to dash
Advocate: Petter Reinholdtsen?
Release-Team-Contact: ??
Description: Make sure dash is installed and preseed debconf
Lucas Nussbaum dixit:
On 26/08/08 at 13:00 +, Thorsten Glaser wrote:
DDPOMail robot dixit:
=== libbsd-arc4random-perl:
= Not in testing for 27 days.
If things don't change, it won't be part of lenny!
See
http://release.debian.org/migration/testing.pl?package=libbsd-arc4random
Luk Claes dixit:
Yes, the reason is that new packages unfortunately take too much time to
review and the freeze is meant for getting stable, not for introducing
new features and packages into testing.
Well, technically these were uploaded before the freeze, and mine even
independent of any time
Debian Installer dixit:
Accepted:
mksh_35.2-3.dsc
to pool/main/m/mksh/mksh_35.2-3.dsc
Closing bugs: 499139
Today’s sponsor and the bug submitter agree that this bug, as it
affects debconf and, as such, dpkg/apt usability, should be fixed
in lenny. I would like to request a freeze exception
On Wed, 12 Dec 2012, Niels Thykier wrote:
On 2012-12-12 10:58, Dominik George wrote:
Dear release managers,
today, I chose to fix RC bug #694998. It is a security issue with
To be exact, I asked Dominik whether he can have a look at it
and review it (and ask the Release Team) because I
On Wed, 12 Dec 2012, Niels Thykier wrote:
The filtered diff looks reasonable, feel free to upload 1.19.3-0.1 to
unstable. Please file an unblock bug for it after it has been in
unstable for some time.
Thanks Niels.
Dominik, please commit the changes needed, version as 1:1.19.3-1
and mark as
On Sat, 15 Dec 2012, Adam D. Barratt wrote:
The first patch was *not* in the 1.19.2 package:
Indeed, I totally fucked up this one. Apparently, there was a
“wheezy” branch in svn which I was supposed to use but did not.
The changes that sled in were:
• the “| php5-mysqlnd” dependency (#689758)
Jonathan Wiltshire dixit:
Any idea what the comment in
++ array('a', /* does not work */ 'img')));
is about?
The MediaWiki HTML sanitiser accepts an array of tags to also
accept in the output. I’ve tried whitelisting 'a' and 'img',
but the latter does not currently work. I hope
Andres Salomon dixit:
Hm. Rather than simply remove it, can we actually provide an upgrade
path to rsyslog? I'd be happy to NMU a version of ksyslogd that
does this in unstable (for consideration in wheezy), as long as rsyslog
is truly a drop-in replacement.
No, I veto that, I’m happily using
On Wed, 27 Feb 2013, Adam D. Barratt wrote:
As a side note, the changelog didn't really need:
+ * Note: these changes were part of this upload, even though
+they were not detailed in this changelog entry when uploading:
which will look a little odd to those perusing the changelog in
On Thu, 28 Feb 2013, Adam D. Barratt wrote:
I'd just have included them in the older changelog stanza as is and noted in
the current version that I'd added them; there's no particular need to know in
future versions that they were added after the fact. ymmv.
OK, thanks, will do that next
: #700604)
+
+ -- Thorsten Glaser t...@mirbsd.de Fri, 15 Feb 2013 19:00:40 +
+
+mksh (40.9.20120630-6) unstable; urgency=low
+
+ * Revert the fix for LP#1104543 as it causes Debian #700526
+(not closing as it’s not a proper fix)
+
+ -- Thorsten Glaser t...@mirbsd.de Fri, 15 Feb 2013 17:44:20
+
+ [ Platonides ]
+ * Update config URL in README.Debian (Closes: #703804)
+
+ [ Thorsten Glaser ]
+ * Re-add LocalSettings creation snippet for support of the
+mediawiki-extensions Debian packaging (Closes: #703852)
+ * New upstream security-only release:
+- (bug 47251) SECURITY
Jay Berkenbilt qjb at debian.org writes:
hoping Jessie will ship with only one version of the tiff library:
[…]
I'd obviously like to get on this as soon as possible, but I understand
Agreed, but tiff depends on jpeg, and there are people who want to switch
jpeg to “jpeg-turbo” (still being
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu
nmu unscd_0.48-2 . ALL . -m Rebuild against eglibc major version 2.17
Hi,
for FusionForge I’m using unscd instead of nscd, which makes much
less trouble. It needs to be binNMU’d against
On Mon, 2 Sep 2013, Jérémy Bobbio wrote:
On the page described the transition to get rid of Ruby 1.8 [1],
How is this supposed to work, anyway?
• I don’t see either a bts entry or an explanation linked anywhere.
• ruby1.9.1 Build-Depends ruby1.8
bye,
//mirabilos
--
«MyISAM tables -will- get
Niels Thykier dixit:
Then there are more concrete things like ruby's test suite seg. faulting
on ia64 (#593141), ld seg. faulting with --as-needed on ia64
And only statically linked klibc-compiled executables work on IA64,
not dynamically linked ones. I’ve looked into it, but Itanic is so
retitle 779997 unblock: mksh/50d-5
tags 779997 - moreinfo
thanks
Axel Beckert dixit:
I've just made a pbuilder build whose debdiff only differs from the
debdiff posted here as follows, i.e. only in dates and version numbers:
Thanks, this looks as expected.
bye,
//mirabilos
--
igli exceptions:
@@ -1,3 +1,12 @@
+mksh (50d-4) unstable; urgency=medium
+
+ * QA upload.
+ * Backport upstream fix:
+- [tg] SECURITY: make unset HISTFILE actually work
+ * Adjust shell version accordingly
+
+ -- Thorsten Glaser t...@mirbsd.de Sat, 07 Mar 2015 22:16:53 +0100
+
mksh (50d-3) unstable
Niels Thykier dixit:
I see the upload has happened, but the diff seems to be very unlike the
one you included in the bug. A diffstat of what I see is:
[…]
I.e. a patch is being dropped and no other changes. Your original
debdiff suggested there ought to be changes to said patch instead.
tags 779997 - moreinfo
thanks
Niels Thykier dixit:
Ack, seems reasonable. Please have it uploaded to unstable and remove
the moreinfo tag once it is accepted.
ok, done
bye,
//mirabilos
--
This space for rent.
--
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a
Philipp Kern dixit:
>> Maybe wb could do a “dak ls” and whatever the equivalent for dpo mini-dak is.
>
>Unfortunately it is not being run on the same host as dak either.
Hm, rmadison then. What does packages.d.o/sid/binpkgname use? (On the
other hand, that’s often quite behind…)
bye,
On Fri, 23 Oct 2015, Emilio Pozuelo Monfort wrote:
> >> Ah, cool – so we have only to patch this tool to automatically
> >> use the highest number per batch on all affected architectures
> >> (or even to use the highest number if all architectures would
> >> be touched, but that’s probably an
On Fri, 23 Oct 2015, Emilio Pozuelo Monfort wrote:
> I can go back to scheduling binNMUs for release architectures only, or for ANY
> -x32. But I don't have the time to look at every architecture and determine
> which one needs a binNMU and which one has already done it. Anyway if your
OK. In
On Fri, 23 Oct 2015, Adam D. Barratt wrote:
> and testing), so the only way to be certain what binNMU number to use is to
> check manually. In practice what actually happens is that people forget about
Maybe wb could do a “dak ls” and whatever the equivalent for dpo mini-dak is.
I’ll have a
On Fri, 23 Oct 2015, Adam D. Barratt wrote:
> wanna-build does, yes, but at least the Release Team tend to use the "wb"
> wrapper tool which automatically works out the next free number on each
> architecture.
Ah, cool – so we have only to patch this tool to automatically
use the highest number
On Fri, 23 Oct 2015, Emilio Pozuelo Monfort wrote:
> I didn't say once per arch. I said once per package, which is worse. I
> normally
> schedule binNMUs for several dozens packages. Multiply that by several
But you need to look the number up anyway? The wanna-build
--binNMU parameter gets the
+ be denied reading.
+
+ Contact me (mirabilos) in #cvs on irc.freenode.net if you have
+ any questions about this change or require further support.
+
+ -- Thorsten Glaser <t...@mirbsd.de> Tue, 28 Mar 2017 19:54:01 +0200
+
cvs (2:1.12.13+real-7) unstable; urgency=high
rcs2log no longer
retitle 860025 unblock: bsdmainutils/9.0.12+nmu1
tags 860025 - moreinfo
thanks
Niels Thykier dixit:
>Please go ahead and remove the moreinfo tag once the NMU has reached
>unstable + have been built on all relevant architectures.
According to
On Wed, 12 Apr 2017, Niels Thykier wrote:
> If the maintainer agrees with you on it, I am happy to accept that patch
> for stretch.
OK, thanks.
> Mind you, I am also open to reviewing his proposal of
> adding those headers even with -a (letting -a override the
> auto-generated ones when there
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
I would like to request a pre-approval before uploading a fixed
package. The bug in question is #859935 (bsd-mailx sends 8bit
messages without MIME headers).
I consider this
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
I would like to request another pre-approval for a one-line fix
to bsdmainutils to fix a bad patch. The Debian bug is #859933.
In jessie (and on BSD), calling 'calendar' would output:
On Fri, 14 Apr 2017, Robert Luberda wrote:
> The patch looks OK. The addition of -D_GNU_SOURCE flag causes warnings
> during compilation of files that already #define _GNU_SOURCE, but this
> is easy to fix by using #define in main.c.
Hm ok… as long as the definition is before *any* inclusion.
Adrian Bunk dixit:
>As an example, what happens if I debootstrap and deploy the resulting
>filesytem to a large number of identical embedded systems without
>entropy sources?
Just get into a habit of not doing so, for example by modifying the
image during each writing process.
Having the
Theodore Y. Ts'o dixit:
>that problems helps most of our users, and we shouldn't let the
>perfect be the enemy of the good.
Agreed. Start small, then enhance one bootloader at a time.
Or boot protocol, I assume.
>Also note that the bootloader has depend on userspace to refresh the
>seed
On Wed, 17 Apr 2019, Thorsten Glaser wrote:
> it should sit in sid for a bit longer, that’s no problem either.
Oops, I apparently fsck’d up (but why this didn’t show up in lintian
for -5 but does show up for the upload in the experimental branch I’m
currently doing, I’ll never know) in DE
und for DEP 5 syntax in a complex case
+ * Fix share/plugins/notenames.qml and general copyright years
+ * Correct copyright info for the demos
+
+ -- Thorsten Glaser Thu, 18 Apr 2019 14:01:18 +0200
+
+musescore (2.3.2+dfsg2-5) unstable; urgency=medium
+
+ * debian/patches/experiments/
On Tue, 2 Apr 2019, Rene Engelhard wrote:
> We as distros can patch it for LibreOffice, but this change breaks
> LibreOffice out there unless
> patched, and I doubt they will (or will be happy) to add extra stanzas for
> "Debian", "Ubuntu" or
> whatever else.
>
> I really believe this should
+1,9 @@
+musescore (2.3.2+dfsg2-7) unstable; urgency=high
+
+ * Disable webkit functionality (Closes: #931021)
+
+ -- Thorsten Glaser Mon, 24 Jun 2019 18:07:46 +0200
+
musescore (2.3.2+dfsg2-6) unstable; urgency=medium
* Workaround for DEP 5 syntax in a complex case
--- a/debian/control
+++ b
(2.3.2+dfsg2-7~deb10u1) buster; urgency=high
+
+ * Rebuild 2.3.2+dfsg2-7 for buster-updates (cf. #931040)
+
+ -- Thorsten Glaser Wed, 03 Jul 2019 14:22:57 +0200
+
+musescore (2.3.2+dfsg2-7) unstable; urgency=high
+
+ * Disable webkit functionality (Closes: #931021)
+
+ -- Thorsten Glaser Mon, 24
Hi,
>> It would need to be a new upload, indeed. The version seems sensible,
>> and target would indeed be "buster". Please attach a debdiff of the
>> proposed upload to this report (but do not upload it at this stage).
thanks, will do.
>Actually, as Salvatore pointed out on IRC, that should be
Package: release.debian.org
Severity: normal
In #931040 I was indicated to postpone the fix for #931021 to
past the initial buster release, so it can get some more testing
in unstable in the meantime. (That being said I hope to get
MuseScore 3.x into unstable as opposed to experimental rather
complicated:
+ they were originally PD “Written by Jezar at Dreampoint”,
+ but modified by Werner who, as EU citizen, cannot relinquish
+ copyright, so they are, effectively, published under the same
+ terms as the rest of MuseScore (GPLv2); document that
+
+ -- Thorsten Glaser Tue, 16
Adam D. Barratt dixit:
>Please go ahead; sorry for the delay.
Done, thanks!
bye,
//mirabilos
--
> Hi, does anyone sell openbsd stickers by themselves and not packaged
> with other products?
No, the only way I've seen them sold is for $40 with a free OpenBSD CD.
-- Haroon Khalid and
Hi again, sorry for bothering, but…
… in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931040#10
it was indicated this should go into the first point release,
and https://lists.debian.org/debian-devel-announce/2019/07/msg2.html
indicates that that will be done in little more than a weel,
On Wed, 2019-07-03 at 06:43 +0100, Adam D. Barratt wrote:
> and target would indeed be "buster". Please attach a debdiff of the
> proposed upload to this report (but do not upload it at this stage).
Is it OK to upload now?
Thanks,
//mirabilos
--
15:41⎜ Somebody write a testsuite for helloworld
Hi Adam,
>+sssd (1.16.3-3.2) buster; urgency=medium
>
>1.16.3-3.1+deb10u1 would be more conventional, please.
Yes, indeed (although there has been precedence for this,
considering the version numbers are only so they don’t
confluct with later uploads in $distro+1). I admit I had
not consciously
.
+(Closes: #946847)
+
+ -- Thorsten Glaser Fri, 21 Feb 2020 14:31:19 +0100
+
sssd (1.16.3-3.1) unstable; urgency=high
* Non-maintainer upload.
diff -u sssd-1.16.3/debian/patches/series sssd-1.16.3/debian/patches/series
--- sssd-1.16.3/debian/patches/series
+++ sssd-1.16.3/debian/patches
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu
nmu unscd_0.53-1+b2 . ANY . unstable . -m "Rebuild against glibc 2.30"
As usual with new glibc major versions, please binNMU unscd quickly,
not having it prevents the installation of the
Simon McVittie dixit:
>To -ports people (cc'd): for the -ports architectures, mutter and
>muffin should be rebuilt as above on all the 32-bit ports, with the
>same dep-wait. Additionally, some differences in build order mean that
>gtk+3.0 needs a rebuild on m68k (but not on release architectures
On Thu, 3 Dec 2020, tony mancill wrote:
> Given that the JVM bug can affect any application seems to tilt the
> scale towards proceeding with the JDK update, so the release of an
> upgrade path for Jenkins is a relief.
How about versioning it differently? Make it 11.0.9-2 for a while?
Convince
On Wed, 18 Nov 2020, Matthias Klose wrote:
> On 11/18/20 8:03 PM, Adrian Bunk wrote:
> > New OpenJDK versions tend to cause both buildtime and runtime breakages
> > in reverse dependencies, some of them hard to resolve and requiring
> > updates to new upstream versions which in turn require new
block 976811 by 980567
thanks
On Sat, 12 Dec 2020, Ondřej Surý wrote:
> And let me restate that it’s not my intent to make anyone’s life hell and
> I am willing to help with any package (as usual). I am just trying to do
> the most sane thing to do security and maintainer wise.
You probably
) unstable; urgency=medium
+
+ * Add patch to fix large soundfonts/samples’ offsets
+
+ -- Thorsten Glaser Sun, 06 Jun 2021 15:22:08 +0200
+
polyphone (2.2.0.20210109+dfsg1-1) unstable; urgency=medium
* Improve compiler flags handling, via MuseScore packaging
diff -Nru polyphone-2.2.0.20210109
-05 17:57:30.0
+0100
+++ musescore2-2.3.2+dfsg4/debian/changelog 2021-06-05 18:04:54.0
+0200
@@ -1,3 +1,9 @@
+musescore2 (2.3.2+dfsg4-15) unstable; urgency=medium
+
+ * Fix soundfont-related crashes or audible artefacts (Closes: #985129)
+
+ -- Thorsten Glaser Sat, 05 Jun 2021
; urgency=medium
+
+ * Fix a -Wpointer-sign in escaping code
+ * Shrink escape diff (algorithm unchanged) for easier review
+
+ -- Thorsten Glaser Mon, 31 May 2021 02:42:55 +0200
+
+mksh (59c-7) unstable; urgency=medium
+
+ * Do not use sigsetjmp(â¦, 0) with klibc (cf. #988027)
+ * Cherry-pick
Ben Hutchings dixit:
>Thorsten Glaser tested the s390x fix in unstable. It has not (yet)
>been manually tested in this version.
Unfortunately we don’t have a baseline, as the only test I had that
triggered this doesn’t trigger in buster (probably because only a
newer GCC scheduled things
/debian/changelog 2021-02-01 02:44:43.0 +0100
+++ mc-4.8.26/debian/changelog 2021-06-01 15:26:23.0 +0200
@@ -1,3 +1,10 @@
+mc (3:4.8.26-1.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Fix PKZIP archive handling, patch backported from upstream
+
+ -- Thorsten Glaser
the correct FPU registers
+(f8‥f15 not f1/f3/f5/f7) (Closes: #943425)
+
+ -- Thorsten Glaser Thu, 27 May 2021 00:12:10 +0200
+
klibc (2.0.8-6) unstable; urgency=medium
* Upload to unstable
diff -Nru
klibc-2.0.8/debian/patches/0041-klibc-set-long-jmp-s390x-save-restore-the-correct
Package: apache2
Version: 2.4.48-3
Severity: important
X-Debbugs-Cc: t...@mirbsd.de, debian-release@lists.debian.org
Having just upgraded machines from 2.4.46-4 to 2.4.48-3
I now get daily¹ cron mails:
| From: Anacron
| Message-ID: <20210702075325.946f340...@ci-busyapps.lan.tarent.de>
| To:
1 - 100 of 134 matches
Mail list logo
