ely it doesn't look like there was progress on #887649 this
cycle either. So I fear that we'll end up needing to tag both #887649
and #885563 bookworm-ignore. :(
Kind regards
Philipp Kern
could instead be read
from disk - i.e. the from the existing tzdata package?
This would add up to the load of all the various packages of various
languages that already need updating with every tzdata release.
Kind regards
Philipp Kern
age, that we should at least
temporarily disable stable/oldstable builds on the IPv6-only buildds.
I have commented out stretch and buster (and their corresponding
security and backports suites) on x86-conova-01 for now. I'll definitely
leave bullseye on, though. Not sure if there's another IPv6-only buildd
lingering around.
Kind regards and thanks
Philipp Kern
s
> Description: Set of fundamental utilities for Linux on S/390
> The package contains:
My assumption is that this is not fixable through -updates but requires
a point release to be properly fixed.
Kind regards and thanks
Philipp Kern
diff -Nru s390-tools-2.3.0/debian/changelog s390-
s.
I'd also suggest to do a roll call of porters and have them reconfirm
their involvement and what is expected from them. I don't think any such
thing happened in years now.
Kind regards
Philipp Kern
signature.asc
Description: OpenPGP digital signature
On 9/2/2019 9:06 PM, Clint Adams wrote:
> On Mon, Sep 02, 2019 at 06:40:24PM +0200, Philipp Kern wrote:
>> I would prefer JSON as an input format, looking roughly like this:
>>
>> [{"pkg": "haskell-active", "ver": "0.2.0.13-6"
On 2019-09-02 11:03, Joachim Breitner wrote:
Am Montag, den 02.09.2019, 10:57 +0200 schrieb Philipp Kern:
FWIW, I started working on this. Unfortunately we do not really have
transactions available to schedule all or nothing. If someone has a
creative idea on how to best signal back partial
On 2019-09-02 10:33, Emilio Pozuelo Monfort wrote:
On 29/08/2019 12:08, Philipp Kern wrote:
On 2019-08-29 11:46, Emilio Pozuelo Monfort wrote:
On 29/08/2019 11:17, Philipp Kern wrote:
On 2019-08-29 11:14, Emilio Pozuelo Monfort wrote:
Why don't you let the interested teams run the script
On 2019-08-29 11:46, Emilio Pozuelo Monfort wrote:
On 29/08/2019 11:17, Philipp Kern wrote:
On 2019-08-29 11:14, Emilio Pozuelo Monfort wrote:
Why don't you let the interested teams run the scripts and generate
the required
binNMUs (like they do now), and then you pull that from a cronj
anity checks.
What would those sanity checks be?
Kind regards
Philipp Kern
binaries used for this as the Haskell binNMU thing is
obviously written in Haskell rather than being a script.
Kind regards
Philipp Kern
InRelease files (not to mention that it doubles the
traffic for no-change cases), I'm surprised they aren't using InRelease
files yet.
Given the timeline, shouldn't we also get oldstable to ship an InRelease
file?
Kind regards
Philipp Kern
changes they
do not consider to actually be part of the ABI they support.)
Kind regards
Philipp Kern
em crazy to me to do that.
But I don't dispute that the complexity could be high to do this
properly. It's unfortunate that this came up that late, given that it
was already a problem for users of testing.
Kind regards
Philipp Kern
ion, even if still
disruptive. On the other hand I guess you'd need to start the cluster
for serving anyway for reindex to work and would then serve broken data
in the meantime, too?
Kind regards
Philipp Kern
ual
address space or don't have modern languages like Go or Rust around, it
quickly approaches the point where it's not worth it anymore.
Kind regards
Philipp Kern
x27;t actually rely on a support
contract.
For s390x I can say that the port was driven without any commercial
interest on both Aurelien's and my side.
Kind regards
Philipp Kern
On 6/10/18 11:40 AM, Andreas Beckmann wrote:
> can we tag
> "Invalid maintainer address pkg-foo...@lists.alioth.debian.org"
> bugs as stretch-ignore?
As we need a way to reach people, I suppose that'd only make sense if
the metadata has been fixed in unstable, no?
Kind regards
Philipp kern
gher priority to migrate. But it still doesn't
help when manual work is required because they are stuck behind a
transition.
Kind regards
Philipp Kern
signature.asc
Description: OpenPGP digital signature
ends on
krb5-kdc being up, it might be better to wait instead of trying to
contact a hanging kdc. But then the time is still better spent to
implement sd_notify(READY=1)... (But maybe not in stable?)
Kind regards
Philipp Kern
signature.asc
Description: OpenPGP digital signature
shared
> thing between those two teams rather than solely a w-b thing. It
> happens once every few years though so there isn't really a process to
> vet people.
So can we have an opinion on the current proposal, which is a single DD
(stapelberg)? As far as I know DSA's ticket is c
ent here was set by nomeata (at least), who schedules binNMUs for
OCaml and Haskell in unstable and hence required access across all
architectures. As long as we add persons relatively sparingly (the
request is for nother single person), I think we should be fine?
Kind regards and thanks
Philipp Kern
with older machines. I'll try to restart
the discussion again.
What's the venue to have this discussion in? :)
Kind regards and thanks
Philipp Kern
On 2017-07-21 15:51, Antoine Beaupré wrote:
On 2017-07-20 18:15:00, Philipp Kern wrote:
On 07/17/2017 09:41 PM, Antoine Beaupré wrote:
Let's not jump the gun here. We're not shipping NSS in
ca-certificates,
just a tiny part of it: one text file, more or less.
Yeah, and the consen
on?
Is that actually planned? Because the whole point of that was that
adding LE directly isn't actually critical. (And people should use the
chain provided by ACME rather than relying on certificates shipped by
Debian.)
Kind regards
Philipp Kern
signature.asc
Description: OpenPGP digital signature
t Mozilla enforced in NSS we
couldn't check in any other tools using ca-certificates. We also do not
sync the NSS version or backport the cert checks when such distrusts
happen. So we can only react in a similar way when the time for full
distrust has come (which is sort of the case now with the
00 +0100
> +++ cubemap-1.3.2/debian/changelog2017-05-27 11:17:45.0 +0200
> @@ -1,3 +1,9 @@
> +cubemap (1.3.2-1) unstable; urgency=medium
> +
> + * New upstream release (Closes: #863280)
> +
> + -- Philipp Kern Sat, 27 May 2017 11:17:45 +0200
> +
> cu
an't really judge whether this could be annoying in d-i,
> it seems to me that's just fixing a move which hadn't happened with the
> net.ifnames transition, for specific hardware?
FWIW, I have tested this on an installation and haven't seen any problems.
Kind regards
Philipp Kern
signature.asc
Description: OpenPGP digital signature
te safe about it, but it'd be
>> probably useful to have it for testing in d-i sooner than later.
> ACK, thanks. It migrated on its own already.
It'd also be nice if zipl-installer could still make it. #840230 is
pretty nasty.
Kind regards
Philipp Kern
signature.asc
Description: OpenPGP digital signature
- provide hardware for a buildd and am working with IBM to obtain
more support on that front
I am a DD.
I have no real opinion about -fPIE/-pie on s390x. Ubuntu sets both, so
it seems sane to me to do the same in Debian.
Philipp Kern
signature.asc
Description: OpenPGP digital signature
ackages would we need to install to keep track of new
major kernel versions in backports?
Kind regards and thanks
Philipp Kern
here are patches around for that.
* X drivers
I don't see backports for them.
Would it also mean X proper or "just" drivers?
Kind regards
Philipp Kern
e hw support.
Debian already makes use of Marist's resources. The challenge was/is to
get redundancy as DSA very sensibly insists on.
Kind regards
Philipp Kern
On Mon, Jun 13, 2016 at 07:33:56PM +, Niels Thykier wrote:
> Philipp Kern:
> > On 2016-06-05 12:01, Niels Thykier wrote:
> >> * amd64, i386, armel, armhf, arm64, mips, mipsel, powerpc, ppc64el,
> >>s390x
> >>- *No* blockers at this time from
and thanks
Philipp Kern
> seem suitable for inclusion in the next jessie point release?
Just considering nvme in addition to block and gracefully coping with it
not existing seems fine to me.
Kind regards
Philipp Kern
-LTS kernels can be quite short. [1] visualizes that. For instance
once the new LTS and the HWE got backported to the old LTS, all
intermediate ones (except base + new LTS) are dropped pretty much
instantly. You are also expected to migrate HWEs in the meantime
when new ones are made available.
K
on our TODO
> list if it is not listed in the bug tracker.
There's that and it helps to look at the debdiff to see what the actual
changes are. Cert updates are likely to be much easier on us than
packaging/script updates.
Kind regards
Philipp Kern
signature.asc
Description: Digital signature
autotools, changelog, and po
churn, but apart from that does only contain the above changes.
If needed I can back out the glib 2.46 change, although I'd prefer
to upload the whole thing as the change is arguably more correct
even with older glibs.
Kind regards and thanks
Philipp Kern
diff
ing of the various error conditions s390-dasd emits. Without
the logging you cannot deduce why it exited with a failure.
I'm also happy to skip the .po changes if needed, but it seemed cleaner
to just backport stretch's current version.
Kind regards and thanks
Philipp Kern
diff -Nru s390-da
t
> 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.
Kind regards
Philipp Kern
signature.asc
Description: Digital signature
/changelog b/debian/changelog
index 8dc90b9..4f2d3bc 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+netcfg (1.131+deb8u1) stable; urgency=medium
+
+ * Fix is_layer3_qeth on s390x to avoid bailing out if the network
+driver is not qeth. (Closes: #798376)
+
+ -- Philipp Kern
any of the patches into 0.6.5-1 and base a +deb8u1 off
that.
Kind regards and thanks
Philipp Kern
diff -Nru libinfinity-0.6.5/ChangeLog libinfinity-0.6.6/ChangeLog
--- libinfinity-0.6.5/ChangeLog 2015-01-18 02:29:29.071909458 +0100
+++ libinfinity-0.6.6/ChangeLog 2015-05-13 02:57:57.089748067 +02
Needed to delete the partial upload on the FTP server (FTP is so
terrible) and reupload.
Kind regards
Philipp Kern
--
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.de
om testing.
Kind regards
Philipp Kern
--
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/50e1ae2a77c3a7450871ca08b280e...@hub.kern.lc
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package libinfinity
libinfinity 0.6.5 contains multiple crash fixes. I'd feel much better if
those were included in the package. The diff is slightly noisy, but
mostly becaus
ks fine.
Please go ahead with the upload and report back once it has been
accepted.
Kind regards and thanks for your efforts
Philipp Kern
signature.asc
Description: Digital signature
retitle 773712 pre-approval: unblock: jenkins-job-builder/0.9.0-0.1
tag 773712 + confirmed
thanks
On Mon, Dec 22, 2014 at 03:29:36PM +0100, Michael Prokop wrote:
> The version of jenkins-job-builder as available in current jessie is
> totally broken with regards to its feature to delete Jenkins jo
retitle 773515 pre-approval: mono/3.2.8+dfsg-9
thanks
On Mon, Dec 22, 2014 at 10:11:51AM +, Jo Shields wrote:
> On 22/12/14 09:35, Philipp Kern wrote:
> > On Fri, Dec 19, 2014 at 11:55:00AM +, Jo Shields wrote:
> >> Please unblock package mono
> >
> > Thi
On Fri, Dec 19, 2014 at 11:55:00AM +, Jo Shields wrote:
> Please unblock package mono
This doesn't seem to have hit sid yet.
Kind regards
Philipp Kern
signature.asc
Description: Digital signature
tes where this
> package is installable. Ideally there would be a way to actually detect the
> Android kernel, I have not found that way.
I wonder if you could probe for either ashmem or binder?
Kind regards
Philipp Kern
signature.asc
Description: Digital signature
countries. These should
> also go into stable so that users can easily comply with current laws
> and use the full permitted ranges of frequency and transmit power.
please go ahead. Thanks!
Kind regards
Philipp Kern
signature.asc
Description: Digital signature
ported anymore.
if this request still applies, please provide an updated debdiff against stable
of what you want to ship. Thanks!
Kind regards
Philipp Kern
signature.asc
Description: Digital signature
'd be used.
Assuming that you tested that in a minimal chroot and that this is sufficient
vs. build-essential, I'd be inclined to approve the upload.
Kind regards
Philipp Kern
signature.asc
Description: Digital signature
houldn't pose
a problem when reviewing. If patch content itself changed, that'd be
different.
Kind regards
Philipp Kern
signature.asc
Description: Digital signature
sk you is it would be ok to upload this fix now (or if
> I must wait for jessie release). I know it is a purely cosmetic bug, no bad
> behavior is involved in any case.
Sounds good to me. Please ping the bug once it has reached the
archive. Thanks.
Kind regards
Philipp Kern
signature.asc
Description: Digital signature
-infinote (0.5.0-4) unstable; urgency=medium
+
+ * Correct libinfinity-0.6-dbg recommends on gobby-dbg.
+ * Remove the gobby-0.5 alternative unconditionally. (Closes: #768242)
+
+ -- Philipp Kern Wed, 12 Nov 2014 02:42:44 +0100
+
gobby-infinote (0.5.0-3) unstable; urgency=medium
* Update
by(src).)
Kind regards and thanks
Philipp Kern
signature.asc
Description: Digital signature
not want gobby-0.4 to stay around for jessie, it won't receive
any more updates upstream. net6 and obby are support packages only around
for gobby-0.4 and can (and should) hence go as well.
Kind regards and thanks
Philipp Kern
--
To UNSUBSCRIBE, email to debian-release-requ...@lists.debia
replaces my key signing key with the current one in the
keyring.
Kind regards
Philipp Kern
diff -Nru debian-archive-keyring-2012.4/active-keys/add-jessie-stable debian-archive-keyring-2014.1~deb7u1/active-keys/add-jessie-stable
--- debian-archive-keyring-2012.4/active-keys/add-jessie-stable 1970-01
Hi,
On Sat, Jul 26, 2014 at 09:29:47PM +0200, Philipp Kern wrote:
> Oh well, you just uncovered a bug that was not exposed widely because there's
> a fallback P-a-s in the toplevel directory:
>
> * All the triggers source triggers/common.
> * common says at the top:
ages-arch-specific"
* $SUITE is set subsequently but the file has already been source and hence
we get "/srv/buildd.debian.org/web/quinn-diff//Packages-arch-specific" for
all suites.
* This file exists and points to the sid checkout.
/srv/buildd.debian.org/web/quinn-diff/Packages-arch-
On Fri, Jul 25, 2014 at 02:19:38PM +0200, Johannes Schauer wrote:
> Quoting Philipp Kern (2014-07-24 00:25:41)
> > so I think this would rather be a question for stable, than for backports?
> Maybe. We'd be equally (if not more) happy if SRM would reconsider their
> decision (
chive can
hence be modified to incorporate the new syntax, stable tooling will no longer
work with them?
Kind regards
Philipp Kern
signature.asc
Description: Digital signature
sues.
Will it necessarily explode if both libcs are loaded into the same
address space or only if the broken functionality is used? Would
setjmp/longjmp only break if used across libc6/6.1 boundaries? Passing
around an incompatible pthread struct seems bad, though.
If this would work, a re-bootstrap w
1.0.3+really0.56-1?). Alternately, I could try backporting the kernel
> API, which looks fairly easy. Before I do that, what would the release
> team prefer?
Backporting the kernel API sounds good to me.
Kind regards and thanks
Philipp Kern
signature.asc
Description: Digital signature
Agreed, those won't happen. Just the changes to the csv files.
Kind regards
Philipp Kern
signature.asc
Description: Digital signature
stricter), or that people were more
tolerant to do incompatible changes. There was, as far back as I
remember, always the notion that things need to land in stable before
they can be used.
dist-upgrade path was a primary motivator, but handling of packages,
even source packages, with stable tooling
Hi,
On Thu, Apr 17, 2014 at 06:46:00PM +0200, Kurt Roeckx wrote:
> I would like to also add support for the padding extention in
> stable. It's part of the 1.0.1g release.
NACK, at least for now.
Kind regards
Philipp Kern
signature.asc
Description: Digital signature
Package: ftp.debian.org
Severity: normal
Dear FTP masters,
by tomorrow sparc's content should be dropped from testing (i.e., with
the next britney run at 22 UTC). Please deconfigure it from dak
afterwards.
Kind regards and thanks
Philipp Kern
--
To UNSUBSCRIBE, email to debian-release
s.tool is still linked against libgnustep-base1.22 because 1.24 is still
stuck in experimental.
Yavor, is there any plan to do the transition? #673538 didn't look like it was
blocking on us.
Kind regards
Philipp Kern
signature.asc
Description: Digital signature
aking the patch from #699740
> +(closes: #743925)
> +
> + -- Gerfried Fuchs Fri, 25 Apr 2014 16:47:00 +0200
ACK.
Kind regards
Philipp Kern
signature.asc
Description: Digital signature
g special.
I'd not make the change opt-in for the reasons you suggested.
Kind regards and thanks
Philipp Kern
signature.asc
Description: Digital signature
be the same bucket you'd want to
use, that seems to be the key takeaway here.
Kind regards
Philipp Kern
signature.asc
Description: Digital signature
You either need to get the armel, armhf builds to be removed from
unstable through a bug against ftp.debian.org or get the package to
build there again.
Kind regards
Philipp Kern
signature.asc
Description: Digital signature
ywhere.
It was pretty clear that it will take a while until we're at a point where
this can be done. But it doesn't make sense to run the tracker somewhere
different. Getting rid of an old interpreter version is something which
happens every one or two releases, so it's nothing n
o working on the port
both wrt buildd maintenance and debugging. He is listed on [1], too.
But obviously that does not imply GCC maintainance for s390*.
And indeed, we should've copied Bastian on this. I apologize.
Kind regards
Philipp Kern
[1] http://release.debian.org/wheezy/arch_qualify.h
What's the reason for them being versioned?
Kind regards
Philipp Kern
signature.asc
Description: Digital signature
attached. I emailed the maintainers
> of the packages and the uploaders (only for packages that aren't team
> maintained).
Please go ahead.
Kind regards
Philipp Kern
signature.asc
Description: Digital signature
mirror_2.45
Kind regards
Philipp Kern
signature.asc
Description: Digital signature
there are several options in this scenario.
my personal guess is that there's probably nothing s390x-specific to it,
it's probably broken with 64bit big endian. The d-ports build for
sparc64 fails as well.
Kind regards
Philipp Kern
signature.asc
Description: Digital signature
releases, and none of those created any trouble.
Thanks for trading the R release cycle with Debian's and for delaying the
release. The harm has already been done, so somebody should probably go
and create a transition tracker for it?
Kind regards
Philipp Kern
signature.asc
Description: Digital signature
+[Install]
+WantedBy=multi-user.target
Could the acpid maintainers upload this change with version
1:2.0.16-1+deb7u1 to t-p-u? Unstable does contain a new upstream version
and hence the fix cannot propagate from there, even though it's fixed in
unstable already.
Kind regards
Philipp Kern
--
n
+ sed -i -e
's/rfc3442-classless-static-routes;/rfc3442-classless-static-routes,
ntp-servers;/' /etc/dhcp/dhclient.conf
+ fi
Please don't do things with awk that can be realized with cut,
especially in a preinst. But since awk is still pseudo-essential
(pre-depends
believe there is precedent for
> an updated package in stable to update DNS root server hints in [0].)
please go ahead, thanks!
Kind regards
Philipp Kern
signature.asc
Description: Digital signature
pening gambit, some proposed dates,
> all of which appear to currently work for me:
>
> February 23rd
>
> March 2nd
>
> March 9th
These all work for me. I will be sort of offline, however, from February
14th to (including) 17th, which looks like the preparation range for th
But I guess both times
concerns about "not being built within the suite in question" might
apply. But we still do that for packages installed into *stable* (i.e.
across the major divergence between stable and unstable, or
at least into testing).
Kind regards
Philipp Kern
signature.asc
Description: Digital signature
> * iceape_2.7.12-1_powerpc.changes
thanks for the list. I reuploaded those packages. Please just mail
$arch@buildd.d.o next time.
> The log files for queued are now rotated. Older entries can be found in
> /srv/upload.debian.org/queued/log.*.xz.
Good to know, thanks.
Kind regards
Philipp Kern
ause the iceape-dbg is huge and the upload was cut off
somewhere in between. queued on ftp-master doesn't have any info beyond Feb
1st, and it never reached dak (neither for powerpc nor s390).
dput's now running on both in a screen. Hopefully that helps.
Kind regards
Philipp Kern
signature.asc
Description: Digital signature
tion, not us.
Kind regards
Philipp Kern
signature.asc
Description: Digital signature
ailure code 2?
I just want to be sure I understand the logic before ACKing it. (And sorry
for the delay on that.)
Thanks
Philipp Kern
signature.asc
Description: Digital signature
ight clarifications are among them.
Kind regards
Philipp Kern
signature.asc
Description: Digital signature
rated, so that might warrant an addition to policy? ("Do
not build a binary package that has the name of a totally unrelated source
package"?)
Kind regards
Philipp Kern
--
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20130115122433.ga12...@hub.kern.lc
SRMs, is it OK to upload at the moment?
yes. The sooner the better. ;)
Kind regards
Philipp Kern
signature.asc
Description: Digital signature
On Sat, Jan 12, 2013 at 04:38:03PM +, Adam D. Barratt wrote:
> On Thu, 2012-12-27 at 21:56 +0100, Philipp Kern wrote:
> > On Wed, Oct 24, 2012 at 05:44:00PM +0100, Adam D. Barratt wrote:
> > > From a very quick scan and with apologies if I'm missing something
> >
On Thu, Dec 27, 2012 at 09:56:34PM +0100, Philipp Kern wrote:
> On Wed, Oct 24, 2012 at 05:44:00PM +0100, Adam D. Barratt wrote:
> > From a very quick scan and with apologies if I'm missing something
> > due to unfamiliarity with the codebase:
> >
> > -my @offic
ot yield a situation where one
can use shell escapes or similar? It's "just" about being able to bypass
the SPF check by supplying crafted data?
Kind regards
Philipp Kern
signature.asc
Description: Digital signature
unhappy about how
this went, but I think we should have the fixes 9.8.4 provides in wheezy.
Kind regards
Philipp Kern
signature.asc
Description: Digital signature
ese from exp, the
> build-depends needs to be bumped (i.e. it will require a sourceful upload)
That's not exactly true, it is possible to add build-depends (or
-conflicts) for a one-shot binNMU. But for clarity and further binNMUs
(against unstable) doing the right thing a sourceful uploa
to
> keep working.
there's no reason at all to incur a PATH-based lookup for something that
has a fixed path in a distribution. Obviously the burden's on the one
who changes the location of a binary to grep the archive for changes
that need to be made.
Kind regards
Philipp Kern
sig
1 - 100 of 1035 matches
Mail list logo
