On 5/11/24 8:47 PM, John Paul Adrian Glaubitz wrote:
export PYTHONPATH = $(CURDIR)
Try setting it to the build_dir path:
PYTHONPATH=$(shell pybuild --print build_dir --interpreter python3)
Kind Regards,
Bas
--
GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146 50D1
On 3/21/24 11:47 AM, Ian Jackson wrote:
Ian Jackson writes ("Re: Package marked for autoremoval due to closed bug? [and 1
more messages]"):
Steve, could you please do this for *all* the time_t transition RC
bugs?
IMO things are currently ON FIRE.
Exaggeration is an art.
If no-one else
On 3/15/24 7:31 AM, Andreas Tille wrote:
g++ -std=gnu++17 -shared -L/usr/lib/R/lib -Wl,-z,relro -o V8.so RcppExports.o
bindings.o -lv8 -lv8_libplatform -L/usr/lib/R/lib -lR
It likely works by adding the library path, e.g.:
g++ -std=gnu++17 -shared -L/usr/lib/R/lib -Wl,-z,relro -o V8.so
On 2/10/24 13:40, Holger Levsen wrote:
On Sat, Feb 10, 2024 at 12:16:48PM +, Holger Levsen wrote:
I'm also of the opinion that *someone* should do this for all these bugs
but I am too lazy to do it myself.
sebas...@debian.org has thankfully done this, 15min before I wrote the above.
On 9/26/23 16:56, Daniel Gröber wrote:
The old web service had explainations and additional context for the
various lintian tags. UDD doesn't seem to offer that so where can we find
this information now?
lintian-explain-tags(1) is your friend:
How would one implement this in the common Salsa CI pipeline?
There is an old issue for this [0], but unless someone provides an MR
its unlikely to get implemented.
Occasional rebuild campaigns like this don't catch regression in a
timely manner. Having a build-twice job in the Salsa CI
On 7/27/23 15:24, Simon McVittie wrote:
On Thu, 27 Jul 2023 at 13:49:33 +0200, Timo Röhling wrote:
recently there have been two independent changes in the Python and
CMake world which conspired to FTBFS a number of packages.
TL;DR: export DEB_PYTHON_INSTALL_LAYOUT=deb_system in d/rules
Is
On 6/29/23 12:32, Helmut Grohne wrote:
On Thu, Jun 29, 2023 at 08:19:51AM +0200, Sebastiaan Couwenberg wrote:
On 6/28/23 21:49, Helmut Grohne wrote:
Debian GIS Project
postgis
qgis
Why is postgis on this list?
$ grep -c Replaces debian/control*
debian/control:0
debian
On 6/28/23 21:49, Helmut Grohne wrote:
Debian GIS Project
postgis
qgis
Why is postgis on this list?
$ grep -c Replaces debian/control*
debian/control:0
debian/control.in:0
Kind Regards,
Bas
--
GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750
On 1/5/23 14:13, Simon McVittie wrote:
2. If there is already a version in experimental that is unsuitable for
the next stable release, because there's only one experimental, in the
rare case that upstream bumps the SONAME of the "old" branch, we can't
do as asked. For example:
On 1/5/23 12:26, Paul Gevers wrote:
Are there objections against this workflow? (Or voices from people who
This has been a best practice for quite a while, high time to make it
hard requirement.
Kind Regards,
Bas
--
GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146
On 12/15/22 10:34, Andrius Merkys wrote:
However, I have no idea why '-o 0 -g 0' options are used. They do not
seem to be used before.
Recent changes in debhelper, see:
https://salsa.debian.org/debian/debhelper/-/commit/ca66cf4bc74fe31b3d5c8131788e7fdd8731
On 11/21/22 17:56, Peter Wienemann wrote:
Any hints pointing towards the underlying issue are appreciated.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024520
Retrying the build by giving back the package fixes the issue.
Kind Regards,
Bas
--
GPG Key ID: 4096R/6750F10AE88D4AF1
On 10/20/22 12:25, Andrej Shadura wrote:
The version of pkgconf package providing the pkg-config binary package has been
sitting in experimental for some time. I think I have tested the upgrade
process quite extensively, but it would still be great if someone else could
have a look. In any
On 10/20/22 12:25, Andrej Shadura wrote:
I’ve been rebuilding packages with pkgconf for the past couple of weeks, and it
looks very good so far:
http://pkgconf-migration.debian.net/
The "Failures only" page is empty.
Kind Regards,
Bas
--
GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint:
On 10/2/22 04:23, Adam Borowski wrote:
This leaves one big set: packages that fail the clean step due to
undeclared B-Depends. According to the Policy:
# "clean"
#Only the "Build-Depends" and "Build-Conflicts" fields must be
#satisfied when this target is invoked.
... which makes
On 9/12/22 14:01, Enrico Zini wrote:
The Debian libgeos++-dev package has intentionally stopped[2] shipping
some include files that are needed to build programs with the C++ API,
stating:
Upstream removed the .inl files in 3.11.0:
On 8/22/22 07:15, Steve Robbins wrote:
Oh. I did use Eller -- but the architecture is listed as mipsel. I need
mips64el
eller has mips64el chroots too, just like there are i386 chroots on the
amd64 porterbox:
sebastic@eller:~$ schroot -l | grep mips64el
On 8/22/22 05:36, Steven Robbins wrote:
The list at https://db.debian.org/machines.cgi suggests all available machines
are "buildd" and restricted.
eller.debian.org is the mipsel/mips64el porterbox.
Kind Regards,
Bas
--
GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D
On 3/1/22 12:48, a a wrote:
Today a tried to access contents of debian instaler git repository on
salsa.debian.org and the server responded with 403 error. Next i tried
other content located on said server with the same resposne. Was there a
change in access policy or something is wrong with the
On 3/1/22 10:54, Julien Puydt wrote:
Le mardi 01 mars 2022 à 10:34 +0100, Sebastiaan Couwenberg a écrit :
On 3/1/22 10:28, Julien Puydt wrote:
Is there really no mips64el porterbox, or is it only a transitory
situation?
eller.debian.org has mips64el chroots.
How do I use one of those
On 3/1/22 10:28, Julien Puydt wrote:
Is there really no mips64el porterbox, or is it only a transitory
situation?
eller.debian.org has mips64el chroots.
Kind Regards,
Bas
--
GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
On 1/28/22 07:53, Ole Streicher wrote:
Hi,
I just observed that many of my packages that are currently in unstable
are not migrating because of
| Not touching package due to block request by elbrus (Follow the freeze
| policy when applying for an unblock)
where the "freeze policy" is linked
On 6/18/20 10:15 AM, mer...@debian.org wrote:
> In addition to that, "Watch" column displays dashes ("-") only.
That's due to #932296
Kind Regards,
Bas
--
GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
On 4/8/20 8:54 AM, Mechtilde Stehmann wrote:
> How can I solve it?
Run uscan on your own system to check for new upstream releases.
This is a known issue due to the high number of packages that are
checked by the QA servers, see: #955268.
Kind Regards,
Bas
--
GPG Key ID:
On 4/4/20 9:28 AM, Lucas Nussbaum wrote:
> On 04/04/20 at 08:09 +0200, Paul Gevers wrote:
>>> I keep wondering if we should make an effort to remove from testing
>>> packages whose packaging 'style' is clearly outdated, such as packages
>>> not updated since 2004 ('beav' is an example)...
>>
>> Is
On 3/21/20 1:29 PM, Ondřej Surý wrote:
> This seems like a regression to me, but before I fill a bug with lintian, is
> there anything I can do to my packages to fix this?
It's fixed in lintian (2.58.0), see:
https://bugs.debian.org/954146
Kind Regards,
Bas
--
GPG Key ID:
On 2/24/20 4:40 PM, Andreas Tille wrote:
> On Mon, Feb 24, 2020 at 04:07:37PM +0100, Sebastiaan Couwenberg wrote:
>> On 2/24/20 4:04 PM, Andreas Tille wrote:
>>> This worked since we moved to Salsa but since some weeks only
>>> "Tag push" is triggeri
On 2/24/20 4:04 PM, Andreas Tille wrote:
> This worked since we moved to Salsa but since some weeks only
> "Tag push" is triggering any mails. Did I missed something
> that the behavious on push events had changed or is this a bug
> on Salsa which I should report?
You need to reconfigure the
On 12/29/19 3:53 PM, Theodore Y. Ts'o wrote:
> On Sun, Dec 29, 2019 at 09:52:44AM +0100, Enrico Zini wrote:
>> some time ago I uploaded a new version of dballe, which went through NEW
>> because of a change in binary package names (SONAME bump, IIRC). It took
>> two weeks to go through NEW and I
On 4/13/19 10:20 AM, Lucas Nussbaum wrote:
> Additionally (and much more controversially I guess :-) ) I also added
> an analysis of "package smells"[3], such as "not using dh", "not using a
> recent debhelper compat level", "not using a 3.0 source format", etc. I
> understand that in some cases
On 08/16/2018 07:45 AM, Paul Wise wrote:
> On Thu, Aug 16, 2018 at 4:32 AM, Alec Leamas wrote:
>> But where is that old packaging repo?
https://salsa.debian.org/debian-gis-team/opencpn
You should talk to the OSGeoLive people, who kept the opencpn package in
their Ubuntu based distribution.
You
On 06/29/2018 01:41 AM, Ian Jackson wrote:
> Paul Gevers writes ("Re: Bug filing for autopkgtest regressions? [Was: Re:
> appears to break multiple autopkgtests]"):
>> On 28-06-18 20:50, Sebastiaan Couwenberg wrote:
>>> Please don't file bugs until the trigger
On 06/28/2018 07:50 PM, Paul Gevers wrote:
> If one (me) can't determine the likely principle package that needs
> fixing after some effort [1], one bug (per upload of the triggering
> package) can be filed against the trigging package with the other
> packages in X-Debbugs-CC and in Affects at
On 05/25/2018 12:09 PM, Mattia Rizzolo wrote:
> On Thu, May 24, 2018 at 09:02:04PM +0200, Sebastiaan Couwenberg wrote:
>> On 05/24/2018 08:53 PM, Raphael Hertzog wrote:
>>> On Thu, 24 May 2018, Sebastiaan Couwenberg wrote:
>>>> None of the other QA tools mail the
On 05/24/2018 08:53 PM, Raphael Hertzog wrote:
> On Thu, 24 May 2018, Sebastiaan Couwenberg wrote:
>> None of the other QA tools mail the maintainer without them asking for
>> it, autopkgtest shouldn't either.
>
> With the exception of piuparts, none of them affect testing m
On 05/24/2018 08:28 PM, Raphael Hertzog wrote:
> Hi Paul,
>
> On Wed, 23 May 2018, Paul Gevers wrote:
>> I have had a complaint about my e-mail, boiling down to it should be
>> opt-in. I am not fully convinced (as I fear too many package maintainers
>> will miss the fact their autopkgtest delays
On 03/04/2017 10:13 AM, Simon Josefsson wrote:
> I have searched for non-free licensed IETF RFCs in the archive and found
> the files below in the stretch suite. Compare earlier work here [1].
Instead of trying to get standards documents out of Debian, I'd rather
see effort invested in working
On 01/20/2017 11:56 AM, Boyuan Yang wrote:
> # This one seems acceptable, too
> Vcs-Browser: https://anonscm.debian.org/cgit/pkg-foo/bar.git
>
> # This one is also acceptable
> Vcs-Git: https://anonscm.debian.org/git/pkg-foo/bar.git
These are the ones you should use, because both use encryption
On 01/14/2017 03:47 PM, Pirate Praveen wrote:
> Sebastiaan Couwenberg <sebas...@xs4all.nl> wrote:
>> No new source packages are allowed into stretch, new upstream
>> versions of packages which are in testing are still allowed.
>
> Is this applicable to new depende
On 01/14/2017 03:31 PM, Ralf Treinen wrote:
> Hi, I was under the impression that during the soft freeze (i.e, now) new
> usptream versions of packages that are already in testing are blocked
> from migrating. However, I can't find anything to this effect in the
> announcements by the release
On 11/05/2016 04:07 PM, Adrian Bunk wrote:
> On Sat, Nov 05, 2016 at 11:14:02AM +0100, Thomas Goirand wrote:
>> ...
>> Finally, with the above examples as illustration (and please, these
>> aren't attacks in any way...), I guess what I'm trying to say here is:
>>
>> While disruptive changes are
On 11/05/2016 01:39 PM, Geert Stappers wrote:
> Today is november fifth, day of the soft freeze in the Debian release
> schedule.
The soft freeze was moved to January 5th, today is the day of the
transition freeze:
"
Key release dates
[2016-Nov-05] Transition freeze
[2016-Dec-05] Mandatory
On 10/28/2016 02:40 PM, Andreas Tille wrote:
> On Fri, Oct 28, 2016 at 01:18:37PM +0100, James Cowgill wrote:
>>
>> I just tried building the version of cimg in its git repo and it worked
>> fine...
>>
>> It looks like the % and & handling was fixed in doxygen 1.8.12 which is
>> in unstable. I
On 10/01/2016 07:47 PM, Ruben Undheim wrote:
> Can anyone tell me why 'yosys' is marked for autoremoval from testing because
> of a bug which has already been fixed?
>
> See here:
> https://tracker.debian.org/pkg/yosys
>
> The bug #835678 was fixed in (and is marked as such) in 0.6-7 which is
Dear Santiago,
Thanks for publicly shaming me, makes me feel much better about your
bugreports.
On 09/13/2016 01:49 PM, Santiago Vila wrote:
> You can't reproduce it, or you don't want to reproduce it?
I added the tag because I couldn't reproduce the issue in unstable where
we build our
On 25-01-16 19:47, Bastien Roucaries wrote:
> I expect more problems detected in the next few days
I guess the autorejects for Multi-Arch: no are among those problems.
The use of Multi-Arch: no was suggested by
https://lintian.debian.org/tags/old-style-config-script-multiarch-path.html
The
On 19-08-15 10:37, Ghislain Vaillant wrote:
Just to report that d-sicience-maintainers [1] keeps receiving email
about an upload (clblas/2.6-2) which has been accepted already.
Removing the left over .changes file should fix this, you can use `dcut`
for this:
dcut rm -f
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 03/08/2015 12:43 AM, Guus Sliepen wrote:
On Sun, Mar 08, 2015 at 12:08:56AM +0100, Bas Couwenberg wrote:
* Package name: node-isarray
isarray provides Arrray#isArray for older browsers.
node-isarray is required for
There was webmin/usermin for a long time in debian, until it was kicked
off.
The repo masters claimed, bacaus of bad coding. They named ist
Spaghetti
code or similar.
That's not how I remember it. Jaldhar H. Vyas had the package removed
because he was not longer able to maintain it, not
Package: wnpp
Owner: Bas Couwenberg sebas...@xs4all.nl
Severity: wishlist
X-Debbugs-CC: debian-devel@lists.debian.org,debian-...@lists.debian.org
* Package name: tinyows
Version : 1.1.0-3
Upstream Author : Barbara Philippot, Olivier Courtin and the MapServer
team.
* URL
Package: wnpp
Owner: Bas Couwenberg sebas...@xs4all.nl
Severity: wishlist
X-Debbugs-CC: debian-devel@lists.debian.org,debian-p...@lists.debian.org
* Package name: libpg-hstore-perl
Version : 1.03
Upstream Author : Galimov Albert a...@cpan.org
* URL :
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Zachary Palmer wrote:
I'm rather new at this, so I don't know exactly how I should proceed.
What is the process for screening my package?
Is this the appropriate mailing list to discuss the matter?
The debian-mentors list is probably a better
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Charles Plessy wrote:
Distribution of this software is prohibited. It may only be
obtained by downloading from Stanford's web site
(http://folding.stanford.edu and pages linked therein).
I guess that in that case, there would be a link
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Magnus Holmgren wrote:
Sebastiaan Couwenberg wrote:
Has there been any talk about moving to the BOINC infrastructure?
There used to be work on a BOINC [EMAIL PROTECTED] client, but this work has
stopped
due to personnel turnover.
See:
http
55 matches
Mail list logo
