Hi,
xorgxrdp at Salsa is still on the previous version and using a clone
here is what I am getting:
$ git clone https://salsa.debian.org/debian-remote-team/xorgxrdp.git
$ cd xorgxrdp
$ uscan
uscan warn: In debian/watch no matching files for watch line
https://github.com/neutrinolabs/xorgxrdp/re
refreshes it
>
> So in the normal case, approximately 30 mins after the mirror push, you
> should have correct uscan information in UDD.
>
> Since I don't know about DPT, I cannot help on that side.
>
> Lucas
>
>
> On 22/07/24 at 20:43 +0200, Patrice Duro
|
(2 lignes)
Le lun. 22 juil. 2024 à 20:37, Patrice Duroux
a écrit :
>
> HI,
>
> After the (very) recent upload of xorgxrdp (version1:0.10.0-2),
> I was curious to check both DPT and UDD about it.
> But currently DPT shows me:
>
> Problems while searching for a new upstr
HI,
After the (very) recent upload of xorgxrdp (version1:0.10.0-2),
I was curious to check both DPT and UDD about it.
But currently DPT shows me:
Problems while searching for a new upstream version high
uscan had problems while searching for a new upstream version:
In debian/watch no matching fi
Ok so this is probably due to the version of the DHs used when generating the
postrm script during packaging.
On my system, the diversity is quite large regarding all the installed packages
and the dh_installsystemd:
$ grep -ho 'dh_installsystemd/.\+' /var/lib/dpkg/info/*.postrm | cut -d '/' -
Hi,
Nice I found some similar cases to your one.
But I have even more strange cases like:
$ systemctl list-units --all "alsa*"
UNIT LOAD ACTIVE SUB DESCRIPTION
● alsa-restore.service not-found inactive dead alsa-restore.service
● alsa-state.service not-found
Hi,
By the time on my Sid system, there is an accumulation of:
$ systemctl list-units --all | grep '●'
● run-credentials-systemd\x2dresolved.service.mount
not-found inactive dead
run-credentials-systemd\x2dresolved.service.mount
● run-credentials-systemd\x2dsysctl.serv
so could I suggest to consider the following packages:
https://tracker.debian.org/pkg/sump-logicanalyzer - 2011-07-27
https://tracker.debian.org/pkg/libvirt-tck - 2011-11-13
https://tracker.debian.org/pkg/dtc - 2012-06-08
https://tracker.debian.org/pkg/tinysvm - 2013-02-16
https://tracker.debian
Thanks!
My point is more on this fact:
is this a consequence of the fact that both src:puppet (6.16.0-1) and
src:puppetserver (8.4.0-1~exp1) are in experimental? And if this is
the case, why should the former still be there?
Hi,
Not sure where to address my point here.
https://tracker.debian.org/pkg/puppet shows exp: 6.16.0-1
https://tracker.debian.org/pkg/puppetserver shows exp: 8.4.0-1~exp1
And as both puppet and puppetserver provide the same binary packages
(puppet-master and puppet-master-passenger), it is a bit
Hi Lucas,
My curiosity sometimes pushes me to look at the list of packages that haven't
been uploaded to the archive both in unstable and experimental releases in more
than a certain number of years. And UDD is so useful for that!!
Many thanks,
Patrice
web/cgi-bin/mentors.cgi:if l['distribution'] == 'unstable'
web/cgi-bin/mentors.cgi:elsif l['distribution'] == 'experimental'
web/cgi-bin/mentors.cgi: puts "#{l['distribution']}"
And here it is the 'mentors_most_recent_packag
Hi,
I am a bit surprised with the following output:
udd=> select distinct distribution from upload_history;
distribution
-
experimental
froxzen unstable
froze unstable
frozen
frozen unstable
frozen unstable
frozen unstable contrib
frozen woody
f
Hi,
I do not know if this is something already addressed.
Otherwise could it be interesting to handle such a situation in a
Debian QA perspective?
Regards,
Patrice
$ apt-file search environ.7.gz
manpages: /usr/share/man/man7/environ.7.gz
manpages-cs: /usr/share/man/cs/man7/environ.7.gz
manpages
Dear weston maintainers,
If I follow well, this request is already closed by this commit:
https://salsa.debian.org/xorg-team/wayland/weston/-/commit/a3edbe19bd55b8eee64e0a40c459c25e22afb4a9
that is included in 11.0.0-2 (rc-buggy).
Dear QA team,
My trouble was that its Debian Package Tracker page
Hi,
My starting point is:
https://tracker.debian.org/pkg/libxmp
that does not show the new upstream 4.6.0 (since 2023-06-15)
and UDD says also that upstream_version is 4.5.0 and not 4.6.0
Are the Debian Tracker content based on UDD?
How often is UDD content updated?
I checked at: https://udd.de
Nice catch!
Even if it is also not available in a Debian package.
Let see if this one is less runtime sensitive and not suffering from the lack of
an installation procedure. Using codesearch-cli.py as is (and without modifying
the Python env by anyway) outside its own directory will throw a Python
Hi again,
Regarding the use of >&2 redirection in some echoing message,
is this useful when it is not to really do something special (hiding, ...)?
For instance:
$ sed -n 60,61p /var/lib/dpkg/info/xserver-xorg-legacy.postinst
echo "not updating $XWRAPPER_CONFIG; problems communicating" \
Hi,
Thanks for all your replies.
I built a small script that based on codesearch-cli tries to
approximate(*) the current state and
here is its current output:
[preinst]
adduser: 1useradd: 5both: 0 ()
deluser: 0userdel: 0both: 0 ()
addgroup: 12groupadd: 3both: 0 ()
delgrou
Hi,
After considering https://piuparts.debian.org/sid/fail/mrtg_2.17.10-4+b1.log
and reporting #1034530, I would like to be sure that another case
like: https://piuparts.debian.org/sid/pass/pipewire_0.3.65-3.log is
more tricky due to that pipewire may be purged after both with adduser
have been a
Sorry maybe I wasn't clear enough, but my purpose was more to track packages
facing such cases (a subset of my first pattern):
chiark-scripts: /usr/lib/python2.7/dist-packages/fishdescriptor/__init__.py
chiark-scripts: /usr/lib/python2.7/dist-packages/fishdescriptor/indonor.py
gtimelog: /usr/lib
Hi,
I am facing ^M (\r) character in the .build output file using sbuild
on my system (Sid).
For instance:
$ file timidity_2.14.0-9_amd64-2023-03-18T18:33:37Z.build
timidity_2.14.0-9_amd64-2023-03-18T18:33:37Z.build: ASCII text, with
very long lines (307), with CRLF, CR, LF line terminators
It s
Hi,
Regarding my previous post about replacing '2&>1' by '2>&1', most of
the issues reported upstream have been closed. Great!
Another point is about the following command:
apt-file search -x 'python(2|3\.(0|2|4|5|6|7|8|9))'
?
Is there something about this related to the Debian packaging/policy?
Sorry but the title of my message is wrong: s/having/that should have/
So stupid to create bad noise in the message archives.
Thanks Bart Martens!
ps: more MR or issues have been submitted upstream (sup-mail, plptools, vice)
Le mar. 28 févr. 2023 à 15:51, Patrice Duroux
a écrit :
>
&
handle some of those?
But it sure would be a good thing.
Le mer. 1 mars 2023 à 18:06, James Addison a écrit :
>
> On Wed, 1 Mar 2023 at 15:53, Patrice Duroux wrote:
> >
> > Great, I will give a look at shellcheck.
>
> Thanks - if it can also detect these problems, then --
Sorry.
So I should have split this work into two patches and then sent one to
linux-perf-user and the other one to linux-kselftest.
Would it be possible to send an email to these (sub)lists with just a
ref to my first post then or do I really have to split the patch etc.?
Any script to magically do
Great, I will give a look at shellcheck.
Regarding the upstream cases, at least I started with two of them:
1. https://lkml.org/lkml/2023/3/1/396
2. https://github.com/apache/jena/pull/1787
And let's see my level of courage for the others.
Thanks!
Le mer. 1 mars 2023 à 01:38, James Addison a éc
Hi,
Following the recent case of #1032122 (chkrootkit: bad redirection
creating file '1'?) and previously #1030120 (ipmiutil: cron script is
creating file /root/1), I tried using Debian CodeSearch to look for
other possible wrong cases like those and here is for instance a list
of candidates to ch
Hi Holger,
> thanks for reaching out and reporting the issue, which I have now fixed
> with
>
https://salsa.debian.org/qa/jenkins.debian.net/-/commit/6503fafd91f58b4a3b4dbff4b358a1ac3a2b7d00
So simple, stupid me. :)
> It might take up to 24h until the fix has propagated everywhere and
> the fix
Hi,
I would have helped more but looking in the source code of
jenkins.debian.net, I could not understand why the 'Tested suite' list
is sorted differently than in the other pages.
Regards,
Patrice
Hi,
So I'm assuming you are talking about the contents of Installed-Build-Depends
which is part of the .buildinfo file of the build packages output.
Because I tried to check the .deb content, the UDD, the different index files of
the Debian pool and also DPT, to find such a relationship but with
Thanks!
But I am still surprise to see such case for instance:
curl -s https://ftp.debian.org/debian/dists/oldstable/main/source/Sources.xz |
xzgrep -A 3 "Package: appdirs"
Package: appdirs
Binary: python-appdirs, python3-appdirs, pypy-appdirs
Version: 1.4.0-2
Maintainer: Benjamin Drung
--
Pa
Hi,
I am surprised to find multiple entries for a given package and
architecture having different versions
in a specific (same distribution, release, component) source index file.
For instance:
curl -s https://ftp.debian.org/debian/dists/experimental/main/source/Sources.xz
| xzgrep -A 7 "Package:
Hi,
Regarding DUCK it seems not to be very active looking there:
https://tracker.debian.org/pkg/duck
and its VCS is not responding.
Perhaps I will consider another Debian tool then...
Subsidiary question: contrary to the recent Debian Janitor now in the list,
Debian Trends (https://trends.debia
Hi Paul,
That is a good point and I will look for this.
Thanks for the advice!
I also working on a tool that tries checking (and suggest updates) to a given
list of URLs: bad links, different cases of redirections, replacing http by
https, etc.
This exercice was first to go over, Paul, your nice
Dear QA Team,
I hope to address here an interesting point otherwise sorry for the noise.
You may already have a (better) way to track this but... where?
(I did not see something related in the long list of the Debian QA Group's Wiki)
Also I hope to not offend any maintainer work providing a list s
Dear Debian QA team,
For my curiosity, I am currently working to get a kind of QA webpage for the
list of packages that have not been «uploaded» since years (more than 3 by
default), for example: https://tracker.debian.org/pkg/beav, meaning also no
change across Debian releases.
Technically it is
Hi,
This reminds me also the work of Lucas:
https://trends.debian.net/
that is not a member of the list in the Wiki Page of the Debian QA Group:
https://wiki.debian.org/qa.debian.org
I just found this in the Debian Wiki:
https://wiki.debian.org/Trends
but I suppose it is a bit old regarding the
Dear Debian team,
I was thinking about the current Sid situation of jackd2 and libopus,
and I do not known if this was already discussed neither if there are
some (QA?) tools to address the following.
Is there a possibility to evaluate package dependency relation in terms
of, for instance:
- num
39 matches
Mail list logo
